tde-users

users@trinitydesktop.org

6 participants
4292 discussions

Migration of services - 8. crash reports storage
by Slávek Banko 13 Dec '20

13 Dec '20

Hi all, the eighth service on the list of services to migrate is Crash report storage. -- Migration status -- While for previous services here I could bring positive information, now it's time for a service that is very sad. Because this service resides on old primary server, it requires migration. Unfortunately, we do not currently have any information about this service - nor the source code for server side. Therefore in the current state of service, we can not ensure the issuance of a new ssl certificate. For everything, we must be able to contact Tim. Other problems are that the web interface is unfinished, making it difficult to use. It is not possible to mark a records as completed. At the same time, retrieving the list is often not complete, so there is an increased effort required to obtain the latest records. Many records are generated without the presence of debug symbols, so their usefulness is reduced. -- What needs to be done -- We have to decide what to do next with this service. We will either need to obtain the source code and data of existing records so that we can migrate the service and then work on improving it. Or we could implement the server side of the service from scratch, based on the client side code in tdelibs. Or we can look for a similar service with a GPL license and the ability to install on our server. In any case, it will probably take a lot of effort here to make the service useful. -- More ideas and suggestions? Do you have any other ideas and suggestions? Do you know of any open source solutions that could serve our purpose? Cheers -- Slávek

6 15

Migration of services - 7. automation scripts
by Slávek Banko 11 Dec '20

11 Dec '20

Hi all, the seventh service on the migration list is automation scripts. -- Migration status -- Previously, on the former primary server, automation scripts provided updating of submodules in the master branch in the main 'tde' module, updating clones of repositories for the CGit interface, and generating data for the Commit history page and. Along with the launch of TGW, automation scripts were run on the VPS machine. These scripts now provide not only an update of the master branch, but of all main branches. The CGit interface no longer needs a separate update of the repositories because it displays the repositories directly from the TGW. Processing is now faster and takes place every hour. In case of changes in the common admin or cmake module, it may take longer to process all branches. -- What needs to be done -- In addition to processing submodules, a script for updating translations is run regularly here. This script updates the POT files and merges the translations from the master branch to the stable branch. Currently, this script is initialized manually, because when updating POT templates, TWTW automatically provides an update of PO files, which may take some undefined time. At the same time, it requires that packages be installed that would not otherwise be installed on a public server (such as Xserver screen savers). However, even for this script, it is intended that its execution can be automated. Another thing that will be useful to automate is the update of Summary issues in TGW. -- More ideas and suggestions? Do you have any other ideas and suggestions? Cheers -- Slávek

2 1

In a TDM theme's xml file, what does @@@TDEBACKGROUND@@@ point to?
by J Leslie Turriff 09 Dec '20

09 Dec '20

I'm trying to write a custom theme file for TDM, using os_enterprise theme as an example. It contains | <greeter> | <item type="pixmap" > | <normal file="@@@TDMBACKGROUND@@@" /> | : to define the login screen's background. I've looked through the various TDE handbooks and poked around on the wiki, but nothing mentions this symbol. (In fact, the only page in the wiki that I found that discusses the internals of theme files seems to be out of date, since it talks about Theme.rc files, whereas the control file in each /opt/trinity/share/apps/tdm/themes subdirectory is an xml file. When the os_enterprise theme is active its display looks like its preview.png, even if the background.png file is different; so what is @@@TDEBACKGROUND@@@ pointing to? Leslie

1 0

cannot run apt-get upgrade, mirror not found
by Uwe Brauer 09 Dec '20

09 Dec '20

Hi I am on Ubuntu 16.04. When running sudo apt-get upgrade I obtain The following packages will be upgraded: akregator-trinity amarok-common Etc all together some 66 packages Then saying yes WARNING: The following packages cannot be authenticated! Then even saying yes I obtain Err:11 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb xenial/main-r14 amd64 kate-trinity amd64 4:14.0.10~pre13-0ubuntu16.04.0+1 404 Not Found Can somebody please tell me what is wrong here? Thanks and regards Uwe Brauer --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting

3 3

Re: [tde-devels] [OT] Qt6
by BorgLabs - Kate Draven 08 Dec '20

08 Dec '20

> Not sure if someone is interested, thus OT, but I just read Qt6 was released > > https://www.qt.io/product/qt6 > > > ____________________________________________________ > tde-devels mailing list -- devels(a)trinitydesktop.org > To unsubscribe send an email to devels-leave(a)trinitydesktop.org > Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydesk… > Cool. Thanks Kate

1 0

hvac service nrea me
by saransh＠swasthyakart.com 08 Dec '20

08 Dec '20

https://www.trustedcaptain.com/hvac-repair-services-near-me.html If you don’t know how to get your hands on Cheap Air Conditioning Repair Near Me services then Don’t get tensed anymore just make a call on our 24*7 operational toll-free helpline number and we help you in getting dedicated HVAC Repair, installation & maintenance Services related to various heating brands and companies within no time. We have leading professionals on our platform who are available even in the odd hours to offer you the desired solutions. Our HVAC technicians have genuine experience in providing customer-oriented Heating And Air Conditioning services for commercial & residential places.

1 0

Suggestion to improve TDE/Ubuntu image
by Edward 08 Dec '20

08 Dec '20

Since installing the TDE/Ubuntu 20.04.1 image (in a VirtualBox), it had not displayed the GRUB boot menu, it displays a couple of lines (as if it were a terminal window), then goes straight to the Ubuntu splash screen. The beginning of the original /etc/default/grub file was: GRUB_DEFAULT="0" GRUB_TIMEOUT_STYLE="hidden" GRUB_TIMEOUT="0" GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`" GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX="" I manually made the following changes: * removed: GRUB_TIMEOUT_STYLE="hidden" * made: GRUB_TIMEOUT="5" then ran update-grub and rebooted. The GRUB menu now appears. I would like to offer a friendly suggestion that for future TDE/Ubuntu images, if this is possible to do, the default grub file not contain GRUB_TIMEOUT_STYLE="hidden" and the GRUB_TIMEOUT entry be set to at least 3. Please note that I do not know if the original default items copied above, is the actual standard for all Ubuntu images. Ubuntu offers a package grub-customizer. When I looked at that, the General settings indicated the GRUB menu was set to display, but it seems that the GRUB_TIMEOUT_STYLE="hidden" entry overrides that and was preventing it from displaying. After saving the settings in grub-customizer, GRUB_TIMEOUT_STYLE="hidden" was still in /etc/default/grub.

2 2

Upgrading Trinity with Debian
by Edward 07 Dec '20

07 Dec '20

Debian released version 10.7 yesterday and I decided to install Debian on my other desktop directly, as I saw no need for two of the same distro to be installed, as I'm not really testing anything. Debian required a non-free firmware package for it to recognize the AMD Radeon video and once that was installed and system rebooted, the graphical desktop came up fine and I was then able to install Trinity. When Debian 11 (bullseye) is officially released next year, is it best to wait and upgrade everything (Debian and Trinity packages) at the same time? I do not know if it is safe to upgrade just Debian to bullseye, if the Trinity packages for bullseye were not yet available at the same time. I am aware that Debian 10 is being supported for five years from the date it was initially released. Thanks in advance. -- This message was sent using virtual technology.

3 3

Migration of services - 6. Weblate
by Slávek Banko 07 Dec '20

07 Dec '20

Hi all, to move forward on the list of service migrations, we have the sixth item here - Weblate. -- Migration status -- TDE Weblate Translation Workspace (TWTW) is a new service that was set up on VPS. It is fully functional and therefore there is currently no need to address its migration. -- What needs to be done -- The second stage of TWTW integration is currently underway. This is adding translations for desktop style files. Only modules that are built with CMake are added, because merging translations into desktop files is not done by some external magic script, but by intltool-merge during build. We then envisage a third level of integration, for the translation of documentation and manual pages. However, it will first require preparing CMake macros to handle the documentation and to merge translations of the documentation and manual pages during build. If this proves to be useful, we can consider a TDE skin for TWTW. However, this is a matter that currently has no priority. -- More ideas and suggestions? Does everything work fine with the TWTW? Do you have any other ideas and suggestions? Cheers -- Slávek

1 0

Migration of services - 5. bugzilla
by Slávek Banko 07 Dec '20

07 Dec '20

Hi all, the fifth service on the migration list is Bugzilla. For the Bugzilla, the situation is significantly different, because we need to discuss here before any steps are taken. -- Migration status -- Bugzilla is on Tim's original infrastructure. Therefore, no one else can manage the current instance. And there are various issues that we are currently unable to resolve, such as problem with login when https is used. So it definitely needs some change. -- What needs to be done -- First of all, we need to discuss and decide whether we want to continue using Bugzilla. As mentioned earlier, TGW is now used as a comprehensive workspace. And TGW contains Issues that can be used instead of bug reports in a separate Bugzilla. There are several benefits to using Issues. Above all, Issues are well integrated into the development workflow. It also provides good comfort - for example, it is possible to use comment formatting to make it more readable and clear. At the same time, it seems like a good idea to use one problem reporting tool rather than two independent ones. If we find a consensus that there is no significant reason to use Bugzilla, we need to decide how to deal with existing bug reports. There are two options: 1) Migrate Bugzilla to a new instance, which will be locked for adding new bug reports. This can be done more easily. However, the problem remains that there will continue to be two places for users to look for problem reports. 2) Migrate bug reports from Bugzilla into Issues in TGW and then stop Bugzilla completely. Although it is likely to be more difficult to do, I think it would be a better solution. -- More ideas and suggestions? What is your opinion on Bugzilla migration? Do you have any other ideas and suggestions? Cheers -- Slávek

5 10

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

tde-users