Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Clint Priest
    @cpriest
    On shims, I've found a better way to deal with them (prior to using scoop) that works really well. Add .LNK to the PATHEXT environment variable, then just use shortcut links (which let you specify working directory, path to executable and command parameters if desired). If you have a autoruns.lnk, for example, typing autoruns at the command line will resolve to the .lnk and launch it per that windows shortcut.
    Michael Murphy
    @mjmurphy
    I had some error messages installing docker and trying to get it to work - is this the best place to ask? Or should I open a ticket on Github?
    Creating shim for 'innounp'.
    'innounp' (0.47) was installed successfully!
    Installing 'docker' (18.06.1-ce) [64bit]
    DockerToolbox-18.06.1-ce.exe (214.7 MB) [=====================================================================] 100%
    Checking hash of DockerToolbox-18.06.1-ce.exe ... ok.
    Unpacking innosetup... Move-Item : Access to the path 'C:\Users\username\scoop\apps\docker\18.06.1-ce\_scoop_unpack\{app}\installers' is
    denied.
    At C:\Users\username\scoop\apps\scoop\current\lib\install.ps1:772 char:51
    + ... ildItem "$dir\_scoop_unpack\{app}" -r | Move-Item -dest "$dir" -force
    +                                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : WriteError: (C:\Users\murphm...app}\installers:DirectoryInfo) [Move-Item], IOException
        + FullyQualifiedErrorId : MoveDirectoryItemIOError,Microsoft.PowerShell.Commands.MoveItemCommand
    
    Move-Item : Access to the path
    'C:\Users\username\scoop\apps\docker\18.06.1-ce\_scoop_unpack\{app}\installers\virtualbox' is denied.
    At C:\Users\username\scoop\apps\scoop\current\lib\install.ps1:772 char:51
    + ... ildItem "$dir\_scoop_unpack\{app}" -r | Move-Item -dest "$dir" -force
    +                                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : WriteError: (C:\Users\murphm...lers\virtualbox:DirectoryInfo) [Move-Item], IOException
        + FullyQualifiedErrorId : MoveDirectoryItemIOError,Microsoft.PowerShell.Commands.MoveItemCommand
    
    done.
    Linking ~\scoop\apps\docker\current => ~\scoop\apps\docker\18.06.1-ce
    Creating shim for 'docker'.
    Creating shim for 'docker-compose'.
    Creating shim for 'docker-machine'.
    Creating shortcut for Kitematic (Kitematic.exe)
    Running post-install script...
    rm : Cannot find path 'C:\Users\username\scoop\apps\docker\current\installers' because it does not exist.
    At line:1 char:1
    + rm -r "$dir\installers"
    + ~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (C:\Users\murphm...rent\installers:String) [Remove-Item], ItemNotFoundEx
       ception
        + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand
    
    'docker' (18.06.1-ce) was installed successfully!
    I am trying to install docker on a machine with no privaleges
    Michael Murphy
    @mjmurphy
    it does seem to be installed, but trying to run a basic docker command like docker pull hello-world gives an error
    docker pull hello-world
    Using default tag: latest
    Warning: failed to get default registry endpoint from daemon (error during connect: Get http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/info: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.). Using system default: https://index.docker.io/v1/
    error during connect: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.38/images/create?fromImage=hello-world&tag=latest: open //./pipe/docker_engine: The system cannot find the file specified. In the default daemon configuration on Windows, the docker client must be run elevated to connect. This error may also indicate that the docker daemon is not running.
    Simon Hartcher
    @deevus
    Docker on Windows uses a VM so you will probably have issues without administrator access
    @mjmurphy
    However you have a few issues in the install so I would create an issue on gh
    I'm not certain but it's likely that the docker installation through scoop is just the client and not the services required to run a host
    Michael Murphy
    @mjmurphy
    thanks for the feedback @deevus I will open a ticket on Github about the install issues.
    Maybe I was being too optimistic about getting docker to run without admin access!
    xeijin
    @xeijin
    Hello - I'm trying to copy a scoop install & apps made on one computer to another (the other computer is a work machine which blocks downloads, so can't use scoop in the 'regular' way)
    the 'SCOOP' variable on the original machine was set to C:/scoop, on the new machine it's also set to C:/scoop
    I've added C:/scoop/shims to my PATH variable, so I can use 'scoop' from the commandline
    But when I try a scoop cleanup <app> it begins deleting the app (why?!) when I do a scoop reset it tries to link the 'current' folder of the app and gives me an error: Error: version 'current' is not allowed!
    Anyone know what I need to do to simply copy an existing installation from one machine to another? Am I missing some key file somewhere?
    Niels Bo Andersen
    @niboan
    @xeijin, you probably copied the junction folders (e.g. 'current' and persisted directories) as folders. XCOPY does that. It's said that FastCopy does the trick (haven't tried it)
    Pieter De Decker
    @pieterdd
    How safe is scoop? I assume that all of the packages are maintained by volunteers. Could someone create a malicious version of git and get it installed onto my machine through scoop's update mechanism?
    Richard Kuhnt
    @r15ch13
    @pieterdd if the Git maintainers would publish a malicious build it would get updated via the update mechanism of scoop automatically (nothing that we can do about this). The code for the update service can be found here https://github.com/r15ch13/Excavator
    It runs on my personal root server via docker (maybe it would be better to run it from a cloud service).
    Pieter De Decker
    @pieterdd
    @r15ch13 How many maintainers are there? Would one rogue maintainer be enough to distribute malware or are code reviews by at least one other maintainer enforced through GitHub's pull request system?
    Richard Kuhnt
    @r15ch13
    @pieterdd 5-6 (can't see the users list, only @lukesampson has these privileges). Currently there are no enforced code reviews on the master branch. So one maintainer is able distribute malware, yes. From the user list of https://github.com/scoopinstaller I can see that some of those maintainers don't have two-factor auth active also. Hm, this should be addressed.
    Pieter De Decker
    @pieterdd
    @r15ch13 Okay, good to know. I agree that mandatory two-factor would help make Scoop safer. While we're on this topic, have you guys ever considered adding an option to scoop install letting people view the JSON file before deciding if they want to proceed with the installation? That might be a simple way to give end users more power to see what they install.
    Pieter De Decker
    @pieterdd
    On second thought, maybe it's better if I just file a feature request on GitHub for that 😉
    Chawye Hsu
    @chawyehsu
    Currently, no. But you could use scoop info <app> and scoop virustotal <app> to dig into the package, before running scoop install <app>.
    scoop virustotal <app> is a good enough way to inspect and analyze suspicious files of a package, I think.
    Pieter De Decker
    @pieterdd
    Good tips, thanks!
    xeijin
    @xeijin

    May be of interest to some here:

    I don't always have access to PowerShell & Git to update my own external bucket, so using a modified appveyor.yml + checkver.ps1 I now automatically update any app manifests when the AppVeyor CI build runs:

    https://gitlab.com/xeijin-dev/propositum-bucket/blob/master/appveyor.yml

    xeijin
    @xeijin

    @xeijin, you probably copied the junction folders (e.g. 'current' and persisted directories) as folders. XCOPY does that. It's said that FastCopy does the trick (haven't tried it)

    By the way @niboan thanks for your help. I did eventually find the issue (though would have found it even quicker had I read your mention!)

    I was 7zip-ing the entire contents of the scoop folder for upload to BinTray as an artifact. However the .7z format doesn't support junctions/symlinks.

    To workaround this I first had to create a .tar archive with 7zip (which preserves the symlinks) and then create a .7z archive from the .tar to get the filesize down, as .tar doesn't support compression.

    Clint Priest
    @cpriest
    There's a problem w/ the keypirinha package that causes it to fail every time an update happens. (The keypirinha package contains a portable folder in the zip file and it fails on the attempt to persist that.) Where would I report that issue appropriately?
    Dan Schmidt
    @codeswish
    Hey, I'm confused about the difference between dotnet and dotnet-sdk. When I install dotnet, it says it is deprecated and to instead install dotnet-sdk. I install dotnet-sdk and uninstalled dotnet, but now I have no dotnet-cli. I uninstalled dotnet because I was having issues that I thought were related to it not using the current version .net sdk, not sure about this. Basically, I'm just wondering the scoop way of installing dotnet-sdk and the dotnet cli
    Dan Schmidt
    @codeswish
    Well, I just reinstalled dotnet and ran dotnet restore on my HelloWorld app and it is now working.
    Richard Kuhnt
    @r15ch13
    probably some A/B testing on their side. We can't do much about that
    Sam Garfinkel
    @sgarfinkel
    Is there a way to change which bucket a current installation is using? I have my own parallel bucket that runs some post-installation scripts, but unfortunately I already installed the main version of some things. Rather than completely reinstall from my own bucket, I was hoping there might be some way to change which bucket scoop used to track future changes.
    Richard Kuhnt
    @r15ch13
    @sgarfinkel you could try to change the "install.json" which is located in every installed apps directory to use your bucket. The next run of scoop update <app> should use your bucket
    Sam Garfinkel
    @sgarfinkel
    @r15ch13 Ok, I will try that. Thanks!
    xeijin
    @xeijin
    Does anyone know what autohotkey doesnt make the necessary file associations with .ahk files when installed?
    I notice there's another package 'autohotkey-installer' which looks like it would fix the issue, but it requires UAC which is what I am generally trying to avoid with scoop...
    Clint Priest
    @cpriest
    file associations would need to be done in the registry which would require elevation anyways
    if you want to capture those though, you could run something like regshot or some other registry capture/diff tool while you run the installer
    xeijin
    @xeijin
    @cpriest thanks, will take a look.
    Tres Finocchiaro
    @tresf

    file associations would need to be done in the registry which would require elevation anyways

    Although this statement is true for HKEY_CLASSES_ROOT, user file associations can be placed in HKEY_CURRENT_USER\Software\Classes\ without elevation.

    equinox
    @equinox
    @r15ch13 Hey, when you get a spare moment, could you take a look at why cygwin isn't updating beyond 2.895? I think it's because the sha512 aren't being updated on https://cygwin.com/sha512.sum but I have no idea how to help resolve the issue. Version 2.895 is from back in October '18, whereas it's at 3.0.1 as of a week or two ago. Thanks!
    Yannick Schinko
    @BrainStone
    Hi there. After installing dig, I'm unable to run it through the GitBash.
    I'm getting this error: C:/Users/<me>/scoop/shims/dig.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory
    It works fine from the powershell
    Any idea what's wrong?
    Ross Smith II
    @rasa
    @equinox Setup’s version is still 2.895. The Cygwin.dll’s version is 3.01. They should list setup’s version number to avoid the confusion.
    equinox
    @equinox
    @rasa cheers for the response and yeah they should, it sure confused the heck out of me!
    Clint Priest
    @cpriest
    Would it be possible to require a description for a package manifest?
    The library is growing so quickly it's hard to keep up with everything available, going through scoop info followed by scoop home (because there is no short description) is a bit annoying
    Richard Kuhnt
    @r15ch13
    @cpriest might be a good thing. Currently there are many manifest without a description that need to be updated before we make it a requirement.