[Bug 433679] New: zypper -C broken in specific cases
https://bugzilla.novell.com/show_bug.cgi?id=433679 Summary: zypper -C broken in specific cases Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: admin@vbi.vt.edu QAContact: jsrain@novell.com Found By: --- It seems that the following functionality zypper in -C 'perl(Regexp::Common)' breaks while parsing the arguments in opensuse 11.0, while it worked just fine in opensuse 10.3. ~ # LANG=CC zypper -v in -C 'perl(Regexp::Common)' Verbosity: 1 Non-option program arguments: 'perl(Regexp::Common)' Initializing Target Reading installed packages... Force resolution: Yes Resolving dependencies... 'Common)' not found Force resolution: Yes Resolving dependencies... Nothing to do. While the following syntax still works as expected: ~ # LANG=CC zypper -v wp 'perl(Regexp::Common)' Verbosity: 1 Non-option program arguments: 'perl(Regexp::Common)' Initializing Target Downloading: repomd.xml [done] Reading installed packages... S | Name | Type | Version | Arch | Repository --+--------------------+---------+-------------+--------+----------------------------- | perl-Regexp-Common | package | 2.120-110.1 | x86_64 | suse11.0-oss | perl-Regexp-Common | package | 2.120-110.1 | i586 | suse11.0-oss We'd be happy to provide any additional details that would help, thanks! -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=433679
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=433679
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=433679#c1
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=433679
User mls@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=433679#c2
--- Comment #2 from Michael Schröder
https://bugzilla.novell.com/show_bug.cgi?id=433679
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=433679#c3
--- Comment #3 from Ján Kupec
I'd prefer 1), i.e. get rid of that repository:capability hack. That's what the '-r' option is for.
There are two differences: first, -r puts the rest of your repos (the ones you don't specify) out of play (they can't be used e.g. to satisfy deps), second, you can't specify repo per package with -r. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=433679
User mls@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=433679#c4
--- Comment #4 from Michael Schröder
https://bugzilla.novell.com/show_bug.cgi?id=433679
User bitdealer@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=433679#c5
Stephan Kleine
https://bugzilla.novell.com/show_bug.cgi?id=433679
User mls@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=433679#c6
--- Comment #6 from Michael Schröder
https://bugzilla.novell.com/show_bug.cgi?id=433679
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=433679#c7
Ján Kupec
As we now have '--from' in zypper, I don't see why we can't get rid of that repository-by-capability hack. Who needs repo per package?
It was requested in FATE #302919. I agree it's a corner case, maybe nobody used it so far :O)
(Uh, the man page says that --from implies --name, why is that the case?)
Because of insufficient solver API in libzypp. We'd need and API to install by name/capability while enforcing specific repository. Schubi, could this be provided? This is one of examples of what's needed that i mentioned in http://lists.opensuse.org/zypp-devel/2009-03/msg00012.html - yes, i'll send detailed list later. -- 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.
participants (1)
-
bugzilla_noreply@novell.com