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

Any plans to upgrade SetACL to the new version? #309

Closed
jpluimers opened this issue Oct 4, 2022 · 6 comments
Closed

Any plans to upgrade SetACL to the new version? #309

jpluimers opened this issue Oct 4, 2022 · 6 comments

Comments

@jpluimers
Copy link

SetACL 3.1.2 has been available for quite a while now.

Any plans to upgrade to it from the current 3.0.6?

Are you open for pull request (since there are a few open ones)?

@bcurran3
Copy link
Owner

bcurran3 commented Oct 4, 2022 via email

@jpluimers
Copy link
Author

Thanks for the maintainer state offer. I'm flattered, but decline: given the high chances of metastases returning and left-over symptoms after all the procedures I had, I'm actively cutting down on people/things/processes depending on me like (maintenance) responsibilities. Energy permitting I do provide pull requests and guidance.

The 3.0.6 version download file has disappeared, so now the package installation fails (see output below).

Today is a good day, so I will create a pull request for that.

For my reference:

  1. Download link
  2. SHA checksum
  3. Version number

Note that the Chocolatey checksum validation uses checksum.exe which compares hashes without case sensitivity. Since I'm from a certutil and unix background that default to lowercase hashes for test vectors the above sha256 hashes are lowercase.

I got to the checksum source code via chocolatey/choco: Improve handling for checksum type #1018

Relevant source line: https://github.com/chocolatey/checksum/blob/master/src/checksum/Program.cs#L90

For historic purposes:

Output:

C:\temp>choco upgrade --yes setacl
Chocolatey v1.1.0
Upgrading the following packages:
setacl
By upgrading, you accept licenses for the packages.
setacl is not installed. Installing...
Progress: Downloading setacl 3.0.6.0... 100%
Progress: Downloading setacl 3.0.6.0... 100%

setacl v3.0.6.0 [Approved]
setacl package files upgrade completed. Performing other installation steps.
Attempt to get headers for https://helgeklein.com/downloads/SetACL/current/SetACL%20(executable%20version).zip failed.
  The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://helgeklein.com/downloads/SetACL/current/SetACL%20(executable%20version).zip'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found."
Downloading setacl
  from 'https://helgeklein.com/downloads/SetACL/current/SetACL%20(executable%20version).zip'
ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://helgeklein.com/downloads/SetACL/current/SetACL%20(executable%20version).zip'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found."
This package is likely not broken for licensed users - see https://docs.chocolatey.org/en-us/features/private-cdn.
The upgrade of setacl was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\setacl\tools\chocolateyInstall.ps1'.
 See log for details.

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

Failures
 - setacl (exited 404) - Error while running 'C:\ProgramData\chocolatey\lib\setacl\tools\chocolateyInstall.ps1'.
 See log for details.

@bcurran3
Copy link
Owner

Thanks. You put enough work into this that you should maintain it. :-)
Done.

@bcurran3
Copy link
Owner

p.s. Hope all is well and that you're procedures were all successful.

@jpluimers
Copy link
Author

p.s. Hope all is well and that you're procedures were all successful.

Yup. 18 months of hectic stuff behind us.

Long story short: I recovered from the surgery better than expected, we found a place for my mentally retarded brother to live internally with 24/7 care, did a big part of administration that had lagged behind for way too long, finally had time on our hands to think "now that we don't spend 20 hours care/week any more: what is good for ourselves to do?".

We decided that living in our split-level house would not be future proof, prepared the house for sale (basically by arranging some big storage units getting rid of excess stuff so they could make this video: https://youtu.be/uBMgRPrQdS0) and got ourselves a maisonette apartment with elevator which is also much closer to my brother. Similar view https://photos.app.goo.gl/xAVwnh347BUXNYkb8

In retrospect, the apartment had quite a few issues most of which are mostly solved by now (only 1/3 of rooms halfway unusable instead of only 1 room usable).

Which means I am becoming a bit more active on GitHub this year, awaiting more checks to see if the intestines are holding up nicely and no metastases evolving. The better half moved jobs and still is doing lots of physiotherapy to postpone the moment she gets into a wheelchair. She succeeded for 3 years now, so hopefully that too will be OK enough for a couple of years.

Glad the change request got merged last year, I can now finally ditch the testing VM I had for it (:

--jeroen

@bcurran3
Copy link
Owner

I'm amazed you kept a VM around just for this.
You are a true trooper!

p.s. I am no longer maintaining ANY Chocolatey packages. You should request to become the package maintainer. I KNOW it would be in good hands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants