On Fri, Aug 05, 2016 at 01:45:18AM +0800, Chi Hsuan Yen via aur-general wrote:
Maybe the only way is waiting. I have once submitted patches of PKGBUILDs to bugs.archlinux.org, but I don't think a trivial version bump will be accepted as a valid bug, as the bug tracker says: "Do NOT report bugs for outdated packages!"
On Thu, Aug 4, 2016 at 12:41 AM, Alive 4ever <alive4ever@live.com> wrote:
Since links package has been flagged out of date for almost one month, I can't help myself to contribute a patch and stop bugging maintainer to package an updated version.
I hope this is the right place to submit the patch.
------ Upgrade links to version 2.13
Signed-off-by: Alif <alive4ever@live.com> --- trunk/PKGBUILD | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/trunk/PKGBUILD b/trunk/PKGBUILD index 85ce55c..3f2a3bf 100644 --- a/trunk/PKGBUILD +++ b/trunk/PKGBUILD @@ -2,8 +2,8 @@ # Maintainer: Eric Bélanger <eric@archlinux.org>
pkgname=links -pkgver=2.12 -pkgrel=2 +pkgver=2.13 +pkgrel=1 pkgdesc="A text WWW browser, similar to Lynx" arch=('i686' 'x86_64') url="http://links.twibright.com/" @@ -15,7 +15,7 @@ optdepends=('libx11: for using xlinks' 'libpng: for using xlinks' 'librsvg: for using xlinks') source=(http://links.twibright.com/download/${pkgname}-${pkgver}.tar.bz2 links.desktop) -sha1sums=('952dfecded9496ff1a73184ce538d08dbbb5152b' +sha1sums=('ee5ef004723664d3928e29a603cb150db013603f' 'f600e27c2a71184444f7dd07a10230aa44463a02')
prepare() { -- 2.9.2
It's right. Development isn't just fixing bugs. Development also involves making improvements. The Arch Linux Flyspray bugtracker is just about one side of Arch Linux development: fixing bugs. Making improvement should be discussed in a development mailing list and I think this is the only place suitable for discussing Arch Linux development, mostly regarding improvements. * For the newly elected TU, can you help with packaging new 'links' * package, so that it's available from the repository, at least make a * staging to test repository.