Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Mathias Behrle Newsgroups: linux.debian.maint.python,linux.debian.bugs.dist Subject: Re: [tryton-debian] Namespace conflict for python-magic Date: Fri, 27 Oct 2017 14:50:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Fri Oct 27 12:44:54 2017 Old-Return-Path: X-Amavis-Spam-Status: No, score=-12.7 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .m9s. - helo: .mx1.mailbox. - helo-domain: .mailbox.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -5 Organization: MBSolutions MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/Ly50tEF8f_0Bj5jBKwmuvxl"; protocol="application/pgp-signature" X-Mailing-List: archive/latest/15346 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20171027144420.5194574a@monsterix.mbehrle.de Approved: robomod@news.nic.it Lines: 120 Sender: robomod@news.nic.it X-Original-Cc: Tryton package maintenance in Debian , Christoph Biedl , Christos Zoulas , debian-python , 877849@bugs.debian.org X-Original-Date: Fri, 27 Oct 2017 14:44:20 +0200 X-Original-Message-ID: <20171027144420.5194574a@monsterix.mbehrle.de> X-Original-References: <20170904174256.40241925@monsterix.mbehrle.de> <1504545692@msgid.manchmal.in-ulm.de> <20170905130017.1eb29221@monsterix.mbehrle.de> <1504628090@msgid.manchmal.in-ulm.de> <20170906102348.6587419c@monsterix.mbehrle.de> <20171005120116.3a92221a@monsterix.mbehrle.de> Xref: csiph.com linux.debian.maint.python:9963 linux.debian.bugs.dist:859341 --Sig_/Ly50tEF8f_0Bj5jBKwmuvxl Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable * Mathias Behrle: " Re: [tryton-debian] Namespace conflict for python-magic" (Thu, 5 Oct 2017 12:01:16 +0200): Hi Adam, are there any news on the subject? The release of Tryton, that will require python-magic is scheduled for next week. It would be a great service to our users and simplify things a lot, i= f we had a common python-magic in place. Please let us know, if we can help with= the planned merge. Thanks, Mathias > * Adam Hupp: " Re: Namespace conflict for python-magic" (Tue, 3 Oct 2017 > 11:06:38 -0700): >=20 > That's good news, Adam, thanks for it! Looking forward to get your diff. >=20 > Best regards, > Mathias >=20 >=20 > > Sorry about the slow response. This has been a pain for a while. I > > have a provisional diff to merge the two packages. Will give it some > > testing and pass a branch to you folks to take a look. Ideally the > > upstream file package would take it over. > >=20 > > On Wed, Sep 6, 2017 at 1:23 AM, Mathias Behrle wro= te: =20 > > > * Christoph Biedl: " Re: Namespace conflict for python-magic" (Tue, 5= Sep > > > 2017 18:24:25 +0200): > > > =20 > > >> Mathias Behrle wrote... > > >> =20 > > >> > * Christoph Biedl: " Re: Namespace conflict for python-magic" (Mon= , 4 > > >> > Sep 2017 19:38:56 +0200): =20 > > >> =20 > > >> > > The cleanest solution indeed was to bring both upstreams togethe= r and > > >> > > ask them to reconcile the APIs and eventually make one of the bo= th > > >> > > implementations obsolete. As things happen such an attempt was > > >> > > started two years ago but appearently never came to a result.[1]= =20 > > >> > > > >> > Agreed, that this would be the cleanest solution, but as you say t= here > > >> > is little probability, that the two upstreams will work together to > > >> > merge their implementations. =20 > > >> > > >> Still this should be tried first. Also, I'm not that pessimistic, see > > >> below. So let's bring the parties involved into the loop: =20 > > > > > > [...] > > > > > > Thanks for your additional information and initiative to re-launch the > > > merge of the two packages. This reads much better and more optimistic= than > > > what I could find until now! Crossing fingers now in the hope for the= best > > > outcome for everybody. > > > > > > Cheers, > > > Mathias > > > > > > -- > > > > > > Mathias Behrle > > > PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405B= BF6 > > > AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6 =20 > >=20 > >=20 > > =20 >=20 >=20 >=20 --=20 Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6 AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6 --Sig_/Ly50tEF8f_0Bj5jBKwmuvxl Content-Type: application/pgp-signature Content-Description: Digitale Signatur von OpenPGP -----BEGIN PGP SIGNATURE----- Comment: Signed by Mathias Behrle iQIzBAEBCgAdFiEErCl+XEa50LYccXaB1tCb5IQFu/YFAlnzKiQACgkQ1tCb5IQF u/bqxw/+KWXCjNpHA84Ur9lT+kHbL3TGAz91IaVvR8C/erWxooj+XfRzWXKERNnR OtQhQZFwWUKCj7nBc1hnH3NsU5xc0VaGN9FrgZU9VGPOVTa/vN5jTt5/Ygx7zeQM xiICj1l6+OZTFVVZI89AUI4mXgdFo/bchg32GOFNN2wETCPAtT71A1kdIsvBXhXR 4Y//aezbQDDCnBHam61gdjvUTkWDLY/bfovxG1S00o2RCjgHcIb7DMlbMht2O1qt /hbbqXJSTeTIZiVqz7WOiqvCC1s49OYSj/odTPjsvQqR7o0UFyxytFUXcNoV+Swl +znnvMV8UlP/9gTqjFA0wqWUqGVcAxM3y68B1k52xlcM2Tyr1aqhylJH4eLLCvm9 8RHMJyLJuAh+pxeOAqHeEJWJGUfWWbsS47fEP86NpnfgcuRsfX2d1ytPIAJ54yUn ZIjozw3VD7pPzInm93ZmWlyMcQAi8Z5xSDk23oPe9iDXgehUJn6v0AVPWi4GmRli wDcNQ1HlFgaG4wjCsvuC33UitoPHNmtvjWKLB5ZQ0LwGjqkQH9XGb9po3HnqXAzF KNJ+KKk0Gf2RoaBiQ/mR4rlhhjuH/UFQj/PrjOeLgN1eXHlSLFD8U/aEAzPB70Sv 2RS5nH5Z3/Nj47W5oJuH90v4N0+1YGMBXPOAmlA5zqvgHdrzj/g= =qOik -----END PGP SIGNATURE----- --Sig_/Ly50tEF8f_0Bj5jBKwmuvxl--