Bug 1538829 - monitor-parse-edid fails to run with perl errors on F27
Summary: monitor-parse-edid fails to run with perl errors on F27
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: monitor-edid
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Till Maas
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-25 23:06 UTC by Jason Tibbitts
Modified: 2019-05-28 21:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 21:56:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
proposed patch (409 bytes, patch)
2018-01-31 14:35 UTC, Björn Augustsson
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Mageia 22293 0 None None None 2018-02-11 12:05:05 UTC

Description Jason Tibbitts 2018-01-25 23:06:20 UTC
I needed to see what monitors were attached to some machines but didn't feel like walking to all of them, so I installed monitor-edid.  Unfortunately it failed to run:

Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/.*? = { <-- HERE / at /usr/bin/monitor-parse-edid line 735.

I guess that became illegal in some more recent Perl version.  The fix is pretty trivial; backwhack two curly braces on line 735.  At least that gets it going where I needed it but I didn't check all of the code for other places where braces need to be escaped.

Comment 1 Björn Augustsson 2018-01-31 14:35:38 UTC
Created attachment 1389005 [details]
proposed patch

Comment 2 Björn Augustsson 2018-01-31 14:36:34 UTC
I just ran into this as well. Only the first curly needs a backslash though. Attached a proposed patch.

Comment 3 Till Maas 2018-02-08 09:41:29 UTC
Thank you for the report and the patch. The package does not build currently:
https://koji.fedoraproject.org/koji/taskinfo?taskID=24832904

Would you be interested in taking it over?

Comment 4 Till Maas 2018-02-08 10:12:23 UTC
FWIW: There seems to be a newer version in Mandriva but I do not know where they store the source tarball:
https://github.com/OpenMandrivaAssociation/monitor-edid

Comment 5 Till Maas 2018-02-11 12:05:06 UTC
I reported this upstream with the patch.

Comment 6 Denis Leroy 2018-07-24 13:55:40 UTC
Till, I can take over the package if you don't have the bandwidth.

Comment 7 Ben Cotton 2019-05-02 21:15:57 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2019-05-28 21:56:52 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.