Just to clarify for the folks following along at home:
Steve Kemp accidentally left out a leading 'U' on the last line of the
fixed example. it should really look like this:
# DscIndices: Sources Release . .gz bzip2.sh
# DebIndices: Packages Release . .gz bzip2.sh
# UDebIndices: Packages . .gz
Package: libbonobo
Severity: normal
Tags: patch
The existing debian/watch file for libbonobo seems to be capable of
only detecting libbonobo versions 2.8.x. Given that the current
version of libbonobo in debian is 2.10.1, and the current released
version from GNOME is 2.13.0, the existing
-dev (closes: #326296)
* bumped policy to 3.6.2.1 (no changes)
* added debian/watch suggested from http://dehs.alioth.debian.org/
* set debhelper compatibility level to 5 (added debian/compat, removed
export from debian/rules, updated debian/control)
-- Daniel Kahn Gillmor [EMAIL
Package: minicom
Version: 2.1-10
Severity: normal
Tags: patch
try adding a comment line to /etc/minicom/minirc.fubar that is longer
than 80 chars. It screws up linecounting for future error reports
about the config file, and (worse!) it tries to evaluate the tail of
that line after char 80 as
Package: minicom
Version: 2.1-10
Severity: normal
the minicom packaging includes a number of patches in debian/patches
which fail to apply cleanly during a pbuilder process. (maybe because
they've been adopted upstream?)
You can see this from (for example) the results of the powerpc buildd:
Hello--
Thanks for the quick reply! i understand about not wanting to release
a development version into debian. i'm still a bit confused about
GNOME versioning, i suppose, since some GNOME projects appear to be
stable at odd minor numbers (e.g. gnumeric is in debian at 1.5.90
right now). But
Thanks for the prompt reply, Martin.
On November 26, [EMAIL PROTECTED] said:
The patches are good.
i did a bit more looking into the minicom build process, and of course
you're right: they're good. However, the build process emits a lot of
bad-looking error messages in the initial clean
On November 29, [EMAIL PROTECTED] said:
See above, seems the vm removal thingy is a misunderstanding.
What a relief! For anyone looking to stop using mime-codecs within
the vm suite, i thought i'd explicitly mention the perl one-liners
that can replace them.
From my ~/.vm:
; ***
just wanted to chime in and report that this is indeed a problem. An
example of such breakage is bug 341634 [0], filed against evince.
If a user of beast encounters this problem, it looks like it can be
repaired with:
update-mime-database /usr/share/mime
as suggested by Sebastien Bacher
Package: gnome-games
Version: 1:2.10.1-5.1
Severity: minor
Tags: patch
in gnobots2 on my mixed etch/sid system, i'm offered two non-sensical
graphics themes teleport and rteleport. It looks like this is
because a function in graphics.c is mis-filtering
/usr/share/pixmaps/gnobots, and doesn't
Package: fontforge
Version: 0.0.20050911-1.dkg.0
Severity: normal
Tags: patch
it looks to me like the current debian/watch doesn't actually track
the source for fontforge (perhaps because upstream isn't terribly
consistent with providing links).
the following watchfile seems to work for me,
i don't fully understand the /etc/serial.conf
vs. /var/lib/setserial/autoserial.conf distinction, but i think the
reason the script was trying to bail might be this:
/etc/init.d/etc-setserial is responsible for working with the
canonical /etc/serial.conf, if such a file exists.
if such a file
i'd like to second this particular request. in addition to making it
easier to use xpdf's code in other applications, having a shared
library would make dealing with security problems in xpdf much
simpler.
there has been a flood of recent DSA's [0] due to xpdf code copied
into other projects.
Package: inkscape
Version: 0.43-0.0etch1
Severity: normal
Inkscape is great! my only complaint is that it always launches by
default with A4 paper (yes, i'm an American... sigh).
when i change /usr/share/inkscape/default.svg by hand, new versions of
inkscape overwrite my changes.
it seems
tags 343840 +patch
thanks
(this patch was first submitted to bug 342388, but it is probably more
relevant here.)
The attached patch allows for individual users to keep their preferred
default template in ~/.inkscape/templates/default.svg
with this patch applied, a user who wants to have a
tags 342388 +patch
thanks
The attached patch allows for individual users to keep their preferred
default template in ~/.inkscape/templates/default.svg
with this patch applied, a user who wants to have a default template
of, say, US letter, could simply do:
mkdir -p ~/.inkscape/templates
ln
Package: inkscape
Version: 0.43-0.0etch2
Severity: wishlist
Tags: patch
inkscape 0.43 has collaborative, networked editing via XMPP built-in,
with the Inkboard project. More info is available about it in
/usr/share/doc/inkscape/NEWS.gz
The attached patch seems to enable this feature for the
Thanks for the prompt response, Wolfram.
On December 19, [EMAIL PROTECTED] said:
I know the efforts around inkboard quite well and I thought about
including the option in the debian package. But since there are some
bug (besides security risks) which are being worked on, I decided not to
Package: lavaps
Version: 2.7-4
Severity: minor
Tags: patch
i was just experimenting with lavaps. it seems to work well, but i
noticed that i was getting error messages on stderr when i
left-clicked on a zombie process. The error messages look like this:
(lavaps:9389): Gtk-WARNING **: Failed
Package: mime-codecs
Version: 7.19-7
Severity: grave
Tags: patch
Justification: renders package unusable
It appears that the buffering recently introduced to base64-decode has
some major flaws in it that render of all base64-encoded files that
are larger than the input buffer size (~36K)
Package: inkscape
Version: 0.42.2-1
Followup-For: Bug #329075
found 329075 0.42.2-1
thanks
i'm able to reproduce this problem on a mixed etch/sid system.
printing as bitmap produces the expected clipping mask, as does
exporting to a PNG. However, printing using postscript operators
ignores the
Just a ping to see what's going on with this package... it would be
great to see this move into debian (even if only to non-free at the
moment). Any word on those two remaining Numerical Algorithm
routines?
--dkg
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Package: udev
Version: 0.071-1
Severity: normal
Tags: patch
After an upgrade to udev 0.70-1 (which forced a removal of hotplug), i
found that my cryptoflex eGate USB smartcard reader wasn't being
properly attached to the openct framework when it was automatically
plugged in.
Since i need the
Package: initrd-tools
Version: 0.1.82
Followup-For: Bug #296464
found 296464 0.1.82
tags 296464 + patch
thanks
This is still a problem for me with a /dev/random keyed swap partition
and linux-image-2.6-686 version 2.6.12-10.
I'm running with version 0.1.82 of initrd-tools and cryptsetup
This looks very similar to bug 296464 to me. the extra prompt at boot
time is likely just a prompt for the crypted swap partition.
There is a patch to mkinitrd attached to that bug [0] which avoids
running cryptsetup on devices with a key specified in /etc/cryptab
during the initrd phase.
hth,
Package: fontforge
Version: 0.0.20050911-1
Severity: minor
Tags: patch
the debian package-specific web browser patch isn't applying during a
run of dpkg-buildpackage -rfakeroot for me, probably because the list
of preferred browsers changed upstream recently.
i'm attaching a revised version of
Package: fontforge
Version: 0.0.20050911-1.dkg.0
Severity: wishlist
Tags: patch
Attached is a patch to add a function SetTTFWeight() to fontforge's
scripting commands, since i couldn't find a way to set this variable
from any existing script function.
You can currently access this information
Package: gnome-session
Severity: normal
Tags: patch
in a system using pam_mount, it can be important for security that the
user's home directory be unmounted (via pam_close_session()) when they
log out.
However, debian's gnome-session spawns esd at login with a current
working directory (cwd)
Package: coreutils
Version: 5.2.1-2.1
Severity: wishlist
This is an unabashed wishlist. But i notice that Sun's nohup command
is capable of acting on already-running processes. See:
http://blogs.sun.com/roller/page/ahl/20040709
for more details on how it's done from the developer. It would
Package: mediawiki
Severity: wishlist
hello! mediaWiki released version 1.5 this month (now up to 1.5.1 as
a security update has been issued). it would be great to see it in
debian.
You can see the release notes here:
http://sourceforge.net/project/shownotes.php?release_id=366110
In
compression library - runtime
mailutils recommends no packages.
-- no debconf information
From [EMAIL PROTECTED] Tue Sep 13 17:41:04 2005
X-VM-Bookmark: 4
X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil]
[9 Tuesday 13 September 2005 17:41:04 -0400 Daniel Kahn
Gillmor [EMAIL PROTECTED] nil 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On October 17, [EMAIL PROTECTED] said:
I'm currently not sure if changing vlock is the right approach - or if
it is a misfeature in the pam module.
i agree with you that there may be problems in the pam module as well,
and it would be better if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there--
i'm happy to take over maintenance for redir. i'm not a
debian-developer yet, but i've started the NM process. i've uploaded
a version of redir containing version 2.2.1 here:
http://lair.fifthhorseman.net/~dkg/src/redir/
it fixes a
:06AM -0400, Daniel Kahn Gillmor wrote:
Hi there--
i'm happy to take over maintenance for redir. i'm not a
debian-developer yet, but i've started the NM process. i've uploaded
a version of redir containing version 2.2.1 here:
http://lair.fifthhorseman.net/~dkg/src/redir
Package: pcmcia-cs
Version: 3.2.8-5
Severity: normal
Tags: patch
i've got a PCMCIA network card from US Robotics. [0] The model number
is USR7901 (a.k.a. USR997901).
Under Linux, this card uses the pcnet_cs kernel module.
if the following stanza is added to /etc/pcmcia/config, the card
should
Package: redir
Version: 2.2.1-1
Severity: normal
In the course of tweaking the packaging for redir, i found that the
copyloop() function in this latest version (2.2.1) seems defective.
in 2.1, copyloop used:
char buf[4096]
But upstream's copyloop() in 2.2.1 allocates buf like this:
char
Hello--
i just noticed this bug. i'm really hoping that the vm package
doesn't go away. if mime-codecs go away, that wouldn't be the end of
the world (as manoj mentioned, there are one-line perl equivalents
available), but i really want vm itself to stay in debian.
i would be willing to
i'm running socat version 1.4.2.0-1, and i don't see any hexadecimal
0xB4 characters in the man page, despite there being many 0x27
characters there:
[EMAIL PROTECTED] socat]$ zcat /usr/share/man/man1/socat.1.gz | hexdump -e '1/1
%02x \n' | grep ' B4 ' | wc -l
0
[EMAIL PROTECTED] socat]$ zcat
tags 311064 + patch
thanks
here's a patch for the broken man page. i hope it's useful:
--- socat-1.4.2.0/socat.1 2005-03-18 16:24:55.0 -0500
+++ socat-1.4.2.0.dkg/socat.1 2005-11-24 00:08:26.0 -0500
@@ -2034,7 +2034,7 @@
connected to the TCP socket (nofork)\. The shell
Package: socat
Version: 1.4.2.0-1
Severity: wishlist
Tags: patch
socat version 1.4.3 is available from upstream at:
http://www.dest-unreach.org/socat/
http://www.dest-unreach.org/socat/download/socat-1.4.3.0.tar.gz
i've built it into a deb with minimal changes (just enough to close
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At 2006-12-04 23:21, [EMAIL PROTECTED] said:
When receiving mail with X-DSPAM headers already present,
local dspam adds its own to the bottom.
I just confirmed this: dspam does not replace already-present X-DSPAM
headers on a functioning dspam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks--
this is definitely a serious bug, and 10.3 has been released, claiming
to fix it.
I would actually say that this bug makes trac unusable in a standard
configuration (e.g. with an active svn repository, when hosted via
apache). Perhaps
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reopen 337317
thanks
Hi folks--
I recently upgraded openct, and switched to kernel 2.6.18 as well -- i
know: too many things changing at once! But i think i'm seeing a
recurrence of this problem, unfortunately.
After the switchover, i noticed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the quick followup, Andreas--
At 2006-12-13 22:10, [EMAIL PROTECTED] said:
If you have both /dev/bus/usb and /proc/bus/usb that is a bug in
your system config and can trigger this.
hrm. /dev/bus/usb appears to be created/managed by
i agree with Sam Morris that this bug should be treated as a security
concern.
checkrestart appears to be used primarily as a security audit tool: to
find outdated versions of libraries still in use, particularly after
security upgrades. It fails to report the things it claims to be able
to
Package: trac
Version: 0.10-3dkg1
Severity: grave
Tags: security
Justification: user security hole
Trac 0.10.1 is now available. It contains a fix for a CSRF
vulnerability:
http://trac.edgewall.org/wiki/TracDownload
It would be great if this new version could make it into debian soon.
Package: nslu2-utils
Version: 0.10+r71-1
Severity: minor
i think the senses of fast and slow are reversed in the way that
/usr/bin/leds sets up the lamps. I tend to think fast should be
high frequency (short period), and slow should be low frequency
(long period).
the following patch fixes
i'm running a mixed etch/sid system, and could not reproduce this
problem with bash_completion turned on.
TAB below reflects my hitting the tab key:
[0 [EMAIL PROTECTED] ~]$ dpkg -l bash grep dpkg libphp-pclzip
Desired=Unknown/Install/Remove/Purge/Hold
|
i tried to upgrade my instance of trac today from 0.10-1 to 0.10-2,
and apt wants to remove libapache2-mod-python (i have version 3.2.10-1
installed, which is the etch version).
i'm not sure i understand why the removal is being requested, but if i
were to agree with it, it would make trac
On October 20, [EMAIL PROTECTED] said:
A new upload has been made that i believe solves the problem. Check
under incoming.debian.org
Yep. That does it for me. I'll remember the versioned Conflicts:
approach for next time i see something like this. Thanks, Jesus.
--dkg
--
To
I can confirm this.
the precise error messages in my syslog look like this:
Oct 24 09:03:07 squeak udevd[4790]: add_to_rules: invalid SUBSYSTEMS operation
Oct 24 09:03:07 squeak udevd[4790]: add_to_rules: invalid rule
'/etc/udev/rules.d/z60_openct.rules:49'
Oct 24 09:03:07 squeak udevd[4790]:
i just wanted to followup to confirm Jan Wagner's workaround. When i
blacklist 8250_pnp, i can boot successfully with 2.6.17-2-686.
i blacklisted 8250_pnp in two spots: /etc/hotplug/blacklist.d/8250_pnp, and
also in /etc/modprobe.d/blacklist (i'm running backported udev and not
hotplug on this
I just built the trac package from a combination of:
a) the official 0.10 release tarball
(http://ftp.edgewall.com/pub/trac/trac-0.10.tar.gz)
b) the beta1 diff.gz in experimental (0.10~b1-1)
(ftp://ftp.debian.org/debian/pool/main/t/trac/trac_0.10~b1-1.diff.gz)
the diff applies fine
Perhaps i'm not following the thread on bug #367610 properly, but it
sounds to me like this isn't actually a subversion bug any more, but
rather an apache bug. Is this correct?
If so, can bug 367610 be closed (or reassigned)? Or does svn 1.4.0
still failing on ia64, even with the libapr fix?
Hi folks--
i can also duplicate this bug on a mixed sarge/sarge-backports machine
with a serial console.
I haven't had the chance yet to try the workaround jan wagner has
suggested. The errors from the console look like this:
...
00:06: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
hw_random: RNG
Package: putty-tools
Version: 0.58-5
Severity: normal
When i run puttygen (either to create a new key, or to translate an
openssh-style key), the emitted ppk file (the putty private key) is
created with the standard umask, which by default in debian leaves
things world-readable.
this is in
Package: putty-tools
Version: 0.58-5
Severity: wishlist
When writing tools to interact with Windows systems, the kh2reg.py
script in putty's contrib/ directory is actually pretty useful for
pre-seeding windows registry Putty info with known hosts information.
While i know i can grab it by
tags 396667 +patch
thanks
i'm seeing this also, when i try to build libivorbisidec (tremor,
the integer-math-only ogg vorbis decoder, a new package for debian).
# Add here commands to configure the package.
./autogen.sh --prefix=/usr
checking for autoconf...
checking for automake... yes
I question whether debian bug #168966 is appropriately tagged with
severity: minor. /etc/sudoers syntax is not for the faint of heart
(q.v. sudoers(5)). And any sudoers file of even minor complexity can
be challenging to debug if the reported line number of the error is
wrong. I suggest that
I can confirm Jacob Winther's diagnosis:
rm /usr/lib/irssi/modules/libfe_silc.so
was sufficient for me to avoid getting the duplicated messages.
I have not yet tried the modification of the Makefile to see if that
builds acceptable packages.
Thanks for the heads-up, Jacob!
--dkg
retitle 495630 ITP: faketime: report faked system time to programs
thanks
As of version 0.8, upstream is now providing a wrapper script
(/usr/bin/faketime), so the package can be built along the lines of
fakeroot and fakechroot. Upstream has also provided a man page, which
is quite nice.
Package: installation-reports
Boot method: netboot
Image version: lenny d-i beta2
Date: Tue, 26 Aug 2008 21:22:47 -0400
Machine: monkeyman
Processor: Intel(R) Xeon(TM) CPU 3.20GHz
Memory: 1G
Partitions:
0 shoveler:/# df -Tl
FilesystemType 1K-blocks Used Available Use% Mounted on
Package: gpgv
Version: 1.4.9-3
Severity: minor
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The EXAMPLES section of gpgv(1) is confusing and unclear. Attached is
a patch to improve it.
Regards,
--dkg
- -- System Information:
Debian Release: lenny/sid
APT prefers
These two bugs both seem related, in that aptitude is masking problems
and making it difficult to diagnose a failed (or compromised) mirror:
http://bugs.debian.org/457372
http://bugs.debian.org/121313
Maybe they should be merged?
I'm behind an explicit http_proxy which (while it knows that
On Thu 2008-08-28 11:40:51 -0400, Jérémy Bobbio wrote:
On Tue, Aug 26, 2008 at 09:45:33PM -0400, Daniel Kahn Gillmor wrote:
Image version: lenny d-i beta2
FWIW, this arrangment (LVM over dm-crypt over RAID) seems like a
reasonable common one, so it should be easy to configure from d-i.
See
Package: seahorse
Version: 2.22.3-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When creating a new OpenPGP key, seahorse sets all capabilities on the
key (Encrypt, Certify, Sign, Authenticate) even though it claims to
create Sign-Only keys.
To reproduce from a bare account:
From an strace of a running seahorse process (i used strace -f -s4096
seahorse), i get this output during the key creation of a key that is
ostensibly RSA (Sign-Only):
[...]
11214 execve(/usr/bin/gpg, [gpg, --batch, --no-sk-comment,
--lc-messages, C, --lc-ctype, C, --status-fd, 16, --no-tty,
Package: sqlite3
Version: 3.5.9-3
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is a unicode SQL script:
- -
CREATE TABLE foo (a varchar(10) UNIQUE);
INSERT INTO foo (a) VALUES ('@');
INSERT INTO foo (a) VALUES (NULL);
INSERT INTO foo (a) VALUES ('●');
retitle 501340 sqlite3 is wrong on SELECT DISTINCT a WHERE a IS NOT NULL over a
TEXT UNIQUE column
thanks
OK, i'm narrowing down the case where this seems to be a problem. A
couple notes:
* if the a column is not declared UNIQUE, the misbehavior goes
away.
* including the NULL entry
Package: libjs-jquery
Version: 1.2.6-1
Severity: minor
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --- /usr/share/doc/libjs-jquery/README.Debian 2008-07-18 10:52:02.0
-0400
+++ tmp/README.Debian 2008-10-08 22:07:53.0 -0400
@@ -1,7 +1,7 @@
jquery for Debian
Package: git-daemon-run
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It looks to me like git-daemon-run creates a listening service running
git-daemon as the superuser.
I've set up similar runit-supervised git-daemon instances that operate
as a non-privileged user and they
What's the status on this ITP? It would be useful to have
libcrypt-dsa-perl in debian.
--dkg
pgpEwSjjZqelG.pgp
Description: PGP signature
On Thu 2008-08-14 09:32:26 -0400, Bdale Garbee wrote:
I'm in the process of packaging upstream head of CVS for pax, and
spent some time looking at this bug. I haven't found the root cause
yet, but it appears to be an upstream problem and not unique to
Debian.
Thanks for looking into this,
Tim Kientzle of FreeBSD (author of libarchive, attempting to CC here)
describes the cpio format here:
http://people.freebsd.org/~kientzle/libarchive/man/cpio.5.txt
This document states about the SRV4 (newc) format (magic 070701, which
is what we're dealing with):
In this format,
On Mon 2008-08-18 12:53:07 -0400, Tim Kientzle wrote:
Oh, yeah. Gunnar Ritter's Heirloom toolchest
(based on open-sourced ATT code) is also a good
comparison point:
http://heirloom.sourceforge.net/tools.html
I just tested the heirloom suite here with a GNU cpio-built archive,
and it seems
Package: wnpp
Severity: wishlist
Owner: Daniel Kahn Gillmor [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: libfaketime
Version : 0.7
Upstream Author : [EMAIL PROTECTED]
* URL : http://www.code-wizards.com/projects/libfaketime
The libfaketime LD_PRELOAD hack would be really useful to me for
writing a test suite for some time-sensitive code. However, packaging
it as a library seems a little bit weird. I'm tempted to package it
instead as a simple binary package called faketime, by analogy with
fakeroot and fakechroot.
(CC'ing upstream for both datefudge and libfaketime)
This is in reference to my proposal to package libfaketime for debian,
found here:
http://bugs.debian.org/495630
On Tue 2008-08-19 03:27:47 -0400, Peter Palfrader wrote:
How does this differ from datefudge?
On Tue 2008-08-19 05:41:31
Package: aptitude
Version: 0.4.11.8-1
Followup-For: Bug #457372
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Even worse than saying Err: and then exiting with status 255 is *not*
saying Err: and exiting with status 255:
0 nik:/# aptitude update
Hit http://security.debian.org lenny/updates
On Tue 2008-08-19 13:33:06 -0400, Wolfgang Hommel wrote:
Actually, if you could point out in more detail how you'd like
libfaketime to be enhanced, e.g. how the time specification syntax
could be improved from your perspective, I'm certainly interested in
working on that. I didn't find
On Tue 2008-08-19 14:07:15 -0400, Daniel Kahn Gillmor wrote:
This was on a debian lenny amd64 vserver system. When i switched
/etc/apt/sources.list to use ftp.us.debian.org (instead of
ftp.debian,org), it looks like these silent errors went away.
These errors are back today, even
Package: cryptsetup
Version: 2:1.0.6-6
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a documentation bug, not a functionality bug:
cryptsetup luksFormat does the right thing by choosing aes-cbc-essiv
as the default cipher.
However, the man page for cryptsetup suggests
Package: silc
Version: 1.1.4-1+b1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The silc client fails if the controlling terminal is resized while the
private key passphrase prompt is present.
Steps to reproduce:
0) Open a resizable terminal emulator (konsole,
in case we are process group leader
+ *
+ * 2008-08-20 Daniel Kahn Gillmor [EMAIL PROTECTED]
+ * - if forked, wait on child process and emit its return code (exit
+ * 111 if child doesn't exit cleanly).
*
*/
#include stdio.h
#include unistd.h
#include stdlib.h
+#include sys/types.h
Package: irssi
Version: 0.8.12-5
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have both the OTR and XMPP plugins for irssi installed on my system
(see below for versions).
irssi will reliably segfault if i do the following (using a real
account on a real XMPP server, of
clone 361539 -1
reassign -1 gnupg
thanks
On Fri 2008-09-19 06:14:31 -0400, Jonathan McDowell wrote:
I agree. However the bug you've followed up to is assigned to the
debian-keyring package, whereas the issue really seems to be gpg's
behaviour.
Hrm, yes you're right about that. It affects
Package: coreutils
Version: 6.10-6
Severity: wishlist
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
there is another base64 program that performs the same purpose as
base64 in coreutils:
http://www.fourmilab.ch/webtools/base64/
It accepts -e or --encode to mean the same thing that
Package: irssi-plugin-otr
Version: 0.2-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just tried out irssi-plugin-otr for the first time. Very nice. I'm
a little concerned about the behavior when using the plugin on
multiple networks, though, given that i've seen irssi
Package: postgresql-common
Version: 90
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Currently, you cannot install the postgresql server without installing
postgresql-common. and postgresql-common depends on ssl-cert, which
brings in its own dependencies. There are reasonable
Package: irssi-plugin-otr
Version: 0.2-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you already have a registered nick on some $IRC_SERVER, Try the
following:
* launch irssi with no arguments, and make sure ~/.irssi/config
contains no autoconnect stanzas.
* /load
Hi Jack--
gnutls 2.2.1 is now in unstable:
[0 [EMAIL PROTECTED] ~]$ date
Mon Feb 11 11:54:50 EST 2008
[0 [EMAIL PROTECTED] ~]$ apt-cache policy libgnutls-dev
libgnutls-dev:
Installed: 2.2.1-3
Candidate: 2.2.1-3
Version table:
*** 2.2.1-3 0
200 http://mirrors.kernel.org
retitle 464628 tweak crashes as superuser when terminal size is exceeded
thanks
Thanks for the report!
On Thu 2008-02-07 21:19:10 -0500, A. Costa wrote:
As 'root' in an xterm:
# Show current size.
% echo $COLUMNS $LINES
99 34
# view hard drive
% tweak -l /dev/hda
Do
Package: manpages
Version: 2.67-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
random(4) currently says:
/proc Interface
The files in the directory /proc/sys/kernel/random (present since
2.3.16) provide an additional interface to the /dev/random device.
On Mon 2008-01-07 06:05:51 -0500, Jeff King wrote:
Line 107 uses '==', which is a bash-ism, breaking the script for dash
users. It can be replaced with the POSIX '='. Patch is below.
--- dnscache.orig 2008-01-07 06:05:12.0 -0500
+++ dnscache 2008-01-07 05:56:02.0 -0500
tags 458566 +pending
thanks
On Mon 2008-01-07 16:21:12 -0500, Petter Reinholdtsen wrote:
I would say you should commit it. The fix is obvious, correct, and
will solve a problem for the wast set of users using dash as /bin/sh.
I am one of them. :)
i've committed the fix to svn. hopefully
On Mon 2008-01-07 18:46:17 -0500, Daniel Kahn Gillmor wrote:
i've committed the fix to svn. hopefully it'll make it into 1.38.
Looks like we missed the window for 1.38. it'll be in 1.39. Sorry
for the delay, and thanks for the report!
Regards,
--dkg
pgpudv3CbqjG6.pgp
Description: PGP
Just following up here to say that this fix worked for me on a system
that only has postfix-doc installed:
[0 [EMAIL PROTECTED] ~]# aptitude install postfix-doc/experimental
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state
Package: nullmailer
Version: 1:1.03-5
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Version 1.0.4 of nullmailer is available from upstream:
http://untroubled.org/nullmailer/
Thanks for keeping nullmailer up-to-date in debian!
Regards,
--dkg
- -- System
Package: wnpp
Severity: wishlist
Owner: Daniel Kahn Gillmor [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: xdotool
Version : 20071229
Upstream Author : Jordan Sissel [EMAIL PROTECTED]
* URL : http://www.semicomplete.com/blog/projects
tags 431181 +pending
thanks
On Mon 2007-12-31 06:10:17 -0500, Roger Leigh wrote:
Has anything happened regarding this bug? I would really like to
see this fixed for Lenny. The patch I provided has been tested,
including for Etch-Lenny upgrades.
Thanks for the patch, and for the ping,
1 - 100 of 4303 matches
Mail list logo
