[pkg-bacula-devel] Incomplete upload found in Debian upload queue
luca at pca.it
Fri Jun 22 10:43:40 UTC 2012
Please do not Cc: me, I read the list.
On Fri, 22 Jun 2012 11:40:52 +0200, Bart Swedrowski wrote:
> On 22 June 2012 08:26, Luca Capello <luca at pca.it> wrote:
>> Could you push all your changes to the Git repository in a
>> squeeze-backports branch, please?
> Will do, as soon as I put those packages through some testing and make
> sure they’re working fine.
Ideally, you push before "announcing" your packages in the wild ;-)
> BTW I have couple of questions about that:
> 1). Is squeeze-backports branch name going to be okay or would you
> rather have squeeze-backports-bart or something like this (I did
> notice lenny-backports-alfie branch there).
IMHO squeeze-backports is better than squeeze-backports-$MAINTAINER,
given that MAINTAINER can change over time, while the branch does not.
> 2). Is that git repo publicly commitable? I didn’t try just yet
> but just wanted to check whether I’ll be able to push changes right
> away or do I need to do something special before hand (or you need to
> add me somewhere).
You need to be part of the pkg-bacula group on Alioth. Basically, you
create an Alioth login  and then request to be added to that group:
 non-official Debian Project Members automatically get the -guest
suffix and usually your login is the Debian login you would like to
get, choose carefully testing with `finger $LOGIN at db.debian.org` ;-)
> 3). I did read that you usually back port packages, they should be
> in testing; bacula atm is in sid. Do you think that’s going to be a
> major show-stopper?
It is, sorry. Nevertheless, 5.2.6+dfsg-$VERSION will migrate to
testing, given that it was uploaded before the 19:52 dinstall of
I still had not time yet to look at #677700, I will do over the week-end
if no one replies before: I suspect the reason for this is the
(uncoordinated) MySQL-5.5 transition. This is actually the only reason
I see ATM why 5.2.6+dfsg-1 can not migrate to testing:
>> BTW, I found strange that you could get so far with the upload, given
>> that I could not find your key in any of the Debian keyrings. Feel free
>> to ask if you need a sponsor, but please read beforehand:
> Yeah, I found that a bit strange as well; I wasn’t expecting to be
> able to upload anything but after that I was able to FTP to that
> machine without any problem as anonymous (wasn’t able to remove those
> packages though).
The correct procedure to remove uploaded files is `man dcut` and for
backports you do not upload to ftp-master.d.o, but backports-master.d.o.
> Backport process was pretty straight-forward and limited just to
> changing debian/control file and using PostgreSQL 8.4 as minimal
> dependency and debhelper 8.0.0.
> If you’re keen to have a go as well, you can grab .debs from
> http://sultan.timedout.org/~bart/debian/ (distro is
Thank you for an apt-get repository, two notes:
1) the Release file is not signed
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)
> So far, I upgraded 12 machines with that and they
> went through incremental backup without any problems. Running
> differential now.
I will do once I have finished testing the i386 squeeze-proposed-updates
packages at (incremental backups are OK from clients, the director will
be tested this night):
Gismo / Luca
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 835 bytes
Desc: not available
More information about the pkg-bacula-devel