[pkg-bacula-devel] Incomplete upload found in Debian upload queue
bart at timedout.org
Fri Jun 22 15:43:59 UTC 2012
Thanks for reply. All advice is much appreciated.
First, few in-line answers:
On 22 June 2012 11:43, Luca Capello <luca at pca.it> wrote:
> Please do not Cc: me, I read the list.
I did not CC you, I actually sent the email to you (To: luca…) and
CCed the list. This way, MUA or better web clients (like Gmail) can
mark the message as important as it’s directed to you. Quite a lot of
mailing lists allows this kind of practice, but since you’ve been here
quite a while I take it’s not welcomed here. I’ll change that :-).
> Thank you for an apt-get repository, two notes:
> 1) the Release file is not signed
Thanks, I’ve fixed that :-).
> 2) you should not use official Debian distribution names in your
> repository setup, because someone using your packages without pay
> attention will (automatically) get updates from them. Use "fake"
> names instead, like bart-$OFFICIALNAME, and aliases (the package will
> be the same (thus with an official name)
Yeah, makes sense. I’ll get that changed, as well.
> PS, I hope you are not getting my remark as negative points, actually it
> is the other way around: thank you for stepping up and helping the
> pkg-bacula team!
Not at all. I’m quite new to Debian official processes and rules,
even though I’ve been building packages for my private repos for quite
a while (few years actually!). I’ll appreciate any tips or pointers.
I’ve made the changes and created branch on Alioth as well as tagged
5.2.6+dfsg-1~bpo60+1. Packages I’ve built from that tag are working
like a charm on all of my 12 servers (in next few months I’ll be
rolling out Bacula in my work place where there’s 200+ machines
that’ll be backed up).
I guess if you manage to fix that aforementioned bug, I’ll just merge
that commit with squeeze-backports branch, tag it again, test and
it’ll be ready for backports.d.o as soon as it reaches testing.
More information about the pkg-bacula-devel