FS#58212 - The glibmm package should specify versions of its dependencies

Attached to Project: Arch Linux
Opened by Marc Ranolfi (marc.2377) - Thursday, 12 April 2018, 23:51 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 13 April 2018, 00:22 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Today I inadvertently upgraded glibmm from version 2.54.1-1 to 2.56.0-1 (all I wanted was to reinstall it), and broke many things in my system.

This could have been prevented by using Arch's PKGBUILD syntax to specify dependency version (https://wiki.archlinux.org/index.php/PKGBUILD#depends).

Ideally, this should be done for ALL critical packages, specially those closely related to GNOME's Glib. And, of course, GNU's glibc (had a similar regarding glibc, a while ago).
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Friday, 13 April 2018, 00:22 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Arch pretty specifically does not support this use case.

Also glibmm is hardly a critical package just because you say so.

Loading...