[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#353680: marked as done (libjack0.100.0-0: 04_configure_in_jack_version.patch makes add-on installation complicated)

Your message dated Wed, 25 Apr 2007 22:41:01 +0000
with message-id <E1HgqAX-0008E5-5y@ries.debian.org>
and subject line Bug#353680: fixed in jack-audio-connection-kit 0.103.0-1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: libjack0.100.0-0
Version: 0.100.0-4
Severity: normal

Could you please explain the rationale behind above patch?
By default, jack uses ${libdir}/jack as directory for searching
for plugins (and in-process client modules).  The patch mentioned above
changes this relatively simple dirname to a dir with the jack client
lib version number in it.  However, there is no obvious way
to figure out whats the correct dir to use for addon packages.

So, how would a in-process client module know where
it has to go on a Debian system?  On systems running jackd from
source, they simply go into /usr/lib/jack, which is relatively
easy to figure out in configure scripts.

I suggest we either drop the above patch, and use
the same ADDON_DIR as other jackd installations, or
we offer some way for addon packages to query this
directory name.

-- 
CYa,
  Mario

Attachment: pgpGVp4NvFUHb.pgp
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Source: jack-audio-connection-kit
Source-Version: 0.103.0-1

We believe that the bug you reported is fixed in the latest version of
jack-audio-connection-kit, which is due to be installed in the Debian FTP archive:

jack-audio-connection-kit_0.103.0-1.diff.gz
  to pool/main/j/jack-audio-connection-kit/jack-audio-connection-kit_0.103.0-1.diff.gz
jack-audio-connection-kit_0.103.0-1.dsc
  to pool/main/j/jack-audio-connection-kit/jack-audio-connection-kit_0.103.0-1.dsc
jack-audio-connection-kit_0.103.0.orig.tar.gz
  to pool/main/j/jack-audio-connection-kit/jack-audio-connection-kit_0.103.0.orig.tar.gz
jackd_0.103.0-1_amd64.deb
  to pool/main/j/jack-audio-connection-kit/jackd_0.103.0-1_amd64.deb
libjack-dev_0.103.0-1_amd64.deb
  to pool/main/j/jack-audio-connection-kit/libjack-dev_0.103.0-1_amd64.deb
libjack0.100.0-0_0.103.0-1_all.deb
  to pool/main/j/jack-audio-connection-kit/libjack0.100.0-0_0.103.0-1_all.deb
libjack0.100.0-dev_0.103.0-1_all.deb
  to pool/main/j/jack-audio-connection-kit/libjack0.100.0-dev_0.103.0-1_all.deb
libjack0_0.103.0-1_amd64.deb
  to pool/main/j/jack-audio-connection-kit/libjack0_0.103.0-1_amd64.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 353680@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Free Ekanayaka <freee@debian.org> (supplier of updated jack-audio-connection-kit package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Wed, 11 Apr 2007 01:43:06 +0200
Source: jack-audio-connection-kit
Binary: libjack0 libjack0.100.0-dev libjack-dev libjack0.100.0-0 jackd
Architecture: source amd64 all
Version: 0.103.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Team <debian-multimedia@lists.debian.org>
Changed-By: Free Ekanayaka <freee@debian.org>
Description: 
 jackd      - JACK Audio Connection Kit (server and example clients)
 libjack-dev - JACK Audio Connection Kit (development files)
 libjack0   - JACK Audio Connection Kit (libraries)
 libjack0.100.0-0 - JACK Audio Connection Kit (libraries)
 libjack0.100.0-dev - JACK Audio Connection Kit (libraries)
Closes: 353680
Changes: 
 jack-audio-connection-kit (0.103.0-1) unstable; urgency=low
 .
   * New upstream release
   * Drop patches 04_configure_in_jack_version and 02_release-in-libjack-name
     as suggested by the upstream developers, they will take are of
     possible ABI changes and add the relevant runtime checks
   * Drop patch 11_configure.ac, fixed the lib64 path in debian/rules
   * Drop build-dependency on automake
   * Rename the library and the headers binary packages to reflect
     the fact that they are not anymore version-specific, add dummy
     binary package libjack0.100.0 to provide an upgrade path
   * Bug fix: "libjack0.100.0-0: 04_configure_in_jack_version.patch makes
     add-on installation complicated", thanks to Mario Lang (Closes: #353680).
   * Remove rpath from the binary programs using chrpath
   * Enabled SSE (see http://ardour.org/node/820)
Files: 
 03b77a23c3212060f166251fa21c5af0 1415 sound optional jack-audio-connection-kit_0.103.0-1.dsc
 4f51538a2d5e8d74061a7fe6081856af 759145 sound optional jack-audio-connection-kit_0.103.0.orig.tar.gz
 4d7d8cfdf0d9cbd72d6766161ca2c772 27907 sound optional jack-audio-connection-kit_0.103.0-1.diff.gz
 6672211fcb9005c745e255810867fba4 11956 libs optional libjack0.100.0-0_0.103.0-1_all.deb
 9c901587e73bff396c6a1c368558e5ad 11966 libs optional libjack0.100.0-dev_0.103.0-1_all.deb
 48d9b80f704481e986414558bd166867 106406 sound optional jackd_0.103.0-1_amd64.deb
 b4bf381572f4cbc87043f8ee121361e5 91398 libs optional libjack0_0.103.0-1_amd64.deb
 088f66667fc81e7d68a4c8f127eea77a 127794 libdevel optional libjack-dev_0.103.0-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGHeH8canJGlcVnlkRAmVZAJ9ERF6aGQ/UB8UVVVKzubxt9s9D7wCgyNhG
zQuSYi0eRdaxGtCGW3scofU=
=zcOM
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: