Home_greyopenFATE - openSUSE feature tracking > #308407
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Simplify debranding in Kiwi and SUSE Studio

Feature state



I build appliances based on openSUSE. I've done some of them in SUSE Studio, and some of them on my workstation using Kiwi, VirtualBox OSE, Xen or VMware Workstation. I am starting to get some that I'd like to distribute.

In order to distribute them, I need to be able to re-brand some packages - remove the openSUSE branding and replace it with upstream branding or my own. See
http://en.opensuse.org/Making_a_SUSE_based_distribution for the details. I've tried to do this using SUSE Studio, since it's a lot more convenient, but I have been unable to create a de-branded appliance because of package conflicts in the built-in patterns. See

The essential difficulty, both in SUSE Studio and in Kiwi is that the base patterns which define package lists contain unremovable branding packages. For these patterns, I need to

  1. Find a list of all the packages in the patterns and their dependencies
  2. Acquire the source for the branded packages, de-brand them at the source level, and then rebuild binary RPMs.

That's a significant amount of labor with no value added to the recipients of the redistributed software. So what I am requesting is that the openSUSE project

  1. Make the base patterns ("default", "kde4", "gnome", "xfce", etc.) branding-free, and create a new "branding-openSUSE" pattern to replace the upstream branding with openSUSE branding, and
  2. Create de-branded RPMs for the few packages that don't have a "branding-upstream" equivalent.

I haven't done the research to identify all of these, but I believe most of them are in the YaST infrastructure.


icons/user_comment.png M. E. wrote: (8 years ago)

Actually, now that I look at the packages and patterns in a YaST software management window, it looks like the intention / design was there for action 1, branding-free base patterns plus a "branding-openSUSE" pattern. It's just that you can't remove "branding-openSUSE" without conflicts:

#### YaST2 conflicts list - generated 2009-11-25 09:44:32 ####
patterns-openSUSE-base-11.2-20.22.1.x86_64 requires branding-openSUSE, but this requirement cannot be provided
    [ ] keep branding-openSUSE-11.2-2.2.noarch
    [ ] Following actions will be done:
deinstallation of patterns-openSUSE-base-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-x11_opt-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-x11-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-kde4_basis-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-enhanced_base-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-devel_rpm_build-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-devel_basis-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-apparmor_opt-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-apparmor-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-sw_management_kde4-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-non_oss-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-imaging_opt-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-imaging-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-games-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-kde4_imaging-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-kde4-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-devel_kernel-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-devel_ide-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-devel_C_C++-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-non_oss_opt-11.2-20.22.1.x86_64
deinstallation of patterns-openSUSE-devel_kde-11.2-20.22.1.x86_64
    [ ] break patterns-openSUSE-base by ignoring some of its dependencies

#### YaST2 conflicts list END ###

Time for more research into the way dependencies work, I guess. :-)

icons/user_comment.png A. J. wrote: (7 years ago)

This is fixed now for openSUSE 11.2 with the latest update of packages. It's also fixed for 11.3 and if you find again a bug in this area, please open a bugreport.

icons/user_comment.png M. E. wrote: (7 years ago)

I'm starting to test this over the weekend. Should I test with 11.2 first, or 11.3? I just downloaded 11.3 Milestone 4 but couldn't get it to work in a VirtualBox guest. 11.3 Milestone 3 does work as a guest, though. I also have a spare hard disk partition I can test on.

icons/user_comment.png A. J. wrote: (7 years ago)

It works with 11.2 with all updates applied and with 11.3 Milestone 4 (not sure about 3). Feel free to test either...

Last change: 7 years ago
Loading tags...
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint