Your message dated Sat, 16 Jun 2012 19:59:10 +0900
with message-id <20120616105910.GI23133@goofy.localdomain>
and subject line Did you use dpkg (1.16.4)?: Bug#676717: debiandoc-sgml:
has caused the Debian Bug report #676717,
regarding debiandoc-sgml: does not work at all with minimal document
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 ow...@bugs.debian.org
immediately.)


-- 
676717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debiandoc-sgml
Version: 1.2.27
Severity: grave
Justification: renders package unusable

$ cat test.sgml
<!doctype debiandoc system>
<debiandoc>
  <book>
    <titlepag>
      <title>Some title</title>
      <author>
        <name>Some author</name>
      </author>
  </book>
</debiandoc>
$ debiandoc2text test.sgml
nsgmls:/etc/sgml/xml-resume-library.cat:8:8:E: cannot open 
"/usr/share/sgml/xml-resume-library/dtd/resume.cat" (No such file or directory)
nsgmls:/etc/sgml/w3c-dtd-xhtml.cat:8:8:E: cannot open 
"/usr/share/xml/xhtml/schema/dtd/1.0/catalog" (No such file or directory)
nsgmls:/etc/sgml/w3c-dtd-xhtml.cat:9:8:E: cannot open 
"/usr/share/xml/xhtml/schema/dtd/1.1/catalog" (No such file or directory)
nsgmls:/etc/sgml/w3c-dtd-xhtml.cat:10:8:E: cannot open 
"/usr/share/xml/xhtml/schema/dtd/basic/catalog" (No such file or directory)
nsgmls:/etc/sgml/w3c-dtd-xhtml.cat:11:8:E: cannot open 
"/usr/share/xml/xhtml/schema/dtd/catalog" (No such file or directory)
nsgmls:/etc/sgml/w3c-dtd-xhtml.cat:12:8:E: cannot open 
"/usr/share/xml/entities/xhtml/catalog" (No such file or directory)
nsgmls:test.sgml:9:8:E: end tag for "BOOK" which is not finished
$

ouch, I cannot even rebuild tex-common anymore due to that!!!

Thanks

Norbert

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (499, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5.0-rc1+ (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages debiandoc-sgml depends on:
ii  libhtml-parser-perl  3.69-2
ii  libroman-perl        1.23-1
ii  libtext-format-perl  0.56-1
ii  perl                 5.14.2-11
ii  sgml-base            1.26+nmu3
ii  sgml-data            2.0.6
ii  sgmlspl              1.03ii-32
ii  sp                   1.3.4-1.2.1-47.1

Versions of packages debiandoc-sgml recommends:
ii  ghostscript          9.05~dfsg-6
ii  texinfo              4.13a.dfsg.1-10
ii  texlive              2012.20120529-1
ii  texlive-latex-extra  2012.20120529-1

Versions of packages debiandoc-sgml suggests:
pn  debiandoc-sgml-doc  <none>
ii  latex-cjk-all       4.8.2+git20111216-2
ii  texlive-lang-all    2012.20120529-1

-- no debconf information



--- End Message ---
--- Begin Message ---
Hi,

Thanks for d-d list posting warning me not to unplug my PC :-)
We have many rough edges just before the wheezy release.

On Sat, Jun 09, 2012 at 11:46:57AM +0900, Norbert Preining wrote:
> Package: debiandoc-sgml
> Version: 1.2.27
> Severity: grave
> Justification: renders package unusable

True but you were a bit late for this major bug party of dpkg.

I think you checked BTS after new dpkg (1.16.4) was upload but tested all these
cases before dpkg (1.16.4).

   * Always activate all path components for file triggers, this fixes file
     trigger handling for conffiles and dpkg-trigger invokations.
     Closes: #675613, #676061, #676062, #676107, #676118, #676122

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675613

> ouch, I cannot even rebuild tex-common anymore due to that!!!

Sure. This package was in a position to get a big peripheral damage.

I am pretty sure this is another casuality of #675613.  I am closing
this.  But if this problem persists after dpkg (1.16.4), please reopen
it.

Osamu


--- End Message ---

Reply via email to