Hi.
Jima <jima@xxxxxxxxxxxxxx> wrote:
> Actually, I threw together a patch this morning and emailed it to
> Jeremy, as he solicited on Monday. My Makefile-fu is weak, though, so
> I can't be absolutely sure it's good. (Also, I don't know if I should
> be uploading junk files for testing.) However, AFAICT, the expiration
> date is in plaintext, so my method of testing was to just edit the date
> (as that's all my patch checks for).
> Anyone more knowledgable in Makefiles, or simply braver than me, can
> play with this:
>
> http://beer.tclug.org/fedora-extras/fedora-cert-expired.patch
>
> Feedback is readily encouraged. :)
Ah. That is a way to check it that did not occur to me.
My take is below, just to provide some choice :)
Thanks to Dawid Gajownik for providing me with an expired certificate.
--
Eagles may soar, but weasels don't get sucked into jet engines.
--- Makefile.common.orig 2006-07-15 19:41:03.000000000 +0200
+++ Makefile.common 2006-08-17 20:46:46.000000000 +0200
@@ -170,7 +170,12 @@
define upload-request
echo "Checking : $$b on $(UPLOAD_REPOSITORY)..." ; \
check=$$($(upload-check)) ; retc=$$? ; \
-if test $$retc -ne 0 ; then \
+if test $$retc -eq 52; then \
+ echo "ERROR: Could not read response from server. Your certificate may be expired." ; \
+ echo "To get a new one, go to: https://admin.fedoraproject.org/accounts/"; ; \
+ echo "and click 'Download a client-side certificate.'" ; \
+ exit -1 ; \
+elif test $$retc -ne 0 ; then \
echo "ERROR: could not check remote file status" ; \
exit -1 ; \
elif test "$$check" = "Available" ; then \
--
fedora-extras-list mailing list
fedora-extras-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-extras-list
