Rob Browning writes:
> Sounds reasonable -- any chance y'all are going to have someone who
> might know handy at debconf?
Oh, and if you do happen to chat with anyone dpkg-related, as an
alternative, it might be handy if we had a tool (dpkg or other) that
could properly sort a list of packages i
Sean Whitton writes:
> Thanks. When David and I talked about it, we thought that we shouldn't
> rely on ordering that's not guaranteed by the triggers spec -- though
> possibly the spec has fallen out-of-date with the implementation.
Sounds reasonable -- any chance y'all are going to have someo
dh-elpa_2.1.3_source.changes uploaded successfully to localhost
along with the files:
dh-elpa_2.1.3.dsc
dh-elpa_2.1.3.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Wed, 24 Jul 2024 02:24:21 +
with message-id
and subject line Bug#973393: fixed in dh-elpa 2.1.3
has caused the Debian Bug report #973393,
regarding truncate less of the backtrace during failing ert tests
to be marked as done.
This means that you claim that the problem has b
Your message dated Wed, 24 Jul 2024 02:24:21 +
with message-id
and subject line Bug#1069326: fixed in dh-elpa 2.1.3
has caused the Debian Bug report #1069326,
regarding dh-elpa: Don't rename files under test directories during autopkgtest
by default
to be marked as done.
This means that you
Your message dated Wed, 24 Jul 2024 02:24:21 +
with message-id
and subject line Bug#1069210: fixed in dh-elpa 2.1.3
has caused the Debian Bug report #1069210,
regarding dh-elpa: Support nested directory in elpa installation
to be marked as done.
This means that you claim that the problem has
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 24 Jul 2024 11:20:49 +0900
Source: dh-elpa
Architecture: source
Version: 2.1.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team
Changed-By: Sean Wh
Hello,
On Tue 23 Jul 2024 at 08:18pm -05, Rob Browning wrote:
> Sean Whitton writes:
>
>> We noticed that the triggers spec[0] says "It is not defined in what
>> order triggers will run." We think this may invalidate your current
>> approach. Or did you already see this and account for it?
>
>
Sean Whitton writes:
> We noticed that the triggers spec[0] says "It is not defined in what
> order triggers will run." We think this may invalidate your current
> approach. Or did you already see this and account for it?
I'll have to refresh, but from what I recall offhand, that might be a
pr
9 matches
Mail list logo
