> Gesendet: Montag, 27. April 2020 um 20:22 Uhr
> Von: "John Scott"
> An: 919769-submit...@bugs.debian.org, hikaru.deb...@web.de
> Betreff: Re: RE: firefox-esr: OB Firefox 60.4 crashes immediately on amrhf
> (Raspberry Pi)
>
> On Mon, 4 Feb 2019 19:00:59 +0100 hikaru.deb...@web.de wrote:
> > So I
Package: default-jdk
Version: openjdk-11-jre
Followup-For: Bug #929685
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
- I was installing default-jre/jdk on my 32-bit ARM machine and it refused
to install
Rob Browning writes:
> Please try to migrate soon, and at this point, to guile-3.0 if possible.
> Otherwise we might need to consider removing the package from Debian.
As far as I'm concerned, you can feel free to remove geda-gaf from Debian.
I'm personally quite happily living on the fork that
Processing commands for cont...@bugs.debian.org:
> tags 958851 + pending
Bug #958851 [src:initramfs-tools] initramfs-tools: autopkgtest needs update for
new version of shellcheck: SC2086: Double quote to prevent globbing and word
splitting.
Added tag(s) pending.
> thanks
Stopping processing here
Please try to migrate soon, and at this point, to guile-3.0 if possible.
Otherwise we might need to consider removing the package from Debian.
Sometimes it's sufficient to just update the build dependency from say
guile-2.0-dev to guile-3.0-dev and adjust some of the related versions
in configur
Please try to update this soon, or we'll need to consider removing
freehdl from Debian, and if possible please attempt to move to guile-3.0
instead of guile-2.2 now, if possible.
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0
I think we probaly either need to address this soon, or consider
removing libmatheval from Debian.
Sometimes it's sufficient to just update the build dependency from say
guile-2.0-dev to guile-3.0-dev and adjust some of the related versions
in configure.ac (or configure.in), but in this case it
Your message dated Mon, 27 Apr 2020 22:28:52 +
with message-id
and subject line Bug#958756: Removed package(s) from unstable
has caused the Debian Bug report #943227,
regarding python-torctl: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Package: broadcom-sta-dkms
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Because I recently had trouble with Wifi after an upgrade of package
firmware-b43-installer,
I purged this package and tried to install package broadcom-sta-dkms,
according to the recently updated
Your message dated Mon, 27 Apr 2020 22:33:12 +
with message-id
and subject line Bug#958978: Removed package(s) from unstable
has caused the Debian Bug report #860614,
regarding golang-github-rackspace-gophercloud: FTBFS on i386: Test failures
to be marked as done.
This means that you claim th
Your message dated Mon, 27 Apr 2020 22:33:12 +
with message-id
and subject line Bug#958978: Removed package(s) from unstable
has caused the Debian Bug report #917747,
regarding golang-github-rackspace-gophercloud: FTBFS: tests failed
to be marked as done.
This means that you claim that the pr
Your message dated Mon, 27 Apr 2020 22:33:12 +
with message-id
and subject line Bug#958978: Removed package(s) from unstable
has caused the Debian Bug report #929584,
regarding Not suitable for buster
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Mon, 27 Apr 2020 22:32:38 +
with message-id
and subject line Bug#958971: Removed package(s) from unstable
has caused the Debian Bug report #882466,
regarding kubernetes-addon-heapster FTBFS: schema.go:26:2: cannot find package
"github.com/emicklei/go-restful/swagger"
to be
Your message dated Mon, 27 Apr 2020 22:29:49 +
with message-id
and subject line Bug#958913: Removed package(s) from unstable
has caused the Debian Bug report #950512,
regarding quotecolors: not usable anymore with TB>= 68.x
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 27 Apr 2020 22:27:36 +
with message-id
and subject line Bug#958743: Removed package(s) from unstable
has caused the Debian Bug report #938615,
regarding synopsis: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 27 Apr 2020 22:26:53 +
with message-id
and subject line Bug#958742: Removed package(s) from unstable
has caused the Debian Bug report #937779,
regarding python-gd: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 27 Apr 2020 22:26:27 +
with message-id
and subject line Bug#958741: Removed package(s) from unstable
has caused the Debian Bug report #937429,
regarding pyeos: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Mon, 27 Apr 2020 22:26:27 +
with message-id
and subject line Bug#958741: Removed package(s) from unstable
has caused the Debian Bug report #915754,
regarding pyeos FTBFS with python-pip 18.1
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Mon, 27 Apr 2020 22:25:58 +
with message-id
and subject line Bug#958739: Removed package(s) from unstable
has caused the Debian Bug report #936793,
regarding kid: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 27 Apr 2020 22:25:04 +
with message-id
and subject line Bug#958726: Removed package(s) from unstable
has caused the Debian Bug report #873372,
regarding anything-el: package is outdated and obsolete, removal required
to be marked as done.
This means that you claim that
Dear Maintainer,
I could reproduce the issue on i386 and tried to collect
some more information.
It crashes with the backtrace below.
The crash seems to be caused by using the wrong data type
in the calls to variadic functions goo_canvas_ellipse_new
and goo_canvas_polyline_new.
The modifications
Package: rakudo
Version: 2020.02.1-1
Severity: serious
Dear Maintainer,
/usr/share/perl6/rakudo-helper.pl uses autodie and system(), which
requires IPC::System::Simple, causing the following error when
installing or upgrading the package:
Setting up rakudo (2020.02.1-1) ...
IPC::System::Simple r
Your message dated Mon, 27 Apr 2020 21:07:36 +
with message-id
and subject line Bug#951978: fixed in vala-panel 0.4.92+dfsg1-1
has caused the Debian Bug report #951978,
regarding vala-panel: FTBFS: ./obj-x86_64-linux-gnu/../util/misc.c:100:
multiple definition of `vala_panel_reset_schema_with
Processing commands for cont...@bugs.debian.org:
> notfound 949067 340.108
Bug #949067 [nvidia-legacy-340xx-kernel-dkms] nvidia-legacy-340xx-kernel-dkms:
NVRM: RmInitAdapter failed! on Linux Kernel 5.4
There is no source info for the package 'nvidia-legacy-340xx-kernel-dkms' at
version '340.108'
Your message dated Mon, 27 Apr 2020 20:48:39 +
with message-id
and subject line Bug#958986: fixed in celery 4.4.2-2
has caused the Debian Bug report #958986,
regarding celery: FTBFS with Sphinx 2.0.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Mon, 27 Apr 2020 20:36:02 +
with message-id
and subject line Bug#958467: fixed in libonig 6.9.5-2
has caused the Debian Bug report #958467,
regarding libonig: set --enable-posix-api=yes again
to be marked as done.
This means that you claim that the problem has been dealt wi
Control: tags 956359 + pending
Dear maintainer,
I've prepared an NMU for netgen (versioned as 6.2.1804+dfsg1-3.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
--
tobi
diff -Nru netgen-6.2.1804+dfsg1/debian/changelog netgen-6.2.1804+dfsg1/debi
Processing control commands:
> tags 956359 + pending
Bug #956359 [src:netgen] netgen: FTBFS with new opencascade 7.4 (library
transistion)
Added tag(s) pending.
--
956359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with prob
Your message dated Mon, 27 Apr 2020 19:33:54 +
with message-id
and subject line Bug#958983: fixed in sphinx-celery 2.0.0-1
has caused the Debian Bug report #958983,
regarding sphinx-celery: incompatible with sphinx 2+
to be marked as done.
This means that you claim that the problem has been d
Control: reopen -1
Control: retitle -1 autopkgtest must be marked superficial
On 23-04-2020 22:16, Paul Gevers wrote:
> with my release team member
> hat on, I request you to mark you smoke-test as superficial as it's
> hardly testing the package.
I don't see this has happened.
Paul
signature
Processing control commands:
> reopen -1
Bug #958574 {Done: Michael Crusoe } [src:toil] toil:
autopkgtest regression in a superficial test
'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
Processing commands for cont...@bugs.debian.org:
> owner 958986 !
Bug #958986 [src:celery] celery: FTBFS with Sphinx 2.0.0
Owner changed from ! to Mattia Rizzolo .
> owner 958983 !
Bug #958983 [src:sphinx-celery] sphinx-celery: incompatible with sphinx 2+
Owner recorded as Mattia Rizzolo .
> thank
On Mon, 4 Feb 2019 19:00:59 +0100 hikaru.deb...@web.de wrote:
> So I'd conclude this problem is specific to the Stretch/arm* architectures.
Thanks. This bug looks like #909498. That was also reported on Stretch with a
Raspberry Pi. Can you still reproduce it?
Also look at #949834, but both indiv
Processing control commands:
> close -1 9.0.3+~5.0.0+~4.0.0-2
Bug #958990 [src:node-hoek] src:node-hoek: fails to migrate to testing for too
long
Marked as fixed in versions node-hoek/9.0.3+~5.0.0+~4.0.0-2.
Bug #958990 [src:node-hoek] src:node-hoek: fails to migrate to testing for too
long
Marke
Source: node-hoek
Version: 8.5.0+~4.2.1+~3.3.1-1
Severity: serious
Control: close -1 9.0.3+~5.0.0+~4.0.0-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 952143
Dear maintainer(s),
As recently announced [1], the Release Team now consider
Processing control commands:
> forcemerge 948708 -1
Bug #948708 [firefox-esr] firefox-esr: dies with SIGILL in libxul.so on aarch64
following upgrade
Bug #949834 [firefox-esr] [arm64] firefox-esr: illegal instruction in
/usr/lib/firefox-esr/libxul.so
Severity set to 'important' from 'critical'
B
Control: forcemerge 948708 -1
Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1609535
Hi,
This looks like #948708 which indicates this might've been fixed in 68.5.0.
Could you upgrade if you haven't already and see if it crashes again?
signature.asc
Description: This is a dig
Source: celery
Version: 4.4.2-1
Severity: serious
Control: block -1 by 958983
Control: 958983 !
Owner: !
SSIA.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org
Processing control commands:
> block -1 by 958983
Bug #958986 [src:celery] celery: FTBFS with Sphinx 2.0.0
958986 was not blocked by any bugs.
958986 was not blocking any bugs.
Added blocking bug(s) of 958986: 958983
> 958983 !
Unknown command or malformed arguments to command.
--
958986: https
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:libopenshot-audio
> # 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.debi
Source: sphinx-celery
Version: 1.3.1-2
Severity: serious
This theme is not compatible with sphinx 2.
There seems to be a new upstream available in
https://github.com/celery/sphinx_celery that at least has relevant
commits.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A F
Processing commands for cont...@bugs.debian.org:
> # the current FTBFS is different, close this again
> close 952217 4.4.2-1
Bug #952217 [src:celery] celery: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.8 3.7" --system=custom
"--test-args={interpreter} setup.
Your message dated Mon, 27 Apr 2020 16:33:38 +
with message-id
and subject line Bug#867515: fixed in mdp 3.6-1
has caused the Debian Bug report #867515,
regarding mdp FTBFS with python 3.6 as supported version
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Mon, 27 Apr 2020 16:33:43 +
with message-id
and subject line Bug#940215: fixed in printrun 2.0.0~rc5-1.1
has caused the Debian Bug report #940215,
regarding printrun: missing Breaks+Replaces: printrun (<< 2) for package split
to be marked as done.
This means that you claim
Your message dated Mon, 27 Apr 2020 16:33:43 +
with message-id
and subject line Bug#956842: fixed in printrun 2.0.0~rc5-1.1
has caused the Debian Bug report #956842,
regarding printrun: FTBFS with python 3.8
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 27 Apr 2020 17:05:47 +0100
with message-id <20200427160547.gb3...@tack.einval.com>
and subject line Re: Bug#958722: grub-efi-amd64-signed - Uninstallable
has caused the Debian Bug report #958722,
regarding grub-efi-amd64-signed - Uninstallable
to be marked as done.
This mea
control: tags -1 patch
Hi,
there are basically only 2 python scripts included,
src/battery-stats-generate and src/battery-stats-graph.
Attached is a patch that adds a patch to d/patches to modify those for
python3 and also updates d/control & d/rules accordingly.
Cheers,
Birger
From 5c5e08d97955
Processing control commands:
> tags -1 patch
Bug #936187 [src:battery-stats] battery-stats: Python2 removal in sid/bullseye
Added tag(s) patch.
--
936187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 27 Apr 2020 15:58:22 +0200
with message-id
and subject line Fixed in 4.0.0-2
has caused the Debian Bug report #958574,
regarding toil: autopkgtest regression in a superficial test
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Mon, 27 Apr 2020 13:53:31 +
with message-id
and subject line Bug#956219: fixed in webkit2gtk 2.28.2-2
has caused the Debian Bug report #956219,
regarding Error out when DISPLAY is unset
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> found 954148 0.31.0-1
Bug #954148 [src:doit] src:doit: Requires a package outside of Main
Marked as found in versions doit/0.31.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
954148: https://bugs.debian.org/
Control: severity -1 normal
I concur with Bernhard.
And since there's not enough information, we can go only by the log
messages.
It seems to me that either BIND uses custom selinux/apparmor profile
or something else is in place that disallows named from accessing those
files.
The BIND 9 provid
Processing control commands:
> severity -1 normal
Bug #958934 [bind9] bind9: named fails to start after upgrade to 9.16.2
Severity set to 'normal' from 'critical'
--
958934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pro
Hi,
On Sat, Apr 25, 2020 at 12:56:48AM +0200, Lorenzo wrote:
> I have a question:
> let's say that I change the recommends, like the following
>
> Recommends: runit-systemd | runit-sysv | runit-init
>
> What happens in a given system if the "runit-systemd" package is not
> in the apt index (the pa
Am 26.04.20 um 23:42 schrieb R. Scott Bailey:
Dear Scott,
> Life was good on my DNS server until my recent update to 9.16.2-3.
> After upgrading, the exact configuration that was happy now fails to
> start. Example:
>
> # named -g -u bind
> 26-Apr-2020 17:25:50.921 Could not open '//run/named/n
Processing commands for cont...@bugs.debian.org:
> severity 958828 important
Bug #958828 [src:telegram-purple] telegram-purple: FTBFS on big endian
architectures
Severity set to 'important' from 'serious'
> outlook 958828 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958828#18
Outlook recorde
severity 958828 important
outlook 958828 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958828#18
thanks
Hi Ben,
> tl;dr: wontfix (cantfix)
ok. If it’s by design, I can declare the package little-endian-only.
> I'm effectively the maintainer of telegram-purple. Not because I
> actually *deve
On Monday 27 April 2020 11:15:30 Paul van Tilburg wrote:
> Hi!
>
> This bug report was originally about buster and in my opinion a
> backport is necessary (stretch also had one). I reckon mostly servers
> use Let's Encrypt, and they mostly run Debian buster/stable.
> Given that upstream doesn't se
Hi!
This bug report was originally about buster and in my opinion a
backport is necessary (stretch also had one). I reckon mostly servers
use Let's Encrypt, and they mostly run Debian buster/stable.
Given that upstream doesn't seem to change to that much, is that a
possibility?
I didn't reopen th
Your message dated Mon, 27 Apr 2020 11:17:42 +0200
with message-id <42989909-7d24-9416-fe84-14069ed40119@malerba.space>
and subject line New release uploaded.
has caused the Debian Bug report #950847,
regarding python-icecream needs new upstream for Python 3.8 support
to be marked as done.
This me
Control: tags -1 + patch
On Sat, 25 Apr 2020 at 20:42:22 +0200, Paul Gevers wrote:
> With a recent upload of vulkan-loader you added an autopkgtest, great.
> However, it fails. I copied some of the output at the bottom of this
> report. It seems you're missing some test dependencies.
Sorry, that
Processing control commands:
> tags -1 + patch
Bug #958836 [src:vulkan-loader] vulkan-loader: autopkgtest failure: missing
test dependencies
Added tag(s) patch.
--
958836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with prob
Source: btfs
Version: 2.20-1
Severity: serious
Tags: ftbfs bullseye sid
Hi Maintainer
A recent rebuild of btfs against libtorrent-rasterbar10 FTBFS on
release architectures armel and mipsel, among others [1].
I've included what I hope is the relevant part of the log below.
I believe the solutio
On Mon, Apr 27, 2020 at 11:01 AM Sergei Golovan wrote:
> Looks like changes in Erlang regular expressions library broke Elixir
> again. Elixir stores internal binary representation of regular
> expressions in its compilation phase, and it breaks when Erlang
> changes this representation (which hap
Control: affects -1 src:python-biopython
On Tue, 14 Apr 2020 at 17:39, Andreas Tille wrote:
> Control: reassign -1 clustalo
> Control: retitle -1 "clustalo: Bus error on mipsel"
> Control: tags -1 upstream
> Control: forwarded -1 clust...@ucd.ie
Marking this bug as affecting src:python-biopython
Processing control commands:
> affects -1 src:python-biopython
Bug #956324 [clustalo] "clustalo: Bus error on mipsel"
Added indication that 956324 affects src:python-biopython
--
956324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956324
Debian Bug Tracking System
Contact ow...@bugs.debian
Hi Paul!
On Sat, Apr 25, 2020 at 10:09 PM Paul Gevers wrote:
>
> Dear maintainer(s),
>
> With a recent upload of erlang the autopkgtest of elixir-lang fails in
> testing when that autopkgtest is run with the binary packages of erlang
> from unstable. It passes when run with only packages from tes
Hi folks,
we have the issue that eCryptfs has not made it into Buster and has
fallen out of testing due to bug #765854.
To me it seems the most easy solution is from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854#107
as non-interactive logins don't have any passphrase to unlock an
e
Your message dated Mon, 27 Apr 2020 17:14:30 +1000
with message-id <2148203.0bjhXUgxBM@simurgh>
and subject line Re: Bug#954403: joblib: configuration error installing
python3-joblib
has caused the Debian Bug report #954403,
regarding joblib: configuration error installing python3-joblib
to be mar
69 matches
Mail list logo
