ModuleNotFoundError: No module named 'shatag.cli'

Bug #1870839 reported by Brian Foster
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
shatag (Debian)
Fix Released
Unknown
shatag (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

$ shatag --help
Traceback (most recent call last):
  File "/usr/bin/shatag", line 11, in <module>
    load_entry_point('shatag==0.4.1', 'console_scripts', 'shatag')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 480, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2693, in load_entry_point
    return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2324, in load
    return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2330, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
ModuleNotFoundError: No module named 'shatag.cli'
$

Whilst the --help option was used in the above example,
the same(?) "No module named ..." error appears to happen
whatever one tries. Using locate(1), no "shatag.cli" file
seems to exist (the package has been installed for awhile
now, and so updatedb(1) should have catalogued the files).
In addition, there is no "cli" (anything) listed as being
part of the package ("dpkg-query -L shatag | grep -i cli"
finds nothing).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: shatag 0.5.0-2
ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
Uname: Linux 4.15.0-91-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Apr 4 22:34:59 2020
InstallationDate: Installed on 2016-10-07 (1275 days ago)
InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: shatag
UpgradeStatus: Upgraded to bionic on 2018-08-18 (595 days ago)

Revision history for this message
Brian Foster (blfoster) wrote :
Revision history for this message
Brian Foster (blfoster) wrote :

This 2018 problem report (with the same name as this report!),
 https://bitbucket.org/maugier/shatag/issues/9/modulenotfounderror-no-module-named
indicates that the problem was found and fixed.

It also mentions "shattr by @weakish clone shattr", which I seems to mean this
clone/rewrite,
 https://github.com/weakish/shattr
which seems to be in Redhat(?)'s Ceylon programming language.

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for reporting.

I get the same error message with shatag 0.5.0-3 on Ubuntu Focal. I've also reproduced and forwarded the bug report to Debian, see the attached bug watch.

Changed in shatag (Ubuntu):
status: New → Confirmed
tags: added: eoan focal
Changed in shatag (Debian):
status: Unknown → New
tags: added: groovy
removed: eoan
Revision history for this message
Carl Mäkinen (carlsster) wrote :

I noticed that the package is now fixed in Debian
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956373

It runs for me after I downloaded and installed the updated deb-file from Debian
http://deb.debian.org/debian/pool/main/s/shatag/shatag_0.5.0-4_all.deb

Thank you Didier Raboud and Hans Joachim Desserud!

Changed in shatag (Debian):
status: New → Fix Released
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

I can also verify the error is fixed in shatag 0.5.0-4build1 in Ubuntu 21.04 :)

Changed in shatag (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.