Package: phpunit-mock-object
Version: 6.1.1-1
Severity: serious
phpunit 7.2 merged phpunit-mock-object back in its tree, so there is no
need to keep an outdated and conflicting version of phpunit-mock-object
in Debian.
A removal request should follow as soon as phpunit 7.2 reaches testing,
but
Control: tags -1 patch
It's failing because the documentation build (arch:all) expects the main
build (arch:any) to have been done first. Fix:
diff -Nru libgpuarray-0.6.9/debian/rules libgpuarray-0.6.9/debian/rules
--- libgpuarray-0.6.9/debian/rules 2017-07-26 21:25:20.0 +0100
+++
Your message dated Wed, 20 Jun 2018 23:25:18 +0200
with message-id <20180620212518.3zoda26oas5gq...@mraw.org>
and subject line Re: Bug#900317: debian-installer: black screen and no answer
from X server
has caused the Debian Bug report #900317,
regarding debian-installer: black screen and no
Your message dated Wed, 20 Jun 2018 22:34:11 +
with message-id
and subject line Bug#901900: fixed in dgit 5.1
has caused the Debian Bug report #901900,
regarding dgit fails autopkgtest: true/false are no valid working-tree-encodings
to be marked as done.
This means that you claim that the
Your message dated Wed, 20 Jun 2018 16:41:27 +
with message-id
and subject line Bug#901154: fixed in msxpertsuite 5.3.3-1
has caused the Debian Bug report #901154,
regarding msxpertsuite: Does not trap errors in upstream Makefile
to be marked as done.
This means that you claim that the
Your message dated Wed, 20 Jun 2018 19:14:25 +0100
with message-id <4ff5d3fd-508f-678c-265a-f34a4e3ef...@debian.org>
and subject line Re: Bug#901784: libmypaint-1.3-0: Can't install
libmypaint-1.3-0
has caused the Debian Bug report #901784,
regarding libmypaint-1.3-0: Can't install
Package: sddm
Version: 0.17.0-1
Severity: grave
Dear Maintainer,
sddm.service will never start on usr-merged systems because of:
ExecStartPre=/bin/sh -c '[ "$(cat /etc/X11/default-display-manager
2>/dev/null)" = "/usr/bin/sddm" ]'
and
~$ cat /etc/X11/default-display-manager
/bin/sddm
please
Processing commands for cont...@bugs.debian.org:
> block 899655 by 899636
Bug #899655 [src:php-zmq] php-zmq: Invalid maintainer address
pkg-php-p...@lists.alioth.debian.org
899655 was not blocked by any bugs.
899655 was not blocking any bugs.
Added blocking bug(s) of 899655: 899636
> thanks
On Fri, May 25, 2018 at 11:05:58AM +0200, intrig...@debian.org wrote:
> Package: libgnupg-interface-perl
> Version: 0.52-9
> Severity: important
> X-Debbugs-Cc: d...@debian.org
> ci.d.n alerted us about a regression in libgnupg-interface-perl test
> suite since the upload of gnupg2/2.2.7-1:
>
Processing commands for cont...@bugs.debian.org:
> retitle 900855 [qtquickcontrols2-opensource-src] Bundles fontello.ttf which
> is not properly rebuilt from source
Bug #900855 [qtquickcontrols2-opensource-src] [qtquickcontrols2-opensource-src]
FTBFS font fontenello
Changed Bug title to
Your message dated Wed, 20 Jun 2018 23:18:05 +0200
with message-id <20180620211805.6jat52ejjhujz...@mraw.org>
and subject line Re: Bug#891964: Unable to install Debian Buster from buster
mini.iso
has caused the Debian Bug report #891964,
regarding Unable to install Debian Buster from buster
Debian Bug Tracking System writes ("Bug#901897 closed by Jonathan Nieder
(Bug#901897: fixed in git 1:2.18.0~rc2-2)"):
> git (1:2.18.0~rc2-2) unstable; urgency=low
> .
>* debian/control: Breaks: dgit (<< 5.1~) that lacks support
> for working-tree-encoding attribute (thx Ian Jackson;
>
Jonathan Nieder writes ("Re: git introduces new hazardous working-tree-encoding
attribute"):
> Ian Jackson wrote:
> > 5.1 is ready and has passed all its tests. It works fine with the git
> > in sid. I am not able to upload it right now, but this will happen
> > later today.
>
> Thanks.
>
>
Your message dated Wed, 20 Jun 2018 20:35:03 +
with message-id
and subject line Bug#901897: fixed in git 1:2.18.0~rc2-2
has caused the Debian Bug report #901897,
regarding git needs Breaks against dgit versions without working-tree-encoding
support
to be marked as done.
This means that you
Your message dated Wed, 20 Jun 2018 20:37:53 +
with message-id
and subject line Bug#901915: fixed in monero 0.12.2.0~dfsg-2
has caused the Debian Bug report #901915,
regarding monero: Incomplete debian/copyright?
to be marked as done.
This means that you claim that the problem has been dealt
On 2018-06-13 08:19:32 [+0200], To Axel Beckert wrote:
> I asked upstream what they thing about ignoring these errors because the
> perl script does so. On the other hand what about cleaning up these
> dangling symlinks?
ca-certificate maintainers: what do we do here?
[ ] we intend to figure out
Your message dated Wed, 20 Jun 2018 22:06:24 +
with message-id
and subject line Bug#899758: fixed in unbound 1.7.2-1
has caused the Debian Bug report #899758,
regarding unbound: Invalid maintainer address
pkg-dns-de...@lists.alioth.debian.org
to be marked as done.
This means that you claim
Ian Jackson wrote:
> 5.1 is ready and has passed all its tests. It works fine with the git
> in sid. I am not able to upload it right now, but this will happen
> later today.
Thanks.
$ git ls-remote git://git.chiark.greenend.org.uk/~ianmdlvl/dgit.git
fatal: Could not read from remote
Processing commands for cont...@bugs.debian.org:
> notfixed 901952 1.38
Bug #901952 [pristine-tar] xdelta: expected from file
(/tmp/pristine-tar.SljdkfANnj/recreatetarball) of length 7557120 bytes
Ignoring request to alter fixed versions of bug #901952 to the same values
previously set
>
End of
Your message dated Wed, 20 Jun 2018 19:21:32 +
with message-id
and subject line Bug#901960: fixed in speech-dispatcher 0.8.8-5
has caused the Debian Bug report #901960,
regarding speech-dispatcher can't be installed
to be marked as done.
This means that you claim that the problem has been
This is probably some useful new info:
https://salsa.debian.org/eighthave/fdroidserver/-/jobs/26316
gbp:error: Error creating fdroidserver_1.0.6.orig.tar.gz: Pristine-tar
couldn't checkout "fdroidserver_1.0.6.orig.tar.gz": mkdir
Ian Jackson writes ("Re: git introduces new hazardous working-tree-encoding
attribute"):
> Jonathan Nieder writes ("Re: git introduces new hazardous
> working-tree-encoding attribute"):
> > Happy to add a Breaks. Do you know what version of dgit will have the
> > fix?
>
> 5.1. I suggest
>
>
Package: pristine-tar
Version: 1.44
Severity: serious
In Debian/testing:
$ gbp clone https://salsa.debian.org/debian/fdroidserver.git
$ cd fdroidserver
$ rm ../fdroidserver_1.0.6.orig.tar.gz*
$ git reset --hard; git clean -fdx
$ gbp buildpackage -uc -us
gbp:info: Creating
Processing commands for cont...@bugs.debian.org:
> block 900522 by 901011
Bug #900522 {Done: Pirate Praveen } [src:gitlab] gitlab:
Security Release: 10.8.2, 10.7.5, and 10.6.6
900522 was not blocked by any bugs.
900522 was not blocking any bugs.
Added blocking bug(s) of 900522: 901011
> block
Processing commands for cont...@bugs.debian.org:
> fixed 901952 1.38
Bug #901952 [pristine-tar] xdelta: expected from file
(/tmp/pristine-tar.SljdkfANnj/recreatetarball) of length 7557120 bytes
Marked as fixed in versions pristine-tar/1.38.
>
End of message, stopping processing here.
Please
Processing commands for cont...@bugs.debian.org:
> notfound 901952 1.38
Bug #901952 [pristine-tar] xdelta: expected from file
(/tmp/pristine-tar.SljdkfANnj/recreatetarball) of length 7557120 bytes
Ignoring request to alter found versions of bug #901952 to the same values
previously set
>
End of
Your message dated Wed, 20 Jun 2018 16:04:47 +
with message-id
and subject line Bug#901884: fixed in cryptsetup 2:2.0.3-3
has caused the Debian Bug report #901884,
regarding cryptsetup-initramfs: Unbootable initrd compiled with MODULES=dep on
systems lacking AES-NI
to be marked as done.
Package: speech-dispatcher
Version: 0.8.8-4
Severity: grave
Dear Maintainer,
this is a fresh gnome-core system. Installing Gnome fails because
speech-dispatcher is not
installable:
# apt install speech-dispatcher
Reading package lists... Done
Building dependency tree
Reading state
Package: invesalius
Version: 3.1.1-3
Followup-For: Bug #901562
Running the python file wxVTKRenderWindowInteractor.py also gives a segfault:
$ python wxVTKRenderWindowInteractor.py
Segmentation fault
$
Here is a gdb backtrace:
(gdb) set args wxVTKRenderWindowInteractor.py
(gdb) run
Starting
Source: glusterfs
Version: 3.8.8-1
Severity: grave
Tags: patch security upstream
Hi,
The following vulnerability was published for glusterfs.
CVE-2018-10841[0]:
| glusterfs is vulnerable to privilege escalation on gluster server
| nodes. An authenticated gluster client via TLS could use gluster
Source: sundials
Version: 3.1.1+dfsg-1
Severity: serious
Your package hangs in the test suite in several architectures:
56/87 Test #56: test_nvector_mpi_4 Passed
0.60 sec
Start 57: test_nvector_mpi_4_1000_0
57/87 Test #57: test_nvector_mpi_4_1000_0
This line:
blockcipher="$(printf '%s' "$value" | cut -d':' -f1 | cut -d'-' -f1)"
should be:
blockcipher="$(printf '%s' "$value" | cut -d':' -f1 | cut -d'-' -f2)"
Processing control commands:
> found -1 62.0.3202.89-1
Bug #900596 [chromium-browser] [chromium-browser] unicode non free license
There is no source info for the package 'chromium-browser' at version
'62.0.3202.89-1' with architecture ''
Unable to make a source version for version
Control: found -1 62.0.3202.89-1
On Mon, 18 Jun 2018 19:24:48 +0200 Emilio Pozuelo Monfort
wrote:
> On Fri, 01 Jun 2018 21:56:51 +0200 "Bastien =?ISO-8859-1?Q?ROUCARI=C8S?="
> wrote:
> > Package: chromium-browser
> > Severity: serious
> > version: 67.0.3396.62-1
> >
> > The following file
Source: discount
Severity: grave
Tags: security
Hi,
please see
https://security-tracker.debian.org/tracker/CVE-2018-11468
https://security-tracker.debian.org/tracker/CVE-2018-11503
https://security-tracker.debian.org/tracker/CVE-2018-11504
Package: ruby-sprockets
Severity: grave
Tags: security
Hi,
please see http://www.openwall.com/lists/oss-security/2018/06/19/2
Cheers,
Moritz
Your message dated Wed, 20 Jun 2018 23:33:57 +
with message-id
and subject line Bug#899453: fixed in bluez-firmware 1.2-4
has caused the Debian Bug report #899453,
regarding bluez-firmware: Invalid maintainer address
pkg-bluetooth-maintain...@lists.alioth.debian.org
to be marked as done.
Your message dated Wed, 20 Jun 2018 23:34:24 +
with message-id
and subject line Bug#899965: fixed in inspircd 2.0.24-1.1
has caused the Debian Bug report #899965,
regarding inspircd: Invalid maintainer address
pkg-irc-maintain...@lists.alioth.debian.org
to be marked as done.
This means that
Package: fetchmail
Followup-For: Bug #768843
I too use fetchmail, and it is a vital part of my notmuch setup. Is there any
progress with this issue in Debian? I notice Adrian Bunk stated that the
problem
is fixed in the upstream 6.4 branch last august.
Do you plan to wait for a new upstream
Source: monero
Version: 0.12.2.0~dfsg-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Jonas Smedegaard
Hi,
I just ACCEPTed monero from NEW but noticed it was missing
attribution in debian/copyright for at least the gtest code
copy and what (looks like at a quick glance) some
Processing commands for cont...@bugs.debian.org:
> found 901913 3.7.0-1
Bug #901913 [ruby-sprockets] CVE-2018-3760
Marked as found in versions ruby-sprockets/3.7.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
901913:
Source: uriparser
Version: 0.8.5-1
Severity: serious
Tags: patch
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:libkml
Dear Maintainer,
liburiparser-dev contains a broken symlink:
$ ls -l /usr/lib/*/liburiparser.so*
lrwxrwxrwx 1 root root 22 May
Processing control commands:
> affects -1 src:libkml
Bug #901955 [src:uriparser] uriparser: Broken .so symlink (liburiparser.so ->
liburiparser.so.1.0.20)
Added indication that 901955 affects src:libkml
--
901955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901955
Debian Bug Tracking
Processing commands for cont...@bugs.debian.org:
> affects 842023 -node-jquery
Bug #842023 [node-jsdom] update jsdom to a version that does not require
contextify
Bug #846718 [node-jsdom] node-jquery-textcomplete: FTBFS: build-dependency not
installable: node-jquery
Removed indication that
Le 20/06/2018 à 00:21, Guilhem Moulin a écrit :
> On Tue, 19 Jun 2018 at 23:52:45 +0200, Guilhem Moulin wrote:
>> Sorry, I meant between your backup initrd.img (presumably also compiled
>> with MODULES=dep) and the new, broken one.
> Alternatively, if you don't have this initrd around anymore, are
Hi.
Thanks for your help and sorry for the delay in answering.
I found the problem while gathering info for you:
# apt-cache policy
Package files:
100 /var/lib/dpkg/status
release a=now
1 http://deb.debian.org/debian experimental/main amd64 Packages
release
Hi Jonas,
> I am unaware of any ambiguity now (after adding the gtest part),
> however, and consider this bugreport solved.
Thanks. It /might/ have been that this had a different author ("Shen"
rings a bell) but if the Copyright is the same then I'm happy. :)
Regards,
--
,''`.
:
On Wed, 20 Jun 2018 at 06:42:03 +, 901...@chiru.no wrote:
> This line:
> blockcipher="$(printf '%s' "$value" | cut -d':' -f1 | cut -d'-' -f1)"
> should be:
> blockcipher="$(printf '%s' "$value" | cut -d':' -f1 | cut -d'-' -f2)"
That's indeed the regression, causing modules required for the
Your message dated Wed, 20 Jun 2018 15:35:44 +
with message-id
and subject line Bug#899612: fixed in mongo-cxx-driver-legacy 1.1.3-1
has caused the Debian Bug report #899612,
regarding mongo-cxx-driver-legacy: Invalid maintainer address
pkg-mongodb-maintain...@lists.alioth.debian.org
to be
Quoting Chris Lamb (2018-06-20 16:33:17)
>> I fail to locate any omission under src/ringct/. If you mean the
>> references to Sarang Noether then I believe that is […]
>
> I'm afraid I can't recall exactly what it was but if there is any
> ambiguity whatsoever please clarify this in
On Tue, 19 Jun 2018 18:28:13 -0700 Jonathan Nieder
wrote:
> By the way, is there a way to trigger these autopkgtests automatically
> with git from experimental as well? That way, I'd get earlier notice
> about these issues.
Not yet. It's on my list to add experimental support in ci.d.n, but it
Hi Jonas,
> gtest code copy I simply forgot to list
Thanks.
> I fail to locate any omission under src/ringct/. If you mean the
> references to Sarang Noether then I believe that is […]
I'm afraid I can't recall exactly what it was but if there is any
ambiguity whatsoever please clarify this
Package: nvidia-driver
Version: 390.59-1
Followup-For: Bug #901919
Control tag -1 confirmed
I can confirm this issue which occured with 4.16.16-1, but not with 4.16.12-1
my relevant part of kern.log
Jun 13 16:32:53 bagend kernel: [6.992399] [ cut here
]
Jun 13
Package: src:linux
Version: 4.16.16-1
Severity: critical
Justification: breaks the whole system
Dear debian kernel maintainers
after switching to version 4.16.16-1 of linux-image-4.16.0-2-amd64 my system
does not boot anymore. I obtain a kernel BUG message in syslog in usercopy.c.
Reverting to
Dear maintainers,
please find below the "kernel BUG" message in syslog .
In order to reboot i had to downgrade to testing (= 4.16.12-1 ) the
following packages :
linux-headers-4.16.0-2-common
linux-image-4.16.0-2-amd64
linux-headers-4.16.0-2-amd64
and to run
dpkg-reconfigure nvidia-kernel-dkms
Package: nvidia-driver
Version: 390.48-3
Severity: grave
Justification: renders package unusable
After upgrade to the Linux kernel 4.16.16-1, I get a black screen.
-- Package-specific info:
uname -a:
Linux zira 4.16.0-2-amd64 #1 SMP Debian 4.16.16-1 (2018-06-19) x86_64 GNU/Linux
/proc/version:
Quoting Chris Lamb (2018-06-20 10:07:57)
> I just ACCEPTed monero from NEW but noticed it was missing attribution
> in debian/copyright for at least the gtest code copy and what (looks
> like at a quick glance) some imported code under src/ringct/.
Thanks, for accepting but also for spotting
Hi. Thanks for your prompt attention. Again, sorry for my
contribution to an annoying situation.
Jonathan Nieder writes ("Re: git introduces new hazardous working-tree-encoding
attribute"):
> Ian Jackson wrote:
> > Subject: git introduces new hazardous working-tree-encoding attribute
>
> This
Control: found -1 + 4.4
This problem was not introduced in dgit 5.0; dgit has not changed in
this respect since the gitattributes tests were added. The regression
is triggered by a change in git, as discussed in #901900 and its
parent #901897.
Ian Jackson writes ("grep-excuses"):
> dgit (4.4 to
Your message dated Wed, 20 Jun 2018 11:20:02 +
with message-id
and subject line Bug#899517: fixed in ganeti-instance-debootstrap 0.16-6
has caused the Debian Bug report #899517,
regarding ganeti-instance-debootstrap: Invalid maintainer address
pkg-ganeti-de...@lists.alioth.debian.org
to be
Processing control commands:
> retitle -1 nvidia-driver: black screen with the latest Linux kernel - general
> protection fault
Bug #901919 [nvidia-driver] nvidia-driver: black screen with the latest Linux
kernel
Changed Bug title to 'nvidia-driver: black screen with the latest Linux kernel
-
Control: retitle -1 nvidia-driver: black screen with the latest Linux kernel -
general protection fault
The kernel log was not included. It ends with:
Jun 20 11:46:59 zira kernel: [ 17.930908] usercopy: Kernel memory exposure
attempt detected from SLUB object 'nvidia_stack_cache' (offset
Your message dated Wed, 20 Jun 2018 11:51:09 +
with message-id
and subject line Bug#899614: fixed in mongo-tools 3.4.14-3
has caused the Debian Bug report #899614,
regarding mongo-tools: Invalid maintainer address
pkg-mongodb-maintain...@lists.alioth.debian.org
to be marked as done.
This
Your message dated Wed, 20 Jun 2018 12:07:53 +
with message-id
and subject line Bug#901108: fixed in grr 3.1.0.2+dfsg-6
has caused the Debian Bug report #901108,
regarding grr: FTBFS when built with dpkg-buildpackage -A
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 20 Jun 2018 12:07:54 +
with message-id
and subject line Bug#888957: fixed in linuxbrew-wrapper 20180209-1
has caused the Debian Bug report #888957,
regarding linuxbrew-wrapper should go to contrib: It is an installer for
linuxbrew
to be marked as done.
This means
65 matches
Mail list logo
