Bug#360690: [FTBFS] install scripts do not run; package seems mangled

2006-04-20 Thread Joe Mason
Stephen Gran wrote: > The main problem was lost +x perms, most likely due to patch, and me > not noticing that the x bit was lost before upload. I don't know that > wholesale reversion of packaging decisions is a good thing to do in > an NMU. > No, adding the +x perms and running the script man

Bug#360690: install scripts do not run; package seems mangled

2006-04-03 Thread Joe Mason
Package: webcalendar Version: 1.0.2-2 Severity: grave When I installed webcalendar, I got the option "Let debconf manage settings.php?" - Choosing "yes" led to a permissions error trying to execute /usr/share/webcalendar/tools/dbconfig_oldconf.sh (which had permissions 644) - Choosing "no" le

Bug#329422: No warnings when uninstalling kernel package

2005-09-21 Thread Joe Mason
Package: kernel-image-2.6.8-2-686 Version: 2.6.8-16 Severity: critical Most of the time when I try to uninstall a package that's critical to system functionality, it tells me I'm about to uninstall a core component and asks me to type, "Yes I know what I'm doing" or similar to continue. $ sudo ap

Bug#321724: cannot enable executable stack as shared object requires: Error 14

2005-08-07 Thread Joe Mason
Package: libelfg0 Version: 0.8.5-1 Severity: critical I just did a dist-upgrade, and every time I try to run a program linked with libelf I get the following error: error while loading shared libraries: libelf.so.0: cannot enable executable stack as shared object requires: Error 14 Many other li

Bug#321721: cannot enable executable stack as shared object requires: Error 14

2005-08-07 Thread Joe Mason
Package: libssl0.9.7 Version: 0.9.7g-1 Severity: critical I just did a dist-upgrade, and every time I try to run a program linked with libcrypto I get the following error: error while loading shared libraries: libcrypto.so.0.9.7: cannot enable executable stack as shared object requires: Error 14

Bug#321723: cannot enable executable stack as shared object requires: Error 14

2005-08-07 Thread Joe Mason
Package: libgdbm3 Version: 1.8.3-2 Severity: critical I just did a dist-upgrade, and every time I try to run a program linked with libgdbm I get the following error: error while loading shared libraries: libgdbm.so.3: cannot enable executable stack as shared object requires: Error 14 Many import

Bug#321720: cannot enable executable stack as shared object requires: Error 14

2005-08-07 Thread Joe Mason
Package: libgcrypt11 Version: 1.2.1-4 Severity: critical I just did a dist-upgrade, and every time I try to run a program linked with libgcrypt11 I get the following error: error while loading shared libraries: libacl.so.1: cannot enable executable stack as shared object requires: Error 14 Notab

Bug#321718: Upgrade caused many libs to complain about "executable stack"

2005-08-07 Thread Joe Mason
Package: upgrade-reports Severity: critical I just did a dist-upgrade, and every time I try to run a program linked with libacl (which includes mv, cp, and ls) I get the following error: error while loading shared libraries: libacl.so.1: cannot enable executable stack as shared object requires: E

Bug#321717: cannot enable executable stack as shared object requires: Error 14

2005-08-07 Thread Joe Mason
Package: libacl1 Version: 2.2.29-1.0.1 Severity: critical I just did a dist-upgrade, and every time I try to run a program linked with libacl (which includes mv, cp, and ls) I get the following error: error while loading shared libraries: libacl.so.1: cannot enable executable stack as shared obje

Bug#290999: depends on wvstreams3, not wvstreams4

2005-01-17 Thread Joe Mason
Package: retchmail Severity: grave libwvstreams3 seems to have disappeared from Debian unstable, but retchmail still depends on it instead of libwvstreams4: [EMAIL PROTECTED]:~$ sudo apt-get install retchmail Reading Package Lists... Done Building Dependency Tree... Done Some packages could not b