March 2009 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] web client & auto trigger rebuilds
by Erik Aronesty 20 Mar '09

20 Mar '09

i've only been using just the web client so far, and think it's more than good enough for my needs, however... i notice that the web client auto-triggers rebuilds when you edit a file this is ?nice?, but... - is there any way to turn off the web client's itchy-trigger finger? - is there any way to "unschedule" a build via the web client? - feature request: it should rebuild only debian/ubuntu if a debian.control file is edited, not all of them (project name: smx) - erik -- 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] Last updated view
by Sascha 'saigkill' Manns 20 Mar '09

20 Mar '09

Hello Mates, a few weeks ago, i'm used an function from OBS, that let me know, what is last updated, most active Repo. But i doesn't found it now. Is the function removed or i'm blind? -- Sincereley yours Sascha Manns openSUSE Marketing Team openSUSE Build Service openSUSE Features Screening Team Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- 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] OBS 1.5 Announced
by Martin Mohring 19 Mar '09

19 Mar '09

Hi, now OBS 1.5 finally arrived officially: http://news.opensuse.org/2009/03/19/opensuse-build-service-15-announced Kind Regards, Martin Mohring -- 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] inject local rpm data for buildinfo calculation
by Marcus Hüwe 19 Mar '09

19 Mar '09

Hi, I wrote a small patch to inject rpm/deb/whatever data to the buildinfo calculation. This means one can collect the rpm/deb provides and requires of local packages and send them to the obs which uses them to calculate the buildinfo for local builds. Usecase: * you submitted a new package to the obs: before you can build a local package which depends on this new package you have to wait until the obs has built it (now you could simply do sth. like "osc build ... -p /path/to/local/pkgs" and it'll directly start the local build). How it works: A client like osc collects the requires and provides of some local packages, stores these information in a xml file and finally creates a cpio archive which contains the xml + a spec/dsc file and sends it to the obs. (Note: I decided to store the data in a xml because I didn't want to introduce yet another metadata format - this results in less additional code) Example xml: <localdeps> <package name="foobar" version="3.0.1" release="0" arch="i586"> <provides>foobar = 3.0.1-0</provides> <requires>glibc</requires> <requires>libfoo-devel >= 2.0</requires> </package> ... </localdeps> Any feedback, corrections etc. are welcome:) If there are no objections I'll commit it within the next few days. Marcus

5 13

[opensuse-buildservice] Debian 5.0 problem
by Michael Behrisch 18 Mar '09

18 Mar '09

Hello, I try to package https://build.opensuse.org/package/show?package=sumo&project=home%3Abehrisch for Debian 5.0 and get the following error: ... Processing triggers for man-db ... installing ca-certificates Updating certificates in /etc/ssl/certs..../usr/sbin/update-ca-certificates: line 59: mktemp: command not found dpkg: error processing ca-certificates (--install): subprocess post-installation script returned error exit status 127 Processing triggers for man-db ... Errors were encountered while processing: ca-certificates warning: can't open /etc/mtab: No such file or directory mount: can't find / in /etc/fstab or /etc/mtab System halted. Can anyone tell me how to fix this? Thanks in advance, Michael -- 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] New user intro & smx project
by Erik Aronesty 18 Mar '09

18 Mar '09

Dear OBS Users, (Following the tutorial mentioned posting a brief intro to the opensuse-buildservice mailing list.) I've been developing software for a while (20 years), in various and sundry languages. I think my first major development project was a Foxpro database for a law firm in NJ, done while majoring in CS so that properly dates and places me. I am a software developer, and one of the projects that I have been working on a lot recently is called "SMX". It's a language for developing websites that I like and I think other people, if they used it, would also like. In part by soliciting volunteers, I've gotten SMX to work on 32 and 64 bit versions Win32, Linux, BSD, and an older version was working on Debian. I have since lost access to my Debian machine. Maintaining access to various machines in order to run builds has been difficult and I went looking today for some other way of doing it. In 20 years, this is my first time that I've ever thought to seriously need to compile a given project on many flavors of operating systems, and I'm hoping that OBS is the right tool to help me there. SMX is also a fairly "big" and "old" project (some code goes back to 1996) with many "optional dependencies", and other such configuration messiness. I'm not sure if starting it as a "home project" is right, or if I should just request to create it as "smx". - Erik Aronesty http://www.smxlang.org http://svn.googlecode.com -- 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] osc 0.115, local OBS instance edition
by Adrian Schröter 18 Mar '09

