attend.
The meeting will be at the regular date/time of Tuesday 05/06 at 15:00 UTC
and the video link is https://meet.google.com/poh-xmxm-qyc.
--
Jason Brooks
He/Him
Senior Manager, Community Architects & Infrastructure
Red Hat Open Source Program Office (OSPO)
https://community.redh
> Zbigniew Jędrzejewski-Szmek writes:
> Let's take a step back. Does it make sense to implement complicated
> and fragile scriptlets in packages?
No, of course not.
> Can we *please* get rid of this footgun that has been a continous
> source of problems?
The mantra on the packaging committ
> maxwell--- via devel-announce
> writes:
> fedscm-admin cqi, ignatenkobrain, limb, 3 weeks
> ago
> mohanboddu, orphan, tibbs
>
I can't think of any reason this shouldn't simply be retired. All of
the
For what it is worth I was able to build it on Fedora 41:
```
Checking for unpackaged file(s): /usr/lib/rpm/check-files
/home/jason/rpmbuild/BUILD/thunderbird-128.4.2-build/BUILDROOT
Wrote: /home/jason/rpmbuild/SRPMS/thunderbird-128.4.2-1.fc41.src.rpm
Wrote:
/home/jason/rpmbuild/RPMS/ppc64le
Thank you for the PR, I have merged it.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
Thank you for the review! I will start reviewing these for you this evening!
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraprojec
URL: https://people.redhat.com/jmontleo/python-durationpy.spec
SRPM URL:
https://people.redhat.com/jmontleo/python-durationpy-0.9-1.fc41.src.rpm
Source URL: https://github.com/icholy/durationpy
Thank you!
Jason
--
___
devel mailing list -- devel
> Laurent Rineau writes:
> The result is that the following
> packages no longer build (F42FTBFS, RAWHIDEFTBFS):
> - prusa-slicer
> https://koji.fedoraproject.org/koji/taskinfo?taskID=124921682
Just so I don't forget (as I have no time to dig into this today), I see
some related information
ct.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not rep
DvE3hbmLUo
- Streamlining bootable container workflows with podman-bootc -
https://www.youtube.com/watch?v=uLPyeXmIdyE
[1] https://fedoramagazine.org/get-involved-with-fedora-bootable-containers/
[2] https://gitlab.com/fedora/bootc/tracker/-/issues
[3] https://gitlab.com/fedora/bootc/tracker/-/issues/24
l@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
--
Jason Montleon| email: jmont...@redhat.com
Red Hat, Inc. | gpg key: 0x069E3022
Cell: 508-496-0663| irc: jmontleo / jmontleon
--
_
> Jiri Konecny writes:
> Also a question, is kickstart command for RDP requirement for you? Or
> is inst.rdp (replacement of inst.vnc) enough to work with? We are
> trying to find out if we can drop the kickstart command.
I don't particularly care about how the functionality gets activated;
> Jiri Konecny writes:
> Hi, the only change should be that you will change "vnc --connect"
> with the new API we will provide and also use RDP as your client
> instead of VNC.
Thanks. I don't particularly care about VNC itself; I just wanted to
make sure that it was known that someone does
> Aoife Moloney writes:
> === VNC switch to RDP for remote GUI installations ===
I'm curious how my usual install workflow will be affected by this
change. I use the kickstart "vnc --connect" option extensively in my
workflow; I may have a bunch of installs running in parallel, and they
jus
For many years I have maintained xu4 (https://xu4.sourceforge.net/,
https://src.fedoraproject.org/rpms/xu4/), an open source engine which
can run the freely available Ultima IV game files. When the original
code was subsumed into the ScummVM engine, I was conflicted about what
should be done with
> Adam Williamson writes:
> Honestly, we could really use more automation here, but it's a fairly
> hard thing to do *reliably* and there just isn't anybody specifically
> tasked with it so it doesn't happen.
So sure, we could use something but it doesn't have to start out as some
complex fu
> Kevin Kofler via devel writes:
> My pet peeve is provenpackagers or comaintainers who add unwanted
> automagic (autorelease, autosetup, autochangelog) to my packages.
That really shouldn't be happening for anything which wasn't officially
made mandatory or forbidden or whatnot. Sure, I we
So I've been in this situation, both on the receiving end of nasty flames
because I dared touch someone else's package and having duplicated work
because I didn't check before trying to update something.
> Michael J Gruber writes:
> So, due to me following my package (notmuch)
The idea is t
> Christopher writes:
>> $ wget mypackage.rpm
>> $rpm --checksig mypackage.rpm
> the whole point of
> using DNF to install a local file is for consistency of using the same
> command as for repo packages, not manually altering the RPM database
> outside of YUM/DNF (that results in a warning
> Robert Marcano via devel writes:
> I seriously don't know how gnome-browser-connector [1] has ownership
> of:
> /usr/lib64/mozilla/native-messaging-hosts
> and not have conflict problems with mozilla-filesystem at install
> time, maybe because they usually get installed at the same time
> Sandro writes:
> That aside, having the document linked in the packaging guidelines is
> a big step towards letting packagers know of its existence.
I just wanted to point out that the packaging guidelines have pointed
users to the document for quite some time (early 2019) in this section
> Maxwell G writes:
> IIRC, we used to have nim in Fedora and then it was retired.
Yes, it was in Fedora 33 but orphaned for some time and then retired.
The last version packaged was 1.0.4. The final spec doesn't look very
complicated but of course it's tough to say how that would apply to
> Sandro Mani writes:
> To keep these functional, I've prepared a podofo-compat package with
> the previous 0.9.x library. The review request is here [2]. Happy to
> review in exchange.
Note that it's not necessary to go through the review process for
multiple versions of packages like this,
> Gary Buhrmaster writes:
> I have found that using something like libfoo.so.X{,.*} in the %files
> directive can be a useful reminder (enforcer) to reduce such surprises
> (that particular glob presumes semantic versioning, and that minor and
> patch level updates do not require rebuilds, bu
> Nicholas Frizzell writes:
> Has anyone investigated making use of multithreading for check-files
> previously?
I'm not sure multithreading is all that meaningful for that script; it's
really quite simple, after all. It runs find to get a list of files,
sorts it, and diffs that against the
; Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam
> Miroslav Suchý writes:
> No, I'm not saying that. Somebody has enough courage to open the
> package review, discuss it, get to the point that the package review
> was approved. But did not have the courage to reach sponsors. It was
> road block for them.
That's an odd case, I suppose. I h
> Miroslav Suchý writes:
> Again. This is not what we are telling them.
Again? There's no need for that.
In any case, what I wrote was the procedure I documented it when I set
it up. If all of that documentation was lost, then I don't know what to
say but that's not what was intended.
I
> Jakub Kadlčík writes:
> Currently, we have 31 people waiting to be sponsored
> https://fedoraproject.org/PackageReviewStatus/needsponsor.html many of
> them waiting for months. To get to the point of waiting to be
> sponsored, all of these people invested their time to learn the basics
> of
> Kenneth Goldman writes:
> but … if the tutorial has a sample .spec file, I think it would
> help the new user if it was 100% complete.
I believe that the section "A Complete hello.spec File" at
https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_GNU_Hello/#_a_comple
> Maxwell G writes:
> If you don't want to clone every distgit repository and use the git
> log, [...]
Even if you did, there is full copy of the git data tarred up nightly at
https://src.fedoraproject.org/repo/git-seed-latest.tar.xz which would
probably save a big load of time.
- J<
_
> stan via devel writes:
> As they say in the BUILDING.md file,
> though, fedora lacks wxWidgets 3.1.5 or greater. That stops the
> configuration, cmake -G Ninja -S . -B build when it errors out.
That's odd; as far as I can see, F36 has 3.1.5 and F37 has 3.2.1.
- J<
___
> Ewoud Kohl van Wijngaarden writes:
> Right now you can't test them since they haven't been migrated to
> testing yet.
You can download the packages directly from koji. From the relevant
update page, you can clock the "Builds" tab which will give you a link.
You can down exactly the packag
> Felix Schwarz writes:
> imho removing the devel packages is basically the same as removing
> openssl1.1 entirely. To me the idea of "deprecation" is to warn users
> that something is going away WITHOUT removing functionality
> immediately.
I just wanted to note, since I haven't noticed it
Hi All,
I am looking for someone to take over the pam_radius packaging as I no
longer have time to do so.
Thanks in advance
JT
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
F
So I went to do a dnf system-upgrade from F35 to F36 on a test machine,
as part of my usual testing. In the middle of the process, it appears
that /var filled up and that left the system in an unfortunate state.
Surprisingly (to me) it did boot with a random mix of F35 and F36
packages and even th
> Ben Cotton writes:
> == Make UEFI a hardware requirement for new Fedora installations on
> platforms that support it (x86_64).
My problem here is that I have real, useful hardware which has always
run Fedora that I would like to continue using. But it's just old
enough (purchased in 2011)
> Brandon Nielsen writes:
> I would like to see the forge macros removed from the guidelines if
> development truly has ceased.
I would like to get into them and at least see what needs to change
but... the internal implementation is somewhat baroque and my time is
severely limited. I think
> Gary Buhrmaster writes:
> I have occasionally conjectured that there should be a "last gasp"
> version of some core package released into updates for a version going
> unsupported that drops a file into /etc/motd.d that is, essentially:
I've thought about it as well, but I still wonder goo
> Robbie Harwood writes:
> Fabio Valentini writes:
>> Since it's not practical to modify almost all Fedora packages to add
>> "ExcludeArch: %{ix86}" to them, we'd probably need a different
>> machanism for this.
> Is it really not? This seems the easiest way to go about it, honestly
> - ju
I have a similar system. lspci out looks near identical. The system was
just booted this morning.
I normally run it headless with just power and network connected, but
plugging in a USB mouse, thumb drive, and USB optical drive, they show
up fine in dmesg and lsusb output using random USB port
> Rex Dieter writes:
> I'm sure there's a way to opt-out of this behavior (right?)
There is a standard way to opt out of any of the brp scripts:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_brp_buildroot_policy_scripts
- J<
___
de
Unfortunately I again have a scheduling conflict today, and won't be
near a computer for an hour either side of the meeting. Sorry about
this; for some reason things keep lining up badly.
- J<
___
devel mailing list -- devel@lists.fedoraproject.org
To
I am not the maintainer of the package, but I am aware that there are
two sources with two versions here:
https://src.fedoraproject.org/rpms/python-pyasn1/blob/f33/f/python-pyasn1.spec
The sub-package ends up with a provides with the modules version:
# rpm -q --provides python3-pyasn1-modules
p
essor (The
predecessor to the Pentium chip)
In my personal time, I'm learning a little about fedora packaging in order
to build some Fedora packages on RHEL8/CENTOS8 for my personal use. I'm
somewhat familiar with RPM spec files and building RPM
wn package maintainer, but I
need to know a lot more before being willing to commit.
Thanks,
Jason
On Sun, Nov 15, 2020 at 5:04 PM José Abílio Matos wrote:
> On Sunday, November 15, 2020 3:10:03 PM WET Jason Edgecombe wrote:
>
> > Hi everyone,
>
> >
>
> > I want to rebuil
don't know what that is. How can I recursively find all of the builddeps
for packages?
Ideally, I would like some type of (semi-)automated way to track packages
on Fedora and automatically build them on EL8, but I'm at a loss for how to
d
I'll apologize in advance for rambling, but I've been kicking around
ideas in this space for very many years now.
> "SJS" == Stephen John Smoogen writes:
SJS> Well it is quite clear we are doing something wrong and have been
SJS> for as long as the project has been going on.
It's true that
Welcome!
JT
On Mon, Nov 18, 2019, 05:51 Ankur Sinha wrote:
> Hello!
>
> Please welcome Julen (@jlanda) to the packager group. I have just
> sponsored them
> to it now[1]. They're interested in helping with the zathura related
> packages that I took over recently, and are also interested in help
orted non-responsive:
https://bugzilla.redhat.com/show_bug.cgi?id=1731535
Additional BZ's:
https://bugzilla.redhat.com/show_bug.cgi?id=1700334
Does anyone know how to get in contact with the maintainers for these
packages?
Thanks,
--
Jason Montleon | email: jmont...@redhat.com
Softwar
> "BC" == Ben Cotton writes:
BC> Use the annocheck program from the annobin package to
BC> produce an analysis of the security hardening of a compiled package
BC> when reviewing a Bodhi update.
While I don't disagree with running annocheck at some point in the build
process, _only_ doing thi
I am interested in this package as well, I can help maintain it (fas:
jtaylor)
Thanks!
JT
On Sun, Oct 20, 2019, 10:57 Igor Gnatenko
wrote:
> Feel free to assign it to me and I'll try to make an update to it as
> soon as possible.
>
> On Sun, Oct 20, 2019, 16:47 Stephen John Smoogen wrote:
>
>
> "AI" == Artur Iwicki writes:
AI> I imagine the reason is that this allows us to add new
AI> architectures to FPC and do some trial-and-error builds of FPC
AI> without affecting dependent packages - if FPC itself used
AI> %{fpc_arches}, then adding new architectures to FPC would require
AI>
> "MM" == Matthew Miller writes:
MM> Whether or not it's documented policy (and I can't remember or find
MM> anything either), many packages have the practice of trimming very
MM> old entries.
You can't always do this. I tried to purge changelog entries from a
package older than 2010 and wa
> "C" == Christopher writes:
C> With version-controlled package sources, changelogs in SPEC seem so
C> obsolete to me. They are already problematic today when they conflict
C> due to changes in multiple branches.
It's important to note that the RPM changelog is rather a different
thing from
> "CM" == Chris Murphy writes:
CM> But anyway, I did laugh a bit out loud at 23:45 UTC because *of
CM> course* there are many other totally unambiguous times to choose
CM> from instead. Some of the best comedy is pointing out the obvious.
If we're going to bikeshed it, I'll vote for two minu
On 8/27/19 7:36 AM, Björn Persson wrote:
Jason Montleon wrote:
And even if they implemented it your way you are expecting that the
developer of the application and all the libraries it uses have
written perfect bug free code with zero vulnerabilities.
You wanted to block VNC with a packet
uld put work into alternative desktops.
>
> -Dan
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraprojec
page that there are
security implications for downloading Workstation instead of Server.
On Mon, Aug 26, 2019 at 7:10 PM Björn Persson wrote:
>
> Jason Montleon wrote:
> >Imagine starting up VNC, having no intention of opening port 59xx, and
> >intending to use SSH tunneling to
27;t even
know their system has been left intentionally less secure will simply be
left none the wiser, possibly until it's too late.
On 8/26/19 10:23 AM, Anderson, Charles R wrote:
Perhaps VNC should default to listing only on the loopback interface.
On Mon, Aug 26, 2019 at 08:55:59AM -0400,
el-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
--
Jason Montleon | email:
> "C" == Christopher writes:
C> BuildError: package thrift is
C> blocked for tag f32-updates-candidate
C> (https://koji.fedoraproject.org/koji/taskinfo?taskID=37187038)
It means that thrift has been blocked in koji. The usual reason for
this is that the package has been retired, and the bl
> "GH" == Gerald Henriksen writes:
GH> On the other hand, unbuildable packages could be viewed as a
GH> security risk.
I mentioned security explicitly in my message. Just not in the portion
you quoted.
GH> If you can't just fix the security issue and rebuild, but instead
GH> have to also f
> "DS" == David Sommerseth writes:
DS> As I can see it, there is little benefit of removing lz4-static.
Isn't that entirely the decision of those maintaining the package? It's
still completely reasonable if they want to remove it for no other
reason than it eliminates ten lines from the spe
> "FW" == Florian Weimer writes:
FW> Debian treats FTBFS bugs as release-critical. They either have to
FW> be fixed, or the package gets removed from the release. However,
FW> this is not an automated process.
Of course, Debian works on a slightly different release schedule, so
it's not ex
> "MH" == Miro Hrončok writes:
MH> If we stop here, the current "setting to ASSIGNED to stop this"
MH> remains a problem.
Let's think about why this is perceived as a problem. The maintainer
has performed an affirmative act that shows they noticed. Can't we just
accept that as some stateme
> "IG" == Igor Gnatenko writes:
IG> We can actually get rid out of this using `libcurl-minimal`, but it
IG> is not easy to teach DNF to replace libcurl-minimal with libcurl
IG> without explicit --allowerasing on the command line.
That does prompt the question as to whether dnf itself is requ
I'm on vacation and a few days behind on email, sorry.
> "ZJ" == Zbigniew Jędrzejewski-Szmek writes:
ZJ> Also, there are still some obvious packages to trim:
I wonder if the rpm dependency on curl (the executable, not the library)
is strictly necessary. I believe it's only because of the
%
> "TH" == Tom Hughes writes:
TH> Presumably in this case the performance penalty was considered small
TH> enough that it was worth building even production code with this
TH> mode enabled.
I'd like to know if any performance analysis was done about this,
because the upstream of a package I h
> "KK" == Kaleb Keithley writes:
KK> The firewalld packager doesn't seem to know how to add an
KK> ExcludeArch: to the .spec or how to remove the 'Requires: kernel
KK> ...' line.
KK> https://bugzilla.redhat.com/show_bug.cgi?id=1733602
KK> Maybe someone with some authority on the subject can
> "NG" == Neal Gompa writes:
NG> You just set localpkg_gpgcheck=1 in /etc/dnf/dnf.conf
NG> That said, you probably don't want to do that, since most downloaded
NG> packages aren't signed...
I think that the ideal behavior would be to always check, but
warn/prompt for unsigned packages or th
Code of Conduct:
MH> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List
MH> Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
MH> List Archives:
MH> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
--
Jason L Tibbit
> "TC" == Tom Callaway writes:
TC> One of my packages (alienarena) fails to build in rawhide on s390x
TC> (and only that arch), but the build log shows it never even
TC> starts.
Does it fail repeatably? This error is known but as far as I know it's
always been transient. It only seems to c
> "FW" == Florian Weimer writes:
FW> At one point, there was a verified hash chain from the https://
FW> metalink service, to the repository metadata, down to individual
FW> packages. Any tampering was detected then.
I understand that the metalink contains enough information to verify the
r
> "KF" == Kevin Fenzi writes:
KF> * If you use metalinks, rpm signatures are just gravy on top, in the
KF> end you are still just trusing SSL CA's.
Only if you trust every mirror to always serve authentic content.
- J<
___
devel mailing list -- d
> "SG" == Stephen Gallagher writes:
SG> Do any tools exist to simplify the conversion to MDB? Can this be
SG> automated?
I'd like to know this as well. It's always better to provide tools or
extremely clear and detailed instructions, because it's not safe to
assume that people know how to d
> "PM" == Panu Matilainen writes:
PM> So a big +1 for sysusers in sub-packages + file trigger to handle
PM> running systemd-sysusers. It solves more problems than the current
PM> sysusers-proposal and in a far more elegant way at that.
It's great that you agree. That leaves all of the detai
> "JN" == Jamie Nguyen writes:
JN> I couldn't find clear packaging policy on this. The guidelines [0]
JN> talk about %config(noreplace) vs %config, but /etc/named.conf is
JN> installed as a "noreplace" file.
I don't think there's a guideline about this. %config and
%config(noreplace) are si
> "RF" == Richard Fearn writes:
RF> According to
RF>
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_architecture_build_failures:
>> If a Fedora package does not successfully compile, build or work on
>> an architecture, then those architectures should be listed in the
>> spec i
> "JO" == Joe Orton writes:
JO> In the historic CVS-based build system which predated what we now
JO> use, we could do GPG key verification at the time of downloading and
JO> importing a new tarball.
You're right; tmz dug up a copy of the old Makefile.common file:
https://tmz.fedorapeople.or
> "TS" == Tom Stellard writes:
TS> Are these updated builders only used for f30?
It appears that there are 29 PPC64le builders configured currently:
https://koji.fedoraproject.org/koji/hosts?start=80&state=enabled&order=name
They don't all have the same "capacity" rating.
TS> Because I'm s
> "FW" == Florian Weimer writes:
FW> ELF multilib DSOs inside RPMs result in code deduplication,
FW> affecting container image size.
I think it's important to quantify this kind of thing. I think we can
all agree that there is very little benefit to duplicating every single
library, so extr
> "KK" == Kaleb Keithley writes:
KK> I built the latest ceph-14 (14.2.2) on rawhide successfully two days
KK> ago. Two different builds on f30 built or are building fine on
KK> x86_64, i686, and aarch64, but failed with different errors on
KK> ppc64le at different places in the build. One l
>>>>> "JLT" == Jason L Tibbitts writes:
JLT> And, let's see, I'd have to toss out five desktops (which isn't too
JLT> bad, I guess)
I was wrong. It would be 36 desktops. Being charitable requires me to
assume this was proposed without adequ
> "BC" == Ben Cotton writes:
BC> * Other developers: Other developers may have to adjust test suites
BC> which expect exact floating point results, and correct linking with
BC> libatomic. They will also have to upgrade their x86-64
BC> machines to something that can execute AVX2 instructions.
> "ZD" == Zdenek Dohnal writes:
ZD> Converted to spaces now.
Well I appreciate that, but my point is that it's really personal
preference.
ZD> It is designed for user to run rpmdev-bumpspec
ZD> .spec, so the tool will supply correct format of changelog
ZD> entry and increment the release.
Welcome back to Fedora. I've clicked the necessary sponsorship buttons.
- J<
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject
> "ZD" == Zdenek Dohnal writes:
ZD> Hi all, I would like to ask as Vim co-maintainer, do you find useful
ZD> for Vim to do:
ZD> - when you open new file with .spec suffix, Vim will get you basic
ZD> spec file structure?
Personally I have always found that behavior annoying. If I open a new
> "FW" == Florian Weimer writes:
FW> I strongly doubt this will be true indefinitely. I expect things
FW> will change pretty quickly once partners can access and file bugs in
FW> the other bug tracker.
This is interesting in light of the fact that one reason given for not
enabling Pagure is
> "VO" == Vít Ondruch writes:
VO> I just wonder what is the point of:
VO>
https://github.com/systemd/systemd/blob/b0ca726/src/core/macros.systemd.in#L122
I guess it just saves packagers from having to call systemd-sysusers
properly. You include the configuration file in the source package
> "MC" == Michael Cronenworth writes:
MC> Yes, something would have to be invented, and I guess that's why no
MC> one replied.
Well I replied, bit I'm behind on email so...
MC> However, the data exists it is just not available in a standard,
MC> parsable format.
And that was really my ques
> "MC" == Michael Cronenworth writes:
MC> Any long term plans to support C/C++ apps?
Depends on what you mean by "support", really. Really there's just a
new spec section that gets run and it just needs to echo a list of build
dependencies. That's really all this does; the existing Rust su
> "PK" == Philip Kovacs via devel writes:
PK> Years ago when I was writing my specs to add the packages I now
PK> maintain, I recall someone recommended to me the use of these macros as
PK> Fedora "tribal knowledge." I am happy to remove mine if their use is
PK> unnecessary and could lead to
>>>>> "JP" == Jens-Ulrik Petersen writes:
JP> Jason, can you explain in more details (bug report is also fine) how
JP> exactly you are installing?
I install a generic minimal system via kickstart (booted using the
Server PXE images and using the Everything r
I noticed that my F30 installs are coming out far larger than my F29
installs (by 3GB or so) and did some digging into why.
With F30 we switched away from having groups named like "korean-support"
that you could install to get input methods and fonts needed to display
a language and instead we hav
> "PM" == Panu Matilainen writes:
PM> Note that rpm doesn't support parallel zstd compression, and while
PM> it does for xz, that's not even utilized in Fedora.
Doing parallel xz compression has a surprising cost in compression ratio
which gets worse as the thread count increases (because it
> "BC" == Ben Cotton writes:
BC> * The change requires setting a new compression algorithm in rpm
BC> macros. Then a mass rebuild of all packages is required.
Technically there is no harm if a mass rebuild is not done; there will
simply be no benefit for packages which aren't rebuilt. Certa
> "PP" == Petr Pisar writes:
PP> I'm going to rebase miniz in Rawhide from 1.15_r4 to
PP> 2.1.0.
Thanks for doing this; it allows me to unbundle miniz from prusa-slicer,
at least in rawhide.
- J<
___
devel mailing list -- devel@lists.fedoraprojec
> "AT" == Andrew Toskin writes:
AT> I'm looking specifically into VeraCrypt, the open-source fork from
AT> TrueCrypt.
Has the situation which has kept VeraCrypt out of Fedora previously been
changed?
See this, for example:
https://lists.fedoraproject.org/archives/list/devel@lists.fedorapro
> "DH" == David Howells writes:
DH> I'm not entirely clear how I should go about requesting FPC
DH> approval. It says it is preferable that a ticket be filed in the
DH> packaging committee pagure - do they mean to raise an issue, do you
DH> know?
Just file a ticket:
https://pagure.io/packa
1 - 100 of 667 matches
Mail list logo
