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

Bug#369102: marked as done (x11proto-render-dev: Dummy package still needed?)

Your message dated Mon, 03 Sep 2007 16:32:09 +0000
with message-id <E1ISEqP-0002Sf-C7@ries.debian.org>
and subject line Bug#369102: fixed in x11proto-render 2:0.9.3-1
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: x11proto-render-dev
Version: 2:0.9.2-3
Severity: wishlist

your package builds 'render-dev' for transitional purposes. Currently
there are only 2 packages left (in sid) which depend on render-dev
- xorg-x11 (6.9)
- openoffice.org (bug for changing the dependency has been filed).

Is this dummy still needed after resolving these 2 occurrences?


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

Versions of packages x11proto-render-dev depends on:
ii  x11-common                    1:7.0.20   X Window System (X.Org) infrastruc

x11proto-render-dev recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: x11proto-render
Source-Version: 2:0.9.3-1

We believe that the bug you reported is fixed in the latest version of
x11proto-render, which is due to be installed in the Debian FTP archive:

  to pool/main/x/x11proto-render/x11proto-render-dev_0.9.3-1_all.deb
  to pool/main/x/x11proto-render/x11proto-render_0.9.3-1.diff.gz
  to pool/main/x/x11proto-render/x11proto-render_0.9.3-1.dsc
  to pool/main/x/x11proto-render/x11proto-render_0.9.3.orig.tar.gz

A summary of the changes between this version and the previous one is

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 369102@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
Julien Cristau <jcristau@debian.org> (supplier of updated x11proto-render package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)

Hash: SHA1

Format: 1.7
Date: Mon, 03 Sep 2007 18:20:18 +0200
Source: x11proto-render
Binary: x11proto-render-dev
Architecture: source all
Version: 2:0.9.3-1
Distribution: experimental
Urgency: low
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Julien Cristau <jcristau@debian.org>
 x11proto-render-dev - X11 Render extension wire protocol
Closes: 369102
 x11proto-render (2:0.9.3-1) experimental; urgency=low
   [ Brice Goglin ]
   * Drop render-dev transitional package since nobody in Etch uses it,
     thanks Stefan Huehner, closes: #369102.
   * Add URL in debian/copyright.
   * Make the description more clear about providing development headers.
   * Update references to upstream in the long description.
   * Add XS-Vcs-* to debian/control.
   * Remove Fabio from Uploaders, with his permission.
   [ Julien Cristau ]
   * New upstream release.
   * Add myself to Uploaders and remove Branden with his permission.
 682092eeaa1230d702d8b8db77a3270d 876 x11 optional x11proto-render_0.9.3-1.dsc
 ab8f3e356973d9c99810a8f092db3a2e 62235 x11 optional x11proto-render_0.9.3.orig.tar.gz
 8b9f41d025d1dc3b559fc919e463d4d2 18321 x11 optional x11proto-render_0.9.3-1.diff.gz
 a3ccd539d2a6c1cd9eaa0cb4eb442093 7018 x11 optional x11proto-render-dev_0.9.3-1_all.deb

Version: GnuPG v1.4.6 (GNU/Linux)


--- End Message ---

Reply to: