|
Bugzilla – Full Text Bug Listing |
| Summary: | zypper lu -t package -r "RepoName" not working as expected | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Forgotten User zhFaldehF_ <forgotten_zhFaldehF_> |
| Component: | libzypp | Assignee: | Jan Kupec <jkupec> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Duncan Mac-Vicar <dmacvicar> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | dimstar |
| Version: | RC 1 | Flags: | coolo:
SHIP_STOPPER-
|
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Zypper Log
Zypper Log from 11.0 |
||
|
Description
Forgotten User zhFaldehF_
2008-05-29 15:57:52 UTC
Works for me. Is the "KDE 4 Desktop" an alias? The -r option takes alias, repo # from 'zypper lr' or repo URI. What's your 'zypper lr -d'? Also please attach zypper.log, since you should get something like this even if you supplied an invalid argument to the -r option: $ zypper lu -t package -r "Packman 11.0" Repository 'Packman 11.0' not found by its alias, number, or URI. Use 'zypper repos' to get the list of defined repositories. (and please shorten the output listing in the future, there's no need for the whole 'lu' list here) :O) Here is the output pertaining to KDE 4 Desktop for zypper lr -d 7 | KDE 4 Desktop | KDE 4 Desktop | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/KDE%3a/KDE4%3a/STABLE%3a/Desktop/openSUSE_10.3/ Here is the output of the repo file: bkevan@LSSUSE01007250:~> cat /etc/zypp/repos.d/KDE\ 4\ Desktop\ Repository.repo [KDE 4 Desktop] name=KDE 4 Desktop baseurl=http://download.opensuse.org/repositories/KDE%3a/KDE4%3a/STABLE%3a/Desktop/openSUSE_10.3/ path=/ type=rpm-md enabled=1 autorefresh=1 gpgcheck=1 keeppackages=1 Created attachment 218950 [details]
Zypper Log
Zypper Log that you requested
I tailed the last 50000 lines since the original log was 13MB.. should be plenty for ya
Also note.. this worked fine before upgrading to the backport repository and I did a zypper ref --force and also deleted /var/cache/zypp to see if that caused the issues. I am upgrading the urgency of this. Why? Because I just installed RC1 and have the same behavior with: bkevan@bksuse11test:/etc/zypp/repos.d> rpm -qa | grep zypp libzypp-4.25.0-5 zypper-0.11.5-2 bkevan@bksuse11test:/etc/zypp/repos.d> zypper lu -t package Reading installed packages... S | Repository | Name | Version | Arch --+--------------------+-----------------------------+------------------+----- v | Packman Repository | amarok | 1.4.9.1-101.pm.1 | i586 v | Packman Repository | amarok-libvisual | 1.4.9.1-101.pm.1 | i586 v | Packman Repository | amarok-yauap | 1.4.9.1-101.pm.1 | i586 v | Packman Repository | fftw3 | 3.1.2-142.pm.3 | i586 v | Packman Repository | gstreamer-0_10 | 0.10.19-42.pm.1 | i586 v | Packman Repository | gstreamer-0_10-plugins-base | 0.10.19-42.pm.1 | i586 v | Packman Repository | gstreamer-0_10-plugins-good | 0.10.8-42.pm.1 | i586 v | Packman Repository | k3b | 1.0.5-0.pm.2 | i586 v | Packman Repository | libgstinterfaces-0_10-0 | 0.10.19-42.pm.1 | i586 v | Packman Repository | libtunepimp | 0.5.3-100.pm.9 | i586 v | Packman Repository | libtunepimp5 | 0.5.3-100.pm.9 | i586 v | Packman Repository | mjpegtools | 1.9.0rc3-0.pm.1 | i586 bkevan@bksuse11test:/etc/zypp/repos.d> sudo zypper up -t package -r "http://ftp.skynet.be/pub/packman/suse/11.0/" Reading installed packages... Nothing to do. I am considering blocker as zypper (a main part) is not functioning as suspected. I will update the logs for my new 11.0 RC1 install since it's pretty clean. I am upgrading the urgency of this. Why? Because I just installed RC1 and have the same behavior with: bkevan@bksuse11test:/etc/zypp/repos.d> rpm -qa | grep zypp libzypp-4.25.0-5 zypper-0.11.5-2 bkevan@bksuse11test:/etc/zypp/repos.d> zypper lu -t package Reading installed packages... S | Repository | Name | Version | Arch --+--------------------+-----------------------------+------------------+----- v | Packman Repository | amarok | 1.4.9.1-101.pm.1 | i586 v | Packman Repository | amarok-libvisual | 1.4.9.1-101.pm.1 | i586 v | Packman Repository | amarok-yauap | 1.4.9.1-101.pm.1 | i586 v | Packman Repository | fftw3 | 3.1.2-142.pm.3 | i586 v | Packman Repository | gstreamer-0_10 | 0.10.19-42.pm.1 | i586 v | Packman Repository | gstreamer-0_10-plugins-base | 0.10.19-42.pm.1 | i586 v | Packman Repository | gstreamer-0_10-plugins-good | 0.10.8-42.pm.1 | i586 v | Packman Repository | k3b | 1.0.5-0.pm.2 | i586 v | Packman Repository | libgstinterfaces-0_10-0 | 0.10.19-42.pm.1 | i586 v | Packman Repository | libtunepimp | 0.5.3-100.pm.9 | i586 v | Packman Repository | libtunepimp5 | 0.5.3-100.pm.9 | i586 v | Packman Repository | mjpegtools | 1.9.0rc3-0.pm.1 | i586 bkevan@bksuse11test:/etc/zypp/repos.d> sudo zypper up -t package -r "http://ftp.skynet.be/pub/packman/suse/11.0/" Reading installed packages... Nothing to do. I am considering blocker as zypper (a main part) is not functioning as suspected. I will update the logs for my new 11.0 RC1 install since it's pretty clean. Created attachment 219010 [details]
Zypper Log from 11.0
ZYpper logs from 11.0 RC1 installation with
bkevan@bksuse11test:/etc/zypp/repos.d> rpm -qa | grep zypp
libzypp-4.25.0-5
zypper-0.11.5-2
this is still not a blocker I consider it to be higher then normal. Why? Because I cannot update easily or use zypper functions how they were intended to be used. Zypper is the only tool I use for updating, and would hate to have to replace it with yum since yum would work. On the mailing list at least one other has reported the same issue and I also see this in 11.0 RC1 Ben, I think your "updates" are not performed due to a provider change of the packages. All the packages have now Provider SUSE Linux, but you try to 'update' them to the PackMan or OBS versions. Zypper does not treat this as a 'safe update' as far as I understood. But I agree that zypper lu -t package should be consistent with what zypper up -t package is going to do (or mark the packages as 'provider different', but for this we're to late in 11.0) (In reply to comment #12 from Dominique Leuenberger) > Ben, I think your "updates" are not performed due to a provider change of the > packages. > > All the packages have now Provider SUSE Linux, but you try to 'update' them to > the PackMan or OBS versions. Zypper does not treat this as a 'safe update' as > far as I understood. > > But I agree that > zypper lu -t package > > should be consistent with what zypper up -t package is going to do (or mark the > packages as 'provider different', but for this we're to late in 11.0) > Yes, however even the ones that are detected (at times a few are detected) and are installed change providers. Why can't the others be detected, installed then providers changed? Yum handles this just fine. *** This bug has been marked as a duplicate of bug 392591 *** |