FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 02-16-2011, 01:18 PM
 
Default Bug#613662: unmet dependencies race condition

Package: linux-image-2.6-686

You have a race condition or something that caused:
The following packages have unmet dependencies:
linux-image-2.6-686: Depends: linux-image-2.6.37-1-686 which is a virtual package.
linux-image-686: Depends: linux-image-2.6.37-1-686 which is a virtual package.
linux-doc-2.6: Depends: linux-doc-2.6.37 which is a virtual package.

I'm sure it will go away soon, however there should never be a moment
when this can occur.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 8762skf4g0.fsf@jidanni.org">http://lists.debian.org/8762skf4g0.fsf@jidanni.org
 
Old 02-17-2011, 09:02 AM
"Didier 'OdyX' Raboud"
 
Default Bug#613662: unmet dependencies race condition

Le Thursday 17 February 2011 02:04:27 jidanni@jidanni.org, vous avez écrit :
> >>>>> "D'R" == Didier 'OdyX' Raboud <odyx@debian.org> writes:
> D'R> Such temporary glitches are perfectly normal (and transitional) in the
> unstable D'R> distribution. All those packages are built and uploaded,
> they will reach your D'R> mirror really soon now. Hence closing this
> non-bug.
>
> Can't they be sent in a different order so as not to expose the problem?

This is not feasible, because of the nature of unstable. Packages get uploaded
and get auto-built by build daemons after the upload. As building packages can
take much time, it is frequent to have architectures that have many more
packages built than others.

On those 'slow' architectures, unsatisfied dependencies are frequent, but almost
always get solved by _waiting_ (I run 'aptitude update; aptitude safe-upgrade'
daily and I don't even see these issues). Hence you cannot expect developers to
wait for _all_ architectures to be up2date to upload packages that depend on a
given package, that would just slow up things for no benefit.

If you want a system that has no such things, you should try testing (currently
Wheezy) or even stable (currently Squeeze), whose migration scripts are
_designed_ to avoid this. Unsatisfied dependencies in the testing or sable
suites are bugs; in unstable they are not (and cannot be, for the reasons
explained above).

Regards,

OdyX

--
Didier Raboud, proud Debian Developer.
CH-1020 Renens
odyx@debian.org



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201102171102.38113.odyx@debian.org">http://lists.debian.org/201102171102.38113.odyx@debian.org
 
Old 02-17-2011, 09:30 AM
 
Default Bug#613662: unmet dependencies race condition

>>>>> "D'R" == Didier 'OdyX' Raboud <odyx@debian.org> writes:
D'R> On those 'slow' architectures, unsatisfied dependencies are frequent, but almost
D'R> always get solved by _waiting_ (I run 'aptitude update; aptitude safe-upgrade'
D'R> daily and I don't even see these issues).
Try 'aptitude update; aptitude full-upgrade'
All I know is I use
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

I don't know if that architecture is slow.

Looking again at

The following packages have unmet dependencies:
linux-image-2.6-686: Depends: linux-image-2.6.37-1-686 which is a virtual package.
linux-image-686: Depends: linux-image-2.6.37-1-686 which is a virtual package.
linux-doc-2.6: Depends: linux-doc-2.6.37 which is a virtual package.

Why can't they simply ensure the lower layers in this particular
dependency pyramid are sent out before or at the same time as the other
parts?

E.g., if I have two web pages, one referring to the other, I know to
make sure the one does not appear before the other.

Anyway, there upon full upgrade we get asked:

The following actions will resolve these dependencies:

Remove the following packages:
1) linux-doc-2.6
2) linux-image-2.6-686
3) linux-image-686

One slip of the finger and we have removed our operating system, "never
to boot again", "it was time for grandpa to retire anyway".

Yes of course it will probably ask us "are we sure?".



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 871v37gdgv.fsf@jidanni.org">http://lists.debian.org/871v37gdgv.fsf@jidanni.org
 
Old 02-17-2011, 09:44 AM
"Didier 'OdyX' Raboud"
 
Default Bug#613662: unmet dependencies race condition

Le Thursday 17 February 2011 11:30:40 jidanni@jidanni.org, vous avez écrit :
> Why can't they simply ensure the lower layers in this particular
> dependency pyramid are sent out before or at the same time as the other
> parts?

Because it's not important in unstable (as it gets solved over time)!

You are using unstable, that is a suite _designed_ to suffer those issues
_all_the_time_ (and will continue to do so).

If you want a system that doesn't have this type of problems; use testing!

> Anyway, there upon full upgrade we get asked:
> (…)
> One slip of the finger and we have removed our operating system, "never
> to boot again", "it was time for grandpa to retire anyway".
>
> Yes of course it will probably ask us "are we sure?".

… This happens because you try a "full upgrade", which is the _WRONG_ thing to
do when using unstable. I mentioned you already that using "safe-upgrade" or
"upgrade" doesn't trigger that type of problems. So you should really try using
the correct tools for the suite you are using; expectations you can have on
stable are not the same than the ones you can have on unstable; both imply
different use cases, different tools and different temporary issues.

Now there is plenty of documentation out there that will explain this better
than me; please let this non-bugreport die.

--
Didier Raboud, proud Debian Developer.
CH-1020 Renens
odyx@debian.org



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201102171144.55600.odyx@debian.org">http://lists.debian.org/201102171144.55600.odyx@debian.org
 

Thread Tools




All times are GMT. The time now is 05:35 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org