Re: developing the "critical updates repo" plan

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Fri, May 23, 2014 at 04:21:43PM +0200, Tomas Mraz wrote:
> You have to understand that the repoclosure process takes some time and
> the metadata on the updates repository is much larger. This affects work
> of release engineers and it basically prevents the mirrors to sync such
> large repository too often.

Okay, so would this new repo, only for [critical?] security updates be turned on by default so everyone would be checking this repo?  As long as it's not an optional/non-enabled repo I think it's a fine idea.

- -- Eric

- --------------------------------------------------
Eric "Sparks" Christensen
Red Hat, Inc - Product Security Team

sparks@xxxxxxxxxx - sparks@xxxxxxxxxxxxxxxxx
097C 82C3 52DF C64A 50C2  E3A3 8076 ABDE 024B B3D1
- --------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQGcBAEBCgAGBQJTf2ZoAAoJEB/kgVGp2CYvRzoMAJiHfOyXZ9W5JBpZLi0Bk6xi
/E8GdmfFUcqN8UzW1MIFMOhbqriKrgo7XnVEgmw617adUEwsb/ah8o3FrAGH+EN9
+p1Si94I+ZFSuFBpXCSPSmgHGfuL5hVP49XVGfnG2Hafli9cx/BVYPqoiReb+qss
1RgJdsacC4zaHM7rrTWZfbt5ELhd713nvu56nQlTdUVif4dPwxdzv7yoOUpYIczg
R0wmGMoDAVzRoZ1T+7MPya/5llxi6StYAf1T9g9NBKadjPtUDkCRDSXPT3SE4iJv
rQhMuEPAsrIEuiJ1PieNS6NQ8oX3Ecgaqsh8jRMOX9awIkLamq/cgcYLV+K/CiLO
L79c7i3QcwIU6HABjtLhUg/k+ZVwudYZrFoMFn3/7vpSyl8Q3f+HB2Cp1kQB8ku6
6jCGUKHb6HmF/0GxrEjUMUCqrf2HloA578Yf8+reoofqirSUkBgeCvujaI89aYXV
0QC4In12ESlCbbvcAzEq9NYS2YW4dYvUXL2jyZnh6g==
=iw/6
-----END PGP SIGNATURE-----
--
security mailing list
security@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/security





[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Coolkey]

  Powered by Linux