(Clarify about when debuginfo stops being available) |
mNo edit summary |
||
Line 8: | Line 8: | ||
--[[User:Wwoods|WillWoods]] 19:50, 5 February 2009 (UTC) | --[[User:Wwoods|WillWoods]] 19:50, 5 February 2009 (UTC) | ||
To clarify a bit: a properly-updated debuginfofs server should | To clarify a bit: a properly-updated debuginfofs server should have debuginfo for all packages in ''all configured Fedora repos'' - that is, we'll have debuginfo for the base version, the updated version, and the updates-testing version of every package. | ||
For packages that have ''left'' the repos (e.g. obsoleted updates) debuginfo isn't deleted immediately, but probably will be deleted after a short grace period - a week for stable releases, less for Rawhide. | |||
--[[User:Wwoods|WillWoods]] 22:49, 6 March 2009 (UTC) | --[[User:Wwoods|WillWoods]] 22:49, 6 March 2009 (UTC) |
Revision as of 23:01, 6 March 2009
Versioning
12:02 < dwmw2> I'm slightly confused about versioning 12:02 < dwmw2> does it cope if clients aren't completely up to date?
Yes. The debuginfo filenames are unique, even across different versions of the same package. So, there will be debuginfo files available for every version of every package available in the debuginfo repos.
--WillWoods 19:50, 5 February 2009 (UTC)
To clarify a bit: a properly-updated debuginfofs server should have debuginfo for all packages in all configured Fedora repos - that is, we'll have debuginfo for the base version, the updated version, and the updates-testing version of every package.
For packages that have left the repos (e.g. obsoleted updates) debuginfo isn't deleted immediately, but probably will be deleted after a short grace period - a week for stable releases, less for Rawhide.
--WillWoods 22:49, 6 March 2009 (UTC)