zypper plugin for discovering reverse dependencies
a project by bzoltan1
Updated almost 3 years ago. 10 hacker ♥️. 5 followers.

Often when we test maintenance updates or when we decide to push an update for a package we want to know what that change may cause. Right now it is really difficult to figure out what package depends on a given package.

Motivation

When I was looking for orphan packages in SLE or in openSUSE what could start maintaining I was looking for low risk packages. Naturally for a less experienced package maintainer it is comforting to know that the package they start making updates for is not going to mess up hundreds of other packages. So when choosing a package to maintain it would be handy to know what other packages depend on the given package. Also when we are doing maintenance update validation for SLE it would be nice to know what other packages we should test with more attention. We test user scenarios and the whole platform, but if a package X depends on package Y and package Y gets a maintenance update then maybe it is a good idea to test the package X with extra attention.

Goal

  • Refresh a bit the rdepends project
  • Create a new project under the zypper development project in the Open Build Service
  • Push an initial version of a working prototype
  • Figure out if the plugin can be done in python without executing the zypper itself

Resources

Join this project

Looking for hackers with the skills:

zypper libsolv python

This project is part of:

Hack Week 22

Activity

  • over 2 years ago: okurz liked this project.
  • over 2 years ago: wfrisch liked this project.
  • over 2 years ago: iivanov liked this project.
  • almost 3 years ago: dfaggioli liked this project.
  • almost 3 years ago: idefx liked this project.
  • almost 3 years ago: robert.richardson liked this project.
  • almost 3 years ago: bzoltan1 added keyword "zypper" to this project.
  • almost 3 years ago: bzoltan1 added keyword "libsolv" to this project.
  • almost 3 years ago: bzoltan1 added keyword "python" to this project.
  • almost 3 years ago: bzoltan1 started this project.
  • almost 3 years ago: dmdiss liked this project.
  • almost 3 years ago: tinita liked this project.
  • almost 3 years ago: fbonazzi liked this project.
  • almost 3 years ago: amanzini liked this project.
  • almost 3 years ago: bzoltan1 originated this project.


    • Comments

    • dancermak
      almost 3 years ago by dancermak | Reply

      You might want to look at dnf's repoquery command, which supports exactly this use case. (And you can actually use dnf against openSUSE & SLE repos)

      • bzoltan1
        almost 3 years ago by bzoltan1 | Reply

        Thank you for the idea Dan. I will check it out. I am coming from Debian and Ubuntu and there is apt-cache rdepends command for this purpose.

      • zbenjamin
        almost 3 years ago by zbenjamin | Reply

        Or use the zypper se --requires-pkg functionality ;). It is not recursive though so it only checks the reverse deps of the given package

    Similar Projects

    Bring to Cockpit + System Roles capabilities from YAST by miguelpc

    Bring to Cockpit + System Roles features from YAST

    Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.

    Goals

    The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.

    Resources

    A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit

    Linux System Roles: https://linux-system-roles.github.io/