Hi,
I am new and trying local build on s390x with SLE_12_SP3 using the
following command
sudo osc build
but I get the public key not available for many packages. You can see
the output by clicking the following link
https://pastebin.com/YBQk3vGe
I know that I can use --noverify option to bypass this and builds
complete successfully when I use --noverify option but how can I fix
this? What will happen if I don't fix it?
--
Usman
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I am running OBS Appliance 2.8.2 on VMware ESX. When the appliance
boots I get an error "Failed to start LSB: Finds the storage device
to be used for OBS server and/or worker." I have included a dump of
systemctl status obsstoagesetup.service below. I Just want to confirm
if this is normal or should be addressed.
I also attempted and update of a clone of my appliance via zypper but
2 GB root drive is not sufficient for upgrades. Update begins but end
with "Error Code: Write Error". I checked root drive and it was up to
100% utilization from 93% prior to update. I decided to install latest
version of OBS appliance over existing install. New appliance adopts
my old setting but now I am getting and error on boot "Failed to start
LSB: open build service source service server." In addition I am
unable to build rpms in this current state.
Not sure what to do next to get the cloned appliance to build a package.
SYSTEMCTL status obsstoragesetup.service
obsstoragesetup.service - LSB: Finds the storage device to be used for
OBS server and/or worker Loaded: loaded
(/etc/init.d/obsstoragesetup; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2018-03-06 18:44:59
UTC; 16min ago
Docs: man:systemd-sysv-generator(8)
Process: 1365 ExecStart=/etc/init.d/obsstoragesetup start
(code=exited, status=1/FAILURE)
Mar 06 18:44:59 linux obsstoragesetup[1365]: OBS_SERVER_SIZE=38912
Mar 06 18:44:59 linux obsstoragesetup[1365]: TOTAL_SWAP_SIZE=1024
Mar 06 18:44:59 linux obsstoragesetup[1365]: FINAL_VG_SIZE = 12284 -
38912 - 25600 - 1024
Mar 06 18:44:59 linux obsstoragesetup[1365]: FINAL_VG_SIZE=-53252
Mar 06 18:44:59 linux obsstoragesetup[1365]: OBS_WORKER_ROOT_SIZE=-26626
Mar 06 18:44:59 linux obsstoragesetup[1365]: MIN_WORKER_ROOT_SIZE=4096
Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Control
process exited, code=exited status=1
Mar 06 18:44:59 linux systemd[1]: Failed to start LSB: Finds the
storage device to be used for OBS server and/or worker.
Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Unit
entered failed state.
Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Failed with
result 'exit-code'.
SYSTEMCTL status obsservice.service
obsservice.service - LSB: open build service source service server
Loaded: loaded (/etc/init.d/obsservice; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2018-03-09 11:59:39
UTC; 3min 34s ago
Docs: man:systemd-sysv-generator(8)
Process: 1761 ExecStart=/etc/init.d/obsservice start (code=exited, status=7)
Mar 09 11:59:38 linux systemd[1]: Starting LSB: open build service
source service server...
Mar 09 11:59:39 linux startproc[1788]: startproc: exit status of
parent of /usr/lib/obs/server/bs_service: 13
Mar 09 11:59:39 linux obsservice[1761]: Initializing obsservice..failed
Mar 09 11:59:39 linux systemd[1]: obsservice.service: Control process
exited, code=exited status=7
Mar 09 11:59:39 linux systemd[1]: Failed to start LSB: open build
service source service server.
Mar 09 11:59:39 linux systemd[1]: obsservice.service: Unit entered failed state.
Mar 09 11:59:39 linux systemd[1]: obsservice.service: Failed with
result 'exit-code'.
'.
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello, guys! I searched how to integrate OBS with GitHub so that a git
push would cause OBS to fetch the source code and build. I followed
directions on these pages:
https://openbuildservice.org/2013/11/22/source-update-via_token/https://github.com/seccubus/obs_autobuild_test
(CC their authors, thank you for the great material!)
But when I opened GitHub's Integration & services to add the Obs
service, I read this:
"Note: [GitHub Services are being deprecated][1]. Please contact your
integrator for more information on how to migrate or replace a service
with [webhooks][2] or [GitHub Apps][3]."
[1]: https://developer.github.com/changes/2018-04-25-github-services-deprecation/
[2]: https://developer.github.com/webhooks/
[3]: https://developer.github.com/apps/differences-between-apps/#about-github-ap…
The news is from April 25, 2018. The first paragraph summarizes it:
"GitHub plans on shutting down GitHub Services so we can shift focus
to other areas of the API, such as strengthening GitHub Apps and
GraphQL, and improving webhooks. The intention of GitHub Services was
to allow third-party developers to submit code for integrating with
their services, but this functionality has been superseded by GitHub
Apps and webhooks. GitHub Services has not supported new features
since April 25, 2016, and we plan to officially deprecate it on
October 1st, 2018."
Although I successfully integrated OBS with GitHub using a GitHub
Service, is it already possible to do that same integration using
GitHub Apps or webhooks?
Thank you!
Antonio
The Linux Kamarada Project
http://kamarada.github.io/
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
The URLs in the Debian:Next meta are no longer valid. DoD therefore
practically does not work since quite a while.
The nearest OBS global project admin: please edit the URLs
as per the following change:
$ osc meta prj Debian:Next
<repository name="update">
- <download arch="x86_64" url="http://ftp.de.debian.org/debian/testing-updates/main" repotype="deb">
+ <download arch="x86_64" url="http://ftp.de.debian.org/debian/dists/testing-update/main/" repotype="deb">
(including any other url= occurrences in the XML)
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
back-home x86_64 is dead.
https://build.opensuse.org/monitor
Happy holidays.
Paolo
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi all,
First, what do I want to achieve?
The VDR project (https://build.opensuse.org/project/show/vdr) will get a
version update to version 2.4 in the near future (hopefully ;-)
In the past (when updating from 1.6.x to 2.0...) I created a vdr:legacy
project where I just copied all sources before updating.
I'd like to do something similar now, this time "vdr:2.2", but I'd
rather not copy the sources over and build everything again. Instead I
was wondering if nifty tricks with "osc release" could be used to
achieve what I want.
My idea was to temporarily set a release target for vdr (and
vdr:plugins) to vdr:2.2, release everything and then remove the release
target again.
Will this work as I intend it to? Or will the binaries vanish once I
remove the release target from the vdr repo? (I doubt it, but who knows ;-)
Have fun,
seife
--
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.
Quote:
------------------------------------------------------------------------------
seife@vbox-seife:~> osc help release
release: Release sources and binaries
This command is used to transfer sources and binaries without rebuilding them.
It requires defined release targets set to trigger="manual". Please refer the
release management chapter in the OBS book for details.
------------------------------------------------------------------------------
I'm desperately seeking for the "OBS book" which contains a "release management chapter".
Can anyone help me find it?
Have fun,
seife
--
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
I am trying to release packages from:
https://build.opensuse.org/project/show/systemsmanagement:Uyuni:Master:Cent…
to:
https://build.opensuse.org/project/show/systemsmanagement:Uyuni:Stable:Cent…
With:
$ osc release systemsmanagement:Uyuni:Master:CentOS6-Uyuni-Client-Tools
<status code="invoked">
<summary>Job invoked</summary>
</status>
But for some reason only one package (cobbler) was released. I can't see any errors, but
no other packages are released, and the status of the repositories is "State needs
recalculations, former state was: No build possible atm, waiting for jobs in other
repositories"
The strange thing is CentOS7 worked fine when I released packages from:
https://build.opensuse.org/project/show/systemsmanagement:Uyuni:Master:Cent…
to
https://build.opensuse.org/project/show/systemsmanagement:Uyuni:Stable:Cent…
With:
$ osc release systemsmanagement:Uyuni:Master:CentOS7-Uyuni-Client-Tools
<status code="invoked">
<summary>Job invoked</summary>
</status>
It is hard to me to believe that this is a config problem, as meta and project are almost the
same at origin and destination (only exception being that at Master:CentOS6-Uyuni-Client-
Tools there is an extra patch project to systemsmanagement:Uyuni:Master:Temp).
Any idea of what is going on?
--
Julio González Gil <jgonzalez(a)suse.com>
Release Engineer
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg
Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)
I reviewed so far:
- https://en.opensuse.org/openSUSE:Build_Service_Concept_Product_Definition is
outdated (it still refers to _product)
- https://speakerdeck.com/openbuildservice/open-build-service-project-workshop
(linked at https://openbuildservice.org/help/ is outdated as well)
- Nothing at this list https://lists.opensuse.org/cgi-bin/search.cgi?
query=000product&advanced.x=0&advanced.y=0&list=opensuse-buildservice
I also had a look at the differences between _product for Leap 42.3 and
000product for Leap 15.0 and the only BIG difference I can see so far is that,
for 000product, there are .kiwi files.
But what puzzles me is that the image definition is still at the .product
file.
Has anyone here experience with migration from _product to 000product and
things we should keep in mind? :-)
And one extra question: is the migration mandatory, keeping in mind that our
product will be based on SLE15 (SUSE Manager) or openSUSE 15 (Uyuni)?
--
Julio González Gil <jgonzalez(a)suse.com>
Release Engineer
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg
Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)
Hello Everyone,
I couldn't find any resource so far on how to setup partitions on the backend. There is a reference about partitions on the OBS Architecture page [1] in the reference guide, but no instructions on how to go about setting things up.
While searching the archives of this list, I came across one thread where Adrian suggested [2] what is explained in BSConfig.pm.
I want to split backends for "existing" projects (let's say, home:). From what I understand from reading code, only "newer" content will be pushed / moved to the partitioned servers. My questions are:
- What contents should I be moving to the new partitioned server? (e.g., partitioning home: projects)
* /srv/obs/build/home:*
* /srv/obs/repos/home:/*
- Do I need move any other data?
- Do I need to stop all backend services on the main server before moving this data? I'm assuming yes, but wanted a confirmation.
- Do I need to run or check something else after moving the data over to partitioned server(s)?
Regards,
Srinidhi.
[1] https://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.archi…
[2] https://lists.opensuse.org/opensuse-buildservice/2016-07/msg00041.html
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org