-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test issue #1
Comments
Another test to see if email is working. |
nickva
pushed a commit
that referenced
this issue
Apr 27, 2022
feat: patch rpmspec to prompt for cookie value
rnewson
added a commit
that referenced
this issue
Jan 22, 2023
A cookie value with a '/' in it caused a sed error during postinst; ``` sed: -e expression #1, char 53: unknown option to `s' ``` We use a control character (RS - record separator) instead of / to reduce the chances of a collision with a valid cookie string. I applied the same change to nodename even though a / in node name would be an error, for consistency.
rnewson
added a commit
that referenced
this issue
Jan 22, 2023
A cookie value with a '/' in it caused a sed error during postinst; ``` sed: -e expression #1, char 53: unknown option to `s' ``` We use a control character (RS - record separator) instead of / to reduce the chances of a collision with a valid cookie string. I applied the same change to nodename even though a / in node name would be an error, for consistency.
rnewson
added a commit
that referenced
this issue
Jan 23, 2023
A cookie value with a '/' in it caused a sed error during postinst; ``` sed: -e expression #1, char 53: unknown option to `s' ``` We use a control character (RS - record separator) instead of / to reduce the chances of a collision with a valid cookie string. I applied the same change to nodename even though a / in node name would be an error, for consistency.
rnewson
added a commit
that referenced
this issue
Jan 23, 2023
A cookie value with a '/' in it caused a sed error during postinst; ``` sed: -e expression #1, char 53: unknown option to `s' ``` We use a control character (RS - record separator) instead of / to reduce the chances of a collision with a valid cookie string. I applied the same change to nodename even though a / in node name would be an error, for consistency.
rnewson
added a commit
that referenced
this issue
Jan 24, 2023
A cookie value with a '/' in it caused a sed error during postinst; ``` sed: -e expression #1, char 53: unknown option to `s' ``` We use a control character (RS - record separator) instead of / to reduce the chances of a collision with a valid cookie string. I applied the same change to nodename even though a / in node name would be an error, for consistency.
rnewson
added a commit
that referenced
this issue
Jan 24, 2023
A cookie value with a '/' in it caused a sed error during postinst; ``` sed: -e expression #1, char 53: unknown option to `s' ``` We use a control character (RS - record separator) instead of / to reduce the chances of a collision with a valid cookie string. I applied the same change to nodename even though a / in node name would be an error, for consistency.
rnewson
added a commit
that referenced
this issue
Jan 24, 2023
A cookie value with a '/' in it caused a sed error during postinst; ``` sed: -e expression #1, char 53: unknown option to `s' ``` We use a control character (RS - record separator) instead of / to reduce the chances of a collision with a valid cookie string. I applied the same change to nodename even though a / in node name would be an error, for consistency.
rnewson
added a commit
that referenced
this issue
Jan 24, 2023
A cookie value with a '/' in it caused a sed error during postinst; ``` sed: -e expression #1, char 53: unknown option to `s' ``` We use a control character (RS - record separator) instead of / to reduce the chances of a collision with a valid cookie string. I applied the same change to nodename even though a / in node name would be an error, for consistency.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Testing GH-ASF integration!
The text was updated successfully, but these errors were encountered: