Dominik Heidler
Dominik Heidler
[](https://www.bountysource.com/issues/27791158-feature-request-message-archive-management)
Looking at the OBS API docs, I don't see a way to query for description: https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.binary_tracking.html#id-1.5.10.12.6 Also this is referring to a package regarding OBS logic, but an OBS package...
I'm not 100% sure if I understood what you mean. Opi is getting installed into a python version specific directory: ``` rpm -ql opi | head /usr/bin/opi /usr/lib/python3.8/site-packages/opi /usr/lib/python3.8/site-packages/opi-2.4.7-py3.8.egg-info /usr/lib/python3.8/site-packages/opi/__init__.py...
One one side that could be faster in some situations but on the other side a user could want to remove the repo when he aborted the installation. So I...
`gh` is already included in the default repo of tumbleweed (not the latest release, though). Is there a specific reason why you prefer the upstream repo?
The reason for this seems to be that _gifski_ build in the devel project (`graphics`) agaist both Tumbleweed and Factory: https://build.opensuse.org/package/show/graphics/gifski This is not the case for other packages like...
```python >>> binaries = opi.search_published_binary('openSUSE', 'gifski') >>> pprint(binaries) [{'arch': 'x86_64', 'baseproject': 'openSUSE:Factory', 'filename': 'gifski-20211001.git.b804a8b-1.1.x86_64.rpm', 'filepath': 'graphics/openSUSE_Factory/x86_64/gifski-20211001.git.b804a8b-1.1.x86_64.rpm', 'name': 'gifski', 'obs_instance': 'openSUSE', 'package': 'gifski', 'project': 'graphics', 'release': '1.1', 'repository': 'openSUSE_Factory', 'type': 'rpm',...
I guess that the xpath query is only matching the baseproject here which is `openSUSE:Factory` in both cases. Only the `repository` entry seems to distinguish them. ```perl contains-ic(@name, 'gifski') and...
That stuff seems to be managed at https://github.com/openSUSE/openSUSE-welcome
Am 13. Dezember 2018 20:52:12 MEZ schrieb Frieder Steinmetz : >Can we just agree to pretend you did not open this issue almost a year >ago? :-/ Sure :)