Sometimes you have appA in your repo building for both old and new
openSUSE versions. appA depends on libA > X, but only the latest
openSUSE version provides it. openSUSE <latest-1> came with libA
<X-1>. The solution is to package libA > X for the old distributions
and usually you do that linking to the devel project.
I would like an openSUSE:Current project that would always contains
the latest supported version of the packages. Right now the packages
from openSUSE:12.1:Update, but once 12.2 is released it should be
changed to openSUSE:12.2:Update. This way I could link to those
packages instead of linking to the devel project. It would let me
compile appA in old distros while giving to the users a libA package
that is not soooooo unsupported (this would be officially unsupported
anyway, but...).
I would like this since it's a single place to change when a new
openSUSE version is released (If needed I can do it).
Looking at the openSUSE:12.1:Update project metadata I guess it would
just need be something like
<project name="openSUSE:Current">
<title>Current version of openSUSE</title>
<description></description>
<link project="openSUSE:12.1:Update"/>
<debuginfo>
<enable/>
</debuginfo>
</project>
But I'm not sure since I never really saw a doc explaining the meaning
of <link> in the *project metadata*, only in _link files.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello everyone,
I have a question/problem with Perl packages and BuildRequires when
building for SLES(SP2).
The problem comes up with multiple packages when trying to build them
for SLES, let's look at perl-HTTP-BrowserDetect from
devel:languages:perl for example.
The spec files includes:
---
BuildRequires: perl(Module::Build) >= 0.3601
---
and the build log clearly states (see
https://build.opensuse.org/package/rawlog?arch=x86_64&package=perl-HTTP-Bro…)
that it is being installed:
---
installing perl-Module-Build-0.36.07-4.1
---
but still, the build fails with:
---
Module::Build version 0.3601 required--this is only version 0.280801 at
Build.PL line 5.
---
As far as I understand, "Module::Build" v0.280801 is already installed
by default under SLES11SP2 and the newer required version 0.3607 is not
found OR the older version is found first by the script "Build.pl".
A second example would be "perl-POE-Test-Loops" which requires a version
of Test::More/Test::Simple >=0.94, but this is not found although
installed (i.e. only an older version is found), see log here:
https://build.opensuse.org/package/live_build_log?arch=x86_64&package=perl-…
How do I circumvent this problem?
Thanks for your help!
Hello,
related to the "obs-worker - restarting services in chroot env at build
time" mailing we still have some problems to get a more or less "clean"
chroot build environment on a dedicated obs-worker machine.
Therefore the question:
Is there an (scripting) entry point to cleanup the obs-worker chroot
build environment after _every_ build of a package even if the build has
failed?
In our case we have to kill some services like mysql or apache2 to
ensure that they aren't running accidently after a (failed) build on the
obs-worker.
Your help is again very much appreciated.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
On Mon, 25 Jun 2012 19:16:17 +0200
Boris Manojlovic <boris(a)steki.net> wrote:
> as stated in paste did you run command from debug log? (missing
> initrd)
>
> On Mon, Jun 25, 2012 at 5:53 PM, Malcolm
> <malcolm_lewis(a)bellsouth.net> wrote:
> > Hi
> > I've enabled qemu-kvm and it's working fine for running an iso
> > image as my user.
> >
> > I've configured my ~/.oscrc for the three options: build-device,
> > build-swap and build-memory, however when testing I get the
> > following;
> >
> > http://paste.opensuse.org/72274785
> >
> > I'm on SLED 11 SP2, with osc version 0.134.1.
> >
> > Is there something I'm missing?
> >
Ahh running the env command was it many thanks :)
--
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.31-0.9-default
up 3:17, 4 users, load average: 0.51, 0.52, 0.49
CPU Intel i5 CPU M520(a)2.40GHz | Intel Arrandale GPU
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
here's a small summary of the 10th (coding) week. Last week I worked
mostly on the new fetcher code which I finally pushed into the git
repo. Apart from this I did some refactoring here and there.
The todo for this and the next week is to start with the new osc
user interface (that is the client code). As I already wrote in the
proposal the new osc client will be based on python's argparse module
and the Jinja2 template engine.
Marcus
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello
With the opensuse build service [obs] getting more usage every day
I wonder if this would make a diffence :-
1. Use solid state disks [ssd] to improve build times of package rpms
on, perhaps point the BuildRoot or _tmppath to the ssd's
Reason for asking.
Improve the packaging times during busy times on obs.
Cheers Glenn.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hello
Is there a osc command to remove/delete a package from the obs server.
There is no local copy.
If so what is the osc command yo do this ?
Example package to remove:
openSUSE Build Service > Projects > home:doiggl > Packages > xsd
https://build.opensuse.org/package/show?package=xsd&project=home%3Adoiggl
Thanks Glenn
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org