• Bug#1061692: chirp fails to start with 'No module named 'chirp.stock_co

    From Harlan Lieberman-Berg@21:1/5 to All on Sun Jan 28 20:00:01 2024
    Package: chirp
    Version: 1:20240122-1
    Severity: grave
    X-Debbugs-Cc: debian@jouellet.net, hlieberman@debian.org

    Hello Dave, all,

    Thank you for updating chirp! Unfortunately, it seems that pybuild may have failed to pick up one of the necessary directories that contains the stock configurations. Running `chirpw` instantly crashes with the following error:

    Traceback (most recent call last):
    File "/usr/bin/chirpw", line 33, in <module>
    sys.exit(load_entry_point('chirp==20240122', 'console_scripts', 'chirpw')())
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/usr/lib/python3/dist-packages/chirp/wxui/__init__.py", line 178, in chirpmain
    mainwindow = main.ChirpMain(None, title='CHIRP')
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/usr/lib/python3/dist-packages/chirp/wxui/main.py", line 414, in __init__
    self.SetMenuBar(self.make_menubar())
    ^^^^^^^^^^^^^^^^^^^
    File "/usr/lib/python3/dist-packages/chirp/wxui/main.py", line 644, in make_menubar
    self.OPEN_STOCK_CONFIG_MENU = self.add_stock_menu()
    ^^^^^^^^^^^^^^^^^^^^^
    File "/usr/lib/python3/dist-packages/chirp/wxui/main.py", line 573, in add_stock_menu
    in importlib_resources.files('chirp.stock_configs').iterdir()
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/usr/lib/python3.11/importlib/resources/_common.py", line 22, in files
    return from_package(get_package(package))
    ^^^^^^^^^^^^^^^^^^^^
    File "/usr/lib/python3.11/importlib/resources/_common.py", line 53, in get_package
    resolved = resolve(package)
    ^^^^^^^^^^^^^^^^
    File "/usr/lib/python3.11/importlib/resources/_common.py", line 44, in resolve
    return cand if isinstance(cand, types.ModuleType) else importlib.import_module(cand)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
    File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
    File "<frozen importlib._bootstrap>", line 1140, in _find_and_load_unlocked ModuleNotFoundError: No module named 'chirp.stock_configs'

    Hopefully this is an easy fix! Thanks for your help maintaining this.

    73,

    --
    Harlan Lieberman-Berg (KC1CHE)
    ~hlieberman

    -- System Information:
    Debian Release: trixie/sid
    APT prefers testing
    APT policy: (500, 'testing')
    Architecture: amd64 (x86_64)
    Foreign Architectures: i386

    Kernel: Linux 6.5.0-5-amd64 (SMP w/16 CPU threads; PREEMPT)
    Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
    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 chirp depends on:
    ii python3 [python3-supported-min] 3.11.4-5+b1
    ii python3-importlib-resources 6.0.1-1
    ii python3-requests 2.31.0+dfsg-1
    ii python3-serial 3.5-2
    ii python3-six 1.16.0-4
    ii python3-yattag 1.15.1-1
    ii wxpython-tools 4.2.1+dfsg-3

    chirp recommends no packages.

    chirp suggests no packages.

    -- no debconf information

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Thu Feb 1 01:30:01 2024
    This is a multi-part message in MIME format...

    Your message dated Thu, 01 Feb 2024 00:22:41 +0000
    with message-id <E1rVKqn-000PKJ-0t@fasolo.debian.org>
    and subject line Bug#1061692: fixed in chirp 1:20240122-2
    has caused the Debian Bug report #1061692,
    regarding chirp fails to start with 'No module named 'chirp.stock_configs'
    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.)


    --
    1061692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061692
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 28 Jan 2024 18:46:13 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-13.8 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,FOURLA,FROMDEVELOPER,HAS_PACKAGE,RCVD_IN_PBL,
    RCVD_IN_SORBS_DUL,RDNS_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE,
    XMAILER_REPORTBUG autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 53; hammy, 150; neutral, 164; spammy,
    0. spammytokens: hammytokens:0.000-+--python3, 0.000-+--XDebbugsCc,
    0.000-+--X-Debbugs-Cc, 0.000-+--sk:taint_o, 0.000-+--sk:TAINT_O Return-path: <hlieberman@debian.org>
    Received: from [138.88.4.243] (port=55394 helo=[127.0.0.1])
    by buxtehude.debian.org with esmtp (Exim 4.94.2)
    (envelope-from <hlieberman@