Your message dated Thu, 21 Oct 2021 16:09:16 +0200
with message-id <[email protected]>
and subject line Re: pyinotify: fix the git repo
has caused the Debian Bug report #955628,
regarding pyinotify: fix the git repo
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 [email protected]
immediately.)
--
955628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955628
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pyinotify
Severity: important
Hello,
pyinotify git repo is in a poor state:
- 0.9.6-1 was uploaded in 2016 but never officially made it into the repo
- there has been 2 NMUs since then, that are not in the repo (another one is
coming in the next few minutes)
- further changes have been made to master, further diverging from the archive
state and the git state
in order to function as a team, we need repos that are up-to-date and in sync
with the archive.
Regards,
Sandro
-- System Information:
Debian Release: 10.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
On Fri, 03 Apr 2020 12:02:54 -0400 Sandro Tosi <[email protected]> wrote:
pyinotify git repo is in a poor state:
- 0.9.6-1 was uploaded in 2016 but never officially made it into the repo
- there has been 2 NMUs since then, that are not in the repo (another one is
coming in the next few minutes)
- further changes have been made to master, further diverging from the archive
state and the git state
master is now in a state that new changes can be accepted.
--- End Message ---
