xdaliclock (was: Re: Orphaned packages looking for new maintainers)

2026-05-05 Thread Richard W.M. Jones 
On Sun, May 03, 2026 at 11:04:44PM +, Packaging Reports via devel-announce 
wrote:
> xdaliclockorphan   1 weeks 
> ago  

I took this.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
nbdkit - Flexible, fast NBD server with plugins
https://gitlab.com/nbdkit/nbdkit

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-05-04 Thread Michael J Gruber 
Packaging Reports via devel-announce venit, vidit, dixit 2026-05-04 01:04:44:
> Report started at 2026-05-03 22:00:54 UTC
> 
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
...
> dex-autostart orphan   2 weeks 
> ago  

I've taken this one. If there's a regular user of this who wishes to
maintain or co-maintain it - please speak up :)

I seem to remember that the sway spin uses this (and I always planned to
incorporate it in my sway config). While these reports list dependent
packages, is there a way they could check for dependent spins, too?
Otherwise leaf packages could go missing.

Also, first thing I check is why a package got orphaned[*]. A short version
is on pagure/dist-git, so maybe ... ;-)

Cheers
Michael

[*] "Don't use it any more." in this case; next thing to check was latest
builds (built), bugs (none) and upstream (kinda alive, it's just a py
script), but with orphan reasons like "upstream dead for 5 years" or
such I don't even check these.
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-05-01 Thread Artur Frenszek-Iwicki 
> > Can someone be going to take overship for this (gtk2)?
>
> The package has 5 people will commit access, but if none of them
> want to take it over, then I could do it.

It's been over a week since my previous message and gtk2 is still
orphaned, so I decided to bite the bullet and adopt the package.

Cheers,
Artur FI
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-04-24 Thread Nicolas Chauvet 
Le mar. 21 avr. 2026 à 20:15, Packaging Reports
 a écrit :
>
> Report started at 2026-04-21 18:00:33 UTC
>
...
> Depending on: cryptopp (3), status change: 2026-04-02 (2 weeks ago)
> clementine (maintained by: yselkowitz)
> clementine-1.4.1-10.fc44.src requires pkgconfig(libcryptopp) 
> = 8.8
>
> cryfs (maintained by: thunderbirdtr)
> cryfs-0.11.3-15.fc44.src requires cryptopp-devel = 
> 8.8.0-11.fc44
>
> tegrarcm (maintained by: jkastner, kwizart)
> tegrarcm-1.9-1.fc45.src requires pkgconfig(libcryptopp) = 8.8
> tegrarcm-1.9-1.fc45.x86_64 requires libcryptopp.so.8()(64bit)
>
I've taken cryptopp, needed by tegrarcm. However I wonder if tegrarcm
can learn to use another crypto library.
If done, I will likely re-orphan cryptopp.
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-04-23 Thread Remi Collet 

Le 21/04/2026 à 20:15, Packaging Reports via devel-announce a écrit :

The following packages require above mentioned packages:
Depending on: botan2 (4), status change: 2026-04-17 (0 weeks ago)
rnp (maintained by: remi)
librnp-0.18.1-3.fc44.x86_64 requires libbotan-2.so.19()(64bit)
rnp-0.18.1-3.fc44.src requires pkgconfig(botan-2) = 2.19.5


rnp now uses botan3 (libbotan-3.so.11()(64bit))


Cheers,
Remi

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-04-23 Thread Orion Poplawski 

On 4/21/26 12:15, Packaging Reports wrote:

Report started at 2026-04-21 18:00:33 UTC

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.

Request package ownership via the *Take* button in the left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://a.gtmx.me/orphans/orphans.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan

 Package  (co)maintainers   Status 
Change




gtk2  alexl, mkasik, orphan,   0 weeks ago



The following packages require above mentioned packages:




garcon (maintained by: kevin, nonamedotc, orion)
garcon-devel-4.20.0-4.fc44.i686 requires gtk2-devel = 
2.24.33-26.fc45
garcon-devel-4.20.0-4.fc44.x86_64 requires gtk2-devel = 
2.24.33-26.fc45


This is a mistake, fixed by 
https://src.fedoraproject.org/rpms/garcon/pull-request/2



libxfce4ui (maintained by: kevin, nonamedotc, orion)
libxfce4ui-4.20.2-2.fc44.src requires pkgconfig(gtk+-2.0) = 
2.24.33
libxfce4ui-devel-4.20.2-2.fc44.i686 requires gtk2-devel = 
2.24.33-26.fc45
libxfce4ui-devel-4.20.2-2.fc44.x86_64 requires gtk2-devel = 
2.24.33-26.fc45


This is a mistake, fixed by 
https://src.fedoraproject.org/rpms/libxfce4ui/pull-request/1


--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   [email protected]
Boulder, CO 80301 https://www.nwra.com/
--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-04-23 Thread Dan Horák 
On Thu, 23 Apr 2026 21:01:34 +0900
Mamoru TASAKA  wrote:

> Packaging Reports wrote on 2026/04/22 3:15:
> > Report started at 2026-04-21 18:00:33 UTC
> > 
> > The following packages are orphaned and will be retired when they
> > are orphaned for six weeks, unless someone adopts them. If you know for sure
> > that the package should be retired, please do so now with a proper reason:
> > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> > 
> 
> > 
> >  Package  (co)maintainers   Status 
> > Change
> > 
> > gtk2  alexl, mkasik, orphan,   0 weeks 
> > ago
> >rhughes, rstrode, tdawson
> 
> 
> This is going to affect many packages / packagers.
> Can someone be going to take overship for this (gtk2)?

I think this is also an opportunity to review if the dependency is
still valid. And it wasn't eg. for xfburn.


Dan
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-04-23 Thread Artur Frenszek-Iwicki 
> Can someone be going to take overship for this (gtk2)?
The package has 5 people will commit access, but if none of them
want to take it over, then I could do it.

Artur FI
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-04-23 Thread Mamoru TASAKA 

Packaging Reports wrote on 2026/04/22 3:15:

Report started at 2026-04-21 18:00:33 UTC

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life





 Package  (co)maintainers   Status 
Change

gtk2  alexl, mkasik, orphan,   0 weeks ago
   rhughes, rstrode, tdawson



This is going to affect many packages / packagers.
Can someone be going to take overship for this (gtk2)?

Regards,
Mamoru
--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-04-23 Thread Wolfgang 

Am 21.04.26 um 20:15 schrieb Packaging Reports:

mate-themes (maintained by: raveit65, robert)
mate-themes-3.22.26-9.fc44.src requires gtk2-devel = 
2.24.33-26.fc45


Hi,

fixed by https://koji.fedoraproject.org/koji/buildinfo?buildID=2985499

I removed all build and runtime requires to gtk2-devel, 
gdk-pixbuf2-devel and gtk2-engines for f45.



cheers

Wolfgang



OpenPGP_0x0C0B57D962C87B8D.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-04-09 Thread Peter Lemenkov 
Hello!
Taking asterisk. Co-maintainers are welcome!



-- 
With best regards, Peter Lemenkov.
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: coccinelle, ocaml-pcre (was: Re: Orphaned packages looking for new maintainers)

2026-03-25 Thread Richard W.M. Jones 
On Wed, Mar 25, 2026 at 11:34:17AM +, Richard W.M. Jones wrote:
> 
> This change should remove the coccinelle -> ocaml-pcre build
> dependency, replacing it with ocaml-pcre2:
> 
> https://src.fedoraproject.org/rpms/coccinelle/c/01d156529f3c6b695d3dc84f99b1919f40c6186d?branch=rawhide
> https://koji.fedoraproject.org/koji/taskinfo?taskID=143674379

Fixed the hevea dependency, so now coccinelle builds successfully:

https://koji.fedoraproject.org/koji/taskinfo?taskID=143675848

Rich.

> Thanks Olaf for the upstream work.
> 
> Rich.
> 
> -- 
> 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

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: coccinelle, ocaml-pcre (was: Re: Orphaned packages looking for new maintainers)

2026-03-25 Thread Richard W.M. Jones 

This change should remove the coccinelle -> ocaml-pcre build
dependency, replacing it with ocaml-pcre2:

https://src.fedoraproject.org/rpms/coccinelle/c/01d156529f3c6b695d3dc84f99b1919f40c6186d?branch=rawhide
https://koji.fedoraproject.org/koji/taskinfo?taskID=143674379

Thanks Olaf for the upstream work.

Rich.

-- 
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 -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: coccinelle, ocaml-pcre (was: Re: Orphaned packages looking for new maintainers)

2026-03-25 Thread Richard W.M. Jones 
On Tue, Mar 24, 2026 at 08:39:48PM +0100, Olaf Hering wrote:
> Tue, 24 Mar 2026 18:43:22 + "Richard W.M. Jones" :
> 
> > I can't find that commit...  Did upstream git change (from
> > https://github.com/coccinelle/coccinelle)?
> 
> The primary source is probably 
> https://gitlab.inria.fr/coccinelle/coccinelle.git

That was not obvious from their webpages which all point to github!

I have found your commits there so we can take these in Fedora.

Thanks,

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
nbdkit - Flexible, fast NBD server with plugins
https://gitlab.com/nbdkit/nbdkit

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: coccinelle, ocaml-pcre (was: Re: Orphaned packages looking for new maintainers)

2026-03-24 Thread Olaf Hering via devel 
Tue, 24 Mar 2026 18:43:22 + "Richard W.M. Jones" :

> I can't find that commit...  Did upstream git change (from
> https://github.com/coccinelle/coccinelle)?

The primary source is probably https://gitlab.inria.fr/coccinelle/coccinelle.git


Olaf


pgpUFeivZhzfm.pgp
Description: Digitale Signatur von OpenPGP
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: coccinelle, ocaml-pcre (was: Re: Orphaned packages looking for new maintainers)

2026-03-24 Thread Richard W.M. Jones 
On Tue, Mar 24, 2026 at 07:20:31PM +0100, Olaf Hering wrote:
> Tue, 24 Mar 2026 16:44:25 + "Richard W.M. Jones" :
> 
> > However it didn't appear to go anywhere and I don't find anything else
> > upstream.
> 
> This was applied upstream as 0af334383425b4de18f1d9a087e38838c75c2c4d
> and the following commits to the master branch.

I can't find that commit...  Did upstream git change (from
https://github.com/coccinelle/coccinelle)?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: coccinelle, ocaml-pcre (was: Re: Orphaned packages looking for new maintainers)

2026-03-24 Thread Olaf Hering via devel 
Tue, 24 Mar 2026 16:44:25 + "Richard W.M. Jones" :

> However it didn't appear to go anywhere and I don't find anything else
> upstream.

This was applied upstream as 0af334383425b4de18f1d9a087e38838c75c2c4d
and the following commits to the master branch.


Olaf


pgpAexxt5RyaJ.pgp
Description: Digitale Signatur von OpenPGP
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: coccinelle, ocaml-pcre (was: Re: Orphaned packages looking for new maintainers)

2026-03-24 Thread Richard W.M. Jones 
On Tue, Mar 24, 2026 at 10:34:05AM -0600, Jerry James wrote:
> On Tue, Mar 24, 2026 at 10:11 AM Richard W.M. Jones  wrote:
> > There's an alternate project called (upstream) pcre2-ocaml:
> >
> >   https://github.com/mmottl/pcre2-ocaml
> >
> > Or maybe it's this one:
> >
> >   https://github.com/camlp5/pcre2-ocaml
> >
> > I don't know which is the official one?!
> 
> The second one, I believe.  We have it in Fedora as ocaml-pcre2.

Oh, so we do, and I even rebuilt it only a few weeks ago :-)

For cocci, Olaf Hering proposed this for pcre2 support about a year ago:

  https://sympa.inria.fr/sympa/arc/cocci/2025-03/msg00161.html

However it didn't appear to go anywhere and I don't find anything else
upstream.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: coccinelle, ocaml-pcre (was: Re: Orphaned packages looking for new maintainers)

2026-03-24 Thread Jerry James 
On Tue, Mar 24, 2026 at 10:11 AM Richard W.M. Jones  wrote:
> There's an alternate project called (upstream) pcre2-ocaml:
>
>   https://github.com/mmottl/pcre2-ocaml
>
> Or maybe it's this one:
>
>   https://github.com/camlp5/pcre2-ocaml
>
> I don't know which is the official one?!

The second one, I believe.  We have it in Fedora as ocaml-pcre2.
-- 
Jerry James
http://www.jamezone.org/
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-03-24 Thread Jerry James 
On Tue, Mar 24, 2026 at 9:34 AM Packaging Reports
 wrote:
> Report started at 2026-03-24 15:00:07 UTC
>
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please do so now with a proper reason:
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

[snip]

> pcre  @db-sig, lkundrak, orphan,   4 weeks ago

There are still a number of packages that depend on pcre.  These are
the direct dependencies:

adanaxisgpl
aircrack-ng
ccze
coccinelle
ghc-pcre-light
ghc-regex-pcre
kdelibs
kdelibs3
kf5-kjs
mod_auth_openid
monotone
ocaml-pcre
opensips
pads
powwow
proxysql
python-qutepart
sslh
tinyfugue
trafficserver
vdr-epgfixer
xgrep

What worries me more are the indirect dependencies, though.  For
example, coccinelle depends on ocaml-pcre, and I understand that the
kernel developers use coccinelle.  Plus, kdelibs and kdelibs3 are in
that list.  That seems worrisome as well.
-- 
Jerry James
http://www.jamezone.org/
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

coccinelle, ocaml-pcre (was: Re: Orphaned packages looking for new maintainers)

2026-03-24 Thread Richard W.M. Jones 
On Tue, Mar 24, 2026 at 03:34:10PM +, Packaging Reports wrote:
> Report started at 2026-03-24 15:00:07 UTC

>   ocaml-pcre (maintained by: rjones)
>   ocaml-pcre-8.0.5-4.fc45.src requires pcre-devel = 8.45-1.fc43.9
>   ocaml-pcre-8.0.5-4.fc45.x86_64 requires libpcre.so.1()(64bit)
>   ocaml-pcre-devel-8.0.5-4.fc45.x86_64 requires 
> pcre-devel(x86-64) = 8.45-1.fc43.9

There's an alternate project called (upstream) pcre2-ocaml:

  https://github.com/mmottl/pcre2-ocaml

Or maybe it's this one:

  https://github.com/camlp5/pcre2-ocaml

I don't know which is the official one?!

Since ocaml-pcre is a dead end, I wonder if we want to start up a new
Fedora package, or just reuse ocaml-pcre.  Unfortunately version
numbers are earlier so we'd need to use Epoch.

Thoughts?

>   coccinelle (maintained by: rjones)
>   coccinelle-1.3.1-5.fc45.x86_64 requires libpcre.so.1()(64bit)

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

There are mailing list patches to make coccinelle use pcre2, but they
don't appear to be included in coccinelle itself yet.

> rjones: pcre, nvml, jdependency

We removed the dep from qemu -> nvml a week or two ago.  I'm not sure
what jdependency refers to here.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-03-24 Thread Daniel P . Berrangé 
On Tue, Mar 24, 2026 at 03:34:10PM +, Packaging Reports wrote:
> Report started at 2026-03-24 15:00:07 UTC
> 
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please do so now with a proper reason:
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> 
> Note: If you received this mail directly you (co)maintain one of the affected
> packages or a package that depends on one. Please adopt the affected package 
> or
> retire your depending package to avoid broken dependencies, otherwise your
> package will be retired when the affected package gets retired.
> 
> Request package ownership via the *Take* button in the left column on
> https://src.fedoraproject.org/rpms/
> 
> Full report available at:
> https://a.gtmx.me/orphans/orphans.txt
> grep it for your FAS username and follow the dependency chain.
> 
> For human readable dependency chains,
> see https://packager-dashboard.fedoraproject.org/
> For all orphaned packages,
> see https://packager-dashboard.fedoraproject.org/orphan

...snip...

>   glibc (maintained by: codonell, djdelorie, fberat, fweimer, josmyers, 
> mcermak, mfabian, pfrankli, siddhesh, submachine)
>   glibc-2.43.9000-4.fc45.src requires systemtap-sdt-devel = 
> 5.4-3.fc44

Loosing glibc through a long orphaned deps chain feels sub-optimal
for the future success of Fedora !

IIUC, the full chain is

  glibc -> systemtap -> byteman -> maven-shade-plugin -> jdependency

With regards,
Daniel
-- 
|: https://berrange.com   ~~https://hachyderm.io/@berrange :|
|: https://libvirt.org  ~~  https://entangle-photo.org :|
|: https://pixelfed.art/berrange   ~~https://fstop138.berrange.com :|

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-03-09 Thread Richard W.M. Jones 
On Mon, Mar 09, 2026 at 05:32:43PM +0100, Fabio Valentini wrote:
> On Mon, Mar 9, 2026 at 5:28 PM Richard W.M. Jones  wrote:
> >
> > On Mon, Mar 09, 2026 at 03:58:04PM +, Richard W.M. Jones wrote:
> > > On Mon, Mar 09, 2026 at 02:59:30PM +, Packaging Reports wrote:
> > > > Depending on: nvml (45), status change: 2026-02-18 (2 weeks ago)
> > > ...
> > > > qemu (maintained by: @virtmaint-sig, berrange, bonzini, crobinso, 
> > > > mcascella, rjones)
> > > > qemu-2:10.2.0-8.fc44.src requires libpmem-devel = 
> > > > 2.1.0-5.fc44, librbd-devel = 2:20.2.0-9.fc45
> > > ...
> > > > libvirt (maintained by: @virtmaint-sig, berrange, crobinso, laine)
> > > > libvirt-daemon-driver-storage-rbd-12.1.0-1.fc45.x86_64 
> > > > requires librados.so.2()(64bit), librados.so.2(LIBRADOS_14.2.0)(64bit), 
> > > > librbd.so.1()(64bit)
> > > > libvirt-daemon-driver-qemu-12.1.0-1.fc45.x86_64 requires 
> > > > /usr/bin/qemu-img
> > > > libvirt-daemon-driver-storage-core-12.1.0-1.fc45.x86_64 
> > > > requires /usr/bin/qemu-img
> > > > libvirt-daemon-kvm-12.1.0-1.fc45.x86_64 requires qemu-kvm = 
> > > > 2:10.2.0-8.fc44
> > > > libvirt-daemon-qemu-12.1.0-1.fc45.x86_64 requires qemu = 
> > > > 2:10.2.0-8.fc44
> > >
> > > We'll have to turn off libpmem support in qemu.  Not sure if anyone
> > > has ever used that.
> >
> > https://src.fedoraproject.org/rpms/qemu/pull-request/96
> 
> Well you don't have to drop support for it immediately ...
> The package will only be retired from Fedora Rawhide / F45+ if no new
> maintainer is found in the next ~4 weeks.

That change got merged straight away.  As I understand it, this qemu
feature emulates Optane hardware, which is of course no longer
manufactured and wasn't very popular outside some niches.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
nbdkit - Flexible, fast NBD server with plugins
https://gitlab.com/nbdkit/nbdkit

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-03-09 Thread Fabio Valentini 
On Mon, Mar 9, 2026 at 5:28 PM Richard W.M. Jones  wrote:
>
> On Mon, Mar 09, 2026 at 03:58:04PM +, Richard W.M. Jones wrote:
> > On Mon, Mar 09, 2026 at 02:59:30PM +, Packaging Reports wrote:
> > > Depending on: nvml (45), status change: 2026-02-18 (2 weeks ago)
> > ...
> > > qemu (maintained by: @virtmaint-sig, berrange, bonzini, crobinso, 
> > > mcascella, rjones)
> > > qemu-2:10.2.0-8.fc44.src requires libpmem-devel = 
> > > 2.1.0-5.fc44, librbd-devel = 2:20.2.0-9.fc45
> > ...
> > > libvirt (maintained by: @virtmaint-sig, berrange, crobinso, laine)
> > > libvirt-daemon-driver-storage-rbd-12.1.0-1.fc45.x86_64 
> > > requires librados.so.2()(64bit), librados.so.2(LIBRADOS_14.2.0)(64bit), 
> > > librbd.so.1()(64bit)
> > > libvirt-daemon-driver-qemu-12.1.0-1.fc45.x86_64 requires 
> > > /usr/bin/qemu-img
> > > libvirt-daemon-driver-storage-core-12.1.0-1.fc45.x86_64 
> > > requires /usr/bin/qemu-img
> > > libvirt-daemon-kvm-12.1.0-1.fc45.x86_64 requires qemu-kvm = 
> > > 2:10.2.0-8.fc44
> > > libvirt-daemon-qemu-12.1.0-1.fc45.x86_64 requires qemu = 
> > > 2:10.2.0-8.fc44
> >
> > We'll have to turn off libpmem support in qemu.  Not sure if anyone
> > has ever used that.
>
> https://src.fedoraproject.org/rpms/qemu/pull-request/96

Well you don't have to drop support for it immediately ...
The package will only be retired from Fedora Rawhide / F45+ if no new
maintainer is found in the next ~4 weeks.

Fabio
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-03-09 Thread Richard W.M. Jones 
On Mon, Mar 09, 2026 at 03:58:04PM +, Richard W.M. Jones wrote:
> On Mon, Mar 09, 2026 at 02:59:30PM +, Packaging Reports wrote:
> > Depending on: nvml (45), status change: 2026-02-18 (2 weeks ago)
> ...
> > qemu (maintained by: @virtmaint-sig, berrange, bonzini, crobinso, 
> > mcascella, rjones)
> > qemu-2:10.2.0-8.fc44.src requires libpmem-devel = 2.1.0-5.fc44, 
> > librbd-devel = 2:20.2.0-9.fc45
> ...
> > libvirt (maintained by: @virtmaint-sig, berrange, crobinso, laine)
> > libvirt-daemon-driver-storage-rbd-12.1.0-1.fc45.x86_64 requires 
> > librados.so.2()(64bit), librados.so.2(LIBRADOS_14.2.0)(64bit), 
> > librbd.so.1()(64bit)
> > libvirt-daemon-driver-qemu-12.1.0-1.fc45.x86_64 requires 
> > /usr/bin/qemu-img
> > libvirt-daemon-driver-storage-core-12.1.0-1.fc45.x86_64 
> > requires /usr/bin/qemu-img
> > libvirt-daemon-kvm-12.1.0-1.fc45.x86_64 requires qemu-kvm = 
> > 2:10.2.0-8.fc44
> > libvirt-daemon-qemu-12.1.0-1.fc45.x86_64 requires qemu = 
> > 2:10.2.0-8.fc44
> 
> We'll have to turn off libpmem support in qemu.  Not sure if anyone
> has ever used that.

https://src.fedoraproject.org/rpms/qemu/pull-request/96

Rich.

-- 
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 -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-03-09 Thread Richard W.M. Jones 
On Mon, Mar 09, 2026 at 02:59:30PM +, Packaging Reports wrote:
> Depending on: nvml (45), status change: 2026-02-18 (2 weeks ago)
...
>   qemu (maintained by: @virtmaint-sig, berrange, bonzini, crobinso, 
> mcascella, rjones)
>   qemu-2:10.2.0-8.fc44.src requires libpmem-devel = 2.1.0-5.fc44, 
> librbd-devel = 2:20.2.0-9.fc45
...
>   libvirt (maintained by: @virtmaint-sig, berrange, crobinso, laine)
>   libvirt-daemon-driver-storage-rbd-12.1.0-1.fc45.x86_64 requires 
> librados.so.2()(64bit), librados.so.2(LIBRADOS_14.2.0)(64bit), 
> librbd.so.1()(64bit)
>   libvirt-daemon-driver-qemu-12.1.0-1.fc45.x86_64 requires 
> /usr/bin/qemu-img
>   libvirt-daemon-driver-storage-core-12.1.0-1.fc45.x86_64 
> requires /usr/bin/qemu-img
>   libvirt-daemon-kvm-12.1.0-1.fc45.x86_64 requires qemu-kvm = 
> 2:10.2.0-8.fc44
>   libvirt-daemon-qemu-12.1.0-1.fc45.x86_64 requires qemu = 
> 2:10.2.0-8.fc44

We'll have to turn off libpmem support in qemu.  Not sure if anyone
has ever used that.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
nbdkit - Flexible, fast NBD server with plugins
https://gitlab.com/nbdkit/nbdkit

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-03-09 Thread Ankur Sinha 
> python-cro@neuro-sig, orphan   0 weeks 
> ago  

Removed neuro-sig from here.

-- 
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 -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-01-28 Thread Maxwell G 

On 1/28/26 11:50 AM, Packaging Reports via devel-announce wrote:

rust-rand_regex   @rust-sig, orphan6 weeks ago


By the way, this package has already been retired. See 
.

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://forge.fedoraproject.org/infra/tickets/issues/new

Re: Orphaned packages looking for new maintainers

2026-01-28 Thread Gwyn Ciesla via devel 
I've taken bluprint-compiler, comaintainers welcome.



-- 
Gwyn Ciesla
she/her/hers
 
in your fear, seek only peace 
in your fear, seek only love
-d. bowie


Sent with Proton Mail secure email.

On Wednesday, January 28th, 2026 at 11:51 AM, Packaging Reports 
 wrote:

> Report started at 2026-01-28 17:00:30 UTC
> 

> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please do so now with a proper reason:
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> 

> Note: If you received this mail directly you (co)maintain one of the affected
> packages or a package that depends on one. Please adopt the affected package 
> or
> retire your depending package to avoid broken dependencies, otherwise your
> package will be retired when the affected package gets retired.
> 

> Request package ownership via the Take button in the left column on
> https://src.fedoraproject.org/rpms/
> 

> 

> Full report available at:
> https://a.gtmx.me/orphans/orphans.txt
> grep it for your FAS username and follow the dependency chain.
> 

> For human readable dependency chains,
> see https://packager-dashboard.fedoraproject.org/
> For all orphaned packages,
> see https://packager-dashboard.fedoraproject.org/orphan
> 

> Package (co)maintainers Status Change
> 
> blueprint-compiler @gnome-sig, orphan 1 weeks ago
> cmake-fedora orphan 2 weeks ago
> deco orphan 5 weeks ago
> deco-archive orphan 5 weeks ago
> dssp orphan 2 weeks ago
> dwayland @deepinde-sig, orphan 3 weeks ago
> fctxpd orphan 5 weeks ago
> freeopcua orphan 0 weeks ago
> gecode orphan 5 weeks ago
> golang-cloud-google-monitoring @go-sig, orphan 5 weeks ago
> golang-cloud-google-trace @go-sig, orphan 5 weeks ago
> golang-github-adrg-xdg @go-sig, orphan 3 weeks ago
> golang-github-alibabacloud- @go-sig, orphan 5 weeks ago
> debug
> golang-github-alibabacloud-tea @go-sig, orphan 5 weeks ago
> golang-github-aliyun-cli @go-sig, orphan 5 weeks ago
> golang-github-aliyun- @go-sig, orphan 5 weeks ago
> credentials
> golang-github-aliyun-ossutil @go-sig, orphan 5 weeks ago
> golang-github-alyu-configparser @go-sig, orphan 5 weeks ago
> golang-github-armon-metrics @go-sig, orphan 5 weeks ago
> golang-github-aymanbagabas- @go-sig, orphan 3 weeks ago
> osc52
> golang-github-azure-sdk- @go-sig, orphan 3 weeks ago
> internal
> golang-github-cli-safeexec @go-sig, orphan 3 weeks ago
> golang-github-coreos-oidc @go-sig, orphan 3 weeks ago
> golang-github-droundy-goopt @go-sig, orphan 5 weeks ago
> golang-github-dustinkirkland- @go-sig, orphan 5 weeks ago
> petname
> golang-github-eclipse-paho-mqtt @go-sig, orphan 5 weeks ago
> golang-github-gocql @go-sig, orphan 3 weeks ago
> golang-github-google-wire @go-sig, orphan 5 weeks ago
> golang-github-haproxytech- @go-sig, orphan 5 weeks ago
> client-native
> golang-github-haproxytech- @go-sig, orphan 5 weeks ago
> config-parser
> golang-github-haproxytech- @go-sig, orphan 5 weeks ago
> logger
> golang-github-integrii-flaggy @go-sig, orphan 5 weeks ago
> golang-github-jarcoal-httpmock @go-sig, orphan 3 weeks ago
> golang-github-kr-pty @go-sig, jchaloup, orphan 3 weeks ago
> golang-github-lestrrat-envload @go-sig, orphan 5 weeks ago
> golang-github-lestrrat-strftime @go-sig, orphan 5 weeks ago
> golang-github-magiconair- @go-sig, orphan 5 weeks ago
> properties
> golang-github-mattn-ieproxy @go-sig, orphan 3 weeks ago
> golang-github-nats-io-nuid @go-sig, orphan 5 weeks ago
> golang-github-peterbourgon-ff-3 @go-sig, orphan 5 weeks ago
> golang-github-rjeczalik-notify @go-sig, orphan 5 weeks ago
> golang-github-sagikazarmark- @go-sig, orphan 5 weeks ago
> slog-shim
> golang-github-sgreben-flagvar @go-sig, orphan 5 weeks ago
> golang-github-shulhan-bindata @go-sig, orphan 5 weeks ago
> golang-github-vividcortex-ewma @go-sig, jchaloup, orphan 3 weeks ago
> golang-github-xanzy-gitlab @go-sig, orphan 3 weeks ago
> golang-github-zcalusic-sysinfo @go-sig, orphan 5 weeks ago
> golang-sr-spc-log @go-sig, orphan 3 weeks ago
> irstlm @epel-packagers-sig, orphan 5 weeks ago
> lizardfs orphan 3 weeks ago
> lxsplit orphan 5 weeks ago
> mingw-speexdsp orphan 5 weeks ago
> muse orphan 5 weeks ago
> netstat-nat orphan 2 weeks ago
> nipy-data ignatenkobrain, orphan 2 weeks ago
> nodejs-underscore orphan 5 weeks ago
> perl-Alien-Packages orphan 5 weeks ago
> perl-MooX-Roles-Pluggable orphan 5 weeks ago
> perl-Net-Twitter orphan 5 weeks ago
> perl-Unix-Statgrab cicku, orphan, steve 5 weeks ago
> perl-WWW-Shorten orphan 5 weeks ago
> python-catkin_lint @robotics-sig, cottsay, orphan 2 weeks ago
> python-fissix orphan 4 weeks ago
> python-jsonpath-rw orphan 2 weeks ago
> python-novaclient-os-networks ctria, orphan 5 weeks ago
> python-pandas-flavor orphan 6 weeks ago
> python-pyramid_sawin

Re: Orphaned packages looking for new maintainers

2026-01-23 Thread Frank R Dana Jr. 
Jiri Vanek wrote:
> On 1/15/26 13:38, Miro Hrončok wrote:
> > Which maintainer do we pass it to, if there are multiple?
> > It has no obvious solution.

> It have - the most active one in package. If there is non such, then the most 
> active in whole distribution (from `that` package maintainers, the one which 
> contribute to most packages distribution-wide). 

See, that's where we get into the "no OBVIOUS solution" thing, because those 
are not the obvious actions everyone can agree on. In fact, I would personally 
argue that dumping even MORE work on the most active packagers (the busiest 
ones already dealing with the most packages) is exactly the wrong approach. 
They have enough going on already.

Anyway, a package being orphaned is not a crisis event. In the short term, 
nothing changes, except that it gets placed on this report so that other 
packagers are aware that it's available in case they might have an interest in 
maintaining it.

Even if a package manages to stay in orphaned state for 6 weeks and get 
retired, reversing that is not particularly difficult. It's not like the 
package is banned from the distro forever.
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2026-01-15 Thread Jiri Vanek 



On 1/15/26 13:38, Miro Hrončok wrote:

On 15. 01. 26 12:44, Jiri Vanek wrote:


On 1/15/26 12:23, Miro Hrončok wrote:

On 15. 01. 26 11:50, Jiri Vanek wrote:


Hello!

Can please anybody remaind me how is this composed? How the package could end as orhpan, even if it is maintianed (commit at least once per three monhts, but usually more often (including upstream versions updates), and passing all mass 
rebuilds ...), and working fine?


I assume this is about openjdk-asmtools, correct?

See https://pagure.io/find-inactive-packagers/issue/2367

The main admin was inactive and was removed, their packages were orphaned


I see. When there is active co-maintainer, maybe the heritage can pass to they?


This is a reoccurring topic of discussions.


Sure, sorry:( But if it is so reoccuring, then maybe indeed the long run action 
should take palce.


Which maintainer do we pass it to, if there are multiple?

It has no obvious solution. That's why the co-maintainers are cc-ed in those 
tickets and they can react and figure it out among themselves.


It have - the most active one in package. If there is non such, then the most active in whole distribution (from `that` package maintainers, the one which contribute to most packages distribution-wide). If none such exists, then maybe 
random, but rather the approach as is now should continue. As the obvious issue with people doing mass rebuilds suddenly getting weird packages whcih they co-maintained ages ago, I see the issue. Thanks a lot for the "llooking for new 
maintainers" email, and no more stealing of your cycles.


TY!
  J.




--
Jiri Vanek 
Principal JDK QA engineer
IBM Middleware Czechia s.r.o.
+420 775 39 01 09

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2026-01-15 Thread Miro Hrončok 

On 15. 01. 26 12:44, Jiri Vanek wrote:


On 1/15/26 12:23, Miro Hrončok wrote:

On 15. 01. 26 11:50, Jiri Vanek wrote:


Hello!

Can please anybody remaind me how is this composed? How the package could 
end as orhpan, even if it is maintianed (commit at least once per three 
monhts, but usually more often (including upstream versions updates), and 
passing all mass rebuilds ...), and working fine?


I assume this is about openjdk-asmtools, correct?

See https://pagure.io/find-inactive-packagers/issue/2367

The main admin was inactive and was removed, their packages were orphaned


I see. When there is active co-maintainer, maybe the heritage can pass to they?


This is a reoccurring topic of discussions.

Which maintainer do we pass it to, if there are multiple?

It has no obvious solution. That's why the co-maintainers are cc-ed in those 
tickets and they can react and figure it out among themselves.


--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: mhroncok

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2026-01-15 Thread Jiri Vanek 


On 1/15/26 12:23, Miro Hrončok wrote:

On 15. 01. 26 11:50, Jiri Vanek wrote:


Hello!

Can please anybody remaind me how is this composed? How the package could end as orhpan, even if it is maintianed (commit at least once per three monhts, but usually more often (including upstream versions updates), and passing all mass 
rebuilds ...), and working fine?


I assume this is about openjdk-asmtools, correct?

See https://pagure.io/find-inactive-packagers/issue/2367

The main admin was inactive and was removed, their packages were orphaned


I see. When there is active co-maintainer, maybe the heritage can pass to they?


, you were mentioned.

Right, ty!!
And I immediately took it.

Best regards,
  J.

--
Jiri Vanek 
Principal JDK QA engineer
IBM Middleware Czechia s.r.o.
+420 775 39 01 09

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2026-01-15 Thread Jiri Vanek 



On 1/15/26 12:04, Alexander Ploumistos wrote:

Hi Jiri,

On Thu, Jan 15, 2026 at 11:52 AM Jiri Vanek  wrote:


Hello!

Can please anybody remaind me how is this composed? How the package could end 
as orhpan, even if it is maintianed (commit at least once per three monhts, but 
usually more often (including upstream versions updates), and passing all mass
rebuilds ...), and working fine?


As far as I know, a package becomes an orphan the moment it loses its


Yah! And how it can happen? They did not FTBS Ihad not get rid of the... So 
why? How?

This time it was  https://src.fedoraproject.org/rpms/openjdk-asmtools/
and last time it was https://src.fedoraproject.org/rpms/jd-core and/or 
https://src.fedoraproject.org/rpms/java-jd-decompiler

Some time ago, when I was less watchfull about this kind of emial (thanks for 
it!), some of my packages even retired and I noticed oonly during push 
(shameful:( )
I think I keep watching FTBFS quite enouugh...


main admin. Commits and rebuilds do not matter (unless of course it
FTBFS for some time), the important part is ownership.
You can claim any of these packages, e.g.
https://src.fedoraproject.org/rpms/cmake-fedora by logging in and
clicking on the "Take" button in the left-hand column.


Yout, that is known to me, and if I see my name in "Orphaned packages looking for new 
maintainers" I moreover automatically click "take" again.

Just why.. :)


Thanx a lot for reply In fedora lists, one is never alone. Thanks again!

J.

--
Jiri Vanek 
Principal JDK QA engineer
IBM Middleware Czechia s.r.o.
+420 775 39 01 09

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2026-01-15 Thread Miro Hrončok 

On 15. 01. 26 11:50, Jiri Vanek wrote:


Hello!

Can please anybody remaind me how is this composed? How the package could end 
as orhpan, even if it is maintianed (commit at least once per three monhts, but 
usually more often (including upstream versions updates), and passing all mass 
rebuilds ...), and working fine?


I assume this is about openjdk-asmtools, correct?

See https://pagure.io/find-inactive-packagers/issue/2367

The main admin was inactive and was removed, their packages were orphaned, you 
were mentioned.


--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: mhroncok

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2026-01-15 Thread Alexander Ploumistos 
Hi Jiri,

On Thu, Jan 15, 2026 at 11:52 AM Jiri Vanek  wrote:
>
> Hello!
>
> Can please anybody remaind me how is this composed? How the package could end 
> as orhpan, even if it is maintianed (commit at least once per three monhts, 
> but usually more often (including upstream versions updates), and passing all 
> mass
> rebuilds ...), and working fine?

As far as I know, a package becomes an orphan the moment it loses its
main admin. Commits and rebuilds do not matter (unless of course it
FTBFS for some time), the important part is ownership.
You can claim any of these packages, e.g.
https://src.fedoraproject.org/rpms/cmake-fedora by logging in and
clicking on the "Take" button in the left-hand column.
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2026-01-15 Thread Jiri Vanek 


Hello!

Can please anybody remaind me how is this composed? How the package could end as orhpan, even if it is maintianed (commit at least once per three monhts, but usually more often (including upstream versions updates), and passing all mass 
rebuilds ...), and working fine?


It i s not first time I found my package in this list, seeing it was orphaned where I normally use it nad maintain it. On contrary there is at least one package, which is nomrally working and building, but except Rebuilt for 
...Fedora_XYZ_Mass_Rebuild was not touched for years, is still there without ay complications...


Thanks!
  J.


On 1/13/26 01:08, Packaging Reports wrote:

Report started at 2026-01-13 00:00:08 UTC

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.

Request package ownership via the *Take* button in the left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://a.gtmx.me/orphans/orphans.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan

 Package  (co)maintainers   Status 
Change

bashmount orphan   3 weeks ago
cmake-fedora  orphan   0 weeks ago
contractororphan   4 weeks ago
deco  orphan   3 weeks ago
deco-archive  orphan   3 weeks ago
dwayland  @deepinde-sig, orphan1 weeks ago
fctxpdorphan   3 weeks ago
fmidi orphan   4 weeks ago
folio orphan   0 weeks ago
gecodeorphan   3 weeks ago
glide @go-sig, orphan  4 weeks ago
golang-cloud-google-monitoring@go-sig, orphan  3 weeks ago
golang-cloud-google-trace @go-sig, orphan  3 weeks ago
golang-github-adrg-xdg@go-sig, orphan  1 weeks ago
golang-github-alibabacloud-   @go-sig, orphan  3 weeks ago
debug
golang-github-alibabacloud-tea@go-sig, orphan  3 weeks ago
golang-github-aliyun-cli  @go-sig, orphan  3 weeks ago
golang-github-aliyun- @go-sig, orphan  3 weeks ago
credentials
golang-github-aliyun-ossutil  @go-sig, orphan  3 weeks ago
golang-github-alyu-configparser   @go-sig, orphan  3 weeks ago
golang-github-armon-metrics   @go-sig, orphan  3 weeks ago
golang-github-aymanbagabas-   @go-sig, orphan  1 weeks ago
osc52
golang-github-azure-sdk-  @go-sig, orphan  1 weeks ago
internal
golang-github-cli-safeexec@go-sig, orphan  1 weeks ago
golang-github-coreos-oidc @go-sig, orphan  1 weeks ago
golang-github-droundy-goopt   @go-sig, orphan  3 weeks ago
golang-github-dustinkirkland- @go-sig, orphan  3 weeks ago
petname
golang-github-eclipse-paho-mqtt   @go-sig, orphan  3 weeks ago
golang-github-gocql   @go-sig, orphan  0 weeks ago
golang-github-google-wire @go-sig, orphan  2 weeks ago
golang-github-haproxytech-@go-sig, orphan  3 weeks ago
client-native
golang-github-haproxytech-@go-sig, orphan  3 weeks ago
config-parser
golang-github-haproxytech-@go-sig, orphan  3 weeks ago
logger
golang-github-integrii-flaggy @go-sig, orphan  3 weeks ago
golang-github-jarcoal-httpmock@go-sig, orphan  1 weeks ago
golang-github-kr-pty  @go-sig, jchaloup, orphan1 weeks ago
golang-github-lestrrat-envload@go-sig, orphan  3 weeks ago
golang-github-lestrrat-strftime   @go-sig, orphan  3 weeks ago
golang-github-magiconair- @go-sig, orphan

Re: Orphaned packages looking for new maintainers

2026-01-04 Thread Neal Gompa 
On Sun, Jan 4, 2026 at 2:31 AM Simon de Vlieger  wrote:
>
> On Sun, Jan 4, 2026, at 12:49 AM, Packaging Reports wrote:
>
> > ...
>
> The huge list here seems to be caused by the orphaning of `cvsps` [1]. I've
> taken the package for now so it has an owner and the cascade stops.
>
> However, since the upstream (seems to) be gone perhaps we can get rid of the
> dependency on it in `git(-cvs)` or dropping that subpackage entirely.
>
> [1]: https://src.fedoraproject.org/rpms/cvsps

It looks like cvsps 3.x was developed by ESR until 2013 (we didn't
notice?): http://www.catb.org/~esr/cvsps/

But also, he recommends using cvs-fast-export whenever possible (which
we don't have): http://www.catb.org/~esr/cvs-fast-export/




--
真実はいつも一つ！/ Always, there's only one truth!
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2026-01-04 Thread Sandro Mani 


On 04.01.26 10:33, Fabio Porcedda wrote:

Hi all,

Il giorno dom 4 gen 2026 alle ore 02:10 Packaging Reports via
devel-announce  ha scritto:

Report started at 2026-01-03 23:00:04 UTC
...
ceres-solver  smani2 weeks ago

I would like to adopt the ceres-solver package but because I'm not yet
a package maintainer I'm waiting for the package review:
https://bugzilla.redhat.com/show_bug.cgi?id=2425618


I took ceres-solver, happy to add you as comaintainer as soon as you are 
sponsored.


Sandro

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2026-01-04 Thread Fabio Porcedda 
Hi all,

Il giorno dom 4 gen 2026 alle ore 02:10 Packaging Reports via
devel-announce  ha scritto:
>
> Report started at 2026-01-03 23:00:04 UTC
> ...
> ceres-solver  smani2 weeks ago

I would like to adopt the ceres-solver package but because I'm not yet
a package maintainer I'm waiting for the package review:
https://bugzilla.redhat.com/show_bug.cgi?id=2425618

Regards
-- 
Fabio Porcedda
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2026-01-03 Thread Simon de Vlieger 
On Sun, Jan 4, 2026, at 12:49 AM, Packaging Reports wrote:

> ...

The huge list here seems to be caused by the orphaning of `cvsps` [1]. I've
taken the package for now so it has an owner and the cascade stops.

However, since the upstream (seems to) be gone perhaps we can get rid of the
dependency on it in `git(-cvs)` or dropping that subpackage entirely.

[1]: https://src.fedoraproject.org/rpms/cvsps
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-12-10 Thread Łukasz Wojniłowicz 

On 25-12-09 22:30, Fabio Valentini wrote:

On Sun, Dec 7, 2025 at 7:43 PM Łukasz Wojniłowicz
 wrote:


On 25-12-06 18:26, Fabio Valentini wrote:
>On Sat, Dec 6, 2025 at 1:11 PM Łukasz Wojniłowicz
> wrote:
>>
>> I took rust-jpeg-encoder and rust-gufo.
>
>I would recommend to coordinate with the Rust SIG and / or the
>Workstation WG here - they're dependencies of "core" parts of the
>distribution and require a bit of care.
>Also, those two are not the only orphaned packages that still need to
>be unorphaned to clear up the rust-* <- glycin <- all of GNOME and
>other GTK based DEs dependency chain.
>
>Fabio

No problem, but I don't know what exactly I should do. I didn't want the
package that I care about to be taken down by those orphaned packages, so I
took them. If you or anybody else would like to retake them from me, then
feel free to do so.


I have unorphaned the remaining `rust-gufo*` and `rust-glycin-*`
packages for now.
If you don't know what to do with the ones you unorphaned (why did you
take them then?), feel free to "Give" them to me for now ...

Fabio


By writing "I don't know what exactly I should do" I meant with your "I would recommend to 
coordinate with the Rust SIG" and not with package maintenance. Anyway, I "gave" you the 
packages.

--
Łukasz
--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-12-09 Thread Fabio Valentini 
On Sun, Dec 7, 2025 at 7:43 PM Łukasz Wojniłowicz
 wrote:
>
> On 25-12-06 18:26, Fabio Valentini wrote:
> >On Sat, Dec 6, 2025 at 1:11 PM Łukasz Wojniłowicz
> > wrote:
> >>
> >> I took rust-jpeg-encoder and rust-gufo.
> >
> >I would recommend to coordinate with the Rust SIG and / or the
> >Workstation WG here - they're dependencies of "core" parts of the
> >distribution and require a bit of care.
> >Also, those two are not the only orphaned packages that still need to
> >be unorphaned to clear up the rust-* <- glycin <- all of GNOME and
> >other GTK based DEs dependency chain.
> >
> >Fabio
>
> No problem, but I don't know what exactly I should do. I didn't want the
> package that I care about to be taken down by those orphaned packages, so I
> took them. If you or anybody else would like to retake them from me, then
> feel free to do so.

I have unorphaned the remaining `rust-gufo*` and `rust-glycin-*`
packages for now.
If you don't know what to do with the ones you unorphaned (why did you
take them then?), feel free to "Give" them to me for now ...

Fabio
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-12-07 Thread Łukasz Wojniłowicz 

On 25-12-06 18:26, Fabio Valentini wrote:

On Sat, Dec 6, 2025 at 1:11 PM Łukasz Wojniłowicz
 wrote:


I took rust-jpeg-encoder and rust-gufo.


I would recommend to coordinate with the Rust SIG and / or the
Workstation WG here - they're dependencies of "core" parts of the
distribution and require a bit of care.
Also, those two are not the only orphaned packages that still need to
be unorphaned to clear up the rust-* <- glycin <- all of GNOME and
other GTK based DEs dependency chain.

Fabio


No problem, but I don't know what exactly I should do. I didn't want the
package that I care about to be taken down by those orphaned packages, so I
took them. If you or anybody else would like to retake them from me, then
feel free to do so.
--
Łukasz
--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-12-06 Thread Fabio Valentini 
On Sat, Dec 6, 2025 at 1:11 PM Łukasz Wojniłowicz
 wrote:
>
> I took rust-jpeg-encoder and rust-gufo.

I would recommend to coordinate with the Rust SIG and / or the
Workstation WG here - they're dependencies of "core" parts of the
distribution and require a bit of care.
Also, those two are not the only orphaned packages that still need to
be unorphaned to clear up the rust-* <- glycin <- all of GNOME and
other GTK based DEs dependency chain.

Fabio
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-11-17 Thread Gwyn Ciesla via devel 
Taking python-pytest-cov.



-- 
Gwyn Ciesla
she/her/hers
 
in your fear, seek only peace 
in your fear, seek only love
-d. bowie


Sent with Proton Mail secure email.

On Sunday, November 16th, 2025 at 10:18 PM, Packaging Reports 
 wrote:

> Report started at 2025-11-17 03:00:21 UTC
> 

> SPECIAL NOTE: The exception for Golang library packages granted in
> https://pagure.io/fesco/issue/3447, is going away,
> as the new Golang Packaging Guidelines have been released.
> 2025-11-03 is the flag date for resuming retirements for these packages.
> Any package orphaned before the flag date will be retired
> six weeks after the flag date — around 2025-12-15.
> Packages orphaned after the flag date will be retied six weeks after they were
> orphaned, per the usual policy.
> Note that, if a Golang library becomes a leaf in a subsequent report, it will
> be retired based on when it was originally orphaned, not the flag date,
> as leaf packages are not subject to the exemption issued by FESCo.
> 

> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please do so now with a proper reason:
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> 

> Note: If you received this mail directly you (co)maintain one of the affected
> packages or a package that depends on one. Please adopt the affected package 
> or
> retire your depending package to avoid broken dependencies, otherwise your
> package will be retired when the affected package gets retired.
> 

> Request package ownership via the Take button in the left column on
> https://src.fedoraproject.org/rpms/
> 

> 

> Full report available at:
> https://a.gtmx.me/orphans/orphans.txt
> grep it for your FAS username and follow the dependency chain.
> 

> For human readable dependency chains,
> see https://packager-dashboard.fedoraproject.org/
> For all orphaned packages,
> see https://packager-dashboard.fedoraproject.org/orphan
> 

> Package (co)maintainers Status Change Time since Golang
> flag date
> 
> appeditor orphan 3 weeks ago n/a
> caribou @epel-packagers- 2 weeks ago n/a
> sig, orphan
> chafa jonathanspw, orphan 0 weeks ago n/a
> conan orphan 1 weeks ago n/a
> ddclient cicku, orphan 2 weeks ago n/a
> deepin-daemon @deepinde-sig, @go- 4 weeks ago n/a
> sig, cheeselee,
> orphan, zsun
> deepin-screenshot @deepinde-sig, 4 weeks ago n/a
> cheeselee, orphan,
> zsun
> deepin-session-shell @deepinde-sig, 4 weeks ago n/a
> cheeselee, orphan
> earlyoom @epel-packagers- 2 weeks ago n/a
> sig, orphan
> efs-utils fkolwa, miyunari, 0 weeks ago n/a
> orphan
> gir-to-d orphan 1 weeks ago n/a
> golang-contrib- @go-sig, orphan 8 weeks ago 2 weeks ago
> opencensus-exporter-
> stackdriver
> golang-github- @go-sig, orphan 18 weeks ago 2 weeks ago
> akamensky-argparse
> golang-github- @go-sig, orphan 18 weeks ago 2 weeks ago
> antchfx-xpath
> golang-github-azure- @go-sig, orphan 5 weeks ago n/a
> sdk-azidentity
> golang-github- @go-sig, orphan 13 weeks ago 2 weeks ago
> bradfitz-gomemcache
> golang-github- @go-sig, orphan 18 weeks ago 2 weeks ago
> casbin-2
> golang-github- @go-sig, jchaloup, 18 weeks ago 2 weeks ago
> cenkalti-backoff orphan
> golang-github- @go-sig, orphan 3 weeks ago n/a
> cenkalti-backoff5
> golang-github- @go-sig, orphan 18 weeks ago 2 weeks ago
> cespare-xxhash
> golang-github- @go-sig, orphan 5 weeks ago n/a
> charmbracelet-
> bubbletea
> golang-github- @go-sig, orphan 5 weeks ago n/a
> charmbracelet-
> harmonica
> golang-github- @go-sig, orphan 5 weeks ago n/a
> charmbracelet-
> lipgloss
> golang-github- @go-sig, orphan 1 weeks ago n/a
> dennwc-ioctl
> golang-github-dsnet- @go-sig, orphan 18 weeks ago 2 weeks ago
> compress
> golang-github-dsnet- @go-sig, orphan 18 weeks ago 2 weeks ago
> golib
> golang-github- @go-sig, orphan 18 weeks ago 2 weeks ago
> emirpasic-gods
> golang-github- @go-sig, orphan 17 weeks ago 2 weeks ago
> fnproject-fdk
> golang-github- @go-sig, orphan 18 weeks ago 2 weeks ago
> gobwas-httphead
> golang-github- @go-sig, orphan 18 weeks ago 2 weeks ago
> gobwas-pool
> golang-github- @go-sig, orphan 18 weeks ago 2 weeks ago
> gobwas-ws
> golang-github- @go-sig, jchaloup, 10 weeks ago 2 weeks ago
> hashicorp-raft orphan
> golang-github- @go-sig, orphan 9 weeks ago 2 weeks ago
> hashicorp-terraform-
> exec
> golang-github- @go-sig, orphan 1 weeks ago n/a
> hebcal-gematriya
> golang-github- @go-sig, orphan 1 weeks ago n/a
> hebcal-hdate
> golang-github- @go-sig, orphan 18 weeks ago 2 weeks ago
> jbenet-context
> golang-github- @go-sig, orphan 18 weeks ago 2 weeks ago
> jpillora-backoff
> golang-github- @go-sig, orphan 1 weeks ago n/a
> kelvins-
> sunrisesunset
> golang-github- @go-sig, orphan 18 weeks ago 2 weeks ago
> kevinburke-ssh-
> config
> golang-github- @go-sig, o

Re: Orphaned packages looking for new maintainers

2025-11-17 Thread Dominik 'Rathann' Mierzejewski 
On Monday, 17 November 2025 at 08:17, Jens-Ulrik Petersen wrote:
> Can someone explain what pulls the rust-gufo deps? :)

gdk-pixbuf2 -> glycin -> rust-gufo

Regards,
Dominik
-- 
Fedora   https://fedoraproject.org
Deep in the human unconscious is a pervasive need for a logical universe that
makes sense. But the real universe is always one step beyond logic.
-- from "The Sayings of Muad'Dib" by the Princess Irulan
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-11-16 Thread Sandro 

On 17-11-2025 08:17, Jens-Ulrik Petersen wrote:

Can someone explain what pulls the rust-gufo deps? :)


Likely glycin, which is required by gdk-pixbuf2, which 675 packages 
depend on...



--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-11-16 Thread Jens-Ulrik Petersen 
Can someone explain what pulls the rust-gufo deps? :)
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-11-04 Thread Davide Cavalca 

On 2025-11-03 12:53, Packaging Reports wrote:

usrsctp@epel-packagers-  0 weeks ago n/a
   sig, dcavalca,
   orphan


Picked this one up.

Cheers
Davide
--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-09-17 Thread Robby Callicotte via devel 
On Monday, July 28, 2025 9:36:26 PM Central Daylight Time maxwell--- via 
devel-announce wrote:
> python-pytest-orderingorphan   3 weeks
> ago

I picked up this package.

--
Robby



-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-28 Thread Debarshi Ray via devel 
On Mon, 2025-08-25 at 17:11 -0500, Packaging Reports wrote:

> telepathy-logger  @kde-sig, orphan, rishi  1
> weeks ago

I really shouldn't be a co-admin of telepathy-logger:
https://src.fedoraproject.org/rpms/telepathy-logger

It's been ten years since I last did anything significant with the
package:
https://src.fedoraproject.org/rpms/telepathy-logger/c/80777469269a5ecb4a220dd3368134aedcc57d16

I only fixed two build failures in the past 5 or 6 years:
https://src.fedoraproject.org/rpms/telepathy-logger/c/a28ec1afc29654b2983dba801a641b45fe366762
https://src.fedoraproject.org/rpms/telepathy-logger/c/3c01421ffbcbe700521161cf6b1df16d6b956add

I have now removed myself.  I hope someone (the KDE SIG?) picks it up,
if it's needed.
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-21 Thread Lukas Slebodnik 
I took  python-requests-pkcs12

LS
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-17 Thread Jens-Ulrik Petersen 
I took llvm18 and clang18, needed by ghc9.12 - and also lld18.

Jens
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-15 Thread Miro Hrončok 

On 15. 08. 25 16:40, Sandro wrote:
If I take back python-diff-match-patch now, should I take care of the rebuild 
for 3.14.0rc2 myself? Or will it be picked up in the next run?


The builds are pending:

https://koji.fedoraproject.org/koji/taskinfo?taskID=136068438
https://koji.fedoraproject.org/koji/taskinfo?taskID=136068440

--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: mhroncok

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-15 Thread Sandro 

On 15-08-2025 12:28, Miro Hrončok wrote:

On 15. 08. 25 12:13, Miro Hrončok wrote:

On 15. 08. 25 9:15, Sandro wrote:

On 14-08-2025 22:27, Miro Hrončok wrote:

On 14. 08. 25 21:35, Sandro wrote:
Unlikely. The reason for orphaning is cleared (or should be) when a 
package is picked up by another user. At least that's my experience 
using the UI. The API may behave differently.


I think the reason is hidden from the UI but stays in the DB. 
Assigning the package to orphan via the "give package to user" then 
uncovers the old reason.


That would explain the misleading reason. The question then boils 
down to:


Who gave the package away and why?

I suppose only users or scripts with elevated access would be able to 
do so.
It look like all the packages from https://pagure.io/releng/ 
issue/12739 are orphaned now.


That makes me think I must have rerun that action by accident. I still 
don't know how or when, but if it was indeed me, I sincerely apologize.


Maybe infra folks might be able to dig the previous owners up?


I've deduced the maintainers from Koji and emailed them.


Thanks for the heads up and for looking into it.

If I take back python-diff-match-patch now, should I take care of the 
rebuild for 3.14.0rc2 myself? Or will it be picked up in the next run?


--
Sandro

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-15 Thread Fabio Valentini 
On Fri, Aug 15, 2025 at 7:49 AM Milan Crha  wrote:
>
> On Thu, 2025-08-14 at 19:32 +0200, Miro Hrončok wrote:
> > > I think bijiben and gtksourceview4 are suspicious and maybe
> > > orphaned in error.
>
> Hi again,
> okay, I want the gnome-sig to take over the bijiben package. I took
> over the bijiben package, which made me the main admin and it also
> preserved my commit access (my nick had two entries there). I did set
> the gnome-sig as a (co-)maintainer. I thought when I'll orphan it again
> the gnome-sig will take over, but it clearly does not work that way.
> More importantly, I lost both entries, the main admin and the commit
> access to that package. I suppose groups cannot be the main admins of
> the packages, can they?

Yes, groups cannot be the main point of contact / "main admin" ACL for
a package, only users.

Fabio
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-15 Thread Miro Hrončok 

On 15. 08. 25 12:13, Miro Hrončok wrote:

On 15. 08. 25 9:15, Sandro wrote:

On 14-08-2025 22:27, Miro Hrončok wrote:

On 14. 08. 25 21:35, Sandro wrote:
Unlikely. The reason for orphaning is cleared (or should be) when a package 
is picked up by another user. At least that's my experience using the UI. 
The API may behave differently.


I think the reason is hidden from the UI but stays in the DB. Assigning the 
package to orphan via the "give package to user" then uncovers the old reason.


That would explain the misleading reason. The question then boils down to:

Who gave the package away and why?

I suppose only users or scripts with elevated access would be able to do so.
It look like all the packages from https://pagure.io/releng/issue/12739 are 
orphaned now.


That makes me think I must have rerun that action by accident. I still don't 
know how or when, but if it was indeed me, I sincerely apologize.


Maybe infra folks might be able to dig the previous owners up?


I've deduced the maintainers from Koji and emailed them.

--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: mhroncok

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-15 Thread Miro Hrončok 

On 15. 08. 25 9:15, Sandro wrote:

On 14-08-2025 22:27, Miro Hrončok wrote:

On 14. 08. 25 21:35, Sandro wrote:
Unlikely. The reason for orphaning is cleared (or should be) when a package 
is picked up by another user. At least that's my experience using the UI. 
The API may behave differently.


I think the reason is hidden from the UI but stays in the DB. Assigning the 
package to orphan via the "give package to user" then uncovers the old reason.


That would explain the misleading reason. The question then boils down to:

Who gave the package away and why?

I suppose only users or scripts with elevated access would be able to do so.
It look like all the packages from https://pagure.io/releng/issue/12739 are 
orphaned now.


That makes me think I must have rerun that action by accident. I still don't 
know how or when, but if it was indeed me, I sincerely apologize.


Maybe infra folks might be able to dig the previous owners up?

--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: mhroncok

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-15 Thread Miro Hrončok 

On 15. 08. 25 7:26, Milan Crha wrote:

No idea how you found that ticket,


I happened to be the one who processed it.

--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: mhroncok

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-15 Thread Sandro 

On 14-08-2025 22:27, Miro Hrončok wrote:

On 14. 08. 25 21:35, Sandro wrote:
Unlikely. The reason for orphaning is cleared (or should be) when a 
package is picked up by another user. At least that's my experience 
using the UI. The API may behave differently.


I think the reason is hidden from the UI but stays in the DB. Assigning 
the package to orphan via the "give package to user" then uncovers the 
old reason.


That would explain the misleading reason. The question then boils down to:

Who gave the package away and why?

I suppose only users or scripts with elevated access would be able to do so.

--
Sandro

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-14 Thread Milan Crha 
On Thu, 2025-08-14 at 19:32 +0200, Miro Hrončok wrote:
> > I think bijiben and gtksourceview4 are suspicious and maybe
> > orphaned in error.

Hi again,
okay, I want the gnome-sig to take over the bijiben package. I took
over the bijiben package, which made me the main admin and it also
preserved my commit access (my nick had two entries there). I did set
the gnome-sig as a (co-)maintainer. I thought when I'll orphan it again
the gnome-sig will take over, but it clearly does not work that way.
More importantly, I lost both entries, the main admin and the commit
access to that package. I suppose groups cannot be the main admins of
the packages, can they?

I took bijiben (again), even I do not intend to be the main admin for
it. I had commit rights only to be able to rebuild it in case
evolution-data-server bumps its soname version. I'd like to give away
the main admin flag from me on that package, I'm definitely not going
to fix any of its bug reports.

Bye,
Milan

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-14 Thread Milan Crha 
On Thu, 2025-08-14 at 19:32 +0200, Miro Hrončok wrote:
> Both orphaned via https://pagure.io/releng/issue/12858

Hi,
aha, I see, that makes sense now.

No idea how you found that ticket, but the Filter->Search in pagure is
dull and doesn't find that ticket when searching for the
gtksourceview4. That's another thing.

Thanks and bye,
Milan

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-14 Thread Miro Hrončok 

On 14. 08. 25 21:35, Sandro wrote:
Unlikely. The reason for orphaning is cleared (or should be) when a package is 
picked up by another user. At least that's my experience using the UI. The API 
may behave differently.


I think the reason is hidden from the UI but stays in the DB. Assigning the 
package to orphan via the "give package to user" then uncovers the old reason.


--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: mhroncok

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-14 Thread Carlos Rodriguez-Fernandez 

On 8/13/25 7:46 PM, maxwell--- via devel-announce wrote:

Report started at 2025-08-14 02:00:41 UTC



I'm taking this one and fixing the build issue.


strongswandcavalca, orphan, pemensik,  0 weeks ago
   salimma



-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-14 Thread Sandro 

On 14-08-2025 17:47, Miro Hrončok wrote:

On 14. 08. 25 17:25, Sandro wrote:

On 14-08-2025 04:46, [email protected] wrote:

python-diff-match-patch   orphan   0 
weeks ago


Could someone help me understand how python-diff-match-patch ended up 
orphaned? The bug referenced in the orphan message [1] is closed and 
there are no other open bugs for the package.


I adopted the package back in May. After fixing the build issue, the 
package has been successfully rebuilt for Python 3.14 and the F43 mass 
rebuild.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=2354097


I orphaned it via https://pagure.io/releng/issue/12739 in May.


Yeah. After that I picked it up. That can also be inferred from the 
bug's metadata. The bug was reassigned to orphan-owner on 17 May and 
than again to me on 23 May after I adopted the package.


Looks like it was given to the orphan user now and the previous reason 
stayed there.


Unlikely. The reason for orphaning is cleared (or should be) when a 
package is picked up by another user. At least that's my experience 
using the UI. The API may behave differently.



No idea what happened here, or who orphaned it this time :/
Strange indeed. I will wait a couple more days before picking it up 
again in case someone else wants to poke around.


--
Sandro

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-14 Thread Miro Hrončok 

On 14. 08. 25 18:59, Milan Crha wrote:

Hi,
where does one get the reasons behind the orphanage, or the history of
admin/ownership changes in general, please?


No idea.


I think bijiben and gtksourceview4 are suspicious and maybe orphaned in
error.


Both orphaned via https://pagure.io/releng/issue/12858

--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: mhroncok

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-14 Thread Milan Crha 
On Thu, 2025-08-14 at 17:47 +0200, Miro Hrončok wrote:
> Looks like it was given to the orphan user now and the previous
> reason stayed there.
> 
> No idea what happened here, or who orphaned it this time :/

Hi,
where does one get the reasons behind the orphanage, or the history of
admin/ownership changes in general, please?

I think bijiben and gtksourceview4 are suspicious and maybe orphaned in
error. I do not see announcements of orphaning them here on the list
(only one from 2016 for bijiben) and both built fine in rawhide and
earlier Fedoras.

ngompa is the main admin of the gtksourceview4, which might be added
just recently, only not mentioned on the list? Though that still does
not explain why it had been orphaned.

The bijiben has a short notice in the [1] saying: `Orphaned for:
Orphaned by releng` which is not helpful. I tried to search releng
tickets [2], but that did not catch anything.

Thanks and bye,
Milan

[1] https://src.fedoraproject.org/rpms/bijiben
[2] 
https://pagure.io/releng/issues?status=Closed&search_pattern=bijiben&close_status=

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-14 Thread Miro Hrončok 

On 14. 08. 25 17:25, Sandro wrote:

On 14-08-2025 04:46, [email protected] wrote:


python-diff-match-patch   orphan   0 weeks ago


Could someone help me understand how python-diff-match-patch ended up orphaned? 
The bug referenced in the orphan message [1] is closed and there are no other 
open bugs for the package.


I adopted the package back in May. After fixing the build issue, the package 
has been successfully rebuilt for Python 3.14 and the F43 mass rebuild.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=2354097


I orphaned it via https://pagure.io/releng/issue/12739 in May.

Looks like it was given to the orphan user now and the previous reason stayed 
there.


No idea what happened here, or who orphaned it this time :/

--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: mhroncok

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-08-14 Thread Sandro 

On 14-08-2025 04:46, [email protected] wrote:


python-diff-match-patch   orphan   0 weeks ago


Could someone help me understand how python-diff-match-patch ended up 
orphaned? The bug referenced in the orphan message [1] is closed and 
there are no other open bugs for the package.


I adopted the package back in May. After fixing the build issue, the 
package has been successfully rebuilt for Python 3.14 and the F43 mass 
rebuild.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=2354097

--
Sandro
--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-07-30 Thread Ben Beasley 
Note that it is going to be quite difficult to migrate gaupol away from 
%py3_build/%py3_install macros, 
https://bugzilla.redhat.com/show_bug.cgi?id=2377265, due to upstream’s 
use of a particularly creative customized setup.py based on distutils. 
This is not a crisis for the package yet, but it will need to be 
addressed in the short to medium term.


You may (or may not) have better luck submitting a new python-aeidon 
source package to support translate-toolkit, leaving the 
gaupol/python3-gaupol parts behind. It would still take some finesse to 
get this working with pyproject-rpm-macros, but you might end up with 
fewer moving parts to worry about.


– Ben Beasley (FAS: music)

On 7/30/25 6:58 AM, Sudip Shil wrote:

Hello,
I took Gaupol, as it's required by translate-toolkit. just noting it 
here so others are aware.


Sincerely,
Sudip Shil

On Mon, Apr 21, 2025 at 9:10 AM maxwell--- via devel-announce 
 wrote:


Report started at 2025-04-20 22:00:03 UTC

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you
know for sure
that the package should be retired, please do so now with a proper
reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

Note: If you received this mail directly you (co)maintain one of
the affected
packages or a package that depends on one. Please adopt the
affected package or
retire your depending package to avoid broken dependencies,
otherwise your
package will be retired when the affected package gets retired.

Request package ownership via the *Take* button in the left column on
https://src.fedoraproject.org/rpms/

Full report available at:
https://a.gtmx.me/orphans/orphans.txt
grep it for your FAS username and follow the dependency chain.

For human readable dependency chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan

            Package                      (co)maintainers      
 Status Change


deepin-control-center             @deepinde-sig, cheeselee,      
2 weeks ago
                                  orphan, zsun
deepin-editor                     @deepinde-sig, cheeselee,      
2 weeks ago
                                  orphan, zsun
flowcanvas                        orphan        0 weeks ago
fuse-emulator-utils               orphan        4 weeks ago
getmail                           orphan        0 weeks ago
golang-github-aclements-gg        @go-sig, jchaloup, orphan      
4 weeks ago
golang-github-edoardottt-golazy   @go-sig, orphan       4 weeks ago
golang-github-edoardottt-lit-     @go-sig, orphan       4 weeks ago
bb-hack-tools
kdissert                          orphan        0 weeks ago
libsoup                           @gnome-sig, alexl, danw,      
 0 weeks ago
                                  orphan, rhughes, rstrode,
                                  tpopela
netdata                           @go-sig, orphan       0 weeks ago
nginx-mod-headers-more            orphan        1 weeks ago
nova-agent                        orphan, tonyskapunk       4
weeks ago
ogre                              dtimms, ignatenkobrain, orphan 
 0 weeks ago
php-doctrine-doctrine-cache-      orphan, remi        3 weeks ago
bundle
prelude-lml-rules                 orphan        2 weeks ago
prewikka-updatedb                 orphan        2 weeks ago
pygsl                             orphan        2 weeks ago
python-barbicanclient             @epel-packagers-sig,        4
weeks ago
                                  @openstack-sig, apevec, orphan
python-designateclient            @openstack-sig, apevec, orphan 
 4 weeks ago
python-magnumclient               @epel-packagers-sig,        4
weeks ago
                                  @openstack-sig, apevec, orphan
python-pygeoip                    @infra-sig, orphan        4
weeks ago
python-pypet                      orphan        0 weeks ago
python-simplebayes                @python-packagers-sig, orphan   
4 weeks ago
python-sphinxcontrib-apidoc       @epel-packagers-sig,        2
weeks ago
                                  @openstack-sig, orphan
rawstudio                         orphan        0 weeks ago
rubygem-serialport                orphan        5 weeks ago
splint                            orphan        0 weeks ago
startdde                          @deepinde-sig, @go-sig,       3
weeks ago
                                  cheeselee, orphan, zsun

The following packages require above mentioned packages:
Depending on: deepin-control-center (8), status

Re: Orphaned packages looking for new maintainers

2025-07-30 Thread Sudip Shil 
Hello,
I took Gaupol, as it's required by translate-toolkit. just noting it here
so others are aware.

Sincerely,
Sudip Shil

On Mon, Apr 21, 2025 at 9:10 AM maxwell--- via devel-announce <
[email protected]> wrote:

> Report started at 2025-04-20 22:00:03 UTC
>
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for
> sure
> that the package should be retired, please do so now with a proper reason:
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
>
> Note: If you received this mail directly you (co)maintain one of the
> affected
> packages or a package that depends on one. Please adopt the affected
> package or
> retire your depending package to avoid broken dependencies, otherwise your
> package will be retired when the affected package gets retired.
>
> Request package ownership via the *Take* button in the left column on
> https://src.fedoraproject.org/rpms/
>
> Full report available at:
> https://a.gtmx.me/orphans/orphans.txt
> grep it for your FAS username and follow the dependency chain.
>
> For human readable dependency chains,
> see https://packager-dashboard.fedoraproject.org/
> For all orphaned packages,
> see https://packager-dashboard.fedoraproject.org/orphan
>
> Package  (co)maintainers   Status
> Change
>
> 
> deepin-control-center @deepinde-sig, cheeselee,2 weeks
> ago
>   orphan, zsun
>
> deepin-editor @deepinde-sig, cheeselee,2 weeks
> ago
>   orphan, zsun
>
> flowcanvasorphan   0 weeks
> ago
> fuse-emulator-utils   orphan   4 weeks
> ago
> getmail   orphan   0 weeks
> ago
> golang-github-aclements-gg@go-sig, jchaloup, orphan4 weeks
> ago
> golang-github-edoardottt-golazy   @go-sig, orphan  4 weeks
> ago
> golang-github-edoardottt-lit- @go-sig, orphan  4 weeks
> ago
> bb-hack-tools
>
> kdissert  orphan   0 weeks
> ago
> libsoup   @gnome-sig, alexl, danw, 0 weeks
> ago
>   orphan, rhughes, rstrode,
>
>   tpopela
>
> netdata   @go-sig, orphan  0 weeks
> ago
> nginx-mod-headers-moreorphan   1 weeks
> ago
> nova-agentorphan, tonyskapunk  4 weeks
> ago
> ogre  dtimms, ignatenkobrain, orphan   0 weeks
> ago
> php-doctrine-doctrine-cache-  orphan, remi 3 weeks
> ago
> bundle
>
> prelude-lml-rules orphan   2 weeks
> ago
> prewikka-updatedb orphan   2 weeks
> ago
> pygsl orphan   2 weeks
> ago
> python-barbicanclient @epel-packagers-sig, 4 weeks
> ago
>   @openstack-sig, apevec, orphan
>
> python-designateclient@openstack-sig, apevec, orphan   4 weeks
> ago
> python-magnumclient   @epel-packagers-sig, 4 weeks
> ago
>   @openstack-sig, apevec, orphan
>
> python-pygeoip@infra-sig, orphan   4 weeks
> ago
> python-pypet  orphan   0 weeks
> ago
> python-simplebayes@python-packagers-sig, orphan4 weeks
> ago
> python-sphinxcontrib-apidoc   @epel-packagers-sig, 2 weeks
> ago
>   @openstack-sig, orphan
>
> rawstudio orphan   0 weeks
> ago
> rubygem-serialportorphan   5 weeks
> ago
> splintorphan   0 weeks
> ago
> startdde  @deepinde-sig, @go-sig,  3 weeks
> ago
>   cheeselee, orphan, zsun
>
>
> The following packages require above mentioned packages:
> Depending on: deepin-control-center (8), status change: 2025-04-06 (2
> weeks ago)
> deepin-file-manager (maintained by: @deepinde-sig, cheeselee,
> topazus, zsun)
> deepin-desktop-6.0.56-8.fc43.x86_64 requires
> deepin-control-center = 6.0.62-4.fc43, deepin-session-ui = 6.0.22-1.fc42
>
> deepin-network-core (maintained by: @deepinde-sig, cheeselee, zsun)
> deepin-network-core-2.0.32-2.fc42.src requires
> cmake(DdeControlCenter) = 6.0.44, cmake(DdeSessionShell)
> de

Re: Orphaned packages looking for new maintainers

2025-07-29 Thread Steven A. Falco 

On 7/28/25 10:36 PM, maxwell--- via devel-announce wrote:


nng   orphan   3 weeks ago


Taken, because KiCad needs it.

Steve

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-07-29 Thread Christiano Anderson 

On 29/07/2025 04:36, maxwell--- via devel-announce wrote:


python-geojsonorphan   3 weeks ago


I took this one


Christiano Anderson
Mastodon: https://chaos.social/@canderson
https://christiano.dev
--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-07-28 Thread Maxwell G 

Hi everyone,

I have some updates about the orphaned packages process. Feedback is 
always welcome!


=== IMPORTANT REMINDER ===

Please make sure to pay special attention to the orphaned packages 
report [1]. There are many more packages there than usual in part due to 
nonresponsive maintainer processes. There is also a special note about 
Golang packages at the beginning of the report that may impact your 
packages.


=== Comps groups ===

Recently, Fedora Atomic image builds broke [2] due to the retirement of 
fros that was orphaned and not picked up within six weeks. I suggested 
adding a section to this report that lists orphaned packages that are 
part of comps groups or that are dependents of packages include in comps 
groups to help catch issues like this earlier. If anybody would like to 
contribute that change to
releng/scripts/orphaned-packages-process/find_unblocked_orphans.py [3] 
(my time to work on this is currently limited) or has other ideas about 
preventing issues like this, please chime in.


I believe that occasionally breaking packages ensures that this process 
actually fulfills its purpose of removing unmaintained packages from the 
distribution, but I obviously don't want to break composes and create 
extra work for Releng and QA if these issues can be avoided. There are 
ongoing discussions about issues with packages retirements in the releng 
tracker [4].


=== Less important updates about the way these reports are processed ===

On 7/28/25 9:36 PM, [email protected] wrote:

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.


Note that, since I took over the reports a year and a half ago, the 
emails have only been sent directly to co-maintainers of the orphaned 
packages, not of any of the packages that depend on orphans, due to a 
scripting error. I only identified the problem recently, but I have 
decided not to fix it yet, as due to the current amount of orphans, I 
worry that sending emails with ~300 addresses BCCed will make my email 
hosting provider unhappy.


Also, as of last month, I no longer not use the @fedoraproject.org 
aliases to send direct copies of the reports and instead query FASJSON 
manually for addresses for better reliability and to avoid issues I've 
had with rejected emails when using the aliases (although I hope 
changing my domain's SPF records will remedy this) [5]. Members of SIG 
co-maintainers also receive direct copies of these reports to the emails 
they have listed in FAS. I no longer send to the private packaging SIG 
mailing lists as these are usually only set up to receive mails from 
Bugzilla and reject or moderate other messages.


Feedback about the way the reports are sent is always welcome.

Best,
Maxwell


[1] https://a.gtmx.me/orphans/orphans.txt

[2] https://pagure.io/releng/failed-composes/issue/8412

[3] 
https://pagure.io/releng/blob/main/f/scripts/orphaned-packages-process/find_unblocked_orphans.py. 
Please apply changes on top of 
https://pagure.io/releng/pull-request/12840 to avoid conflicts.


[4] https://pagure.io/releng/issue/11957

[5] 
https://git.sr.ht/~gotmax23/fedora-scripts/tree/main/item/get_fas_mail.py

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-06-17 Thread Vitaly Zaitsev via devel 

On 17/06/2025 10:36, Cristian Le via devel wrote:

Why not retire and obsolute them with the psi-plus package?


I don't want to obsolete it by the psi-plus package because users won't 
be happy if all their accounts/messages suddenly disappear.


Psi-plus has its own profiles and settings and can't import them 
automatically from the original Psi client.


--
Sincerely,
  Vitaly Zaitsev ([email protected])
--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-06-17 Thread Cristian Le via devel 

On 2025/06/17 9:32, Vitaly Zaitsev via devel wrote:

I orphaned it because it's not maintained. Psi-plus is now the primary 
upstream from the same authors.

Why not retire and obsolute them with the psi-plus package?
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-06-17 Thread Vitaly Zaitsev via devel 

On 17/06/2025 09:38, Benson Muite wrote:

Ok. Orphaned.


jdns is also no longer needed, since psi-plus doesn't use it anymore.

--
Sincerely,
  Vitaly Zaitsev ([email protected])
--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-06-17 Thread Benson Muite 


On Tue, Jun 17, 2025, at 10:32 AM, Vitaly Zaitsev via devel wrote:
> On 17/06/2025 09:10, Benson Muite wrote:
>>> psi   orphan, slankes  0 weeks 
>>> ago
>> Taken
>
> I orphaned it because it's not maintained. Psi-plus is now the primary 
> upstream from the same authors.

Ok. Orphaned.
>
> -- 
> Sincerely,
>Vitaly Zaitsev ([email protected])
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-06-17 Thread Vitaly Zaitsev via devel 

On 17/06/2025 09:10, Benson Muite wrote:

psi   orphan, slankes  0 weeks ago

Taken


I orphaned it because it's not maintained. Psi-plus is now the primary 
upstream from the same authors.


--
Sincerely,
  Vitaly Zaitsev ([email protected])
--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-06-17 Thread Benson Muite 
On Tue, Jun 17, 2025, at 12:46 AM, maxwell--- via devel-announce wrote:
> Report started at 2025-06-16 20:59:14 UTC

> jdns  orphan   0 weeks 
> ago  
Taken

> psi   orphan, slankes  0 weeks 
> ago  
Taken

> xsd   orphan, sagitter, tdawson5 weeks 
> ago  
taken
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-06-16 Thread Miro Hrončok 

On 16. 06. 25 23:46, [email protected] wrote:

Depending on: levmar (3), status change: 2025-05-06 (5 weeks ago)
meshlab (maintained by: churchyard, spot)
meshlab-2023.12-11.fc43.src requires levmar-devel = 2.6-18.fc42
meshlab-2023.12-11.fc43.x86_64 requires 
liblevmar.so.2.6()(64bit)

sourcextractor++ (maintained by: aalvarez)
sourcextractor++-1.0.1-2.fc43.src requires levmar-devel = 
2.6-18.fc42
sourcextractor++-1.0.1-2.fc43.x86_64 requires 
liblevmar.so.2.6()(64bit)

teem (maintained by: @neuro-sig, music)
teem-1.11.0-81.fc43.src requires levmar-devel = 2.6-18.fc42


Took this one. Co-maintainers welcome.

--
Miro Hrončok
--
Phone: +420777974800
Fedora Matrix: mhroncok

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-06-07 Thread Richard W.M. Jones 
On Sat, Jun 07, 2025 at 09:25:47AM -0600, Jerry James wrote:
> On Sat, Jun 7, 2025 at 8:45 AM Richard W.M. Jones  wrote:
> > On Fri, Jun 06, 2025 at 02:52:06PM -0500, maxwell--- via devel-announce 
> > wrote:
> > > ocaml-odocdefolos, orphan  1 
> > > weeks ago
> >
> > I thought this one might be used by more packages, but I think the
> > only dependency chain is ocaml-odoc -> ocaml-sedlex -> haxe.
> 
> It isn't even used there.  The usage in ocaml-sedlex is conditioned on
> "%if %{with docs}" and higher up you'll see "%bcond docs 0".
> 
> > I think we removed the dependency from lots of packages in the past.
> > For example (taken at random):
> 
> That is correct; no Fedora packages depend on ocaml-odoc anymore.
> 
> > I'm not sure if odoc is still used somehow implicitly that I'm not
> > understanding, or did we just get rid of the documentation?
> > (I actually favour the latter, package documentation generated from
> > source files like this isn't usually very useful, and adds little
> > value over simply looking at the *.mli files.)
> 
> Right, we no longer generate documentation for packages that require
> ocaml-odoc.  We do still generate documentation for a few packages
> that use ocaml-ocamldoc to do so.

Understood!  So I guess we can just let this one fall out of Fedora,
unless someone (defolos maybe) wishes to become the owner.

I always think it's a bit weird that we count packages as orphaned
when there are still maintainers ...

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-06-07 Thread Jerry James 
On Sat, Jun 7, 2025 at 8:45 AM Richard W.M. Jones  wrote:
> On Fri, Jun 06, 2025 at 02:52:06PM -0500, maxwell--- via devel-announce wrote:
> > ocaml-odocdefolos, orphan  1 weeks 
> > ago
>
> I thought this one might be used by more packages, but I think the
> only dependency chain is ocaml-odoc -> ocaml-sedlex -> haxe.

It isn't even used there.  The usage in ocaml-sedlex is conditioned on
"%if %{with docs}" and higher up you'll see "%bcond docs 0".

> I think we removed the dependency from lots of packages in the past.
> For example (taken at random):

That is correct; no Fedora packages depend on ocaml-odoc anymore.

> I'm not sure if odoc is still used somehow implicitly that I'm not
> understanding, or did we just get rid of the documentation?
> (I actually favour the latter, package documentation generated from
> source files like this isn't usually very useful, and adds little
> value over simply looking at the *.mli files.)

Right, we no longer generate documentation for packages that require
ocaml-odoc.  We do still generate documentation for a few packages
that use ocaml-ocamldoc to do so.
-- 
Jerry James
http://www.jamezone.org/
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-06-07 Thread Richard W.M. Jones 
On Fri, Jun 06, 2025 at 02:52:06PM -0500, maxwell--- via devel-announce wrote:
> ocaml-odocdefolos, orphan  1 weeks 
> ago  

I thought this one might be used by more packages, but I think the
only dependency chain is ocaml-odoc -> ocaml-sedlex -> haxe.

I think we removed the dependency from lots of packages in the past.
For example (taken at random):

https://src.fedoraproject.org/rpms/ocaml-ptmap/c/214f40d2863e8a563d4c95ab63fdf5e226fe04b6?branch=rawhide

I'm not sure if odoc is still used somehow implicitly that I'm not
understanding, or did we just get rid of the documentation?
(I actually favour the latter, package documentation generated from
source files like this isn't usually very useful, and adds little
value over simply looking at the *.mli files.)

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual machines.  Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-06-06 Thread Davide Cavalca 

On 2025-06-06 12:52, maxwell--- via devel-announce wrote:
bmap-toolsorphan   4 
weeks ago


I picked this up, planning to get it updated to the new upstream that's 
under Yocto.


Cheers
Davide
--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-30 Thread Orion Poplawski 

On 5/30/25 03:55, Sandro wrote:

On 30-05-2025 10:27, Carl George wrote:

FYI, the epel-packagers-sig group is deprecated and should no longer
be added to packages.


Thank you for pointing that out. I didn't know. I wish I had or that it 
had been pointed out when I did just that and mentioning doing so in 
response to a few EPEL10 branching requests.


Is there an alternative? Personally, I think it would be better having a 
group assigned than just a single person.


-- Sandro



Yeah, I just learned about that now - after having built a couple of 
packages that had been assigned to the sig and requesting it be added to 
a few more.  Is there a discussion somewhere that can be read?


Thanks.

--
Orion Poplawski
he/him/his  - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane   [email protected]
Boulder, CO 80301 https://www.nwra.com/
--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-30 Thread Sandro 

On 30-05-2025 10:27, Carl George wrote:

FYI, the epel-packagers-sig group is deprecated and should no longer
be added to packages.


Thank you for pointing that out. I didn't know. I wish I had or that it 
had been pointed out when I did just that and mentioning doing so in 
response to a few EPEL10 branching requests.


Is there an alternative? Personally, I think it would be better having a 
group assigned than just a single person.


-- Sandro

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-30 Thread Carl George 
Indeed, I was added as a co-maintainer originally to take care of the
EPEL 10 build.  I'm happy to be set as the default EPEL bugzilla
assignee, I just can't do it myself since only the main admin can do
that.

FYI, the epel-packagers-sig group is deprecated and should no longer
be added to packages.

https://docs.fedoraproject.org/en-US/epel/epel-packagers-sig/

On Tue, May 27, 2025 at 1:47 AM Sandro  wrote:
>
> On 26-05-2025 23:59, Bill Pemberton via devel wrote:
> >> ack   carlwgeorge, orphan  1 weeks 
> >> ago
> >
> > I'll take this, at least for Fedora.  When I claimed it in 
> > src.fedoraproject.org it also gave me the ownership of the EPEL packages -- 
> > I don't maintain any EPEL packages anymore.
>
> It looks like your co-maintainer, carlwgeorge, took care of building the
> package for epel10 recently. I'd hand over the EPEL part to him. You may
> also want to add epel-packagers-sig as a collaborator for epel*.
>
> -- Sandro
>
> --
> ___
> devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 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/[email protected]
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue



-- 
Carl George

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-29 Thread Robby Callicotte via devel 
On Thursday, May 22, 2025 3:55:55 PM Central Daylight Time maxwell--- via 
devel-announce wrote:
> fedora-review-plugin-java orphan   1 weeks
> ago
> python-cerberus   ngompa, orphan   2 weeks 
ago  

I've taken these.

--
Robby Callicotte


-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-29 Thread Neal Gompa 
On Thu, May 22, 2025 at 4:56 PM  wrote:
>
[...]
> yarnpkg   @epel-packagers-sig, ngompa, 2 weeks ago
>   orphan, smani

Took this one since it's kind of critical, but co-maintainers welcome!



--
真実はいつも一つ！/ Always, there's only one truth!
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-27 Thread Michel Lind 
On Thu, 2025-05-22 at 15:55 -0500, maxwell--- via devel-announce wrote:
> 
> Depending on: python-paginate (6), status change: 2025-05-16 (0 weeks
> ago)
>   mkdocs-material (maintained by: @mkdocs-sig, dcavalca)
>   mkdocs-material-9.6.12-1.fc43.noarch requires
> python3.13dist(mkdocs-material-extensions) = 1.3.1,
> python3.13dist(paginate) = 0.5.6
>   mkdocs-material-9.6.12-1.fc43.src requires
> python3dist(mkdocs-git-revision-date-localized-plugin) = 1.3,
> python3dist(mkdocs-material-extensions) = 1.3.1, python3dist(mkdocs-
> rss-plugin) = 1.17.1, python3dist(paginate) = 0.5.6
>   mkdocs-material+git-9.6.12-1.fc43.noarch requires
> python3.13dist(mkdocs-git-revision-date-localized-plugin) = 1.3
>   mkdocs-material+recommended-9.6.12-1.fc43.noarch
> requires python3.13dist(mkdocs-rss-plugin) = 1.17.1
> 
I've taken python-paginate and added the mkdocs-sig group to it.

Best regards,

-- 
 _o) Michel Lind
_( ) identities:
https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2
 README: https://fedoraproject.org/wiki/User:Salimma#README
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-26 Thread Sandro 

On 26-05-2025 23:59, Bill Pemberton via devel wrote:

ack   carlwgeorge, orphan  1 weeks ago


I'll take this, at least for Fedora.  When I claimed it in 
src.fedoraproject.org it also gave me the ownership of the EPEL packages -- I 
don't maintain any EPEL packages anymore.


It looks like your co-maintainer, carlwgeorge, took care of building the 
package for epel10 recently. I'd hand over the EPEL part to him. You may 
also want to add epel-packagers-sig as a collaborator for epel*.


-- Sandro

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-26 Thread Bill Pemberton via devel 
> ack   carlwgeorge, orphan  1 weeks 
> ago  

I'll take this, at least for Fedora.  When I claimed it in 
src.fedoraproject.org it also gave me the ownership of the EPEL packages -- I 
don't maintain any EPEL packages anymore.

-- 
Bill
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-23 Thread Gwyn Ciesla via devel 


Done, thank you!
-- 
Gwyn Ciesla
she/her/hers
 
in your fear, seek only peace 
in your fear, seek only love
-d. bowie


Sent with Proton Mail secure email.

On Friday, May 23rd, 2025 at 2:58 PM, Alexander Ploumistos 
 wrote:

> Hi Gwyn,
> 

> On Fri, May 23, 2025 at 7:01 PM Gwyn Ciesla via devel
> [email protected] wrote:
> 

> > I took a bunch of things, I had a list but failed to save it. As always, 
> > co-maintainers welcome.
> 

> 

> Feel free to add me (alexpl) as a co-maintainer to muParser.
> --
> ___
> devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> 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/[email protected]
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue

signature.asc
Description: OpenPGP digital signature
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-23 Thread Alexander Ploumistos 
Hi Gwyn,

On Fri, May 23, 2025 at 7:01 PM Gwyn Ciesla via devel
 wrote:
>
> I took a bunch of things, I had a list but failed to save it. As always, 
> co-maintainers welcome.

Feel free to add me (alexpl) as a co-maintainer to muParser.
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-23 Thread Hans de Goede 
Hi All,

On 22-May-25 10:55 PM, maxwell--- via devel-announce wrote:

> ogre  dtimms, ignatenkobrain, orphan   4 weeks 
> ago  

I've taken ogre since funguloids depends on it, co-maintainers very much 
welcome.

Regards,

Hans

-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-23 Thread Steven A. Falco 

On 5/22/25 04:55 PM, maxwell--- via devel-announce wrote:

po4a  orphan, sharkcz  1 weeks ago


I've taken this one because KiCad depends on it.  It looks like a lot of other 
packages depend on it too.  Co-maintainers are welcome.

Steve

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-23 Thread Artur Frenszek-Iwicki 
> icon  orphan   2 weeks 
> ago  
Taking this. Will try to update it to latest version over the weekend.

A.FI.
-- 
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Orphaned packages looking for new maintainers

2025-05-23 Thread Peter Hanecak 

Hello,

On 5/22/25 22:55, [email protected] wrote:

miglayout hanecak, orphan  2 weeks ago


I took this one.

Sincerely

Peter

--
___
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

  1   2   3   4   5   6   7   8   9   10   >