Custom Query (1145 matches)

Reported by jdreed, 14 years ago.

Right now, if a new kernel update comes out before openafs is built, and the auto-updater happens to run, every machine on campus will whine loudly to ops about the fact that the update would remove openafs-modules-generic. This is potentially annoying.

#243 will fix this, but if we're not going to fix #243 anytime soon, we should make auto-update less loud, in some sort of clever fashion.

Reported by geofft, 15 years ago.

On a couple of Debathena machines I use:

sipbadmin@tyger:~$ find /etc -name "*.dpkg-new" 2>/dev/null
/etc/bind/named.conf.options.debathena-orig.dpkg-new
/etc/openafs/afs.conf.debathena-orig.dpkg-new

dr-wily:~ geofft$ find /etc -name "*.dpkg-new" 2>/dev/null
/etc/bash.bashrc.debathena-orig.dpkg-new
/etc/bind/named.conf.options.debathena-orig.dpkg-new
/etc/openafs/cacheinfo.debathena.dpkg-new
/etc/openafs/afs.conf.debathena-orig.dpkg-new
/etc/openafs/cacheinfo.debathena.debathena-orig.dpkg-new
/etc/ssh/sshd_config.debathena.debathena-orig.dpkg-new
/etc/security/access.conf.debathena.dpkg-new

ozok-the-destroyer:~ geofft$ find /etc -name "*.dpkg-new" 2>/dev/null
/etc/bash.bashrc.debathena-orig.dpkg-new
/etc/ldap/ldap.conf.debathena-orig.dpkg-new
/etc/firefox-3.0/pref/ubufox.js.debathena-orig.dpkg-new
/etc/texmf/xdvi/XDvi.debathena-orig.dpkg-new
/etc/texmf/dvips/config/config.ps.debathena-orig.dpkg-new
/etc/texmf/dvipdfm/config/config.debathena-orig.dpkg-new
/etc/texmf/tex/generic/config/pdftexconfig.tex.debathena-orig.dpkg-new
/etc/lprng/lpd.conf.debathena-orig.dpkg-new
/etc/cups/cupsd.conf.debathena-orig.dpkg-new
/etc/fuse.conf.debathena-orig.dpkg-new
/etc/security/access.conf.debathena-orig.dpkg-new
/etc/pam.d/login.debathena-orig.dpkg-new
/etc/pam.d/gdm.debathena-orig.dpkg-new
/etc/pam.d/sshd.debathena-orig.dpkg-new
/etc/openafs/afs.conf.debathena-orig.dpkg-new
/etc/ssh/ssh_config.debathena-orig.dpkg-new
/etc/gdm/gdm.conf-custom.debathena-orig.dpkg-new
/etc/ntp.conf.debathena-orig.dpkg-new
/etc/bind/named.conf.options.debathena-orig.dpkg-new
/etc/krb.realms.debathena-orig.dpkg-new
/etc/csh.cshrc.debathena-orig.dpkg-new

kid-icarus:~ geofft$ find /etc -name "*.dpkg-new" 2>/dev/null
/etc/csh.cshrc.debathena-orig.dpkg-new
/etc/bash.bashrc.debathena-orig.dpkg-new
/etc/cups/cupsd.conf.debathena-orig.dpkg-new
/etc/openafs/afs.conf.debathena-orig.dpkg-new
/etc/ntp.conf.debathena-orig.dpkg-new
/etc/lprng/lpd.conf.debathena-orig.dpkg-new
/etc/bind/named.conf.options.debathena-orig.dpkg-new
/etc/apparmor.d/usr.sbin.cupsd.debathena-orig.dpkg-new

Zephyr discussion reminded me that this is due to  a bug in dpkg regarding diverted conffiles that's been fixed in dpkg 1.15. Jaunty and Lenny both still have 1.14, and we more or less still care about them, so we should consider adding code in auto-update to clean these up appropriately.

Reported by broder, 15 years ago.

Right now, if anything triggers a dpkg conffile conflict, auto-update will hang indefinitely. Not the best failure mode.

On cluster machines, since we are the sysadmin, we should be passing -o Dpkg::Options::=--force-confnew to aptitude.