folks,
I just noticed I'm up to r14.0.1 [development] on one of my laptops; what is the best way to downgrade to r14.0.0?
F.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2014/12/28 06:19 PM, Felmon Davis wrote:
folks,
I just noticed I'm up to r14.0.1 [development] on one of my laptops;
what is the best way to downgrade to r14.0.0?
F.
It means you are using the packages from the development branch, I suspect Slavek's repository. One way is to switch to the official TDE R14.0.0 packages (you can find instruction on the wiki), or if you are not going to upgrade that system for a while, you can just stick with what you have. R14.0.1 (development) so far has a few fixes over R14.0.0 already commited, so they wouldn't harm your installation.
Cheers Michele
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2014/12/28 06:19 PM, Felmon Davis wrote:
It means you are using the packages from the development branch, I suspect Slavek's repository. One way is to switch to the official TDE R14.0.0 packages (you can find instruction on the wiki), or if you are not going to upgrade that system for a while, you can just stick with what you have. R14.0.1 (development) so far has a few fixes over R14.0.0 already commited, so they wouldn't harm your installation.
Cheers Michele
On Sun, 28 Dec 2014, Michele Calgaro wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2014/12/28 06:19 PM, Felmon Davis wrote:
It means you are using the packages from the development branch, I suspect Slavek's repository. One way is to switch to the official TDE R14.0.0 packages (you can find instruction on the wiki), or if you are not going to upgrade that system for a while, you can just stick with what you have. R14.0.1 (development) so far has a few fixes over R14.0.0 already commited, so they wouldn't harm your installation.
Cheers Michele
I think I'm asking the wrong question. to be sure, I don't know how I got into the Development branch but the real issue is I'm having trouble with several programs.
let me mention the issues; perhaps there's some general approach to them. I'm reluctant to spin off more threads though; I've taken up too much time as it is.
a) can't start evince except by exporting XAUTHORITY and running it as root. (and I hate the interface!)
b) cannot install okular without massive dependencies or backpedalling this or that systemd files or other bits of intestines.
c) can't install bluetooth utilities on the laptop that has it.
any general words of wisdom are welcome.
my sources.list follows:
------
deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-r14.0.0/debian jessie main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-r14.0.0/debian jessie main deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-r14.0.0... jessie main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-r14.0.0... jessie main
#deb http://ftp.uk.debian.org/debian wheezy main deb http://ftp.uk.debian.org/debian jessie main #deb http://ftp.uk.debian.org/debian sid main deb http://http.debian.net/debian/ jessie main contrib non-free deb http://www.deb-multimedia.org jessie main non-free
------
F.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Sun, 28 Dec 2014, Michele Calgaro wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2014/12/28 06:19 PM, Felmon Davis wrote:
It means you are using the packages from the development branch, I suspect Slavek's repository. One way is to switch to the official TDE R14.0.0 packages (you can find instruction on the wiki), or if you are not going to upgrade that system for a while, you can just stick with what you have. R14.0.1 (development) so far has a few fixes over R14.0.0 already commited, so they wouldn't harm your installation.
Cheers Michele
I think I'm asking the wrong question. to be sure, I don't know how I got into the Development branch but the real issue is I'm having trouble with several programs.
let me mention the issues; perhaps there's some general approach to them. I'm reluctant to spin off more threads though; I've taken up too much time as it is.
a) can't start evince except by exporting XAUTHORITY and running it as root. (and I hate the interface!)
That sounds like one of the GTK engines might be causing problems. When you run evince under TDE from a terminal what does it spew?
b) cannot install okular without massive dependencies or backpedalling this or that systemd files or other bits of intestines.
IIRC okular will have many dependencies due to being a KDE application; this is normal-ish?
c) can't install bluetooth utilities on the laptop that has it.
Terminal output would be helpful here too. :-)
Tim
On Sun, 28 Dec 2014, Timothy Pearson wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Sun, 28 Dec 2014, Michele Calgaro wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2014/12/28 06:19 PM, Felmon Davis wrote:
It means you are using the packages from the development branch, I suspect Slavek's repository. One way is to switch to the official TDE R14.0.0 packages (you can find instruction on the wiki), or if you are not going to upgrade that system for a while, you can just stick with what you have. R14.0.1 (development) so far has a few fixes over R14.0.0 already commited, so they wouldn't harm your installation.
Cheers Michele
I think I'm asking the wrong question. to be sure, I don't know how I got into the Development branch but the real issue is I'm having trouble with several programs.
let me mention the issues; perhaps there's some general approach to them. I'm reluctant to spin off more threads though; I've taken up too much time as it is.
a) can't start evince except by exporting XAUTHORITY and running it as root. (and I hate the interface!)
That sounds like one of the GTK engines might be causing problems. When you run evince under TDE from a terminal what does it spew?
my googling hasn't helped so far but here is the message; this error occurs frequently on google.
------ ** (evince:1399): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files Segmentation fault ------
b) cannot install okular without massive dependencies or backpedalling this or that systemd files or other bits of intestines.
IIRC okular will have many dependencies due to being a KDE application; this is normal-ish?
hope not! hmm.... it seems it may now install on one of the lappies! just gives a list of dependencies but no complaints; I'll proceed later. on the other I get:
------ Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies: okular : Depends: libokularcore5 (= 4:4.14.2-2) but it is not going to be installed Depends: kde-runtime (> 4:4.10) but it is not going to be installed Depends: libphonon4 (>= 4:4.6.0really4.3.80) but it is not going to be installed Depends: phonon but it is not going to be installed E: Unable to correct problems, you have held broken packages. ------
I run "dpkg --get-selections | grep hold" and see nothing.
c) can't install bluetooth utilities on the laptop that has it.
Terminal output would be helpful here too. :-)
for instance attempting "apt-get install bluedevil" yields:
------ The following packages have unmet dependencies: bluedevil : Depends: kde-runtime (> 4:4.10) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ------
weird how kde-runtime is involved. attempting to install it yields another bouquet of "depends ... not going to be installed; you have held broken packages" messages.
F.
On Sun, 28 Dec 2014 14:49:02 -0500 (EST) Felmon Davis davisf@union.edu wrote:
On Sun, 28 Dec 2014, Timothy Pearson wrote:
On Sun, 28 Dec 2014, Michele Calgaro wrote:
On 2014/12/28 06:19 PM, Felmon Davis wrote:
c) can't install bluetooth utilities on the laptop that has it.
Terminal output would be helpful here too. :-)
for instance attempting "apt-get install bluedevil" yields:
The following packages have unmet dependencies: bluedevil : Depends: kde-runtime (> 4:4.10) but it is not going to be installed E: Unable to correct problems, you have held broken packages.
weird how kde-runtime is involved. attempting to install it yields another bouquet of "depends ... not going to be installed; you have held broken packages" messages.
bluedevil is a KDE project, so it's unsurprising it wants a bunch of KDE4 stuff installed. There are a couple of alternatives, though.
blueman is a GTK+-based GUI bluetooth manager. It seems to be the only widely available one not tied to a desktop environment. If your distro offers it, this is probably the easiest choice.
You also have the option of using bluetoothctl (or simple-agent) to pair devices from the command line. These tools are part of bluez, the package that bluedevil and blueman provide a front-end for. Warning: this is Not Pretty. The Gentoo wiki has a mostly distro-agnostic list of commands at http://wiki.gentoo.org/wiki/Bluetooth#Device_pairing .
E. Liddell
On Sun, 28 Dec 2014, E. Liddell wrote:
On Sun, 28 Dec 2014 14:49:02 -0500 (EST) Felmon Davis davisf@union.edu wrote:
On Sun, 28 Dec 2014, Timothy Pearson wrote:
On Sun, 28 Dec 2014, Michele Calgaro wrote:
On 2014/12/28 06:19 PM, Felmon Davis wrote:
c) can't install bluetooth utilities on the laptop that has it.
Terminal output would be helpful here too. :-)
for instance attempting "apt-get install bluedevil" yields:
The following packages have unmet dependencies: bluedevil : Depends: kde-runtime (> 4:4.10) but it is not going to be installed E: Unable to correct problems, you have held broken packages.
weird how kde-runtime is involved. attempting to install it yields another bouquet of "depends ... not going to be installed; you have held broken packages" messages.
bluedevil is a KDE project, so it's unsurprising it wants a bunch of KDE4 stuff installed. There are a couple of alternatives, though.
someone else made a comment like this "X is a kde app so not surprising the number of dependencies" which I find perplexing since this is KDE(3) land after all.
anyway, I had to do some futzing around, basically accepting a number of 'downgrades', for example:
----- Downgrade the following packages: 2) libpulse0 [1:5.0-13+nosystemd1 (now) -> 5.0-13 (testing)] -----
and for another example:
----- Downgrade the following packages: 8) dbus [1:1.8.8-2+nosystemd1 (now) -> 1.8.12-1 (testing)] 9) dbus-x11 [1:1.8.8-2+nosystemd1 (now) -> 1.8.12-1 (testing)] 10) libdbus-1-3 [1:1.8.8-2+nosystemd1 (now) -> 1.8.12-1 (testing)]
------
and now I have okular and yes, blueman (haven't tested a connection yet though) running on one of the laptops.
okular throws tons of stuff on the terminal but starts up. don't yet know if it is all stable.
evince remains evasive (only runs as root after exporting XAUTHORITY) so got to figure that out.
blueman is a GTK+-based GUI bluetooth manager. It seems to be the only widely available one not tied to a desktop environment. If your distro offers it, this is probably the easiest choice.
You also have the option of using bluetoothctl (or simple-agent)
couldn't find either of these in my apt-cache. bluez and friends are installed.
to pair devices from the command line. These tools are part of bluez, the package that bluedevil and blueman provide a front-end for. Warning: this is Not Pretty.
that's ok. they (bluez, et al.) were running fine before the upgrade.
F.
The Gentoo wiki has a mostly distro-agnostic list of commands at http://wiki.gentoo.org/wiki/Bluetooth#Device_pairing .
E. Liddell
On Sunday 28 December 2014 7:55:35 pm you wrote:
On Sun, 28 Dec 2014, E. Liddell wrote:
On Sun, 28 Dec 2014 14:49:02 -0500 (EST)
Felmon Davis davisf@union.edu wrote:
On Sun, 28 Dec 2014, Timothy Pearson wrote:
On Sun, 28 Dec 2014, Michele Calgaro wrote:
On 2014/12/28 06:19 PM, Felmon Davis wrote:
c) can't install bluetooth utilities on the laptop that has it.
Terminal output would be helpful here too. :-)
for instance attempting "apt-get install bluedevil" yields:
The following packages have unmet dependencies: bluedevil : Depends: kde-runtime (> 4:4.10) but it is not going to be installed E: Unable to correct problems, you have held broken packages.
weird how kde-runtime is involved. attempting to install it yields another bouquet of "depends ... not going to be installed; you have held broken packages" messages.
bluedevil is a KDE project, so it's unsurprising it wants a bunch of KDE4 stuff installed. There are a couple of alternatives, though.
someone else made a comment like this "X is a kde app so not surprising the number of dependencies" which I find perplexing since this is KDE(3) land after all.
anyway, I had to do some futzing around, basically accepting a number of 'downgrades', for example:
The reference to KDE is that most distro package repositories will have the latest version of KDE4, the Trinity desktop is TDE, package names ending in '-trinity'
On Monday 29 December 2014 04:55:35 Felmon Davis wrote:
someone else made a comment like this "X is a kde app so not surprising the number of dependencies" which I find perplexing since this is KDE(3) land after all.
No, it isn't. It's *T*DE land. Sadly KDE3 is dead and KDE4 rules. But surely X is not a KDE application, so should not have KDE dependancies.
Lisi
On Mon, 29 Dec 2014, Lisi Reisz wrote:
On Monday 29 December 2014 04:55:35 Felmon Davis wrote:
someone else made a comment like this "X is a kde app so not surprising the number of dependencies" which I find perplexing since this is KDE(3) land after all.
No, it isn't. It's *T*DE land. Sadly KDE3 is dead and KDE4 rules. But surely X is not a KDE application, so should not have KDE dependancies.
sorry, I meant 'X' as a logical variable as in 'x is greater than y'. I was unclear.
anyhoo, I've fixed just about all the problems.
strangely if I start evince (from the cli) without a pdf file, it crashes (segmentation fault) but otherwise it seems to work. I don't know how to interpret the strace so I'll only remark it dies after 'futex_wake' calls.
F.
On Sunday 28 of December 2014 10:19:06 Felmon Davis wrote:
folks,
I just noticed I'm up to r14.0.1 [development] on one of my laptops; what is the best way to downgrade to r14.0.0?
F.
ExeGNU/Linux uses an alternative apt source 'preliminary-stable-builds'. For the recent information about this apt source see http://bugs.trinitydesktop.org/showdependencytree.cgi?id=2246
As you rightly ascertained, the first packages for the upcoming R14.0.1 are beginning to appear. If you're wondering what was fixed - see bug 2246: http://bugs.trinitydesktop.org/showdependencytree.cgi?id=2246
If you want to go back to R14.0.0 use the following procedure:
1) run aptitude install apt-trinity-archive 2) give into remarks apt source mirrors.xcer.cz/trinity-sb 3) start aptitude and limit the display to "~i-trinity~V14.0.1" 4) for all displayed packages manually select the version 14.0.0 - when choosing do not let to distractions that aptitude will report a broken dependencies - all will be fine, until all the packages will be selected for degradation.
On Sunday 28 of December 2014 15:11:27 Slávek Banko wrote:
ExeGNU/Linux uses an alternative apt source 'preliminary-stable-builds'. For the recent information about this apt source see http://bugs.trinitydesktop.org/showdependencytree.cgi?id=2246
oops, wrong link - should be http://trinity-users.pearsoncomputing.net/?0::7263
On Sun, 28 Dec 2014, Slávek Banko wrote:
On Sunday 28 of December 2014 10:19:06 Felmon Davis wrote:
folks,
I just noticed I'm up to r14.0.1 [development] on one of my laptops; what is the best way to downgrade to r14.0.0?
F.
ExeGNU/Linux uses an alternative apt source 'preliminary-stable-builds'. For the recent information about this apt source see http://bugs.trinitydesktop.org/showdependencytree.cgi?id=2246
As you rightly ascertained, the first packages for the upcoming R14.0.1 are beginning to appear. If you're wondering what was fixed - see bug 2246: http://bugs.trinitydesktop.org/showdependencytree.cgi?id=2246
If you want to go back to R14.0.0 use the following procedure:
thank you but I'll hold off for now to see if I can fix my problems. btw I ran the first command below (but inserted '-s' before 'install' and got an error about not being able to find that package.
F.
- run aptitude install apt-trinity-archive
- give into remarks apt source mirrors.xcer.cz/trinity-sb
- start aptitude and limit the display to "~i-trinity~V14.0.1"
- for all displayed packages manually select the version 14.0.0 - when
choosing do not let to distractions that aptitude will report a broken dependencies - all will be fine, until all the packages will be selected for degradation.
On Sunday 28 December 2014 10:33:39 am you wrote:
On Sun, 28 Dec 2014, Slávek Banko wrote:
On Sunday 28 of December 2014 10:19:06 Felmon Davis wrote:
folks,
I just noticed I'm up to r14.0.1 [development] on one of my laptops; what is the best way to downgrade to r14.0.0?
F.
ExeGNU/Linux uses an alternative apt source 'preliminary-stable-builds'. For the recent information about this apt source see http://bugs.trinitydesktop.org/showdependencytree.cgi?id=2246
As you rightly ascertained, the first packages for the upcoming R14.0.1 are beginning to appear. If you're wondering what was fixed - see bug 2246: http://bugs.trinitydesktop.org/showdependencytree.cgi?id=2246
If you want to go back to R14.0.0 use the following procedure:
thank you but I'll hold off for now to see if I can fix my problems. btw I ran the first command below (but inserted '-s' before 'install' and got an error about not being able to find that package.
F.
To fix installs, add 'apt-get -f install' to your tool box. Another tool, 'apt-cache search apt-trinity-archive' or any string of text, will let you know whats available and what the actual package name is.
- run aptitude install apt-trinity-archive
- give into remarks apt source mirrors.xcer.cz/trinity-sb
- start aptitude and limit the display to "~i-trinity~V14.0.1"
- for all displayed packages manually select the version 14.0.0 - when
choosing do not let to distractions that aptitude will report a broken dependencies - all will be fine, until all the packages will be selected for degradation.
On Sun, 28 Dec 2014, Greg Madden wrote:
On Sunday 28 December 2014 10:33:39 am you wrote:
On Sun, 28 Dec 2014, Slávek Banko wrote:
On Sunday 28 of December 2014 10:19:06 Felmon Davis wrote:
folks,
I just noticed I'm up to r14.0.1 [development] on one of my laptops; what is the best way to downgrade to r14.0.0?
F.
ExeGNU/Linux uses an alternative apt source 'preliminary-stable-builds'. For the recent information about this apt source see http://bugs.trinitydesktop.org/showdependencytree.cgi?id=2246
As you rightly ascertained, the first packages for the upcoming R14.0.1 are beginning to appear. If you're wondering what was fixed - see bug 2246: http://bugs.trinitydesktop.org/showdependencytree.cgi?id=2246
If you want to go back to R14.0.0 use the following procedure:
thank you but I'll hold off for now to see if I can fix my problems. btw I ran the first command below (but inserted '-s' before 'install' and got an error about not being able to find that package.
F.
To fix installs, add 'apt-get -f install' to your tool box.
already sitting in the top drawer of my tool box but doesn't work.
Another tool, 'apt-cache search apt-trinity-archive' or any string of text, will let you know whats available and what the actual package name is.
thanks. I know. ain't in there. but many thanks! did
apt-cache search archive |grep trinity
and caught some potentially useful fish! it lists "trinity-apt-archive" for instance.
thanks for prompting this deeper search.
F.
On Sunday 28 of December 2014 22:42:01 Felmon Davis wrote:
On Sun, 28 Dec 2014, Greg Madden wrote:
On Sunday 28 December 2014 10:33:39 am you wrote:
On Sun, 28 Dec 2014, Slávek Banko wrote:
On Sunday 28 of December 2014 10:19:06 Felmon Davis wrote:
folks,
I just noticed I'm up to r14.0.1 [development] on one of my laptops; what is the best way to downgrade to r14.0.0?
F.
ExeGNU/Linux uses an alternative apt source 'preliminary-stable-builds'. For the recent information about this apt source see http://bugs.trinitydesktop.org/showdependencytree.cgi?id=2246
As you rightly ascertained, the first packages for the upcoming R14.0.1 are beginning to appear. If you're wondering what was fixed - see bug 2246: http://bugs.trinitydesktop.org/showdependencytree.cgi?id=2246
If you want to go back to R14.0.0 use the following procedure:
thank you but I'll hold off for now to see if I can fix my problems. btw I ran the first command below (but inserted '-s' before 'install' and got an error about not being able to find that package.
F.
To fix installs, add 'apt-get -f install' to your tool box.
already sitting in the top drawer of my tool box but doesn't work.
Another tool, 'apt-cache search apt-trinity-archive' or any string of text, will let you know whats available and what the actual package name is.
thanks. I know. ain't in there. but many thanks! did
apt-cache search archive |grep trinity
and caught some potentially useful fish! it lists "trinity-apt-archive" for instance.
thanks for prompting this deeper search.
F.
Oops, my mistake - I wrote the package name from memory... and then I forgot to verify it.
-
E. Liddell -
Felmon Davis -
Greg Madden -
Lisi Reisz -
Michele Calgaro -
Slávek Banko -
Timothy Pearson