Bug#373089: sarge backport

Frank S. Thomas frank at thomas-alfeld.de
Tue Jun 13 16:19:50 UTC 2006

On Tuesday 13 June 2006 15:39, Robert Millan wrote:
> On Tue, Jun 13, 2006 at 11:13:16AM +0200, Frank S. Thomas wrote:
> > On Monday 12 June 2006 20:22, Robert Millan wrote:
> > > Here's a pair of compat hacks to aid in sarge backport.
> > >
> > > It is not complete, as all changes weren't clean/desirable, though.
> >
> > Thanks for the patch, I've applied it. We have a sarge backport in our
> > SVN repository, which is a bit outdated - it's still at BOINC version
> > 5.4.3: http://svn.debian.org/wsvn/pkg-boinc/branches/sarge/boinc/
> >
> > Would you be interested in updating it to the latest version, apply all
> > your other backport patches and upload it to backports.org?
> Here's the diff for current trunk.

Thanks. I've now resynchronized the sarge branch with the current trunk. 

> Note: branches/sarge/boinc contained some changes that aren't really
> necessary, like deleting (harmless) dh_clean parameters for non-existant
> files.

I also added all the boinc-manager files to make the diff between the trunk 
and the sarge branch as small as possible. That should ease future 

So, the only remaining question is if we should upload the backported package 
to backports.org? Since I'm not a DD, I can't do it myself.

Die Garde stirbt, aber sie ergibt sich nicht!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-boinc-devel/attachments/20060613/9ba54bf0/attachment.pgp

More information about the pkg-boinc-devel mailing list