Upgrade to Gutsy failed ( possibly due to apt-listbugs )

Bug #154757 reported by Jordan
16
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Medium
Michael Vogt

Bug Description

Binary package hint: update-manager

[apport] package update-manager failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process if dpkg -s apt-listbugs | grep -q '^Status: .* ok installed'; then /usr/sbin/apt-listbugs apt || ( test $? -ne 10 || exit 10; echo 'Warning: apt-listbugs exited abnormally, hit enter key to continue.' 1>&2 ; read a < /dev/tty ); fi returned an error code (10), E:Failure running script if dpkg -s apt-listbugs | grep -q '^Status: .* ok installed'; then /usr/sbin/apt-listbugs apt || ( test $? -ne 10 || exit 10; echo 'Warning: apt-listbugs exited abnormally, hit enter key to continue.' 1>&2 ; read a < /dev/tty ); fi

The above was set as the summery for my bug report automatically, I should probably file another bug report on that alone, and I assume that the all of "debug information" is not attached.

I tried upgrading to Gutsy from feisty using update-manager and had to say "no" to apt-listbugs because it refused to let me continue if I chose yes. That caused the upgrade to fail and while no packages had been installed ( apt-listbugs stops things before that happens ) my sources.lst still pointed to Gutsy ( the change was not undone ). I then restored my sources.list so it was pointing back at Feisty, removed apt-listbugs and tried to upgrade again. This time I received an error that update-manager "Could not calculate the upgrade" so I am also, as I was directed, going to attach the contents of /var/log/dist-upgrade/ . I hope this is somewhat coherent since It is late, I would be glad to clarify anything if it is not.

ProblemType: Package
Date: Fri Oct 19 23:09:59 2007
ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process if dpkg -s apt-listbugs | grep -q '^Status: .* ok installed'; then /usr/sbin/apt-listbugs apt || ( test $? -ne 10 || exit 10; echo 'Warning: apt-listbugs exited abnormally, hit enter key to continue.' 1>&2 ; read a < /dev/tty ); fi returned an error code (10), E:Failure running script if dpkg -s apt-listbugs | grep -q '^Status: .* ok installed'; then /usr/sbin/apt-listbugs apt || ( test $? -ne 10 || exit 10; echo 'Warning: apt-listbugs exited abnormally, hit enter key to continue.' 1>&2 ; read a < /dev/tty ); fi

Package: update-manager
SourcePackage: update-manager

Revision history for this message
Jordan (jordanu) wrote :
Revision history for this message
Jordan (jordanu) wrote :
Revision history for this message
Jordan (jordanu) wrote :
Revision history for this message
Jordan (jordanu) wrote :

term.log is empty

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Could you please remove the "hpijs" package and try again without it? Can the upgrade be calculated then?

Thanks,
 Michael

Changed in update-manager:
assignee: nobody → mvo
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Jordan (jordanu) wrote : Re: [Bug 154757] Re: Upgrade to Gutsy failed ( possibly due to apt-listbugs )

I have actually already upgraded ( using apt-get dist-upgrade and doing A
LOT of fixing ) but I had to download many packages manually from
packages.ubuntu.com and install them with dpkg -i because they "were being
held back", they are still being held back but they are all currently at the
newest version. Sorry if I have made it harder to debug this problem, should
I still remove hpijs and see if those packages are still held back? Here is
the output of apt-get upgrade:

" sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
  apt aptitude brltty dpkg evince evolution-exchange gdebi gnome-applets
gnome-screensaver gnome-system-monitor gnome-utils gthumb
libssl0.9.8mono-jit nautilus-sendto
openoffice.org-writer perl perl-base
  python python-software-properties python-support rss-glx ruby1.8serpentine
0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded.
"

And as an example, here is the output of apt-cache policy dpkg:

" apt-cache policy dpkg
dpkg:
  Installed: 1.14.5ubuntu16
  Candidate: (none)
  Package pin: (not found)
  Version table:
 *** 1.14.5ubuntu16 1000
        500 http://us.archive.ubuntu.com gutsy/main Packages
        100 /var/lib/dpkg/status
"

On 10/24/07, Michael Vogt <email address hidden> wrote:
>
> Thanks for your bugreport.
>
> Could you please remove the "hpijs" package and try again without it?
> Can the upgrade be calculated then?
>
> Thanks,
> Michael
>
> ** Changed in: update-manager (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Michael Vogt (mvo)
> Status: New => Incomplete
>
> --
> Upgrade to Gutsy failed ( possibly due to apt-listbugs )
> https://bugs.launchpad.net/bugs/154757
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Jordan (jordanu) wrote :

I would like to re-install and the only thing keeping me from doing so now is the possibility that I could help fix this bug, so if upgrading has made it so that I can't provide any usefull information please tell me so that I can re-install.

Revision history for this message
xandrio (xandrio) wrote :

i also have a similar problem upgrading feisty -> gutsy and i guess theres hpijs || cupsys involved. i tried removing both of them but that concludes in also removing ubuntu-desktop so im going in circles. Attaching log files next

Revision history for this message
xandrio (xandrio) wrote :
Revision history for this message
xandrio (xandrio) wrote :
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

xandrio, is it a cdrom upgrade ?

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in update-manager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.