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

fetch-crl: update to 3.0.21 #7567

Merged
merged 1 commit into from Jul 3, 2020
Merged

fetch-crl: update to 3.0.21 #7567

merged 1 commit into from Jul 3, 2020

Conversation

chrstphrchvz
Copy link
Contributor

Description

From CHANGES file:

Changes in 3.0.20-1
----------------------
* network connection failure messages are pre-filtered and only primary
  status lines shown in logs for download and head requests (bugzilla #29)

Changes in 3.0.19-1
----------------------
* Do not add spurious newline to DER-format files (fixes report 201670320-01)
* run a script after the completion of every fetch-crl run (uses postexec
  directive in config file)

From wiki for 3.0.21:

* Add option to override the UserAgent string sent in the LWP web requests (both HEAD and GET)
Type(s)
  • bugfix
  • enhancement
  • security fix
Tested on

Untested.

Verification

Have you

  • checked your Portfile with port lint?
  • tried existing tests with sudo port test?
  • tried a full install with sudo port -vst install?
  • tested basic functionality of all binary files?

@macportsbot
Copy link

Notifying maintainers:
@petrrr for port fetch-crl.

@chrstphrchvz
Copy link
Contributor Author

The other maintainer's GitHub handle appears to be @dvandok. Dennis, are you still interested in maintaining this port and igtf-ca-bundle? If so, is the email address listed still correct? MacPorts would also like to list your GitHub handle in the portfiles so that you are notified of changes (see https://trac.macports.org/ticket/56050); is this the handle you would prefer being listed?

@dvandok
Copy link

dvandok commented Jun 28, 2020

Unfortunately I no longer have a Mac OS X machine to do this work on, so I will have to decline.
(The info is otherwise still correct.)

@chrstphrchvz
Copy link
Contributor Author

@dvandok Thanks for the quick response and for your past contributions. I will go ahead and remove you from the maintainers.

@macportsbot
Copy link

Travis Build #12420 Passed.

Lint results
--->  Verifying Portfile for fetch-crl
--->  0 errors and 0 warnings found.

Port fetch-crl success on xcode10.3. Log
Port fetch-crl-launchd success on xcode10.3. Log
Port fetch-crl success on xcode9.4. Log
Port fetch-crl-launchd success on xcode9.4. Log
Port fetch-crl success on xcode8.3. Log
Port fetch-crl-launchd success on xcode8.3. Log
Port fetch-crl success on xcode7.3. Log
Port fetch-crl-launchd success on xcode7.3. Log

@chrstphrchvz
Copy link
Contributor Author

I forgot to reset revision of fetch-crl-launchd to 0; fixed in cd627b1815

@macportsbot
Copy link

Travis Build #12438 Passed.

Lint results
--->  Verifying Portfile for fetch-crl
--->  0 errors and 0 warnings found.

Port fetch-crl success on xcode10.3. Log
Port fetch-crl-launchd success on xcode10.3. Log
Port fetch-crl success on xcode9.4. Log
Port fetch-crl-launchd success on xcode9.4. Log
Port fetch-crl success on xcode8.3. Log
Port fetch-crl-launchd success on xcode8.3. Log
Port fetch-crl success on xcode7.3. Log
Port fetch-crl-launchd success on xcode7.3. Log

Remove nikhef.nl:dennisvd from maintainers: they have declined to
further maintain their ports (see https://git.io/JJvBU)
@macportsbot
Copy link

Travis Build #12513 Passed.

Lint results
--->  Verifying Portfile for fetch-crl
--->  0 errors and 0 warnings found.

Port fetch-crl success on xcode10.3. Log
Port fetch-crl-launchd success on xcode10.3. Log
Port fetch-crl success on xcode9.4. Log
Port fetch-crl-launchd success on xcode9.4. Log
Port fetch-crl success on xcode8.3. Log
Port fetch-crl-launchd success on xcode8.3. Log

@mf2k mf2k merged commit 725d431 into macports:master Jul 3, 2020
@chrstphrchvz chrstphrchvz deleted the patch-3 branch July 3, 2020 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
5 participants