Re: [gentoo-dev] gcc-11 enters ~arch tree
> On 27 Apr 2021, at 19:22, Sergei Trofimovich wrote: > > Today gcc-11.1.0 released upstream and was added to ::gentoo as: > > https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cc068d96fb49e308456cbe944fb29b1f78e6ad5c > And same day too! > [snip] > As usual if you can't figure out what is wrong with your package > pull in toolchain@ to the bug and we'll get to the bottom of it. Just wanted to say thanks for always being there to sort out things like this, cheers for that. Let’s hope we have a smoother time than 10, but I think some of us are more braced for it either way... > > Good luck! > > -- > > Sergei > Best, sam signature.asc Description: Message signed with OpenPGP
[gentoo-dev] Last-rites: app-misc/mediacrush-cli
# Andreas Sturmlechner (2021-04-27) # Unmaintained, dead service, EAPI-5. # Removal on 2021-05-14 app-misc/mediacrush-cli signature.asc Description: This is a digitally signed message part.
[gentoo-dev] gcc-11 enters ~arch tree
Today gcc-11.1.0 released upstream and was added to ::gentoo as: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cc068d96fb49e308456cbe944fb29b1f78e6ad5c User-visible changes are nicely described in upstream porting doc: https://gcc.gnu.org/gcc-11/porting_to.html A few highlights I personally encountered are: - use -std=gnu++17 instead of -std=gnu++14 - ordered pointer comparison with integer (like int *p; 'p > 0') - dynamic exception specifications - gcc now enforces that comparison objects be invocable as const - header dependency changes On top of that: - -fipa-modref (enabled by default) might expose latent bugs in existing programs. -fno-ipa-modref should be a quick hack to check the hypothesis. Failures don't look widespread, thus gcc-11 should be fine to use as a default compiler. Check out known bugs and workarounds on gcc-11 tracker: https://bugs.gentoo.org/show_bug.cgi?id=gcc-11 Gentoo Toolchain wiki page for common fixes (nothing there so far): https://wiki.gentoo.org/wiki/Project:Toolchain#gcc-11 As usual if you can't figure out what is wrong with your package pull in toolchain@ to the bug and we'll get to the bottom of it. Good luck! -- Sergei
[gentoo-dev] last-rite: dev-java/helpgui, dev-java/higlayout
# Miroslav Šulc (2021-04-27) # library with no consumer # removal in 30 days # see bug: https://bugs.gentoo.org/786117 dev-java/helpgui # Miroslav Šulc (2021-04-27) # library with no consumer # removal in 30 days # see bug: https://bugs.gentoo.org/786120 dev-java/higlayout
[gentoo-dev] last-rite: dev-java/hamcrest-integration
# Miroslav Šulc (2021-04-27) # library with no consumer # removal in 30 days # see bug: https://bugs.gentoo.org/786096 dev-java/hamcrest-integration
[gentoo-dev] last-rite: dev-java/fscript, dev-java/fastinfoset
# Miroslav Šulc (2021-04-27) # library with no consumer # removal in 30 days # see bug: https://bugs.gentoo.org/786090 dev-java/fscript # Miroslav Šulc (2021-04-27) # library with no consumer # removal in 30 days # see bug: https://bugs.gentoo.org/786087 dev-java/fastinfoset
[gentoo-dev] last-rite: dev-java/ehcache
# Miroslav Šulc (2021-04-27) # library with no consumer # removal in 30 days # see bug: https://bugs.gentoo.org/785985 dev-java/ehcache
[gentoo-dev] Re: [gentoo-dev-announce] [GURU] Bug mail now directed to guru-bugs@g.o
On martedì 27 aprile 2021 10:12:09 CEST Michał Górny wrote: > not to mention someone suddenly starting to file such a large > number of bugs without any heads up. Here are the heads up: https://archives.gentoo.org/gentoo-dev/message/ 9dcfdcd82b774ac812bdb1e7b7fbd396 https://archives.gentoo.org/gentoo-dev/message/ 59efe56d47253521c514d11039e3ff1b
[gentoo-dev] [GURU] Bug mail now directed to guru-bugs@g.o
Hello, TL;DR: all new bugs related to packages in GURU should be assigned/CC-ed to guru-bugs@g.o rather than guru@g.o. The new alias is entirely opt- in, and people interested in bug mail should watch it via Bugzilla's 'email preferences'. The recent tinderboxing effort against GURU packages has caused tons of mail to be delivered to GURU contributor's mailboxes. I am sorry about that, I do realize that you never expected that signing up for GURU would result in getting hundreds of mails every day. Let's be honest -- when I set up the mail aliases for GURU, I wasn't sure the project would catch, not to mention someone suddenly starting to file such a large number of bugs without any heads up. Resolving this is a non-trivial problem. While in Gentoo the amount of bug spam is reduced by assigning them directly to package maintainers, GURU is generally a 'free for all' project. While some of the contributors are listing themselves as maintainers of individual packages, we generally assume anyone can fix anything and FWICS there are a few people who actually actively work on resolving bugs everywhere (thank you!). For this reason, I've decided to create a new opt-in mail alias, guru- bugs@.g.o. All new package bugs should either be assigned to this alias, or CC-ed to it (if assigning to actual maintainers). The previous aliases should only be used for the rare need of actually reaching all people in the project. I've 'reassigned' all existing bugs to the new alias to cease the further bug spam. Actually, I've just changed the email address of the old Bugzilla account to avoid additional mails about reassignment. If you're interested in following the bug mail for GURU, please use the watching feature found in Bugzilla's 'Email Preferences'. Thank you for your work on GURU! -- Best regards, Michał Górny
