Your message dated Sun, 17 Nov 2013 02:05:02 +0100
with message-id 
<CAK0Odpyq5LSsk=vqak7rsrrjgrrgles_csubeb7iibzjmei...@mail.gmail.com>
and subject line Re: Bug#729729: meld: Uninstallable
has caused the Debian Bug report #729729,
regarding meld: Uninstallable
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.)


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

It seems that meld is uninstallable. While upgrading to sid from a fresh 
install of
7.2, I'm getting this error from meld:

$ dpkg: dependency problems prevent configuration of meld:
 meld depends on python:any (>= 2.6.6-7~).
 
 dpkg: error processing meld (--configure):
  dependency problems - leaving unconfigured
  Errors were encountered while processing:
   meld
   E: Sub-process /usr/bin/dpkg returned an error code (1)
   E: Failed to process build dependencies
   
Apparently, below in this bug report it is claimed that "python:any" is
not installed, but I do have:

ii  python                  2.7.3-4+deb7u1   all
ii  python2.6               2.6.8-1.1        amd64
ii  python2.6-minimal       2.6.8-1.1        amd64
ii  python2.7               2.7.3-6          amd64
ii  python2.7-minimal       2.7.3-6          amd64
ii  python3                 3.3.2-17         amd64
ii  python3-minimal         3.3.2-17         amd64
ii  python3.3               3.3.2-7          amd64
ii  python3.3-minimal       3.3.2-7          amd64

Best regards
Torquil Sørensen

-- System Information:
Debian Release: 7.2
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages meld depends on:
ii  patch             2.6.1-3
ii  python-glade2     2.24.0-3+b1
ii  python-gobject-2  2.28.6-12+b1
ii  python-gtk2       2.24.0-3+b1
pn  python:any        <none>

Versions of packages meld recommends:
pn  python-gconf           <none>
pn  python-gnome2          <none>
pn  python-gtksourceview2  <none>
ii  yelp                   3.4.2-1+b1

meld suggests no packages.

-- no debconf information

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

2013/11/16 Torquil Macdonald Sørensen <torq...@gmail.com>:
> Package: meld
> Followup-For: Bug #729729
>
> I now found that I had not yet done a full upgrade from stable to sid at the
> time when apt-get install meld failed. After apt-get dist-upgrade, I can do
> apt-get install meld successfully. So maybe this could be fixed by adjusting
> dependencies for meld, but I'm not sure how myself.
The dependency is added through ${python:Depends}, thus I can't really fix that.

>
> So what I really did was to try to install meld from sid, on wheezy (or
> something halfway between wheezy and sid).
It is not expected to work. :-(

>
> So it is up to you if this is a bug or not. Since the system was confused
> about the presence of "python:any", maybe this is multiarch-related?
Most probably it was multiarch related, you probably wanted to install
a multiarch-enabled
package without the multiarch infrastructure present.

Cheers,
Balint

--- End Message ---

Reply via email to