Re: Processing of kfreebsd-10...
- To: "firstname.lastname@example.org" <email@example.com>
- Subject: Re: Processing of kfreebsd-10...
- From: Steven Chamberlain <firstname.lastname@example.org>
- Date: Wed, 28 Jan 2015 21:51:13 +0000
- Message-id: <[🔎] 54C959D1.email@example.com>
- In-reply-to: <firstname.lastname@example.org>
- References: <E1YGGoD-0008LP-W8@franck.debian.org> <20150128005125.GI3901@squeeze.pyro.eu.org> <email@example.com> <20150128133925.GA6450@squeeze.pyro.eu.org> <firstname.lastname@example.org> <email@example.com>
On 28/01/15 17:42, Christoph Egger wrote:
> I see you're having fun with dak ;-)
Sorry for all this noise on debian-bsd@...
> Anyway your *_multi.changes might have been the right thing if uploaded
> after the *_source.changes had been thrown away .. ow the _source stole
> some of the files.
Yeah, things didn't happen in quite the expected order.
A similar thing happened again, where the *_multi.changes was still
being retained somewhere (it was gone from
ftp://ftp.eu.upload.debian.org/pub/UploadQueue/ so I assumed it had been
rejected already; that was actually still being retried, and repeatedly
deleting files meant for a later upload attempt).
> Anyway if you're building your upload on a jessie system probably the
> best way is to use `dpkg-buildpackage -g` -- that's how I did the kernel
> builds -- it gets you a single changes with all that is needed
Thanks, I did find that, which is the *_kfreebsd-amd64.changes, which
may actually succeed this time.
(It doesn't help that there's a long delay between actions happening and
then the notification email.)