Re: Triggers Pending
On 2008-04-27 01:34 +0200, Kurt Roeckx wrote: On Sat, Apr 26, 2008 at 03:06:04PM -0700, Mike Bird wrote: With today's 1.14.18 dpkg update in Testing, my initramfs-tools status has changed from ii to it, meaning that I want the package installed and triggers are pending. FWIW, the system attained this state without dpkg ever being invoked with an explicit trigger-related command-line option. initramfs-tools was updated about six days before the latest dpkg and the ii only changed to it when dpkg was updated. I'm seeing the same thing. This is because initramfs-tools already uses triggers, see #447611¹. I'm not convinced that it is a very good idea to do this in Lenny packages, since the Etch versions of apt and aptitude lack support for the new trigger states. While dpkg 1.14.18 conflicts with these versions, a dist-upgrade from Etch to Lenny will still be done by the old versions. Sven ¹ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447611 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Triggers Pending
On Sun, Apr 27, 2008 at 09:40:19AM +0200, Sven Joachim wrote: On 2008-04-27 01:34 +0200, Kurt Roeckx wrote: On Sat, Apr 26, 2008 at 03:06:04PM -0700, Mike Bird wrote: With today's 1.14.18 dpkg update in Testing, my initramfs-tools status has changed from ii to it, meaning that I want the package installed and triggers are pending. FWIW, the system attained this state without dpkg ever being invoked with an explicit trigger-related command-line option. initramfs-tools was updated about six days before the latest dpkg and the ii only changed to it when dpkg was updated. I'm seeing the same thing. This is because initramfs-tools already uses triggers, see #447611¹. I'm not convinced that it is a very good idea to do this in Lenny packages, since the Etch versions of apt and aptitude lack support for the new trigger states. While dpkg 1.14.18 conflicts with these versions, a dist-upgrade from Etch to Lenny will still be done by the old versions. I remember from previous release notes that one step before upgrading the entire system was to upgrade aptitude. Probably similar shall be done now. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Triggers Pending
Sven Joachim wrote: This is because initramfs-tools already uses triggers, see #447611¹. I'm not convinced that it is a very good idea to do this in Lenny packages, since the Etch versions of apt and aptitude lack support for the new trigger states. While dpkg 1.14.18 conflicts with these versions, a dist-upgrade from Etch to Lenny will still be done by the old versions. When an old version of dpkg is installed, the code in initramfs-tools will behave exactly as it did before trigger support was added. -- see shy jo signature.asc Description: Digital signature
Re: Triggers Pending
On Sat April 26 2008 19:15:45 Patrick Wiseman wrote: On Sat, Apr 26, 2008 at 7:34 PM, Kurt Roeckx [EMAIL PROTECTED] wrote: On Sat, Apr 26, 2008 at 03:06:04PM -0700, Mike Bird wrote: With today's 1.14.18 dpkg update in Testing, my initramfs-tools status has changed from ii to it, meaning that I want the package installed and triggers are pending. FWIW, the system attained this state without dpkg ever being invoked with an explicit trigger-related command-line option. initramfs-tools was updated about six days before the latest dpkg and the ii only changed to it when dpkg was updated. I'm seeing the same thing. I was seeing the same thing until I installed something else and the initramfs issue was dealt with at the same time. I just updated mtr-tiny using dpkg 1.14.18 but initramfs-tools is still in it state: Package: initramfs-tools Status: install ok triggers-pending Priority: optional Section: utils Installed-Size: 396 Maintainer: Debian kernel team [EMAIL PROTECTED] Architecture: all Version: 0.92 snip --Mike Bird -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Triggers Pending
On 2008-04-27 18:30 +0200, Joey Hess wrote: Sven Joachim wrote: This is because initramfs-tools already uses triggers, see #447611¹. I'm not convinced that it is a very good idea to do this in Lenny packages, since the Etch versions of apt and aptitude lack support for the new trigger states. While dpkg 1.14.18 conflicts with these versions, a dist-upgrade from Etch to Lenny will still be done by the old versions. When an old version of dpkg is installed, the code in initramfs-tools will behave exactly as it did before trigger support was added. I understand that. What I'm concerned about is that aptitude (or apt-get) will upgrade itself, dpkg and initramfs-tools - and then get confused about the unknown package states. I have no idea how severe this would be, but the conflicts were probably added with a reason. But probably it is as Andrei said and the release notes will tell to upgrade aptitude first. Though 70% (?) of the users don't read the release notes and then come and scream in the debian-user* lists. Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Triggers Pending
With today's 1.14.18 dpkg update in Testing, my initramfs-tools status has changed from ii to it, meaning that I want the package installed and triggers are pending. FWIW, the system attained this state without dpkg ever being invoked with an explicit trigger-related command-line option. initramfs-tools was updated about six days before the latest dpkg and the ii only changed to it when dpkg was updated. According to man dpkg, triggers-pending means The package has been triggered, which sounds to me like the exact opposite of triggers pending. Do I need to run dpkg --configure --pending, and if so how often? --Mike Bird Please respect reply-to debian-user as I'm not subscribed to debian-dpkg. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Triggers Pending
On Sat, Apr 26, 2008 at 03:06:04PM -0700, Mike Bird wrote: With today's 1.14.18 dpkg update in Testing, my initramfs-tools status has changed from ii to it, meaning that I want the package installed and triggers are pending. FWIW, the system attained this state without dpkg ever being invoked with an explicit trigger-related command-line option. initramfs-tools was updated about six days before the latest dpkg and the ii only changed to it when dpkg was updated. I'm seeing the same thing. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Triggers Pending
On Sat, Apr 26, 2008 at 7:34 PM, Kurt Roeckx [EMAIL PROTECTED] wrote: On Sat, Apr 26, 2008 at 03:06:04PM -0700, Mike Bird wrote: With today's 1.14.18 dpkg update in Testing, my initramfs-tools status has changed from ii to it, meaning that I want the package installed and triggers are pending. FWIW, the system attained this state without dpkg ever being invoked with an explicit trigger-related command-line option. initramfs-tools was updated about six days before the latest dpkg and the ii only changed to it when dpkg was updated. I'm seeing the same thing. I was seeing the same thing until I installed something else and the initramfs issue was dealt with at the same time. Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
