17 Mar
2016
17 Mar
'16
noon
On Thursday 17 March 2016 08:35:32 deloptes wrote:
Michele Calgaro wrote:
Why not just use Slávek's Preliminary Stable Builds repository instead of the
ones you have? It would solve your problem immediately for very little
effort. I switched some while ago because I wanted a patch fast and have
never looked back. It is great! You get exactly what will be going into
14.0.4, but you get it sooner. And come the release of 14.0.4 you won't need
to upgrade because you will already have it. Note the "Stable" in the
name. ;-)
Lisi
On 03/17/2016 02:09 AM, deloptes wrote:
Hi Michele,
I use this - not sure what it is exactly, but I think this is the official
repo
deb http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/debian
jessie main
deb-src http://mirror.ppa.trinitydesktop.org/trinity/trinity-r14.0.0/debian
jessie main
deb
http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/debi
an jessie main
deb-src
http://mirror.ppa.trinitydesktop.org/trinity/trinity-builddeps-r14.0.0/debi
an jessie main
I don't know what is best to wait or to recompile, because its the libs and
there is a lot of packages produced/dependant.
Is it possible to get/download this package after it was build on Slaveks
stable build as deb file?
thanks in advance Hi
I filed a bug 2613
(https://bugs.trinitydesktop.org/show_bug.cgi?id=2613)
This is really blocking me ATM, hence the high prio I set. How does the
fix cycle looks like from time line perspective?
I'm considering downloading the source and patching myself.
thanks in advance
Hi Deloptes,
I will fix this (including support for Z format) during the weekend or
next week at most. In terms of fix cycle, it depends on what distro and
repository you use. If you are on Debian/Ubuntu and use Slavek's
preliminary stable build, you can expect the fix to be available right
after the fix (just the time to recompile on Slavek's builder). If you
are on Debian/Ubuntu and use the nighly builds, same thing. If you use
other PPA or other distros, you will probably get the fix with the next
R14.0.4 release (probably 2-3 months later). If you need the fix
urgently, you will probably have to download the fix from GIT and then
rebuild locally and then use that until the next maintenance release.
Cheers
Michele