[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#70269: automatic build fails for potato

Steve Greenland wrote:
> So I'm supposed to go back and figure out if my packages can be
> successfully built with debhelper 2.0.58? If so, how can I -- is there
> a complete archive of all released debhelpers somewhere?

Please read the bottom of http://cgi.debian.org/cgi-bin/bugreport.cgi?bug=51898
There's a 5 step checklist, and a slighlty longer checklist, depending
on how well you want to do it. If you want to do it at all.

> this is going to happen. Instead, I'll just (probably automatically)
> update my build-depends line to the version of debhelper that's
> installed on my machine. So the de-facto requirement is going to be
> "a nearly current version of debhelper". The same is true for the
> build-essential packages -- nobody is going to go back and check their
> stuff against old versions of gcc and make. Admittedly, those are much
> slower moving targets...but dpkg-dev isn't, necessarily.

I agree. I actually don't see much evidence that they're slower moving.

Since we all arn't experts on incomapatable changes added to make, gcc,
debhelper, etc, etc, and we probably don't have an unlimited amount of
time to research them, document them, or write automated tools to detect
them, I think the best we can do is add versions to the build-depends 
line if bugs are filed.

> Mine don't. Or rather, the version needed is sufficiently old that I
> have no idea what it might be. 

It's probably approximatly 2 years old. That's how far back I had to go
to find versions of debhelper that my packages.

see shy jo

To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: