Package: emacs24
Version: 24.5+1-6+b1
Severity: serious
Tags: security
Justification: 5(b) of https://release.debian.org/testing/rc_policy.txt
Debian's emacs builds are linked against gnutls:
(gnutls-available-p)
t
By default, they aren't configured to validate TLS certificates,
leaving users
McVittie s...@debian.org wrote:
On Mon, 17 Nov 2014 at 21:47:12 +, Nathaniel Smith wrote:
Here's my apt history files. history.log.1 has the big upgrade that
caused the problem; history.log has the mucking about I did to fix it.
OK, thanks.
At the top of history.log.1 you have:
Upgrade
Here's my apt history files. history.log.1 has the big upgrade that
caused the problem; history.log has the mucking about I did to fix it.
Notice that the big upgrade got interrupted in the middle by libaudio2
failing to install (#768651), so there was some 'apt-get install -f'
and 'dpkg
Package: python-gobject-dbg
Version: 2.14.1-1
Severity: grave
Justification: renders package unusable
Most -dbg packages are set up so that when running under gdb, the
debugging libraries are automatically used. Not so for pygobject.
After flailing around for a while, the *only* way I could come
On Tue, Jul 03, 2007 at 07:42:08AM -0700, Daniel Burrows wrote:
On Mon, Jul 02, 2007 at 10:00:53PM -0700, Nathaniel Smith [EMAIL PROTECTED]
was heard to say:
On Sun, Jul 01, 2007 at 06:12:11PM -0700, Daniel Burrows wrote:
Does installing the version in experimental fix the problem
On Sun, Jul 01, 2007 at 06:12:11PM -0700, Daniel Burrows wrote:
Does installing the version in experimental fix the problem for you?
Yes, the aptitude in experimental (0.4.4-5~2, which appears to be
linked against apt 0.6.46.4-0.1, which is no longer in unstable?)
works fine.
-- Nathaniel
--
Package: lftp
Version: 3.5.9-1
Severity: grave
Justification: renders package unusable
~$ sudo dpkg -i /var/cache/apt/archives/lftp_3.5.10-1_i386.deb
(Reading database ... 109953 files and directories currently installed.)
Preparing to replace lftp 3.5.9-1 (using .../lftp_3.5.10-1_i386.deb) ...
On Wed, Nov 22, 2006 at 09:54:42AM -0700, Shaun Jackman wrote:
On 11/22/06, Roman Zippel [EMAIL PROTECTED] wrote:
...
1. Is this more likely a bug in Boost or a bug in monotone?
2. Is it reasonable to workaround this bug by removing
-DBOOST_SP_DISABLE_THREADS?
3. Is it worth going to the
On Tue, Nov 21, 2006 at 02:04:07PM -0700, Shaun Jackman wrote:
It appears the BOOST_SP_DISABLE_THREADS is the source of monotone's
cross-platform issues on Debian. Namely, that monotone fails to run
(deadlock) on s390, hppa, sparc, mips, and mipsel, but runs fine on
i386, amd64, ia64, alpha
This is indeed a Boost/gcc 4.0 incompatibility, but it only affects
code that monotone does not actually use; monotone 0.21's configure
checks for boost 1.32 and does some preprocessor kluging to work
around the problem. So, monotone 0.21 should fix this.
-- Nathaniel
--
Civil rights were not
10 matches
Mail list logo
