Bug 26906 - Local repos double up in MCC
Summary: Local repos double up in MCC
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-06 14:40 CEST by Herman Viaene
Modified: 2020-07-08 10:03 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Herman Viaene 2020-07-06 14:40:31 CEST
Description of problem:
Using QArepo to retrieve update packages while QA-testing.
When I add the folder where QArepo stores the packaes as a local repository, I give it a name which is different than the foldername.
This is OK and works well, but when I reboot, I get the repos twice in MCC: one time with the name I gave it, and one with the foldername. When I try to remove the second one, then the first entry is still shown but is corrupted.

Version-Release number of selected component (if applicable):


How reproducible:
When i noticed this, deleted the two entries and defined the local repo again in the same way and got the same result.

Steps to Reproduce:
1.
2.
3.
Comment 1 Lewis Smith 2020-07-06 21:08:50 CEST
This is a bit confused, Herman.
First, can you say what QArepo (after my QA time) does; is there any info about it, like a Wiki?
> When I add the folder where QArepo stores the packages as a local repository,
> I give it a name which is different than the foldername
> I get the repos twice in MCC: one time with the name I gave it,
> and one with the foldername
which reduces to "I add the folder ... I give it a name which is different than the foldername" and "one time with the name I gave it, and one with the foldername." Sorry, lost!

If you could please clarify this - particularly what you mean by "a/the name" and "foldername".
And perhaps add a screenshot illustrating "I get the repos twice in MCC".

CC: (none) => lewyssmith

Comment 2 Herman Viaene 2020-07-06 22:06:58 CEST
QARepo: see https://wiki.mageia.org/en/QA_Repo.
As you see, qarepo makes a folder "qa-testing" in the users home. In this folder it makes a local repo just for the test packages you select in it.
Then define this local repo in MCC - Software - Media - Add a custom media. In the dialogue you have to give the repo a name and refer to its actual location.
I give the name "qarepo" and refer to <userhome>qa-testing folder. OK so far, and I can select the update packages in MCC.
But when I reboot the next day for a new testing session, I get the local media with the name "qarepo" as I defined, but I get !!! additionally !!! a local media with the name "QA-Testing" and refering to the same <userhome>qa-testing folder, i.e. it took the folder name as the media name.
I can work with the qarepo tool, refresh the"qarepo" media when I change its contents etc... Biut I cann't remove the "QA-Testing" named media without blowing the setup apart.
Comment 3 Lewis Smith 2020-07-07 21:40:28 CEST
Thank you for all the explanation, it certainly helps to understand the problem.
QA Repo is a significant tool; thanks for the Wiki ref.

> But when I reboot the next day for a new testing session, I get the local media
> with the name "qarepo" as I defined, but I get !!! additionally !!! a local
> media with the name "QA-Testing" and refering to the same <userhome>qa-testing
> folder, i.e. it took the folder name as the media name
Can you supply a screenshot illustrating this?

Assigning this to the tools maintainers for MCC; CC'ing Martin for QArepo.

CC: lewyssmith => mageia
Assignee: bugsquad => mageiatools

Comment 4 Martin Whitaker 2020-07-08 09:46:12 CEST
Herman, you don't need to add the local repo to the urpmi media yourself - QARepo does that for you. See the sections

https://wiki.mageia.org/en/QA_Repo#Synchronising_and_enabling_the_local_repository

and

https://wiki.mageia.org/en/QA_Repo#Disabling_the_local_repository

I think this explains the double entries - one created by you, one automatically created.

This was meant to save you time :-)
Comment 5 Herman Viaene 2020-07-08 10:03:03 CEST
Usually, I run qarepo on my desktop, and have that one shared out (nfs) to my laptop(s). So I had to define the local repo manually.
But my desktop is out of order now (power supply gone south) and this is the first time I run qarepo locally on my test laptop. That explains why I never paid attention to those paragraphs in the wiki.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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