The following packages have been failing to build on Factory for more than 30 days. This is a reminder for anybody that could be interested in any of them. Any package failing to build for more than 100 days will be dropped from openSUSE. - libgcj43 Fails for 277 days: undefined reference to `__cxa_call_unexpected' - elilo Fails for 92 days: undefined reference to `__stack_chk_fail_local' (New upstream version 3.14 available) - opensuse-manuals_ru Fails for 86 days: java 1.7 breaks it - selinux-policy Fails for 74 days: error(s) encountered while parsing configuration (Different changes in devel project (since 6 months)) - libgcj41 Fails for 47 days: java test cases... - compiz Fails for 44 days: kwin changes - kdegraphics3 Fails for 42 days: gphoto update (Current sources were declined: request 138654) - xerces-j2-bootstrap Fails for 33 days: temporary failure - hawk Fails for 33 days: cannot load such file -- gettext/tools/rgettext (rails 2 vs rails 3?) - python-tagpy Fails for 33 days: taglib update - rubygem-webyast-time Fails for 31 days: Missing partial shared/online_help (Different changes in devel project (since 23 days)) - ccscript3 Fails for 30 days: undefined reference to `main' (Request 139531 to network:telephony) - iscsitarget Fails for 30 days: kernel 3.6 This is a test. Please give some feedback. Anything to improve? Did this email actually helped you? The email was sent BCC to the package maintainers I could identify. I couldn't identify one clear one for ccscript3 and sent it to the latest .changes entry. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Sat, 27 Oct 2012 12:46:29 +0100 Cristian Morales Vega wrote:
- opensuse-manuals_ru Fails for 86 days: java 1.7 breaks it
I don't think this is a real problem. The package is built noarch. And it is buit successfully for i586. So we have it in repository any way. https://build.opensuse.org/package/show?package=opensuse-manuals_ru&project=openSUSE%3AFactory -- WBR Kyrill
Am 27.10.2012 18:32, schrieb Kyrill Detinov:
On Sat, 27 Oct 2012 12:46:29 +0100 Cristian Morales Vega wrote:
- opensuse-manuals_ru Fails for 86 days: java 1.7 breaks it
I don't think this is a real problem. The package is built noarch. And it is buit successfully for i586. So we have it in repository any way. https://build.opensuse.org/package/show?package=opensuse-manuals_ru&project=openSUSE%3AFactory
If java 1.7 breaks fop on x86_64, it *is* a problem. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Sat, 27 Oct 2012 19:27, Stephan Kulow
Am 27.10.2012 18:32, schrieb Kyrill Detinov:
On Sat, 27 Oct 2012 12:46:29 +0100 Cristian Morales Vega wrote:
- opensuse-manuals_ru Fails for 86 days: java 1.7 breaks it
I don't think this is a real problem. The package is built noarch. And it is buit successfully for i586. So we have it in repository any way. https://build.opensuse.org/package/show?package=opensuse-manuals_ru&project=openSUSE%3AFactory
If java 1.7 breaks fop on x86_64, it *is* a problem.
But where exactly? Java 1.7, the toolchain used to build the package, or the sourcefiles of the package, here: opensuse-manuals_ru. This rises a harsh question: why does java balk just at 64bit *-ru ? If the root of the troubles is not in the toolchain (inc. java), are the sources of the manual encoded right? (ONLY UTF8 should be allowed) The ONE time I had trouble with 64bit and no trouble with 32bit, was caused by wrong Byte-Order-Marks in UTF16 encoded files, that where ignored by the tools used. -- Yamaban. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 27 октября 2012 20:22:16 Yamaban wrote:
If the root of the troubles is not in the toolchain (inc. java), are the sources of the manual encoded right? (ONLY UTF8 should be allowed)
The ONE time I had trouble with 64bit and no trouble with 32bit, was caused by wrong Byte-Order-Marks in UTF16 encoded files, that where ignored by the tools used.
enca log http://susepaste.org/42452143 -- Friendly openSUSE Community -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Sun, 28 Oct 2012 08:09, EGD
On 27 октября 2012 20:22:16 Yamaban wrote:
If the root of the troubles is not in the toolchain (inc. java), are the sources of the manual encoded right? (ONLY UTF8 should be allowed)
The ONE time I had trouble with 64bit and no trouble with 32bit, was caused by wrong Byte-Order-Marks in UTF16 encoded files, that where ignored by the tools used.
enca log http://susepaste.org/42452143
Thanks for the log, the lines with: - Doubly-encoded to UTF-8 from ISO-8859-5, - Mixed line terminators, - Unrecognized encoding, - Surrounded by/intermixed with non-text data, are the candidates for trouble. The XML spec calls for a declarative header UTF8, esp. "Unrecognized encoding" should never happen. "Double encoding" is just bad, cleanup is advised. "Mixed line terminators" is bad form, but most tools can handle that. "Surrounded by/intermixed with non-text data" ??? Please cleanup, maybe even per hand. -- Yamaban.
On Sat, Oct 27, 2012 at 07:27:17PM +0200, Stephan Kulow wrote:
Am 27.10.2012 18:32, schrieb Kyrill Detinov:
On Sat, 27 Oct 2012 12:46:29 +0100 Cristian Morales Vega wrote:
- opensuse-manuals_ru Fails for 86 days: java 1.7 breaks it
I don't think this is a real problem. The package is built noarch. And it is buit successfully for i586. So we have it in repository any way. https://build.opensuse.org/package/show?package=opensuse-manuals_ru&project=openSUSE%3AFactory
If java 1.7 breaks fop on x86_64, it *is* a problem.
On the other hand using a recursion in Java is probably the symptom of bad design, causing StackOverflowError. From my POW fop is what is broken ... BTW: I've already sent an email to docu team with hints, how to deal with is. At least xmlgraphics-fop 1.1 baked in Java:packages is an one part of a solution. Regards Michal Vyskocil
On 30 октября 2012 16:44:02 Michal Vyskocil wrote:
On Sat, Oct 27, 2012 at 07:27:17PM +0200, Stephan Kulow wrote:
Am 27.10.2012 18:32, schrieb Kyrill Detinov:
On Sat, 27 Oct 2012 12:46:29 +0100 Cristian Morales Vega wrote:
- opensuse-manuals_ru Fails for 86 days: java 1.7 breaks it
I don't think this is a real problem. The package is built noarch. And it is buit successfully for i586. So we have it in repository any way. https://build.opensuse.org/package/show?package=opensuse-manuals_ru&proj ect=openSUSE%3AFactory> If java 1.7 breaks fop on x86_64, it *is* a problem.
On the other hand using a recursion in Java is probably the symptom of bad design, causing StackOverflowError. From my POW fop is what is broken ...
BTW: I've already sent an email to docu team with hints, how to deal with is. At least xmlgraphics-fop 1.1 baked in Java:packages is an one part of a solution.
Regards Michal Vyskocil
If use fop from Java:packages both packages not building (32- and 64-bit). -- Friendly openSUSE Community -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Thu, Nov 01, 2012 at 07:42:25PM +0400, EGD wrote:
On 30 октября 2012 16:44:02 Michal Vyskocil wrote:
On Sat, Oct 27, 2012 at 07:27:17PM +0200, Stephan Kulow wrote:
Am 27.10.2012 18:32, schrieb Kyrill Detinov:
On Sat, 27 Oct 2012 12:46:29 +0100 Cristian Morales Vega wrote:
- opensuse-manuals_ru Fails for 86 days: java 1.7 breaks it
I don't think this is a real problem. The package is built noarch. And it is buit successfully for i586. So we have it in repository any way. https://build.opensuse.org/package/show?package=opensuse-manuals_ru&proj ect=openSUSE%3AFactory> If java 1.7 breaks fop on x86_64, it *is* a problem.
On the other hand using a recursion in Java is probably the symptom of bad design, causing StackOverflowError. From my POW fop is what is broken ...
BTW: I've already sent an email to docu team with hints, how to deal with is. At least xmlgraphics-fop 1.1 baked in Java:packages is an one part of a solution.
Regards Michal Vyskocil
If use fop from Java:packages both packages not building (32- and 64-bit).
I see no problem with a fop in J:p - can you give me details? $ osc r Java:packages xmlgraphics-fop openSUSE_12.1 x86_64 unresolvable openSUSE_12.1 i586 unresolvable openSUSE_12.2 x86_64 succeeded openSUSE_12.2 i586 succeeded openSUSE_Factory i586 blocked* openSUSE_Factory x86_64 succeede BTW: as I see J:p as Factory "devel" project, I am not that interested in fixing builds for older distributions. Regards Michal Vyskocil
Dnia poniedziałek, 5 listopada 2012 17:13:30 Michal Vyskocil pisze:
If use fop from Java:packages both packages not building (32- and 64-bit).
I see no problem with a fop in J:p - can you give me details?
The problem is fop crashes at run time while processing the manual in a 64-bit environment. Not that I really care; the HTML version is enough for me. But I understand you guys need to print the manual an put it into the pretty little box with a Gecko on it so it needs to be fixed somehow; it looks like an upstream problem though. Chris -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi, On Sat, Oct 27, 2012 at 12:46:29PM +0100, Cristian Morales Vega wrote:
The following packages have been failing to build on Factory for more than 30 days. This is a reminder for anybody that could be interested in any of them. Any package failing to build for more than 100 days will be dropped from openSUSE.
- libgcj43 Fails for 277 days: undefined reference to `__cxa_call_unexpected'
@Richard: I wouldd drop all older releases of gcc-java and leave only the latest (libgcj47 atm) one for openjdk bootstrap. Unfortunatelly, there's no chance to do drop it completelly.
- elilo Fails for 92 days: undefined reference to `__stack_chk_fail_local' (New upstream version 3.14 available) - opensuse-manuals_ru Fails for 86 days: java 1.7 breaks it
I'm looking on it, but it might make a sense to accept some of the noarch packages to be built only on one architecture. At least in case opensuse-manuals, doing the i586/x86_64 builds is pointless and waste our limited build power.
- selinux-policy Fails for 74 days: error(s) encountered while parsing configuration (Different changes in devel project (since 6 months)) - libgcj41 Fails for 47 days: java test cases...
The same as libgcj43
- compiz Fails for 44 days: kwin changes - kdegraphics3 Fails for 42 days: gphoto update (Current sources were declined: request 138654) - xerces-j2-bootstrap Fails for 33 days: temporary failure
Because of libgcj47 dependencies ...
- hawk Fails for 33 days: cannot load such file -- gettext/tools/rgettext (rails 2 vs rails 3?) - python-tagpy Fails for 33 days: taglib update - rubygem-webyast-time Fails for 31 days: Missing partial shared/online_help (Different changes in devel project (since 23 days)) - ccscript3 Fails for 30 days: undefined reference to `main' (Request 139531 to network:telephony) - iscsitarget Fails for 30 days: kernel 3.6
This is a test. Please give some feedback. Anything to improve? Did this email actually helped you? The email was sent BCC to the package maintainers I could identify. I couldn't identify one clear one for ccscript3 and sent it to the latest .changes entry.
OK, some feedback * Why the subject is Re: your email? I'm bit curious it did not end in my spam folder ;-) * I don't think that using BCC is needed - all our emails are easilly accessible for every OBS user and the maintainer should be interested someone is going to fix his package ... Regards Michal Vyskocil
On 29 October 2012 09:15, Michal Vyskocil
OK, some feedback
* Why the subject is Re: your email? I'm bit curious it did not end in my spam folder ;-)
Because I forgot to set a subject and something added it in the way to you. I will fix that for the next one.
* I don't think that using BCC is needed - all our emails are easilly accessible for every OBS user and the maintainer should be interested someone is going to fix his package ...
If nobody disagrees in using CC instead I will do it for the next one. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Mon, 29 Oct 2012 10:26, Cristian Morales Vega
On 29 October 2012 09:15, Michal Vyskocil
wrote: OK, some feedback
* Why the subject is Re: your email? I'm bit curious it did not end in my spam folder ;-)
Because I forgot to set a subject and something added it in the way to you. I will fix that for the next one.
Thanks, that will make sorting and searching easier.
* I don't think that using BCC is needed - all our emails are easilly accessible for every OBS user and the maintainer should be interested someone is going to fix his package ...
If nobody disagrees in using CC instead I will do it for the next one.
Please, if you can, set a 'Reply-To:' header to the list, that would make it easier for everybody. General feedback: Thank you very much. This makes tracking misbehaving packages easier, and brings them back into fokus. Sometimes, another set of eyes sees the error oneself overlooks. -- Yamaban. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (7)
-
Cristian Morales Vega
-
EGD
-
Krzysztof Żelechowski
-
Kyrill Detinov
-
Michal Vyskocil
-
Stephan Kulow
-
Yamaban