Re: Enabling plymouth on livemedia-creator iso creation

On Tue, Feb 14, 2023 at 02:19:15PM -0800, Brian C. Lane wrote: > Way back in the day... :) livemedia-creator inherited an '--omit > plymouth' from the boot.iso creation process. The boot.iso was changed a > few years later, but lmc kept it. Fred noticed this and submitted >

Re: Planned Outage - s390x builders - 2023-02-10 08:00 UTC -> 22:00 UTC

On Mon, Feb 13, 2023 at 03:01:34PM +0100, Luna Jernberg wrote: > ssmoogen > Current s390x status: Networking and storage on systems is not acting > appropriately. Site admins are trying to figure out what is going on. Everything is back up now. Sorry for the extended outage. We will will

Re: Planned Outage - s390x builders - 2023-02-10 08:00 UTC -> 22:00 UTC

On Sun, Feb 12, 2023 at 09:30:53PM +, Sérgio Basto wrote: > On Sat, 2023-02-11 at 10:54 +0100, Dan Horák wrote: > > On Sat, 11 Feb 2023 09:37:08 + > > "Richard W.M. Jones" wrote: > > > > > On Thu, Feb 09, 2023 at 11:35:14AM -0500, Stephen Smoogen wrote: > > > > Affected Services: > > > >

Re: Unable to create f38 branch

On Sat, Feb 11, 2023 at 12:19:30PM -0800, Luya Tshimbalanga wrote: > > On 2023-02-11 12:15, Kevin Fenzi wrote: > > On Sat, Feb 11, 2023 at 11:47:26AM -0800, Luya Tshimbalanga wrote: > > > Hello team, > > > > > > I am unable to create a f38 branch for f38-ba

Re: Unable to create f38 branch

On Sat, Feb 11, 2023 at 11:47:26AM -0800, Luya Tshimbalanga wrote: > Hello team, > > I am unable to create a f38 branch for f38-backgrounds at this time of > writing. Does it mean the branching is in process? No, branching was all completed a while back. Can you expand on why/what happens/what

Re: s390x emulation build woes

On Sat, Feb 11, 2023 at 06:42:51AM -0600, Richard Shaw wrote: > On Sat, Feb 11, 2023 at 12:13 AM John Reiser wrote: > > > On 2/10/23 19:57, Richard Shaw wrote: > > > So I know the s390x builders are down but I have an active BZ for tests > > failing with s390x so I figured what the heck, maybe

Re: Request exemption for f38-backgrounds

On Wed, Feb 08, 2023 at 07:42:35PM -0800, Luya Tshimbalanga wrote: > Hello team, Hey there. > I filed an exemption[1] for f38-backgrounds packaging review[2] as > suggestion from desktop team on discussion last year. The spec file remains > virtually unchanged other than an updated default

Re: Fedora Linux 38 branched

On Fri, Feb 10, 2023 at 03:21:06PM +, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Feb 09, 2023 at 06:44:03PM +0100, Tomas Hrcka wrote: > > Hi All, > > > > Fedora Linux 38 has now been branched, please be sure to do a git pull > > --rebase to pick up the new branch > > I know this has been

Re: Risc-V SIG?

On Thu, Feb 09, 2023 at 11:03:27AM +, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Feb 09, 2023 at 10:55:50AM +, Richard W.M. Jones wrote: > > On Thu, Feb 09, 2023 at 10:38:38AM +, Zbigniew Jędrzejewski-Szmek wrote: > > I just got a VF2 as well (as in, yesterday). I'm still waiting on

Re: bodhi tests missing

On Fri, Feb 03, 2023 at 05:27:06PM -0700, Orion Poplawski wrote: > > Thanks, but no go: > > bodhi updates trigger-tests FEDORA-2023-96ebcd6f4d > Login successful! > Traceback (most recent call last): This may well be because those updates are in a updates push right now and the updates are

Re: shorter shutdown timers are now enabled in rawhide

On Fri, Feb 03, 2023 at 06:32:20PM +0100, Fabio Valentini wrote: > > It's a 1:1 copy of the update "notes" from bodhi (except re-flowed to > fit into however many columns plain-text emails support). > So it's "markdown", not "awful", but sometimes it's hard to see the > difference ;) > Not sure

[EPEL-devel] Re: [SPF:fail] A coordinated plan for ansible-collection updates in EPEL?

On Tue, Jan 31, 2023 at 07:21:03PM -0700, Orion Poplawski wrote: > On 1/31/23 11:03, Maxwell G wrote: > > On Tue Jan 31, 2023 at 15:01 +0200, Sagi Shnaidman wrote: > > Hi all, > > > > > Hi, Orion > > > Thanks for raising this question. > > > > Indeed! > > > > > I wonder if it's possible to

Re: How to migrate database format during package update?

On Wed, Feb 01, 2023 at 01:56:20PM +0100, Milan Crha wrote: > Hi, > this is a query for an opinion and a best-practice experience for a > case when a package needs to change its internal database format > between versions, in an environment, which does not allow real > migration, aka the app

Re: Bootstrapping package with circular dependencies in koji

On Tue, Jan 31, 2023 at 07:06:25PM -0700, Orion Poplawski wrote: > On 1/31/23 11:06, Kevin Fenzi wrote: > > On Tue, Jan 31, 2023 at 02:23:48PM +0100, Vít Ondruch wrote: > > > > > > > > > It seems that Koji supports this, but it need some configuration change.

Re: What should we do about "shopping list" groups in comps?

On Tue, Jan 31, 2023 at 02:39:27PM -0800, Adam Williamson wrote: > Hey folks! > ...snip... > > So, I'm wondering what folks think we should do with these. We could, > of course, just get rid of them. But perhaps they are still of value to > someone? Is anyone still "package shopping" via

[EPEL-devel] Re: [SPF:fail] A coordinated plan for ansible-collection updates in EPEL?

On Tue, Jan 31, 2023 at 06:03:48PM +, Maxwell G wrote: > On Tue Jan 31, 2023 at 15:01 +0200, Sagi Shnaidman wrote: > Hi all, Note that some folks cc'ed are not subscribed to epel-devel, so it probibly rejected their posts. :( > > > Hi, Orion > > Thanks for raising this question. > >

[EPEL-devel] Re: Replace versioned MODULE_COMPAT_ requires by generators

On Tue, Jan 31, 2023 at 10:19:09AM +0100, Jitka Plesnikova wrote: > Hi, > > I added the package perl-generators-epel to EPEL 7/8/9. The package is > adding the behavior provided in perl-generators-1.16. > > I created pull requests for epel-rpm-macros to add perl-generators-epel > to EPEL

Re: Bootstrapping package with circular dependencies in koji

On Tue, Jan 31, 2023 at 02:23:48PM +0100, Vít Ondruch wrote: > > > It seems that Koji supports this, but it need some configuration change. I > have opened followup ticket here: > > https://pagure.io/releng/issue/11254 Yeah, my first thought about this was that it might be too broad, but it

Re: Fedora 38 mass rebuild is finished

On Tue, Jan 24, 2023 at 09:42:10AM +, Zbigniew Jędrzejewski-Szmek wrote: > On Mon, Jan 23, 2023 at 06:52:30PM -0800, Kevin Fenzi wrote: > > On Mon, Jan 23, 2023 at 10:26:18PM +, Sérgio Basto wrote: > > > > > > I found more 5 with > > > https://koj

Re: Proposal: dnf should offer to update all of the dependencies of any package installed or updated

On Sat, Jan 28, 2023 at 09:03:35PM +, Zbigniew Jędrzejewski-Szmek wrote: > > This is indeed a shortcoming in the rpm symbol dependency generation scheme. Is it though? I'm probibly reading this too quickly and missing something, but isn't the underlying problem here that nghttp2 changed abi

Nonresponsive maintainers ( was Re: Red Hat Bugzilla mail FAS field is now handled correctly by Bugzilla sync scripts )

On Tue, Jan 17, 2023 at 02:49:10PM +0100, Michal Konecny wrote: > Hi everybody, > > TL;DR; Check if you have correct e-mail in Red Hat Bugzilla Mail field in > Fedora Accounts [0]. Empty mail is also OK. > > the Red Hat Bugzilla Email field in Fedora Accounts [0] was till now ignored > by most

Re: List of long term FTBFS packages to be retired in February​

On Thu, Jan 26, 2023 at 11:07:34PM +0100, Miro Hrončok wrote: > > Unfortunately, as seen by the lenght of the packages listed in my emails, > thsi is not always the case. Yeah. ;( > Some packagers do set the bugzillas to ASSIGNED to get rid of the reminders > and then they forget to actually

Re: List of long term FTBFS packages to be retired in February​

On Thu, Jan 26, 2023 at 10:21:27AM +0100, Miro Hrončok wrote: > On 26. 01. 23 4:51, Yaakov Selkowitz wrote: > > On Tue, 2023-01-24 at 15:55 +0100, Miro Hrončok wrote: > > > Based on the current fail to build from source policy, the following > > > packages > > > should be retired from Fedora 38

Re: Bootstrapping package with circular dependencies in koji

On Wed, Jan 25, 2023 at 03:45:35PM +0100, Jaroslav Skarvada wrote: > On Wed, Jan 25, 2023 at 12:13 PM Miro Hrončok wrote: > > > > On 25. 01. 23 11:50, Vít Ondruch wrote: > > > Reading the thread, I was afraid this will be the end result. > > > Nevertheless, > > > given this would be used just

Re: [Fedora Update] [CRITPATH] [comment] alt-ergo-2.3.3-5.fc38, apron-0.9.13-16.fc38, and 182 more

On Wed, Jan 25, 2023 at 01:12:47PM +, Richard W.M. Jones wrote: ...snip... > Alternately, why does an older build block a push to stable? Won't > the old build simply be ignored if there's a higher NVR version > around? Nope, koji and pungi have no idea about 'older' or 'newer', they only

Re: Bootstrapping package with circular dependencies in koji

On Tue, Jan 24, 2023 at 03:36:41PM -0500, Neal Gompa wrote: > On Tue, Jan 24, 2023 at 3:00 PM Kevin Fenzi wrote: > > > > On Tue, Jan 24, 2023 at 07:54:29PM +0100, Jaroslav Skarvada wrote: > > > > > > I initially thought about: > > > release bump > >

Re: Bootstrapping package with circular dependencies in koji

On Tue, Jan 24, 2023 at 07:54:29PM +0100, Jaroslav Skarvada wrote: > > I initially thought about: > release bump > $ koji edit-tag SIDETAG -x %_with_bootstrap=1 > build > handle circular dep > $ koji edit-tag SIDETAG -r %_with_bootstrap > build > > But I haven't tried it yet because I didn't

Re: Fedora 38 mass rebuild is finished

On Mon, Jan 23, 2023 at 10:26:18PM +, Sérgio Basto wrote: > > I found more 5 with > https://koji.fedoraproject.org/koji/tasks?owner=releng=active=tree=all=-id > > 96481236 build (f38-rebuild, > /rpms/yaksa.git:528d57e3c954abfedba6f530f5ac09abaa9170fa) > > 96474133 build

Re: Fedora 38 mass rebuild is finished

On Mon, Jan 23, 2023 at 08:11:03PM -0500, Rafael Aquini wrote: > FYI: > > memkind failure (aarch64) seems to be koji/mock related: > > This package was updated and sucessfully built in rawhide and f37 a week > ago (01/13) > > ---8<--- > > EXCEPTION: [Error('Command failed: \n #

Re: Fedora 38 mass rebuild is finished

On Mon, Jan 23, 2023 at 01:36:10PM -0600, Jonathan Wright via devel wrote: > I'm seeing the same errors on rawhide buildroot right now. The problem was libunistring-1.1-3.fc38 (again). We untagged it in december, but looks like no one followed up to get dependent packages rebuilt:

Re: Fedora 38 mass rebuild is finished

On Mon, Jan 23, 2023 at 10:30:05AM -0700, Jerry James wrote: > > Can somebody cancel the bigloo build? It's been running for several > days and is obviously off in the weeds. I'll investigate. Done. kevin signature.asc Description: PGP signature

Re: Rawhide updates stuck for the past ~4 hours?

On Sat, Jan 21, 2023 at 03:25:48PM +, Sérgio Basto wrote: > On Fri, 2023-01-20 at 15:54 -0600, Michel Alexandre Salim wrote: > > On Fri, 2023-01-20 at 22:44 +0100, Miro Hrončok wrote: > > > My Rawhide Bodhi updates are stuck in pending, so I've checked > > > > > >

Re: When to close CVE's

On Fri, Jan 20, 2023 at 04:47:05PM +, Gary Buhrmaster wrote: > On Fri, Jan 20, 2023 at 3:48 PM Richard Shaw wrote: > > > I think in practical terms that makes sense but our tools don't really help. > > I agree, and that seems to be an artifact of > the single Fedora component in RHBZ, which

Re: Improving Fedora boot time when libvirt is installed

On Thu, Jan 19, 2023 at 11:32:24AM -0800, Gordon Messmer wrote: > On 2023-01-19 09:48, Daniel P. Berrangé wrote: > > The idea is that an application will put a dep on the > > specific libvirt-daemon-driver-XXX that its functionality > > requires. If Boxes requires storage APIs, then add a > >

Re: Automation of Fedora SCM requests

On Wed, Jan 18, 2023 at 12:36:35PM -0600, Michel Alexandre Salim wrote: > Hi Michal, > > On Wed, 2023-01-11 at 17:13 +0100, Michal Konecny wrote: > >  Hi everyone, > >   > >  all the remaining issues were solved and the bot is now processing > > tickets as it should. I will watch the SCM request

bodhi upgraded to 7.0.1

Hey folks, just a heads up that bodhi has been updated to 7.0.1 now. https://bodhi.fedoraproject.org See: https://github.com/fedora-infra/bodhi/releases for a full list of bugs fixed/enhancements. Note that this adds the concept of 'frozen' releases, which will: * show a warning / note for

bodhi upgraded to 7.0.1

Hey folks, just a heads up that bodhi has been updated to 7.0.1 now. https://bodhi.fedoraproject.org See: https://github.com/fedora-infra/bodhi/releases for a full list of bugs fixed/enhancements. Note that this adds the concept of 'frozen' releases, which will: * show a warning / note for

Re: HyperKitty: Thread tree broken?

On Thu, Jan 12, 2023 at 07:14:33PM +0100, Jun Aruga (he / him) wrote: > > > > 1. > > > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Z2RR2OE5TAQH5CVJ5VB5T3R7OM5ULYPQ/#QZUTH6DSULKYBMGPPYNZMPX7YSYKOBTT > > > > 2. > > > >

Re: HyperKitty: Thread tree broken?

On Thu, Jan 12, 2023 at 11:41:20AM -0500, Stephen Smoogen wrote: > On Thu, 12 Jan 2023 at 11:34, Jun Aruga (he / him) > wrote: > > > I see one issue on HyperKitty on the Fedora project. > > > > Below is thread 1 and 2 for the actual thread: "RISC-V -- are we ready > > for more, and what do we

Re: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)

On Wed, Jan 11, 2023 at 04:35:33PM +, Zbigniew Jędrzejewski-Szmek wrote: > > We have thousands of systemd services in Fedora. To "just add timeouts > to things that take too long" would mean updating them individually. > (Or maybe only some, but we don't really know which ones.) Sure,

Re: Schedule for Tuesday's FESCo Meeting (2023-01-03)

On Tue, Jan 10, 2023 at 09:15:41PM -0500, Siddhesh Poyarekar wrote: ...snip... > > Finally, another voting member commented, this time on the re-vote > ticket[1], again indicating that the reason for the revote is the > misdirection in the _FORTIFY_SOURCE proposal discussion. Just to set the

Re: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)

On Tue, Jan 10, 2023 at 06:00:59PM -0600, Michael Catanzaro wrote: > On Tue, Jan 10 2023 at 03:19:10 PM -0800, Kevin Fenzi > wrote: > > Is there something wrong with that approach that I am not understanding? > > No, I don't think you're missing anything. That should work fin

Re: F38 proposal: Shorter Shutdown Timer (System-Wide Change proposal)

On Mon, Jan 09, 2023 at 08:45:43PM +, Zbigniew Jędrzejewski-Szmek wrote: > > The current default is mostly arbitrary. It was just selected as a nice round > value, in the spirit of "let's pick something large enough to be larger than > any > realistic process will ever need". > > I think

Re: TeXLive 2022 landing in rawhide today

On Sat, Jan 07, 2023 at 09:11:32AM -0700, Orion Poplawski wrote: > > Seems to be breaking LaTeXML's tests: > https://apps.fedoraproject.org/koschei/package/LaTeXML?collection=f38 > > Unfortunately koschei's query to see what else might be affected hits a > gateway timeout: > >

Re: F38 proposal: Rpmautospec by Default (System-Wide Change proposal)

On Sat, Dec 31, 2022 at 03:37:34PM -0500, Stephen Smoogen wrote: > On Sat, 31 Dec 2022 at 13:40, Kevin Kofler via devel < > > https://docs.pagure.org/fedora-infra.rpmautospec/autochangelog.html#changelog-entries-generated-from-commit-messages > > > > All in all a very complicated and error-prone

Re: Scripts to rebuild dependencies in copr

On Wed, Dec 21, 2022 at 09:15:10PM -0700, Orion Poplawski wrote: > I've been using an old review_pr.py script produced by the Fedora > Stewardship SIG to rebuild the depedencies of a package in COPR to test > changes/updates to packages. It's been incredibly useful. However, it > seems that the

Re: Orphaned packages looking for new maintainers

On Mon, Dec 19, 2022 at 05:47:52PM +, Barry Scott wrote: > > > > On 19 Dec 2022, at 17:40, Ben Cotton wrote: > > > > On Mon, Dec 19, 2022 at 12:36 PM Barry wrote: > >> > >> Why is pysvn on the list? I the pysvn maintainer and i am active. > >> I am also the upstream maintainer. > > > >

Re: Some reasons I really dislike buildroot overrides and would like us to get rid of them soon

On Sat, Dec 03, 2022 at 12:04:18PM +0100, Vitaly Zaitsev via devel wrote: > On 02/12/2022 22:30, Adam Williamson wrote: > > 1. Packages that have been pushed stable since the last time a compose > > succeeded (for Rawhide that's a Rawhide compose, for Branched it's a > > Branched compose, for

Re: Need help with disappeared update from repository

On Thu, Dec 01, 2022 at 04:51:18PM +, Sérgio Basto wrote: > On Thu, 2022-12-01 at 13:21 +0800, yanq...@fedoraproject.org wrote: > > Hi all, > > > > It seems update fcitx5-qt-5.0.16-2.fc37 from [1] somehow did not make > > it to stable repository while other package in same update did. This >

Planned Outage - Updates / Reboots - 2022-11-30 21:00 UTC

There will be an outage starting at 2022-11-30 21:00 UTC 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 '2022-11-30 21:00UTC' Reason for outage: We will be applying updates and

Planned Outage - Updates / Reboots - 2022-11-30 21:00 UTC

There will be an outage starting at 2022-11-30 21:00 UTC 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 '2022-11-30 21:00UTC' Reason for outage: We will be applying updates and

Re: Direct to stable updates

On Sat, Nov 26, 2022 at 05:27:30PM -, Mattia Verga via devel wrote: > @kevin I've announced on Bodhi matrix channel that I was planning to draft > the new release, but since I received no response I've pushed out Bodhi 7.0.0. > > I have followed the SOP at [1] and bodhi-* RPMs are now

Re: Should the policy documents better reflect real package maintenance practice?

On Fri, Nov 25, 2022 at 12:20:10AM +, Gary Buhrmaster wrote: > On Thu, Nov 24, 2022 at 1:40 PM Miroslav Suchý wrote: > > > I have to make confession. I am breaking this guidelines too. With > > releasing of new version of Mock and fedora-license-data. The problem for > > me is that the

Re: Should the policy documents better reflect real package maintenance practice?

On Thu, Nov 24, 2022 at 01:42:20PM -0800, Adam Williamson wrote: > > Thinking it over some more - I think Gordon's right that I hadn't > considered all the language - I think my personal opinion would be that > the policy should be adjusted to be less opinionated on this idea of > "introducing

Re: spin-kickstarts package

On Wed, Nov 23, 2022 at 09:33:48PM -0500, Neal Gompa wrote: > > Is there a reason we couldn't just automatically update the package > once we're in freeze so that it has what we're shipping? By the time > we're down to the wire for final freeze, we're not changing the > kickstarts that often.

Re: Orphaned a lot of (mostly) Go packages owned by @fpokorny

On Wed, Nov 23, 2022 at 05:44:01PM +, Daniel P. Berrangé wrote: > > The mitigation/successor strategy is to have comaintainers for every > package. > > Unfortunately our tools enforce the notion of a "main admin" and > if that person leaves that role has to be given to another > comaintainer

spin-kickstarts package

Greetings everyone. So, we used to have a release requirement that we package up and release along side the release a spin-kickstarts rpm package with the current kickstarts used for that release. This resulted in a bunch of last minute scrambling and blockers, and even then, we often pushed

Re: Direct to stable updates

On Fri, Nov 18, 2022 at 08:10:56AM +, Mattia Verga via devel wrote: > Il 17/11/22 18:10, Adam Williamson ha scritto: > > On Wed, 2022-11-16 at 17:37 +, Mattia Verga via devel wrote: > >> Kevin, the PR for Bodhi is nearly finished, it will add support for > >> using the 'frozen' release

Re: koji down?

On Wed, Nov 16, 2022 at 11:37:43AM -0600, Richard Shaw wrote: > On Wed, Nov 16, 2022 at 11:32 AM Kevin Fenzi wrote: > > > Everything should be back up now... > > > > I'm watching it for a bit before I declare things are back fully to > > normal though. ;) >

Re: Direct to stable updates

On Wed, Nov 16, 2022 at 02:09:47PM +0100, Kevin Kofler via devel wrote: > > Kevin Fenzi is currently a member of FESCo (see > https://docs.fedoraproject.org/en-US/fesco/) and has been in that role for > years. So pushing the blame off to "someone else" is not going to

Re: Direct to stable updates

On Wed, Nov 16, 2022 at 05:37:07PM +, Mattia Verga via devel wrote: > > Kevin, the PR for Bodhi is nearly finished, it will add support for > using the 'frozen' release state to avoid pausing the push cron job and > avoid direct pending to stable push of updates when the release is frozen.

Re: koji down?

Everything should be back up now... I'm watching it for a bit before I declare things are back fully to normal though. ;) Do note that mailing list threads aren't a great place to report outages. Please report them to the infrastructure ticket tracker: https://pagure.io/fedora-infrastructure/

Re: Direct to stable updates

On Mon, Nov 14, 2022 at 11:54:32PM +0100, Kevin Kofler via devel wrote: ...snip... I think we are going to just have to agree to disagree here. I think we have had this discussion a number of times now and aren't going to convince the other. kevin signature.asc Description: PGP signature

Re: Pull-request related question.

On Sat, Nov 12, 2022 at 08:29:17PM -, Sergey Mende wrote: > Hi, > during development of my own project I hit the bug in `gdb` that is already > fixed upstream but not backported to rawhide yet. > I did a backport and ready to submit a PR. What is the right way to proceed: > > a) just file a

Re: Direct to stable updates

For a few years I was keeping track of updates that caused big problems: https://fedoraproject.org/wiki/Updates_Lessons The orig "very bad" update was a dbus update that broke everything. In any case I have seen our current updates system working and blocking tons of harmfull updates over the

Re: Direct to stable updates

On Thu, Nov 10, 2022 at 05:16:44PM +, Mattia Verga via devel wrote: > Il 10/11/22 01:58, Kevin Kofler via devel ha scritto: > > Kevin Kofler via devel wrote: > > > >> Mattia Verga via devel wrote: > >>> with the current workflow, Bodhi doesn't know when a release is freezed. > >>> There is

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

On Wed, Nov 09, 2022 at 04:26:23AM +, Naheem Zaffar wrote: > On Tue, 8 Nov 2022, 19:22 Vitaly Zaitsev via devel, < > devel@lists.fedoraproject.org> wrote: > > > On 08/11/2022 19:53, Naheem Zaffar wrote: > > > Has there been any consideration to turn on frame pointers for atleast > > > dev

Re: Help understanding Fedora CI failure wrt RPM Sequoia

On Thu, Nov 10, 2022 at 11:39:27AM +0200, Panu Matilainen wrote: > > So, overnight somebody updated the koji package in > https://kojipkgs.fedoraproject.org/repos/rawhide/ to the current unsigned > rawhide build, which makes the issue go away. Nothing should have updated the koji package. The

Re: F38 proposal: MobilityPhoshImage (Self-Contained Change proposal)

On Thu, Nov 10, 2022 at 01:35:36AM -, Scott Anecito via devel wrote: > What is the driver for choosing Phosh over GNOME Shell? There's no choosing something over something else. This isn't a Fedora Mobility Edition, but rather a first look at a Phosh based setup. Phosh has been around a

Re: F38 proposal: MobilityPhoshImage (Self-Contained Change proposal)

On Tue, Nov 08, 2022 at 03:09:46PM -0500, Ben Cotton wrote: > On Tue, Nov 8, 2022 at 1:34 PM Kevin Fenzi wrote: > > > > Yeah, was going to try and work it out with them (which I have not yet > > done). Where's the best place to engage with them these days? > > I'd sta

Re: F38 proposal: MobilityPhoshImage (Self-Contained Change proposal)

On Tue, Nov 08, 2022 at 10:21:43AM -0500, Ben Cotton wrote: > On Tue, Nov 8, 2022 at 10:10 AM Ben Cotton wrote: > > > > Initial images are produced for x86_64 and aarch64 mobile devices > > using the Phosh desktop. > > Is the plan to add these images to an existing website or a new one? The new

Re: Fedora SCM requests on the weekend

On Mon, Nov 07, 2022 at 10:21:43AM +0100, Mikel Olasagasti wrote: > Hi Kevin, > > Hau idatzi du Kevin Fenzi (ke...@scrye.com) erabiltzaileak (2022 uzt. > 9, lr. (20:11)): > > > > On Fri, Jul 08, 2022 at 01:02:15PM -, Mukundan Ragavan wrote: > > > > On S

Re: Karma for OpenSSL needed

On Thu, Nov 03, 2022 at 12:51:28PM +0100, Vít Ondruch wrote: > > Now who will be motivated enough to at least open the Koji ticket as > suggested in the other place of this thread? :D > > Actually, for my purposes, it would be much better if there was something > like `koji download-url --signed

Re: Karma for OpenSSL needed

On Wed, Nov 02, 2022 at 08:15:00PM +0200, Otto Liljalaakso wrote: > Vít Ondruch kirjoitti 2.11.2022 klo 16.18: > > > > Dne 01. 11. 22 v 18:59 Fabio Valentini napsal(a): > > > On Tue, Nov 1, 2022 at 6:53 PM Demi Marie Obenour > > > wrote: > > > > > > > > Please push them out to testing

Re: Fwd: Your message to devel@lists.fedoraproject.org awaits moderator approval

On Wed, Nov 02, 2022 at 08:02:07AM -0500, Richard Shaw wrote: > U... Isn't it considered a good practice to CC maintainers of affected > packages? Should I have done it as BCC instead? You could do BCC instead, but then if there's some feedback that someone wants to send to everyone, you

Re: systemd 252 feature: SUPPORT_END in /etc/os-release

On Tue, Nov 01, 2022 at 07:02:33PM -0400, Matthew Miller wrote: > See: > https://lists.freedesktop.org/archives/systemd-devel/2022-October/048519.html > >Systemd will set the taint flag 'support-ended' if it detects that >the OS image is past its end-of-support date. This date is

Re: Karma for OpenSSL needed

On Tue, Nov 01, 2022 at 02:55:34PM -0700, Josh Stone wrote: > On 11/1/22 11:16 AM, Neal Gompa wrote: > > That said, the packages *are* signed in Koji, because as soon as it's > > submitted to Bodhi, the packages are signed in-place in Koji. > > Is that really in-place? Bodhi says these are

Re: F40 proposal: Porting Fedora to Modern C (System-Wide Change proposal)

On Wed, Oct 26, 2022 at 10:23:40AM +0200, Florian Weimer wrote: > * Zbigniew Jędrzejewski-Szmek: > > > On Tue, Oct 25, 2022 at 10:05:52AM -0400, Ben Cotton wrote: ...snip... > >> == How To Test == > > > > As discussed by others, this needs to explain how to opt-in for early > > testing, and

Re: [side tags] Undesired automatic side-tag removal happened - how to deal with it in the future?

On Mon, Oct 17, 2022 at 12:55:44PM +0200, Zdenek Dohnal wrote: > Koji devs forwarded me to releng pagure, so there is a new issue for this > https://pagure.io/releng/issue/11093 . So, it turns out that koji upstream added a 'inactivity' check. ie, no builds tagged in or out in a timeperiod. We

Re: [side tags] Undesired automatic side-tag removal happened - how to deal with it in the future?

On Tue, Oct 11, 2022 at 08:08:32AM -, Michael J Gruber wrote: > > Oh, also I forgot to mention... > > > > If your sidetag is deleted, you can just request a new one, tag the old > > builds back into it and be back in business. I realize that that could > > be anoying if you told people a

Re: stuck s390x builds in koji

On Tue, Oct 11, 2022 at 11:35:45AM +0200, Dominik 'Rathann' Mierzejewski wrote: > On Tuesday, 11 October 2022 at 11:27, Dan Horák wrote: > > On Tue, 11 Oct 2022 11:18:12 +0200 > > Luna Jernberg wrote: > > > On 10/11/22, Dominik 'Rathann' Mierzejewski > > > wrote: > > > > Hi! > > > > It seems

Re: [side tags] Undesired automatic side-tag removal happened - how to deal with it in the future?

Oh, also I forgot to mention... If your sidetag is deleted, you can just request a new one, tag the old builds back into it and be back in business. I realize that that could be anoying if you told people a specific one and then had to make a new one, but it's not like those builds are lost.

Re: [side tags] Undesired automatic side-tag removal happened - how to deal with it in the future?

So, just to add some data... sidetags are cleaned up via a cron job that calls: /usr/sbin/koji-sidetag-cleanup --empty-delay=14 --old-delay=30 So, it should have only deleted it if it was empty after 14 days, but it looks like it deleted it with things tagged into it. ;( Would you be willing

Re: SRPM macros, EPEL, and side tags

On Wed, Oct 05, 2022 at 08:40:12PM -, Artur Frenszek-Iwicki wrote: > Hi all, > > some time ago I've built the Free Pascal Compiler [0] for EPEL9, > and recently I got the idea it might be good to do the same with > the Lazarus IDE [1]. Testing things locally with mock, > I realized that

Re: Replacing GNOME Disks with Blivet GUI in comps' admin-tools?

On Wed, Oct 05, 2022 at 02:22:52PM -0400, Ben Cotton wrote: > In going through the bugs against comps, I came across > https://bugzilla.redhat.com/show_bug.cgi?id=1971338 > > The "admin-tools" group in comps includes GNOME Disks, which is a > surprise for KDE Plasma users. We can swap it out for

aarch64 builders upgrade

Greetings. I thought I would let everyone know that I have moved all the buildvm-a64 instances from some older hardware (lenovo emags) to newer hardware (altra Mt. Snow). This should result in a noticable speed increase along with allowing us to increase density of vm's per host. If you notice

aarch64 builders upgrade

Greetings. I thought I would let everyone know that I have moved all the buildvm-a64 instances from some older hardware (lenovo emags) to newer hardware (altra Mt. Snow). This should result in a noticable speed increase along with allowing us to increase density of vm's per host. If you notice

Re: How do I "unstick" koji?

On Wed, Sep 28, 2022 at 10:10:34AM -0400, Steven A. Falco wrote: > On 9/28/22 09:59 AM, Stephen Smoogen wrote: > > > > > > On Wed, 28 Sept 2022 at 09:53, Steven A. Falco > > wrote: > > > > Yesterday, I had a build that failed.  The task ID is 92381483. > > >

Re: F39 proposal: Replace DNF with DNF5 (System-Wide Change proposal)

Sorry for the delay in my reply here. ;( Some questions: > * Release engineering: [https://pagure.io/releng/issues #Releng issue number] no releng ticket? :( releng depends on dnf4 for a LOT of scripts. We will need a lot of help moving those to dnf5 I am sure. A porting guide for the

Planned Outage - networking work - 2022-09-26 21:00 UTC and 2022-09-27 21:00 UTC

There will be an outage starting at 2022-09-26/2022-09-27 21:00 UTC, which will last approximately 4 hours on 2022-09-26 and 5 hours on 2022-09-27. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2022-09-26 21:00UTC' date

Planned Outage - networking work - 2022-09-26 21:00 UTC and 2022-09-27 21:00 UTC

There will be an outage starting at 2022-09-26/2022-09-27 21:00 UTC, which will last approximately 4 hours on 2022-09-26 and 5 hours on 2022-09-27. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2022-09-26 21:00UTC' date

Re: Summary/Minutes from today's FESCo Meeting (2022-09-20)

On Wed, Sep 21, 2022 at 02:47:21AM +0200, Kevin Kofler via devel wrote: > Miro Hrončok wrote: > >* https://fedoraproject.org/wiki/Changes/JdkInTreeLibsAndStdclibStatic > > was submitted as an Fedora 37 update after it was deferred to Fedora > > 38. We need to decide what to do.

Re: Proposal: disable comps component in Bugzilla

On Tue, Sep 20, 2022 at 10:01:36AM -0400, Ben Cotton wrote: > comps, the system of XML files used to put packages into functional > groups is hosted on a Pagure repo[1] but also has a Bugzilla > component. In the interests of simplicity, I propose to disable the > comps component and use the

[olsaj...@gmail.com: Re: unannounced soname bump in libbpf]

14:36:13 +0200 > From: Jiri Olsa > To: devel@lists.fedoraproject.org, Kevin Fenzi > Cc: jo...@fedoraproject.org > Subject: Re: unannounced soname bump in libbpf > > On Sat, Sep 03, 2022 at 05:01:47PM -0700, Kevin Fenzi wrote: > > Greetings. > > > > Seems

Re: Inactive packagers to be removed after the F37 release

On Mon, Sep 19, 2022 at 05:58:36PM +0200, Vít Ondruch wrote: > > Dne 16. 09. 22 v 19:03 Kevin Fenzi napsal(a): > > On Fri, Sep 16, 2022 at 10:03:35AM +0200, Vít Ondruch wrote: > > > Isn't peer review much better and easier solution over all? We could also > > >

Re: Fedora rawhide compose report: 20220917.n.0 changes

On Sat, Sep 17, 2022 at 11:15:40AM +, Fedora Rawhide Report wrote: > OLD: Fedora-Rawhide-20220916.n.0 > NEW: Fedora-Rawhide-20220917.n.0 On Sat, Sep 17, 2022 at 12:51:42PM +, Fedora Rawhide Report wrote: > OLD: Fedora-37-20220916.n.0 > NEW: Fedora-37-20220917.n.0 I'd like to note that

Re: Inactive packagers to be removed after the F37 release

On Fri, Sep 16, 2022 at 10:03:35AM +0200, Vít Ondruch wrote: > Isn't peer review much better and easier solution over all? We could also > require signed commits I guess. I think it would slow things down quite a lot to require peer review of every commit. I'd personally like to avoid anything

Re: Inactive packagers to be removed after the F37 release

On Fri, Sep 16, 2022 at 10:29:17AM +0300, Alexander Bokovoy wrote: > > One thing I want to get properly implemented in SSSD in upcoming FIDO2 > support is to allow admins to filter out certain types of public SSH > keys associated with the user account. E.g. get a way for administrator > to say

Re: Inactive packagers to be removed after the F37 release

On Thu, Sep 15, 2022 at 04:34:08PM -0400, Demi Marie Obenour wrote: > On 9/15/22 13:55, Kevin Fenzi wrote: > > On Thu, Sep 15, 2022 at 09:26:36AM +0300, Alexander Bokovoy wrote: > >> > >> Proven packagers seem to be a fair category to address. Also packagers > >&

Re: Inactive packagers to be removed after the F37 release

On Thu, Sep 15, 2022 at 11:54:13AM -0700, Adam Williamson wrote: > On Thu, 2022-09-15 at 10:55 -0700, Kevin Fenzi wrote: > > On Thu, Sep 15, 2022 at 09:26:36AM +0300, Alexander Bokovoy wrote: > > > > > > Proven packagers seem to be a fair category to address. Also

<    1   2   3   4   5   6   7   8   9   10   >