Decommissioned Pagure still used for base Fedora packages?

[Henryk Paluch]

Hello!

I'm thinking about taking over few packages (to fix broken Avocado-VT 
stuff) but I'm already confused at start with contradictory statements 
on Pagure obsolescence.

On https://fedoramagazine.org/whats-next-for-pagure-io/ it says:
> Pagure itself as a project is hosted on pagure.io,
> and that service is going to be decommissioned at the
> end of July 2026.
> ...
> Note: Do not expect to be able to log in to pagure.io after July 2026.

But when I look on package of my interest - python-aexpect:

Latest Koji build (July 2026) on 
https://koji.fedoraproject.org/koji/buildinfo?buildID=3049903 is showing:
> Source

git+https://src.fedoraproject.org/rpms/python-aexpect.git#becebb891c87bf7915a0fb...

But https://src.fedoraproject.org/rpms/python-aexpect is clearly on 
Pagure and active - last commit from July 2026 - 
https://src.fedoraproject.org/rpms/python-aexpect/c/becebb891c87bf7915a0fb92...

Would someone explain what is correct?

1. Are base Fedora packages using Pagure or Forgejo (or we are in mixed 
state)?
2. Are there any plans to move python-aexpect from Pagure to Forgejo?

Regards
   --Henryk Paluch

[Artur Frenszek-Iwicki]

Hi Henryk,

"decomissioning of pagure" refers to the Pagure instance powering
pagure.io. The Pagure instance powering src.fedoraproject.org
is here to stay for now.

The long term plan is to switch src.fp.o to Forgejo as well, but that's
a work in progress, as there are still 1) some features missing
in Forgejo that we really need; 2) some infra issues to iron out.

Someone from the infra team can probably give you more info (or correct
me if I got something wrong), but that's the short version.

Cheers,
Artur FI

[Michael J Gruber]

Henryk Paluch via devel venit, vidit, dixit 2026-08-21 09:31:46:
> Hello!
>
> I'm thinking about taking over few packages (to fix broken Avocado-VT 
> stuff) but I'm already confused at start with contradictory statements 
> on Pagure obsolescence.
>
> On https://fedoramagazine.org/whats-next-for-pagure-io/ it says:
> > Pagure itself as a project is hosted on pagure.io,
> > and that service is going to be decommissioned at the
> > end of July 2026.
> > ...
> > Note: Do not expect to be able to log in to pagure.io after July 2026.
>
> But when I look on package of my interest - python-aexpect:
>
> Latest Koji build (July 2026) on 
> https://koji.fedoraproject.org/koji/buildinfo?buildID=3049903 is showing:
> > Source
>
> git+https://src.fedoraproject.org/rpms/python-aexpect.git#becebb891c87bf7915a0fb...
>
> But https://src.fedoraproject.org/rpms/python-aexpect is clearly on 
> Pagure and active - last commit from July 2026 - 
> https://src.fedoraproject.org/rpms/python-aexpect/c/becebb891c87bf7915a0fb92...
>
> Would someone explain what is correct?
> Are base Fedora packages using Pagure or Forgejo (or we are in mixed
>
> state)?
> 2. Are there any plans to move python-aexpect from Pagure to Forgejo?

It's no surprise that you're confused. That's the result of overly bold
statements like "our new home" and misleading naming like "on pagure",
"our forge". Classical communication failure.

"pagure" is a platform technology, and such is "forgejo".

We used to use two instances of pagure:

- one for our package sources (spec etc), often called "dist-git"
  (that name has its own history), living at src.fedoraproject.org

- one for other Fedora/packaging related stuff, in particular packaging
  tools, new package request tickets, SIGs. This used to live at
  "pagure.io" because how better to confuse people than naming the thing
  by the tool that happens to be used?

The second one has been migrated to a forgejo instance, living at
forge.fedoraproject.org.

Yes, why not repeat the same mistake, at least half-way ("forge"), and
make it worse because tons of people speak of "dist-git" as the "source
forge", "dist-git forge" etc since "forge" is a generic term for a home
for repos of any kind?

So, "dist-git" is still at src.fp.o and running "pagure". There are
plans to migrate to a "forgejo" instance, but this still requires quite
some work. Once it's done, we will have two forgejo instances which both
are "forges of git repos" and which both will host source code and other
packaging related material. One will be named forge.fp.o. Would you
guess which one, if you didn't know the above?

Michael

[Shawn W Dunn]

On Fri, Aug 21, 2026 at 09:54:24AM +0200, Michael J Gruber wrote:
> Henryk Paluch via devel venit, vidit, dixit 2026-08-21 09:31:46:
> > Hello!
> >
> > I'm thinking about taking over few packages (to fix broken Avocado-VT 
> > stuff) but I'm already confused at start with contradictory statements 
> > on Pagure obsolescence.
> >
> > On https://fedoramagazine.org/whats-next-for-pagure-io/ it says:
> > > Pagure itself as a project is hosted on pagure.io,
> > > and that service is going to be decommissioned at the
> > > end of July 2026.
> > > ...
> > > Note: Do not expect to be able to log in to pagure.io after July 2026.
>
> It's no surprise that you're confused. That's the result of overly bold
> statements like "our new home" and misleading naming like "on pagure",
> "our forge". Classical communication failure.
>
> "pagure" is a platform technology, and such is "forgejo".
>
> We used to use two instances of pagure:
>
> one for our package sources (spec etc), often called "dist-git"
> (that name has its own history), living at src.fedoraproject.org
>
> one for other Fedora/packaging related stuff, in particular packaging
> tools, new package request tickets, SIGs. This used to live at
> "pagure.io" because how better to confuse people than naming the thing
> by the tool that happens to be used?
>
> The second one has been migrated to a forgejo instance, living at
> forge.fedoraproject.org.
>
> Yes, why not repeat the same mistake, at least half-way ("forge"), and
> make it worse because tons of people speak of "dist-git" as the "source
> forge", "dist-git forge" etc since "forge" is a generic term for a home
> for repos of any kind?
>
> So, "dist-git" is still at src.fp.o and running "pagure". There are
> plans to migrate to a "forgejo" instance, but this still requires quite
> some work. Once it's done, we will have two forgejo instances which both
> are "forges of git repos" and which both will host source code and other
> packaging related material. One will be named forge.fp.o. Would you
> guess which one, if you didn't know the above?

Yup, clear as mud, and always has been, even before the introduction of
the new forge.fp.o, this was confusing as hell.

[Kevin Fenzi]

Yeah, it's very anoying to me that many people say/type 'pagure' and
they mean some specific instance, but they just assume you know what one
they mean. ;(

In any case as others have noted, 'pagure' is the software.

pagure.io was a general instance of this for people to use. Fedora
related things that were there have moved to the forge.fedoraproject.org
forgejo instance. Other things have moved to other forges (github,
gitlab, coreberg, etc).

src.fedoraproject.org is another instance that is specific to fedora
packages. It has not moved yet.

kevin