Bug#963101: cozy-audiobook-player: "Request For Package"
Hi, I am currently working on this package [0]. I would need a sponsor to review and upload the package. Thanks Manuel [0] https://salsa.debian.org/manut/cozy
Bug#1063380: ITP: libuio -- Linux Kernel UserspaceIO helper library
Hi Dima, > On 7 Feb 2024, at 18:27, Dima Kogan wrote: > > Hi. Thanks for your contribution. I looked at the upstream code a tiny > bit, and it looks like it might have portability bug, at least on > big-endian architectures. For instance: > > > https://github.com/missinglinkelectronics/libuio/blob/6ef3d8d096a641686bfdd112035aa04aa16fe81a/irq.c#L78 > > This assumes that sizeof(long)==4. Maybe this is benign, but it would be > nice to fix. Are you upstream or do you know upstream? Can yall fix > these? The kernel expects a 4 byte write here, since unsigned long is defined as at least 32 bit this shall work on all architectures. If your concern is about endianess this is not in the current scope of libuio and needs to be addressed by a higher layer. I am very familiar with library and in close contact with upstream. Best regards Manuel
Bug#1063380: ITP: libuio -- Linux Kernel UserspaceIO helper library
> On 7 Feb 2024, at 18:27, Dima Kogan wrote: > > Hi. Thanks for your contribution. I looked at the upstream code a tiny > bit, and it looks like it might have portability bug, at least on > big-endian architectures. For instance: > > > https://github.com/missinglinkelectronics/libuio/blob/6ef3d8d096a641686bfdd112035aa04aa16fe81a/irq.c#L78 Thanks for having a look. I will take care. > > This assumes that sizeof(long)==4. Maybe this is benign, but it would be > nice to fix. Are you upstream or do you know upstream? Can yall fix > these? I will try to do a MR upstream > > Thanks! >
Bug#1063380: ITP: libuio -- Linux Kernel UserspaceIO helper library
Package: wnpp Severity: wishlist Owner: Manuel Traut X-Debbugs-Cc: debian-de...@lists.debian.org, ma...@mecka.net * Package name: libuio Version : 0.2.8 Upstream Contact: Benedikt Spranger * URL : https://github.com/missinglinkelectronics/libuio * License : LGPL Programming Lang: C Description : Linux Kernel UserspaceIO helper library A small Userspace IO driver helper library. More details about UIO can be found here: https://www.kernel.org/doc/html/latest/driver-api/uio-howto.html UIO can be used to map device memory and interrupts into user-space. It is used to write user-space drivers for devices that do not fit in any existing kernel subsystem. libuio makes it easy to access a UIO device from user-space. It is what is libgpio for GPIOs or libiio for IIO devices. I would need a sponsor to upload this package.
Bug#1036631: still exists in bookworm
Hi Craig, The bug is not fixed in bookworm. Can you please pick the attached patches for stable? Greetings Manuel
Bug#1036631: bugfix is available upstream
Hi,
I added the following two patches to procps:2:4.0.2-3 in bookworm.
This resolved this issue.
Since this bug is also available in bookworm, can you please provide a
update for stable?
Thanks
ManuelFrom 35dc38cb7fcfb71b151a020abb16197b88370337 Mon Sep 17 00:00:00 2001
From: Jim Warner
Date: Wed, 24 May 2023 00:00:00 -0500
Subject: [PATCH 1/2] ps: address missing or corrupted fields with -m option
Coincidentally, a Debian bug report and a gitlab issue
were raised at nearly the same time and are referenced
below. They both dealt with that '-m' (thread) option.
That option forces tasks and their threads to be shown
on separate lines. Also, information may be suppressed
between that main process and any lightweight process.
The bottom line was sometimes a required pids_item may
not have been requested from the library before trying
to display a result. For the best case, some incorrect
results might be shown. However, in the worst case (as
with PIDS_WCHAN_NAME) a segmentation fault is created.
[ After addressing the '-m' option problems, another ]
[ issue was found with that '-F' (extra full format) ]
[ option. The PSR (processor) field was always zero. ]
[ It was addressed in a similar manner to the above. ]
Reference(s):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036631
https://gitlab.com/procps-ng/procps/-/issues/279
Signed-off-by: Jim Warner
---
src/ps/display.c | 7 +++
1 file changed, 7 insertions(+)
Index: procps-4.0.2/src/ps/display.c
===
--- procps-4.0.2.orig/src/ps/display.c
+++ procps-4.0.2/src/ps/display.c
@@ -596,6 +596,13 @@ static void finalize_stacks (void)
// special items with 'extra' used as former pcpu
chkREL(extra)
chkREL(noop)
+ // lastly, any remaining needs ...
+ if (format_flags & FF_Uf)
+chkREL(PROCESSOR);
+ if (thread_flags & TF_U_m) {
+chkREL(PRIORITY);
+chkREL(WCHAN_NAME);
+ }
// now accommodate any results not yet satisfied
f_node = format_list;
From 93b7f05e54293af4919498fceedb236a523336df Mon Sep 17 00:00:00 2001
From: Jim Warner
Date: Fri, 26 May 2023 00:00:00 -0500
Subject: [PATCH 2/2] ps: trade previous fix for final solution to -m option
Well as luck would have it I found yet another missing
field (SCHED_CLASS) that's needed by that '-m' option.
And, while it could just be added to the previous test
of thread_flags and TF_U_m, here is a much better fix.
[ The problem lies with the lists_and_needs function ]
[ where a new format list was created and some print ]
[ functions changed to pr_nop which displays a dash! ]
[ So, by calling the finalize_stacks function before ]
[ calling lists_and_needs, the former will see those ]
[ format nodes before any print function is changed. ]
Reference(s):
May, 2023 - missing fields with -m option
commit 35dc38cb7fcfb71b151a020abb16197b88370337
Signed-off-by: Jim Warner
---
src/ps/display.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
Index: procps-4.0.2/src/ps/display.c
===
--- procps-4.0.2.orig/src/ps/display.c
+++ procps-4.0.2/src/ps/display.c
@@ -596,13 +596,6 @@ static void finalize_stacks (void)
// special items with 'extra' used as former pcpu
chkREL(extra)
chkREL(noop)
- // lastly, any remaining needs ...
- if (format_flags & FF_Uf)
-chkREL(PROCESSOR);
- if (thread_flags & TF_U_m) {
-chkREL(PRIORITY);
-chkREL(WCHAN_NAME);
- }
// now accommodate any results not yet satisfied
f_node = format_list;
@@ -672,8 +665,8 @@ int main(int argc, char *argv[]){
init_output(); /* must be between parser and output */
- lists_and_needs();
finalize_stacks();
+ lists_and_needs();
if(forest_type || sort_list) fancy_spew(); /* sort or forest */
else simple_spew(); /* no sort, no forest */
Bug#1035055: ITP: firmware-imx -- Firmware binary blobs needed on NXP i.MX platforms
Package: wnpp Severity: wishlist Owner: Manuel Traut X-Debbugs-Cc: debian-de...@lists.debian.org, manuel.tr...@mt.com, ma...@mecka.net * Package name: firmware-imx Version : 8.19 Upstream Contact: NXP * URL : https://www.nxp.com/ * License : LA_OPT_NXP_Software_License_v42 Description : Firmware binary blobs needed on NXP i.MX platforms i.MX Firmware including firmware for VPU, DDR, EPDC, HDMI, DP (Display Port), and SDMA To build a working u-boot for i.MX8* at least the DDR train binaries from NXP are needed. More details are available in this document: https://www.nxp.com/docs/en/release-note/IMX_LINUX_RELEASE_NOTES.pdf The package shall provide the files from firmware-imx-8.19.bin: epdc/epdc_ED060XH2C1.fw.nonrestricted epdc/epdc_ED060XH7U2.fw epdc/epdc_E97_V110.fw epdc/epdc_E60_V220.fw epdc/epdc_E60_V110.fw epdc/epdc_E060SCM.fw sdma/sdma-imx7d.bin sdma/sdma-imx51-to3.bin sdma/sdma-imx31-to2.bin sdma/sdma-imx35-to2.bin sdma/sdma-imx35-to1.bin sdma/sdma-imx25-to1.bin sdma/sdma-imx6q.bin sdma/sdma-imx31-to1.bin sdma/sdma-imx53-to1.bin xuvi/vpu_fw_imx8_xuvi.bin ddr/synopsys/ddr4_imem_1d.bin ddr/synopsys/ddr3_dmem_1d_201810.bin ddr/synopsys/ddr4_dmem_2d_201810.bin ddr/synopsys/lpddr4_pmu_train_2d_dmem_202006.bin ddr/synopsys/lpddr4_pmu_train_1d_dmem_202006.bin ddr/synopsys/lpddr4_pmu_train_2d_imem_202006.bin ddr/synopsys/lpddr4_pmu_train_1d_imem.bin ddr/synopsys/ddr4_imem_2d.bin ddr/synopsys/ddr4_imem_1d_202006.bin ddr/synopsys/lpddr4_dmem_1d_v202201.bin ddr/synopsys/lpddr4_pmu_train_2d_imem_201904.bin ddr/synopsys/ddr4_dmem_1d_201810.bin ddr/synopsys/lpddr4_pmu_train_1d_dmem_201904.bin ddr/synopsys/ddr4_dmem_2d.bin ddr/synopsys/lpddr4_pmu_train_2d_dmem.bin ddr/synopsys/lpddr4_pmu_train_1d_imem_202006.bin ddr/synopsys/ddr4_dmem_1d_202006.bin ddr/synopsys/ddr4_dmem_1d.bin ddr/synopsys/lpddr4_pmu_train_1d_dmem.bin ddr/synopsys/ddr4_imem_1d_201810.bin ddr/synopsys/lpddr4_pmu_train_2d_dmem_201904.bin ddr/synopsys/lpddr4_imem_1d_v202201.bin ddr/synopsys/ddr4_imem_2d_202006.bin ddr/synopsys/ddr4_imem_2d_201810.bin ddr/synopsys/ddr3_imem_1d_201810.bin ddr/synopsys/lpddr4_imem_2d_v202201.bin ddr/synopsys/ddr3_dmem_1d.bin ddr/synopsys/ddr4_dmem_2d_202006.bin ddr/synopsys/lpddr4_dmem_2d_v202201.bin ddr/synopsys/lpddr4_pmu_train_1d_imem_201904.bin ddr/synopsys/ddr3_imem_1d.bin ddr/synopsys/lpddr4_pmu_train_2d_imem.bin easrc/easrc-imx8mn.bin vpu/vpu_fw_imx8_enc.bin vpu/vpu_fw_imx8_dec.bin vpu/vpu_fw_imx6q.bin vpu/vpu_fw_imx53.bin vpu/vpu_fw_imx27_TO1.bin vpu/vpu_fw_imx51.bin vpu/vpu_fw_imx6d.bin vpu/vpu_fw_imx27_TO2.bin hdmi/cadence/dp_ls1028a.bin hdmi/cadence/signed_dp_imx8m.bin hdmi/cadence/signed_hdmi_imx8m.bin hdmi/cadence/hdmitxfw.bin hdmi/cadence/hdmirxfw.bin hdmi/cadence/dpfw.bin xcvr/xcvr-imx8mp.bin e.g. in /lib/firmware/imx
Bug#1016963: Please test u-boot for colibri_imx6
Hi vagrant, If you have access to any of these boards, please consider testing u-boot versions as packaged in debian for versions from debian stable (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental (2023.01-rc*) and updating the wiki page if successful and/or replying to 1016...@bugs.debian.org with a positive confirmation... colibri_imx6 this target is only activated in experimental. I tested the package successfully today: U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +) CPU: Freescale i.MX6DL rev1.4 996 MHz (running at 792 MHz) CPU: Commercial temperature grade (0C to 95C) at 66C Reset cause: WDOG DRAM: 512 MiB PMIC: device id: 0x10, revision id: 0x21, programmed Core: 111 devices, 17 uclasses, devicetree: separate MMC: FSL_SDHC: 1, FSL_SDHC: 0 Loading Environment from MMC... OK In:serial@202 Out: serial@202 Err: serial@202 Model: Toradex 0015 Colibri iMX6DL 512MB V1.1A Serial#: 10770584 Net: eth0: ethernet@2188000 Hit any key to stop autoboot: 0 MMC: no card present switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2117 bytes read in 2 ms (1 MiB/s) ## Executing script at 1700 ... Thanks for your support Manuel
Bug#1027899: u-boot-menu: menu is not created by kernel-install command
Package: u-boot-menu Version: 4.1.0 Severity: normal Tags: patch X-Debbugs-Cc: manuel.tr...@mt.com Dear Maintainer, if kernel-install is called manualy the extlinux.conf file is not generated. This can be resolved with an .install file in /usr/lib/kernel/install.d Regards Manuel >From 01a6363deaff470cf6623a2cd8df27dfe283d221 Mon Sep 17 00:00:00 2001 From: Manuel Traut Date: Tue, 22 Nov 2022 16:33:42 +0100 Subject: [PATCH] Add extlinux gen hook on kernel-install Signed-off-by: Manuel Traut --- debian/rules | 3 +++ debian/u-boot-menu.install | 1 + 2 files changed, 4 insertions(+) diff --git a/debian/rules b/debian/rules index 5cb246e..28dfa41 100755 --- a/debian/rules +++ b/debian/rules @@ -2,6 +2,9 @@ %: dh $@ +override_dh_autoreconf: + cp -a zz-u-boot-menu 91-uboot.install + override_dh_installinit: cp -f default debian/u-boot-menu.u-boot.default dh_installinit --name=u-boot diff --git a/debian/u-boot-menu.install b/debian/u-boot-menu.install index 1f801fe..72d229f 100644 --- a/debian/u-boot-menu.install +++ b/debian/u-boot-menu.install @@ -1,3 +1,4 @@ u-boot-update usr/sbin zz-u-boot-menu etc/kernel/postinst.d zz-u-boot-menu etc/kernel/postrm.d +91-uboot.installusr/lib/kernel/install.d -- 2.39.0
Bug#1024329: u-boot: extlinux.conf prompt value is ignored
also posted on the u-boot ML: https://lists.denx.de/pipermail/u-boot/2022-November/499967.html
Bug#1024329: u-boot: extlinux.conf prompt value is ignored
Hi vagrant, On Thu, Nov 17, 2022 at 09:01:59AM -0800, Vagrant Cascadian wrote: > On 2022-11-17, Manuel Traut wrote: > > during testing on the imx6 colibri board i recognized > > that the prompt value of extlinux.conf is ignored. > > > > The attached patch fixes the problem. > > Could you spell this out in a little more detail exactly what is > missing? Maybe cut-and-paste what it looks like with and without the > patch applied? regarding the documentation if there is prompt = 0 in the extlinux.conf it shall not ask the user for input. In combination with timeout = 0 it boots directly into the configured target. https://github.com/u-boot/u-boot/blob/master/common/menu.c#L347 However this does not work, because prompt is set to one per default in the source code and is not read from the extlinux.conf https://github.com/u-boot/u-boot/blob/master/boot/pxe_utils.c#L1328 > I'm also curious why this is noticed with the imx6 colibri board and > presumably not other boards... I have definitely used the > pxeboot/extlinux functionality with many other boards (maybe I'm not > using this specific functionality in this code path, though). This feature is probably broken for all boards. Maybe ordinary users are fine with having a 1 second timeout, however in our use-case booting as fast as possible is important. > > Can it be added to debian or shall I try to submit > > it upstream first? > > Submitting something like this upstream is always a good idea. Feel free > to CC me. I suspect upstream will want more verbosity in the error > description too... Ok, I will do so tomorrow and add you to Cc. Thanks for your support Manuel > Depending on how that goes, I'll consider applying and/or backporting in > Debian. > > Thanks! > > live well, > vagrant > > > From: Manuel Traut > > Date: Thu, 17 Nov 2022 16:38:47 +0100 > > Subject: distro/pxe boot: read prompt value from config > > > > Currently the configuration of prompt in extlinux.conf is > > ignored. > > > > Read it from the file, if not given do not fail. > > > > Signed-off-by: Manuel Traut > > --- > > boot/pxe_utils.c | 5 - > > 1 file changed, 4 insertions(+), 1 deletion(-) > > > > diff --git a/boot/pxe_utils.c b/boot/pxe_utils.c > > index 8133006..a6c56e0 100644 > > --- a/boot/pxe_utils.c > > +++ b/boot/pxe_utils.c > > @@ -1359,7 +1359,10 @@ static int parse_pxefile_top(struct pxe_context > > *ctx, char *p, unsigned long bas > > break; > > > > case T_PROMPT: > > - eol_or_eof(); > > + err = parse_integer(, >prompt); > > + // Do not fail if prompt configuration is missing > > +if (err < 0) > > + eol_or_eof(); > > break; > > > > case T_EOL:
Bug#1024329: u-boot: extlinux.conf prompt value is ignored
Source: u-boot Version: 2021.01+dfsg-5 Severity: normal Tags: patch X-Debbugs-Cc: manuel.tr...@mt.com Hi vagrant, during testing on the imx6 colibri board i recognized that the prompt value of extlinux.conf is ignored. The attached patch fixes the problem. Can it be added to debian or shall I try to submit it upstream first? cu, Manuel From: Manuel Traut Date: Thu, 17 Nov 2022 16:38:47 +0100 Subject: distro/pxe boot: read prompt value from config Currently the configuration of prompt in extlinux.conf is ignored. Read it from the file, if not given do not fail. Signed-off-by: Manuel Traut --- boot/pxe_utils.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/boot/pxe_utils.c b/boot/pxe_utils.c index 8133006..a6c56e0 100644 --- a/boot/pxe_utils.c +++ b/boot/pxe_utils.c @@ -1359,7 +1359,10 @@ static int parse_pxefile_top(struct pxe_context *ctx, char *p, unsigned long bas break; case T_PROMPT: - eol_or_eof(); + err = parse_integer(, >prompt); + // Do not fail if prompt configuration is missing +if (err < 0) + eol_or_eof(); break; case T_EOL:
Bug#1023443: u-boot: Add colibri_imx6 configuration
Am 10.11.2022 um 09:11 hat Vagrant Cascadian geschrieben: > On 2022-11-10, Manuel Traut wrote: Hi vagrant, > > U-Boot 2022.04+dfsg-2 (Apr 10 2022 - 23:28:14 +) > ... > > Can you pick the patch for sid? > > That's not the verison in sid, though. If you can test it on 2022.10 > (currently in sid) and 2023.01-rc1 (currently in git), that would be > great! sorry, I was not aware that there was a newer version in sid. Test, see below. U-Boot 2022.10+dfsg-1.1 (Nov 14 2022 - 09:52:49 +) CPU: Freescale i.MX6SOLO rev1.4 996 MHz (running at 792 MHz) CPU: Commercial temperature grade (0C to 95C) at 52C Reset cause: POR DRAM: 256 MiB PMIC: device id: 0x10, revision id: 0x21, ���Core: 111 devices, 17 uclasses, devicetree: separate MMC: FSL_SDHC: 1, FSL_SDHC: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In:serial@202 Out: serial@202 Err: serial@202 Model: Toradex 0014 Colibri iMX6S 256MB V1.1A Serial#: 10757742 Net: eth0: ethernet@2188000 Hit any key to stop autoboot: 0 MMC: no card present switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 1442 bytes read in 2 ms (704.1 KiB/s) > Generally ask people to test new versions periodically: > > https://wiki.debian.org/U-boot/Status > > Preferrably at least each new upstream version as it's uploaded to > debian sid and/or experimental. That is fine for me. I can add the result to the wiki as soon as the target is activated. Doing it now might confuse people? > > Shall I also test with the new version found in experimental? > > Haven't yet uploaded to experiemental, but in git I've updated to > 2023.01-rc1 recently, maybe will upload that shortly. > > I might upload 2023.01-rc1 before another unstable upload, in either > case, I'll try to include your patch, thanks! The one targeted for experimental also boots like expected: U-Boot 2023.01-rc1+dfsg-1~0.1+nmu1-01626-g3021e2ac5e-dirty (Nov 14 2022 - 09:28:23 +) CPU: Freescale i.MX6SOLO rev1.4 996 MHz (running at 792 MHz) CPU: Commercial temperature grade (0C to 95C) at 46C Reset cause: POR DRAM: 256 MiB PMIC: device id: 0x10, revision id: 0x21, p߽ɕ��� 111 devices, 17 uclasses, devicetree: separate MMC: FSL_SDHC: 1, FSL_SDHC: 0 Loading Environment from MMC... OK In:serial@202 Out: serial@202 Err: serial@202 Model: Toradex 0014 Colibri iMX6S 256MB V1.1A Serial#: 10757742 Net: eth0: ethernet@2188000 Hit any key to stop autoboot: 0 MMC: no card present switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Thanks a lot, Manuel
Bug#1023443: Acknowledgement (u-boot: Add colibri_imx6 configuration)
I was able to build a package with the attached patch that shall apply
to the package in sid.
I tested it with my hardware:
--8<--
Commercial temperature grade DDR3 timings, 32bit bus width.
Trying to boot from MMC1
U-Boot 2022.04+dfsg-2 (Apr 10 2022 - 23:28:14 +)
CPU: Freescale i.MX6SOLO rev1.4 996 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 47C
Reset cause: POR
DRAM: 256 MiB
PMIC: device id: 0x10, revision id: 0x21, programmed
Core: 65 devices, 15 uclasses, devicetree: separate
MMC: FSL_SDHC: 1, FSL_SDHC: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment
auto-detected panel vga-rgb
Display: vga-rgb (640x480)
In:serial
Out: serial
Err: serial
Model: Toradex Colibri iMX6 Solo 256MB V1.1A, Serial# 10673915
Net: eth0: ethernet@2188000
Hit any key to stop autoboot: 0
--8<--
Can you pick the patch for sid?
Shall I also test with the new version found in experimental?
Regards,
Manuel
>From beca702860ef7b9ce60b5c314efff44dce9dcc24 Mon Sep 17 00:00:00 2001
From: Manuel Traut
Date: Fri, 4 Nov 2022 09:16:35 +0100
Subject: [PATCH] u-boot-imx: Add colibri_imx6
(Closes: #1023443)
Signed-off-by: Manuel Traut
---
debian/targets.mk | 4
1 file changed, 4 insertions(+)
diff --git a/debian/targets.mk b/debian/targets.mk
index 235d745277..6e9de55f52 100644
--- a/debian/targets.mk
+++ b/debian/targets.mk
@@ -295,6 +295,10 @@ else ifeq (${DEB_HOST_ARCH},armhf)
# u-boot-imx
+ # Manuel Traut
+ u-boot-imx_platforms += colibri_imx6
+ colibri_imx6_targets := SPL u-boot.img uboot.elf
+
# Marek Vasut
u-boot-imx_platforms += dh_imx6
dh_imx6_targets := u-boot-with-spl.imx uboot.elf
--
2.35.1
Bug#1023443: u-boot: Add colibri_imx6 configuration
Source: u-boot Version: 2021.01+dfsg-5 Severity: wishlist X-Debbugs-Cc: manuel.tr...@mt.com Dear Maintainer, the configuration for colibri_imx6 is not build. If it is fine for you, I could provide a patch that activates it and test on real hardware. Regards, Manuel
Bug#1020917: debos: Please package new upstream release 1.1.0
Package: debos Version: 1.0.0+git20210707.c66a48d-2+b2 Severity: normal X-Debbugs-Cc: manuel.tr...@mt.com Dear Maintainer, there is a new upstream version that fixes some known issues. It would be nice to have this version in Debian (bookworm) -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 5.19.0-1-amd64 (SMP w/6 CPU threads; PREEMPT) Kernel taint flags: TAINT_SOFTLOCKUP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debos depends on: ii busybox1:1.35.0-2 ii debootstrap1.0.127 ii libc6 2.34-8 ii libglib2.0-0 2.74.0-1 ii libostree-1-1 2022.5-3 ii qemu-system-x861:7.1+dfsg-2 ii qemu-user-static 1:7.1+dfsg-2 ii systemd-container 251.4-3 Versions of packages debos recommends: ii bmap-tools 3.6-1 ii bzip2 1.0.8-5+b1 ii e2fsprogs 1.46.6~rc1-1 ii linux-image-amd64 5.19.6-1 ii mount 2.38.1-1 ii ovmf 2022.08-1 ii parted 3.5-2 ii udev 251.4-3 ii xz-utils 5.2.5-2.1 ii zip3.0-12 debos suggests no packages. -- no debconf information
Bug#1017640: RFS: libusbgx/0.2.0-2 [ITP] -- C library encapsulating the kernel USB gadget-configfs
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "libusbgx": * Package name: libusbgx Version : 0.2.0-2 Upstream Author : Krzysztof Opasiak * URL : https://github.com/linux-usb-gadgets/libusbgx * License : GPL-2.0+, __AUTO_PERMISSIVE__, LGPL-2.1+ * Vcs : https://salsa.debian.org/debian/libusbgx Section : libs The source builds the following binary packages: libusbgx-dev - Development files for libusbgx libusbgx-doc - Documentation files for libusbgx libusbgx2 - C library encapsulating the kernel USB gadget-configfs To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libusbgx/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/libu/libusbgx/libusbgx_0.2.0-2.dsc Changes for the initial release: libusbgx (0.2.0-2) unstable; urgency=medium . * Initial release. (Closes: #1016019) Regards, -- Manuel Traut
Bug#1016019: ITP: libusbgx -- libusbgx is a C library encapsulating the kernel USB gadget-configfs
Package: wnpp Severity: wishlist Owner: Manuel Traut X-Debbugs-Cc: debian-de...@lists.debian.org, manuel.tr...@mt.com * Package name: libusbgx Version : 0.2.0 Upstream Author : Krzysztof Opasiak * URL : https://github.com/linux-usb-gadgets/libusbgx * License : GPL, LGPL Programming Lang: C Description : libusbgx is a C library encapsulating the kernel USB gadget-configfs It provides routines for creating and parsing USB gadget devices using the configfs API. Currently, all USB gadget configfs functions that can be enabled in kernel release 3.11 (Linux for Workgroups!) are supported. The package is used in many embedded Linux based products. I would need a sponsor and help for uploading the package.
Bug#903016: python3-libvirt: import fails with current python interpreter in sid
Package: python3-libvirt Version: 4.0.0-1+b1 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, the package is broken on sid: The following packages were automatically installed and are no longer required: iputils-arping liblogging-stdlog0 libnginx-mod-http-auth-pam libnginx-mod-http-dav-ext libnginx-mod-http-echo libngin libnginx-mod-http-xslt-filter libnginx-mod-mail libnginx-mod-stream libplacebo4 libwireshark10 libwiretap7 libwscodec Use 'sudo apt autoremove' to remove them. The following packages have been kept back: medcon xmedcon 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up python3-libvirt (4.0.0-1+b1) ... File "/usr/lib/python3/dist-packages/libvirtaio.py", line 49 from asyncio import async as ensure_future ^ SyntaxError: invalid syntax dpkg: error processing package python3-libvirt (--configure): installed python3-libvirt package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: python3-libvirt E: Sub-process /usr/bin/dpkg returned an error code (1) The problem is fixed upstream with this commit: https://github.com/libvirt/libvirt-python/commit/e27528204c887b4099b892a0237766f187959737#diff-cd56dd4108fa77f26cb6c1e6358beba1 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-libvirt depends on: ii libc6 2.27-3 ii libvirt0 4.3.0-1 ii python3 3.6.6-1 Versions of packages python3-libvirt recommends: ii libvirt-daemon 4.3.0-1 python3-libvirt suggests no packages. -- debconf-show failed >From e27528204c887b4099b892a0237766f187959737 Mon Sep 17 00:00:00 2001 From: Cole Robinson Date: Mon, 25 Jun 2018 14:14:57 -0400 Subject: [PATCH 1/2] libvirtaio: Fix compat with python 3.7 In python 3.7, async is now a keyword, so this throws a syntax error: File "/usr/lib64/python3.7/site-packages/libvirtaio.py", line 49 from asyncio import async as ensure_future ^ SyntaxError: invalid syntax Switch to getattr trickery to accomplish the same goal Reviewed-by: Pavel Hrdina Reviewed-by: Andrea Bolognani Signed-off-by: Cole Robinson --- libvirtaio.py | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/libvirtaio.py b/libvirtaio.py index 1c432dd..328e6f2 100644 --- a/libvirtaio.py +++ b/libvirtaio.py @@ -43,10 +43,13 @@ import warnings import libvirt -try: -from asyncio import ensure_future -except ImportError: -from asyncio import async as ensure_future +# Python < 3.4.4 doesn't have 'ensure_future', so we have to fall +# back to 'async'; however, since 'async' is a reserved keyword +# in Python >= 3.7, we can't perform a straightforward import and +# we have to resort to getattr() instead +ensure_future = getattr(asyncio, "ensure_future", None) +if not ensure_future: +ensure_future = getattr(asyncio, "async") class Callback(object): -- 2.18.0
Bug#844566: qemu-system-x86: ipv6 and dns is broken with netdev user
Hi, i see the same effect with latest qemu from upstream. The bugreport for upstream qemu is here: https://bugs.launchpad.net/qemu/+bug/1642421 Regards, Manuel
Bug#844566: qemu-system-x86: ipv6 and dns is broken with netdev user
Package: qemu-system-x86
Version: 1:2.7+dfsg-3+b1
Severity: important
Tags: ipv6
Dear Maintainer,
dhcp inside qemu returns an ipv6 address as dns-server. However this is not
working. If i replace it with the ipv4 address '10.0.0.2' dns is working
again. I would expect that the qemu emulated dhcp server responds either an
ipv4 configuration that is working or its dns server/forwarder listens on the
ipv6 address returned by the emulated dhcp server.
I started qemu with the following command:
qemu-system-x86_64 -enable-kvm -M pc -device virtio-rng-pci -device
virtio-net-pci,netdev=user.0 -drive file=buildenv.img,if=virtio,bus=1,unit=0
-no-reboot -netdev user,id=user.0,hostfwd=tcp::5022-:22,hostfwd=tcp::7587-:7588
-m 1024 -usb -nographic -smp 4
buildenv.img is a debian jessie amd64 installation.
Inside qemu the network is configured to use dhcp:
$ cat /etc/network/interfaces
allow-hotplug eth0
iface eth0 inet dhcp
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 52:54:00:12:34:56
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::5054:ff:fe12:3456/64 Scope:Link
inet6 addr: fec0::5054:ff:fe12:3456/64 Scope:Site
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3215 (3.1 KiB) TX bytes:3638 (3.5 KiB)
$ cat /etc/resolv.conf
nameserver fec0::3
$ arp google.de
google.de: Host name lookup failure
$ strace -f arp google.de
...
socket(PF_INET6, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 4
connect(4, {sa_family=AF_INET6, sin6_port=htons(53), inet_pton(AF_INET6,
"fec0::3", _addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0
poll([{fd=4, events=POLLOUT}], 1, 0)= 1 ([{fd=4, revents=POLLOUT}])
sendto(4, "\17\320\1\0\0\1\0\0\0\0\0\0\6google\2de\0\0\1\0\1", 27,
MSG_NOSIGNAL, NULL, 0) = 27
poll([{fd=4, events=POLLIN}], 1, 5000) = 0 (Timeout)
poll([{fd=4, events=POLLOUT}], 1, 0)= 1 ([{fd=4, revents=POLLOUT}])
sendto(4, "\17\320\1\0\0\1\0\0\0\0\0\0\6google\2de\0\0\1\0\1", 27,
MSG_NOSIGNAL, NULL, 0) = 27
poll([{fd=4, events=POLLIN}], 1, 5000) = 0 (Timeout)
close(4)= 0
...
$ echo nameserver 10.0.0.2 > /etc/resolv.conf
$ arp google.de
google.de (216.58.208.35) -- no entry
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 4.8.6 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages qemu-system-x86 depends on:
ii ipxe-qemu 1.0.0+git-20161027.b991c67-1
ii libaio1 0.3.110-3
ii libasound2 1.1.2-1
ii libbluetooth3 5.43-1
ii libbrlapi0.65.4-2
ii libc6 2.24-5
ii libcacard0 1:2.5.0-2
ii libfdt1 1.4.0+dfsg-2
ii libgcc1 1:6.2.0-13
ii libglib2.0-02.50.2-1
ii libgnutls30 3.5.6-4
ii libjpeg62-turbo 1:1.5.1-2
ii libncurses5 6.0+20160917-1
ii libnettle6 3.3-1
ii libpixman-1-0 0.34.0-1
ii libpng16-16 1.6.26-1
ii libpulse0 9.0-5
ii libsasl2-2 2.1.27~72-g88d82a3+dfsg-1
ii libsdl1.2debian 1.2.15+dfsg1-4
ii libseccomp2 2.3.1-2
ii libspice-server10.12.8-1
ii libtinfo5 6.0+20160917-1
ii libusb-1.0-02:1.0.21-1
ii libusbredirparser1 0.7.1-1
ii libuuid12.29-1
ii libvdeplug2 2.3.2+r586-2+b1
ii libx11-62:1.6.3-1
ii libxen-4.8 4.8.0~rc5-1
ii libxenstore3.0 4.8.0~rc5-1
ii qemu-system-common 1:2.7+dfsg-3+b1
ii seabios 1.9.3-2
ii zlib1g 1:1.2.8.dfsg-2+b3
Versions of packages qemu-system-x86 recommends:
ii qemu-utils 1:2.7+dfsg-3+b1
Versions of packages qemu-system-x86 suggests:
ii kmod 23-1
ii ovmf 0~20160813.de74668f-2
pn qemu-block-extra
pn samba
ii sgabios 0.0~svn8-3
pn vde2
-- no debconf information
Bug#776057: apt: packages not marked auto-installed / autoremove broken
Package: apt Version: 0.9.7.9+deb7u7 Severity: important Dear Maintainer, i'm afraid marking several packages as auto_installed is currently broken in wheezy. I found out an easy way to reproduce may situation: % debootstrap wheezy wheezy http://ftp.de.debian.org/debian % chroot wheezy % apt-get install libtiff4 # installs libjbig0 libjpeg8 as extra packages % apt-get remove libtiff4 % apt-get autoremove libtiff4 # doesn't remove libjpeg8 and libjbig0 % aptitude why libjbig0 i vim-common Recommends vim | vim-gnome | vim-gtk | vim-athena | vim-nox | vim-tiny p vim-gtkDependslibgdk-pixbuf2.0-0 (= 2.22.0) p libgdk-pixbuf2.0-0 Dependslibtiff4 (= 3.9.5-2) p libtiff4 Dependslibjbig0 % aptitude why libjpeg8 i vim-common Recommends vim | vim-gnome | vim-gtk | vim-athena | vim-nox | vim-tiny p vim-gtkDependslibgdk-pixbuf2.0-0 (= 2.22.0) p libgdk-pixbuf2.0-0 Dependslibjpeg8 (= 8c) I believe the problem is, that the packages are not tagged as 'Automatically installed': % aptitude show libjbig0 Package: libjbig0 State: installed Automatically installed: no Multi-Arch: same Version: 2.0-2+deb7u1 Priority: extra Section: libs Maintainer: Michael van der Kolff mvanderko...@gmail.com Architecture: amd64 Uncompressed Size: 98.3 k Depends: libc6 (= 2.2.5) PreDepends: multiarch-support Description: JBIGkit libraries Homepage: http://www.cl.cam.ac.uk/~mgk25/jbigkit/ however i can remove both packages by % apt-get remove libjbig0 libjpeg8 and no further dependencies are removed. I expect that apt-get autoremove removes those both libraries. If I do the same, with another package, eg. vim-nox auto-removal of the installed dependencies works. -- Package-specific info: -- apt-config dump -- APT ; APT::Architecture amd64; APT::Build-Essential ; APT::Build-Essential:: build-essential; APT::Install-Recommends 1; APT::Install-Suggests 0; APT::NeverAutoRemove ; APT::NeverAutoRemove:: ^firmware-linux.*; APT::NeverAutoRemove:: ^linux-firmware$; APT::NeverAutoRemove:: ^linux-image.*; APT::NeverAutoRemove:: ^kfreebsd-image.*; APT::NeverAutoRemove:: ^linux-restricted-modules.*; APT::NeverAutoRemove:: ^linux-ubuntu-modules-.*; APT::NeverAutoRemove:: ^gnumach$; APT::NeverAutoRemove:: ^gnumach-image.*; APT::Never-MarkAuto-Sections ; APT::Never-MarkAuto-Sections:: metapackages; APT::Never-MarkAuto-Sections:: restricted/metapackages; APT::Never-MarkAuto-Sections:: universe/metapackages; APT::Never-MarkAuto-Sections:: multiverse/metapackages; APT::Never-MarkAuto-Sections:: oldlibs; APT::Never-MarkAuto-Sections:: restricted/oldlibs; APT::Never-MarkAuto-Sections:: universe/oldlibs; APT::Never-MarkAuto-Sections:: multiverse/oldlibs; APT::Architectures ; APT::Architectures:: amd64; APT::Compressor ; APT::Compressor::. ; APT::Compressor::.::Name .; APT::Compressor::.::Extension ; APT::Compressor::.::Binary ; APT::Compressor::.::Cost 1; APT::Compressor::gzip ; APT::Compressor::gzip::Name gzip; APT::Compressor::gzip::Extension .gz; APT::Compressor::gzip::Binary gzip; APT::Compressor::gzip::Cost 2; APT::Compressor::gzip::CompressArg ; APT::Compressor::gzip::CompressArg:: -9n; APT::Compressor::gzip::UncompressArg ; APT::Compressor::gzip::UncompressArg:: -d; APT::Compressor::bzip2 ; APT::Compressor::bzip2::Name bzip2; APT::Compressor::bzip2::Extension .bz2; APT::Compressor::bzip2::Binary false; APT::Compressor::bzip2::Cost 3; APT::Compressor::xz ; APT::Compressor::xz::Name xz; APT::Compressor::xz::Extension .xz; APT::Compressor::xz::Binary xz; APT::Compressor::xz::Cost 4; APT::Compressor::xz::CompressArg ; APT::Compressor::xz::CompressArg:: -6; APT::Compressor::xz::UncompressArg ; APT::Compressor::xz::UncompressArg:: -d; APT::Compressor::lzma ; APT::Compressor::lzma::Name lzma; APT::Compressor::lzma::Extension .lzma; APT::Compressor::lzma::Binary xz; APT::Compressor::lzma::Cost 5; APT::Compressor::lzma::CompressArg ; APT::Compressor::lzma::CompressArg:: --format=lzma; APT::Compressor::lzma::CompressArg:: -9; APT::Compressor::lzma::UncompressArg ; APT::Compressor::lzma::UncompressArg:: --format=lzma; APT::Compressor::lzma::UncompressArg:: -d; APT::CompressorName ; APT::CompressorExtension .; APT::CompressorBinary ; APT::CompressorCost 100; APT::CompressorCompressArg ; APT::CompressorCompressArg:: -9; APT::CompressorUncompressArg ; APT::CompressorUncompressArg:: -d; Dir /; Dir::State var/lib/apt/; Dir::State::lists lists/; Dir::State::cdroms cdroms.list; Dir::State::mirrors mirrors/; Dir::State::extended_states extended_states; Dir::State::status /var/lib/dpkg/status; Dir::Cache var/cache/apt/; Dir::Cache::archives archives/; Dir::Cache::srcpkgcache srcpkgcache.bin; Dir::Cache::pkgcache pkgcache.bin; Dir::Etc etc/apt/; Dir::Etc::sourcelist
Bug#748043: qemu-user-static: qemu-arm-static bug in signal handling avoids using mono
Package: qemu-user-static Version: 2.0.0+dfsg-4 Severity: normal Tags: upstream patch Dear Maintainer, running mono in a chroot environment with qemu-user-static is not posible because at least one signal used during termination of mono is routed to the host. This can be reproduced by: debootstrap --include=mono-runtime --foreign --arch=armel wheezy mono-test http://ftp.de.debian.org//debian; cp /usr/bin/qemu-arm-static mono-test/usr/bin mount -t proc none mono-test/proc mount -o bind /dev mono-test/dev mount -o bind /sys mono-test/sys chroot mono-test ../debootstrap/debootstrap --second-stage exit mount -t proc none mono-test/proc mount -o bind /sys mono-test/sys chroot mono-test QEMU_STRACE=1 /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe This will block on a futex: --8-- 18663 sched_yield(0,0,2582980,0,0,2582928) = 0 18663 clock_gettime(1,-150996384,2,1,2585016,2585600) = 0 18663 tgkill(18663,18664,30,18664,30,-161951744) = 0 18663 futex(0x00293774,FUTEX_PRIVATE_FLAG|FUTEX_WAIT,0,NULL,NULL,0) --8-- If you use mono within strace on a native x86 box you can see, that signals between threads are used during termination: strace -f -o log.txt /usr/bin/mono /usr/lib/mono/4.0/gacutil.exe --8-- 14075 sched_yield() = 0 14075 tgkill(14075, 14083, SIGPWR) = 0 14075 futex(0x983f00, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ... 14083 ... futex resumed ) = ? ERESTARTSYS (To be restarted) 14083 --- SIGPWR (Power failure) @ 0 (0) --- 14083 futex(0x983f00, FUTEX_WAKE_PRIVATE, 1) = 1 14075 ... futex resumed ) = 0 14083 rt_sigsuspend(~[INT QUIT ABRT TERM XCPU RTMIN RT_1] unfinished ... 14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 24) = 3 14078 ... futex resumed ) = 0 14078 futex(0x94da20, FUTEX_WAKE_PRIVATE, 1) = 1 14077 ... futex resumed ) = 0 14075 futex(0x94d9a4, FUTEX_CMP_REQUEUE_PRIVATE, 1, 2147483647, 0x94da20, 26 unfinished ... --8-- This also blocks the installation of libnunit2.6-cil within a armel chroot, because it uses mono in its postinst script. E.g. (/usr/bin/mono /usr/share/mono/MonoGetAssemblyName.exe /usr/lib/cli/nunit.core-2.6/nunit.core.dll) Obviously the same as described in: http://lists.opensuse.org/opensuse-arm/2011-12/msg0.html is happening here. There is an openSuSE patch against qemu: https://build.opensuse.org/package/view_file/Virtualization:Qemu/qemu/0002-XXX-work-around-SA_RESTART-race-wit.patch?expand=1 This patch also applies against qemu from backports-wheezy and resolves this issue. As it seems, that this issue is not Debian specific i will also report it to the qemu project and reference this bug report. -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (500, 'stable') Architecture: armel (armv7l) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698782: libc6: pthread_mutexattr_setrobust is not exported
Package: libc6 Version: 2.11.3-4 Severity: minor The non-posix versions of mutexattr_setrobust are not exported by libpthread: root@p:~/x# strings /lib/libpthread.so.0 | grep mutexattr_setrobust pthread_mutexattr_setrobust_np but they are defined in the pthread.h header file: root@p:~/x# grep mutexattr_setrobust /usr/include/pthread.h extern int pthread_mutexattr_setrobust (pthread_mutexattr_t *__attr, extern int pthread_mutexattr_setrobust_np (pthread_mutexattr_t *__attr, so applications using the _np variant compile, but cannot be linked. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: armel (armv5tejl) Kernel: Linux 2.6.32-5-versatile Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libc6 depends on: ii libc-bin 2.11.3-4 Embedded GNU C Library: Binaries ii libgcc1 1:4.4.5-8 GCC support library libc6 recommends no packages. Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy pn glibc-doc none (no description available) ii locales 2.11.2-10 Embedded GNU C Library: National L -- debconf information: glibc/upgrade: true glibc/restart-services: glibc/disable-screensaver: glibc/restart-failed: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
