Bug#719638: opu: package libspf2/1.2.9-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: opu Tags: squeeze I got a request (see below, Bug#718581) for an oldstable upload to fix the couple of additional bugs, causing crashes when libspf2 is called to validate email received over IPv6, that were fixed in wheeze but not in squeeze. The diff is quite minimal. Do you think this is worthwhile? friday 2 August 2013 16.51.12, Olivier Diserens wrote: The packaged version in Squeeze does not includes the full ipv6-bugs patch that comes in Wheezy. It means that some SPF resolutions do not correctly work in IPv6 and lead to possible refusal of valid messages. I recompiled the package with this patch (taken from the Wheezy packages) and it fixed the issue. I don't know of any security implication for now, but since it implies some wrong return values it seems quite important. -- Magnus Holmgren Debian DeveloperIndex: debian/patches/ipv6_buffer_miscalculation.dpatch === --- debian/patches/ipv6_buffer_miscalculation.dpatch (revision 74) +++ debian/patches/ipv6_buffer_miscalculation.dpatch (arbetskopia) @@ -1,10 +1,10 @@ #! /bin/sh /usr/share/dpatch/dpatch-run -## ipv6_buffer_miscalculation.dpatch by Matthias Scheler t...@netbsd.org +## ipv6_buffer_miscalculation.dpatch by Matthias Scheler t...@netbsd.org and others ## -## DP: Fix an abort() caused by miscalculating the size of an internal buffer. -## DP: This can crash applications using libspf2 (e.g. milter-greylist) -## DP: in an e-mail gets delivered via SMTP over IPv6 depending on the -## DP: remote machine's IPv6 address. +## DP: Fix various IPv6-related typos, CP bugs etc. +## DP: These can crash applications using libspf2 or give the wrong result if +## DP: an e-mail gets delivered via SMTP over IPv6 depending on the remote +## DP: machine's IPv6 address. @DPATCH@ --- a/src/libspf2/spf_expand.c 2008-11-03 21:29:00.0 + @@ -18,3 +18,42 @@ if (d-dv.url_encode) len *= 3; buflen += len; +--- a/src/libspf2/spf_interpret.c 2008-10-22 11:47:43.0 -0400 b/src/libspf2/spf_interpret.c 2009-09-08 00:42:25.0 -0400 +@@ -505,7 +505,7 @@ + char dst_ip6_buf[ INET6_ADDRSTRLEN ]; + + struct in6_addr src_ipv6; +- intcidr, mask; ++ intcidr, cidr_save, mask; + inti; + intmatch; + +@@ -517,6 +517,7 @@ + cidr = SPF_i_mech_cidr(spf_request, mech); + if ( cidr == 0 ) + cidr = 128; ++ cidr_save = cidr; + + match = TRUE; + for( i = 0; i array_elem( ipv6.s6_addr ) match; i++ ) +@@ -538,7 +539,7 @@ + INET_NTOP(AF_INET6, ipv6.s6_addr, + dst_ip6_buf, sizeof(dst_ip6_buf)); + SPF_debugf( ip_match: %s == %s (/%d): %d, +-src_ip6_buf, dst_ip6_buf, cidr, match ); ++src_ip6_buf, dst_ip6_buf, cidr_save, match ); + } + + return match; +--- a/src/libspf2/spf_compile.c 2008-11-03 15:37:33.0 -0500 b/src/libspf2/spf_compile.c 2009-09-07 23:46:02.0 -0400 +@@ -778,7 +778,7 @@ + const char *end; + const char *p; + +- char buf[ INET_ADDRSTRLEN ]; ++ char buf[ INET6_ADDRSTRLEN ]; + size_t len; + int err; + Index: debian/changelog === --- debian/changelog (revision 74) +++ debian/changelog (arbetskopia) @@ -1,3 +1,10 @@ +libspf2 (1.2.9-4squeeze1) oldstable; urgency=low + + * ipv6_buffer_miscalculation.dpatch: Include further fixes from wheezy +(Closes: #718581). + + -- Magnus Holmgren holmg...@debian.org Tue, 13 Aug 2013 10:27:39 +0200 + libspf2 (1.2.9-4) unstable; urgency=low * Drop obsolete README.Debian-source; move non-obsolete info to signature.asc Description: This is a digitally signed message part.
Bug#711593: pike7.8-gtk: fails to upgrade from 'testing' - trying to overwrite /usr/lib/pike7.8/modules/Tools.pmod/PV.pike
On lördagen den 8 juni 2013, you stated the following: during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. Getting the right modules in the right package drives me crazy! For the record, I did add Replaces and Breaks declarations, I was just one off with the release number. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#708366: marked as done (pike7.8: FTBFS due to conflicting REG_* definitions)
found 708366 7.8.700-3 stop Oops, that didn't work. Apparently I only tested building the package on i386 in my mind. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#698650: Use of uninitialized value when verifying DKIM signatures
On måndagen den 21 januari 2013, Carlos Alberto Lopez Perez wrote:
On a mailserver running spamassassin (Debian/Squeeze), I started to see
this kind of logs a couple of days ago:
Jan 21 18:06:08 mailserver spamd[17151]: Use of uninitialized value
$prms{Selector} in concatenation (.) or string at
/usr/share/perl5/Mail/DKIM/PublicKey.pm line 91. [...]
Do you have any clue of what could cause this errors? Can it be safely
ignored?
The header parser is rather generic and the verifier doesn't actually check
that all required parts are there before trying to fetch the public key.
Possibly the domain and selector are both missing. Do you know what mail
messages caused those log messages?
--
Magnus Holmgrenholmg...@debian.org
Debian Developer
signature.asc
Description: This is a digitally signed message part.
Bug#692212: unblock (pre-approval): pike7.8/7.8.700-2
or write to a
connection that has been abruptly closed (to detect truncation
attacks better).
- Fixed issue where SSL3 async_client objects became garbage even
after close().
- Tools.X509 uses a unique serial number for each selfsigned certificate.
Firefox otherwise complains about serial number clashes.
o Misc:
- System.normalize_path no long fails for files with 8-bit chars in
their names.
- Improved widestring support for Parser.Tabular.
- Fixed a problem in pike -x module that prevented auto tools from
running in the correct directory.
- Fixed issue where GTK objects weren't destroyed properly.
http://pike.ida.liu.se/docs/tutorial/hello/window.xml now
works again.
- Fixed encoding/decoding bug in pike -x httpserver that prevented
files with space in the name from being accessable.
- Parser.XML.Tree contains fixes for add_child_before() and
add_child_after().
- Parser.Tabular fixes support for Stdio.File objects. For example:
Pike v7.8 release 468 running Hilfe v3.5 (Incremental Pike Frontend)
Parser.Tabular(Stdio.File(data.csv), Stdio.File(format.csv));
- Fixed return value from Regexp.PCRE.exec to always have entries for all
submatches.
- Fuse has fixed support for readlink().
- Fixed infinite loop in Audio.Format when reading MP3 frames.
- Added path to pike binary in pike -x module used by verify targets.
Should also fix problems installing modules using pike -x monger.
- Reduce optimization in gethostby{addr,name} that could cause
overzealous caching or results.
--
Magnus Holmgrenholmg...@debian.org
Debian Developer
signature.asc
Description: This is a digitally signed message part.
Bug#692212: unblock (pre-approval): pike7.8/7.8.700-2
On söndagen den 3 mars 2013, intrigeri wrote: Niels Thykier wrote (03 Nov 2012 15:53:00 GMT) : I think we'd need to see a debdiff to determine if this is acceptable. Feel free to filter (e.g. w. filterdiff) autogenerated parts and translations (if those appear in the diff). Also if the diff is large, please check it actually reaches debian-release@l.d.o. Four months have passed without a reply from the requester, so I recommend the release team closes this unblock request. I did send a prompt reply to debian-release, as you can see here: https://lists.debian.org/debian-release/2012/11/msg00122.html I didn't manage to send it to the bug address though. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#693478: unblock: nettle/2.4-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package nettle, fixing problem with documentation missing after upgrade. * Add postinst script that replaces old documentation directory (from before 1.15-4) in nettle-bin with symlink (Closes: #692950). * Spell check package descriptions (Closes: #680627). Thanks to Filipus Klutiero. unblock nettle/2.4-3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693343: unblock: lyskom-server/2.1.2-13
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package lyskom-server
I've taken over this package and fixed the RC bug #689898 that caused it to be
removed
from testing, as well as cleaned up a few other relatively important issues.
With this,
I hope that it can be let back in testing.
unblock lyskom-server/2.1.2-13
Debdiff follows (excluding some changes to config.{guess,sub} files.
diff -Nru --exclude 'config.*' lyskom-server-2.1.2/debian/changelog
lyskom-server-2.1.2/debian/changelog
--- lyskom-server-2.1.2/debian/changelog2012-11-15 16:40:46.0
+0100
+++ lyskom-server-2.1.2/debian/changelog2012-11-15 16:40:46.0
+0100
@@ -1,3 +1,37 @@
+lyskom-server (2.1.2-13) unstable; urgency=low
+
+ * New maintainer.
+ * Rename debian/lyskom-server.copyright debian/copyright as a source
+package should have a debian/copyright file.
+ * Create /var/run/lyskom-server in the init script instead of shipping
+it with the package (Closes: #689898). Thanks Thomas Goirand.
+ * Drop the $startonboot variable, which is rather pointless since
+lyskomd is actually started via cron, is disabled there by default,
+and will start regardless of $startonboot because the status file
+won't exist.
+ * Fix LSB header in the init script: add $remote_fs and move $local_fs
+to Required-Start/Required-Stop; delete commas.
+ * Add dependency on rsyslog | system-log-daemon, since the LSB header
+indicates that lyskomd requires a syslog facility.
+ * Rework and simplify lyskom-server.postinst:
+* Use dpkg-statoverride to set ownership of data and log directories.
+* Don't nullify errors; the package should be left in an unconfigured
+ state in such cases. Remove sanity checks.
+* Simply call adduser with --quiet instead of checking whether the
+ lyskom user already exists.
+* Set stricter modes on the directories.
+ * Don't delete /var/run/lyskom-server/status in the init script. It is
+created by komrunning when shutting down lyskomd to keep updateLysKOM
+from starting lyskomd again.
+ * lyskom-server.postrm: As recommended by policy, don't delete log files
+until on purge. Also, simply rm -rf /var/lib/lyskom-server
+/var/log/lyskom-server.
+ * Add dependendy on cron | cron-daemon, since that's how lyskomd is
+started.
+ * debian/rules: Add build-indep and build-arch targets.
+
+ -- Magnus Holmgren holmg...@debian.org Thu, 15 Nov 2012 09:26:58 +0100
+
lyskom-server (2.1.2-12) unstable; urgency=low
* Added Danish translation of Debconf templates.
diff -Nru --exclude 'config.*' lyskom-server-2.1.2/debian/control
lyskom-server-2.1.2/debian/control
--- lyskom-server-2.1.2/debian/control 2012-11-15 16:40:46.0 +0100
+++ lyskom-server-2.1.2/debian/control 2012-11-15 16:40:46.0 +0100
@@ -1,7 +1,7 @@
Source: lyskom-server
Section: net
Priority: extra
-Maintainer: Peter Krefting pet...@debian.org
+Maintainer: Magnus Holmgren holmg...@debian.org
Build-Depends: debhelper (= 5.0), bison, flex, po-debconf, autotools-dev
Standards-Version: 3.8.2
Homepage: http://www.lysator.liu.se/lyskom/lyskom-server/
@@ -10,7 +10,8 @@
Package: lyskom-server
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, debconf | debconf-2.0, adduser
+Depends: ${shlibs:Depends}, ${misc:Depends}, debconf | debconf-2.0, adduser,
+ rsyslog | system-log-daemon, cron | cron-daemon
Suggests: lyskom-elisp-client | lyskom-tty-client
Homepage: http://www.lysator.liu.se/lyskom/lyskom-server/
Description: Server for the LysKOM conference system
diff -Nru --exclude 'config.*' lyskom-server-2.1.2/debian/copyright
lyskom-server-2.1.2/debian/copyright
--- lyskom-server-2.1.2/debian/copyright1970-01-01 01:00:00.0
+0100
+++ lyskom-server-2.1.2/debian/copyright2012-11-15 16:40:46.0
+0100
@@ -0,0 +1,27 @@
+Package: lyskom-server
+Obtained from: ftp://ftp.lysator.liu.se/pub/lyskom/server
+Packaged for Debian by: Peter Krefting pet...@debian.org
+
+Copyright (C) 1991-2003 Lysator Academic Computer Association.
+The LysKOM server was written by Lars Aronsson, Thomas Bellman, David Byers,
+Per Cederqvist, Pär Emanuelsson, Peter Eriksson, Linus Tolke, Inge Wallin,
+Lars Willför et.al. Please the AUTHORS file for more information.
+
+ LysKOM is free software; you can redistribute it and/or modify it
+ under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 1, or (at your
+ option) any later version.
+
+ LysKOM is distributed in the hope that it will be useful, but
+ WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with LysKOM. If not, write to Lysator, c
Bug#692212: unblock (pre-approval): pike7.8/7.8.700-2
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock I request permission to upload pike7.8 7.8.700-2 to unstable, targeted at wheezy. It would be practically the same as 7.8.700-1, currently sitting in experimental. pike7.8 is the current stable branch of the Pike programming language. Three years after the last stable release, 7.8.352, a new release was finally made this September, just a little too late for the freeze. pike7.8 currently has no rdepends, and few popcon-reported installations. The lack of bug reports certainly doesn't mean that there are no bugs in 7.8.352. Several bugs have been fixed in 7.8.700, some rather serious, and backporting would be risky according to the upstream developers that I'm talking to at the Pike conference right now. They would much appreciate if 7.8.700 could be included in wheezy. I'm asking them to test the current package in experimental. Thanks for your consideration. -- Magnus Holmgren Debian Developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668008: transition/unblock: uw-imap
user release.debian@packages.debian.org usertags - transition thanks I've uploaded uw-imap 8:2007f~dfsg-2 implementing Julien's suggestion. Please unblock it. uw-imap (8:2007f~dfsg-2) unstable; urgency=medium * New maintainer (Closes: #686448). * Disable unnecessarily strict version check (Closes: #682256). -- Magnus Holmgren holmg...@debian.org Thu, 25 Oct 2012 23:00:39 +0200 -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#668008: transition/unblock: uw-imap
On söndagen den 14 oktober 2012, you stated the following: On Mon, Sep 24, 2012 at 08:12:19 +0200, Magnus Holmgren wrote: Unfortunately, Jonas's decision to upload without an SONAME bump broke all packages that use libc-client (see bug #682256), due to an extra, internal (and in this case unnecessarily strict) version check that fails. The SONAME *shouldn't* have had to be changed as 2007f is merely a bugfix release, except for an attempt to also support AIX 5.2, but that's nothing that affects us. There are no ABI or API changes. See attached diff. How about the patch below? It might certainly be a good idea too disable that check permanently; it is rather redundant after all. diff -Nru uw-imap-2007f~dfsg/debian/changelog uw-imap-2007f~dfsg/debian/changelog --- uw-imap-2007f~dfsg/debian/changelog 2012-06-29 13:32:24.0 +0200 +++ uw-imap-2007f~dfsg/debian/changelog 2012-10-14 20:02:14.0 +0200 @@ -1,3 +1,10 @@ +uw-imap (8:2007f~dfsg-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Disable broken version check (closes: #682256) + + -- Julien Cristau jcris...@debian.org Sun, 14 Oct 2012 20:02:13 +0200 + -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#689544: unblock: lsh-utils/2.0.4-dfsg-11
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package lsh-utils This is merely a review of package descriptions and Debconf templates along with l10n updates. unblock lsh-utils/2.0.4-dfsg-11 -- Magnus Holmgren holmg...@debian.org Debian Developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686212: [BTS#686212] templates://lsh-utils/{lsh-server.templates,control}
On söndagen den 23 september 2012, you stated the following: Please let me know if you intend to fix this bug in Wheezy: if so, I'll shake a bit more the Spanish translators in order to make sure they provide an update, since it's one of the languages already (almost) 100 % complete, it would be a shame to brake its status while improving the English one. Dunno, you initiated the process and I'll be happy to finish it, even though it doesn't feel like the most urgent thing, as long as it's covered by the freeze exception policy, which it still is, right? Now the Spanish translation has been updated too. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#688607: unblock: libspf2/1.2.9-7
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: freeze-exception Please unblock package libspf2/1.2.9-7. It fixes RC bugs #687862, #687863 and #687864 (all concerning doc directories not properly replaced with symlinks), nothing else. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#668008: transition/unblock: uw-imap
On Fri, 29 Jun 2012 14:21:19 +0200 Jonas Smedegaard wrote:
On 12-04-28 at 03:40pm, Adam D. Barratt wrote:
On Sun, 2012-04-08 at 09:54 +0200, Jonas Smedegaard wrote:
I have prepared a new upstream release of uw-imap. It includes
libc-client which is requires recompilation of 5 other packages:
libmail-cclient-perl
mailsync
php5
prayer
asterisk
First three build-depend on the virtual libc-client-dev so should do
with a simple binNMU.
Should? Are there any API changes in the new libc-client which are
likely to affect those packages?
Actually it turned out there wasn't even a need for a SONAME bump.
I now released new uw-imap, and this transition is unneeded.
Unfortunately, Jonas's decision to upload without an SONAME bump broke all
packages that use libc-client (see bug #682256), due to an extra, internal
(and in this case unnecessarily strict) version check that fails.
The SONAME *shouldn't* have had to be changed as 2007f is merely a bugfix
release, except for an attempt to also support AIX 5.2, but that's nothing
that affects us. There are no ABI or API changes. See attached diff.
At this point we have to either go through with the transition (it's a small
one), cheat and set the internal version string back to 2007e, or bump the
epoch and really roll back to 2007e.
Meanwhile, the maintainer of mailsync fixed this problem by rebuilding and
adding a dependency on libc-client2007e (= 8:2007f~dfsg-1). It will therefore
be broken if we roll back to 2007e.
--
Magnus Holmgrenholmg...@debian.org
Debian Developer
From d083ad99d779eb6cf8cff6a9d1b6fca64742c33f Mon Sep 17 00:00:00 2001
From: Jonas Smedegaard d...@jones.dk
Date: Sat, 7 Apr 2012 20:05:22 +0200
Subject: [PATCH] Imported Upstream version 2007f~dfsg
---
Makefile |3 ++-
docs/RELNOTES | 11
src/c-client/mail.h |4 +--
src/imapd/imapd.c |4 +--
src/osdep/unix/Makefile |8 ++
src/osdep/unix/env_unix.c |4 +--
src/osdep/unix/os_a52.c | 63 +
src/osdep/unix/os_a52.h | 53 ++
src/osdep/unix/tcp_unix.c | 12 +
9 filer ändrade, 150 tillägg(+), 12 borttagningar(-)
create mode 100644 src/osdep/unix/os_a52.c
create mode 100644 src/osdep/unix/os_a52.h
diff --git a/Makefile b/Makefile
index e6e4987..5fcf1dd 100644
--- a/Makefile
+++ b/Makefile
@@ -37,6 +37,7 @@
# The following ports are bundled:
# a32 AIX 3.2 for RS/6000
# a41 AIX 4.1 for RS/6000
+# a52 Attempt at AIX 5.2
# aix AIX/370 (not RS/6000!!)
# ami AmigaDOS
# am2 AmigaDOS with a 68020+
@@ -306,7 +307,7 @@ SPECIALS:
# Note on SCO you may have to set LN to ln.
-a32 a41 aix bs3 bsi d-g d54 do4 drs epx ga4 gas gh9 ghp ghs go5 gsc gsg gso gul h11 hpp hpx lnp lyn mct mnt nec nto nxt nx3 osf os4 ptx qnx sc5 sco sgi sg6 shp sl4 sl5 slx snx soc sol sos uw2: an
+a32 a41 a52 aix bs3 bsi d-g d54 do4 drs epx ga4 gas gh9 ghp ghs go5 gsc gsg gso gul h11 hpp hpx lnp lyn mct mnt nec nto nxt nx3 osf os4 ptx qnx sc5 sco sgi sg6 shp sl4 sl5 slx snx soc sol sos uw2: an
$(BUILD) BUILDTYPE=$@
# If you use sv4, you may find that it works to move it to use the an process.
diff --git a/docs/RELNOTES b/docs/RELNOTES
index 5cfd913..db18b67 100644
--- a/docs/RELNOTES
+++ b/docs/RELNOTES
@@ -11,6 +11,17 @@
*
*/
+Updated: 22 July 2011
+
+imap-2007f fixes a couple bugs.
+Fix for RFC 4959 Initial Client Response auth failures noted first by
+ MacOSX Lion Mail users.
+Adjust tcp_open.c:tcp_socket_open to make it a little more useful by adding
+ a write file descriptor test to the select in the case that the open
+ timeout is set.
+In osdep/unix/env_unix.c:create_path there was a printf that should have
+ been an sprintf. Doesn't matter on modern systems.
+
Updated: 16 December 2008
imap-2007e is a maintenance release, consisting primarily of bugfixes to
diff --git a/src/c-client/mail.h b/src/c-client/mail.h
index 391561f..e90b92e 100644
--- a/src/c-client/mail.h
+++ b/src/c-client/mail.h
@@ -21,12 +21,12 @@
* Internet: m...@washington.edu
*
* Date: 22 November 1989
- * Last Edited: 16 December 2008
+ * Last Edited: 22 July 2011
*/
/* The Version */
-#define CCLIENTVERSION 2007e
+#define CCLIENTVERSION 2007f
/* Build parameters */
diff --git a/src/imapd/imapd.c b/src/imapd/imapd.c
index d3d1566..4045019 100644
--- a/src/imapd/imapd.c
+++ b/src/imapd/imapd.c
@@ -21,7 +21,7 @@
* Internet: m...@washington.edu
*
* Date: 5 November 1990
- * Last Edited: 3 March 2008
+ * Last Edited: 22 July 2011
*/
/* Parameter files */
@@ -2141,7 +2141,7 @@ unsigned char *snarf_base64 (unsigned char **arg)
/* must be at least one BASE64 char */
else if (!base64mask[*ret]) return NIL;
else { /* quick and dirty */
-while (base64mask[*s++]); /* scan until end
Bug#686212: [BTS#686212] templates://lsh-utils/{lsh-server.templates,control}
On fredagen den 7 september 2012, David Prévot wrote: Control: tags -1 patch Dear Debian maintainer, On Wednesday, August 29, 2012, I notified you of the beginning of a review process concerning debconf templates for jffnms. The debian-l10n-english contributors have now reviewed these templates, and the final proposed changes are attached to this update to the original bug report. Please review the suggested changes, and if you have any objections, let me know in the next 3 days. I just noticed that your final patch didn't uppercase sftp in _Description: Enable the sftp subsystem? as Justin suggested. I'll just go ahead and change that throughout, OK? Or is there a distinction between the sftp subsystem (as in /usr/lib/lsh- server/sftp-server) and the SFTP protocol? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#686448: ITA: uw-imap -- c-client library for mail protocols - development files
retitle 686448 ITA: uw-imap -- c-client library for mail protocols - development files thanks I could take this. I at least manage a package that depends on it. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#688027: prayer cannot connect to session server
On tisdagen den 18 september 2012, you stated the following: # prayer-session prayer PANICLOG: Failed to open panic log file: paniclog Error was: Sep 18 13:51:09 [6961] Fatal error: c-client library version skew, app=2007e library=2007f Aborted This appears to be a bug in the uw-imap source package. There are already several bugs filed against that package. I think Jonas forgot to change the libc-client package name last time. -- Magnus Holmgrenholmg...@debian.org Debian Developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626203: dpkg: handle better package upgrade replacing symlink by a folder
On måndagen den 9 maj 2011, you stated the following: Hi, Yves-Alexis Perez wrote: as said on irc, it'd be nice if dpkg could handle package upgrade involving symlinks and directories a bit more nicely. See also [1], [2], and [3]. The intent of the current behavior is that the sysadmin is free to use symlinks to cause files in one directory to appear on a different partition, and dpkg will leave that alone rather than replacing it with a directory. For symmetry, dpkg will not automatically replace a directory with a symlink, either. Better semantics, implemented in maintainer scripts for many packages, are: - after a directory changes to a symlink in the shipped package, change the directory on disk to a symlink, if it is a directory and is empty. If it is not empty, make a backup and then put a symlink there. After a package has been unpacked, dpkg doesn't actually know which files were originally directories or symlinks, so it can't currently implement these semantics internally. This symmetry argument doesn't strike me as very persuasive. The sysadmin may very well want to move a directory and put a symlink, pointing to the new location, in its place, but how often does one replace a symlink with a copy of the directory it points to? In the case that a package replaces a directory with a symlink, the package upgrade would normally leave us with an empty directory. I can't see how that could ever be considered the correct and desired result. Now, if there are unowned files or files from other packages in the directory it must of course not be removed - that's either something the sysadmin has to sort out, or an error. One technical problem seems to be that files which were in the old version of a package but not in the new are not removed until after the files in the new package have been unpacked (and after the point of no return; policy 6.6, step 5). dpkg will thus either have to determine ahead of that point what directories will disappear, or perform an extra step of replacing empty directories with symlinks. But in any case I don't think dpkg needs to know which files where previously directories but now should be symlinks. - before a symlink changes to a directory in the shipped package, check if there is a symlink to the shipped target there on disk. If so, remove the symlink and replace it with a directory. (If not, leave the symlink alone.) This opposite direction is clearly more complicated, but another sign that a symlink should be replaced with a separate directory is when otherwise files from different packages would overwrite each other. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#686212: Please allow translation of all debconf templates
On onsdagen den 29 augusti 2012, you stated the following: A small typo in one of the templates (missing prepending underscore) prevent one screen to be translated. That's intentional. I don't plan to present that template to the administrator at this time; It's just there so the EXTRA_ARGS variable in /etc/default/lsh- server can be preserved. Still, it may be worthwhile to translate it for future use. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#675773: libopenjpeg2: Please make libopenjpeg2 multi-arch: same
On lördagen den 16 juni 2012, Michael Gilbert wrote:
tag 675773 patch
thanks
Hi, I've uploaded an nmu fixing this issue to delayed/5. See attached
patch.
Here's a slightly less intrusive patch. Also, I think Michaels patch added
Multi-Arch: same to too many packages and added a dependency to openjpeg-
tools for no apparent reason. I too think it would be nice to have this fixed.
It's a relatively simple operation.
--
Magnus Holmgrenholmg...@debian.org
Debian Developer
diff -u openjpeg-1.3+dfsg/debian/openjpeg-tools.install openjpeg-1.3+dfsg/debian/openjpeg-tools.install
--- openjpeg-1.3+dfsg/debian/openjpeg-tools.install
+++ openjpeg-1.3+dfsg/debian/openjpeg-tools.install
@@ -1,4 +1 @@
-j2k_to_image /usr/bin/
-image_to_j2k /usr/bin/
-index_create /usr/bin/
-jp2-thumbnailer /usr/bin/
+usr/bin
diff -u openjpeg-1.3+dfsg/debian/rules openjpeg-1.3+dfsg/debian/rules
--- openjpeg-1.3+dfsg/debian/rules
+++ openjpeg-1.3+dfsg/debian/rules
@@ -4,6 +4,7 @@
# used as trailer in the generated manpages
UVERSION = $(shell dpkg-parsechangelog | perl -ne 'print $$1\n if (/^Version: (.*?)(?:\.dfsg)?\-.*?$$/)')
+DEB_HOST_MULTIARCH = $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
EXTRA_CFLAGS += -O0
@@ -59,12 +60,13 @@
dh_clean -k
dh_installdirs
- $(MAKE) dist
+ $(MAKE) install DESTDIR=dist INSTALL_LIBDIR='$$(PREFIX)/lib/$(DEB_HOST_MULTIARCH)'
# The libraries and header file are in dist/
# So we'll dump the binaries there too
- cp codec/j2k_to_image codec/image_to_j2k dist/
- cp indexer_JPIP/index_create dist/
- cp debian/jp2-thumbnailer dist/
+ install -d -m 755 dist/usr/bin
+ install -m 755 codec/j2k_to_image codec/image_to_j2k dist/usr/bin
+ install -m 755 indexer_JPIP/index_create dist/usr/bin
+ install -m 755 debian/jp2-thumbnailer dist/usr/bin
binary-indep: build install
# We have nothing to do by default.
diff -u openjpeg-1.3+dfsg/debian/libopenjpeg2.install openjpeg-1.3+dfsg/debian/libopenjpeg2.install
--- openjpeg-1.3+dfsg/debian/libopenjpeg2.install
+++ openjpeg-1.3+dfsg/debian/libopenjpeg2.install
@@ -1 +1 @@
-lib*.so* usr/lib/
+usr/lib/*/lib*.so*
diff -u openjpeg-1.3+dfsg/debian/libopenjpeg-dev.install openjpeg-1.3+dfsg/debian/libopenjpeg-dev.install
--- openjpeg-1.3+dfsg/debian/libopenjpeg-dev.install
+++ openjpeg-1.3+dfsg/debian/libopenjpeg-dev.install
@@ -1,2 +1,2 @@
-*.h usr/include/
-lib*.a usr/lib
+usr/include/
+usr/lib/*/lib*.a
diff -u openjpeg-1.3+dfsg/debian/control openjpeg-1.3+dfsg/debian/control
--- openjpeg-1.3+dfsg/debian/control
+++ openjpeg-1.3+dfsg/debian/control
@@ -23,6 +23,8 @@
Package: libopenjpeg2
Section: libs
Architecture: any
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}
Description: JPEG 2000 image compression/decompression library
Libopenjpeg2 is a library for handling the JPEG 2000 image compression format.
@@ -38,6 +40,8 @@
Package: openjpeg-tools
Section: graphics
+Multi-Arch: foreign
+Pre-Depends: ${misc:Pre-Depends}
Architecture: any
Depends: ${shlibs:Depends}
Description: command-line tools using the JPEG 2000 library
diff -u openjpeg-1.3+dfsg/debian/changelog openjpeg-1.3+dfsg/debian/changelog
signature.asc
Description: This is a digitally signed message part.
Bug#672833: aspell-sv: In Swedish aspell considers full stops to be part of words
On tisdagen den 26 juni 2012, Francois Gouget wrote: In French too full stops are used in abbreviations, such as in c.-à-d. for c'est-à-dire. http://fr.wikipedia.org/wiki/Abr%C3%A9viation#Typographie_et_abr.C3.A9viati ons Yet trailing full stops are never included in misspelt words. So the difference in behavior is still strange and confusing. That's because aspell-fr nevertheless specifies that full stops do not appear at the end of words. Maybe that's wrong, maybe it's right, maybe it's a good compromise. aspell could be smarter. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#678650: Please recognize doc-base section Network/Remote Access
Package: lintian Version: 2.5.8 Network/Remote Access is a valid doc-base section: `Network/Remote Access' Tools for remotely managing of computer -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#672833: aspell-sv: In Swedish aspell considers full stops to be part of words
On måndagen den 14 maj 2012, Francois Gouget wrote: Consider this: $ echo Invalid kombinationsrutemeddelande. swedish.txt $ aspell --lang sv check swedish.txt This will flag 'kombinationsrutemeddelande.' as being misspelt. Notice that this includes the full stop so that if alternatives are suggested (as is the case if one adds --run-together --run-together-limit=4), the full stop will be lost. Yes, sv.dat specifies that full stops can be part of words. That's probably because, in Swedish, full stops are used in abbreviations such as t.ex. and d.v.s., which should be spell checked as a unit. Unfortunately aspell then considers them part of any misspelled word as well. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#666634: pyscrabble: FTBFS: /bin/sh: 2: rsvg: not found
severity 34 wishlist retitle 34 Use rsvg-convert instead of rsvg to convert icons thanks On lördagen den 31 mars 2012, Lucas Nussbaum wrote: During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: for size in 16 22 32 48 64 96; do \ rsvg -h $size -w $size debian/pyscrabble.svg pyscrabble-$size.png; \ done /bin/sh: 2: rsvg: not found /bin/sh: 2: rsvg: not found /bin/sh: 2: rsvg: not found /bin/sh: 2: rsvg: not found /bin/sh: 2: rsvg: not found /bin/sh: 2: rsvg: not found make: *** [build-stamp] Error 127 That seems to be rsvg's fault (http://bugs.debian.org/666276), but I guess I should switch to rsvg-convert eventually. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#578563: Looking for a new sponsor for FriBID
On tisdagen den 11 oktober 2011, you stated the following: My prospective sponsor won't be able to sponsor for some time. If anyone else can offer sponsoring (or even review the packaging), please leave a message. I just sent an annoyed message to my bank support, but I guess I should just forget about the official BankID client and look into this instead at the earliest opportunity. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#657140: sa-exim: unowned files after purge (policy 6.8, 10.8)
On tisdagen den 24 januari 2012, you stated the following: during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): sa-exim uses Debconf to ask the administrator whether said files should be deleted or kept, but the default is to keep them, which is why they aren't purged under Piuparts. I have been considering changing the default to delete though. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#657116: libtar: FTBFS on hurd-i386
On tisdagen den 24 januari 2012, you stated the following: This patch solves the build problems for GNU/Hurd due to MAXPATHLEN issues. The solution is to make dynamic string allocations instead of using fixed length buffers. The functions mkdirhier, basename and dirname have all been checked with separate test programs on Linux and Hurd and with valgrind on Linux without problems. Furthermore, parts of the the code has been reviewed by GN/Hurd developers and Debian GNU/Hurd developers and maintainers. Thanks! I've been thinking of doing something about this myself but there were so many instances of MAXPATHLEN that I got tired before I got started. :-) Build and run tested on both Linux and Hurd without problems. Also heap and leak tested on Linux with valgrind. No heap errors, but still memory leaks (coming from the original code). Removing the memory leaks will need another deep investigation of the original code, which time does not permit right now. Leaks other than the ones in th_get_pathname()? Since there is no upstream, the wish is that the Debian Maintainer takes a look at this patch and checks if it can be applied. Test programs are available on request. This patch will affect all architectures, completely removing the MAXPATHLEN dependencies (except for a few unused compat functions). I'll have a look and forward it to the libtar mailing list. There actually is sort of an official unofficial upstream at http://repo.or.cz/w/libtar.git since a while back. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#657116: libtar: FTBFS on hurd-i386
On torsdagen den 26 januari 2012, Svante Signell wrote: On Thu, 2012-01-26 at 22:19 +0100, Magnus Holmgren wrote: I'll have a look and forward it to the libtar mailing list. There actually is sort of an official unofficial upstream at http://repo.or.cz/w/libtar.git since a while back. Good to know about this repo. Regarding mailing list the link https://lists.feep.net:8080/mailman/listinfo.cgi/libtar times out all the time for me. Is another mailing list used? No, that's the one AFAIK. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#648014: Too strict dependencies on binutils, maybe due to inappropriate dynamic linking with binutils libraries?
On onsdagen den 9 november 2011, Yaroslav Halchenko wrote: thanks for the update... not sure if I will be able to dig into it within upcoming week (traveling), so if you get a chance -- would be appreciated! No need, it built on the second try. On Wed, 09 Nov 2011, Magnus Holmgren wrote: On onsdagen den 9 november 2011, you stated the following: Thanks Magnus, was about to upload it myself but got distracted -- you were first -- you won ;) Crapfully enough the build failed on armel due to a SIGILL of all things, and I don't know if it's due to randomness, a bug in the new version of binutils, or the static linkage. On Wed, 09 Nov 2011, Magnus Holmgren wrote: On tisdagen den 8 november 2011, Yaroslav Halchenko wrote: if you are a DD -- just proceed with NMU fixing this issue... I have no time atm for lush One NMU coming up, as follows: -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#644808: limit source to ssvnc, tagging 644808
On torsdagen den 10 november 2011, you stated the following: tags 644808 - pending thanks Le dimanche, 9 octobre 2011 22.49:33, Magnus a écrit : #ssvnc (1.0.29-1) unstable; urgency=low # # * Simply build-depend on libjpeg-dev instead of libjpeg62-dev | #libjpeg-dev (Closes: #644808). # limit source ssvnc tags 644808 + pending thanks Hi Magnus, it's been one month since you prepared this upload which you tagged pending (automatically I guess). Where did this upload go? Cheers, Sorry, it got stuck behind an attempt to make debian/rules use dpkg- buildflags, which was a bit tricky since the package uses imake. I'll upload in a jiffy. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#648014: Too strict dependencies on binutils, maybe due to inappropriate dynamic linking with binutils libraries?
On tisdagen den 8 november 2011, Yaroslav Halchenko wrote:
if you are a DD -- just proceed with NMU fixing this issue... I have no
time atm for lush
One NMU coming up, as follows:
diff -Nru lush-1.2.1/debian/changelog lush-1.2.1/debian/changelog
--- lush-1.2.1/debian/changelog 2011-02-27 22:13:03.0 +0100
+++ lush-1.2.1/debian/changelog 2011-11-08 22:22:44.0 +0100
@@ -1,3 +1,12 @@
+lush (1.2.1-9+cvs20110227+nmu1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/patches/05-static-libbfd-needs-lz: Make linking statically
+against libbfd work by appending -lz, which libbfd needs (Closes:
+#648014). Thanks to Niels Möller.
+
+ -- Magnus Holmgren holmg...@debian.org Tue, 08 Nov 2011 22:18:13 +0100
+
lush (1.2.1-9+cvs20110227) unstable; urgency=low
* Upload to unstable
diff -Nru lush-1.2.1/debian/control lush-1.2.1/debian/control
--- lush-1.2.1/debian/control 2011-02-27 22:13:03.0 +0100
+++ lush-1.2.1/debian/control 2011-11-08 23:14:15.0 +0100
@@ -2,7 +2,7 @@
Section: devel
Priority: extra
Maintainer: Yaroslav Halchenko deb...@onerussian.com
-Build-Depends: debhelper (= 7.0.50~), autotools-dev, binutils-dev, libxt-dev,
libxft-dev, gfortran, indent, pkg-config, libncurses-dev, libreadline-dev,
libgsl0-dev, liblapack-dev,
libgl1-mesa-dev | libgl-dev, libsdl-dev, libcv-dev, libasound2-dev,
libaudiofile-dev
+Build-Depends: debhelper (= 7.0.50~), autotools-dev, binutils-dev, libxt-dev,
libxft-dev, gfortran, indent, pkg-config, libncurses-dev, libreadline-dev,
libgsl0-dev, liblapack-dev,
libgl1-mesa-dev | libgl-dev, libsdl-dev, libcv-dev, libasound2-dev,
libaudiofile-dev, zlib1g-dev
Standards-Version: 3.9.1
Homepage: http://lush.sourceforge.net/
Vcs-Browser: http://git.onerussian.com/?p=deb/lush.git
diff -Nru lush-1.2.1/debian/patches/05-static-libbfd-needs-lz
lush-1.2.1/debian/patches/05-static-libbfd-needs-lz
--- lush-1.2.1/debian/patches/05-static-libbfd-needs-lz 1970-01-01
01:00:00.0 +0100
+++ lush-1.2.1/debian/patches/05-static-libbfd-needs-lz 2011-11-08
22:14:30.0 +0100
@@ -0,0 +1,26 @@
+From: Niels Möller ni...@lysator.liu.se
+Subject: When linking statically against libbfd we need to link against libz
as well.
+Bug-Debian: http://bugs.debian.org/648014
+
+--- a/configure
b/configure
+@@ -5895,7 +5895,7 @@ else
+ fi
+
+ i_LIBS=`echo $n_LIBS | sed -e 's/-liberty/ -lintl/'`
+-sn_LIBS=`echo $n_LIBS | sed -e 's/-lbfd\( -liberty\)*/-Wl,-Bstatic
-Wl,-Bdynamic/'`
++sn_LIBS=`echo $n_LIBS | sed -e 's/-lbfd\( -liberty\)*/-Wl,-Bstatic
-Wl,-Bdynamic -lz/'`
+ si_LIBS=`echo $i_LIBS | sed -e 's/-lbfd\( -liberty\)*/-Wl,-Bstatic
-Wl,-Bdynamic/'`
+ LIBS=$sn_LIBS
+ { echo $as_me:$LINENO: checking whether bfd works with -Bstatic 5
+--- a/configure.ac
b/configure.ac
+@@ -151,7 +151,7 @@ if test x$has_bfd = xyes ; then
+ has_intl=
+ AC_CHECK_LIB(intl, dcgettext, [has_intl=yes],[has_intl=no])
+ i_LIBS=`echo $n_LIBS | sed -e 's/-liberty/ -lintl/'`
+-sn_LIBS=`echo $n_LIBS | sed -e 's/-lbfd\( -liberty\)*/-Wl,-Bstatic
-Wl,-Bdynamic/'`
++sn_LIBS=`echo $n_LIBS | sed -e 's/-lbfd\( -liberty\)*/-Wl,-Bstatic
-Wl,-Bdynamic -lz/'`
+ si_LIBS=`echo $i_LIBS | sed -e 's/-lbfd\( -liberty\)*/-Wl,-Bstatic
-Wl,-Bdynamic/'`
+ LIBS=$sn_LIBS
+ AC_MSG_CHECKING([whether bfd works with -Bstatic])
diff -Nru lush-1.2.1/debian/patches/series lush-1.2.1/debian/patches/series
--- lush-1.2.1/debian/patches/series2011-02-27 22:13:03.0 +0100
+++ lush-1.2.1/debian/patches/series2011-11-08 22:17:44.0 +0100
@@ -3,3 +3,4 @@
02-manpage
03-gcc4-mips
04-ld-no-add-needed
+05-static-libbfd-needs-lz
--
Magnus Holmgrenholmg...@debian.org
Debian Developer
diff -Nru lush-1.2.1/debian/changelog lush-1.2.1/debian/changelog
--- lush-1.2.1/debian/changelog 2011-02-27 22:13:03.0 +0100
+++ lush-1.2.1/debian/changelog 2011-11-08 22:22:44.0 +0100
@@ -1,3 +1,12 @@
+lush (1.2.1-9+cvs20110227+nmu1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * debian/patches/05-static-libbfd-needs-lz: Make linking statically
+against libbfd work by appending -lz, which libbfd needs (Closes:
+#648014). Thanks to Niels Möller.
+
+ -- Magnus Holmgren holmg...@debian.org Tue, 08 Nov 2011 22:18:13 +0100
+
lush (1.2.1-9+cvs20110227) unstable; urgency=low
* Upload to unstable
diff -Nru lush-1.2.1/debian/control lush-1.2.1/debian/control
--- lush-1.2.1/debian/control 2011-02-27 22:13:03.0 +0100
+++ lush-1.2.1/debian/control 2011-11-08 23:14:15.0 +0100
@@ -2,7 +2,7 @@
Section: devel
Priority: extra
Maintainer: Yaroslav Halchenko deb...@onerussian.com
-Build-Depends: debhelper (= 7.0.50~), autotools-dev, binutils-dev, libxt-dev, libxft-dev, gfortran, indent, pkg-config, libncurses-dev, libreadline-dev, libgsl0-dev, liblapack-dev, libgl1-mesa-dev | libgl-dev, libsdl-dev, libcv-dev, libasound2-dev, libaudiofile-dev
+Build-Depends: debhelper
Bug#648014: Too strict dependencies on binutils, maybe due to inappropriate dynamic linking with binutils libraries?
On onsdagen den 9 november 2011, you stated the following: Thanks Magnus, was about to upload it myself but got distracted -- you were first -- you won ;) Crapfully enough the build failed on armel due to a SIGILL of all things, and I don't know if it's due to randomness, a bug in the new version of binutils, or the static linkage. On Wed, 09 Nov 2011, Magnus Holmgren wrote: On tisdagen den 8 november 2011, Yaroslav Halchenko wrote: if you are a DD -- just proceed with NMU fixing this issue... I have no time atm for lush One NMU coming up, as follows: -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#629233: ssvnc: Depend on x-terminal-emulator
On lördagen den 15 oktober 2011, Karl J. Runge wrote: But is it necessary to create wrapper scripts on the fly (in a manner that I'm not entirely sure is secure) and execute those? I guess to remove the xterm dependency there would be a debian patch that modifies the wrapper(s) to set SSVNC_XTERM_REPLACEMENT=x-terminal-emulator if it wasn't already externally set by the user. Hmmm, without looking at the scripts I'm not sure how that would interact with a ~/.ssvncrc setting though, but that would be easy to test. That alone wouldn't work, would it? The wrapper scripts are only run if SSVNC_XTERM_REPLACEMENT isn't set in the first place. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#629233: ssvnc: Depend on x-terminal-emulator
On lördagen den 4 juni 2011, Torquil Macdonald Sørensen wrote: If possible, please depend on x-terminal-emulator instead of xterm, so I can uninstalling the latter while keeping ssvnc. I use mrxvt, and have no direct need for xterm. Does ssvnc really need xterm exactly? Yes and no, I suppose. Debian policy only states three requirements for x- terminal-emulator providers: being able to emulate a VT100 terminal, supporting the -e option, and supporting the -T option. ssvnc uses additional options and X resources that other x-terminal-emulator providers don't understand, but I'm not sure how important those are. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#629233: ssvnc: Depend on x-terminal-emulator
On fredagen den 10 juni 2011, Karl J. Runge wrote: As an aside (i.e. independent of a distro's dependencies), the environment variable SSVNC_XTERM_REPLACEMENT can be set to a different terminal emulator (one can also set this variable in ~/.ssvncrc) See Help - Tip 15 for more info. But is it necessary to create wrapper scripts on the fly (in a manner that I'm not entirely sure is secure) and execute those? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#563492: Debian-exim can't write to /var/spool/sa-exim/tuplets
On Sunday, 3 January 2010, Andrew Archibald wrote: Greylisting in the latest stable sa-exim doesn't appear to work with the default permissions on the tuplets directory left by a d-i fresh install, using the 'Mail server' software collection option. # ls -ld /var/spool/sa-exim/tuplets/ drwxr-x--- 2 nobody Debian-exim 4096 2009-12-17 11:20 /var/spool/sa-exim/tuplets/ It seems that reconfiguring, as below, tidies up the perms. # dpkg-reconfigure sa-exim Reloading exim4 configuration files: exim4. # ls -ld /var/spool/sa-exim/tuplets drwxrwx--x 2 nobody Debian-exim 4096 2009-12-17 11:20 /var/spool/sa-exim/tuplets Yes, that the permissions where set differently the first time than on subsequent invokations was a bug. The default of running the greylistclean as nobody also surprised me. With Debian-exim writing to the tuplets dir, nobody didn't have enough access: nobody@myhost:/$ /usr/share/sa-exim/greylistclean Can't cd to (/var/spool/sa-exim/tuplets/) 92: Permission denied at /usr/share/sa-exim/greylistclean line 79 Well, the default setup relies on you running spamd as nobody, as described in README.greylisting. That is, however, not really a great idea - nobody shouldn't own any files IIUC - so I'll change the package to work with the default setup of spamd and add more information to the README files. I'll try to make it so that existing installations won't be broken... -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#640278: heimdal-dev: Symlinks broken after multi-arch conversion
On torsdagen den 8 september 2011, Matthias Klose wrote: No, the symlinks are not broken. Maybe you do maintain a package with broken or explicit checks for locations of libraries? The symlinks are fine in the unstable/testing version (1.4.0-8), because there they're created by hand in debian/rules, but they are indeed broken in the experimental version: $ ls -l /usr/lib/libkrb5.so /usr/lib/libasn1.so lrwxrwxrwx 1 root root 18 14 aug 04.30 /usr/lib/libasn1.so - heimdal/libasn1.so lrwxrwxrwx 1 root root 18 14 aug 04.29 /usr/lib/libkrb5.so - heimdal/libkrb5.so $ ls -l /usr/lib/heimdal ls: cannot access /usr/lib/heimdal: No such file or directory As I wrote elsewhere, using krb5-config --libs (or pkg-config) avoids the problem, but then maybe these symlinks should be dropped altogether? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#634294: nettle-dev: please support pkg-config
Sorry, I didn't realise this was an old bug report and that I had forgotten to include it in debian/changelog. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#640278: heimdal-dev: Symlinks broken after multi-arch conversion
Package: heimdal-dev Version: 1.5~pre2+git20110729-2 Severity: serious The symlinks listed in debian/heimdal-dev.links were left behind in /usr/lib and are thus broken. They should be moved to /usr/lib/$DEB_HOST_MULTIARCH somehow, or possibly at least point to targets in /usr/lib/$DEB_HOST_MULTIARCH/heimdal. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#633574: ANNOUNCE: Nettle-2.2
On torsdagen den 14 juli 2011, Simon Josefsson wrote: Magnus Holmgren holmg...@debian.org writes: On måndagen den 11 juli 2011, you stated the following: Package: nettle Severity: wishlist Hi! Version 2.2 has been released, and is now completely licensed under LGPLv2+. Could you package it? Btw, if you need any help with packaging, I'd be happy to work on it and provide patches to bring it up to 2.2 There shouldn't be too much to do, I think, apart from making a symbols file. Anything else important you can think of? Yes, the copyrights file needs to be updated to reflect the license change. Right. Making the package multiarch friendly would be another nice idea (GnuTLS packages are already converted), but I haven't done that yet myself so I'm just as good as anyone to help with that part. I was planning to do that as well. Are the debian files stored in version controlled sources anywhere? If things are still working, the Vcs fields in debian/control should be correct. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#633574: ANNOUNCE: Nettle-2.2
On måndagen den 11 juli 2011, you stated the following: Package: nettle Severity: wishlist Hi! Version 2.2 has been released, and is now completely licensed under LGPLv2+. Could you package it? Btw, if you need any help with packaging, I'd be happy to work on it and provide patches to bring it up to 2.2 There shouldn't be too much to do, I think, apart from making a symbols file. Anything else important you can think of? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#545139: fixed in akonadi 1.3.1-4
On tisdagen den 7 juni 2011, Ansgar Burchardt wrote: Modestas Vainius mo...@debian.org writes: Akonadi is supposed to create a socket in /tmp only if it can't do that in $HOME. No, with the patch akonadi will always create the socket in /tmp and only place a symlink in $HOME (unless SocketDirectory is set in the configuration). This means that new processes will not be able to connect to the old socket after an upgrade; it should work correctly once the database process is restarted. I did not bother with caring about the upgrade case when I wrote the initial patch, but for a stable update we might want to look for an already existing socket in the old location first. Well, I didn't notice any problem until after I rebooted my computer, which is why I'm confused. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#545139: fixed in akonadi 1.3.1-4
On lördagen den 30 april 2011, you stated the following: Changes: akonadi (1.3.1-4) unstable; urgency=low . * Add patch 04_socket_location.diff to allow akonadi-server to run when HOME is mounted to the network filesystem (Closes: #545139). Thanks to Ansgar Burchardt for the patch. After upgrading to that version, kmail stopped working because it (or rather libakonadi-kde4, or libakonadiprivate1?) still tries to use the old socket path. What have I missed regarding how clients find the socket? (No socket path is defined in ~/.config/akonadi/akonadiserverrc, so the new default is used.) -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#624489: RM: pike7.6/experimental -- RoM; obsolete version
Package: ftp.debian.org Severity: normal Like http://bugs.debian.org/618963 -- please remove pike7.6 from experimental too. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#611833: pyscrabble-server: doesn't start, fails to lock a file
severity 611833 minor thanks On torsdagen den 3 februari 2011, Nobuhiro Iwamatsu wrote: You do not start directly, and it is necessary to start with init.d, because pyscrabble-server is a daemon program. However, it is not preferable to be finished by an error. The program had better check uid and gid, I think. And it is not written in README.Debian about the start method of daemon. I think that I had better write these. README.Debian indeed states that the PyScrabble server is installed as a system daemon and that it's modified to read and write /etc/pyscrabble and /var/*/pyscrabble. Although it doesn't say exactly that you shouldn't run it from the command line, I think that follows more or less directly from the aforementioned points, but I'll add a clarification anyway. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#566666: pyscrabble: Can't register new users
On Sunday, 24 january 2010, Nigel Horne wrote: When attempting to register a user I get an error and the user isn't added. Traceback (most recent call last): File /usr/lib/python2.5/site-packages/pyscrabble/gui/register.py, line 283, in createNewUser_cb val,msg = s.createNewUser(uname, util.hashPassword(pw1)) File /usr/lib/python2.5/xmlrpclib.py, line 1147, in __call__ return self.__send(self.__name, args) File /usr/lib/python2.5/xmlrpclib.py, line 1437, in __request verbose=self.__verbose File /usr/lib/python2.5/xmlrpclib.py, line 1191, in request headers xmlrpclib.ProtocolError: ProtocolError for gateway.bandsman.co.uk:/xmlrpc: -1 Okay, this is of course way too late, but it would appear that you've mixed up the game and web ports and entered for the web port. The default server configuration is for the game port and for the web port. It's certainly not easy to know that, though. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#620809: lsh-server update overwrites /etc/default/lsh-server
On måndagen den 4 april 2011, you stated the following: after upgrade of lsh-server the file /etc/default/lsh-server gets overwritten, i.e. stuff like port and interface specifications and other commandline parameters. if lshd runs on a port other than 22 there will be no possibility to login after an upgrade (because there will likely be a firewall), if it should not listen on all interfaces it will etc... please don't do that! (it has alrady happened the last three times) Apparently my predecessor(s) intended for /etc/default/lsh-server to be editable, but didn't get that to work well together with debconf, so at the moment you have to use dpkg-reconfigure to make the configuration stick, despite what the comment in the file says. Thanks for letting me know; I hadn't thought about that. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#619191: nmu: nettle transition
On måndagen den 21 mars 2011, Julien Cristau wrote: On Mon, Mar 21, 2011 at 22:51:56 +0100, Magnus Holmgren wrote: A recent new version of nettle was recently updated, introducing some API and ABI changes. nettle doesn't have many rdepends, but these exist (and require no source changes): nmu chiark-utils_4.1.28+nmu2 . ALL . -m Rebuild against nettle 2.1 (libnettle4) nmu chiark-tcl_1.1.0+nmu2 . ALL . -m Rebuild against nettle 2.1 (libnettle4) nmu rdup_1.0.5-1 . ALL . -m Rebuild against nettle 2.1 (libnettle4) Scheduled. Note that xorg-server also uses libnettle.a (for the debian installer), hopefully that doesn't need source changes either. What about the other reverse dependencies? - lsh-utils Already uploaded. - pike7.6 Filed for removal, http://bugs.debian.org/618963. - rdfind Oops, missed that one, so nmu rdfind_1.2.4-2 . ALL . -m Rebuild against nettle 2.1 (libnettle4) -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#619191: nmu: nettle transition
Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: normal A recent new version of nettle was recently updated, introducing some API and ABI changes. nettle doesn't have many rdepends, but these exist (and require no source changes): nmu chiark-utils_4.1.28+nmu2 . ALL . -m Rebuild against nettle 2.1 (libnettle4) nmu chiark-tcl_1.1.0+nmu2 . ALL . -m Rebuild against nettle 2.1 (libnettle4) nmu rdup_1.0.5-1 . ALL . -m Rebuild against nettle 2.1 (libnettle4) -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#602910: pike7.8-dev: modules/Image/image.h not in /usr/include/pike7.8
On tisdagen den 9 november 2010, Marc Dirix wrote: Package: pike7.8-dev Version: 7.8.352-dfsg-3 Severity: minor When compiling an external module which depends on the Image module with pike -x module it fails, because the header file modules/Image/image.h is not installed. I do wonder what kind of module that is, but I guess that if you write a module in C that uses some other module that's also written in C you need some header file(s). Are there other modules in the main tree whose headers should be included in pike7.8-dev, and how can I tell? I suppose such header files should be installed under /usr/include/pike7.8. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#618963: RM: pike7.6 -- RoM; obsolete version
Package: ftp.debian.org Severity: normal Just like Python, multiple versions of Pike are maintained in parallel. Version 7.6 has been obsolete for several years now and should be dropped for wheezy. A pike-defaults package is planned, but for now there is no upgrade path, nor is one really needed, though /usr/bin/pike is controlled by the alternatives system. There are no Debian packages containing Pike code and users who have written their own scripts will have to check them for compatibility themselves. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#607559: Fix FTBFS with ld --as-needed
On söndagen den 19 december 2010, you stated the following: Adding libraries to LDFLAGS instead of LIBS is always a bad idea. Indeed. You mean that if --as-needed is added to LDFLAGS when building the package (have you begun letting dpkg-buildpackage do that by default on Ubuntu, perhaps?), -ldl ends up too early on the command lines when linking, so all its symbols are dropped as they aren't needed yet? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#607261: prayer: fails to start if no IPv6 Routers present
On torsdagen den 16 december 2010, you stated the following: after installing a new debian squeeze system, prayer fails to start with [...] Error was: [os_bind_inet_socket()] bind() failed: Address already in use Aborted a deep inspection shows that the problem is that no IPv6 Routers are (in my environment) present. Actually, the bug is that Prayer tries to bind IPv4 and IPv6 sockets separately without setting the IPV6_V6ONLY flag. That fails because when the sysctl net.ipv6.bindv6only is set to 0 (after a long debate, the default value on Debian), IPv6 sockets listening on [::] will also handle IPv4 packets (with the remote address looking like :::1.2.3.4). So the problem occurs on dual-stack systems whether IPv6 actually works or not, but not on systems without any IPv6 support at all. But thanks for reporting anyway. I should have noticed it myself but for some reason never really tried starting Prayer with net.ipv6.bindv6only=0. To work around the problem one can set net.ipv6.bindv6only=1 in /etc/sysctl.conf (will affect all software on the system) or set use_http_port to 0.0.0.0:port or :::port as you suggest. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#607305: Unblock request: prayer/1.3.3-dfsg1-3 (Re: Bug#607261)
Package: release.debian.org Please consider unblocking prayer/1.3.3-dfsg1-3. It merely adds a patch setting the IPV6_V6ONLY socket option. * ipv6_v6only.patch (new): Set the IPV6_V6ONLY socket option on AF_INET6 sockets; since Prayer by default enumerates available address families and calls bind() once for each, conflicts will occur otherwise. On torsdagen den 16 december 2010, Magnus Holmgren wrote: Actually, the bug is that Prayer tries to bind IPv4 and IPv6 sockets separately without setting the IPV6_V6ONLY flag. That fails because when the sysctl net.ipv6.bindv6only is set to 0 (after a long debate, the default value on Debian), IPv6 sockets listening on [::] will also handle IPv4 packets (with the remote address looking like :::1.2.3.4). So the problem occurs on dual-stack systems whether IPv6 actually works or not, but not on systems without any IPv6 support at all. But thanks for reporting anyway. I should have noticed it myself but for some reason never really tried starting Prayer with net.ipv6.bindv6only=0. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#607222: /usr/sbin/prayer: wrong permission of /var/log/prayer
severity 607222 normal thanks On onsdagen den 15 december 2010, you stated the following: The prayer package in squeeze installs /var/log/prayer with group-owner adm The Config File prayer.cf sets as default the group of prayer to nogroup. So if you start prayer with check_directory_perms = TRUE, you will get an Error: Starting webmail server: prayerprayer PANICLOG: Failed to open panic log file: paniclog Error was: Dec 15 20:25:25 [1785] /var/log/prayer directory must be owned by user prayer, group nogroup and not accessible by othe0rs failed! Solution: install /var/log/prayer with group-owner nogroup The idea is that nobody and nogroup should be completely unprivileged, and hence should not own _anything_. Many log files belong to group adm. check_directory_perms is probably a bit too picky as it doesn't even accept group root. I probably should just arrange for a group prayer to be created and the directories assigned to it, and if you want to set check_directory_perms=TRUE you should probably do that too for now. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#604224: pike7.8-dev: installation fails
On söndagen den 28 november 2010, gregor herrmann wrote: On Sun, 21 Nov 2010 10:58:10 +0100, Lucas Nussbaum wrote: While testing the installation of all packages in unstable, I ran into the following problem: I can reproduce your other fails-to-install bug reports in my cowbuilder chroot but not this one. The package installs just fine for me. I found an interesting line in the log: Setting up pike7.8-core (7.8.352-dfsg-3) ... update-alternatives: using /usr/bin/pike7.8 to provide /usr/bin/pike (pike) in auto mode. Alarm clock dpkg: error processing pike7.8-core (--configure): subprocess installed post-installation script returned error exit status 142 I've never seen this Alarm clock - any idea where this is coming from? Looks like what the shell would print if a child is terminated by SIGALRM (exit code 142 = 128+14), but I don't know why that happens. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#595372: soundkonverter crashin everytime when adding files
On fredagen den 3 september 2010, qmor wrote: soundkonverter crashing everytime when i'm trying to add some mp3 files to convert. I was able to reproduce this. It appears that for some reason the Use Plugin dropdown list is initially empty when ogg vorbis is the default output format is ogg vorbis (or when Last used is default and ogg vorbis was the last used format). Switching to e.g. mp3 and then back to ogg vorbis, or setting the default to mp3 and switching to ogg every time, works around the bug. at /home/magnus/src/soundkonverter/soundkonverter-0.9.91/filelist.cpp:948 948 QDomElement conversionOptions = config-conversionOptionsManager()-getConversionOptions(ids.at(i))-toXml(list); (gdb) bt #0 0x0045b977 in FileList::save (this=0xa13de0, user=value optimized out) at /home/magnus/src/soundkonverter/soundkonverter-0.9.91/filelist.cpp:948 #1 0x0044e07a in soundKonverterView::showFileDialog (this=0xa11250) at /home/magnus/src/soundkonverter/soundkonverter-0.9.91/soundkonverterview.cpp:185 #2 0x00450560 in soundKonverterView::qt_metacall (this=0xa11250, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffc9f0) at /home/magnus/src/soundkonverter/soundkonverter-0.9.91/obj-x86_64-linux-gnu/soundkonverterview.moc:118 #3 0x7580e306 in QMetaObject::activate (sender=0xa9f5d0, m=value optimized out, local_signal_index=value optimized out, argv=0x2) at kernel/qobject.cpp:3295 ... When trying to add CD tracks Soundkonverter crashes under the same conditions before any format selection can be made. options-currentConversionOptions() returns NULL here: 0x00431e25 in CDOpener::proceedClicked (this=0xc2dbd0) at /home/magnus/src/soundkonverter/soundkonverter-0.9.91/opener/cdopener.cpp:1043 1043if( options-currentConversionOptions()-outputDirectoryMode == OutputDirectory::Source ) (gdb) bt #0 0x00431e25 in CDOpener::proceedClicked (this=0xc2dbd0) at /home/magnus/src/soundkonverter/soundkonverter-0.9.91/opener/cdopener.cpp:1043 #1 0x0041acd7 in CDOpener::qt_metacall (this=0xc2dbd0, _c=QMetaObject::InvokeMetaMethod, _id=-176040447, _a=0x7fffb1f0) at /home/magnus/src/soundkonverter/soundkonverter-0.9.91/obj-x86_64-linux-gnu/moc_cdopener.cpp:134 #2 0x7580e306 in QMetaObject::activate (sender=0xc32520, m=value optimized out, local_signal_index=value optimized out, argv=0xfff79d18) at kernel/qobject.cpp:3295 ... -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#596363: Verifier fails to handle lines ending in \0x0a without \0x0d, (line-feed without CR) .
On fredagen den 10 september 2010, you stated the following: After that I edited the copy of the perl script file-- I commented out '$dkim-load(*STDIN);' I added a line 's/\012$//;' immediately before 's/\015$//;' . Ah, but the second change didn't actually do anything; it was the first change alone that made the script work. The example in the manpage says to use either $dkim-load(*STDIN) *or* $dkim-PRINT for each line, but the methods are not equivalent since the load routine requires CRLF line endings, as the manpage also tells you (or rather, both load and PRINT require CRLF endings, but the example code adds them in the latter case). Still, the documentation could perhaps be a little bit clearer. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#596363: Verifier fails to handle lines ending in \0x0a without \0x0d, (line-feed without CR) .
On fredagen den 10 september 2010, you stated the following: When I tried to use libmail-dkim-perl to verify a signature, authorised by the domain gmail.com (selector gamma), the result obtained was that the Verifier failed to detect any headers. Could you please post an example of such a DKIM-signed mail that demonstrates the bug? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#595700: dkimproxy: init script fails if package is removed but not purged
Package: dkimproxy
Severity: important
Version: 1.2-6
/etc/init.d/dkimproxy should check if /usr/sbin/dkimproxy.{in,out} still
exists and exit silently otherwise. See Policy § 9.3.2 (the paragraph
beginning These scripts should not fail obscurely ...).
--
Magnus Holmgrenholmg...@debian.org
Debian Developer
signature.asc
Description: This is a digitally signed message part.
Bug#592873: ssvnc: Connection from UVNC Single-Click does not start vncviewer
On onsdagen den 25 augusti 2010, you stated the following:
Hello,
The recently released upstream version 1.0.28 of SSVNC should fix this bug:
It's just this patch, right?
--- ssvnc-1.0.27/vnc_unixsrc/vncviewer/rfbproto.c 2010-04-18
04:34:38.0 +0200
+++ ssvnc-1.0.28/vnc_unixsrc/vncviewer/rfbproto.c 2010-06-04
03:20:39.0 +0200
@@ -854,7 +854,9 @@
switch (secType) {
case rfbSecTypeNone:
fprintf(stderr, No VNC authentication needed\n);
- if (viewer_minor = 8) {
+ if (accept_uvnc) {
+ ; /* we pretended 3.16 etc. */
+ } else if (viewer_minor = 8) {
CARD32 authResult;
if (!ReadFromRFBServer((char *)authResult, 4))
{
--
Magnus Holmgrenholmg...@debian.org
Debian Developer
signature.asc
Description: This is a digitally signed message part.
Bug#594386: nettle: new upstream version 2.1 is available
On onsdagen den 25 augusti 2010, you stated the following: Upstream released nettle version 2.1 at the end of July: http://lists.lysator.liu.se/pipermail/nettle-bugs/2010/002040.html This adds support for other members of the SHA-2 family of digest algorithms, and the Camellia block cipher. It appears to include an soname bump, fwiw, due to API changes. I will package it before too long, but it'll hardly be in squeeze. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#591595: fixed in comixcursors 0.6.1-3
On onsdagen den 25 augusti 2010, Ben Finney wrote: On 22-Aug-2010, Magnus Holmgren wrote: On tisdagen den 17 augusti 2010, Ben Finney wrote: * debian/preinst: + Handle the case where no cursor themes are yet installed (Closes: Bug#591595). However, it was clearly postinst that failed. I am unable to reproduce this behaviour with ‘comixcursors’ 0.6.1-3. What have you done to confirm that the bug still occurs after this change? In a sid chroot: # aptitude install comixcursors The following NEW packages will be installed: comixcursors 0 packages upgraded, 1 newly installed, 0 to remove and 2 not upgraded. Need to get 0B/4639kB of archives. After unpacking 51.3MB will be used. Selecting previously deselected package comixcursors. (Reading database ... 12905 files and directories currently installed.) Unpacking comixcursors (from .../comixcursors_0.6.1-3_all.deb) ... Setting up comixcursors (0.6.1-3) ... update-alternatives: error: no alternatives for x-cursor-theme. update-alternatives: using /etc/X11/cursors/ComixCursors-Black-Small.theme to provide /usr/share/icons/default/index.theme (x-cursor-theme) in auto mode. update-alternatives: error: unable to make /usr/share/icons/default/index.theme.dpkg-tmp a symlink to /etc/alternatives/x-cursor-theme: No such file or directory dpkg: error processing comixcursors (--configure): -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#593890: Share bug 499344: Wrong cursor when oxygencursors are installed
On söndagen den 22 augusti 2010, Ben Finney wrote: On 22-Aug-2010, Ben Finney wrote: Can you please improve these reports by showing what you think is missing in each of the packages. Also, if I might ask further: can you please show your source for the cursor name associations you are requesting. Probably something in the Qt docs? http://doc.trolltech.com/4.6/qcursor.html#a-note-for-x11-users -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#591595: fixed in comixcursors 0.6.1-3
On söndagen den 22 augusti 2010, Ben Finney wrote: On 22-Aug-2010, Magnus Holmgren wrote: On tisdagen den 17 augusti 2010, Ben Finney wrote: * debian/preinst: + Handle the case where no cursor themes are yet installed (Closes: Bug#591595). However, it was clearly postinst that failed. What you need to do is ship an empty /usr/share/icons/default directory. Crystalcursors had the same bug not once but twice: 363059 and 582517. Do I understand you correctly that *every* cursor theme package needs to ship the same empty directory? That this is cause to make a lintian override for every such empty directory? Why? I've just recently begun looking into cursor packages, but as I understand it, that's how things stand currently. Strangely enough, lintian doesn't complain about the empty directory in crystalcursors. I haven't figured out why yet. Why is it not, rather, a directory provided by some single, common package? I don't think there is actually any suitable package to hold it. Cursor themes are handled on the client side of X, so x11-common and other server-side packages are out. I also don't think it's a good idea to put it libxcursor or any other client library package. I think that what it would come down to is a cursor-themes-common package that would contain nothing but that empty directory, and that's hardly worth it. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#548804: crystalcursors: the corner resize cursors are swapped
reassign 548804 kdebase-workspace forwarded 548804 https://bugs.kde.org/248599 tags 548804 + upstream patch thanks On söndagen den 8 augusti 2010, Magnus Holmgren wrote: Basically all the cursor packages except oxygencursors display the same bug. It appears that it has to do with the hash symlinks fcf1c3c7cd4491d801f1e1c78f10 and c7088f0f3e6c8088236ef8e1e3e7, which according to the author of Crystalcursors is part of the QT symlinks mess. oxygencursors does not have these symlinks; apparently KDE/Qt uses size_fdiag and size_bdiag instead. It's almost as if those two hashes were mixed up in KDE 4, perhaps in QString XCursorTheme::findAlternative(const QString name) const in xcursortheme.cpp? Suggested patch if this is the case is attached. If it's not the case, the world (of cursor theme makers) should be told. -- Magnus Holmgrenholmg...@debian.org Debian Developer --- a/kcontrol/input/xcursor/xcursortheme.cpp +++ b/kcontrol/input/xcursor/xcursortheme.cpp @@ -82,8 +82,8 @@ QString XCursorTheme::findAlternative(co // Note that the MD5 hash for left_ptr_watch is for the KDE version of that cursor. alternatives.insert(size_ver, 81600681408080010102); alternatives.insert(size_hor, 028006030e0e7ebffc7f7070c0600140); -alternatives.insert(size_bdiag, c7088f0f3e6c8088236ef8e1e3e7); -alternatives.insert(size_fdiag, fcf1c3c7cd4491d801f1e1c78f10); +alternatives.insert(size_bdiag, fcf1c3c7cd4491d801f1e1c78f10); +alternatives.insert(size_fdiag, c7088f0f3e6c8088236ef8e1e3e7); alternatives.insert(whats_this, d9ce0ab605698f320427677b458ad60b); alternatives.insert(split_h,14fef782d02440884392942c11205230); alternatives.insert(split_v,2870a09082c103050810ffde0204); signature.asc Description: This is a digitally signed message part.
Bug#499344: reassign 499344 to crystalcursors
On måndagen den 9 augusti 2010, I stated the following: On söndagen den 8 augusti 2010, Sune Vuorela stated the following: KDE only tells X the paths where to look for cursors Also reported at https://bugs.kde.org/show_bug.cgi?id=213615, with a perhaps better analysis. I still don't think it's a bug in any cursor package; maybe in Qt? I think you could have been more helpful, but anyway, I now understand that it's libXcursor that is responsible for the fallback to the default theme, and that neither KDE nor Qt can do much about it (except that Qt could have used standard X11 cursor names when running under X11). Perhaps lower the alternatives priority for oxygencursors so that if the administrator installs additional themes besides Oxygen, one of them will be the default by default, so to speak? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#499344: Wrong cursor when oxygencursors are installed
On söndagen den 8 augusti 2010, Magnus Holmgren wrote: Alternatively, or as a workaround, all cursor packages might have to provide all their cursors under the new names as well. That would also work around the swapped resize cursors bug 548804. It appears that, at least for the time being, all cursor packages will have to provide the Qt cursor names as symlinks for them to work in KDE when Oxygen is the default theme. Here is a list: center_ptr up_arrow watch wait xterm ibeam fleur size_all hand pointing_hand v_double_arrow size_ver h_double_arrow size_hor fd_double_arrow size_bdiag bd_double_arrow size_fdiag question_arrow whats_this sb_h_double_arrow split_h sb_v_double_arrow split_v crossed_circle forbidden grabbing closedhand fleur openhand (?) -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#593890: Share bug 499344: Wrong cursor when oxygencursors are installed
On söndagen den 22 augusti 2010, Julien Cristau wrote: On Sat, Aug 21, 2010 at 23:41:49 +0200, Magnus Holmgren wrote: severity 499344 minor clone 499344 -1 -2 -3 -4 reassign -1 comixcursors reassign -2 dmz-cursor-theme reassign -3 chameleon-cursor-theme reassign -4 xcursor-themes Why? It should be clear from the bug report log, but in short, if you run KDE, have one of the Oxygen themes as system default and a user tries to choose a different theme using KDE's control panel, several of the theme's cursors will not be used. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#593890: Share bug 499344: Wrong cursor when oxygencursors are installed
On söndagen den 22 augusti 2010, Ben Finney wrote: The general problem is clear. But in cloning this report, you haven't shown where each of the packages needs to be fixed. Your list doesn't really help me find what needs to be fixed in the package. Can you please improve these reports by showing what you think is missing in each of the packages. In the case of comixcursors, I think the easiest way is to patch link- cursors.sh, appending the following (I hope I got it all right): # Qt cursor names ln -sf up-arrow up_arrow ln -sf ibeamtext ln -sf fleursize_all ln -sf pointer pointing_hand ln -sf nwse-resize size_fdiag ln -sf nesw-resize size_bdiag ln -sf ns-resizesize_ver ln -sf ew-resizesize_hor ln -sf help whats_this ln -sf col-resize split_h ln -sf row-resize split_v ln -sf not-allowed forbidden ln -sf fleuropenhand ln -sf grabbing closedhand By the way, I realise now that there is an actual conflict in that Qt expects cross to be a crosshair, but everyone else expect it to be something slightly different. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#591595: fixed in comixcursors 0.6.1-3
reopen 591595 thanks On tisdagen den 17 augusti 2010, Ben Finney wrote: * debian/preinst: + Handle the case where no cursor themes are yet installed (Closes: Bug#591595). However, it was clearly postinst that failed. What you need to do is ship an empty /usr/share/icons/default directory. Crystalcursors had the same bug not once but twice: 363059 and 582517. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#592595: (feature request) add more paramters in /etc/defaults/lsh-server
tags 592595 + confirmed thanks On onsdagen den 11 augusti 2010, you stated the following: I need to set --interface --login-root. Is it possible to add some variables in /etc/default/lsh-server? Yeah, I've also been thinking that there should be more configuration options. In the meantime though, remember that you can always edit the init script directly. It's considered a configuration file, so it won't be overwritten on upgrade. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#537259: O: skencil -- Interactive vector drawing program for X11
On torsdagen den 16 juli 2009, you stated the following: I'm orphaning skencil due to lack of interest in this package. If there is no new maintainer within about a month, I'm going to request its removal. So...? :-) -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#499344: Wrong cursor when oxygencursors are installed
reassign 499344 kdebase-workspace thanks To restate the bug report, crystalcursors includes all the important cursors, including wait/busy, what is this?, pointing hand, text selection, and resizing cursors, but the corresponding cursors from Oxygen are used nonetheless. I suspect this is because there are at least two names for each cursor, and KDE 4 uses the cursor with the preferred/new name from the default theme before any cursor available under an alternative name in the selected theme (actually I think it's just those MD5 hashes of the hardcoded built-in cursors that are used). I think that's a bug in KDE, but I'm not sure which package is responsible. I picked kdebase-workspace because it's kdebase-workspace-data that depends on oxygencursors. Please pass the bug on if I guessed wrong. Alternatively, or as a workaround, all cursor packages might have to provide all their cursors under the new names as well. That would also work around the swapped resize cursors bug 548804. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#499344: reassign 499344 to crystalcursors
On söndagen den 8 augusti 2010, you stated the following: KDE only tells X the paths where to look for cursors Also reported at https://bugs.kde.org/show_bug.cgi?id=213615, with a perhaps better analysis. I still don't think it's a bug in any cursor package; maybe in Qt? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#592119: prayer
Package: prayer Version: 1.0.18-1 Severity: serious If you enable SSL session caching, prayer uses Berkeley DB (libdb) for that, and, during initialization, compares the version number (major.minor.patch) returned by db_version() with the compile time version and terminates if the major or minor version numbers don't match or the current patch number is lower than the compile time patch number. That's unnecessary and incorrect, at least for Debian's purposes, because a) packaging, dependencies, and sonames make sure that a compatible version of libdb will be loaded, and b) the documentation states that there will be no API or ABI changes within a minor version. What can happen, and what happened now, is that prayer is built and uploaded to unstable, transitions to testing before the version of libdb it was linked against, and, if SSL session caching is enabled, complains that libdb is too old when in fact it is not. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#591966: False positive: /var/log/alternatives.log
Package: piuparts Version: 0.38 Since dpkg 1.15.8, update-alternatives logs to /var/log/alternatives.log instead of /var/log/dpkg.log, which causes a false positive for any package using alternatives. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#567945: lsh-server: Does not configure on mipsel
severity 567945 normal thanks On lördagen den 24 juli 2010, Magnus Holmgren wrote: On torsdagen den 17 juni 2010, you stated the following: Hi, sh4 has the same problem. What is sh4 by the way? There was the following logs in syslog. Jun 17 05:38:44 localhost lshd[26143]: lshd: Could not bind any address. The problem probably is that while lsh-server.postinst creates /etc/ssh/sshd_not_to_be_run, it doesn't actually stop sshd. [...] Still though, I find it strange that lsh-server would be installed if openssh- server is already, since that would fulfil lam-runtime's ssh-server dependency. Of course, if you install lsh-server in a chroot, pbuilder or otherwise, and an SSH server is installed outside it, binding port 22 will still fail, and there's not much that can be done about that. You would probably get exactly the same result if openssh-server were to be installed instead of lsh-server, because the former's postinst also fails if sshd can't be started. In summary, if you install lsh-server when there is already an sshd listening on port 22 you *have* to choose a different port for lsh-server, and having any package build-depend (indirectly) on ssh-server is probably a bad idea. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#567945: lsh-server: Does not configure on mipsel
On torsdagen den 17 juni 2010, you stated the following: Hi, sh4 has the same problem. There was the following logs in syslog. Jun 17 05:38:44 localhost lshd[26143]: lshd: Could not bind any address. The problem probably is that while lsh-server.postinst creates /etc/ssh/sshd_not_to_be_run, it doesn't actually stop sshd. I could fix that, as long as policy allows it, but the problem is that it is generally difficult to keep track of what ports and interfaces the local administrator has configured various services to use. Because two packages providing the same network service, such as HTTP/WWW, can be configured to use different ports, such packages generally do not declare conflicts with each other. Avoiding port conflicts is the responsibility of the administrator. This also means that a dependency on ssh-server is no guarantee that an SSH server is listening on port 22. Also, /etc/ssh/sshd_not_to_be_run is an old, ugly hack that should not be relied upon, and sshd could have already have been configured to listen to another port, meaning that is should not be disabled. In the case of SSH servers, it could be argued that there is little reason having more than one installed. On the other hand, I wouldn't want to remove one SSH server before I know that the next one works. At least not remotely, but on the third hand, configuring SSH servers is probably something you should do from a local console. Still though, I find it strange that lsh-server would be installed if openssh- server is already, since that would fulfil lam-runtime's ssh-server dependency. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#572271: idjc glib report
tags 572271 + patch
severity 572271 grave
justification Application doesn't start.
retitle 572271 IDJC fails to start after recent changes
thanks
On tisdagen den 2 mars 2010, Alessio Treglia wrote:
Please provide me more information.
I suspect the OP meant to report the following bug. Running idjc results in
the following exception:
Traceback (most recent call last):
File /usr/lib/python2.5/site-packages/idjcgui.py, line 90, in module
import gtk, gobject, time, fcntl, signal, stat, cairo, socket
File /usr/share/pyshared/gtk-2.0/gtk/__init__.py, line 30, in module
import gobject as _gobject
File /usr/share/pyshared/gtk-2.0/gobject/__init__.py, line 26, in module
from glib import spawn_async, idle_add, timeout_add, timeout_add_seconds,\
File /usr/share/pyshared/gtk-2.0/glib/__init__.py, line 22, in module
from glib._glib import *
ImportError: No module named _glib
I don't know why this happens, but changing
${python} ${pyexecdir}/idjcgui.py
into
${python} -m idjcgui
helps a bit. But then you get unable to open a pipe to the mixer module
because idjc_config.py wasn't updated after idjcmixer and idjcsourceclient
were moved from /usr/lib/idjc to /usr/bin. But why were they moved? They
aren't meant to be run standalone, are they? Looks like they belong in
/usr/lib/idjc.
--
Magnus Holmgrenholmg...@debian.org
Debian Developer
signature.asc
Description: This is a digitally signed message part.
Bug#567945: lsh-server: Does not configure on mipsel
On måndagen den 1 februari 2010, Adam C Powell IV wrote: lsh-server fails to configure on mipsel, as can be seen in the buildd log for scalapack: Setting up lsh-server (2.0.4-dfsg-6+b1) ... Creating lsh random seed file (this may take a while) ... done. Creating lsh host key ... .. done. Starting secure shell v2 server: lshdClosed spurious fd 3 failed! Can someone please check if there's any syslog output from lshd? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#539874: FIXED-UPSTREAM/PENDING: popups.kvs script broken
On tisdagen den 18 augusti 2009, Kai Wasserbäch wrote: Dear »antsev«, thank you for reporting the problem! As Pier has pointed out, the bug is fixed in a later SVN revision, which is ready for upload and only lacking a sponsor (our regular sponsor isn't reachable at the moment). We're trying hard to get the latest package into unstable but need to rely on a sponsor for the upload. What's the status of the kvirc package and the sponsoring of same? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#555161: doc-base: Please add section for remote access/control software
Package: doc-base Version: 0.9.5 I think a new section is needed for SSH, VNC and similar software with which you can log on remotely. At least to me none of the existing sections seem sompletely appropriate. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#553411: SSVNC's SSL support should not be disabled by default.
On lördagen den 31 oktober 2009, Karl J. Runge wrote: The debian ssvnc package puts 'stunnel4' on its recommends list instead of its depends list. This leads to a situation that confuses nearly all users that start up the SSVNC encryption gui (i.e. the main 'ssvnc' command), namely that SSVNC's default mode of encryption is SSL and all of its documentation assumes that SSL is it not disabled. Recommended packages *are* installed by default nowadays. Debian policy says that Recommends lists packages that should be installed in all but unusual cases. But you may be right that ssvnc should depend on stunnel4 nevertheless. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#552717: prayer: FTBFS: Nonexistent build-dependency: libc-client2007b-dev
On onsdagen den 28 oktober 2009, Lucas Nussbaum wrote: During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: ** Using build dependencies supplied by package: Build-Depends: cdbs, debhelper (= 5), quilt, libc-client2007b-dev | libc-client2007-dev | libc-client-dev (= 7:2007~), libldap2-dev, zlib1g-dev, libssl-dev (= 0.9.6), libdb-dev ┌ ──┐ │ Install build dependencies │ └ ──┘ Checking for already installed source dependencies... W: Unable to locate package libc-client2007-dev W: Unable to locate package libc-client2007b-dev What happened/is happening with the planned switch to unversioned libc-client post-lenny? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#544250: ssvnc: -help crashes
On lördagen den 31 oktober 2009, Karl J. Runge wrote: This bug is fixed in the recent upstream SSVNC 1.0.24 release. Great! Could you please fix sshvnc and tsvnc in the same manner? :-) -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#544250: ssvnc: -help crashes
On lördagen den 31 oktober 2009, Karl J. Runge wrote:
Great! Could you please fix sshvnc and tsvnc in the same manner? :-)
Whoops, you're right. I just uploaded a fix in the 1.0.25 dev tarball.
I created the attached patch. It handles -he and -hel too. I also notices that
the tsvnc and sshvnc wrappers redundantly sets SSVNC_{TS,SSH}_ONLY *and*
passes -ssh/-ts. The former should suffice.
--
Magnus Holmgrenholmg...@debian.org
Debian Developer
confusing_-h.dpatch
Description: application/shellscript
signature.asc
Description: This is a digitally signed message part.
Bug#103011: Development version of lsh moves config files to subdirectory of /etc
tag 103011 - wontfix thanks Upstream has actually introduced configuration files and expects them in a subdirectory (/etc/lshd) in the development branch of lsh, so we'll have to deal with that transitionl eventually. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#546918: prayer: New upstream version 1.3.2
On onsdagen den 16 september 2009, Alexander Wirt wrote: 1.3.2 has been released some time ago, what about updating the package in debian? Nice to hear that you're interested in Prayer! I'm working on it, but there are a few issues I feel I have to resolve before finalizing 1.3.2-1, most importantly that of the cam template set including the logo of the University of Cambridge. I'd like to replace it with something configurable. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#524147: libdkim-dev: should include libdkimtest
On onsdagen den 15 april 2009, Russell Coker wrote: The inclusion of libdkimtest would make it easier to test for correct operation of DKIM. Without libdkimtest it's very difficult to bootstrap DKIM development as you lack software to conveniently test the results of DKIM signing. I've done this, though it's trivial and a good excercise to compile libdkimtest.cpp (which was already included as an example) yourself. Also libdkimtest needs to be a little more user-friendly, it should display information on how to use it when incorrect parameters are given (currently it will SEGV). Can you provide more details as to what kinds of incorrect parameters cause segfaults? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#524133: libdkim0d: compile warnings
severity 524133 minor thanks On onsdagen den 15 april 2009, Russell Coker wrote: Package: libdkim0d Version: 1:1.0.19-3 Severity: normal Please apply the following patch to fix the compile warnings and to increase the use of const. Im generally reluctant to add patches merely fixing warnings, but I've made an exception since upstream is so unresponsive. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#521372: prayer: [patch] trust_from_address option for user-set envelope sender
tags 521372 - patch thanks On fredagen den 27 mars 2009, Simon McVittie wrote: The attached patch adds a trust_from_address option, which is basically the opposite of fix_from_address. If set, then each user's configurable From address is used as the SMTP envelope sender (if possible), and the user's authenticated username is placed in an X-header. It builds on usernames_with_at.patch. (Also, as a bugfix for usernames_with_at.patch, if the authenticated username contains '@', return_domain is no longer appended.) This is analogous to Exim's untrusted_set_sender option, and Postfix's default behaviour. Even if we can trust the users not to use forged sender addresses, I think we still need to sanitize the input before passing it to the shell. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#545090: lsh-server upgrade causes installation problem
On fredagen den 4 september 2009, Bartłomiej Gródek wrote: aptitude dist-upgrade causes installation error. Please find the error log below: Setting up lsh-server (2.0.4-dfsg-3) ... Starting secure shell v2 server: lshd failed! invoke-rc.d: initscript lsh-server, action start failed. Fix is on its way. But even then you need to work around it by setting VERBOSE=no. So to recover, please run (as root) VERBOSE=no dpkg --configure --pending now, or VERBOSE=no aptitude dist-upgrade after 2.0.4-dfsg-4 arrives. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#543123: chiark-utils: FTBFS: Nonexistent build-dependency: libnettle-dev
Checking for already installed source dependencies... libx11-dev: missing libnettle-dev: missing debhelper: missing Checking for source dependency conflicts... E: Package libnettle-dev has no installation candidate I intend to NMU this very shortly. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#384720: tk8.4: error messages with wish -h
On Saturday, 26 August 2006, you stated the following: Just got back from enforced vacation (dead machine). The patch looks ok, but I think I want to check with upstream before replacing an error return from a function with an exit. It all seems sensible to me, but I want to make sure there's no hidden side-effects before incorporating it. Have you checked with upstream yet? :-) -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#543150: ITP: pdkim -- cryptographically identify the sender of email
On måndagen den 24 augusti 2009, Andreas Metzler wrote: On 2009-08-23 Magnus Holmgren holmg...@debian.org wrote: On lördagen den 22 augusti 2009, Aaron M. Ucko wrote: Magnus Holmgren holmg...@debian.org writes: * Self-contained, no dependencies (except libc), thanks to code included from the PolarSSL project. From a Debian perspective, that's a policy violation, not a feature! Please arrange for it to use an external PolarSSL installation. I know and agree and will talk to Tom about this. PolarSSL currently only provides a static library however, which is also not good. I am somehow also not happy with a situation where any given exim installation would end linked dynamically (indirectly) against at least two full blown ssl libraries (OpenSSL or GnuTLS for STARTTLS, polarssl for DKIM). On a sidenote, is the cause for this ITP just exim or is general interest in this library? Primarily for Exim. Also because I already maintain a couple of DKIM-related packages. Did you want it? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#516978: spfquery: return codes and arguments changed without notice
On tisdagen den 24 februari 2009, Corin Langosch wrote: After upgrading spfquery a lot of mails got refused by our mailserver. It turned out spfquery changed a lot of their return codes (for example before success was 1, now it is 2; temp dns-failure was 5, now it is 6). Also some arguments seem to have changed, for example ipv4 is now only named ip. I couldn't find these very important changes documented anywhere. Please correct me if I'm wrong, otherwise please take care to clearly document such important changes in the future. Thank's a lot! :) spfquery *should* return (as its exit code) the SPF_RESULT_ code from libspf2, and that hasn't changed since 1.2.5 at least, and neither has the -ip parameter. Which version was it you used before? -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#543262: [checks/scripts] add pike version 7.8
Package: lintian Severity: wishlist pike7.8 is finally coming, so it needs to be added to the list of known interpreters. It's going to stay in experimental for a while, though, because we haven't decided whether the metapackages should be restructured (IOW the required depencency might be something other than pike$1-core | pike$1 for 7.8). -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Bug#459705: Status upload of pike7.8?
On lördagen den 22 augusti 2009, Luk Claes wrote: Hi What's the status of uploading pike7.8 which uses an updated Nettle? Soonish. I have checked in a patch; I'll just see what other changes to include in the same upload. -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
