Re: Freeze Break request: update kernel on buildhw-x86*

Thanks. This is done now. kevin signature.asc Description: PGP signature -- ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org Fedora Code of Conduct:

Freeze break request: update pungi on compose hosts

We need a newer pungi version that adds support for kiwi and has changes for osbuild arm minimal. These are both things we are trying to land for beta. There's a 4.6.2 release upstream that we need. So, I'd like to build this for f39 (which our compose hosts are) and update them. If something

Freeze Break request: update kernel on buildhw-x86*

Hey everyone. The koji builders are currently using 6.7.6-200.fc39, which is mostly fine, but on i386 builds there's some kind of memory issue and (some) builds run out of memory and fail. ;( See: https://pagure.io/fedora-infrastructure/issue/11775 I'd like to upgrade the buildhw-x86*

Re: libxslxwriter (misspelled package) in zombie state

On Fri, Mar 01, 2024 at 11:49:06AM +, Richard W.M. Jones wrote: > > We were discussing this on IRC, so just to bring the topic up on the > mailing list ... > > (1) Package libxslxwriter (note: "xslx") with only automated activity > and no builds: >

Re: Untagged resources in AWS

On Fri, Mar 01, 2024 at 04:20:30PM +0100, Miroslav Suchý wrote: > This is without AMIs and Snapshots that still produce looong list. > > Region: ap-southeast-1 > Instances: (name, id, owner) >  * proxy38 (i-0a1ee820c765d573c, N/A) > Volumes - [id name (attached to instance, owner)]: >  *

Fedora 40 beta freeze now in effect

Greetings. We are now in the infrastructure freeze leading up to the Fedora 40 Beta release. This is a pre release freeze. We do this to ensure that our infrastructure is stable and ready to release the Fedora 40 Beta when it's available. You can see a list of hosts that do not freeze by

Re: Login issues to lists.* and src.*? Any outages?

All that said, I have filed: https://pagure.io/fedora-infrastructure/issue/11799 for us to investigate why it's not properly disabling the unresponsive nodes and look into the underlying unresponsiveness issue. kevin signature.asc Description: PGP signature --

Re: Login issues to lists.* and src.*? Any outages?

On Thu, Feb 22, 2024 at 04:46:23PM -0500, Christopher wrote: > On Thu, Feb 22, 2024 at 4:01 PM Gary Buhrmaster > wrote: > > > > On Thu, Feb 22, 2024 at 8:20 PM Christopher > > wrote: > > > > > > Are there any known issues right now for logging in to > > > lists.fedoraproject.org or

koji news and 1.34.0 upgrade

Greetings. After the outage that just completed, koji has been upgraded to 1.34.0 plus a few patches from upstream. Some highlights: * The scheduler has been redone completely, hopefully this will allow for more complex scheduling adjustments. In the mean time it should be pretty similar from the

koji news and 1.34.0 upgrade

Greetings. After the outage that just completed, koji has been upgraded to 1.34.0 plus a few patches from upstream. Some highlights: * The scheduler has been redone completely, hopefully this will allow for more complex scheduling adjustments. In the mean time it should be pretty similar from the

Re: List of long term FTBFS packages to be retired in 1 week

On Wed, Feb 21, 2024 at 04:43:26PM +0100, Miro Hrončok wrote: > NOTE: This was not sent to individual maintainers, as @fedoraproject.org > aliases are currently broken > https://pagure.io/fedora-infrastructure/issue/11768 (Side note: This should now be fixed) kevin signature.asc Description:

Re: The semiannual "Transaction failed: Signature verification failed." exercise

On Sun, Feb 18, 2024 at 12:32:45PM +, Zbigniew Jędrzejewski-Szmek wrote: > > Oh, OK. So it was a misunderstanding on my side. I thought that since e.g. F41 > has a bunch of packages taken from F40 and F39 and earlier, they will be > signed > by those respective keys. But we resign them, so

Planned Outage - koji upgrade - 2024-02-21 21:00 UTC

Planned Outage - koji upgrade - 2024-02-21 21:00 UTC There will be an outage starting at 2024-02-21 21:00 UTC, which will last approximately 3 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2024-02-21 21:00UTC'

