Fedora Rawhide 20160120 compose check report
Missing expected images: Kde disk raw armhfp Kde live i386 Kde live x86_64 Images in this compose but not Rawhide 20160119: Cloud_atomic vagrant virtualbox x86_64 Cloud_atomic vagrant libvirt x86_64 No images in Rawhide 20160119 but not this. Failed openQA tests: 4 of 63 ID: 3484Test: x86_64 universal server_software_raid URL: https://openqa.fedoraproject.org/tests/3484 ID: 3535Test: x86_64 workstation_live base_services_start URL: https://openqa.fedoraproject.org/tests/3535 ID: 3491Test: x86_64 universal package_set_kde URL: https://openqa.fedoraproject.org/tests/3491 ID: 3517Test: i386 universal package_set_kde URL: https://openqa.fedoraproject.org/tests/3517 Passed openQA tests: 59 of 63 -- 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: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Criteria proposal: applying 'post-install' criteria to live and appliance images
On Wed, 2016-01-20 at 03:53 -0500, Kamil Paral wrote: > > Hi, folks! I'm working through some criteria issues that came up during > > F23 validation. > > > > Here's one: a few times, we hit issues on live images which would have > > been violations of the 'post-install' release criteria, except those > > are explicitly for 'installed' systems. We generally felt that the > > relevant 'post-install' criteria should also apply to live boots. > > > > Here's a top-level idea for handling that: > > > > 1. Rename the 'Post-install requirements' section on each criteria page > > to 'Post-deployment and live requirements' > > 2. Add some text at the top of the section explaining the general idea: > > the requirements in the section apply to installed systems, 'appliance' > > environments like the cloud images, *and* live environments, where > > appropriate > > 3. Adjust the wording of each individual criterion in the sections, > > where appropriate. Just to give an example: > > > > "Unless explicitly specified otherwise, after system installation > > SELinux must be enabled and in enforcing mode." > > > > would become something like: > > > > "Unless explicitly specified otherwise, SELinux must be enabled and in > > enforcing mode in live environments and after system installation." > > > > Does this general approach sound good? If so, I'll post some drafts > > later in the week. Thanks! > > +1 > > But in the SELinux case, I think anaconda disables SELinux even on > Live, so it might need some clarification. It does, but I'm not sure that's worth mentioning in the criterion, and really I was just trying to give a sample of the wording changes that would happen, not be super precise. If we're gonna mention that I'd do it in a footnote. (It only sets Permissive mode while it's actually running, it restores Enforcing on quit, IIRC). -- 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: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: GStreamermm
On Wed, 2016-01-20 at 10:11 +, Russel Winder wrote: > On Wed, 2016-01-20 at 00:35 +, Peter Robinson wrote: > […] > > There's nothing stopping you packaging it up :-) > […] > > Clearly true, per se. I have though no idea how to create packages, > especially for submission to the Fedora repository. Good thing we have comprehensive documentation on it, then! https://fedoraproject.org/wiki/Join_the_package_collection_maintainers -- 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: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Error while upgrade F22 to F23
Hi all! I am trying to upgrade my F22 to F23 but have some error: [root@xps ~]# dnf system-upgrade download --releasever=23 Error: Failed to synchronize cache for repo 'updates' from ' http://download.fedoraproject.org/pub/fedora/linux/updates/23/x86_64/': Yum repo downloading error: Downloading error(s): repodata/47725165e267c3d2c65c479d6d51c401b02d1ec5dc2216bb4aa1a0597a7227b6-filelists.xml.gz - Cannot download, all mirrors were already tried without success; repodata/2c127fe4a8ac7a5618aa2d7ed0791878b401c9517f3d4b9c2503484c98a54f71-updateinfo.xml.xz - Cannot download, all mirrors were already tried without success Maybe anyone know how resolve this error? Thanks. Best regards, Alexander Kolesnikov -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Error while upgrade F22 to F23
On 01/20/2016 03:10 PM, Alexander Kolesnikov wrote: I am trying to upgrade my F22 to F23 but have some error: [root@xps ~]# dnf system-upgrade download --releasever=23 Error: Failed to synchronize cache for repo 'updates' from 'http://download.fedoraproject.org/pub/fedora/linux/updates/23/x86_64/': Yum repo downloading error: Downloading error(s): repodata/47725165e267c3d2c65c479d6d51c401b02d1ec5dc2216bb4aa1a0597a7227b6-filelists.xml.gz - Cannot download, all mirrors were already tried without success; repodata/2c127fe4a8ac7a5618aa2d7ed0791878b401c9517f3d4b9c2503484c98a54f71-updateinfo.xml.xz - Cannot download, all mirrors were already tried without success Maybe anyone know how resolve this error? Check that your repo config is using the metalink and not the baseurl. You probably just need to try again. Maybe add a --refresh to the command to force dnf to update its repo cache. -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
Re: Criteria proposal: applying 'post-install' criteria to live and appliance images
> Hi, folks! I'm working through some criteria issues that came up during > F23 validation. > > Here's one: a few times, we hit issues on live images which would have > been violations of the 'post-install' release criteria, except those > are explicitly for 'installed' systems. We generally felt that the > relevant 'post-install' criteria should also apply to live boots. > > Here's a top-level idea for handling that: > > 1. Rename the 'Post-install requirements' section on each criteria page > to 'Post-deployment and live requirements' > 2. Add some text at the top of the section explaining the general idea: > the requirements in the section apply to installed systems, 'appliance' > environments like the cloud images, *and* live environments, where > appropriate > 3. Adjust the wording of each individual criterion in the sections, > where appropriate. Just to give an example: > > "Unless explicitly specified otherwise, after system installation > SELinux must be enabled and in enforcing mode." > > would become something like: > > "Unless explicitly specified otherwise, SELinux must be enabled and in > enforcing mode in live environments and after system installation." > > Does this general approach sound good? If so, I'll post some drafts > later in the week. Thanks! +1 But in the SELinux case, I think anaconda disables SELinux even on Live, so it might need some clarification. -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
rawhide report: 20160120 changes
Compose started at Wed Jan 20 05:15:02 UTC 2016 Broken deps for i386 -- [IQmol] IQmol-2.3.0-9.fc24.i686 requires libboost_serialization.so.1.58.0 IQmol-2.3.0-9.fc24.i686 requires libboost_iostreams.so.1.58.0 IQmol-2.3.0-9.fc24.i686 requires libOpenMeshCore.so.3.2 [alliance] alliance-5.0-40.20090901snap.fc22.i686 requires libXm.so.2 [asterisk] asterisk-calendar-13.3.2-1.fc23.2.i686 requires libical.so.1 [avogadro] avogadro-libs-1.1.1-15.fc24.i686 requires libGLEW.so.1.10 [banshee] banshee-2.6.2-12.fc23.i686 requires mono(taglib-sharp) = 0:2.0.3.7 [banshee-community-extensions] banshee-community-extensions-2.4.0-11.fc23.i686 requires mono(taglib-sharp) = 0:2.0.3.7 [bes] bes-3.14.0-8.fc24.i686 requires libdap.so.17 [couchdb] couchdb-1.6.1-7.fc24.i686 requires erlang(erl_nif_version) = 0:2.7 couchdb-1.6.1-7.fc24.i686 requires erlang(erl_drv_version) = 0:3.1 [eclipse-jbosstools] eclipse-jbosstools-as-4.2.2-1.fc22.noarch requires osgi(org.eclipse.tm.terminal) [ejabberd] ejabberd-14.07-6.fc22.i686 requires erlang(erl_nif_version) = 0:2.7 ejabberd-14.07-6.fc22.i686 requires erlang(erl_drv_version) = 0:3.1 [erlang-basho_metrics] erlang-basho_metrics-1.0.0-15.fc23.i686 requires erlang(erl_nif_version) = 0:2.7 [erlang-bitcask] erlang-bitcask-1.6.3-6.fc22.i686 requires erlang(erl_nif_version) = 0:2.7 [erlang-ebloom] erlang-ebloom-2.0.0-2.fc23.i686 requires erlang(erl_nif_version) = 0:2.7 [erlang-eleveldb] erlang-eleveldb-1.3.2-7.fc22.i686 requires erlang(erl_nif_version) = 0:2.7 [erlang-emmap] erlang-emmap-0-0.12.git05ae1bb.fc23.i686 requires erlang(erl_nif_version) = 0:2.7 [erlang-esasl] erlang-esasl-0.1-18.20120116git665cc80.fc23.i686 requires erlang(erl_drv_version) = 0:3.1 [erlang-js] erlang-js-1.3.0-1.fc22.i686 requires erlang(erl_drv_version) = 0:3.1 [erlang-skerl] erlang-skerl-1.1.0-11.fc23.i686 requires erlang(erl_nif_version) = 0:2.7 [erlang-snappy] erlang-snappy-1.0.3-0.11.git80db168.fc23.i686 requires erlang(erl_nif_version) = 0:2.7 [fawkes] fawkes-core-0.5.0-26.fc24.i686 requires libmicrohttpd.so.10 fawkes-plugin-player-0.5.0-26.fc24.i686 requires libgeos-3.4.2.so fawkes-plugin-xmlrpc-0.5.0-26.fc24.i686 requires libmicrohttpd.so.10 [gcc-python-plugin] gcc-python2-debug-plugin-0.14-8.fc24.i686 requires gcc = 0:5.3.1-2.fc24 gcc-python2-plugin-0.14-8.fc24.i686 requires gcc = 0:5.3.1-2.fc24 gcc-python3-debug-plugin-0.14-8.fc24.i686 requires gcc = 0:5.3.1-2.fc24 gcc-python3-plugin-0.14-8.fc24.i686 requires gcc = 0:5.3.1-2.fc24 [gnash] 1:gnash-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_serialization.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:gnash-0.8.10-19.fc24.i686 requires libboost_date_time.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_serialization.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:gnash-cygnal-0.8.10-19.fc24.i686 requires libboost_date_time.so.1.58.0 1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-extension-dejagnu-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-extension-fileio-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0 1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires libboost_program_options.so.1.58.0 1:gnash-extension-lirc-0.8.10-19.fc24.i686 requires libboost_iostreams.so.1.58.0 1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires libboost_thread.so.1.58.0 1:gnash-extension-mysql-0.8.10-19.fc24.i686 requires libboost_system.so.1.58.0
Re: GStreamermm
On Wed, 2016-01-20 at 00:35 +, Peter Robinson wrote: […] > There's nothing stopping you packaging it up :-) […] Clearly true, per se. I have though no idea how to create packages, especially for submission to the Fedora repository. Also I am going to fall into the "chicken and egg" pit myself: it is easier and quicker to create an application specific C++ wrapper around the C API than to contribute the package. I bet this is what is happening generally. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
