From: daerich <daerich@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] steam: fix typo in README.voidlinux
Date: Thu, 26 Aug 2021 13:21:50 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32684@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1661 bytes --]
There is a new pull request by daerich against master on the void-packages repository
https://github.com/daerich/void-packages steam_typo
https://github.com/void-linux/void-packages/pull/32684
steam: fix typo in README.voidlinux
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
"Changes" in #32662 introduced a typo. Fix it and rewrap.
A patch file from https://github.com/void-linux/void-packages/pull/32684.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-steam_typo-32684.patch --]
[-- Type: text/x-diff, Size: 2086 bytes --]
From ce1c8c2f6d89c5c108eb53368929d7c3af6f6725 Mon Sep 17 00:00:00 2001
From: DaErich <daerich@sourceforge.net>
Date: Thu, 26 Aug 2021 13:14:51 +0200
Subject: [PATCH] steam: fix typo in README.voidlinux
---
srcpkgs/steam/files/README.voidlinux | 10 +++++-----
srcpkgs/steam/template | 2 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/srcpkgs/steam/files/README.voidlinux b/srcpkgs/steam/files/README.voidlinux
index 9d18f3525970..99bd1e8e393f 100644
--- a/srcpkgs/steam/files/README.voidlinux
+++ b/srcpkgs/steam/files/README.voidlinux
@@ -32,11 +32,11 @@ If your audio is not working, try installing pulseaudio,
alsa-plugins-pulseaudio, and their "<package>-32bit" equivalents.
If you are using SteamPlay/Proton and the game crashes or hangs with error
-messages that include "eventfd: Too many open files", this means
-the number of open file descriptors per process is too low for proper Proton
-functionality. In this case, consult limits.conf(5) and set a higher nofile
-limit for your user. Formore information, see the upstream documentation in
-the README.esync file from https://github.com/ValveSoftware/wine.
+messages that include "eventfd: Too many open files", this means the number of
+open file descriptors per process is too low for proper Proton functionality.
+In this case, consult limits.conf(5) and set a higher nofile limit for your
+user. For more information, see the upstream documentation in the README.esync
+file from https://github.com/ValveSoftware/wine.
If you are encountering runtime errors, the Steam Ubuntu bootstrap tarball might
be using an incompatible libstdc++ library. You can verify this by running the
diff --git a/srcpkgs/steam/template b/srcpkgs/steam/template
index 5594b6a59793..2b88e0623166 100644
--- a/srcpkgs/steam/template
+++ b/srcpkgs/steam/template
@@ -1,7 +1,7 @@
# Template file for 'steam'
pkgname=steam
version=1.0.0.71
-revision=2
+revision=3
archs="i686 x86_64"
wrksrc=steam-launcher
depends="zenity xz curl dbus freetype gdk-pixbuf hicolor-icon-theme desktop-file-utils
next reply other threads:[~2021-08-26 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 11:21 daerich [this message]
2021-08-26 17:28 ` cinerea0
2021-08-26 23:07 ` [PR PATCH] [Updated] " daerich
2021-08-27 17:35 ` [PR PATCH] [Merged]: " ericonr
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32684@inbox.vuxu.org \
--to=daerich@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).