Hello everyone,
I was advised to come here since I'm aware that there are at least a few that use TDE on FreeBSD. I have the port from the gitea repository but I've had a number of issues. I'm still fairly new to FreeBSD so sorry if I seem inexperienced. I am especially new to using ports since I only have one or two on my system. Let me try to elaborate what I've done so far:
I first attempted installing TDE in the beginning of May, which is when I first switched from Devuan to FreeBSD 13.0-RELEASE. This was right after the R14.0.10 release. I had the freebsd TDE folder and assumed I needed to build it with make install clean, as most ports are, and I (from what I remember) think it worked until I hit a snag. I stopped there and settled with Xfce which I was already using for the time being and completely forgot what the snag was.
I then tried it again yesterday, as I missed using TDE very much (as its most certainly my favorite desktop environment, which is why I'm subbed to these lists now =D ). I removed my desktop environment and login manager (Xfce + LightDM), and cloned the tde-packaging freebsd port once again. I had to run /make install clean///as root (I used doas, probably also did this the first attempt and just forgot), and everything was good and well until about 30 minutes into the make process when I received an error about pinentry-tqt. You can see my issue here: https://mirror.git.trinitydesktop.org/gitea/TDE/tde-packaging/issues/86. At this point, I was in a conversation on Matrix and a TDE user on Slackware was trying to help me out the best he could. I had been trying to fix it all day and by the end of it had a massive headache so I quit and installed Fluxbox temporarily (needed a way to communicate easier as well). I had tampered with the make directory quite a bit without backing it up so now I cloned it again and am making sure to keep an unmodified copy (so I don't have to go through the process of getting it all again with my horrible internet..)
So this morning I'm back at square one, which is why I'm here to ask how did any of you install it on FreeBSD? Did you run into the same issues, and is there any idea how I can go about getting it to work? I feel like I'm probably doing something wrong.
Hi!
Anno domini 2021 Sat, 5 Jun 13:39:26 -0500 Hunter via tde-users scripsit:
[...] So this morning I'm back at square one, which is why I'm here to ask how did any of you install it on FreeBSD? Did you run into the same issues, and is there any idea how I can go about getting it to work? I feel like I'm probably doing something wrong.
Oh that pinentry-tqt ... did you try building with portmaster? That was what I did and it did not turn out well. I had to build everything manually.
This is what I did, when it hit me:
- uninstall everything trinity - delete the ports tree of trinity - pkg autoremove - clone tde-packaging again, switch banch, enter freebsd/dependencies - manually enter each packages directory and do "make install clean" - same process for the core/...
Then modify /etc/ttys to your needs, i.e. make it start tdm instead of xdm.
Ohm and to speed up things I interrupted the make process whenever another package was about to be built that was also in packages. Installed that package, marked it as auto and run make again. Most likely there's a better way of doing this, but ... :)
Nik
Dr. Nikolaus Klepp wrote:
Oh that pinentry-tqt ... did you try building with portmaster? That was what I did and it did not turn out well. I had to build everything manually.
But what is the problem with pinentry-tqt exactly? Is it the TQt code or other part of the package. In any case I am still on the GnuPG mailing list and could pull some strings there to improve the code if you have improvement. I do not know if they build GnuPG for FreeBSD or you have probably a conflict because you pull the GnuPG code from somewhere else.
Can you explain?
Anno domini 2021 Sun, 06 Jun 08:46:55 +0200 deloptes scripsit:
Dr. Nikolaus Klepp wrote:
Oh that pinentry-tqt ... did you try building with portmaster? That was what I did and it did not turn out well. I had to build everything manually.
But what is the problem with pinentry-tqt exactly? Is it the TQt code or other part of the package. In any case I am still on the GnuPG mailing list and could pull some strings there to improve the code if you have improvement. I do not know if they build GnuPG for FreeBSD or you have probably a conflict because you pull the GnuPG code from somewhere else.
Can you explain?
It's not a problem with pinentry-tqt, it's a problem of the build system. By some obscure reason the build fails when you have not installed all build dependencies (so the ports system builds them) and you use one of the higher level makefiles. Somehow things get messed up when you do it this way and not by hand.
I'm sure there is just a little glitch causing it, but I don't have the slightest clue where to start looking.
Nik
Good morning (here anyway) :)
I'm still working in the core directory because I ran into another hitch. It turns out I will need tdepim, since tdeaddons depends on it and possibly more, so instead of skipping onward I'm trying to "grab the bull by the horns" and I have some more information on tdepim.
In the FreeBSD matrix room somebody gave me a tip I didn't know about - I could hit Ctrl + T to give more information on the process being ran:
load: 0.05 cmd: ninja 1195 [select] 4.02r 0.04u 0.00s 0% 22204k mi_switch+0xc1 sleepq_catch_signals+0x2e6 sleepq_wait_sig+0x9 _cv_wait_sig+0xe4 seltdwait+0xa9 kern_poll+0x51b sys_ppoll+0x6f amd64_syscall+0x10c fast_syscall_common+0xf8 make: Working in: /usr/home/hunter/Projects/freebsd/core/tdepim
I know this is jargon (it is for me anyway) but maybe someone will know more about what's going on because I can't find *anything* online about Ninja and this test function. This is about 10 minutes in. Last night when I first realized tdeaddons depended on tdepim I decided to leave it running for an hour, but it was still stuck there so I shut it down for the night. I just don't understand how 29 of the other tests finished but the 30th takes this long..
Thanks,
On Sun, 6 Jun 2021 07:44:24 -0500 Hunter via tde-users users@trinitydesktop.org wrote:
Good morning (here anyway) :)
I'm still working in the core directory because I ran into another hitch. It turns out I will need tdepim, since tdeaddons depends on it and possibly more, so instead of skipping onward I'm trying to "grab the bull by the horns" and I have some more information on tdepim.
I think the only thing in tdeaddons that depends on tdepim is kaddressbook-plugins. My suggestion would be, unless you know you know you need tdepim for something else, cherry-pick only the bits of tdeaddons that you need.
E. Liddell
Dne ne 6. června 2021 14:44:24 Hunter via tde-users napsal(a):
Good morning (here anyway) :)
I'm still working in the core directory because I ran into another hitch. It turns out I will need tdepim, since tdeaddons depends on it and possibly more, so instead of skipping onward I'm trying to "grab the bull by the horns" and I have some more information on tdepim.
In the FreeBSD matrix room somebody gave me a tip I didn't know about - I could hit Ctrl + T to give more information on the process being ran:
load: 0.05 cmd: ninja 1195 [select] 4.02r 0.04u 0.00s 0% 22204k mi_switch+0xc1 sleepq_catch_signals+0x2e6 sleepq_wait_sig+0x9 _cv_wait_sig+0xe4 seltdwait+0xa9 kern_poll+0x51b sys_ppoll+0x6f amd64_syscall+0x10c fast_syscall_common+0xf8 make: Working in: /usr/home/hunter/Projects/freebsd/core/tdepim
I know this is jargon (it is for me anyway) but maybe someone will know more about what's going on because I can't find *anything* online about Ninja and this test function. This is about 10 minutes in. Last night when I first realized tdeaddons depended on tdepim I decided to leave it running for an hour, but it was still stuck there so I shut it down for the night. I just don't understand how 29 of the other tests finished but the 30th takes this long..
Thanks,
There you see the listing like this? [29/30] Linking CXX executable libkcal/tests/testresource
The next step 30 is to run the tests as such and there are 455 of them: [30/30] Running tests ... Test project /usr/ports/x11/trinity/core/tdepim/work/tdepim-trinity_14.0.11~pre4/.build Start 1: testrecurrence__next__data/RecurrenceRule/ConnectDaily/ConnectDaily1.ics__ 1/455 Test #1: testrecurrence__next__data/RecurrenceRule/ConnectDaily/ConnectDaily1.ics__ .
Cheers
Thank you very much for your help everyone! I am *not* experienced enough with this! Attached is my working TDE environment here on FreeBSD 13 :) I finally got it working.
When I had that problem I talked about this morning with ninja, I eventually figured out I could skip the check (which it was stuck on) by commenting out "post-build: tde-cmake-check". Thankfully this is the only part where I had to do this.
Trinity works great with the applications which I am using. I noticed there were way more than I expected (I didn't think about the metapackages), so is there any way to remove those without removing the whole metapackage? I also have problems using kysguard (gives an error "Connection to localhost has been lost" which keeps popping up). This is also accompanied by the system load applet not working. These are the only errors I've had.
Congratulations on this release and it's very nice to be using Trinity on FreeBSD finally! :)
Anno domini 2021 Sun, 6 Jun 17:51:12 -0500 Hunter via tde-users scripsit:
Thank you very much for your help everyone! I am *not* experienced enough with this! Attached is my working TDE environment here on FreeBSD 13 :) I finally got it working.
When I had that problem I talked about this morning with ninja, I eventually figured out I could skip the check (which it was stuck on) by commenting out "post-build: tde-cmake-check". Thankfully this is the only part where I had to do this.
Trinity works great with the applications which I am using. I noticed there were way more than I expected (I didn't think about the metapackages), so is there any way to remove those without removing the whole metapackage? I also have problems using kysguard (gives an error "Connection to localhost has been lost" which keeps popping up). This is also accompanied by the system load applet not working. These are the only errors I've had.
Congratulations on this release and it's very nice to be using Trinity on FreeBSD finally! :)
Congratulations :)
Nik
-
deloptes -
Dr. Nikolaus Klepp -
E. Liddell -
Hunter -
Slávek Banko