Bug 757318

Summary: OCICLI - duplicating repos
Product: [openSUSE] openSUSE Tumbleweed Reporter: Daniel Pecka <nettezzaumanaa>
Component: YaST2Assignee: YaST Team <yast-internal>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Enhancement    
Priority: P3 - Medium CC: gankov, ncutler
Version: Current   
Target Milestone: Current   
Hardware: Other   
OS: Other   
URL: https://trello.com/c/aLnol1uq
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Daniel Pecka 2012-04-16 12:26:27 UTC 
User-Agent:       Opera/9.80 (Windows NT 6.1; WOW64; U; cs) Presto/2.10.229 Version/11.62

Hello,

OCICLI doesn't check if the repo is present but adds it. If there is a different name (for example you use a custom name by specifing it as zypper ar $url $custname), the repo with same url is added.

It should contain at least some basic check for repo presence by url.

regards, daniel

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Comment 1 Nathan Cutler 2017-08-13 17:12:51 UTC 
Moving to Tumbleweed so it doesn't get autoclosed.
Comment 2 Stefan Hundhammer 2019-05-21 14:30:59 UTC 
7 years old and AFAICS not at all YaST related. Closing.
Comment 3 Daniel Pecka 2019-05-22 09:20:41 UTC 
@Stefan ...

# rpm -qf `which OCICLI `
yast2-metapackage-handler-4.0.0-lp150.1.3.noarch

maybe you've put your input into wrong bugreport .. reopening

dan
Comment 4 Stefan Hundhammer 2019-05-22 10:24:02 UTC 
Since nothing whatsoever happened here within 7 years, I wouldn't get my hopes too high.
Comment 5 Nathan Cutler 2019-05-22 14:54:38 UTC 
(In reply to Stefan Hundhammer from comment #4)
> Since nothing whatsoever happened here within 7 years, I wouldn't get my
> hopes too high.

The bug was originally opened against a stable openSUSE release, so once that release went out of maintenance the bug was never looked at again. Now that it's against Tumbleweed, the bug stays on the radar.
Comment 6 Stefan Hundhammer 2019-06-03 09:41:15 UTC 
(In reply to Nathan Cutler from comment #5)
> (In reply to Stefan Hundhammer from comment #4)
> > Since nothing whatsoever happened here within 7 years, I wouldn't get my
> > hopes too high.
> 
> The bug was originally opened against a stable openSUSE release, so once
> that release went out of maintenance the bug was never looked at again. Now
> that it's against Tumbleweed, the bug stays on the radar.

All those years of inactivity speak against that theory.
Comment 7 Daniel Pecka 2019-06-03 09:47:26 UTC 
hello guys,

did fast checking ... at least in leap it's gone .. problem seems resolved .. changing status to closed ..

thanks for input & care & support

dan
Comment 8 Daniel Pecka 2019-06-03 09:48:12 UTC 
REOPENED -> RESOLVED (FIXED)