https://bugs.kde.org/show_bug.cgi?id=420501
Harald Sitter changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=420501
--- Comment #5 from Harald Sitter ---
Shouldn't break anything.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420501
--- Comment #4 from Dag Andersen ---
Yes, it's probably just history...
Q: As a workaound, would it be possible to just change the project name in
release_data file manually to calligra/calligra?
Or would something else break?
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=420501
--- Comment #3 from Harald Sitter ---
You'll likely just to talk to sysadmins about moving the calligra repos to the
relevant modules then (extragear/playground/apps/whatever). I don't think there
is much or any benefit from sitting in a module that mea
https://bugs.kde.org/show_bug.cgi?id=420501
--- Comment #2 from Dag Andersen ---
Well, calligra does not (and afaics, will not) use the modele feature, as the
reason for splitting in the first place is to allow for separate releases.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=420501
--- Comment #1 from Harald Sitter ---
In the repo-metadata calligra is ambiguous. It can mean 'calligra' the module
or 'calligra/calligra' the repo within that module. The fact that it tars all
calligra/* when you just calligra is by design to allow eas
