Greetings. As previously announced, releng has made a number of changes as part of it's 2016 "flag day". All package maintainers will want to make sure they have updated to the following package versions (some may be in testing as of this email): python-cccolutils-1.4-1 fedpkg-1.26-2 fedora-packager-0.6.0.0-1 pyrpkg-1.47-3 koji-1.11.0-1 Please also see the following links for up to date information: https://fedoraproject.org/wiki/ReleaseEngineering/FlagDay2016 The following changes were made: * koji and the source lookaside were changed to use kerberos authentication instead of ssl certificates. All maintainers will need to: kinit YOUR-FAS-ACCOUNTNAME@xxxxxxxxxxxxxxxxxx to get a valid kerberos TGT and be able to authenticate to koji and the lookaside upload cgi. See the general kerberos information at: https://fedoraproject.org/wiki/Infrastructure_kerberos_authentication for more details. Additionally, via GSSAPI many browsers allow you to seamlessly login to any of our ipsilon using applications simply by clicking on the login button ( bodhi, fedorahosted trac, elections, fedocal, mailman3, etc) * koji now uses a well known cert for https. * pkgs.fedoraproject.org now redirects to https://src.fedoraproject.org and that uses a well known cert. Please correct any links you use to use https://src.fedoraproject.org for packages spec and patch files. * rawhide builds now land in the f26-pending tag, where they are signed and then added to the f26 tag for compose in the next rawhide compose. This allows rawhide packages to be fully signed as well as a point where automated QA can take place in the future. * packages "sources" files now use sha512 by default instead of md5. You will need the fedpkg update in order to create and use these new checksums. Questions or concerns as always welcome at #fedora-admin on irc.freenode.net or tickets at https://pagure.io/fedora-infrastructure. ; _______________________________________________ devel-announce mailing list -- devel-announce@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-announce-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx