July 2008 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] GCJ java components?
by John Calcote 14 Jul '08

14 Jul '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've got a package that uses some java in the build process (openxdas). Java is optional, and if javac (gcj -C), jar or javadoc utilities are not found, then the java build is skipped. I'm currently using gcc-java in BuildRequires. That get's me gcj -C in my JAVA env var, but I don't know what to use that gets me corresponding jar and javadoc utilities. Recently, I've discovered the java-1_5_0-gcj-compat-devel package, and added it to my BuildRequires line. That get's me there for opensuse platforms, but it apparently doesn't exist on any others. Isn't there an all-in-one solution for Java? Thanks, John -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkh7gjIACgkQdcgqmRY/OH/oOQCfbITbqdV3/h4RrcTL3MxR2lfY 5g4AnifeoXZKwm6BLLEG6PSdvBIP28gG =Q2N9 -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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] libexpat-devel not found on CentOS and Fedora_8
by John Calcote 14 Jul '08

14 Jul '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Can anyone tell me what the compatible package is for libexpat-devel on CentOS 5 and Fedora 8? I'm getting expansion errors on this package for these platforms. Also, since I probably have to use a conditional for these packages on these platforms, can someone tell me how to tell them from the others in my spec file? Thanks, John -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkh7gO4ACgkQdcgqmRY/OH/KpQCfa3I9x2D9A2xYe3feeiwAHWlH Hd0Aniv43834GxYwWai+sikqiYyz12mh =lmyk -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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] openSUSE Build Service Trust concept
by Marko Jung 14 Jul '08

14 Jul '08

Hi, after a lot of inspiring conversations with co-workers at SUSE and friends from the open source community I finally published a first abstract draft how we could add some metrics to openSUSE build service to create a trust system. http://en.opensuse.org/Build_Service/Concepts/Trust This article does not go much into particular neither explains concrete implementation details. Main target of this proposal is to have a basis for discussion. The article even goes beyond the focus on trust and proposes some additional metrics to support openSUSE users in their decision from which repositories they should obtain their software packages. Within the next weeks I would like to discuss this with you. So if you are interested in this topic please contact me. Any suggestions, feedback or critics are highly appreciated. Cheers! Marko --------------------------------------------------------------------- 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] Using svn for source instead of uploading tarball
by Kevin James 14 Jul '08

14 Jul '08

Hi all, I'm still pretty new to the build service, so I was looking around the wiki documentation for some kind of best practice on managing source code - it's not a problem yet as noone is using my package, but I'm trying to find out now how to deal with stable versus unstable somewhere down the line - so if I have version 1.3 as a stable version, and then working on 1.4 which may or may not build.. Should I only do local builds of the 1.4 until it's released, then upload to the build service? I'm also trying to figure out how to deal with a source code repository - currently I have a shell script which tars up my source directory and then commits it through osc, but I found this page on the wiki: http://en.opensuse.org/Build_Service/Workflows under "Edit Packages" near the bottom, it says add sources (http source, svn/cvs source) Does this mean I can get the build service to grab the source straight from my svn server? Cheers, KEv. -- Kevin James Applied Technology Senior Strategist Novell Global Enablement ------------------------ Novell, Inc. http://www.novell.com --------------------------------------------------------------------- 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] ERROR Your flag configuration seems to be too complex to be saved through this interface. Please use OSC
by Dirk Stöcker 14 Jul '08

14 Jul '08

Hello, could the webinterface please be fixed, so this warning comes no longer when repositories have been removed. Every year the webinterface gets unusable to change configuration, because a repository has been removed. 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] Mandriva 2006 "Add Repo." error: unable to walk on path
by Mark V 14 Jul '08

14 Jul '08

Hi Group, Using the OBS web client, when I try to: Add Repository>> Mandriva 2006 I get the following error: Error Details: Errorcode: package_save_error Message: error saving project: unable to walk on path 'Mandriva:2006/standard' Should I report this sort fo error via bugzilla or is this list OK? Regards Mark --------------------------------------------------------------------- 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] opensuse11 repository for project filesystems
by Biber 13 Jul '08

13 Jul '08

Hi, I know it's friday evening...but could someone add the opensuse11 repository to the project filesystems ? I've been already personally asked by mail where the openafs-client for the new version is ;-) Cheers, Christof --------------------------------------------------------------------- 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] Shared spec vs duplicated spec's
by Mark V 11 Jul '08

11 Jul '08

Hi Group, I raised this on the IRC channel so apologies if you've seen this. I have a project's src.rpm that I'd like to move onto the OBS, and this has raised some issues.... The current src.rpm uses lots of --build "option n" switches. Some of these are accommodated by OBS since they are distro specific builds. Others however relate to building different components. My Question is how to 'map' this to OBS? Do I setup one package per 'component', and so have many duplicates of the src.spec file? Or, is it possible for several projects to share a common spec file and build specific components by passing in some parameters? Appreciate any suggestions or better yet if you can point to a project that uses such a 'shared-spec' setup :) Regards Mark --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 5

[opensuse-buildservice] Build fails with rpmlint crashing (again?)
by Dominik George 11 Jul '08

11 Jul '08

Hallo list, several weeks ago, I had problems getting a package built because rpmlint crashed. I asked for that on IRC and was told that it was a bug that the team was working on. I just tried again and noticed that the build still fails at the same point, rendering me unable to get the package compiled. On IRC, I was told that the rpmlint bug was fixed some time ago. The project in question is pidgin-lastfm in Home::Natureshadow (linked in GNOME::Community). Any ideas? Regards, Nik --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] rpmlint and older suse_version checks
by Wolfgang Rosenauer 11 Jul '08

11 Jul '08

Hi, could we stop moaning about old %suse_version checks as long as SLES9 is still supported? Please stop the warnings for stuff down to 910 since I'm not going to rewrite my working specfiles just for SLES9. Wolfgang --------------------------------------------------------------------- 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] Clarification of step 3 in the OBS tutorial
by Mark V 11 Jul '08

11 Jul '08

Hi Group, I'm new to package and the OBS so am working through the tutorial. I might be dim but it took me a while to work this out: Step one and two relate to the package page of the web client.... For step three you need to go back to the user's OBS home page! I'm not sure what the convetion is for these changes.... in the meantime I've edited step three of the tutorial. http://en.opensuse.org/Build_Service/Tutorial#Step_Three_-_Add_Repositories HTH? Mark --------------------------------------------------------------------- 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] _link or _aggregate with regular build
by Archie Cobbs 10 Jul '08

10 Jul '08

I noticed that if an OBS package has an _aggregate file AND a normal spec file, then the spec file is ignored. Any reason why you can't do a normal build and an _aggregate link together at the same time in the same package? This would seem like a logical thing to do when your goal is simply to aggregate the "normal" RPM's requirements into your project, so your repository is transitively closed. -Archie -- Archie L. Cobbs --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 6

[opensuse-buildservice] osc 0.105
by Peter Poeml 10 Jul '08

10 Jul '08

Hi, I released osc 0.105 last night, which incorporates the last two or three weeks of work. Mostly work done by Marcus and Dirk. I posted about it here: http://lizards.opensuse.org/2008/07/10/new-osc-package-released/ You'll find a summarized list of changes. Thanks, Peter -- Contact: admin(a)opensuse.org (a.k.a. ftpadmin(a)suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development

5 11

[opensuse-buildservice] How can i setup package signing on local obs?
by Carsten Schoene 10 Jul '08

