FS#33762 - [digikam] conflicts with kde-l10n-*

Attached to Project: Arch Linux
Opened by Antonio Rojas (arojas) - Friday, 08 February 2013, 10:15 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 03 June 2013, 17:43 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ronald van Haren (pressh)
Andrea Scarpino (BaSh)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
The file /usr/share/locale/es/LC_MESSAGES/libkipi.mo is in both kde-l10n-es and digikam
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Monday, 03 June 2013, 17:43 GMT
Reason for closing:  Fixed
Additional comments about closing:  digikam 3.2.0-2
Comment by Andrea Scarpino (BaSh) - Friday, 08 February 2013, 11:18 GMT
Are you using digikam 3.0?
Comment by Oliver Goethel (deezy) - Friday, 08 February 2013, 11:23 GMT
digikam 3.0-rc1 is now in Extra. So it comes together with the kde 4.10 update.
Comment by Antonio Rojas (arojas) - Friday, 08 February 2013, 12:51 GMT
  • Field changed: Percent Complete (100% → 0%)
Yes, this is with kde 4.10 and digikam 3.0
Comment by Ronald van Haren (pressh) - Friday, 08 February 2013, 12:57 GMT
Suppose the libkipi.mo files don't belong in the digikam package. I remove it with the 3.0.0 final update tonight that was just uploaded to the kde servers.

@Andrea: If you can do it earlier please do so.
Comment by Andrea Scarpino (BaSh) - Friday, 08 February 2013, 12:58 GMT
  • Field changed: Summary ([kde-l10n][digikam] file conflict → [digikam] conflicts with kde-l10n-*)
I'm fixing digikam and report this upstream
Comment by Ronald van Haren (pressh) - Friday, 08 February 2013, 13:05 GMT
Don't forget to change the source url for the new version ;-)

http://download.kde.org/stable/digikam/digikam-3.0.0.tar.bz2
Comment by Antonio Rojas (arojas) - Monday, 03 June 2013, 17:18 GMT
  • Field changed: Percent Complete (100% → 0%)
Happening again with 3.2.0, it seems this was never fixed upstream
Comment by Andrea Scarpino (BaSh) - Monday, 03 June 2013, 17:19 GMT
Damn. I did check it, but I failed.

Loading...