Bug#935890: Rename "dgit push-source" to "dgit push"

s, Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#868527: [buildd-tools-devel] Bug#868527: Bug#868527: want sbuild --no-source or something

about already. So maybe it should live in src:sbuild... HTH. Regards, Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#939280: dgit push-source rejects source-only .changes containing .orig.tar.gz.asc

Simon McVittie writes ("Re: Bug#939280: dgit push-source rejects source-only .changes containing .orig.tar.gz.asc"): > On Wed, 04 Sep 2019 at 00:02:06 +0100, Ian Jackson wrote: > > I think the -C option should not be necessary. Indeed I'm > > not even sure what it does (

Bug#939280: dgit push-source rejects source-only .changes containing .orig.tar.gz.asc

> > > > dgit: error: user-specified changes file is not source-only For my reference: it's not clear to me whether dgit used the specified -C at all. It may have built a correct .changes file an then complained about its own output. > Workaround: > > * Use dgit push in

Bug#935890: Rename "dgit push-source" to "dgit push"

Sean Whitton writes ("Re: Bug#935890: Rename "dgit push-source" to "dgit push""): > On Tue 27 Aug 2019 at 11:30AM +01, Ian Jackson wrote: > > Package: dgit > > Version: 9.7 > > User: d...@packages.debian.org > > Usertags: rsn >

Bug#935898: adns package is undermaintained and needs comaintainers

overwrite will be needed to stitch in the .dsc import). And I guess we should either rewind/overwrite the salsa master branch from Gianfranco, or stitch in with "git merge -s ours" ? Magnus, are you able to do that ? Do you want me to help out ? Thanks, Ian. -- Ian JacksonThese opi

Bug#935898: adns package is undermaintained and needs comaintainers

'm not sure I agree with the decision to change the source package format but since I have been doing little work on this package, I don't feel I ought to try to veto it. I would like to hear what Magnus thinks. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.n

Bug#935890: Rename "dgit push-source" to "dgit push"

Package: dgit Version: 9.7 User: d...@packages.debian.org Usertags: rsn dgit push-source should be primary. We should start by renaming "dgit push" to "dgit push-built" (at first, with an alias). Ian. -- Ian JacksonThese opinions are my own. If I emailed you from a

Bug#935874: dgit: "Push failed, while checking state of the archive" if previous upload was too recent

Control: retitle -1 fetch can fail due to mirror lag Colin Watson writes ("Bug#935874: dgit: "Push failed, while checking state of the archive" if previous upload was too recent"): > Package: dgit > Version: 9.7 > Severity: normal > > I tried to make two uploads of man-db this morning, the

Bug#935443: Want more docs reassurance about --new (esp. dgit-maint-bpo)

s case) multiple signed .changes files for the same version. I think dgit ought to suggest this to you, when it looks like you are in this situation. > i ended up, uploading with `dput`, which worked ok for now (next time i > upload the package to bpo, i will use `dgit` again) Thanks, Ian. --

Bug#935443: Want more docs reassurance about --new (esp. dgit-maint-bpo)

IOhannes m zmölnig (Debian/GNU) writes ("Bug#935443: Want more docs reassurance about --new (esp. dgit-maint-bpo)"): > On 8/22/19 6:50 PM, Ian Jackson wrote: > > Out of interest, did you read the description of --new in dgit(1) ? > > I ask because I want to know if impro

Bug#935762: dgit: behaviour of --quilt=auto is surprising when a quilt series exists

y selects the right quilt mode which it very much doesn't (and which isn't possible, sadly). Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#935443: Want more docs reassurance about --new (esp. dgit-maint-bpo)

Package: dgit Version: 9.7 Hi. IOhannes, I think you won't mind me copying this private mail of yours to the bug system. IOhannes m zmölnig (Debian/GNU) writes ("Re: dgit with backports"): > On 8/22/19 1:58 PM, IOhannes m zmölnig (Debian/GNU) wrote: > > it refuses with > >> package appears to

Bug#934948: Unnecessary dependencies vs multiple binary packages

tical dependencies of less-critical subcomponents. devscripts is perhaps the best example. > * When a user installs a library for one interpreter or environment, > in general, we don't want the package dependencies to require that > user to install an unrelated interpreter. I think this de

Bug#935084: git-debpush manpage suggestions [and 1 more messages]

Control: user d...@packages.debian.org Control: tags -1 + rsn Sean, thanks for the review. These bugs are now readily actionable. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce

Bug#935085: git-debpush UI observations

edge that git-debpush embodies and it should be useable by itself. I think we can still change anything we like in this area. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#935084: git-debpush manpage suggestions

es service and should be reported there ? Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#934945: startpar: insserv attemps to write to /etc/.boot.* even with -p option

ing the test script. For Debian, this test failure is regarded as an RC bug. So we need to fix it there ASAP, by forward porting the commit. (A simple git cherry pick I assume. Plus the test dependency change if we need it, of course, but we need to keep that. Ian. -- Ian JacksonThese

Bug#934945: startpar: insserv attemps to write to /etc/.boot.* even with -p option

etc/init.d -i etc/init.d test It sounds like we should make this change to the test suite, and also add a test dependency saying we need at least whatever insserv gained the -i option ? Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#934807: want warning for misplaced positional dgit options

Package: dgit Version: 9.7 User: d...@packages.debian.org Usertags: rsn Félix Sipma writes ("Re: dgit for DM [and 1 more messages]"): > On 2019-08-14 08:00+0100, Ian Jackson wrote: > > Félix Sipma writes ("Re: dgit for DM [and 1 more messages]"): > >&g

Bug#910673: Request for a new mailing list: debian-xen

Alexander Wirt : > That list is still missing any other advocated speaking for the lists, > I would really prefer if at least Ian Jackson would speak up. Hi. I think this list would be a good idea. Indeed, it was during an IRL conversation with me that I suggested to Knorrie that he r

Bug#932696: Please document Haskell team style Vcs-Git sytax

ain [ ] but permits (and eats) spaces inside the [ ]. I'm inclined to think that these questions show that my original proposal was not brilliant and that your idea is better. HTH. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that i

Bug#933827: "dgit fetch" fails with "cannot remove directory for ..."

this in a commit message by adding your Signed-off-by line (git commit -s), or with your approval I can put it in for you. [1] https://browse.dgit.debian.org/dgit.git/tree/DEVELOPER-CERTIFICATE If you have questions about the s-o-b process I'll be happy to answer them; maybe private email would be be

Bug#934126: malfunctions due to being confused about git repository

r/bin/dgit line 4886 main::cmd_fetch() called at /usr/bin/dgit line 7798 Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932584: Epydoc and Pydoctor

u would be. Thank you for this. However, you did an upload with binaries and it therefore isn't migrating. I will do a source-only upload right away. Regards, Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address wh

Bug#934062: Upstream metadata to help our users contribute back to projects we redistribute.

han for just perl packages. Yes. I think "dgit clone" should set up a remote for this automatically. (The information is useful for a lot more than contributing back: having the upstream git history, where it can be found, is often useful for bugfixing, etc.) What does pkg-perl-tools

Bug#933827: "dgit fetch" fails with "cannot remove directory for ..."

Hi. I'm sorry you're having trouble and I want to make it work for you (in your existing configuration). Stéphane Glondu writes ("Bug#933827: "dgit fetch" fails with "cannot remove directory for ...""): > It might be relevant to know that /home/steph is on NFS. Urgh. > Indeed,

Bug#932584: Epydoc and Pydoctor

gt; any replies for more than 18 months now, I won't wait that long before > doing this NMU. That sounds really good to me for now. I think you can do this NMU whenever you like. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org

Bug#726953: dgit and submodules

lly they are the worst answer. Even (especially) to the situation they were specifically intended to address. They are simply too broken. Of course this is of no help to you as a downstream if your upstream has drunk the poison kool-aid. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932795: Ethics of FTBFS bug reporting

Simon McVittie writes ("Bug#932795: Ethics of FTBFS bug reporting"): > For the specific question of whether a single CPU core is a "reasonable" > build environment, my answer at the moment is "I don't know". There are two issues here: 1. "Is a 1-cpu system `reasonable' or `supported'" (or

Bug#932584: Please help fix pydoctor

a package of mine has a dependency chain via gbp.) Thanks, Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932753: tag2upload should record git tag signer info in .dsc [and 1 more messages]

aps, is to leave this out now, and intend to introduce a `fingnerprintv5' value later. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932570: dgit should pin to the LE CA for ftpmasterapi

from intrigeri, I think. I'm finding 1 a bit of a struggle. My current WIP branch (rebasing) is here: https://salsa.debian.org/dgit-team/dgit/commits/wip.tls Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private

Bug#933017: Please add source link and bug reporting info to footer

and it wasn't there. I see now that this page https://www.debian.org/Bugs/pseudo-packages does have it. This is mysterious to me. I hope someone in the web team can do something sensible about this... Thanks, Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address

Bug#932946: libhttp-server-simple-perl: Please document "minimal implementation" listening socket FH

suggests no packages. -- no debconf information >From 0e3370aae5609c1220d5320d7242443192d0b2da Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Thu, 25 Jul 2019 02:02:22 +0100 Subject: [PATCH] Document the minimal server listening socket filehandle name Knowing this is useful in post_setup_h

Bug#932871: rpush improvemnts for tag2upload

. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932753: tag2upload should record git tag signer info in .dsc [and 1 more messages]

' for pubkey-algo and `8' for hash-algo then ? Ian. [1] Part of the output of gpgv --status-fd=2 --keyring=/usr/share/keyrings/debian-keyring.gpg < ../bpd/dgit_9.4.dsc -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a pri

Bug#932841: libdpkg-perl: Dpkg::Source::Package installs a permanent SIGINT handler

Package: libdpkg-perl Version: 1.18.25 Severity: normal $ perl -we 'use Data::Dumper; print Dumper($SIG{INT})' $VAR1 = undef; $ perl -we 'use Data::Dumper; use Dpkg::Source::Package; print Dumper($SIG{INT})' $VAR1 = sub { "DUMMY" }; $ This is a problem because when a SIGINT handler is

Bug#932570: dgit should pin to the LE CA for ftpmasterapi

Ian Jackson writes ("Re: Bug#932570: dgit should pin to the LE CA for ftpmasterapi"): > If I had done this I might well do: > 1. split up api_query into api_query_raw that doesn't do > decode json, which is called by a small new api_query > 2. make cmd_archive_api_q

Bug#932802: tag2upload .dsc should be reproducible

this is a blocker for deployment. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932795: Ethics of FTBFS bug reporting

is reasonable but not supported. etc. On the point at issue, do these packages build in a cheap single-vcpu vm from some kind of cloud vm service ? ISTM that this is a much better argument than the one you made, if the premise is true. Ian. -- Ian JacksonThese opinions are my own.

Bug#932753: tag2upload should record git tag signer info in .dsc [and 1 more messages]

Ian Jackson writes ("Re: Bug#932753: tag2upload should record git tag signer info in .dsc [and 1 more messages]"): > Russ Allbery writes ("Bug#932753: tag2upload should record git tag signer > info in .dsc [and 1 more messages]"): > > Git-Tag-Info: fingerp

Bug#932753: tag2upload should record git tag signer info in .dsc [and 1 more messages]

g RFC-2822-style fields we > have), which I think increases the chances that parsers will get this > right. Right. I already need and have code to turn a git-style committer/author/tagger line into deb822 form. Ian. -- Ian JacksonThese opinions are my own. If I emaile

Bug#932753: tag2upload should record git tag signer info in .dsc [and 1 more messages]

Hi. I am consulting on the name and syntax of a new field I intend to put in .dsc's. This is for our tag-to-upload service[1], as described here: https://spwhitton.name/blog/entry/tag2upload/ The tag2upload service will take a signed git tag, and verify it against the Debian keyrings and

Bug#932753: tag2upload should record git tag signer info in .dsc

Package: dgit-infrastructure Version: 9.4 Raphael Hertzog writes ("Re: git & Debian packaging sprint report"): > On Sun, 21 Jul 2019, Ian Jackson wrote: > > IME as a sponsor I get (AFAICT) no mails as a result of my sponsorship > > signatures so I think ther

Bug#932696: Please document Haskell team style Vcs-Git sytax [and 1 more messages]

can also be added. So the overall syntax is roughly [ " -b " ] [ " " ] [ " [" ( | "=" "; " )* "]" ] We can say that it's if it has "=" before any "/". Then paths containing = are expressable as ./f

Bug#932612: git-debpush: detect unstitched gdr branch

Sean Whitton writes ("Bug#932612: git-debpush: detect unstitched gdr branch"): > On Mon 22 Jul 2019 at 02:40PM +01, Ian Jackson wrote: > > We could add a failing git-debpush invocation to some random gdr-test. > > (adding the dependency and regenerating d/t/control) >

