Package: ruby3.1
Version: 3.1.2-8
Severity: serious
Tags: ftbfs
A build of ruby3.1 fails on the test stage, since multiple
test/net/http/test_https.rb tests return
> "ERROR OpenSSL::SSL::SSLError: SSL_accept returned=1 errno=0
peeraddr=(null) state=error: sslv3 alert certificate expired\n"
Control: tags -1 +upstream
Control: severity -1 normal
Resetting severity to normal, as it was a result of the FTBFS. There's
an old ckeditor version bundled by upstream. It's not confirmed if the
CVE can be exploited in RT.
Should be fixed, but not a release-critical issue.
>
Control: tags +upstream
Control: severity normal
Resetting severity to normal, as it was a result of the FTBFS. There's
an old ckeditor version bundled by upstream. It's not confirmed if the
CVE can be exploited in RT.
Should be fixed, but not a release-critical issue.
tags 1042527 -ftbfs
Hello Bastien
Upstream does provide only a minified javascript in their release
tarball, but Debian package includes the source of the ckeditor used
within the third-party tarball
The error here is that ./debian/build-final-ckeditor.sh fails with
« can't locate java: No such file or directory »
This script is actually calling ckbuilder ( jexec /usr/bin/ckbuilder --
build ... )
However, the package correctly lists ckbuilder as a build-dep, and
ckbuilder itself depends on
Package: grub2
Version: 2.02+dfsg1-20+deb10u4
Followup-For: Bug #984520
Dear Maintainer,
I am also facing this error every now and then. Sometimes GRUB doesn't
boot and keeps showing "error: symbol `grub_register_command_lockdown'
not found.".
On pressing any key, GRUB restarts and I get the
Changing "xpinstall.signatures.required" to "false" will work on builds
without MOZ_REQUIRE_SIGNING.
This can be checking by going to resource://gre/modules/AppConstants.jsm
and checking the value of MOZ_REQUIRE_SIGNING, if it is false, the
signatures can be disabled with the above config.
Note
Rodrigo Campos wrote:
> It's already on sid and a backport is ready, will ask for BSA and craig will
> upload when the BSA is assigned.
What about the versions on wheezy/jessie/stretch? Should they be handled
on this bug, get a new one for each, or will they simply be handled
without one by the
Salvatore wrote:
> have you identified already the issue -> fixing commit mappings?
For version 4.8.1 [buster, sid], upstream fixed them on 4.8.2
https://codex.wordpress.org/Version_4.8.2
For version 4.7.5 [stretch], upstream fixed them on 4.7.6
https://codex.wordpress.org/Version_4.7.6
For
Thanks Arno,
I didn't find 702475 when searching earlier.
Stefan, I confirm that the workaround works
(but you need to use the full path).
--- /etc/apache2/mods-available/mpm_itk.load2013-05-12
10:39:44.743748291 +
+++ /etc/apache2/mods-available/mpm_itk.load2013-05-12
Package: kmess
Version: 2.0.3-2
Severity: normal
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.35-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8
11 matches
Mail list logo
