Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-09-10 Thread WHR
[Jérémy Lal] > 1. Please use DEP-3 format for patches (missing at least Description, > Forwarded fields) > https://dep-team.pages.debian.net/deps/dep3/ > Oddly lintian didn't pick that. > > 2. It would be nicer to have a debian/watch file Hi, These has been imlemented on https://salsa.debian.org

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-09-10 Thread WHR
[Petter Reinholdtsen] > As far as I understand Appstream, it only need to be unique string. > Given that it is a different code base, I suspect it should not use a > org.freebsd ID. Make sense. I will keep the current ID. I just created a debian/watch file, available on Salsa; give it a review?

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-09-10 Thread WHR
[Petter Reinholdtsen] > Please bring up your view with the group maintaining the Appstream > specification. As things stand right now, the Appstream metainfo XML > parser require it, so for the hardware mapping to make it into the > directory for use by isenkram and others, it need to be accepted

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-09-10 Thread WHR
The 'control' file and the patch has been updated accordingly. [Petter Reinholdtsen] > E: rivoreo.mfiutil:3: cid-is-not-rdns rivoreo.mfiutil > W: rivoreo.mfiutil:~: metainfo-filename-cid-mismatch > > ✘ Validation failed: errors: 1, warnings: 1, pedantic: 1 > > The appstream XML parser

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-09-09 Thread WHR
Hello. It seems no activtiy in a while. Any progress?

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-31 Thread WHR
>> Good to know. What about passing code the other way? Among other >> things, I notice there are lots of endian fixes in the Linux port that >> are missing in the FreeBSD port. I guess it would be useful on big >> endian FreeBSD machines. > > I would like to do so, but I don't think FreeBSD wo

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-31 Thread WHR
[Petter Reinholdtsen] > Good to know. What about passing code the other way? Among other > things, I notice there are lots of endian fixes in the Linux port that > are missing in the FreeBSD port. I guess it would be useful on big > endian FreeBSD machines. I would like to do so, but I don't th

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-31 Thread WHR
> I suspect I lack a tag. There are no tags in my clone, so I suspect you > forgot 'git push --tags'. Yep. > Btw, do you know if uptream is in contact with the FreeBSD maintainers > of mfiutil? Look to me like there have been some updates on FreeBSD > that are not inlcuded in the Linux port. Th

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-31 Thread WHR
> Is the idea to use git-buildpackage? No, I havn't used this. > Do you plan to use > pristine-tar to be able to reproduce the orig.tar.gz file from the git > repo? I notice there is no pristine-tar branch there now. I have just created a pristine-tar delta for the newly released upstream sour

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-30 Thread WHR
>> I will finalize the first release by tomorrow, assuming no additional >> issues >> are found in the source tree. >> >> I have updated the Debian packaging repo to the latest upstream version: >> https://salsa.debian.org/Low-power/mfiutil/-/tree/master/ > > Good. Is the idea to use git-buildpac

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-29 Thread WHR
Hi. I will finalize the first release by tomorrow, assuming no additional issues are found in the source tree. I have updated the Debian packaging repo to the latest upstream version: https://salsa.debian.org/Low-power/mfiutil/-/tree/master/ [Petter Reinholdtsen] > (Btw, how did you come up wit

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-28 Thread WHR
Hello. I have got an account at Salsa: https://salsa.debian.org/Low-power/

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-28 Thread WHR
> [WHR] >> None. I havn't started using git for it yet. > > Right. Salsa might be the best choice, then. Did you get any response > from the Salsa admins? They said to try register again. I'm waiting for account approval once again. >> Uploaded at https://

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-28 Thread WHR
>> [WHR] >>> I'm asking for suggestion of any improvement that should be done in the >>> non-Debian source tree. For example should the Makefile be having some >>> more >>> features, that would benefit the Debian build system and possibly others? >

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-28 Thread WHR
> [WHR] >> I'm asking for suggestion of any improvement that should be done in the >> non-Debian source tree. For example should the Makefile be having some >> more >> features, that would benefit the Debian build system and possibly others? >> >> In the

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-27 Thread WHR
Hello. I'm asking for suggestion of any improvement that should be done in the non-Debian source tree. For example should the Makefile be having some more features, that would benefit the Debian build system and possibly others? In the case of this Makefile btw, I already have a Debian patch to

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-26 Thread WHR
> Le mar. 27 août 2024 à 01:04, WHR a écrit : > >> > [WHR] >> >> I was writing a new section for the man page today. I will commit this >> >> patch by tomorrow. Thanks. >> > >> > Good. What is your timeline for getting the package into De

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-26 Thread WHR
> [WHR] >> I was writing a new section for the man page today. I will commit this >> patch by tomorrow. Thanks. > > Good. What is your timeline for getting the package into Debian? I > suspect the deadline to make it to the next stable release is > approaching very

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-26 Thread WHR
> > I built and tested the source on a machine running testing, and it seem > to work fine. According to the compiler there are some potential buffer > overflows: > > gcc -I include -std=gnu99 -Wall -Wno-unused-value -Os -c -o mfi_drive.o > mfi_drive.c > mfi_drive.c: In function ‘mfi_pdstate’:

Bug#1079642: ITP: mfiutil -- Utility for managing LSI MegaRAID SAS controllers

2024-08-25 Thread WHR
Package: wnpp Severity: wishlist Owner: WHR X-Debbugs-Cc: debian-de...@lists.debian.org, w...@rivoreo.one * Package name: mfiutil Version : 1.0.15-rivoreo-r1 Upstream Contact: WHR * URL : https://sourceforge.net/projects/mfiutil/ * License : BSD-3-Clause

Bug#648635: May be it is out of nfs-utils' control

2024-07-16 Thread WHR
> For later releases, simply set the 'host' directive under '[nfsd]' section. I mean in the config file /etc/nfs.conf == For later releases, simply set the 'host' directive under '[nfsd]' section in /etc/nfs.conf.

Bug#648635: May be it is out of nfs-utils' control

2024-07-16 Thread WHR
I found a workaround. By using option '--host' in rpc.nfsd(8), it will creating the socket from user space, then passing the file descriptor to kernel via /proc/fs/nfsd/portlist; thus bypasses the previously mentioned socket creation code in kernel. So to listen on IPv4 only, pass option '--host=

Bug#648635: May be it is out of nfs-utils' control

2024-07-16 Thread WHR
I think the bug is in linux, where it didn't provide a way to not create an IPv6 socket; specifically the /proc/fs/nfsd/portlist interface can only be to control transport protocol (tcp, udp, rdma) and port number. The underlying code of this interface is hardcoded to create both IPv4 and IPv6 sock

Bug#1075748: Patch

2024-07-04 Thread WHR
Control: tags 1075748 + patch This patch makes installkernel(8) additionally recognizing 'Image' as a name for uncompressed image file. --- installkernel.orig 2024-06-09 15:25:40.0 +0800 +++ installkernel 2024-07-04 17:22:48.201433536 +0800 @@ -63,11 +63,14 @@ fi } -if [ "$(basename

Bug#1075748: debianutils: installkernel(8) incorrectly named uncompressed Linux image for riscv64 as 'vmlinuz-...'

2024-07-04 Thread WHR
Package: debianutils Version: 5.19 Severity: minor X-Debbugs-Cc: w...@rivoreo.one Hello. The Debian-specific installkernel(8) script would install the new Linux image under /boot/ with name begining with 'vmlinuz', despite the image is compeltely uncompressed. The Linux riscv build system names u

Bug#1072559: xfce4-terminal: Please provide an option to disable escape sequence-controlled terminal window resizing

2024-06-04 Thread WHR
Package: xfce4-terminal Version: 1.1.3-1 Severity: minor X-Debbugs-Cc: w...@rivoreo.one Hello. For anyone don't aware this type of escape sequences, open a xfce4-terminal(1) window, with bash(1) running in it, then type: printf '\x1b[8;2;2;t' See https://invisible-island.net/xterm/ct

Bug#1070808: zsh(1) changes behavior of the keypad Enter key and didn't restore it on exiting

2024-05-09 Thread WHR
Package: zsh Version: 5.9-6 Severity: normal X-Debbugs-Cc: bmy...@gmail.com, w...@rivoreo.one Hello. I actually don't use zsh myself, but sometimes when I comes to collaborate with others in tmux(1), where their login shell is zsh, or I just need to test something in zsh, I always encounters thi

Bug#1056296: dash: redirecting stdout for current shell via 'exec' command didn't work correctly

2023-11-19 Thread WHR
Package: dash Version: 0.5.12-6 Severity: normal X-Debbugs-Cc: msl023...@gmail.com Please see the following test case: # cat redir-stdout-test.sh #!/bin/sh set -e rm -f /tmp/empty true > /tmp/empty exec 1<> /tmp/empty ls -l /proc/$$/fd/ 1>&2 # bash redir-stdout-test.sh total 0 lrwx--

Bug#1052472: linux-image-6.5.0-1-powerpc64: Can't run program if its executable file was made immutable via chattr(1)

2023-09-22 Thread WHR
Package: src:linux Version: 6.5.3-1 Severity: normal X-Debbugs-Cc: msl023...@gmail.com, msl023...@gmail.com Taking executable file /usr/bin/ssh to demonstrate the issue: # which ssh /usr/bin/ssh # ssh

Bug#1042074: bash-completion: Completion for 'sh' command filters file name with only '*.sh'

2023-07-26 Thread WHR
Package: bash-completion Version: 1:2.11-7 Severity: normal Tags: patch X-Debbugs-Cc: msl023...@gmail.com Hello. I think completing file names to include '*.sh' only, is a bug, because in reality many Unix shell scripts are named without a suffix at all. Based on my experiences for past year

Bug#1024639: file(1) couldn't detect Apple's HFSX version 5 (HFS Plus Extended)

2022-11-22 Thread WHR
Package: file Version: 1:5.41-4 Severity: normal X-Debbugs-Cc: msl023...@gmail.com Hello. While HFS Plus version 4 can be detected by file(1), the extended version 5, aka. HFSX, couldn't be detected at all, reporting only 'data'. According to Apple's HFS Volume Format (TN1150), HFSX is an ext

Bug#1023847: libsdl2-2.0-0: SDL2 failed to detect remote X11 connection and attempted to use MIT-SHM extension on it

2022-11-11 Thread WHR
Package: libsdl2-2.0-0 Version: 2.24.2+dfsg-1 Severity: normal X-Debbugs-Cc: msl023...@gmail.com Hello. When trying to run some simple SDL2-based programs over a remote X11 display (for example SSH X11 forwarding), this version of SDL2 incorrectly enables MIT-SHM extension, which isn't possibl

Bug#1022162: ftpsync: Sync big repositories sometimes (often?) fail with rsync(1) error due to --max-delete limit

2022-10-21 Thread WHR
Package: ftpsync Version: 20180513 Severity: normal The rsync(1) log file under /var/log/ftpsync/ shows something like: Deletions stopped due to --max-delete limit (168906 skipped) ... rsync error: the --max-delete limit stopped deletions (code 25) at main.c(1677) [generator=3.1.3] -- System In

Bug#1022063: gdb crashes target program if any breakpoint was set at a shared library function before it was first used

2022-10-19 Thread WHR
referenced by the target program, for example when setting breakpoint before running the program, the target program would crash as soon as it calls the shared library function. For example: whr@debian:~/src$ gdb rval-test GNU gdb (Debian 12.1-4) 12.1 Copyright (C) 2022 Free

Bug#1022056: gdb: Cannot return a specified value from a shared library function using the 'return' command

2022-10-19 Thread WHR
Package: gdb Version: 12.1-4 Severity: minor X-Debbugs-Cc: msl023...@gmail.com Hello. The issue happens when I specific a return value to the 'return' command in gdb(1), in order to return from a shared library function with my specified return value. The following example uses function gete

Bug#1022049: libnettle8: Illegal instruction on IBM POWER7

2022-10-19 Thread WHR
Package: libnettle8 Version: 3.8.1-2 Severity: normal X-Debbugs-Cc: msl023...@gmail.com Hello. I think the Debian architecture I'm using (ppc64) should still supporting POWER7, but apparently this library was built to use instructions unavailable on POWER7. gdb(1) output: Program received si

Bug#1012562: gdb makes time(2) no longer returning correct value

2022-06-09 Thread WHR
Package: gdb Version: 10.1-2+b1 Severity: important X-Debbugs-Cc: msl023...@gmail.com Hello. I'm actually not sure whether this is a GDB or a GLIBC bug, but I currently can only reproduce this bug with gdb(1) (not strace(1) for exmaple). I found one of my program starts to behave abnormally

Bug#1008715: libpam-modules: Module pam_motd.so prints motd into stdout which breaks SSH-based services

2022-03-30 Thread WHR
Package: libpam-modules Version: 1.4.0-9+deb11u1 Severity: normal X-Debbugs-Cc: msl023...@gmail.com Hello. When using this module with sshd(8) as the default configuration, it prints MOTD into stdout (file descriptor 1) of the SSH stream. When setting up a SSH-based service using a delegated l

Bug#1001049: /usr/bin/hexdump: hexdump: no longer work with some format strings containing backslash escape sequences

2021-12-02 Thread WHR
Package: bsdextrautils Version: 2.36.1-8 Severity: normal File: /usr/bin/hexdump X-Debbugs-Cc: msl023...@gmail.com Hello. It seems that hexdump(1) no longer recognizing certain format strings that containing backslash character, either used as a part of an escape sequence, or used for backslas

Bug#988975: bash-completion: Wrong completion after some certain words such as TZ, TERM and LANG

2021-05-22 Thread WHR
Package: bash-completion Version: 1:2.11-2 Severity: important X-Debbugs-Cc: msl023...@gmail.com This version has a bug that didn't exist in previous Debian release (Buster). The completion becomes wrong after certain words; for exmaple I want to search for word 'TERM' in a file, so I typed (^

Bug#985003: shellcheck: –list-optional: openBinaryFile: does not exist (No such file or directory)

2021-05-21 Thread WHR
Package: shellcheck Version: 0.7.1-1 Followup-For: Bug #985003 X-Debbugs-Cc: msl023...@gmail.com This is obviously an error during man page processing; this '–' character was originally a double dash '--', the option you looking for is actually '--list-optional'. I can confirm that the origina

Bug#986630: elinks: Pasting text using some terminal emulators broken in ELinks 0.13

2021-04-08 Thread WHR
Package: elinks Version: 0.13~20190125-3 Severity: normal This ELinks version is broken with some older versions of GNOME Terminal, after pasting text into any ELinks window, some garbled characters appeared before and after the pasted text; I attached an example screenshot, where I pasted text 'c

Bug#980277: gcc: c99(1) provided by c99-gcc(1) isn't conforming to POSIX

2021-01-16 Thread WHR
Package: gcc Version: 4:8.3.0-1 Severity: minor POSIX has option '-O ' for c99(1) command, which means 'c99 -O 1 ...' should be exactly same as 'c99 -O1 ...'; however it is not in c99-gcc(1): $ ls -l /etc/alternatives/c99 lrwxrwxrwx 1 root root 16 Sep 14 17:12 /etc/alternatives/c99 -> /usr/bin/c9

Bug#970913: nmap: Nmap default ping scan unable to detect any hosts in an InfiniBand LAN

2020-09-25 Thread WHR
Package: nmap Version: 7.70+dfsg1-6+deb10u1 Severity: normal I have an InfiniBand interface configured as following: ibp129s0: flags=4163 mtu 2044 inet 10.4.4.35 netmask 255.255.0.0 broadcast 10.4.255.255 inet6 fe80::202:c903:f3:6ec1 prefixlen 64 scopeid 0x20 unspec 8

Bug#757143: vinagre doesn't send F10

2020-07-08 Thread WHR
Package: vinagre Version: 3.22.0-7 Followup-For: Bug #757143 Just checked, this bug is still existing in Debian Bullseye. -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64

Bug#757143: vinagre doesn't send F10

2020-07-08 Thread WHR
Package: vinagre Version: 3.22.0-6 Followup-For: Bug #757143 Tested Vinagre on Debian Buster. Press F10 always triggering the menu instead of sending the key to remote system, for whether 'Keyborad shortcuts' option is enabled or not. -- System Information: Debian Release: 10.1 APT prefers sta

Bug#963543: ucarp: Feature Request: Add UCARP_VHID environment variable for up/down commands

2020-06-23 Thread WHR
Package: ucarp Version: 1.5.2-2.2 Severity: wishlist Tags: patch This patch adds an environment variable to pass VHID when running the address up/down commands. This can be useful for scripts to distinguish from different addresses with its VHID, for example adding the VHID as a virtual interface

Bug#958447: elinks(1) blocked background processes from printing to terminal

2020-04-22 Thread WHR
Package: elinks Version: 0.13~20190125-3 Severity: normal Tags: patch elinks(1) has a wried hehavior that blocks the controlling terminal from being written by other background processes, while this may be intended to maintain the readability the ELinks TUI, it usually causing problems due to proc

Bug#939445: libc6: Localized sorting has unexpected change in zh_CN locale

2019-09-04 Thread WHR
Package: libc6 Version: 2.28-10 Severity: normal Tags: l10n Hi, I found the item sorting has surprising change in Debian Buster when using zh_CN locale; the Chinese characters are now sorted before English letters. I usually using LANG=zh_CN.UTF-8 to display localized messages in my system; howeve

Bug#933053: libncurses6: Ncurses-based Terminal UI Programs Broken in Debian Buster

2019-07-25 Thread WHR
Package: libncurses6 Version: 6.1+20181013-2 Severity: important Tags: a11y Hello. Most TUI programs that based on ncurses in Debian buster seem broken. Affecting programs aptitude(8), cfdisk(8), iftop(8), nano(1), nmon(1) and nload(1). Some screenshots are attached. May related to bug #905247. T

Bug#933052: systemd: Garbled outputs for terminal from systemctl(1)

2019-07-25 Thread WHR
Package: systemd Version: 241-5 Severity: normal Hello. I found the systemctl(1) command outputs are garbled in my terminal, if auto terminal paging is disabled. A screenshot is attached, or it is also available from http://mygnuos.tk/test/systemctl-terminal-garbled.png The outputs look normal whe

Bug#906727: file: Shared libraries wrongly detected as 'pie executable'

2018-08-20 Thread WHR
Package: file Version: 1:5.34-2 Severity: normal I found the file(1) tool on Debian buster would erroneously detect ELF shared libraries as 'pie executable'; for example: ~/src$ cat sample.c #include void func1(int a) { fprintf(stderr, "function: func1(%d)\n", a); } ~/src$ gcc -Wall -

Bug#896944: service: this wrapper script should pass additional options to systemctl(8) when using systemd

2018-04-26 Thread WHR
Package: init-system-helpers Version: 1.48 Severity: wishlist Tags: patch The service(8) script should pass additional options, if any after '${ACTION}', to systemctl(8). For example, if I run 'service rsyslog status', I would got: # service rsyslog status ● rsyslog.service - System Logging Se

Bug#863197: sysstat: sar program buffer overflow when option -s or -e are specified

2017-05-23 Thread WHR
Package: sysstat Version: 11.4.3-1 Severity: normal The program /usr/bin/sar shows a buffer overflow if I use option either -s or -e to specify start or end time. [whr@ZONGYI-TMACH]:[20]:[~]:$ sar -s 04:00 *** buffer overflow detected ***: sar terminated === Backtrace: = /lib/x86_64

Bug#806902: Wrong index of invalid socket fds in readConfiguration may results a segmentation fault

2015-12-02 Thread Whr
Package: rinetd Version: 0.62-5.1 Severity: important Tags: upstream patch First, the function readConfiguration will be called at program start up; it reads config file and identify what line is a forwarding rule, and count with a global var 'seTotal'; then process the rule, including get a soc