Re: Keeping upstream commits separate from Debian packaging commits (was: Fighting commit storm madness)
On 2014-10-10 15:59, Ben Finney wrote: > Agreed. This is a direct result of rebasing Debian packaging history > onto upstream VCS history, and keeping them all in the same repo as one > undifferentiated history, no? Not sure, but isn't this more a result of the scripts in use, to not differentiate paths? I assume, that the script uses post-receive, so it has access to all commits, including all affected paths. If so, generating only emails or IRC messages when debian/ is involved should be easy. -- 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/20141010062107.GA23092@fama
Re: Keeping upstream commits separate from Debian packaging commits (was: Fighting commit storm madness)
On 9 October 2014 22:59, Ben Finney wrote: > It's a good illustration of why I much prefer the workflow of a separate > VCS for the ‘debian/’ directory, merged with upstream source only at > build time. The results of the merge are in a separate location and are > never checked into VCS, they're used only for the build. At the BoF during DebConf, me and paultag discussed how we use exactly this workflow for Docker stuff in Git, and we love it. We don't ever worry about any kind of upstream commits in the packaging, and only deal with upstream tarballs/source at build time, which keeps things simple. Looking at the history of our repo is a direct look at the history of debian/, which makes sense because it's a repo for the packaging, and anything other than that really is a distraction. During the BoF, we were kind of alone in recommending this workflow, but it's certainly nice (for me anyhow) to see other people advocating it as well! :) TL;DR +1 for ditching upstream artifacts :> ♥, - Tianon -- 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/cahnknk0gbmk6jeeidfqrtqupgpmw-_iyzajhab-yj+njamh...@mail.gmail.com
Re: Fighting commit storm madness (was: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1)
Le Fri, Oct 10, 2014 at 12:03:38AM -0400, Scott Kitterman a écrit : > > Changing the number of commits is solving the wrong problem. The problem > that > needs to be solved is including upstream commits. That's thoroughly > uninteresting for a packaging team. Also, it's not just the mails, it's the > IRC bot too (I believe the IRC bot acts off the repository, not mails). In my experience, when updating the upstream branch, the number of upstream commits is usually higher than 20, and therfore the push of the upstream branch will generate a single message. Cheers, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- 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/20141010054912.gc29...@falafel.plessy.net
Keeping upstream commits separate from Debian packaging commits (was: Fighting commit storm madness)
Scott Kitterman writes: > Changing the number of commits is solving the wrong problem. The > problem that needs to be solved is including upstream commits. That's > thoroughly uninteresting for a packaging team. Agreed. This is a direct result of rebasing Debian packaging history onto upstream VCS history, and keeping them all in the same repo as one undifferentiated history, no? It's a good illustration of why I much prefer the workflow of a separate VCS for the ‘debian/’ directory, merged with upstream source only at build time. The results of the merge are in a separate location and are never checked into VCS, they're used only for the build. See ‘git-buildpackage(1)’ for the ‘--git-overlay’ option, which AFAIK does this. That way, the history of the Debian packaging VCS is entirely about what happened to Debian packaging; upstream VCS history is elsewhere. That seems to address the trouble entirely. -- \ “Liberty, n. One of imagination's most precious possessions.” | `\ —Ambrose Bierce, _The Devil's Dictionary_, 1906 | _o__) | Ben Finney -- 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/8538awtt8v.fsf...@benfinney.id.au
Re: Fighting commit storm madness (was: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1)
On Friday, October 10, 2014 12:56:41 Charles Plessy wrote: > Le Thu, Oct 09, 2014 at 11:41:47PM -0400, Scott Kitterman a écrit : > > On Friday, October 10, 2014 11:08:53 Chow Loong Jin wrote: > > > On Thu, Oct 09, 2014 at 07:57:48PM -0400, Scott Kitterman wrote: > > > > [..] > > > > Presumably "one" is the one who set up the git repos. I, for another > > > > one, > > > > would really appreciate it if someone would take care of this. > > > > > > Don't they all share the hook script? > > > > I've no idea. I just want the madness to stop. > > Hi Scott, > > Why do not you check by yourself ? > > ssh alioth.debian.org "grep -L 'maxCommitEmails = 20' > /git/python-modules/packages/*.git/config" > > All Git repositories contain “maxCommitEmails = 20” in their config file, > which will strongly mitigate the problem. Somebody modified all these > files on Oct 9 around 8 am UTC, and I guess that this was to add this > parameter. Because I'm not the one setting these git repos up and trying to figure out what someone else set up and then arguing with them about fixing it doesn't seem to me like a profitable use of the limited time I have for Debian. I'd prefer whoever is doing the work, just do it right. Changing the number of commits is solving the wrong problem. The problem that needs to be solved is including upstream commits. That's thoroughly uninteresting for a packaging team. Also, it's not just the mails, it's the IRC bot too (I believe the IRC bot acts off the repository, not mails). Scott K -- 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/8889694.mlq4ahQI7f@scott-latitude-e6320
Re: Fighting commit storm madness (was: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1)
Le Thu, Oct 09, 2014 at 11:41:47PM -0400, Scott Kitterman a écrit : > On Friday, October 10, 2014 11:08:53 Chow Loong Jin wrote: > > On Thu, Oct 09, 2014 at 07:57:48PM -0400, Scott Kitterman wrote: > > > [..] > > > Presumably "one" is the one who set up the git repos. I, for another one, > > > would really appreciate it if someone would take care of this. > > > > Don't they all share the hook script? > > I've no idea. I just want the madness to stop. Hi Scott, Why do not you check by yourself ? ssh alioth.debian.org "grep -L 'maxCommitEmails = 20' /git/python-modules/packages/*.git/config" All Git repositories contain “maxCommitEmails = 20” in their config file, which will strongly mitigate the problem. Somebody modified all these files on Oct 9 around 8 am UTC, and I guess that this was to add this parameter. Cheers, -- Charles Plessy Tsurumi, Kanagawa, Japan -- 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/20141010035641.gb29...@falafel.plessy.net
Re: Fighting commit storm madness (was: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1)
On Friday, October 10, 2014 11:08:53 Chow Loong Jin wrote: > On Thu, Oct 09, 2014 at 07:57:48PM -0400, Scott Kitterman wrote: > > [..] > > Presumably "one" is the one who set up the git repos. I, for another one, > > would really appreciate it if someone would take care of this. > > Don't they all share the hook script? I've no idea. I just want the madness to stop. Scott K signature.asc Description: This is a digitally signed message part.
Re: Fighting commit storm madness (was: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1)
On Thu, Oct 09, 2014 at 07:57:48PM -0400, Scott Kitterman wrote: > [..] > Presumably "one" is the one who set up the git repos. I, for another one, > would really appreciate it if someone would take care of this. Don't they all share the hook script? -- Kind regards, Loong Jin signature.asc Description: Digital signature
Re: Fighting commit storm madness (was: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1)
On Friday, October 10, 2014 00:22:42 Dimitri John Ledkov wrote: > On 9 October 2014 20:57, Scott Kitterman wrote: > > On October 9, 2014 10:43:38 AM EDT, Barry Warsaw wrote: > >>On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote: > >>>Upstream commits are off topic. > >> > >>Agreed. There's no reason why we need notifications of upstream > >>commits, > >>though I don't know if it's possible to filter them out. > >> > >>>I'm probably going to give up on hanging out on #debian-python once we > >> > >>get > >> > >>>more packages in git. The commits are way too much and don't add > >> > >>value. > >> > >>Have you seen #debian-openstack-commits? Maybe we should just create a > >>#debian-python-commits channel and send the notifications, and only the > >>notifications, there. That way, it doesn't clutter up the discussion > >>channel, > >>and people can choose to join the -commits or not. > >> > > If there's no way to avoid the upstream stuff, I guess that's what we'll > > have to do. I would prefer not though. I sometimes find the existing > > commits valuable. > > > > Scott K > > Given that notifications operate as git server hooks (I presume), one > should have full facility to filterdiff the commit emails and discard > notifications for commits that do not change anything under "debian/*" > paths. Or don't have debian/ subdir to begin with. Presumably "one" is the one who set up the git repos. I, for another one, would really appreciate it if someone would take care of this. Scott K -- 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/2134513.o5gDnWauo8@scott-latitude-e6320
Re: Fighting commit storm madness (was: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1)
On 9 October 2014 20:57, Scott Kitterman wrote: > On October 9, 2014 10:43:38 AM EDT, Barry Warsaw wrote: >>On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote: >> >>>Upstream commits are off topic. >> >>Agreed. There's no reason why we need notifications of upstream >>commits, >>though I don't know if it's possible to filter them out. >> >>>I'm probably going to give up on hanging out on #debian-python once we >>get >>>more packages in git. The commits are way too much and don't add >>value. >> >>Have you seen #debian-openstack-commits? Maybe we should just create a >>#debian-python-commits channel and send the notifications, and only the >>notifications, there. That way, it doesn't clutter up the discussion >>channel, >>and people can choose to join the -commits or not. > > If there's no way to avoid the upstream stuff, I guess that's what we'll have > to do. I would prefer not though. I sometimes find the existing commits > valuable. > > Scott K > Given that notifications operate as git server hooks (I presume), one should have full facility to filterdiff the commit emails and discard notifications for commits that do not change anything under "debian/*" paths. Or don't have debian/ subdir to begin with. -- Regards, Dimitri. -- 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/canbhlui3kobhyl_ney8xkdunktp35ny-3vfoxtxq5pq88eb...@mail.gmail.com
Re: Fighting commit storm madness (was: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1)
On October 9, 2014 10:43:38 AM EDT, Barry Warsaw wrote: >On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote: > >>Upstream commits are off topic. > >Agreed. There's no reason why we need notifications of upstream >commits, >though I don't know if it's possible to filter them out. > >>I'm probably going to give up on hanging out on #debian-python once we >get >>more packages in git. The commits are way too much and don't add >value. > >Have you seen #debian-openstack-commits? Maybe we should just create a >#debian-python-commits channel and send the notifications, and only the >notifications, there. That way, it doesn't clutter up the discussion >channel, >and people can choose to join the -commits or not. If there's no way to avoid the upstream stuff, I guess that's what we'll have to do. I would prefer not though. I sometimes find the existing commits valuable. Scott K -- 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/5050dab9-d745-4aaa-a72a-95f6025c7...@kitterman.com
Re: Fighting commit storm madness (was: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1)
On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote: >Upstream commits are off topic. Agreed. There's no reason why we need notifications of upstream commits, though I don't know if it's possible to filter them out. >I'm probably going to give up on hanging out on #debian-python once we get >more packages in git. The commits are way too much and don't add value. Have you seen #debian-openstack-commits? Maybe we should just create a #debian-python-commits channel and send the notifications, and only the notifications, there. That way, it doesn't clutter up the discussion channel, and people can choose to join the -commits or not. -Barry -- 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/20141009104338.4caf2...@limelight.wooz.org
Re: Fighting commit storm madness (was: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1)
On October 9, 2014 5:36:02 AM EDT, Raphael Hertzog wrote: >On Thu, 09 Oct 2014, W. Martin Borgert wrote: >> On 2014-10-09 10:02, Raphael Hertzog wrote: >> > I fixed the default configuration in setup-repository to limit to >20 >> > commits per push as a maximum. And I also limited the size of >individual >> > commit emails to 1000 lines. >> >> I wonder, whether some kind of digest function would be possible >> and useful? > >There is already a single mail per push that summarizes all the commits >and the individual commits are sent as replies to that initial mails >(provided that the number of commit doesn't exceed 20, otherwise you >only >get the summary mail). Solving the wrong problem I think. Upstream commits are off topic. I'm probably going to give up on hanging out on #debian-python once we get more packages in git. The commits are way too much and don't add value. Scott K -- 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/765e14a1-2717-4e54-868d-b22dce8f9...@kitterman.com
Package naming question: fastaq or python3-fastaq (Was: Package Fastaq git mess)
Hi Jorge, On Thu, Oct 09, 2014 at 10:27:55AM +0100, Jorge Sebastião Soares wrote: > > > I think I'm going to delete the fastaq.git project on git alioth and > > create > > > a new project. Since the code is python3 only I will call it > > python3-fastaq. > > > > Regarding the name: If it is an *application* please stick to the fastaq > > name. Only python modules should have the python[3]- prefix. > > > > https://github.com/sanger-pathogens/Fastaq > Is a set of scripts that need to be installed for > > https://github.com/sanger-pathogens/iva > > to run. > > In that sense, it sort of is a library. But really as I said above, it's > just a set of scripts. > > Should I keep the old nomenclature? I admit I'm a bit unsure since it has Reverse complement all sequences in a file: fastaq_reverse_complement in.fastq out.fastq which looks like an application as well as Here is a template for counting the sequences in a FASTA or FASTQ file: from fastaq import sequences ... which is definitely a Python module. So I keep debian-python in CC - may be they know about a better way to distinguish. Kind regards Andreas. -- http://fam-tille.de -- 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/20141009095022.go10...@an3as.eu
Re: Fighting commit storm madness (was: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1)
On Thu, 09 Oct 2014, W. Martin Borgert wrote: > On 2014-10-09 10:02, Raphael Hertzog wrote: > > I fixed the default configuration in setup-repository to limit to 20 > > commits per push as a maximum. And I also limited the size of individual > > commit emails to 1000 lines. > > I wonder, whether some kind of digest function would be possible > and useful? There is already a single mail per push that summarizes all the commits and the individual commits are sent as replies to that initial mails (provided that the number of commit doesn't exceed 20, otherwise you only get the summary mail). Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- 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/20141009093602.gg3...@x230-buxy.home.ouaza.com
Re: Fighting commit storm madness
> I wonder, whether some kind of digest function would be possible > and useful? how's getting 1 email with 100 upstream commits different to getting 100 emails with upstream commits? (other than it's easier to read these 100 emails and a bit easier to delete digest one) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- 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/20141009092050.gp4...@sts0.p1otr.com
Fighting commit storm madness (was: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1)
(Please, when using email, choose an appropriate subject. Thanks!) On 2014-10-09 10:02, Raphael Hertzog wrote: > I fixed the default configuration in setup-repository to limit to 20 > commits per push as a maximum. And I also limited the size of individual > commit emails to 1000 lines. I wonder, whether some kind of digest function would be possible and useful? -- 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/20141009084250.GB29160@fama
Re: [Python-modules-commits] [python-mplexporter] 135/135: Merge pull request #30 from rainwoodman/patch-1
On Thu, 09 Oct 2014, Sandro Tosi wrote: > so is there any chance you stop this commit storm madness anytime > soon? another bunch of >300 commit messages arrive this night I fixed the default configuration in setup-repository to limit to 20 commits per push as a maximum. And I also limited the size of individual commit emails to 1000 lines. I updated the configuration of the already existing repositories. hertzog@moszumanska:/git/python-modules/packages$ for i in *.git; do cd $i; git config multimailhook.maxCommitEmails 20; git config multimailhook.emailMaxLines 1000; cd -; done Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- 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/20141009080251.gf3...@x230-buxy.home.ouaza.com
