Planned Outage - mailman - 2024-06-27 10:00 UTC

Planned Outage - mailman - 2024-06-27 10:00 UTC There will be an outage starting at 2024-06-27 10:00 UTC 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: date -d '2024-06-27 10:00UTC' Reason

Planned Outage - mailman - 2024-06-27 10:00 UTC

Planned Outage - mailman - 2024-06-27 10:00 UTC There will be an outage starting at 2024-06-27 10:00 UTC 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: date -d '2024-06-27 10:00UTC' Reason

Re: Fedora Elections - Voting is now open!

Hi everyone, could you open a ticket on badges issue tracker [0]? We will look at that. Michal [0] - https://github.com/fedora-infra/tahrir/issues On 20. 05. 24 9:59, Marcin Szydelski wrote: Also couldn't get the badge. Pozdrawiam/Best regards, Marcin Szydelski

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

On 26. 02. 24 18:08, Christopher wrote: On Mon, Feb 26, 2024 at 6:13 AM Michal Konecny wrote: [snip] It's usually good to wait for some time and try again. If the issue persists you can open ticket on https://pagure.io/fedora-infrastructure/issues Michal I did try over the course of a few

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

On 24. 02. 24 12:30, Richard W.M. Jones wrote: ... So I sometimes have issues logging in. For example it happened about 5 minutes ago, but the error isn't very interesting: Original

Dist-git decoupling investigation finished

Hi everyone, We would like to inform you thatAdvanced Reconnaissance Crew (ARC) from the CPE team finished research into decoupling dist-git from its pagure-related dependencies. The finished investigation is available here

Dist-git decoupling investigation

Hi everyone, We would like to inform you that Advanced Reconnaissance Crew (ARC) [0] from the CPE team is currently conducting research into decoupling dist-git from its pagure-related dependencies. This investigation has come about as part of discussions that arose from

Re: Add a push update mechanism for https://release-monitoring.org/

We have the packit even recommended in the-new-hotness documentation (it's the application responsible for creating tickets in bugzilla when release-monitoring.org finds new version). https://the-new-hotness.readthedocs.io/en/stable/user-guide.html#opening-pull-requests-in-dist-git Michal On

Re: fedora-scm-requests email

That's strange, I never noticed this e-mail when doing initial testing during first deployment on production. Michal On 18. 07. 23 5:35, Kevin Fenzi wrote: On Tue, Jul 18, 2023 at 02:37:54AM +, Maxwell G wrote: Hi, It seems the fedora-scm-requests processor is creating the initial

Re: Take 1 minute to help with Infra & Releng Team with a decision - closing tomorrow

Konecny wrote: Hi everyone, this survey will be closed tomorrow, so you have last day to fill it. We will share the results once the survey will be closed. Thanks everybody for helping us decide. On behalf of I Team, Michal On 07. 02. 23 16:24, Michal Konecny wrote: Hi everyone, it came

Take 1 minute to help with Infra & Releng Team with a decision - closing tomorrow

Hi everyone, this survey will be closed tomorrow, so you have last day to fill it. We will share the results once the survey will be closed. Thanks everybody for helping us decide. On behalf of I Team, Michal On 07. 02. 23 16:24, Michal Konecny wrote: Hi everyone, it came to Infra

Re: Take 1 minute to help with Infra & Releng Team with a decision

On 08. 02. 23 18:54, Chuck Anderson wrote: On Wed, Feb 08, 2023 at 06:43:02PM +0100, Eike Rathke wrote: Hi Michal, On Tuesday, 2023-02-07 16:24:16 +0100, Michal Konecny wrote: [0] - https://forms.gle/J2HWDkw1UNuj8HYD8 Don't be surprised if you don't get the number of answers you hoped

Take 1 minute to help with Infra & Releng Team with a decision

Hi everyone, it came to Infra & Releng Team (sub-team in CPE that is taking care of Fedora Infra, Fedora Release Engineering and CentOS Infra) attention that there is a confusion about the labels we are using for issues in our trackers. Namely fedora-infrastructure, releng and centos-infra.

Re: Release monitoring for stable releases only

This feature is implemented in hotness, which is commenting in Bugzilla. It's already implemented in dist-git and Pagure as well. This is now waiting for new version of Pagure to be available in Fedora infra, dist-git with the changes is already available. :-) You can look at the upcoming

Anitya [release-monitoring.org] 1.7.0

Hi everyone, the new version of Anitya [0] (1.7.0) is deployed on production. The major change in this version is the migration to Bootstrap 5 [1], this means that there is a new design of Anitya. It also helped to unify the page design in Anitya. The reason to move to Bootstrap 5 was the

Re: Automation of Fedora SCM requests

-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 repository for next few days to see if everything

Re: Automation of Fedora SCM requests

Hi Michel, you can file feature requests in https://pagure.io/fedora-infra/toddlers/issues On behalf of CPE Team, Michal On 18. 01. 23 19:36, 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

Red Hat Bugzilla mail FAS field is now handled correctly by Bugzilla sync scripts

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 of the apps. This was changed now with the latest update to toddlers [1],

Red Hat Bugzilla mail FAS field is now handled correctly by Bugzilla sync scripts

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 of the apps. This was changed now with the latest update to toddlers [1],

Re: Automation of Fedora SCM requests

I've always requested branches as someone with "commit" access and never had them rejected. On Thu, Jan 12, 2023 at 3:30 AM Dominik 'Rathann' Mierzejewski wrote: On Wednesday, 11 January 2023 at 17:13, Michal Konecny wrote: > Hi everyone, > > all the re

Re: Automation of Fedora SCM requests

/issue/50370 On 10. 01. 23 13:52, Michal Konecny wrote: Hi everyone, after deployment we had some issues with API tokens for src.fedorapoject.org and pagure.io. Those issues are now solved. Only one issue remains and that is missing list of epel9 packages on https

Re: Automation of Fedora SCM requests

On 10. 01. 23 13:52, Michal Konecny wrote: Hi everyone, after deployment we had some issues with API tokens for src.fedorapoject.org and pagure.io. Those issues are now solved. Only one issue remains and that is missing list of epel9 packages on https://infrastructure.fedoraproject.org/repo

Re: Automation of Fedora SCM requests

On 10. 01. 23 13:52, Michal Konecny wrote: Hi everyone, after deployment we had some issues with API tokens for src.fedorapoject.org and pagure.io. Those issues are now solved. Only one issue remains and that is missing list of epel9 packages on https://infrastructure.fedoraproject.org/repo

Re: Automation of Fedora SCM requests

The documentation would need to be updated in multiple places, but I didn't know about this one. Thanks for sharing. Michal On 10. 01. 23 14:08, Richard Shaw wrote: On Tue, Jan 10, 2023 at 5:26 AM Michal Konecny wrote: Hi everyone, this automation is now in place and new SCM

Re: Automation of Fedora SCM requests

the epel9 branch requests will fail right now, we will reprocess them once this is fixed. On behalf of CPE Team, Michal On 10. 01. 23 12:26, Michal Konecny wrote: Hi everyone, this automation is now in place and new SCM requests will be processed automatically. If you find any issue

Re: Automation of Fedora SCM requests

:10, Michal Konecny wrote: Hello everyone, for some time CPE (Community Platform Engineering) team is working on automating Fedora SCM requests [0]. The automation is currently live on staging. You can see the output (closed tickets) in Fedora SCM requests staging repo [1]. The automation

Re: Automation of Fedora SCM requests

the epel9 branch requests will fail right now, we will reprocess them once this is fixed. On behalf of CPE Team, Michal On 10. 01. 23 12:26, Michal Konecny wrote: Hi everyone, this automation is now in place and new SCM requests will be processed automatically. If you find any issue

Re: Automation of Fedora SCM requests

:10, Michal Konecny wrote: Hello everyone, for some time CPE (Community Platform Engineering) team is working on automating Fedora SCM requests [0]. The automation is currently live on staging. You can see the output (closed tickets) in Fedora SCM requests staging repo [1]. The automation

Re: Curious how Upstream Release Monitoring works

There is a plan to automate that when you request a new package in Fedora [0], but it's still work in progress. The notification settings are now explained in the-new-hotness documentation [1] with new coming in upcoming release of src.fedoraproject.org. Michal [0] -

CPE Weekly Update - Week 49 2022

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/cpe-weekly-update-week-49-2022/. If you want to receive weekly reports by emails in the future, please subscribe to either

Automation of Fedora SCM requests

Hello everyone, for some time CPE (Community Platform Engineering) team is working on automating Fedora SCM requests [0]. The automation is currently live on staging. You can see the output (closed tickets) in Fedora SCM requests staging repo [1]. The automation is done using a plugin in

Automation of Fedora SCM requests

Hello everyone, for some time CPE (Community Platform Engineering) team is working on automating Fedora SCM requests [0]. The automation is currently live on staging. You can see the output (closed tickets) in Fedora SCM requests staging repo [1]. The automation is done using a plugin in

CPE Weekly Update - Week 42 2022

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/ cpe-weekly-update---week-42-2022/ . If you want to receive weekly reports by emails in

CPE Weekly Update - Week 38 2022

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/cpe-weekly-update---week-38-2022/. If you want to receive weekly reports by emails in the future, please subscribe to either

CPE Weekly Update - Week 36 2022

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/ cpe-weekly-update---week-36-2022/. If you want to receive weekly reports by emails in the future, please subscribe to either

Re: CPE Weekly Update - Week 34 2022

:02:06 AM Michal Konecny : If you want to receive weekly reports by emails in the future, please subscribe to either https://communityblog.fedoraproject.org/ or https://discussion.fedoraproject.org/c/news/commblog/61. We will stop sending them in the future. Why is that? I appreciate getting

CPE Weekly Update - Week 34 2022

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/ cpe-weekly-update---week-34-2022/. If you want to receive weekly reports by emails in the future, please subscribe to either

CPE Weekly Update – Week 33 2022

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). Week: 15th August - 19th August 2022 If you wish to read

CPE Weekly Update - Week 30 2022

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). Week: 25th July - 29th July 2022 If you wish to read

Re: HTTP 500 - https://admin.fedoraproject.org/accounts/

The accounts are now on this URL https://accounts.fedoraproject.org/ Michal On 28. 07. 22 14:06, Andrew Bauer wrote: I don't know where to report this, so I'm doing it here. The backend server that is hosting admin.fedoraproject.org/accounts/ is throwing an HTTP 500 SSL handshake error.

Re: Upstream Release Monitoring - bug report

On 26. 07. 22 21:03, Maxwell G via devel wrote: On 22/07/26 09:54AM, Kevin Fenzi wrote: If you want to watch activity on a package you want The little 'watch' pulldown under The package description. You can set there if you want to watch bugs, commits, both, etc. If you only wanted to watch

Re: Fedora SCM requests on the weekend

Last time I checked we were stuck on pagure not emitting any messages on staging. I will look into this more this week. I will try to test on tickets that are on https://stg.pagure.io/releng/fedora-scm-requests and if they will be processed without issue, I plan to deploy it on production.

CPE Weekly Update – Week 27 2022

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). Week: 4th - 7th July 2022 If you wish to read this in

release-monitoring.org 1.4.0 is now live

Hi everyone, today was deployed 1.4.0 version of https://release-monitoring.org. Here is a highlight of some of the changes: *Features* * Add link to AlmaLinux package to distribution mapping * Add sourceforge (git) backend to retrieve git tags * Add Python (PEP 440) versioning scheme *Bug

CPE Weekly Update – Week 24 2022

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). Week: 13th - 17th June 2022 If you wish to read this in

CPE Weekly Update – Week 23 2022

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). Week: 6th - 10th 2022 If you wish to read this in form

the-new-hotness 1.2.0 released

