On Sun, Apr 07, 2019 at 02:01:33PM +0200, Darshaka Pathirana wrote:
> Hey,
>
> On Mon, 11 Mar 2019 12:05:55 +0200 Adrian Bunk wrote:
> > On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote:
> > > Hello Everyone,
> > > I own a qnap ts-119pII with a similar cpu.
> > >
> > > See
> You're welcome :-) Does clearing the SSL_MODE_AUTO_RETRY context flag
> (i.e., reverting the default from OpenSSL <1.1.1) solves this for you
> too? If so, what do you think about my proposed paths forwards from
Simply clearing SSL_MODE_AUTO_RETRY will cause problems with blocking
connections
Hi Hugo,
On Mon, Apr 08, 2019 at 10:20:29PM +0200, Hugo Lefeuvre wrote:
> Hi Salvatore,
>
> > CVE-2016-10745 was assigned for this issue.
>
> Thanks for the information.
>
> I just noticed you added CVE-2016-10745 to the tracker. I am fairly
> confused, do you know why this CVE was not
Processing control commands:
> reassign -1 grub2-common
Bug #926689 [cryptsetup] cryptsetup-initramfs: config lines in grub.cfg for
cryptodisk/luks and other modules missing
Bug reassigned from package 'cryptsetup' to 'grub2-common'.
No longer marked as found in versions cryptsetup/2:2.1.0-2.
Control: reassign -1 grub2-common
Control: merge-1 924151
Hi,
On Mon, 08 Apr 2019 at 20:19:47 -0400, Gabriel Filion wrote:
> Package: cryptsetup
> Version: 2:2.1.0-2
> […]
> I found out that some configuration lines are missing in all options that get
> generated inside grub.cfg.
>
> Here's
Package: cryptsetup
Version: 2:2.1.0-2
Severity: grave
Justification: renders package unusable
Hello,
I've rebooted my computer this morning and the password prompt to unlock the
crypto device would not appear before grub would search for the lvm device
inside.
This means that the system was not
Processing commands for cont...@bugs.debian.org:
> reassign 926687 src:linux 4.19.28-2
Bug #926687 [linux] Debian does not start up after upgrade to linux image
4.19.0-4-amd64
Bug reassigned from package 'linux' to 'src:linux'.
No longer marked as found in versions linux-image-4.19.0-4-amd64.
Hi Release Team,
Frank and I would like to see RC bug #926103 fixed in Debian 10. Please approve
the attached debdiff, so that I can upload the fixed package to unstable.
Thank you for your consideration.
Best,
Reinhard
diff -Nru pcsc-cyberjack-3.99.5final.sp09/debian/changelog
Your message dated Mon, 08 Apr 2019 22:04:44 +
with message-id
and subject line Bug#926103: fixed in pcsc-cyberjack 3.99.5final.sp13+dfsg-1
has caused the Debian Bug report #926103,
regarding libifd-cyberjack6: driver breaks with pcsc-lite versions >= 1.8.21
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> severity 926603 important
Bug #926603 [systemd] Debian fails to start after installation into Virtualbox
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926603:
On Mon, 8 Apr 2019 16:50:31 +0100 ana wrote:
> Thanks for the update on this. It would be a shame to drop the package
> entirely from Debian. Have had a look at the packaging on salsa and I'm
> happy to take over. I would need DM permissions on it to make uploads.
Hi Ana!
Happy to sponsor you
Control: reassign -1 src:kdepim
Hi Ivo,
On Mon, Apr 08, 2019 at 11:36:10AM +0200, Ivo De Decker wrote:
> Hi,
>
> On Sat, May 19, 2018 at 07:18:06PM +0200, Sandro Knauß wrote:
> > I now created a debdiff for kdepim. The patch depdends on the new symbol
> > that
> > was added in new
Hi Salvatore,
> CVE-2016-10745 was assigned for this issue.
Thanks for the information.
I just noticed you added CVE-2016-10745 to the tracker. I am fairly
confused, do you know why this CVE was not referenced in the tracker?
Or did you just request it?
cheers,
Hugo
--
Hugo
Processing control commands:
> reassign -1 src:kdepim
Bug #899128 [kdepim] Limit CVE-2017-17689 (EFAIL) for kmail
Bug reassigned from package 'kdepim' to 'src:kdepim'.
Ignoring request to alter found versions of bug #899128 to the same values
previously set
Ignoring request to alter fixed
Your message dated Mon, 08 Apr 2019 20:48:51 +
with message-id
and subject line Bug#917807: fixed in libcaca 0.99.beta19-2.1
has caused the Debian Bug report #917807,
regarding libcaca: CVE-2018-20544 CVE-2018-20545 CVE-2018-20546 CVE-2018-20547
CVE-2018-20548 CVE-2018-20549
to be marked as
Hi Tobias,
Thanks for tackling this. I'm a bit busy last week due to Linaro connect.
And yes as you described, telegram-cli seems still needs the header of SSL
to be compiled. I use wolfssl completely due to the license issue.
I've also tried to backport the patch for wolfssl but it seems to me
Control: found 926646 0.7.5-2
On Mon, 08 Apr 2019 at 08:43:57 -0400, Chris Lamb wrote:
> I just ACCEPTed libdmtx from NEW but the FTP team had noticed that the
> copyright stanza for debian/ is labelled GPL-2+ but its content is
> GPL-2.
This is not a regression in my NMU (which didn't touch
Processing control commands:
> found 926646 0.7.5-2
Bug #926646 [src:libdmtx] libdmtx: Incomplete debian/copyright?
Marked as found in versions libdmtx/0.7.5-2.
--
926646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Any progress on fixing this in Jessie?
Your message dated Mon, 8 Apr 2019 22:07:04 +0200
with message-id <20190408200702.wynemt75hgpc6...@debian.org>
and subject line Re: caffe-contrib: needs new upload for leveldb transition
has caused the Debian Bug report #926584,
regarding caffe-contrib: needs new upload for leveldb transition
to
Processing commands for cont...@bugs.debian.org:
> tags 926613 buster
Bug #926613 [release-notes] openssh-server: Locked out of server after
upgrading to buster.
Bug #926653 [release-notes] openssh-server: Locked out of server after
upgrading to buster.
Added tag(s) buster.
Added tag(s) buster.
Processing commands for cont...@bugs.debian.org:
> tags 926670 + upstream fixed-upstream
Bug #926670 [src:node-xterm] CVE-2019-0542
Added tag(s) fixed-upstream and upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926670:
Source: node-xterm
Severity: grave
Tags: security
Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0542
Cheers,
Moritz
Hi,
I'm another happy user of make-kpkg. ;-) I've just tested the "make bindeb-
pkg" method. I see two drawback:
- (minor) I didn't find the way to do the same thing as the "--revision"
option.
- I see a big advantage of using make-kpkg with dkms. I can keep the kernel
sources in a
Processing commands for cont...@bugs.debian.org:
> # bug is in stretch kernel, not in buster/sid
> tags 924891 = stretch
Bug #924891 [src:glibc] glibc: misc/tst-pkey fails due to cleared PKRU register
after signal in amd64 32-bit compat mode
Added tag(s) stretch; removed tag(s) sid and buster.
>
Your message dated Mon, 08 Apr 2019 17:34:45 +
with message-id
and subject line Bug#926626: fixed in libfm-qt 0.14.1-4
has caused the Debian Bug report #926626,
regarding libfm-qt6: Cannot copy dirs over smb
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> tags 919296 + buster-ignore
Bug #919296 [git-daemon-run] git-daemon-run: fails with 'warning: git-daemon:
unable to open supervise/ok: file does not exist'
Added tag(s) buster-ignore.
> thanks
Stopping processing here.
Please contact me if you
Processing commands for cont...@bugs.debian.org:
> tags 864472 + stretch buster sid
Bug #864472 [zeroc-ice-manual] zeroc-ice-manual: outdated version
Added tag(s) buster, sid, and stretch.
> severity 864472 serious
Bug #864472 [zeroc-ice-manual] zeroc-ice-manual: outdated version
Severity set to
Your message dated Mon, 08 Apr 2019 16:35:31 +
with message-id
and subject line Bug#854743: fixed in golang-github-mailru-easyjson
0.0~git20161103.0.159cdb8-1.1
has caused the Debian Bug report #854743,
regarding golang-github-mailru-easyjson: FTBFS (32-bit): constant 4294967295
overflows
Thanks for the update on this. It would be a shame to drop the package
entirely from Debian. Have had a look at the packaging on salsa and I'm
happy to take over. I would need DM permissions on it to make uploads.
Cheers,
Ana
Processing commands for cont...@bugs.debian.org:
> severity 924840 serious
Bug #924840 [src:highwayhash] highwayhash: FTBFS: dh_makeshlibs: failing due to
earlier errors
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing control commands:
> reassign -1 release-notes
Bug #926653 [openssh-server] openssh-server: Locked out of server after
upgrading to buster.
Bug reassigned from package 'openssh-server' to 'release-notes'.
Ignoring request to alter found versions of bug #926653 to the same values
Control: reassign -1 release-notes
Control: merge 926613 -1
On Mon, Apr 08, 2019 at 02:31:36PM +0100, Sam Bull wrote:
> Due to a change in how some options are handled in sshd_config, upgrading to
> buster can result in the user getting locked out of their system if the config
> is not updated.
Your message dated Mon, 8 Apr 2019 15:58:07 +0200
with message-id <20190408135807.y7k4j3sx3gwto...@topinambour.cristau.org>
and subject line Re: Bug#926647: leveldb-sharp: ABI change in libleveldb 1.20
has caused the Debian Bug report #926647,
regarding leveldb-sharp: ABI change in libleveldb 1.20
On Mon, Apr 08, 2019 at 01:38:04PM +, Ivo De Decker wrote:
> The latest version of python-trustme in unstable fails on all:
See also bug 925576. I haven't got round to looking at it yet. I hope to
investigate and fix it soon; patches also welcome.
signature.asc
Description: PGP signature
Package: openssh-server
Severity: serious
Justification: Policy 8.2
Dear Maintainer,
Due to a change in how some options are handled in sshd_config, upgrading to
buster can result in the user getting locked out of their system if the config
is not updated.
Probably the most likely cause (and
On 2019-04-08 14:50, Julien Cristau wrote:
> as documented in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=83 libleveldb's
> ABI changed incompatibly in 1.20. The 1.20-2.1 NMU changed SONAME to
> reflect that, and leveldb-sharp 1.9.1-1.2 was patched to use the new
> SONAME. However,
package: src:python-trustme
version: 0.4.0-2
severity: serious
tags: ftbfs
Hi,
The latest version of python-trustme in unstable fails on all:
https://buildd.debian.org/status/package.php?p=python-trustme
Cheers,
Ivo
Looking a bit further it seems that /var/lib/alsa/asound.state doesn't
exist.
That means that we are facing a chicken-egg problem here, the file will
never be created as the service is never started (and then never
stopped).
I don't know, if it helps, but I could manually create a working
Hi Hugo,
On Mon, Apr 08, 2019 at 10:04:35AM +0200, Hugo Lefeuvre wrote:
> > This should help confirming vulnerability in other suites.
>
> 2.7.3-1 and all later releases affected. In addition, both 2.7.3-1 and
> 2.8-1 are affected by the previous str.format issue[0].
>
> [0]
Hi Filippo,
I realised that msxpertsuite is marked for removal from testing in 7 days
while it is not yet marked for unblock. I'm just pinging this bug to avoid
that it will be removed soon.
Kind regards
Andreas.
--
http://fam-tille.de
Your message dated Mon, 08 Apr 2019 13:03:44 +
with message-id
and subject line Bug#924337: fixed in collectd 5.8.1-1.3
has caused the Debian Bug report #924337,
regarding Please reenable mqtt and varnish
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 08 Apr 2019 13:03:44 +
with message-id
and subject line Bug#924337: fixed in collectd 5.8.1-1.3
has caused the Debian Bug report #924337,
regarding collectd: disabled mqtt in build breaks upgrades on configs with mqtt
to be marked as done.
This means that you claim
Your message dated Mon, 08 Apr 2019 13:00:10 +
with message-id
and subject line Bug#908815: fixed in libdmtx 0.7.5-2.1
has caused the Debian Bug report #908815,
regarding [libdmtx0a] Structs in dmtx.h have changed without new ABI number
to be marked as done.
This means that you claim that
Source: leveldb-sharp
Version: 1.9.1-1.1
Severity: serious
Hi,
as documented in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=83 libleveldb's
ABI changed incompatibly in 1.20. The 1.20-2.1 NMU changed SONAME to
reflect that, and leveldb-sharp 1.9.1-1.2 was patched to use the new
SONAME.
Source: libdmtx
Version: 0.7.5-2.1
Severity: serious
Justication: Policy § 12.5
X-Debbugs-CC: Simon McVittie , ftpmas...@debian.org,
spwhit...@debian.org
Hi,
I just ACCEPTed libdmtx from NEW but the FTP team had noticed that the
copyright stanza for debian/ is labelled GPL-2+ but its content is
Your message dated Mon, 08 Apr 2019 12:33:38 +
with message-id
and subject line Bug#922552: fixed in diffutils 1:3.7-3
has caused the Debian Bug report #922552,
regarding diffutils: FTBFS in ppc64el (failing tests)
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> found 922552 1:3.7-2
Bug #922552 {Done: Santiago Vila } [src:diffutils]
diffutils: FTBFS in ppc64el (failing tests)
Marked as found in versions diffutils/1:3.7-2; no longer marked as fixed in
versions diffutils/1:3.7-2 and reopened.
> thanks
Based on this analysis by Frédéric Bonnard (thanks a lot!) I infer
that the "sleep 5" does not fix the problem at all, so I'm going
to disable the test completely for buster, as it's clearly buggy.
- Forwarded message from Frédéric Bonnard -
Date: Wed, 27 Feb 2019 16:48:38 +0100
From:
Processing commands for cont...@bugs.debian.org:
> unarchive 922552
Bug #922552 {Done: Santiago Vila } [src:diffutils]
diffutils: FTBFS in ppc64el (failing tests)
Unarchived Bug 922552
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
922552:
Hello!
> What I see, you do not run autopkgtest within the pipelines. In my
> understanding, this test should go to a autopkgtest. I'll add it to my TODO
> list, to write such an test for mariadb, when I'm writing autopkgtest for
> akonadi.
We do run: see
Your message dated Mon, 08 Apr 2019 10:19:49 +
with message-id
and subject line Bug#925066: fixed in lirc 0.10.1-5.2
has caused the Debian Bug report #925066,
regarding lirc: prompting due to modified conffiles which were not modified by
the user: /etc/lirc/lirc_options.conf
to be marked as
Your message dated Mon, 08 Apr 2019 10:19:49 +
with message-id
and subject line Bug#925477: fixed in lirc 0.10.1-5.2
has caused the Debian Bug report #925477,
regarding src:lirc: Uncoordinated removal of transitional packages during
freeze breaks other packages
to be marked as done.
This
Processing control commands:
> tags -1 pending
Bug #926591 [libelogind0] libelogind0: does not ship SONAME link
/lib//libelogind.so.0 -> libsystemd.so.0.25.0
Added tag(s) pending.
--
926591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926591
Debian Bug Tracking System
Contact
control: tags -1 pending
On Sun, Apr 07, 2019 at 02:12:54PM +0200, Andreas Beckmann wrote:
> I think the symlink setup is overly complicated by using both
> /lib and /usr/lib. You should either move everything to /lib
> (if that is really required for compatibility with libsystemd0)
> or just
Processing control commands:
> reassign -1 release-notes
Bug #926613 [openssh-server] openssh-server: Locked out of server after
upgrading to buster.
Bug reassigned from package 'openssh-server' to 'release-notes'.
Ignoring request to alter found versions of bug #926613 to the same values
Control: reassign -1 release-notes
On Sun, Apr 07, 2019 at 08:36:11PM +, Sam Bull wrote:
> Package: openssh-server
> Severity: serious
> Justification: Policy 8.2
Policy 8.2 is "Shared library support files", which seems to have
nothing to do with this.
> Due to a change in how some options
Hi,
On Sat, May 19, 2018 at 07:18:06PM +0200, Sandro Knauß wrote:
> I now created a debdiff for kdepim. The patch depdends on the new symbol that
> was added in new messageviewer (see #899127).
Does this bug still affect buster/sid? From the bug log and the tracker for
CVE-2017-17689, it look
Your message dated Mon, 08 Apr 2019 09:03:51 +
with message-id
and subject line Bug#926247: fixed in ruby-hangouts-chat 0.0.5-2
has caused the Debian Bug report #926247,
regarding ruby-hangouts-chat: access network during build?
to be marked as done.
This means that you claim that the
> This should help confirming vulnerability in other suites.
2.7.3-1 and all later releases affected. In addition, both 2.7.3-1 and
2.8-1 are affected by the previous str.format issue[0].
[0] https://palletsprojects.com/blog/jinja-281-released/
--
Hugo Lefeuvre (hle)|
usertag 917501 bsp-2019-04-se-gothenburg
thank you
On Sat, 30 Mar 2019 19:35:37 +0100 Giovanni Mascellani
wrote:
> I tried to work on this bug for a few hours, but I am quite puzzled:
> first of all, the issue I am experiencing right now is different from
> what is already described in the bug
Processing commands for cont...@bugs.debian.org:
> found 926602 2.8-1
Bug #926602 [src:jinja2] jinja2: CVE-2019-10906
Marked as found in versions jinja2/2.8-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926602:
Processing commands for cont...@bugs.debian.org:
> close 924188
Bug #924188 [knxd-dev] knxd-dev: missing dependency on library package - and a
separate library package in the first place
Marked Bug as done
> quit
Stopping processing here.
Please contact me if you need assistance.
--
924188:
Processing commands for cont...@bugs.debian.org:
> found 926602 2.7.3-1
Bug #926602 [src:jinja2] jinja2: CVE-2019-10906
Marked as found in versions jinja2/2.7.3-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926602:
package: tdbcmysql
version: 1.1.0-1
severity: serious
Hi,
tdbcmysql has a hard-coded (build-)dependency on "libmariadbclient18 |
libmysqlclient18 | libmysqlclient20". This is clearly wrong.
This now blocks the migration of mariadb-10.3 to testing, because
libmariadbclient18 is no longer built.
Hey,
> Can you please test again with the latest version in Debian unstable
> and verify this is fixed now?
I tested the 41873 build and now akonadi-server is able to start a fresh
installation with only madiadb-server-core. So 1:10.3.13-3 will finally make it
possible to switch back to
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package pbgenomicconsensus
Hi,
since this package went through several iterations until the autopkgtest
was finally fixed I'm hereby refreshing the metadata of the unblock
Hi,
I'm working on a potential jinja2 Debian LTS security update. Here is a
proof of concept which allows to easily reproduce the issue. This should
help confirming vulnerability in other suites.
>>> from jinja2.sandbox import SandboxedEnvironment
>>> env = SandboxedEnvironment()
>>> config =
Control: reassign -1 src:dune-istl 2.6.0-2
Control: affects -1 src:dune-pdelab
Santiago Vila writes:
> /usr/include/dune/istl/paamg/transfer.hh:97:5: error: no declaration matches
> 'void Dune::Amg::Transfer Dune::Amg::SequentialInformation>::prolongateVector(const
> Dune::Amg::AggregatesMap&,
Processing control commands:
> reassign -1 src:dune-istl 2.6.0-2
Bug #926215 [src:dune-pdelab] dune-pdelab: FTBFS with gcc 8.3
Bug reassigned from package 'src:dune-pdelab' to 'src:dune-istl'.
No longer marked as found in versions dune-pdelab/2.6~20180302-1.
Ignoring request to alter fixed
Package: libfm-qt6
Version: 0.14.1-3
Severity: grave
Justification: renders package unusable
Hi there,
Note, first bug report so please advise on improvements.
Recursive copying, (specifically directories) over a samba share does not work
as expected, it fails with "operation not supported".
71 matches
Mail list logo
