Your message dated Thu, 16 Jul 2020 08:10:17 +0000
with message-id <e1jvyy9-0008wg...@fasolo.debian.org>
and subject line Bug#964057: fixed in readerwriterqueue 1.0.2-1
has caused the Debian Bug report #964057,
regarding ITP: readerwriterqueue -- single-producer, single-consumer lock-free 
queue for C++
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 ow...@bugs.debian.org
immediately.)


-- 
964057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist

Subject: ITP: readerwriterqueue -- single-producer, single-consumer lock-free 
queue for C++
Package: wnpp
Owner: Steffen Moeller <moel...@debian.org>
Severity: wishlist

* Package name    : readerwriterqueue
  Version         : 1.0.2
  Upstream Author : Cameron Desrochers  
* URL             : https://github.com/cameron314/readerwriterqueue
* License         : BSD
  Programming Lang: C
  Description     : single-producer, single-consumer lock-free queue for C++
 This package provides a lock-free queue  for C++.  It only supports
 a two-thread use case (one consuming, and one producing). The threads
 can't switch roles, though you could use this queue completely from a
 single thread if you wish (but that would sort of defeat the purpose!).
 .
 Features:
  * Blazing fast
  * Compatible with C++11 (supports moving objects instead of making
  copies)
  * Fully generic (templated container of any type) -- just like
    std::queue, you never need to allocate memory for elements yourself
    (which saves you the hassle of writing a lock-free memory manager
    to hold the elements you're queueing)
  * Allocates memory up front, in contiguous blocks
  * Provides a try_enqueue method which is guaranteed never to allocate
    memory (the queue starts with an initial capacity)
  * Also provides an enqueue method which can dynamically grow the size
    of the queue as needed
  * Also provides try_emplace/emplace convenience methods
  * Has a blocking version with wait_dequeue
  * Completely "wait-free" (no compare-and-swap loop). Enqueue and
    dequeue are always O(1) (not counting memory allocation)
  * On x86, the memory barriers compile down to no-ops, meaning enqueue
    and dequeue are just a simple series of loads and stores (and
    branches)

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/readerwriterqueue

--- End Message ---
--- Begin Message ---
Source: readerwriterqueue
Source-Version: 1.0.2-1
Done: Steffen Moeller <moel...@debian.org>

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

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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steffen Moeller <moel...@debian.org> (supplier of updated readerwriterqueue 
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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 30 Jun 2020 23:15:23 +0200
Source: readerwriterqueue
Binary: libreaderwriterqueue-dev
Architecture: source all
Version: 1.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 
<debian-med-packag...@lists.alioth.debian.org>
Changed-By: Steffen Moeller <moel...@debian.org>
Description:
 libreaderwriterqueue-dev - single-producer, single-consumer lock-free queue 
for C++
Closes: 964057
Changes:
 readerwriterqueue (1.0.2-1) unstable; urgency=medium
 .
   * Initial release (Closes: #964057)
Checksums-Sha1:
 a507290e7037616fd3bf1174ac55c793c408451a 2064 readerwriterqueue_1.0.2-1.dsc
 6bed9095e09cfd1d20bb73074e90cedaa83a02d7 37032 
readerwriterqueue_1.0.2.orig.tar.gz
 1d626cc5f2464dafb84f28794792619f12841f45 3432 
readerwriterqueue_1.0.2-1.debian.tar.xz
 250e04a10fdc5cb235fd683bf3a1b90544f39a5b 15248 
libreaderwriterqueue-dev_1.0.2-1_all.deb
 473fea98b058136157cef5da7b6d3e96d9d1d1af 5566 
readerwriterqueue_1.0.2-1_amd64.buildinfo
Checksums-Sha256:
 a9991c9afdfff98c5e879ef751326360e0677f655705a5499ea9263d7c35e2e2 2064 
readerwriterqueue_1.0.2-1.dsc
 cbefc020dfa4c767c11919e918dddd1d2a9890188ec7fe5117fcaaad2b0c8623 37032 
readerwriterqueue_1.0.2.orig.tar.gz
 02423ebf1444db1e48c71e44a41ca40fa944038a63f617333d57736ebe592fff 3432 
readerwriterqueue_1.0.2-1.debian.tar.xz
 9a8d54b8fc6ee3689840d7fab4710e4a1f14ea1da458c244ef6f8a834836e37a 15248 
libreaderwriterqueue-dev_1.0.2-1_all.deb
 578d1867bb547ef9808bdadc04df728451990ef800c4b036f32048c02aafa66c 5566 
readerwriterqueue_1.0.2-1_amd64.buildinfo
Files:
 48f90c75ef5c3e4771480da81b0f0b88 2064 devel optional 
readerwriterqueue_1.0.2-1.dsc
 9e355a2660bd2810cb1874fb7366906e 37032 devel optional 
readerwriterqueue_1.0.2.orig.tar.gz
 883a132f2cf26151719719c86e22f5a5 3432 devel optional 
readerwriterqueue_1.0.2-1.debian.tar.xz
 6363f0450b78ae008375e44e18330a9f 15248 libdevel optional 
libreaderwriterqueue-dev_1.0.2-1_all.deb
 9149d1cc94978b5589f624582702e73b 5566 devel optional 
readerwriterqueue_1.0.2-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl8CLCIRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtER8xAAlnuhoEW2ipK04L9FpmM+6VormIyb1mm+
qBrXnYJEiBLZRSMcYaPUsIi16L7ttSBHog6QJ6WcWh/62oAR+kIy8XcR0ivPPbNF
Xs24V9JS4QoJQFj6/MFsKs3LJ+LN4nrdDZwZ4pFkWJggGpYDnM0Ec6m+yYlIxjC7
UMeu+sMOV1I3uLOVlmAXN2xLIuIY+tYTKnjWd5auPOunvN8UKoowv/n8qVRvV3NQ
4eZGIapX00xfMnVM96/YEDDGhzxy6rgFdrtyvSYFKaQayJQamscSiGSmnWE20G5H
fFAvMfrzhYueqL2o/+VQj8K/pQKv2xnzTmbW/TAC9KulPbqhdG5q+sBk+RlG1Ke/
mmJnXjepH0V27JAQAtXTJS2DB40U1ftwJDiSlUQyxN6XstnJ/YwP4d0C4NH+VffT
/l+GZdVTwY7inJ5Bd2JvajV6v25aRK/HfWKvnMMB+C19h4vUKDUI0OIVwG9H4TrH
pQ4wifUiFxACj3KKqOTBdzlWCc2ItvuGLe9gmoxZYwRpYNBR1+8cyexpyCOM7lFO
yGwXLtc+Qpv0j7kfwZu61Wg4Ej84in/FOl4MFtpZMsoN+/wWnnqp4GPkMk5iB4QF
0ThDj/6+kJ3mbkj8O84s9Yh9ZjbRTjJNgfaThHPqdZQHPppj0hn4FfpLrKoJUeZx
An82bKM5cXA=
=q0Oe
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to