Re: Non-responsive maintainer check for lkundrak

2024-05-03 Thread Tomi Lähteenmäki
On ti, huhti 30 2024 at 14.07.47 +02:00:00, Miroslav Suchý 
 wrote:



 plus work related email (added to cc)


Thank you! I was able to get a reply in Mastodon.

-Tomi

--
___
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: Non-responsive maintainer check for lkundrak

2024-04-30 Thread Miroslav Suchý

Dne 30. 04. 24 v 12:25 odp. Tomi Lähteenmäki napsal(a):

Hi,

I'm trying to reach the maintainer of phosh [1] and phoc [2]. Allan has tried to reach out for him without success [3] 
so I created bug [4] for this non-responsive maintainer check.


If someone knows how to contact him, please let me know.


https://metalhead.club/@lkundrak

plus work related email (added to cc)

--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
--
___
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


Non-responsive maintainer check for lkundrak

2024-04-30 Thread Tomi Lähteenmäki

Hi,

I'm trying to reach the maintainer of phosh [1] and phoc [2]. Allan has 
tried to reach out for him without success [3] so I created bug [4] for 
this non-responsive maintainer check.


If someone knows how to contact him, please let me know.

Best Regards,
Tomi Lähteenmäki

[1] <https://src.fedoraproject.org/rpms/phosh>
[2] <https://packages.fedoraproject.org/pkgs/phoc/phoc/>
[3] 
<https://matrix.to/#/!sXLzaXgfXmVJufaSWq:fedoraproject.org/$enwmPkm_mLr27-OEb78Uk4XIXCJreZ1_IwjUBpUJBeY?via=matrix.scrye.com=matrix.org=fedora.im>

[4] <https://bugzilla.redhat.com/show_bug.cgi?id=2277951>


--
___
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: Non-responsive maintainer check for aarapov

2024-04-15 Thread Richard W.M. Jones
(Adding Eugene for increased visibility)

On Mon, Apr 15, 2024 at 02:38:01PM +0200, Anton Arapov wrote:
> Hello Lichen,
> 
> I commented on the issue. Apologies, I didn’t spot it earlier;
> https://pagure.io/find-inactive-packagers/issue/1695
> 
> https://pagure.io/user/esyr Eugene Syromiatnikov, should be looking after 
> dmidecode; He should be with Red Hat still.

About dmidecode, it's currently shown with just Anton as packager:

https://src.fedoraproject.org/rpms/dmidecode

If Eugene wishes to co-maintain we should add him.

Lichen Liu and Coiby Xu are Red Hat associates & kernel devs who are
maintaining this package in RHEL, and they have expressed a wish to
co-maintain it also:

https://pagure.io/packager-sponsors/issue/644

Note this is not either-or, you can all co-maintain it together if you
want, but the package currently seems unmaintained.

Rich.

> Anton.
> 
> > On 15. 4. 2024, at 4:28, Lichen Liu  wrote:
> > 
> > Hello devel-list!
> > 
> > Does anyone know how to contact @aarapov, the maintainer of dmidecode?
> > 
> > Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2275034
> > 
> > I haven't seen any activity recently, and there is a 
> > find-inactive-packagers ticket:
> > 
> > https://pagure.io/find-inactive-packagers/issue/1695
> > 
> > Dmidecode is a very important package, I want to keep it updated.
> > 
> > Thanks
> > 
> > Lichen
> > 

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
--
___
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


Non-responsive maintainer check for aarapov

2024-04-14 Thread Lichen Liu

Hello devel-list!

Does anyone know how to contact @aarapov, the maintainer of dmidecode?

Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2275034

I haven't seen any activity recently, and there is a 
find-inactive-packagers ticket:


https://pagure.io/find-inactive-packagers/issue/1695

Dmidecode is a very important package, I want to keep it updated.

Thanks

Lichen
--
___
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: Non-responsive maintainer landgraf for package aunit.

2024-03-28 Thread Björn Persson
Pavel Zhukov wrote:
> I see you have received review of the MR .  Emails have been answered by 
> Bjorn too.

If you don't have time to maintain Aunit, then please give me or Dennis
access to the package so we can take care of it.

Björn Persson


pgpFCmfiDkSCT.pgp
Description: OpenPGP digital signatur
--
___
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: Non-responsive maintainer landgraf for package aunit.

2024-03-28 Thread Dennis van Raaij
Hi Pavel,

Thanks for your response.

> I see you have received review of the MR .

Yes, indeed. I'm grateful that Bjorn was willing to have look at the PR despite 
not being a co-maintainer of the package.

> Emails have been answered by Bjorn too.

Yes, but I got no reply from you as the sole maintainer of package aunit.

So, would you be willing to have a look at the PR and consider it for updating 
the package?

- Dennis
--
___
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: Non-responsive maintainer landgraf for package aunit.

2024-03-28 Thread Pavel Zhukov
I see you have received review of the MR .  Emails have been answered by Bjorn 
too.

--
Pavel


On Thu, Mar 28, 2024, at 20:17, Dennis van Raaij wrote:
> Hi,
> 
> I've been trying to contact package maintainer Pavel Zhukov (landgraf).
> 
> I submitted a proposal to update package 'aunit' some months ago [1] but
> received no response from its maintainer, Pavel Zhukov. This proposal 
> supersedes
> an earlier one for which I received no response either. I tried to contact him
> by email [2] but did not receive a reply.
> 
> As I have no other way to get in contact, and as the PR has been open for
> months, I've decided to submit a bug [3] and post here as per Fedora 
> guidelines
> on non-responsive maintainers.
> 
> - Dennis
> 
> [1] https://src.fedoraproject.org/rpms/aunit/pull-request/2
> [2] https://accounts.fedoraproject.org/user/landgraf/?
> [3] https://bugzilla.redhat.com/show_bug.cgi?id=2272094
> --
> ___
> 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
> 
--
___
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


Non-responsive maintainer landgraf for package aunit.

2024-03-28 Thread Dennis van Raaij
Hi,

I've been trying to contact package maintainer Pavel Zhukov (landgraf).

I submitted a proposal to update package 'aunit' some months ago [1] but
received no response from its maintainer, Pavel Zhukov. This proposal supersedes
an earlier one for which I received no response either. I tried to contact him
by email [2] but did not receive a reply.

As I have no other way to get in contact, and as the PR has been open for
months, I've decided to submit a bug [3] and post here as per Fedora guidelines
on non-responsive maintainers.

- Dennis

[1] https://src.fedoraproject.org/rpms/aunit/pull-request/2
[2] https://accounts.fedoraproject.org/user/landgraf/?
[3] https://bugzilla.redhat.com/show_bug.cgi?id=2272094
--
___
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: Non-responsive maintainer check for dagostinelli

2024-03-28 Thread Arthur Bols

On 27/03/2024 14:28, Andreas Schneider wrote:

Hi,

I'm trying to reach the maintainer of fswatch [1]. fswatch will be a
dependency of neovim 0.10 and I would like to get it updated to be prepared
for the release. It looks like the maintainer is unresponsive. I've open the
bugs [2] and [3]. [3] is the bug for this non-responsive maintainer check for
dagostinelli.

I can also (co-)maintain the package as it is a dependency of neovim soon.


Best regards


Andreas


[1] https://src.fedoraproject.org/rpms/fswatch
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2270266
[3] https://bugzilla.redhat.com/show_bug.cgi?id=2271832

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

I haven't seen him, adding CC to their email.

--
Arthur Bols
fas/irc: principis
--
___
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


Non-responsive maintainer check for dagostinelli

2024-03-28 Thread Andreas Schneider
Hi,

I'm trying to reach the maintainer of fswatch [1]. fswatch will be a 
dependency of neovim 0.10 and I would like to get it updated to be prepared 
for the release. It looks like the maintainer is unresponsive. I've open the 
bugs [2] and [3]. [3] is the bug for this non-responsive maintainer check for 
dagostinelli.

I can also (co-)maintain the package as it is a dependency of neovim soon.


Best regards


Andreas


[1] https://src.fedoraproject.org/rpms/fswatch
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2270266
[3] https://bugzilla.redhat.com/show_bug.cgi?id=2271832

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


Non-responsive maintainer check for lcts

2024-01-05 Thread Lukáš Zaoral
Hello!
Does anyone know how to contact @lcts, the maintainer of rear?

Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2256943

I see no activity in dist-git, Koji or Bugzilla for more than a year.

There is currently an urgent bug in rear which must be fixed.
Otherwise, the tool is practically unusable on Fedora at the moment:

https://bugzilla.redhat.com/show_bug.cgi?id=2254871

Currently, the are also other bugs assigned to lcts including
over 100 nextcloud CVE tracking bugs without any response so far.

Regards,
Lukas
--
___
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: Non responsive maintainer check for marxin

2024-01-05 Thread Sandro

On 05-01-2024 01:50, Priscila Gutierres wrote:

I would like to apologize if it seems that I’m being rude asking for a
review in this thread.


It's perfectly fine asking for a review. But that should go into its own 
mail to the list or, preferably, to <${package}-maintainers@fp.o>.


Currently, this thread aims to solve the maintainer situation with 
regards to pebble. Once that's done, the package will be handed over to 
an active maintainer.


Since you appear to be interested in maintaining pebble, you might even 
get to be added as a maintainer once the current situation has been solved.



My point of view is that if the package is a dependency and no one is
looking on it, it would be a priority to keep it up to date.


That depends...


I don’t know if merging it would be possible, since the maintainer is not
responding, if not, I can close it.


Leave it open. A proven packager can still merge it or you may get to 
merge it yourself once the package has been handed over.



Also, I noticed any maintainer can merge it.


Yes. Anyone with commit rights can merge. But currently there's only one 
person enlisted and only that person can add co-maintainers.



I am a new maintainer and I don’t want to create polemics, I am here to
hear and learn, but if I don’t participate in the discussion is more hard
to learn. In any case, I apologize again if I was impolite.


It's all good. This thread is regarding the non-responsive maintainer 
check [1]. It shouldn't become a discussion thread. That's all I was/am 
concerned about.


[1] 
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/

--
___
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: Non responsive maintainer check for marxin

2024-01-04 Thread Priscila Gutierres
I would like to apologize if it seems that I’m being rude asking for a
review in this thread.
My point of view is that if the package is a dependency and no one is
looking on it, it would be a priority to keep it up to date.
I don’t know if merging it would be possible, since the maintainer is not
responding, if not, I can close it.
Also, I noticed any maintainer can merge it.
I am a new maintainer and I don’t want to create polemics, I am here to
hear and learn, but if I don’t participate in the discussion is more hard
to learn. In any case, I apologize again if I was impolite.


Em qui., 4 de jan. de 2024 às 20:07, Sandro  escreveu:

> On 04-01-2024 23:05, Priscila Gutierres wrote:
> > I bumped python-pebble to the latest version.
> > Can someone please review this PR?
> > https://src.fedoraproject.org/rpms/python-pebble/pull-request/3
>
> Reviewing the PR is not a problem. However, who would merge it, once
> approved? That needs a proven packager in the current situation, since
> the sole maintainer is unresponsive.
>
> No offense, but you are kinda hijacking this thread.
>
> -- Sandro
>
> --
> ___
> 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
>
--
___
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: Non responsive maintainer check for marxin

2024-01-04 Thread Sandro

On 04-01-2024 23:05, Priscila Gutierres wrote:

I bumped python-pebble to the latest version.
Can someone please review this PR?
https://src.fedoraproject.org/rpms/python-pebble/pull-request/3


Reviewing the PR is not a problem. However, who would merge it, once 
approved? That needs a proven packager in the current situation, since 
the sole maintainer is unresponsive.


No offense, but you are kinda hijacking this thread.

-- Sandro

--
___
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: Non responsive maintainer check for marxin

2024-01-04 Thread Priscila Gutierres
I bumped python-pebble to the latest version.
Can someone please review this PR?
https://src.fedoraproject.org/rpms/python-pebble/pull-request/3


On Tue, Jan 2, 2024 at 5:05 PM Sandro  wrote:

> On 02-01-2024 20:28, Priscila Gutierres wrote:
> > Does any package depend on python-pebble?
> > I could not find anything running repoquery  --whatrequires python-pebble
>
> You need to query for `python3-pebble`.
>
> $ dnf repoquery --whatrequires python3-pebble
> Last metadata expiration check: 0:04:03 ago on Tue 02 Jan 2024 20:57:02.
> cvise-0:2.8.0-1.fc39.x86_64
> python3-bluepyopt-0:1.14.3-1.fc39.x86_64
> python3-bluepyopt-0:1.14.6-5.fc39.x86_64
>
> I use `fedrq` these days.
>
> $ fedrq wr -s python3-pebble
> cvise-2.9.0-1.fc40.src
> python-bluepyopt-1.14.6-5.fc40.src
>
> -- Sandro
>
> --
> ___
> 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
>
--
___
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: Non responsive maintainer check for marxin

2024-01-02 Thread Priscila Gutierres
Thank you !

Em ter., 2 de jan. de 2024 às 17:05, Sandro  escreveu:

> On 02-01-2024 20:28, Priscila Gutierres wrote:
> > Does any package depend on python-pebble?
> > I could not find anything running repoquery  --whatrequires python-pebble
>
> You need to query for `python3-pebble`.
>
> $ dnf repoquery --whatrequires python3-pebble
> Last metadata expiration check: 0:04:03 ago on Tue 02 Jan 2024 20:57:02.
> cvise-0:2.8.0-1.fc39.x86_64
> python3-bluepyopt-0:1.14.3-1.fc39.x86_64
> python3-bluepyopt-0:1.14.6-5.fc39.x86_64
>
> I use `fedrq` these days.
>
> $ fedrq wr -s python3-pebble
> cvise-2.9.0-1.fc40.src
> python-bluepyopt-1.14.6-5.fc40.src
>
> -- Sandro
>
> --
> ___
> 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
>
--
___
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: Non responsive maintainer check for marxin

2024-01-02 Thread Sandro

On 02-01-2024 20:28, Priscila Gutierres wrote:

Does any package depend on python-pebble?
I could not find anything running repoquery  --whatrequires python-pebble


You need to query for `python3-pebble`.

$ dnf repoquery --whatrequires python3-pebble
Last metadata expiration check: 0:04:03 ago on Tue 02 Jan 2024 20:57:02.
cvise-0:2.8.0-1.fc39.x86_64
python3-bluepyopt-0:1.14.3-1.fc39.x86_64
python3-bluepyopt-0:1.14.6-5.fc39.x86_64

I use `fedrq` these days.

$ fedrq wr -s python3-pebble
cvise-2.9.0-1.fc40.src
python-bluepyopt-1.14.6-5.fc40.src

-- Sandro

--
___
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: Non responsive maintainer check for marxin

2024-01-02 Thread Priscila Gutierres
Does any package depend on python-pebble?
I could not find anything running repoquery  --whatrequires python-pebble

On Tue, Jan 2, 2024 at 2:56 PM Ankur Sinha  wrote:

> Hi folks,
>
> Would anyone know how to contact @marxin? They only maintain the one
> package, python-pebble, but it doesn't look like they've been active in
> a while. The package did not see to have been updated at all since the
> initial import:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2227456
>
> and there are now new pending bugs that have not seen responses too:
> https://bugzilla.redhat.com/show_bug.cgi?id=2250914
>
> We've waited for responses to PRs in the past and then had to use proven
> packager rights to update and maintain the package:
>
> https://src.fedoraproject.org/rpms/python-pebble/pull-request/2
> https://src.fedoraproject.org/rpms/python-pebble/commits/rawhide
>
> Since a Neuro-SIG package depends on it, we're happy to take it over.
>
> Here's what I could get from fedora-active-user:
>
> python fedora_active_user.py --user marxin --email mli...@suse.cz
> --nofas
> Last action on koji:
>Fri, 15 Sep 2023 tag_package_owners entry created by humaton [still
>active]
>
>Last package update on bodhi:
>   2020-06-29 07:10:30 on package python-pebble-4.5.3-1.fc33
>   Last actions performed according to fedmsg:
>
>   Last email on mailing list:
>   ERROR:active-user:name 'mailinglist' is not defined
>
>
> Here's the tracker bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=2256491
>
> --
> Thanks,
> Regards,
> Ankur Sinha "FranciscoD" (He / Him / His) |
> https://fedoraproject.org/wiki/User:Ankursinha
> Time zone: Europe/London
> --
> ___
> 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
>
--
___
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


Non responsive maintainer check for marxin

2024-01-02 Thread Ankur Sinha
Hi folks,

Would anyone know how to contact @marxin? They only maintain the one
package, python-pebble, but it doesn't look like they've been active in
a while. The package did not see to have been updated at all since the
initial import:

https://bugzilla.redhat.com/show_bug.cgi?id=2227456

and there are now new pending bugs that have not seen responses too:
https://bugzilla.redhat.com/show_bug.cgi?id=2250914

We've waited for responses to PRs in the past and then had to use proven
packager rights to update and maintain the package:

https://src.fedoraproject.org/rpms/python-pebble/pull-request/2
https://src.fedoraproject.org/rpms/python-pebble/commits/rawhide

Since a Neuro-SIG package depends on it, we're happy to take it over.

Here's what I could get from fedora-active-user:

python fedora_active_user.py --user marxin --email mli...@suse.cz
--nofas
Last action on koji:
   Fri, 15 Sep 2023 tag_package_owners entry created by humaton [still
   active]

   Last package update on bodhi:
  2020-06-29 07:10:30 on package python-pebble-4.5.3-1.fc33
  Last actions performed according to fedmsg:

  Last email on mailing list:
  ERROR:active-user:name 'mailinglist' is not defined


Here's the tracker bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2256491

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


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


Non-responsive maintainer check for Samuel P (survient)

2023-12-06 Thread Ondřej Holý
Hi,

this email is part of the non-responsive maintainer policy for the wsdd
package:
https://bugzilla.redhat.com/show_bug.cgi?id=2253133

It would be nice to update the package to the latest upstream:
https://bugzilla.redhat.com/show_bug.cgi?id=2175523

I proposed a pull request for it two months ago but it remains unnoticed:
https://src.fedoraproject.org/rpms/wsdd/pull-request/1

The last activity by the maintainer on the package was in 2021:
https://src.fedoraproject.org/rpms/wsdd/c/5d6fcc9443ecb7a41c965df2fe562f277843ac8b

There is no activity recorded for the past year:
https://src.fedoraproject.org/user/survient

Does anyone know how to contact the maintainer?

Regards

Ondrej
--
___
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


Non-responsive maintainer check for David Howells (dhowells)

2023-11-12 Thread bbhtt
Hi, 

This email is part of the non-responsive maintainer policy for the keyutils [1] 
package (https://bugzilla.redhat.com/show_bug.cgi?id=2249374).

The package is several versions out-of-date, 1.6.3 being the latest one, 
released in 2020.

The last activity by the maintainer on the package was in 2018 [2] and 
src.fedoraproject.org shows no activity for the past year with several PRs open.

Does anyone know how to contact the maintainer (I've cc-ed them to this email)?

The published version is affected by this bug [3] which is fixed in 1.6.3 and 
prevents building other packages depending on keyutils like keepassxc (git 
develop) [4].


[1]: https://src.fedoraproject.org/rpms/keyutils
[2]: 
https://src.fedoraproject.org/rpms/keyutils/c/f14178ee749fee6ff20e0e162caf997f7dedd453?branch=rawhide
[3]: 
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git/commit/keyutils.h?id=9b815047340ad7e1d9e3be496b232a29f1b5b232
[4]: https://github.com/keepassxreboot/keepassxc/pull/8983

Thanks!

-- 
- bbhtt

https://bbhtt.github.io/
___
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


Non-responsive maintainer check for eneville

2023-10-26 Thread Fabio Valentini
Hi all,

Does anybody know if eneville is still contributing to Fedora and / or
how to reach them?

c.f. https://bugzilla.redhat.com/show_bug.cgi?id=2246443

I see no activity in dist-git, bodhi, koji, or pagure.io in the last 365 days.

Their packages seem to have been unmaintained for a while, and there
is now also an open CVE issues against rust-pleaser: CVE-2023-46277

c.f. https://bugzilla.redhat.com/show_bug.cgi?id=2245340

Fabio
___
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


Bug 2246344 - Non-responsive maintainer check for hno

2023-10-26 Thread Michal Ambroz
Hello,
Please anyone knows about any other channel to contact hno - Henrik
Nordstrom ?

I have not heard from him for like a year and I would like to take over the
primary admin role
for the radare2 package so the bugs get primarily assigned to me.





This is part of the non-responsive maintainer check for hno - Bug 2246344
https://bugzilla.redhat.com/show_bug.cgi?id=2246344
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_
maintainers/
(https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/)




Thank you


Michal Ambroz
___
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: Non-responsive maintainer Daiki Ueno

2023-09-20 Thread Daiki Ueno
Hello,

Peter Oliver  writes:

> As per the non-responsive package maintainer process
> (https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/),
> does anyone know how to contact Daiki Ueno?  fedora-active-user isn’t
> working for me at the moment, so I haven’t been able to check his
> activity within Fedora, but he is active elsewhere (e.g.,
> https://gitlab.com/dueno).
>
> There is a backlog of pull requests for the Fedora Emacs package
> (https://src.fedoraproject.org/rpms/emacs/pull-requests).  Marc-André
> Lureau and I have volunteered to become co-maintainers to help merge
> them, but we have not had a response.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2239916

I'm still active in Fedora and willing to help emacs when time permits;
I just updated the bug.

Sorry for not responding to the co-maintainer request sooner; you two
should have the commit rights now.

Regards,
-- 
Daiki Ueno
___
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


Non-responsive maintainer Daiki Ueno

2023-09-20 Thread Peter Oliver

As per the non-responsive package maintainer process 
(https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/),
 does anyone know how to contact Daiki Ueno?  fedora-active-user isn’t working 
for me at the moment, so I haven’t been able to check his activity within 
Fedora, but he is active elsewhere (e.g., https://gitlab.com/dueno).

There is a backlog of pull requests for the Fedora Emacs package 
(https://src.fedoraproject.org/rpms/emacs/pull-requests).  Marc-André Lureau 
and I have volunteered to become co-maintainers to help merge
them, but we have not had a response.

https://bugzilla.redhat.com/show_bug.cgi?id=2239916

--
Peter Oliver___
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: Non-responsive maintainer mkulik

2023-09-13 Thread Mattia Verga via devel
Il 13/09/23 11:58, Filip Janus ha scritto:

> Hi all,
> mkulik is the main admin of pg_auto_failover component, and I can't reach 
> him. So I would like to start the process of moving the main admin role to 
> me(I am an admin now but the default assignee is mkulik due to the main admin 
> role).
> Here is the mandatory BZ:
> https://bugzilla.redhat.com/show_bug.cgi?id=2238708
>
> -Filip-

Note that there's also an ongoing ticket for the inactive packagers policy:

https://pagure.io/find-inactive-packagers/issue/1673

Mattia___
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


Non-responsive maintainer mkulik

2023-09-13 Thread Filip Janus
Hi all,
mkulik is the main admin of pg_auto_failover component, and I can't reach
him. So I would like to start the process of moving the main admin role to
me(I am an admin now but the default assignee is mkulik due to the main
admin role).
Here is the mandatory BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=2238708

-Filip-
___
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: Non-responsive maintainer check for Karsten Hopp (karsten)

2023-09-09 Thread Mattia Verga via devel
Il 09/09/23 02:09, Valter Sage ha scritto:
> Does anyone know how to contact Karsten Hopp (karsten)? This email is 
> part of the non-responsive maintainer process 
> (https://bugzilla.redhat.com/show_bug.cgi?id=2237962).
>
> The activity report at https://src.fedoraproject.org/user/karsten/ 
> shows no activity in the past year, and fedora-active-user reports:
>
> Last package update on bodhi:
>    2020-10-21 13:02:09 on package libcap-2.44-1.fc34
>
> A list of some other apparently-neglected bugs follows:
>
>     libcap: sole maintainer, new version available for almost three 
> years https://bugzilla.redhat.com/show_bug.cgi?id=1919609
>
>     dictd: FTBFS in Fedora rawhide/f39 
> https://bugzilla.redhat.com/show_bug.cgi?id=2225754
>
> I apologize in advance for any errors or omissions in this list.


Note that there is also an ongoing ticket for the inactive-packagers policy:

https://pagure.io/find-inactive-packagers/issue/1478

Mattia

___
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


Non-responsive maintainer check for Karsten Hopp (karsten)

2023-09-08 Thread Valter Sage
Does anyone know how to contact Karsten Hopp (karsten)? This email is part
of the non-responsive maintainer process (
https://bugzilla.redhat.com/show_bug.cgi?id=2237962).

The activity report at https://src.fedoraproject.org/user/karsten/ shows no
activity in the past year, and fedora-active-user reports:

Last package update on bodhi:
   2020-10-21 13:02:09 on package libcap-2.44-1.fc34

A list of some other apparently-neglected bugs follows:

libcap: sole maintainer, new version available for almost three years
https://bugzilla.redhat.com/show_bug.cgi?id=1919609

dictd: FTBFS in Fedora rawhide/f39
https://bugzilla.redhat.com/show_bug.cgi?id=2225754

I apologize in advance for any errors or omissions in this list.
___
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


Non-responsive maintainer check for juergh

2023-08-24 Thread Ondrej Mosnáček
Hello,

Does anyone know how to contact juergh (Juerg Haefliger)? They are the
sole maintainer of a single package in Fedora (cloud-utils), which
hasn't seen any activity for almost 4 years.

I've filed a non-responsive check bug here:
https://bugzilla.redhat.com/show_bug.cgi?id=2234606

Here are open bugs and PRs waiting for a response from them:
https://src.fedoraproject.org/rpms/cloud-utils/pull-request/3
https://bugzilla.redhat.com/show_bug.cgi?id=2051099
https://bugzilla.redhat.com/show_bug.cgi?id=2184158

Thanks,
Ondrej
___
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


rpms/sslh non-responsive maintainer

2023-07-29 Thread Maxim Van Damme
Dear Devel list

I was sent here from the Non-responsive maintainer policy.
Does anyone know how to contact the maintainer (aperezbios) for the package 
rpms/sslh.
The following ticket was openend some time ago: 
https://bugzilla.redhat.com/show_bug.cgi?id=2191660
Please let me know if you need anything else.

Kind Regards
Maxim Van Damme
___
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: Non-responsive maintainer check for Athos Ribeiro,(athoscr)

2023-07-17 Thread Ben Beasley
Thanks for your response! Of course, I understand that free time is a scarce 
and unpredictable commodity.

Please do let me know if you need someone to co-maintain, or just make a few 
PR’s for, any of the font-related Python packages.

Best wishes,
Ben Beasley (FAS music)

On Mon, Jul 17, 2023, at 3:51 PM, Athos Ribeiro wrote:
> On Mon, Jul 17, 2023 at 03:13:31PM -0400, Ben Beasley wrote:
>>Does anyone know how to contact Athos Ribeiro (FAS: athoscr)? This 
>>email is part of the non-responsive maintainer process 
>>(https://bugzilla.redhat.com/show_bug.cgi?id=2223422).
>
> Hi Ben,
>
> Thanks for the contact :)
>
> I haven't been able to give those some love due to ENOTIME different job
> in a while.
>
> I am setting up my fedora dev env once again this week and will start
> either giving some love to each of those or start passing the one I am
> no longer interested in maintaining forward!
>
>>The following PR and bug/NEEDINFO have received no response in 7-9 months:
>>
>>https://src.fedoraproject.org/rpms/python-defcon/pull-request/1
>>
>>    https://bugzilla.redhat.com/show_bug.cgi?id=1936574
>>
>>The activity report at https://src.fedoraproject.org/user/athoscr/ 
>>shows no activity in the past year, and fedora-active-user reports:
>>
>>    $ python3 fedora_active_user.py --user athoscr --nofas
>>    Last action on koji:
>>       Wed, 31 May 2023 tag_package_owners entry created by bodhi 
>>[still active]
>>
>>    Last package update on bodhi:
>>       2021-02-19 23:00:32 on package hugo-0-1
>>    Last actions performed according to fedmsg:
>>      - io.pagure.prod.pagure.issue.comment.added on 2023-02-15 07:07:42
>>
>>A list of some other apparently-neglected bugs follows.
>>
>>Updates available for a long time with the release-monitoring.org bugs 
>>still in the NEW state:
>>
>>    flawfinder: https://bugzilla.redhat.com/show_bug.cgi?id=1914559
>>
>>    python-fontMath: https://bugzilla.redhat.com/show_bug.cgi?id=1974954
>>
>>    python-glyphsLib: https://bugzilla.redhat.com/show_bug.cgi?id=1881116
>>
>>    python-pyclipper: https://bugzilla.redhat.com/show_bug.cgi?id=194
>>
>>    rubygem-chake: https://bugzilla.redhat.com/show_bug.cgi?id=1907051
>>
>>    rubygem-fakefs: https://bugzilla.redhat.com/show_bug.cgi?id=2209178
>>
>>    rubygem-pathspec: https://bugzilla.redhat.com/show_bug.cgi?id=1912644
>>
>>A Python 3.12 compatibility bug has also received no response since 
>>late last year:
>>
>>    python-firehose: https://bugzilla.redhat.com/show_bug.cgi?id=2154946
>>
>>Additionally, a request to consider fixing or retiring a package:
>>
>>    rubygem-sinatra-rabbit: 
>>https://bugzilla.redhat.com/show_bug.cgi?id=1880144
>>
>
> -- 
> Athos Ribeiro
___
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: Non-responsive maintainer check for Athos Ribeiro,(athoscr)

2023-07-17 Thread Athos Ribeiro

On Mon, Jul 17, 2023 at 03:13:31PM -0400, Ben Beasley wrote:
Does anyone know how to contact Athos Ribeiro (FAS: athoscr)? This 
email is part of the non-responsive maintainer process 
(https://bugzilla.redhat.com/show_bug.cgi?id=2223422).


Hi Ben,

Thanks for the contact :)

I haven't been able to give those some love due to ENOTIME different job
in a while.

I am setting up my fedora dev env once again this week and will start
either giving some love to each of those or start passing the one I am
no longer interested in maintaining forward!


The following PR and bug/NEEDINFO have received no response in 7-9 months:

https://src.fedoraproject.org/rpms/python-defcon/pull-request/1

    https://bugzilla.redhat.com/show_bug.cgi?id=1936574

The activity report at https://src.fedoraproject.org/user/athoscr/ 
shows no activity in the past year, and fedora-active-user reports:


    $ python3 fedora_active_user.py --user athoscr --nofas
    Last action on koji:
       Wed, 31 May 2023 tag_package_owners entry created by bodhi 
[still active]


    Last package update on bodhi:
       2021-02-19 23:00:32 on package hugo-0-1
    Last actions performed according to fedmsg:
      - io.pagure.prod.pagure.issue.comment.added on 2023-02-15 07:07:42

A list of some other apparently-neglected bugs follows.

Updates available for a long time with the release-monitoring.org bugs 
still in the NEW state:


    flawfinder: https://bugzilla.redhat.com/show_bug.cgi?id=1914559

    python-fontMath: https://bugzilla.redhat.com/show_bug.cgi?id=1974954

    python-glyphsLib: https://bugzilla.redhat.com/show_bug.cgi?id=1881116

    python-pyclipper: https://bugzilla.redhat.com/show_bug.cgi?id=194

    rubygem-chake: https://bugzilla.redhat.com/show_bug.cgi?id=1907051

    rubygem-fakefs: https://bugzilla.redhat.com/show_bug.cgi?id=2209178

    rubygem-pathspec: https://bugzilla.redhat.com/show_bug.cgi?id=1912644

A Python 3.12 compatibility bug has also received no response since 
late last year:


    python-firehose: https://bugzilla.redhat.com/show_bug.cgi?id=2154946

Additionally, a request to consider fixing or retiring a package:

    rubygem-sinatra-rabbit: 
https://bugzilla.redhat.com/show_bug.cgi?id=1880144




--
Athos Ribeiro
___
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


Non-responsive maintainer check for Athos Ribeiro,(athoscr)

2023-07-17 Thread Ben Beasley
Does anyone know how to contact Athos Ribeiro (FAS: athoscr)? This email 
is part of the non-responsive maintainer process 
(https://bugzilla.redhat.com/show_bug.cgi?id=2223422).


The following PR and bug/NEEDINFO have received no response in 7-9 months:

https://src.fedoraproject.org/rpms/python-defcon/pull-request/1

    https://bugzilla.redhat.com/show_bug.cgi?id=1936574

The activity report at https://src.fedoraproject.org/user/athoscr/ shows 
no activity in the past year, and fedora-active-user reports:


    $ python3 fedora_active_user.py --user athoscr --nofas
    Last action on koji:
       Wed, 31 May 2023 tag_package_owners entry created by bodhi 
[still active]


    Last package update on bodhi:
       2021-02-19 23:00:32 on package hugo-0-1
    Last actions performed according to fedmsg:
      - io.pagure.prod.pagure.issue.comment.added on 2023-02-15 07:07:42

A list of some other apparently-neglected bugs follows.

Updates available for a long time with the release-monitoring.org bugs 
still in the NEW state:


    flawfinder: https://bugzilla.redhat.com/show_bug.cgi?id=1914559

    python-fontMath: https://bugzilla.redhat.com/show_bug.cgi?id=1974954

    python-glyphsLib: https://bugzilla.redhat.com/show_bug.cgi?id=1881116

    python-pyclipper: https://bugzilla.redhat.com/show_bug.cgi?id=194

    rubygem-chake: https://bugzilla.redhat.com/show_bug.cgi?id=1907051

    rubygem-fakefs: https://bugzilla.redhat.com/show_bug.cgi?id=2209178

    rubygem-pathspec: https://bugzilla.redhat.com/show_bug.cgi?id=1912644

A Python 3.12 compatibility bug has also received no response since late 
last year:


    python-firehose: https://bugzilla.redhat.com/show_bug.cgi?id=2154946

Additionally, a request to consider fixing or retiring a package:

    rubygem-sinatra-rabbit: 
https://bugzilla.redhat.com/show_bug.cgi?id=1880144

___
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: non-responsive maintainer check for anthr76

2023-07-14 Thread Mikel Olasagasti
Hi Mark,

Anthony announced a hiatus a couple of months ago:

https://lists.fedoraproject.org/archives/list/gol...@lists.fedoraproject.org/thread/5NUXD4CESPDXKV6NQL2QDQAZP4BTQF2I/

As go-sig has permissions I guess you can continue updating the
package once unretired.

Regards,
Mikel

Hau idatzi du Mark E. Fuller (mark.e.ful...@gmx.de) erabiltzaileak
(2023 uzt. 14(a), or. (18:03)):
>
> https://bugzilla.redhat.com/show_bug.cgi?id=964
>
> This email is part of the non-responsive maintainer procedure for
> anthr76, following
> https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/.
>
> Please respond if you are still active in Fedora and want to maintain
> golang-github-google-renameio-2.
>
> Please see the request for unretirement at
> https://bugzilla.redhat.com/show_bug.cgi?id=2219084
>
> ___
> 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
___
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


non-responsive maintainer check for anthr76

2023-07-14 Thread Mark E. Fuller

https://bugzilla.redhat.com/show_bug.cgi?id=964

This email is part of the non-responsive maintainer procedure for 
anthr76, following 
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/.


Please respond if you are still active in Fedora and want to maintain 
golang-github-google-renameio-2.


Please see the request for unretirement at 
https://bugzilla.redhat.com/show_bug.cgi?id=2219084




OpenPGP_0xD599E76CFFCABF60.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital 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


[Bug 2219882] - Non-responsive maintainer check for jirka

2023-07-05 Thread reanima...@fedoraproject.org
Does anyone know how to reach jirka?

https://bugzilla.redhat.com/show_bug.cgi?id=2219882
___
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: Non responsive maintainer check for @ilgrad

2023-07-03 Thread Ankur Sinha
FYI: also forwarded to the correct gmail address (I'd used org instead of com)

On Mon, Jul 03, 2023 11:43:05 +0100, Ankur Sinha wrote:
> Dear all,
> 
> Would anyone know how to contact @ilgrad (Ilya Gradina)? They are one of
> the original members of the neuro-sig packager group, but we've not
> heard from them in quite a while now.
> 
> I've filed a non-responsive check bug here:
> https://bugzilla.redhat.com/show_bug.cgi?id=2219364
> 
> Here are the bugs that they've not responded to:
> https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__=Fedora=product%2Ccomponent%2Cassigned_to%2Cstatus%2Csummary%2Clast_change_time%2Cseverity%2Cpriority=ilya.gradina%40gmail.com_to1=1=1=substring_id=13252967=status%2C%20priority%2C%20assigned_to%2C%20id%2C%20=Fedora_format=advanced
> 
> 
> fedora_active_user.py output:
> 
> $ python fedora_active_user.py --user ilgrad --email ilya.grad...@gmail.com 
> --nofas
> Last action on koji:
>Fri, 10 Mar 2023 tag_package_owners entry created by humaton [still active]
> 
> Last package update on bodhi:
>2019-10-22 22:36:05 on package flacon-5.5.1-1.fc31
> Last actions performed according to fedmsg:
>   - io.pagure.prod.pagure.issue.comment.added on 2022-08-18 23:28:59
> 
> Last email on mailing list:
>   On 2016-04-07T11:58:30Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
> https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
>   On 2016-04-07T11:14:57Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
> https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
>   On 2016-04-07T10:47:15Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
> https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
>   On 2016-04-05T19:55:29Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
> https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
>   On 2016-04-04T22:26:04Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
> https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
>   On 2016-04-04T19:30:01Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
> https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
>   On 2015-08-07T20:28:02Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
> https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
>   On 2015-07-20T15:16:18Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
> https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
> 
> Bugzilla activity
>6 bugs assigned, cc or on which ilya.grad...@gmail.com commented
> Last comment on the most recent ticket on bugzilla:
> 
> 
> -- 
> Thanks,
> Regards,
> Ankur Sinha "FranciscoD" (He / Him / His) | 
> https://fedoraproject.org/wiki/User:Ankursinha
> Time zone: Europe/London



-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


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


Non responsive maintainer check for @ilgrad

2023-07-03 Thread Ankur Sinha
Dear all,

Would anyone know how to contact @ilgrad (Ilya Gradina)? They are one of
the original members of the neuro-sig packager group, but we've not
heard from them in quite a while now.

I've filed a non-responsive check bug here:
https://bugzilla.redhat.com/show_bug.cgi?id=2219364

Here are the bugs that they've not responded to:
https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__=Fedora=product%2Ccomponent%2Cassigned_to%2Cstatus%2Csummary%2Clast_change_time%2Cseverity%2Cpriority=ilya.gradina%40gmail.com_to1=1=1=substring_id=13252967=status%2C%20priority%2C%20assigned_to%2C%20id%2C%20=Fedora_format=advanced


fedora_active_user.py output:

$ python fedora_active_user.py --user ilgrad --email ilya.grad...@gmail.com 
--nofas
Last action on koji:
   Fri, 10 Mar 2023 tag_package_owners entry created by humaton [still active]

Last package update on bodhi:
   2019-10-22 22:36:05 on package flacon-5.5.1-1.fc31
Last actions performed according to fedmsg:
  - io.pagure.prod.pagure.issue.comment.added on 2022-08-18 23:28:59

Last email on mailing list:
  On 2016-04-07T11:58:30Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
  On 2016-04-07T11:14:57Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
  On 2016-04-07T10:47:15Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
  On 2016-04-05T19:55:29Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
  On 2016-04-04T22:26:04Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
  On 2016-04-04T19:30:01Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
  On 2015-08-07T20:28:02Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
  On 2015-07-20T15:16:18Z ilya.grad...@gmail.com emailed as Ilia Gradina on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/

Bugzilla activity
   6 bugs assigned, cc or on which ilya.grad...@gmail.com commented
Last comment on the most recent ticket on bugzilla:


-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


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: Non-responsive maintainer - rkuska

2023-04-17 Thread Mattia Verga via devel
Il 17/04/23 17:39, Jakub Kadlcik ha scritto:
> Hello,
> per the Non-responsive maintainer policy
> https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers
>
> I am sending this email. We (copr-sig) would like to (co)maintain the
> python-flask-whooshee package but @rkuska can't give us permission
> because he lost access to his FAS account.
>
> We talked about this off-list, so this is basically just FYI for others.
>
> RHBZ ticket: https://bugzilla.redhat.com/show_bug.cgi?id=2042681
>
> Jakub

rksuska was removed from packagers some months ago:

https://pagure.io/find-inactive-packagers/issue/253

python-flask-whooshee was orphaned and is now taken by msuchy. I've
resetted the BZ ticket assignee to the default assignee (msuchy).

Mattia

___
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


Non-responsive maintainer - rkuska

2023-04-17 Thread Jakub Kadlcik
Hello,
per the Non-responsive maintainer policy
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers

I am sending this email. We (copr-sig) would like to (co)maintain the
python-flask-whooshee package but @rkuska can't give us permission
because he lost access to his FAS account.

We talked about this off-list, so this is basically just FYI for others.

RHBZ ticket: https://bugzilla.redhat.com/show_bug.cgi?id=2042681

Jakub
___
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: Non-responsive maintainer check for jamatos

2023-03-23 Thread José Abílio Matos
On Monday, 13 March 2023 03.50.01 WET Yaakov Selkowitz wrote:
> This is a non-responsive maintainer check for jamatos (José Matos).  Does
> anyone know how to contact José?

I am here and I will look into those issues.
The end of the first semester fallback took a lot longer than I was expecting.

-- 
José Abílio

___
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


Non-responsive maintainer check for datamash

2023-03-18 Thread Georg Sauthoff
Hello,

I've entered

Bug 2179536 - Non-responsive maintainer check for datamash 

to see whether the maintainer is still interested in maintaining that
package.

Background: That package was almost retired, and in the last months of
that retirement process the maintainer didn't respond to any related
bugzilla activity:

https://bugzilla.redhat.com/show_bug.cgi?id=2045298
https://bugzilla.redhat.com/show_bug.cgi?id=2056736

It just wasn't retired because a proven packager applied a patch I
provided, after I brought that issue to the mailinglist.

Does anyone know how to contact jhladky?


Best regards,
Georg

-- 
'This bit is cleared only by a POR/PDR
 or by setting the WURST bit in the PMU_CTL register.'
(GD32VF103 RISC-V MCU User Manual)
___
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: Non-responsive maintainer check for eclipseo

2023-03-16 Thread Dominik 'Rathann' Mierzejewski
Hi, Bob!

On Thursday, 16 March 2023 at 07:34, Bob Mauchin wrote:
> I'm here just very busy with work and being tired, I ll try to work on
> stuff this weekend.

It's a relief knowing you're okay. I have one bug in particular I'd like
to draw your attention to: https://bugzilla.redhat.com/show_bug.cgi?id=2162675
Please let me know if you're ok with me resolving it for you.

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
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: Non-responsive maintainer check for eclipseo

2023-03-16 Thread Bob Mauchin
I'm here just very busy with work and being tired, I ll try to work on
stuff this weekend.

On Wed, Mar 15, 2023, 18:23 Mark E. Fuller  wrote:

> Thanks for the suggestion, but I do not use Twitter and don't want to
> create an account.
>
>
> On March 15, 2023 5:13:43 PM GMT+02:00, Fabio Valentini <
> decatho...@gmail.com> wrote:
>
>> On Wed, Mar 15, 2023 at 4:04 PM Mark E. Fuller  
>> wrote:
>>
>>>
>>>  Hi,
>>>  This is a non-responsive maintainer check for eclipseo.
>>>  I am trying to contact him as the owner of
>>>  golang-github-masterminds-semver[0].
>>>  There is one other open non-responsive maintainer check, filed ~2 weeks
>>>  ago[1].
>>>  Does anyone know how to contact eclipseo?
>>>
>>
>> I haven't had luck with getting responses to bugs or emails either ...
>> Maybe reaching out on twitter could work? https://twitter.com/eclipseo10
>>
>> Fabio
>> --
>> 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
>>
>> ___
> 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
>
___
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: Non-responsive maintainer check for eclipseo

2023-03-15 Thread Mark E. Fuller
Thanks for the suggestion, but I do not use Twitter and don't want to create an 
account.

On March 15, 2023 5:13:43 PM GMT+02:00, Fabio Valentini  
wrote:
>On Wed, Mar 15, 2023 at 4:04 PM Mark E. Fuller  
>wrote:
>>
>> Hi,
>> This is a non-responsive maintainer check for eclipseo.
>> I am trying to contact him as the owner of
>> golang-github-masterminds-semver[0].
>> There is one other open non-responsive maintainer check, filed ~2 weeks
>> ago[1].
>> Does anyone know how to contact eclipseo?
>
>I haven't had luck with getting responses to bugs or emails either ...
>Maybe reaching out on twitter could work? https://twitter.com/eclipseo10
>
>Fabio
>___
>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
___
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: Non-responsive maintainer check for eclipseo

2023-03-15 Thread Fabio Valentini
On Wed, Mar 15, 2023 at 4:04 PM Mark E. Fuller  wrote:
>
> Hi,
> This is a non-responsive maintainer check for eclipseo.
> I am trying to contact him as the owner of
> golang-github-masterminds-semver[0].
> There is one other open non-responsive maintainer check, filed ~2 weeks
> ago[1].
> Does anyone know how to contact eclipseo?

I haven't had luck with getting responses to bugs or emails either ...
Maybe reaching out on twitter could work? https://twitter.com/eclipseo10

Fabio
___
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


Non-responsive maintainer check for eclipseo

2023-03-15 Thread Mark E. Fuller

Hi,
This is a non-responsive maintainer check for eclipseo.
I am trying to contact him as the owner of 
golang-github-masterminds-semver[0].
There is one other open non-responsive maintainer check, filed ~2 weeks 
ago[1].

Does anyone know how to contact eclipseo?

Thanks,
fuller

[0] https://bugzilla.redhat.com/show_bug.cgi?id=2178685
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2166945
___
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


Non-responsive maintainer check for jamatos

2023-03-12 Thread Yaakov Selkowitz
This is a non-responsive maintainer check for jamatos (José Matos).  Does
anyone know how to contact José?

https://bugzilla.redhat.com/show_bug.cgi?id=2175015
https://bugzilla.redhat.com/show_bug.cgi?id=2171739
https://bugzilla.redhat.com/show_bug.cgi?id=2171428
https://bugzilla.redhat.com/show_bug.cgi?id=2159961
https://bugzilla.redhat.com/show_bug.cgi?id=2155024
https://bugzilla.redhat.com/show_bug.cgi?id=2143162
https://bugzilla.redhat.com/show_bug.cgi?id=2141483
https://bugzilla.redhat.com/show_bug.cgi?id=2140587
https://bugzilla.redhat.com/show_bug.cgi?id=2135121
https://bugzilla.redhat.com/show_bug.cgi?id=2113191
https://bugzilla.redhat.com/show_bug.cgi?id=2071484
https://bugzilla.redhat.com/show_bug.cgi?id=2071430
https://bugzilla.redhat.com/show_bug.cgi?id=2031345
https://bugzilla.redhat.com/show_bug.cgi?id=2020067
https://bugzilla.redhat.com/show_bug.cgi?id=2005785
https://src.fedoraproject.org/rpms/tellico/pull-request/5

-- 
Yaakov Selkowitz
Principal Software Engineer - Platform Enablement
Red Hat, Inc.
___
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


Non-responsive maintainer check for avsej

2023-02-12 Thread Yaakov Selkowitz
This is a non-responsive maintainer check for avsej (Sergey Avseyev).  Does
anyone know how to contact Sergey?

https://bugzilla.redhat.com/show_bug.cgi?id=2169250
https://bugzilla.redhat.com/show_bug.cgi?id=212
https://bugzilla.redhat.com/show_bug.cgi?id=2162893
https://bugzilla.redhat.com/show_bug.cgi?id=2151887
https://bugzilla.redhat.com/show_bug.cgi?id=2131877
https://bugzilla.redhat.com/show_bug.cgi?id=2102133

All of which should be fixed by:

https://src.fedoraproject.org/rpms/mypaint/pull-request/1

-- 
Yaakov Selkowitz
Principal Software Engineer - Platform Enablement
Red Hat, Inc.

___
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


Non-responsive maintainer check for andymenderunix

2023-02-02 Thread Scott Talbert
This is a non-responsive maintainer check for andymenderunix (Andy 
Mender).  Does anyone know how to contact Andy?


https://bugzilla.redhat.com/show_bug.cgi?id=2166645

Thanks,
Scott
___
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: Non-responsive maintainer check for rmattes / update libQGLViewer to 2.9.1

2023-02-01 Thread Susi Lehtola
On 1/29/23 12:57, Mamoru TASAKA wrote:
> Maybe slightly off-topic, but:
> 
> This PR removes qt4 version libQGLViewer, which skyviewer depends on:
> 
> $ dnf -q repoquery --repo=koji-38  --qf 
> '%{name}-%{epoch}:%{version}-%{release}\t%{sourcerpm}' --whatrequires 
> libQGLViewer
> libQGLViewer-devel-0:2.6.4-10.fc38libQGLViewer-2.6.4-10.fc38.src.rpm
> libQGLViewer-doc-0:2.6.4-10.fc38  libQGLViewer-2.6.4-10.fc38.src.rpm
> skyviewer-0:1.0.1-29.fc38 skyviewer-1.0.1-29.fc38.src.rpm
> 
> , and qt5 version does soname bump, which octomap depends on:
> 
> $ dnf -q repoquery --repo=koji-38  --qf 
> '%{name}-%{epoch}:%{version}-%{release}\t%{sourcerpm}' --whatrequires 
> libQGLViewer-qt5
> libQGLViewer-qt5-devel-0:2.6.4-10.fc38
> libQGLViewer-2.6.4-10.fc38.src.rpm
> octomap-octovis-0:1.9.7-5.fc38octomap-1.9.7-5.fc38.src.rpm
> $ dnf -q repoquery --repo=koji-38  --qf 
> '%{name}-%{epoch}:%{version}-%{release}\t%{sourcerpm}' --requires 
> octomap-octovis | grep QGL
> libQGLViewer-qt5.so.2.6.4()(64bit)
> 
> This means this PR is going to break all packages which currently depends on 
> libQGLViewer
> unless properly handled.
> 
> So my question is that what is the exact reason that IQmol
> "need an update of libQGLViewer to a more modern version, since the old 
> version of
> libQGLViewer is causing IQmol builds to fail".
> If this means that IQmol needs new API of libQGLViewer, this may mean that
> other packages which libQGLViewer depends on are going to FTBFS, then
> we may have to be more careful for updating libQGLViewer.

IQmol needs some functions that are only in the new API. skyviewer has also
dropped qt4 support in their latest release (from July 2020), so the issue is
that skyviewer hasn't been updated in a few years. The soname bump is hopefully
not an issue with octomap.

>> In addition to these two, I have also tried to reach Rich through
>> libqglviewer-ow...@fedoraproject.org, however, I have not received any 
>> replies
>> so far. (Granted, this all happened starting on Wednesday, but February is 
>> right
>> around the corner!)
> 
> Currently this is -maintain...@fedoraproject.org , not -owner.
> https://fedoraproject.org/wiki/EmailAliases

Thanks!
-- 
Susi Lehtola
Fedora Project Contributor
jussileht...@fedoraproject.org
___
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: Non-responsive maintainer check for rmattes / update libQGLViewer to 2.9.1

2023-01-31 Thread Rich Mattes

On 1/29/23 5:57 AM, Mamoru TASAKA wrote:


Susi Lehtola wrote on 2023/01/29 17:13:

Hi,

does anyone know how to contact Rich Mattes? They maintain 
libQGLViewer, which

was last updated five years ago

* Sun Aug 12 2018 Rich Mattes  - 2.6.4-1
- Update to release 2.6.4, with upstream fix for qreal on armv7 
(rhbz#1556028)

- Remove upstream patch and update library names

and there has been no other activity in the package other than 
automated rebuilds.


At least this is some activity from rmattes on koji on 2022/Dec:
https://koji.fedoraproject.org/koji/userinfo?userID=1186


I'm here.  Mamoru brings up some good points about the Qt4 package deps, 
we can continue the conversation in the PR.


Rich
___
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: Non-responsive maintainer check for rmattes / update libQGLViewer to 2.9.1

2023-01-29 Thread Mamoru TASAKA


Susi Lehtola wrote on 2023/01/29 17:13:

Hi,

does anyone know how to contact Rich Mattes? They maintain libQGLViewer, which
was last updated five years ago

* Sun Aug 12 2018 Rich Mattes  - 2.6.4-1
- Update to release 2.6.4, with upstream fix for qreal on armv7 (rhbz#1556028)
- Remove upstream patch and update library names

and there has been no other activity in the package other than automated 
rebuilds.


At least this is some activity from rmattes on koji on 2022/Dec:
https://koji.fedoraproject.org/koji/userinfo?userID=1186



I urgently need an update of libQGLViewer to a more modern version, since the
old version of libQGLViewer is causing IQmol builds to fail, and IQmol is at
threat of being removed in a week or so from now due to long-time FTBFS issues
originally caused by the update of OpenBabel to version 3.

https://bugzilla.redhat.com/show_bug.cgi?id=2164341

I have since done the work to update the package to version 2.6.4 myself, and
filed a pull request against libQGLViewer to update it to the newest release in

https://src.fedoraproject.org/rpms/libQGLViewer/pull-request/1


Maybe slightly off-topic, but:

This PR removes qt4 version libQGLViewer, which skyviewer depends on:

$ dnf -q repoquery --repo=koji-38  --qf 
'%{name}-%{epoch}:%{version}-%{release}\t%{sourcerpm}' --whatrequires 
libQGLViewer
libQGLViewer-devel-0:2.6.4-10.fc38  libQGLViewer-2.6.4-10.fc38.src.rpm
libQGLViewer-doc-0:2.6.4-10.fc38libQGLViewer-2.6.4-10.fc38.src.rpm
skyviewer-0:1.0.1-29.fc38   skyviewer-1.0.1-29.fc38.src.rpm

, and qt5 version does soname bump, which octomap depends on:

$ dnf -q repoquery --repo=koji-38  --qf 
'%{name}-%{epoch}:%{version}-%{release}\t%{sourcerpm}' --whatrequires 
libQGLViewer-qt5
libQGLViewer-qt5-devel-0:2.6.4-10.fc38  libQGLViewer-2.6.4-10.fc38.src.rpm
octomap-octovis-0:1.9.7-5.fc38  octomap-1.9.7-5.fc38.src.rpm
$ dnf -q repoquery --repo=koji-38  --qf 
'%{name}-%{epoch}:%{version}-%{release}\t%{sourcerpm}' --requires 
octomap-octovis | grep QGL
libQGLViewer-qt5.so.2.6.4()(64bit)

This means this PR is going to break all packages which currently depends on 
libQGLViewer
unless properly handled.

So my question is that what is the exact reason that IQmol
"need an update of libQGLViewer to a more modern version, since the old version 
of
libQGLViewer is causing IQmol builds to fail".
If this means that IQmol needs new API of libQGLViewer, this may mean that
other packages which libQGLViewer depends on are going to FTBFS, then
we may have to be more careful for updating libQGLViewer.


In addition to these two, I have also tried to reach Rich through
libqglviewer-ow...@fedoraproject.org, however, I have not received any replies
so far. (Granted, this all happened starting on Wednesday, but February is right
around the corner!)


Currently this is -maintain...@fedoraproject.org , not -owner.
https://fedoraproject.org/wiki/EmailAliases


I would like to get commit rights to libQGLViewer so I can update the package. I
do have provenpackager rights, but this would go over their purview..

The only packages that appear to depend on libQGLViewer, in addition to IQmol,
appear to be skyviewer and octomap, whose maintainers have been copied into this
messages.

Susi


Mamoru
___
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


Non-responsive maintainer check for rmattes / update libQGLViewer to 2.9.1

2023-01-29 Thread Susi Lehtola
Hi,


does anyone know how to contact Rich Mattes? They maintain libQGLViewer, which
was last updated five years ago

* Sun Aug 12 2018 Rich Mattes  - 2.6.4-1
- Update to release 2.6.4, with upstream fix for qreal on armv7 (rhbz#1556028)
- Remove upstream patch and update library names

and there has been no other activity in the package other than automated 
rebuilds.

I urgently need an update of libQGLViewer to a more modern version, since the
old version of libQGLViewer is causing IQmol builds to fail, and IQmol is at
threat of being removed in a week or so from now due to long-time FTBFS issues
originally caused by the update of OpenBabel to version 3.

https://bugzilla.redhat.com/show_bug.cgi?id=2164341

I have since done the work to update the package to version 2.6.4 myself, and
filed a pull request against libQGLViewer to update it to the newest release in

https://src.fedoraproject.org/rpms/libQGLViewer/pull-request/1

In addition to these two, I have also tried to reach Rich through
libqglviewer-ow...@fedoraproject.org, however, I have not received any replies
so far. (Granted, this all happened starting on Wednesday, but February is right
around the corner!)

I would like to get commit rights to libQGLViewer so I can update the package. I
do have provenpackager rights, but this would go over their purview..

The only packages that appear to depend on libQGLViewer, in addition to IQmol,
appear to be skyviewer and octomap, whose maintainers have been copied into this
messages.

Susi
-- 
Susi Lehtola
Fedora Project Contributor
jussileht...@fedoraproject.org
___
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: Non-responsive maintainer: mymindstorm

2023-01-19 Thread Vitaly Zaitsev via devel

On 19/01/2023 17:00, Brendan Early wrote:
Sorry for not responding to this earlier. I had changed the tickets to 
ASSIGNED in RHBZ to indicate that I am working on the problem with the 
package you are concerned about. I will have an update pushed this weekend.


Great.

Pull request with fix:
https://src.fedoraproject.org/rpms/quaternion/pull-request/1

--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
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


Non-responsive maintainer: mymindstorm

2023-01-19 Thread Vitaly Zaitsev via devel

Hello.

According to non-responsive maintainer procedure, I'm asking if anyone 
knows how to contact mymindstorm?


RHBZ issue: https://bugzilla.redhat.com/show_bug.cgi?id=2162447

--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
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


Non-responsive maintainer check for jhli

2023-01-10 Thread Ali Erdinc Koroglu

Hello everyone!
Does anyone know how to contact Juston Li (jhli)? I have tried to reach out via 
email but have not received a response.

https://bugzilla.redhat.com/show_bug.cgi?id=2159807

--
Ali Erdinc Koroglu
Linux OS Systems Engineering
___
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


Non-responsive maintainer check for amatyuko

2023-01-09 Thread Ali Erdinc Koroglu

Hello everyone!
Does anyone know how to contact Andrey Matyukov (amatyuko)? I have tried to 
reach out via email but have not received a response.

https://bugzilla.redhat.com/show_bug.cgi?id=2159390

--
Ali Erdinc Koroglu
Linux OS Systems Engineering
___
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: Non-responsive maintainer for lz4 package (pjp)

2022-12-12 Thread Smith, Stewart via devel

> On Dec 9, 2022, at 8:29 AM, Timothée Ravier  wrote:
> 
> Hey folks,
> 
> I've started the non-responsive maintainer procedure for pjp 
> (https://accounts.fedoraproject.org/user/pjp/) with 
> https://bugzilla.redhat.com/show_bug.cgi?id=2152159
> 
> I currently have a pull request that has been blocked for 4 months now: 
> https://src.fedoraproject.org/rpms/lz4/pull-request/5

… which also contains a security fix, CVE-2021-3520 which was rated by RH as a 
Moderate https://access.redhat.com/security/cve/cve-2021-3520 for its products.

So it’d be good to get the update out at some point so that Fedora users can be 
patched.
___
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


Non-responsive maintainer for lz4 package (pjp)

2022-12-09 Thread Timothée Ravier
Hey folks,

I've started the non-responsive maintainer procedure for pjp 
(https://accounts.fedoraproject.org/user/pjp/) with 
https://bugzilla.redhat.com/show_bug.cgi?id=2152159

I currently have a pull request that has been blocked for 4 months now: 
https://src.fedoraproject.org/rpms/lz4/pull-request/5

I have not checked if other pull requests or bugs are blocked.

fedora-active-user (https://github.com/pypingou/fedora-active-user) reports the 
last action as:

```
Last action on koji:
   Fri, 09 Sep 2022 tag_package_owners entry created by humaton [still active]
```

I'll CC this mail to him but if you know how to reach him that will be best.

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, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Non-responsive maintainer check for jehane

2022-11-18 Thread Mattia Verga via devel
Il 18/11/22 00:11, Sérgio Basto ha scritto:
> Almost a year later we haven't any reply
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2031448
>
>
> Marianne not have any activity since Fev 2022  (expect in a
> tag_package_owners entry!?!? )
>
> Last login in FAS:
> jehane 2021-02-18
>
> Last action on koji:
> Fri, 09 Sep 2022 tag_package_owners entry created by humaton [still
> active]
>
> Last package update on bodhi:
> 2021-02-01 13:54:59 on package perl-POE-Component-Client-Ping-1.176-
> 1.fc33
> Last actions performed according to fedmsg:
> - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-15 01:23:48
> - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-15 01:23:48
> - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-04 15:03:10
> - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-04 15:03:09
> - org.fedoraproject.prod.bugzilla.bug.update on 2021-12-13 16:34:31
> - org.fedoraproject.prod.bugzilla.bug.new on 2021-12-13 16:34:31
> - org.fedoraproject.prod.bugzilla.bug.update on 2021-12-12 02:40:57
> - org.fedoraproject.prod.bugzilla.bug.new on 2021-12-12 02:40:57
>
See https://pagure.io/find-inactive-packagers/issue/311

They will probably be removed from packagers next week.

Mattia

___
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: Non-responsive maintainer check for cottsay

2022-11-17 Thread Zbigniew Jędrzejewski-Szmek
On Thu, Nov 17, 2022 at 11:06:46AM -0500, Steven A. Falco wrote:
> The package hackrf has several open bugs [1], [2].
> 
> I've started the non-responsive maintainer process by filing [3].
> 
> I've CC'd the maintainer on this email, but if anyone knows how else to 
> contact them, please let me know.

I was just talking with him yesterday in 
https://bugzilla.redhat.com/show_bug.cgi?id=2141745.
Seems he's still active in general. [...] Oh, I see that the replies in 
#1941132.
I guess all is well then ;)

Zbyszek
___
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


Non-responsive maintainer check for jehane

2022-11-17 Thread Sérgio Basto
Almost a year later we haven't any reply 

https://bugzilla.redhat.com/show_bug.cgi?id=2031448


Marianne not have any activity since Fev 2022  (expect in a
tag_package_owners entry!?!? )

Last login in FAS:
jehane 2021-02-18

Last action on koji:
Fri, 09 Sep 2022 tag_package_owners entry created by humaton [still
active]

Last package update on bodhi:
2021-02-01 13:54:59 on package perl-POE-Component-Client-Ping-1.176-
1.fc33
Last actions performed according to fedmsg:
- org.fedoraproject.prod.bugzilla.bug.update on 2022-01-15 01:23:48
- org.fedoraproject.prod.bugzilla.bug.update on 2022-01-15 01:23:48
- org.fedoraproject.prod.bugzilla.bug.update on 2022-01-04 15:03:10
- org.fedoraproject.prod.bugzilla.bug.update on 2022-01-04 15:03:09
- org.fedoraproject.prod.bugzilla.bug.update on 2021-12-13 16:34:31
- org.fedoraproject.prod.bugzilla.bug.new on 2021-12-13 16:34:31
- org.fedoraproject.prod.bugzilla.bug.update on 2021-12-12 02:40:57
- org.fedoraproject.prod.bugzilla.bug.new on 2021-12-12 02:40:57

-- 
Sérgio M. B.
___
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


Non-responsive maintainer check for cottsay

2022-11-17 Thread Steven A. Falco

The package hackrf has several open bugs [1], [2].

I've started the non-responsive maintainer process by filing [3].

I've CC'd the maintainer on this email, but if anyone knows how else to contact 
them, please let me know.

Thanks,
Steve

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1941132
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2113439
[3] https://bugzilla.redhat.com/show_bug.cgi?id=2143712
___
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


Non-responsive maintainer check for strobert

2022-11-14 Thread Robert Scheck
Hello,

does somebody know how to contact Steven Roberts? Yes, two requests are for
EPEL 9, but I would be even happy to maintain the EPEL branch(es) myself in
case of a negative response.

 - https://bugzilla.redhat.com/show_bug.cgi?id=1974006
 - https://bugzilla.redhat.com/show_bug.cgi?id=2072993
 - https://bugzilla.redhat.com/show_bug.cgi?id=2104397

I also filed https://bugzilla.redhat.com/show_bug.cgi?id=2142700 to follow
the non-responsive maintainer policy.


Regards,
  Robert


pgpe2SLIIBchF.pgp
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


Non-responsive maintainer check for guidograzioli

2022-11-08 Thread Richard Shaw
Looking here, I don't see any activity in the last year:

https://src.fedoraproject.org/user/guidograzioli

I have not gotten any response to BZs for yaml-cpp.

Does anyone know how to contact them?

Thanks,
Richard
___
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: Non-responsive maintainer check for deji - grads

2022-11-07 Thread Mattia Verga via devel
Il 08/11/22 02:12, Orion Poplawski ha scritto:
> Non-responsive maintainer check for deji
>
> Mainly for grads:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2140875
>
> But there is also an old bug for TexMaker:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2088781
>
> Has anyone else heard from Deji?
>
> Is anyone else interested in taking over grads or TexMaker should it
> come to that?
>
> Thanks,
>
>    Orion
>
No response from Deji to the inactive packager policy ticket so far:
https://pagure.io/find-inactive-packagers/issue/554

Mattia

___
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: Non-responsive maintainer check for deji - grads

2022-11-07 Thread Jeffrey Stewart
Hello, I am interesting in maintaining this package(grads) if no one 
else will, but I require sponsorship since I am still new to this group.


On 11/7/22 17:12, Orion Poplawski wrote:

Non-responsive maintainer check for deji

Mainly for grads:

https://bugzilla.redhat.com/show_bug.cgi?id=2140875

But there is also an old bug for TexMaker:

https://bugzilla.redhat.com/show_bug.cgi?id=2088781

Has anyone else heard from Deji?

Is anyone else interested in taking over grads or TexMaker should it
come to that?

Thanks,

   Orion



___
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

___
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


Non-responsive maintainer check for deji - grads

2022-11-07 Thread Orion Poplawski
Non-responsive maintainer check for deji

Mainly for grads:

https://bugzilla.redhat.com/show_bug.cgi?id=2140875

But there is also an old bug for TexMaker:

https://bugzilla.redhat.com/show_bug.cgi?id=2088781

Has anyone else heard from Deji?

Is anyone else interested in taking over grads or TexMaker should it 
come to that?

Thanks,

  Orion



___
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


Non-responsive maintainer check for package ModemManager

2022-11-02 Thread Tao J
This is an accompanying mail for [0] in accordance with "Non-responsive 
maintainer policy"

ModemManager[1] has some abrt issues [2][3][4][5] and also need a version 
bump[6][7] to support new hardware.

A PR was sent about two months ago and no action from the maintainer. For the 
past two years, "Peter Robinson" is the sole committer to this package, while 
listed 4 maintainers has no commits.

To fix both problem A bump to version >= 1.18.12 is suggested. [8]
[0]: https://bugzilla.redhat.com/show_bug.cgi?id=2137444
[1]: https://src.fedoraproject.org/rpms/ModemManager
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=2139298
[3]: https://bugzilla.redhat.com/show_bug.cgi?id=2139291
[4]: https://bugzilla.redhat.com/show_bug.cgi?id=2139279
[5]: https://bugzilla.redhat.com/show_bug.cgi?id=2129461
[6]: 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/806
[7]: https://bugzilla.redhat.com/show_bug.cgi?id=2134227
[8]: 
https://lists.freedesktop.org/archives/modemmanager-devel/2022-September/009419.html
___
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


Non responsive maintainer check for ultrafredde

2022-10-30 Thread Ankur Sinha
Hi folks,

Would anyone know how to contact @ultrafredde please?

A new contributor opened a PR to update the task package quite a while
back, but there's been no response either on the PR or on the bug.

@ultrafredde only maintains the one package, task.

Here's the output of fedora-active-user:

$ python ./fedora_active_user.py --user ultrafredde --email 
ultrafre...@gmail.com
Last login in FAS:
   ultrafredde 2021-03-12

Last action on koji:
   Fri, 09 Sep 2022 tag_package_owners entry created by humaton [still active]

Last package update on bodhi:
   2011-03-04 01:10:36 on package task-1.9.4-1.el6
Last actions performed according to fedmsg:
  - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-05 08:09:04
  - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-05 08:09:04
  - org.fedoraproject.prod.bugzilla.bug.update on 2021-11-30 18:27:24
  - org.fedoraproject.prod.bugzilla.bug.update on 2021-11-30 18:27:24
  - org.fedoraproject.prod.bugzilla.bug.update on 2021-11-04 15:44:53
  - org.fedoraproject.prod.bugzilla.bug.update on 2021-11-04 14:46:23

Last email on mailing list:
  On 2009-09-01T13:50:04Z ultrafre...@gmail.com emailed as Federico Hernandez 
on 
https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/
  On 2009-08-24T19:35:46Z ultrafre...@gmail.com emailed as Federico Hernandez 
on 
https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/
  On 2009-07-06T20:18:57Z ultrafre...@gmail.com emailed as Federico Hernandez 
on 
https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/
  On 2009-06-20T23:20:28Z ultrafre...@gmail.com emailed as Federico Hernandez 
on 
https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/
  On 2009-06-20T22:04:29Z ultrafre...@gmail.com emailed as Federico Hernandez 
on 
https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/
  On 2009-06-09T17:38:24Z ultrafre...@gmail.com emailed as Federico Hernandez 
on 
https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/
  On 2009-06-09T17:02:02Z ultrafre...@gmail.com emailed as Federico Hernandez 
on 
https://lists.fedoraproject.org/archives/api/list/packag...@lists.fedoraproject.org/

Bugzilla activity
   2 bugs assigned, cc or on which ultrafre...@gmail.com commented
ERROR:active-user:https://bugzilla.redhat.com/docs/en/html/api/core/v1/general.html#authentication
 for details on using the 'Authorization' header. at 
/usr/share/perl5/vendor_perl/SOAP/Lite.pm line 2855.\n">


Here's the non-responsive package maintainer bug on Bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=2138642


Here are the open bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1872005
https://bugzilla.redhat.com/show_bug.cgi?id=1872005

and here is the pending PR:
https://src.fedoraproject.org/rpms/task/pull-request/1


-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


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: Non-responsive maintainer check for volter

2022-10-13 Thread Kevin Kofler via devel
Scott Talbert wrote:
> This is a non-responsive maintainer check for volter (Volker Fröhlich).
> Does anyone know how to contact this user?
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2134665

Volker basically left Fedora packaging almost a year ago:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/3QANCB2C5PLVBJD4SNQPBZQ7Q5MU2L45/#T4NT6DFNGYXB3WI6GBQOVSPC5NKQZVN6

Does the e-mail address in FAS and Bugzilla (the gmx.at one) no longer work?

I am going to ping him on IRC (volter at Libera Chat) pointing him to this 
thread, but considering the thread linked above, I think we can probably 
fast-track the orphaning.

Kevin Kofler
___
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


Non-responsive maintainer check for mikedep333

2022-10-13 Thread Scott Talbert
This is a non-responsive maintainer check for mikedep333 (Michael 
DePaulo).  Does anyone know how to contact this maintainer?


https://bugzilla.redhat.com/show_bug.cgi?id=2134659
___
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


Non-responsive maintainer check for ivazquez

2022-10-13 Thread Scott Talbert
This is a non-responsive maintainer check for ivazquez (Ignacio 
Vazquez-Abrams).  Does anyone know how to contact this user?


https://bugzilla.redhat.com/show_bug.cgi?id=2134660
___
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


Non-responsive maintainer check for volter

2022-10-13 Thread Scott Talbert
This is a non-responsive maintainer check for volter (Volker Fröhlich). 
Does anyone know how to contact this user?


https://bugzilla.redhat.com/show_bug.cgi?id=2134665___
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


Non-responsive maintainer check for wolfy

2022-10-13 Thread Scott Talbert
This a non-responsive maintainer check for wolfy (manuel wolfshant). 
Does anyone know how to contact this maintainer?


https://bugzilla.redhat.com/show_bug.cgi?id=2134664
___
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: Non-responsive maintainer check for olem

2022-09-25 Thread Robert-André Mauchin

On 9/22/22 01:10, Maxwell G wrote:

On Fri Sep 2, 2022, Maxwell G via devel wrote:


Sep 2, 2022 5:36:41 AM Fabio Valentini :


Does anybody know whether olem still wants to maintain their Fedora
packages?

I'm fairly sure that they no longer wish to maintain Fedora packages. I
reached out to them about moby-engine and containerd at the end of May,
and they said they no longer have time to maintain them. I have been
maintaining those packages myself for a while.

Side note: I have asked for co-maintainers for those packages a couple
times, but so far, I have not found any. Perhaps one of the CoreOS people
would be interested? It seems those packages are used a lot there based
on the bug reports we've gotten.


It looks like the nonresponsive maintainer process is going to proceed.
I've done some analysis of the Go packages that will be orphaned so the
Go SIG can figured out how to handle this. This was done by hand, so
please excuse any errors.

The following packages are dependencies of golang-github-docker{,-cli} and/or
containerd:

1. golang-github-hanwen-fuse
2. golang-github-fvbommel-sortorder
3. golang-github-containerd-nri
4. golang-github-moby-locker
5. golang-github-moby-term
6. golang-github-tonistiigi-rosetta
7. golang-github-google-containerregistry
8. golang-github-containerd-stargz-snapshotter (FTBFS)

9. golang-github-kyokomi-emoji is a dependency of hugo

olem also maintained open-policy-agent and some of its
dependencies:

- open-policy-agent
- golang-github-yashtewari-glob-intersection (open-policy-agent is the only 
dependent)
- golang-uber-automaxprocs (dependency of both open-policy-agent and
   clash)

This maintainer also maintained golang-github-jsonnet-bundler and
golang-github-containerd-cni. These packages are leaves. I sent a
separate message to the golang list about retiring these. I suppose we
could just wait for it to happen automatically.

Many of these libraries are out of date, but only one of them FTBFS
(according to Koschei), which I'd consider pretty good. Updating these
packages will likely require packaging a bunch of new dependencies. I
think eclipseo has been doing some work on the docker side of things,
though. Thanks for that!

I have been keeping containerd and moby-engine up to date. moby-engine
could use a cleanup. Currently, docker-proxy
(github.com/moby/libnetwork), docker-init (bundled tini-static), dockerd
(github.com/moby/moby), and the docker cli (github.com/docker/cli) are
all part of the moby-engine package. This makes the specfile rather
cumbersome. Ideally, it should be split up. I just haven't had the time
to do so. docker cli should be straightforward.
github.com/moby/libnetwork will soon be merged into
github.com/moby/moby, so docker-proxy doesn't make sense to split out
right now. For docker-init, we should investigate whether we could
configure docker to look for the existing tini-static binary or at least
create a symlink. It expects the binary to be installed to
%{_libexecdir}/docker/docker-init. I am really not a fan of the bundled
tini-static.

--
Best,

Maxwell G (@gotmax23)
Pronouns: He/Him/His


Hi,

I can take care of all the Docker deps since I am in the process of updating 
them.

Best regards,

Robert-André
___
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


Non-responsive maintainer check for Othman Madjoudj a.k.a. athmane

2022-09-24 Thread PGNet Dev

Does anyone know how to contact Othman Madjoudj a.k.a. athmane?

https://bugzilla.redhat.com/show_bug.cgi?id=2129515

Bug List, pkg libmodsecurity
ID   Status   ResolSummary  
Changed
2129515  NEW   Non-responsive maintainer check for athmane  
2022-09-24T10:19:52Z
2129200  NEW   is libmodsecurity pkg still being maintained?
2022-09-22T21:44:55Z
2128321  NEW   Please port your pcre dependency to pcre2. Pcre has 
been deprecated  2022-09-20T13:46:18Z
2113484  NEW   libmodsecurity: FTBFS in Fedora rawhidef37 
2022-08-10T23:38:43Z
1957933  CLOSED   EOL  CVE-2019-25043 libmodsecurity: crafted key-value 
pair can lead t...  2022-06-07T20:07:31Z
2031842  NEW   CVE-2021-42717 libmodsecurity: crafted JSON objects 
with nesting...  2022-01-06T06:32:29Z
2021301  NEW   CVE-2021-35368 libmodsecurity: request body bypass 
via a trailin...  2021-11-08T18:42:06Z
1879589  CLOSED   EOL  CVE-2020-15598 libmodsecurity: specially crafted 
payload could r...  2021-05-25T18:33:30Z
1801719  CLOSED   ERRATA   CVE-2019-19886 libmodsecurity: denial of service in 
Transaction:...  2020-04-06T01:05:43Z
1672678  CLOSED   RAWHIDE  libmodsecurity: update to 3.0.3 release  
2019-07-02T08:22:43Z
___
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: Non-responsive maintainer check for olem

2022-09-21 Thread Maxwell G via devel
On Fri Sep 2, 2022, Maxwell G via devel wrote:
>
> Sep 2, 2022 5:36:41 AM Fabio Valentini :
>
> > Does anybody know whether olem still wants to maintain their Fedora
> > packages?
> I'm fairly sure that they no longer wish to maintain Fedora packages. I
> reached out to them about moby-engine and containerd at the end of May,
> and they said they no longer have time to maintain them. I have been
> maintaining those packages myself for a while.
>
> Side note: I have asked for co-maintainers for those packages a couple
> times, but so far, I have not found any. Perhaps one of the CoreOS people
> would be interested? It seems those packages are used a lot there based
> on the bug reports we've gotten.

It looks like the nonresponsive maintainer process is going to proceed.
I've done some analysis of the Go packages that will be orphaned so the
Go SIG can figured out how to handle this. This was done by hand, so
please excuse any errors.

The following packages are dependencies of golang-github-docker{,-cli} and/or
containerd:

1. golang-github-hanwen-fuse
2. golang-github-fvbommel-sortorder
3. golang-github-containerd-nri
4. golang-github-moby-locker
5. golang-github-moby-term
6. golang-github-tonistiigi-rosetta
7. golang-github-google-containerregistry
8. golang-github-containerd-stargz-snapshotter (FTBFS)

9. golang-github-kyokomi-emoji is a dependency of hugo

olem also maintained open-policy-agent and some of its
dependencies:

- open-policy-agent
- golang-github-yashtewari-glob-intersection (open-policy-agent is the only 
dependent)
- golang-uber-automaxprocs (dependency of both open-policy-agent and
  clash)

This maintainer also maintained golang-github-jsonnet-bundler and
golang-github-containerd-cni. These packages are leaves. I sent a
separate message to the golang list about retiring these. I suppose we
could just wait for it to happen automatically.

Many of these libraries are out of date, but only one of them FTBFS
(according to Koschei), which I'd consider pretty good. Updating these
packages will likely require packaging a bunch of new dependencies. I
think eclipseo has been doing some work on the docker side of things,
though. Thanks for that!

I have been keeping containerd and moby-engine up to date. moby-engine
could use a cleanup. Currently, docker-proxy
(github.com/moby/libnetwork), docker-init (bundled tini-static), dockerd
(github.com/moby/moby), and the docker cli (github.com/docker/cli) are
all part of the moby-engine package. This makes the specfile rather
cumbersome. Ideally, it should be split up. I just haven't had the time
to do so. docker cli should be straightforward.
github.com/moby/libnetwork will soon be merged into
github.com/moby/moby, so docker-proxy doesn't make sense to split out
right now. For docker-init, we should investigate whether we could
configure docker to look for the existing tini-static binary or at least
create a symlink. It expects the binary to be installed to
%{_libexecdir}/docker/docker-init. I am really not a fan of the bundled
tini-static.

--
Best,

Maxwell G (@gotmax23)
Pronouns: He/Him/His
___
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: Non-responsive maintainer check for golang-github-prometheus-common-devel

2022-09-18 Thread Otto Liljalaakso
18. syyskuuta 2022 13.31.24 GMT+03:00 zebo...@gmail.com kirjoitti:
>
>I haven't seen fpokorny active even when I started working on Go
>packages. Is there a way to reallocate all is Go packages to either the
>go-sig group or myself?

According to policy, they cannot be allocated to the SIG: "SIGs cannot be 
primary maintainers, but they can be co-maintainers." [1] 

[1]: 
https://docs.fedoraproject.org/en-US/fesco/Policy_for_encouraging_comaintainers_of_packages/#_who_can_be_a_co_maintainer
___
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: Non-responsive maintainer check for golang-github-prometheus-common-devel

2022-09-18 Thread zebob . m

On 9/17/22 4:18 AM, Maxwell G via devel  wrote:

Hi Tobias,

On Fri Sep 16, 2022, Tobias Zellner wrote:
> some weeks ago I opened the bug 
https://bugzilla.redhat.com/show_bug.cgi?id=2109630

I commented on your bug and submitted a fix.

> Since there is no response to this bug, and following your guide lines 
(https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/),
 I opend Non-responsive maintainer check f a for this package

For the record, the maintainer is fpokorny.

Indeed, it seems that maintainer is unresponsive. They haven't had any
recent activity in distgit. Other Go SIG members have been maintaining
their packages for some time. They are also slated to be removed[1] from the
packager group as part of the new Inactive Packager process[2]. This
won't actually happen until the end of October, so feel free to continue
with the standard Nonresponsive Maintainer process.

[1]: https://pagure.io/find-inactive-packagers/issue/222
[2]: https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/


--
Best,

Maxwell G (@gotmax23)
Pronouns: He/Him/His


___
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



I haven't seen fpokorny active even when I started working on Go packages. Is 
there a way to reallocate all is Go packages to either the go-sig group or 
myself?

Best regards,

Robert-André
___
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: Non-responsive maintainer check for golang-github-prometheus-common-devel

2022-09-16 Thread Maxwell G via devel
Hi Tobias,

On Fri Sep 16, 2022, Tobias Zellner wrote:
> some weeks ago I opened the bug 
> https://bugzilla.redhat.com/show_bug.cgi?id=2109630

I commented on your bug and submitted a fix.

> Since there is no response to this bug, and following your guide lines 
> (https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/),
>  I opend Non-responsive maintainer check f a for this package

For the record, the maintainer is fpokorny.

Indeed, it seems that maintainer is unresponsive. They haven't had any
recent activity in distgit. Other Go SIG members have been maintaining
their packages for some time. They are also slated to be removed[1] from the
packager group as part of the new Inactive Packager process[2]. This
won't actually happen until the end of October, so feel free to continue
with the standard Nonresponsive Maintainer process.

[1]: https://pagure.io/find-inactive-packagers/issue/222
[2]: https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/


--
Best,

Maxwell G (@gotmax23)
Pronouns: He/Him/His


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


Non-responsive maintainer check for golang-github-prometheus-common-devel

2022-09-16 Thread Tobias Zellner
Hello all,

some weeks ago I opened the bug 
https://bugzilla.redhat.com/show_bug.cgi?id=2109630

Since there is no response to this bug, and following your guide lines 
(https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/),
 I opend Non-responsive maintainer check f a for this package: 
https://bugzilla.redhat.com/show_bug.cgi?id=2125873

And as requested in your guide lines as well, I send this post here.
I hope this helps to solve the issue.

Have a nice day
imker
___
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: Non-responsive maintainer check for Michal Ambroz a.k.a. rebus

2022-09-08 Thread Michal Ambroz
Hi Andy,
I am here.
Michal Ambroz
-- Původní e-mail --
Od: Mattia Verga via devel 
Komu: devel@lists.fedoraproject.org
Kopie: Mattia Verga 
Datum: 24. 8. 2022 7:46:54
Předmět: Re: Non-responsive maintainer check for Michal Ambroz a.k.a. rebus
"
Il 23/08/22 22:36, zonexpertconsult...@outlook.com
(mailto:zonexpertconsult...@outlook.com) ha scritto:

"
Does anyone know how to contact Michal Ambroz a.k.a. rebus?




https://bugzilla.redhat.com/show_bug.cgi?id=2120834
(https://bugzilla.redhat.com/show_bug.cgi?id=2120834)






This is blocking the ZoneMinder package in RPMFusion:

https://bugzilla.redhat.com/show_bug.cgi?id=2115572
(https://bugzilla.redhat.com/show_bug.cgi?id=2115572)








Thanks,
Andy





"
Accordingly to src.fp.o stats they are active:

https://src.fedoraproject.org/api/0/user/rebus/activity/stats
(https://src.fedoraproject.org/api/0/user/rebus/activity/stats)




It's August, so people could be on vacation... the relevant bug was opened
on 4th August, so a non-responsive maintainer ticket seems a bit premature
to me...




Mattia

___
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
"___
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


[Bug 2120834] Non-responsive maintainer check for rebus

2022-09-08 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2120834

Michal Ambroz  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |CURRENTRELEASE
Last Closed||2022-09-08 09:31:00



--- Comment #1 from Michal Ambroz  ---
Hello,
I agree with Andrew being assigned to comaintain the perl-Number-Bytes-Human.
Welcome to the team and thanks for help.
Michal Ambroz


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2120834
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Non-responsive maintainer check for olem

2022-09-02 Thread Maxwell G via devel
On Friday, September 2, 2022 Dusty Mabe wrote:
> > Side note: I have asked for co-maintainers for those packages a couple
> > times, but so far, I have not found any. Perhaps one of the CoreOS people
> > would be interested? It seems those packages are used a lot there based
> > on the bug reports we've gotten.
> 
> Interesting. I opened an issue for us to discuss:
> https://github.com/coreos/fedora-coreos-tracker/issues/1291

Thank you! I left to a comment to add more context.

-- 
Best,

Maxwell G (@gotmax23)
Pronouns: He/Him/His

signature.asc
Description: This is a digitally signed message part.
___
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: Non-responsive maintainer check for olem

2022-09-02 Thread Dusty Mabe


On 9/2/22 10:20, Maxwell G via devel wrote:
> 
> Sep 2, 2022 5:36:41 AM Fabio Valentini :
> 
>> Does anybody know whether olem still wants to maintain their Fedora
>> packages?
> I'm fairly sure that they no longer wish to maintain Fedora packages. I 
> reached out to them about moby-engine and containerd at the end of May, 
> and they said they no longer have time to maintain them. I have been 
> maintaining those packages myself for a while.

Thank you for doing that. I wasn't aware olem was no longer active.

> 
> Side note: I have asked for co-maintainers for those packages a couple 
> times, but so far, I have not found any. Perhaps one of the CoreOS people 
> would be interested? It seems those packages are used a lot there based 
> on the bug reports we've gotten.

Interesting. I opened an issue for us to discuss: 
https://github.com/coreos/fedora-coreos-tracker/issues/1291

Dusty
___
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: Non-responsive maintainer check for olem

2022-09-02 Thread Maxwell G via devel


Sep 2, 2022 5:36:41 AM Fabio Valentini :


Does anybody know whether olem still wants to maintain their Fedora
packages?
I'm fairly sure that they no longer wish to maintain Fedora packages. I 
reached out to them about moby-engine and containerd at the end of May, 
and they said they no longer have time to maintain them. I have been 
maintaining those packages myself for a while.


Side note: I have asked for co-maintainers for those packages a couple 
times, but so far, I have not found any. Perhaps one of the CoreOS people 
would be interested? It seems those packages are used a lot there based 
on the bug reports we've gotten.

--
Best,

Maxwell G (@gotmax23)
Pronouns: He/Him/His

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


Non-responsive maintainer check for olem

2022-09-02 Thread Fabio Valentini
Hi all,

This is the "Week 0" email to the devel list according to the
"Non-responsive maintainer policy" for "olem" / Olivier Lemasle.

Non-responsive maintainer bug:
https://bugzilla.redhat.com/show_bug.cgi?id=2123691

Their packages are in various states of disrepair, with me maintaining
any Rust packages as Rust SIG for months. Their packages are now
starting to be orphaned due to non-responsiveness even with "needinfo"
requests on FTI / FTBFS bugs:

- rust-just: FTBFS in Fedora rawhide/f37: RHBZ#2113717
- F37FailsToInstall: rust-just-devel: RHBZ#2103627
- F36FailsToInstall: rust-just-devel: RHBZ#2103776
- F35FailsToInstall: rust-just-devel: RHBZ#2103780

According to fedora-active-user, their last activity in Fedora was
over half a year ago:

python3 ./fedora_active_user.py --user olem --email o.lema...@gmail.com
FAS username: decathorpe
FAS password for decathorpe:
Last login in FAS:
   olem 2021-03-21

Last action on koji:
   Fri, 02 Sep 2022 tag_package_owners entry revoked by bodhi

Last package update on bodhi:
   2022-02-02 18:36:31 on package open-policy-agent-0.31.0-2.fc35
Last actions performed according to fedmsg:
  - Fedora 35 Update: open-policy-agent-0.31.0-2.fc35 on 2022-02-11 02:23:38
  - olem's open-policy-agent-0.31.0-2.fc35 bodhi update completed push
to stable on 2022-02-11 02:19:54
  - FEDORA-2022-7adcde1092 has met stable testing requirements on
2022-02-10 02:36:02
  - bodhi submitted FEDORA-2022-7adcde1092 to stable on 2022-02-10 02:36:02
  - olem's open-policy-agent-0.31.0-2.fc35 bodhi update completed push
to testing on 2022-02-03 02:34:10
  - Bodhi's open-policy-agent-0.31.0-2.fc35 bodhi update is ready for
testing on 2022-02-03 02:33:58
  - olem edited FEDORA-2022-7adcde1092 on 2022-02-02 19:37:46
  - olem submitted FEDORA-2022-7adcde1092 to testing on 2022-02-02 19:36:39
  - FEDORA-2022-caa8151005 has met stable testing requirements on
2022-02-02 18:09:41
  - Bodhi's open-policy-agent-0.31.0-3.fc36 bodhi update is ready for
testing on 2022-02-02 18:07:29

Last email on mailing list:
  On 2021-12-02T19:02:33Z o.lema...@gmail.com emailed as Olivier
Lemasle on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
  On 2021-06-20T13:29:55Z o.lema...@gmail.com emailed as Olivier
Lemasle on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
  On 2020-11-02T21:45:09Z o.lema...@gmail.com emailed as Olivier
Lemasle on 
https://lists.fedoraproject.org/archives/api/list/gol...@lists.fedoraproject.org/
  On 2019-07-15T14:46:11Z o.lema...@gmail.com emailed as Olivier
Lemasle on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
  On 2019-07-11T20:32:06Z o.lema...@gmail.com emailed as Olivier
Lemasle on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
  On 2017-03-06T22:22:48Z o.lema...@gmail.com emailed as Olivier
Lemasle on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/
  On 2017-03-05T23:06:33Z o.lema...@gmail.com emailed as Olivier
Lemasle on 
https://lists.fedoraproject.org/archives/api/list/devel@lists.fedoraproject.org/

Bugzilla activity
   20 bugs assigned, cc or on which o.lema...@gmail.com commented
(... fedora-active-user crashed due to the new token authentication
requirement for BugZilla ...)

Does anybody know whether olem still wants to maintain their Fedora
packages? Olivier, if you're reading this email, consider orphaning
your Rust packages so that other maintainers can pick them up and fix
them, if they want to (or let them be removed from Fedora, since
they're broken).

Fabio
___
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: Non-responsive maintainer check for Michal Ambroz a.k.a. rebus

2022-08-23 Thread Mattia Verga via devel
Il 23/08/22 22:36, zonexpertconsult...@outlook.com ha scritto:

> Does anyone know how to contact Michal Ambroz a.k.a. rebus?
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2120834
>
> This is blocking the ZoneMinder package in RPMFusion:
> https://bugzilla.redhat.com/show_bug.cgi?id=2115572
>
> Thanks,
> Andy

Accordingly to src.fp.o stats they are active:

https://src.fedoraproject.org/api/0/user/rebus/activity/stats

It's August, so people could be on vacation... the relevant bug was opened on 
4th August, so a non-responsive maintainer ticket seems a bit premature to me...

Mattia___
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


Non-responsive maintainer check for Michal Ambroz a.k.a. rebus

2022-08-23 Thread zonexpertconsulting
Does anyone know how to contact Michal Ambroz a.k.a. rebus?

https://bugzilla.redhat.com/show_bug.cgi?id=2120834

This is blocking the ZoneMinder package in RPMFusion:
https://bugzilla.redhat.com/show_bug.cgi?id=2115572


Thanks,
Andy

___
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


[Bug 2120834] Non-responsive maintainer check for rebus

2022-08-23 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2120834

Andrew Bauer  changed:

   What|Removed |Added

   Assignee|lys...@gmail.com|re...@seznam.cz
   Doc Type|--- |If docs needed, set a value
Product|Fedora  |Fedora EPEL
Version|rawhide |epel9
  Component|perl-Number-Bytes-Human |perl-Number-Bytes-Human




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2120834
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[Bug 2120834] New: Non-responsive maintainer check for rebus

2022-08-23 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2120834

Bug ID: 2120834
   Summary: Non-responsive maintainer check for rebus
   Product: Fedora
   Version: rawhide
  Hardware: All
OS: Linux
Status: NEW
 Component: perl-Number-Bytes-Human
  Severity: medium
  Priority: medium
  Assignee: lys...@gmail.com
  Reporter: zonexpertconsult...@outlook.com
QA Contact: extras...@fedoraproject.org
CC: lys...@gmail.com, m...@fabian-affolter.ch,
perl-devel@lists.fedoraproject.org, re...@seznam.cz
  Target Milestone: ---
Classification: Fedora



This bug is part of the non-responsive maintainer procedure for rebus,
following
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/.

Please respond if you are still active in Fedora and want to maintain the EPEL
branches of perl-Number-Bytes-Human.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2120834
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Non-responsive maintainer check for Igor Raits (ignatenkobrain)

2022-08-12 Thread Fabio Valentini
On Fri, Aug 12, 2022 at 6:12 PM Ben Beasley  wrote:
>

(snip)

> rust-abomonation: sole maintainer (with @rust-sig); CVE bug ignored for
> eight months: https://bugzilla.redhat.com/show_bug.cgi?id=2039788
>
> rust-brotli-sys: primary maintainer; CVE bug ignored for eight months:
> https://bugzilla.redhat.com/show_bug.cgi?id=2034890
>
> rust-nix: sole maintainer (with @rust-sig); CVE bug ignored for seven
> months: https://bugzilla.redhat.com/show_bug.cgi?id=2039785
>
> (I have omitted bug reports for Rust packages that are merely
> out-of-date since these are often updated by SIG members rather than
> individual maintainers.)

I actually had those CVE bugs on my radar, but didn't have the time to
do a full investigation.
I've closed the first two, since they actually can no longer affect
any Fedora packages (no application depends on the problematic crates,
or they don't enable the affected features).

The third one could only have affected some really old builds on
Fedora 35, since rust-nix had been updated for that CVE problem some
time before the Fedora 36 mass rebuild. And the f35 packages that I
spot checked had all been rebuilt for some reason or updated at some
point, so none of them were affected, either. And even if some package
that I happened to miss had its last build at the Fedora 35 mass
rebuild, it is unlikely that it actually used the affected API.

Fabio
___
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


Non-responsive maintainer check for Igor Raits (ignatenkobrain)

2022-08-12 Thread Ben Beasley
I have opened a bug on python-parameterized, 
https://bugzilla.redhat.com/show_bug.cgi?id=2117916, initiating a 
non-responsive maintainer check for Igor Raits, FAS ignatenkobrain. Does 
anybody know how to contact Igor, or whether they are still actively 
maintaining Fedora packages? I have sent an email to the email address 
listed at https://accounts.fedoraproject.org/user/ignatenkobrain/.


It looks like Igor’s last login in FAS was 2021-03-31, and their last 
package update in Bodhi was 2022-06-18. On 
https://src.fedoraproject.org/user/ignatenkobrain, the last activity was 
in mid-June. This would not be too concerning by itself, except that 
Igor is primary or sole maintainer on a large number of packages, many 
of which need attention.


Igor, if this message reaches you, I value and appreciate your 
significant contributions to Fedora. It seems like your time for package 
maintenance is oversubscribed. Please consider identifying packages that 
you don’t have time to take care of—especially those without other 
active maintainers—and either orphaning them or soliciting new 
co-maintainers.


As recommended by 
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/#steps, 
I am including links to other bug reports on apparently-neglected 
packages. I apologize in advance for any errors or omissions in this 
list, which was tabulated by hand.


– Ben Beasley



angelscript: sole maintainer, new version available for almost three 
years: https://bugzilla.redhat.com/show_bug.cgi?id=1754292


ansible-collection-ansible-netcommon: sole maintainer (plus @infra-sig): 
new major version available 
(https://bugzilla.redhat.com/show_bug.cgi?id=2089526), PRs to update 
minor releases in old major version ignored for three months 
(https://src.fedoraproject.org/rpms/ansible-collection-ansible-netcommon/pull-request/4, 
https://src.fedoraproject.org/rpms/ansible-collection-ansible-netcommon/pull-request/5), 
EPEL9 branch request ignored 
(https://bugzilla.redhat.com/show_bug.cgi?id=2033029).


cln: primary maintainer, new version available for over two years: 
https://bugzilla.redhat.com/show_bug.cgi?id=1773485, PR ignore for four 
months: https://src.fedoraproject.org/rpms/cln/pull-request/1


colm: primary maintainer, new version available for over two years: 
https://bugzilla.redhat.com/show_bug.cgi?id=1825150


cppcodec: sole maintainer, FTBFS since F36: 
https://bugzilla.redhat.com/show_bug.cgi?id=2045280


eegdev: sole maintainer, FTBFS since F36: 
https://bugzilla.redhat.com/show_bug.cgi?id=2045334, PR ignored for two 
years: https://src.fedoraproject.org/rpms/eegdev/pull-request/1#


eegview: sole maintainer, PR ignored for two years: 
https://src.fedoraproject.org/rpms/eegview/pull-request/1


git-archive-all: sole maintainer, new version available for over two 
years: https://bugzilla.redhat.com/show_bug.cgi?id=1771112


git-fame: primary maintainer, new version available for two years: 
https://bugzilla.redhat.com/show_bug.cgi?id=1853884


jwn: sole maintainer, new version available for nine months: 
https://bugzilla.redhat.com/show_bug.cgi?id=2021057, PR’s ignored for 
two years: https://src.fedoraproject.org/rpms/jwm/pull-request/2, 
https://src.fedoraproject.org/rpms/jwm/pull-request/1


kyua: primary maintainer, PR ignored for a year with multiple status 
checks: https://src.fedoraproject.org/rpms/kyua/pull-request/1


libgit2: primary maintainer; update available for six months, no 
response to NEEDINFOs: https://bugzilla.redhat.com/show_bug.cgi?id=2054093


libnitrokey: sole maintainer; FTBFS since F36: 
https://bugzilla.redhat.com/show_bug.cgi?id=2045819; update available 
for two years: https://bugzilla.redhat.com/show_bug.cgi?id=1870893


libxml2: primary maintainer; multilib conflict bug open without response 
for four months: https://bugzilla.redhat.com/show_bug.cgi?id=2071836


mcpanel: sole maintainer; new version available for over two years: 
https://bugzilla.redhat.com/show_bug.cgi?id=1795359


nitrokey-app: sole maintainer; new version available for two years: 
https://bugzilla.redhat.com/show_bug.cgi?id=1856549


parzip: sole maintainer; new version available for three years: 
https://bugzilla.redhat.com/show_bug.cgi?id=1718070


protobuf-c: primary maintainer; new version available for a year: 
https://bugzilla.redhat.com/show_bug.cgi?id=1961967


python-aiofiles: sole maintainer; new version available for nine months: 
https://bugzilla.redhat.com/show_bug.cgi?id=2027053


python-aiohttp-socks: primary maintainer; new version available for over 
a year: https://bugzilla.redhat.com/show_bug.cgi?id=2025292; no response 
to NEEDINFO and PR 
(https://src.fedoraproject.org/rpms/python-aiohttp-socks/pull-request/4) 
for 20+ days


python-argopt: sole maintainer; new version available for over three 
years: https://bugzilla.redhat.com/show_bug.cgi?id=1697394


python-arpy: primary maintainer; new version available

Non-responsive maintainer check for dbruno

2022-08-08 Thread Robby Callicotte via devel
Hello,

Per the unresponsive package maintainer policy, I am checking if anyone has a 
way to contact Daniel Bruno , fas ID: dbruno.

Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=2116543


# Fedora Active User data: #
Last action on koji:
   Wed, 22 Jun 2022 tag_package_owners entry revoked by bodhi

Last package update on bodhi:
   2017-05-08 16:19:23 on package python-libcloud-2.0.0-1.fc24

Last actions performed according to fedmsg:
  - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-17 01:14:52
  - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-17 01:14:22
  - org.fedoraproject.prod.bugzilla.bug.new on 2022-01-17 01:14:22
  - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-05 16:07:49
  - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-05 16:03:42
  - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-05 16:03:42
  - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-05 16:03:42
  - org.fedoraproject.prod.bugzilla.bug.update on 2022-01-05 16:03:42
  - org.fedoraproject.prod.bugzilla.bug.update on 2021-12-10 03:00:12
  - org.fedoraproject.prod.bugzilla.bug.update on 2021-12-10 02:57:09

Last email on mailing list:
  On 2017-05-09T16:37:16Z dbr...@fedoraproject.org emailed as Daniel Bruno on 
https://lists.fedoraproject.org/archives/api/list/embajadores-fedora-la...@lists.fedoraproject.org/
  On 2017-05-09T12:34:54Z dbr...@fedoraproject.org emailed as Daniel Bruno on 
https://lists.fedoraproject.org/archives/api/list/embajadores-fedora-la...@lists.fedoraproject.org/
  On 2017-02-02T05:13:09Z dbr...@fedoraproject.org emailed as Daniel Bruno on 
https://lists.fedoraproject.org/archives/api/list/embajadores-fedora-la...@lists.fedoraproject.org/
  On 2016-09-14T17:39:56Z dbr...@fedoraproject.org emailed as Daniel Bruno on 
https://lists.fedoraproject.org/archives/api/list/fama-ment...@lists.fedoraproject.org/
  On 2016-06-10T14:57:18Z dbr...@fedoraproject.org emailed as Daniel Bruno on 
https://lists.fedoraproject.org/archives/api/list/brasil-market...@lists.fedoraproject.org/
  On 2016-06-09T15:38:49Z dbr...@fedoraproject.org emailed as Daniel Bruno on 
https://lists.fedoraproject.org/archives/api/list/embajadores-fedora-la...@lists.fedoraproject.org/
  On 2016-04-14T04:42:15Z dbr...@fedoraproject.org emailed as Daniel Bruno on 
https://lists.fedoraproject.org/archives/api/list/brasil-market...@lists.fedoraproject.org/
  On 2016-04-07T23:22:28Z dbr...@fedoraproject.org emailed as Daniel Bruno on 
https://lists.fedoraproject.org/archives/api/list/brasil-market...@lists.fedoraproject.org/
  On 2016-03-09T14:24:42Z dbr...@fedoraproject.org emailed as Daniel Bruno on 
https://lists.fedoraproject.org/archives/api/list/embajadores-fedora-la...@lists.fedoraproject.org/
  On 2016-02-12T18:17:12Z dbr...@fedoraproject.org emailed as Daniel Bruno on 
https://lists.fedoraproject.org/archives/api/list/
infrastruct...@lists.fedoraproject.org/

Bugzilla activity
   19 bugs assigned, cc or on which dbr...@fedoraproject.org commented

Regards,

-- 
Robby Callicotte
He/His
Timezone: US/Central

___
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: Non-responsive maintainer check for hguemar

2022-08-08 Thread Haïkel
Hi,

send me your FAS account and I'll transfer ownership to you of pyperclip.
You're welcome to contact me directly through email (I'm currently in
sick leave but I'll browse email from time to time).

Regards,
H.
___
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


Non-responsive maintainer check for hguemar

2022-08-07 Thread Jonathan Wright via devel
Per the unresponsive package maintainer policy I'm checking if anyone has a
way to contact  Haïkel Guémar  (FAS hguemar).

https://bugzilla.redhat.com/show_bug.cgi?id=2116206

Lack of updates to one of his packages, python-pyperclip is holding up
other packages.

https://bugzilla.redhat.com/show_bug.cgi?id=1887119

LinkedIn lists him as a RH employee.  Would anyone have his @redhat.com
address by chance?

-- 
Jonathan Wright
AlmaLinux Foundation
Mattermost: chat 
___
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


  1   2   3   4   5   6   7   8   9   >