For my own backports I have been changing the debhelper version dependency in the debian/control file to specify the woody version. I have not backported debhelper. This process has worked pretty well so far.
Indeed that was what I was thinking to do if nobody answered my pray. I hope it also works for me. :)
Note that I follow the lead of others and I decrement the version and add a unique identifier. This way when sarge releases and a sarge update done the backported packages will be automatically upgraded to the official Debian repository versions. I only do this when I need to make any modifications to the package. If it is just a straight recompile then I usually am lazy and I don't modify the package at all.
Well, for some time I will only recompile things, but moreover I'd like to know more details about that procedure (decrementing version, adding a unique identifier, any example?). Please note that I am not using sarge but woody instead.
Just curious, what programs are you trying to backport?
Well, indeed many of them. I am trying to backport sound applications only available in unstable to make them available for subscribers of my sound related mailing list that lack the spare-time/interest/bandwidth for upgrading to sid. Specially, I am thinking of ardour, one of those applications whose backporting seems a mess.
For other apps, I also get stuck usually backporting cdbs, but I think I will be editing its control file to remove build dependencies from springgraph, another death loop well known for me. ;)
Thanks a lot, even though any further feedback will still be very useful.
Regards, Ismael -- "Tout fourmille de commentaries; d'auteurs il en est grande cherté"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
