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 d
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 EPE
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 package
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 Callic
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!
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(mkd
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
> 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
--
_
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
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 mai
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
--
__
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
--
___
> icon orphan 2 weeks
> ago
Taking this. Will try to update it to latest version over the weekend.
A.FI.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
Hello,
On 5/22/25 22:55, maxw...@gtmx.me wrote:
miglayout hanecak, orphan 2 weeks ago
I took this one.
Sincerely
Peter
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email
python-backcall @epel-packagers-sig, @python-0 weeks ago
packagers-sig, orion, orphan,
salimma
python-pathtools @python-packagers-sig, orphan2 weeks ago
> ektype-mukta-fontsorphan 2 weeks
> ago
> libxeddsa orphan 2 weeks
> ago
> poezioorphan 2 weeks
> ago
> python-slixmpporph
On Friday, May 9, 2025 1:20:50 PM Central Daylight Time Kevin Fenzi wrote:
> Per their request, I've removed them from all their packages.
>
> Here's the list of packages needing a new main admin:
> (Note that some may have active co-maintainers)
>
> rpms/adns
> rpms/anyremote
> rpms/apt
> rpms/c
Per their request, I've removed them from all their packages.
Here's the list of packages needing a new main admin:
(Note that some may have active co-maintainers)
rpms/adns
rpms/anyremote
rpms/apt
rpms/clamav
rpms/containerd
rpms/ddnet
rpms/debconf
rpms/debhelper
rpms/debmirror
rpms/debootstrap
python-emoji orphan 0 weeks ago
I took python-emoji.
-- Sandro
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code o
Have take XMPP related packages. Thanks to fantom for maintaining them.
If you use any of them and would be interested in creating a SIG to ease
maintenance,
please let me know.
On Mon, May 5, 2025, at 7:52 AM, maxwell--- via devel-announce wrote:
> Report started at 2025-05-05 03:00:32 UTC
>
tmx.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://package
chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
On Sunday, March 23, 2025 10:12:09 AM Central Daylight Time maxwell--- via
devel-announce wrote:
> IMPORTANT NOTE: I forgot to process the orphaned packages and send the
> report that was due the second week of March, so some packages have been
> orphaned for more than six weeks but
chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
IMPORTANT NOTE: I forgot to process the orphaned packages and send the report
that was due the second week of March, so some packages have been orphaned for
more than six weeks but were not announced as usual. I will wait until
Wednesday to retire the remaining packages orphaned for 6+ weeks
On Wed, Feb 26, 2025 at 08:10:20AM -0800, Davide Cavalca wrote:
> On 2025-02-24 17:33, maxw...@gtmx.me wrote:
> > simh orphan 0
> > weeks ago
>
> I picked this up and somewhat coaxed it into building again, but I'd be
> happy to have some co-m
On 2025-02-24 17:33, maxw...@gtmx.me wrote:
simh orphan 0
weeks ago
I picked this up and somewhat coaxed it into building again, but I'd be
happy to have some co-maintainers if anybody's interested.
Cheers
Davide
--
_
On Tuesday, 25 February 2025 at 02:33, maxw...@gtmx.me wrote:
> Report started at 2025-02-25 01:00:06 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, pleas
On Wed, Jan 22, 2025 at 8:45 AM Ondrej Mosnáček wrote:
>
> On Tue, 21 Jan 2025 at 21:42, maxwell--- via devel-announce
> wrote:
> >
> > Report started at 2025-01-21 20:00:10 UTC
> >
> > The following packages are orphaned and will be retired when they
> > are orphaned for six weeks, unless someon
On Tue, 21 Jan 2025 at 21:42, maxwell--- via devel-announce
wrote:
>
> Report started at 2025-01-21 20:00:10 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
On 15-01-2025 01:00, maxwell--- via devel-announce wrote:
python-pep440
Adopted as it's needed by a bunch of packages I (co-)maintain.
-- Sandro
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@l
I took the golang cgroup ones, since I'm familiarized with it, as well
as with golang. Also trying to start getting into golang packages.
On 1/14/25 5:00 PM, maxwell--- via devel-announce wrote:
olang(github.com/containerd/containerd/cio) = 1.6.23-1.fc41,
golang(github.com/containerd/container
Hi Jerry,
I made you main admin of the three projects. I stayed as admin in case
you need a hand.
Thank you,
Carlos R.F.
On 1/8/25 4:07 PM, Jerry James wrote:
On Wed, Jan 8, 2025 at 8:29 AM Carlos Rodriguez-Fernandez
wrote:
I'm taking because of their dependencies:
* lrcalc
* Singular
On Wed, Jan 8, 2025 at 8:29 AM Carlos Rodriguez-Fernandez
wrote:
> I'm taking because of their dependencies:
>
> * lrcalc
>
> * Singular
>
> * imlib2
>
> * cliquer
>
>
> If any of the previous admin, committers, or collaborators to those
> packages want to take it, please let me know.
I have cont
On Tue, 2025-01-07 at 23:46 -0600, maxwell--- via devel-announce wrote:
> Report started at 2025-01-08 05:00:11 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 re
Il 08/01/25 06:46, maxwell--- via devel-announce ha scritto:
> python-pyramid_sawing orphan 0 weeks ago
Taking it, since it is used by Bodhi.
Mattia
--
___
devel mailing list -- devel@lists.fedoraproject.org
To u
,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status
Change
Sin
ns/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-das
chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
On Wed, Dec 18, 2024 at 6:35 PM Clemens Lang wrote:
>
> I realized that after I clicked send, but I don’t think it really makes a
> difference.
> The main admin for many of the packages maintained by the crypto team is no
> longer the person that takes care of the tickets by default.
>
> For exa
On Wed, Dec 18, 2024 at 10:55:13AM -0600, Jason Tibbitts wrote:
> > maxwell--- via devel-announce
> > writes:
>
> > fedscm-admin cqi, ignatenkobrain, limb, 3 weeks
> > ago
> > mohanboddu, orphan, tibbs
> >
Hi,
> On 18. Dec 2024, at 17:51, Fabio Valentini wrote:
>
> On Wed, Dec 18, 2024 at 10:43 AM Clemens Lang wrote:
>>
>> See https://src.fedoraproject.org/rpms/stunnel, or
>> https://src.fedoraproject.org/rpms/gnutls, owned by @crypto-team.
>
> Looks like there are multiple different things be
h a proper
> > > > reason:
> > > > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> > >
> > > I see lots of packages that are orphaned, but have one or more
> > > co-maintainer. Sometimes they may quickly take the package, sometimes they
>
> maxwell--- via devel-announce
> writes:
> fedscm-admin cqi, ignatenkobrain, limb, 3 weeks
> ago
> mohanboddu, orphan, tibbs
>
I can't think of any reason this shouldn't simply be retired. All of
the
On Wed, Dec 18, 2024 at 10:43 AM Clemens Lang wrote:
>
> Hi Neal,
>
> > On 18. Dec 2024, at 10:21, Neal Gompa wrote:
> >
> > One thing I hope we never do is allow something to be principally
> > owned by groups as a rule.
>
> See https://src.fedoraproject.org/rpms/stunnel, or
> https://src.fedor
On Wed, Dec 18, 2024 at 3:40 PM Miroslav Suchý wrote:
>
> Dne 18. 12. 24 v 2:25 odp. Emmanuel Seyman napsal(a):
> > If there are several co-maintainers, which one do you choose?
>
> Anyone.
That's literally the worst way to handle this IMO.
Packages that get orphaned due to long-standing "issues
t would be different. But I cannot change
it. And we should not deny it.
BTW what problem do you want to fix actually? Having orphaned packages
on itself is not a problem IMHO. Having owned packages with unresponsive
maintainers *is* real problem OTOH.
I your SPDX case, you should be hap
Dne 18. 12. 24 v 2:25 odp. Emmanuel Seyman napsal(a):
If there are several co-maintainers, which one do you choose?
Anyone.
If one of those co-maintainers is there to maintain a specific part
of the package (a given feature, bindings to $LANGUAGE, ...), how do
you ensure he is not promoted t
On 18. 12. 24 12:53, Miroslav Suchý wrote:
Dne 18. 12. 24 v 10:53 dop. Miro Hrončok napsal(a):
When the package is orphaned (e.g. because the buzgilla that said it does not
install was ignored by all 8 maintainers), it would be assigned to one of
them, we are at 7 maintainers. It would take 8 a
aprsd orphan 4
weeks ago
xdemorse orphan 4
weeks ago
xpsk31orphan 4
weeks ago
I've taken these.
Cheers
Davide
--
_
* Miroslav Suchý [18/12/2024 12:59] :
>
> emails. And instead of putting the package on the list, it would the API
> call to pagure and assign the package to another co-maintainer. So there
> will be alway one main-maintainer.
If there are several co-maintainers, which one do you choose?
If one o
gt; I see lots of packages that are orphaned, but have one or more
> > co-maintainer. Sometimes they may quickly take the package, sometimes they
> > may be on holidays.
> >
> > Would you object if promote a co-maintainer to main maintainer for orphaned
> > pa
Dne 18. 12. 24 v 10:53 dop. Daniel P. Berrangé napsal(a):
I don't accept that co-maintainers are (or should be assumed to be)
"typically" non-responsive. That is a depressing denigration of
many Fedora co-maintainer's work.
During this year, as part of my work on SPDX, I opened several hundreds
Dne 18. 12. 24 v 10:51 dop. Vít Ondruch napsal(a):
Also making `ruby-packagers-sig` as a primary contact is problematic, because the group cannot e.g. retire such
package without opening rel-eng ticket.
Valid concern. Can be solved by skipping @ID. So only real people would be
assigned.
--
Mi
Dne 18. 12. 24 v 10:03 dop. Daniel P. Berrangé napsal(a):
What would you suggest
if there are currently 2 (or more) "admin"s (co-maintainers).
No. I thinking about implementation in the script that generates
"Orphaned packages looking for new maintainers"
emails. And in
Dne 18. 12. 24 v 10:53 dop. Miro Hrončok napsal(a):
When the package is orphaned (e.g. because the buzgilla that said it does not install was ignored by all 8
maintainers), it would be assigned to one of them, we are at 7 maintainers. It would take 8 another weeks to orphan it
again, and again,
Daniel P. Berrangé venit, vidit, dixit 2024-12-18 10:53:00:
> On Wed, Dec 18, 2024 at 10:43:33AM +0100, Vít Ondruch wrote:
> > I would object! We've been there prior we arrived to the current workflow.
> > And the typical situation was that such package was moved from one
> > non-responsive maintai
-maintainer to main maintainer for orphaned
packages and make it a rule?
I would, as repeatedly said in the past.
Let's say we have a package that has 8 listed maintainers.
When the package is orphaned (e.g. because the buzgilla that said it does not
install was ignored by all 8 maintainers
On Wed, Dec 18, 2024 at 10:43:33AM +0100, Vít Ondruch wrote:
> I would object! We've been there prior we arrived to the current workflow.
> And the typical situation was that such package was moved from one
> non-responsive maintainer to the other non-responsive maintainer. With my
> handle beginni
Dne 18. 12. 24 v 10:42 Clemens Lang napsal(a):
Hi Neal,
On 18. Dec 2024, at 10:21, Neal Gompa wrote:
One thing I hope we never do is allow something to be principally
owned by groups as a rule.
See https://src.fedoraproject.org/rpms/stunnel, or
https://src.fedoraproject.org/rpms/gnutls, ow
tainer for
orphaned packages and make it a rule?
...
Here is random example from today's announce of orphaned packages:
Package (co)maintainers Status Change
Singular
Hi Neal,
> On 18. Dec 2024, at 10:21, Neal Gompa wrote:
>
> One thing I hope we never do is allow something to be principally
> owned by groups as a rule.
See https://src.fedoraproject.org/rpms/stunnel, or
https://src.fedoraproject.org/rpms/gnutls, owned by @crypto-team.
> As a general pract
o now with a proper
> > > > reason:
> > > > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> > >
> > > I see lots of packages that are orphaned, but have one or more
> > > co-maintainer. Sometimes they may quickly take the package, sometimes they
> &g
I see lots of packages that are orphaned, but have one or more
> > co-maintainer. Sometimes they may quickly take the package, sometimes they
> > may be on holidays.
> >
> > Would you object if promote a co-maintainer to main maintainer for orphaned
> > packages and ma
package, sometimes they
> may be on holidays.
>
> Would you object if promote a co-maintainer to main maintainer for orphaned
> packages and make it a rule?
Broadly it is a good idea, but with impl questions due to Pagure.
IIUC Pagure only allows for 1 "main admin" (owner)
packages and make it a rule?
...
Here is random example from today's announce of orphaned packages:
Package (co)maintainers Status
Change
Sin
Am 09.12.24 um 15:30 schrieb Stephen Gallagher:
On Sat, Dec 7, 2024 at 12:21 PM Carlos Rodriguez-Fernandez
wrote:
I took sparse, and http-parser.
http-parser in particular is a dead project upstream. However, there is a good
set of packages depending on it. There are also past contributors.
It does build without that dependency :)
The tests were passing but I had to kill it because it was using lots of
memory, and as a result, my machine was running out of RAM, and the
oomkiller was out doing its thing.
On 12/10/24 7:38 AM, Fabio Valentini wrote:
On Tue, Dec 10, 2024 at 5:28 A
oject.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,
>
On Tue, Dec 10, 2024 at 5:28 AM Carlos Rodriguez-Fernandez
wrote:
>
> I agree. This dead package has probably security issues waiting to be
> discovered.
>
> There are the other projects as well that would need some relook at its
> http-parser dependency and see if it can be dropped: julia, cantor
On Tue, Dec 10, 2024 at 9:26 AM Petr Špaček wrote:
>
> On 09. 12. 24 15:32, Stephen Gallagher wrote:
> > On Mon, Dec 9, 2024 at 9:30 AM Stephen Gallagher wrote:
> >> On Sat, Dec 7, 2024 at 12:21 PM Carlos Rodriguez-Fernandez
> >> wrote:
> >>> I took sparse, and http-parser.
> >>>
> >>> http-parse
I agree. This dead package has probably security issues waiting to be
discovered.
There are the other projects as well that would need some relook at its
http-parser dependency and see if it can be dropped: julia, cantor, and
LabPlot.
Regards,
Carlos R.F.
On 12/9/24 7:30 AM, Stephen Gall
On Mon, Dec 9, 2024 at 9:30 AM Stephen Gallagher wrote:
>
> On Sat, Dec 7, 2024 at 12:21 PM Carlos Rodriguez-Fernandez
> wrote:
> >
> > I took sparse, and http-parser.
> >
> > http-parser in particular is a dead project upstream. However, there is a
> > good set of packages depending on it. Ther
On Sat, Dec 7, 2024 at 12:21 PM Carlos Rodriguez-Fernandez
wrote:
>
> I took sparse, and http-parser.
>
> http-parser in particular is a dead project upstream. However, there is a
> good set of packages depending on it. There are also past contributors. If
> any of the past contributors want to
chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
On 07. 11. 24 22:41, maxw...@gtmx.me wrote:
python-httptools (maintained by: aekoroglu)
python-httptools-0.6.0-6.fc41.src requires http-parser-devel =
2.9.4-12.fc41
python3-httptools-0.6.0-6.fc41.x86_64 requires
libhttp_parser.so.2()(64bit)
If http-par
chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
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
>
&g
chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
On Tue, Oct 8, 2024 at 6:32 PM Peter Robinson wrote:
>
> Hi Fabio,
>
> > > rust-sval @rust-sig, orphan0
> > > weeks ago
> > > rust-sval_buffer @rust-sig, orphan0
> > > weeks ago
> > > rust-sval_derive @rust
Hi Fabio,
> > rust-sval @rust-sig, orphan0 weeks
> > ago
> > rust-sval_buffer @rust-sig, orphan0 weeks
> > ago
> > rust-sval_derive @rust-sig, orphan0 weeks
> > ago
> > rust-sval_derive_mac
On Tue, Oct 8, 2024 at 6:07 PM wrote:
(snip)
> rust-sval @rust-sig, orphan0 weeks ago
> rust-sval_buffer @rust-sig, orphan0 weeks ago
> rust-sval_derive @rust-sig, orphan0 weeks ago
> rust-s
chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
maxw...@gtmx.me kirjoitti 23.9.2024 klo 21.38:
Report started at 2024-09-23 18:00:57 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 prop
I've taken pmix and pycanberra. Co-maintainers welcome.
signature.asc
Description: OpenPGP digital signature
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Co
chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
On Sat, Aug 03, 2024 at 10:05:55AM -0500, maxw...@gtmx.me wrote:
> Report started at 2024-08-03 14:00:44 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, pl
Hi Neil,
just expressing a bit of gratitude for slurm getting adopted. I've had the fun of trying
to roll out long-time-since-last-packaged older HPC schedulers (son of gridengine), and,
this is cool, especially seeing that you're active in the Rocky HPC SIG. I think that
already packages slur
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
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
rphans.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-das
n 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.
gt;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 a
t;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
On Sat, Aug 03, 2024 at 10:13:52AM GMT, Maxwell G wrote:
>
> On 8/3/24 10:05 AM, maxw...@gtmx.me wrote:
> > Report started at 2024-08-03 14:00:44 UTC
> >
> > The following packages are orphaned and will be retired when they
> > are orphaned for six weeks, unless someone adopts them.
>
> The pack
On 8/3/24 10:05 AM, maxw...@gtmx.me wrote:
Report started at 2024-08-03 14:00:44 UTC
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them.
The packages listed as orphaned for 6 weeks have already been retired in
distgit but
chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
chains,
see https://packager-dashboard.fedoraproject.org/
For all orphaned packages,
see https://packager-dashboard.fedoraproject.org/orphan
Package (co)maintainers Status Change
Dne 02. 07. 24 v 9:45 odp. maxw...@gtmx.me napsal(a):
python-orderedset orphan 2 weeks ago
Note that we have python-ordered-set that is well maintained. Same interface.
Different implementation.
--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT
1 - 100 of 1513 matches
Mail list logo
