How do bug upgrades work in Trisquel?
- Login o registrati per inviare commenti
One of my favorite programs, Jitsi, is still near unusable on Trisquel. Or at least the repo version is near unusable. There are already a couple of other threads here in the Trisquel forum about Jitsi crashing.
The Jitsi version in the Trisquel repo is 2.4.4997
But if you look here: https://download.jitsi.org/jitsi/debian/
You'll see there are several new stable releases that have since come out. Now, I know that we won't get any of them until the next release of Trisquel, but surely, the crashing bug has been addressed by now. Why no bug fix to our version of Jitsi? How does that process "work?"
Are we doomed to have a crummy unusable version of Jitsi in our repos until the next release of Trisquel?
Your question is really one of how Ubuntu's updates work. Trisquel pulls in the updates. If you experience crashes, report them as bugs so that they can be fixed in maintenance updates. But generally, you're right: Don't expect major updates between versions. It's why I like Trisquel.
I am a translator!
compile it! Jitsi wasn't included in Debian 8. I had to compile it. Sid's version is 2.4. The latest stable source code is 2.8.
There is no need to compile. The wanted .deb package can be downloaded from https://download.jitsi.org/jitsi/debian/ and installed (with 'sudo dpkg -i' or graphically with GDebi). The package creates /etc/apt/sources.list.d/jitsi.list, hence an automatic upgrade whenever a new version is released.
Do you have any idea why it's no longer in Debain 8 repo? It's also not in Ubuntu Vivid. I'm worried that maybe some part of Jitsi is no longer free software or something.
I am a translator!
Yes Trisk Spellian -> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760853
Nothing there mentions a freedom issue. Only an incompatibility with the version of a dependency that currently is in Debian's repository.
I am a translator!
The question was: Do you have any idea why it's no longer in Debain 8 repo?
The answer was: Yes Trisk Spellian -> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760853
There was also a second question, which banana answered.
I am a translator!
My rule is: whatever software external to the OS repository goes compiled! I don't trust external debs becuse I'm maaaaaaad and paranoiiiiid :P
Jetsi's .deb packages are provided by the same developers who cook the source code you compile. You need not trust any third person.
I am a translator!
Yes. And the debs in Ubuntu are cooked by the same people who provide the sourcecode of the same. I trust their sourcecode. I don't trust their debs. Who guarantees you that nothing was added to the deb?
And the debs in Ubuntu are cooked by the same people who provide the sourcecode of the same.
No, they are not.
"Who guarantees you that nothing was added to the deb?"
i wonder if there’s some kind of checksum a compiler can generate when there’s specific source code that you can compare to the binary?
anyone tried this before?
- Login o registrati per inviare commenti