From: Brice Waegeneire <brice@waegenei.re>
To: Simon Streit <simon@netpanic.org>
Cc: 53695@debbugs.gnu.org
Subject: bug#53695: trash-cli crashes
Date: Sat, 12 Feb 2022 11:03:14 +0100 [thread overview]
Message-ID: <87o83cwgf1.fsf@waegenei.re> (raw)
In-Reply-To: <ygu35l2bwc0.fsf@netpanic.org> (Simon Streit's message of "Tue, 01 Feb 2022 13:33:19 +0100")
Hello Simon,
Simon Streit <simon@netpanic.org> writes:
> With trash-cli's last update, it doesn't work any more and exits with
> the following error:
>
> Traceback (most recent call last):
> File "/home/ss2/.guix-profile/bin/trash-list", line 4, in <module>
> from trashcli.list import main as main
> ModuleNotFoundError: No module named 'trashcli'
I'm the one who updated trash-cli¹; sorry to have broken it for you.
Unfortunalty, I can't manage to reproduce it on my side:
--8<---------------cut here---------------start------------->8---
$ /gnu/store/kbsw86qqip1p9yzrnm36d71xhk278m1l-profile/bin/trash-list
2021-12-11 09:12:37 /home/bricewge/project/guix/bricewge/channel
2021-12-21 08:23:06 /home/bricewge/project/guix/bricewge/symlink
[...]
--8<---------------cut here---------------end--------------->8---
Alos I'm using trash-cli daily without any issue since updating it. The commit
updating the package also activate tests which pass fine on the CI².
Is it still broken on your side? Are you on a foreign distro? Can you share
other relevant information to find in which condition the package break ?
¹ https://issues.guix.gnu.org/50235
² http://ci.guix.gnu.org/build/405413/log/raw
Cheers,
- Brice
next prev parent reply other threads:[~2022-02-12 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 12:33 bug#53695: trash-cli crashes Simon Streit
2022-02-12 10:03 ` Brice Waegeneire [this message]
2022-02-12 14:56 ` Simon Streit
2022-02-15 9:41 ` Lars-Dominik Braun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o83cwgf1.fsf@waegenei.re \
--to=brice@waegenei.re \
--cc=53695@debbugs.gnu.org \
--cc=simon@netpanic.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).