September 2014 - openSUSE Build Service

[opensuse-buildservice] page you are looking for is currently down for https://openqa.opensuse.org/results/
by doiggl＠velocitynet.com.au 15 Sep '14

15 Sep '14

FYI, https://openqa.opensuse.org/results/ result 503 Sorry, the page you are looking for is currently down for maintenance. Cheers Glenn -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] How to find out the origins of a package
by gny＠xs4all.nl 15 Sep '14

15 Sep '14

Hi, Is there an easy way to trace back from which sub/home project a particular package is originated from? Thanks, G. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] QA tests Invalid signature - Installation aborted.
by doiggl＠velocitynet.com.au 13 Sep '14

13 Sep '14

Hello, FYI I see cd/content: Invalid signature. Installation aborted on QA tests https://openqa.opensuse.org/tests/22319 https://openqa.opensuse.org/tests/22319/modules/welcome/steps/1 Cheers Glenn -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Managing a new devel repo
by Greg Freemyer 11 Sep '14

11 Sep '14

All, At my request a new repo (security:forensics) has been created. I have used "osc copypac" to populate it with about 60 packages that I maintain in various other devel repos. All 60 are either forensics specific packages or packages I created to satisfy novel dependencies of a forensic package. At some point I want to change things to have security:forensics be the official home of these packages from factories perspective. Questions: - How do I make security:forensics a legitimate source of SRs to factory. - Given I have 60 or so packages to "osc changedevelrequest" (CRs), when is the right time to do that? Now before 13.2 is put to bed or wait a few weeks until 13.2 is truly separated from factory. Or wait until after 13.2 is truly out so the team has a break. - When the time is right, should I do all 60 at one whack, or should I spread them out over time so as not to overwhelm the factory review team. - Do I need to reach out to anyone directly before I start issuing CRs. - Once the CRs are done, do I just issue a bunch of osc deletes? Since I'm a maintainer on all these packages I think that will just make it happen and not issue a SR for people to see. Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] persistent build error for older releases
by Detlef Steuer 10 Sep '14

10 Sep '14

Hi! I had hoped it would just go away again, but now it remains broken for quite some time already. I.e.: osc remotebuildlog devel:languages:R:patched R openSUSE_11.1 i586 | less --- snip a lot ---, then: [ 25s] [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/vda [ 25s] /dev/vda: clean, 2621/1281120 files, 228191/5120000 blocks [ 25s] fsck succeeded. Mounting root device read-write. [ 25s] Mounting root /dev/disk/by-id/virtio-0 [ 25s] mount -o rw,defaults -t ext4 /dev/disk/by-id/virtio-0 /root [ 25s] replacing /etc/mtab with symlink to /proc/self/mounts [ 26s] ### WATCHDOG MARKER END ### [ 26s] 2nd stage started in virtual machine [ 26s] machine type: x86_64 [ 26s] switching personality to 8... [ 27s] 2nd stage started in virtual machine [ 27s] machine type: i686 [ 27s] mkswap: error while loading shared libraries: libuuid.so.1: cannot open shared object file: No such file or directory [ 27s] swapon on /dev/disk/by-id/virtio-1 [ 27s] found swap v0 signature string for 4 KiB PAGE_SIZE [ 27s] swapon: /dev/disk/by-id/virtio-1: Invalid argument [ 27s] ### WATCHDOG MARKER START ### [ 30s] [ 6.452230] SysRq : Power Off [ 30s] [ 6.459801] reboot: Power down [ 30s] ### WATCHDOG MARKER END ### Can anything be done about that? (Same situation for 11.1 and i586) Detlef -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] SRs to maintenance projects fails if package name differs
by Wolfgang Rosenauer 09 Sep '14

09 Sep '14

Hi, I ran into an issue recently and can reproduce it every time. An SR into a maintenance project seems to fail under certain circumstances. In my case I cannot submit an updated Thunderbird package to Evergreen 11.4 via osc sr mozilla thunderbird24 openSUSE:Evergreen:11.4 MozillaThunderbird The diff which shows up looks pretty fine still but the resulting request does not seem to have any relation to the target package: https://build.opensuse.org/request/show/248162 I consider this a bug? So the only workaround is to create a real mbranch for that package? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] [obs-signd] need advice about gpg key generation
by Valentin Gologuzov 09 Sep '14

09 Sep '14

Hi, I'm looking for an advice with key generation for obs-signd. We would run it independently from OBS. ( we want to utilize obs-signd for package signing at Copr - http://fedorahosted.org/copr) If I understand correctly, OBS manages user key outsides from obs-signd, and provides private[public] keys directly to /bin/sign. At our service we want to minimize key manamement, keep secrets on secured machine (where singd runs) and avoid sending secrets through network. Here is our (future) setup: host-0: secure machine where key-pairs is stored in /root/.gnupg/ it runs: - [A] perl signd - [B] small httpd service which generates new key-pairs into the keyring and write generated passphrases to /root/.phrases/ host-1: backend where builds occurs and result rpms are signed by invocation of /bin/sign [C] [C] is configured by /etc/sign.conf to access [A] at host-0 When user `foo` builds first package, service [B] will be invocked and passphrase will be added to /root/.phrases/ and keys will be added to keyring, so that [A] can sign packages for user `foo` without recieving keys through network. [C] will be used: * To sign rpm [@host-1]:# sign -u foo(a)example.com target.rpm * To obtain public key for user: [@host-1]:# sign -u foo(a)example.com -p Please, tell if this design makes sense or how should it be changed. Additional question: Do we really need to protect keys with passhrases on [host-0]? Private keys should never leave keyring at that machine. -- Best regards, Gologuzov Valentin. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] OBS 2.5 / openSUSE 13.1 / KVM Worker - could not find /dev/sda
by Matthew Drobnak 08 Sep '14

08 Sep '14

I upgraded our production machine to 2.5 this morning. Only a few hiccups. However, one major one is that KVM does not work. I installed the KVM package using zypper, (zypper in kvm), and that installed a bunch of stuff. obsworker then found KVM and attempted to use it, but starting of the VMs failed -- it complained about not being able to find /dev/sda during boot of the VM, instead referring to /dev/disk/by-id/..... Has anyone seen this? Did I miss a step? Thanks. -Matt

2 3

[opensuse-buildservice] How to bootstrap a new OBS (v2.5.4) server from scratch?
by Dennis Olsson 08 Sep '14

08 Sep '14

Hi there, I need to setup our own OBS server (without internet access) for the architectures Intel "x86_64" and ARM "armv5tel". I am using the OBS Appliance v2.5.4.3 downloaded from: http://openbuildservice.org/download/ running as a VM in VirtualBox having 3 discs: sda1 root 97GiB / sda2 swap 2GiB swap sdb1 LVM 25GiB vg:OBS:cache /var/cache/obs/worker rest vg:OBS:worker_{root,swap}_[1..8] /var/cache/obs/worker/root_[1..8] sdc1 LVM 300 GiB vg:data:server /srv/obs I have tried to make use of the following recipes to get such a stand-alone OBS server up and running, but so far it has all been in vain (have tried multiple times, but have not even been able to get a reproducible result each time so far): 1. From Open Build Service documentation, Chapter 5 Boot Strapping: http://openbuildservice.org/help/manuals/obs-best-practices/cha.obs.best-pr… 2. From the reference made in Chap. 5: http://en.opensuse.org/openSUSE:Build_Service_private_instance_boot_strappi… 3. From the "README.SETUP" found in the source repository of OBS: https://github.com/openSUSE/open-build-service/blob/2.5/dist/README.SETUP The recipes are either completely outdated (using references to non-existing projects / domains (1 and 2)) or either referring to features in OBS that are not available anymore (in OBS v2.5) or outdated versions of OBS altogether (2 and 3)! E.g. the instructions described in "README.SETUP" in chapter 6 simply cannot work anymore in OBS v2.5, because port 81 is not available anymore, just to mention one among other things. So, what does one have to do, to bootstrap an OBS v2.5.4 server for the Intel "x86_64" and ARM "armv5tel" architectures from scratch? For the bootstrapping itself, I would be able to have internet access, if need be, but after having gotten the OBS server fully bootstrapped, it must be able to continue to work without any internet access. Many thanks in advance & Mit freundlichen Grüßen, | Med venlig hilsen | Best regards, Dennis Olsson ______________________________________________________________ Dennis Olsson | devolo AG | Software Engineer & Developer Charlottenburger Allee 60 | D-52068 Aachen | Germany HRB 8931 Amtsgericht Aachen

1 0

[opensuse-buildservice] [obs-signd] user documentation for sign.c
by Valentin Gologuzov 06 Sep '14

06 Sep '14

Hi, all! I am working on the Copr lightweight build service ( http://fedorahosted.org/copr ) and we want to utilize obs-signd for package signing. In the past few days i've managed to run signd and use /bin/sign to manually sign rpms, but lack of up-to date documentation in the obs-signd is no good. I've tried to document my findings, and I would be glad if authors or other person familiar with signd will review and correct (or even add :) ) manpage. Changes available in attachement or here https://github.com/evilkost/obs-sign/commit/0d68bd8ea34e507c1212d12ce03cab7… . -- Best regards, Gologuzov Valentin.

2 1