Luya Tshimbalanga wrote on 2022/10/10 2:46:
Hello team,
openshadinglanguage 1.12.6.2 only successfully built on x86_64 architecture but
failed on others due to the following errors:
In file included from
/builddir/build/BUILD/OpenShadingLanguage-1.12.6.2/src/liboslexec/oslexec_pvt.h:42,
Hi Stephen,
Stephen Gallagher writes:
> On Tue, Sep 6, 2022 at 2:29 PM Ben Cotton wrote:
> *snip*
> When a Node.js release goes out of support, we have a question to
> answer: do we Obsolete it with a newer version? If so, which one? The
> most recent version or the oldest one? It will not be
Hello team,
openshadinglanguage 1.12.6.2 only successfully built on x86_64
architecture but failed on others due to the following errors:
In file included from
/builddir/build/BUILD/OpenShadingLanguage-1.12.6.2/src/liboslexec/oslexec_pvt.h:42,
from
/builddir/build/BUILD/Open
OLD: Fedora-37-20221008.n.0
NEW: Fedora-37-20221009.n.0
= SUMMARY =
Added images:0
Dropped images: 1
Added packages: 0
Dropped packages:0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages:0 B
Size of upgraded
Announcing the creation of a new nightly release validation test event
for Fedora 37 Branched 20221009.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
OLD: Fedora-Rawhide-20221008.n.0
NEW: Fedora-Rawhide-20221009.n.0
= SUMMARY =
Added images:0
Dropped images: 2
Added packages: 0
Dropped packages:0
Upgraded packages: 56
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages:0 B
Size
Thanks!
Daniel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fed
On Sun, Oct 09, 2022 at 10:25:08AM -, Daniel Rusek wrote:
> Hello,
>
> Just a note. If someone from RPM Fusion who is interested in packaging
> full mesa-va-drivers package reads this, please, make sure that the
> package also contains valid AppStream metadata and is showing in GNOME
> Softwar
It is just a simple, short xml file, not a big deal for maintainers, but
actually quite a big deal for many end users. If anyone from RPM Fusion needs a
help with this file, feel free to drop me a line. :-)
___
devel mailing list -- devel@lists.fedorapr
Because Fedora also targets regular users who are not experts and also because
it would make it much easier for all users to find and install that package
(for example by entering "h264" in GNOME Shell Overview on a RPM Fusion enabled
system) instead of requiring them to search/install the packa
On Sun, 2022-10-09 at 10:25 +, Daniel Rusek wrote:
> Hello,
>
> Just a note. If someone from RPM Fusion who is interested in
> packaging full mesa-va-drivers package reads this, please, make sure
> that the package also contains valid AppStream metadata and is
> showing in GNOME Software / K
Here is an example of the driver component AppStream metadata type:
https://www.freedesktop.org/software/appstream/docs/sect-Metadata-Driver.html
You can probably ignore the tag.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe se
Hello,
Just a note. If someone from RPM Fusion who is interested in packaging full
mesa-va-drivers package reads this, please, make sure that the package also
contains valid AppStream metadata and is showing in GNOME Software / KDE
Discover the same way as, for example, NVIDIA driver does. It i
Am 05.10.22 um 23:07 schrieb Chris Murphy:
On Wed, Oct 5, 2022, at 3:01 PM, Vít Ondruch wrote:
3. "Boot menu" in GUI? Given that one can reach the GUI, why it should
not be possible to choose the boot entry for next boot? Or even choose
to open FW setup.
This could solve this other problem
14 matches
Mail list logo
