Fedora 24 updates-testing report

[updates]

The following Fedora 24 Security updates need testing:
 Age  URL
  57  https://bodhi.fedoraproject.org/updates/FEDORA-2016-32eaf0c41e   
redis-3.2.3-1.fc24
  40  https://bodhi.fedoraproject.org/updates/FEDORA-2016-0ef628998f   
chicken-4.11.0-3.fc24
  13  https://bodhi.fedoraproject.org/updates/FEDORA-2016-89060100d7   
mongodb-3.2.8-2.fc24
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2016-a64716084e   
irssi-0.8.20-2.fc24
   6  https://bodhi.fedoraproject.org/updates/FEDORA-2016-7f193a0c59   
php-ZendFramework-1.12.20-1.fc24
   6  https://bodhi.fedoraproject.org/updates/FEDORA-2016-5706eeb875   
python-django-1.9.10-1.fc24
   6  https://bodhi.fedoraproject.org/updates/FEDORA-2016-861b8c46b7   
nodejs-4.6.0-5.fc24
   6  https://bodhi.fedoraproject.org/updates/FEDORA-2016-c23a8ce9e5   
mingw-openjpeg2-2.1.2-1.fc24
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2016-c75bdc394a   
zathura-pdf-mupdf-0.3.0-2.fc24 mujs-0-5.20160921git5c337af.fc24
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-328754be1c   
libdwarf-20160929-1.fc24
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-1cc00cde2d   
c-ares-1.12.0-1.fc24
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-a7f9e86df7   
mingw-c-ares-1.12.0-1.fc24
   1  https://bodhi.fedoraproject.org/updates/FEDORA-2016-e1d4972701   
nsd-4.1.13-1.fc24
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-870236238e   
perl-DBD-MySQL-4.037-1.fc24
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-d61c4f72da   
chromium-53.0.2785.143-1.fc24
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-98768233b8   
python-pillow-3.2.0-2.fc24
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-96045ad97b   
ghostscript-9.16-5.fc24


The following Fedora 24 Critical Path updates have yet to be approved:
 Age URL
   6  https://bodhi.fedoraproject.org/updates/FEDORA-2016-229e5b4143   
lorax-24.21-1.fc24
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2016-2bf9743359   
pungi-4.1.9-2.fc24
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2016-cf7725e102   
koji-1.10.1-13.fc24
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-a300f36043   
perl-Scalar-List-Utils-1.46-1.fc24
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-639b10779f   
hwdata-0.293-1.fc24


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

LuxRender-1.4-1.fc24
ceres-solver-1.11.0-9.fc24
check-mk-1.2.8p11-2.fc24
chromium-53.0.2785.143-1.fc24
cmst-2016.10.03-1.gitf85b216.fc24
corebird-1.3.3-1.fc24
dpm-dsi-1.9.9-1.fc24
eigen3-3.2.10-1.fc24
exodusii-6.02-5.fc24
fail2ban-0.9.5-3.fc24
gajim-0.16.6-1.fc24
gammu-1.37.4-2.fc24
gasnet-1.26.4-5.fc24
ghostscript-9.16-5.fc24
hwdata-0.293-1.fc24
java-1.8.0-openjdk-aarch32-1.8.0.102-6.160812.fc24
libgit2-0.24.2-1.fc24
libreoffice-5.1.5.2-9.fc24
liveusb-creator-3.95.4-1.fc24
mingw-eigen3-3.2.10-1.fc24
mingw-gdk-pixbuf-2.34.0-1.fc24
mingw-opusfile-0.8-1.fc24
octave-parallel-3.1.1-1.fc24
otter-browser-0.9.11-0.2.beta11gitc051a5e.fc24
perl-DBD-MySQL-4.037-1.fc24
perl-Digest-SHA3-0.25-1.fc24
perl-Qt-4.14.3-4.fc24
php-bartlett-php-compatinfo-db-1.13.0-1.fc24
php-phpseclib-2.0.4-1.fc24
php-symfony-2.8.12-2.fc24
php-twig-1.26.0-1.fc24
php-udan11-sql-parser-3.4.10-1.fc24
pjproject-2.4.5-8.fc24
python-backports-functools_lru_cache-1.2.1-1.fc24
python-bitarray-0.8.1-4.fc24
python-blowfish-0.6.1-1.fc24
python-marshmallow-2.10.3-1.fc24
python-pillow-3.2.0-2.fc24
python-statsmodels-0.6.1-7.fc24
python26-2.6.9-2.fc24
sks-1.1.6-1.fc24
wine-1.9.20-1.fc24
xfce4-weather-plugin-0.8.8-2.fc24
zstd-1.1.0-1.fc24

Details about builds:



 LuxRender-1.4-1.fc24 (FEDORA-2016-0a6f58d32e)
 Lux Renderer, an unbiased rendering system

Update Information:

Update to version 1.4




 ceres-solver-1.11.0-9.fc24 (FEDORA-2016-ef6ba542f2)
 A non-linear least squares minimizer

Update Information:

Update to version 3.2.10, see
http://eigen.tuxfamily.org/index.php?title=ChangeLog#Eigen_3.2.10 for details.




 check-mk-1.2.8p11-2.fc24 (FEDORA-2016-d81e722d85)
 A new general purpose Nagios-plugin for retrieving data

Update Information:

Dist tag fix for mod_python to be a require on EL6 only.    New upstream

Fedora 25 updates-testing report

[updates]

The following Fedora 25 Security updates need testing:
 Age  URL
  40  https://bodhi.fedoraproject.org/updates/FEDORA-2016-9b3ed5f170   
chicken-4.11.0-3.fc25
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2016-39de4eb5e7   
irssi-0.8.20-2.fc25
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2016-666d95d1d5   
php-ZendFramework-1.12.20-1.fc25
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2016-704e85cac2   
python-django-1.9.10-1.fc25
   6  https://bodhi.fedoraproject.org/updates/FEDORA-2016-43ff70c6b1   
nodejs-6.7.0-107.fc25
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2016-f8235d2ef9   
mingw-openjpeg2-2.1.2-1.fc25
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2016-8d73759936   
zathura-pdf-mupdf-0.3.0-2.fc25 mujs-0-5.20160921git5c337af.fc25
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2016-4f34f26649   
mingw-c-ares-1.12.0-1.fc25
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2016-f99c0a8b69   
mingw-libidn-1.33-1.fc25
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-9960d370f7   
nsd-4.1.13-1.fc25
   1  https://bodhi.fedoraproject.org/updates/FEDORA-2016-9b8717537a   
libdwarf-20161001-1.fc25
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-9273c6809c   
perl-DBD-MySQL-4.037-1.fc25
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-a90040934d   
chromium-53.0.2785.143-1.fc25
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-e05e6d46df   
ghostscript-9.16-5.fc25


The following Fedora 25 Critical Path updates have yet to be approved:
 Age URL
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2016-b806dfedca   
lorax-25.16-1.fc25
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2016-265c3fca0d   
perl-Scalar-List-Utils-1.46-1.fc25
   4  https://bodhi.fedoraproject.org/updates/FEDORA-2016-a614337c28   
pungi-4.1.9-2.fc25
   1  https://bodhi.fedoraproject.org/updates/FEDORA-2016-84b1e5af31   
libarchive-3.2.1-4.fc25
   1  https://bodhi.fedoraproject.org/updates/FEDORA-2016-27e206277f   
nspr-4.13.0-1.fc25 nss-3.27.0-1.1.fc25 nss-softokn-3.27.0-1.0.fc25 
nss-util-3.27.0-1.0.fc25
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-c067f9aa7a   
hwdata-0.293-1.fc25
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-b596fd5579   
selinux-policy-3.13.1-216.fc25
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-a5c3ebe67a   
libXfont2-2.0.1-2.fc25 tigervnc-1.7.0-2.fc25 xorg-x11-drivers-7.7-18.fc25 
xorg-x11-drv-amdgpu-1.1.2-3.20160929git97d7386c.fc25 
xorg-x11-drv-armsoc-1.4.0-3.20160929.fc25 
xorg-x11-drv-ati-7.7.1-1.20160928git3fc839ff.fc25 
xorg-x11-drv-dummy-0.3.6-26.fc25 xorg-x11-drv-evdev-2.10.4-1.fc25 
xorg-x11-drv-fbdev-0.4.3-25.fc25 xorg-x11-drv-fbturbo-0.5.1-0.8.20150221.fc25 
xorg-x11-drv-freedreno-1.4.0-3.20160929.fc25 xorg-x11-drv-geode-2.11.18-2.fc25 
xorg-x11-drv-intel-2.99.917-26.20160929.fc25 xorg-x11-drv-ivtv-1.2.0-0.22.fc25 
xorg-x11-drv-libinput-0.19.1-2.20160929.fc25 xorg-x11-drv-nouveau-1.0.13-1.fc25 
xorg-x11-drv-omap-0.4.4-3.fc25 xorg-x11-drv-openchrome-0.5.0-2.fc25 
xorg-x11-drv-opentegra-0.7.0-8.fc25 
xorg-x11-drv-qxl-0.1.4-9.20160929gite13d28ee.fc25 
xorg-x11-drv-sisusb-0.9.6-24.fc25 
xorg-x11-drv-synaptics-1.8.99.1-2.20160929git48632211.fc25 
xorg-x11-drv-v4l-0.2.0-47.fc25 xorg-x11-drv-vesa-2.3.2-25.fc25 xorg-x11-drv-vmw
 are-13.0.2-12.20150211git8f0cf7c.fc25 xorg-x11-drv-voodoo-1.2.5-25.fc25 
xorg-x11-drv-wacom-0.33.0-2.20160929gitb61d1711.fc25 
xorg-x11-font-utils-7.5-32.fc25 xorg-x11-proto-devel-7.7-20.fc25 
xorg-x11-server-1.19.0-0.1.20160929.fc25


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

LuxRender-1.4-1.fc25
NetworkManager-fortisslvpn-1.2.4-0.1.fc25
NetworkManager-openvpn-1.2.6-1.fc25
NetworkManager-vpnc-1.2.4-1.fc25
ceres-solver-1.11.0-9.fc25
check-mk-1.2.8p11-2.fc25
chromium-53.0.2785.143-1.fc25
cmake-3.6.2-6.fc25
cmst-2016.10.03-1.gitf85b216.fc25
corebird-1.3.3-1.fc25
dpm-dsi-1.9.9-1.fc25
eigen3-3.2.10-1.fc25
engrid-2.0.0-0.14.gitbaef0ce.fc25
exodusii-6.02-5.fc25
fail2ban-0.9.5-3.fc25
filezilla-3.22.0-1.fc25
gajim-0.16.6-1.fc25
gammu-1.37.4-2.fc25
gasnet-1.26.4-5.fc25
ghostscript-9.16-5.fc25
gnome-shell-extension-openweather-1-0.25.20161004git34d7e39.fc25
gnome-shell-extension-panel-osd-1-0.20.20161004gitc33034a.fc25
hwdata-0.293-1.fc25
java-1.8.0-openjdk-aarch32-1.8.0.102-6.160812.fc25
jsoncpp-1.7.7-1.fc25
language-detector-0.5-2.fc25
libXfont2-2.0.1-2.fc25
libblockdev-1.9-3.fc25
libfilezilla-0.7.1-1.fc25
libgit2-0.24.2-1.fc25
liveusb-creator-3.95.4-1.fc25
mingw-eigen3-3.2.10-1.fc25
mingw-opusfile-0.8-1.fc25
mrpt-1.3.2-9.fc25
octave-optim-1.5.2-1.fc25
octave-parallel-3.1.1-1.fc25
orthanc-1.1.0-2.fc25
otter-browser-0.9.11-0.2.beta11gitc051a5e.fc25
pcl-1.8.0-2.fc25
perl-DBD-MySQL-4.037-1.fc25
perl-Digest-SHA3-0.25-1.fc25
perl-Qt-4.14.3-5.fc25

Fedora Rawhide-20161004.n.1 compose check report

[Fedora compose checker]

Missing expected images:

Kde live i386
Workstation live i386
Kde live x86_64
Cloud_base raw-xz i386
Workstation live x86_64

Failed openQA tests: 53/80 (x86_64), 13/15 (i386)

Old failures (same test failed in Rawhide-20161004.n.0):

ID: 38690   Test: x86_64 Everything-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38690
ID: 38691   Test: x86_64 Everything-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/38691
ID: 38692   Test: i386 Everything-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38692
ID: 38693   Test: x86_64 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38693
ID: 38694   Test: x86_64 Workstation-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/38694
ID: 38695   Test: i386 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38695
ID: 38696   Test: x86_64 Atomic-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38696
ID: 38699   Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38699
ID: 38700   Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/38700
ID: 38701   Test: x86_64 Server-dvd-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/38701
ID: 38702   Test: x86_64 Server-dvd-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/38702
ID: 38709   Test: x86_64 Server-dvd-iso install_repository_nfs_variation
URL: https://openqa.fedoraproject.org/tests/38709
ID: 38710   Test: x86_64 Server-dvd-iso install_repository_nfs_graphical
URL: https://openqa.fedoraproject.org/tests/38710
ID: 38719   Test: x86_64 Server-dvd-iso install_updates_nfs
URL: https://openqa.fedoraproject.org/tests/38719
ID: 38720   Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38720
ID: 38721   Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/38721
ID: 38722   Test: x86_64 universal install_btrfs@uefi
URL: https://openqa.fedoraproject.org/tests/38722
ID: 38723   Test: x86_64 universal install_ext3@uefi
URL: https://openqa.fedoraproject.org/tests/38723
ID: 38724   Test: x86_64 universal install_xfs@uefi
URL: https://openqa.fedoraproject.org/tests/38724
ID: 38725   Test: x86_64 universal install_lvmthin@uefi
URL: https://openqa.fedoraproject.org/tests/38725
ID: 38726   Test: x86_64 universal install_no_swap@uefi
URL: https://openqa.fedoraproject.org/tests/38726
ID: 38727   Test: x86_64 universal install_kickstart_hdd
URL: https://openqa.fedoraproject.org/tests/38727
ID: 38738   Test: x86_64 universal install_updates_img_local
URL: https://openqa.fedoraproject.org/tests/38738
ID: 38739   Test: x86_64 universal install_shrink_ext4
URL: https://openqa.fedoraproject.org/tests/38739
ID: 38740   Test: x86_64 universal install_shrink_ntfs
URL: https://openqa.fedoraproject.org/tests/38740
ID: 38741   Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/38741
ID: 38742   Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/38742
ID: 38743   Test: x86_64 universal install_kickstart_firewall_disabled
URL: https://openqa.fedoraproject.org/tests/38743
ID: 38744   Test: x86_64 universal install_kickstart_firewall_configured
URL: https://openqa.fedoraproject.org/tests/38744
ID: 38745   Test: x86_64 universal install_package_set_minimal
URL: https://openqa.fedoraproject.org/tests/38745
ID: 38746   Test: x86_64 universal install_anaconda_text
URL: https://openqa.fedoraproject.org/tests/38746
ID: 38748   Test: x86_64 universal install_repository_http_variation
URL: https://openqa.fedoraproject.org/tests/38748
ID: 38749   Test: x86_64 universal install_repository_http_graphical
URL: https://openqa.fedoraproject.org/tests/38749
ID: 38750   Test: x86_64 universal install_mirrorlist_graphical
URL: https://openqa.fedoraproject.org/tests/38750
ID: 38751   Test: x86_64 universal install_delete_pata
URL: https://openqa.fedoraproject.org/tests/38751
ID: 38752   Test: x86_64 universal install_delete_pata@uefi
URL: https://openqa.fedoraproject.org/tests/38752
ID: 38753   Test: x86_64 universal install_kickstart_user_creation
URL: https://openqa.fedoraproject.org/tests/38753
ID: 38754   Test: x86_64 universal install_scsi_updates_img
URL: https://openqa.fedoraproject.org/tests/38754
ID: 38755   Test: x86_64 universal install_multi
URL: https://openqa.fedoraproject.org/tests/38755
ID: 38756   Test: x86_64 universal install_multi@uefi
URL: https://openqa.fedoraproject.org/tests/38756
ID: 38757   Test: x86_64 universal install_simple_encrypted
URL: https://openqa.fedoraproject.org/tests/38757
ID: 38758   Test: x86_64 universal install_simple_free_space

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

[Adam Williamson]

On Tue, 2016-10-04 at 23:08 +0100, Patrick O'Callaghan wrote:
> 
> You say:
> 
> If your system has more than one graphics adapter, and you update
> the systemd-udev package while X is running, X will crash. 
> 
> I presume you mean that more than one adaptor is connected to a
> respective monitor. Just having the adaptor presumably shouldn't do
> anything in itself. This is the case with practically all mobos with an
> additional video card. Or have I misunderstood?

We're not 100% sure yet. I'll update my blog post to say 'may well' or
something like that. So far, we have multiple reports of affected
hybrid laptops - those are the ones with both an Intel adapter and an
NVIDIA or AMD adapter, not intended to drive multiple screens but
rather intended to use the Intel adapter when just sitting at a desktop
but the dedicated adapter when running a game, that sort of thing.

We have one report of a system with two 'regular' adapters, both
connected to monitors, being affected.

We have two reports of hybrid laptops *not* being affected.

And we have - so far as I can tell - no reports of a system with just
one video adapter being affected.

So we can't say absolutely all multi-adapter cases are affected, but so
far it seems to be the case that *only* multi-adapter cases are
affected, and given the reports so far, at least a fair percentage of
all multi-adapter cases are affected.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

[Patrick O'Callaghan]

On Tue, 2016-10-04 at 14:44 -0700, Adam Williamson wrote:
> On Tue, 2016-10-04 at 14:04 -0700, Adam Williamson wrote:
> > 
> > 
> > I'm gonna write up a blog post and spread the word about this a bit,
> > I'll send the link shortly; if people could spread it around that'd be
> > great.
> 
> Blog post:
> 
> https://www.happyassassin.net/2016/10/04/x-crash-during-fedora-update-when-system-has-hybrid-graphics-and-systemd-udev-is-in-update/
> 
> If folks can spread that around, it'd be great. Please let me know of
> any errors or inaccuracies you spot.

You say:

If your system has more than one graphics adapter, and you update
the systemd-udev package while X is running, X will crash. 

I presume you mean that more than one adaptor is connected to a
respective monitor. Just having the adaptor presumably shouldn't do
anything in itself. This is the case with practically all mobos with an
additional video card. Or have I misunderstood?

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

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

[Adam Williamson]

On Tue, 2016-10-04 at 14:04 -0700, Adam Williamson wrote:
> 
> I'm gonna write up a blog post and spread the word about this a bit,
> I'll send the link shortly; if people could spread it around that'd be
> great.

Blog post:

https://www.happyassassin.net/2016/10/04/x-crash-during-fedora-update-when-system-has-hybrid-graphics-and-systemd-udev-is-in-update/

If folks can spread that around, it'd be great. Please let me know of
any errors or inaccuracies you spot.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

[Adam Williamson]

On Tue, 2016-10-04 at 22:15 +0100, Tom Hughes wrote:
> On 04/10/16 22:04, Adam Williamson wrote:
> 
> > We've pretty much pinned it down, now. The recipe is: hybrid graphics +
> > systemd-udev update == X crash. That is, if there's a systemd-udev
> > update in the dnf transaction, and the system has hybrid graphics, and
> > X is running while the update runs, X will crash. If you're running the
> > update in a VT, X will crash but the update will complete OK. If you
> > run the update inside X, the update process will die when X crashes and
> > your system will be left messed up.
> 
> 
> My machine at work where this happens isn't hybrid. It has three 
> monitors spread over two Nvidia cards though, driven by nouveau rather 
> than the proprietary drivers.

OK, so probably strictly speaking this is triggered by having multiple
adapters. 'Hybrid graphics' is by far the most common case of that
these days, though. Thanks for the note, I'll revise my blog post (that
I'm writing ATM).
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Self-introduction: Jacob GODYN

[Jacob GODYN]

Hi,
Here my first activity, the testcase Mediakit Size ISO :)

https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20160930.n.0_Installation#Image_sanity

https://qa.fedoraproject.org/blockerbugs/milestone/25/beta/buglist

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

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

[Adam Williamson]

On Tue, 2016-10-04 at 21:54 +0100, Tom Hughes wrote:
> 
> It only ever happens on one of my machines, so it's obviously something 
> about the environment, possibly the graphics card as that's the only 
> machine I do this on that has nvidia graphics?
> 
> The weird thing is that there was nothing particularly X related in the 
> update that caused it this morning. In fact systemd was probably about 
> the most low level thing that was in the update.

We've pretty much pinned it down, now. The recipe is: hybrid graphics +
systemd-udev update == X crash. That is, if there's a systemd-udev
update in the dnf transaction, and the system has hybrid graphics, and
X is running while the update runs, X will crash. If you're running the
update in a VT, X will crash but the update will complete OK. If you
run the update inside X, the update process will die when X crashes and
your system will be left messed up.

I'm gonna write up a blog post and spread the word about this a bit,
I'll send the link shortly; if people could spread it around that'd be
great.

The bug reports are
https://bugzilla.redhat.com/show_bug.cgi?id=1341327 (for the X side)
and
https://bugzilla.redhat.com/show_bug.cgi?id=1378974 (for the systemd
side). We are going to try and ensure the bug doesn't affect F25 Beta
installs. An update is pending for F24, but ironically (since the
service restart is in %postun not %post), the transaction to apply the
update will *suffer from* the problem; the update will only ensure that
*subsequent* updates no longer trigger the problem.

Thanks for the data everyone!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Fedora Rawhide-20161004.n.0 compose check report

[Fedora compose checker]

Missing expected images:

Kde live i386
Workstation live i386
Kde live x86_64
Cloud_base raw-xz i386
Workstation live x86_64

Failed openQA tests: 57/80 (x86_64), 14/15 (i386)

New failures (same test did not fail in Rawhide-20161003.n.1):

ID: 38504   Test: x86_64 universal upgrade_desktop_encrypted_64bit
URL: https://openqa.fedoraproject.org/tests/38504
ID: 38518   Test: x86_64 universal install_anaconda_text
URL: https://openqa.fedoraproject.org/tests/38518

Old failures (same test failed in Rawhide-20161003.n.1):

ID: 38462   Test: x86_64 Everything-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38462
ID: 38463   Test: x86_64 Everything-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/38463
ID: 38464   Test: i386 Everything-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38464
ID: 38465   Test: x86_64 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38465
ID: 38466   Test: x86_64 Workstation-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/38466
ID: 38467   Test: i386 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38467
ID: 38468   Test: x86_64 Atomic-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38468
ID: 38471   Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38471
ID: 38472   Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/38472
ID: 38473   Test: x86_64 Server-dvd-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/38473
ID: 38474   Test: x86_64 Server-dvd-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/38474
ID: 38481   Test: x86_64 Server-dvd-iso install_repository_nfs_variation
URL: https://openqa.fedoraproject.org/tests/38481
ID: 38482   Test: x86_64 Server-dvd-iso install_repository_nfs_graphical
URL: https://openqa.fedoraproject.org/tests/38482
ID: 38491   Test: x86_64 Server-dvd-iso install_updates_nfs
URL: https://openqa.fedoraproject.org/tests/38491
ID: 38492   Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38492
ID: 38493   Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/38493
ID: 38494   Test: x86_64 universal install_btrfs@uefi
URL: https://openqa.fedoraproject.org/tests/38494
ID: 38495   Test: x86_64 universal install_ext3@uefi
URL: https://openqa.fedoraproject.org/tests/38495
ID: 38496   Test: x86_64 universal install_xfs@uefi
URL: https://openqa.fedoraproject.org/tests/38496
ID: 38497   Test: x86_64 universal install_lvmthin@uefi
URL: https://openqa.fedoraproject.org/tests/38497
ID: 38498   Test: x86_64 universal install_no_swap@uefi
URL: https://openqa.fedoraproject.org/tests/38498
ID: 38499   Test: x86_64 universal install_kickstart_hdd
URL: https://openqa.fedoraproject.org/tests/38499
ID: 38503   Test: x86_64 universal upgrade_kde_64bit
URL: https://openqa.fedoraproject.org/tests/38503
ID: 38508   Test: x86_64 universal upgrade_2_kde_64bit
URL: https://openqa.fedoraproject.org/tests/38508
ID: 38510   Test: x86_64 universal install_updates_img_local
URL: https://openqa.fedoraproject.org/tests/38510
ID: 38511   Test: x86_64 universal install_shrink_ext4
URL: https://openqa.fedoraproject.org/tests/38511
ID: 38512   Test: x86_64 universal install_shrink_ntfs
URL: https://openqa.fedoraproject.org/tests/38512
ID: 38513   Test: x86_64 universal install_european_language
URL: https://openqa.fedoraproject.org/tests/38513
ID: 38514   Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/38514
ID: 38515   Test: x86_64 universal install_kickstart_firewall_disabled
URL: https://openqa.fedoraproject.org/tests/38515
ID: 38516   Test: x86_64 universal install_kickstart_firewall_configured
URL: https://openqa.fedoraproject.org/tests/38516
ID: 38517   Test: x86_64 universal install_package_set_minimal
URL: https://openqa.fedoraproject.org/tests/38517
ID: 38520   Test: x86_64 universal install_repository_http_variation
URL: https://openqa.fedoraproject.org/tests/38520
ID: 38521   Test: x86_64 universal install_repository_http_graphical
URL: https://openqa.fedoraproject.org/tests/38521
ID: 38522   Test: x86_64 universal install_mirrorlist_graphical
URL: https://openqa.fedoraproject.org/tests/38522
ID: 38523   Test: x86_64 universal install_delete_pata
URL: https://openqa.fedoraproject.org/tests/38523
ID: 38524   Test: x86_64 universal install_delete_pata@uefi
URL: https://openqa.fedoraproject.org/tests/38524
ID: 38525   Test: x86_64 universal install_kickstart_user_creation
URL: https://openqa.fedoraproject.org/tests/38525
ID: 38526   Test: x86_64 universal install_scsi_updates_img
URL: 

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

[Ralf Corsepius]

On 10/04/2016 05:51 PM, Adam Williamson wrote:

Recently several reports of people getting 'duplicated packages' and
'kernel updates not working' have come through to us in QA from Fedora
24 users. I managed to get one reporter to explain more specifically
what happened, and it sounds a lot like what's happening is that
something in the 'dnf update' process can cause a GNOME or X crash,
possibly depending on hardware or package set installed. When that
happens, the update process is killed and does not complete cleanly,
which is why you get 'duplicated packages' and other odd results.

I'm working with the reporter right now to investigate and hopefully
get this fixed, but in the meantime - and this is in fact our standard
advice anyway, but it bears repeating - DON'T RUN 'dnf update' INSIDE A
DESKTOP.


FWIW: Since ca. f22/f23 I've repeatedly seen "dnf update" running in 
xfce4-terminals in Xfce4 desktops killing X or something underneath of 
X, leaving duplicate packages in rpmdb.


So far, I've been suspecting some systemd services is killing something 
related to networking or X, but I never managed to isolate the cause.


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

Re: ... and Fedora 25! - Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

[Adam Williamson]

On Tue, 2016-10-04 at 18:28 +0200, Karel Volný wrote:
> > Recently several reports of people getting 'duplicated packages' and
> > 'kernel updates not working' have come through to us in QA from Fedora
> > 24 users. I managed to get one reporter to explain more specifically
> > what happened, and it sounds a lot like what's happening is that
> > something in the 'dnf update' process can cause a GNOME or X crash,
> 
> 
> LXQT in my case, so more X than GNOME crash
> 
> is there a bug I can subscribe to?

Seems the bug is: https://bugzilla.redhat.com/show_bug.cgi?id=1341327
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

[Chris Murphy]

On Tue, Oct 4, 2016 at 9:56 AM, Patrick O'Callaghan
 wrote:
>
> On 4 October 2016 at 16:51, Adam Williamson 
> wrote:
>>
>> Running the update process inside a desktop just gives it all the more
>> opportunity to crash somehow. If the terminal app crashes, the update
>> crashes. If the desktop crashes, the update crashes.
>>
>> I don't want to get in the KDE folks' bad graces, but this likely could
>> also affect KDE's graphical update system, so I'd advise against using
>> that for the present too.
>
>
> Maybe I've just been lucky but I run dnf on a daily basis in a Konsole
> terminal window (under KDE) and have never seen this kind of problem. I
> don't use the graphical updater(s).

I do it also but I also take a snapshot of root first, and then I
expect without warning that the GUI could just vanish and munge a
bunch of things. It's a use case I expect to not work, even though it
Works For Me™.

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

Re: ... and Fedora 25! - Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

[Adam Williamson]

On Tue, 2016-10-04 at 18:28 +0200, Karel Volný wrote:
> > Recently several reports of people getting 'duplicated packages' and
> > 'kernel updates not working' have come through to us in QA from Fedora
> > 24 users. I managed to get one reporter to explain more specifically
> > what happened, and it sounds a lot like what's happening is that
> > something in the 'dnf update' process can cause a GNOME or X crash,
> 
> 
> LXQT in my case, so more X than GNOME crash
> 
> is there a bug I can subscribe to?

Not yet (AFAIK), I'm trying to walk the reporter who's currently in
#fedora-qa through filing one. abrt is showing an X crash for him,
indeed. If you have hit this and you still have the system live, you
should be able to find the X crash in abrt and report it.

> > Otherwise, at least run 'dnf update' in a VT -
> > hit ctrl-alt-f3 to get a VT console login prompt, log in, and do it
> > there. Don't do it inside your desktop.
> 
> 
> or better (IMHO) - run it using `screen` ;-)

I think whether that's better or not depends on exactly how the
screen/tmux server process was run...
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

... and Fedora 25! - Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

[Karel Volný]

Recently several reports of people getting 'duplicated packages' and
'kernel updates not working' have come through to us in QA from Fedora
24 users. I managed to get one reporter to explain more specifically
what happened, and it sounds a lot like what's happening is that
something in the 'dnf update' process can cause a GNOME or X crash,


LXQT in my case, so more X than GNOME crash

is there a bug I can subscribe to?


Otherwise, at least run 'dnf update' in a VT -
hit ctrl-alt-f3 to get a VT console login prompt, log in, and do it
there. Don't do it inside your desktop.


or better (IMHO) - run it using `screen` ;-)

K.

--
Karel Volný
BaseOS QE - Daemons
Red Hat Czech, Brno
tel. +420 532294274
(RH: +420 532294111 ext. 8262074)
:: "Never attribute to malice what can
::  easily be explained by stupidity."
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

[Adam Williamson]

On Tue, 2016-10-04 at 16:56 +0100, Patrick O'Callaghan wrote:
> On 4 October 2016 at 16:51, Adam Williamson 
> wrote:
> 
> > Running the update process inside a desktop just gives it all the more
> > opportunity to crash somehow. If the terminal app crashes, the update
> > crashes. If the desktop crashes, the update crashes.
> > 
> > I don't want to get in the KDE folks' bad graces, but this likely could
> > also affect KDE's graphical update system, so I'd advise against using
> > that for the present too.
> > 
> 
> 
> Maybe I've just been lucky but I run dnf on a daily basis in a Konsole
> terminal window (under KDE) and have never seen this kind of problem. I
> don't use the graphical updater(s).

Well, as I said it may be package set or hardware dependent, or just a
case of luck. There've been I think at least five or six reports so far
that I've heard of one way or another, which seemed like enough to send
out a mail shot.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

[Patrick O'Callaghan]

On 4 October 2016 at 16:51, Adam Williamson 
wrote:

> Running the update process inside a desktop just gives it all the more
> opportunity to crash somehow. If the terminal app crashes, the update
> crashes. If the desktop crashes, the update crashes.
>
> I don't want to get in the KDE folks' bad graces, but this likely could
> also affect KDE's graphical update system, so I'd advise against using
> that for the present too.
>

Maybe I've just been lucky but I run dnf on a daily basis in a Konsole
terminal window (under KDE) and have never seen this kind of problem. I
don't use the graphical updater(s).

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

Fedora 25-20161004.n.0 compose check report

[Fedora compose checker]

Missing expected images:

Cloud_base raw-xz i386

Failed openQA tests: 5/102 (x86_64), 1/17 (i386), 1/2 (arm)

New failures (same test did not fail in 25-20161003.n.0):

ID: 38574   Test: x86_64 Workstation-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/38574
ID: 38590   Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/38590

Old failures (same test failed in 25-20161003.n.0):

ID: 38571   Test: x86_64 Workstation-live-iso desktop_notifications_live
URL: https://openqa.fedoraproject.org/tests/38571
ID: 38572   Test: x86_64 Workstation-live-iso 
desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/38572
ID: 38577   Test: x86_64 Atomic-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/38577
ID: 38678   Test: i386 universal upgrade_2_desktop_32bit
URL: https://openqa.fedoraproject.org/tests/38678
ID: 38682   Test: x86_64 universal install_iscsi
URL: https://openqa.fedoraproject.org/tests/38682

Passed openQA tests: 97/102 (x86_64), 16/17 (i386)

New passes (same test did not pass in 25-20161003.n.0):

ID: 38639   Test: x86_64 universal install_anaconda_text
URL: https://openqa.fedoraproject.org/tests/38639

Skipped openQA tests: 1 of 121
-- 
Mail generated by check-compose:
https://git.fedorahosted.org/cgit/fedora-qa.git/tree/check-compose
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

[Adam Williamson]

Recently several reports of people getting 'duplicated packages' and
'kernel updates not working' have come through to us in QA from Fedora
24 users. I managed to get one reporter to explain more specifically
what happened, and it sounds a lot like what's happening is that
something in the 'dnf update' process can cause a GNOME or X crash,
possibly depending on hardware or package set installed. When that
happens, the update process is killed and does not complete cleanly,
which is why you get 'duplicated packages' and other odd results.

I'm working with the reporter right now to investigate and hopefully
get this fixed, but in the meantime - and this is in fact our standard
advice anyway, but it bears repeating - DON'T RUN 'dnf update' INSIDE A
DESKTOP.

Running the update process inside a desktop just gives it all the more
opportunity to crash somehow. If the terminal app crashes, the update
crashes. If the desktop crashes, the update crashes.

I don't want to get in the KDE folks' bad graces, but this likely could
also affect KDE's graphical update system, so I'd advise against using
that for the present too.

If you're using Workstation, the offline update system is expressly
designed to minimize the likelihood of this kind of problem, so please
do consider using it. Otherwise, at least run 'dnf update' in a VT -
hit ctrl-alt-f3 to get a VT console login prompt, log in, and do it
there. Don't do it inside your desktop.

Thanks folks!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: USB writing changes: wiki instructions, tests

[Kamil Paral]

> I don't quite see why you claim that Workstation live is the only case
> where we should test optical media any more. Why is Workstation live
> special? Why not the KDE live? Why not the Server DVD? I just don't get
> the grounds for the distinction.

I was thinking about real world scenarios, and Workstation Live is the only one 
that is probably going to be given away on optical discs (at conferences, 
university events, etc). KDE Live would probably also fit in this. I don't 
think we're ever giving out Server discs, or Cloud (ha ha).

As for personal downloads, again Workstation Live is the most commonly 
downloaded image for standard users, so if the machine can't boot from USB, 
this is likely the image that is going to get burned to a DVD. I don't think 
people install servers from optical media too much, but I might be wrong. But 
for Server, sysadmins are probably able to leverage a different method of 
installation anyway (pxeboot).

Ideally we should of course test all combinations. But that's not practical. So 
this was all about covering the most commonly used methods.

> 
> It sucks, but I'd say in an ideal world we would actually be testing
> all supported boot methods - VM 'optical disc', real optical disc, each
> supported USB write method - for each image, for both x86_64 and UEFI.
> Given that we have six release-blocking ISO images, if we only tested
> one USB write method, that'd be 36 tests. Fun for all the family! Add
> another 12 for each support USB write method we decide to test
> independently...

Right. We clearly need to pick a "reasonable subset".
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Fedora 23 updates-testing report

[updates]

The following Fedora 23 Security updates need testing:
 Age  URL
 379  https://bodhi.fedoraproject.org/updates/FEDORA-2015-16240   
nagios-4.0.8-1.fc23
 337  https://bodhi.fedoraproject.org/updates/FEDORA-2015-81ded368fe   
miniupnpc-1.9-6.fc23
 310  https://bodhi.fedoraproject.org/updates/FEDORA-2015-27392b3324   
jbig2dec-0.12-2.fc23
 261  https://bodhi.fedoraproject.org/updates/FEDORA-2015-dd52a54fa1   
python-pymongo-3.0.3-1.fc23
 260  https://bodhi.fedoraproject.org/updates/FEDORA-2015-06a7c972e8   
thttpd-2.25b-37.fc23
 225  https://bodhi.fedoraproject.org/updates/FEDORA-2016-637618fcd4   
mingw-nsis-2.50-1.fc23
 101  https://bodhi.fedoraproject.org/updates/FEDORA-2016-fcccb0a547   
nodejs-0.10.46-1.fc23
  79  https://bodhi.fedoraproject.org/updates/FEDORA-2016-70b5173c05   
ecryptfs-utils-111-1.fc23
  67  https://bodhi.fedoraproject.org/updates/FEDORA-2016-8d79ade826   
flex-2.6.0-2.fc23
  56  https://bodhi.fedoraproject.org/updates/FEDORA-2016-c2ec9c716e   
redis-3.2.3-1.fc23
  49  https://bodhi.fedoraproject.org/updates/FEDORA-2016-d6288f555c   
libarchive-3.2.1-3.fc23 python-libarchive-c-2.5-1.fc23
  47  https://bodhi.fedoraproject.org/updates/FEDORA-2016-47dc2b203f   
firewalld-0.4.3.3-1.fc23
  33  https://bodhi.fedoraproject.org/updates/FEDORA-2016-b3a6435b14   
dhcpcd-6.11.3-1.fc23
  24  https://bodhi.fedoraproject.org/updates/FEDORA-2016-ed1c402851   
thunderbird-45.3.0-1.fc23
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2016-97454404fe   
openssl-1.0.2j-1.fc23
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2016-0551065fe0   
irssi-0.8.20-2.fc23
   6  https://bodhi.fedoraproject.org/updates/FEDORA-2016-77e5105570   
php-ZendFramework-1.12.20-1.fc23
   6  https://bodhi.fedoraproject.org/updates/FEDORA-2016-3795497354   
python-django-1.8.15-1.fc23
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2016-ad1871cf02   
openjpeg2-2.1.2-1.fc23
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2016-fe55f449e0   
mingw-openjpeg2-2.1.2-1.fc23
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-3af8b344f1   
bind-9.10.4-2.P3.fc23
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-cbef6c8619   
bind99-9.9.9-2.P3.fc23
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-1b9d24c2b6   
zathura-pdf-mupdf-0.3.0-2.fc23 mujs-0-5.20160921git5c337af.fc23
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-7aa3c89e7b   
c-ares-1.12.0-1.fc23
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-66d9389548   
mingw-c-ares-1.12.0-1.fc23
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-f15168439d   
bash-4.3.42-5.fc23
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-bb007a4097   
openssh-7.2p2-6.fc23
   1  https://bodhi.fedoraproject.org/updates/FEDORA-2016-8e4e733bef   
systemd-222-17.fc23
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-c0f589bd32   
perl-DBD-MySQL-4.033-3.fc23
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-2e50862950   
chromium-53.0.2785.143-1.fc23
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-e99bb57db9   
python-pillow-3.0.0-5.fc23
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-94bdf707d4   
ghostscript-9.16-5.fc23


The following Fedora 23 Critical Path updates have yet to be approved:
 Age URL
  76  https://bodhi.fedoraproject.org/updates/FEDORA-2016-98a7a1b6e0   
abrt-2.8.0-6.fc23 libreport-2.6.4-3.fc23
  49  https://bodhi.fedoraproject.org/updates/FEDORA-2016-d6288f555c   
libarchive-3.2.1-3.fc23 python-libarchive-c-2.5-1.fc23
  24  https://bodhi.fedoraproject.org/updates/FEDORA-2016-ed1c402851   
thunderbird-45.3.0-1.fc23
  10  https://bodhi.fedoraproject.org/updates/FEDORA-2016-79072fd70e   
python-virtkey-0.63.0-1.fc23
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2016-ab35400bb1   
poppler-0.34.0-4.fc23
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2016-7aef55393a   
polkit-qt-0.112.0-8.fc23
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2016-97454404fe   
openssl-1.0.2j-1.fc23
   7  https://bodhi.fedoraproject.org/updates/FEDORA-2016-6a3e81a5be   
linux-firmware-20160923-68.git42ad5367.fc23
   5  https://bodhi.fedoraproject.org/updates/FEDORA-2016-cf2b06f96f   
libass-0.13.3-1.fc23
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-bb007a4097   
openssh-7.2p2-6.fc23
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-f15168439d   
bash-4.3.42-5.fc23
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-9d283ed227   
python-2.7.11-11.fc23
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-3af8b344f1   
bind-9.10.4-2.P3.fc23
   3  https://bodhi.fedoraproject.org/updates/FEDORA-2016-d26923757a   
koji-1.10.1-13.fc23
   1  https://bodhi.fedoraproject.org/updates/FEDORA-2016-8e4e733bef   
systemd-222-17.fc23
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-fdf15e65fd   
hwdata-0.293-1.fc23
   0  https://bodhi.fedoraproject.org/updates/FEDORA-2016-c0f589bd32   
perl-DBD-MySQL-4.033-3.fc23
   0  

Re: Self-introduction: Jacob GODYN

[Sumantro Mukherjee]

- Original Message -
> From: "Jacob GODYN" 
> To: test@lists.fedoraproject.org
> Sent: Tuesday, October 4, 2016 5:41:38 PM
> Subject: Re: Self-introduction: Jacob GODYN
> 
> Hi  Sumantro Mukherjee,
> 
> Thank you for the links, I'll read the documentation carefully. I would come
> back to you if I have questions.
> 
> Thanks.
> Jacob


Hii

Sure thing!

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

Re: Self-introduction: Jacob GODYN

[Jacob GODYN]

Hi  Sumantro Mukherjee,

Thank you for the links, I'll read the documentation carefully. I would come 
back to you if I have questions.

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

Re: Self-introduction: Jacob GODYN

[Sumantro Mukherjee]

- Original Message -
> From: "Jacob Godyn" 
> To: test@lists.fedoraproject.org
> Sent: Tuesday, October 4, 2016 1:00:24 AM
> Subject: Self-introduction: Jacob GODYN
> 
> Hello,
> 
> My name is Jacob GODYN, I'm 35 years old and live in France. I'm system and
> storage administrator, I discovered Linux in 2001, now it's time for me to
> contribute, I hope to help.
> 
> So, thanks a lot for some people who accepted me at Fedora Project.
> 
> Bye

Hey Jacob GODYN,

First of all , welcome to fedora qa team. I have sponsored you :)

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 branched, you can run test cases which are mentioned [1] 
and submit your results in the test matrix.

Note that each of the test cases[2] 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 [3] 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

You can also do update-testing, 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 [4]. You can also, use fedora-easy-karma for giving out feedbacks.

[1]https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20160930.n.0_Installation?rd=Test_Results:Current_Installation_Test
[2]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[3]https://bugzilla.redhat.com/
[4]https://fedoraproject.org/wiki/QA:Updates_Testing


We also have Fedora QA onboarding call. The session is primarily targeted to 
people who are enthusiastic and interested to learn and contribute in Fedora 
QA. These are open onboarding session, which means there is literally no 
knowledge required as pre-requisit. We are having the poll open for votes for 
the best possible timings at 
https://public.etherpad-mozilla.org/p/Fedoraqaonboardingoct . Make sure you 
vote your preferred timings. Note that all the timings are in UTC so convert 
them to local time before you vote in.
 
Should you have any question, you reach out to me directly or in the list!


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

[security fix] ghostscript ready for testing

[David Kaspar]

Hello guys,

I have just created bodhi updates for ghoscript, to fix its security issue 
(impact = moderate, CVE has not been assigned yet). More info in Bugzilla:  
https://bugzilla.redhat.com/show_bug.cgi?id=1380415

If you would like, you can test the updates and the fix by yourself. The steps 
for it are described in bodhi release notes. [1][2][3] The fix is included in 
Rawhide as well.

NOTE: In order to deliver the security fix, the OpenJPEG support had to be 
temporarily disabled. I will work on delivering the OpenJPEG support back as 
soon as possible.

Best regards,

Dee'Kej

[1] https://bodhi.fedoraproject.org/updates/ghostscript-9.16-5.fc25
[2] https://bodhi.fedoraproject.org/updates/ghostscript-9.16-5.fc24
[3] https://bodhi.fedoraproject.org/updates/ghostscript-9.16-5.fc23
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Self-introduction: Dexter Haslem

[Sumantro Mukherjee]

- Original Message -
> From: "Dexter Haslem" 
> To: test@lists.fedoraproject.org
> Sent: Tuesday, October 4, 2016 9:47:56 AM
> Subject: Self-introduction: Dexter Haslem
> 
> Hi all,
> 
> I'm interested in helping out with QA efforts, I'm looking to bang on
> pre-releases and rawhide as well as QA docs. I also like to test
> things on ARM and MIPS when possible. I've been using linux in some
> capacity since around 2004 and fedora is my favorite distro, I use
> both desktop and server releases currently. You can find me on IRC as
> 'dmh', I've created a FAS and sent a request to the group. I'm in MST
> timezone (UTC-7) and available most evenings.
> 

Hey Dexter Haslem,

First of all , welcome to fedora qa team. I have sponsored you

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 branched, you can run test cases which are mentioned [1] 
and submit your results in the test matrix.

Note that each of the test cases[2] 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 [3] 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

You can also do update-testing, 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 [4]. You can also, use fedora-easy-karma for giving out feedbacks.

[1]https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20160930.n.0_Installation?rd=Test_Results:Current_Installation_Test
[2]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[3]https://bugzilla.redhat.com/
[4]https://fedoraproject.org/wiki/QA:Updates_Testing


We also have Fedora QA onboarding call. The session is primarily targeted to 
people who are enthusiastic and interested to learn and contribute in Fedora 
QA. These are open onboarding session, which means there is literally no 
knowledge required as pre-requisit. We are having the poll open for votes for 
the best possible timings at 
https://public.etherpad-mozilla.org/p/Fedoraqaonboardingoct . Make sure you 
vote your preferred timings. Note that all the timings are in UTC so convert 
them to local time before you vote in.
 
Should you have any question, you reach out to me directly or in the list!


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

Re: USB writing changes: wiki instructions, tests

[Adam Williamson]

On Tue, 2016-10-04 at 04:30 -0400, Kamil Paral wrote:

> Alternatively, we could somehow connect this to the "Default boot and
> install" section, which is very much related, and we'll need to
> rethink it anyway (because currently it says "bare metal required"
> and we fill it with openqa...). Maybe we could have "Workstation live
> optical" (which is probably the only case where it still makes sense
> to test optical media) and the rest would be considered either USB or
> VM. Also, Live and DVD USB would be already present in
> QA:Testcase_USB_dd-like_install row.

This is basically the alley I was chasing down this morning in the
shower, but more important stuff took over.

I don't quite see why you claim that Workstation live is the only case
where we should test optical media any more. Why is Workstation live
special? Why not the KDE live? Why not the Server DVD? I just don't get
the grounds for the distinction.

It sucks, but I'd say in an ideal world we would actually be testing
all supported boot methods - VM 'optical disc', real optical disc, each
supported USB write method - for each image, for both x86_64 and UEFI.
Given that we have six release-blocking ISO images, if we only tested
one USB write method, that'd be 36 tests. Fun for all the family! Add
another 12 for each support USB write method we decide to test
independently...

We could do this either as three tables, or as one table with six
result columns. Not really sure which is best.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: F25, how to reclaim space - manually partitioning

[Joerg Lechner]

Hi Chris,
manual partitioning with reclaim space I could do -according to Your help. The 
installation result on an USB connected medium (in this case USB 3.0 flash 
medium) is the same as with automatic partitioning and reclaim space, and also 
when I "clean" the USB flash medium with media writer and following gparted and 
try installation without reclaiming space->   installation does not work on usb 
connected media - dracut error report is always the same.
Kind regards 

 

 

 

-Ursprüngliche Mitteilung- 
Von: Chris Murphy 
An: For testing and quality assurance of Fedora releases 

Verschickt: Mo, 3 Okt 2016 10:28 pm
Betreff: Re: F25, how to reclaim space - manually partitioning

On Mon, Oct 3, 2016 at 6:51 AM, Joerg Lechner  wrote:> Hi,> 
problems in reclaiming space in manual partitioning for F25 Alpha> Workstation 
installation.> Does anyone know, how to do this? If error and so far not 
solved,> worthwhile to file a bug?Click on Fedora Linux 25... and it will 
reveal the mount points forthat installation. Click one and then click the '-' 
button to deleteit.-- Chris 
Murphy___test mailing list -- 
test@lists.fedoraproject.orgTo 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: USB writing changes: wiki instructions, tests

[Kamil Paral]

> Hey folks! Wanted to send a heads-up that I've made some fairly
> significant changes to the wiki regarding writing Fedora to USB.
> 
> I've done (yet another) revision of the main wiki instructions for
> writing USB sticks:
> 
> https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB

Thanks!

> 
> since the Fedora Media Writer tool - the rewrite (of the rewrite?) of
> LiveUSB Creator - now looks to be working well in testing, and is
> available on all our target platforms, the page now heavily promotes it
> as the best tool to use in almost all cases. Some other methods have
> been entirely removed - FMW should be a better choice for Windows and
> macOS than the tools that were listed before.
> 
> I retained sections for:
> 
> * livecd-iso-to-disk, as it's now the only tool that supports non-
> destructive write and data persistence
> 
> * gnome-disk-utility, for non-Fedora *nix without Flatpak support
> 
> * dd, for non-Fedora *nix without Flatpak or GNOME and people who just
> like dd
> 
> * unetbootin, because the section basically exists to explicitly state
> that we don't support it (maybe we should add a similar section for
> Rufus...)

I'd probably create a new top-level headline called "Non-recommended tools" or 
"Known to be broken tools" and put unetbootin in there. Because currently if 
you quickly look over TOC, unetbootin looks like a viable alternative, unless 
you read the details in its section. A separate section would make it clearer 
(and we can add more tools in the future).

> 
> Please do tell me about any problems you note, or if you think I
> removed something wrongly, or anything. Note that as of right now the
> best version of mediawriter for F23 and F24 is in updates-testing, so I
> had the instructions to install it include `--enablerepo=updates-
> testing`; I'm expecting the updates will go stable soon and we can
> remove that.
> 
> For validation testing folks, I have also revised the USB validation
> test cases. I really kinda hated the way the Installation matrix was
> set up with test names that didn't match the test case page names for
> no good reason, and also didn't think we really needed all the
> different test cases, so I've consolidated them into three
> consistently-named test cases with more result columns:
> 
> https://fedoraproject.org/wiki/QA:Testcase_USB_dd
> https://fedoraproject.org/wiki/QA:Testcase_USB_fmw

I propose to add a note into this testcase saying that by verifying FMW works 
correctly you can also mark dd testcase as passed. Because FMW is just a UI on 
top of dd-like approach, so this will allow more effective test coverage 
without any substantial risks (I believe). It's not like everyone would ever 
use FMW and not touch dd from this point on, I wouldn't worry that dd could get 
broken (that being quite unlikely by itself) without us noticing.

> https://fedoraproject.org/wiki/QA:Testcase_USB_litd
> 
> The effect is pretty much the same as before - except that we now
> include the FMW test instead of the LiveUSB Creator test - we test all
> three methods for both BIOS and UEFI and for both live and DVD images,
> but it's just arranged a little differently (and, I hope, better). I
> combined the separate 'live' and 'dvd' versions of the dd and litd test
> cases (which were barely different at all) into single test cases, and
> consolidated common wording between all the test cases using templates.
> I've put this change live on the current Installation validation page -
> https://fedoraproject.org/wiki/Test_Results:Fedora_25_Branched_20160930.n.0_Installation

Shouldn't those columns be called
x86_64 BIOS DVD 
x86_64 BIOS Live
x86_64 UEFI DVD 
x86_64 UEFI Live
?
Because currently it might be a bit confusing.

Also, should we add Mac and Windows columns for FMW? (And do we block on that? 
I'm not even sure.)

And finally, I was thinking about how to make testing more efficient. With FMW 
doing a dd copy, I don't think we actually need to perform a default 
installation for each of those methods, because the written stick should look 
exactly the same (it's a direct image copy in both cases). I believe doing just 
one default installation with dd-style-copied image would be sufficient, and in 
the other case we can simply just verify that the image passes verification and 
boots properly into the installer.

Would it be too confusing to create a QA:Testcase_USB_dd-like_install row which 
would mark an install performed, and QA:Testcase_USB_dd and QA:Testcase_USB_fmw 
would just mark verified image boot?

Alternatively, we could somehow connect this to the "Default boot and install" 
section, which is very much related, and we'll need to rethink it anyway 
(because currently it says "bare metal required" and we fill it with 
openqa...). Maybe we could have "Workstation live optical" (which is probably 
the only case where it still makes sense to test optical media) and the rest 
would be considered either USB or VM. Also, Live and DVD