Mailinglist Archive: opensuse-bugs (4156 mails)

< Previous Next >
[Bug 739910] New: Apper: Uses filenames found in "/etc/zypp/repos.d" to infer repository name in update dialogue
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 6 Jan 2012 09:26:23 +0000
  • Message-id: <bug-739910-21960@http.bugzilla.novell.com/>

https://bugzilla.novell.com/show_bug.cgi?id=739910

https://bugzilla.novell.com/show_bug.cgi?id=739910#c0


Summary: Apper: Uses filenames found in "/etc/zypp/repos.d" to
infer repository name in update dialogue
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: 64bit
OS/Version: SuSE Other
Status: NEW
Severity: Minor
Priority: P5 - None
Component: KDE4 Applications
AssignedTo: kde-maintainers@xxxxxxx
ReportedBy: lukrez.forums@xxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---


User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20100101
Firefox/9.0

Apper always presented me upgrades originating from repository
"openSUSE-11.4-Update" despite using openSUSE 12.1 (upgraded from 11.4) and
having changed base repositories accordingly.

I discovered, that the file names containing the repository configuration found
in "/etc/zypp/repos.d" still reflect the old configuration:

/etc/zypp/repos.d> cat openSUSE-11.4-Update.repo
[openSUSE-11.4-Update]
name=openSUSE-12.1-Update
enabled=1
autorefresh=1
baseurl=http://download.opensuse.org/update/openSUSE-current//
path=/
type=rpm-md
priority=20
keeppackages=0

Apper should use the configured name "openSUSE-12.1-Update" in order to present
the user the repository to update from.

Reproducible: Always

Steps to Reproduce:
* Update from openSUSE 11.4 and edit base repository accordingly
* Use Apper to get notifications on updates/upgrades

Actual Results:
Apper uses old repository name, as inferred from file names found in
"/etc/zypp/repos.d".

Expected Results:
Apper should use the configured repository name.

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
This Thread
  • No further messages