From msalter at redhat.com Tue Jul 7 22:03:10 2009 From: msalter at redhat.com (Mark Salter) Date: Tue, 07 Jul 2009 18:03:10 -0400 Subject: crossbuilding rpms with koji Message-ID: <1247004190.2512.14.camel@deneb.localdomain> I have been doing some experimenting with crossbuilds of rpms using koji. I realize that fedora policy requires supported arches to be native built, but my focus is towards infrastructure to crossbuild rpms for embedded systems where the fedora distribution is not well suited. So as a first stab at this, I started working with the F-10 release packages with an armv5tel target. The reason for this was that the ongoing work with fedora arm secondary arch allowed me to focus on the crossbuild infrastructure without having to spend a lot of time working on arch-specific patches in the packages themselves. Anyway, I ended up crossbuilding around 400 F-10 packages. Enough to build up a rootfs which boots to a familiar looking gnome desktop on an omap-based beagleboard. Of those 400 packages, about 20% needed some amount of patching to support crossbuilding. Most were simple things like specfile tweaks (i.e. "s/gcc/%{__cc}/") or simple makefile patches to get around hard-coded tool names. And a handful needed more complicated patches (almost entirely autoconf/automake related). Now that I've gotten to this point, I'd like to solicit some comments on the approach taken and get some guidance on how to beat the kludgey first cut into shape so that it can be acceptable upstream. The infrastructure side consists of: * A yum plugin which allows yum to install non-native rpms into the build roots. * A mock plugin to handle the crossbuilding details. * A koji patch to support the crossbuild extensions to mock * A cross-toolchain package * A cross-rpm-config package which provides configuration for rpm in the mock chroot and configuration details for the mock plugin. The koji build machines need the first three things. The kojihub only needs the patched koji. Native builds are not affected by any of the above. There are no changes to the koji db schema. Tweaking the schema may make some things cleaner, but I don't have a lot of db experience and I left it alone for the first cut at this. There is nothing special in the koji server/builder setup except that the patch adds an option to the kojid.conf which is used to indicate that a host can crossbuild for some target(s). This is something that should probably be done in the database. The mock config file is used to distinguish native build from cross builds. Mock commands work the same for crossbuilding as for native. For crossbuilding, the "chroot_setup_cmd" needs to install the cross toolchain and cross-rpm-config packages in addition to the usual 'build' group. The koji patch adds a 'build-cross-' group to the mock config to accomplish this. The cross toolchain uses a sysroot to provide standard headers and libraries for the crossbuild. Basically, there is the normal mock chroot populated just as it would be for native builds. The mock cross plugin supports a second 'root' which serves as the toolchain sysroot. That is, if we crossbuild package 'foo' which 'BuildRequires: a b c', the normal mock code depsolves for 'a', 'b', and 'c' using a native-arch repo and installs those in the mock chroot. The mock cross plugin will also depsolve for 'a', 'b', and 'c', except using a target-arch repo and install them into the toolchain sysroot. The cross plugin also sets up a .rpmmacros and .rpmrc file in the mock build homedir which overrides rpmbuild macros such as "%{__cc}" to reference the cross-toolchain. That's the overview, but its really more complicated than that. For instance, if a package buildrequires texinfo to make docs, we really don't want to waste time/space putting texinfo into the toolchain sysroot because the native one is the one we want. The cross-rpm-config package has configuration that tells mock not to bother with that package for the target sysroot. These are the sorts of devils in the details of crossbuilding rpms. If anyone is interested and would like to take a look at the code and comment, I placed source rpms at: http://people.redhat.com/msalter/crossbuild/source/ For convenience, here is the koji patch: http://people.redhat.com/msalter/crossbuild/koji/koji.patch And the yum plugin: http://people.redhat.com/msalter/crossbuild/yum/cross.py And the mock plugin: http://people.redhat.com/msalter/crossbuild/mock/cross.py and just for fun, a pic of F-10 running on a beagleboard: http://people.redhat.com/msalter/beagle-gnome.jpg --Mark From kedars at marvell.com Thu Jul 9 05:24:14 2009 From: kedars at marvell.com (Kedar Sovani) Date: Wed, 8 Jul 2009 22:24:14 -0700 Subject: crossbuilding rpms with koji In-Reply-To: <20090708160006.E6C6B61A23A@hormel.redhat.com> Message-ID: <25B60CDC2F704E4E9D88FFD52780CB4C04A505BDD7@SC-VEXCH1.marvell.com> > -----Original Message----- > Date: Tue, 07 Jul 2009 18:03:10 -0400 > From: Mark Salter > Subject: crossbuilding rpms with koji > To: fedora-buildsys-list at redhat.com > Message-ID: <1247004190.2512.14.camel at deneb.localdomain> > Content-Type: text/plain > > I have been doing some experimenting with crossbuilds of rpms > using > koji. I realize that fedora policy requires supported arches to > be > native built, but my focus is towards infrastructure to > crossbuild > rpms for embedded systems where the fedora distribution is not > well > suited. So as a first stab at this, I started working with the > F-10 > release packages with an armv5tel target. The reason for this > was > that the ongoing work with fedora arm secondary arch allowed me > to > focus on the crossbuild infrastructure without having to spend > a lot > of time working on arch-specific patches in the packages > themselves. > > Anyway, I ended up crossbuilding around 400 F-10 packages. > Enough to > build up a rootfs which boots to a familiar looking gnome > desktop on > an omap-based beagleboard. Of those 400 packages, about 20% > needed > some amount of patching to support crossbuilding. Most were > simple > things like specfile tweaks (i.e. "s/gcc/%{__cc}/") or simple > makefile > patches to get around hard-coded tool names. And a handful > needed more > complicated patches (almost entirely autoconf/automake > related). Great! I had a similar attempt to build cross rpms for ARM. And since I was cross-building I could built those against glibc as well as uClibc. Although my package set is much smaller (~50). I'll try to place the cross patches that I have somewhere, probably most of them are already in your setup. I didn't build these in koji though, but it would be cool to have them in there. > > Now that I've gotten to this point, I'd like to solicit some > comments > on the approach taken and get some guidance on how to beat the > kludgey > first cut into shape so that it can be acceptable upstream. The > infrastructure side consists of: > > * A yum plugin which allows yum to install non-native rpms > into the build roots. > > * A mock plugin to handle the crossbuilding details. > > * A koji patch to support the crossbuild extensions to mock > > * A cross-toolchain package > > * A cross-rpm-config package which provides configuration > for rpm in the mock chroot and configuration details for > the mock plugin. > IIUC you have pkgname.armv5tel.rpm? If so, how did you make rpm to build those? I had to modify /etc/rpm/platform to fool rpm in thinking it is building for armv5tel. Is there a cleaner way for doing this? ...snip... > > If anyone is interested and would like to take a look at the > code and > comment, I placed source rpms at: > > http://people.redhat.com/msalter/crossbuild/source/ > > For convenience, here is the koji patch: > > http://people.redhat.com/msalter/crossbuild/koji/koji.patch > > And the yum plugin: > > http://people.redhat.com/msalter/crossbuild/yum/cross.py > > And the mock plugin: > > http://people.redhat.com/msalter/crossbuild/mock/cross.py > > and just for fun, a pic of F-10 running on a beagleboard: > > http://people.redhat.com/msalter/beagle-gnome.jpg > > --Mark Kedar. From jiteshs at marvell.com Thu Jul 9 08:54:35 2009 From: jiteshs at marvell.com (Jitesh Shah) Date: Thu, 9 Jul 2009 14:24:35 +0530 Subject: mock gid Message-ID: <1247129675.24105.9.camel@localhost.localdomain> I see some code in mock that picks up the mockuser uid/gid from the host machine. why is it so? I ask because recently, we came across some issues while building in koji where the builds failed with this : DEBUG util.py:280: Executing command: ['/usr/sbin/groupadd', '-g', '499', 'mockbuild'] DEBUG util.py:256: groupadd: GID 499 is not unique DEBUG util.py:319: Child returncode was: 4 (http://arm.koji.fedoraproject.org/koji/getfile?taskID=45343&name=root.log) GID 499 is already taken (in this case, by avahi). What is a good way to workaround this problem? Regards, Jitesh (PS: I am not sure whether this is the right place to ask mock-related questions. Let me know if I need to redirect it to the mock community) From msalter at redhat.com Thu Jul 9 12:50:38 2009 From: msalter at redhat.com (Mark Salter) Date: Thu, 09 Jul 2009 08:50:38 -0400 Subject: crossbuilding rpms with koji In-Reply-To: <25B60CDC2F704E4E9D88FFD52780CB4C04A505BDD7@SC-VEXCH1.marvell.com> References: <25B60CDC2F704E4E9D88FFD52780CB4C04A505BDD7@SC-VEXCH1.marvell.com> Message-ID: <1247143838.2512.58.camel@deneb.localdomain> On Wed, 2009-07-08 at 22:24 -0700, Kedar Sovani wrote: > IIUC you have pkgname.armv5tel.rpm? If so, how did you make rpm > to build those? I had to modify /etc/rpm/platform to fool rpm in > thinking it is building for armv5tel. Is there a cleaner way for > doing this? I'm pretty sure all I had to do was pass --target=armv5tel to rpmbuild. I had some missteps early on where some packages ended up building as native packages but were named armv5tel. It didn't matter that they were full of i386 binaries and rpm query would tell me the %{ARCH} was armv5tel. A quick experiment with a minimal specfile shows that rpmbuild seems perfectly happy to use any made up arch name you pass it. --Mark From giallu at gmail.com Sun Jul 12 23:38:31 2009 From: giallu at gmail.com (Gianluca Sforna) Date: Mon, 13 Jul 2009 01:38:31 +0200 Subject: Mock issue with ifarch BuildRequires Message-ID: I am trying to run the tests included in the BuildBot package during the RPM build, and one of the tests requires darcs, which is built in Fedora ExclusiveArch %{ix86} x86_64 ppc alpha. Now, I'm adding to buildbot's spec[1] file an ifarch like: %ifarch %{ix86} x86_64 ppc alpha # darcs ExclusiveArchs BuildRequires: darcs %endif but it seems darcs is never installed in the buildroot [2] am I just doing something stupid or there's a bug somewhere? [1] http://cvs.fedoraproject.org/viewvc/rpms/buildbot/devel/buildbot.spec?view=log [2] http://koji.fedoraproject.org/koji/getfile?taskID=1470380&name=root.log -- Gianluca Sforna http://morefedora.blogspot.com http://www.linkedin.com/in/gianlucasforna From jkeating at redhat.com Wed Jul 15 19:29:11 2009 From: jkeating at redhat.com (Jesse Keating) Date: Wed, 15 Jul 2009 12:29:11 -0700 Subject: mock gid In-Reply-To: <1247129675.24105.9.camel@localhost.localdomain> References: <1247129675.24105.9.camel@localhost.localdomain> Message-ID: <1247686151.3073.1192.camel@localhost.localdomain> On Thu, 2009-07-09 at 14:24 +0530, Jitesh Shah wrote: > I see some code in mock that picks up the mockuser uid/gid from the host > machine. why is it so? > > I ask because recently, we came across some issues while building in > koji where the builds failed with this : > DEBUG util.py:280: Executing command: ['/usr/sbin/groupadd', '-g', '499', 'mockbuild'] > DEBUG util.py:256: groupadd: GID 499 is not unique > DEBUG util.py:319: Child returncode was: 4 > (http://arm.koji.fedoraproject.org/koji/getfile?taskID=45343&name=root.log) > > GID 499 is already taken (in this case, by avahi). > What is a good way to workaround this problem? > > Regards, > Jitesh > > (PS: I am not sure whether this is the right place to ask mock-related > questions. Let me know if I need to redirect it to the mock community) > I do believe it picks the mock uid/gid from the host system so that the correct write permissions exist inside the chroot, particularly for doing things as non-root such as the rpm build. Perhaps we need to do the group addition step before we install the BuildRequirements. I assume that avahi picks a somewhat random UID when it installs itself? -- Jesse Keating Fedora -- Freedom? is a feature! identi.ca: http://identi.ca/jkeating -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From petersen at redhat.com Thu Jul 16 06:22:28 2009 From: petersen at redhat.com (Jens Petersen) Date: Thu, 16 Jul 2009 02:22:28 -0400 (EDT) Subject: [patch] hardcode SPECFILE In-Reply-To: <1277390851.790951247725044723.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> Message-ID: <9582207.791071247725348886.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com> A few times I have run into SPECFILE=$(firstword $(wildcard *.spec)) grabbing a different spec file in a pkg cvs dir than intended when doing local testbuilds. While unlikely I think it would be embarrassing if one day such an alternate spec somehow ended up in koji (eg via cvs-import.sh), so I would like to propose that we hardcode SPECFILE based on package NAME for all new packages with the attached patch. Jens -------------- next part -------------- A non-text attachment was scrubbed... Name: cvs-import.sh-specfile.patch Type: text/x-patch Size: 687 bytes Desc: not available URL: From sergio at sergiomb.no-ip.org Thu Jul 16 20:35:39 2009 From: sergio at sergiomb.no-ip.org (Sergio Monteiro Basto) Date: Thu, 16 Jul 2009 21:35:39 +0100 Subject: pungi recent bug Message-ID: <1247776539.7936.22.camel@segulix> Hi, I am trying http://sergiomb.no-ip.org/pungi/confs/buildiso-f11.sh with pungi-2.0.16-1.fc11 don't obey to less like: -wormux-0.8.2-5.fc11.i586 I saw on changelog: 2.0.14-1 - Fix package excludes in kickstart files and try pungi-2.0.13 , and voil? it works again. I check duplicates with my script: http://sergiomb.no-ip.org/pungi/confs/checkduplicateds Thanks, -- S?rgio M. B. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2192 bytes Desc: not available URL: From jkeating at redhat.com Thu Jul 16 21:44:33 2009 From: jkeating at redhat.com (Jesse Keating) Date: Thu, 16 Jul 2009 14:44:33 -0700 Subject: pungi recent bug In-Reply-To: <1247776539.7936.22.camel@segulix> References: <1247776539.7936.22.camel@segulix> Message-ID: <1247780673.3012.23.camel@localhost.localdomain> On Thu, 2009-07-16 at 21:35 +0100, Sergio Monteiro Basto wrote: > Hi, > I am trying http://sergiomb.no-ip.org/pungi/confs/buildiso-f11.sh > with pungi-2.0.16-1.fc11 don't obey to less like: > -wormux-0.8.2-5.fc11.i586 > > I saw on changelog: > 2.0.14-1 - Fix package excludes in kickstart files Pungi treats the -foo entries much like kickstart does now, in that it won't actively /select/ that package, but the package could still be brought in due to dependencies. Check your pungi logs to see when/where wormux is being brought in. -- Jesse Keating Fedora -- Freedom? is a feature! identi.ca: http://identi.ca/jkeating -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: From dennis at ausil.us Mon Jul 13 03:44:15 2009 From: dennis at ausil.us (Dennis Gilmore) Date: Sun, 12 Jul 2009 22:44:15 -0500 Subject: Mock issue with ifarch BuildRequires In-Reply-To: References: Message-ID: <200907122244.23306.dennis@ausil.us> Em Domingo 12 Julho 2009, ?s 06:38:31 pm, Gianluca Sforna escreveu: > I am trying to run the tests included in the BuildBot package during > the RPM build, and one of the tests requires darcs, which is built in > Fedora ExclusiveArch %{ix86} x86_64 ppc alpha. > Now, I'm adding to buildbot's spec[1] file an ifarch like: > > %ifarch %{ix86} x86_64 ppc alpha > # darcs ExclusiveArchs > BuildRequires: darcs > %endif > > but it seems darcs is never installed in the buildroot [2] > > am I just doing something stupid or there's a bug somewhere? > > [1] > http://cvs.fedoraproject.org/viewvc/rpms/buildbot/devel/buildbot.spec?view= >log [2] > http://koji.fedoraproject.org/koji/getfile?taskID=1470380&name=root.log What arech are you building the srpm on? if its not one of the ifarch'd arches it wont be in the BR's for the srpm. thats part of why we create the sroms on th ebuild arch in koji. Dennis -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: From giallu at gmail.com Fri Jul 17 14:32:40 2009 From: giallu at gmail.com (Gianluca Sforna) Date: Fri, 17 Jul 2009 16:32:40 +0200 Subject: Mock issue with ifarch BuildRequires In-Reply-To: <200907122244.23306.dennis@ausil.us> References: <200907122244.23306.dennis@ausil.us> Message-ID: On Mon, Jul 13, 2009 at 5:44 AM, Dennis Gilmore wrote: > What arech are you building the srpm on? ?if its not one of the ifarch'd > arches it wont be in the BR's for the srpm. ?thats part of why we create the > sroms on th ebuild arch in koji. I'm on x86_64, but i'm not usre I understand how what you stated above can affect me. -- Gianluca Sforna http://morefedora.blogspot.com http://www.linkedin.com/in/gianlucasforna From sergio at sergiomb.no-ip.org Sat Jul 18 22:46:06 2009 From: sergio at sergiomb.no-ip.org (Sergio Monteiro Basto) Date: Sat, 18 Jul 2009 23:46:06 +0100 Subject: pungi recent bug In-Reply-To: <1247780673.3012.23.camel@localhost.localdomain> References: <1247776539.7936.22.camel@segulix> <1247780673.3012.23.camel@localhost.localdomain> Message-ID: <1247957166.12466.18.camel@segulix> Hi, On Thu, 2009-07-16 at 14:44 -0700, Jesse Keating wrote: > On Thu, 2009-07-16 at 21:35 +0100, Sergio Monteiro Basto wrote: > > Hi, > > I am trying http://sergiomb.no-ip.org/pungi/confs/buildiso-f11.sh > > with pungi-2.0.16-1.fc11 don't obey to less like: > > -wormux-0.8.2-5.fc11.i586 > > > > I saw on changelog: > > 2.0.14-1 - Fix package excludes in kickstart files > > Pungi treats the -foo entries much like kickstart does now, in that it > won't actively /select/ that package, but the package could still be > brought in due to dependencies. Check your pungi logs to see when/where > wormux is being brought in. Well , when I pungi fedora11 with updates, many packages appears duplicated on dir Packages, and this is the root of the problem. For example, now, when I updated with latest updates, the dir packages contains: plplot-5.9.2-4.fc11.i586 plplot-5.9.4-1.fc11.i586 plplot-devel-5.9.2-4.fc11.i586 plplot-devel-5.9.4-1.fc11.i586 plplot-libs-5.9.2-4.fc11.i586 plplot-libs-5.9.4-1.fc11.i586 qmf-0.5.752600-5.fc11.i586 qmf-0.5.790661-1.fc11.i586 qpidc-0.5.752600-5.fc11.i586 qpidc-0.5.790661-1.fc11.i586 The updated and the original (from fedora11 release), to workaround this issues , I put -plplot-5.9.2-4.fc11.i586 on .ks, which btw stops to work in latest pungi. I don't think that the old version 5.9.2-4 is need it any more. So who I build a repo without duplicated ? that my goal. Thanks, -- S?rgio M. B. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2192 bytes Desc: not available URL: From sergio at sergiomb.no-ip.org Sat Jul 18 23:01:52 2009 From: sergio at sergiomb.no-ip.org (Sergio Monteiro Basto) Date: Sun, 19 Jul 2009 00:01:52 +0100 Subject: pungi recent bug In-Reply-To: <1247780673.3012.23.camel@localhost.localdomain> References: <1247776539.7936.22.camel@segulix> <1247780673.3012.23.camel@localhost.localdomain> Message-ID: <1247958112.12466.28.camel@segulix> BTW : my builds can be found on http://sergiomb.no-ip.org/pungi/11/ when I'm not building a new one :) On Thu, 2009-07-16 at 14:44 -0700, Jesse Keating wrote: > Check your pungi logs to see when/where > wormux is being brought in. Pungi:INFO: Checking deps of wormux-data.noarch Pungi:INFO: Added wormux.i586 for wormux-data.noarch Pungi:INFO: Checking deps of wormux.i586 Pungi:INFO: Added wormux-data.noarch for wormux.i586 Pungi:INFO: Added wormux-data.i586 for wormux.i586 Pungi:INFO: Checking deps of wormux-data.i586 Pungi:INFO: Added wormux.i586 for wormux-data.i586 Pungi:INFO: Checking deps of wormux.i586 and Pungi:INFO: Download list: [(...) u'wormux-data.i586', u'wormux-data.noarch', u'wormux.i586', u'wormux.i586', (...) ] That's the log I can get for wormux. Thanks, -- S?rgio M. B. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2192 bytes Desc: not available URL: From jkeating at j2solutions.net Sun Jul 19 03:11:56 2009 From: jkeating at j2solutions.net (Jesse Keating) Date: Sat, 18 Jul 2009 20:11:56 -0700 Subject: pungi recent bug In-Reply-To: <1247958112.12466.28.camel@segulix> References: <1247776539.7936.22.camel@segulix> <1247780673.3012.23.camel@localhost.localdomain> <1247958112.12466.28.camel@segulix> Message-ID: <485F2C4D-2B6F-4DBF-8DCA-3970381B7AA2@j2solutions.net> On Jul 18, 2009, at 16:01, Sergio Monteiro Basto wrote: > BTW : my builds can be found on > http://sergiomb.no-ip.org/pungi/11/ > when I'm not building a new one :) > > > On Thu, 2009-07-16 at 14:44 -0700, Jesse Keating wrote: >> Check your pungi logs to see when/where >> wormux is being brought in. > > Pungi:INFO: Checking deps of wormux-data.noarch > Pungi:INFO: Added wormux.i586 for wormux-data.noarch > Pungi:INFO: Checking deps of wormux.i586 > Pungi:INFO: Added wormux-data.noarch for wormux.i586 > Pungi:INFO: Added wormux-data.i586 for wormux.i586 > Pungi:INFO: Checking deps of wormux-data.i586 > Pungi:INFO: Added wormux.i586 for wormux-data.i586 > Pungi:INFO: Checking deps of wormux.i586 > > and Pungi:INFO: Download list: [(...) u'wormux-data.i586', > u'wormux-data.noarch', u'wormux.i586', u'wormux.i586', > (...) ] > That's the log I can get for wormux. > > Thanks, > > -- > S?rgio M. B. > -- > Fedora-buildsys-list mailing list > Fedora-buildsys-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-buildsys-list So you exclude wormux but not wormux-data? From jkeating at j2solutions.net Sun Jul 19 03:14:00 2009 From: jkeating at j2solutions.net (Jesse Keating) Date: Sat, 18 Jul 2009 20:14:00 -0700 Subject: pungi recent bug In-Reply-To: <1247957166.12466.18.camel@segulix> References: <1247776539.7936.22.camel@segulix> <1247780673.3012.23.camel@localhost.localdomain> <1247957166.12466.18.camel@segulix> Message-ID: On Jul 18, 2009, at 15:46, Sergio Monteiro Basto wrote: > Hi, > On Thu, 2009-07-16 at 14:44 -0700, Jesse Keating wrote: >> On Thu, 2009-07-16 at 21:35 +0100, Sergio Monteiro Basto wrote: >>> Hi, >>> I am trying http://sergiomb.no-ip.org/pungi/confs/buildiso-f11.sh >>> with pungi-2.0.16-1.fc11 don't obey to less like: >>> -wormux-0.8.2-5.fc11.i586 >>> >>> I saw on changelog: >>> 2.0.14-1 - Fix package excludes in kickstart files >> >> Pungi treats the -foo entries much like kickstart does now, in that >> it >> won't actively /select/ that package, but the package could still be >> brought in due to dependencies. Check your pungi logs to see when/ >> where >> wormux is being brought in. > > Well , when I pungi fedora11 with updates, many packages appears > duplicated on dir Packages, and this is the root of the problem. > For example, now, when I updated with latest updates, the dir packages > contains: > > plplot-5.9.2-4.fc11.i586 > plplot-5.9.4-1.fc11.i586 > plplot-devel-5.9.2-4.fc11.i586 > plplot-devel-5.9.4-1.fc11.i586 > plplot-libs-5.9.2-4.fc11.i586 > plplot-libs-5.9.4-1.fc11.i586 > qmf-0.5.752600-5.fc11.i586 > qmf-0.5.790661-1.fc11.i586 > qpidc-0.5.752600-5.fc11.i586 > qpidc-0.5.790661-1.fc11.i586 > > The updated and the original (from fedora11 release), to workaround > this > issues , I put -plplot-5.9.2-4.fc11.i586 on .ks, which btw stops to > work > in latest pungi. > I don't think that the old version 5.9.2-4 is need it any more. > So who I build a repo without duplicated ? that my goal. > > Thanks, > -- > S?rgio M. B. > -- > Fedora-buildsys-list mailing list > Fedora-buildsys-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-buildsys-list Hrm that may be a bug. Pungi is only supposed to grab the latest version of a package but since I mostly test on rawhide I may have misses this bug -- Jes From sergio at sergiomb.no-ip.org Sun Jul 19 09:57:06 2009 From: sergio at sergiomb.no-ip.org (Sergio Monteiro Basto) Date: Sun, 19 Jul 2009 10:57:06 +0100 Subject: pungi recent bug In-Reply-To: <485F2C4D-2B6F-4DBF-8DCA-3970381B7AA2@j2solutions.net> References: <1247776539.7936.22.camel@segulix> <1247780673.3012.23.camel@localhost.localdomain> <1247958112.12466.28.camel@segulix> <485F2C4D-2B6F-4DBF-8DCA-3970381B7AA2@j2solutions.net> Message-ID: <1247997426.4880.17.camel@segulix> On Sat, 2009-07-18 at 20:11 -0700, Jesse Keating wrote: > > On Jul 18, 2009, at 16:01, Sergio Monteiro Basto > wrote: > > > BTW : my builds can be found on > > http://sergiomb.no-ip.org/pungi/11/ > > when I'm not building a new one :) > > > > > > On Thu, 2009-07-16 at 14:44 -0700, Jesse Keating wrote: > >> Check your pungi logs to see when/where > >> wormux is being brought in. > > > > Pungi:INFO: Checking deps of wormux-data.noarch > > Pungi:INFO: Added wormux.i586 for wormux-data.noarch > > Pungi:INFO: Checking deps of wormux.i586 > > Pungi:INFO: Added wormux-data.noarch for wormux.i586 > > Pungi:INFO: Added wormux-data.i586 for wormux.i586 > > Pungi:INFO: Checking deps of wormux-data.i586 > > Pungi:INFO: Added wormux.i586 for wormux-data.i586 > > Pungi:INFO: Checking deps of wormux.i586 > > > > and Pungi:INFO: Download list: [(...) u'wormux-data.i586', > > u'wormux-data.noarch', u'wormux.i586', u'wormux.i586', > > (...) ] > > That's the log I can get for wormux. > > > > So you exclude wormux but not wormux-data? yes, to just exclude wormux, I think just appears wormux in duplicates and also is enough to solve the duplicated. Thanks, -- S?rgio M. B. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2192 bytes Desc: not available URL: From bugs.michael at gmx.net Wed Jul 22 20:28:45 2009 From: bugs.michael at gmx.net (Michael Schwendt) Date: Wed, 22 Jul 2009 22:28:45 +0200 Subject: Mock issue with ifarch BuildRequires In-Reply-To: References: <200907122244.23306.dennis@ausil.us> Message-ID: <20090722222845.3d8dd31d@faldor> On Fri, 17 Jul 2009 16:32:40 +0200, Gianluca wrote: > On Mon, Jul 13, 2009 at 5:44 AM, Dennis Gilmore wrote: > > What arech are you building the srpm on? ?if its not one of the ifarch'd > > arches it wont be in the BR's for the srpm. ?thats part of why we create the > > sroms on th ebuild arch in koji. > > I'm on x86_64, but i'm not usre I understand how what you stated above > can affect me. PEBKAC Theory: A spec file's BuildRequires become the src.rpm's Requires. So, typically, one rebuilds the src.rpm from the spec file per target build architecture prior to resolving the build deps for that target-specific src.rpm. However, your package is "BuildArch: noarch", so the %ifarch never holds true when processing the src.rpm's Requires for target "noarch". From giallu at gmail.com Thu Jul 23 07:31:04 2009 From: giallu at gmail.com (Gianluca Sforna) Date: Thu, 23 Jul 2009 09:31:04 +0200 Subject: Mock issue with ifarch BuildRequires In-Reply-To: <20090722222845.3d8dd31d@faldor> References: <200907122244.23306.dennis@ausil.us> <20090722222845.3d8dd31d@faldor> Message-ID: On Wed, Jul 22, 2009 at 10:28 PM, Michael Schwendt wrote: > Theory: A spec file's BuildRequires become the src.rpm's Requires. So, > typically, one rebuilds the src.rpm from the spec file per target build > architecture prior to resolving the build deps for that target-specific > src.rpm. > > However, your package is "BuildArch: noarch", so the %ifarch never > holds true when processing the src.rpm's Requires for target "noarch". much clearer now... thank you very much -- Gianluca Sforna http://morefedora.blogspot.com http://www.linkedin.com/in/gianlucasforna From julian.fedoralists at googlemail.com Thu Jul 23 18:44:22 2009 From: julian.fedoralists at googlemail.com (Julian Aloofi) Date: Thu, 23 Jul 2009 20:44:22 +0200 Subject: Creating a custom distro with pungi Message-ID: <1248374662.19980.4.camel@Julians-Notebook> I'm currently trying to create a custom distro with pungi. More precisely, I've been using rpm -qa --qf="%{n}\n" to create a list of packages currently installed on my system, added the needed repos (rpmfusion-free, rpmfusion-free-updates and adobe-linux-i386) and built a kickstart file out of this. Now I have some questions, and it's pretty hard to find any documentation about that, so I thought I'd just ask on this list. 1.)How can I specify which packages should be installed by default? The packages in my kickstart file get added, but don't get installed by default. I figured out that it had something to do with some xml files, but what exactly do I have to do to, for example, install all packages from the kickstart file by default? I'm not so comfortable with anaconda and repo files, so please mention file locations if I have to edit some files. 2.)How can I replace fedora-logos, fedora-release and fedora-release-notes with generic-logos, generic-release and generic-release-notes? I tried to exclude them from repos in the kickstart file and excluding them from the package manifest, however it didn't work. Thanks in advance, Julian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: