Fedora 20 updates-testing report
The following Fedora 20 Security updates need testing: Age URL 95 https://admin.fedoraproject.org/updates/FEDORA-2014-11969/krb5-1.11.5-16.fc20 47 https://admin.fedoraproject.org/updates/FEDORA-2014-15371/rubygem-actionpack-4.0.0-5.fc20 46 https://admin.fedoraproject.org/updates/FEDORA-2014-15489/rubygem-sprockets-2.8.2-5.fc20 25 https://admin.fedoraproject.org/updates/FEDORA-2014-16494/mutt-1.5.23-4.fc20 23 https://admin.fedoraproject.org/updates/FEDORA-2014-16845/resteasy-3.0.6-3.fc20 23 https://admin.fedoraproject.org/updates/FEDORA-2014-16825/asterisk-11.14.2-1.fc20 23 https://admin.fedoraproject.org/updates/FEDORA-2014-16869/docker-io-1.4.0-1.fc20 23 https://admin.fedoraproject.org/updates/FEDORA-2014-16932/libhtp-0.5.6-2.fc20 22 https://admin.fedoraproject.org/updates/FEDORA-2014-16964/mpfr-3.1.2-5.fc20 19 https://admin.fedoraproject.org/updates/FEDORA-2014-16530/nss-util-3.17.3-1.fc20,nss-3.17.3-2.fc20,nss-softokn-3.17.3-1.fc20 19 https://admin.fedoraproject.org/updates/FEDORA-2014-17153/httpd-2.4.10-2.fc20 17 https://admin.fedoraproject.org/updates/FEDORA-2014-17272/ca-certificates-2014.2.2-1.0.fc20 15 https://admin.fedoraproject.org/updates/FEDORA-2014-17415/thermostat-1.0.6-1.fc20 15 https://admin.fedoraproject.org/updates/FEDORA-2014-17089/aeskulap-0.2.2-0.20beta1.fc20,orthanc-0.8.5-2.fc20,dcmtk-3.6.1-1.fc20 12 https://admin.fedoraproject.org/updates/FEDORA-2014-17559/mapserver-6.2.2-1.fc20 9 https://admin.fedoraproject.org/updates/FEDORA-2014-17641/dokuwiki-0-0.23.20140929b.fc20 2 https://admin.fedoraproject.org/updates/FEDORA-2015-0072/drupal6-flag-2.1-3.fc20 The following Fedora 20 Critical Path updates have yet to be approved: Age URL 5 https://admin.fedoraproject.org/updates/FEDORA-2014-17748/kdelibs-4.14.3-8.fc20 2 https://admin.fedoraproject.org/updates/FEDORA-2015-0082/btrfs-progs-3.18-1.fc20 2 https://admin.fedoraproject.org/updates/FEDORA-2015-0069/gawk-4.1.0-4.fc20 2 https://admin.fedoraproject.org/updates/FEDORA-2015-0086/perl-Filter-1.53-1.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2015-0220/xorg-x11-drv-synaptics-1.7.7-2.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2015-0173/vdpauinfo-0.9-0.1.fc20,libvdpau-0.9-1.fc20 0 https://admin.fedoraproject.org/updates/FEDORA-2015-0177/llvm-3.4-12.fc20 The following builds have been pushed to Fedora 20 updates-testing abiword-3.0.1-1.fc20 apache-commons-math-3.4-1.fc20 axmail-2.0-1.fc20 copr-cli-1.41-1.fc20 csmith-2.2.0-1.fc20 gammu-1.34.0-1.fc20 gettext-0.18.3.2-4.fc20 haproxy-1.5.10-1.fc20 libfprint-0.5.1-5.fc20 marsshooter-0.7.5-5.20140507gitc855d04.fc20 perl-Directory-Scratch-0.16-1.fc20 perl-MCE-1.522-1.fc20 php-jsonlint-1.3.1-1.fc20 python-bitmath-1.2.3-3.fc20 rubygem-rake-compiler-0.9.5-1.fc20 tuned-2.4.1-2.fc20 wammu-0.38-1.fc20 whois-5.2.3-1.fc20 wxsqlite3-3.2.0-2.fc20 xorg-x11-drv-synaptics-1.7.7-2.fc20 Details about builds: abiword-3.0.1-1.fc20 (FEDORA-2015-0207) Word processing program Update Information: Update to 3.0.1 bugfix release ChangeLog: * Wed Dec 24 2014 Peter Robinson 1:3.0.1-1 - Update to 3.0.1 stable * Fri Aug 15 2014 Fedora Release Engineering - 1:3.0.0-14 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild * Tue Jul 22 2014 Kalev Lember - 1:3.0.0-13 - Rebuilt for gobject-introspection 1.41.4 * Tue Jul 8 2014 Rex Dieter 1:3.0.0-12 - update scriptlets (mimeinfo mostly) * Mon Jun 30 2014 Jon Ciesla - 1:3.0.0-11 - Corrected and second patches from Linas Vepstas. * Tue Jun 24 2014 Jon Ciesla - 1:3.0.0-10 - Rebuild for new link-grammar, with patch for API change. - Add librevenge BuildRequires, modified patch for current librevenge header placement. * Fri Jun 6 2014 Fedora Release Engineering - 1:3.0.0-9 - Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild * Tue May 27 2014 David Tardon - 1:3.0.0-8 - switch to librevenge-based import libs * Fri May 23 2014 Petr Machata - 1:3.0.0-7 - Rebuild for boost 1.55.0 * Tue Apr 22 2014 Tomáš Mráz - 1:3.0.0-6 - Rebuild for new libgcrypt References: [ 1 ] Bug #1043897 - [abrt] abiword: AP_UnixApp::catchSignals(): abiword killed by SIGABRT https://bugzilla.redhat.com/show_bug.cgi?id=1043897 [ 2 ] Bug #1052934 - abiword: symbol lookup error: /usr/lib64/abiword-3.0/plugins/aiksaurus.so: undefined symbol: _ZN17AiksaurusGTK_impl12AiksaurusGTKC1Ev https://bugzilla.redhat.com/show_bug.cgi?id=1052934 [ 3 ] Bug #1073445 - Abiword does not change the text color by the Format->Font... menu
Fedora 21 updates-testing report
The following Fedora 21 Security updates need testing: Age URL 48 https://admin.fedoraproject.org/updates/FEDORA-2014-15342/rubygem-actionpack-4.1.5-2.fc21 46 https://admin.fedoraproject.org/updates/FEDORA-2014-15413/rubygem-sprockets-2.12.1-3.fc21 25 https://admin.fedoraproject.org/updates/FEDORA-2014-16782/mutt-1.5.23-7.fc21 23 https://admin.fedoraproject.org/updates/FEDORA-2014-16823/tcpdump-4.6.2-3.fc21 23 https://admin.fedoraproject.org/updates/FEDORA-2014-16880/libhtp-0.5.16-1.fc21 23 https://admin.fedoraproject.org/updates/FEDORA-2014-16833/asterisk-11.14.2-1.fc21 22 https://admin.fedoraproject.org/updates/FEDORA-2014-16967/mpfr-3.1.2-8.fc21 20 https://admin.fedoraproject.org/updates/FEDORA-2014-17049/openvas-cli-1.3.1-1.fc21,openvas-manager-5.0.7-1.fc21,openvas-scanner-4.0.5-1.fc21 19 https://admin.fedoraproject.org/updates/FEDORA-2014-17195/httpd-2.4.10-15.fc21 15 https://admin.fedoraproject.org/updates/FEDORA-2014-17139/aeskulap-0.2.2-0.20beta1.fc21,orthanc-0.8.5-2.fc21,dcmtk-3.6.1-1.fc21 15 https://admin.fedoraproject.org/updates/FEDORA-2014-17384/thermostat-1.0.6-1.fc21 12 https://admin.fedoraproject.org/updates/FEDORA-2014-17567/mapserver-6.2.2-1.fc21 9 https://admin.fedoraproject.org/updates/FEDORA-2014-17635/dokuwiki-0-0.23.20140929b.fc21 2 https://admin.fedoraproject.org/updates/FEDORA-2015-0046/smack-4.0.6-1.fc21 2 https://admin.fedoraproject.org/updates/FEDORA-2015-0078/drupal6-flag-2.1-3.fc21 The following Fedora 21 Critical Path updates have yet to be approved: Age URL 13 https://admin.fedoraproject.org/updates/FEDORA-2014-17526/libical-1.0-8.fc21 12 https://admin.fedoraproject.org/updates/FEDORA-2014-17610/harfbuzz-0.9.36-1.fc21 9 https://admin.fedoraproject.org/updates/FEDORA-2014-17633/llvm-3.5.0-6.fc21 7 https://admin.fedoraproject.org/updates/FEDORA-2014-17658/phonon-4.8.2-1.fc21 2 https://admin.fedoraproject.org/updates/FEDORA-2015-0091/gawk-4.1.1-6.fc21 2 https://admin.fedoraproject.org/updates/FEDORA-2015-0113/perl-Filter-1.53-1.fc21 0 https://admin.fedoraproject.org/updates/FEDORA-2015-0227/dbus-1.8.14-1.fc21 0 https://admin.fedoraproject.org/updates/FEDORA-2015-0204/man-db-2.6.7.1-13.fc21 0 https://admin.fedoraproject.org/updates/FEDORA-2015-0190/NetworkManager-0.9.10.1-1.git20150105.fc21 0 https://admin.fedoraproject.org/updates/FEDORA-2015-0238/bash-4.3.33-1.fc21 0 https://admin.fedoraproject.org/updates/FEDORA-2015-0188/less-471-1.fc21 The following builds have been pushed to Fedora 21 updates-testing NetworkManager-0.9.10.1-1.git20150105.fc21 axmail-2.0-1.fc21 bash-4.3.33-1.fc21 copr-cli-1.41-1.fc21 csmith-2.2.0-1.fc21 dbus-1.8.14-1.fc21 gammu-1.34.0-1.fc21 gnome-multi-writer-3.15.1-1.fc21 gogoc-1.2-41.fc21 haproxy-1.5.10-1.fc21 less-471-1.fc21 libccp4-6.4.6-1.fc21 libe-book-0.1.2-1.fc21 libfprint-0.5.1-5.fc21 libmwaw-0.3.4-1.fc21 light-themes-14.04-2.20141217bzr408.fc21 man-db-2.6.7.1-13.fc21 marsshooter-0.7.5-5.20140507gitc855d04.fc21 nano-2.3.4-4.fc21 perl-Devel-PatchPerl-1.30-1.fc21 perl-Directory-Scratch-0.16-1.fc21 perl-IO-Socket-IP-0.35-1.fc21 perl-MCE-1.522-1.fc21 perl-Package-Constants-0.06-1.fc21 php-bartlett-PHP-CompatInfo-3.7.2-1.fc21 php-bartlett-PHP-Reflect-2.6.2-1.fc21 php-jsonlint-1.3.1-1.fc21 python-bitmath-1.2.3-3.fc21 rubygem-rake-compiler-0.9.5-1.fc21 scipy-0.14.1-1.fc21 thc-ipv6-2.7-1.fc21 tintin-2.01.1-1.fc21 tinyxml2-2.2.0-1.20140914git5321a0e.fc21 tuned-2.4.1-2.fc21 wammu-0.38-1.fc21 warzone2100-3.1.2-1.fc21 whois-5.2.3-1.fc21 wxsqlite3-3.2.0-2.fc21 Details about builds: NetworkManager-0.9.10.1-1.git20150105.fc21 (FEDORA-2015-0190) Network connection manager and user applications Update Information: This update brings a new snapshot of 0.9.10 branch. It fixes (among other things) this problem:\r\n\r\n* dhcp: fix dhclient abnormal exit due to SIGPIPE (bgo #735962) (rh #1178666) ChangeLog: * Mon Jan 5 2015 Jiří Klimeš - 1:0.9.10.1-1.git20150105 - update to latest snapshot of 0.9.10 - dhcp: fix dhclient abnormal exit due to SIGPIPE (bgo #735962) (rh #1178666) References: [ 1 ] Bug #1178666 - dhclient fails to get an address if journald is rerstarted https://bugzilla.redhat.com/show_bug.cgi?id=1178666 axmail-2.0-1.fc21 (FEDORA-2015-0244) UROnode addon - an SMTP mailbox
Fedora 19 updates-testing report
The following Fedora 19 Security updates need testing: Age URL 437 https://admin.fedoraproject.org/updates/FEDORA-2013-19963/openstack-glance-2013.1.4-1.fc19 95 https://admin.fedoraproject.org/updates/FEDORA-2014-12057/krb5-1.11.3-29.fc19 71 https://admin.fedoraproject.org/updates/FEDORA-2014-13551/wpa_supplicant-2.0-12.fc19 55 https://admin.fedoraproject.org/updates/FEDORA-2014-14738/gnutls-3.1.20-6.fc19 52 https://admin.fedoraproject.org/updates/FEDORA-2014-12407/sddm-0.10.0-2.fc19 48 https://admin.fedoraproject.org/updates/FEDORA-2014-15248/kde-runtime-4.11.5-3.fc19 47 https://admin.fedoraproject.org/updates/FEDORA-2014-15378/rubygem-actionpack-3.2.13-7.fc19 46 https://admin.fedoraproject.org/updates/FEDORA-2014-15466/rubygem-sprockets-2.8.2-4.fc19 41 https://admin.fedoraproject.org/updates/FEDORA-2014-15740/facter-1.6.18-8.fc19 35 https://admin.fedoraproject.org/updates/FEDORA-2014-15999/libreoffice-4.1.6.2-10.fc19 35 https://admin.fedoraproject.org/updates/FEDORA-2014-16045/util-linux-2.23.2-6.fc19 30 https://admin.fedoraproject.org/updates/FEDORA-2014-16485/pam-1.1.6-13.fc19 23 https://admin.fedoraproject.org/updates/FEDORA-2014-16896/tcpdump-4.4.0-5.fc19 23 https://admin.fedoraproject.org/updates/FEDORA-2014-16874/asterisk-11.14.2-1.fc19 23 https://admin.fedoraproject.org/updates/FEDORA-2014-16728/xorg-x11-server-1.14.4-5.fc19 23 https://admin.fedoraproject.org/updates/FEDORA-2014-16865/docker-io-1.4.0-1.fc19 19 https://admin.fedoraproject.org/updates/FEDORA-2014-17110/mariadb-5.5.40-2.fc19 19 https://admin.fedoraproject.org/updates/FEDORA-2014-16826/nss-3.17.3-2.fc19,nss-util-3.17.3-1.fc19,nss-softokn-3.17.3-1.fc19 17 https://admin.fedoraproject.org/updates/FEDORA-2014-17284/ca-certificates-2014.2.2-1.0.fc19 12 https://admin.fedoraproject.org/updates/FEDORA-2014-17555/mapserver-6.2.2-1.fc19 9 https://admin.fedoraproject.org/updates/FEDORA-2014-17640/dokuwiki-0-0.23.20140929b.fc19 2 https://admin.fedoraproject.org/updates/FEDORA-2015-0112/drupal6-flag-2.1-3.fc19 The following Fedora 19 Critical Path updates have yet to be approved: Age URL 385 https://admin.fedoraproject.org/updates/FEDORA-2013-22326/fedora-bookmarks-15-5.fc19 311 https://admin.fedoraproject.org/updates/FEDORA-2014-3245/testdisk-6.14-2.fc19.1,ntfs-3g-2014.2.15-1.fc19 2 https://admin.fedoraproject.org/updates/FEDORA-2015-0054/perl-Filter-1.53-1.fc19 0 https://admin.fedoraproject.org/updates/FEDORA-2015-0162/vdpauinfo-0.9-0.1.fc19,libvdpau-0.9-1.fc19 The following builds have been pushed to Fedora 19 updates-testing perl-MCE-1.522-1.fc19 python-bitmath-1.2.3-3.fc19 whois-5.2.3-1.fc19 Details about builds: perl-MCE-1.522-1.fc19 (FEDORA-2015-0230) Many-core Engine for Perl providing parallel processing capabilities Update Information: Update to the latest and greatest MCE. See http://cpansearch.perl.org/src/MARIOROY/MCE-1.522/CHANGES for details on changes in this release. ChangeLog: * Mon Jan 5 2015 Petr Šabata - 1.522-1 - 1.522 bump References: [ 1 ] Bug #1178395 - perl-MCE-1.522 is available https://bugzilla.redhat.com/show_bug.cgi?id=1178395 python-bitmath-1.2.3-3.fc19 (FEDORA-2015-0209) Aids representing and manipulating sizes in various prefix notations Update Information: Add mock to build requires ChangeLog: * Sun Jan 4 2015 Tim Bielawa - 1.2.3-3 - Add mock to build requires * Sun Jan 4 2015 Tim Bielawa - 1.2.3-2 - Add python-progressbar build-dependency to satisfy 'check' tests * Sun Jan 4 2015 Tim Bielawa - 1.2.3-1 - Add progressbar example to the README * Sun Jan 4 2015 Tim Bielawa - 1.2.2-1 - Fix some problems with the automated build system * Sun Jan 4 2015 Tim Bielawa - 1.2.1-1 - Add a new integration: the progressbar module FileTransferSpeed widget * Mon Dec 29 2014 Tim Bielawa - 1.2.0-1 - Add argparse integration with a BitmathType argument type whois-5.2.3-1.fc19 (FEDORA-2015-0197) Improved WHOIS client Update Information: This release adds records for 46 new generic TLDs. It upd
2015-01-05 @ 16:00 UTC - Fedora QA Meeting - Minutes
== #fedora-meeting: Fedora QA meeting == Meeting started by adamw at 16:03:07 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2015-01-05/fedora-qa.2015-01-05-16.03.log.html . Meeting summary --- * Roll call (adamw, 16:03:11) * Previous meeting follow-up (adamw, 16:09:59) * ACTION: adamw to sync with cmurf and look at revising multiboot criteria (adamw, 16:11:05) * Blocker bug review planning (adamw, 16:14:20) * AGREED: everyone seems on board with the idea of starting up blocker review now and reviewing for all milestones to try and stay on top of the bug pile (adamw, 16:24:54) * ACTION: roshi to arrange and announce first f22 blocker review meeting this week (adamw, 16:25:11) * Open floor (adamw, 16:26:04) * current Rawhide nightly boot.iso installs hit a console login screen for satellit since ~5 days ago, confirmation would be great (adamw, 16:29:33) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1178932 wireless crash of boot.iso (satellit_e, 16:48:14) Meeting ended at 16:49:11 UTC. Action Items * adamw to sync with cmurf and look at revising multiboot criteria * roshi to arrange and announce first f22 blocker review meeting this week Action Items, by person --- * adamw * adamw to sync with cmurf and look at revising multiboot criteria * roshi * roshi to arrange and announce first f22 blocker review meeting this week * **UNASSIGNED** * (none) People Present (lines said) --- * adamw (50) * roshi (23) * Corey84 (19) * satellit (8) * zodbot (6) * Kinokoio (6) * amita (5) * satellit_e (5) * danofsatx|w (4) * kparal (3) * apatel (3) * pschindl (2) * tflink (1) * nirik (1) * brunowolff (1) * Greylocks (1) * mkrizek (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot -- 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: https://admin.fedoraproject.org/mailman/listinfo/test
[Test-Announce] 2015-01-07 @ 1600 UTC ** Fedora 22 Blocker Review Meeting
# First F22 Blocker Review meeting # Date: 2015-01-07 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net While it's not the usual time to start blocker reviews, after much deliberation at today's QA meeting, it was decided to start the blocker review process earlier than usual. With that being decided, we're going to get started this week! The other change to the blocker review process: we're going to start going through all the remaining milestones for a release. The thought is that this will keep bugs from piling up, which gives developers and QA more time to code and test (respectively). Hopefully this will lessen the number of really long blocker review meetings. If we happen to have a bunch of blockers that we can't get through in one meeting, we'll try to schedule another during the week to get through them. Currently we have 3 Alpha, 2 Beta and 3 Final proposed Blockers and 4 proposed Alpha Freeze Exceptions. If you want to take a look at the proposed or accepted blockers, the full list can be found here: https://qa.fedoraproject.org/blockerbugs/ Make sure to click through the milestones to see how many we have before the meeting! We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F22 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting See you Wednesday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- // Mike -- Fedora QA freenode: roshi http://roshi.fedorapeople.org ___ 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] 2015-01-05 @16:00 UTC - Fedora QA Meeting
On Mon, 2015-01-05 at 13:19 -0500, Sudhir Dharanendraiah wrote: > - Adam Williamson wrote: > > On Mon, 2015-01-05 at 22:47 +0530, Sudhir Dharanendraiah wrote: > > > On 01/05/2015 10:18 PM, Adam Williamson wrote: > > > > In*theory*, if a bug's rejected as a blocker for one release > > > > it won't be a blocker for the next release either - remember > > > > Fedora doesn't use the RHEL system where bugs can be dropped > > > > as blockers for time reasons, in the Fedora system blockers > > > > are supposed to be unconditional. In practice we handwave a > > > > bit, but it's still > > > > generally the case that rejected blockers for one release > > > > won't be accepted for the next. > > > > > > Ah.. understood. thanks :) > > > > > > > Bugzilla doesn't make it super easy to find rejected blockers > > > > for a specific release, as you can't search for bugs > > > > which*once* > > > > blocked another bug but don't any more (bit of a shame) - but > > > > here's an approximate search, for open bugs filed in 2014 that > > > > have the 'RejectedBlocker' whiteboard: > > > > > > > > Yeah, dependent on whiteboard. Alternatively, we can use tracker > > > bugs for the various stages (Alpha/Beta/Final) of release. That > > > can provide a > > > tree view of bugs (can be blocker bugs in this case) targeted > > > for that specific milestone and the ones closed will strike out > > > leaving the ones that got dropped. > > > > > > > That's the system we do use, but the problem is that when we > > reject a bug as a blocker, we do it by making it not block the > > tracker bug any more. So to find those bugs, you'd need to do a > > search for 'bugs which blocked F21AlphaBlocker / F21BetaBlocker / > > F21FinalBlocker once, but don't any more', but Bugzilla doesn't > > have that option. > > > > We *could* make it so bugs that are rejected as blockers still > > block the tracking bug (but just have the 'RejectedBlocker' > > whiteboard field added), but I think that'd be confusing and a bad > > idea. > > Oh yes, its a bad idea to keep them in that state forever :). I was > only suggesting to keep the bugs till it is reviewed. But anyway, > since blockers are not pushed because of time constraint, that would > make no difference either. Yep. As I said the system we have is actually exactly as you describe. There are tracker bugs for each milestone - you can see them listed at: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers the blockerbugs web app - http://qa.fedoraproject.org/blockerbugs/current - is handy for several reasons, but before we had it, we still used the same set of trackers. At that time we did indeed use the tracker bug tree views as you suggest, e.g. here's the tree view for 22 Alpha: https://bugzilla.redhat.com/showdependencytree.cgi?id=1043121&hide_resolved=1 some of the benefits of the blockerbugs app are that it distinguishes between proposed and accepted blockers (we had custom searches for this, but custom searches are kind of a pain) and pulls in info from Bodhi, so we know the status of the updates for each bug. I do remember back around 16-17, though, I'd just have the tree views open and keep refreshing them... -- 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: https://admin.fedoraproject.org/mailman/listinfo/test
Re: contribution
5.1.2015, 20:30, shailendra acharya kirjoitti: > how can i contribute to fedora. See here: https://fedoraproject.org/wiki/Join -- Markku Kolkka markku.kol...@iki.fi -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
contribution
how can i contribute to fedora. i have skills of c,c++,java,php,python. plz suggest me asap. i want to do some coding for fedora -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] 2015-01-05 @16:00 UTC - Fedora QA Meeting
- Adam Williamson wrote: | On Mon, 2015-01-05 at 22:47 +0530, Sudhir Dharanendraiah wrote: | > On 01/05/2015 10:18 PM, Adam Williamson wrote: | > > In*theory*, if a bug's rejected as a blocker for one release it | > > won't be a blocker for the next release either - remember Fedora | > > doesn't use the RHEL system where bugs can be dropped as blockers | > > for time reasons, in the Fedora system blockers are supposed to be | > > unconditional. In practice we handwave a bit, but it's still | > > generally the case that rejected blockers for one release won't be | > > accepted for the next. | > | > Ah.. understood. thanks :) | > | > > Bugzilla doesn't make it super easy to find rejected blockers for a | > > specific release, as you can't search for bugs which*once* | > > blocked another bug but don't any more (bit of a shame) - but | > > here's an approximate search, for open bugs filed in 2014 that | > > have the 'RejectedBlocker' whiteboard: | > | | > Yeah, dependent on whiteboard. Alternatively, we can use tracker | > bugs for the various stages (Alpha/Beta/Final) of release. That can | > provide a | > tree view of bugs (can be blocker bugs in this case) targeted for | > that specific milestone and the ones closed will strike out leaving | > the ones that got dropped. | > | | That's the system we do use, but the problem is that when we reject a | bug as a blocker, we do it by making it not block the tracker bug any | more. So to find those bugs, you'd need to do a search for 'bugs which | blocked F21AlphaBlocker / F21BetaBlocker / F21FinalBlocker once, but | don't any more', but Bugzilla doesn't have that option. | | We *could* make it so bugs that are rejected as blockers still block | the tracking bug (but just have the 'RejectedBlocker' whiteboard field | added), but I think that'd be confusing and a bad idea. Oh yes, its a bad idea to keep them in that state forever :). I was only suggesting to keep the bugs till it is reviewed. But anyway, since blockers are not pushed because of time constraint, that would make no difference either. Regards, Sudhir | -- | 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: | https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] 2015-01-05 @16:00 UTC - Fedora QA Meeting
On Mon, 2015-01-05 at 22:47 +0530, Sudhir Dharanendraiah wrote: > On 01/05/2015 10:18 PM, Adam Williamson wrote: > > In*theory*, if a bug's rejected as a blocker for one release it > > won't be a blocker for the next release either - remember Fedora > > doesn't use the RHEL system where bugs can be dropped as blockers > > for time reasons, in the Fedora system blockers are supposed to be > > unconditional. In practice we handwave a bit, but it's still > > generally the case that rejected blockers for one release won't be > > accepted for the next. > > Ah.. understood. thanks :) > > > Bugzilla doesn't make it super easy to find rejected blockers for a > > specific release, as you can't search for bugs which*once* > > blocked another bug but don't any more (bit of a shame) - but > > here's an approximate search, for open bugs filed in 2014 that > > have the 'RejectedBlocker' whiteboard: > > Yeah, dependent on whiteboard. Alternatively, we can use tracker > bugs for the various stages (Alpha/Beta/Final) of release. That can > provide a > tree view of bugs (can be blocker bugs in this case) targeted for > that specific milestone and the ones closed will strike out leaving > the ones that got dropped. > That's the system we do use, but the problem is that when we reject a bug as a blocker, we do it by making it not block the tracker bug any more. So to find those bugs, you'd need to do a search for 'bugs which blocked F21AlphaBlocker / F21BetaBlocker / F21FinalBlocker once, but don't any more', but Bugzilla doesn't have that option. We *could* make it so bugs that are rejected as blockers still block the tracking bug (but just have the 'RejectedBlocker' whiteboard field added), but I think that'd be confusing and a bad idea. -- 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: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] 2015-01-05 @16:00 UTC - Fedora QA Meeting
On 01/05/2015 10:18 PM, Adam Williamson wrote: In*theory*, if a bug's rejected as a blocker for one release it won't be a blocker for the next release either - remember Fedora doesn't use the RHEL system where bugs can be dropped as blockers for time reasons, in the Fedora system blockers are supposed to be unconditional. In practice we handwave a bit, but it's still generally the case that rejected blockers for one release won't be accepted for the next. Ah.. understood. thanks :) Bugzilla doesn't make it super easy to find rejected blockers for a specific release, as you can't search for bugs which*once* blocked another bug but don't any more (bit of a shame) - but here's an approximate search, for open bugs filed in 2014 that have the 'RejectedBlocker' whiteboard: Yeah, dependent on whiteboard. Alternatively, we can use tracker bugs for the various stages (Alpha/Beta/Final) of release. That can provide a tree view of bugs (can be blocker bugs in this case) targeted for that specific milestone and the ones closed will strike out leaving the ones that got dropped. Regards, Sudhir -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] 2015-01-05 @16:00 UTC - Fedora QA Meeting
On Mon, 2015-01-05 at 19:06 +0530, Sudhir Dharanendraiah wrote: > On 01/05/2015 07:24 AM, Adam Williamson wrote: > > > > roshi and I had a quick chat about the idea of starting up blocker > > bug review for the F22 cycle this week, in the interests of > > reducing the number of long meetings later in the cycle by > > starting earlier - so let's see what folks think of that. I don't > > have any other specific topics for the agenda - please reply to > > this mail if you do! Thanks. > > That is a great idea. Probably start with the list of bugs that were > proposed blockers for Fedora 21 but got kicked from the blocker > category, would be a good list to start with? In *theory*, if a bug's rejected as a blocker for one release it won't be a blocker for the next release either - remember Fedora doesn't use the RHEL system where bugs can be dropped as blockers for time reasons, in the Fedora system blockers are supposed to be unconditional. In practice we handwave a bit, but it's still generally the case that rejected blockers for one release won't be accepted for the next. The exception is when we decide to change the release criteria, based on something that happened during blocker review; in that case someone will usually transfer the proposal. Right now we have 8 proposed blockers for F22 (Alpha, Beta and Final) so we'll probably start with that list at the meeting roshi is going to schedule. Bugzilla doesn't make it super easy to find rejected blockers for a specific release, as you can't search for bugs which *once* blocked another bug but don't any more (bit of a shame) - but here's an approximate search, for open bugs filed in 2014 that have the 'RejectedBlocker' whiteboard: https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&chfield=[Bug%20creation]&chfieldfrom=2014-01-01&chfieldto=2014-12- 01&classification=Fedora&list_id=3125416&query_format=advanced&status_whiteboard=RejectedBlocker&status_whiteboard_type=allwordssubstr if someone wanted to poke through and see if any of those should be 22 blockers, that'd be great of course! -- 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: https://admin.fedoraproject.org/mailman/listinfo/test
Re: [Test-Announce] 2015-01-05 @16:00 UTC - Fedora QA Meeting
On 01/05/2015 07:24 AM, Adam Williamson wrote: roshi and I had a quick chat about the idea of starting up blocker bug review for the F22 cycle this week, in the interests of reducing the number of long meetings later in the cycle by starting earlier - so let's see what folks think of that. I don't have any other specific topics for the agenda - please reply to this mail if you do! Thanks. That is a great idea. Probably start with the list of bugs that were proposed blockers for Fedora 21 but got kicked from the blocker category, would be a good list to start with? Regards, Sudhir == Proposed Agenda Topics == 1. Previous meeting follow-up 2. Blocker bug review planning 3. Open floor -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20150105 changes
Compose started at Mon Jan 5 05:15:02 UTC 2015 Broken deps for i386 -- [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [aeskulap] aeskulap-0.2.2-0.19beta1.fc22.i686 requires libofstd.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires liboflog.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg8.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg16.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg12.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmnet.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmjpeg.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmimgle.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmimage.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmdata.so.3.6 [boswars] boswars-2.7-5.fc22.i686 requires libtolua++-5.1.so [cab] cab-0.1.9-12.fc22.i686 requires cabal-dev [dnssec-check] dnssec-check-1.14.0.1-4.fc20.i686 requires libval-threads.so.14 dnssec-check-1.14.0.1-4.fc20.i686 requires libsres.so.14 [fawkes] fawkes-lua-0.5.0-19.fc22.i686 requires libtolua++-5.1.so fawkes-plugin-katana-0.5.0-19.fc22.i686 requires libtolua++-5.1.so fawkes-plugin-pantilt-0.5.0-19.fc22.i686 requires libtolua++-5.1.so fawkes-plugin-roomba-0.5.0-19.fc22.i686 requires libtolua++-5.1.so fawkes-plugin-skiller-0.5.0-19.fc22.i686 requires libtolua++-5.1.so [gcc-python-plugin] gcc-python2-debug-plugin-0.13-2.fc22.i686 requires gcc = 0:4.9.2-1.fc22 gcc-python2-plugin-0.13-2.fc22.i686 requires gcc = 0:4.9.2-1.fc22 gcc-python3-debug-plugin-0.13-2.fc22.i686 requires gcc = 0:4.9.2-1.fc22 gcc-python3-plugin-0.13-2.fc22.i686 requires gcc = 0:4.9.2-1.fc22 [glances] glances-2.2.1-2.fc22.noarch requires python-psutil >= 0:2.0.0 [guacamole-server] libguac-client-rdp-0.9.3-1.fc22.i686 requires libfreerdp-utils.so.1.2 libguac-client-rdp-0.9.3-1.fc22.i686 requires libfreerdp-core.so.1.2 libguac-client-rdp-0.9.3-1.fc22.i686 requires libfreerdp-codec.so.1.2 libguac-client-rdp-0.9.3-1.fc22.i686 requires libfreerdp-cache.so.1.2 [guayadeque] guayadeque-0.3.7-4.svn1893.fc22.i686 requires libwxcode_gtk2_wxsqlite3-2.8.so.0 [nifti2dicom] nifti2dicom-0.4.9-1.fc22.i686 requires libitksys-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libitkopenjpeg-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libitkdouble-conversion-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libitkNetlibSlatec-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKznz-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKniftiio-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKgiftiio-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKWatersheds-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKVtkGlue-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKVideoIO-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKVideoCore-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKVTK-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKVNLInstantiation-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKStatistics-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKSpatialObjects-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKReview-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKQuadEdgeMesh-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKPolynomials-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKPath-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKOptimizersv4-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKOptimizers-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKNrrdIO-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKMetaIO-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKMesh-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKLabelMap-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKKLMRegionGrowing-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKIOXML-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKIOVTK-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKIOTransformMatlab-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKIOTransformInsightLegacy-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKIOTransformHDF5-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKIOTransformBase-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKIOTIFF-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKIOStimulate-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i686 requires libITKIOSpatialObjects-4.6.so.1 nifti2dicom-0.4.9-1.fc22.i68
