We migrate the source of the official OBS books to github as well now.
This was done basically for two resons:
* People were too frightend to ask for a svn.opensuse.org account
and just want to push something.
* I want to keep a review process to avoid that these pages become
just an unreviewed kiwi copy. So we need something like pull requests.
The new pages are online on openbuildservice.org now. (Update was broken
since quite some time).
If you want to improve it, please just go to
https://github.com/openSUSE/open-build-service-documentation
and do the classic github way via forking, committing and pull request.
Btw, I do still want to remind you that it is okay to have specific content
in the books for specific instances. These can be tagged and we generate them
only for some exports of the docuementation. Eg. There can be openSUSE or
Tizen or $yourhome specific instance content inside.
thanks!
adrian
--
Adrian Schroeter
email: adrian(a)suse.de
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284
(AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Open Build Service(OBS) 2.4.4 just got released
===============================================
Another bugfix release of the 2.4 series is out there.
This release fixes a serious security leak tracked as CVE-2013-3703
and Novell bugzilla 828256:
Users can add or remove other users to projects or packages even when
they have no maintainership there.
All OBS 2.4 admins a requested to updated immediatly to close this
hole. Instances with OBS 2.3 and before are not affected.
While OBS 2.4.4 only contains the bugfix for this situation, we introduced
a better design in master branch to avoid these kinds of bugs in future.
Beside of that a number of bugfixes for constraints and change detections
in the backend are included in this release.
>From the official Release Notes:
Feature backports:
==================
* none
Changes:
========
* None
Bugfixes:
=========
* api: Fix for CVE-2013-3703
* api: Do not hide projects which have an explicit access enabled tag.
* api: handle invalid strings in options.yml for
allow_user_to_create_home_project setting
* backend: repository type changes got not catched by the scheduler
* backend: fix project deleting not cleaning up build area in async mode
* backend: hostlabel build constraints had no effect
* backend: constraints defined in project config had no effect
* backend: start more then one worker by default if not using zVM
--
Adrian Schroeter
email: adrian(a)suse.de
SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284
(AG Nürnberg)
Maxfeldstraße 5
90409 Nürnberg
Germany
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I'm running an instance of OBS 2.3
I have a package that always says 'unresolvable', and when I use osc
to ask for buildinfo, it lists a half-dozen packages like this:
<error>unresolvable: have choice for PACKAGE_FOO needed by
PACKAGE_BAR: PACKAGE_DEP1 PACKAGE_DEP2, have choice for ....
Now, the problem is that PACKAGE_FOO says it built successfully, and
I'm using in a parent project's buildconf:
Substitute: PACKAGE_DEP2 PACKAGE_DEP1
because I *always* want to use PACKAGE_DEP2.
I don't understand what's going on here.
In summary:
project 1, package A builds fine.
project 2 (which uses project 1 as a build repo), package B refuses to
build, the problem listed is a problem with package A.
--
Jon
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello, i have the next problem.
repo A: has an rpm package X, that Requires Y
\ (A is a repository for B)
|- repo B: has a kiwi package that needs package X
Y doesn't exist and project config has Substitute to other package Z. (in both projects)
But kiwi package is in unresolvable state with "nothing provides Y"
Any ideas?--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Beaded Necklace - faceted peridot
Elsa Peretti for Tiffany Lapis square and sterling silver ring
Elsa Peretti for Tiffany Black Lacquer round pendant on silk cord
Elsa Peretti for Tiffany 5 teardrop necklace - sterling silver
Cushion earrings in sterling silver
-----
where to sell gold
--
View this message in context: http://opensuse.14.x6.nabble.com/Elsa-Peretti-for-Tiffany-5-teardrop-neckla…
Sent from the opensuse-buildservice mailing list archive at Nabble.com.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Will post later as well:
heart tag bracelet
heart lock necklace (thin chain)
1837 lock necklace (thick chain like heart tag)
1837 square ring
mesh ring
-----
where to sell gold
--
View this message in context: http://opensuse.14.x6.nabble.com/1837-lock-necklace-thick-chain-like-heart-…
Sent from the opensuse-buildservice mailing list archive at Nabble.com.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I'll have to post pics later, but here's what I've got:
Heart tag bracelet
SS & Yellow gold Heart link bracelet
Madonna pendant necklace
Open heart pendant necklace
-----
where to sell gold
--
View this message in context: http://opensuse.14.x6.nabble.com/pics-later-but-here-s-what-I-ve-got-tp4994…
Sent from the opensuse-buildservice mailing list archive at Nabble.com.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I have some square ones from Tiffany that I had engraved for my wedding but,
I can't find them on the catalogue.
What can I say? I'm a Tiffany's girl
I'll send ya pics later--once I've snapped 'em and then worked out how to
post 'em.
-----
where to sell gold
--
View this message in context: http://opensuse.14.x6.nabble.com/worked-out-how-to-post-em-tp4994564.html
Sent from the opensuse-buildservice mailing list archive at Nabble.com.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I'll have to post pics later (when I figure out how to!):
Diamond solitare Ring - Tiffany setting
Diamond Half Chanel (wedding ring)
Paloma Picasso hammered white gold ring with single diamond
T & Co 1837 Bangle in sterling silver
-----
where to sell gold
--
View this message in context: http://opensuse.14.x6.nabble.com/Diamond-solitare-Ring-Tiffany-setting-tp49…
Sent from the opensuse-buildservice mailing list archive at Nabble.com.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I'm using the OBS packages with version 2.4.4-4.1 (obs-api, obs-server, etc.)
I have createrepo-0.9.9-4.1.1 installed.
It seems that my OBS instance has started having problems running createrepo:
yum/zypper repodata is no longer being generated correctly
They no longer have the full list of the RPM packages that are
published. I can look inside the repodata/primary.xml.gz, and many
packages that are configured to be published are not in the repo data.
The packages themselves are placed into the download location - there's
just no repodata that catalogs the package's existence to yum/zypper.
I've checked and re-checked that both the project and package
publishing is enabled.
The problem doesn't appear to be related to any particular
distribution; it happens across the board, on RHEL, SLES, openSUSE, and
Fedora.
/srv/obs/log/publisher.log has entries like the following:
running createrepo
Worker 0: Traceback (most recent call last):
Worker 0: File "/usr/share/createrepo/worker.py", line 99, in <module>
syncing database (11 ops)
waiting for an event...
I'm not sure if that is actually a problem, as in looking at
bs_publish, it seems clear that if there's a failure, a message will be
printed "createrepo failed re-running without extra options", and the
repo will be regenerated again. I'm not seeing the error message.
As a minor diagnostic, I pivoted the repodata directory out of place, and ran:
createrepo .
That completed without problems, and the generated repo appears to have
the data needed.
However, as OBS isn't generating the repodata properly, it's still a problem.
Does anyone have an ideas what I can do to find out what is happening,
and where the error is?
Thanks.
--
Troy Telford
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org