From: m0bcy <m0bcy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: consolelocker-1.1.0
Date: Mon, 04 Dec 2023 05:52:55 +0100 [thread overview]
Message-ID: <20231204045255.xVntNeoQiwFOOGbgY2Drnxsfp85AhcIZr3Dur0vMQU4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47544@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 678 bytes --]
There is an updated pull request by m0bcy against master on the void-packages repository
https://github.com/m0bcy/void-packages consolelocker-1.1.0_1
https://github.com/void-linux/void-packages/pull/47544
New package: consolelocker-1.1.0
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
A patch file from https://github.com/void-linux/void-packages/pull/47544.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-consolelocker-1.1.0_1-47544.patch --]
[-- Type: text/x-diff, Size: 3757 bytes --]
From 73d14304ca4cc706812ab1cc4523bbf9659d2fe9 Mon Sep 17 00:00:00 2001
From: Nikita Ermakov <sh1r4s3@mail.si-head.nl>
Date: Sat, 2 Dec 2023 23:12:43 -0600
Subject: [PATCH] New package: consolelocker-1.1.0
---
srcpkgs/consolelocker/files/consolelocker.8 | 47 +++++++++++++++++++
.../consolelocker/files/consolelockerd/run | 3 ++
srcpkgs/consolelocker/template | 27 +++++++++++
3 files changed, 77 insertions(+)
create mode 100644 srcpkgs/consolelocker/files/consolelocker.8
create mode 100755 srcpkgs/consolelocker/files/consolelockerd/run
create mode 100644 srcpkgs/consolelocker/template
diff --git a/srcpkgs/consolelocker/files/consolelocker.8 b/srcpkgs/consolelocker/files/consolelocker.8
new file mode 100644
index 0000000000000..e16aa6a5c479f
--- /dev/null
+++ b/srcpkgs/consolelocker/files/consolelocker.8
@@ -0,0 +1,47 @@
+.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.49.2.
+.TH \FBCONSOLELOCKER\FR "8" "August 2023" "consolelocker version 1.0.0" "System Administration Utilities"
+.SH NAME
+\fBconsolelocker\fR \- virtual console lock daemon
+.SH SYNOPSIS
+.B consolelocker
+[\fI\,OPTIONS\/\fR]
+.SH DESCRIPTION
+This is a program to lock sessions on the Linux console
+and virtual consoles. After startup it open FIFO to read
+events from console user.
+This program is simple wrapper for vlock(1).
+.SH OPTIONS
+.TP
+\fB\-g\fR, \fB\-\-group\fR=\fI\,NAME\/\fR
+make socket group writable
+.TP
+\fB\-p\fR, \fB\-\-pidfile\fR=\fI\,FILE\/\fR
+pidfile location;
+.TP
+\fB\-l\fR, \fB\-\-loglevel\fR=\fI\,LVL\/\fR
+set logging level;
+.TP
+\fB\-f\fR, \fB\-\-foreground\fR
+stay in the foreground;
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+print program version and exit.
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+output a brief help message.
+.SH FILES
+.TP
+.I /var/run/consolelocker
+.TP
+\fI/var/run/consolelocker.pid
+.SH AUTHOR
+Written by Alexey Gladkov <legion@altlinux.org>
+.SH COPYRIGHT
+Copyright \(co 2006\-2018 Alexey Gladkov <legion@altlinux.org>
+.PP
+.br
+This is free software; see the source for copying conditions.
+There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
+.SH "SEE ALSO"
+.BR vlock (1),
+.BR pam_console (8).
diff --git a/srcpkgs/consolelocker/files/consolelockerd/run b/srcpkgs/consolelocker/files/consolelockerd/run
new file mode 100755
index 0000000000000..aed511823193b
--- /dev/null
+++ b/srcpkgs/consolelocker/files/consolelockerd/run
@@ -0,0 +1,3 @@
+#!/bin/sh
+exec 2>&1
+exec consolelocker -g wheel -f
diff --git a/srcpkgs/consolelocker/template b/srcpkgs/consolelocker/template
new file mode 100644
index 0000000000000..23dac5c13653b
--- /dev/null
+++ b/srcpkgs/consolelocker/template
@@ -0,0 +1,27 @@
+# Template file for 'consolelocker'
+pkgname=consolelocker
+version=1.1.0
+revision=1
+build_style=gnu-makefile
+# Disable manpage generation for now as the program uses help2man(1) to
+# generate a man page. help2man(1) executes binary to get the help message.
+# This causes issues with cross compiled binaries. It could be solved by using
+# binfmt but let's bundle the manpage.
+make_build_args="MAN8PAGES="
+depends=kbd
+short_desc="Lock sessions on the Linux console and virtual consoles"
+maintainer="Nikita Ermakov <sh1r4s3@mail.si-head.nl>"
+license="GPL-2.0-or-later"
+homepage="https://github.com/legionus/consolelocker"
+distfiles="https://github.com/legionus/consolelocker/archive/refs/tags/${version}-alt1.tar.gz"
+checksum="a26ce14bcecbe909743766cbc040afc673534300b2c21dc86c936fad9026f94d"
+
+do_install() {
+ vbin consolelock
+ vbin consolelocker
+ # Helper program and script
+ vmkdir usr/libexec/consolelocker 755
+ vinstall vlocka 700 usr/libexec/consolelocker/
+ vman "${FILESDIR}/consolelocker.8"
+ vsv consolelockerd
+}
next prev parent reply other threads:[~2023-12-04 4:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 5:16 [PR PATCH] " m0bcy
2023-12-03 5:24 ` [PR PATCH] [Updated] " m0bcy
2023-12-03 5:26 ` m0bcy
2023-12-03 5:36 ` m0bcy
2023-12-04 4:52 ` m0bcy [this message]
2023-12-11 2:58 ` m0bcy
2023-12-11 5:14 ` m0bcy
2023-12-12 15:34 ` m0bcy
2024-03-12 1:44 ` github-actions
2024-03-12 3:31 ` sh1r4s3
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231204045255.xVntNeoQiwFOOGbgY2Drnxsfp85AhcIZr3Dur0vMQU4@z \
--to=m0bcy@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).