March 2009 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Release tag in BuildService
by Michal Vyskocil 13 Mar '09

13 Mar '09

Hi, I'd like to ask how is the Release Tag generated in a BuildService. My current problem with an automatic Release Tag handling is that we don't allow a usage of our rpms and those from jpackage.org, as Fedora does [2]. Is it possible to tell OBS that it should leave a Release Tag in specfile and just append it's output behind it instead of completely rewrite? I understood that this change will not appeared in Factory, because all jpackage RPMs in SUSE now has a larger Release Tag than jpackage.org RPMs, but this still should be applicable on Java:jpackage-5.0 (1.7) projects. [1] https://fedoraproject.org/wiki/Packaging/JPackagePolicy Regards Michal Vyskocil -- 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] Build Clients Switched off for ~ 12 hours
by Adrian Schröter 11 Mar '09

11 Mar '09

Hi, due to a partial power outage in one of our server rooms, the build clients are switched off atm. We expect to get this fixed tomorrow morning. The dispatcher is stopped intentionally for the time being. sorry adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] Download statistics of a specific project?
by Carsten Hoeger 10 Mar '09

10 Mar '09

Hi, is it possible to fetch download statistics of a specific project only using the OBS API? I don't see anything in https://api.opensuse.org/apidocs/ -- With best regards, Carsten Hoeger

5 10

[opensuse-buildservice] Build Team Meeting
by Adrian Schröter 10 Mar '09

10 Mar '09

present: rlihm, abauer, mls, freitag, adrian, poeml, cwh, froh, lrupp Topics: * Status * Scheduler Optimization Thoughts Status round: ============= abauer: * fixing Hermes setup issues. adrian: * Started ARM setup on opensuse.org, not finished yet * fixing some live imaging issues * extended Build number handling mls: * worked on merge handling for broken source links. Created a 100 lines perl prototype, which needs to get integrated into osc. * working also on merge of patches of source link, change is not trivial and needs better testing. freitag: * Deployed new hermes.opensuse.org - RSS feed support is working now - data model change poeml: * new osc release * worked on factory sync mechanism to keep old packages for a while * zypper has support for profiles * mirror scanner improvements to scan subdirectory only and remove also disappeared entries. * General mirror admin work * Deliver checksums via metalinks for direct usage in client Optimization thoughts ===================== Scheduler (and hardware) of external build service is at its limits. mls has some thoughts how to improve the speed, ideas are: - use libsatlover and use .solv local format instead of perl - rewrite expansion code in C Both changes will have the effect that the backend will not be pure perl anymore, but use C libs via perl xs bindings. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- 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] Colons considered harmful: escaping LD_LIBRARY_PATH in OBS projects
by Brandon Philips 09 Mar '09

09 Mar '09

Hello All- The problem can be illustrated by trying this out: osc co openSUSE:Factory attr cd openSUSE:Factory/attr quilt setup attr.spec cd attr-2.4.39/ ./configure make strace getfattr/getfattr / Here is a snip from that strace: open("/home/philips/projects/openSUSE/x86_64/libattr.so.1", O_RDONLY) = -1 ENOENT (No such file or directory) stat("/home/philips/projects/openSUSE/x86_64", 0x7ffffec11540) = -1 ENOENT (No such file or directory) open("/home/philips/projects/openSUSE/libattr.so.1", O_RDONLY) = -1 ENOENT (No such file or directory) stat("/home/philips/projects/openSUSE", 0x7ffffec11540) = -1 ENOENT (No such file or directory) open("Factory/attr/attr-2.4.39/libattr/.libs/tls/x86_64/libattr.so.1", O_RDONLY) = -1 ENOENT (No such file or directory) open("Factory/attr/attr-2.4.39/libattr/.libs/tls/libattr.so.1", O_RDONLY) = -1 ENOENT (No such file or directory) open("Factory/attr/attr-2.4.39/libattr/.libs/x86_64/libattr.so.1", O_RDONLY) = -1 ENOENT (No such file or directory) Not ideal! The process is trying to load obviously non-existent libraries. This is because libtool creates a wrapper for getfattr so it will be executed using local libraries built in the source tree instead of the system libraries: # Add our own library path to LD_LIBRARY_PATH LD_LIBRARY_PATH="/home/philips/projects/openSUSE:Factory/attr/attr-2.4.39/libattr/.libs:$LD_LIBRARY_PATH" But it is breaking because LD_LIBRARY_PATH uses colon characters as a separator like PATH... I talked to the libtool maintainer about this and he said: On 07:37 Thu 18 Dec 2008, Ralf Wildenhues wrote: > > I have found that libtool generates temporary wrappers with improperly > > escaped LD_LIBRARY_PATH. If the current directory path contains a colon. > > For example /home/philips/test:directory/attr-2.4.43/ > > Where is it documented that LD_LIBRARY_PATH is interpreted as with > backslash escaping for colons in the names? I've never heard of that > before. > > The ld.so(1) man page on my Debian testing system documents that > LD_LIBRARY_PATH is interpreted similarly to PATH. I confirmed now that > PATH uses this kind of colon escaping, surprisingly. I cannot find it > documented anywhere though, certainly not in the Posix pages (but hey, > I overlooked things before). > > We can think about supporting it when and where this is suitably safe to > do so, but my gut reaction would be "don't do it when it hurts". Ralf's first point is correct. ld doesn't accept \: as a literal colon like PATH does. So, we will need to fix this first. _ OR _ Instead of taking on the pain of fixing ld and all of the tools and scripts to generate and understand slash escaped colon characters we could stop using colon as a separator in build service project names. Upstream maintainers are not going to be excited about fixing the colon character problem up because the build service is probably the only thing using it. So, can we please use another separator? Perhaps the dash "-". This character is well accepted and works across http/dns/sh/etc without escaping or special consideration. Doing nothing about this isn't an option. Many packages use this trick to test programs as they sit in the source tree without doing a `make install`. If we do nothing developers who are new to OBS and unaware of the issue will waste time, as I did, trying to figure out why their library fixes aren't working. Thoughts? Thanks, Brandon P.S. I first filed a bug against libtool here: https://bugzilla.novell.com/show_bug.cgi?id=460044 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

8 17

[opensuse-buildservice] Change scheme of the package name
by Ulf 09 Mar '09

09 Mar '09

Hi, how to change the name of the resulting package. In my spec file I defined: %define _rpmfilename %%{NAME}-%%{VERSION}-%%{RELEASE}.%{disttype}.%%{ARCH}.rpm The resulting name is okay, but the OBS does not collect the file. Do I have to change the project meta data? Regards, Ulf -- Computer Bild Tarifsieger! GMX FreeDSL - Telefonanschluss + DSL für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a -- 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] bug/feature request in/for installer image
by Christof Hanke 09 Mar '09

09 Mar '09

Hi, a colleague of mine installed opensuse 11.1 on one of our company blade-servers. Unfortunately, it took 3 days, which didn't really impress him. The problem was the following: the Bios(system)-time was completely off (August 2008). The installation failed, because the checking of the SHA1 digests of some files (or repositories?) failed. In the log it just said "not checked". Thus, he (and me for some time) were looking for a problem in the usb_storage or whatever, because the DVD was always umounted after the failure. It would be nice if in the log file the reason for "not checked" e.g. "clock screw too large" would be mentioned. Where can I report this officially ? Many thanks, Christof -- 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] Nix package manager
by Archie Cobbs 09 Mar '09

09 Mar '09

I thought folks on this list would be interested to read this article about Nix: http://www.linux.com/feature/155922 How does this compare with openSUSE efforts to solve the same kinds of problem? -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

6 8

[opensuse-buildservice] RFC: openSUSE:Dropped project
by Lars Vogdt 09 Mar '09

09 Mar '09

Hi there Following the "Package foo needs new maintainer" resp. "Drop request for package foo" mails on opensuse-packaging for a while. Community members already asked for more details when a package is dropped from Factory. So what about creating an "openSUSE:Dropped" project, where people can find the latest source of a dropped package - and at least can get an overview about currently dropped packages? Means: 1) Packager sends drop request internally 2) Project manager agrees => drop package ^^^^^ Same as before. 3) the latest checked in package source (regardless if successful building or not) is copied into the project openSUSE:Dropped ^^^^^ New - formerly we just moved the source to an internal backup space and marked it as deleted in PDB. ---- 4) People can always see, which formerly packages are removed from the current Factory (and therefore will not be in the next release) looking at the openSUSE:Dropped repository 5) Interested community packagers can use/copy the latest source from openSUSE:Dropped Open questions: 1) Is this idea worth to be implemented? 2) What about packages with security problems? - Publishing should be disabled for all packages in the openSUSE:Dropped repo. But is this enough? 3) What to do with undropped packages? * If a package is maintained by community - regardless of the project -, should it be removed from openSUSE:Dropped? * Should it be removed ONLY if the package is in openSUSE:Contrib? Best solution for 2 (in my eyes) could be: Community packager wants to maintain a dropped package => he builds it in his home-Project => he sends a request to the openSUSE:Contrib project => openSUSE:Contrib maintainers are also maintainers of openSUSE:Dropped and can remove the package from openSUSE:Dropped as soon as it is accepted for openSUSE:Contrib With kind regards, Lars -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

6 5

Re: [opensuse-buildservice] ARM
by Peter Czanik 08 Mar '09

08 Mar '09

Hello, Martin Mohring írta: >> Any news on this? I'll hopefully receive an iMX515 developer board ( >> http://www.linuxdevices.com/news/NS8595694202.html ) in the near future, >> and would be nice, if I could run openSUSE next to (or rather: instead >> of) Ubuntu! >> >> > Do you plan to help us with development? It would be nice! > Well, I can't really help with coding (Pascal does not seem to count in most cases :-) ), but I use SuSE from 4.3 and test it from 5.x, so I got some SuSE and testing/bugreporting experience. And also documented SuSE installation for a couple of PPC boards, and created an installer and boot kernel for a couple Freescale PPC devel boards. I also recompile selected Packman packages on PPC, which I hope to do for ARM too. >> Bye, >> CzP >> >> > We are currently bootstrapping openSUSE @ ARM, and there will be some > news soon if/when we activate ARM builds in the public OBS also. > OK, thanks for the update! I'll come back to the ARM topic, once I got the board. Right now I only have an x86 and many PPC... Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0