Also is there any way I can control the order of the installation in my package list ?
For example given the package list:
> %packages
> @^workstation-product-environment
> @admin-tools
> @authoring-and-publishing
> @c-development
> @container-management
> @d-development
> @development-tools
> @editors
> @headless-management
> @libreoffice
> @mate-applications
> @network-server
> @office
> @rpm-development-tools
> @sound-and-video
> @system-tools
> @window-managers
> @^workstation-product-environment
> @admin-tools
> @authoring-and-publishing
> @c-development
> @container-management
> @d-development
> @development-tools
> @editors
> @headless-management
> @libreoffice
> @mate-applications
> @network-server
> @office
> @rpm-development-tools
> @sound-and-video
> @system-tools
> @window-managers
How do I chose which is installed first and which is installed later ? Or are they installed just in the order they are specified ?
On Sun, Apr 12, 2020 at 1:15 AM Samuel Sieb <samuel@xxxxxxxx> wrote:
On 4/10/20 1:55 PM, Sreyan Chakravarty wrote:
> I am doing a Kickstart installation of Fedora Workstation from the
> Fedora Server NetInstall ISO. Everything is going as expected until I
> hit the installation of the package: flatpak-selinux.
>
> Well I wish Anaconda would let me continue the installation if one
> package failed, but no I have to exit the installer and begin
> downloading 2.13 GB again and again.
> First question, any way for Anaconda to ignore such errors in the
> Kickstart file ?
I've run into similar issues, but as annoying as it is, it would not be
a good idea to continue if there's a failure.
> Secondly, what should I do about this error ?
>
> An open bug already exists here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1723118
> and https://bugzilla.redhat.com/show_bug.cgi?id=1723940
>
> One has a status of CLOSED and one has a status of MODIFIED.
>
> Now I can understand CLOSED since it was a duplicate but what does
> modified mean ? Also there are no solutions so what do I do now?
I found the documentation for the states:
https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow
MODIFIED means a fix is checked in, but an update hasn't been created yet.
> I actually got this bug in VirtualBox once during the testing of my
> Kickstart file but it got resolved automatically on a next install. This
> is not the case for my laptop though, it hits the error every time.
>
> These are the packages in my Kickstart:
> %packages
> @^workstation-product-environment
> @admin-tools
> @authoring-and-publishing
> @c-development
> @container-management
> @d-development
> @development-tools
> @editors
> @headless-management
> @libreoffice
> @mate-applications
> @network-server
> @office
> @rpm-development-tools
> @sound-and-video
> @system-tools
> @window-managers
>
> Should I delete some packages ? flatpak-selinux seems like a mandatory
> package, is there any way to not install it ?
You can't exclude it. It's in the dependency chain of gnome-software.
Try adding "selinux-policy" to the top of the packages list and see if
that solves the problem.
_______________________________________________
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
Regards,
Sreyan Chakravarty
_______________________________________________ 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
