From: Alex Alexander <wired@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] revbumping ebuilds after USE dependency changes
Date: Wed, 24 Jul 2013 15:49:23 +0300 [thread overview]
Message-ID: <20130724124923.GB3010@ion.office.nerd.gr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
Hello,
Please revbump an ebuild after changing its USE dependencies.
Using net-p2p/transmission as an example, it used to depend on
dev-qt/qtgui:4=[dbus]
however, qtgui lost the dbus useflag, so the dependency was changed to
dev-qt/qtgui:4=[dbus(+)]
without revbumping the transmission ebuild. [0]
Portage fails to notice this when resolving dependencies if the package was
installed prior to the change, resulting in errors like the following:
(dev-qt/qtgui-4.8.5::gentoo, ebuild scheduled for merge) conflicts
with dev-qt/qtgui:4/4=[dbus] required by
(net-p2p/transmission-2.80::gentoo, installed)
which, I imagine, could be very frustrating for a user who doesn't mess
with the internals of Gentoo often.
You might think that such a revbump is overkill, but in reality the user will
have to re-emerge the package anyway in order to get rid of the error, so there
is no point in avoiding it, unless portage changes the way it handles these
changes.
[0] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-p2p/transmission/transmission-2.80.ebuild?r1=1.1&r2=1.2
Thanks,
--
Alex Alexander | wired@gentoo
+ www.linuxized.com
++ www.leetworks.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-07-24 12:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 12:49 Alex Alexander [this message]
[not found] ` < CAJ0EP43edWPPYXXMOQPL4V2ZdO8R4YArpcNJK5cgBOqahzVdYw@mail.gmail.com>
2013-07-24 14:15 ` [gentoo-dev] revbumping ebuilds after USE dependency changes Mike Gilbert
2013-07-24 15:31 ` Alex Alexander
2013-07-24 15:48 ` "Paweł Hajdan, Jr."
[not found] ` < 20130724132315.19acde44@caribou.gateway.2wire.net>
2013-07-24 19:23 ` [gentoo-dev] " Ryan Hill
2013-07-24 19:17 ` Michał Górny
2013-07-24 19:18 ` Ciaran McCreesh
2013-07-25 0:53 ` Rick "Zero_Chaos" Farina
2013-07-25 3:50 ` "Paweł Hajdan, Jr."
2013-07-25 3:54 ` Zac Medico
2013-07-25 15:29 ` Rick "Zero_Chaos" Farina
2013-07-25 17:28 ` Zac Medico
2013-07-25 18:29 ` Rick "Zero_Chaos" Farina
2013-07-25 18:36 ` Zac Medico
2013-07-24 19:40 ` Ryan Hill
2013-07-24 19:44 ` Ciaran McCreesh
2013-07-25 7:07 ` Michael Palimaka
2013-07-28 9:11 ` Michał Górny
2013-07-28 12:37 ` Kent Fredric
[not found] ` <20130728111113.318cdc6a@gentoo. org>
2013-07-29 0:39 ` Duncan
2013-07-29 8:04 ` Zac Medico
2013-07-29 11:03 ` Duncan
2013-07-24 17:54 ` [gentoo-dev] " Davide Pesavento
2013-07-25 7:43 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130724124923.GB3010@ion.office.nerd.gr \
--to=wired@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox