rawhide report: 20100805 changes
Compose started at Thu Aug 5 08:15:11 UTC 2010 Broken deps for x86_64 -- Mayavi-3.3.0-1.fc13.x86_64 requires python(abi) = 0:2.6 Mayavi-3.3.0-1.fc13.x86_64 requires libpython2.6.so.1.0()(64bit) PragmARC-20060427-6.fc13.i686 requires libgnarl-4.4.so PragmARC-20060427-6.fc13.i686 requires libgnat-4.4.so PragmARC-20060427-6.fc13.x86_64 requires libgnarl-4.4.so()(64bit) PragmARC-20060427-6.fc13.x86_64 requires libgnat-4.4.so()(64bit) QuantLib-test-1.0.1-3.fc14.x86_64 requires libboost_unit_test_framework.so.1.41.0()(64bit) 1:anjuta-2.30.0.0-2.fc14.i686 requires libgladeui-1.so.9 1:anjuta-2.30.0.0-2.fc14.i686 requires libwebkit-1.0.so.2 1:anjuta-2.30.0.0-2.fc14.i686 requires libdevhelp-1.so.1 1:anjuta-2.30.0.0-2.fc14.x86_64 requires libgladeui-1.so.9()(64bit) 1:anjuta-2.30.0.0-2.fc14.x86_64 requires libdevhelp-1.so.1()(64bit) 1:anjuta-2.30.0.0-2.fc14.x86_64 requires libwebkit-1.0.so.2()(64bit) antlr3-python-3.1.2-7.fc14.noarch requires python(abi) = 0:2.6 barry-0.17-0.1.20100329git.fc14.x86_64 requires libboost_serialization.so.1.41.0()(64bit) cairo-java-1.0.5-12.fc12.i686 requires libgcj.so.10 cairo-java-1.0.5-12.fc12.x86_64 requires libgcj.so.10()(64bit) cyphesis-0.5.21-2.fc13.x86_64 requires libpython2.6.so.1.0()(64bit) ekg2-python-0.2-0.12.rc1.fc14.x86_64 requires libpython2.6.so.1.0()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libedata-book-1.2.so.2()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libcamel-1.2.so.17()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libgtkhtml-editor.so.0()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libebook-1.2.so.9()(64bit) evolution-couchdb-0.4.92-1.fc14.x86_64 requires libcamel-provider-1.2.so.17()(64bit) evolution-sharp-0.21.1-7.fc14.x86_64 requires libebook-1.2.so.9()(64bit) evolution-sharp-0.21.1-7.fc14.x86_64 requires libecal-1.2.so.7()(64bit) fmt-ptrn-java-1.3.20-5.fc13.i686 requires libgcj.so.10 fmt-ptrn-java-1.3.20-5.fc13.x86_64 requires libgcj.so.10()(64bit) frysk-0.4-26.fc14.x86_64 requires libgcj.so.10()(64bit) frysk-devel-0.4-26.fc14.i386 requires libgcj.so.10 frysk-devel-0.4-26.fc14.x86_64 requires libgcj.so.10()(64bit) frysk-gnome-0.4-26.fc14.x86_64 requires libgcj.so.10()(64bit) fusecompress-2.6-6.20100223git754bc0de.fc14.x86_64 requires libboost_filesystem-mt.so.1.41.0()(64bit) fusecompress-2.6-6.20100223git754bc0de.fc14.x86_64 requires libboost_system-mt.so.1.41.0()(64bit) fusecompress-2.6-6.20100223git754bc0de.fc14.x86_64 requires libboost_program_options-mt.so.1.41.0()(64bit) fusecompress-2.6-6.20100223git754bc0de.fc14.x86_64 requires libboost_iostreams-mt.so.1.41.0()(64bit) fusecompress-2.6-6.20100223git754bc0de.fc14.x86_64 requires libboost_serialization-mt.so.1.41.0()(64bit) glib-java-0.2.6-16.fc12.i686 requires libgcj.so.10 glib-java-0.2.6-16.fc12.x86_64 requires libgcj.so.10()(64bit) 1:gnome-bluetooth-2.90.0-4.fc15.x86_64 requires gnome-bluetooth-libs = 0:2.90.0-4.fc15 1:gnome-bluetooth-libs-devel-2.90.0-4.fc15.i686 requires gnome-bluetooth-libs = 0:2.90.0-4.fc15 1:gnome-bluetooth-libs-devel-2.90.0-4.fc15.x86_64 requires gnome-bluetooth-libs = 0:2.90.0-4.fc15 1:gnome-bluetooth-moblin-2.90.0-4.fc15.x86_64 requires gnome-bluetooth-libs = 0:2.90.0-4.fc15 gnomeradio-1.8-6.fc14.x86_64 requires libgnome-media-profiles.so.0()(64bit) gpx-viewer-0.1.2-2.fc14.x86_64 requires libchamplain-gtk-0.4.so.0()(64bit) gpx-viewer-0.1.2-2.fc14.x86_64 requires libchamplain-0.4.so.0()(64bit) hugin-2010.0.0-3.fc14.x86_64 requires libboost_thread-mt.so.1.41.0()(64bit) hugin-base-2010.0.0-3.fc14.i686 requires libboost_thread-mt.so.1.41.0 hugin-base-2010.0.0-3.fc14.x86_64 requires libboost_thread-mt.so.1.41.0()(64bit) intellij-idea-9.0.1.94.399-11.fc14.x86_64 requires jna-examples kdeedu-math-4.4.95-1.fc14.py27.x86_64 requires libboost_python-mt.so.1.41.0()(64bit) libgconf-java-2.12.4-14.fc12.i686 requires libgcj.so.10 libgconf-java-2.12.4-14.fc12.x86_64 requires libgcj.so.10()(64bit) libglade-java-2.12.5-12.fc12.i686 requires libgcj.so.10 libglade-java-2.12.5-12.fc12.x86_64 requires libgcj.so.10()(64bit) libgnome-java-2.12.4-12.fc12.i686 requires libgcj.so.10 libgnome-java-2.12.4-12.fc12.x86_64 requires libgcj.so.10()(64bit) libgtk-java-2.8.7-13.fc13.i686 requires libgcj.so.10 libgtk-java-2.8.7-13.fc13.x86_64 requires libgcj.so.10()(64bit) 1:libguestfs-1.5.2-4.fc14.i686 requires /lib/libxtables.so.4 1:libguestfs-1.5.2-4.fc14.x86_64 requires /lib64/libxtables.so.4
need proventester approval for an update
Hiyas, an update of mine for Fedora 12 needs proventester approval: https://admin.fedoraproject.org/updates/cryptsetup-luks-1.1.3-1.fc12,libHX-3.4-1.fc12,pam_mount-2.4-2.fc12 It did not get any karma for a month, even though the critical path component (cryptsetup-luks) is afaik installed on every Fedora system and the respective F13 update got +4 within about four days. So can someone please approve this update? Regards Till pgpNw31IcV2mJ.pgp Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: need proventester approval for an update
On Thu, 05 Aug 2010 16:59:58 +0200 Till Maas opensou...@till.name wrote: Hiyas, an update of mine for Fedora 12 needs proventester approval: https://admin.fedoraproject.org/updates/cryptsetup-luks-1.1.3-1.fc12,libHX-3.4-1.fc12,pam_mount-2.4-2.fc12 It did not get any karma for a month, even though the critical path component (cryptsetup-luks) is afaik installed on every Fedora system and the respective F13 update got +4 within about four days. So can someone please approve this update? I keep seeing this update, but my f12 test box doesn't have any encrypted fs'es. ;( I can do some manual testing with a crypt loop fs. ;) kevin signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: need proventester approval for an update
On 05/08/10 20:15, Kevin Fenzi wrote: I keep seeing this update, but my f12 test box doesn't have any encrypted fs'es. ;( I can do some manual testing with a crypt loop fs. ;) kevin Would it be ok to test with an F12 Guest in Virt-Manager? everythin bar boot is luks (on the guest) -- Regards, Frank Murphy UTF_8 Encoded Friend of Fedora -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: need proventester approval for an update
On Thu, Aug 05, 2010 at 08:24:36PM +0100, Frank Murphy wrote: On 05/08/10 20:15, Kevin Fenzi wrote: I keep seeing this update, but my f12 test box doesn't have any encrypted fs'es. ;( I can do some manual testing with a crypt loop fs. ;) Would it be ok to test with an F12 Guest in Virt-Manager? everythin bar boot is luks (on the guest) Thank you both, the update is now approved and requested to be pushed to stable. Regards Till pgpFWSpm0LsWw.pgp Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Broken dependencies with Fedora 14 + updates-testing - 2010-08-05
== The results in this summary consider Test Updates! == Fixed packages compared with F-14 Branched report: LuxRender avogadro easystroke fuse-encfs glom mkvtoolnix pulsecaster python-eventlet qgis sugar-paint Still broken compared with F-14 Branched report: 58 builds Additional broken packages (by src.rpm name): gcc gnome-bluetooth gnome-color-manager gnome-media gnome-packagekit gnome-power-manager libguestfs == Broken packages in fedora-14-development-i386: 1:libguestfs-1.5.2-4.fc14.i686 requires /lib/libxtables.so.4 gnome-bluetooth-2.90.0-4.fc14.i686 requires libgnome-control-center.so.1 gnome-color-manager-2.31.4-1.fc14.i686 requires libgnome-control-center.so.1 gnome-media-2.31.5-4.fc14.i686 requires libgnome-control-center.so.1 gnome-packagekit-2.31.4-2.fc14.i686 requires libgnome-control-center.so.1 gnome-power-manager-2.31.4-1.fc14.i686 requires libgnome-control-center.so.1 == Broken packages in fedora-14-development-x86_64: 1:libguestfs-1.5.2-4.fc14.i686 requires /lib/libxtables.so.4 1:libguestfs-1.5.2-4.fc14.x86_64 requires /lib64/libxtables.so.4 gcc-gfortran-4.5.0-3.fc14.i686 requires libgfortran = 0:4.5.0-3.fc14 gcc-gfortran-4.5.0-3.fc14.i686 requires gcc = 0:4.5.0-3.fc14 gnome-bluetooth-2.90.0-4.fc14.x86_64 requires libgnome-control-center.so.1()(64bit) gnome-color-manager-2.31.4-1.fc14.x86_64 requires libgnome-control-center.so.1()(64bit) gnome-media-2.31.5-4.fc14.x86_64 requires libgnome-control-center.so.1()(64bit) gnome-packagekit-2.31.4-2.fc14.x86_64 requires libgnome-control-center.so.1()(64bit) gnome-power-manager-2.31.4-1.fc14.x86_64 requires libgnome-control-center.so.1()(64bit) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Fedora QA] #112: 'Translation/Keyboard in anaconda' Test Day - 2010/09/09
#112: 'Translation/Keyboard in anaconda' Test Day - 2010/09/09 ---+ Reporter: rhe | Owner: rhe Type: task | Status: assigned Priority: major | Milestone: Fedora 14 Component: Test Day | Version: Resolution:|Keywords: ---+ Comment (by igor): I started writing a draft page for the test day: https://fedoraproject.org/wiki/Test_Day:2010-09-09_AnacondaTranslationKeyboard We need to discuss some details such as: * Time - Maybe you guys can suggest an UTC time that might be good for you. Normally I'm available between 14 UTC - 19 UTC and 23 UTC - 04:00 UTC just to let you know. * I'm not sure if a smolt profile helps in those tests. IMHO requiring them might add unnecessary complexity for users who are willing to participate since the profiles don't show the keyboard layout, only the language. * Which test image will we use, that one specific for translators or an updated nightly build? IMHO we should use the one more updated at the time. -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/112#comment:5 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
[Fwd: Call for testers - f14 critpath update: mdadm]
I noticed Doug didn't send this to test@ , so I'm forwarding it.
Unfortunately I don't have a RAID array to test with.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
---BeginMessage---
I've submitted an updated f14 mdadm package (3.1.3-0.git20100804.2).
This update should fix a race condition in the handling of the mdadm
device map file. This file is responsible for mdadm knowing what
devices it has already seen during incremental assembly so that as new
devices show up, they can be added to the already created arrays. There
was a race condition in the locking around that file, which was fixed
with a patch I wrote. That patch didn't deal properly with dangling
lock files and so mdadm could hang if there was a stale lock file.
Upstream modified my patch to fix operation in the face of a stale lock
file (you can still generate a stale lock file, but now we deal with it
gracefully). I would very much like for this update to make it into f14
before we cut a release candidate, but since it's a critpath package,
that means it needs lots of positive karma and some QE love (I've
disabled karma automatism on the update, but I still need the karma to
push the update from testing to stable).
In particular, any testing that stresses simultaneous incremental
assembly is appreciated. For my own purposes, I created a series of
loopback devices, made a raid1 array on every pair of devices (I had 6
arrays total), then I would stop all arrays and run this command on the
command line:
for dev in loop{0..11}; do (mdadm -I /dev/$dev ); done
and check for proper assembly of all arrays. This could also be
beneficial with random killing of mdadm instances immediately after
putting them all in the background (at least some will be waiting on the
lock of the device map file, and they would be easy targets to kill I
would think...I'll leave that exercise up to the tester) followed by
rerunning the killed mdadm instances and making sure they recover from
the stale lock file and being killed mid operation OK.
In addition, it needs to be tested in a dracut environment just to make
sure that the initramfs generation hasn't been negatively impacted by
the update.
Obviously, the normal it worked with my raid arrays testing is also
much appreciated, but the above targeted testing is what's needed to
verify specifically the changes between the existing f14 build and the
current f14 build.
Any help getting this tested would be much appreciated.
The bodhi ticket:
https://admin.fedoraproject.org/updates/mdadm-3.1.3-0.git20100804.2.fc14
And if you feel like testing it on earlier releases, the other bodhi
tickets:
https://admin.fedoraproject.org/updates/mdadm-3.1.3-0.git20100804.2.fc13
https://admin.fedoraproject.org/updates/mdadm-3.1.3-0.git20100804.2.fc12
Since the package has yet to hit the updates-testing repo, the package
link in the bodhi ticket will allow you to directly download the packages.
--
Doug Ledford dledf...@redhat.com
GPG KeyID: CFBFF194
http://people.redhat.com/dledford
Infiniband specific RPMs available at
http://people.redhat.com/dledford/Infiniband
signature.asc
Description: OpenPGP digital signature
--
devel mailing list
de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel---End Message---
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 14 Alpha Blocker Bug Review Meeting 2010-08-06 @ 16:00 UTC (12 PM EST/9 AM PST)
Meeting at our regular time and location! When: 16:00 UTC (12 PM EST/9 AM PST) Where: irc.freenode.net #fedora-bugzappers Please join us. Here are the bugs we'll look at and discuss: 621102 :: NEW :: udev :: Harald Hoyer :: The installer doesn't use packages repository in DVD as default :: https://bugzilla.redhat.com/show_bug.cgi?id=621102 621200 :: ASSIGNED :: systemd :: Lennart Poettering :: [abrt] systemd-units-5-2.fc15: selabel_lookup_common: Process /bin/systemctl was killed by signal 11 (SIGSEGV) :: https://bugzilla.redhat.com/show_bug.cgi?id=621200 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Test-Announce] Fedora 14 Alpha RC1 Available Now!
Fedora 14 Alpha RC1 is now available [1]. Please refer to the following pages for download links and testing instructions. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Ideally, all Alpha priority test cases for installation [2] and desktop [3] should pass in order to meet the Alpha Release Criteria [4]. Help is available on #fedora-qa on irc.freenode.net [5], or on the test list [6]. [1] http://poelstra.fedorapeople.org/schedules/f-14/f-14-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Installation_validation_testing [3] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [4] https://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria [5] irc://irc.freenode.net/fedora-qa [6] https://admin.fedoraproject.org/mailman/listinfo/test signature.asc Description: OpenPGP digital signature ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce-- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] Fedora 14 Alpha RC1 Available Now!
Hi all, There's a kernel panic in the first stage of anaconda in x86_64 boot.iso (probably in other x86_64 images as well): Bug 621775 - kernel panic- not syncing: VFS : unable to mount root fs on unknown-block(9,2) Rgds, Hurry On Fri, 2010-08-06 at 00:40 -0400, Andre Robatino wrote: Fedora 14 Alpha RC1 is now available [1]. Please refer to the following pages for download links and testing instructions. Installation: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test Desktop: https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Ideally, all Alpha priority test cases for installation [2] and desktop [3] should pass in order to meet the Alpha Release Criteria [4]. Help is available on #fedora-qa on irc.freenode.net [5], or on the test list [6]. [1] http://poelstra.fedorapeople.org/schedules/f-14/f-14-quality-tasks.html [2] https://fedoraproject.org/wiki/QA:Installation_validation_testing [3] https://fedoraproject.org/wiki/QA:Desktop_validation_testing [4] https://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria [5] irc://irc.freenode.net/fedora-qa [6] https://admin.fedoraproject.org/mailman/listinfo/test ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- Contacts Hurry FAS Name: Rhe Timezone: UTC+8 TEL: 86-010-62608141 IRC nick: rhe #fedora-qa #fedora-zh -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
