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 Request]: All KDE Packages - Nightly, Stable, Release #39190

Open
72 tasks
Trenly opened this issue Dec 29, 2021 · 9 comments
Open
72 tasks

[Package Request]: All KDE Packages - Nightly, Stable, Release #39190

Trenly opened this issue Dec 29, 2021 · 9 comments
Labels
Help-Wanted This is a good candidate work item from the community.

Comments

@Trenly
Copy link
Contributor

Trenly commented Dec 29, 2021

This issue is to combine all the requests for KDE packages into a single place and reduce clutter

Nightly

Stable

Release

@ghost ghost added the Needs-Triage This work item needs to be triaged by a member of the core team. label Dec 29, 2021
@RokeJulianLockhart

This comment has been minimized.

@Trenly
Copy link
Contributor Author

Trenly commented Dec 29, 2021

This comment is response to "http://github.com/microsoft/winget-pkgs/issues/39190#issue-1090227311" and "http://github.com/microsoft/winget-pkgs/issues/39190#issuecomment-1002592593".

I am able to assist compilation of this list so that frequent modification of it by @ItzLevvie and @Trenly shall not be necessary:

Addition of "http://github.com/microsoft/winget-pkgs/issues/39245" is necessary. Addition of "http://github.com/microsoft/winget-pkgs/issues/39247" is necessary. Addition of "http://github.com/microsoft/winget-pkgs/issues/39251" is necessary. Addition of "http://github.com/microsoft/winget-pkgs/issues/39252" is necessary.

Approximately 37 are remaining.

@BEEDELLROKEJULIANLOCKHART Please stop opening new issues for all of the package requests for KDE. You can just put the package ID's here. We are familiar with the KDE site and are already looking into the best way to add these packages. This issue was created to combine all of the other issues you opened into a single issue so that the issues tab isn't filled with KDE request spam

The problem with these packages is the retention of the packages and the fact that the Jenkins API's to fetch the latest URL's are not fast enough to catch all of the builds.

@RokeJulianLockhart
Copy link
Contributor

RokeJulianLockhart commented Dec 29, 2021

#39190 (comment)

Apologies – I'll do as you say.

I am able to add the identifiers manually, but that is not assistive, because the sole aspects which that effort is necessary for are:

  • verification of correctness of the URI that has been utilised for each description, and
  • ascertainment of the "Current Package Identifier" that is for each package.

However, I have not added them for any but #30233 (comment).

@Trenly
Copy link
Contributor Author

Trenly commented Dec 29, 2021

I shall adhere to your request. I am able to add the identifiers manually, but that is not assistive, because the sole aspects that effort is necessary for are verification of correctness the URI that has been utilised for each description, and ascertainment of the "Current Package Identifier" that is for each package, although I have not added that for any but "http://github.com/microsoft/winget-pkgs/issues/30233#issue-1025347565".

The URI's you have provided don't work after 3 days anyways. As long as we know which packages need to be added yet, we can find the correct URI's

@vedantmgoyal9
Copy link
Contributor

vedantmgoyal9 commented Feb 13, 2022

@BEEDELLROKEJULIANLOCKHART can you make manifests and open PRs to add an initial version of them in this repo, after that, it will be auto updated by the automation. Or, if anyone else would like to do so?

@RokeJulianLockhart

This comment has been minimized.

@RokeJulianLockhart
Copy link
Contributor

RokeJulianLockhart commented Aug 22, 2022

#39190 (comment)

Has remediation of this problem progressed? I ask because many, many packages await this treatment.

If not, https://download.kde.org/stable and https://download.kde.org/unstable may be useful.

@RokeJulianLockhart
Copy link
Contributor

RokeJulianLockhart commented Jan 12, 2023

#39190 (comment)

Per vedantmgoyal9/vedantmgoyal9#185 (comment), I propose the undermentioned as the solution:

$BaseUrl = 'https://binary-factory.kde.org/view/Windows%2064-bit/job/kdeconnect-kde_Release_win64/'
((Invoke-WebRequest -Uri "$BaseUrl").Links | Where-Object {$_.outerText -like "Last successful build*"} | Select-Object -Property outerText) -match '[0-9]{3,}' | Out-Null; $build = $Matches.Values
$BaseUrl+$build+"/$(((Invoke-WebRequest -Uri "$BaseUrl$build/").Links | Where-Object {$_.href -like '*.exe'}).href)" 

$BaseUrl = 'https://binary-factory.kde.org/view/Windows%2064-bit/job/Cantor_Release_win64/'
((Invoke-WebRequest -Uri "$BaseUrl").Links | Where-Object {$_.outerText -like "Last successful build*"} | Select-Object -Property outerText) -match '[0-9]{3,}' | Out-Null; $build = $Matches.Values
$BaseUrl+$build+"/$(((Invoke-WebRequest -Uri "$BaseUrl$build/").Links | Where-Object {$_.href -like '*.exe'}).href)"

$BaseUrl = 'https://binary-factory.kde.org/view/Windows%2064-bit/job/KBibTeX_Nightly_win64/'
((Invoke-WebRequest -Uri "$BaseUrl").Links | Where-Object {$_.outerText -like "Last successful build*"} | Select-Object -Property outerText) -match '[0-9]{3,}' | Out-Null; $build = $Matches.Values
$BaseUrl+$build+"/$(((Invoke-WebRequest -Uri "$BaseUrl$build/").Links | Where-Object {$_.href -like '*.exe'}).href)"

It appears to operate for me!

@RokeJulianLockhart
Copy link
Contributor

RokeJulianLockhart commented Nov 16, 2024

#39190 (comment)

https://blogs.kde.org/2024/01/30/farewell-binary-factory-add-craft-jobs-your-apps-kdes-gitlab-now/ may invalidate some of the concerns expressed here. I presume that WinGet is well-tooled to support GitLab CI?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Help-Wanted This is a good candidate work item from the community.
Projects
None yet
Development

No branches or pull requests

4 participants