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

Bug#388807: marked as done (libxcomposite1: Please can we have 0.3?)



Your message dated Sat, 30 Sep 2006 01:03:23 +0200
with message-id <20060929230323.GA24654@bee.dooz.org>
and subject line libxcomposite1: Please can we have 0.3?
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: libxcomposite1
Version: 1:0.2.2.2-3
Severity: wishlist

Are there any plans to upload libXcomposite 0.3 to the archive? My
understanding is that this is part of what's required to take advantage
of the shiny new composite extension present in 7.1 that's recently hit
unstable.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages libxcomposite1 depends on:
ii  libc6                        2.3.6.ds1-4 GNU C Library: Shared libraries
ii  libx11-6                     2:1.0.0-9   X11 client-side library
ii  libxext6                     1:1.0.1-2   X11 miscellaneous extension librar
ii  libxfixes3                   1:4.0.1-4   X11 miscellaneous 'fixes' extensio
ii  x11-common                   1:7.1.0-1   X Window System (X.Org) infrastruc

libxcomposite1 recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1:0.3-1

        Hi,

On Fri, Sep 22, 2006, Jonathan McDowell wrote:
> Are there any plans to upload libXcomposite 0.3 to the archive? My
> understanding is that this is part of what's required to take advantage
> of the shiny new composite extension present in 7.1 that's recently hit
> unstable.

 It's in, closing the bug.

-- 
Loïc Minier <lool@dooz.org>

--- End Message ---

Reply to: