Bug 55526 – Local repository server - suggest setting the start version

Bug 55526 - Local repository server - suggest setting the start version


Summary:	Local repository server - suggest setting the start version

Status:	NEW

Product:	UCS manual
Classification:	Unclassified
Component:	General
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Docu maintainers
QA Contact:	Docu maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2023-01-03 13:16 CET by Lukas Zumvorde
Modified:	2023-04-27 17:26 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.137
Enterprise Customer affected?:	Yes
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Usability
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Lukas Zumvorde

2023-01-03 13:16:50 CET

If one installs a new repository server on a UCS with a version >5.0-0 (for example 5.0-2) the UCRV repository/mirror/version/start and repository/mirror/version/end are being set to the current version (for example 5.0-2). This results in the repository not containing any UCS versions from UCS 5.0-0 up to the current one. 
We should add a note to the manual suggesting to set the UCRV repository/mirror/version/start and repository/mirror/version/end.

- Where is the documentation gap that needs a change needed? 
  The change should be made in https://docs.software-univention.de/manual/5.0/de/software/repository-server.html#software-create-repo
- What information did the documentation not deliver that you needed? What questions does the documentation not answer? What is missing?
  The need to set repository/mirror/version/start to the major release version if one wants to use the repository for an upgrade from an earlier version should be mentioned. 
- What is the impact of the documentation gap?
  The repository mirror will not work as expected by the user.
- Who benefits from closing the documentation gap?
  The administrators of UCS systems with local repository mirrors. 
- Why do you think should it be documented?
  Upgrades are a major use case for local repository mirrors. We should make the documentation as intuitive and easy as we can. This includes mentioning this use case.

Comment 2 Stefan Gohmann

2023-04-27 17:26:38 CEST

Remove "Waiting Support" issue because it doesn't match our criteria. "How will those affected feel about the bug?" has to be 3 or higher.