Fedora 26 updates-testing report

2017-07-16 Thread updates
The following Fedora 26 Security updates need testing:
 Age  URL
 100  https://bodhi.fedoraproject.org/updates/FEDORA-2017-1bf5a0ce01   
python-XStatic-jquery-ui-1.12.0.1-2.fc26
  39  https://bodhi.fedoraproject.org/updates/FEDORA-2017-2522df3526   
nodejs-brace-expansion-1.1.7-1.fc26
  10  https://bodhi.fedoraproject.org/updates/FEDORA-2017-b8bb4b86e2   
php-7.1.7-1.fc26
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-d3d38a53f9   
knot-2.4.5-1.fc26
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-114e1abf9d   
irssi-1.0.4-1.fc26
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-661dddc462   
groovy18-1.8.9-28.fc26
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e6aaef4475   
knot-resolver-1.3.1-1.fc26
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-2afe501b36   
heimdal-7.4.0-1.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e8bdc4ede0   
kernel-4.11.10-300.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-a40590256c   
glpi-9.1.5-1.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-8f018a3d39   
golang-1.8.3-1.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-690a2548ba   
openvswitch-2.7.1-2.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-bbb664e0a0   
mingw-poppler-0.52.0-3.fc26
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-7c1621d2e8   
nodejs-6.11.1-1.fc26
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-05888dd4fe   
phpldapadmin-1.2.3-10.fc26
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-0642394b5a   
minicom-2.7.1-1.fc26
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-088b16a69a   
yara-3.6.3-1.fc26


The following Fedora 26 Critical Path updates have yet to be approved:
 Age URL
   8  https://bodhi.fedoraproject.org/updates/FEDORA-2017-73370082fb   
garcon-0.6.1-1.fc26
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-244f799ac9   
nss-3.31.0-1.0.fc26 nss-util-3.31.0-1.0.fc26 nss-softokn-3.31.0-1.0.fc26 
nspr-4.15.0-1.fc26
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-654872eda8   
lorax-26.9-1.fc26
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-f6b14e0e63   
supermin-5.1.18-1.fc26
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-aa537fe626   
libproxy-0.4.15-2.fc26
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-ad7e5c5657   
libvirt-3.2.1-4.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-97c48d9a81   
qemu-2.9.0-3.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e8bdc4ede0   
kernel-4.11.10-300.fc26
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-9fb17899f4   
python-setuptools-36.2.0-1.fc26
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-28fd8ef47d   
unzip-6.0-34.fc26


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

GtkAda-2.24.2-23.fc26
GtkAda3-3.14.2-4.fc26
PragmARC-20130728-13.fc26
abbayedesmorts-gpl-2.0.1-3.20170709git.fc26
ahven-2.6-6.fc26
anet-0.3.4-2.fc26
clpeak-0.1-14.20170711git8edab23.fc26
cvc4-1.5-1.fc26
git-extras-4.4.0-1.fc26
golang-github-klauspost-reedsolomon-1.4-1.fc26
hspell-1.4-1.fc26
libmwaw-0.3.12-1.fc26
libvmi-0.11.0-8.20170214gite919365.fc26
mine_detector-6.0-30.fc26
minicom-2.7.1-1.fc26
mldonkey-3.1.6-1.fc26
naev-0.7.0-1.fc26
naev-data-0.7.0-2.fc26
ocaml-menhir-20170712-1.fc26
python-glyphsLib-1.7.5-2.fc26
python-jinja2-cli-0.6.0-1.fc26
python-multidict-3.1.3-1.fc26
python-setuptools-36.2.0-1.fc26
python-yarl-0.12.0-1.fc26
tmux-2.5-1.fc26
tomboy-1.15.9-1.fc26
xed-1.4.6-1.fc26
yara-3.6.3-1.fc26
zfs-fuse-0.7.2.2-4.fc26
zlib-ada-1.4-0.16.20120830CVS.fc26
zstd-1.3.0-1.fc26

Details about builds:



 GtkAda-2.24.2-23.fc26 (FEDORA-2017-b75de105b2)
 GTKada 2, an Ada binding to GTK+ 2

Update Information:

Ada packages had to be rebuilt because GCC 7.1 invalidated the ALI files.




 GtkAda3-3.14.2-4.fc26 (FEDORA-2017-b75de105b2)
 GTKada 3, an Ada binding to GTK+ 3

Update Information:

Ada packages had to be rebuilt because GCC 7.1 invalidated the ALI files.




 PragmARC-20130728-13.fc26 (FEDORA-2017-b75de105b2)
 PragmAda Reusable Components, a component library for Ada

Update Information:

Ada packages had to be rebuilt because GCC 7.1 invalidated 

Fedora 25 updates-testing report

2017-07-16 Thread updates
The following Fedora 25 Security updates need testing:
 Age  URL
 201  https://bodhi.fedoraproject.org/updates/FEDORA-2016-d79ba708cb   
exim-4.87.1-1.fc25
 100  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e2d17af41e   
python-XStatic-jquery-ui-1.12.0.1-4.fc25
  44  https://bodhi.fedoraproject.org/updates/FEDORA-2017-7dbbbafea6   
runc-1.0.0-7.git6394544.fc25.2
  39  https://bodhi.fedoraproject.org/updates/FEDORA-2017-ec3c82e64d   
libstaroffice-0.0.3-3.fc25
  39  https://bodhi.fedoraproject.org/updates/FEDORA-2017-5d7498559f   
nodejs-brace-expansion-1.1.7-1.fc25
  11  https://bodhi.fedoraproject.org/updates/FEDORA-2017-1ca18683e4   
openldap-2.4.44-11.fc25
   8  https://bodhi.fedoraproject.org/updates/FEDORA-2017-b9e4c24094   
subversion-1.9.6-1.fc25
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-b0a2770a9b   
knot-2.4.5-1.fc25
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-90ad72e684   
irssi-1.0.4-1.fc25
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-efdd962fee   
putty-0.70-1.fc25
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-c844713925   
qt5-qtwebkit-5.212.0-0.5.alpha2.fc25
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-33c8085c5d   
groovy18-1.8.9-28.fc25
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-92643d70b7   
knot-resolver-1.3.1-1.fc25
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-7eaec3353d   
poppler-0.45.0-5.fc25
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-5d6a9e0c9c   
heimdal-7.4.0-1.fc25
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-f941184db1   
qemu-2.7.1-7.fc25
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-f2f29441f9   
kernel-4.11.10-200.fc25
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-cc0b92f6c1   
glpi-9.1.5-1.fc25
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-9fa2cefa7a   
mingw-poppler-0.45.0-3.fc25
   1  https://bodhi.fedoraproject.org/updates/FEDORA-2017-81522ac6d8   
nodejs-6.11.1-1.fc25
   1  https://bodhi.fedoraproject.org/updates/FEDORA-2017-346836a623   
phpldapadmin-1.2.3-10.fc25
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-90cf7a82de   
minicom-2.7.1-1.fc25
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-2d8a1226d1   
libmwaw-0.3.12-1.fc25
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-c22a8af4e9   
rubygem-rack-cors-0.4.1-1.fc25
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-1d46019681   
yara-3.6.3-1.fc25


The following Fedora 25 Critical Path updates have yet to be approved:
 Age URL
  44  https://bodhi.fedoraproject.org/updates/FEDORA-2017-613a72e282   
lorax-25.22-1.fc25
  22  https://bodhi.fedoraproject.org/updates/FEDORA-2017-0187b2a605   
selinux-policy-3.13.1-225.19.fc25
  16  https://bodhi.fedoraproject.org/updates/FEDORA-2017-118505dd77   
libsoup-2.56.0-3.fc25
  11  https://bodhi.fedoraproject.org/updates/FEDORA-2017-a90ed7e59d   
libtirpc-1.0.2-0.fc25
  11  https://bodhi.fedoraproject.org/updates/FEDORA-2017-1ca18683e4   
openldap-2.4.44-11.fc25
  11  https://bodhi.fedoraproject.org/updates/FEDORA-2017-7cd9e81996   
quota-4.03-8.fc25
   9  https://bodhi.fedoraproject.org/updates/FEDORA-2017-b18eded0a5   
glusterfs-3.10.4-1.fc25
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-ebeb4bb332   
mariadb-10.1.25-1.fc25
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-ddd2aa1a04   
xen-4.7.3-1.fc25
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e587cfd70e   
supermin-5.1.18-1.fc25
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-f21d307d97   
nss-3.31.0-1.0.fc25 nss-softokn-3.31.0-1.0.fc25 nss-util-3.31.0-1.0.fc25 
nspr-4.15.0-1.fc25
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-04bf7c03b8   
libproxy-0.4.15-2.fc25
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-f941184db1   
qemu-2.7.1-7.fc25
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-7eaec3353d   
poppler-0.45.0-5.fc25
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-6d834aa7e7   
breeze-icon-theme-5.36.0-1.fc25 extra-cmake-modules-5.36.0-1.fc25 
kf5-5.36.0-1.fc25 kf5-attica-5.36.0-1.fc25 kf5-baloo-5.36.0-1.fc25 
kf5-bluez-qt-5.36.0-1.fc25 kf5-frameworkintegration-5.36.0-1.fc25 
kf5-kactivities-5.36.0-1.fc25 kf5-kactivities-stats-5.36.0-1.fc25 
kf5-kapidox-5.36.0-1.fc25 kf5-karchive-5.36.0-1.fc25 kf5-kauth-5.36.0-1.fc25 
kf5-kbookmarks-5.36.0-1.fc25 kf5-kcmutils-5.36.0-1.fc25 
kf5-kcodecs-5.36.0-1.fc25 kf5-kcompletion-5.36.0-1.fc25 
kf5-kconfig-5.36.0-1.fc25 kf5-kconfigwidgets-5.36.0-1.fc25 
kf5-kcoreaddons-5.36.0-1.fc25 kf5-kcrash-5.36.0-1.fc25 
kf5-kdbusaddons-5.36.0-1.fc25 kf5-kdeclarative-5.36.0-1.fc25 
kf5-kded-5.36.0-1.fc25 kf5-kdelibs4support-5.36.0-1.fc25 
kf5-kdesignerplugin-5.36.0-1.fc25 kf5-kdesu-5.36.0-1.fc25 
kf5-kdewebkit-5.36.0-1.fc25 kf5-kdnssd-5.36.0-1.fc25 
kf5-kdoctools-5.36.0-1.fc25 kf5-kemoticons-5.36.0-1.fc25 
kf5-kfilemetadata-5.36.0-1.fc25 kf5-kglobalaccel-5.36.0-1.fc25 kf5-kguiad
 dons-5.36.0-2.fc25 

Fedora 24 updates-testing report

2017-07-16 Thread updates
The following Fedora 24 Security updates need testing:
 Age  URL
 208  https://bodhi.fedoraproject.org/updates/FEDORA-2016-26f9817b08   
squid-3.5.23-1.fc24
 201  https://bodhi.fedoraproject.org/updates/FEDORA-2016-eaaa9c4a08   
exim-4.87.1-1.fc24
 164  https://bodhi.fedoraproject.org/updates/FEDORA-2017-ece16ba6ba   
runc-1.0.0-5.rc2.gitc91b5be.fc24
 100  https://bodhi.fedoraproject.org/updates/FEDORA-2017-8330a48ca2   
python-XStatic-jquery-ui-1.12.0.1-1.fc24
  39  https://bodhi.fedoraproject.org/updates/FEDORA-2017-5f1006afb1   
libstaroffice-0.0.3-3.fc24
  39  https://bodhi.fedoraproject.org/updates/FEDORA-2017-a1f4c48c68   
nodejs-brace-expansion-1.1.7-1.fc24
  30  https://bodhi.fedoraproject.org/updates/FEDORA-2017-bbae64fdc2   
libmwaw-0.3.11-3.fc24
  19  https://bodhi.fedoraproject.org/updates/FEDORA-2017-37f68e3534   
webkitgtk4-2.16.5-1.fc24
  19  https://bodhi.fedoraproject.org/updates/FEDORA-2017-56cf7067e7   
irssi-1.0.3-1.fc24
   9  https://bodhi.fedoraproject.org/updates/FEDORA-2017-5ade380ab2   
php-5.6.31-1.fc24
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-bd6aa662fc   
knot-2.4.5-1.fc24
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-21c0e9b25b   
qt5-qtwebkit-5.212.0-0.5.alpha2.fc24
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-405453f285   
groovy18-1.8.9-28.fc24
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-081fc9ad77   
knot-resolver-1.3.1-1.fc24
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-61689edaf4   
spice-0.12.8-3.fc24
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-06c1422db8   
evince-3.20.1-3.fc24
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-5ce9d89b82   
kernel-4.11.10-100.fc24
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-93868169a0   
mingw-poppler-0.41.0-3.fc24
   1  https://bodhi.fedoraproject.org/updates/FEDORA-2017-aa44293a53   
nodejs-4.8.4-6.fc24
   1  https://bodhi.fedoraproject.org/updates/FEDORA-2017-1a8bebaab4   
phpldapadmin-1.2.3-10.fc24
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-31af7a849d   
minicom-2.7.1-1.fc24
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-944e86b623   
yara-3.6.3-1.fc24


The following Fedora 24 Critical Path updates have yet to be approved:
 Age URL
  19  https://bodhi.fedoraproject.org/updates/FEDORA-2017-37f68e3534   
webkitgtk4-2.16.5-1.fc24
  17  https://bodhi.fedoraproject.org/updates/FEDORA-2017-6c2a7b1453   
thunderbird-52.2.1-1.fc24
  11  https://bodhi.fedoraproject.org/updates/FEDORA-2017-bc6b0dec8a   
gnome-keyring-3.20.1-1.fc24
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-5a6f49afbd   
mariadb-10.1.25-1.fc24
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-de05b989aa   
net-snmp-5.7.3-14.fc24
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-5ce9d89b82   
kernel-4.11.10-100.fc24


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

clpeak-0.1-14.20170711git8edab23.fc24
git-extras-4.4.0-1.fc24
golang-github-klauspost-reedsolomon-1.4-1.fc24
minicom-2.7.1-1.fc24
tomboy-1.15.9-1.fc24
xed-1.4.6-1.fc24
yara-3.6.3-1.fc24
zstd-1.3.0-1.fc24

Details about builds:



 clpeak-0.1-14.20170711git8edab23.fc24 (FEDORA-2017-3771bf0ea6)
 Find peak OpenCL capacities like bandwidth & compute

Update Information:

- Update to the latest upstream, fixes rhbz#1423267 - Include upstream fix for
https://github.com/krrishnarraj/clpeak/issues/36

References:

  [ 1 ] Bug #1423267 - clpeak: FTBFS in rawhide
https://bugzilla.redhat.com/show_bug.cgi?id=1423267




 git-extras-4.4.0-1.fc24 (FEDORA-2017-07c59a88a4)
 Little git extras

Update Information:

git-extras-4.4.0 is available

References:

  [ 1 ] Bug #1471372 - git-extras-4.4.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1471372




 golang-github-klauspost-reedsolomon-1.4-1.fc24 (FEDORA-2017-9e7225b6de)
 Reed-Solomon Erasure Coding in Go

Update Information:

Update to version 1.4.




 minicom-2.7.1-1.fc24 (FEDORA-2017-31af7a849d)
 

Re: keyboard producing diacritics (acute accent, dot-above, cedilla-below)

2017-07-16 Thread George R Goffe
Stan,

Thanks for your response.


Text widgets like email in Firefox and various sites, including 
bugzilla.redhat.com. Sigh.

Except for the fact that this is a rawhide system, it's been quite stable. This 
system has a lot of the package groups installed. I did this to look for 
package and packagemanagement bugs. I did the group installs "with optional" 
right after I did the install. The problem didn't appear until later, a couple 
of weeks ago.

I am sure it's something in the system because I rarely use Opera. I am a 
fairly heavy user of Firefox. They used to have an option for "Western" 
encoding but that has gone away and the view->text encoding seems adamant on 
"unicode", autodetect is off. Also, I removed as much of KDE related files 
(.kde* .config* .gtk* .cache* .gnome*) from my userid and then started kde 
freshly. Either I missed a file or it's not KDE. I'm going to try both with 
WindowMaker.


The keyboard is a USB HP version and has "US" on the back... I haven't swapped 
out the keyboard yet though. I'm grasping at straws.

Thanks again for your response.

George...






From: stan 
To: test@lists.fedoraproject.org 
Cc: George R Goffe 
Sent: Sunday, July 16, 2017 2:15 PM
Subject: Re: keyboard producing diacritics (acute accent, dot-above, 
cedilla-below)



On Sun, 16 Jul 2017 13:21:58 + (UTC)
George R Goffe  wrote:

> System is Fedora 27 x86_64 (rawhide), fully up to date with the
> rawhide repo. 

[snip]


> Firefox and Opera are producing diacritics (acute accent, dot-above, 
> cedilla-below) when I type in text windows. Other apps such as
> konsole seem to work just fine and I have not seen this problem
> elsewhere.
> Any/all hints/tips/suggestions would be greatly appreciated.

I was just using firefox in a fully updated rawhide, and I didn't see
this at all.  What specifically do you mean by 'text windows'?  I
assume you mean input dialogs, like the url line, etc. .  It is probably
a setting you have somewhere, but I don't know where that would be. Have
you looked in the configuration for firefox or opera to see if somehow
something changed the defaults?
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


[Test-Announce] 2017-07-17 @ 15:00 UTC - Fedora QA Meeting

2017-07-16 Thread Adam Williamson
# Fedora Quality Assurance Meeting
# Date: 2017-07-17
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net

Greetings testers!

We didn't get through everything last week, so let's have a follow-up
meeting.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 27 planning
3. Storage test matrix update status
4. Open floor
-- 
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: Error when trying to go to f27

2017-07-16 Thread stan
On Sun, 16 Jul 2017 13:40:14 +0800
Ed Greshko  wrote:

> On 07/16/17 13:27, Ed Greshko wrote:
> > On 07/16/17 13:11, Samuel Sieb wrote:  
> >> On 07/15/2017 10:00 PM, Ed Greshko wrote:  
> >>> Trying to get a test system installed on a VM which is a clone of
> >>> a fully updated F26 system.

I don't think there is an updates repository for rawhide.  At least I
never see on when it is updating usind dnf.  It just pulls from the
rawhide repository, and that's all.  When I look in /etc/yum.repos.d
all I see is fedora-rawhide.repo.

When I've wanted to update a clone to rawhide in the past, I just
grabbed the fedora-release files for rawhide from koji, installed them,
checked that the current release repos were turned off, rawhide was
turned on, and ran dnf upgrade.  It worked, barring all the obsoletes
and their consequences.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Fedora 26 updates-testing report

2017-07-16 Thread updates
The following Fedora 26 Security updates need testing:
 Age  URL
 100  https://bodhi.fedoraproject.org/updates/FEDORA-2017-1bf5a0ce01   
python-XStatic-jquery-ui-1.12.0.1-2.fc26
  39  https://bodhi.fedoraproject.org/updates/FEDORA-2017-2522df3526   
nodejs-brace-expansion-1.1.7-1.fc26
  10  https://bodhi.fedoraproject.org/updates/FEDORA-2017-b8bb4b86e2   
php-7.1.7-1.fc26
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-d3d38a53f9   
knot-2.4.5-1.fc26
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-114e1abf9d   
irssi-1.0.4-1.fc26
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-661dddc462   
groovy18-1.8.9-28.fc26
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e6aaef4475   
knot-resolver-1.3.1-1.fc26
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-2afe501b36   
heimdal-7.4.0-1.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e8bdc4ede0   
kernel-4.11.10-300.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-a40590256c   
glpi-9.1.5-1.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-8f018a3d39   
golang-1.8.3-1.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-690a2548ba   
openvswitch-2.7.1-2.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-bbb664e0a0   
mingw-poppler-0.52.0-3.fc26
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-7c1621d2e8   
nodejs-6.11.1-1.fc26
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-05888dd4fe   
phpldapadmin-1.2.3-10.fc26


The following Fedora 26 Critical Path updates have yet to be approved:
 Age URL
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2017-73370082fb   
garcon-0.6.1-1.fc26
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-244f799ac9   
nss-3.31.0-1.0.fc26 nss-util-3.31.0-1.0.fc26 nss-softokn-3.31.0-1.0.fc26 
nspr-4.15.0-1.fc26
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2017-654872eda8   
lorax-26.9-1.fc26
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-f6b14e0e63   
supermin-5.1.18-1.fc26
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-aa537fe626   
libproxy-0.4.15-2.fc26
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2017-ad7e5c5657   
libvirt-3.2.1-4.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-97c48d9a81   
qemu-2.9.0-3.fc26
   2  https://bodhi.fedoraproject.org/updates/FEDORA-2017-e8bdc4ede0   
kernel-4.11.10-300.fc26
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2017-28fd8ef47d   
unzip-6.0-34.fc26


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

btbuilder-0.5.15-1.fc26
cacti-1.1.13-1.fc26
calligra-3.0.1-6.fc26
container-selinux-2.21-1.fc26
containernetworking-cni-0.5.2-3.fc26
copr-dist-git-0.32-1.fc26
copr-frontend-1.115-1.fc26
fleet-commander-admin-0.10.1-1.fc26
golang-github-cznic-lexer-0-0.1.20141211.git52ae786.fc26
golang-github-cznic-lldb-1.1.0-1.fc26
lftp-4.8.0-1.fc26
libtaskotron-0.4.24-1.fc26
lynis-2.5.2-1.fc26
mate-panel-1.18.3-4.fc26
nagios-plugins-2.2.1-4git.fc26
nodejs-6.11.1-1.fc26
nrpe-3.2.0-2git.fc26
oci-register-machine-0-3.10.gitcbf1b8f.fc26
ostrichriders-0.6.4-2.fc26
perl-Cache-FastMmap-1.46-1.fc26
php-JMSParser-1.0.0-9.fc26
php-Metadata-1.6.0-1.fc26
php-PhpCollection-0.5.0-1.fc26
php-PhpOption-1.5.0-1.fc26
phpldapadmin-1.2.3-10.fc26
plasma-discover-5.10.2-1.fc26
python-compyte-0.0.1-0.8.git11dc003.fc26
python-m2ext-0.1-12.fc26
python-pymod2pkg-0.6.1-4.fc26
python-pyopencl-2017.2-1.fc26
python-pytools-2017.3-1.fc26
python-slackclient-1.0.6-2.fc26
qt-creator-4.2.2-5.fc26
qucs-0.0.18-10.fc26
switchboard-plug-printers-0.1.1-1.fc26
terminology-1.0.0-3.fc26
torrent-file-editor-0.3.6-1.fc26
trace-cmd-2.6.1-1.fc26
unzip-6.0-34.fc26

Details about builds:



 btbuilder-0.5.15-1.fc26 (FEDORA-2017-c32314a9e1)
 Turn based role-playing game builder and engine

Update Information:

New version of btbuilder released.




 cacti-1.1.13-1.fc26 (FEDORA-2017-b4ed8be9a5)
 An rrd based graphing tool

Update Information:

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

References:

  [ 1 ] Bug #1471091 - None
https://bugzilla.redhat.com/show_bug.cgi?id=1471091




 calligra-3.0.1-6.fc26 

Re: keyboard producing diacritics (acute accent, dot-above, cedilla-below)

2017-07-16 Thread stan
On Sun, 16 Jul 2017 13:21:58 + (UTC)
George R Goffe  wrote:

> System is Fedora 27 x86_64 (rawhide), fully up to date with the
> rawhide repo. 

[snip]

> Firefox and Opera are producing diacritics (acute accent, dot-above, 
> cedilla-below) when I type in text windows. Other apps such as
> konsole seem to work just fine and I have not seen this problem
> elsewhere.
> Any/all hints/tips/suggestions would be greatly appreciated.

I was just using firefox in a fully updated rawhide, and I didn't see
this at all.  What specifically do you mean by 'text windows'?  I
assume you mean input dialogs, like the url line, etc. .  It is probably
a setting you have somewhere, but I don't know where that would be. Have
you looked in the configuration for firefox or opera to see if somehow
something changed the defaults?
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: F26 doesn't wake up after updates

2017-07-16 Thread Michael Schwendt
On Sun, 16 Jul 2017 11:40:28 -0400, Richard Ryniker wrote:

> I have found some problems with resume from suspended state to be much
> improved after I switched to "GNOME on xorg".  It is too soon  to
> conclude they will not recur, but several days have passed without
> difficulty.

It has worked for me for a very long time. AFK, then GNOME Shell
blank screen power saving kicks it after some time (10 mins or so
as customized in the settings), and when I return, I can unlock the
screen, enter password and continue without problems. One of the updates
has introduced breakage.

Meanwhile, I've installed F26 Workstation from Live USB, and after
rebooting, I arrive at the login screen, but after typing in the password,
the system freezes completely. Empty screen, grey background from display
manager, mouse pointer in the middle of the screen, no response at all
anymore. Haven't given it another try yet. In any way, it's some embarrassing
instability in some component.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: F26 doesn't wake up after updates

2017-07-16 Thread Richard Ryniker
I have found some problems with resume from suspended state to be much
improved after I switched to "GNOME on xorg".  It is too soon  to
conclude they will not recur, but several days have passed without
difficulty.

F26 up-to-date on a Lenovo Yoga 3 11-inch laptop, model name 80J8.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


keyboard producing diacritics (acute accent, dot-above, cedilla-below)

2017-07-16 Thread George R Goffe
Hi,


System is Fedora 27 x86_64 (rawhide), fully up to date with the rawhide repo. 


Firefox and Opera are producing diacritics (acute accent, dot-above, 
cedilla-below) when I type in text windows. Other apps such as konsole 
seem to work just fine and I have not seen this problem elsewhere.


locale says:


LANG=en_US.UTF-8

LC_CTYPE="en_US.UTF-8"

LC_NUMERIC="en_US.UTF-8"

LC_TIME="en_US.UTF-8"

LC_COLLATE="en_US.UTF-8"

LC_MONETARY="en_US.UTF-8"

LC_MESSAGES="en_US.UTF-8"

LC_PAPER="en_US.UTF-8"

LC_NAME="en_US.UTF-8"

LC_ADDRESS="en_US.UTF-8"

LC_TELEPHONE="en_US.UTF-8"

LC_MEASUREMENT="en_US.UTF-8"

LC_IDENTIFICATION="en_US.UTF-8"

LC_ALL=


Any/all hints/tips/suggestions would be greatly appreciated.


Thanks,


George...

Try the new Yahoo Mail 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


F26 doesn't wake up after updates

2017-07-16 Thread Michael Schwendt
Since an update of F26 on Friday, F26 GNOME Shell doesn't wake up anymore
after entering default power-saving mode. Black screen. Monitor doesn't
wake up. No reaction to keyboard or mouse.

python2-fedora-0.9.0-6.fc26.noarchFri 14 Jul 2017 11:44:30 PM CEST
vim-minimal-8.0.705-1.fc26.x86_64 Fri 14 Jul 2017 11:44:29 PM CEST
rpmfusion-free-release-26-1.noarchFri 14 Jul 2017 11:44:29 PM CEST
rpmfusion-free-appstream-data-26-2.fc26.noarch Fri 14 Jul 2017 11:44:29 PM CEST
pcre-utf16-8.41-1.fc26.x86_64 Fri 14 Jul 2017 11:44:28 PM CEST
mutter-3.24.3-2.fc26.x86_64   Fri 14 Jul 2017 11:44:27 PM CEST
lz4-libs-1.7.5-4.fc26.x86_64  Fri 14 Jul 2017 11:44:26 PM CEST
lz4-1.7.5-4.fc26.x86_64   Fri 14 Jul 2017 11:44:26 PM CEST
glibc-langpack-en-2.25-7.fc26.x86_64  Fri 14 Jul 2017 11:44:26 PM CEST
python3-brlapi-0.6.6-5.fc26.x86_64Fri 14 Jul 2017 11:44:25 PM CEST
openssh-server-7.5p1-3.fc26.x86_64Fri 14 Jul 2017 11:44:25 PM CEST
evince-djvu-3.24.0-3.fc26.x86_64  Fri 14 Jul 2017 11:44:25 PM CEST
glibc-devel-2.25-7.fc26.x86_64Fri 14 Jul 2017 11:44:24 PM CEST
evince-nautilus-3.24.0-3.fc26.x86_64  Fri 14 Jul 2017 11:44:24 PM CEST
pciutils-3.5.5-1.fc26.x86_64  Fri 14 Jul 2017 11:44:23 PM CEST
ostree-2017.8-2.fc26.x86_64   Fri 14 Jul 2017 11:44:23 PM CEST
f26-backgrounds-gnome-26.2.6-1.fc26.noarchFri 14 Jul 2017 11:44:23 PM CEST
libreoffice-x11-5.3.4.2-3.fc26.x86_64 Fri 14 Jul 2017 11:44:22 PM CEST
libreofficekit-5.3.4.2-3.fc26.x86_64  Fri 14 Jul 2017 11:44:22 PM CEST
libreoffice-gtk2-5.3.4.2-3.fc26.x86_64Fri 14 Jul 2017 11:44:22 PM CEST
libreoffice-emailmerge-5.3.4.2-3.fc26.x86_64  Fri 14 Jul 2017 11:44:22 PM CEST
libreoffice-xsltfilter-5.3.4.2-3.fc26.x86_64  Fri 14 Jul 2017 11:44:21 PM CEST
libreoffice-filters-5.3.4.2-3.fc26.x86_64 Fri 14 Jul 2017 11:44:21 PM CEST
libreoffice-math-5.3.4.2-3.fc26.x86_64Fri 14 Jul 2017 11:44:20 PM CEST
libreoffice-impress-5.3.4.2-3.fc26.x86_64 Fri 14 Jul 2017 11:44:20 PM CEST
libreoffice-calc-5.3.4.2-3.fc26.x86_64Fri 14 Jul 2017 11:44:19 PM CEST
libreoffice-pdfimport-5.3.4.2-3.fc26.x86_64   Fri 14 Jul 2017 11:44:17 PM CEST
libreoffice-graphicfilter-5.3.4.2-3.fc26.x86_64 Fri 14 Jul 2017 11:44:17 PM CEST
libreoffice-draw-5.3.4.2-3.fc26.x86_64Fri 14 Jul 2017 11:44:17 PM CEST
libreoffice-writer-5.3.4.2-3.fc26.x86_64  Fri 14 Jul 2017 11:44:16 PM CEST
libreoffice-pyuno-5.3.4.2-3.fc26.x86_64   Fri 14 Jul 2017 11:44:15 PM CEST
libreoffice-langpack-en-5.3.4.2-3.fc26.x86_64 Fri 14 Jul 2017 11:44:14 PM CEST
libreoffice-core-5.3.4.2-3.fc26.x86_64Fri 14 Jul 2017 11:44:14 PM CEST
libreoffice-gtk3-5.3.4.2-3.fc26.x86_64Fri 14 Jul 2017 11:43:58 PM CEST
libreoffice-ure-5.3.4.2-3.fc26.x86_64 Fri 14 Jul 2017 11:43:57 PM CEST
f26-backgrounds-base-26.2.6-1.fc26.noarch Fri 14 Jul 2017 11:43:57 PM CEST
autocorr-en-5.3.4.2-3.fc26.noarch Fri 14 Jul 2017 11:43:57 PM CEST
pciutils-libs-3.5.5-1.fc26.x86_64 Fri 14 Jul 2017 11:43:55 PM CEST
libreoffice-ure-common-5.3.4.2-3.fc26.noarch  Fri 14 Jul 2017 11:43:55 PM CEST
libreoffice-opensymbol-fonts-5.3.4.2-3.fc26.noarch Fri 14 Jul 2017 11:43:55 PM 
CEST
ostree-libs-2017.8-2.fc26.x86_64  Fri 14 Jul 2017 11:43:54 PM CEST
glibc-headers-2.25-7.fc26.x86_64  Fri 14 Jul 2017 11:43:54 PM CEST
evince-3.24.0-3.fc26.x86_64   Fri 14 Jul 2017 11:43:52 PM CEST
perl-Git-2.13.3-1.fc26.noarch Fri 14 Jul 2017 11:43:48 PM CEST
git-2.13.3-1.fc26.x86_64  Fri 14 Jul 2017 11:43:48 PM CEST
git-core-doc-2.13.3-1.fc26.x86_64 Fri 14 Jul 2017 11:43:47 PM CEST
git-core-2.13.3-1.fc26.x86_64 Fri 14 Jul 2017 11:43:45 PM CEST
openssh-clients-7.5p1-3.fc26.x86_64   Fri 14 Jul 2017 11:43:44 PM CEST
pcre-8.41-1.fc26.x86_64   Fri 14 Jul 2017 11:43:33 PM CEST
expat-2.2.1-1.fc26.x86_64 Fri 14 Jul 2017 11:43:33 PM CEST
brlapi-0.6.6-5.fc26.x86_64Fri 14 Jul 2017 11:43:33 PM CEST
brltty-5.5-5.fc26.x86_64  Fri 14 Jul 2017 11:43:31 PM CEST
openssh-7.5p1-3.fc26.x86_64   Fri 14 Jul 2017 11:43:30 PM CEST
evince-libs-3.24.0-3.fc26.x86_64  Fri 14 Jul 2017 11:43:30 PM CEST
openldap-2.4.45-1.fc26.x86_64 Fri 14 Jul 2017 11:43:29 PM CEST
libcrypt-nss-2.25-7.fc26.x86_64   Fri 14 Jul 2017 11:43:29 PM CEST
libreoffice-data-5.3.4.2-3.fc26.noarchFri 14 Jul 2017 11:43:28 PM CEST
glibc-2.25-7.fc26.x86_64  Fri 14 Jul 2017 11:43:26 PM CEST
glibc-all-langpacks-2.25-7.fc26.x86_64Fri 14 Jul 2017 11:43:23 PM CEST
glibc-common-2.25-7.fc26.x86_64   Fri 14 Jul 2017 11:43:20 PM CEST
___
test 

Re: introduction

2017-07-16 Thread Sumantro Mukherjee


- Original Message -
> From: "Rakshana B" 
> To: test@lists.fedoraproject.org
> Sent: Saturday, July 15, 2017 1:34:49 PM
> Subject: introduction
> 
> Hello Everyone,
> 
> I'm Rakshana, computer science student at Kgisl Institute of Technology,
> Coimbatore, India. I have just started with my fedora contribution under the
> guidance of Vipul Siddharth and Prakash Mishra.
> I am looking forward to contribute to Fedora QA.
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 
Hey Rakshana,
First of all, Welcome and thanks for showing your interest in Fedora QA.Please 
create a FAS account and send a QA group 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.


We just had a release but you can still test rawhide. In between the release 
cycle , 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 very soon , stay tuned to this mailing 
list as I will be sending an Poll very soon.
Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: Introduction Mail - Saravanan

2017-07-16 Thread Sumantro Mukherjee


- Original Message -
> From: "c saravanan" 
> To: test@lists.fedoraproject.org
> Sent: Saturday, July 15, 2017 1:30:19 PM
> Subject: Introduction Mail - Saravanan
> 
> Hai, I am Saravanan RIM's student in KGISL IMS Global Academy Coimbatore city
> in TamilNadu, India. Here Prakash mishra and Vipul Siddharth are teaching us
> how to get started with contributing to fedora qa.
> I am looking forward to be a part of fedora community.
> 
> Thanks & Regards
> SARAVANAN.C
> 
>   Virus-free. www.avast.com
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 


Hey Saravanan
First of all, Welcome and thanks for showing your interest in Fedora QA.Please 
create a FAS account and send a QA group 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.


We just had a release but you can still test rawhide. In between the release 
cycle , 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 very soon , stay tuned to this mailing 
list as I will be sending an Poll very soon.
Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: Introduction - Mathumitha

2017-07-16 Thread Sumantro Mukherjee


- Original Message -
> From: "Mathu Mitha" 
> To: test@lists.fedoraproject.org
> Sent: Saturday, July 15, 2017 1:26:26 PM
> Subject: Introduction - Mathumitha
> 
> Hello Everyone,
> 
> I'm Mathumitha an ECE student at KGISL Institute of technology, Coimbatore,
> Tamil nadu, India. I have just started with my fedora contribution under the
> guidance of Vipul Siddharth and Prakash Mishra.
> I am so interested to contribute to Fedora QA and Fedora Community.
> 
> I want to develop myself and so i am here.
> 
> with regards
> Thanking you
> 
> 
> 
> 
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 
Hey Mathumita,

First of all, Welcome and thanks for showing your interest in Fedora QA.Please 
create a FAS account and send a QA group 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.


We just had a release but you can still test rawhide. In between the release 
cycle , 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 very soon , stay tuned to this mailing 
list as I will be sending an Poll very soon.
Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: introduction-Nishajenifer

2017-07-16 Thread Sumantro Mukherjee


- Original Message -
> From: "Nisha Jenifer" 
> To: test@lists.fedoraproject.org
> Sent: Saturday, July 15, 2017 1:26:42 PM
> Subject: introduction-Nishajenifer
> 
> Hi Everyone,
> 
> I'm Nisha jenifer an electronic and communication engineer
> studying 2nd year at KGISL Instituition of
> technology,Coimbatore,Tamilnadu,india
> i have just started with my fedora contribution and Vipul Siddarth and
> Prakash mishra are help[oing me with it.
> I hope to contribute enough to Fedora QA to make an impact. :)
> 
> Cheers
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 
Hey Nisha,

First of all, Welcome and thanks for showing your interest in Fedora QA.Please 
create a FAS account and send a QA group 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.


We just had a release but you can still test rawhide. In between the release 
cycle , 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 very soon , stay tuned to this mailing 
list as I will be sending an Poll very soon.
Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: Introduction

2017-07-16 Thread Sumantro Mukherjee


- Original Message -
> From: "Shankar Dhandapani" 
> To: test@lists.fedoraproject.org
> Sent: Saturday, July 15, 2017 1:25:03 PM
> Subject: Introduction
> 
> Hello Everyone,
> 
> I'm Shankar,Computer Science student in KGiSL Institute of
> Technology,Coimbatore,India.I have just started with my Fedora contribution
> under the guidance of Vipul Siddharth and Prakash Mishra.I am looking
> forward to contribute to fedora QA.
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 

Hey Shankar,

First of all, Welcome and thanks for showing your interest in Fedora QA.Please 
create a FAS account and send a QA group 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.


We just had a release but you can still test rawhide. In between the release 
cycle , 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 very soon , stay tuned to this mailing 
list as I will be sending an Poll very soon.
Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: Introductory mail

2017-07-16 Thread Sumantro Mukherjee


- Original Message -
> From: "Dharsan Kumar" 
> To: test@lists.fedoraproject.org
> Sent: Saturday, July 15, 2017 3:40:37 PM
> Subject: Introductory mail
> 
> 
> 
> Hello Everyone,
> 
> I'm Dharsan.K studying Information Technology at KGiSL Institute of
> Technology,Coimbatore,Tamilnadu,India,Here with Vipul Siddharth and Prakash
> Mishra,Started our first contribution towards Fedora.I'm Excited to
> contribute Fedora QA and also to the Fedora Community.
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 
Hey Darshan,
First of all, Welcome and thanks for showing your interest in Fedora QA.Please 
create a FAS account and send a QA group 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.


We just had a release but you can still test rawhide. In between the release 
cycle , 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 very soon , stay tuned to this mailing 
list as I will be sending an Poll very soon.
Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: Introductory mail

2017-07-16 Thread Sumantro Mukherjee


- Original Message -
> From: "Kishore Raj" 
> To: test@lists.fedoraproject.org
> Sent: Saturday, July 15, 2017 1:34:42 PM
> Subject: Introductory mail
> 
> Hi!!. Am Kishore, from KGiSL Institute of Technology, Coimbatore, Tamil Nadu,
> India. I have just started to contribute fedora under the guindance of Vipul
> Siddharth and Prakash Mishra. I am very much interested in coding.. Recently
> I have did a project based on html,css and also in c,c++,python etc. I am
> very fascinated to contribute towards Fedora QA.
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 

Hey Kishore,

First of all, Welcome and thanks for showing your interest in Fedora QA.Please 
create a FAS account and send a QA group 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.


We just had a release but you can still test rawhide. In between the release 
cycle , 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 very soon , stay tuned to this mailing 
list as I will be sending an Poll very soon.
Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: Introductory mail

2017-07-16 Thread Sumantro Mukherjee


- Original Message -
> From: "barani tharan" 
> To: test@lists.fedoraproject.org
> Sent: Saturday, July 15, 2017 1:31:30 PM
> Subject: Introductory mail
> 
> Hola!!!
> I am Baranitharan pursuing Final year Computer Science Engineering at Kings
> College of Engineering, Tamilnadu, India. I am an active contributor of
> Quality Assurance team in Mozilla Firefox by past 1 year. Vipul and Prakash
> guiding as for contribute to Fedora, so I am very exciting to contribute
> Fedora QA.
> 
> Regards,
> Baranitharan.
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 
Hey Baranitharan,
First of all, Welcome and thanks for showing your interest in Fedora QA.Please 
create a FAS account and send a QA group 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.


We just had a release but you can still test rawhide. In between the release 
cycle , 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 very soon , stay tuned to this mailing 
list as I will be sending an Poll very soon.
Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: Introductory mail

2017-07-16 Thread Sumantro Mukherjee


- Original Message -
> From: "Nagarajan R" 
> To: test@lists.fedoraproject.org
> Sent: Saturday, July 15, 2017 1:31:19 PM
> Subject: Introductory mail
> 
> Hello,
> I am Nagarajan studying in final year cse department in Kings College of
> Engineering, Thanjavur, Tamilnadu,India.
> I am one of the open source contributor for mozilla in the field of
> Localization and Q
> I have just started with my fedora contribution under the guidance of Vipul
> Siddharth and Prakash Mishra.
> I am looking forward to contribute to Fedora QA. I want to take the fedora to
> the next level.
> 
> Thanking you.
> 
> 
> 
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 

Hey Nagarajan,

First of all, Welcome and thanks for showing your interest in Fedora QA.Please 
create a FAS account and send a QA group 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.


We just had a release but you can still test rawhide. In between the release 
cycle , 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 very soon , stay tuned to this mailing 
list as I will be sending an Poll very soon.
Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: Introductory mail

2017-07-16 Thread Sumantro Mukherjee


- Original Message -
> From: "boo pathy" 
> To: test@lists.fedoraproject.org
> Sent: Saturday, July 15, 2017 1:30:01 PM
> Subject: Introductory mail
> 
> hi I am Boopathy,doing my computer science degree in Info Institute of
> Engineering,Coimbatore,Tamilnadu,India.
> I have just started my open source contribution under the guidance of Vipul
> Siddharth and Prakash Mishra
> 
> I am an open source enthusiastic person and like to give more contribution
> towards Linux development.
> I am full stack web developer and interested in embedded system,I am a
> youtuber and Linux evangelist and convince people to work with LInux.
> 
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org


First of all, Welcome and thanks for showing your interest in Fedora QA.Please 
create a FAS account and send a QA group 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.


We just had a release but you can still test rawhide. In between the release 
cycle , 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 very soon , stay tuned to this mailing 
list as I will be sending an Poll very soon.
Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: Introduction about myself

2017-07-16 Thread Sumantro Mukherjee


- Original Message -
> From: "pavithra roselin" 
> To: test@lists.fedoraproject.org
> Sent: Saturday, July 15, 2017 5:34:56 PM
> Subject: Introduction about myself
> 
> Hello all
> I am Pavithra Roselin from coimbatore, Tamilnadu. I am pursuing final year
> B.Tech IT in KGISL institute of Technology. I'm really excited to work with
> Vipul Siddharth and Prakash Mishra in contributing to the Fedora community.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Regards
> 
> Pavithra Roselin
> 
> 
> 
> 
> Email : pavithraroseli...@gmail.com
> 
> contact :+91 8056342852
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 

Hey Pavithra,

First of all, Welcome and thanks for showing your interest in Fedora QA.Please 
create a FAS account and send a QA group 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.


We just had a release but you can still test rawhide. In between the release 
cycle , 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 very soon , stay tuned to this mailing 
list as I will be sending an Poll very soon.
Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: Introducing myself

2017-07-16 Thread Sumantro Mukherjee


- Original Message -
> From: gauravsitl...@riseup.net
> To: test@lists.fedoraproject.org
> Sent: Saturday, July 15, 2017 7:28:23 PM
> Subject: Introducing myself
> 
> Hi everyone,
> My name is Gaurav Sitlani, new here, just getting started with fedora QA
> while reading Sumantro Mukherjee's fedora magazine post.
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 


Hey Gaurav,

First of all, Welcome and thanks for showing your interest in Fedora QA.Please 
create a FAS account and send a QA group 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.


We just had a release but you can still test rawhide. In between the release 
cycle , 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 very soon , stay tuned to this mailing 
list as I will be sending an Poll very soon.
Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org