rpm needs db-6.1.26+ patch (was Re: python3 optional deps)
On Jun 1, 2016, at 6:29 PM, Elan Ruusamäe wrote: > > 1. were in middle of 5.4.15 -> 5.4.17 change The attached patch (for db-6.1.26/db-6.2.23) is necessary with rpm-5.4.x). Earlier versions of db-x.y.z need no modification. hth 73 de Jeff == jbj13.patch Description: Binary data ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: python3 optional deps
On 06.05.2016 14:36, Jacek Konieczny wrote: On 2016-05-06 10:59, Elan Ruusamäe wrote: On 06.05.2016 11:47, Jacek Konieczny wrote: Feel free to separate it :-) sure. suggest package name? rpm-pythonprov? It is already a separate package, just built with whole RPM. looks like there's just one file to move: /usr/lib/rpm/pythoneggs.py [jajcus@jajo ~]$ rpm -ql rpm-pythonprov /usr/lib/rpm/pythondeps.sh /usr/lib/rpm/pythoneggs.py while i didn't actually solve the previous problem, i've hit similar problem with making change to gem_helper.rb https://github.com/pld-linux/rpm/commit/d2eb086f435776799b4bde76f34ecd5f67eb171f the change should be versioned, so .spec files could use it, it being built from rpm.spec means the dep should be rpm version specific, which i do not like: 1. were in middle of 5.4.15 -> 5.4.17 change 2. the change isn't in rpm code at all 3. some (qboosh?) still uses his own rpm build (rpm4.5?) 4. pld-ac also uses rpm4.5, altho it's probably not affected for these two cases (python and ruby) so, move all those *prov* packages from rpm.spec to rpm-build-macros package? these are never going to be using upstream files, we always patch them. (and this doesn't prevent time to time submitting them to upstream) -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: python3 optional deps
On Fri, May 06, 2016 at 09:11:26AM +0200, Jacek Konieczny wrote:
> On 2016-05-04 11:11, Elan Ruusamäe wrote:
> >
> >can someone check (and fix?) why those optional deps:
> >https://github.com/docker/docker-py/blob/1.8.1/setup.py#L14-L17
> >
> >
> >
> >
> >extras_require = {
> >
> >':python_version < "3.5"': 'backports.ssl_match_hostname >= 3.5',
> >
> >':python_version < "3.3"': 'ipaddress >= 1.0.16',
> >
> >}
> >
> >
> >
> >end up in python3 egg and therefore rpm deps:
>
> They will end up in the egg, that is the design. Those should not be
> converted to rpm deps, though. And for python3 package these deps are
> useless even in the egg-info.
The other problem IIRC is that even python3egg dependencies with
python_version conditions are resolved using system python2 version
(because python dependency generator is run with python2).
--
Jakub Boguszhttp://qboosh.pl/
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: python3 optional deps
On May 6, 2016, at 3:41 AM, Elan Ruusamäe wrote: > On 06.05.2016 10:11, Jacek Konieczny wrote: >> >> I guess the python dependency generator should be fixed in our RPM, to >> ignore the 'extras' dependencies (or to make them 'suggest', skipping the >> ':python_version' ones. > is there python module to parse the egg info? or just manual parsing each time > > btw, maybe it's better to extract the python dependency generators as > separate package, out of rpm sourcetree? > it would be a lot simplier to maintain, than patching patch patching the > previous patch. our patches will likely never end up upstream. > Submit any patches for rpm you wish. Meanwhile, rpm cannot carry extractors for every possible dependency forever, that simply does not scale. 73 de Jeff ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: python3 optional deps
On 2016-05-06 10:59, Elan Ruusamäe wrote: On 06.05.2016 11:47, Jacek Konieczny wrote: Feel free to separate it :-) sure. suggest package name? rpm-pythonprov? It is already a separate package, just built with whole RPM. looks like there's just one file to move: /usr/lib/rpm/pythoneggs.py [jajcus@jajo ~]$ rpm -ql rpm-pythonprov /usr/lib/rpm/pythondeps.sh /usr/lib/rpm/pythoneggs.py Jacek ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: python3 optional deps
On 06.05.2016 11:47, Jacek Konieczny wrote: Feel free to separate it :-) sure. suggest package name? looks like there's just one file to move: /usr/lib/rpm/pythoneggs.py or just move it to rpm-build-macros package? -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: python3 optional deps
On 2016-05-06 09:41, Elan Ruusamäe wrote: On 06.05.2016 10:11, Jacek Konieczny wrote: I guess the python dependency generator should be fixed in our RPM, to ignore the 'extras' dependencies (or to make them 'suggest', skipping the ':python_version' ones. is there python module to parse the egg info? or just manual parsing each time btw, maybe it's better to extract the python dependency generators as separate package, out of rpm sourcetree? it would be a lot simplier to maintain, than patching patch patching the previous patch. our patches will likely never end up upstream. Feel free to separate it :-) I can try to fix it then. Jacek ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: python3 optional deps
On 06.05.2016 10:11, Jacek Konieczny wrote: I guess the python dependency generator should be fixed in our RPM, to ignore the 'extras' dependencies (or to make them 'suggest', skipping the ':python_version' ones. is there python module to parse the egg info? or just manual parsing each time btw, maybe it's better to extract the python dependency generators as separate package, out of rpm sourcetree? it would be a lot simplier to maintain, than patching patch patching the previous patch. our patches will likely never end up upstream. -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: python3 optional deps
On 2016-05-04 11:11, Elan Ruusamäe wrote:
can someone check (and fix?) why those optional deps:
https://github.com/docker/docker-py/blob/1.8.1/setup.py#L14-L17
extras_require = {
':python_version < "3.5"': 'backports.ssl_match_hostname >= 3.5',
':python_version < "3.3"': 'ipaddress >= 1.0.16',
}
end up in python3 egg and therefore rpm deps:
They will end up in the egg, that is the design. Those should not be
converted to rpm deps, though. And for python3 package these deps are
useless even in the egg-info.
I guess the python dependency generator should be fixed in our RPM, to
ignore the 'extras' dependencies (or to make them 'suggest', skipping
the ':python_version' ones.
The easy fix for python-docker.spec would be to strip those from
docker_py-1.8.1-py3.5.egg-info/requires.txt (everything from the first '[').
Jacek
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
python3 optional deps
can someone check (and fix?) why those optional deps:
https://github.com/docker/docker-py/blob/1.8.1/setup.py#L14-L17
extras_require = {
':python_version < "3.5"': 'backports.ssl_match_hostname >= 3.5',
':python_version < "3.3"': 'ipaddress >= 1.0.16',
}
end up in python3 egg and therefore rpm deps:
1. error:[python-docker.spec
]
python3-docker-1.8.1-1.noarch: req
python3egg(backports.ssl-match-hostname) >= 3.5 not found
2. error:[python-docker.spec
]
python3-docker-1.8.1-1.noarch: req python3egg(ipaddress) >= 1.0.16
not found
spec itself is here:
https://github.com/pld-linux/python-docker/blob/auto/th/python-docker-1.8.1-1/python-docker.spec
--
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
