OK, this one
is meant for Planet Debian...
One of many, many changes in the latest lintian is vendor profiles and, thanks to a heads-up by
Niels Thykier, Emdebian will have working profile support in the next upload of emdebian-grip. (The only reason it's not already in Debian is my own fault for not uploading when I thought I had the time to upload.)
$ lintian --profile emdebian-grip drivel_3.0.2-1em1_amd64.deb
$ lintian --profile debian drivel_3.0.2-1em1_amd64.deb
E: drivel: debian-changelog-file-missing
E: drivel: copyright-file-compressed
W: drivel: copyright-without-copyright-notice
E: drivel: description-contains-invalid-control-statement
W: drivel: binary-without-manpage usr/bin/drivel
So the em1 version implements
Emdebian Policy for
Emdebian Grip. Clean for Emdebian Grip, just as the Debian package is clean prior to the changes.
I expect this to dramatically improve the processing of Emdebian packages, both for Grip and for the cross-built flavour, Crush, once that actually starts up.
Thanks to the lintian team for this support. Now if there was some way of backporting this version of lintian to Squeeze, I could also use this at work to suppress really annoying lintian warnings about non-standard suite names. (The whole point of using a non-standard suite name is to keep our stuff separate from the normal Debian/Emdebian stuff for licensing reasons etc.)
Update: of course, I didn't check the PTS for lintian before writing that, so hence didn't notice that the backport already exists! Thanks again to Niels for the prompt. I've now got another package to create for work.
Update2: Thanks to Joerg Jaspert for the tip that all lintian versions get backported directly from unstable as an exception on ~bpo. The work package is ready, so this is going to make things a lot easier when building stuff on stable.
In other news, the same version of emdebian-grip will include support for
integrating Emdebian Grip into Debian itself. This too will use vendor-specific support, this time an internal vendor name which just needs to work on the "buildd".
(It's not quite a buildd, Emdebian Grip doesn't build anything, it's all post-processing. It's just that the processing of Debian packages for Emdebian Grip will look a bit like having a second buildd working on the packages uploaded by the existing buildd. The process itself is still developing...)