You are not logged in.

#1 2026-07-19 22:30:38

dreieck
Member
Registered: 2012-10-08
Posts: 75

extra/fig2dev: Package update not detected, but also cannot report.

Ahoj,

there is the Arch Linux package 'extra/fig2dev'.

It is out of date since year 2024 ('extra/fig2dev' is at version 3.2.9, upstream has released 3.2.9a).

On the package's website I can no longer flag it out of date; trying to do it via bug report gets the issue report automatically closed because this is not a packaging bug.

The Arch Wiki site "reasons for not beeing a bug" states

A package which is not-up-to-date. Users are not expected to manually flag packages out of date, since this is automated via bumpbuddy and the nvchecker files in each individual repository (see this example in the chromium package).

But the '.nvchecker.toml' file in the PKGBUILD repository for fig2dev seems not to catch the updated version number with 'a':

[fig2dev]
source = "regex"
url = "https://sourceforge.net/projects/mcj/files"
regex = 'fig2dev-(\d+\.\d+\.\d+).tar.xz'

.. so, what to do about it, if the version update is not automatically catched, but a manual report of beeing out of date is not possible and automatically closed for not beeing a bug?

Regards!

Offline

#2 2026-07-20 06:30:46

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,981

Re: extra/fig2dev: Package update not detected, but also cannot report.

File a bug about the bogus nvchecker - fig2dev had used that pattern constantly, so it lacks "[a-z]{0,1}"
That is a bug and is relevant to the package (only)

Offline

Board footer

Powered by FluxBB