Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #7686
| From | Jean-Michel Vourgère <nirgal@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Git migration schedule |
| Date | 2015-10-18 22:10 +0200 |
| Message-ID | <ql2rg-7dt-5@gated-at.bofh.it> (permalink) |
| References | <qf9vr-5XN-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi there > Remember that the page describing how things will work within the team once > we've migrated to git is described here: > https://wiki.debian.org/Python/GitPackaging > We'll make that page official once the migration is done. I've using git for some years now, and so does upstream in most of the packages I maintain. Git multiple remotes is a nice feature. We can plug right into upstream tree. I like it for copyrights tracking, for example. You labelled the wiki as "official" and use terms like "must". I dislike that. "master" branch name is already used by upstream (This is *very* often the case). Using "master" ourself makes the things quite confusing in my opinion. debian/master or debian/sid make more sense to me. I use debian/wheezy and similar for security and backports. This is compatible with DEP14 while your guideline is not. As for the tags, I'm using "git pull" then "git push alioth --tags", so that all upstream tags are automatically copied in our git. If upstream tags "1.2" it is put in alioth, not "upstream/1.2". I love that feature. That's forbidden now? Also, for patches, I'm used to source format 3.0 (quilt). Is that bad now? When I changed a file, I used to have a hint to run "dpkg-source --commit". I miss that. I'm not using git-buildpakage, but a simple debuild (tests) or sbuild (for final uploads). sbuild is the tool used by buildd on the official packages. I can't begin to understand why it would be unacceptable. So basically, I'm out of line. Please soften the new rules. Can someone point me to some advantages of using gpb? Right now I can only see useless constraints like branch names that collide with names used by upstream, duplicate clean during build, and quilt files that aren't created automatically on build and so on and so forth. Why I should learn yet another set of tools such as gbp? There must be some advantages, I presume? Maybe I'm too far gone and should just leave the team?
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar
Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-02 16:30 +0200
Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-02 22:50 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-02 23:10 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-03 11:50 +0200
Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-03 12:50 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-03 16:30 +0200
Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-03 17:00 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-03 20:10 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-03 21:00 +0200
Re: Git migration schedule Daniele Tricoli <eriol@mornie.org> - 2015-10-03 21:50 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-03 22:30 +0200
Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-04 21:10 +0200
Re: Git migration schedule Julien Puydt <julien.puydt@laposte.net> - 2015-10-04 21:30 +0200
Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-04 21:40 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-04 23:10 +0200
Re: Git migration schedule IOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org> - 2015-10-05 12:10 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-05 22:40 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 23:30 +0200
Re: Git migration schedule IOhannes m zmölnig (Debian/GNU) <umlaeute@debian.org> - 2015-10-06 09:40 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 18:00 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-04 23:10 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 17:50 +0200
Re: Git migration schedule Scott Kitterman <debian@kitterman.com> - 2015-10-05 18:30 +0200
Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-06 02:40 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-08 17:10 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 18:00 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 22:40 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-05 22:40 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 17:40 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-09 10:30 +0200
Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 01:10 +0200
Re: Git migration schedule Ben Finney <ben+debian@benfinney.id.au> - 2015-10-10 03:20 +0200
Re: Git migration schedule Mattia Rizzolo <mattia@mapreri.org> - 2015-10-10 03:50 +0200
Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 04:40 +0200
Re: Git migration schedule Barry Warsaw <barry@python.org> - 2015-10-10 21:10 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-11 10:30 +0200
Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-18 03:00 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-05 17:50 +0200
Re: Git migration schedule Daniel Stender <debian@danielstender.com> - 2015-10-05 21:00 +0200
Re: Git migration schedule Barry Warsaw <barry@python.org> - 2015-10-06 01:20 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-06 01:30 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-08 17:10 +0200
Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-09 02:00 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-09 10:00 +0200
Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 00:40 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-10 01:00 +0200
Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-11 02:30 +0200
Re: Git migration schedule Raphael Hertzog <hertzog@debian.org> - 2015-10-12 09:10 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-12 21:40 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-09 10:10 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-09 16:50 +0200
Re: Git migration schedule Arthur de Jong <adejong@debian.org> - 2015-10-09 18:50 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-09 19:40 +0200
Re: Git migration schedule Arthur de Jong <adejong@debian.org> - 2015-10-09 21:30 +0200
Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 00:30 +0200
Re: Git migration schedule Stefano Rivera <stefanor@debian.org> - 2015-10-11 10:30 +0200
Re: Git migration schedule pushback permissions/DEP-3 workflow Daniel Stender <debian@danielstender.com> - 2015-10-12 20:20 +0200
Re: Git migration schedule pushback permissions/DEP-3 workflow Daniele Tricoli <eriol@mornie.org> - 2015-10-12 20:30 +0200
Re: Git migration schedule Brian May <brian@microcomaustralia.com.au> - 2015-10-10 00:20 +0200
Re: Git migration schedule IOhannes m zmölnig <zmoelnig@umlaeute.mur.at> - 2015-10-10 21:40 +0200
Re: Git migration schedule Jean-Michel Vourgère <nirgal@debian.org> - 2015-10-18 22:10 +0200
Re: Git migration schedule Piotr Ożarowski <piotr@debian.org> - 2015-10-18 23:10 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-19 19:20 +0200
Re: Git migration schedule Brian May <bam@debian.org> - 2015-10-19 23:40 +0200
Re: Git migration schedule Raphael Hertzog <hertzog@debian.org> - 2015-10-21 10:00 +0200
Re: Git migration schedule Brian May <bam@debian.org> - 2015-10-19 23:40 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-20 16:10 +0200
Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-21 09:40 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-21 16:50 +0200
Re: Git migration schedule Sandro Tosi <morph@debian.org> - 2015-10-21 23:40 +0200
Re: Git migration schedule Brian May <bam@debian.org> - 2015-10-22 00:10 +0200
Re: Git migration schedule Sandro Tosi <sandro.tosi@gmail.com> - 2015-10-22 00:30 +0200
Re: Git migration schedule Raphael Hertzog <hertzog@debian.org> - 2015-10-22 09:20 +0200
Re: Git migration schedule Barry Warsaw <barry@debian.org> - 2015-10-23 01:50 +0200
Re: Git migration schedule Julien Puydt <julien.puydt@laposte.net> - 2015-10-22 10:00 +0200
Re: Git migration schedule Piotr Ożarowski <piotr@debian.org> - 2015-10-22 10:10 +0200
pristine-tar (was: Git migration schedule) "W. Martin Borgert" <debacle@debian.org> - 2015-10-22 13:10 +0200
Re: pristine-tar (was: Git migration schedule) Barry Warsaw <barry@debian.org> - 2015-10-23 01:50 +0200
Re: Git migration schedule Brian May <bam@debian.org> - 2015-10-22 10:30 +0200
csiph-web