> recent u-boot platforms in Debian, and u-boot has been blocked from
> migration to testing partly because of this.
>
> As the bookworm freeze approaches, this is getting to be... worrysome!
That Ordoid N2 board that I had was damaged about year ago.
I have not procured a replacement to it since then.
So I cannot test u-boot on Odroid N2 in the foreseeable future.
Reco
N ports work.
- USB ports work too.
The kernel from the experimental just misses the usual:
- pca963x for WAN/WIFI leds
- wifi.
Wifi requires out of tree module anyway, and its outside of the scope of
this bug report.
Sincerely yours, Reco
ready built u-boot for amlogic/g12a.
I beleive we've discussed this issue at debian-arm, [1].
Sincerely yours, Reco
[1] https://lists.debian.org/msgid-search/87v9evu2yt.fsf@yucca
-- System Information:
Debian Release: 10.6
APT prefers stable-updates
APT policy: (500, 'stable-
-boot-amlogic in its current form is unsuitable for the task.
I beleive we've discussed this issue at debian-arm, [1].
Sincerely yours, Reco
[1] https://lists.debian.org/msgid-search/87v9evu2yt.fsf@yucca
-- System Information:
Debian Release: 10.6
APT prefers stable-updates
APT policy: (50
ip is disabled in Debian kernels, so please
consider building it as a module
Sincerely yours, Reco
-- Package-specific info:
** Version:
Linux version 4.19.0-8-rpi (debian-ker...@lists.debian.org) (gcc version 8.3.0
(Debian 8.3.0-6)) #1 Debian 4.19.98-1 (2020-01-26)
** Command line:
bcm2708_fb.fb
00080 f9402c00 (f9401400)
[ 181.148838] ---[ end trace 04c9f90c72f843fa ]---
I can reproduce this problem on both QEMU and a real hardware, and as far as I
can tell both aarch64 and armhf are affected.
Sincerely yours, Reco
-- Package-specific info:
** Version:
Linux version 4.19.0-5-arm64 (debi
Debian's kernel source tree, but is currently disabled.
Tainted status of the current kernel comes from self-built bcm2835_v4l2.
Sincerely yours, Reco
-- Package-specific info:
** Version:
Linux version 4.19.0-5-arm64 (debian-ker...@lists.debian.org) (gcc version
8.3.0 (Debian 8.3.0-7)) #1 SMP D
Hi.
On Mon, Feb 18, 2019 at 05:09:12PM +0100, Cyril Brulebois wrote:
> Checking this on real hardware would be great, trying to put everyone
> involved in the loop through cc.
Confirming that the patched kernel booted successfully on
Armada385/Caiman.
Reco
Hi.
On Sun, Feb 17, 2019 at 08:27:34PM +0100, Cyril Brulebois wrote:
> Hi,
>
> Reco (2019-02-17):
> > Did this already in QEMU (virt board).
> > 4.9.135-1 works.
> > 4.9.144-1 (next one) is broken.
>
> Is there any chance you could share how to get such
dy in QEMU (virt board).
4.9.135-1 works.
4.9.144-1 (next one) is broken.
The problem is - 4.9.144-1 introduced large amount of changes, including
two Spectre mitigations.
My attempts to build a kernel with CONFIG_SPECTRE=n yielded unbootable
kernels, which may mean that:
a) Spectre mitigations are not related to the problem.
b) My kernel-rebuilding skill could use some improvement.
Reco
Hi all.
I'd like to add that plain armmp (non-lpae) is broken too.
At least for Armada385/Caiman and QEMU's virt.
Reco
yours, Reco
-- System Information:
Debian Release: 9.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)
Kernel: Linux 4.18.0-0.bpo.3-armmp (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=U
Dear Maintainer,
I'd like to add that the problem includes chrony too - 50-ntp.conf refers to
non-existent "chronyd" serivce (actual one's called "chrony").
I propose to include this patch that solves the problem for me.
Reco
--- a/dhcpcd-hooks/50-ntp.conf
/"ham" list, and this kind
of problem should never reproduce if both lists contain something.
Attached patch solves the issue for me.
Sincerely yours, Reco
--- a/src/word.c 2018-10-05 07:12:10.281153971 +
+++ b/src/word.c 2018-10-05 07:12:03.937217631 +
@@ -37,6 +37,10 @@
tended otherwise.
I meant '\s'. Attaching modified patch.
Sincerely yours, Reco
--- a/usr/share/logwatch/scripts/services/mdadm 2017-01-21 19:44:03.0 +0300
+++ b/usr/share/logwatch/scripts/services/mdadm 2018-10-02 11:50:37.950642398 +0300
@@ -37,7 +37,7 @@
open(MDADM,"md
yours, Reco
-- Package-specific info:
** Version:
Linux version 4.9.0-8-armmp (debian-ker...@lists.debian.org) (gcc version 6.3.0
20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21)
** Command line:
console=ttyS0,115200 root=/dev/mapper/xx-root ro quiet appar
l 2>&1"
Which, of course, fails with "redirection unexpected".
Suggested fix is attached to this bug report.
Sincerely yours, Reco
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable
including:
deny /proc/acpi/* rwx,
to all Apparmor profiles that are provided by lxc package.
And, since this can be considered a security issue, feel free to tag the
bug as 'serious'.
Sincerely yours, Reco
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT po
void) X509_PUBKEY_get0_param(NULL, NULL, 0, &algor, key);
as the result of X509_PUBKEY_get0_param is not checked anywhere anyway.
Reco
-- System Information:
Debian Release: 9.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x8
archive_read_open_fd was also using for reading and saving archives.
Original patch did not address these, this one does.
Reco
--- archivemount-0.8.7.orig/archivemount.c
+++ archivemount-0.8.7/archivemount.c
@@ -450,7 +450,7 @@ build_tree( const char *mtpt )
return archive_errno
neously assumes that all files in the archive are empty
(zip).
Attached patch workarounds the problem by using
archive_read_open_filename instead, which solves the issue for me.
Reco
--- archivemount-0.8.7.orig/archivemount.c
+++ archivemount-0.8.7/archivemount.c
@@ -450,7 +450,7 @@ build_tr
Package: libpam-cgroup
Version: 0.41-6
Severity: important
Dear Maintainer,
Current stable version for libpam-cgroup suffers from severe programming
error, which prevents libpam-cgroup from doing anything at all.
libpam-cgroup calls 'cgroup_change_cgroup_uid_gid_flags' libcgroup
function with CG
ere's nothing
upstart-specific in the package, for example.
Therefore, there're only two cases to document - systemd one (being a
default init in jessie, this case deserves special treatment indeed),
and a generic one (i.e. anything other than systemd).
Both cases were addressed (I ho
-fashioned way by appending README.Debian to
libvirt-daemon-system.examples?
I don't *that* familiar with these new dh_ tricks :(
And, a usual thing - hereby transferring an authorship of this patch
and all appropriate rights to the Debian Libvirt Maintainers.
Reco
diff --git a/debian/READ
authorship of this patch and all appropriate rights to the Debian
Libvirt Maintainers.
Reco
diff --git a/debian/libvirt-daemon.NEWS b/debian/libvirt-daemon.NEWS
index 59bdd40..d7a23ac 100644
--- a/debian/libvirt-daemon.NEWS
+++ b/debian/libvirt-daemon.NEWS
@@ -1,3 +1,12 @@
+libvirt (1.2.9-3~) unst
on unsuspecting
servers is a drawback in my book. Especially if said mechanism has
less-than-stellar security record.
At least, please update NEWS.Debian (or README.Debian) for libvirt with
explanation of libvirt's usage of policykit-1.
Reco
--
To UNSUBSCRIBE, email to debian-bugs-d
Package: libvirt-daemon-system
Version: 1.2.9-3~bpo70+1
Severity: minor
Dear Maintainer,
A recent upload of backported libvirt packages introduced policykit-1
hard dependency on libvirt-daemon-system package.
Such dependency is unnecessary strict, as 'polkit' authentication type
(according to th
Package: src:linux
Version: 3.14.13-2~bpo70+1
Severity: normal
Dear Maintainer,
Current backported version of Linux kernel running in qemu-system-ppc64 panics
on shutdown with:
[ 567.737855] Oops: Exception in kernel mode, sig: 4 [#1]
[ 567.738864] SMP NR_CPUS=32 NUMA pSeries
[ 567.739615] M
Package: isc-dhcp-client
Version: 4.2.2.dfsg.1-5+deb70u6
Severity: normal
Dear Maintainer,
Both stable and current unstable versions of isc-dhcp-client in
Debian/kFreeBSD do not configure network interface with address received
from DHCPv6 server (ia-n
Hi.
Today the problem was fixed in this upstream commit:
http://libvirt.org/git/?p=libvirt.git;a=commit;h=5fc590ad9f4
Please consider uploading fixed version of libvirt and friends.
An upload to backports would be appreciated too.
Reco
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
Package: zpaq
Version: 1.10-1
Severity: wishlist
Dear Maintainer,
upstream has released several major versions of zpaq since the initial
packaging of this fine software (current version being 6.43).
Please consider updating the package.
-- System Information:
Debian Release: 7.3
APT prefers s
7;s /dev/initctl is a pipe actually.
Sincerely yours, Reco
PS I'm not subscribed to this list, in case of further questions please
CC me.
--- a/src/util/virinitctl.c 2013-12-18 11:13:10.078432196 +0400
+++ b/src/util/virinitctl.c 2013-12-18 11:26:50.0 +0400
@@ -24,7 +24,10 @@
#include
#
Package: libvirt-bin
Version: 1.1.4-2~bpo70+1
Severity: important
Dear Maintainer,
As of versions 1.1.4 (current backported one) and 1.2.0 (current
experimental one) libvirt's implementation for LXC containers lacks
basic sanity checks in container shutdown implementation.
One can trace the pro
33 matches
Mail list logo
