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

Bug#862498: jessie-pu: package gitolite3/3.6.1-2+deb8u2



Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian.org@packages.debian.org
Usertags: pu

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

I'd like to close #834153 in stable. The bug has an easy workaround,
but it still admittedly pretty annoying.

There isn't that much to test here, but I've installed the resulting
package on jessie, and did a few basic operations.  Of course I
already had openssh-client on the host in question.

diff -u gitolite3-3.6.1/debian/changelog gitolite3-3.6.1/debian/changelog
- --- gitolite3-3.6.1/debian/changelog
+++ gitolite3-3.6.1/debian/changelog
@@ -1,3 +1,10 @@
+gitolite3 (3.6.1-2+deb8u2) stable; urgency=medium
+
+  * Bug fix: "gitolite3 should depend on openssh-client", thanks to Keller
+    Fuchs (Closes: #834153).
+
+ -- David Bremner <bremner@debian.org>  Sat, 13 May 2017 12:38:44 -0300
+
 gitolite3 (3.6.1-2+deb8u1) stable; urgency=medium
 
   * Bug fix: "Git-annex-shell not working", thanks to risca (Closes:
diff -u gitolite3-3.6.1/debian/control gitolite3-3.6.1/debian/control
- --- gitolite3-3.6.1/debian/control
+++ gitolite3-3.6.1/debian/control
@@ -13,7 +13,7 @@
 Package: gitolite3
 Architecture: all
 Depends: ${misc:Depends}, git (>= 1:1.7.0.4) | git-core (>= 1:1.6.2), perl (>= 5.6.0-16),
- - ssh-server, debconf (>= 0.5) | debconf-2.0, adduser
+ ssh-server, debconf (>= 0.5) | debconf-2.0, adduser, openssh-client
 Suggests: git-daemon-run, gitweb
 Description: SSH-based gatekeeper for git repositories (version 3)
  Gitolite is an SSH-based gatekeeper providing access control for a server that


- -- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64
 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlkXM28ACgkQ8gKXHaSn
nixJNAv+K3/xnzDa+8u/pJqwRlqpwcmbtytfmABpCiKMLefChRKfPu0wRTj+ljuL
Y/146rZ6JZ/PfOj8jY+lJa8xagh+XdxOsBssrm1LW8l7+5F3ksT1c53pTPgiqimS
NA2KSCeT72fwScCmUfYnc//apWfiuzsg03UbhveN/iU7GXUcU1BUbK7U3sBOjUOA
VvjmgG00NdHtd5d9AbZPrP4x8IUG+0umnQMgXAmAQ5ZvQjOWB6FvHT9oVi4HPwD1
Tz6zCzHjkOVdNgZSm1RPBaTLDa626h/uYihqgo6xtNH3lTPOepKyL5Z8YULCwIKM
Hkmq8jootM6SdheKg0hfGsTdLjRVghssM3sIBRs72X+XMkLIlfBHB9DZD1fiqPHb
YweHcgbm9POUu/v2EzgcoNKaB9zafwcB5wt8dfA09WhFwrG8pL4+wH2oBV7ZIveq
xmph7ASdMnJFbLg6paiWyDWVPDgDhAQ6s3syYA9Jt0QZc4tGXSz141UkQFBZ0I9y
Pv2JJmWs
=En6i
-----END PGP SIGNATURE-----


Reply to: