* micah anderson [2019-01-20 21:03:53 +0100]:
> I'm not disputing this bug exists, I'm just trying to determine why it
> is you set the severity to "Serious". As you are probably aware, this
> severity indicates that this is a sever violation of Debian policy
> (violates a "must" or "required" dire
Processing control commands:
> affects -1 src:forensic-artifacts src:backblaze-b2
Bug #919974 [src:yapf] yapf: Python 2 removal breaks build dependencies of
other packages
Added indication that 919974 affects src:forensic-artifacts and src:backblaze-b2
--
919974: https://bugs.debian.org/cgi-bin
Source: yapf
Version: 0.25.0-1
Severity: serious
Control: affects -1 src:forensic-artifacts src:backblaze-b2
yapf (0.25.0-1) unstable; urgency=medium
...
[ Ana C. Custura ]
* debian/control:
- updates standards version to 4.3.0
- bumps debhelper version to 12
- removes support for
Your message dated Mon, 21 Jan 2019 07:51:39 +
with message-id
and subject line Bug#905415: fixed in nodejs 10.15.0~dfsg-9
has caused the Debian Bug report #905415,
regarding libnode-dev: broken symlinks:
/usr/include/nodejs/deps/uv/include/{uv,uv.h} -> ../../../../{uv,uv.h}
to be marked as d
Your message dated Mon, 21 Jan 2019 07:34:48 +
with message-id
and subject line Bug#919823: fixed in harp 1.5+data-2
has caused the Debian Bug report #919823,
regarding harp: FTBFS in sid (ERROR: CODA library and/or header file not found)
to be marked as done.
This means that you claim that t
Attempting to find solution, also asked on debian-python for some
assistance.
Package: netdata
Version: 1.12.0~rc3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From th
Package: node-rollup-pluginutils
Version: 2.3.3-2
Severity: serious
Tags: patch
Hello, looks like the latest upload fails its autopkgtestsuite, since
some days/weeks.
See e.g.:
https://ci.debian.net/data/autopkgtest/unstable/amd64/n/node-rollup-pluginutils/1618356/log.gz
(Reading database ... 22
Processing commands for cont...@bugs.debian.org:
> affects 919968
> src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,
Bug #919968 [openjdk-11-jdk-headless] libreoffice: bin
reassign 919968 openjdk-11-jdk-headless
merge 919883 919968
thanks
Hi,
On Mon, Jan 21, 2019 at 08:28:16AM +0200, Adrian Bunk wrote:
> ...
> [build BIN] ucbhelper
> S=/<> && I=$S/instdir && W=$S/workdir && mkdir -p
> $W/Module/nonl10n/ && touch $W/Module/nonl10n/ucbhelper
> javadoc: error - The
Processing commands for cont...@bugs.debian.org:
> affects 919968
> src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind
Bug #919968 [openjdk-11-jdk-headless] libreoffice: bina
Processing commands for cont...@bugs.debian.org:
> affects 919968
> src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind
Bug #919968 [openjdk-11-jdk-headless] libreoffice: bina
Processing commands for cont...@bugs.debian.org:
> reassign 919968 openjdk-11-jdk-headless
Bug #919968 [src:libreoffice] libreoffice: binary-all FTBFS
Bug reassigned from package 'src:libreoffice' to 'openjdk-11-jdk-headless'.
No longer marked as found in versions libreoffice/1:6.1.5~rc1-1.
Ignori
Processing commands for cont...@bugs.debian.org:
> severity 919962 serious
Bug #919962 [goaccess] Errors caused by not installing Recommend packages
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919962: https://bugs.debian
Source: libreoffice
Version: 1:6.1.5~rc1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=all&ver=1%3A6.1.5~rc1-1&stamp=1547977527&raw=0
...
[build BIN] ucbhelper
S=/<> && I=$S/instdir && W=$S/workdir && mkdir -p
$W/Module/nonl10n/ && touch $W/Modu
Source: ndcube
Version: 1.0.1-2
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ndcube.html
...
Running Sphinx v1.7.9
/usr/lib/python3/dist-packages/astropy_helpers/sphinx/conf.py:5: UserWarning:
Note that astropy_helpers.sphinx.conf is deprecated
Package: akregator
Version: 4:18.08.1-1
Severity: grave
Justification: renders package unusable
akregator doesn't start anymore. It exits with the following error message:
akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5:
undefined symbol:
_ZN7KNSCore6Engine15signal
Hi Ondřej,
On Sun, Jan 20, 2019 at 10:01:04PM +0100, OndÅ?ej Surý wrote:
> No harm doing was intended. I simply missed the NMU.
>
> If you can point me to the direction of the patches you prepared I will try
> to care of it before soft freeze.
In good NMU practise, I sent the combined patch to
Processing commands for cont...@bugs.debian.org:
> tags 919965 + buster sid
Bug #919965 [unyaffs] unyaffs: Non-working maintainer address
Added tag(s) buster and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919965: https://bugs.debian.org/cgi-bin/bugreport
Processing commands for cont...@bugs.debian.org:
> found 919965 0.9.6-1
Bug #919965 [unyaffs] unyaffs: Non-working maintainer address
Marked as found in versions unyaffs/0.9.6-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919965: https://bugs.debian.org/cgi-b
Your message dated Mon, 21 Jan 2019 06:59:44 +0200
with message-id <20190121045944.GN32397@localhost>
and subject line Fixed in 1.9.3-2
has caused the Debian Bug report #919717,
regarding biosig4c++ FTBFS on 32bit: symbol differences
to be marked as done.
This means that you claim that the problem
Package: unyaffs
Version: 0.9.7-0.1
Severity: serious
Justification: Policy 3.3
A working maintainer address is required:
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
matthew.fisc...@ubuntu.com
Processing commands for cont...@bugs.debian.org:
> merge 917756 918201 918625
Bug #917756 [src:astropy-healpix] astropy-healpix: FTBFS: tests failed
Unable to merge bugs because:
severity of #918625 is 'normal' not 'serious'
affects of #918625 is 'src:python-numpy' not ''
severity of #918201 is 'n
Hello,
I extracted Helmut's changes for this issue from the debdiff he posted
in an earlier message, and proposed a merge request on salsa.
https://salsa.debian.org/debian/cyrus-sasl2/merge_requests/3
as a git-format-patch(1) patch:
https://salsa.debian.org/debian/cyrus-sasl2/merge_requests/
Thank you for bug report. I am going to upload ntopng 3.8 soon and it will
fix the build against the latest ndpi.
Ludovico
On Sun, Jan 20, 2019 at 8:36 AM Adrian Bunk wrote:
> Source: ntopng
> Version: 2.4+dfsg1-4
> Severity: serious
> Tags: ftbfs
>
>
> https://tests.reproducible-builds.org/deb
Your message dated Mon, 21 Jan 2019 00:20:48 +
with message-id
and subject line Bug#919349: fixed in pyvo 0.9.2-2
has caused the Debian Bug report #919349,
regarding pyvo: Please remove python-astropy-helpers build dependency
to be marked as done.
This means that you claim that the problem ha
Processing commands for cont...@bugs.debian.org:
> affects 919895 src:dirgra
Bug #919895 [openjdk-11-jdk-headless] openjdk-11-jdk-headless: Regression:
Breaks a bunch of packages using javadoc
Bug #919798 [openjdk-11-jdk-headless] antlr4: FTBFS (Failed to execute goal
org.apache.maven.plugins:ma
Processing commands for cont...@bugs.debian.org:
> tag 891756 + pending
Bug #891756 [lmms] lmms: demote Dependency on "calf-ladspa" to "Recommends"
Added tag(s) pending.
> tag 897806 + pending
Bug #897806 [src:lmms] lmms: ftbfs with GCC-8
Added tag(s) pending.
> tag 918242 + pending
Bug #918242 [s
tag 891756 + pending
tag 897806 + pending
tag 918242 + pending
thanks
I have uploaded a fix. It is unfortunately waiting for my new signing
sub-key to be rolled into the Debian Keyring.
Regards,
Ross
signature.asc
Description: OpenPGP digital signature
Your message dated Sun, 20 Jan 2019 23:05:43 +
with message-id
and subject line Bug#919855: fixed in klibc 2.0.5-2
has caused the Debian Bug report #919855,
regarding klibc crashes on hppa
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Sun, 20 Jan 2019 23:05:43 +
with message-id
and subject line Bug#919855: fixed in klibc 2.0.5-2
has caused the Debian Bug report #919855,
regarding s390x executables crash
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not t
Processing commands for cont...@bugs.debian.org:
> reassign 919857 src:klibc
Bug #919857 [klibc] klibc crashes on hppa
Bug reassigned from package 'klibc' to 'src:klibc'.
No longer marked as found in versions 2.0.5-1.
Ignoring request to alter fixed versions of bug #919857 to the same values
prev
Processing control commands:
> forcemerge 919855 919857
Bug #919855 [src:klibc] s390x executables crash
Unable to merge bugs because:
package of #919857 is 'klibc' not 'src:klibc'
Failed to forcibly merge 919855: Did not alter merged bugs.
--
919855: https://bugs.debian.org/cgi-bin/bugreport.cg
Control: forcemerge 919855 919857
On Sun, Jan 20, 2019 at 02:22:38PM +, Thorsten Glaser wrote:
> Ben Hutchings dixit:
>
> >the new Debian version crashes on s390x. It looks like this is due to
> >an address collision between the build ID in the shared library and
> >the code in the executable
Processing control commands:
> forcemerge 919855 919857
Bug #919855 [src:klibc] s390x executables crash
Unable to merge bugs because:
package of #919857 is 'klibc' not 'src:klibc'
Failed to forcibly merge 919855: Did not alter merged bugs.
--
919855: https://bugs.debian.org/cgi-bin/bugreport.cg
Your message dated Sun, 20 Jan 2019 22:49:14 +
with message-id
and subject line Bug#919827: fixed in asterisk-espeak 5.0~1-2
has caused the Debian Bug report #919827,
regarding asterisk-espeak: FTBFS (Externally compiled modules must declare
AST_MODULE_SELF_SYM)
to be marked as done.
This me
Your message dated Sun, 20 Jan 2019 22:34:25 +
with message-id
and subject line Bug#919738: fixed in asterisk-flite 3.0-3
has caused the Debian Bug report #919738,
regarding asterisk-flite: FTBFS (Externally compiled modules must declare
AST_MODULE_SELF_SYM)
to be marked as done.
This means
Your message dated Sun, 20 Jan 2019 22:36:18 +
with message-id
and subject line Bug#915997: fixed in unyaffs 0.9.7-0.1
has caused the Debian Bug report #915997,
regarding unyaffs FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Processing commands for cont...@bugs.debian.org:
> forwarded 919828 https://github.com/traud/asterisk-opus/issues/15
Bug #919828 [src:asterisk-opus] asterisk-opus: FTBFS (Externally compiled
modules must declare AST_MODULE_SELF_SYM)
Set Bug forwarded-to-address to
'https://github.com/traud/aster
Processing control commands:
> tag -1 -ftbfs
Bug #912249 [src:ruby-file-tail] ruby-file-tail FTBFS:
test_tail_change2(FileTailTest) fails
Removed tag(s) ftbfs.
> retitle -1 test_tail_change2(FileTailTest) fails
Bug #912249 [src:ruby-file-tail] ruby-file-tail FTBFS:
test_tail_change2(FileTailTest
Control: tag -1 -ftbfs
Control: retitle -1 test_tail_change2(FileTailTest) fails
Control: severity -1 normal
Hi,
This test is now disabled in the test suite (build and autopkgtest).
I am therefore downgrading the severity of the bug and removing the
ftbfs tag, but leave the bug open, waiting for
Paul Gevers writes ("Re: Conflict over /usr/bin/dune"):
> For all those that haven't followed along in the bug report, the bug got
> reassigned to whitedune. I'm not sure if I agree with the reassignment,
> but an NMU by me is hanging in DELAYED/7 to fix the conflict in
> whitedune. If people objec
Processing control commands:
> block -1 by 919951
Bug #919953 [dune] /usrr/bin/dune and `dune' binary package should refer to
dune-common
919953 was not blocked by any bugs.
919953 was not blocking any bugs.
Added blocking bug(s) of 919953: 919951
--
919953: https://bugs.debian.org/cgi-bin/bugr
Package: dune
Version: 1.6.2-2
Severity: serious
Control: block -1 by 919951
According to Debian policy file conflicts should be resolved by no-one
using the conflicting name. This applies to /usr/bin/dune.
Additionally, the only referent of `dune' that anyone has heard of
(eg, wikipedia) is a C
Package: src:freezegun
Followup-For: Bug #916702
I locally created a version based on the more recent 0.3.11 upstream version,
with the same Debian files (plus an extra changelog entry, of course), and
``dpkg-buildpackage -A`` seemed to successfully build, pass the tests and
package everything.
S
Your message dated Sun, 20 Jan 2019 21:37:20 +
with message-id
and subject line Bug#919375: fixed in monitoring-plugins 2.2-5
has caused the Debian Bug report #919375,
regarding monitoring-plugins: FTBFS with mariadb-10.3: check_mysql.c:61:24:
error: 'MYSQL_PORT' undeclared
to be marked as do
Processing commands for cont...@bugs.debian.org:
> tag 891297 patch
Bug #891297 [src:gnome-keyring] gnome-keyring: Incomplete debian/copyright?
Ignoring request to alter tags of bug #891297 to the same tags previously set
>
End of message, stopping processing here.
Please contact me if you need a
Processing commands for cont...@bugs.debian.org:
> tag 891297 patch
Bug #891297 [src:gnome-keyring] gnome-keyring: Incomplete debian/copyright?
Added tag(s) patch.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
891297: https://bugs.debian.org/cgi-bin/bug
Your message dated Sun, 20 Jan 2019 21:35:16 +
with message-id
and subject line Bug#917055: fixed in blktool 4-7.1
has caused the Debian Bug report #917055,
regarding blktool FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Hello from the Montreal BSP!
I created a Merge Request on Salsa to fix this bug [1].
If there is a problem with that patch, don't hesitate to ping me and
I'll be glad to fix it.
Cheers!
[1] https://salsa.debian.org/gnome-team/gnome-keyring/merge_requests/1
--
,''`.
: :' : Loui
Processing control commands:
> notfound -1 0.4.4~bpo9+1
Bug #919915 [grub-cloud-amd64] grub2-common: fails to upgrade from
'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub
from grub-cloud-amd64 0.0.4~bpo9+1
There is no source info for the package 'grub-cloud-amd64'
Control: notfound -1 0.4.4~bpo9+1
Control: found -1 0.0.4~bpo9+1
Control: fixed -1 0.0.4
Control: severity -1 important
Control: tags -1 wontfix
On Sun, Jan 20, 2019 at 05:46:27PM +, Colin Watson wrote:
> It isn't me who needs the policy lecture here - this is grub2-common's
> configuration fi
> On Sat, Jan 12, 2019 at 02:11:25PM +0100, Vincent Lefevre wrote:
> I'm not at all sure that I agree. The configuration in question exists
> in order to tell the postinst which devices it should run grub-install
> on. If the device does not exist, it obviously isn't possible to run
> grub-instal
No harm doing was intended. I simply missed the NMU.
If you can point me to the direction of the patches you prepared I will try to
care of it before soft freeze.
Ondrej
--
Ondřej Surý
> On 25 Dec 2018, at 11:58, Helmut Grohne wrote:
>
> Hi Ryan,
>
>> On Mon, Dec 24, 2018 at 03:48:19PM -080
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 909313 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 909313 31.0.0-1
Bug #909313 {Done: Carsten Schoenert }
[x
Processing commands for cont...@bugs.debian.org:
> severity 919919 important
Bug #919919 [src:linux] frequent lockups requiring power off
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919919: https://bugs.debian.org/cgi-b
Processing commands for cont...@bugs.debian.org:
> forwarded 918418 https://github.com/korfuri/django-prometheus/issues/83
Bug #918418 [src:django-prometheus] django-prometheus FTBFS: test failures
Set Bug forwarded-to-address to
'https://github.com/korfuri/django-prometheus/issues/83'.
> thanks
Hello Sergio,
I'm reviewing bugs that are currently release critical at our local bug
squashing party, and I stumbled on yours.
I'm not disputing this bug exists, I'm just trying to determine why it
is you set the severity to "Serious". As you are probably aware, this
severity indicates that th
Hello Marc,
I'm checking up on RC bugs, because we are working on a Bug Squashing
Party here.
Back in November, you were saying you were going to combine this fix
with a bump of upstream's version:
> I was planning to combine this with an update from upstream.
I'm wondering if you are plannin
Control: severity -1 grave
On Sun, 2019-01-20 at 06:39 +, Ben Hutchings wrote:
> Source: klibc
> Version: 2.0.5-1
> Severity: serious
>
> While investigating some test failures on klibc upstream, I found that
> the new Debian version crashes on s390x. It looks like this is due to
> an addres
Processing control commands:
> severity -1 grave
Bug #919855 [src:klibc] s390x executables crash
Severity set to 'grave' from 'serious'
--
919855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Sun, Jan 20, 2019 at 07:33:44PM +0100, Mattia Rizzolo wrote:
> Then if you don't mind I'd still keep my NMU as it is and let it enter
> unstable. The only thing is that you'd find yourself to integrate it
> into your own tree.
no worries. will merge it.
thanks
felix
Your message dated Sun, 20 Jan 2019 19:04:27 +
with message-id
and subject line Bug#919255: fixed in gnucap-python 0.0.2-1.1
has caused the Debian Bug report #919255,
regarding gnucap-python: please stop build-depending on python3.6
to be marked as done.
This means that you claim that the pro
On Sun, Jan 20, 2019 at 07:36:57PM +0100, Felix Salfelder wrote:
> On Sun, Jan 20, 2019 at 07:33:44PM +0100, Mattia Rizzolo wrote:
> > Then if you don't mind I'd still keep my NMU as it is and let it enter
> > unstable. The only thing is that you'd find yourself to integrate it
> > into your own t
Processing commands for cont...@bugs.debian.org:
> tag 792851 - pending
Bug #792851 [src:cyrus-sasl2] FTCBFS: confuses build arch and host arch compiler
Removed tag(s) pending.
> tag 880393 - pending
Bug #880393 [libsasl2-modules-gssapi-heimdal] libsasl2-modules-gssapi-heimdal
seems built against
tag 792851 - pending
tag 880393 - pending
thanks
Since Helmut's NMU was canceled as described in #880393, I am removing
the "pending" tag from these two bugs.
On Sun, Jan 20, 2019 at 05:03:27PM +0100, Felix Salfelder wrote:
> On Sun, Jan 20, 2019 at 04:34:28PM +0100, Mattia Rizzolo wrote:
> > If it's only about sponsoring I'm happy to help, but I don't really want
> > to play with symbols at this time…
>
> my preferred solution will be to accept the dpk
Your message dated Sun, 20 Jan 2019 18:21:35 +
with message-id
and subject line Bug#919909: fixed in libconfig-model-backend-yaml-perl 2.133-2
has caused the Debian Bug report #919909,
regarding libconfig-model-backend-yaml-perl: fails to upgrade from 'stretch' -
trying to overwrite /usr/shar
0.8 51748 33624 pts/2S+ 19:06 0:00
/usr/bin/python3 /usr/bin/reportbug atop
user 549910 0.0 0.0 2512 508 pts/2S+ 19:07 0:00 sh -c vim -c
:6 '/tmp/user/1000/reportbug-atop-20190120-547330-uof401oa'
user 549911 0.1 0.1 12340 7324 pts/2S+ 19:07 0
Processing control commands:
> tag -1 pending
Bug #919909 [libconfig-model-backend-yaml-perl]
libconfig-model-backend-yaml-perl: fails to upgrade from 'stretch' - trying to
overwrite /usr/share/man/man3/Config::Model::Backend::Yaml.3pm.gz
Added tag(s) pending.
--
919909: https://bugs.debian.or
Your message dated Sun, 20 Jan 2019 18:05:24 +
with message-id
and subject line Bug#919899: fixed in ppl 1:1.2-7
has caused the Debian Bug report #919899,
regarding libppl-{c4,swi}: unhandled symlink to directory conversion:
/usr/share/doc/PACKAGE
to be marked as done.
This means that you cl
Control: tag -1 pending
Hello,
Bug #919909 in libconfig-model-backend-yaml-perl 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/perl-team/modules/packages/libc
Processing commands for cont...@bugs.debian.org:
> reassign 783346 src:xen 4.1.4-3+deb7u4
Bug #783346 [xen-utils-4.1] patch for booting Jessie domU with wheezy dom0
Bug reassigned from package 'xen-utils-4.1' to 'src:xen'.
No longer marked as found in versions xen/4.1.4-3+deb7u4.
Ignoring request
Processing commands for cont...@bugs.debian.org:
> severity 919882 normal
Bug #919882 [firefox-esr] firefox-esr: linker options under investigation for
32-bit builds
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919882: h
reassign 783346 src:xen 4.1.4-3+deb7u4
severity 783346 normal
thanks
Hi Daniel,
This is about the bug report that you filed before about pygrub in the
Debian bug tracker against the Xen packages.
Your bug report was targeted at a Xen package in a Debian distribution
older than the current stable
severity 912592 normal
tags 912592 + moreinfo
thanks
Hi zer0 divide,
Thanks for your report.
I have never used the combination of Xen dom0 and cryptsetup myself.
Did you already find out what the cause of this issue is? It sounds a
bit like a problem with your initramfs. Or, can you explain why
Processing commands for cont...@bugs.debian.org:
> severity 912592 normal
Bug #912592 [src:xen] Xen stuck at boot "device-mapper: ioctl: …"
Severity set to 'normal' from 'critical'
> tags 912592 + moreinfo
Bug #912592 [src:xen] Xen stuck at boot "device-mapper: ioctl: …"
Added tag(s) moreinfo.
> t
Control: reassign -1 grub-cloud-amd64 0.4.4~bpo9+1
Control: affects -1 grub2-common
On Sun, Jan 20, 2019 at 06:03:36PM +0100, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch'.
> It installed fine in 'stretch', then the upgrade to 'buste
Processing commands for cont...@bugs.debian.org:
> severity 919774 serious
Bug #919774 [meld] add dependency on python3-gi-cairo
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919774: https://bugs.debian.org/cgi-bin/bugrepo
Processing control commands:
> reassign -1 grub-cloud-amd64 0.4.4~bpo9+1
Bug #919915 [grub2-common] grub2-common: fails to upgrade from
'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub
from grub-cloud-amd64 0.0.4~bpo9+1
Bug reassigned from package 'grub2-common' to
Package: src:linux
Version: 4.19.12-1
Severity: grave
Tags: upstream
Hello,
I experience lockups about every few minutes to hours of my laptop which
I guess are kernel bugs. At least, the machine is fairly new, and
hardware diagnostics turned up nothing.
The system has a standard /boot and an L
Processing commands for cont...@bugs.debian.org:
> severity 882806 normal
Bug #882806 [src:xen] xen-hypervisor-4.8-amd64: After upgrade to stretch all
Windows VM crash on boot or hang on boot
Severity set to 'normal' from 'critical'
> tags 882806 + moreinfo
Bug #882806 [src:xen] xen-hypervisor-4.
Source: scikit-learn
Version: 0.20.1+dfsg-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=scikit-learn&suite=sid
There are several, potentially unrelated, test failures
on various architectures.
severity 882806 normal
tags 882806 + moreinfo
thanks
Hi Dan,
Thanks for your report.
There's a small team of Debian package maintainers, and a huge amount of
different things you can do with Xen. While Xen allows running Windows
guests, the Debian maintainers do not have much experience with tha
Your message dated Sun, 20 Jan 2019 17:19:45 +
with message-id
and subject line Bug#919902: fixed in exim4 4.92~RC4-3
has caused the Debian Bug report #919902,
regarding exim4-config: fails to upgrade from 'stretch': option
"hosts_try_dane" unknown
to be marked as done.
This means that you c
Processing control commands:
> affects -1 + libjs-protoaculous
Bug #919917 [yui-compressor] yui-compressor: insufficient java dependency in
jessie
Added indication that 919917 affects libjs-protoaculous
> found -1 libjs-protoaculous/5
Bug #919917 [yui-compressor] yui-compressor: insufficient java
Package: yui-compressor
Version: 2.4.7-2
Severity: serious
Tags: jessie
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libjs-protoaculous
Control: found -1 libjs-protoaculous/5
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition o
Package: grub2-common
Version: 2.02+dfsg1-10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + grub-cloud-amd64
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'bu
Processing control commands:
> affects -1 + grub-cloud-amd64
Bug #919915 [grub2-common] grub2-common: fails to upgrade from
'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub
from grub-cloud-amd64 0.0.4~bpo9+1
Added indication that 919915 affects grub-cloud-amd64
--
Package: gnome-tweaks
Version: 3.30.2-1
Severity: grave
Tags: security
Recently, disabling the setting "Suspend when laptop lid is closed"
seems to have started preventing *any* action on lid close, including
locking the screen; disabling that setting adds a startup file to run
/usr/lib/gnome-twea
Package: src:knxd
Version: 0.14.29-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
Control: tag -1 pending
Hello,
Bug #917493 in fenix 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/games-team/fenix/commit/dd9057c3f20c60483cdb8aae27f0679cd5c1
Processing control commands:
> tag -1 pending
Bug #917493 [src:fenix] fenix: FTBFS when built with dpkg-buildpackage -A
Added tag(s) pending.
--
917493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> affects -1 + libconfig-model-perl
Bug #919909 [libconfig-model-backend-yaml-perl]
libconfig-model-backend-yaml-perl: fails to upgrade from 'stretch' - trying to
overwrite /usr/share/man/man3/Config::Model::Backend::Yaml.3pm.gz
Added indication that 919909 affects l
Package: libconfig-model-backend-yaml-perl
Version: 2.133-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libconfig-model-perl
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then
Source: ntopng
Version: 2.4+dfsg1-4
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ntopng.html
...
g++ -g -Wall -I/build/1st/ntopng-3.2+dfsg1
-I/build/1st/ntopng-3.2+dfsg1/include -I/usr/local/include
-D_FILE_OFFSET_BITS=64 -I/usr/include/hiredi
Package: src:node-istanbul
Version: 0.4.5+ds-3
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
dh_update_autoto
Processing commands for cont...@bugs.debian.org:
> owner 891297 po...@debian.org
Bug #891297 [src:gnome-keyring] gnome-keyring: Incomplete debian/copyright?
Owner recorded as po...@debian.org.
> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was po...@debian.
Processing commands for cont...@bugs.debian.org:
> tags 919877 + buster sid
Bug #919877 [src:ruby-sprite-factory] ruby-sprite-factory: FTBFS (failing test)
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
919877: https://bugs.debian.org
Package: exim4-config
Version: 4.92~RC4-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + exim4-daemon-light
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'bus
1 - 100 of 175 matches
Mail list logo
