On 15/06/2021 13:00, ToddAndMargo via users wrote:
Bind-chroot upgrade from FC3 to FC34 disables the service breaking a server https://bugzilla.redhat.com/show_bug.cgi?id=1972000
Since that BZ lacks much in the area of detail why don't you: 1. Install F33 in VM. 2. Configure a named-chroot server 3. Make sure the F33 VM is then fully updated. 4. Collect information on what files you found you needed to fix. 5. Collect information on the status of named-chroot.service 6. Perform an upgrade from F33 to F34 in the attempt to recreate the issue. Problems which are reproducible have a better chance of being fixed. -- Remind me to ignore comments which aren't germane to the thread. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
