March 2008 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] what does blocked mean?
by John Calcote 27 Mar '08

27 Mar '08

Hi list, I've seen this error more than once - almost always on the opensuse factory repo: i586 | blocked | autoconf, automake, binutils, bison, bzip2, doxygen, flex, gcc, gcc43, gettext-runtime, glibc, gmp, libgomp43, libmpfr1, libopenssl-devel, libopenssl0_9_8, libpng12-0, libtool, ncurses, openssl-certs, perl, rpm, zlib, zlib-devel Anyone know what it means? Am I doing something wrong, or is the system in a maintenance mode or something? Thanks! John --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] osc build
by Dirk Stoecker 25 Mar '08

25 Mar '08

On Wed, 30 Jan 2008, Marcus Rueckert wrote: > On 2008-01-30 08:46:56 +0100, Dirk Stoecker wrote: > > osc build does not clear the build-environment, when the plattform is > > changed. So when I switch from 10.2 to 10.3, some packager get deinstalled > > and installed and the result is a (usually not working) mixed setup. > > in the general section of ~/.oscrc add: > build-root: /srv/osc/build-root-%(repo)s > > then you get one build chroot per repository. > > build-root: /srv/osc/build-root-%(repo)s-%(arch)s > > is also possible. > > now you just have to watch the diskusage.:) Workarounds are a lot. But the problem is not fixed by these. Under special conditions this bug may cause hard to track build errors, thus I reported it. Saving a "This build environment is xxx"-file somewhere in the build-dir should fix the problem. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 10

[opensuse-buildservice] chown issues
by John Calcote 25 Mar '08

25 Mar '08

I've got a package with this code snippet in one of my Makefiles: install-exec-hook: $(install_sh) -d $(DESTDIR)$(sysrundir) if [ `id -u` -eq 0 ]; then \ chown $(dnx_user):$(dnx_group) $(DESTDIR)$(sysrundir); \ fi Yes, this is actually an automake file, but that's irrelevant to the issue at hand here. I'm trying in this target to install a directory (usually "/var/run/dnx"), and it's generally the case that this directory belongs to my package. Because my daemon runs as it's own user, $(dnx_user), I want to ensure this user can create files in this directory, so I want to "chown" the directory. When I install my package from the command line, it all works fine because I chown as long as I'm running as root, but not if I'm running as a user (can't chown anyway). When I do a staged installation using DESTDIR=${BUILDROOT} on the make command line (inside my spec file), it also works fine, because I don't build my rpm as root. When I build for ubuntu or debian, however, it appears that these servers build their packages as root, so the build fails because the package build is trying to chown something in the BUILDROOT. Here's what I did to fix it: install-exec-hook: $(install_sh) -d $(DESTDIR)$(sysrundir) if [ `id -u` -eq 0 ] && [ -z ${DESTDIR} ]; then \ chown $(dnx_user):$(dnx_group) $(DESTDIR)$(sysrundir); \ fi I just added a check for an empty DESTDIR - no DESTDIR, no staged installation. It seems to work. My question: Is this a good approach, or am I TOTALLY off base? :) Thanks in advance, John --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 3

[opensuse-buildservice] gpsd in Education:Desktop
by Dirk Stoecker 24 Mar '08

24 Mar '08

Hello, is there a special reason, why gpsd now is also in Education:Desktop? Isn't Application:Geo enough? I copied the changes from Education:Desktop to Application:Geo. Using a patch against factory instead of file copying. Please could you continue development there? Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1

[opensuse-buildservice] Fedora 6 x86_64
by Dirk Stoecker 23 Mar '08

23 Mar '08

Hello, how can https://build.opensuse.org/package/live_build_log?arch=x86_64&package=merka… suceed? Does Fedora 6 really have "installing qt4-4.3.2-1.fc6" as default. Seems to me an updated repository. Fedora 7 fails as well as Fedora 6 i586 due to older qt packages. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Re: [opensuse-project] How should we inform packagers about new upstreamversions?
by Vincent Untz 23 Mar '08

23 Mar '08

Le mercredi 27 février 2008 à 20:15 +0100, Pascal Bleser a écrit : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Christian Morales Vega wrote: > > Sometimes do you find packages in the OBS that are outdated. You never > > know why, perhaps the packager doesn't knows about the new upstream > > version and perhaps he knows but is just busy. > > Up to now when I found such a case I reported it like an "Enhancement" > > bug in bugzilla. But some packagers think bugzilla isn't the correct > > place for such a thing. > > > > If the packager doesn't knows about the new version he can leave the > > package outdated for a long time. So would be good that, at some time, > > if an user finds the problem he reports it. But, how should be > > reported? There is any feature planned in the OBS to help with this? > > What other distros do? > > A very good point. > > Personally, I think Bugzilla is the best place to report it. > It also makes it much easier to track the status. I think another approach would make sense: users could report it on software.opensuse.org since that's where they look for software. Then we just need a way to mail the relevant packagers about this "new upstream" report. Vincent -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

6 10

[opensuse-buildservice] workers on walkout?
by Dominique Leuenberger 21 Mar '08

21 Mar '08

Hi, I was just wondering what happened to all the workers? At the moment I can see there are about 48 running (0 waiting) and out of the 48 running, I would see some of them at least are not that busy. All the entries from build13 seem to have stalled (most no log available).. I guess this machine refuses to work on Friday in general :) Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4

[opensuse-buildservice] Expansion error: nothing provides libpfm-devel
by Bernhard Walle 20 Mar '08

20 Mar '08

Hi, $ cd openSUSE:Factory/libpfm $ osc results standard i586 succeeded standard x86_64 succeeded but $ cd ../pfmon $ osc results standard i586 succeeded standard x86_64 expansion error: nothing provides libpfm-devel I don't get where the problem is. Can somebody enlighten me? Bernhard --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] gpg failed to import key
by Roberto Mannai 19 Mar '08

19 Mar '08

Hi all After packaged my RPM, I was going to test it. I ran: rpm --import /home/Roberto/openSUSE-Build-Service.asc Then, using SMART, I was able to add and refresh the channel; but when I went to *install* my package, a popup warned me: "gpg failed to import key". Standard/Error output printed this message: linux-jad:~ # smart --gui warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 71e0b02a gpg: requesting key 71E0B02A from hkp server subkeys.pgp.net gpg: no valid OpenPGP data found. gpg: Total number processed: 0 I'm using the root user, to avoid any headache (or at least to decrease it :)). Any idea? Must I generate any key? Ciao Roberto --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4

[opensuse-buildservice] gpg failed to import key
by Roberto Mannai 19 Mar '08

19 Mar '08

Sure I can, but I'm not very expert on this OBS stuff :) As much as I've just learned, I should insert that row only in the SMART section (and not in YAST or zypper sections). Could you confirm? On Wed, Mar 19, 2008 at 11:52 AM, Andreas Jaeger <aj(a)suse.de> wrote: > It's a wiki - could you change the page to reflect what you just > learned, please? > > > > > > > Generally speaking, SMART (or YAST) should download automatically the > > key, shouldn't it? > > YaST does if you once you add the repository, > > Andreas > -- > Andreas Jaeger, Director Platform/openSUSE, aj(a)suse.de > SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) > Maxfeldstr. 5, 90409 Nürnberg, Germany > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 > --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0