Your message dated Fri, 01 Jul 2011 23:17:28 +0000
with message-id <[email protected]>
and subject line Bug#621544: fixed in ldm 2:2.2.2-2
has caused the Debian Bug report #621544,
regarding ldm: 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.)


-- 
621544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621544
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ldm
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.

ldm 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
ldm 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: ldm
Source-Version: 2:2.2.2-2

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

ldm-server_2.2.2-2_all.deb
  to main/l/ldm/ldm-server_2.2.2-2_all.deb
ldm_2.2.2-2.debian.tar.gz
  to main/l/ldm/ldm_2.2.2-2.debian.tar.gz
ldm_2.2.2-2.dsc
  to main/l/ldm/ldm_2.2.2-2.dsc
ldm_2.2.2-2_i386.deb
  to main/l/ldm/ldm_2.2.2-2_i386.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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vagrant Cascadian <[email protected]> (supplier of updated ldm 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, 01 Jul 2011 15:41:53 -0700
Source: ldm
Binary: ldm ldm-server
Architecture: source all i386
Version: 2:2.2.2-2
Distribution: unstable
Urgency: low
Maintainer: LTSP Debian/Ubuntu Maintainers 
<[email protected]>
Changed-By: Vagrant Cascadian <[email protected]>
Description: 
 ldm        - LTSP display manager
 ldm-server - server components for LTSP display manager
Closes: 621544
Changes: 
 ldm (2:2.2.2-2) unstable; urgency=low
 .
   [ Luk Claes ]
   * Don't ship .la files (Closes: #621544).
Checksums-Sha1: 
 bc8112031c42c14169d1086e1a75ad81b63a83c3 2127 ldm_2.2.2-2.dsc
 27bdf12ab8228be0e75504d729bd470112d3f925 12628 ldm_2.2.2-2.debian.tar.gz
 62148215cb51ee20509d1679c26b0d52052205c3 70138 ldm-server_2.2.2-2_all.deb
 8f8cfd1633b33ab066668bf04ee7f72c55b3adc5 178256 ldm_2.2.2-2_i386.deb
Checksums-Sha256: 
 5bd487aed89bd41f922ed54e535da3621abf1db7e215c01338bf00438702febc 2127 
ldm_2.2.2-2.dsc
 54240cb219f526de62311e760386f7bf652dee2f0ad319142790ca7062d64c15 12628 
ldm_2.2.2-2.debian.tar.gz
 e01bf2993de1d0b815725dc73f24cebbe841196e50b5abe70765709a391b4724 70138 
ldm-server_2.2.2-2_all.deb
 a710d4581f20300ec9fd30179e67ac4ab5689f8c6fc757f30079472b7836b17f 178256 
ldm_2.2.2-2_i386.deb
Files: 
 7527b1f55a1f2d0ec0f4c7b2af8468d2 2127 misc extra ldm_2.2.2-2.dsc
 348e663d08f0b101181c2d266f37a77e 12628 misc extra ldm_2.2.2-2.debian.tar.gz
 5414527dab09bf5ba6d005e5b0a8c65d 70138 misc extra ldm-server_2.2.2-2_all.deb
 17e6738f708cc271033b0efcceac001a 178256 misc extra ldm_2.2.2-2_i386.deb

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

iQIcBAEBAgAGBQJODlFKAAoJELeLgtSBS5G2DE8P/i+A1ITqsIKlSNBVZBm/UArI
c1ZQrKRFHeVZ4GiTLaFMMcyA20HhelYhl7eRmQql5rlgmtOF3RDDLMkVSOqCDtgx
TMdCPdz0bPg9KudLEOctOxuzprUdhxAh5nwvfMefjp+MI6vnGMQLY4zo4pWFGIXc
tWBqkQO2GexEBfdSaashwEPahpgr2j75Gu/wzoZhP/0diC1YwQJKBI9vfkDtDm+F
k6BpCszwCei8nAwUEU54zFqWJ/VcriC8jV8FSut0+qAyMjR683gvjBCkYzuWX3po
kfqAZlU6u4PsxDz5u7QsRgXRQlnxBbYsCQQpCdULeHIsws6IDoC080/VKosN+503
sBL1rD0x19GUOIrt5pF2Yhoa+4mTP4pxLIHrR/7efNz8UHf8t6CLQyqmJ7jS/Ggt
Ku99/jwhJ7KiYQPC++/tmrGbARnr3Euor2yvcTJgdmG0eKE7U/W0GfcLfRNfuQ0e
Z3+AZMdfJTtqT/tIeBCDjonTBNU2RkwgFZSmJpuFvCqz/xdXgiGV5WmYnwUli2yN
JPkslbRAM1CvdRZDYEUAKNCSBDulnLWPl86La9vB5Dg7nhzPbW3n+Gc6KE5MmbOQ
4mVgFy27qEp3nqsFEBQSnZDnL92yPletzw7DN0Bqz5rE3sL7GMN3j7+/LrZezBXo
xJ5JXhzmZ8gNIYvxV+mX
=jaC1
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to