tde-devels

devels@trinitydesktop.org

9 participants
3817 discussions

Trinity Repository problems
by Keith Daniels 22 Oct '12

22 Oct '12

Following the instructions for "For Precise [Ubuntu 12.04] LTS (v3.5.13.1)" from: http://www.trinitydesktop.org/wiki/bin/view/Documentation/UbuntuBinaryInsta…. I got these "Failed to fetch" messages with "apt-get update": ----------- From: http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/ubuntu/d… source/Sources binary-amd64/Packages binary-i386/Packages Error: 404 Not Found From: http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-v3.5.1… /source/Sources /binary-amd64/Packages /binary-i386/Packages Error: 404 Not Found ---------- I assume this is why I got so many "unmet dependencies" when I tried "apt-get install" Is there something wrong with the repository or is it something on my end...? ALSO: I am trying to install Trinity on Lubuntu 12.04. Lubuntu was a fresh install on a blank drive and has not been modified since the install. Will using Lubuntu instead of Ubuntu, be a problem? Keith

2 3

GIT builds for other distros
by Darrell Anderson 22 Oct '12

22 Oct '12

We provide no way for regular users to help us test the development branch. Do we have a mechanism in place to upload daily/nightly/weekly builds from GIT? If not then what needs to be done to provide that access? What about the GIT repo itself? For example, I notice the following directory: http://git.trinitydesktop.org/cgit/tde-packaging/tree/slackware Although intended for hosting build scripts and packaging information, why not a single set of binary packages too? The packages would not be mirrored. Darrell

2 3

Re: [trinity-devel] A few duplicate locolor icons
by Slávek Banko 22 Oct '12

22 Oct '12

Dne Monday 22 of October 2012 21:41:45 jste napsal(a): > On Monday 22 of October 2012 21:36:31 Francois Andriot wrote: > > >> I show the following in my package sets: > > >> > > >> kbabel.png: > > >> tdeartwork, tdesdk > > >> > > >> ktimemon.png: > > >> tdeartwork, tdeaddons > > >> > > >> Darrell > > > > > > Yes, we have the same files - Debian binary packages are more > > > granulary. I will update the installation, to be installed in only one > > > of these packages. The question is, from which package? > > > > > > a) All from tdearwork > > > b) From tdeaddons and tdesdk > > > c) None of the above => another interesting idea :) > > > > > > Slavek > > > > I think the locolor icons should go with the package that provides the > > "index" for the locolor theme. > > Without the index installed, the icons are useless. > > I believe the package providing locolor index is tdeartwork. > > > > Francois > > François, absolutely perfect note! > The decision was made :) > > Thank you. > > Slavek It's a little complicated. Icons are installed in the standard way (automake as well as cmake) == automatically installs all variants of the icon that are available. It appears that there are three possible solutions: 1) Remove locolor icon. 2) Rename icon or move to a subfolder. 3) Skip icon during packaging in individual distributions. Any other ideas? Which solution seems preferable? Slavek --

2 4

RPM packages for 3.5.13.1
by Darrell Anderson 22 Oct '12

22 Oct '12

Some favorable comments here about Trinity: http://lxer.com/module/forums/t/33920/ Folks are looking for 3.5.13.1 RPM packages but the Trinity web site has no links. I recall reading Francois had made RPM packages for several distros. Where are the links on the web page? Darrell

5 11

A few duplicate locolor icons
by Slávek Banko 22 Oct '12

22 Oct '12

Hi all, With commit e5a2da23 showed few duplicate locolor icons: tdeartwork-theme-icon-trinity: opt/trinity/share/icons/Locolor/16x16/apps/kbabel.png opt/trinity/share/icons/Locolor/16x16/apps/ktimemon.png opt/trinity/share/icons/Locolor/32x32/apps/kbabel.png opt/trinity/share/icons/Locolor/32x32/apps/ktimemon.png kicker-applets-trinity: opt/trinity/share/icons/locolor/32x32/apps/ktimemon.png opt/trinity/share/icons/locolor/16x16/apps/ktimemon.png kbabel-trinity: opt/trinity/share/icons/locolor/32x32/apps/kbabel.png opt/trinity/share/icons/locolor/16x16/apps/kbabel.png I have a very simple question is: From which package exclude their installation? I'd recommend installing with the tdeartwork and exclude from tdeaddons and tdesdk. What is your opinion? Slavek --

3 6

To hide or not to hide (symbols)
by Darrell Anderson 22 Oct '12

22 Oct '12

Been a long time since we discussed gcc hidden visibility for symbols. Last I remember, this was supported in (T)Qt3, arts, tdelibs, and tdebase. I tried building my normal package suite with this option enabled in every package. Some packages built but ignored the configure option. Some failed to build. Some built and there were no messages at all about the option. Removing the option from the failure group allowed the packages to build. For the latter group, as no errors or build failures occurred, I presume the option is supported. Still, is this a good idea? I read a bit about the topic and the information is way over my head. The only thing I do understand is using the option is supposed to reduce libary size and improve loading speeds. Darrell

2 7

Q_ENUMS->TQ_ENUMS
by Darrell Anderson 22 Oct '12

22 Oct '12

Tim, I pushed patches for koffice and kmymoney to update Q_ENUMS->TQ_ENUMS. They both failed to build last night during my build run. Both now build. Darrell

1 0

Tim: Commit f209ff4b, et. al. breaks tdebindings
by Darrell Anderson 20 Oct '12

20 Oct '12

I built my normal package set on Oct. 15. Today I can't. My local tree is current. The failure messages with tdebindings: x_16.cpp:5632: error: ISO C++ forbids initialization in array new x_16.cpp:5632: error: no matching function for call to 'TQStyleControlElementGenericWidgetData::TQStyleControlElementGenericWidgetData(TQStyleControlElementGenericWidgetData [4])' x_16.cpp:5656: error: expected primary-expression before '[' token x_16.cpp:5656: error: expected primary-expression before ')' token x_16.cpp:5656: error: expected ';' before 'x' Looking at the commits since Oct. 15 I see f209ff4b, which has code that matches the failure messages. x_16.cpp, which is generated during the build, has #include <ntqstyle.h>. After rebuilding tqt3, /opt/trinity/include/ntqstyle.h includes class TQStyleControlElementGenericWidgetData. How do we fix? Darrell

2 2

kate/kwrite stalls a long time opening any *.kcrash file
by Darrell Anderson 20 Oct '12

20 Oct '12

Latest R14. Would somebody please confirm this behavior? Run crashtest. Save the backtrace. Open the file with kate or kwrite. Open directly from within or through konqueror. On my dual core system with SATA II drives, opening a *.kcrash file takes more than a minute to open, creating the impression the app has stalled or locked. Thanks. Darrell

3 4

Quick 3.5.13.1 test please
by Darrell Anderson 20 Oct '12

20 Oct '12

Would somebody running 3.5.13.1 please test opening kopete? Thank you! Darrell

3 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels