Upstream software project

vim-fugitive-pagure

Pagure support for vim-fugitive plugin

About vim-fugitive-pagure

Pagure support for vim-fugitive plugin

This project links 2 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

vim-fugitive-pagure repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.vim-fugitive-pagure: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
vim-fugitive-pagure
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
GPL-2.0-or-later
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Pagure support for :Gbrowse feature provided by vim-fugitive plugin

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package vim-fugitive-pagure

    43 (Fedora 43) (Unspecified): Pagure support for vim-fugitive plugin

    1.5-6.fc43: noarch

    Source: vim-fugitive-pagure

Fedora 44

  1. Package vim-fugitive-pagure

    44 (Fedora 44) (Unspecified): Pagure support for vim-fugitive plugin

    1.5-7.fc44: noarch

    Source: vim-fugitive-pagure

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.