Skip to content

setup_kernels_arches should not call rpm on Debian/Ubuntu based distros #329

Closed

Description

@anbe42

If the distribution is based on Debian/Ubuntu, dkms should not make any calls to rpm.
There are currently unguarded calls in setup_kernels_arches and do_uninstall.

There is an unwanted side effect of creating an empty rpmdb in /.rpmdb/ or /root/.rpmdb/ on Debian and derivatives when performing rpm queries and rpm is installed.

Activity

  1. evelikov commented on Apr 19, 2023

    @evelikov
    Collaborator

    Glancing at the two uses:

    Michael do you recall what distro/version it's aimed at, is it still relevant?

    Edit: fwiw actual rpm invocations around ia32e were introduced by 3abe63b, although one can remove the whole block if the Arch is no longer supported/relevant.

    What are the side-effects of removing the (empty) folder when it's owned by rpm? Should we do a similar check for other package manageds - yum, apt, pacman, etc? I don't think such a check scales well, plus my gut feeling is that this might be a workaround for broken package.

  2. added a commit that references this issue on Apr 19, 2023
    096979d
  3. anbe42 commented on Apr 19, 2023

    @anbe42
    CollaboratorAuthor

    a possible solution: anbe42@096979d
    this adds a case "$running_distribution" in around rpm usage but does not try to reimplement the rpm usage with dkms/pacman, not yet tested ;-)

  4. evelikov commented on Apr 20, 2023

    @evelikov
    Collaborator

    Our ultimate goal is to remove all running_distribution instances. Iff needed a config toggle can be used to control the code flow. Considering the side effect is couple of empty directories, I'm not in favour of adding more.

  5. evelikov commented on Aug 15, 2023

    @evelikov
    Collaborator

    I've added the required notes to the "move distro specifics into the config" task and I'll be closing this in favour of it.

    Hope that's OK, I see you've got a local workaround in Debian for the short term.

  6. added a commit that references this issue on Dec 6, 2023
    4c8057c
  7. added a commit that references this issue on Feb 8, 2024
    2315ab0
  8. added 2 commits that reference this issue on Feb 1, 2025
    276851d
    d3aedcd
  9. added a commit that references this issue on Feb 4, 2025
    878c618
  10. added a commit that references this issue on Feb 12, 2025
    c5ceed9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions