Re: Etch dependency failures
hi OK i'm not a package maintainer or anything. but i've been watching the status of etch and sid for a couple weeks now because i've had the same problems as you - each time i try for an aptitude upgrade i get depencency hell. as far as i understand, what is happening is that several critical and co-dependent packages are getting some bugs hammered out, and are slightly out of sync with each other in terms of the next source upload, with the result that a lot of dependencies are broken right now. every couple days, _some_ of the problems are resolved. (although sadly more crop up). I'm almost at the point now where my aptitude upgrade goes through without errors. seems they're clearing things up. cheers adam
Re: Etch dependency failures
On Sun, Feb 19, 2006 at 04:53:23PM -0500, Amadan Korvin wrote: hi OK i'm not a package maintainer or anything. but i've been watching the status of etch and sid for a couple weeks now because i've had the same problems as you - each time i try for an aptitude upgrade i get depencency hell. as far as i understand, what is happening is that several critical and co-dependent packages are getting some bugs hammered out, and are slightly out of sync with each other in terms of the next source upload, with the result that a lot of dependencies are broken right now. every couple days, _some_ of the problems are resolved. (although sadly more crop up). I'm almost at the point now where my aptitude upgrade goes through without errors. seems they're clearing things up. cheers adam Hi Adam, this is the process of creating a relatively bug-free distribution! It takes a LOT of this to finally produce 'stable' where all these issue are resolved. As this process proceeds, testing becomes more stable and less things are pulled out and put in. It takes between 12 and 24 months for Debian. There are ways to speed up this process, because you do not have to be a Debian Developer to fix problems. Not every package is maintained by Debian Developers. Most of the applications are not done by Debian Developers. The hard part is finding out what needs to be done SPECIFICALLY beyond locating orphaned packages or looking in the BTS (bugs.debian.org, our bug tracking system) but the main thrust is to fix things you are interested it and submit them as bug reports or patches. Cheers, Kev -- | .''`. == Debian GNU/Linux == | my web site: | | : :' : The Universal | debian.home.pipeline.com | | `. `' Operating System| go to counter.li.org and | | `-http://www.debian.org/ |be counted! #238656 | | my keysever: pgp.mit.edu | my NPO: cfsg.org | signature.asc Description: Digital signature
Re: Re: Etch dependency failures
Hi sorry, i guess i came off sounding complaining. actually i knew that this is a normal process. i was just hoping that the info might be useful to the other dude on the thread. and i've been doing bug reports for the packages, to help ;) adam
Etch dependency failures
I'm running Etch. For a few weeks now, whenever I do my regular (more than once a week) 'aptitude dist-upgrade', I get messages about unmet dependencies. The original ones were about libpaper1 and libpaper-utils, but in the last week or so more have started appearing each time. I'm surprised that these haven't been fixed quickly. Does anybody know what is the reason for these errors? The following packages have unmet dependencies: libpaperg: Depends: libpaper1 (= 1.1.14-3) but 1.1.14-5 is to be installed. Depends: libpaper-utils (= 1.1.14-3) but 1.1.14-5 is to be installed. python2.3-glade2: Depends: python2.3-gtk2 (= 2.6.3-2) but 2.8.2-3 is installed. dbus-glib-1: Depends: dbus-1 (= 0.23.4) but it is not installable libhal0: Depends: dbus-1 (= 0.23.4) but it is not installable libhal-storage0: Depends: dbus-1 (= 0.23.4) but it is not installable dbus-qt-1-dev: Depends: dbus-qt-1c2 (= 0.23.4-8) but it is not installable Depends: dbus-1-dev (= 0.23.4-8) but it is not installable -- David Jarvie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Etch dependency failures
On 2/18/06, David Jarvie [EMAIL PROTECTED] wrote: I'm running Etch. For a few weeks now, whenever I do my regular (more thanonce a week) 'aptitude dist-upgrade', I get messages about unmetdependencies. The original ones were about libpaper1 and libpaper-utils, but in the last week or so more have started appearing each time. I'm surprisedthat these haven't been fixed quickly. Does anybody know what is the reasonfor these errors?The following packages have unmet dependencies: libpaperg: Depends: libpaper1 (= 1.1.14-3) but 1.1.14-5 is to be installed. Depends: libpaper-utils (= 1.1.14-3) but 1.1.14-5 is to beinstalled.python2.3-glade2: Depends: python2.3-gtk2 (= 2.6.3-2) but 2.8.2-3 isinstalled.dbus-glib-1: Depends: dbus-1 (= 0.23.4) but it is not installable libhal0: Depends: dbus-1 (= 0.23.4) but it is not installablelibhal-storage0: Depends: dbus-1 (= 0.23.4) but it is not installabledbus-qt-1-dev: Depends: dbus-qt-1c2 (= 0.23.4-8) but it is not installable Depends: dbus-1-dev (= 0.23.4-8) but it is not installable I had a similar experience 3 or 4 weeks ago (I do weekly updates with aptitude). Aptitude reported that several packages - a list similar to that above - were broken. I followed the broken dependencies and fixed them one by one (using 'b' in aptitude to find each broken package, and then examining each one for what was missing and installing it). As I recall, it took a couple of passes to get everything back in order, but I haven't had the problem since. Of course, all that should not be necessary - but at least it worked, for me at least. Patrick
Re: Etch dependency failures
On Sat, Feb 18, 2006 at 10:23:18AM +, David Jarvie wrote: I'm running Etch. For a few weeks now, whenever I do my regular (more than once a week) 'aptitude dist-upgrade', I get messages about unmet dependencies. The original ones were about libpaper1 and libpaper-utils, but in the last week or so more have started appearing each time. I'm surprised that these haven't been fixed quickly. Does anybody know what is the reason for these errors? The following packages have unmet dependencies: libpaperg: Depends: libpaper1 (= 1.1.14-3) but 1.1.14-5 is to be installed. Depends: libpaper-utils (= 1.1.14-3) but 1.1.14-5 is to be installed. python2.3-glade2: Depends: python2.3-gtk2 (= 2.6.3-2) but 2.8.2-3 is installed. dbus-glib-1: Depends: dbus-1 (= 0.23.4) but it is not installable libhal0: Depends: dbus-1 (= 0.23.4) but it is not installable libhal-storage0: Depends: dbus-1 (= 0.23.4) but it is not installable dbus-qt-1-dev: Depends: dbus-qt-1c2 (= 0.23.4-8) but it is not installable Depends: dbus-1-dev (= 0.23.4-8) but it is not installable Hi David, the developent cycle begins with bug reports with bug fixes or new upstream versions. When those happen, a new version is created and its upload to unstable/sid. If this version is not found to be buddy, after about 10 days, it will get moved to testing/etch by 'britney'. So, things do not get fixed 'quickly'. The thing about testing is that things can be added and removed depending upon available depenpencies which leads to the situation above. The name 'testing' is actaully the workshop of 'Debian' as its where the next stable is born. -Kev -- | .''`. == Debian GNU/Linux == | my web site: | | : :' : The Universal | debian.home.pipeline.com | | `. `' Operating System| go to counter.li.org and | | `-http://www.debian.org/ |be counted! #238656 | | my keysever: pgp.mit.edu | my NPO: cfsg.org | signature.asc Description: Digital signature
Re: Etch dependency failures
On Saturday 18 February 2006 15:08, Patrick Wiseman wrote: On 2/18/06, David Jarvie [EMAIL PROTECTED] wrote: I'm running Etch. For a few weeks now, whenever I do my regular (more than once a week) 'aptitude dist-upgrade', I get messages about unmet dependencies. The original ones were about libpaper1 and libpaper-utils, but in the last week or so more have started appearing each time. I'm surprised that these haven't been fixed quickly. Does anybody know what is the reason for these errors? The following packages have unmet dependencies: libpaperg: Depends: libpaper1 (= 1.1.14-3) but 1.1.14-5 is to be installed. Depends: libpaper-utils (= 1.1.14-3) but 1.1.14-5 is to be installed. python2.3-glade2: Depends: python2.3-gtk2 (= 2.6.3-2) but 2.8.2-3 is installed. dbus-glib-1: Depends: dbus-1 (= 0.23.4) but it is not installable libhal0: Depends: dbus-1 (= 0.23.4) but it is not installable libhal-storage0: Depends: dbus-1 (= 0.23.4) but it is not installable dbus-qt-1-dev: Depends: dbus-qt-1c2 (= 0.23.4-8) but it is not installable Depends: dbus-1-dev (= 0.23.4-8) but it is not installable I had a similar experience 3 or 4 weeks ago (I do weekly updates with aptitude). Aptitude reported that several packages - a list similar to that above - were broken. I followed the broken dependencies and fixed them one by one (using 'b' in aptitude to find each broken package, and then examining each one for what was missing and installing it). As I recall, it took a couple of passes to get everything back in order, but I haven't had the problem since. Of course, all that should not be necessary - but at least it worked, for me at least. Aptitude didn't show any broken packages for me. But I tried marking one of two of the packages as automatically installed, and that allowed aptitude to resolve the errors. Thanks for pointing me in the right direction. -- David Jarvie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Etch dependency failures
On Saturday 18 February 2006 16:21, Kevin Mark wrote: On Sat, Feb 18, 2006 at 10:23:18AM +, David Jarvie wrote: I'm running Etch. For a few weeks now, whenever I do my regular (more than once a week) 'aptitude dist-upgrade', I get messages about unmet dependencies. The original ones were about libpaper1 and libpaper-utils, but in the last week or so more have started appearing each time. I'm surprised that these haven't been fixed quickly. Does anybody know what is the reason for these errors? The following packages have unmet dependencies: libpaperg: Depends: libpaper1 (= 1.1.14-3) but 1.1.14-5 is to be installed. Depends: libpaper-utils (= 1.1.14-3) but 1.1.14-5 is to be installed. python2.3-glade2: Depends: python2.3-gtk2 (= 2.6.3-2) but 2.8.2-3 is installed. dbus-glib-1: Depends: dbus-1 (= 0.23.4) but it is not installable libhal0: Depends: dbus-1 (= 0.23.4) but it is not installable libhal-storage0: Depends: dbus-1 (= 0.23.4) but it is not installable dbus-qt-1-dev: Depends: dbus-qt-1c2 (= 0.23.4-8) but it is not installable Depends: dbus-1-dev (= 0.23.4-8) but it is not installable Hi David, the developent cycle begins with bug reports with bug fixes or new upstream versions. When those happen, a new version is created and its upload to unstable/sid. If this version is not found to be buddy, after about 10 days, it will get moved to testing/etch by 'britney'. So, things do not get fixed 'quickly'. The thing about testing is that things can be added and removed depending upon available depenpencies which leads to the situation above. The name 'testing' is actaully the workshop of 'Debian' as its where the next stable is born. -Kev I know that 'testing' isn't guaranteed to be as bug-free as stable. I was just under the impression that dependencies were things that you never have to worry about at all using Debian, whether you're using stable, testing or unstable. These are the first such errors I can remember in over a year using Debian testing, so I was a bit surprised when they didn't go away. Anyway, thanks to Patrick's suggestion, I've managed to resolve them now. Regardless of these small problems, I'm still a big fan of Debian's dependency handling and of how upgrades are handled (particularly the fact that it doesn't overwrite manually edited config files without asking first). -- David Jarvie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
