<p dir="ltr"><br>
On Jul 10, 2013 1:15 PM, "Braddock" <<a href="mailto:braddock@braddock.com">braddock@braddock.com</a>> wrote:<br>
><br>
> -----BEGIN PGP SIGNED MESSAGE-----<br>
> Hash: SHA1<br>
><br>
> Thanks Michael, that provides some clarity.<br>
><br>
> I think I probably need to coordinate with the maintainer of the<br>
> python-backports-ssl_match_hostname package, because he is clobbering<br>
> the backports/__init__.py* namespace files we both need. While I<br>
> could patch the __init__.py files to be identical, the compiled .pyc<br>
> files are never exactly the same. They need to be factored out into a<br>
> separate package somehow.<br>
></p>
<p dir="ltr">My hope would be that you could just rm the __init__.pyc,o, files. If there Ian't a meaningful difference in the .py files then there won't be a meaningful difference in the pyc files either. (The observed differences would be sure to embedding timestamps rather than differences in code).</p>
<p dir="ltr">However, rm of those files in your package would leave you needing to Require: the python-backports-ssl_match_hostname package as you will need the __init__.py files installed at runtime.</p>
<p dir="ltr">There is a python-backports package that only provides the namespace on pypi. I talked to the python-backports-ssl-match-hostname maintainer about packaging that and requiring it which he was going to do but I don't know the status of that. It's probably the way to go for both of your packages.</p>
<p dir="ltr">> My newbie question is how do I find the maintainer? The RPM meta-data<br>
> only specifies "Fedora Project" as the maintainer.<br>
></p>
<p dir="ltr">Tibbs sent some links and pointers for finding this out on your own but I also happen to know it is ianweller.</p>
<p dir="ltr">-Toshio</p>
<p dir="ltr">> - -braddock<br>
><br>
> > Date: Sun, 7 Jul 2013 20:48:59 +0200 From: Michael Schwendt<br>
> > <<a href="mailto:mschwendt@gmail.com">mschwendt@gmail.com</a>> To: <a href="mailto:packaging@lists.fedoraproject.org">packaging@lists.fedoraproject.org</a><br>
> > Subject: Re: [Fedora-packaging] Issue packaging python lib into<br>
> > RPM due to conflicting __init__.py Message-ID:<br>
> > <20130707204859.10ed3776@faldor.intranet> Content-Type: text/plain;<br>
> > charset=utf-8<br>
> ><br>
> > On Sun, 07 Jul 2013 09:20:47 -0700, Braddock wrote:<br>
> ><br>
> >> file /usr/lib/python2.7/site-packages/backports/__init__.py from<br>
> >> install of backports.lzma-0.0.2-1.armv7hl conflicts with file<br>
> >> from package<br>
> >> python-backports-ssl_match_hostname-3.2-0.3.a3.fc18.noarch<br>
> ><br>
> > This means that both packages contain a file in that path, and<br>
> > either the file checksum or the file permissions are not the same.<br>
> ><br>
> >> I am uncertain how to resolve this. Is there a way for an RPM to<br>
> >> only create the backports/__init__.py file if it does not already<br>
> >> exist?<br>
> ><br>
> > No. When you create these packages, _you_ need to ensure that they<br>
> > don't include conflicting files. How do those __init__.py files<br>
> > differ in those multiple packages? Is it only a matter of different<br>
> > versions of the backports module? Remember, you've got full control<br>
> > over the package %{buildroot} at build-time, so you could delete<br>
> > files you don't want and which are included in a separate (shared!)<br>
> > package already.<br>
> ><br>
> >> There are a number of packages which would want to live under<br>
> >> the backports/ module.<br>
> ><br>
> > That's okay, but it's not okay if they all contain a differing<br>
> > backports/__init__.py file.<br>
> ><br>
><br>
> -----BEGIN PGP SIGNATURE-----<br>
> Version: GnuPG v1.4.11 (GNU/Linux)<br>
> Comment: Using GnuPG with Thunderbird - <a href="http://www.enigmail.net/">http://www.enigmail.net/</a><br>
><br>
> iQEcBAEBAgAGBQJR3cDuAAoJEHWLR/DQzlZuuFIH/08Y7qkxY01ZbRNV2aOLVZC+<br>
> mjI3+QcR2bKPadDD2BALNyUT/ct36i7u3+endu+j1A8HHj2ls9iEIRisvIM5S9QM<br>
> 3QuvWcDUR3rkQSZlDcqSiuKDbo0qJU297n/HW1YJmGYLdXW6ClbSU5vt0WYvd5vw<br>
> 77hHRF86mvyKsd30rGRLzmbksOIz4nO6gdauh3fAgd2bGLIgJgsExBTSwz9yoV8b<br>
> GVW66wfVREyFa3BmxvpoGnOczW/UoN1sNqDykVHx7EwXQAQ8HOlgB4poxsIY0AHu<br>
> Fqwmsgj74G0RKAwqnRxT91n1J2xYhUNULXUx9ngnM81RkfOjkygE7ewaisOgbpg=<br>
> =euFm<br>
> -----END PGP SIGNATURE-----<br>
> --<br>
> packaging mailing list<br>
> <a href="mailto:packaging@lists.fedoraproject.org">packaging@lists.fedoraproject.org</a><br>
> <a href="https://admin.fedoraproject.org/mailman/listinfo/packaging">https://admin.fedoraproject.org/mailman/listinfo/packaging</a></p>