Bug#1026804: bug fix already done by upstream

2023-02-10 Thread
http://lists.infradead.org/pipermail/linux-amlogic/2023-February/015338.html please close this bug when Debian kernel get these changes.

Bug#1025934: update the patch

2022-12-12 Thread
there are some mistake in previous patch, update a new version From d74cc8be25d1e6e3ad90b39ce3b961c4db7809ae Mon Sep 17 00:00:00 2001 From: Zhang Ning Date: Tue, 13 Dec 2022 13:30:51 +0800 Subject: [PATCH v1] split fcitx5-pinyin split fcitx5-pinyin to 3 packages fcitx5-pinyin fcitx5-pinyin-data f

Bug#1025934: patch for split fcitx5-pinyin

2022-12-12 Thread
please consider to split the package. this patch make it possible (or a step) to in stall fcitx5 without QT. Or you can write some similar patch. I understand there is a package fcitx5-config-qt, which is needed by fcitx5, but I can remove it after settle down the configs, or even I can manaul

Bug#1025934: 回复: Bug#1025934: Feature Request: Split fcitx5-pinyin to fcitx5-pinyin and fcitx5-pinyin-dictmanager

2022-12-12 Thread
>发件人: Shengjing Zhu >发送时间: 2022年12月13日 4:55 >收件人: 张 宁 ; 1025...@bugs.debian.org ><1025...@bugs.debian.org> >主题: Re: Bug#1025934: Feature Request: Split fcitx5-pinyin to fcitx5-pinyin and >fcitx5-pinyin-dictmanager >  >On Mon, Dec 12, 2022 at 08:00:40AM +,

Bug#1025954: would you like to test new patch?

2022-12-12 Thread
Hi, I understand why it fail to boot. static int parse_label(char **c, struct pxe_menu *cfg) it failed to parse "kalsrseed", and move to uplayer, and uplayer still don't know how to handle it. and affected "append" I don't have old version u-boot, thus can't test it out. I have a new patch, wou

Bug#1025934: Feature Request: Split fcitx5-pinyin to fcitx5-pinyin and fcitx5-pinyin-dictmanager

2022-12-12 Thread
Package: fcitx5-pinyin Version: 5.0.16-1 fcitx5-pinyin depends on QT5 which unfriendly to GTK-only system. after search code only "libpinyindictmanager.so" depends on QT5, libpinyin.so doesn't. thus request to split fcitx5-pinyin to more friendly to GTK-only systems. BR. Ning.

Bug#1021981: qemu: wrong behave for bash in qemu-loongarch64-static

2022-10-18 Thread
Package: qemu-user-static Version: 1:7.1+dfsg-2 Hi, Debian Qemu team I find wrong behave for bash in qemu-loongarch64-static. $ [[ -w . ]] && echo 1 but expect: $ [[ -w . ]] && echo 1 1 you can use gentoo stage3 image to reproduce it. https://bouncer.gentoo.org/fetch/root/all/releases/loong/

Bug#924631: os-probe failed to detect second debian

2019-03-15 Thread
Package: os-probe Version: 1.76~deb9u1 I rsynced debian to new partition, and run update-grub2. and reboot and select new boot entry, but still go into old debian. after check, I find new boot entry still old debian. menuentry 'Debian GNU/Linux 9 (stretch) (on /dev/sdd2)' --class debian --class

Bug#886291: pycryptodome naming

2018-03-03 Thread
agree with Alexis Murzeau. my suggest is pythonX-pycryptodome conflicts to and provides pythonX-crypto, and pythonX-pycryptodomex is a new package. BR. Ning.

Bug#891619: wrong package name for python-pycryptodome

2018-02-27 Thread
Package: python-pycryptodome Version: 3.4.7-1 due to pycrypto is dead, pycryptodome is a replacement. as said by pycryptodome developers: pycryptodome works as pycrypto while pycryptodomex works as pycryptodome. actully deb package python-pycryptodome is pycryptodomex. in this point of view