Debian Dependencies - CVS Head
Hi, guys! Yesterday, I tried to compile the latest FreeRadius (cvs head) on Sarge and got this: dpkg-buildpackage: source package is freeradius dpkg-buildpackage: source version is 2.0.0-pre2 dpkg-buildpackage: source maintainer is Nicolas Baradakis <nbk@sitadelle.com> dpkg-buildpackage: host architecture is i386 dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 5) dpkg- dev (>= 1.13.25) dpkg-buildpackage: Build dependencies/conflicts unsatisfied; aborting. dpkg-buildpackage: (Use -d flag to override.) I should note that 2.0pre0 worked fine, and trying with -d didn't work. I thought: OK, tomorrow I install on a new machine. Got one with Ubuntu Server LTS, and then... got the same error. This time the error was only with dpkg-dev (Ubuntu comes with 1.13.11), but anyway, does it really need those versions? What do I have to use to compile it without errors? P.S.: I ended up commenting the dependency and it (seems to have) worked. -- Humberto Diógenes http://humberto.digi.com.br
On Sat, Sep 01, 2007 at 12:24:04AM -0300, Humberto Diogenes said:
Hi, guys!
Yesterday, I tried to compile the latest FreeRadius (cvs head) on Sarge and got this:
dpkg-buildpackage: source package is freeradius dpkg-buildpackage: source version is 2.0.0-pre2 dpkg-buildpackage: source maintainer is Nicolas Baradakis <nbk@sitadelle.com> dpkg-buildpackage: host architecture is i386 dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 5) dpkg- dev (>= 1.13.25) dpkg-buildpackage: Build dependencies/conflicts unsatisfied; aborting. dpkg-buildpackage: (Use -d flag to override.)
I should note that 2.0pre0 worked fine, and trying with -d didn't work.
I thought: OK, tomorrow I install on a new machine. Got one with Ubuntu Server LTS, and then... got the same error. This time the error was only with dpkg-dev (Ubuntu comes with 1.13.11), but anyway, does it really need those versions? What do I have to use to compile it without errors?
I don't see any big changes in dpkg-dev 1.13.25 aside from support for lzma archives, which I doubt is needed here. 1.13.19 is a version that is frequently used as a versioned dependency, since that's when the ${source:Version} and so on variables were introduced. Debhelper 5 is likely to be necessary for a variety of reasons. The package will probably build with those versions relaxed, but it may not generate dependencies as the packagers expect. -- -------------------------------------------------------------------------- | Stephen Gran | QOTD: I've heard about civil | | steve@lobefin.net | Engineers, but I've never met one. | | http://www.lobefin.net/~steve | | --------------------------------------------------------------------------
On 01/09/2007, at 08:39, Stephen Gran wrote:
On Sat, Sep 01, 2007 at 12:24:04AM -0300, Humberto Diogenes said:
dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 5) dpkg- dev (>= 1.13.25)
I don't see any big changes in dpkg-dev 1.13.25 aside from support for lzma archives, which I doubt is needed here. 1.13.19 is a version that is frequently used as a versioned dependency, since that's when the ${source:Version} and so on variables were introduced. Debhelper 5 is likely to be necessary for a variety of reasons. The package will probably build with those versions relaxed, but it may not generate dependencies as the packagers expect.
Stephen, It worked fine with dpkg-dev 1.13.11. I then had to edit debian/ control again to "downgrade" lsb-base, too (as you can see further down). The only glitch I found was that the /etc/init.d/freeradius script didn't work anymore, I had to use the older one (pre1). It's OK for me if you decided to break compatibility with Debian Sarge, but I expect FreeRadius 2.0 to be compatible with at least Ubuntu Server LTS (Dapper). Index: control =================================================================== RCS file: /source/radiusd/debian/control,v retrieving revision 1.48 diff -r1.48 control 2c2 < Build-Depends: debhelper (>= 5), dpatch (>= 2), dpkg-dev (>= 1.13.25), autotools-dev, libtool (>= 1.5), libltdl3-dev, libpam0g- dev, libmysqlclient15-dev | libmysqlclient-dev, libgdbm-dev, libldap2- dev, libsasl2-dev, libiodbc2-dev, libkrb5-dev, libperl-dev, libpcap- dev, snmp, libsnmp9-dev | libsnmp-dev, libpq-dev, libssl-dev ---
Build-Depends: debhelper (>= 5), dpatch (>= 2), dpkg-dev (>= 1.13), autotools-dev, libtool (>= 1.5), libltdl3-dev, libpam0g-dev, libmysqlclient15-dev | libmysqlclient-dev, libgdbm-dev, libldap2-dev, libsasl2-dev, libiodbc2-dev, libkrb5-dev, libperl-dev, libpcap-dev, snmp, libsnmp9-dev | libsnmp-dev, libpq-dev, libssl-dev 10c10 < Depends: lsb-base (>= 3.1-23.2), adduser, openssl, ${shlibs:Depends}
Depends: lsb-base (>= 3.1), adduser, openssl, ${shlibs:Depends}
-- Humberto Diógenes http://humberto.digi.com.br
On Sat, Sep 01, 2007 at 05:31:01PM -0300, Humberto Diogenes said:
On 01/09/2007, at 08:39, Stephen Gran wrote: Stephen,
It worked fine with dpkg-dev 1.13.11. I then had to edit debian/ control again to "downgrade" lsb-base, too (as you can see further down).
The only glitch I found was that the /etc/init.d/freeradius script didn't work anymore, I had to use the older one (pre1).
This will be because of the downgrade of lsb-base.
It's OK for me if you decided to break compatibility with Debian Sarge, but I expect FreeRadius 2.0 to be compatible with at least Ubuntu Server LTS (Dapper).
I am not responsible for the debian/ directory in the distributed tarball. I and my comaintainer are responsible for what ships with Debian. These two things are related, but not the same. That being said, I am afraid I have to tell you that I am unlikely to keep new features out of the packaging for the benefit of Ubuntu's LTS contracts. Take care, -- -------------------------------------------------------------------------- | Stephen Gran | Wagner's music is better than it | | steve@lobefin.net | sounds. -- Mark Twain | | http://www.lobefin.net/~steve | | --------------------------------------------------------------------------
Humberto Diogenes wrote:
I thought: OK, tomorrow I install on a new machine. Got one with Ubuntu Server LTS, and then... got the same error. This time the error was only with dpkg-dev (Ubuntu comes with 1.13.11), but anyway, does it really need those versions? What do I have to use to compile it without errors?
I voluntarily put these versions to require "etch". Some new features were not working with previous (obsolete) releases of Debian. Since "etch" is the stable release for several months now, it shouldn't be a problem. You may manage to make a package with earlier versions of the Debian utilities but I can't tell the result because they're not the versions I used when I tested the packaging scripts.
It worked fine with dpkg-dev 1.13.11. I then had to edit debian/ control again to "downgrade" lsb-base, too (as you can see further down).
The only glitch I found was that the /etc/init.d/freeradius script didn't work anymore, I had to use the older one (pre1).
The new initscript requires lsb-base 3.1-23.2 to work. Your changes to debian/control are resulting in a defective package. The initscript is now using the LSB start_daemon, killproc and log_* functions instead of calling directly the start-stop-daemon utility. It depends on a specific version of lsb-base to address a serious bug in the package: http://bugs.debian.org/434756
It's OK for me if you decided to break compatibility with Debian Sarge, but I expect FreeRadius 2.0 to be compatible with at least Ubuntu Server LTS (Dapper).
Sorry, but it isn't as simple as putting a few numbers after the packages names in the dependencies. My goal is to provide the best possible package for the Debian users. I'm not inclined to remove the new features for Ubuntu's long-term support. -- Nicolas Baradakis
On 02/09/2007, at 10:35, Nicolas Baradakis wrote:
It's OK for me if you decided to break compatibility with Debian Sarge, but I expect FreeRadius 2.0 to be compatible with at least Ubuntu Server LTS (Dapper).
Sorry, but it isn't as simple as putting a few numbers after the packages names in the dependencies.
Yes, I know that. I just thought it wouldn't be so hard because pre1 worked even on Sarge.
My goal is to provide the best possible package for the Debian users. I'm not inclined to remove the new features for Ubuntu's long-term support.
Well, if that's how it'll be done, I suggest it should be clearly stated in the docs: "Debian package creation will only work on Etch", or something like that. -- Humberto Diógenes http://humberto.digi.com.br
Humberto Diogenes wrote:
On 02/09/2007, at 10:35, Nicolas Baradakis wrote:
It's OK for me if you decided to break compatibility with Debian Sarge, but I expect FreeRadius 2.0 to be compatible with at least Ubuntu Server LTS (Dapper).
Sorry, but it isn't as simple as putting a few numbers after the packages names in the dependencies.
Yes, I know that. I just thought it wouldn't be so hard because pre1 worked even on Sarge.
The scripts have been updated in pre2 and are now a lot better and also easier to maintain. The downside is that newer utilities are required. After reexamination the only thing I could change is downgrading dpkg-dev (>= 1.13.25) to 1.13.19 so the package may build on edgy or knoppix. As Stephen said, 1.13.19 is the minimum required version for the variable ${source:Version}. Although I couldn't test it, the other changes in dpkg-dev should not affect the freeradius package.
My goal is to provide the best possible package for the Debian users. I'm not inclined to remove the new features for Ubuntu's long-term support.
Well, if that's how it'll be done, I suggest it should be clearly stated in the docs: "Debian package creation will only work on Etch", or something like that.
No because it is just not true. The pre2 will work on all the variants of Debian that are up-to-date. The problem here is not really FreeRADIUS, it's because Ubuntu is providing to you a distribution with obsolete packages. -- Nicolas Baradakis
participants (3)
-
Humberto Diogenes -
Nicolas Baradakis -
Stephen Gran