r than them getting your
copy on which a reply-to-all goes to submit@ again with no bug
number.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
t has
its own idea of the public keys to use for signature verifications.
But this test case should not involve any of that.)
FYI this is currently preventing the migration of the new dpkg.
>From the above it seems to me that that migration block is correct
because src:dpkg has a regression here
ably --debug-quick-random, which I don't
think there was a way to easily control other than by wrapping
gpg-agent.
AFAICT the bodges are in
tests/tstunt/gpg
tests/tstunt/gpg-withagent
tests/tstunt/gpg-agent
and tests/tstunt/gpg-locked is a previous attempt which is no longer
used.
HTH.
org/pkg/rsync
and it says under "versions"
NEW/unstable: 3.1.3-9
which is rather odd. I thought you should be told.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
jects are preloaded only from the
> standard search directories and only if they have set-user-ID mode bit
> enabled (which is not typical).
Obviously it wouldn't be right for eatmydata to be loaded by actually
setuid programs.
Ian Jackson writes ("Re: Bug#963508: /lib/ld
Aurelien Jarno writes ("Re: Bug#963508: /lib/ld-linux.so.2: LD_PRELOAD breaks
with plain filename"):
> On 2020-06-23 11:46, Ian Jackson wrote:
> > Should apparmor make a difference between absolute paths and leafnames
> > in LD_PRELOAD ? Because I can repr
libfaketime.so.1' from LD_PRELOAD cannot be preloaded
> > (cannot open shared object file): ignored.
> > $
>
> > This message on debian-user seems related:
> > https://lists.debian.org/debian-user/2017/03/msg00335.html
>
> Yes, there seems to be an issue
Package: libc6
Version: 2.28-10
Severity: normal
File: /lib/ld-linux.so.2
Hi. I found this behaviour:
$ eatmydata man ls >/dev/null
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libeatmydata.so' from
to fix and we (the dgit
maintainers) will fix it promptly. But it seems the proper conduct to
me.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
lusive, compared
to the value to be gained.
> So I think we can close the clone of this bug against Policy for now.
The bugs seem very confusing to me. A sprawling mass of
partially-duplicated stuff. See my comment above for a suggested
wording clarification.
Ian.
--
Ian Jackson
the
right place.
So I think it would be best if lintian would warn about 1.0 format
native source packages with non-native versions, with a suitable
explantion which will encourage the maintainer to override the
warning if they did this on purpose.
Ian.
--
Ian JacksonThese opinions are my own
that it is easy to do this by
mistake. The maintainer can override it if it's deliberate.
For non-1.0 packages I think the warning should be removed but from
lintian's pov I can see that that would be blocked by the policy
debate.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
P
why it was designed the way it was.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
as it
goes but doesn't address the key problems, namely that the single
patch ends up inside the tree.
This could be solved by a new `3.0 (diff)' format perhaps. If and
when that is provided then this one scenario would perhaps be better
handled that way. But we are not there yet.
The other two scen
Sean Whitton writes ("Bug#961683: dgit-maint-debrebase(7): Drop bad advice
about upstream/ tag case"):
> Package: dgit
> Version: 9.10
> Tags: patch
Acked-by: Ian Jackson
Sean Whitton writes ("Bug#961682: Dgit::upstream_commitish_search(): should
fail if more than one tag found"):
> Package: dgit
> Version: 9.10
> Severity: important
> X-debbugs-cc: brem...@debian.org
> Attached is a minimal fix.
Reviewed-by: Ian Jackson
, see
this posting of mine to the xen-devel list and various Xen folks:
https://lists.xenproject.org/archives/html/xen-devel/2020-05/msg01710.html
Thanks,
Ian.
>From 143c0b32f7db83ca63bb80b9bd9486dd62dffc71 Mon Sep 17 00:00:00 2001
From: Ian Jackson
Date: Wed, 27 May 2020 17:00:45 +0100
Subj
Hans van Kranenburg writes ("Re: [PATCH 2/2] debian/rules: --no-start for xen
dh_installinit"):
> On 5/26/20 12:44 PM, Ian Jackson wrote:
> > I think it would be wise to look at the generated .debs and see that
> > they contain (only) the expected pieces in their main
van Kranenburg
> Closes: #932759 (1/2)
> Fixes: cc85504103 "xen init script: Do nothing if running for wrong Xen
> package"
Reviewed-by: Ian Jackson
using --no-start
>
> Closes: #932759 (2/2)
> Signed-off-by: Hans van Kranenburg
Reviewed-by: Ian Jackson
I think it would be wise to look at the generated .debs and see that
they contain (only) the expected pieces in their maintscripts.
Ian.
roach leaves you with 0.14.0's
autotools output (because it looks to git like you added it!) but
0.14.1's autotools input. So this only works well if the 0.14.0
Debian branch you start with was made from something which looks like
upstream git.
Ian.
--
Ian JacksonThese opinions are my own.
If
it.
The patch applies cleanly as far back as buster, at least.
Regards,
Ian.
[1] https://www.greenend.org.uk/rjk/disorder/
>From a36579b07058b6bfcb5f7472e404c354bfa2813d Mon Sep 17 00:00:00 2001
From: Ian Jackson
Date: Sat, 2 May 2020 19:40:06 +0100
Subject: [PATCH] cookies: Properly han
Nikolaus Rath writes ("Bug#958989: dgit-user(7): building instructions don't
work"):
> Here's another datapoint:
>
> $ dgit clone valgrind
> $ cd vagrind; sbuild -c buster-amd64
>
> works fine (i.e., if I don't apply any changes).
Can you please send me those changes ? Best would be if you
Nikolaus Rath writes ("Bug#958989: dgit-user(7): building instructions don't
work"):
> On Apr 28 2020, Ian Jackson wrote:
> >mkdir ../aside
> >mv ../valgrind_* ../aside
> >sbuild --chroot-mode=autopkgtest --autopkgtest-virt-server=null -A \
> >
Nikolaus Rath writes ("Re: Bug#958989: dgit-user(7): building instructions
don't work"):
> On Apr 28 2020, Ian Jackson wrote:
> > Could I get you to do this:
> >
> > sbuild -c buster-amd64 -b -n 958989
>
> Uhm. I feel pretty dumb, but what is the "
Nikolaus Rath writes ("Re: Bug#958989: dgit-user(7): building instructions
don't work"):
> I updated the chroot about an hour before I filed the bug.
This is getting quite odd.
> The error occurrs before compilation started.
In that case it is working for me.
> Will send you a full log
Ian Jackson writes ("Re: Bug#958989: dgit-user(7): building instructions don't
work"):
> I will try with those patches...
They don't seem to have fixed the FTBFS for me.
I ran this:
sbuild --chroot-mode=autopkgtest --autopkgtest-virt-server=null -A \
--no-clean-source --dpk
l-security
but it didn't seem to contain that patch.
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.
Nikolaus Rath writes ("Re: Bug#958989: dgit-user(7): building instructions
don't work"):
> FWIW, I have tried this on an AMD64 buster system with an AMD64 chroot. When
> compiling without schroot it works fine (I was trying to add support for the
> copy file range syscall, not fix a compile
Nikolaus Rath writes ("Bug#958989: dgit-user(7): building instructions don't
work"):
> FWIW, I have tried this on an AMD64 buster system with an AMD64 chroot. When
> compiling without schroot it works fine (I was trying to add support for the
> copy file range syscall, not fix a compile error)
Nikolaus Rath writes ("Re: Bug#958989: dgit-user(7): building instructions
don't work"):
> On Apr 27 2020, Ian Jackson wrote:
> > Nikolaus Rath writes ("Bug#958989: dgit-user(7): building instructions
> > don't work"):
> >> But this eventua
Nikolaus Rath writes ("Bug#958989: dgit-user(7): building instructions don't
work"):
> I'm trying to follow dgit-user(7) to build a modified version of a package.
> I did:
Hi. This is a thing you should be able to do.
> $ dgit clone valgrind
> $ cd valgrind
> $ git apply
his issue, I filed this bug report against
> both packages. Can you please investigate the situation and reassign the
> bug to the right package?
I hope what I have done with the bug (i) has the right syntax and did
what I hoped and (ii) meets with everyone's approval.
Regards,
Ian.
--
me number or something?'.
There is absolutely no requirement for this to correspond to the
source format.
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.
Chris Lamb writes ("Re: Bug#953554: Please permit Debian revisions with 1.0
native packages [and 1 more messages]"):
> Ian Jackson wrote:
> > I have no problem with this being a lintian warning. In this bug I am
> > requesting this "error" to be returned to i
Control: clone -1 -2
Control: reassign -2 debian-policy
Felix Lechner writes ("Re: Bug#953554: Please permit Debian revisions with 1.0
native packages [and 1 more messages]"):
> On Wed, Mar 11, 2020 at 4:58 AM Ian Jackson
> wrote:
> >
> > It works today. The only pr
Felix Lechner writes ("Re: Bug#953554: Please permit Debian revisions with 1.0
native packages"):
> On Tue, Mar 10, 2020 at 7:51 AM Ian Jackson
> wrote:
> > I am packaging a small program for which I am the upstream. It does
> > not make sense to use a complicat
with calling this an error.
Previously it was a warning. (Full disclosure: I know the dpkg
maintainer disagrees with my position here.)
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
Ian Jackson writes ("Re: Bug#953183: Acknowledgement (Default for --wipe or
--zero does not seem as documented)"):
> This just happened to me:
>
> 2020-03-05 16:16:43 Z executing ssh ... root@172.16.144.30 lvcreate -Z y -W y
> -L 1M -n debian.buster.guest.osstest-disk
This just happened to me:
2020-03-05 16:16:43 Z executing ssh ... root@172.16.144.30 lvcreate -Z y -W y
-L 1M -n debian.buster.guest.osstest-disk elbling0-vg
WARNING: dos signature detected on
/dev/elbling0-vg/debian.buster.guest.osstest-disk at offset 510. Wipe
it? [y/n]:
So -Z y -W y is
Package: lvm2
Version: 2.02.168-2
Severity: important
This happened to me:
root@elbling0:~# lvcreate -L 1M -n debian.buster.guest.osstest-disk
elbling0-vg
WARNING: dos signature detected on
/dev/elbling0-vg/debian.buster.guest.osstest-disk at offset 510. Wipe it?
[y/n]: ^C Interrupted...
Package: lvm2
Version: 2.02.168-2
This happened to me:
root@elbling0:~# lvcreate -L 1M -n debian.buster.guest.osstest-disk
elbling0-vg
WARNING: dos signature detected on
/dev/elbling0-vg/debian.buster.guest.osstest-disk at offset 510. Wipe it?
[y/n]: ^C Interrupted...
Aborted wiping of
Package: lvm2
Version: 2.02.168-2
This happened to me:
root@elbling0:~# lvcreate -L 1M -n debian.buster.guest.osstest-disk
elbling0-vg
WARNING: dos signature detected on
/dev/elbling0-vg/debian.buster.guest.osstest-disk at offset 510. Wipe it?
[y/n]: ^C Interrupted...
Aborted wiping of
Ian Jackson writes ("Re: new network-manager-strongswan package [and 1 more
messages]"):
> Rather than going another round with you I propose to fix this as
> follows:
> 1. upload your version as-is
> 2. immediately "nmu" an upload to only fix the previ
nalised in git (that is, the release changed to
"unstable", and/or the trailer line put in).
I hope this meets with your approval. If in future you would like me
to deal with such an issue differently, please let me know.
Ian.
--
Ian JacksonThese opinions are my own.
If I e
hink are brought in by pydoctor...
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.
here.
Thanks to Anthony Fok for fixing pydoctor but the py2 rot seems wider
including in gbp itself.
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.
For -devel, context is that Anthony Fok just uploaded a new upstream
version of pydoctor (a tool for extracting API docs for python
modules) in order to fix a couple of upstream bugs. Anthony, thank
you very much for your work to help fix one of our (mutual) indirect
dependencies.
Unfortunately
ri-guest") a maintainer of it.
I think you can do all the rest of the setup yourself. Let me know if
you want anything else doing.
> On 2/24/20 3:02 PM, Ian Jackson wrote:
> >
> > I looked at the diff etc. and I have some observations:
> >
> > * It woul
ven on very old versions of Debian.)
(I am experimentally using X-Debbugs-CC to try to file this MR as a
bug and also reply to Salsa...)
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.
ve user `iwj' access to the repo.
* If it's OK with you I like doing reviews in public. I think a "new
upstream version" bug against the package is a good place because it
means that if either of us drops it, our work is easily available as
a starting point for others.
Regards,
Ian.
--
documentation generation ?
Thanks,
Ian.
(CCing various people who helped last time pydoctor broke...)
--
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.
Control: close -1
Michael, I am the maintainer of this package. As the maintainer I
have declared this a non-bug. Reopening it is pure bug tag.
Ie, it is abuse. Please stop.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk
Package: openscad
Version: 2019.05-3
Severity: normal
An idle copy of openscad uses about 7% of the CPU on my very fast
laptop. stracing it shows it polling, with a short timeout. Some of
this work is to spot changes to input files, but it calls call poll()
many times for each time it actually
Debian Bug Tracking System writes ("Bug#930869: marked as done (Don't release
with buster)"):
> The new maintainer, Ian Jackson, seems to be quite busy, and did not
> decide yet whether to drop the i386 parts. But, even if untestable
> for most of us, they're unlikely to
for the conversion
script(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.
eturn status 256 executed command :
/usr/bin/gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS
"/tmp/psinZUL0CV"
The interpreter seems to have failed, cannot proceed !
$
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org
I would accept patches. Preferably as
a git branch - you can find the git history with `dgit clone' - but
any other format would be welcome.
Since I wouldn't use this feature myself I don't currently intend to
implement it myself.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
# uses tag, eg "v1.2.3"
but this is in general broken
No -i etc. mentioned in full description of new-upstream
What actually works is this
git debrebase -fupstream-not-ff new-upstream 4.13.0+10-g721f2c323c-1 \
upstream/4.13.0+10-g721f2c323c -i
--
Ian JacksonThese opinion
635b2a6e7d55503a75ace034d96326d5b2197798
You can just dpkg-buildpackage -uc -b and dpkg -i the .deb.
Upload will probably be tomorrow.
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
not the case then
please feel free to downgrade or even close this report against 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.
> The system is running buster, git is at version 1:2.20.1-2+deb10u1
> git-buildpackage is at 0.9.14 and dgit is at 9.9~bpo10+1
Thanks. I have reproduced the problem.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a p
be able to reproduce this on stretch. What versions
of git-buildpackage and git do you have installed ?
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.
gt; gbp:error: Failed to apply
> '/build/git/b/binutils/.git/dgit/unpack/binutils-2.33.90.20200122/debian/patches/001_ld_makefile_patch.patch':
> Failed to commit tree: fatal: invalid date format: ??
> gbp:error: Couldn't apply patches
> gbp pq import failed: subprocess failed with er
Package: authbind
Version: 2.1.2
--
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.
Package: dput-ng
Version: 1.13+deb9u1
I don't think this Recommends makes sense. I think in general it is
wrong to Recommend bash-completion. If the user doesn't have it
installed that's probably because they don't like it...
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed
Thanks for the patch. Unfortunately (due mostly to me flailing) my
tests of this are so far inconclusive. I will get back to this in
January.
Regards,
Ian.
Ian Jackson writes ("debian-installer multi-console race with preseeding"):
> A workaround is to specify *exactly one* appropriate console=
> on the kernel command line. This causes the kernel to report only
> that console in /proc/consoles and the bug is avoided.
This
ied a manpage, help message, etc.
This program is useful with formail to work around a bug in git-am,
where if it gets a base64-encoded patch it fails because the base64
correctly contains cr-lf line endings.
Ian.
#!/usr/bin/perl -w
# Copyright (C)2019 Citrix plc
# Author: Ian Jackson
# GPLv3+
I just experienced this bug. Thanks for some very useful hints and
pointers from Colin Watson.
This is particularly awkward to debug because one of the parallel
invocations of d-i is usually invisible. And the precise results are
the results of races and can be different from one run to
.
Mark wrote:
| Are you satisfied that this bug can be closed?
So, I think this bug should be closed now, unless there is something
that remains to be done to improve things here.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net
bug ought to be closed. Everything
in it has been dealt with, one way or another.
If there are any remaining particular, specific, issues or problems,
it would probably be most convenient if they were filed as individual
bugs. That would let us get to grips with them properly.
Thanks,
Ian.
--
I
Package: lvm2
Version: 2.02.168-2
I have encountered a situation where:
2019-10-28 16:45:09 Z executing ssh ... root@172.16.144.40 lvcreate -Z y -L
1M -n debianhvm.guest.osstest-disk italia0-vg
WARNING: dos signature detected on /dev/italia0-vg/debianhvm.guest.osstest-disk
at offset 510.
Russ Allbery writes ("Bug#943374: dgit push-source fails and loses a package
version number without retries"):
> Package: dgit
> Version: 9.9
> Severity: normal
>
> This was unpleasant:
How annoying.
> The network from which I was trying to do dgit push-source had 20% packet
> loss. If the
.
libc-bin suggests no packages.
-- no debconf information
>From 90d97e44554a3f1a8b3d5739598337da480c7e37 Mon Sep 17 00:00:00 2001
From: Ian Jackson
Date: Tue, 22 Oct 2019 15:15:30 +0100
Subject: [PATCH] getconf(1): Mention `sysconf', mostly for the benefit of
search
This makes this handy utility cons
Just to confirm that this is still an issue in current buster.
Ian.
Ian Jackson writes ("Bug#792547: grub-installer: add option to _not_ install to
UEFI boot order"):
> I see that Ian C updated this patch (in July 2015) and reported
> testing it successfully. Is it now OK ?
every Debian release I update our workaround to apply to the current
rel
tests at least as
reliable (I think I may have seen some anomalies with strange corner
cases with the original runes above, but I haven't tried a systematic
repro). (It is also rather mad.)
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.
64-linux-gnu/perl-base) at
> /usr/bin/git-deborig line 93.
This is odd. I wonder why the tests don't catch it.
Anyway thanks for the report.
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.
yes | head -1 ; then id; fi'
+ set -o pipefail
+ yes
+ head -1
y
mariner:~>
11:39 that’s more readable to me at least
11:40 I guess the performance is not really a consideration since it's
O(n) either way
11:40 (both because the worst case is O(n) and because the rest
wo messages as going together, even in the
presence of other noise
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.
Sean Whitton writes ("Bug#935443: [PATCH] dgit-maint-bpo(7): Mention occasional
need for --new"):
> On Mon 09 Sep 2019 at 01:38PM +01, Ian Jackson wrote:
> > But if you prefer it towards the end then OK.
>
> I don't think it's that odd to put it before TERMINOLOGY b
Ian Jackson writes ("Re: Bug#935443: [PATCH] dgit-maint-bpo(7): Mention
occasional need for --new"):
> The text describing the workflows is very long. Many people who read
> this manual will already know roughly how to do backports with git and
> will already have cho
ow to do it with dgit.
I thought this bit about --new was important enough to go above all
that. But it felt very odd to put it above TERMINOLOGY which probably
ought to come first.
But if you prefer it towards the end then OK.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
If I em
ntain the registry since devscripts maintainers don't want it".
Open questios then are filename and syntax but maybe -devel can tell
us what to use.
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
Sean Whitton writes ("Re: Bug#935443: [PATCH] dgit-maint-bpo(7): Mention
occasional need for --new"):
> On Thu 05 Sep 2019 at 04:50PM +01, Ian Jackson wrote:
> > +=head1 GENERAL TIPS
> > +
> > +The first time a package is backported
> > +for any particul
Control: severity -1 important
Ian Jackson writes ("Re: fetch can fail due to mirror lag"):
> The http changes in 9.6 broke this. I just experienced it myself and
> was able to repro and write a fix.
Also, given that this is a bug in 9.6 and later, I think the
experienced frequ
Control: tags -1 pending
Control: fixed -1 9.5
The http changes in 9.6 broke this. I just experienced it myself and
was able to repro and write a fix.
I need to add a test case for it too.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net
/dgit/dgit_9.7.dsc gave HTTP code 302
--
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.
sers
each of these commands.)
This ought to work without depending on any of these utilities, and
without depending on git, etc.
I think this means we need a Debian-wide env var or a config file.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @
If you like this idea please send another patch.
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.
Ian Jackson writes ("[PATCH] dgit-maint-bpo(7): Mention occasional need for
--new"):
> Closes: #935443
> Signed-off-by: Ian Jackson
Rereading the bug description I thought a 2nd patch was needed.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you
Closes: #935443
Signed-off-by: Ian Jackson
---
dgit-maint-bpo.7.pod | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/dgit-maint-bpo.7.pod b/dgit-maint-bpo.7.pod
index e977d258..e776a478 100644
--- a/dgit-maint-bpo.7.pod
+++ b/dgit-maint-bpo.7.pod
@@ -47,6 +47,12
that users probably want
push-source rather than push-built.
> On Thu 05 Sep 2019 at 09:46AM +01, Ian Jackson wrote:
> > Is this worth the disruption ?
>
> If what I just wrote is the only reason for doing this, then I'm not
> convinced that it is.
Fair enough. Maybe
Control: tags -1 patch
Comments on this proposed text would be very welcome - particularly,
does it address the problem with discoverability/encouragement of
--new ?
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk
Control: tags -1 patch
Comments on this proposed text would be very welcome - particularly,
does it address the problem with discoverability/encouragement/choice
of --overwrite vs --deliberately.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address
Closes: #935443
Signed-off-by: Ian Jackson
---
dgit.1 | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/dgit.1 b/dgit.1
index 8969e2f2..c270b303 100644
--- a/dgit.1
+++ b/dgit.1
@@ -630,11 +630,16 @@ fails even on ignored untracked files.
This could perhaps
t(1) means "any push that isn't a fast-forward". I don't
> know if I'm the only one for whom it has that connotation.
This makes sense. So, I am changing uses of "rewind" which do not
mean precisely going back to an ancestor.
I think we can often use the word "re
Closes: #928473
Signed-off-by: Ian Jackson
---
dgit.1 | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/dgit.1 b/dgit.1
index 29825c2c..2c224294 100644
--- a/dgit.1
+++ b/dgit.1
@@ -679,6 +679,7 @@ unless you know what you are doing.
This option is useful if you
where the user has already made an earlier intervention.
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.
301 - 400 of 3535 matches
Mail list logo
