Re: Joining the team
On Sat, 2017-05-20 at 17:40 +0200, sab wrote: > > On 07/05/2017 17:30, sab wrote: > > > > On 06/05/2017 17:14, Piotr Ożarowski wrote: > > > [sab, 2017-05-06] > > > > 'https://anonscm.debian.org/git/python-modules/packages/python-zxcvbn.git/': > > > > > > > git+ssh://git.debian.org/git/python-modules/packages/python-zxcvbn.git > > Thanks > > I have pushed on > > git+ssh://anonscm.debian.org/git/python-modules/packages/python-zxcvbn.git/ > > for all branches. > > Now who sponsors the changes? > > Regards, > > Sabino > > > > Hi! > How do I make package accepted into experimental? > https://anonscm.debian.org/cgit/python-modules/packages/python-zxcvbn.git/ > Regards, > Sabino You need to request sponsorship for uploading your package [1]. Then, an interested sponsor should review your packaging and may ask for further improvement to it prior to the upload. [1] https://mentors.debian.net/sponsor/rfs-howto Ghis
Re: Joining the team
On 07/05/2017 17:30, sab wrote: On 06/05/2017 17:14, Piotr Ożarowski wrote: [sab, 2017-05-06] 'https://anonscm.debian.org/git/python-modules/packages/python-zxcvbn.git/': git+ssh://git.debian.org/git/python-modules/packages/python-zxcvbn.git Thanks I have pushed on git+ssh://anonscm.debian.org/git/python-modules/packages/python-zxcvbn.git/ for all branches. Now who sponsors the changes? Regards, Sabino Hi! How do I make package accepted into experimental? https://anonscm.debian.org/cgit/python-modules/packages/python-zxcvbn.git/ Regards, Sabino
No longer uploading mercurial
Hi, I have been uploading mercurial for some years, but since November I'm struggling to find time to work on the package. I don't think I will have time to keep up with mercurial's release schedule when stretch is released. Cheers, Javi signature.asc Description: PGP signature
Re: avoiding regressions with python3-all-dev in between transitions?
Steve Langasek writes: > As with every recent transition, we are finding a number of packages that > have wrong build-dependencies on python3-all-dev despite having no support > in the packaging for multiple versions. Some of these packages just > continue to build for the default version, and some of them fail to build. I suspect a related issue is packages that build fine, but the tests don't actually run tests against all python versions. For example, python-django-jsonfield has in debian/rules: override_dh_auto_test: python2 debian/run_tests.py python3 debian/run_tests.py Wonder how many other packages are similar. This particular case looks like it was my fault :-( - from a change made in 2014. It is possible I used the same pattern in other packages, although I can't find anything else right now (not counting a package not in Debian) - from a quick scan of all my */debian/rules files on my system - which I think includes all packages I have ever touched. -- Brian May
