[arch-general] Bug reports for out of date packages?
Hi, Arch's packages usually (almost always) get updated pretty fast and the system "don't create a bug report, just flag the package out of date to get dev's/TU's attention" works fine. But sometimes there exist packages both in community and in extra (I'm not sure about core but maybe even there) that don't get updated even after a significant time from the upstream's release (e. g. swt, amarok, jre or jdk from the nearest past). Shouldn't there be a time limit (two weeks? a month?) after which it would be OK to create a bug report? That way there could be a discussion about why that package hasn't/couldn't be updated and everyone would know where to look for the reasons without having to go through mailing list archives, bbs and so on. Just a thought though. Ondřej -- Cheers, Ondřej Kučera
On Tue, 07 Apr 2009 00:37:14 +0200 Ondřej Kučera <ondrej.kucera@centrum.cz> wrote:
Hi,
Arch's packages usually (almost always) get updated pretty fast and the system "don't create a bug report, just flag the package out of date to get dev's/TU's attention" works fine. But sometimes there exist packages both in community and in extra (I'm not sure about core but maybe even there) that don't get updated even after a significant time from the upstream's release (e. g. swt, amarok, jre or jdk from the nearest past). Shouldn't there be a time limit (two weeks? a month?) after which it would be OK to create a bug report? That way there could be a discussion about why that package hasn't/couldn't be updated and everyone would know where to look for the reasons without having to go through mailing list archives, bbs and so on.
Just a thought though.
Ondřej
I wondered about that as well. For example jack-audio-connection-kit, qjackctl and ardour, all in extra, have been out of date at least since I joined arch, and I believe this was around October/November. Mailing the maintainer didn't help. Philipp
2009/4/6 <hollunder@gmx.at>:
On Tue, 07 Apr 2009 00:37:14 +0200 Ondřej Kučera <ondrej.kucera@centrum.cz> wrote:
Hi,
Arch's packages usually (almost always) get updated pretty fast and the system "don't create a bug report, just flag the package out of date to get dev's/TU's attention" works fine. But sometimes there exist packages both in community and in extra (I'm not sure about core but maybe even there) that don't get updated even after a significant time from the upstream's release (e. g. swt, amarok, jre or jdk from the nearest past). Shouldn't there be a time limit (two weeks? a month?) after which it would be OK to create a bug report? That way there could be a discussion about why that package hasn't/couldn't be updated and everyone would know where to look for the reasons without having to go through mailing list archives, bbs and so on.
Just a thought though.
Ondřej
I wondered about that as well. For example jack-audio-connection-kit, qjackctl and ardour, all in extra, have been out of date at least since I joined arch, and I believe this was around October/November. Mailing the maintainer didn't help.
Philipp
Send a mail to the mailing list if the maintainer doesn't respond (preferably attach the PKGBUILD you updated)
I suppose that some maintainer are not looking as often as some people from the arch's community want to there package. Couldn't be multiple maintainer for package ?
On Tue, 7 Apr 2009 10:41:00 +0200 ludovic coues <couesl@gmail.com> wrote:
I suppose that some maintainer are not looking as often as some people from the arch's community want to there package.
Couldn't be multiple maintainer for package ?
Some of us (archaudio people) wished that was possible in AUR as well, simple because it happens that some maintainer is not available for some time. This is one reason for our upcoming binary repo, but I'd personally rather stick with AUR. So yeah, is something like this possible for any of the repos? Philipp
Excerpts from hollunder's message of Di Apr 07 13:35:20 +0200 2009:
On Tue, 7 Apr 2009 10:41:00 +0200 ludovic coues <couesl@gmail.com> wrote:
I suppose that some maintainer are not looking as often as some people from the arch's community want to there package.
Couldn't be multiple maintainer for package ?
Some of us (archaudio people) wished that was possible in AUR as well, simple because it happens that some maintainer is not available for some time. This is one reason for our upcoming binary repo, but I'd personally rather stick with AUR.
So yeah, is something like this possible for any of the repos?
You can do what the arch-haskell group has done: create a new user: archaudio, adopt all the packages that you want to be shared, and share the password :)
On Mon, Apr 6, 2009 at 7:02 PM, Daenyth Blank <daenyth+arch@gmail.com> wrote:
2009/4/6 <hollunder@gmx.at>:
On Tue, 07 Apr 2009 00:37:14 +0200 Ondřej Kučera <ondrej.kucera@centrum.cz> wrote:
Hi,
Arch's packages usually (almost always) get updated pretty fast and the system "don't create a bug report, just flag the package out of date to get dev's/TU's attention" works fine. But sometimes there exist packages both in community and in extra (I'm not sure about core but maybe even there) that don't get updated even after a significant time from the upstream's release (e. g. swt, amarok, jre or jdk from the nearest past). Shouldn't there be a time limit (two weeks? a month?) after which it would be OK to create a bug report? That way there could be a discussion about why that package hasn't/couldn't be updated and everyone would know where to look for the reasons without having to go through mailing list archives, bbs and so on.
Just a thought though.
Ondřej
I wondered about that as well. For example jack-audio-connection-kit, qjackctl and ardour, all in extra, have been out of date at least since I joined arch, and I believe this was around October/November. Mailing the maintainer didn't help.
Philipp
Send a mail to the mailing list if the maintainer doesn't respond (preferably attach the PKGBUILD you updated)
This is probably the best way - send an updated PKGBUILD that you've personally tested and you know works fine. This is generally how I've been doing gnucash anymore, as I stopped using it, but I get regular updates from people who like the package and test it If you're looking for "multiple maintainers", this is probably the best way, even if it is informal
Aaron Griffin wrote:
On Mon, Apr 6, 2009 at 7:02 PM, Daenyth Blank <daenyth+arch@gmail.com> wrote:
2009/4/6 <hollunder@gmx.at>:
On Tue, 07 Apr 2009 00:37:14 +0200 Ondřej Kučera <ondrej.kucera@centrum.cz> wrote:
Hi,
Arch's packages usually (almost always) get updated pretty fast and the system "don't create a bug report, just flag the package out of date to get dev's/TU's attention" works fine. But sometimes there exist packages both in community and in extra (I'm not sure about core but maybe even there) that don't get updated even after a significant time from the upstream's release (e. g. swt, amarok, jre or jdk from the nearest past). Shouldn't there be a time limit (two weeks? a month?) after which it would be OK to create a bug report? That way there could be a discussion about why that package hasn't/couldn't be updated and everyone would know where to look for the reasons without having to go through mailing list archives, bbs and so on.
Just a thought though.
Ondřej
I wondered about that as well. For example jack-audio-connection-kit, qjackctl and ardour, all in extra, have been out of date at least since I joined arch, and I believe this was around October/November. Mailing the maintainer didn't help.
Philipp
Send a mail to the mailing list if the maintainer doesn't respond (preferably attach the PKGBUILD you updated)
This is probably the best way - send an updated PKGBUILD that you've personally tested and you know works fine. This is generally how I've been doing gnucash anymore, as I stopped using it, but I get regular updates from people who like the package and test it
If you're looking for "multiple maintainers", this is probably the best way, even if it is informal
Maybe we should have some way of sorting packages by how long they have been flagged out of date. Two that come up on the forums a lot recently are gmpc and obex-data-server so I will push updates sometime tomorrow if no-one else does... Allan
hollunder@gmx.at wrote:
jack-audio-connection-kit, qjackctl and ardour, all in extra, have been out of date... <snip>
So, does anyone have working updated PKGBUILDs for these that I can push to [extra]? Allan
2009/4/9 Allan McRae <allan@archlinux.org>:
hollunder@gmx.at wrote:
jack-audio-connection-kit, qjackctl and ardour, all in extra, have been out of date... <snip>
So, does anyone have working updated PKGBUILDs for these that I can push to [extra]?
Allan
This one for ardour2 from AUR works fine on my machine: # Maintainer: Philipp Ãœberbacher <hollunder at gmx dot at> pkgname=ardour-lv2 pkgver=2.8 pkgrel=3 pkgdesc="Ardour is a digital audio workstation." arch=('i686' 'x86_64') url="http://ardour.org/" license=('GPL') depends=('rubberband' 'liblrdf' 'libgnomecanvas' 'liblo' 'libusb' 'aubio' 'slv2') makedepends=('boost' 'ladspa' 'scons' 'gettext' 'libtool' 'pkgconfig') options=('!libtool') conflicts=('ardour' 'ardour2') provides=('ardour' 'ardour2') source=("http://releases.ardour.org/ardour-$pkgver.tar.bz2") md5sums=('24bd768dbe08f1f2724dc97704ee0518') build() { cd ${startdir}/src/ardour-${pkgver} || return 1 scons PREFIX="/usr" \ FREESOUND=1 \ DESTDIR="${pkgdir}" || return 1 scons PREFIX="/usr" \ DESTDIR="${pkgdir}" \ install || return 1 } -- Ryan W Sims
On Thu, 9 Apr 2009 12:45:46 -0400 Ryan Sims <rwsims@gmail.com> wrote:
2009/4/9 Allan McRae <allan@archlinux.org>:
hollunder@gmx.at wrote:
jack-audio-connection-kit, qjackctl and ardour, all in extra, have been out of date... <snip>
So, does anyone have working updated PKGBUILDs for these that I can push to [extra]?
Allan
This one for ardour2 from AUR works fine on my machine:
# Maintainer: Philipp Ãœberbacher <hollunder at gmx dot at>
pkgname=ardour-lv2 pkgver=2.8 pkgrel=3 pkgdesc="Ardour is a digital audio workstation." arch=('i686' 'x86_64') url="http://ardour.org/" license=('GPL') depends=('rubberband' 'liblrdf' 'libgnomecanvas' 'liblo' 'libusb' 'aubio' 'slv2') makedepends=('boost' 'ladspa' 'scons' 'gettext' 'libtool' 'pkgconfig') options=('!libtool') conflicts=('ardour' 'ardour2') provides=('ardour' 'ardour2') source=("http://releases.ardour.org/ardour-$pkgver.tar.bz2") md5sums=('24bd768dbe08f1f2724dc97704ee0518') build() { cd ${startdir}/src/ardour-${pkgver} || return 1 scons PREFIX="/usr" \ FREESOUND=1 \ DESTDIR="${pkgdir}" || return 1 scons PREFIX="/usr" \ DESTDIR="${pkgdir}" \ install || return 1 }
Note that some of the dependencies are missing in [ extra ]. - Rubberband is for time stretching/pitch shifting and used in an increasing number of apps. - LV2 is the successor of LADSPA. Ardour builts with both by default as you can guess from the scons line. I don't know off the top of my head if it's possible to build without rubberband. Another question is the recent support of VST without Steinberg headers, which would allow distribution of VST enabled binaries (but IANAL). This would add wine as dependency AFAIK, I haven't used this myself but I'm sure there are plenty of people at #archaudio that have. Jack is even more important than ardour, the following PKGBUILD should be fine, except that I'm not sure about --enable-optimize for binary packages. The PKGBUILD in extra builds it with POSIX-SHM support which is not recommended by jacks main author. # Contributor: Philipp Überbacher <hollunder at gmx dot at> pkgname=jack-audio-connection-kit pkgver=0.116.2 pkgrel=1 pkgdesc="A low-latency audio server" arch=(i686 x86_64) license=(GPL2 LGPL2) depends=('libsamplerate' 'readline') makedepends=('doxygen') provides=('jack-audio-connection-kit') conflicts=('jack-audio-connection-kit') url="http://jackaudio.org/" options=('!libtool') source=(http://jackaudio.org/downloads/${pkgname}-${pkgver}.tar.gz) md5sums=('9c0ae9880e9b6e081f1a238fe6a28bd5') build() { cd "${startdir}/src/${pkgname}-${pkgver}" ./configure --prefix=/usr --enable-optimize || return 1 make || return 1 make DESTDIR=${startdir}/pkg install || return 1 } Qjackctl is lest important of the bunch, here's simple the updated PKGBUILD from [extra]: # Contributor: Tobias Kieslich <tobias@justdreams.de> pkgname=qjackctl pkgver=0.3.4 pkgrel=1 pkgdesc="a qt based frontend to the jack server (jack-audio-connection-kit)" arch=(i686 x86_64) license=('GPL2') depends=('jack-audio-connection-kit' 'qt') # options=('!libtool') install=${pkgname}.install url="http://qjackctl.sourceforge.net/" source=(http://downloads.sourceforge.net/${pkgname}/${pkgname}-${pkgver}.tar.gz) md5sums=('65736e83650468256ba22aa5d35fd0cb') build() { cd ${startdir}/src/${pkgname}-${pkgver} ./configure --prefix=/usr make || return 1 make prefix=${pkgdir}/usr install } I have no illusions about the need to build from source, but these are pretty basic and common tools and it's nice to have them reasonably up-to-date in the repos. If you have questions just mail or visit #archaudio Best regards, Philipp
hollunder@gmx.at wrote:
On Thu, 9 Apr 2009 12:45:46 -0400 Ryan Sims <rwsims@gmail.com> wrote:
2009/4/9 Allan McRae <allan@archlinux.org>:
hollunder@gmx.at wrote:
jack-audio-connection-kit, qjackctl and ardour, all in extra, have been out of date... <snip>
So, does anyone have working updated PKGBUILDs for these that I can push to [extra]?
Allan
This one for ardour2 from AUR works fine on my machine:
# Maintainer: Philipp Ãœberbacher <hollunder at gmx dot at>
pkgname=ardour-lv2 pkgver=2.8 pkgrel=3 pkgdesc="Ardour is a digital audio workstation." arch=('i686' 'x86_64') url="http://ardour.org/" license=('GPL') depends=('rubberband' 'liblrdf' 'libgnomecanvas' 'liblo' 'libusb' 'aubio' 'slv2') makedepends=('boost' 'ladspa' 'scons' 'gettext' 'libtool' 'pkgconfig') options=('!libtool') conflicts=('ardour' 'ardour2') provides=('ardour' 'ardour2') source=("http://releases.ardour.org/ardour-$pkgver.tar.bz2") md5sums=('24bd768dbe08f1f2724dc97704ee0518') build() { cd ${startdir}/src/ardour-${pkgver} || return 1 scons PREFIX="/usr" \ FREESOUND=1 \ DESTDIR="${pkgdir}" || return 1 scons PREFIX="/usr" \ DESTDIR="${pkgdir}" \ install || return 1 }
Note that some of the dependencies are missing in [ extra ]. - Rubberband is for time stretching/pitch shifting and used in an increasing number of apps. - LV2 is the successor of LADSPA.
Ardour builts with both by default as you can guess from the scons line. I don't know off the top of my head if it's possible to build without rubberband.
Another question is the recent support of VST without Steinberg headers, which would allow distribution of VST enabled binaries (but IANAL). This would add wine as dependency AFAIK, I haven't used this myself but I'm sure there are plenty of people at #archaudio that have.
Jack is even more important than ardour, the following PKGBUILD should be fine, except that I'm not sure about --enable-optimize for binary packages. The PKGBUILD in extra builds it with POSIX-SHM support which is not recommended by jacks main author.
# Contributor: Philipp Überbacher <hollunder at gmx dot at>
pkgname=jack-audio-connection-kit pkgver=0.116.2 pkgrel=1 pkgdesc="A low-latency audio server" arch=(i686 x86_64) license=(GPL2 LGPL2) depends=('libsamplerate' 'readline') makedepends=('doxygen') provides=('jack-audio-connection-kit') conflicts=('jack-audio-connection-kit') url="http://jackaudio.org/" options=('!libtool') source=(http://jackaudio.org/downloads/${pkgname}-${pkgver}.tar.gz) md5sums=('9c0ae9880e9b6e081f1a238fe6a28bd5') build() { cd "${startdir}/src/${pkgname}-${pkgver}" ./configure --prefix=/usr --enable-optimize || return 1 make || return 1 make DESTDIR=${startdir}/pkg install || return 1 }
Qjackctl is lest important of the bunch, here's simple the updated PKGBUILD from [extra]:
# Contributor: Tobias Kieslich <tobias@justdreams.de>
pkgname=qjackctl pkgver=0.3.4 pkgrel=1 pkgdesc="a qt based frontend to the jack server (jack-audio-connection-kit)" arch=(i686 x86_64) license=('GPL2') depends=('jack-audio-connection-kit' 'qt') # options=('!libtool') install=${pkgname}.install url="http://qjackctl.sourceforge.net/" source=(http://downloads.sourceforge.net/${pkgname}/${pkgname}-${pkgver}.tar.gz) md5sums=('65736e83650468256ba22aa5d35fd0cb')
build() { cd ${startdir}/src/${pkgname}-${pkgver} ./configure --prefix=/usr make || return 1 make prefix=${pkgdir}/usr install }
I have no illusions about the need to build from source, but these are pretty basic and common tools and it's nice to have them reasonably up-to-date in the repos. If you have questions just mail or visit #archaudio
I have put updated version of jack-audio-connection-kit and qjackctl in [testing]. Please test them out. Ardour will hopefully follow soon. Allan
participants (8)
-
Aaron Griffin
-
Allan McRae
-
Daenyth Blank
-
hollunder＠gmx.at
-
Jan Spakula
-
ludovic coues
-
Ondřej Kučera
-
Ryan Sims