Joining Python Applications Packaging Team
Hello, I am a python developer interested in packaging my application WereSync (https://github.com/DonyorM/weresync) for Debian and would like to join the PAPT in doing this. My username on Alioth is: donyorm-guest. I have read the policy guide for both PAPT and DPMT and agree with them. Sincerely, Daniel Manila
Re: upstream release of unreleased package
On 10/2/19 21:37, Brian May wrote: This is your first error. Changes to debian/* files belong to the debian/master branch, not the patch-queue/debian/master branch. So you should be finalise the changes to the patch-queue first, then run something like "gbp pq export" which will switch back the the debian/master branch, then you can make changes to the debian/* files. Sorry, I don't have time to try to explain how to fix this right now :-( Thanks for the information. Now I understand better the problem.
Re: python-numeric: Fails to build 2.3 version
On Wednesday 22 November 2006 21:32 pm, Raphael Hertzog wrote: > > As the subject says, if I build python-numeric under pbuilder, the > > resulting package has no contents for python2.3, nor any Provides of > > python2.3-numeric. > > This is the normal behaviour of the package since in sid python2.3 is no > more marked as supported in /usr/share/python/debian_defaults ... It seems to me that it's a bad idea to make this change in sid while the old python packages are frozen in etch. The result will be: if anybody uploads updated versions of their python packages, they will get autobuilt against the sid packages and thus have no 2.3 contact, which is out of sync with what would happen with people wanting to hand-build their packages locally using etch. I think you should decide whether you want python2.3 to be supported in etch or not. If you do, you should revert the changes in sid until after the etch release; if you don't, you need to ask the release team to let the new python packages into etch despite the freeze of "base toolchain" packages, and also prepare a list of appropriate binNMU's needed to sync up the packages in sid with this change. I'm Cc'ing debian-release to get their opinion on this issue (since I don't see any discussion on this in a quick search of the list archives for the last month). -- Daniel Schepler Content analysis details:(-4.4 points, 5.0 required) pts rule name description -- -- -1.8 ALL_TRUSTEDPassed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.]
Re: python-numeric: Fails to build 2.3 version
On Thursday 30 November 2006 15:35 pm, Raphael Hertzog wrote: > Hi, > > On Thu, 30 Nov 2006, Daniel Schepler wrote: > > > This is the normal behaviour of the package since in sid python2.3 is > > > no more marked as supported in /usr/share/python/debian_defaults ... > > > > It seems to me that it's a bad idea to make this change in sid while the > > old python packages are frozen in etch. The result will be: if anybody > > uploads updated versions of their python packages, they will get > > autobuilt against the sid packages and thus have no 2.3 contact, which is > > out of sync with what would happen with people wanting to hand-build > > their packages locally using etch. > > And how is this a problem ? It's not technical problem... it's at most a > problem of consistency in the packages built, some will provide support > for 2.3 and 2.4 while other will only support 2.4. What if a new upload has reverse deps which still have a 2.3 version, which then becomes unusable? And anyway, reproducibility of package builds is important, while the current situation results in significantly different packages depending on whether sid or etch is used to build, and furthermore depending on when exactly the buildd's last built the arch-dependent packages. > Matthias's goal has always been to get rid of python2.3 completely. It's > likely doable. And I discussed on #debian-release their move to etch, it > will likely happen soon (after my recent NMUs which fixed some issues > related to that change). OK, it's good to know the release team already knew about this. The main reason for my mail was to make sure they did know about it, and as I said I had found no evidence to indicate that was the case. -- Daniel Schepler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: json-py (updated package)
Dear mentors and Pythonistas, I am looking for a sponsor for the new version 3.4-4 of my package "json-py". It builds these binary packages: python-json - a JSON (http://json.org) reader and writer in Python The package appears to be lintian clean. The upload would fix these bugs: 493796 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/j/json-py - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/j/json-py/json-py_3.4-4.dsc I would be glad if someone uploaded this package for me. Kind regards, -- Daniel Watkins (Odd_Bloke) signature.asc Description: PGP signature
Re: RFS: json-py (updated package)
Hi Piotr, On Fri, 22 Aug 2008 00:27:32 +0200 Piotr Ożarowski <[EMAIL PROTECTED]> wrote: > [Daniel Watkins, 2008-08-21] > > I am looking for a sponsor for the new version 3.4-4 > > of my package "json-py". > > uploaded. Please contact release managers about unblocking it > (note that -3 didn't propagate to testing) Thanks for your sponsorship (once again). I'm not totally convinced that it is worth requesting a freeze exception (which I assume is what you're talking about) as the changes between -2 and -4 are almost entirely concerned with the packaging (there are no modifications to the functionality of the installed package) and no bugs have been closed by -3 or -4 (with the exception of the adoption bug). If, however, you think there would be value, I would be more than happy to defer to the greater experience and go ahead and request the exception. Regards, -- Daniel Watkins (Odd_Bloke) signature.asc Description: PGP signature
RFS: configobj (updated package)
Dear mentors, I am looking for a sponsor for the new version 4.5.3-1 of my package "configobj". It builds these binary packages: python-configobj - a simple but powerful config file reader and writer for Python The package appears to be lintian clean. The upload would fix these bugs: 493792 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/c/configobj - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/c/configobj/configobj_4.5.3-1.dsc I would be glad if someone uploaded this package for me. Regards, -- Daniel Watkins (Odd_Bloke) signature.asc Description: PGP signature
RFS: gwibber
Dear mentors and Pythonistas, I am looking for a sponsor for my package "gwibber". * Package name: gwibber Version : 0.1~bzr102-1 Upstream Author : Ryan Paul <[EMAIL PROTECTED]> * URL : https://launchpad.net/gwibber * License : GPL Section : misc It builds these binary packages: gwibber- microblogging client for GNOME The package appears to be lintian clean. The upload would fix these bugs: 496326 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/gwibber - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/gwibber/gwibber_0.1~bzr102-1.dsc I would be glad if someone uploaded this package for me. Regards, -- Daniel Watkins (Odd_Bloke) signature.asc Description: PGP signature
Re: RFS: gwibber
Hi Piotr, On Wed, 3 Sep 2008 01:20:17 +0200 Piotr Ożarowski <[EMAIL PROTECTED]> wrote: > [I just took a quick look at the package, I'm still on VAC] Thanks! I've realised that I shouldn't have requested sponsorship for this yet, because one of its dependencies is still an ITP. I'm chasing that up, and will include the changes mentioned below in the package for which I eventually seek sponsorship. > [Daniel Watkins, 2008-09-02 23:08] > > I am looking for a sponsor for my package "gwibber". > > PAPT is in Uploaders so you can add the package to our TODO list[1] > and/or ping us on #debian-python Will do, as per above. > from homepage: > | Please note that this is pre-alpha software > > are you sure you want to upload it to unstable? How about > experimental? Well, I've been using it regularly without issue, so I'd have no qualms about it going into unstable. > Did you contact Jorge and ask him about co-maintaining this package? I did not. Jorge contacted me, having seen my ITP. His intent is to derive the Ubuntu packaging in future from the Debian packaging. > Vcs-* fields are missing, python2.5 is hardcoded in debian/control > (you probably want "python (>= 2.5)") Fixed. Dan -- Daniel Watkins (Odd_Bloke) signature.asc Description: PGP signature
Re: intent to hijack turbogears 2 (and some of its friends)
Stefano Zacchiroli wrote: > Given that the maintainer (Cc-ed) has not replied to any of the above > bug reports---the latter is 7-month old---I'm hereby notifying my > intention to hijack both turbogears 2 and turbojson. as stated in the wnpp bug when i took over, my only interest in turbogears is that a) it doesn't get away (and that quickly >= 1.0.7 got available), and b) openerp-web-client uses it. now that openerp-web-client will get ported away from turbogears 1.x to cherrypy-only, it's not on my priority list anymore. therefore, please take over the packages. Regards, Daniel -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@panthera-systems.net Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Didjvu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi guys, I am working on packaging Jakub Wilks's Didjvu. That is a smart little DjVu encoder employing the Gamera framework (python-gamera) for automatic foreground mask generation which drastically improves the workflow towards document scanning / creating of ebooks (cf. bug #601781). I am beginning maintainer / Debian Python packager so I would be thankful for any pointers. I've read towards RFA Python modules that they "have to stay under the DPMT umbrella for at least 12 months". What does that mean? Greetings, Daniel Stender https://alioth.debian.org/users/danstender-guest/ http://www.danielstender.com/granthinam/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzK/CoACgkQU8fCMhZUvZysTQCfXciLV0BJqYRZjleCijr6uHM+ LqcAoMGBWTI6EsvXVjCeqK9XTX4B9Spl =nADH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ccafc2a.7020...@danielstender.com
RFS: Didjvu, Djvusmooth, Ocrodjvu, Pybtex
Hi people, I'm kindly asking for overchecking/uploading of the following packages: /python-apps/packages/didjvu/tags/0.2.1-1/ initial release of 0.2.1 /python-apps/packages/djvusmooth/tags/0.2.8-2/ /python-apps/packages/ocrodjvu/tags/0.4.6-3 closes important bug #600539 in testing /python-apps/packages/pybtex/tags/0.14.1-1 new upstream release All packages are lintian clean. Thank you very much in advance, Daniel Stender -- http://www.danielstender.com/granthinam/ GPG key ID: 1654BD9C -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd442c6.50...@danielstender.com
Re: RFS: Didjvu, Djvusmooth, Ocrodjvu, Pybtex
Thanks Stefano for checking the packets and for the precious pointers (for most
of the issues it's
hard to find comprehensive documentation).
On 05.11.2010 20:46, Stefano Rivera wrote:
> As a not-yet-DD I can't upload, but here's a review.
>
> First, we don't tag releases until they are uploaded. You can leave the
> changelog entry as UNRELEASED, and the sponsor will fix that and tag on
> upload.
I was following maint-guide 4.3 with that: "distribution should be either
unstable (or even
experimental) [16]" - but I was wondering about this anyway. Thanks for the
pointer! I've fixed that
for all packages.
>> /python-apps/packages/didjvu/tags/0.2.1-1/ initial release of 0.2.1
>> Depends: ${misc:Depends}, ${python:Depends}, python-imaging, libdjvulibre21
>> (>= 3.5.21), python-argparse
>
> I'd suggest wrapping that (after every comma is quite neat).
>
> argparse is part of the standard library in Python 2.7. A dependency on
> python (>= 2.7) | python-argparse is probably preferable.
Allright.
> The description could probably be broken into a couple of shorter
> paragraphs.
Mhmm, too long? o.k.
> debian/copyright mentions jwilk, but not you. You should state the
> licencing of your packaging.
Didn't get it. It says: "This work was packaged for Debian by Daniel Stender"
and also states the
license of both the upstream and the packet. I was following again maint-guide
(5.2) with details.
> Also, you BD on debhelper >= 7, but use an override, which requires
> debhelper >= 7.0.50~.
Fixed.
> debian/rules: Not a fan of dh $...@?
> I'm guessing you misunderstood my message on this topic, as you are
> totally avoiding the setup.py and using dh_install + dh_link to install
> files.
> I think the following debian/rules will do what you want (and you won't
> need debian/install or debian/links any more):
>
>
> #!/usr/bin/make -f
> %:
> dh $@
>
> override_dh_auto_install:
> dh_auto_install -- --install-lib /usr/share/didjvu
>
Yes, great! I've got problems with "dh $@" that without the lib path the
modules were considered to
be public, now it works. But without my links the executeable resides in
/usr/share/bin, isn't that
substandard?
> For new packages, you should probably consider using dh_python2 instead
> of python-support. The eventual plan is to migrate all Python packages
> to it.
Yes definitely. I've followed Piotr's presentation at debconf 2010 on this. I
would like to to put
that on the agenda for further work on that.
>> /python-apps/packages/djvusmooth/tags/0.2.8-2/
> Predates you, but "djvusmooth is a graphical editor for DjVu
> files, which allows to:" isn't correct English grammar. ..."which allows
> one to" would be better.
Fixed.
> You probably want to add yourself to debian/copyright (even if you
> haven't made any significant modifications yet). This applies to all the
> packages.
Ah yes sure ... just overseen it. Fixed everywhere.
>> /python-apps/packages/ocrodjvu/tags/0.4.6-3 closes important bug
>> #600539 in testing
> My previous argparse comment still applies, but this is aimed at squeeze
> which doesn't have python2.7, so you don't need to do this yet (but
> consider it for the trunk, please).
Allright.
>> /python-apps/packages/pybtex/tags/0.14.1-1 new upstream release
> I see some trailing whitespace in debian/changelog.
> Mixed tabs and spaces in debian/postinst (naughty jwilk)
All fixed and refreshed (so, everything else seem to be alright I'll guess).
Please, one more towards the procedure of updated already tagged stuff: svn
commit or again
debcommit? Then svn copy /trunk /tags/0.2.1-1?
Greetings,
Daniel Stender
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cd52422.2000...@danielstender.com
Re: RFS: Didjvu, Djvusmooth, Ocrodjvu, Pybtex
All refreshed. How do I update tags? Svn copy (/trunk /tags/foo) says "permission denied". Thanks for all pointers, Daniel Stender On 06.11.2010 11:15, Stefano Rivera wrote: > Hi Daniel (2010.11.06_11:47:14_+0200) >>> argparse is part of the standard library in Python 2.7. A dependency on >>> python (>= 2.7) | python-argparse is probably preferable. >> >> Allright. > > I suppose that's not necessary, Jakub had a good point that python will > probably provide python-argparse when 2.7 is the default version. That > appears to be how previous transitions (without renames) into the stdlib > were handled. > >> Didn't get it. It says: "This work was packaged for Debian by Daniel >> Stender" and also states the >> license of both the upstream and the packet. I was following again >> maint-guide (5.2) with details. > > I'm saying you should add something like: > | The Debian packaging is (C) 2010, Daniel Stender > | and is licensed under the GPL v2, see above > or use DEP-5, with a "Files: debian/*" section. Your Licence block looks > like it was copied from another debian/copyright file that used DEP5. > http://dep.debian.net/deps/dep5/ > >> Yes, great! I've got problems with "dh $@" that without the lib path >> the modules were considered to be public, now it works. > > Well, it installs, as Jakub also pointed out, you'll need a patch or > your own wrapper to get Python to find the private module. > >> But without my links the executeable resides in /usr/share/bin, isn't >> that substandard? > > Hmm, I don't see that, but you haven't committed your changes to the > repo yet, so I can't look at the code you are working with. > >> Please, one more towards the procedure of updated already tagged stuff: svn >> commit or again >> debcommit? Then svn copy /trunk /tags/0.2.1-1? > > I debcommit when I've made changes to debian/changelog (i.e. when I > first make a change). If I have to go back and fix something which > hasn't been published yet, then there won't be a changelog entry, so I > have to provide my own commit message with svn commit. > > SR -- http://www.danielstender.com/granthinam/ GPG key ID: 1654BD9C -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cd54a6f.6060...@danielstender.com
Re: RFS: Didjvu, Djvusmooth, Ocrodjvu, Pybtex
Another problem:
To give "XS-Python-Version: >= 2.6" together with "${misc:Depends},
${python:Depends}, python (>=
2.7) | python-argparse" in debian/control results in an INFO file in the
deb-packet which contains:
"Depends: python (>= 2.6), python (>= 2.7) | python-argparse"
On 06.11.2010 14:16, Stefano Rivera wrote:
> Hi debian-python (2010.11.06_12:15:18_+0200)
>> Well, it installs, as Jakub also pointed out, you'll need a patch or
>> your own wrapper to get Python to find the private module.
>
> Or the obvious solution, your previous one (and the one used by
> the other packages in this set), to use a symlink to the wrapper, which
> you put in /usr/share/didjvu.
>
> didjvu is missing a dependency on python-gamera.
>
>> Files: debian/*
>> -Copyright: 2009, 2010 Jakub Wilk
>> +Copyright: 2010 Daniel Stender
>
> I don't think you should forget Jakub, just add yourself.
>
> Otherwise no issues I can see.
>
> SR
--
http://www.danielstender.com/granthinam/
GPG key ID: 1654BD9C
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cd58899.3020...@danielstender.com
Re: Debhelper: LDFLAGS
... ups, misleaded. Please excuse. On 19.12.2010 21:04, Daniel Stender wrote: >> If we are still talking about the gummi package, I just put >> >> export LDFLAGS=-Wl,--as-needed >> >> at top of debian/rules and the dpkg-shlibdeps warnings went away. > > ... does it? What I am missing here? > > Dan -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d0e6627.6020...@danielstender.com
Re: Debhelper: LDFLAGS
> If we are still talking about the gummi package, I just put > > export LDFLAGS=-Wl,--as-needed > > at top of debian/rules and the dpkg-shlibdeps warnings went away. ... does it? What I am missing here? Dan -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d0e6555.5030...@danielstender.com
RFS: didjvu, djvusmooth, pybtex
Hi guys, I would like to refresh the RFS for the following packets: didjvu 0.2.1-1 - initial release djvusmooth 0.2.8-2 - maintainer switch, standards bumped to 3.9.1 pybtex 0.14.1-1 - new upstream release Everything is at: http://svn.debian.org/wsvn/python-apps/packages/ I would say that everything is ready for upload. Towards e-documenting relating Python stuff I am also working on python-djvulibre but that needs some more days. Thanks in advance for any care for & consideration, Daniel Stender -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d2c1d86.3040...@danielstender.com
Re: RFS: didjvu
I've converted didjvu to dh_python2 now, could anybody please check it over again? Any hints welcome! Greetings, Daniel Stender -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d4e7754.3050...@danielstender.com
Re: RFS: didjvu
All right, all fixed. Thanks for checking!
Daniel
On 06.02.2011 14:35, Stefano Rivera wrote:
> Hi Daniel (2011.02.06_12:26:28_+0200)
>> I've converted didjvu to dh_python2 now, could anybody please check it
>> over again? Any hints welcome!
>
> Looks fine. A couple of minor things:
>
> Might as well use X-Python-Version instead of XS, as it's available in
> python 2.6.6-3.
>
> I like using Breaks: ${python:Breaks}. It separates the Python version
> dependencies out of Depends.
>
> The --with should come after $@:
> dh $@ --with python2
>
> The DEP5 copyright file doesn't include a revision in the Format.
>
> SR
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d4ecfd2.9090...@danielstender.com
RFS: pybtex
Hi guys, I would like to refresh my request for sponsorship towards Pybtex 0.15-1 after RFA. Please check it as usual at Alioth: http://svn.debian.org/wsvn/python-apps/packages/pybtex Any review welcome. Sponsors in favour of Python_dh2 as always welcome ;-) (get you chat ready then for a session). Greetings, Daniel Stender -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d7f89d7.90...@danielstender.com
Re: RFS: pybtex
Hi people, I would like to refresh my RFS for Pybtex. Isn't there anybody with a little time ...? Greetings, Daniel Stender On 15.03.2011 16:46, Daniel Stender wrote: > Hi guys, > > I would like to refresh my request for sponsorship towards Pybtex 0.15-1 > after RFA. Please check it > as usual at Alioth: http://svn.debian.org/wsvn/python-apps/packages/pybtex > > Greetings, > Daniel Stender -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dac4d97.50...@danielstender.com
RFS: python-djvu & ocrodjvu
Hi guys, Jakub would like to get rid of the maintenance of these packets, has anybody a couple of minutes and would be so nice to review my latest packings of python-djvulibre (0.3.3-1) and ocrodjvu (0.7.1-1) ... both packets are building fine. Python3-ing the Djvu bindings needs some more time to get deeper into things, I would like to go for that towards 0.3.3-2. Greetings, Daniel Stender -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4de291d7.2010...@danielstender.com
RFS python-markdown 2.1.0
I'd like to help with packaging python-markdown. There's a new upstream, and some lintian warnings. I've built a package following the New Maintainers' guide. Does someone have time to review it and tell me what next steps should be? Changelog: python-markdown (2.1.0-1) unstable; urgency=low * New upstream release * Added support for python -m syntax (upstream; Closes: #579004) * Fix interpreter lines in two extensions (Lintian warnings) * Upstream moved executable to markdown_py (replaces debian rule) -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87r4zp3b3f@wonderlust.lan
RFS: python-ebooklib
Hello, I am a non-DD looking for sponsorship of (or any helpful hints about) my first upload to Debian: http://mentors.debian.net/package/python-ebooklib EbookLib is a Python library for managing EPUB2/EPUB3 and Kindle files. It's capable of reading and writing EPUB files (Kindle support is under development). Upstream homepage is https://github.com/aerkalov/ebooklib I have had some general feedback from the Debian Mentors list and believe the package is now ready for review. I'd be happy to join a packaging team should that be possible. My username on Alioth is dhj-guest, if that helps :-) Thanks! Daniel -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53593d05.7010...@64studio.com
Re: RFS: python-ebooklib
Hi Zygmunt, > I think you are quite welcome to join DPMT > > https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin Thanks, I have sent a request via the web interface. I have also helped upstream create some Sphinx documentation and re-uploaded the package to include it. Cheers! Daniel > On Thu, Apr 24, 2014 at 6:34 PM, Daniel James <mailto:dan...@64studio.com>> wrote: > > Hello, > > I am a non-DD looking for sponsorship of (or any helpful hints about) my > first upload to Debian: > http://mentors.debian.net/package/python-ebooklib > > EbookLib is a Python library for managing EPUB2/EPUB3 and Kindle files. > It's capable of reading and writing EPUB files (Kindle support is under > development). Upstream homepage is https://github.com/aerkalov/ebooklib > > I have had some general feedback from the Debian Mentors list and > believe the package is now ready for review. > > I'd be happy to join a packaging team should that be possible. My > username on Alioth is dhj-guest, if that helps :-) > > Thanks! > > Daniel -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/535a7e23.5010...@64studio.com
Re: RFS: python-ebooklib
Hi Vincent, > Please update Vcs-Svn and Vcs-Browser if you choose to store your > packaging in the team's svn repo, and update the Maintainer field as > well (in d/control). Currently the packaging is in https://github.com/booktype/ebooklib-packaging. If the team SVN is preferred it can be moved there later, no problem. As a non-DD I don't think I can upload to the team repo yet, as my membership application to the team has not been approved (it was only a couple of days ago). > Also, don't hardcode python versions in your package's dependencies > (as mentioned previously on the list [1] Thanks for forwarding that tip, I've made the change and re-uploaded to http://mentors.debian.net/debian/pool/main/p/python-ebooklib/python-ebooklib_0.15-1.dsc > and if you're not > subscribed to the list already, please do so Somehow I missed doing that, I'm subscribed now. Cheers! Daniel -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/535f8938.6040...@64studio.com
Fwd: Re: Bug#756331: RFS: aafigure/0.5-4 [ITA]
Forwarding to the other Debian Python List... Original Message Subject: Re: Bug#756331: RFS: aafigure/0.5-4 [ITA] Date: Mon, 28 Jul 2014 22:52:35 +0100 From: Daniel Lintott To: Breno Leitao , 756...@bugs.debian.org CC: python-modules-t...@lists.alioth.debian.org Hi, I'm not a DD so cannot sponsor your package. I haven't tried to build the package, but a couple of comments. On 28/07/14 21:49, Breno Leitao wrote: > Dear mentors, > > I am looking for a sponsor for my package "aafigure". This is a package that I > want to adopt (under ITA) but I am not a DD, so, I would need a sponsor to > upload this package. > > * Package name: aafigure > Version : 0.5-5 > Upstream Author : orphaned Upstream Author seems to be either aafigure-team or Chris Liechti > * URL : https://launchpad.net/aafigure > * License : specific license at LICENSE.txt That would be a BSD-3-Clause license > Section : python > > It builds those binary packages: > >python-aafigure - ASCII art to image converter > > To access further information about this package, please visit the following > URL: > > http://mentors.debian.net/package/aafigure > > Alternatively, one can download the package with dget using this command: > > dget -x > http://mentors.debian.net/debian/pool/main/a/aafigure/aafigure_0.5-5.dsc > > More information about hello can be obtained from http://www.example.com. > > Changes since the last upload: > > aafigure (0.5-5) unstable; urgency=low > > * Set myself as maintainer (closes: #719549). > * Bump Standards-Version from 3.9.4 to 3.9.5 > * Transition to dh_python2 > >-- Breno Leitao Mon, 28 Jul 2014 19:27:41 + > It seems there is some previous involvement with the Debian Python Modules team, where the packaging exists in SVN. It would probably be a good idea to liaise with them (I'm not a member myself, so don't how the team works). I have added them to the CC. The the mentors page there is one lintian info warning, which is trivial to fix. - vcs-field-not-canonical Regards, Daniel signature.asc Description: OpenPGP digital signature
python3-aiohttp
Hi Guys, I have a package I'm working on which makes use of aiohttp and was wondering what the plans were for the python3-aiohttp package in Debian? I can't find an ITP/RFP bug for the package, but see that there are some files already in SVN. Please cc me in any replies as I'm not subscribed to debian-python. Regards, Daniel signature.asc Description: OpenPGP digital signature
Re: python3-aiohttp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Tianon, On 31 March 2015 16:35:00 BST, Tianon Gravi wrote: >On 31 March 2015 at 07:24, Daniel Lintott wrote: >> I can't find an ITP/RFP bug for the package, but see that there are >some >> files already in SVN. > >I was packaging it originally for something paultag was working on, >but he no longer needed it so I didn't finish (and it felt like a >waste to just purge it completely). > >Piotr recently expressed some interest (on IRC), but I don't think he >took it any further after I offered it to him. I'd reiterate what I >told him though; I'm happy to work on finishing it out more if there's >some interest in it, but I also won't be sad if someone wants to just >take over from me (either using my bits or scrapping them entirely and >starting fresh). I'd point out that it's really close as-is, though. >:) Well the software I'm packaging requires aiohttp so there is definitely interest in having it available in Debian! Personally I don't have time to take the maintenance of aiohttp on myself, so if you're happy to maintain it that would be preferable. - -- Daniel -BEGIN PGP SIGNATURE- iQJOBAEBCAA4MRxEYW5pZWwgTGludG90dCAoZGxpbnRvdHQpIDxkYW5pZWxAc2Vy dmVyYi5jby51az4FAlUbMAsACgkQyHJk111z7G45tg//XHhVI6AN+Yj32YUUxTsD maQXw1ZOPqpGmAL6jFFTaOEvE5ZH+ZwRZbj39n6G4gPjpxvAQXk1CRa5p5NGL+6m cH8G71k999mWJzJZcf7DVP5ORnH0hAEHO7c6DNKXcs7oeP/98QV5+1hFrOZ0TEZt nW7PKMIxNvOlZ/epcEsSsWGMXA4bXvzkDYJBTbVX2hOMMB0kwfs5/FckIpC2lioK 8Y2sX2jIVmVO+o+F9LucHo9okMw/QtydOjfrQrvjwbn1Ckq1fJUNJcqMorjL6dq1 4wVjxyzjHmY/AK5CjOGsliGtOlPOaI/i8eY4fFdrKcyYw1tOt4jWe9/A8FxWnCvW 8bajOu1XH6HFAttO03PQzB/bcgj8O1UmzbU7aTQlu1RhzPRlYreiDu7KGB3P0dC0 uMV7dXaeYCX8z69Fes4rA0ECPhydYS8BPhXfZZKRJcCkTDHf2pvvHRY/WawV+tZC ni9kEQrQx5SnTCMcNWHw3U6JSUf2ItM51lFceGoi9dxmB/6hQXg0EK2rmIzfIp+d 3lB9HHUkGTO3g/GSK7Eonj/gNY0iS4UwMuLyAiLOPgbJV3WqMX32iPBD2xebaXca 19FnFO5sf+4jeD9cdtycZbchocyZo2vwNReIddv9FGGOImeXwNLEcjmVRMaXDcHY onvMYQ0CVozRleufkltVUJY= =PAF+ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1aeb16eb-eb63-4356-8e67-3de737a75...@serverb.co.uk
PAPT: git-multimail packaging
Dear Team, Git-multimail is a post-recieve hook script for git implemented in python 2, and distributed in git/contrib on git.kernel.org I'd like to see git-multimail in debian. There are currently no RFP/ITP ( but there is a wishlist bug against git https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718396 ) I'm not team member neither I have extensive python knowledge, but I've tried to make a package of it which may be suitable for the team after by the Maintainer field and the changelog entry. Upstream: https://github.com/git-multimail/git-multimail my version (adding only to debian/*): https://github.com/dancsa/git-multimail/tree/1.0.2_deb Comments are welcome. Daniel Galambos / Dancsa signature.asc Description: OpenPGP digital signature
Re: pybuild and proxies -- could we make "prohibition" optional?
On 22.07.2015 15:45, Yaroslav Halchenko wrote: > > On Wed, 22 Jul 2015, Piotr Ożarowski wrote: > >> [Yaroslav Halchenko, 2015-07-21] >>> As I have mentioned some tools might not be smart about empty values >>> in http_proxy, try e.g. git-annex under such settings > >> ah, sorry, I only quickly scanned you email. > >> I already followed Dimitri's suggestion to add no_proxy=localhost and >> will add your PYBUILD_FAKE_PROXY later today > > awesome! feel free to tune the name to whatever you feel more appropriate. > Just an additional piece of support to allow simply disabling automatic > assignment of fake proxies and that no_proxy doesn't work for some > libs/packages: Daniel Stender tried export no_proxy=localhost on > pytest-tornado > without success. ... pytest-localserver currently (in the multiple package dep solving approach for vcr.py), dh-python 2.20150719. DS -- http://www.danielstender.com/blog/ 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55afa0ec.5070...@danielstender.com
Re: Git migration schedule
Hi, these old SVN repos could be spared and removed: On 03.10.2015 20:52, Stefano Rivera wrote: > The errors: > > Cannot "git-dpm init" package: gamera is already in: git://anonscm.debian.org/python-modules/packages/gamera.git > Cannot "git-dpm init" package: nltk old/obsolete packaging, the initial Debian package was uploaded for Debian Science > Cannot "git-dpm init" package: svg.path got into: http://anonscm.debian.org/cgit/python-modules/packages/python-svg.path.git before the initial upload and > Cannot "git-dpm init" package: pyuca ... is currently in NEW. I'll convert that manually. Cheers, DS -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Re: Git migration schedule pushback permissions/DEP-3 workflow
On 08.10.2015 17:06, Stefano Rivera wrote: > Hi Barry (2015.10.02_16:24:28_+0200) >> 8-Oct - Assuming no objections or showstoppers, turn off write access to all >> of DPMT svn. > > Done. And kicking off the migration now... > > SR Thanks for the work, things likes automatically updated Vcs fields are much appreciated. Git-dpm patching appears to be great with features like auto-dropping of patches applied by upstream, that's much better than Quilt. Exploring ... I've got a push back error here: $ git push Counting objects: 22, done. Delta compression using up to 4 threads. Compressing objects: 100% (21/21), done. Writing objects: 100% (22/22), 2.72 KiB | 0 bytes/s, done. Total 22 (delta 12), reused 0 (delta 0) remote: error: insufficient permission for adding an object to repository database ./objects remote: fatal: failed to write object error: unpack failed: unpack-objects abnormal exit To ssh://danstender-gu...@git.debian.org/git/python-modules/packages/citeproc-py.git ! [remote rejected] master -> master (unpacker error) error: failed to push some refs to 'ssh://danstender-gu...@git.debian.org/git/python-modules/packages/citeproc-py.git' Question: When new patch has been installed after it misses a DEP-3 compliant header. I've now edited debian/patches/0001-foo.patch for that and made another commit on master. Is there a better/another workflow for this? Thanks DS -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Re: git repo lint tool
On 13.10.2015 16:30, Stefano Rivera wrote: > Daniel Stender >deap >gamera >greekocr4gamera >ocr4gamera >pep8-naming >pylint-celery >pylint-common >pytest-catchlog >pytest-localserver >pytest-tornado >python-djvulibre >python-requirements-detector >python-setoptconf >python-subprocess32 >python-xmp-toolkit >vcr.py All of these packages were in /git/python-modules/packages/ already before the migration, a couple have been migrated manually from SVN to Git some months before, for the other part (new packages) the packaging have been started already on/in Git. I've now restored the repos like suggested in the GitPackaging wiki page (Post-migration clean up), and there are all going to be configured for git-dpm patching in the course of the next days. In all packages, Vcs points to Vcs-Git: git://anonscm.debian.org/python-modules/packages/.git Vcs-Browser: http://anonscm.debian.org/cgit/python-modules/packages/.git Best, DS -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Re: git repo lint tool
On 13.10.2015 17:57, Stefano Rivera wrote: > Hi Daniel (2015.10.13_17:47:01_+0200) >> In all packages, Vcs points to >> Vcs-Git: git://anonscm.debian.org/python-modules/packages/.git >> Vcs-Browser: >> http://anonscm.debian.org/cgit/python-modules/packages/.git > > The linter script wants https for Vcs-Browser. > > SR Ah, o.k.! :-) I'll fix this, too. Thanks, Daniel -- 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 LPI certified Linux admin (LPI000329859 64mz6f7kt4) http://www.danielstender.com/blog/
Re: ITP: python-freetype -- Python bindings for the FreeType library (and request to join DPMT)
Hi, I'm planning to package python-freetype (freetype-py) as it is needed by another project that I am planning to package (python-palaso - no ITP yet). I'd like to join DPMT to have it team maintained. (username 'wdg'). I've read https://python-modules.alioth.debian.org/policy.html and I accept it. I've put the packaging I've got so far into team git: git+ssh://git.debian.org/git/python-modules/packages/freetype-py.git This is my first python package so it would help if someone else could check it before I upload. I think it is ready (bar a decision on below). python-palaso hasn't been ported to Python 3 yet, so would it be ok to create a Python 2 package for python-freetype as well as the Python 3 one for now? If not (though policy chap 1 says new packages 'should use Python 3' rather than must) and I have to do the python-palaso port, before it can be used, so be it. Regards, Daniel signature.asc Description: Digital signature
Re: ITP: python-freetype -- Python bindings for the FreeType library (and request to join DPMT)
On Thu, Nov 12, 2015 at 06:58:15PM +, Daniel Glassey wrote: > Hi, > > I'm planning to package python-freetype (freetype-py) as it is needed by > another project that I am planning to package (python-palaso - no ITP yet). > > I'd like to join DPMT to have it team maintained. > (username 'wdg'). > I've read https://python-modules.alioth.debian.org/policy.html and I accept > it. > > I've put the packaging I've got so far into team git: > git+ssh://git.debian.org/git/python-modules/packages/freetype-py.git > > This is my first python package so it would help if someone else could > check it before I upload. I think it is ready (bar a decision on below). > > python-palaso hasn't been ported to Python 3 yet, so would it be ok to create > a Python 2 package for python-freetype as well as the Python 3 one for now? > If not (though policy chap 1 says new packages 'should use Python 3' rather > than must) and I have to do the python-palaso port, before it can be used, > so be it. Hi, Any opinions/thoughts? Thanks, Daniel signature.asc Description: Digital signature
Re: static analysis and other tools for checking Python code
On 03.03.2016 01:38, Paul Wise wrote: > On Thu, Mar 3, 2016 at 7:52 AM, Jeremy Stanley wrote: >> ... > > All of flake8, hacking, bandit, pep257, clonedigger and more are on > the TODO list: > > https://anonscm.debian.org/cgit/collab-maint/check-all-the-things.git/tree/data/python > > FYI pep257 is definitely packaged: > > https://packages.debian.org/search?keywords=pep257 > >> I can probably think up more that I've used, but the above rise to >> the top of my list. > > More suggestions would be useful but most useful would be actual > tests. They are very simple to add if you know how to run the tools. BTW there's also Prospector which provides a uniform interface to many individual linters: https://packages.qa.debian.org/p/prospector.html Cheers, DS -- 4096R/DF5182C8 http://www.danielstender.com/blog/
Re: pep8 python module is now in python-pep8 - triggers FTBFS
On 10.03.2016 12:10, Edward Betts wrote: > I checked a few of these, in detail: > > - fix for fuzzywuzzy uploaded > - bug filed for blockdiag > - fix for django-sekizai pushed to git, e-mailed uploaders Prospector: fixed. DS -- 4096R/DF5182C8 http://www.danielstender.com/blog/
Re: pypi2deb 1.20160809 and --profile dpmt
On 09.08.2016 21:27, Piotr Ożarowski wrote: > Hi, > > FYI: I just uploaded pypi2deb 1.20160809 which initializes all the git-dpm > stuff if you invoke py2dsp with --profile dpmt option > > example: > > $ py2dsp --profile dpmt django > [...] > I: to create repository on git.debian.org: > ssh git.debian.org -c 'cd /git/python-modules && ./setup-repository > django "django packaging"' > I: to push (after reviewing all files) changes to DPMT's repo: > git push --set-upstream origin --all > [...] > $ cd result/django-1.10/ > $ git branch -a > * master >pristine-tar >upstream > $ git remote -v > origin ssh://git.debian.org/git/python-modules/packages/django.git (fetch) > origin ssh://git.debian.org/git/python-modules/packages/django.git (push) On this occasion ... let it be me to start the discussion: let's get into Git also for Python Apps soon. DS -- 4096R/DF5182C8 http://www.danielstender.com/blog/
Re: PAPT git migration
On 31.05.2017 20:58, Stefano Rivera wrote: > It's been a while, but I found some time and energy at PyCon, to work > our SVN->Git migration. > > I started with our DPMT migration script, pulled out the git-dpm bits, > and fixed the obvious issues I saw. > > Here's what the migration currently looks like [0]. > > [0]: https://anonscm.debian.org/cgit/users/stefanor/python-apps/ > > This is after several rounds of migration, and fixes to both the SVN > repo, and the migration script. Below are the notes I made during the > rounds of migration. I haven't re-reviewed every package, after fixing > it, only a couple of spot checks. The first round was ta revision 13997, > and the final one (published at [0]) was at revision 14089. > > And this is the migration script: > https://anonscm.debian.org/cgit/users/stefanor/dpmt-migration.git/ > > Does that look reasonable? Should we do this? > > SR +1 pybtex has been moved to Debian Science. BTW, the fix of #833469 from svn-buildpackage (copy .asc file together with tar) is needed to avoid problems with the error message "orig-tarball-missing-upstream-signature" from Lintian 2.5.52. DS -- 4096R/DF5182C8 (sten...@debian.org) http://www.danielstender.com/
Some pytest related packages on RFA
Hi, I have some pytest plugin packages for which I'm seeking an adopter for: 1) pytest-catchlog (https://bugs.debian.org/868844) https://packages.qa.debian.org/p/pytest-catchlog.html 2) pytest-httpbin (https://bugs.debian.org/868845) https://packages.qa.debian.org/p/pytest-httpbin.html 3) pytest-localserver (https://bugs.debian.org/868846) https://packages.qa.debian.org/p/pytest-localserver.html 4) pytest-tornado (https://bugs.debian.org/868847) https://packages.qa.debian.org/p/pytest-tornado.html 5) pytest-xdist (https://bugs.debian.org/870844) https://packages.qa.debian.org/p/pytest-xdist.html Greetings, DS -- 4096R/DF5182C8 (sten...@debian.org) http://www.danielstender.com/
Re: python logo.
On 03/06/2018 06:38 AM, Peter Green wrote: I am looking into cleaning up some software so it can be uploaded to Debian. Inside the documentation folder is a copy of the python logo. I found the python.org page for the logo more confusing than helpful. 1. Is the python logo under a license acceptable for including in a Debian package? or does it need to be stripped out? 2. If it is acceptable for inclusion how should it be documented in debian/copyright? See https://lists.debian.org/debian-legal/2015/03/msg2.html DS -- 4096R/DF5182C8 (sten...@debian.org) http://www.danielstender.com/
Joining PAPT
Hello, I would like to join PAPT because I am maintaining the weresync package (https://salsa.debian.org/python-team/applications/weresync). I have read the PAPT policy file at https://salsa.debian.org/python-team/tools/python-modules/ blob/master/policy.rst and I accept it. My Salsa username is donyorm-guest. I believe I had an account under svn, but I was on a hiatus for a year an either it was not transferred to salsa or I lost the login. Sincerely, Daniel
Request to join DPMT (adopting python-svg.path)
Hi! I'm interested in adopting this package. On Sun, 29 Mar 2020 at 11:04, Daniel Stender wrote: > > The terms of this RFA are the following: > > - anybody is free to pick up the package and close this bug without my > permission. > > - I won't be able to sponsor this due to lack of time, but I'm willing to help > to find a sponsor. For that, please just reach me at or > <816512-submit...@bugs.debian.org>. It would be great is someone from DPMT should like to sponsor me. > > > The package is community maintained within the DPMT, it would be great if this > could be kept, and it increases the chance to find a sponsor. I would like to join the DPMT and my salsa username is penlect-guest. Best regards, Daniel Andersson
joining the team
Hello Pythonistas, I would like to join the Python team. I help maintaining some Golang packages and would like to help maintaining Python packages as well since Python is my primary language of daily use. I have read the policy and I agree. My salsa login is dundee. I would be glad for some tips for first work. Thanks Daniel OpenPGP_0xEF0BA1C4F3990103.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital signature
Re: [Debichem-devel] [help] pymol: Deprecation warning during startup
Am Dienstag, dem 14.12.2021 um 21:17 +0100 schrieb Andreas Tille: > Hi, > > I think I've fixed the issue[1] and it works nicely at command line. > Unfortunately > Salsa-CI[2] shows a new issue > > AttributeError: module 'importlib' has no attribute 'util' > > which I do not understand at all since at command line there is the attribute > 'util'. importlib/util.py is part of libpython3.x-minimal, and while libpython3.10- minimal gets installed, libpython3.9-minimal is not and it seems, python3.9 is the default. So technically the error would be correct. As I said in my other mail, maybe use import importlib.util; ... Not sure of that fixes your dependencies. You have to depend on the right libpython3.x-minimal, it seems. HTH Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
Request to join the Debian Python team
Hi, I'd like to join the team. I've packaged and uploaded python-keycloak recently, and I would like to maintain it under the team's umbrealla. I've read the policy and my salsa handle is "dleidert". Regards, Daniel
Re: Request to join the Debian Python team
Ping? Am Donnerstag, dem 20.07.2023 um 00:44 +0200 schrieb Daniel Leidert: > Hi, > > I'd like to join the team. I've packaged and uploaded python-keycloak > recently, and I would like to maintain it under the team's umbrealla. > I've read the policy and my salsa handle is "dleidert". > > Regards, Daniel >
Joining the Debian Python Team
Hey, I wanna join the debian-python packaging team. I've got Mike Gabriel, who will be my teacher guiding me through my way to become a Debian Maintainer. I already have got a bit of experience with Debian Packaging (especially in the Debian Edu realm). You can see that on my salsa profile. I am online in the #debian-python IRC channel too, you can ping me there, if you have questions. > Why you want to join the team: e.g. maintain your current packages within the team, help maintain some specific packages, etc. I intend to package https://github.com/dscripka/openWakeWord. > Your Salsa login. https://salsa.debian.org/dzatoah > A statement that you have read https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst and that you accept it. I read it, understood it and accepted it. Greeting, dzatoah
Request to join Debian Python team
Hi Team, I am interested in joining the team, because, actually I am working in adopting some python apps [1][2][3] My Salsa login is epsilon[4]. Thanks! Regards [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065239 [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065241 [3]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065237 [4]: https://salsa.debian.org/epsilon -- Daniel Echeverri Debian Developer Linux user: #477840 GPG Fingerprint: D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB
Re: Request to join Debian Python team
Hello Team! El sáb, 9 mar 2024 a la(s) 11:33 a.m., Daniel Echeverri (epsi...@debian.org) escribió: > Hi Team, > > I am interested in joining the team, because, actually I am working in > adopting some python apps [1][2][3] > > My Salsa login is epsilon[4]. > > Thanks! > > Regards > > [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065239 > [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065241 > [3]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065237 > [4]: https://salsa.debian.org/epsilon > > -- > Daniel Echeverri > Debian Developer > Linux user: #477840 > GPG Fingerprint: > D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB > I forgot to say, that I accept the policy team mentioned in https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst Thanks in advance. Kind Regards. -- Daniel Echeverri Debian Developer Linux user: #477840 GPG Fingerprint: D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB
Broken python Build-Depends
It seems the recent change to drop the python dependency from python2.3 has broken a large number of package builds. The affected packages usually have Build-Depends on python2.3 and assume that will mean python is also installed. I'm planning to start filing bugs on these packages in a few days. In the meantime, it would be a good idea for maintainers of Python packages to use pbuilder to check whether their packages still build or not. -- Daniel Schepler "Please don't disillusion me. I [EMAIL PROTECTED]haven't had breakfast yet." -- Orson Scott Card
Re: Bug#708573: trac-accountmanager: Please remove Python Applications Packaging Team as maintainer
[dropping the bug report from the cc list] On 05/17/2013 11:49 AM, Scott Kitterman wrote: > We've been through this a number of times for both PAPT and DPMT. We want a > common repository for each team (not split between different VCSs). There's > been discussion about what would be needed to migrate from SVN to something > else and about what work would need to be done to do that. So far no one has > done the work. Perhaps this should be documented someplace so that when it comes up in the future, there is a clear document to refer to. I haven't heard any of these discussions, and i don't know where they took place or who took part in them. sorry for my ignorance! It's hard to make an overarching, universal, and complete transition plan without at least some pilot work being done. Maybe my recent work on the trac package can be helpful to the team for this kind of consideration. I see 199 packages in PAPT (svn+ssh://svn.debian.org:/svn/python-apps/packages) and 616 in DPMT (svn+ssh://svn.debian.org:/svn/python-modules/packages). It sounds to me like PAPT is the simpler place to start. If the packaging is generally uniform in nature (it looks like it is from the poking around i've done), I would be willing to write some conversion scripts that breaks that 200-package SVN repo into 200 separate git repositories. I note that the svn repo only appears to contain the debian/ directories, and does not contain the upstream sources as well. I think it is easier to work from a revision control system that directly tracks upstream source packages too, so part of my conversion scripts would be to fetch the appropriate upstream files for the latest versions and import them (unpacked) as well, along with a pristine-tar delta so that the original tarball can be reconstructed from the git repo. I do not currently expect to be able to import all the old upstream tarballs for each package, so the history for the upstream tarballs would "begin" at the present (if there are specific cases we care about, does this sound like a reasonable workplan? are people interested in working on it with me? > The shorter answer is that there are no PAPT maintained git repositories > because the team uses svn. would the team be interested in using the git repositories if the above workplan is successful? If you're not sure how to answer because you're not sure how a converted repository looks, feel free to take a look at git://anonscm.debian.org/collab-maint/trac.git Regards, --dkg signature.asc Description: OpenPGP digital signature
Re: Bug#708573: trac-accountmanager: Please remove Python Applications Packaging Team as maintainer
On 05/17/2013 01:20 PM, Thomas Kluyver wrote: > This came up recently on debian-python. It's a very long thread, but the > basic outcome was that, while quite a few people wanted to move away from > svn, there was very little consensus on which VCS to migrate to, whether to > include full source tarballs, and how to do any migration. It was suggested > that if someone was willing to put the time in to drive a migration, that > might be OK, but by then the discussion had pretty much killed all > enthusiasm for it. > > My memory is that there was also disagreement over whether the team could > live with packages split across two difference VCSs. Some people argued > that the teams packages should be unified, others that a migration would be > easier if it didn't need to be all-at-once. Some other packaging teams > (e.g. Games) do have packages in two VCSs. > > Here's the start of that thread, if you've got time to read through it all: > http://lists.debian.org/debian-python/2013/02/msg00032.html thanks for the link. I am willing to drive the migration for python-apps (PAPT); i will target moving all of the packages to git, and i will include upstream tarballs. I will use tools and scripts that i will document and i will document my work so that other python-related teams can take advantage of my effort. If the PAPT team wants to bless this effort by creating a tree of git repositories that i can stage this transition into, that is fine by me. If not, i will stage these transitions directly into the collab-maint tree of git repos (as i have already done with trac), and then people can decide whether they want to move them into some hypothetical PAPT tree of git repos whenever the PAPT team gets around to making that decision. Which would folks prefer? --dkg signature.asc Description: OpenPGP digital signature
Re: Bug#708573: trac-accountmanager: Please remove Python Applications Packaging Team as maintainer
On 05/17/2013 01:40 PM, Scott Kitterman wrote: > If the team moves to full source git archives, I'll just drop the team from > all the packages I maintain. > > Scott K > > P.S. See, now the fun begins. fun, indeed. it sounds to me like you're saying: A) re: #708573 if some members of the team want to use full source git archives for some PAPT packages, they cannot keep those packages as part of the team, because B) any VCS transition needs to be all packages or none of them, and C) if such a full transition happens then you will take "your" packages out of the team. This doesn't sound like a team, it sounds like a weird fiefdom with people holding each other hostage. No, thanks. I rescind my offer to drive a team-wide transition, since i had offered it in order to try to respond in good faith to the concerns of people who wanted a uniform packaging framework, but apparently that's not feasible. I will instead move any packaging i'm responsible for to collab-maint, where people can work together more easily even if they have slightly different habits from each other. I welcome anyone from PAPT (or elsewhere!) to work on those packages with me if they like, and i'm sorry that i'm apparently not allowed to do this under the PAPT umbrella. Bummer, because i was looking forward to having explicit support from other packagers who are specifically interested in making python applications work well with debian, which is what i had imagined PAPT would be. Have fun, --dkg signature.asc Description: OpenPGP digital signature
Re: Bug#708573: trac-accountmanager: Please remove Python Applications Packaging Team as maintainer
On 05/17/2013 01:55 PM, Scott Kitterman wrote: > You misunderstand. I don't think i misunderstood at all. > I'm all for having a good common environment for the team to work on. I > happen to think you suggested just about the worst one possible. I've tried > it and I find it much more complex, error prone, and time consuming than what > we have now. I understand that this is what you believe, you made that clear. Your experience with DVCS with full upstream source does not match my experience with the same tools, but i'm sure our experiences are different in many ways :) > So I'm all for improvement, but it should be an improvement. I'd love it if > we we using a DVCS, but I don't think full source branches are a good idea. I was offering to do the work to drive a transition. I'm sorry that the end point of the transition i was proposing is not what you wanted. Unsurprisingly, I'm not willing to do the work to drive a transition that ends up somewhere that doesn't make sense to me (though if it was a transition to git i would happily support someone else doing that work even if we differed on whether to include upstream source or not). But it doesn't sound like anyone is willing to do the work to drive a transition that ends up where you want; or if they are, i haven't heard any offers. So PAPT will probably stay with one large centralized VCS that seems to be no ones' first choice. ah well, --dkg signature.asc Description: OpenPGP digital signature
Re: [py3porters-devel] Python 2 in the default installation -- progress made!
On Thu 2016-12-29 23:41:39 -0500, Stuart Prescott wrote: > one of the objectives for stretch was to reduce the number of Python 2 > packages that are installed in common scenarios, instead having the > Python 3 stack take over. The "standard task" within tasksel is a > reasonable place to look.¹ [...] > python-gpg > python3-gpg fwiw, python-gpg and python3-gpg should not be Priority: standard, and they are indicated as such in the source packages. https://packages.qa.debian.org/g/gpgme1.0.html indicates that they're marked that way due to override files, but i don't think there'd be any objection from myself or any of the other pkg-gnupg-maint team (cc'ed here) if those overrides were removed. --dkg signature.asc Description: PGP signature
Re: [py3porters-devel] Python 2 in the default installation -- progress made!
On Mon 2017-01-02 19:47:00 -0500, Ansgar Burchardt wrote: > There was an open bug about changing the overrides (#849903) and I just > set all packages built from gpgme1.0 to "Priority: optional". > > I don't think there is any reason for the lib*-dev packages to be at > Priority: extra? I read: https://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities as suggesting that -dev packages are generally more "extra-ish" than "optional", but then again, i think of workstations set up for software development as having "specialized requirements" compared with what most computers might reasonably want to install: >> optional >> >> (In a sense everything that isn't required is optional, but that's >> not what is meant here.) This is all the software that you might >> reasonably want to install if you didn't know what it was and don't >> have specialized requirements. This is a much larger system and >> includes the X Window System, a full TeX distribution, and many >> applications. Note that optional packages should not conflict with >> each other. >> >> extra >> >> This contains all packages that conflict with others with required, >> important, standard or optional priorities, or are only likely to >> be useful if you already know what they are or have specialized >> requirements (such as packages containing only detached debugging >> symbols). I personally develop software, and i maintain many computers (for myself, even), and i definitely *don't* want most of my computers to include the -dev packages. I'm happy to go with whatever the ftp-master team prefers, though. :) --dkg signature.asc Description: PGP signature
Re: Bug#936604: getmail: Python2 removal in sid/bullseye
On Wed 2019-11-13 15:31:04 +0100, Iustin Pop wrote: > On 2019-11-13 15:06:54, Thomas Goirand wrote: >> On 11/12/19 4:37 PM, Osamu Aoki wrote: >> > The related binary packages are available in 2 binary names (depending on >> > release) >> > getmail4 (version=4,5) popcon installed ~2000 >> > getmail (version=3,5) popcon installed ~1000 >> > >> > https://qa.debian.org/popcon-graph.php?packages=getmail%20getmail4&show_installed=on&want_legend=on&want_ticks=on&date_fmt=%25Y-%25m&beenhere=1 >> > >> > I think this qualifies for "py2keep". >> >> IMO, this qualifies for RM-RoM. getmail is an alternative to fetchmail, >> which is still available in Debian (and with 4 times the number of >> installed package in popcon...). So I see no reason to keep getmail >> then. Maybe tell this to upstream, and they may think another time. > > Uh, no. Functionality-wise, they're quite different. getmail is (AFAIK) > the only tool that works for gmail with ASPs disabled (i.e. with OAUTH). > > Heck, I'd be very willing to maintain Py3 patches myself, because I need > this tool. Thanks for the clarification about what you need from this tool. I stopped using getmail several months ago, and i'm in the process of taking my name out of the uploaders list. Sorry to bail on it, Osamu! I just don't feel write being named as responsible for it when i no longer even have python2 on many systems that i care about. Upstream appears to indicate that getmail for python3 is likely to be a nearly complete rewrite. For myself, i've been using the very simple imap-dl (now in mailscripts 0.18, i'm the main author, and Sean Whitton is a very capable maintainer). But imap-dl doesn't have the OAUTH mechanism for gmail built in. If you wanted to port that mechanism into imap-dl, i'd be happy to review it, though! Regards, --dkg signature.asc Description: PGP signature
