gnome-boxes blocker bug, name resolution fails on first boot
by Chris Murphy
Please drop libvirt 'default' network dependency for F24 GA, disrupts
livecd networking
https://bugzilla.redhat.com/show_bug.cgi?id=1164492
This bug has been a blocker for previous releases, and has been
reopened and inherited the previous blocker status for Fedora 24.
QA is currently inclined to keep it accepted as a blocker bug. This
email is just a friendly reminder since the bug hasn't been updated by
the gnome-boxes maintainer and in case there's a change in opinion
about how to handle the problem.
Thanks,
--
Chris Murphy
6 years, 10 months
Graphical Upgrade Test Day conflicts
by Eric Griffith
Hey guys, I'm attempting to take part in the May 16 Test Day, but I'm
running into a slight problem with the Gnome320 copr. Fully up to date F23
Workstation system is giving me the following conflict during upgrade.
sudo dnf update gnome-software --best --allowerasing
Installing:
f24-backgrounds-base
noarch 24.1.1-1.fc23 rhughes-f23-gnome320
23 M
Upgrading:
gnome-software x86_64 3.20.3-0.191.20160425git.fc23 rhughes-f23-gnome320
3.3 M
json-glib x86_64 1.2.0-1.fc23 rhughes-f23-gnome320
137 k
libgusb x86_64 0.2.9-1.fc23 rhughes-f23-gnome320
46 k
Removing:
colord-libs i686 1.2.12-1.fc23 @fedora
534 k
gtk3 i686 3.18.9-1.fc23 @updates
17 M
json-glib i686 1.0.4-2.fc23 @fedora
457 k
libgusb i686 0.2.8-1.fc23 @updates
103 k
libnm-gtk i686 1.0.10-1.fc23 @updates
229 k
Specifically the "Lets remove gtk3" when I don't see anything from the copr
that would replace it.
The "problem package" is libgusb-0.2.9.1 from gnome320.
Thoughts on if this would be safe to do?
--Eric--
6 years, 10 months
Re: F25 Self Contained Change: Replace UDisks2 by Storaged
by Stephen Gallagher
On 04/14/2016 10:50 AM, Jan Kurik wrote:
> = Proposed Self Contained Change: Replace UDisks2 by Storaged =
> https://fedoraproject.org/wiki/Changes/Replace_UDisks2_by_Storaged
>
> Change owner(s):
> * Peter Hatina <phatina redhat com>
> * Tomáš Smetana <tsmetana redhat com >
>
> Storaged extends UDisks2 API by exporting several enterprise features
> (in form of plugins), such as LVM2 and iSCSI. This project is a
> drop-in replacement for UDisks2, either from D-Bus or binary point of
> view. The main motivation of this change is to provide the unified
> D-Bus API for all the clients who are willing to manage LVM2, iSCSI,
> Btrfs, BCache, LSM and ZRam.
>
> == Detailed Description ==
> Aim of Storaged is to provide unified higher level management
> interface for various clients who are willing to query and manage
> storage bits of the system. We plan to replace UDisks2 by Storaged,
> since the Storaged itself is the fork of UDisks2 and these 2 projects
> in its core haven't diverged so much (Storaged got some improvements
> which popped up while using it).
>
> == Scope ==
> Proposal owners: To implement this Change
>
> Other developers: N/A (not a System Wide Change)
>
> Release engineering: N/A (not a System Wide Change)
>
> List of deliverables: N/A (not a System Wide Change)
>
> Policies and guidelines: N/A (not a System Wide Change)
>
> Trademark approval: N/A (not needed for this Change)
>
CCing the desktop list, but please keep replies on the Fedora devel list.
At today's FESCo meeting[1], we raised several questions that we would like to
have answered about this change.
1) Have the GNOME, Anaconda/Blivet and Cockpit folks agreed to replacing Udisks2?
2) Is it expected to be a complete cutover (where we drop Udisks2 from the
default install and/or from the distro entirely
Additionally (from my own stockpile of questions): how is such a replacement
going to be done? Are you planning to have storaged take ownership of
org.freedesktop.Udisks2 or are you expecting to convert all consumers of that
interface over to using org.storaged.Storaged? I know that, except for the
interface name, storaged is providing a superset of the functionality offered by
storaged, so I would guess that the simplest approach would be to have it take
over org.freedesktop.Udisks2, but that hasn't been documented anywhere that I
can find.
Please include answers to these questions on the Change Proposal.
[1]
https://meetbot.fedoraproject.org/fedora-meeting/2016-05-13/fesco.2016-05...
6 years, 10 months
Re: Why isn't git installed in Workstation?
by Ryan Lerch
On May 13, 2016 6:14 AM, "Michael Catanzaro" <mcatanzaro(a)gnome.org> wrote:
>
> On Thu, 2016-05-12 at 13:01 -0700, Luya Tshimbalanga wrote:
> > Is gitg (a gnome git frontend) suited for Workstation?
>
> It's a useful application, but I don't think we should have it
> installed by default. It would be pretty confusing to non-developers,
> and I think most developers would not use it.
>
> It would be cool to feature it in GNOME Software.
I agree that the GUI app is probably something that should be not installed
by default, but I think the original post was referring to the git command
line.
To be honest, I assumed this was installed by default on Fedora
workstation, and if it isn't, imho it should be.
It is useful to many of our identified target audiences of workstation, and
has a small enough installed footprint to be included by default.
Cheers,
Ryan Lerch.
>
> Michael
> --
> desktop mailing list
> desktop(a)lists.fedoraproject.org
> http://lists.fedoraproject.org/admin/lists/desktop@lists.fedoraproject.org
6 years, 10 months
More test coverage for Boxes
by Jiri Eischmann
Hi,
Boxes is the pre-installed solution for VMs on Workstation, but it
doesn't get as much attention as it should.
Currently development composes of F24 don't even work in Boxes on F23,
so users who'd like to test F24 in the default VM app are out of luck.
It clearly violates one of the release criteria:https://fedoraproject.o
rg/wiki/Fedora_24_Beta_Release_Criteria#Guest_on_current_stable_release
The problem is that even though Boxes is the default VM app in
Workstation it's not among recommended Fedora virtualization tools the
criteria is referring to: https://fedoraproject.org/wiki/Getting_starte
d_with_virtualization
Fedora QA also use solely virt-manager and they only test Boxes from
time to time to make sure the basic functionality works.
Boxes have been here for some time, it's our default solution, we
should make sure it's the best working desktop VM on Fedora and work
with Fedora QA on ways to improve the test coverage. I think we should
start with adding Boxes to recommended virt tools. Does anyone have an
idea if it needs to go through some committee or is it just "go ahead
and edit" wiki page?
Jiri
6 years, 10 months
Re: comps and spin-kickstarts migration this friday (2016-05-13)
by Bastien Nocera
----- Original Message -----
> Greetings.
>
> This friday (2016-05-13) at 16UTC we will be migrating:
>
> https://fedorahosted.org/comps/
> https://fedorahosted.org/spin-kickstarts/
>
> to
>
> https://pagure.io/fedora-comps/
> https://pagure.io/fedora-kickstarts/
>
> With this migration we will be changing the workflow for
> changes to these repositories from a simple commit model
> to a pull request model. This means in order to make some
> change you should submit a pull request, which will be reviewed
> by at least one other person and then pushed live into the
> repo. Initially commit on these new repos will be set to
> the pagure releng group, but more people will be added as needed.
>
> This model will allow us to run CI tests on Pull Requests and
> confirm that they are not going to cause syntax errors
At least syntax errors could have been dealt with a git hook
server side.
> or other simple breakage. Additionally, this will allow us
> to properly handle changes to these repos during milestone
> Freezes (getting approval for a freeze break before pushing
> changes, etc).
>
> With the migration of the fedora-kickstarts project we will
> also be trying to identify owner(s) for each kickstart file.
> This will allow us to properly assign issues to the
> folks that can address them.
Are those unwanted or broken changes something that happened that
often that we'd want to have this level of review for the patches,
but for me it would probably be any barrier to contribution.
Cheers
6 years, 10 months
Re: comps and spin-kickstarts migration this friday (2016-05-13)
by Paul W. Frields
Sending this on to desktop@ list used by the Workstation WG. Probably
most WG members read devel-announce, but in case not, I didn't want
this to be missed...
On Mon, May 09, 2016 at 10:58:27AM -0600, Kevin Fenzi wrote:
> Greetings.
>
> This friday (2016-05-13) at 16UTC we will be migrating:
>
> https://fedorahosted.org/comps/
> https://fedorahosted.org/spin-kickstarts/
>
> to
>
> https://pagure.io/fedora-comps/
> https://pagure.io/fedora-kickstarts/
>
> With this migration we will be changing the workflow for
> changes to these repositories from a simple commit model
> to a pull request model. This means in order to make some
> change you should submit a pull request, which will be reviewed
> by at least one other person and then pushed live into the
> repo. Initially commit on these new repos will be set to
> the pagure releng group, but more people will be added as needed.
>
> This model will allow us to run CI tests on Pull Requests and
> confirm that they are not going to cause syntax errors
> or other simple breakage. Additionally, this will allow us
> to properly handle changes to these repos during milestone
> Freezes (getting approval for a freeze break before pushing
> changes, etc).
>
> With the migration of the fedora-kickstarts project we will
> also be trying to identify owner(s) for each kickstart file.
> This will allow us to properly assign issues to the
> folks that can address them.
Kevin, typically our component management is done by people such as
kalev, otaylor, and catanzaro. Can we include them please?
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
6 years, 10 months
Re: Announcing the release of Fedora 24 Beta!
by Debarshi Ray
Hey,
On Tue, May 10, 2016 at 09:03:06AM -0500, Dennis Gilmore wrote:
> The Fedora 24 Beta is here, on schedule for our planned June final
> release. Download the prerelease from our Get Fedora site:
>
> - Get Fedora 24 Beta Workstation: a reliable, user-friendly, and powerful
> operating system for your laptop or desktop computer
> https://getfedora.org/workstation/prerelease/
>
> - Get Fedora 24 Beta Server: make use of the very latest server-based
> technologies available in the open source community
> https://getfedora.org/server/prerelease/
>
> - Get Fedora 24 Beta Cloud: build scale-out computing and utilize the next
> generation of container deployment technology
> https://getfedora.org/cloud/prerelease/
>
> - Get Fedora 24 Beta Spins: alternative desktops for Fedora
> https://spins.fedoraproject.org/prerelease
>
> - Get Fedora 24 Beta Labs: curated bundles of purpose-driven software and
> content
> https://labs.fedoraproject.org/prerelease
>
> - Get Fedora 24 Beta ARM: Fedora tailored for running on ARM-based devices
> https://arm.fedoraproject.org/prerelease
>
> [...]
>
> Workstation
> -----------
>
> The Fedora 24 Workstation release will not default to Wayland, the next
> generation graphic stack, but this is planned for future releases.
> Wayland is available as an option, and the Workstation team would
> greatly appreciate your help in testing it out. Our goal is to have one
> full release where Wayland works almost seamlessly as a drop in
> replacement for X11. At that point we plan to set it as the default
> display server in Fedora. This new release also features GNOME 3.20.
> There have been changes to the theming API in GTK+ 3. At this time the
> API is under heavy development and will not remain stable. As a result,
> applications that use custom CSS theming for example, may have rendering
> issues. This could include default applications that come with Fedora 24
> Beta Workstation. We request that users try out their favorite GTK+ 3
> based applications and report bugs to the upstream developers so they
> can be fixed in time for the final release.
I was reading the Fedora 24 Beta release announcement, and this
snippet is a bit inaccurate:
"This new release also features GNOME
3.20. There have been changes to the theming API in GTK+ 3. At this
time the API is under heavy development and will not remain stable."
While GTK+ 3.20 did significantly change the theming API, it should be
much more stable from now on. Or in other words, the theming API was
considered unstable till now, but should be stable going forward.
I don't know the best way to report this, so I am just mentioning it
here in the hope that the right people will notice.
Other than that it looks great!
Cheers,
Rishi
6 years, 10 months