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

Bug#990289: marked as done (ITP: django-pglocks -- Django based context manager for PostgreSQL advisory locks)



Your message dated Thu, 14 Oct 2021 11:00:09 +0000
with message-id <E1mayT3-0005hn-NH@fasolo.debian.org>
and subject line Bug#990289: fixed in django-pglocks 1.0.4-1~exp1
has caused the Debian Bug report #990289,
regarding ITP: django-pglocks -- Django based context manager for PostgreSQL advisory locks
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.)


-- 
990289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990289
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Carsten Schoenert <c.schoenert@t-online.de>
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name    : django-pglocks
  Version         : 1.0.4
  Upstream Author : Christophe Pettus <xof@thebuild.com>
* URL             : https://github.com/Xof/django-pglocks
* License         : MIT
  Programming Lang: Python
  Description     : Django based context manager for PostgreSQL advisory locks

 django-pglocks is a context manager for Django.
 Advisory locks are application-level locks that are acquired and released
 purely by the client of the database; PostgreSQL never acquires them on its
 own. They are very useful as a way of signalling to other sessions that a
 higher-level resource than a single row is in use, without having to lock an
 entire table or some other structure.
 
 It's entirely up to the application to correctly acquire the right lock.
 
 Advisory locks are either session locks or transaction locks. A session lock
 is held until the database session disconnects (or is reset); a transaction
 lock is held until the transaction terminates.
 
 Currently, the context manager only creates session locks, as the behavior of
 a lock persisting after the context body has been exited is surprising, and
 there's no way of releasing a transaction-scope advisory lock except to exit
 the transaction.

This package is a dependency for netbox I consider to package.

The package will get maintained within the Debian Python Team.

--- End Message ---
--- Begin Message ---
Source: django-pglocks
Source-Version: 1.0.4-1~exp1
Done: Carsten Schoenert <c.schoenert@t-online.de>

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

Debian distribution maintenance software
pp.
Carsten Schoenert <c.schoenert@t-online.de> (supplier of updated django-pglocks 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: Thu, 24 Jun 2021 18:41:38 +0200
Source: django-pglocks
Binary: python3-django-pglocks
Architecture: source all
Version: 1.0.4-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Team <team+python@tracker.debian.org>
Changed-By: Carsten Schoenert <c.schoenert@t-online.de>
Description:
 python3-django-pglocks - Django based context manager for PostgreSQL advisory locks (Pytho
Closes: 990289
Changes:
 django-pglocks (1.0.4-1~exp1) experimental; urgency=medium
 .
   * [94a8cd9] New upstream version 1.0.4
   * [f24cd87] First and basic Debianization (Closes: #990289)
Checksums-Sha1:
 c592cc89062943bdaca636b952677e2be471379b 2156 django-pglocks_1.0.4-1~exp1.dsc
 15334e93a57581afa620a8960e3dd47b0211d873 4085 django-pglocks_1.0.4.orig.tar.gz
 893d83d1793fdfe6a0e3feefb293fccfa8688c53 3264 django-pglocks_1.0.4-1~exp1.debian.tar.xz
 04e7f0c5ba449d7928148a54f6f7d67b9ba9b4b1 6318 django-pglocks_1.0.4-1~exp1_amd64.buildinfo
 1ea3d45cebaca9664de72014309ea1bf39bf03b1 5204 python3-django-pglocks_1.0.4-1~exp1_all.deb
Checksums-Sha256:
 b98885a6a5446754174e7f9974e0e5362c005b41f6d8897ff47902c558126b86 2156 django-pglocks_1.0.4-1~exp1.dsc
 3c47c66fbfbd268ef46269673a0516a039539b0972b8ed2ec9cfee44c4b65523 4085 django-pglocks_1.0.4.orig.tar.gz
 400f66e97055e097a0dac51016cce1332c8566a75458f4664453a5281e707665 3264 django-pglocks_1.0.4-1~exp1.debian.tar.xz
 4a08409e314e9022713ecfcbb1cb1ac3b1ac90cfe1d5a254b171599ed4ad0e36 6318 django-pglocks_1.0.4-1~exp1_amd64.buildinfo
 d47bf22eabd164a13abba71d8a42b8d00db02a08120432ecd9ed5512cc85b343 5204 python3-django-pglocks_1.0.4-1~exp1_all.deb
Files:
 f9c5a4e2693b33236549955dfbc8e6b6 2156 python optional django-pglocks_1.0.4-1~exp1.dsc
 4907244be5a47d0bc618ae31ab68a9f9 4085 python optional django-pglocks_1.0.4.orig.tar.gz
 55d0ef3ec89ae40b1de19fb2bec42210 3264 python optional django-pglocks_1.0.4-1~exp1.debian.tar.xz
 09e8b253051558f64d7f961127c2c5f5 6318 python optional django-pglocks_1.0.4-1~exp1_amd64.buildinfo
 2f9245f717d210b402405162ddf6fc0a 5204 python optional python3-django-pglocks_1.0.4-1~exp1_all.deb

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

iQJMBAEBCgA2FiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAmDWOYcYHGMuc2Nob2Vu
ZXJ0QHQtb25saW5lLmRlAAoJEIMBYBQlHR2wLDQQAJA6sZLYpBXm4OKBCoFlA6Fl
y/bOHGcZyomr+XKpbhBCAyZRSnUhGYStwGay79U2SAIDWeFDEwWjYi8fUk/iunye
MnaZGpuaetblgyCvVPZh/RM8yr+z6+BeQNOoCoNnCup63xKl0Tw3MxHEOQJVhNUP
nY/YpYbqswCeYrtNyo57SxudW+Y18pvTZy5T58tFqGy4z2eYGwAz+ls+NNo9uK7Q
gbDz7UXItAFQ/nzqXzDVmqdq5KmfQH/4k113i76SzsIs4S/ULxcLECxdJH5R77AE
uGzizRazNpUn1NvoIFB/2NjVKC45AP+uzfCL3wTSIFPPZ7Yuqf3XK5aZfxweiNho
0OVAtTbVGRC2NO/JFQT3F8hg2JZ1/efxOMk6grsFRqcKAMCES+r2Wtax7ELAnd5k
DR2DVN7fqpj4uKhBZcjJBWNr32O/FG711X1VsrDGivBFfL7dxmZEasxf0+xj5rFx
/XxqKHorlmoYVJ9SVW+hwoOegSBTpc42J+uNW3/GFr9DgxLFbY6aYYVPLIuTJ6Mi
asPR9QFWEPjQT7qBpGsOKOi8z/8W7yzk/o9SJPzj3wehnpXAJdVKPdcBZfbAIf8w
4NEF91kXoyF0+zeQH7voniXR4HwXvHgE+ZSt0+V6xmncRY5bSTgOQ82r+2oOlR85
s8xKRDkO1VdsAFGsqxi1
=MZdC
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: