[Pkg-privacy-maintainers] Bug#849727: Adopting seahorse-nautilus?

u u at 451f.org
Sun Mar 19 17:19:00 UTC 2017

Hi Carlos,

any news about this?


> Hi,
> (Carlos, are you subscribed to the list? If so I'll stop Cc'ing you.
> If not, well, you should :)
> u:
>> I've created the corresponding Git repository and Carlos has imported
>> his changes in there. I've reviewed the packaging and Carlos did a lot
>> of great work there. I can confirm that everything builds fine.
> Great :)
>> There are some new patches for which I have not enough technical
>> expertise in order to evaluate them, so this should be done by somebody
>> else.
> I can do that once their Origin field documents where they come from,
> and they are all forwarded upstream (or documented why it's not
> relevant for upstream).
>> In the patches, I think we could have some more specific information
>> about what "more recent versions" is supposed to mean:
>> In debian/patches/update-Makefile-am.patch
>> " This allows the Makefile.am files to work with more recent versions of
>>   automake without warnings."
> Yes, please.
>> There is a false positive in older versions of lintian reporting "E
>> missing-build-dependency-for-dh_-command":
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835449
>> And here are some other errors I get, but I'm unsure if this is because
>> I use Jessie's lintian.
> (Hint: a newer one is in jessie-backports, and quite often the version
> from testing/sid works just fine on stable.)
>> $ lintian --pedantic seahorse-nautilus_3.11.92-2_amd64.changes
>> E: seahorse-nautilus-dbgsym: extended-description-is-empty
>> W: seahorse-nautilus-dbgsym: debug-package-should-be-named-dbg
>> usr/lib/debug/.build-id/
> I confirm those are issues with the old Lintian, can't reproduce on sid.
>> Could you take this over from here, intrigeri?
> Sure. I've sent this back to Carlos' plate (see above
> comments) though.
> Cheers!

More information about the Pkg-privacy-maintainers mailing list