Re: [aur-requests] [PRQ#2585] Merge Request for upower-pm-utils
Hi Muflone, Recently I've filed a request to merge upower-pm-utils into upower-nosystemd (comments by arcanis starting in https://lists.archlinux.org/pipermail/aur-requests/2015-March/005436.html), however you later rejected the request and merged upower-nosystemd into upower-pm-utils instead. I've posted a follow-up message to the AUR mailing list (https://lists.archlinux.org/pipermail/aur-requests/2015-March/005679.html). The issue now is that the maintainer refuses to change the eudev dependency to udev, preventing the package's use with systemd-udev (see the discussion in https://aur.archlinux.org/packages/upower-pm-utils/). I'm aware it's easy to change the PKGBUILD for my personal use; but while booting to a different init is a fairly straightforward process, removing systemd itself (and using eudev) is anything but. That latter step would be necessary to use the package in question is misleading. What would you suggest as best course of action? Regards, Alad
Hello
Recently I've filed a request to merge upower-pm-utils into upower-nosystemd (comments by arcanis starting in https://lists.archlinux.org/pipermail/aur-requests/2015-March/005436.html), however you later rejected the request and merged upower-nosystemd into upower-pm-utils instead.
There were two conflicting requests [1] [2] to merge the two packages. One of these requests was made from the maintainer of the upower-nosystemd package [3] and he told us: "I've agreed with the offer of upower-pm-utils maintainer to merge these packages." [2] Therefore the maintainer of upower-nosystemd asked us to delete the package and merge it into upower-pm-utils (which has also a better name and lacks any foolish nosytemd suffix).
I'm aware it's easy to change the PKGBUILD for my personal use; but while booting to a different init is a fairly straightforward process, removing systemd itself (and using eudev) is anything but. That latter step would be necessary to use the package in question is misleading.
The package systemd if part of the core packages in Arch Linux, everything that is against the official init system is entirely not supported by the distribution, including on what happens on the AUR. Please don't ask us to solve issues between the maintainers of two unsupported packages. This is the main reason why I ask the requesters to settle the things with the packages maintainers and don't force us to do a choice against a package or another. [1] https://lists.archlinux.org/pipermail/aur-requests/2015-March/005472.html [2] https://lists.archlinux.org/pipermail/aur-requests/2015-March/005396.html [3] https://aur.archlinux.org/account/TZ86/ Greetings -- Fabio Castelli aka Muflone
Muflone schreef op 2015-03-21 16:35:
Hello
Recently I've filed a request to merge upower-pm-utils into upower-nosystemd (comments by arcanis starting in https://lists.archlinux.org/pipermail/aur-requests/2015-March/005436.html), however you later rejected the request and merged upower-nosystemd into upower-pm-utils instead.
There were two conflicting requests [1] [2] to merge the two packages.
One of these requests was made from the maintainer of the upower-nosystemd package [3] and he told us: "I've agreed with the offer of upower-pm-utils maintainer to merge these packages." [2]
Therefore the maintainer of upower-nosystemd asked us to delete the package and merge it into upower-pm-utils (which has also a better name and lacks any foolish nosytemd suffix).
I'm aware it's easy to change the PKGBUILD for my personal use; but while booting to a different init is a fairly straightforward process, removing systemd itself (and using eudev) is anything but. That latter step would be necessary to use the package in question is misleading.
The package systemd if part of the core packages in Arch Linux, everything that is against the official init system is entirely not supported by the distribution, including on what happens on the AUR.
Please don't ask us to solve issues between the maintainers of two unsupported packages. This is the main reason why I ask the requesters to settle the things with the packages maintainers and don't force us to do a choice against a package or another.
[1] https://lists.archlinux.org/pipermail/aur-requests/2015-March/005472.html [2] https://lists.archlinux.org/pipermail/aur-requests/2015-March/005396.html [3] https://aur.archlinux.org/account/TZ86/
Greetings
Thanks Muflone, I wasn't aware of the second merge request and will keep your advice in mind. Regards, Alad
participants (2)
-
Alad Wenter
-
Muflone