Fedora 25 updates-testing report

[updates]

The following Fedora 25 Security updates need testing:
 Age  URL
 146  https://bodhi.fedoraproject.org/updates/FEDORA-2016-d79ba708cb   
exim-4.87.1-1.fc25
  45  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e2d17af41e   
python-XStatic-jquery-ui-1.12.0.1-4.fc25
  25  https://bodhi.fedoraproject.org/updates/FEDORA-2017-f85c37ae3d   
squirrelmail-1.4.22-19.fc25
  18  https://bodhi.fedoraproject.org/updates/FEDORA-2017-8d625a8d2b   
lynis-2.5.0-1.fc25
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2017-410749716d   
FlightGear-2016.3.1-4.fc25
   6  https://bodhi.fedoraproject.org/updates/FEDORA-2017-40a6d19c7b   
FlightCrew-0.9.1-7.fc25
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2017-d968f5a95f   
wordpress-4.7.5-1.fc25
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-0e08170fd3   
libvncserver-0.9.11-2.fc25.1
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-4cc8d795e0   
moodle-3.1.6-1.fc25
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-5135c91b36   
mupdf-1.10a-7.fc25
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-a3c7d077c7   
perltidy-20170521-1.fc25


The following Fedora 25 Critical Path updates have yet to be approved:
 Age URL
  14  https://bodhi.fedoraproject.org/updates/FEDORA-2017-6d5aa85fd7   
livecd-tools-24.4-1.fc25
  10  https://bodhi.fedoraproject.org/updates/FEDORA-2017-116fdd792f   
pungi-4.1.15-1.fc25
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2017-6a5530c175   
gtk3-3.22.15-1.fc25
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2017-b8d8e95f8a   
tigervnc-1.8.0-1.fc25
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-1a705b1ff4   
libtiff-4.0.8-1.fc25
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-4d461d73e5   
libinput-1.6.3-5.fc25


The following builds have been pushed to Fedora 25 updates-testing

R-Rcpp-0.12.11-1.fc25
cacti-1.1.7-1.fc25
composer-1.4.2-2.fc25
gnome-gmail-2.4-1.fc25
libinput-1.6.3-5.fc25
librdkafka-0.9.5-1.fc25
libtiff-4.0.8-1.fc25
lilypond-2.19.61-1.fc25
lilypond-doc-2.19.61-1.fc25
mingw-mediawriter-4.1.0-1.fc25
nasm-2.13.01-1.fc25
perltidy-20170521-1.fc25
php-latte-2.4.4-1.fc25
php-pear-Mail-Mime-1.10.1-1.fc25
php-phpunit-diff-1.4.3-1.fc25
php-zendframework-zend-filter-2.7.2-1.fc25
php-zendframework-zend-form-2.10.2-1.fc25
php-zendframework-zend-i18n-2.7.4-1.fc25
php-zendframework-zend-inputfilter-2.7.4-1.fc25
php-zendframework-zend-log-2.9.2-1.fc25
php-zendframework-zend-validator-2.9.1-1.fc25
python-pytoml-0.1.13-1.git270397b.fc25

Details about builds:



 R-Rcpp-0.12.11-1.fc25 (FEDORA-2017-ae8c50af22)
 Seamless R and C++ Integration

Update Information:

https://cran.r-project.org/web/packages/Rcpp/news.html

References:

  [ 1 ] Bug #1453062 - Version  0.12.11 was released
https://bugzilla.redhat.com/show_bug.cgi?id=1453062




 cacti-1.1.7-1.fc25 (FEDORA-2017-fb86a4307b)
 An rrd based graphing tool

Update Information:

- Update to 1.1.7  Release notes:
http://www.cacti.net/release_notes.php?version=1.1.7




 composer-1.4.2-2.fc25 (FEDORA-2017-2e98abe35c)
 Dependency Manager for PHP

Update Information:

**Version 1.4.2** - 2017-05-17* Fixed Bitbucket API handler parsing old
deleted branches in hg repos   * Fixed regression in gitlab downloads   * Fixed
output inconsistencies   * Fixed unicode handling in `init` command for author
names   * Fixed useless warning when doing partial updates/removes on packages
that are not currently installed   * Fixed xdebug disabling issue when combined
with disable_functions and allow_url_fopen CLI overrides




 gnome-gmail-2.4-1.fc25 (FEDORA-2017-a7aed4baa7)
 Integrate GMail into the GNOME desktop

Update Information:

Update to 2.4, hack to work with Wayland

References:

  [ 1 ] Bug #1452973 - gnome-gmail-2.4 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1452973

Fedora 24 updates-testing report

[updates]

The following Fedora 24 Security updates need testing:
 Age  URL
 153  https://bodhi.fedoraproject.org/updates/FEDORA-2016-26f9817b08   
squid-3.5.23-1.fc24
 146  https://bodhi.fedoraproject.org/updates/FEDORA-2016-eaaa9c4a08   
exim-4.87.1-1.fc24
 109  https://bodhi.fedoraproject.org/updates/FEDORA-2017-ece16ba6ba   
runc-1.0.0-5.rc2.gitc91b5be.fc24
  89  https://bodhi.fedoraproject.org/updates/FEDORA-2017-4b176c1694   
redis-3.2.8-1.fc24
  45  https://bodhi.fedoraproject.org/updates/FEDORA-2017-8330a48ca2   
python-XStatic-jquery-ui-1.12.0.1-1.fc24
  25  https://bodhi.fedoraproject.org/updates/FEDORA-2017-0b6da97aa5   
squirrelmail-1.4.22-19.fc24
  18  https://bodhi.fedoraproject.org/updates/FEDORA-2017-c3ce061ea7   
lynis-2.5.0-1.fc24
  17  https://bodhi.fedoraproject.org/updates/FEDORA-2017-7a0e2d58f8   
thunderbird-52.1.0-1.fc24
  16  https://bodhi.fedoraproject.org/updates/FEDORA-2017-ebe41f3fd7   
python-fedora-0.9.0-3.fc24
  10  https://bodhi.fedoraproject.org/updates/FEDORA-2017-01a7989fc0   
git-2.7.5-1.fc24
  10  https://bodhi.fedoraproject.org/updates/FEDORA-2017-4de07172f4   
postgresql-9.5.7-1.fc24
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2017-3f2d5790d2   
lxterminal-0.3.0-3.fc24 menu-cache-1.0.2-4.D20170514git56f6668459.fc24 
pcmanfm-1.2.5-2.fc24
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2017-fc10e3165a   
FlightGear-2016.1.2-6.fc24
   6  https://bodhi.fedoraproject.org/updates/FEDORA-2017-607352ce5f   
FlightCrew-0.9.1-7.fc24
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2017-7d698eba8b   
chromium-58.0.3029.110-2.fc24 
chromium-native_client-58.0.3029.81-1.20170421gitc948e9b.fc24
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2017-46fcfd8c98   
wordpress-4.7.5-1.fc24
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-dd5d2381e4   
libvncserver-0.9.11-2.fc24.1
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-1f15fde598   
moodle-3.1.6-1.fc24
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-1f11501a9f   
perltidy-20170521-1.fc24


The following Fedora 24 Critical Path updates have yet to be approved:
 Age URL
  32  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e1905fd566   
koji-1.12.0-2.fc24
  17  https://bodhi.fedoraproject.org/updates/FEDORA-2017-7a0e2d58f8   
thunderbird-52.1.0-1.fc24
  10  https://bodhi.fedoraproject.org/updates/FEDORA-2017-01a7989fc0   
git-2.7.5-1.fc24
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2017-3f2d5790d2   
lxterminal-0.3.0-3.fc24 menu-cache-1.0.2-4.D20170514git56f6668459.fc24 
pcmanfm-1.2.5-2.fc24
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e2c9e5e8fe   
tigervnc-1.8.0-1.fc24
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-718c9992ef   
vim-8.0.600-1.fc24
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-6f5c3ec36e   
python-coverage-4.4.1-1.fc24
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-3ca90a77bd   
libtiff-4.0.8-1.fc24


The following builds have been pushed to Fedora 24 updates-testing

R-Rcpp-0.12.11-1.fc24
cacti-1.1.7-1.fc24
composer-1.4.2-2.fc24
librdkafka-0.9.5-1.fc24
libtiff-4.0.8-1.fc24
lilypond-2.19.61-1.fc24
lilypond-doc-2.19.61-1.fc24
mingw-mediawriter-4.1.0-1.fc24
perltidy-20170521-1.fc24
php-pear-Mail-Mime-1.10.1-1.fc24
php-phpunit-diff-1.4.3-1.fc24
php-zendframework-zend-filter-2.7.2-1.fc24
php-zendframework-zend-form-2.10.2-1.fc24
php-zendframework-zend-i18n-2.7.4-1.fc24
php-zendframework-zend-inputfilter-2.7.4-1.fc24
php-zendframework-zend-log-2.9.2-1.fc24

Details about builds:



 R-Rcpp-0.12.11-1.fc24 (FEDORA-2017-f422eee632)
 Seamless R and C++ Integration

Update Information:

https://cran.r-project.org/web/packages/Rcpp/news.html

References:

  [ 1 ] Bug #1453062 - Version  0.12.11 was released
https://bugzilla.redhat.com/show_bug.cgi?id=1453062




 cacti-1.1.7-1.fc24 (FEDORA-2017-13b078aae6)
 An rrd based graphing tool

Update Information:

- Update to 1.1.7  Release notes:
http://www.cacti.net/release_notes.php?version=1.1.7




 composer-1.4.2-2.fc24 (FEDORA-2017-b1905e59c9)
 Dependency Manager for PHP

Update Information:

**Version 1.4.2** - 2017-05-17* Fixed Bitbucket API handler parsing old
deleted branches in hg repos   * 

Verification testings and processes.

[Ryan]

  
  
Hello everyone,
I gave a shot at running a verification test. I was looking at Fedora_26_Branched_20170513.n.0
installation Should I be testing the milestones labeled as
  Final in the nightly builds?

I hope I did this the right way. Here is what I did.
Went to Fedora_26_Branched_20170513.n.0
installation, Image sanity, and chose the repoclosure test
  case. Followed the procedures and got the results below:
Added myrepo repo from /media
  Reading in repository metadata - please wait
  Checking Dependencies
  Repos looked at: 1
     myrepo
  Num Packages in Repos: 2836
  package: python-smbios-2.3.0-4.fc26.x86_64 from myrepo
    unresolved deps: 
   python-ctypes
Which shows one unresolved dependency. If I am correct this would
  qualify as a automatic blocker for the final release and I should
  submit a bug report and update the test results page to show
  failed?
I apologize I am just trying to familiarize myself with the
  layout and how things are done. So this test labeled as final for
  this particular build should have this issue resolved before it
  gets integrated into the main Fedora 26 build? I am just trying to
  understand this process. Once I am able to edit the appropriate
  pages and sections I will post my findings on this test and submit
  the bug report. If I did this wrong and missed a few steps could
  someone please point me in the right direction.

Thank you for your patience and help.
Ryan



  
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Updating the applications and launchers policy

[Michael Catanzaro]

At today's blocker meeting, Stephen suggested that this rule is somewhat out of 
place in our applications and launchers policy, which is a fair point. We 
decided to go with his suggestion instead, which is to not modify any policy 
and simply declare it a blocker.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Updating the applications and launchers policy

[Kamil Paral]

On Mon, May 22, 2017 at 5:25 PM, Stephen Gallagher 
wrote:

> On 05/22/2017 10:13 AM, Michael Catanzaro wrote:
> > Hi,
> >
> > Currently we have the following as a final blocker criterion:
> >
> > "All applications installed by default in Fedora Workstation must comply
> with each MUST and MUST NOT guideline in the Applications and Launchers
> policy."
> >
> > That policy is: http://fedoraproject.org/wiki/Workstation/Guidelines/
> Applications_and_Launchers
> >
> > We recently noticed that we don't have an available blocker criterion to
> deal with issues where an application unexpectedly appears in the default
> install. In particular, see https://bugzilla.redhat.com/
> show_bug.cgi?id=1449752 which has prompted this. We want the blivet-gui
> package maintainers to either create a subpackage for its desktop file, or
> otherwise figure something out to prevent blivet-gui from appearing as an
> application in our default install. The package maintainers do not want to
> do this, so we want a blocker criterion to force a resolution. I see two
> easy solutions here:
> >
> >  * We could add a new blocker criterion that explicitly says the
> Workstation WG gets to decide which applications are installed by default.
> >  * We could add that as a MUST guideline to our applications and
> launchers policy, since there is already a blocker criterion that covers
> that.
>

I think adding it to the policy is fine. However, please note that you
should either maintain a list of approved applications on the wiki, so that
we can check it from time to time, or you need to police that yourselves
and let us know (propose a blocker) when something like that happens (the
latter is better for us, of course).


> >
> > I'm planning to do the later and then propose this blivet-gui bug as a
> blocker. Is the QA team OK with this course of action? Do you prefer to
> just add a new criterion?
>
> I can't seem to find the original decision (it's been a few years of
> meetings
> now), but I'm pretty sure that FESCo actually ruled that the WGs have the
> right
> to declare a blocker to their Edition by fiat. So if the Workstation WG
> feels
> that the inclusion of the blivet-gui desktop file is unacceptable for the
> Workstation Edition, I *think* they can just declare it so.
>

If that turns out to be true, then it might be the easiest approach. Just
file a blocker proposal and describe what's wrong and that you're applying
your WG veto, and we'll auto-accept it. Of course, you can still add the
policy to the wiki (so that it's documented).


>
> CCing the FESCo list for anyone else there to chime in. (We also always
> have the
> option of FESCo making this declaration on your behalf as well.)
>
>
> ___
> 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

Re: Updating the applications and launchers policy

[Stephen Gallagher]

On 05/22/2017 10:13 AM, Michael Catanzaro wrote:
> Hi,
> 
> Currently we have the following as a final blocker criterion:
> 
> "All applications installed by default in Fedora Workstation must comply with 
> each MUST and MUST NOT guideline in the Applications and Launchers policy."
> 
> That policy is: 
> http://fedoraproject.org/wiki/Workstation/Guidelines/Applications_and_Launchers
> 
> We recently noticed that we don't have an available blocker criterion to deal 
> with issues where an application unexpectedly appears in the default install. 
> In particular, see https://bugzilla.redhat.com/show_bug.cgi?id=1449752 which 
> has prompted this. We want the blivet-gui package maintainers to either 
> create a subpackage for its desktop file, or otherwise figure something out 
> to prevent blivet-gui from appearing as an application in our default 
> install. The package maintainers do not want to do this, so we want a blocker 
> criterion to force a resolution. I see two easy solutions here:
> 
>  * We could add a new blocker criterion that explicitly says the Workstation 
> WG gets to decide which applications are installed by default.
>  * We could add that as a MUST guideline to our applications and launchers 
> policy, since there is already a blocker criterion that covers that.
> 
> I'm planning to do the later and then propose this blivet-gui bug as a 
> blocker. Is the QA team OK with this course of action? Do you prefer to just 
> add a new criterion?

I can't seem to find the original decision (it's been a few years of meetings
now), but I'm pretty sure that FESCo actually ruled that the WGs have the right
to declare a blocker to their Edition by fiat. So if the Workstation WG feels
that the inclusion of the blivet-gui desktop file is unacceptable for the
Workstation Edition, I *think* they can just declare it so.

CCing the FESCo list for anyone else there to chime in. (We also always have the
option of FESCo making this declaration on your behalf as well.)



signature.asc
Description: OpenPGP digital signature
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Updating the applications and launchers policy

[Michael Catanzaro]

I forgot to include the exact text that I'm planning to add. It would be:

"App launchers installed by default MUST be approved by the Workstation WG."

See also: https://pagure.io/fedora-workstation/issue/15

Michael
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Updating the applications and launchers policy

[Michael Catanzaro]

Hi,

Currently we have the following as a final blocker criterion:

"All applications installed by default in Fedora Workstation must comply with 
each MUST and MUST NOT guideline in the Applications and Launchers policy."

That policy is: 
http://fedoraproject.org/wiki/Workstation/Guidelines/Applications_and_Launchers

We recently noticed that we don't have an available blocker criterion to deal 
with issues where an application unexpectedly appears in the default install. 
In particular, see https://bugzilla.redhat.com/show_bug.cgi?id=1449752 which 
has prompted this. We want the blivet-gui package maintainers to either create 
a subpackage for its desktop file, or otherwise figure something out to prevent 
blivet-gui from appearing as an application in our default install. The package 
maintainers do not want to do this, so we want a blocker criterion to force a 
resolution. I see two easy solutions here:

 * We could add a new blocker criterion that explicitly says the Workstation WG 
gets to decide which applications are installed by default.
 * We could add that as a MUST guideline to our applications and launchers 
policy, since there is already a blocker criterion that covers that.

I'm planning to do the later and then propose this blivet-gui bug as a blocker. 
Is the QA team OK with this course of action? Do you prefer to just add a new 
criterion?

Michael
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Self Introduction

[Cecil Johnson]

Thank you for the sponsor. I'm currently downloading the fedora 25 workstation.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Fedora 24 updates-testing report

[updates]

The following Fedora 24 Security updates need testing:
 Age  URL
 152  https://bodhi.fedoraproject.org/updates/FEDORA-2016-26f9817b08   
squid-3.5.23-1.fc24
 146  https://bodhi.fedoraproject.org/updates/FEDORA-2016-eaaa9c4a08   
exim-4.87.1-1.fc24
 108  https://bodhi.fedoraproject.org/updates/FEDORA-2017-ece16ba6ba   
runc-1.0.0-5.rc2.gitc91b5be.fc24
  88  https://bodhi.fedoraproject.org/updates/FEDORA-2017-4b176c1694   
redis-3.2.8-1.fc24
  44  https://bodhi.fedoraproject.org/updates/FEDORA-2017-8330a48ca2   
python-XStatic-jquery-ui-1.12.0.1-1.fc24
  24  https://bodhi.fedoraproject.org/updates/FEDORA-2017-0b6da97aa5   
squirrelmail-1.4.22-19.fc24
  17  https://bodhi.fedoraproject.org/updates/FEDORA-2017-c3ce061ea7   
lynis-2.5.0-1.fc24
  16  https://bodhi.fedoraproject.org/updates/FEDORA-2017-7a0e2d58f8   
thunderbird-52.1.0-1.fc24
  15  https://bodhi.fedoraproject.org/updates/FEDORA-2017-ebe41f3fd7   
python-fedora-0.9.0-3.fc24
   9  https://bodhi.fedoraproject.org/updates/FEDORA-2017-01a7989fc0   
git-2.7.5-1.fc24
   9  https://bodhi.fedoraproject.org/updates/FEDORA-2017-4de07172f4   
postgresql-9.5.7-1.fc24
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2017-eaab38c11e   
deluge-1.3.15-1.fc24
   6  https://bodhi.fedoraproject.org/updates/FEDORA-2017-3f2d5790d2   
lxterminal-0.3.0-3.fc24 menu-cache-1.0.2-4.D20170514git56f6668459.fc24 
pcmanfm-1.2.5-2.fc24
   6  https://bodhi.fedoraproject.org/updates/FEDORA-2017-fc10e3165a   
FlightGear-2016.1.2-6.fc24
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2017-607352ce5f   
FlightCrew-0.9.1-7.fc24
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e75602d3ed   
kernel-4.10.16-100.fc24
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-7d698eba8b   
chromium-58.0.3029.110-2.fc24 
chromium-native_client-58.0.3029.81-1.20170421gitc948e9b.fc24
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-46fcfd8c98   
wordpress-4.7.5-1.fc24
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-dd5d2381e4   
libvncserver-0.9.11-2.fc24.1
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-1f15fde598   
moodle-3.1.6-1.fc24
   1  https://bodhi.fedoraproject.org/updates/FEDORA-2017-f426acf49d   
openvpn-2.3.16-1.fc24


The following Fedora 24 Critical Path updates have yet to be approved:
 Age URL
  31  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e1905fd566   
koji-1.12.0-2.fc24
  16  https://bodhi.fedoraproject.org/updates/FEDORA-2017-7a0e2d58f8   
thunderbird-52.1.0-1.fc24
   9  https://bodhi.fedoraproject.org/updates/FEDORA-2017-01a7989fc0   
git-2.7.5-1.fc24
   6  https://bodhi.fedoraproject.org/updates/FEDORA-2017-3f2d5790d2   
lxterminal-0.3.0-3.fc24 menu-cache-1.0.2-4.D20170514git56f6668459.fc24 
pcmanfm-1.2.5-2.fc24
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e2c9e5e8fe   
tigervnc-1.8.0-1.fc24
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e75602d3ed   
kernel-4.10.16-100.fc24
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-718c9992ef   
vim-8.0.600-1.fc24
   1  https://bodhi.fedoraproject.org/updates/FEDORA-2017-6f5c3ec36e   
python-coverage-4.4.1-1.fc24


The following builds have been pushed to Fedora 24 updates-testing

bsd-games-2.17-53.fc24
elementary-icon-theme-4.1.0-1.fc24
fcitx-configtool-0.4.9-1.fc24
fcitx-sunpinyin-0.4.1-9.fc24
freeorion-0.4.7-2.fc24
gnome-shell-extension-media-player-indicator-0-0.11.20170520git065ea3b.fc24
lizardfs-3.11.0-2.fc24
mycli-1.10.0-2.fc24
pcmanfm-qt-0.11.3-5.fc24
pssh-2.3.1-18.fc24
python-jenkins-0.4.14-2.fc24
smb4k-1.2.3-1.fc24
snapd-2.26.3-2.fc24
snapd-glib-1.12-1.fc24

Details about builds:



 bsd-games-2.17-53.fc24 (FEDORA-2017-5529e97fa5)
 Collection of text-based games

Update Information:

Update wtf to 20170512




 elementary-icon-theme-4.1.0-1.fc24 (FEDORA-2017-bf8952e8ef)
 Icons from the Elementary Project

Update Information:

Update to version 4.1.0.




 fcitx-configtool-0.4.9-1.fc24 (FEDORA-2017-310e5401c9)
 Gtk+-based configuring tools for Fcitx

Update Information:

Update to 0.4.9

References:

  [ 1 ] Bug #1420558 - fcitx-configtool-0.4.9 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1420558

Re: Self Introduction

[Sumantro Mukherjee]

- Original Message -
> From: "Cecil Johnson" 
> To: test@lists.fedoraproject.org
> Sent: Monday, May 22, 2017 2:08:55 PM
> Subject: Self Introduction
> 
> Hi guys,
> 
> My name is Cecil Johnson, I'm 26 years old and live at Kerala, Kochi.Im
> mechanical/Petroleum engineer with some knowledge in software testing and
> android development.
> 
> Even though in comparatively new to this, im a fast learner and hope i could
> be helpful to the cause.
> 
> Bye
> 
> 
> email: johnsonciz...@gmail.com
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 
Hey Cecil,
First of all, Welcome and thanks for showing your interest in Fedora QA.I've 
sponsored your request

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 alpha (Fedora 26 Branched 20170513), 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_20170513.n.0_Installation
[3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4]https://bugzilla.redhat.com/

PS we have a on-boarding call happening , here is a poll link which you can use 
to vote your preferred timing 
:https://beta.doodle.com/poll/hz6hcdx79f88g56r#table 

Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Self Introduction

[Cecil Johnson]

Hi guys,

My name is Cecil Johnson, I'm 26 years old and live at Kerala, Kochi.Im 
mechanical/Petroleum engineer with some knowledge in software testing and 
android development. 

Even though in comparatively new to this, im a fast learner and hope i could be 
helpful to the cause. 

Bye


email: johnsonciz...@gmail.com___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

[Test-Announce] [Test Day] i18n 2017-05-23

[Sumantro Mukherjee]

 Hey Testers, 

 
Tuesday 2017-05-23 will be i18n[1] Test Day!
As part of this planned Change[2] for Fedora 26, So this is an important Test 
Day! 
Test Day will focus on testing Internationalization a.k.a. i18n around Desktops 
including their applications.
This aims to ensure if i18n support works enough on them. 


We hope to see whether it’s working well enough and catch any remaining issues. 
As always, the event will be in #fedora-test-day on Freenode IRC.

[1]: https://fedoraproject.org/wiki/Test_Day:2017-05-23_I18N_Test_Day
[2]: http://fedoraproject.org/wiki/Changes/libpinyin2.0
 http://fedoraproject.org/wiki/Changes/FontconfigCacheDirChange

Thanks 
//sumantrom
___
test-announce mailing list -- test-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org

[Test-Announce] Fedora 26 Beta Go/No-Go Meeting on Thursday, May 25 @ 17:00 UTC

[Jan Kurik]

Join us on irc.freenode.net in #fedora-meeting-2 for this important
meeting, wherein we shall determine the readiness of the Fedora 26
Beta.

The meeting is going to be held on Thursday, May 25, 2017 at 17:00
UTC. Please check the [1] link for your time zone.

Before each public release Development, QA and Release Engineering
meet to determine if the release criteria are met for a particular
release. This meeting is called the Go/No-Go Meeting. Verifying that
the Release criteria are met is the responsibility of the QA Team.

Release Candidate (RC) availability and good QA coverage are
prerequisites for the Go/No-Go meeting. If you have any bug on the
list, please help us with Beta release. If we won't be ready by
Thursday, we will use this meeting to review blockers and decide what
to do.

In the meantime, please keep also an eye on the Fedora 26 Beta Blocker list [2].

For more details about this meeting please follow the [3] link.

[1] https://apps.fedoraproject.org/calendar/meeting/5760/
[2] http://qa.fedoraproject.org/blockerbugs/milestone/26/beta/buglist
[3] https://fedoraproject.org/wiki/Go_No_Go_Meeting

Thank you in advance for your support.
Regards, Jan

-- 
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
___
test-announce mailing list -- test-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org

Re: Introduction

[Sumantro Mukherjee]

- Original Message -
> From: "Ryan" 
> To: "Fedora Test List" 
> Sent: Sunday, May 21, 2017 10:36:36 PM
> Subject: Introduction
> 
> Hello all,
> 
> My name is Ryan Alecci, I am 21 years old and currently live in
> California. I have been using Linux for the last four years. I have
> experimented with Arch, CentOS, Fedora and Redhat. I am looking forward
> to learning from all of you.
> 
> I have never done any community involvement or contributed to anything
> related to Linux but I am looking to get involved and learn. I am just
> looking for a place to start where I can learn.
> 
> I have some experience with system administration and setting up
> media/NAS/Home servers. I have limited programming knowledge with python
> and writing bash scripts. I like to tinker with the Operating Systems
> and get under the hood and see what I can tweak and change.
> 
> 
> Contact
> 
> IRC: S0ulz @ irc.freenode.net (I am usually on around 4pm PST)
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 

Hey Ryan,

First of all, Welcome and thanks for showing your interest in Fedora QA. You 
can start by sending a request to the Fedora QA FAS group 
[https://admin.fedoraproject.org/accounts/group/application_screen/qa]

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 alpha (Fedora 26 Branched 20170513), 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_20170513.n.0_Installation
[3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4]https://bugzilla.redhat.com/

Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org