Merging python-jenkins from Ubuntu
Greetings list, I wanted to start discussion around merging a package from Ubuntu, python-jenkins[1], into Debian. The reason for this is it is actually a dependency for another piece of software I am hoping to package for Debian, jenkins-job-builder[2]. I'd like to go through mentors.debian.net and find sponsorship, but before I started that I wanted to send a email to the list first. I don't expect much trouble getting the packaging in shape for Debian, but I'd be interested to hear any initial feedback of this process. [1] https://launchpad.net/python-jenkins [2] https://github.com/openstack-ci/jenkins-job-builder -- Paul Belanger | PolyBeacon, Inc. Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode) Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger -- 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/callkq0sk+zn_vkqbqjwshhebtjvmgo1vwogfrdzoodz-0jd...@mail.gmail.com
Re: Merging python-jenkins from Ubuntu
On Wed, Nov 14, 2012 at 11:47 AM, Paul Belanger wrote: > Greetings list, > > I wanted to start discussion around merging a package from Ubuntu, > python-jenkins[1], into Debian. The reason for this is it is actually > a dependency for another piece of software I am hoping to package for > Debian, jenkins-job-builder[2]. I'd like to go through > mentors.debian.net and find sponsorship, but before I started that I > wanted to send a email to the list first. > > I don't expect much trouble getting the packaging in shape for Debian, > but I'd be interested to hear any initial feedback of this process. > > [1] https://launchpad.net/python-jenkins > [2] https://github.com/openstack-ci/jenkins-job-builder > As a follow up, I have already created the ITP and uploaded the package to mentors.debian.net[2]. Any sort of mentoring / sponsorship would be welcomed. Next up is the RFS. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693268 [2] http://mentors.debian.net/package/python-jenkins -- Paul Belanger | PolyBeacon, Inc. Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode) Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger -- 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/callkq0qz1_p8zymypshzjejbalvrhba0b2xxpxfeq5uspgx...@mail.gmail.com
Re: Merging python-jenkins from Ubuntu
On 12-11-16 11:49 AM, Jakub Wilk wrote: (I don't intend to sponsor this package.) I appreciate the feedback * Paul Belanger , 2012-11-14, 17:20: As a follow up, I have already created the ITP and uploaded the package to mentors.debian.net[2]. Any sort of mentoring / sponsorship would be welcomed. Next up is the RFS. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693268 [2] http://mentors.debian.net/package/python-jenkins A direct link to .dsc would have been more helpful: http://mentors.debian.net/debian/pool/main/p/python-jenkins/python-jenkins_0.2-1.dsc Lintian reports: O: python-jenkins source: unknown-field-in-dsc original-maintainer I: python-jenkins: unknown-field-in-control original-maintainer Why is that tag overridden? Fixed, I was using logic from Ubuntu when syncing a package from Debian. I've reverted the Maintainer field to the original person and added myself to Uploaders. The binary package appears to be architecture-independent, so it should be "Architecture: all" rather than "Architecture: all". Fixed. As far as I can see, "python-dev" build-dependency could be replaced by "python". Even better, make it "python-all" to work around #683557. Fixed. If I were you I would bother to provide get-orig-source target that only calls uscan... But if you really want to have it, please make it policy-compliant (§4.9), and please don't hide commands it runs. Quick question, the most comment syntax for uscan I could find was: uscan --noconf --force-download --rename --repack --destdir=. Would that be acceptable? The license in debian/copyright is different than in COPYING. This is a serious bug. I've update the file to be more explicit with the license. -- Paul Belanger | PolyBeacon, Inc. Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode) Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger -- 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/50a7deed.6030...@polybeacon.com
Re: Merging python-jenkins from Ubuntu
On 12-11-17 02:01 PM, Paul Belanger wrote: On 12-11-16 11:49 AM, Jakub Wilk wrote: (I don't intend to sponsor this package.) I appreciate the feedback * Paul Belanger , 2012-11-14, 17:20: As a follow up, I have already created the ITP and uploaded the package to mentors.debian.net[2]. Any sort of mentoring / sponsorship would be welcomed. Next up is the RFS. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693268 [2] http://mentors.debian.net/package/python-jenkins A direct link to .dsc would have been more helpful: http://mentors.debian.net/debian/pool/main/p/python-jenkins/python-jenkins_0.2-1.dsc Lintian reports: O: python-jenkins source: unknown-field-in-dsc original-maintainer I: python-jenkins: unknown-field-in-control original-maintainer Why is that tag overridden? Fixed, I was using logic from Ubuntu when syncing a package from Debian. I've reverted the Maintainer field to the original person and added myself to Uploaders. The binary package appears to be architecture-independent, so it should be "Architecture: all" rather than "Architecture: all". Fixed. As far as I can see, "python-dev" build-dependency could be replaced by "python". Even better, make it "python-all" to work around #683557. Fixed. If I were you I would bother to provide get-orig-source target that only calls uscan... But if you really want to have it, please make it policy-compliant (§4.9), and please don't hide commands it runs. Quick question, the most comment syntax for uscan I could find was: uscan --noconf --force-download --rename --repack --destdir=. Would that be acceptable? The license in debian/copyright is different than in COPYING. This is a serious bug. I've update the file to be more explicit with the license. Apologies, I didn't attach the direct link to the .dsc: http://mentors.debian.net/debian/pool/main/p/python-jenkins/python-jenkins_0.2-2.dsc -- Paul Belanger | PolyBeacon, Inc. Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode) Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger -- 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/50a7e170.9040...@polybeacon.com
Re: statsd + voluptuous packaged!
On 13-03-21 08:59 AM, Antoine Musso wrote: Hello, I have been a long time Debian user and finally starts contributing back to the project \O/ For the context, I am a contractor for the Wikimedia Foundation which uses Ubuntu. To install python modules on the production infrastructure, we are required to use Debian packages. My needs were for the voluptuous and statsd python modules. The very first step was to fill the ITPs: statsd http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703613 voluptuous http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698354 The voluptuous one has been build and deployed on one of the Wikimedia server already, the statsd is in the pipeline. I have posted some details on the voluptuous ITP: -8<---8<---8<---8<- We completed the packaging of python-voluptuous version 0.6.1 for Ubuntu Precise. The debian/* files are available in Wikimedia git repository: https://gerrit.wikimedia.org/r/p/operations/debs/python-voluptuous.git The APT repository is apt.wikimedia.org , the generated files can be found at: http://apt.wikimedia.org/wikimedia/pool/main/p/python-voluptuous/ -8<---8<---8<---8<- The package is meant for Ubuntu Precise right now. I would like to have the package reviewed by some expert and ultimately get it uploaded to the Debian.org archive. I will be more than happy to maintain it. My questions are thus: - is there any mentoring program? - are my packages awfully wrong for inclusion in Debian.org, if so how can I enhance them :-] - can a package support both Ubuntu and Debian? - how do I upload it for inclusion in debian/experimental or testing? I am 'hashar' on OFTC and Freenode IRC. I write english and french. Available during European business hours. Thank you! Ohai! Here is a few things I noticed[1]. Ping me on IRC again, and I'll help more if I can. I think you are pretty close to upload to mentors.debian.net [1] https://github.com/pabelanger/python-voluptuous-deb/commit/06f14f76e923f5dbbed1db8ffd6e0f7a39d8abce -- Paul Belanger | PolyBeacon, Inc. Jabber: paul.belan...@polybeacon.com | IRC: pabelanger (Freenode) Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger -- 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/515b735b.9000...@polybeacon.com
