Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 736750 - media-sound/qsynth-0.6.2 fails to build(?) due to broken translation files
Summary: media-sound/qsynth-0.6.2 fails to build(?) due to broken translation files
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-11 13:08 UTC by Eric F. GARIOUD
Modified: 2020-08-11 21:37 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Remove sr and ru translation files from the build (ignore_broken_translations.patch,769 bytes, patch)
2020-08-11 13:08 UTC, Eric F. GARIOUD
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Eric F. GARIOUD 2020-08-11 13:08:27 UTC
Created attachment 654112 [details, diff]
Remove sr and ru translation files from the build

Building media-sound/qsynth-0.6.2 leads to miscellaneous :

lrelease error : Parse error at src/translations/qsynth_xyz.ts, Premature end of document

xyz standing for sr (serbian) and ru (russian)

I feel just too old for parsing those files looking for the precise syntax error.

Waiting for upstream to correct those broken files, I suggest to simply remove those two langages from the TRANSLATIONS set of the src/CMakelists.txt.

Which is what the attached patch achieve.
Comment 1 Andreas Sturmlechner gentoo-dev 2020-08-11 18:19:43 UTC
Why no build.log?
Comment 2 Andreas Sturmlechner gentoo-dev 2020-08-11 18:22:32 UTC
Builds for me.
Comment 3 Jonas Stein gentoo-dev 2020-08-11 18:57:20 UTC
Thank you for the report. 
asturm couldn't reproduce it. 
We need to have all information at hand before ticket assignment. That is why I ask you to 
* attach the logs and 
* paste the emerge info 
as described on https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket
Please reopen this ticket (Status:UNCONFIRMED) afterwards.
Comment 4 Eric F. GARIOUD 2020-08-11 21:14:51 UTC
(In reply to Andreas Sturmlechner from comment #1)
> Why no build.log?

Simply because I do not ask you (or anybody else) to investigate!

And additionally because having spent a couple of hours making this package able to build from sources, I feel too old to revert and reemerge whatever broken ebuild for the sole sake of providing useless info.
Comment 5 Eric F. GARIOUD 2020-08-11 21:17:47 UTC
(In reply to Andreas Sturmlechner from comment #2)
> Builds for me.

Why no build.log ?

Don't take this personally but regarding an issue being acknowledged FTBFS upstream... that'd be at least informative for everybody!
Comment 6 Eric F. GARIOUD 2020-08-11 21:37:55 UTC
(In reply to Jonas Stein from comment #3)

Thank you Jonas for taking care of this package.
Feel free to mark this bug resolved fixed or whatever UNCONF as I won't provide any more info. (Per pure laziness)

As upstream rightly says... at the end of the day... that's just... xml files...
who would care ?

Anyone encountering the same issue can freely use the patch I provide.
I can also provide a patch to the ebuild if necessary upon request.