Hi all,
I'm setting up an internal OBS instance that builds packages for Ubuntu
16.04, and I'm wondering: is there a way to pre-emptively install a
package in the chroot before installing the package's build
dependencies? I would like to unconditionally install the pkg-create-
dbgsym package when building for Ubuntu 16.04.
Kyle
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello,
I am trying to figure out the correct syntax,
the guide I found doesn't clearly state it / show an example.
Maybe I have already found the correct one but sometimes
changing this value breaks the scheduler on my local obs,
sometimes other quirks and it may not have had recovered,
if one of the following was to be correct:
Repotype: prestodelta splitdebug:-debuginfo
#Repotype: rpm-md options:prestodelta splitdebug:-debuginfo
#Repotype: rpm-md options:prestodelta splitdebug:-debuginfo
#Repotype: rpm-md options:-prestodelta splitdebug:-debuginfo
#Repotype: rpm-md:-prestodelta splitdebug:-debuginfo
#Repotype: rpm-md[:prestodelta] splitdebug:-debuginfo
#Repotype: rpm-md[prestodelta] splitdebug:-debuginfo
#Repotype: rpm-md:prestodelta splitdebug:-debuginfo
I'd appreciate if you can point me to which syntax is correct.
Thanks,
Damian
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
I am currently working on updating the OBS z/VM Worker implementation.
Currently, package building works without issues, but container
building fails. The reason seems to be that I do have a mismatch
between installed and running kernel.
In the original implementation, the system just takes the kernel image
from the controlling guest to make the actual builder bootable.
However, this typically is not kernel-obs-build. Now, the
kernel-obs-build package does not provide the image file
below /boot/image to make the system bootable via the s390x bootloader
zipl. Therefore, I am a bit stuck and don't exactly know how to
proceed. There are several possibilities, and I would like to hear what
would be a preferred solution:
1. Add the image file to kernel-obs-build for s390x. This would allow
me to just use the provided image file to make the target disk bootable.
2. Setup the two stage bootprocess with grub and do a kexec boot during
the build process to reboot the worker with the current kernel.
3. Boot the worker over the reader. In that case I would not need zipl
and kernel-obs-build would be sufficient to boot. This is similar to
booting for Installation.
4. ??? I have no idea what else could be done. Maybe you have some
suggestion.
Any suggestions are welcome.
Thanks
Berthold (azouhr(a)opensuse.org)
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hello everyone,
Qactus 2.0.0 has been released!
This version comes with a much improved OBS browser and revamped UI; there are
more actions available for projects/packages such as submit, copy, link and
properties. Please take into account that the MetaConfigEditor (edit package/
project) is in beta, so use it with care.
http://www.javierllorente.com/2020/04/20/qactus-v2-0-0-is-out/
Greetings,
--
Javier Llorente
Hi,
Is there a way to ignore this error and continue with build,
may sound strange but the link targets don't exist on purpose
and no rpm will provide them.
>>ERROR: link target doesn't exist (neither in build root nor in installed system):
Thanks in advance,
Damian
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hey all,
Can we get Fedora 32 added? Fedora 32 GA is next Tuesday[1].
[1]: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-04-23/f32-final-go_…
--
真実はいつも一つ!/ Always, there's only one truth!
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
I am trying to setup a new tumbleweed_into_dir, install obs and run it
as nspawn container,
using the OBS:/Server:/Unstable/openSUSE_Factory repo
So far it works except that signing fails and building for anything
that requires make.
At the end of the email you will find the commands used to setup
everything so far.
I would like to know if someone has a suggestion how to fix build and
signing issue.
The build process log show various /dev/null permission denied and
someObsDir/dev/loopback's
mknod failed
Adding --property='DevicePolicy=auto' to nspawn command which should
allow all devices,
had no effect, although I am not absolutely sure if this isn't ignore
because of another conf file somewhere.
mkdir obs_server && cd obs_server
sudo mkdir -p sys proc dev etc/zypp/repos.d
sudo mount -t proc proc proc/
sudo mount -o bind /sys sys/
sudo mount -o bind /dev dev/
sudo zypper --no-gpg-checks --non-interactive --cache-dir
/var/cache/zypp --root obs_server in --allow-unsigned-rpm
--auto-agree-with-licenses filesystem bash permissions
sudo zypper --no-gpg-checks --non-interactive --cache-dir
/var/cache/zypp --root obs_server in --allow-unsigned-rpm
--auto-agree-with-licenses filesystem bash bash-completion cpio
coreutils glibc permissions systemd systemd-rpm-macros
systemd-presets-branding-openSUSE distribution-logos-Novos rpm zypper
nano system-group-wheel system-group-hardware system-user-bin
system-user-root system-user-nobody sudo systemd-network yast2-network
NetworkManager nmcli-dmenu mariadb systemd-container
sudo zypper --no-gpg-checks --non-interactive --cache-dir
/var/cache/zypp --root obs_server in --allow-unsigned-rpm
--replacefiles --auto-agree-with-licenses -t pattern OBS_Server
#bind later by nspawn must be removed
sudo rm obs_server/etc/resolv.conf
sudo umount -l proc
sudo umount -l dev
sudo umount -l sys
#boot it
sudo systemd-nspawn -D /path/to/obs -b --resolv-conf=bind-host --capability=all
#from another console
sudo machinectl --machine obs_server shell
#run it and ignore all errors for now
# at hostname give it localhost
/usr/lib/obs/server/setup-appliance.sh --force
#required? /etc/sign.conf add allow localhost allow localhost.localdomain
#below is required on every container boot at the moment
#/run is a temp overlay into the container
mkdir -p /run/mysql/ /run/passenger/ && chmod -R 777 /run/mysql/
#chown -R mysql:mysql /run/mysql fails - no such group mysql though it exist
#private-users=pick --private-users-chown for systemd-nspawn may fix this
#but on opensuse these two break nspawn-boot
systemctl restart mariadb
systemctl restart apache2
on the host you can open the web broweser and go to 127.0.0.1
Regards,
Damian
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
since I fought with a new local OBS setup for the last two days, it's time to
fix the bouquet of misleading/dead wrong signer guide on the wiki. (No, the
signer wasn't the reason for the fight. That was /usr/sbin/obsstoragesetup.
But that's a different story..).
Before I start to fix the wiki, can we agree on a couple of facts beforehand?
Section: Required Packages
I think, it's save to remove all paragraphs after the item enumeration.
Section: Set up the GPG key
I would remove:
Some programs[which?] cannot handle DSA 2048, so if you are actually affected,
you may want to limit yourself to a 1024 bit-DSA key instead.
Section: Prep the signer
Phrases go to /srv/obs/gnupg<fullstop>
The symlink is unnecessary.
Section: Configure the signer
For the appliance at least, the key *have* to be in /srv/obs/obs-default-
gpg.asc. Contraventions will be punished by prolonged troubleshooting, that
will likely end in /usr/lib/obs/server/setup-appliance.sh function
prepare_obssigner...
A further note for sign_project is advised (and relocated from troubleshooting
section).
Outdated:
If you run a version older than obs-signd-2.1.2 where /etc/permissions.d/sign
is missing, create this file and add to it:
/usr/bin/sign root:obsrun 4750
Run SuSEconfig --module permissions after having created this file.
Remove?
Section: Activate the Signer
We arrived in systemd age.
Section: Signing EFI binaries/kernel modules for EFI Secure Boot
and below: out of my capabilities.
Comments please.
Cheers,
Pete
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
vdvfdv
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org
Hi,
I would like to see something similar to https://github.com/pricing
with private repositories in obs.
It seems there is even some code that should do that from
packmans obs instance.
[ ] Hide the entire project
[ ] Deny access to sources of project
I imagine that there could be others interested who
do not wish do have their own obs instance but use an already hosted obs
to build for Linux distributions (maybe more).
My 2 Pfennigs,
Damian
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org