Good evening,
I am having a problem building a package with gcc on OBS Arch image.
The package is just a `./configure; make; make install` one, although it
doesn't work because within the Arch chroot something is broken.
The important part of the failed configuration log is the following:
configure:2941: checking whether the C++ compiler works
configure:2963: g++ -march=x86-64 -mtune=generic -O2 -pipe
-fstack-protector-strong -fno-plt -D_FORTIFY_SOURCE=2
-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now conftest.cpp >&5
/usr/bin/ld: /usr/lib/libc.so.6: version `GLIBC_2.27' not found
(required by /usr/bin/ld)
collect2: error: ld returned 1 exit status
I am not sure which fixtures has the Arch chroot, but I believe this
should not happen. By using the official chroot tool provided by Arch
this issue does not arise.
If needed I can attach the *config.log* generated by `./configure`.
--
Giovanni Santini
My blog: http://giovannisantini.tk
My code: https://git{hub,lab}.com/ItachiSan
My GPG: 2FADEBF5
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
I have running projects on older versions of the OBS but I decided to
start with a freshly installed appliance from 2.8.4.
When I try to build the ARM repo I get the following message.
[ 1s] [27/28] preinstalling rpm...
[ 1s] [28/28] preinstalling pam...
[ 1s]
[ 1s] running aaa_base preinstall script
[ 1s] chroot: failed to run command 'sh': No such file or directory
[ 1s] running aaa_base postinstall script
[ 1s] chroot: failed to run command 'sh': No such file or directory
[ 1s] initializing rpm db...
[ 1s] chroot: failed to run command '/usr/bin/rpmdb': No such file or
directory
[ 1s]
I've looked at many reports about this issue but I didn't see any
resolution.
I'm using a very simple package for testing that works for i586, x86_64.
ARM Repo
<repository name="qemu">
<path project="openSUSE.org:openSUSE:Factory:ARM"
repository="standard"/>
<arch>armv7l</arch>
<arch>aarch64</arch>
</repository>
IA repo
<repository name="qemu_accel" rebuild="local" block="local">
<path project="openSUSE.org:openSUSE:Factory" repository="standard"/>
<arch>x86_64</arch>
</repository>
Steve
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
It seems a project config like
```
<repository name="openSUSE_Leap_15.0_update+ports">
<path project="openSUSE:Leap:15.0:Update" repository="standard"/>
<path project="openSUSE:Leap:15.0:Update" repository="ports"/>
<arch>x86_64</arch>
<arch>ppc64le</arch>
</repository>
```
causes a problem that no package dependencies for the x86_64 build can be found.
Please see the example project
https://build.opensuse.org/package/show/home:okurz:test-leap15-update/test-…
showing this problem.
It also shows all other combinations that work, e.g. using only the GM
repositories, using :Update for x86_64 only without ports, using Leap 42.3, etc.
Is this a generic OBS problem or Leap 15.0 specific? Is there a best practice how to handle?
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
OpenSUSE:Tools/openSUSE-release-tools fails to resolve for SLE_15 repo:
> nothing provides python-cmdln, nothing provides python-colorama
This same problem previously that occurred with SLE_12_SP3 and was resolved by
including all modules or some-such on OBS side.
>From what I can tell it looks like a bunch of modules are included in SLE-15
setup. Any idea what is missing as the packages are definitely in SLE-15.
--
Jimmy
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello, need help.
Have a problem with gpg keys for my private repo.
I need one key for all ubuntu repositories and hash algo >=sha256.
When publish projects in obs-server, they are signed with a key (example
key below). The key is the algorithm rsa (algo 1) and encryption sha256
(digest algo 8).
But when publish packages, hosts with OS ubuntu 16.04, warn that the key
has a sha1 cipher:
"Signature by key 167F971DD45E6807EF611BB1A18A8926E4050125 uses weak digest
algorithm (SHA1)"
The problem is solved if I create a separate key for the project.
osc signkey --create certbot
obs_admin --republish-repository certbot Ubuntu_16.04_standard
But I need one key for all the repositories. How can I solve this?
Created key example:
gpg2 --list-packets /srv/obs/obs-default-gpg.asc
:public key packet:
version 4, algo 1, created 1525702323, expires 0
pkey[0]: [4096 bits]
pkey[1]: [17 bits]
keyid: 00AAADA57778C8B1
:user ID packet: "private OBS (key without passphrase) <defaultkey@localobs
> "
:signature packet: algo 1, keyid 00AAADA57778C8B1
version 4, created 1525702323, md5len 0, sigclass 0x13
digest algo 8, begin of digest 80 f8
hashed subpkt 2 len 4 (sig created 2018-05-07)
hashed subpkt 27 len 1 (key flags: 2F)
hashed subpkt 11 len 4 (pref-sym-algos: 9 8 7 3)
hashed subpkt 21 len 4 (pref-hash-algos: 10 9 8 11)
hashed subpkt 22 len 4 (pref-zip-algos: 2 3 1 0)
hashed subpkt 30 len 1 (features: 01)
hashed subpkt 23 len 1 (key server preferences: 80)
subpkt 16 len 8 (issuer key ID 00AAADA57778C8B1)
data: [4096 bits]
:public sub key packet:
version 4, algo 1, created 1525702323, expires 0
pkey[0]: [4096 bits]
pkey[1]: [17 bits]
keyid: A18A8926E4050125
:signature packet: algo 1, keyid 00AAADA57778C8B1
version 4, created 1525702323, md5len 0, sigclass 0x18
digest algo 8, begin of digest e6 30
hashed subpkt 2 len 4 (sig created 2018-05-07)
hashed subpkt 27 len 1 (key flags: 2E)
subpkt 16 len 8 (issuer key ID 00AAADA57778C8B1)
subpkt 32 len 540 (signature: v4, class 0x19, algo 1, digest algo 8)
data: [4096 bits]
I have installed private installation obs server 2.9.2.
Options in BSConfig.pm:
our $forceprojectkeys = 1;
our $sign_project = 0;
our $sign = "/usr/bin/sign";
our $keyfile = "/srv/obs/obs-default-gpg.asc";
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello everyone,
I was trying to push an update to a package of mine but `osc ci` gives
me a segfault which I am not sure how to debug.
I am on Arch and I have the tools from the OBS tools official repo.
--
Giovanni Santini
My blog: http://giovannisantini.tk
My code: https://git{hub,lab}.com/ItachiSan
My GPG: 2FADEBF5
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi OBS Admins,
there was an unexpected feature to many in the "patch" util, which
could be used to execute scripts.
So your OBS instance is affected by that as well, since there is an
old feature which allows to apply patches via _link files.
So it was possible to execute code on your source server via ed-script
crafted patches.
Please be sure that you installed the latest distributions updates
for
CVE-2018-1000156 (bsc#1088420, savannah#53566)
for the "patch" utils.
They should be out for all SUSE platforms.
bye
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