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

Bug#497235: marked as done (ITP: libbitmask -- supports multi-word bitmask operations)

Your message dated Sat, 25 Oct 2008 10:48:16 +0000
with message-id <E1Ktggq-0008Ix-LM@ries.debian.org>
and subject line Bug#497235: fixed in libbitmask 2.0-1
has caused the Debian Bug report #497235,
regarding ITP: libbitmask -- supports multi-word bitmask operations
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.)


-- 
497235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497235
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Anibal Monsalve Salazar <anibal@debian.org>

* Package name    : libbitmask
  Version         : 2.0
  Upstream Author : Paul Jackson <pj@sgi.com>
* URL             : http://oss.sgi.com/projects/cpusets/
* License         : LGPL
  Programming Lang: C
  Description     : supports multi-word bitmask operations

 This Bitmask library supports multi-word bitmask operations for
 applications programmed in 'C'. It works in conjunction with recent
 Linux kernel support for processor and memory placement on
 multiprocessor SMP and NUMA systems. The cpuset library, being
 developed in parallel, depends on this bitmask library.
 .
 Bitmasks provide multi-word bit masks and operations thereon to do
 such things as set and clear bits, intersect and union masks,
 query bits, and display and parse masks.
 .
 The initial intended use for these bitmasks is to represent sets of
 CPUs and Memory Nodes, when configuring large SMP and NUMA systems.
 However there is little in the semantics of bitmasks that is
 specific to this particular use, and bitmasks should be usable for
 other purposes that had similar design requirements.
 .
 These bitmasks share the same underlying layout as the bitmasks
 used by the Linux kernel to represent sets of CPUs and Memory
 Nodes. Unlike the kernel bitmasks, these bitmasks use dynamically
 allocated memory and are manipulated via a pointer. This enables a
 program to work correctly on systems with various numbers of CPUs
 and Nodes, without recompilation.
 .
 There is a related cpuset library which uses the bitmask type
 provided here to represent sets of CPUs and Memory Nodes. The
 internal representation (as an array of unsigned longs, in little
 endian order) is directly compatible with the sched_setaffinity(2)
 and sched_getaffinity(2) system calls (added in Linux 2.6).

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Source: libbitmask
Source-Version: 2.0-1

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

libbitmask-dev_2.0-1_amd64.deb
  to pool/main/libb/libbitmask/libbitmask-dev_2.0-1_amd64.deb
libbitmask1_2.0-1_amd64.deb
  to pool/main/libb/libbitmask/libbitmask1_2.0-1_amd64.deb
libbitmask_2.0-1.diff.gz
  to pool/main/libb/libbitmask/libbitmask_2.0-1.diff.gz
libbitmask_2.0-1.dsc
  to pool/main/libb/libbitmask/libbitmask_2.0-1.dsc
libbitmask_2.0.orig.tar.gz
  to pool/main/libb/libbitmask/libbitmask_2.0.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 497235@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anibal Monsalve Salazar <anibal@debian.org> (supplier of updated libbitmask 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: SHA1

Format: 1.8
Date: Mon, 25 Aug 2008 20:13:00 +1000
Source: libbitmask
Binary: libbitmask-dev libbitmask1
Architecture: source amd64
Version: 2.0-1
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar <anibal@debian.org>
Changed-By: Anibal Monsalve Salazar <anibal@debian.org>
Description: 
 libbitmask-dev - header files and docs for libbitmask
 libbitmask1 - supports multi-word bitmask operations
Closes: 497235
Changes: 
 libbitmask (2.0-1) unstable; urgency=low
 .
   * Initial release; closes: #497235
Checksums-Sha1: 
 fcc15ea389947f6525d529ae07c45074b1e9e70f 1054 libbitmask_2.0-1.dsc
 6adaf78e5d3c6435ba2c43a770ad458950568f2c 117512 libbitmask_2.0.orig.tar.gz
 2328709954ba83b79bf4fc5dd56b04557702edb1 2481 libbitmask_2.0-1.diff.gz
 8f684a193445fb12647f5455352ab32727394363 31350 libbitmask-dev_2.0-1_amd64.deb
 960fd51da1358f84286840ad1c510311c54f1b1d 9646 libbitmask1_2.0-1_amd64.deb
Checksums-Sha256: 
 9906f81c8e72fa5b028bce666a7630208f0ce5a5f761800061b847cf21ca83cc 1054 libbitmask_2.0-1.dsc
 e66e509ba71c780cecde2b39432378b3fc74503a4dbb280c3bfd4c95fc887ddb 117512 libbitmask_2.0.orig.tar.gz
 02652005b92e8ddb4d8cee05ffcdb223dae2cdfd29d1703d873d3269a79b4f0a 2481 libbitmask_2.0-1.diff.gz
 1d51e100e16e80f0c5126dddadedcdea5417c7651c5e34a5c2644c21790a4fd0 31350 libbitmask-dev_2.0-1_amd64.deb
 666693d1d1108f632559a7fe2c1113e6e8b8bcc6cee858605f81a1e0e3eecfa3 9646 libbitmask1_2.0-1_amd64.deb
Files: 
 340cd93a1ded1e916c83372d3f1bda3b 1054 libs optional libbitmask_2.0-1.dsc
 10ed091f41024d4bea48a25e09931f7f 117512 libs optional libbitmask_2.0.orig.tar.gz
 3f27fa23112d507befd031e4834e6f26 2481 libs optional libbitmask_2.0-1.diff.gz
 226013f5153f4dc6fe0562da58099a56 31350 libdevel optional libbitmask-dev_2.0-1_amd64.deb
 7cbc04004a3788774619293d8b98547d 9646 libs optional libbitmask1_2.0-1_amd64.deb

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

iEYEARECAAYFAki6UQ4ACgkQgY5NIXPNpFW8WgCcClYzbNjARwEJIN3oZasTOyhw
sjUAn2yhaEoLHGel/xGemIro5uY1vwDZ
=BzEh
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: