I'm afriad
closing the bug in the Debian BTS this way is premature. The fix is
not in Debian yet.
These bugs will be marked closed by the corresponding upload to
Debian, assuming that the debian/changelog mentions them.
The `fixed-upstream' tag is used for this state.
Regards,
Ian.
--
Ian Jackson
id an upload to experimental
intending to adopt the package, unaware of our efforts (in part
because we failed to write to this RFA bug about them), but that we
are welcoming him, or some such.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @eva
Jesse Smith writes ("Bug#586709: closed by Thomas Goirand"):
> That's just the thing, it is not a bug in this package. The bug exists
> in the init scripts, not in the sysvinit package.
On my stretch system here /etc/init.d/halt is in the `initscripts'
package which comes from the `sysvinit'
new ones.
So, should the next thing be an RM bug requesting the package be
removed from unstable ?
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.
Jesse Smith writes ("Bug#586709: Think I found the problem"):
> [implementation details]
Thanks for looking at this bug. I'm afraid I don't think I agree that
it should be closed, though.
AFAICT the user's complaint is that, when halt or poweroff actually
invoke shutdown, the actual
Hans van Kranenburg writes ("[Pkg-xen-devel] Bug#865086:
xen-hypervisor-4.8-amd64: Default grub entry broken with locales (how to
reproduce)"):
> What am I doing wrong, so that the first test already doesn't give me:
> "Debian GNU/Linux, met Xen-hypervisor"
You are missing the -d option to
Ian Jackson writes ("Re: Should the weboob package stay in Debian?"):
> I look forward to hearing from the Debian maintainer, who I think is
> the first point of contact for the management of the package in
> Debian.
I am concerned about the lack of progress. I would be
Tollef Fog Heen writes ("Bug#904302: Whether vendor-specific patch series
should be permitted in the archive"):
> Second draft:
...
> The Committee recognises that there is a need for packages to behave
> differently when built on different distributions, but this should be
> done by using
, of course. For this reason in general bugs should be
reported against src:xen rather than against binary packages with
Xen versions in their package name.
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: severity -1 normal
Control: retitle -1 xenstore-utils should declare Breaks old xen-utils-common
Ian Jackson writes ("Re: xenstore-utils: removal of xenstore-utils makes files
disappear from xen-utils-common"):
> Indeed I looked at the log and it does show a downgrade, no
Thorsten Glaser writes ("Bug#769494: [Pkg-sysvinit-devel] Bug#769494: Please
mount cgroup automatically"):
> On Wed, 17 Oct 2018, Ian Jackson wrote:
> > I notice that on my laptop I have some binfmt_misc filesystem mounted.
> > I'm pretty sure I don't use anything that
on my laptop I have some binfmt_misc filesystem mounted.
I'm pretty sure I don't use anything that uses binfmt_misc. I also
have something called pstore. IDK what that is. It's emty so I guess
I'm not using it.
This all seems harmless enough. Am I wrong about cgroup ?
Ian.
--
Ian JacksonThe
help and to give some new helpful perspectives on this matter.
Thank you for your contribution to Debian. I thought your message was
very helpful, even if I don't know that I 100% agree with your
conclusion :-).
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you f
Russ Allbery writes ("Bug#911165: debian-policy: drop requirement to ship
sysvinit init script with same name"):
> This is not the sort of thing that we should be dropping on an ad hoc
> basis given the project decision to support multiple init systems, since
> if we give up this principle it
ut from
> /usr/share/insserv/check-initd-order, and to wrap up the output from
> /usr/share/insserv/make-testsuite as an attachment to this bug to allow
> anyone to try to reproduce the problem.
Cool, I didn't know about that. Much better.
Ian.
--
Ian JacksonThese opinions are my o
be a very very bad reason.
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 ("Bug#776413: The priority of the ed package"):
> Bastian Blank writes ("Re: Bug#776413: The priority of the ed package"):
> > Serial lines have absolutely no problem with vim or similar stuff. ANSI
> > command sequences work on all
Ian Jackson writes ("Re: Bug#776413: The priority of the ed package"):
> I don't think ex is in the base system. Are you suggesting that an
> implementation of it should be added ? On my system here it seems to
> be provided by vim.tiny and /usr/bin/ex is 20x the size of /bin/
Bastian Blank writes ("Re: Bug#776413: The priority of the ed package"):
> On Tue, Oct 16, 2018 at 11:49:58AM +0100, Ian Jackson wrote:
> > This makes it sound theoretical, or a question of breaking people's
> > `finger macros'. That is indeed annoying. But there i
nal,
being sure to get the numbers right, or rely on a program like
resize(1)). But then one must remember not to resize the window !
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 ("Re: xenstore-utils: removal of xenstore-utils makes files
disappear from xen-utils-common"):
> > The installation sequence to reproduce this problem is
> >
> > apt-get install xen-utils-common/stretch
> > # (1)
> > apt-get
ven in stretch). You could in theory upgrade only
xenstore-utils and then downgrade it again, to make the files
disappear, but I don't think that is supported. And in practice
no-one would do that.
So I don't think this is a bug we care about.
Ian.
--
Ian JacksonThese opinions are my o
Josh Triplett writes ("Bug#904248: Beginnings of a patch to add netbase to
build-essential"):
> On Mon, 15 Oct 2018 13:39:32 +0100 Ian Jackson
> wrote:
> > My proposed wording about "longstanding and conventionally available
> > service and protocol names and nu
and numbers" says that if the admin has
modified the file they need to make sure their modified version isn't
toally borked.
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.
extend* rather than *specify* the
flake8 ignore list. I found that it is possible to fish the existing
list out of the relevant python module, but I didn't know how to write
such a programmatic thing in setup.cfg.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an
with the FTP Masters if so desired.
I thought the bug that ed was not in the default install had been
fixed. I agree that it ought to be in all but the most minimal
installations.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that
Guido Günther writes ("Re: Bug#910446: NMU diff (substantive patches in
git-format-patch form)"):
> On Sun, Oct 14, 2018 at 03:36:49PM +0100, Ian Jackson wrote:
> > Hi. I fixed this bug, and some other FTBFS, and am about to upload
> > the result. I'm doing this my
is not too tiresome. I left them as the 11 separate
commits as I thought that would be more convenient.
Regards,
Ian.
>From d20c8b1efd7198af5be7836c9777c5982dd117b1 Mon Sep 17 00:00:00 2001
From: Ian Jackson
Date: Sun, 14 Oct 2018 13:34:04 +0100
Subject: [PATCH 01/20] .gitignore: Fetch from
bad idea, it's that it's
not comprehensive enough.
I suggest that instead of abandoning it, we should bump the lintian
message to a warning.
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.
Guillem Jover writes ("Re: Bug#910737: dpkg-source -b /path/to/somewhere should
not delete somewhere.orig"):
> Well, this is the documented behavior for source format 1.0 (it does
> not apply to newer source formats) which has acted like this since its
> introduction in dpkg 1.3.0:
>
>
>
Sean Whitton writes ("Bug#910705: Bug#910687: dgit: build-source and
push-source disregard -wc"):
> I'm pretty sure this is a straightforward bug -- unless --ignore-dirty
> or --include-dirty is specified, push-source and build-source are meant
> to error out if the tree is dirty.
There are
Ian Jackson writes ("Re: Bug#910687: dgit: build-source and push-source
disregard -wc"):
> I think in fact that this needs to be more general. For example, with
> --clean=dpkg-source: if dpkg-source leaves untracked files, this
> should be detected. I think this check sho
binary-package-in-preparation permissions (which need to be those
intended for the output package).
Does that make sense ?
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.
asily cherry-pick
> what to extract...
It could search the tree for bad links after extraction but before
exiting status 0.
Or we could request that tar grow an option like rsync's --safe-links.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evad
Mattia Rizzolo writes ("Bug#910740: dgit: please enable make --include-dirty
work with --build-products-dir"):
> Package: dgit
> Version: 7.1
> Severity: wishlist
> Control: block -1 by 910737 865426
>
> As requested in Bug#910725 ("something eats ../foo_1.2.3.orig.tar.gz")
> I'm opening this
cannot access '../mason.orig': No such file or directory
zealot:bpd>
--
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.
or --include-dirty
--build-products-dir to work, blocked by (a).
Regards,
Ian.
commit 7e5b054e22287250c05d43501d40b163ef3fec69
Author: Ian Jackson
Date: Wed Oct 10 13:40:46 2018 +0100
dgit: Forbid source building with --include-dirty non-.. bpd
Right now, this does bizar
Mattia Rizzolo writes ("Bug#910687: dgit: crash with perl backtrace"):
> On Wed, Oct 10, 2018 at 11:51:24AM +0100, Ian Jackson wrote:
> > That seems coherent. Unless you think --include-dirty should turn
> > --clean=check into --clean=none ? That seems unwise.
>
&
Mattia Rizzolo writes ("Bug#910725: dgit: something eats
../foo_1.2.3.orig.tar.gz"):
> It's just a rendomly named directory. I like to keep a directory named
> the same as the package it is going to contain. So:
> ~/devel/debian/QA/mason ← random directory. I usually mkdir that
>
Mattia Rizzolo writes ("Re: Bug#910687: dgit: build-source and push-source
disregard -wc"):
> On Wed, Oct 10, 2018 at 11:34:40AM +0100, Ian Jackson wrote:
> > You never made a commit like that. The dgit import isn't because it
> > doesn't have debian/patches because it w
Mattia Rizzolo writes ("Bug#910725: dgit: something eats
../foo_1.2.3.orig.tar.gz"):
> Package: dgit
> Version: 7.10
> Severity: important
Hi. I will investigate this later. In the meantime,
> mattia@warren ~/devel/debian/QA/mason % ls
> mason mason_1.0.0-12.3.diff.gz mason_1.0.0-12.3.dsc
Mattia Rizzolo writes ("Re: Bug#910687: dgit: crash with perl backtrace"):
> On Tue, Oct 09, 2018 at 11:44:34PM +0100, Ian Jackson wrote:
> > I think this diff will fix it. You can apply it directly with patch
> > to dgit in your /usr/bin if you like.
>
> Ri
magic to include the untracked files in
> whatever dgit is going to do
I think that should already work.
Anyway, thanks for exploring all this with me.
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.
Control: clone -1 -2
Control: retitle -2 build-source and push-source disregard -wc
Control: tags -2 - patch
Control: severity -2 normal
Mattia Rizzolo writes ("Bug#910687: dgit: crash with perl backtrace"):
> I'm now already falling asleep, I'll try to apply your patch tomorrow and
> report back
Control: tags -1 + patch
Mattia Rizzolo writes ("Bug#910687: dgit: crash with perl backtrace"):
> Package: dgit
> Version: 7.0
> Severity: important
Sorry about this.
I think this diff will fix it. You can apply it directly with patch
to dgit in your /usr/bin if you like.
I will make a
hly what they do right now.
The support for configuration in something like policy-rc.d has a few
design decisions to be made but doesn't seem really difficult. Also
nothing blocks on it. The TC would simply be saying "this would be a
good thing to have".
Ian.
--
Ian JacksonThese
hey would say `apt source'. Hence the
desire to fix #790093.)
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.
it is wrong for your
downstreams and users. We should be discouraging such tradeoffs.
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 ("No TOFU for git server host key"):
> I think now would be a good time to look at #790093 again. Would
> anyone from the DSA team with the requisite TLS knowledge be available
> to get together with me to sketch out a solution ?
Ping ?
I think we are nea
Control: tags -1 + moreinfo
Ian Jackson writes ("Re: Bug#906317: dgit: consider demoting git-buildpackage
to recommends"):
> So I'm inclined to think that the subset of dgit's functionality which
> is useable without gbp pq is too small for your use case (and too
> small
Sean Whitton writes ("Bug#905433: git-debrebase: debrebase new-upstream fails
with "uninitialized value""):
> On Sun 19 Aug 2018 at 08:51PM +0100, Ian Jackson wrote:
> > I think
> > convert-from-unpatched-upstream-source
> > convert-from-unp
Adrian Bunk writes ("Bug#904302: Whether vendor-specific patch series should be
permitted in the archive"):
> On Thu, Oct 04, 2018 at 08:21:07PM +0200, Philip Hands wrote:
> > IMO policy should recomend the use of separate source packages as the
> > prefered solution to the problem that
Philip Hands writes ("Re: Bug#904302: Whether vendor-specific patch series
should be permitted in the archive"):
> IMO policy should recomend the use of separate source packages as the
> prefered solution to the problem that vendor-specific patch series were
> supposed to address.
That would be
Adrian Bunk writes ("Bug#904302: Whether vendor-specific patch series should be
permitted in the archive"):
> On Wed, Sep 19, 2018 at 02:39:23PM +0200, Philip Hands wrote:
> > The Committee therefore resolves that:
> >
> > 1. Any use of dpkg's vendor-specific patch series feature is a bug
t someone would disingenuously argue that a
series.ubuntu file, in a package in Debian, is not "use" of the
feature.
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 dgit cannot handle git-debrebase ENOENT
Felipe Sateler writes ("Bug#910221: dgit: missing dependency on git-debrebase
for sbuild"):
> dgit cannot do sbuild without git-debrebase:
>
> % dgit sbuild
> Format `3.0 (quilt)', need to check/update patch stack
> dgit: failed
I have signed the new tag
> debian/1.4.4-2.
Done, 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.
Anonymous writes ("Bug#904302: That's a free software issue!"):
> If Debian want patches it has to support this process with tools. The
> attitude Debian owns all source packages is wrong. Sharing source
> packages among different vendors is more efficient. Different patch
> series may be the best
fix is in the upstream 4.11 branch.
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.
k at these failures since they are blocking my
package refactoring work and I expect that as an output I will produce
a list of upstream commits to cherry pick, which I will send to this
bug.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk,
c:308:5: error: 'strncpy' specified bound 16 equals destination size
[-Werror=stringop-truncation]
strncpy(scaling_governor, govname, CPUFREQ_NAME_LEN);
^~~~
cc1: all warnings being treated as errors
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 ("Re: want dgit smash-working-tree-timestamps [and 1 more
messages]"):
> Certainly it's a workaround. My goal is to make it easy for people
> who want to modify the way their systems work, to work around bugs
> they find in Debian.
>
> Certainly no
and the update failed
because it said the version was wrong.
touch debian/control "fixed" 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.
Martín Ferrari writes ("Re: Should the weboob package stay in Debian?"):
> I am writing on behalf of the Anti-Harassment team, as our input has
> been requested on this issue.
Thanks for your considered and helpful response.
>our recommendation would be to either work with
> upstream on
Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> On 2018-09-25 14:22:44, Ian Jackson wrote:
> > If you can't get a better idea I would suggest
> > << 0.242+git20151019-1.1~
> > which is all versions until the next draft
Ian Jackson writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia
> namespace"):
> > On 2018-09-25 14:22:44, Ian Jackson wrote:
> > > If you can't get a better idea I would
Iain Learmonth writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> On 25/09/18 14:16, Antoine Beaupré wrote:
> > ... but it hasn't been migrated to Salsa. Would you be okay to move this
> > in the Python module's team umbrella (as opposed to simply collab-maint)?
>
> The whole
Antoine Beaupré writes ("Re: possible conflict over the /usr/bin/ia namespace"):
> Makes sense. How about:
>
> Conflicts: python-duckduckgo2 (<= 0.242+git20151019-1)
>
> This way we assume any newer upload of the package will remove ia?
That's not a good choice because it excludes (local)
duckduckgo2 is changed there there
should probably be a bug against python-duckduckgo2. I guess that bug
doesn't need to be rc ?
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.
Mike Gabriel writes ("Re: Bug#909192: mate-desktop-environment: Installing
sysvinit-core removes mate-desktop-environment"):
> many thanks for all this background info. I might have a potential
> contract to get this solved in the loop, so, I may probably return to
> it soon (or not so soon).
Ian Jackson writes ("mate-desktop-environment: Installing sysvinit-core removes
mate-desktop-environment"):
> Long term, systemd-shim is undesirable.
See also #905388, which is about `elogind', a fork of systemd-logind,
which might be easier to maintain.
Ian.
--
Ian JacksonT
logged in on the console can do certaain things.
An alternative approach that would probably satisfy sysvinit users
would be to simply add, as a matter of configuration, appropriate
users to a Unix group with equivalent power.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed yo
Ian Jackson writes ("Re: Bug#908933: debian-policy: typo in document in section
3.4 page no 15 line number 16 needs improvement."):
> However, I looked at
> /usr/share/doc/debian-policy/policy.pdf.gz
> from debian-policy_4.2.1.1_all.deb with mupdf on my stretch i386
>
ly fine. See attached policy-ok.png.
I also looked at it in xpdf on stretch. I even looked in evince,
although I find it maddening. It all seems fine.
I notice that the screenshot is from Adobe Reader.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you fro
Philip Hands writes ("Bug#904302: Whether vendor-specific patch series should
be permitted in the archive"):
> Possibly also with something like this?:
>
> Post-Buster this should be implemented in Debian Policy by
> declaring that a package MUST NOT contain a non-default series
>
Stuart Prescott writes ("Bug#904558: What should happen when maintscripts fail
to restart a service"):
> Ian Jackson wrote:
> > When I wrote that, it didn't occur to me that anyone would think that
> > a failure by a postinst script to perform an intended operation
Tollef Fog Heen writes ("Bug#904558: What should happen when maintscripts fail
to restart a service"):
> Ian Jackson:
> > There may be good reasons not to treat daemon startup failure as a
> > postinst failure, but the argument above is not one of them.
>
> I thin
George Taylor writes ("Re: Bug#909118: /proc not mounted before use"):
> On 18/09/2018, Ian Jackson wrote:
> > Thanks. Have you tried this on a system _with_ a Debian-generated
> > initramfs ?
>
> Yes, on a Debian 9 VM. When using initramfs /proc/stat exists a
Control: tags -1 patch
George Taylor writes ("Bug#909118: /proc not mounted before use"):
> I suggest replacing elif with a simple else.
Thanks. Have you tried this on a system _with_ a Debian-generated
initramfs ?
Ian.
--
Ian JacksonThese opinions are my own.
If I ema
herwise, I don't see any benefit
> from postinst (particularly postinst + configure) ever failing.
Frankly I'm disturbed to be reading this, here. See above.
If the postinst fails, then the user has the opportunity to fix the
root cause and rerun dpkg-source --configure --pending. That will
then
Mattia Rizzolo writes ("Re: want dgit smash-working-tree-timestamps [and 1 more
messages]"):
> On Sat, Sep 15, 2018 at 09:00:26AM -0700, Sean Whitton wrote:
> > I guess that experience using the script to avoid FTBFS will reveal
> > whether this behaviour needs to be tweaked; we probably
ns the generator and fails if the output is
not identical to the current file. So not updating the test list is
itself a test failure.
I commit the resulting d/t/control to git. This is slightly ugly but
not a practical problem. In particular, any merge conflicts are
easily resolved by rerunni
he maintainer's debian/source/options and the implied
tar-ignore.
> I think both options, never-add-tar-ignore-defaults-even-if-specified
> and clear-all-tar-ignore are valid, and I might add both, just wanted
> to make sure I understand which one you are requesting here.
So I think I want
Julian Andres Klode writes ("Re: Bug#908747: Default -I and -i option should
not exclude .ignore"):
> On Thu, Sep 13, 2018 at 12:26:27PM +0100, Ian Jackson wrote:
> > The result of this default is that many source packages in the Debian
> > archive are incomplete. [...
For a throwaway source package I think you don't care if it has a .git
directory and your whole revision history ?
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.
Ian Jackson writes ("Re: Bug#908417: dgit does not handle debian/.gitignore
missing from source package"):
> I will file a bug against dpkg requesting a command line option which
> resets the tar-ignore list.
I've just filed
#908742 Want way to reset tar-ignore list
&g
not):
.shelf
_MTN
_darcs
{arch}
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.
and
everything would work right.
So, please could you provide such an 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.
l wrongly lack debian/.gitignore.
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.
gregor herrmann writes ("Re: Bug#908323: gtk+3.0 breaks libgtk3-perl
autopkgtest"):
> I was wondering if we should just add a build-dependency and
> dependency on gir1.2-gdkpixbuf-2.0, like we do for other
> gir*-packages, now that we need to use it explicitly since some
> definitions have been
rs and depending on gdk-pixbuf (and probably
others 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.
likely there is no UTF-8 encoder either.
It would probably be easier and more fruitful to add the wanted
features (or UI frills) from eterm to another terminal emulator.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a
review from someone of my proposed messages.
> You also do not appear to have looped AH in on this, despite them being
> almost-certainly having some kind of viewpoint and de facto weight,
> if not a de jure one.
Did you overlook this email ?
From: Ian Jackson
To: lea...@debian.org
CC: a
8f618
> Repo: https://git.notmuchmail.org/git/notmuch
>
> If you look at branch release, you can see the dgit created merge after
> that commit, and before the actual archive tag.
Thanks. I will look at this.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you fro
Ian Jackson writes ("Re: Bug#908417: dgit does not handle debian/.gitignore
missing from source package"):
> I'm sorry to be dim, but I don't understand what you think the bug in
> dgit is ? dgit's design principle is that the source package and git
> tree are idnntica
David Bremner writes ("Bug#908417: dgit does not handle debian/.gitignore
missing from source package"):
> Package: dgit
> Version: 6.11
> Severity: normal
>
> notmuch had until recently "tar-ignore" in debian/source/options so
> that a default set of VCS related things is dropped from the
would not want to try
to decide this on a supermajority.
> Note: Personally, I would very much prefer that upstream accepted
> https://git.weboob.org/weboob/devel/issues/154 and removed the remaining
> insults (if any), so we could put all of this behind us.
That would indeed be great.
ange to Policy about this.
Maybe adding a link or xref to policy 5.6.12.1 would be helpful.
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.
not able to
deal individually with every bug report, are "slacking" in their
"duty", quite objectionable, I'm afraid.
> Ian Jackson ,
> > What did you think of the text I proposed just over <- there, that
> > Moritz was happy with ?
>
> Just answering becaus
riate documentation, by (scaleable) outreach activities, and so
on.
What did you think of the text I proposed just over <- there, that
Moritz was happy with ?
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a pri
701 - 800 of 3545 matches
Mail list logo
