=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/
There are currently:
* 0 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 0 fully signed off packages
* 18 packages missing signoffs
* 1 package older than 14 days
(Note: the word 'package' as used here refers to packages as grouped by
pkgbase, architecture, and repository; e.g., one PKGBUILD produces one
package per architecture, even if it is a split package.)
== Incomplete signoffs for [community] (17 total) ==
* arm-none-eabi-newlib-2.2.0-3 (any)
0/2 signoffs
* gcc-docs-5.1.0-1 (any)
1/2 signoffs
* puppet-4.0.0-2 (any)
1/2 signoffs
* arm-none-eabi-binutils-2.25-3 (i686)
0/1 signoffs
* arm-none-eabi-gcc-5.1.0-2 (i686)
0/1 signoffs
* mingw-w64-gcc-5.1.0-3 (i686)
0/1 signoffs
* nodejs-0.12.2-4 (i686)
0/1 signoffs
* openscad-2015.03.01-3 (i686)
0/1 signoffs
* qscintilla-qt5-2.9-1 (i686)
0/1 signoffs
* sqliteman-1.2.2-8 (i686)
0/1 signoffs
* arm-none-eabi-binutils-2.25-3 (x86_64)
0/2 signoffs
* arm-none-eabi-gcc-5.1.0-2 (x86_64)
1/2 signoffs
* mingw-w64-gcc-5.1.0-3 (x86_64)
0/2 signoffs
* nodejs-0.12.2-4 (x86_64)
0/2 signoffs
* openscad-2015.03.01-3 (x86_64)
0/2 signoffs
* qscintilla-qt5-2.9-1 (x86_64)
0/2 signoffs
* sqliteman-1.2.2-8 (x86_64)
0/2 signoffs
== Incomplete signoffs for [unknown] (1 total) ==
* npm-2.9.0-1 (any)
0/2 signoffs
== All packages in [community-testing] for more than 14 days (1 total) ==
* puppet-4.0.0-2 (any), since 2015-04-20
== Top five in signoffs in last 24 hours ==
Hello fellow Arch users, and good whatever time of the day is in your time
zone.
I'm currently maintaining the iojs package which just hit 2.0.0 and for
some reason it's causing a bit of trouble with python versions.
The package was able to build as a copy and adapt from the nodejs package
from the repos, until 1.8.1, but now it doesn't build because what I think
is some kind of python version mismatch [ 0 ], but I don't know python.
I've been looking at the changelog from the iojs project but nothing of
what I've seen for now seems to suggest a change that could cause this and
I'm totally lost.
Problem is, my scripting and PKGBUILD skills are a little rusty and I don't
know exactly how to address this, as I've been for a couple of hours with
no success.
You'll find the PKGBUILD at [ 1 ]
Any hints?
Thank you
[ 0 ] : http://sprunge.us/eMeO
[ 1 ] : http://sprunge.us/CMJL
Hi,
I am maintaining a lot of octave-forge packages:
https://aur.archlinux.org/packages/?O=0&K=octave-
I have a hard time keeping up with the upstream package updates. I have
implemented a script which will update the PKGBUILD by determining the
latest verison, downloading the package, and reading meta-data such as
dependencies and licensing information from the octave package
description:
https://github.com/drizzd/octave-forge-archlinux/blob/master/newpkg
Still, it is some manual effort to figure out which packages are
outdated, run the script for each, build and test, make a source package
and upload.
Is it possible to integrate the script in the PKGBUILD itself? Such that
it will automatically download the latest package version? That comes
with the risk that an upstream release breaks the build (it happened a
couple of times over the last years). But I think it's better than not
being able to update the PKGBUILDs in time.
Many of the octave-* packages not owned by me are not updated at all,
which is why I hesitate to simply orphan them. I would be happy to use a
dedicated account for octave-* packages which I could share with other
maintainers. Is it ok to create such a shared account?
Cheers,
Clemens