Processing of dh-elpa_2.1.2_source.changes

dh-elpa_2.1.2_source.changes uploaded successfully to localhost along with the files: dh-elpa_2.1.2.dsc dh-elpa_2.1.2.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#973393: marked as done (truncate less of the backtrace during failing ert tests)

Your message dated Fri, 12 Jul 2024 06:19:36 + with message-id and subject line Bug#973393: fixed in dh-elpa 2.1.2 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

Bug#1069210: marked as done (dh-elpa: Support nested directory in elpa installation)

Your message dated Fri, 12 Jul 2024 06:19:36 + with message-id and subject line Bug#1069210: fixed in dh-elpa 2.1.2 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

Bug#1069326: marked as done (dh-elpa: Don't rename files under test directories during autopkgtest by default)

Your message dated Fri, 12 Jul 2024 06:19:37 + with message-id and subject line Bug#1069326: fixed in dh-elpa 2.1.2 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

dh-elpa_2.1.2_source.changes ACCEPTED into experimental

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Jul 2024 14:03:04 +0800 Source: dh-elpa Architecture: source Version: 2.1.2 Distribution: experimental Urgency: medium Maintainer: Debian Emacsen team Changed-By: Sea

Re: org-roam_2.2.2-2_source.changes ACCEPTED into unstable

Hello, On Thu 11 Jul 2024 at 03:14pm +02, Aymeric Agon-Rambosson wrote: > Hi, > > Le jeudi 11 juillet 2024 à 08:09, Sean Whitton a > écrit : > >> If you were going to make complex edits you would always fix it in the >> .org and regenerate the .texi, right? > > That would indeed be my own prefer

Bug#1076116: marked as done (org-roam: restore rebuilding org-roam.texi)

Your message dated Thu, 11 Jul 2024 14:49:53 + with message-id and subject line Bug#1076116: fixed in org-roam 2.2.2-3 has caused the Debian Bug report #1076116, regarding org-roam: restore rebuilding org-roam.texi to be marked as done. This means that you claim that the problem has been deal

org-roam_2.2.2-3_source.changes ACCEPTED into unstable

Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 11 Jul 2024 16:06:23 +0200 Source: org-roam Architecture: source Version: 2.2.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Emacsen team Changed-By: Ayme

Processing of org-roam_2.2.2-3_source.changes

org-roam_2.2.2-3_source.changes uploaded successfully to localhost along with the files: org-roam_2.2.2-3.dsc org-roam_2.2.2-3.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Re: org-roam_2.2.2-2_source.changes ACCEPTED into unstable

Hi, Le jeudi 11 juillet 2024 à 08:09, Sean Whitton a écrit : If you were going to make complex edits you would always fix it in the .org and regenerate the .texi, right? That would indeed be my own preference, yes. I just did not think that I could deduce from it that it was upstream