On Wed, Apr 16, 2025 at 6:50 AM Aoife Moloney via devel-announce <
devel-annou...@lists.fedoraproject.org> wrote:
> Wiki - https://fedoraproject.org/wiki/Changes/CMake_drop_install_vars
> Discussion thread -
>
> https://discussion.fedoraproject.org/t/f42-change-proposal-cmake-drop-non-standard-var
On Tue, Apr 15, 2025 at 6:20 AM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:
> Hi,
>
> When a system is _upgraded_ to F42, we try to "merge", by making
> /usr/sbin a symlink to /usr/bin. This is blocked when a package lists
> files under /usr/sbin. It'd be great to rebuild/update those
On Tue, Apr 8, 2025 at 3:38 PM Ben Beasley wrote:
> On Tue, Apr 8, 2025, at 7:41 AM, Richard Shaw wrote:
> > On Tue, Apr 8, 2025 at 6:35 AM Ben Beasley
> wrote:
> >> In one week, 2025-04-15, or slightly later, I plan to update
> >> openshadinglanguage from 1.13.12.
On Tue, Apr 8, 2025 at 6:35 AM Ben Beasley wrote:
> In one week, 2025-04-15, or slightly later, I plan to update
> openshadinglanguage from 1.13.12.0 to 1.14.5.0 in F43/Rawhide[1].
>
I've slept too many times since then, but isn't this one of the main
reasons OpenImageIO could not be upgraded to
On Thu, Feb 6, 2025 at 6:16 PM Fabio Valentini wrote:
> On Thu, Feb 6, 2025 at 11:37 PM Richard Shaw wrote:
> >
> > It seems to be the only reason for FTBFS. A single test is failing.
> Upstream has no interest in supporting 32bit anymore, which I think makes
> sense.
>
It seems to be the only reason for FTBFS. A single test is failing.
Upstream has no interest in supporting 32bit anymore, which I think makes
sense.
For posterity here are the potential affected packages:
$ fedrq whatrequires-src --branch rawhide --format source
--exclude-subpackages openexr
CImg
The project[1] was originally used for FreeCAD which was retired due to
complicated dep issues and has no other dependents and is currently
FTBFS[3].
It has a fractured upstream[2] (I think I'm on my 3rd upstream) and the
current one has not made a release since 2022.
[1] https://src.fedoraprojec
On Wed, Feb 5, 2025 at 2:00 PM Kevin Fenzi wrote:
> On Wed, Feb 05, 2025 at 01:42:17PM +0100, Fabio Valentini wrote:
> > On Wed, Feb 5, 2025 at 1:26 PM Artur Frenszek-Iwicki
> > wrote:
> > >
> > > We're currently in the middle of F42 branching + related freeze.
> > >
> > > > All builds that will
Here's the final (mostly) failed list. I was able to fix butt with a simple
header include patch:
$ grep failed rebuild_status
butt: failed, fixed with patch
dillo: failed, config specifically looks for fltk 1.3.
flwkey: failed, config specifically looks for fltk 1.3.
giac: failed, non-trivial fix
On Tue, Dec 10, 2024 at 9:45 AM Michel Lind wrote:
> On Mon, Dec 09, 2024 at 07:18:54AM -0600, Richard Shaw wrote:
> > Upstream has made a new release and it's not fully backwards compatible
> > with 1.3. The plan is to create a fltk13 compatibility package for
> proje
I did a rebuild of all affected packages in my COPR[1] and here are the
results. When I have time I'll notify package maintainers directly for
failed packages.
To be clear, I only tested whether the project built or not.
$ grep failed rebuild_status
butt: failed
dillo: failed
flwkey: failed
giac:
Upstream has made a new release and it's not fully backwards compatible
with 1.3. The plan is to create a fltk13 compatibility package for projects
which don't yet support 1.4.
I'll test in COPR builds first to see which packages cannot build with 1.4.
Dependent packages are:
OpenEXR_Viewers
Open
On Mon, Dec 2, 2024 at 6:34 AM Martin Gansser
wrote:
> Hi,
>
> when I try to compile cpu-x under fedora 41 it fails [1] with the
> following error message
[SNIP]
> CMake Error at data/CMakeLists.txt:41 (if):
> if given arguments:
>
> "STREQUAL" ""
>
> Unknown arguments specified
>
Most
It looks like openshadinglanguage has not made a release that's compatible
with OIIO 3.x so for now I'm abandoning my efforts.
I tried adapting a commit from upstream but it strangely only built for
F41...
Thanks,
Richard
--
___
devel mailing list -- d
Sorry for the delay... $LIFE and $DAYJOB got in the way. Will be picking
this back up soon.
Thanks,
RIchard
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Con
OpenImageIO 3 has been released and I plan on building in the next few days.
The following packages are affected:
$ fedrq wr -F "name" -s OpenImageIO-devel
blender
embree
luxcorerender
oidn
openshadinglanguage
usd
I will build in a side tag for Rawhide only unless someone has a compelling
reason
On Sat, Oct 26, 2024 at 9:07 AM Orion Poplawski wrote:
> On 10/26/24 05:44, Richard Shaw wrote:
> > On Fri, Oct 25, 2024 at 9:06 PM Orion Poplawski > <mailto:or...@nwra.com>> wrote:
> >
> > On 10/7/24 20:42, Richard Shaw wrote:
> > > Th
On Fri, Oct 25, 2024 at 9:06 PM Orion Poplawski wrote:
> On 10/7/24 20:42, Richard Shaw wrote:
> > There are some behind the scenes changes and although
> > fedabipkgdiff doesn't see any difference upstream bumped the soname out
> > of an abundance of caution.
> >
On Wed, Oct 23, 2024 at 2:37 AM Jan Grulich wrote:
> Hi,
>
> út 22. 10. 2024 v 20:51 odesílatel Richard Shaw
> napsal:
>
>> On Tue, Oct 22, 2024 at 11:45 AM Jan Grulich wrote:
>>
>>>
>>>
>>> On Tuesday, October 22, 2024, Richard Shaw w
On Tue, Oct 22, 2024 at 11:45 AM Jan Grulich wrote:
>
>
> On Tuesday, October 22, 2024, Richard Shaw wrote:
>
>> Just installed since I had an immediate need.
>>
>> Windows 10
>> SD Card detected in Windows disk manager
>> This version did not detect
Just installed since I had an immediate need.
Windows 10
SD Card detected in Windows disk manager
This version did not detect my SD card while the previous version did. USB
Flash drive detection seemed to work.
Thanks,
Richard
--
___
devel mailing list
No hurry, and probably not a big deal but just in case!
OpenImageIO 3.0.0 is in beta[1]. This includes removal of some log
deprecated API calls[2] that hopefully no one is using.
If I have time I'll do some test builds in COPR.
Thanks,
Richard
[1]
https://github.com/AcademySoftwareFoundation/Op
colrdx is FTBFS and is only really of interest to ham radio operators.
I submitted an issue upstream in July and there has been no activity.
Additionally the last time a commit was made was 4 years ago so I'm
considering it abandoned.
https://github.com/f4exb/colrdx
Thanks,
Richard
FAS: hobbes10
There are some behind the scenes changes and although fedabipkgdiff doesn't
see any difference upstream bumped the soname out of an abundance of
caution.
The following packages will need to be rebuilt but I don't expect any
issues since the abidiff was clean other than the soname change:
$ fedrq w
I have a report[1] of an issue with wsjtx installing on aarch64 only:
Problem: cannot install the best update candidate for package
wsjtx-2.7.0-3.fc40.aarch64
- nothing provides libm.so.6(GLIBC_2.2.5)(64bit) needed by
wsjtx-2.7.0-6.fc40.aarch64 from updates
- nothing provides libmvec.so.1(GLIB
I need a class again on how to do this... I remember years ago being told
we should try to come up with what the effective license is, so if the
package has sources that are both GPL--or-later and they have both GPL 2
and GPL 3 sources that the combination should be considered GPL-3-or-later.
Or s
On Mon, Sep 2, 2024 at 5:21 AM Miroslav Suchý wrote:
> Do you want to make Fedora 41 better? Please spend 1 minute of your time
> and try to run:
>
> dnf --releasever=41 --enablerepo=updates-testing --assumeno
> distro-sync
>
Here's my results, seems to be some issues with InsightToolkit, gu
Summary:
HP ENVY x360 (Ryzen 5 4500U w/ Intel SSD)
I've been running Fedora on my laptop for about 3 years and just now had
this issue and have reproduced it twice after fresh installs.
I have tested my memory 15+ times with Memtest86, multiple SMART checks on
the NVME drive, and 10 complete HP
On Tue, Jul 30, 2024 at 9:08 AM Miroslav Suchý wrote:
> As the SPDX Change slowly finishes I focused on the license that I
> regularly report as:
>
> warning: not valid neither as Callaway nor as SPDX, please check
>
> These are license tags that are hard to automatically parse. It include
> te
On Wed, Jul 3, 2024 at 11:03 PM Benson Muite
wrote:
> On 03/07/2024 22.15, Richard Shaw wrote:
> > smesh has not been updated to build with OpenCascade 7.8.x and upstream
> > appears dead.
> >
> > Since nothing in Fedora requires smesh with FreeCAD already being
&
smesh has not been updated to build with OpenCascade 7.8.x and upstream
appears dead.
Since nothing in Fedora requires smesh with FreeCAD already being retired I
plan to retire smesh as well.
Let me know if you want the package.
Thanks,
Richard
--
___
On Tue, Jul 2, 2024 at 9:55 AM Jerry James wrote:
> On Tue, Jul 2, 2024 at 8:51 AM Richard Shaw wrote:
> > I'm trying to do a test build of a new OpenImageIO release but when I
> try to build the package I get:
> >
> > Failed to resolve the transaction:
> > Pr
I'm trying to do a test build of a new OpenImageIO release but when I try
to build the package I get:
Failed to resolve the transaction:
Problem: package openvdb-devel-11.0.0-12.fc41.x86_64 from fedora requires
cmake(tbb) = 2020.3, but none of the providers can be installed
- package tbb2020.3-d
Forgot the link in my first email:
https://github.com/containers/podlet
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://docs.
Since `podman generate systemd` is deprecated, should podlet be packaged
for Fedora?
I really like how the systemd method works so I'm actually a little upset
it's deprecated, but I kinda understand the direction podman is going with
kubernetes config compatibility.
I don't really have a lot of t
I'm trying to reproduce the problem on the Fedora rawhide test machine but
it's running without error!
$ sudo systemctl status fail2ban.service
● fail2ban.service - Fail2Ban Service
Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; disabled;
preset: disabled)
Drop-In: /usr/lib/sys
On Sat, May 4, 2024 at 4:49 PM Carlos Rodriguez-Fernandez <
carlosrodrifernan...@gmail.com> wrote:
> The suggestion for one of the comments of using `/run/fail2ban(/.*)?`
> instead of `/run/fail2ban.*` doesn't work?
>
I try to be very careful with making changes in SELinux and I don't know
what t
I still don't understand SELinux and would appreciate an assist!
fail2ban-server is unable to create the socket file
/run/fail2ban/fail2ban.sock
There's a lot of custom SELinux policies and I'm unable to figure out what
needs to change.
https://bugzilla.redhat.com/show_bug.cgi?id=2279054
https:/
Just an observation...
I'm very happy for the assist, I don't have the time I used to for
packaging and the dependency chain for this particular package is "fun",
but as the primary maintainer for openexr, you can imagine my surprise as
this announcement.
Perhaps it would be a good idea to contac
On Tue, Feb 20, 2024 at 7:40 AM Brad Smith
wrote:
> I had this problem too. There is a new version of mock and
> more-core-config (not sure of name still getting first cup of coffee) in
> updates-testing that has the fix.
>
Ahh, updating mock didn't pull in mock-core-config. Both it and
distribu
On Tue, Feb 20, 2024 at 7:00 AM Miro Hrončok wrote:
>
>
> On 20. 02. 24 13:31, Richard Shaw wrote:
> > For about a week I've been seeing this when trying to test build
> packages for
> > rawhide locally:
> >
> > Transaction failed: Signature verificatio
For about a week I've been seeing this when trying to test build packages
for rawhide locally:
Transaction failed: Signature verification failed.
PGP check for package "bash-5.2.26-3.fc40.x86_64"
(/var/lib/mock/fedora-rawhide-x86_64/root/var/cache/dnf/fedora-2d95c80a1fa0a67d/packages/bash-5.2.26-3
Almost there but running into a build problem with Blender...
https://koji.fedoraproject.org/koji/taskinfo?taskID=112606258
---
/builddir/build/BUILD/blender-4.0.2/intern/cycles/scene/image_vdb.cpp: In
member function ‘bool ccl::ToNanoOp::operator()(const
openvdb::v11_0::GridBase::ConstPtr&)’:
/bu
On Mon, Jan 29, 2024 at 12:03 PM Jerry James wrote:
> For the second time in two days, running "fedpkg build" gave me a few
> dozen lines that say:
>
> warning: runaway fork() in Lua script
>
> before the usual build messages start appearing. Is this a known issue?
>
Just started seeing this af
On Mon, Jan 29, 2024 at 7:13 AM Sérgio Basto wrote:
> >
> > Well I just re-tried openvdb with _smp_build_ncpus 1 and it still
> > failed so I don't think we have a choice at this point. Perhaps it
> > was hitting the 4GB max per process due to being 32bit?
> >
>
> Have you try set in build the ul
On Mon, Jan 29, 2024 at 4:16 AM Jonathan Wakely wrote:
> On Sun, 28 Jan 2024 at 15:18, Richard Shaw wrote:
> >
> > Well I upped the memory to 10GB and got it to build but the issue on
> i686 with the wrong tbb package being pulled in has not been corrected by
> any of the
On Sun, Jan 28, 2024 at 9:55 AM Ben Beasley wrote:
> Blender already excludes i686:
>
>
> https://src.fedoraproject.org/rpms/blender/blob/8088da10c20e53ab0e1dd5de6fd3a2344bd288aa/f/blender.spec#_207
>
> So does prusa-slicer:
>
>
> https://src.fedoraproject.org/rpms/prusa-slicer/blob/44359e4b53c50
Well I upped the memory to 10GB and got it to build but the issue on i686
with the wrong tbb package being pulled in has not been corrected by any of
the 4 maintainers of the package. So I did a minimal update and changed the
tbb BR's from pkgconf to cmake and a scratch build completed pulling in t
On Wed, Jan 24, 2024 at 10:56 PM Mamoru TASAKA
wrote:
> Richard Shaw wrote on 2024/01/25 12:43:
>
> See:
>
> https://src.fedoraproject.org/rpms/build-constraints-rpm-macros/blob/rawhide/f/macros.build-constraints
>
> The macro attemps to reduce parallel make jobs when t
So with the tbb[1] update OpenVDB is one of the stragglers having issues
that need to be addressed before I can build OpenImageIO.
Looking at the releng rebuilt attempt it failed on ppc64le. I kicked off
the build again[2] and this time it failed on s390x:
https://kojipkgs.fedoraproject.org//work/
On Tue, Jan 16, 2024 at 5:36 PM Aleksei Bavshin
wrote:
> Ah, I misread the include path. It's our package that is too old :(
> https://src.fedoraproject.org/rpms/rapidjson/pull-request/4 should help.
>
It doesn't look like the pull request has gotten any attention. Perhaps
it's time to initiate
I'm working on getting a new dependency of one of my packages into Fedora:
https://github.com/socketio/socket.io-client-cpp/releases
After doing successful test builds locally in mock (no error output at all)
I used fedora-create-review but all the builds failed with:
In file included from
/buil
While it's only a warning, I would like to "fix" it.
When building flrig I'm seeing the following:
widgets/font_browser.cxx: In member function '__ct_base .constprop':
widgets/font_browser.cxx:202:52: warning: argument 1 value
'18446744073709551615' exceeds maximum object size 9223372036854775807
I plan to build OpenImageIO 2.5.x in rawhide in the near future.
Affected packages to be built in a side tag:
$ fedrq wr -F "name" -s OpenImageIO-devel
OpenColorIO
blender
embree
luxcorerender
oidn
openshadinglanguage
usd
Thanks,
Richard
FAS: hobbes1069
--
On Mon, Oct 30, 2023 at 7:49 AM Lukas Javorsky wrote:
> The possible remediation for this FTBFS packages are:
>
> Chromium -> Use bundled minizip library
> Libdigidocpp -> Use bundled minizip library
> OpenColorIO -> Don't upgrade minizip-ng to the new 4th version of API
> (stay with minizip-ng-3
Never mind, I hadn't realized fedpkg had grown the ability to do COPR
builds.
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://doc
I'm trying to test build packages before actually creating a side tag and
doing real builds.
I'm using rpkg to do the test builds but openshading language uses
RPMAutoSpec. I've tried creating empty commits to bump the release but it
does not appear to be working.
What's the work around?
Thanks,
Forgot to mention I'm doing the test builds here:
https://copr.fedorainfracloud.org/coprs/hobbes1069/OIIO/builds/
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
On Mon, Sep 25, 2023 at 2:11 AM Sandro wrote:
> On 24-09-2023 03:26, Richard Shaw wrote:
> > I haven't been able to find the new command in my email history to find
> > dependencies but my old script shows the following need to be rebuilt:
> >
> > ble
I haven't been able to find the new command in my email history to find
dependencies but my old script shows the following need to be rebuilt:
blender
krita
luxcorerender
OpenImageIO
usd
I'll try them in a COPR first to make sure there aren't any issues.
Thanks,
Richard
_
On Fri, Sep 1, 2023 at 9:02 AM Richard W.M. Jones wrote:
> On Fri, Sep 01, 2023 at 07:10:59AM -0500, Richard Shaw wrote:
> > Drive by comment because I found this thread interesting...
> >
> > What compression level was used for zstd? My understanding is that higher
>
Drive by comment because I found this thread interesting...
What compression level was used for zstd? My understanding is that higher
levels take longer to compress but decompression time remains virtually the
same.
Thanks,
Richard
___
devel mailing lis
On Wed, Aug 23, 2023 at 1:41 PM Steven A. Falco
wrote:
> On 8/23/23 02:22 PM, Miroslav Suchý wrote:
> > dnf --releasever=39 --setopt=module_platform_id=platform:f39 \
> > --enablerepo=updates-testing \
> > $(rpm -q fedora-repos-modular >/dev/null && echo
> --enablerepo=updates-testing-modular) \
Specifically I think this needs to be addressed if possible:
# dnf repoquery --whatrequires libchromaprint\* | grep x86_64
Last metadata expiration check: 0:02:55 ago on Sun 06 Aug 2023 10:10:31 AM
CDT.
acoustid-fingerprinter-0:0.6-31.fc38.x86_64
chromaprint-tools-0:1.5.1-8.fc38.x86_64
clementine-
On Sun, Aug 6, 2023 at 9:44 AM Sérgio Basto wrote:
> On Sun, 2023-08-06 at 08:04 -0500, Richard Shaw wrote:
>
> From what I can tell in the spec file[1] for chromaprint, the only thing
> that's supposed to depend on ffmpeg is the tools package, but it seems to
> hav
>From what I can tell in the spec file[1] for chromaprint, the only thing
that's supposed to depend on ffmpeg is the tools package, but it seems to
have found its way into libchromaprint[2] as well.
I'm trying to build a new version of codec2 with a soname change but I'm
hitting this:
DEBUG util.p
I plan to update codec2 to version 1.5.0 and will perform all rebuilds in a
side tag.
Affected packages:
baresip
ffmpeg
freedv
gnuradio
lpcnetfreedv
sdrangel
sdrpp
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe se
On Wed, Aug 2, 2023 at 7:14 AM Miroslav Lichvar wrote:
> On Wed, Aug 02, 2023 at 06:47:58AM -0500, Richard Shaw wrote:
> > I was poking around trying to fix the FTBFS problem with direwolf and it
> > looks simple enough. As it has built before for years I assume it's
>
I have orphaned qodem. I haven't used it in years and was only interested
during a brief revival of the good ole' BBS days many years ago.
https://src.fedoraproject.org/rpms/qodem
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
T
I was poking around trying to fix the FTBFS problem with direwolf and it
looks simple enough. As it has built before for years I assume it's related
to GCC 13.
Here's the error:
/builddir/build/BUILD/direwolf-1.6/src/direwolf.h:303:56: error: expected
declaration specifiers or '...' before string
On Thu, Jul 13, 2023 at 5:10 PM Kevin Kofler via devel <
devel@lists.fedoraproject.org> wrote:
> Richard Shaw wrote:
> > # FIXME This patch is completely meaningless in the context of C++.
> > # It is a workaround for a pyside2 build failure with Qt 5.15.9,
> > # p
I was able to work around that error but now hitting the following, and the
crumb trail I followed seems to indicate that this needs to be fixed in
Qt5, not PySide2[1]
In file included from
/builddir/build/BUILD/pyside-setup-opensource-src-5.15.10/redhat-linux-build/sources/pyside2/PySide2/QtGui/P
So it looks like upstream has no intention of supporting Python 3.12 in
Pyside2 (5.15.x series), only in Pyside6 which AFAIK requires Qt6.
https://bugreports.qt.io/browse/PYSIDE-2388
Porting is non-trivial and Python upstream does not provide a porting guide.
https://docs.python.org/3/c-api/unic
On Thu, Jul 6, 2023 at 5:41 AM Jonathan Wakely wrote:
> >
> > Wouldn't it be better to just update OpenCascade to its new upstream
> version in that sidetag as well instead of doing a compat package for it?
>
> Define better.
> To be clear, I'm not "doing a compat package" for it. I'm just
> chan
For anyone who didn't see discussion on the list OpenCOLLADA upstream
hasn't seen a commit since 2018 and no one has stepped up to port it to
pcre2.
I tried to convert it to use the bundled pcre as a stop gap to keep it
going a bit further but it installs the library instead of building
statically
On Wed, Jun 28, 2023 at 6:37 AM Richard Shaw wrote:
> On Wed, Jun 28, 2023 at 6:12 AM Vitaly Zaitsev via devel <
> devel@lists.fedoraproject.org> wrote:
>
>> Results: 37 builds succeeded, 19 failed.
>>
>> gnuradio
>>
>
> Issue filed upstream:
>
On Wed, Jun 28, 2023 at 6:12 AM Vitaly Zaitsev via devel <
devel@lists.fedoraproject.org> wrote:
> Results: 37 builds succeeded, 19 failed.
>
> gnuradio
>
Issue filed upstream:
https://github.com/gnuradio/gnuradio/issues/6735
Also, not all the maintainers may review the devel list as closely. In
On Mon, Jun 26, 2023 at 10:02 AM Michal Schorm wrote:
> > Moreover, it's designed to give the end users a simple workflow to build
> their own custom images.
>
> That's something I'd be interested in.
> I always have an USB drive (or several) with Fedora ISO(s) lying
> around, being handy from ti
> >
> > > > On Mon, 5 Jun 2023 17:53:59 -0500
> > > > Richard Shaw wrote:
> > > >
> > > > > I just saw this[1] on the packager dashboard:
> > > > >
> > > > > error: Could not create out
I just saw this[1] on the packager dashboard:
error: Could not create output directory
/builddir/build/BUILD/libftdi1-1.5/redhat-linux-build/doc/xml
Full log:
https://kojipkgs.fedoraproject.org/work/tasks/5182/101845182/build.log
Is this a known issue?
[1] https://koschei.fedoraproject.org/pack
On Mon, May 29, 2023 at 8:26 AM Sam Varshavchik
wrote:
> Richard Shaw writes:
>
> > error: possibly dangling reference to a temporary [-Werror=dangling-
> > reference]
> > 315 | const auto & parents =
> > dae.root().selectNodes("//*[@sid]/
OpenCOLLADA has been failing to build with gcc 13 due to[1]:
error: possibly dangling reference to a temporary
[-Werror=dangling-reference]
315 | const auto & parents =
dae.root().selectNodes("//*[@sid]/..");
The code in question[2] is:
// InstanceWithExtra and other with "ur
On Sat, May 27, 2023 at 4:48 AM Vitaly Zaitsev via devel <
devel@lists.fedoraproject.org> wrote:
> On 26/05/2023 14:07, Richard Shaw wrote:
> > Doxygen was updated from 1.9.6 to 1.9.7 which I would assume should be a
> > pretty harmless update
>
> Some Doxygen min
On a side note I love the packager dashboard!
I noticed that OpenColorIO builds in rawhide were failing[1] and took a
look at the logs and the errors seem to be around doxygen:
In file included from
/builddir/build/BUILD/OpenColorIO-2.2.1/src/bindings/python/PyOpenColorIO.h:18,
f
So subject kind of says it all, but to follow up, when I google Fedora
known good licenses I get this:
https://fedoraproject.org/wiki/Licensing:Main#SoftwareLicenses
Which uses the old license identifiers, so there's that. And
licensecheck is a PITA because I have to always add
"--shortname-schem
On Sun, Apr 23, 2023 at 4:09 AM Miroslav Suchý wrote:
> New version of fedora-license-data and license-validate has been released.
>
> NEW: the package fedora-license-data now contains BNF grammar which you
> can use. It is available in `/usr/share/fedora-license-data/grammar.lark`
>
You'll have
On Fri, Apr 21, 2023 at 3:39 PM Ben Cotton wrote:
> On Fri, Apr 21, 2023 at 4:05 PM Maxwell G wrote:
> >
> > What evidence shows that the group is ever shrinking? I often see Self
> > Introduction posts and new people interacting with project. I suppose
> > that whether they continue interacting
Not quoting anything in particular, just my opinion and a +1.
Being a solid Gen X'er I'm comfortable in both worlds. I will say that I've
found the large volume of emails between Fedora and MythTV (though it's
slowed in the last few years) occasionally overwhelming.
The first thing I do almost ev
On Tue, Apr 4, 2023 at 12:45 AM Miroslav Suchý wrote:
> Dne 04. 04. 23 v 3:20 Richard Shaw napsal(a):
>
> I have updated my licensecount script which summarises the licenses in a
> source and uses licensecheck to output SPDX licenses instead, but they
> output the "short&q
WARNING: This is a small rant...
I have tried to keep up with the emails on the devel list around this but I
admit that I haven't been able to devote the time to GROK them all.
I decided to look up my packages on src.fedoraproject.org (I'm still not
sure if it's showing me all packages I'm admin
On Wed, Mar 1, 2023 at 7:45 AM Daniel P. Berrangé
wrote:
>
> Fast forward 6 months and evidentally no one else was enthusiastic about
> updating the MinGW packaging guidelines, so I've taken on that task myself
> :-)
>
Thanks for volunteering! I converted one of my packages but honestly I've
had
On Wed, Feb 22, 2023 at 6:05 PM Miro Hrončok wrote:
> On 23. 02. 23 0:56, Richard Shaw wrote:
> > On Wed, Feb 22, 2023 at 2:52 PM Thomas Rodgers > <mailto:trodg...@redhat.com>> wrote:
> >
> > The f39-boost side tag builds have finished.
> >
> >
On Wed, Feb 22, 2023 at 2:52 PM Thomas Rodgers wrote:
> The f39-boost side tag builds have finished.
>
> The following packages FTBFS but the build logs provide no useful
> information -
> - OpenImageIO [[
> https://kojipkgs.fedoraproject.org//work/tasks/3952/97793952/build.log][build.log
> ]]
>
I currently have to disable tests for s390x[1] (and ppc64le) for likely
endianess issues.
Troubleshooting these is more than a little outside of my wheelhouse.
I hate keeping them disabled so I wanted to see if anyone could spare a few
cycles to investigate.
Thanks,
Richard
[1] https://github.c
On Sat, Feb 11, 2023 at 12:13 AM John Reiser wrote:
> On 2/10/23 19:57, Richard Shaw wrote:
> > So I know the s390x builders are down but I have an active BZ for tests
> failing with s390x so I figured what the heck, maybe doing a local
> mocbuild attempt using qemu could help h
So I know the s390x builders are down but I have an active BZ for tests
failing with s390x so I figured what the heck, maybe doing a local
mocbuild attempt using qemu could help here like it did with aarch64.
Well at first everything seemed to be working as normal but all of the repo
package GPG c
On Fri, Feb 10, 2023 at 9:41 AM Scott Talbert wrote:
> Hi all,
>
> What I'm unclear about is whether there are any RPM Fusion users left -
> I'm unsure of how to repoquery RPM Fusion.
>
I have both RPM Fusion Free and Non-Free enabled and ran my
"needs_rebuilding" script against all the library
On Tue, Jan 24, 2023 at 7:20 AM Richard Shaw wrote:
> hobbes1069 (9):
> cqrlog - Fails for some weird lazbuild issue I don't understand
> flnet - Spec conditional oops. Fixed.
> flrig - Needed cstdint. Fixed
> freecad - Needs cstdint. Working on it.
> gmsh - Needed cstdin
hobbes1069 (9):
cqrlog - Fails for some weird lazbuild issue I don't understand
flnet - Spec conditional oops. Fixed.
flrig - Needed cstdint. Fixed
freecad - Needs cstdint. Working on it.
gmsh - Needed cstdint. Fixed.
openCOLLADA - error: possibly dangling reference to a temporary. Don't know
how t
On Fri, Jan 20, 2023 at 2:29 PM Demi Marie Obenour
wrote:
>
> My general rule is that a security fix is worth backporting a SONAME change
> for, if there is no way to backport the patch.
>
In this case all the Fedora branches are recent enough but EL 7 and EL 8
are not and are impractical to fix
1 - 100 of 1146 matches
Mail list logo
