Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Package Issue]: Discord.Discord architecture/version number issue #137157

Open
2 tasks done
ghost opened this issue Jan 30, 2024 · 4 comments
Open
2 tasks done

[Package Issue]: Discord.Discord architecture/version number issue #137157

ghost opened this issue Jan 30, 2024 · 4 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation.

Comments

@ghost
Copy link

ghost commented Jan 30, 2024

Please confirm these before moving forward

  • I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
  • I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue

Other

Brief description of your issue

Discord is not providing same version of application for x64 & x86.
Both have different version.
This may cause issue during winget upgrade --all as it will use latest version instead of correct architecture.
See screenshot of both latest version downloaded using following link:

https://discord.com/api/downloads/distributions/app/installers/latest?channel=stable&platform=win&arch=x86
https://discord.com/api/downloads/distributions/app/installers/latest?channel=stable&platform=win&arch=x64

These urls redirect to installer seen in screenshot.
image

Steps to reproduce

winget upgrade --all

Actual behavior

Upgrade to latest version irrelevant to architecture.

Expected behavior

Proposed solutions:

  1. Remove x86 package entirely from winget
  2. Separate packages Discord.Discord.x86 & Discord.Discord.x64

Environment

Windows Package Manager v1.6.3482
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22631.3085
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.21.3482.0

Screenshots and Logs

No response

@ghost ghost added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Jan 30, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage This work item needs to be triaged by a member of the core team. label Jan 30, 2024
Copy link
Contributor

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@Exorcism0666
Copy link
Contributor

#136960 (comment)

@ghost
Copy link
Author

ghost commented Jan 31, 2024

#136960 (comment)

The installer urls used in that PR is same as mentioned here.
But the latest version for both have different version number. (See screenshot of downloaded installer)
That is why they shouldn't be used in manifests of same version.

@stephengillie stephengillie removed the Needs-Triage This work item needs to be triaged by a member of the core team. label Jan 31, 2024
@ghost ghost changed the title [Package Issue]: Discord.Discord architecture issue [Package Issue]: Discord.Discord architecture/version number issue Feb 1, 2024
@seangibbz
Copy link
Contributor

There are a couple issues here, which I hope to resolve.

  1. Some of the poorly-configured manifests use the dynamic latest links instead of static version links.
  2. x86 and x64 versions are seperate releases and use different numbering conventions (i.e. current x86 is v1.0.9048 and current x64 is 1.0.9149). Some poorly-configured manifests list both x86 and x64 despite having different actual version numbers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation.
Projects
None yet
Development

No branches or pull requests

3 participants