Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> writes: > On Fri, Jul 12, 2013 at 09:57:04PM +0200, lee wrote: >> The upgrade from 17 to 18 silently broke apache because the >> configuration had changed. That is something that shouldn't happen, the >> devs know when there are changes like that and make sure the users are >> informed accordingly. >> Where/how do you make suggestions like that? > > We try to. That's part of the change process. Fedora, as a fast moving > distribution, doesn't make any promises that new versions will be backwards > compatible like that, but of course we try to minimize the pain where > possible and where it's reasonable given the upstream package. If there is > an incompatible change, we do try to make users aware and put it in the > release notes, or at least in the "common bugs" list after the fact. > Software is complicated and configuration possibilities infinite, so it's > not actually aways known when upgrades will have an impact. But we try. Please don't get me wrong, I don't expect backwards compatibility like that. It's perfectly fine when things change if needed. The point is informing the users. The package management tools in Debian send you emails about changes like that, even about very little changes, when packages are being replaced by more recent versions. Maybe this could be done in Fedora as well? BTW, I upgraded to F19 today and it went basically flawless. It seems you guys have done an awesome job with F19. Thank you! A few packages from F18 were left installed, apparently because fedup doesn't downgrade packages and because some are needed for older kernel versions. This led to emacs not running because it needs a different version of gnutls --- 'yum dist-sync' fixed that. However, 'yum dist-sync full' fails because there is no kernel from F18 available anymore. So far, I found one thing that doesn't work anymore: The keymap for the console doesn't seem to be loaded during booting and I'm getting an American or English keyboard layout instead of a German one. The keymap which is supposed to be loaded is still specified in /etc/vconsole.conf, and the map itself is available and can be loaded manually with loadkeys. A 'systemctl status systemd-vconsole-setup.service' doesn't show any problems, but it says the journal has been rotated. For some reason, the system figures I have a keyboard with 105 keys though I modified /etc/X11/xorg.conf.d/00-keyboard.conf to tell it that I have 102 keys. I haven't found out any more about this yet. It's quite funny, considering that the installer also insists on a qwerty layout :) Is there a way to show the progress when a new SELinux policy is installed during an upgrade? It seems to take quite a while to do this, and the computer appears to be frozen --- this was where I rebooted when upgrading last time from 17 to 18, so it might even have worked. At least a warning like "We need to check all the files on your computer so this can take many hours, depending on how many files you have." (or whatever makes it take so long) would help. -- Fedora 19 -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
