I've been dual-booting Siduction (my favourite distro) and Mint debian, because I've tried endlessly, but Siduction doesn't recognise qtstalker with apt-get, although it installs and works perfectly in Mint. I've even downloaded the qtstalker.deb package, but dpkg -i can't find all the dependencies and neither can I.
Dual booting is tedious and I recently dumped Mint, so I'd appreciate any help installing qtstalker in Siduction, please.
Info:
System: Host: mainbox Kernel: 3.6-0.towo-siduction-amd64 x86_64 (64 bit)
Desktop: KDE 4.8.4 Distro: siduction 12.1.1 Desperado Reloaded - kde - (201206241901)
Machine: Mobo: Intel model: DG965WH version: AAD41692-304
Bios: Intel version: MQ96510J.86A.1618.2007.0117.1535 date: 01/17/2007
CPU: Dual core Intel Core2 CPU 6300 (-MCP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 ssse3 vmx)
Clock Speeds: 1: 1596.00 MHz 2: 1596.00 MHz
Graphics: Card: NVIDIA G73 [GeForce 7300 GT] X.Org: 1.12.4 driver: nvidia Resolution: 1920x1080@60.0hz
GLX Renderer: GeForce 7300 GT/PCIe/SSE2 GLX Version: 2.1.2 NVIDIA 304.51
Audio: Card-1: Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel Sound: ALSA ver: 1.0.25
Card-2: Creative Labs SB Live! EMU10k1 driver: snd_emu10k1
Network: Card-1: Intel 82566DC Gigabit Network Connection driver: e1000e
IF: eth0 state: down mac: 00:19:d1:29:e5:99
Card-2: Ralink RT2870/RT3070 Wireless Adapter driver: rt2800usb
IF: wlan0 state: up mac: 00:e0:4c:6c:bb:72
Drives: HDD Total Size: 1250.3GB (19.5% used) 1: id: /dev/sda model: ST3250620AS size: 250.1GB
2: id: /dev/sdb model: ST31000424CS size: 1000.2GB
Partition: ID: / size: 232G used: 17G (8%) fs: btrfs ID: /home size: 932G used: 211G (24%) fs: btrfs
ID: swap-1 size: 1.06GB used: 0.00GB (0%) fs: swap
Hello,
well, it is a little bit tricky but I've installed it on my siduction machine with success.
Please do the following:
apt-get install libjpeg62
Get the following packages from Debian stable:
http://ftp.de.debian.org/debian/pool/main/q/qt-x11-free/libqt3-mt_3.3.8b-7+b1_amd64.deb
http://ftp.de.debian.org/debian/pool/main/d/db4.6/libdb4.6_4.6.21-16_amd64.deb
http://ftp.de.debian.org/debian/pool/main/q/qtstalker/qtstalker_0.32-3.2_amd64.deb
If you work with a 32bit machine, replace the amd64 with i386.
Enter the Download Folder as root and do the following:
dpkg -i *.deb
If dpkg ends with a error because of missing dependencies, do an:
apt-get -f install
Perhaps a new dist-upgrade will remove qtstalker, in this case ask again.
Kind regards,
Holger
Thanks, Holger. Your solution was quick and easy. Qtstalker is now working well for me.
Your prompt help is very much appreciated and I can once again keep track of my modest nest-egg.
By the way, siduction is perfect for me.
Hello @paleoflatus,
nice to read that this works for you. I've made a dist-upgrade after installing qtstalker and apt hasn't removed it.
I think a better solution would be a build of qtstalker against packages in Debian sid, but building clean debian packages is not so quick and easy :-)
Perhaps a debian professional in our developement team could do this.
Appart from that, please avoid using packages from Ubuntu or annother Ubuntu based distro in such cases, this could destroy your installation.
Kind regards,
Holger
Why not use the tarball and compile it and run it from your home directory if you don't want to mess up your siduction install? It may also be a matter of installing several -dev packages as well in order to build it
Quote from: "DeepDayze"Why not use the tarball and compile it and run it from your home directory if you don't want to mess up your siduction install? It may also be a matter of installing several -dev packages as well in order to build it
Hello @DeepDayze,
your suggestion is annother possibility, but one question:
Why do I mess up my siduction install when I integrate three Debian stable packages without usind any force option and without any hold?
Kind regards,
Holger
Quote
Why do I mess up my siduction install when I integrate three Debian stable packages without usind any force option and without any hold?
Mixing stable and unstable packages is like playing russian roulette. It's a gamble, stable is old, farks with dependencies, libraries, etc.
It's kinda like installing a ubuntu .deb on a debian system. It might work, it might not, it might mess your system especially after a d-u
Hello piper,
I've learned in my experience with debian since woody, that mixing stable and unstable repos is dangerous.
That my suggestion, using three packages from Debian stable and avoiding holds, is dangerous for an installation of sid, is a new information for me.
But please keep in mind, that I've written:
QuoteI think a better solution would be a build of qtstalker against packages in Debian sid, but building clean debian packages is not so quick and easy.
I don't want to give help, which can destroy an installation of siduction.
Kind regards,
Holger
Mixing repos that have another repo inbetween them (in this case testing) is always a gamble and the success of such an undertaking depends on 2 things mostly:
- the interdependencies of the packages involved
- the ability of the user to see the hidden pitfalls therein
We as supporters tend to be very cautious with the recommendations we give, because we mostly do not know the skillset of the given user. So, for someone knowledgable enough it is no problem to override our precautions, succeed in his task or keep the pieces if he breaks it :)
greetz
devil
Hello,
okay, a summary:
1. I've given following suggestion, a manuel download of three packages of stable, I have not talking about adding any stable repo.
2. Then I've talked about installing that three packages per dpkg -i, I have not suggest any hold.
In this case no apt-get -f install was needed.
I cannot see any dangerous situation for a siduction installation in this case.
I try to give suggestions with care, and I think, also warnings should be given with care avoiding to unsettle users.
Kind regards,
Holger
Sorry holgerw, I didn't mean to step on your toes, mixing stable & unstable can have some bad effects for non-experienced users.
I will refrain from posting on these type of posts in the future.
Again my apologies