Accepted 389-admin 1.1.46-1 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 04 Oct 2017 20:54:19 +0300
Source: 389-admin
Binary: libds-admin-serv0 389-admin
Architecture: source
Version: 1.1.46-1
Distribution: unstable
Urgency: medium
Maintainer: Debian 389ds Team <pkg-fedora-ds-maintainers@lists.alioth.debian.org>
Changed-By: Timo Aaltonen <tjaalton@debian.org>
Description:
389-admin - 389 Directory Administration Server
libds-admin-serv0 - Libraries for the 389 Directory Administration Server
Closes: 870032
Launchpad-Bugs-Fixed: 1652476
Changes:
389-admin (1.1.46-1) unstable; urgency=medium
.
* New upstream release.
* rules, postinst: Don't fail the install when the unconfigured
service doesn't start. (Closes: 870032) (LP: #1652476)
* patches: Refreshed.
* local-options: Add VERSION.sh to extend-diff-ignore.
* Bump debhelper compat to 10.
* Update upstream URLs.
* Bump policy to 4.1.1, no changes.
* dirs, postrm: Add a dir for logs, and remove all cruft on purge.
* Fix systemd service to stop properly.
* Remove adm.conf example, it's useless.
Checksums-Sha1:
9dd5a6d536316edec3f07ab413d31f6e680f52fe 2228 389-admin_1.1.46-1.dsc
735c51c0f19e448fbe9f552893ee4f9297420831 662165 389-admin_1.1.46.orig.tar.bz2
01cc5e90598fef051c948c1ada38965bbb53baac 13556 389-admin_1.1.46-1.debian.tar.xz
Checksums-Sha256:
c7f69a01682b24f7fdcd3a3e25d05a63b0df5aa9d675d15abde2a764aecc75cf 2228 389-admin_1.1.46-1.dsc
6e1da6f8494bc6693cb50f77db448e3c3aa7cd96470f92ef95ed4b784e7b58fe 662165 389-admin_1.1.46.orig.tar.bz2
1eda3fd045fb9593c03dceaab7759e9fe5392ed5b1bb4a229b0d883dd05aac83 13556 389-admin_1.1.46-1.debian.tar.xz
Files:
3ed96a8b74415fd282c1958fcfc878ce 2228 net optional 389-admin_1.1.46-1.dsc
9bae6245eafe691cf47d20ba04e59fa9 662165 net optional 389-admin_1.1.46.orig.tar.bz2
21c54fda440c4d1dbb39e0e0364084a0 13556 net optional 389-admin_1.1.46-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJZ1SBWAAoJEMtwMWWoiYTceNEP/07e00U8gSfFhYT7kWzdpdpd
nS7jnhdaEjH+8Qna5pYqwv2WHJBtWMVb4HyRzmvChSS9PYoRwI2jGZiZlllRoZJw
OtT72630T1IP2wwAHUqGXG+HgP2S9YkS77+kbU3OBandF3D07BHc2t+EVl4a3+V7
fH35bRWnSA0C95QljvroklSkDmktk8IjuGBXiCHU8G/vKRF919FrpiYdsn9zOzJZ
TNzxurpygNRBGZbTqJzkfe8UhuBoWALRdv+4Lvvaq2b4a74oLIlRbiNFE4Cn29n7
ozLIPXfucSAz6szwjDc6v19K97CUyD6RH+Qy8kZR0TLVph9TNW1s1lCaTOQxBPti
nEZnBj+PwxQxneNLK2AdHRB3Thxzt0/W1PRHyEP8uKT+UrZ5NB0ooTAo9z/4itpV
NHNpCY8Lj3B7kXwUnHeo0tMSPriEm3/inyeHJW2nLOGfaZUiO/S9mSu1UDFyzHY8
/MtKc2YCC6ul+lh0zVimfdbvr6akaOyQMt4IJatfkXPf/rbCYHqgzDUUKfe1TQ7c
PhYIwcylFhTLHC7xGYBypyrCWDyCNMcvxcg0Smk2vJsilAjoSWeVR5/AQp3IbZRd
Kl3Gshm9gEIQNS/Ul5tMyL2nFakBXFViwMwv2Pfe8voWPeYBurNWHPj+uCRhi7AV
pnkMolCKGP8TEQqaEQZ5
=1lHb
-----END PGP SIGNATURE-----
Reply to: