Proposal: Stewardship Group / SIG for taking care of otherwise
"module-only" packages
by Fabio Valentini
Hi everybody,
In the past few weeks, it has come up regularly that future
"module-only" packages are orphaned (and hence will soon be retired),
and nobody stepped up to fix this issue - especially for non-leaf
packages. I don't think fedora as a project has a solution for this
yet.
I propose to create a "Stewardship" Group / SIG that will take care of
such packages - either until a new main maintainer steps up, or until
modularity matures enough so it won't be necessary anymore. (Or, until
it dies a quiet death, which is always a possibility.) However, I
think this is necessary until the situation stabilizes.
Comments and future contributors are very welcome.
Fabio
5 years, 1 month
mythes-eo package
by Carmen Bianca Bakker
Hello developers,
I have created a `mythes` and `hyphen` package for the Esperanto language.
Unfortunately, I am not a sponsored Fedora developer, and the package
doesn't seem like it'll be accepted unless I become sponsored.
Between all manner of tasks, I do not have the time to pursue becoming
sponsored. But even so I would like the package to enter Fedora. It
likely requires zero maintenance.
Is there someone who would like to take this package from me?
The bug report is:
https://bugzilla.redhat.com/show_bug.cgi?id=1644268
Many thanks and with kindness,
Carmen
5 years, 1 month
strange failures with gcc-9.0.1-0.11.fc31.x86_64
by Zbigniew Jędrzejewski-Szmek
Hi,
I'm trying to compile systemd in koji and mock, and I'm getting suspicious
crashes...
$ valgrind x86_64-redhat-linux-gnu/test-terminal-util
/* test_default_term_for_tty */
...
/* test_read_one_char */
==21== Invalid read of size 4
==21== at 0x48C09EC: fputs (in /usr/lib64/libc-2.29.9000.so)
==21== by 0x109301: UnknownInlinedFun (test-terminal-util.c:43)
==21== by 0x109301: main (test-terminal-util.c:80)
==21== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==21==
==21==
==21== Process terminating with default action of signal 11 (SIGSEGV)
The problem is at this line, there is just a call to (a function which
transitively calls) mkostemp(). It seems like the inlining is somehow
going wrong.
Strangely, gdb also crashes:
$ gdb x86_64-redhat-linux-gnu/test-terminal-util
GNU gdb (GDB) Fedora 8.3.50.20190321-3.fc31
...
Reading symbols from x86_64-redhat-linux-gnu/test-terminal-util...
(gdb) r
Starting program: /builddir/build/BUILD/systemd-49bd196d693efe0acfc8d56c4e3d8f7ba9f91b5d/x86_64-redhat-linux-gnu/test-terminal-util
Missing separate debuginfos, use: dnf debuginfo-install glibc-2.29.9000-8.fc31.x86_64
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
/* test_default_term_for_tty */
...
/* test_read_one_char */
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7e759ec in fputs () from /lib64/libc.so.6
Segmentation fault (core dumped)
There also are compilation failures related to inlining, when I disable LTO:
In file included from ../src/basic/macro.h:549,
from ../src/basic/alloc-util.h:9,
from ../src/network/networkd-link.c:9:
In function ‘link_enable_ipv6’,
inlined from ‘link_set_mtu’ at ../src/network/networkd-link.c:1483:16:
../src/basic/log.h:104:9: error: ‘%s’ directive argument is null [-Werror=format-overflow=]
104 | log_internal_realm(LOG_REALM_PLUS_LEVEL(LOG_REALM, (level)), __VA_ARGS__)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/shared/log-link.h:21:25: note: in expansion of macro ‘log_internal’
21 | log_internal(level, error, __FILE__, __LINE__, __func__, ##__VA_ARGS__); \
| ^~~~~~~~~~~~
../src/shared/log-link.h:33:50: note: in expansion of macro ‘log_link_full’
33 | #define log_link_warning_errno(link, error, ...) log_link_full(link, LOG_WARNING, error, ##__VA_ARGS__)
| ^~~~~~~~~~~~~
../src/network/networkd-link.c:324:17: note: in expansion of macro ‘log_link_warning_errno’
324 | log_link_warning_errno(link, r, "Cannot %s IPv6 for interface %s: %m",
| ^~~~~~~~~~~~~~~~~~~~~~
../src/network/networkd-link.c: In function ‘link_set_mtu’:
../src/network/networkd-link.c:324:79: note: format string is defined here
324 | log_link_warning_errno(link, r, "Cannot %s IPv6 for interface %s: %m",
| ^~
The argument is field in a structure, and when the structure is
created, it is always set. It's hard to say for sure that it's never
null, but I think gcc must be confused when it says it's *always* null.
The same rpm compiles fine with gcc-9.0.1-0.8.fc30, gcc-9.0.1-0.8.fc31.
I'm writing to the mailing list instead of opening a bug because I'm not
really sure if gcc is at fault, or if systemd code is somehow buggy in
a non-obvious way... Has anyone else seen similar failures with the
latest gcc build?
Zbyszek
example failed koji scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=33792874
5 years, 1 month
Orphaning python-Lektor
by Charalampos Stratakis
Not interested anymore in this package, feel free to reach me out if you'd like to take it, I'll orphan it this week.
It will probably need a re-review to rename it to 'lektor' as it's mainly an application.
It's sort of active on github [0]. More info [1].
[0] https://github.com/lektor/lektor
[1] https://www.getlektor.com/
--
Regards,
Charalampos Stratakis
Software Engineer
Python Maintenance Team, Red Hat
5 years, 1 month
fedpkg clone lollypop ... Permission denied (publickey),
after copying my fedora cert to new vmware with f30
by Martin Gansser
Hi,
i get the error after copying my home folder /home/martin from a vmware with f29 to a new vmware with f30.
Cloning into 'lollypop'...
martin(a)pkgs.fedoraproject.org: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Could not execute clone: Failed to execute command.
What have i to do, that the fedpkg clone lollypop works again ?
Thanks
Martin
5 years, 1 month
Strange C++ error with GCC 9.0.1
by Peter Lemenkov
Hello All!
I cannot build SIPp anymore. It fails with a very cryptic (for me) message:
https://koji.fedoraproject.org/koji/taskinfo?taskID=33763853
```
g++ -DHAVE_CONFIG_H -DUSE_OPENSSL -DPCAPPLAY -DRTP_STREAM -DUSE_SCTP
-DHAVE_EPOLL -I. -I./include -D__LINUX -I./include -Wall -pedantic
-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
-Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong
-grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
-c -o src/sipp-sipp.o `test -f 'src/sipp.cpp' || echo
'./'`src/sipp.cpp
In file included from ./include/strings.hpp:24,
from ./include/sipp.hpp:484,
from src/sipp.cpp:41:
/usr/include/c++/9/cstddef:52:8: error: expected unqualified-id before
string constant
52 | extern "C++"
| ^~~~~
make[1]: *** [Makefile:1768: src/sipp-sipp.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/home/petro/rpmbuild/BUILD/sipp-3.5.2'
make: *** [Makefile:830: all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.Y5CFt4 (%build)
```
^^^ That's exactly where I'm stuck now. This is how my
`/usr/include/c++/9/cstddef` looks like:
* https://github.com/gcc-mirror/gcc/blob/25694c85/libstdc%2B%2B-v3/include/...
And I tend to think that this issue is related to this commit:
* https://github.com/gcc-mirror/gcc/commit/038feca5beacbe36e28680c8e1a8af83...
--
With best regards, Peter Lemenkov.
5 years, 1 month
New Golang Packaging Guidelines: Feedback needed and appreciated
by Robert-André Mauchin
Hello Fedora people,
As you may or may not know, currently applied Golang packaging guidelines
have always been simply a « draft ». Part of the new Go SIG mission is to
update ours best practices and tooling. As such, Nicolas Mailhot designed a
new set of macros based on lua script to improve our current situation. As a
result, we needed to draft new guidelines to reflect the future implementation
of these macros.
I have written these new guidelines and I'd like to ask for your help in
order to review them: both from current Go SIG packagers point of view and
from novices in the matter, in order to make sure they are clear and
understandable enough for everyone.
I have uploaded a mirror of the Guidelines on my FedoraPeople space:
https://eclipseo.fedorapeople.org/guidelines/packaging-guidelines/Golang/
Please, if you have 10 mn to spare, read them and send me feedback. If you
wish you can also directly send me a Merge Request on Pagure:
https://pagure.io/fork/eclipseo/packaging-committee/ (branch
implement_golang_guidelines).
Best regards,
Robert-André
5 years, 1 month
