Your message dated Wed, 12 Oct 2016 22:00:26 -0400
with message-id 
and subject line 
has caused the Debian Bug report #812949,
regarding libmongoc-doc: contains manpages with generic names: index(3), 
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

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: libbson-doc
Version: 1.3.1-1
Severity: serious
Usertags: piuparts
Control: clone -1 -2
Control: reassign -2 libmongoc-doc 1.3.1-1
Control: retitle -2 libmongoc-doc: contains manpages with generic names: 
index(3), installing(3)


during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files, since it ships
manpages with very generic names (that don't even belong in section 3):


Adding Conflicts/Breaks/Replaces is *not* the correct solution
for this specific problem.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libmongoc-doc.
  Preparing to unpack .../libmongoc-doc_1.3.1-1_all.deb ...
  Unpacking libmongoc-doc (1.3.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libmongoc-doc_1.3.1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man3/installing.3.gz', which is also in 
package libbson-doc 1.3.1-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:



Attachment: libbson-doc=1.3.1-1_libmongoc-doc=1.3.1-1.log.gz
Description: application/gzip

--- End Message ---
--- Begin Message ---
Version: 1.4.1-1

Fixed in the upstream repository and uploaded as a new package version to
Debian. See the forwarded-to bug in MongoDB's Jira for details.

--- End Message ---

Reply via email to