Unresponsive packagers: suanand and vponcova

[Pierre-Yves Chibon]

Good Morning Everyone,

We have been emailing daily the following users to notify that the email they
have set in FAS does not correspond to a valid bugzilla account.
This is a requirement for Fedora packagers.

Does someone know how to contact them?

suanand - emailed since April 5th

suanand is maintainer of rpms/gettext
suanand is main admin of rpms/php-gettext-gettext
  rpms/php-gettext-gettext co-maintainers: @petersen
suanand has a bugzilla override on rpms/php-gettext-gettext
suanand is main admin of rpms/php-gettext-languages
  rpms/php-gettext-languages co-maintainers: @petersen
suanand has a bugzilla override on rpms/php-gettext-languages
suanand is maintainer of rpms/python-polib
suanand is maintainer of rpms/python-tinydb
suanand is maintainer of rpms/translate-toolkit
suanand is maintainer of rpms/transtats-cli
suanand is maintainer of rpms/zanata-python-client

vponcova - emailed since February 26th

vponcova is maintainer of rpms/anaconda
vponcova is maintainer of rpms/pykickstart
vponcova is maintainer of rpms/python-blivet
vponcova is maintainer of rpms/python-dasbus


Thanks for your help,

Pierre
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: convert everything to rpmautospec?

[Pierre-Yves Chibon]

On Thu, Apr 11, 2024 at 09:18:09AM +0200, Ondrej Mosnáček wrote:
> On Wed, 10 Apr 2024 at 16:30, Pierre-Yves Chibon  wrote:
> [...]
> > Let's look at it in another way: would you say that the people who leaved 
> > in the
> > 14th century were liars for saying that the earth is flat?
> > No, they just didn't know.
> 
> Off-topic and not really affecting the validity of your point, but the
> idea that people in the 14th century / Middle Ages generally believed
> that the earth was flat is a myth. I recently read about it in the
> book "Fake History: 101 Things that Never Happened" by Jo Teeuwisse
> (great book, BTW!), but also Wikipedia happens to have a decent
> article about it: https://en.wikipedia.org/wiki/Myth_of_the_flat_Earth

I stand corrected, maybe "we believed earth was the center of the universe"
would have worked better?
Or something related to medicine?

Anyway, as you said, the point was: context changes and that doesn't make
what someone said a lie.


Thanks,
Pierre
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: convert everything to rpmautospec?

[Pierre-Yves Chibon]

On Mon, Apr 08, 2024 at 02:55:36PM +0200, Emmanuel Seyman wrote:
> * Zbigniew Jędrzejewski-Szmek [08/04/2024 09:02] :
> >
> > Well, you and Kevin see "salami tactics" (whatever that may be),
> 
> FTR, I have no idea what "salami tactics" is.
> 
> > while I see normal engineering practice: some new idea is hatched,
> > it's implemented and used narrowly, them it's applied by default
> > and more widely, and possibly at the end previous methods are
> > deprecated.
> 
> This sounds acceptable but is not at all how these changes are proposed.
> 
> An proposal is made, stating explicity that it will be opt-in or target
> a subset of the target audience and never even suggesting that the scope
> might one day be expanded.
> 
> It is accepted based on that premise and, after a while, changes are
> made to make the change default or opt-out, leaving the people who would
> not have accepted it had they known they would be forced to use it with
> no recourse.
> 
> This is unfriendly (thus violating one of Fedora's core principles) at
> best and deceitful at worst.
> 
> > The alternative would be to have "grand plans" where we decide that
> > some technology will be used by default and mandatory before we deploy
> > it widely and get feedback.
> 
> Another alternative would be not lie to the target audience by
> initially claiming that the change is opt-in. Yet another alternative
> would be to not go back on this claim.

There is one flaw in the reasoning here, as one of the original person behind
rpmautospec (with Nils who arguably has done more for it than me), you can see
that neither of us are involved in this proposal nor this discussion.

So it's a bit unfair to qualify that this was/is a lie and that the goal from
the get go when the change is being asked/proposed by someone else.

So no, it was not a lie, the goal was to make it opt-in. It is still the agreed
behavior and if someone proposes to change it, it's still not a lie. It would be
a lie if at that time, I would have thought: "this is going to be awesome and
we'll end up forcing it but for now I won't present it as such".

Let's look at it in another way: would you say that the people who leaved in the
14th century were liars for saying that the earth is flat?
No, they just didn't know.
Things/context changes and with this our knowledge or opinions. That doesn't
mean where we started from was a lie, it was just a different time/context.


So please, express your feeling in another way and don't use that word.

Thanks,
Pierre
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [Pierre-Yves Chibon] Unresponsive packagers: nknazeko

[Pierre-Yves Chibon]

On Tue, Feb 13, 2024 at 11:20:59AM +0100, Pierre-Yves Chibon wrote:
> 
> On Sun, Feb 11, 2024 at 10:44:18PM +0100, Vit Mojzis wrote:
> > Nikola left Red Hat and hence changed the email address in FAS. I'm
> > guessing that only her Red Hat email was tied to a BZ account.
> > I'll try and let her know. Do I understand correctly that she just needs
> > to create a new BZ account using the email address in FAS?
> 
> That's correct, she either need to create a bugzilla account associated with 
> the
> email she uses in FAS, or fill in the "bugzilla email" field of her FAS 
> account
> with the email of her bugzilla account.

Hey Vit,

Just out of curiosity, have you heard back from her?
From our side the issue still seems to be present.

Thanks,
Pierre
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: [Pierre-Yves Chibon] Unresponsive packagers: nknazeko

[Pierre-Yves Chibon]

On Sun, Feb 11, 2024 at 10:44:18PM +0100, Vit Mojzis wrote:
>  Hello Pierre,

Hi Vit,

Sorry for the late reply

> Nikola left Red Hat and hence changed the email address in FAS. I'm
> guessing that only her Red Hat email was tied to a BZ account.
> I'll try and let her know. Do I understand correctly that she just needs
> to create a new BZ account using the email address in FAS?

That's correct, she either need to create a bugzilla account associated with the
email she uses in FAS, or fill in the "bugzilla email" field of her FAS account
with the email of her bugzilla account.

Thanks for your help!

Pierre


> On 2/9/24 15:06, Petr Lautrbach wrote:
> Good Morning Everyone,
> 
> Since November 1st, we have been emailing daily the following user to notify
> that the email they have set in FAS does not correspond to a valid bugzilla
> account.
> This is a requirement for Fedora packagers.
> 
> Does someone know how to contact nknazeko?
> 
> nknazeko is maintainer of rpms/selinux-policy
> 
> 
> Thanks for your help,
> 
> Pierre
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>  End of forwarded message 
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Unresponsive packagers: yangrr

[Pierre-Yves Chibon]

Good Morning Everyone,

Since January 17th, we have been emailing daily the following user to notify
that the email they have set in FAS does not correspond to a valid bugzilla
account.
This is a requirement for Fedora packagers.

Does someone know how to contact yangrr?

yangrr is watching rpms/0x
yangrr is watching rpms/hstr
yangrr is maintainer of rpms/kexec-tools


Thanks for your help,

Pierre
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Unresponsive packagers: nknazeko

[Pierre-Yves Chibon]

Good Morning Everyone,

Since November 1st, we have been emailing daily the following user to notify
that the email they have set in FAS does not correspond to a valid bugzilla
account.
This is a requirement for Fedora packagers.

Does someone know how to contact nknazeko?

nknazeko is maintainer of rpms/selinux-policy


Thanks for your help,

Pierre
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Synching user database from Fedora IPA to pagure

[Pierre-Yves Chibon]

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 
> user login in Pagure.

I know this thread has been closed for a while and I'm pretty sure that info has
been passed onto the other place where this discussion evolved, but for the
posterity I'm adding it here as well:

pagure.io does not rely on groups from FAS, only src.fp.o does.
Groups in pagure.io are entirely managed within pagure.io, just the user account
are coming from FAS.
src.fp.p on the other hand is the opposite, all the groups are managed from FAS*
and membership is indeed synced upon login.

So now that it's here for the posterity, we can go back to what we were doing :)

Thanks,
Pierre




*well, an admin needs to create it on src.fp.o with the same name and then it'll
be added to the list of groups pagure asks upon login.
So if you want sig-foo, you create sig-foo in FAS and add its users there, then
you create sig-foo in src.fp.o and membership will sync over time.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Unresponsive packagers: kubo

[Pierre-Yves Chibon]

Good Morning Everyone,

Since June 30th, we have been emailing daily the following user to notify
that the email they have set in FAS does not correspond to a valid bugzilla
account.
This is a requirement for Fedora packagers.

Does someone know how to contact kubo?

kubo is watching rpms/golang-github-docopt-docopt-go
kubo is maintainer of rpms/perl-Array-Utils
kubo is maintainer of rpms/perl-Astro-FITS-CFITSIO
kubo is maintainer of rpms/perl-Crypt-Rijndael
kubo is maintainer of rpms/perl-DBD-MariaDB
kubo is maintainer of rpms/perl-DBD-Mock
kubo is maintainer of rpms/perl-DateTime-Event-Recurrence
kubo is maintainer of rpms/perl-DateTime-Set
kubo is maintainer of rpms/perl-DateTimeX-Easy
kubo is maintainer of rpms/perl-Digest-Perl-MD5
kubo is maintainer of rpms/perl-Email-Valid
kubo is maintainer of rpms/perl-Excel-Writer-XLSX
kubo is maintainer of rpms/perl-Exception-Class-TryCatch
kubo is maintainer of rpms/perl-File-Path-Tiny
kubo is maintainer of rpms/perl-HTML-Table
kubo is maintainer of rpms/perl-HTML-Template-Pro
kubo is maintainer of rpms/perl-HTTP-Body
kubo is maintainer of rpms/perl-Heap
kubo is maintainer of rpms/perl-MooseX-Aliases
kubo is maintainer of rpms/perl-MooseX-NonMoose
kubo is maintainer of rpms/perl-MooseX-Types-Path-Class
kubo is maintainer of rpms/perl-PDL
kubo is maintainer of rpms/perl-SQL-Abstract
kubo is maintainer of rpms/perl-Statistics-Descriptive
kubo is maintainer of rpms/perl-Test-Spec


Thanks for your help,

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: The new Change discussion process is painful

[Pierre-Yves Chibon]

On Wed, Sep 13, 2023 at 10:46:04AM +0200, Vít Ondruch wrote:
> 
> Dne 13. 09. 23 v 9:08 Remi Collet napsal(a):
> > Le 13/09/2023 à 08:09, Adam Williamson a écrit :
> > > On Wed, 2023-09-13 at 05:51 +0200, Kevin Kofler via devel wrote:
> > > > Hi,
> > > > 
> > > > it is really a pain that the Change discussion is now hidden in
> > > > a web forum
> > > > behind a web link, instead of happening right here in this
> > > > mailing list. It
> > > > was promised that Discourse would NOT replace the mailing lists,
> > > > but that is
> > > > effectively no longer the case. Can this "Discourse for Change
> > > > discussion"
> > > > experiment please be stopped? It has no advantages and only adds
> > > > a useless
> > > > layer of indirection.
> > > 
> > > I don't really understand what you mean. AFAICT, every Change that has
> > > been announced at
> > > https://discussion.fedoraproject.org/c/project/changes/89 has also been
> > > announced at
> > > https://lists.fedoraproject.org/archives/list/devel-announce%40lists.fedoraproject.org/
> > > 
> > > , so nothing has been replaced.
> > 
> > Sadly it seems there is some email issues
> > 
> > For a few days, tons of messages are lost
> > so, I also don't receive any of the recent change announcements
> 
> 
> If nothing else, the announcements were previously send to devel-announce
> with devel in CC, while the CC is not included anymore. IOW can we have
> devel back in CC, please?

I'm pretty sure devel is subscribed to devel-announce, so email sent to
devel-announce will/should land on devel as well.


Pierre


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: PDC replacement proposal

[Pierre-Yves Chibon]

On Tue, Sep 05, 2023 at 11:35:19AM -0700, Kevin Fenzi wrote:
> On Mon, Sep 04, 2023 at 04:51:22PM +0200, Tomas Hrcka wrote:
> > Hello all, it took us a few years but we are finally getting rid of the PDC
> > project. Thanks to the ARC research we identified use cases in our tooling
> > and proposed solution.
> > 
> > The essential functionalities currently provided by PDC will be
> > re-implemented in other applications within our release infrastructure, as
> > there are no immediate plans for their replacement and are currently
> > maintained
> > 
> > This work is anticipated to span several months for completion. However,
> > before we embark on this endeavor,
> > 
> > we would like to proactively share our proposed solution with all of you
> > and gather your valuable feedback.
> > 
> > Below, we outline our strategy to preserve the core functionality of PDC by
> > leveraging existing applications within our ecosystem.
> > 
> > Current uses of PDC:
> > 
> > Currently, we rely on the Package Database (PDC) for various data
> > management tasks, including:
> > 
> > 
> >1.
> > 
> >Critical Path Package Tracking: Bodhi leverages PDC to track packages on
> >the critical path.
> 
> As Adam mentioned this is already not in pdc. ;) 
> 
> >2.
> > 
> >Retirement of Packages and Service Level Agreements (SLAs): PDC assists
> >in managing the retirement of packages and their associated SLAs.
> 
> Yeah. The super big one is that its queried from a git commit hook for
> all src.fedoraproject.org git commits. Right now if pdc is down, no one
> could commit anything. 
> 
> 
> >3.
> > 
> >Metadata for Nightly Composes: Our Release Engineering and Fedora
> >Quality Assurance teams rely on PDC for metadata related to nightly
> >composes.
> > 
> > 
> > More info on the usage can be found here:
> > https://fedora-arc.readthedocs.io/en/latest/pdc/users.html
> 
> mass rebuild of modules can be dropped. ;) 
> 
> fedscm-admin is now the scm requests toddler. It still uses pdc tho
> of course. 
>  
> > Specific Endpoints in Use:
> 
> ...snip...
> 
> > Upcoming Changes
> > 
> > Bodhi:
> > 
> > Bodhi will assume responsibility for the following tasks, reducing our
> > reliance on PDC:
> > 
> > /rest_api/v1/releases/: Bodhi will now manage release-related data.
> 
> Do note that bodhi still has a window after we are 'go' for a relase
> where it thinks it's released, but it's not yet. We probibly need to
> address this if we are moving this to bodhi.
> 
> > /rest_api/v1/component-branches/: Specifically, Bodhi will handle the
> > critical-path flag.
> 
> Already done. 
> 
> ...snip...
> > 
> > Pagure-dist-git:
> > 
> > Pagure-dist-git will take over several responsibilities from PDC, including:
> > 
> > /rest_api/v1/product-versions
> > 
> > /rest_api/v1/global-components
> > 
> > /rest_api/v1/component-branches/
> > 
> > /rest_api/v1/component-branch-slas/
> > 
> > Pagure already has a robust database of global components (repositories)
> > and product versions (repository branches).
> > 
> > It utilizes the PDC API to query component branches when a package is
> > retired, and an auxiliary table in Pagure-dist-git will store the reasons
> > for orphaning these components.
> 
> So, I know this will work... but it means more closely tying ourselves
> to pagure-dist-git. ;( 
> 
> With modules going out of the picture, most branches just have the
> release cycle of the fedora or rhel release they are based on, so
> couldn't we just default that somewhere?

In the pkgdb time, the EOL status was basically simply computed from the release
status, ie: what we still have at: 
https://admin.fedoraproject.org/pkgdb/api/collections
(looks like we should fix the branchname in that json)
but we could just go back to this :)


Pierre


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Cleaning infra groups on Pagure and GitHub

[Pierre-Yves Chibon]

On Fri, Sep 01, 2023 at 02:59:12PM +0200, Michal Konecny wrote:
> Hi everyone,
> 
> I did a cleaning in Fedora infra groups in both Github (fedora-infra
> organization https://github.com/fedora-infra) and Pagure (fedora-infra group
> https://pagure.io/group/fedora-infra). I removed the people that were
> inactive in the last year.
> 
> I also removed people from infra-sig FAS group
> (https://accounts.fedoraproject.org/group/infra-sig/) I only left the same
> members as in fedora-infra pagure group (I didn't add any). I thought that
> those groups should be synced, but it doesn't seem like they are. Is this
> correct?

Groups in FAS and pagure aren't automatically synced (unlike with src.fp.o).
I had a script back then that would allow to do it (I believe this may the
something that CentOS use or used):
https://pagure.io/pagure-utility/blob/master/f/sync_fas_group_membership.py
It definitely needs a refresh to become useful again though.


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: congrats to another new sysadmin-mainer

[Pierre-Yves Chibon]

On Wed, Aug 09, 2023 at 10:15:58AM -0700, Kevin Fenzi wrote:
> I'm happy to announce that We have approved a new member in our
> sysadmin-main group:
> 
> adamwill - Adam Williamson

Finally!

Welcome aboard Adam :)

Pierre


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: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Update on DNF05 in Fedora

[Pierre-Yves Chibon]

On Thu, Jul 27, 2023 at 11:27:37AM -0700, Kevin Fenzi wrote:
> On Thu, Jul 27, 2023 at 08:41:42AM -0400, Samantha Bueno wrote:
> > I want to close on a positive note and commend my team for the incredible
> > amount of hard work they have poured into this project thus far, as well as
> > people we've been collaborating with and who have been testing and offering
> > feedback. We have more test days planned and will continue to operate
> > transparently as we proceed through development.
> 
> I wanted to repeat what I noted in the FESCo meeting:
> 
> I'd like to also thank the dnf5 team. It can't be easy to retarget something 
> you
> were working on so long. My thanks for being honest about the status and
> realistic about timeframes and needed work. Kudos!

I'd like to second that, these decisions are never easy to take and thank you
for having the courage of making it.


Pierre


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: congrats to our new sysadmin-mainer

[Pierre-Yves Chibon]

On Mon, Jul 24, 2023 at 01:20:42PM -0700, Kevin Fenzi wrote:
> I'm happy to announce that We have approved a new member in our
> sysadmin-main group:
> 
> darknao - Francois Andrieu
> 
> This is the core group of trusted folks that high level access to most
> everything in fedora infrastructure.
> 
> Francois has done of ton of things around Fedora infrastructure. From
> helping manage our OpenShift clusters, to revamping how our docs and
> websites are built and deployed, to just helping anyone with issues all
> around.
> 
> He has proved his dedication, trustworthiness, and ability.

Congratulations and welcome aboard! :)

Cheers!
Pierre


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: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: clean up on aisle pagure.io

[Pierre-Yves Chibon]

On Tue, Apr 25, 2023 at 02:17:34PM -0700, Kevin Fenzi wrote:
> Hey folks. 
> 
> So, a few weeks back I noticed some spam projects on pagure.io. 
> So, I cleaned up about 165 of them and deactivated 165 spam users.

I took out a few a week or so ago, but not as many, I'm impressed :)

> Now, I see there's another pile of them. :( 
> 
> So, I started to look at cleaning things up again, but I think we need a
> better solution that doesn't involve admins manually cleaning things up.
> ;( Additionally, the clean up is not really very scripted and takes a
> long time to do.
> 
> So, thoughts on a longer term solution? I can think of a few:
> 
> 1. only allow fedora 'contributors' to make new projects. (ie, people in
> at least one non cla/non base ipa group
> Pros:
> - Would very likely cut off the spam or at least cut it way down.
> - Might be easy to implement? (not sure tho!)
> Cons:
> - Would block legit people who aren't fedora contributors.

That might be the easiest as iirc, it's a simple config change (like the one we
had before enforcing fpca on src.fp.o).

 
> 2 Some kind of moderation for new projects
> Pros:
> - Would let non fedora folks make new projects.
> - Would likely cut spam
> Cons:
> - Would require someone to moderate things
> - Would requite us to make some kind of moderation code

Another con:
- will require code change

> 3. A script to do all the cleanup so we could do it easier and some kind
> of 'bad words' blocklist we could put in place to stop obvious spammers
> (most of these are bogus "exam answers" ones)
> Pros:
> - Will cut down on spam some, but not fully.
> Cons:
> - Will have to write the script and implement the blocklist
> - It's likely spammers will use different words over time and avoid the
>   block.

We had basset in the past and always had in mind to hook pagure into it, but we
decommissioned basset before we hooked pagure into it :/


Pierre


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: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: planet

[Pierre-Yves Chibon]

On Fri, Apr 14, 2023 at 07:22:57PM -0300, Pedro Moura wrote:
> >
> > Yeah, hopefully. It might be possible to reach out to those groups...
> > design, security? They have irc rooms, we could try asking there?
> >
> 
> Due to time zone differences and the possibility of some users not seeing
> my message on IRC, I created a survey with 3 questions to gather data on
> the use of subplanets on Fedora Planet. I have sent the survey to the
> devel, design, and desktop mailing lists. I did this because some mailing
> lists that would represent subplanet groups don't exist or don't have
> subscribers.

Might be worth sending it to devel-announce, or maybe even announce?
They should be low(er) traffic and high(er) attention.


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: planet

[Pierre-Yves Chibon]

On Wed, Apr 12, 2023 at 07:44:13PM -, Pedro Moura wrote:
> > On Thu, Apr 06, 2023 at 12:22:59PM -0400, Ben Cotton wrote:
> > 
> > One thing to keep in mind is that from time to time people are having 
> > multiple
> > blogs in their .planet.ini. We could check on fedorapeople how often this
> > happens, and from there see if we need to keep that feature.
> > 
> > 
> > Pierre
> 
> Not very often. There are currently 789 users who have added their blogs to 
> the Fedora Planet directory. However, the last updates to the .planet were as 
> follows:
> 
> - 12 made last year (mostly in the beginning of the year)
> - 20 made in 2021
> - 25 made in 2020
> 
> The rest were updated prior to 2020, and there have been no updates made by 
> any user this year. 

> It's worth noting that some users have more than one blog listed in that file.

This is what I was pointing out, sorry if I wasn't clear :)


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: planet

[Pierre-Yves Chibon]

On Thu, Apr 06, 2023 at 12:22:59PM -0400, Ben Cotton wrote:
> On Wed, Apr 5, 2023 at 6:05 PM Pedro Moura  wrote:
> >
> > Instead of users having to SSH and create a .planet file to add their 
> > blogs, the idea would be simply add their blogs to Fedora Accounts. The 
> > fields in Fedora Accounts should be available in FasJSON, and we are using 
> > this API to create the files for each planet so Pluto can build them.
> 
> That seems like a nice improvement in usability.

One thing to keep in mind is that from time to time people are having multiple
blogs in their .planet.ini. We could check on fedorapeople how often this
happens, and from there see if we need to keep that feature.


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Non-responsive packagers: sbluhm, shaneallcroft

[Pierre-Yves Chibon]

Good Morning Everyone,

The packagers listed here have been receiving a daily email asking them to
either adjust their bugzilla or their FAS account so the email address in FAS
matches an existing bugzilla account.

Having a bugzilla account is mandatory per:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account

- sbluhm contacted since January 11th 2023
sbluhm is maintainer of rpms/apache-commons-digester
sbluhm has a bugzilla override on rpms/apache-commons-digester
sbluhm is maintainer of rpms/disruptor
sbluhm has a bugzilla override on rpms/disruptor
sbluhm is maintainer of rpms/ecj
sbluhm is maintainer of rpms/jakarta-activation
sbluhm is maintainer of rpms/jakarta-servlet
sbluhm has a bugzilla override on rpms/jakarta-servlet
sbluhm is maintainer of rpms/jaxb-api
sbluhm is maintainer of rpms/jdom
sbluhm is maintainer of rpms/mercurial
sbluhm is maintainer of rpms/mxparser
sbluhm has a bugzilla override on rpms/mxparser
sbluhm is main admin of rpms/nekohtml
  rpms/nekohtml co-maintainers: @fnasser, @mizdebsk
sbluhm has a bugzilla override on rpms/nekohtml
sbluhm is maintainer of rpms/openpgm
sbluhm is maintainer of rpms/perl-Mail-RFC822-Address
sbluhm is maintainer of rpms/python-debian
sbluhm is maintainer of rpms/python-geoip2
sbluhm is maintainer of rpms/python-maxminddb
sbluhm is maintainer of rpms/python-ws4py
sbluhm is maintainer of rpms/snakeyaml
sbluhm has a bugzilla override on rpms/snakeyaml
sbluhm is maintainer of rpms/xmlpull
sbluhm has a bugzilla override on rpms/xmlpull
sbluhm is main admin of rpms/xpp3
  rpms/xpp3 co-maintainers: @jerboaa, @mizdebsk
sbluhm has a bugzilla override on rpms/xpp3
sbluhm is maintainer of rpms/xstream
sbluhm has a bugzilla override on rpms/xstream


- shaneallcroft contacted since January 11th 2023
shaneallcroft is main admin of rpms/pyplane
shaneallcroft has a bugzilla override on rpms/pyplane


Does anyone know how to contact them?


Thanks,

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

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

[Pierre-Yves Chibon]

On Thu, Jan 26, 2023 at 05:10:15PM -0800, Kevin Fenzi wrote:
> On Tue, Jan 17, 2023 at 02:49:10PM +0100, Michal Konecny wrote:
> > Hi everybody,
> > 
> > TL;DR; Check if you have correct e-mail in Red Hat Bugzilla Mail field in
> > Fedora Accounts [0]. Empty mail is also OK.
> > 
> > the Red Hat Bugzilla Email field in Fedora Accounts [0] was till now ignored
> > by most of the apps.
> > 
> > This was changed now with the latest update to toddlers [1], which contains
> > most of the syncing scripts that are run automatically in Fedora Infra
> > including distgit_bugzilla_sync [2], packager_bugzilla_sync [3] and
> > packagers_without_bugzilla [4] scripts. All these scripts are using shared
> > methods for working with Fedora Accounts system.
> > 
> > With the addition of scm_request_processor [5] there was a small change in
> > how the Fedora Accounts mails are handled in regard to Red Hat Bugzilla
> > mail. This change caused it to first look for Red Hat Bugzilla Mail and then
> > look at the personnel e-mail associated with the account if Bugzilla mail is
> > not set.
> > 
> > This unfortunately caused issues for some users that had Red Hat Bugzilla
> > Mail field set incorrectly. I was the one who did the change and I actually
> > forgot about it, because it happened at the beginning of
> > scm_request_processor development cycle and I didn't know it could have that
> > large impact. So I apologize for any issue this could have caused for you.
> > 
> > If you are one of the users, who were impacted by this change, you can fix
> > it by adding correct Red Hat Bugzilla mail to your Fedora Account. You can
> > do this in Settings->Emails in Fedora Accounts page [0].
> > 
> > We will fix the message that is being sent to packagers without Bugzilla
> > e-mail to correspond with this change.
> 
> Hello everyone. 
> 
> After this we still have 4 users who's bugzilla email does not exist. :( 
> 
> They are: 

> npmccallum

Nathaniel has been on the list for 2 or 3 months at this point. I've been
wanting to start the non-responsive process a while back but got a bit lazy to
look at the exact date when we started sending him emails :(

Thanks for starting this Kevin!

Pierre


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Rethinking fedora websites deployment

[Pierre-Yves Chibon]

On Thu, Nov 24, 2022 at 07:25:03PM +0100, darknao wrote:
> 
> 
> On 2022-11-24 18:58, Jan K wrote:
> > What is likelyhood of Openshift going down?   A would be best
> > solution if stable enough.
> > 
> >  copperi
> > 
> 
> Openshift is quite stable. But everything around it may not. Having a
> network outage, internal VPN issue, datacenter incident, or just an
> openshift migration that goes wrong can still happen.

The other aspect is that you would then suddenly have all the worldwide traffic
goes to our static website converge onto our openshift cluster instead of
hitting the geo-distributed proxies.
That will have an impact on the user side: suddenly the websites take longer to
reach (openshift is in the US instead of me hitting the nearby proxy) as well as
on the bandwidth usage for the openshift cluster itself.

So I would not recommend serving these websites from our openshift cluster
directly. There is real value in the proxies in the loop.


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

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

[Pierre-Yves Chibon]

On Thu, Oct 13, 2022 at 10:36:52AM +0300, Panu Matilainen wrote:
> On 10/12/22 17:47, Stephen Smoogen wrote:
> > 
> > 
> > On Wed, 12 Oct 2022 at 10:32, Kevin P. Fleming  > > wrote:
> > 
> > On 10/12/22 08:59, Stephen Smoogen wrote:
> >  > Maybe call it the Fedora Update Manager 'FUM' ?
> > 
> > Unless we're going to call it RUM when it makes its way into RHEL, that
> > name may not be the best choice :-)
> > 
> > 
> > Well Red Hat shipped the Yellowdog Update Manager for 2 releases so I am
> > sure they can go with FUM or RUM (RPM Update Manager)..
> 
> RPM Update Manager, an easily pronouncable and distro agnostic acronym which
> even makes sense. Now that would be a hard sell...

Depends, once the age question is resolved, buying RUM should be fairly straight
forward :-p


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: RHEL9 migration

[Pierre-Yves Chibon]

On Wed, Sep 28, 2022 at 11:35:09AM -0700, Kevin Fenzi wrote:
> On Tue, Sep 27, 2022 at 04:04:41PM +0200, Neal Gompa wrote:
> > On Tue, Sep 27, 2022 at 3:20 PM Neal Gompa  wrote:
> > >
> > > On Tue, Sep 27, 2022 at 3:01 PM Stephen Smoogen  
> > > wrote:
> > > >
> > > >
> > > >
> > > > On Mon, 26 Sept 2022 at 17:56, Kevin Fenzi  wrote:
> > > >>
> > > >> Here's my thoughts on rhel9 upgrades.
> > > >>
> > > >> We have 188 RHEL7 or RHEL8 instances (counting both vm's and bare 
> > > >> hardware).
> > > >>
> > > >>
> > > >> Some will just not move anytime soon:
> > > >>
> > > >
> > > > Is it possible to look at these as 'why does this need fedmsg?' 'what 
> > > > happens if it doesn't have fedmsg', and  'do we need it?'
> 
> Sure, we can. 
> 
> But at this point I think we have already gotten rid of most of the
> things we really don't need. So, someone will need to make a compelling
> argument for dropping things (at least to me).
> 
> > > > mailman01 is one where maybe not having it on fedmsg wouldn't be earth 
> > > > shattering
> > > > but it also has the bigger problem of all its libraries being FTBFS in 
> > > > Fedora and
> > > > being retired from there. At which point we go with 'do we need to run 
> > > > mailing lists?'
> 
> Well, until we figure out how to otherwise handle the use cases that 
> mailing lists handle now?
> 
> For example: all the -sig groups in pagure have mailing lists that get
> all the bugs send to it. We would need to find another way to get bug
> content to those groups (and still keep it private). 
> scm-commits is still important IMHO, because its a external record of
> changes. If someone messed with git history, that might be the only
> record of real changes. 
> devel/test/a few other lists are still active. They would have to move
> to discourse or otherwise have something. 
> 
> So, needs a concrete plan. I am not at all in favor of 'turn it off'
> without moving all the needs. 

I took it more as a: do we need to *run* mailing list? More than a: Do we need
mailing list?
Ie: should we look to host our lists for us?

That's a fair question and I can see pros and cons to it, but I'm definitely in
the camp of "we need mailing lists" :)


Pierre


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: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Inactive provenpackagers to be removed from group

[Pierre-Yves Chibon]

On Thu, Aug 11, 2022 at 02:07:08PM -0400, Ben Cotton wrote:
> In accordance with FESCo policy[1], the following provenpackagers will
> be submitted for removal in two weeks based on a lack of Koji builds
> submitted in the last six months. If you received this directly, you
> can reply off-list to indicate you should still be in the
> provenpackager group.
> 
> Note that removal from this group is not a "punishment" or a lack of
> appreciation for the work you have done. The intent of the process is
> to ensure contributors with distro-wide package privileges are still
> active and responsive. This process is done regularly at the branch
> point in each release.
> 
> [1] 
> https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/#_maintaining_provenpackager_status
> 
> Checked 140 provenpackagers
> The following 14 provenpackagers have not submitted a Koji build since
> at least 2022-02-03 00:00:00:
> pingou

I have indeed done very little packaging lately and in the spirit of only having
the level of access that you need, I'm fine with being removed from the
provenpackager group.
I just hope that if I need this level of access in the future it won't be
painful to ask for them again :)


Thanks for doing this!

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Debugging Datanommer performance issues

[Pierre-Yves Chibon]

On Mon, Aug 15, 2022 at 10:49:50AM -0700, Kevin Fenzi wrote:
> On Thu, Aug 11, 2022 at 09:51:06AM +0200, Aurelien Bompard wrote:
> > Hey folks!
> > 
> > There's been a report of queries long enough to cause a timeout in
> > datagrepper:
> > https://github.com/fedora-infra/datagrepper/issues/467
> > I don't think those queries should take so much time, and I'd like to debug
> > this performance issue, possibly try a couple new indexes on the tables,
> > etc. However, I can't reproduce the issue on staging, probably because the
> > datanommer database there is much smaller.
> > So I was wondering what is the best course of action. I see the following
> > options:
> > 
> >  1. Sync the prod DB to staging. This looks like an obvious first choice,
> > but the messages in the staging DB actually come from the staging
> > environment and are used by other contributors to check that their service
> > is behaving properly on staging. Also, the topic prefix of the messages is
> > different on staging and on prod, so syncing the DB with prod messages and
> > then adding staging ones may cause a mess.
> 
> I think it might work, but not sure we have anyplace off hand with
> enough disk space. We might. I can look more if this is the way we want
> to go. 
> 
> > 2. Having a second datanommer DB in prod, and syncing them. The problem
> > here is of course the disk space required. I don't know if that's even
> > possible with the hardware we have.
> 
> It might be possible, but it's not a good way to go I don't think.
> 
> > 3. Something else?
> 
> Perhaps a aws instance? Just restore the db snapshot from prod and then
> spin up a small datagrepper instance to talk to it?

In the past we've imported the prod DB instance into an aws instance when we
needed to play around with it (that's also how ARC investigated the db changes
when it looked at datanommer/datagrepper).


Pierre


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: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: congrats to our new sysadmin-mainers

[Pierre-Yves Chibon]

On Wed, Aug 03, 2022 at 07:56:29AM -0700, Kevin Fenzi wrote:
> I'm happy to announce that We have approved several folks into the
> sysadmin-main group:
> 
> nphilipp - Nils Philippsen
> zlopez - Michal Konečný
> ryanlerch - Ryan Lerch
> 
> This is the core group of trusted folks that high level access to most
> everything in fedora infrastructure.
> 
> Nils is a long time contributor who has worked on a bunch of things,
> including our ipa sudo/ssh permissions setup. 
> 
> Michal has worked on many of our applications and is also serving to
> help keep us on plan for planned work over the quarters. 
> 
> Ryan has been around for a long time working on many things, including
> our revamped status application, FMN, gitlab permissions and more. 
> 
> They have both proved their dedication, trustworthiness, and ability.
> 
> Congrats to them all!
> 
> Use your powers for good! :)

Congratulations folks!

Note: we don't get badges for the parking nor parking places near the entrance,
but still pretty cool to have you there! ;-)


Pierre


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: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Non-responsive packagers: benzea

[Pierre-Yves Chibon]

On Thu, Jul 21, 2022 at 11:30:07AM +0200, Benjamin Berg wrote:
> Hi,
> 
> sorry for not dealing with this earlier. I was somewhat out for a
> while, and didn't give the mail much significance.
> 
> What happened is that I'll be leaving Red Hat. As a first step, I
> changed my FAS email address while explicitly keeping my Red Hat
> address for bugzilla for now.
> 
> I thought that just having two different addresses on
> accounts.fedorproject.org would work, but I suppose I would also need
> to add myself to
> https://pagure.io/fedora-infra/ansible/raw/main/f/roles/openshift-apps/toddlers/templates/email_overrides.toml
> 
> Either way, I think I'll just fix it by creating the corresponding
> bugzilla account so that the two addresses are in sync again.

Thanks for addressing this! :)


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive packagers: benzea

[Pierre-Yves Chibon]

On Mon, Jul 18, 2022 at 10:12:55AM +0200, Tomáš Popela wrote:
> Hi Pierre,
> 
> Is the subject right? It talks about "michaelanguskelly", but the queries
> are for Benjamin (benzea). I can talk to Benjamin if needed (already
> pointed him at this thread just in case).

Hi Tomáš,

Thanks for pointing this out, that's what I get for re-using an old email as
template :(

The correct user is benzea indeed.

Thanks for pointing him to this thread!


Pierre


> On Mon, Jul 18, 2022 at 9:59 AM Pierre-Yves Chibon 
> wrote:
> 
> > Good Morning Everyone,
> >
> > The packagers listed here have been receiving a daily email asking them to
> > either adjust their bugzilla or their FAS account so the email address in
> > FAS
> > matches an existing bugzilla account.
> >
> > Having a bugzilla account is mandatory per:
> >
> > https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account
> >
> > - benzea contacted since June 23rd 2022
> > benzea is maintainer of rpms/bolt
> > benzea is main admin of rpms/devtodo
> > benzea has a bugzilla override on rpms/devtodo
> > benzea is main admin of rpms/fprintd
> > benzea has a bugzilla override on rpms/fprintd
> > benzea is main admin of rpms/fwts
> > benzea has a bugzilla override on rpms/fwts
> > benzea is maintainer of rpms/gamemode
> > benzea is main admin of rpms/gnome-network-displays
> > benzea has a bugzilla override on rpms/gnome-network-displays
> > benzea is main admin of rpms/libfprint
> > benzea has a bugzilla override on rpms/libfprint
> > benzea is maintainer of rpms/libusb
> > benzea is maintainer of rpms/libusb-compat-0.1
> > benzea is maintainer of rpms/libusb1
> > benzea is main admin of rpms/libusbx
> > benzea has a bugzilla override on rpms/libusbx
> > benzea is main admin of rpms/thermald
> > benzea has a bugzilla override on rpms/thermald
> > benzea is maintainer of rpms/umockdev
> > benzea is maintainer of rpms/upower
> > benzea is main admin of rpms/uresourced
> > benzea has a bugzilla override on rpms/uresourced
> >
> >
> >
> > Does anyone know how to contact them?
> >
> >
> > Thanks,
> >
> > Pierre
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> > Do not reply to spam on the list, report it:
> > https://pagure.io/fedora-infrastructure
> >

> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Non-responsive packagers: michaelanguskelly

[Pierre-Yves Chibon]

Good Morning Everyone,

The packagers listed here have been receiving a daily email asking them to
either adjust their bugzilla or their FAS account so the email address in FAS
matches an existing bugzilla account.

Having a bugzilla account is mandatory per:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account

- benzea contacted since June 23rd 2022
benzea is maintainer of rpms/bolt
benzea is main admin of rpms/devtodo
benzea has a bugzilla override on rpms/devtodo
benzea is main admin of rpms/fprintd
benzea has a bugzilla override on rpms/fprintd
benzea is main admin of rpms/fwts
benzea has a bugzilla override on rpms/fwts
benzea is maintainer of rpms/gamemode
benzea is main admin of rpms/gnome-network-displays
benzea has a bugzilla override on rpms/gnome-network-displays
benzea is main admin of rpms/libfprint
benzea has a bugzilla override on rpms/libfprint
benzea is maintainer of rpms/libusb
benzea is maintainer of rpms/libusb-compat-0.1
benzea is maintainer of rpms/libusb1
benzea is main admin of rpms/libusbx
benzea has a bugzilla override on rpms/libusbx
benzea is main admin of rpms/thermald
benzea has a bugzilla override on rpms/thermald
benzea is maintainer of rpms/umockdev
benzea is maintainer of rpms/upower
benzea is main admin of rpms/uresourced
benzea has a bugzilla override on rpms/uresourced



Does anyone know how to contact them?


Thanks,

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Email replies to src.fpo notifications

[Pierre-Yves Chibon]

On Thu, Jul 14, 2022 at 10:53:30AM -0700, Kevin Fenzi wrote:
> On Wed, Jul 13, 2022 at 08:13:23PM -, Frank R Dana Jr. wrote:
> > Recently, after receiving an email notification regarding a pull request at 
> > src.fedoraproject.org, I attempted[1] to update the discussion via email 
> > reply to the notification email.
> > 
> > That attempt was not successful. Moreover, I was only made AWARE that the 
> > attempt was  unsuccessful 24 hours later, when Google's MTA responded with 
> > an undeliverable notification saying that it couldn't contact the recipient 
> > email, pag...@pkgs.fedoraproject.org.
> > 
> > If email reply to src.fpo notifications is supposed to be working, it's 
> > not. If it's INTENDED  not to be working, then perhaps the reply address 
> > for notifications could be set to something that bounces immediately 
> > (donotre...@fedoraproject.org or similar, perhaps?), rather than an address 
> > at a non-responsive hostname that's subject to lengthy timeouts before the 
> > status of the attempted reply is updated?
> 
> So, I am not sure what was intended long ago, but to my understanding
> it's never worked, nor was it setup to work. 

While we have it working for pagure.io it does not work (and never has) for
src.fedoraproject.org (the notification does not invite you to reply unlike on
pagure.io).

I'm +1 on keeping it not working


Pierre


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: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Software Bill of Materials for Fedora

[Pierre-Yves Chibon]

On Mon, Jul 11, 2022 at 12:53:57PM +1000, Jason Shepherd wrote:
> Hello Fedora Infrastructure team,
> 
> Red Hat Product Security are building an application called Component
> Registry to meet the requirements set out in the recent Executive Order
> 14028 [1], "Improving the Nation's Cybersecurity". The executive order
> requires that software producers and suppliers should take steps to report
> and validate a listing of all components included in or used by their
> software products, aka a Software Bill of Materials. We'd like to build our
> application in the open by providing the source code to the
> opensource community.
> 
> Since all the Red Hat build infrastructure is internal to Red Hat, we'd
> like also provide this service to Fedora so that our open source project
> can have a life outside of Red Hat's corporate firewall. I suspect we are
> close to being able to provide an example of the Software Bill of Materials
> (SBOM) for Fedora, since it is built in a very similar way to Red Hat
> Enterprise Linux. The reason for reaching out is to find out if you are
> interested in hosting an SBOM for Fedora or not. We could build it inside
> the Red Hat firewall, and provide a static file for each target release of
> Fedora, undated periodically. Alternatively we could run the application
> somewhere on your infrastructure in order to make the data available via an
> API on demand. In which case we'd probably need to help to maintain that
> infrastructure.

This sounds really interesting, thanks for reaching out!

Do you know what kind of requirements your application has currently? Can it
easily be run on openshift?
Which approach would you prefer? Is there an interest in hosting a "live"
instance in the Fedora Infrastructure, beside having an API instead of static
files? (Are the static files JSON files or HTML btw?)


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Once again, more than 8 days delayed notifications

[Pierre-Yves Chibon]

On Sat, Jul 09, 2022 at 09:36:14AM -0400, Stephen Smoogen wrote:
> On Sat, 9 Jul 2022 at 09:25, Ralf Corsépius  wrote:
> 
> > Hi,
> >
> > I thought the notification delay mess was fixed. Apparently, I was wrong.
> >
> >
> 
> No, I believe the service which is behind these emails is called FMN. It is
> very fragile for multiple reasons where it falls over for different reasons
> all the time. It is the reason why it is on the top of being replaced by
> CPE in this quarter (aka by October-ish). 

Just a quick note, I doubt the app will be re-written and deploy in a single
quarter, I expect this to be more a multi-months effort. So while it has the top
of the priority list for CPE to work on, it'll still take a little time before
we see a v4 (we've already restructured it 3 times).

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Once again, more than 8 days delayed notifications

[Pierre-Yves Chibon]

On Sat, Jul 09, 2022 at 05:16:55PM +0200, Ralf Corsépius wrote:
> 
> 
> Am 09.07.22 um 15:36 schrieb Stephen Smoogen:
> > 
> > 
> > On Sat, 9 Jul 2022 at 09:25, Ralf Corsépius  > > wrote:
> > 
> > Hi,
> > 
> > I thought the notification delay mess was fixed. Apparently, I was
> > wrong.
> > 
> > 
> > 
> > No, I believe the service which is behind these emails is called FMN. It
> > is very fragile for multiple reasons where it falls over for different
> > reasons all the time. It is the reason why it is on the top of being
> > replaced by CPE in this quarter (aka by October-ish). Until that
> > happens, please be aware that these notifications are likely to come in
> > bursts as things go up and down. I would also suggest that turning off
> > as many notifications as you can would help the load as one of the
> > largest email problems Fedora Infrastructure has is the many people who
> > have turned on getting email on a lot of events.
> 
> Why don't you turn this stuff off globally and send the guys behind it back
> to the drawing board?
> 
> In its present shape it's just dysfunctional and not helpful at all.

It is very much self-service, so you can easily turn off the notifications for
your account if you wish to:
https://apps.fedoraproject.org/notifications


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: [RFC] Build tag in RPM: from NVR to NVRB

[Pierre-Yves Chibon]

On Tue, Jun 21, 2022 at 12:27:57AM +0200, Fabio Valentini wrote:
> On Tue, Jun 21, 2022 at 12:15 AM Neal Gompa  wrote:
> >
> > On Mon, Jun 20, 2022 at 3:48 PM Zbigniew Jędrzejewski-Szmek
> >  wrote:
> > >
> > > On Sat, Jun 18, 2022 at 01:05:31PM +0200, Aleksandra Fedorova wrote:
> > > > The most visible impact of the proposal would be the filename change:
> > > >
> > > >   Current: dnf-4.9.0-12.fc36.noarch.rpm
> > > >   Proposed: dnf-4.9.0-12.fc36.34897715.noarch.rpm
> > >
> > > The history of development of rpm and the ecosystem has shown that
> > > modifications that are visibile at the level of the output binary rpm
> > > have a long implementation tail for the ecosystem. In particular, if
> > > we allow add the build-number information, many many consumers will
> > > need to adjust for this, from trivial things like regexps to match
> > > '%dist.rpm' in the filename to complicated things that extract and
> > > make use of the version field. So if we want to add a new feature
> > > here, a much strong justification why what we have already is not
> > > enough would need to be provided.
> > >
> >
> > This is already something people have to expect, since our existing
> > policy permits a tailing number and it is used for various purposes.
> 
> Well, it's complicated.
> 
> There's currently a 100% foolproof way to parse NEVRs into their
> components, because there are *always* two "-" separators (when
> counting from the end) that separate "name", "epoch:version", and
> "release" (i.e. you can do nevr.rsplit("-", 2) in Python, and you get
> 100% correct results for 100% of packages in Fedora repositories).

That is already broken today with modules where the stream which is included in
the name can have '-' in them.


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: openshift 3->4 moves status and info needed

[Pierre-Yves Chibon]

On Fri, Jun 17, 2022 at 12:25:08PM +0200, Vít Ondruch wrote:
> 
> Dne 15. 06. 22 v 1:49 Kevin Fenzi napsal(a):
> > Greetings everyone.
> > 
> > I finally had a quiet afternoon to really dig into the ocp3->4
> > migration.
> > 
> > We have a total of 64 unique applications/projects over the 4 clusters
> > (ocp3 prod/stg and ocp4 prod/stg).
> > 
> > Of those 20 have been moved to ocp4 (either stg or prod or both).
> > 
> > There's 4 that are sort of in the midst of moving to ocp4 prod, but need
> > some more tweaking (flatpak-indexer, release-monitoring,
> > discourse2fedmsg, transtats).
> > 
> > I'd like to propose removing the following 9 entirely:
> > REMOVE: simple-koji-ci.yml
> >( This was retired a long time ago)
> 
> 
> Does it mean that simple-koji-ci will be decommissioned soon? That is sad
> news.

It has not been running for quite a while now.
There is an equivalent service provided by the fedora-ci folks, so you shouldn't
have seen it in any PR for a long time.


Pierre


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: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: on rpms

[Pierre-Yves Chibon]

On Tue, May 24, 2022 at 06:24:10PM +0200, Aurelien Bompard wrote:
> > Something like:
> >>
> >> Applications in Fedora Infrastructure may be deployed via non rpm
> >> methods (as long as they obey licensing guidelines (
> >> https://fedoraproject.org/wiki/Infrastructure_Licensing )). For those
> >> applications, creating and maintaining an rpm is optional.
> >>
> >>
> > How about:
> >
> > Applications in Fedora Infrastructure need to be deployed in an auditable
> > and repeatable way. These methods need to allow someone to determine which
> > software was installed, when it was installed, and what it was meant to be
> > done (example: rpms or podman build scripts for containers). The goal is to
> > be kind to our future selves at 2 am who need to figure out why a critical
> > application is broken and how to rebuild and redeploy as needed.
> >
> 
> Yeah that seems sensible (although I'm not sure of the wording of "what it
> was meant to be done", but I think I get it).
> This would satisfy apps built with s2i as long as they are pinning their
> dependencies with something like poetry or pipenv. We are currently
> standardizing on poetry but any would do as long as deps are pinned).
> 
> For s2i based apps, I see two ways of ensuring repeatability, one being
> stricter but more transparent than the other:
> 1. have the buildconfig track a production branch upstream, and rely on the
> build log to know which exact commit was built
> 2. have the buildconfig specify the commit hash, and change the buildconfig
> each time we want to deploy a new prod version

A third option which we've used in a few of our apps is to have a specific
branch (or branches) for our deployment. That branch can then have commits
dedicated to our deployment, such as support for s2i which aren't needed in the
'main' branch.
We could do things like the version pining in that branch as well, making it
easy/easier for people to package the application while still helping us ensure
the reproducibility we want in openshift.


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Non-responsive packagers: michaelanguskelly

[Pierre-Yves Chibon]

Good Morning Everyone,

The packagers listed here have been receiving a daily email asking them to
either adjust their bugzilla or their FAS account so the email address in FAS
matches an existing bugzilla account.

Having a bugzilla account is mandatory per:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account

- michaelanguskelly contacted since March 29th
michaelanguskelly is maintainer of rpms/python-oauthlib


Does anyone know how to contact them?


Thanks,

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: FBR: update mirror ip addresses for kernel.org

[Pierre-Yves Chibon]

On Tue, Mar 22, 2022 at 02:34:57PM +, Mark O'Brien wrote:
> Hi All,
> 
> We have had a request from the people at mirrors.kernel.org to update their
> IP address: https://pagure.io/fedora-infrastructure/issue/10598
> 
> This PR should take care of it
> https://pagure.io/fedora-infra/ansible/pull-request/1010
> 
> I would also need to run the download playbook to apply the change.
> 
> Let the +1/-1's flow please.

+1 for me as well


Pierre


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: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Can't fedpkg new-sources (403)

[Pierre-Yves Chibon]

On Wed, Mar 16, 2022 at 01:45:52PM -0400, Neal Becker wrote:
>On Wed, Mar 16, 2022 at 1:38 PM Neal Becker <[1]ndbeck...@gmail.com>
>wrote:
> 
>  I believe it is failing on the line:
>    File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line
>  298, in upload
>      if self.remote_file_exists(name, filename, hash):
>    File "/usr/lib/python3.10/site-packages/pyrpkg/lookaside.py", line
>  259, in remote_file_exists
>      self.raise_upload_error(status)
>  So maybe the file already exists in the cache?  But then, sources has
>  not been updated, and if I try 
>  fedpkg local it will attempt to build the old version 1.8.1, not the new
>  1.9.0.
> 
>OK, so unuran-1.9.0.tar.gz already exists in the cache.  So I had to
>manually update sources by running
>md5sum unuran-1.9.0.tar.gz, which luckily I just guessed.  Now everything
>seems to be working fine.

Also, we no longer use md5sum in our lookaside cache by default, but sha512, so
you may have more chances using that algorithm :)


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Freeze Break Request

[Pierre-Yves Chibon]

On Mon, Mar 14, 2022 at 02:18:09PM +, Mark O'Brien wrote:
> Hi All,
> 
> There are a few of our proxies in AWS that are giving us errors which I
> believe are related to low memory. I would like to reinstall a few of
> these. I would do one at a time so disruption should be minimal. There is a
> few benefits.
> 
> 1. Increase server resources to allow for a bigger load
> 2. Stop using instances with ephemeral storage to avoid a need for a
> reinstall in future
> 3. Assign Elastic IPs to allow for zero downtime replacement in future
> 
> Let me know what you think and add +1/-1 as you see fit.

+1 for me as well


Pierre


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: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Do we have any policy for disabling inactive users

[Pierre-Yves Chibon]

On Sat, Feb 12, 2022 at 10:29:54AM +, Mattia Verga via devel wrote:
> Il 11/02/22 20:24, Kevin Fenzi ha scritto:
> > On Fri, Feb 11, 2022 at 11:33:13AM +, Mattia Verga via devel wrote:
> >> Il 11/02/22 12:20, Florian Weimer ha scritto:
> >>> * Mattia Verga via devel:
> >>>
>  Il 11/02/22 10:41, Miro Hrončok ha scritto:
> > On 11. 02. 22 10:12, Mattia Verga via devel wrote:
> >> Where are those 2543 packagers come from? src.fedoraproject.org only
> >> shows 1787 users in the packager group:
> >>
> >> https://src.fedoraproject.org/api/0/group/packager
> > They might have never even logged into src.fedoraproject.org
> >
>  \o/ So, I think those 756 can be added to the removal list as well...
> >>> Why?  Isn't logging into src.fedoraproject.org optional from a workflow
> >>> perspective?
> >>>
> >> I suppose "logging" means that src.fedoraproject.org has no knowledge
> >> about that user... so that user never pushed any commit / PR / comment.
> > I don't think just pushing a commit would log you into pagure. You need
> > to login to the web interface for it to create/refresh your account.
> > PR's and comments would definitely, but just pushing commits would not.
> >
> mmm... I suppose that, even if a user only uses CLI to push a commit,
> pagure needs to verify its credentials and associates the commit to the
> user in the web UI... so pagure MUST know about the user in its database.

I was going to say that only packagers have a shell account on src.fp.o and
should thus be allowed to push, but I've quickly checked the code and you are
correct, in order to determine if an user is allowed to push to a specific
package, we check their access level in pagure's database (ie: are they a
package admin? committer? collaborator?), so I don't think a packager that has
never logged in on src.fp.o would be allowed to push a commit.


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Do we have any policy for disabling inactive users

[Pierre-Yves Chibon]

On Fri, Feb 11, 2022 at 11:24:24AM -0800, Kevin Fenzi wrote:
> On Fri, Feb 11, 2022 at 11:33:13AM +, Mattia Verga via devel wrote:
> > Il 11/02/22 12:20, Florian Weimer ha scritto:
> > > * Mattia Verga via devel:
> > >
> > >> Il 11/02/22 10:41, Miro Hrončok ha scritto:
> > >>> On 11. 02. 22 10:12, Mattia Verga via devel wrote:
> >  Where are those 2543 packagers come from? src.fedoraproject.org only
> >  shows 1787 users in the packager group:
> > 
> >  https://src.fedoraproject.org/api/0/group/packager
> > >>> They might have never even logged into src.fedoraproject.org
> > >>>
> > >> \o/ So, I think those 756 can be added to the removal list as well...
> > > Why?  Isn't logging into src.fedoraproject.org optional from a workflow
> > > perspective?
> > >
> > I suppose "logging" means that src.fedoraproject.org has no knowledge
> > about that user... so that user never pushed any commit / PR / comment.
> 
> I don't think just pushing a commit would log you into pagure. You need
> to login to the web interface for it to create/refresh your account.
> PR's and comments would definitely, but just pushing commits would not.
> 
> > Have I misunderstood? Does src.fedoraproject.org not recognize a user to
> > be in the packager group if they never logged in and only pushed things
> > by CLI?
> 
> I think that is indeed the case, but I'm not 100% sure. 
> Perhaps Pingou could chime in on this. 

Correct on both accounts. src.fp.o has no idea who someone is until they log in
via the user-interface, so the same thing applies for group membership.


Pierre


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive packagers: lef, msehnout, shaneallcroft

[Pierre-Yves Chibon]

On Mon, Feb 07, 2022 at 10:47:11AM +0100, Fabio Valentini wrote:
> On Mon, Feb 7, 2022 at 9:58 AM Pierre-Yves Chibon  wrote:
> >
> > Good Morning Everyone,
> >
> > The packagers listed here have been receiving a daily email asking them to
> > either adjust their bugzilla or their FAS account so the email address in 
> > FAS
> > matches an existing bugzilla account.
> >
> > Having a bugzilla account is mandatory per:
> > https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account
> >
> > - msehnout contacted since December 15th
> >
> > msehnout is watching rpms/bind
> > msehnout is watching rpms/bind99
> > msehnout is maintainer of rpms/ipcalc
> > msehnout is watching rpms/libpcap
> > msehnout is maintainer of rpms/osbuild
> > msehnout is maintainer of rpms/osbuild-composer
> > msehnout is watching rpms/pure-ftpd
> > msehnout is watching rpms/tcpdump
> > msehnout is watching rpms/vsftpd
> > msehnout is watching rpms/wireshark
> >
> > (I will be opening a FESCo ticket for msehnout right now as this is the 
> > second
> > email sent to the devel list)
> >
> > - shaneallcroft contacted since January 28th
> >
> > shaneallcroft is main admin of rpms/pyplane
> > shaneallcroft has a bugzilla override on rpms/pyplane
> >
> > - lef contacted since January 22nd
> >
> > (lef's package list is quite large, so I'm putting it at the very end of 
> > this
> > email)
> 
> We already went through the non-responsive maintainer process for lef in 2019:
> https://pagure.io/fesco/issue/2160
> 
> Looks like the script to remove them from packages either hasn't been
> around, or hasn't been run

Ok, thanks for the info, I'll run the script for lef then :)

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Non-responsive packagers: lef, msehnout, shaneallcroft

[Pierre-Yves Chibon]

Good Morning Everyone,

The packagers listed here have been receiving a daily email asking them to
either adjust their bugzilla or their FAS account so the email address in FAS
matches an existing bugzilla account.

Having a bugzilla account is mandatory per:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account

- msehnout contacted since December 15th

msehnout is watching rpms/bind
msehnout is watching rpms/bind99
msehnout is maintainer of rpms/ipcalc
msehnout is watching rpms/libpcap
msehnout is maintainer of rpms/osbuild
msehnout is maintainer of rpms/osbuild-composer
msehnout is watching rpms/pure-ftpd
msehnout is watching rpms/tcpdump
msehnout is watching rpms/vsftpd
msehnout is watching rpms/wireshark

(I will be opening a FESCo ticket for msehnout right now as this is the second
email sent to the devel list)

- shaneallcroft contacted since January 28th

shaneallcroft is main admin of rpms/pyplane
shaneallcroft has a bugzilla override on rpms/pyplane

- lef contacted since January 22nd

(lef's package list is quite large, so I'm putting it at the very end of this
email)


Does anyone know how to contact them?


Thanks,

Pierre


lef is maintainer of rpms/HikariCP
lef has a bugzilla override on rpms/HikariCP
lef is maintainer of rpms/PyXB
lef has a bugzilla override on rpms/PyXB
lef is maintainer of rpms/aesh
lef has a bugzilla override on rpms/aesh
lef is maintainer of rpms/airline
lef has a bugzilla override on rpms/airline
lef is maintainer of rpms/antlr-maven-plugin
lef has a bugzilla override on rpms/antlr-maven-plugin
lef is maintainer of rpms/antlr3
lef is maintainer of rpms/antlr4
lef has a bugzilla override on rpms/antlr4
lef is watching rpms/apache-commons-csv
lef has a bugzilla override on rpms/apache-commons-csv
lef is maintainer of rpms/apache-james-project
lef has a bugzilla override on rpms/apache-james-project
lef is watching rpms/apache-mime4j
lef has a bugzilla override on rpms/apache-mime4j
lef is maintainer of rpms/apache-poi
lef has a bugzilla override on rpms/apache-poi
lef is maintainer of rpms/apiviz
lef has a bugzilla override on rpms/apiviz
lef is maintainer of rpms/aries-blueprint-annotation-api
lef has a bugzilla override on rpms/aries-blueprint-annotation-api
lef is maintainer of rpms/aries-blueprint-api
lef has a bugzilla override on rpms/aries-blueprint-api
lef is maintainer of rpms/aries-blueprint-core
lef has a bugzilla override on rpms/aries-blueprint-core
lef is maintainer of rpms/aries-blueprint-parser
lef has a bugzilla override on rpms/aries-blueprint-parser
lef is maintainer of rpms/aries-proxy-api
lef has a bugzilla override on rpms/aries-proxy-api
lef is maintainer of rpms/aries-proxy-impl
lef has a bugzilla override on rpms/aries-proxy-impl
lef is maintainer of rpms/aries-quiesce-api
lef has a bugzilla override on rpms/aries-quiesce-api
lef is maintainer of rpms/aries-util
lef has a bugzilla override on rpms/aries-util
lef is maintainer of rpms/arquillian-core
lef has a bugzilla override on rpms/arquillian-core
lef is maintainer of rpms/artemis
lef has a bugzilla override on rpms/artemis
lef is maintainer of rpms/artemis-wildfly-integration
lef has a bugzilla override on rpms/artemis-wildfly-integration
lef is maintainer of rpms/atool
lef has a bugzilla override on rpms/atool
lef is watching rpms/auto
lef has a bugzilla override on rpms/auto
lef is maintainer of rpms/avro
lef has a bugzilla override on rpms/avro
lef is watching rpms/bean-validation-api
lef has a bugzilla override on rpms/bean-validation-api
lef is maintainer of rpms/bytelist
lef has a bugzilla override on rpms/bytelist
lef is watching rpms/c3p0
lef is maintainer of rpms/castor
lef has a bugzilla override on rpms/castor
lef is maintainer of rpms/checkstyle
lef is maintainer of rpms/classmate
lef has a bugzilla override on rpms/classmate
lef is maintainer of rpms/cli-parser
lef has a bugzilla override on rpms/cli-parser
lef is maintainer of rpms/conakry-fonts
lef has a bugzilla override on rpms/conakry-fonts
lef is maintainer of rpms/cookcc
lef has a bugzilla override on rpms/cookcc
lef is maintainer of rpms/cryptacular
lef has a bugzilla override on rpms/cryptacular
lef is watching rpms/crypto-policies
lef is maintainer of rpms/cxf
lef has a bugzilla override on rpms/cxf
lef is maintainer of rpms/cxf-build-utils
lef has a bugzilla override on rpms/cxf-build-utils
lef is maintainer of rpms/cxf-xjc-utils
lef has a bugzilla override on rpms/cxf-xjc-utils
lef is maintainer of rpms/deltaspike
lef has a bugzilla override on rpms/deltaspike
lef is watching rpms/derby
lef has a bugzilla override on rpms/derby
lef is watching rpms/disruptor
lef is maintainer of rpms/easymock3
lef has a bugzilla override on rpms/easymock3
lef is maintainer of rpms/eclipse
lef is maintainer of rpms/eclipse-filesystem
lef has a bugzilla override on rpms/eclipse-filesystem
lef is maintainer of rpms/eclipselink
lef has a bugzilla override on rpms/eclipselink
lef is maintainer of 

Re: Action Required: Bugzilla - API Authentication changes

[Pierre-Yves Chibon]

On Tue, Feb 01, 2022 at 01:41:01PM +0100, Miro Hrončok wrote:
> On 01. 02. 22 13:37, Fabio Valentini wrote:
> > Hi Miro,
> > 
> > Thanks for forwarding this announcement.
> > Apparently the talk about "improving communication between RHBZ and
> > the Fedora Project" has not born fruit yet. ;)
> 
> Well the announcement was public, I recommend subscribing to
> https://listman.redhat.com/mailman/listinfo/bugzilla-announce-list if you
> interact with bugzilla a lot.
> 
> > Do we know if any of our tools and scripts that interact with RHBZ
> > will get broken by this?
> > I assume you have an eye on at least some of the releng scripts (FTI,
> > FTBFS, etc.).
> 
> I will check. I think it's all broken.
> 
> > But what about fedora-review? fedora-create-review? The tool that
> > syncs assignees from dist-git to RHBZ?
> 
> No idea.

Most of these tools are written in python and as the email says, the most recent
version of python-bugzilla works fine (which is already in Fedora and EPEL -
stable).

So as long as your systems are up to date, it should be somewhat transparent.


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive packagers: anoopcs, gtiwari, msehnout, sebix, vanessa_kris

[Pierre-Yves Chibon]

On Fri, Jan 21, 2022 at 02:31:57PM +0530, Anoop C S wrote:
> On Thu, 2022-01-20 at 09:57 +0100, Pierre-Yves Chibon wrote:
> > Good Morning Everyone,
> > 
> > The packagers listed here have been receiving a daily email asking
> > them to
> > either adjust their bugzilla or their FAS account so the email
> > address in FAS
> > matches an existing bugzilla account.
> > 
> > Having a bugzilla account is mandatory per:
> > https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account
> > 
> > - anoopcs contacted since November 27th
> > 
> > anoopcs is maintainer of rpms/glusterfs
> > anoopcs is main admin of rpms/glusterfs-coreutils
> > anoopcs has a bugzilla override on rpms/glusterfs-coreutils
> > anoopcs is maintainer of rpms/richacl
> > anoopcs is maintainer of rpms/samba
> > anoopcs is watching rpms/socket_wrapper
> 
> I am aware and was ignoring it based on the reply I got for the ticket
> raised[1] on the exact same issue. I also wanted to know where the
> ongoing work for making use of bugzilla field in FAS(I made another
> comment after ticket got closed) is being tracked. May be issue
> #9863[2]?

That's a question I do not have the answer to.

> Very recent request(via email) for bugzilla email validation gave me an
> impression that its finally gonna happen.

It is being worked on but it is not ready yet (I expect that it will be
announced once it is).

> If not, how important it is to match both(FAS and bugzilla) email
> addresses at this point? Or is it a requirement now to have same email
> address to get the work completed? Sorry, I am little confused.

It is important as it breaks the sync from dist-git to bugzilla and for the
entire component (package), so it impacts you as well as potentially any other
co-maintainers or watchers of the packages you are linked to.

Currently there are two ways to get this sync working:
- either have a valid bugzilla account corresponding to your main FAS email
- add an override to manually map your main FAS email to your bugzilla account
  in:
  
https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openshift-apps/toddlers/templates/email_overrides.toml


Hoping this helps,
Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive packagers: anoopcs, gtiwari, msehnout, sebix, vanessa_kris

[Pierre-Yves Chibon]

On Thu, Jan 20, 2022 at 10:04:25AM +, Ankur Sinha wrote:
> Hello,
> 
> > - vanessa_kris contacted since December 10th
> > 
> > vanessa_kris is main admin of rpms/python-git-changelog
> > vanessa_kris has a bugzilla override on rpms/python-git-changelog
> > vanessa_kris is main admin of rpms/python-glymur
> > vanessa_kris has a bugzilla override on rpms/python-glymur
> 
> Vanessa had to create a new user because the `_` doesn't work for
> fedorapeople.org:
> 
> https://pagure.io/fedora-infrastructure/issue/10377#comment-767776
> 
> So, they've now created vanessakris (without the `_`) and we've given
> the new account admin access on all these packages, and disabled the
> older account.
> 
> I guess we should've used the older account to orphan these first? I can
> ask Vanessa to do that now.

Looks to be fixed this morning, many thanks for handling this :)


Pierre


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Non-responsive packagers: anoopcs, gtiwari, msehnout, sebix, vanessa_kris

[Pierre-Yves Chibon]

Good Morning Everyone,

The packagers listed here have been receiving a daily email asking them to
either adjust their bugzilla or their FAS account so the email address in FAS
matches an existing bugzilla account.

Having a bugzilla account is mandatory per:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account

- anoopcs contacted since November 27th

anoopcs is maintainer of rpms/glusterfs
anoopcs is main admin of rpms/glusterfs-coreutils
anoopcs has a bugzilla override on rpms/glusterfs-coreutils
anoopcs is maintainer of rpms/richacl
anoopcs is maintainer of rpms/samba
anoopcs is watching rpms/socket_wrapper

- gtiwari contacted since January 14th

gtiwari is main admin of rpms/bluez
gtiwari has a bugzilla override on rpms/bluez

- msehnout contacted since December 15th

msehnout is watching rpms/bind
msehnout is watching rpms/bind99
msehnout is maintainer of rpms/ipcalc
msehnout is watching rpms/libpcap
msehnout is maintainer of rpms/osbuild
msehnout is maintainer of rpms/osbuild-composer
msehnout is watching rpms/pure-ftpd
msehnout is watching rpms/tcpdump
msehnout is watching rpms/vsftpd
msehnout is watching rpms/wireshark

- sebix contacted since December 4th

sebix is maintainer of rpms/lockfile-progs
sebix has a bugzilla override on rpms/lockfile-progs
sebix is maintainer of rpms/logcheck
sebix has a bugzilla override on rpms/logcheck

- vanessa_kris contacted since December 10th

vanessa_kris is main admin of rpms/python-git-changelog
vanessa_kris has a bugzilla override on rpms/python-git-changelog
vanessa_kris is main admin of rpms/python-glymur
vanessa_kris has a bugzilla override on rpms/python-glymur


Does anyone know how to contact them?


Thanks,

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Workflow and other problems with the Fedora container infrastructure

[Pierre-Yves Chibon]

On Sun, Jan 16, 2022 at 08:42:30AM -0500, Josh Boyer wrote:
>On Sat, Jan 15, 2022, 6:57 PM Kevin Fenzi <[1]ke...@scrye.com> wrote:
> 
>  On Thu, Jan 13, 2022 at 02:14:19PM -0500, Neal Gompa wrote:
>  >
>  > One of the things that has recently happened in the Koji space is the
>  > addition of a kiwi-build task to build images using the KIWI tool[1].
>  >
>  > KIWI supports building all kinds of operating system images, including
>  > OCI containers. The Fedora Cloud WG is poking at the idea of using
>  > KIWI for the cloud image to replace the unmaintained and brittle
>  > ImageFactory, and we could also look at doing container builds with
>  > KIWI to replace the OpenShift Atomic Reactor system. That would
>  > drastically simplify the architecture and make container image builds
>  > considerably more reasonable for the Container SIG and any other
>  > stakeholders.
> 
>  Yeah, thats quite interesting. I would be happy to move to a pipeline
>  thats less fragile here. :)
> 
>  There's also talk about moving things to use ImageBuilder, but I don't
>  think it does containers.
> 
>We can, and should, have RFEs for Image Builder to do containers.  I know
>we need this internally as well.  It may farm that out to buildah in the
>background or something, but that remains to be determined.
>In the interest of commonality across the Fedora/CentOS/RHEL ecosystem, I
>really think using Image Builder as the tool to build images is the best
>approach.

The underlying tool, osbuild, can already build container. They can be made
available as tarball which one can just `podman import` afterward :)


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Sysadmin - main group

[Pierre-Yves Chibon]

On Mon, Nov 29, 2021 at 12:36:15PM +, Mark O'Brien wrote:
> I'm happy to announce that We have added a new member to the
> sysadmin-main group:
> 
> Saffronique - David Kirwan
> 
> This is the core group of trusted folks that have high level access to
> almost everything in fedora infrastructure.
> 
> David has been working on Fedora infra for about a year now and
> has been involved in some fairly big pieces of work including adding
> an aarch64 cluster to osbs as well as bringing up the new ocp4
> cluster in Fedora.
> 
> He has proved trustworthiness, and ability and I'd like to be the first
> to wish him congratulations


Congratulations David!

We'll let you the secret hand check later on ;-)


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: sourcegraph and src.fedoraproject.org

[Pierre-Yves Chibon]

On Wed, Nov 24, 2021 at 07:10:31PM -0500, Matthew Miller wrote:
> Sourcegraph is planning to, very shortly, start cloning all non fork repos
> from src.fedoraproject.org as well as asking the Pagure API for the metadata
> of those repos. Their user agent for API requests is `Sourcegraph-Bot` and
> for git protocol stuff `git/Sourcegraph-Bot`.
> 
> If there's a problem, let me know and I'll let them know. :)

Maybe they could pre-seed their script with:
https://src.fedoraproject.org/lookaside/git-seed-latest.tar.xz
That way instead of pulling all the data for all the git repos, they will just
pull the changes since the last run of the cron (which runs daily).


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: [FBR] Update pagure to 5.13.3

[Pierre-Yves Chibon]

On Mon, Nov 01, 2021 at 11:07:26AM -0400, Neal Gompa wrote:
> On Mon, Nov 1, 2021 at 11:06 AM Pierre-Yves Chibon  
> wrote:
> >
> > Good Morning Everyone,
> >
> > This morning, I have cut a new release of pagure: 5.13.3 with the following
> > changelog:
> > - Warn users when a PR contains some characters
> > - srcfpo theme: Change "Packages" link to new packages website (Brendan 
> > Early)
> > - srcfpo theme: left-align the lines in description (Zbigniew 
> > Jędrzejewski-Szmek)
> > - fas user url updated for new accounts system (Mark O Brien)
> > - Change fas link from admin.fp.o to accounts.fp.o (Lenka Segura)
> > - Remove message about 60 day key length (Ken Dreyer)
> > - Escape $ to fix Jenkins interpolation warning (#5178) (Anatoli Babenia)
> > - Fix another invalid  width/height attribute (Anatoli Babenia)
> > - Fix missing space before src in 

[FBR] Update pagure to 5.13.3

[Pierre-Yves Chibon]

Good Morning Everyone,

This morning, I have cut a new release of pagure: 5.13.3 with the following
changelog:
- Warn users when a PR contains some characters
- srcfpo theme: Change "Packages" link to new packages website (Brendan Early)
- srcfpo theme: left-align the lines in description (Zbigniew 
Jędrzejewski-Szmek)
- fas user url updated for new accounts system (Mark O Brien)
- Change fas link from admin.fp.o to accounts.fp.o (Lenka Segura)
- Remove message about 60 day key length (Ken Dreyer)
- Escape $ to fix Jenkins interpolation warning (#5178) (Anatoli Babenia)
- Fix another invalid  width/height attribute (Anatoli Babenia)
- Fix missing space before src in 

Non-responsive packager: kasong

[Pierre-Yves Chibon]

Good Morning Everyone,

The packager listed here has been receiving a daily email asking them to
either adjust their bugzilla or their FAS account so the email address in FAS
matches an existing bugzilla account.

Having a bugzilla account is mandatory per:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account


kasong has received daily emails since September 28th.

kasong is main admin of rpms/kdump-anaconda-addon
kasong has a bugzilla override on rpms/kdump-anaconda-addon
kasong is maintainer of rpms/kexec-tools
kasong is main admin of rpms/memstrack
kasong has a bugzilla override on rpms/memstrack
kasong is watching rpms/systemd


Does anyone know how to contact them?


Thanks,

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Using YubiKey for accounts.fedoraproject.org OTP?

[Pierre-Yves Chibon]

On Mon, Sep 27, 2021 at 03:27:43PM +0200, Miro Hrončok wrote:
> Hello,
> 
> I've been trying to add the OPT token from accounts.fedoraproject.org to my
> yubikey. I get a QR code and a otpauth://totp/username?secret=xxx URI.
> 
> I copypasted the xxx secret (56 characters: digits and uppercase letters)
> and tried to add it via YubiKey Manager GUI via Applications/OTP as
> OATH-HOTP (6 digits).
> 
> I get "Failed to configure Long Touch (Slot 2). undefined" error.
> 
> When I tried to use the CLI:
> 
> $ ykman otp hotp -d 6 -c 0 2 xxx
> 
> I get "Error: key lengths >20 bytes not supported".
> 
> Is there a way to use YubiKey for accounts.fedoraproject.org OTP, or is the
> device not compatible?

You may want to check: https://github.com/fedora-infra/noggin/issues/202


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora  Java: The Death of Two SIGs

[Pierre-Yves Chibon]

On Mon, Sep 27, 2021 at 10:57:12AM +0200, Peter Boy wrote:
> 
> 
> > Am 27.09.2021 um 10:47 schrieb Ankur Sinha :
> > 
> > On Sun, Sep 26, 2021 21:20:07 +0200, Fabio Valentini wrote:
> >> Should the @java-maint-sig group be removed from any packages it is
> >> still associated with? Should it be dissolved, and members be removed?
> >> Should the remaining ruins that used to be packages be orphaned?
> >> Retired? Buried? Forgotten?
> >> 
> >> I don't know.
> > 
> > 
> > Unfortunately, I think removing the java-maint-sig is the only thing to
> > do.

As heart-breaking as it is, I agree with Ankur. Letting things as they are is
not correct.
The group itself will not disappear, so if some people wanted to revive it some
time in the future, they could still do, but it would not give the impression
that someone/some team is looking after packages while they are not.

> What do you want to gain from it? What is the goal to be? 

I believe the original email from Fabio answers both of these questions.


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: FBR: run batcave playbook for rbac

[Pierre-Yves Chibon]

On Tue, Sep 21, 2021 at 03:08:12PM +0100, Mark O'Brien wrote:
> Hi All,
> 
> I am requesting permissions to run the batcave
> playbook to update rbac permissions to allow the
> sysadmin-analysis group run the logserver playbook
> as requested in this ticket:
> 
> https://pagure.io/fedora-infrastructure/issue/10231
> 
> As always comments/+1's welcome

+1 for me

Pierre


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: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Non-responsive packager: michelmno

[Pierre-Yves Chibon]

Good Morning Everyone,

The packager listed here has been receiving a daily email asking them to
either adjust their bugzilla or their FAS account so the email address in FAS
matches an existing bugzilla account.

Having a bugzilla account is mandatory per:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account

- michelmno contacted since July 13th

michelmno is main admin of rpms/libcxl
michelmno is main admin of rpms/libocxl
michelmno is maintainer of rpms/ocaml-camlp5
michelmno is watching rpms/opal-prd


Does anyone know how to contact them?


Thanks,

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: How to get list of retired packages?

[Pierre-Yves Chibon]

On Thu, Sep 16, 2021 at 02:36:58PM +0200, Miroslav Suchý wrote:
> Hi.
> 
> What is the best way to get list of retired packages in F35? I can get list
> of all retired packages by scanning dist-git. But if I want it for one
> release of Fedora? And I do not want to do that manually; I rather want to
> script it.
> 
PDC would be your source of truth for this info. You'll need to look at the
"active" state of the package/branch.


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Freeze Break Request: Blockerbugs Hotfix to Deal With RHBZ Change

[Pierre-Yves Chibon]

On Wed, Sep 15, 2021 at 01:12:07PM -, Kamil Páral wrote:
> > For now, I've kept the limit to 20 because I was having trouble getting 
> > more than 20
> > to work for me.
> 
> For anyone interested - we found out that only logged-in users can receive 
> more than 20 responses per query. For anonymous queries, the max limit is 20. 
> I had a bugzilla token configured, that's why I had no troubles raising the 
> limit to 100, while it didn't work for Tim because he didn't have any token.

Fun one!

Thanks for the info,

Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Freeze Break Request: Blockerbugs Hotfix to Deal With RHBZ Change

[Pierre-Yves Chibon]

On Mon, Sep 13, 2021 at 12:49:21PM -0600, Tim Flink wrote:
> It turns out that the configuration for rhbz was changed without an 
> announcement and now the max number of bugs returned for any query is 20. 
> Some of the queries that we use in blockerbugs return more than 20 bugs so I 
> have a hotfix to deal with the new pagination requirements. I've attached the 
> patch to this email.
> 
> I'd like to apply this patch to production. Unfortunately, we're in the 
> middle of a non-trivial rewrite that's currently on stg so testing the patch 
> isn't really an option and that code isn't ready for production use right now.
> 
> Thanks,
> 
> Tim

> diff --git a/blockerbugs/util/bz_interface.py 
> b/blockerbugs/util/bz_interface.py
> index 471140f..a9f90d7 100644
> --- a/blockerbugs/util/bz_interface.py
> +++ b/blockerbugs/util/bz_interface.py
> @@ -29,11 +29,14 @@ from xmlrpc.client import Fault
>  
>  from blockerbugs import app
>  
> +# rhbz has been updated to have a max of 20 results returned
> +BUGZILLA_QUERY_LIMIT = 20

If I understood correctly, you can request more than 20 results, but if you
don't specify how many you want, you'll only get 20.
I believe if you set it to 0 you may get everything, but this needs to be
confirmed empirically.

Anyway, I would check first if you can't retrieve 100 or 200 results in one go
instead of doing iterations of 20 ;-)

>  base_query = {'o1': 'anywords',
>'f1': 'blocked',
>'query_format': 'advanced',
> -  'extra_fields': ['flags']}
> -
> +  'extra_fields': ['flags'],
> +  'limit': BUGZILLA_QUERY_LIMIT}
>  
>  class BZInterfaceError(Exception):
>  """A custom wrapper for XMLRPC errors from Bugzilla"""
> @@ -77,7 +80,8 @@ class BlockerBugs():
>  # 
> https://bugzilla.stage.redhat.com/buglist.cgi?bug_status=NEW_status=ASSIGNED
>  # 
> _status=POST_status=MODIFIED=Fedora=anaconda=component
>  # 
> =changedafter=Fedora_format=advanced=2013-03-21%2012%3A25=19
> -def get_bz_query(self, tracker: int, last_update: datetime.datetime = 
> None) -> dict[str, Any]:
> +def get_bz_query(self, tracker: int, last_update: datetime.datetime = 
> None, offset: int = 0
> + ) -> dict[str, Any]:

If you can set the limit to 0 to retrieve everything, you may want to default to
None rather than 0.

>  """Build a Bugzilla query to retrieve all necessary info about all 
> bugs which block the
>  `tracker` bug.
>  
> @@ -129,6 +133,9 @@ class BlockerBugs():
>  'f10': 'CP'
>  })
>  
> +if offset > 0:

And if you default to None, this will need to be tweaked.

> +query.update({'offset': offset})
> +
>  return query
>  
>  def query_tracker(self, tracker: int, last_update: 
> Optional[datetime.datetime] = None
> @@ -139,8 +146,21 @@ class BlockerBugs():
>  :param last_update: If provided, the query is modified to ask only 
> about bugs which have
>  recent modifications; otherwise asks about all 
> bugs.
>  """
> -query = self.get_bz_query(tracker, last_update)
> -buglist = self.bz.query(query)
> +
> +buglist = []
> +last_query_len = BUGZILLA_QUERY_LIMIT
> +
> +
> +# this is a hotfix hack to work around the sudden config change in 
> rhbz where the max
> +# number of bugs returned for a query is 20
> +# it seems to be working for now but may need more work going forward
> +while last_query_len == BUGZILLA_QUERY_LIMIT:
> +
> +new_query = self.get_bz_query(tracker, last_update, 
> offset=len(buglist))
> +new_buglist = self.bz.query(new_query)
> +buglist.extend(new_buglist)
> +last_query_len = len(new_buglist)
> +

Looks alright to me otherwise.


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Freeze Break Request: more ipsilon/sssd debugging

[Pierre-Yves Chibon]

On Mon, Sep 13, 2021 at 01:44:45PM -0400, Stephen John Smoogen wrote:
> On Mon, 13 Sept 2021 at 13:34, Kevin Fenzi  wrote:
> >
> > So, it turns out the additional debugging we setup in that sssd package
> > on the ipsilon servers isn't sufficent to show what the problem is. ;(
> >
> > sssd developers would like us to crank up debugging to try and get logs
> > of whats happening. Unfortunately, this will use a ton of disk space,
> > which these vm's do not have much of. ;(
> >
> > I was going to ask to grow the disk on ipsilon02, but I think perhaps
> > cleaner would be to create a NFS volume and mount it on /var/log/sssd/
> > on ipsilon02. This way we don't need to actually take the machine down
> > and it's really easy to back out.
> >
> 
> Yeah either do an NFS or a seperate vmdisk to mount as that and then
> blow away when done.
> 
> > So, can I get +1s to:
> >
> > * make a NFS volume and mount it on /var/log/sssd on ipsilon02
> > * adjust ipsilon02's sssd to enable crazy levels of debug.
> > * restart sssd and wait for the next failure.
> > * profit!
> >
> 
> I would try this and if NFS fails then go with a seperate disk for this.

+1 on either.


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Freeze Break Request: OSBS docker

[Pierre-Yves Chibon]

On Tue, Sep 07, 2021 at 03:06:45PM -0700, Kevin Fenzi wrote:
> Some of you may be aware of: 
> https://pagure.io/fedora-infrastructure/issue/10145
> 
> TLDR: some new syscalls in f35+ make docker in our OSBS cluster fail
> some new syscalls. This means we have had no new f35/rawhide based OSBS
> containers built. 
> 
> Note that the base and minimal base are built a different way in
> rawhide/branched composes, so we have those, we just don't have any OSBS
> builds. Also it's not affecting flatpak's (yet) because those are built
> against f34 currently. 
> 
> Internally, Red Hat has a docker package that disables seccomp for
> docker build. Docker has no option for this without patching. 
> OpenShift 3.11 (and also thus OSBS) default to seccomp off, but they
> can't do that at build time currently. 
> 
> So, I would like to: 
> 
> * Make sure it's ok for us to use that internal docker build.
> (If it's not I guess we get to hack up that seccomp disable patch
> ourselves). 
> * Apply it on our OSBS nodes. 
> 
> Our aarch64 nodes are fedora 33, and I don't think they are affected by
> this, but I am not sure (if someone seeing this could make sure one way
> or another that would be great, I will also ask in the bug). 
> 
> Anyhow, can I get +1's to update docker and adjust it's startup unit to
> run builds with no seccomp to work around this issue?

+1 for me


P.Yves


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: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: FAS email for authentication

[Pierre-Yves Chibon]

On Fri, Jul 09, 2021 at 11:13:19AM -0400, Christopher wrote:
> Why does FAS use the email forwarding address when I use it to
> authenticate, rather than the permanent @fedoraproject.org alias for
> the address?
> 
> I should be able to change my forwarding address without changing how
> authentication works. However, it looks like if I change my forwarding
> address, then try to use FAS to log in to Bugzilla, it would tell me
> that there is no account for  and asks if I want
> to register. This currently happens when I try to log in with FAS,
> because I registered my bugzilla account using my
> ctubb...@fedoraproject.org alias instead. Obviously, I don't want to
> create a new account if I change my forwarding address. I can't
> imagine ever wanting to authenticate using my forwarding address,
> rather than my Fedora alias for accessing Fedora systems, because my
> forwarding address is subject to change.
> 
> Every FAS account has a corresponding @fedoraproject.org email alias.

There is the invalid assumption :)
You need to be in one group and have signed the FPCA to have the alias.
You can see have a FAS account and do contribution (for examples to projects
hosted on pagure.io) without either of these requirements.



Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Bochecha unavailable for a little while

[Pierre-Yves Chibon]

Good Morning Everyone,

I am in contact with bochecha who has asked me that I announce his
un-availability for personal reason for a little while.
To this end, he has orphaned the package "buildstream" on Wednesday. There may
be more coming.

Bochecha still wants to come back to Fedora once things have settled down but he
didn't want for anything to wait on him while he is not available.


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: IRC nicks in account system, FMN and matrix

[Pierre-Yves Chibon]

On Thu, Jun 24, 2021 at 02:32:05PM +0200, Michal Konecny wrote:
> 
> 
> On 24. 06. 21 11:51, Aurelien Bompard wrote:
> > 
> > > * Do we want to get noggin to be able to verify nicks first?
> > How will the verification works?
> > 
> > 
> > We don't know yet.  I was thinking of having and IRC bot that would get
> > an HTTP request from Noggin to verify a user, and would send a link with
> > a JWT token as a private message that the user would click on, pretty
> > much like what we do for email (except it requires an IRC bot). Of
> > course, if we want to support Matrix, we'll need a Matrix bot too to
> > verify the nicknames as well.
> > That's a pretty decent chunk of work and I don't think it can be done by
> > next week. Hopefully sometime in the north hemispherian summer. So if we
> > make it a requirement it's going to delay things quite a bit.

> I thought we will just validate that the username exists. If we want to
> validate it's really the user it will be more difficult.

It's basically what FMN does and it works the way Aurélien has described it. I
wonder if we could re-use parts of the code there? Or maybe even share the IRC
bot?


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: rpmautospec: Invitiation to Test

[Pierre-Yves Chibon]

On Tue, Jun 08, 2021 at 02:00:00PM +0200, Nils Philippsen wrote:
> Hey everybody,
> 
> we've recently deployed the changes needed to enable automatic RPM
> release numbers and changelogs to Koji in staging, and now we want you
> to throw things at it!
> 
> Detailed information is below, but the gist is: it looks like this will
> be real sometime soon. This is the time to ensure we folks working on
> it over the past weeks haven't left in any glaring errors.
> 
> We look forward to hearing from you!

I haven't taken the time to test this yet, but I just wanted to send a: thank
you for working on this.

I very much look forward seeing it :)


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: why some package are retired and others are retired without be orphan ?

[Pierre-Yves Chibon]

On Thu, Apr 22, 2021 at 01:53:47PM +0200, Pierre-Yves Chibon wrote:
> On Thu, Apr 22, 2021 at 11:11:37AM +0100, Sérgio Basto wrote:
> > Hi, 
> > 
> > while https://src.fedoraproject.org/rpms/projectM-jack is retired ,
> > 
> > https://src.fedoraproject.org/rpms/publican-fedora and https://src.fedo
> > raproject.org/rpms/gdesklets have the button orphan , why ? 
> 
> Because they still have a main admin?
> If that main admin was "orphan", you would not see that button.
> 
> And in the case of these two packages:
> - publican-fedora has not been orphaned nor retired
> https://src.fedoraproject.org/rpms/publican-fedora/
> https://pdc.fedoraproject.org/rest_api/v1/component-branches/?global_component=publican-fedora=rpm=rawhide
> 
> - gdesklets has not been orphaned but seems to have been retired
> https://src.fedoraproject.org/rpms/gdesklets/
> https://pdc.fedoraproject.org/rest_api/v1/component-branches/?global_component=gdesklets=rpm=rawhide
> 
> 
> > Or better , when the package is retired by some rules like FTBFS or
> > RetirePython2 , the package should be also orphaned . To allow other
> > packager adopt it (IMO). 
> 
> We have a cron that runs monthly and orphans all packages that have been
> retired. 
> Looking at its last run, it should have processed gdesklets:
> > - Orphaning rpms/gdesklets from sergiomb
> > - Removing access on rpms/gdesklets to sergiomb
> 
> I'll try to debug why it did not.

Found it, gdesklet has been orphaned :)


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: why some package are retired and others are retired without be orphan ?

[Pierre-Yves Chibon]

On Thu, Apr 22, 2021 at 11:11:37AM +0100, Sérgio Basto wrote:
> Hi, 
> 
> while https://src.fedoraproject.org/rpms/projectM-jack is retired ,
> 
> https://src.fedoraproject.org/rpms/publican-fedora and https://src.fedo
> raproject.org/rpms/gdesklets have the button orphan , why ? 

Because they still have a main admin?
If that main admin was "orphan", you would not see that button.

And in the case of these two packages:
- publican-fedora has not been orphaned nor retired
https://src.fedoraproject.org/rpms/publican-fedora/
https://pdc.fedoraproject.org/rest_api/v1/component-branches/?global_component=publican-fedora=rpm=rawhide

- gdesklets has not been orphaned but seems to have been retired
https://src.fedoraproject.org/rpms/gdesklets/
https://pdc.fedoraproject.org/rest_api/v1/component-branches/?global_component=gdesklets=rpm=rawhide


> Or better , when the package is retired by some rules like FTBFS or
> RetirePython2 , the package should be also orphaned . To allow other
> packager adopt it (IMO). 

We have a cron that runs monthly and orphans all packages that have been
retired. 
Looking at its last run, it should have processed gdesklets:
> - Orphaning rpms/gdesklets from sergiomb
> - Removing access on rpms/gdesklets to sergiomb

I'll try to debug why it did not.


Thanks,
Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Inactive packagers to be removed from their packages

[Pierre-Yves Chibon]

On Fri, Apr 16, 2021 at 03:25:01PM +0200, Pierre-Yves Chibon wrote:
> Good Morning Everyone,
> 
> When we rolled out the new AAA solution a few weeks ago, some accounts have 
> not
> been migrated:
> - Accounts that have been set inactive by their owner
> - Accounts that are disabled
> - Accounts marked as spam
> 
> This resulted in some packager accounts not being migrated.
> As a consequence, since then, the script that syncs the default-assignee and 
> CC
> list for each component from dist-git to bugzilla has been notifying us about 
> a
> list of packagers in dist-git that could not be synced to bugzilla due to a 
> lack
> of bugzilla account (or rather, in this case, the lack of Fedora account). 
> Since
> these accounts do not exist in the new FAS, I will be removing them from their
> packages on dist-git.
> 
> Here is the list of account impacted:
> - amukunda
> - brolley
> - dp67
> - ianweller
> - jensm
> - jima
> - jjmcd
> - juanmabc
> - kmatsui
> - kurtseifried
> - marcusk
> - rnorwood
> - sindrepb
> - splinux
> - vvitek
> 
> I am planning on removing these users on April 20th. If anyone is opposed to
> this, please let me know.

The only feedback I've had about this email were positive (as in, it should be
done). So I'm going to proceed.


Thanks,
Pierre


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive maintainer: nando pavlix

[Pierre-Yves Chibon]

On Mon, Apr 19, 2021 at 11:51:35AM +0200, Miro Hrončok wrote:
> On 19. 04. 21 10:52, Pierre-Yves Chibon wrote:
> > On Fri, Apr 16, 2021 at 03:12:34PM +0200, Pierre-Yves Chibon wrote:
> > > Good Morning Everyone,
> > > 
> > > The packagers listed here have been receiving a daily email asking them to
> > > either adjust their bugzilla or their FAS account so the email address in 
> > > FAS
> > > matches an existing bugzilla account.
> > > 
> > > Having a bugzilla account is mandatory per:
> > > https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account
> > > 
> > > - nando contacted since March 26th
> > > - pavlix contacted since March 18th
> > 
> > Thanks to zoglesby and liangwen12year for fixing their accounts.
> > 
> > Does anyone know how to contact nando and pavlix?
> 
> I know how to contact pavlix.

That seems to have worked, thanks!

The only person left is nando.


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: account system group deletions

[Pierre-Yves Chibon]

On Mon, Apr 19, 2021 at 11:29:41AM -0700, Kevin Fenzi wrote:
> Greetings. 
> 
> I thought I would bring up for dicussion here something thats come up
> after the new account system has been put in place. 
> 
> Namely, how do we handle group deletions. 
> In the FAS2 world, we never deleted anything. I think this was partly
> due to an over abundence of caution (there could be files owned by the
> group left over on various machines) and partly just because it was
> easier. 
> 
> We now have 5 requests to remove various no longer used groups.
> 
> I've enabled audit logging on our ipa01 instance, so we have audit logs
> (and I intend to back them up and keep them forever). So we can tell
> when a group was deleted by whom. We also have a db dump from fas2
> before the switchover where we can look at who was in what group or what
> created it. 
> 
> So, I would like to propose: 
> 
> * we will remove groups on request/ticket from a group manager. 
> * we will not seek out groups to remove, as them being there doesn't
> really hurt anything.
> 
> Thoughts?

+1 for me on groups.

This does raise the question about user accounts no?
We could have a group that is created with the same name as a group that was
deleted, and suddenly our auditing trail needs to take into account a time
component as group X at time A may be different than group X at time B.

I've the feeling that user accounts are a tad more sensitive and thus we may
want to keep our current policies, I'm raising the question here nonetheless :)


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Disabling BZ `fedora_requires_release_note` flag

[Pierre-Yves Chibon]

On Mon, Apr 19, 2021 at 09:11:19AM -0400, Ben Cotton wrote:
> On Sun, Apr 18, 2021 at 4:13 PM Zbigniew Jędrzejewski-Szmek
>  wrote:
> >
> > What about the unused "qa contact field"? Kevin suggested dropping
> > qa-extras [1], but it never went anywhere, afaics?
> >
> Good idea. I have a few other BZ cleanup things I want to look at
> post-release. I'll add this to the list.

This one may have been done already actually, worth double checking though.


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive maintainer: nando pavlix

[Pierre-Yves Chibon]

On Fri, Apr 16, 2021 at 03:12:34PM +0200, Pierre-Yves Chibon wrote:
> Good Morning Everyone,
> 
> The packagers listed here have been receiving a daily email asking them to
> either adjust their bugzilla or their FAS account so the email address in FAS
> matches an existing bugzilla account.
> 
> Having a bugzilla account is mandatory per:
> https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account
> 
> - nando contacted since March 26th
> - pavlix contacted since March 18th

Thanks to zoglesby and liangwen12year for fixing their accounts.

Does anyone know how to contact nando and pavlix?


Pierre
 
> nando is maintainer of rpms/clthreads
> nando is maintainer of rpms/hydrogen
> nando is maintainer of rpms/jamin
> nando is watching rpms/jconv
> nando is maintainer of rpms/jconvolver
> nando is maintainer of rpms/ladspa-amb-plugins
> nando is maintainer of rpms/ladspa-blop-plugins
> nando is maintainer of rpms/ladspa-caps-plugins
> nando is maintainer of rpms/ladspa-cmt-plugins
> nando is maintainer of rpms/ladspa-fil-plugins
> nando is maintainer of rpms/ladspa-mcp-plugins
> nando is maintainer of rpms/ladspa-rev-plugins
> nando is maintainer of rpms/ladspa-tap-plugins
> nando is maintainer of rpms/ladspa-vco-plugins
> nando is maintainer of rpms/muse
> nando is maintainer of rpms/qjackctl
> nando is maintainer of rpms/qsynth
> nando is watching rpms/rtaudio
> nando is main admin of rpms/sooperlooper
> nando has a bugzilla override on rpms/sooperlooper
> nando is maintainer of rpms/swami
> nando is maintainer of rpms/zita-convolver
> 
> pavlix is watching rpms/NetworkManager-iodine
> pavlix is watching rpms/NetworkManager-l2tp
> pavlix is watching rpms/NetworkManager-openconnect
> pavlix is watching rpms/NetworkManager-openvpn
> pavlix is watching rpms/NetworkManager-pptp
> pavlix is maintainer of rpms/NetworkManager-ssh
> pavlix is maintainer of rpms/NetworkManager-strongswan
> pavlix is watching rpms/NetworkManager-vpnc
> pavlix is watching rpms/bind10
> pavlix is maintainer of rpms/dhcpcd
> pavlix is maintainer of rpms/dnsmasq
> pavlix is maintainer of rpms/dnssec-trigger
> pavlix is maintainer of rpms/getdns
> pavlix is maintainer of rpms/hostname
> pavlix is maintainer of rpms/iproute
> pavlix is maintainer of rpms/libecap
> pavlix is maintainer of rpms/python-ptrace
> pavlix is maintainer of rpms/python-pyroute2
> pavlix is maintainer of rpms/radvd
> pavlix is maintainer of rpms/rdist
> pavlix is maintainer of rpms/rsync
> pavlix is maintainer of rpms/squid
> pavlix is maintainer of rpms/strongswan
> pavlix is maintainer of rpms/unbound
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive maintainer: liangwen12year nando pavlix zoglesby

[Pierre-Yves Chibon]

On Fri, Apr 16, 2021 at 01:41:41PM -, Zach Oglesby wrote:
> > On Fri, Apr 16, 2021 at 9:19 AM Pierre-Yves Chibon 
> >  > Huh. That still exists? What a throwback!
> > 
> > I sent a tweet in zoglesby's direction. He posted about a week ago, so
> > hopefully he'll see it.
> Fixed

Thanks!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Inactive packagers to be removed from their packages

[Pierre-Yves Chibon]

Good Morning Everyone,

When we rolled out the new AAA solution a few weeks ago, some accounts have not
been migrated:
- Accounts that have been set inactive by their owner
- Accounts that are disabled
- Accounts marked as spam

This resulted in some packager accounts not being migrated.
As a consequence, since then, the script that syncs the default-assignee and CC
list for each component from dist-git to bugzilla has been notifying us about a
list of packagers in dist-git that could not be synced to bugzilla due to a lack
of bugzilla account (or rather, in this case, the lack of Fedora account). Since
these accounts do not exist in the new FAS, I will be removing them from their
packages on dist-git.

Here is the list of account impacted:
- amukunda
- brolley
- dp67
- ianweller
- jensm
- jima
- jjmcd
- juanmabc
- kmatsui
- kurtseifried
- marcusk
- rnorwood
- sindrepb
- splinux
- vvitek

I am planning on removing these users on April 20th. If anyone is opposed to
this, please let me know.


At the bottom of this email is the list of component affected for each of these
users.

Thanks,
Pierre


---
amukunda is maintainer of rpms/java-atk-wrapper

brolley is maintainer of rpms/si-units
brolley is watching rpms/systemtap
brolley is maintainer of rpms/uom-lib
brolley is maintainer of rpms/uom-parent
brolley is maintainer of rpms/uom-systems

dp67 is watching rpms/HamFax
dp67 is watching rpms/ax25-apps
dp67 is watching rpms/cwirc
dp67 is maintainer of rpms/demorse
dp67 is watching rpms/dxcc
dp67 is watching rpms/gmfsk
dp67 is watching rpms/gpsk31
dp67 is maintainer of rpms/gpsman
dp67 is maintainer of rpms/gridloc
dp67 is maintainer of rpms/linpsk
dp67 is watching rpms/lpsk31
dp67 is watching rpms/xgridloc
dp67 is maintainer of rpms/xpsk31

ianweller is watching rpms/abattis-cantarell-fonts
ianweller is maintainer of rpms/datagrepper
ianweller is watching rpms/ezstream
ianweller is watching rpms/fedora-business-cards
ianweller is watching rpms/gnome-gmail-notifier
ianweller is watching rpms/irclog2html
ianweller is watching rpms/lordsawar
ianweller is watching rpms/mediawiki-CategoryTree
ianweller is watching rpms/mediawiki-HTTP302Found
ianweller is maintainer of rpms/mediawiki-ParserFunctions
ianweller has a bugzilla override on rpms/mediawiki-ParserFunctions
ianweller is main admin of rpms/mediawiki116-Cite
ianweller has a bugzilla override on rpms/mediawiki116-Cite
ianweller is main admin of rpms/mediawiki116-ParserFunctions
ianweller has a bugzilla override on rpms/mediawiki116-ParserFunctions
ianweller is watching rpms/odfpy
ianweller is watching rpms/openarena
ianweller is maintainer of rpms/python-backports-lzma
ianweller is maintainer of rpms/python-backports-ssl_match_hostname
ianweller is maintainer of rpms/python-fedmsg-meta-debian
ianweller is maintainer of rpms/python-fedmsg-meta-fedora-infrastructure
ianweller is watching rpms/python-flask
ianweller is watching rpms/python-flickrapi
ianweller is watching rpms/python-simplemediawiki
ianweller is main admin of rpms/python-sqlite3dbm
ianweller has a bugzilla override on rpms/python-sqlite3dbm
ianweller is watching rpms/python-transitfeed
ianweller is watching rpms/python-werkzeug
ianweller is watching rpms/rsstool
ianweller is main admin of rpms/supybot-fedora
ianweller is watching rpms/techtalk-pse
ianweller is watching rpms/wordpress-plugin-add-to-any
ianweller is watching rpms/wordpress-plugin-add-to-any-subscribe

jensm is watching rpms/callgit
jensm is watching rpms/perl-Ham-Reference-QRZ
jensm is maintainer of rpms/pisg

jima is maintainer of rpms/alpine
jima is watching rpms/alsa-oss
jima is watching rpms/aoetools
jima is watching rpms/banner
jima is watching rpms/bwm-ng
jima is maintainer of rpms/clusterssh
jima is watching rpms/conserver
jima is watching rpms/dnsmasq
jima is watching rpms/graphviz
jima is watching rpms/libdnet
jima is watching rpms/libstatgrab
jima is watching rpms/miau
jima is watching rpms/ngrep
jima is maintainer of rpms/perl-Device-SerialPort
jima is maintainer of rpms/perl-X11-Protocol
jima is watching rpms/prtconf
jima is watching rpms/putty
jima is watching rpms/rblcheck
jima is watching rpms/scanssh
jima is watching rpms/silo
jima is watching rpms/vblade
jima is watching rpms/videodog
jima is watching rpms/xorg-x11-drv-sunbw2
jima is watching rpms/xorg-x11-drv-suncg14
jima is watching rpms/xorg-x11-drv-suncg3
jima is watching rpms/xorg-x11-drv-suncg6
jima is watching rpms/xorg-x11-drv-sunffb
jima is watching rpms/xorg-x11-drv-sunleo
jima is watching rpms/xorg-x11-drv-suntcx

jjmcd is main admin of rpms/R-qcc
jjmcd has a bugzilla override on rpms/R-qcc
jjmcd is main admin of rpms/rcrpanel
jjmcd has a bugzilla override on rpms/rcrpanel

juanmabc is main admin of rpms/mkproject
juanmabc has a bugzilla override on rpms/mkproject
juanmabc is main admin of rpms/rf
juanmabc has a bugzilla override on rpms/rf
juanmabc is main admin of rpms/tw
juanmabc has a bugzilla override on rpms/tw

kmatsui is main 

Inactive packagers to be removed from their packages

[Pierre-Yves Chibon]

Good Morning Everyone,

When we rolled out the new AAA solution a few weeks ago, some accounts have not
been migrated:
- Accounts that have been set inactive by their owner
- Accounts that are disabled
- Accounts marked as spam

This resulted in some packager accounts not being migrated.
As a consequence, since then, the script that syncs the default-assignee and CC
list for each component from dist-git to bugzilla has been notifying us about a
list of packagers in dist-git that could not be synced to bugzilla due to a lack
of bugzilla account (or rather, in this case, the lack of Fedora account). Since
these accounts do not exist in the new FAS, I will be removing them from their
packages on dist-git.

Here is the list of account impacted:
- amukunda
- brolley
- dp67
- ianweller
- jensm
- jima
- jjmcd
- juanmabc
- kmatsui
- kurtseifried
- marcusk
- rnorwood
- sindrepb
- splinux
- vvitek

I am planning on removing these users on April 20th. If anyone is opposed to
this, please let me know.


At the bottom of this email is the list of component affected for each of these
users.

Thanks,
Pierre


---
amukunda is maintainer of rpms/java-atk-wrapper

brolley is maintainer of rpms/si-units
brolley is watching rpms/systemtap
brolley is maintainer of rpms/uom-lib
brolley is maintainer of rpms/uom-parent
brolley is maintainer of rpms/uom-systems

dp67 is watching rpms/HamFax
dp67 is watching rpms/ax25-apps
dp67 is watching rpms/cwirc
dp67 is maintainer of rpms/demorse
dp67 is watching rpms/dxcc
dp67 is watching rpms/gmfsk
dp67 is watching rpms/gpsk31
dp67 is maintainer of rpms/gpsman
dp67 is maintainer of rpms/gridloc
dp67 is maintainer of rpms/linpsk
dp67 is watching rpms/lpsk31
dp67 is watching rpms/xgridloc
dp67 is maintainer of rpms/xpsk31

ianweller is watching rpms/abattis-cantarell-fonts
ianweller is maintainer of rpms/datagrepper
ianweller is watching rpms/ezstream
ianweller is watching rpms/fedora-business-cards
ianweller is watching rpms/gnome-gmail-notifier
ianweller is watching rpms/irclog2html
ianweller is watching rpms/lordsawar
ianweller is watching rpms/mediawiki-CategoryTree
ianweller is watching rpms/mediawiki-HTTP302Found
ianweller is maintainer of rpms/mediawiki-ParserFunctions
ianweller has a bugzilla override on rpms/mediawiki-ParserFunctions
ianweller is main admin of rpms/mediawiki116-Cite
ianweller has a bugzilla override on rpms/mediawiki116-Cite
ianweller is main admin of rpms/mediawiki116-ParserFunctions
ianweller has a bugzilla override on rpms/mediawiki116-ParserFunctions
ianweller is watching rpms/odfpy
ianweller is watching rpms/openarena
ianweller is maintainer of rpms/python-backports-lzma
ianweller is maintainer of rpms/python-backports-ssl_match_hostname
ianweller is maintainer of rpms/python-fedmsg-meta-debian
ianweller is maintainer of rpms/python-fedmsg-meta-fedora-infrastructure
ianweller is watching rpms/python-flask
ianweller is watching rpms/python-flickrapi
ianweller is watching rpms/python-simplemediawiki
ianweller is main admin of rpms/python-sqlite3dbm
ianweller has a bugzilla override on rpms/python-sqlite3dbm
ianweller is watching rpms/python-transitfeed
ianweller is watching rpms/python-werkzeug
ianweller is watching rpms/rsstool
ianweller is main admin of rpms/supybot-fedora
ianweller is watching rpms/techtalk-pse
ianweller is watching rpms/wordpress-plugin-add-to-any
ianweller is watching rpms/wordpress-plugin-add-to-any-subscribe

jensm is watching rpms/callgit
jensm is watching rpms/perl-Ham-Reference-QRZ
jensm is maintainer of rpms/pisg

jima is maintainer of rpms/alpine
jima is watching rpms/alsa-oss
jima is watching rpms/aoetools
jima is watching rpms/banner
jima is watching rpms/bwm-ng
jima is maintainer of rpms/clusterssh
jima is watching rpms/conserver
jima is watching rpms/dnsmasq
jima is watching rpms/graphviz
jima is watching rpms/libdnet
jima is watching rpms/libstatgrab
jima is watching rpms/miau
jima is watching rpms/ngrep
jima is maintainer of rpms/perl-Device-SerialPort
jima is maintainer of rpms/perl-X11-Protocol
jima is watching rpms/prtconf
jima is watching rpms/putty
jima is watching rpms/rblcheck
jima is watching rpms/scanssh
jima is watching rpms/silo
jima is watching rpms/vblade
jima is watching rpms/videodog
jima is watching rpms/xorg-x11-drv-sunbw2
jima is watching rpms/xorg-x11-drv-suncg14
jima is watching rpms/xorg-x11-drv-suncg3
jima is watching rpms/xorg-x11-drv-suncg6
jima is watching rpms/xorg-x11-drv-sunffb
jima is watching rpms/xorg-x11-drv-sunleo
jima is watching rpms/xorg-x11-drv-suntcx

jjmcd is main admin of rpms/R-qcc
jjmcd has a bugzilla override on rpms/R-qcc
jjmcd is main admin of rpms/rcrpanel
jjmcd has a bugzilla override on rpms/rcrpanel

juanmabc is main admin of rpms/mkproject
juanmabc has a bugzilla override on rpms/mkproject
juanmabc is main admin of rpms/rf
juanmabc has a bugzilla override on rpms/rf
juanmabc is main admin of rpms/tw
juanmabc has a bugzilla override on rpms/tw

kmatsui is main 

Non-responsive maintainer: liangwen12year nando pavlix zoglesby

[Pierre-Yves Chibon]

Good Morning Everyone,

The packagers listed here have been receiving a daily email asking them to
either adjust their bugzilla or their FAS account so the email address in FAS
matches an existing bugzilla account.

Having a bugzilla account is mandatory per:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account

- liangwen12year contacted since April 6th
- nando contacted since March 26th
- pavlix contacted since March 18th
- zoglesby contacted since April 6th


liangwen12year is maintainer of rpms/nmstate

nando is maintainer of rpms/clthreads
nando is maintainer of rpms/hydrogen
nando is maintainer of rpms/jamin
nando is watching rpms/jconv
nando is maintainer of rpms/jconvolver
nando is maintainer of rpms/ladspa-amb-plugins
nando is maintainer of rpms/ladspa-blop-plugins
nando is maintainer of rpms/ladspa-caps-plugins
nando is maintainer of rpms/ladspa-cmt-plugins
nando is maintainer of rpms/ladspa-fil-plugins
nando is maintainer of rpms/ladspa-mcp-plugins
nando is maintainer of rpms/ladspa-rev-plugins
nando is maintainer of rpms/ladspa-tap-plugins
nando is maintainer of rpms/ladspa-vco-plugins
nando is maintainer of rpms/muse
nando is maintainer of rpms/qjackctl
nando is maintainer of rpms/qsynth
nando is watching rpms/rtaudio
nando is main admin of rpms/sooperlooper
nando has a bugzilla override on rpms/sooperlooper
nando is maintainer of rpms/swami
nando is maintainer of rpms/zita-convolver

pavlix is watching rpms/NetworkManager-iodine
pavlix is watching rpms/NetworkManager-l2tp
pavlix is watching rpms/NetworkManager-openconnect
pavlix is watching rpms/NetworkManager-openvpn
pavlix is watching rpms/NetworkManager-pptp
pavlix is maintainer of rpms/NetworkManager-ssh
pavlix is maintainer of rpms/NetworkManager-strongswan
pavlix is watching rpms/NetworkManager-vpnc
pavlix is watching rpms/bind10
pavlix is maintainer of rpms/dhcpcd
pavlix is maintainer of rpms/dnsmasq
pavlix is maintainer of rpms/dnssec-trigger
pavlix is maintainer of rpms/getdns
pavlix is maintainer of rpms/hostname
pavlix is maintainer of rpms/iproute
pavlix is maintainer of rpms/libecap
pavlix is maintainer of rpms/python-ptrace
pavlix is maintainer of rpms/python-pyroute2
pavlix is maintainer of rpms/radvd
pavlix is maintainer of rpms/rdist
pavlix is maintainer of rpms/rsync
pavlix is maintainer of rpms/squid
pavlix is maintainer of rpms/strongswan
pavlix is maintainer of rpms/unbound

zoglesby is main admin of rpms/ghc-X11-xft
zoglesby has a bugzilla override on rpms/ghc-X11-xft
zoglesby is watching rpms/ghc-utf8-string
zoglesby is maintainer of rpms/publican-fedora


Does anyone know how to contact them?


Thanks,

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Redirecting and testing the new fedocal in openshift

[Pierre-Yves Chibon]

On Wed, Apr 07, 2021 at 10:30:25AM +0200, Arnaud wrote:
> All of them give me the error.
> 
> I checked in tor browser, and it doesn't do it there.
> It must be my firefox configuration (but it is the one I use all the time).
> 
> As it does it only for me it seems (and the ones that use a configuration 
> close to me),
> I give you the error log I get in firefox as information.

So we've debugged this on IRC and found out that this was related to the french
locale that basically fails to load.

I've turned off localization in fedocal for now until someone can figure out how
to make it work properly in a container (starting with compiling the .po files
so they are usable).

We tested in staging and once we found the fix we pushed it in production as
well, so things are now working for Arnaud as well as darknao who could also
reproduce this.

Thanks for your help folks!


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Redirecting and testing the new fedocal in openshift

[Pierre-Yves Chibon]

On Wed, Apr 07, 2021 at 10:09:00AM +0200, Arnaud wrote:
> Hello, 
> 
> Maybe it is just me, but I am getting: Internal Server Error
> if I click on a calendar for: https://calendar.fedoraproject.org/

Could you give a link?
All of these work for me:
https://calendar.fedoraproject.org/design-FAD/
https://calendar.fedoraproject.org/Elections/
https://calendar.fedoraproject.org/infrastructure/

Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[PATCH] proxies: redirect apps.fp.o/calendar to calendar.fp.o in openshift

[Pierre-Yves Chibon]

Signed-off-by: Pierre-Yves Chibon 
---
 playbooks/include/proxies-redirects.yml | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/playbooks/include/proxies-redirects.yml 
b/playbooks/include/proxies-redirects.yml
index 17a536149..49f2bb418 100644
--- a/playbooks/include/proxies-redirects.yml
+++ b/playbooks/include/proxies-redirects.yml
@@ -111,6 +111,12 @@
 regex: /voting
 target: https://elections.fedoraproject.org/
 
+  - role: httpd/redirectmatch
+shortname: calendar
+website: apps.fedoraproject.org
+regex: /calendar
+target: https://calendar.fedoraproject.org/
+
   - role: httpd/redirectmatch
 shortname: mailman
 website: admin.fedoraproject.org
-- 
2.30.2
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[PATCH] proxies: redirect apps.fp.o/calendar to calendar.fp.o in openshift

[Pierre-Yves Chibon]

Signed-off-by: Pierre-Yves Chibon 
---
 playbooks/include/proxies-redirects.yml | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/playbooks/include/proxies-redirects.yml 
b/playbooks/include/proxies-redirects.yml
index 17a536149..4d5223ad5 100644
--- a/playbooks/include/proxies-redirects.yml
+++ b/playbooks/include/proxies-redirects.yml
@@ -111,6 +111,12 @@
 regex: /voting
 target: https://elections.fedoraproject.org/
 
+  - role: httpd/redirectmatch
+shortname: calendar
+website: admin.fedoraproject.org
+regex: /calendar
+target: https://calendar.fedoraproject.org/
+
   - role: httpd/redirectmatch
 shortname: mailman
 website: admin.fedoraproject.org
-- 
2.30.2
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Redirecting and testing the new fedocal in openshift

[Pierre-Yves Chibon]

This is both a call for more testing as well as the first FBR of this
new freeze.

I have deployed fedocal in openshift, using OIDC and fedora-messaging,
running on python 3 at: https://calendar.fedoraproject.org
I have done some testing and for what I looked at and for everything
seems to work (including the sending of the reminder email).

If you have a little time, please have a look at it.
Do note that this instances uses the prod database so be reasonable, if
you want to do more testing feel free to poke at the staging instance
at: https://calendar.stg.fedoraproject.org.

Unless I hear otherwise, I would like to redirect the current (VM-based)
fedocal over to its new location (openshift) using the attached patch.

+1?

Thanks,

Pierre

___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Congrats to Nick Bebout

[Pierre-Yves Chibon]

On Mon, Apr 05, 2021 at 08:47:54AM -0700, Kevin Fenzi wrote:
> Greetings.
> 
> I'm happy to announce that Nick Bebout(fas: nb, irc: nb)
> has been added to our sysadmin-main group.
> 
> This is the core group of trusted folks that high level access to most
> everything in fedora infrastructure.
> 
> Nick has been doing infrastructure tasks for various groups for many
> years in sysadmin-noc, sysadmin-web, and too many other groups to list.
> 
> He's proved his dedication, trustworthiness, and ability.
> 
> Congrats!

Congrats and welcome aboard ;-)


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Has dist-git changed/broken in the last few hours?

[Pierre-Yves Chibon]

On Wed, Mar 31, 2021 at 01:52:16PM +0100, Richard W.M. Jones wrote:
> 
> $ git pull --rebase
> fatal: '/rpms/libguestfs' does not appear to be a git repository
> fatal: Could not read from remote repository.
> 
> Please make sure you have the correct access rights
> and the repository exists.
> 
> $ git remote get-url origin
> ssh://rjo...@pkgs.fedoraproject.org/rpms/libguestfs


I can reproduce. Something is odd.
Looking into it and updated status.fp.o


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora 34 Beta Freeze is now over

[Pierre-Yves Chibon]

With the successful release of Fedora 34 beta yesterday we are now out of
freeze.

Our next planned freeze is 2021-04-06 for Fedora 34 final.

Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Planned Outage - Fedora Account System Replacement - 2021-03-25 10:30 UTC

[Pierre-Yves Chibon]

On Mon, Mar 22, 2021 at 01:56:46PM +0100, Pavel Raiskup wrote:
> In Copr We use OpenID API in FAS to allow users to log-in, and to gather some
> basic info about the user (FAS groups and timezone afair).  Will this API work
> after the transition?

For OpenID, saml or OIDC we rely on ipsilon which is not being directly impacted
by this change. It will need to be reconfigured to check LDAP instead of FAS in
the backend, but the beauty of these this auth protocol is that the auth
applications should not be impacted by this change.

Feel free to point at id.stg.fedoraproject.org if you would like to test this.


Pierre


> On Friday, March 19, 2021 3:23:16 PM CET Mark O'Brien wrote:
> > All,
> > 
> > Fedora infrastructure is getting a new accounts system! To put this in
> > place we will need an outage to our services.
> > 
> > There will be an outage starting at 2021-03-25 10:30UTC,
> > which will last approximately *TWO* days.
> > 
> > To convert UTC to your local time, take a look at
> > http://fedoraproject.org/wiki/Infrastructure/UTCHowto
> > or run:
> > 
> > date -d '2021-03-25 10:30UTC'
> > 
> > *Affected Services:*
> > 
> > All Fedora Services
> > 
> > 
> >- As this is the authentication system there may be issues logging in to
> >some services.
> >- Users may not be able to access people.fedoraproject.org or
> >secondary.fedoraproject.org during the outage
> >- Maintainer test instances are a special case and as such will be in a
> >"frozen" state for access after the outage. This means that no updates 
> > will
> >be made to users or ssh keys on these machines.
> > 
> > 
> > Ticket:
> > 
> > https://pagure.io/fedora-infrastructure/issue/9747
> > 
> > If you have any questions or concerns please use any of the following
> > methods of communication.
> > 
> >- Comment on the ticket
> >- IRC on #fedora-admin or #fedora-noc
> >- Reply to this mail
> > 
> 
> 
> 
> ___
> infrastructure mailing list -- infrastructure@lists.fedoraproject.org
> To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive maintainer: kir

[Pierre-Yves Chibon]

On Tue, Mar 16, 2021 at 06:44:21PM +0200, Alexander Bokovoy wrote:
> On ti, 16 maalis 2021, Pierre-Yves Chibon wrote:
> > Good Morning Everyone,
> > 
> > Since February 24th the packager kir has been receiving a daily email asking
> > them to either adjust their bugzilla or their FAS account so the email 
> > address
> > in FAS matches an existing bugzilla account.
> > 
> > Having a bugzilla account is mandatory per:
> > https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account
> > 
> > kir is maintainer of rpms/runc
> > 
> > Does anyone know how to contact kir?
> 
> Yes, I asked Kir to respond.

It seems the situation has been fixed, thanks for your help!


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Congrats to Tomáš Hrčka

[Pierre-Yves Chibon]

On Tue, Mar 16, 2021 at 02:06:16PM -0700, Kevin Fenzi wrote:
> Greetings. 
> 
> I'm happy to announce that Tomáš Hrčka (fas: humaton, irc: jednorozec)
> has been added to our sysadmin-main group. 
> 
> This is the core group of trusted folks that high level access to most
> everything in fedora infrastructure.
> 
> Tomáš has been doing a great job working on releng tasks as well as
> releng apps and scripting and the like.
> 
> He's proved his dedication, trustworthiness, and ability.
> 
> Congrats!
> 
> Use your powers for good! :)

Congrats Tomáš!

And remember: "with great powers come great electricity bills".
Hm, I'm suddenly wondering if this is the right quote...

Anyway, congrats again!


Pierre


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: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Non-responsive maintainer: kir

[Pierre-Yves Chibon]

Good Morning Everyone,

Since February 24th the packager kir has been receiving a daily email asking
them to either adjust their bugzilla or their FAS account so the email address
in FAS matches an existing bugzilla account.

Having a bugzilla account is mandatory per:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account

kir is maintainer of rpms/runc

Does anyone know how to contact kir?


Thanks,

Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: libravatar ported to Fedora's AWS

[Pierre-Yves Chibon]

On Sun, Mar 14, 2021 at 10:32:23PM +, clime wrote:
> Hello,
> 
> I have just finished port of libravatar.org service to server provided
> by Fedora. Big thanks to the Fedora project for sponsoring libravatar.
> Avatars in pagure.io, src.fp.o, Bodhi should now load much faster.

Awesome, thanks!


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Bodhi client prompting for a password

[Pierre-Yves Chibon]

On Thu, Mar 04, 2021 at 12:15:53AM +0100, Björn Persson wrote:
> Fabio Valentini wrote:
> > On Wed, Mar 3, 2021 at 9:31 PM Miro Hrončok  wrote:
> > >
> > > On 03. 03. 21 21:08, Florian Weimer wrote:  
> > > > I want to run this command:
> > > >
> > > >bodhi updates trigger-tests FEDORA-2021-279dee1742
> > > >
> > > > But I'm prompted for a username and password.  I have a working Kerberos
> > > > setup for koji/fedpkg, so this is somewhat surprising.  Is this
> > > > expected?  
> > >
> > > Yes, that is how bodhi CLI client works.  
> > 
> > Yes. Sadly, most Fedora projects use different methods for
> > authenticating with your FAS account.
> > 
> > koji uses kerberos, bodhi uses OpenID over HTTP, dist-git uses SSH ...
> 
> It wouldn't be a user interface problem if they'd all fetch the
> passcode from the same keyring. Then the user wouldn't need to know how
> many different protocols are used under the hood.

Well kerberos, FAS, OpenID, OIDC are all using the same password. Only the ssh
key can differ depending on how it was created.


Pierre


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: ssh git access to src.fedoraproject.org feedback

[Pierre-Yves Chibon]

On Wed, Mar 03, 2021 at 07:35:00PM -0500, Neal Gompa wrote:
> On Wed, Mar 3, 2021 at 6:12 PM Kevin Fenzi  wrote:
> >
> > On Wed, Mar 03, 2021 at 05:26:46PM -0500, Neal Gompa wrote:
> > > On Wed, Mar 3, 2021, 5:13 PM Matthew Miller 
> > > wrote:
> > >
> > > > On Wed, Mar 03, 2021 at 01:53:28PM -0800, Kevin Fenzi wrote:
> > > > > 4) We could add some kind of GSSAPI/Kerberos support to pagure, so
> > > > > people could use https and a kerberos ticket.
> > > >
> > > > What's amount of effort required for this option? Because other than "it
> > > > might be a lot of work", it seems ideal, and would resolve a lot of 
> > > > other
> > > > cases where it's an extra step to have to configure an access token for
> > > > pagure. But "it might be a lot of work" is a pretty big con.
> > > >
> > > > If the answer is "yeah, it's a lot", I vote for whichever other option
> > > > makes
> > > > this a logical next step when there is time to do such work.
> > > >
> > >
> > > I don't think it would be that hard anymore. Recently, Pagure changed to
> > > proxy and handle Git via HTTPS, meaning that we can do whatever we want to
> > > authenticate pulls and pushes.
> >
> > Except this doesn't work currently for src.fedoraproject.org pagure, as
> > the OIDC tokens take over. :(
> >
> 
> Yeah, we need to fix this somehow. But it shouldn't be too hard, I
> think? We already have this setup for pagure.io...

No pagure.io doesn't have mod_oidc allowing to push over https using an OIDC
token.

Moving to mod_gssapi may be the way to do this, however I'm no sure how
eaasy/hard it will be to get it to support full pagure user account.


Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora Account System and Bugzilla Mismatch email

[Pierre-Yves Chibon]

On Wed, Mar 03, 2021 at 11:27:44AM -, Lukas Zapletal wrote:
> Hey,
> 
> I got an email asking me to change my fedora email to match my BZ account. 
> Problem is, in BZ I have to use my redhat account which allows me to be 
> granted special permissions for RH-related bugs. Fedora wants to do this for 
> the same reason, however I'd like to separate my upstream contribution and 
> all accounts from my work account, therefore I'd like to continue using my 
> private email.
> 
> Is this something that can be solved? Like by adding a special field which is 
> used to link BZ so users can set these individually?

There is an override file at:
https://pagure.io/fedora-infra/ansible/raw/main/f/roles/openshift-apps/toddlers/templates/email_overrides.toml
that can be used to, well override email in FAS with email in bugzilla.

Feel free to open a pull-request to edit that file and add yourself :)


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 Change: rpmautospec - removing release and changelog fields from spec files (System-Wide Change proposal)

[Pierre-Yves Chibon]

On Wed, Mar 03, 2021 at 01:07:44AM +0100, Miro Hrončok wrote:
> On 02. 03. 21 22:05, Pierre-Yves Chibon wrote:
> > The devil is in the details: pre-release, snapinfo, minorbump aren't really
> > covered by distance being just an integer bumped.
> 
> I don't see this covered in the current method either. Or was it in the
> meantime? Anyway:

It is planned and part of the work to be done with this proposal:
https://docs.pagure.org/fedora-infra.rpmautospec/autorel.html#using-autorel
 
> - pre-release should go into version (~)
> - snapinfo should go into version (~ or ^)
> 
> The only real problem I see here is minorbump. We could have something like:
> %{autorel -m}. That means, micobump since this was added here. But I guess
> it is ugly.
> 
> > I know we considered the "number of commits since the last version bump" 
> > when we
> > looked into this. I honestly do not remember precisely why we didn't go 
> > with it.
> 
> IIRC it was because you considered building several rebuilds with different
> releases from the same commit a goal (while I'd rather require an empty
> commit that explains the reason for the rebuild).

Indeed, that approach would not allow rebuilding a commit without adding a new
(potentially empty) commit.
One of the idea being that not having to add commits would make it easier to do
auto-rebuild of dependency chains.


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 35 Change: rpmautospec - removing release and changelog fields from spec files (System-Wide Change proposal)

[Pierre-Yves Chibon]

On Tue, Mar 02, 2021 at 09:30:41PM +0100, Fabio Valentini wrote:
> On Tue, Feb 16, 2021 at 8:20 PM Pierre-Yves Chibon  
> wrote:
> >
> > On Tue, Feb 16, 2021 at 03:38:35PM +0100, Fabio Valentini wrote:
> > > On Tue, Feb 16, 2021 at 3:01 PM Miro Hrončok  wrote:
> > > >
> > > > On 16. 02. 21 14:48, Fabio Valentini wrote:
> > > > >  if version_at(commit) != last_version:
> > > > >  return 0
> > > >
> > > > Should this be "return 1"?
> > >
> > > No, 0 is correct. If the version does not match, this is the last
> > > commit *before* a version update.
> > > The "max(parents) + 1" then sets the Release to 1 for the commit that
> > > actually changed the version :)
> > >
> > > > To prevent accidental divergence between the git history and the build 
> > > > system.
> > > > That's why this information is only used in the koji plugin, locally 
> > > > (ie: via
> > > > the rpmautospec CLI) it only relies on the git tags.
> > >
> > > So ... you want to *prevent* divergence by *introducing* divergence? I
> > > do not follow ...
> >
> > The build information is used to check if all the builds made in koji 
> > exists as
> > tags. If they don't, then they are added, thus resolving the divergence.
> > If they do, git tags are used, just like they are used locally.
> 
> There's another issue that I see with using both git tags and koji
> build history:
> How do users get those tags into their local repository clones, if
> they are created by koji after successful builds?

The first time it can be done via the rpmautospect CLI command.

> Will we need to "git pull" after every successful koji build so we get
> consistent results between local checkout and infra build?

After that, git pull/fetch is indeed the easiest method.

> Side note: This amended algorithm should always produce incrementing
> release numbers, even across branches:
> 
> def release_num(commit, last_version) -> int:
> if version_at(commit) != last_version:
> return 0
> else:
> distance = max(release_num(parent, last_version) for parent of 
> commit))
> if is_merge_commit(commit):
> return distance
> else:
> return distance + 1
> 
> That should solve both the upgrade path issue and the data source
> problem. No need to look at either git tags or koji build history :)

The devil is in the details: pre-release, snapinfo, minorbump aren't really
covered by distance being just an integer bumped.

I know we considered the "number of commits since the last version bump" when we
looked into this. I honestly do not remember precisely why we didn't go with it.

Maybe Nils or Adam remember it?


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Non-responsive maintainer: sabbaka

[Pierre-Yves Chibon]

Good Morning Everyone,

Since February 7th the packager sabbaka has been receiving a daily email asking
them to either adjust their bugzilla or their FAS account so the email address
in FAS matches an existing bugzilla account.

Having a bugzilla account is mandatory per:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Create_a_Bugzilla_Account

sabbaka is maintainer of rpms/tlog

Does anyone know how to contact sabbaka?


Thanks,

Pierre



PS: the users dkaspar, kir and leogallego having been receiving the same email
since February 24th. Their attention to that email would be appreciated.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Introducing the ARC sub-team in CPE - and first research topic

[Pierre-Yves Chibon]

On Mon, Jan 18, 2021 at 04:25:09PM +0100, Pierre-Yves Chibon wrote:
> Good Morning Everyone,
> 
> While planning work, the CPE team has realized that a number of our 
> initiatives
> actually start with a research phase to find the most appropriate technical
> solution.
> This leads to some issues with planning as without knowing the technical
> solution we want to take, it's hard to evaluate the amount of work needed and
> thus the time it'll take to do it.
> 
> In order to help with this, we're creating a small sub-team in CPE, called the
> ARC team for Advance Reconaissance Crew*.
> The goal of this team will be to investigate what we believe to be the 
> possible
> technical solutions for initiatives and advise the team on what they believe
> would be the appropriate solution.
> To this end, we will reach out when we start looking for ideas as you may have
> ideas that we did not think about.
> 
> The first investigation, led by Will Woods, Mark O'Brien and I, will be around
> datanommer and datagrepper.
> 
> datanommer is an application listening to fedmsg and filling a (postgresql)
> database with all the messages passing on the bus.
> datagrepper is a web application exposing these messages and offering a way to
> filter or search them.
> available at: https://apps.fedoraproject.org/datagrepper/
> 
> Currently our ideas are:
> - for datanommer:
> - port it to fedora-messaging
> - adjust it to whichever solution we chose to replace datagrepper
> 
> - for datagrepper:
> - keep it as is
> - Replace by
> - postgres https://postgrest.org/
> - prest https://github.com/prest/prest
> - kinto https://docs.kinto-storage.org/en/stable/
> - Swagger/OpenAPI https://swagger.io/
> - Add support for Graphql
> 
> - for the postgresql server
> - Split messages per year in different table
> - Unite them using a postgresql view
> - Kick out the old messages per year
> - Keep the current year + n-1 in the current DB
> - Kick the other to another DB?
> - Kick the other to a tarball somewhere?
> - Output the database daily dump to file / year
> - TimescaleDB a postgresql plugin for time-series data
> - 
> https://alibaba-cloud.medium.com/postgresql-time-series-database-plug-in-timescaledb-deployment-practices-6a07e246eb0d
> - https://dev.t-matix.com/blog/postgresql-as-a-time-series-database/
> - https://docs.timescale.com/latest/introduction
> - Make the msg field in the message table be a JSON field
> 
> Would you have any other ideas of things we could look at?

Just as a follow up to this thread, our findings can be found at: 
https://fedora-arc.readthedocs.io/en/latest/datanommer_datagrepper/index.html
and I've also presented them in a blog post at:
http://blog.pingoured.fr/index.php?post/2021/02/26/datanommer/datagrepper-investigations


Hoping this helps,
Pierre
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: git push on master branch rejected.

[Pierre-Yves Chibon]

On Mon, Feb 22, 2021 at 09:28:53AM -0500, Steve Dickson wrote:
> 
> 
> On 2/22/21 2:39 AM, Pierre-Yves Chibon wrote:
> > On Sun, Feb 21, 2021 at 05:21:33PM -0500, Steve Dickson wrote:
> >>
> >> Thanks you for your rapid reply! 
> >>
> >> On 2/21/21 4:57 PM, Michael Young wrote:
> >>> On Sun, 21 Feb 2021, Steve Dickson wrote:
> >>>
> >>>> I apologies if I missed something... If there is a
> >>>> thread that talks about this please point me at it
> >>>> but...
> >>>>
> >>>> when I do a git push on the master branch I get:
> >>> ...
> >>>
> >>> You missed the branch renaming - master has been replaced by rawhide with 
> >>> alias main.
> >> I figured it was something like that... but when I do a git branch -r I 
> >> don't 
> >> see the rawhide branch... So how do I move from master to rawhide?
> >>
> >> From your explanation I figured all I had to is a
> >>  git checkout -b main origin/main
> >>
> >> which worked but when I do a git pull I get
> >>
> >> $ git pull
> >> error: cannot lock ref 'refs/remotes/origin/rawhide': 
> >> 'refs/remotes/origin/rawhide/user/steved/pnfs-rawhide' exists; cannot 
> >> create 'refs/remotes/origin/rawhide'
> >> From ssh://pkgs.fedoraproject.org/rpms/nfs-utils
> >>  ! [new branch]  rawhide-> origin/rawhide  (unable to update local 
> >> ref)
> >>
> >> It appears that a very old refs "origin/rawhide/user/steved/pnfs-rawhide" 
> >> is messing things up... so how do I get ride of that old refs?
> > 
> > I have renamed it on the server side, so if you try again this should work 
> > now
> > :)
> Thank you... but I still unable to create the rawhide branch:
> 
> git pull
> error: cannot lock ref 'refs/remotes/origin/rawhide': 
> 'refs/remotes/origin/rawhide/user/steved/pnfs-rawhide' exists; cannot create 
> 'refs/remotes/origin/rawhide'
> From ssh://pkgs.fedoraproject.org/rpms/nfs-utils
>  ! [new branch]  rawhide-> origin/rawhide  (unable to update local 
> ref)
>  * [new branch]  rawhide_old/user/steved/pnfs-rawhide -> 
> origin/rawhide_old/user/steved/pnfs-rawhide
> 
> Doing the pull again I get:
> 
> git pull
> error: cannot lock ref 'refs/remotes/origin/rawhide': 
> 'refs/remotes/origin/rawhide/user/steved/pnfs-rawhide' exists; cannot create 
> 'refs/remotes/origin/rawhide'
> From ssh://pkgs.fedoraproject.org/rpms/nfs-utils
>  ! [new branch]  rawhide-> origin/rawhide  (unable to update local 
> ref)

Do you have the old rawhide/user/sted/pnfs-rawhide branch in your local clone?
If so, try git fetch -p or just delete the branch (since it was renamed, you
could checkout rawhide_old/user/steved/pnfs-rawhide at any point).

It seems the issue is with your local clone.


Pierre
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure