Re: python rebuild procedure?
On Wednesday 04 of May 2016, Elan Ruusamäe wrote: > On 04.05.2016 13:07, Jacek Konieczny wrote: > > That could be because of the recent changes to python3.spec by Jan, > > which I knew they are breaking something, but I couldn't tell what. > > seems builds now after arekm changes (whatever they were) poldek -uGv python3-modules --nodeps --force, after that it builds (--without tests) -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: python rebuild procedure?
On 04.05.2016 13:07, Jacek Konieczny wrote: That could be because of the recent changes to python3.spec by Jan, which I knew they are breaking something, but I couldn't tell what. seems builds now after arekm changes (whatever they were) -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: python rebuild procedure?
On 2016-05-04 11:17, Elan Ruusamäe wrote: On 03.05.2016 23:59, Arkadiusz Miśkiewicz wrote: What's the rebuild procedure in case of openssl bump after this change? python2 fixed, python3 looks like broken due other reasons, fails with install even without tests. That could be because of the recent changes to python3.spec by Jan, which I knew they are breaking something, but I couldn't tell what. Does python3.spec build with older python3? Jacek ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: python rebuild procedure?
On 03.05.2016 23:59, Arkadiusz Miśkiewicz wrote: What's the rebuild procedure in case of openssl bump after this change? python2 fixed, python3 looks like broken due other reasons, fails with install even without tests. -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: python rebuild procedure?
not sure, maybe the strict dep can be dropped as last time it was due broken openssl build breaking sslv2 symbols. but i'd rather keep it strict dep, as it has been broken several times in the past if openssl was upgraded because rpm doesn't support forward library dependencies. i.e if python was compiled with openssl 1.0.0 being installed at compile time then having the same old python installed but openssl upgraded to 1.1.1 installed will still work, but not opposite way. or something like such scenario. somebody suggested to add version map to openssl like debian does, but that was just left as the discussion, nothing actually implemented. the threads are several years old so it takes time to find those. On 03.05.2016 23:59, Arkadiusz Miśkiewicz wrote: What's the rebuild procedure in case of openssl bump after this change? commit 9a0fad23f3d83106291fc38815d3fa40a2063ee7 Author: Elan Ruusamäe Date: Fri Mar 4 10:10:31 2016 +0200 openssl 1.0.2g rebuild, strict openssl version dep See recent openssh/python/python3 build logs. -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
python rebuild procedure?
What's the rebuild procedure in case of openssl bump after this change? commit 9a0fad23f3d83106291fc38815d3fa40a2063ee7 Author: Elan Ruusamäe Date: Fri Mar 4 10:10:31 2016 +0200 openssl 1.0.2g rebuild, strict openssl version dep See recent openssh/python/python3 build logs. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
