Fedora Workstation 40 aarch64 download -- How to run Live CD installer?
by Brian Masney
Hi all,
I want to put Fedora 40 on my Lenovo Thinkpad x13s laptop, which is an
aarch64-based laptop with a Qualcomm SoC. I downloaded the Fedora raw
image from [1], and I can boot from USB using the directions at [2].
All of the other supported architectures have an ISO available,
however aarch64 only has a raw image available.
In the past, I would dd the Fedora image directly to my nvme drive,
however this time I'd like to go through the installer so that I can
easily setup LUKS encryption on my nvme drive through the installer.
The raw image doesn't have the installer, and I didn't have luck
installing the anaconda-livecd package.
Is there a Live ISO available for aarch64 anywhere with an installer?
I looked on the alternative downloads page [3] and the only ISO is for
KDE.
[1] https://fedoraproject.org/workstation/download
[2] https://fedoraproject.org/wiki/Thinkpad_X13s
[3] https://alt.fedoraproject.org/alt/
Brian
1 hour, 51 minutes
LLVM Packaging Ideas for Fedora 41
by Tom Stellard
Hi,
After each Fedora release we do a retrospective with the LLVM package maintainers
and talk about how we can improve the LLVM packages[1] in Fedora. We've come up
with some ideas for Fedora 41 that we'd like to share to raise awareness and
get feedback. Right now these are just ideas, and we plan to write up a formal
change proposal once we have decided which of these we are going to implement:
* Spec file merge. We plan to merge the clang, compiler-rt, and libomp packages
in with llvm and have them be sub-packages of the llvm package. This will allow
us to use the build configuration recommended by upstream and also make it possible
to optimize the packages using Profile-Guided Optimizations (PGO).
* Build compat packages (e.g. llvm18) as early as possible. When we package a new
major release of llvm, we create a compat package so that packages that aren't
compatible with the new version can still use the old version. In the past, we've
waited to introduce the compat packages until the new version of LLVM was ready
(typically during the Beta Freeze). However, this proved to be an issue this
release for packages the were ready to switch to the compat packages early in
the release cycle, but then had to wait for Beta freeze.
* Switch to python-style compat/main packages. In order to make the packaging more
consistent between the main package (e.g. llvm) and the compat package (e.g. llvm18),
we would retire the un-versioned dist-git for llvm, and create a new versioned dist-git
for each new release (e.g. llvm19, llvm20, llvm21 etc.). We would then designate one
of these as the 'main version', and that version would produce binary rpms that look
like the current main package (i.e. llvm-libs instead of llvm19-libs).
* Invert the order of compat/main packages. Instead of having the compat package be
the old version, and the main package be the new version, we would have the compat package
be newer and the main package be older. This would allow us to introduce a new version of
llvm without impacting other packages that depend on the main version of LLVM.
If anyone has any feedback on these ideas we'd like to hear it and are happy to discuss
these more.
Thanks,
Tom
[1] LLVM Packages are: llvm, clang, compiler-rt, libomp, lld, lldb, llvm-test-suite, libclc,
llvm-bolt, libcxx, mlir, flang, python-lit, and polly.
2 hours, 20 minutes
Schedule for Monday's FESCo Meeting (2024-05-20)
by Stephen Gallagher
Following is the list of topics that will be discussed in the
FESCo meeting Monday at 19:00 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-05-20 19:00 UTC'
Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda
= Discussed and Voted in the Ticket =
#3210 Change: Perl 5.40
https://pagure.io/fesco/issue/3210
APPROVED (+5, 0, -0)
#3209 Change: Node.js 22.x by default
https://pagure.io/fesco/issue/3209
APPROVED (+3, 0, -0)
#3208 Change: Fedora Miracle
https://pagure.io/fesco/issue/3208
APPROVED (+5, 0, -0)
#3207 Change: Drop Mandatory Requires on JRE
https://pagure.io/fesco/issue/3207
APPROVED (+4, 0, -0)
= Followups =
#3203 Change: Replace Redis with Valkey
https://pagure.io/fesco/issue/3203
#3205 Request exception to permit shipping pre-built, signed SGX
enclave binaries in Fedora
https://pagure.io/fesco/issue/3205
= New business =
#3212 Exception request to ship prebuilt macOS binaries in asahi-installer
https://pagure.io/fesco/issue/3212
= Open Floor =
For more complete details, please visit each individual
issue. The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda
If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
2 hours, 48 minutes
Intention to unretire and rename pyftpdlib
by Sandro
Hi,
I intend to unretire pyftpdlib [1] and rename the base package to
python-pyftpdlib in line with current Python Packaging Guidelines. The
package has been retired for more than eight weeks. So it will require a
re-review.
Since only the base package (SRPM) will be renamed, I'm wondering if it
needs any Obsoletes and/or Provides. The name of the sub package will
remain unchanged: python3-pyftpdlib.
I don't think it's needed. But I'd like to hear from more experienced folks.
I need pyftpdlib as a dependency for another package I've already
prepared. It appears to be still maintained, but was retired due to an
FTI bug [2] not being attended to.
[1] https://src.fedoraproject.org/rpms/pyftpdlib
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2220082
Cheers,
--
Sandro
FAS: gui1ty
Matrix: Penguinpee
Elsewhere: [Pp]enguinpee
3 hours, 16 minutes
Introduction: Adrian Edwards - Fedora Community Architect Intern
by Adrian Edwards
Hello Fedora devel mailing list,
My name is Adrian and i'm a CS student at RIT who is minoring in Free and Open Source Software. I wanted to send this out briefly to introduce myself.
I'll be working as a Fedora Community Architect Intern during my time with Red Hat in Boston (US/Eastern TZ) and I'm excited to learn about the Fedora community. One particular recurring interest of mine has been wondering how to encourage more of the people who benefit from open source to support it or give back in some way so that working on smaller, independent open source passion projects that others rely on can become as common as making a living working on corporate-controlled open source and improve the stability of the system as a whole (here's an [amazing podcast episode](https://www.npr.org/2024/05/17/1197959102/open-source-xz-hack) i recently heard about the recent XZ hack that makes a really good point about public goods at the end).
Maybe this is a bigger goal than I'll realistically be able to tackle in the next few months in my current role, but I hope to at least learn as much as possible about Fedora and surrounding communities to see where there may be opportunities for me to make a difference.
If you need to reach me, I'll do my best to monitor the following places:
- Fedora Discussions: @moralcode
- Matrix: @moralcode:fedora.im
- Email: moralcode(a)fedoraproject.org
Adrian Edwards
5 hours, 46 minutes
F38 is End of Life
by Samyak Jain
Hello all,
Fedora Linux 38 reached its end of life for updates and support on
2024-05-21. As of that date, no further updates of any kind, including
security updates or security announcements, will be available for
Fedora Linux 38. The distribution ceased pushing any updates,
including those to the stable release. On the other hand, Fedora Linux
39 will continue to receive updates until approximately one month
after the release of Fedora Linux 41. The maintenance schedule of
Fedora Linux releases is documented on the Fedora Project wiki [1].
For instructions on upgrading from a previous release of Fedora Linux
to a version receiving updates, the Fedora Project wiki provided
comprehensive guidance [2].
Regards,
Samyak Jain
Fedora Release Engineering
[1] https://docs.fedoraproject.org/en-US/releases/lifecycle/#_maintenance_sch...
[2]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades
7 hours, 13 minutes
Fedora Elections - Voting is now open!
by Aoife Moloney
Hi all,
The F40 elections have now officially opened after a little delay. You can
find all of the candidate details in the Elections blog post[1]. We have
open positions in Fedora Council, EPEL Steering Committee, Mindshare and
Fedora Engineering Steering Committee (FESCo) and the voting period will
close on Thursday 30th May @ 23:59:59 UTC sharp so please do take some time
to read the wonderful candidate interviews we have received for the various
open positions, cast your vote and dont forget to claim your Fedora badge
too!
[1] https://communityblog.fedoraproject.org/elections-voting-is-now-open/
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
7 hours, 32 minutes
GRUB2 rebase (from 2.06 to 2.12) landing soon on rawhide
by Leo Sandoval
Hi team,
We (the Red Hat bootloader team) are completing the work of
rebasing/reviewing/testing current rawhide patches, from GRUB2 2.06 to
2.12, so at
some point in the near future these would land finally into rawhide. Once
everything is in place, we would like your help to start testing the
package and report any boot issue found.
If there is any concern on this work, please let me know.
Regards,
Leo
8 hours, 49 minutes
Intention to retire mlocate
by Michal Sekletar
Hi everyone,
We have had a plocate as a drop-in replacement for mlocate for quite a
while now. My intention is to retire the mlocate package next week in order
to prevent duplication and so that we can focus only on plocate
going forward.
Have a nice weekend,
Michal
9 hours, 48 minutes
Re: Spec file using github repo - not tarball
by Tom Hughes
On 08/05/2024 21:36, Kenneth Goldman wrote:
> Is it possible for a .spec file to clone a github.com repo rather than
> download a tarball? Can someone link to a working example?
No, but github can give you a tar ball for any ref you want so why
would you need/want to?
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/
9 hours, 58 minutes