Re: [Python-modules-team] pygame 1.9.3 upload (was: Re: pygame_1.9.3+dfsg-1_source.changes REJECTED)

2017-01-27 Thread Dominik George 
On Fri, Jan 27, 2017 at 01:32:59AM -0800, Vincent Cheng wrote:
> (please keep the team's mailing list cc-ed)

I bounced the mail there right after I sent it…

> Do you know whether pygame 1.9.3 introduces any backwards-incompatible
> API changes?

Now that's about being a dependency, not being a reverse dependency, as
you said before ;).

And no, both 1.9.2 and 1.9.3 are pure bugfix releases.

> If yes, we would want to treat this like any other
> library transition, i.e. defer it until the next stable release. What
> I want to avoid at this point is to be uploading library packages that
> break its reverse dependencies/build-dependencies and causes a bunch
> of new RC bugs. Have you had a chance to verify at least some of the
> packages listed below to see if they would be negatively affected by
> this upload?
> 
> […]

Yes, I actually did that, as well as some other pygame projects not in
Debian to verify.

Cheers,
Nik

-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296

Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Mobile: +49-1520-1981389 · https://www.dominik-george.de/

Teckids e.V. · FrOSCon e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Maintainer

LPIC-3 Linux Enterprise Professional (Security)


signature.asc
Description: PGP signature
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] pygame 1.9.3 upload (was: Re: pygame_1.9.3+dfsg-1_source.changes REJECTED)

2017-01-27 Thread Vincent Cheng 
On Fri, Jan 27, 2017 at 1:29 AM, Dominik George  wrote:
>> Well, I do have a sponsor, but apparently, he failed to correctly
>> re-sign my prepared files yesterday ;). Will get him to re-upload
>> today.
>
> Oh, and then it was refused again because of the -doc package… now
> seriously, what's the use of *that* policy (source only uploads not
> allowed to NEW)?

Any newly added binary package will cause your package to land in the
NEW queue (regardless of whether the source package itself is new or
not). Source only uploads to NEW aren't allowed likely because it
prevents the ftpmasters from being able to check the newly introduced
binary packages for whatever criteria they have to accept/reject
packages.

Regards,
Vincent

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] pygame 1.9.3 upload (was: Re: pygame_1.9.3+dfsg-1_source.changes REJECTED)

2017-01-27 Thread Dominik George 
> Well, I do have a sponsor, but apparently, he failed to correctly
> re-sign my prepared files yesterday ;). Will get him to re-upload
> today.

Oh, and then it was refused again because of the -doc package… now
seriously, what's the use of *that* policy (source only uploads not
allowed to NEW)?

-nik

-- 
PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17  FD26 B79A 3C16 A0C4 F296

Dominik George · Hundeshagenstr. 26 · 53225 Bonn
Mobile: +49-1520-1981389 · https://www.dominik-george.de/

Teckids e.V. · FrOSCon e.V.
Fellowship of the FSFE · Piratenpartei Deutschland
Opencaching Deutschland e.V. · Debian Maintainer

LPIC-3 Linux Enterprise Professional (Security)


signature.asc
Description: PGP signature
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] pygame 1.9.3 upload (was: Re: pygame_1.9.3+dfsg-1_source.changes REJECTED)

2017-01-27 Thread Dominik George 
Hi,

>Thanks for preparing an update for pygame!
>
>I haven't yet had a chance to take a close look at your changes, but
>just from skimming your changelog, I have a few comments. Have you had
>a chance to send your newly added patches upstream?

Not yet, but I will.

> Also, would you consider targeting experimental?

No, for various reasons...

> I don't
>think now is an appropriate time to attempt to push packages into
>unstable/testing, especially since pygame is a reverse-dep for many
>other packages.

Hmm... So, I see no issues with that. Dependencies haven't changed (apart from 
sphinx and the font package), the python3 package has the same dependencies as 
the python2 package, and I don't see how it would impact other packages badly.

I was reminded of pygame being old and not having a python3 package yesterday, 
and as I said on IRC, rumour has it the release team might with a very small 
chance let it through.

Pygame is a very important package in education, for example at Teckids, so I 
wanted to at least try.

Again, I do not see negative influence, whether it migrates or not.

>Unless you already have a sponsor, I can take a closer look and
>sponsor your package if you'd like?

Well, I do have a sponsor, but apparently, he failed to correctly re-sign my 
prepared files yesterday ;). Will get him to re-upload today.

I do think the changes really make the package fit for sid or even stable.

Cheers,
Nik

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Re: [Python-modules-team] pygame 1.9.3 upload (was: Re: pygame_1.9.3+dfsg-1_source.changes REJECTED)

2017-01-27 Thread Vincent Cheng 
(please keep the team's mailing list cc-ed)

On Fri, Jan 27, 2017 at 1:20 AM, Dominik George  wrote:

>> Also, would you consider targeting experimental?
>
> No, for various reasons...
>
>> I don't
>>think now is an appropriate time to attempt to push packages into
>>unstable/testing, especially since pygame is a reverse-dep for many
>>other packages.
>
> Hmm... So, I see no issues with that. Dependencies haven't changed (apart 
> from sphinx and the font package), the python3 package has the same 
> dependencies as the python2 package, and I don't see how it would impact 
> other packages badly.

Do you know whether pygame 1.9.3 introduces any backwards-incompatible
API changes? If yes, we would want to treat this like any other
library transition, i.e. defer it until the next stable release. What
I want to avoid at this point is to be uploading library packages that
break its reverse dependencies/build-dependencies and causes a bunch
of new RC bugs. Have you had a chance to verify at least some of the
packages listed below to see if they would be negatively affected by
this upload?

$ ssh mirror.ftp-master.debian.org dak rm -s testing -Rn pygame
Authenticated to mirror.ftp-master.debian.org ([5.153.231.11]:22).
Will remove the following packages from testing:

pygame | 1.9.1release+dfsg-10 | source
python-pygame | 1.9.1release+dfsg-10+b1 | mips64el
python-pygame | 1.9.1release+dfsg-10+b2 | amd64, arm64, armel, armhf,
i386, mips, mipsel, ppc64el, s390x

Maintainer: Debian Python Modules Team


--- Reason ---

--

Checking reverse dependencies...
# Broken Depends:
angrydd: angrydd
ardentryst: ardentryst
bambam: bambam
bouncy: bouncy
bubbros: bubbros
childsplay: childsplay
ffrenzy: ffrenzy
fofix-dfsg: fofix
freealchemist: freealchemist
freevial: freevial
fretsonfire: fretsonfire-game
funnyboat: funnyboat
impressive: impressive
kivy: python-kivy
krank: krank
lightyears: lightyears
magicor: magicor
monsterz: monsterz-data
oneisenough: oneisenough
opensesame: opensesame
pathological: pathological
pydxcluster: pydxcluster
pykaraoke: pykaraoke
   pykaraoke-bin
   python-pykaraoke
pyntor: pyntor
pyracerz: pyracerz
pyscrabble: pyscrabble
pysiogame: pysiogame
pysolfc: pysolfc
pysycache: pysycache
python-elements: python-elements
python-expyriment: python-expyriment
pyvnc2swf: pyvnc2swf
seahorse-adventures: seahorse-adventures
singularity: singularity
snowballz: snowballz
solarwolf: solarwolf
sugar-physics-activity: sugar-physics-activity
sugar-pippy-activity: sugar-pippy-activity
whichwayisup: whichwayisup

# Broken Build-Depends:
angrydd: python-pygame
bouncy: python-pygame
funnyboat: python-pygame
impressive: python-pygame
oggvideotools: python-pygame
opensesame: python-pygame (>= 1.8.1~)
pathological: python-pygame
psychopy: python-pygame
pykaraoke: python-pygame
python-expyriment: python-pygame (>= 1.9.1~)
seahorse-adventures: python-pygame
visionegg: python-pygame
whichwayisup: python-pygame

Dependency problem found.

Regards,
Vincent

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] pygame 1.9.3 upload (was: Re: pygame_1.9.3+dfsg-1_source.changes REJECTED)

2017-01-27 Thread Vincent Cheng 
Hi Dominik,

On Thu, Jan 26, 2017 at 4:33 PM, Debian FTP Masters
 wrote:
>
>
> Source-only uploads to NEW are not allowed.
>
> binary:python-pygame-doc is NEW.

Thanks for preparing an update for pygame!

I haven't yet had a chance to take a close look at your changes, but
just from skimming your changelog, I have a few comments. Have you had
a chance to send your newly added patches upstream? I'm mostly
concerned about the patch you added to fix various spelling issues;
it's bound to eventually become a maintenance burden if not
upstreamed. Also, would you consider targeting experimental? I don't
think now is an appropriate time to attempt to push packages into
unstable/testing, especially since pygame is a reverse-dep for many
other packages.

Unless you already have a sponsor, I can take a closer look and
sponsor your package if you'd like?

Regards,
Vincent

___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team