after all changes with sarge getting stable

hyllplan · 06-10-2005, 08:52 AM

1) What about non-us in sources.list it does not work anymore?, someone said it should not be used anymore.
2) security patches work for sarge/stable but not for testing/etch shoud it not?

craigevil · 06-10-2005, 09:46 AM

"non-US obsoleted
For the sarge release, packages that were formerly in the non-US part of the archive have been moved into the regular archive. If you have any lines referring to "non-us" in your /etc/apt/sources.list, you should remove them." http://www.debian.org/releases/sarg...n.html#s-non-us

Quote:

Originally posted by Dead Parrot
Or you could add this page to your bookmarks and check every now and then if "testing" will appear among the available options: http://security.debian.org/dists/

I'm also curious to see how Etch/testing will be receiving security updates -- but so far there has been very little info about this available. Apparently the "testing security team" already exists and their plans are that:

"After sarge is released and once the autobuilder infrastructure is in place, we hope to begin issuing security advisories for holes in testing, and providing fixed packages immediatly on security.debian.org or a similar site." http://secure-testing.alioth.debian.org/

However, they merely say that they "hope to" start these actions after Sarge has been released, so we will have to wait to see if these hopes will actually turn into concrete actions.

hyllplan · 06-10-2005, 10:52 AM

Thanks man craigevil

farpoint · 06-10-2005, 03:30 PM

Whats going to be the situation when Sarge goes stable? I upgraded my Debian 3.0r2 Woody to testing over the net, and am getting updates from the testing repo with no problems. When sarge gets moved to stable, am I going to have to uncomment the stable repo again, or can I still stay on the testing repo? Nigel. Sailing close to the wind.

Deeze · 06-10-2005, 11:57 PM

Quote:

Originally posted by farpoint
Whats going to be the situation when Sarge goes stable? I upgraded my Debian 3.0r2 Woody to testing over the net, and am getting updates from the testing repo with no problems. When sarge gets moved to stable, am I going to have to uncomment the stable repo again, or can I still stay on the testing repo? Nigel. Sailing close to the wind.

Sarge went stable at the start of this week. If you want to stay with stable, you need to get your repos changed to point to stable instead of testing. You might already be tainted with new packages, though nothing big has gone through yet that I'm aware of (they're just in the process of moving Gnome 2.10 into unstable now).

farpoint · 06-18-2005, 04:17 PM

Hi Deeze. Sorry for the delay in replying. I've decided to stay on the testing repo, like going into the unknown Etch territory. There are some problems.
1: Ardour-gtk was held back when doing an apt-get dist-upgrade.
I did an apt-get install ardour-gtk, but it insisted on removing libardour at the same time. Ardour still fires up but I havn;t tried it.
2: There were 2 more upgrades. One was base-config, the other I can't remember (and it's very annoying that Debian doesn't keep a log of upgrades/dist upgrades). Anyway the one I cant remember installed, ok, base-config was held back. Tried an apt-get install base-config, and was told tasksel needed to be removed to install the upgrade to base-config. I didn't go ahead with that. Perhaps the upgrade to base-config is now handling the stuff that tasksel did.
I don't know if this is a good move staying on testing. I at least now have the 2.6.11 kernel now with Alsa 1.08, which I don't think was on testing when sarge was using it. Any comments would be welcome.

To conclude:
Sarge is now using the stable repo
Etch is now using the testing repo. Where has Etch come from?
Sid is using the unstable repo. Will sid always be the unstable version?

A little bit confused, but pressing onward into unknown territory (a bit like Star Trek) Nigel. aka farpoint.