tde-devels

devels@trinitydesktop.org

2 participants
3755 discussions

Re: [trinity-devel] Icon conflicts in tdeaddons-tdeartwork-tdesdk (which one to choose?)

by Darrell Anderson

> We have run into another icon conflict error. I know some Who is we, kemosabi? >package managers do >not care and will let you overwrite icons, fonts, etc.., but >Arch's pacman >package manager will not let you overwrite anything in the >filesystem on the >theory that "No package should conflict with another". Of course >you can --force >any install and removal, but that defeats the purpose of proper >packaging. That is what happens in an anal world. > There are a couple of TDE icons that are present in several >different >packages. If one package is installed before any other containing >the same >icons, then install of the subsequent packages fails. At issue >are: > >tde-tdeaddons-14.0.0-1-i686.pkg.tar.xz > >opt/trinity/share/icons/locolor/32x32/apps/ktimemon.png >opt/trinity/share/icons/locolor/16x16/apps/ktimemon.png > >tde-tdeartwork-14.0.0-1-i686.pkg.tar.xz > >opt/trinity/share/icons/locolor/32x32/apps/ktimemon.png >opt/trinity/share/icons/locolor/32x32/apps/kbabel.png >opt/trinity/share/icons/locolor/16x16/apps/ktimemon.png >opt/trinity/share/icons/locolor/16x16/apps/kbabel.png > >tde-tdesdk-14.0.0-1-i686.pkg.tar.xz > >opt/trinity/share/icons/locolor/32x32/apps/kbabel.png >opt/trinity/share/icons/locolor/16x16/apps/kbabel.png > > So this has to be handled from a packaging standpoint on arch. >Fortunately, >the package that contains all icons at issue is tdeartwork. For >Arch, I will >write conditional checks for tdeaddons and tdesdk to avoid the >issue. > > How are the other distros handling this? Can TDE move these >conflicting icons >to tdeartwork exclusively. tdeaddons is from where the ktimemon applet is installed and is the rightful place for related base icons. tdesdk is from where kbabel is installed and is the rightful place for related base icons. Seems the tdeartwork versions should be deleted. That said, the tdeartwork versions for kbabel seem more global. The tdesdk icons are US-centric. As far as I can tell the ktimemon images are duplicates, both in appearance and in file size. Darrell

11 years

Icon conflicts in tdeaddons-tdeartwork-tdesdk (which one to choose?)

by David C. Rankin

Darrell, We have run into another icon conflict error. I know some package managers do not care and will let you overwrite icons, fonts, etc.., but Arch's pacman package manager will not let you overwrite anything in the filesystem on the theory that "No package should conflict with another". Of course you can --force any install and removal, but that defeats the purpose of proper packaging. There are a couple of TDE icons that are present in several different packages. If one package is installed before any other containing the same icons, then install of the subsequent packages fails. At issue are: tde-tdeaddons-14.0.0-1-i686.pkg.tar.xz opt/trinity/share/icons/locolor/32x32/apps/ktimemon.png opt/trinity/share/icons/locolor/16x16/apps/ktimemon.png tde-tdeartwork-14.0.0-1-i686.pkg.tar.xz opt/trinity/share/icons/locolor/32x32/apps/ktimemon.png opt/trinity/share/icons/locolor/32x32/apps/kbabel.png opt/trinity/share/icons/locolor/16x16/apps/ktimemon.png opt/trinity/share/icons/locolor/16x16/apps/kbabel.png tde-tdesdk-14.0.0-1-i686.pkg.tar.xz opt/trinity/share/icons/locolor/32x32/apps/kbabel.png opt/trinity/share/icons/locolor/16x16/apps/kbabel.png So this has to be handled from a packaging standpoint on arch. Fortunately, the package that contains all icons at issue is tdeartwork. For Arch, I will write conditional checks for tdeaddons and tdesdk to avoid the issue. How are the other distros handling this? Can TDE move these conflicting icons to tdeartwork exclusively. -- David C. Rankin, J.D.,P.E.

11 years

tde parallel build issue with tqt3? tdeartwork, amarok, k9copy all failing with strange error

by David C. Rankin

Tim, Darrell, All, Last night I started an i686 build run. During that run, several packages failed that had just built without issue on x86_64. At first it just looked like a cmake/library issue, but comparing the build failures, there is some common thread running between them that I cannot put my finger on. I need help to determine what the issue is. Most errors I can poke around at enough to figure out, but this one looks strange enough, I would like a second pair of eyes on it. Specifically, it looks to me like any time a link is called involving something openGL related, the build fails with a sting of "undefined reference to `TQGLWidget::" messages. Examples: tdeartwork: <snip> CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::staticMetaObject()': Euphoria.cpp:(.text+0x389): undefined reference to `TQGLWidget::staticMetaObject()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::~EuphoriaWidget()': Euphoria.cpp:(.text+0xd45): undefined reference to `TQGLWidget::~TQGLWidget()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::EuphoriaWidget(TQWidget*, char const*)': Euphoria.cpp:(.text+0x2b5e): undefined reference to `TQGLWidget::TQGLWidget(TQWidget*, char const*, TQGLWidget const*, unsigned int)' <snip> amarok: <snip> analyzers/libanalyzers.a(analyzerbase.cpp.o): In function `Analyzer::Base3D::tqt_emit(int, TQUObject*)': analyzerbase.cpp:(.text+0x1e7): undefined reference to `TQGLWidget::tqt_emit(int, TQUObject*)' analyzers/libanalyzers.a(analyzerbase.cpp.o): In function `Analyzer::Base3D::tqt_property(int, int, TQVariant*)': analyzerbase.cpp:(.text+0x21f): undefined reference to `TQGLWidget::tqt_property(int, int, TQVariant*)' analyzers/libanalyzers.a(analyzerbase.cpp.o): In function `Analyzer::Base3D::staticMetaObject()': analyzerbase.cpp:(.text+0x391): undefined reference to `TQGLWidget::staticMetaObject()' <snip> Not having any logical explanation for the failures and there being no explicit library missing, I went back and rebuilt everything again. from tqt3 to kdebase. Now recall, the build last night proceeded without error from tqt3 to kdebase, so I should simply be rebuilding the exact same code as was done in: makepkg --> SUCCEEDED for tqt3 at Jan 27 20:11:18 makepkg --> SUCCEEDED for tqtinterface at Jan 27 20:13:07 makepkg --> SUCCEEDED for arts at Jan 27 20:16:27 makepkg --> SUCCEEDED for dbus-tqt at Jan 27 20:16:34 makepkg --> SUCCEEDED for dbus-1-tqt at Jan 27 20:16:56 makepkg --> SUCCEEDED for tqca-tls at Jan 27 20:17:02 makepkg --> SUCCEEDED for libart-lgpl at Jan 27 20:17:21 makepkg --> SUCCEEDED for avahi-tqt at Jan 27 20:17:44 makepkg --> SUCCEEDED for libcaldav at Jan 27 20:18:07 makepkg --> SUCCEEDED for libcarddav at Jan 27 20:18:22 makepkg --> SUCCEEDED for sip4-tqt at Jan 27 20:19:09 makepkg --> SUCCEEDED for python-tqt at Jan 27 20:26:48 makepkg --> SUCCEEDED for tdelibs at Jan 27 20:51:11 makepkg --> SUCCEEDED for tdebase at Jan 27 21:16:07 <snip> makepkg --> FAILED for tdeartwork at Jan 27 22:05:12 After rebuilding the same packages again, (tqt3-tdebase) I can build tdeartwork without issue: makepkg --> SUCCEEDED for tdeartwork at Jan 28 15:16:25 Anybody else see this type of behavior? I rebuilt using parallel building again, so if it was to blame to begin with, it looks like this is some of the spurious type of errors that can occur. -- David C. Rankin, J.D.,P.E.

11 years

tdebinding (libsmoketqt) conflicts with libtqt-perl (libsmoketqt) - which is correct?

by David C. Rankin

Can someone confirm which package is supposed to provide libsmoke. Currently I have libtqt-perl providing: opt/trinity/bin/puic opt/trinity/lib/libsmoketqt.so opt/trinity/lib/libsmoketqt.la opt/trinity/lib/libsmoketqt.so.1.2.1 opt/trinity/lib/libsmoketqt.so.1 tdebindings (which finally built!) also provides: opt/trinity/lib/libsmoketqt.so opt/trinity/lib/libsmoketqt.la opt/trinity/lib/libsmoketde.so.1 opt/trinity/lib/libsmoketde.so Which package should provide libsmoketqt? -- David C. Rankin, J.D.,P.E.

11 years

Arch - Building TDE i686 on x86_64 hardware

by David C. Rankin

All, A note to all who may try building TDE on arch. You can build/package both x86_64 and i686 packages on your x86_64 box -- simply. To build i686 packages on x86_64, create a 2nd archroot using a custom makepkg.conf and pacman.conf. To create the custom conf files, the only changes necessary are change '$auto' or auto, and x86_64 and x86-64 to 'i686' as follows: echo " Creating i686 pacman.conf" cp /etc/pacman.conf "$tmp" sed -i 's/Architecture = auto/Architecture = i686/' "$tmp/pacman.conf" echo " Creating new i686 archroot in '$CHROOT'" cp /etc/makepkg.conf "$tmp" sed -i 's/x86.64/i686/g' "$tmp/makepkg.conf" echo " Creating new i686 archroot in '$CHROOT'" sudo mkarchroot \ -C "$tmp/pacman.conf" \ -M "$tmp/makepkg.conf" \ $CHROOT/root base base-devel sudo gdb Build your first package by switching to the directory with the PKGBUILD for the first dependency and build/clean with: sudo makechrootpkg -c -r $CHROOT Then create a [local] repository to hold all packages with 0777 permissions and update your $CHROOT/root/etc/pacman.conf with the [local] repo definition sudo mkdir -p $CHROOT/root/repo || echo -e " WARNING: unable to create \$CHROOT/root/repo\n You must manually setup local repository.\n" echo " Setting permissions for '$CHROOT/root/repo'" [[ -d $CHROOT/root/repo ]] && sudo chmod 0777 $CHROOT/root/repo echo " Adding local repository to root/pacman.conf" echo -e "\n[local]\nSigLevel = Never\nServer = file:///repo\n" > /tmp/repotmp.txt sudo bash -c "cat /tmp/repotmp.txt >> $CHROOT/root/etc/pacman.conf" rm /tmp/repotmp.txt The copy the first package to $CHROOT/root/etc/pacman.conf and create the [local] repository index with: sudo repo-add $CHROOT/root/repo/local.db.tar.gz $CHROOT/root/repo/*.xz Then simply build all remaining dependencies and TDE in the order specified, install each complete package to the rw-layer of the chroot when built, and copy each completed package to $CHROOT/root/repo updating the local repository index as shown above after building/installing each package Build all remaining packages with: sudo makechrootpkg -r $CHROOT -- David C. Rankin, J.D.,P.E.

11 years

KControl joystick module screen captures needed

by Darrell Anderson

All, I have a joystick help handbook to push to git but no screen captures. I don't own a joystick! :) I need two screen captures: * tdecmshell joystick (3.5.13.2: kcmshell joystick) * The Calibrate dialog Preferred ksnapshot method: Capture mode: Window under cursor Thank you! Darrell

11 years

New tdertwork FTBFS - undefined reference to `TQGLWidget::glDraw() CMakeFiles/keuphoria.kss

by David C. Rankin

Darrell, It looks like tdeartwork will be the spoiler in my perfect end-to-end build. tdeartwork built fine on x86_64 a few days ago, and now fails -- any ideas on the error? Linking CXX executable keuphoria.kss cd /build/tde-tdeartwork/src/build/tdescreensaver/kdesavers && /usr/bin/cmake -E cmake_link_script CMakeFiles/keuphoria.kss.dir/link.txt --verbose=1 /usr/bin/c++ -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -I/opt/tqt3/include -I/usr/include/tqt -DQT_NO_ASCII_CAST -DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -Wl,-O1,--sort-common,--as-needed,-z,relro CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o -o keuphoria.kss -L/opt/tqt3/lib -L/opt/trinity/lib -rdynamic /opt/trinity/lib/libtdescreensaver.so.14.0.0 /opt/trinity/lib/libtdeui.so.14.0.0 -lGLU -lGL -lSM -lICE -lX11 -lXext /opt/trinity/lib/libtdecore.so.14.0.0 /opt/trinity/lib/libDCOP.so.14.0.0 /opt/trinity/lib/libtdefx.so.14.0.0 -ltqt -ltqt-mt -lXrender -lX11 -lc -lz -lidn -lXcomposite -lICE -lSM -lfreetype -lfontconfig -Wl,-rpath,/opt/tqt3/lib:/opt/trinity/lib: CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::staticMetaObject()': Euphoria.cpp:(.text+0x389): undefined reference to `TQGLWidget::staticMetaObject()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::~EuphoriaWidget()': Euphoria.cpp:(.text+0xd45): undefined reference to `TQGLWidget::~TQGLWidget()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::EuphoriaWidget(TQWidget*, char const*)': Euphoria.cpp:(.text+0x2b5e): undefined reference to `TQGLWidget::TQGLWidget(TQWidget*, char const*, TQGLWidget const*, unsigned int)' Euphoria.cpp:(.text+0x2c0c): undefined reference to `TQGLWidget::~TQGLWidget()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::~EuphoriaWidget()': Euphoria.cpp:(.text+0xcf8): undefined reference to `TQGLWidget::~TQGLWidget()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::tqt_cast(char const*)': Euphoria.cpp:(.text+0x32cb): undefined reference to `TQGLWidget::tqt_cast(char const*)' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::tqt_invoke(int, TQUObject*)': Euphoria.cpp:(.text+0x331f): undefined reference to `TQGLWidget::tqt_invoke(int, TQUObject*)' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::tqt_emit(int, TQUObject*)': Euphoria.cpp:(.text+0x3341): undefined reference to `TQGLWidget::tqt_emit(int, TQUObject*)' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o: In function `EuphoriaWidget::tqt_property(int, int, TQVariant*)': Euphoria.cpp:(.text+0x3351): undefined reference to `TQGLWidget::tqt_property(int, int, TQVariant*)' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTI14EuphoriaWidget[_ZTI14EuphoriaWidget]+0x8): undefined reference to `typeinfo for TQGLWidget' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0xac): undefined reference to `TQGLWidget::setMouseTracking(bool)' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x108): undefined reference to `TQGLWidget::reparent(TQWidget*, unsigned int, TQPoint const&, bool)' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x148): undefined reference to `TQGLWidget::paintEvent(TQPaintEvent*)' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x150): undefined reference to `TQGLWidget::resizeEvent(TQResizeEvent*)' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x1c4): undefined reference to `TQGLWidget::makeCurrent()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x1c8): undefined reference to `TQGLWidget::swapBuffers()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x1cc): undefined reference to `TQGLWidget::setFormat(TQGLFormat const&)' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x1d0): undefined reference to `TQGLWidget::setContext(TQGLContext*, TQGLContext const*, bool)' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x1d4): undefined reference to `TQGLWidget::renderPixmap(int, int, bool)' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x1d8): undefined reference to `TQGLWidget::grabFrameBuffer(bool)' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x1dc): undefined reference to `TQGLWidget::makeOverlayCurrent()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x1e0): undefined reference to `TQGLWidget::updateGL()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x1e4): undefined reference to `TQGLWidget::updateOverlayGL()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x1f4): undefined reference to `TQGLWidget::initializeOverlayGL()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x1f8): undefined reference to `TQGLWidget::resizeOverlayGL(int, int)' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x1fc): undefined reference to `TQGLWidget::paintOverlayGL()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x200): undefined reference to `TQGLWidget::glInit()' CMakeFiles/keuphoria.kss.dir/Euphoria.cpp.o:(.rodata._ZTV14EuphoriaWidget[_ZTV14EuphoriaWidget]+0x204): undefined reference to `TQGLWidget::glDraw()' collect2: error: ld returned 1 exit status tdescreensaver/kdesavers/CMakeFiles/keuphoria.kss.dir/build.make:109: recipe for target 'tdescreensaver/kdesavers/keuphoria.kss' failed make[2]: *** [tdescreensaver/kdesavers/keuphoria.kss] Error 1 make[2]: Leaving directory '/build/tde-tdeartwork/src/build' CMakeFiles/Makefile2:540: recipe for target 'tdescreensaver/kdesavers/CMakeFiles/keuphoria.kss.dir/all' failed make[1]: *** [tdescreensaver/kdesavers/CMakeFiles/keuphoria.kss.dir/all] Error 2 make[1]: Leaving directory '/build/tde-tdeartwork/src/build' Makefile:119: recip -- David C. Rankin, J.D.,P.E.

11 years

Does artsd need a daemon service file for systemd - if so, anybody have one?

by David C. Rankin

Darrell, Tim, Do you have artsd.service files for arts in any of your distros? We will probably need one to manage the daemon under systemd. -- David C. Rankin, J.D.,P.E.

11 years

Re: [trinity-devel] Initial draft of ktorrent help handbook

by Darrell Anderson

> Maybe I'm missing something, but the default on ksnapshot should >be >whole-desktop by default, then you can select individual window or >region. The >reason being that individual window captures accept a 'delay' >input set by the >user on the dialog and 'region' requires a user box-outline. That >is not >accessible when launched by default. > > That was the entire purpose of setting > >[PrtScr]='ksnapshot' >Shift-[PrtScr]='ksnapshot --current' > > Default behavior captures a snapshot of the screen, the >alternate use captures >the current window. What you are proposing is making 'ksnapshot -- >current' the >default behavior. At least for me, that somewhat defeats the >purpose of the >--current option for the alternate call. Perhaps you are confusing a basic keyboard shortcut to capture the desktop to the clipboard versus actually launching Ksnapshot and manually changing the desired capture option. :) I often take screen captures of windows rather than the entire desktop. Regarding the preferred style for screen captures, I need to write those guidelines soon. We want all images in all handbooks to have the same consistent look. Yes, capturing images will require setting up a separate user account, theme, or a VM to ensure that consistency. > On ktorrent - it has always failed. The autofoo files are messed >up and I'm no >autofoo wizard. I think it will probably be an easy fix for a >makefile/automake guru... Refer to bug report 1465. I have to use the enable-closure configuration option. As i shared in the bug report, something changed after April 15 because I never had to use that option before I filed the bug report. I still can't build ktorrent without that option. I can't build with the additional handbook files with or without that option. Darrell

11 years

Initial draft of ktorrent help handbook

by Darrell Anderson

Ktorrent never has had a help handbook. In nug report 1880 is a patch to add a ktorrent help handbook. The original file is a version 0.13 draft from KDE4. I've performed some basic tweaks to adapt the docbooks to Trinity. Content editing is needed by a ktorrent subject matter expert. I am unable to build ktorrent when I use the patch. The build always fails with the following: Making all in doc make[2]: Entering directory `/dev/shm/ktorrent/doc' make[2]: *** No rule to make target `all'. Stop. I have searched the web to no avail. I am doing the same thing as I have done when adding handbooks to other packages but ktorrent is the only package that won't build. ==================================== After somebody resolves the build failure, all of the screen captures need to be adapted to Trinity rather than KDE4. Some of the screen captures do not apply and further editing of the images and respective text is needed. The preferred style guide rule for screen captures: look at the user guide for screen capture examples. When using ksnapshot, only capture the active window and not the entire desktop. Thank you. Darrell

11 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

tde-devels