On 14-08-2024 18:45, Kevin Fenzi wrote:
On Wed, Aug 14, 2024 at 04:30:09PM GMT, Sandro via devel wrote:
On 14-08-2024 15:32, Ben Beasley wrote:
Given the timing and the complexity of the dependency chains involved
here, I used provenpackager privilege to start rebuilding grpc in both
F42 and
On 14-08-2024 16:45, Dan Horák wrote:
On Wed, 14 Aug 2024 16:30:09 +0200
Sandro via devel wrote:
On 14-08-2024 15:32, Ben Beasley wrote:
Given the timing and the complexity of the dependency chains involved
here, I used provenpackager privilege to start rebuilding grpc in both
F42 and F41
On 14-08-2024 15:32, Ben Beasley wrote:
Given the timing and the complexity of the dependency chains involved
here, I used provenpackager privilege to start rebuilding grpc in both
F42 and F41, which will unblock many of the other packages that need to
be rebuilt.
To do so, I added a BuildReq
Hi,
re2-20240702 just landed in rawhide [1]. The update comes with an soname
bump from libre2.so.9 to libre2.so.11 and breaks quite some packages [2]:
$ fedrq wrsrc -Xs -F name re2
CuraEngine_grpc_definitions
bloaty
ceph
credentials-fetcher
dnsdist
grpc
libarrow
libphonenumber
mtxclient
nheko
On 11-08-2024 18:47, Javier Jardón via devel wrote:
I'd like to report here that the update of buildstream package to
2.x will be incompatible with current 1.x version
For users of BuildStream, which will eventually be upgraded to
BuildStream 2 when F41 arrives, see upstream's porting guide:
On 24-07-2024 07:50, Sandro via devel wrote:
On 23-07-2024 20:30, Sandro via devel wrote:
PyGithub will be updated to 2.3.0 in rawhide soon. This is a major
update and according to upstream's changelog [1] it comes with
breaking changes. The first update containing breaking changes is
1
On 08-08-2024 10:31, Tomi Lähteenmäki wrote:
"Hijacking" this thread I stumbled up on this also some months ago in
one of my packages when I was doing builds locally with "mock". The
tests were failing so I had to create a patch [1] to make sure the
Unix-socket is created in a path which does n
On 31-07-2024 18:50, Sandro via devel wrote:
On 31-07-2024 17:34, Sandro Mani wrote:
See https://bugzilla.redhat.com/show_bug.cgi?id=2302033. The source of
the issue is that the Requires: environment(modules) in rpm-mpi-hooks
(which is a BuildRequirement of openmpi/mpich) did not result in
On 31-07-2024 17:34, Sandro Mani wrote:
See https://bugzilla.redhat.com/show_bug.cgi?id=2302033. The source of
the issue is that the Requires: environment(modules) in rpm-mpi-hooks
(which is a BuildRequirement of openmpi/mpich) did not result in
environment-modules getting installed, which brok
Hi,
It seems something is going on with RPM metadata generation.
With the latest update of openmpi the generated metadata has changed:
$ rpm -q --provides -p openmpi-5.0.5-1.fc41.x86_64.rpm
config(openmpi) = 5.0.5-1.fc41
libmpi.so.40()(64bit)
libmpi_java.so.40()(64bit)
libmpi_mpifh.so.40()(64bi
On 23-07-2024 20:30, Sandro via devel wrote:
PyGithub will be updated to 2.3.0 in rawhide soon. This is a major
update and according to upstream's changelog [1] it comes with breaking
changes. The first update containing breaking changes is 1.59.0. We are
currently on 1.58.2.
Please t
Hi,
PyGithub will be updated to 2.3.0 in rawhide soon. This is a major
update and according to upstream's changelog [1] it comes with breaking
changes. The first update containing breaking changes is 1.59.0. We are
currently on 1.58.2.
Please take a look yourself if it affects your package.
On 15-07-2024 10:24, Pavel Raiskup wrote:
TL;DR: We plan to start monitoring build activity in Copr projects.
If no builds appear for a long time in these "rolling" chroots (such as
Fedora Rawhide), we'll disable such chroots, preserve the built results
for a while, and then delete them if no act
On 09-07-2024 17:22, David Bold wrote:
Sandro wrote:
On 09-07-2024 17:01, David Bold wrote:
Is it possible to have a PR without any code changes?
Is there an alternative, recommended way to ask for rebuilds?
Specifically in the case of %autorelease, you can bump the release with
an empty commi
On 09-07-2024 17:01, David Bold wrote:
Is it possible to have a PR without any code changes?
Is there an alternative, recommended way to ask for rebuilds?
Specifically in the case of %autorelease, you can bump the release with
an empty commit:
git commit --allow-empty -m 'Rebuild for ...'
-
15 matches
Mail list logo
