Re: Intent to relicense fontpackages

[Nicolas Mailhot]

Le vendredi 02 novembre 2018 à 03:48 +0100, Kevin Kofler a écrit :

Hi Kevin,

> I don't think you even have to ask the people who contributed in this
> case, 
> because you are converting from LGPLv3+ to GPLv3+, which the licenses
> are 
> designed to allow.

That was more or less my understanding too, but it’s nicer to ask.

Regards,

-- 
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

GNOME/Icon themes expert help needed: Trash icon stopped showing up with "my" icon theme

[Miro Hrončok]

Hi.

I got a bugzilla that says gnome-color-icon-theme fails to show empty 
Trash icon.


https://bugzilla.redhat.com/show_bug.cgi?id=1645368

However apparently nothing changed in the package, hence I guess 
something must have changed in GNOME. Is there anyone who can help me 
understand and debug this?


Thanks,
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Cătălin George Feștilă]

+1 SELinux and policy rules.
I open this. I don't start an "'wich hunting" on specific topics.

I think the problem is still in working with SETID and SELinux rules.
( this is not the only way to solve the
https://fedoraproject.org/wiki/Features/RemoveSETUID)

Will be great if we know how applications involve this issues versus
collateral development teams and fix under SELinux policies.




On Fri, Nov 2, 2018 at 8:53 AM Raphael Groner 
wrote:

> > On Thu, Nov 01, 2018 at 04:33:21PM -0400, Adam Jackson wrote:
> >
> > If I understand this CVE correctly, it doesn't matter what X server is
> > running (if any at all). Do matter what setuid-root Xorg binary is
> > installed (or not).
>
> +1
> SELinux should block such kind of attacks.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Mate/Icon themes expert help needed: Trash icon stopped showing up with "my" icon theme

[Miro Hrončok]

On 02. 11. 18 10:24, Miro Hrončok wrote:

Hi.

I got a bugzilla that says gnome-color-icon-theme fails to show empty 
Trash icon.


https://bugzilla.redhat.com/show_bug.cgi?id=1645368

However apparently nothing changed in the package, hence I guess 
something must have changed in GNOME. Is there anyone who can help me 
understand and debug this?


Thanks,


So apparently, it is Mate, not GNOME.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Nobody care about dmz-cursor-themes package

[Ivan Romanov]

Hi, Raphael. 

I don't care about psi-plus. It was very good time. But now it not
interested for me. About libsignal it can be build without problem on
Fedora and it works fine. But atm I no enough time to make package. But
I agree this package will be useful.

On Fri, 02 Nov 2018 06:05:20 -
"Raphael Groner"  wrote:

> Hi Ivan,
> do you still care about psi-plus? I felt so free to update this
> package. Maybe you can help with better support for OMEMO. Upstream
> told there's no other alternative than libsignal but it's not
> packaged and I don't have time for that. Sorry for my offtopic
> question to this thread. Regards, Raphael
> ___ devel mailing list --
> devel@lists.fedoraproject.org To unsubscribe send an email to
> devel-le...@lists.fedoraproject.org Fedora Code of Conduct:
> https://getfedora.org/code-of-conduct.html List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Need assistance to build LuxCoreRender

[Robert-André Mauchin]

A few unrelated notes:

 - don't mix tabs and spaces
 - Apache 2.0s is not a valid license shorthand, use ASL 2.0
 - don't capitalize the spec name, use luxcorerender
 - Should be Source2 here, not Source3:

install -pm 0644 %{SOURCE2} \
   %{buildroot}%{blender_libdir}/scripts/bpydata/config/blendluxcore-
default.cfg
 
 - In %files %{blender_libdir}/scripts/bpydata/config/luxblend-default.cfg 
should probably be %{blender_libdir}/scripts/bpydata/config/blendluxcore-
default.cfg

 - Use BuildRequires:  boost-devel instead of static and add the PYTHON_V=3 
variable as a cmake parameter. It will now detect Boost correctly

%cmake \
-DCMAKE_VERBOSE_MAKEFILE:BOOL=TRUE \
-DCMAKE_CXX_FLAGS="$CXXFLAGS -DLUXRAYS_DISABLE_OPENCL=0" \
-DPYTHON_V=3

 - %{buildroot}%{bindir} → %{buildroot}%{_bindir}

  - The install part seems  not to be working, try something like:

install -Dpm 0755 bin/* %{buildroot}%{_bindir}/
install -Dpm 0755 lib/*.{a,so*} %{buildroot}%{_libdir}/
mv %{buildroot}%{_libdir}/pyluxcore.so %{buildroot}%{python3_sitearch}/
install -Dpm 0644 include/* %{buildroot}%{_includedir}/

 - there are no luxcorerender.desktop and luxcorerender.svg files

  - blendluxcore is rot extracted and installed

  - %package lib → %package libs for consistency

  - COPYING.txt should be intalled with %license not %doc

 

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Enabling powerline theme system wide by default

[Dominik 'Rathann' Mierzejewski]

On Thursday, 01 November 2018 at 01:13, Luya Tshimbalanga wrote:
> It will be nice to enable powerline theme by default system and user
> wide. Simple reason is refresh the look of terminal while also providing
> useful information especially for git branch. Since powerline does not
> impact the performance, it will be great to set for Fedora 30.
> 
> Comments welcome.

You could start by explaining what "powerline theme" is and why is
it worth enabling.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPMFusion   http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Enabling powerline theme system wide by default

[Stephen Gallagher]

On Fri, Nov 2, 2018 at 9:10 AM Dominik 'Rathann' Mierzejewski
 wrote:
>
> On Thursday, 01 November 2018 at 01:13, Luya Tshimbalanga wrote:
> > It will be nice to enable powerline theme by default system and user
> > wide. Simple reason is refresh the look of terminal while also providing
> > useful information especially for git branch. Since powerline does not
> > impact the performance, it will be great to set for Fedora 30.
> >
> > Comments welcome.
>
> You could start by explaining what "powerline theme" is and why is
> it worth enabling.
>

https://fedoramagazine.org/add-power-terminal-powerline/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

rpm-ostree 2018.9 (and rollup of other releases)

[Colin Walters]

This is one of a semi-regular rollup/highlights post of what's happening in the 
rpm-ostree project, used by [Fedora Atomic Host](https://getfedora.org/atomic/) 
as well as [Fedora Silverblue](https://silverblue.fedoraproject.org/), and 
planned to be used by the converged [Fedora 
CoreOS](https://coreos.fedoraproject.org/).
We make releases approximately once a month.

Previously: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/5PPQYJV72TUKW2OAUUWHRPFEURRS2F4N/

We just recently released v2018.9:
https://github.com/projectatomic/rpm-ostree/releases/tag/v2018.9

The previous rollup post linked above was discussing v2018.6 - so an astute 
reader well-versed in incrementing integers will surmise we also released:
https://github.com/projectatomic/rpm-ostree/releases/tag/v2018.8
https://github.com/projectatomic/rpm-ostree/releases/tag/v2018.7

Additionally since then, in the libostree project there have also been 3 
releases:
https://github.com/ostreedev/ostree/releases/tag/v2018.9
https://github.com/ostreedev/ostree/releases/tag/v2018.8
https://github.com/ostreedev/ostree/releases/tag/v2018.7

(We don't always release once a month for each project, but so far the version 
numbers of the two have stayed roughly in sync)

Looking over the releases, I'll just highlight two things from the libostree 
side.
First are some patches from Javier Martinez Canillas to better integrate with 
the BootloaderSpec
support in GRUB2 - hopefully for both Fedora CoreOS and Silverblue
we can drop os-prober.  The other thing I think is neat on the libostree side 
is we have a new contributor
who is working on Rust bindings: 
https://mail.gnome.org/archives/ostree-list/2018-October/msg0.html

On the rpm-ostree side, we now default to "staging" updates.  This fixes
the "where did my changes in /etc go" problem.  For Fedora CoreOS,
the plan is definitely to do automatic updates by default just like Container 
Linux.
We are having discussion about that in this issue:
https://github.com/coreos/fedora-coreos-tracker/issues/3

I would like to turn this on in Silverblue too by default, although there is 
more work to do
gnome-software side for that.

On the low side, we have hit some bugs in `ex livefs`, and it now requires
a `--i-like-danger` switch.  We plan to revisit this in the future, but
personally...I consider it somewhat of a feature, as it discourages installing
software directly on the host, particularly development tools.
(This is venturing somewhat from rpm-ostree rollup, but keep an eye on
 https://github.com/debarshiray/fedora-toolbox )

There's been a lot of internal cleanups in rpm-ostree; in particular the YAML
syntax is now working very well, and we have continued "oxidation", or 
conversion
of some C code into Rust.

Probably one of the biggest focuses of effort as been on the new
https://github.com/coreos/coreos-assembler
project which we plan to use for Fedora CoreOS.  For anyone who thinks
"FAH/Silverblue are interesting, but I really want to build my own" - please 
keep an eye
on that project and try it out.  We will support the existing `rpm-ostree 
compose tree`
interface probably forever, but it's likely that most improvements on the build 
side
will land in the coreos-assembler project.

Also speaking of custom builds, a good example improvement is that
rpm-ostree now supports `recommends: false` in the treefile, as was
requested by the Fedora IoT group.

A lot of work happened in the background for rojig ♲📦:
https://github.com/projectatomic/rpm-ostree/issues/1081
It's possible that that will be stabilized in the next release or two.

There's more than this of course, if you're interested please
do have a look at the individual releases too!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: IBM buying RedHat

[David Sommerseth]

On 01/11/18 17:31, mcatanz...@gnome.org wrote:
> On Thu, Nov 1, 2018 at 8:32 AM, Neal Gompa  wrote:
>> These are questions I'm interested in answers on. However, I'm also
>> worried about how much the "cloud" was mentioned in the presser. It
>> makes me nervous about Red Hat's investment into other areas, which a
>> lot of the Linux ecosystem relies on, even outside of the Fedora
>> community. Desktop Linux, traditional server platforms, IoT, etc. look
>> like areas that might be disinvested in. :(
> 
> The press release's focus on cloud cloud cloud sure makes it sound like
> desktop team will be first in line for cuts. I think it's quite natural for
> Fedora Workstation users to be worried right now, given the lack of public
> statement regarding the future of Red Hat's desktop work. It goes without
> saying that Fedora will not have a very bright future if Red Hat's investment
> in desktop and Workstation were to cease or be significantly reduced.
> 
> Plus a lot of my friends work on desktop and they will be :( :( :( if their
> jobs go away.

Please, this is speculation.  This does no good.  Do notice these parts from
the press release:

- "IBM to maintain Red Hat’s open source innovation legacy, scaling its vast
   technology portfolio and *empowering its widespread developer community*"

- "With this acquisition, IBM will *remain committed* to Red Hat’s open
   governance, open source contributions, *participation in the open source*
   *community* and development model, and fostering its widespread developer
   ecosystem."

- "Upon closing of the acquisition, Red Hat will join IBM’s Hybrid Cloud team
   *as a distinct unit*, preserving the *independence* and *neutrality* of
   Red Hat’s open source development heritage and commitment, current product
   portfolio and go-to-market strategy, and unique development culture.
   Red Hat will continue to be led by Jim Whitehurst and Red Hat’s current
   management team. [...] IBM intends to *maintain* Red Hat’s headquarters,
   facilities, *brands* and *practices*."

   (my own emphasizing)

All can be found here:


And more details:
-



In addition, according to zdnet [0]:

  'Arvind Krishna, IBM's senior vice president of hybrid cloud, said: "Red Hat
   must, and will, remain independent."'

This is a fairly strong statement from IBM.

[0]



Lots can be said about IBM.  But despite the rumours on the street, IBM isn't
stupid.  They have not spend 34 billion dollars to whack any chances of
success and even jeopardise the chance of getting something really valuable
back in return.

The cloud services IBM provides can benefit from the knowledge and experience
Red Hat employees have.  But these employees will not get that experience or
being able to move forward if the RHEL stops innovating.  And RHEL builds on
Fedora.  And if IBM managed to really mess this up, they will loose a great
community which has helped Red Hat by far way achieving the position they
have.  Bare in mind that Red Hat's mission statement is all about this:

   "To be the catalyst in communities of customers, contributors, and partners
creating better technology the open source way."

With this deal, IBM didn't just get the Red Hat brand and Red Hat employees.
They also got a thriving and engaged community.  And a good leadership is able
to see this and the value this gives.  The Red Hat leadership definitely sees
this and I'm pretty sure they will ensure IBM understands this too.

Plus, IBM is not unfamiliar with open source and they also drive their own
open source projects too.  Just look at what they've done on the POWER
platforms and the OpenPower projects they've helped fuelling.

If IBM plays their cards well and also pays good attention to the advices I am
sure the Red Hat leadership will give them, this can go very well - for all -
including the Fedora community.

Now, you raise concerns about Fedora Workstation.  But what is the fundamental
base this variant of Fedora builds on?  Fedora Workstation, Fedora Server and
Fedora Atomic all builds on the same fundamental base.  And what wouldn't be a
better way to ensure Fedora is growing further into the developer areas than
to have a solid Fedora based desktop on top of the server side?  My point is,
jeopardizing Fedora Workstation doesn't only reduce the desktop experience; it
impacts the bigger scope of what Fedora is.  It puts the whole "empowering
widespread developer community" statement at risk.

Plus ... IBM does not, will not and can not manage or control the community
itself regardless of Red Hat being acquired or not.  It can only manage the
people on their payroll in regards to what they work on in their 

Re: Enabling powerline theme system wide by default

[John Florian]

On 11/2/18 9:41 AM, Stephen Gallagher wrote:

On Fri, Nov 2, 2018 at 9:10 AM Dominik 'Rathann' Mierzejewski
 wrote:

On Thursday, 01 November 2018 at 01:13, Luya Tshimbalanga wrote:

It will be nice to enable powerline theme by default system and user
wide. Simple reason is refresh the look of terminal while also providing
useful information especially for git branch. Since powerline does not
impact the performance, it will be great to set for Fedora 30.

Comments welcome.

You could start by explaining what "powerline theme" is and why is
it worth enabling.


https://fedoramagazine.org/add-power-terminal-powerline/
That provides a nice overview, but as someone who's extensively diddled 
their bash configuration to achieve most all of this via a very 
glorified PS1, can anyone tell me why powerline needs a daemon?  Or if 
it's not needed, what benefit does it bring?

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: CVE-2018-14665 : Xorg X Server Vulnerabilities

[Lukas Vrabec]

On 11/2/18 7:01 AM, Raphael Groner wrote:
>> On 11/1/18 5:08 PM, Cătălin George Feștilă wrote:
>>
>> SELinux can block the exploit if the "unconfined" module is disabled.
> 
> Same thoughts here. No main process (by user) should be allowed to overwrite 
> system configuration except the dedicated tools or an editor.
> 
>> I'm writing blog about it. When it will be ready, I add link also to
>> this thread.
> 
> Thanks. Please let us know about your work.
> 

https://lukas-vrabec.com/index.php/2018/11/02/cve-2018-14665-xorg-x-server-vulnerabilities-vs-selinux/

> Regards, Raphael
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> 


-- 
Lukas Vrabec
Software Engineer, Security Technologies
Red Hat, Inc.



signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Enabling powerline theme system wide by default

[Robert Marcano]

On 11/2/18 10:12 AM, John Florian wrote:

On 11/2/18 9:41 AM, Stephen Gallagher wrote:

On Fri, Nov 2, 2018 at 9:10 AM Dominik 'Rathann' Mierzejewski
 wrote:

On Thursday, 01 November 2018 at 01:13, Luya Tshimbalanga wrote:

It will be nice to enable powerline theme by default system and user
wide. Simple reason is refresh the look of terminal while also 
providing

useful information especially for git branch. Since powerline does not
impact the performance, it will be great to set for Fedora 30.

Comments welcome.

You could start by explaining what "powerline theme" is and why is
it worth enabling.


https://fedoramagazine.org/add-power-terminal-powerline/
That provides a nice overview, but as someone who's extensively diddled 
their bash configuration to achieve most all of this via a very 
glorified PS1, can anyone tell me why powerline needs a daemon?  Or if 
it's not needed, what benefit does it bring?



For bash mode it can run without it, but it is painfully slow (it has so 
many options and features that it is not a small process doing simple 
fast tasks), so the daemon allows to have the process running all the 
time and a small renderer calls it for the current prompt line. It also 
allow to have multiple renderers for tmux, vim, etc.


This is no small python service running and consuming resources all the 
time for something non CLI users will ever use. Maybe someone manages to 
make the powerline daemon to start on demand (if a terminal is opened).



___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

icecast-2.4.4 license correction

[Petr Pisar]

I've just built icecast-2.4.4 for all Fedoras and EPEL-7 and corrected
a license tag from "GPLv2+" to "GPLv2+ and GPLv2 and BSD" in icecast binary
package and to "GPLv2+ and MIT and FSFULLR and FSFUL" in icecast-doc
binary package to reflect the reality (the GPLv2 only code also existed
in older icecast releases).

-- Petr
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Schedule for Monday's FESCo Meeting (2018-11-05)

[Zbigniew Jędrzejewski-Szmek]

NOTE: daylight savings time goes out of effect in US this weekend, so
the meeting is at "one hour earlier", i.e. at 15:00 UTC / 10:00 EST / 07:00 PST.


Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2018-11-05 15:00 UTC'

Links to all issues to be discussed can be found at: 
https://pagure.io/fesco/report/meeting_agenda

= Discussed and Voted in the Ticket =

Publish Fedora base container image on quay.io
https://pagure.io/fesco/issue/2002
Approved: +6, 0, 0.

= Followups =

#topic 2003 Ursa Major (modules in buildroot) enablement
.fesco 2003
https://pagure.io/fesco/issue/2003

#topic 2004 Enabling pm_request in fedoraproject koji
.fesco 2004
https://pagure.io/fesco/issue/2004

= Open Floor = 

For more complete details, please visit each individual issue. The
report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can reply to
this e-mail, file a new issue at https://pagure.io/fesco, e-mail me
directly, or bring it up at the end of the meeting, during the open
floor topic. Note that added topics may be deferred until the
following meeting.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Enabling powerline theme system wide by default

[Chris Murphy]

On my Intel NUC, which is x86_64, powerline-daemon uses about 1.2% CPU
at all times even when idle. I'm not sure why. The TIME+ colume in top
shows it using about 1/5th the CPU time of NetworkManager and 1/2 the
time of dbus and 1/3 that of docker running pihole. I dunno, I
tolerate it but I'm not sure it's efficient enough by default, but
then I have no idea why NetworkManager is consuming as much CPU as it
is for that matter, maybe somehow the pihole ends up offloading its
work onto NetworkManager.


Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

NeuroFedora review swaps: python-fslpy, python-fsleyes-widgets

[Ankur Sinha]

Hello,

Would anyone like to swap reviews please? I've got two more python
packages that are now ready for review:

- python-fslpy: https://bugzilla.redhat.com/show_bug.cgi?id=1645329
- python-fsleyes-widgets: https://bugzilla.redhat.com/show_bug.cgi?id=1645661

One can follow the NeuroFedora reviews here:
https://bugzilla.redhat.com/show_bug.cgi?id=1276941
and here:
https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open&tags=S%3A+Needs+review

This is the list of packages in that still need packaging:
https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open&tags=S%3A+Needs+packaging

-- 
Thanks,
Regards,

Ankur Sinha "FranciscoD"

https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Need assistance to build LuxCoreRender

[Luya Tshimbalanga]

Thanks for the pointers. The build encountered an issue due to the use
of boost-static (for some strange reason, boost-devel will not be
detected). I put the SRPM in COPR for testing:
https://copr-be.cloud.fedoraproject.org/results/luya/LuxCoreRender/fedora-29-x86_64/00818528-LuxCoreRender/

including the SPEC file. Suggestion welcome.


Luya




signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Need assistance to build LuxCoreRender

[Luya Tshimbalanga]

Thanks for the pointers. The build encountered an issue due to the use
of boost-static (for some strange reason, boost-devel will not be
detected). I put the SRPM in COPR for testing:
https://copr-be.cloud.fedoraproject.org/results/luya/LuxCoreRender/fedora-29-x86_64/00818528-LuxCoreRender/

including the SPEC file. Suggestion welcome.


Luya




signature.asc
Description: OpenPGP digital signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Fedora updates-20181102.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 2/2 (x86_64)

Old failures (same test failed in updates-20181101.0):

ID: 304835  Test: x86_64 AtomicHost-dvd_ostree-iso install_default
URL: https://openqa.fedoraproject.org/tests/304835
ID: 304836  Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/304836
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Fedora testing-20181102.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 2/2 (x86_64)

ID: 304837  Test: x86_64 AtomicHost-dvd_ostree-iso install_default
URL: https://openqa.fedoraproject.org/tests/304837
ID: 304838  Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/304838
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Enabling powerline theme system wide by default

[stan]

On Fri, 2 Nov 2018 09:41:34 -0400
Stephen Gallagher  wrote:

> On Fri, Nov 2, 2018 at 9:10 AM Dominik 'Rathann' Mierzejewski
>  wrote:
> >
> > On Thursday, 01 November 2018 at 01:13, Luya Tshimbalanga wrote:  
> > > It will be nice to enable powerline theme by default system and
> > > user wide. Simple reason is refresh the look of terminal while
> > > also providing useful information especially for git branch.
> > > Since powerline does not impact the performance, it will be great
> > > to set for Fedora 30.

I read in comments here people saying that it takes approximately 1 to 2
per cent of CPU constantly.  How is this not an impact to performance?
Even if it is small, why waste cpu?  Not to mention the context
switching hit.

> > >
> > > Comments welcome.  
> >
> > You could start by explaining what "powerline theme" is and why is
> > it worth enabling.
> >  
> 
> https://fedoramagazine.org/add-power-terminal-powerline/

I just use 
PS1='\e[1;33;40m\w\e[0;37;40m  \@  \u  \l\n\$ '
I hope there is a way to turn powerline off as I don't need it, if it
is just doing what is described in that article.  Not saying some
people might not find it a wonderful addition, and they should be able
to run it.  Is there an option in the json configuration file that
disables it, if you do decide to make it the default?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: NeuroFedora review swaps: python-fslpy, python-fsleyes-widgets

[Raphael Groner]

Hi Ankur,

I could look into your review requests later.

Maybe we can do a review swap with python-slacker and slack-cleaner? Currently, 
I am working on both of them but not yet finished to have it ready for review.
https://github.com/os/slacker
https://github.com/kfei/slack-cleaner
https://bugzilla.redhat.com/show_bug.cgi?id=1645723

Regards, Raphael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org