Your message dated Tue, 28 May 2019 05:18:28 +
with message-id
and subject line Bug#929618: fixed in t-digest 1:3.0-2
has caused the Debian Bug report #929618,
regarding t-digest: latest-debian-changelog-entry-reuses-existing-version
to be marked as done.
This means that you claim that the
On Sun, May 26, 2019 at 08:58:29PM +0200, Moritz Mühlenhoff wrote:
> On Fri, May 24, 2019 at 09:19:00AM +0100, Chris Lamb wrote:
> > tags 929283 + patch
> > thanks
> >
> > Hi Moritz,
> >
> > > > > zookeeper: CVE-2019-0201: information disclosure vulnerability
> > > >
> > > > Happy to prepare an
Source: docker.io
Version: 18.09.1+dfsg1-7
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/docker/docker/pull/39252
Control: found -1 18.09.1+dfsg1-7~deb10u1
Control: found -1 18.09.5+dfsg1-1
Hi,
The following vulnerability was published
Processing control commands:
> found -1 18.09.1+dfsg1-7~deb10u1
Bug #929662 [src:docker.io] docker.io: CVE-2018-15664
Marked as found in versions docker.io/18.09.1+dfsg1-7~deb10u1.
> found -1 18.09.5+dfsg1-1
Bug #929662 [src:docker.io] docker.io: CVE-2018-15664
Marked as found in versions
Processing commands for cont...@bugs.debian.org:
> fixed 927153 2.13.1-2
Bug #927153 {Done: Hideki Yamane } [fontconfig]
fontconfig: fc-cache with -y option is broken
Marked as fixed in versions fontconfig/2.13.1-2.
>
End of message, stopping processing here.
Please contact me if you need
Control: forcemerge 921267 -1
Am 28.05.19 um 00:59 schrieb Kathryn Tolsen:
> Package: systemd
> Version: 241-3
> Severity: Serious
>
> All systemd services are failing to start, best guess is, this is
> related to:
>
> https://github.com/systemd/systemd/issues/11810
This is already fixed in
Processing control commands:
> forcemerge 921267 -1
Bug #921267 {Done: Michael Biebl } [systemd] systemd fails to
reach shutdown.target when rebooting or shutting down the system after resuming
from suspend
Bug #929655 [systemd] Obscure "Failed to set invocation ID for unit: File
exists" error
Package: systemd
Version: 241-3
Severity: Serious
All systemd services are failing to start, best guess is, this is related
to:
https://github.com/systemd/systemd/issues/11810
Your message dated Tue, 28 May 2019 07:38:28 +0900
with message-id <20190528073828.03bc966461bb40edfe58f...@iijmio-mail.jp>
and subject line
has caused the Debian Bug report #927153,
regarding fontconfig: fc-cache with -y option is broken
to be marked as done.
This means that you claim that the
/usr/share/initramfs-tools/hooks/plymouth failed with return 134
Message-Id: <20190528073815.2ba8e2fb13cf10d0fb4bc...@iijmio-mail.jp>
In-Reply-To: <20190520133004.gb2...@zira.vinc17.org>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain;
On 5/27/19 2:45 AM, Nico Schlömer wrote:
>> I was going to go ahead and do a +really upload with this fix either today
>> or this weekend.
>
> This is getting rather urgent now. Do you need any help?
>
No, I just was waiting for the response on #929108. I'm traveling with
poor connection
IvyBridge / Haswell systems
Message-Id: <20190528065209.ab9aed4d6eabe80a6b398...@iijmio-mail.jp>
In-Reply-To: <20190528064028.dec9969527111b97d555d...@iijmio-mail.jp>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Processing control commands:
> tags -1 +fixed-upstream
Bug #92 [src:linux] linux-image-4.19.0-4-amd64: [regression] No graphics on
some IvyBridge / Haswell systems
Bug #925967 [src:linux] linux-image-4.19.0-4-amd64: [regression] No graphics on
some IvyBridge / Haswell systems
Bug #926193
control: tags -1 +fixed-upstream
Hi,
It seems that fixed in 4.9.38 as below.
> commit 2bc7ce32eb21b094b3ae3e489017fabfe72b4dda
> Author: Dave Airlie
> Date: Wed Apr 24 10:47:56 2019 +1000
>
> Revert "drm/i915/fbdev: Actually configure untiled displays"
>
> commit
CVE-2019-12214 does not affect buster and stretch.
Jessie should be double checked because an older
version is used there.
Anton
Am So., 26. Mai 2019 um 22:01 Uhr schrieb Anton Gladky :
>
> Hi Moritz,
>
> thanks for the reporting. As far as I see, there is still
> no available fix from upstream.
Package: src:openjdk-8
Version: 8u212-b01-1
Severity: serious
openjdk-8 is staying in unstable. It is used to prepare updates for
stable-security, and to bootstrap kotlin.
Your message dated Mon, 27 May 2019 19:47:05 +
with message-id
and subject line Bug#929333: Removed package(s) from unstable
has caused the Debian Bug report #918171,
regarding Broken with Thunderbird 60
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Hi Andreas,
On Mon, May 27, 2019 at 03:23:45PM +0200, Andreas Beckmann wrote:
> On 2019-05-27 11:23, Gennaro Oliva wrote:
> > I have prepared an updated version of the package available here:
> >
> > https://people.debian.org/~oliva/slurm-llnl-16.05.9-1+deb9u4/
>
> I can confirm that it builds
Your message dated Mon, 27 May 2019 19:38:29 +
with message-id
and subject line Bug#927988: Removed package(s) from unstable
has caused the Debian Bug report #908941,
regarding python3-rpyc: did not build
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 27 May 2019 19:38:29 +
with message-id
and subject line Bug#927988: Removed package(s) from unstable
has caused the Debian Bug report #908941,
regarding rpyc FTBFS: test_registry.TestUdpRegistry failures
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:zookeeper
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Am 27.05.19 um 19:04 schrieb Balint Reczey:
> Hi Tobias,
>
> Thank you for taking care of packages with open security issues, but
> I'm wondering why you chose to do an immediate NMU.
> I planed uploading 2.6.9-1 today following the usual process we agreed
> on with the Security Team and I
Your message dated Mon, 27 May 2019 17:33:57 +
with message-id
and subject line Bug#924029: fixed in poppler 0.71.0-4.1
has caused the Debian Bug report #924029,
regarding evince: Crashes when opening a PDF
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 27 May 2019 17:33:57 +
with message-id
and subject line Bug#924029: fixed in poppler 0.71.0-4.1
has caused the Debian Bug report #924029,
regarding libevdocument3-4: Evince passes NULL pointer to poppler_date_parse
to be marked as done.
This means that you claim that
Your message dated Mon, 27 May 2019 17:33:57 +
with message-id
and subject line Bug#924029: fixed in poppler 0.71.0-4.1
has caused the Debian Bug report #924029,
regarding evince crashes in poppler on unusual pdf document
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 27 May 2019 17:33:57 +
with message-id
and subject line Bug#924029: fixed in poppler 0.71.0-4.1
has caused the Debian Bug report #924029,
regarding libevdocument3-4: Evince passes NULL pointer to poppler_date_parse
to be marked as done.
This means that you claim that
Hi Tobias,
Thank you for taking care of packages with open security issues, but
I'm wondering why you chose to do an immediate NMU.
I planed uploading 2.6.9-1 today following the usual process we agreed
on with the Security Team and I believe fixing this bug after 4 days
it was opened is not an
Hi,
Kurt Kremitzki writes:
> On 5/17/19 4:14 AM, Ansgar wrote:
>> I tried and with this line removed gmsh builds again. I'll ask the
>> release team about t-p-u or reverting in unstable.
[...]
> Sorry for not addressing this sooner such that you needed to spend time
> looking at it. I was going
Your message dated Mon, 27 May 2019 14:42:22 +
with message-id
and subject line Bug#929446: fixed in wireshark 2.6.8-1.1
has caused the Debian Bug report #929446,
regarding wireshark: CVE-2019-12295
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
On 2019-05-27 11:23, Gennaro Oliva wrote:
> I have prepared an updated version of the package available here:
>
> https://people.debian.org/~oliva/slurm-llnl-16.05.9-1+deb9u4/
I can confirm that it builds locally in a pbuilder stretch/i386
environment :-)
Andreas
On Mon, May 27, 2019 at 02:18:54PM +0200, Ulrike Uhlig wrote:
> It would be useful to know with which statements or assumptions you do
> not agree with and why - so that the discussion may become more
> productive & helpful.
"cannot be maintained in stable". I think this can at least be tried.
Your message dated Mon, 27 May 2019 12:33:44 +
with message-id
and subject line Bug#925173: fixed in ltsp 5.18.12-2
has caused the Debian Bug report #925173,
regarding ltsp: codename detection code not useful for stable
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 27 May 2019 12:33:35 +
with message-id
and subject line Bug#928986: fixed in cloudcompare 2.10.1-2
has caused the Debian Bug report #928986,
regarding CloudCompare: error while loading shared libraries: libQCC_IO_LIB.so:
to be marked as done.
This means that you claim
Hi Holger,
On 27.05.19 11:56, Holger Levsen wrote:
> i'm not sure I agree with the assumptions from this bug report but
It would be useful to know with which statements or assumptions you do
not agree with and why - so that the discussion may become more
productive & helpful.
> anyway, i just
Processing commands for cont...@bugs.debian.org:
> forwarded 929597
> https://sourceforge.net/p/freeimage/discussion/36111/thread/e06734bed5/
Bug #929597 [src:freeimage] CVE-2019-12211 CVE-2019-12212 CVE-2019-12213
CVE-2019-12214
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> found 929597 3.18.0+ds2-1
Bug #929597 [src:freeimage] CVE-2019-12211 CVE-2019-12212 CVE-2019-12213
CVE-2019-12214
Marked as found in versions freeimage/3.18.0+ds2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Processing commands for cont...@bugs.debian.org:
> tags 929597 + upstream
Bug #929597 [src:freeimage] CVE-2019-12211 CVE-2019-12212 CVE-2019-12213
CVE-2019-12214
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
929597:
On 5/25/19 6:49 PM, Thomas Lamprecht wrote:
> Package: iptables
> Version: 1.8.2-4
> Severity: grave
> File: /usr/sbin/xtables-nft-multi
> Justification: renders package unusable by segfaulting on usage
>
> Reproducer:
> # cat simple-segv-table
> *filter
> :NEW-OUTPUT - [0:0]
> -A OUTPUT -j
Thanks for the patch, I managed to aplpy to the server, now I will test it.
Given the seriousness of the bug, I believe we should release a fixed
version of the package.
Changing the iptables alternative to use the legacy binaries causes the
segfault not to occur.
hi,
i'm not sure I agree with the assumptions from this bug report but
anyway, i just want to point out that 'maintaining tbl in stretch via
stretch-backports' doesnt work because tbl is not in buster and thus, if
this bug gets retitled to 'tbl should not be part of bullseye',
maintaining tbl in
Source: t-digest
Version: 1:3.0-1
Severity: serious
W: libt-digest-java: latest-debian-changelog-entry-reuses-existing-version
1:3.0-1 == 3.0-1 (last used: Tue, 14 Oct 2014 10:44:34 +0200)
N:
N:The latest changelog entry has a version that matches one used in the
N:specified previous
Source: d3-format
Version: 1:1.0.2-1
Severity: serious
W: libjs-d3-format: latest-debian-changelog-entry-reuses-existing-version
1:1.0.2-1 == 1.0.2-1 (last used: Sat, 19 Nov 2016 04:00:20 +0100)
N:
N:The latest changelog entry has a version that matches one used in the
N:specified
Hi Andreas,
On Sun, May 26, 2019 at 10:31:14PM +0200, Andreas Beckmann wrote:
> the stretch update of slurm-llnl FTBFS on the 32-bit architectures:
thank you very much for filing this bug report.
I have prepared an updated version of the package available here:
Hi Moritz,
> > > Chris, thanks for your proposal to update Stretch, I very much
> > > appreciate it.
[…]
> This doesn't warrant a DSA, feel free to fix it via a point release instead.
Sure thing. Proposed in #929613.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'`
Source: libconvert-units-perl
Version: 1:0.43-2
Severity: serious
W: libconvert-units-perl: latest-debian-changelog-entry-reuses-existing-version
1:0.43-2 == 0.43-2 (last used: Mon, 17 Dec 2001 22:33:30 +0100)
N:
N:The latest changelog entry has a version that matches one used in the
N:
Same problem here.
Is it not possible to have an update for the stable release?
What is the procedure for applying the proposed patch?
Processing control commands:
> close -1 1:0.4.3-18
Bug #929614 [naist-jdic,naist-jdic-utf8] naist-jdic: 0.4.3-4 (lenny) was
overwritten by 1:0.4.3-4 (jessie) on archive.debian.org
Marked as fixed in versions naist-jdic/1:0.4.3-18.
Bug #929614 [naist-jdic,naist-jdic-utf8] naist-jdic: 0.4.3-4
Package: naist-jdic,naist-jdic-utf8
Version: 0.4.3-4
Severity: grave
User: debian...@lists.debian.org
Usertags: piuparts
Control: close -1 1:0.4.3-18
naist-jdic/lenny is no longer installable from archive.debian.org
(noticed in a piuparts test)
Get:1 http://archive.debian.org lenny/main
On Sun, May 26, 2019 at 02:27:34PM -0700, Vagrant Cascadian wrote:
> Apparently, it's already impacting buster:
>
> $ sudo ltsp-build-client
> NOTE: adding default dist and components to security mirror:
> http://security.debian.org/ 10.0/updates main
> ERROR: invalid distribution: 10.0
iirc,
Your message dated Mon, 27 May 2019 07:33:40 +
with message-id
and subject line Bug#923930: fixed in heimdal 7.5.0+dfsg-3
has caused the Debian Bug report #923930,
regarding FTBFS: FAIL test_chain (exit status: 1)
to be marked as done.
This means that you claim that the problem has been
51 matches
Mail list logo
