[gentoo-user] package update quirck

[gentoo-user] package update quirck

[Dorin Scutarasu]

[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]

Hi,

I just noticed that when I do 'emerge -avuDN world' not all packages get 
updated to the last stable version:

> $ emerge -pvuDN world
>
> These are the packages that would be merged, in order:
>
> Calculating world dependencies                    ... done!
>
> Total: 0 packages, Size of downloads: 0 kB

...but than...

> $ emerge -pv dbus
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies ... done!
> [ebuild     U ] sys-apps/dbus-1.0.2 [0.62-r2] USE="X -debug -doc (-selinux)
> (-gtk%*) (-mono%) (-python%*) (-qt3%*) (-qt4%*)" 1,368 kB
>
> Total: 1 package (1 upgrade), Size of downloads: 1,368 kB

... so I can update to sys-apps/dbus-1.0.2. Also, I see that there are 
packages that need <sys-apps/dbus-0.90:
> $ equery d dbus
> [ Searching for packages depending on dbus... ]
> app-cdr/k3b-0.12.17 (hal? <sys-apps/dbus-0.90)
>                     (hal ? >=sys-apps/dbus-0.30)
>                     (hal ? >=sys-apps/dbus-0.30)
> [...]

... so shouldn't portage prevent me from updating to dbus-1.0.2 since there 
are ebuilds that depend on <sys-apps/dbus-0.90?


-- 
The world is a tragedy to those who feel, but a comedy to those who
think.(Horace Walpole)
*
Dorin Scutarasu,
www.info.UAIC.ro

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-user] Re: package update quirck

[»Q«]

Dorin Scutarasu <dorin.scutarasu@gmail.com> wrote:

> ... so shouldn't portage prevent me from updating to dbus-1.0.2 since
> there are ebuilds that depend on <sys-apps/dbus-0.90?

The required revdep-rebuild after upgrading dbus will take care of
those reverse dependencies. 

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] package update quirck

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]

On Sunday 21 January 2007 23:08, Dorin Scutarasu wrote:
> I just noticed that when I do 'emerge -avuDN world' not all packages get
>
> updated to the last stable version:
> > $ emerge -pvuDN world
[SNIP]
> > Total: 0 packages, Size of downloads: 0 kB
>
> ...but than...
>
> > $ emerge -pv dbus
[SNIP]
> > [ebuild     U ] sys-apps/dbus-1.0.2 [0.62-r2] USE="X -debug -doc
[SNIP]
> ... so I can update to sys-apps/dbus-1.0.2. Also, I see that there are

This suggests that dbus isn't in world or a dep on anything in world. Hence it 
should show up on `emerge --depclean -p`.

> packages that need <sys-apps/dbus-0.90:
> > $ equery d dbus
> > [ Searching for packages depending on dbus... ]
> > app-cdr/k3b-0.12.17 (hal? <sys-apps/dbus-0.90)
> >                     (hal ? >=sys-apps/dbus-0.30)
> >                     (hal ? >=sys-apps/dbus-0.30)
> > [...]
>
> ... so shouldn't portage prevent me from updating to dbus-1.0.2 since there
> are ebuilds that depend on <sys-apps/dbus-0.90?

The actual dependency looks like this:

# grep -A 2 "hal?" $(portageq portdir)/app-cdr/k3b/k3b-0.12.17.ebuild
        hal? ( || ( dev-libs/dbus-qt3-old
                                ( <sys-apps/dbus-0.90 >=sys-apps/dbus-0.30 ) )
                sys-apps/hal )

So k3b doesn't depend on dbus if the hal USE flag is disabled or if 
dbus-qt3-old is installed.

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] package update quirck

[Dorin]

[-- Attachment #1: Type: text/plain, Size: 928 bytes --]

On Monday 22 January 2007 03:04, Bo Ørsted Andresen wrote:
> This suggests that dbus isn't in world or a dep on anything in world. Hence
> it should show up on `emerge --depclean -p`.
Actually k3b is in my world file and dbus doesn't show up 
on 'emerge --depclean -p'.

> The actual dependency looks like this:
>
> # grep -A 2 "hal?" $(portageq portdir)/app-cdr/k3b/k3b-0.12.17.ebuild
>         hal? ( || ( dev-libs/dbus-qt3-old
>                                 ( <sys-apps/dbus-0.90 >=sys-apps/dbus-0.30
> ) ) sys-apps/hal )
>
> So k3b doesn't depend on dbus if the hal USE flag is disabled or if
> dbus-qt3-old is installed.
That would explain it, but I checked and dbus-qt3-old isn't installed and 
an 'equery u k3b' shows k3b actually  has the hal USE flag enabled.

-- 
The world is a tragedy to those who feel, but a comedy to those who
think.(Horace Walpole)
*
Dorin Scutarasu,
www.info.UAIC.ro

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] package update quirck

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]

On Monday 22 January 2007 08:53, Dorin wrote:
> > This suggests that dbus isn't in world or a dep on anything in world.
> > Hence it should show up on `emerge --depclean -p`.
>
> Actually k3b is in my world file and dbus doesn't show up
> on 'emerge --depclean -p'.
>
> > The actual dependency looks like this:
> >
> > # grep -A 2 "hal?" $(portageq portdir)/app-cdr/k3b/k3b-0.12.17.ebuild
> >         hal? ( || ( dev-libs/dbus-qt3-old
> >                                 ( <sys-apps/dbus-0.90
> > >=sys-apps/dbus-0.30 ) ) sys-apps/hal )
> >
> > So k3b doesn't depend on dbus if the hal USE flag is disabled or if
> > dbus-qt3-old is installed.
>
> That would explain it, but I checked and dbus-qt3-old isn't installed and
> an 'equery u k3b' shows k3b actually  has the hal USE flag enabled.

Hmm.. Actually this is the exact reason `emerge -avuDN world` don't try to 
upgrade dbus. When you type `emerge -pv dbus` emerge does not check whether 
any packages in world or in your system requires a lower version or blocks 
dbus. It only checks whether there is an upgrade for dbus and upgrades it if 
there is. 

If you do that on your next `emerge -avuDN world` you will probably see 
portage pull in dev-libs/dbus-qt3-old because ( <sys-apps/dbus-0.90 
>=sys-apps/dbus-0.30 ) is no longer satisfied and dev-libs/dbus-qt3-old is 
listed first and hence preferred.

:)

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] package update quirck

[Dorin Scutarasu]

[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]

Hi,

On Monday 22 January 2007 10:15, Bo Ørsted Andresen wrote:
> Hmm.. Actually this is the exact reason `emerge -avuDN world` don't try to
> upgrade dbus. When you type `emerge -pv dbus` emerge does not check whether
> any packages in world or in your system requires a lower version or blocks
> dbus. It only checks whether there is an upgrade for dbus and upgrades it
> if there is.
>
> If you do that on your next `emerge -avuDN world` you will probably see
> portage pull in dev-libs/dbus-qt3-old because ( <sys-apps/dbus-0.90
>
> >=sys-apps/dbus-0.30 ) is no longer satisfied and dev-libs/dbus-qt3-old is
>
> listed first and hence preferred.
>
> :)

You're right Bo, that's exactly what happend after upgrading.  I had looked in 
that k3b ebuild but not knowing the syntax I didn't realise it needs either 
dev-libs/dbus-qt3-old or <sys-apps/dbus-0.90.

Thanks a lot! :)

-- 
The world is a tragedy to those who feel, but a comedy to those who
think.(Horace Walpole)
*
Dorin Scutarasu,
www.info.UAIC.ro

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]