Bug#1033073: libnginx-mod-rtmp: clients hang trying to play published streams due to Debian default nginx configuration

2023-03-16 Thread Mark Nipper
no packages. -- no debconf information -- Mark Nipper

Bug#1025795: live-build: --memtest option broken with current version of memtest86+

2022-12-09 Thread Mark Nipper
The attached patch, aside from the missing associated documentation changes, seems to do the trick. Please include or modify as you see fit. Thanks! -- Mark Nipper --- /usr/share/live/build/functions/configuration.sh.bk 2022-12-09 18:15:15.623888651 -0800 +++ /usr/share/live

Bug#1025795: live-build: --memtest option broken with current version of memtest86+

2022-12-09 Thread Mark Nipper
-container 252.2-1 ii wget1.21.3-1+b2 ii xz-utils5.2.9-0.0 Versions of packages live-build suggests: ii e2fsprogs 1.46.6~rc1-1+b1 pn mtd-utils ii parted 3.5-3 -- no debconf information -- Mark Nipper

Bug#925591: grub-install fails on raid1+efi setup

2022-11-18 Thread Mark Nipper
of this same problem: --- https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1868553 I assume it would be possible to incorporate the same fix easily enough into the Debian version of this package to properly support this scenario. -- Mark Nipper

Bug#993811: midish: please package newest version

2021-09-06 Thread Mark Nipper
linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages midish depends on: ii libasound21.2.5.1-1 ii libc6 2.31-17 ii libreadline8 8.1-2 midish recommends no packages. midish suggests no packages. -- no debconf information -- Mark

Bug#990048: dhelp cron.monthly job using invalid syntax for xargs

2021-06-18 Thread Mark Nipper
Package: dhelp Version: 0.6.26 Severity: normal Just got this today from one of my systems: --- /etc/cron.monthly/dhelp: xargs: warning: options --max-args and --max-lines/-l are mutually exclusive, ignoring previous --max-args value -- System Information: Debian Release: 11.0 APT

Bug#880145: nftables: When more than 2-3 elements are in an anonymous set the rule does not match to any of them

2017-10-30 Thread Mark Nipper
Package: nftables Version: 0.8-1 Followup-For: Bug #880145 I experienced a variation of the reported issue. Previously, this rule was working as intended: --- tcp dport { http, https } accept After the upgrade to the newer kernel and nftables versions, I was able to connect over 443

Bug#838372: stterm: New upstream version

2016-10-02 Thread Mark Nipper
Package: stterm Version: 0.6-1 Followup-For: Bug #838372 I'd like to second the request to package 0.7. However, as the latest tmux (currently in unstable, 2.3) supports true color with stterm, I'd like to vote against including the scrollback patch in the base stterm, since it's antithetical to

Bug#827670: libpam-google-authenticator: recent update completely broke ability to log into system

2016-06-19 Thread Mark Nipper
Package: libpam-google-authenticator Version: 20160607-1 Severity: important I just updated yesterday which brought down the new libpam-google-authenticator package uploaded recently. This completely rendered my system unusable which required booting into single user mode and reverting

Bug#823147: libinput10: AlpsPS/2 ALPS DualPoint TouchPad middle mouse button emulation stopped working

2016-05-01 Thread Mark Nipper
Package: libinput10 Version: 1.2.4-1 Severity: normal This looks like an upstream bug. I have the following devices on my Dell Latitude E6540: --- $ xinput list | grep Alps ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=13 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick

Bug#794509: grepcidr: new upstream version

2015-08-03 Thread Mark Nipper
Package: grepcidr Version: 1.3-6 Severity: normal Looks like upstream at http://www.pc-tools.net/unix/grepcidr/ has a newer 2.0 version released 2014-05-26. It might be nice to get this package updated. Thanks! -- System Information: Debian Release: stretch/sid APT prefers testing

Bug#776728: newsbeuter: nasty memory leak in 2.8

2015-01-31 Thread Mark Nipper
Package: newsbeuter Version: 2.8-2 Severity: important It seems there is a rather nasty memory leak in 2.8 of newsbeuter. The bug for it is mentioned here (with a pretty graph!): --- https://github.com/akrennmair/newsbeuter/issues/119 This has caused a smaller virtual host I have

Bug#701641: Segfault when saving messages: ../sysdeps/x86_64/multiarch/strcmp.S: No such file or directory.

2013-03-19 Thread Mark Nipper
a problem with mutt at all but a problem with Dovecot and Cyrus, both of which depended on a broken libssl! -- Mark Nipper ni...@bitgnome.net (XMPP) +1 979 575 3193 - Long live the fighters! -- Paul Muad'Dib, Dune, 1984 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

Bug#701641: Segfault when saving messages: ../sysdeps/x86_64/multiarch/strcmp.S: No such file or directory.

2013-03-16 Thread Mark Nipper
: --- ii cyrus-imapd-2.4 2.4.16-3 amd64 Cyrus mail system - IMAP support So, kind of similar, but not really (I'm not sure how much the two have diverged at this point). -- Mark Nipper ni...@bitgnome.net (XMPP) +1 979 575 3193 - Whenever you find you are on the side of the majority, it is time

Bug#701641: mutt: tls_socket_read (A TLS fatal alert has been received.)

2013-02-27 Thread Mark Nipper
Package: mutt Version: 1.5.21-6.2 Followup-For: Bug #701641 This is simply a me too. I receive the TLS error upon starting mutt for the first time while trying to open my default INBOX via IMAPS. Looking at the debug output from mutt, it happens while mutt is listing the STATUS for all of my

Bug#694930: nsd3 fails to start during boot every time

2012-12-02 Thread Mark Nipper
Package: nsd3 Version: 3.2.12-1 Severity: important I ran across the same problem seemingly that this person mentions here: --- http://serverfault.com/questions/444354/nginx-and-nsd3-dont-start-on-boot-because-they-cannot-use-the-assigned-ip The error I see in my nsd.log is: ---

Bug#651155: nvidia-glx: happens regardless of display manager I think

2012-04-18 Thread Mark Nipper
On 04 Apr 2012, Mark Nipper wrote: I just installed 295.33-1, and the screen corruption still occurs. And still happening with 295.40-1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas

Bug#651155: nvidia-glx: happens regardless of display manager I think

2012-04-04 Thread Mark Nipper
On 18 Feb 2012, Andreas Beckmann wrote: Please test the new 295.20 driver. Does this change the behaviour? I just installed 295.33-1, and the screen corruption still occurs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Bug#664880: php-apc: APC not working very well under 5.4 (at least using mpm-itk)

2012-03-21 Thread Mark Nipper
Package: php-apc Version: 3.1.9-0.1+b1 Severity: grave Justification: renders package unusable My system just got the PHP 5.4.0 upgraded packages. After which, a lot of unhappiness ensued with APC. Disabling APC entirely clears up my problems. I'm getting a lot of these: --- *** glibc

Bug#664895: squirrelmail: completely broken with PHP 5.4

2012-03-21 Thread Mark Nipper
Package: squirrelmail Version: 2:1.5.1-5 Severity: grave Justification: renders package unusable With the upgrade to PHP 5.4.0 coming down the pipeline, SquirrelMail has been rendered unusable. Commenting out the session_(un)register functions get things working somewhat again, but SM is

Bug#664895: Info received (squirrelmail: completely broken with PHP 5.4)

2012-03-21 Thread Mark Nipper
I should say that the version of SM in testing/unstable (2:1.4.22-1) actually works much better even than the experimental version and only requires hex2bin to be fixed. A patch for that looks like it's already been submitted upstream: ---

Bug#651155: nvidia-glx: happens regardless of display manager I think

2012-02-20 Thread Mark Nipper
On 18 Feb 2012, Andreas Beckmann wrote: Please test the new 295.20 driver. Does this change the behaviour? No. It's still corrupting the display with 295.20. -- Mark Nipper ni...@bitgnome.net (XMPP) +1 979 575 3193 - Computers are like Old Testament gods: lots of rules and no mercy

Bug#627145: Unable to load dynamic library

2012-01-23 Thread Mark Nipper
Package: php5-common Version: 5.3.9-1 Followup-For: Bug #627145 This should be merged with bug 656495 as it's caused by the same problem and is going to be fixed shortly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Bug#656500: xkb-data: XF86_Ungrab and XF86_ClearGrab security hole upstream

2012-01-19 Thread Mark Nipper
Package: xkb-data Version: 2.3-2 Severity: grave Tags: security upstream Justification: user security hole As originally reported at: --- http://gu1.aeroxteam.fr/2012/01/19/bypass-screensaver-locker-program-xorg-111-and-up/ and further syndicated by: ---

Bug#656500: xkb-data: XF86_Ungrab and XF86_ClearGrab security hole upstream

2012-01-19 Thread Mark Nipper
On 19 Jan 2012, Cyril Brulebois wrote: Downgrading severity per: http://packages.qa.debian.org/x/xorg-server/news/20120119T101901Z.html Excellent. I had looked around for a previously reported bug, but missed this one. Sorry for the noise! -- Mark Nipper ni...@bitgnome.net (XMPP

Bug#651155: nvidia-glx: happens regardless of display manager I think

2012-01-04 Thread Mark Nipper
Package: nvidia-glx Version: 295.09-1 Followup-For: Bug #651155 I'm having the exact same problem, but I'm using xdm as my display manager (and awesome as my window manager), so no GNOME/KDE interaction at all here. Part of the xdm login window is corrupted after the first X session has

Bug#630625: mysql-client-5.1: add support for properly chained SSL certificates and linking against OpenSSL

2011-06-15 Thread Mark Nipper
Package: mysql-client-5.1 Version: 5.1.57-1.3 Severity: wishlist Tags: patch Having recently configured MySQL 5.1 for the first time to properly support SSL certificates under RHEL 6, I found out that the Debian version of the MySQL 5.1 library does not correctly connect to such servers

Bug#629326: encfs: change Depends from fuse-utils to just fuse

2011-06-05 Thread Mark Nipper
Package: encfs Version: 1.7.4-2.1+b1 Severity: normal Since fuse-utils is a dummy package now, the Depends in the encfs control file needs to be updated to just fuse I believe. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (650, 'testing'), (600,

Bug#629327: sshfs: change Depends from fuse-utils to just fuse

2011-06-05 Thread Mark Nipper
Package: sshfs Version: 2.2-1 Severity: normal Since fuse-utils is a dummy package now, the Depends in the sshfs control file needs to be updated to just fuse I believe. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (650, 'testing'), (600,

Bug#589884: [buildd-tools-devel] Bug#589884: schroot seems to fail when using libpam-ldap / libnss-ldap

2010-07-22 Thread Mark Nipper
driven. Very slick! -- Mark Nipper ni...@bitgnome.net (XMPP) +1 979 575 3193 - I cannot tolerate intolerant people. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#589884: schroot seems to fail when using libpam-ldap / libnss-ldap

2010-07-21 Thread Mark Nipper
Package: schroot Version: 1.4.7-1 Severity: important While trying to run schroot -p --debug=notice on a system with lib(pam|nss)-ldap installed and configured (in both the chroot and main system), I'm getting: --- D(1): Loading config file: /etc/schroot/schroot.conf D(1): Loading data

Bug#485989: metadata=1 problems with initramfs

2010-03-27 Thread Mark Nipper
Package: mdadm Version: 3.0.3-2 Severity: normal Following up to my initial report in this bug, I finally found that not messing with the metadata line generated correctly by mkconf but rather removing the name portion of the line fixed the problem for my mdadm entry that is using

Bug#572525: php-apc: install 3.1.3p1 via pecl CLI

2010-03-23 Thread Mark Nipper
Package: php-apc Version: 3.0.19-2 Severity: normal I had similar issues with a complex internal application when upgrading from PHP 5.2 to 5.3 (in Debian). Removing php-apc fixed all the weird problems we were seeing. Upgrading using the pecl CLI installed with php-pear to php-apc

Bug#568604: msmtp: support for authentication method LOGIN is not compiled in

2010-02-05 Thread Mark Nipper
Package: msmtp Version: 1.4.19-1 Severity: normal The subject pretty much says it all. msmtp is complaining because this option is no longer configured in the Debian binary. I'm not sure if this was an upstream or maintainer change. But while using LOGIN over TLS may still not be

Bug#568604: Acknowledgement (msmtp: support for authentication method LOGIN is not compiled in)

2010-02-05 Thread Mark Nipper
Doh! Known issue: --- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564661 You can close this as a duplicate. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#563365: mumble-server: Server connection failed: Connection refused. IPv4/IPv6 problem

2010-01-02 Thread Mark Nipper
Package: mumble-server Version: 1.2.0-1 Severity: important I've already reported this upstream on the Mumble SourceForge site at: --- https://sourceforge.net/projects/mumble/forums/forum/492607/topic/3504682 The general problem is that murmurd appears to be binding to all IPv6

Bug#485989: mdadm: similar problem with latest version in testing after dist-upgrade from stable

2009-12-30 Thread Mark Nipper
Package: mdadm Version: 3.0.3-2 Severity: normal I'm adding this problem report to this existing bug, although it may not actually belong here. The problem is that md1 is not being autoassembled correctly inside the initrd. Looking at this bug report, I thought it was because

Bug#550763: squirrelmail: search bug in release candidate

2009-10-12 Thread Mark Nipper
Package: squirrelmail Version: 2:1.4.20~rc2-1 Severity: important Tags: patch There is a bug in the release candidate version of SquirrelMail currently in Debian. This bug breaks search capability against Cyrus 2.2 (the Debian version also). The bug report on the SM side is at:

Bug#466343: openclipart: new upstream version 0.19 finally published

2009-08-31 Thread Mark Nipper
Package: openclipart Version: 0.18+dfsg-8 Severity: normal Upstream finally published a new version as of March 31, 2009. The release of version 0.19 can be found at: --- http://openclipart.org/media/viewfile/downloads.xml and includes almost twice as many images as the 0.18 release.

Bug#541089: xterm: well, maybe not...

2009-08-11 Thread Mark Nipper
Package: xterm Severity: normal Actually, it appears that suddenly the colorBDMode resource is being honored. I had it (along with colorBLMode and colorULMode) defined in my .Xresources file as true. So it appears yesterday's update actually fixed a long standing issue possibly.

Bug#541089: xterm: bold color attribute now displaying as black by default

2009-08-11 Thread Mark Nipper
Package: xterm Version: 244-1 Severity: minor With yesterday's update of xterm, bold attributes are displaying in the color black. I'm assuming '+bdc' got set by default somehow instead of '-bdc'? Anyway, since a lot of people probably use black as their default background

Bug#541089: xterm: bold color attribute now displaying as black by default

2009-08-11 Thread Mark Nipper
, xterm is actually working as documented now (which apparently it wasn't before). So thanks! :) -- Mark Nipper ni...@bitgnome.net (XMPP) (979)575-3193 - If the fool would persist in his folly he would become wise. -- one of the Proverbs of Hell from William Blake's _The Marraige of Heaven

Bug#520941: nagios3-common: missing then statement on conditional

2009-05-18 Thread Mark Nipper
Package: nagios3-common Severity: normal If this is the same bug as what I just saw trying to remove nagios3-common, I got the following upon removal: --- /var/lib/dpkg/info/nagios3-common.prerm: line 23: syntax error near unexpected token `fi' because the if statement is missing a then

Bug#516528: ejabberd: 2.0.5 has been released upstream

2009-04-05 Thread Mark Nipper
Package: ejabberd Version: 2.0.3-2 Severity: normal It would be nice if 2.0.5 could be packaged soon. Not only would it fix the s2s problems against the newest versions of libssl, but it would also clear up bug #520852 (CVE-2009-0934) which was fixed in 2.0.4. -- To UNSUBSCRIBE,

Bug#521691: linux-image-2.6.29-1-amd64: appears to be a bug in netfilter

2009-03-31 Thread Mark Nipper
Package: linux-image-2.6.29-1-amd64 Version: 2.6.29-2~snapshot.13298 Severity: normal I just ran into this earlier this evening. It was happening after trying to download the linux-source-2.6.29 package, and it would only make it through 5-10MB before everything would die. Same results

Bug#521691: Info received (linux-image-2.6.29-1-amd64: appears to be a bug in netfilter)

2009-03-31 Thread Mark Nipper
Well, scratch that. I think I just experienced the same problem even without NF loaded. Moving back to 2.6.26 for now. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#520523: dpkg: may be a problem in lsb-base

2009-03-20 Thread Mark Nipper
Package: dpkg Version: 1.14.25 Followup-For: Bug #520523 The offending line is in /lib/lsb/init-functions at line 52. It reads: --- args=--start --chdir '$PWD' --nicelevel $nice --quiet --oknodo Getting rid of the single apostrophes fixes the problem. But I'm not sure it's the right

Bug#500150: mysql-server-5.0: bug in subquery handling not found in most recent upstream

2008-09-25 Thread Mark Nipper
Package: mysql-server-5.0 Version: 5.0.51a-12 Severity: important So I just ran across this bug which is not present in 5.0.67 upstream. My report on the bug is at: --- http://bugs.mysql.com/bug.php?id=39639 Essentially, the subquery form of an identical join statement is

Bug#494273: php-apc: Debian version should include apc.php script from upstream

2008-08-08 Thread Mark Nipper
Package: php-apc Version: 3.0.19-1 Severity: wishlist The Debian package should keep a copy of the apc.php script from the upstream source at least in /usr/share/doc/php-apc. This control script is extremely valuable. If you decide to do this, you might also recommend the php5-gd

Bug#488703: php-apc: new upstream release 3.0.19

2008-06-30 Thread Mark Nipper
Package: php-apc Version: 3.0.18-1 Severity: normal It's wonderful to finally see PHP APC packaged in Debian. However, there has been a newer version available at: --- http://pecl.php.net/package/APC since 2008-05-15. Just wanted to file this in hopes that this package might be upgraded

Bug#407619: iceweasel: same problem with 3.0~rc2-1

2008-06-17 Thread Mark Nipper
Package: iceweasel Version: 3.0~rc2-1 Followup-For: Bug #407619 This is simply a me too on the latest version of the package. This bug is definitely because of the iceweasel-gnome-support package. If removed, the problem goes away. -- System Information: Debian Release: lenny/sid APT

Bug#455858: db_port is commented out during update in sympa.conf and breaks update

2007-12-11 Thread Mark Nipper
Package: sympa Version: 5.3.3-5 Severity: important Every time sympa updates, it breaks upon trying to restart the services because the update insists on commenting out db_port in sympa.conf which is required on my machine to connect to my PostgreSQL server. I have to run something like:

Bug#443076: spamassassin: patch /usr/share/perl5/Mail/SpamAssassin/BayesStore/PgSQL.pm to fix escape

2007-12-11 Thread Mark Nipper
Package: spamassassin Version: 3.2.3-1 Followup-For: Bug #443076 Okay, some more details on this particular problem. It's not a bug per se, but it does tend to fill up your logs a bit with needless information. The warning that is generated is something like this: --- Dec 12

Bug#445212: erroneous path information in /usr/share/postgresql-8.2-plsh/createlang_pgplsh.sql

2007-10-03 Thread Mark Nipper
Package: postgresql-8.2-plsh Version: 1.2-2 Severity: important It looks like during the build process the file createlang_pgplsh.sql has some incorrect path information included from the build process. I have: --- CREATE FUNCTION pg_catalog.plsh_handler() RETURNS language_handler AS

Bug#443690: xfwm4: wrong display chosen in multi-head setup when using startup notification

2007-09-23 Thread Mark Nipper
Package: xfwm4 Version: 4.4.1-3 Severity: important I've been running xfce4 for awhile now using a multi-head disply configuration (:0.0 and :0.1, no Xinerama). Most of my menu items have Use startup notification checked. Up until a recent update (I assume the update to 4.4.1-3 today

Bug#433587: [Pkg-shadow-devel] Bug#433587: request to add /usr/sbin/nologin to /etc/shells

2007-07-18 Thread Mark Nipper
it as a debconf item would be the best option? Or maybe an informational notice of some kind? But it's whatever. I just ran across this one situation where it should be defined and thought that it might be something to consider. Thanks for thinking about it. -- Mark Nipper

Bug#433587: request to add /usr/sbin/nologin to /etc/shells

2007-07-17 Thread Mark Nipper
Package: login Version: 1:4.0.18.1-11 Severity: wishlist This is a request to add /usr/sbin/nologin to /etc/shells. I ran across a problem earlier with vsftpd not allowing access to a user account which I only wished to allow FTP access on my system. The reason vsftpd was disallowing

Bug#432511: initscripts: rpc.statd not starting until runlevel 2

2007-07-10 Thread Mark Nipper
Package: initscripts Version: 2.86.ds1-38 Followup-For: Bug #432511 Just adding a me too here. For whatever reason, 2.6.22 seemed to introduce this new behavior. I'm running 2.6.22 on my NFS server while this client (and two others) are both running 2.6.21.5 still. Anyway, I'm

Bug#431827: mount hangs as normal user when fstype is auto depending on blkid.tab data

2007-07-05 Thread Mark Nipper
Package: mount Version: 2.12r-19 Severity: normal I have several identical Debian unstable machines in my office. A user reported not being able to mount his USB flash drive on one of these machines, while it was working fine on the other two. This didn't make any sense at first because

Bug#370141: X crashing on PCI-e 7900GTX

2007-06-11 Thread Mark Nipper
definitely close this bug finally. :) -- Mark Nippere-contacts: 4320 Milam Street [EMAIL PROTECTED] Bryan, Texas 77801-3920 http://nipsy.bitgnome.net/ (979)575-3193 AIM

Bug#416180: vpnc: disabling dead peer detection working but not the default

2007-06-09 Thread Mark Nipper
Package: vpnc Version: 0.4.0-3 Followup-For: Bug #416180 With the sync of SVN revision 174, disabling dead peer detection seems to fix the problems people were having, but the option has to be fed to either vpnc or vpnc-connect manually, which is unexpected for a lot of people most likely

Bug#370141: X crashing on PCI-e 7900GTX

2007-05-08 Thread Mark Nipper
out awhile and Xorg is maturing nicely. -- Mark Nippere-contacts: 4320 Milam Street [EMAIL PROTECTED] Bryan, Texas 77801-3920 http://nipsy.bitgnome.net/ (979)575-3193 AIM/Yahoo

Bug#379185: kernel-package: possibly the same or related problem as original poster

2006-09-30 Thread Mark Nipper
' \ -e 's/=SA//g' -e 's/=L/ /g' \ -e 's/=I//g'\ -e 's/=CV/./g' \ -e 's/=M/Mark Nipper [EMAIL PROTECTED]/g' \ -e 's/=ST/linux/g' -e 's/=B/i386/g

Bug#389329: php4-xcache: new stable release upstream 1.0.2

2006-09-24 Thread Mark Nipper
Package: php4-xcache Version: 1.0-4 Severity: normal I realize you just started packaging 1.0 at the beginning of September, but I thought I'd point out that 1.0.1 came out 20060909 and 1.0.2 came out 20060916. Just filing this report as a reminder for packaging 1.0.2 whenever you get

Bug#374967: samba: XP client unable to access files with a question mark in the name

2006-06-22 Thread Mark Nipper
Package: samba Version: 3.0.22-1 Severity: important This may be related to the previously reported quotation mark bug (Debian bug #333778), but I'm not sure. Anyway, I have a file named: --- 02-you know what you are?.flac which appears as: --- 0J1HP7~2 with the default mangle

Bug#362404: xfonts-x3270-misc: x3270 fonts are now in the wrong location

2006-06-03 Thread Mark Nipper
Package: xfonts-x3270-misc Version: 3.3.4p6-3.1 Followup-For: Bug #362404 With the transition to the new Xorg font location, the package is putting the fonts in the wrong location. Currently fonts are going in: --- /usr/share/fonts/X11/fonts/misc/ where I think they actually just need

Bug#362404: patch to fix xfonts-x3270-misc using incorrect path

2006-06-03 Thread Mark Nipper
Package: xfonts-x3270-misc Version: 3.3.4p6-3.1 Followup-For: Bug #362404 As a follow-up to my last report, here's the rather trivial patch to fix the problem. I don't know about the incorrect path making the package unusable, but it almost certainly breaks policy and since the postinst

Bug#370141: X crashing on PCI-e 7900GTX

2006-06-03 Thread Mark Nipper
Package: xserver-xorg-video-nv Version: 1:1.0.1.5-2 Severity: important The card shows up as: --- :05:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0290 (rev a1) :05:00.0 0300: 10de:0290 (rev a1) --- I'm attaching my Xorg.0.log. I'm assuming this is

Bug#363248: xserver-xorg: still present in 7.0.15

2006-05-02 Thread Mark Nipper
Package: xserver-xorg Version: 1:7.0.15 Followup-For: Bug #363248 I just wanted to bump this to stay the bug is still happening with 7.0.15. No matter which protocol is selected, ExplorerPS/2 is always written to file. -- System Information: Debian Release: testing/unstable APT

Bug#361384: same problem in libdspam7-drv-mysql

2006-04-12 Thread Mark Nipper
Package: dspam Version: 3.6.4-3 Followup-For: Bug #361384 I'm seeing the exact same problem with the installation of libdspam7-drv-mysql. It looks like a debconf problem: --- $ DEBCONF_DEBUG=developer ./libdspam7-drv-mysql.postinst configure debconf (developer): frontend started debconf

Bug#357992: patch against nvidia-kernel-source/1.0.8178-2 for 2.6.16

2006-03-21 Thread Mark Nipper
Package: nvidia-kernel-source Version: 1.0.8178-2 Followup-For: Bug #357992 Attached is patch consolidating the differences between the Debian nVidia source and the nVidia patch set to allow compilation under 2.6.16. Patch has been tested and works under amd64. -- System Information:

Bug#354631: zsh: error in compaudit with 4.3.0-dev-5-1 as root

2006-03-01 Thread Mark Nipper
On 01 Mar 2006, Clint Adams wrote: compaudit:107: unknown group What groups is root in? What NSS modules are used to fetch the groups? What is the group ownership of every directory in root's $fpath and the parent directories of those? Bear with me. This is going to be a bit of

Bug#354633: zsh: %n in prompt expansion no longer set as root with 4.3.0-dev-5-1

2006-03-01 Thread Mark Nipper
On 01 Mar 2006, Clint Adams wrote: What does `getent passwd root` output? root:x:0:0:root:/root:/bin/zsh4-static -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#354633: zsh: %n in prompt expansion no longer set as root with 4.3.0-dev-5-1

2006-03-01 Thread Mark Nipper
On 01 Mar 2006, Clint Adams wrote: What does `getent passwd root` output? root:x:0:0:root:/root:/bin/zsh4-static Ah. Are you experiencing this problem with zsh or only with zsh-static? I just tried /bin/zsh instead of zsh-static and both this bug (354633) and bug 354631 went away.

Bug#354633: zsh: %n in prompt expansion no longer set as root with 4.3.0-dev-5-1

2006-03-01 Thread Mark Nipper
On 01 Mar 2006, Clint Adams wrote: I just tried /bin/zsh instead of zsh-static and both this bug (354633) and bug 354631 went away. What's the difference now? Neither problem happened in previous zsh-static's. Previously, zsh-static still relied on /lib/libnss* to get

Bug#354631: zsh: error in compaudit with 4.3.0-dev-5-1 as root

2006-02-27 Thread Mark Nipper
Package: zsh Version: 4.3.0-dev-5-1 Severity: normal Starting with 4.3.0-dev-5-1, I now get: --- compaudit:107: unknown group with: --- autoload -U compinit compinit in my .zshrc when logging in as root. I don't get it as any other user and this happens across multiple different

Bug#354633: zsh: %n in prompt expansion no longer set as root with 4.3.0-dev-5-1

2006-02-27 Thread Mark Nipper
Package: zsh Version: 4.3.0-dev-5-1 Severity: normal I set my prompt using: --- export PS1=[EMAIL PROTECTED]/%l:%~ With 4.3.0-dev-5-1 and logged in as root, %n is empty and so my prompt always starts with @. I tried dropping the bold clause around the %n, but that didn't help. It also

Bug#342660: cyrus22-imapd: suggest making skiplist the default database backend for new installs

2005-12-09 Thread Mark Nipper
Package: cyrus22-imapd Version: 2.2.12-1 Severity: wishlist Tags: patch After recent problems upgrading from the 2.2.12 packages previously available from debian.speedblue.org which were using db3 to the new official packages using db4.2, I would suggest making the default backend for

Bug#342314: cyrus22-imapd: long line bug in Cyrus

2005-12-06 Thread Mark Nipper
Package: cyrus22-imapd Version: 2.2.12-1 Severity: important Tags: patch Please include the patch below as seen on the DSPAM users list recently (and supposedly already reported to the Cyrus folks, but no new releases have been made upstream since then). And thanks for getting

Bug#341396: iptables: error while saving state

2005-11-30 Thread Mark Nipper
Package: iptables Version: 1.3.3-2 Severity: important I've had iptables installed for a long time, but I've never had netfilter compiled into my kernel. Well, recent activity caused me to finally do so, and the first time I went to do '/etc/init.d/iptables save active', I got: ---

Bug#315346: removal of /var/log/aptitude causes issues

2005-11-30 Thread Mark Nipper
Package: aptitude Version: 0.4.0-3 Followup-For: Bug #315346 I'm not sure if this is addressed in the latest unstable or experimental version, but I removed aptitude earlier today and the prerm or postrm script failed because /var/log/aptitude or /var/log/aptitude.[0-9].gz (or something

Bug#336553: New Debian mirror submission

2005-10-30 Thread Mark Nipper
Package: mirrors Severity: wishlist Site: mirror.tamu.edu Type: leaf Archive-http: /debian/ CDImage-http: /debian-cd/ Mirrors-from: rsync://rsync.osuosl.org::debian and rsync://ftp-linux.cc.gatech.edu::debian-cd Maintainer: Mark Nipper [EMAIL PROTECTED] Country: US United States Location

Bug#336042: esmtp: same error in package slapd

2005-10-27 Thread Mark Nipper
Package: esmtp Version: 0.5.1-2.0.1 Followup-For: Bug #336042 This same TLS error is happening with the current version of slapd in etch. The bug is #335780. Just letting both maintainers know about this problem since it looks like it might end up being a libssl issue. -- System

Bug#335780: slapd: same error in esmtp package

2005-10-27 Thread Mark Nipper
Package: slapd Version: 2.2.26-4.0.1 Followup-For: Bug #335780 Just so there isn't too much duplication of effort, the same bug has been reported to the package esmtp in bug #336042. I'll report this bug over there too so both maintainers are aware. I'm getting this same error

Bug#195948: URL for workaround list

2005-10-20 Thread Mark Nipper
Package: wnpp Followup-For: Bug #195948 Owner: Mark Nipper [EMAIL PROTECTED] Just in case someone gets to the end here like I did and is wondering where the workaround list is, the URL is: --- http://workaround.org/pipermail/dspam-debian/ Hopefully that is okay to give out. Wasn't too

Bug#195948: URL for workaround list

2005-10-20 Thread Mark Nipper
far, so good. -- Mark Nippere-contacts: Computing and Information Services [EMAIL PROTECTED] Texas AM Universityhttp://ops.tamu.edu/nipsy/ College Station, TX 77843-3142 AIM/Yahoo: texasnipsy ICQ

Bug#195948: URL for workaround list

2005-10-20 Thread Mark Nipper
-drv7_3.6.0-1_i386.deb libdspam-dev_3.6.0-1_i386.deb libdspam7_3.6.0-1_i386.deb libmysql-drv7_3.6.0-1_i386.deb libpgsql-drv7_3.6.0-1_i386.deb libsqlite3-drv7_3.6.0-1_i386.deb So that isn't to say it's finished, but looks to be headed more in the right direction. -- Mark Nipper

Bug#195948: URL for workaround list

2005-10-20 Thread Mark Nipper
the rules/control/... files. As Jesus pointed out, most of those files are empty anyway. So: --- http://debian.pumuki.org/dspam/ might be the better choice for now. -- Mark Nippere-contacts: Computing and Information Services

Bug#330859: cherokee: new upstream version 0.4.26 since 19/20 Sep 2005

2005-09-30 Thread Mark Nipper
Package: cherokee Version: 0.4.26-1 Severity: wishlist This is simply a request to update the official Debian package to 0.4.26. I grabbed the Debian source for 0.4.25 and copied over the debian directory into 0.4.26 and built it locally, but an official release would be nice. -- System

Bug#241223: apache2-common: me three?

2005-09-29 Thread Mark Nipper
Package: apache2-common Version: 2.0.54-5 Followup-For: Bug #241223 I'm having what I assume is the exact same problem. Automatically built indexes avoid showing files larger than 2GB and directly trying to GET those files produces a 403 and this in error.log: --- (75)Value too large for

Bug#330798: cherokee: invalid symlink causes autoindex to partially fail

2005-09-29 Thread Mark Nipper
Package: cherokee Version: 0.4.25-1 Severity: important This needs to go upstream most likely. I noticed on my Debian server which acts as a mirror server for a number of different distributions that the SuSE directory index was not complete. Looking at the file system showed all the

Bug#330494: dbus-1: installation fails if shadowconfig is off

2005-09-28 Thread Mark Nipper
Package: dbus-1 Version: 0.23.4-1 Severity: important Just noticed this on a server which is using LDAP primarily for authentication and for whatever reason had 'shadowconfig off' set at the time. The error I received upon trying to install an updated version of dbus-1 (may have been

Bug#323902: same file in both libafterimage0 and libafterstep1

2005-08-19 Thread Mark Nipper
Package: libafterimage0 Version: 2.1.2-1 Severity: grave Justification: renders package unusable I received the following while updating: --- Unpacking libafterimage0 (from .../libafterimage0_2.1.2-1_i386.deb) ... dpkg: error processing

Bug#321935: fuse-source: patch for this problem

2005-08-13 Thread Mark Nipper
Package: fuse-source Version: 2.3.0-3 Followup-For: Bug #321935 I've attached the patch. Amazing how this simple omission causes such problems! :) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1,

Bug#321935: fuse-source: try this patch again...

2005-08-13 Thread Mark Nipper
Package: fuse-source Version: 2.3.0-3 Followup-For: Bug #321935 Damn white space. Try this patch instead. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell:

Bug#292932: openssh-server: both patches should be included

2005-08-13 Thread Mark Nipper
Package: openssh-server Version: 1:4.1p1-6 Followup-For: Bug #292932 There shouldn't be any security issues with including at least the performance patch to allow for scalable buffer sizes. But it would be nice if the hpn11-none cipher patch could also be included as there is

Bug#292932: openssh-server: actually, to provide something useful...

2005-08-13 Thread Mark Nipper
Package: openssh-server Version: 1:4.1p1-6 Followup-For: Bug #292932 In an attempt to provide something useful to this request (rather than my me too post a moment ago), I just ran across this: ---

Bug#292932: openssh-server: okay, so here's the patch I used...

2005-08-13 Thread Mark Nipper
Package: openssh-server Version: 1:4.1p1-6 Followup-For: Bug #292932 Well, after downloading those two patches from: --- http://www.psc.edu/networking/projects/hpn-ssh/ I realized that they were the same but one has the none cipher changes thrown in. Blah. Anyway, I'm attaching

Bug#292932: openssh-server: new patch to fix disconnect problem

2005-08-13 Thread Mark Nipper
Package: openssh-server Version: 1:4.1p1-6 Followup-For: Bug #292932 This patch is to replace my previous. It reverts one of Darren's suggested changes which was causing disconnects on large transfers and reverses the order in which I had added the -hpn string to the version string. --

Bug#321562: zsh-static: libc version problem indeed

2005-08-07 Thread Mark Nipper
Package: zsh-static Version: 4.2.5-11 Followup-For: Bug #321562 Yep, looks right. I rebuilt locally with 4.2.5-10 and the segfaults quit. I also just upgraded to 4.2.5-11 from incoming (not built locally) and it's fixed there also. So I guess you can close this one. Thanks for

  1   2   >