28 Dec
2014
28 Dec
'14
9:19 a.m.
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.
--
Felmon Davis
The way out is never as easy as the way in.
28 Dec
28 Dec
11:24 a.m.
New subject: [trinity-users] backpedal to r14.0.0
-----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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJUn+hwAAoJECp1t8qK3tXPQWUQALngvcPq7fVKHhpvgOO0GW17
6r6gFi93NsFR/3yr//aJHfI58iXiiJtw7ehacKky/0gvnmbWmkd3/6mBIP7xXwMR
l1/4CksE2B1GGjZ0trOcwVYfeLDtVsM/9bbxvY0Kv1KeZTUOnyftKg8Yx/lDsr5O
Ep9bpaykPEI8CrkP9bab2NyddDt4wwWGSUQ2AkeiR4/OB5yyblYQ2KRFDihlMAVD
StT7YqbTQoDDDWbdZ39/VNhsW9liyHV/KveN8+k+gPPU8tNMyDncCcC+AzEZvtrk
R6Z9jSvmL4rGU9gqbFAG3T+1Hk+4cY9rDETyEnzvJumqOVjh9RJ7MJrnrXuk9CGJ
HWSMPrOG2QisbF5H7dwiwNcSB8tiUOtgTNvZvlTuwXks2xza326PeT4qaCnkrX+F
qJMgwr2SioJ1lkRuiFaMnb+W6dJQYWMCwRCPkX5vQKXQbgWhBLOa99sCptzS2gDf
ZTHHqISV4bRRER8BsQPWqZxFlFR6PzfV6IlRFXq8Kbw/TqOKTKhw12km0LRFGz4o
LbubGv4fFUERGWnXmM4QwYaKcDRBqL0PtWlBnMEzehK09vsJbaDn+wVQgXLukzVO
yhkuIgLt9ls0UGIN351HTP0iAi6Zb2lIXmNG37L7uYAtvChoAYYFrDuaUJCdGrsV
oQCgcgX8+1C2q3WMoGQK
=JiWj
-----END PGP SIGNATURE-----
7:26 p.m.
New subject: [trinity-users] backpedal to r14.0.0
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.…
jessie main
deb-src
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-r14.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.
--
Felmon Davis
The way out is never as easy as the way in.
7:30 p.m.
New subject: [trinity-users] backpedal to r14.0.0
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
On Sun, 28 Dec 2014, Michele Calgaro wrote:
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?
-----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.
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlSgWjoACgkQLaxZSoRZrGH6FgDgu4PVPbCvyiySdRXseezMcIcL
fdhHvvdDr4czZADfaZO5PDqOC1+QxgQ7OUz+PvIMiIP1W+XMKfdi/A==
=PCuk
-----END PGP SIGNATURE-----
7:49 p.m.
New subject: [trinity-users] backpedal to r14.0.0
On Sun, 28 Dec 2014, Timothy Pearson wrote:
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.
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.
--
Felmon Davis
I've enjoyed just about as much of this as I can stand.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
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
------
On Sun, 28 Dec 2014, Michele Calgaro wrote:
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?
-----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.
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. :-) 
11:31 p.m.
New subject: [trinity-users] backpedal to r14.0.0
On Sun, 28 Dec 2014 14:49:02 -0500 (EST)
Felmon Davis <davisf(a)union.edu> wrote:
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, 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. :-)
29 Dec
29 Dec
4:55 a.m.
New subject: [trinity-users] backpedal to r14.0.0
On Sun, 28 Dec 2014, E. Liddell wrote:
On Sun, 28 Dec 2014 14:49:02 -0500 (EST)
Felmon Davis <davisf(a)union.edu> wrote:
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.
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. :-) 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
--
Felmon Davis
While you recently had your problems on the run, they've regrouped and
are making another attack.
7:46 a.m.
New subject: [trinity-users] backpedal to r14.0.0
On Sunday 28 December 2014 7:55:35 pm you wrote:
On Sun, 28 Dec 2014, E. Liddell wrote:
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'
--
Peace,
Greg
On Sun, 28 Dec 2014 14:49:02 -0500 (EST)
Felmon Davis <davisf(a)union.edu> 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.
anyway, I had to do some futzing around, basically accepting a number
of 'downgrades', for example: On Sun, 28 Dec 2014, Timothy Pearson wrote:
bluedevil is a KDE project, so it's unsurprising it wants a bunch
of KDE4 stuff installed. There are a couple of alternatives, though. > 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. 
8 a.m.
New subject: [trinity-users] backpedal to r14.0.0
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
5:35 p.m.
New subject: [trinity-users] backpedal to r14.0.0
On Mon, 29 Dec 2014, Lisi Reisz wrote:
On Monday 29 December 2014 04:55:35 Felmon Davis
wrote:
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.
--
Felmon Davis
grep me no patterns and I'll tell you no lines.
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.
28 Dec
28 Dec
11:24 a.m.
New subject: [trinity-users] backpedal to r14.0.0
-----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 SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJUn+h1AAoJECp1t8qK3tXPTLgP+gIEzX4hJoJOw4ZVHQRAOb85
Lt2+LCcpCqDYlWdpwZwqDhh9+RvyAwK3yzVJ/9VUGTDdTmduf4eeTJvr14R19hPg
lbD+b9fz5suWAQpnKd4hzEv+pX/gUw/y7NudawuIF++YmYyolCCbJBrj1WdgpLv/
abO9d4sN5y8h4ahybGdhnvoCQR17qZdQSCL5dnoSBa8CfCr8sdwTs+UgcOzx40md
9Zah4eqsBFtNWaTQLp+maboRFFoYbnVsf2lR7rLPDt1K4P5mm5pC0op5GpEq2Yvg
3TRinZzVXuvdZ3B2BQW0pTAgNnYlmFKZsdZ2F+4g3AVWmEcMUlLX6re/Z/DiBLli
mi4QNmAlp21uUim9wbg+2ERSoZZqssLEuFB72AbTtHr49GniXFjbuu7lBXPi/jLV
8wsbP78NwjNJ6E6IYR9NpHsy4G4eazvcrUrNMx+M60L5vDinUSEz/7a1q0Q9dilL
5FyFi4+o0boxDch9E9TnCM0HvwzOxDzkT7D2MPSXOZy/X734iUfwYqCe9lJZLMIT
kH4KRNS+rJoRR1mkxvWQba/TnEBuR61BxolOd/gtk90fcz1cUmVmDl84GSCRId4D
wOI/UF+RsI4iamHMlkigyhoGzT0B7Lmo1GprtiJ/6l2PGe8ASo+Dxq1EGNiztR60
AuE20927hF2IRPUp+O93
=48Tf
-----END PGP SIGNATURE-----
2:11 p.m.
New subject: [trinity-users] backpedal to r14.0.0
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.
--
Slávek
2:15 p.m.
New subject: [trinity-users] backpedal to r14.0.0
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
7:33 p.m.
New subject: [trinity-users] backpedal to r14.0.0
On Sun, 28 Dec 2014, Slávek Banko wrote:
On Sunday 28 of December 2014 10:19:06 Felmon Davis
wrote:
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.
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.
--
Felmon Davis
Desperate diseases must have desperate cures.
9:19 p.m.
New subject: [trinity-users] backpedal to r14.0.0
On Sunday 28 December 2014 10:33:39 am you wrote:
On Sun, 28 Dec 2014, Slávek Banko wrote:
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.
On Sunday 28 of December 2014 10:19:06 Felmon
Davis wrote:
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. 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.
--
Peace,
Greg
9:42 p.m.
New subject: [trinity-users] backpedal to r14.0.0
On Sun, 28 Dec 2014, Greg Madden wrote:
On Sunday 28 December 2014 10:33:39 am you wrote:
already sitting in the top drawer of my tool box but doesn't work.
On Sun, 28 Dec 2014, Slávek Banko wrote:
To fix installs, add 'apt-get -f install' to your tool box. On Sunday 28 of December 2014 10:19:06 Felmon
Davis wrote:
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. 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: 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.
--
Felmon Davis
Please come again.
29 Dec
29 Dec
12:27 a.m.
New subject: [trinity-users] backpedal to r14.0.0
On Sunday 28 of December 2014 22:42:01 Felmon Davis wrote:
On Sun, 28 Dec 2014, Greg Madden wrote:
Oops, my mistake - I wrote the package name from memory... and then I forgot
to verify it.
--
Slávek
On Sunday 28 December 2014 10:33:39 am you
wrote:
already sitting in the top drawer of my tool box but doesn't work.
On Sun, 28 Dec 2014, Slávek Banko wrote:
To fix installs, add 'apt-get -f install' to your tool box. 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. 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.
3404
days inactive
3405
days old
16 comments
7 participants
participants (7)
-
E. Liddell -
Felmon Davis -
Greg Madden -
Lisi Reisz -
Michele Calgaro -
Slávek Banko -
Timothy Pearson