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
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
>
> 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)?
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
(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
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
6 matches
Mail list logo