Also note 5.7.23 has not yet been released (it will be out by the end of
the month).
--
Lars
On 07/20/2018 07:34 AM, Lars Tangvald wrote:
Correction: This should be for 5.7.22, I think.
CVE List:
CVE-2018-0739
CVE-2018-2767
CVE-2018-3054
CVE-2018-3056
CVE-2018-3058
CVE-2018-3060
Your message dated Fri, 20 Jul 2018 04:19:17 +
with message-id
and subject line Bug#897811: fixed in mmc-utils 0+git20180327.b4fe0c8c-1
has caused the Debian Bug report #897811,
regarding mmc-utils: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been
Source: mysql-5.7
Version: 5.7.21-1
Severity: grave
Tags: security upstream
Hi
Details at
http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html#AppendixMSQL
Regards,
Salvatore
Your message dated Fri, 20 Jul 2018 04:04:17 +
with message-id
and subject line Bug#897700: fixed in afnix 2.8.1-2
has caused the Debian Bug report #897700,
regarding afnix: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Control: tags 892250 + pending
Dear maintainer,
I've prepared an NMU for ruby-rack-protection (versioned as 1.5.3-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
The update is just a reupload for sid/buster on what Moritz prepared
as DSA.
Regards,
Processing control commands:
> tags 892250 + pending
Bug #892250 {Done: Moritz Muehlenhoff }
[src:ruby-rack-protection] ruby-rack-protection: CVE-2018-1000119: Timing
attack in authenticity_token.rb
Added tag(s) pending.
--
892250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892250
On 07/18/2018 01:16 PM, Juhani Numminen wrote:
On Fri, 04 May 2018 12:22:31 + Matthias Klose wrote:
Package: src:linbox
Version: 1.4.2-5
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8
Package: arriero
Version: 0.6-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing 'arriero' in a minimal system
importing the module 'arriero.moo' into a
python interpreter fails with the following error:
$ python -c 'import arriero.moo'
Traceback (most
Package: python3-tower-cli
Version: 3.2.0-2
Severity: serious
User: helm...@debian.org
Usertags: python-import
Control: affects -1 + ansible-tower-cli
After installing 'python3-tower-cli' in a minimal system
importing the module 'tower_cli.resources.setting' into a
python interpreter fails with
Processing control commands:
> affects -1 + ansible-tower-cli
Bug #904117 [python3-tower-cli] python3-tower-cli: tower_cli.resources.setting
fails to import
Added indication that 904117 affects ansible-tower-cli
--
904117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904117
Debian Bug
Processing control commands:
> reopen -1
Bug #897802 {Done: Ben Hutchings } [src:linux] linux:
ftbfs with GCC-8
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in
Control: reopen -1
Control: notfixed -1 4.16.12-1
On Thu, 2018-07-19 at 18:22 +0100, Ben Hutchings wrote:
> Version: 4.16.12-1
> Control: tag -1 - experimental
>
> On Thu, 24 May 2018 13:34:37 +0900 Nobuhiro Iwamatsu
> wrote:
> > Control: tag -1 fixed-upstream
> >
> > Hi,
> >
> > They are
Your message dated Thu, 19 Jul 2018 22:35:43 +
with message-id
and subject line Bug#897810: fixed in minicoredumper 2.0.1-1
has caused the Debian Bug report #897810,
regarding minicoredumper: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 19 Jul 2018 18:24:42 -0400
with message-id <87k1pqamol@sergiodj.net>
and subject line Re: Bug#903528: python3-seqdiag fails to install with Python
3.7 as supported version
has caused the Debian Bug report #903528,
regarding python3-seqdiag fails to install with Python
Processing commands for cont...@bugs.debian.org:
> close 901835 2.7.0+dfsg-1
Bug #901835 {Done: Sebastian Reichel } [src:radare2] radare2
ftbfs on i386 and mips*
Marked as fixed in versions radare2/2.7.0+dfsg-1.
Bug #901835 {Done: Sebastian Reichel } [src:radare2] radare2
ftbfs on i386 and
Your message dated Thu, 19 Jul 2018 23:56:27 +0200
with message-id <20180719215627.ig7wyoocwl4mlots@earth.universe>
and subject line Fixed
has caused the Debian Bug report #901835,
regarding radare2 ftbfs on i386 and mips*
to be marked as done.
This means that you claim that the problem has been
Source: squid3
thanks
Trying to reassign to 3.x source packages. So BTS does not block v4
squid package uploads on this old RC issue.
Amos
This is my primary workstation, which is not very convenient to test with
at this time (I lost 3 hours of work already getting it stabilized again).
Could you perhaps use my config on one of your test systems and try to
duplicate first? If you can not duplicate, I will be willing to put some
more
Processing commands for cont...@bugs.debian.org:
> found 904112 6.3.8+dfsg-1
Bug #904112 [src:mysql-workbench] CVE-2018-2598
Marked as found in versions mysql-workbench/6.3.8+dfsg-1.
> tags 904112 + upstream
Bug #904112 [src:mysql-workbench] CVE-2018-2598
Added tag(s) upstream.
> thanks
Stopping
Samuel Thibault, le jeu. 19 juil. 2018 23:13:26 +0200, a ecrit:
> Samuel Thibault, le jeu. 19 juil. 2018 23:00:04 +0200, a ecrit:
> > What I think is still missing is "to be loaded by
> > java.util.ServiceLoader". How is that supposed to happen?
> >
> > To make it work, Fridrich Strba says in
>
Source: mysql-workbench
Severity: grave
Tags: security
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2598
Control: tags -1 moreinfo
On 11.07.2018 22:06, Sebastian Ramacher wrote:
Hi Sebastian,
> Source: pjproject
> Version: 2.7.2~dfsg-2
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> Tags: ftbfs
>
> pjproject currently fails to build:
> |
Processing control commands:
> tags -1 moreinfo
Bug #903607 [src:pjproject] pjproject: FTBFS due to d-devlibdeps errors
Added tag(s) moreinfo.
--
903607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Samuel Thibault, le jeu. 19 juil. 2018 23:00:04 +0200, a ecrit:
> What I think is still missing is "to be loaded by
> java.util.ServiceLoader". How is that supposed to happen?
>
> To make it work, Fridrich Strba says in
>
Your message dated Thu, 19 Jul 2018 21:04:27 +
with message-id
and subject line Bug#899550: fixed in ibus-table-extraphrase 1.3.9.20110826-1
has caused the Debian Bug report #899550,
regarding ibus-table-extraphrase: Invalid maintainer address
pkg-ime-de...@lists.alioth.debian.org
to be
On 2018-07-19 13:38:04 [-0700], Adam Lambert wrote:
> clamd (28514): Using fanotify permission checks may lead to deadlock;
> tainting kernel
> and shortly thereafter
This seems to become true.
> INFO: task clamd:28512 blocked for more than 120 seconds.
That is deadlock that happens.
> I
Hello,
Tiago Daitx, le jeu. 19 juil. 2018 16:46:23 -0300, a ecrit:
> The ATK was updated to use the new interface last year by Fridrich
> Strba [1,2], but it seems that upstream never updated it to include
> those patches - the bugs he reported and attached patches remain open.
>
> Might be
Your message dated Thu, 19 Jul 2018 20:50:14 +
with message-id
and subject line Bug#903455: fixed in menhir 20180530-2
has caused the Debian Bug report #903455,
regarding menhir-doc: fails to upgrade from 'stable' to 'sid' - trying to
overwrite /usr/share/doc/menhir/examples/Makefile
to be
Your message dated Thu, 19 Jul 2018 20:49:32 +
with message-id
and subject line Bug#897733: fixed in cwidget 0.5.17-11
has caused the Debian Bug report #897733,
regarding cwidget: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Thu, 19 Jul 2018 20:50:39 +
with message-id
and subject line Bug#888360: fixed in pjproject 2.7.2~dfsg-3
has caused the Debian Bug report #888360,
regarding pjproject: FTBFS with FFmpeg 4.0
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> tags 860064 -stretch
Bug #860064 {Done: Simon Kelley } [dnsmasq] [dnsmasq]
startup failue when dns-root-data installed
Bug #863896 {Done: Simon Kelley } [dnsmasq] dnsmasq:
systemd appends junk to the dnsmasq commandline
Removed tag(s) stretch.
tags 860064 -stretch
thanks
Am 19.07.2018 um 19:34 schrieb Adam D. Barratt:
>>
>> Please explain how the file was changed in stretch on that date.
>> Specifically, which version of dns-root-data was updated, from which
>> version.
>>
>> Sorry to keep going on about this, but there wasn't a
Your message dated Thu, 19 Jul 2018 20:37:59 +
with message-id
and subject line Bug#900558: fixed in libssh2 1.8.0-2
has caused the Debian Bug report #900558,
regarding libssh2-1-dev: missing dependency on zlib1g-dev
to be marked as done.
This means that you claim that the problem has been
Package: clamav-daemon
Version: 0.100.0+dfsg-0+deb9u2
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
After a recent apt upgrade, within a few minutes, my system started locking up.
A reboot would buy me about 2 minutes of working time before it locked up again.
I
Your message dated Thu, 19 Jul 2018 20:35:33 +
with message-id
and subject line Bug#897710: fixed in astyle 3.1-2
has caused the Debian Bug report #897710,
regarding astyle: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
On Tue, 17 Jul 2018 22:18:57 +0300 Juhani Numminen
wrote:
[...]
> Ah, it is the lovely -Werror.
>
> It seems that gcc-8 build succeeds when I add this line in debian/rules:
>
> export DEB_CXXFLAGS_MAINT_APPEND = -Wno-error
I think this is sensible here. I will update the package as soon as
Your message dated Thu, 19 Jul 2018 19:50:28 +
with message-id
and subject line Bug#903631: fixed in openjdk-11 11~23-1
has caused the Debian Bug report #903631,
regarding openjdk-11: FTBFS on several architectures: dh_install: Cannot find
(any matches for)
The ATK was updated to use the new interface last year by Fridrich
Strba [1,2], but it seems that upstream never updated it to include
those patches - the bugs he reported and attached patches remain open.
Might be worth to check if we can apply these to our packages.
[1]
Your message dated Thu, 19 Jul 2018 19:17:39 +
with message-id
and subject line Bug#903838: fixed in linux 4.9.110-2
has caused the Debian Bug report #903838,
regarding Unable to mount ext4 filesystem with meta_bg flag
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 19 Jul 2018 19:17:39 +
with message-id
and subject line Bug#903767: fixed in linux 4.9.110-2
has caused the Debian Bug report #903767,
regarding xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5
(linux-image-4.9.0-7-amd64)
to be marked as done.
Your message dated Thu, 19 Jul 2018 19:17:42 +
with message-id
and subject line Bug#903788: fixed in znc 1.6.5-1+deb9u1
has caused the Debian Bug report #903788,
regarding znc: CVE-2018-14056: path traversal flaw
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 19 Jul 2018 19:17:42 +
with message-id
and subject line Bug#903787: fixed in znc 1.6.5-1+deb9u1
has caused the Debian Bug report #903787,
regarding znc: CVE-2018-14055: privilege escalation to admin permission
(injection of rogue values in znc.conf)
to be marked as
Your message dated Thu, 19 Jul 2018 19:17:39 +
with message-id
and subject line Bug#903767: fixed in linux 4.9.110-2
has caused the Debian Bug report #903767,
regarding Xen domU panic on boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Thu, 19 Jul 2018 19:17:39 +
with message-id
and subject line Bug#903767: fixed in linux 4.9.110-2
has caused the Debian Bug report #903767,
regarding linux-image-4.9.0-7-amd64: general protection fault / kernel panic at
boot
to be marked as done.
This means that you claim
Your message dated Thu, 19 Jul 2018 19:17:39 +
with message-id
and subject line Bug#892250: fixed in ruby-rack-protection 1.5.3-2+deb9u1
has caused the Debian Bug report #892250,
regarding ruby-rack-protection: CVE-2018-1000119: Timing attack in
authenticity_token.rb
to be marked as done.
Your message dated Thu, 19 Jul 2018 19:17:39 +
with message-id
and subject line Bug#903767: fixed in linux 4.9.110-2
has caused the Debian Bug report #903767,
regarding Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 4.8
to be marked as done.
This means that you claim that the
Your message dated Thu, 19 Jul 2018 19:07:11 +
with message-id
and subject line Bug#888353: fixed in moc 1:2.6.0~svn-r2949-2.1
has caused the Debian Bug report #888353,
regarding moc: FTBFS with FFmpeg 4.0
to be marked as done.
This means that you claim that the problem has been dealt with.
* James Cowgill [2018-07-19 18:32 +0100]:
> Hi,
>
> On 19/07/18 18:05, Elimar Riesebieter wrote:
[...]
> My patch hasn't been uploaded to unstable yet, so you can ignore those
> logs. It's still in deferred [1,2].
>
> [1] https://ftp-master.debian.org/deferred.html
> [2]
Source: aiscm
Version: 0.515.4-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Tags: sid buster
aiscm failed to build for the ffmpeg 4.0 transition:
|
| Testsuite
Your message dated Thu, 19 Jul 2018 17:35:02 +
with message-id
and subject line Bug#900902: fixed in predict 2.2.5+dfsg.1-1
has caused the Debian Bug report #900902,
regarding predict does not trap build command errors (policy 4.6)
to be marked as done.
This means that you claim that the
Hi,
On 19/07/18 18:05, Elimar Riesebieter wrote:
> * James Cowgill [2018-07-17 11:36 +0100]:
>> On Mon, 28 May 2018 20:24:23 +0100 James Cowgill
>> wrote:
>>> On Wed, 24 Jan 2018 22:26:50 + jcowg...@debian.org wrote:
Your package FTBFS with the upcoming version 3.5 of FFmpeg.
>>>
>>>
On Thu, 2018-07-19 at 18:23 +0100, Adam D. Barratt wrote:
> On Thu, 2018-07-19 at 18:42 +0200, Christoph Martin wrote:
> > tags 860064 +stretch
> > tags 860064 +jessie
> > thanks
> >
> > Am 01.07.2018 um 15:38 schrieb Adam D. Barratt:
> > > On Sun, 2018-07-01 at 11:38 +, Martin, Christoph
Processing commands for cont...@bugs.debian.org:
> tags 898526 + ftbfs
Bug #898526 [src:h5py] h5py: FTBFS - FAIL: test_out_of_order_offsets
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
898526:
On Thu, 2018-07-19 at 18:42 +0200, Christoph Martin wrote:
> tags 860064 +stretch
> tags 860064 +jessie
> thanks
>
> Am 01.07.2018 um 15:38 schrieb Adam D. Barratt:
> > On Sun, 2018-07-01 at 11:38 +, Martin, Christoph wrote:
> > > dns-root-data had an update a week before. the file with the
Your message dated Thu, 19 Jul 2018 18:22:25 +0100
with message-id <13b7eec5e9f24fe2fbafc63dbccba21d93721619.ca...@decadent.org.uk>
and subject line Re: Bug#897802: linux: ftbfs with GCC-8
has caused the Debian Bug report #897802,
regarding linux: ftbfs with GCC-8
to be marked as done.
This means
* James Cowgill [2018-07-17 11:36 +0100]:
> Control: tags -1 pending
>
> Hi,
>
> On Mon, 28 May 2018 20:24:23 +0100 James Cowgill
> wrote:
> > Control: tags -1 patch
> >
> > Hi,
> >
> > On Wed, 24 Jan 2018 22:26:50 + jcowg...@debian.org wrote:
> > > Source: moc
> > > Version:
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:exiv2
> # 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
tags 860064 +stretch
tags 860064 +jessie
thanks
Am 01.07.2018 um 15:38 schrieb Adam D. Barratt:
> On Sun, 2018-07-01 at 11:38 +, Martin, Christoph wrote:
>> dns-root-data had an update a week before. the file with the dns root
>> keys was updated. at least the format has changed.
>
> To
Rob Browning writes:
> Rob Browning writes:
>
>> It looks like gc.test may be failing intermittently in Debian (see below).
>> Searching around I saw at least one other report of this in the #guile
>> logs from last year.
>>
>> For now, I'm wondering if if would be plausible to mark the test as
The new 1.10.1 release now builds with cython 0.28.2-4 in testing.
Tested with buster on 2018-07-19 using
https://salsa.debian.org/python-team/modules/kivy.git with the attached patch
applied to avoid a modified sources error:
dpkg-source: info: local changes detected, the modified files
Hi Raphael,
Le 18/07/2018 à 20:38, Raphael Hertzog a écrit :
> Control: severity -1 important
> Control: tag -1 + unreproducible
>
> Philippe, if you don't put Sylvestre and Axel in copy, they won't get
> your mail sent only to 902...@bugs.debian.org.
Sorry for that ! I've seen that when I sent
Hi,
On Thu, 24 May 2018 09:44:19 +0200 (CEST) Christoph Biedl
wrote:
> Package: src:php-imagick
> Version: 3.4.3~rc2-2
> Severity: serious
> User: ad...@alioth-lists.debian.net
> Usertag: alioth-lists-maintainer
>
> Dear uploader of php-imagick,
>
> as you've probably heard, Debian's alioth
Processing control commands:
> reassign -1 sicherboot
Bug #901610 [sicherboot] sicherboot,dracut: conffile problems when installing
both
Ignoring request to reassign bug #901610 to the same package
--
901610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901610
Debian Bug Tracking System
Control: reassign -1 sicherboot
Yes, the integration there is a disaster.
On Thu, 19 Jul 2018 at 13:27, Thomas Lange
wrote:
>
> IMO the bug is not in dracut, but only in sicherboot.
>
> From the control file:
> This package diverts the /etc/kernel/postinst.d/dracut file and replace it
> with
Processing control commands:
> reassign -1 sicherboot
Bug #901610 [sicherboot,dracut] sicherboot,dracut: conffile problems when
installing both
Bug reassigned from package 'sicherboot,dracut' to 'sicherboot'.
No longer marked as found in versions sicherboot/0.1.5 and dracut/047+31-2.
Ignoring
On Fri, 04 May 2018 12:23:15 + Matthias Klose wrote:
> Package: src:qpid-proton
> Version: 0.22.0-1
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-8
> /<>/proton-c/bindings/cpp/src/scalar_test.hpp:89:60: error:
> catching polymorphic type
Processing control commands:
> severity -1 important
Bug #897516 [src:cram] cram: FTBFS: tests failed
Severity set to 'important' from 'serious'
--
897516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: severity -1 important
On Thu, Jul 19, 2018 at 12:16:00PM +0200, JCF Ploemen wrote:
> The original bug reported here - partial failure of cram's test suite -
> seems to be triggered by python-coverage >= 4.5, first uploaded to
> Debian in Februari of 2018 (i.e. roughly 2 years after cram
Your message dated Thu, 19 Jul 2018 13:04:25 +
with message-id
and subject line Bug#897713: fixed in blender 2.79.b+dfsg0-3
has caused the Debian Bug report #897713,
regarding blender: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> tag -1 pending
Bug #897713 [src:blender] blender: ftbfs with GCC-8
Added tag(s) pending.
--
897713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #897713 in blender reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
Processing commands for cont...@bugs.debian.org:
> tags 904091 + ftbfs
Bug #904091 [src:arpack] arpack ftbfs on armel, mips64el, ppc64el
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
904091:
Package: src:arpack
Version: 3.6.1-1
Severity: serious
Tags: sid buster
arpack ftbfs on armel, mips64el, ppc64el. The build fails when running the
tests.
Sorry for the unexplained reopen, I expected `bts reopen` to give me
the opportunity to write something.
AFAICT the upstream bug remains open and [0] indicates that the
workaround is only temporary. Neither [1] nor any of the issues it
links to as closed seem related and [2] does show any changes
Same here. I use openrc. If I'm forced to install systemd (which loves to
fuck my RAID1) before 2 or 3 years more (since its developers prefer add
features to solve bugs in such a critical package), I will remove Debian in
all my systems and migrate do Devuan.
--
Agur: Javier Ortega Conde
Processing commands for cont...@bugs.debian.org:
> reopen 885914
Bug #885914 {Done: Gianfranco Costamagna } [s3cmd]
"RuntimeError: dictionary changed size during iteration" in s3cmd put
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared,
Processing commands for cont...@bugs.debian.org:
> forwarded 904081 https://gitlab.gnome.org/GNOME/goffice/issues/42
Bug #904081 [src:goffice] goffice fails its tests on i386
Set Bug forwarded-to-address to
'https://gitlab.gnome.org/GNOME/goffice/issues/42'.
> thanks
Stopping processing here.
Processing commands for cont...@bugs.debian.org:
> tags 904081 + upstream
Bug #904081 [src:goffice] goffice fails its tests on i386
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
904081:
IMO the bug is not in dracut, but only in sicherboot.
>From the control file:
This package diverts the /etc/kernel/postinst.d/dracut file and replace it
with its own file that calls the diverted one before running sicherboot,
as dracut does not support any form of hooks. dpkg is not entirely
Your message dated Thu, 19 Jul 2018 11:09:08 +
with message-id
and subject line Bug#885914: fixed in s3cmd 2.0.2-1
has caused the Debian Bug report #885914,
regarding "RuntimeError: dictionary changed size during iteration" in s3cmd put
to be marked as done.
This means that you claim that
this is not confirm-able and seems to be a local issue I'm still
working out where it lies. This is not however a grave bug affecting
this package version as originally suspected. If there is a bug at all
its related to reinstalling after purge and rm -rf of all config dirs
and hplip.conf not
The original bug reported here - partial failure of cram's test suite -
seems to be triggered by python-coverage >= 4.5, first uploaded to
Debian in Februari of 2018 (i.e. roughly 2 years after cram 0.7-1). With
earlier versions of coverage, cram 0.7-1 builds fine. I don't know
whether the bug is
Processing commands for cont...@bugs.debian.org:
> forwarded 897872 https://github.com/eclipse/sumo/issues/4110
Bug #897872 [src:sumo] sumo: ftbfs with GCC-8
Set Bug forwarded-to-address to 'https://github.com/eclipse/sumo/issues/4110'.
> tags 897872 fixed-upstream
Bug #897872 [src:sumo] sumo:
Package: src:goffice
Version: 0.10.41-1
Severity: serious
Tags: sid buster
make check-TESTS
make[4]: Entering directory '/<>/tests'
make[5]: Entering directory '/<>/tests'
../test-driver: line 107: 7492 Aborted "$@" > $log_file 2>&1
FAIL: test-quad
PASS: test-math
Dear maintainer,
On Fri, 04 May 2018 12:23:53 + Matthias Klose wrote:
> Package: src:systemtap
> Version: 3.1-3
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-8
> [...]
> ./includes/sys/sdt.h:119:75: error: type qualifiers ignored on cast
Package: sponsorship-requests
Severity: important
X-Debbugs-CC: sunwea...@debian.org gud...@gudjon.org
Dear Gudjon, Mike,
I noticed RC bug #903329 (https://bugs.debian.org/903329) and #903717
(https://bugs.debian.org/903717) in package "eric" in Debian that have already
triggered testing
Processing commands for cont...@bugs.debian.org:
> forwarded 897882 https://github.com/tobez/validns/issues/68
Bug #897882 [src:validns] validns: ftbfs with GCC-8
Set Bug forwarded-to-address to 'https://github.com/tobez/validns/issues/68'.
> thanks
Stopping processing here.
Please contact me if
Dear Julien,
On Thu, Jul 19, 2018 at 09:19:50AM +0200, Julien Yann Dutheil wrote:
> Will make a new release then, but I will only be able to start the process
> in the second week of August.
While this will mean that the packages will be autoremoved from testing
after 10 days I do not think that
Hi Raphael,
Raphael Hertzog wrote:
> > From my point of view this means that either another BinNMU was
> > necessary since the previous BinNMU, but was not yet triggered, or
> > something else is broken in the package.
>
> Yeah, a new binutils got uploaded multiple times in the last days.
On 19.07.2018 09:32, Raphael Hertzog wrote:
> Hi,
>
> On Wed, 18 Jul 2018, Axel Beckert wrote:
>>> Axel mentioned failed bin-nmu but it looks like the bin-nmu worked:
>>> https://buildd.debian.org/status/fetch.php?pkg=wcc=amd64=0.0.2%2Bdfsg-3%2Bb2=1531313043=0
>>
>> Sorry, I deduced that from
Hi,
On Wed, 18 Jul 2018, Axel Beckert wrote:
> > Axel mentioned failed bin-nmu but it looks like the bin-nmu worked:
> > https://buildd.debian.org/status/fetch.php?pkg=wcc=amd64=0.0.2%2Bdfsg-3%2Bb2=1531313043=0
>
> Sorry, I deduced that from "uninstallable + FTBFS".
>
> > I downgraded the bug
Your message dated Thu, 19 Jul 2018 07:04:23 +
with message-id
and subject line Bug#903224: fixed in systemd 239-6
has caused the Debian Bug report #903224,
regarding udev: Fails to upgrade
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Source: python-cryptography
Version: 1.9-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com//pyca/cryptography/pull/4342
Hi,
The following vulnerability was published for python-cryptography.
CVE-2018-10903[0]:
GCM tag forgery via truncated
Package: hplip-gui
Version: 3.16.11+repack0-3
Severity: grave
The GUI components of HPLIP are failing to start on Debian 9.5
I had some serious SNAFU/FUBAR with cups/hplip and purged all pacakges,
removed all configs, killed all processes, did an upgrade to 9.5 from 9.4,
then reinstalled cups and
94 matches
Mail list logo
