Coder Social home page Coder Social logo

Comments (13)

mkevenaar avatar mkevenaar commented on June 22, 2024 1

Thank you for creating this issue. I will have a look at it soon.

from chocolatey-packages.

mkevenaar avatar mkevenaar commented on June 22, 2024 1

@ptanmay143 I ended up changing the work into a Stream to have a pre-release and a stable stream automatically updating in Chocolatey. They released a pre-release and a stable release at the same time.

You can see my changes in this commit: 8b14c50

from chocolatey-packages.

ptanmay143 avatar ptanmay143 commented on June 22, 2024 1

I can confirm that this does install the correct version on my school computer as well as my personal computer. I'm closing this issue now. Thanks.

from chocolatey-packages.

ptanmay143 avatar ptanmay143 commented on June 22, 2024

Moreover, I had the v1.0.1401.0 already installed and then I ran a chocolatey upgrade. This caused the start menu to have two entries for Microsoft Terminal.
image
I suspected this was due to the pre-release version (also called as Preview in Windows) having a different Appx package name. So I ran Get-AppxPackage and I actually did saw two entries for Windows Terminal.

Name              : Microsoft.WindowsTerminal
Publisher         : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture      : X64
ResourceId        :
Version           : 1.0.1401.0
PackageFullName   : Microsoft.WindowsTerminal_1.0.1401.0_x64__8wekyb3d8bbwe
InstallLocation   : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.0.1401.0_x64__8wekyb3d8bbwe
IsFramework       : False
PackageFamilyName : Microsoft.WindowsTerminal_8wekyb3d8bbwe
PublisherId       : 8wekyb3d8bbwe
IsResourcePackage : False
IsBundle          : False
IsDevelopmentMode : False
NonRemovable      : False
IsPartiallyStaged : False
SignatureKind     : Store
Status            : Ok

Name              : Microsoft.WindowsTerminalPreview
Publisher         : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture      : X64
ResourceId        :
Version           : 1.1.1671.0
PackageFullName   : Microsoft.WindowsTerminalPreview_1.1.1671.0_x64__8wekyb3d8bbwe
InstallLocation   : C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.1.1671.0_x64__8wekyb3d8bbwe
IsFramework       : False
PackageFamilyName : Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe
PublisherId       : 8wekyb3d8bbwe
IsResourcePackage : False
IsBundle          : False
IsDevelopmentMode : False
NonRemovable      : False
IsPartiallyStaged : False
SignatureKind     : Store
Status            : Ok

This difference in Appx Package name would also render the chocoUninstall.ps1 script (https://github.com/mkevenaar/chocolatey-packages/blob/master/automatic/microsoft-windows-terminal/tools/chocolateyUninstall.ps1) useless since it would not actually remove the preview version from Windows.

from chocolatey-packages.

ptanmay143 avatar ptanmay143 commented on June 22, 2024

The link (https://api.github.com/repos/microsoft/terminal/releases) provides a JSON output of all the releases (stable and pre-release both). The boolean key prerelease determines whether a release is a prelease or stable. To get the direct download link to the .msixbundle file of a specific release, one needs to traverse into the assets key array and look for the browser_download_url key.
Just for reference, I'm copying here only the above keys for the two releases in question (1.0.1401.0 and 1.1.1671.0).

[
    {
        [...]
        "tag_name": "v1.1.1671.0",
        [...]
        "prerelease": true,
        [...]
        "assets": [
            {
                [...]
                "browser_download_url": "https://github.com/microsoft/terminal/releases/download/v1.1.1671.0/Microsoft.WindowsTerminal_1.1.1671.0_8wekyb3d8bbwe.msixbundle"
            }
        ],
        [...]
    },
    {
        [...]
        "tag_name": "v1.0.1401.0",
        [...]
        "prerelease": false,
        [...]
        "assets": [
            {
                [...]
                "browser_download_url": "https://github.com/microsoft/terminal/releases/download/v1.0.1401.0/Microsoft.WindowsTerminalPreview_1.0.1402.0_8wekyb3d8bbwe.msixbundle"
            }
        ],
        [...]
    },
[...]
]

from chocolatey-packages.

ptanmay143 avatar ptanmay143 commented on June 22, 2024

I tried installing Windows terminal on another system using choco install -y microsoft-windows-terminal but this still installed the preview version. How do I specifically install the stable version?

from chocolatey-packages.

mkevenaar avatar mkevenaar commented on June 22, 2024

@ptanmay143 They have split the software into two separate parts. Could you run the following in an elevated powershell?

choco uninstall microsoft-windows-terminal -n -y
Get-AppxPackage -Name Microsoft.WindowsTerminalPreview | Remove-AppxPackage
Get-AppxPackage -Name Microsoft.WindowsTerminal| Remove-AppxPackage
choco install microsoft-windows-terminal -y

This will uninstall the package, the two separate packages for Microsoft Windows Terminal and then it should install the latest version of Terminal without a pre-release.

Could you confirm that this is working for you so I can close this case again?

from chocolatey-packages.

ptanmay143 avatar ptanmay143 commented on June 22, 2024

The output of choco uninstall microsoft-windows-terminal -n -y:

Chocolatey v0.10.15
Uninstalling the following packages:
microsoft-windows-terminal

microsoft-windows-terminal v1.1.1671.0
 Skipping auto uninstaller - No registry snapshot.
 microsoft-windows-terminal has been successfully uninstalled.

Chocolatey uninstalled 1/1 packages. 
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

The outputs of Get-AppxPackage -Name Microsoft.WindowsTerminalPreview | Remove-AppxPackage and Get-AppxPackage -Name Microsoft.WindowsTerminal | Remove-AppxPackage are both blank.
The output of choco install microsoft-windows-terminal -n -y:

Chocolatey v0.10.15
Installing the following packages:
microsoft-windows-terminal
By installing you accept licenses for the packages.

Progress: Downloading microsoft-windows-terminal 1.1.1671.0... 0%
[...]
Progress: Downloading microsoft-windows-terminal 1.1.1671.0... 99%
Progress: Downloading microsoft-windows-terminal 1.1.1671.0... 100%

microsoft-windows-terminal v1.1.1671.0 [Approved]
microsoft-windows-terminal package files install completed. Performing other installation steps.
 The install of microsoft-windows-terminal was successful.
  Software install location not explicitly set, could be in package or
  default install location if installer.

Chocolatey installed 1/1 packages. 
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

So, this still installs the v1.1.1671.0 which is a pre-release version and another issue is that now there is no start menu entry for Windows Terminal or Preview either. Doing a Get-AppxPackage -Name Microsoft.WindowsTerminal and Get-AppxPackage -Name Microsoft.WindowsTerminalPreview now returns nothing.

from chocolatey-packages.

mkevenaar avatar mkevenaar commented on June 22, 2024

@ptanmay143 I have pulled that version just now. Can you run the commands again?

This should result in the installation of v1.0.1811.0 which should be the latest available release as of now.

If you want the latest pre-release you'll need to specifically add --pre to the command as shown here:

https://chocolatey.org/packages/microsoft-windows-terminal/1.1.1812.0-beta

from chocolatey-packages.

ptanmay143 avatar ptanmay143 commented on June 22, 2024

choco install microsoft-windows-terminal still installs v1.1.1671. Is there some way I need to update the databases so that chocolatey knows that this version does not exist?
Additional info:

PS C:\Users\ptanmay143> choco outdated
Chocolatey v0.10.15
Outdated Packages
 Output is package name | current version | available version | pinned?
PS C:\Users\ptanmay143> choco list -lo
Chocolatey v0.10.15
[...]
microsoft-windows-terminal 1.1.1671.0
[...]
45 packages installed.
PS C:\Users\ptanmay143> choco upgrade all
Chocolatey v0.10.15
Upgrading the following packages:
all
By upgrading you accept licenses for the packages.
[...]
microsoft-windows-terminal v1.1.1671.0 is newer than the most recent.
 You must be smarter than the average bear...
[...]
Chocolatey upgraded 0/45 packages. 
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
PS C:\Users\ptanmay143> choco search microsoft-windows-terminal
Chocolatey v0.10.15
microsoft-windows-terminal 1.1.1671.0 [Approved]
1 packages found.

from chocolatey-packages.

MortenBoysen avatar MortenBoysen commented on June 22, 2024

I also followed these steps:

choco uninstall microsoft-windows-terminal -n -y
Get-AppxPackage -Name Microsoft.WindowsTerminalPreview | Remove-AppxPackage
Get-AppxPackage -Name Microsoft.WindowsTerminal| Remove-AppxPackage
choco install microsoft-windows-terminal -n -y

And it removed both packages. The last step installed the correct version, but I am also lacking a start menu entry. Hence I cannot start the terminal since I do not know where the binary is.

from chocolatey-packages.

ptanmay143 avatar ptanmay143 commented on June 22, 2024

I also followed these steps:

choco uninstall microsoft-windows-terminal -n -y
Get-AppxPackage -Name Microsoft.WindowsTerminalPreview | Remove-AppxPackage
Get-AppxPackage -Name Microsoft.WindowsTerminal| Remove-AppxPackage
choco install microsoft-windows-terminal -n -y

And it removed both packages. The last step installed the correct version, but I am also lacking a start menu entry. Hence I cannot start the terminal since I do not know where the binary is.

In the last command, you specified the -n option which skips running the chocoInstall.ps1 script. You could do a choco install microsoft-windows-terminal --force. I'll have to check tomorrow if it installs the correct version in my school laptop.

from chocolatey-packages.

MortenBoysen avatar MortenBoysen commented on June 22, 2024

And it removed both packages. The last step installed the correct version, but I am also lacking a start menu entry. Hence I cannot start the terminal since I do not know where the binary is.

In the last command, you specified the -n option which skips running the chocoInstall.ps1 script. You could do a choco install microsoft-windows-terminal --force. I'll have to check tomorrow if it installs the correct version in my school laptop.

Cheers! That fixed the issue and everything seems to work as expected now. No preview installed and the correct version of the Windows Terminal is installed (1.0.1811.0)

from chocolatey-packages.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.