[pkg-bacula-devel] Incomplete upload found in Debian upload queue

Bart Swedrowski bart at timedout.org
Fri Jun 22 09:40:52 UTC 2012

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.

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).

  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).

  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?

> 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:
>  <http://backports-master.debian.org/Contribute/>

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).

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
squeeze-backports).  So far, I upgraded 12 machines with that and they
went through incremental backup without any problems.  Running
differential now.

More information about the pkg-bacula-devel mailing list