Re: expected stable-updates but got squeeze-updates
On Thu, 31, Mar, 2011 at 08:25:38AM +, Philipp Kern spoke thus..
On 2011-03-30, Adam D. Barratt a...@adam-barratt.org.uk wrote:
However, having squeeze in sources.list whilst the Release file
contains stable works okay, so I assume apt is managing the
translation internally in that case.
Nah, that's the bug we received and then assigned to ftp-master, which didn't
fix it yet:
pkern@franck:~/ftp/ftp/dists$ egrep -i '(codename|suite)'
squeeze{,-updates}/Release
squeeze/Release:Suite: stable
squeeze/Release:Codename: squeeze
squeeze-updates/Release:Suite: squeeze-updates
squeeze-updates/Release:Codename: squeeze-updates
I've put a temporary hack in place in generate-releases to fix this for
now until we change dak/projectb to use the codenames instead of suite
names for the main suites. Should be live as of the next dinstall.
I'm keeping the bug open for now until it's fixed properly.
Mark
--
Mark Hymers mhy at debian dot org
I told you I was ill
The epitaph of Spike Milligan (1918-2002)
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2011040200.ga14...@hymers.org.uk
Re: expected stable-updates but got squeeze-updates
On 2011-03-30, Adam D. Barratt a...@adam-barratt.org.uk wrote:
However, having squeeze in sources.list whilst the Release file
contains stable works okay, so I assume apt is managing the
translation internally in that case.
Nah, that's the bug we received and then assigned to ftp-master, which didn't
fix it yet:
pkern@franck:~/ftp/ftp/dists$ egrep -i '(codename|suite)'
squeeze{,-updates}/Release
squeeze/Release:Suite: stable
squeeze/Release:Codename: squeeze
squeeze-updates/Release:Suite: squeeze-updates
squeeze-updates/Release:Codename: squeeze-updates
Kind regards
Philipp Kern
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnip8ek2.avb.tr...@kelgar.0x539.de
Re: expected stable-updates but got squeeze-updates
On Thu, Mar 31, 2011 at 00:24, Adam D. Barratt a...@adam-barratt.org.uk wrote: However, having squeeze in sources.list whilst the Release file contains stable works okay, so I assume apt is managing the translation internally in that case. Clarification: Thankfully it doesn't -- it would be another place to keep up to date with respect to codenames of releases… (we have it for the manpages, but these are at least not mission-critical) Its simpler: The Release files tell us which Codename and Suite this archive is for - if thats different from the one you mentioned in sources.list you will get this lovely warning… And yes, Christoph is right, something is wrong with stable-updates as if we look at the current Release file of it [0] we can see that it says […] Suite: squeeze-updates Codename: squeeze-updates […] change Suite to 'stable-updates' and it will work again for everyone who has 'stable-updates' written in his sources.list. User with sources.list entries mentioning 'squeeze-updates' doesn't have a problem with it obviously… The normal stable gets it right with 'stable' and 'squeeze'. The mentioned debian-security btw, too, through you might notice that it says 'stable' and 'squeeze' instead of 'stable/security' and alike, but thats intended - otherwise APT would warn again… (which kind of make sense, as security is already stable, while updates want to become part of stable with the next point release -- at least as far as i have understood it) Best regards David Kalnischkies [0] http://ftp.debian.org/debian/dists/stable-updates/Release -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktin+6+tqueubc1g724zyjubndc42aicgntsku...@mail.gmail.com
Re: expected stable-updates but got squeeze-updates
On Thu, March 31, 2011 09:18, David Kalnischkies wrote: Its simpler: The Release files tell us which Codename and Suite this archive is for - if thats different from the one you mentioned in sources.list you will get this lovely warning And yes, Christoph is right, something is wrong with stable-updates as if we look at the current Release file of it [0] we can see that it says [ ] Suite: squeeze-updates Codename: squeeze-updates [ ] change Suite to 'stable-updates' and it will work again for everyone who has 'stable-updates' written in his sources.list. Actually, I suspect codename should be changed in this case - the suite is called squeeze-updates in projectb, so that's correct. I'm also not sure quite what's going to happen here once the rest of the archive moves to becoming codename-based internally, which is on ftp-master's to-do list. User with sources.list entries mentioning 'squeeze-updates' doesn't have a problem with it obviously The normal stable gets it right with 'stable' and 'squeeze'. Yep, I'd forgotten about the disparity there, and the fact that a bug already exists - #614310. Regards, Adam -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/fa12efec373be599ef1c0c6f54fbd221.squir...@adsl.funky-badger.org
Re: expected stable-updates but got squeeze-updates
On Wed, 30 Mar 2011 23:24:09 +0100, Adam D. Barratt a...@adam-barratt.org.uk wrote: Because security.debian.org is not debian-mirror.lrz.de. The entries above are for security.debian.org, whereas the error message you quoted was for an entry containing debian-mirror.lrz.de; the entries for security are not what's causing your error message. Oh,.. now I've seen your problem ;)... Actually the sources.list is correct, I just copied the wrong lines here. security comes from s.d.o, and the normal archive from lrz.de,... and there I get the errors from. So the problematic lines are actually these: deb ftp://debian.mirror.lrz.de/debian/ stable-updates main contrib non-free deb-src ftp://debian.mirror.lrz.de/debian/ stable-updates main contrib non-free Sorry for the confusion. It's also not universally agreed to be a good idea, as once a new stable release occurs, your next apt-get update will suddenly pull in an entirely new release's package lists, which isn't generally what you want. Well yes,... but that should be something the administrator can decide. Cheers, Chris. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5594df2d57327184da800ee6594d8...@imap.dd24.net
expected stable-updates but got squeeze-updates
Hi. Using the following in sources.list: deb ftp://security.debian.org/debian-security/ stable/updates main contrib non-free deb-src ftp://security.debian.org/debian-security/ stable/updates main contrib non-free I always get warnings like these: W: Conflicting distribution: ftp://debian.mirror.lrz.de stable-updates Release (expected stable-updates but got squeeze-updates) when updating. Is this a false warning of apt[itude] or a problem on the ftp-servers? Cheers, Chris. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/a1f8761144647ef82f4c50dbc2bd7...@imap.dd24.net
Re: expected stable-updates but got squeeze-updates
On Wed, 2011-03-30 at 20:45 +, Christoph Anton Mitterer wrote: Using the following in sources.list: deb ftp://security.debian.org/debian-security/ stable/updates main contrib non-free deb-src ftp://security.debian.org/debian-security/ stable/updates main contrib non-free The above is not related to the warning below. Compare the server names and suite names between the two. I always get warnings like these: W: Conflicting distribution: ftp://debian.mirror.lrz.de stable-updates Release (expected stable-updates but got squeeze-updates) when updating. Is this a false warning of apt[itude] or a problem on the ftp-servers? It's not really either of those, but rather due to your sources.list containing an entry for debian-mirror.lrz.de for the stable-updates suite. However, the suite is actually called squeeze-updates, and that's therefore what appears in the Release file. Changing sources.list to point at squeeze-updates instead should make the warning go away. Regards, Adam -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1301521131.12508.4061.ca...@hathi.jungle.funky-badger.org
Re: expected stable-updates but got squeeze-updates
On Wed, 2011-03-30 at 22:38 +0100, Adam D. Barratt wrote: On Wed, 2011-03-30 at 20:45 +, Christoph Anton Mitterer wrote: Using the following in sources.list: deb ftp://security.debian.org/debian-security/ stable/updates main contrib non-free deb-src ftp://security.debian.org/debian-security/ stable/updates main contrib non-free The above is not related to the warning below. Compare the server names and suite names between the two. Why not? It's the place where I set the suite name?! It's not really either of those, but rather due to your sources.list containing an entry for debian-mirror.lrz.de for the stable-updates suite. However, the suite is actually called squeeze-updates, and that's therefore what appears in the Release file. Changing sources.list to point at squeeze-updates instead should make the warning go away. But then, why do we have those symlinks at all? And it's quite handy IMHO that one can just use stable and get the current stable suite. The same should work for the volatile replacement. Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Re: expected stable-updates but got squeeze-updates
On Thu, 2011-03-31 at 00:10 +0200, Christoph Anton Mitterer wrote: On Wed, 2011-03-30 at 22:38 +0100, Adam D. Barratt wrote: On Wed, 2011-03-30 at 20:45 +, Christoph Anton Mitterer wrote: Using the following in sources.list: deb ftp://security.debian.org/debian-security/ stable/updates main contrib non-free deb-src ftp://security.debian.org/debian-security/ stable/updates main contrib non-free The above is not related to the warning below. Compare the server names and suite names between the two. Why not? It's the place where I set the suite name?! Because security.debian.org is not debian-mirror.lrz.de. The entries above are for security.debian.org, whereas the error message you quoted was for an entry containing debian-mirror.lrz.de; the entries for security are not what's causing your error message. It's not really either of those, but rather due to your sources.list containing an entry for debian-mirror.lrz.de for the stable-updates suite. However, the suite is actually called squeeze-updates, and that's therefore what appears in the Release file. Changing sources.list to point at squeeze-updates instead should make the warning go away. But then, why do we have those symlinks at all? And it's quite handy IMHO that one can just use stable and get the current stable suite. It's also not universally agreed to be a good idea, as once a new stable release occurs, your next apt-get update will suddenly pull in an entirely new release's package lists, which isn't generally what you want. However, having squeeze in sources.list whilst the Release file contains stable works okay, so I assume apt is managing the translation internally in that case. If it doesn't do so when the Release file contains a codename then this is likely to become a more general problem in future, given that ftp-master would like to move the archive to being codename-based internally. Regards, Adam -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1301523849.12508.4212.ca...@hathi.jungle.funky-badger.org
