emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#53883: closed (python-twice cannot be installed in a profile due to


From: GNU bug Tracking System
Subject: bug#53883: closed (python-twice cannot be installed in a profile due to collisions)
Date: Wed, 16 Feb 2022 22:07:02 +0000

Your message dated Wed, 16 Feb 2022 23:06:26 +0100
with message-id <87zgmq31r1.fsf@gnu.org>
and subject line Re: bug#53883: strange conflicts with guix package -m manifest
has caused the debbugs.gnu.org bug report #53883,
regarding python-twice cannot be installed in a profile due to collisions
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
53883: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=53883
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: strange conflicts with guix package -m manifest Date: Tue, 08 Feb 2022 22:05:32 +0100 User-agent: mu4e 1.6.10; emacs 27.2
Hello Guix,

I see strange conflicts when trying to update packages via manifest:

guix package: error: profile contains conflicting entries for python-cffi
guix package: error:   first entry: python-cffi@1.15.0 
/gnu/store/fnkn12qv3bw7z3jhdgp2drd0nnn0p433-python-cffi-1.15.0
guix package: error:    ... propagated from python-cmarkgfm@0.7.0
guix package: error:    ... propagated from python-readme-renderer@32.0
guix package: error:    ... propagated from python-twine@1.15.0
guix package: error:   second entry: python-cffi@1.14.4 
/gnu/store/4zz00w8rqrfazv5lsjajs0g8y04ysa8g-python-cffi-1.14.4
guix package: error:    ... propagated from python-cryptography@3.3.1
guix package: error:    ... propagated from python-pyopenssl@20.0.1
guix package: error:    ... propagated from python-urllib3@1.26.7
guix package: error:    ... propagated from python-requests@2.26.0
guix package: error:    ... propagated from python-requests-toolbelt@0.9.1
guix package: error:    ... propagated from python-twine@1.15.0


As you can see, both packages are python-twine, and they have
conflicting dependencies.

I attached both my manifest and my channels file.

To reproduce:


    LANG=C guix package -kK --fallback -m ~/fluss-guix.manifest


$ LANG=C guix describe
Generation 377  Feb 07 2022 10:35:27    (current)
  guix c6b407c
    repository URL: https://git.savannah.gnu.org/git/guix.git
    branch: master
    commit: c6b407c923253ac3e7ce8439b31f52ef94de7846
  flat ece373b
    repository URL: https://github.com/flatwhatson/guix-channel.git
    branch: master
    commit: ece373bcd1e00ef746fb7b104e56ab610cc4af2a
    

Attachment: fluss-guix.manifest
Description: Binary data

Attachment: channels.scm
Description: Binary data

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: bug#53883: strange conflicts with guix package -m manifest Date: Wed, 16 Feb 2022 23:06:26 +0100
Ludovic Courtès <ludo@gnu.org> skriver:

> Hi,
>
> Leo Famulari <leo@famulari.name> skribis:
>
>> Basically, the python-twine package, as it is now, cannot be installed
>> in a profile.
>>
>> That is because its dependency graph of propagated packages includes
>> different versions of python-cffi, and you cannot install both of these
>> cffi packages alongside each other in a symlink forest (i.e. a profile).
>
> Any idea how this could be addressed?
>
> There are currently 133 dependents of python-cffi@1.15 (python-cmarkgfm
> is the only direct user) and 3,807 dependents of python-cffi@1.14.  It’d
> be easier if they all depended on 1.14.
>
> Unfortunately we can’t just use 1.14 for python-cmarkgfm:
>
> --8<---------------cut here---------------start------------->8---
> $ guix build python-cmarkgfm --with-input=python-cffi@1.15=python-cffi@1.14
> […]
> ERROR: Could not find a version that satisfies the requirement cffi>=1.15.0 
> (from versions: none)
> ERROR: No matching distribution found for cffi>=1.15.0
> --8<---------------cut here---------------end--------------->8---
>
> Should we downgrade python-cmarkgfm, or relax its requirements?  Marius,
> WDYT?  :-)

I dug around in the upstream commit history and it appears that the
requirement was only added for Python 3.10 compatibility.  So I relaxed
its requirements in commit f37eb24df5ecb3a14bd42507076854cc979ddecf.

-- 
Thanks,
Marius

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]