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

Bug#939763: marked as done (sphinxsearch: Still maintained (same version since stretch)?)

Your message dated Fri, 03 Dec 2021 10:07:02 +0000
with message-id <E1mt5T4-000By8-24@fasolo.debian.org>
and subject line Bug#939763: fixed in sphinxsearch 2.2.11-5
has caused the Debian Bug report #939763,
regarding sphinxsearch: Still maintained (same version since stretch)?
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.)


-- 
939763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939763
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: sphinxsearch
Severity: important

Hi

While checking another issue I noticed that sphinxsearch is at 2.2.11
since stretch and was never updated to as well more recent 3.x
version. It has unsafe defaults in sample files with listener
listening to 0.0.0.0, cf. #939762.

Is sphinxsearch still of use or should it be removed from unstable and
not included in bullseye?

Regards,
Salvatore

--- End Message ---
--- Begin Message --- 
Source: sphinxsearch
Source-Version: 2.2.11-5
Done: Andrej Shadura <andrewsh@debian.org>

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

Debian distribution maintenance software
pp.
Andrej Shadura <andrewsh@debian.org> (supplier of updated sphinxsearch 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: SHA256

Format: 1.8
Date: Fri, 03 Dec 2021 10:41:03 +0100
Source: sphinxsearch
Architecture: source
Version: 2.2.11-5
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura <andrewsh@debian.org>
Changed-By: Andrej Shadura <andrewsh@debian.org>
Closes: 656326 772370 861262 871944 939763
Changes:
 sphinxsearch (2.2.11-5) unstable; urgency=medium
 .
   * New maintainer (Closes: #939763).
   * Add gbp.conf.
   * Convert copyright file to machine-readable format.
   * Add exclusions for current and future releases.
   * Simplify the init script (Closes: #861262, #772370, #656326).
   * Fix the crontab user (Closes: #656326).
   * Update the sample/minimal conf files to match installation paths.
   * Don't install an extra copy of the configuration sample.
   * debian/copyright: use spaces rather than tabs to start continuation lines.
   * Set Standards-Version: 4.6.0.
   * Drop B-D on dh-autoreconf, autotools-dev and adduser.
   * Enable re2 support.
   * Move the example.sql to /usr/share/doc (Closes: #871944).
Checksums-Sha1:
 8bac5c0abc5e0fccd053f8951695c1821d5cada3 1453 sphinxsearch_2.2.11-5.dsc
 2f581af4f6e7fd051e4d31a580225d35801126e4 16816 sphinxsearch_2.2.11-5.debian.tar.xz
Checksums-Sha256:
 e02f2339e87ff419ed86ac676ecc178b0c8bbde78fc83b6fe50df9213d331bfa 1453 sphinxsearch_2.2.11-5.dsc
 560d216482ef2f96d2f1570abbe112e4984758dc28008155b9b703ef860c7eed 16816 sphinxsearch_2.2.11-5.debian.tar.xz
Files:
 d4b1ac04a5e83c3670219106706feb39 1453 misc optional sphinxsearch_2.2.11-5.dsc
 870bc8f3c0b711f7276265e7c336c99c 16816 misc optional sphinxsearch_2.2.11-5.debian.tar.xz

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

iHUEARYIAB0WIQSD3NF/RLIsyDZW7aHoRGtKyMdyYQUCYanpSQAKCRDoRGtKyMdy
YfyXAP9cLvrBstyzrkWFSGqSuitY5DfxKvQRCd4Lt2LPOhMQnAEA4h5eAJ56U+vr
klFVv/KBHCsbPweDegj2TJ6YIS+Fiwg=
=QxDx
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: