On Sun, May 31, 2026 at 06:39:18PM -0600, Matthew Turner wrote:
I am fairly new to this so bear with me. I am updating from the previous version (3.3.2-3) and kept the configuration consistent. Now, I realize that this is not an excuse to leave lintian warnings alone, but I also don't necessarily expect to resolve everything on the immediate version.
Sure, but I'm talking about ones that are specific to your upload.
That being said, the warnings and errors that I see locally (debuild -us -uc) are E: libapache2-mod-authnz-external changes: bad-distribution-in-changes-file unstable W: libapache2-mod-authnz-external source: newer-standards-version 4.7.3 (current is 4.6.2) W: libapache2-mod-authnz-external source: obsolete-url-in-packaging http://code.google.com/p/mod-auth-external/downloads/list?can=1 [debian/watch] The first, "unstable", is expected since I understand I am to upload it as such before it gets officially published.
No, it's not expected. It's one of the many warnings tat you have because you are building this package on Ubuntu and running lintian on Ubuntu. I also assume you aren't building it in a clean chroot either and aren't testing it on Debian at all.
Concerning the mentors.debain.net issues, these are more difficult for me to understand why they are different than my local system. I am especially confused as to why debuild and the consistent configuration would give a malformed archive. What would be the best way to resolve this?
The best way to resolve this would be building your package on Debian unstable, as expected for packages that are going to be uploaded to Debian unstable.
For the NMU warning, I thought that since I am adopting this, that all I needed was to include my name as the maintainer; am I also supposed to have something special in the changelog?
You are supposed to read the lintian tag descriptions, not just guess the solutions based on the tag names. The second paragraph of the description describes your problem.
-- WBR, wRAR
signature.asc
Description: PGP signature
