Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Olivier Sallou Newsgroups: linux.debian.maint.python,linux.debian.bugs.dist Subject: Re: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref Date: Fri, 26 Jan 2018 16:20:02 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Jan 26 15:17:45 2018 Old-Return-Path: X-Amavis-Spam-Status: No, score=-8.979 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, THREADTOPIC=2] autolearn=ham autolearn_force=no X-Policyd-Weight: DYN_NJABL=ERR(0) NOT_IN_SBL_XBL_SPAMHAUS=-1.5 BL_NJABL=SKIP(-1.5) CL_IP_EQ_HELO_IP=-2 (check from: .irisa. - helo: .mail3-relais-sop.national.inria. - helo-domain: .inria.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -7 X-Ironport-Av: E=Sophos;i="5.46,417,1511823600"; d="scan'208";a="252615122" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [93.182.241.67] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - GC64 (Linux)/8.0.9_GA_6191) Thread-Topic: Next python-mote pre-condition - issue with pybuild: python-backports.tempfile conflicting python-backports.weakref Thread-Index: UHUNzU59CPuQ7TE36rRqZ/sStyOgMRPmIidL X-Mailing-List: archive/latest/15484 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/2053892684.30216711.1516979842872.JavaMail.zimbra@irisa.fr Approved: robomod@news.nic.it Lines: 104 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org, Debian Science List , 777089@bugs.debian.org, Andreas Tille X-Original-Date: Fri, 26 Jan 2018 16:17:22 +0100 (CET) X-Original-Message-ID: <2053892684.30216711.1516979842872.JavaMail.zimbra@irisa.fr> X-Original-References: <20180112160153.swvluhcudyw43ll6@an3as.eu> <20180115115929.gnffbsmgmr2b2dcr@an3as.eu> <20180115125227.e63vjwbitdyes26l@sar0.p1otr.com> <20180115150627.kgbqbkp4vxctyaj6@an3as.eu> <20180115151500.zki5z3lxuhldylzr@sar0.p1otr.com> <20180116204521.xm27u6rucyoxgk2p@an3as.eu> <20180122140410.llapcwh7xg2uwsg7@an3as.eu> <1287060898.28997207.1516723865837.JavaMail.zimbra@irisa.fr> Xref: csiph.com linux.debian.maint.python:10089 linux.debian.bugs.dist:877838 ----- Mail original ----- > De: "Olivier Sallou" > =C0: "Andreas Tille" > Cc: debian-python@lists.debian.org, "Debian Science List" , 777089@bugs.debian.org > Envoy=E9: Mardi 23 Janvier 2018 17:11:05 > Objet: Re: Next python-mote pre-condition - issue with pybuild: python-ba= ckports.tempfile conflicting > python-backports.weakref >=20 >=20 >=20 > ----- Mail original ----- > > De: "Andreas Tille" > > =C0: debian-python@lists.debian.org, "Debian Science List" > > , 777089@bugs.debian.org > > Envoy=E9: Lundi 22 Janvier 2018 15:04:10 > > Objet: Re: Next python-mote pre-condition - issue with pybuild: > > python-backports.tempfile conflicting > > python-backports.weakref > >=20 > > Hi, > >=20 > > 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 >=20 > well, package name should not really use dots in name, I suppose that's w= hat > leads to error. But don't know how to fix that with python helper... :-( >=20 > 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 >=20 > However, in Debian case, I do not know how this can be handled as 2 packa= ges > cannot hold the same file (even if __init__ is only an empty file), and a= t > least one must be present (if you install only one). >=20 > Olivier >=20 > >=20 > > /usr/lib/python*/dist-packages/backports > >=20 > > leaving the same package > >=20 > > /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/__i= nit__.py from backports.XXX packages. If they depend on backports, this file will will always be present, and wil= l 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 > >=20 > > for both packages and thus the packages are conflicting. I have no ide= a > > 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 > >=20 > >=20 > > override_dh_auto_install: > > for dir in `find .pybuild -type d -name backports | sort | uniq= ` ; > > do > > \ > > mv $${dir} $${dir}.weakref ; \ > > done > > dh_auto_install > >=20 > > but this rather has led to an empty package. > >=20 > > Any help is welcome > >=20 > > Andreas. > >=20 > >=20 > > [1] https://salsa.debian.org/science-team/python-backports.tempfile.git > > [2] https://salsa.debian.org/science-team/python-backports.weakref.git > >=20 > > -- > > http://fam-tille.de > >=20 > >=20 >=20 >=20