Quoting Jakub Wilk (jw...@debian.org):
> (I'm not the maintainer.)
> 
> Hi Christian. I saw your NMU in deferred. Unfortunately there are
> some problems with it:
> 
> - The NMU diff hasn't been sent to BTS. (Or maybe I can't find it.
> You wrote you'll send it on April 10...)

Has been indeed sent in the bug report where I was originally working
(an l10n update)

> 
> - You changed source format from 1.0 to 3.0 (quilt). I don't believe
> that such a change is suitable for an NMU.

Well, that's debatable. As the package currently includes several
upstream changes in the Debian diff, adding one more change to that
pile just makes it bigger. So my view is that switching to source v3
makes at least the new patch easier to identify in the future.

> 
> - As far as I can see, you fixed #650582, but didn't close the bug
> in the changelog.
> 
> - Apparently the package wasn't built in a clean environment: the
> binary package depends on libpng15-15, which exists only in
> experimental so far.


Oh, that's correct. My sid chroot has a leftover from another build
where I was needing experimental packages.

Maybe, by the way, this is what caused the FTBFS.

I rebuilt the NMU in a cleaner environment. And, indeed, the patch is
no longer needed, so the FTBFS was itself caused by the build
environment using packages from experimental.

So, my new NMU is now again an l10n-only NMU.





Attachment: signature.asc
Description: Digital signature

Reply via email to