19:25 bapt 

Simplify plist

 

10:58 bapt 

Cleanup plist

 

16:43 antoine 

Fix packaging

Reported by:	pkg-fallout
Note: if this directory was reported as a leftover by tinderbox, this would be a
bug in tinderbox (home directory of a user created by the port)

 

10:34 wg 

devel/py-mercurialserver: support staging and use auto plist

 

21:31 pawel 

Update to version 1.2.0

PR:             ports/160844
Submitted by:   Aldis Berjoza <graudeejs@gmail.com> (maintainer)
Approved by:    miwi, wen (mentors implicit)

02:07 pgollucci 

mercurial-server gives your developers remote read/write access to centralized
Mercurial repositories using SSH public key authentication; it provides
convenient and fine-grained key management and access control.

All of the repositories controlled by mercurial-server are owned by a single
user (the "hg" user in what follows), but many remote users can act on them,
and different users can have different permissions. We don't use file
permissions to achieve that - instead, developers log in as the "hg" user
when they connect to the repository host using SSH, using SSH URLs of the
form "ssh://hg@repository-host/repository-name". A restricted shell prevents
them from using this access for unauthorized purposes. Developers
are authenticated only using SSH keys; no other form of authentication is
supported.

To give a user access to the repository, place their key in an

(Only the first 15 lines of the commit message are shown above )