On Fri, Jan 13, 2017 at 12:16:18PM -0500, Stephen Gallagher wrote: > On 01/13/2017 12:03 PM, Przemek Klosowski wrote: > > On 01/13/2017 11:30 AM, Michael Mraka wrote: > >> Przemek Klosowski: > >>> Easy access to debug information is very well done in Fedora, and is > >>> one of its most empowering features. It's very easy to trace > >> ... > >>> Once the debuginfo is installed, however, we have a little bit of a > >>> stalemate, because the regular updates do not update the debuginfo > >>> files, so the symbols and sources get out of synch with the actual > >>> installed software. It's not a big problem---all that's required is > >>> to enable the appropriate debuginfo repos for the update, but I > >>> haven't found a really nice way of doing it. Currently I use > >>> > >>> dnf update --enablerepo *debuginfo > >> > >> /etc/dnf/plugins/debuginfo-install.conf > >> > >> The minimal content of conf file should contain main sections with > >> enabled and autoupdate parameter. > >> > >> autoupdate > >> A boolean option which controls updates of debuginfo packages. If > >> options is enabled and there are debuginfo packages installed it > >> automatically enables all configured debuginfo repositories. > >> (Disabled by default.) > >> > > Ah, wonderful. The default setting seems to be 'autoupdate=0' though. Is there a > > problem with changing it to '1'? People who install debuginfos do it for > > presumably well founded reasons, and I believe enabling autoupdate would serve > > them better. > > Probably because debuginfo files are very large and you might not want to waste > bandwidth keeping them updated. (Just guessing here) Yeah, bandwidth *and* the installation time. But the autoupdate= option could be made more visible. Maybe dnf debuginfo-install should print a warning if autoupdate=0 and *debug repos are disabled: "autoupdate of debuginfo packages is disabled, they might get out of sync on updates. Set autoupdate=1 in ... to enable automatic debuginfo updates." ? Zbyszek _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
