[opensuse-packaging] Factory Status (2012/12/28)
This time I didn't report the new problems. Simply we are in Christmas and people is less active. But just in case somebody feels like fixing something, here is the list. In any case the list is too long, We have six build failures because sblim-sfcb removed its /etc/init.d/sfcb file to use only Systemd and those packages restart the service in the scriplets. Then there are also a few C# failures. And the classic failures from the kernel update. Name Devel Project Bug report Status - selinux-policy security:SELinux bnc#789160 Fails for 136 days: error(s) encountered while parsing configuration (Request 145734 to openSUSE:Factory) - hawk network:ha-clustering:Factory bnc#789165 Fails for 95 days: cannot load such file -- gettext/tools/rgettext (rails 2 vs rails 3?) (Request 146273 to openSUSE:Factory) - psi network bnc#789178 Fails for 85 days: error: 'OtrlMessageAppOps' has no member named 'notify' (Different changes in devel project (since 15 days)) - gnome-do-plugins GNOME:Apps bnc#789193 Fails for 85 days: Type `FlickrNet.FoundUser' does not contain a definition for `Username' - qutim KDE:Distro:Factory bnc#789195 Fails for 85 days: libotr update - f-spot GNOME:Apps bnc#789196 Fails for 85 days: The type or namespace name `Licenses' could not be found - pcsc-asedriveiiie-usb security:chipcard bnc#793542 Fails for 52 days: /usr/lib/udev/rules.d/*.rules not found - ksymoops Base:System bnc#793544 Fails for 47 days: #error config.h must be included before this header - excalibur Java:packages bnc#793551 Fails for 47 days: error: method checkPackage in class Component cannot be applied - postgresql server:database:postgresql bnc#793553 Fails for 45 days: timezone package needed for timezone (Different changes in devel project (since 3 months)) - libzypp-bindings zypp:Head bnc#793554 Fails for 45 days: test suite fails - webyast-base YaST:Web bnc#793558 Fails for 40 days: No such file or directory - /var/lib/polkit-1/ (Request 146369 to openSUSE:Factory) - libimobiledevice mobile:synchronization:FACTORY bnc#796133 Fails for 25 days: Overriding final methods is not allowed - compiz X11:Compiz bnc#789161 Fails for 19 days: kwin 4.10 - mono-tools Mono:Factory Fails for 18 days: error CS1061: Type `Mono.Cecil.Cil.ExceptionHandler' does not contain a definition for `FilterEnd' (Different sources in devel project (since about 1 month)) - nant Mono:Factory Fails for 18 days: missing framework mono - gnome-do GNOME:Apps Fails for 18 days: error CS0012: The type `Do.Platform.Linux.IConfigurable' is defined in an assembly - gbrainy GNOME:Apps Fails for 18 days: error CS1729: The type `Mono.CSharp.Report' does not contain a constructor - docky GNOME:Apps Fails for 18 days: Assuming assembly reference `Mono.Cairo - libvirt-cim Virtualization Fails for 18 days: /etc/init.d/sfcb: No such file or directory (Systemd port) - sblim-cmpi-ssh_service_profile systemsmanagement:wbem Fails for 18 days: /etc/init.d/sfcb: No such file or directory (Systemd port) - sblim-cmpi-power_supply_profile systemsmanagement:wbem Fails for 18 days: /etc/init.d/sfcb: No such file or directory (Systemd port) - sblim-cmpi-fan_profile systemsmanagement:wbem Fails for 18 days: /etc/init.d/sfcb: No such file or directory (Systemd port) - sblim-cmpi-ethport_profile systemsmanagement:wbem Fails for 18 days: /etc/init.d/sfcb: No such file or directory (Systemd port) - sblim-cmpi-boot_control_profile systemsmanagement:wbem Fails for 18 days: /etc/init.d/sfcb: No such file or directory (Systemd port) - smuxi GNOME:Apps Fails for 18 days: error CS0305: Using the generic type `System.Action<T>' requires `1' type argument(s) (New upstream version 0.8.10.12100 available) - perl-Sys-Virt Virtualization Fails for 17 days: libvirt >= 1.0.0 is required - atspiuiasource Mono:Factory Fails for 17 days: Warning as Error: Assuming assembly reference `WindowsBase - uiadbus Mono:Factory Fails for 17 days: Warning as Error: Assuming assembly reference `WindowsBase - uiaatkbridge Mono:Factory Fails for 17 days: Warning as Error: Assuming assembly reference `WindowsBase - uiautomationwinforms Mono:Factory Fails for 17 days: Warning as Error: Assuming assembly reference `WindowsBase - xerces-j2-bootstrap openSUSE:Factory Fails for 13 days: the typical java one - python-nose devel:languages:python Fails for 10 days: assert 'test_timeout' in log - haveged security Fails for 10 days: failing test suite (Request 146266 to openSUSE:Factory) - ImageMagick graphics Fails for 10 days: failing test suite - calibre Documentation:Tools Fails for 9 days: /etc/bash_completion.d/calibre not found (Different changes in devel project (since 3 days)) - bundle-lang-gnome-extras openSUSE:Factory Fails for 9 days: dia graphs are missing - libwebkit3 openSUSE:Factory Fails for 9 days: Installed (but unpackaged) file(s) found: - _product:openSUSE-ftp-livetree-gnome-i586 Fails for 9 days: outdated lists - _product:openSUSE-ftp-livetree-gnome-x86_64 Fails for 9 days: outdated lists - kernel-vanilla openSUSE:Factory Fails for 8 days: worker ran out of disc space (Request 146394 to openSUSE:Factory) - gstreamer-0_10-plugins-bad multimedia:libs Fails for 8 days: error: expected ')' before '__attribute__' - iscsitarget hardware Fails for 8 days: Kernel 3.7 - hdjmod hardware Fails for 8 days: Kernel 3.7 (Request 146314 to openSUSE:Factory) - ndiswrapper hardware Fails for 8 days: Kernel 3.7 - virtualbox Virtualization Fails for 8 days: Kernel 3.7 - xtables-addons security:netfilter Fails for 8 days: Kernel 3.7 (Request 146265 to openSUSE:Factory) - coreutils-testsuite openSUSE:Factory Fails for 8 days: broken spec - cogl GNOME:Factory Fails for 8 days: compiling docu fails (libxml?) - ibus M17N Fails for 8 days: compiling docu fails (libxml?) - installation-images system:install:head Fails for 7 days: no such package: libnl-* - libdlm network:ha-clustering:Factory Fails for 7 days: Unknown build failure - gdome2 GNOME:Apps Fails for 7 days: Unknown build failure - yast2-installation YaST:Head Fails for 7 days: Unknown build failure -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
El 28/12/12 15:07, Cristian Morales Vega escribió:
- haveged security Fails for 10 days: failing test suite (Request 146266 to openSUSE:Factory)
Test suite might fail at any time, if that happends you have to trigger a manual rebuild. It is a random number generator which may fail the randomness tests randomly :-) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Fri, Dec 28, 2012 at 8:32 PM, Cristian Rodríguez
- haveged security Fails for 10 days: failing test suite (Request 146266 to openSUSE:Factory)
Test suite might fail at any time, if that happends you have to trigger a manual rebuild.
It is a random number generator which may fail the randomness tests randomly :-)
Perhaps it needs better tests? Back when I was working with PRNGs for security purposes, I don't recall NIST randomness tests being so flaky. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Fri, Dec 28, 2012 at 08:32:49PM -0300, Cristian Rodríguez wrote:
El 28/12/12 15:07, Cristian Morales Vega escribió:
- haveged security Fails for 10 days: failing test suite (Request 146266 to openSUSE:Factory)
Test suite might fail at any time, if that happends you have to trigger a manual rebuild.
It is a random number generator which may fail the randomness tests randomly :-)
Builds should be reproducible and not randomly fail. Ciao, marcus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
El mar 22 ene 2013 11:15:52 CLST, Marcus Meissner escribió:
On Fri, Dec 28, 2012 at 08:32:49PM -0300, Cristian Rodríguez wrote:
El 28/12/12 15:07, Cristian Morales Vega escribió:
- haveged security Fails for 10 days: failing test suite (Request 146266 to openSUSE:Factory)
Test suite might fail at any time, if that happends you have to trigger a manual rebuild.
It is a random number generator which may fail the randomness tests randomly :-)
Builds should be reproducible and not randomly fail.
Sure, but how we predict the outcome of a random number generator ? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, Jan 22, 2013 at 12:53 PM, Cristian Rodríguez
Builds should be reproducible and not randomly fail.
Sure, but how we predict the outcome of a random number generator ?
Pseudorandom. You seed it, and it always produces the same output. If you want to test randomness, you can use a better test suite (like NIST's, one that won't result in false positives). If you're already using the better test suite, then the false positive is not a false positive, it's a positive, it shows some cases when the generator isn't random, and should be investigated. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hello, On Jan 22 13:26 Claudio Freire wrote (excerpt):
If you want to test randomness, you can use a better test suite (like NIST's, one that won't result in false positives). If you're already using the better test suite, then the false positive is not a false positive, it's a positive, it shows some cases when the generator isn't random, and should be investigated.
Only out of curiosity: A random number generator that generates only the numbers 0 and 1 should produce a sequence of n same numbers with probability 2 * ( 1 / ( 2^n ) ) = 1 / 2^(n-1) = 2^(1-n) There is a non-zero probability to get a sequence of same numbers with arbitrary length n. Because of the randomness a sequence of n same numbers can happen at any time. I wonder if it is possible to make a test suite that finishes in finite time that never shows false positives or false negatives. I think it is not possible to make such a test suite. Reasoning: Assume the test suite starts and the first sample is a sequence of n same numbers. The probability of this sequence is 2^(1-n) so that the test suite should check at least 1 / 2^(1-n) = 2^(n-1) subsequent samples to make some kind of reasonable decision (*) whether or not the first sample happened with reasonable probability. Because n is not limited, the test suite cannot finish in finite time. (*) I am not at all a random number generator test suite expert. I don't know how such a test suite actually makes its decisions whether or not the random number generator is good or bad. Therefore I called it "Reasoning" and not "Proof". Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Wed, Jan 23, 2013 at 5:26 AM, Johannes Meixner
On Jan 22 13:26 Claudio Freire wrote (excerpt):
If you want to test randomness, you can use a better test suite (like NIST's, one that won't result in false positives). If you're already using the better test suite, then the false positive is not a false positive, it's a positive, it shows some cases when the generator isn't random, and should be investigated.
Only out of curiosity:
A random number generator that generates only the numbers 0 and 1 should produce a sequence of n same numbers with probability 2 * ( 1 / ( 2^n ) ) = 1 / 2^(n-1) = 2^(1-n)
There is a non-zero probability to get a sequence of same numbers with arbitrary length n.
Because of the randomness a sequence of n same numbers can happen at any time.
I wonder if it is possible to make a test suite that finishes in finite time that never shows false positives or false negatives.
I think it is not possible to make such a test suite.
It's far more than that. NIST also tests conditional probabilities, distribution independence over subsampling, and a lot of important tests if one is to use that generator in security-critical applications. In any case, all those tests are probabilistic, and can be parameterized to decide how often you're willing to get false positives. If you set that to "2^(-64)", you'll be a very old man by the time it fails. Or not and be SOL. But in any case, it wouldn't by any chance be a common occurrence, and you would be safe to consider it a true bug worthy of a bug report if it failed several times in short succession. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, Jan 22, 2013 at 12:53:45PM -0300, Cristian Rodríguez wrote:
El mar 22 ene 2013 11:15:52 CLST, Marcus Meissner escribió:
On Fri, Dec 28, 2012 at 08:32:49PM -0300, Cristian Rodríguez wrote:
El 28/12/12 15:07, Cristian Morales Vega escribió:
- haveged security Fails for 10 days: failing test suite (Request 146266 to openSUSE:Factory)
Test suite might fail at any time, if that happends you have to trigger a manual rebuild.
It is a random number generator which may fail the randomness tests randomly :-)
Builds should be reproducible and not randomly fail.
Sure, but how we predict the outcome of a random number generator ?
I'd say this is totally out of scope of %check in rpm. All we need is to to check daemon don't crash and return something. The randomness of an output is upstream job and we just have to make sure there are no distribution patches in the core of haveged affecting it (aka Debian openssl syndromme). Atm, there is one ppc patch in configure.ac, which can be considered as OK. If someone wants to perform real testing, then he should be able to prove his testing is correct - but it'd be a part of openqa or similar system. Regards Michal Vyskocil
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (6)
-
Claudio Freire -
Cristian Morales Vega -
Cristian Rodríguez -
Johannes Meixner -
Marcus Meissner -
Michal Vyskocil