Bug#506498: dpkg fails with parse error in /var/lib/dpkg/status
On Sun, 23 Nov 2008, Raj Kiran Grandhi wrote: Again, I am sorry for the version confusion. Please see my other reply. I never really used 1.14.22 on my system. The 1.14.22 in the status file and the logs was actually 1.14.21 which apparently did not complain about the triggers. Are you sure it's really 1.14.21 and not 1.14.19 (the one that was previously installed) or even an older version ? 1.14.21 is the first version that should remove the Trigger-Awaited lines by itself if there's no corresponding Triggers-Pending entry in the package providing the trigger. But all versions of dpkg (that are trigger-aware at least, ie 1.14.17) would fail with a status file like you had (i.e. packages marked as installed but containing Triggers-Awaited lines). Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506498: dpkg fails with parse error in /var/lib/dpkg/status
Raphael Hertzog wrote: On Sun, 23 Nov 2008, Raj Kiran Grandhi wrote: Again, I am sorry for the version confusion. Please see my other reply. I never really used 1.14.22 on my system. The 1.14.22 in the status file and the logs was actually 1.14.21 which apparently did not complain about the triggers. Are you sure it's really 1.14.21 and not 1.14.19 (the one that was previously installed) or even an older version ? I guess it could be 1.14.19, I am not very sure. It is definitely not 1.14.22 and very unlikely that it is older than 1.14.19. I had been postponing a dist-upgrade for several months and apt is configured to just download updates without installing. I had picked the previous version lying in the archive cache and used it. 1.14.21 is the first version that should remove the Trigger-Awaited lines by itself if there's no corresponding Triggers-Pending entry in the package providing the trigger. But all versions of dpkg (that are trigger-aware at least, ie 1.14.17) would fail with a status file like you had (i.e. packages marked as installed but containing Triggers-Awaited lines). Cheers, -- If you can't explain it simply, you don't understand it well enough. -- Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506498: dpkg fails with parse error in /var/lib/dpkg/status
severity 506498 normal retitle 506498 dpkg: fails with package has status installed but triggers are awaited tag 506498 unreproducible thanks On Sun, 23 Nov 2008, Raj Kiran Grandhi wrote: I guess it could be 1.14.19, I am not very sure. It is definitely not 1.14.22 and very unlikely that it is older than 1.14.19. Well, since I can't identify clearly how this happened I'll set the severity back to important/normal and mark it as unreproducible. Maybe someone else will experience it too. If not, we'll close the bug later. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506498: dpkg fails with parse error in /var/lib/dpkg/status
severity 506498 serious thanks On Sat, 22 Nov 2008, Raj Kiran Grandhi wrote: Package: dpkg Version: 1.14.23 Severity: normal dpkg fails complaining about the following parse error in the `status' file. Please send us a copy of the status file and of any file in /var/lib/dpkg/updates/. Log started: 2008-11-21 18:34:54 (Reading database ... 283360 files and directories currently installed.) Preparing to replace dpkg 1.14.22 (using .../archives/dpkg_1.14.23_i386.deb) ... Unpacking replacement dpkg ... Log ended: 2008-11-21 18:35:26 Log started: 2008-11-21 18:36:06 dpkg: parse error, in file `/var/lib/dpkg/status' near line 2881 package `python -4suite-xml': package has status installed but triggers are awaited Log ended: 2008-11-21 18:36:07 Was there nothing else before this that could explain how the package python-4suite-xml got into this inconsistent state ? Please show us /var/log/dpkg.log. Following the error, dpkg is unusable with every invocation resulting in the above error. I'll tell you more how to get out of this when you have sent us the relevant files. Most probably removing the Triggers-Awaited line concerning python-4suite-xml in the status file should be enough. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506498: dpkg fails with parse error in /var/lib/dpkg/status
On Sat, 22 Nov 2008, Raj Kiran Grandhi wrote: Just did that but still dpkg complains of the same problem albeit for a different package (libhtml-format-perl this time), so I do not think it is a problem with one specific mis-behaving package. Will it be too invasive if I remove all the 34 Triggers-Awaited lines? No, it's fine. What files should I backup before doing this? None. The weird thing is that it looks like that only dpkg 1.14.23 causes you trouble and not 1.14.22. But the code that deals with lonely Triggers-Awaited dates back to Mon Aug 11 (commit 587b8d8696cb92a4a18901085db033d44bfe6f32) and dpkg 1.14.21. I don't see what changes could explain that the error now gets noticed when it wasn't before. And the package that had those fields were not recently updated either. I can certainly get a failure with 1.14.22 if I add Triggers-Awaited fields to packages that are marked as installed. So how is it possible that you were using dpkg 1.14.22 without troubles yesterday and that now you have a borked status file exactly when you upgrade to 1.14.23… Did you do anything special recently that could have an impact on the status of all those packages ? Can you check if you already had all those Triggers-Awaited tags in the previous days ? Check in the backups: /var/backups/dpkg.status.* Maybe send us the one that corresponds to Nov 20th. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506498: dpkg fails with parse error in /var/lib/dpkg/status
On 2008-11-22 18:22 +0100, Raphael Hertzog wrote: The weird thing is that it looks like that only dpkg 1.14.23 causes you trouble and not 1.14.22. But the code that deals with lonely Triggers-Awaited dates back to Mon Aug 11 (commit 587b8d8696cb92a4a18901085db033d44bfe6f32) and dpkg 1.14.21. I don't see what changes could explain that the error now gets noticed when it wasn't before. And the package that had those fields were not recently updated either. I can certainly get a failure with 1.14.22 if I add Triggers-Awaited fields to packages that are marked as installed. So how is it possible that you were using dpkg 1.14.22 without troubles yesterday and that now you have a borked status file exactly when you upgrade to 1.14.23… There is another strange thing in Raj's dpkg log: packages never entered a state of triggers-awaited or triggers-pending. Compare that with my system: , | % egrep -c 'triggers-(pending)|(awaited)' /var/log/dpkg.log | 182 ` And note that he had been running dpkg 1.14.19 in the first ten days of this month before he upgraded to 1.14.22. Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506498: dpkg fails with parse error in /var/lib/dpkg/status
On Sat, 22 Nov 2008, Sven Joachim wrote: On 2008-11-22 18:22 +0100, Raphael Hertzog wrote: The weird thing is that it looks like that only dpkg 1.14.23 causes you trouble and not 1.14.22. But the code that deals with lonely Triggers-Awaited dates back to Mon Aug 11 (commit 587b8d8696cb92a4a18901085db033d44bfe6f32) and dpkg 1.14.21. I don't see what changes could explain that the error now gets noticed when it wasn't before. And the package that had those fields were not recently updated either. I can certainly get a failure with 1.14.22 if I add Triggers-Awaited fields to packages that are marked as installed. So how is it possible that you were using dpkg 1.14.22 without troubles yesterday and that now you have a borked status file exactly when you upgrade to 1.14.23… There is another strange thing in Raj's dpkg log: packages never entered a state of triggers-awaited or triggers-pending. Right, Raj, did you configure apt in any strange way? Did you activate the DPkg::NoTriggers option for example? Please check /etc/apt/apt.conf and /etc/apt/apt.conf.d/*. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506498: dpkg fails with parse error in /var/lib/dpkg/status
Raphael Hertzog wrote: On Sat, 22 Nov 2008, Raj Kiran Grandhi wrote: Just did that but still dpkg complains of the same problem albeit for a different package (libhtml-format-perl this time), so I do not think it is a problem with one specific mis-behaving package. Will it be too invasive if I remove all the 34 Triggers-Awaited lines? No, it's fine. What files should I backup before doing this? None. Done. Removed all the Triggers-Awaited lines and now dpkg is happy :) Thank you. The weird thing is that it looks like that only dpkg 1.14.23 causes you trouble and not 1.14.22. But the code that deals with lonely Triggers-Awaited dates back to Mon Aug 11 (commit 587b8d8696cb92a4a18901085db033d44bfe6f32) and dpkg 1.14.21. I don't see what changes could explain that the error now gets noticed when it wasn't before. And the package that had those fields were not recently updated either. I can certainly get a failure with 1.14.22 if I add Triggers-Awaited fields to packages that are marked as installed. So how is it possible that you were using dpkg 1.14.22 without troubles yesterday and that now you have a borked status file exactly when you upgrade to 1.14.23… I think I faced this problem even with 1.14.22. I had attempted a dist-upgrade several days back. dpkg was one of the packages marked for upgrade and it crashed after being unpackd (I think). I did not pay much attention to the specific error message then. I had the older dpkg-1.14.22 deb lying around in /var/cache/apt/archives and I manually unpacked it into a temporary directory can copied over the dpkg executable to /usr/bin. So, the actual executable I had been using earlier was 1.14.21. Sorry for the confusion. Did you do anything special recently that could have an impact on the status of all those packages ? Can you check if you already had all those Triggers-Awaited tags in the previous days ? Check in the backups: /var/backups/dpkg.status.* Yes, all the backups have Triggers-Awaited tags. But, as I mentioned earlier, dpkg 1.14.21 was apparently ok with that. Maybe send us the one that corresponds to Nov 20th. Cheers, -- If you can't explain it simply, you don't understand it well enough. -- Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506498: dpkg fails with parse error in /var/lib/dpkg/status
Sven Joachim wrote: On 2008-11-22 18:22 +0100, Raphael Hertzog wrote: The weird thing is that it looks like that only dpkg 1.14.23 causes you trouble and not 1.14.22. But the code that deals with lonely Triggers-Awaited dates back to Mon Aug 11 (commit 587b8d8696cb92a4a18901085db033d44bfe6f32) and dpkg 1.14.21. I don't see what changes could explain that the error now gets noticed when it wasn't before. And the package that had those fields were not recently updated either. I can certainly get a failure with 1.14.22 if I add Triggers-Awaited fields to packages that are marked as installed. So how is it possible that you were using dpkg 1.14.22 without troubles yesterday and that now you have a borked status file exactly when you upgrade to 1.14.23… There is another strange thing in Raj's dpkg log: packages never entered a state of triggers-awaited or triggers-pending. Compare that with my system: , | % egrep -c 'triggers-(pending)|(awaited)' /var/log/dpkg.log | 182 ` And note that he had been running dpkg 1.14.19 in the first ten days of this month before he upgraded to 1.14.22. Again, I am sorry for the version confusion. Please see my other reply. I never really used 1.14.22 on my system. The 1.14.22 in the status file and the logs was actually 1.14.21 which apparently did not complain about the triggers. For now, I have removed all the Triggers-Awaited lines and the problem appears to have gone. I shall be happy to provide any other info that may be required. Thank you, Raj Kiran Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#506498: dpkg fails with parse error in /var/lib/dpkg/status
Package: dpkg Version: 1.14.23 Severity: normal dpkg fails complaining about the following parse error in the `status' file. # apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 27 not upgraded. 1 not fully installed or removed. After this operation, 0B of additional disk space will be used. dpkg: parse error, in file `/var/lib/dpkg/status' near line 2881 package `python-4suite-xml': package has status installed but triggers are awaited E: Sub-process /usr/bin/dpkg returned an error code (2) # The relevant portion of apt's term.log: Log started: 2008-11-21 18:34:54 (Reading database ... 283360 files and directories currently installed.) Preparing to replace dpkg 1.14.22 (using .../archives/dpkg_1.14.23_i386.deb) ... Unpacking replacement dpkg ... Log ended: 2008-11-21 18:35:26 Log started: 2008-11-21 18:36:06 dpkg: parse error, in file `/var/lib/dpkg/status' near line 2881 package `python -4suite-xml': package has status installed but triggers are awaited Log ended: 2008-11-21 18:36:07 Following the error, dpkg is unusable with every invocation resulting in the above error. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
