On Tue, 03 Jan 2012, Kay Hayen wrote:
> >* custom get-orig-source rule in debian/rules -- most popular way to
> > automate things of this kind ;)
> That's just where to put it, not what to put there?
yeap... "what" could indeed be either a call to dh_wraporig or just a
tandem of two tar commands (one to extract, another one to compress
again with a set of --exclude options).
N.B. I am somewhat surprised that tar itself doesn't have an option
to filter a tar archive applying --exclude to a stream from STDIO
> Yeah yeah. :-)
> I had installed the "pbuilder" stuff and things, but honestly,
> normally I don't see much point, once it will be working again.
> Mostly because the binary package contains no binaries and the tame
> dependencies.
;-) you would be surprised ... there is dozen of reasons not to
mention that some (e.g. me) make it a requirement for sponsored
uploads... here is few:
- since upload happens to debian sid (AKA unstable) it might have newer
versions that what you have on your system, thus building in an
up-to-date sid chroot would be beneficial to spot fresh
incompatibilities/problems earlier than later
- building in a clean environment also provides better
assurance that package would build for anyone trying to build it later
on
> And I even predicted it, but couldn't fix it anymore. I knew it was
> flawed, but "mentors.debian.net" won't let me upload any "-2" ever,
> presumably due to the changed "orig" source.
yeap -- .orig for a given "upstream" version, once uploaded must
not change ;-), thus shouldn't even be uploaded in general for -2, -3,
... debian revisions.
--
=------------------------------------------------------------------=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120102235824.gs16...@onerussian.com
