Package: linux
Version: 5.14-1~exp1
Severity: serious
Hi,
after applying the perf fixes, it builds for me on amd64, i386, armel,
and armhf, but fails on arm64:
---snip---
dh_prep
kernel-wedge install-files 5.14.0-trunk
install -D -m 644
Processing control commands:
> tag -1 pending
Bug #993651 [lintian] lintian: "Profile debian/main references unknown checks"
when run from Debian package
Added tag(s) pending.
--
993651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993651
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #993651 in lintian 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:
Your message dated Sun, 05 Sep 2021 01:19:38 +
with message-id
and subject line Bug#978927: fixed in xwelltris 1.0.1-18
has caused the Debian Bug report #978927,
regarding xwelltris: ftbfs with autoconf 2.70
to be marked as done.
This means that you claim that the problem has been dealt
On 2021-09-04 23:45, Diane Trout wrote:
Hmm...
So dask doesn't think jinja is required for base functionality. It's a
dependency for an extended extras.
OK, thanks for checking it.
...
At dask's end jinja should probably be a suggests or recommends, but
since you can use dask without
On Sat, 2021-09-04 at 17:08 +0200, Axel Beckert wrote:
> Also it is unclear to me why the source is the Mozilla XPI while the
> package works with both and upstream offers different download files
> for Firefox and for Chromium/Chrome. (Then again, I haven't worked on
> browser extensions since
hello,
looks like the error regarding the forced kill is not a debian issue but
also happens on ubuntu.
Bug should be closed.
The message seems curious as it is only produced when docker.service is
stopped, not when a container is stopped using docker stop; next to that
I do see containers
Hmm...
So dask doesn't think jinja is required for base functionality. It's a
dependency for an extended extras.
>From dask's setup.py
extras_require = {
"array": ["numpy >= 1.18"],
"bag": [], # keeping for backwards compatibility
"dataframe": ["numpy >= 1.18", "pandas >= 1.0"],
Processing commands for cont...@bugs.debian.org:
> found 993303 2.2.9-2+deb11u1
Bug #993303 [haproxy] haproxy: Fails to handle URL paths starting with more
than one '/' using HTTP/2
Marked as found in versions haproxy/2.2.9-2+deb11u1.
> affects 993303 + release.debian.org,security.debian.org
Bug
Your message dated Sat, 04 Sep 2021 21:34:32 +
with message-id
and subject line Bug#992971: fixed in grilo 0.3.13-1.1
has caused the Debian Bug report #992971,
regarding grilo: CVE-2021-39365
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Processing control commands:
> affects -1 src:python-xarray
Bug #993694 [python3-dask] missing Depends: python3-jinja2
Added indication that 993694 affects src:python-xarray
--
993694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993694
Debian Bug Tracking System
Contact
Package: python3-dask
Version: 2021.08.1+dfsg-1
Severity: serious
Justification: debci
Control: affects -1 src:python-xarray
dask imports from jinja2 in
/usr/lib/python3/dist-packages/dask/widgets/widgets.py, but
Depends: python3-jinja2 has not been declared.
dask's own tests are apparently not
Package: webpack
Version: 5.6.0+~cs6.4.0-1~exp2
Severity: grave
I was trying to update another js-team package and couldn't understand
what was wrong until I tried to just run webpack by itself in another
directory:
$ webpack
[webpack-cli] ReferenceError: options is not defined
at
Package: docker.io
Version: 20.10.5+dfsg1-1+b5
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: hostmas...@appelo.org
Dear Maintainer,
install a debian fresh bullsye system. install docker.io and run
nginx as a container. the container is forcefully killed:
Source: pytest-mpi
Version: 0.5-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of pytest-mpi the autopkgtest of pytest-mpi fails
in testing when that autopkgtest is run with the binary
Your message dated Sat, 04 Sep 2021 20:22:40 +
with message-id
and subject line Bug#993480: fixed in gcl 2.6.12-103
has caused the Debian Bug report #993480,
regarding gcl: Fails to install in unstable
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 4 Sep 2021 18:56:31 +0200
with message-id
and subject line Re: Bug#993532: libpod: autopkgtest regression between 29 Aug
2021 and 2 Sep 2021
has caused the Debian Bug report #993532,
regarding libpod: autopkgtest regression between 29 Aug 2021 and 2 Sep 2021
to be marked
Your message dated Sat, 04 Sep 2021 16:03:30 +
with message-id
and subject line Bug#992439: fixed in libconfig-model-dpkg-perl 2.149
has caused the Debian Bug report #992439,
regarding libconfig-model-dpkg-perl: blocks fails autopkgtest with recent
licensecheck
to be marked as done.
This
Hi,
Paul Wise wrote:
> uMatrix is no longer developed upstream:
>
> https://github.com/gorhill/uMatrix
>
> This repository has been archived by the owner. It is now read-only.
[…]
> The upstream author has stated they no longer have time for it:
>
>
>
Package: debianutils
Version: 5.4-3
Severity: critical
Justification: breaks unrelated software
The tempfile saga is not over. It might be wise grepping through the
maintainer scripts of all packages.
printer-driver-pnm2ppa still requires it.
Best
-- System Information:
Debian Release:
❦ 4 September 2021 15:49 +03, Michael Tokarev:
>> Kernel: Linux 5.13.0-trunk-amd64 (SMP w/12 CPU threads)
>
> Can you please check if it works with not-so-fresh kernel
> (eg the one from bullseye)?
>
> I wont able to do this until late evening today.
>
> I'm guessing this is the upstream way to
Processing commands for cont...@bugs.debian.org:
> found 993361 3.0.9-1
Bug #993361 [src:kylin-burner] kylin-burner: Please release 3.0.10 to unstable
Marked as found in versions kylin-burner/3.0.9-1.
> tags 993361 + bookworm sid
Bug #993361 [src:kylin-burner] kylin-burner: Please release 3.0.10
04.09.2021 14:33, Vincent Bernat wrote:
> Package: qemu-user-static
> Version: 1:6.1+dfsg-4
> Severity: critical
>
Hey!
Since 6.0, qemu-user-static does not seem to work properly through
binfmt. I am a bit lost on how to diagnose that:
...
When invoked through binfmt, the binaries seem to go
Processing commands for cont...@bugs.debian.org:
> # Fixed since 1.4.2, see https://github.com/gorhill/uMatrix/releases/tag/1.4.2
> tags 991344 + fixed-upstream
Bug #991344 [src:umatrix] umatrix: CVE-2021-36773: Denial of Service
Bug #991770 [src:umatrix] umatrix: new upstream release (1.4.4)
On Sat, 28 Dec 2019 at 21:15:35 +, Simon McVittie wrote:
> This package has a build-dependency on libpangox-1.0-dev, the Core X
> backend for Pango, which has been deprecated since at least 2012, is
> unmaintained upstream and is essentially unmaintained in Debian.
...
> There doesn't seem to
Source: drbd-doc
Version: 8.4~20151102-1
Severity: serious
Justification: blocker for resolving other serious bugs
User: User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pangox
drbd-doc Build-Depends on libgtkmathview-bin, which is obsolete and is
blocking the removal of
Source: src:firefox-esr
Version: FTBFS and embdeded copy
Severity: serious
Tags: upstream ftbfs
Control: clone -1 -2
Control: affects -2 src:firefox
Dear Maintainer,
I could not found the source of the following files
https://sources.debian.org/src/firefox-
Processing control commands:
> severity -1 serious
Bug #947900 [chemical-mime-data] chemical-mime-data: build-depends on
unmaintained gnome-mime-data
Severity set to 'serious' from 'important'
--
947900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947900
Debian Bug Tracking System
Your message dated Sat, 04 Sep 2021 11:33:38 +
with message-id
and subject line Bug#993611: fixed in xrootd 5.3.1-2
has caused the Debian Bug report #993611,
regarding xrootd FTBFS on 32bit: error: no matching function for call to
‘max(off64_t, uint64_t&)’
to be marked as done.
This means
Package: qemu-user-static
Version: 1:6.1+dfsg-4
Severity: critical
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
Since 6.0, qemu-user-static does not seem to work properly through
binfmt. I am a bit lost on how to diagnose that:
13:23 ❱ cat /proc/sys/fs/binfmt_misc/qemu-aarch64
enabled
Package: lintian
Version: 2.104.0
Severity: serious
Hi,
Building the Debian package of Lintian from Git (5de96f0301) and then
running it, for example, on itself results in the error below.
Am assuming it's a dev/prod path issue, and had a glance at the code
but couldn't quite work out why it
Your message dated Sat, 04 Sep 2021 09:18:32 +
with message-id
and subject line Bug#992674: fixed in lmfit-py 1.0.2-1
has caused the Debian Bug report #992674,
regarding scipy breaks lmfit-py autopkgtest
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 4 Sep 2021 08:00:26 +0200
with message-id <20210904060026.ga8...@shell.thinkmo.de>
and subject line Re: Bug#993560: closed by Bastian Blank
(Re: Bug#993560: FTBFS on arch-any)
has caused the Debian Bug report #993560,
regarding FTBFS on arch-any
to be marked as done.
33 matches
Mail list logo
