As with every new version of koffice, the update of koffice-i18n is delayed. As koffice-i18n depends on koffice-1.3.2 at the moment, portage gets in an endless upgrade/downgrade cycle. koffice 1.3.3 works fine with 18n files from 1.3.2. Two solutions are possible (as this will 99% happen again with 1.3.4) make koffice-i18n not depend on the specific koffice version but a more general approach (a la koffice-1.3.*) Or put some pointer somewhere that the i18n packages stay in sync. The KDE team does release the i18n packages in sync, so it should not be that hard. This problem is also valid for main KDE. Reproducible: Always Steps to Reproduce: 1. emerge koffice 2. emerge koffice-i18n 3. emerge -puD world
committed 1.3.3 for now >Or put some pointer somewhere that the i18n packages stay in sync. It's the advantage using stable ebuilds only, that devs (should) take care for this. :] I'll have a look at this later. The ebuilds need a clean up anyways.
Longitud: 1,078,151 [application/x-tar] 100%[===============================================================================>] 1,078,151 25.66K/s ETA 00:00 17:36:33 (25.60 KB/s) - `/usr/portage/distfiles/koffice-i18n-es-1.3.3.tar.bz2' guardado [1078151/1078151] !!! File is corrupt or incomplete. (Digests do not match) >>> our recorded digest: 2058c70dc6a8f2fd65321785a4ccf2ee >>> your file's digest: dbbb10da7360f109ac2199f00442d9c1 !!! File does not exist: /usr/portage/distfiles//koffice-i18n-es-1.3.3.tar.bz2
mapelo: fixed
The koffice-i18n package must be updated together with the koffice/koffice-meta packages to prevent an upgrade/downgrade loop. We'll just have to be careful not to make such a mistake ever again...
