[Bug 711125] New: zypper in chrooted environment: "Cannot read input: bad stream or EOF."
https://bugzilla.novell.com/show_bug.cgi?id=711125 https://bugzilla.novell.com/show_bug.cgi?id=711125#c0 Summary: zypper in chrooted environment: "Cannot read input: bad stream or EOF." Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: andreas_nordal_4@hotmail.com QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.6; Linux) KHTML/4.6.5 (like Gecko) SUSE When installing programs (e.g. zypper install nano), zypper normally asks the user to confirm the changes, and waits for the answer. When in a chrooted environment, zypper fails to wait and complains (see Actual Results). As zypper suggests, «--non-interactive» will omit the question. With this workaround, zypper works flawlessly, at the loss of interactivity. Reproducible: Always Steps to Reproduce: 1. zypper --root=/suse install zypper 2. chroot /suse 3. zypper install nano Actual Results: Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: nano 1 new package to install. Overall download size: 193.0 KiB. After the operation, additional 550.0 KiB will be used. Continue? [y/n/?] (y): Cannot read input: bad stream or EOF. If you run zypper without a terminal, use '--non-interactive' global option to make zypper use default answers to prompts. Expected Results: Zypper should read standard in. I was using bash as shell. There seemed to be nothing wrong with standard in, as I was able to use vim and a proof-of-concept shellscript that successfully read from standard in. -- 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=711125 https://bugzilla.novell.com/show_bug.cgi?id=711125#c zj jia <zjjia@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@novell.com AssignedTo|bnc-team-screening@forge.pr |zypp-maintainers@forge.prov |ovo.novell.com |o.novell.com -- 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=711125 https://bugzilla.novell.com/show_bug.cgi?id=711125#c1 --- Comment #1 from Andreas Nordal <andreas_nordal_4@hotmail.com> 2011-08-14 13:55:41 UTC --- The problem disappears if "mount --bind /dev /suse/dev" is executed before "chroot /suse". IMHO, since mount-binding /dev is a good idea anyway, an acceptible fix would be to just inform about this (unintuitive) dependency of the /dev pseudo filesystem in the error message. Example: "Did you remember to mount the /dev filesystem?" -- 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=711125 https://bugzilla.novell.com/show_bug.cgi?id=711125#c2 Alexander Bergmann <abergmann@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abergmann@novell.com --- Comment #2 from Alexander Bergmann <abergmann@novell.com> 2012-01-26 09:27:19 UTC --- I've ran into this problem with an OpenVZ virtualized guest system. After upgrading from openSUSE 11.4 to 12.1 I've got the same error message. "Cannot read input: bad stream or EOF." The problem was a the missing "/dev/tty" device. Instead of an character device I found an empty regular file. # ls -l /dev/tty -rw-r--r-- 1 root root 0 Jan 26 11:03 /dev/tty So I removed that file and created the right character device again. # rm /dev/tty # mknod /dev/tty c 5 0 # ls -l /dev/tty crw-r--r-- 1 root root 5, 0 Jan 26 12:16 /dev/tty Happy days! Everything is back to normal. PS: I'm not hundred percent convinced that this is reproducible. -- 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=711125 https://bugzilla.novell.com/show_bug.cgi?id=711125#c3 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #3 from Michael Andres <ma@suse.com> 2013-09-30 17:34:08 CEST --- no zypp issue -- 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