Bug 1146085 - tumbleweed does not understand /history URL as installation source
tumbleweed does not understand /history URL as installation source
Status: REOPENED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem
Current
x86-64 Linux
: P5 - None : Normal (vote)
: ---
Assigned To: Jimmy Berry
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-08-19 08:11 UTC by Olaf Hering
Modified: 2020-09-21 13:40 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olaf Hering 2019-08-19 08:11:28 UTC
If a system is installed from http://download.opensuse.org/history/ instead of http://download.opensuse.org/tumbleweed/, tumbleweed-cli is unable to maintain repositories.
Apparently it expects to be installed from the ever-changing tree, instead of the fixed snapshot that does not change (until it disappears).

After install baseurl= will be identical to the install= URL, which is something like  http://download.opensuse.org/history/20190810/tumbleweed/repo/oss
There is no '$snapshotVersion' in the URL.
Comment 1 Marco Strigl 2020-09-21 08:29:02 UTC
Is this still an issue?
I am not sure what I can do to fix this bug...
Comment 2 Olaf Hering 2020-09-21 09:29:04 UTC
Still broken, with 20200917 as install= URL.
Comment 3 Dominique Leuenberger 2020-09-21 11:58:19 UTC
IMHO, this is far out of what TW is supposedly doing.

The installer will take whatever URL you pass it. /history is an attempt to help people slowing down the progress and stick to a snapshot and still allow to install packages.

Installing from a specific /history provided snapshot and expecting things to 'just work out' is unrealistic.
Comment 4 Olaf Hering 2020-09-21 13:22:33 UTC
There is an obvious difference between 'TW' and 'tumbleweed.rpm'.

The latter can easily detect what the current repo is. Someone familiar with the tool just has to fix it.