Hello all!
Just about 5min ago, I was trying to create a new Fedora account, so i can
be more helpful towards the project. But I keep getting the error:
*The following error(s) have occurred with your request:*
*captcha: Incorrect value. *
I’m pretty sure I’ve typed 6 times a few different captchas. I’ve even
audio checked and still error came up. Can you please point me on the right
direction?
Regards from Portugal.
// pedro andrade
// www.pedroandrade.pt
#5451: A broken link was found on YubiKey page (FAS)
------------------------------+-----------------------------
Reporter: rodrigodearaujo | Owner: webmaster
Type: bug | Status: new
Priority: minor | Milestone: HANDWAVY-FUTURE
Component: Web Content | Version:
Severity: Normal | Keywords:
Blocked By: | Blocking:
Sensitive: 0 |
------------------------------+-----------------------------
= bug description =
A link provided here is broken:
https://admin.fedoraproject.org/accounts/yubikey/?_csrf_token=6b1241566bf2b…
= bug analysis =
The following link provided on the page above is broken:
http://www.yubico.com/files/YubiKey_manual-2.0.pdf
= fix recommendation =
To find a new link to that YubiKey Manual.
--
Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/5451>
Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure>
Fedora Infrastructure Project for Bugs, feature requests and access to our source code.
Hello all,
It was requested from members of the Fedora Cloud WG that we
provide a persistent URL that will always offer up the latest Two Week
Atomic Host release from Fedora.
Initially I wrote some code that would handle this in the Two Week
Atomic script[0] but dgilmore brought up a good point that this
removes our ability to easily track what compose any given "latest"
image downloaded at various points of time actually is since it would
overwrite the images in-place (we could maintain a listing of
checksums but that's not ideal). What was then proposed and I like
better is to offer a web endpoint that would do two things:
1) Serve up the latest image for the different image types (something
like getfedora.org/atomic/latest/$IMAGE_TYPE)
2) A simple URL endpoint that would return the actual image name that
is the 'latest' for use by people who want to write scripts to
automate and verify the images. (something like
getfedora.org/atomic/latest/$IMAGE_TYPE/filename)
The needed data is already provided via fedmsg by the Two Week Release
and is used to populate download links for the Atomic page[1] so
hopefully this won't be too much work. I'm also willing to do the work
and just submit the code for review but would like some guidance and
feedback on the topic in general.
Thank you,
-AdamM
[0] - https://pagure.io/fork/maxamillion/releng/c/9a49e6cfc8ee1b23dc383cbf527b896…
[1] - https://getfedora.org/en/cloud/download/atomic.html