Try fully specifying the .spec file name as in "./ltib -m prep -p shorwall-5.0.5-wsu.spec"
On 02/22/2016 04:37 PM, Aaron Wegner wrote: > In my pkg_map I have > > PKG_SHOREWALL_CORE = shorewall-core-5.0.5-wsu > PKG_SHOREWALL = shorewall-5.0.5-wsu > > and in my packages.lkc I have > > config PKG_SHOREWALL_CORE > bool "shorewall-core" > default y > help > Say something here. > > config PKG_SHOREWALL > bool "shorewall" > default y > help > Say something here. > > Yet when I run ltib I get > > [robert@geiswbuild1 ~/0358/ltib Mon Feb 22 16:28:12] > $ ./ltib -m prep -p shorewall > > Processing: shorewall-core-5.0.5-wsu > ====================================== > Build path taken because: build key set, no prebuilt rpm, > > rpmbuild --dbpath /home/robert-lovelock/0358/ltib/rootfs//var/lib/rpm > --target ppc --define '_unpackaged_files_terminate_build 0' --define > '_target_cpu ppc' --define '__strip strip' --define '_topdir > /home/robert-lovelock/0358/ltib/rpm' --define '_prefix /usr' --define > '_tmppath /home/robert-lovelock/0358/ltib/tmp' --define '_rpmdir > /home/robert-lovelock/0358/ltib/rpm/RPMS' --define '_mandir > /usr/share/man' --define '_sysconfdir /etc' --define '_localstatedir > /var' -bp config/platform/mpc5121ads/shorewall-core-5.0.5-wsu.spec > > > so it's using the spec file for shorewall-core rather than the one for > shorewall. In the past when I encountered a name conflict I've just > renamed one package completely. Has anyone else run into this? Any > suggestions? > > $ ./ltib --version > ltib 13.2.1 ($Revision: 1.93 $) > > > _______________________________________________ > LTIB home page: http://ltib.org > > Ltib mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/ltib > . > -- Peter Barada [email protected] _______________________________________________ LTIB home page: http://ltib.org Ltib mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/ltib
