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 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
This question concerns both the OBS and packaging so I am sending to both
lists.
I am currently working on packaging the Swiss Ephemeris
http://www.astro.com/swisseph/
I am currently at the planning scheming and experimentation stage.
First I will do the library. But then there is the data. The data is about 60
files not all of which will be wanted by all people. There may be ways of
grouping but I am not sure. Perhaps one rpm per file. The Web page says:
> For this extended timespan the ephemeris requires 32 Mbytes of ephemeris
> files.
It would be a shame if this had to repeat for each distro. There may be other
projects with even more data.
This data is distro and architecture independent.
I understand that there should be different rpm per distro because different
distros link libraries differently and do other details differently.
There could be rpm version dependencies. Perhaps one distro can not understand
rpms from another distro as raw data.
My question is this is there a lowest common denominator rpm format that can
represent pure data (and a few text licensing files) and be understood by all
distros?
How would you get the build service to produce such rpms?
After you produced them how would you get the build service to serve them for
all rpm based distros?
Same question for debs and the debian based distros?
Unrelated question: a while back OBS debian binary repositories were debian
compatible but the source repositories were not. Is this still true?
--
Paul Elliott 1(512)837-1096
pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J
http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117
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
JFYI,
we switched to a new login proxy mechanism today:
http://news.opensuse.org/2011/04/19/infrastructure-updates/
please report if you see unexpected changes.
Let's hope that eastern is safe ;)
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,
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