Bug#932696: Please document Haskell team style Vcs-Git sytax [and 1 more messages]

Russ Allbery writes ("Re: Bug#932696: Please document Haskell team style Vcs-Git sytax [and 1 more messages]"): > Sure, an extensible syntax sounds great. The problem is that we kind of > had one (Vcs-Git was a subset of a git checkout command line, which > allowed support of the -b option), but

Bug#932570: dgit should pin to the LE CA for ftpmasterapi

intrigeri writes ("Bug#932570: dgit should pin to the LE CA for ftpmasterapi"): > Here's a first proof-of-concept on the 932570-pin-LetsEncrypt-CA > branch on https://salsa.debian.org/intrigeri/dgit. Hi. Thanks a lot. I have looked at your mail and code in detail now. First there is some

Bug#932612: git-debpush: detect unstitched gdr branch

> On Sun 21 Jul 2019 at 03:02PM +01, Ian Jackson wrote: > > Look for the ffq-prev ref. Any gdr unstitched branch will have such a > > corresponding ref. See STITCHING, PSEUDO-MERGES, FFQ RECORD in > > git-debrebase(5). > > Thanks. Patch enclosed. Nice work. L

Bug#932477: git-debpush checking that patches (un)apply

> > This seems like a very long way of writing a very short sed rune ? > > Now that there's only one while loop, I don't believe this comment > applies. I agree. > In the revised series, I find the explicit -z check (l. 146) more > readable than avoiding that check by means of sed. So I'd like

Bug#932570: dgit should pin to the LE CA for ftpmasterapi

intrigeri writes ("Bug#932570: dgit should pin to the LE CA for ftpmasterapi"): > Hi, Hi to you! > What do you think? Yay! Wow! Also it is 0230 and I need to sleep :-). Will produce more err focused response tomorrow. Ian. -- Ian JacksonThese opinions are my own.

Bug#932705: git tag -s should print error from gpg

Package: git Version: 1:2.11.0-3+deb9u4 Severity: normal In some git tree, observed behaviour: $ git tag -u no-such-key -s -m spong foo error: gpg failed to sign the data error: unable to sign the tag $ echo $? 128 Expected behaviour: $ git tag -u no-such-key -s -m spong foo gpg: skipped

Bug#932696: Please document Haskell team style Vcs-Git sytax [and 1 more messages]

