Hi,
We currently use OBS for building and publishing APT packages for the
Apertis project[1] (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
dpkg-scanpackages/dpkg-scansources.
As we're considering implementing a new APT publisher based on aptly[2],
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
advice/comments/suggestions.
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.
Thanks,
Arnaud
[1] https://apertis.org
[2] https://aptly.info
I've been having trouble getting deno to build since v1.9.0 (April 13th,
2021) on x86_64.
Tried various _constraints values, but the job is failing with the same
error:
[ 3311s] LLVM ERROR: IO failure on output stream: No space left on device
[ 3311s] /.build/build-vm: line 460: echo: write error: No space left on device
[ 3312s] error: could not compile `deno`
[ 3312s]
https://build.opensuse.org/package/show/devel:languages:javascript/deno#com…
Can anyone advise?
Thanks,
avindra goolcharan
Hello all,
since the release of 15.3 is near I'd like to test it on our internal OBS (2.10).
I created a new project with a download on demand repository like this
--- snip ---
<project name="openSUSE.org:Leap:15.3">
<title>openSUSE Leap 15.3 OSS (DoD)</title>
<description>dod</description>
<person userid="x" role="maintainer"/>
<repository name="standard">
<download arch="x86_64"
url="http://download.opensuse.org/distribution/leap/15.3/repo/oss/" repotype="rpmmd"/>
<arch>x86_64</arch>
</repository>
</project>
--- snap ---
I also copied the project configuration from api.opensuse.org/openSUSE:Leap:15.3.
But when I try to use my new repo all I get in the webgui is a red warning sign and
the message
The repository setup is broken, build or publish not possible
Looking into /srv/obs/log/dodup.log only gives me
--- snip ---
obs:/srv/obs/log # grep 15.3 dodup.log
2021-05-10 00:37:34: [1622] checking openSUSE.org:Leap:15.3/standard/x86_64...
updating metadata for rpmmd repo at
http://download.opensuse.org/distribution/leap/15.3/repo/oss/
2021-05-10 00:44:34: [1622] checking PRESENSE/openSUSE_Leap_15.3/x86_64...
updating metadata for rpmmd repo at
http://download.opensuse.org/distribution/leap/15.3/repo/oss/
2021-05-10 00:49:57: [1622] checking openSUSE.org:Leap:15.3/standard/x86_64...
updating metadata for rpmmd repo at
http://download.opensuse.org/distribution/leap/15.3/repo/oss/
--- snap ---
The same worked perfectly for openSUSE Leap 15.*2*.
Has anything changed or how do I proceed to pinpoint the error?
Thanks and regards -- Till
--
Dipl.-Inform. Till Dörges doerges(a)pre-sense.de
PRESENSE Technologies GmbH Nagelsweg 41, D-20097 HH
Geschäftsführer/Managing Directors AG Hamburg, HRB 107844
Till Dörges, Jürgen Sander USt-IdNr.: DE263765024
Hi,
tl;dr if you rely on package reviews for your development process in OBS
make sure requests have a revision. Only osc shows the information you
are looking for.
Turns out submit request in OBS do not necessarily refer to a specific
revision in the originating package. Means the sources can change after
a review passed. Unfortunately changing the sources does not reset
reviews and reviews do not record the revision they were done for. That
obviously defeats the purpose of source reviews. Accepting a request
without revision may therefore lead to accepting something different
from what was reviewed (resp staged).
AFAIK this feature has been in OBS since the very beginning, it's just
well hidden as the official interfaces osc and the webui do add a
revision when creating requests. There is no way to turn that off
either. Also tools such as bots that use osc as python module
automatically generate submit request with revision. This is not because
the server enforces it but because the client code does it.
So anyone who wants to fool reviewers just has to use a custom client.
According to the OBS team this hidden behavior is actually considered a
feature. The security team doesn't treat it as security issue as it's
kind of documented¹, even though osc doesn't behave in the documented way.
There are plans to add a special attribute to disallow unversioned
requests per project². IMHO a global setting to require revisions by
default with the option for exceptions would have been more sensible.
Anyway, apparently the fix needs some time to ripe still.
Meanwhile the factory-auto bot was enhanced to decline unversioned
requests to Factory (thanks Fabian).
If you are using reviews in eg your devel project or run your own OBS
you need to create your own bot or watch out manually. The webui does
not seem to display any revision at all, so not helpful.
In osc it looks like this:
Request: #12345
submit: foo:bar/baz@42 -> blah
Absence of the @number means no revision.
cu
Ludwig
[1]
https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.request_an…
[2] https://github.com/openSUSE/open-build-service/pull/10992
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.com/
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer
HRB 36809 (AG Nürnberg)
Hey everyone,
we've been hard at work on extending the integration between OBS and
GitHub/GitLab. We're looking forward to hear from you on the subject.
Have a look at our latest blog post for details:
https://openbuildservice.org/2021/05/31/scm-integration/
Best regards
Dany from the Build Solutions team
--
Dany Marcoux <dmarcoux(a)suse.de>
Full Stack Web Developer - Open Build Service
SUSE Linux GmbH
Maxfeldstrasse 5
90409 Nürnberg
Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
Hi,
just sadly noticed that a Project Maintainer can't edit his projects
Attributes.
The Maintainer User is not an OBS admin.
Seems only an OBS admin is able to edit Project Attributes
Is this a Feature or a BUG ?
--
Christian
------------------------------------------------------------
https://join.worldcommunitygrid.org?recruiterId=177038
------------------------------------------------------------
https://www.sc24.de - Sportbekleidung
------------------------------------------------------------
An setting is missing for Fedora_Rawhide:
have choice for libusb-1.0.so.0()(64bit) needed by libgusb: libusb1 libusbxh
have choice for libusb-1.0.so.0 needed by libgusb: libusb1 libusbx
Regards,
Martin
nowadays <a href="https://www.wavemaker.com/low-code-app-development-platform/">low code platforms</a> are becoming prominent,and time saving for the business. even with minimal coding knowledge people can create apps. so many businesses are opting for it.