Bug 1261149

Summary: umph does not work
Product: [Fedora] Fedora Reporter: Till Maas <opensource>
Component: umphAssignee: Filipe Rosset <rosset.filipe>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: goeran, rosset.filipe
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 15:11:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Till Maas 2015-09-08 17:28:37 UTC
Description of problem:
Trying to use umph with the Fedora Flock 2015 playlist (and other playlists I randomly tried) reveals that it does not work (anymore).

Version-Release number of selected component (if applicable):
umph-0.2.5-5.fc21

How reproducible:
always

Steps to Reproduce:
1. umph PL0x39xti0_64fA6uRtcfoJPkHfZdeVTRC
2. umph https://www.youtube.com/playlist?list=PL0x39xti0_64fA6uRtcfoJPkHfZdeVTRC

Actual results:
given is experimental at /usr/bin/umph line 253.
when is experimental at /usr/bin/umph line 255.
when is experimental at /usr/bin/umph line 263.
given is experimental at /usr/bin/umph line 286.
when is experimental at /usr/bin/umph line 288.
when is experimental at /usr/bin/umph line 292.
Checking ... 
error: GData: NoLongerAvailableException: No longer available
 at /usr/bin/umph line 121.
	main::chk_error_resp(XML::DOM::Document=ARRAY(0x1a74218)) called at /usr/bin/umph line 209
	main::main() called at /usr/bin/umph line 38



Expected results:
Should show me URLs to all videos in playlist


Additional info:

Comment 1 Fedora End Of Life 2016-07-19 17:49:44 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.

Comment 2 Göran Uddeborg 2018-03-22 22:44:52 UTC
The problem remains in Fedora 22, umph-0.2.5-9.fc27.noarch.  If the program isn't working any more, perhaps it ought to be retired?

Comment 3 Ben Cotton 2018-11-27 16:31:02 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 4 Ben Cotton 2018-11-30 20:33:50 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.

Comment 5 Göran Uddeborg 2018-12-11 10:53:17 UTC
The program still doesn't seem to work in F29, umph-0.2.5-11.fc29.noarch.

mimmi$ umph PLxiRZKD6RS49jYklKIXTPQGaPSR4zVibR
given is experimental at /usr/bin/umph line 250.
when is experimental at /usr/bin/umph line 252.
when is experimental at /usr/bin/umph line 260.
given is experimental at /usr/bin/umph line 283.
when is experimental at /usr/bin/umph line 285.
when is experimental at /usr/bin/umph line 289.
Checking ... Couldn't parsefile [http://gdata.youtube.com/feeds/api/playlists/PLxiRZKD6RS49jYklKIXTPQGaPSR4zVibR?v=2&start-index=1&max-results=25&strict=true] with LWP: 
not well-formed (invalid token) at line 1, column 252, byte 252 at /usr/lib64/perl5/vendor_perl/XML/Parser.pm line 187.

Comment 6 Ben Cotton 2019-10-31 20:20:10 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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 7 Göran Uddeborg 2019-11-11 14:05:57 UTC
Repeating the test case with F31 (umph-0.2.5-13.fc31) I get an error very similar to the one in comment 5.  Only the line and column numbers differ slightly:

mimmi$ umph PLxiRZKD6RS49jYklKIXTPQGaPSR4zVibR
given is experimental at /usr/bin/umph line 250.
when is experimental at /usr/bin/umph line 252.
when is experimental at /usr/bin/umph line 260.
given is experimental at /usr/bin/umph line 283.
when is experimental at /usr/bin/umph line 285.
when is experimental at /usr/bin/umph line 289.
Checking ... Couldn't parsefile [http://gdata.youtube.com/feeds/api/playlists/PLxiRZKD6RS49jYklKIXTPQGaPSR4zVibR?v=2&start-index=1&max-results=25&strict=true] with LWP: 
not well-formed (invalid token) at line 2, column 11, byte 27 at /usr/lib64/perl5/vendor_perl/XML/Parser.pm line 187.

Comment 8 Filipe Rosset 2019-11-11 14:08:41 UTC
I'll take a look if we can fix this issue.
Upstream looks dead, if I cannot fix until End-November I'll retire this package from all Fedora releases.

Comment 9 Ben Cotton 2020-11-03 14:57:15 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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 10 Göran Uddeborg 2020-11-03 20:25:40 UTC
The problem remains in F33, but the package is not retired. Did you find something last year, or did more important things come in between?

Comment 11 Ben Cotton 2021-11-04 17:24:00 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 '33'.

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 33 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 12 Göran Uddeborg 2021-11-08 21:55:38 UTC
The problem remains in F35.

umph-0.2.5-17.fc35.noarch

Comment 13 Ben Cotton 2022-11-29 16:44:30 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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
'version' of '35'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 14 Ben Cotton 2022-12-13 15:11:36 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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