Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#80333 - [python-pytorch-opt-rocm] Does not provide a version string for python-pytorch-rocm 'provides' field

Attached to Project: Arch Linux
Opened by Christopher Snowhill (kode54) - Thursday, 23 November 2023, 01:20 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:21 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Konstantin Gizdov (kgizdov)
Torsten Keßler (tpkessler)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The opt packages do not affix a version string to their provides fields for the non-opt packages, so downstream packages which depend on specific versions will force installation of the non-opt package.

Additional info:
* package version(s)
python-pytorch-opt-rocm 2.1.0-1

Steps to reproduce:
1. Install python-pytorch-opt-rocm
2. Attempt to build and install python-torchvision-rocm 0.16.1 from the AUR
3. Get asked to replace python-pytorch-opt-rocm with python-pytorch-rocm due to latest AUR package adding the `>=2.1.0` qualifier to the package.
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:21 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/python-pytorch/issues/ 3
Comment by Christopher Snowhill (kode54) - Thursday, 23 November 2023, 01:32 GMT
Upon further inspection, it appears all of the variant subpackages need:

```
=${pkgver}
```

on all of their provides= values. So this isn't just specific to the rocm packages, or to just the opt variants, but to all variants and anything downstream checking a base package name with a version qualifier.
Comment by Toolybird (Toolybird) - Friday, 24 November 2023, 05:32 GMT
Yeah, it's a bit subtle and easy to overlook. I had to simulate it with dummy pkgs to figure out what was going on. In actual fact, this requirement is detailed in the Wiki [1] (refer the "Note:" block.)

Although, it could be argued that there is no problem with the main repo pkgs. It's only a problem now because an AUR pkg decided to depend on a *version* of the "provided" pkg.

[1] https://wiki.archlinux.org/title/PKGBUILD#provides

Loading...