15 Feb
2022
15 Feb
'22
4:43 p.m.
# zypper install trinity-desktop
...
Problem: nothing provides 'libjasper.so.4()(64bit)' needed by the to be installed
trinity-tdelibs-14.0.11-1.osstw.x86_64
Solution 1: do not install trinity-desktop-14.0.11-1.osstw.noarch
Solution 2: break trinity-tdelibs-14.0.11-1.osstw.x86_64 by ignoring some of its
dependencies
libjasper4-2.0.33-2.1.x86_64.rpm
has been replaced by
libjasper6-3.0.0-1.1.x86_64.rpm
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
17 Feb
17 Feb
8:41 a.m.
Le 16/02/2022 à 01:43, Felix Miata a écrit :
# zypper install trinity-desktop
...
Problem: nothing provides 'libjasper.so.4()(64bit)' needed by the to be installed
trinity-tdelibs-14.0.11-1.osstw.x86_64
Solution 1: do not install trinity-desktop-14.0.11-1.osstw.noarch
Solution 2: break trinity-tdelibs-14.0.11-1.osstw.x86_64 by ignoring some of its
dependencies
libjasper4-2.0.33-2.1.x86_64.rpm
has been replaced by
libjasper6-3.0.0-1.1.x86_64.rpm
Hello Felix,
Alas, tdelibs fails to build against jasper 3.0 :(
/usr/bin/make -f kimgio/CMakeFiles/kimg_jp2-module.dir/build.make
kimgio/CMakeFiles/kimg_jp2-module.dir/build
make[3]: Entering directory
'/tmp/BUILD.osstw.x86_64/trinity-tdelibs-14.0.11/build'
[ 80%] Linking CXX shared module kimg_jp2.so
cd /tmp/BUILD.osstw.x86_64/trinity-tdelibs-14.0.11/build/kimgio &&
/usr/bin/cmake -E cmake_link_script
CMakeFiles/kimg_jp2-module.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -O2 -g -m64 -fmessage-length=0 -D_FORTIFY_SOURCE=2
-fstack-protector -funwind-tables -fasynchronous-unwind-tables
-fdebug-prefix-map=/tmp/BUILD.osstw.x8
6_64/trinity-tdelibs-14.0.11=.
-fmacro-prefix-map=/tmp/BUILD.osstw.x86_64/trinity-tdelibs-14.0.11=.
-fvisibility=hidden -fvisibility-inlines-hidden -DQT_NO_ASCII_CAST -DQ
T_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION
-DQT_THREAD_SUPPORT -D_REENTRANT -I/usr/include/tqt3 -I/usr/include/tqt
-include tqt.h -DQT_NO_ASCII_CAST
-DQT_CLEAN_NAMESPACE -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION
-DQT_THREAD_SUPPORT -D_REENTRANT -include tqt.h -DNDEBUG
-Wl,--as-needed -Wl,--no-undefined -shared -
o kimg_jp2.so CMakeFiles/kimg_jp2-module.dir/jp2.cpp.o
-Wl,-rpath,/tmp/BUILD.osstw.x86_64/trinity-tdelibs-14.0.11/build/tdecore:/tmp/BUILD.osstw.x86_64/trinity-tdelibs-14
.0.11/build/dcop:/tmp/BUILD.osstw.x86_64/trinity-tdelibs-14.0.11/build/tdefx
../tdecore/libtdecore.so.14.0.0 -ljasper -ljpeg
../dcop/libDCOP.so.14.0.0 ../tdefx/libtdefx.so
.14.0.0 -ltqt -ltqt-mt -lXrender -lX11 -lc -lICE -lSM -lz
/usr/lib64/gcc/x86_64-suse-linux/11/../../../../x86_64-suse-linux/bin/ld:
CMakeFiles/kimg_jp2-module.dir/jp2.cpp.o: in function `kimgio_jp2_write':
./build/kimgio/./kimgio/jp2.cpp:282: undefined reference to `jp2_encode'
collect2: error: ld returned 1 exit status
make[3]: *** [kimgio/CMakeFiles/kimg_jp2-module.dir/build.make:106:
kimgio/kimg_jp2.so] Error 1
make[3]: Leaving directory
'/tmp/BUILD.osstw.x86_64/trinity-tdelibs-14.0.11/build'
make[2]: *** [CMakeFiles/Makefile2:19724:
kimgio/CMakeFiles/kimg_jp2-module.dir/all] Error 2
make[2]: Leaving directory
'/tmp/BUILD.osstw.x86_64/trinity-tdelibs-14.0.11/build'
make[1]: *** [Makefile:149: all] Error 2
make[1]: Leaving directory
'/tmp/BUILD.osstw.x86_64/trinity-tdelibs-14.0.11/build'
François
11:46 a.m.
On Thu, 17 Feb 2022 17:41:30 +0100
François Andriot <francois.andriot(a)libertysurf.fr> wrote:
Le 16/02/2022 à 01:43, Felix Miata a écrit :
libjasper is there to provide support for an image format that no one really
uses. It's probably safe (even for packaging) to compile tdelibs with
WITH_JASPER off and drop the dependency. It's very unlikely that
anyone will ever notice.
E. Liddell
# zypper install trinity-desktop
...
Problem: nothing provides 'libjasper.so.4()(64bit)' needed by the to be installed
trinity-tdelibs-14.0.11-1.osstw.x86_64
Solution 1: do not install trinity-desktop-14.0.11-1.osstw.noarch
Solution 2: break trinity-tdelibs-14.0.11-1.osstw.x86_64 by ignoring some of its
dependencies
libjasper4-2.0.33-2.1.x86_64.rpm
has been replaced by
libjasper6-3.0.0-1.1.x86_64.rpm
Hello Felix,
Alas, tdelibs fails to build against jasper 3.0 :( 
11:55 a.m.
On Thursday, February 17, 2022, E. Liddell <ejlddll(a)warpmail.net> wrote:
On Thu, 17 Feb 2022 17:41:30 +0100
François Andriot <francois.andriot(a)libertysurf.fr> wrote:
libjasper is there to provide support for an image format that no one
really
uses. It's probably safe (even for packaging) to compile tdelibs with
WITH_JASPER off and drop the dependency. It's very unlikely that
anyone will ever notice.
if we talk about (open) jpeg2000 some users might notice.. but well, for
development packages hopefully this can be resolved in some way (either by
changing code to compile with new libjasper or adding libopenjpeg
decoding)
Le 16/02/2022 à 01:43, Felix Miata a écrit :
> # zypper install trinity-desktop
> ...
> Problem: nothing provides 'libjasper.so.4()(64bit)' needed by the to
be installed trinity-tdelibs-14.0.11-1.osstw.x86_64
> Solution 1: do not install
trinity-desktop-14.0.11-1.osstw.noarch
> Solution 2: break trinity-tdelibs-14.0.11-1.osstw.x86_64 by
ignoring some
of its dependencies
libjasper4-2.0.33-2.1.x86_64.rpm
has been replaced by
libjasper6-3.0.0-1.1.x86_64.rpm
Hello Felix,
Alas, tdelibs fails to build against jasper 3.0 :(
E. Liddell
____________________________________________________
tde-devels mailing list -- devels(a)trinitydesktop.org
To unsubscribe send an email to devels-leave(a)trinitydesktop.org
Web mail archive available at https://mail.trinitydesktop.
org/mailman3/hyperkitty/list/devels(a)trinitydesktop.org
12:07 p.m.
On Thursday, February 17, 2022, Andrew Randrianasulu <
randrianasulu(a)gmail.com> wrote:
On Thursday, February 17, 2022, E. Liddell <ejlddll(a)warpmail.net> wrote:
https://jasper-software.github.io/jasper-manual/releases/version-3.0.0/html…
hopefully enough info for adding changes.... or at least you can look
around and ask author for explaining them a bit more
On Thu, 17 Feb 2022 17:41:30 +0100
François Andriot <francois.andriot(a)libertysurf.fr> wrote:
libjasper is there to provide support for an image format that no one
really
uses. It's probably safe (even for packaging) to compile tdelibs with
WITH_JASPER off and drop the dependency. It's very unlikely that
anyone will ever notice.
if we talk about (open) jpeg2000 some users might notice.. but well, for
development packages hopefully this can be resolved in some way (either by
changing code to compile with new libjasper or adding libopenjpeg
decoding)
Le 16/02/2022 à 01:43, Felix Miata a écrit :
> # zypper install trinity-desktop
> ...
> Problem: nothing provides 'libjasper.so.4()(64bit)' needed by the to
be installed trinity-tdelibs-14.0.11-1.osstw.x86_64
> Solution 1: do not install
trinity-desktop-14.0.11-1.osstw.noarch
> Solution 2: break trinity-tdelibs-14.0.11-1.osstw.x86_64 by
ignoring some
of its dependencies
libjasper4-2.0.33-2.1.x86_64.rpm
has been replaced by
libjasper6-3.0.0-1.1.x86_64.rpm
Hello Felix,
Alas, tdelibs fails to build against jasper 3.0 :( E. Liddell
____________________________________________________
tde-devels mailing list -- devels(a)trinitydesktop.org
To unsubscribe send an email to devels-leave(a)trinitydesktop.org
Web mail archive available at https://mail.trinitydesktop.or
g/mailman3/hyperkitty/list/devels(a)trinitydesktop.org
7:45 p.m.
On 2022/02/18 01:41 AM, François Andriot wrote:
Le 16/02/2022 à 01:43, Felix Miata a écrit :
In Debian we build our own version of jasper 1.9:
https://mirror.git.trinitydesktop.org/gitea/TDE/extra-dependencies/src/bran…
Perhaps the same can be done for rpm distros.
Cheers
Michele
# zypper install trinity-desktop
..
Problem: nothing provides 'libjasper.so.4()(64bit)' needed by the to be installed
trinity-tdelibs-14.0.11-1.osstw.x86_64
Solution 1: do not install trinity-desktop-14.0.11-1.osstw.noarch
Solution 2: break trinity-tdelibs-14.0.11-1.osstw.x86_64 by ignoring some of its
dependencies
libjasper4-2.0.33-2.1.x86_64.rpm
has been replaced by
libjasper6-3.0.0-1.1.x86_64.rpm
6 Mar
6 Mar
6:21 p.m.
Felix Miata composed on 2022-02-15 19:43 (UTC-0500):
# zypper install trinity-desktop
...
Problem: nothing provides 'libjasper.so.4()(64bit)' needed by the to be installed
trinity-tdelibs-14.0.11-1.osstw.x86_64
Solution 1: do not install trinity-desktop-14.0.11-1.osstw.noarch
Solution 2: break trinity-tdelibs-14.0.11-1.osstw.x86_64 by ignoring some of its
dependencies
libjasper4-2.0.33-2.1.x86_64.rpm
has been replaced by
libjasper6-3.0.0-1.1.x86_64.rpm
I tried installing trinity-tdm on a TW installation that had had only xdm, and
none of Trinity. Installation count came to 57 packages, but "broken", because
libjasper4 is neither installed nor available. TDM doesn't appear broken in any
functional way, though as usual, I run it "themeless", with the default look
inherited from KDE that I consider to be a theme superior to all others I've been
exposed to.
Since I know nothing meaningful about building, I can't imagine why François
wasn't been able to build using libjasper6. :(
Also, on first attempt to start TDM (at boot), it doesn't, because it wants to
start X before /dev/dri/card0 exists:
# grep \(EE *old
[ 7.611] (EE) open /dev/dri/card0: No such file or directory
[ 7.611] (EE) open /dev/dri/card0: No such file or directory
[ 7.611] (EE) Screen 0 deleted because of no matching config section.
[ 7.611] (EE) Device(s) detected, but none match those in the config file.
[ 7.611] (EE)
[ 7.611] (EE) no screens found(EE)
Is this a case where KMS needs to be triggered early in boot? Is there some way to
delay TDM's attempt to get X started? I tried tdmrc OpenDelay=25 instead of 15,
but it didn't help, and neither StartAttempts=5 instead of 4.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
8:56 p.m.
On 2022/03/07 11:21 AM, Felix Miata wrote:
Felix Miata composed on 2022-02-15 19:43 (UTC-0500):
I may have mentioned this already, but the source code for jasper 1.9 is available on the
extra dependencies repo.
In debian we build this already. Not sure what is happening in the RPM world though.
https://mirror.git.trinitydesktop.org/gitea/TDE/extra-dependencies/src/bran…
Cheers
Michele
# zypper install trinity-desktop
...
Problem: nothing provides 'libjasper.so.4()(64bit)' needed by the to be installed
trinity-tdelibs-14.0.11-1.osstw.x86_64
Solution 1: do not install trinity-desktop-14.0.11-1.osstw.noarch
Solution 2: break trinity-tdelibs-14.0.11-1.osstw.x86_64 by ignoring some of its
dependencies
libjasper4-2.0.33-2.1.x86_64.rpm
has been replaced by
libjasper6-3.0.0-1.1.x86_64.rpm
I tried installing trinity-tdm on a TW installation that had had only xdm, and
none of Trinity. Installation count came to 57 packages, but "broken",
because
libjasper4 is neither installed nor available. TDM doesn't appear broken in any
functional way, though as usual, I run it "themeless", with the default look
inherited from KDE that I consider to be a theme superior to all others I've been
exposed to.
Since I know nothing meaningful about building, I can't imagine why François
wasn't been able to build using libjasper6. :(
Also, on first attempt to start TDM (at boot), it doesn't, because it wants to
start X before /dev/dri/card0 exists:
# grep \(EE *old
[ 7.611] (EE) open /dev/dri/card0: No such file or directory
[ 7.611] (EE) open /dev/dri/card0: No such file or directory
[ 7.611] (EE) Screen 0 deleted because of no matching config section.
[ 7.611] (EE) Device(s) detected, but none match those in the config file.
[ 7.611] (EE)
[ 7.611] (EE) no screens found(EE)
Is this a case where KMS needs to be triggered early in boot? Is there some way to
delay TDM's attempt to get X started? I tried tdmrc OpenDelay=25 instead of 15,
but it didn't help, and neither StartAttempts=5 instead of 4.
14 May
14 May
10:11 p.m.
Michele Calgaro via tde-devels composed on 2022-03-06 23:56 (UTC-0400):
Felix Miata wrote:
> Felix Miata composed on 2022-02-15 19:43
(UTC-0500):
>> # zypper install trinity-desktop
>> ...
>> Problem: nothing provides 'libjasper.so.4()(64bit)' needed by the to be
installed trinity-tdelibs-14.0.11-1.osstw.x86_64
>> Solution 1: do not install trinity-desktop-14.0.11-1.osstw.noarch
>> Solution 2: break trinity-tdelibs-14.0.11-1.osstw.x86_64 by ignoring some of
its dependencies
>> libjasper4-2.0.33-2.1.x86_64.rpm
>> has been replaced by
>> libjasper6-3.0.0-1.1.x86_64.rpm
> I tried installing trinity-tdm on a TW
installation that had had only xdm, and
> none of Trinity. Installation count came to 57 packages, but "broken",
because
> libjasper4 is neither installed nor available. TDM doesn't appear broken in any
> functional way, though as usual, I run it "themeless", with the default
look
> inherited from KDE that I consider to be a theme superior to all others I've
been
> exposed to.
> Since I know nothing meaningful about building, I
can't imagine why François
> wasn't been able to build using libjasper6. :(
I may have mentioned this already, but the source code
for jasper 1.9 is available on the extra dependencies repo.
In debian we build this already. Not sure what is happening in the RPM world though.
https://mirror.git.trinitydesktop.org/gitea/TDE/extra-dependencies/src/bran…
$MIRROR/opensuse/repositories/KDE:/KDE3/openSUSE_Tumbleweed/x86_64/libjasper4-2.0.14-1.47.x86_64.rpm
may be able to fill the bill, but having KDE3 repos enabled with TDE installations
could pose a problem, no?
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
10:41 p.m.
On Sat May 14 2022 22:11:39 Felix Miata wrote:
Michele Calgaro via tde-devels composed on 2022-03-06
23:56 (UTC-0400):
Would one of these from the TDE archive be suitable?
# find . -iname '*jasper*rpm'
./trinity/rpm/osstw/trinity-r14/RPMS/x86_64/libjasper-devel-2.0.14-3.19.1.x86_64.rpm
./trinity/rpm/osstw/trinity-r14/RPMS/x86_64/libjasper4-2.0.14-3.19.1.x86_64.rpm
./trinity/rpm/osstw/trinity-r14/RPMS/x86_64/jasper-2.0.14-3.19.1.x86_64.rpm
./trinity/rpm/osstw/trinity-r14/RPMS/i586/libjasper-devel-2.0.14-3.19.1.i586.rpm
./trinity/rpm/osstw/trinity-r14/RPMS/i586/jasper-2.0.14-3.19.1.i586.rpm
./trinity/rpm/osstw/trinity-r14/RPMS/i586/libjasper4-2.0.14-3.19.1.i586.rpm
--Mike
Felix Miata wrote:
$MIRROR/opensuse/repositories/KDE:/KDE3/openSUSE_Tumbleweed/x86_64/libjaspe
r4-2.0.14-1.47.x86_64.rpm may be able to fill the bill, but having KDE3
repos enabled with TDE installations could pose a problem, no? Felix Miata composed on 2022-02-15 19:43
(UTC-0500):
I may have mentioned this already, but the source code for jasper 1.9 is
available on the extra dependencies repo. In debian we build this
already. Not sure what is happening in the RPM world though.
https://mirror.git.trinitydesktop.org/gitea/TDE/extra-dependencies/src/br
anch/master/debian/jasper # zypper install trinity-desktop
...
Problem: nothing provides 'libjasper.so.4()(64bit)' needed by the to be
installed trinity-tdelibs-14.0.11-1.osstw.x86_64 Solution 1: do not
install trinity-desktop-14.0.11-1.osstw.noarch Solution 2: break
trinity-tdelibs-14.0.11-1.osstw.x86_64 by ignoring some of its
dependencies
libjasper4-2.0.33-2.1.x86_64.rpm
has been replaced by
libjasper6-3.0.0-1.1.x86_64.rpm
I tried installing trinity-tdm on a TW installation that had had only
xdm, and none of Trinity. Installation count came to 57 packages, but
"broken", because libjasper4 is neither installed nor available. TDM
doesn't appear broken in any functional way, though as usual, I run it
"themeless", with the default look inherited from KDE that I consider to
be a theme superior to all others I've been exposed to.
Since I know nothing meaningful about building, I can't imagine why
François wasn't been able to build using libjasper6. :(
15 May
15 May
7:04 p.m.
Mike Bird composed on 2022-05-14 22:41 (UTC-0700):
Felix Miata wrote:
>
$MIRROR/opensuse/repositories/KDE:/KDE3/openSUSE_Tumbleweed/x86_64/libjaspe
>r4-2.0.14-1.47.x86_64.rpm may be able to fill the bill, but having KDE3
> repos enabled with TDE installations could pose a problem, no?
Would one of these from the TDE archive be suitable?
# find . -iname '*jasper*rpm'
./trinity/rpm/osstw/trinity-r14/RPMS/x86_64/libjasper-devel-2.0.14-3.19.1.x86_64.rpm
./trinity/rpm/osstw/trinity-r14/RPMS/x86_64/libjasper4-2.0.14-3.19.1.x86_64.rpm
./trinity/rpm/osstw/trinity-r14/RPMS/x86_64/jasper-2.0.14-3.19.1.x86_64.rpm
./trinity/rpm/osstw/trinity-r14/RPMS/i586/libjasper-devel-2.0.14-3.19.1.i586.rpm
./trinity/rpm/osstw/trinity-r14/RPMS/i586/jasper-2.0.14-3.19.1.i586.rpm
./trinity/rpm/osstw/trinity-r14/RPMS/i586/libjasper4-2.0.14-3.19.1.i586.rpm
I see someone has put libjasper4-2.0.14-3.19.1 into the TW TDE repos, with no
evident packaging errors to install, and TDM & TDE are still working. :)
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
14 Sep
14 Sep
7:46 p.m.
New subject: [Fedora 37b] nothing provides 'libjasper.so.4
Felix Miata composed on 2022-02-15 19:43 (UTC-0400):
# zypper install trinity-desktop
...
Problem: nothing provides 'libjasper.so.4()(64bit)' needed by the to be installed
trinity-tdelibs-14.0.11-1.osstw.x86_64
Solution 1: do not install trinity-desktop-14.0.11-1.osstw.noarch
Solution 2: break trinity-tdelibs-14.0.11-1.osstw.x86_64 by ignoring some of its
dependencies
libjasper4-2.0.33-2.1.x86_64.rpm
has been replaced by
libjasper6-3.0.0-1.1.x86_64.rpm
Same problem now trying to upgrade Fedora 36 to 37 beta, keeping F36 tde packages
installed. I had to do
rpm -e --justdb --nodeps trinity-tdelibs
to force the upgrade to proceed. Is there a source for the required libjasper, or
preliminary builds for Fedora 37?
I've already done this on at least two systems in recent weeks, and have noted no
issues opening a TDE session from TDM.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
15 Sep
15 Sep
12:48 p.m.
New subject: [Fedora 37b] nothing provides 'libjasper.so.4
Le 15/09/2022 à 04:46, Felix Miata a écrit :
...
to force the upgrade to proceed. Is there a source for the required libjasper, or
preliminary builds for Fedora 37?
I've already done this on at least two systems in recent weeks, and have noted no
issues opening a TDE session from TDM.
Hello Felix,
thanks for reporting.
I'm currently building the 14.0.12 packages for Fedora 37 (beta), using
the patch from Slavek that allows tdelibs to build with Jasper3.
I'll let you know when packages are available.
François
7:17 p.m.
New subject: [Fedora 37b] nothing provides 'libjasper.so.4
On Thu, 15 Sep 2022 21:48:01 +0200
François Andriot <francois.andriot(a)libertysurf.fr> wrote:
Le 15/09/2022 à 04:46, Felix Miata a écrit :
It might be worth considering porting the jpeg 2000 support to the openjpeg
library (which is what the few other packages supporting this format seem to
be using now) and getting rid of the jasper dependency altogether.
Personally, I'd just drop the jpeg 2000 support altogether, since I've never seen
an image using it "in the wild" (it is *not* the same file format as ordinary
jpeg),
but others may have had different experiences.
E. Liddell
...
to force the upgrade to proceed. Is there a source for the required libjasper, or
preliminary builds for Fedora 37?
I've already done this on at least two systems in recent weeks, and have noted no
issues opening a TDE session from TDM.
Hello Felix,
thanks for reporting.
I'm currently building the 14.0.12 packages for Fedora 37 (beta), using
the patch from Slavek that allows tdelibs to build with Jasper3.
I'll let you know when packages are available. 
9:47 p.m.
New subject: [Fedora 37b] nothing provides 'libjasper.so.4
Anno domini 2022 Thu, 15 Sep 22:17:35 -0400
E. Liddell scripsit:
On Thu, 15 Sep 2022 21:48:01 +0200
François Andriot <francois.andriot(a)libertysurf.fr> wrote:
+1 jpeg 2000 never took off and with webp it'll never will.
Nik
Le 15/09/2022 à 04:46, Felix Miata a écrit :
It might be worth considering porting the jpeg 2000 support to the openjpeg
library (which is what the few other packages supporting this format seem to
be using now) and getting rid of the jasper dependency altogether.
Personally, I'd just drop the jpeg 2000 support altogether, since I've never
seen
an image using it "in the wild" (it is *not* the same file format as ordinary
jpeg),
but others may have had different experiences. ...
to force the upgrade to proceed. Is there a source for the required libjasper, or
preliminary builds for Fedora 37?
I've already done this on at least two systems in recent weeks, and have noted no
issues opening a TDE session from TDM.
Hello Felix,
thanks for reporting.
I'm currently building the 14.0.12 packages for Fedora 37 (beta), using
the patch from Slavek that allows tdelibs to build with Jasper3.
I'll let you know when packages are available.
E. Liddell
____________________________________________________
tde-devels mailing list -- devels(a)trinitydesktop.org
To unsubscribe send an email to devels-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydesk…
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
17 Sep
17 Sep
11:45 p.m.
New subject: [Fedora 37b] nothing provides 'libjasper.so.4
Le 15/09/2022 à 21:48, François Andriot a écrit :
Le 15/09/2022 à 04:46, Felix Miata a écrit :
> ...
>
> to force the upgrade to proceed. Is there a source for the required
> libjasper, or
> preliminary builds for Fedora 37?
>
> I've already done this on at least two systems in recent weeks, and
> have noted no
> issues opening a TDE session from TDM.
Hello,
The packages for Fedora 37 are available on the mirrors:
http://mirror.ppa.trinitydesktop.org/trinity/rpm/f37/
Installation procedure is the same as usual for Fedora.
Regards
François
798
days inactive
1012
days old
15 comments
7 participants
participants (7)
-
Andrew Randrianasulu -
Dr. Nikolaus Klepp -
E. Liddell -
Felix Miata -
François Andriot -
Michele Calgaro -
Mike Bird