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
We upgraded one of our products to use the new version of product definitions,
and it seems "staticlinks" does not work anymore, as the repositories are
generated with buildnumbers.
So far I discovered that using:
Repotype: slepool:nobuildid
OBS able to generate repositories without build numbers.
However: is it possible to have both repositories with and without build
numbers at the same time, as I think it was the case with "staticlinks"?
--
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 originally posted this yesterday on the forum and an administrator
malcolmlewis offered a workaround using --no-verify and suggested
posting to this mailing list to determine the real problem.
I have had a package for some time which builds correctly on the Build
Service for openSuse, Debian and Fedora. It also builds correctly for
openSuse and Debian on my local machine using:-
osc build --local-package openSUSE_LEAP_15.0
osc build --local-package openSUSE_Tumbleweed
osc build --local-package Debian_9.0
Yesterday I tried to build the package for Fedora (29 and Rawhide)
locally for the first time:-
osc build --local-package Fedora_29
osc build --local-package Fedora_Rawhide
The first run populated the package cache which took a long time
(around 1 hour) screen output pausing when not found at the
downloads site and retrieval was attempted via API. After this stage
and on all subsequent build attempts I got the errors:-
using keys from Fedora:Rawhide, home:m-grant-prg
warning: /var/cache/osbuild-packagecache/Fedora:Rawhide/standard/x86_64/attr-2.4.48-4.fc30.x86_64.rpm:
Header V3 RSA/SHA256 Signature, key ID cfc659b9:
NOKEY /var/cache/osbuild-packagecache/Fedora:Rawhide/standard/x86_64/attr-2.4.48-4.fc30.x86_64.rpm :
public key not available
The last message was repeated many times for multiple packages.
openSUSE and Debian builds continue to work correctly.
Any help or suggestions would be most welcome.
Regards,
Mark
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
How can I check if a projects signkey is still valid or needs extension.
Is there an osc or gpg command I can use to find that out to write a
Nagios check to warn me, before the key expires and users complain.
Kind regards
Ralf
--
Ralf Becker
EGroupware GmbH [www.egroupware.org]
Handelsregister HRB Kaiserslautern 3587
Geschäftsführer Birgit und Ralf Becker
Leibnizstr. 17, 67663 Kaiserslautern, Germany
Telefon +49 631 31657-0
hi all,
is there any way how I can enable "Developer Toolsets" in centos/rhel
projects in the OBS, please?
For one of my packages I need gcc toolset >= 5.x, unfortunately these
distros contain 4.x only.
reference:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
or do I need to import all these packages into my OBS?
http://mirror.centos.org/centos/7/sclo/x86_64/rh/devtoolset-7/
thanks,
Petr
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
When I build packages locally, I get the following error message:
> osc build openSUSE_Tumbleweed mysql-community-server.spec
[...]
[ 15s] -----------------------------------------------------------------
[ 15s] ----- building mysql-community-server.spec (user abuild)
[ 15s] -----------------------------------------------------------------
[ 15s] -----------------------------------------------------------------
[ 15s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature /home/abuild/rpmbuild/SOURCES/mysql-community-server.spec
[ 15s] rpmbuild: symbol lookup error: rpmbuild: undefined symbol: rpmcliVSFlags
How can I fix this?
The affected repository is:
https://build.opensuse.org/package/show/home:bjoernv/mysql-community-server
Setup:
- Tumbleweed 20190115
- osc 0.163.0
Greetings,
Björn
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I've been building Wine packages for Debian_Testing (https://build.opensuse.org/project/show/Emulators:Wine:Debian) for awhile now without any problems, but today it's showing as "unresolvable" because "nothing provides gcc-6-base."
I checked https://packages.debian.org/buster/gcc, and it appears the gcc package for buster is now gcc-8, and gcc-6 is no longer available (https://packages.debian.org/buster/gcc-6 just shows an error message). I've added gcc-8 to my control and dsc files, but the OBS doesn't seem to recognize it--it's still trying to use gcc-6.
--
Rosanne DiMesio <dimesio(a)gmail.com>
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
python3-vtk is already fixed, but netcdf13 is still needed ...
Kind regards,
Stefan
---------- Forwarded Message ----------
Subject: [opensuse-science] Please add prefers for MPI variants
Date: Samstag, 12. Januar 2019, 18:37:20 CET
From: Stefan Brüns <stefan.bruens(a)rwth-aachen.de>
To: opensuse-factory(a)opensuse.org
CC: opensuse-science(a)opensuse.org
Hi,
due to the recent MPI cleanup work in science, which has reached Factory
meanwhile, there are a few new choices:
python3-vtk: python3-vtk python3-vtk-openmpi python3-vtk-openmpi2
netcdf13: libnetcdf13 libnetcdf13-openmpi libnetcdf13-openmpi2
Please add Prefer's for the non-MPI variants.
Note, for netcdf there already is "Prefer: -libnetcdf13-openmpi". There is
also "(+)netcdf11", which no longer exists.
Btw, is there a better way to specify this, especially for versioned
libraries?
Kind regards,
Stefan
--
Stefan Brüns / Bergstraße 21 / 52062 Aachen
home: +49 241 53809034 mobile: +49 151 50412019
-----------------------------------------
--
Stefan Brüns / Bergstraße 21 / 52062 Aachen
home: +49 241 53809034 mobile: +49 151 50412019