| Summary: | =app-cdr/k3b-2.0.2-r4 - QA Notice: Package triggers severe warnings which indicate that it may exhibit random runtime failures. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | John (EBo) David <ebo> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | media-optical |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | required emerge info | ||
> QA Notice: Package triggers severe warnings which indicate that it
> may exhibit random runtime failures.
> ...
> Please do not file a Gentoo bug and instead report the above QA
> issues directly to the upstream developers of this software.
Thanks for reporting. But portage told you where it have to be reported.
|
Created attachment 352800 [details] required emerge info THis is a trivial thing, but I thought I would mention the QA notices seen when compiling k3b: * QA Notice: Package triggers severe warnings which indicate that it * may exhibit random runtime failures. * /var/tmp/portage/app-cdr/k3b-2.0.2-r4/work/k3b-2.0.2/libk3b/tools/k3biso9660.cpp:105:136: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] * /var/tmp/portage/app-cdr/k3b-2.0.2-r4/work/k3b-2.0.2/libk3b/tools/k3biso9660.cpp:570:77: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] * /var/tmp/portage/app-cdr/k3b-2.0.2-r4/work/k3b-2.0.2/libk3b/tools/k3biso9660.cpp:571:77: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] * /var/tmp/portage/app-cdr/k3b-2.0.2-r4/work/k3b-2.0.2/libk3b/tools/k3biso9660.cpp:572:77: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] * /var/tmp/portage/app-cdr/k3b-2.0.2-r4/work/k3b-2.0.2/libk3b/tools/k3biso9660.cpp:579:84: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] These are minor to trivial, but I have had such things bight me in the past, and thought I would put in a ticket to have them fixed.