Please remove rhn-client-tools and python-gudev from bionic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt-spacewalk (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
lxkeymap (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
python-gudev (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
python-xklavier (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
rhn-client-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
rhnsd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Please remove all the listed below packages (both source and binary) from the bionic archive. All packages are no longer actively maintained and have been requested to be removed from Debian as well (with rhn-client-tools, rhnsd, apt-spacewalka and python-xklavier already removed from testing). lxkeymap did not have a new update since over 4 years.
python-gudev
rhn-client-tools
rhnsd
apt-spacewalk
python-xklavier
lxkeymap
Dependency chain:
$ reverse-depends src:python-gudev
Reverse-Depends
===============
* rhn-client-tools (for python-gudev)
$ reverse-depends src:rhn-
Reverse-Depends
===============
* apt-transport-
* rhnsd (for rhn-client-tools)
$ reverse-depends src:rhnsd
Reverse-Recommends
==================
* apt-transport-
$ reverse-depends src:apt-spacewalk
No reverse dependencies found
$ reverse-depends src:python-xklavier
Reverse-Depends
===============
* lxkeymap (for python-xklavier)
$ reverse-depends src:lxkeymap
No reverse dependencies found
Build-dependency chain:
$ reverse-depends -b src:apt-spacewalk
No reverse dependencies found
$ reverse-depends -b src:rhnsd
No reverse dependencies found
$ reverse-depends -b src:lxkeymap
No reverse dependencies found
$ reverse-depends -b src:python-gudev
No reverse dependencies found
$ reverse-depends -b src:rhn-
No reverse dependencies found
$ reverse-depends -b src:python-xklavier
No reverse dependencies found
The python-gudev and python-xklavier are depending on a removed transitional package python-gobject-dev and keeping it around. The best way to proceed would be to simply remove the whole dependency chain from the archives completely.
looks good to me