Planned Outage - koji upgrade - 2024-02-21 21:00 UTC

Planned Outage - koji upgrade - 2024-02-21 21:00 UTC There will be an outage starting at 2024-02-21 21:00 UTC, which will last approximately 3 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2024-02-21 21:00UTC'

Planned Outage - koji upgrade - 2024-02-21 21:00 UTC

Planned Outage - koji upgrade - 2024-02-21 21:00 UTC There will be an outage starting at 2024-02-21 21:00 UTC, which will last approximately 3 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2024-02-21 21:00UTC'

Re: The semiannual "Transaction failed: Signature verification failed." exercise

On Fri, Feb 16, 2024 at 09:37:25AM -0800, Kevin Fenzi wrote: ...snip... > > It should have been. I am not sure where the process failed. > > I did generate the fedora-42 key. FYI, I was lacking coffee or something. it's there in the rawhide fedora-repos: https://src.fedoraproj

Re: The semiannual "Transaction failed: Signature verification failed." exercise

On Fri, Feb 16, 2024 at 11:12:07AM +, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Feb 15, 2024 at 06:03:59PM -0800, Kevin Fenzi wrote: > > That won't do it. We need mock to update it's config at exactly the same > > moment a successfull rawhide compose completes and mirr

Re: The semiannual "Transaction failed: Signature verification failed." exercise

On Fri, Feb 16, 2024 at 09:46:05AM +0100, Vít Ondruch wrote: > > > Other solution could be if Rawhide lived in rawhide repos instead of f41. I'm not sure I follow... rawhide is in a rawhide repo? pub/fedora/linux/development/rawhide/ Or did you mean to sign rawhide with a 'rawhide' key

Re: The semiannual "Transaction failed: Signature verification failed." exercise

On Thu, Feb 15, 2024 at 07:57:37PM +, Zbigniew Jędrzejewski-Szmek wrote: > It's this time of the year again: ... > > Could we please do something so that this doesn't happen? > Dunno, generate and distribute the keys earlier so that mock > and https://fedoraproject.org/fedora.gpg get updated

Re: Where can I find "Packages Restricting Arches" script.

On Wed, Feb 14, 2024 at 02:20:39PM +0100, Sandro wrote: > Hi, > > Some script running on pkgs01.iad2.fedoraproject.org sends a report titled > "Packages Restricting Arches" to arch-exclu...@lists.fp.o every night > (between 04:00 and 05:00 UTC)[1]. I was wondering where I could find that >

Re: Schedule for Monday's FESCo Meeting (2024-02-12)

On Tue, Feb 13, 2024 at 02:57:15AM +0100, Kevin Kofler via devel wrote: > Stephen Gallagher wrote: > > Meeting summary > > Do we have the full log somewhere? html: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-02-12/fesco.2024-02-12-19.30.log.html plain text:

Re: AWS cleanup - what to delete next?

On Mon, Feb 12, 2024 at 08:40:32PM +0100, Miroslav Suchý wrote: > Dne 09. 02. 24 v 20:34 Miroslav Suchý napsal(a): > > > I think we should leave "GA" images. Even thought they are EOL for the > > > most part, I think it's still possibly nice to be able to spin one up to > > > test something or the

Re: Different owner of some Fedora-Cloud-Base images in AWS?

On Mon, Feb 12, 2024 at 11:10:57AM -0500, Dusty Mabe wrote: > > > On 2/12/24 05:14, Miroslav Suchý wrote: > > I was wondering why I cannot tag some images in AWS and I found that some > > GA images in AWS have different owner. > > > > I.e. all our images has > > > > Owner account ID 

Re: FYI: removal of bastion server in DNSBL spam.dnsbl.anonmails.de requested

On Mon, Feb 12, 2024 at 09:04:25AM -0500, Stephen Smoogen wrote: > On Mon, 12 Feb 2024 at 06:12, Marius Schwarz wrote: > > > Hi, > > > > as die Infrastructure ML did not react ( or could not react ;) ), I > > requested the removal at that antispam blacklist. > > > > > I did not see any email to

Re: FYI: removal of bastion server in DNSBL spam.dnsbl.anonmails.de requested

On Mon, Feb 12, 2024 at 09:04:25AM -0500, Stephen Smoogen wrote: > On Mon, 12 Feb 2024 at 06:12, Marius Schwarz wrote: > > > Hi, > > > > as die Infrastructure ML did not react ( or could not react ;) ), I > > requested the removal at that antispam blacklist. > > > > > I did not see any email to

Re: AWS cleanup - what to delete next?

On Thu, Feb 08, 2024 at 05:09:27PM +0100, Miroslav Suchý wrote: > Yesterday I finally deleted all Fedora-AtomicHost AMIs and associated > snapshots (it took whole night to finish). > > This time, I know we have to start with AMIs first (and only then delete > snapshots). > > Where I can

Re: just to let you know FESCo agreed to a preliminary injunction while we consider this issue

On Thu, Feb 08, 2024 at 08:43:52PM +0100, Fabio Valentini wrote: > > One thing that seems to be overlooked in many of the posts on this thread: > > Nobody can *force* the KDE Plasma maintainers to do *anything*, just > like nobody can force *any* packager to do anything. Fedora a > volunteer-run

Re: Not tagged resource in AWS

On Wed, Feb 07, 2024 at 02:49:01PM +0100, Miroslav Suchý wrote: > This is a resource from AWS that does not have propper tag: > > Region: eu-west-1 > Volumes - [id name (attached to instance, owner)]: >   * vol-0e5efafe67ed944ad N/A (apps-containerization, N/A) > > Can the owner please tag (or

Planned Outage - server updates - 2024-02-07 22:00 UTC

There will be an outage starting at 2024-02-07 22:00UTC, which will last approximately 6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2024-02-07 22:00UTC' Reason for outage: We will be applying updates and

Planned Outage - server updates - 2024-02-07 22:00 UTC

There will be an outage starting at 2024-02-07 22:00UTC, which will last approximately 6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2024-02-07 22:00UTC' Reason for outage: We will be applying updates and

Planned Outage - server updates - 2024-02-07 22:00 UTC

There will be an outage starting at 2024-02-07 22:00UTC, which will last approximately 6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2024-02-07 22:00UTC' Reason for outage: We will be applying updates and

Planned Outage - server updates - 2024-02-07 22:00 UTC

There will be an outage starting at 2024-02-07 22:00UTC, which will last approximately 6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2024-02-07 22:00UTC' Reason for outage: We will be applying updates and

Re: Re: Re: A reminder: you cannot just "revert" package version bumps

On Thu, Feb 01, 2024 at 02:51:54AM +0100, Kevin Kofler via devel wrote: > kevin wrote: > > distro-sync is nice and all, but it's not a silver bullet. > > In cases of simple packages a downgrade may not break anything, but in > > cases where other things already built upon it, where the new one > >

Re: Re: Are package-owner mail addresses working?

On Wed, Jan 03, 2024 at 09:59:23AM -0500, Stephen Gallagher wrote: > On Wed, Jan 3, 2024 at 8:15 AM Sergio Pascual wrote: > > > > El lun, 1 ene 2024 a las 13:49, Mamoru TASAKA > > () escribió: > > > > > > Sergio Pascual wrote on 2024/01/01 21:36: > > > > Hello and happy new year. > > > > > > > >

Re: Bugzilla and Groups

On Thu, Dec 21, 2023 at 01:19:46PM -0700, Tim Flink wrote: > What are the general rules around default bugzilla assignee for packages? I'm > trying to set the default assignee for rocm-cmake to rocm-packagers-sig but > keep getting an error: > > Unable to update the bugzilla assignee(s):

[fedora-arm] Re: State of the mibility SIG, dec 2023

On Thu, Dec 14, 2023 at 09:16:02AM +, Peter Robinson wrote: > One other thing I had meant to bring up to mobility meetings, which I > had been missing which I think I now realise is probably because they > moved to matrix. > > Is handheld gaming consoles a possible focus or interest for

[fedora-arm] Re: State of the mibility SIG, dec 2023

On Thu, Dec 14, 2023 at 08:47:10AM +, Peter Robinson wrote: > Hi Kevin, > > Thanks for the update. Comments inline. > > Firstly I'd like to apologise for my lack of public participation in > the SIG, the last year or two has proven quite problematic for me > personally, I've had a lot of

[fedora-arm] Re: State of the mibility SIG, dec 2023

On Thu, Dec 14, 2023 at 08:00:50AM +0100, Dan Čermák wrote: > Hi Kevin, > > I'm sorry to hear that you bumped into so many issues with upstreaming > patches and hence have to put the SIG into a dormant state. > > Nevertheless, I would like to thank you and all the contributors for > your amazing

[fedora-arm] State of the mibility SIG, dec 2023

Greetings. This will be a bit long, but I hope it will explain the current unfortunate state of the mobility sig. First a bit of history. The mobility sig was originally formed back in 2010. The goal then was “… a group of Fedora contributors that are interested in Fedora on small devices.

Re: Creation of new package repo failed, Invalid or expired token

On Tue, Dec 12, 2023 at 11:14:03AM -, Felix Wang wrote: > I opened an releng issue about this. [1] At the time of writing, I noticed > that there is probably an similar issue of failure of package creation > appeared. [2] Hope anyone can help me solve the problem, which maybe the > cause of

Re: [Test-Announce] 2023-12-11 @ 16:00 UTC - Fedora QA Meeting

Could it be something like https://discussion.fedoraproject.org/t/registration-difficulties-on-chat-fedoraproject-org/39072/52 TLDR: matrix is supposed to show you a 'agreement' thing when you first login to accept, somehow for this other user it got in a weird state where they were not able to

Re: Proven to be sickened

On Mon, Dec 11, 2023 at 08:28:31AM -0500, Stephen Gallagher wrote: > > While I generally agree that a merge request is a more polite and > elegant solution, if a package is listed as FTBFS (having had a bug > automatically opened) and some reasonable amount of time (two, three > weeks?) has

Re: Fedora Review Service and setting the AutomationTriaged keyword

Thanks for working on this Jakub. I think it's quite useful. :) 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

Holiday reminder 2023

Just a gentle reminder that the holiday season is coming up. Many contributors have more time to work on things, others are spending time away with friends and family. When you push changes during the holidays be extra aware of anything that might cause outages or breakage that might pull

Re: Should we retire the mailx package?

I'm definitely in favor. I hit this broken step a while back myself. ;( Hopefully the current maintainers are on board with this? kevin signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To

Re: Heads up - AWS Snapshots cleanup

On Sat, Dec 02, 2023 at 10:57:11PM +0100, Miroslav Suchý wrote: > Dne 02. 12. 23 v 22:45 Miroslav Suchý napsal(a): > > I wonder - do we have written retention policy for our images? Do we > > want to keep the old one? Public ones? Private ones? > > It seems that Fedora Atomic Host is EOLed since

congrats to another new sysadmin-mainer

I'm happy to announce that We have approved a new member in our sysadmin-main group: praiskup This is the core group of trusted folks that high level access to most everything in fedora infrastructure. As many of you know, he's wrangled copr for quite some time, as well as taking on other

Re: Synching user database from Fedora IPA to pagure

On Tue, Nov 28, 2023 at 10:13:35AM +, Mattia Verga via devel wrote: > I'd like to start writing a script to synch users/groups from Fedora IPA > to pagure.io and src.fp.o: both pagure.io and src.fp.o logins are based > on Fedora accounts, but the Pagure user database is only updated when a

Re: Introduction - Chris(devic3)

o. So thats: [#meeting-3:fedoraproject.org](https://matrix.to/#/%23meeting-3%3Afedoraproject.org) kevin -- > > Chris > > wt., 28 lis 2023 o 01:29 Kevin Fenzi napisał(a): > > > On Mon, Nov 27, 2023 at 07:18:55PM +0100, Krzysztof Kuberski wrote: > > > Hello, > &

Re: Introduction - Chris(devic3)

On Mon, Nov 27, 2023 at 07:18:55PM +0100, Krzysztof Kuberski wrote: > Hello, > > I wish to help in contributing at Fedora, below some informations about me > > IRC - DeviC3 > > Skills/job: > Actually, I'm working as sysadmin in the RHEL environment and a secondary > job as LSE in the same

Re: AWS Snapshots without FedoraGroup tag

On Thu, Nov 23, 2023 at 04:38:01PM +0100, Miroslav Suchý wrote: > > I had time to investigate it a bit: Thanks for digging into it. ...snip... > > Based on this founding I propose: > > 1) Delete **all** snapshots without FedoraGroup tag older than - let say - > 2021. This way we can

Re: Missing notifications

Also... if you meant the scm-commits mailing list, then yeah, that is broken currently. ;( https://github.com/fedora-infra/fmn/issues/1024 kevin signature.asc Description: PGP signature -- ___ devel mailing list -- devel@lists.fedoraproject.org To

Re: Missing notifications

On Sun, Nov 19, 2023 at 03:13:21PM -0500, Stephen Smoogen wrote: > It could be due to the retirement of the old notifications system earlier > this month. See the email "intent to retire: fedmsg-irc, old fmn, osbs" > sent to the mailing list earlier. > > FMN is the tool which sends notifications

Re: Inactive packages removed from packager group

On Mon, Nov 20, 2023 at 08:27:47AM +1100, Arthur G wrote: > I recall a number of years back a proposed gcc upgrade broke many builds. > This required most maintainers to log in and refactor their source code > against the new gcc (and new gcc options). > > I hadn't logged into Fedora for years

Re: Inactive packages removed from packager group

On Sun, Nov 19, 2023 at 06:34:39PM +, Richard W.M. Jones wrote: > On Sun, Nov 19, 2023 at 08:33:02AM +, Mattia Verga via devel wrote: > > rpms/cairo > > rpms/createrepo_c > > rpms/desktop-backgrounds > > rpms/ed > > rpms/libcap > > rpms/vim > > Just noting that these packages seem to be

Inactive packages removed from packager group

Hi all, Today, 2023-11-18, 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

Inactive packages removed from packager group

Hi all, Today, 2023-11-18, 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

Re: Rust bindings for Python (pyo3 versions <0.19, cpython) broken with Python 3.12

On Mon, Nov 13, 2023 at 07:25:10PM +0100, Fabio Valentini wrote: > > Yup, I've mentioned that in the bug I filed for python-bcrypt - > It might be as simple as bumping the dependency on pyo3 from v0.15 to v0.19. I've made an attempt here:

Planned Outage - pagure.io network switch updates - 2023-11-17 13:00 UTC

Planned Outage - pagure.io network switch updates - 2023-11-17 13:00 UTC There will be an outage starting at 2023-11-17 13:00UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d

Planned Outage - pagure.io network switch updates - 2023-11-17 13:00 UTC

Planned Outage - pagure.io network switch updates - 2023-11-17 13:00 UTC There will be an outage starting at 2023-11-17 13:00UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d

Planned Outage - pagure.io network switch updates - 2023-11-17 13:00 UTC

Planned Outage - pagure.io network switch updates - 2023-11-17 13:00 UTC There will be an outage starting at 2023-11-17 13:00UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d

Re: onboard still in the Xfce spin

On Wed, Nov 15, 2023 at 10:59:52AM +1100, Ian Laurie wrote: > > Mystery solved. > > Using the everything-net-install to install Xfce didn't drag in onboard. > > My own fedora-install.sh script that I always run after fresh installs > caused the problem when it installed slick-greeter. > > So

Re: onboard still in the Xfce spin

On Tue, Nov 14, 2023 at 01:24:59PM +1100, Ian Laurie wrote: > I did a fresh install using the everything-net-install and Xfce still > installs with onboard, which was orphaned in Fedora and doesn't actually > work anymore. > > https://bugzilla.redhat.com/show_bug.cgi?id=2227390 > > We should

Planned Outage - Server updates/Reboots - 2023-11-15 20:00 UTC

Planned Outage - Server updates/Reboots - 2023-11-15 20:00 UTC There will be an outage starting at 2023-11-15 20:00 UTC, which will last approximately 6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2023-11-15

Planned Outage - Server updates/Reboots - 2023-11-15 20:00 UTC

Planned Outage - Server updates/Reboots - 2023-11-15 20:00 UTC There will be an outage starting at 2023-11-15 20:00 UTC, which will last approximately 6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2023-11-15

Planned Outage - Server updates/Reboots - 2023-11-15 20:00 UTC

Planned Outage - Server updates/Reboots - 2023-11-15 20:00 UTC There will be an outage starting at 2023-11-15 20:00 UTC, which will last approximately 6 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2023-11-15

Re: dnf conflict in rawhide Docker container in GitHub Action

On Mon, Nov 13, 2023 at 11:02:29AM -0800, Adam Williamson wrote: > > Neither I nor nirik can reproduce this as described. Note the web UI is > basically just lies / incomplete info; I think it's telling you when > the tag was created, not when the image behind it was last updated. The web page

Re: cannot update to Fedora 39 aarch64(rpi 4) Signature errors

On Mon, Nov 13, 2023 at 11:13:07AM -0500, Jeffrey Walton wrote: > On Mon, Nov 13, 2023 at 10:52 AM Kevin Fenzi wrote: > > > > Could be this: > > > > https://discussion.fedoraproject.org/t/f38-to-f39-dnf-system-upgrade-can-fail-on-raspberry-pi/92403 > > Intere

Re: cannot update to Fedora 39 aarch64(rpi 4) Signature errors

Could be this: https://discussion.fedoraproject.org/t/f38-to-f39-dnf-system-upgrade-can-fail-on-raspberry-pi/92403 kevin signature.asc Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to

intent to retire: fedmsg-irc, old fmn, osbs

Greetings everyone. Now that fedora 39 is out the door, I'd like to schedule some retirements of a few old services: fedmsg-irc: This is a old fedmsg process that send fedmsg's to IRC. Currently we have one running in production and one in staging, both on rhel7 vm's that we would like to

intent to retire: fedmsg-irc, old fmn, osbs

Greetings everyone. Now that fedora 39 is out the door, I'd like to schedule some retirements of a few old services: fedmsg-irc: This is a old fedmsg process that send fedmsg's to IRC. Currently we have one running in production and one in staging, both on rhel7 vm's that we would like to

Re: Self Introduction: Jamie Chapman

Hey Jamie! Welcome. :) If you get a chance do drop by our matrix space and chime in with any questions or comments. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email

Re: AWS Snapshots without FedoraGroup tag

On Mon, Nov 06, 2023 at 10:22:57PM +0100, Miroslav Suchý wrote: > Dne 06. 11. 23 v 20:45 Kevin Fenzi napsal(a): > > Can we get what volume they are snapshots of? Perhaps the volume name > > would help us figure things out? > > Most of the 6GiB volumes like snap-098326d4

Re: Didn't get an email about a new merge request on a package

On Wed, Nov 08, 2023 at 01:26:53PM +0100, Fabio Valentini wrote: ...snip... > > So to me this sounds like there was just some hiccup somewhere that > resulted in the email not being sent. Yeah, seems like: Oct 28 09:04:13 pkgs01 celery[1147999]: 2023-10-28 09:04:13,585 [ERROR]

Fedora 39 Final freeze now over!

With the release of Fedora 39 yesterday, infrastructure freeze is now over. Our next freeze is for Fedora 40 beta, currently scheduled for 2024-02-20. kevin signature.asc Description: PGP signature ___ infrastructure mailing list --

Re: AWS Snapshots without FedoraGroup tag

On Thu, Nov 02, 2023 at 10:32:20AM +0100, Miroslav Suchý wrote: > We have (almost) all instances and volumes properly tagged. Now let check > Snapshots. Thanks for continuing to drive this forward. ;) > OMG - there are A LOT of them. The list has 97k lines! Because of the size I > will not

Re: DNF5: Checking signatures of packages installed out of a repository?

On Wed, Nov 01, 2023 at 11:05:33AM -0400, Christopher wrote: > On Tue, Oct 31, 2023 at 7:50 PM Kevin Fenzi wrote: > > > > FWIW, from what I can recall, yum used to check all packages, but this > > resulted in tons of people complaining because they did not want it to

Re: DNF5: Checking signatures of packages installed out of a repository?

FWIW, from what I can recall, yum used to check all packages, but this resulted in tons of people complaining because they did not want it to check their local packages. So, a localpkg_gpgcheck option was added and set to false. dnf4 still has this option. It's also worth noting that if you pass

Re: AWS discontinue IAM...

On Mon, Oct 30, 2023 at 08:46:04PM +0100, Miroslav Suchý wrote: > From > > https://us-east-1.console.aws.amazon.com/iamv2/home?region=us-east-2#/home > > Attention: Extended Deadline for Updating Your Access Permissions - December > 11, 2023 > AWS has discontinued use of old IAM permissions for

Re: Is package (gnome-shell extension) split into legacy and current required?

On Mon, Oct 16, 2023 at 12:02:05PM +0200, Alexander Ploumistos wrote: > Hello, > > I maintain the gnome-shell extension for bubblemail. I was informed by > the upstream developer that in order to support GNOME ≥ 45, he is > rewriting most of the code. What is currently the master branch will >

Re: Self Introduction: Pavol Zacik

On Thu, Oct 12, 2023 at 03:35:10PM +0200, Pavol Zacik wrote: > Hello all, > > I have recently joined Red Hat as a software engineer, where I will > hopefully get to contribute to multiple Fedora packages such as TuneD. > Previously, I've made some contributions e.g., to the Botan C++ >

Re: [Test-Announce] Fedora Linux 39 Final is NO-GO

On Wed, Oct 11, 2023 at 09:45:01AM -0700, Adam Williamson wrote: > On Wed, 2023-10-11 at 15:45 +0200, Michael J Gruber wrote: > > I was just wondering what the "anchor" is, say "right after final > > freeze" or "7 days before GA". We could put "updates-testing disabled > > in fedora-release GA

Re: Meeting Agenda Item: Introduction Blake Ridgway

On Wed, Oct 11, 2023 at 08:13:50AM -0500, Blake Ridgway wrote: > Good day Fedora Infrastructure team, > > I'm Blake Ridgway. My IRC alias is /Zormak/ and my Matrix alias is > /@blakeridgway:fedora.im. /I am reaching out to introduce myself to the > Fedora Infrastructure team and express my

Re: Should Xfce's Orage be brought back?

On Sat, Oct 07, 2023 at 12:53:05PM +1100, Ian Laurie wrote: > Fedora retired Orage (small Xfce calendar app) some while back. I can't > remember what triggered the decision (most likely a bug), but I seem to > recall at the time it was perceived to be abandoned upstream. > > If I'm not mistaken

Re: Occasional random Koji build failures only on ppc64le

Circling back here... I downgraded the hosts yesterday and they have been all checking in reliably as far as I can see. Are you still seeing any build issues? kevin signature.asc Description: PGP signature ___ devel mailing list --

Re: Intention to tighten RPM crypto-policy back

On Fri, Oct 06, 2023 at 01:09:08PM +0200, Petr Pisar wrote: > > These Fedora Project keys distribute in > are also affected: > > $ gpg --list-keys 6A2FAEA2352C64E5 > pub rsa4096 2013-12-16 [SCE] > 91E97D7C4A5E96F17F3E888F6A2FAEA2352C64E5 > uid

Re: Mock v5.0 released (and mock-core-configs v39)

On Wed, Oct 04, 2023 at 11:24:15PM +0200, Pavel Raiskup wrote: > On úterý 3. října 2023 21:48:24 CEST Kevin Fenzi wrote: > > On Tue, Oct 03, 2023 at 10:30:45AM +0200, Pavel Raiskup wrote: > > > > > > Well, in what shape is our "layered image" build syst

Re: Occasional random Koji build failures only on ppc64le

On Thu, Oct 05, 2023 at 09:23:57PM +0200, Fabio Valentini wrote: > On Thu, Oct 5, 2023 at 9:12 PM Richard W.M. Jones wrote: > > > > Getting $SUBJECT. The errors are always of the form: > > > > DEBUG util.py:446:: Cannot download, all mirrors were > > already tried without success > > > >

Re: Freeze Break request: update koji-flatpak on builders

On Thu, Oct 05, 2023 at 11:27:56AM -0400, Stephen Smoogen wrote: > On Wed, 4 Oct 2023 at 11:52, Kevin Fenzi wrote: > > > We tried to get everything working with the new flatpak building setup > > before freeze, but at the last minute we ran into some issues between > >

Freeze Break request: update koji-flatpak on builders

We tried to get everything working with the new flatpak building setup before freeze, but at the last minute we ran into some issues between bodhi and the metadata that flatpak builds store in koji. We got several things sorted out yesterday before freeze, but there's still an issue with the

Fedora 39 Final freeze now in effect!

Greetings. we are now in the infrastructure freeze leading up to the Fedora 39 Final release. This is a final release freeze. We do this to ensure that our infrastructure is stable and ready to release Fedora 39 when it's available. You can see a list of hosts that do not freeze by checking out

Re: Mock v5.0 released (and mock-core-configs v39)

On Tue, Oct 03, 2023 at 10:30:45AM +0200, Pavel Raiskup wrote: > > Well, in what shape is our "layered image" build system? Aren't we able Terrible, and going to be decomissioned after f39 release. ;) But if you mean base images... those are fine. > to create a new official image say

Re: time is running: security issue BZ#2241470

On Sat, Sep 30, 2023 at 11:13:32AM +0200, Marius Schwarz wrote: > > Hi, > > this is emerg ping for the security team, to take a look at this bz : > > https://bugzilla.redhat.com/show_bug.cgi?id=2241470 If this is an embargoed bug (I can't see it, so no idea if it is, but it seems likely),

[EPEL-devel] Re: retirement of klee from EPEL 9

On Thu, Sep 28, 2023 at 10:37:28PM -0500, Carl George wrote: > It recently came to my attention that the klee package in EPEL 9 > needed to be rebuilt against the LLVM 15 library that shipped in RHEL > 9.2. I filed a bug for this [0], and then noticed it was assigned to > "Orphan Owner". It

Re: Packaging guidelines - validation of AppStream metadata files

On Thu, Sep 28, 2023 at 01:03:08PM +0100, Richard Hughes wrote: > On Wed, 27 Sept 2023 at 22:41, Kevin Fenzi wrote: > > I'm not sure at all that it would be possible to do at compose-time... > > composes are taking around 3.5-4hours and thats after I have done > > a

Re: Packaging guidelines - validation of AppStream metadata files

On Wed, Sep 27, 2023 at 10:05:38AM -0400, Neal Gompa wrote: > On Wed, Sep 27, 2023 at 9:48 AM Richard Hughes wrote: > > > > On Wed, 27 Sept 2023 at 13:23, Mattia Verga via devel > > wrote: > > > Can't this script be moved to run in Openshift as cron-based? > > > > Yes! In fact, that's what I

Re: can't ping

On Wed, Sep 27, 2023 at 11:46:07AM -0700, Mike Wright wrote: > Hi everybody, > > I have no idea how I got in this mess, but I've lost the ability to use ping > as a regular user. sudo still works. > > Nothing in lsattr, regular perms are 755 no suid. > > ping: socktype: SOCK_RAW > ping:

Re: Intention to tighten RPM crypto-policy back

On Tue, Sep 26, 2023 at 07:22:56PM +0200, Alexander Sosedkin wrote: > > Whoa, that's too many, I suspect misreporting. Could be. > I seriously doubt they were all really using DSA-1024 and switched over. > But if that really was the case --- great job to all of them. > > > The list from

Re: Resource usage in AWS per group

On Mon, Sep 25, 2023 at 05:38:44AM +0200, Miroslav Suchý wrote: > Now when we have all instances and volumes tagged. I can say who is using > what resources. Below you will find the aggregated overview of resources we > are using in AWS. > > If you will not mind, I plan to send this overview

Re: AWS Instances without tag FedoraGroup=*

On Fri, Sep 22, 2023 at 02:32:00PM +0200, Miroslav Suchý wrote: >  = Current status > > We have almost everything tagged with FedoraGroup. There are some small > leftovers (see bottom of this email). > > If no one stop me (or tag it) I will delete them by end of next week. Awesome. Thanks

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