[amd64] Building of architecture-independent parts (docs) of Ghostscript not stable against small toolchain changes

Bug #185602 reported by Till Kamppeter on 2008-01-24
4
Affects Status Importance Assigned to Milestone
ghostscript (Debian)
Fix Released
Unknown
ghostscript (Ubuntu)
High
Martin Pitt

Bug Description

Binary package hint: ghostscript

I have built a new Ghostscript package to apply a small patch to the code of the IJS interface. This does not add or remove files in the binary package and also no documentation files are modified and debian/rules was also not modified.

When installing the new packages a conflict gets reported:

dpkg: warning - old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
dpkg: ... it looks like that went OK.
Unpacking replacement ghostscript ...
dpkg: error processing /var/cache/apt/archives/ghostscript_8.61.dfsg.1-0ubuntu4_amd64.deb (--unpack):
 trying to overwrite `/usr/share/doc/ghostscript/README.gz', which is also in package ghostscript-doc
Errors were encountered while processing:
 /var/cache/apt/archives/ghostscript_8.61.dfsg.1-0ubuntu4_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
till@till-laptop:~/ubuntu/gutenprint$ less ../ghostscript/ghostscript-8.61.dfsg.1/debian/changelog

Related branches

Changed in ghostscript:
importance: Undecided → High
milestone: none → hardy-alpha-4
assignee: nobody → pitti
Martin Pitt (pitti) on 2008-01-30
Changed in ghostscript:
status: New → In Progress
Changed in ghostscript:
status: Unknown → New
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ghostscript - 8.61.dfsg.1-0ubuntu5

---------------
ghostscript (8.61.dfsg.1-0ubuntu5) hardy; urgency=low

  * debian/rules: Do not ship README.gz in ghostscript, it collides with
    ghostscript-doc. (LP: #185602, Debian #460692)

 -- Martin Pitt <email address hidden> Wed, 30 Jan 2008 11:11:03 +0100

Changed in ghostscript:
status: In Progress → Fix Released
Changed in ghostscript:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.