Page 6 of 6

Re: Sources.list

Posted: 03 Mar 2018 09:29
by Arjen Balfoort
I don't remember exactly why we decided to leave the updates repository out but I think it had to do to maximize stability of the system and only allow security updates.

[Edit]
If decided different, I could write that line to the sources.list file with an update on solydxk-system. Of course, we'd need consensus about such a change.

Re: Sources.list

Posted: 03 Mar 2018 11:46
by ilu
If I had to name my priorities, it would be security - stability - convenience, in that order. Is there a way to list all packages in -updates? Edit: here https://packages.debian.org/stretch-updates/allpackages

Clamav had several serious security flaws for quite some time which were actively exploited as of Jan 26. An unpatched clamav can do more damage than good. If you want to keep clamav, at least it needs security updates which are only distributed via -updates.

Either clamav has to go or that line has to come. I'd vote against clamav, but I'm ok with the other solution too.

I'd like to hear grizzler and kurotsugi on this.

Re: Sources.list

Posted: 03 Mar 2018 15:33
by grizzler
Updates should be included, I think.

As for solydxk-system modifying sources.list, I've always had my doubts about that, but I can't think of a better way to make sure people have the right items in the list... :?

Re: Sources.list

Posted: 03 Mar 2018 16:40
by Arjen Balfoort
grizzler wrote:Updates should be included, I think.
Do you think there's a risk of introducing instability with this repository?
Currently, these packages are being updated from the updates repository:

Code: Select all

clamav
clamav-base
clamav-freshclam
libclamav7
tzdata
grizzler wrote:As for solydxk-system modifying sources.list, I've always had my doubts about that, but I can't think of a better way to make sure people have the right items in the list... :?
The only alternatives are to include clamav in our own repository or to let people manually change the sources list. However, we cannot assume that everybody will know how to change the sources.list and even if the know there is no guarantee that they will change their sources.list.

Re: Sources.list

Posted: 03 Mar 2018 21:23
by ilu
I can't imagine anything problematic with tzdata. The rest is clamav. There's also a lot of bind9 and dns related stuff in that repo which might not be relevant for us?
Modifying sources.list needs to be done by you because otherwise most people wont get clamav updates.

Re: Sources.list

Posted: 04 Mar 2018 09:56
by grizzler
Schoelje wrote:
grizzler wrote:Updates should be included, I think.
Do you think there's a risk of introducing instability with this repository?
Not really. The standard sources.list according to The Debian Administrator's Handbook (section 6.1.2) includes it.

Re: Sources.list

Posted: 04 Mar 2018 11:05
by Arjen Balfoort
I've updated solydxk-system to append the stretch-updates repository if it doesn't exist in sources.list.

I've uploaded it to the testing repository:

Code: Select all

deb http://repository.solydxk.com solydxk-9 main upstream import testing
or download it here.

Re: Sources.list

Posted: 06 Mar 2018 17:57
by Arjen Balfoort
Shall I upload it to the main repository?

Re: Sources.list

Posted: 10 Mar 2018 13:33
by jsvenancio
Good afternoon.

How do I add the nVidia Backport to be able to update my nVidia card?

Re: Sources.list

Posted: 22 Mar 2019 02:26
by FuzzyJ
Sources.list
by Arjen Balfoort - 21 Sep 2013 22:29

In relation to SolydXK (KDE desktop) Release Date - 2019-03-03, is this
advice/procedure still current?

Re: Sources.list

Posted: 22 Mar 2019 17:07
by Arjen Balfoort
FuzzyJ wrote: In relation to SolydXK (KDE desktop) Release Date - 2019-03-03, is this
advice/procedure still current?
apt-transport-https was missing the trailing 's'. I've updated the OP, the rest is still valid.

Re: Sources.list

Posted: 23 Mar 2019 01:16
by FuzzyJ
apt-transport-https was missing the trailing 's'. I've updated the OP, the rest is still valid.
Thank you, I'll be guided accordingly.