Problem while using an OBS generated repository on ArchLinux

[fabiocosta0305]

Issue Description

When trying to update some packages from an Arch repository for OBS generated packages, receive a 404 error

Expected Result

Pacman (Arch Linux package manager) would update the files generated

How to Reproduce

1. Add an repository on /etc/pacman.conf

Example:

[home_PerryWerneck_pw3270_Arch]
SigLevel = Never
Server = https://download.opensuse.org/repositories/home:/PerryWerneck:/pw3270/Arch/$arch

2. Use pacman to run the update and/or install package - pacman -Syu and/or pacman -S pw3270
3. It would install, but now it doesn't download with a 404 error

Further Information

• A link to an OBS instance showing the issue
  https://download.opensuse.org/repositories/home:/PerryWerneck:/pw3270

• A pacman -Syu --debug output
  https://www.pastery.net/mzgvkd/

By what I detected, OBS is still listing tar.gz files on the OBS repository .db files, altought it builds proper .tar.zst files, as accepted now by pacman.

A more complete documentation is on the original software issue

PerryWerneck/pw3270#10 (comment)

[M0ses]

I could not reproduce this error in a test VM - does the problem still persists?

[neodarksoldier]

I'm having the same issue:

error: failed retrieving file 'pw3270-5.3-0-x86_64.pkg.tar.xz' from download.opensuse.org : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.

[adrianschroeter]

this could be an infrastructure problem or the way how we generate repos or a bug on the client side.

However, without any concrete example and used URLs and possible redirections you get we can not follow up on this.

So please report exact URL's, the pacman output and check also the redirection header with curl (because the content is not delivered by download.opensuse.org and you may get a different redirecition then we do)

[neodarksoldier]

Thank you for replying so fast. I'm not very good at debugging. I have attached a file with some data. Not sure if it helps.
pw3270-arch.txt

[hawkeye116477]

I had similar problem and seems that's because it tries to download package from mirror, but mirror doesn't have yet that package or version of that package, so it shows 404. Workaround is to replace download.opensuse.org with downloadcontent.opensuse.org.

[maxrd2]

I have the same problem on my home repo: https://build.opensuse.org/project/show/home:maxrd2

Relative repository is here: https://download.opensuse.org/repositories/home:/maxrd2/Arch/x86_64/
Problem is that home_maxrd2_Arch.db file contains reference to the old package version subtitlecomposer-git-0.7.0.211git7f28c7d3-1 that was built several days ago, instead of latest successfully built version subtitlecomposer-git-0.7.0.216git43f11913-1-x86_64.pkg.tar.zst

EDIT: just saw previous comment. Replacing download.opensuse.org with downloadcontent.opensuse.org downloads correct file.

I'm nut sure how caching on mirror is implemented, maybe that strict-transport-security: max-age=31536000 has something to do with it?

EDIT2: The mirror to which download.opensuse.com redirects has old .db version (header Last-Modified: Sat, 28 Nov 2020 00:16:22 GMT) while correct version is served from downloadcontent.opensuse.org with header last-modified: Wed, 02 Dec 2020 16:50:28 GMT.

$ curl -I https://download.opensuse.org/repositories/home:/maxrd2/Arch/x86_64/home_maxrd2_Arch.db
HTTP/2 302 
date: Wed, 02 Dec 2020 16:51:49 GMT
server: Apache/2.4.43 (Linux/SUSE)
x-mirrorbrain-mirror: ftp2.nluug.nl
x-mirrorbrain-realm: region
link: <https://download.opensuse.org/repositories/home:/maxrd2/Arch/x86_64/home_maxrd2_Arch.db.meta4>; rel=describedby; type="application/metalink4+xml"
link: <http://ftp2.nluug.nl/os/Linux/distr/opensuse/repositories/home:/maxrd2/Arch/x86_64/home_maxrd2_Arch.db>; rel=duplicate; pri=1; geo=nl
link: <http://ftp1.nluug.nl/os/Linux/distr/opensuse/repositories/home:/maxrd2/Arch/x86_64/home_maxrd2_Arch.db>; rel=duplicate; pri=2; geo=nl
location: http://ftp2.nluug.nl/os/Linux/distr/opensuse/repositories/home:/maxrd2/Arch/x86_64/home_maxrd2_Arch.db
content-type: text/html; charset=iso-8859-1

$ curl -I http://ftp2.nluug.nl/os/Linux/distr/opensuse/repositories/home:/maxrd2/Arch/x86_64/home_maxrd2_Arch.db
HTTP/1.1 200 OK
Date: Wed, 02 Dec 2020 16:52:55 GMT
Server: Apache/2.2.15 (CentOS)
Last-Modified: Sat, 28 Nov 2020 00:16:22 GMT
ETag: "7c018601a-626-5b51fafd3b283"
Accept-Ranges: bytes
Content-Length: 1574
Content-Type: application/x-tar
Content-Encoding: x-gzip

$ curl -I https://downloadcontent.opensuse.org/repositories/home:/maxrd2/Arch/x86_64/home_maxrd2_Arch.db
HTTP/2 200 
server: nginx
date: Wed, 02 Dec 2020 16:53:27 GMT
content-type: application/octet-stream
content-length: 1589
last-modified: Wed, 02 Dec 2020 16:50:28 GMT
etag: "5fc7c5d4-635"
strict-transport-security: max-age=31536000
accept-ranges: bytes

[redtide]

I'm not sure this is related to the current issue, but Arch build reports a fatal: unable to access 'https://github.com/sfztools/sfizz-ui/': Could not resolve host: github.com error.
I gave a look to stackoverflow and it seems it might be a proxy issue.

Click to view log

[   26s] now finalizing build dir...
[   26s] SIOCSIFADDR: File exists
[   26s] Running build time source services...
[   26s] Preparing sources...
[   30s] Cloning into bare repository '/usr/src/packages/SOURCES/sfizz-ui'...
[   30s] fatal: unable to access 'https://github.com/sfztools/sfizz-ui/': Could not resolve host: github.com
[   30s] ==> ERROR: Failure while downloading sfizz-ui git repo
[   30s]     Aborting...
[   30s] failed to prepare sources
[   30s] ### VM INTERACTION START ###
[   31s] [   21.928756][    T1] sysrq: Power Off
[   31s] [   21.930894][  T195] reboot: Power down
[   31s] ### VM INTERACTION END ###
[   31s] 
[   31s] sheep87 failed "build _service:set_version:PKGBUILD" at Tue May 23 22:34:33 UTC 2023.
[   31s] 

[hennevogel]

@redtide builds on OBS have no network access. please take this to the mailing list, this is not a support forum.