Hi All!
golinux asked me to forward this message to the TDE mailing list :-)
Nik
To: trinity-users(a)lists.pearsoncomputing.net
Subject: TDE on Devuan
Date: Fri, 12 May 2017 13:37:29 -0500
From: golinux(a)dyne.org
Greetings from the Devuan project!
Several Devuan users have chosen TDE as their DE. Dr. Nikolaus Klepp
has even customized the 'Plastic' theme to match the default Devuan
desktop! Devuan Stable will be released soon and then we will turn our
attention to Ascii (Stretch). If TDE is compatible with Ascii (not
entangled with systemd) we are hoping to get it packaged so users will
be able to install TDE directly from our repos. Thanks for providing a
viable alternative!
Cheers!
golinux
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
All,
It's that time of year again! As we look toward the release of Debian
Stretch and another version of TDE, I'd like to ask for your continued
support to help keep TDE online.
This year I'm going to try something new. If you donate $40 to TDE [1], I
will allow 2 months access to the nightly build repositories that now
include Debian Stretch and Raspbian Jessie. Additionally, I'd like those
who donate at this level to nominate two bugs that I will personally look
into (excepting those relating to support for Wayland, Qt4/Qt5, or
Webkit). This way your donations have a direct and positive effect on TDE
itself, and TDE can continue to exist in its current form.
Personally I would suggest the LibreOffice integration bug or possibly an
update of the GTK3 theme engine to fix the rendering bugs as potential
candidates, but in the end it's up to you! A full listing of open bugs is
available here:
http://bugs.trinitydesktop.org/buglist.cgi?bug_status=__open__&content=&no_…
As always, thank you for your support and continued feedback -- we
couldn't develop TDE without it!
Tim
[1] https://trinitydesktop.org/donate.php
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlj3qjAACgkQLaxZSoRZrGEhXwDcDpHwUy8Z77OEEKHrdVMSqlcW
6uT+v3pMwqNAXQDeM9WnwPpziYGFQIsfb5I6DiVBLNsZaBL2tab+yw==
=FFOS
-----END PGP SIGNATURE-----
Hi all
I get following error when building tdepim on Stretch. Two months ago I was
able to build it. Since then I updated Stretch. It is looking in the wrong
directory. Do you know by chance What I can change to make it build?
The files are in
obj-x86_64-linux-gnu/kontact/plugins/korganizer/libkontact_journalplugin.so
Also Slavek, Michele, can we clear the issue with the knotes revision/date
tracking? Otherwise I can not pull the last from the repo
thanks and regards
dh_shlibdeps -pkontact-trinity -Xopt/trinity/lib/trinity/libkontact_korganizer-trinityplugin.so -Xopt/trinity/lib/trinity/libkontact_specialdatesplugin.so -Xopt/trinity/lib/trinity/libkontact_journalplugin.so -Xopt/trinity/lib/trinity/libkontact_kpilot-trinityplugin.so -Xopt/trinity/lib/trinity/libkontact_todoplugin.so -- -dRecommends
debian/kontact/opt/trinity/lib/trinity/libkontact_korganizer-trinityplugin.so
debian/kontact/opt/trinity/lib/trinity/libkontact_specialdatesplugin.so -dSuggests
debian/kontact/opt/trinity/lib/trinity/libkontact_journalplugin.so
debian/kontact/opt/trinity/lib/trinity/libkontact_kpilot-trinityplugin.so
debian/kontact/opt/trinity/lib/trinity/libkontact_todoplugin.so -dDepends
dpkg-shlibdeps: error: cannot read
debian/kontact/opt/trinity/lib/trinity/libkontact_journalplugin.so: No such
file or directory
dh_shlibdeps: dpkg-shlibdeps -Tdebian/kontact-trinity.substvars -dRecommends
debian/kontact/opt/trinity/lib/trinity/libkontact_korganizer-trinityplugin.so
debian/kontact/opt/trinity/lib/trinity/libkontact_specialdatesplugin.so -dSuggests
debian/kontact/opt/trinity/lib/trinity/libkontact_journalplugin.so
debian/kontact/opt/trinity/lib/trinity/libkontact_kpilot-trinityplugin.so
debian/kontact/opt/trinity/lib/trinity/libkontact_todoplugin.so -dDepends
debian/kontact-trinity/opt/trinity/bin/kontact
debian/kontact-trinity/opt/trinity/lib/trinity/libkontact_newstickerplugin.so
debian/kontact-trinity/opt/trinity/lib/trinity/kcm_kontact.so
debian/kontact-trinity/opt/trinity/lib/trinity/libkontact_weatherplugin.so
debian/kontact-trinity/opt/trinity/lib/trinity/libkontact_karm.so
debian/kontact-trinity/opt/trinity/lib/trinity/libkontact_korganizerplugin.so
debian/kontact-trinity/opt/trinity/lib/trinity/libkontact_knodeplugin.so
debian/kontact-trinity/opt/trinity/lib/trinity/kcm_sdsummary.so
debian/kontact-trinity/opt/trinity/lib/trinity/kcm_korgsummary.so
debian/kontact-trinity/opt/trinity/lib/trinity/libkontact_knotesplugin.so
debian/kontact-trinity/opt/trinity/lib/trinity/kcm_kmailsummary.so
debian/kontact-trinity/opt/trinity/lib/trinity/libkontact_summaryplugin.so
debian/kontact-trinity/opt/trinity/lib/trinity/libkontact_kaddressbookplugin.so
debian/kontact-trinity/opt/trinity/lib/trinity/libkontact_kmailplugin.so
debian/kontact-trinity/opt/trinity/lib/trinity/kcm_kontactknt.so
debian/kontact-trinity/opt/trinity/lib/trinity/libkontact_akregator.so
debian/kontact-trinity/opt/trinity/lib/trinity/kcm_kontactsummary.so
debian/kontact-trinity/opt/trinity/lib/libkontact.so.1.0.0
debian/kontact-trinity/opt/trinity/lib/libkpinterfaces.so.1.0.0 returned
exit code 2
/usr/share/cdbs/1/rules/debhelper.mk:333: recipe for
target 'binary-predeb-IMPL/kontact-trinity' failed
make: *** [binary-predeb-IMPL/kontact-trinity] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit
status 2
On Sun, Apr 30, 2017 at 21:23 (+0200), deloptes wrote:
> Keith Daniels wrote:
>> My bias is anti systemd, just so you know.-- scant documentation
>> and there has never been a security review of its package.
> Meanwhile the situation has improved . There are many things
> improved including documentation. What I can recommend is the
> "systemd cheat sheet" which can be found in different flavors
> around.
> Just few examples.
> https://wiki.debian.org/systemd/CheatSheet
> https://gist.github.com/mbodo/8f87c96ce11e91f80fbf6175412a2206
> My personal experience is ... after looking into it I used systemd
> free debian for some time until I was ready to move my system to
> systemd. It took me few hours ... mainly fixing some custom
> networking logic (scripts that would execute on certain conditions)
> and migrating few scripts.
> Since than I can not complain. I moved all systems from init to
> systemd - no issue.
> I can just conclude that the main problem is the unwillingness to
> grow.
I don't know whether that is merely a poorly-thought out idea or a
deliberately abrasive obnoxious over-generalization. There is a lot
of debate about the merits of systemd, and some people have come to
the conclusion (rightly or wrongly) that they would prefer to not use
it in their system.
> Of course I can understand this - why fixing something again after
> some 10-15y when it was working flawlessly ...
Are you talking about ("somethign") SysV (or BSD) init scripts? 10-15 years?
Perhaps more like 40 years.
> but guys this is called evolution - for good or for bad.
So if it is possibly bad, why would we want to evolve in that direction?
I use Slackware, and the guy in charge has made the conscious
decision to not use systemd, and it seems like he is unlikely to
change that any time soon. There are currently other distros with
similar strategies. Do people working on Trinity really want to
alienate people who use systemd-free distros? That seems like a bad
idea to me, but that is just my opinion.
Jim
TDM according to ps -A is "running" when init completes even though multi-user
is default target, and regardless whether 3 or 5 or neither is included on
cmdline. Killall tdm then startx does produce a TDE session, but there's no
.xsession-errors.
There doesn't seem to be any kind of clues I can decipher in any logs:
http://fm.no-ip.com/Tmp/Linux/Xorg/tdm.log-fi965-stretchhttp://fm.no-ip.com/Tmp/Linux/Xorg/xorg.0.log-fi965-stretch
ii tdm-trinity 4:14.0.5~pre14-0debian9.0.0+2~a amd64
# inxi -c0 -v1
System: Host: fi965 Kernel: 4.9.0-2-amd64 x86_64 (64 bit) Desktop: N/A
Distro: Debian GNU/Linux 9 (stretch)
CPU: Dual core Intel Core2 6700 (-MCP-) speed: 2668 MHz (max)
Graphics: Card: Advanced Micro Devices [AMD/ATI] Cedar [Radeon HD
5000/6000/7350/8350 Series]
Display Server: X.org 1.19.2 drivers: modesetting (unloaded: fbdev,vesa)
tty size: 111x36 Advanced Data: N/A for root
# systemctl status tdm
â tdm.service - Trinity Display Manager
Loaded: loaded (/lib/systemd/system/tdm.service; static; vendor preset: enabled)
Active: inactive (dead)
Docs: man:tdm-trinity(1)
Is ignoring the default target normal or expected on Debian running systemd?
Searching BZ for comment including systemd and target produced no hits except
for an Ubuntu crasher. Is there some way to get TDM to not start automatically
on Stretch boot?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/