10 Jul '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, can someone explain how to setup the signd & sign program on a local bs setup? I got the daemon running, and the sign program connects but than hangs, while the signd starts some subprocesses and nothing happens. I'm not sure where to place the key files used for signing, maybe someone can bring some light into the darkness ;) attached, a processlist and log entrys of signd thanks Carsten -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHRuae6NfbfHY52TsRAgubAJwNh/AXwCe6/XCVp2dPix/B4l0BdwCeLVVf z3ee5EhaDBaeVIcGeWdVpDI= =X06F -----END PGP SIGNATURE----- obsrun 25247 0.0 0.4 12632 9284 ? S 10:57 0:00 /usr/bin/perl -w ./bs_repserver obsrun 25248 0.0 0.0 1820 560 ? S 10:57 0:00 /srv/obs/sign/sign -r /srv/obs/jobs/x86_64/multimedia::SLE_10::portaudio18-6337f29c4f0b6a49147cef12bb42056f:dir/portau obsrun 25251 0.0 0.4 12632 9284 ? S 10:57 0:00 /usr/bin/perl -w ./bs_repserver obsrun 25252 0.0 0.0 1816 552 ? S 10:57 0:00 /srv/obs/sign/sign -r /srv/obs/jobs/i586/multimedia::SLE_10::portaudio18-6337f29c4f0b6a49147cef12bb42056f:dir/portaudi root 28395 0.0 0.1 9348 2816 ? Ss 13:34 0:01 sshd: root@pts/0 root 28397 0.0 0.0 4276 2044 pts/0 Ss 13:34 0:00 -bash postfix 31139 0.0 0.0 5692 1716 ? S 14:51 0:00 pickup -l -t fifo -u root 31790 0.0 0.0 2480 856 pts/0 R+ 15:26 0:00 ps axu obs-web:~/bin # ps axu|grep sign root 5981 0.0 0.1 4868 3196 ? Ss Nov21 0:00 /usr/bin/perl ./signd obsrun 6328 0.0 0.0 1820 560 ? S Nov21 0:00 /srv/obs/sign/sign -r /srv/obs/jobs/i586/internetx:mysql5::SLE_10::libmemcached-3baa823c6ef50fd1588d72fdcb28e683:dir/libmemcached-0.9-5.7.i586.rpm root 6329 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6330 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6331 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6332 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6333 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6334 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6335 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6336 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6337 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6338 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd root 6340 0.0 0.1 4868 2456 ? S Nov21 0:00 /usr/bin/perl ./signd obsrun 25248 0.0 0.0 1820 560 ? S 10:57 0:00 /srv/obs/sign/sign -r /srv/obs/jobs/x86_64/multimedia::SLE_10::portaudio18-6337f29c4f0b6a49147cef12bb42056f:dir/portaudio18-devel-18.1-1.1.x86_64.rpm obsrun 25252 0.0 0.0 1816 552 ? S 10:57 0:00 /srv/obs/sign/sign -r /srv/obs/jobs/i586/multimedia::SLE_10::portaudio18-6337f29c4f0b6a49147cef12bb42056f:dir/portaudio18-devel-18.1-1.1.i586.rpm obs-web:~/bin # cat /srv/obs/log/signd.log 2007-11-21 17:04:21: signproxy started 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2 2007-11-21 17:08:02: <ip-removed>: sign buildservice@<domain-removed> 6657796b8a7aac3228df34447f8d5f48a9514a93@00474457e2 df4d4ac23bb2662ac5d550b4de263a4c09a67317@00474457e2

5 12

[opensuse-buildservice] mirrors not in sync
by Christian 10 Jul '08

10 Jul '08

Hi, repoview not listed on Filename: repositories/openSUSE:/Tools/SLE_10/openSUSE:Tools.repo Client IP address: 213.146.121.138 Found 8 mirrors: 3 country, 2 region, 2 elsewhere Mirrors in the same country (DE): http://widehat.opensuse.org/repositories/openSUSE:/Tools/SLE_10/openSUSE:To… (score 100) http://ftp5.gwdg.de/pub/opensuse/repositories/openSUSE:/Tools/SLE_10/openSU… (score 100) Kind regards Chris --------------------------------------------------------------------- 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] Status or change of all Suse repo.
by Petit Eric 10 Jul '08

10 Jul '08

Hi I use OBS web interface to build csharp-obexftp rpm, with obexftp 0.22, i build all distro with success, now with the new obexftp release, 0.23, i just change the version number and rpm date/coment in the spec file, all are build with success expect for all Suse distro. I had try to google the problem and most often time, it is a corupted rpm problem (requist) or phyton devel pckg, or gcc problem. Something has changing in Suse VM images ? The full output of the build is here : http://monoport.com/29647 For user who have a OBS account, project is here : https://build.opensuse.org/package/show?package=csharp-obexftp&project=home… On the project page we see all 0.23 success and 0.22 success with fail for 0.23. Any help or answer is really welcome, thank's -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. --------------------------------------------------------------------------- Few people are done for independence, it is the privilege of the powerful ones. --------------------------------------------------------------------------- No key was wounded during the drafting of this message. --------------------------------------------------------------------- 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] kdesvn 0.14.1 incompatible with svn 1.5.0
by Philippe Andersson 10 Jul '08

10 Jul '08

Hello list, I installed the following RPM offered on the BuildService: - kdesvn-0.14.1-8.1.x86_64.rpm - kdesvn-kiosvn-0.14.1-8.1.x86_64.rpm Unfortunately, this version of kdesvn is broken and crashes with a SIGSEGV when you try and access a working copy created with the svn 1.5.0 client with it. According to the kdesvn author, this problem has been fixed in kdesvn 0.14.4. To quote him: > In latest version of kdesvn (0.14.4) this problem is fixed (misuse of > subversion lib) but I didn't build it for opensuse this moment. Could you please consider building new RPMs for version 0.14.4 ? (I'm interested in x86_64 builds for OpenSuSE 10.3, if this matters). TIA Cheers. Bye. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan(a)iba-group.com <http://www.iba-worldwide.com> The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.

3 4

[opensuse-buildservice] Missing package repoview on SLE10 required by obs 1.0
by Carsten Hoeger 09 Jul '08

09 Jul '08

Hi, when I try to do a fresh install of obs 1.0, I get the following error: #### YaST2 conflicts list - generated 2008-06-28 03:49:31 #### obs-server-1.0.0-4.1.noarch[20080628-031724] kann aufgrund fehlender Abh344ngigkeiten nicht installiert werden Es sind keine installierbaren Anbieter von repoview verf374gbar f374r obs-server-1.0.0-4.1.noarch[20080628-031724] Konfliktl366sung: ( ) obs-server nicht installieren ( ) Anforderung wird hier ignoriert #### YaST2 conflicts list END ### I have all repos integrated as described in http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial/SL… Where to get the missing package repoview? -- With best regards, Carsten Hoeger

3 2

[opensuse-buildservice] Using OSC to set package flags
by Kevin James 09 Jul '08

09 Jul '08

Hi all, I've linked a package (tomboy) from the openSuSE 11:0 project, in order to try building it with a patch that may fix a bug I entered in bugzilla. I was clicking on the package flags to disable the SLE_10 build of my package (only testing with openSuSE 11.0 for this package), and I accidentally clicked in the wrong place. What I wanted was everything in the table to be default, except "SLE_10/All Arch." which would be disabled. When I try and change anything there now I get the message ERROR: Your flag configuration seems to be too complex to be saved through this interface. Please use OSC. However, I can't find any information on how to use OSC to fix these flags. Can anyone help out? Cheers, KEv. -- Kevin James Applied Technology Senior Strategist Novell Global Enablement ------------------------ Novell, Inc. http://www.novell.com --------------------------------------------------------------------- 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] osc importsrcpkg - _rpm.error
by Christian 08 Jul '08

08 Jul '08

Hi, can not import src package. admin@atlas:~/MyObs/SIT:perl> osc importsrcpkg /srv/ftp/pub/sles10/extras/rpm/src/perl-IO-Socket-INET6-2.51-1.SIT.src.rpm warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 55f4b686 Traceback (most recent call last): File "/usr/bin/osc", line 12, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.5/site-packages/osc/babysitter.py", line 33, in run return prg.main() File "/usr/lib/python2.5/site-packages/osc/cmdln.py", line 256, in main return self.cmd(args) File "/usr/lib/python2.5/site-packages/osc/cmdln.py", line 279, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.5/site-packages/osc/cmdln.py", line 395, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.5/site-packages/osc/cmdln.py", line 1070, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.5/site-packages/osc/commandline.py", line 2057, in do_importsrcpkg rpm_data = data_from_rpm(srpm, 'Name:', 'Summary:', '%description') File "/usr/lib/python2.5/site-packages/osc/core.py", line 3089, in data_from_rpm header = ts.hdrFromFdno(file.fileno()) _rpm.error: public key not available where should this public key be placed ? Thanks Chris --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] Aggregating from non-standard repository name
by Archie Cobbs 08 Jul '08

08 Jul '08

If you look at the status of the voiceglue package in the network:telephony project on openSUSE_Factory, you will see the build failed because "missing repositories: devel:languages:perl/openSUSE_Factory": https://build.opensuse.org/package/show?package=voiceglue&project=network%3… Here's why.... This RPM needs perl-ExtUtils-CBuilder to build, which is provided by project devel:languages:perl. So it contains an _aggregate: <aggregatelist> <aggregate project="devel:languages:perl"> <package>perl-ExtUtils-CBuilder</package> </aggregate> ... </aggregatelist> But for some reason the "devel:languages:perl" names their factory repository "SUSE_Linux_Factory" instead of "openSUSE_Factory". My questions are: (a) How do I tell the OBS to look in "openSUSE_Factory" instead of "SUSE_Linux_Factory"? (b) Why in the world is that project using a non-standard name? Thanks, -Archie -- Archie L. Cobbs --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] Aggregating from non-standard repository name
by Archie Cobbs 08 Jul '08

08 Jul '08

Marcus wrote: > Btw: why don't you directly build against this repository? This would avoid > package duplicates on the mirrors. Because I was told to... see below. Clearly there is some confusion or disagreement on whether it is better to add a repository to your project or aggregate in order to make BuildRequires RPMs available. Maybe the collective wisdom of this list can come up with a definitive "best practice" here? Thanks, -Archie ---------- Forwarded message ---------- From: Peter Nixon <listuser(a)peternixon.net> Date: Fri, May 23, 2008 at 11:43 AM Subject: Re: Meta-data change for network:telephony To: Archie Cobbs <archie(a)dellroad.org> Cc: max(a)novell.com, mrueckert(a)novell.com, hvogel(a)novell.com, richard.bos(a)xs4all.nl, lurch(a)gmx.li, opensuse.org(a)jerris.com, pvanveen84(a)hotmail.com Archie You are not irritating.. I asked all these questions and more to Darix (mrueckert) and he patiently answered them :-) When you put another project as a dependency of your project in the metadata it will allow your packages to build, but then when someone tries to use your repo to install your package those dependencies will not be supplied if they are needed as "Requires" forcing the user to go off in search of those dependencies too. When you "link" a particular package into your project it is rebuilt which takes up resources on the Build Service but is usefull if you want one of IT'S dependencies to be supplied by a package in your project without touching its spec, or if you want to build for a target which is not enable in it's home project. Once built the package is uploaded to the mirrors which also takes up mirror resources, and it also will have a different build version number which means that you may (or may not) randomly upgrade existing packages of the same name on your users system.. When you "aggregate" a particular package into your project it is not rebuilt, but rather copied directly from its home project. It keeps the same version number, so when it is uploaded to mirrors it does take up resources on them but it will not replace the same package if already installed on a users system (from the parent project). This is the preferred and cleanest way of sucking in a few extra dependencies to your project. I hope that makes things clearer. Regards Peter On Fri 23 May 2008, Archie Cobbs wrote: > On Fri, May 23, 2008 at 2:17 AM, Peter Nixon <listuser(a)peternixon.net> wrote: > > > > It would be much better if you simply aggregated the packages you > > > > require rather than linking in extra entire projects. Look at > > > > the "freeradius-client" package for an example. > > Got it, looks easy. > > What follows is a separate question, feel free to ignore if I'm > starting to get irritating... > > The goal here is simply to have certain RPMs that exist in other > projects (but not in standard SuSE) available as Build-Requires. > > As I understand it, aggregating is akin to copying in a package from > another project into your project. When you aggregate another package > X from project A into project B, then when you search for "X" on > software.opensuse.org, you get a match for "project A package X" and > also "project B package X", and OBS is building package X twice, once > in each project, producing two separate downloadable RPMs. > > On the other hand, I thought that adding another project to your > project (via "osc meta -a PRJ") simply made the RPMs in that other > project available to your project (e.g. for Build-Requires, etc). > I.e., it did the equivalent of "zypper addrepo otherproject" to your > project. The result is that there is no redundant building of any RPM > twice, in contrast to linking/aggregating. > > It to me seems like (since I don't need to modify these RPMs) that the > second option is more sensible than the first. > > Obviously, there is some other cost to the second option that I'm > unaware of. Can you explain what it is? > > Thanks, > -Archie > > -- > Archie L. Cobbs -- Peter Nixon http://peternixon.net/ -- Archie L. Cobbs --------------------------------------------------------------------- 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] eclipse-bs status report, week 27
by Michal Marek 08 Jul '08

08 Jul '08

(sorry for the late report, it's my fault, not long's) [GREEN] - connection wizard to select api server and set user:pass, reads and writes this info from/to .oscrc - dialog to set some more .oscrc options [OUTLOOK] - start writing code for browsing projects / packages --------------------------------------------------------------------- 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] fedora-release in default installs
by Chris Frey 07 Jul '08

07 Jul '08

Hi, Would it be possible to include the fedora-release package in the Fedora repos by default? This would include the /etc/rpm/macros.dist file, which includes the macros %fedora and %fc9 and %fc8. This package is usually installed automatically when installing Fedora through the usual process. It would make it possible to write spec files that build on multiple distros, both inside and outside the Opensuse Build Service. The %fedora_version macro available on OBS is not available on a regular Fedora9 install. Thanks, - Chris --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] obs-api-0.9.99-3.1.noarch.rpm missing files /srv/www/docs !!!
by Christian 07 Jul '08

07 Jul '08

Hi, there are missing files inside "obs-api-0.9.99-3.1.noarch.rpm". complete dir "/srv/www/docs" is missing. Kind regards Chris --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5