Package: mplayer
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: benjamin.poir...@gmail.com
Dear Maintainer,
The mplayer package is currently not installable in Sid:
root@vsid:/tmp# apt install mplayer
Reading package lists... Done
Building dependency tree... Done
Reading
Package: firmware-amd-graphics
Version: 20230625-2
Severity: normal
X-Debbugs-Cc: benjamin.poir...@gmail.com
Dear Maintainer,
My laptop, Lenovo ThinkPad P14s Gen 4 with AMD Ryzen 7 PRO 7840U w/
Radeon 780M Graphics SoC, fails to enter suspend.
When I try to suspend, in ~9/10 cases, the suspend
I also see this issue with the following drive, nvme1 on my system:
Model Number: Samsung SSD 970 EVO Plus 1TB
Firmware Version: 2B2QEXM7
PCI Vendor/Subsystem ID:0x144d
This has been going on for months and until recently the output of
On 2021-03-05 10:59 +0100, Michael Biebl wrote:
[...]
>
> Is Scott the user who initially encountered this issue on Cumulus Linux 4?
>
Scott is another Cumulus employee working on this issue.
I asked about involving the original reporter here but no success,
unfortunately.
On 2021-03-04 13:38 +0100, Michael Biebl wrote:
[...]
>
> This does look like a reasonable candidate for a buster backport.
> Have you verified, that this commit fixes the crash you are seeing?
I have not been able to reproduce the issue myself.
According to the discussion that led to the
Package: systemd
Version: 241-7~deb10u4
Severity: important
Tags: upstream patch
Dear Maintainer,
A user of Cumulus Linux 4, which uses some Debian Buster packages
including systemd, reported a systemd crash:
2021-03-03T20:59:58.426342+00:00 systemd[1]: Reloading.
On 2020-09-06 15:43 +0200, Bernhard Übelacker wrote:
> Control: fixed -1 1:2.26.0-1
>
>
> Dear Maintainer,
> I tried to have a look and found that it
> showed the message: Error: can't read "::main_status": no such variable
>
> But starting with version 1:2.26.0-1 I could not see
> this message
I think that the wrong "Bug-Debian" tag was inserted in
debian/patches/protobuf_generated_classes_no_inheritance.patch:
Description: Fix build with latest protobuf
Origin: gentoo
Source: mozc
Version: 2.23.2815.102+dfsg-9
Followup-For: Bug #963244
FYI, the following patch fixes the build failure,
https://github.com/google/mozc/issues/460#issuecomment-489511210
rsion 1.14.4-2 where it would appear as "From:
Benjamin Poirier ".
On 2020-05-26 17:10 +0300, Adrian Bunk wrote:
> Control: severity -1 normal
> Control: tags -1 - ftbfs
>
> On Tue, May 26, 2020 at 11:58:19AM +0900, Benjamin Poirier wrote:
> > Source: crash
> > Severity: serious
> > Tags: upstream patch ftbfs
> > Justi
Source: crash
Severity: serious
Tags: upstream patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
The crash package sometimes fails to build when dpkg-buildpackage is
invoked with -j > 1:
# dpkg-buildpackage -us -uc -j4
Package: git-gui
Version: 1:2.25.0-1
Severity: normal
When running `git gui blame` and using "Show history context", git-gui pops up
an "Application Error" window which says 'Error: can't read "::main_status":
no such variable'. Clicking "OK" closes the window and the rest of the
functionality
On 2020/01/16 15:11 +0100, Stéphane Glondu wrote:
> Le 14/01/2020 à 02:26, Benjamin Poirier a écrit :
> > The coccinelle package has been uninstallable for many weeks in unstable:
> >
> > root@f3:~# apt install coccinelle
> > [...]
> > The following
Source: coccinelle
Version: 1.0.4.deb-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The coccinelle package has been uninstallable for many weeks in unstable:
root@f3:~# apt install coccinelle
Reading package lists... Done
Building dependency tree
Reading state
On 2020/01/07 10:12, Michael Jeanson wrote:
> On 2020-01-06 7:46 p.m., Benjamin Poirier wrote:
> > I'm not sure if it's related but I saw almost the same error on last
> > upgrade (but for 5.4.0-2):
> >
> > depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file()
I'm not sure if it's related but I saw almost the same error on last
upgrade (but for 5.4.0-2):
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open
builtin file
'/var/tmp/mkinitramfs_J2sneW/lib/modules/5.4.0-2-amd64/modules.builtin.bin'
and I now get:
root@vsid:~#
Package: lttng-tools
Version: 2.11.0-3
Severity: normal
The CONFDIR variable (set from `./configure --sysconfdir=/etc [...]`) is not
expanded correctly when building the documentation of the lttng-tools
packages. For example, lttng-sessiond(8) claims automatic loading of tracing
session
2.0.5-1
ii libnettle6 3.4.1-1
Versions of packages iputils-ping recommends:
ii libcap2-bin 1:2.25-2
iputils-ping suggests no packages.
-- no debconf information
>From 769a6790437e883d72eebbabd06d33a05a0340ca Mon Sep 17 00:00:00 2001
From: Benjamin Poirier
Date: Thu, 26 Dec 2019 10:44
Thanks for your analysis. I have the same problem and a simple
workaround for the time being is to do:
ln -s /tmp/.wine-1000/ /run/user/1000/wine
On 2019/12/05 11:34, Michael Biebl wrote:
[...]
>
> The old 73-usb-net-by-mac.rules file contained:
>
> TEST!="/etc/systemd/network/99-default.link", \
>
> This check can't be expressed via .link files.
> The new 73-usb-net-by-mac.link link file does respect the net.ifnames=0
> kernel
Package: linux-perf-4.19
Version: 4.19.67-2+deb10u2
Severity: normal
Tags: upstream
perf embeds a python interpreter and the debian linux source package has
debian/rules.d/tools/perf/Makefile:MAKE_PERF += PYTHON=/usr/bin/python3
However, many of the scripts in tools/perf/scripts/python, executed
On 2019/10/03 13:34, Michael Biebl wrote:
> Hi
>
> Am 03.10.19 um 10:17 schrieb Benjamin Poirier:
> > Package: udev
> > Version: 243-2
> > Severity: normal
> >
> > /lib/udev/rules.d/73-usb-net-by-mac.rules prevents the renaming of network
> > interfac
Package: udev
Version: 243-2
Severity: normal
/lib/udev/rules.d/73-usb-net-by-mac.rules prevents the renaming of network
interfaces from usb adapters using the systemd.link(5) mechanism.
The latter is implemented using /lib/udev/rules.d/80-net-setup-link.rules
which is ineffective because
24 matches
Mail list logo
