Re: Cannot find a valid baseurl for repo: preupgrade-main
Hi, Frank, I just tested the preupgrade from f14 and f15 to f16, this also happened. That is because the mirrorlist address is not correct, you can update it as below: baseurl=http://download.fedoraproject.org/pub/fedora/linux/development/16/x86_64/os/ installurl=http://dl.fedoraproject.org/pub/alt/stage/16-Alpha.TC1/Fedora/x86_64/os/ That works fine. Hongqing - Original Message - From: Frank Murphy frankl...@gmail.com To: test@lists.fedoraproject.org Sent: Tuesday, August 2, 2011 4:53:51 PM Subject: Re: Cannot find a valid baseurl for repo: preupgrade-main On 02/08/11 09:47, Hongqing Yang wrote: I think it is the same with the bug at https://bugzilla.redhat.com/show_bug.cgi?id=727428 I'm not using anaconda, well it'n not installed. mirrormanager problem? -- Regards, Frank Murphy UTF_8 Encoded Friend of fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Anaconda: LUKSError: luks device not configured
Downloaded Fedora 16 Alpha TC1 netinstall iso x86_64 for a first brief look. Booted the included isolinux kernel+initrd. Cancelled the first LUKS passphrase prompt, but entered the passphrase for an experimental /home LV, which is shared by several dist releases on this machine. Had to enter it a second time before the installer would continue (uh?). After choosing Create custom layout, Anaconda re-examined the devices once more, then crashed: LUKSError: luks device not configured Trying to Save the backtrace, I encountered additional problems, apparently failing (silently?) to enable a network device, mouse pointer animation didn't stop spinning, and Cannot connect to Gnome keyring daemon appeared, also on a virtual console. I'll retry the installation during the day a few more times. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Plan for gobject-introspection / pygobject2 mismatch?
Hello all, The stable release of pygobject2 does not support the latest versions of gobject-introspection (that we ship in F-16 and Rawhide); this is exposed by e.g. gnome-tweak-tool not working; see https://bugzilla.redhat.com/show_bug.cgi?id=719791 for details. Mageia has a fix for this (thanks, Adam Williamson, for ferreting out other distros' bug reports), which involves making gobject-introspection generate old-style annotations. The commit for that fix (see my comment on the bugzilla link) mentions that the alternative is to use the invoke-rewrite branch of pygobject2. Since there probably are other affected apps, in addition to gnome-tweak-tool, we probably need to find a solution to this quick. Do pygobject2 and gobject-introspection maintainers have a preference as to which? My preference is to update pygobject2 -- if we revert gobject-introspection, who knows what other bugs might crop up; and pygobject2's rewrite could use some additional testers anyway. Thanks, -- Michel Alexandre Salim Fedora Project Contributor: http://fedoraproject.org/ Email: sali...@fedoraproject.org | GPG key ID: 78884778 Jabber: hir...@jabber.ccc.de | IRC: hir...@irc.freenode.net () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Fedora QA] #222: L10N Test Day
#222: L10N Test Day ---+ Reporter: noriko| Owner: Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Test Day | Version: Resolution:|Keywords: ---+ Comment (by rhe): Replying to [comment:23 noriko]: According to noriko, the specific images will be provided for L10N test day, so I guess the installed system is not suitable for test? But it's a good idea to do it before i18n desktop day. Also as Igor suggested, we still give each test day an exact date but with proper announcements. In all the test week could be organized like: * https://fedoraproject.org/wiki/Test_Day:2011-08-22_L10n_Desktop (Mon) * https://fedoraproject.org/wiki/Test_Day:2011-08-24_L10n_i18n_Installation (Wed) * https://fedoraproject.org/wiki/Test_Day:2011-08-26_I18n_Desktop (Fri) I've updated the test day schedule to include these. Feel free to discuss and modify it in need. Sorry replying late. It looks beautiful.[[BR]] One favour, is it possible or too late to change L10N test date from 2011-08-22 to 2011-08-23 Tuesday?[[BR]] The image to be used for this test will be composed on 2011-08-19 Friday. It is convenient to have a day (Monday) for preparation before testing.[[BR]] This is minor, and both dates fine but just preference. It's not late as long as it's before the test days imo.:) If you prefer the other day, can you please move the current page to the new one, and adjust the F16 test day schedule accordingly? Thanks. -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/222#comment:24 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
Problem with the link column on http://alt.fedoraproject.org/pub/alt/nightly-composes/
Pressing any taskinfo URL in the Link column of the page http://alt.fedoraproject.org/pub/alt/nightly-composes/; produces following error: Error An error has occurred while processing your request. ValueError: invalid literal for int(): 3247016 Task info Traceback (most recent call last): File /usr/share/koji-web/lib/kojiweb/publisher.py, line 16, in publish_object return old_publish_object(req, object) File /usr/lib/python2.4/site-packages/mod_python/publisher.py, line 425, in publish_object return publish_object(req,util.apply_fs_data(object, req.form, req=req)) File /usr/lib/python2.4/site-packages/mod_python/util.py, line 554, in apply_fs_data return object(**args) File /usr/share/koji-web/scripts/index.py, line 486, in taskinfo taskID = int(taskID) ValueError: invalid literal for int(): 3247016 Task info --- This happens for all items listed in the Fedora spin column -- Joachim Backes joachim.bac...@rhrk.uni-kl.de http://www.rhrk.uni-kl.de/~backes smime.p7s Description: S/MIME Cryptographic Signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Security testing
Hello, I just wanted to let everyone know that I've made a number of tests available for assessing security of the distribution. It is by no means a comprehensive auditing tool, but the scripts definitely find problems. http://people.redhat.com/sgrubb/security/ On this list, the rpm-chksec program is the one that I am most interested in people using right now. For Fedora 16, we have updated the policy to recommend all packages be compiled with partial RELRO and important programs have full RELRO enabled. This script can check individual rpms or the whole distribution at once for compliance. I have text explaining what each test does. If anyone finds problems with a script, please let me know. I will be adding more scripts as I find problems that need widespread attention. Hope this helps find and fix problems... Thanks, -Steve -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-16 Branched report: 20110803 changes
Compose started at Wed Aug 3 13:15:48 UTC 2011 Broken deps for x86_64 -- 389-ds-base-1.2.9.0-1.fc16.2.x86_64 requires libnetsnmpagent.so.25()(64bit) 389-ds-base-1.2.9.0-1.fc16.2.x86_64 requires libnetsnmpmibs.so.25()(64bit) 389-ds-base-1.2.9.0-1.fc16.2.x86_64 requires libnetsnmp.so.25()(64bit) LuxRender-0.7.1-6.fc16.x86_64 requires libboost_serialization-mt.so.1.46.1()(64bit) LuxRender-0.7.1-6.fc16.x86_64 requires libboost_iostreams-mt.so.1.46.1()(64bit) LuxRender-0.7.1-6.fc16.x86_64 requires libboost_system-mt.so.1.46.1()(64bit) LuxRender-0.7.1-6.fc16.x86_64 requires libboost_thread-mt.so.1.46.1()(64bit) LuxRender-0.7.1-6.fc16.x86_64 requires libboost_filesystem-mt.so.1.46.1()(64bit) LuxRender-0.7.1-6.fc16.x86_64 requires libboost_program_options-mt.so.1.46.1()(64bit) LuxRender-0.7.1-6.fc16.x86_64 requires libboost_regex-mt.so.1.46.1()(64bit) LuxRender-core-0.7.1-6.fc16.x86_64 requires libboost_serialization-mt.so.1.46.1()(64bit) LuxRender-core-0.7.1-6.fc16.x86_64 requires libboost_iostreams-mt.so.1.46.1()(64bit) LuxRender-core-0.7.1-6.fc16.x86_64 requires libboost_system-mt.so.1.46.1()(64bit) LuxRender-core-0.7.1-6.fc16.x86_64 requires libboost_thread-mt.so.1.46.1()(64bit) LuxRender-core-0.7.1-6.fc16.x86_64 requires libboost_filesystem-mt.so.1.46.1()(64bit) LuxRender-core-0.7.1-6.fc16.x86_64 requires libboost_program_options-mt.so.1.46.1()(64bit) LuxRender-core-0.7.1-6.fc16.x86_64 requires libboost_regex-mt.so.1.46.1()(64bit) QuantLib-test-1.1-1.fc16.x86_64 requires libboost_unit_test_framework.so.1.46.1()(64bit) acheck-0.5.1-4.fc15.noarch requires perl(Text::Aspell) almanah-0.7.3-12.fc16.x86_64 requires libcamel-1.2.so.26()(64bit) almanah-0.7.3-12.fc16.x86_64 requires libedataserverui-3.0.so.0()(64bit) almanah-0.7.3-12.fc16.x86_64 requires libcryptui.so.0()(64bit) 1:anerley-0.2.14-7.fc16.i686 requires libcamel-1.2.so.26 1:anerley-0.2.14-7.fc16.x86_64 requires libcamel-1.2.so.26()(64bit) apvlv-0.0.9.8-4.fc16.x86_64 requires libpoppler.so.13()(64bit) apvlv-0.0.9.8-4.fc16.x86_64 requires libpoppler-glib.so.6()(64bit) assogiate-0.2.1-5.fc15.x86_64 requires libgnomevfsmm-2.6.so.1()(64bit) bibletime-2.8.1-1.fc16.x86_64 requires libclucene.so.0()(64bit) 1:cheese-3.0.2-1.fc16.x86_64 requires libcogl.so.1()(64bit) 1:cheese-libs-3.0.2-1.fc16.i686 requires libcogl.so.1 1:cheese-libs-3.0.2-1.fc16.x86_64 requires libcogl.so.1()(64bit) claws-mail-plugins-geolocation-3.7.9-7.fc16.x86_64 requires libcogl.so.1()(64bit) cluster-snmp-0.18.7-1.fc16.x86_64 requires libnetsnmp.so.25()(64bit) clutter-gtk-1.0.2-1.fc16.i686 requires libcogl.so.1 clutter-gtk-1.0.2-1.fc16.x86_64 requires libcogl.so.1()(64bit) coda-backup-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit) coda-backup-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit) coda-backup-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires libseglwp.so.1()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires librvmlwp.so.1()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit) coda-client-6.9.5-6.fc16.x86_64 requires librdslwp.so.1()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires rvm-tools coda-server-6.9.5-6.fc16.x86_64 requires libseglwp.so.1()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires librvmlwp.so.1()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires libse.so.5()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires librpc2.so.5()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires liblwp.so.2()(64bit) coda-server-6.9.5-6.fc16.x86_64 requires librdslwp.so.1()(64bit) collectd-snmp-4.10.3-7.fc16.x86_64 requires libnetsnmp.so.25()(64bit) comoonics-cdsl-py-0.2-18.noarch requires comoonics-base-py comoonics-cluster-py-0.1-24.noarch requires comoonics-base-py contextkit-0.5.15-2.fc15.i686 requires libcdb.so.1 contextkit-0.5.15-2.fc15.x86_64 requires libcdb.so.1()(64bit) deskbar-applet-2.32.0-4.fc15.x86_64 requires libebook-1.2.so.10()(64bit) deskbar-applet-2.32.0-4.fc15.x86_64 requires gnome-python2-applet deskbar-applet-2.32.0-4.fc15.x86_64 requires libcamel-1.2.so.23()(64bit) dh-make-0.55-3.fc15.noarch requires debhelper ease-0.4-5.fc16.i686 requires libcogl.so.1 ease-0.4-5.fc16.x86_64 requires libcogl.so.1()(64bit) easystroke-0.5.4-1.fc16.x86_64 requires libboost_serialization-mt.so.1.46.1()(64bit)
Re: Problem with the link column on http://alt.fedoraproject.org/pub/alt/nightly-composes/
On Wed, 2011-08-03 at 13:30 +0200, Joachim Backes wrote: Pressing any taskinfo URL in the Link column of the page http://alt.fedoraproject.org/pub/alt/nightly-composes/; produces following error: Error An error has occurred while processing your request. ValueError: invalid literal for int(): 3247016 Task info Traceback (most recent call last): File /usr/share/koji-web/lib/kojiweb/publisher.py, line 16, in publish_object return old_publish_object(req, object) File /usr/lib/python2.4/site-packages/mod_python/publisher.py, line 425, in publish_object return publish_object(req,util.apply_fs_data(object, req.form, req=req)) File /usr/lib/python2.4/site-packages/mod_python/util.py, line 554, in apply_fs_data return object(**args) File /usr/share/koji-web/scripts/index.py, line 486, in taskinfo taskID = int(taskID) ValueError: invalid literal for int(): 3247016 Task info --- This happens for all items listed in the Fedora spin column The links are bad. Just delete the 'Task info' string from the end, so the URL terminates in the last digit of the build ID. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Fedora 15 updates-testing report
The following Fedora 15 Security updates need testing: https://admin.fedoraproject.org/updates/samba-3.5.10-70.fc15.1 https://admin.fedoraproject.org/updates/foomatic-4.0.7-3.fc15 https://admin.fedoraproject.org/updates/freetype-2.4.4-5.fc15 https://admin.fedoraproject.org/updates/libcap-2.22-1.fc15 https://admin.fedoraproject.org/updates/cifs-utils-5.0-2.fc15 https://admin.fedoraproject.org/updates/drupal7-7.6-1.fc15 https://admin.fedoraproject.org/updates/clamav-0.97.2-1500.fc15 https://admin.fedoraproject.org/updates/cgit-0.9.0.2-2.fc15 https://admin.fedoraproject.org/updates/wireshark-1.4.8-1.fc15 https://admin.fedoraproject.org/updates/phpMyAdmin-3.4.3.2-1.fc15 https://admin.fedoraproject.org/updates/p7zip-9.20.1-2.fc15 https://admin.fedoraproject.org/updates/openarena-0.8.5-4.fc15,quake3-1.36-11.svn2102.fc15 https://admin.fedoraproject.org/updates/libsoup-2.34.3-1.fc15 The following Fedora 15 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/openssh-5.6p1-34.fc15.1 https://admin.fedoraproject.org/updates/shadow-utils-4.1.4.2-13.fc15 https://admin.fedoraproject.org/updates/perl-Compress-Raw-Lzma-2.036-2.fc15,xz-5.0.3-1.fc15 https://admin.fedoraproject.org/updates/PackageKit-0.6.17-1.fc15 https://admin.fedoraproject.org/updates/logrotate-3.7.9-14.fc15 https://admin.fedoraproject.org/updates/kernel-2.6.40-3.fc15 https://admin.fedoraproject.org/updates/cyrus-sasl-2.1.23-18.fc15 https://admin.fedoraproject.org/updates/pinentry-0.8.1-4.fc15 https://admin.fedoraproject.org/updates/sendmail-8.14.5-3.fc15 https://admin.fedoraproject.org/updates/nss-3.12.10-5.fc15 https://admin.fedoraproject.org/updates/nspr-4.8.8-4.fc15 https://admin.fedoraproject.org/updates/nss-softokn-3.12.10-4.fc15 https://admin.fedoraproject.org/updates/xorg-x11-drv-wacom-0.11.1-3.fc15 https://admin.fedoraproject.org/updates/freetype-2.4.4-5.fc15 https://admin.fedoraproject.org/updates/mash-0.5.22-1.fc15 https://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.904-14.fc15.1 https://admin.fedoraproject.org/updates/lldpad-0.9.41-3.fc15 https://admin.fedoraproject.org/updates/libfprint-0.4.0-1.fc15,fprintd-0.4.1-1.fc15 The following builds have been pushed to Fedora 15 updates-testing bind-9.8.0-9.P4.fc15 bind-dyndb-ldap-0.2.0-4.fc15 cabal-dev-0.8-2.fc15 jd-2.8.2-0.3.rc110803.fc15 klt-1.3.4-1.fc15 luci-0.25.0-1.fc15 memcached-1.4.6-1.fc15 mercurial-1.9.1-1.fc15 openssh-5.6p1-34.fc15.1 python-rhsm-0.96.8-1.fc15 ql2400-firmware-5.06.00-1.fc15 ql2500-firmware-5.06.00-1.fc15 rwall-0.17-32.fc15 samba-3.5.10-70.fc15.1 wget-1.12-4.fc15 Details about builds: bind-9.8.0-9.P4.fc15 (FEDORA-2011-10296) The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) server Update Information: This update fixes following issues: * named could have crashed during reload/shutdown when bind-dyndb-ldap was used (BZ#725741) * named could have hung due race-condition in bind-dyndb-ldap ChangeLog: * Wed Aug 3 2011 Adam Tkac atkac redhat com 32:9.8.0-9.P4 - improve patch for #725741 * Tue Jul 26 2011 Adam Tkac atkac redhat com 32:9.8.0-8.P4 - named could have crashed during reload when dyndb module is used (#725741) References: [ 1 ] Bug #725741 - [abrt] bind-9.8.0-7.P4.fc15: __GI_raise: Process /usr/sbin/named was killed by signal 6 (SIGABRT) https://bugzilla.redhat.com/show_bug.cgi?id=725741 bind-dyndb-ldap-0.2.0-4.fc15 (FEDORA-2011-10296) LDAP back-end plug-in for BIND Update Information: This update fixes following issues: * named could have crashed during reload/shutdown when bind-dyndb-ldap was used (BZ#725741) * named could have hung due race-condition in bind-dyndb-ldap ChangeLog: * Wed Aug 3 2011 Adam Tkac atkac redhat com - 0.2.0-4 - fix race condition in semaphore_wait (#727856) References: [ 1 ] Bug #725741 - [abrt] bind-9.8.0-7.P4.fc15: __GI_raise: Process /usr/sbin/named was killed by signal 6 (SIGABRT) https://bugzilla.redhat.com/show_bug.cgi?id=725741
Fedora 14 updates-testing report
The following Fedora 14 Security updates need testing: https://admin.fedoraproject.org/updates/samba-3.5.10-78.fc14 https://admin.fedoraproject.org/updates/foomatic-4.0.7-2.fc14 https://admin.fedoraproject.org/updates/freetype-2.4.2-5.fc14 https://admin.fedoraproject.org/updates/cifs-utils-4.8.1-7.fc14 https://admin.fedoraproject.org/updates/drupal7-7.6-1.fc14 https://admin.fedoraproject.org/updates/clamav-0.97.2-1400.fc14 https://admin.fedoraproject.org/updates/cgit-0.9.0.2-2.fc14 https://admin.fedoraproject.org/updates/wireshark-1.4.8-1.fc14 https://admin.fedoraproject.org/updates/NetworkManager-0.8.4-2.git20110622.fc14 https://admin.fedoraproject.org/updates/system-config-firewall-1.2.27-2.fc14 https://admin.fedoraproject.org/updates/libsndfile-1.0.25-1.fc14 https://admin.fedoraproject.org/updates/glpi-0.78.5-2.svn14966.fc14,glpi-data-injection-2.0.2-1.fc14,glpi-mass-ocs-import-1.4.2-1.fc14,glpi-pdf-0.7.2-1.fc14 https://admin.fedoraproject.org/updates/phpMyAdmin-3.4.3.2-1.fc14 https://admin.fedoraproject.org/updates/libcap-2.22-1.fc14 https://admin.fedoraproject.org/updates/quake3-1.36-11.svn2102.fc14,openarena-0.8.5-4.fc14 https://admin.fedoraproject.org/updates/libsoup-2.32.2-2.fc14 https://admin.fedoraproject.org/updates/dbus-1.4.0-3.fc14 https://admin.fedoraproject.org/updates/tomcat6-6.0.26-21.fc14 https://admin.fedoraproject.org/updates/openldap-2.4.23-10.fc14 https://admin.fedoraproject.org/updates/gdk-pixbuf2-2.22.0-2.fc14 The following Fedora 14 Critical Path updates have yet to be approved: https://admin.fedoraproject.org/updates/dbus-1.4.0-3.fc14 https://admin.fedoraproject.org/updates/libsoup-2.32.2-2.fc14 https://admin.fedoraproject.org/updates/libcap-2.22-1.fc14 https://admin.fedoraproject.org/updates/pinentry-0.8.1-4.fc14 https://admin.fedoraproject.org/updates/freetype-2.4.2-5.fc14 https://admin.fedoraproject.org/updates/mdadm-3.1.3-0.git20100804.3.fc14 https://admin.fedoraproject.org/updates/libsndfile-1.0.25-1.fc14 https://admin.fedoraproject.org/updates/sed-4.2.1-6.fc14 https://admin.fedoraproject.org/updates/ModemManager-0.4.998-1.git20110706.fc14 https://admin.fedoraproject.org/updates/unique-1.1.6-3.fc14 https://admin.fedoraproject.org/updates/xorg-x11-drv-savage-2.3.2-3.fc14 https://admin.fedoraproject.org/updates/mash-0.5.22-1.fc14 https://admin.fedoraproject.org/updates/gdk-pixbuf2-2.22.0-2.fc14 https://admin.fedoraproject.org/updates/perl-5.12.4-146.fc14 https://admin.fedoraproject.org/updates/policycoreutils-2.0.85-30.2.fc14 https://admin.fedoraproject.org/updates/xorg-x11-drv-openchrome-0.2.904-8.fc14.2 https://admin.fedoraproject.org/updates/xorg-x11-drv-qxl-0.0.21-3.fc14 https://admin.fedoraproject.org/updates/xorg-x11-drv-nouveau-0.0.16-14.20101010git8c8f15c.fc14 https://admin.fedoraproject.org/updates/libconcord-0.23-5.fc14,udev-161-9.fc14,concordance-0.23-2.fc14 https://admin.fedoraproject.org/updates/openldap-2.4.23-10.fc14 The following builds have been pushed to Fedora 14 updates-testing dump-0.4-0.9.b43.fc14 jd-2.8.2-0.3.rc110803.fc14 klt-1.3.4-1.fc14 luci-0.25.0-1.fc14 python-rhsm-0.96.8-1.fc14 ql2400-firmware-5.06.00-1.fc14 ql2500-firmware-5.06.00-1.fc14 samba-3.5.10-78.fc14 wget-1.12-4.fc14 Details about builds: dump-0.4-0.9.b43.fc14 (FEDORA-2011-10284) Programs for backing up and restoring ext2/ext3 filesystems Update Information: This update fixes following issue: * `dump -w` didn't recognize ext4 filesystems. (BZ#727657) ChangeLog: * Thu Dec 2 2010 Jan Görig jgorig redhat com 0.4-0.9.b42 - fix dump -w does not work on ext4 fielsystems (#658890) References: [ 1 ] Bug #727657 - dump -w does not work for ext4 https://bugzilla.redhat.com/show_bug.cgi?id=727657 jd-2.8.2-0.3.rc110803.fc14 (FEDORA-2011-10282) A 2ch browser Update Information: New version 2.8.2 rc 110803 is released. ChangeLog: * Wed Aug 3 2011 Mamoru Tasaka mtas...@fedoraproject.org - 2.8.2-0.3.rc110803 - 2.8.2 rc 110803 klt-1.3.4-1.fc14 (FEDORA-2011-10291) An
Re: [Fedora QA] #222: L10N Test Day
#222: L10N Test Day ---+ Reporter: noriko| Owner: Type: task | Status: new Priority: major | Milestone: Fedora 16 Component: Test Day | Version: Resolution:|Keywords: ---+ Comment (by igor): Replying to [comment:23 noriko]: Sorry replying late. It looks beautiful.[[BR]] One favour, is it possible or too late to change L10N test date from 2011-08-22 to 2011-08-23 Tuesday?[[BR]] The image to be used for this test will be composed on 2011-08-19 Friday. It is convenient to have a day (Monday) for preparation before testing.[[BR]] This is minor, and both dates fine but just preference. No problem Noriko but remember that we are proposing a Test Week, so if you want to keep the test day on the current date and run the tests over the week there is no problem either. -- Ticket URL: https://fedorahosted.org/fedora-qa/ticket/222#comment:25 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
Post-TC1 strategizin'
I thought it'd be a good idea to take a step back and plan a strategy for post-Alpha TC1. We're in trouble for Alpha; we're a long way behind schedule, and we have a lot of blocker bugs remaining. TC1 is in pretty bad shape. By policy, we can't call a build an RC until all known blockers are fixed in it. I'm thinking we may be a way out from that. So, we have the choice of waiting for all blockers to be resolved before we do the next compose, which might take a while, or doing a TC2 with the most critical fixes in. What approach do people think we should take? Would a TC2 have any value or should we just clean up all the blockers we know about before we do another build, and make it RC1? I'm thinking we're likely to slip the Alpha at least a week either way, unfortunately. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Post-TC1 strategizin'
On 08/03/2011 08:41 PM, Adam Williamson wrote: I thought it'd be a good idea to take a step back and plan a strategy for post-Alpha TC1. We're in trouble for Alpha; we're a long way behind schedule, and we have a lot of blocker bugs remaining. TC1 is in pretty bad shape. By policy, we can't call a build an RC until all known blockers are fixed in it. I'm thinking we may be a way out from that. So, we have the choice of waiting for all blockers to be resolved before we do the next compose, which might take a while, or doing a TC2 with the most critical fixes in. What approach do people think we should take? Would a TC2 have any value or should we just clean up all the blockers we know about before we do another build, and make it RC1? I'm thinking we're likely to slip the Alpha at least a week either way, unfortunately. I vote for cleaning up as many of the blockers as you can in a week to match the expected week slip. Prioritize them first? I suspect this is vacation time for many, so a longer slip might be in the offing. -- Regards, OldFart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Post-TC1 strategizin'
Honestly I rather having the extra TC build to weed out any potential blocker that could arise during fixing and spinning of the known blockers. I've seen that happen in the past and an extra spin can help make sure RC is better at the start. -- John Watzke On Aug 3, 2011 8:12 PM, Clyde E. Kunkel clydekunkel7...@cox.net wrote: On 08/03/2011 08:41 PM, Adam Williamson wrote: I thought it'd be a good idea to take a step back and plan a strategy for post-Alpha TC1. We're in trouble for Alpha; we're a long way behind schedule, and we have a lot of blocker bugs remaining. TC1 is in pretty bad shape. By policy, we can't call a build an RC until all known blockers are fixed in it. I'm thinking we may be a way out from that. So, we have the choice of waiting for all blockers to be resolved before we do the next compose, which might take a while, or doing a TC2 with the most critical fixes in. What approach do people think we should take? Would a TC2 have any value or should we just clean up all the blockers we know about before we do another build, and make it RC1? I'm thinking we're likely to slip the Alpha at least a week either way, unfortunately. I vote for cleaning up as many of the blockers as you can in a week to match the expected week slip. Prioritize them first? I suspect this is vacation time for many, so a longer slip might be in the offing. -- Regards, OldFart -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Post-TC1 strategizin'
On Wed, 2011-08-03 at 21:08 -0400, Clyde E. Kunkel wrote: I suspect this is vacation time for many, so a longer slip might be in the offing. No-one gets any vacation while there are still open blockers. ;) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F16 TC1
Could we get a respin of TC1 that can install the software development choice without missing files? If there is a URL that actually works for a net install, could someone post it exactly? -- Chuck Forsberg WA7KGX N2469R c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc The High Reliability Software 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Security testing
On Wednesday, August 03, 2011 03:29:00 PM Adam Williamson wrote: I just wanted to let everyone know that I've made a number of tests available for assessing security of the distribution. It is by no means a comprehensive auditing tool, but the scripts definitely find problems. http://people.redhat.com/sgrubb/security/ On this list, the rpm-chksec program is the one that I am most interested in people using right now. For Fedora 16, we have updated the policy to recommend all packages be compiled with partial RELRO and important programs have full RELRO enabled. This script can check individual rpms or the whole distribution at once for compliance. I have text explaining what each test does. If anyone finds problems with a script, please let me know. I will be adding more scripts as I find problems that need widespread attention. Hope this helps find and fix problems... Looks like interesting stuff. Would any of these be appropriate to be integrated into AutoQA so they could be run regularly? Honestly, I don't know. On the one hand, I have some scripts that are good for fedora QE in general. For example, the shell error test...why would anyone purposely write shell script that does not work? This can always be fixed before a release. Some tests are still under development like the ELF binary well known tmp file test. This can make some false positives, but there are enough good things in it to start asking real questions about packages...like.../home/cagney/tmp/a.out...why is that in any program? But the chroot tests are solid. As are the exec stack tests. So, yes there are things that can be automated so problems are not shipped. -Steve -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Security testing
On Wednesday, August 03, 2011 03:29:00 PM Adam Williamson wrote: Looks like interesting stuff. Would any of these be appropriate to be integrated into AutoQA so they could be run regularly? One thing I want to emphasize, every single script on that page found real problems in F15. I opened bugs on some things, but its fertile ground for anyone with ambition. -Steve -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Security testing
On Wed, 2011-08-03 at 23:09 -0400, Steve Grubb wrote: On Wednesday, August 03, 2011 03:29:00 PM Adam Williamson wrote: I just wanted to let everyone know that I've made a number of tests available for assessing security of the distribution. It is by no means a comprehensive auditing tool, but the scripts definitely find problems. http://people.redhat.com/sgrubb/security/ On this list, the rpm-chksec program is the one that I am most interested in people using right now. For Fedora 16, we have updated the policy to recommend all packages be compiled with partial RELRO and important programs have full RELRO enabled. This script can check individual rpms or the whole distribution at once for compliance. I have text explaining what each test does. If anyone finds problems with a script, please let me know. I will be adding more scripts as I find problems that need widespread attention. Hope this helps find and fix problems... Looks like interesting stuff. Would any of these be appropriate to be integrated into AutoQA so they could be run regularly? Honestly, I don't know. On the one hand, I have some scripts that are good for fedora QE in general. For example, the shell error test...why would anyone purposely write shell script that does not work? This can always be fixed before a release. Some tests are still under development like the ELF binary well known tmp file test. This can make some false positives, but there are enough good things in it to start asking real questions about packages...like.../home/cagney/tmp/a.out...why is that in any program? But the chroot tests are solid. As are the exec stack tests. So, yes there are things that can be automated so problems are not shipped. Awesome. CCing autoqa-devel on the reply, then; is anyone from AutoQA willing to work with Steve to take a look at his tests and identify good candidates for bringing into AutoQA? Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
FC16 Alpha testing
Hello All, I have tried to install the FC16 Alpha TC1 on VMWare virtual machine, after selecting the hard disk for the portioning getting the error message as no usable disk has found. Any clue what I am missing here?? BTW it's detecting the harddisk and showing it's size also (20 GB) in the previous step before throwing the above error message. Regards, Srinivasa N -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
