Package Details: storageexplorer 1.36.2-1

Git Clone URL: https://aur.archlinux.org/storageexplorer.git (read-only, click to copy)
Package Base: storageexplorer
Description: Microsoft Azure Storage Explorer is a standalone app from Microsoft that allows you to easily work with Azure Storage data on Windows, macOS and Linux.
Upstream URL: https://github.com/microsoft/AzureStorageExplorer/releases
Keywords: azure cloud microsoft storage
Licenses: unknown
Provides: storageexplorer
Submitter: XenGi
Maintainer: faultylee
Last Packager: faultylee
Votes: 28
Popularity: 0.000047
First Submitted: 2017-02-23 15:38 (UTC)
Last Updated: 2024-10-31 06:03 (UTC)

Pinned Comments

faultylee commented on 2024-05-28 06:20 (UTC)

The latest update from 1.34.0 is now using .NET Core 8.0 (extra/dotnet-runtime)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

faultylee commented on 2018-06-25 04:07 (UTC)

@nhjm thanks for sharing. It's a good note for other users. FYI fs.inotify.max_user_instances settings is system dependent, it's required for many other packages depending on your setup, i.e. Atom, Dropbox...etc. I don't think it's a good idea to include in the install script.

nhjm449 commented on 2018-06-15 23:25 (UTC)

FYI: In order to get this app to work, I had to increase the number of allowed inotify instances.

sysctl -w fs.inotify.max_user_instances=1024

System.IO.FileSystemWatcher was throwing a "The configured user limit (128) on the number of inotify instances has been reached." exception upon startup, causing the app to display a "Please install .NET Core 2.0" dialog.

faultylee commented on 2018-05-19 23:11 (UTC)

@johnhamelink the checksum seems fine. If you're using AUR helpers, there might be a cached copy of StorageExplorer-linux-x64.tar.gz from the previous version, which caused the checksum to fail. I just tested that and it works after I deleted StorageExplorer-linux-x64.tar.gz. Can you confirm on your end? I'll try to see if there's away to avoid this, though most recommendation points to using makepkg as the standard method and understanding how it works behind the scene.

johnhamelink commented on 2018-05-16 08:36 (UTC)

storageexplorer is currently failing its validity check

faultylee commented on 2018-05-12 02:37 (UTC)

Noted @cinatic, I've updated to 1.1.0 at the same time

cinatic commented on 2018-05-03 13:41 (UTC)

hi,

storage explorer needs community/dotnet-runtime, you maybe want to add it as dependency

faultylee commented on 2017-11-03 06:56 (UTC)

Yes, you're right, thanks for notifying. It's updated to 0.9.2. I've been monitoring Chocolatey and Microsoft, and both have not update the version on their page after they swapped out the file.

MilmraiTruearrow commented on 2017-11-03 00:38 (UTC) (edited on 2017-11-03 05:36 (UTC) by MilmraiTruearrow)

Seems that package checksum needs to be updated. Perhaps new version? ==> Retrieving sources... -> Found StorageExplorer-linux-x64.tar.gz -> Found storageexplorer.desktop ==> Validating source files with sha256sums... StorageExplorer-linux-x64.tar.gz ... FAILED storageexplorer.desktop ... Passed ==> ERROR: One or more files did not pass the validity check! Error installing storageexplorer : exit status 1 Current value: ▶ sha256sum StorageExplorer-linux-x64.tar.gz a150e38ff7b391a00871950cf7016120b4bcac9f9a85bffa903231c357408eff StorageExplorer-linux-x64.tar.gz

faultylee commented on 2017-10-18 00:24 (UTC)

@PoisonousJohn, thank you for spotting this, should be fixed now, give it a try. It was my mistake in not checking the file content which have changed, and when I tested it, I still have the old src folder lingering around.

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »