Please remove "lizardfs" from "unstable".

The package is no longer properly maintained upstream and it FTBFS here
in Debian.

Thanks.

LizardFS users should migrate to MooseFS.
---

The end cannot justify the means for the simple and obvious reason that the
means employed determine the nature of the ends produced.
 -- Aldous Huxley

---

"Increased emergency cardiovascular events among under-40 population in
Israel during vaccine rollout and third COVID-19 wave" (2022-04-28)
 -- https://www.nature.com/articles/s41598-022-10928-z#Sec14

"MIT study has found a 25% increase in cardiovascular events in young
people during the vaccine rollout. Excess deaths are associated with
vaccine rollouts all over the world." -- Dr. Simone Gold

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

  lizardfs | 3.12.0+dfsg-3 | source
  lizardfs | 3.12.0+dfsg-4 | source
lizardfs-adm | 3.12.0+dfsg-3+b10 | armel, mipsel
lizardfs-adm | 3.12.0+dfsg-4 | amd64, arm64, armhf, i386, mips64el, ppc64el, s390x
lizardfs-cgi | 3.12.0+dfsg-3 | all
lizardfs-cgi | 3.12.0+dfsg-4 | all
lizardfs-cgiserv | 3.12.0+dfsg-3+b10 | armel, mipsel
lizardfs-cgiserv | 3.12.0+dfsg-4 | amd64, arm64, armhf, i386, mips64el, ppc64el, s390x
lizardfs-chunkserver | 3.12.0+dfsg-3+b10 | armel, mipsel
lizardfs-chunkserver | 3.12.0+dfsg-4 | amd64, arm64, armhf, i386, mips64el, ppc64el, s390x
lizardfs-client | 3.12.0+dfsg-3+b10 | armel, mipsel
lizardfs-client | 3.12.0+dfsg-4 | amd64, arm64, armhf, i386, mips64el, ppc64el, s390x
lizardfs-common | 3.12.0+dfsg-3 | all
lizardfs-common | 3.12.0+dfsg-4 | all
lizardfs-master | 3.12.0+dfsg-3+b10 | armel, mipsel
lizardfs-master | 3.12.0+dfsg-4 | amd64, arm64, armhf, i386, mips64el, ppc64el, s390x
lizardfs-metalogger | 3.12.0+dfsg-3+b10 | armel, mipsel
lizardfs-metalogger | 3.12.0+dfsg-4 | amd64, arm64, armhf, i386, mips64el, ppc64el, s390x

------------------- Reason -------------------
ROM; obsolete; FTBFS
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1010587@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1010587

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)