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

Bug#668219: marked as done (ITP: otf -- Open Trace Format support library)



Your message dated Sun, 20 May 2012 16:32:42 +0000
with message-id <E1SW93i-0005dL-1j@franck.debian.org>
and subject line Bug#668219: fixed in otf 1.10.2+dfsg-1
has caused the Debian Bug report #668219,
regarding ITP: otf -- Open Trace Format support library
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 owner@bugs.debian.org
immediately.)


-- 
668219: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668219
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Samuel Thibault <sthibault@debian.org>

* Package name    : otf
  Version         : 1.8.1
  Upstream Author : TU dresden
* URL             : http://www.tu-dresden.de/zih/otf
* License         : BSD
  Programming Lang: C
  Description     : Open Trace Format (OTF) support library

OTF is a standard trace format used by several high-performance tools,
using an ASCII encoding, which supports multiple streams. The libotf
provides support for reading/writing them.



libotf is actually already used by openmpi, could be used by vite, and
by the prospective eztrace package (ITP #658116).

There is already a libotf in debian, for handling OpenType Font. What
I intend to do is renaming the so to allow co-installation, but
keep development file names as is and use a conflict between -dev
packages. Does it sound OK?



--- End Message ---
--- Begin Message ---
Source: otf
Source-Version: 1.10.2+dfsg-1

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

libotf-trace-dev_1.10.2+dfsg-1_amd64.deb
  to main/o/otf/libotf-trace-dev_1.10.2+dfsg-1_amd64.deb
libotf-trace1_1.10.2+dfsg-1_amd64.deb
  to main/o/otf/libotf-trace1_1.10.2+dfsg-1_amd64.deb
libotfaux0_1.10.2+dfsg-1_amd64.deb
  to main/o/otf/libotfaux0_1.10.2+dfsg-1_amd64.deb
otf-trace_1.10.2+dfsg-1_amd64.deb
  to main/o/otf/otf-trace_1.10.2+dfsg-1_amd64.deb
otf_1.10.2+dfsg-1.debian.tar.gz
  to main/o/otf/otf_1.10.2+dfsg-1.debian.tar.gz
otf_1.10.2+dfsg-1.dsc
  to main/o/otf/otf_1.10.2+dfsg-1.dsc
otf_1.10.2+dfsg.orig.tar.gz
  to main/o/otf/otf_1.10.2+dfsg.orig.tar.gz



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

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

Debian distribution maintenance software
pp.
Samuel Thibault <sthibault@debian.org> (supplier of updated otf 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)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 20 Apr 2012 14:38:31 +0200
Source: otf
Binary: otf-trace libotf-trace-dev libotf-trace1 libotfaux0
Architecture: source amd64
Version: 1.10.2+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Samuel Thibault <sthibault@debian.org>
Changed-By: Samuel Thibault <sthibault@debian.org>
Description: 
 libotf-trace-dev - Open Trace Format support library - development files
 libotf-trace1 - Open Trace Format support library - shared library
 libotfaux0 - Open Trace Format support library - shared library
 otf-trace  - Open Trace Format support library - development files
Closes: 668219
Changes: 
 otf (1.10.2+dfsg-1) unstable; urgency=low
 .
   * Initial release (Closes: #668219)
Checksums-Sha1: 
 6232a14fcc43488520cf675bac2fc481f1a57492 1503 otf_1.10.2+dfsg-1.dsc
 c29d71d38226a9cef56921adc265d345c21db501 774120 otf_1.10.2+dfsg.orig.tar.gz
 a85ec1511f3bc86a3c8fba107eeaa8c32396790f 3846 otf_1.10.2+dfsg-1.debian.tar.gz
 dcdec82ccc16a99cb8811db0b2e30cde1c1f83f4 297934 otf-trace_1.10.2+dfsg-1_amd64.deb
 2db490d9712501a170364097ead847630de52178 163486 libotf-trace-dev_1.10.2+dfsg-1_amd64.deb
 3ba894b8aef84e21a88c8a64013673edbfd9c8bf 97774 libotf-trace1_1.10.2+dfsg-1_amd64.deb
 09a282ff42f1fa4067dab8fc683c272d53cea0ec 15800 libotfaux0_1.10.2+dfsg-1_amd64.deb
Checksums-Sha256: 
 01bd5e6519f93e65ae8bb4fda125b8183d4bb8ff621a0d193a4d2d3a96199216 1503 otf_1.10.2+dfsg-1.dsc
 e21b8b2554a1b8c05820b4976f3a905b891fa79b7de58b57a4258fae8237ef1b 774120 otf_1.10.2+dfsg.orig.tar.gz
 066ac996d9042fb4a30eb04383470eb2841df6b7f314c00286ff248d181a09dc 3846 otf_1.10.2+dfsg-1.debian.tar.gz
 158cd99e5364aed7dbb2eebfc4d8cdf045b77b5e3ea5968177d5e8d2f679888a 297934 otf-trace_1.10.2+dfsg-1_amd64.deb
 bfc68006d6993c0bc4a05822f7725a0b0ddf0ec5bbda6cda8cc1ee08617db2a2 163486 libotf-trace-dev_1.10.2+dfsg-1_amd64.deb
 2a05aea6702aec96f656e5e8b042a859e9868ea12a8cbb1009d610b179243059 97774 libotf-trace1_1.10.2+dfsg-1_amd64.deb
 85da2d630b1fb9d7468c334277e84f3da776636a7a48c2b85099eeed700854cb 15800 libotfaux0_1.10.2+dfsg-1_amd64.deb
Files: 
 ec379ecf739dc61286c125657498ee77 1503 libs extra otf_1.10.2+dfsg-1.dsc
 c7e0fcbef8a4af7caa140061ca16776a 774120 libs extra otf_1.10.2+dfsg.orig.tar.gz
 465e7b4ebbe37c5477944b5ed3ff4404 3846 libs extra otf_1.10.2+dfsg-1.debian.tar.gz
 07b0d64b1f426a460346b3ffe8cb032f 297934 science extra otf-trace_1.10.2+dfsg-1_amd64.deb
 9baddaf3d06e49ccd4e697e0f1da1c17 163486 libdevel extra libotf-trace-dev_1.10.2+dfsg-1_amd64.deb
 9fc373472b37821f60f4db0d9b2e39d5 97774 libs extra libotf-trace1_1.10.2+dfsg-1_amd64.deb
 f25d0a2591436c5d287ca14cb9ba762a 15800 libs extra libotfaux0_1.10.2+dfsg-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iF4EAREKAAYFAk+pbf4ACgkQUesQhRznqygrMwEAtJIehcDqaTA9PK8AKN2F5V2P
dQL3ROZI6zEvIYasZrMA/RIX2HGIFb226cwiCHbqcUKxm3ZM6ItWLH56WgnZ2pt+
=FlKJ
-----END PGP SIGNATURE-----



--- End Message ---

Reply to: