Package: libjsonnet-dev
Version: 0.12.1+ds-1
Thank you for packaging jsonnet for Debian.
The C++ library libjsonnet++.so is missing from the current packaging.
It is needed in order to use the libjsonnet++.h header which is included
in the packaging.
I guess the reason libjsonnet++.so was not i
Package: x11-common
Version: 1:7.6+10
Severity: normal
Tags: patch
Dear Maintainer,
I've been trying to get the sawfish WM to work with the latest gnome3.
One the sawfish mailing list I was pointed to how xmonad got things to
work:
https://wiki.archlinux.org/index.php/Xmonad#GNOME_3_and_xmonad
FYI, I was investigating this same problem in Ubuntu's
python-4suite-xml and found this other Debian bug comment that fixed
the problem for me:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468601#25
Maybe it applies to Debian's version.
Cheers,
-Brett.
--
To UNSUBSCRIBE, email to debian-
Package: openssh-client
Version: 1:4.3p2-9etch1
Severity: normal
When options are used in an authorized_keys file ssh-vulnkey fails to
identify the key as being vulnerable to dsa-1576. This example
reproduces it with a known bad key:
gateway:~# ssh-vulnkey bad_key.pub
COMPROMISED: 2048 99:9c:fe
Package: libpam-ldap
Version: 180-1.7
Severity: wishlist
Tags: patch
I use pam_ldap to authenticate systems that accept SSH passwords as
well as ones that explicitly do not allow passwords (relying on SSH
keys instead). For these latter systems, there is no way I have found
to tell pam_ldap to i
Package: puppet
Version: 0.18.4-1
Severity: wishlist
Hi.
Just a friendly wish: 0.19.1 is out!
Thanks.
-Brett.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bi
Package: puppet
Version: 0.18.4-1
Severity: wishlist
Hi,
I don't find any man pages for the puppet/puppetmaster executables. I
marked this as wishlist, but maybe it is policy too? It would be
handy even if rdoc was run on each executable and then dump that into
their respective man pages.
Tha
Okay, getting somewhere!
I noticed that the "rdoc", "rdoc1.8" and "irb1.8" packages were
installed on the broken system and were missing on the working system.
Removing irb1.8 also removed the rdoc packages and got the broken
system working again.
I then installed just irb1.8 on the previously wo
Matthew Palmer <[EMAIL PROTECTED]> writes:
> You can rename /lib/tls to something else (I like /lib/tls.disabled) and the
> linker will then run everything against the regular libraries. Perhaps give
> that a go temporarily on the failing system and see if that corrects the
> problem (then obviou
Matthew Palmer <[EMAIL PROTECTED]> writes:
> Thanks anyway for the bug report, though; we might get lucky this time and
> actually nail (one of) these bugs to the wall.
More input:
I installed the puppet client package on another machine but talking
to the same server. I brought up-to-date all
Package: puppet
Version: 0.18.4-1
Severity: important
Hi,
I'm finding that running puppetd with a very simple (but possibly
wrong) setup leads to random Ruby back traces and SegVs. Here is the
setup:
The server ("home.phy.bnl.gov") is run like:
puppetmasterd --debug
The client ("lycastus.p
Hi,
This bug seems to be show up on fresh system that lack any
pre-existing /etc/locale* files. To fix it just add
touch $LOCALEGEN
just after the definition of this variable in the file
/var/lib/dpkg/info/localepurge.config.
-Brett.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subj
Moritz Schulte <[EMAIL PROTECTED]> writes:
> I *think* an example is given in the info manual.
I find examples on how to use poldi-ctrl and they all work fine. But,
I don't see anything on what lines I need in pam.d/ files. General
googling turned up empty as well.
> Besides, I am
> currently
Package: libpam-poldi
Version: 0.3.0-2
Severity: important
Maybe I'm just being daft but as far as I can see, this package does
not actually integrate the pam_poldi module into PAM. And there are
apparently no examples of how to do this manually. At the very least
can there be a few examples gi
Package: sfs-server
Version: 1:0.8-0+pre20050819.1-2
Severity: important
Running sfssd on a system which gets user information from pam/ldap
fails to let "sfskey register" work. I found bug 225662 so either
that wasn't a complete fix or there has been a regression (but, just
in case, I include /
Package: cogito
Version: 0.12.1+20050730-1
Severity: minor
This is really minor, but for the cvsimport method to work, cvsps
(v2.1) is needed. Maybe this package should be aded to the Suggests
or Recommends header.
Thanks,
-Brett.
-- System Information:
Debian Release: testing/unstable
APT p
Package: cogito
Version: 0.12.1+20050730-1
Severity: normal
Hi,
/usr/bin/git-cvsimport-script tries to exec "git" and fails.
Reproduce it by running the following against an existing CVS
repository of your choice:
gt cvsimport -v -d $CVSROOT -C MODULE_NAME OUTPUT_DIRECTORY
...
(copious unrelate
17 matches
Mail list logo
