Hi again,
* Nicolas Schodet [2025-04-25 19:18]:
> > I have not found this patch in BTS neither did I found any MR for
> > imlib2. [...]
> Sorry, I did not send it as it was a quick & dirty test. I cleaned it up
> and attached it to this message in case you choose to use it
31d20c55c7fba Mon Sep 17 00:00:00 2001
From: Nicolas Schodet
Date: Thu, 24 Apr 2025 13:11:40 +0200
Subject: [PATCH] Fix dynamic loading using RTLD_LOCAL
Add patches/link-modules-with-libimlib2.patch. Use the configure script
--enable-rtld-local-support option to enable it.
Gbp-Dch: Full
Clo
Control: reassign -1 libimlib2 1.12.4-1
Control: affects -1 src:libimage-imlib2-perl
Thanks
Hi,
* Andreas Tille [250424 12:48]:
> [...]
> Thus I investigated a bit and found out the problem is caused by the
> Upgrade from imlib 1.12.3 to 1.12.4.
Thanks, I used this information as a starting poi
* Santiago Vila [2025-03-23 12:35]:
> Thanks a lot for the bug tidy up. I'm using "src:" here instead
> so that the bug is shown here:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=brickos
I am still learning to use the BTS properly :)
Thanks you,
Nicolas.
Control: reassign 1101084 gcc-h8300-hms 1:3.4.6+dfsg2-4.3
Control: affects 1101084 = brickos
Control: tags 1101084 + pending
Hello,
This is actually a bug in gcc-h8300-hms, it changes the directory used
for tools from /usr/h8300-hitachi-coff to /usr/lib/h8300-hitachi-coff,
while binutils-h8300-hm
* Helmut Grohne [2025-03-17 08:00]:
> brickos-doc/trixie takes over the files
> - /usr/share/doc/brickos/NEWS.gz
> - /usr/share/doc/brickos/README
> - /usr/share/doc/brickos/README.usb
> - /usr/share/doc/brickos/VERSION
> from brickos/bookworm. It therefore must declare Breaks and Replaces. A
Hi,
* Keith Packard [2024-11-28 12:02]:
> > 2. Somebody fixes the mips64el problem for gcc-riscv64-unknown-elf and then
> > re-introduces mips64el as an architecture that gcc-riscv64-unknown-elf
> > is
> > built for.
> I'm trying this approach now; my simple testing showed that adding
>
Hello,
I am part of the Debian LEGO Team and a sponsored maintainer of
nxt-firmware, which depends on picolibc to build.
It seems that gcc-riscv64-unknown-elf still did not migrate to testing.
Is there something I can do to help?
If I understand properly the problem, the code, or the GOT is too
* Sietse Achterop [2022-07-22 14:45]:
> Thanks for the quick response!
> Here the strace of both nqc and firmdl3
Thanks,
Looking at the kernel module source code, legousbtower does not seems to
behave like a tty driver, so it looks normal that the ioctl does not
work.
Looking at the nqc source
* Sietse Achterop [2022-07-22 11:55]:
> I now realize that the main problem maybe is in the device
> /dev/usb/legousbtower0, which is created
> when plugging in the IR-tower.
>
> Jul 22 11:53:03 Sietses-PC kernel: [137264.570103] usb 1-9: new low-speed USB
> device number 16 using xhci_hcd
> Ju
Hello,
* Petter Reinholdtsen [2021-08-18 07:10]:
> Nice! What can be changed to ensure you discover such issues before
> releases in the future?
Is it possible to cc me on nxt-firmware bug reports?
Nicolas.
> Thank you for discovering this issue. I hope someone find a fix in time
> for the next Debian release. I suspect I will not.
Hello,
I just upgraded to bullseye and saw this.
I have made a fix on my git repo:
https://git.ni.fr.eu.org/nxt-firmware.git/log/
Now I need to update the website an
12 matches
Mail list logo