Arch Linux User Repository

Updated

Well, it's NOT LIKE the upstream author isn't having LOTS of problems and releasing quite often these days. Hi Hi.... Anyways, I decided to "comment-out" the conflicts field AND add the suggested "--without-asciidoc" as a config directive. *** Hope this helps !

This package is out-of-date because it attempts to download the version of fldigi 4.1.15 which does not appear to be there anymore because they updated it to 4.1.16. Maintainer, please fix!

For the time being, download the current PKGBUILD, edit change the "pkgver" variable from 4.1.15 to 4.1.16. You will also have to update the md5sum and sha256sum. Download fldigi from the official link found in the PKGBUILD or google it. You should download "fldigi-4.1.16.tar.gz". Then run sha256sum and md5sum on the file and replace the sums in the PKGBUILD. Now run makepkg -si where it should now attempt to download and build fldigi.

It might fail because you are missing some dependent packages, these are found in the aur and I just downloaded them using my aur-helper: yay -S cty flxmlrpc hamradio-menus

Should work after updating pkgver, updating the sums, and downloading the proper packages!

Do we even need asciidoc enabled for this package? I would expect that to only be fore developers which would probably build fldigi locally?

Possible build error related to broken dialogs/guide.cxx is caused by that asciidoc is for some reason inserting several \x0D (^M) characters. It can be fixed, for manual builds by adding

sed -i 's/\r//g' ./src/dialogs/guide.cxx

into PKGBUILD:build() just above make ..., after first makepkg failed, then running makepkg -e, then makepkg -U <generated pkg file>.

Or by adding --without-asciidoc configure flag.

you are right, the patch doesn't cleanly apply. and i found out that that is because the lines are fine when the source is first extracted. they only get changed during the build process, by some process that is prefixed with "GUIDE" in the build output. i will try and figure out what that process is, but that's gonna be tomorrow... sleep now. :P

Actually that patch is being "rejected" on the latest source.;

a) malformed: i.e. some of the lines begin like this;

\n\iv id=\"toc\">

b) Um...AND the line numbers do not match the source. (Off by one line)

c) finally it is written so to ADD newline characters (which are already there....)

ANYWAYS ...that's why I didn't use it.....Would/could you please check it grandchild ?

Sorry, but the solution is not to simply conflict with asciidoc. asciidoc is actually an optional make dependency. If it is present, then more things get built.

The solution would either be to apply the patch I made, or to explicitly disable the part that gets built when asciidoc is present. I haven't checked which part that is, and if it has a configure flag to disable it. Maybe it does?

Okey dokey.....made the appropriate change....thanks OM's ...es vy 73

Thanks for your very fast reactions. I can confirm that "asciidoc" causes the issue. I deinstalled it, after that the build process finished successfully. Then I reinstalled asciidoc. It is a workaround - but it works :)