rawhide report: 20101202 changes
Compose started at Thu Dec 2 08:15:04 UTC 2010 Broken deps for x86_64 -- beagle-0.3.9-19.fc14.x86_64 requires libmono.so.0()(64bit) beagle-0.3.9-19.fc14.x86_64 requires libmono.so.0(VER_1)(64bit) db4o-7.4-2.fc13.x86_64 requires mono(Mono.GetOptions) = 0:2.0.0.0 dh-make-0.55-2.fc15.noarch requires debhelper eog-plugins-2.30.0-2.fc14.x86_64 requires libgdata.so.7()(64bit) gedit-vala-0.10.2-2.fc15.i686 requires libvala-0.10.so.0 gedit-vala-0.10.2-2.fc15.x86_64 requires libvala-0.10.so.0()(64bit) 1:gnome-bluetooth-moblin-2.91.2-1.fc15.x86_64 requires libmoblin-panel.so.0()(64bit) 1:gnome-games-extra-2.31.91.1-1.fc15.x86_64 requires libclutter-gtk-0.10.so.0()(64bit) gnome-gmail-notifier-0.10.1-1.fc14.x86_64 requires libnotify.so.1()(64bit) gnome-pilot-eds-2.32.0-1.fc14.x86_64 requires libcamel-1.2.so.19()(64bit) gnome-python2-brasero-2.32.0-1.fc14.x86_64 requires libbrasero-burn.so.1()(64bit) gnome-python2-brasero-2.32.0-1.fc14.x86_64 requires libbrasero-media.so.1()(64bit) gnome-python2-evince-2.32.0-1.fc14.x86_64 requires libevdocument.so.3()(64bit) gnome-python2-evince-2.32.0-1.fc14.x86_64 requires libevview.so.3()(64bit) gnome-python2-evolution-2.32.0-1.fc14.x86_64 requires libcamel-1.2.so.19()(64bit) gnome-python2-totem-2.32.0-1.fc14.x86_64 requires libgnome-media-profiles.so.0()(64bit) gnome-rdp-0.2.3-6.fc12.x86_64 requires mono(Mono.Data.SqliteClient) = 0:2.0.0.0 gpx-viewer-0.2.0-3.fc14.x86_64 requires libchamplain-0.6.so.0()(64bit) gpx-viewer-0.2.0-3.fc14.x86_64 requires libclutter-gtk-0.10.so.0()(64bit) gpx-viewer-0.2.0-3.fc14.x86_64 requires libchamplain-gtk-0.6.so.0()(64bit) gshutdown-0.2-6.fc12.x86_64 requires libnotify.so.1()(64bit) gsql-0.2.1-4.fc12.i686 requires libnotify.so.1 gsql-0.2.1-4.fc12.x86_64 requires libnotify.so.1()(64bit) gyachi-plugin-libnotify-1.2.10-3.fc14.x86_64 requires libnotify.so.1()(64bit) hornsey-1.5.2-0.3.fc15.x86_64 requires libnotify.so.1()(64bit) hornsey-1.5.2-0.3.fc15.x86_64 requires libclutter-gtk-0.10.so.0()(64bit) ibus-fbterm-0.9.1-10.fc15.x86_64 requires libibus.so.2()(64bit) ibus-input-pad-0.1.3-3.fc15.x86_64 requires libinput-pad.so.0()(64bit) intellij-idea-9.0.1.94.399-12.fc15.x86_64 requires commons-collections ircp-tray-0.7.4-1.fc14.x86_64 requires libnotify.so.1()(64bit) java-gnome-4.0.16-3.fc14.x86_64 requires libnotify.so.1()(64bit) libnotifymm-0.6.1-8.fc14.i686 requires libnotify.so.1 libnotifymm-0.6.1-8.fc14.x86_64 requires libnotify.so.1()(64bit) log4net-1.2.10-13.fc13.x86_64 requires mono(System) = 0:1.0.5000.0 log4net-1.2.10-13.fc13.x86_64 requires mono(System.Data) = 0:1.0.5000.0 log4net-1.2.10-13.fc13.x86_64 requires mono(mscorlib) = 0:1.0.5000.0 log4net-1.2.10-13.fc13.x86_64 requires mono(System.Xml) = 0:1.0.5000.0 log4net-1.2.10-13.fc13.x86_64 requires mono(System.Web) = 0:1.0.5000.0 mars-sim-2.84-6.fc14.noarch requires commons-collections moblin-panel-media-0.0.8-0.2.fc13.x86_64 requires libmoblin-panel.so.0()(64bit) moblin-panel-status-0.1.21-6.fc14.x86_64 requires libmoblin-panel.so.0()(64bit) moblin-panel-status-0.1.21-6.fc14.x86_64 requires libsocialweb-client.so.1()(64bit) moblin-panel-status-0.1.21-6.fc14.x86_64 requires libchamplain-0.6.so.0()(64bit) moblin-panel-status-0.1.21-6.fc14.x86_64 requires libclutter-gtk-0.10.so.0()(64bit) mono-ndoc-1.3.1-8.fc13.x86_64 requires mono(System.Drawing) = 0:1.0.5000.0 mono-ndoc-1.3.1-8.fc13.x86_64 requires mono(System.Windows.Forms) = 0:1.0.5000.0 mono-ndoc-1.3.1-8.fc13.x86_64 requires mono(System) = 0:1.0.5000.0 mono-ndoc-1.3.1-8.fc13.x86_64 requires mono(mscorlib) = 0:1.0.5000.0 mono-ndoc-1.3.1-8.fc13.x86_64 requires mono(System.Xml) = 0:1.0.5000.0 nagios-plugins-snmp-disk-proc-1.2-6.fc13.x86_64 requires libnetsnmp.so.20()(64bit) 1:nant-0.85-34.fc13.x86_64 requires mono(ICSharpCode.SharpZipLib) = 0:0.84.0.0 nntpgrab-gui-0.6.90-3.fc15.x86_64 requires libnotify.so.1()(64bit) padevchooser-0.9.4-0.11.svn20070925.fc13.x86_64 requires libnotify.so.1()(64bit) pcmanx-gtk2-0.3.9-6.20100618svn.fc14.i686 requires libnotify.so.1 pcmanx-gtk2-0.3.9-6.20100618svn.fc14.x86_64 requires libnotify.so.1()(64bit) pidgin-gfire-0.9.2-2.fc15.x86_64 requires libnotify.so.1()(64bit) qtgpsc-0.2.3-6.fc12.x86_64 requires libgps.so.18()(64bit) spacewalk-backend-tools-1.2.74-2.fc15.noarch requires spacewalk-admin = 0:0.1.1-0 sunbird-1.0-0.33.b2pre.fc15.x86_64 requires libnotify.so.1()(64bit) synce-trayicon-0.15-1.fc14.x86_64 requires libnotify.so.1()(64bit)
scp requires openssh-clients on server machine?
Today I discovered that I cannot use 'scp' to transfer files when the remote site has only 'openssh-server' package installed. I can ssh to it, but I can't scp to it. I spits this error message: bash: scp: command not found lost connection When I install 'openssh-clients' package on the remote site, I can now scp to it. Is this really expected, or is it a bug? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: scp requires openssh-clients on server machine?
On 12/02/2010 07:04 AM, Kamil Paral wrote: Today I discovered that I cannot use 'scp' to transfer files when the remote site has only 'openssh-server' package installed. I can ssh to it, but I can't scp to it. I spits this error message: ... Is this really expected, or is it a bug? It is expected. Scp is a client/server application, i.e., the same program is used for the client and server end of the scp protocol. That's why scp needs to be available on the server. If you want to be able to transfer files with a server without scp installed on it, you can configure sshd on the server to use the internal-sftp subsystem for servicing sftp requests, and then use the sftp client to transfer files to/from the server. jik smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nohz=off and system performance
On Thu, 2010-12-02 at 03:03 +0100, Dennis Jacobfeuerborn wrote: I just noticed that when I boot with nohz=off I get improved vmstat numbers. When playing a YouTube video I get an idle percentage of around 25-30 but when I boot with nohz=off the system seems to cope much better and show an idle percentage of 50. Can anyone shed some light on what is going on here? Given this and the problems described in bug 650934 I'm wondering how trustworthy Fedoras system metrics are. Values for load and cpu usage shouldn't really be this flaky. There's at least one bug in recent kernels where active CPU time (as reported by top and friends) are wildly overaccounted. powertop still seems to show a pretty reasonable estimate though. Also, you didn't mention which hardware this was with, but at least on Intel GPU systems there's a known issue where graphics performance suffers when the CPU appears idle but the GPU has work to do; the system enters a lower C state based on the CPU workload, but that lowers the memory clock, which means the GPU gets starved for bandwidth. - ajax -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: WRT MacBook Air and Fedora
On 12/02/2010 08:39 AM, Jurgen Kramer wrote: On Sat, 2010-11-27 at 07:54 -0500, Jan Wildeboer wrote: Will try this evening and report here! BTW - are you using nouveau or (a)kmod-nvidia? Jan Does sound work with my latest kernel? Nope. See attached dmesg for clues (I cannot see sth obvious). I tried alsamixer and put everything on 100% levels, I switched between stereo duplex and stereo output in sound preferences, no luck :-( Jan -- Jan H Wildeboer| EMEA Open Source Affairs | Office: +49 (0)89 205071-207 Red Hat GmbH | Mobile: +49 (0)174 33 23 249 Technopark II, Haus C | Fax:+49 (0)89 205071-111 Werner-von-Siemens-Ring 11 -15 | 85630 Grasbrunn| _ Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 11 -15 85630 Grasbrunn, Handelsregister: Amtsgericht Muenchen HRB 153243 Geschaeftsfuehrer: Brendan Lane, Charlie Peters, Michael Cunningham, Charles Cachera _ GPG Key: 3AC3C8AB Fingerprint: 3D1E C4E0 DD67 E16D E47A 9564 A72F 5C39 3AC3 C8AB [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.35.6-48.mbajk6.fc14.x86_64 (kra...@nasng.slim) (gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) ) #1 SMP Sat Nov 27 12:40:07 CET 2010 [0.00] Command line: ro root=/dev/mapper/vg_mba31-lv_root rd_LVM_LV=vg_mba31/lv_root rd_LVM_LV=vg_mba31/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=de nomodeset rhgb quiet reboot=pci [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0008f000 (usable) [0.00] BIOS-e820: 0008f000 - 0009 (reserved) [0.00] BIOS-e820: 0009 - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e - 0010 (reserved) [0.00] BIOS-e820: 0010 - af00 (usable) [0.00] BIOS-e820: af00 - bf00 (reserved) [0.00] BIOS-e820: bf00 - bf719000 (usable) [0.00] BIOS-e820: bf719000 - bf939000 (ACPI NVS) [0.00] BIOS-e820: bf939000 - bfef9000 (ACPI data) [0.00] BIOS-e820: bfef9000 - bfeff000 (reserved) [0.00] BIOS-e820: bfeff000 - bff0 (ACPI data) [0.00] BIOS-e820: d320 - d3201000 (reserved) [0.00] BIOS-e820: f000 - f400 (reserved) [0.00] BIOS-e820: fec0 - fec01000 (reserved) [0.00] BIOS-e820: fee0 - fee01000 (reserved) [0.00] BIOS-e820: ffc0 - 0001 (reserved) [0.00] BIOS-e820: 0001 - 00014000 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI 2.4 present. [0.00] e820 update range: - 1000 (usable) == (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] No AGP bridge found [0.00] last_pfn = 0x14 max_arch_pfn = 0x4 [0.00] MTRR default type: write-back [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-F uncachable [0.00] MTRR variable ranges enabled: [0.00] 0 base 0C000 mask FC000 uncachable [0.00] 1 base 0BFF0 mask 0 uncachable [0.00] 2 disabled [0.00] 3 disabled [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] last_pfn = 0xbf719 max_arch_pfn = 0x4 [0.00] initial memory mapped : 0 - 2000 [0.00] init_memory_mapping: -bf719000 [0.00] 00 - 00bf60 page 2M [0.00] 00bf60 - 00bf719000 page 4k [0.00] kernel direct mapping tables up to bf719000 @ 8000-d000 [0.00] init_memory_mapping: 0001-00014000 [0.00] 01 - 014000 page 2M [0.00] kernel direct mapping tables up to 14000 @ b000-11000 [0.00] RAMDISK: 3737f000 - 37ff [0.00] ACPI: RSDP 000fe020 00024 (v02 APPLE ) [0.00] ACPI: XSDT bf96a1c0 0008C (v01 APPLE Apple00 0061 0113) [0.00] ACPI: FACP bf968000 000F4 (v04 APPLE Apple00 0061 Loki 005F) [0.00] ACPI: DSDT bf95b000 0572C (v01 APPLE MacBookA 00030001 INTL 20061109) [0.00] ACPI: FACS
call for tests
As you know, we've got this automated storage test system for anaconda now. I've got enough tests to cover all the partitioning parts of the Fedora test matrix (except for resizing, which kickstart cannot express). You can see the list of tests for yourself here: http://git.fedorahosted.org/git/?p=autoqa.git;a=tree;f=tests/anaconda_storage/framework/suites;hb=refs/heads/clumens What I'm interested in is more suggestions for tests. If you can come up with a good description of what the disks look like when we start, what we should do to them, and what they should look like when we're done that would be very helpful. I'll keep a list in git. What'd be even more helpful would be if people were interested in writing tests themselves. I might try to offer training for this at FUDCon or perhaps in irc one day given enough interest. If you wanted to write a test, you'd need to: * Know python well. I'm not willing to teach people how to program. * Have some familiarity with python's unittest module. This is easy. If you can program, you can pick it up in about five minutes. * Know kickstart well. The tests themselves are run through kickstart files, so you need to know how to express various partitioning setups. I can teach this. * Be really picky. * Know what anaconda's expected behavior is. This is pretty tough, but I'm willing to explain this as needed. - Chris -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Fedora QA] #152: Test Cases Management
#152: Test Cases Management --+- Reporter: rhe | Owner: rhe Type: enhancement | Status: new Priority: major| Milestone: Fedora 15 Component: Wiki | Version: Resolution: |Keywords: retrospective --+- Comment (by adamwill): I know James has been talking about this with some RH people. We discussed it on the phone and agreed that we like the idea in principle but the ease and flexibility of the current wiki system is something we don't want to lose, so we thought we should set some quite high barriers: any tcms system must be as easy to use (both for those creating the test cases and those running them) as the wiki is. -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/152#comment:1 Fedora QA http://fedorahosted.org/fedora-qa Fedora Quality Assurance -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: call for tests
On 12/02/2010 04:53 PM, Chris Lumens wrote: What I'm interested in is more suggestions for tests. Given my rough ride when testing anaconda with multiple partitions with multiple different file systems types is there a test case that covers that? For examples creates 15 different partitions with separated mount points on different files system types? JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Fedora QA] #152: Test Cases Management
#152: Test Cases Management --+- Reporter: rhe | Owner: rhe Type: enhancement | Status: new Priority: major| Milestone: Fedora 15 Component: Wiki | Version: Resolution: |Keywords: retrospective --+- Comment (by jlaska): I love the idea of doing a test event with a pilot instance of nitrate/TCMS. It was fun doing that with the semantic-mediawiki, and I think we learn a lot with that approach. We've all talked about TCMS and how best to integrate it with our workflow. There are definite shortcomings to our current wiki-based approach that limit our ability to growth, but there are plenty of positive lessons learned that I think we should recognize and prioritize. Hurry: Would you be willing to start drafting some wiki content so we can capture this? Either a requirements or technology comparison document? I don't want this to be a free-for-all 'I want a pony' list of features we want of a TCMS solution. But perhaps starting with documenting the pro's and con's with our current wiki-based workflow? The goal for me would be to identify what our MUST-HAVE and NICE-TO-HAVE's are from any solution. Ideally, we can use that to determine the best route forward (whether it's filing bugs/tickets/rfe's against TCMS, or something else). -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/152#comment:2 Fedora QA http://fedorahosted.org/fedora-qa Fedora Quality Assurance -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: call for tests
yeah, I agree this would be useful: we have a fairly ambitious final release criterion that basically states that any failure to install to a valid partition table (where the /boot and / are big enough, obviously) with supported partition types is a release blocker. So we should have some as-complex/weird-as-possible automated tests for this; a ton of partitions, complex layered RAID/LVM setups and so on. All of these are possible. The most complex things I have now are: (1) Do autopartitioning on sda. Do autopartitioning on sdb. Now they have the same PV/LV names. Do autopartitioning on sda+sdb and see if it works. (2) Create some filesystems on part of sda. Do autopartitioning in the remaining space. Is the initial stuff still there? (3) LVM on top of RAID0. If you can think it up, we can add it. However at some point, we're likely to hit too many tests and this ends up taking forever to run. I'm sure we can think of solutions to that, and it's a problem I would love to have. A computer just sitting there chewing through storage tests all day would be pretty fun. - Chris -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 14 updates-testing report
The following Fedora 14 Security updates need testing: https://admin.fedoraproject.org/updates/phpMyAdmin-3.3.8.1-1.fc14 https://admin.fedoraproject.org/updates/bind-9.7.2-4.P3.fc14 https://admin.fedoraproject.org/updates/krb5-1.8.2-7.fc14 https://admin.fedoraproject.org/updates/mailman-2.1.13-6.fc14.1 https://admin.fedoraproject.org/updates/exim-4.72-2.fc14 https://admin.fedoraproject.org/updates/bareftp-0.3.7-1.fc14 The following Fedora 14 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/python-decorator-3.2.1-1.fc14 https://admin.fedoraproject.org/updates/selinux-policy-3.9.7-14.fc14 https://admin.fedoraproject.org/updates/xorg-x11-drv-geode-2.11.10-1.fc14 https://admin.fedoraproject.org/updates/perl-CGI-3.50-2.fc14,perl-5.12.2-140.fc14 https://admin.fedoraproject.org/updates/libwnck-2.30.4-1.fc14 The following builds have been pushed to Fedora 14 updates-testing apvlv-0.0.9.8-1.fc14 astyle-2.01-1.fc14 bind-9.7.2-4.P3.fc14 django-staticfiles-0.3.2-3.fc14 django-threadedcomments-0.5.3-2.fc14 eclipse-collabnet-merge-2.2.1-1.fc14 emacs-slime-3.0-0.1.20101113cvs.fc14 fldigi-3.20.32-1.fc14 geany-0.19.2-1.fc14 ghc-attoparsec-0.8.2.0-1.fc14 ghc-base64-bytestring-0.1.0.1-2.fc14 ghc-text-0.10.0.0-1.fc14 google-perftools-1.6-2.fc14 gssdp-0.8.2-1.fc14 mercurial-1.7.2-1.fc14 ndisc6-1.0.0-1.fc14 nfs-utils-1.2.3-2.fc14 olpc-utils-1.2.4-1.fc14 openchange-0.9-9.fc14 openscap-0.6.5-1.fc14 perl-Config-General-2.50-1.fc14 perl-DBIx-Class-Schema-Loader-0.07002-2.fc14 perl-Moose-1.12-2.fc14 perlbrew-0.14-1.fc14 php-pear-Mail-Mime-1.8.1-1.fc14 publican-2.4-1.fc14 python-boto-1.9b-5.fc14 python-decorator-3.2.1-1.fc14 selinux-policy-3.9.7-14.fc14 system-config-network-1.6.2-1.fc14 tomcat6-6.0.26-15.fc14 xorg-x11-drv-geode-2.11.10-1.fc14 zathura-0.0.8.2-1.fc14 Details about builds: apvlv-0.0.9.8-1.fc14 (FEDORA-2010-18451) PDF viewer which behaves like Vim Update Information: Initial packaging. References: [ 1 ] Bug #654848 - Review Request: apvlv - PDF viewer which behaves like Vim https://bugzilla.redhat.com/show_bug.cgi?id=654848 astyle-2.01-1.fc14 (FEDORA-2010-18444) Source code formatter for C-like programming languages Update Information: Update to new version, with many bugfixes. For full changes see: http://astyle.sourceforge.net/notes.html ChangeLog: * Wed Dec 1 2010 Thomas Spura toms...@fedoraproject.org - 2.01-1 - update to new version bind-9.7.2-4.P3.fc14 (FEDORA-2010-18469) The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) server Update Information: Update to 9.7.2-P3 release which contains various security fixes. ChangeLog: * Thu Dec 2 2010 Adam Tkac atkac redhat com 32:9.7.2-4.P3 - update to 9.7.2-P3 References: [ 1 ] Bug #658982 - CVE-2010-3615 bind: allow-query processed incorrectly allowing access to authoritative zones that should be restricted https://bugzilla.redhat.com/show_bug.cgi?id=658982 [ 2 ] Bug #658974 - CVE-2010-3613 bind: failure to clear existing RRSIG records when a NO DATA is negatively cached could DoS named https://bugzilla.redhat.com/show_bug.cgi?id=658974 [ 3 ] Bug #658977 - CVE-2010-3614 bind: key algorithm rollover may mark secure answers as insecure https://bugzilla.redhat.com/show_bug.cgi?id=658977 django-staticfiles-0.3.2-3.fc14 (FEDORA-2010-18438) A Django app that provides helpers for serving static files Update Information: A Django app that provides helpers for serving static filess References: [ 1 ] Bug
Fedora 13 updates-testing report
The following Fedora 13 Security updates need testing: https://admin.fedoraproject.org/updates/mailman-2.1.12-16.fc13 https://admin.fedoraproject.org/updates/phpMyAdmin-3.3.8.1-1.fc13 https://admin.fedoraproject.org/updates/wireshark-1.2.13-1.fc13 https://admin.fedoraproject.org/updates/krb5-1.7.1-16.fc13 https://admin.fedoraproject.org/updates/bareftp-0.3.7-1.fc13 The following Fedora 13 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/selinux-policy-3.7.19-74.fc13 https://admin.fedoraproject.org/updates/perl-5.10.1-121.fc13,perl-CGI-3.50-2.fc13 https://admin.fedoraproject.org/updates/elfutils-0.150-1.fc13 https://admin.fedoraproject.org/updates/livecd-tools-13.0-1.fc13 https://admin.fedoraproject.org/updates/gnome-desktop-2.30.2-1.fc13 https://admin.fedoraproject.org/updates/mingetty-1.08-6.fc13 https://admin.fedoraproject.org/updates/sendmail-8.14.4-6.fc13 https://admin.fedoraproject.org/updates/mash-0.5.20-1.fc13 https://admin.fedoraproject.org/updates/openldap-2.4.21-11.fc13 https://admin.fedoraproject.org/updates/nss-3.12.7-4.fc13,nss-util-3.12.7-2.fc13,nss-softokn-3.12.7-3.fc13,nspr-4.8.6-1.fc13 https://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.904-7.fc13 The following builds have been pushed to Fedora 13 updates-testing astyle-2.01-1.fc13 cabal2spec-0.22.2-1.fc13 django-staticfiles-0.3.2-3.fc13 django-threadedcomments-0.5.3-2.fc13 emacs-slime-3.0-0.1.20101113cvs.fc13 fldigi-3.20.32-1.fc13 geany-0.19.2-1.fc13 ghc-attoparsec-0.8.2.0-1.fc13 ghc-base64-bytestring-0.1.0.1-2.fc13 google-perftools-1.6-2.fc13 mercurial-1.7.2-1.fc13 ndisc6-1.0.0-1.fc13 perlbrew-0.14-1.fc13 publican-2.4-1.fc13 selinux-policy-3.7.19-74.fc13 tomcat6-6.0.26-13.fc13 zathura-0.0.8.2-1.fc13 Details about builds: astyle-2.01-1.fc13 (FEDORA-2010-18462) Source code formatter for C-like programming languages Update Information: Update to new version, with many bugfixes. For full changes see: http://astyle.sourceforge.net/notes.html ChangeLog: * Wed Dec 1 2010 Thomas Spura toms...@fedoraproject.org - 2.01-1 - update to new version cabal2spec-0.22.2-1.fc13 (FEDORA-2010-18478) Tool for creating .spec files for Haskell Cabal Packages ChangeLog: * Tue Jul 27 2010 Jens Petersen peter...@redhat.com - 0.22.2-1 - start releases from 0 - drop cgi-bin/hackage-scripts/ prefix from URLs - bcond for hscolour - require ghc-rpm-macros-0.8.1 - bring back ghc_pkg_c_deps for binlib django-staticfiles-0.3.2-3.fc13 (FEDORA-2010-18457) A Django app that provides helpers for serving static files Update Information: A Django app that provides helpers for serving static files. References: [ 1 ] Bug #645762 - Review Request: django-staticfiles - A Django app that provides helpers for serving static files https://bugzilla.redhat.com/show_bug.cgi?id=645762 django-threadedcomments-0.5.3-2.fc13 (FEDORA-2010-18449) A simple yet flexible threaded commenting system for Django Update Information: A simple yet flexible threaded commenting system for Django. References: [ 1 ] Bug #645761 - Review Request: django-threadedcomments - a simple yet flexible threaded commenting system for Django https://bugzilla.redhat.com/show_bug.cgi?id=645761 emacs-slime-3.0-0.1.20101113cvs.fc13 (FEDORA-2010-18483) The superior lisp interaction mode for emacs References: [ 1 ] Bug #632858 - Review Request: emacs-slime - The superior lisp interaction mode for emacs
Re: call for tests
On 12/02/2010 11:53 AM, Chris Lumens wrote: As you know, we've got this automated storage test system for anaconda now. I've got enough tests to cover all the partitioning parts of the Fedora test matrix (except for resizing, which kickstart cannot express). You can see the list of tests for yourself here: http://git.fedorahosted.org/git/?p=autoqa.git;a=tree;f=tests/anaconda_storage/framework/suites;hb=refs/heads/clumens What I'm interested in is more suggestions for tests. If you can come up with a good description of what the disks look like when we start, what we should do to them, and what they should look like when we're done that would be very helpful. I'll keep a list in git. What'd be even more helpful would be if people were interested in writing tests themselves. I might try to offer training for this at FUDCon or perhaps in irc one day given enough interest. If you wanted to write a test, you'd need to: * Know python well. I'm not willing to teach people how to program. * Have some familiarity with python's unittest module. This is easy. If you can program, you can pick it up in about five minutes. * Know kickstart well. The tests themselves are run through kickstart files, so you need to know how to express various partitioning setups. I can teach this. * Be really picky. * Know what anaconda's expected behavior is. This is pretty tough, but I'm willing to explain this as needed. - Chris Don't know about the python part, but: Install / to a LV over raid10 after first reducing the LVs in the VG to gain the space, /boot on an available partition, mount all other LV distros and their /boot partitions, mount all other non-LV partitions. This is basically what I ask anaconda to do when a new fedora release starts thru the development cycle. Reducing the LVs did not work during the F14 cycle. Regards, OldFart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Re: [Fedora QA] #152: Test Cases Management
Hi,
i can say i am new to Fedora in general as project but i have
participated in many testing campaigns professionaly, so honestly i see
this TCMS(?) or any other way to organise test cases as big add value.
It would be really great if we had a list of test cases for whole system
(of course everyone can contibute) and mark each of them as
successful/failed, track the status etc...
The one of the advantages is that i am looking at such list of test
cases and i am able to easily figure out what has been already tested
and wht remaining is.
If have missed something and such 'thing exists please correct me an
forget the idea, otherwise what do you think ??
Regards,
Karol
W dniu 20:59, Fedora QA pisze:
ם�z�BjǬ1�ځ鞞ߑz�+���㰝秅��zg��+Z��'{늊�)���̊W�h��y
���w��h��W��*'E�(��b�r��
+v��,��-��
��z{[ɧZ����'�Z��!j��z{Z�H�a���(��G��)��v+ �� v+h��^�'y��j
�y�aj� �) ��u梞��ȩ^y� jw_��bn)b�* ����ޞ��+2�צ��(��a�x0y�'����%�Ǭ��� �.�� ��zb�ڮ���Ƨ���̬�馺�[y� j̭�� n�a~�톋 r���)��z�\jǬjwm�� ���x-�隲�^�)���rG�Q��l���v�چ�-y�+���v�ک��� ��y��Wm���y�+j,��h��y�+j��y�+i ��+r�.���e===
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Installing fedora while running fedora?
Using a liveCD I can install fedora on my system while running the LiveCD. Can you do the same thing just running vanilla Fedora? This would be a really useful feature, but I'm not seeing any information on how to do it. Rodd -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
