Your message dated Fri, 9 Sep 2016 23:04:01 +0200
with message-id <[email protected]>
and subject line Re: libgtk2.0-0: triggers ci file contains unknown directive
`interest-noawait' (needs newer dpkg)
has caused the Debian Bug report #722355,
regarding libgtk2.0-0: triggers ci file contains unknown directive
`interest-noawait' (needs newer dpkg)
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 [email protected]
immediately.)
--
722355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722355
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libgtk2.0-0
Version: 2.24.20-1
Severity: important
Dear Maintainer,
Upgrading to libgtk2.0-0 on a legacy system wedges apt due to an
undeclared dependency on a newer version of dpkg (1.17?).
It is traditional, if not release critical, for inter-package
dependencies to be explicitly declared. A "Pre-Depends" will solve the
problem for the many users who will soon stumble onto this issue due to
wide-spread dependencies on gtk2. There are other solutions, but an
unstated dependency on someone else globally fixing the problem is not
really one of them.
See bug #714409 and bug #709443 for the same problem in gtk3 and texinfo,
respectively.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.39.1-linode34 (SMP w/8 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) (ignored: LC_ALL set to
en_US)
Shell: /bin/sh linked to /bin/bash
Versions of packages libgtk2.0-0 depends on:
ii libatk1.0-0 1.28.0-1
ii libc6 2.17-92
ii libcairo2 1.10.2-6
ii libcomerr2 1.42.4-3
ii libcups2 1.6.3-1
ii libfontconfig1 2.10.2-2
ii libfreetype6 2.4.2-2.1
ii libgcrypt11 1.5.3-2
ii libgdk-pixbuf2.0-0 2.28.2-1
ii libglib2.0-0 2.36.4-1
ii libgnutls26 2.12.20-1
ii libgssapi-krb5-2 1.10.1+dfsg-1
ii libgtk2.0-common 2.24.20-1
ii libk5crypto3 1.10.1+dfsg-1
ii libkrb5-3 1.10.1+dfsg-1
ii libpango-1.0-0 1.32.5-5+b1
ii libpangocairo-1.0-0 1.32.5-5+b1
ii libpangoft2-1.0-0 1.32.5-5+b1
ii libx11-6 2:1.6.1-1
ii libxcomposite1 1:0.4.4-1
ii libxcursor1 1.1.7-4
ii libxdamage1 1:1.1.4-1
ii libxext6 1:1.0.1-2
ii libxfixes3 1:4.0.1-5
ii libxi6 1:1.0.1-4
ii libxinerama1 2:1.1.3-1
ii libxrandr2 2:1.4.1-1
ii libxrender1 1:0.9.1-3
ii multiarch-support 2.13-10
ii shared-mime-info 0.70-1
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages libgtk2.0-0 recommends:
ii hicolor-icon-theme 0.12-1
pn libgtk2.0-bin <none>
Versions of packages libgtk2.0-0 suggests:
pn gvfs <none>
pn librsvg2-common <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, 10 Sep 2013 10:11:51 -0400 greg <[email protected]> wrote:
> Package: libgtk2.0-0
> Version: 2.24.20-1
> Severity: important
>
> Dear Maintainer,
>
> Upgrading to libgtk2.0-0 on a legacy system wedges apt due to an
> undeclared dependency on a newer version of dpkg (1.17?).
>
> It is traditional, if not release critical, for inter-package
> dependencies to be explicitly declared. A "Pre-Depends" will solve the
> problem for the many users who will soon stumble onto this issue due to
> wide-spread dependencies on gtk2. There are other solutions, but an
> unstated dependency on someone else globally fixing the problem is not
> really one of them.
>
Even oldstable has a recent enough dpkg and dist-upgrades are only
supported from one version to the next. So it's safe to close this old
bug report.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
