Re: Hand pygame maintainership over to Debian Python Modules Team?
On Fri, May 17, 2013 at 2:33 AM, Vincent Cheng wrote: > Hi Andrea and Ed, > > Would it be ok with you if we were to set pygame's maintainer to the > Debian Python Modules Team > ? I'm personally in > favour of moving as many packages as possible over to team > maintainership, and pygame is important enough that I think it > deserves to have more people taking care of it (and besides, team > uploads are easier to do than NMUs). > > Ed: you're currently pygame's maintainer, but even though I've sent > you multiple private emails (and I and Andreas cc'ed you in our > conversations) since I took up de facto maintainership of pygame back > in June of 2011, I've never heard back from you at all. Not to mention > that a quick search through Debian's mailing lists seems to indicate > that you were last seen around 2002...are you still active in Debian, > and would you still like to take part in maintaining pygame? > > Regards, > Vincent Err, I meant to cc debian-python@l.d.o, not python-modules-team@l.a.d.o. My bad. -- 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/CACZd_tCoQLYpiaBuN4LVLqYKbrv-W5RtPUy2uz_5aqZ=vrj...@mail.gmail.com
Re: Hand pygame maintainership over to Debian Python Modules Team?
Glad to see that you're still alive and not MIA, Ed. :) Since both you and Andreas agree, I'll switch the maintainer field over to the Debian Python Modules Team (and keep you and Andrea's names in Uploaders, of course) and move pygame over from collab-maint soon-ish (well, as soon as I'm accepted into the team). Thanks! Regards, Vincent On Fri, May 17, 2013 at 6:33 AM, Ed Boraas wrote: > Assigning maintainership to the team makes sense to me (and I favour team > maintainership as well), but I'd like to hear Andrea's thoughts. As noted, > my activity level has been quite low of late, and I wouldn't want my opinion > taken to have too much significance. > > Realistically, I'm not likely to be able to play a significant role in > pygame's maintenance going forward. > > -Ed > > On May 17, 2013 3:38 AM, "Vincent Cheng" wrote: >> >> On Fri, May 17, 2013 at 2:33 AM, Vincent Cheng >> wrote: >> > Hi Andrea and Ed, >> > >> > Would it be ok with you if we were to set pygame's maintainer to the >> > Debian Python Modules Team >> > ? I'm personally in >> > favour of moving as many packages as possible over to team >> > maintainership, and pygame is important enough that I think it >> > deserves to have more people taking care of it (and besides, team >> > uploads are easier to do than NMUs). >> > >> > Ed: you're currently pygame's maintainer, but even though I've sent >> > you multiple private emails (and I and Andreas cc'ed you in our >> > conversations) since I took up de facto maintainership of pygame back >> > in June of 2011, I've never heard back from you at all. Not to mention >> > that a quick search through Debian's mailing lists seems to indicate >> > that you were last seen around 2002...are you still active in Debian, >> > and would you still like to take part in maintaining pygame? >> > >> > Regards, >> > Vincent >> >> Err, I meant to cc debian-python@l.d.o, not python-modules-team@l.a.d.o. >> My bad. -- 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/caczd_tceqaeyvvqcmj0o4roj2fpoaoyyt87k4tjrgv+da83...@mail.gmail.com
Re: Request to Join Project Python Modules Packaging Team from Vincent Cheng (vincentc-guest)
Hi all, On Fri, May 17, 2013 at 8:04 AM, Jakub Wilk wrote: >> I currently maintain pygame outside of the team, and I'd like to bring it >> into the Debian Python Modules Team (instead of having it just sit in >> collab-maint). If I have time I can also help out with some of the other >> python modules maintained by the team, of course. :) > > > Could you re-send the join request to debian-python@lists.debian.org? Thanks > in advance. > I guess I should briefly introduce myself to the rest of the team first. Well, I'm currently a DM (DDPO profile here [1]), and I'd like to join the DPMT and PAPT to move some of my self-maintained packages (pygame is one of them) into team maintainership. Most of my other packages are also team-maintained (I'd estimate half of my packages to be in the Debian Games team, in fact). I also lurk on IRC as vincent_c, so feel free to poke me there if you'd like to chat with me. Thanks! Regards, Vincent [1] http://qa.debian.org/developer.php?login=vincentc1...@gmail.com -- 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/caczd_tbnqqprg9fvw1bd6lw-xvd0hjv2ovsl9kmpzean3ua...@mail.gmail.com
Re: Request to Join Project Python Modules Packaging Team from Vincent Cheng (vincentc-guest)
On Sun, May 19, 2013 at 7:09 AM, Jakub Wilk wrote:
> * Vincent Cheng , 2013-05-18, 01:50:
>
>> I'm currently a DM (DDPO profile here [1]), and I'd like to join the DPMT
>> and PAPT to move some of my self-maintained packages (pygame is one of them)
>> into team maintainership. Most of my other packages are also team-maintained
>> (I'd estimate half of my packages to be in the Debian Games team, in fact).
>
>
> Welcome to the team!
Thanks! :)
> Here's my review of pygame_1.9.2~pre~r3189-2:
>
> You have "python3.2-dev (>= 3.2.3-7)" in Build-Depends. Could you put
> "python3.2-dev (<< 3.2.3-7)" in Build-Conflicts instead? That should have
> the same effect, while making it easier to remove python3.2 from the archive
> in the future.
Fixed.
> What is libjs-sphinxdoc in Depends for? The changelog says "Add depends on
> libjs-sphinxdoc and replace embedded js libraries with symlinks in
> debian/rules", but I don't see anything relevant in debian/rules. But
> anyway, should probably put ${sphinxdoc:Depends} in Depends and use
> dh_shpinxdoc instead of replacing this stuff manually.
Errr...I remember that at one point lintian complained about embedded
js libraries (jquery IIRC), but they don't seem to be present anymore
with the latest hg snapshot. I'll have to take a closer look at
this...
> I advocate against using ${python:Provides}:
> http://lists.debian.org/20110324164804.ga5...@jwilk.net
Fixed.
> It's time to drop Replaces/Conflict with python2.{3,4}-pygame.
Fixed.
> “for” loops in debian/rules lack “set -e”; see Policy §4.6.
Fixed.
> Please honour DEB_BUILD_OPTIONS=nocheck.
>
> Please run tests with all supported Python versions, not only the default
> one.
>
> Is there a reason test failures are ignored?
Some of the tests require X and a display adapter, hence me being lazy
and deciding to just skip tests altogether. I didn't know about xvfb
until just now however, so I'll definitely take another look at it.
> You might want to try run the tests under xvfb. Hopefully that should allow
> running more of them than currently.
>
> You never call "setup.py build" with python3.X, so building Python 3.X
> modules takes place only when you call "setup.py install", that is in
> binary* targets, with (pseudo)root privileges. This is something your should
> avoid.
Fixed.
> /usr/share/pyshared/pygame/docs: AFAICS this is the very same documentation
> as in /usr/share/doc/python-pygames/. Are two copies really needed?
>
> /usr/share/pyshared/examples: examples normally belong to
> /usr/share/doc/$package/examples/.
>
> Documentation and examples are quite big, and they are included in both
> binary packages. Maybe it would make sense to move them to a separate
> documentation package?
Definitely, that's on my TODO list for pygame...which has now just
grown much longer ;)
> /usr/share/pyshared/tests: do tests make sense in the binary package? I
> wouldn't install them.
>
> /usr/share/pyshared/pygame/LGPL: Lintian should have emitted
> extra-license-file.
>
> I see you overrode image-file-in-usr-lib, but "This is where distutils
> installs everything" is a poor excuse. :)
Is there any easy workaround for this? Admittedly I was being a bit
lazy here as well, but pygame's source doesn't contain that many
images and I didn't think it was worth adding more complexity to the
packaging in order to appease lintian.
> test/test_utils/unittest.py is an embedded copy of stdlib module. Please
> make sure it's not used at build time, and that it's not installed into
> binary packages.
>
> Please regenerate src/pypm.c from src/pypm.pyx at build time.
>
> docs/reST/ref/code_examples/joystick_calls.py uses "print" as method name.
> You can't do that in Python 2.X (unless you import print_function from
> __future__).
>
As for everything else, I'll fix each issue one by one when I have
some spare time. In the meantime, I've moved the packaging over from
collab-maint to the team's repository; any help would definitely be
appreciated.
Thanks for the very thorough review! :)
Regards,
Vincent
--
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/caczd_tarllfjy2d1skmmx_r5nzm5fj7l3em22yz0usxde_3...@mail.gmail.com
Re: Request to Join Project Python Modules Packaging Team from Vincent Cheng (vincentc-guest)
On Sun, May 19, 2013 at 6:27 PM, Yaroslav Halchenko wrote: > > On Sun, 19 May 2013, Jakub Wilk wrote: >> You might want to try run the tests under xvfb. Hopefully that >> should allow running more of them than currently. > > just so it might come handy for others: to enable GLX support under > Xvfb, here is the line I have suggested to be used (upstream just > adopted it ;) ) for impressive build time testing: > > xvfb-run -s "-screen 0 640x480x24 -ac +extension GLX +render -noreset" COMMAND > > seems to work fine (besides on Ubuntu 12.10 for unknown to me yet reason). It > seems thought that you would also need build-depends on libgl1-mesa-dri to > make > it work ;) > Thanks for the tip! I'll have to read up on xvfb in my spare time; it looks to be rather useful and I kinda wish I learned about it earlier. Regards, Vincent -- 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/caczd_tb6py36xvuq+togqdagtgco8kyoh1epgep_v7-nprg...@mail.gmail.com
Re: Upload new version of Veusz
Hi Jeremy, On Sat, Feb 15, 2014 at 9:02 AM, Jeremy Sanders wrote: > Could someone have a look at uploading a new version of Veusz? The current > Debian version, 1.15, is very old (>1.5 yrs). > > I've updated Veusz in the PAPT repository to 1.20.1. These are the changes > since the current version. It appears to build properly in pbuilder for sid. I've briefly looked at your package (i.e. I haven't tried building it yet; my local network is acting up and it's taking forever to download the required build-deps at the moment...), but anyways, some comments about your package: - latest standards version is 3.9.5 - please collapse all unreleased d/changelog entries into a single entry (dch -i should've done that for you); it should look something like this: veusz (1.20.1-1) unstable; urgency=low [ Jakub Wilk ] * Use canonical URIs for Vcs-* fields. [ Jeremy Sanders ] * Update to Veusz 1.20.1 ... - since you sign your tarballs upstream, please have uscan check the signature as well (lintian-info -t debian-watch-may-check-gpg-signature) Regards, Vincent -- 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/caczd_tbk7jgip1mxf-dahqqxzrdryal4d6xgir3ubuaazmv...@mail.gmail.com
Re: RFS: Pyspread 0.2.6-1
On Mon, Feb 17, 2014 at 12:57 PM, Andreas Noteng wrote: > Requesting a review and upload of Pyspread 0.2.6-1 available in the papt > repo. > Package is lintian clean, but I'm unsure if I did the DEP-8 implementation > correctly or if it's at all possible. Running the tests manually works just > fine but with adt-run some of them fail > Changes since last upload: I haven't looked at this package any further beyond the changelog below, but... > pyspread (0.2.6-1) unstable; urgency=low > > * New upstream release > * Refresh patches > * Delete documentation_typos.patch, fixed upstream > * Add DEP-8 tests > * Remove runstests.py from original tarball and regenerate during test run > * Add recommends: python-xlrd, ttf-mscorefonts-installer ...A package in main must not depend or recommend a non-main package (in this case, ttf-mscorefonts-installer, which is in contrib). Refer to Policy 2.2.1. > * Standards-Version bumped to 3.9.5 (no change) > Regards, Vincent -- 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/CACZd_tCnZLDKfOQB4EO78Ve7GjQf_Zrnaw7254uB=oYtXzM=_...@mail.gmail.com
Re: Upload new version of Veusz
On Mon, Feb 17, 2014 at 2:50 AM, Jeremy Sanders wrote: > Ok - I've added this. I wasn't sure whether the correct place to > put the keyring was in upstream/ or in upstream-signing-key.pgp, > as there seemed to be some inconclusive discussion about whether > upstream/ is correct. I ended up using upstream-signing-key.pgp. That's fine. > One unresolved question is whether to support Python 3 at the > moment. Veusz can use either (py3 support is poorly tested, > though). Veusz is both an app and a python module, so it's a bit > unclear what to do. Maybe it needs splitting up into a > module (py2 and py3) and an app (py2?) package. The same source > can run under both py2/3, however. There are quite a lot of > common data files, so maybe we'd end up with > > veusz > python-veusz > python3-veusz > python-veusz-helpers > python3-veusz-helpers > veusz-data > > It seems a bit of a nightmare of package multiplication and > complexity though. Maybe this can be left until later? (My understanding of) the consensus is that modules should provide both python2 and python3 packages when possible, and individual applications can depend on either python2 or python3. I'm not entirely sure if there's consensus on what happens in the case where a package provides both a python module and is an application at the same time (I'll leave it to others on the list to chime in), but in any case, that's not a blocker and is something you can work on for future uploads anyways. Built, signed, and uploaded. Oh, and don't forget to verify and close #714891 otherwise veusz won't migrate to testing. Regards, Vincent -- 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/caczd_tcvkb5b1dlil11+feksf7fx5rcsrkjth-f+2yh36go...@mail.gmail.com
Re: Upload new version of Veusz
On Tue, Feb 18, 2014 at 3:14 AM, Jeremy Sanders wrote: > On 02/18/2014 02:28 AM, Vincent Cheng wrote: > >> Built, signed, and uploaded. Oh, and don't forget to verify and close >> #714891 otherwise veusz won't migrate to testing. > > > Thanks very much. However, I've just had a report from someone that there is > a problem installing the new package on testing. Apparently it requires a > sip-api-8.1 and only sip-api-10 is available. I don't have a testing system > with me at the moment to confirm, but this seems to show it: > https://packages.debian.org/en/sid/veusz-helpers > > Did something go wrong with the build here or was it my mistake? Sorry, that was entirely my fault. (I was also in the midst of preparing packages for upload to wheezy-backports, and it looks like I might've accidentally built veusz in a wheezy environment. My bad!) There's a binNMU request for this already filed (#739467), so this'll get fixed when that's done. Vincent -- 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/caczd_tbhlc1qx1vzuqxtoqqbvq0djke6z7j0bokbbw3gwcm...@mail.gmail.com
Re: RFS: Pyspread 0.2.6-1
On Tue, Feb 18, 2014 at 3:48 AM, Andreas Noteng wrote: > On 17. feb. 2014 23:26, Vincent Cheng wrote: >> >> ...A package in main must not depend or recommend a non-main package >> (in this case, ttf-mscorefonts-installer, which is in contrib). Refer >> to Policy 2.2.1. > > Thanks. I knew depend was not OK but believed recommends was. But, according > to 2.2.1 suggests is ok, right? > Pyspread works just fine without ttf-mscorefonts-installer, so I guess > suggests would be a better choice anyway. The tests will fail without the > package though. Is it OK to include ttf-mscorefonts-installer as a test > dependency in debian/tests/control ? Suggests is fine, yes. I don't really know how autopkgtests work, but if they're run automatically during the build process like dh_auto_test, then that would cause your package to FTBFS. Can you modify the tests so that they work with other fonts, or disable the offending tests entirely? Regards, Vincent -- 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/CACZd_tB=sp9mbovedu9hyabdfybcrztbrestecjtwricycc...@mail.gmail.com
Re: RFS: Pyspread 0.2.6-1
On Fri, Feb 21, 2014 at 6:27 AM, Barry Warsaw wrote: > On Feb 21, 2014, at 01:59 PM, Dmitry Shachnev wrote: > >>On Wed, Feb 19, 2014 at 7:45 PM, Barry Warsaw wrote: >>> They don't run automatically during package build for either pbuilder or >>> sbuild afaik, although that would be really nice. >> >>No. Autopkgtests are designed to test *installed* packages, which is >>just not possible to do at build time (i.e. because that requires a >>different set of dependencies). > > Right. I was just saying that I think it would be nice if sbuild/pbuilder > could arrange to run run-adt-test with the artifacts of the build installed. > It's probably a bit tricky to get it right, but not doing so probably means > that most autopkgtests aren't actually getting run locally before being > uploaded. Thanks for the explanation! You're right, it'd be nice to see autopkgtest integrated with pbuilder and/or sbuild; it would certainly give autopkgtest more visibility in Debian. It seems to me that only Ubuntu is taking advantage of it, but autopkgtest adoption could be sped up a lot more (in both Debian and Ubuntu) if DDs in general were aware of it and started adding them to their own packages en masse. With regards to pyspread...given the discussion above, I don't think ttf-mscorefonts-installer even belongs in suggests? End users are usually the only ones that care about suggested packages, and they're not the ones who are going to be creating or running autopkgtests anyways. Regards, Vincent -- 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/caczd_tcw1tyn+t_54pexyvom_rdbcfac2wj72grndbyiio+...@mail.gmail.com
Re: RFS: Pyspread 0.2.6-1
On Mon, Mar 3, 2014 at 11:01 AM, Andreas Noteng wrote: > On 17. feb. 2014 21:57, Andreas Noteng wrote: >> >> Requesting a review and upload of Pyspread 0.2.6-1 available in the papt >> repo. >> Package is lintian clean, but I'm unsure if I did the DEP-8 implementation >> correctly or if it's at all possible. Running the tests manually works just >> fine but with adt-run some of them fail > > Made some changes and removed the ttf-mscorefonts-installer dependency from > the tests and changed the dependency on it from recommends to suggests. > Apparently the fonts are useful if opening pyspread files created on > windows. New changelog: > > > pyspread (0.2.6-1) unstable; urgency=low > > * New upstream release > * Refresh patches > * Delete documentation_typos.patch, fixed upstream > * Add DEP-8 tests > * Remove runstests.py from original tarball and regenerate during test run If there aren't any non-DFSG-compliant files in upstream's tarball (and I see nothing that would suggest that this file in particular is non-DFSG-compliant), please do not repack upstream's tarball; it's simply not necessary at all. You can simply remove this file on clean and regenerate it as you would normally do. (Some other pet peeves of mine: not appending +dfsg/+ds to the version number if you're using a repacked tarball, and not uploading your repacked tarball to mentors.d.n so I can compare your tarball with one that I'd generate myself with your get-orig-source target.) > * Add recommends: python-xlrd > * Add suggests: ttf-mscorefonts-installer > * Make sure tests don't fail if ttf-mscorefonts-installer is not installed > (tests_font_check.patch) > * Switch from using key uid to key id (Closes: #739907) > (gpg_uid_to_key_id.patch) > > * Standards-Version bumped to 3.9.5 (no change) > > -- Andreas Noteng Mon, 03 Mar 2014 17:00:24 +0100 > > A review and hopefully an upload would be appreciated. Looks ok, I haven't found any other issues other than the one above. Also, according to DEHS, there's a new upstream release that you may want to consider packaging. Regards, Vincent -- 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/caczd_tdtks3g_h8geso2uws61hpx5qcjuv7oob+pjiymtmk...@mail.gmail.com
Re: RFS: Pyspread 0.2.6-1
On Sat, Mar 8, 2014 at 4:57 AM, Andreas Noteng wrote: > On 07. mars 2014 02:52, Vincent Cheng wrote: >> >> If there aren't any non-DFSG-compliant files in upstream's tarball >> (and I see nothing that would suggest that this file in particular is >> non-DFSG-compliant), please do not repack upstream's tarball; it's >> simply not necessary at all. You can simply remove this file on clean >> and regenerate it as you would normally do. > > No, the only issue is the non verifyable binary code in the script. If > you're ok with uploading the original tarball that's fine by me. SVN > updated. If you can regenerate that file during the build process, I'd argue that it doesn't qualify as non-verifyable binary code (given that source is present and you do in fact regenerate the file). :) >> Looks ok, I haven't found any other issues other than the one above. > > The previous releases have been thoroughly checked by Jakub Wilk, so I think > it should be OK. :-) > >> >> Also, according to DEHS, there's a new upstream release that you may >> want to consider packaging. > > The newer tarball is a windows only change, so I'll wait for the next > upstream release. Ack. Built, signed, and uploaded; thanks for your contribution to Debian! Regards, Vincent -- 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/CACZd_tBmkYdgBru5_4QZ+=Uu5MFz=F=v06uva8yauo0yb68...@mail.gmail.com
Re: RFS: python-ebooklib
On Fri, Apr 25, 2014 at 8:24 AM, Daniel James wrote: > 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. 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). Also, don't hardcode python versions in your package's dependencies (as mentioned previously on the list [1] - and if you're not subscribed to the list already, please do so). Regards, Vincent [1] https://lists.debian.org/debian-python/2014/04/msg00040.html -- 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/CACZd_tBuE42_7n=cyzpx4mboqlmgxncqrwqyotayax5nsnu...@mail.gmail.com
Re: RFS: python-twython - Pure Python wrapper for the Twitter API
On Thu, May 1, 2014 at 8:07 PM, Josue Ortega wrote: > Hi Team, > I am looking for a sponsor for my package and maitain it with the DPMT. > The package is python-twython Pure Python wrapper for the Twitter API. > This closes #739010 which is an ITP. > Here is some useful information about the package: > Version : 3.1.2-1 > Upstream Author : Ryan McGrath > URL : https://github.com/ryanmcgrath/twython/tree/master > License : MIT > > > It builds those binary packages: > python-twython - Pure Python wrapper for the Twitter API > python3-twython - Pure Python3 wrapper for the Twitter API > > If you are interested you can get it on mentors[0] or in the SVN DPMT[1]. Just curious, how does this differ from python-twitter, which is already in the archive? Do we need two different sets of python wrappers around Twitter's API? Regards, Vincent -- 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/CACZd_tDxg1bkV_1kAdt8tWssh5EwWp1y-3WMpUCX5WfjTa=-8...@mail.gmail.com
Re: RFS: oct2py -- GNU Octave to Python bridge
Hi Josue, On Sat, May 3, 2014 at 7:02 PM, Josue Ortega wrote: > Hi Team, > I am looking for a sponsor for my package and maitain it with the DPMT. > The package is python-oct2py -- GNU Octave to Python bridge > Oct2Py is a means to seamlessly call M-files and Octave functions from Python. > It manages the Octave session for you, sharing data behind the scenes using > MAT > files. > > This closes #743499 which is an ITP. > > Here is some useful information about the package: > > * Package name: oct2py >Version : 1.3.0-1 >Upstream Author : Steven Silves > * URL : http://blink1073.github.io/oct2py/docs/ > * License : MIT >Section : python > > It builds those binary packages: > python-oct2py - Python to GNU Octave bridge --> run m-files from Python > python3-oct2py - Python3 to GNU Octave bridge --> run m-files from Python > > If you are interested you can get it on mentors[0] or in the SVN DPMT[1]. > > Thank you for your help. - debian/control: "Suggests:" is spelled with two "s"-es, not one - debian/control: you use --buildsystem=pybuild in debian/rules, but you don't declare a build-dep on dh-python Both the above issues should cause your package to FTBFS (assuming you actually tested your package by building it with pbuilder/sbuild/etc.). Regards, Vincent -- 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/CACZd_tAtY038dYfkWyX7eEoRK4=4o4gg3k9q+hcuduzmfgh...@mail.gmail.com
Re: RFS: oct2py -- GNU Octave to Python bridge
On Sat, May 3, 2014 at 7:02 PM, Josue Ortega wrote: > Hi Team, > I am looking for a sponsor for my package and maitain it with the DPMT. > The package is python-oct2py -- GNU Octave to Python bridge > Oct2Py is a means to seamlessly call M-files and Octave functions from Python. > It manages the Octave session for you, sharing data behind the scenes using > MAT > files. > > This closes #743499 which is an ITP. > > Here is some useful information about the package: > > * Package name: oct2py >Version : 1.3.0-1 >Upstream Author : Steven Silves > * URL : http://blink1073.github.io/oct2py/docs/ > * License : MIT >Section : python > > It builds those binary packages: > python-oct2py - Python to GNU Octave bridge --> run m-files from Python > python3-oct2py - Python3 to GNU Octave bridge --> run m-files from Python > > If you are interested you can get it on mentors[0] or in the SVN DPMT[1]. > > Thank you for your help. - debian/control: "Suggests:" is spelled with two "s"-es, not one - debian/control: you use --buildsystem=pybuild in debian/rules, but you don't declare a build-dep on dh-python Both the above issues should cause your package to FTBFS (assuming you actually tested your package by building it with pbuilder/sbuild/etc.). Also, your package on mentors.debian.net has an .orig.tar.xz, but the upstream tarball distributed on pypi is a gzipped tarball. Please use the original, pristine tarball as provided by upstream unless you have a specific reason for repacking (i.e. DFSG conformance). Regards, Vincent -- 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/caczd_tdkrmmspi9yb6bt9n812b+thujewq1vicauunmpvp+...@mail.gmail.com
Re: RFS: confiture/2.0-1
Hi Antoine,
On Mon, May 12, 2014 at 2:54 PM, Antoine Millet wrote:
> Hi,
>
> As this is my first post here, I'll start by introducing myself:
I've cc-ed you in case you aren't subscribed to the list. Let me know
if you are so I can drop it.
> I'm a french Python developer and Debian user since several years. I
> did a lot of Debian packaging in my current company and for my own
> usage, but I never submitted my packages into Debian.
>
> I want to start doing this, in a first time by submitting my own
> library and software packages, and, depending on my spare time, by
> helping the team by providing some work force for other packages (yep, I
> also apply to join the team!).
>
> Here is the mentors page of the first package for which I request a
> sponsorship: http://mentors.debian.net/package/confiture
I've briefly reviewed your packaging and can't find any issues with it
(it's pretty much the textbook example of pybuild/dh-python usage
though), although if you intend on maintaining it within the DPMT
(Debian Python Modules Team), please add Vcs-{Browser,Svn} links in
debian/control. You'll have to join the DPMT/PAPT on Alioth first [1]
first, however.
> This is a library I wrote to parse configuration files in Python and
> which is used as dependency for other projects[1][2] that I wish to
> include in Debian.
My one concern at this point is that I'm not sure how your library
differs from the various other packages that are already in the Debian
archive (e.g. "aptitude search parse"); I wouldn't be surprised if
there's some degree of overlap. I mean no offense by this, but I'm
somewhat reluctant to sponsor small "vanity" packages into Debian
because more often than not, they end up just bitrotting in the
archive once the author loses interest in it (or Debian, for that
matter), especially if nobody else actually uses the package / there's
no real user demand for it.
However, we do have plenty of packages and teams in Debian that could
use an extra set of helping hands, and you are definitely more than
welcome to join the team and assist with team-maintained packages. I'm
certain that there are lots of packages in the DPMT/PAPT that could
use some extra love, especially those with RC bugs and/or inactive
uploaders; you can see [2][3] for a full list of packages we maintain,
some of which may interest you.
Regards,
Vincent
[1] https://wiki.debian.org/Teams/PythonModulesTeam/
[2]
http://qa.debian.org/developer.php?login=python-modules-t...@lists.alioth.debian.org
[3]
http://qa.debian.org/developer.php?login=python-apps-t...@lists.alioth.debian.org
--
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/CACZd_tBXV2ryhbh4=qxfsrdp9mrwrdpezkhjbyjzygczycg...@mail.gmail.com
Re: RFS: confiture/2.0-1
On Tue, May 13, 2014 at 11:11 AM, Antoine Millet wrote:
> On Mon, 2014-05-12 at 22:16 -0700, Vincent Cheng wrote:
>> Hi Antoine,
>
> Hi Vincent,
>
>> I've cc-ed you in case you aren't subscribed to the list. Let me know
>> if you are so I can drop it.
>
> I already subscribed to the list, so you can drop it.
>
>> (it's pretty much the textbook example of pybuild/dh-python usage
>> although if you intend on maintaining it within the DPMT
>> (Debian Python Modules Team), please add Vcs-{Browser,Svn} links in
>> debian/control. You'll have to join the DPMT/PAPT on Alioth first [1]
>> first, however.
>
> I requested to join on Alioth, but an admin answered me to post here.
You'll have to be approved for membership into the DPMT/PAPT before
you'll get commit access to our svn packaging repos. If you've gotten
no further response, I suggest pinging the team admins on IRC (I think
Piotr is one of the admins?).
>> My one concern at this point is that I'm not sure how your library
>> differs from the various other packages that are already in the Debian
>> archive (e.g. "aptitude search parse"); I wouldn't be surprised if
>> there's some degree of overlap. I mean no offense by this, but I'm
>> somewhat reluctant to sponsor small "vanity" packages into Debian
>> because more often than not, they end up just bitrotting in the
>> archive once the author loses interest in it (or Debian, for that
>> matter), especially if nobody else actually uses the package / there's
>> no real user demand for it.
>
> I understand your concern, and I know that all I can say will be tainted
> by the fact that I'm also the author of this library.
>
> I started this project because I was not able to find anything like that
> in the Python ecosystem. The most similar project is ConfigObj, but the
> syntax of parsed files is significantly different and the way to validate
> too.
>
> I also maintains a Debian package for this library on my own repository
> since the beginning of the project (2 years ago) and imho, doing this
> work for Debian is probably more productive than doing it in my little
> corner.
>
> Finally, the library is not only used by me. I got some emails from users
> about bugs and suggestions, I also got issues and PR on Github, and the
> library has beeny packaged on some distro by other people (Archlinux[1]
> and Frugalware[2]).
In case nobody on this list is interested in your package, perhaps
you'd like to consider asking for sponsorship on other Debian
channels, e.g. debian-ment...@lists.debian.org, the
sponsorship-requests pseudo-package/bug tracker, or #debian-mentors on
OFTC?
>> However, we do have plenty of packages and teams in Debian that could
>> use an extra set of helping hands, and you are definitely more than
>> welcome to join the team and assist with team-maintained packages. I'm
>> certain that there are lots of packages in the DPMT/PAPT that could
>> use some extra love, especially those with RC bugs and/or inactive
>> uploaders; you can see [2][3] for a full list of packages we maintain,
>> some of which may interest you.
>
> I would be glad to help. Is updating some package to the latest upstream
> version a good way to start?
Sure, assuming it's team-maintained and nobody else is already working
on it. Bug fixing/triaging is also another great way to start
contributing. :)
Regards,
Vincent
--
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/caczd_tcwxfukbj4j5dg+1pqdfnjeypndo_eexkgya_w+wdh...@mail.gmail.com
Re: Join the Team
Hi Hugo, On Sat, May 17, 2014 at 12:55 PM, Hugo Lefeuvre wrote: > Hi, > > I've made a request on alioth to join the team. But, I think it's > important to introduce myself to the other members of the team. Welcome (in advance) to the team! Please let me know if you're subscribed to the list, so I can stop cc-ing you. > So, I'm a french student who will help the Debian project. I'm using > Debian for several years, and I like programming (Python naturally, C++ > and Perl), but I have no skills in Debian packaging. So, I'm here to > learn. :) An excellent hands-on guide to learning Debian packaging is Lucas Nussbaum's packaging-tutorial (either apt-get install packaging-tutorial, or fetch it online [1]), and I strongly recommend it. There's also maint-guide ([2], or install it through apt), which is more comprehensive. > I have a lot of free time. For the moment, I've decided to adopt the > kupfer package (#741022), but I would like to adopt other packages in > the future. Great! You'll have to be accepted to the DPMT/PAPT in alioth first before you'll have commit access to the svn repos. If you need somewhere to upload your packages prior to asking for a review, I suggest using mentors.debian.net [3]. Regards, Vincent [1] https://www.debian.org/doc/manuals/packaging-tutorial/packaging-tutorial.en.pdf [2] https://www.debian.org/doc/manuals/maint-guide/ [3] http://mentors.debian.net/intro-maintainers -- 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/CACZd_tD06WSKK7y-rzcaVs1qkbk+h9Ysc8svbwVY8GkpNYXF=w...@mail.gmail.com
Re: python-setproctitle - Abandoned?
On Sun, May 18, 2014 at 1:34 AM, Matt Grant wrote: > Hi All! > > Just wanting to check in on what to do. > > I have an application package in an ITP dms that would benefit from the > python3 version of python-setproctitle being packaged for use by its > daemon. > > I have tired contacting the maintainer of the module Örjan Persson > a number of times, but have not received any answers. > It has been about a year or so since I first tried from work, and has > not responded to my email of the 6/3/2014 > > What would be required before this module could be claimed by the Debian > Python Modules Team? Is there a procedure for this? Contact the MIA team [1], ask for the package to be orphaned, and proceed to adopt the package and maintain it within the DPMT (usually by setting DPMT as maintainer, and you as uploader). The entire process is more thoroughly documented in devref §7.4 [2]. Regards, Vincent [1] https://wiki.debian.org/Teams/MIA [2] https://www.debian.org/doc/manuals/developers-reference/beyond-pkging.html#mia-qa -- 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/caczd_tbcbyt-rkzlryz_307ivk9tasdtobdy3nro_va2zyc...@mail.gmail.com
Re: Join the Team
On Sun, May 18, 2014 at 5:28 AM, Hugo Lefeuvre wrote:
> Hi Vincent,
>
>> Welcome (in advance) to the team! Please let me know if you're
>> subscribed to the list, so I can stop cc-ing you.
>
> Thank you ! I've made it.
>
> I've already followed Lucas Nussbaum's tutorial for a week (which is
> very interesting), but I made a mistake in my latest email: With
> 'I have no skills in Debian packaging', I wanted to say that I had no
> experience in maintaining Debian packages. :)
>
>> Great! You'll have to be accepted to the DPMT/PAPT in alioth first
>> before you'll have commit access to the svn repos. If you need
>> somewhere to upload your packages prior to asking for a review, I
>> suggest using mentors.debian.net [3].
>
> I'll upload my patch for the kupfer package in mentors.debian.net. I've
> already an account (with the username hugo6390).
For the purposes of this review, I'm going to assume that what you
uploaded is this source package (since you didn't give a direct link):
http://mentors.debian.net/debian/pool/main/k/kupfer/kupfer_0+v208-3.dsc
- Your new upload has to have a different version number than past
uploads. kupfer/0+v208-3 was already uploaded on 2013-12-19 by Luca
Falavigna; you should instead be using version 0+v208-4 instead.
- Please revert your changes to debian/watch; your watch file doesn't
work (404; use uscan(1) to verify).
- Please revert your changes to Vcs-{Svn,Browser} in debian/control:
the original Vcs-* links are correct and are the canonical Vcs links
that you should be using in d/control. [1]
- Please revert the rest of your changes to debian/control (having a
single build-dep/dependency on each line makes it much easier to see
what changed with a diff in between uploads; wrap-and-sort(1) from the
"devscripts" package helps to format debian/control like what it is
currently. Don't "un-"wrap-and-sort the package...
- Please set DPMT as maintainer, and you as uploader (instead of the
other way around).
The only remaining change now is your removal of a number of patches
applied to the package (almost every other change you made is bogus
and should be reverted, sorry). A few comments about this:
- Please document this in debian/changelog
- Why did you remove these patches? Include a brief rationale in d/changelog.
Regards,
Vincent
[1] http://lintian.debian.org/tags/vcs-field-not-canonical.html
--
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/caczd_tcmk2lzqmsnn7c4jhwxy4jw+d_9d6uheyj5x-orf7o...@mail.gmail.com
Re: Request to join python-apps
Hi Alexander, On Mon, May 19, 2014 at 12:05 PM, Alexander Alemayhu wrote: > Hei, > > I was on the #debian-python IRC channel on irc.efnet.org earlier. I want to irc.efnet.org? Don't you mean OFTC (or its alias irc.debian.org)? > join the python-apps team and have already sent a request in the web interface > on alioth. My intention is to adopt postr[0] within the team and maintain it > together with Yoann Gauthier. Is there any official process to adopting a > package within a team after joining? > > [0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711833 If you intend to join the PAPT, please create an account on Alioth [1] and join the team there in order to get commit access to our svn repos; more info at [2]. I suggest uploading the package to mentors.debian.net (definitely read [3] first) as well to make it easier to review your package. Regards, Vincent [1] https://alioth.debian.org/ [2] https://wiki.debian.org/Teams/PythonAppsPackagingTeam [3] http://mentors.debian.net/intro-maintainers -- 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/CACZd_tB7+m2=2L7Z4HhHmypRu=y5jz1jnReYtgss3ixM4=x...@mail.gmail.com
Re: Join the Team
On Wed, May 21, 2014 at 12:23 PM, Hugo Lefeuvre wrote: > Hi Vincent, > > I've uploaded the new version on mentors.debian.net. [0] > It should be good now. :) > > [0] http://mentors.debian.net/package/kupfer These are rather pedantic issues, but I encourage you to be a bit more verbose in d/changelog; instead of just "New Maintainer and co-maintainer", spell out the fact that you've added the PAPT as the maintainer (and you as uploader). Same thing w.r.t. your "debian/copyright" line. You also have a trailing comma in your Uploaders line in d/control. Can you please commit your changes to the svn repo? Regards, Vincent -- 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/caczd_tapdrbo5e3z24hckn6bfumokpd5+krcy-pnt_y7fox...@mail.gmail.com
Re: Join the Team
On Thu, May 29, 2014 at 2:05 AM, Hugo Lefeuvre wrote: > Hi Vincent, > > I've commited my changes to the SVN repo. It should be good now. I've > also released and tagged the new version. Built, signed, and uploaded; thanks for your contribution to Debian! Regards, Vincent -- 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/caczd_tawqyehowxkj1emvphda77frhx4ynf7sa4z1cb7zap...@mail.gmail.com
Re: python-Pandocfilters
Hi Sebastian, (Please let me know if you're subscribed to the list, so I can stop cc-ing you.) On Thu, May 29, 2014 at 12:59 PM, Sebastian Humenda wrote: > Hello, > > I have prepared a package for python-pandocfilters. AFAIT, it should > correspond > to the python packaging guidelines and it builds nicely with Debhelper. BTW, > thanks to the developers and to those who documented the process, great job! > > It is Lintian-clean, but I would love to have someone looking over it, because > this is my first Python-related package. I think it would make also sense to > include it in the debian-python team repositories, if you wish. If so, please > add me on alioth (moomoc-guest), and I'll create a git repository there. Please follow the instructions at mentors.debian.net [1] to upload your package for review and file a sponsorship request. If you'd like to maintain your package within the team, you'll have to file a request to join the DPMT/PAPT on alioth (and then wait for an admin to approve your request). Note that for various reasons (feel free to dig into the list archives), DPMT/PAPT packages are only maintained in svn, so you'd have to maintain python-pandocfilters in svn, not git, if you choose to maintain it within the team. Regards, Vincent [1] http://mentors.debian.net/intro-maintainers -- 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/caczd_td4zcl28x0y2fwcwk+s55n4re0t9potxs1dse0+2_s...@mail.gmail.com
Re: policy for source package names
On Mon, Aug 4, 2014 at 2:17 PM, Antonio Valentino wrote: > Hi list, > I read in [1] and [2] that binary packages with public modules should > have the python- (or python3-) prefix in the name. > I'm wondering if the same naming rules should be used for source packages. > > I'm preparing some new packages so I would like to be sure I'm using the > correct naming before the first upload. > AFAIK, no, there aren't any hard and fast rules regarding source package names. In fact, I don't think there are any rules at all; just don't pick a source package name that's already taken, and pick one that is relevant to your package (if you take a look at existing DPMT packages [1], most of them either use their module name, or prefix it with python-). Regards, Vincent [1] https://qa.debian.org/developer.php?login=python-modules-t...@lists.alioth.debian.org -- 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/CACZd_tDoQntzD4fkw_idDL5iMSUif1=ih+LZYuQ-XkpFSf=y...@mail.gmail.com
Re: Update to Veusz 1.21.1
On Sun, Aug 31, 2014 at 6:43 AM, Jeremy Sanders wrote: > Hi - I've update Veusz from 1.20.1 to 1.21.1. This change is minor in the > packaging (updating changelog and removal of an unnecessary patch). > > If anyone has time, could you please give me feedback or upload it? Debdiff looks fine, uploaded; thanks for your contribution to Debian! > There's further future possibility to add py3 support, but this will require > further splitting of the package, e.g. into veusz-data, > python-veusz-support, python-veusz, python3-veusz and veusz (the > application). Before commenting on your proposed package split, I'd just like to point out that you don't have to feel compelled to add py3 support to your python application when there's no tangible benefit to users (as opposed to python modules, of course), although I don't know enough about veusz to say whether this is the case or not. Regards, Vincent -- 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/caczd_tc+yi79wopvzw+xf4cddrnunlyy_bghui5grikaj2r...@mail.gmail.com
Re: Could you take over my package Kivy?
Hi Bastian, On Sun, Nov 9, 2014 at 8:30 AM, Bastian Venthur wrote: > Dear Python team, > > I'm currently unable to maintain the kivy package properly, as I am > busy writing my Ph.D. Could I kindly ask you to take over this package? I'd be glad to take the role as an uploader for kivy and maintain it under the DPMT's umbrella. In fact I had suggested this a while ago in #737351, but you never replied, so I just assumed that you weren't interested in team maintenance at all. Glad to see that I was mistaken! Regards, Vincent -- 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/CACZd_tAq8UqxfN4wFt8cQFTk0LVwKAMGMtRz5zwowxmXEvD=q...@mail.gmail.com
Re: Looking for a sponsor, just dput python-django-bootstrap to mentors.debian.net
Hi Caio,
On Fri, Dec 5, 2014 at 6:45 AM, Caio Begotti wrote:
> Hi everyone! I just dput python-django-bootstrap to
> https://mentors.debian.net/package/django-bootstrap3 and marked it as
> needing a sponsor to review it etc. Would you be interested in it?
>
> I was not sure if this team had a different policy for RFS or what, so I
> decided to send this e-mail anyway hoping you guys would let me know if I
> did the wrong thing :-)
AFAIK there's no team-specific RFS policy. From what I've seen though,
sponsorship within the DPMT/PAPT often takes place via IRC (OFTC,
#debian-python), and relatively few RFS requests come through the
mailing list. I only saw this because I'm trying to work through my
email backlog at the moment...
Anyways, here's a quick review of your package:
- please file an ITP bug report [1] and close it in debian/changelog.
New packages should only have a single, short changelog entry
(typically something like "Initial release (Closes: #xx)").
- debian/clean seems to be redundant with your override target in d/rules
- Vcs-{Svn,Browser} is missing in d/control; please apply for access
to the DPMT's svn repo at Alioth and upload (and maintain) your
package there, then add the missing Vcs-* fields to d/control
- I suggest following DEP-5 [3] for d/copyright, but that's up to you.
However, you should either have the full upstream license text in
d/copyright, or if it's a license available in
/usr/share/common-licenses, explicitly provide a link to the
appropriate license file. You also seem to be missing a
copyright+license statement for the packaging itself (debian/*).
- some issues caught by lintian that you can easily fix:
P: django-bootstrap3 source: no-dep5-copyright
P: python-django-bootstrap: no-upstream-changelog
I: python-django-bootstrap: extended-description-is-probably-too-short
I: python-django-bootstrap: possible-documentation-but-no-doc-base-registration
(HISTORY.rst looks like an upstream changelog to me)
- the build log contains a bunch of import errors when the docs are
built (i.e. "ImportError: No module named django") - missing
build-dep?
Regards,
Vincent
[1] https://www.debian.org/devel/wnpp/
[2] https://alioth.debian.org/project/request.php?group_id=30714
[3] https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
--
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/CACZd_tAFrNBsjsBQr9j2HB3t8-J7CeP+xwRyjgq-E=mkr5v...@mail.gmail.com
Re: Kivy packages at Debian
Hi Thomas, > Am 25.01.2015 um 15:24 schrieb Thomas Pietrowski: >> Hello, >> >> my name is Thomas-Karl Pietrowski. I'm working for the kivy project on >> the Ubuntu packages. I found many differences between on my and your >> packages, which now are also landing in Ubuntu. >> If you are interested you can take a look at the latest debian/* files >> at https://github.com/kivy/kivy/tree/pkg-debian-daily . The kivy package currently in Ubuntu (15.04/vivid) [1] is identical to the package that we have in Debian [2], and has been kept in sync since trusty was released, so it looks like it's not a matter of keeping the Debian and Ubuntu packages in sync (as Bastian seems to be suggesting), but rather, keeping the Debian/Ubuntu packages in sync with upstream-provided PPA packages? I'll make a note to myself to take a closer look at the diff between the official Debian/Ubuntu packages, and the packaging in the above github repo (which I presume is being used for a PPA?), but at first glance there does seem to be major differences that may make syncing this more trouble than it's worth (e.g. package names; getting them in sync means adding a mess of breaks+replaces relationships and regular testing to ensure a smooth upgrade path between Ubuntu<->PPA). Strictly speaking PPAs aren't officially supported to begin with, so the easy way out would be to just say that the Ubuntu packages aren't compatible with upstream-provided PPA packages... Regards, Vincent [1] https://launchpad.net/ubuntu/+source/kivy [2] https://packages.qa.debian.org/k/kivy.html -- 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/CACZd_tDKc+6K4GqeaPiSnwVjOs0V=mqxon_ffgcasmqu5if...@mail.gmail.com
Re: [Python-modules-team] pygame and python 3
Hi, pygame maintainer here, sorry for the delayed reply! On Thu, Apr 16, 2015 at 6:47 PM, peter green wrote: > One python package used heavilly in the raspberry pi community is pygame. > Unfortunately the package hasn't had an upstream stable release since 2009 > and the upstream stable release doesn't support python3. > > Currently sid has the latest upstream stable release and no python3-pygame > package. Experimental does have a python3-pygame package but I have not > tested it (i'm not really a python guy myself). > > Thoughts? has anyone tried the pythong3-pygame package in experimental? > should it be pushed to unstable (after jessie release)? are there better > alternatives to pygame? Yes, I've tested the python3-pygame package (briefly) prior to uploading it to experimental, and it is indeed functional. The reason it's in experimental and not unstable is because I'd rather not upload a snapshot of upstream svn/hg to sid (I have no idea when upstream is planning to release 1.9.2). When 1.9.2 is released, I'll push the current packaging in experimental to sid. There's also an upstream bug report about python3 support in the Debian package [1], although there's really nothing new there. Regards, Vincent [1] https://bitbucket.org/pygame/pygame/issue/221/debian-python-3-package-for-192 -- 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/caczd_tcqwof3cggxvaakk25r1fc1c_bvbjyeoqzcuf7xvw0...@mail.gmail.com
Re: [Python-modules-team] pygame and python 3
Hi Lenard, First off, thanks for all your work on pygame! On Thu, Apr 16, 2015 at 9:26 PM, Lenard Lindstrom wrote: > Hi, > > Pygame supported python3 since before version 1.9.0 in 2009. All Pygame code > is written to work with either Python 2.x or 3.x. So building Pygame for > python3 is the same as for python2. Just use "python3 setup.py build" > instead of "python setup.py build". Installation is also the same. For > Pygame 1.9.2, which I > test against Python 2.7 and 3.4 on i386 Linux Mint, python3 support is > complete. > > So if a stable Pygame package already exists for python2, adapting it for > python3 should be straight forward. Let me know if some Pygame bug causes > problems and I will deal with it promptly. > > Thanks for the effort in keeping Pygame in Linux. Just to confirm, does the latest stable pygame release (1.9.1) actually support python3? Because back when I initially prepared python3 pygame 1.9.1 packages for Debian a few years back, I recall that I was able to build it, but just importing pygame with a python3 interpreter resulted in an error. 1.9.2pre works great though. Is there a rough estimate of when 1.9.2 is expected to be released, by the way, or is it more along the lines of "it'll be done when it's done"? ;) Regards, Vincent -- 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/caczd_taf_zdtzoqehy9tznwmnczciws2dnxxwzaokqteas3...@mail.gmail.com
Re: [Python-modules-team] pygame and python 3
Hi Lenard, On Mon, May 4, 2015 at 5:47 PM, Lenard Lindstrom wrote: > Hi Vincent, > > > On 15-04-29 03:34 AM, Vincent Cheng wrote: >> >> Hi Lenard, >> >> First off, thanks for all your work on pygame! >> >> On Thu, Apr 16, 2015 at 9:26 PM, Lenard Lindstrom wrote: >>> >>> Hi, >>> >>> Pygame supported python3 since before version 1.9.0 in 2009. All Pygame >>> code >>> is written to work with either Python 2.x or 3.x. So building Pygame for >>> python3 is the same as for python2. Just use "python3 setup.py build" >>> instead of "python setup.py build". Installation is also the same. For >>> Pygame 1.9.2, which I >>> test against Python 2.7 and 3.4 on i386 Linux Mint, python3 support is >>> complete. >>> >>> So if a stable Pygame package already exists for python2, adapting it for >>> python3 should be straight forward. Let me know if some Pygame bug causes >>> problems and I will deal with it promptly. >>> >>> Thanks for the effort in keeping Pygame in Linux. >> >> Just to confirm, does the latest stable pygame release (1.9.1) >> actually support python3? Because back when I initially prepared >> python3 pygame 1.9.1 packages for Debian a few years back, I recall >> that I was able to build it, but just importing pygame with a python3 >> interpreter resulted in an error. 1.9.2pre works great though. >> >> Is there a rough estimate of when 1.9.2 is expected to be released, by >> the way, or is it more along the lines of "it'll be done when it's >> done"? ;) >> >> Regards, >> Vincent > > I checked Pygame 1.9.1 with Python 3.4 and see where the problem is. Pygame > 1.9.1 was built and tested on an earlier Python 3 release. Basically, the > early effort on Python 3 went towards the language upgrade. The C api was > slower to follow. So Python 3 is basically a moving target for extension > module developers. I suppose Pygame 1.9.1 could be updated for Python 3.4, > but is it worth it? > > For practical purposes, Pygame 1.9.2 is in the beta stage of testing. I see > no new features or rewrites happening before the formal release, just bug > fixes. Basically the delay in release is one of logistics, getting a new > automated build site for Windows and OS X. But for Linux, specifically Linux > Mint 17.1 Cinnamon 32-bit (Ubuntu 14.04.2 LTS, Trusty Tahr), it passes the > unit tests. Other than some document editing, I think it is as ready as it > will ever be for a Linux release. As for the date of the formal release, > that is up to the project administrator, René Dudfield. Thanks for the explanation! I don't follow upstream development closely, and I was unsure how close to release 1.9.2 actually is. In that case, would you consider 1.9.2 as of the last commit on bitbucket (or any specific commit if you want to suggest one, I suppose) ready for inclusion in a stable release of Debian/Ubuntu? If so, I'd be happy to upload 1.9.2 to unstable rather than just experimental. Regards, Vincent -- 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/caczd_tafimejqh4+4rwqecjq6ui0o2tvnovrrmx9fvjugik...@mail.gmail.com
Re: Uploading pyusb 1.0.0~b2 to unstable
Hi Ruben,
On Wed, Jun 17, 2015 at 3:52 PM, Ruben Undheim wrote:
> Hi,
>
> Could someone in the Python Modules Team help me get the version of
> pyusb in experimental uploaded to sid.
>
> I've prepared the package here:
>
> https://mentors.debian.net/package/pyusb
>
> It also contains python3-usb which people are waiting for.
> See:
> http://bugs.debian.org/787792
> https://bugs.launchpad.net/ubuntu/+source/pyusb/+bug/1366285
>
Please push your changes to svn first.
Just a quick review: debian/pyversions is unneeded since you already
have X-Python{,3}-Version stanzas in d/control. Also, consider using
pybuild [1]; it'll greatly simplify your d/rules, and you already have
a build-dep on dh-python anyways.
Regards,
Vincent
[1] https://wiki.debian.org/Python/Pybuild
--
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/caczd_taw2wu4mtgyokubmjncbp9zqcywz-kyspbuhmy5mac...@mail.gmail.com
Re: Uploading pyusb 1.0.0~b2 to unstable
On Thu, Jun 18, 2015 at 12:39 PM, Ruben Undheim wrote: > Hi, > > I've done the suggested changes and reuploaded to mentors. > > However, I'm not able to push to the svn repository. It's strange, I > get "Authorization failed" even though I'm a member of the scm_python-modules > alioth group. I've never used svn on alioth before, only git. > > I checked out the following url: > svn://rubund-gu...@svn.debian.org/python-modules/packages/pyusb The url you're using is incorrect, try this instead: svn://rubund-gu...@svn.debian.org/svn/python-modules/packages/pyusb Regards, Vincent -- 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/CACZd_tB0thtnoXYRgfhu67107iPQx+dZ2N0Wqub7HP=3u6f...@mail.gmail.com
Re: Uploading pyusb 1.0.0~b2 to unstable
Hi Bernd, Are you stepping down as uploader for pyusb? You've been recently de-listed as uploader in pyusb's svn repo, and I just wanted to confirm that this was done with your consent. Thanks for all the work you've put into maintaining pyusb! Regards, Vincent -- 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/CACZd_tDiNEVv1a1SjaPXMj1m==zph9_rzca4c3rif--egir...@mail.gmail.com
Re: Uploading pyusb 1.0.0~b2 to unstable
On Fri, Jun 19, 2015 at 10:32 PM, Bernd Zeimetz wrote: > Hi, > > Yes, I don't use it anymore so it would be great if you could take care of > it. Ruben removed me after I suggested to do so. Ack, thanks for the reply. Ruben, I've gone ahead and uploaded pyusb to sid; thanks for your work! Regards, Vincent -- 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/caczd_tdoxfk1voxx6udbteb+f23jkq5ghxb+w_h0x8sbhxe...@mail.gmail.com
Re: RFS: terminado -- a tornado websocket backend for the term.js javascript terminal emulator library
Hi Julien, On Fri, Aug 14, 2015 at 8:41 AM, Julien Puydt wrote: > Hi, > > * Package name: python-terminado > Version : 0.5 > Upstream author : Thomas Kluyver > * URL : https://github.com/takluyver/terminado > License : BSD > Description : a tornado websocket backend for the term.js javascript > terminal emulator library > > It's one of the deps for the new ipython 3 ; I prepared a package, for > review & sponsoring here : > ssh://git.debian.org/git/python-modules/packages/terminado.git The upstream contents of your git repo isn't identical to the tarball I fetched with uscan --download-current-version. Also, d/rules seems to include some unused variables (PYVERS and PY3VERS)? I haven't been keeping up with the list recently...have we already migrated to git, or are we already allowed to use git repos for packaging? Regards, Vincent
Re: RFS: terminado -- a tornado websocket backend for the term.js javascript terminal emulator library
On Fri, Aug 21, 2015 at 12:25 PM, Julien Puydt wrote: > Hi, > > On 21/08/2015 10:42, Vincent Cheng wrote: >> >> Hi Julien, >> >> On Fri, Aug 14, 2015 at 8:41 AM, Julien Puydt >> wrote: >>> >>> Hi, >>> >>> * Package name: python-terminado >>>Version : 0.5 >>>Upstream author : Thomas Kluyver >>> * URL : https://github.com/takluyver/terminado >>>License : BSD >>>Description : a tornado websocket backend for the term.js >>> javascript >>> terminal emulator library >>> >>> It's one of the deps for the new ipython 3 ; I prepared a package, for >>> review & sponsoring here : >>> ssh://git.debian.org/git/python-modules/packages/terminado.git >> >> >> The upstream contents of your git repo isn't identical to the tarball >> I fetched with uscan --download-current-version. > > > Uh... and I "diff -urN" both trees and they're not identical!? I just > updated my package, but it's puzzling... would upstream have updated the > tarball under my feet ? Another possibility is that you may have actually imported terminado from github instead of pypi. Either way, please ensure that your orig tarball matches up with whatever uscan spits out for future uploads. Uploaded to NEW, thanks! Regards, Vincent
Re: Pushing a bunch of packages to jessie-backports
Hi Piotr,
On Thu, Nov 26, 2015 at 7:09 AM, Piotr Ożarowski wrote:
> [Piotr Ożarowski, 2015-11-26]
>> that's the first mistake most backporters do, they forgot to include orig
>> tarball
>> (ftp masters would detect that and reject your package, additional work for
>> them)
>>
>> solution: pass -sa to dpkg-source ("--force-orig-source" in sbuild or
>> "--debbuildopts -sa" in pbuilder)
No, that's not necessary as long as the orig tarball is already
present in the archive in another suite (which would be true for
backports, since the package is supposed to be derived from the
current version in testing).
> the second one is missing changelog items and your packages have this one too.
>
> solution: pass -vFOO to dpkg-source (where FOO is version in stable)
> ("--force-orig-source --debbuildopt -vFOO" in sbuild and
> "--debbuildopts '-sa -vFOO'" in pbuilder)
No, the -v flag is no longer required as of April of this year [1]. It
is merely "recommended" now [2].
Regards,
Vincent
[1] https://lists.debian.org/debian-backports-announce/2015/04/msg0.html
[2] http://backports.debian.org/Contribute/#index7h3
Re: Pushing a bunch of packages to jessie-backports
Hi Piotr, On Thu, Nov 26, 2015 at 7:02 AM, Piotr Ożarowski wrote: >> I've uploaded all what I prepared to this URL: >> http://sid.gplhost.com/bpo/ > > THANK YOU! > [build log snipped] > that's why I don't believe you built it in jessie. python-sphinx is not > backported > and you didn't mention any patches > > solutions: > 1) backport python-sphinx, or > 2) use patch from Ubuntu: > https://patches.ubuntu.com/r/routes/routes_2.2-1ubuntu1.patch Backports packages are allowed to build-dep on other backported packages of the same suite (i.e. you can build packages destined for jessie-backports in a chroot with packages from both jessie and jessie-backports to satisfy build dependencies). Given that Thomas has already mentioned in the very beginning of this thread that he intends on backporting sphinx to jessie-backports as well (which satisfies the unmet build-dep above), I think it's safe to assume that he will be uploading packages to backports in the necessary order to satisfy build dependencies. FWIW, I see no *technical* reason to reject Thomas' backported packages. It looks to me that he's done everything he needs to do according to the backports rules, and that you're imposing additional requirements that (strictly speaking) he doesn't have to meet (i.e. providing debdiffs for every backports upload). Regards, Vincent
Re: Bug#967174: monster-masher: Unversioned Python removal in sid/bullseye
+ debian-python On Tue, Aug 4, 2020 at 2:32 AM Matthias Klose wrote: > > Package: src:monster-masher > Version: 1.8.1-8 > Severity: serious > Tags: sid bullseye > User: debian-python@lists.debian.org > Usertags: py2unversioned > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html > > We will keep some Python2 package as discussed in > https://lists.debian.org/debian-python/2020/07/msg00039.html > but removing the unversioned python packages python-minimal, python, > python-dev, python-dbg, python-doc. > > Your package either build-depends, depends on one of those packages. > Please either convert these packages to Python3, or if that is not > possible, replaces the dependencies on the unversioned Python > packages with one of the python2 dependencies (python2, python2-dev, > python2-dbg, python2-doc). > > Please check for dependencies, build dependencies AND autopkg tests. > > If there are questions, please refer to the wiki page for the removal: > https://wiki.debian.org/Python/2Removal, or ask for help on IRC > #debian-python, or the debian-python@lists.debian.org mailing list. src:monster-masher has no build dependencies on python2, the only binary package it builds (monster-masher) has no runtime dependencies on python2, and this package has no autopkgtests. There's actually not a single line of python in this package. Can I go ahead and close this bug, or have I missed something? Regards, Vincent
Re: review for kivy/2.1.0-1
Hi Dean, Thanks for doing the heavy lifting in getting kivy/2.1.0-1 ready for upload! I'm currently going through all of the packages that I (co-)maintain in preparation for the upcoming freeze, and you've saved me a ton of work here! I've pushed a few very minor changes to the packaging, but otherwise I think this is ready for upload; if Jeroen isn't planning on uploading kivy in the next day or so, I'd be happy to do so myself. I also invite you to add yourself as an Uploader in d/control if you anticipate maintaining kivy in the future. One thing I wanted to bring up before actually uploading kivy is that you've added a new (emacs-specific) binary package, and adding a new binary package will force kivy to take a round-trip through the NEW queue. While that's not usually a problem, since we're so close to the freeze, there's a risk that ftpmasters may not be able to review it in time before the freeze takes effect. Would you consider either merging the contents of elpa-kivy-mode into python3-kivy, or defer adding the new package for a subsequent upload? Thanks! Regards, Vincent
