openSUSE Build Service November 2008

buildservice@lists.opensuse.org

66 participants
89 discussions

[opensuse-buildservice] How does the download.opensuse.org/repositories work...

by Sylvester Lykkehus

[Originally posted to opensuse(a)opensuse.org] ..in respect to, who decides which packages and when to update them, and who do the actual packaging ? I know the home:/ repo's are individual users using the buildservice. But how about, e.g. /repositories/server:/mail/ ? The reason I am asking about server:/mail, is that 10.2 and 10.3 repo's both contains new(er) versions of e.g. courier-imap, but 11.0 repo does not. So, who decides that the 10.2 repo should contain new and updated packages of courier-imap, but the 11.0 repo should not have courier-imap at all ? This is not a complaint, I'm just trying to understand the layout and "package cycles" of download.opensuse.org/repositories. Best regards Sylvester Lykkehus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] Error failed depencies

by Sascha Manns

Hello, now i'm building neccp in home:saigkill. But the osc (commandline) says: "586-suse-linux/bin/ld: cannot find -latlas". Then i installed blas and libblas3 and marked both at Build Requires. But the same Effect. Then i installed libatlas-cpp and libatlas-cpp-devel and inserted it in BuildReq. Same Effect. Last but not least i installed libatlas3 and libatlas3-devel. The same Effect. But now i have no ideas... -- Sincereley yours Sascha Manns Open-News-Network e.V. Web: http://saschamanns.gulli.to -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] chmod after unpacking

by Sascha Manns

Hello, i had in my %setup: %setup -q -n skrooge %Patch1 -p1 Now i would chmod a file after unpack. The absolute PATH is: /skrooge/po/listFiles.sh Now must: chmod +x listFiles.sh. How can i insert this in my spec? Which format? -- Sincereley yours Sascha Manns Open-News-Network e.V. Web: http://saschamanns.gulli.to -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] SLE 10

by Joop Boonen

All, I want to build a package that needs qt4 on SLE 10. Does anyone know who i can add qt4 during the build, as it's not a standard part of SLE 10. Regards, Joop. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

Re: [opensuse-buildservice] chmod after unpacking

by Sascha Manns

Hello Michael, Am Dienstag 04 November 2008 10:17:42 schrieb Michael Schroeder: > On Tue, Nov 04, 2008 at 10:14:03AM +0100, Sascha Manns wrote: > > Am Dienstag 04 November 2008 10:01:48 schrieb Michael Schroeder: > > > > Now i would chmod a file after unpack. The absolute PATH is: > > > > /skrooge/po/listFiles.sh > > > > > > Are you saying that a file from a tar archive is unpacked with > > > the wrong permissions? Sounds like a bug to me. > > > > Yes. If i build normaly the Package, the build fails: listFiles.sh > > Permission denied. If i make chmod on this file, the build > > finished. I must make chmod before compiling... > > What project/package is that? The project named: skrooge URL: http://www.kde-apps.org/content/show.php/skrooge?content=92458 -- Sincereley yours Sascha Manns Open-News-Network e.V. Web: http://saschamanns.gulli.to -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] Build Team Meeting Minutes

by Adrian Schröter

present: mls, jcborn, tpatzig, mjung, freitag, adrian, poeml, dmueller Topics: * Status round. * OBS Roadmap Status round ============ mls: * reworked classic kiwi processing in OBS jcborn: * created branch in kiwi svn for OBS * bugfixing and patch merging for * kiwi packages for OBS build in home project currently mjung: * Presented trust concept work in university * started implementation of trust value calculation freitag: * working on hermes rewrite due to feedback of Andreas and Thomas This will speed up hermes a lot Will also switch to michas XML perl lib, because upstream is too slow poeml: * visited "Internet Messurement Conference" * Work on redirector: -> Improved mirror database admin tool -> Optimized mirror selection to support fallbacks outside of country -> GeoIP updates handled automatically now -> Torrent files are supported adrian: * introduced second KIWICollect modul which optimizes OBS use case. (CPU time from more than 1 day to 56 seconds for Factory usecase) * fixed handling of src and debug package handling in kiwi * Currently diffing resulting medias, they look really correct now ! Roadmap ======= New OBS Roadmap has been discussed and will be published this week. Last missing feature for next release is local build support for kiwi images. -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) 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

12 years, 2 months

[opensuse-buildservice] Kiwi-inside-obs - bug-squashing the loop

by Jan-Simon Möller

Hi! We improved kiwi now to be able to build also images for arm (and other architectures) on an x86 host. Only remaining is the rebuild-loop when kiwi is used inside obs. Let's hunt that little bug now ;). Summary: The scenario is like this: project "imaging:Admin", package "foo", repository "image". Simple kiwi-config (only bootstrap section!), output is ext2-image. Filename ends in "*0.0.1" (version in the kiwi.xml). So far: build succeeds, things get uploaded here (also show up in /srv/obs/build/<foo>), BUT not in /srv/obs/repos and the job is directly rescheduled and thus builds in a loop. here's the scheduler-log: event finished:imaging::image::obs-imaging-8d2731b6e7128e3694ffb623f20177a6 0 left) - imaging/image: obs-imaging built: 3 files looking at med prio imaging/image (0/0/1/0/17) - imaging/image expanding dependencies sorting 1 packages - obs-imaging (kiwi) +autoconf +automake [...] +openvpn +perl-base +python +python-xml +rpm +rpm-python +smart +terminfo-base +xenomai +zlib meta change, start build Use of uninitialized value in substitution (s///) at BSFileDB.pm line 86. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 1. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 1. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 1. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 2. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 2. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 2. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 3. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 3. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 3. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 4. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 4. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 4. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 5. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 5. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 5. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 6. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 6. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 6. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 7. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 7. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 7. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 8. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 8. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 8. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 9. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 9. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 9. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 10. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 10. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 10. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 11. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 11. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 11. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 12. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 12. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 12. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 13. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 13. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 13. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 14. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 14. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 14. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 15. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 15. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 15. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 16. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 16. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 16. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 17. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 17. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 17. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 18. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 18. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 18. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 19. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 19. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 19. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 20. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 20. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 20. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 21. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 21. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 21. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 22. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 22. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 22. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 23. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 23. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 23. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 24. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 24. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 24. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 25. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 25. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 25. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 26. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 26. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 26. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 27. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 27. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 27. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 28. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 28. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 28. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 29. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 29. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 29. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 30. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 30. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 30. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 31. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 31. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 31. Use of uninitialized value in string eq at BSFileDB.pm line 124, <F> line 32. Use of uninitialized value in length at BSFileDB.pm line 124, <F> line 32. Use of uninitialized value in concatenation (.) or string at BSFileDB.pm line 124, <F> line 32. scheduled: 1 building: 1, notready: 1 took 0 seconds to check the packages looking at low prio imaging/image (0/0/0/0/17) - imaging/image expanding dependencies sorting 1 packages scheduled: 1 building: 1, notready: 1 took 0 seconds to check the packages waiting for an event... Looks like BSFileDB doesn't find variables in this case. My worker sends these files: $VAR1 = [ { 'filename' => '/tmp//root_1/.build.packages/KIWI/limbo-auto-config.i686-0.0.1', 'name' => 'limbo-auto-config.i686-0.0.1' }, { 'filename' => '/tmp//root_1/.build.meta', 'name' => 'meta' }, { 'filename' => '/tmp//root_1/.build.log', 'name' => 'logfile' } ]; We need to find a way to accept kiwi's output filenames (other than .iso). I looked at bs_sched, but I'm (a bit) lost finding the right spot. best regards, Jan-Simon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] Finding dependent builds

by Luke Imhoff

Is there a way through the API to find out which packages depend on a given package? This has come up a couple times when I've been showing OBS to developers at my company. Here's a use-case: I have a patch to the kernel, so kernel-source, kernel-syms, and kernel-<flavor> are all directly affected by a change to their source (since they all share kernel-source's tarball). Being a careful developer, I want to make sure the change to the kernel doesn't break any kernel module packages that depend on the kernel. So, I want to find out all kmps that I need to rebuild. Is there a way using the API to find out which packages depend on a given kernel-source/kernel-syms pair so that I can branch them off and test the kernel change with all the dependent packages before checking in the change to something important? A solution other than scanning the specs files for BuildRequires: kernel-syms would be nice since I don't think that will scale well. I know this data is available to the scheduler since it must be contructing a dep graph to mark packages as blocked while the kernel is building after a check in to OBS occurs. I just don't know if I can get the same information through the API since the scheduler is on the backend while the API is on the frontend. (It's the same machine for our local OBS, but I know conceptually they are separate.) Modifying the obs-server/obs-api isn't a big deal since we're already doing it for some other reasons (adding LDAP auth and subversion integration), but if something exists already in the API I'd rather use that. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

[opensuse-buildservice] Building packages in projects against the previous build of Factory

by Vincent Untz

Hi, Beware, this is a naive question :-) When oS:F gets rebuilt, all packages in GNOME:Factory, eg, get blocked for quite some time, which makes it a bit more difficult to work (at least, for me). I was wondering if there was a way to build G:F against the last complete build of oS:F, so that G:F is not blocked for so long. Maybe people already considered this and it can't work? But, well, it'd make my life so much easier... Thanks, 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

12 years, 2 months

[opensuse-buildservice] Download counter

by Michael Behrisch

Hello, I played a little with the statistics and it is mentioning download counters for some packages and for others not. Even after having a (very short) look at the api and searching the list archive and the forums I could not find out for which packages / files the counters are enabled or how to enable them. Maybe someone here can shed a little light ...? Regards, Michael -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

12 years, 2 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service November 2008