Your message dated Mon, 06 Nov 2006 03:32:15 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#358256: fixed in gprolog 1.2.18-17
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: dpkg
Version: 1.13.10
Severity: normal

I presently have:

  $ for n in serialver prolog javadoc javap; do ls -l /usr/bin/$n 
/etc/alternatives/$n; done;
  lrwxr-xr-x  1 root root 21 Oct  5  2004 /etc/alternatives/serialver -> 
/usr/bin/serialver-cp
  lrwxr-xr-x  1 root root 27 Aug 10  2004 /usr/bin/serialver -> 
/etc/alternatives/serialver
  lrwxr-xr-x  1 root root 16 Sep 28  2004 /etc/alternatives/prolog -> 
/usr/bin/gprolog
  lrwxrwxrwx  1 root root 24 Jun  6  2003 /usr/bin/prolog -> 
/etc/alternatives/prolog
  lrwxr-xr-x  1 root root 14 Aug 10  2004 /etc/alternatives/javadoc -> 
/usr/bin/gjdoc
  lrwxr-xr-x  1 root root 25 Aug 10  2004 /usr/bin/javadoc -> 
/etc/alternatives/javadoc
  lrwxr-xr-x  1 root root 17 Oct  5  2004 /etc/alternatives/javap -> 
/usr/bin/javap-cp
  lrwxr-xr-x  1 root root 23 Aug 10  2004 /usr/bin/javap -> 
/etc/alternatives/javap

all of which are broken symlinks (well, the /usr/bin/links point to
existing links in /etc/alternatives, which are links to nonexisting
_other_ things in /usr/bin/).

It seems reasonable to me that there are broken links in
/etc/alternatives (there are many more); I am guessing that that is
considered considered a type of "conffile", and isn't modified by dpkg
(maybe it is removed on removal [purge?] if it points to where it
would, by default?).

But, it seems that broken links should not exist in /usr/bin/.  I know
I haven't played with any of those links ..

Is dpkg at fault?  Or mb classpath?


--- End Message ---
--- Begin Message ---
Source: gprolog
Source-Version: 1.2.18-17

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

gprolog-doc_1.2.18-17_all.deb
  to pool/main/g/gprolog/gprolog-doc_1.2.18-17_all.deb
gprolog_1.2.18-17.diff.gz
  to pool/main/g/gprolog/gprolog_1.2.18-17.diff.gz
gprolog_1.2.18-17.dsc
  to pool/main/g/gprolog/gprolog_1.2.18-17.dsc
gprolog_1.2.18-17_i386.deb
  to pool/main/g/gprolog/gprolog_1.2.18-17_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.
Salvador Abreu <[EMAIL PROTECTED]> (supplier of updated gprolog 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.7
Date: Mon,  6 Nov 2006 10:40:23 +0000
Source: gprolog
Binary: gprolog gprolog-doc
Architecture: source i386 all
Version: 1.2.18-17
Distribution: unstable
Urgency: low
Maintainer: Salvador Abreu <[EMAIL PROTECTED]>
Changed-By: Salvador Abreu <[EMAIL PROTECTED]>
Description: 
 gprolog    - GNU Prolog compiler
 gprolog-doc - documentation for the GNU Prolog compiler
Closes: 356406 358256 397135
Changes: 
 gprolog (1.2.18-17) unstable; urgency=low
 .
   * Fix non-ascii character in doc/use.tex; this only seems to be a
     problem with more recent versions of hevea.  (closes: #397135)
   * Fix unaligned access on amd64.  This is done in a way which I'd rather
     not have to confess: I had GCC produce assembly code, which is then
     patched via a sed script before being fed to as.  Thanks to
     [EMAIL PROTECTED] for pointing out the location of the problem.
     (closes: #356406)
   * Fixed a few things in order to be able to use more recent versions of
     gcc, most notably casts in lvalues.  As of now, gcc 4.1 can be used to
     compile gprolog!
   * Doesn't leave anything in /etc/alternatives nor /usr/bin after being
     purged.  (closes: #358256)
Files: 
 d2578ad6ef2fa87666dcdd689839782b 704 devel optional gprolog_1.2.18-17.dsc
 4b047d7b1a98e8e451054276a958f07a 116575 devel optional 
gprolog_1.2.18-17.diff.gz
 f2dbcfdc45f4cd643dbb0646b6788a57 1049544 doc optional 
gprolog-doc_1.2.18-17_all.deb
 53a48a9762c54c45ae44b3158718df18 1120032 devel optional 
gprolog_1.2.18-17_i386.deb

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

iD8DBQFFTxHZzoTo55Wk8dYRAsVnAKDX24gpe/DD+eHqDgVp8LfvNkwPXwCfa5VP
gAk3Bx0Efam6MKLsFpnAU/I=
=7cD2
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to