Re: appimages still failing
On Donnerstag, 30. Dezember 2021 14:39:46 CET Thomas Baumgart via KMyMoney-devel wrote: > On Donnerstag, 30. Dezember 2021 09:58:55 CET Thomas Baumgart via > KMyMoney-devel wrote: > > [...] > > > What I will do next: > > > > 4) Take the results of 2) and try them locally (which is OK) and then > > somehow > >get it to the CI craft build (the fix is in git only as of this time, so > >there is a bit of work ahead) > > I added the fix to the KDE repo and ran the build. It now fails in a > different location > (which apparently worked before). I already sent feedback to the author. > Let's see if > he can make head and tail out of it. Alexander and I were able to identify the problem and located it in Gwenhywfar's configure and build system. We made the necessary changes in https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/7674e6d608993883a49f2022e6c6dc345bca4eaf https://invent.kde.org/packaging/craft-blueprints-kde/-/commit/a533c32b0b712c5e4308bfaa1de8e54581ef5797 as well as upstream https://www.aquamaniac.de/rdm/projects/gwenhywfar/repository/revisions/ba5a3653c66b3d881f85565ad6126e27bc0d1ffd/diff This now builds all dependencies and KMyMoney itself but fails while packaging :( So we're a step closer to a working appimage. I contacted KDE-sysadmin and asked them to take a look. > > 6) do more work on KMyMoney (Multi-Currency-Input and Cusomizable tab order > > for input fields) > > Progressing. Had to do a bit of house-hold work on the side. Screenshot attached. Not functional at all atm. Inspired by Qt-Designer p.s. I don't have a son (see below) but I love my random footer generator -- Regards Thomas Baumgart https://www.signal.org/ Signal, the better WhatsApp - My son asked me what our IP address was. I pointed to the toilet. - signature.asc Description: This is a digitally signed message part.
Re: appimages still failing
On 2021.12.30 03:58, Thomas Baumgart wrote: On Donnerstag, 30. Dezember 2021 01:17:09 CET Jack via KMyMoney-devel wrote: It seems that since converting the appimage builds to use Craft, they have not completed a successful build. As I read the logs, it looks like it's failing building deps, specifically when linking gwenhywfar. The error I see is "/usr/bin/ld: cttest.o: undefined reference to symbol 'libintl_bindtextdomain'." From my likely inadequate searching and simplistic understanding, might this be as simple as a missing -lintl somewhere? That is what I was thinking, the problem is to figure out where this needs to be inserted. NOTE: I finally found and dug into the Craft blueprints repository, and found a relevant MR from three days ago - so I can see that this is being worked on. Can you post the link? Then I can save some time for the search. https://invent.kde.org/packaging/craft-blueprints-kde is for the repository. There are only 5 MRs, and I see you already found it. Posting here anyway for anyone following this thread. r> > it just slipped through the cracks. What I have done so far: 1) chatted with KDE sysadmin about the problem to get their feedback 2) contacted the maintainer of Gwen/AqB to get help/fix. Here's what he did yesterday https://www.aquamaniac.de/rdm/projects/gwenhywfar/repository/diff/configure.ac?utf8=%E2%9C%93=f47694a4f8721def02424224d661b0971d8f5bfc_to=4961b5bfce972848f7ae233a46d03849e20953e7 3) work on setting up a docker image to build AppImages (time consuming process - mostly waiting) What I will do next: 4) Take the results of 2) and try them locally (which is OK) and then somehow get it to the CI craft build (the fix is in git only as of this time, so there is a bit of work ahead) 5) continue with 3) 6) do more work on KMyMoney (Multi-Currency-Input and Cusomizable tab order for input fields) Hope that gives some insights -- Regards Thomas Baumgart https://www.signal.org/ Signal, the better WhatsApp - The good thing about FOSS is that people can see your code and comment it. The bad thing is that people can see your code and comment it. (asoliverez) -
Re: appimages still failing
On Donnerstag, 30. Dezember 2021 09:58:55 CET Thomas Baumgart via KMyMoney-devel wrote: [...] > What I will do next: > > 4) Take the results of 2) and try them locally (which is OK) and then somehow >get it to the CI craft build (the fix is in git only as of this time, so >there is a bit of work ahead) I added the fix to the KDE repo and ran the build. It now fails in a different location (which apparently worked before). I already sent feedback to the author. Let's see if he can make head and tail out of it. > 5) continue with 3) Got a basic system (with compiled Qt and libs ready as docker image). Keep going. > 6) do more work on KMyMoney (Multi-Currency-Input and Cusomizable tab order > for input fields) Progressing. Had to do a bit of house-hold work on the side. -- Regards Thomas Baumgart https://www.signal.org/ Signal, the better WhatsApp - Progress isn't made by early risers. It's made by lazy men trying to find easier ways to do something. -- Robert Heinlein - signature.asc Description: This is a digitally signed message part.
Re: appimages still failing
Hi everyone, On Donnerstag, 30. Dezember 2021 01:17:09 CET Jack via KMyMoney-devel wrote: > It seems that since converting the appimage builds to use Craft, they > have not completed a successful build. As I read the logs, it looks > like it's failing building deps, specifically when linking gwenhywfar. > The error I see is "/usr/bin/ld: cttest.o: undefined reference to > symbol 'libintl_bindtextdomain'." From my likely inadequate searching > and simplistic understanding, might this be as simple as a missing > -lintl somewhere? That is what I was thinking, the problem is to figure out where this needs to be inserted. > NOTE: I finally found and dug into the Craft blueprints repository, > and found a relevant MR from three days ago - so I can see that this is > being worked on. Can you post the link? Then I can save some time for the search. > I know available time is tight, and actually fixing > the problem is certainly more important than talking about it, but I'd > like to request that there be at least occasional updates on the status > of this (and similar future) issues to save a lot of folks wondering if > it just slipped through the cracks. What I have done so far: 1) chatted with KDE sysadmin about the problem to get their feedback 2) contacted the maintainer of Gwen/AqB to get help/fix. Here's what he did yesterday https://www.aquamaniac.de/rdm/projects/gwenhywfar/repository/diff/configure.ac?utf8=%E2%9C%93=f47694a4f8721def02424224d661b0971d8f5bfc_to=4961b5bfce972848f7ae233a46d03849e20953e7 3) work on setting up a docker image to build AppImages (time consuming process - mostly waiting) What I will do next: 4) Take the results of 2) and try them locally (which is OK) and then somehow get it to the CI craft build (the fix is in git only as of this time, so there is a bit of work ahead) 5) continue with 3) 6) do more work on KMyMoney (Multi-Currency-Input and Cusomizable tab order for input fields) Hope that gives some insights -- Regards Thomas Baumgart https://www.signal.org/ Signal, the better WhatsApp - The good thing about FOSS is that people can see your code and comment it. The bad thing is that people can see your code and comment it. (asoliverez) - signature.asc Description: This is a digitally signed message part.
appimages still failing
It seems that since converting the appimage builds to use Craft, they have not completed a successful build. As I read the logs, it looks like it's failing building deps, specifically when linking gwenhywfar. The error I see is "/usr/bin/ld: cttest.o: undefined reference to symbol 'libintl_bindtextdomain'." From my likely inadequate searching and simplistic understanding, might this be as simple as a missing -lintl somewhere? NOTE: I finally found and dug into the Craft blueprints repository, and found a relevant MR from three days ago - so I can see that this is being worked on. I know available time is tight, and actually fixing the problem is certainly more important than talking about it, but I'd like to request that there be at least occasional updates on the status of this (and similar future) issues to save a lot of folks wondering if it just slipped through the cracks. Thanks. Jack
