Package Details: storageexplorer 1.33.1-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.003583
First Submitted: 2017-02-23 15:38 (UTC)
Last Updated: 2024-04-11 01:36 (UTC)

Pinned Comments

faultylee commented on 2022-08-05 14:48 (UTC)

The latest update is now using .NET Core 6.0, should help resolve some of the issues some of you had previously around installing .NET Core 3.1

Latest Comments

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

faultylee commented on 2019-12-29 04:39 (UTC) (edited on 2019-12-29 04:40 (UTC) by faultylee)

Should be resolved now, sorry for the delay. Do let me know if there's still issue. Thanks @gnloch for the tips

faultylee commented on 2019-12-12 00:19 (UTC)

Hi @gnloch thanks for the tips. I'll try that out some time during this weekend. Thanks for everyone's patience

gnloch commented on 2019-12-11 18:33 (UTC)

Following the suggestion on the github issue, I was able to use version 1.11.1 by adding an env variable DOTNET_ROOT=/opt/dotnet (besides adapting the PKGBUILD source/sha256sums)

gnloch commented on 2019-12-09 14:37 (UTC)

There is a bug on 1.11.1 https://github.com/microsoft/AzureStorageExplorer/issues/2322

faultylee commented on 2019-12-09 02:09 (UTC) (edited on 2019-12-12 00:17 (UTC) by faultylee)

Hi everyone, I ran into some issue with 1.11.1 myself, I was unable to satisfied the dotnet core 2.1 needed by storage explorer. I've tried installing dotnet runtime/core/sdk 2.1 but none worked. I need more time to figure this out. If you know how to resolve this do share it here. Please bare with me for now. Thank you for your patient

faultylee commented on 2019-09-22 06:50 (UTC)

thanks @jungliztik and @henix for reporting this. I used to monitor https://storageexplorerpublish.blob.core.windows.net/versionjson/version2.json which is the same url used by the "Check for Updates" so that the update comes as Microsoft is ready to release it to everyone, but I didn't realized my browser extension lost that update check list list, lol. The github link is indeed better. I'll use that as the backup to get notified of updates

henix commented on 2019-09-22 06:29 (UTC) (edited on 2019-09-22 06:29 (UTC) by henix)

Hi @faultylee, you can use these versioned tarball files from https://github.com/microsoft/AzureStorageExplorer/releases (e.g. https://github.com/microsoft/AzureStorageExplorer/releases/download/V1.10.1/Linux.StorageExplorer.tar.gz ) to avoid sha256sum inconsistency. I just encountered the same problem, hash is out of date.

jungliztik commented on 2019-07-03 07:36 (UTC)

It looks like the hash for the tarball file is out of date. From the PKGBUILD

b282f78cb81c027b3fc7d375f1d2a02564af37604c70dff6b1cc18e0bacedc6f

From the archive I manually downloaded

1ae970ff09eb8d5db9cf7e44aae73ae23cfecd399c5285dee1f4d8eac20db287 StorageExplorer-linux-x64.tar.gz

faultylee commented on 2018-12-28 01:22 (UTC)

@cluxter I would guessed it's the cached copy of the source zip file downloaded by aurman. When you changed to pacaur, it uses a diff cache folder, which will download a new source zip file. Hence it works, but it will fail in the next version.

cluxter commented on 2018-12-11 17:55 (UTC)

I also had an integrity check issue when I was using "aurman". I tried with "pacaur" and it worked. My feeling is that the hash which was in the PKGBUILD was not updated according to v1.6 when it was released and "aurman" downloaded it and put it in cache, then used it even when it was updated with the right hash. So when I tried with "pacaur" it downloaded the right PKGBUILD and build succeeded.

My own explanation sounds weird to me because "aurman" looks like a very solid software, so the real reason of the issue might come from something else.

Also: I used "pacaur" as a workaround, but remember "pacaur" is not maintained anymore, so don't use it to update your system or to install softwares.

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