it seems to be a week of SIG announcements, so why shouldn't I share that
we also have Rust SIG <https://fedoraproject.org/wiki/SIGs/Rust>.
At this point we have over 400 crates packaged, few applications like
ripgrep, tokei, stratisd and more.
Feel free to stop by and don't hesitate to ping me ;)
P.S. I'm going to Flock this year, so let me know if you would like to meet
and work on.
The elfutils tools can demangle C++ symbols through the standard
_cxa_demangle interface. The elfutils tools are written in C and
so simply link with -lstdc++ to get access to __cxa_demangle.
There is a BuildRequires: libstdc++-devel in the elfutils.spec.
But it looks like that isn't enough anymore to pull in libstdc++.so
to build against.
It looks like that is provided through a symlink in gcc-c++.
Should the elfutils.spec just BuildRequires: gcc-c++ instead of
libstdc++-devel? Or is this a packaging/requires issue somewhere
Peter Lemenkov  is an active packager (he submitted a new erlang
build to bodhi an hour ago) but I was unable to contact him for the last
I first "encountered" him when he used his rights as provenpackager to
merge some PRs on the elixir package, without thoughts for the ongoing
discussions. He even submitted builds to bodhi but we *never* got any
message from him. I'm now trying to contact him over RHBZ #1434779 
but am still unable to get a response.
Does anyone know how to contact him ? Mail, IRC, RHBZ, Bodhi and src.fp.o
I've just got 20 bugs auto-filed against packages which I co-maintain
and that is just for packages starting with the letter 'a'.
A quick check shows that these are all caused by a missing
BuildRequires on gcc / g++ related to:
I'm not sure if this means that the FTBFS script has been run before
all the automatic fixing which was planned for this was in place;
or if this means that the automatic fixing missed many many
packages, but either way something needs to happen here, the amount
of work now being pushed onto packagers caused by:
Is unacceptable IMHO.
If the FTBFS script has ran too early, all the FTBFS bugs need to be
closed and the FTBFS script has to be run again later.
If the automatic BuildRequires fixing script missed all these, then
I suggest that:
Gets reverted for now and we again close all the FTBFS bugs and
rerun the script for them after doing a fresh build with the
buildroot restored as it was.