Package Details: sftpman-gtk 1.1-1

Git Clone URL: (read-only, click to copy)
Package Base: sftpman-gtk
Description: GTK frontend for SftpMan (application that handles sshfs/sftp file systems mounting).
Upstream URL:
Keywords: sftp sshfs
Licenses: GPL3
Submitter: s.pantaleev
Maintainer: s.pantaleev
Last Packager: s.pantaleev
Votes: 30
Popularity: 1.32
First Submitted: 2011-06-17 23:24 (UTC)
Last Updated: 2021-10-12 09:28 (UTC)

Latest Comments

1 2 Next › Last »

FuelFlo commented on 2021-12-18 11:10 (UTC)

Okay, the rebuild fixed the problem. Thx and sorry for bothering you!

s.pantaleev commented on 2021-12-18 07:22 (UTC)

I can't reproduce the problem you're observing.

Have you tried rebuilding this package after you have upgraded to Python 3.10?

FuelFlo commented on 2021-12-17 23:14 (UTC) (edited on 2021-12-17 23:16 (UTC) by FuelFlo)

Hi I'm getting following error, trying to start sftpman-gtk, since some time:

Traceback (most recent call last):
  File "/usr/bin/sftpman-gtk", line 33, in <module>
    sys.exit(load_entry_point('sftpman-gtk==1.1', 'console_scripts', 'sftpman-gtk')())
  File "/usr/bin/sftpman-gtk", line 22, in importlib_load_entry_point
    for entry_point in distribution(dist_name).entry_points
  File "/usr/lib/python3.10/importlib/metadata/", line 919, in distribution
    return Distribution.from_name(distribution_name)
  File "/usr/lib/python3.10/importlib/metadata/", line 518, in from_name
    raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: No package metadata was found for sftpman-gtk

Any idea what I could do?

s.pantaleev commented on 2013-11-26 16:15 (UTC)

Updated. Thanks!

Logout22 commented on 2013-11-26 15:54 (UTC)

python-distribute has been replaced by python-setuptools. It would be nice if you updated the requirements to fit.

amiad commented on 2013-09-30 20:03 (UTC)

Thanks. The update working now.

s.pantaleev commented on 2013-09-30 19:32 (UTC)

Yes. It seems like you're right, @amiad. I thought you were getting an error that prevents you from updating, and I couldn't reproduce that on 2 different machines. Looks like it was throwing that harmless warning while building the package on my machine as well. I didn't even notice. It's fixed in 0.4.1. Thanks for the report.

s.pantaleev commented on 2013-09-30 09:56 (UTC)

@amiad, I don't think this is related to the current package (and its PKGBUILD). Something else is likely broken on your system. Try searching for the error you're getting and see if you can find anything wrong.