Packages files from /etc to /usr/lib, how to adjust packages?
Hi, NetworkManager upstream moved many stuff from /etc/NetworkManager to /usr/lib/NetworkManager, like the dispatcher.d and VPN directories. We have many packages which still install their stuff into e.g. /etc/NetworkManager/dispatcher.d/ This is a specific example, but many other packages suffer from the same problem. So dbus upstream moved also many files from /etc/dbus-1 to /usr/share/dbus-1, and you can continue this list with other "infrastructure" packages. What would be a good way to: - inform all package maintainers that they have to move their files? - make sure new packages make it right from the beginning? I think one option would be to add new rules to rpmlint to forbid files in /etc/NetworkManager or /etc/dbus-1? Any toughts? Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Ivo Totev (HRB 36809, AG Nürnberg)
On Thursday 2022-02-24 12:04, Thorsten Kukuk wrote:
What would be a good way to: - inform all package maintainers that they have to move their files?
opensuse-factory should be ok, I think. The other issue is that, even though so notified, whether they will follow up is up to everybody individually. Sometimes, there will be movement only when a submit request or a bug report is present.
- make sure new packages make it right from the beginning?
Probably an rpmlint check, though I am not sure if opensuse-review-bot currently autodeclines based on that.
On Thu, 2022-02-24 at 12:23 +0100, Jan Engelhardt wrote:
On Thursday 2022-02-24 12:04, Thorsten Kukuk wrote:
What would be a good way to: - inform all package maintainers that they have to move their files?
opensuse-factory should be ok, I think. The other issue is that, even though so notified, whether they will follow up is up to everybody individually. Sometimes, there will be movement only when a submit request or a bug report is present.
- make sure new packages make it right from the beginning?
Probably an rpmlint check, though I am not sure if opensuse-review-bot currently autodeclines based on that.
as opensuse-review-bot does not exist, it does not decline :) You probably mean factory-auto: that one works on sources, way before something is staged: it has no access to build results (the ones from devel projects have proven unreliable in the past and often times are just not present when submissions happen) With rpmlint we have the chance to add 'fatal errors' (like license errors) to block the packages in an adi from building (usually we let them build in devel projects, so maintainers can test their packages) The problem there: we can only arm a new fatal error once all packages currently violating the new check are fixed. So it can help avoid the issues in new packages, but the delay until it can be armed in Factory is substantial. Cheers, Dominique
What would be a good way to: - inform all package maintainers that they have to move their files? - make sure new packages make it right from the beginning?
I think one option would be to add new rules to rpmlint to forbid files in /etc/NetworkManager or /etc/dbus-1?
I think the way to complete this is: - Inform Factory of new policy - Create new rpm macros for the dirs - Create a new rpmlint check (non fatal) so that a package list of offending packages is listed at rpmlint.opensuse.org NetworkManager already has a macro for the VPN change called %_vpnservicedir It needs another one for the dispatcher changes -- Callum Farmer gmbr3@opensuse.org openSUSE - gmbr3
participants (4)
-
Callum Farmer -
Dominique Leuenberger / DimStar -
Jan Engelhardt -
Thorsten Kukuk