Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref
----- Mail original -----
> De: "Olivier Sallou" <olivier.sallou@irisa.fr>
> À: "Andreas Tille" <andreas@an3as.eu>
> Cc: debian-python@lists.debian.org, "Debian Science List" <debian-science@lists.debian.org>, 777089@bugs.debian.org
> Envoyé: Mardi 23 Janvier 2018 17:11:05
> Objet: Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting
> python-backports.weakref
>
>
>
> ----- Mail original -----
> > De: "Andreas Tille" <andreas@an3as.eu>
> > À: debian-python@lists.debian.org, "Debian Science List"
> > <debian-science@lists.debian.org>, 777089@bugs.debian.org
> > Envoyé: Lundi 22 Janvier 2018 15:04:10
> > Objet: Re: Next python-mote pre-condition - issue with pybuild:
> > python-backports.tempfile conflicting
> > python-backports.weakref
> >
> > Hi,
> >
> > I kept on working packaging python-moto predependencies. I'm now
> > stumbling upon python-backports.tempfile[1] and
> > python-backports.weakref[2]. My naive packaging attempt puts
> > the modules into
>
> well, package name should not really use dots in name, I suppose that's what
> leads to error. But don't know how to fix that with python helper... :-(
>
> both modules use the same "base module", ie *backports* so final dest is
> correct. From a pure python point of view, you can "merge" multiple sub
> modules in the same mail module, python will manage the duplication of
> __init__.py
>
> However, in Debian case, I do not know how this can be handled as 2 packages
> cannot hold the same file (even if __init__ is only an empty file), and at
> least one must be present (if you install only one).
>
> Olivier
>
> >
> > /usr/lib/python*/dist-packages/backports
> >
> > leaving the same package
> >
> > /usr/lib/python3/dist-packages/backports/__init__.py
after thinking about this, I think the "easy" solution would be to:
* create a *backports* package, that simply embeds a backports/__init__.py
* depends on this backports package itself and simply remove backports/__init__.py from backports.XXX packages.
If they depend on backports, this file will will always be present, and will be of for backports.xx modules.
You would only need to remove the file from installed files in packages.
I see though that you have already uploaded package, how did you handle the issue?
Olivier
> >
> > for both packages and thus the packages are conflicting. I have no idea
> > why pybuild simply uses the dir backports instead of the full module
> > name nor do I have any idea how to fix this. I tried to hack around in
> > the backports.weakref package using
> >
> >
> > override_dh_auto_install:
> > for dir in `find .pybuild -type d -name backports | sort | uniq` ;
> > do
> > \
> > mv $${dir} $${dir}.weakref ; \
> > done
> > dh_auto_install
> >
> > but this rather has led to an empty package.
> >
> > Any help is welcome
> >
> > Andreas.
> >
> >
> > [1] https://salsa.debian.org/science-team/python-backports.tempfile.git
> > [2] https://salsa.debian.org/science-team/python-backports.weakref.git
> >
> > --
> > http://fam-tille.de
> >
> >
>
>
Reply to: