(Cross-posting, because I don't know if this is an OBS problem or
another crazy policy)
Today I found that my packages in home:seife:testing are almost all
gone, which prevented my daily "zypper -v dup --no-r
--no-allow-vendor-change" from completing successfully.
https://build.opensuse.org/project/show/home:seife:testing
All but one package in the Factory repo are "excluded" and apparently
there's no way to include them again.
How do I fix that?
--
Stefan Seyfried
"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Good morning,
after the update to 2.8.3, I found that local users (most prominent the Admin user ;)) no longer work, when LDAP mode is
enabled.
It was pretty easy to get the existing users to work again:
+++ app/models/user.rb 2017-09-20 06:45:18.666231345 +0000
@@ -199,7 +199,10 @@
# in the database. Returns the user or nil if he could not be found
def self.find_with_credentials(login, password)
if CONFIG['ldap_mode'] == :on
- return find_with_credentials_via_ldap(login, password)
+ user = find_with_credentials_via_ldap(login, password)
+ if user
+ return user
+ end
end
user = find_by_login(login)
This still does not enable me to create new users (as admin), because I'm just sent to the Sign Up page, which then
tells me that new users can only sign up via LDAP.
While looking to also fix that and let an admin allow to create (and edit) local users, I found that in git master many
more changes have been made to make this virtually impossible.
So I'm asking why this usecase is actively destroyed. Local OBS users (apart from the obvious Admin user) are useful
e.g. as technical accounts, for automation jobs etc. which are not always possible to get into a corporate user directory.
Thanks,
Stefan
--
Stefan Seyfried
"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi all!
Since about two days I'm getting strange build failures for armv7l
packages, please see attached e-mail notifications. It appears that at
least one build host has some kind of local problem?
We use the armv7l packages mainly to confirm that our "make check"
passes on non-x86 architectures, so this is absolutely non-critical for
the osmocom builds, so no rush from my side.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hello we have here
https://build.opensuse.org/package/show/Application:Geo/sumo
old _service files that we are unable to delete they don't appear when doing a
osc co nor have delete button on Gui.
If someone can help us to clean up some Mb, or explain how to do it.
Thanks.
--
Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch
Bareos Partner, openSUSE Member, fsfe fellowship
GPG KEY : D5C9B751C4653227
irc: tigerfoot
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I try to add a new board to openSUSE:Factory:ARM. I did this already in
the past and for doing that I had to modify the JeOS package and add
links to it with JeOS-<boardname>. Those links are no more in
openSUSE:Factory:ARM, instead of this the JeOS package contains now a
"_multibuild" file, which is generated by the pre_checkin.sh script. I
added my board to pre_checkin.sh. But how to trigger now the build of my
new added board image instead of the native JeOS image?
In the past I just called "osc build factory armv7l" in the
JeOS-<boardname> linked package to build it local, and I committed it to
my work project to build it in obs.
osc --version
0.155.0
Br,
Frank
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
I logged in to accept a request, but while OBS worked a few minutes
ago, now I get:
"Service unavailable!
The server is temporarily unable to service your request due to
maintenance downtime or capacity problems. Please try again later.
If you think this is a server error, please contact the webmaster.
Error 503
build.opensuse.org
Apache/2.4.23 (Linux/SUSE)
"
When I click "accept request"...
Bye,
CzP
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
A while back you may remember a request for read access to a few tables or a
snapshot of them from which one could work on extracting metrics of interest.
That request never went anywhere so when revisiting this subject recently I
went for a completely external approach using the API and some processing
code. Since InfluxDB and Grafana were mentioned as the tools which the OBS
team would use if they were to provide metrics I went ahead and used those.
The code is built atop the osc-plugin-factory/osclib [1] and primarily uses /
search/request API call to retrieve requests for given projects of interest.
The code then walks the combined state changes of all the requests to re-
create the staging state at any point in time. A variety of metrics are
generated along the way and some quite interesting graphs can be produced in
Grafana. Additionally, I plan to create an event log [2] for use by the
release team both for SLE and openSUSE to provide a clear overview of what is
being done by the various staging masters.
Long story short, I plan to cleanup and push the code which can be used to
update the metrics on the regular basis. The original responses indicated that
if something is setup there may be interest in moving forward with the
metrics. Is there interest in hosting an InfluxDB and Grafana instance that
could also be expanded with metrics added directly by OBS? If there is no
interest I will look into setting up a proper host for the release teams.
The URL to my local instances has been shared a few times, but I would rather
not include it in a public mailing list since it is not setup for any sort of
load or real public access. If individuals are interested feel free to reply
or contact me in IRC.
As a teaser, here are some of the work-in-progress graphs which only include
accepted submit requests. The negative dip on the first Factory graph is
documented in the OBS bug regarding dates [3]. In fact the graph would be much
worse without some major workarounds to detect and avoid such corrupted data.
- https://imgur.com/a/lqMPo
Lastly, I had quite a time walking the data structure to extract the desired
values and documented a number of bugs and problems [4].
[1] https://github.com/openSUSE/osc-plugin-factory/tree/master/osclib
[2] https://github.com/openSUSE/osc-plugin-factory/issues/730
[3] https://github.com/openSUSE/open-build-service/issues/3858
[4] https://github.com/openSUSE/open-build-service/issues/3898
--
Jimmy
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org