again able to
request stable and it will be added to the next compose.
We are looking into changes around this behavior for the next beta.
kevin
--
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an emai
r build that was there).
But as long as anything handles these corner cases, ok...
> > Kevin, to your original question: if we create individual updates for
> > each package, what, except for my work behind the scenes (to determine
> > built packages and trigger an update for them) c
On Mon, Sep 15, 2025 at 11:51:41AM -0700, Adam Williamson wrote:
> On Mon, 2025-09-15 at 10:06 -0700, Kevin Fenzi wrote:
> > On Mon, Sep 15, 2025 at 09:47:53AM -0700, Adam Williamson wrote:
> > >
> > > Oh, if you think a side tag would be better I'm happy to defe
critpath.
ok, if you think the load will be acceptable then we can give it a try
that way. I still think a sidetag would be better (for the signing if
nothing else), but either way...
kevin
--
___
devel mailing list -- devel@lists.fedorapr
ll we
> try.
It might be a wash... releng side-tag would allow signing as builds
finish, but per build bodhi updates would allow for gating to catch
anything that was really broken.
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To
automation to create all of the individual updates (short of
> submitting them as a single update from a side-tag).
yeah.
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproj
or XFCE in rawhide or is
> something manual needed?
Nothing manual should be needed.
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https
o make sure QE is ok with that.
> 6. Open bugzillas for the remaining packages (failed or skipped rebuild).
>
> The rebuild can be done in any order (i.e. all at once) and does not need to
> happen in a side tag.
> I will follow up when things start moving. Let me know if I should
rking as of:
https://pagure.io/fedora-infrastructure/issue/12669#comment-982728
I looked and there's no obvious errors. I tried to restart the pod in
case it was just stuck. If that doesn't fix it, we need to investigate
further. (please file a ticket).
kevin
signature
On Wed, Sep 10, 2025 at 02:45:41PM -0700, Kevin Fenzi wrote:
>
> It _was_ all working as of:
> https://pagure.io/fedora-infrastructure/issue/12669#comment-982728
>
> I looked and there's no obvious errors. I tried to restart the pod in
> case it was just stuck. If that doe
ink that'd make sense. Probably better to call it fedora-presets
> to maintain visual seperation from systemd subpackages.
I'm not sure this complexity is really worth it... but I'll comment on
the bug I guess.
kevin
--
___
devel mailing l
oday) to migrate
> to openssl providers, or should we expect
> the openssl 3.x compatibility package
> to live for another decade or so?
The current signing tool (sigul) needs engine support.
However, it's being re-written by Jeremy in rust and
I hope it will no longer h
plies a once or (more?) mass rebuild in stable releases
with the new version? Or is it intended that packages just build with
the new go version the next time they need to be built?
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To
sibly be confused/delayed pushing something if they aren't
there.
My 2cents
kevin
signature.asc
Description: PGP signature
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject
ng (with a acceptable
license) in copr. It has no affect on anything else...
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct
On Sun, Aug 24, 2025 at 01:27:05PM -0600, Orion Poplawski wrote:
> On 8/24/25 10:09, Kevin Fenzi wrote:
> > On Sat, Aug 23, 2025 at 04:48:11PM -0600, Orion Poplawski wrote:
> > ...snip..
> > >
> > > Although it seems like s390x builders have changed recently fro
No other hardware changes I know of...
kevin
--
___
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/co
good enough?
Well, could be a self contained change? But if it's transparent to
users, perhaps just a release note?
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
uot;ACTION" could mention here that no approval was granted yet and the
> decision was to followup on ML / Discourse.
Sure, someone should have added a info about that, sorry.
We can try and do better.
kevin
--
___
devel mailing list -- devel@lists.
her. So, in the end everyone just got a blank slate.
Improvements welcome at https://github.com/fedora-infra/fmn
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora C
es out there.
Kevin Kofler
--
___
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
do not convert any packages governed by the KDE SIG to
> RPMAutoSpec, especially if it is released by the KDE community.
Makes a lot of sense.
While we are at it, I would also ask to NOT convert any of MY packages to
RPMAutoSpec. (In my case, I am also opposed to %autosetup, which the KDE S
produce some screenshots, but
right now, my main priority was to get it out there for all the interested
users.
It is NOT currently planned to get this into Fedora proper. If there is
sufficient interest in my Copr, I might have another try at making this
happen for some future Fedora release, but ri
nge: Filter Fedora Flatpaks for Atomic Desktops
> > (@fale:fale.io, 17:06:00)
>
>
> Please, any chance to provide more details? Were the changes approved or
> not? Is there any other action?
>
> (and this applies to this report as a whole)
Well, there's no Agreed or
event such
> > updates from landing in F43?
>
> Yes, updates filed now are intended to go into F43-is-rawhide, yes,
> but not *only* into F43-is-branched.
Right, they would not be also first going to rawhide, but due to the git
repo changes they would be in git for rawhide, just not bu
included in fedora-packager
Of course all these have downsides (spf changes might mean others get
more spam pretending to be from your domain, the rewriting service could
be used to spam-wash emails, the script could be used to gather emails
to spam people with, etc).
Sorry there's no clear
On Thu, Aug 07, 2025 at 06:43:02PM +, Christian Stadelmann wrote:
> Hi Kevin,
>
> you wrote:
> > We have blocked the 'blame' and 'history' web enpoints.
>
> Would it be possible to allow them again, maybe only for logged in users? I'd
> l
On Tue, Jul 29, 2025 at 10:04:18AM -0700, Adam Williamson wrote:
> On Tue, 2025-07-29 at 09:58 -0700, Kevin Fenzi wrote:
> > On Tue, Jul 29, 2025 at 09:37:44AM +, Frantisek Krenzelok wrote:
> > > First of all apologies for this mess.
> > > I have thought this would b
The meeting was called due to lack of voting members present.
=
# #meeting:fedoraproject.org: fesco
=
Meeting started by @nirik:matrix.scrye.com at 2025-08-05 17:00:02
Meeting summary
---
* TOPIC: Init Process
Following is the list of topics that will be discussed in the
FESCo meeting Tuesday at 17: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 '2025-08-05 17:00 UTC'
Links to all issues to be
There will be an outage starting at 2025-08-05 21:00 UTC, which will last
approximately 5 hours.
To convert UTC to your local time, take a look at
https://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2025-08-05 21:00 UTC'
Reason for outage:
We will be applying updates to all our servers and
needed).
Are there any docs or description of the full flow there?
I mean, there's a bunch of corner cases... like you have 5 PR's (so I
guess you merge one and the rest make new draft builds and the next one,
etc).
But yeah, we could fi
comment to all 'stuck in gating' rawhide updates
saying 'hey, the mass rebuild is starting in a week, please fix this or
the day before the mass rebuild we will unpush this and revert git to
the previous passing builds commit'
Thats yet more work for releng/qe, but some/much
gt; fix affected (undiscovered) packages before release
I'm all for documenting this better, but where?
We could perhaps add something to the reminder about the mass rebuild
coming up (which is supposed to be a week before I think?).
kevin
--
. But now the comparison really
looks like only noise, no measurable differences.
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Co
-pointer (slow).
Kevin Kofler
--
___
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
the council has been working on a policy...
https://discussion.fedoraproject.org/t/ai-policy-in-fedora-wip/144297/20
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
F
ormance-amd-graphics.html
And the result is always the same: X11 is faster and consumes less power and
other resources.
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedo
being tracked in https://pagure.io/releng/issue/12813
I was working on it much of the day yesterday.
We finally got it to finish and all the rest of the pending updates are
going out now.
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To un
as announced beforehand (if it is known beforehand it will
> have to be done) or after all post-movement work is done.
>
> Thank you in advance!
I tried to announce things to devel-announce (which also cc to this
list).
Open to ideas on how to better announce things.
kevin
--
to do the
ONLY sensible thing here and completely ignore the expiry date (but I would
not count on that).
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.or
t of an attack).
SSH assumes that the host key NEVER changes and will always print a big
scary warning and refuse to connect if it does. So the ONLY sensible thing
to do is to NEVER change the host key.
Kevin Kofler
--
___
devel mailing li
Kevin Kofler via devel wrote:
> Why should they? Anubis is a scourge that wastes massive energy for all
> legitimate browsers, breaks search engines, and if configured in a
> particularly aggressive way as on the GNOME GitLab, even entirely locks
> out some browsers (though that is a
do not think adding more energy waste is going to solve that problem.
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://d
Neal Gompa wrote:
> But those are hand-written directives, no? That approach doesn't scale at
> all.
Handwritten unwinding information for handwritten assembly. C code has
compiler-generated unwinding information.
Kevin Kofler
--
__
compositing enabled. The author hints that X11 is even faster if
you turn off compositing, but unfortunately does not share the numbers for
that.)
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
On Thu, Jul 03, 2025 at 08:05:20AM +0100, Leigh Scott wrote:
> Why isn't fedora infra using Anubis to block LLM scrappers?
We have been considering it (along with other possible options).
However, we have been a bit busy with other things recently
On Thu, Jul 03, 2025 at 07:51:47AM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Jul 02, 2025 at 06:14:15PM -0700, Kevin Fenzi via devel-announce
> wrote:
> > If you are trying to use the new src.fedoraproject.org server, you may have
> > noticed it's ssh host keys
ocks out
some browsers (though that is an issue with the setup at GNOME
specifically).
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
later today.
With that all our major services should be back up.
Please let us know if you see any major issues.
kevin
--
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announ
so be having a retrospective and sharing what we learned after
everything is back in a good state.
Thanks again for your patience.
kevin
--
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-
r the
packager or deciding it automatically based on the target (Android = static,
GNU/Linux = dynamic)? IMHO, it is not acceptable.
I could revert the offending commit in my fork, but that would not help all
the users using the stock Fedora GTK, and it is also not what the fork is
supposed to
ience.
kevin
--
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
ipping parallel packages in the official Fedora repositories means one has
to deal with file conflicts (using explicit Conflicts tags, most likely),
with packages hardcoding dependencies on X.Org (which could be fixed by
Provides in X(11)Libre, but you do not want any Provides there), etc.
for them.
Kevin Kofler
--
___
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/
List G
g. I'm still going to stick to Wayland, but Xorg is
> finally usable on Asahi Linux and fully accelerated thanks to Xlibre. Most
> Asahi Linux users are on Fedora, so it could help a lot of people.
Kevin Kofler
--
___
devel mailing li
ste everyone's time by continuing
this discussion that is not leading anywhere.
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
) is
> even copyrightable at all. And the fix would be to get the copyright
> notice and the SPDX declaration on that new header file fixed, not to ban
> the whole project for such a tiny mistake.
Kevin Kofler
--
___
devel mailing
On Wed, Jun 18, 2025 at 08:14:44AM +0200, Petr Pisar wrote:
> V Tue, Jun 17, 2025 at 08:02:16AM -0700, Kevin Fenzi via devel-announce
> napsal(a):
> >
> > * Contributors should expect for applications and services to be down or
> > not fully working
> > on monda
for those days as we work to migrate things.
Starting Wednsday the 2nd things should be up in the new datacenter
and we will start fixing issues that are reported as we can do so.
We ask for your patience in the next few weeks as we setup
to do a smooth transfer of resources.
kevin
t; ticket for the EPEL branches, contact the maintainer to get
> co-maintainership, or what?
See:
https://docs.fedoraproject.org/en-US/epel/epel-package-request/
Basically file a bug asking for the epel10 branch and offer to maintain
it if you are w
han the corresponding half of OpenH264.)
> Most users would be better served using gstreamer1-plugins-ugly and
> ffmpeg-libs from rpmfusion.
And so you also need gstreamer1-plugin-libav (which is actually built
against FFmpeg, not the libav fork) in addition to gstreamer1-plugins-ugly.
this changeable?
>
>
> [1]
> https://fedoraproject.org/wiki/Changes/Debuginfod_IMA_Verification#Release_Notes
Yeah, those are rpms that are used in making fedora flatpaks.
It might be changeable, not fully sure.
Whats the use case? Can you pull debuginfo into a
because it
is not a drop-in replacement (does not support even basic things such as
FTP).
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code
rust) compilers produce
staticlly linked binaries and there's no runtime dep on the compiler.
Of course you are 100% correct in the case where the thing you are
adding adds a runtime dep. Thats why this path is tricky. ;(
kevin
--
___
devel mailing
re are some tricky things you can also do like tag in a build
you need, do your builds and untag it, but you should only do that
if you really know what you are doing, because the other build's update
might not go stable at the same time as yours and if there's a runtime
dependency there,
e and include that file with OPTIONAL so there is no error
when it is missing. I think it should be straightforward to adapt to other
projects if you understand CMake.
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
Glade
rpms/xonsh
rpms/xsd
kevin
--
___
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/
List
Hi all,
Today, 2025-05-06, we have removed inactive packagers
from the packager group.
This is in accordance with the FESCo policy on inactive packagers:
https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/
If the removed user is 'main admin' for a package, this package
will
filed against
> the package.
The main assignee for the firefox package has been going to /dev/null
for many many years. ;)
Just not having email notifications doesn't always mean the package
isn't being maintained. For example, there are groups that just handle
bugs via queries and d
o merge.
* If the bug isn't a packaging one, perhaps try engaging with upstream?
If the bug is known/fixed there it would get pulled in the next release
hopefully...
Its a hard balance. There's way more bugs than people to fix them, so
sometimes there's no good answer.
kevin
On Fri, Apr 25, 2025 at 03:55:40PM +0200, Fabio Valentini wrote:
> On Thu, Apr 24, 2025 at 12:52 AM Kevin Fenzi wrote:
> >
> > So, some things I wonder about this process (in no particular order):
> >
> > If this lightweight process is easier, will not people just
.
Yeah, this is old data I think using the old countme stuff.
I think there is definitely interest in fixing it up. I think that would
probibly happen before flock.
So, I wouldn't use this for much right now...
kevin
--
___
devel mailing list -- d
3 (which this change is for) _will_ have removed it
upstream.
In that sense, isn't this just a 'hey, heads up, this is going away in
f43' change?
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe sen
7;s
not working out.
kevin
signature.asc
Description: PGP signature
--
___
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/e
On Thu, Apr 17, 2025 at 12:27:26AM +0200, Fabio Valentini wrote:
> On Wed, Apr 16, 2025 at 10:04 PM Kevin Fenzi wrote:
> >
> > On Tue, Apr 15, 2025 at 06:21:20PM +0200, Fabio Valentini wrote:
> > ...snip...
> >
> > > The only remaining blocker fr
hat is possible.
I'd be happy to help.
kevin
--
___
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-co
; https://gitlab.com/fedora/docs/docs-website/docs-fp-o/-/blob/stg/site.yml#L109
I'm happy to work with any websites / packaging / docs folks to get this
done.
> Please reply with other examples so we can have a TODO list.
> (Not just branch names, but that is the least-effo
or the like, but
note that some functionality may be missing if you do. In particular in
the past (but I have not tested at all recently), screen locking may not
work (since it depended on the 'gdm' session being there).
kevin
--
___
devel mailing
Kevin Fenzi wrote:
> On Wed, Apr 09, 2025 at 03:35:06PM -0400, Eduard Lucena wrote:
>> Can we go ahead in time and let kevin to create the gdm-x11 package? We
>
> Sure, if he wants to?
I do not currently have plans to introduce that package, though I would
encourage people
On Wed, Apr 09, 2025 at 03:35:06PM -0400, Eduard Lucena wrote:
> Can we go ahead in time and let kevin to create the gdm-x11 package? We
Sure, if he wants to?
But I'll note that as far as I know, upstream plans to remove this in
the upcoming gnome cycle, so you would need to re-add it
ges would not exist in Fedora today
if it were not for me and my perseverance over this issue.
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Co
Neal Gompa wrote:
> You need to switch to another display manager, as GDM no longer
> supports X11 sessions.
Time to fork GDM.
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to de
if GDM is not the display manager being used
(which is another issue, but not a new one, and not Fedora's fault).
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fed
Jared K. Smith wrote:
> On Wed, Apr 9, 2025 at 12:59 PM Kevin Kofler via devel <
> devel@lists.fedoraproject.org> wrote:
>
>> This crusade against X11 in Fedora needs to stop NOW!
>>
>
> I'm not involved in this change -- but I take exception to your l
a Change? If yes, I'd argue that it should be reverted
> and done in F43 with a proper Change.
Note that this was a DOWNSTREAM Fedora change, upstream GDM still supports
X11 sessions!
This crusade against X11 in Fedora needs to stop NOW!
Kevin Kofler
--
___
n. It should be easily possible for anyone interested to build a
gdm-x11 package in Fedora without even patching the upstream code (at this
time – patching might become required in a later version).
Kevin Kofler
--
___
devel mailing list -- de
an see, is a specific subpackage…
> kf5-sonnet-aspel
… and the same goes for Sonnet.
For the other reverse dependencies:
> eiskaltdcpp-qt
> perl-Text-Aspell
> php-pspel
> recoll
> yagf
it might be harder to make them use something else
rsions).
if(IS_ABSOLUTE path) has been supported since forever.
Kevin Kofler
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedor
Kevin Fenzi wrote:
> Ideally things would just be more resistant to being able to make the
> mistakes in the first place, but sometimes thats not easy to do.
As far as I can see, things are quite resistant already considering that the
gating has blocked this from going into Rawhide. :-)
I
li, @michich, @salimma
> dledford has a bugzilla override on rpms/qperf
> dledford is maintainer of rpms/rdma-core
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraprojec
Planned Outage - updates / reboots - 2025-03-26 21:00UTC
There will be an outage starting at 2025-03-26 21:00UTC
which will last approximately 5 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2025-03-26 21:00UTC'
R
On Fri, Mar 21, 2025 at 02:58:46AM +, Gary Buhrmaster wrote:
> On Thu, Mar 20, 2025 at 6:15 PM Kevin Fenzi wrote:
>
> > As a side note: if this sort of thing happens and you need something
> > untagged for some reason, please file a releng ticket.
> > ( https://pagu
kage
> libfido2-1.15.0-3.fc42.x86_64
> - cannot install the best update candidate for package
> libcbor-0.11.0-3.fc42.x86_64
As a side note: if this sort of thing happens and you need something
untagged for some reason, please file a releng ticket.
( https://pagure.io/releng )
Thats likely
idate tag (ie,
f42-updates-candidate),
which any maintainer can do with a 'koji tag-build f42-updates-candidate
NVR).
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorapr
the
> > frama-c build now fails in Rawhide:
> >
> > We seem to have zero cmake builds tagged into Rawhide at the moment.
>
> Yep.
> cmake-3.31.6-1.fc43 /
> https://koji.fedoraproject.org/koji/buildinfo?buildID=26
and needs to be fixed.
Removing those -D arguments from the %cmake macro is a completely gratuitous
backwards-incompatible change that will break a whole bunch of specfiles for
no good reason.
Kevin Kofler
--
___
devel maili
gt; https://pagure.io/releng/issue/12617
> https://pagure.io/fedora-infrastructure/issue/12112
Just FYI, this should be fixed (for rawhide at least) now.
kevin
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an em
the tool.
I think having a rpm would be awesome and agree with your reasons.
That said, we shouldn't say it's a requirement for Infrastructure.
We already deploy some applications other ways and don't have a hard
requirement on an rpm being available anymore.
But w
feedback as they can.
kevin
--
___
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/
Li
1 - 100 of 7526 matches
Mail list logo
