Source: libbpp-seq
Version: 2.4.1-10.1
Severity: normal
Tags: patch
This dependency will be automatically generated by ${shlibs:Depends}
and avoids a co-dependency on both libbpp-core4 and libbpp-core4t64.
diff -Nru libbpp-seq-2.4.1/debian/control libbpp-seq-2.4.1/debian/control
---
Source: groonga-normalizer-mysql
Version: 1.2.3-2
Severity: normal
This dependency is already provided via ${shlibs:Depends}.
diff -Nru groonga-normalizer-mysql-1.2.3/debian/control
groonga-normalizer-mysql-1.2.3/debian/control
--- groonga-normalizer-mysql-1.2.3/debian/control 2024-03-03
Source: gfal2
Version: 2.22.1-1.1build2
Severity: normal
Tags: patch
The proper shlib dependency will automatically be added by ${shlib:deps}.
This avoids a co-dependency on libgfal-srm-ifce1 and libgfal-srm-ifce1t64.
diff -Nru gfal2-2.22.1/debian/control gfal2-2.22.1/debian/control
---
Source: rshim-user-space
Version: 2.0.12+debian-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
The switch to fuse3 appears to have introduced a build issue for 32-bit
architectures such as armhf:
From
Source: rshim-user-space
Version: 2.0.20+debian-1
Severity: minor
X-Debbugs-Cc: Taihsiang Ho (tai271828)
>From lintian:
W: rshim-user-space source: build-depends-on-obsolete-package Build-Depends:
pkg-config => pkgconf
N:
N: The package build-depends on a package that has been superseded.
forwarded 1060398 https://gitlab.com/kraxel/virt-firmware/-/issues/10
tags 1060398 + upstream
severity 1060398 minor
thanks
Thanks Michael. We don't currently install the impacted code, but I've
gone ahead and reported this upstream.
On Thu, Feb 15, 2024 at 10:06:35AM +, Simon John wrote:
> I have the same problem when changing settings or even
> starting an existing aarch64 VM in virt-manager, the error
> I get is:
>
> Error starting domain: operation failed: Unable to find
> 'efi' firmware that is compatible with the
On Sun, Feb 11, 2024 at 08:46:32PM +0100, Salvatore Bonaccorso wrote:
> Does this split look good to you?
Yes, thank you!
-dann
Thanks Salvatore.
The first 7 are now fixed upstream, so I'm preparing an upload for
those. Fixes for CVE-2023-45236 and CVE-2023-45237 are still in the
works. Should we split those into separate bugs?
-dann
fixed 967994 2023.05-1
thanks
Yes, there is a fix for this in upstream edk2-stable202305. However,
the CVE is marked as rejected:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14560
But it seems to have been treated a valid issue.
There is a note about requesting a new CVE:
fixed 1014468 2022.11-1
thanks
CVE-2021-38576 was fixed in 2021.11-1.
CVE-2021-38577 was rejected.
CVE-2021-38578 was fixed in 2022.11-1.
-dann
On Sun, Dec 17, 2023 at 07:53:52PM +0100, Luca Boccassi wrote:
> On Sun, 17 Dec 2023, 17:45 dann frazier, wrote:
>
> > On Thu, Dec 07, 2023 at 08:58:23PM +, Luca Boccassi wrote:
> > > On Wed, 15 Nov 2023 05:54:23 -0700 dann frazier
> > > wrote:
> >
On Thu, Dec 07, 2023 at 08:58:23PM +, Luca Boccassi wrote:
> On Wed, 15 Nov 2023 05:54:23 -0700 dann frazier
> wrote:
> > Package: wnpp
> > Severity: wishlist
> > Owner: dann frazier
> > X-Debbugs-Cc: debian-de...@lists.debian.org
> >
> > * Pac
tag 1052173 + patch
tag 1052173 + fixed-upstream
thanks
I found that this problem does not occur with latest upstream, so I used
bisection to identify the fix. The problem no longer occurs after
applying this fix to the existing package:
commit 124efd03f3cb9b1df819134eb7cb6683497be9b1
Author:
Package: wnpp
Severity: wishlist
Owner: dann frazier
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: virt-firmware
Version : 23.10
Upstream Contact: Gerd Hoffmann
* URL : https://gitlab.com/kraxel/virt-firmware
* License : GPL-2+
Programming
tag 1049840 + pending
thanks
Hi Lucas,
This does not seem to be a problem with rebuilding per se. I can not
reproduce it, and I don't see a way a "dirty tree" could cause this
failure. The log shows a timeout in a pyexpect script, so I
hypothesize that the 2nd build just ran slower than the
On Sat, Sep 23, 2023 at 11:15:45AM +0100, Simon John wrote:
> Thanks for looking into this!
>
> I was hoping we could revert the offending edk2 commit in debian rather than
> getting every guest os vendor to update their shim - which would mean only
> fresh installs would work.
>
> Red Hat seem
OK, I finally found some time to debug this. I debugged it with an
Ubuntu VM that used shim 15.7, but I suspect it is the same issue with
Fedora 38 and AlmaLinux 9.2.
shim 15.6 introduced the following commit:
commit 226fee25ffcbd29988399ba080c7706eb1d52251
Author: Peter Jones
Date: Thu Dec 2
Package: colord
Version: 1.4.6-3
Severity: normal
I noticed that this service has been stuck in a respawn/segfault loop on
my system.
[...]
[ 4969.616799] colord[22761]: segfault at 55fd30d664d5 ip 7f47219ccc01 sp
7ffecd7fd3a8 error 4 in libgobject-2.0.so.0.7800.0[7f47219a1000+34000]
We've been discussing this with upstream at
https://github.com/OP-TEE/optee_client/pull/355 , which is an attempt
to make emulation a runtime option. An argument is being made that
it should remain a build time switch, to avoid having to ship the
emulation code in production environments. We'll
Source: optee-client
Version: 3.21.0-1
Severity: wishlist
tee-supplicant can be configured at build-time to either use a real RPMB
or to emulate one. The default is to emulate one, and that appears
to be what the Debian binary does today. Please provide support for using
a real RPMB.
# first bad commit: [1c4dfadb4611ef511816dfdfbdb37d7d100b5a4b] ArmPkg/CpuDxe:
Implement EFI memory attributes protocol
Reverting that from latest upstream seems to make the problem go
away. But the reason is not clear to me. This commit registers a
protocol, but it doesn't appear to use that
Package: binutils
Version: 2.40.90.20230714-2
Severity: normal
Tags: upstream
edk2 has begun to FTBFS after recent binutils updates. Log follows below[*],
as well as a log using gcc -v[**].
This is reproducible with upstream binutils. I bisected the failure to
upstream commit fb221fba1a5 ("Add
Package: wnpp
Severity: wishlist
Owner: dann frazier
X-Debbugs-Cc: debian-de...@lists.debian.org, Liming Sun ,
Taihsiang Ho
* Package name: rshim-user-space
Version : 2.0.7
Upstream Contact: Mellanox Technologies
* URL : https://github.com/Mellanox/rshim-user-space
Source: libpcap
Version: 1.10.3-1
Severity: wishlist
Tags: patch
This would enable the RDMA sniffer in tcpdump.
--- libpcap-1.10.3/debian/controlorig 2023-02-08 14:31:21.136166108 -0700
+++ libpcap-1.10.3/debian/control 2023-02-08 14:22:13.560898916 -0700
@@ -7,6 +7,7 @@ Build-Depends:
tag 1025656 + confirmed
thanks
Thank you for the bug report. Something does seem to be wrong with the
qemu-efi-aarch64. I'll see if I can find the cause through bisection.
On Wed, Dec 07, 2022 at 11:22:10AM -0500, James Bottomley wrote:
> On Wed, 2022-12-07 at 17:04 +0100, Ard Biesheuvel wrote:
> > On Wed, 7 Dec 2022 at 17:02, Gerd Hoffmann wrote:
> > >
> > > On Wed, Dec 07, 2022 at 09:14:39AM -0500, James Bottomley wrote:
> > > > On Wed, 2022-12-07 at 15:09
On Wed, Dec 7, 2022 at 10:36 AM Vincent Danjean wrote:
>
> Package: ovmf
> Version: 2022.11-1
> Severity: normal
>
> Hi,
>
> I was thinking my bug was #1016359, but with the additionnal
> info, it is a different one. So, I'm opening this bug as asked.
>
> ovmf in sid does not allow one to
On Tue, Dec 06, 2022 at 09:21:21PM +, Thorsten Glaser wrote:
> Hi dann,
>
> >OK, then I think there may be multiple conflated issues here. Let's
> >focus on the original use case you described - a VM created with
> >virt-manager using a SCSI controller doesn't work. You tried
>
> Nonono, not
On Tue, Dec 06, 2022 at 07:25:27PM +, Thorsten Glaser wrote:
> Hi dann,
>
> > Could you confirm the last version that worked for you - perhaps
>
> I have never booted an EFI system before; this VM was the first
> time for me, so I do not have a “last version” either way.
>
> As I said,
tag 1016359 + moreinfo
thanks
Hi Thorsten,
Could you confirm the last version that worked for you - perhaps
testing some builds from snapshot.debian.org if you're unsure? If you
can provide the libvirt XML from your VM, that may be useful as well.
-dann
On Tue, Dec 06, 2022 at 06:56:49AM +0100, Gerd Hoffmann wrote:
> On Mon, Dec 05, 2022 at 04:36:15PM -0700, dann frazier wrote:
> > On Tue, Jul 26, 2022 at 12:46:39PM -0700, Michael D Kinney wrote:
> > > The email addresses for the reviewers of the MptScsi and
> > >
On Tue, Nov 29, 2022 at 04:47:58PM +0100, Vincent Danjean wrote:
> Hi,
>
> I can confirm that virtio-scsi does not work anymore
> (and that this is indeed really annoying).
It looks like upstream changed the default to disabled ahead of stable202208:
commit
) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Workaround test failures by using modules symlinked into a temp dir.
+(Closes: #1022365).
+
+ -- dann frazier Sun, 27 Nov 2022 15:07:39 -0700
+
pdsh (2.34-0.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru pdsh-2.34
This seems to be the source of the problem:
pdsh@ip-10-84-234-180: module path "/<>/src/modules/.libs"
insecure.
pdsh@ip-10-84-234-180: "/build": Owner not root, current uid, or pdsh
executable owner
pdsh@ip-10-84-234-180: Couldn't load any pdsh modules
Indeed, I can reproduce by building in a
Weird, tests pass for me locally. Will look into it.
Would you consider adding host argument support without providing a
[ppa] implementation? Users could then opt-in by adding a [ppa]
section to their /etc/dput.cf (or ~/.dput.cf). Here's just that piece
of the Ubuntu delta:
diff -urpN dput-1.1.2.orig/doc/man/dput.1 dput-1.1.2/doc/man/dput.1
---
).
+ * Updated Homepage URL (closes: #940539).
+ * Add Brazilian Portuguese debconf templates translation, thanks to
+Adriano Rafael Gomes (closes: #811540).
+
+ -- dann frazier Wed, 10 Aug 2022 11:35:52 -0600
+
pdsh (2.31-3) unstable; urgency=low
* Add Italian translation (closes: #764088
On Wed, Aug 10, 2022 at 04:23:56PM +0200, Bastian Blank wrote:
> I don't know how to debug it. With older versions it works. On amd64 it
> also works.
hey Bastian,
makedumpfile often needs updates to adjust to changes in upstream
kernel internals, and that tends to lag the kernel releases
tag 1015759 + confirmed
thanks
On Wed, Jul 20, 2022 at 04:45:03PM +, Robert wrote:
> Package: ovmf
> Version: 2022.05-2
> Severity: normal
> X-Debbugs-Cc: robert.schneide...@sap.com
>
> Dear Maintainer,
>
> I'm trying to test an image creation mechanism by booting the resulting
> image with
Package: openocd
Version: 0.11.0-1+b1
Severity: wishlist
I'm using openocd to debug an Nvidia Bluefield device using rshim. In order
to do this, I needed to rebuild the package with --enable-rshim.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy:
On Wed, Mar 16, 2022 at 09:15:16PM +0100, Mara Sophie Grosch wrote:
> Package: ovmf
> Version: 2022.02-2
> Severity: important
> Tags: upstream patch
>
> Hi,
>
> the latest edk2 stable release (202202) introduces an issue with the
> NVMe controller in QEMU, recognizing it as not support NVMe
On Sun, Mar 06, 2022 at 04:47:58PM +, Etienne Dechamps wrote:
> Package: ovmf
> Version: 2022.02-1
> Severity: important
> Control: fixed -1 2021.11-1
>
> An ovmf regression somewhere between 2021.11-1 and 2022.02-1 makes it
> impossible to use a TPM in Windows guest VMs (tested with various
Package: systemtap-sdt-dev
Version: 4.6-1
Severity: normal
dtrace generates .c code in a predictable temporary file which makes it
susceptible to crashes. I've seen this happen in practice when rebuilding
libvirt/focal on a system with 48 cores. The race window is wide enough that
the crash is
Source: rootlesskit
Version: 0.14.6-1
Severity: normal
rootlesskit uses the "nindent" template function in its help output.
This wasn't added to golang-github-urfave-cli-v2 until version 2.3:
See: https://github.com/urfave/cli/commit/be9c0378
$ git tag --contains be9c0378
v2.3.0
rootlesskit
Source: golang-github-moby-sys
Version: 0.0~git20201113.5a29239-1
Severity: normal
Tags: patch
Rebuilding golang-github-moby-sys with an older golang-golang-x-sys-dev
fails:
golang.org/x/sys/unix
path/filepath
github.com/moby/sys/mountinfo
# github.com/moby/sys/mountinfo
On Fri, Feb 18, 2022 at 1:27 PM Limonciello, Mario
wrote:
>
> [Public]
>
> >
> > On Fri, Feb 18, 2022 at 08:16:00PM +, Limonciello, Mario wrote:
> > > [Public]
> > >
> > > The package is present in Ubuntu (which shares the same source package as
> > Debian). So would prefer to keep it in
On Fri, Feb 18, 2022 at 08:16:00PM +, Limonciello, Mario wrote:
> [Public]
>
> The package is present in Ubuntu (which shares the same source package as
> Debian). So would prefer to keep it in place.
Just a thought, but couldn't you modify the build to dynamically add
this relationship
On Mon, Jan 10, 2022 at 02:50:27PM -0600, Glenn Washburn wrote:
> Package: qemu-efi-arm
> Version: 2020.11-2
>
> Hello Maintainers,
>
> There seems to be an issue with the 32-bit ARM UEFI firmware VARS file,
> at /usr/share/AAVMF/AAVMF32_VARS.fd. When I try to use it, I get a Data
> exception
(sorry for the late response)
On Fri, Oct 29, 2021 at 01:03:32PM -0500, Glenn Washburn wrote:
> On Thu, 28 Oct 2021 12:00:09 -0600
> dann frazier wrote:
>
> > On Thu, Oct 28, 2021 at 11:19:06AM -0500, Glenn Washburn wrote:
> > > On Thu, 28 Oct 2021 07:46:11 -0600
&
On Thu, Oct 28, 2021 at 11:19:06AM -0500, Glenn Washburn wrote:
> On Thu, 28 Oct 2021 07:46:11 -0600
> dann frazier wrote:
> > On Tue, Oct 26, 2021 at 07:31:38PM -0500, Glenn Washburn wrote:
> > > Package: ovmf-ia32
> > > Version: 2020.11-4
> > >
> &g
severity 997913 wishlist
thanks
On Tue, Oct 26, 2021 at 07:31:38PM -0500, Glenn Washburn wrote:
> Package: ovmf-ia32
> Version: 2020.11-4
>
> Hello Maintainers,
>
> I'd like ovmf-ia32 to install a file useable by QEMU's -bios option.
> Currently the package only installs
On Tue, Aug 31, 2021 at 10:00:18PM +0300, Michael Tokarev wrote:
> 31.08.2021 18:02, dann frazier wrote:
>
> > char device redirected to /dev/pts/14 (label charserial0)
> > about to fire assert: salen=2
> > qemu-system-x86_64: ../../util/qemu-sockets.c:1352:
> > s
Here's an updated assert using 1:6.1+dfsg-3:
char device redirected to /dev/pts/8 (label charserial0)
qemu-system-x86_64: ../../util/qemu-sockets.c:1349:
socket_sockaddr_to_address_unix: Assertion `salen >=
sizeof(su->sun_family) + 1 && salen <= sizeof(struct sockaddr_un) +
su->sun_path[0] ? 1 :
On Tue, Aug 31, 2021 at 01:13:40AM +0300, Michael Tokarev wrote:
> dann, can you please add a printf to util/qemu-sockets.c
> before the assert() which is failing, to see what's the
> value of salen? since you can reproduce this..
> I'm still not 100% sure what the actual problem is -
> or _which_
On Tue, Aug 31, 2021 at 01:13:40AM +0300, Michael Tokarev wrote:
> dann, can you please add a printf to util/qemu-sockets.c
> before the assert() which is failing, to see what's the
> value of salen? since you can reproduce this..
> I'm still not 100% sure what the actual problem is -
> or _which_
On Mon, Aug 30, 2021 at 02:38:30PM -0600, dann frazier wrote:
> On Sat, Aug 28, 2021 at 02:53:01PM +0300, Michael Tokarev wrote:
> > On 27.08.2021 23:25, dann frazier wrote:
> > > Package: qemu-system-x86
> > > Version: 1:6.1+dfsg-1
> > > Severity: normal
>
On Sat, Aug 28, 2021 at 02:53:01PM +0300, Michael Tokarev wrote:
> On 27.08.2021 23:25, dann frazier wrote:
> > Package: qemu-system-x86
> > Version: 1:6.1+dfsg-1
> > Severity: normal
> >
> >
> > A VM that I created with either virt-manager or virtinst some
Package: qemu-system-x86
Version: 1:6.1+dfsg-1
Severity: normal
A VM that I created with either virt-manager or virtinst sometime ago now
crashes when I attempt to start it under QEMU 6.1.
2021-08-27 20:12:17.236+: starting up libvirt version: 7.6.0, package: 1
(Andrea Bolognani Thu, 19
; urgency=medium
+
+ * Address Boot Guard TOCTOU vulnerability (CVE-2019-11098) (Closes: #991495)
+
+ -- dann frazier Wed, 18 Aug 2021 16:57:56 -0600
+
edk2 (2020.11-2) unstable; urgency=medium
* autopkgtest: Add allow-stderr to Restrictions to fix failure.
diff -Nru edk2-2020.11/debian/patches
Source: edk2
Severity: normal
Once the default gcc becomes gcc-11, edk2 will begin to FTBFS:
"arm-linux-gnueabihf-gcc" -MMD -MF
/<>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/ArmPkg/Library/CompilerIntrinsicsLib/CompilerIntrinsicsLib/OUTPUT/Arm/ashldi3.obj.deps
-mthumb -march=armv7-a -E -x
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package kdump-tools
[ Reason ]
Addresses two bugs:
[ Benjamin Drung ]
* Fix broken status log messages when dumping w/ FTP (Closes: #991412).
[ dann frazier
Package: makedumpfile
Version: 1:1.6.8-4
Severity: important
makedumpfile in buster does not support extraction of dmesg from buster's
kernel:
[7.032459] kdump-tools[517]: The dumpfile is saved to STDOUT.
[7.034898] kdump-tools[517]: makedumpfile Completed.
[7.054470]
Package: kdump-tools
Version: 1:1.6.8.3
Severity: important
X-Debbugs-Cc: Benjamin Drung
Due to use of the wrong variable names, dumps to an FTP server log incorrect
messages. For example:
[7.598933] kdump-tools[498]: kdump-tools: saved vmcore via FTP in :.
when it should be:
[
On Wed, Jul 7, 2021 at 12:17 PM Guilherme Piccoli
wrote:
>
> Hi Troy, I'd like to enforce that request! We want to upgrade crash
> version on next Ubuntu release, and the correct process would be to
> match Debian's Sid version.
> Thanks in advance,
Hi Guillherme!
Just a heads-up that Debian is
Source: systemd
Version: 247.3-5
I noticed that systemd-machined was failing to start on an arm64
box. This box had armhf enabled, and turns out systemd had been
cross-graded over to systemd:armhf[*]. It still had
systemd-container:arm64 installed, so now I had an arm64
tag 990464 + moreinfo
thanks
On Tue, Jun 29, 2021 at 06:25:48PM -0500, Kody Barks wrote:
> Package: kdump-tools
> Version: 1:1.6.5-1
>
> When the kernel panics, it loads the kdump kernel correctly but this kernel
> is unable to use NVME, making it unable to mount the root filesystem and
> thus
) UNRELEASED; urgency=medium
+
+ * Fix issue where 'showregs' can cause certain Samsung devices
+to go offline. (Closes: #989840)
+
+ -- dann frazier Mon, 14 Jun 2021 11:50:30 -0600
+
nvme-cli (1.12-5) unstable; urgency=medium
* Add uuid-runtime as dependency. (Closes: #970637)
diff -Nru
nvme
Package: nvme-cli
Version: 1.12-5
Severity: important
Tags: upstream fixed-upstream
nvme show-regs has been found to cause certain Samsung controllers
(MZ1L21T9HCLS in particular) to go offline:
[963314.311332] nvme nvme2: controller is down; will reset: CSTS=0x3,
PCI_STATUS=0x10
On Fri, Jun 11, 2021 at 1:57 AM Rich Ercolani wrote:
>
> Package: kdump-tools
> Version: 1:1.6.5-1
> Severity: important
>
> Dear Maintainer,
>
> Installed kdump-tools appear to work, echo 'c' | sudo tee /proc/sysrq-trigger
> boots the crashkernel and
> takes a dump and reboots, but attempting
@@
+manpages (5.10-2) UNRELEASED; urgency=medium
+
+ * kernel_lockdown.7: Remove description of unsupported lockdown lift
+mechanism via SysRq. (Closes: #989580) (LP: #1931171)
+
+ -- dann frazier Thu, 10 Jun 2021 13:13:28 -0600
+
manpages (5.10-1) unstable; urgency=medium
* New upstream
Upon proof-reading, I realized I missed another reference:
https://lore.kernel.org/linux-man/20210607221943.78414-1-dann.fraz...@canonical.com/T/#u
2021-06-07 15:55:43.0 -0600
@@ -0,0 +1,45 @@
+From 09df87e9ee3e1a429a2c1709dfd16ec8ff0f6160 Mon Sep 17 00:00:00 2001
+From: dann frazier
+Date: Wed, 26 May 2021 11:34:55 -0600
+Subject: [PATCH] kernel_lockdown.7: Remove description of lifting via SysRq
+ (not upstream)
+
+The patch
Package: manpages
Version: 5.10-1
Severity: normal
Tags: upstream patch
The patch that implemented lockdown lifting via SysRq ended up getting
dropped[*] before the feature was merged upstream, but the man page still
describes it.
I've submitted a patch upstream which has been accepted by a
Package: linux-base
Version: 4.6
Severity: normal
Tags: patch
Using argv:
$ linux-version sort 5.8.0-50-generic 5.8.0-50-generic-64k
5.8.0-50-generic
5.8.0-50-generic-64k
Using stdin:
$ cat versions.txt
5.8.0-50-generic
5.8.0-50-generic-64k
$ cat versions.txt | linux-version sort
=medium
+
+ [ Ioanna Alifieraki ]
+ * Fix failure of dmesg. creation on 5.10+ kernels.
+(Closes: #985896) (LP: #1921403).
+ * Fix makedumpfile failure on arm64 with 5.4 kernels.
+(Closes: #986594) (LP: #1879214)
+
+ -- dann frazier Wed, 07 Apr 2021 16:32:38 -0600
+
makedumpfile (1:1.6.8-3
).
+
+ -- dann frazier Mon, 22 Mar 2021 21:39:59 -0600
+
kdump-tools (1:1.6.8.2) unstable; urgency=medium
* debian/control: Add Vcs-* tags.
diff -Nru kdump-tools-1.6.8.2/debian/kdump-config.in
kdump-tools-1.6.8.3/debian/kdump-config.in
--- kdump-tools-1.6.8.2/debian/kdump-config.in 2021-02
On Mon, Mar 22, 2021 at 11:31 AM dann frazier wrote:
> Thanks for the report Ioanna! Could you test the branch here? I'm
> still trying to figure out how to propose it in a merge...
> https://salsa.debian.org/dannf/kdump-tools/-/commits/bug985716
Oh, figured it out - please feel free t
On Mon, Mar 22, 2021 at 9:33 AM Ioanna Alifieraki
wrote:
>
> Package: kdump-tools
> Version: 1:1.6.8.2
> Severity: normal
> X-Debbugs-Cc: ioanna-maria.alifier...@canonical.com
>
> Dear Maintainer,
>
> Commit 38fe0c8f41fd (Support compressing the dumpfile) [1]
> changes the call to makedumpfile :
fyi, I submitted a PR here:
https://github.com/mati75/openbox-debian/pull/14
Package: openbox
Version: 3.6.1-9
Severity: normal
There's a seemingly obvious bug in screen.c that can cause an infinite loop.
A patch was submitted upstream to fix it:
https://github.com/AlexGoinsNV/openbox-multiXscreen-bugfix/commit/2635c87d160aa5f6f9e91e290678e99111788d57
Would it be
On Thu, Feb 25, 2021 at 6:21 AM Stefan Haberland wrote:
>
> Am 25.02.21 um 08:30 schrieb Christian Borntraeger:
> >
> > On 24.02.21 23:40, dann frazier wrote:
> >> Source: s390-tools
> >> Version: 2.15.1-2
> >>
> >> I'm one of the main
Source: s390-tools
Version: 2.15.1-2
I'm one of the maintainers of kdump-tools, which has a need to manipulate
the kernel command line parameters in boot loader configurations.
Currently zipl provides no way to do this without modifying
/etc/zipl.conf directly. It would be helpful if there was
On Mon, Jan 4, 2021 at 10:34 AM Christoph Biedl
wrote:
>
> Control: tags 979248 confirmed
>
> dann frazier wrote...
>
> > Source: clevis
> > Version: 15-1
> > Severity: normal
> >
> > Now that clevis-dracut depends on dracut[*], the autopkgtest depen
Source: clevis
Version: 15-1
Severity: normal
Now that clevis-dracut depends on dracut[*], the autopkgtest dependencies
are no longer satisfiable causing the tests to fail. clevis-dracut and
clevis-initramfs cannot be installed at the same time, as dracut conflicts
with initramfs-tools.
[*]
-dereference-CVE-2019.patch
+
+ -- dann frazier Tue, 15 Dec 2020 12:30:28 -0700
+
edk2 (0~20181115.85588389-3+deb10u2) buster; urgency=medium
* Fix integer overflow in DxeImageVerificationHandler. (CVE-2019-14562)
diff -Nru
edk2-0~20181115.85588389/debian/patches/CryptoPkg-BaseCryptLib-fix-NULL
/CryptoPkg-BaseCryptLib-fix-NULL-dereference-CVE-2019.patch
+
+ -- dann frazier Tue, 15 Dec 2020 12:30:28 -0700
+
edk2 (0~20181115.85588389-3+deb10u2) buster; urgency=medium
* Fix integer overflow in DxeImageVerificationHandler. (CVE-2019-14562)
diff -Nru
edk2-0~20181115.85588389/debian
Package: qemu-system-x86
Version: 1:5.2+dfsg-2
Severity: normal
One of my libvirt/QEMU guests is now segfaulting on startup:
Thread 1 (Thread 0x7fcd275e5e80 (LWP 829788)):
#0 audio_init (dev=dev@entry=0x0, name=name@entry=0x5590b2b8a27b "hda") at
../../audio/audio.c:1712
#1 0x5590b2890f7a
forcemerge 973783 974844
thanks
Since we are targetting the OvmfPkgX64 platform, you currently have to
explicitly disable S3 support on the QEMU command line:
-global ICH9-LPC.disable_s3=1
We are looking at switching to the OvmfPkgIa32X64 platform, which
would not require disabling S3.
Looking at git history, I see this commit that makes an assertion
counter to my test results:
http://git.grml.org/?p=grml2usb.git;a=commit;h=7a6e10df
Previous to that commit, I did not see fsync being used. Michael: is
that commit message based on experimentation? If so, perhaps neither
sync
Package: grml2usb
Version: 0.18.3
Severity: normal
Tags: patch
grml2usb autopkgtest frequently fail in Ubuntu's CI. For example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/g/grml2usb/20201116_194744_cbe0f@/log.gz
severity 973730 wishlist
thanks
I had the same concern when I first started working on this package,
but I learned that there is no requirement that a package be buildable
on any architecture where it can be used. If you believe that is
incorrect, please cite a policy section.
On Tue, Nov 3, 2020 at 12:45 PM Christian Kastner wrote:
>
> Control: severity -1 wishlist
>
> On 11/2/20 8:44 PM, Ryutaroh Matsumoto wrote:
> > Control: reassign -1 src:edk2> Control: forcemerge -1 842683
> >
> > I am hoping the above control commands merge 973571 and 842683
> > (I don't know
Package: network-manager
Version: 1.27.90-3
Severity: normal
After upgrading to 1.27.91-1, I've found that connecting to my VPN causes
my existing "nameserver" option to disappear from /etc/resolv.conf.
Before connecting:
# Generated by NetworkManager
nameserver 192.168.1.1
After
Package: conserver-server
Version: 8.2.4-2+b1
Severity: important
The postinst fails when installing conserver-server:
$ sudo apt install conserver-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically
Package: conserver-server
Version: 8.2.4-2+b1
Severity: normal
Tags: upstream
I'm using an access list that looks like this:
access * {
trusted 127.0.0.1,10.2.3.4,10.5.6.0/18,10.6.7.0/18;
allowed 127.0.0.1,10.2.3.4,10.5.6.0/18,10.6.7.0/18;
}
After upgrading from 8.2.1-1 to
Package: peek
Version: 1.5.1-1
Severity: normal
I attempted to record a portion of my (wayland) desktop this morning (mp4), and
found on playback that the video was just black except for the mouse pointer.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT
Package: clevis-initramfs
Version: 13-2
Severity: normal
Tags: patch
I've prepared a branch that backports several fixes to the initramfs support:
https://salsa.debian.org/dannf/clevis/-/commits/v13-initramfs-fixes
Here's a summary extracted from the changelog:
* initramfs: Fix parsing of
-SecDataD.patch
+ - d/p/0002-SecurityPkg-DxeImageVerificationLib-assign-WinCertif.patch
+ - d/p/0003-SecurityPkg-DxeImageVerificationLib-catch-alignment-.patch
+
+ -- dann frazier Thu, 17 Sep 2020 13:45:52 -0600
+
edk2 (0~20181115.85588389-3+deb10u1) buster; urgency=medium
* Fix numeric
On Fri, Aug 28, 2020 at 10:38:25PM +0200, Thomas Goirand wrote:
> Hi Dann,
>
> If you look into the minissdpd configuration script (ie:
> /var/lib/dpkg/info/minissdpd.config) it does read what's in the
> /etc/default/minissdpd configuration file before attempting to configure
> the package. Maybe
1 - 100 of 2273 matches
Mail list logo
