[gentoo-user] libffi-3.3.0-rc0

[gentoo-user] libffi-3.3.0-rc0

[Ian Zimmerman]

After my weekly webrsync this morning, emerge -p showed me a whale of an
upgrade, including rebuilding both pythons, llvm and firefox, on top of
the legitimate and long overdue texlive update.  It would have taken
half a day even on a reasonably capable desktop.

Inspecting the -p output I blame libffi, and indeed using the
package.mask file to block its new version I got a more manageable
upgrade.  My question is, how come a -rc0 version got unkeyworded?  Does
this normally happen or was it a mistake?

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.

Re: [gentoo-user] libffi-3.3.0-rc0

[Franz Fellner]

[-- Attachment #1: Type: text/plain, Size: 905 bytes --]

No mistake:
https://bugs.gentoo.org/694978

Am Sa., 28. Sept. 2019 um 19:54 Uhr schrieb Ian Zimmerman <
itz@very.loosely.org>:

> After my weekly webrsync this morning, emerge -p showed me a whale of an
> upgrade, including rebuilding both pythons, llvm and firefox, on top of
> the legitimate and long overdue texlive update.  It would have taken
> half a day even on a reasonably capable desktop.
>
> Inspecting the -p output I blame libffi, and indeed using the
> package.mask file to block its new version I got a more manageable
> upgrade.  My question is, how come a -rc0 version got unkeyworded?  Does
> this normally happen or was it a mistake?
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for no-use.mooo.com.
>
>

[-- Attachment #2: Type: text/html, Size: 1378 bytes --]