FS#58369 - [wesnoth] 1.14.0 upgrade needs to replace wesnoth-data

Attached to Project: Community Packages
Opened by LightDot (lightdot) - Friday, 27 April 2018, 15:50 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 28 April 2018, 14:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Previous wesnoth version consisted of wesnoth and wesnoth-data, now only wesnoth remains.

When upgrading from wesnoth 1.12.6-8 and wesnoth-data 1.12.6-1, the wesnoth 1.14.0-1 doesn't provide or obsolete the old wesnoth-data package.

Consequently, the old wesnoth-data package remains installed on the system and its files conflict with the upgrade. How did this get past testing? ;)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 28 April 2018, 14:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  wesnoth 1.14.0-2
Comment by Jens G (Thah) - Friday, 27 April 2018, 19:55 GMT
I can confirm this.

IMO due to the size of the -data package (~350MB for v1.12.6) the split made sense: When you look at the revisions of wesnoth{,-data} v1.12.6
the non-data part had to be rebuilt 7 times while the data part stayed at revision 1 which saved a lot of essentially unnecessary bandwith/time
while upgrading (many people still don't have fast internet).
Comment by LightDot (lightdot) - Friday, 27 April 2018, 23:29 GMT
Indeed, the division to wesnoth and wesnoth-data looks reasonable due to size. The update from 1.14.0-1 to 1.14.0-2 took 391.05 MB to download, just for this simple PKGBUILD change...
Comment by Jens G (Thah) - Saturday, 28 April 2018, 06:25 GMT
If the packager agreed to re-split the package maybe that could be done the next time when a rebuilt/upgrade
is necessary, since the upgrade issue itself seems to be resolved now?

Loading...