ubuntustudio-bugs team mailing list archive

[Erich Eickmeyer <2083262@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

[ Impact ]

Due to an accidental removal of code in Ubuntu Studio Installer prior to
24.04's release, the removal mechanism that makes sure dependencies and
recommends of the metapackages of Ubuntu Studio (e.g. ubuntustudio-
audio, ubuntustudio-video, etc.) are marked as auto before an
autoremoval proceeds to remove them was erroneously removed. Therefore,
users wishing to customize their system after install cannot.

[ Test Case ]

Using Ubuntu Studio (full install on Oracular):

* Run Ubuntu Studio Installer

* Attempt to remove a metapackage by unchecking a metapackage and
clicking "modify installation".

In any flavor other than Ubuntu Studio

* Install ubuntustudio-installer

* Install a metapackage by checking a box using ubuntustudio-installer

* Attempt to remove said metapackage by unchecking the metapackage and
clicking "modify installation".

DESIRED BEHAVIOR: Metapackage and its recommends are removed.
ACTUAL BEHAVIOR: Nothing happens, returned to menu.

[ Problems that could occur ]

This entire mechanism relies on, and always has relied on, apt's
autoremove function. It will, therefore, also autoremove other packages
that are not part of those metapackages such as old, no-longer-needed
kernels that have been marked by the system as removable already. I
would argue that if a user were keeping their system maintained this
wouldn't be a problem.

However, this is safer than force-removing packages that are in the meta
that might be part of another meta since, if it's in the other meta, it
would not get autoremoved.

That said, this was tested with great success prior to initial
implementation and this is just bringing back an erroneous removal. I
would argue that any "regression" is the result of a poorly maintained
system or people are blindly marking packages as "auto" without thinking
about the repercussions.

** Affects: ubuntustudio-installer (Ubuntu)
     Importance: High
     Assignee: Erich Eickmeyer (eeickmeyer)
         Status: In Progress

** Affects: ubuntustudio-installer (Ubuntu Noble)
     Importance: High
     Assignee: Erich Eickmeyer (eeickmeyer)
         Status: In Progress

** Affects: ubuntustudio-installer (Ubuntu Oracular)
     Importance: High
     Assignee: Erich Eickmeyer (eeickmeyer)
         Status: In Progress

** Also affects: ubuntustudio-installer (Ubuntu Noble)
   Importance: Undecided
       Status: New

** Also affects: ubuntustudio-installer (Ubuntu Oracular)
   Importance: High
     Assignee: Erich Eickmeyer (eeickmeyer)
       Status: In Progress

** Changed in: ubuntustudio-installer (Ubuntu Noble)
       Status: New => In Progress

** Changed in: ubuntustudio-installer (Ubuntu Noble)
   Importance: Undecided => High

** Changed in: ubuntustudio-installer (Ubuntu Noble)
     Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer)

** Changed in: ubuntustudio-installer (Ubuntu Noble)
    Milestone: None => noble-updates

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-installer in Ubuntu.
https://bugs.launchpad.net/bugs/2083262

Title:
  [SRU] Ubuntu Studio Installer's removal mechanism fails to activate

Status in ubuntustudio-installer package in Ubuntu:
  In Progress
Status in ubuntustudio-installer source package in Noble:
  In Progress
Status in ubuntustudio-installer source package in Oracular:
  In Progress

Bug description:
  [ Impact ]

  Due to an accidental removal of code in Ubuntu Studio Installer prior
  to 24.04's release, the removal mechanism that makes sure dependencies
  and recommends of the metapackages of Ubuntu Studio (e.g.
  ubuntustudio-audio, ubuntustudio-video, etc.) are marked as auto
  before an autoremoval proceeds to remove them was erroneously removed.
  Therefore, users wishing to customize their system after install
  cannot.

  [ Test Case ]

  Using Ubuntu Studio (full install on Oracular):

  * Run Ubuntu Studio Installer

  * Attempt to remove a metapackage by unchecking a metapackage and
  clicking "modify installation".

  In any flavor other than Ubuntu Studio

  * Install ubuntustudio-installer

  * Install a metapackage by checking a box using ubuntustudio-installer

  * Attempt to remove said metapackage by unchecking the metapackage and
  clicking "modify installation".

  DESIRED BEHAVIOR: Metapackage and its recommends are removed.
  ACTUAL BEHAVIOR: Nothing happens, returned to menu.

  [ Problems that could occur ]

  This entire mechanism relies on, and always has relied on, apt's
  autoremove function. It will, therefore, also autoremove other
  packages that are not part of those metapackages such as old, no-
  longer-needed kernels that have been marked by the system as removable
  already. I would argue that if a user were keeping their system
  maintained this wouldn't be a problem.

  However, this is safer than force-removing packages that are in the
  meta that might be part of another meta since, if it's in the other
  meta, it would not get autoremoved.

  That said, this was tested with great success prior to initial
  implementation and this is just bringing back an erroneous removal. I
  would argue that any "regression" is the result of a poorly maintained
  system or people are blindly marking packages as "auto" without
  thinking about the repercussions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/2083262/+subscriptions