Fedora 23 updates-testing report
The following Fedora 23 Security updates need testing: Age URL 347 https://bodhi.fedoraproject.org/updates/FEDORA-2015-16240 nagios-4.0.8-1.fc23 304 https://bodhi.fedoraproject.org/updates/FEDORA-2015-81ded368fe miniupnpc-1.9-6.fc23 277 https://bodhi.fedoraproject.org/updates/FEDORA-2015-27392b3324 jbig2dec-0.12-2.fc23 228 https://bodhi.fedoraproject.org/updates/FEDORA-2015-dd52a54fa1 python-pymongo-3.0.3-1.fc23 228 https://bodhi.fedoraproject.org/updates/FEDORA-2015-06a7c972e8 thttpd-2.25b-37.fc23 193 https://bodhi.fedoraproject.org/updates/FEDORA-2016-637618fcd4 mingw-nsis-2.50-1.fc23 68 https://bodhi.fedoraproject.org/updates/FEDORA-2016-fcccb0a547 nodejs-0.10.46-1.fc23 47 https://bodhi.fedoraproject.org/updates/FEDORA-2016-70b5173c05 ecryptfs-utils-111-1.fc23 35 https://bodhi.fedoraproject.org/updates/FEDORA-2016-9402100276 openssh-7.2p2-5.fc23 selinux-policy-3.13.1-158.22.fc23 34 https://bodhi.fedoraproject.org/updates/FEDORA-2016-8d79ade826 flex-2.6.0-2.fc23 34 https://bodhi.fedoraproject.org/updates/FEDORA-2016-aa394a130e nodejs-string-dot-prototype-dot-repeat-0.2.0-2.fc23 23 https://bodhi.fedoraproject.org/updates/FEDORA-2016-c2ec9c716e redis-3.2.3-1.fc23 20 https://bodhi.fedoraproject.org/updates/FEDORA-2016-b1a368 389-ds-base-1.3.4.14-1.fc23 20 https://bodhi.fedoraproject.org/updates/FEDORA-2016-5aa6973100 jasper-1.900.1-33.fc23 16 https://bodhi.fedoraproject.org/updates/FEDORA-2016-d6288f555c libarchive-3.2.1-3.fc23 python-libarchive-c-2.5-1.fc23 14 https://bodhi.fedoraproject.org/updates/FEDORA-2016-f9e951386e ca-certificates-2016.2.9-1.0.fc23 14 https://bodhi.fedoraproject.org/updates/FEDORA-2016-47dc2b203f firewalld-0.4.3.3-1.fc23 13 https://bodhi.fedoraproject.org/updates/FEDORA-2016-2b4ecfa79f libgcrypt-1.6.6-1.fc23 13 https://bodhi.fedoraproject.org/updates/FEDORA-2016-8e55114267 lcms2-2.8-2.fc23 13 https://bodhi.fedoraproject.org/updates/FEDORA-2016-87dde780b8 glibc-2.22-18.fc23 9 https://bodhi.fedoraproject.org/updates/FEDORA-2016-3a0195918f gnupg-1.4.21-1.fc23 7 https://bodhi.fedoraproject.org/updates/FEDORA-2016-d349b1c5f1 ganglia-3.7.2-10.fc23 2 https://bodhi.fedoraproject.org/updates/FEDORA-2016-06e4de8210 phpMyAdmin-4.6.4-2.fc23 2 https://bodhi.fedoraproject.org/updates/FEDORA-2016-ce1678471e mediawiki-1.26.4-1.fc23 2 https://bodhi.fedoraproject.org/updates/FEDORA-2016-db62a2d5a6 libksba-1.3.5-1.fc23 1 https://bodhi.fedoraproject.org/updates/FEDORA-2016-1f2444f878 vdsm-4.18.999-440.git0bb7717.fc23 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-820a4795a9 elog-3.1.1-7.fc23 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-7e817cbf55 slock-1.3-2.fc23 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-b3a6435b14 dhcpcd-6.11.3-1.fc23 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-7b4a60ae66 python-jwcrypto-0.3.2-1.fc23 The following Fedora 23 Critical Path updates have yet to be approved: Age URL 43 https://bodhi.fedoraproject.org/updates/FEDORA-2016-98a7a1b6e0 abrt-2.8.0-6.fc23 libreport-2.6.4-3.fc23 35 https://bodhi.fedoraproject.org/updates/FEDORA-2016-9402100276 openssh-7.2p2-5.fc23 selinux-policy-3.13.1-158.22.fc23 20 https://bodhi.fedoraproject.org/updates/FEDORA-2016-5aa6973100 jasper-1.900.1-33.fc23 16 https://bodhi.fedoraproject.org/updates/FEDORA-2016-d6288f555c libarchive-3.2.1-3.fc23 python-libarchive-c-2.5-1.fc23 15 https://bodhi.fedoraproject.org/updates/FEDORA-2016-343c55ea44 linux-firmware-20160816-67.git7c3dfc0b.fc23 14 https://bodhi.fedoraproject.org/updates/FEDORA-2016-471ab66d4d nss-3.26.0-1.0.fc23 nss-softokn-3.26.0-1.0.fc23 nss-util-3.26.0-1.0.fc23 14 https://bodhi.fedoraproject.org/updates/FEDORA-2016-f9e951386e ca-certificates-2016.2.9-1.0.fc23 13 https://bodhi.fedoraproject.org/updates/FEDORA-2016-87dde780b8 glibc-2.22-18.fc23 13 https://bodhi.fedoraproject.org/updates/FEDORA-2016-f1f7e3722d systemd-222-16.fc23 13 https://bodhi.fedoraproject.org/updates/FEDORA-2016-8e55114267 lcms2-2.8-2.fc23 13 https://bodhi.fedoraproject.org/updates/FEDORA-2016-66a914144d libfm-1.2.4-6.D20160627git2a537414de.fc23 13 https://bodhi.fedoraproject.org/updates/FEDORA-2016-2b4ecfa79f libgcrypt-1.6.6-1.fc23 12 https://bodhi.fedoraproject.org/updates/FEDORA-2016-1e281b415b redhat-rpm-config-37-1.fc23.1 11 https://bodhi.fedoraproject.org/updates/FEDORA-2016-bebe7b9c5b libavc1394-0.5.4-1.fc23 9 https://bodhi.fedoraproject.org/updates/FEDORA-2016-3a0195918f gnupg-1.4.21-1.fc23 8 https://bodhi.fedoraproject.org/updates/FEDORA-2016-4de7497ac4 gnupg2-2.1.13-2.fc23 6 https://bodhi.fedoraproject.org/updates/FEDORA-2016-221e4b44b9 gnome-online-accounts-3.18.6-1.fc23 4 https://bodhi.fedoraproject.org/updates/FEDORA-2016-22e1403506 livecd-tools-23.4-1.fc23 4
Fedora 24 updates-testing report
The following Fedora 24 Security updates need testing: Age URL 41 https://bodhi.fedoraproject.org/updates/FEDORA-2016-b3f93ead5b moin-1.9.8-1.fc24 23 https://bodhi.fedoraproject.org/updates/FEDORA-2016-32eaf0c41e redis-3.2.3-1.fc24 7 https://bodhi.fedoraproject.org/updates/FEDORA-2016-0ef628998f chicken-4.11.0-3.fc24 7 https://bodhi.fedoraproject.org/updates/FEDORA-2016-8749c58855 ganglia-3.7.2-10.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2016-2eef68e635 phpMyAdmin-4.6.4-2.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2016-af3b0af887 mediawiki-1.26.4-1.fc24 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-508767e6b7 elog-3.1.1-7.fc24 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-985b68721b slock-1.3-2.fc24 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-dcf5cad792 python-jwcrypto-0.3.2-1.fc24 The following Fedora 24 Critical Path updates have yet to be approved: Age URL 21 https://bodhi.fedoraproject.org/updates/FEDORA-2016-ddadfe403c pungi-4.1.8-1.fc24 python-productmd-1.2-2.fc24 13 https://bodhi.fedoraproject.org/updates/FEDORA-2016-aa32e6e85b libfm-1.2.4-6.D20160627git2a537414de.fc24 4 https://bodhi.fedoraproject.org/updates/FEDORA-2016-0edc0e1794 livecd-tools-23.4-1.fc24 2 https://bodhi.fedoraproject.org/updates/FEDORA-2016-88d8834106 pcmanfm-1.2.4-3.fc24 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-3687780371 libcdio-0.93-8.fc24 0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-8d425ad02f orc-0.4.26-1.fc24 The following builds have been pushed to Fedora 24 updates-testing NetworkManager-ssh-1.2.1-0.fc24 adobe-source-serif-pro-fonts-1.017-2.fc24 astigmatic-grand-hotel-fonts-1.000-3.fc24 fedpkg-1.25-1.fc24 feh-2.17.1-1.fc24 gpodder-3.9.1-1.fc24 gr-air-modes-0-0.49.20160831git3bad1f5d.fc24 haproxy-1.6.9-1.fc24 hub-2.2.5-1.fc24 krop-0.4.11-2.fc24 libcdio-0.93-8.fc24 libmfx-1.16-1.20160317git7adf2e4.fc24 lilypond-2.19.47-1.fc24 lilypond-doc-2.19.47-1.fc24 lis-1.5.76-1.fc24 mingw-mediawriter-0-1.1git19b13a8.fc24 openfst-1.5.4-1.fc24 opengrm-ngram-1.3.1-1.fc24 orc-0.4.26-1.fc24 python-cvss-1.4-1.fc24 python-fauxquests-1.1-1.fc24 python-jwcrypto-0.3.2-1.fc24 python-pytest-mock-1.1-3.fc24 python-simpletal-4.3-11.fc24 python-toml-0.9.2-1.fc24 python3-simpletal-5.2-1.fc24 setroubleshoot-3.3.11-1.fc24 setroubleshoot-plugins-3.3.6-1.fc24 sphinxtrain-1.0.8-30.fc24 tlock-1.6-1.fc24 typetype-molot-fonts-1.000-4.fc24 varnish-agent-4.1.1-1.fc24 Details about builds: NetworkManager-ssh-1.2.1-0.fc24 (FEDORA-2016-94b9224d4c) NetworkManager VPN plugin for SSH Update Information: Update to 1.2.1 release References: [ 1 ] Bug #1350244 - NetworkManager-ssh not working https://bugzilla.redhat.com/show_bug.cgi?id=1350244 adobe-source-serif-pro-fonts-1.017-2.fc24 (FEDORA-2016-0aa7a43b4b) A set of OpenType fonts designed to complement Source Sans Pro Update Information: Initial package References: [ 1 ] Bug #1371635 - Review Request: adobe-source-serif-pro-fonts - A set of OpenType fonts designed to complement Source Sans Pro https://bugzilla.redhat.com/show_bug.cgi?id=1371635 astigmatic-grand-hotel-fonts-1.000-3.fc24 (FEDORA-2016-8b432f332a) Script retro style fonts Update Information: New fonts for Fedora repository References: [ 1 ] Bug #1368606 - Review Request: astigmatic-grand-hotel-fonts - Script retro style fonts https://bugzilla.redhat.com/show_bug.cgi?id=1368606 fedpkg-1.25-1.fc24 (FEDORA-2016-316df24b5a) Fedora utility for working with dist-git Update Information: - update project URL (mattdm) - Allow fedpkg to be compatible with both bodhi 1 and bodhi 2. (randy) -
Re: Fedora 25-20160901.n.0 compose check report
On Thu, 2016-09-01 at 15:57 +, Fedora compose checker wrote: > Missing expected images: > > Cloud_base raw-xz i386 > Atomic raw-xz x86_64 > > Failed openQA tests: 15/89 (x86_64), 4/17 (i386), 1/2 (arm) > > ID: 31621 Test: x86_64 Workstation-live-iso install_default_upload > URL: https://openqa.fedoraproject.org/tests/31621 > ID: 31622 Test: x86_64 Workstation-live-iso install_default@uefi > URL: https://openqa.fedoraproject.org/tests/31622 > ID: 31628 Test: x86_64 Workstation-boot-iso install_default > URL: https://openqa.fedoraproject.org/tests/31628 > ID: 31629 Test: x86_64 Workstation-boot-iso install_default@uefi > URL: https://openqa.fedoraproject.org/tests/31629 > ID: 31630 Test: i386 Workstation-live-iso install_default > URL: https://openqa.fedoraproject.org/tests/31630 > ID: 31631 Test: i386 Workstation-boot-iso install_default > URL: https://openqa.fedoraproject.org/tests/31631 These are mostly needle issues, and should be solved tomorrow. The tests passed on staging, where I fixed the needles. > ID: 31632 Test: x86_64 Atomic-boot-iso install_default > URL: https://openqa.fedoraproject.org/tests/31632 This is the same ol' bug that's been around for months, but at least there's some movement now. > ID: 31641 Test: arm Minimal-raw_xz-raw.xz > install_arm_image_deployment_upload > URL: https://openqa.fedoraproject.org/tests/31641 It seems initial-setup is not running on boot (or, possibly, it's just too slow and we're not waiting long enough). Jan wrote the ARM test stuff, so if you could look into this... > ID: 31653 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller > URL: https://openqa.fedoraproject.org/tests/31653 This is a dependency issue, but I haven't immediately been able to reproduce it. I'll fiddle with it a bit more. > ID: 31655 Test: x86_64 Server-dvd-iso server_cockpit_default > URL: https://openqa.fedoraproject.org/tests/31655 This is another odd dependency issue, dnf refusing to install firefox because of some sqlite dependency issue, even though sqlite of the correct version is present in the repos and images with firefox on them composed just fine. Again, not quite sure what's going on here. It could simply be that the tests ran with yesterday's repos and there was a problem there, we'll see what happens tomorrow. > ID: 31684 Test: x86_64 universal install_iscsi > URL: https://openqa.fedoraproject.org/tests/31684 Same old: https://bugzilla.redhat.com/show_bug.cgi?id=1347415 this should get fixed in the next anaconda update. > ID: 31698 Test: x86_64 universal upgrade_desktop_64bit > URL: https://openqa.fedoraproject.org/tests/31698 > ID: 31700 Test: x86_64 universal upgrade_kde_64bit > URL: https://openqa.fedoraproject.org/tests/31700 > ID: 31701 Test: x86_64 universal upgrade_desktop_encrypted_64bit > URL: https://openqa.fedoraproject.org/tests/31701 > ID: 31703 Test: x86_64 universal upgrade_2_desktop_64bit > URL: https://openqa.fedoraproject.org/tests/31703 > ID: 31704 Test: x86_64 universal upgrade_2_server_64bit > URL: https://openqa.fedoraproject.org/tests/31704 > ID: 31705 Test: x86_64 universal upgrade_2_kde_64bit > URL: https://openqa.fedoraproject.org/tests/31705 > ID: 31706 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit > URL: https://openqa.fedoraproject.org/tests/31706 > ID: 31723 Test: i386 universal upgrade_desktop_32bit > URL: https://openqa.fedoraproject.org/tests/31723 > ID: 31724 Test: i386 universal upgrade_2_desktop_32bit > URL: https://openqa.fedoraproject.org/tests/31724 The desktop fails here are the same needle issues as with the desktop image install tests. The others are: https://bugzilla.redhat.com/show_bug.cgi?id=1366793 https://bugzilla.redhat.com/show_bug.cgi?id=1333591 > Passed openQA tests: 65/89 (x86_64), 13/17 (i386) > > Skipped openQA tests: 8 of 108 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24
Hi just loaded Kernel 4.7.2 in F24, boot ok, so far no further problems. Acer Laptop E15 E5-571G, F24 on an usb 3.0 flash medium. Kind regards -Ursprüngliche Mitteilung- Von: Adam WilliamsonAn: For testing and quality assurance of Fedora releases Verschickt: Mi, 31 Aug 2016 8:19 am Betreff: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24 Hi folks! Just thought I'd send out a testing idea for anyone who'slooking for something they can do.We currently have kernel 4.7 in updates-testing for Fedora 23 andFedora 24:23 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-f1adaaadc624 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-2e5ebfed6dit's always good to get new kernel releases tested on as much hardwareas possible, so if you haven't done it yet, please try updating thekernel on any machines you have running Fedora 23 or 24. This commandshould do it:dnf --enablerepo=updates-testing update kernel*then you can reboot, and check if all your hardware and your normal useof the system works OK with the new kernel. If it does, give positivefeedback for the update; if not, file a bug and give negative feedbackfor the update, with a link to your bug report. Testing kernel updatesis nice and safe, because even if it doesn't work well, you can justreboot and pick an older kernel from the boot menu - Fedora will alwayskeep three kernels installed, so you have a fallback if the newest onedoesn't work right.Thanks everyone! :)Just as a quick note on other testing topics: for Fedora 25 validation,we'll start getting nightly composes 'nominated' for testing againsoon, working towards the Beta release; Beta freeze is 2016-09-27, so amonth or so to go before we start thinking about Beta RCs. The Fedora25 Test Days should also be starting up soon - Sumantro is away rightnow, but I expect we'll start seeing announcements soon, so look outfor those! And of course, we can always test updates (not just thekernel updates) for 23, 24 and 25. Happy testing :)--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Fedora 25-20160901.n.0 compose check report
Missing expected images: Cloud_base raw-xz i386 Atomic raw-xz x86_64 Failed openQA tests: 15/89 (x86_64), 4/17 (i386), 1/2 (arm) ID: 31621 Test: x86_64 Workstation-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/31621 ID: 31622 Test: x86_64 Workstation-live-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/31622 ID: 31628 Test: x86_64 Workstation-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/31628 ID: 31629 Test: x86_64 Workstation-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/31629 ID: 31630 Test: i386 Workstation-live-iso install_default URL: https://openqa.fedoraproject.org/tests/31630 ID: 31631 Test: i386 Workstation-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/31631 ID: 31632 Test: x86_64 Atomic-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/31632 ID: 31641 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/31641 ID: 31653 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller URL: https://openqa.fedoraproject.org/tests/31653 ID: 31655 Test: x86_64 Server-dvd-iso server_cockpit_default URL: https://openqa.fedoraproject.org/tests/31655 ID: 31684 Test: x86_64 universal install_iscsi URL: https://openqa.fedoraproject.org/tests/31684 ID: 31698 Test: x86_64 universal upgrade_desktop_64bit URL: https://openqa.fedoraproject.org/tests/31698 ID: 31700 Test: x86_64 universal upgrade_kde_64bit URL: https://openqa.fedoraproject.org/tests/31700 ID: 31701 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/31701 ID: 31703 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/31703 ID: 31704 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/31704 ID: 31705 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/31705 ID: 31706 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/31706 ID: 31723 Test: i386 universal upgrade_desktop_32bit URL: https://openqa.fedoraproject.org/tests/31723 ID: 31724 Test: i386 universal upgrade_2_desktop_32bit URL: https://openqa.fedoraproject.org/tests/31724 Passed openQA tests: 65/89 (x86_64), 13/17 (i386) Skipped openQA tests: 8 of 108 -- 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: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: 'dnf system-upgrade reboot' doesn't do anything
On Thu, Sep 1, 2016 at 8:32 AM, Richard Rynikerwrote: > I am unhappy with the suggestion that the semantics of kernel parameters > may depend on some notion about how "temporary" they are. If a kernel > parameter is specified, it is present; if not specified, it is absent. 3 isn't even a kernel parameter, most things now on the kernel parameter line isn't even meant for the kernel, there is no way to infer what will parse it or what it does. It's a simple hack, and therefore it means the user has to, you know, know what the fuck they're doing when they use boot params. What you're basically saying is, you're unhappy that you have to know what the fuck you're doing to get it to do what you want it to do. Sorry. > It is proper to design parameter syntax and default values to favor > common usage. There also have to be mechanisms to handle different > specifications for the same parameter (first or last wins...) and use of > incompatible parameters (pick one, ignore both... but always log the > choice!) The last one wins. The last one is the 3 because that's what you set at boot time. By doing that, you're asking for multi-user.target which is exactly what you get. You do not ever get default.target. and since /system-update symlink causes default.target to mean system-update.target, you don't get that. > > In this case, "dnf system-upgrade reboot" is an explicit command to > perform an offline system update. Followed 10 seconds later by your 3. Last one wins. >That is what should happen, > regardless of the (default) target. Any target specification should > apply after the offline update. You overrode that. That's what you're asking for when you set 3 in the bootloader configuration. If you don't like that, stop doing things wrong, and start doing them correctly. > Are you concerned about the possibility "dnf system-upgrade reboot" was > ordered, then immediately decided it was wrong? How many times do you > want to ask "Do you really mean this?" Why should specification of > boot target 3 as a kernel parameter pretermit the offline update - but > possibly leave it waiting to occur unexpectedly during a subsequent boot? I don't have answers to your questions because I refuse the premise by which they even arise. I only use 3 when I'm editing a particular boot menu entry, non-persistently. If I wanted it persistent I'd change what default.target points to. That's the correct way to make persistent changes. Boot parameters make the OS less portable also. And I foresee the day when Fedora cannot be booted from another OS's bootloader because of this. > Your explanation of how systemd implements offline update using a symlink > offers an escape: boot from a different root file system (a live image, > if necessary) and remove the offline update symlink. If you think that > is too esoteric or awkward, implement a new kernel parameter such as > "cancel-offline-update" that does this. Request denied. > What is the relation between run level 1 and offline update? Does run > level 1 stop the init process before offline update? If yes, then that > is an easy escape: boot to run level 1, remove the offline update > symlink, then "systemctl default". My expectation is that any runlevel specified as a boot parameter will inhibit use of default.target and inhibit the offline update. Explicitly stating the runlevel at boot time means don't use default.target. -- Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: 'dnf system-upgrade reboot' doesn't do anything
I am unhappy with the suggestion that the semantics of kernel parameters may depend on some notion about how "temporary" they are. If a kernel parameter is specified, it is present; if not specified, it is absent. It is proper to design parameter syntax and default values to favor common usage. There also have to be mechanisms to handle different specifications for the same parameter (first or last wins...) and use of incompatible parameters (pick one, ignore both... but always log the choice!) In this case, "dnf system-upgrade reboot" is an explicit command to perform an offline system update. That is what should happen, regardless of the (default) target. Any target specification should apply after the offline update. Are you concerned about the possibility "dnf system-upgrade reboot" was ordered, then immediately decided it was wrong? How many times do you want to ask "Do you really mean this?" Why should specification of boot target 3 as a kernel parameter pretermit the offline update - but possibly leave it waiting to occur unexpectedly during a subsequent boot? Your explanation of how systemd implements offline update using a symlink offers an escape: boot from a different root file system (a live image, if necessary) and remove the offline update symlink. If you think that is too esoteric or awkward, implement a new kernel parameter such as "cancel-offline-update" that does this. What is the relation between run level 1 and offline update? Does run level 1 stop the init process before offline update? If yes, then that is an easy escape: boot to run level 1, remove the offline update symlink, then "systemctl default". -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24
Hi, Updated on HP Pavilion g6 and it booted fine. it is currently working perfectly hardwares detected correctly F24. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Self-introduction: Craig MacEachern
cmaceach...@sdf.org: > Greetings folks, > > I'm interested in helping out QA to get myself more involved with the > *nix ecosystem I've used for many years. I have no prior QA experience, > but I am excited to learn! > > My story: > Learned computing back in the DOS and BBS days (still love the King's > Quest and point-and-click genre of games). Discovered *nix around mid > 90s, but had so many problems even getting X to run (from what I > remember, there were ACPI issues and the infamous wireless drivers > issues). Got more serious about *nix in the mid 2000s when Ubuntu was > taking off. Ubuntu expanded my horizons and led me to discover Fedora. I > stick with Fedora as the sysadmin aspect of it carries over nicely into > most corporate environments with either RedHat or CentOS deployments. > > Credentials/experience in sysadmin/programming: > * I use, and maybe abuse, CentOS 6.x and 7.x on work servers daily. I do > light sysadmin/devops stuff (running an internal wiki, running > bash/python scripts) > * I run Fedora 24 at home as my daily driver. > * Passed the Linux Foundation Certified System Administrator course a > couple years ago. It just lapsed last month and I don't feel like > shelling out another $300 to do the exam again and re-certify. > * Several years programming experience, self-taught through online > course, books, articles, etc. Experience developing python GUI apps with > both QT and Tk, and homebrew games with SDL and C. Other languages > sprinkled here and there over the years (PHP/MySQL, QBasic!). > > Fun facts: I have a Master of Library Science degree and an English > degree. Greatly regret not doing computer science, but seems to have > worked out okay regardless. Hobies are wood working and brazilian > jiu-jitsu. > > Thanks everyone, and nice to meet you all! > > Craig MacEachern, aka saltycraig > > cmaceach...@sdf.org > SDF Public Access UNIX System - http://sdf.org > -- > test mailing list > test@lists.fedoraproject.org > To unsubscribe: > https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org Craig, Welcome to the ML. I trust you have found the release validation pages [0][1] [0] https://fedoraproject.org/wiki/QA:Release_validation_test_plan [1] https://fedoraproject.org/wiki/QA/SOP_Release_Validation_Test_Event Hope to see you around in meetings and the ML in the coming weeks and months.. -- Corey Sheldon +1 310.909.7672 0x8B4E89435A88E539 | C006 564F FA67 CDEA E29B F202 8B4E 8943 5A88 E539 0x59276298D2264944 | 6292 9ABD 6374 6AA7 6D4B 730F 5927 6298 D226 4944 https://gist.github.com/linux-modder/ac5dc6fa211315c633c9 || https://keybase.io/linuxmodder 'Have no limitation, as limitation, have no way as way' --Bruce Lee 'Everything is impossible, until it's Done!' -- Nelson Mandela 'Any man willing to sacrifice freedom for security, deserves neither' --Benjamin Franklin Disclaimer: All correspondence shall be deemed privileged and confidential unless otherwise stated in the contents of respective correspondence. All emails ARE signed with at least one of the keys shown above. Any email or correspondence lacking such shall be regarded as suspect. The key signed or encrypted with IS ALWAYS attached as a $keyid.asc, $keyid.sig, or included in the attached csv file. If this correspondence has reached you in error please disregard it and it is kindly requested that a return email with a simple subject 'Miss-routed mail, please remove me' shall be sufficient. GPG mail is openly and freely solicited. 0xD2264944.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24
booted on lenovo X1 carbon OK -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Can't login in Wayland after change language from Russian to English in Fedora 25 alpha
2016-09-01 13:36 GMT+03:00 Kamil Paral: > > Hi, when you say you installed it in Russian language, have you also > configured Russian keyboard layout (that is the default when you pick > Russian language), or have you used USA keyboard by default? What keyboard > layout have you used when creating the password for your user in anaconda? > When you say you changed your language to English in GNOME, do you mean > changing *only* the language, or have you also changed the keyboard layouts? > > When you are in GDM and you can't log in - does switching the keyboard > layout (should be available in top right corner) help? > > Do you have multiple standard users defined in the system, or just one > (because if you have just one, GNOME changes the language of the whole > system, if you have more of them, it changes the language of just that one > user). > In anakonda I configure Russian keyboard layout and create only password for root without creation new user. New user I create after installation for in first login via root. I have two lamguage layouts: Russian and English. After installation I have RU.png (in attachments) settings and change to EN.png settings. Best regards, Alexander Kolesnikov -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Self-introduction: Craig MacEachern
Greetings folks, I'm interested in helping out QA to get myself more involved with the *nix ecosystem I've used for many years. I have no prior QA experience, but I am excited to learn! My story: Learned computing back in the DOS and BBS days (still love the King's Quest and point-and-click genre of games). Discovered *nix around mid 90s, but had so many problems even getting X to run (from what I remember, there were ACPI issues and the infamous wireless drivers issues). Got more serious about *nix in the mid 2000s when Ubuntu was taking off. Ubuntu expanded my horizons and led me to discover Fedora. I stick with Fedora as the sysadmin aspect of it carries over nicely into most corporate environments with either RedHat or CentOS deployments. Credentials/experience in sysadmin/programming: * I use, and maybe abuse, CentOS 6.x and 7.x on work servers daily. I do light sysadmin/devops stuff (running an internal wiki, running bash/python scripts) * I run Fedora 24 at home as my daily driver. * Passed the Linux Foundation Certified System Administrator course a couple years ago. It just lapsed last month and I don't feel like shelling out another $300 to do the exam again and re-certify. * Several years programming experience, self-taught through online course, books, articles, etc. Experience developing python GUI apps with both QT and Tk, and homebrew games with SDL and C. Other languages sprinkled here and there over the years (PHP/MySQL, QBasic!). Fun facts: I have a Master of Library Science degree and an English degree. Greatly regret not doing computer science, but seems to have worked out okay regardless. Hobies are wood working and brazilian jiu-jitsu. Thanks everyone, and nice to meet you all! Craig MacEachern, aka saltycraig cmaceach...@sdf.org SDF Public Access UNIX System - http://sdf.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Can't login in Wayland after change language from Russian to English in Fedora 25 alpha
2016-09-01 14:28 GMT+03:00 Kamil Paral: I think I have reproduced the bug and reported it here: > https://bugzilla.redhat.com/show_bug.cgi?id=1372300 > > Can you please confirm whether the workaround works for you (switching the > keyboard layout to a different one and then back to the desired one)? > Thanks. > Switching the keyboard layout in Log In window? First EN->RU then RU->EN and try to login? Or what? If you mean this case - it does not work. Best regards, Alexander Kolesnikov -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24
Hi, have updated the F23 Kernel to 4.7.2 -> so far no problems, an update of F24 is still not possible Kernel 4.7.2 seem so far not to be in updates-testing. Kind regards -Ursprüngliche Mitteilung- Von: Adam WilliamsonAn: For testing and quality assurance of Fedora releases Verschickt: Mi, 31 Aug 2016 8:19 am Betreff: Testing idea: kernel 4.7 for Fedora 23 / Fedora 24 Hi folks! Just thought I'd send out a testing idea for anyone who'slooking for something they can do.We currently have kernel 4.7 in updates-testing for Fedora 23 andFedora 24:23 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-f1adaaadc624 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-2e5ebfed6dit's always good to get new kernel releases tested on as much hardwareas possible, so if you haven't done it yet, please try updating thekernel on any machines you have running Fedora 23 or 24. This commandshould do it:dnf --enablerepo=updates-testing update kernel*then you can reboot, and check if all your hardware and your normal useof the system works OK with the new kernel. If it does, give positivefeedback for the update; if not, file a bug and give negative feedbackfor the update, with a link to your bug report. Testing kernel updatesis nice and safe, because even if it doesn't work well, you can justreboot and pick an older kernel from the boot menu - Fedora will alwayskeep three kernels installed, so you have a fallback if the newest onedoesn't work right.Thanks everyone! :)Just as a quick note on other testing topics: for Fedora 25 validation,we'll start getting nightly composes 'nominated' for testing againsoon, working towards the Beta release; Beta freeze is 2016-09-27, so amonth or so to go before we start thinking about Beta RCs. The Fedora25 Test Days should also be starting up soon - Sumantro is away rightnow, but I expect we'll start seeing announcements soon, so look outfor those! And of course, we can always test updates (not just thekernel updates) for 23, 24 and 25. Happy testing :)--test mailing listtest@lists.fedoraproject.orgTo unsubscribe:https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Can't login in Wayland after change language from Russian to English in Fedora 25 alpha
> > Hi all! > > > I am install Fedora 25 Alpha Workstation with Russian language. In settings > > change language to English and log out. After that I can't login into my > > users (root and new account). Reopens the login window without errors. But > > if I change settings from GNOME to GNOME on Xorg - I can login. > > > Best regards, > > > Alexander Kolesnikov > > Hi, when you say you installed it in Russian language, have you also > configured Russian keyboard layout (that is the default when you pick > Russian language), or have you used USA keyboard by default? What keyboard > layout have you used when creating the password for your user in anaconda? > When you say you changed your language to English in GNOME, do you mean > changing *only* the language, or have you also changed the keyboard layouts? > When you are in GDM and you can't log in - does switching the keyboard layout > (should be available in top right corner) help? > Do you have multiple standard users defined in the system, or just one > (because if you have just one, GNOME changes the language of the whole > system, if you have more of them, it changes the language of just that one > user). > Thanks. I think I have reproduced the bug and reported it here: https://bugzilla.redhat.com/show_bug.cgi?id=1372300 Can you please confirm whether the workaround works for you (switching the keyboard layout to a different one and then back to the desired one)? Thanks. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Self-introduction: Akinsola
Thanks -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Self-introduction: Akinsola
I am grateful for the approval and would subsequently ask if I need help. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Can't login in Wayland after change language from Russian to English in Fedora 25 alpha
> Hi all! > I am install Fedora 25 Alpha Workstation with Russian language. In settings > change language to English and log out. After that I can't login into my > users (root and new account). Reopens the login window without errors. But > if I change settings from GNOME to GNOME on Xorg - I can login. > Best regards, > Alexander Kolesnikov Hi, when you say you installed it in Russian language, have you also configured Russian keyboard layout (that is the default when you pick Russian language), or have you used USA keyboard by default? What keyboard layout have you used when creating the password for your user in anaconda? When you say you changed your language to English in GNOME, do you mean changing *only* the language, or have you also changed the keyboard layouts? When you are in GDM and you can't log in - does switching the keyboard layout (should be available in top right corner) help? Do you have multiple standard users defined in the system, or just one (because if you have just one, GNOME changes the language of the whole system, if you have more of them, it changes the language of just that one user). Thanks. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Can't login in Wayland after change language from Russian to English in Fedora 25 alpha
On Wed, 2016-08-31 at 16:17 +0300, Alexander Kolesnikov wrote: > Hi all! > > I am install Fedora 25 Alpha Workstation with Russian language. In > settings change language to English and log out. After that I can't > login into my users (root and new account). Reopens the login window > without errors. But if I change settings from GNOME to GNOME on Xorg > - I can login. The sanctions, you should be ready for it. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Can't login in Wayland after change language from Russian to English in Fedora 25 alpha
2016-08-31 19:14 GMT+03:00 Chris Murphy: > > > On Wed, Aug 31, 2016 at 7:17 AM, Alexander Kolesnikov > wrote: > >> Hi all! >> >> I am install Fedora 25 Alpha Workstation with Russian language. In >> settings change language to English and log out. After that I can't login >> into my users (root and new account). Reopens the login window without >> errors. But if I change settings from GNOME to GNOME on Xorg - I can login. >> > > Could be gdm or gnome-shell, not sure. If you can file a bug and attach > 'journalctl --since=-30m > journal.log' that'd be useful. If you can > tighten up the time estimate that keeps it a bit cleaner; so if you know > the failed login attempt on Wayland was about 5 minutes ago, you can do > --since=-6m or whatever, a little more is better than cutting it off. That > is a minus before the number. > Hi, Chris. I am trying to login via GUI with Wayland and after that use 'journalctl --since=-30m > journal.log via ssh. And attach file. journal1.log Description: Binary data -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Presentation - Ask for approval
- Original Message - > From: "Rodrigo de Araujo"> To: test@lists.fedoraproject.org > Sent: Wednesday, August 31, 2016 8:41:19 PM > Subject: Presentation - Ask for approval > > Hello there, > > My name is Rodrigo, I'm 32 y.o and I am from Belo Horizonte, Brazil. > > I am writing because I would like to join the Fedora Quality Assurance Group, > please. I already asked to join on the FAS system, so now it's pending of > approval. > > I have a degree in Advertising and as a graduate student I am working on a > Master degree in Language and Technology. I work as a Audiovisual Producer > and Editor here. > > I already help the project by voting for tags and adding tags to packages > without them. I also installed Fedora on 6 computers of friends and family > members, etc. > > By joining this group I think I would be able to vote for supplemental > wallpapers too which is great. :-) > > I pĺan to learn more about Testing and QA so I can help the group in the next > releases. > > Thank you for your time. > > My FAS account name is 'rodrigodearaujo' > > With my best regards, > > Rodrigo Hey and Welcome avillarreal Thanks for your interest in joining qa team, I have approved your request. Next,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 candidate, 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_Alpha_1.2_Summary?rd=Test_Results:Current_Summary [2]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc [3]https://bugzilla.redhat.com/ [4]https://fedoraproject.org/wiki/QA:Updates_Testing Should you have any question, you reach out to me directly or in the list! We also have on-boarding call when we have ~10 new people joining qa group , On boarding calls are video+text (Hangout sessions) where we run through how to start and focus on how to do testing the right way. Lookout for the "Call for action On boarding Call" email this month! Thanks Sumantro -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Introduction: Adan
- Original Message - > From: "Adan Villarreal"> To: test@lists.fedoraproject.org > Sent: Thursday, September 1, 2016 4:53:22 AM > Subject: Introduction: Adan > > Hi, my name is Adan Villarreal. I am a 19 year old software engineering > student and have been using linux for a while. I want to contribute to the > project in some way. > I have experience with c++, java, python and a bit of security. > Hope I can help. > > Adan Villarreal > IRC: avillarreal > Hey and Welcome avillarreal You can start off with requesting sponsorship of "qa" group if you haven't done already. Next,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 candidate, 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_Alpha_1.2_Summary?rd=Test_Results:Current_Summary [2]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc [3]https://bugzilla.redhat.com/ [4]https://fedoraproject.org/wiki/QA:Updates_Testing 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: https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org