Your message dated Wed, 20 Aug 2014 18:05:06 -0400
with message-id <878umix1f1....@naesten.mooo.com>
and subject line Re: Bug#751929: gdb-doc uninstallable on Jessie alongside gdb 
and or gdbserver
has caused the Debian Bug report #751929,
regarding gdb-doc uninstallable on Jessie alongside gdb and or gdbserver
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.)


-- 
751929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdb-doc
Version: 7.6.2-1
Severity: important

Dear Maintainer,

   * What led up to the situation?

I run testing and have both gdb and gdb-doc installed.


   * What exactly did you do (or not do) that was effective (or
     ineffective)?

I am attempting to upgrade all packages to the latest version in
testing/jessie.


   * What was the outcome of this action?

Pressing plus on the package in Aptitude puts these messages in the
bottom frame:

  * gdb-doc breaks gdb (< 7.7)
  * gdb-doc breaks gdbserver (< 7.7)


   * What outcome did you expect instead?

For this version of gdb-doc to not be available in testing until it can
be installed alongside the gdb and gdbserver available.


This seems to sum up the problem:

% rmadison -s jessie gdb-doc gdb
 gdb     | 7.6.2-1.1    | jessie          | source
 gdb     | 7.6.2-1.1+b1 | jessie          | amd64, armel, armhf, i386, 
kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x
 gdb-doc | 7.7.1-1      | jessie/non-free | source, all


The cause of it could of course be some bug in the testing migration logic
that keeps gdb from migrating but it really does not intuitively seem
correct that gdb-doc replaces older versions of gdb and gdbserver and does
not recommend or suggest the corresponding version of gdb.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- no debconf information

Best regards
/Ulrik Haugen

--- End Message ---
--- Begin Message ---
Well, gdb has finally migrated, so I'm closing this bug to let gdb-doc
migrate too.

Ulrik Haugen <q...@lysator.liu.se> writes:

> The cause of it could of course be some bug in the testing migration logic
> that keeps gdb from migrating but it really does not intuitively seem
> correct that gdb-doc replaces older versions of gdb and gdbserver and does
> not recommend or suggest the corresponding version of gdb.

I had personally been hoping that britney would keep gdb-doc from
migrating before gdb due to the Breaks.

When I realized that it was not going to do this, I went to file a
serious bug to keep it from migrating, but someone else had already
filed a bug.  Unfortunately, someone else came along and closed that bug
after gdb made it through NEW, letting gdb-doc migrate.

Any tips on how to prevent this in the future would be greatly
appreciated.  (Failing any technical measures, I suppose it would be a
good idea to leave a note on the relevant bug to please not close it
until the relevant package migrates?)

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!

--- End Message ---

Reply via email to