Fedora 25 updates-testing report
The following Fedora 25 Security updates need testing: Age URL 184 https://bodhi.fedoraproject.org/updates/FEDORA-2016-d79ba708cb exim-4.87.1-1.fc25 83 https://bodhi.fedoraproject.org/updates/FEDORA-2017-e2d17af41e python-XStatic-jquery-ui-1.12.0.1-4.fc25 26 https://bodhi.fedoraproject.org/updates/FEDORA-2017-7dbbbafea6 runc-1.0.0-7.git6394544.fc25.2 22 https://bodhi.fedoraproject.org/updates/FEDORA-2017-ec3c82e64d libstaroffice-0.0.3-3.fc25 22 https://bodhi.fedoraproject.org/updates/FEDORA-2017-5d7498559f nodejs-brace-expansion-1.1.7-1.fc25 13 https://bodhi.fedoraproject.org/updates/FEDORA-2017-bcfa3569d6 libmwaw-0.3.11-3.fc25 8 https://bodhi.fedoraproject.org/updates/FEDORA-2017-f68c93aaac kmail-16.12.3-2.fc25 8 https://bodhi.fedoraproject.org/updates/FEDORA-2017-bb1ecba1bc kf5-messagelib-16.12.3-2.fc25 8 https://bodhi.fedoraproject.org/updates/FEDORA-2017-a11f853361 kdepim4-4.14.10-31.fc25 7 https://bodhi.fedoraproject.org/updates/FEDORA-2017-708adeb9b6 libsndfile-1.0.28-3.fc25 7 https://bodhi.fedoraproject.org/updates/FEDORA-2017-0d636042ef drupal8-8.3.4-1.fc25 6 https://bodhi.fedoraproject.org/updates/FEDORA-2017-c3149b5fcb xen-4.7.2-7.fc25 5 https://bodhi.fedoraproject.org/updates/FEDORA-2017-63aca509fb zabbix-3.0.9-1.fc25 4 https://bodhi.fedoraproject.org/updates/FEDORA-2017-7591a8e2c9 globus-xio-5.16-1.fc25 globus-net-manager-0.17-1.fc25 globus-gass-cache-program-6.7-1.fc25 globus-gass-copy-9.27-1.fc25 globus-gssapi-gsi-12.16-1.fc25 globus-gram-job-manager-14.36-1.fc25 globus-gridftp-server-12.2-1.fc25 globus-io-11.9-1.fc25 globus-xio-gsi-driver-3.11-1.fc25 globus-xio-pipe-driver-3.10-1.fc25 globus-xio-udt-driver-1.27-1.fc25 myproxy-6.1.28-1.fc25 globus-ftp-client-8.35-2.fc25 4 https://bodhi.fedoraproject.org/updates/FEDORA-2017-38113758e7 drupal7-7.56-1.fc25 3 https://bodhi.fedoraproject.org/updates/FEDORA-2017-6f7d6fbccc php-horde-Horde-Image-2.5.1-1.fc25 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-bff1b87765 webkitgtk4-2.16.5-1.fc25 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-4c57da6642 libmtp-1.1.13-1.fc25 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-372bb1edb3 libdb-5.3.28-24.fc25 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-75c571778e irssi-1.0.3-1.fc25 1 https://bodhi.fedoraproject.org/updates/FEDORA-2017-620085cede httpd-2.4.26-1.fc25 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-03954b6dc4 jetty-test-helper-3.1-3.fc25 jetty-alpn-8.1.11-2.v20170118.fc25 jetty-9.4.6-1.v20170531.fc25 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-d3bc944153 pius-2.2.4-1.fc25 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-a348b32eb5 libgcrypt-1.7.8-1.fc25 The following Fedora 25 Critical Path updates have yet to be approved: Age URL 26 https://bodhi.fedoraproject.org/updates/FEDORA-2017-613a72e282 lorax-25.22-1.fc25 13 https://bodhi.fedoraproject.org/updates/FEDORA-2017-a83e0e61d6 fwupd-0.9.4-1.fc25 10 https://bodhi.fedoraproject.org/updates/FEDORA-2017-bd92718a5a pungi-4.1.16-3.fc25 8 https://bodhi.fedoraproject.org/updates/FEDORA-2017-82f4a3afee storaged-2.6.2-6.fc25 7 https://bodhi.fedoraproject.org/updates/FEDORA-2017-708adeb9b6 libsndfile-1.0.28-3.fc25 6 https://bodhi.fedoraproject.org/updates/FEDORA-2017-c3149b5fcb xen-4.7.2-7.fc25 5 https://bodhi.fedoraproject.org/updates/FEDORA-2017-d90aa59a73 libguestfs-1.36.5-1.fc25 5 https://bodhi.fedoraproject.org/updates/FEDORA-2017-0187b2a605 selinux-policy-3.13.1-225.19.fc25 3 https://bodhi.fedoraproject.org/updates/FEDORA-2017-80862de14e perl-Scalar-List-Utils-1.48-1.fc25 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-413688447e vim-8.0.679-1.fc25 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-372bb1edb3 libdb-5.3.28-24.fc25 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-bff1b87765 webkitgtk4-2.16.5-1.fc25 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-e31a3d0217 thunderbird-52.2.1-1.fc25 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-a348b32eb5 libgcrypt-1.7.8-1.fc25 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-92a040da1a rsync-3.1.2-4.fc25 The following builds have been pushed to Fedora 25 updates-testing boomaga-0.9.1-1.git5ae3c05.fc25 cherrytree-0.38.1-1.fc25 cjs-3.4.2-1.fc25 cscope-15.8b-3.fc25 egl-wayland-1.0.2-0.1.20170628git818b613.fc25 eiskaltdcpp-2.2.11-4.20170207git3b9c502.fc25 fedmsg-0.18.4-1.fc25 freeipa-4.4.4-4.fc25 gnome-shell-extension-media-player-indicator-0-0.12.20170629git7bc47fd.fc25 golang-1.7.6-2.fc25 jetty-9.4.6-1.v20170531.fc25 jetty-alpn-8.1.11-2.v20170118.fc25 jetty-test-helper-3.1-3.fc25 klavaro-3.02-5.fc25 libgcrypt-1.7.8-1.fc25 lilypond-2.19.63-1.fc25 lilypond-doc-2.19.63-1.fc25
Fedora 24 updates-testing report
The following Fedora 24 Security updates need testing: Age URL 191 https://bodhi.fedoraproject.org/updates/FEDORA-2016-26f9817b08 squid-3.5.23-1.fc24 184 https://bodhi.fedoraproject.org/updates/FEDORA-2016-eaaa9c4a08 exim-4.87.1-1.fc24 147 https://bodhi.fedoraproject.org/updates/FEDORA-2017-ece16ba6ba runc-1.0.0-5.rc2.gitc91b5be.fc24 83 https://bodhi.fedoraproject.org/updates/FEDORA-2017-8330a48ca2 python-XStatic-jquery-ui-1.12.0.1-1.fc24 22 https://bodhi.fedoraproject.org/updates/FEDORA-2017-5f1006afb1 libstaroffice-0.0.3-3.fc24 22 https://bodhi.fedoraproject.org/updates/FEDORA-2017-a1f4c48c68 nodejs-brace-expansion-1.1.7-1.fc24 13 https://bodhi.fedoraproject.org/updates/FEDORA-2017-bbae64fdc2 libmwaw-0.3.11-3.fc24 8 https://bodhi.fedoraproject.org/updates/FEDORA-2017-b8d76bef4e chromium-native_client-59.0.3071.86-1.20170607gitaac1de2.fc24 8 https://bodhi.fedoraproject.org/updates/FEDORA-2017-4932c9b886 c-ares-1.13.0-1.fc24 6 https://bodhi.fedoraproject.org/updates/FEDORA-2017-5596f2f94d openvpn-2.3.17-1.fc24 6 https://bodhi.fedoraproject.org/updates/FEDORA-2017-2cfb239358 libsndfile-1.0.28-3.fc24 6 https://bodhi.fedoraproject.org/updates/FEDORA-2017-3159dd230a drupal8-8.3.4-1.fc24 6 https://bodhi.fedoraproject.org/updates/FEDORA-2017-b3bdaf58bc xen-4.6.5-7.fc24 5 https://bodhi.fedoraproject.org/updates/FEDORA-2017-e0a9e51dd5 graphite2-1.3.10-1.fc24 5 https://bodhi.fedoraproject.org/updates/FEDORA-2017-d191fb7fce zabbix-3.0.9-1.fc24 4 https://bodhi.fedoraproject.org/updates/FEDORA-2017-5f8ebbd2b1 globus-xio-5.16-1.fc24 globus-net-manager-0.17-1.fc24 globus-gass-cache-program-6.7-1.fc24 globus-gass-copy-9.27-1.fc24 globus-gssapi-gsi-12.16-1.fc24 globus-gram-job-manager-14.36-1.fc24 globus-gridftp-server-12.2-1.fc24 globus-io-11.9-1.fc24 globus-xio-gsi-driver-3.11-1.fc24 globus-xio-pipe-driver-3.10-1.fc24 globus-xio-udt-driver-1.27-1.fc24 myproxy-6.1.28-1.fc24 globus-ftp-client-8.35-2.fc24 4 https://bodhi.fedoraproject.org/updates/FEDORA-2017-e8a2017b3c drupal7-7.56-1.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-37f68e3534 webkitgtk4-2.16.5-1.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-299525e757 php-horde-Horde-Image-2.5.1-1.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-6b1f07acd9 flatpak-0.8.7-1.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-d26266eb32 libmtp-1.1.13-1.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-014d67fa9d libdb-5.3.28-24.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-56cf7067e7 irssi-1.0.3-1.fc24 1 https://bodhi.fedoraproject.org/updates/FEDORA-2017-72f0c1ea9c systemd-229-22.fc24 1 https://bodhi.fedoraproject.org/updates/FEDORA-2017-cf9599a306 httpd-2.4.26-1.fc24 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-06d7ff5a5d pius-2.2.4-1.fc24 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-3b70d0b976 libgcrypt-1.7.8-1.fc24 The following Fedora 24 Critical Path updates have yet to be approved: Age URL 70 https://bodhi.fedoraproject.org/updates/FEDORA-2017-e1905fd566 koji-1.12.0-2.fc24 15 https://bodhi.fedoraproject.org/updates/FEDORA-2017-07fed9b000 libteam-1.27-1.fc24 11 https://bodhi.fedoraproject.org/updates/FEDORA-2017-ce8c7053eb audit-2.7.7-1.fc24 6 https://bodhi.fedoraproject.org/updates/FEDORA-2017-2cfb239358 libsndfile-1.0.28-3.fc24 5 https://bodhi.fedoraproject.org/updates/FEDORA-2017-e0a9e51dd5 graphite2-1.3.10-1.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-014d67fa9d libdb-5.3.28-24.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-bbfb70fc1d kernel-4.11.7-100.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-6b1f07acd9 flatpak-0.8.7-1.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-3e62f0d34b perl-5.22.3-371.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-37f68e3534 webkitgtk4-2.16.5-1.fc24 1 https://bodhi.fedoraproject.org/updates/FEDORA-2017-72f0c1ea9c systemd-229-22.fc24 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-6c2a7b1453 thunderbird-52.2.1-1.fc24 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-3b70d0b976 libgcrypt-1.7.8-1.fc24 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-8100aed299 rsync-3.1.2-4.fc24 The following builds have been pushed to Fedora 24 updates-testing cherrytree-0.38.1-1.fc24 eiskaltdcpp-2.2.11-4.20170207git3b9c502.fc24 grip-3.4.2-2.fc24 libgcrypt-1.7.8-1.fc24 lilypond-2.19.63-1.fc24 lilypond-doc-2.19.63-1.fc24 mame-0.187-1.fc24 mpage-2.5.7-1.fc24 nagios-4.3.2-5.fc24 nodejs-4.8.3-5.fc24 openttd-1.7.1-1.fc24 perl-Devel-REPL-1.003028-2.fc24 php-nikic-php-parser3-3.0.6-1.fc24 pius-2.2.4-1.fc24 resultsdb-2.0.5-1.fc24 rpkg-1.49-5.fc24
Heads up: short-lived 26 RC-1.1 probably coming soon
Hi folks! I've just requested a 26 Final candidate compose, which will show up (assuming it succeeds) in several hours, under the name '26 RC-1.1'. Despite the name, this compose will not be a true 'release candidate' compose for 26 Final, as several blockers are still not fixed. However, we wanted to run a compose just to check that everything is set up properly and the quite large number of FE fixes that will be pulled in don't cause any unexpected problems. The compose will be nominated for validation testing as usual, and any testing anyone wants to do on it would be most welcome, but be aware that we're hoping to do a 'real' 26 Final RC compose tomorrow, so this first candidate compose will probably be short-lived. I'll let you know if anything changes. Thanks, everyone! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora 26 updates-testing report
The following Fedora 26 Security updates need testing: Age URL 83 https://bodhi.fedoraproject.org/updates/FEDORA-2017-1bf5a0ce01 python-XStatic-jquery-ui-1.12.0.1-2.fc26 22 https://bodhi.fedoraproject.org/updates/FEDORA-2017-2522df3526 nodejs-brace-expansion-1.1.7-1.fc26 6 https://bodhi.fedoraproject.org/updates/FEDORA-2017-5c6a9b07a3 xen-4.8.1-4.fc26 6 https://bodhi.fedoraproject.org/updates/FEDORA-2017-2df90e929a drupal8-8.3.4-1.fc26 5 https://bodhi.fedoraproject.org/updates/FEDORA-2017-5c8a4ebccd zabbix-3.0.9-1.fc26 4 https://bodhi.fedoraproject.org/updates/FEDORA-2017-6874606e19 drupal7-7.56-1.fc26 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-28387b61fd php-horde-Horde-Image-2.5.1-1.fc26 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-64f47504e4 ocaml-4.04.0-10.fc26 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-69fdb38f3e libmtp-1.1.13-1.fc26 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-2b68e14594 libdb-5.3.28-24.fc26 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-2f30e218e7 irssi-1.0.3-1.fc26 1 https://bodhi.fedoraproject.org/updates/FEDORA-2017-e83c26a8c9 qt5-qtwebengine-5.9.0-4.fc26 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-4e2312892e jetty-9.4.6-1.v20170531.fc26 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-808dbfe1d3 pius-2.2.4-1.fc26 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-22107b1986 libgcrypt-1.7.8-1.fc26 The following Fedora 26 Critical Path updates have yet to be approved: Age URL 10 https://bodhi.fedoraproject.org/updates/FEDORA-2017-0dec8a74c5 pungi-4.1.16-3.fc26 6 https://bodhi.fedoraproject.org/updates/FEDORA-2017-59ca80e001 libguestfs-1.36.5-1.fc26 6 https://bodhi.fedoraproject.org/updates/FEDORA-2017-83bfe1d789 flatpak-0.9.6-1.fc26 6 https://bodhi.fedoraproject.org/updates/FEDORA-2017-0d905dbef8 util-linux-2.30-1.fc26 6 https://bodhi.fedoraproject.org/updates/FEDORA-2017-5c6a9b07a3 xen-4.8.1-4.fc26 2 https://bodhi.fedoraproject.org/updates/FEDORA-2017-2b68e14594 libdb-5.3.28-24.fc26 1 https://bodhi.fedoraproject.org/updates/FEDORA-2017-364e5206ba opus-1.2.1-1.fc26 1 https://bodhi.fedoraproject.org/updates/FEDORA-2017-06d188a0fc webkitgtk4-2.16.5-1.fc26 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-2e8066314b thunderbird-52.2.1-1.fc26 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-22107b1986 libgcrypt-1.7.8-1.fc26 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-b4786b0b24 tracker-1.12.1-1.fc26 0 https://bodhi.fedoraproject.org/updates/FEDORA-2017-8e092b9210 rsync-3.1.2-5.fc26 The following builds have been pushed to Fedora 26 updates-testing boomaga-0.9.1-1.git5ae3c05.fc26 cherrytree-0.38.1-1.fc26 cjs-3.4.2-1.fc26 cockpit-144-1.fc26 egl-wayland-1.0.2-0.1.20170628git818b613.fc26 eiskaltdcpp-2.2.11-4.20170207git3b9c502.fc26 fedmsg-0.18.4-1.fc26 gnome-shell-extension-media-player-indicator-0-0.12.20170629git7bc47fd.fc26 golang-github-gonum-lapack-0-0.7.git88ec467.fc26 grass-7.2.1-1.fc26 jetty-9.4.6-1.v20170531.fc26 klavaro-3.02-5.fc26 libarcus-2.6.1-1.fc26 libgcrypt-1.7.8-1.fc26 libsavitar-2.6.1-1.fc26 lilypond-2.19.63-1.fc26 lilypond-doc-2.19.63-1.fc26 mame-0.187-1.fc26 mpage-2.5.7-1.fc26 nagios-4.3.2-5.fc26 nodejs-6.11.0-1.fc26 openttd-1.7.1-1.fc26 perl-Devel-REPL-1.003028-4.fc26 perl-Mail-Box-IMAP4-3.001-1.fc26 php-nikic-php-parser3-3.0.6-1.fc26 php-pear-1.10.5-2.fc26 pius-2.2.4-1.fc26 python-uranium-2.6.1-2.fc26 resultsdb-2.0.5-1.fc26 rpkg-1.49-5.fc26 rsync-3.1.2-5.fc26 rubygem-test-unit-3.2.5-100.fc26 screen-4.6.0-1.fc26 snapd-glib-1.13-2.fc26 thunderbird-52.2.1-1.fc26 tracker-1.12.1-1.fc26 vdr-epg2vdr-1.1.73-1.fc26 wine-2.11-1.fc26 wingpanel-indicator-session-2.0.2-1.fc26 xed-1.4.4-1.fc26 xreader-1.4.4-1.fc26 xviewer-1.4.3-1.fc26 youtube-dl-2017.06.25-1.fc26 Details about builds: boomaga-0.9.1-1.git5ae3c05.fc26 (FEDORA-2017-01093f1788) A virtual printer for viewing a document before printing Update Information: Update to 0.9.1-1.git5ae3c05 cherrytree-0.38.1-1.fc26 (FEDORA-2017-b3a53c8cb3) Hierarchical note taking application Update Information: update to latest version 0.38.1 References: [ 1 ] Bug #1460404 - cherrytree-0.38.1 is available
[Test-Announce] Reminder: Fedora 26 Upgrade Test Day tomorrow
Just a reminder, as the announcement was over a week ago, that tomorrow is Fedora 26 Upgrade Test Day in #fedora-test-day on Freenode! https://fedoraproject.org/wiki/Test_Day:2017-06-30_Upgrade_Test_Day Please come out and help test if you can. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Re: Self-Introduction
Welcome, David! (: signature.asc Description: PGP signature ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Schedule concern next week: holidays ahead!
On Thu, 2017-06-29 at 10:19 -0400, Peter Jones wrote: > On Wed, Jun 28, 2017 at 06:53:58PM -0700, Adam Williamson wrote: > > There are five proposed blockers. My professional guesstimate *at this > > point* is that at least four of them will probably be rejected, though > > that could change with more data (attention pjones: if #1418360 and > > #1451071 are more serious than they seem to us so far, please do let us > > know). > > They absolutely are: basically Secure Boot doesn't trigger kmod > signature checking, read-only /dev/mem, etc., in the current trees. > This update fixes a grub bug that's triggering that behavior in the > newer kernels, but was not triggering it in the older ones. > > So yes, I very much think these should be blockers. Ah, from the description I thought it was purely an informational thing (just the user couldn't tell whether SB was enabled, but if it was in fact enabled, it was working properly). So basically the appropriate protections aren't put in place when SB is active, making it quite easy to subvert SB? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Schedule concern next week: holidays ahead!
On Wed, Jun 28, 2017 at 06:53:58PM -0700, Adam Williamson wrote: > There are five proposed blockers. My professional guesstimate *at this > point* is that at least four of them will probably be rejected, though > that could change with more data (attention pjones: if #1418360 and > #1451071 are more serious than they seem to us so far, please do let us > know). They absolutely are: basically Secure Boot doesn't trigger kmod signature checking, read-only /dev/mem, etc., in the current trees. This update fixes a grub bug that's triggering that behavior in the newer kernels, but was not triggering it in the older ones. So yes, I very much think these should be blockers. -- Peter ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Schedule concern next week: holidays ahead!
> > Given the urgency of the situation, please schedule a blocker meeting for > today (formally or informally). I'll be ready to run a meeting at the usual 1600 UTC time in #fedora-blocker-review. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Self-Introduction
- Original Message - > From: "David Wynter"> To: test@lists.fedoraproject.org > Sent: Thursday, June 29, 2017 3:11:01 PM > Subject: Self-Introduction > > Hi All, > My Name is David and im a Security Architect for a Telco in the UK > I have been using Linux generally in many capacities since i was 13 (30 now) > > Tried many different flavours for many different reasons but always seem to > circle back to fedora and find the community inc info the easiest to get > stuck in on. > > I have been contributing when i can on QA via bodhi but am keen to do more, > if i can just find some more spare time :) . Im also keen to expand beyond > Bodhi and contribute further so may fire some questions to the more > experienced folk here. > > I will try and get more active via IRC also. > > FAS: wynter919 > IRC: octoray919 > PGP: https://pgp.key-server.io/0x73814AE713A515B7 > > Many Thanks > David > > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Hey David, First of all, Welcome and thanks for showing your interest in Fedora QA. I would like you to apply for QA FAS group. You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 24 , Fedora 25 and Fedora 26. Update testing is where a tester tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to bodhi.fedoraproject.org where you can sort the packages with Fedora Releases and tags viz "pending" & "testing" . You can read much about update testing here [1]. You can also, use fedora-easy-karma for giving out feedbacks. you can start with Release Validation testing. In Release Validation all you need to do is to check the nightly/TC/RC against certain criteria. For example, let's take the latest build (Fedora 26 Branched 20170628), you can run test cases which are mentioned [2] and submit your results in the test matrix. Note that each of the test cases[3] will have "How to test" section which will have the steps (to be executed sequentially) and if the results match with the expected results you can mark it as pass by editing the wiki page {{result|PASS|}} . Always make sure to check for "Associated release criterion" which can be found on the top of test case page , if your test case fails you can mark it fail by editing the wiki page {{result|FAIL|}} and file a bug at RHBZ [4] under Fedora. You can always find the ‘current’ validation pages using these addresses: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test https://fedoraproject.org/wiki/Test_Results:Current_Base_Test https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test https://fedoraproject.org/wiki/Test_Results:Current_Server_Test https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test For Automation, you can start looking at Taskotron [https://fedoraproject.org/wiki/Taskotron] and Open QA[https://fedoraproject.org/wiki/OpenQA]. [1]https://fedoraproject.org/wiki/QA:Updates_Testing [2]https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170628.n.1_Installation [3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc [4]https://bugzilla.redhat.com/ We have a test day coming up tomorrow, which is where we are going to test if everything upgrades smoothly from F25 to F26. More about the test day can be found [https://fedoraproject.org/wiki/Test_Day:2017-06-30_Upgrade_Test_Day]. Thanks //sumantrom ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Schedule concern next week: holidays ahead!
On Wed, Jun 28, 2017 at 9:54 PM Adam Williamsonwrote: > On Wed, 2017-06-28 at 21:41 -0400, Mohan Boddu wrote: > > Hi, > > > > I think we can have RC compose once all the blockers are resolved and QA > > files the ticket even during the holidays, even though I am not > > guaranteeing it but I think someone will get to it sooner or later. > > > > But my major concern is blockers, I am not sure if we can get all the > > blockers fixed by next Tue. > > > > Also, there are few proposed blockers and I dont know how many people > will > > show up for Blocker Review meeting. > > So here's a very quick and informal blocker status mail: > > There are four accepted blockers. > > #1462825 doesn't look like it should be particularly difficult for the > right people to fix - i.e. folks who know libreport and anaconda's > interface with it. We just need to make sure we have their eyes on it; > I've attempted to CC all appropriate people. > > We have an approach for fixing #1449752 agreed and it just needs the > maintainer to go ahead and do it. I've tried to explain the urgency of > this in the bug this afternoon. > > #1436873 is in a state of slight disagreement about whether it's really > happening, I think. ;) The openQA test is still failing quite often > (although not always). I will try and reproduce the issue manually > tomorrow, since there appears to be scepticism among the KDE folks. But > in general the KDE folks are quite fast to fix issues once we do pin > them down specifically, I would be quite optimistic about getting this > one fixed. > > #1404285 is a GNOME crash quite a lot of people seem to be encountering > in different ways (possibly because it's a tracker issue and tracker is > hooked into lots of things). In at least some cases it causes GNOME as > a whole to crash back to GDM, which is of course bad. There are various > different reproduction steps documented in the bug. I'm hoping the > desktop team is looking at this, and will be able to provide us with > some more assessment. > > There are five proposed blockers. My professional guesstimate *at this > point* is that at least four of them will probably be rejected, though > that could change with more data (attention pjones: if #1418360 and > #1451071 are more serious than they seem to us so far, please do let us > know). #1462444 is the most unclear one, but it doesn't seem like a lot > of people are running into it, and we may wind up rejecting it also on > that basis. > > Given the holiday situation, it might make sense to do a blocker > meeting tomorrow (Thursday) or Friday, depending on how much notice > folks need, to give us at least a shot at doing an RC on Friday or over > the weekend, if all the accepted blockers happen to get resolved. > > There are also a *ton* of proposed FEs for broken dependencies; we > might also want to blow through those quickly at a meeting. > Given the urgency of the situation, please schedule a blocker meeting for today (formally or informally). ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Re: Introduction
Thanks Sumantro, Kushal. On 29 Jun 2017 7:03 pm, "Sumantro Mukherjee"wrote: > > > - Original Message - > > From: "Bijal Thanawala" > > To: test@lists.fedoraproject.org > > Sent: Wednesday, June 28, 2017 1:46:11 AM > > Subject: Introduction > > > > > > Hi all, > > > > I am Bijal Thanawala. My background is software development (of relevancy > > here - C, Python) with some systems-level programming. > > > > My long-term vision is to develop for operating systems architecture | > > networking protocols. > > > > I have been a Linux user past nearly 9 years, of which last 4 or so > years I > > am a Fedora user. > > > > By joining QA community I wish to learn about build|release processes at > > larger scale, fill in gaps in my knowledge of Linux, understand the very > > platform (Fedora) I use daily better, and gradually take on contributing > to > > Linux Kernel or like. > > > > To start with, I have already created FAS account, mid-way into > Sumantro's > > recorded "Global onboarding call" (youtube) and looking at how to create > IRC > > account. > > > > Please guide me if there is anything else at this stage I need to have > ready. > > > > Looking forward to collaborate and learn. > > > > Best Regards > > Bijal > > > > > > ___ > > test mailing list -- test@lists.fedoraproject.org > > To unsubscribe send an email to test-le...@lists.fedoraproject.org > > > > > Hey Bijal, > > First of all, Welcome and thanks for showing your interest in Fedora QA. I > would like you to apply for QA FAS group. > > You can start off by testing updates in [http://bodhi.fedoraproject.org/] > for Fedora 24 , Fedora 25 and Fedora 26. Update testing is where a tester > tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL. > You can go to bodhi.fedoraproject.org where you can sort the packages > with Fedora Releases and tags viz "pending" & "testing" . You can read much > about update testing here [1]. You can also, use fedora-easy-karma for > giving out feedbacks. > > > you can start with Release Validation testing. In Release Validation all > you need to do is to check the nightly/TC/RC against certain criteria. For > example, let's take the latest build (Fedora 26 Branched 20170628), you can > run test cases which are mentioned [2] and submit your results in the test > matrix. > > Note that each of the test cases[3] will have "How to test" section which > will have the steps (to be executed sequentially) and if the results match > with the expected results you can mark it as pass by editing the wiki page > {{result|PASS|}} . Always make sure to check for "Associated > release criterion" which can be found on the top of test case page , if > your test case fails you can mark it fail by editing the wiki page > {{result|FAIL|}} and file a bug at RHBZ [4] under Fedora. > > > You can always find the ‘current’ validation pages using these addresses: > > https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test > https://fedoraproject.org/wiki/Test_Results:Current_Base_Test > https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test > https://fedoraproject.org/wiki/Test_Results:Current_Server_Test > https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test > > > For Automation, you can start looking at Taskotron [ > https://fedoraproject.org/wiki/Taskotron] > and Open QA[https://fedoraproject.org/wiki/OpenQA]. > > > > [1]https://fedoraproject.org/wiki/QA:Updates_Testing > [2]https://fedoraproject.org/wiki/Test_Results:Fedora_26_ > Branched_20170628.n.1_Installation > [3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc > [4]https://bugzilla.redhat.com/ > > We have a test day coming up tomorrow, which is where we are going to test > if everything upgrades smoothly from F25 to F26. More about the test day > can be found [https://fedoraproject.org/wiki/Test_Day:2017-06-30_ > Upgrade_Test_Day]. > > > Thanks > //sumantrom > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Self-Introduction
Hi All, My Name is David and im a Security Architect for a Telco in the UK I have been using Linux generally in many capacities since i was 13 (30 now) Tried many different flavours for many different reasons but always seem to circle back to fedora and find the community inc info the easiest to get stuck in on. I have been contributing when i can on QA via bodhi but am keen to do more, if i can just find some more spare time :) . Im also keen to expand beyond Bodhi and contribute further so may fire some questions to the more experienced folk here. I will try and get more active via IRC also. FAS: wynter919 IRC: octoray919 PGP: https://pgp.key-server.io/0x73814AE713A515B7 Many Thanks David ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora 26-20170628.n.1 compose check report
No missing expected images. Failed openQA tests: 6/128 (x86_64), 1/2 (arm) New failures (same test did not fail in 26-20170627.n.0): ID: 114378 Test: x86_64 KDE-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/114378 ID: 114389 Test: x86_64 KDE-live-iso desktop_notifications_live URL: https://openqa.fedoraproject.org/tests/114389 ID: 114402 Test: x86_64 universal install_mirrorlist_graphical URL: https://openqa.fedoraproject.org/tests/114402 ID: 114420 Test: x86_64 universal install_delete_partial@uefi URL: https://openqa.fedoraproject.org/tests/114420 ID: 114463 Test: x86_64 universal install_kickstart_firewall_disabled URL: https://openqa.fedoraproject.org/tests/114463 Old failures (same test failed in 26-20170627.n.0): ID: 114392 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/114392 ID: 114448 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/114448 Soft failed openQA tests: 3/128 (x86_64), 2/24 (i386) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in 26-20170627.n.0): ID: 114353 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/114353 ID: 114354 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/114354 ID: 114394 Test: x86_64 Atomic-dvd_ostree-iso install_default URL: https://openqa.fedoraproject.org/tests/114394 ID: 114395 Test: x86_64 Atomic-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/114395 ID: 114462 Test: x86_64 universal install_asian_language URL: https://openqa.fedoraproject.org/tests/114462 Passed openQA tests: 110/128 (x86_64), 22/24 (i386) New passes (same test did not pass in 26-20170627.n.0): ID: 114344 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller URL: https://openqa.fedoraproject.org/tests/114344 ID: 114345 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/114345 ID: 114348 Test: x86_64 Server-dvd-iso realmd_join_cockpit URL: https://openqa.fedoraproject.org/tests/114348 ID: 114349 Test: x86_64 Server-dvd-iso realmd_join_sssd URL: https://openqa.fedoraproject.org/tests/114349 ID: 114449 Test: x86_64 universal upgrade_realmd_client URL: https://openqa.fedoraproject.org/tests/114449 ID: 114461 Test: x86_64 universal install_cyrillic_language URL: https://openqa.fedoraproject.org/tests/114461 Skipped openQA tests: 10 of 154 Installed system changes in test x86_64 Server-boot-iso install_default: Mount /boot contents changed to 79.00104393% of previous size Mount /boot size changed from 975 to 1014 MiB System load changed from 0.02 to 0.38 Previous test data: https://openqa.fedoraproject.org/tests/113817#downloads Current test data: https://openqa.fedoraproject.org/tests/114331#downloads Installed system changes in test x86_64 Server-boot-iso install_default@uefi: Mount /boot contents changed to 77.72265937% of previous size Mount /boot size changed from 975 to 1014 MiB Previous test data: https://openqa.fedoraproject.org/tests/113818#downloads Current test data: https://openqa.fedoraproject.org/tests/114332#downloads Installed system changes in test x86_64 Server-dvd-iso install_default_upload: Mount /boot contents changed to 79.18841197% of previous size Mount /boot size changed from 975 to 1014 MiB Previous test data: https://openqa.fedoraproject.org/tests/113819#downloads Current test data: https://openqa.fedoraproject.org/tests/114333#downloads Installed system changes in test x86_64 Server-dvd-iso install_default@uefi: Mount /boot contents changed to 77.92583352% of previous size Mount /boot size changed from 975 to 1014 MiB Previous test data: https://openqa.fedoraproject.org/tests/113820#downloads Current test data: https://openqa.fedoraproject.org/tests/114334#downloads Installed system changes in test i386 Server-boot-iso install_default: Mount /boot contents changed to 78.33900086% of previous size Mount /boot size changed from 975 to 1014 MiB Previous test data: https://openqa.fedoraproject.org/tests/113839#downloads Current test data: https://openqa.fedoraproject.org/tests/114353#downloads Installed system changes in test i386 Server-dvd-iso install_default: Mount /boot contents changed to 78.57260590% of previous size Mount /boot size changed from 975 to 1014 MiB System load changed from 0.17 to 0.06 Previous test data: https://openqa.fedoraproject.org/tests/113840#downloads Current test data: https://openqa.fedoraproject.org/tests/114354#downloads Installed system changes in test x86_64 Workstation-live-iso install_default_upload: System load changed from 0.73 to 0.53 Used mem changed from 986 MiB to 844 MiB Previous test data:
Re: Introduction
- Original Message - > From: "Bijal Thanawala"> To: test@lists.fedoraproject.org > Sent: Wednesday, June 28, 2017 1:46:11 AM > Subject: Introduction > > > Hi all, > > I am Bijal Thanawala. My background is software development (of relevancy > here - C, Python) with some systems-level programming. > > My long-term vision is to develop for operating systems architecture | > networking protocols. > > I have been a Linux user past nearly 9 years, of which last 4 or so years I > am a Fedora user. > > By joining QA community I wish to learn about build|release processes at > larger scale, fill in gaps in my knowledge of Linux, understand the very > platform (Fedora) I use daily better, and gradually take on contributing to > Linux Kernel or like. > > To start with, I have already created FAS account, mid-way into Sumantro's > recorded "Global onboarding call" (youtube) and looking at how to create IRC > account. > > Please guide me if there is anything else at this stage I need to have ready. > > Looking forward to collaborate and learn. > > Best Regards > Bijal > > > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Hey Bijal, First of all, Welcome and thanks for showing your interest in Fedora QA. I would like you to apply for QA FAS group. You can start off by testing updates in [http://bodhi.fedoraproject.org/] for Fedora 24 , Fedora 25 and Fedora 26. Update testing is where a tester tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to bodhi.fedoraproject.org where you can sort the packages with Fedora Releases and tags viz "pending" & "testing" . You can read much about update testing here [1]. You can also, use fedora-easy-karma for giving out feedbacks. you can start with Release Validation testing. In Release Validation all you need to do is to check the nightly/TC/RC against certain criteria. For example, let's take the latest build (Fedora 26 Branched 20170628), you can run test cases which are mentioned [2] and submit your results in the test matrix. Note that each of the test cases[3] will have "How to test" section which will have the steps (to be executed sequentially) and if the results match with the expected results you can mark it as pass by editing the wiki page {{result|PASS|}} . Always make sure to check for "Associated release criterion" which can be found on the top of test case page , if your test case fails you can mark it fail by editing the wiki page {{result|FAIL|}} and file a bug at RHBZ [4] under Fedora. You can always find the ‘current’ validation pages using these addresses: https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test https://fedoraproject.org/wiki/Test_Results:Current_Base_Test https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test https://fedoraproject.org/wiki/Test_Results:Current_Server_Test https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test For Automation, you can start looking at Taskotron [https://fedoraproject.org/wiki/Taskotron] and Open QA[https://fedoraproject.org/wiki/OpenQA]. [1]https://fedoraproject.org/wiki/QA:Updates_Testing [2]https://fedoraproject.org/wiki/Test_Results:Fedora_26_Branched_20170628.n.1_Installation [3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc [4]https://bugzilla.redhat.com/ We have a test day coming up tomorrow, which is where we are going to test if everything upgrades smoothly from F25 to F26. More about the test day can be found [https://fedoraproject.org/wiki/Test_Day:2017-06-30_Upgrade_Test_Day]. Thanks //sumantrom ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org