[opensuse-buildservice] cpio fails to build, why?
I started a small opensuse 11.0 base system and bootstrapped it. All packages succeeded except cpio, which fails. Can someone please look in my project home:a23d56:opensuse-11.0-minimal:self, and see why this fails. I did not make any changes to the 11.0 package, so I don't see why it should fail. The rpms were created, how can it fail? Here is the end of the log: Supplements: packageand(bundle-lang-other:cpio) Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/cpio-2.9-build Wrote: /usr/src/packages/SRPMS/cpio-2.9-52.1.src.rpm Wrote: /usr/src/packages/RPMS/i586/cpio-2.9-52.1.i586.rpm Wrote: /usr/src/packages/RPMS/i586/cpio-lang-2.9-52.1.i586.rpm ... checking for files with abuild user/group RPMLINT report: =============== Traceback (most recent call last): File "rpmlint.py", line 293, in <module> File "rpmlint.py", line 97, in main File "rpmlint.py", line 166, in runChecks File "SpecCheck.py", line 178, in check File "Pkg.py", line 146, in readlines IOError: [Errno 2] No such file or directory: '/tmp/cpio-2.9-52.1.src.rpm.10814/cpio.spec' System halted. -- Webmail for Dialup Users http://www.isp2dial.com/freeaccounts.html -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
John Kelly napsal(a):
The problem might be that rpmlint needs cpio to unpack the rpms (rpm2cpio ... | cpio -id). And there is no cpio package when building cpio itself ;-). Try adding Keep: cpio to the project config (osc meta prjconf <your project> -e). See http://en.opensuse.org/Build_Service/Tips_and_Tricks#How_is_a_buildenvironme... hth, Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, 24 Nov 2008 16:10:26 +0100, Michal Marek <mmarek@suse.cz> wrote:
When using that line alone, nothing happened. Maybe I was defaulting to the openSUSE:11.0 config, and my one line config overrode that? In any case, I copied the openSUSE:11.0 config and used it in my project, added the line you suggest, and now cpio does build. Thanks for that. When I get bootstrapped with base packages, I want to delete my repo reference to openSUSE:11.0, so my own repo becomes self sufficient. That didn't work before either. Maybe using my own project config will fix that too. I hope so. For anyone trying to bootstrap their own distro, the docs leave many questions unanswered. The OBS system, and especially the web interface, is very slow. Too much scripting probably. Why people try to build large scale systems from scripting goop like Ruby and Python, is a mystery to me. I had two packages in showing finished status for at least 30 minutes before they succeeded. That's annoying. -- Webmail for Dialup Users http://www.isp2dial.com/freeaccounts.html -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
John Kelly napsal(a):
The problem might be that rpmlint needs cpio to unpack the rpms (rpm2cpio ... | cpio -id). And there is no cpio package when building cpio itself ;-). Try adding Keep: cpio to the project config (osc meta prjconf <your project> -e). See http://en.opensuse.org/Build_Service/Tips_and_Tricks#How_is_a_buildenvironme... hth, Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, 24 Nov 2008 16:10:26 +0100, Michal Marek <mmarek@suse.cz> wrote:
When using that line alone, nothing happened. Maybe I was defaulting to the openSUSE:11.0 config, and my one line config overrode that? In any case, I copied the openSUSE:11.0 config and used it in my project, added the line you suggest, and now cpio does build. Thanks for that. When I get bootstrapped with base packages, I want to delete my repo reference to openSUSE:11.0, so my own repo becomes self sufficient. That didn't work before either. Maybe using my own project config will fix that too. I hope so. For anyone trying to bootstrap their own distro, the docs leave many questions unanswered. The OBS system, and especially the web interface, is very slow. Too much scripting probably. Why people try to build large scale systems from scripting goop like Ruby and Python, is a mystery to me. I had two packages in showing finished status for at least 30 minutes before they succeeded. That's annoying. -- Webmail for Dialup Users http://www.isp2dial.com/freeaccounts.html -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
John Kelly -
Michal Marek