On Sat, Oct 29, 2016 at 10:32:34PM +0200, Sebastian Andrzej Siewior wrote:
> One thing that confuses me: Why has none
> of the libraries a dependency on libssl?
>From what I understand they use dlopen() and this would allow GPL
applications to use QT when they don't use OpenSSL. (QT itself
being L
On Sun, Oct 30, 2016 at 11:35:23PM +0200, Adrian Bunk wrote:
> I am raising this to RC severity since 1.0.2 will likely still be
> shipped in stretch, and removing ciphers from the 1.0.2 defaults
> that were already removed from the 1.1.0 defaults should clearly
> be done for stretch.
I did plan
Package: docker.io
Version: 1.11.2~ds1-6
Severity: serious
Hi,
I just installed docker and it doesn't seem to be working
properly, claiming it's not running.
When I run "docker info" strace is showing:
socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 3
setsockopt(3, SOL_SOCKET, SO_BR
t; | Fix memory overrun in rsa padding check functions
> |
> | Fixes #8364 and #8357
> |
> | Reviewed-by: Kurt Roeckx
> | (Merged from https://github.com/openssl/openssl/pull/8365)
> |
> | (cherry picked from commit d7f5e5ae6d53f1387a42d210806cf5e9ed0882d6)
>
On Tue, Jun 04, 2019 at 12:46:07AM +0200, Sebastian Andrzej Siewior wrote:
>
> So if I decoded it right, it does
>
> | fbuf = sha1("The magic words are squeamish ossifrage."); /* 0xbf, 0xf0,
> 0x04 … */
> | flen = RSA_public_encrypt(20, fbuf, tobuf, )
> | /* flen -> 128 */
> | r
On Tue, Jun 04, 2019 at 02:24:12PM +0200, Matěj Cepl wrote:
> Sebastian Andrzej Siewior píše v Út 04. 06. 2019 v 14:15 +0200:
> > Let me ping upstream: Matěj, could you please take a look at
> > https://bugs.debian.org/929903
> >
> > and check if it is okay the test no longer fails or if opens
Package: fetchmail
Version: 6.4.22-1
Severity: serious
Hi,
With version 6.4.22-1 and 6.4.23-1 I get the following error:
configuration requires TLS, but STARTTLS is not permitted because of
authenticated state (PREAUTH). Aborting connection. Server permitting, try
--ssl instead (see manual).
It seems that 6.4.23 actually changed the message to:
configuration requires TLS, but STARTTLS is not permitted because of
authenticated state (PREAUTH). Aborting connection. If your plugin is secure,
you can defeat STARTTLS with --sslproto '' (see manual).
See: https://gitlab.com/fetchmail/fe
Package: lbeibiou
Version: 3.61.2-1
Severity: serious
Hi,
During an upgrade, I get the following:
dpkg: considering deconfiguration of lebiniou-data, which would be broken by
installation of lebiniou ...
dpkg: yes, will deconfigure lebiniou-data (broken by lebiniou)
Preparing to unpack .../110-l
On Tue, Sep 17, 2019 at 08:32:28AM +0200, Sebastian Andrzej Siewior wrote:
> Package: python-cryptography
> Version: 2.6.1-3
> Severity: serious
>
> The upload of latest openssl 1.1.1d triggert three testsuite failures in
> python-cryptography [0]
>
> - _ test_buffer_protocol_alte
On Sun, Mar 10, 2019 at 02:20:45PM +, Steve McIntyre wrote:
> Hi!
>
> I don't know if you've even seen this RC bug. Could you please update
> the maintainer address to point to something that works?
I never got an email to the -owner address, so I couldn't migrate
it. I assume our CVS reposit
On Tue, Mar 19, 2019 at 10:28:06PM +0100, Holger Weiß wrote:
> Just for the record:
>
> * Sebastian Andrzej Siewior [2018-11-05 00:28]:
> > It is a TLS1.3 issue. If I limit max protocol to TLS1.2 then the
> > testsuite passes.
>
> Yes, it's an OpenSSL bug. If TLSv1.3 is used, SSL_get_psk_identi
On Tue, Mar 19, 2019 at 11:21:19PM +0100, Holger Weiß wrote:
> * Kurt Roeckx [2019-03-19 22:59]:
> > On Tue, Mar 19, 2019 at 10:28:06PM +0100, Holger Weiß wrote:
> > > Yes, it's an OpenSSL bug. If TLSv1.3 is used, SSL_get_psk_identity()¹
> > > unexpectedly returns
All the errors in the test suite are problems in the test suite
itself. Some of those have been fixed upstream.
Some of the problems are:
- The test suite used 1024 bit keys, they have been replaced by
2048 bit keys
- The test suite didn't send the Finished message to the server,
the client ju
On Wed, Oct 17, 2018 at 09:22:35PM +0300, Niko Tyni wrote:
>
> As a status update, I count just six packages left in testing that are
> marked as blockers for this bug. (I could be wrong of course; double
> checking welcome.)
I think you missed one.
> - src:foolscap #898800: foolscap: FTBFS agai
On Thu, Oct 18, 2018 at 04:05:32PM +0200, Mattia Rizzolo wrote:
> On Thu, Oct 18, 2018 at 04:01:59PM +0300, Niko Tyni wrote:
> > On Wed, Oct 17, 2018 at 09:21:29PM +0200, Kurt Roeckx wrote:
> > > On Wed, Oct 17, 2018 at 09:22:35PM +0300, Niko Tyni wrote:
> >
> > &
I will enable SSLv2, SSLv3, 3DES, RC4, export ciphers, and so on again.
On Sun, Oct 07, 2018 at 11:00:48AM +0200, Andrej Shadura wrote:
>
> I’m unsure what can be done to help resolve this issue from the wpa side.
The only thing I can think of is that wpa could add a way to
specify the minimum tls version.
On Tue, Sep 25, 2018 at 11:29:28PM +0200, Sebastian Andrzej Siewior wrote:
> On 2018-08-25 10:33:54 [+0200], Kurt Roeckx wrote:
> > On Fri, Jun 01, 2018 at 11:22:09AM +, Sandro Knauß wrote:
> > > Source: kopete
> > > Source-Version: 4:18.04.1-1
> > >
> &
Package: python-twisted-core
Version: 18.7.0-2~bpo9+1
Severity: serious
Hi,
With python-twisted-core and python-attr 16.3.0-1, I get the
following error:
[...]
File "/usr/lib/python2.7/dist-packages/twisted/web/http.py", line 100, in
from twisted.internet import interfaces, protocol, addr
On Sat, Nov 03, 2018 at 11:12:37AM +0100, Julien Lecomte wrote:
> Package: openssl
> Version: 1.1.1-2
> Severity: serious
> Justification: makes unrelated software on the system (or the whole system)
> break
>
> Dear Maintainer,
>
> On a fresh install of Debian/Buster via the alpha3 dvd ISO, whe
On Mon, Nov 05, 2018 at 12:28:50AM +0100, Sebastian Andrzej Siewior wrote:
>
> No, it is not. It is a TLS1.3 issue. If I limit max protocol to TLS1.2
> then the testsuite passes. The problem with TLS1.3 could be that
> SSL_read() could return SSL_ERROR_WANT_READ asking to do the same. Was
> there
--- Begin Message ---
Hi, everybody,
there is a new release of M2Crypto, most complete Python bindings
for OpenSSL (from 1.0.1e to 1.1.1), supporting both Python 2 (2.6
and 2.7) and Python 3 (from 3.4 upwards).
This is mostly bugfix release, including:
- support for OpenSSL 1.1.1
- Fixes for
On Sun, Oct 28, 2018 at 11:29:43PM +0100, Sebastian Andrzej Siewior wrote:
> On 2018-10-21 12:31:45 [+0200], Kurt Roeckx wrote:
> > On Tue, Sep 25, 2018 at 11:29:28PM +0200, Sebastian Andrzej Siewior wrote:
> > > On 2018-08-25 10:33:54 [+0200], Kurt Roeckx wrote:
> > > &
On Sat, Nov 10, 2018 at 03:48:37PM +0100, Pino Toscano wrote:
> In data sabato 10 novembre 2018 13:30:19 CET, Kurt Roeckx ha scritto:
> > On Sun, Oct 28, 2018 at 11:29:43PM +0100, Sebastian Andrzej Siewior wrote:
> > > On 2018-10-21 12:31:45 [+0200], Kurt Roeckx wrote:
> >
Source: kde4libs
Version: 4:4.14.38-2
Severity: serious
Hi,
It seems that kde4libs Build-Depends on libssl1.0-dev as a result
of #828363. There are currently no packages depending on
libssl1.0.2 left in testing, but this source package is the only
one that has a Build-Depends against libssl1.0-de
On Wed, Nov 28, 2018 at 02:35:42PM +, Christoph Groth wrote:
> My mbsync (isync package) setup stopped working for a particular IMAP server
> because of this bug. I get the following error message:
>
> Socket error: secure connect to imap.server.com (1.2.3.4:993):
> error:141A318A:SSL routi
On Sun, Dec 02, 2018 at 11:36:06PM +0100, gregor herrmann wrote:
> On Sun, 02 Dec 2018 23:18:38 +0100, Sebastian Andrzej Siewior wrote:
>
> > On 2018-12-02 13:06:04 [+], Debian Bug Tracking System wrote:
> > > #900160: ruby-eventmachine: FTBFS against openssl 1.1.1
> > > ruby-eventmachine (1.
tags 996276 - bookworm-ignore experimental + bookworm sid
thanks
This is affecting the bookworm release. The release managers approved the
upload to unstable and marked it as serious/release critical.
You can test it by installing the version from unstable.
On Wed, May 11, 2022 at 07:25:45PM +0300, Andriy Grytsenko wrote:
> >You can test it by installing the version from unstable.
>
> It is not in unstable yet, see
That should have said experimental.
Kurt
It looks like it's fixed here: https://github.com/openssl/openssl/pull/18247
Source: thrift
Version: 0.16.0-5
Severity: serious
Tags: sid bookworm
Hi,
It seems that thrift does not depend on libssl after being rebuild
against OpenSSL 3.0, but did depend on libssl1.1.
Kurt
Source: nvidia-cuda-toolkit
Version: 11.4.3-2
Severity: serious
Tags: sid bookworm
Hi,
It seems build-depends on libssl1.1 and not on libssl-dev. It also
depends on libssl1.1 and doesn't transition to libssl3 on rebuild.
Can you please move to using libssl3?
Kurt
On Sun, Sep 25, 2022 at 02:16:00AM +, Thorsten Glaser wrote:
> Kurt Roeckx dixit:
>
> >On Sat, Sep 24, 2022 at 10:34:19PM +0200, Thorsten Glaser wrote:
> >> $ openssl s_client -CApath /etc/ssl/certs -connect www.mirbsd.org:443
> >> -legacy_renegotiation -tls1
&
Package: gitlab
Version: 15.4.2+ds1-1~fto11+3
Severity: serious
Setting up gitlab (15.4.2+ds1-1~fto11+3) ...
Bundler could not find compatible versions for gem "omniauth-oauth2":
In Gemfile:
omniauth-auth0 (~> 2.0) was resolved to 2.0.0, which depends on
omniauth-oauth2 (~> 1.4) x86_64
fasttrack contains a 1.7.3 version that's new enough. The 1.8.0 version
from backports is too new it seems, and it what gets installed when
you just do: apt install gitlab
Source: aflplusplus
Version: 4.04c-1
Severity: serious
Hi,
On the buildds, we get:
# -/usr/bin/make -C utils/plot_ui
/usr/bin/make -C frida_mode
make[3]: Entering directory '/<>/frida_mode'
mkdir -p /<>/frida_mode/build/
mkdir -p /<>/frida_mode/build/frida/
wget -qO
/<>/frida_mode/build/frida/fr
On Mon, Oct 18, 2021 at 10:40:59PM +0200, Julien Cristau wrote:
> On Mon, Oct 18, 2021 at 02:50:50PM +0200, Benjamin Hof wrote:
> > Hi,
> >
> > I think the following change might be the relevant one:
> >
> > --- a/update-ca-certificates
> > +++ b/update-ca-certificates
> > @@ -164,8 +
On Tue, Jun 12, 2018 at 09:57:56PM +0200, Axel Beckert wrote:
> Hi,
>
> Thijs Kinkhorst wrote:
> > >> I've read about this bug (and the other one) on d-devel. I uploaded
> > >> recently a new version of openssl to unstable (1.1.0h-3)which changes
> > >> the exit code of "openssl rehash" to zero in
On Fri, Apr 06, 2018 at 01:58:03PM +0100, Simon McVittie wrote:
> Package: osc
> Version: 0.162.1-1
> Severity: grave
> Justification: osc tool becomes mostly unusable
>
> This is probably a bug in libssl1.1 or in python-m2crypto, but I'm
> reporting it against osc for now, because that's the only
On Fri, Apr 06, 2018 at 07:54:44PM +0100, Simon McVittie wrote:
> On Fri, 06 Apr 2018 at 19:44:18 +0200, Kurt Roeckx wrote:
> > On Fri, Apr 06, 2018 at 01:58:03PM +0100, Simon McVittie wrote:
> > > This is probably a bug in libssl1.1 or in python-m2crypto, but I'm
> &g
On Tue, Feb 27, 2018 at 09:39:11PM +0100, Sebastian Andrzej Siewior wrote:
> control: clone -1 -2
> control: reassign -2 libio-socket-ssl-perl 2.056-1
> control: severity -2 normal
> control: tags -2 patch
>
> On 2018-02-27 21:52:23 [+0800], 積丹尼 Dan Jacobson wrote:
> > Here is all you need to repr
On Tue, Feb 27, 2018 at 02:37:38AM +0800, 積丹尼 Dan Jacobson wrote:
> Package: libssl1.1
> Version: 1.1.1~~pre1-1
> Severity: grave
>
> SSL connect attempt failed error:141A90B5:SSL
> routines:ssl_cipher_list_to_bytes:no ciphers available
See https://www.openssl.org/blog/blog/2018/02/08/tlsv1.3/ a
On Mon, Sep 11, 2017 at 11:33:22AM +0200, Raphaël Hertzog wrote:
> Or at least I would like a system-wide flag (in a configuration file?) to
> let me re-enable old protocols easily.
It was my understanding that other people also prefered to do this
on a per package level and not system wide.
Kur
On Mon, Sep 11, 2017 at 12:30:30PM +0200, Raphael Hertzog wrote:
> But in Debian testing, we have real end-users (direct and through
> "rolling" derivatives) and they should not have to be impacted by this
> experiment IMO.
I have to admit that I didn't consider derivatives that take a
snapshot of
On Wed, May 02, 2018 at 05:19:20PM +0100, Simon McVittie wrote:
> * https://github.com/openssl/openssl/pull/5967
>
> """
> Commit d316cdc introduced some extra
> checks into the session-cache update procedure, intended to prevent
> the caching of sessions whose resumption would lead to a h
On Wed, May 02, 2018 at 07:26:02PM +0200, Sebastian Andrzej Siewior wrote:
> On 2018-05-02 18:34:35 [+0200], Kurt Roeckx wrote:
> > On Wed, May 02, 2018 at 05:19:20PM +0100, Simon McVittie wrote:
> > > * https://github.com/openssl/openssl/pull/5967
> > >
> &g
On Fri, Dec 29, 2017 at 02:57:11PM +0100, Andreas Henriksson wrote:
> Control: severity -1 serious
> Control: affects -1 iproute2
> Control: tags -1 + patch
>
> Hello,
>
> Missing dependency is a policy violation, thus bumping to severity
> to serious.
> Hopefully this can be fixed very soon (so
On Tue, Mar 31, 2020 at 09:03:01AM +0200, Salvatore Bonaccorso wrote:
> On Sat, Mar 21, 2020 at 08:31:21PM +0100, gregor herrmann wrote:
> > On Fri, 20 Mar 2020 21:50:08 +0100, Sebastian Andrzej Siewior wrote:
> >
> > > The package FTBFS since openssl has been updated to 1.1.1e because the
> > > t
On Tue, Mar 31, 2020 at 09:49:51PM +0200, Salvatore Bonaccorso wrote:
> Hi Kurt,
>
> On Tue, Mar 31, 2020 at 06:46:44PM +0200, Kurt Roeckx wrote:
> > On Tue, Mar 31, 2020 at 09:03:01AM +0200, Salvatore Bonaccorso wrote:
> > > On Sat, Mar 21, 2020 at 08:31:21PM +010
On Tue, Mar 31, 2020 at 11:48:26PM +0200, Steffen Ullrich wrote:
> > You should fix your tests not to trigger an unexpected EOF. You
> > probably have code now that ignores the current error, you
> > shouldn't ignore that error, it's a real error.
>
> Fixing the tests to only consider an ideal wor
Package: unbound
Version: 1.9.6-1
Severity: serious
Hi,
After upgrade to 1.9.6-1, unbound did no longer start. It did not
log anything about this in any log file.
I have a config that says:
do-not-query-localhost: no
It now returns a syntax error for that.
Kurt
Package: rng-tools
Version: 5-1
Severity: serious
I tried to upgrade from 2-unofficial-mt.14-1+b2 to 5-1, but
installation failed because --feed-interval and --rng-entropy
are no longer supported.
It's non-trivial to found out what the problem is, no error message
is logged or displayed on the s
On Mon, Jun 01, 2020 at 01:29:39AM +0200, Axel Beckert wrote:
> OpenSSL 1.1.1g 21 Apr 2020
> → openssl s_client -connect mirror.sinavps.ch:443
> CONNECTED(0003)
> depth=3 C = SE, O = AddTrust AB, OU = AddTrust External TTP Network, CN =
> AddTrust External CA Root
> verify error:num=10:certif
Just to clarify, as I understand it, openssl 1.0.2 (so libssl1.0.2
in oldstable) still has the problem, which means things like
libcurl in oldstable have that problem. And removing the
certificate from the trust store fixes it.
Kurt
There might be a related change that doesn't allow restarting the operation
with the same context without setting things up again.
On Mon, Jun 05, 2006 at 07:39:00PM +0200, Matej Vela wrote:
> tag 360456 moreinfo
> thanks
>
> "Angus Lees" <[EMAIL PROTECTED]> writes:
>
> > On 4/2/06, Kurt Roeckx <[EMAIL PROTECTED]> wrote:
> >
> > Package: libembperl-perl
>
found 300146 1.6.7-1
thanks
Just marking this as found in version 1.6.7-1, since it wasn't
marked as found in any version, and it's still the version
currently in testing.
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: libgnomesu0
Version: 0.9.5-2+b1
Severity: grave
Hi,
It seems there was a binNMU for libgnomesu on amd64 and s390 to
rebuild against libtasn1-3. But now it's uninstallable because
it has a arch all package with a strict versioned dependency on.
Could you please do a sourceful upload to
Package: plplot
Version: 5.6.0-1
Severity: serious
Hi,
Your package currently can't be build because it has conflicting
build dependencies.
You build depend on both gcj and libgcj6-dev, which can't be
installed at the same time now, since gcj moved to gcj 4.1.
You should probably either change
Package: xfce4-showdesktop-plugin
Version: 0.4.0-3
Severity: serious
Hi,
Your package is failing to build with the following error:
checking for XFCE4_PANEL... configure: error: Package requirements
(xfce4-panel-1.0 >= 4.0.0) were not met:
No package 'xfce4-panel-1.0' found
Consider adjusting
Package: fftw
Version: 2.1.3-18
Severity: serious
Hi,
On all 64 bit arches, your package is failing to build with the
following error:
#/usr/bin/make -C tests check
./tests/fftw_test -t -e -v -p 1024 -x 1
make: *** [build-arch-stamp] Terminated
Build killed with signal 15 after 150 minutes of in
Package: whowatch
Version: 1.6.0a-1
Severity: serious
Hi,
Your package is failing to build with the following error:
gcc -g -O0 -Wall -I. -ggdb -rdynamic -o whowatch process.o procinfo.o
proctree.o owner.o screen.o block.o user.o subwin.o pluglib.o menu.o
input_box.o menu_hooks.o info_box.o
Package: psycopg
Version: 1.1.21-6
Severity: serious
Hi,
Your package is failing to build with the following error:
gzip -f9 ZPsycopgDA-1.1.21.tar
make[1]: Leaving directory `/build/buildd/psycopg-1.1.21'
/bin/sh: line 3: dh_installzope: command not found
make: *** [install] Error 127
This is p
On Thu, Jun 15, 2006 at 11:21:23PM +0200, KELEMEN Peter wrote:
> * Kurt Roeckx ([EMAIL PROTECTED]) [20060615 19:23]:
>
> > whowatch.o: In function `main':
> > /build/buildd/whowatch-1.6.0a/src/whowatch.c:288: undefined reference to
> > `read_key'
>
&
Package: starfighter
Version: 1.1-4
Severity: serious
Hi,
Your package is failing to build with the following error:
dh_clean
debian/rules build
dh_testdir
mkdir pak
(cd pak && python ../debian/unpack.py ../starfighter.pak)
/bin/sh: python: command not found
make: *** [configure-stamp] Error 127
On Fri, Jun 16, 2006 at 11:16:04AM +0200, KELEMEN Peter wrote:
> * Kurt Roeckx ([EMAIL PROTECTED]) [20060615 23:35]:
>
> > checking whether select() modifies the time value... no
>
> > And you should probably look at why the configure script returns
> > that.
>
On Mon, Jun 12, 2006 at 04:57:34PM +0200, Peter Eisentraut wrote:
> If --exec is not to be used, I suppose this patch, which uses --startas,
> would
> be the way to go. The problem is that the ntpd child processes, which are
> not listed in the pidfile, are pretty slow to go away if you SIGTERM
Hi,
Current svn looks like:
Package: ntp-server
Depends: ntp-simple (>> 1:4.2.0a+stable-6) | ntp-refclock (>>
1:4.2.0a+stable-6), ntp
Package: ntp-refclock
Depends: ${shlibs:Depends}, ${misc:Depends}, adduser
Recommends: ntp-server (= ${Source-Version})
Package: ntp-simple
Depends: ${shlibs:Dep
On Sat, Jun 17, 2006 at 12:29:25AM +0200, Peter Eisentraut wrote:
> Another thought is to fold the ntp-simple and ntp-refclock packages into
> ntp-server and handle the choice via alternatives or some other simple
> switch.
I actually have no idea why it was splitted in 2 packages. Afaik
the on
found 312331 1:4.2.0a+stable-8.2
thanks
It's still doing that in 1:4.2.0a+stable-8.2.
I think we want an && instead of an || in the ntp-server.preinst?
preinst can be called in the following ways:
* `install'
* `install'
* `upgrade'
* `abort-upgrade'
And w
On Sat, Jun 17, 2006 at 02:22:14PM +0200, Peter Eisentraut wrote:
>
> I think we only want to cover case 3, because case 2 is that the old
> package is removed but not purged, so there should be no binaries left
> to kill anyway.
>
> But actually, the checked version 1:4.2.0a-10 is older than t
On Sat, Jun 17, 2006 at 08:32:41PM +0200, Peter Eisentraut wrote:
> Kurt Roeckx wrote:
> > The rest of the preinst seems to be for a pre-sarge version too
> > (and is there since 1:4.2.0a-2), so maybe we can just get rid
> > that whole part of the preinst?
>
> So i
Package: qm
Version: 2.3-2
Severity: serious
Hi,
Your package is failing to build with the following error:
for v in 2.3 2.4; do \
python$v setup.py clean; \
done
running clean
/bin/sh: line 1: python2.4: command not found
make: *** [clean] Error 127
Kurt
--
To UNSUBSCRIBE
Package: libgphoto2-2
Version: 2.2.0-2
Severity: serious
Hi,
Your package is failing to install with the following error:
Setting up libgphoto2-2 (2.2.0-2) ...
/var/lib/dpkg/info/libgphoto2-2.postinst: line 25:
/usr/share/hal/fdi/information/10freedesktop/10-camera-libgphoto2.fd: No such
file o
Package: libbonoboui2-dev
Version: 2.14.0-2
Severity: serious
Hi,
libgnutls-dev just changed from depending on libtasn1-2-dev to
libtasn1-3-dev. You have a Depends on both libtasn1-2-dev and
libgnutls-dev, so those now conflict.
PS: Why do you depend on it when you don't have a build
dependency
Package: shishi
Version: 0.0.26-1
Severity: serious
Hi,
Your package can't install it's build dependencies. It depeneds
on both libgnutls-dev and libtasn1-2-dev. libgnutls-dev now
depends on libtasn1-3-dev and that conflicts with libtasn1-2-dev.
You should probably change from libtasn1-2-dev t
Package: gphoto2
Version: 2.2.0-1
Severity: serious
Hi,
Your package is failing to build with the following error:
checking whether popt is required... no
checking whether popt is requested... auto
checking popt.h usability... no
checking popt.h presence... no
checking for popt.h... no
checking p
On Sun, Jun 18, 2006 at 05:06:29PM +0200, Loïc Minier wrote:
> On Sun, Jun 18, 2006, Kurt Roeckx wrote:
> > PS: Why do you depend on it when you don't have a build
> > dependency for either of those?
>
> Because of *.la files (the list of deps added for *.la files is h
On Sun, Jun 18, 2006 at 05:21:06PM +0200, Loïc Minier wrote:
> On Sun, Jun 18, 2006, Kurt Roeckx wrote:
> > You really should only add those -dev packages your packages
> > added to it. If your package wasn't using them, they should be
> > in other .la files, and tho
On Sun, Jun 18, 2006 at 06:18:01PM +0200, Loïc Minier wrote:
>
> On Sun, Jun 18, 2006, Kurt Roeckx wrote:
> > > grep /usr/lib/libtasn1.la /usr/lib/libbonoboui-2.la
> > If I rebuild it now, it's actually not there anymore. So you can
> > just remove it.
>
On Sun, Jun 18, 2006 at 07:06:53PM +0200, Loïc Minier wrote:
>
> *.la files are pure evil, and we should get rid of them. I wish I
> wouldn't have to resort to awful dependencies like I have to right now,
> but the removal process is long when done properly (ie not like
> Xcursor).
I agree t
found 346958 2.10-2
thanks
Hi,
Your package is failing to build with error message like:
xpad-session-manager.o: In function
`xpad_session_manager_stop_interact':/build/buildd/xpad-2.10/src/xpad-session-manager.c:168:
undefined reference to `SmcInteractDone'
xpad-session-manager.o: In function
Hi,
It seems to me that tls1_enc() is setting
SSL_OP_TLS_BLOCK_PADDING_BUG, while the other side does
not have that bug.
The code looks like this:
/* First packet is even in size, so check */
if ((memcmp(s->s3->read_sequence,
Package: kmymoney2
Version: 0.8.2-1
Severity: serious
Hi,
Your package is failing to build with the following error:
fakeroot debian/rules clean
debian/rules:7: /usr/share/cdbs/1/class/autotools.mk: No such file or directory
debian/rules:8: /usr/share/cdbs/1/rules/debhelper.mk: No such file or d
Package: libusb
Version: 2:0.1.11-1
Severity: serious
Hi,
Your package is failing to build on a few arches with the
following error:
gcc -DHAVE_CONFIG_H -I. -Werror -Wall -g -O2 -MT linux.lo -MD -MP -MF
.deps/linux.Tpo -c ../linux.c -fPIC -DPIC -o .libs/linux.o
cc1: warnings being treated as er
found 347036 2.2.5-5
thanks
Hi,
pente is now failing to build with the following error:
checking for X... no
[...]
cd wmslib/src/abut; gcc -O2 -fomit-frame-pointer -I/build/buildd/pente-2.2.5/wm
slib/src -I/build/buildd/pente-2.2.5/obj-x86_64-Linux -g -Wall -O2 -c abut.c
In file included from /bu
On Sun, Jan 22, 2006 at 09:23:13PM +0100, Martin Sebald wrote:
> Hello!
>
> > We believe that the bug you reported is fixed in the latest version of
> > openssl, which is due to be installed in the Debian FTP archive:
>
> Was this meant for me? Otherwise sorry for spamming around... ;-)
>
> I u
On Sun, Jan 22, 2006 at 11:20:10PM +0100, Martin Sebald wrote:
>
> I tried it after Yari wrote again (I attached his mail at the bottom of
> this mail). And it works. I also do not think it is the best solution but I
> think it is a workaround until the bug in OpenSSL is fixed.
The default cipher
On Fri, Jan 27, 2006 at 07:24:33PM +0100, Martin Sebald wrote:
>
> Why are the two packages openssl and libsslx.x.x not depending on each
> other?
openssl does depend on libssl0.9.8, it has a depends on:
libssl0.9.8 (>= 0.9.8a-1)
There is no reason they should be from the same source version.
Package: libavahi-qt3-dev
Version: 0.6.4-2
Severity: serious
Hi,
Your libavahi-qt3.la references the /usr/lib/libXft.la which was
part of libxft-dev. It has been removed, and now packages who
have an (indirect) build dependency on you that use libtool fail
to build because it's looking for it.
Package: gri
Version: 2.12.10-1
Severity: serious
Hi,
Your package is failing to build with the following error on 64
bit arches:
CmdFile.hh: In copy constructor 'CmdFile::CmdFile(const CmdFile&)':
CmdFile.hh:25: error: cast from 'const CmdFile*' to 'unsigned int' loses precis
ion
CmdFile.hh:25:
Package: libclutils0-dev
Version: 20051029-1
Severity: serious
Hi,
When building the savant package, I get the following error:
checking for isClutils in -lclutils... no
configure: error: Could not find a workable libclutils.so or libclutils.a.
You probably need to install clutils and/or spec
Package: mesa
Version: 6.4.1-0.2
Severity: serious
Hi,
Your package is failing to build on the auto builders with the
following error:
E: Couldn't find package makedepend
The problem is the order of the build dependencies. It has:
makedepend | xutils
sbuild will always pick the first one, and
Hi,
Has there been any progress on fixing this?
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: warped
Version: 20051029-2
Severity: serious
Hi,
Your package is failing to build with the following error:
checking for PCCTS includes... /usr/include/pccts
checking AParser.h usability... no
checking AParser.h presence... no
checking for AParser.h... no
configure: error: Could not find
Package: librmagick-ruby
Version: 1.10.0-1
Severity: serious
Hi,
Your package is failing to build with the following error:
fakeroot debian/rules clean
debian/rules:11: *** target file `unpatch' has both : and :: entries. Stop.
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a sub
Package: prelude-manager
Version: 0.9.2-1
Severity: serious
Hi,
Your package is failing to build with the following error:
checking for libprelude-config... /usr/bin/libprelude-config
checking for libprelude - version >= 0.9.4... no
*** An old version of LIBPRELUDE (0.9.0) was found.
*** You need
Package: libgpevtype0-dev
Version: 0.11-1
Severity: serious
Hi,
Your libgpevtype.pc file states:
Requires: glib-2.0, mimedir-1.0
You should be adding dependencies for those packages to your -dev
package in case they really are required. This seems to mean you
need to add a depends on libglib2.0
severity 352047 serious
thanks
On Thu, Feb 09, 2006 at 02:27:19PM +0100, Gabriel Forté wrote:
> On Thu, Feb 09, 2006 at 03:08:01AM -0800, Steve Langasek wrote:
> > On Thu, Feb 09, 2006 at 11:39:29AM +0100, Gabriel Forté wrote:
> > > Package: libssl0.9.8
> > > Version: 0.9.8a-6
> > > Severity: crit
101 - 200 of 2617 matches
Mail list logo
