Re: Packages FTBFS with Python 3.6

On Tue, Jan 17, 2017 at 08:14:36PM +, Zbigniew Jędrzejewski-Szmek wrote: > On Tue, Jan 17, 2017 at 08:29:16AM -0700, Jerry James wrote: > > On Tue, Jan 17, 2017 at 7:08 AM, Zbigniew Jędrzejewski-Szmek > > wrote: > > > On Mon, Jan 16, 2017 at 10:27:19PM -0800, Adam

Re: Packages FTBFS with Python 3.6

On Tue, Jan 17, 2017 at 08:29:16AM -0700, Jerry James wrote: > On Tue, Jan 17, 2017 at 7:08 AM, Zbigniew Jędrzejewski-Szmek > wrote: > > On Mon, Jan 16, 2017 at 10:27:19PM -0800, Adam Williamson wrote: > >> On Tue, 2017-01-17 at 05:33 +, Zbigniew Jędrzejewski-Szmek wrote: >

Re: Packages FTBFS with Python 3.6

On Mon, Jan 16, 2017 at 10:27:19PM -0800, Adam Williamson wrote: > On Tue, 2017-01-17 at 05:33 +, Zbigniew Jędrzejewski-Szmek wrote: > > On Tue, Jan 17, 2017 at 05:29:35AM +, Zbigniew Jędrzejewski-Szmek wrote: > > > On Wed, Jan 11, 2017 at 04:28:18AM +, Zbigniew Jędrzejewski-Szmek > >

Re: Packages FTBFS with Python 3.6

On Wed, Jan 11, 2017 at 04:28:18AM +, Zbigniew Jędrzejewski-Szmek wrote: > > python3-sympy-0:1.0-3.fc25.noarch > Pfff, it still fails in the test suite :( I'm chipping away at this one. There are some failing python2 tests which I had to disable, but it seems that things are mostly with

Re: Packages FTBFS with Python 3.6

On Wed, Jan 11, 2017 at 03:58:18AM +, Zbigniew Jędrzejewski-Szmek wrote: > On Wed, Jan 11, 2017 at 03:38:59AM +, Zbigniew Jędrzejewski-Szmek wrote: > > PS. What's the status of the python3.6 rebuild? Can somebody post > > a list of work-needing packages? > > I guess that the right

Re: Packages FTBFS with Python 3.6

On Wed, Jan 11, 2017 at 03:38:59AM +, Zbigniew Jędrzejewski-Szmek wrote: > PS. What's the status of the python3.6 rebuild? Can somebody post > a list of work-needing packages? I guess that the right invocation: $ dnf repoquery --whatrequires 'python(abi) = 3.5'

Re: Packages FTBFS with Python 3.6

On Wed, Dec 21, 2016 at 12:18 AM, Miro Hrončok wrote: > Hi all, > We've recently tried to rebuild all Python packages with Python 3.6. > However, we currently have bunch of packages that simply fail to build. > > As the list contains >200 packages, it would be very helpful,

Re: Packages FTBFS with Python 3.6

On 21.12.2016 00:18, Miro Hrončok wrote: Hi all, We've recently tried to rebuild all Python packages with Python 3.6. However, we currently have bunch of packages that simply fail to build. As the list contains >200 packages, it would be very helpful, if you (package maintainers) could help us

Re: Packages FTBFS with Python 3.6

On 21.12.2016 14:52, Zdenek Dohnal wrote: On 12/21/2016 02:39 PM, Miro Hrončok wrote: On 21.12.2016 14:11, Zdenek Dohnal wrote: I think I encountered same issue with libpython3.5m.so.1.0: Example: Error: nothing provides libpython3.5m.so.1.0 needed by python3-cups-1.9.72-9.fc25.i686. nothing

Re: Packages FTBFS with Python 3.6

On 21.12.2016 14:11, Zdenek Dohnal wrote: I think I encountered same issue with libpython3.5m.so.1.0: Example: Error: nothing provides libpython3.5m.so.1.0 needed by python3-cups-1.9.72-9.fc25.i686. nothing provides libpython3.5m.so.1.0 needed by unbound-libs-1.5.10-1.fc26.i686 Translates

Re: Packages FTBFS with Python 3.6

On 21.12.2016 09:53, Richard W.M. Jones wrote: On Wed, Dec 21, 2016 at 12:18:47AM +0100, Miro Hrončok wrote: libguestfs As should be obvious from the (multiple) build failures when you've been trying to build it over the past few days, this fails because of: DEBUG util.py:426: Error:

Re: Packages FTBFS with Python 3.6

On 21.12.2016 07:41, Pavel Raiskup wrote: On Wednesday, December 21, 2016 12:18:47 AM CET Miro Hrončok wrote: Hi all, We've recently tried to rebuild all Python packages with Python 3.6. However, we currently have bunch of packages that simply fail to build. ... Everything currently happens in

Packages FTBFS with Python 3.6

Hi all, We've recently tried to rebuild all Python packages with Python 3.6. However, we currently have bunch of packages that simply fail to build. As the list contains >200 packages, it would be very helpful, if you (package maintainers) could help us solve the issues, as we cannot go one