-
Notifications
You must be signed in to change notification settings - Fork 243
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
y++ #952
Merged
Merged
y++ #952
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Feb 15, 2024
Closed
Instead of adding 1, we should add the value the we stored previously in the variable. Fixes: 45c6603 ("[svn-upgrade] Integrating new upstream version, shadow (19990709)") Closes: <shadow-maint#939> Link: <shadow-maint#942> Reported-by: Michael Vetter <jubalh@iodoru.org> Reported-by: Gus Kenion <https://github.com/kenion> Cc: Iker Pedrosa <ipedrosa@redhat.com> Cc: Serge Hallyn <serge@hallyn.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
v1b changes:
|
Closed
Thanks for taking care of that @alejandro-colomar ! |
BTW, in the test above:
This is funny, and nothing transcendental, but I entered |
c3f3509
to
d53bc20
Compare
Sorry, took me awhile ... but it looks correct, thanks. |
Hi Serge,
On Fri, Feb 16, 2024 at 05:58:49PM -0800, Serge Hallyn wrote:
Sorry, took me awhile ...
No problem! :)
but it looks correct, thanks.
Thanks!
Have a lovely night,
Alex
…--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
|
alejandro-colomar
added a commit
that referenced
this pull request
Feb 17, 2024
Instead of adding 1, we should add the value the we stored previously in the variable. Fixes: 45c6603 ("[svn-upgrade] Integrating new upstream version, shadow (19990709)") Closes: <#939> Link: <#942> Reported-by: Michael Vetter <jubalh@iodoru.org> Reported-by: Gus Kenion <https://github.com/kenion> Cc: Iker Pedrosa <ipedrosa@redhat.com> Cc: Serge Hallyn <serge@hallyn.com> Signed-off-by: Alejandro Colomar <alx@kernel.org> Cherry-picked-from: 4d139ca ("lib/getdate.y: get_date(): Fix calculation") Link: <#952> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this pull request
Feb 14, 2025
This reverts commit 3f5b4b5. The dates are stored as UTC, and are stored as a number of days since Epoch. We don't have enough precision to translate it into local time. Using local time has caused endless issues in users. This patch is not enough for fixing this issue completely, since printing a date without time-zone information means that the date is a local date, but what we're printing is a UTC date. A future patch should add time-zone information to the date. For now, let's revert this change that has caused so many issues. Fixes: 3f5b4b5 (2024-08-01; "lib/, src/: Use local time for human-readable dates") Link: <https://github.com/ansible/ansible/blob/devel/test/integration/targets/user/tasks/test_expires.yml#L2-L20> Link: <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095430> Link: <https://lists.iana.org/hyperkitty/list/tz@iana.org/message/ENE5IFV3GAH6WK22UJ6YU57D6TQINSP5/> Link: <shadow-maint#1202> Link: <shadow-maint#1057> Link: <shadow-maint#939> Link: <shadow-maint#1058> Link: <shadow-maint#1059 (comment)> Link: <shadow-maint#952> Link: <shadow-maint#942> Reported-by: Chris Hofstaedtler <zeha@debian.org> Reported-by: Gus Kenion <https://github.com/kenion> Reported-by: Alejandro Colomar <alx@kernel.org> Reported-by: Michael Vetter <jubalh@iodoru.org> Reported-by: Lee Garrett <lgarrett@rocketjump.eu> Cc: Paul Eggert <eggert@cs.ucla.edu> Cc: Tim Parenti <tim@timtimeonline.com> Cc: Iker Pedrosa <ipedrosa@redhat.com> Cc: "Serge E. Hallyn" <serge@hallyn.com> Cc: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this pull request
Feb 16, 2025
This reverts commit 3f5b4b5. The dates are stored as UTC, and are stored as a number of days since Epoch. We don't have enough precision to translate it into local time. Using local time has caused endless issues in users. This patch is not enough for fixing this issue completely, since printing a date without time-zone information means that the date is a local date, but what we're printing is a UTC date. A future patch should add time-zone information to the date. For now, let's revert this change that has caused so many issues. Fixes: 3f5b4b5 (2024-08-01; "lib/, src/: Use local time for human-readable dates") Link: <https://github.com/ansible/ansible/blob/devel/test/integration/targets/user/tasks/test_expires.yml#L2-L20> Link: <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095430> Link: <https://lists.iana.org/hyperkitty/list/tz@iana.org/message/ENE5IFV3GAH6WK22UJ6YU57D6TQINSP5/> Link: <shadow-maint#1202> Link: <shadow-maint#1057> Link: <shadow-maint#939> Link: <shadow-maint#1058> Link: <shadow-maint#1059 (comment)> Link: <shadow-maint#952> Link: <shadow-maint#942> Reported-by: Chris Hofstaedtler <zeha@debian.org> Reported-by: Gus Kenion <https://github.com/kenion> Reported-by: Alejandro Colomar <alx@kernel.org> Reported-by: Michael Vetter <jubalh@iodoru.org> Reported-by: Lee Garrett <lgarrett@rocketjump.eu> Cc: Paul Eggert <eggert@cs.ucla.edu> Cc: Tim Parenti <tim@timtimeonline.com> Cc: Iker Pedrosa <ipedrosa@redhat.com> Cc: "Serge E. Hallyn" <serge@hallyn.com> Cc: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
to alejandro-colomar/shadow
that referenced
this pull request
Feb 25, 2025
This reverts commit 3f5b4b5. The dates are stored as UTC, and are stored as a number of days since Epoch. We don't have enough precision to translate it into local time. Using local time has caused endless issues in users. This patch is not enough for fixing this issue completely, since printing a date without time-zone information means that the date is a local date, but what we're printing is a UTC date. A future patch should add time-zone information to the date. For now, let's revert this change that has caused so many issues. Fixes: 3f5b4b5 (2024-08-01; "lib/, src/: Use local time for human-readable dates") Link: <https://github.com/ansible/ansible/blob/devel/test/integration/targets/user/tasks/test_expires.yml#L2-L20> Link: <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095430> Link: <https://lists.iana.org/hyperkitty/list/tz@iana.org/message/ENE5IFV3GAH6WK22UJ6YU57D6TQINSP5/> Link: <shadow-maint#1202> Link: <shadow-maint#1057> Link: <shadow-maint#939> Link: <shadow-maint#1058> Link: <shadow-maint#1059 (comment)> Link: <shadow-maint#952> Link: <shadow-maint#942> Reported-by: Chris Hofstaedtler <zeha@debian.org> Reported-by: Gus Kenion <https://github.com/kenion> Reported-by: Alejandro Colomar <alx@kernel.org> Reported-by: Michael Vetter <jubalh@iodoru.org> Reported-by: Lee Garrett <lgarrett@rocketjump.eu> Cc: Paul Eggert <eggert@cs.ucla.edu> Cc: Tim Parenti <tim@timtimeonline.com> Cc: "Serge E. Hallyn" <serge@hallyn.com> Cc: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca> Reviewed-by: Iker Pedrosa <ipedrosa@redhat.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
alejandro-colomar
added a commit
that referenced
this pull request
Feb 25, 2025
This reverts commit 3f5b4b5. The dates are stored as UTC, and are stored as a number of days since Epoch. We don't have enough precision to translate it into local time. Using local time has caused endless issues in users. This patch is not enough for fixing this issue completely, since printing a date without time-zone information means that the date is a local date, but what we're printing is a UTC date. A future patch should add time-zone information to the date. For now, let's revert this change that has caused so many issues. Fixes: 3f5b4b5 (2024-08-01; "lib/, src/: Use local time for human-readable dates") Link: <https://github.com/ansible/ansible/blob/devel/test/integration/targets/user/tasks/test_expires.yml#L2-L20> Link: <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1095430> Link: <https://lists.iana.org/hyperkitty/list/tz@iana.org/message/ENE5IFV3GAH6WK22UJ6YU57D6TQINSP5/> Link: <#1202> Link: <#1057> Link: <#939> Link: <#1058> Link: <#1059 (comment)> Link: <#952> Link: <#942> Reported-by: Chris Hofstaedtler <zeha@debian.org> Reported-by: Gus Kenion <https://github.com/kenion> Reported-by: Alejandro Colomar <alx@kernel.org> Reported-by: Michael Vetter <jubalh@iodoru.org> Reported-by: Lee Garrett <lgarrett@rocketjump.eu> Cc: Paul Eggert <eggert@cs.ucla.edu> Cc: Tim Parenti <tim@timtimeonline.com> Cc: "Serge E. Hallyn" <serge@hallyn.com> Cc: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca> Reviewed-by: Iker Pedrosa <ipedrosa@redhat.com> Signed-off-by: Alejandro Colomar <alx@kernel.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of adding 1, we should add the value the we stored previously in the variable.
Fixes: 45c6603 ("[svn-upgrade] Integrating new upstream version, shadow (19990709)")
Closes: #939
Link: #942
Reported-by: @jubalh
Reported-by: @kenion
Cc: @ikerexxe
And here goes my first patch to a YACC file. Please be very skeptic. Disclaimer: this comes with no warrany, neither expressed nor implied. :)
Here goes some test:
Does it break anything else? Good question. I don't have an answer. :)