2009/4/7 Brandon Metcalf <bran...@geronimoalloys.com> > ----- Arnaud Quette <aquette....@gmail.com> wrote: > > 2009/4/7 Brandon Metcalf <bran...@geronimoalloys.com> > > > > > > > > ----- Arnaud Quette <aquette....@gmail.com> wrote: > > > > 2009/4/6 Brandon Metcalf <bran...@geronimoalloys.com> > > > > > What do you mean by backport the packages in jaunty? What is > involved > > > in > > > > > doing this? > > > > > > > > > > > > > - getting the source package (.dsc, .orig.tar.gz and .diff.gz) from > here > > > > http://packages.ubuntu.com/jaunty/nut > > > > - install the build toolchain (gcc, make, ...) andautotools-dev > fakeroot > > > > dh-make build-essential devscripts > > > > - unpack the source package: dpkg-source -x *.dsc > > > > - from the build dir: debuild -us -uc > > > > - you'll be warned of the missing prerequisites > > > > - once built successfully, your debs will be in the parent dir. > > > > > > I'm running "debuild -us -uc" and, as you said, getting a lot of unmet > > > build dependencies. My questions are, should I upgrade my hardy system > with > > > these dependencies or override them with -d? I ultimately want to > install > > > nut 2.4.1 on a different server system running hardy. Will these > > > dependencies need to be upgraded on this server system as well? If so, > I'm > > > not sure I want to configure this system beyond the standard hardy > install. > > > > > > > it depends on the deps! > > first, you can trim down debian/control Build-deps, remove the > powerman-pdu > > packages and possibly some more (nut-snmp?) according to your needs. > > then go to debian/rules and remove the uneeded options from the configure > > call. > > after that, the remaining deps should be straightworfard... you may want > to > > force --without-wrap or bring down the dep on libwrap too. > > maybe one more iirc: the debhelper dep. can be brought down to hardy's > > version if you remove the dh_lintian call in debian/rules. > > > > Thanks for your help. As you suggested, I would prefer to install a deb > > > package for nut 2.4.1 since it does offer better integration. > > I should have provided this information the first time. Here are the unmet > dependencies: > > $ debuild -us -uc > dpkg-checkbuilddeps: Unmet build dependencies: debhelper (>= 6.0.7~) > autoconf automake libtool libgd2-xpm-dev | libgd2-noxpm-dev libsnmp-dev | > libsnmp9-dev libusb-dev (>= 0.1.8) libhal-dev (>= 0.5.8) libdbus-1-dev > libdbus-glib-1-dev libglib2.0-dev libneon27-gnutls-dev | > libneon26-gnutls-dev | libneon-dev | libneon27-dev | libneon26-dev > libwrap0-dev (>= 7.6) dpatch > debuild: fatal error at line 993: > You do not appear to have all build dependencies properly met, aborting. > (Use -d flag to override.) > > Based on this, can you give me some help on what to do? I'm still a little > unclear. > > still the same as my above explanation (modify control and rules) I've missed the nut-xml package that can be removed with the neon deps. now it's up to you to remove the deps you don't need with all the explanation given...
cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/
_______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser