[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#321888: marked as done (merge is overly picky)

Your message dated Tue, 18 Apr 2006 16:36:29 -0700
with message-id <20060418233629.GD14053@volo.donarmstrong.com>
and subject line Blocks/Blocked-by bugs need to be blocked the same way
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: bugs.debian.org
Severity: normal

Tried to merge two bugs from the same source, but they happened to be
filed on different binary packages:

> merge 320987 318066
Bug#318066: libsoqt-dev: unusable with current libcoin due to ABI change
Bug#320987: libsoqt20c102: Not installable, because it depends on libcoin40 and not on
Mismatch - only Bugs in same state can be merged:
Values for `package' don't match:
 #318066 has `libsoqt-dev';
 #320987 has `libsoqt20c102'

That strikes me as a bit picky.  Why must merged bugs be in the same
"state"?  Can we relax the rules to check source package rather than
binary package?  How about ignoring the severity?  


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

--- End Message ---
--- Begin Message ---
Blocked bugs (and those blocked-by) need to be blocked in the same
way; otherwise merging them will produce an undefined state. Merging
the set of blocks isn't exactly obvious either.

The implementation of forcemerge will enable the second bug to take on
the exact same state as the first bug listed, but that's not yet fully
tested. As that bug already exists in multiple forms (see #14043 et
al.) I'm closing this bug.

Don Armstrong

The solution to a problem changes the problem.
 -- Peer's Law

http://www.donarmstrong.com              http://rzlab.ucr.edu

--- End Message ---

Reply to: