Processing commands for cont...@bugs.debian.org:
> reassign 926392 libregexp-pattern-license-perl
Bug #926392 [licensecheck] licensecheck chokes on long lines
Bug reassigned from package 'licensecheck' to 'libregexp-pattern-license-perl'.
No longer marked as found in versions 3.0.36.
Ignoring requ
For me there are still issues with 3.16.0-8-amd64 after updating to
3.16.64-2, so I have to still run some machines on 3.16.0-7 to have them
working.
After boot dmesg gives output like attached.
Software stack which has a problem with this is postfix/rspamd/redis.
Redis does consume a lot of CPU
Processing control commands:
> tags -1 +patch +pending
Bug #927263 [riece] riece: unusable on Emacs 26
Ignoring request to alter tags of bug #927263 to the same tags previously set
Bug #927263 [riece] riece: unusable on Emacs 26
Added tag(s) pending.
--
927263: https://bugs.debian.org/cgi-bin/bu
control: tags -1 +patch +pending
Hi,
Thanks for your patch, I'll test and upload in this weekend holiday.
--
Hideki Yamane
On Thu, Apr 18, 2019 at 09:32:06PM +0200, Hans-Christoph Steiner wrote:
>
> One possibility would be including libsparse as a patch, it doesn't
> change a lot:
> https://android.googlesource.com/platform/system/core/+log/master/libsparse
>
> But it depends on Android's libbase and libz-host.
Thi
Your message dated Fri, 19 Apr 2019 02:35:27 +
with message-id
and subject line Bug#927301: fixed in gpustat 0.5.0-3
has caused the Debian Bug report #927301,
regarding missing depends on python3-pkg-resources
to be marked as done.
This means that you claim that the problem has been dealt wit
On 2019-04-16 19:43 +, Santiago Vila wrote:
> Package: src:caveconverter
> Version: 0~20170114-4
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> I tried to build this package in buster but it failed:
>
> jh_build: Compatibility levels before 9 are deprecated (level 7 in use)
> jh_
Processing commands for cont...@bugs.debian.org:
> forcemerge 927353 927354 927359
Bug #927353 [src:htslib] src:htslib: Please stop building on any-i386
Bug #927354 [src:htslib] libhts2: Please stop building on any-i386
Bug #927359 [src:htslib] tabix: Please stop building on any-i386
Merged 927353
Processing commands for cont...@bugs.debian.org:
> reassign 927354 src:htslib
Bug #927354 [libhts2] libhts2: Please stop building on any-i386
Bug reassigned from package 'libhts2' to 'src:htslib'.
No longer marked as found in versions htslib/1.9-10.
Ignoring request to alter fixed versions of bug
Processing commands for cont...@bugs.debian.org:
> retitle 927353 src:htslib: Please stop building on any-i386
Bug #927353 [src:htslib] libhts-dev: Please stop building on any-i386
Changed Bug title to 'src:htslib: Please stop building on any-i386' from
'libhts-dev: Please stop building on any-i3
Processing commands for cont...@bugs.debian.org:
> reassign 927359 src:htslib
Bug #927359 [tabix] tabix: Please stop building on any-i386
Bug reassigned from package 'tabix' to 'src:htslib'.
No longer marked as found in versions htslib/1.9-10.
Ignoring request to alter fixed versions of bug #92735
Processing commands for cont...@bugs.debian.org:
> # second try
> reassign 927353 src:htslib
Bug #927353 [libhts-dev] libhts-dev: Please stop building on any-i386
Bug reassigned from package 'libhts-dev' to 'src:htslib'.
No longer marked as found in versions htslib/1.9-10.
Ignoring request to alte
Processing commands for cont...@bugs.debian.org:
> merge 927353 927354 927359
Bug #927353 [libhts-dev] libhts-dev: Please stop building on any-i386
Unable to merge bugs because:
package of #927359 is 'tabix' not 'libhts-dev'
package of #927354 is 'libhts2' not 'libhts-dev'
Failed to merge 927353:
Your message dated Fri, 19 Apr 2019 00:33:26 +0200
with message-id <20190418223323.l455nxwmqs6mb...@debian.org>
and subject line Re: augustus: Please stop building on any-i386
has caused the Debian Bug report #927357,
regarding samtools: Please stop building on any-i386
to be marked as done.
This
merge 927353 927354 927359
retitle 927353 src:htslib: Please stop building on any-i386
thanks
Hi James,
On Thu, Apr 18, 2019 at 01:26:22PM +0100, James Clarke wrote:
> Package: libhts-dev
> Version: 1.9-10
> Severity: serious
>
> Hi,
> This package uses htslib, which is no longer supported on an
Your message dated Fri, 19 Apr 2019 00:33:26 +0200
with message-id <20190418223323.l455nxwmqs6mb...@debian.org>
and subject line Re: augustus: Please stop building on any-i386
has caused the Debian Bug report #927358,
regarding segemehl: Please stop building on any-i386
to be marked as done.
This
Your message dated Fri, 19 Apr 2019 00:33:26 +0200
with message-id <20190418223323.l455nxwmqs6mb...@debian.org>
and subject line Re: augustus: Please stop building on any-i386
has caused the Debian Bug report #927351,
regarding augustus: Please stop building on any-i386
to be marked as done.
This
Your message dated Fri, 19 Apr 2019 00:33:26 +0200
with message-id <20190418223323.l455nxwmqs6mb...@debian.org>
and subject line Re: augustus: Please stop building on any-i386
has caused the Debian Bug report #927355,
regarding nanopolish: Please stop building on any-i386
to be marked as done.
Thi
Your message dated Fri, 19 Apr 2019 00:33:26 +0200
with message-id <20190418223323.l455nxwmqs6mb...@debian.org>
and subject line Re: augustus: Please stop building on any-i386
has caused the Debian Bug report #927356,
regarding qtltools: Please stop building on any-i386
to be marked as done.
This
Your message dated Fri, 19 Apr 2019 00:33:26 +0200
with message-id <20190418223323.l455nxwmqs6mb...@debian.org>
and subject line Re: augustus: Please stop building on any-i386
has caused the Debian Bug report #927352,
regarding delly: Please stop building on any-i386
to be marked as done.
This mea
Processing control commands:
> severity -1 grave
Bug #927263 [riece] riece: unusable on Emacs 26
Severity set to 'grave' from 'serious'
--
927263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: severity -1 grave
Processing control commands:
> retitle -1 riece: unusable on Emacs 26
Bug #927263 [riece] riece: error on (wrong-number-of-arguments (1 . 1) 2)
Changed Bug title to 'riece: unusable on Emacs 26' from 'riece: error on
(wrong-number-of-arguments (1 . 1) 2)'.
> severity -1 serious
Bug #927263 [riece
Processing control commands:
> tags -1 patch
Bug #918578 [gosa] gosa: GOsa web interface missing password field
Added tag(s) patch.
--
918578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 patch
Hi all,
On Fr 05 Apr 2019 00:31:03 CEST, Wolfgang Schweer wrote:
Ping this bug again to keep the chance to fix it.
Wolfgang
Patch attached. Sorry for the dramatic pause before sitting down and
finding a fix. Please test.
Mike
--
DAS-NETZWERKTEAM
c\o Technik- und
Your message dated Thu, 18 Apr 2019 16:48:29 +
with message-id
and subject line Bug#926728: fixed in arptables 0.0.4+snapshot20181021-4
has caused the Debian Bug report #926758,
regarding Removing the package breaks the alternative on usr-merge system
to be marked as done.
This means that you
Your message dated Thu, 18 Apr 2019 21:04:26 +
with message-id
and subject line Bug#927385: fixed in jquery 3.3.1~dfsg-2
has caused the Debian Bug report #927385,
regarding jquery: Prototype Pollution vulnerability
to be marked as done.
This means that you claim that the problem has been deal
Control: tag -1 pending
Hello,
Bug #927385 in jquery 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:
https://salsa.debian.org/js-team/jquery/commit/b6fb904f1d1818c03841425de36d037fc0ed2
Processing control commands:
> tag -1 pending
Bug #927385 [src:jquery] jquery: Prototype Pollution vulnerability
Added tag(s) pending.
--
927385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: invesalius
Version: 3.1.2-2
Severity: grave
Dear Maintainer,
When attempting to run InVesalius for the first time, I am presented
with the first-run language selector followed by the splash screen,
but no window ever appears and the invesalius3 process remains active
until manually t
Source: jquery
Version: 3.3.1~dfsg-1
Severity: grave
Tags: patch security upstream fixed-upstream
Justification: user security hole
Control: found -1 3.1.1-2
Hi
A prototype pollution vulnerability (so far no CVE) has been fixed in
jQuery 3.4.0:
https://blog.jquery.com/2019/04/10/jquery-3-4-0-rel
Your message dated Thu, 18 Apr 2019 19:48:43 +
with message-id
and subject line Bug#883872: fixed in bitlbee 3.6-1.1
has caused the Debian Bug report #883872,
regarding bitlbee: Extremely incomplete d/copyright
to be marked as done.
This means that you claim that the problem has been dealt wi
Processing control commands:
> found -1 3.1.1-2
Bug #927385 [src:jquery] jquery: Prototype Pollution vulnerability
Marked as found in versions jquery/3.1.1-2.
--
927385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problem
One possibility would be including libsparse as a patch, it doesn't
change a lot:
https://android.googlesource.com/platform/system/core/+log/master/libsparse
But it depends on Android's libbase and libz-host.
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:phpldapadmin
> # 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.or
Even though buster's e2fsprogs includes support for android_sparse in
the source code, it requires linking against libsparse, which is in
android-libsparse. That means making e2fsprogs Build-Depend on
android-libsparse-dev.
This is pending since
https://salsa.debian.org/mariadb-team/mariadb-10.3/commit/5046bb4fc2a8ff47a1cf139eba468286a29fcf13
Should be fixed when 10.3.14-1 is uploaded.
Control: reassign 924591 e2fsprogs 1.44.5-1
Looks like the bug is because buster's e2fsprogs is not building with
the android_sparse option, even though it is included in the source code.
$ strace -f -e trace=execve -s4000 /usr/bin/fastboot
format:ext4:0x180b0 userdata
execve("/usr/bin/fast
Processing control commands:
> reassign 924591 e2fsprogs 1.44.5-1
Bug #924591 [fastboot] fastboot format:ext4 misses
/usr/lib/android-sdk/platform-tools/mke2fs
Bug reassigned from package 'fastboot' to 'e2fsprogs'.
No longer marked as found in versions
android-platform-system-core/1:8.1.0+r23-4.
Processing control commands:
> severity -1 normal
Bug #927275 [gnome-shell] gnome-shell - Intel GPU - monitors.xml is ignored and
settings are not applied after suspend/reboot
Severity set to 'normal' from 'serious'
> reassign -1 libmutter-3-0 3.30.2-6
Bug #927275 [gnome-shell] gnome-shell - Inte
Control: severity -1 normal
Control: reassign -1 libmutter-3-0 3.30.2-6
Control: tags -1 + moreinfo
Control: affects -1 gnome-shell
On Wed, 17 Apr 2019 at 10:32:25 +0200, - wrote:
> Severity: serious
This is an annoying bug, but is not so serious that removing GNOME from
Debian would be better th
Hi Filippo,
msxpertsuite is about to be removed from unstable. Do you need
help?
Kind regards
Andreas.
--
http://fam-tille.de
On Tue, 2 Apr 2019 09:41:25 +0300 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?=
wrote:
> OK, so current MariaDB 10.3.13 we have in Debian contains MariaDB
> Connector C 3.0.9
>
> mariadb-10.3$ grep -rF 'SET(CPACK_PACKAGE_VERSION_' libmariadb/CMakeLists.txt
> SET(CPACK_PACKAGE_VERSION_MAJOR 3)
> SET(CPACK_
Your message dated Thu, 18 Apr 2019 17:32:17 +
with message-id
and subject line Bug#913641: fixed in libreoffice 1:5.2.7-1+deb9u7
has caused the Debian Bug report #913641,
regarding libreoffice-report-builder: report builder reports fail to run after
S8195874 in OpenJDK
to be marked as done.
Your message dated Thu, 18 Apr 2019 17:32:08 +
with message-id
and subject line Bug#925257: fixed in ghostscript 9.26a~dfsg-0+deb9u2
has caused the Debian Bug report #925257,
regarding ghostscript: CVE-2019-3838: forceput in DefineResource is still
accessible
to be marked as done.
This means
Your message dated Thu, 18 Apr 2019 17:32:08 +
with message-id
and subject line Bug#922453: fixed in cernlib 20061220+dfsg3-4.3+deb9u1
has caused the Debian Bug report #922453,
regarding cernlib: fortran modules must be compiled with no stronger
optimization than -O1 (aka -O)
to be marked as
Your message dated Thu, 18 Apr 2019 17:32:53 +
with message-id
and subject line Bug#924509: fixed in rsync 3.1.2-1+deb9u2
has caused the Debian Bug report #924509,
regarding CVE-2016-9840 CVE-2016-9841 CVE-2016-9842 CVE-2016-9843
to be marked as done.
This means that you claim that the proble
Your message dated Thu, 18 Apr 2019 17:32:51 +
with message-id
and subject line Bug#920855: fixed in mariadb-10.1 10.1.38-0+deb9u1
has caused the Debian Bug report #920855,
regarding mariadb-10.1: FTBFS on mips{,{,64}el}: linker failures
to be marked as done.
This means that you claim that th
Your message dated Thu, 18 Apr 2019 17:32:08 +
with message-id
and subject line Bug#925256: fixed in ghostscript 9.26a~dfsg-0+deb9u2
has caused the Debian Bug report #925256,
regarding ghostscript: CVE-2019-3835: superexec operator is available
to be marked as done.
This means that you claim
Your message dated Thu, 18 Apr 2019 17:32:51 +
with message-id
and subject line Bug#920854: fixed in mariadb-10.1 10.1.38-0+deb9u1
has caused the Debian Bug report #920854,
regarding mariadb-10.1: FTBFS on s390x (test failure)
to be marked as done.
This means that you claim that the problem h
Your message dated Thu, 18 Apr 2019 17:32:18 +
with message-id
and subject line Bug#912848: fixed in mariadb-10.1 10.1.37-0+deb9u1
has caused the Debian Bug report #912848,
regarding mariadb-10.1: CVE-2018-3282 CVE-2018-3174 CVE-2018-3143 CVE-2018-3156
CVE-2018-3251
to be marked as done.
Thi
Your message dated Thu, 18 Apr 2019 17:18:39 +
with message-id
and subject line Bug#927292: fixed in libqb 1.0.4-2
has caused the Debian Bug report #927292,
regarding libqb: Breaks applications not running as root (for example
pacemaker-based AKA cib)
to be marked as done.
This means that yo
Your message dated Thu, 18 Apr 2019 16:48:35 +
with message-id
and subject line Bug#926728: fixed in ebtables 2.0.10.4+snapshot20181205-3
has caused the Debian Bug report #926728,
regarding Removing the package breaks the alternative on usr-merge system
to be marked as done.
This means that y
Your message dated Thu, 18 Apr 2019 16:48:29 +
with message-id
and subject line Bug#926728: fixed in arptables 0.0.4+snapshot20181021-4
has caused the Debian Bug report #926728,
regarding Removing the package breaks the alternative on usr-merge system
to be marked as done.
This means that you
Between the version which worked and the version which is failing, the
implementation of magick/resource.c was changed to allocate a semaphore for
each resource limit rather than using a single global semaphore across all
resource limits.
Something else which changed since the changeset vers
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
to be marked as done.
T
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
to be marked as done.
T
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
to be marked as done.
T
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
to be marked as done.
T
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding texlive-latex-extra: package tabu broken when xcolor is used
to be marked as done.
This means that you claim t
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding caffe: FTBFS: Fatal error occurred, no output PDF file produced!
to be marked as done.
This means that you cla
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding texlive-base: breaks build of forthcoming doxygen 1.8.15
to be marked as done.
This means that you claim that
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding bliss: FTBFS (LaTeX error)
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
to be marked as done.
T
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
to be marked as done.
T
Your message dated Thu, 18 Apr 2019 15:00:52 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190227-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
to be marked as done.
T
* Anton Ivanov [2019-04-18 15:05 +0100]:
> That is not an advice.
>
> If nscd is a required dependency, NIS should bring it in.
This is not a "must have"
>
> Presently it is not.
>
> Still broken
The advice is also mentioned in the changelog:
* Drop -no-dbus from YPBINDARGS= in /etc/defa
Please reopen.
Advice is no replacement for a Depends in the package control file.
As shipped the package is still broken and at the reported severity -
breaking most of the system
A.
On 18/04/2019 14:48, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug
That is not an advice.
If nscd is a required dependency, NIS should bring it in.
Presently it is not.
Still broken
A.
On 18/04/2019 14:43, Elimar Riesebieter wrote:
* Elimar Riesebieter [2019-04-03 11:06 +0200]:
* Anton Ivanov [2019-04-03 09:43 +0100]:
Package: nis
Version: 3.17.1-3+b1
Your message dated Thu, 18 Apr 2019 15:43:59 +0200
with message-id <20190418134359.t6sqscgqkem7i...@pippin.home.lxtec.de>
and subject line Re: Bug#926305: nis startup scripts are completely broken
has caused the Debian Bug report #926305,
regarding nis startup scripts are completely broken
to be ma
* Elimar Riesebieter [2019-04-03 11:06 +0200]:
> * Anton Ivanov [2019-04-03 09:43 +0100]:
>
> > Package: nis
> > Version: 3.17.1-3+b1
> > Severity: critical
> > Justification: breaks unrelated software
> >
> > Dear Maintainer,
> >
> > Startup scripts are completely broken. Something in the sy
On Thu, 18 Apr 2019, László Böszörményi wrote:
#2 0x7334640f in __assert_fail_base
(fmt=0x734a8ee0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
assertion=0x76657940 "semaphore_info != (SemaphoreInfo *) NULL",
file=0x766578c8 "magick/semaphore.c", line=606,
function=) at a
Hi,
On Fri, 5 Apr 2019 23:26:55 +0200 =?UTF-8?Q?Bernhard_=c3=9cbelacker?=
wrote:
> Dear Maintainer,
> just tried to help triaging this issue.
Me too.
>
> Seems this is "expected" behaviour with LC_ALL not
> set to "C". In the end it leads to this upstream bug:
>
> https://github.com/sirf
Package: segemehl
Version: 0.3.4-1
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any-i3
Package: tabix
Version: 1.9-10
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any-i386.
Package: samtools
Version: 1.9-4
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any-i386
Package: qtltools
Version: 1.1+dfsg-3
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any
Package: libhts2
Version: 1.9-10
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any-i386
Package: libhts-dev
Version: 1.9-10
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any-i
Package: delly
Version: 0.8.1-2
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any-i386.
Package: augustus
Version: 3.3.2+dfsg-2
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on a
Package: nanopolish
Version: 0.11.0-2
Severity: serious
Hi,
This package uses htslib, which is no longer supported on any-i386. #914991
removed the binaries on any-i386, but until any-i386 is removed from
Architecture:, wanna-build will re-build the package, thereby reinstating the
binaries on any
Processing commands for cont...@bugs.debian.org:
> # Missing dependencies are RC
> severity 927301 serious
Bug #927301 [gpustat] missing depends on python3-pkg-resources
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
927301
Processing commands for cont...@bugs.debian.org:
> retitle 926827 ruby-vcr: FTBFS randomly (failing tests)
Bug #926827 [src:ruby-vcr] ruby-vcr: FTBFS (failing tests)
Changed Bug title to 'ruby-vcr: FTBFS randomly (failing tests)' from 'ruby-vcr:
FTBFS (failing tests)'.
> severity 926827 important
retitle 926827 ruby-vcr: FTBFS randomly (failing tests)
severity 926827 important
tags 926827 + patch
thanks
Hi. This is really random, so I'm downgrading.
I've put a bunch of build logs here from my autobuilders:
https://people.debian.org/~sanvila/build-logs/ruby-vcr/
The failing test seems to
Processing commands for cont...@bugs.debian.org:
> severity 919849 grave
Bug #919849 [salt-doc] salt-doc: broken symlinks:
/usr/share/doc/salt/html/_static/*/bootstrap* ->
../../../../../twitter-bootstrap/files/*/bootstrap*
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.
Your message dated Thu, 18 Apr 2019 08:33:48 +
with message-id
and subject line Bug#927333: fixed in node-postcss-reporter 6.0.1+~3.0.0-1
has caused the Debian Bug report #927333,
regarding node-postcss-reporter: depends on non-existent node-log-symbols
to be marked as done.
This means that y
Processing control commands:
> tag -1 pending
Bug #927333 [node-postcss-reporter] node-postcss-reporter: depends on
non-existent node-log-symbols
Added tag(s) pending.
--
927333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927333
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Control: tag -1 pending
Hello,
Bug #927333 in node-postcss-reporter 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:
https://salsa.debian.org/js-team/node-postcss-reporter/commit/783094e
89 matches
Mail list logo
