On 11/2/24 5:49 PM, Robin Candau wrote:
I haven't take a detailed look but, after a quick glance, the PKGBUILD looks
generally good. Here are a few details I was able to spot:
- "Previous Maintainer" should be listed as "Contributor" (e.g. `#
Contributor: name `) [1]
- No reason to list the
On 11/2/24 11:00 PM, David C. Rankin wrote:
On 11/1/24 1:23 PM, Robin Candau wrote:
You can't update a package without being a maintainer / co-maintainer
for it. However, since the package is currently orphaned, you can
become the maintainer for it and push the update.
Robin,
I adopted
namcap both the resulting package and the PKGBUILD.
> unclear whether I should list debugedit as a build dependency
https://wiki.archlinux.org/title/Arch_User_Repository#Prerequisites
Martin
On Sat, Nov 2, 2024 at 11:01 PM David C. Rankin wrote:
>
> On 11/1/24 1:23 PM, Robin Candau wrote:
> >
On 02-11-2024 11:15, lists.archlinux@ihavea.quest wrote:
Has there been any update/activity in this regard?
This was an excellent idea!
Almost every package has a .nvchecker.toml file now and pkgctl version
check now works for those packages
On 11/1/24 1:23 PM, Robin Candau wrote:
You can't update a package without being a maintainer / co-maintainer for it.
However, since the package is currently orphaned, you can become the
maintainer for it and push the update.
Robin,
I adopted the package as maintainer and pushed updates t
On 11/2/24 5:15 AM, lists.archlinux@ihavea.quest wrote:
Has there been any update/activity in this regard?
This was an excellent idea!
Yes it is. Only issues I see is for packages that build for container apps
that need a specific version, not the latest upstream. There is also the issue
of
Has there been any update/activity in this regard?
This was an excellent idea!
--
txtsd
https://ihavea.quest
On 2/1/22 1:55 AM, Jelle van der Waa wrote:
We’ve wanted automatic flagging packages out of date for a while and
currently every packager has to come up with it’s own solution. Let’s
so
