Re: Announcing the release of Fedora 21 Beta!
Hi, this link http://fedoraproject.org/get-prerelease i.e. for F21 Workstation Beta points still to ttp://download.fedoraproject.org/pub/fedora/linux/releases/test/21-Beta/Workstation/x86_64/iso/Fedora-Live-Workstation-x86_64-21_Beta-4.iso Kind Regards -Ursprüngliche Mitteilung- Von: Dennis Gilmore den...@ausil.us An: announce annou...@lists.fedoraproject.org; devel-announce devel-annou...@lists.fedoraproject.org; test-announce test-annou...@lists.fedoraproject.org Verschickt: Di, 4 Nov 2014 9:28 pm Betreff: Announcing the release of Fedora 21 Beta! -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The Fedora 21 beta release is here, and - as usual - is packed with amazing improvements to Fedora, as well as fantastic free and open source software, gently harvested for your enjoyment. No bits were harmed in the making of this beta. What is the Beta Release? = The beta release is the last important milestone before the release of Fedora 21. A Beta release is code-complete and bears a very strong resemblance to the third and final release. Only critical bug fixes will be pushed as updates up to the general release of Fedora 21. The final release of Fedora 21 is [https://fedoraproject.org/wiki/Releases/21/Schedule] expected in early December. Meanwhile, download the beta of Fedora 21 and help us make it even better: http://fedoraproject.org/get-prerelease We need your help to make Fedora 21 the best release yet, so please take some time to download and try out the beta and make sure the things that are important to you are working. If you find a bug, please report it: https://fedoraproject.org/wiki/How_to_file_a_bug_report Every bug you uncover is a chance to improve the experience for millions of Fedora users worldwide. Together, we can make Fedora 21 a rock-solid distribution. We have a culture of coordinating new features and pushing fixes upstream as much as feasible and your feedback will help improve not only Fedora but Linux and free software on the whole. https://fedoraproject.org/wiki/Staying_close_to_upstream_projects (See the end of this announcement for more information on how to help.) Since it's a beta release, some problems may still be lurking. A list of problems that we already know about can be found at the Common F21 bugs page: http://fedoraproject.org/wiki/Common_F21_bugs Fedora.Next and Fedora 21 Products == As part of the Fedora.next initiative, Fedora 21 will boast three products, Cloud, Server, and Workstation: * Cloud: https://fedoraproject.org/wiki/Cloud * Server: https://fedoraproject.org/wiki/Server * Workstation: https://fedoraproject.org/wiki/Workstation We encourage you to visit the wiki pages providing the details of these individual products for more information. Spins - - In addition to the new Fedora products, Fedora users also have the choice of Fedora Spins that highlight user favorites like KDE Plasma Workspaces, Xfce, LXDE, and Sugar on a Stick (SoaS). If you're interested in trying out one of the spins, head over to the prelease page for Fedora Spins and grab the spins you're interested in: http://fedoraproject.org/get-spin-prerelease Fedora 21 Base - -- Each of the products will build on the base set of packages for Fedora. For instance, each product will use the same packages for the kernel, RPM, Yum, systemd, Anaconda, and so forth. The Base Working Group develops the standard platform for all Fedora products, which includes the installer, compose tools, and basic platform for the other products. The Base set of packages is not a full product intended for use on its own, but to be kept as a small, stable platform for other products to build on. Highlights in the Beta Release == In this section, we'll look at some of the things that are new or interesting in the Beta release. A Note on Shellshocked - -- You've probably read all about the Shellshocked vulnerability in GNU Bash, which affected Fedora 19, 20, and 21 Alpha. Rest assured that Fedora 21 beta has been patched to close this vulnerability. Fedora 21 Cloud === The Fedora Cloud Working Group and Special Interest Group (SIG) has been busy leading up to Fedora 21. Cloud is now a top-level product for Fedora 21, and will include images for use in private cloud environments like OpenStack, as well as AMIs for use on Amazon, and a new image streamlined for running Docker containers. Modular Kernel Packaging for Cloud - -- Space is precious, and there's little reason to include drivers for hardware that doesn't exist in the cloud. As part of the work for Fedora 21, the cloud SIG and kernel team split the kernel into two packages. One package contains the minimum modules for running in a virtualized environment, the other contains the larger set of modules for a more general installation. As a
Re: Adding GNOME ....
On Wed, 2014-11-05 at 13:35 +0800, Ed Greshko wrote: On 10/26/14 11:06, Adam Williamson wrote: On Sun, 2014-10-26 at 10:51 +0800, Ed Greshko wrote: On 10/26/14 10:48, Adam Williamson wrote: On Sun, 2014-10-26 at 10:44 +0800, Ed Greshko wrote: On 10/26/14 10:40, Adam Williamson wrote: On Sun, 2014-10-26 at 10:20 +0800, Ed Greshko wrote: After doing a KDE install from the Fedora-Server-netinst-x86_64-21_Beta ISO I wanted to add GNOME to the mix. In the past, even on B-TC4 I believe, I simply did yum groupinstall GNOME Desktop. However, now that choice no longer exists when doing yum grouplist. Try 'yum install @^gnome-desktop-environment'. [root@localhost ~]# yum install @^gnome-desktop-environment Loaded plugins: langpacks Group gnome-desktop-environment does not exist. Error: Nothing to do huh, i see it in comps. maybe someone removed it since my last checkout? Will you follow up or does a bugzilla of some sort need to be created? It's not necessarily a bug. It wants more looking into, but I'm not gonna do it tonight. Still can't find a way to install the GNOME desktop after doing a KDE install. Using the latest, and greatest, Beta just released. This could be very annoying to some people. :-) try 'yum groupinstall gnome-desktop-environment'. -- 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: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Announcing the release of Fedora 21 Beta!
On Wed, 2014-11-05 at 03:32 -0500, Joerg Lechner wrote: Hi, this link http://fedoraproject.org/get-prerelease i.e. for F21 Workstation Beta points still to ttp://download.fedoraproject.org/pub/fedora/linux/releases/test/21-Beta/Workstation/x86_64/iso/Fedora-Live-Workstation-x86_64-21_Beta-4.iso Kind Regards Well...why wouldn't it? That's the right link... -- 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: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
On 11/05/14 16:59, Adam Williamson wrote: On Wed, 2014-11-05 at 13:35 +0800, Ed Greshko wrote: On 10/26/14 11:06, Adam Williamson wrote: On Sun, 2014-10-26 at 10:51 +0800, Ed Greshko wrote: On 10/26/14 10:48, Adam Williamson wrote: On Sun, 2014-10-26 at 10:44 +0800, Ed Greshko wrote: On 10/26/14 10:40, Adam Williamson wrote: On Sun, 2014-10-26 at 10:20 +0800, Ed Greshko wrote: After doing a KDE install from the Fedora-Server-netinst-x86_64-21_Beta ISO I wanted to add GNOME to the mix. In the past, even on B-TC4 I believe, I simply did yum groupinstall GNOME Desktop. However, now that choice no longer exists when doing yum grouplist. Try 'yum install @^gnome-desktop-environment'. [root@localhost ~]# yum install @^gnome-desktop-environment Loaded plugins: langpacks Group gnome-desktop-environment does not exist. Error: Nothing to do huh, i see it in comps. maybe someone removed it since my last checkout? Will you follow up or does a bugzilla of some sort need to be created? It's not necessarily a bug. It wants more looking into, but I'm not gonna do it tonight. Still can't find a way to install the GNOME desktop after doing a KDE install. Using the latest, and greatest, Beta just released. This could be very annoying to some people. :-) try 'yum groupinstall gnome-desktop-environment'. [root@f21-b1k ~]# yum groupinstall gnome-desktop-environment Loaded plugins: langpacks Warning: group gnome-desktop-environment does not exist. Maybe run: yum groups mark install (see man yum) Error: No packages in any requested group available to install or update [root@f21-b1k ~]# yum grouplist Loaded plugins: langpacks Available environment groups: Fedora Server Fedora Cloud Server Fedora Workstation KDE Plasma Workspaces Xfce Desktop LXDE Desktop Cinnamon Desktop MATE Desktop Sugar Desktop Environment Development and Creative Workstation Web Server Infrastructure Server Basic Desktop Minimal Install -- If you can't laugh at yourself, others will gladly oblige. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
On Sun, 2014-10-26 at 10:20 +0800, Ed Greshko wrote: There is a Fedora Workstation but that can't be installed due to I have a similar issue actually, but the other way around: Fresh F21 beta workstation install. I tried to install KDE using dnf, but fedora-release-workstation and fedora-release-nonproduct conflict. If I try to remove fedora-release-workstation, dnf replaces it with fedora-release-server which gets me back to the same state really. Is it impossible to install other DEs along the workstation at the moment using dnf? [asinha@localhost ~]$ sudo dnf remove fedora-release-workstation Dependencies resolved. Package Arch Version Repository Size Installing: cockpit x86_64 0.27-1.fc21 fedora 342 k cockpit-assets noarch 0.27-1.fc21 fedora 920 k fedora-release-server noarch 21-0.16 fedora 19 k firewalld-config-server noarch 0.3.12-1.fc21 fedora 45 k libssh x86_64 0.6.3-3.fc21fedora 150 k python-futures noarch 2.1.6-3.fc21fedora 34 k rolekit noarch 0.1.0-2.fc21fedora 99 k storagedx86_64 0.3.1-1.fc21fedora 92 k Removing: fedora-release-workstation noarch 21-0.16 @System1.0 k firewalld-config-workstationnoarch 0.3.12-1.fc21 @System1.0 k Transaction Summary Install 8 Packages Remove 2 Packages Total download size: 1.7 M Is this ok [y/N]: __ I'm assuming yum shell should be able to help here, but dnf doesn't have such a feature yet - I also don't expect a normal end user to resort to yum shell. Do the different fedora-release-* packages have to conflict? Can't I be running a workstation product and a server product and miscellaneous bits (a union, rather than the current apparent mutual exclusion)? This must've been discussed before, I just can't find the discussion. -- Thanks, Regards, Ankur Sinha signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
Fedora Workstation -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Announcing the release of Fedora 21 Beta!
On 05.11.2014 10:00, Adam Williamson wrote: On Wed, 2014-11-05 at 03:32 -0500, Joerg Lechner wrote: Hi, this link http://fedoraproject.org/get-prerelease i.e. for F21 Workstation Beta points still to ttp://download.fedoraproject.org/pub/fedora/linux/releases/test/21-Beta/Workstation/x86_64/iso/Fedora-Live-Workstation-x86_64-21_Beta-4.iso Kind Regards Well...why wouldn't it? That's the right link... ttp:// == totally trashed protocol? :) -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
On 05.11.2014 11:11, poma wrote: Fedora Workstation or maybe not ... a reliable, user-friendly and powerful operating system for laptops and PC hardware. http://fedoraproject.org/wiki/Workstation So yum is offering a whole system to install inside already system installed, not a desktop, environment or group? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20141105 changes
Compose started at Wed Nov 5 05:15:03 UTC 2014 Broken deps for i386 -- [3Depict] 3Depict-0.0.16-3.fc22.i686 requires libmgl.so.7.2.0 [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [audtty] audtty-0.1.12-9.fc20.i686 requires libaudclient.so.2 [authhub] authhub-0.1.2-3.fc19.i686 requires libjson.so.0 [cab] cab-0.1.9-12.fc22.i686 requires cabal-dev [collectd] collectd-onewire-5.4.1-10.fc22.i686 requires libowcapi-2.9.so.7 [condor] condor-plumage-8.1.4-7.a1a7df5.fc22.i686 requires libmongoclient.so [deltacloud-core] deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudservers) deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudfiles) [django-recaptcha] django-recaptcha-0.1-7.20091212svn6.fc21.noarch requires python-django14 [dnssec-check] dnssec-check-1.14.0.1-4.fc20.i686 requires libval-threads.so.14 dnssec-check-1.14.0.1-4.fc20.i686 requires libsres.so.14 [dragonegg] dragonegg-3.4-0.3.rc0.fc21.i686 requires libLLVM-3.4.so dragonegg-3.4-0.3.rc0.fc21.i686 requires gcc = 0:4.8.2-14.fc21 [edelib] edelib-2.1-5.fc22.i686 requires libedelib.so edelib-devel-2.1-5.fc22.i686 requires libedelib.so [fatrat] 1:fatrat-1.2.0-0.21.beta2.fc22.i686 requires libtorrent-rasterbar.so.7 [flush] flush-0.9.12-10.fc22.i686 requires libtorrent-rasterbar.so.7 [gdesklet-SlideShow] gdesklet-SlideShow-0.9-16.fc21.noarch requires gdesklets [gdesklets-citation] gdesklets-citation-2.0-3.20120702git355e2ee.fc19.noarch requires gdesklets [gedit-valencia] gedit-valencia-0.4.0-1.20131223git94442bf.fc21.i686 requires libvala-0.24.so.0 [ghc-hjsmin] ghc-hjsmin-0.1.4.7-3.fc22.i686 requires libHSoptparse-applicative-0.9.0-ghc7.6.3.so [glances] glances-2.1.2-2.fc22.noarch requires python-psutil = 0:2.0.0 [gofer] ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) = 0:0.16.0 [iwhd] iwhd-1.6-11.fc22.i686 requires libmongoclient.so [juffed] juffed-plugin-terminal-0.10-10.fc22.i686 requires libqtermwidget.so.0 [kmid2] kmid2-2.4.0-7.fc22.i686 requires libdrumstick-file.so.0 kmid2-2.4.0-7.fc22.i686 requires libdrumstick-alsa.so.0 [leiningen] leiningen-1.7.1-7.fc20.noarch requires maven-ant-tasks leiningen-1.7.1-7.fc20.noarch requires classworlds [libghemical] libghemical-2.99.1-24.fc20.i686 requires libf77blas.so.3 libghemical-2.99.1-24.fc20.i686 requires libatlas.so.3 [libopensync-plugin-irmc] 1:libopensync-plugin-irmc-0.22-7.fc20.i686 requires libopenobex.so.1 [ltsp] ltsp-client-5.4.5-8.fc21.i686 requires fuse-unionfs ltsp-server-5.4.5-8.fc21.i686 requires cdialog [meshmagick] meshmagick-0.6.0-20.svn2898.fc21.i686 requires libOgreMain.so.1.8.1 meshmagick-libs-0.6.0-20.svn2898.fc21.i686 requires libOgreMain.so.1.8.1 [monodevelop-vala] monodevelop-vala-2.8.8.1-6.fc21.i686 requires vala 0:0.25.0 [netdisco] netdisco-1.1-7.fc21.noarch requires perl(SNMP::Info::Layer2::Bay) [nfs-utils] 1:nfs-utils-1.3.1-2.0.fc22.i686 requires libnfsidmap.so.0(V_0.26) [nwchem] nwchem-openmpi-6.3.2-11.fc21.i686 requires libmpi_usempi.so.1 [odb] odb-2.3.0-6.fc22.i686 requires gcc = 0:4.9.1 [openshift-origin-msg-node-mcollective] openshift-origin-msg-node-mcollective-1.18.0.1-2.fc21.noarch requires openshift-origin-msg-common [openslides] openslides-1.3.1-3.fc21.noarch requires python-django 0:1.5 [openvas-client] openvas-client-3.0.3-8.fc20.i686 requires libopenvas_omp.so.6 openvas-client-3.0.3-8.fc20.i686 requires libopenvas_nasl.so.6 openvas-client-3.0.3-8.fc20.i686 requires libopenvas_misc.so.6 openvas-client-3.0.3-8.fc20.i686 requires libopenvas_hg.so.6 openvas-client-3.0.3-8.fc20.i686 requires libopenvas_base.so.6 [perl-RT-Authen-ExternalAuth] perl-RT-Authen-ExternalAuth-0.11-5.fc21.noarch requires rt3 perl-RT-Authen-ExternalAuth-0.11-5.fc21.noarch requires perl(:MODULE_COMPAT_5.18.2) [perl-RT-Extension-CommandByMail] perl-RT-Extension-CommandByMail-0.07-10.fc21.noarch requires perl(RT::Interface::Email) perl-RT-Extension-CommandByMail-0.07-10.fc21.noarch requires perl(:MODULE_COMPAT_5.18.2) [pipelight-selinux] pipelight-selinux-0.2.1-2.fc22.noarch requires pipelight-common pipelight-selinux-0.2.1-2.fc22.noarch requires pipelight-common pipelight-selinux-0.2.1-2.fc22.noarch requires pipelight pipelight-selinux-0.2.1-2.fc22.noarch requires pipelight [pootle] pootle-2.1.6-8.fc21.noarch requires python-django14 [python-askbot-fedmsg] python-askbot-fedmsg-0.1.0-2.fc21.noarch requires askbot [python-coffin] python-coffin-0.3.7-3.fc21.noarch requires python-django14
F-21 Branched report: 20141105 changes
Compose started at Wed Nov 5 07:15:02 UTC 2014 Broken deps for armhfp -- [PyQuante] PyQuante-libint-1.6.4-11.fc21.1.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 [audtty] audtty-0.1.12-9.fc20.armv7hl requires libaudclient.so.2 [authhub] authhub-0.1.2-3.fc19.armv7hl requires libjson.so.0 [avro] avro-mapred-1.7.5-9.fc21.noarch requires hadoop-mapreduce avro-mapred-1.7.5-9.fc21.noarch requires hadoop-client [blender] 1:blender-2.72b-1.fc21.armv7hl requires libOpenCOLLADAStreamWriter.so.0.1 1:blender-2.72b-1.fc21.armv7hl requires libOpenCOLLADASaxFrameworkLoader.so.0.1 1:blender-2.72b-1.fc21.armv7hl requires libOpenCOLLADAFramework.so.0.1 1:blender-2.72b-1.fc21.armv7hl requires libOpenCOLLADABaseUtils.so.0.1 1:blender-2.72b-1.fc21.armv7hl requires libMathMLSolver.so.0.1 1:blender-2.72b-1.fc21.armv7hl requires libGeneratedSaxParser.so.0.1 1:blenderplayer-2.72b-1.fc21.armv7hl requires libOpenCOLLADAStreamWriter.so.0.1 1:blenderplayer-2.72b-1.fc21.armv7hl requires libOpenCOLLADASaxFrameworkLoader.so.0.1 1:blenderplayer-2.72b-1.fc21.armv7hl requires libOpenCOLLADAFramework.so.0.1 1:blenderplayer-2.72b-1.fc21.armv7hl requires libOpenCOLLADABaseUtils.so.0.1 1:blenderplayer-2.72b-1.fc21.armv7hl requires libMathMLSolver.so.0.1 1:blenderplayer-2.72b-1.fc21.armv7hl requires libGeneratedSaxParser.so.0.1 [cduce] cduce-0.5.5-9.fc21.armv7hl requires ocaml(Camlp4) = 0:ebd368022fd2bc7b305a42902efa4c90 [deltacloud-core] deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudservers) deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudfiles) [django-recaptcha] django-recaptcha-0.1-7.20091212svn6.fc21.noarch requires python-django14 [dragonegg] dragonegg-3.4-0.3.rc0.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 [edelib] edelib-2.1-5.fc21.armv7hl requires libedelib.so edelib-devel-2.1-5.fc21.armv7hl requires libedelib.so [fatrat] 1:fatrat-1.2.0-0.21.beta2.fc21.armv7hl requires libtorrent-rasterbar.so.7 [flush] flush-0.9.12-10.fc21.armv7hl requires libtorrent-rasterbar.so.7 [gdesklet-SlideShow] gdesklet-SlideShow-0.9-16.fc21.noarch requires gdesklets [gdesklets-citation] gdesklets-citation-2.0-3.20120702git355e2ee.fc19.noarch requires gdesklets [gedit-valencia] gedit-valencia-0.4.0-1.20131223git94442bf.fc21.armv7hl requires libvala-0.24.so.0 [gofer] ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) = 0:0.16.0 [golang-github-influxdb-influxdb] golang-github-influxdb-influxdb-datastore-0.8.0-0.3.rc4.git67f9869.fc21.noarch requires golang(github.com/jmhodges/levigo) golang-github-influxdb-influxdb-datastore-0.8.0-0.3.rc4.git67f9869.fc21.noarch requires golang(code.google.com/p/log4go) golang-github-influxdb-influxdb-devel-0.8.0-0.3.rc4.git67f9869.fc21.noarch requires golang(github.com/jmhodges/levigo) golang-github-influxdb-influxdb-devel-0.8.0-0.3.rc4.git67f9869.fc21.noarch requires golang(github.com/influxdb/go-cache) golang-github-influxdb-influxdb-devel-0.8.0-0.3.rc4.git67f9869.fc21.noarch requires golang(github.com/bmizerany/pat) golang-github-influxdb-influxdb-devel-0.8.0-0.3.rc4.git67f9869.fc21.noarch requires golang(code.google.com/p/log4go) [gorm] gorm-1.2.18-5.fc20.armv7hl requires libgnustep-gui.so.0.23 [leiningen] leiningen-1.7.1-7.fc20.noarch requires maven-ant-tasks leiningen-1.7.1-7.fc20.noarch requires classworlds [libghemical] libghemical-2.99.1-24.fc20.armv7hl requires libf77blas.so.3 libghemical-2.99.1-24.fc20.armv7hl requires libatlas.so.3 [libopensync-plugin-irmc] 1:libopensync-plugin-irmc-0.22-7.fc20.armv7hl requires libopenobex.so.1 [ltsp] ltsp-client-5.4.5-8.fc21.armv7hl requires fuse-unionfs ltsp-server-5.4.5-8.fc21.armv7hl requires cdialog [meshmagick] meshmagick-0.6.0-20.svn2898.fc21.armv7hl requires libOgreMain.so.1.8.1 meshmagick-libs-0.6.0-20.svn2898.fc21.armv7hl requires libOgreMain.so.1.8.1 [monodevelop-vala] monodevelop-vala-2.8.8.1-6.fc21.armv7hl requires vala 0:0.25.0 [netdisco] netdisco-1.1-7.fc21.noarch requires perl(SNMP::Info::Layer2::Bay) [ocaml-pa-do] ocaml-pa-do-0.8.16-3.fc21.armv7hl requires ocaml(Camlp4) = 0:ebd368022fd2bc7b305a42902efa4c90 [openslides] openslides-1.3.1-3.fc21.noarch requires python-django 0:1.5 [openstack-nova] openstack-nova-compute-2014.1.2-1.fc21.noarch requires libvirt-daemon-xen [openvas-client] openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_omp.so.6 openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_nasl.so.6 openvas-client-3.0.3-8.fc20.armv7hl requires libopenvas_misc.so.6
Re: Announcing the release of Fedora 21 Beta!
Hi, if I click to this link (http://fedoraproject.org/get-prerelease#workstation) I still get workstation Beta-TC4 (1.3GB)( http://download.fedoraproject.org/pub/fedora/linux/releases/test/21-Beta/Workstation/x86_64/iso/Fedora-Live-Workstation-x86_64-21_Beta-4.iso) and not prerelease (1.4GB). Kind Regards. -Ursprüngliche Mitteilung- Von: Adam Williamson adamw...@fedoraproject.org An: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Verschickt: Mi, 5 Nov 2014 10:00 am Betreff: Re: Announcing the release of Fedora 21 Beta! On Wed, 2014-11-05 at 03:32 -0500, Joerg Lechner wrote: Hi, this link http://fedoraproject.org/get-prerelease i.e. for F21 Workstation Beta points still to ttp://download.fedoraproject.org/pub/fedora/linux/releases/test/21-Beta/Workstation/x86_64/iso/Fedora-Live-Workstation-x86_64-21_Beta-4.iso Kind Regards Well...why wouldn't it? That's the right link... -- 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: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Announcing the release of Fedora 21 Beta!
Hi, what is confusing is that F21-Final-TC1 has 1.4GB and the download link for prerelease says: Download now! 1.4GB, ISO format image for 64bit-compatible PC Therefore I don't know, the 1.3GB build beta RC4 or the 1.4GB build beta final TC1 is the prerelease build. Anyway for me no problem I use always the newest build to look at. Kind Regards -Ursprüngliche Mitteilung- Von: Adam Williamson adamw...@fedoraproject.org An: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Verschickt: Mi, 5 Nov 2014 10:00 am Betreff: Re: Announcing the release of Fedora 21 Beta! On Wed, 2014-11-05 at 03:32 -0500, Joerg Lechner wrote: Hi, this link http://fedoraproject.org/get-prerelease i.e. for F21 Workstation Beta points still to ttp://download.fedoraproject.org/pub/fedora/linux/releases/test/21-Beta/Workstation/x86_64/iso/Fedora-Live-Workstation-x86_64-21_Beta-4.iso Kind Regards Well...why wouldn't it? That's the right link... -- 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: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
On 05.11.2014 11:25, poma wrote: On 05.11.2014 11:11, poma wrote: Fedora Workstation or maybe not ... a reliable, user-friendly and powerful operating system for laptops and PC hardware. http://fedoraproject.org/wiki/Workstation So yum is offering a whole system to install inside already system installed, not a desktop, environment or group? Got it, this seems like a different upgrade form of yum dist upgrade for, well for something I guess. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Shouldn't this work?
On Tue, 04 Nov 2014 11:10:04 -0800 Adam Williamson wrote: I thought I read that support for Maxwell (I think its maxwell :-) was in the latest nouveau and mesa. Is the latest not in f21? Is it a bug that it doesn't work? (I just get a black screen on my UHD monitor with display port cable). mesa isn't going to affect basic console output. The key thing there is mostly the code that's in the kernel, certainly not mesa and probably not the DDX. F21 has kernel 3.17. Well, I managed to boot in multiuser mode, and found a failed to load fuc409c nvidia firmware message in dmesg, so I submitted a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1160706 If it is missing firmware, maybe nouveau isn't packaged correctly? I certainly have no idea :-). -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fwd: F21 nm-openvpn and md5
I've tried to add the environment variable as you described below, but it still does not work. In a virtual machine with F20 I updated the F20 openssl-1.0.1e-40.fc20 to openssl-1.0.1e-40.fc21. After the update I get the error as expected. But after adding Environment=OPENSSL_ENABLE_MD5_VERIFY=1 to /usr/lib/systemd/system/NetworkManager.service the openvpn connection started to work. The same change under F21 does not help, I still get the error. Zoltan On Wed, Nov 5, 2014 at 7:53 AM, poma pomidorabelis...@gmail.com wrote: On 04.11.2014 22:57, Zoltan Kota wrote: Hi, With F21 on, openssl has been patched to disallow verification of certificates that are signed with MD5 algorithm. Until I get our sysadmins generate new keys I should use the workaround described as: a temporary measure the OPENSSL_ENABLE_MD5_VERIFY environment variable can be set to allow verification of certificates signed with MD5 algorithm. On my pre-F21 (test)machine I use gnome with Networkmanager(-openvpn). How can I add the above environment variable for Networkmanager? [openssl] disable verification of certificate, CRL, and OCSP signatures using MD5 https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-2013/1144043.html Chapter 28. Networking https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.0_Release_Notes/Known-Issues-Networking.html openssl component, BZ#1062656 It is not possible to connect to any Wi-Fi Protected Access (WPA) Enterprise Access Point (AP) that requires MD5-signed certificates. To work around this problem, copy the wpa_supplicant.service file from the /usr/lib/systemd/system/ directory to the /etc/systemd/system/ directory and add the following line to the Service section of the file: Environment=OPENSSL_ENABLE_MD5_VERIFY Then run the systemctl daemon-reload command as root to reload the service file. Important Note that MD5 certificates are highly insecure and Red Hat does not recommend using them. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Announcing the release of Fedora 21 Beta!
On Wed, Nov 05, 2014 at 07:26:55AM -0500, Joerg Lechner wrote: what is confusing is that F21-Final-TC1 has 1.4GB and the download link for prerelease says: Download now! 1.4GB, ISO format image for 64bit-compatible PC Therefore I don't know, the 1.3GB build beta RC4 or the 1.4GB build beta final TC1 is the prerelease build. Anyway for me no problem I use always the newest build to look at. RC comes after TC, and TCs can never be the release. That said, I see your concern. Awesomely, whether it is 1.3G or 1.4G is somewhat ambiguous. Storage is usually measured with _decimal_ prefixes, so 1410334720 ÷ 10⁹ is 1.41G. This includes DVD and Blu-Ray media, so there's some logic in using it. Of course, may other things in computing are measured with binary prefixes, so a 1410334720 ÷ 2³⁰ = 1.31GiB, which is probably what your browser is telling you (although also probably not with the for-nerds-only GiB prefix). -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Fwd: F21 nm-openvpn and md5
On 05.11.2014 14:55, Zoltan Kota wrote: I've tried to add the environment variable as you described below, but it still does not work. Quote, not description. :) Send sysadmins chocolates and flowers. In a virtual machine with F20 I updated the F20 openssl-1.0.1e-40.fc20 to openssl-1.0.1e-40.fc21. After the update I get the error as expected. But after adding Environment=OPENSSL_ENABLE_MD5_VERIFY=1 to /usr/lib/systemd/system/NetworkManager.service the openvpn connection started to work. The same change under F21 does not help, I still get the error. Zoltan On Wed, Nov 5, 2014 at 7:53 AM, poma pomidorabelis...@gmail.com wrote: On 04.11.2014 22:57, Zoltan Kota wrote: Hi, With F21 on, openssl has been patched to disallow verification of certificates that are signed with MD5 algorithm. Until I get our sysadmins generate new keys I should use the workaround described as: a temporary measure the OPENSSL_ENABLE_MD5_VERIFY environment variable can be set to allow verification of certificates signed with MD5 algorithm. On my pre-F21 (test)machine I use gnome with Networkmanager(-openvpn). How can I add the above environment variable for Networkmanager? [openssl] disable verification of certificate, CRL, and OCSP signatures using MD5 https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-2013/1144043.html Chapter 28. Networking https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.0_Release_Notes/Known-Issues-Networking.html openssl component, BZ#1062656 It is not possible to connect to any Wi-Fi Protected Access (WPA) Enterprise Access Point (AP) that requires MD5-signed certificates. To work around this problem, copy the wpa_supplicant.service file from the /usr/lib/systemd/system/ directory to the /etc/systemd/system/ directory and add the following line to the Service section of the file: Environment=OPENSSL_ENABLE_MD5_VERIFY Then run the systemctl daemon-reload command as root to reload the service file. Important Note that MD5 certificates are highly insecure and Red Hat does not recommend using them. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F21 Beta: Fantastic
Hi Gents, I have updated my Fedora Installations to F21 Beta and must express my thanks to all. This is easily the best Fedora release I ever have installed. - Anaconda is well structured - It's blazing fast. Did somebody did some magic on the graphics stack ? - It's booting very fast. - Gnome did fix the user interface problems and is very usable - IPv6 does work out of the box - my M-Audio Fast Track Ultra did work out of the box, this always needed some work in Alsa and Pulseaudio before. - Docked and closed laptops show the login screen on the external display ... This will be a fantastic release ! cu romal -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Announcing the release of Fedora 21 Beta!
On 06/11/14 03:57, Matthew Miller wrote: On Wed, Nov 05, 2014 at 07:26:55AM -0500, Joerg Lechner wrote: what is confusing is that F21-Final-TC1 has 1.4GB and the download link for prerelease says: Download now! 1.4GB, ISO format image for 64bit-compatible PC Therefore I don't know, the 1.3GB build beta RC4 or the 1.4GB build beta final TC1 is the prerelease build. Anyway for me no problem I use always the newest build to look at. RC comes after TC, and TCs can never be the release. That said, I see your concern. Awesomely, whether it is 1.3G or 1.4G is somewhat ambiguous. Storage is usually measured with _decimal_ prefixes, so 1410334720 ÷ 10⁹ is 1.41G. This includes DVD and Blu-Ray media, so there's some logic in using it. Of course, may other things in computing are measured with binary prefixes, so a 1410334720 ÷ 2³⁰ = 1.31GiB, which is probably what your browser is telling you (although also probably not with the for-nerds-only GiB prefix). I tend to think that all reporting of bytes should be in powers of 2. So RAM and other storage should be in units of 1024*n. Therefore reporting disk space in powers of 10 is essentially cheating, and at best misleading. Also always using powers of 2 would be a lot more consistent. But hey, I've only been programming since 1968, so what is my opinion worth! :-) Cheers, Gavin Cheers, Gavin -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
On 11/05/2014 12:35 AM, Ed Greshko wrote: On 10/26/14 11:06, Adam Williamson wrote: On Sun, 2014-10-26 at 10:51 +0800, Ed Greshko wrote: On 10/26/14 10:48, Adam Williamson wrote: On Sun, 2014-10-26 at 10:44 +0800, Ed Greshko wrote: On 10/26/14 10:40, Adam Williamson wrote: On Sun, 2014-10-26 at 10:20 +0800, Ed Greshko wrote: After doing a KDE install from the Fedora-Server-netinst-x86_64-21_Beta ISO I wanted to add GNOME to the mix. In the past, even on B-TC4 I believe, I simply did yum groupinstall GNOME Desktop. However, now that choice no longer exists when doing yum grouplist. Try 'yum install @^gnome-desktop-environment'. [root@localhost ~]# yum install @^gnome-desktop-environment Loaded plugins: langpacks Group gnome-desktop-environment does not exist. Error: Nothing to do huh, i see it in comps. maybe someone removed it since my last checkout? Will you follow up or does a bugzilla of some sort need to be created? It's not necessarily a bug. It wants more looking into, but I'm not gonna do it tonight. Still can't find a way to install the GNOME desktop after doing a KDE install. Using the latest, and greatest, Beta just released. This could be very annoying to some people. :-) OK, try some of the following: yum -v group list which should list the groups available. yum -v group info workstation-product-environment which shows workstation-product and finally yum -v info workstation-product which shows all of the packages for workstation-product (which is what I belive you are looking for). Gene -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
On 11/06/14 06:00, Gene Czarcinski wrote: OK, try some of the following: yum -v group list which should list the groups available. yum -v group info workstation-product-environment which shows workstation-product and finally yum -v info workstation-product which shows all of the packages for workstation-product (which is what I belive you are looking for). What I am asking is, what I am looking for is, how to install GNOME after an fresh install of F21 with KDE. In previous versions of Fedora the command yum group list returned a list including GNOME Desktop (gnome-desktop-environment) And one would simply invoke . yum groupinstall 'GNOME Desktop' or gnome-desktop-environment and the needful and you were done. Now in F21 you don't get that You get (as I've now written more than once) Available environment groups: Fedora Server Fedora Cloud Server Fedora Workstation KDE Plasma Workspaces Xfce Desktop LXDE Desktop Cinnamon Desktop MATE Desktop Sugar Desktop Environment Development and Creative Workstation Web Server Infrastructure Server Basic Desktop Minimal Install And one can quickly notice GNOME Desktop (gnome-desktop-environment) is nowhere to be seen And, as previously written as well, one could type yum group install Fedora Workstation thinking that would get them GNOME but they will be greeted with -- Finished Dependency Resolution Error: fedora-release-nonproduct conflicts with fedora-release-workstation-21-0.16.noarch Error: firewalld-config-standard conflicts with fedora-release-workstation-21-0.16.noarch Error: firewalld-config-workstation conflicts with firewalld-config-standard-0.3.12-1.fc21.noarch Error: fedora-release-workstation conflicts with fedora-release-nonproduct-21-0.16.noarch Error: firewalld-config-standard conflicts with firewalld-config-workstation-0.3.12-1.fc21.noarch You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest So. There seems to be no easy way to install GNOME. I hope nobody is suggesting that everyone has to discover what packages are in workstation-product and then pick and choose and eventually get a GNOME environment. -- If you can't laugh at yourself, others will gladly oblige. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
One Desktop and one Desktop ONLY.
Sorry to start yet another thread on the same issue But I only just now discover that once you install Fedora Workstation you can't install another desktop yum group install LXDE Desktop gets you -- Finished Dependency Resolution Error: fedora-release-workstation conflicts with fedora-release-nonproduct-21-0.16.noarch Error: fedora-release-nonproduct conflicts with fedora-release-workstation-21-0.16.noarch You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest yum group install KDE Plasma Workspaces gets you the same thing As does any yum group install your desired desktop -- If you can't laugh at yourself, others will gladly oblige. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
On 11/05/2014 02:00 PM, Gene Czarcinski wrote: On 11/05/2014 12:35 AM, Ed Greshko wrote: On 10/26/14 11:06, Adam Williamson wrote: On Sun, 2014-10-26 at 10:51 +0800, Ed Greshko wrote: On 10/26/14 10:48, Adam Williamson wrote: On Sun, 2014-10-26 at 10:44 +0800, Ed Greshko wrote: On 10/26/14 10:40, Adam Williamson wrote: On Sun, 2014-10-26 at 10:20 +0800, Ed Greshko wrote: After doing a KDE install from the Fedora-Server-netinst-x86_64-21_Beta ISO I wanted to add GNOME to the mix. In the past, even on B-TC4 I believe, I simply did yum groupinstall GNOME Desktop. However, now that choice no longer exists when doing yum grouplist. Try 'yum install @^gnome-desktop-environment'. [root@localhost ~]# yum install @^gnome-desktop-environment Loaded plugins: langpacks Group gnome-desktop-environment does not exist. Error: Nothing to do huh, i see it in comps. maybe someone removed it since my last checkout? Will you follow up or does a bugzilla of some sort need to be created? It's not necessarily a bug. It wants more looking into, but I'm not gonna do it tonight. Still can't find a way to install the GNOME desktop after doing a KDE install. Using the latest, and greatest, Beta just released. This could be very annoying to some people. :-) OK, try some of the following: yum -v group list which should list the groups available. yum -v group info workstation-product-environment which shows workstation-product and finally yum -v info workstation-product which shows all of the packages for workstation-product (which is what I belive you are looking for). Gene This is listed under available groups on my fed21 system: gnome-desktop Available environment groups: Basic Desktop (basic-desktop-environment) Cinnamon Desktop (cinnamon-desktop-environment) Development and Creative Workstation (developer-workstation-environment) Fedora Cloud Server (cloud-server-environment) Fedora Server (server-product-environment) Fedora Workstation (workstation-product-environment) Infrastructure Server (infrastructure-server-environment) KDE Plasma Workspaces (kde-desktop-environment) LXDE Desktop (lxde-desktop-environment) MATE Desktop (mate-desktop-environment) Minimal Install (minimal-environment) Sugar Desktop Environment (sugar-desktop-environment) Web Server (web-server-environment) Xfce Desktop (xfce-desktop-environment) Installed groups: Administration Tools (admin-tools) Audio Production (audio) Authoring and Publishing (authoring-and-publishing) Books and Guides (books) C Development Tools and Libraries (c-development) Container Management (container-management) D Development Tools and Libraries (d-development) Design Suite (design-suite) Development Tools (development-tools) Editors (editors) Educational Software (education) Engineering and Scientific (engineering-and-scientific) Fedora Eclipse (eclipse) GNOME Desktop Environment (gnome-desktop) Games and Entertainment (games) Graphical Internet (graphical-internet) LibreOffice (libreoffice) Office/Productivity (office) Sound and Video (sound-and-video) System Tools (system-tools) Text-based Internet (text-internet) Window Managers (window-managers) Available groups: 3D Printing (3d-printing) Cloud Infrastructure (cloud-infrastructure) Cloud Management Tools (cloud-management) Cloud Server Tools (cloud-server) Domain Membership (domain-client) Electronic Lab (electronic-lab) FreeIPA Server (freeipa-server) Hardware Support (hardware-support) Headless Management (headless-management) KDE (K Desktop Environment) (kde-desktop) MATE Applications (mate-applications) MATE COMPIZ (mate-compiz) Medical Applications (medical) Milkymist (milkymist) Network Servers (network-server) RPM Development Tools (rpm-development-tools) Robotics (robotics-suite) Security Lab (security-lab) dnf group install gnome-desktop Reynold -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
On 11/06/14 06:44, Reynold wrote: On 11/05/2014 02:00 PM, Gene Czarcinski wrote: On 11/05/2014 12:35 AM, Ed Greshko wrote: On 10/26/14 11:06, Adam Williamson wrote: On Sun, 2014-10-26 at 10:51 +0800, Ed Greshko wrote: On 10/26/14 10:48, Adam Williamson wrote: On Sun, 2014-10-26 at 10:44 +0800, Ed Greshko wrote: On 10/26/14 10:40, Adam Williamson wrote: On Sun, 2014-10-26 at 10:20 +0800, Ed Greshko wrote: After doing a KDE install from the Fedora-Server-netinst-x86_64-21_Beta ISO I wanted to add GNOME to the mix. In the past, even on B-TC4 I believe, I simply did yum groupinstall GNOME Desktop. However, now that choice no longer exists when doing yum grouplist. Try 'yum install @^gnome-desktop-environment'. [root@localhost ~]# yum install @^gnome-desktop-environment Loaded plugins: langpacks Group gnome-desktop-environment does not exist. Error: Nothing to do huh, i see it in comps. maybe someone removed it since my last checkout? Will you follow up or does a bugzilla of some sort need to be created? It's not necessarily a bug. It wants more looking into, but I'm not gonna do it tonight. Still can't find a way to install the GNOME desktop after doing a KDE install. Using the latest, and greatest, Beta just released. This could be very annoying to some people. :-) OK, try some of the following: yum -v group list which should list the groups available. yum -v group info workstation-product-environment which shows workstation-product and finally yum -v info workstation-product which shows all of the packages for workstation-product (which is what I belive you are looking for). Gene This is listed under available groups on my fed21 system: gnome-desktop Available environment groups: Basic Desktop (basic-desktop-environment) Cinnamon Desktop (cinnamon-desktop-environment) Development and Creative Workstation (developer-workstation-environment) Fedora Cloud Server (cloud-server-environment) Fedora Server (server-product-environment) Fedora Workstation (workstation-product-environment) Infrastructure Server (infrastructure-server-environment) KDE Plasma Workspaces (kde-desktop-environment) LXDE Desktop (lxde-desktop-environment) MATE Desktop (mate-desktop-environment) Minimal Install (minimal-environment) Sugar Desktop Environment (sugar-desktop-environment) Web Server (web-server-environment) Xfce Desktop (xfce-desktop-environment) Installed groups: Administration Tools (admin-tools) Audio Production (audio) Authoring and Publishing (authoring-and-publishing) Books and Guides (books) C Development Tools and Libraries (c-development) Container Management (container-management) D Development Tools and Libraries (d-development) Design Suite (design-suite) Development Tools (development-tools) Editors (editors) Educational Software (education) Engineering and Scientific (engineering-and-scientific) Fedora Eclipse (eclipse) GNOME Desktop Environment (gnome-desktop) Games and Entertainment (games) Graphical Internet (graphical-internet) LibreOffice (libreoffice) Office/Productivity (office) Sound and Video (sound-and-video) System Tools (system-tools) Text-based Internet (text-internet) Window Managers (window-managers) Available groups: 3D Printing (3d-printing) Cloud Infrastructure (cloud-infrastructure) Cloud Management Tools (cloud-management) Cloud Server Tools (cloud-server) Domain Membership (domain-client) Electronic Lab (electronic-lab) FreeIPA Server (freeipa-server) Hardware Support (hardware-support) Headless Management (headless-management) KDE (K Desktop Environment) (kde-desktop) MATE Applications (mate-applications) MATE COMPIZ (mate-compiz) Medical Applications (medical) Milkymist (milkymist) Network Servers (network-server) RPM Development Tools (rpm-development-tools) Robotics (robotics-suite) Security Lab (security-lab) dnf group install gnome-desktop Reynold Well [root@localhost ~]# dnf group list Available environment groups: Basic Desktop Cinnamon Desktop Development and Creative Workstation Fedora Cloud Server Fedora Server Fedora Workstation Infrastructure Server KDE Plasma Workspaces LXDE Desktop MATE Desktop Minimal Install Sugar Desktop Environment Web Server Xfce Desktop Available groups: 3D Printing Administration Tools Audio Production Authoring and Publishing Books and Guides C Development Tools and Libraries Cloud Infrastructure Cloud Management Tools Cloud Server Tools Container Management D Development Tools and Libraries Design Suite Development Tools Domain Membership Editors Educational Software Electronic Lab Engineering and Scientific Fedora Eclipse FreeIPA Server Games and
Re: Adding GNOME ....
What is the advantage of using dnf instead of yum ? Adrian Fewster -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
On 11/06/14 07:06, Adrian wrote: What is the advantage of using dnf instead of yum ? None yum group install gnome-desktop Would have worked just as well The *problem* however is finding this out when a list of the groups doesn't show it in either yum or dnf. -- If you can't laugh at yourself, others will gladly oblige. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
On 11/5/2014 3:10 PM, Ed Greshko wrote: On 11/06/14 07:06, Adrian wrote: What is the advantage of using dnf instead of yum ? This command works with f21-live-workstation Beta_FinalTC-1 x86_64 DVDHD install (with yum update run first) yum install @sugar-desktop @KDE-desktop None yum group install gnome-desktop Would have worked just as well The *problem* however is finding this out when a list of the groups doesn't show it in either yum or dnf. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
Ok, I went from the Gnome desktop in workstation to KDE, with |yum groupinstallKDE Plasma Workspaces| with no issue. I installed the rc4 just before official beta release. [root@fedora21desk yum.repos.d]# cat fedora-updates.repo [updates] name=Fedora $releasever - $basearch - Updates failovermethod=priority #baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/ metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-f$releaseverarch=$basearch enabled=1 metadata_expire=6h gpgcheck=1 metadata_expire=6h gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch skip_if_unavailable=False [updates-debuginfo] name=Fedora $releasever - $basearch - Updates - Debug failovermethod=priority #baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/debug/ metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-debug-f$releaseverarch=$basearch enabled=0 gpgcheck=1 metadata_expire=6h gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch skip_if_unavailable=False [updates-source] name=Fedora $releasever - Updates Source failovermethod=priority #baseurl=http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/SRPMS/ metalink=https://mirrors.fedoraproject.org/metalink?repo=updates-released-source-f$releaseverarch=$basearch enabled=0 gpgcheck=1 metadata_expire=6h gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$releasever-$basearch skip_if_unavailable=False [root@fedora21desk yum.repos.d]# So I understand I will keep updating, and the system will become 'final release' when that happens auto with updates, or is anything else needed ? I really like what I see so far, it feels like a release not a beta I am using. Adrian ... vk4tux -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
On 11/06/14 07:34, Thomas Gilliard wrote: On 11/5/2014 3:10 PM, Ed Greshko wrote: On 11/06/14 07:06, Adrian wrote: What is the advantage of using dnf instead of yum ? This command works with f21-live-workstation Beta_FinalTC-1 x86_64 DVDHD install (with yum update run first) yum install @sugar-desktop @KDE-desktop Great, that works since it doesn't pull in fedora-release-nonproduct but yum groupinstall KDE Plasma Workspaces fails since it does Shouldn't we have some consistency? None yum group install gnome-desktop Would have worked just as well The *problem* however is finding this out when a list of the groups doesn't show it in either yum or dnf. -- If you can't laugh at yourself, others will gladly oblige. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Adding GNOME ....
On Thu, 2014-11-06 at 07:10 +0800, Ed Greshko wrote: On 11/06/14 07:06, Adrian wrote: What is the advantage of using dnf instead of yum ? None yum group install gnome-desktop Would have worked just as well The *problem* however is finding this out when a list of the groups doesn't show it in either yum or dnf. It's not a user-visible group. The comps groups are kind of a bit of a mess now; no-one has overall responsibility for them and they've just been sort of poked ad hoc to get the 'Product'ization stuff looking right, one issue at a time. It's easy enough to go straight to the source to see what's actually going on - just clone comps git: git clone https://git.fedorahosted.org/git/comps.git and look at 'comps-f21.xml.in'. The groups are listed there, in a fairly clear format. group entries are the things yum calls groups. environment entries are the things yum calls environment groups. Groups can be marked 'uservisible' or not. Groups that are marked 'uservisible' appear in yum / dnf 'grouplist'. Environment groups appear on the left hand side of anaconda's package selection screen, and in yum / dnf 'grouplist'. Environment groups must have a grouplist section. These are the package groups that will always be installed as a part of that environment group. Environment groups can have a optionlist section. This contains regular 'groups'. groups listed as part of an environment group's 'option list' are the ones that appear at the top of the list on the right hand side of anaconda's package selection screen *only when that environment group is selected*. Groups that are marked 'uservisible' but are not part of the currently-selected environment group's optionlist appear in the bottom section of that list (there's a small grey separator line), regardless of what environment is selected. Groups cannot contain other groups - so there's really just one level of nesting available, groups within environment groups. The comps system is really a bit too inflexible for our needs in a Product-ized world, because it's hard to make it properly cover both the case of install-time deployment and the case of post-install deployment. At install time, if you're deploying 'Workstation', we really need you to get the fedora-release-workstation package installed, so the 'workstation-product-environment' environment group contains the 'workstation-product' group, which includes the 'fedora-release-workstation' package. But that means you can't easily add it on to a KDE install, because the KDE install already has the fedora-release-nonproduct group. It's not trivial to work around this because it'd really require another layer of nesting or some other form of extra flexibility to cover all cases. As things stand, the 'gnome-desktop' group still exists but is not marked uservisible, so you can use that, but I'm not sure if its continued existence is something anyone's consciously planned or just a happenstance. The whole 'environment group' system was designed to back the newUI package selection UI design (AIUI), it wasn't really designed to back the whole Product system at all, and it seems no-one quite came up with a fully co-ordinated plan for how we'd do the comps groups and kickstarts for Products, it just sort of has been hacked together as we've gone along. Which is probably why it's all a little incoherent now. I think if we were just whiteboarding it from scratch we'd want to set things up so that the groups you could pick at the left-hand side of anaconda's UI would pull in the appropriate 'fedora-release-foo' package, while 'yum grouplist' would show you groups which would deploy the same set of actual packages for the desktop environment in question but would not pull in any particular 'fedora-release' package. I don't believe that's fully possible right now because you can't make environment groups visible in anaconda but not visible in yum. Environment groups don't have any kind of 'visibility' property - if they exist, they show up, both in anaconda and in yum. comps also has weird things called categorys down the bottom, which aren't used by anaconda or yum but are used by (IIRC) yumex. Bill, Stephen, Matt, Kalev - I think we could stand to take another look at this. I see two immediate issues: 1) Workstation is set up rather differently to the other desktop-y products/environments. There's rather an overlap between the 'workstation-product' group and the 'gnome-desktop' group. I'd sort of expect the 'workstation-product-environment' env group would include the 'gnome-desktop' group and then another group which pulled in the things that we want to add that make up the 'workstation product', perhaps? This is how the other desktop small-p products/environments work - kde-desktop-environment pulls in @kde-desktop (plus other package groups) and @fedora-release-nonproduct , xfce-desktop-environment pulls in @xfce-desktop and @fedora-release-nonproduct, etc. 2) We
Re: Adding GNOME ....
On Thu, 2014-11-06 at 07:48 +0800, Ed Greshko wrote: On 11/06/14 07:34, Thomas Gilliard wrote: On 11/5/2014 3:10 PM, Ed Greshko wrote: On 11/06/14 07:06, Adrian wrote: What is the advantage of using dnf instead of yum ? This command works with f21-live-workstation Beta_FinalTC-1 x86_64 DVDHD install (with yum update run first) yum install @sugar-desktop @KDE-desktop Great, that works since it doesn't pull in fedora-release-nonproduct but yum groupinstall KDE Plasma Workspaces fails since it does Shouldn't we have some consistency? They're two different groups. @kde-desktop is the package group: group idkde-desktop/id in comps-f21.xml.in. KDE Plasma Workspaces is the environment group: environment idkde-desktop-environment/id in comps-f21.xml.in. -- 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: https://admin.fedoraproject.org/mailman/listinfo/test
