[Test-Announce] Proposal to CANCEL: 2018-11-05 Fedora QA Meeting

[Adam Williamson]

Hi folks! (Yep, I'm back from vacation). I'm proposing we cancel the QA
meeting tomorrow. Thanks to everyone for the great job in getting
Fedora 29 released last week! As that's done, and there's no other
pressing business I'm aware of, I figured we all deserve a break :)

There are currently several issues with Rawhide - composes are broken,
and the last few composes that completed had a major bug (anaconda
wouldn't start). There's work in progress on all of those issues, so
hopefully we'll get some working composes next week, and the first
Fedora 30 validation event.

If anyone's concerned about how the Big News affects us - well, so far
the answer is "it's kinda too soon to know anything for sure, but for
the immediate future, not at all". Who knows whether anything will
change in the long term, but so far we've had no indication anything is
changing wrt Fedora or Fedora QA in the short to medium term. We can
certainly talk about it more at next week's meeting, but to be honest,
that's all the information we have for now.

Thanks again, everyone!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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/test-annou...@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

Fedora testing-20181105.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 2/2 (x86_64)

ID: 305032  Test: x86_64 AtomicHost-dvd_ostree-iso install_default
URL: https://openqa.fedoraproject.org/tests/305032
ID: 305033  Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/305033
-- 
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 updates-20181105.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-20181104.1):

ID: 305030  Test: x86_64 AtomicHost-dvd_ostree-iso install_default
URL: https://openqa.fedoraproject.org/tests/305030
ID: 305031  Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/305031
-- 
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: Unretire recordmydesktop

[Samuel Sieb]

On 11/4/18 11:47 AM, Michael Schwendt wrote:

Quoting https://bugzilla.redhat.com/1538352#c1

| Yes, recordmydesktop was intentionally retired due to the project being
| abandoned (no new release in 10 years), it contained many crash bugs,
| and was not at all working on Wayland.


I don't know about the other bugs, but not working on Wayland can't be 
held against it.  Nothing works to record the desktop on Wayland since 
that isn't supported yet.

___
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: openmpi dependency problem?

[Richard Shaw]

On Sun, Nov 4, 2018 at 4:07 AM Susi Lehtola 
wrote:

> On 11/3/18 5:11 PM, Richard Shaw wrote:
> > I've been working on getting a good build of FreeCAD 0.17 in Fedora
> > (long story) and I was finally able to get a good scratch build on
> > Rawhide so I decided to do a local mock build for Fedora 28 so I could
> > actually test the package...
> >
> > As expected it built fine but I can't install it due to a dependency on
> > libmpi...
> >
> > # dnf install ./freecad-0.17-2.fc28.x86_64.rpm
> > ./freecad-data-0.17-2.fc28.noarch.rpm
>
> Judging from your package name you are not aware of the MPI packaging
> guidelines
>
> https://fedoraproject.org/wiki/Packaging:MPI


Nope... Just trying to satisfy configuring. Removed and now working, thanks!

Richard
___
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: NeuronFedora review swaps (Was: Re: NeuroFedora review swaps: python-fslpy, python-fsleyes-widgets)

[Ankur Sinha]

Hello,

Would anyone like to swap reviews please? I've a very simple, straight
forward package that needs review:

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

It's a very simple library that's needed for us to package biosig[1].

[1] https://pagure.io/neuro-sig/NeuroFedora/issue/56

-- 
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: Safe to remove yum?

[YOUNG, MICHAEL A.]

On Sun, 4 Nov 2018, Nico Kadel-Garcia wrote:

> On Sun, Nov 4, 2018 at 8:59 AM Dominik 'Rathann' Mierzejewski
>  wrote:
>>
>> On Saturday, 03 November 2018 at 21:10, Neal Gompa wrote:
>>> On Sat, Nov 3, 2018 at 4:10 PM Scott Talbert  wrote:

 Doing a 'dnf autoremove' after upgrading to F29, yum is one of the
 packages it wants to remove.  Is it safe to remove yum these days?

>>>
>>> Yes. Things pretty much don't use yum anymore.
>>
>> Unless you're building packages for EPEL locally using mock,
>> but then you can use mock --dnf.
>>
>> Regards,
>> Dominik
>
> RHEL and CentOS do not support DNF features like "Suggests:". Always
> using dnf and dnf features is a good way to make packages that cannot
> be compiled natively on RHEL or CentOS. Those van be excluded out of
> the configs, but I find it safer to discover those when doing "mock"
> builds.

I suspect that isn't quite true any more as dnf is a Technology Preview 
with yum 4 in RHEL 7.6.

Michael Young
___
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-review]LuxRender renamed luxcorerender

[Luya Tshimbalanga]

Upstream LuxRender changed its name to LuxCoreRender. The source package
is submitted for re-review
https://bugzilla.redhat.com/show_bug.cgi?id=1645913 .

Massive cleanup  from the old LuxRender.spec is done. It does not
include the new macros found on the development release yet but it is
easy setup in that mind. A strange bug during the build triggered a DUP
FUNXC as highlighted on
https://bugzilla.redhat.com/show_bug.cgi?id=1645828 but can be safely
ignored.

Luya




0x5E528174D8A2609A.asc
Description: application/pgp-keys
___
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]

On 2018-11-04 11:21 a.m., Nicolas Mailhot wrote:
> Le dimanche 04 novembre 2018 à 11:01 -0800, Luya Tshimbalanga a écrit :
>> On 2018-11-04 4:43 a.m., Nicolas Mailhot wrote:
>>> So, basically you should just need a do2unix and the following lines
>>> in
>>> rawhide:
>> I have Fedora 29 installed and the above line still led to error. 
> Which error please?
>
> $ rpmspec -P luxcorerender.spec
> 'orgemeta: invalid option -- '
>  in forgemeta(az:sviu:)
> error: line 10: %forgemeta -a
> $ dos2unix luxcorerender.spec
> dos2unix: converting file luxcorerender.spec to Unix format...
> $ rpmspec -P luxcorerender.spec
> Name:   luxcorerender
> Version:2.1
> …
Yes that error. I haven't used rpmspec command before. Very useful.
>> Maybe
>> porting redhat-rpm-macro to the current release will alleviate the
>> issue.
> If you have the above error that’s due to the DOS end of lines in your
> spec file.
>
> Otherwise, as I said, you need devel (a Fedora version with redhat-rpm-
> config 123 or a later version) for forgemeta to understand multiple
> archives.
Noted. That resolved the problem.
>
>>> Name:   luxcorerender
>>> Version:2.1
>>> %global prerelease  beta1
>>> %global forgeurl0   https://github.com/%{name}/LuxCore
>>> %global tag0luxcorerender_v%{version}%{?prerelease}
>>>
>>> %global forgeurl1   https://github.com/%{name}/BlendLuxCore
>>> %global tag1blendluxcore_v%{version}%{?prerelease}
>>>
>>> %forgemeta -a
>>>
>>> […]
That line generated an error using rpmbuild -bs command on Fedora 29. It
looks like the tool needs upgrade as well.
>>>
>>> Source0:%{forgesource0}
>>> Source1:%{forgesource1}
>>>
>>> […]
>>>
>>> %prep
>>> %forgesetup -a
>>> %patch0 -pX 
>> Will it be better to put "%forgesetup -a -pX" in one line similar to
>> "%autosetup" considering this scenario?
> Really, no. You can unpack several archives at once (with -a) or unpack
> one at a time with patching (with forgeautosetup -z ) but rpm
> macro argument parsing is not up to doing both at once safely. %setup
> does not use normal rpm argument parsing, that's why it sort of works.
>
> And, besides, the result would probably be unmaintainable cryptic macro
> calls.
>
> Regards,

Thank you for the explanation.

I submitted the spec for re-review on
https://bugzilla.redhat.com/show_bug.cgi?id=1645913. I'll update shortly
with the newer version.


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: Unretire recordmydesktop

[Michael Schwendt]

On Sun, 4 Nov 2018 12:17:00 +, Richard W.M. Jones wrote:

> recordmydesktop was retired in F27:
> 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/4RCB6MBC4JVGG4SYLIKUDOOT2REGA6N4/
> 
> It's claimed that it doesn't work and is full of crash bugs, but I was
> able to compile it on F29 and it works fine for me, and it's a very
> useful little tool.

Quoting https://bugzilla.redhat.com/1538352#c1

| Yes, recordmydesktop was intentionally retired due to the project being
| abandoned (no new release in 10 years), it contained many crash bugs,
| and was not at all working on Wayland.

There are various WONTFIX and EOL issues tracked in bugzilla. Bringing
back the package without going through those tickets first doesn't sound
like a good idea.
___
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

[Nicolas Mailhot]

Le dimanche 04 novembre 2018 à 11:01 -0800, Luya Tshimbalanga a écrit :
> On 2018-11-04 4:43 a.m., Nicolas Mailhot wrote:
> > So, basically you should just need a do2unix and the following lines
> > in
> > rawhide:
> 
> I have Fedora 29 installed and the above line still led to error. 

Which error please?

$ rpmspec -P luxcorerender.spec
'orgemeta: invalid option -- '
 in forgemeta(az:sviu:)
error: line 10: %forgemeta -a
$ dos2unix luxcorerender.spec
dos2unix: converting file luxcorerender.spec to Unix format...
$ rpmspec -P luxcorerender.spec
Name:   luxcorerender
Version:2.1
…

> Maybe
> porting redhat-rpm-macro to the current release will alleviate the
> issue.

If you have the above error that’s due to the DOS end of lines in your
spec file.

Otherwise, as I said, you need devel (a Fedora version with redhat-rpm-
config 123 or a later version) for forgemeta to understand multiple
archives.

> > Name:   luxcorerender
> > Version:2.1
> > %global prerelease  beta1
> > %global forgeurl0   https://github.com/%{name}/LuxCore
> > %global tag0luxcorerender_v%{version}%{?prerelease}
> > 
> > %global forgeurl1   https://github.com/%{name}/BlendLuxCore
> > %global tag1blendluxcore_v%{version}%{?prerelease}
> > 
> > %forgemeta -a
> > 
> > […]
> > 
> > Source0:%{forgesource0}
> > Source1:%{forgesource1}
> > 
> > […]
> > 
> > %prep
> > %forgesetup -a
> > %patch0 -pX 
> 
> Will it be better to put "%forgesetup -a -pX" in one line similar to
> "%autosetup" considering this scenario?

Really, no. You can unpack several archives at once (with -a) or unpack
one at a time with patching (with forgeautosetup -z ) but rpm
macro argument parsing is not up to doing both at once safely. %setup
does not use normal rpm argument parsing, that's why it sort of works.

And, besides, the result would probably be unmaintainable cryptic macro
calls.

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

Re: Need assistance to build LuxCoreRender

[Luya Tshimbalanga]

On 2018-11-04 4:43 a.m., Nicolas Mailhot wrote:
> So, basically you should just need a do2unix and the following lines in
> rawhide:

I have Fedora 29 installed and the above line still led to error. Maybe
porting redhat-rpm-macro to the current release will alleviate the issue.

> Name:   luxcorerender
> Version:2.1
> %global prerelease  beta1
> %global forgeurl0   https://github.com/%{name}/LuxCore
> %global tag0luxcorerender_v%{version}%{?prerelease}
>
> %global forgeurl1   https://github.com/%{name}/BlendLuxCore
> %global tag1blendluxcore_v%{version}%{?prerelease}
>
> %forgemeta -a
>
> […]
>
> Source0:%{forgesource0}
> Source1:%{forgesource1}
>
> […]
>
> %prep
> %forgesetup -a
> %patch0 -pX 

Will it be better to put "%forgesetup -a -pX" in one line similar to
"%autosetup" considering this scenario?

Thanks for the input.


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: Safe to remove yum?

[Nico Kadel-Garcia]

On Sun, Nov 4, 2018 at 8:59 AM Dominik 'Rathann' Mierzejewski
 wrote:
>
> On Saturday, 03 November 2018 at 21:10, Neal Gompa wrote:
> > On Sat, Nov 3, 2018 at 4:10 PM Scott Talbert  wrote:
> > >
> > > Doing a 'dnf autoremove' after upgrading to F29, yum is one of the
> > > packages it wants to remove.  Is it safe to remove yum these days?
> > >
> >
> > Yes. Things pretty much don't use yum anymore.
>
> Unless you're building packages for EPEL locally using mock,
> but then you can use mock --dnf.
>
> Regards,
> Dominik

RHEL and CentOS do not support DNF features like "Suggests:". Always
using dnf and dnf features is a good way to make packages that cannot
be compiled natively on RHEL or CentOS. Those van be excluded out of
the configs, but I find it safer to discover those when doing "mock"
builds.
___
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: Self Introduction: Carmen

[Benson Muite]

Bonvenon!

On 10/30/2018 02:03 PM, Carmen Bianca Bakker wrote:

Hi all,

The contribution guide thingamajig told me to post a short message
here.  So as follows: I am Carmen from Friesland, The Netherlands.  I am
currently working on GNOME to make the GNOME desktop available in
Esperanto.  At the current rate, GNOME 3.32 will have its core release
(standard apps, core libraries) completely translated into Esperanto,
which I am fairly proud of :-)

Furthermore, I am a former intern of the Free Software Foundation Europe
where I worked on the REUSE Initiative (;).  You
can find me at the FSFE booth at SFScon in Bozen/Bolzano, 16 November.

I am joining this list to make sure that `langpacks-eo` will become
available in Fedora 30.  If someone knows some pointers for me there
while I (slowly) work on it, I would greatly appreciate those.

Thanks and with kindness,
Carmen



___
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: Safe to remove yum?

[Dominik 'Rathann' Mierzejewski]

On Saturday, 03 November 2018 at 21:10, Neal Gompa wrote:
> On Sat, Nov 3, 2018 at 4:10 PM Scott Talbert  wrote:
> >
> > Doing a 'dnf autoremove' after upgrading to F29, yum is one of the
> > packages it wants to remove.  Is it safe to remove yum these days?
> >
> 
> Yes. Things pretty much don't use yum anymore.

Unless you're building packages for EPEL locally using mock,
but then you can use mock --dnf.

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: Need assistance to build LuxCoreRender

[Nicolas Mailhot]

So, basically you should just need a do2unix and the following lines in
rawhide:

Name:   luxcorerender
Version:2.1
%global prerelease  beta1
%global forgeurl0   https://github.com/%{name}/LuxCore
%global tag0luxcorerender_v%{version}%{?prerelease}

%global forgeurl1   https://github.com/%{name}/BlendLuxCore
%global tag1blendluxcore_v%{version}%{?prerelease}

%forgemeta -a

[…]

Source0:%{forgesource0}
Source1:%{forgesource1}

[…]

%prep
%forgesetup -a
%patch0 -pX

-- 
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

Re: Need assistance to build LuxCoreRender

[Nicolas Mailhot]

Le samedi 03 novembre 2018 à 15:13 -0700, Luya Tshimbalanga a écrit :
Hi,

>Source0:   
> 
> https://github.com/%{name}/LuxCore/archive/luxcorerender_v%{version}.tar.gz
> Source1:   
> https://github.com/%{name}/BlendLuxCore/archive/blendluxcore_v%{version}.tar.gz
> Patch0:%{name}-cmake-python.patch

You could probably do something like

Name:   luxcorerender
Version:2.1
%global
prerelease  beta1
%global forgeurl0   https://github.com/%{name}/LuxCore
%global tag0v%{version}%{?prerelease}

%global forgeurl1   https://github.com/%{name}/BlendLuxCore
%global tag1blendluxcore_%{tag0}

%forgemeta -a


[…]
Source0:%{forgesource0}
Source1:%{forgesource1}

[…]

%prep
%forgesetup -a
%patch0 -p1

