Hello,
is usual, openeSUSE 10.3 runs out of maintenance and I will remove all repos
building against it in OBS.
openSUSE:10.3 project has been moved to DISCONTINUED: namespace as announced a
while ago.
bye
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
Hi All,
I am trying to install my program on Mandriva but can't seem to add
the OBS repository.
It seems that the command urpmi.addmedia doesn't work with the
normal RPM PM. Someone on IRC mentioned that I could specify a
different type for the repository in my OBS raw config to
automatically generate a urpmi compatible repo. What do I put as the
type for my Mandriva repo to make it urpmi compatible?
Thanks,
Nick
--
Nick Peterson
Programmer @ Siepel Lab
Cell: (480) 600-2544
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Greetings,
Is there any work being done for OpenVZ, LXC or other OS-level virtualization support for the build environment in OBS?
I am doing my Master's thesis on extending OBS to the cloud. Seeing that Amazon Web Services uses Xen for virtualization (and thus does not support Xen/KVM inside it), and that building without a sandboxed environment is not safe, OpenVZ and LXC would seem promising. There's also much talk about using these technologies in AWS, so I would see it possible.
Best Regards,
Ville Seppänen
Tieto Corporation
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
there seems to be a problem with the getbinarylist call (view=cpio)
and the "Transfer-Encoding" header (depending on the "length" of the
request?). I just tried the following curl calls:
curl -o out.cpio -v -sS \
"https://api.opensuse.org/public/build/openSUSE:Factory/standard/x86_64/_rep… -e "print 'b'x3616")"
and
curl -o out.cpio -v -sS \
"https://api.opensuse.org/public/build/openSUSE:Factory/standard/x86_64/_rep… -e "print 'b'x3617")"
The response of the first request still includes the
"Transfer-Encoding" header but the response of the second request
has no "Transfer-Encoding" header.
Now consider the following call:
curl http://<local obs>/build/<remote project>/<repo>/<arch>/_repository?view=cpio&<long query>
This leads to a "crash" in bs_srcserver (the ajax process dies because
the response has neither a "Transfer-Encoding" nor a "Content-Length"
header).
Any ideas why the "Transfer-Encoding" header gets swallowed?
Marcus
Ps. is this the same bug to which a comment in "worker_getbinaries"
refers?
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
The package cdbs keeps failing on me. I try to backport it from Debian
and / or Ubuntu 10.10 to Ubuntu 10.04. Was always working, but now it
fails or it fails for one architecture (something one sometimes the
other arch...).
https://build.opensuse.org/package/show?package=cdbs3&project=home%3Aopen-s…
I need some help cause pretty some packages depends on a newer version
of cdbs.
Thanks in advance,
~P
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
there's a bug#682 in icedtea bugzilla, that JRE fails to run on i586
machine with guarantee(VM_Version::supports_cmov()) failed: illegal
instruction. After reading the code it seems JIT emits cmov* instructions, so
the produced native code cannot run on i586 processors.
I think the most clean way how to fix this in openSUSE is build our
openjdk (and Sun Java as well?) as i686 only packages as Fedora and
RedHat already does. However it seems like pretty challenging in a
BuildService, because the only one package with i686 version I'm aware
is glibc, but this approach seems not usable for openjdk, where only
i686 and not i586 version is needed.
So how can be only i686 rpm packages produced in a buildservice?
[1] http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=682
Regards
Michal Vyskocil
I'm working with a bit of legacy code that's apparently writing files
manually for an initial ramdisk (initrd).
In its makefile, it's using 'mknod -m 660 tty1 c 4 1'
This causes issues with OBS, as mknod doesn't work for non-root users, IIRC.
I know OBS executes builds as user 'abuild', and it makes sense to me
to have a nonprivileged user doing the build.
Since running builds as root is verboten, what options do I have to
build this package with OBS?
(Note: I am using my own OBS server/build nodes, not build.opensuse.org)
--
Troy Telford
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
hi,
was there some planned outage for today? Web frontend is down, osc
can't connect, etc etc.
bye,
MH
--
gpg key fingerprint: 5F64 4C92 9B77 DE37 D184 C5F9 B013 44E7 27BD
763C
() ascii ribbon campaign against HTML e-mail
/\ www.asciiribbon.org
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org