Sean Whitton writes ("Bug#906786: dgit --build-products-dir build
malfunctions"):
> On Tue 21 Aug 2018 at 02:21AM +0100, Ian Jackson wrote:
> > Well, that's all wrong.
>
> Indeed. Looks like I didn't test this code path sufficiently
I'm not sure if this is the right place but I wanted to publish this
information sooner rather than later.
Closes: #907190.
Signed-off-by: Ian Jackson
---
dgit-maint-debrebase.7.pod | 47 ++
1 file changed, 47 insertions(+)
diff --git a/dgit-maint
Package: faketime
Version: 0.9.6-7+b1
1. faketime does not properly validate the supplied advanced timestamp
format:
$ faketime -f '2018-06-26 09:00:03+02:00' date -R
Tue, 26 Jun 2018 09:00:03 +0100
$ date -R -d '2018-06-26 09:00:03+02:00'
Tue, 26 Jun 2018 08:00:03
Ian Jackson writes ("dgit quilt-fixup sometimes runs dpkg-source"):
> 2. My xen tree does this too, git-show-ref output below.
>I'm on dgit/experimental.draft.
This part of this bug report is actually #907206. That leaves 1.,
which is a design problem.
Ian.
EAD
5b96d7813882ce8d1cb9b498f0a8389f92c0b7cf
refs/wip/wtree/refs/heads/dgit/sid.draft
--
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.
e HEAD
6aabb93ad745360200d7a22e38a7e5c3aec40349
zealot:xen>
This can be found at:
g...@salsa.debian.org:xen-team/debian-xen.git
I think it is confused by the subdirectory.
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
Package: git-debrebase
Version: 6.9
The problem is that the memo did not include $recurse as part of the
lookup key. This could have been serious, but luckily the result is
simply that git-debrebase complains about the directory names, as if
they were unused patches, instead.
Ian.
--
Ian
the Release Team might want to informally consult the TC, or other
relevant people in Debian such as the DPL, ftpmaster or the
antiharassment team.
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 by
Package: git-debrebase
Version: 6.9
zealot:xen> git-debrebase convert-from-gbp 733450b39b
git-debrebase: error: patch # repeated in debian/patches/series !
This is a very funny way of looking at things.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an addr
es, if you really want that:
git debrebase make-patches
git diff dgit/dgit/sid..HEAD -- debian/patches
Also of course there is
git debrebase status
I think some of this information should be in the manpages.
I'll file a bug about that.
--
Ian JacksonThese opinions are my
Simon McVittie writes ("Re: Bug#906949: Clarify documentation location in a
Python2-less distribution"):
> On Thu, 23 Aug 2018 at 15:43:06 +0100, Ian Jackson wrote:
> > There are two reasons for the standardised paths in /usr/share/doc:
> > 1. So that the user can fin
Norbert Preining writes ("Re: Bug#906901: debian-policy: Perl script shebang
requirement is disturbing and inconsistent with rest of policy"):
> Hi Ian,
> > This confusing user experience only occurs if someone prepends a
> > different perl to $PATH. Has anyone actually ever done this and got
>
Stuart Prescott writes ("Bug#906949: Clarify documentation location in a
Python2-less distribution"):
> b) keep using /usr/share/doc/python-foo: do we stick with
> /usr/share/doc/python-foo as a version-independent path even though no such
> package exists once the Python 2 package is gone? (I
ast, old modules will work with new perl binaries ?
If I wanted to install my own Perl I would make sure to have
/usr/bin/perl point to it.
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.
Jonathan Nieder writes ("Bug#906901: debian-policy: Perl script shebang
requirement is disturbing and inconsistent with rest of policy"):
> Dominic Hargreaves wrote:
> > On Tue, Aug 21, 2018 at 08:42:11PM -0700, Russ Allbery wrote:
...
> In this thread, there are three possible rules proposed:
>
cision to the TC.
Or, the Release Team might want to informally consult the TC, or other
relevant people in Debian such as the DPL, ftpmaster or the
antiharassment team.
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 w
s the right --quilt
option or config. Or, maybe, run git-debrebase
forget-was-ever-debrebase.
Along with providing that new subcommand. That would delte a
debrebase-last, which might also be necessary sometimes.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an
Ruben Undheim writes ("Bug#906908: dgit: Fails to push-source for gbp repo.
dgit thinks it is git-debrebase repo"):
> Well, if the error message is good, I do not think extra documentation
> is necessarily required.
OK, thanks.
My current idea of the error message is
Branch is managed by
Control: severity -1 minor
Ruben Undheim writes ("Bug#906908: dgit: Fails to push-source for gbp repo.
dgit thinks it is git-debrebase repo"):
> myshell> dgit --gbp push-source
...
> git-debrebase: error: found unprocessable commit, cannot cope: edits
> debian/patches
ed to make changes we may later ask them
to reverse. And it will remove the animus behind Norbert's setting of
this bug to `serious' - which I think is arguably justified.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk,
Ian Jackson writes ("Re: Bug#906908: dgit: Fails to push-source for gbp repo.
dgit thinks it is git-debrebase repo"):
> Can you please send me the output of
> git show-ref
> like I asked ? dgit uses other refs to decide whether this is
> supposed to be a gdr branch.
A
Ruben Undheim writes ("Re: Bug#906908: dgit: Fails to push-source for gbp repo.
dgit thinks it is git-debrebase repo"):
> Hi Ian,
> > But, can you please tell me the output of
> > git-rev-parse HEAD
> > git-show-ref
> > and tell me where to get these git commits (salsa somewhere I guess?)
>
Control: severity -1 serious
Ruben Undheim writes ("Bug#906908: dgit: Fails to push-source for gbp repo.
dgit thinks it is git-debrebase repo"):
> First time I am unable to push with 'push-source' and had to go back to
> 'dput'.
> Strange that it happens suddenly now. Seems like dgit thinks my
Héctor Orón Martínez writes ("Bug#906317: dgit: consider demoting
git-buildpackage to recommends"):
> For some background, I would like to enable Debian porterbox users
> to be able to run `dgit push`, however some of my colleagues on the
> Debian sysadmin team, consider installing `dgit` a
ature via stable-backports)
For the reasons I have given, I'm not sure that this would help.
Perhaps in the future gbp pq could be its own .deb, but I doubt we
would want to do that in stable.
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.
must use a new version number.
To retry it is much easier to c the command that dgit ran, which is
shown immediately beforehand. It is probably better to refer to that
than to just the changes pathname.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address
, that's all wrong.
I have a vague memory that this was not expected to work, but the docs
don't seem to mention it and I can't find an open bug either.
I'm not sure how this would be implemented but it should either work
or be rejected.
Ian.
--
Ian JacksonThese opinions are my own.
If I
",
"8807b6752bdd45136d099d59586bf7161ebea2f3", undef) called at /usr/bin/dgit line
4237
main::dopush() called at /usr/bin/dgit line 4724
main::cmd_push() called at /usr/bin/dgit line 7142
! Push failed, while preparing your push.
! You can retry the push, after fixing
garding packaging technology, and certainly
less visible to the whole Debian ecosystem).
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.
source
convert-from-unpatched-upstream
have the same problem as
convert-from-unpatched
TBH.
Maybe the answer is to provide aliases.
convert-from-gbp
convert-from-unpatched
?
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.
Control: retitle -1 consider renaming convert-from-gbp
Ian Jackson writes ("Re: Bug#905433: git-debrebase: debrebase new-upstream
fails with "uninitialized value""):
> I think you've probably figured this out now, but in your situation
> git-debrebse convert-from
Jochen Sprickerhof writes ("Bug#906641: git-debrebase: debrebase
convert-from-gbp gives fatal: Not a valid object name archive/debian/0.4.8-1"):
...
> ~> gbp clone g...@salsa.debian.org:science-team/ros-catkin-pkg.git
> gbp:info: Cloning from
) might be needed in some exceptional cases but
normally there is a better way.
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#906139: debian-policy: versioned depends on
libjs-sphinxdoc unsatisfiable on stretch"):
> On Fri 17 Aug 2018 at 03:44PM +0100, Ian Jackson wrote:
> > This is a bug, surely. It should be in ${sphix:Depends} or something.
> > Then you c
Sean Whitton writes ("Re: Bug#906139: debian-policy: versioned depends on
libjs-sphinxdoc unsatisfiable on stretch"):
> On Fri 17 Aug 2018 at 11:37AM +0100, Ian Jackson wrote:
> > What happens, on the system where debian-policy.deb is installed, if
> > this Depends i
where possible, but that should be done by
looking at which of the alternative build dependencies is installer,
or whatever, not by checking dpkg-vendor.
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.
of the content in is still
accessible ? If so, Vagrant's request to downgrade the dependency is
correct.
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.
nder if `fakechroot' is any 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 address which bypasses my fierce spamfilter.
Mo Zhou writes ("Bug#906265: RFH: julia -- ppc64el port of Julia language and
LLVM-6.0"):
> I tried to think of applying for the access to debian's ppc64el porterbox
> but it appears to be impossible for a normal user to install the resulting
> package and build another package. Although maybe I
Ian Jackson writes ("vm: fails to byte-compile with unversioned emacs"):
> I'm just a user of VM but I need it to stay in Debian. Accordingly I
> intend to NMU this time very soon. I may well make mistakes. Hints
> and tips welcome.
>
> Manoj, if you don't want me
Jonathan Nieder writes ("Re: Next steps on "[GPL-3+]" proposal"):
> Ian Jackson wrote:
> > Changing the version would involve parser changes in all parsers.
>
> I don't follow. Why wouldn't a non-validating parser be able to simply
> ignore the Format
onto the users who care about it, and away
from users who do not (and developers like me who are trying to
support those latter users).
Opinions welcome.
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
d95b5bb31e6d4361e356f0ff0853b6bb172a8b6a and
13e85a6dbc1eeda4f95c0d3afcd205579eab5909.
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 error message should mention that a possible cause of quilt
fixup failure is wrong orig tarballs.
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#904608: Support specifying upstream VCS location in
debian/control"):
> No-one needs to do that extra work anytime soon. Policy lags best
> practices. The fact that debian/upstream/metadata is already being used
> to store a URI to the upstream repository for a large
2-only or
whatever, rather than (say) GPLv2+.
IMO in Debian we should not perpetuate this.
Ian.
[1] politically opposed to my own goals, probably deliberately so on
the part of the SPDX authors
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade
Russ Allbery writes ("Bug#883950: Next steps on "[GPL-3+]" proposal"):
> To be clear, I don't believe there's a way forward here that doesn't
> require at least some rewriting of parsers. Currently, copyright-format
> 1.0 requires either that every License stanza in a Files paragraph contain
>
n having a version number at all in the
machine-readable copyright format is quite possibly a mistake.
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.
nent notice that we have modified
> it. I am not a lawyer, but I believe this is enough for the letter and
> spirit of the license: it tells a user "if you are looking for an
> unmodified GNU Hello, this is not it".
I agree. So maybe my suggested text should read something li
Sean Whitton writes ("Bug#459427: Patch seeking seconds on changelog vs. NEWS
handling"):
> +If an upstream release notes file is available, containing a summary
> +of changes between upstream releases intended for end users of the
> +package and often called ``NEWS``, it should be accessible as
28.html
[1] https://lists.debian.org/debian-devel/2018/07/msg00263.html
[2] See for example:
https://lists.debian.org/debian-devel/2018/07/msg00386.html
--
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 b
her approaches will be
better still. It just means that vendor series are worse than
changing the source package.
--
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.
brebase
status'. On my laptop that is now about 3.4s rather than 77s on your
branch.
I can probably improve this by another factor of maybe 4 - how
worthwhile would that be ? I'd have to do some rework of the diffing
arrangements.
Ian.
--
Ian JacksonThese opinions are my o
Package: git-debrebase
Version: 6.6
Severity: important
Ben Hutchings writes ("Issues with using git debrebase for linux"):
> 1. Safe rebasing
>
> linux is team-maintained, and it's normal for multiple developers to
> push changes multiple times between releases. It's therefore not
> acceptable
Control: reassign -1 git-buildpackage 0.9.9
Sorry, I see you already did this. Your first mail got duplicaed and
delayed by a disk problem on chiark...
Ian.
Control: reasssign -1 git-buildpackage
Ben Hutchings writes ("Bug#905934: git-debrebase: convert-from-gbp may lose
non-git header fields"):
> Package: git-debrebase
> Version: 6.6
> Severity: normal
>
> Where patches have DEP-3 header fields that cannot be directly included
> in git metadata,
40c28bae0584bb3 Mon Sep 17 00:00:00 2001
From: Ian Jackson
Date: Sun, 12 Aug 2018 15:32:12 +0100
Subject: [PATCH 1/3] Assemble.c: Use MD_* names when checking state for
most_recent
The literal constant `6' is pretty opaque here. Source-diving tells
me that .disk.state is a bitmask o
Sean Whitton writes ("Bug#905573: dgit-maint-debrebase(7): improve "Converting
an existing package""):
> Ian, could you explain why you recommended convert-from-gbp in #905433?
> Then I can write a patch for this.
convert-from-gbp does the right thing if there are no patches.
Because if there
Package: chiark-utils
Version: 5.0.2
bash: /usr/bin/hexterm: /usr/bin/tclsh8.4: bad interpreter: No such
file or directory
--
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.
bably figured this out now, but in your situation
git-debrebse convert-from-gbp will do what you need.
I'm increasingly of the opinion that that subcommand needs to be
renamed, in addition to improving the docs.
> Quoting Ian Jackson (2018-08-04 18:15:47)
> > This error message is fixed in
t; There is a small, but real, chance of losing valuable patches this
Of course they are still there in the git history, if you can find
them...
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.
Johannes 'josch' Schauer writes ("Bug#905433: git-debrebase: debrebase
new-upstream fails with "uninitialized value""):
> Package: git-debrebase
> Version: 6.4
> Severity: normal
Thanks for the report. This is a very new tool and as you can see it
has some rough edges both in docs and (at
retreat
abandon
--
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: severity -1 normal
--
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.
Jonathan Nieder writes ("Re: permit access to apt repositories during builds"):
> Ian Jackson wrote:
> > See
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813471#126
> > for a more extended rationale for permitting access to sources
> >
y if the service or protocol was not listed in these files
in the package's targeted Debian releases, an appropriate
versioned build-dependency is needed.)
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private addr
` must then be
+declared. It is permitted to download both binaries and/or sources.
+However, this facility should not normally be used.
+
The targets are as follows:
``build`` (required)
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.
Control: tags -1 - moreinfo
> Yes, exactly. Sounds perfect! Thank you
Great.
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.
he default will be to just git push your current remote to its
usual upstream, if there is one.
Or
git config --global dgit.default.hook-post-push \
'-pushpush; -changelog --unfinalised'
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @ev
has the same problem.) Sorry for not asking when you had all
this readily to hand.
I will also need the corresponding orig tarballs but I guess that they
will be readily available from the archive or from snapshot.d.o.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
If I emai
o_launder_head("launder for rebase") called at
> /usr/bin/git-debrebase line 987
> main::defaultcmd_rebase() called at /usr/bin/git-debrebase line 1855
Thanks to both you and Sean for suggesting a good way to make this
actually work. But, even when it's not working, it ought
Package: autopkgtest
Version: 5.4.2
Tags: patch
>From ee5188ba223d31cbdca70f0601c7683090cddfa9 Mon Sep 17 00:00:00 2001
From: Ian Jackson
Date: Fri, 3 Aug 2018 03:32:50 +0100
Subject: [PATCH] doc/README.package-tests.rst: document
hint-testsuite-triggers
There is currently no official
I'm just a user of VM but I need it to stay in Debian. Accordingly I
intend to NMU this time very soon. I may well make mistakes. Hints
and tips welcome.
Manoj, if you don't want me to NMU this please upload a fix
immediately.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed
Package: dgit
Version: 6.4
I should be able to configure dgit to push my branch to salsa or
chiark or whatever, after each push.
Failures of that push should not be fatal.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk
. That style should be controlled by config.
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.
Control: unarchive 851873
Control: forcemerge 851873 -1
This was a manifestation of #851873 (noatime problem). The error
message is improved 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
Control: fixed -1 6.3
I didn't notice this bug report when I fixed this 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.
Control: fixed -1 6.1
This was done with the proper bpd support 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 which bypasses my fierce spamfilter.
Control: fixed -1 6.2
I forgot the Closes: tag in the changelog.
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.
Control: fixed -1 6.2
This was fixed in 6.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.
with epochs.
Maybe git-dpm tag depends on some branches existing. They don't exist
in the playtree.
git-dpm tag takes a number of options. There wouldn't be any way to
pass them.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk,
full diff.
Maybe this should be broken out into Dgit.pm.
Also, it has been suggested that we should just print the diff if it's
"small". I'm not convinced...
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a p
he logic from new-upstream.
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.
s do have the expected author.
> "When Subject is used, it is expected that the long description is
> outside of the structured fields. With Description it is possible to
> embed them in the field using continuation lines."
I agree that this should be better.
Thanks to both o
-upstream doesn't
> accept options" or "--force is not a valid Debian version".
Indeed.
Thanks for all the bug reports.
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.
to documentation, and/or do some
analysis to guess at the cause (maybe by looking in the reflog).
It is too early really to tell what form this should take.
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
(a
vanilla debrebase), a note that it is hazardous to use plain
git-rebase on git-debrebase branches, and a cross-reference to the
above.
- Perhaps expand on or strengthen the "too early" warning in
dgit-maint-debrebase.
Ian.
--
Ian JacksonThese opinions are my
b74a40569522b1ad8bdb55227e09bcf37c67f2ec: Cannot cope with this commit
(d.0x8; edits debian/patches) at /usr/bin/git-debrebase line 685, line
24.
The line number info etc. here is not useful and makes it look like an
internal erro.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address
build products dir is not '..', it should try copying it from '..'.
Yes.
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.
as `git debrebase`.
I'm really glad now about
git-debrebase: Rename `launder' to `launder-v0'
which means that this docs bug isn't too bad a hazard...
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.
Package: dgit
Version: 6.1
Especially dgit and also git-debrebase are useful for non-participants
in Debian, and their users should be able to use dgit in their native
language.
So we want the possibility for:
* message translation
* manpage translation
at the very least.
Ian.
--
Ian
Sean Whitton writes ("Bug#904859: dgit: should warn when $buildproductsdir is
set but using a command that ignores it"):
> On Sun 29 Jul 2018 at 03:30AM +0100, Ian Jackson wrote:
> > Right. Is it just `build' ?
>
> gbp-build too.
t-buildproductsdir-config is in tests/t
t just `build' ? I guess we should add the bpd thing to
at least some of the dsc import test cases.
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.
Package: dgit
Version: 6.0
Severity: wishlist
This will involve g-f-b on the example git repo and probably messing
with some of the built soure package artefacts.
And it will probably make some tests fail.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address
How about a
providing a command which edits /etc/apt/apt.conf.d/50apt-file.conf to
enable the sources contents ? And, presumably, also runs apt update.
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.
g-reconfigure apt-file were able to edit
/etc/apt/apt.conf.d/50apt-file.conf
(or maybe there would be some other way to easily do this).
* apt-file -a source, or apt-file --source, or something,
worked. Experimenting, I discover that the syntax I wantedd was
--index-
ike the contentse of policyrcd-script-zg2.
We would then change invoke-rc.d and deb-systemd-* to run that script,
instead of /usr/sbin/policy-rc.d. As an additional bonus, the new
script can run policy-rc.d from $PATH which would be more compliant
with Debian policy.
Does that sound sensible ?
Ian.
icy-debian) regarding a NEW package. I have improved
that, a lot, and slightly improved a couple of other messages.
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.
then maybe the answer is just that the admin must configure this
differently depending on what init system they have.
I hope this analysis is helpful.
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
is
> completely dependent on the license of the source/binary being fetched.
> It is probably worth mentioning if we add the apt repo exception.
Right.
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.
801 - 900 of 3535 matches
Mail list logo
