Your message dated Fri, 16 Sep 2011 15:17:19 +0000
with message-id <[email protected]>
and subject line Bug#633243: fixed in oopango 1.0-2
has caused the Debian Bug report #633243,
regarding oopango: Getting rid of unneeded *.la / emptying dependency_libs
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
633243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633243
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: oopango
Version: 1.0-1
Severity: normal
User: [email protected]
Usertags: la-file-removal

 To finish an old release goal from Squeeze, to comply with Policy
10.2 and to ease the introduction of MultiArch, I'm filing bugs
against packages which contain .la files which can be either removed
or stripped of the dependency_libs variable.

http://wiki.debian.org/ReleaseGoals/LAFileRemoval

http://lists.debian.org/debian-devel/2011/04/msg00055.html

http://lists.debian.org/debian-devel/2011/04/msg00199.html

Data has been obtained from the output of an automated script:

http://release.debian.org/~aba/la/current.txt

The output is best read in conjunction with the criteria from this
post to debian-devel:

http://lists.debian.org/debian-devel/2009/08/msg00808.html

To generate the list of packages, I've used:

grep -v depended-on current.txt |cut -d: -f1

The data is regularly updated but please accept my apologies if you
have made an upload which changes the situation since the data was
parsed.

oopango (1.0-1) appears in this list as a source package because one
or more of the binary packages (usually -dev packages) contain .la
files.

In most cases, the .la file(s) can simply be removed as the process
behind this MBF has already identified that there are no further
dependencies using the .la file. In the unusual case that your
package uses libltdl directly, it is still necessary to empty the
dependency_libs part of all .la files remaining in the package. Once
oopango is fixed, the process will repeat and other packages which
you maintain may need to be fixed in turn. It is important that
packages are fixed in sequence to avoid FTBFS bugs.

If you believe that your package needs both the .la file and the
dependency_libs settings, please raise this on debian-devel for
clarification.
-- 

Neil Williams
=============
[email protected]
http://www.linux.codehelp.co.uk/




--- End Message ---
--- Begin Message ---
Source: oopango
Source-Version: 1.0-2

We believe that the bug you reported is fixed in the latest version of
oopango, which is due to be installed in the Debian FTP archive:

liblua5.1-oopango-dev_1.0-2_amd64.deb
  to main/o/oopango/liblua5.1-oopango-dev_1.0-2_amd64.deb
liblua5.1-oopango0_1.0-2_amd64.deb
  to main/o/oopango/liblua5.1-oopango0_1.0-2_amd64.deb
oopango_1.0-2.debian.tar.gz
  to main/o/oopango/oopango_1.0-2.debian.tar.gz
oopango_1.0-2.dsc
  to main/o/oopango/oopango_1.0-2.dsc



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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Danjou <[email protected]> (supplier of updated oopango 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 [email protected])


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

Format: 1.8
Date: Fri, 16 Sep 2011 16:52:16 +0200
Source: oopango
Binary: liblua5.1-oopango0 liblua5.1-oopango-dev
Architecture: source amd64
Version: 1.0-2
Distribution: unstable
Urgency: low
Maintainer: Julien Danjou <[email protected]>
Changed-By: Julien Danjou <[email protected]>
Description: 
 liblua5.1-oopango-dev - Pango API for Lua - development files
 liblua5.1-oopango0 - provides Lua with full access to the Pango text rendering 
API
Closes: 633243 636084
Changes: 
 oopango (1.0-2) unstable; urgency=low
 .
   [ Matthias Klose ]
   * Apply patch from Enrico Tassi to fix FTBFS. Closes: #636084
   * Fix oopango.so symlink.
   * Multi-Arch support
   * lua5.1/oopango.so symlink to liboocairo.so.0.0.0 and not liboopango.so
     so that the -dev package is not required to run 'require "oopango"'
     from the lua interpreter
   * kill .la file (Closes: #633243)
 .
   [ Julien Danjou ]
   * Bump standards version
   * Fix boilerplate in copyright file
Checksums-Sha1: 
 533cc320f462042952a6f1387f9b2895101bfbc1 1919 oopango_1.0-2.dsc
 57e558961a7d76e65fffbf8ed5001a4bb5776363 3567 oopango_1.0-2.debian.tar.gz
 fcd4b663ef6ec60923dce4557884453367022d7d 11776 
liblua5.1-oopango0_1.0-2_amd64.deb
 913c9c51175afd81bb622166d64e12bde29d286c 3226 
liblua5.1-oopango-dev_1.0-2_amd64.deb
Checksums-Sha256: 
 c683056465a9e221420ec9c8aa3ac4247285344b4d7ac3abfb32b31ca18c7b74 1919 
oopango_1.0-2.dsc
 4b26be00e0a1163116170862761a52ac45bc9f7513cbd0fbcf0bcf87d4c3020b 3567 
oopango_1.0-2.debian.tar.gz
 d863c7fa086e9f2fa383b8064f776de90e58972adc0be093d7ccc1866d9c2254 11776 
liblua5.1-oopango0_1.0-2_amd64.deb
 d14b7a0a7a3575b2741d158285ab2afa9fdb32ef45e2c58b0d96dab44906bb6e 3226 
liblua5.1-oopango-dev_1.0-2_amd64.deb
Files: 
 55941aaa919928de4b0828e6f7c6f5c7 1919 interpreters optional oopango_1.0-2.dsc
 12f3d792488cb036b2c70c4e16ca7614 3567 interpreters optional 
oopango_1.0-2.debian.tar.gz
 327ca87b0a007c8d2da8e439ef6bb14c 11776 interpreters optional 
liblua5.1-oopango0_1.0-2_amd64.deb
 a246728496fdea519d53213d125b4c63 3226 libdevel optional 
liblua5.1-oopango-dev_1.0-2_amd64.deb

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

iQIcBAEBAgAGBQJOc2MxAAoJEGEbqVCLeKXCP0cP/0qigPVrz02V2vmwwykhn6WK
/FRDIKnecO5nfIUebrz3QxNI8hw6wmAxTtKQdRZZfW5sAlfxhF0i1qu80+i48Pce
GjU6ZG2LSkiYzdf4whrhbfpYjBj1T1vKTCBERR8Yq6fHBRUDOqNo/R+Jc1njnjhF
lrB5JsrXjNdqgtQRdlf8leuEgUzksIP0WpumtIXI3Tp3CQl2SObS/5UbspIMo5ha
k/9dn12dirjAbbUonMXnG2vRGO4dn/dgXwn5n6zv7556kN3WTq4sjvI0I0JHNHL6
JKEVqdqVnuVoZptTqy3qE0BBQZuCClSTGtbFqrwqs9udXajke/Nnz2KX6LMwRoXo
fnMIE0jadfw0qiXjZfTQAT7oy8dgirz0EML8Ox2TeFMd18lnV36j3km+qXJUj2pg
qoircgaHyrjKhgOVh+7JXKQLsdtm36mE9/w5dUJE2xUqNFemwDuLatR0rGfu+min
oZc/J6Ti6/5bVVxRK63sUykFdHDx5N9DWdJkMm9FLk6LrxuZ3wA+G22W0eDnHhWF
H5V4QBWy9TcV3fQ4i6n48D2o7kmUeTZrk7BmqLXkfCO/yurVKEqVoyuZp4YE6w3m
PDhp9FboeHhDW0OYPsCHAdATA4q9Fr9CfwD/ukin7n4724YOBYJY7wL1WvI/8UXw
lfpWxpDFI0EnUn5P/FIy
=j6Y2
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to