| Summary: | Maintainership request: dev-lang/regina-rexx | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | V.Ralf Hagen (dingo) <ralf.hagen> |
| Component: | Current packages | Assignee: | Proxy Maintainers <proxy-maint> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | giuseppe, pacho, proxy-maint, ralf.hagen |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 515944 | ||
|
Description
V.Ralf Hagen (dingo)
2016-08-25 12:10:03 UTC
Thanks Ralf. I would really appreciate your effort. If you need any support I may be able to give, please contact me. I'm in the CC list of this thread. G. Vitillaro. Ok, looks like the newest version needs less fixing than expected. Nevertheless, I see straight away: * QA Notice: Package triggers severe warnings which indicate that it * may exhibit random runtime failures. * ./regutil/regini.c:547:58: warning: implicit declaration of function ‘clock’ [-Wimplicit-function-declaration] * Please do not file a Gentoo bug and instead report the above QA * issues directly to the upstream developers of this software. * Homepage: http://regina-rexx.sourceforge.net * QA Notice: Pre-stripped files found: * /usr/share/Regina-REXX/addons/librxtest2.so * /usr/share/Regina-REXX/addons/librxtest1.so * /usr/share/Regina-REXX/addons/libregutil.so * /usr/lib64/libregina.so.3.9 * /usr/bin/regina * /usr/bin/rxstack * /usr/bin/rxqueue * /usr/bin/rexx So, a) missing #include, b) you need to disable stripping in the package build system. Looking at the ebuild, a few suggestions: 1) update to EAPI=6, 2) use MY_P to commonize SRC_URI and S, 3) probably look into moving 'tc-export CC' into src_compile() ;-). We no longer use these bugs. See: https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/User_Guide#Taking_over_an_existing_package Long story short: 1. If your request has been fulfilled already and you're the maintainer, ignore this. 2. If you have submitted the ebuilds separately, we'll handle it there. If that's via a bug, please make sure that proxy-maint@ is in CC. Feel free to ping us if things aren't moving forward for a long time. 3. If you haven't submitted anything yet, please submit a meaningful change to the package (bugfix, version bump, ebuild update...) along with the maintainer update and you'll become the maintainer when we merge it. Sorry for the trouble. |