From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: 42595@debbugs.gnu.org
Subject: bug#42595: conflicts in propagated imports must be resolved manually
Date: Wed, 29 Jul 2020 09:54:07 +0200 [thread overview]
Message-ID: <87o8nylpsw.fsf@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]
Hi,
When I get conflicts in propagated imports, I must follow a mechanical
multi-step process to resolve them manually.
A recent example: I wanted to install guile-gi. In the first step I was
told to also update python-pycairo, and in the next steps I had to add,
one by one,
dbus-glib cairo guile-charting libsoup poppler pango
And now I gave up. I’m now here and out of time:
LANG=C guix package -i guile-gi python-pycairo dbus-glib cairo guile-charting libsoup poppler pango
The following packages will be upgraded:
python-pycairo (dependencies or package changed)
dbus-glib (dependencies or package changed)
cairo (dependencies or package changed)
guile-charting (dependencies or package changed)
libsoup (dependencies or package changed)
poppler (dependencies or package changed)
pango (dependencies or package changed)
The following package will be installed:
guile-gi 0.3.0
guix package: error: profile contains conflicting entries for glib
guix package: error: first entry: glib@2.62.6 /gnu/store/xr6zfqxklmr7skalljn5i071xmgqxbrm-glib-2.62.6
guix package: error: ... propagated from cairo@1.16.0
guix package: error: ... propagated from pango@1.44.7
guix package: error: second entry: glib@2.62.6 /gnu/store/q4100sjqcsdi6b232ndr93vxfzv9bzij-glib-2.62.6
guix package: error: ... propagated from libnotify@0.7.7
This should be automated, so there would be just one step to add all
updates I need.
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]
next reply other threads:[~2020-07-29 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 7:54 Dr. Arne Babenhauserheide [this message]
2020-07-29 8:14 ` bug#42595: conflicts in propagated imports must be resolved manually Efraim Flashner
2020-08-24 14:44 ` Ludovic Courtès
2022-07-14 3:09 ` Maxim Cournoyer
2022-07-15 13:31 ` Ludovic Courtès
2021-02-15 23:50 ` Luis Felipe via Bug reports for GNU Guix
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=87o8nylpsw.fsf@web.de \
--to=arne_bab@web.de \
--cc=42595@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.