When I'm installing wine (not wine1.2) I still see complaints while it ostensibly installs (why?).
While it's bad practice to have sysctl keys set in /etc/sysctl.d/*.conf and /etc/sysctl.conf, this should not be a deal-breaker nor should it be a noise-maker for wine's installation. Here's what I get when I install - . . . Setting up wine (1.0.1-0ubuntu8) ... kernel.printk = 4 4 1 7 net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 net.ipv4.tcp_syncookies = 1 vm.mmap_min_addr = 0 error: "sysctl vm.dirty_writeback_centisecs" is an unknown key dpkg: error processing wine (--configure): subprocess installed post-installation script returned error exit status 255 . . . Please pardon me if the included patch introduces a BASH-ism, which I tend to add. :) This one-line change should suppress printing unnecessary sysctl output during installation, while still potentially warning the person doing the installing. In my case - . . . Setting up wine (1.0.1-0ubuntu9jrb) ... error: "sysctl vm.dirty_writeback_centisecs" is an unknown key . . . ** Patch added: "patched postinst script" http://launchpadlibrarian.net/40919283/wine-postinst.diff -- Packages with custom /etc/sysctl.d/30-foo.conf files can fail to install: start procps returns exit status 1 https://bugs.launchpad.net/bugs/447197 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
