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.