Dear all,
I have a package https://build.opensuse.org/package/show/home:alvistack/libvirt-libvirt-pyth… which also build for Fedora Rawhide, but keep showing blocked with WebUI as below:
> blocked: downloading 2 dod packages
When trying to build locally with `osc build Fedora_Rawhide` it show following error message:
> remote error: http //ftp-stud.hs-esslingen.de/pub/fedora/linux/development/rawhide/Everything/x86_64/os/Packages/n/netcat-1.218-3.fc36.x86_64.rpm remote error Not Found
And I find that this netcat package is now updated as -4 release:
> http://ftp-stud.hs-esslingen.de/pub/fedora/linux/development/rawhide/Everyt…
Doesn't the block of DoD due to an outdated package list cache?
Regards,
Edison Wong
While the prjmeta of CentOS:CentOS-8 on build.opensuse.org had been
adjusted to account for the decommissioning of mirror.centos.org URLs
(replaced by vault), the same has not been done for
CentOS:CentOS-8:Stream. Please consider updating these too.
I would suggest to do a system-wide grep (e.g. /srv/obs/projects/*.xml)
for mirror.centos.org URLs.
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
The opensuse.org mirrors seem to be out of sync. Specifically, the
provo-mirror.opensuse.org server.
I tried to install some of my OBS project repositories today and got an
error.
neotinker@localhost:~> sudo zypper refresh
Repository 'SLE-Module-Basesystem15-SP3-Pool' is up to date.
Repository 'SLE-Module-Basesystem15-SP3-Updates' is up to date.
Repository 'SLES15-SP3-15.3-0' is up to date.
Repository 'SLE-Product-SLES15-SP3-Pool' is up to date.
Repository 'SLE-Product-SLES15-SP3-Updates' is up to date.
Repository 'SLE-Module-Server-Applications15-SP3-Pool' is up to date.
Repository 'SLE-Module-Server-Applications15-SP3-Updates' is up to date.
Retrieving repository 'home:neotinker3:ROS:External_Dependencies
(SLE_15_SP3)' metadata .........................................[error]
Repository 'home:neotinker3:ROS:External_Dependencies (SLE_15_SP3)' is
invalid.
[home_neotinker3_ROS_External_Dependencies|
https://download.opensuse.org/repositories/home:/neotinker3:/ROS:/External_…]
Valid metadata not found at specified URL
History:
- File
'./repodata/66b1b42b9b7789c9ef188777265e266f28093dda83d9970c01ad5d634bc35616-primary.xml.gz'
not found on medium '
https://download.opensuse.org/repositories/home:/neotinker3:/ROS:/External_…
'
- Can't provide
./repodata/66b1b42b9b7789c9ef188777265e266f28093dda83d9970c01ad5d634bc35616-primary.xml.gz
Please check if the URIs defined for this repository are pointing to a
valid repository.
Skipping repository 'home:neotinker3:ROS:External_Dependencies
(SLE_15_SP3)' because of the above error.
Retrieving repository 'Test Builds (SLE_15_SP3)' metadata
.......................................................................[error]
Repository 'Test Builds (SLE_15_SP3)' is invalid.
[home_neotinker3_ROS_External_Dependencies_Test|
https://download.opensuse.org/repositories/home:/neotinker3:/ROS:/External_…]
Valid metadata not found at specified URL
History:
- File
'./repodata/aa69665681d2905630e52c543665b0dcc99589d0a4d13abb3d42178f0a7ea700-primary.xml.gz'
not found on medium '
https://download.opensuse.org/repositories/home:/neotinker3:/ROS:/External_…
'
- Can't provide
./repodata/aa69665681d2905630e52c543665b0dcc99589d0a4d13abb3d42178f0a7ea700-primary.xml.gz
Please check if the URIs defined for this repository are pointing to a
valid repository.
Skipping repository 'Test Builds (SLE_15_SP3)' because of the above error.
Repository 'ROS Melodic for SLE 15.3 (SLE_15_SP3)' is up to date.
Repository 'ROS Infrastructure (SLE_15_SP3)' is up to date.
Some of the repositories have not been refreshed because of an error.
neotinker@localhost:~>
When I went to the repository url with my browser, the files look to be
present but I can only access the repomd.* files. The primary, other, and
filelist xml files return 404 errors.
https://download.opensuse.org/repositories/home:/neotinker3:/ROS:/External_…
If I click on the "details" link for one of the missing files, I can see
different sources to access the file. The downloadcontent.opensuse.org
link returns the file but the US mirror (provo-mirror.opensuse.org) returns
404.
https://mirrorcache.opensuse.org/repositories/home:/neotinker3:/ROS:/Extern…https://downloadcontent.opensuse.org/repositories/home:/neotinker3:/ROS:/Ex…https://provo-mirror.opensuse.org/repositories/home:/neotinker3:/ROS:/Exter…
Does anyone know what is going on with the mirrors?
Neotinker
Hi Adrian,
Am Dienstag, 29. März 2022, 16:33:29 CEST schrieb Adrian Schröter:
> On Dienstag, 29. März 2022, 16:29:16 CEST Axel Braun wrote:
> > Hi Adrian,
> >
> > Am Dienstag, 29. März 2022, 16:10:24 CEST schrieben Sie:
> > > On Dienstag, 29. März 2022, 16:07:13 CEST Axel Braun wrote:
> > > > Hi,
> > > >
> > > > when I branch an earlier revision of a package like
> > > >
> > > > osc branch -r 36 -f devel:languages:python python-cairocffi <target>
> > >
> > > that revision points to the current revision of the package in
> > > openSUSE:Factory.
> >
> > The version in Factory is the latest - rev. 39 in d:l:p
>
> exactly, but you can merge that one into the old 36 revision.
And how?
> > > So this is causing this conflict:
> > > > I get the error:
> > > >
> > > > BuildService API error: failed to branch: conflict in file python-
> > > > cairocffi.spec
> > > >
> > > > Well, it is expected that the spec file of the reveision deviates from
> > > > the
> > > > actual package. So how can I branch an earlier version?
> > >
> > > You need to have a mergeable revision or in most cases just pick one
> > > from
> > >
> > > osc buildhist ...
> >
> > osc buildhist devel:languages:python python-cairocffi 15.4 x86_64
> > time srcmd5 vers-rel.bcnt
> > rev duration
> > 2022-01-10 14:57:01 1843103fad445f3d497afca4bae8a582 1.3.0-43.1
> > 39 53
> > 2022-01-14 18:43:47 3e7538a12438c0f6d38af68f07bca8e6 1.3.0-44.1
> > 39 75
> > 2022-02-09 07:31:29 3e7538a12438c0f6d38af68f07bca8e6 1.3.0-44.2
> > 39 41
> >
> > -> all of the current release, that will not help
>
> 15.4 is a new repo, check with 15.3 repo.
That goes back to rev. 38, but not beyond (tried with a higher -l as well)
Cheers
Axel
Hi,
when I branch an earlier revision of a package like
osc branch -r 36 -f devel:languages:python python-cairocffi <target>
I get the error:
BuildService API error: failed to branch: conflict in file python-
cairocffi.spec
Well, it is expected that the spec file of the reveision deviates from the
actual package. So how can I branch an earlier version?
Cheers
Axel
Hi all,
I'm trying to beef up the packman arm workers with my army of unused
raspberry pi's.
The "primary" host is a raspberry pi400 (aarch64) running Leap 15.3,
which works reasonably well as a KVM builder.
First tries have been made with a raspberry pi3 (aarch64) running
Tumbleweed, which also works good, albeit slower due to the USB2 ports
for storage.
Now as the raspberry pi3 is a bit more useful for non-buildservice work
as another spare raspberry pi2, I'd like to add the raspberry pi2 as a
dedicated armv7l builder so that the pi400 has less packages to chew at
the end of the day and the overall rebuild times will be a bit better.
Unfortunately, the raspberry pi2 is recognized, but does not get any
packages scheduled for build:
seife@strolchi:~> osc -A pm workerinfo armv7l:seife-raspi2:1
<worker hostarch="armv7l" registerserver="http://10.8.0.1:5252"
workerid="seife-raspi2:1">
<sandbox>lxc</sandbox>
<linux>
<version>5.16.14-1</version>
<flavor>lpae</flavor>
</linux>
<hardware>
<cpu>
<flag>half</flag>
<flag>thumb</flag>
<flag>fastmult</flag>
<flag>vfp</flag>
<flag>edsp</flag>
<flag>neon</flag>
<flag>vfpv3</flag>
<flag>tls</flag>
<flag>vfpv4</flag>
<flag>idiva</flag>
<flag>idivt</flag>
<flag>vfpd32</flag>
<flag>lpae</flag>
<flag>evtstrm</flag>
</cpu>
<processors>4</processors>
<jobs>4</jobs>
<memory>896</memory>
</hardware>
</worker>
Still, it is apparently not acceptable as a worker:
seife@strolchi:~> osc -A pm checkconstraints \
Multimedia yamdi openSUSE_Tumbleweed armv7l
Worker
------
aarch64:hctw01:1
aarch64:hctw01:2
aarch64:hctw01:3
aarch64:n1sdp:1
aarch64:n1sdp:2
aarch64:seife-raspi3:1
aarch64:seife-raspi3:2
aarch64:seife-raspi3:3
aarch64:seife-raspi3:4
aarch64:seife-rpi400:1
aarch64:seife-rpi400:2
aarch64:seife-rpi400:3
The raspberry pi3 has the following workerinfo:
seife@strolchi:~> osc -A pm workerinfo aarch64:seife-raspi3:1
<worker hostarch="aarch64" registerserver="http://10.8.0.1:5252"
workerid="seife-raspi3:1">
<sandbox>kvm</sandbox>
<linux>
<version>5.16.14-1</version>
<flavor>default</flavor>
</linux>
<hardware>
<cpu>
<flag>fp</flag>
<flag>asimd</flag>
<flag>evtstrm</flag>
<flag>crc32</flag>
<flag>cpuid</flag>
</cpu>
<processors>4</processors>
<jobs>2</jobs>
<memory>444</memory>
<swap>1024</swap>
<disk>4096</disk>
</hardware>
<job>Multimedia::openSUSE_Tumbleweed::apache2-mod_musicindex-ba4acdf0de3aa9a378cc9256452fde65</job>
<arch>armv7l</arch>
<jobid>62b2b315e5b816a4ed9f71f7cda0edbf</jobid>
</worker>
I'm actually not sure if the lxc setup on the pi2 is correct, but since
it does not even get a single build job scheduled, this should not yet
matter. It also does not get anything with "chroot".
Can I find out anything about the problem from my side or can only the
PMBS admin investigate the issue (in that case, I'd probably try to set
up my own OBS instance for investigation)?
Thanks,
seife
--
Stefan Seyfried
"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
I am trying to build an i686 package in AlmaLinux but could not do it. I trying adopting your Meta Config in your AlmaLinux8 project but it asks me of Admin rights.
So far, AlmaLinux have i686 packages that is stored in x86_64 url. Can you please add i686 repository to:
https://build.opensuse.org/project/show/AlmaLinux:8
I have pushed a revision (revision 5) on my branch at https://build.opensuse.org/package/show/home:stig124:branches:Base:System/d…
Although Factory, TW and SLE12 responded correctly to the source change and built the package, neither Leap nor SLE 15 had relaunched a build, and they appear with a red warning sign.
I tried cleaning the binaries (which worked), but the build never started, even with a force re-trigger on each arch, they're all stuck on the last (revision 4) build with no possibility of retriggering the build.
Is there something that can be done for that to build, so that I can send my request after a successful build
Regards,
Nicolas FORMICHELLA
stigpro(a)outlook.fr
