Bug 413737

Summary:	zypper ll always prints (any) for repository
Product:	[openSUSE] openSUSE 11.0	Reporter:	Robert Munteanu <rombert>
Component:	libzypp	Assignee:	Jan Kupec <jkupec>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Minor
Priority:	P4 - Low	CC:	felipe.alvarez
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	openSUSE 11.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Robert Munteanu 2008-07-31 20:21:45 UTC

robert@nazgul:~> zypper lr | grep ^4
4  | http://ftp.skynet.be/pub/packman/suse/11.0/                                         | Packman Repository                                                 | Yes     | Yes
robert@nazgul:~> sudo zypper al -r 4 pulseaudio
Reading installed packages...
Specified lock has been successfully added.
robert@nazgul:~> zypper ll
# | Name            | Type    | Repository
--+-----------------+---------+-----------
1 | ktorrent        | package | (any)
2 | ktorrent-lang   | package | (any)
3 | libflashsupport | package | (any)
4 | pulseaudio      | package | (any)

Comment 1 Jan Kupec 2008-10-13 14:06:37 UTC

Thanx! Seems this is fixed in latest zypper (0.12.8):

(root@kompost)-(~)$ zypper al -r 2 foo
Specified lock has been successfully added.
(root@kompost)-(~)$ zypper ll
# │ Name │ Type    │ Repository
──┼──────┼─────────┼────────────
1 │ foo  │ package │ factory-nos

Comment 2 Jan Kupec 2008-10-26 22:25:56 UTC

*** Bug 438943 has been marked as a duplicate of this bug. ***

Comment 3 Felipe Alvarez 2008-10-28 03:11:49 UTC

Will this fix eventually find its way into openSUSE Updates?

Comment 4 Jan Kupec 2008-10-28 16:55:09 UTC

No :O( it's a minor problem, we can't backport each such fix.

Comment 5 Felipe Alvarez 2008-10-28 19:22:13 UTC

Thanks for the reply. Is this a political, ethical, or technical obstacle? I'm sort of new to backporting issue.

Comment 6 Jan Kupec 2008-10-28 21:28:39 UTC

Yes it's a policy, and there are strong arguments behind it. Applying a fix to an older code can be problematic (the code may be completely different - more work, the fix can introduce a new bug - risky for stable release, resources problems - you could theoretically backport fixes for all older releases where applicable, but you would need much more resources, etc).

So the policy generally is to backport and release only fixes for bugs which are serious enough (security, serious functionality bug, etc). So e.g. this particular bug will be fixed in current Factory (development) distro, thus in the next stable release (11.1) and won't be fixed for 11.0 or older openSUSE stable releases. Unless the bug is considered serious enough by several people and a fix requested/approved by release managers.