[Bug 465217] New: annoying zypper cdrom handling
https://bugzilla.novell.com/show_bug.cgi?id=465217 Summary: annoying zypper cdrom handling Classification: openSUSE Product: openSUSE 11.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers@forge.provo.novell.com ReportedBy: andi-nbz@firstfloor.org QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10 (like Gecko) SUSE Build Identifier: Following scenario: - I updated a system which only used network repositories from 11.0 to 11.1 - I did that by booting from the DVD Then after the update I wanted to run zypper to install something, but it hung for ~3 minutes until it told me that it couldn't find the DVD in the CDROM and offered to abort. I tried to get rid of the cd rom source, but even after reading the manpage closely I was unable to do that based on the zypper command line interface. Finally I had to do it with yast which listed all sources. There was a network repository configured, but with a lower priority than the DVD. So. - If there's a network repository configured with the same data as a missing DVD then zypper should not abort but use that. - it would be a good idea to make the cdrom check faster, e.g. by just checking if something is already mounted (hal auto mounts after all), especially when the same files are available in other repositories. - When I do an update it shouldn't add the CDROM source afterwards in the running system. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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=465217
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=465217#c1
Ján Kupec
I tried to get rid of the cd rom source, but even after reading the manpage closely I was unable to do that based on the zypper command line interface.
$ zypper repos
$ zypper removerepo
- If there's a network repository configured with the same data as a missing DVD then zypper should not abort but use that.
Yes, this would be nice. Please create a separate bug report for this.
- it would be a good idea to make the cdrom check faster, e.g.
The three minutes you are experiencing are unusual - the check is as fast as as mounting a CD (via 'mount' on the command line). The delay must have been caused by something else. Your zypper log would tell more (see http://en.opensuse.org/Zypper/Troubleshooting#Log). Please try to reproduce the bug and attach the log. We'll keep this report to check this problem.
- When I do an update it shouldn't add the CDROM source afterwards in the running system.
Why not? It's pretty standard and another user could prefer the exact opposite. One way or the other, you are free to remove the repository after the update yourself. WONTFIX -- 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=465217
User andi-nbz@firstfloor.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=465217#c2
--- Comment #2 from Andi N Kleen
zypper repos
Try it. It gives you no indication at all where the CDROM source is (it doesn't print the pseudo URL) Even using -vvv didn't give that information. Only yast prints it. I even went to grepping /var/* for it (that used to work on older zypper versions), but you seem to hide it much better now.
The three minutes you are experiencing are unusual - the check is as fast as as mounting a CD (via 'mount' on the command line).
The CDROM (it's a slimline one in a server) is just slow to find out that there is no disk in the drive. There's a lot of broken hardware like this around so zypper just has to deal with it.
Why not? It's pretty standard and another user could prefer the exact opposite.
Because it wasn't like this before the update. Updates are not supposed to silently change the configuration like this. I understand you need to change it temporarily during the update to access it, but that should be undone afterwards. Not doing that is a bug. Your argument would make sense for a new installation, but not for an update. And your new bugzilla is still broken, doesn't allow me to remove NEEDINFO. -- 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=465217
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=465217#c3
--- Comment #3 from Ján Kupec
The CDROM (it's a slimline one in a server) is just slow to find out that there is no disk in the drive. There's a lot of broken hardware like this around so zypper just has to deal with it.
If the 'mount' command takes too long, how should zypper deal with it? Should it ask user whether to wait longer or to cancel the mount?
Because it wasn't like this before the update. Updates are not supposed to silently change the configuration like this. I understand you need to change it temporarily during the update to access it, but that should be undone afterwards. Not doing that is a bug.
Nope. You could just as well want to keep the DVD you used for the update as an installation repo for further installations after the update. Or you could do an update without access to network, in which case you surely want use the DVD after the update as well. This is just your use case, not a bug. Nevertheless, if there will be more people complaining about this, we will try to do something about it. -- 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=465217
User andi-nbz@firstfloor.org added comment
https://bugzilla.novell.com/show_bug.cgi?id=465217#c4
--- Comment #4 from Andi N Kleen
Ad 'zypper repos' - there's also 'zypper help repos' which would point you to -d or -u options.
First that's totally unclear from the manpage (which generally seems get worse each release, with more strange concepts getting added like "services" where it is unclear what the difference is to a repository) What would have been useful if the updater had named the cd source it added behind my back "opensuse 11.1 DVD" or something like that. And also if there are multiple sources which are the same list the urls by default to distingush them?
If the 'mount' command takes too long, how should zypper deal with it? Should it ask user whether to wait longer or to cancel the mount?
You could start a background process, if it takes longer than a few seconds start querying the backup network sources too if they got the same package. And yes if it takes longer than some hard timeout it should offer to cancel (although that's often difficult because mount might be blocked somewhere in the kernel)
Nope. You could just as well want to keep the DVD you used for the update as an installation repo for further installations after the update.
Again when I didn't have any DVD sources before the update I don't want the update to second guess my existing configuration and change it behind my back. If I want a new configuration I would have used a new install, not an update. -- 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=465217
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=465217#c5
--- Comment #5 from Ján Kupec
Ad 'zypper repos' - there's also 'zypper help repos' which would point you to -d or -u options.
First that's totally unclear from the manpage
What is unclear about this: there's a 'Repository Management' section and there's repos command: repos (lr) [options] List all defined repositories. The following data are printed for each repository found: # (repository number), Enabled (whether the repository is enabled), Refresh (whether auto-refresh is enabled for the repository), Type (rpm-md, yast2, plaindir), Alias (shorthand for Name), and Name. Other columns can be added using the options listed below. <cut/> -u, --uri Add base URI column to the output. -p, --priority Add repository priority column to the output. There are even examples below: Examples: Backup your repository setup: $ zypper repos -e myreposbackup.repo List repositories with their URIs and priorities: $ zypper lr -pu I really don't know how to make it clearer. Suggest something. Statements like "that's totally unclear from the manpage" won't help us to make it better for you.
(which generally seems get worse each release, with more strange concepts getting added like "services" where it is unclear what the difference is to a repository)
Services Services are one level above repositories and serve to manage repositories or to do some special tasks. Libzypp currently supports only one type of services, the Repository Index Ser- vice (RIS). Repository Index Service (RIS) is a special type of repository which contains a list of other repositories. What is unclear about this? And what exactly is it that makes the man page worse each release? Need to know, otherwise the trend will continue, since i think it's getting better :O)))
What would have been useful if the updater had named the cd source it added behind my back "opensuse 11.1 DVD" or something like that.
Agreed. And how was it actually named?
And also if there are multiple sources which are the same list the urls by default to distingush them?
I'd say no. At least the 'alias' is always unique, but apart from that, adding the URL column based on the data (not user's request) might be confusing. -- 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=465217
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=465217#c6
Ján Kupec
You could start a background process, if it takes longer than a few seconds start querying the backup network sources too if they got the same package.
Yes, that would be nice, but too difficult and not worth doing for such corner case IMO.
And yes if it takes longer than some hard timeout it should offer to cancel (although that's often difficult because mount might be blocked somewhere in the kernel)
Yes, this might be worth trying, but somewhere in the future, since there are more important things. I'll close as WONTFIX for now. -- 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=465217
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=465217#c7
--- Comment #7 from Ján Kupec
Again when I didn't have any DVD sources before the update I don't want the update to second guess my existing configuration and change it behind my back. If I want a new configuration I would have used a new install, not an update.
This is simply not how our distro upgrade is intened to work. It disables all your previously existing repos anyway by default during the update (since they are probably not relevant for the new release anyway) - you have to reenable them yourself. And there's a good chance that the DVD is then your only relevant repository. If you wish to discuss this further, please open a separate bug report for it, or discuss it off bugzilla (e.g. on opensuse-softwaremgmt@opensuse.org ML). -- 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