Bug#344108: Bug#344373: spampd - autolearn fails
> "Sven" == Sven Mueller <[EMAIL PROTECTED]> writes:
>> [28638] dbg: config: using "/root/.spamassassin/user_prefs" for
>> user prefs file
Sven> If you want to use auto-learn (or auto-whitelist for that
Sven> matter), you will have to configure spamassassin in a way that
Sven> it uses some other location. However, since this has to be
Sven> configured in the spamassassin configs, there is nothing I could
Sven> do about this.
I missed this before. The two kludges are either exporting
HOME=/var/lib/spampd in init.d/spampd or adding
$ENV{'HOME}'='/var/lib/spampd' to the perl script.
To elevate that from kludge to hack, do a gecos lookup to find
spampd's HOME. Ie, something like:
my ($pwname,$pwpasswd,$pwuid,$pwgid,$pwquota,$pwcomment,$pwgcos,
$pwdir,$pwshell,$pwexpire) = getpwnam($user);
$ENV{'HOME'} = $pwdir;
after the options are read in should do it.
-JimC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#250216: [tex-k] Plans about supporting TrueType/Type42 fonts in dvips?
> "Karl" == Karl Berry <[EMAIL PROTECTED]> writes: Karl> Support for OpenType would probably be even more useful going Karl> forward. Do you know if they be handled via Type42? Or some Karl> other way? [Pre Scriptum: written for the archives and the CCed bugreport; not just for the people on the CC list -JimC] If by OpenType you mean sfnt/CFF fonts, you just embed the (optionally subsetted) CFF table mostly just like a type1. (The CFF table is in type2 format; you may need to convert the outlines to type1 depending on which version of postscript is targeted. It may also be CID keyed; that may also require a conversion.) The rest of the tables are only relevant for deciding which glyphs to set for a given string and what if any kerning is required. Type42 works for all sfnt/glyf fonts, no matter what additional tables they have. (OpenType, AAT, Graphite, et al.) -JimC -- James H. Cloos, Jr. <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#312115: libapache2-mod-log-sql-dbi
Currently libapache2-mod-log-sql-dbi is the only way to log apache2 to pgsql. I am about to start testing it (once I figure out how to configure it to log to pgsql, what the table needs to look like, etc). So please consider this a vote to keep it (and therefore the dependency on libdbi0) in. I'll follow up here on whether I see any crashes due to making this change in my web server's logging. -JimC -- James Cloos <[EMAIL PROTECTED]> OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#733295: gnutls-bin: please compile GnuTLS with DANE support
>>>>> "AM" == Andreas Metzler writes: AM> libdane requires and links against libunbound. libunbound OTOH AM> is linked against OpenSSL's libssl on Debian[1]. A possible way forward is to configure unbound --with-nss, which should provide license compatibility for all libunbound users. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#505893: seems fixed upstream
Unless this bug is specific to debian, this should be fixed in xmessage-1.0.4 with a current Xorg server. At least it does the right thing for me on my Gentoo workstation. (I only use debian on my servers) -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699746: probably fixed upstream
Xprop(1) got a significant overhall a while back. This should work correcly now. That said, xterm(1) doesn’t do the right thing with such titles in that it stores them on the server as STRING where they ought to be stored as COMPOUND_TEXT for WM_NAME and WM_ICON_NAME and as UTF8_STRING for _NET_WM_NAME and _NET_WM_ICON_NAME (which xterm does not set at all). (The latter two props, of course, were created just to provided the names as UTF8_STRINGs rather than as COMPOUND_TEXT.) -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 signature.asc Description: PGP signature
Bug#739255: nginx: Please upgrade nginx to 1.5 for sid and jessie.
A further note: As of 'zilla 28 (ff28 and sm 2.25) spdy2 is gone. Chromium droped support for spdy2 in 33 or 34. And mod_spdy doesn't support apache 2.4. So nginx 1.5 is the only decent-performance option for those running web services who want to support spdy also for the current beta (soon to be non-beta) releases of the major browsers. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707761: pdns-backend-pgsql: IP fields too short for master/slave operation over IPv6
>>>>> "PD" == Peter van Dijk writes: JC>> The ip column should not be varchar or text. JC>> It should be inet. PD> We are happy to consider this change upstream Pull request sent. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 signature.asc Description: PGP signature
Bug#727608: hylafax-client: jpg conversion fail, -dpi with float
>>>>> "FD" == Frank Doepper writes: FD> "%R" is substituted with a float, 204.00 in my case, and apparently FD> gets interpreted by pnmtops as 0 instead of 204. pnmtops.c expects either INT or INTxINT for -dpi (it calls strtol(dpiOpt, &dpistr2, 10) to parse the numbers), so sending it a float is a bug. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734923: base-passwd: The change to uucp shell broke the uucp cron jobs
Ah. Yes, that is a valid fix. I should have found 734723 before reporting. ☹ Thanks, -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727841: powl() inaccurate but only at runtime
>>>>> "Z" == Zefram writes: Z> On amd64, powl() is generating inaccurate results when called at runtime, Z> but if a call to it gets constant-folded at compile time (by gcc 4.7) Z> then the constant-folded result is much more accurate. AIUI, gcc uses multi-precision arith for constant folding, so that it can generate accurate results even when cross-compiling. The difference you show is likely libm vs mpfr. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727841: powl() inaccurate but only at runtime
[I hit send to soon ... -JimC] And glibc 2.17 gets the same result as gcc does. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729612: nsd: fails to install: dpkg-query: error: package 'nsd3' is not installed
Package: nsd Version: 4.0.0-4 Followup-For: Bug #729612 This bug also applies when upgrading from 4.0.0-3 to 4.0.0-4, if the nsd3 transition package is not also installed. The (non-)?existence of the old /ets/nsd3 directory does not impact the bug. (This bug — at least when upgrading from 4.0.0-3 — also affects ubuntu trusty.) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nsd depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.52 ii libc6 2.17-95 ii libevent-2.0-5 2.0.21-stable-1 ii libssl1.0.01.0.1e-4 ii lsb-base 4.1+Debian12 nsd recommends no packages. nsd suggests no packages. -- Configuration Files: /etc/nsd/nsd.conf changed [not included] -- debconf information: nsd3/old_confdir_exists: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752479: Version 1.0.0 released in April; version 1.0.1 in May
Package: roundcube Version: 0.9.5-4 Severity: normal The changelog from 0.9.5 to 1.0.0 is significant; 1.0.1 fixes even more. Upgrading probably will fix many of the debian bug reports. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages roundcube depends on: ii roundcube-core 0.9.5-4 roundcube recommends no packages. roundcube suggests no packages. Versions of packages roundcube-core depends on: ii dbconfig-common1.8.47+nmu1 ii debconf [debconf-2.0] 1.5.53 ii libjs-jquery 1.7.2+dfsg-3 ii libmagic1 1:5.19-1 ii php-auth 1.6.4-1 ii php-mail-mime 1.8.8-1 ii php-net-smtp 1.6.1-1 ii php-net-socket 1.0.14-1 ii php5 5.6.0~beta4+dfsg-4 ii php5-common5.6.0~beta4+dfsg-4 ii php5-intl 5.6.0~beta4+dfsg-4 ii php5-json 1.3.5-2 ii php5-mcrypt5.6.0~beta4+dfsg-4 ii roundcube-pgsql0.9.5-4 ii tinymce3.4.8+dfsg0-1 ii ucf3.0030 Versions of packages roundcube-core recommends: ii nginx-full [httpd-cgi] 1.6.0-1 ii php5-gd 5.6.0~beta4+dfsg-4 ii php5-pspell 5.6.0~beta4+dfsg-4 Versions of packages roundcube-core suggests: ii php-auth-sasl 1.0.6-1 pn php-crypt-gpg pn roundcube-plugins -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752845: policyd-weight: recent libnet-dns-perl upgrade has broken policyd-weight.
Package: policyd-weight Version: 0.1.15.2-7 Severity: grave Justification: renders package unusable Policyd started generating bogus scores. After a restart it generates errors like this: postfix/policyd-weight[26689]: warning: child: err: Undefined subroutine &main::dn_expand called at /usr/sbin/policyd-weight line 3590, line 26.#012 that results in the mail getting refused. main::dn_expand is from: use Net::DNS::Packet qw(dn_expand); The dn_expand() in /usr/lib/perl5/Net/DNS/Packet.pm is commented out. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages policyd-weight depends on: ii adduser 3.113+nmu3 ii libio-socket-inet6-perl 2.72-1 ii libnet-dns-perl 0.77-3 ii libnet-ip-perl 1.26-1 ii lsb-base 4.1+Debian13 ii perl 5.18.2-4 Versions of packages policyd-weight recommends: ii perl [libsys-syslog-perl] 5.18.2-4 policyd-weight suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752845: recent libnet-dns-perl upgrade has broken policyd-weight.
I see that there is a dn_expand_PP method; perhaps having policyd-weight
call that explicitly might work?
The dn_expand method in /usr/lib/perl5/Net/DNS/Packet.pm is:
sub dn_expand {
#FYImy ($packet, $offset) = @_;
return dn_expand_XS(@_) if $Net::DNS::HAVE_XS;
# warn "USING PURE PERL dn_expand()\n";
return dn_expand_PP(@_, {} ); # $packet, $offset, anonymous hash
}
so it should work, albeit slower than it used to.
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752845: recent libnet-dns-perl upgrade has broken policyd-weight.
>>>>> "WD" == Werner Detter writes: WD> I've prepared a new package, please test: WD> wget http://www.werner-detter.de/policyd-weight_0.1.15.2-8_all.deb It works. Your patch matches what I tried after sending my last note. It is slow for un-cached senders, but those tend to be more rare than repeat senders. And I'd have to bring up a test box to see whether using the XS version, as it used to, also was slow for un-cached. I guess "ship it" is the idiom of the day. ;^) -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#748972: libmilter1.0.1: Opendkim and opendmarc milters have allocation leaks; libmilter is common element
Package: libmilter1.0.1 Version: 8.14.4-5 Severity: normal I’m not certain which package is at fault. I’m starting here because both milters use libmilter1.0.1. The bug is socket-type agnostic. It occurs with unix domain and with tcp sockets. Every milter event allocates ram which is not free(2)d. (It shows up in VmData in /proc/$pid/status.) I estimate that the process vm grows about 10k-20k per message. Rss doesn’t grow. If swap usage grows, it doesn’t do so fast enough to confirm. So the allocated pages may be untouched. Eventually the milter gets a segv. The forensics are insufficient to confirm whether the leak causes or even contributes to the segv. -- Package-specific info: Output of /usr/share/bug/libmilter1.0.1/script: ls -alR /etc/mail: /etc/mail: total 20 drwxr-xr-x 3 root root 4096 Jan 31 2013 . drwxr-xr-x 143 root root 12288 May 20 21:16 .. drwxr-xr-x 2 root root 4096 May 20 21:16 m4 /etc/mail/m4: total 12 drwxr-xr-x 2 root root 4096 May 20 21:16 . drwxr-xr-x 3 root root 4096 Jan 31 2013 .. -rw-r--r-- 1 root root 789 Oct 8 2012 clamav-milter.m4 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libmilter1.0.1 depends on: ii libc6 2.18-7 libmilter1.0.1 recommends no packages. libmilter1.0.1 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#749024: Bad command line in init script
Package: asterisk
Version: 1:11.9.0~dfsg-1
Severity: important
Today’s update breaks /etc/init.d/asterisk.
It passes $ETCDIR (/etc/asterisk) as the value for the -C option when
starting asterisk.
The -C option specifies a file, not a directory.
The easy, short-term workaround is to add:
ETCDIR=/etc/asterisk/asterisk.conf
to /etc/default/asterisk.
If the init script wants to use -C and ETCDIR, it should pass
-C ${ETCDIR}/asterisk.conf
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages asterisk depends on:
ii adduser 3.113+nmu3
ii asterisk-config 1:11.9.0~dfsg-1
ii asterisk-core-sounds-en [asterisk-prompt-en] 1.4.22-1
ii asterisk-core-sounds-en-gsm 1.4.22-1
ii asterisk-modules 1:11.9.0~dfsg-1
ii libc6 2.18-7
ii libcap2 1:2.22-1.2
ii libedit2 3.1-20140213-1
ii libgcc1 1:4.9.0-4
ii libpopt0 1.16-8
ii libsqlite3-0 3.8.4.3-3
ii libssl1.0.0 1.0.1g-4
ii libstdc++64.9.0-4
ii libtinfo5 5.9+20140118-1
ii libxml2 2.9.1+dfsg1-3
Versions of packages asterisk recommends:
ii asterisk-moh-opsound-gsm 2.03-1
ii asterisk-voicemail [asterisk-voicemail-storage] 1:11.9.0~dfsg-1
ii sox 14.4.1-4
Versions of packages asterisk suggests:
pn asterisk-dahdi
ii asterisk-dev 1:11.9.0~dfsg-1
pn asterisk-doc
pn asterisk-ooh323
pn asterisk-vpb
-- Configuration Files:
/etc/default/asterisk changed [not included]
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740775: sks: Upgrade fails (again)
>>>>> "CM" == Christoph Martin writes: CM> sks depends on db-util which depends on the current db utils package. CM> The current db-util in testing/jessie has version 5.3 and depends on CM> db5.3-utils. CM> So this should be no problem. Maybe at the time of your install there CM> was an old version of db-util installed. IIRC, the bug is that a newer version of db5.x-utils got installed, the old version was removed, and apt permitted said removal even though sks needed said old version. I think sks has to depend on the exact version of db5.x-utils it uses, to ensure that it always can recover the db. Unless there is a better way to ensure that the proper recovery tool is available. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741293: git over https fails with "gnutls_handshake() failed: A record packet with illegal version was received."
>>>>> "AG" == Alessandro Ghedini writes: AG> If you are using Debian sid, gnutls-cli is built against libgnutls28 (while AG> licurl uses libgnutls26) so this isn't much useful (unfortunately we can't AG> switch to libgnutls28 for licensing problems). Didn’t the gmp relicensing fix such license issues? Or is that not yet in place for sid? -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741293: git over https fails with "gnutls_handshake() failed: A record packet with illegal version was received."
>>>>> "AG" == Alessandro Ghedini writes: AG> If you mean its relicensing to LGPL3+, No, I mean the more recent relicense to LGPL3+ OR GPL2+, as mentioned on the gnutls thread on debian-devel. I confirmed it in the README in their HG repo https://gmplib.org/repo/gmp/ and the changset: changeset: 16260:da670a8513db user:Torbjorn Granlund date:Mon Jan 27 21:47:39 2014 +0100 summary: Update library files license to use LGPL3+ and GPL2+. But I see that the change is not reflected in the README in the repo for the 5.1 branch, https://gmplib.org/repo/gmp-5.1/. I don't know their intent as to which versions are relicensed. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#739920: nginx: 1.5.10 available, adds SPDY/3.1
I was planning a missive, to end with the suggestion that, even if it couldn’t make sid, it would be enough for it to make experimental. But it seems you beat me to the punch. Thanks! -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742059: nginx: CVE-2014-0133: SPDY heap buffer overflow
>>>>> "y" == yatiohi writes: y> we are not vulnerable since nginx is compiled with the --with-debug y> configure option. Does that also apply to 1.5.11 in experimental? y> Although, we will release 1.4.7-1 shortly to follow y> upstream and include a few module updates as well. Updating experimental to 1.5.12 is welcome in either case. Thanks! -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#698911: pdns-backend-pgsql: Default schema for pdns-backend-pgsql needs update
Package: pdns-backend-pgsql Version: 3.1-4 Severity: grave Justification: renders package unusable Dear Maintainer, Debian’s default schema for pdns-backend-pgsql specifies that the records.content column be varchar(255). That is insufficient for some records, such as RRSIG RRs used with dnssec. Upstream has updated to varchar(65535), although text also would be find. When using deb’s version of pdns as an axfr slave nameserver, pdns will be unable to save the zones which have been dnssec-signed by the master server into the records table, blocking operation for such zones completely. (pdns tries to save the AXFR data in a SQL TRANSACTION; because the RRSIG and other longer records fail to fit in the varchar(255), the transaction fails and pgsql does a ROLLBACK instead when pdns issues its COMMIT.) Simply ALTERing the records table to set the TYPE of contents to text or to varchar(65535) makes everything just work. It is likely that this bug also applies to the related pdns-backend-mysql and pdns-backend-sqlite packages, but I have not confirmed so. The fix for new installs is a simple one-line change to the default schema as described above. Existing installs which choose automatic maintainance of the pdns db, though, should be updated by way of an: ALTER TABLE records ALTER COLUMN content TYPE VARCHAR(65535); (translated as necessary for the other backends, if they indeed also have this bug.) *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages pdns-backend-pgsql depends on: ii dbconfig-common1.8.47+nmu1 ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38 ii libgcc11:4.7.2-5 ii libpolarssl0 1.1.4-1 ii libpq5 9.1.7-1 ii libssl1.0.01.0.1c-4 ii libstdc++6 4.7.2-5 ii pdns-server3.1-4 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages pdns-backend-pgsql recommends: ii postgresql-client-9.1 [postgresql-client] 9.1.7-1 Versions of packages pdns-backend-pgsql suggests: pn postgresql -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639290: sid dist-upgrade failing
My i386 sid box has started complaining: E: Could not perform immediate configuration on 'perl-modules'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) I've tried using -o APT::Immediate-Configure=0 and I've also tried apt-get install on each of the package dist-upgrade wants to upgrade. Botht echniques failed. This seems to be related to the perl 5.12 -> 5.14 update. My amd64 box dist-upgraded w/o such a problem. Is there any way around this? -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685808: pdns-backend-pgsql: schema out-of-date, please provide no-dnssec.schema
Please note that not everyone who uses the pdns packages uses the upstream (or packaged) schema exactly as is. So do not automatically make any schema changes on upgrades. Matching upstream would be beneficial for new installs, but the schema on existing installs only should be edited if you can confirm that it is identical to the current package's suggested schema. Otherwise please just note the recommended changes. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659920: rss2email incorrectly chooses big5 character encoding
Package: rss2email Version: 1:2.71-0.1 Severity: important I was unable to read a number of r2e generated emails today because they were in big5, even though the text was in english. This seems to be related to the use of non-ascii quotes (‘’“”). Any email it generates ought to be in utf8 these days. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages rss2email depends on: ii python 2.7.2-10 ii python-feedparser 5.0.1-1 ii python-html2text 3.200.3-1 rss2email recommends no packages. rss2email suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659920: rss2email incorrectly chooses big5 character encoding
>>>>> "EM" == Etienne Millon writes:
EM> Can you try to put the following line in your config.py ?
EM> CHARSET_LIST='US-ASCII', 'UTF-8', 'BIG5', 'ISO-2022-JP', 'ISO-8859-1'
Ahh. It had been so long since I set my current config up, that either
I had forgotten about r2e's config.py or my setup predated CHARSET_LIST...
I used »CHARSET_LIST='US-ASCII', 'ISO-8859-1', 'UTF-8'« because those
will cover all of the feeds which I monitor.
There is little reason to have 8859-* after utf-8; it would never fall
through to it. But having it ahead of utf-8 can have benefit.
Something in my chain forces r2e's 8859-1 to cte:qp and its utf-8 to
cte:b64. Given that the former can be read w/o decoding, it is useful
to permit its use.
I don't know where the CJ encodings should fall in the default set.
Having them ahead of utf-8 causes harm for non-asian-language feeds,
but having utf-8 first will unify zh and jp text. That is, if the
reader's MUA is configured to prefer a jp font for ideographs, then
zh text in utf-8 will be rendered with that jp font. And visa-versa
if their MUA prefers a zh_{CN,TW,HK} font. I don't know how much
harm that would do. I usually can recognize zh_CN vs zh_TW vs jp
vs kn text, but cannot actually read any of them
Were the character-set matching to limit big5 and 2022 to characters
which are not used outside Asia, though, they could remain before utf-8.
That means that neutral chars -- like the quotes -- should not match
the CJK character sets. Only matching characters which have width
property W in unicode's EastAsianWidth.txt should do the trick.
(The quotes have A, presumably for Ambiguous.)
Explicitly configuring it, though, does fix things for me.
Thanks.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#704683: kamailio: Bulding with tls fails in install phase
Package: kamailio
Version: 3.3.0-1
Severity: normal
Using control.tls and adding tls to PACKAGE_GROUPS results in this from
dpkg-buildpackage:
find:
`/build/kamailio-3.3.0/debian/kamailio-db-modules/usr/lib/x86_64-linux-gnu/kamailio':
No such file or directory
find /build/kamailio-3.3.0/debian/kamailio-tls-modules -depth -empty -type d
-exec rmdir {} \;
mv
/build/kamailio-3.3.0/debian/kamailio-berkeley-modules/usr/sbin/kambdb_recover \
/build/kamailio-3.3.0/debian/kamailio-berkeley-bin/usr/sbin/kambdb_recover
mv: cannot move
‘/build/kamailio-3.3.0/debian/kamailio-berkeley-modules/usr/sbin/kambdb_recover’
to
‘/build/kamailio-3.3.0/debian/kamailio-berkeley-bin/usr/sbin/kambdb_recover’:
No such file or directory
make: *** [install] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
due to the fact that the directories debian/kamailio-db-modules and
kamailio-berkeley-bin do not exist.
My guess is that the control.tls.sh script from svn was not run since
the primary control file last was updated.
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages kamailio depends on:
ii adduser3.113+nmu3
ii libc6 2.13-38
ii libncurses55.9-10
ii libpcre3 1:8.31-2
ii libreadline6 6.2+dfsg-0.1
ii libtinfo5 5.9-10
ii multiarch-support 2.13-38
ii python 2.7.3-4
kamailio recommends no packages.
Versions of packages kamailio suggests:
ii kamailio-berkeley-modules 3.3.0-1
ii kamailio-carrierroute-modules 3.3.0-1
ii kamailio-cpl-modules 3.3.0-1
pn kamailio-ldap-modules
ii kamailio-lua-modules 3.3.0-1
pn kamailio-mono-modules
pn kamailio-mysql-modules
ii kamailio-perl-modules 3.3.0-1
ii kamailio-postgres-modules 3.3.0-1
ii kamailio-presence-modules 3.3.0-1
ii kamailio-python-modules3.3.0-1
pn kamailio-radius-modules
ii kamailio-redis-modules 3.3.0-1
ii kamailio-snmpstats-modules 3.3.0-1
pn kamailio-unixodbc-modules
ii kamailio-xml-modules 3.3.0-1
ii kamailio-xmpp-modules 3.3.0-1
-- Configuration Files:
/etc/default/kamailio changed [not included]
/etc/kamailio/kamailio.cfg changed [not included]
/etc/kamailio/kamctlrc changed [not included]
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#704683: Acknowledgement (kamailio: Bulding with tls fails in install phase)
Using the control.tls.sh script to create a new control.tls from the control which apt-get source kamailio creates fixes the build. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706160: general: it should be easier for ordinary developers to work with Debian packages
>>>>> "CALP" == Carlos Alberto Lopez Perez writes: CALP> This can be even more simple: CALP> dh_make -f ../foo-1.tar.gz CALP> dpkg-buildpackage And where does one find dh_make? Searching on goog suggests it would be part of debhelper. But it isn't: :; dpkg -L debhelper|grep dh_make /usr/bin/dh_makeshlibs /usr/share/man/de/man1/dh_makeshlibs.1.gz /usr/share/man/fr/man1/dh_makeshlibs.1.gz /usr/share/man/man1/dh_makeshlibs.1.gz /usr/share/man/es/man1/dh_makeshlibs.1.gz :; dpkg -l|grep debhelp|perl -pe 's/ +/ /g' ii debhelper 9.20120909 all helper programs for debian/rules -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707761: pdns-backend-pgsql: IP fields too short for master/slave operation over IPv6
The ip column should not be varchar or text. It should be inet. The proper fix is: alter table supermasters alter COLUMN ip type inet using ip::inet; and change the sql which creates the table during install to use inet for that column. That column is only supposed to hold ipv4 or ipv6 addresses, which is exactly what the inet type is for. As an added bonus, inet stores the address as an integer, so it should take up less space than a text/varchar/char column. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#710657: gnutls: Negiotates an SSL v3.0 cipher when talkign to openssl using TLS 1.2
For whatever it is worth, using the same cipher suite on the servers (each running sid), gnutls3 chooses this when talking to nginx-1.4.1: - Description: (TLS1.2-PKIX)-(ECDHE-RSA-SECP256R1)-(AES-256-GCM)-(AEAD) but this when talking to apache2.4: - Description: (TLS1.2-PKIX)-(ECDHE-RSA-SECP256R1)-(AES-128-CBC)-(SHA1) Both ought to negotiate the former, mainly due to GCM and AEAD. Sid's gnutls2 negotiates the same suites, but gnutls2 doesn't have the nice Description output which gnutls3 has. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685808: pdns-backend-pgsql: schema out-of-date, please provide no-dnssec.schema
>>>>> "MH" == Marc Haber writes: MH> On Thu, Sep 20, 2012 at 12:29:20PM -0400, James Cloos wrote: JC>> Please note that not everyone who uses the pdns packages uses the JC>> upstream (or packaged) schema exactly as is. So do not automatically jC>> make any schema changes on upgrades. MH> I disagree with that. dbconfig-common is a widely used helper package, MH> and it does automatic schema changes on upgrades. This is hard to turn MH> off and even harder to handle. My appologies for the ambiguity in my paragraph above. MH> The packages do, however, ask on installation whether dbconfig-common MH> should be used. If the admin chose to use dbconfig-common when installing pdns, then of course it is reasonable to auto-update the schema by way of dbconfig-common when pdns is upgraded. I intended that paragraph specifically for the case where the admin did not choose to use dbconfig-common, including those cases where pdns was instaled before the deb first aquired dbconfig-common support. My primary NS is nearly a decade old now, mostly if not entirely on sid. And still x86, even though its last several hosts ran amd64 dom0 kernels. AFAICR dbconfig was not an option when I installed pdns on it. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685808: pdns-backend-pgsql: schema out-of-date, please provide no-dnssec.schema
>>>>> "MH" == Marc Haber writes: >> AFAICR dbconfig was not an option when I installed pdns on it. MH> But it became an option some time in the past, and it should MH> have asked you. Did it? If it did, given that I had an existing install with a customized schema, it is unlikely that I would have. I have no recolection of such a question, though. I found /etc/dbconfig-common/pdns-backend-pgsql.conf, which has: , | dbc_install='false' | dbc_upgrade='false' | dbc_remove='' ` so evidently I did answer no. :) I do use it on my (recent) secondaries. And it did reduce the time it took to bring up a secondary, which was welcome. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685808: pdns-backend-pgsql: schema out-of-date, please provide no-dnssec.schema
>>>>> "MH" == Marc Haber writes: MH> So we can agree that everything is fine and no changes are necessary MH> (aside from the database schema)? I think I got out of sync with this. It was too long w/o context. Even in the case where dbconfig is set to manage the schema, anyone who runs pdns as a seconday with signed zones will have to have updated the schema on said secondaries to make it work. I wouldn't want any changes made by dbconfig to what I already had to fix. At least not w/o first reading the update script. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#704118: kamailio version 4.0 is out; it is a significant improvement.
Package: kamailio Version: 3.3.0-1 Severity: normal Please update sid to kamailio 4.0 sooner rather than later. The support for websockets and the completion of the merger with ser significantly improve kamailio’s value and capabilities. According to http://packages.debian.org/search?keywords=kamailio it is only in sid, so the wheezy freeze should not have to affect the schedule for updating. Please see http://www.kamailio.org/w/2013/03/kamailio-v4-0-0-released/ for the release announcement. Upstream also announced some packages (http://www.kamailio.org/w/2013/03/packages-for-v4-0-0/) which might be helpful for writing deb’s. -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Versions of packages kamailio depends on: ii adduser3.113+nmu3 ii libc6 2.13-38 ii libncurses55.9-10 ii libpcre3 1:8.31-2 ii libreadline6 6.2+dfsg-0.1 ii libtinfo5 5.9-10 ii multiarch-support 2.13-38 ii python 2.7.3-4 kamailio recommends no packages. Versions of packages kamailio suggests: pn kamailio-berkeley-modules ii kamailio-carrierroute-modules 3.3.0-1 pn kamailio-cpl-modules pn kamailio-ldap-modules pn kamailio-lua-modules pn kamailio-mono-modules pn kamailio-mysql-modules ii kamailio-perl-modules 3.3.0-1 ii kamailio-postgres-modules 3.3.0-1 ii kamailio-presence-modules 3.3.0-1 pn kamailio-python-modules pn kamailio-radius-modules pn kamailio-redis-modules pn kamailio-snmpstats-modules pn kamailio-unixodbc-modules ii kamailio-xml-modules 3.3.0-1 ii kamailio-xmpp-modules 3.3.0-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707041: ifupdown: then clauses require something more than just comments
Package: ifupdown Version: 0.7.41 Followup-For: Bug #707041 The postinst script says: # Generic stuff done on all configurations if [ "$1" = "configure" ] ; then if [ -f /etc/network/interfaces ] ; then # We don't need loopback interface definition anymore as # ifupdown handles loopback interface on its own from now else # ! -f /etc/network/interfaces The syntax error is that nothing but comments appear in the then clause. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ifupdown depends on: ii dpkg 1.16.10 ii initscripts 2.88dsf-41 ii iproute 20120521-3+b4 ii libc62.13-38 ii lsb-base 4.1+Debian9 ifupdown recommends no packages. Versions of packages ifupdown suggests: ii isc-dhcp-client [dhcp-client] 4.2.4-6 ii net-tools 1.60-24.2 pn ppp pn rdnssd -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707049: bugs.debian.org: tls cert on bugs-master.debian.org for a different hostname
Package: bugs.debian.org Severity: normal Dear Maintainer, When sending a bug, the mail gets sent to the mx bugs-master.debian.org. The exim handling port 25 on that box has a tls cert with CN=buxtehude.debian.org. AFAICT there also is no subAltName extension for bugs-master.debian.org. This prevents the use of TLS with at least some MTAs (I use postfix): :; egrep /smtp'\[' /var/log/mail.log May 7 06:23:18 localhost postfix/smtp[19450]: SSL_connect error to bugs-master.debian.org[140.211.166.26]:25: Connection reset by peer May 7 06:23:18 localhost postfix/smtp[19450]: 252371001CE: Cannot start TLS: handshake failure May 7 06:23:18 localhost postfix/smtp[19450]: Host offered STARTTLS: [bugs-master.debian.org] May 7 06:23:19 localhost postfix/smtp[19450]: 252371001CE: to=<707...@bugs.debian.org>, relay=bugs-master.debian.org[140.211.166.26]:25, delay=454, delays=453/0.04/0.95/0.45, dsn=2.0.0, status=sent (250 OK id=1UZbJQ-5W-5M) As you can see, the mail got sent, but without tls. If you want the MX for bugs.d.o to be bugs-master.d.o, then that SHOULD be the mailname of the box bugs-master.d.o A resolves to and the TLS cert SHOULD have that name either in CN or subAltName. Or, the actual mailname and CN should be specified in the MX RR. Try running: :; gnutls-cli -p 25 --starttls bugs-master.debian.org to see why the tls handshake failed above. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699848: sks: sks_build.sh hangs
Any chance of getting ths changes John suggested into the package? ,< to be added to /etc/sks/sksconf > | pagesize: 16 | ptree_pagesize:16 ` -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#709840: [Pkg-postgresql-public] Bug#709840: postgresql-client-common: pg_dump version is old (9.0.6)
>>>>> "RH" == Rene Horn writes: RH> But what other packages have pg_dump in it, particularly one for RH> Postgres 9.1? The /usr/bin/pg_dump in postgresql-client-common is just a wrapper. The actual binary for 9.1 is /usr/lib/postgresql/9.1/bin/pg_dump and is part of postgresql-client-9.1. (Determined empirically by looking at one of my sids.) -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#644200: Two unrelated liby-dev packages in the archive
With the rename, I now get this when upgrading: The following packages have unmet dependencies: bison : Depends: libbison-dev (= 1:2.5.dfsg-2) but it is not installed ... Unpacking libbison-dev (from .../libbison-dev_1%3a2.5.dfsg-2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libbison-dev_1%3a2.5.dfsg-2_i386.deb (--unpack): trying to overwrite '/usr/lib/i386-linux-gnu/liby.a', which is also in package liby-dev 1:2.5.dfsg-1 configured to not write apport reports dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libbison-dev_1%3a2.5.dfsg-2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) And there doesn't seem to be any way around this using apt. The suggested apt-get -f install dies the same was as upgrade, and neither remove nor purge can remove the liby-dev package. One must 'dpkg --purge liby-dev' in order to install libbison-dev. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645539: pdns: powerdns 3.0 has been available since July, adds dnssec support
Package: pdns-server Version: 2.9.22-9 Severity: normal File: pdns Dear Maintainer, An update to pdns 3.0, with it support for dnssec, is needed. My deb box is too small to compile it from src (given the dep on boost). Thank you. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.30.9-xenU (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages pdns-server depends on: ii adduser3.113 ii debconf [debconf-2.0] 1.5.41 ii libc6 2.13-21 ii libgcc11:4.6.1-15 ii libstdc++6 4.6.1-15 ii ucf3.0025+nmu2 ii zlib1g 1:1.2.3.4.dfsg-3 Versions of packages pdns-server recommends: ii pdns-doc 2.9.22-9 Versions of packages pdns-server suggests: pn pdns-backend-pgsql [pdns-backend] 2.9.22-9 pn pdns-recursor -- Configuration Files: /etc/insserv.conf.d/pdns-server [Errno 21] Is a directory: u'/etc/insserv.conf.d/pdns-server' -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#711714: www.debian.org: Typo in description file for anonscm.debian.org git project pkg-fonts/fontforge-doc.git
Package: www.debian.org Severity: minor There is a typo in the description file for pkg-fonts/fontforge-doc.git, which gets propagated into the Subject lines of the commits messages. One can see the source of the typo with: :; curl http://anonscm.debian.org/git/pkg-fonts/fontforge-doc.git/description Packaging for fontforce document ^ It has fontforce (c as in can) instead of fontforge (g as in ghost). -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#711714: [Pkg-fonts-devel] Bug#711714: www.debian.org: Typo in description file for anonscm.debian.org git project pkg-fonts/fontforge-doc.git
>>>>> "PW" == Paul Wise writes: PW> This issue had nothing to do with either fontforge-doc (the package), Which is why I did not report it against the pacakge. PW> nor with www.debian.org. reportbug clearly states to report anything not "covered above" against www.debian.org. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681248: [Pkg-pdns-maintainers] Bug#681248: Here too, powerdns fails after upgrade to wheezy...
The first thing one must do when installing pdns-server is remove /etc/powerdns/pdns.d/pdns.simplebind. And again should an upgrade re-create it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681248: [Pkg-pdns-maintainers] Bug#681248: Here too, powerdns fails after upgrade to wheezy...
>>>>> "TL" == Tom Laermans writes: TL> Except an upgrade should never (re)create it at all if a working TL> configuration is already in place. Cool. I couldn't remember, so through that in just in case. Glad to know that it isn't an issue. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#681248: [Pkg-pdns-maintainers] Bug#681248: Here too, powerdns fails after upgrade to wheezy...
>>>>> "MH" == Marc Haber writes: JC>> And again should an upgrade re-create it. MH> That should not happen. Great. I couldn't remember whether it had, so through that in just in case. It is good to know that it will not. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682426: cups: filter gs takes several minutes consuming 100 % of CPU
A comment on http://bugs.ghostscript.com/show_bug.cgi?id=694360 suggests that transparency might be a factor in why gs uses so much ram. At some point in the last year or two, gecko apps started generating full page transparency whenever *any* image happened to be ARGB (png or gif). Previously, it either pre-flattened the image to the background or skipped the alpha channel when printing. (I don't know which.) This means that the bug will show up for any files printed from gecko apps whenever the webpage or mail has any alpha-blending at all. I haven't tracked down whether this aspect of the bug is in cairo or in how gecko calls cairo. (I also should note that I do not have a deb box on which I can test this; my debs are all headless. My GUI tests are all done on Gentoo. YMMV.) -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682426: cups: filter gs takes several minutes consuming 100 % of CPU
>>>>> "TK" == Till Kamppeter writes: TK> The problem is indeed Cairo, which creates a full-page transparency TK> layer even for small images. Thanks for narrowing that down. TK> There are already upstream bug reports on Cairo. Perhaps you should TK> comment there. I'm subscribed to the cairo-bugs list, but I do not remember seeing such reports. Or maybe I thought there were fixed and this were something else? I'll look for them. TK> This bug report should be moved to Cairo. A DD needs to do that, yes? -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712015: cups-filters: cups-pdf produces ugly pdfs through its pixelated font
>>>>> "BR" == Bastien ROUCARIES writes: BR> It seems that by default cups-ppd use postscript 2 level only (see BR> /usr/share/ppd/cups-pdf/CUPS-PDF.ppd) BR> Could you try to replace LanguageLevel: "2" by LanguageLevel : "3" With the cups-filters pacakge, that won't help. Ubuntu pushed a change into that package upstream which limits all output of the pdftops filter to LanguageLevel2 (or lower) due to a bug with one HP printer. Which breaks the filter for everyone else. See the comment in the src. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682426: cups: filter gs takes several minutes consuming 100 % of CPU
On Thu, Jun 20, 2013 at 05:23:30PM +0200, Bastien ROUCARIES wrote: > On Thu, Jun 20, 2013 at 12:34 AM, Till Kamppeter > > This bug report should be moved to Cairo. > > I respectfully disagree: > - cairo should help here to not generate transparancy > - ghostscript should be optimized and they are some patch to do this I asked on the cairo list. Adrian replied that cairo has been fixed. Cairo now limits the size of the SMasks as much as possible, pre-composes images which do not intersect with vector objects to white when generating postscript, but still outputs transparency when generating pdf. Both gs and poppler/splash (ie odf2ps and pdftops) raster the entire page if *anything* on the page has transparancy. There is an enhancement request upstream for gs to raster only the necessary sections (I didn’t get a reference, and haven’t found it yet). I don’t yet know whether there already is an enhancement request for splash to raster only what needs to be. For the gs bug which came from this report, Ken would like to know whether using a smaller raster dpi (such as 300) avoids the extreme processing times the bug reporter saw. ps2writer defaults to 720 dpi, splash defaults to 300 dpi. To test, use the pdf2ps command above with the added switch: -r300 . Separately, thanks to this report, there was talk of gs, possibly, adding support to use banding when ram is tight. Such a change would improve the gs experience for everyone using it on low-ram boxen. (That is the same mechanism it uses in embedded mode on printers.) -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#714817: More information?
>>>>> "RB" == Rogério Brito writes: RB> Just for reference: are you sure that you didn't have apt or RB> aptitude's flag to download recommended packages by default? Coincidentally, I discovered that the day before you sent this. I hadn't noticed it over the 15ish years I've used debian. It seems to be on by default. There is nothing under /etc/apt which references APT::Install-Recommends, and apt-get(8) describes the flag --no-install-recommends, not --install-recommends, implying that the latter is the intentional default. RB> What happens if you try to uninstall mplayer2? I must have done so. Neither mplayer nor mplayer2 are currently installed on any of my deb vms. But I don't remember doing so. :( So it obviously did not uninstall youtube-dl. (I do recall purging wayland a few days ago; that might have taken mplayer2 and many of its deps along for the ride. Freed up quite a bit of disk.) RB> Just so you know, mplayer2 *is* used, regardless of if it is a headless box RB> or not, to download videos with protocols other than http (in the same RB> fashion as rtmpdump). I didn't know that. Thanks for the info. RB> In any case, *if* this is a bug, I don't really know if this is a bug with RB> my packaging of youtube-dl or with the dependency resolving tools of RB> installers. As I noted above, I hadn't noticed --no-install-recommends before. Although it is (very) surprising that an upgrade would pull in something which hadn't been pulled in during the initial install. After time and sleep, I suspect that I should have posted this against apt rather than against youtube-dl. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#685540: Update needed
With asterisk-11 now in sid, asterisk-flite and asterisk-espeak need, at minimum, re-compilation. Perhaps more. Thanks! -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707761: pdns-backend-pgsql: IP fields too short for master/slave operation over IPv6
>>>>> "MH" == Marc Haber writes: >> alter table supermasters alter COLUMN ip type inet using ip::inet; >> and change the sql which creates the table during install to use inet >> for that column. MH> Can pdns handle that table format? It is transparent to pdns. I've been using it in production since before I posted that. Were pdns to try to store something in that column which wasn't an ip address, pg would complain and the transaction would fail. But pdns only reads that table, and the text returned from a SELECT on an inet column looks like the normal text notation of an ipv4 or ipv6 address. Were someone to store a cidr (such as 10.1.2.4/8) then pdns would complain; but again the result would be no different than if one were to store such data in a text or varchar field. The column needs to be either text, varchar(39) or larger, or inet to support all possible ipv4 and ipv6 addresses. Inet has the benefit of documenting the column's intent and rejecting most bogus data before it can confuse or break pdns. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#710360: First autoremovals happen in about 8 days
This bug report is about to get pdns kicked out of Jessie. Please do something about that. Thanks, -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#721702: Latest update generates SEGV in __strcmp_sse42() when parsing the enabled sites.
Package: nginx-extras
Version: 1.4.1-3+b1
Severity: important
File: nginx-extras
As of this update, nginx will not start due to a segv when parsing the configs.
Switching to nginx-full worked around the bug, but at the cost of loosing spdy
support. (That module probably should be in full anyway)
The sks-recommended proxy blob seems to trigger the bug. Eg:
location /pks {
proxy_pass http://127.0.0.1:11371;
proxy_set_header Host $host:$server_port;
proxy_set_header X-Forwarded-For
$proxy_add_x_forwarded_for;
proxy_pass_header Server;
add_header Via "1.1 keys.example.org:80
(nginx)";
proxy_ignore_client_abort on;
}
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#721702: Latest update generates SEGV in __strcmp_sse42() when parsing the enabled sites.
Slavko> the problem is incoming from the "add_header" directive Slavko> (at least for me) Thanks. I have confirmed that on my box as well. It (using add_header to add a Via: header) used to work. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707049: fixed
This looks to be fixed: :; dig bugs.debian.org mx +dnssec ... ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 1 ... ;; QUESTION SECTION: ;bugs.debian.org. IN MX ... ;; ANSWER SECTION: bugs.debian.org.7184IN MX 10 buxtehude.debian.org. bugs.debian.org.7184IN RRSIG MX 5 3 3600 20131005141707 20130907141707 28707 bugs.debian.org. sxy2dP5z/5LgFhvgQAy/15AAb2KiJmrZZpLXr7oMkeyNqzLqBXNI2Akp EsQa+5C0IbE/zF5q+PwmDdbySQbOfnmbFtXW81vVOyEJtA7ILPI+qlVC /oKXW/9Kcf7eORf6w4SPwfyqfW9avrmYL17YJj4eMrBLrkFsUC4OijIn 03ZxiRGbjzfkwepCPDocPDeD Plus: :; dig _25._tcp.buxtehude.debian.org. +tcp +dnssec tlsa ... ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 5, ADDITIONAL: 11 ... ;; QUESTION SECTION: ;_25._tcp.buxtehude.debian.org. IN TLSA ... ;; ANSWER SECTION: _25._tcp.buxtehude.debian.org. 7200 IN TLSA3 1 1 417919AFDC833EA189DAC35EB7B80C03870419BFF56A6BC6F83A94CB 3A0EB8DF _25._tcp.buxtehude.debian.org. 7200 IN RRSIG TLSA 7 5 3600 20131007215407 20130909215407 17309 debian.org. kCpch8UAGv8Bjv4VVZ6dI0RtSKE+YNkucpm5tfC7TrdJfdtPVblu+46a OS8Nl1K9+3fr1TZZTEYHNhyLcj73ra5IUIBEZhuwMZKzCFzAgalJRcLn w7cwmEhqI1DZFboNCzacjV/RGIV2EnBkqeWEGwGVabr1Ey2t4lkfQ38a gMsFzGC6ZJ8p3CFim9qlbKBp Thanks. Doubled. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#722640: nginx: New upstream stable release 1.4.2
And please enable spdy in -full, not just in -extras. Thanks. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#719876: sks: db update broke sks
I rebuilt the database from a dump last night, and it ran for just a few
hours before it died:
07:26:18 Fatal database error: Bdb.DBError("file key has LSN 16/7354485, past
end of log at 4/2091025")
07:26:18 Key addition failed: Sys.Break
07:26:43 Fatal database error: Bdb.DBError("transaction has active cursors")
07:26:43 Key addition failed: Sys.Break
07:27:43 error in callback.: Bdb.DBError("transaction has
active cursors")
07:27:45 error in callback.: Bdb.DBError("transaction has
active cursors")
07:27:48 error in callback.: Bdb.DBError("transaction has
active cursors")
Either sks needs to be rebuilt against the new libdb5.1 or the library
itself needs help.
-JimC
--
James Cloos OpenPGP: 1024D/ED7DAEA6
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712015: cups-filters: cups-pdf produces ugly pdfs through its pixelated font
>>>>> "TK" == Till Kamppeter writes: TK> This is only true if cups-filters is using the Poppler pdftops utility, TK> if Ghostscript is used (and this is the default in Ubuntu and also TK> upstream), level 3 PostScript is generated if the PPD requests it. Ghostscript only has its ps2write output device; they have not written a ps3write device; it never generates Level3. Xpdf’s pdftops(1) and poppler’s pdftops(1) (and, I suppose, ick☺, acro) are the only options if one want to generate level3. CID-keyed fonts and shadings are probably the most significant level3-only features in this context. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654834: rss2email stopped working with python error
Package: rss2email Version: 1:2.71-0.1 Severity: important I now get this on r2e runs: E: could not parse http://www.weather.gov/xml/current_obs/KDKK.rss Traceback (most recent call last): File "/usr/share/rss2email/rss2email.py", line 681, in run name = h2t.unescape(getName(r, entry)) AttributeError: 'module' object has no attribute 'unescape' It looks like the failures started yesterday after an apt-get upgrade which upgraded python-html2text to 3.200.1-1. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages rss2email depends on: ii python 2.7.2-9 ii python-feedparser 5.0.1-1 ii python-html2text 3.200.1-1 rss2email recommends no packages. rss2email suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654834: rss2email stopped working with python error
>>>>> "EM" == Etienne Millon writes: EM> python-html2text 3.200.2-1, has been uploaded to unstable. It seems to EM> fix the issue for me, is it ok for you ? Yes, it works again. Thanks. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#612147: Why using version 1.6.2.9 - it's not a LTS version with Long Term Support?
>>>>> "TC" == Tzafrir Cohen writes: TC> By the time Wheezy is frozen, Asterisk 10 will likely to have been TC> released. It includes quite a few handy improvements, but it's not a TC> LTS. Package it to experimental? I'd certainly like to see 10 in sid. I don't know about wheezy? -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#831448: gitlab: fails to install database
>>>>> "CB" == Christoph Berg writes: CB> cloos: Was your system configured with "en_US" when you installed CB> postgresql? reportbug now reports your locale to be "en_US.UTF-8". I use: LANG=en_US.UTF-8 LC_COLLATE=C LC_CTYPE=en_US.UTF-8 LC_TIME=C and my deb systems also add LANGUAGE=en_US:en when I ssh in. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#855427: quicktun: Does not work
I'll try again once the new version makes it though. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#855653: libreswan: /etc/init.d/ipsec is missing
The missing file is based on: libreswan/initsystems/sysvinit/ipsec.init.in -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#855653: libreswan: /etc/init.d/ipsec is missing
[A wrong version of this email might have gone out; please ignore it in favour of this version. -JimC] The missing file is based on: libreswan/initsystems/sysvinit/init.debian.in -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#855606: sqrt() regression on powerpc/jessie
It may be a bit more informative to add:
printf("0X %A\n", r);
to that main() to see exactly what is different between the two.
The only ppc I have access to are those in the gcc farm and those (the
online ones anyway) only run fedora and aix, so I cannot test it
myself.
Except that everything else reports:
0X 0X1.C48C6001F0ACP+3
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#855427: quicktun: Does not work
The upstream web site recommended using qt_private_key_file in interfaces. Your readme instead recommends qt_private_key. Switching to qt_private_key helped. But there is still the problem that only one tunnel can be used at a time. It would help were the readme to include mention that in order to run multiple tunnels each has to specify a differnt port number for the udp traffic. I had to strace ifup(8) to notice that. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#855606: sqrt() regression on powerpc/jessie
>>>>> Christoph Berg writes: > Jessie: 0X1.C48C6001F0ABFP+3 > Sid:0X1.C48C6001F0ACP+3 Looking tat the code glibc switched from fsqrt to a software version, resulting in the ulp difference. I see on pgsql-hackers, though, that glibc has enabled fma and as a result that difference is avoided. So jessie's libc6 on ppc32 needs to include the fma patch or switch back to using fsqrt. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#855427: quicktun: Does not work
Theonly other issue is that the web site claims that REMOTE_PORT defaults to LOCAL_PORT. When specifying ports in interfaces with qt_local_port and qt_remote_port, remote does not default to local. The readme should detail all of the qt_ options and their (actual) defaults. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#753163: gnupg-agent: depends on pinentry-gtk2
The problem may best be fixed by making pinentry-curses the first of the three possible dependencies. Ie: s(pinentry-gtk2 | pinentry-curses | pinentry)(pinentry-curses | pinentry-gtk2 | pinentry) That way non-gui boxen will get pinentry-curses w/o having to install it before upgrading or at the same time as a gnupg2 install. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742767: TeX Gyre OpenType and wrongly(?) named glyphs
>>>>> "HH" == Hans Hagen writes: HH> As you mention in a previous mail, it's a bug in poppler (or maybe HH> some library it uses) that somehow used glyph names. The bug shows up when the pdf file does not embed the font, forcing viewers and renderers to find a substitute font. A patch has at least been proposed for poppler to treat glyph names like /f_i as equivilent to names like /fi, at least for the f-ligs found in the standard pdf font encodings for the base14 fonts. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742767: TeX Gyre OpenType and wrongly(?) named glyphs
>>>>> "HH" == Hans Hagen writes: HH> if dropping in otf files for type 1 ones is considered a valid HH> solution, then poppler should do more checking anyway for the few f HH> related ligatures (which makes me wonder why the otf file is used as HH> drop-in) Poppler asks fontconfig for a font with whatever name the pdf specifies; it gets back whatever fontconfig provides. (IIRC, it does map the 14 abbreviations like TiRo, Symb, ZaDb, et cetera to the full names before doing the lookup.) For the vast majority of applications, it is better for fontconfig to provide SFNT fonts rather than T1. It is reasonable to expect apps and libs which do only need the glyphs properly to handle that. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#755525: graphviz: Upgrade pulls in unnecessary junk
Package: graphviz Version: 2.26.3-17.1 Severity: normal The new version in sid pulls in 86.0 MB unnecessary junk on headless systems: libaudio2 libcdt5 libcgraph6 libgvc6 libgvpr2 libmng1 libqtcore4 libqtgui4 qtcore4-l10n qt, especially, in unacceptable. The new depends in graphviz must be eliminated. Anything which would require them should be in a separate package. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages graphviz depends on: ii libc6 2.19-7 ii libcdt4 2.26.3-17.1 ii libcgraph5 2.26.3-17.1 ii libexpat1 2.1.0-6 ii libgd3 2.1.0-3+b1 ii libgraph4 2.26.3-17.1 ii libgvc5 2.26.3-17.1 ii libgvpr12.26.3-17.1 ii libx11-62:1.6.2-2 ii libxaw7 2:1.0.12-2 ii libxmu6 2:1.1.2-1 ii libxt6 1:1.1.4-1 Versions of packages graphviz recommends: ii ttf-liberation 1.07.4-1 Versions of packages graphviz suggests: pn graphviz-doc ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4.2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#755382: ITP: fonts-adobe-sourcehansans-cn -- “Source Han Sans CN” A sans-serif Pan-CJK font family (CN subset) that is offered in seven weights
>>>>> "PW" == Paul Wise writes: >> * Package name: fonts-adobe-sourcehansans-cn PW> Due to the need for Adobe's ADFKO, this will have to go to contrib. PW> IIRC ADFKO will become open source at some point and the font could PW> move to main then. AFAICT, fontforge has enough capability to convert the format of the files in the git repo into OTF files, at least. Pehaps also combining those into the OTC files. The outlines are in the repo as type0 (collection of type1) format, but again fontforge can edit and save that format just as well as its own sfd format, so onecan argue that it is close enough to preferred src format. So it seems they are already dfsg-free, even without a dfsg-free release of adfko, yes? Or did I miss something which fontforge and/or fonttools cannot yet accomplish? -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756627: postfix-pgsql broken with libpq5 (9.4~beta2-1) now in jessie and sid
postfix with libpq5-9.4~beta2-1 works fine on a sid box, at least when using pf config likes like: relay_recipient_maps = proxy:pgsql:/etc/postfix/recipients.cf This must be specific to jessie or to the non-proxy case. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#755525: graphviz: Upgrade pulls in unnecessary junk
>>>>> "MK" == Matthias Klose writes: MK> your wording in your message, "junk", "unacceptable", "eliminated" MK> is not acceptable. The package is currently maintained by the QA MK> team, and can need some help. So instead of shouting, just spend MK> some time and send a patch. Thanks for your understanding. Gui libraries are withough question unnessesary junk on a headless server. It is wrong and inappropriate to pretend otherwise. And there was no shouting. Just statements of fact. Dot should not pull in qt. Or gtk. I can take a look into a fix; I don't know how long it'll take. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#748972: libmilter1.0.1: Opendkim and opendmarc milters have allocation leaks; libmilter is common element
>>>>> "AB" == Andreas Beckmann writes: AB> Is this still occurring with the libmilter from jessie, stretch, sid, or AB> experimental? I.e. version 8.14.4-8 or newer. Yes, sid still shows this. And since the last two updates to opendkim, it crashes daily again. Some days multiple times per day. It hadn't been crashing for a while before that. But the Virt still grows constantly. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#777677: nginx: Please package 1.7 releases
>>>>> "TW" == Thomas Ward writes: TW> I can understand the want of the newer features, but there's a bunch of TW> changes upstream in 1.7.x, and I don't think we can call it 'stable' TW> enough for inclusion. Sid really ought to have the most recent nginx release, but if that is too hard to separate from what testing gets, then the current release should be in experimental. But the current release SHOULD be available somwhere easy to apt-get. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#777677: nginx: Please package 1.7 releases
>>>>> "TW" == Thomas Ward writes: JC>> But the current release SHOULD be available somwhere easy to apt-get. TW> We could create a separate nginx source package, called nginx-mainline, TW> that conflicts with the other nginx packages. It would be the mainline TW> branch, whereas nginx would be the stable. That also is a perfect solution for those using nginx on debian. There are packages which maintain several branches in the alioth gits. > the third party plugins do not all build on 1.7.x as they exist now I, for one, don't mind don't mind some missing 3rd party plugins on mainline. As long as it is well announced, and they get added back as they are forward-ported. But then I do not use -extras. Those who do might prefer otherwise -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#751560: opendkim: Please enable DNSSEC by default
>>>>> "SK" == Scott Kitterman writes: SK> The package is compiled with and linked against libunbound. I don't have SK> DNSSEC, so I can't test this. Reading the documentation, I think you SK> additionally have to install unbound (not just the lib) and configure it with a SK> trust anchor. I mis-hypothesized the reason for the error I saw. In the 2.7.0 section of RELEASE_NOTES I see: , | Feature request #SF3545658: Replace "ResolvConf" with "Nameservers" | and add support for NS list overrides for versions of bind | that have res_setservers(). Also rename "UnboundConfigFile" | to "ResolverConfiguration", and make "TrustAnchorFile" | generally available. ` And, indeed, using ResolverConfiguration works. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#751560: opendkim: Please enable DNSSEC by default
opendkim could depend on dns-root-data and have: TrustAnchorFile /usr/share/dns/root.key in the default opendkim.conf. I've been using TrustAnchorFile /var/lib/unbound/root.key on my MXs for the longer of: as long as opendkim has supported TrustAnchorFile or as long as I've run opendkim (I cannot remember which came first.) But have had a local verifying unbound on them longer than that. dns-root-data's /usr/share/dns/root.key has the same data (less comments) as unbound-anchor's /var/lib/unbound/root.key. Passing an unbound.conf to opendkim could be used to modify how it resolves and verifies, but isn't required for dnssec support. It should be reasonable to expect the dns-root-data package to be updated whenever a new dnskey or ns records are published for . so depending on that package should be sufficient. [Had fully to wake up and think about it...] -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#783946: kamailio: Recompile needed due to sid's openssl uprade.
After some further research, I've discoverred that adding:
modparam("tls", "tls_force_run", 1)
to kamailio.cfg allows kama to start, so the bug probably is a bit less
severe than grave. Testing shows that such an addition does allow kam
to not only start, but actually use tls.
That being said, recomilation still is required.
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780797: Package modifying a user-modified config file? [Bug #780797]
I didn't read much of this thread at it occurred; am catching up now. It is absolutely and unquestionably essential that no file in /etc which has *any* local modifications ever be edited on package upgrade w/o the admin's consent. Adding users and groups on install is one thing, editing a locally edited config file during a package upgrade w/o asking for permission, OTOH, is UNacceptable. The normal dialog, with the options for seeing the diff, accepting the maintainers' version, keeping the local version or starting a shell manually to handle it, works fine. The openssh package should use that just like everything else. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#782167: libasterisk-agi-perl: Update available, fixes important bugs
Package: libasterisk-agi-perl Version: 1.01-2 Severity: normal http://asterisk.gnuinter.net/asterisk-perl/latest/CHANGES shows that 1.03 is available with important fixes for agi quoting, manager parsing and a few other fixes. The quoting issues with 1.01 have a real impact on useful real-world AGI code. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libasterisk-agi-perl depends on: ii perl 5.20.2-3 libasterisk-agi-perl recommends no packages. libasterisk-agi-perl suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#787964:
> Issue has already been addressed in an upload I tried to get a bit > before the Jessie freeze but forgot about since. > IPv6 support is configured through a config_site.h file (see > debian/config_site.h). I hope to shortly upload version 2.4. Cool. Thanks. I only noticed it because when using pjsip asterisk would not accept ip6 transports. Looking forward to the updates. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#792303: asterisk-modules: new upload has undesireable depends
>>>>> "TC" == Tzafrir Cohen writes: TC> res_rtp_asterisk and the pjsip modules link with pjproject TC> libraries. I guess further symbols diet may be needed. Perhaps pjproject needs a x vs nox split? -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#804276: kamailio-tls-modules: Incompatible with the new openssl (wants an sslv3 object, which is no longer there).
Daniel posted the fix upstream (including to the 4.3 branch as commit 946e996fed4bed9a62703cdd248777e2c7ab4a89): diff --git a/modules/tls/tls_init.c b/modules/tls/tls_init.c index bd14647..d7f3cef 100644 --- a/modules/tls/tls_init.c +++ b/modules/tls/tls_init.c @@ -344,9 +344,11 @@ static void init_ssl_methods(void) ssl_methods[TLS_USE_SSLv2 - 1] = SSLv2_method(); #endif +#ifndef OPENSSL_NO_SSL3_METHOD ssl_methods[TLS_USE_SSLv3_cli - 1] = SSLv3_client_method(); ssl_methods[TLS_USE_SSLv3_srv - 1] = SSLv3_server_method(); ssl_methods[TLS_USE_SSLv3 - 1] = SSLv3_method(); +#endif ssl_methods[TLS_USE_TLSv1_cli - 1] = TLSv1_client_method(); ssl_methods[TLS_USE_TLSv1_srv - 1] = TLSv1_server_method(); Please upload new debs w/ that patch. Thanks! -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#804596: pdns-server: New version fails to sign axfrs
>>>>> "CH" == Christian Hofstaedtler writes: CH> Could you please check if completely installing those packages makes CH> the error go away? I removedf the geodns backend -- wasn't using it anyway -- and re-upgraded the two remaining packages (server and pgsql backend). The error remains. Using dpkg to downgrade back to: pdns-server_3.4.6-3+b1_amd64.deb pdns-backend-pgsql_3.4.6-3+b1_amd64.deb gets things working again. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#804596: pdns-server: New version fails to sign axfrs
>>>>> "CH" == Christian Hofstaedtler writes: CH> Upstream suggested to run 'pdnssec check-zone' on any zone that CH> shows this behaviour, as they think that "just failing it" should be CH> covered by their testsuite. That helped. Now only one zone fails (even though only two zones had any errors, and previously all zones failed), and it gives a different error pattern: pdns[25904]: Signing thread died because of std::exception: Reading from socket in Signing Pipe loop: Connection reset by peer but I cannot tell from the log which zone failed. The AXFR which initiated just before that log succeeded. And each of them have the correct (new) SOA values on the secondaries. So it looks like running check-all-zones changed something. Thanks for the quick reply. Given that running check-all-zones seems to have cured things (notwithstanding that one std::exception), I think we can close this (or at least lower its severity) and I'll followup on the upstream mailing list. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#804596: pdns-server: New version fails to sign axfrs
>>>>> "PvD" == Peter van Dijk writes: >> So it looks like running check-all-zones changed something. PvD> That doesn’t make any sense :( check-all-zones is a readonly PvD> operation. That is what I had previously presumed but something changed. I only changed two of the zones based on the check-all-zones output and that allowed all of the zones to *start* working again. Perhaps the issue then is that the geoip backend changed its name and thus failed to upgrade with the server and the pg backend. Although my config didn't load the geo backend... I noticed when I grabbed the old debs from the pool that the package name changed from pdns-backend-geo to pdns-backend-geoip. After Christian's first reply I manually removed the geo backend, fixed the couple of errors reported by check (a couple of duplicate CNAME records and an OPENPGPKEY records in raw syntax from when I was trying to add support back before the stroke). After those changes all of the zones worked again. Before them none of the zones worked. Non AXFR requests worked, though. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#804596: pdns-server: New version fails to sign axfrs
>>>>> "PvD" == Peter van Dijk writes: PvD> geo did not change its name - geoip is a different backend. Sorry for forgetting that. I now recall that again. So I should have written about the one backend replacing the other, and as such apt left the old one there. The geoip deb needs to have an annotation that it replaces the geo deb given that there is no 3.4.7 deb for geo. That should have been done when 3.4.6-3 was uploaded, based on the files currently in pool. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#760564: postgresql-9.4: regexp_matches behavior change 9.3 -> 9.4
> select regexp_matches('gestion/football/ligue-des-champions',
> '^((?!d{4}-d{1,2}-d{1,2})[^/]+?)(?:/((?!d{4}-d{1,2}-d{1,2})[^/]+?))(?:/((?!d{4}-d{1,2}-d{1,2})[^/]+?))?$',
> 'g');
Is there a typo in that? I get no matches on 9.3, too.
-JimC
--
James Cloos OpenPGP: 0x997A9F17ED7DAEA6
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764705: [Pkg-postgresql-public] Bug#764705: Bug#764705: Bug#764705: Bug#764705: postgresql-9.4: ERROR: The database format changed between beta 2 and 3. Please dump, but how?
>> This is a rather awkward position for upgraders to be in, as we >> essentially cannot automate this robustly. Is it really that much of a problem to do something like: su -s /bin/sh -c 'pg_dumpall -c' - postgres >/var/tmp/old_pg94.sql pg_dropcluster 9.4 main --stop ... pg_createcluster 9.4 main service postgres start su -s /bin/sh -c 'psql -f /var/tmp/old_pg94.sql template1' - postgres after checking the size of the data directory vs the amount of free disk space, what 9.4 clusters exist, which ports they each use, et cetera, with the upgrade occuring at the ... point? And stop like it currently did if there isn't enough space. I didn't move anything big over to 9.4, just some small stuff I knew I could afford to deal with should a dump/restore be required, but I still had to fuss with one or two of them to get the pattern down. And for one server I even managed to get β3 installed before grabbing a fresh dump from β2, and had to resort to using an old dump (but not so old that I lost anything). I can imagine that it could be quite an ordeal for some users. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764705: [Pkg-postgresql-public] Bug#764705: Bug#764705: Bug#764705: Bug#764705: Bug#764705: postgresql-9.4: ERROR: The database format changed between beta 2 and 3. Please dump, but how?
>>>>> "CB" == Christoph Berg writes: CB> I've now put a nice NEWS message in postgresql-9.4.NEWS, and updated CB> the preinst failure message to show a similar message. The text is: Yes, that is a suitable message. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#815047: postfix: Postfix fails to start after upgrade
How about using: shlib_directory=/usr/lib/postfix/lib daemon_directory=/usr/lib/postfix/daemons Or both sinngular or both plural? If you feel the need to patch postfix to allow the two directories to continue to coexist, please pushd out a temp update which uses two directories until the patch can be written and tested. A quick change like the above Adding the above to lines to /etc/postfix/main.cf mostly worked. It started, but is complaing about my proxy:pgsql: lines, so either the syntax for those changed or something more is wrong -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