ld probably have coped here. (#932697 in devscripts and #932699 in dgit.) Ia. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932699: Please cope with Haskell-style Vcs-Git header

not appear to be documented in policy. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932697: Please cope with Haskell-style Vcs-Git header

in policy. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932696: Please document Haskell team style Vcs-Git sytax

Package: debian-policy Version: 4.4.0.1 Many packages' .dscs contain something like this: Source: bustle Version: 0.7.4-1 Vcs-Git: https://salsa.debian.org/haskell-team/DHG_packages.git [p/bustle] The semantics do not appearr to be documented in policy. Ian. -- Ian Jackson

Bug#930930: dgit: suggestion to use -wga/-wgfa could also suggest using -wn --include-dirty

ou can use --clean=git[-ff],always (-wga/-wgfa) to delete them. > dgit: To include them in the build, it is usually best to just commit > them. LGTM, thanks. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a priva

Bug#932477: git-debpush checking that patches (un)apply

Sean Whitton writes ("Bug#932477: git-debpush checking that patches (un)apply"): > I've implemented this in branch 'series/git-debpush-apply-patches-v1' of > repo . Hi. I've reviewed your substantive code. Looking reasonably good but I do have some nontrivial

Bug#932477: git-debpush checking that patches (un)apply

Ian Jackson writes ("Re: Bug#932477: git-debpush checking that patches (un)apply"): > The result is in salsa/wip.dpp. That's a rebase of your branch. ... > FYI I intend to push to master everything up to and including > salsa/wip. So don't rebase below there. I have had

Bug#932477: git-debpush checking that patches (un)apply

now... Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932477: git-debpush checking that patches (un)apply

Re git-debpush: check_treesame: Also pass --quiet to 'git diff' When dgit fails for similar reasons we have it print a diffstat and also print a git diff rune so that the user can see what has changed. See near l.4598 in dgit. We probably don't want something that sophisticated but maybe

Bug#932477: git-debpush checking that patches (un)apply

to > git-playtree-create into the script -- it seems that using-intree has > not been taught to make git-playtree-create available to git-debpush in > the right way. Oops. I will fix this. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net o

Bug#930930: dgit: suggestion to use -wga/-wgfa could also suggest using -wn --include-dirty

Sean Whitton writes ("Re: Bug#930930: dgit: suggestion to use -wga/-wgfa could also suggest using -wn --include-dirty"): > On Mon 01 Jul 2019 at 01:28pm +01, Ian Jackson wrote: > > Is the idea of committing them not obvious enough ? > > I'd like to add the suggestion -

Bug#932612: git-debpush: detect unstitched gdr branch

aintainer's branch even in split view). Right. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#926656: git-debrebase docs are intimidating

(Dropping Colin again) Sean Whitton writes ("Bug#926656: git-debrebase docs are intimidating"): > On Sat 20 Jul 2019 at 11:50PM +01, Ian Jackson wrote: > > How about this ? > > I build the manpage with this version, and I find it readable. Nice > work. At last! Gre

Bug#926656: git-debrebase docs are intimidating

nce users might want to use git-debpush to upload. Thanks to Sam Hartman for the user feedback which prompted this and Ian Jackson for feedback on the content of "QUICK REFERENCE". Closes: #926656 Signed-off-by: Sean Whitton Signed-off-by: Ian Jackson --- git-debrebase.1.pod | 28 ++

Bug#932476: git-debpush gbp/unapplied upstream tree check

Sean Whitton writes ("Bug#932476: git-debpush gbp/unapplied upstream tree check"): > New patch attached addressing all of this -- thanks for the review! Great, thanks. Acked-by: Ian Jackson And in my master. (IDK if you noticed that the previous version broke the tagupl-gbp test

Bug#932590: Please provide Let's Encrypt CA (in known location)

. What do you think ? Thanks, Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#790093: dgit is subvertable by X.509 CA cabal

Control: clone -1 -2 Control: retitle -2 dgit should pin to the LE CA for ftpmasterapi Control: retitle -1 dgit should not trust any third party when talking to Debian servers intrigeri writes ("Re: Bug#790093: dgit is subvertable by X.509 CA cabal"): > (after I've started to play with dgit

Bug#857490: [PATCH] dgit-maint-pbo(7): Add to .gitignore

Ian Jackson writes ("[PATCH] dgit-maint-pbo(7): Add to .gitignore"): > Signed-off-by: Ian Jackson > --- > .gitignore | 1 + > 1 file changed, 1 insertion(+) Also, I had to run rm po4a/po4a.cfg make -C po4a po4a.cfg to avoid the i18n-po4a-uptodate test failing.

Bug#926656: git-debrebase docs are intimidating

ebase docs are intimidating"): > I'm inclined to agree with this assessment, but it would be useful to > hear from Sam's imaginary new user perspective. Yes. > On Sat 20 Jul 2019 at 05:34PM +01, Ian Jackson wrote: > > How about: > > > > QUICK REFERENCE > >

Bug#932476: git-debpush gbp/unapplied upstream tree check

thing like git: diff: arrgh, my innards have exploded! git-debpush: the upstream source in tag blah is not identical ... So set +e, rc=$?; set -e. * I think in gbp and unapplied quilt modes, $upstream_tag will always be set by now (if not, then this code is too early), so don't

Bug#932555: dgit and gdr automatic quilt mode ?

Sean Whitton writes ("Re: Bug#932555: dgit and gdr automatic quilt mode ?"): > On Sat 20 Jul 2019 at 04:35PM +01, Ian Jackson wrote: > > If people start using dgit more, or the tag2upload service (when it's > > operatioal) it might be worth dgit and git-debrebase conv

Bug#857490: [PATCH] dgit-maint-pbo(7): Add to .gitignore

Signed-off-by: Ian Jackson --- .gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index a5e13eab..6e87a619 100644 --- a/.gitignore +++ b/.gitignore @@ -16,6 +16,7 @@ dgit-maint-native.7 dgit-maint-merge.7 dgit-maint-gbp.7 dgit-maint-debrebase.7 +dgit-maint

Bug#857490: [PATCH] dgit-maint-bpo(7): new manpage

Sean Whitton writes ("Bug#857490: [PATCH] dgit-maint-bpo(7): new manpage"): > On Mon 01 Jul 2019 at 12:06pm +0100, Ian Jackson wrote: > > Possible solutions may include: [...] > > I think the best thing to recommend is to use the rebasing backports > workflow.

Bug#926656: git-debrebase docs are intimidating

Sean Whitton writes ("Re: Bug#926656: git-debrebase docs are intimidating"): > On Mon 08 Apr 2019 at 03:43PM +01, Ian Jackson wrote: > > Package: git-debrebase > > Version: 8.4 > > > > Sam Hartman wrote the following me in private email. It is a apposi

Bug#932476: git-debpush gbp/unapplied upstream tree check

Sean Whitton writes ("Re: Bug#932476: git-debpush gbp/unapplied upstream tree check"): > On Fri 19 Jul 2019 at 10:51PM +01, Ian Jackson wrote: > > As I wrote in private email: > > > > For gbp and unapplied, I think it would be very sensible to check that >

Bug#932558: git-debpush service is not deployed

Package: git-debpush Version: 9.3 Severity: important Control: block 932520 by -1 This is a tracking bug. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932555: dgit and gdr automatic quilt mode ?

(in the case of dgit) or too much work for what is usually a one-off (for gdr) ? Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932553: tag2upload must pass -k to dgit

Package: dgit-infrastructure Version: 9.3 Otherwise it will try to use the key corresponding to the Maintainer from the changelog, which is not going to work. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address

Bug#932490: bc: ^D can stop working in bc after some ^C

Package: bc Version: 1.06.95-9+b3 Severity: minor Steps to reproduce: 1. Run bc with no arguments 2. Type some decimal digits, "3939" say, and do not hit return. 3. Press ^C to cancel the half-written command 4. Press ^D to try to quit bc Expected behaviour: bc silently exits. Observed

Bug#932465: dgit cowbuilder' fails with "unrecognized option"

gregor herrmann writes ("Re: Bug#932465: dgit cowbuilder' fails with "unrecognized option""): > On Fri, 19 Jul 2019 19:56:32 +0100, Ian Jackson wrote: > > In the meantime, gregor (and anyone else reading this): > > I think a workaround is to pa

Bug#932479: want git-tagpending

good idea I may write a first cut of this script. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932478: --quilt=foo+nopatches or similar

l with git-debpush, but it would make sense with dgit too. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932477: git-debpush checking that patches (un)apply

in the general case. Unfortunately all of this really needs a playtree and we don't want git-debpush to grow a reference to Dgit.pm, so before we can do this we want to convert playtree_setup to shell (and put a copy in each of the .debs, like we do with Dgit.pm). Ian. -- Ian JacksonThese

Bug#932476: git-debpush gbp/unapplied upstream tree check

be a common user error and it's very easy to implement. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932322: A different approach based on suite-map

mit, common to both branches. Good plan. That patch: Acked-by: Ian Jackson > You then end up with csuite names like bionic-updates-train (i.e. > [$UbuntuRelease]-[updates|proposed]-[$OpenstackRelease]), which are > specified on the command-line as bionic-updates:train [1] > > s

Bug#932475: dgit autopkgtest intolerant of git message change

Source: dgit Version: 9.2 Control: affects -1 src:git User: debian...@lists.debian.org Usertags: needs-update git changed Couldn't find remote ref to couldn't find remote ref and this broke our test case. 9.3 is still broken. Upload will follow shortly. Ian. -- Ian Jackson

Bug#932459: git-debpush: support forcing individual checks

kes this new feature much less useable. How about adding `[--force=THING]' to the per-failure error message and doing this: - fail "some checks failed; you can override with --force" + fail "some check(s) failed; say just --force to override them all" or something ? Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932465: dgit cowbuilder' fails with "unrecognized option"

Control: reassign -1 cowbuilder Control: retitle -1 cowbuilder: Please implement --no-source-only-changes gregor herrmann writes ("Bug#932465: dgit cowbuilder' fails with "unrecognized option""): > AFAIK, pbuilder knows about --no-source-only-changes but cowbuilder > doesn't .. (So it can be

Bug#932322: dgit: Add support for Ubuntu cloud archive

see if I can do my own audit to see whether / is OK. Please let me know the list of necessary changes. A cursory glance has found one place already where / would cause trouble; it needs a code change but it would not affect your use case. -- Ian JacksonThese opinions are my own. If

Bug#932096: tag2upload. upstream handling

am tag, to get this check, since it's not going to go hunting for one. I suppose maybe there could be an option to enable it but it seems quite a minor benefit.) Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932096: tag2upload. upstream handling

; Would that satisfy your objectives here? Oh, yes. Good idea. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#932096: tag2upload. upstream handling

and should check that the specified commitish is an ancestor of the maintainer view. tag2upload should pass --upstream-commitish whenever upstream info appeared in the tag. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk

Bug#932095: tag2upload always fails with baredebian

about to file. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#931552: git-debrebase merge resolution

te ad-hoc gbp to gdr history rewriter) -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.

Bug#931509: /usr/bin/git-deborig: git-deborig prints error message to stdout

Package: devscripts Version: 2.19.5~bpo9+1 Severity: normal File: /usr/bin/git-deborig zealot:example> git-deborig --just-print | sed 's/^/stdout: /'; echo ${PIPESTATUS[*]} stdout: upstream/1.0 stdout: ../example_1.0.orig.tar.xz stdout: git -c 'tar.tar.xz.command=xz -c' archive

Bug#756978: .tar-less push

Control: close -1 I'm not sure this is very actionable any more. Hopefully forthcoming ideas about "push to upload" will make this unnecessary. Ian. -- Ian JacksonThese opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private add

Bug#931213: rpush does not work with split brain quilt modes [and 1 more messages]

Control: severity -1 important Ian Jackson writes ("rpush does not work with split brain quilt modes"): > Nevertheless, given the simplicity of the fix, and the fact that this > fix makes my new test case pass as expected, this is IMO a candidate > for a stable update to buster

<    1   2   3   4   5   6   7   8   9   10   >