There might be a related change that doesn't allow restarting the operation
with the same context without setting things up again.
Source: gcc-14
Severity: wishlist
Please consider enabling frame pointers on 64 bit arches. See:
https://www.brendangregg.com/blog/2024-03-17/the-return-of-the-frame-pointers.html
Kurt
Hi,
It's unclear to me what you're reporting as error. The connection seems to be
working. The verification of the certificate seems to fail. It seems you have
your own CA, but the CA is not trusted because it's not in the certificate
store.
Kurt
You seem to have moved the config file for some reason. Are you sure you wanted
to do that?
This seems to be caused by a missing build-depends. If I build it
locally, I do get support for 32 bit builds.
Hi,
Is the issue that with older glibc versions, it was silently casted
to a 32 bit value, but now that glibc supports 64 bit, it knows
it can't represent it, and gives an error?
Maybe for bookworm, we should just ignore the test error?
Kurt
Hi,
Are you waiting for something before uploading this fix?
Kurt
Hi,
It seems a fix for this is sitting git, but hasn't been uploaded. Is
there a reason it's not been uploaded yet?
Kurt
Source: aflplusplus
Version: 4.04c-2
Severity: serious
Hi,
Your package is failing to build on s390x:
[*] Compiling afl++ for OS Linux on ARCH s390x
./test/unittests/unit_maybe_alloc
[==] Running 6 test(s).
[ RUN ] test_pow2
[ OK ] test_pow2
[ RUN ] test_null_allocs
[
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
Source: aflplusplus
Version: 4.04c-1
Hi,
The LTO mode is not build at runtime, the log shows:
[+] llvm_mode detected llvm 10+, enabling neverZero implementation and c++14
[+] llvm_mode detected llvm 11+, enabling afl-lto LTO implementation
GNUmakefile.llvm:229: ld.lld not found, cannot enable
On Tue, Nov 22, 2022 at 06:13:30PM +0100, Kurt Roeckx wrote:
> In any case, the default cluster points to 14, it's just not on port 5432.
That doesn't seem to be true. Commands like createdb, psql default to
port 5432 if there is nothing overriding it, like PGPORT env variable.
Kurt
On Tue, Nov 22, 2022 at 10:20:06PM +0530, Pirate Praveen wrote:
>
>
> On Tue, Nov 22 2022 at 02:27:05 PM +01:00:00 +01:00:00, Kurt Roeckx
> wrote:
> > Package: gitlab
> > Version: 15.4.2+ds1-1~fto11+3
> >
> > On install I get:
> > /var/lib/dpk
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
Package: gitlab
Version: 15.4.2+ds1-1~fto11+3
On install I get:
/var/lib/dpkg/tmp.ci/preinst: 7 [: Illagal number: 9.1
I have several postgresql clusters, 9.1, 9.6, 12, 14. Not all of them
are used. 9.1 is using port 5432.
Kurt
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)
Source: cargo
Version: 0.57.0-7
Severity: wishlist
Hi,
Would it be possible to upload a newer version of cargo? The current
version is preventing me from building things. I think the 0.62 version
matches the 1.61 version of rustc that's currently in testing/unstable.
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
&
On Sun, Sep 18, 2022 at 07:09:05PM +0200, Sebastian Andrzej Siewior wrote:
> On 2020-07-16 08:46:43 [+0200], Kurt Roeckx wrote:
> > On Thu, Jul 16, 2020 at 03:57:17AM +0100, Dimitri John Ledkov wrote:
> > >
> > > openssl package could ship `.include /etc/ss
On Tue, Sep 13, 2022 at 06:40:19PM +0200, Sebastian Andrzej Siewior wrote:
> On 2022-09-13 18:30:05 [+0200], Kurt Roeckx wrote:
> > > > 3) provide a symlink from /usr/lib/ssl/cert.pem to
> > > >/etc/ssl/certs/ca-certificates.crt
> > >
> > > Kurt, I
On Tue, Sep 13, 2022 at 05:23:43PM +0200, Sebastian Andrzej Siewior wrote:
> On 2016-01-04 23:50:10 [+0100], Jan Dittberner wrote:
> > I don't know whether this will have negative side effects but from my point
> > of view it would be nice if the openssl package would do one of the
> > following
On Tue, Aug 02, 2022 at 12:50:05PM +0200, Jérémy Lal wrote:
> Package: openssl
> Version: 3.0.5-1
> Severity: normal
> Control: affects -1 nodejs
>
> Hi,
>
> while building nodejs 18.6.0+dfsg-4 on mips64el, some SSL tests did regress,
>
On Tue, Jul 19, 2022 at 06:11:23PM +0200, Diederik de Haas wrote:
> According to that bug report it should be fixed with 5.19-rc6 and that
> version
> is available in experimental. Can you verify whether it also fixes your issue?
With that version the error goes away.
This is probably https://bugzilla.kernel.org/show_bug.cgi?id=216140
Kurt
I tried older kernels, 5.17.3-1 didn't show it.
Package: linux-image-5.18.0-2-amd64
Version: 5.18.5-1
Hi,
I'm currently seeing this during boot:
[5.632167] usb 1-14: New USB device found, idVendor=8087, idProduct=0aaa,
bcdDevice= 0.02
[5.632171] usb 1-14: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[5.655513]
On Sun, Jun 05, 2022 at 08:44:22PM +0200, Sebastian Andrzej Siewior wrote:
> On 2022-06-05 19:42:43 [+0200], Sebastian Ramacher wrote:
> > Hi Sebastian
> Hi Sebastian,
>
> > > Otherwise I'd fear that the only other options are openssl breaking
> > > libssl1.1 or renaming /etc/ssl/openssl.cnf to
On Thu, May 26, 2022 at 06:26:57PM +0200, Sebastian Ramacher wrote:
>
> That leaves #1011051. What's your view on that bug?
So my understanding is that 1.1.1 doesn't understand the new
configuration file and tries to load an engine (instead of a
provider).
We could ship a file that's comptabile
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
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
It looks like it's fixed here: https://github.com/openssl/openssl/pull/18247
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
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 Sat, Apr 02, 2022 at 11:19:26AM +0200, Thorsten Alteholz wrote:
> Hi Kurt and Patrik,
>
> thanks a lot for your reports. Can you please check whether the problem
> still exists after a few new upstream versions?
Both the printer and the armel server have been replaced in the mean time.
Kurt
On Tue, Mar 22, 2022 at 10:13:25PM +0100, Sebastian Andrzej Siewior wrote:
> On 2022-03-22 21:47:52 [+0100], Kurt Roeckx wrote:
> > On Tue, Mar 22, 2022 at 08:19:01PM +, Adam D. Barratt wrote:
> > > OpenSSL signature algorith
On Tue, Mar 22, 2022 at 08:19:01PM +, Adam D. Barratt wrote:
> OpenSSL signature algorithm check tightening
> =
>
> The OpenSSL update included in this point release includes a change to
> ensure that the requested signature algorithm is supported
On Tue, Mar 22, 2022 at 08:19:01PM +, Adam D. Barratt wrote:
> Is the note below accurate?
Yes.
Kurt
On Tue, Mar 22, 2022 at 07:37:00PM +, Adam D. Barratt wrote:
> On Mon, 2022-03-21 at 00:12 +0100, Sebastian Andrzej Siewior wrote:
> > The change in openssl is commit
> >cc7c6eb8135b ("Check that the default signature type is allowed")
> >
> > Before the commit in question it connects as:
On Mon, Mar 21, 2022 at 12:12:11AM +0100, Sebastian Andrzej Siewior wrote:
>
> The change in openssl is commit
>cc7c6eb8135b ("Check that the default signature type is allowed")
So that's:
commit cc7c6eb8135be665d0acc176a5963e1eaf52e4e2
Author: Kurt Roeckx
Date: Thu
On Sun, Mar 20, 2022 at 10:00:15PM +0100, Paul Gevers wrote:
> Dear Sebastian, Kurt,
>
> On 19-03-2022 12:33, Adam D Barratt wrote:
> > Upload details
> > ==
> >
> > Package: openssl
> > Version: 1.1.1n-0+deb10u1
> >
> > Explanation: new upstream release
>
> We're seeing a
On Fri, Mar 18, 2022 at 10:22:57PM +0100, Sebastian Andrzej Siewior wrote:
> On 2022-03-18 14:51:32 [+], Adam D. Barratt wrote:
> > Boo. Hope you're doing better.
>
> Thanks, yes.
>
> > > I would also do the upload for Buster, would that work? I remember
> > > that
> > > the packages, that
Package: devscripts
Version: 2.21.7
Running dch will give me:
dch warning: neither DEBEMAIL nor EMAIL environment variable is set
dch warning: building email address from username and mailname
dch: Did you see those 2 warnings? Press RETURN to continue...
The manual says I can put it in the
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:
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).
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
Source: cargo
Version: 0.47.0-3
Severity: wishlist
Hi,
Can you package a newer version of cargo? The current version
seems to be too old for some things.
Kurt
Source: hitch
Version: 1.7.1-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
hitch.c: In function init_dh:
hitch.c:318:2: error: PEM_read_bio_DHparams is
Source: haskell-blogliterately
Version: 0.8.7-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
[12 of 12] Compiling Text.BlogLiterately (
Source: haproxy
Version: 2.2.17-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
src/ssl_sock.c: In function ‘ctx_set_TLSv13_func’:
Source: golang-github-mendersoftware-openssl
Version: 1.1.0-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
github.com/mendersoftware/openssl
#
Source: globus-proxy-utils
Version: 7.2-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
make[4]: Entering directory '/<>/test'
FAIL:
Source: globus-gssapi-gsi
Version: 14.17-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
FAIL: gssapi-thread-test-wrapper
On Wed, Oct 13, 2021 at 07:43:26AM +0300, Sergei Golovan wrote:
>
> This is a known issue, see https://github.com/erlang/otp/issues/4577
> and I'm afraid the fix will come only with the new major Erlang 25.
> It's expected to be released in May 2022.
As far as I know, there are 2 issues:
- The
Source: globus-gsi-openssl-error
Version: 4.3-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
not ok 4 - Match reference output
# Failed test 'Match
Source: git-crypt
Version: 0.6.0-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
crypto-openssl-10.cpp: In constructor
Source: freerdp2
Version: 2.3.0+dfsg1-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
/<>/winpr/libwinpr/utils/ssl.c
/<>/winpr/libwinpr/utils/ssl.c: In
Source: freelan
Version: 2.2-3
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
Source: erlang
Version: 24.0.6+dfsg-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
pkey.c:76:14: error: implicit declaration of function FIPS_mode
Source: foxeye_0.12.1-3
Version: 0.12.1-3
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
openssl.c:450:5: warning: implicit declaration of function
Source: erlang-p1-tls
Version: 1.1.13-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
EUnit
module
Source: dovecot
Version: 2.3.16+dfsg1-3
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
test_get_info_pw_encrypted
Source: crda
Version: 4.14+git20191112.9856751-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
reglib.c: In function reglib_verify_db_signature:
Source: clickhouse
Version: 18.16.1+ds-7.2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
11: + openssl dhparam -out
Source: coturn
Version: 4.5.2-3
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
src/client/ns_turn_msg.c: In function stun_produce_integrity_key_str:
Source: clevis
Version: 18-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
In file included from ../src/pins/sss/sss.c:41:
../src/pins/sss/sss.c: In
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
Source: cjose
Version: 0.6.1+dfsg1-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
jwk.c: In function _cjose_jwk_rsa_get:
jwk.c:58:5: error: RSA_get0_key
Source: cfengine3
Version: 3.15.2-3
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
In file included from hash.c:33:
./hash.h:64:28: error: unknown type
Source: certmonger
Version: 0.79.13-3
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
../../src/util-o.c: In function util_EVP_PKEY_id:
Source: boxbackup
Version: 0.13~~git20200326.g8e8b63c-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
NOTICE: Running test bbackupd in debug mode...
Source: botan
Version: 2.18.1+dfsg-3
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
Thread_Pool ran 100 tests all ok
tls:
3DES ECDH ran 2 tests 2 FAILED
Source: boinc
Version: 7.16.17+dfsg-2
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with the
following error:
In file included from /usr/include/openssl/x509.h:29,
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi,
We would like to transition to OpenSSL 3.0.0. It's currently in
experimental. It has an soname change, so the binary packages got
renamed and binNMUs will be required.
We did a
Source: azure-uamqp-python
Version: 1.4.1-1
Severity: important
Tags: bookworm sid
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Hi,
Your package is failing to build using OpenSSL 3.0 with errors
like:
Source: autobahn-cpp
Version: 17.5.1+git7cc5d37-2.1
Severity: important
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: ftbfs-3.0
Your package is building using -Werror and is using functions that
have been deprecated in OpenSSL 3.0. The log contains errors like:
In file included from
Package: cfengine3
Version: 3.15.2-3
Hi,
cfengine3 fails to build with OpenSSL 3.0 beta 1 with the
following error:
In file included from hash.c:33:
./hash.h:64:28: error: unknown type name RSA
64 | Hash *HashNewFromKey(const RSA *rsa, HashMethod method);
|
Package: certmonger
Version: 0.79.13-3
Hi,
Your package is failing to build with OpenSSL 3.0 beta 1.
The problem is that EVP_PKEY_base_id has been renamed to
EVP_PKEY_get_base_id. There is a define to rename it:
/usr/include/openssl/evp.h:# define EVP_PKEY_base_id EVP_PKEY_get_base_id
But your
Package: caml-crush
Version: 1.0.10-4
Hi,
Your package is failing to build against OpenSSL 3.0 beta 1. The
log file show:
configure:6589: checking for SSL_get_peer_certificate in -lssl
configure:6614: gcc -o conftest -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat
reassign 990228 ssl-cert
severity 990228 normal
thanks
So I think there is no bug in OpenSSL and the additional check
being done in 3.0 makes sense. So I'm reassigning this to
ssl-cert.
Kurt
On Thu, Jun 24, 2021 at 12:20:45AM +0200, Kurt Roeckx wrote:
>
> From the manpage:
>Random State Options
>
>Prior to OpenSSL 1.1.1, it was common for applications to store
>information about the state of the random-number generator in a
>file that
On Wed, Jun 23, 2021 at 09:05:03PM +0200, Sebastian Andrzej Siewior wrote:
> On 2021-06-23 14:46:37 [+0200], Andreas Beckmann wrote:
> > Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key'
> > -
> > Warning: No -copy_extensions given; ignoring any extensions in the
Package: gpg
Version: 2.2.27-1
Severity: important
Hi,
It seems that the config file ~/.gnupg/options is no longer read,
and it's now reading (among others) ~/.gnupg/gpg.conf
Jakub Wilk bisected it and pointed to this commit:
https://github.com/gpg/gnupg/commit/a028f24136a062f5
It's not the
On Sun, Feb 28, 2021 at 10:00:35PM +0100, Helmut Grohne wrote:
> Hi Kurt,
>
> On Sun, Feb 28, 2021 at 09:48:04PM +0100, Kurt Roeckx wrote:
> > I think you at least misunderstand the purpose of the script, but
> > we've also not used it in a very long time.
>
> I think
On Sun, Feb 28, 2021 at 09:26:28PM +0100, Helmut Grohne wrote:
> Package: libssl1.1
> Version: 1.1.1j-1
> Tags: patch
> User: debian-d...@lists.debian.org
> Usertags: dpkg-root-support
>
> The libssl1.1 package ships a maintainer script whose entire purpose is
> supporting upgrades from
forwarded 983013 https://gitlab.com/m2crypto/m2crypto/-/issues/293
thanks
I've created an upstream issue for it.
Package: intel-microcode
Version: 3.20201118.1~deb10u1
Hi,
spectre-meltdown-checker reports:
CVE-2018-3640 aka 'Variant 3a, rogue system register read'
* CPU microcode mitigates the vulnerability: NO
> STATUS: VULNERABLE (an up-to-date CPU microcode is needed to mitigate this
>
On Thu, Jan 14, 2021 at 07:03:37PM +0100, Kurt Roeckx wrote:
> There are a whole bunch of other issues and pull requests related to
> this. I hope this is the end of the regressions in the X509 code.
So there is something else now:
https://github.com/openssl/openssl/issues/13931
On Tue, Jan 19, 2021 at 10:55:28AM +0100, Agustin Martin wrote:
> One thing, do you know if processed vim dictionaries are arch:all?
I have no idea, but I assume it is.
Kurt
On Mon, Jan 18, 2021 at 07:34:55PM +0100, Agustin Martin wrote:
> > Note that I need to patch the .aff files to actually make it work
> > properly because vim doesn't implement all the same things
> > hunspell does.
>
> Knowing that vim does not use standard hunspell files makes things
> more
On Mon, Jan 18, 2021 at 01:22:48PM +0100, Agustin Martin wrote:
> El dom, 17 ene 2021 a las 16:06, Kurt Roeckx () escribió:
> >
> > Package: dictionaries-common-dev
> >
> > Hi,
> >
> > Vim has support for spellchecking using it's own spell check
> >
Package: dictionaries-common-dev
Hi,
Vim has support for spellchecking using it's own spell check
files. It can be generated based on hunspell .aff/.dic files, or
based on a wordlist. Files currently need to be placed in
/usr/share/vim/vim82/spell/
It would be good if we had a policy and helper
On Thu, Jan 14, 2021 at 09:13:49PM +0100, Sebastian Andrzej Siewior wrote:
> On 2021-01-14 19:03:37 [+0100], Kurt Roeckx wrote:
> > > Do you have pointers to upstream issues?
> >
> > There are a whole bunch of other issues and pull requests related to
> >
On Thu, Jan 14, 2021 at 05:43:00PM +, Adam D. Barratt wrote:
> Hi,
>
> On Fri, 2021-01-08 at 23:59 +0100, Kurt Roeckx wrote:
> > On Fri, Jan 08, 2021 at 11:39:13PM +0100, Sebastian Andrzej Siewior
> > wrote:
> [...]
> > > The i release in unsta
On Fri, Jan 08, 2021 at 11:39:13PM +0100, Sebastian Andrzej Siewior wrote:
> On 2020-11-24 20:18:15 [+], Adam D. Barratt wrote:
>
> > At some point, could we please have a combined / single diff between
> > the current 1.1.1d-0+deb10u3 and the proposed 1.1.1h-0+deb10u1 (I
> > assume)?
>
>
On Fri, Jan 08, 2021 at 11:15:54AM +0100, Diederik de Haas wrote:
> Package: aspell-nl
> Version: 1:2.20.19-1
> Severity: normal
>
> Warning: The word "&" is invalid. The character '&' (U+26) may not appear at
> the beginning of a word. Skipping word.
[...]
> The 'aptitude safe-upgrade' finish
On Tue, May 15, 2018 at 06:23:24PM +0200, Rene Engelhard wrote:
> # grep-dctrl -FBuild-Depends myspell-tools -sPackage
> # /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources
> Package: ifrench-gut
> Package: ispell-czech
> Package: norwegian
> Package: rus-ispell
That
reopen 977657
thanks
Hi,
The CI test still fails with 1.1.1i:
Testing package ssl:ssl
Script test_ssl.pl failed: Unknown message: exit(1)
% PL-Unit: ssl_options ... done
% PL-Unit: ssl_server . done
% PL-Unit: ssl_keys . done
% PL-Unit: ssl_certificates .
On Mon, Dec 21, 2020 at 05:58:55PM +0100, Michael Biebl wrote:
>
> Doing so now.
> If you feel comfortable sharing the above information via private
> email, you can send it to me directly. I'll promise to not disclose any
> information without your prior consent.
I can't reproduce it anymore
Package: swi-prolog
Version: 8.2.3+dfsg-1
Severity: serious
Forwarded: https://github.com/SWI-Prolog/packages-ssl/issues/159
Tag: patch
Hi,
Swi-prolog is failing to build using OpenSSL 1.1.1i. I've attached
a patch that fixes it.
Kurt
--- packages/ssl/test_ssl.pl.orig 2020-12-18
Package: m2crypto
Version: 0.36.0-1
Severity: serious
Forwarded: https://gitlab.com/m2crypto/m2crypto/-/issues/289
Hi,
m2crypto is failing to build since the 1.1.1i version of OpenSSL,
see the upstream bug report for more details.
Kurt
1 - 100 of 6244 matches
Mail list logo