Hello everyone, it's here! Hotness 1.2.0 was released! For those who don't know, the-new-hotness is the application that creates the notification for new releases on bugzilla for release-monitoring.org. The new version brings a lot of new things and I highlight some of them in this e-mail: *

CPE Weekly Update – Week 20 2022

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). Week: 16th May - 20th May 2022 If you wish to read this

CPE Weekly Update – Week 19 2022

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). Week: 09th May - 13th May 2022 If you wish to read this

CPE Weekly Update – Week 17 2022

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). Week: 25th April - 29th April 2022 If you wish to read

CPE Weekly Update – Week of April 4th – 8th

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). If you wish to read this in form of a blog post, check

CPE Weekly Update – Week of March 21st – 25th

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). If you wish to read this in form of a blog post, check

CPE Weekly Update – Week of February 28th – March 3rd

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). If you wish to read this in form of a blog post, check

Re: VERY late notification emails

On 28. 02. 22 18:24, Kevin Fenzi wrote: On Mon, Feb 28, 2022 at 07:45:27AM -0600, Richard Shaw wrote: I almost wrote this a week ago but decided not to as it's been recently discussed but this is really annoying. 6 days later is more than useless. Previously it was blamed, at least

CPE Weekly Update – Week of February 7th – 11th

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). If you wish to read this in form of a blog post, check the

Re: The New Hotness 1.0.0 deployed on production

to src.fedoraproject.org to notify only about stable versions. Michal P.S.: I removed the beta versions from Anitya project for you. On 13. 12. 21 18:11, Fabio Valentini wrote: On Mon, Dec 13, 2021 at 11:41 AM Michal Konecny wrote: Do you have an example? Because this is a bug. If the project doesn't have some

Re: The New Hotness 1.0.0 deployed on production

This would create a vast amount of bogus notifications and there are multiple reasons why: 1) Editing the project in Anitya (this could create a really strange versions, especially for custom backend) 2) Creating a new project in Anitya (the first check usually retrieves large amount of new

Re: The New Hotness 1.0.0 deployed on production

On 09. 12. 21 21:15, Miro Hrončok wrote: On 09. 12. 21 18:34, Fabio Valentini wrote: On Thu, Dec 9, 2021 at 2:57 PM Miro Hrončok wrote: On 09. 12. 21 13:54, Michal Konecny wrote: Hello everyone, The New Hotness 1.0.0 is now live in Fedora infra production environment. For those who

Re: The New Hotness 1.0.0 deployed on production

On 09. 12. 21 18:34, Fabio Valentini wrote: On Thu, Dec 9, 2021 at 2:57 PM Miro Hrončok wrote: ... The only way I can think of to "ignore" pre-releases is to add a "Version filter" on release-monitoring.org ... I've started adding a "alpha;beta;rc;pre" filter (and set the versioning to

Re: The New Hotness 1.0.0 deployed on production

If you think this will be a fine feature for The New Hotness, please feel free to file a ticket in https://github.com/fedora-infra/the-new-hotness/issues Michal On 09. 12. 21 16:49, Jerry James wrote: On Thu, Dec 9, 2021 at 8:32 AM Michal Konecny wrote: The New Hotness uses RPM version

Re: The New Hotness 1.0.0 deployed on production

+0100, Michal Konecny wrote: The New Hotness uses RPM version comparison for this and if this fails, there isn't much we can do about it. See https://github.com/fedora-infra/the-new-hotness/blob/2b3f7d7c2af847a48d190cab952125e7ccb97690/hotness/common/rpm.py#L32 if you want to look at how

Re: The New Hotness 1.0.0 deployed on production

On 09. 12. 21 15:20, Michael Catanzaro wrote: On Thu, Dec 9 2021 at 02:25:11 PM +0100, Miro Hrončok wrote: Let me use this as an opportunity to ask: How can I disable reporting of pre-releases? I have the opposite question. Previously, once a pre-release tarball was available, the new

Re: The New Hotness 1.0.0 deployed on production

On 09. 12. 21 14:25, Miro Hrončok wrote: On 09. 12. 21 13:54, Michal Konecny wrote: Hello everyone, The New Hotness 1.0.0 is now live in Fedora infra production environment. For those who don't know what this app does, it basically notifying packagers about new versions of packages

The New Hotness 1.0.0 deployed on production

Hello everyone, The New Hotness 1.0.0 is now live in Fedora infra production environment. For those who don't know what this app does, it basically notifying packagers about new versions of packages by creating bugzilla issues. And what is new: * The New Hotness was rewritten from scratch

CPE Weekly Update – Week of December 6th – 10th

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). If you wish to read this in form of a blog post, check the

CPE Weekly Update – Week of November 08th – 12nd

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). If you wish to read this in form of a blog post, check the

CPE Weekly Update – Week of October 18th – 22nd

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat (https://libera.chat/). If you wish to read in form of blog post, check the post on

Re: CPE Feedback Survey

Hi everyone, we still want your feedback about your experiences with the CPE Team. The survey will take only few minutes and there is still some time left before the survey will be closed. Here is the link to survey https://fedoraproject.limequery.com/4?lang=en

Re: the-new-hotness is broken?

The fix is deployed to production. Michal On 04. 02. 21 10:23, Michal Konecny wrote: I will work on the fix today. Not happy about this useless change that just broke plenty of scripts. Michal On 04. 02. 21 0:23, Kevin Fenzi wrote: On Wed, Feb 03, 2021 at 05:41:27PM -0500, Elliott Sales de

Re: the-new-hotness is broken?

I will work on the fix today. Not happy about this useless change that just broke plenty of scripts. Michal On 04. 02. 21 0:23, Kevin Fenzi wrote: On Wed, Feb 03, 2021 at 05:41:27PM -0500, Elliott Sales de Andrade wrote: I just received 3 notifications that the-new-hotness saw an update

Unavailability of some fedoraproject.org services

Hi everyone, we are currently experiencing network issues in IAD2 datacenter. There are plenty of services on fedoraproject.org unavailable right now. Please stay calm and don't ping us on IRC. If you want to follow the issue, we have a ticket for this [0]. On behalf of Fedora

Re: CPE Git Forge Decision

On 03/04/2020 01:25, Jeremy Cline wrote: On Thu, 2020-04-02 at 11:52 +0100, Leigh Griffin wrote: The number of active developers on Fedora initiatives has gone up drastically since I joined the team in 2019. You are possibly not seeing that as the team have moved from a model of siloed work

Re: CPE Git Forge Decision

On 02/04/2020 23:51, Björn Persson wrote: Paul Frields wrote: That statement rings hollow for me, when Github is arguably the single biggest vendor of open source in the world, no part of itself is open source, and thanks to its pervasiveness, open source has won the war of how development

Re: CPE Git Forge Decision

On 01/04/2020 10:53, Vít Ondruch wrote: Dne 01. 04. 20 v 10:37 Michal Konecny napsal(a): On 31/03/2020 20:53, Kevin Fenzi wrote: On Tue, Mar 31, 2020 at 12:40:55PM -0500, Bruno Wolff III wrote: ...snip... Because of switching costs, this is likely to prevent us from going back to Pagure

Re: CPE Git Forge Decision

On 31/03/2020 20:53, Kevin Fenzi wrote: On Tue, Mar 31, 2020 at 12:40:55PM -0500, Bruno Wolff III wrote: ...snip... Because of switching costs, this is likely to prevent us from going back to Pagure if it does develop a vibrant independent community. That would be unfortunate. So, currently

Re: Git Forge Requirements: Please see the Community Blog

On 06/02/2020 22:13, Till Maas wrote: On Tue, Jan 21, 2020 at 04:34:37PM +, Leigh Griffin wrote: On behalf of the CPE team I want to draw the communities attention to a recent blog post which you may be impacted by: https://communityblog.fedoraproject.org/git-forge-requirements/ We

Re: Anitya Upstream Release Monitoring - Dial back Auto-Bugzilla ticket generation

Hi, each project is checked for new version once per hour. There is a service running that is creating a queue from the projects that would be checked. It was just a coincidence that your project was checked at the same time you uploaded a new version. But if you are an upstream maintainer,

Re: Git Forge Requirements: Please see the Community Blog

On 31/01/2020 12:11, Vít Ondruch wrote: Dne 31. 01. 20 v 1:43 Neal Gompa napsal(a): On Thu, Jan 30, 2020 at 6:51 PM Randy Barlow wrote: On Thu, 2020-01-30 at 10:30 +0100, Vít Ondruch wrote: cough cough errata cough cough Honestly, sometimes the disconnect between what is going on in

Re: Git Forge Requirements: Please see the Community Blog

On 21/01/2020 23:13, John M. Harris Jr wrote: On Tuesday, January 21, 2020 2:31:47 PM MST Michael Catanzaro wrote: On Tue, Jan 21, 2020 at 4:04 pm, Neal Gompa wrote: And any discussion of GitHub isn't going to involve self-hosted, it's going to involve GitHub.com, which means we're talking

Re: Let's talk about Fedora in the '20s!

I think, and this is my personal opinion, that Ubuntu is so popular, because it is easy to use for everyone. You don't need to have much technical knowledge to use Ubuntu for most thinks that non technical user needs and it looks good. Every time I'm trying to use Fedora the same way, I

Non-responsive maintainer wzzrd

Hi, I'm sending this e-mail according to non-responsive maintainer policy with link to created issue in bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1765093 This maintainer has also two other issues on him: https://bugzilla.redhat.com/show_bug.cgi?id=1605696

Re: 2020 Datacenter Move: Request for comments

On 2019-10-02 16:45, Fabio Valentini wrote: On Wed, Oct 2, 2019 at 3:07 AM Brian (bex) Exelbierd wrote: On Tue, Oct 1, 2019 at 10:05 AM Pavel Valena wrote: - Original Message - From: "Jun Aruga" To: "Development discussions related to Fedora" Cc: "Fedora Infrastructure" Sent:

Re: Defining the future of the packager workflow in Fedora

On 2019-09-27 17:46, Randy Barlow wrote: On Fri, 2019-09-27 at 10:26 +0200, Michal Konecny wrote: There is still possibility to use libraries.io instead of Anitya, but there are some issues: - lack of downstream mapping (this could be easily solved by some database with only downstream

Re: Defining the future of the packager workflow in Fedora

On 2019-09-26 20:35, Jeremy Cline wrote: On Thu, Sep 26, 2019 at 09:08:16AM -0700, Adam Williamson wrote: On Thu, 2019-09-26 at 15:46 +, Jeremy Cline wrote: Ah right, that makes a lot of sense. I can imagine automatically detecting the new upstream release, building that, and presenting

[Fedocal, Nuancier] looking for new maintainers

Hi everybody, we are currently looking for community members, which will be willing to take ownership of Fedocal and Nuancier. To see our reasons for this look at Fedora community blog article [0]. These two applications are part of the Friday with Infra initiative [1], so you can see what

Re: Drop of PlayOnLinux package (Rawhide)

I can recommend Lutris, it's really good and I think somebody is working on flatpak version for it. Regards, Michal Konecny On 9/10/19 4:11 PM, Frantisek Zatloukal wrote: Also, I have feeling that Lutris is far superior alternative, at least for games :) On Tue, Sep 10, 2019 at 4:01 PM

A Friday with Infra

Good Morning Everyone, As you may remember from [1] the CPE team has started categorizing its applications into the following categories: 1. We maintain it, we run it 2. We don’t maintain it, we run it 3. We don’t maintain it, we don’t run it 4. We turn it off In this process we picked the

A Friday with Infra

Good Morning Everyone, As you may remember from [1] the CPE team has started categorizing its applications into the following categories: 1. We maintain it, we run it 2. We don’t maintain it, we run it 3. We don’t maintain it, we don’t run it 4. We turn it off In this process we picked the

Re: Discussion around app retirements and categorizations by the CPE team

On 7/22/19 9:04 PM, Jeremy Cline wrote: Sure, I don't think GitLab is perfect and it has its pain-points. Working with upstream to make it better for all the communities using it seems like a much better way to spend our collective time, though. I totally agree, working on something that will

Re: Discussion around app retirements and categorizations by the CPE team

On 7/17/19 10:00 PM, Emmanuel Seyman wrote: My initial reaction is that the lists of applications in categories 1 and 2 are very short. My second reaction is that this page doesn't sell me that I should use Python in any business-critical software... These categories are not complete at all.

Re: Fedora 32 Self-Contained Change proposal: Track Changes in Taiga

I support this with every vote I have. mkonecny On 5/20/19 10:33 PM, Ben Cotton wrote: https://fedoraproject.org/wiki/Changes/fedora-change-wrangler = Track Changes in Taiga = The Motivation for this proposal is to propose using the Taiga instance at teams.fedoraproject.org for Change

Re: fedora-img-dl: a tool for downloading Fedora iso's and images

Will this be used by Fedora Media Writer [0]? [0] - https://docs.fedoraproject.org/en-US/quick-docs/creating-and-using-a-live-installation-image/ On 4/15/19 11:22 AM, Jens-Ulrik Petersen wrote: Hi, I made a small cli tool for downloading Fedora iso's etc. It can download rawhide, branched,

Fedora flatpak remote is not GPG verified

Hi, I recently started using Fedora flatpak remote in Fedora 30 Silverblue, but now I'm facing issue with GPG verification. I didn't had any issue when installing the application from the remote few days ago, but when I'm trying to do `flatpak update` I'm getting "Error: Can't pull from

Re: Fedora, Packaging, Java, and Shrooms

Hi, firstly i recommend to use Fedora toolbox [0] for this kind of things on Silverblue (it's part of Silverblue already). Secondly, isn't this what modules are meant for? I'm not sure if there is one for JDK on Fedora. Regards, Michal Konecny [0] - https://github.com/debarshiray/toolbox

Re: Anitya not working again?

Hi, it took some time, but it's done now. Regards, mkonecny On 08/04/19 01:18, Robert-André Mauchin wrote: On Wednesday, 3 April 2019 16:53:06 CEST Michal Konecny wrote: Done, you should see new bugs in a few minutes. mkonecny May I ask you to do it again for the following list of Python

Re: Fedora 30 Beta Silverblue Feedback

On 05/04/19 00:54, Ty Young wrote: However, there are serious issues with Fedora 30 Beta Silverblue(and maybe standard workstation?) with software repositories. On first boot, software center will display software and updates(and even be downloadable and installable) however and error

Re: Anitya not working again?

Done, you should see new bugs in a few minutes. mkonecny On 03/04/19 12:56, Michal Konecny wrote: It should be easy to do it, with the script I have. I just need to do some adjustments. mkonecny On 02/04/19 20:36, Igor Gnatenko wrote: Michal, can you do it for all packages with ecosystem

Re: Anitya not working again?

It should be easy to do it, with the script I have. I just need to do some adjustments. mkonecny On 02/04/19 20:36, Igor Gnatenko wrote: Michal, can you do it for all packages with ecosystem crates.io <http://crates.io>? On Tue, Apr 2, 2019 at 8:04 PM Michal Konecny <mai

Re: Anitya not working again?

I refreshed every project on the list (deleted latest version that will be retrieved again in next check, which is done every hour). You should already see new bugs in Bugzilla for the projects on this list. mkonecny On 29/03/19 10:45, Michal Konecny wrote: On 29/03/19 10:31, Robert-André

Re: Anitya not working again?

On 29/03/19 10:31, Robert-André Mauchin wrote: On Friday, 29 March 2019 09:30:31 CET Michal Konecny wrote: Could you send me the list of projects you added? I will manually refresh them. I was right, there is missing message call in API code for adding new package mapping. I created issue

  1   2   >