Bug#920469: lintian: "internal error: Cannot add another buildinfo file" after mergechanges

Package: lintian Version: 2.5.124 Severity: normal Steps to reproduce: * Have a source package producing a mixture of architecture-specific and architecture-independent packages (I used xdg-desktop-portal) * Run sbuild twice to produce _amd64 and _all packages, separately * mergechanges

Bug#920299: lintian: warning for dh_runit usage

[2019-01-23 23:56] Chris Lamb > part text/plain 418 > tags 920299 + moreinfo > thanks > > Dmitry, > > > please add warning for packages, that use dh_runit(1) debhelper (file > > debian/.runit exists), but do not have Breaks: ${runit:Breaks}. > > Please elaborate why a

Could you tell me more about your organization?

Happy Friday,  I hope this email finds you well! I am researching non-profit organizations to learn about their fundraising efforts and your organization really caught my attention. Would you be the right person to connect with regarding your online fundraising tools? Thank you for the

lintian_2.5.124_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 24 Jan 2019 23:47:53 +0100 Source: lintian Binary: lintian Architecture: source all Version: 2.5.124 Distribution: unstable Urgency: medium Maintainer: Debian Lintian Maintainers Changed-By: Chris Lamb

Bug#920228: marked as done (lintian: Should locate/parse .buildinfo file if mentioned in .changes)

Your message dated Fri, 25 Jan 2019 09:06:07 + with message-id and subject line Bug#920228: fixed in lintian 2.5.124 has caused the Debian Bug report #920228, regarding lintian: Should locate/parse .buildinfo file if mentioned in .changes to be marked as done. This means that you claim that

Bug#920184: marked as done (lintian: incorrectly parses empty changelog signature line as an NMU)

Your message dated Fri, 25 Jan 2019 09:06:07 + with message-id and subject line Bug#920184: fixed in lintian 2.5.124 has caused the Debian Bug report #920184, regarding lintian: incorrectly parses empty changelog signature line as an NMU to be marked as done. This means that you claim that

Bug#920376: marked as done (lintian: Add a check for binaries using obsolete DES encryption)

Your message dated Fri, 25 Jan 2019 09:06:07 + with message-id and subject line Bug#920376: fixed in lintian 2.5.124 has caused the Debian Bug report #920376, regarding lintian: Add a check for binaries using obsolete DES encryption to be marked as done. This means that you claim that the

Processing of lintian_2.5.124_amd64.changes

lintian_2.5.124_amd64.changes uploaded successfully to localhost along with the files: lintian_2.5.124.dsc lintian_2.5.124.tar.xz lintian_2.5.124_all.deb lintian_2.5.124_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

[Git][lintian/lintian] Pushed new tag 2.5.124

Chris Lamb pushed new tag 2.5.124 at lintian / lintian -- View it on GitLab: https://salsa.debian.org/lintian/lintian/tree/2.5.124 You're receiving this email because of your account on salsa.debian.org.

[Git][lintian/lintian][master] 9 commits: Declare new lintian test suite 'tags'; undefine all others.

Chris Lamb pushed to branch master at lintian / lintian Commits: 09965279 by Felix Lechner at 2019-01-25T08:20:21Z Declare new lintian test suite tags; undefine all others. In the future, all tests checking Lintians tag functionality belong to suite tags. Undefine the other suites for tests,