Sources.list

[Arjen Balfoort]

Is there any particular reason not to use httpredir.debian.org (or http.debian.net, which is an alias for it) in the current sources.list? It seems a better choice than ftp.debian.org, which has to be set to a mirror manually.

I don't know what you're talking about So, no, there's no reason at all. Why are those repositories better to use?

[grizzler]

See the page I linked to in my previous message. With httpredir.debian.org/http.debian.net you automatically get to use the nearest mirror.

I just found out the httpredir host was a recent development (used to be http.debian.net, apparently): https://lists.debian.org/debian-devel-a ... 00003.html

[Arjen Balfoort]

I see. That is a good development.

I am testing this sources.list configuration now:

Code: Select all

deb http://repository.solydxk.com/ solydxk main upstream import
deb http://httpredir.debian.org/debian jessie main contrib non-free
deb http://httpredir.debian.org/debian jessie-backports main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free

All seems fine, but I was already pointing at the Dutch Debian mirror.

[Arjen Balfoort]

I see that the jessie backports are not done yet:

Code: Select all

Err http://httpredir.debian.org jessie-backports/main i386 Packages                            
Err http://httpredir.debian.org jessie-backports/main i386 Packages

[grizzler]

Odd. If I visit http://httpredir.debian.org/debian/dists, there's definitely a jessie-backports directory where I end up (http://mirror.proserve.nl/debian), with everything that should be in it.

Edit
An apt-get update with that sources.list picks up everything as expected. Maybe you end up at a 'broken' mirror? In that case I wonder if we should wait a while with implementing this...

[Arjen Balfoort]

We still have time and when TB38 is out we can still make a decision.

[ane champenois]

Very nice...and I notices the predir a few days ago and want to talk about that too. Frank, you're too fast for me
If it's implemented, it could be interesting to deprecate the choice of the mirror in UP manager for Debian ones I suppose.

[palimmo]

I found this
Stable Proposed Updates
https://wiki.debian.org/StableProposedUpdates
I think it would be an excellent idea to add this repository to our main edition in order to characterize more SolydXK.
What do you think?

I've added the repository (changing stable with jessie) a few minutes ago. This is the output:

Code: Select all

The following packages will be upgraded:
  libgnutls-deb0-28 libgnutls-deb0-28:i386 libgnutls-openssl27 libperl5.20 libqt4-dbus
  libqt4-dbus:i386 libqt4-declarative libqt4-designer libqt4-help libqt4-network libqt4-network:i386
  libqt4-opengl libqt4-opengl:i386 libqt4-qt3support libqt4-script libqt4-scripttools libqt4-sql
  libqt4-sql-mysql libqt4-sql-sqlite libqt4-svg libqt4-test libqt4-xml libqt4-xml:i386
  libqt4-xmlpatterns libqt4-xmlpatterns:i386 libqtcore4 libqtcore4:i386 libqtdbus4 libqtdbus4:i386
  libqtgui4 libqtgui4:i386 perl perl-base perl-modules qdbus qtcore4-l10n tzdata tzdata-java
  unattended-upgrades
39 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 33.7 MB of archives.
After this operation, 1,426 kB disk space will be freed.
Do you want to continue? [Y/n]

[Zill]

I found this
Stable Proposed Updates
https://wiki.debian.org/StableProposedUpdates
I think it would be an excellent idea to add this repository to our main edition in order to characterize more SolydXK.
What do you think?

I cannot see how "Stable-proposed-updates" significantly differs from Debian Testing...

StableProposedUpdates

Stable-proposed-updates is an apt repository that contains the files that are being prepared for the next Debian/Stable point release.

DebianStability

Understand that the job of Debian is, and always has been, to produce Stable. The other releases are means to that end.
...
Testing is just what it says it is; it's for testing whether it works reliably prior to its release as a future Stable.

I strongly recommend that this "Stable-proposed-updates" repo is not included by default in the Stable editions of SolydXK for the simple reason that these packages are not stable! With all the potential for dependency hell in mixing packages from different Debian bases, I suggest that this is only for the brave and very competent.

As such a system will be very difficult to support (due to the varying dependency requirements) I suggest that this is not something that SolydXK should recommend to the "average" user. Of course, some users do like to live on the edge and they are welcome to do so and report their system breakages back here. However, IMHO, this should only be done in the "community" section of the forum where it is kept well away from the Stable support sections.

[grizzler]

Stable proposed updates is significantly different from Debian Testing. Testing is the next stage after Sid and prepares for the next Stable release, Debian 9 in this case. Packages from Stable proposed updates will end up in Debian 8.1, 8.2 and so on. They will become part of the current Debian Stable.

[palimmo]

Stable proposed updates is significantly different from Debian Testing. Testing is the next stage after Sid and prepares for the next Stable release, Debian 9 in this case. Packages from Stable proposed updates will end up in Debian 8.1, 8.2 and so on. They will become part of the current Debian Stable.

That's the reason I think we could have a nice pseudo rolling stable debian based released , instead of waiting till the point realease, without giving away stability.

[Zill]

... Packages from Stable proposed updates will end up in Debian 8.1, 8.2 and so on. They will become part of the current Debian Stable.

Which is why, IMHO, there is no need for a separate repo as packages will eventually end up in the current Stable if they are good enough. If they don't make the grade then surely they should not be provided in our new Stable SolydXK.

[Arjen Balfoort]

I cannot speak for the community editions, but I do agree with Zill and cannot find valid arguments to risk increased instability for the sake of being a tad more up-to-date.

[Zill]

I would also add that, IMHO, there would be no real advantage for current Debian Stable users to have this repo as no new functionality will be introduced. Debian point releases exist simply to ensure that the latest ISO incorporates the latest security fixes, reducing the additional package downloading needed following the installation of a new system.

https://wiki.debian.org/DebianReleases/PointReleases

[falke]

Hi,

first, sorry for my (maybe bad english) BUT I must say I'm a little bit confused with this topic posted in the News and Announcement section, because first I thought I had to change my sourcelist and discovering then that it was just a discussion about the opportunity to do it. And the decision was so far not taken to do so.

At this point, i think it would be nice to post in the right section in particulary for non english spoken trying to search and understand difficult themes through the forum.

Real anouncements should instead be pined and uneditable.

Thx for your understanding.

[Zill]

falke: You are quite right in that this topic can be confusing as it contains many discussions about possible content for the sources.list. However, the first post in this thread is usually updated to show the current recommended sources.list and so your SolydXK systems should currently be based on this post. If the recommended sources.list changes again then my understanding is that this first post will be edited to show the required changes.

I agree that posting the sources.list at the start of a forum thread is not the most intuitive place for it to be. As such, I do agree with your comment that "Real anouncements should instead be pined and uneditable."

[josk]

I have pure Debian testing (Stretch). What SolydXK repositories I should add to the sources.list?

[MAYBL8]

The sources.list in the OP is for Solydxk (Stable) or Debian Stable (Jessie).
We need a sources.list in the OP for our Debian Testing thread is what i would say. This also might be referred to now as the EE edition I think.
Correct me if I am wrong.
Thanks
Dan

[Zill]

We need a sources.list in the OP for our Debian Testing thread is what i would say.

As the EE is aimed at enthusiasts who know how to fix Debian Testing when it breaks, I would think such users should already know how to tweak the SolydXK sources.list to run testing. If they don't then, IMHO, they really should not be running the EE!

[MAYBL8]

Zill,
I don't want to get into a debate about this. I might agree with that point that someone that wants to use debian testing should already know how to change their sources.list there are those that are new to testing that want to learn about it and use it.
Should we help those users here or just send them out there to learn for themselves?
Remember ZeroZero. I know he was very helpful to me when I wanted to get started off the Stable path. Just saying.
Thanks
Dan