Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #14645 > unrolled thread

How to deal with cross-dependant packages

Back to article view | Back to linux.debian.maint.python

Contents

  How to deal with cross-dependant packages Andreas Tille <andreas@an3as.eu> - 2022-11-28 18:00 +0100
    Re: How to deal with cross-dependant packages Scott Kitterman <debian@kitterman.com> - 2022-11-28 18:10 +0100

#14645 — How to deal with cross-dependant packages

Hi,

I'd like to update python-thinc for the Debian Science team.  The new
version needs srsly which needs catalogue[1] which in turn needs
srsly[2].  Do you see any means to solve this cross-dependency?

Kind regards
   Andreas.

[1] https://salsa.debian.org/python-team/packages/python-srsly/-/blob/master/requirements.txt
[2] https://salsa.debian.org/python-team/packages/python-catalogue/-/blob/master/requirements.txt

-- 
http://fam-tille.de

[toc] | [next] | [standalone]

#14646

On November 28, 2022 4:51:23 PM UTC, Andreas Tille <andreas@an3as.eu> wrote:
>Hi,
>
>I'd like to update python-thinc for the Debian Science team.  The new
>version needs srsly which needs catalogue[1] which in turn needs
>srsly[2].  Do you see any means to solve this cross-dependency?
>
>Kind regards
>   Andreas.
>
>[1] https://salsa.debian.org/python-team/packages/python-srsly/-/blob/master/requirements.txt
>[2] https://salsa.debian.org/python-team/packages/python-catalogue/-/blob/master/requirements.txt

Your initial build for upload to new is done locally.  Build them both locally and upload to New at the same time.  Once they are in the archive, those binaries are available to do the second build on the buildds.  At that point it's all bootstrapped and should be fine.

Scott K

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web