| 1 |
I get notifications from firefox that an updates are available.
|
| 2 |
|
| 3 |
Once I wondered if it would be able to update and I pushed the update
|
| 4 |
button, it failed (likely in escalading the auths, as Andreas pointed).
|
| 5 |
|
| 6 |
To get rid of long compilation of firefox, I use www-client/firefox-bin.
|
| 7 |
The emerged binary is firefox-bin (rather than firefox as it would be
|
| 8 |
after local compilation).
|
| 9 |
|
| 10 |
In firefox preferences, I can disable firefox updates (so that it
|
| 11 |
doesn't bother for newer versions available).
|
| 12 |
|
| 13 |
Fosco
|
| 14 |
|
| 15 |
Il 12/11/20 08:28, Andreas Fink ha scritto:
|
| 16 |
> On Thu, 12 Nov 2020 07:55:18 +0100 |
| 17 |
> n952162 <n952162@×××.de> wrote: |
| 18 |
> |
| 19 |
>> I was just informed by firefox on one of my gentoo machines that firefox |
| 20 |
>> has updated, I need to restart. |
| 21 |
>> |
| 22 |
>> I no longer find an option to disable automatic update. Is there no hope? |
| 23 |
>> |
| 24 |
>> And do I have to go through another 18 hour firefox emerge to get rid of |
| 25 |
>> their "update"? Or is their binary sitting somewhere different from |
| 26 |
>> "our" binary? |
| 27 |
>> |
| 28 |
>> Oh! Can I just remove their binary and do a resume-emerge? |
| 29 |
>> |
| 30 |
>> |
| 31 |
> When firefox is updated via emerge while it is still running, this |
| 32 |
> update is recognised by the running instance and it will tell you that |
| 33 |
> firefox was updated and needs a restart. No automatic update happened |
| 34 |
> as you assume, it was all done by the package manager. |
| 35 |
> If you insist, you can check the binary that is currently running, and |
| 36 |
> you will most certainly find out that it is not writeable by your user |
| 37 |
> account, i.e. not by the user that is running firefox: |
| 38 |
> pgrep -a firefox |
| 39 |
> |
| 40 |
> Cheers |
| 41 |
> Andreas |
| 42 |
> |
Archives