With the redhat-rpm-config in rawhide. At least that works fine in a
test spec, but not when injected in yours, because the dos end of lines
in your file cause rpmspec to go bonkers

$ rpmspec -P luxcorerender.spec 
'orgemeta: invalid option -- '
 in forgemeta(az:sviu:)
error: line 13: %forgemeta -a

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

Unretire recordmydesktop

[Richard W.M. Jones]

recordmydesktop was retired in F27:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/4RCB6MBC4JVGG4SYLIKUDOOT2REGA6N4/

It's claimed that it doesn't work and is full of crash bugs, but I was
able to compile it on F29 and it works fine for me, and it's a very
useful little tool.

Therefore I'd like to unretire the package and maintain it.  Actually
there are two: recordmydesktop and gtk-recordmydesktop.

This announcement on devel list is persuant to the guidelines[1].  If
no one objects in a few days I'll continue the rest of the process.
(Do we really need to re-review packages ...?  That seems tedious.)

Rich.

[1] 
https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_a_Retired_Package

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
___
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: openmpi dependency problem?

[Susi Lehtola]

On 11/3/18 5:11 PM, Richard Shaw wrote:
I've been working on getting a good build of FreeCAD 0.17 in Fedora 
(long story) and I was finally able to get a good scratch build on 
Rawhide so I decided to do a local mock build for Fedora 28 so I could 
actually test the package...


As expected it built fine but I can't install it due to a dependency on 
libmpi...


# dnf install ./freecad-0.17-2.fc28.x86_64.rpm 
./freecad-data-0.17-2.fc28.noarch.rpm


Judging from your package name you are not aware of the MPI packaging 
guidelines


https://fedoraproject.org/wiki/Packaging:MPI
--
Susi Lehtola
Fedora Project Contributor
jussileht...@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: Wayland hangs (black screen) after dnf update to Fedora 29

[Alain Vigne]

Thank you very much for your replies.
No 'rhgb' is the workaround in my case. I added my comment to the bug
report you mentioned Fabio.

Any idea who is handling this, current status and how/when/why this will be
solved ?

BR, Alain


On Sun, Nov 4, 2018 at 1:05 AM Fabio Valentini  wrote:

> On Sat, Nov 3, 2018 at 11:41 PM Alain Vigne 
> wrote:
> >
> > Hi everyone
> > TLDR; I had a working Wayland Gnome Desktop in f28. Not anymore with f29.
> >
> > Yesterday, I "dnf upgrade" my f28 to f29 ... to find a black screen when
> I want to login to my Gnome session :(
> >
> > The boot is OK till the gdm login screen, but when I enter my password,
> the screen turns black, and the keyboard is locked (non-responsive, Num
> Lock does not toggle, nor caps lock).
> > Then I don't know how to recover control, as no key binding is
> effective, no mouse, no screen :(I power off the machine)
> >
> > I successfully launched the desktop using "startx" from my user account
> after booting with runlevel=3, so I think there is an issue with Wayland !
> >
> > > lspci|grep "VGA"
> > 01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX
> 960] (rev a1)
> > I used to install the nvidia drivers, after each kernel upgrade. I did
> that, as usual using:
> > > ./NVIDIA-Linux-x86_64-410.73.run
> >
> > Where should I look to have more information about what's wrong with my
> system ?
> > Which component should I report on BZ ?
> > What additional info would be helpful for knowledgeable developers ?
> >
> > Thanks for your help
> > Best regards
> > --
> > Alain V.
>
> Hi Alain,
>
> This seems to be a common issue with fedora 29 / NVIDIA drivers, I
> reported it here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1643302
>
> And there are some people on reddit who seem to be affected, too.
>
> Have you tried dropping "rhgb" from the kernel command line (by
> editing the GRUB boot entry)? (Possibly also change
> nvidia-drm.modeset=1 to nvidia-drm.modeset=0 to disable wayland in
> gdm.)
> Most people seem to confirm that this serves as a workaround.
>
> Fabio
>
> > ___
> > 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
>


-- 
Alain V.
___
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