said Dr. Nikolaus Klepp via tde-users: | I have these 2 lines on my devuan testing, which results in TDE 14.2 | dev: | | deb http://mirror.ppa.trinitydesktop.org/trinity-testing ceres main | deps extra deb-src http://mirror.ppa.trinitydesktop.org/trinity-testing | ceres main deps extra I've been running the almost-soup TDE. I'm perfectly willing to run the not-soup-yet version, but for that to do one any good I'd need to have a sense of what log files to maintain to report anything that breaks. What is useful in making a good bug report? (The automatic reporting system here has never to my knowledge worked at all.) Also, on Debian itself instead of "testing" I can use "trixie." Is that true of TDE as well? I don't mean as in trinity-testing, but in terms of the target, ie. trixie instead of bookworm. -- dep Pictures: http://www.ipernity.com/doc/depscribe/album Column: https://ofb.biz/author/dep/ ____________________________________________________ tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx