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
ANy plans to get this working again? I'm at a loss as to how to get it going
though I had branched the project etc. Frankly, I'm figuring out the build
service, and think monoosc would go a long way to fostering a quicker
understanding.
--
Roger Luedecke
openSUSE Ambassador
Ind. Repairs and Consulting
**Looking for a C++ etc. mentor***
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi all,
I found some errors in de configurations of the OBS 2.3 server.
I've attached the corrected files and the patches.
It's related to:
Documentation: /usr/share/doc/packages/obs-api/README.SETUP
Apache vhosts configuration: /etc/apache2/vhosts.d/obs.conf
I've added the api port 81 connection as a quick fix and as the internal
doesn't really need to be encrypted.
Should I create a bug report for this?
Regards,
Joop.
Hi,
could Mageia please get added to OBS?
thanks a lot in advance,
Stephan
--
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
I understand the release tag numbering in spec files (for ‘rpm’ packages):
Release: <CI_CNT>.<B_CNT>
However, I am unable to determine how to perform the same “release”
numbering in ‘deb’ packages.
A simple test in home:srae:tools (build.opensuse.org) shows:
- the ‘rpm’ <CI_CNT> incrementing, but
- the ‘deb’ stays the same
-- actually, it seems to use the <version>-<release> as specified
on the first line of the ‘debian/changelog’ file (in debian.tar.gz)
Thanks in advance!
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(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
Hallo everyone,
we are unable to build packages for ubuntu 11.10 oneiric on our
installation of obs. During the preparation of the build chroot, the
install fails with the following error message:
<snip>
installing base-files
rmdir: failed to remove `/var/run': Directory not empty
dpkg: error processing base-files (--install):
subprocess installed post-installation script returned error exit status 1
Processing triggers for install-info ...
Errors were encountered while processing:
base-files
exit ...
At this point of the installation, the postinstall script of base-files
tries to replace the /var/run directory by a symlink to /run, while it
still contains an empty file /var/run/init.upgraded. This file has been
placed there by libc6 (source package eglibc). The reason for this is
given in the changelog:
eglibc (2.12.1-0ubuntu12) natty; urgency=low
* do not run 'telinit u' on upgrade, as this will break upstart.
touch /var/run/init.upgraded instead, which will force a re-exec
just before remounting root read-only. LP: #672177, LP: #694772.
On build.opensuse.org there is no problem with ubuntu 11.10 builds.
However the site uses a kvm-based setup while our installation uses
chroot-based workers. Also I suspect the b-o-o installation to use a
newer version of obs. On our installation we use the latest version for
opensuse 11.4. Here is a list of our installed obs versions:
obs-server-2.1.11-4.6.x86_64
obs-service-download_files-0.2-26.1.noarch
obs-signd-2.1.2-1.1.x86_64
obs-server-debuginfo-1.0.0-4.4.x86_64
obs-service-tar_scm-0.2.1-18.1.noarch
obs-api-2.1.11-4.6.x86_64
obs-common-2.1.0-2.1.x86_64
obs-service-set_version-0.1-5.1.noarch
obs-worker-2.1.11-4.6.noarch
obs-server-debugsource-1.0.0-4.4.x86_64
obs-service-verify_file-0.1-4.1.noarch
obs-utils-2.1.11-4.6.x86_64
obs-service-recompress-0.1-8.1.noarch
obs-productconverter-2.1.11-4.6.x86_64
I'm unsure what causes this problem and how I could try to fix it.
Either the postinstall configure script of base-files should run before
libc6 gets installed or the file in /var/run should be removed at some
other point during the bootstrapping process after it has been created
by libc6.
Could this be related to the version of the init_buildsystem script in
/usr/lib/obs/server/build? Could I try a newer version here or will this
break things?
I'd be grateful for any hint on how to debug this problem.
Thanks and bests,
Lars
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Greetings,
I'm trying to move a piece of a large build tree into OBS. It is not
possible in one step to move all of the large build tree into OBS.
The piece that I'm trying to build in OBS has dependencies on bits
external to that code.
Is it possible to use rpms from the existing build to satisfy build
dependencies in OBS?
>From the docs, it looks like this is possible. For example as
described in:
http://en.opensuse.org/openSUSE:Build_Service_private_instance_boot_strappi…
or perhaps creating a repo and using the "aggregate" or the "link"
feature, as described elsewhere.
I have created a local repository following the steps presented in the
above "private instance" reference. And the bs_admin --dump-cache does
show the packages of interest for the repository that I created (using
"private instance" reference). It would seem that all that is left to
do is to add this repository to the list of distro repositories used
when building.
However, after a couple days working on this I have been unable to get
the build to find the required package.
(1) It would be very helpful to know that I'm headed in the correct
direction, and ...
(2) I would be very grateful for any suggestions as to what it is that I
might be missing.
Thanks,
Bob Haxo
SGI
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org