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

Bug#1068662: marked as done (xsecurelock references wrong xscreensaver location)

Your message dated Fri, 28 Nov 2025 20:42:39 +0000
with message-id <E1vP5Id-00GCUb-2b@fasolo.debian.org>
and subject line Bug#1068662: fixed in xsecurelock 1.9.0-3
has caused the Debian Bug report #1068662,
regarding xsecurelock references wrong xscreensaver location
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.)


-- 
1068662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068662
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: xsecurelock

The Debian 12.5 xscreensaver package installs the screensavers under
/usr/libexec/xscreensaver, but the xsecurelock package is configured
using --with-xscreensaver=/usr/lib/xscreensaver. I believe the
xsecurelock package should be updated to configure using
--with-xscreensaver=/usr/libexec/xscreensaver.

--- End Message ---
--- Begin Message --- 
Source: xsecurelock
Source-Version: 1.9.0-3
Done: Boyuan Yang <byang@debian.org>

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

Debian distribution maintenance software
pp.
Boyuan Yang <byang@debian.org> (supplier of updated xsecurelock 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: Fri, 28 Nov 2025 14:49:29 -0500
Source: xsecurelock
Architecture: source
Version: 1.9.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Boyuan Yang <byang@debian.org>
Closes: 1048384 1068662
Changes:
 xsecurelock (1.9.0-3) unstable; urgency=medium
 .
   * QA upload.
   * Upload to unstable.
   * debian/clean: Also clean autogenerated files. (Closes: #1048384)
   * debian/rules: Fix xscreensaver location. (Closes: #1068662)
   * debian/control: Move package description to source package section.
Checksums-Sha1:
 91da4f4e2227631eb522faa1ae62780ebee9d629 2527 xsecurelock_1.9.0-3.dsc
 5cc5d18c6fc4e0dc736c36505a84a27bb310f114 222849 xsecurelock_1.9.0.orig.tar.gz
 8df13ec4f9b8cb84fe79cae93ab4eca6fe99010a 3232 xsecurelock_1.9.0-3.debian.tar.xz
 72371eba794f25400ac6011b1ac8ce01dba568b2 7532 xsecurelock_1.9.0-3_amd64.buildinfo
Checksums-Sha256:
 0db107c929dd98c983bcc2d2dcb10d9578d548e92767e4ac2660025917ecc0c1 2527 xsecurelock_1.9.0-3.dsc
 6e8df4d804e388499e7a9116161a0355034d2ebb61471291383875be515e8025 222849 xsecurelock_1.9.0.orig.tar.gz
 a3e2c91f1fc6e293ff104aaaf646fc5a402b148a819ea33028c872d6af744df2 3232 xsecurelock_1.9.0-3.debian.tar.xz
 d01b8974788c7e84ef43931f33c9f5ad1da27bb924eccfcb4fec543f8385f05b 7532 xsecurelock_1.9.0-3_amd64.buildinfo
Files:
 383af98190c606426ab9fe5b034b581b 2527 x11 optional xsecurelock_1.9.0-3.dsc
 ccd6ec5ad9ee89a96020f1f9f5d642ea 222849 x11 optional xsecurelock_1.9.0.orig.tar.gz
 fc6ec1f0869e72e263192a46a3fa5f1c 3232 x11 optional xsecurelock_1.9.0-3.debian.tar.xz
 057607c18a7607cf0884fb66ee604c92 7532 x11 optional xsecurelock_1.9.0-3_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmkp/84ACgkQwpPntGGC
Ws7pZxAAqOGdSfeXFZ545wxAf62kAeBjsLyvBDkUL1LtwEzda96anZpZNheL8RTR
OfMp0EwsXMVINiJy0+QLVKQWIRBnMxdgvvqCJRCKMwNpN6p/iWFhPDsvNzb/nflO
ydFINxNeycmVuuEqpZWYyYf7fqJuzhBSwnGnTWjixG7rlDS9bHYB7tmQyzQYnRpA
aFVDiPSnO6y3D9VBAJEaZ0x42C5fZLAERcjrm1YMnMsUFrZZbM/uWLwVb2Q5/ZRW
0obNkIeD9+TCELaIxKFLYHjqTn1NL+YHkYcz30nFSlMPy73l5IFR39Bk+xdf0vGj
K0Xeb4bqs9xJblbEWrO/4vqMAPeKvQIX5o6yJ6NimzARUmC0monO3LYKXRCJOOUZ
sLjNUsW3D7s+1zYP9vpZXdQ4jYqQKFUWn/LjrqTzKN4s3UCeAASq3x/0+IuNtrzp
P54ywjbxuD8Dn5olwvZ0yLMAagXlZ85S3mdsJIwLZ63EaduwuSoFmPulIeUVS3hU
b4SclSmhhAcKFC6MRA0o1jJLXSUOZz5AQR6lqDRzimYwe1utcXTopwhuwk/eZpl7
r2oiIovzuqCY8QfmVGCPMAtJqMDohXI75q6Yc2qMteo+ljO8SoUwPHFz/qpdWHce
xZV+pYSTlIBAAN0J5Kmy2drjtKha9imH8LsaSUe8rBWRaT/Lhdk=
=4qXU
-----END PGP SIGNATURE-----

Attachment: pgpfr_MOziXeE.pgp
Description: PGP signature


--- End Message ---
Reply to: