We currently use OBS for building and publishing APT packages for the
Apertis project (a Debian derivative distribution).
At the moment we use downstream patches for the publisher
(src/backend/bs_publish) in order to use reprepro instead of
As we're considering implementing a new APT publisher based on aptly,
we'd like to do so in a way that can be upstreamed to OBS so it can
benefit the whole community. This obviously raises several questions as
to how we should proceed, so I'm sending this email as a call for
We're considering the following:
- this new publisher would be implemented in addition to the existing
dpkg-scan* based one and be selectable through global configuration options.
- using aptly opens up possibilities, but it isn't always as
straightforward as a few system() call; we would therefore need to
either ship a helper tool or add a new BSPublisher submodule (the latter
is the preferred option atm)
- aptly can also be used through a REST API, which implies some
asynchronous processing would be preferrable. Is there currently a way
to handle async processing in OBS, or would that require another helper
tool/module, if possible at all?
We're only at the planning and design stage for now, so we would be very
interested in your opinion and comments regarding the above.
While looking at boo, I noticed that the kernel and initrd of the VM
workers are different for different jobs.
For example, for SLES, qemu uses the kernel and initrd under
/var/cache/obs/worker/root_*/.mount/boot/kernel. But for CentOS, it uses
kernel under /boot. It looks like the SLES worker even runs the exact
kernel version of the target OS.
Could some one let me know how can I set my instance to run in such way?
I have a preinstallimage for my project, but I noticed that some
packages did used it, but some didn't. I tried to find out why but
cannot find useful information from build log or server scheduler log.
Could anyone help point out how to debug this issue? Thanks.
# osc maintainer sddm
Server returned an error: HTTP Error 401: Unauthorized
What must I do to get the desired result? I set an account up many years ago,
rarely use it. I tried first osc maintainer inxi, because I thought I might like
to try becoming a maintainer for this simple purpose of making a non-antique inxi
available to Leap users. Its maintainer doesn't seem interested in non-broken inxi
except for TW users, making forum support seriously annoying to provide to Leap users.
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
I'm encountering an issue regarding access through `curl` and python's `requests` against `build.opensuse.org`
Using `osc` when running
osc api /source
work with no trouble and lists the projects.
But I didn't got that to work outside of `osc`
Whatever I do regarding basic auth headers (build it myself, let curl/requests do it), I get a error 401 with :
<summary>Anonymous user is not allowed here - please login</summary>
Full connection log : 
Password is known good as it works in `osc` (fails even if I try to get it from GNOME-keyring through `python-keyring`)
What could be my issue?
We released a number of updates for OBS 2.10 to support latest Ubuntu 21.10.
It is using zstd for control file compression which required a number of changes.
obs packages itself are not affected, but you will need to update
as provided by the OBS repository to be able to build for current Ubuntu.
(Debian itself is not affected and even does not support zstd compressed control
files either yet).
There will also be a new osc release soon to support local builds as well.
Adrian Schroeter <adrian(a)suse.de>
Build Infrastructure Project Manager
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
(HRB 247165, AG München), Geschäftsführer: Felix Imendörffer
I got a RPM repository which has the quite common layout:
I tried to add it as a DoD repository. Then I noticed that:
1. I need to use the same URL for x86_64 and aarch64 repos. Will this
cause any problem?
2. There is no "noarch" to select in the architecture list. So how can I
get those noarch packages downloaded when need? It seems currently
all packages in noarch are not picked thus I have a lot of packages