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

Bug#912752: marked as done (ITP: pyfuse3 -- Python 3 bindings for libfuse 3 using asynchronous I/O)

Your message dated Wed, 03 Feb 2021 00:00:13 +0000
with message-id <E1l75af-000FNQ-3D@fasolo.debian.org>
and subject line Bug#912752: fixed in pyfuse3 3.2.0-1
has caused the Debian Bug report #912752,
regarding ITP: pyfuse3 -- Python 3 bindings for libfuse 3 using asynchronous I/O
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.)


-- 
912752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912752
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Nikolaus Rath <Nikolaus@rath.org>

* Package name    : pyfuse3
  Version         : 1.1
  Upstream Author : Nikolaus Rath <Nikolaus@rath.org>
* URL             : https://github.com/libfuse/pyfuse3
* License         : LGPL
  Programming Lang: Python
  Description     : Python 3 bindings for libfuse 3 using asynchronous I/O

pyfuse3 is a set of Python 3 bindings for libfuse 3. It provides
an asynchronous API compatible with Trio.

The package will be maintained inside the Python modules team.

There are a number of Python bindings for libfuse, but most are
not compatible with libfuse3 and none supports asynchronous I/O.

I intend to upload the package as soon as someone decides
to package Trio (https://github.com/python-trio/trio).

--- End Message ---
--- Begin Message --- 
Source: pyfuse3
Source-Version: 3.2.0-1
Done: Francesco Paolo Lovergine <frankie@debian.org>

We believe that the bug you reported is fixed in the latest version of
pyfuse3, 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 912752@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine <frankie@debian.org> (supplier of updated pyfuse3 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@ftp-master.debian.org)


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

Format: 1.8
Date: Mon, 11 Jan 2021 13:07:48 +0100
Source: pyfuse3
Binary: python3-pyfuse3 python3-pyfuse3-dbg
Architecture: source amd64
Version: 3.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+python@tracker.debian.org>
Changed-By: Francesco Paolo Lovergine <frankie@debian.org>
Description:
 python3-pyfuse3 - Python 3 bindings for libfuse 3 with asynchronous API
 python3-pyfuse3-dbg - Python 3 bindings for libfuse 3 with asynchronous API (debugging
Closes: 912752
Changes:
 pyfuse3 (3.2.0-1) unstable; urgency=medium
 .
   [ Nikolaus Rath ]
   * Initial release. (Closes: #912752)
 .
   [ Francesco Paolo Lovergine ]
   * New upstream release, with two more build-deps.
   * Moved to dh-compat 13, current.
   * Policy bumped to 4.5.1.
   * Added me as an uploader.
   * Added d/gbp.conf and pristin-tar branch.
   * Revised d/copyright.
Checksums-Sha1:
 cf560f8c8a8e61c6614135bc49f019b885c4719f 2335 pyfuse3_3.2.0-1.dsc
 cacd0af07c3c68d0b9ea17f69869f92ebb8df426 465350 pyfuse3_3.2.0.orig.tar.gz
 01bddd33dd0d8a5f65c2ba03bf7a4938540d9938 135088 pyfuse3_3.2.0-1.debian.tar.xz
 181e37fb25dcf17ab2879fde82c2ecfc2b9a05ce 8924 pyfuse3_3.2.0-1_amd64.buildinfo
 ff85b5fa3e6eee27d17be75b4bf854eca7e23e16 1730784 python3-pyfuse3-dbg_3.2.0-1_amd64.deb
 0ccdca9e70a750faf452a1e60968d7060ff5c741 158092 python3-pyfuse3_3.2.0-1_amd64.deb
Checksums-Sha256:
 69bab195f7ba7bf659611454c064f0008b49bc1fee935d25146ddad997c21a9d 2335 pyfuse3_3.2.0-1.dsc
 45f0053ad601b03a36e2c283a5271403674245a66a0daf50e3deaab0ea4fa82f 465350 pyfuse3_3.2.0.orig.tar.gz
 3f5ac5806097097c7d38e6a1926caf9aa80dbdcec77af10b710b0f92de8988d1 135088 pyfuse3_3.2.0-1.debian.tar.xz
 d6aead17e019f2ab94c73a785904f84953d2e71b30183c79d7de18ee713026d2 8924 pyfuse3_3.2.0-1_amd64.buildinfo
 7a8f502403a6d95e759ec906dba99a61d0836f387d6c94c9141788e20fe535ac 1730784 python3-pyfuse3-dbg_3.2.0-1_amd64.deb
 81bab5f7a6dd09a8820d78604cf302f5cc077b937330ec9f38c571d06a84e994 158092 python3-pyfuse3_3.2.0-1_amd64.deb
Files:
 88858c3418d26c46fa977b4d721dbe4a 2335 python optional pyfuse3_3.2.0-1.dsc
 2d4177d8f24aa7c01b3eb2470215dd03 465350 python optional pyfuse3_3.2.0.orig.tar.gz
 75f96fc613a3d9cd9cbf38f4a34e7b2d 135088 python optional pyfuse3_3.2.0-1.debian.tar.xz
 2c11cdece4632d9f508a9d4d71103a23 8924 python optional pyfuse3_3.2.0-1_amd64.buildinfo
 caad51c3d3c302d4ec85ab838a87d919 1730784 debug optional python3-pyfuse3-dbg_3.2.0-1_amd64.deb
 f8a8faa6182884cac083ec5bf4ca7b00 158092 python optional python3-pyfuse3_3.2.0-1_amd64.deb

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

iQJHBAEBCgAxFiEEBXmpeiI46/m+Ye0CDwKl4RY2hqQFAl/8UXMTHGZyYW5raWVA
ZGViaWFuLm9yZwAKCRAPAqXhFjaGpB87D/9rERLOcX5XzWdYy8CdccNYfUKWjozZ
u6xt/d1y+WGJ/meObxInEOtLcAAH8YOhnSN4UBNYjDCSJ6y/I+mpHsqMWBhom2jY
pf7K3KclDx9uQ+5DsHaLAMgTRkA6GmgQVPsifoLANTXwFvpnLbe3/kk3NMBKPkHV
HmXGV7wMDlpfOLjhw2ITwBhCEdPckxAATk7Ji6cqYDsFvQ0nUd+7x4vnm9VNg3H5
Y2VNOSOb3gpvCLYdP7li0w9379G/Y9kFhw0DPTlNw8LFArdjk10KB8qnlZCjO2RN
6sr38oPMEKptcIk3/Y7ALFuwl6GARybxQ2OPY1eCr1sHqIHF3EaKe7MoDpw+rp7a
QvI3pCbguWWGZzL4g6oawqNhuT6mflgq4rKg2VHBBlhTd19uG/WmoxLVALuWssLl
U2r5fDsjvA/F6voBCizgMQ2B6+HZ8mt50XZYeJyYfZBhwNyPgQO8keecGgP7DWrN
VZ15eH8kq2Gce7tdDdfoVChGU+sv6EekeU4exp8LHqUH0PbBQJBdhHFU96KcB/45
cbf+fmn7dymAZppwNTKi5NyxI4a6GL8SGXIs+I4wGrs0PqQW7/rRNp2oVcSvWPA9
qLLhmG6PIL8qzUtVQctqWWsOj3GlkfDZox1kjA2THNXbQMSGTBOunVvo4NMuaFYa
l/ghY30LebcFbg==
=aFPD
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: