Re: Feedback wanted: Testing side-tag for switching dnf5 in Rawhide

On Fri, Apr 26, 2024 at 11:16:28AM GMT, Adam Williamson wrote: > On Fri, 2024-04-26 at 08:56 +0200, Jan Kolarik wrote: > > Hi Kevin, > > > > Personally, I think this is a beta requirement. > > > > > > > IIUC the Fedora 41 Beta requirement is to successfully upgrade the system > > from Fedora

Re: Feedback wanted: Testing side-tag for switching dnf5 in Rawhide

On Thu, Apr 25, 2024 at 11:42:57AM GMT, Jan Kolarik wrote: > Hello Michael, > > Does this mean that distro-upgrade from F41 to F42 is supposed to work > > at F41 release time (ideally at beta time)? > > > > Yes, the system-upgrade functionality should be available before the Fedora > 41 >

Re: F41 Change Proposal: Fedora Miracle Spin (self-contained)

On Thu, Apr 25, 2024 at 05:48:46AM GMT, Zbigniew Jędrzejewski-Szmek wrote: > > There's also the effort of distribuiting and archiving a few > additional gigabytes, putting up the links on the website and browsing > through them, some additional time and and additional step that can > fail during

Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)

On Fri, Apr 19, 2024 at 09:37:38AM GMT, Igor Kerstges wrote: > Those questions regarding privacy are asked and answered to my satisfaction. > I'd like to understand more implications about this change.. There are none. This proposal was withdrawn. It may be adjusted and submitted for

Re: Three steps we could take to make supply chain attacks a bit harder

On Fri, Apr 12, 2024 at 03:45:40PM -0400, Steve Cossette wrote: > What about simply blocking access to the git repos/koji/bodhi for those > without 2fa? Well, git I suppose could be a hook that checks the status of the user, but koji and bodhi don't really have any place to hook that in directly.

Re: Three steps we could take to make supply chain attacks a bit harder

On Fri, Apr 12, 2024 at 09:47:04AM -0700, Adam Williamson wrote: > On Thu, 2024-04-11 at 19:52 -0700, Carlos Rodriguez-Fernandez wrote: > > I was hesitant to have MFA for a while. Imagine losing a phone with tons > > of tokens. What a hassle to recover from that. I found it less than > > ideal

[EPEL-devel] Re: RFC: Django latest vs LTS maintenance plan

On Thu, Apr 11, 2024 at 03:41:02PM -0500, Michel Lind wrote: > Hi all, > > With the recent EOL of the Django 3.2 LTS series[^1], and Django being a > key component of our mailing list infra for both Fedora and CentOS, I > would like to propose the following plan to maintain Django in both >

Re: Three steps we could take to make supply chain attacks a bit harder

On Thu, Apr 11, 2024 at 05:49:27PM -0700, Adam Williamson wrote: > On Fri, 2024-04-12 at 00:09 +, Gary Buhrmaster wrote: > > > > What is the best way to formally propose > > that 2FA is required for packagers after > > some date > > There is already a FESCo ticket.

Re: Looking for people to be stewards of rpminspect-data-fedora

On Tue, Apr 09, 2024 at 01:55:41PM -0400, David Cantrell wrote: > Hello all, > > I am looking for multiple people to help be upstream stewards of the > rpminspect-data-fedora project. This is a project that contains config files > and rules for running rpminspect on Fedora builds. It is a

Re: Schedule for Monday's FESCo Meeting (2024-04-08)

On Mon, Apr 08, 2024 at 06:19:31PM +, Zbigniew Jędrzejewski-Szmek wrote: > On Sat, Apr 06, 2024 at 10:45:52AM -0700, Kevin Fenzi wrote: > > = Discussed and Voted in the Ticket = > > > > Change: GNU Toolchain F41 > > https://pagure.io/fesco/issue/3

Re: EPEL9 updates obsoleted

On Sun, Apr 07, 2024 at 10:11:56PM +0200, Fabio Valentini wrote: > On Sun, Apr 7, 2024 at 10:10 PM Fabio Valentini wrote: > > > > On Sun, Apr 7, 2024 at 7:06 PM Antonio T. sagitter > > wrote: > > > > > > Hi all. > > > > > > Can this update be re-activated or i have to rebuild everything? > > >

Schedule for Monday's FESCo Meeting (2024-04-08)

Following is the list of topics that will be discussed in the FESCo meeting Monday at 19:30 UTC in #meeting:fedoraproject.org on Matrix. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2024-04-08 19:30 UTC' Links to all issues to be

Re: Introduction and Application for Sponsorship

On Fri, Apr 05, 2024 at 03:07:39PM +, seanmott...@posteo.net wrote: > Hi devel! > > I'm Sean (FAS: seaninspace). I've been working professionally in Linux > Sysadmin/Engineering positions for over a decade now, and would like to help > out more :) > > I've spent most of my Fedora time in QA

Re: Switching XZ for ZSTD?

On Thu, Apr 04, 2024 at 08:11:42PM +0200, Leon Fauster via devel wrote: > > One approach that would be at least bring some light into "weak" > (non technical layer) components (albeit not sure how feasible it is), > could be: > > - Checking the resources of a packaged project. >Resources in

Re: F41 Change Proposal: Switch to DNF5 (system-wide)

On Thu, Apr 04, 2024 at 07:00:13AM +0200, Jan Kolarik wrote: > Hi guys, > > the dnf-automatic command will be obsoleted. > > > > Oh, sorry about that. This portion of the text was inadvertently altered > during the review process. I've already corrected the text on the wiki. > > The

Re: Switching XZ for ZSTD?

On Thu, Apr 04, 2024 at 05:04:20PM +, Arnie T via devel wrote: > Hi Stephen, > > Thanks for the explanation. > > I just caught up with the article at the New York Times, > > Did One Guy Just Stop a Huge Cyberattack? >

Re: Switching XZ for ZSTD?

On Thu, Apr 04, 2024 at 01:26:14PM +, Arnie T via devel wrote: > Hi, > > I just installed Fedora on 2 of my PCs a couple of weeks ago. One version of > Fedora 39 release and one of Fedora 40 to see where things are going. > > I learned about this XZ-hack from Ars Technica & The Economist.

Re: F41 Change Proposal: Switch to DNF5 (system-wide)

On Wed, Apr 03, 2024 at 11:57:48AM -0700, Adam Williamson wrote: > On Wed, 2024-04-03 at 14:27 -0400, Przemek Klosowski via devel wrote: > > On 4/3/24 06:36, Aoife Moloney wrote: > > > the dnf-automatic command will be obsoleted. > > > > https://dnf5.readthedocs.io/en/latest/changes.html does not

Re: F42 Change Proposal: Fedora Plasma Workstation (System-Wide)

On Wed, Apr 03, 2024 at 04:24:08AM +0200, Kevin Kofler via devel wrote: > Kevin Fenzi wrote: > > Why not the opposite: > > > > Download Workstation > > > > [I'm a linux user and know what I want, just show me the full list of > > downloads, click here

Re: F42 Change Proposal: Fedora Plasma Workstation (System-Wide)

On Wed, Apr 03, 2024 at 06:17:59PM +0200, Leon Fauster via devel wrote: > Am 02.04.24 um 23:32 schrieb Adam Williamson: > > On Tue, 2024-04-02 at 17:37 -0300, Sergio Belkin wrote: > > > > > > I am a happy KDE user, since the good old days of version 1.0. I celebrate > > > this decision! My

Re: Three steps we could take to make supply chain attacks a bit harder

On Wed, Apr 03, 2024 at 07:27:12AM -0400, Stephen Gallagher wrote: > On Tue, Apr 2, 2024 at 7:41 PM Kevin Fenzi wrote: > > > > On Tue, Apr 02, 2024 at 04:38:25PM -0400, Stephen Gallagher wrote: > > > On Tue, Apr 2, 2024 at 3:55 PM Steve Cossette wrote: > > >

Re: F42 Change Proposal: Fedora Plasma Workstation (System-Wide)

On Wed, Apr 03, 2024 at 02:36:07AM +0200, Kevin Kofler via devel wrote: > Kevin Fenzi wrote: > > Ok, thats obvously somewhat tounge in cheek, but if we promote multiple > > things, we need some way to describe them to uses who might not know the > > history of things and do

Re: F42 Change Proposal: Fedora Plasma Workstation (System-Wide)

On Tue, Apr 02, 2024 at 04:06:45PM -0400, Steve Cossette wrote: > Alright, so a substantial amount of information changed since the original > submission of the change proposal. We aren't necessarily thinking of > demoting Gnome. The overall spirit of the CP is that we think KDE, and to > some

Re: Three steps we could take to make supply chain attacks a bit harder

On Tue, Apr 02, 2024 at 04:38:25PM -0400, Stephen Gallagher wrote: > On Tue, Apr 2, 2024 at 3:55 PM Steve Cossette wrote: > > > > I personally would very much agree with enforcing the use of 2fa on the > > Fedora Account System. Maybe take that opportunity to make it a bit more > > user

Re: Fedora Linux 40 Final Freeze

On Tue, Apr 02, 2024 at 02:24:51PM +0200, Frantisek Zatloukal wrote: > On Tue, Apr 2, 2024 at 12:39 PM Jakub Jelinek wrote: > > > sting->stable marked updates be still included in > > stable without having to go through the exception/blocker process? > > > > I was told there would be one more

Re: xz backdoor

On Mon, Apr 01, 2024 at 05:07:13PM +, Christopher Klooz wrote: > > On 31/03/2024 23.08, Kevin Fenzi wrote: > > On Sun, Mar 31, 2024 at 10:30:23PM +0200, Leon Fauster via devel wrote: > > > Not sure, if it was already mentioned -> containers. I had here a toolbox &g

Re: xz backdoor

On Sun, Mar 31, 2024 at 08:55:37PM +, Christopher Klooz wrote: > The repo files should be the same on Fedora containers, so if the container > is F40 and the testing repo is enabled, it might have installed the malicious > build. Right, if it was dnf updated during the time that the bad

Re: xz backdoor

On Sun, Mar 31, 2024 at 10:30:23PM +0200, Leon Fauster via devel wrote: > > Not sure, if it was already mentioned -> containers. I had here a toolbox > environment with F40. That I had not in my first actions > on the screen. The last state had 5.6.0-3 installed but not sure > if the previous

Re: xz backdoor

On Sun, Mar 31, 2024 at 03:52:12PM -0500, Alex Thomas wrote: > Just to be clear, as I was getting ready to put 40 Beta on a test > machine, this has been fixed. I do the install and run updates and the > compromised version of xz is never installed? Correct. kevin signature.asc Description:

Re: Three steps we could take to make supply chain attacks a bit harder

On Sun, Mar 31, 2024 at 09:12:30AM -0700, Adam Williamson wrote: > Thanks Arthur, yes, that was *exactly* the point. > > I would argue there's a danger of getting too tied up in very specific > technical details of this attack. Yes, it's reasonable to think of ways > to mitigate those specific

Re: Three steps we could take to make supply chain attacks a bit harder

On Sun, Mar 31, 2024 at 07:42:24AM -0400, Neal Gompa wrote: > > At this point, I'm used to MFA for stuff (and I use a password manager > that handles 2FA OTPs too), but the Fedora implementation of MFA is > uniquely bad because we have to do a lot in the terminal, and our MFA > implementation

Re: xz backdoor

On Sat, Mar 30, 2024 at 11:12:02PM +0100, Sandro wrote: > > From what I understood, F40 Beta, the official Beta release, available from > the website as of March 26, has updates-testing disabled by default. That Nope. > was confirmed by several people in #devel yesterday when the Fedora

Reminder: F40 final freeze starts next week (2024-04-02)

Just a reminder that, because Beta used it's 'target date #2' (ie, today), the gap between the Beta release and Final freeze is only 1 week this time. So, please take this time to do any last minute testing and bugfixing and make sure any packages you expect to be in the final f40 base

Reminder: F40 final freeze starts next week (2024-04-02)

Just a reminder that, because Beta used it's 'target date #2' (ie, today), the gap between the Beta release and Final freeze is only 1 week this time. So, please take this time to do any last minute testing and bugfixing and make sure any packages you expect to be in the final f40 base

Re: Fedora Linux 40 Beta Released

On Tue, Mar 26, 2024 at 02:24:10PM +, Barry wrote: > Why is the version of this announcement missing all the details > here? > https://discussion.fedoraproject.org/t/fedora-linux-40-beta-released/109684 I think it was being edited when you looked? It seems to have the details now? Or is

Re: Retiring Celestia from Fedora due to licensing issues

On Wed, Mar 20, 2024 at 04:36:02PM +, Mattia Verga via devel wrote: > After I requested [1] Celestia project upstream to better define > licensing of all the textures and 3d models included in upstream data, > it turned out that at least some content is licensed CC-BY-NC-SA-3.0 [2] > which

Re: F41 Change Proposal: Change Compose Settings (system-wide)

On Mon, Mar 25, 2024 at 10:59:15PM +0100, Kevin Kofler via devel wrote: > Zbigniew Jędrzejewski-Szmek wrote: > > > On Mon, Mar 25, 2024 at 04:50:28PM -0400, Neal Gompa wrote: > >> Keep in mind we also want to make the compose process faster too, I > >> don't know if it's worth it to spend 20x

Re: glibc32 in rawhide is now built from glibc

On Tue, Mar 19, 2024 at 04:36:03PM +0100, Florian Weimer wrote: > * Kevin Fenzi: > > > So, seems glibc32 was updated to update license headers? > > > > https://bodhi.fedoraproject.org/updates/FEDORA-2024-cd577e1535 > > > > So, it's in f40-updates-testing now.

Re: glibc32 in rawhide is now built from glibc

On Fri, Mar 15, 2024 at 05:10:52PM +0100, Florian Weimer wrote: > Joseph Myers enhanced glibc.spec so that we no longer need the separate > glibc32 source package which its tarball of pre-built glibc binaries. > > As part of the DNF5 adjustment to the removal of filelists, I believe > some

Re: glibc32 in rawhide is now built from glibc

On Fri, Mar 15, 2024 at 05:10:52PM +0100, Florian Weimer wrote: > Joseph Myers enhanced glibc.spec so that we no longer need the separate > glibc32 source package which its tarball of pre-built glibc binaries. > > As part of the DNF5 adjustment to the removal of filelists, I believe > some

Planned Outage - fedora.im / chat.fedoraproject.org matrix server - 2024-03-14 07:00 UTC

Planned Outage - fedora.im / chat.fedoraproject.org matrix server - 2024-03-14 07:00 UTC There will be an outage starting at 2024-03-14 07:00UTC, which will last approximately 1 hour. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:

Planned Outage - fedora.im / chat.fedoraproject.org matrix server - 2024-03-14 07:00 UTC

Planned Outage - fedora.im / chat.fedoraproject.org matrix server - 2024-03-14 07:00 UTC There will be an outage starting at 2024-03-14 07:00UTC, which will last approximately 1 hour. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run:

Re: F41 Change Proposal: PHP no 32 bit / PHP 64-bit only (self-contained)

On Tue, Mar 12, 2024 at 07:17:23PM +0100, Fabio Valentini wrote: > > I have thought about this when proposing the Change to make dropping > support for i686 easier. What you suggest is probably not as easy as you > think - the packages that are required for multilib purposes change over > time,

Re: So you can't just copy 'sources' from one package to another?

On Fri, Mar 08, 2024 at 04:19:11PM +, Richard W.M. Jones wrote: > For mingw-* packages we (sometimes) have a separate package from the > native package, eg. libgcrypt vs mingw-libgcrypt. Therefore two > different packages are sometimes built with the exact same sources. > > However I

Re: Possible intermittent lost mail from Pagure

On Wed, Mar 06, 2024 at 11:44:51AM +, Richard W.M. Jones wrote: > I can't quite point to proper evidence, but I have a feeling that > email notifications are being lost from Pagure. I'm guessing from below you mean the src.fedoraproject.org instance? (pagure.io is the other one, so it's best

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: 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'

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: 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: 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: 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

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: 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: 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

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: 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: 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 - 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

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: 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]

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: 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: 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: 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: 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

  1   2   3   4   5   6   7   8   9   10   >