Re: Sarge - Etch upgrade issue
Alexander Schmehl wrote: * Steve Langasek [EMAIL PROTECTED] [060908 01:46]: 1) sarge: 1.1) apt-get dist-upgrade - upgrading to etch [..] Yes, I can see that apt Recommends: debian-archive-keyring and Suggests: gnupg. Given that apt should be doing secure archives by default now, the Suggests: seems like the wrong relationship; I think this warrants a bug on apt, no? Shouldn't the Recommends: debian-archive-keyring be enought? AFAIK the Release Notes recommend using aptitude instead of apt-get. And aptitude respects recommends should pull in debian-archive-keyring, which depends on gnupg. The release notes for sarge recommended aptitude over apt-get due to some strange problems with apt-get alone. Will this still be the case for etch or rather the sarge - etch upgrade? Regards, Joey -- The good thing about standards is that there are so many to choose from. -- Andrew S. Tanenbaum -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge - Etch upgrade issue
On Fri, Sep 15, 2006 at 08:32:13AM +0200, Martin Schulze wrote: Alexander Schmehl wrote: * Steve Langasek [EMAIL PROTECTED] [060908 01:46]: 1) sarge: 1.1) apt-get dist-upgrade - upgrading to etch [..] Yes, I can see that apt Recommends: debian-archive-keyring and Suggests: gnupg. Given that apt should be doing secure archives by default now, the Suggests: seems like the wrong relationship; I think this warrants a bug on apt, no? Shouldn't the Recommends: debian-archive-keyring be enought? AFAIK the Release Notes recommend using aptitude instead of apt-get. And aptitude respects recommends should pull in debian-archive-keyring, which depends on gnupg. The release notes for sarge recommended aptitude over apt-get due to some strange problems with apt-get alone. Will this still be the case for etch or rather the sarge - etch upgrade? Since apt-get doesn't handle Recommends, I expect that this will be the case for etch as well. I'm not thrilled with some of the other behavior changes in aptitude's resolver post-sarge, but I'm not sure they're actually worse than some of apt-get's own idiosyncracies. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge - Etch upgrade issue
* Alexander Schmehl ([EMAIL PROTECTED]) [060909 14:37]: = The following packages are RECOMMENDED but will NOT be installed: aptitude-doc-en debian-archive-keyring libtasn1-2-bin locales mtools = Hm, basically I think we need to check the reason for any of these packages. :/ What now? I don't know how to investigate aptitudes behaviour of not installing debian-archive-keyring during dist-upgrades any further. And I dislike the let's put a paragraph into the release-notes, that people need to install debian-archive-keyring before running dist-upgrade, because there are just to much people, which won't read it. Did you try what happens if apt depends on debian-archive-keyring? Then it should work? In worst case, we need to make apt depend on that package. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge - Etch upgrade issue
Hi! * Andreas Barth [EMAIL PROTECTED] [060910 10:05]: = The following packages are RECOMMENDED but will NOT be installed: aptitude-doc-en debian-archive-keyring libtasn1-2-bin locales mtools = Hm, basically I think we need to check the reason for any of these packages. :/ Hmmm... if the problem is, what vorlon said, that aptitude doesn't install (new?) recommends of installed packages, shouldn't that then be changed? Did you try what happens if apt depends on debian-archive-keyring? Then it should work? In worst case, we need to make apt depend on that package. Yes; if apt depends on debian-archive-keyring, debian-archive-keyring (and with it gnupg) get's installed during an dist-upgrade: = The following NEW packages will be installed: debian-archive-keyring dmidecode gcc-4.1-base gnupg laptop-detect [..] = Yours sincerely, Alexander -- http://learn.to/quote/ http://www.catb.org/~esr/faqs/smart-questions.html signature.asc Description: Digital signature
Re: Sarge - Etch upgrade issue
* Steve Langasek [EMAIL PROTECTED] [060910 04:12]: [ apt-get dist-upgrade to etch doesn't install debianrchive-keyring and gnupg ] Would someone please file a serious bug against apt for this? Done. #386800. Yours sincerely, Alexander signature.asc Description: Digital signature
Re: Sarge - Etch upgrade issue
Hi! * Steve Langasek [EMAIL PROTECTED] [060908 20:36]: [ apt-get dist-upgrade to etch doesn't install debianrchive-keyring and gnupg ] Shouldn't the Recommends: debian-archive-keyring be enought? AFAIK the Release Notes recommend using aptitude instead of apt-get. And aptitude respects recommends should pull in debian-archive-keyring, which depends on gnupg. Ah, good catch. (I wonder why apt has a separate Suggests: gnupg then?) This means that users who dist-upgrade using aptitude, pulling in Recommends, should not have this problem; so the most that should be needed here is release notes documentation. Assuming someone can test that this works as expected? Uhm... seems that I was to fast. I just did a small test (created a new sarge chroot, changed sources.list, tried a dist-upgrade), and even when using aptitude neither debian-archive-keyring nor gnupg are installed. While apt and apt-utils are upgraded, I get the following note from aptitude: = The following packages are RECOMMENDED but will NOT be installed: aptitude-doc-en debian-archive-keyring libtasn1-2-bin locales mtools = Note the debian-archive-keyring. Installing aptitude von etch before dist-upgrading doesn't either; debian-archive-keyring is still not installed... damn, even if I try to install aptitude and gnupg from etch before dist-upgrading debian-archive-keyring won't be installed. (Yes, this is sarges normal aptitude with the out of the box configuration, which should respect recommends; I tried everything with --with-recommends just to be sure, too.) What now? I don't know how to investigate aptitudes behaviour of not installing debian-archive-keyring during dist-upgrades any further. And I dislike the let's put a paragraph into the release-notes, that people need to install debian-archive-keyring before running dist-upgrade, because there are just to much people, which won't read it. Yours sincerely, Alexander -- http://learn.to/quote/ http://www.catb.org/~esr/faqs/smart-questions.html signature.asc Description: Digital signature
Re: Sarge - Etch upgrade issue
* Steve Langasek ([EMAIL PROTECTED]) [060908 01:47]: Yes, I can see that apt Recommends: debian-archive-keyring and Suggests: gnupg. Given that apt should be doing secure archives by default now, the Suggests: seems like the wrong relationship; I think this warrants a bug on apt, no? Agreed. I think we should also note it in the release notes, unless we shift both dependencies to Depends. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge - Etch upgrade issue
Hi! * Steve Langasek [EMAIL PROTECTED] [060908 01:46]: 1) sarge: 1.1) apt-get dist-upgrade - upgrading to etch [..] Yes, I can see that apt Recommends: debian-archive-keyring and Suggests: gnupg. Given that apt should be doing secure archives by default now, the Suggests: seems like the wrong relationship; I think this warrants a bug on apt, no? Shouldn't the Recommends: debian-archive-keyring be enought? AFAIK the Release Notes recommend using aptitude instead of apt-get. And aptitude respects recommends should pull in debian-archive-keyring, which depends on gnupg. Yours sincerely, Alexander -- http://learn.to/quote/ http://www.catb.org/~esr/faqs/smart-questions.html signature.asc Description: Digital signature
Re: Sarge - Etch upgrade issue
On Fri, Sep 08, 2006 at 05:01:07PM +0200, Alexander Schmehl wrote: * Steve Langasek [EMAIL PROTECTED] [060908 01:46]: 1) sarge: 1.1) apt-get dist-upgrade - upgrading to etch [..] Yes, I can see that apt Recommends: debian-archive-keyring and Suggests: gnupg. Given that apt should be doing secure archives by default now, the Suggests: seems like the wrong relationship; I think this warrants a bug on apt, no? Shouldn't the Recommends: debian-archive-keyring be enought? AFAIK the Release Notes recommend using aptitude instead of apt-get. And aptitude respects recommends should pull in debian-archive-keyring, which depends on gnupg. Ah, good catch. (I wonder why apt has a separate Suggests: gnupg then?) This means that users who dist-upgrade using aptitude, pulling in Recommends, should not have this problem; so the most that should be needed here is release notes documentation. Assuming someone can test that this works as expected? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge - Etch upgrade issue
Ingo Juergensmann wrote: Joey asked me to forward this to here, so here it is: When upgrading sarge to etch, apt-get complains about untrusted source of packages because gnupg isn't installed during apt-get dist-upgrade. After manually installing gnupg apt-get update everything seems fine... It may be worth considering to add a Dependency against GnuPG to apt when apt complains if no gnupg or no keyring has been found on the users system. Alternatively, it may be worth considering to alter the default setting of apt so that it will accept packages from untrusted source - i.e. from official Debian mirrors. Maybe by adding // Comment this out to only accept packages from authorised // sources. See apt-key(8) for details. // APT::Get::AllowUnauthenticated true; to /etc/apt/apt.conf (or use a single file in apt.conf.d) Regards, Joey -- The only stupid question is the unasked one. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge - Etch upgrade issue
On Thu, Sep 07, 2006 at 10:07:32AM +0200, Ingo Juergensmann wrote: Hi! (CC: my if necessary, I'm not subscribed here) Joey asked me to forward this to here, so here it is: When upgrading sarge to etch, apt-get complains about untrusted source of packages because gnupg isn't installed during apt-get dist-upgrade. After manually installing gnupg apt-get update everything seems fine... Sorry, what's the exact process you're following when upgrading? The apt-get from sarge shouldn't complain about untrusted packages, AFAIK? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge - Etch upgrade issue
Steve Langasek wrote: On Thu, Sep 07, 2006 at 10:07:32AM +0200, Ingo Juergensmann wrote: When upgrading sarge to etch, apt-get complains about untrusted source of packages because gnupg isn't installed during apt-get dist-upgrade. After manually installing gnupg apt-get update everything seems fine... Sorry, what's the exact process you're following when upgrading? The apt-get from sarge shouldn't complain about untrusted packages, AFAIK? 1) sarge: 1.1) apt-get dist-upgrade - upgrading to etch 2) then on etch 2.1) apt-get install something I would expect that after dist-upgrading to etch everything necessary is installed - that should include gnupg. -- Ciao...// Ingo \X/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge - Etch upgrade issue
On Thu, Sep 07, 2006 at 10:07:32AM +0200, Ingo Juergensmann wrote: Hi! (CC: my if necessary, I'm not subscribed here) Joey asked me to forward this to here, so here it is: When upgrading sarge to etch, apt-get complains about untrusted source of packages because gnupg isn't installed during apt-get dist-upgrade. After manually installing gnupg apt-get update everything seems fine... Please report a bug against release-notes asking to tell users to install gnupg before upgrading. We can always remove it if a better solution is implemented. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge - Etch upgrade issue
On Thu, Sep 07, 2006 at 10:34:35PM +0200, Ingo Juergensmann wrote: Steve Langasek wrote: On Thu, Sep 07, 2006 at 10:07:32AM +0200, Ingo Juergensmann wrote: When upgrading sarge to etch, apt-get complains about untrusted source of packages because gnupg isn't installed during apt-get dist-upgrade. After manually installing gnupg apt-get update everything seems fine... Sorry, what's the exact process you're following when upgrading? The apt-get from sarge shouldn't complain about untrusted packages, AFAIK? 1) sarge: 1.1) apt-get dist-upgrade - upgrading to etch 2) then on etch 2.1) apt-get install something I would expect that after dist-upgrading to etch everything necessary is installed - that should include gnupg. Ok, that just wasn't what I had gathered from your description of the problem; it sounded to me like you were saying that the dist-upgrade itself failed. Yes, I can see that apt Recommends: debian-archive-keyring and Suggests: gnupg. Given that apt should be doing secure archives by default now, the Suggests: seems like the wrong relationship; I think this warrants a bug on apt, no? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
