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

Accepted lyskom-server 2.1.2-13 (source amd64)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 15 Nov 2012 09:26:58 +0100
Source: lyskom-server
Binary: lyskom-server
Architecture: source amd64
Version: 2.1.2-13
Distribution: unstable
Urgency: low
Maintainer: Magnus Holmgren <holmgren@debian.org>
Changed-By: Magnus Holmgren <holmgren@debian.org>
Description: 
 lyskom-server - Server for the LysKOM conference system
Closes: 689898
Changes: 
 lyskom-server (2.1.2-13) unstable; urgency=low
 .
   * New maintainer.
   * Rename debian/lyskom-server.copyright debian/copyright as a source
     package should have a debian/copyright file.
   * Create /var/run/lyskom-server in the init script instead of shipping
     it with the package (Closes: #689898). Thanks Thomas Goirand.
   * Drop the $startonboot variable, which is rather pointless since
     lyskomd is actually started via cron, is disabled there by default,
     and will start regardless of $startonboot because the status file
     won't exist.
   * Fix LSB header in the init script: add $remote_fs and move $local_fs
     to Required-Start/Required-Stop; delete commas.
   * Add dependency on rsyslog | system-log-daemon, since the LSB header
     indicates that lyskomd requires a syslog facility.
   * Rework and simplify lyskom-server.postinst:
     * Use dpkg-statoverride to set ownership of data and log directories.
     * Don't nullify errors; the package should be left in an unconfigured
       state in such cases. Remove sanity checks.
     * Simply call adduser with --quiet instead of checking whether the
       lyskom user already exists.
     * Set stricter modes on the directories.
   * Don't delete /var/run/lyskom-server/status in the init script. It is
     created by komrunning when shutting down lyskomd to keep updateLysKOM
     from starting lyskomd again.
   * lyskom-server.postrm: As recommended by policy, don't delete log files
     until on purge. Also, simply rm -rf /var/lib/lyskom-server
     /var/log/lyskom-server.
   * Add dependendy on cron | cron-daemon, since that's how lyskomd is
     started.
   * debian/rules: Add build-indep and build-arch targets.
Checksums-Sha1: 
 7c6a1c4c441574a862cc1522b46c2c2b1f6d98d4 1280 lyskom-server_2.1.2-13.dsc
 8dadcfe1f46c5f0e3ff047e77dd3c987b2738620 62669 lyskom-server_2.1.2-13.diff.gz
 c084e5b23b227c13a5a6aff95bf1b5d6f1b394b5 647948 lyskom-server_2.1.2-13_amd64.deb
Checksums-Sha256: 
 fd9628bdd65bf7786f6585cec101ac7dc4bac76c15c4419d4d48545a4ac20bbe 1280 lyskom-server_2.1.2-13.dsc
 af01b4e8fbebf8883471391e6807dcc93785ed4add83dadc514c1dc562cc6396 62669 lyskom-server_2.1.2-13.diff.gz
 882f09741a5cf9c629b538adfd2e2c1f2a70e6938d0e047c7efa8e5330537f27 647948 lyskom-server_2.1.2-13_amd64.deb
Files: 
 1fece314f4803dfe45d36e2ac8807f9a 1280 net extra lyskom-server_2.1.2-13.dsc
 05b7a0c157a4f8f203b69cc954330534 62669 net extra lyskom-server_2.1.2-13.diff.gz
 596765d230abdef75ad3b7a98858f807 647948 net extra lyskom-server_2.1.2-13_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEAREIAAYFAlCkqI8ACgkQk7mRNn1h4+birQCggaXT3jXWiMZUgFT+YjfiPMji
pQgAnRxYi1clnvrRDGHEjFg+40SS8Y9k
=iIRw
-----END PGP SIGNATURE-----


Reply to: