Wikipedia:Reference desk/Archives/Computing/2019 May 7
| Computing desk | ||
|---|---|---|
| < May 6 | << Apr | May | Jun >> | May 8 > |
| Welcome to the Wikipedia Computing Reference Desk Archives |
|---|
| The page you are currently viewing is an archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages. |
May 7
[edit]Ubuntu packages
[edit]Firefox has run into certificate signing troubles and released a fix via 66.0.4 on May 5, last Sunday (Mozilla blog post).
However, right now (19:16, 7 May 2019 (UTC)), my Firefox 66.0.3 on Ubuntu 16 is squeaking (since the fix is not here), and it is the latest version available in the package manager. Any clues to why? I have no foggy idea of how the release flows from Mozilla towards the end customer, but it's a super-duper-high priority update and the Firefox team probably has the VIP card to push their updates to Ubuntu package maintainers. TigraanClick here to contact me 19:16, 7 May 2019 (UTC)
- I think I saw something about Ubuntu pushing a fix a few hours ago, so try now. 67.164.113.165 (talk) 19:16, 8 May 2019 (UTC)
- Yeah, I'm good now, but the more general question remains: why does it take more than a day to push that? What is the process? TigraanClick here to contact me 08:32, 9 May 2019 (UTC)
- I believe this is the general process to update packages on stable releases of Ubuntu [1]. This seems to be the Ubuntu package details for the version you refer to [2] including maintainers etc. It strikes me that this may be a "super-duper-high priority update" but was probably not a critical update since AFAIK it wasn't some major security problem like a remote compromise situation. Actually it wasn't a security problem at all AFAIK ignoring people who did stupid things to re-enable their add-ons or those who felt they needed some add-on for their security (which Mozilla and Canonical probably respect but don't treat quite the same as an actual security hole in the software). This may be why urgency is marked as medium in the changelog [3]. (Although to be fair, the last critical was in 2006 and high in 2005. Lows continued for a while but even they seem to have been abandoned.) Nil Einne (talk) 18:58, 12 May 2019 (UTC)
- First link is the charm. Thanks! TigraanClick here to contact me 12:00, 13 May 2019 (UTC)
- I believe this is the general process to update packages on stable releases of Ubuntu [1]. This seems to be the Ubuntu package details for the version you refer to [2] including maintainers etc. It strikes me that this may be a "super-duper-high priority update" but was probably not a critical update since AFAIK it wasn't some major security problem like a remote compromise situation. Actually it wasn't a security problem at all AFAIK ignoring people who did stupid things to re-enable their add-ons or those who felt they needed some add-on for their security (which Mozilla and Canonical probably respect but don't treat quite the same as an actual security hole in the software). This may be why urgency is marked as medium in the changelog [3]. (Although to be fair, the last critical was in 2006 and high in 2005. Lows continued for a while but even they seem to have been abandoned.) Nil Einne (talk) 18:58, 12 May 2019 (UTC)
- Yeah, I'm good now, but the more general question remains: why does it take more than a day to push that? What is the process? TigraanClick here to contact me 08:32, 9 May 2019 (UTC)