Re: Move to salsa? Merge modules and apps team?
On 07/02/2018 08:37, W. Martin Borgert wrote: > Hi, > > how about moving the Python team(s) to salsa? Hello, Does Salsa support merge requests? If so has any work been done to add support to run tests automatically? I am being curious since I would contribute more if I had a test feedback and human reviews :] -- Antoine Musso
git packaging (was: Python packaging help.)
Breaking from another thread On 31/03/15 15:57, Barry Warsaw wrote: The team still officially supports only Subversion, but we have been experimenting with switching to git. https://wiki.debian.org/Python/GitPackaging I personally favor and advocate git-dpm, but this has not yet been decided by the team. I'd like for the team to make the switch very soon after Jessie is released, and I would personally be comfortable switching now. We'll need to decide a few things before we can do that: * Do we adopt git-dpm or something else? Hello, I have only been introduced to git-buildpackage and using Jenkins to more or less automatically build them when proposing a patch or a change is merged. Michael mika Prokop [MIKA] maintains a very nice set of shell scripts that makes it a breeze to integrate in Jenkins a git-buildpackage aware repository and it uses cowbuilder to speed up the process. http://jenkins-debian-glue.org/ [MIKA] https://qa.debian.org/developer.php?login=mika%40debian.org Random example of pull requests being build by Jenkins and providing lintian/piuparts/.deb: https://integration.wikimedia.org/ci/view/Ops-DebGlue/job/labs-toollabs-debian-glue/ * Do we migrate all packages at once or one-at-a-time as needed? From past experience in migrating a huge svn tree, it is usually easier to move them in batches as developers request it. If you get to find some volunteers, they will by the first line dealing with potential issues and updating the doc. Will make it easier for others. * Do we try to keep all svn history, or just upload history? I tend to like the history, the blame and commit message logs are sometime useful to get the context of a change/line of code. I have recently migrated python-gear module which only had two tags. Did that with git-svn which created something more or less appropriate. You have to provide a map of: svn login - First Last em...@example.org Can probably be generated. The tags ended up being orphan branches but I did not care that much. End result: http://anonscm.debian.org/cgit/python-modules/packages/python-gear.git/log/ There is a bunch of tools to migrate from svn to git, can't find any reference right now but there are. In lot of cases, you will have to tweak the tool / write code to adjust it to your svn history. At worse, one can import the trunk with git-svn then manually tag. See also: http://anonscm.debian.org/cgit/users/barry/import-dscs.git/tree/import-dscs.py I'm sure there's more I'm missing. I would definitely like to keep this on the radar. -- 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/551ab3b1.9050...@free.fr
Re: Proposed git migration plan
Le 26/08/2014 20:36, Hans-Christoph Steiner a écrit : * the git-buildpackage workflow is really quite wonderful and reasonably flexible, I highly recommend it, and I think it will improve the productivity of this team. Hello, At Wikimedia we solely use git-buildpackage. DD Michael Prokop wrote a set of script that let you easily build the package using Jenkins which can be made to poll the git repo, and hence build your package when a commit is pushed: http://jenkins-debian-glue.org/ Coupled with a pre review software such as Gerrit, that let one propose a patchset, have the build result displayed and iterate until the patch is ready to land in the branch. That is a huge time saver for us. -- Antoine hashar Musso -- 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/53fd9713.8050...@free.fr
Re: Proposed git migration plan
Le 27/08/2014 10:13, Sandro Tosi a écrit : snip Offline commits? how many time (for real..) you badly needed it? i guess so few that if you (for one time) just do a big commit instead of a storm of micro commit the world wont stop As a side effect, that also mean you don't have to use a potentially lagged network connection when doing simple operations. There is nothing I hate more than waiting for network when using the commands log, commit or blame. is there anything else so attractive about git? Cheap local branches which let you pill up work in progress patches / rewrite without having to keep several copy of the same svn repo. The branches in git are just a name pointing to a commit in the tree. The stash, which let you save your uncommited changes and come back to them later (think of it as lightweight branches). That is really nice when you have to interrupt your workflow, stash it, handle the interrupt, reapply your stash and resume work. Tags can be signed with gpg. They are a pointer to a commit just like branches, and hence don't force you to do a full copy to create a tag. Switching between branches is a breeze and does not need network access either. If we don't define *upfront* what are the problems we currently have and that we want to solve, then we're just proposing a technical exercise without a real gain. and I cant stress this point never enough. I agree there, would be nice to list the problems with svn. But I guess most of them are related to svn being a bad (and slow) CSV system. -- Antoine hashar Musso -- 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/53fd99c2.5040...@free.fr
Re: Proposed git migration plan
Le 25/08/2014 23:00, Barry Warsaw a écrit : Here's the page I mentioned regarding a *proposed* transition plan to using git for team packages. It's more or less a brain dump right now, and don't feel like you need to read it before the DC14 session. https://wiki.debian.org/Python/GitPackaging Food for thought and discussion. From another reply: have you guys considered using a pre commit workflow review system ? In such a system developers propose their change in a gate and they are reviewed/approved before landing in the branch. That let anyone propose a change without potentially breaking the master branch used to build package from. The well known example are GitHub pull requests. OpenStack and Wikimedia foundations are using Gerrit. It is an open source java application developed by Google to develop the Android SDK. It is interface is not the best, but it handles that pre commit review workflow very well. -- Antoine hashar Musso -- 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/53fd9a95.7090...@free.fr
Re: Using ‘export http_proxy = http://127.0.9.1:9/’ to fail noisily on dependency problems
Le 11/10/13 12:21, Piotr Ożarowski a écrit : override_dh_auto_test: http_proxy='' dh_auto_test You ight want to set https_proxy='' as well. -- Antoine hashar Musso -- 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/5257dccd.9060...@free.fr
Re: Disabling pip for root?
Le 20/09/13 10:29, Thomas Goirand a écrit : It's really not hard to package some Python modules for Python. Having a tool that does it automatically - even not very well -, like debpear does, can solve this kind of trouble. Giving access to this kind of tools to a wide user base can also help solving the oh, but that module isn't available in Debian kind of problem. I did my first packages using Effing Package Management (fpm): https://github.com/jordansissel/fpm You give it a source (pypi), a target (deb) and the name of the resource. Then magic happen and you end up with a .deb. The generated .deb is installable and works fine for the simplest packages. The resulting .deb is not on par with Debian quality though and you need a bunch of additional work to make it acceptable. Maybe have a look at fpm and find out how we can get it improved for the py - deb case? -- Antoine hashar Musso -- 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/523e2d11.7050...@free.fr
Re: PEP 453 affects Debian packaging of Python packages
Le 21/09/13 01:17, Thomas Kluyver a écrit : And how many inexperienced packagers will start by filing an ITP bug? Or indeed by searching for existing ITP bugs? More likely, the bug only gets filed when they've prepared a working package and Lintian is complaining about the lack of a line closing the ITP bug. I keep forgetting filling an ITP. It is usually caught on final review because for some reason lintian is not being run by default by my packaging chain :-( I find the ITP/wnpp annoying as well. I usually end up browsing http://www.debian.org/devel/wnpp/ , opening all links then searching for my package :-] I then bootup an instance and try to remember to report the bug against the 'wnpp' package. But I am a newcomer, so I am easily confusing / forgetting rules :) -- Antoine hashar Musso -- 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/523d2883.9070...@free.fr
Re: Is subgit for migrating from Git to SVN?
Le 11/05/13 05:06, Thomas Goirand a écrit : Hi, I came accross http://subgit.com/ Could it be of any help for us? Hello Thomas, Wikimedia migrated its svn repositories to git during spring 2012 which included MediaWiki a 10+years repository. We used a C++ svn2git : https://github.com/ryppl/svn2git and forked it to get some hacks in. Our fork and the migration rules are available in the git repo: git clone https://gerrit.wikimedia.org/r/operations/software Then: /svn2git/src : our fork /svn2git/scripts/rules : our migration rules phase3.rules is the file for MediaWiki One possible long task is determining a real user name and email address for each of the svn account. That is most probably available in Alioth but then you want to make sure people agree to have their email disclosed. cheers, -- Antoine hashar Musso -- 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/518f66f6.7090...@free.fr
Bug#698354: ITP: voluptuous package uploaded to svn
I have uploaded the debian files to Python module team svn with r23955. Mail notification: http://lists.alioth.debian.org/pipermail/python-modules-commits/2013-April/023286.html Viewvc: http://anonscm.debian.org/viewvc/python-modules?view=revisionrevision=23955 -- Antoine hashar Musso -- 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/516fc707.1040...@free.fr
Bug#703613: ITP: statsd package uploaded to svn
I have uploaded the debian files to Python module team svn with r23959. Mail notification: http://lists.alioth.debian.org/pipermail/python-modules-commits/2013-April/023290.html Viewvc: http://anonscm.debian.org/viewvc/python-modules?view=revisionrevision=23959 -- Antoine hashar Musso -- 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/516fd5f3.5020...@free.fr
Request to join PMPT
Hello, I am a contractor for the Wikimedia Foundation in charge of continuous integration. We reuse softwares from the OpenStack foundation and could use some python modules to be packaged. Being brave, I filled the ITP and even did the preliminary packaging work for: * python-statsd http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703613 * python-voluptuous http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698354 I am idling in #debian-python and got accounts on Alioth and mentors.debian.net :-} -- Antoine hashar Musso -- 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/515f13e9.6030...@free.fr
Re: statsd + voluptuous packaged!
Le 03/04/13 02:10, Paul Belanger a écrit : ere 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 Oh I should have pinged this list about a new change I have submitted last week which kind of duplicate your work: https://gerrit.wikimedia.org/r/#/c/56168/ I guess I will rebase your patch on top of mine. I need to talk about 0.7.1 with you, seems Zuul does not support that version :-] -- Antoine hashar Musso -- 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/kjgmke$c0t$1...@ger.gmane.org
Re: statsd + voluptuous packaged!
Le 03/04/13 09:44, Antoine Musso a écrit : Le 03/04/13 02:10, Paul Belanger a écrit : ere 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 Oh I should have pinged this list about a new change I have submitted last week which kind of duplicate your work: https://gerrit.wikimedia.org/r/#/c/56168/ I guess I will rebase your patch on top of mine. Rebased in Wikimedia code review tool: https://gerrit.wikimedia.org/r/#/c/57263/ Though I have left it to 0.6.1 for now. -- Antoine hashar Musso -- 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/kjgnup$no2$1...@ger.gmane.org
statsd + voluptuous packaged!
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! -- Antoine hashar Musso -- 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/514b0414.7090...@free.fr
Re: statsd + voluptuous packaged!
Le 21/03/13 13:59, Antoine Musso a écrit : 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 gitweb link is: https://gerrit.wikimedia.org/r/gitweb?p=operations/debs/python-voluptuous.git;a=summary -- Antoine hashar Musso -- 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/kif4nt$mco$1...@ger.gmane.org
Re: statsd + voluptuous packaged!
Le 21/03/13 19:21, Thomas Goirand a écrit : I happen to also have worked on statsd: http://anonscm.debian.org/gitweb/?p=openstack/statsdpy.git Bonjour =) It seems they are different packages: - statsdpy is a statsd server - python-statsd a client for the nodejs statsd I might be wrong, but the author are different and the code in each repository looks entirely different to me. My ITP was filled before yours: #699411 Next time, please check wnpp better please. I guess that is what happens when newbie joins. They do mistake, so do I. I must confess I have only looked at packages.debian.org :/ Will remember about wnpp, thanks for the tip! I would be happy to co-maintain the package with you. What do you think? My nick is zigo on OFTC and Freenode. Please ping me. I'm French as well (though I live in China currently). Will try to remember to ping you :-] I am now always connected in irc://irc.oftc.net/#debian-python Merci! -- Antoine hashar Musso -- 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/kig11t$gh6$1...@ger.gmane.org