18 Mar '09

Hi, we have just released a new osc 0.115. Users of api.opensuse.org can ignore it, but users of local build service instance might have waited for this. It fixes: 1) Package download from publishing server works now. This makes package downloads for local builds much faster. 2) copypac and linkpac to packages from remote Build Service instances is working now. You can for example run osc linkpac openSUSE.org:openSUSE:11.1 kernel-default home:adrian to link the kernel package from openSUSE:11.1 in external build service to your home project in your local build service. 3) Upload of (large) files is working now to local instances. You can get version 0.115 as usual from http://download.opensuse.org/repositories/openSUSE:/Tools/ All credits are going to Marcus Hüwe, Michael Schröder and Andreas Bauer(server side fixes) for this release. thanks a lot 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 1

[opensuse-buildservice] bug in obs-server sysconfig file
by Jon Nelson 17 Mar '09

17 Mar '09

The obs-server sysconfig file (fillup-style) seems to have a bug in it. EVERY time I reinstall or upgrade obs-server the OBS_SCHEDULER_ARCHITECTURES value in /etc/sysconfig/obs-server gets removed. Why is that and can it be prevented? It's caused me more than a few headaches. -- Jon -- 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] Build Team Meeting
by Adrian Schröter 17 Mar '09

17 Mar '09

present: froh, mls, freitag, abauer, rlihm, adrian, cwh Topics: * Status round * 1.5 release * Infrastructure * Test Development System Status round ============ freitag: * Working on Hermes, fixed bugs and created new :) * Got rid of locks in hermes abauer: * Improved Web Client: - Sub projects are visible in project page now - Improved project page loading time for large projects via delayed loading of build results. both is already active on build.opensuse.org * Thinking about rights management of property system. Not final thought, but updated wiki page. * Implemented meta forwarding for remote projects in frontend. rlihm: * web client css fixes for new version. * Discussion how to move the templates into development. adrian: * Presented openSUSE and Build Service at Linuxtage Chemnitz AI: adrian create fate request for STABLE/Development classification. ( #306323 ) mls: * working on link repair support in source server * fixing osc build for a local build service * implemented meta forwarding for remote projects in backend. 1.5 Release =========== * planned 1.5 release is this thursday. Infrastructure ============== * download/stage.o.o hardware failure * power outage for build hosts for one night * source server problem on sunday, unknown reason for now. * Binary backend server has reached it's limits. Our general purpose backup system will replace it after a memory upgrade. Test Development System ======================= * Klaas will take a former build host and get it installed and reachable via one public IP address for testing and development purposes. -- 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

2 2

Re: [opensuse-buildservice] debian transformer problems on xUbuntu 8.10
by Martin Mohring 17 Mar '09

17 Mar '09

Amilcar do Carmo Lucas wrote: >> Amilcar do Carmo Lucas wrote: >> >>> On Thursday 08 January 2009 09:41:42 Carsten Hoeger wrote: >>> >>> >>>> Did that ever work? I wasn't able to use tar.bz2 on Ubuntu 6.06 AFAIR. >>>> >>>> >>> yes, .tar.bz2 works fine for 6.06, 7.04, 8.04. >>> >>> It would be nice if you fix this regression. >>> >>> >> I got on the other hand the answer from some ubuntu packagers that >> .tar.bz2 will not be accepted by the public build instances for debia or >> ubuntu, so it has a good reason that dpkg-source is crying about not >> allowed .tar.bz2. I switced back to .tar.gz for my combi .deb and .rpm >> packages though. >> >> What I say is valid for at least: >> - Debian Lenny, Sid >> - Ubuntu: 7.10, 8.04, 8.10, 9.04 >> >> > As far as I know the build service automatically repackages the .tar.bz2 > that I give into a .tar.gz file before the build. Like I said AFAIK it > does that for all debs except 8.10. > So I'm waiting that the openSUSE people fix this bug. > I think it does not repackage the sources from .tar.bz2 into .tar.gz. What filenames would you like to use in this case, what should be stated in the .dsc then? Lets do that on an example multiplatform .deb and .spec based package. The source file is called hallo.tar.bz2. The .spec files references then hallo.tar.bz2, this is easy. On the other hand, the .dsc file references then hallo.tar.gz, a file that does not exist, only to circumvent some dpkg-source consistency checks which are there for a good reason? This is not a good solution, because not transparent. Why not fulfil the Debian/Ubuntu and the Fedora/... whatever packaging requirements? -- 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] problems with OBS 1.5rc2 after upgrading host to openSUSE 11.1
by Jon Nelson 16 Mar '09

16 Mar '09

I had a number of problems after upgrading an OBS instance from openSUSE 11.0 to 11.1 The client remains running openSUSE 11.1, as it has for months. The osc version on the client has not changed and is the latest available. The first is that adding a *comment* via osc did not work. I could add and remove files (PUT/DELETE respectively), but the subsequent POST would not, returning a 403. I tracked it down to this code, in /srv/www/obs/frontend/app/controllers/source_controller.rb, near line 139: if not ['diff', 'branch'].include?(cmd) and not @http_user.can_modify_package?(pkg) I believe two things are wrong with this line. First, it does not include 'commit'. Second, the logic is wrong (it used AND instead of OR), and the corrected version is below. if not ['diff', 'branch', 'commit'].include?(cmd) or not @http_user.can_modify_package?(pkg) Why did this work fine with openSUSE 11.0 and not 11.1? The OBS versions are the same (1.5rc2)! Second problem: only for the 'Admin' user, editing the user info (/user/edit) fails every time with: undefined method `source_backend' for #<Person:0x7fac0a31a048> What might be going on here? -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 4

[opensuse-buildservice] Republishing / Signing already published packages?
by Carsten Hoeger 16 Mar '09

16 Mar '09

Hi, is it possible to republish or just sign all packages of a project without rebuilding? It looks like signd died within the last days and now my builds are unsigned... :-( -- With best regards, Carsten Hoeger

4 7

[opensuse-buildservice] Re: home:RedDwarf:branches:home:aaronbockover:Factory in bad state
by Cristian Morales Vega 15 Mar '09

15 Mar '09

2009/3/14 Cristian Morales Vega <cmorve69(a)yahoo.es>: > What can I do from here? >From the web interface I created a new package schroedinger and... the old was deleted :-? From there I was able to delete the project. -- 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] home:RedDwarf:branches:home:aaronbockover:Factory is bad state
by Cristian Morales Vega 14 Mar '09

14 Mar '09

$ osc branch openSUSE:Factory schroedinger Server returned an error: HTTP Error 400: Bad Request branch target package already exists: home:RedDwarf:branches:home:aaronbockover:Factory/schroedinger $ osc deleteprj 'home:RedDwarf:branches:home:aaronbockover:Factory' Project contains packages. It must be empty before deleting it. If you are sure that you want to remove this project and all its packages use the '--force' switch Ok, the project and package already exists, so... $ osc deleteprj -f 'home:RedDwarf:branches:home:aaronbockover:Factory' Server returned an error: HTTP Error 404: Not Found package 'schroedinger' does not exist in project 'home:RedDwarf:branches:home:aaronbockover:Factory' $ osc deletepac 'home:RedDwarf:branches:home:aaronbockover:Factory' 'schroedinger' Server returned an error: HTTP Error 404: Not Found package 'schroedinger' does not exist in project 'home:RedDwarf:branches:home:aaronbockover:Factory' What can I do from here? -- 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] ymp for upgrade?
by Andrew Jorgensen 13 Mar '09

13 Mar '09

Hello, We want to create a ymp (1-Click) which will cause the user to upgrade all packages provided by our repository which are installed, but not ask the user to install anything which is not installed. Is such a thing possible? -- 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] 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