Ah, I forgot to handle the case where /srv/local-apt-repository doesn't exist
when the package is installed. This updated patch (and my latest push on
salsa.d.o) should fix that.
>From bd063c0a9ba11ff53ba9b233ed5c63a64ee97495 Mon Sep 17 00:00:00 2001
From: Darsey Litzenberger
Date:
tags 1085265 + patch
thanks
I've taken these patches, added a few more, and created a merge request at:
https://salsa.debian.org/debian/local-apt-repository/-/merge_requests/2
I've also attached the same series of patches to this message.
--
Darsey Litzenber
| true
# ^ this can fail during a partial write to the directory (which
# would be detected by the loop), so ignore errors here
--
Darsey Litzenberger
Package: tayga
Version: 0.9.2-8
Severity: normal
RFC 8215[1] allocates 64:ff9b:1::/48 as a block of well-known prefixes
for networks that contain more than one NAT64 translator. However,
tayga refuses to run when one of those prefixes is configured.
For example, when "prefix 64:ff9b:1:fffe::
On Sun, Aug 11, 2019 at 03:14:16PM +0200, Christian Marillat wrote:
Dear Maintainer,
/var/lib/dkms/virtualbox-guest/6.0.10/build/vboxvideo/vbox_ttm.c:31:10: fatal
error: ttm/ttm_page_alloc.h: No such file or directory
#include
^~
compilation terminated.
But bevare
ubico-tools not installable. (Closes: #934861)
>From cbe7fc670f2d449bc30e1bd1a12ee500d0d2f689 Mon Sep 17 00:00:00 2001
From: Darsey Litzenberger
Date: Thu, 15 Aug 2019 16:55:44 -0700
Subject: [PATCH 1/3] Fix python-yubico-tools not installable
The package depended on python:any (>= 2.8~), whi
Package: python-yubico-tools
Version: 1.3.2-2.1
Severity: important
The python-yubico-tools package in sid cannot be installed. The recent
NMU of the python-yubico added "X-Python-Version: >= 2.8" to the
debian/control, which resulted in a bogus binary dependency on
python:any (>= 2.8~).
Th
On Sun, May 26, 2019 at 06:07:35PM +0100, Ben Hutchings wrote:
There's no such severity as "severe", so I'll mark this "important".
[...]
I agree this should be enabled; in fact I thought it already was.
Oh... *blink* Oh, I meant to use 'serious' (the lowest available RC
severity), to ensure
Package: src:linux
Version: 5.0.2-1~exp1
Severity: severe
Please build Debian kernels with CONFIG_ALLOW_LOCKDOWN_LIFT_BY_SYSRQ
enabled.
I have a laptop with UEFI Secure Boot support. I dual-boot Windows and
I also want to use Secure Boot to make sure that Debian kernels are
running. Beyond t
I'm seeing the same thing on a MacBookAir5,2 device with this hardware:
02:00.0 Network controller [0280]: Broadcom Limited BCM43224 802.11a/b/g/n
[14e4:4353] (rev 01)
Subsystem: Apple Inc. AirPort Extreme [106b:00e9]
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory
10 matches
Mail list logo
