15 Jan
2015
15 Jan
'15
5:28 a.m.
Hello,
for specific and motivated reasons, my Debian installation is composed
of packages spread across the following repositories listed in my
sources.list:
deb http://ftp.de.debian.org/debian jessie main
deb http://ftp.de.debian.org/debian wheezy main
# kde3 for ubuntu/squeeze (being replaced by Trinity, right now)
#deb http://ppa.launchpad.net/kde3-maintainers/ppa/ubuntu/ karmic main
# trinity
deb 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
## displaylink xorg driver
deb http://ch.archive.ubuntu.com/ubuntu/ precise main universe
After I issue
# apt-get update
# apt-get install tde-trinity
I get:
The following packages have unmet dependencies:
tde-trinity : Depends: tdeaddons-trinity (>= 4:14.0.0~) but it is
not going to be installed
Depends: tdepim-trinity (>= 4:14.0.0~) but it is not
going to be installed
E: Unable to correct problems, you have held broken packages.
Going down the dependency chain, I find:
# apt-get install tde-trinity tdeaddons-trinity
kaddressbook-plugins-trinity kaddressbook-trinity libical1
Package libical1 is not available, but is referred to by another
package. [...]
However the following packages replace it:
libical1a
Is this a bug or a problem with my setup?
What should be done?
-- Davide
15 Jan
15 Jan
6:02 a.m.
New subject: [trinity-users] Debian installation fails: "Package libical1 is not available"
On Thu January 15 2015 05:28:12 Davide Baldini wrote:
Going down the dependency chain, I find:
# apt-get install tde-trinity tdeaddons-trinity
kaddressbook-plugins-trinity kaddressbook-trinity libical1
Package libical1 is not available, but is referred to by another
package. [...]
However the following packages replace it:
libical1a
What happens if you try to install libical1a instead of libical1
with your apt-get command?
--Mike
6:43 a.m.
New subject: [trinity-users] Debian installation fails: "Package libical1 is not available"
Replacing libical1 with libical1a:
# apt-get install tde-trinity tdeaddons-trinity
kaddressbook-plugins-trinity kaddressbook-trinity libical1a
libical1a is already the newest version.
libical1a set to manually installed.
Some packages could not be installed. [...]
The following packages have unmet dependencies:
kaddressbook-trinity : Depends: libical1 (>= 1.0) but it is not
installable
On 01/15/15 15:02, Mike Bird wrote:
What happens if you try to install libical1a instead
of libical1
with your apt-get command?
6:57 a.m.
New subject: [trinity-users] Debian installation fails: "Package libical1 is not available"
On Thursday 15 of January 2015 15:02:00 Mike Bird wrote:
On Thu January 15 2015 05:28:12 Davide Baldini wrote:
Debian Jessie is too much moving target, than to be able to use the final TDE
R14.0.0. Basically final R14.0.0 ever "should not be" officially released for
Jessie. Is simply not possible to release a final release for non-final
system.
You can instead use an alternative apt source 'preliminary-stable-builds',
which already reflect on change libical1 => libical1a.
--
Slávek
Going down the dependency chain, I find:
# apt-get install tde-trinity tdeaddons-trinity
kaddressbook-plugins-trinity kaddressbook-trinity libical1
Package libical1 is not available, but is referred to by another
package. [...]
However the following packages replace it:
libical1a
What happens if you try to install libical1a instead of libical1
with your apt-get command?
--Mike
7:46 a.m.
New subject: [trinity-users] Debian installation fails: "Package libical1 is not available"
On 01/15/15 15:57, Slávek Banko wrote
You can instead use an alternative apt source
'preliminary-stable-builds',
which already reflect on change libical1 => libical1a.
Fantastic. I inserted this repository into sources.list:
deb http://mirror.xcer.cz/trinity-sb jessie deps-r14 main-r14
now APT successfully computes the dependency tree and prompts me for
confirmation to proceed with installation.
However, I also found an alternative repository hosting the same Trinity
release for Jessie, namely:
deb
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/u…
jessie main
Should I prefer one to the other, or are both equivalent?
-- Davide
8:19 a.m.
New subject: [trinity-users] Debian installation fails: "Package libical1 is not available"
On Thursday 15 of January 2015 16:46:09 Davide Baldini wrote:
On 01/15/15 15:57, Slávek Banko wrote
No, they are not identical.
Nightly-builds have target R14.1.0.
Preliminary-stable-builds have target R14.0.1.
--
Slávek
You can instead use an alternative apt source
'preliminary-stable-builds', which already reflect on change libical1 =>
libical1a.
Fantastic. I inserted this repository into sources.list:
deb http://mirror.xcer.cz/trinity-sb jessie deps-r14 main-r14
now APT successfully computes the dependency tree and prompts me for
confirmation to proceed with installation.
However, I also found an alternative repository hosting the same Trinity
release for Jessie, namely:
deb
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/u
buntu jessie main
Should I prefer one to the other, or are both equivalent?
-- Davide
2:36 p.m.
New subject: [trinity-users] Debian installation fails: "Package libical1 is not available"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 01/16/2015 01:19 AM, Slávek Banko wrote:
On Thursday 15 of January 2015 16:46:09 Davide Baldini
wrote:
i.e.
1) http://mirror.xcer.cz/trinity-sb
this is Slavek's own repository. Here you find the R14.0.x branch nightly builds.
2) http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/u…
this is the official nightly build address. Here you find the R14.1.0 branch nightly
builds.
Cheers
Michele
On 01/15/15 15:57, Slávek Banko wrote
No, they are not identical. Nightly-builds have target R14.1.0. Preliminary-stable-builds
have target R14.0.1.
You can instead use an alternative apt source
'preliminary-stable-builds', which already reflect on change
libical1 => libical1a.
Fantastic. I inserted this repository into sources.list: deb
http://mirror.xcer.cz/trinity-sb jessie deps-r14
main-r14
now APT successfully computes the dependency tree and prompts me for confirmation to
proceed with installation.
However, I also found an alternative repository hosting the same Trinity release for
Jessie, namely:
deb http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/u buntu
jessie main
Should I prefer one to the other, or are both equivalent?
-- Davide
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJUuEDoAAoJECp1t8qK3tXP1WMQAKin/Hn4f0CeDVCuO2Jdi/nI
ElVRrk+RjTDI+MTB7Lf794aaaaiJlIf4b7siJoRCs7L81jWQtgDyxO6129NtR3KG
vksQQ9xmCPUcd72Z+GSvzrVRk5M8IggGrNRV1+u68CzgcBUDvrc1lbaxwsVOXevI
SrCXiTSYI8Dhqe4FfZbnoYpWTJFjCOxi+LhFWqfXJBmhUTbVcCsZFA6JyuitiOvm
2SVDIPP92MJbLZO57xxn/fHnWCwFUD/67aWfdQCzli9KPJu+rGkVGndaLwhW61Yx
UFuUItnwb5dAga8HYz9s+8+KJWmNZ/15UTwtPZfHd7WEqdJRVmJjZZvoOZRMsuPy
6C9USUOBmQQXE/XtAps5UVvRvvGbkqtrHAK+r1rHzxJ3Rt8a4MixTNXOtKXrG9rF
eTAT+O+jsUgbtXHgMQXZjnenCpbCyC+A4OSvlqjLuZZDdJ/p0yCNFvAeZ8sdRMh/
YQm2a1mFh/SLSdsmbHrrE7OyRDJKKZorr+x1wkD+Z/tEq7+i8BQ8nCkHYF+9y8qV
awJB3VksKvDlUOJtMfunJ1fdsTeNZUUCKfl8plwzkd2yOE/7faqMKeZjfeM8YS0T
RAN18fDR/hDcXGrSCiBGMb2a2UPmmGLxzdOSG2MM1bXvHFC4hx4NRk17lAiOPMw7
xeFWoWnmTwreCuOYJra8
=W3dB
-----END PGP SIGNATURE-----
2:58 p.m.
New subject: [trinity-users] Debian installation fails: "Package libical1 is not available"
On Thu January 15 2015 14:36:25 Michele Calgaro wrote:
1) http://mirror.xcer.cz/trinity-sb
this is Slavek's own repository. Here you find the R14.0.x branch
nightly builds.
2)
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds/u
buntu this is the official nightly build address. Here you find the R14.1.0
branch nightly builds.
Is there somewhere a user-level explanation of these two branches,
or are they something that regular users (not developers) should
ignore?
--Mike
3:41 p.m.
New subject: [trinity-users] Debian installation fails: "Package libical1 is not available"
On Thursday 15 January 2015 22:58:00 Mike Bird wrote:
On Thu January 15 2015 14:36:25 Michele Calgaro
wrote:
No! Don't ignore them. Following Slavek keeps one nicely up to date with
patches.
Lisi
1) http://mirror.xcer.cz/trinity-sb
this is Slavek's own repository. Here you find the R14.0.x branch
nightly builds.
2)
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds
/u buntu this is the official nightly build address. Here you find the
R14.1.0 branch nightly builds.
Is there somewhere a user-level explanation of these two branches,
or are they something that regular users (not developers) should
ignore?
4:10 p.m.
New subject: [trinity-users] Debian installation fails: "Package libical1 is not available"
On Thu January 15 2015 15:41:08 Lisi Reisz wrote:
No! Don't ignore them. Following Slavek keeps
one nicely up to date with
patches.
Is this like the difference between Stable and Unstable?
I'm really struggling to see how the different versions
are intended to be understood by users.
--Mike
4:44 p.m.
New subject: [trinity-users] Debian installation fails: "Package libical1 is not available"
On Friday 16 of January 2015 01:10:44 Mike Bird wrote:
Is this like the difference between Stable and
Unstable?
I'm really struggling to see how the different versions
are intended to be understood by users.
Yes, this is probably the most accurate expression.
In the apt source 'preliminary-stable-builds' packages are based on
'r14.0.x'
GIT branch == basis for maintenance releases R14.0.1, R14.0.2, etc. In short,
focused on the stable releases.
In the apt source 'nightly-builds' packages are based on the 'master' GIT
branch == basis for a future release R14.1.0. In short, focused on the
development of new features - may be unstable.
--
Slávek
5:12 p.m.
New subject: [trinity-users] Debian installation fails: "Package libical1 is not available"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 01/16/2015 09:44 AM, Slávek Banko wrote:
On Friday 16 of January 2015 01:10:44 Mike Bird
wrote:
R14.0.0: stable version. Does not change.
R14.0.x nightly builds: development branch of next maintenance release of R14.0. Will not
contains major changes from
R14.0.0 unless critical problems are found. Mostly bug fixes for the stable version
R14.1.0 nightly builds: development branch of next minor release (R14.1.0). Major changes
will go here, together with
all fixes done in R14.0.x
1) If you want a real stable version, use R14.0.0.
2) If you want a stable version (but that sometimes may have minor temporary problems) use
R14.0.x branch, so you can
help testing the next maintenance release.
3) If you want a somehow less stable version (that sometimes may also have major temporary
problems) use R14.1.0
branch, so you can help testing the next minor release.
Cheers
Michele
Is this like the difference between Stable and
Unstable?
I'm really struggling to see how the different versions are intended to be understood
by users.
Yes, this is probably the most accurate expression.
In the apt source 'preliminary-stable-builds' packages are based on
'r14.0.x' GIT branch == basis for maintenance
releases R14.0.1, R14.0.2, etc. In short, focused on the stable releases.
In the apt source 'nightly-builds' packages are based on the 'master' GIT
branch == basis for a future release
R14.1.0. In short, focused on the development of new features - may be unstable.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJUuGV2AAoJECp1t8qK3tXPwX4P/jFh8YekhuynhI6xmr/BS7KF
HkZkPtheZuyxpGlTOOiXyZvsTDsAtCWnVDMmAxLt971iX1F3l9ay7tPnYW5i0iIO
yqrVvo9f5znior2hfy/2iaiUBRZGpz1nYYc4hzPcoyvgwpqj0/Aq/Kd4oq7woHvB
2OL+7wZtXFYSz/jkIH4xBwfR+ss8AgtB2q0sgJSUQPpEP2W873y4qXBJr4mZrSDn
ImNknywQakXFsadSd3y1DXE9/O8xwgq0/TppOmE2nr8gxXNb2PgYVjztiohWA+CY
k8mPZwytnh6j/b+4OZxucIilq4VCpRMseq6eY+UX5gvXlbgRK8n3KV7bAGa17gPW
0Z9+2HqjrYMeVmrR2Rlue9p1te++/oCg5rSWStgzdEH5tkyzD5hCc+hLghNLujc2
600Vo2GeAyCa42sTa3l7c70z5fwWLM3lb6hkK+BUr8kR9g2WlTKvKwMs0yOcYbn8
RMKqrPACBQxnZ97yEKWSITYRawoa4AsRvDmRtUeohnOylzKeA3mDRWI6FfJgNCcS
+V7oLU8L01D2Uom8Gh86r6kyOKX7MvuhGQg6orVQfJ8duL22DGudvLZGBKsx4M5b
MLJUz7j/FuBHPWQfTmQASV7Qx5YxrjvIwL9ieIhU0sk8Ddu7jBdQb4hyVHUj4KE+
azZBeia0qutgLh8wSlqR
=08yV
-----END PGP SIGNATURE-----
16 Jan
16 Jan
2:38 a.m.
New subject: [trinity-users] Debian installation fails: "Package libical1 is not available"
On Friday 16 January 2015 00:10:44 Mike Bird wrote:
On Thu January 15 2015 15:41:08 Lisi Reisz wrote:
I look at it that Slavek is Stable with bug fixes. Best of all possible
worlds!
It doesn't quite equate to Stable, Testing, Unstable, Experimental.
Lisi
No! Don't ignore them. Following Slavek
keeps one nicely up to date
with patches.
Is this like the difference between Stable and Unstable?
I'm really struggling to see how the different versions
are intended to be understood by users. 
15 Jan
15 Jan
5:02 p.m.
New subject: [trinity-users] Debian installation fails: "Package libical1 is not available"
On Thursday 15 January 2015 1:58:00 pm you wrote:
On Thu January 15 2015 14:36:25 Michele Calgaro
wrote:
My interpretation of 'regular users' is follow the install instructions on
the Trinity website, there is no mention
of 'http://mirror.xcer.cz/trinity-sb'
I depend on stable, mine is a business environment, new software=new bugs :-)
--
Peace,
Greg
1) http://mirror.xcer.cz/trinity-sb
this is Slavek's own repository. Here you find the R14.0.x branch
nightly builds.
2)
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-nightly-builds
/u buntu this is the official nightly build address. Here you find the
R14.1.0 branch nightly builds.
Is there somewhere a user-level explanation of these two branches,
or are they something that regular users (not developers) should
ignore?
--Mike
3406
days inactive
3407
days old
13 comments
6 participants
participants (6)
-
Davide Baldini -
Greg Madden -
Lisi Reisz -
Michele Calgaro -
Mike Bird -
Slávek Banko