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
Currently the package "maildrop" from server:mail repository fails to
build for many distributions, e.g. for Tumbleweed, Leap 42.3, Leap 15.0
and Factory.
https://build.opensuse.org/package/show/server:mail/maildrop
The error message is "nothing provides gpg-offline".
The maildrop.spec file contains the following GPG related entries:
%if 0%{?suse_version} >= 1230
BuildRequires: gpg-offline
%endif
[...]
%prep
%if 0%{?suse_version} >= 1230
%gpg_verify %{SOURCE1}
%endif
The macro %gpg_verify is unavailable (tested with Tumbleweed).
What is currently the right way to verify GPG signatures of sources?
What is a good example package for GPG verification?
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
Hi,
I had to update the signature key of openSUSE:Tools project.
Your installer will most likely complain.
You can trust the
keyid: 826659A9013E5B65
as documented in the project:
https://build.opensuse.org/project/show/openSUSE:Tools
adrian
--
Adrian Schroeter
email: adrian(a)suse.de
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, 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
On Dienstag, 25. September 2018, 15:30:11 CEST wrote Michael Kuron:
..
> > > Adrian, any idea on the i586 issue
> > Try to reproduce it local and maybe attach strace.
>
> Again, I failed to reproduce it locally in a Docker container, but
> haven't tried building via osc yet. If we could reproduce these issues
> outside of the automated builds, we could probable debug and fix them
> quite easily.
the main difference to the container would be that you get a full VM
without network (except localhost).
You can jump inside during build anyway via a telnet server:
osc build --vm-type=kvm --vm-telnet=$PORT -x telnet-server -x net-tools
or alike. So you run also the original distro kernel of your base.
If you still can not reproduce it, it can be hardware specific or
memory / cpu resource specific.
Did you check the attemps, if there are maybe some random success
on some workers? You may get a pattern .... (osc jobhistory)
--
Adrian Schroeter
email: adrian(a)suse.de
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, 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
Hi guys,
Michael and I are trying to update the espresso package in OpenSuse:
https://build.opensuse.org/package/show/home:cjunghans:branches:devel:langu…
We tracked all issues here: https://github.com/espressomd/espresso/issues/2258
But now we are left with 2 issues, which hard to solve outside of the
Build service VMs:
1.) Segfault on openSUSE_Factory_ARM armv7l
Details: https://github.com/espressomd/espresso/issues/2258#issuecomment-420988560
Michael's attempt so far:
https://github.com/espressomd/espresso/issues/2258#issuecomment-421710470
Cannot be reproduced!
2.) Build on openSUSE_Tumbleweed i586 is super slow and runs out of time.
Additionally there are 2 minor infrastructure issues:
1.) On openSUSE_Tumbleweed x86_64, -grecord-gcc-switches is missing so
we get hundreds of warnings like:
W: python-espressomd no-rpm-opt-flags
All non-Tumbleweed builds don't have that warning
2.) On SLE_12_SP4 x86_64, we cannot install the openmpi-devel package
anymore, error:
File /usr/lib64/mpi/gcc/openmpi/lib64/mpi.mod conflicts between
attempted installs of openmpi-devel-1.10.7-1.15.x86_64 and
openmpi-compat-1.8.1-3.1.x86_64
Any help on the first two issues would be appreciated.
Cheers,
Christoph
--
Christoph Junghans
Web: http://www.compphys.de
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
I'm currently build bash 5.0 beta as well as readline 8.0 beta.
As readline does build local with osc as well as on the OBS and
also bash with --prefer-pkgs $PWD/binaries where the readline
package are stored ... but the build on the OBS results in
nothing provides readline-devel = 8.0
is there any way in prjconf of the repository shell to enforce
that the package readline-devel with version 8.0 will be installed
but oly for the pacakge bash with version 5.0
Werner
--
"Having a smoking section in a restaurant is like having
a peeing section in a swimming pool." -- Edward Burr
Hi,
could we PLEASE have all the beta versions ONLY in K:U:F, and leave K:F
in an actual usable state for the people who actually use the OBS repos
to have an unsable system?
From what it looks like to me right now the latest plasma beta is
actually maintained in K:F and just copied over to K:U:F...
thank you for your consideration.
Mthias