Re: New dpkg-buildpackage error

2006-03-18 Thread Martin Michlmayr
* Joey Hess <[EMAIL PROTECTED]> [2006-03-18 13:47]: > > It sounds more like a change in debhelper. I seem to remember > > something recently about a change in the default compatibility level. > The default compatability is, a and will always be, 1. debhelper does > not break backwards compatibilit

Re: New dpkg-buildpackage error

2006-03-18 Thread Joey Hess
Roland Mas wrote: > It sounds more like a change in debhelper. I seem to remember > something recently about a change in the default compatibility level. The default compatability is, a and will always be, 1. debhelper does not break backwards compatibility. -- see shy jo signature.asc Descri

Re: New dpkg-buildpackage error

2006-03-18 Thread David Jarvie
On Friday 17 March 2006 22:39, Michael Banck wrote: > Your question rather belongs on the debian-mentors list. > > On Fri, Mar 17, 2006 at 10:21:25PM +, David Jarvie wrote: > > cp: cannot stat `./debian/tmp/usr/bin/kalarm': No such file or directory > > dh_install: command returned error code 2

Re: New dpkg-buildpackage error

2006-03-18 Thread Roland Mas
David Jarvie, 2006-03-17 23:30:17 +0100 : [...] > dh_install -pkalarm-upgrade > cp: cannot stat `./debian/tmp/usr/bin/kalarm': No such file or directory > dh_install: command returned error code 256 > make: *** [binary-install/kalarm-upgrade] Error 1 > > True enough, a tmp directory doesn't exist

Re: New dpkg-buildpackage error

2006-03-17 Thread Michael Banck
Hi, Your question rather belongs on the debian-mentors list. On Fri, Mar 17, 2006 at 10:21:25PM +, David Jarvie wrote: > cp: cannot stat `./debian/tmp/usr/bin/kalarm': No such file or directory > dh_install: command returned error code 256 > make: *** [binary-install/kalarm-upgrade] Error 1 >