[opensuse-buildservice] SUSE_Linux_10.1 build on x86_64 failed with "Read-only file system" - how to just rebuild one architecture?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've finally bitten the bullet and started building some of my RPMs using the build service. Great job! I am very impressed, even though it took me a bit to figure out how to use the web interface :) Unfortunately one of my packages failed to build, but just on AMD64 - the last message in the build log is: http://build.opensuse.org/package/live_build_log?package=mercurial&repositor... [SNIP] build02 started "build mercurial.spec" at Wed Aug 2 17:44:53 CEST 2006. [...] installing filesystem-10.1-5 error: unpacking of archive failed on file /proc: cpio: chown failed - Read-only file system [SNIP] Is that a problem with that particular build host? I wonder if triggering a rebuild would fix this. Is there a way to just rebuild on a certain architecture? It seems like one can only trigger rebuilds by Repository currently, but that would also rebuild the i586 package, which actually built fine already. Any help would be appreciated! Thanks. Bye, LenZ - -- - ------------------------------------------------------------------ Lenz Grimmer <lenz@grimmer.com> -o) [ICQ: 160767607 | Jabber: LenZGr@jabber.org] /\\ http://www.lenzg.org/ V_V -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFE0NGbSVDhKrJykfIRAvEtAJ9hM6J6w8P0b9kvUDnwbPOgyCElSwCePA7A lKjbGIUk3J7ALmDIQiOF3xg= =bfWd -----END PGP SIGNATURE-----
On Wed, Aug 02, 2006 at 06:23:56PM +0200, Lenz Grimmer wrote:
Unfortunately one of my packages failed to build, but just on AMD64 - the last message in the build log is:
http://build.opensuse.org/package/live_build_log?package=mercurial&repositor...
[SNIP] build02 started "build mercurial.spec" at Wed Aug 2 17:44:53 CEST 2006. [...] installing filesystem-10.1-5 error: unpacking of archive failed on file /proc: cpio: chown failed - Read-only file system [SNIP]
Is that a problem with that particular build host?
Since this also happens to me again and again I don't think this is related to a particular build host.
I wonder if triggering a rebuild would fix this.
Very likely, yes.
Is there a way to just rebuild on a certain architecture?
I don't think so. :-(
It seems like one can only trigger rebuilds by Repository currently, but that would also rebuild the i586 package, which actually built fine already.
Right, and it wastes the build host resources ... Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany ------------------------------------------------------
On Wednesday, 2. August 2006 18:36, Stefan Dirsch wrote:
On Wed, Aug 02, 2006 at 06:23:56PM +0200, Lenz Grimmer wrote:
Is there a way to just rebuild on a certain architecture?
I don't think so. :-(
api.opensuse.org will support this with the next deploy, which will come this week or early next week. -- Andreas Bauer - Novell - SUSE Internal Tools
On 2006-08-03 11:53:12 +0200, Andreas Bauer wrote:
On Wednesday, 2. August 2006 18:36, Stefan Dirsch wrote:
On Wed, Aug 02, 2006 at 06:23:56PM +0200, Lenz Grimmer wrote:
Is there a way to just rebuild on a certain architecture?
I don't think so. :-(
api.opensuse.org will support this with the next deploy, which will come this week or early next week.
if the smart package manager sees newer packages on i586 than the packages you have for x86_64, it will blindly install those. just a warning. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marcus Rueckert wrote:
On 2006-08-03 11:53:12 +0200, Andreas Bauer wrote:
On Wednesday, 2. August 2006 18:36, Stefan Dirsch wrote:
On Wed, Aug 02, 2006 at 06:23:56PM +0200, Lenz Grimmer wrote:
Is there a way to just rebuild on a certain architecture? I don't think so. :-( api.opensuse.org will support this with the next deploy, which will come this week or early next week.
if the smart package manager sees newer packages on i586 than the packages you have for x86_64, it will blindly install those.
Unless you use my smart packages [1] where I've added a patch that enhances its behavior on x86_64. The patch has been submitted upstream but is not merged (Niemeyer wanted to come up with a better implementation). Yet, it does the trick. [1] http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/System/smart Patch is submitted and explained here: http://tracker.labix.org/issue177 cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser@skynet.be> <guru@unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFE0mUPr3NMWliFcXcRAup/AKCMKNYSBfBlOhzPcJi1MsCg77FkewCgv9y1 5hYH1Ktah95m520fQyPAKS8= =5Df0 -----END PGP SIGNATURE-----
On 2006-08-03 23:05:19 +0200, Pascal Bleser wrote:
Unless you use my smart packages [1] where I've added a patch that enhances its behavior on x86_64. The patch has been submitted upstream but is not merged (Niemeyer wanted to come up with a better implementation). Yet, it does the trick.
no ppc/ppc64 no s390/s390x
[1] http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/System/smart
Patch is submitted and explained here: http://tracker.labix.org/issue177
and you already know it wont go upstream in that form. ;) darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marcus Rueckert wrote:
On 2006-08-03 23:05:19 +0200, Pascal Bleser wrote:
Unless you use my smart packages [1] where I've added a patch that enhances its behavior on x86_64. The patch has been submitted upstream but is not merged (Niemeyer wanted to come up with a better implementation). Yet, it does the trick.
no ppc/ppc64 no s390/s390x
Ooops, sorry, yeah that's a patch for x86_64 only.
[1] http://linux01.gwdg.de/~pbleser/rpm-navigation.php?cat=/System/smart
Patch is submitted and explained here: http://tracker.labix.org/issue177
and you already know it wont go upstream in that form. ;)
I know, but I don't care, it works great for me. Maybe one day Niemeyer will come up with a better implementation but as he's really, really busy, in the meantime (= 1 or 2 years), my patch works ;) cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser@skynet.be> <guru@unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFE0no0r3NMWliFcXcRAsYkAKCUMgusaAlF7s5sE4WN0E1ZL1k/AQCgmj9p orQkLf5otqGPGMH8C8fOs+o= =5xZq -----END PGP SIGNATURE-----
On Wed, Aug 02, 2006 at 06:23:56PM +0200, Lenz Grimmer wrote:
I've finally bitten the bullet and started building some of my RPMs using the build service. Great job! I am very impressed, even though it took me a bit to figure out how to use the web interface :)
Unfortunately one of my packages failed to build, but just on AMD64 - the last message in the build log is:
http://build.opensuse.org/package/live_build_log?package=mercurial&repositor...
[SNIP] build02 started "build mercurial.spec" at Wed Aug 2 17:44:53 CEST 2006. [...] installing filesystem-10.1-5 error: unpacking of archive failed on file /proc: cpio: chown failed - Read-only file system [SNIP]
Ah, I just found the cause of this. The "build.rpm" package mounts /proc with -oro when doing the build, this doesn't work well when multiple build processes are running, as the kernel shares the proc attributes. I now removed the -oro, after all the clients are updated, the /proc problem should be finally gone. Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
participants (6)
-
Andreas Bauer -
Lenz Grimmer -
Marcus Rueckert -
Michael Schroeder -
Pascal Bleser -
Stefan Dirsch