Your message dated Mon, 9 Jan 2023 17:32:35 +0100 with message-id <[🔎] Y7xBowSXOrAyqu0j@msg.df7cb.de> and subject line Re: libhamlib4-Jupiter bug fixed here has caused the Debian Bug report #1025626, regarding libhamlib4: fails to set freq on TT Jupiter to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1025626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025626 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libhamlib4: fails to set freq on TT Jupiter
- From: Ed Lawson <elawson@grizzy.com>
- Date: Tue, 06 Dec 2022 13:55:36 -0500
- Message-id: <167035293645.3289.15661265388568604876.reportbug@ham2-8300>
Package: libhamlib4 Version: 4.5-2+b1 Severity: normal X-Debbugs-Cc: elawson@grizzy.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? When using rigctl to set a freq on the Jupiter for 20M and below, the radio is shifted to 160M band and the reported freq is 1062MHz. There is no problem with setting freq/bands above 20M. All other functions of rigctl work OK. If I set a freq above 20M band, everything returns to normal. * What exactly did you do (or not do) that was effective (or ineffective)? Tried changing comm setting and various config option via rigctl. * What was the outcome of this action? Thee was no change in the behavior. * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libhamlib4 depends on: ii libc6 2.36-6 ii libusb-1.0-0 2:1.0.26-1 libhamlib4 recommends no packages. libhamlib4 suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---
- To: Ed Lawson <elawson@grizzy.com>, 1025626-done@bugs.debian.org
- Cc: debian-hams@lists.debian.org
- Subject: Re: libhamlib4-Jupiter bug fixed here
- From: Christoph Berg <myon@debian.org>
- Date: Mon, 9 Jan 2023 17:32:35 +0100
- Message-id: <[🔎] Y7xBowSXOrAyqu0j@msg.df7cb.de>
- Mail-followup-to: Christoph Berg <myon@debian.org>, Ed Lawson <elawson@grizzy.com>, 1025626-done@bugs.debian.org, debian-hams@lists.debian.org
- In-reply-to: <[🔎] 20230109103134.0718fc7e@800-mini-1>
- References: <[🔎] 20230109103134.0718fc7e@800-mini-1>
Version: 4.5.3-2 Re: Ed Lawson > Bug 1025626 concerning problems with libhamlib4 not setting freq > correctly with TT Jupiter has been resolved, here at least, by the > update of libhamlib-utils to 4.5.3-2. I am no longer having issues > with both xdx and xlog correctly handling freq. changes via hamlib to > and from my Jupiter. Let's close it then, thanks. Christoph
--- End Message ---