[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#902582: marked as done ((some kind of) transition: add python3.7 as a supported python3 version)

Your message dated Tue, 6 Nov 2018 15:50:09 +0100
with message-id <90bc9f97-be25-aa1e-5242-753d308c847e@debian.org>
and subject line Re: Bug#902582: (some kind of) transition: add python3.7 as a supported python3 version
has caused the Debian Bug report #902582,
regarding (some kind of) transition: add python3.7 as a supported python3 version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
902582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902582
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
Please setup a tracker to add python3.7 as a supported python3 version. This is non-blocking, as packages can migrate on their own once built. 

is_affected = .build-depends ~ /python3-all-dev/;
is_good = .depends ~ /python3 \(<< 3\.8\)/ | .depends ~ /python3.7/;
is_bad = .depends ~ /python3 \(<< 3\.7\)/ | .breaks ~ /python \(>= 3\.7\)/;

--- End Message ---
--- Begin Message --- 
On 28/10/2018 17:44, Mattia Rizzolo wrote:
> Hi!
> 
> On Sat, Jul 07, 2018 at 11:33:13AM +0200, Emilio Pozuelo Monfort wrote:
>> On 28/06/18 08:48, Matthias Klose wrote:
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian.org@packages.debian.org
>>> Usertags: transition
>>>
>>> Please setup a tracker to add python3.7 as a supported python3 version. This is
>>> non-blocking, as packages can migrate on their own once built.
>>
>> This is ongoing. Rebuilds are done for levels 1-6, but there are several build
>> problems. The most important one seems to be cython, which is blocking several
>> other packages.
> 
> I think we should be good with this.
> This morning a blocking python3.7 migrated, which was IMHO the biggest
> blocker these last days.
> 
> Looking at the transition tracker, removing the partial, unknwon, and
> the not-in-testing packages, the red lines are:
> 
>  * boost1.62
>    + I haven't investigated this one package, tbh.
>  * libprelude
>    + NMUed, will be good in 2 days
>  * sphinxbase
>    + I don't understand this one: only on mips64el it builds against
>      py3.6 only, despite everything looking good otherwise.  I would be
>      glad if somebody else looked at this one

I did, see #903698.

>  * libarcus, libsavitar
>    + false positives: they build only for the default version but
>      build-depend on py3-all-dev (bugs filed…)
>  * basemap
>    + NMUed, will be good in 2 days if the maintainer doesn't push back
>  * pygame
>    + fix uploaded earlier today, builds ongoing
>  * python-tinycss
>    + RC bug, pending removal from testing (or somebody to fix it)
>  * amp
>    + fix uploaded earlier today, builds ongoing
>  * imexam
>    + rebuild FTBFS in s390x only, RC bug filed, pending removal from testing
> 
> 
> So I'd say we are pretty good.
> IMHO, once all the above are taken care of, this bug can be closed.  In

Yeah, let's close this now.

> the meantime, I would love if doko could run rebuilds like he did for
> py3.7-supported for py3.7-default, and file bugs.

Yeah, that'd be good to have on a new transition bug for python3.7-as-default.

Cheers,
Emilio

--- End Message ---
Reply to: