RFS: PAPT: pyspread 0.1.2-1
Would a sponsor please take a look at the package pyspread in the PAPT svn repo? ITP: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601950 Regards Andreas Noteng signature.asc Description: OpenPGP digital signature
Re: Help in packaging rubber
On 02. mai 2012 23:39, Hilmar Preusse wrote: > Dear python maintainers, > > I intend/plan to adopt the rubber package[1]. I prepared a package > for testing, it is available from here[2]. > > When building the package two warnings occur: > > - dh_pysupport: This program is deprecated, you should use dh_python2 > instead. Migration guide: http://deb.li/dhs2p Make sure you removed python-support from the dependencies, also make sure your rules file calls dh --with python2 (often this is enough: %: dh $@ --with python2 ). Depending on the complexity of your package, you might need to remove any references to python-support in your debian/rules > - dpkg-deb: warning: 'debian/rubber/DEBIAN/control' contains user-defined > field 'Python-Version' It should be X-Python-Version > > Yes, I've read http://deb.li/dhs2p, but I'm failing to understand > what I have to do in the "Before you begin" section. Unfortunately I > don't speak python myself, this might be the reason. > > Please be so kind to teach me, what needs to be changed. Please keep > me in Cc, I'm not subscribed. > Python sponsors tend to be picky; I'd recommend running lintian -Iv --pedantic on the resulting .changes file after building. It'd likely save you a couple of mails back and fourth with the sponsor. Regards -- Andreas Noteng signature.asc Description: OpenPGP digital signature
Re: Help in packaging rubber
On 03. mai 2012 22:54, Hilmar Preusse wrote: > Attached is the patch documenting the changes I've applied. Is this > OK? The patch does not seem to apply to the revision currently in Debian. If you plan to maintain this package I'd strongly recommend joining the PAPT [1], and using the PAPT svn repository and svn buildpackage. This would ease the process of helping you, and later for the sponsors to review your package. I'd also recommend subscribing to this list.. [1]: http://wiki.debian.org/Teams/PythonAppsPackagingTeam Regards -- Andreas Noteng signature.asc Description: OpenPGP digital signature
Re: Help in packaging rubber
On 04. mai 2012 12:01, Hilmar Preuße wrote: > Correct. It applies to a preview for a new upload, which is on my PC. > I just wanted to document, which changes I've applied for the > dh_pysupport -> dh_python2 migration. It's kind of hard to say without seeing the whole package, but if you get it into SVN it'll be easy to see. > I just sent the join request on alioth (https://a.d.org/projects/python-apps/) > Should I make the package team managed, i.e. > python-apps-t...@lists.alioth.debian.org as maintainer? python-apps-t...@lists.alioth.debian.org should be in either maintainer or uploaders. -- Andreas Noteng signature.asc Description: OpenPGP digital signature
Package upgrade needs deletion of config file in ~/
Hello. What is the preffered way of handling situations where a configuration file in ~/ needs to be deleted upon package upgrade? Regards Andreas Noteng -- 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/511a4ff1.9070...@noteng.no
Re: Package upgrade needs deletion of config file in ~/
Den 12. feb. 2013 16:04, skreiv Yaroslav Halchenko: fresh entry in debian/NEWS and probably debian/changelog ? Thanks. I've done this now, along with a friendly message upstream begging for these changes to be handled more elegantly by the application in the future. Andreas -- 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/511aa3b6.9060...@noteng.no
Re: How does team maintenace of python module works?
Den 19. feb. 2013 18:55, skreiv Thomas Goirand: If the above isn't correct, please let everyone know your view. Thomas My contribution to this team is relatively low volume, but anyways: My vote is, in order of preference, DCAB. I'd also be happy with bzr (which I use for my Ubuntu stuff), but IMHO git is the most useable vcs for Debian packaging. Regards Andreas Noteng -- 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/5123e646.9050...@noteng.no
Re: How does team maintenace of python module works?
Den 20. feb. 2013 16:23, skreiv Thomas Goirand: If that doesn't work, you can use the pristine-tar thing, that should always work. I never used it, probably I should learn, it seems quite convenient. Can anyone give feedback about it? My workflow for anything outside of this team and not intended for Ubuntu directly is with git and a full source branch. I don't package often enough to remember everything from time to time, but it's no more than a quick google search away. Roughly the workflow is to use uscan to download the source tarball, git-import-orig with pristine tar to import upstream code into upstream branch. git-import-orig handles committing an tagging necessary changes. Using quilt I can then modyfi anything I like in the source directories, and quilt will keep every change in the debian/patches folder. If I accidentally touch anything not handled by quilt this is easily reverted with a single-file checkout. When I'm happy with the changes I build the package using git-buildpackage (--git-ignore-new if I want to test before commit) --git-builder=pdebuild. Once I'm ready to upload the debian release commit is tagged. Because of pristine tar, the upstream release tarball can be recreated from the upstream branch, and everybody should be happy. IMHO patching and patch handling is way easier in git than in svn, mostly because I never copy or export anything to create and test the patches. I totally agree that all changes to the source should be kept as patches. Regards Andreas Noteng -- 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/512506c1.8030...@noteng.no
Re: About canonical Vcs fields
Den 14. mars 2013 15:01, skreiv Scott Kitterman: 3. Don't care to invest any thought or time in the question. Scott K Agreed. -- 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/51424dd5.1040...@noteng.no
RFS: Pyspread 0.2.6-1
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: 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 * Standards-Version bumped to 3.9.5 (no change) Regards Andreas Noteng -- 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/5302779e.80...@noteng.no
Re: RFS: Pyspread 0.2.6-1
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 ? Regards Andreas Noteng -- 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/53034882.3000...@noteng.no
Re: RFS: Pyspread 0.2.6-1
On 25. feb. 2014 10:53, Vincent Cheng wrote: 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. Upstream sent me a patch so that the tests no longer require msttcorefonts. Committed to SVN. Andreas -- 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/530cf656.1020...@noteng.no
Re: RFS: Pyspread 0.2.6-1
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 * 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. Regards Andreas Noteng Changes since last upload: 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 * Standards-Version bumped to 3.9.5 (no change) Regards Andreas Noteng -- 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/5314d186.2010...@noteng.no
Re: RFS: Pyspread 0.2.6-1
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. 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. Regards Andreas Noteng -- 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/531b13c6.8010...@noteng.no
RFS: python-easygui-0.98.0-1
Dear Debian Developers, Requesting review and sponsorship of python-easygui-0.98.0-1, available in the DPMT git repo. After quite some time with no updates and the upstream author announcing the project dead, development was picked up by a new upstream developer (endorsed by the original maintainer). Upstream now moved documentation to sphynx, and the documentation included in the package was thus moved from html to man. Is it ok to name the man page easygui when the Debian package name is python-easygui? Other changes to the package are made only to reflect new hosting of upstream code and web site. The package has a few lintian warnings: image-file-in-usr-lib These are images used in the easygui.egdemo() function. Having those in /usr/lib should, according to change in version 3.9.6.0 of Debian policy, be ok. Any comments and improvements are highly appreciated. I am a Debian maintainer, in case anybody feels like granting me upload permissions to the package. Sincerely Andreas Noteng signature.asc Description: OpenPGP digital signature
Re add my account?
Hello, I am a DM who have not been active for a few years, but I can still se my name in the list of DMs. Now coming back I see that quite a few things have changed. Most noteably our packages has moved to GIT it seems. Looks like I don't have access to this new host. How would I proceed to gain access and update my long neglected packages? My alioth username was anoteng-guest -- Andreas Noteng
Request to rejoin DPMT and PAPT
Hello, i was previously a member of both teams, but after a few years of inactivity I fell off the wagon during the move from Alioth to Salsa. I have read and accept both polycies, my key is still in the keyring and I have been a debian maintainer since june 2012. My Salsa username is anoteng-guest. I currently maintain the pyspread and python-easygui packages. I have just updated the pyspread package, and will start working on updating the easygui package next. I would prefer to move development to the team repos. I am very happy to see that in my time of absence the repos have changed from svn to git. Best Andreas Noteng
python-easygui upload or DM upload access request
Hello, I thought for sure I had DM upload access for python-easygui, but it turns out I didn't. Would anyone please upload for me or consider granting me DM upload access for python-easygui? The package available in DPMT repo is a new upstream release, has lots of updates to the packaging and drops the python2 package. -- Sincerely, Andreas Noteng
Upload updated python-easygui
Hi, i recently pushed an update to python-easygui fixing an FTBFS-bug recently filed. I though I had DM upload priveleges to the package, but apparently I don't. Would anyone please upload for me, or grant me upload privileges for the package? From before I have DM upload priveleges to packages transgui and pyspread, and I had on package pype before it died upstream an was removed from Debian. Sincerely Andreas Noteng Debian maintainer OpenPGP_signature Description: OpenPGP digital signature
