Hello everyone,
Please join us at the next Open NeuroFedora team meeting on Monday, 29
January at 13:00 UTC. The meeting is a public meeting, and open for
everyone to attend. You can join us over on Matrix in the Fedora Meeting
channel:
https://matrix.to/#/#meeting:fedoraproject.org
You can
I'm trying to add mingw build support to the fmt package spec. I've done
this previously with the pugixml and zipios packages, and submitted the
spec diffs to the package maintainer of those.. Both packages use cmake.
Both in the %build section use %cmake then %cmake_build, and in the
%install sect
For mingw the more recent "%cmake_build" and "%cmake_install" have never
been implemented (one could add them [1]).
For mingw, the most common approach is
%build
%mingw_cmake
%mingw_make_build
%install
%mingw_make_install
# Don't forget this one
|%mingw_debug_install_post|
See also [1] for an
On Fri, Jan 26, 2024 at 08:46:08PM +0100, Jacek Migacz wrote:
> Dear Community!
>
> My name is Jacek Migacz; a software engineer from Poland.
> I'm currently maintaining curl and emacs on Red Hat Enterprise Linux.
> I am eager to learn from the collective wisdom of the community and
> contribute i
On Sat, Jan 27, 2024 at 04:26:50AM +, Neftalí Yagua wrote:
> Dear Community!
>
> My name is Neftalí Yagua, a Software Engineer from Venezuela since 2004,
> I'm worked with Linux since 1997, my beginnings with RHEL have been with
> RedHat, but I have been using Fedora for about 10 years, and I
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 4 maintainers of the package.
I fixed tbb to stop installing tbb32.pc so the underl
Hello, Ben.
On Sunday, 28 January 2024 at 19:43, Ben Beasley wrote:
> In one week, 2024-02-04, or slightly later, I plan to update abseil-cpp from
> 20230802.1 to 20230116.0 (Abseil LTS branch, Jan 2024)[1] in side tags for
Correct me if I'm wrong, but this looks like a downgrade:
$ rpmdev-vercmp
On 29-01-2024 11:16, Dominik 'Rathann' Mierzejewski wrote:
Hello, Ben.
On Sunday, 28 January 2024 at 19:43, Ben Beasley wrote:
In one week, 2024-02-04, or slightly later, I plan to update abseil-cpp from
20230802.1 to 20230116.0 (Abseil LTS branch, Jan 2024)[1] in side tags for
Correct me if
On Fri, 26 Jan 2024 at 12:29, Florian Weimer wrote:
> In the past, this kind of problem would have just compiled and resulted
> in a run-time error when the Python extension module is loaded. In some
> cases, issues went completely unnoticed because the Python bindins were
> unused. But with GCC
Sorry for the late action. I've merged PR for mozc.
Thanks,
On Mon, Jan 29, 2024 at 3:43 AM Ben Beasley wrote:
>
> In one week, 2024-02-04, or slightly later, I plan to update abseil-cpp
> from 20230802.1 to 20230116.0 (Abseil LTS branch, Jan 2024)[1] in side
> tags for F40/Rawhide. If I miss ge
Good evening folks,
FESco previously approved a requirement[1] that Spin/Labs owners send a
keepalive request in order to keep building the spin or lab. I have
opened Pagure issues[2] for all Spins and Labs for this release[3].
If you are the owner of one of those spins and labs, please reply in
Hi,
I intend to get stgit unretired and want to maintain it in the future.
The package has been in Fedora up to f38 but has since been orphaned
and, following that, retired. The reason for orphaning it was lack of
time of the maintainer, especially as stgit got rewritten in Rust and
required
Hello all,
I recorded a very short video showing how you can contribute to the Log
Detective project.
https://www.youtube.com/watch?v=_-O7ryKCnlQ
Any help will be greatly appreciated :-)
Jakub
On Wed, Jan 17, 2024 at 8:26 PM Jiri Kyjovsky wrote:
> Hello Tristan,
>
> We store the data in json
Miroslav,
Could you please double-check this change? I noticed that in spacebar,
LicenseRef-KDE-Accepted-GPL was the actual name of a license file in the
%files section; this was replaced with (GPL-2.0-only OR GPL-3.0-only),
which causes the package to FTBFS.
Looking at the grep output you o
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 4 maintainers of the pa
On Sun, 2024-01-28 at 15:57 -0600, Richard Shaw wrote:
> 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:
> >
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 Wed, Jan 24, 2024 at 05:38:59PM +0100, Miro Hrončok wrote:
> infinipath-psm honli
I think this project should be retired. The upstream repo has been archives
with a message that Intel no longer supports this project.
I'll rebuild mpich without this dependency.
Zbyszek
--
On Thu, Jan 25, 2024 at 02:48:19PM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Jan 25, 2024 at 03:25:02PM +0100, Sandro wrote:
> > On 24-01-2024 17:38, Miro Hrončok wrote:
> > > Dear maintainers.
> > >
> > > Based on the current fail to build from source policy, the following
> > > package
I opened a PR on calligra[1] at the leaf of the remaining i686
dependency chain to start the process of dropping i686, because even if
we get openvdb working now, there’s no good reason to keep i686 versions
of these packages in the future. The EncourageI686LeafRemoval Change was
specifically d
On Mon, 29 Jan 2024 at 13:03, Richard Shaw wrote:
>
> 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 i
Hey Folks,
KDE SIG x Fedora QA hosts the KDE Plasma 6 Test Week.
If you are willing to test new Desktop Environments or use KDE
for some time; this is your time.
Contribute to testing the new KDE and finding bugs ahead of the F40 release.
The instructions are simple, and can be found in the wiki
Following is the list of topics that will be discussed in the
FESCo meeting Monday at 19:30 UTC in #meeting:fedoraproject.org
on Matrix.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2024-01-29 19:30 UTC'
Links to all issues to be d
Hi all,
Per the Fedora Linux f40 schedule and the challenges [1], we started a
mass rebuild for Fedora Linux f40 on 2024-01-22. We did a mass
rebuild for Fedora Linux f40 for changes like:
- https://fedoraproject.org/wiki/Changes/GNUToolchainF40
- https://fedoraproject.org/wiki/Changes/Java21
che
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?
It looks like I am not the only one to encounter this:
https://github.com/QubesOS/qubes-issue
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
https://bugzilla.redhat.com/show_bug.cgi?id=2254463 reappeared, this
time on Fedora 39. The fix is known, it just needs to get built and
released.
On Mon, Jan 29, 2024 at 1:35 PM Richard Shaw wrote:
>
> On Mon, Jan 29, 2024 at 12:03 PM Jerry James wrote:
>>
>> For the second time in two days, ru
Hello folks,
before all, I want to thank everyone putting their time in reviewing new
package requests! That is a key task in distinguish Fedora among the
other Linux distribution and ensure we have high quality packages in our
repositories.
That said, I'd like to make a request and maybe make
Dne 29. 01. 24 v 13:58 Ben Beasley napsal(a):
Could you please double-check this change? I noticed that in spacebar, LicenseRef-KDE-Accepted-GPL was the actual name
of a license file in the %files section; this was replaced with (GPL-2.0-only OR GPL-3.0-only), which causes the
package to FTBFS
Logs and minutes:
https://zbyszek.fedorapeople.org/fesco-2024-01-29.2024-01-29-19.30.log.html
https://zbyszek.fedorapeople.org/fesco-2024-01-29.2024-01-29-19.30.log.txt
https://zbyszek.fedorapeople.org/fesco-2024-01-29.2024-01-29-19.30.minutes.html
https://zbyszek.fedorapeople.org/fesco-2024-01-29.
I've orphaned gnome-translate and libtranslate packages.
Both are unmaintained upstream more than a decade and do not work
nowadays at all.
For replacement just use translate-shell package (cmdline only).
BTW, executable name "/usr/bin/translate" is now free (once upon a time
someone wanted
nirik ran a script that checks for versioning issues in Rawhide today,
and it found several: https://pagure.io/releng/issue/11922#comment-893797
Some of these followed a pattern, so I figured a reminder was in order.
In all these cases, a new version was pushed to Rawhide, then "reverted"
some
nirik ran a script that checks for versioning issues in Rawhide today,
and it found several: https://pagure.io/releng/issue/11922#comment-893797
Aside from rogue version downgrades (see other mail), a few of these
followed a different pattern: problems with snapshot versioning.
1. patool: hig
On Mon, 2024-01-29 at 15:43 -0800, Adam Williamson wrote:
> nirik ran a script that checks for versioning issues in Rawhide
> today,
> and it found several:
> https://pagure.io/releng/issue/11922#comment-893797
>
> Some of these followed a pattern, so I figured a reminder was in
> order.
> In al
On Tue, Jan 30, 2024 at 1:00 AM Sérgio Basto wrote:
>
(snip)
> yes rawhide user should use dnf distro-sync not dnf upgrade
It is better, yes, but it is not *required*.
> https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_rawhide_is_allowed_to_lag_temporarily
This is a comp
Sérgio Basto wrote:
> yes rawhide user should use dnf distro-sync not dnf upgrade
+1. Rawhide EVRs should be allowed to go backwards, that is an integral part
of being a development branch.
Kevin Kofler
--
___
devel mailing list -- devel@lists.
On 2024-01-29 16:00, Sérgio Basto wrote:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_rawhide_is_allowed_to_lag_temporarily
you may do a new build with lower EVR
That is not what that guideline says. It says the Rawhide build can be
lower-versioned than a current bu
Hey folks! You may have noticed unpredictable openQA test failures on
Rawhide updates ATM. This is mainly because of the mass rebuild. All the
packages from the mass rebuild have been tagged into the buildroot repo
(which the openQA tests use), so now there are far more on-the-fly
updates than
Miro Hrončok wrote on 2024/01/25 1:38:
Dear maintainers.
Based on the current fail to build from source policy, the following packages
should be retired from Fedora 40 approximately one week before branching.
5 weekly reminders are required, hence the retirement will happen
approximately in 5 w
39 matches
Mail list logo
