Brad Bell wrote on 2024/01/18 14:00:
I got the Result in the subject above for the following build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=111912575
Looking at the corresponding root.log
https://kojipkgs.fedoraproject.org//work/tasks/2575/111912575/root.log
does not indicate to me w
OLD: Fedora-Rawhide-20240115.n.0
NEW: Fedora-Rawhide-20240117.n.0
= SUMMARY =
Added images:6
Dropped images: 1
Added packages: 21
Dropped packages:1
Upgraded packages: 257
Downgraded packages: 0
Size of added packages: 7.47 GiB
Size of dropped packages
Announcing the creation of a new nightly release validation test event
for Fedora 40 Rawhide 20240117.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
Plese note that as part of the update to Gedit 46, the following
packages will break ABI:
* amtk: renamed to libgedit-amtk, review needed:
https://bugzilla.redhat.com/show_bug.cgi?id=2258912
* tepl
* gedit
Affected packages are gedit-plugins which needs to be updated to match
gedit, and (gnome
On Tue, Jan 16, 2024 at 02:50:43PM -0700, Jerry James wrote:
> Given the problems we had with font packages not being rebuilt in the
> last mass rebuild, can we ensure that the mass rebuild script uses
> "git push --no-verify" instead of plain "git push"?
>
> See:
> - https://bugzilla.redhat.com/s
Hello Tristan,
We store the data in json format. You can access and download the data directly
at our main page at the bottom - "Download collected data". Or via
https://log-detective.com/download
Cheers
Jiri
--
___
devel mailing list -- devel@lists.f
I'll be building boost, tbb, and the packages that depend on them in
the f40-build-side-81691
side tag over the next few hours (in advance of the mass rebuild tomorrow).
If your package gets a "Rebuilt for Boost 1.83.0" comment, please
don't rebuild it in rawhide, we're building it in the side tag
Text Log:
https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-01-17/fedora-coreos-meeting.2024-01-17-16.29.log.txt
HTML Log:
https://meetbot.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2024-01-17/fedora-coreos-meeting.2024-01-17-16.29.log.html
Text Minutes:
https:/
I attempted a quick check:
$ repoquery -q --repo=rawhide -l -a | tee >(
grep -E '^/usr/bin/[^/]+$' | sort -u | xargs -n 1 basename >
bin.txt
) | grep -E '^/usr/sbin/[^/]+$' | sort -u | xargs -n 1 basename
> sbin.txt
$ wc -l bin.txt sbin.txt
31229 bin.txt
Hello Folks,
I hope this email finds you well. I am writing to inform you about a
slight adjustment in our schedule for the upcoming mass rebuild which
was planned to happen on Jan 17, 2024. As per the discussion in our
releng weekly call today, due to an unexpected delay in merging the
side tag c
Hi all,
Per the Fedora Linux f40 schedule [1] we will be having a mass rebuild on
2024-01-17 for Fedora f40. We are running this mass rebuild for the
changes listed in:
https://pagure.io/releng/issues?status=Open&tags=mass+rebuild&tags=f40&tags=changes
This mass rebuild will be done in a side ta
On Wed, Jan 17, 2024 at 12:34 Jiri Kyjovsky wrote:
> Hey, Fedora devs!
>
> Ever find yourself lost in the labyrinth of build logs, desperately seeking
> the elusive culprit behind a failed build? Enter Log Detective – your
> future personal AI guru dedicated to unravelling the mysteries of build l
Dne 17. 01. 24 v 12:45 Priscila Gutierres napsal(a):
Hello James,
I started some months ago as a maintainer and I have been learning
since then.
One important thing I've learned is to ask if "this package should be
kept or should it be retired?"
Good hint is typically in dist-git Pagure,
Hello,
I'm orphaning $SUBJ as I have no longer use for it:
https://src.fedoraproject.org/rpms/rubygem-rubygems-mirror
(Also it fails to build with Ruby 3.3.)
Regards,
Pavel
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send
> On 17 Jan 2024, at 10:57, Jakub Kadlcik wrote:
>
> Hello,
> I just wanted to quickly announce a small project I did in collaboration with
> the Packit folks.
>
> Do you have some tools or services that perform actions on all currently
> active Fedora releases? And do you have to manually u
Hello James,
I started some months ago as a maintainer and I have been learning since
then.
One important thing I've learned is to ask if "this package should be kept
or should it be retired?"
If you want to start to contribute, you can send PRs bumping or fixing
opened bugs first, and I can
help
Hey, Fedora devs!
Ever find yourself lost in the labyrinth of build logs, desperately seeking
the elusive culprit behind a failed build? Enter Log Detective – your
future personal AI guru dedicated to unravelling the mysteries of build log
failures within the RPM community.
*What is Log Detective
Hi All,
I am not sponsored into the packager group yet, but I would like to begin by
maintaining a package that is on this list as "orphaned" however, it is very
difficult to understand which package(s) might be suitable for a newcomer like
me. Any help, advice, or suggested package would be gr
Thanks, that is exactly the message I wanted to tell.
Perhaps I should keep corner cases to myself until someone actually hits
them. It has clearly confused people and created unnecessary reactions.
Conflict will arise only when configuration change done by administrator
were not complete.
O
Please, Stephen, would you please read what I wrote, not what Kevin
wrongly deducted?
The change I made in dnsmasq does not conflict with systemd-resolved in
default configuration or if configured correctly. I have wrote scenario,
when it can conflict and how to fix it. So no, there is no need
Hello,
I just wanted to quickly announce a small project I did in collaboration
with the Packit folks.
Do you have some tools or services that perform actions on all currently
active Fedora releases? And do you have to manually update their list every
time a new Fedora release is branched or EOLed
On 1/16/24 15:54, Tom Hughes via devel wrote:
On 16/01/2024 23:49, Richard Shaw wrote:
On Tue, Jan 16, 2024 at 5:36 PM Aleksei Bavshin
mailto:aleba...@fedoraproject.org>> wrote:
Ah, I misread the include path. It's our package that is too old :(
https://src.fedoraproject.org/rpms/rapid
22 matches
Mail list logo
