General information
About
News
FAQ
Contact us
Documentation
How to file bugs
using templates
Debian policy
piuparts.d.o configuration:
piuparts.conf,
distros.conf,
scripts and logs
README
README_server
piuparts manpage
Summaries
Bugs filed
Suites overview
Suite: oldstable222sid
by maintainer / uploader
by source package
states graph
all tested suites
experimental
sid2experimental
sid
sid-strict
sid-nodoc
sid-merged-usr
sid-broken-symlinks
testing2sid
forky
forky-rcmd
trixie
trixie-rcmd
trixie-security
trixie-pu
trixie2next
bookworm
bookworm-rcmd
bookworm-security
bookworm-pu
bookworm2next
bullseye
bullseye-rcmd
bullseye-security
bullseye-pu
bullseye2next
stable2sid
stable22sid
oldstable222sid
oldstable22testing
src: piuparts
Source
piuparts.d.o bugs
piuparts bugs / ToDo
Other Debian QA efforts
Debian QA Group
Dose tools (former: EDOS)
Lintian
Debian Package Tracker
Ultimate Debian Database
jenkins.debian.net
ci.debian.net
Last update
2025-09-15 21:12 UTC
Packages with failed logs with the string "EOF on stdin at conffile prompt" in oldstable222sid, sorted by reverse dependency count.

The piuparts upgrade test failed because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded...

This is explained in detail in policy 10.7.3 at https://www.debian.org/doc/debian-policy/ch-files.html#behavior which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens."

According to the thread started at 200908191215.05079.holger@layer-acht.org these bugs are to be filed with severity serious.

The commandline to find these logs is:

COMMAND='grep -E "(EOF|end of file) on stdin at conffile prompt"'

Please file bugs!

Affected packages in oldstable222sid: 1