Comment 2 for bug 335977

Revision history for this message
ardentmoth (ardent-moth) wrote : Re: [Bug 335977] Re: upgraded from Jaunty alpha 4 to 5; synaptic now broken.

I'll check it out; since i've got your ear, you might know the answer to a
quick question: is it possible to update from Hardy UNR to Jaunty w/ UNR, or
do i need to just reinstall ubuntu on my netbook with the latest Jaunty?

--C

On Wed, Apr 29, 2009 at 2:36 PM, Charlie Kravetz <email address hidden>wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. The issue that you reported is one that should be
> reproducible with the final release of Jaunty Jackalope 9.04. We were
> wondering is this still an issue for you? Can you try with latest Ubuntu
> release? Thanks again and we appreciate your help.
>
> --
> upgraded from Jaunty alpha 4 to 5; synaptic now broken.
> https://bugs.launchpad.net/bugs/335977
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “synaptic” source package in Ubuntu: New
>
> Bug description:
> 1) rocksndiamonds failed installation on Jaunty Alpha 4.
> 2) during the partial distribution upgrade to Jaunty alpha 5, synaptic
> broke.
> 3) i removed rocksndiamonds from my installation Queue, since it had tried
> to update multiple times; then i opened update manager to grab the other
> updates i needed.
> 4) an error message (two or three actually) told me that synaptic was in
> pain, that i needed to repair some file dependencies. Also, the
> ubuntu-desktop was removed. after running the apt-get install -f, then
> apt-get autoremove to eliminate what i was told were unnecesary packages
> planned for removal, i opened synaptic to try to get my updates better.
> 5) terminal gave me the following:
>
> /usr/bin/lsb_release:81: DeprecationWarning: the sets module is deprecated
> import sets
>
> (synaptic:17169): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper:
> assertion `node != NULL' failed
>
> 6) any attempts to install ubuntu-desktop were prevented by a list of it's
> dependencies followed by "but will not be installed." what on earth?
>
> so there you have it. i will continue attempting to update my other files
> as i would normally; it could be a temporary issue.
>