[devscripts] branch master updated (66ff181 -> 3771d62)

This is an automated email from the git hooks/post-receive script. jamessan pushed a change to branch master in repository devscripts. from 66ff181 mk-origtargz: skip upstream signature when repacking new 3771d62 ci: Add backports and nocheck builds to matrix The 1 revisions l

[devscripts] 01/01: ci: Add backports and nocheck builds to matrix

This is an automated email from the git hooks/post-receive script. jamessan pushed a commit to branch master in repository devscripts. commit 3771d62c13f81f5e390fbba76d6e811fb583fed9 Author: James McCoy Date: Thu Sep 7 22:10:12 2017 -0400 ci: Add backports and nocheck builds to matrix

Bug#874718: debchange doesn't allow empty changelog entry

Control: retitle -1 dch "" should not create maintainer header Control: tags -1 + patch On Sun, 2017-09-10 at 07:37 +0900, Osamu Aoki wrote: > control: retitle -1 dch -u "" creates undesired changelog entry > > Hi, > > On Sat, Sep 09, 2017 at 10:22:14AM +0100, Adam D. Barratt wrote: [...] On Sat

Processed: Re: Bug#874718: debchange doesn't allow empty changelog entry

Processing control commands: > retitle -1 dch "" should not create maintainer header Bug #874718 [devscripts] dch -u "" creates undesired changelog entry Changed Bug title to 'dch "" should not create maintainer header' from 'dch -u "" creates undesired changelog entry'. > tags -1 + patch Bug #87

Bug#874716: marked as done (debchange doesn't allow empty changelog entry)

Your message dated Sun, 10 Sep 2017 07:39:06 +0900 with message-id <20170909223906.zlry6yd6oiglr...@tc4.so-net.ne.jp> and subject line Duplicates has caused the Debian Bug report #874716, regarding debchange doesn't allow empty changelog entry to be marked as done. This means that you claim that t

Bug#874717: marked as done (debchange doesn't allow empty changelog entry)

Your message dated Sun, 10 Sep 2017 07:39:06 +0900 with message-id <20170909223906.zlry6yd6oiglr...@tc4.so-net.ne.jp> and subject line Duplicates has caused the Debian Bug report #874717, regarding debchange doesn't allow empty changelog entry to be marked as done. This means that you claim that t

Bug#874718: debchange doesn't allow empty changelog entry

control: retitle -1 dch -u "" creates undesired changelog entry Hi, On Sat, Sep 09, 2017 at 10:22:14AM +0100, Adam D. Barratt wrote: > [You appear to have filed this bug 3 times. Maybe you want to close > #874717 and #874716?] I guess I need to fix my mailer set up. (This mail may be tripled.) I

Processed: Re: Bug#874718: debchange doesn't allow empty changelog entry

Processing control commands: > retitle -1 dch -u "" creates undesired changelog entry Bug #874718 [devscripts] dch -u "" creates undesired changelog entry Ignoring request to change the title of bug#874718 to the same title -- 874718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874718 Debi

Processed: Re: Bug#874718: debchange doesn't allow empty changelog entry

Processing control commands: > retitle -1 dch -u "" creates undesired changelog entry Bug #874718 [devscripts] debchange doesn't allow empty changelog entry Changed Bug title to 'dch -u "" creates undesired changelog entry' from 'debchange doesn't allow empty changelog entry'. -- 874718: https:

Bug#833012: Need better example URL

Hello Osamu, On Sun, Sep 03 2017, Osamu Aoki wrote: > When I checked, the recent release doesn't have "-signed" in the > "Version 0.4.12" while older release has "Version 0.4.7.1-signed". > Strange. Are you sure this site still provides signature file? If you > add ".asc" before "?" as The -si

Bug#874718: debchange doesn't allow empty changelog entry

[You appear to have filed this bug 3 times. Maybe you want to close #874717 and #874716?] On Sat, 2017-09-09 at 15:08 +0900, Osamu Aoki wrote: > If "" is the text to be added to the changelog, debchange skips > making line > with "*".  This seems to intentional design decision of debchange > which