Bug 10404 - fetchyahoo-2.14.9 no longer works, should be obsolete
Summary: fetchyahoo-2.14.9 no longer works, should be obsolete
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: MGA3TOO'
Keywords: Junior_job
Depends on:
Blocks:
 
Reported: 2013-06-02 23:32 CEST by Bit Twister
Modified: 2013-09-26 15:11 CEST (History)
3 users (show)

See Also:
Source RPM: fetchyahoo-2.14.9-1.mga3.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2013-06-02 23:32:05 CEST 
Description of problem:

Yahoo has changed their page, again, and fetchyahoo-2.14.9 no longer works

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. fetchyahoo --configfile=~/.fetchyahoorc > fetchyahoo.log 2>&1
2. cat fetchyahoo.log

Workaround solution:
 install FetchYahoo Version 2.14.10
 from    Homepage: http://fetchyahoo.sourceforge.net


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-06-08 16:54:57 CEST

Keywords: (none) => Triaged
CC: (none) => cazzaniga.sandro

Comment 1 Bit Twister 2013-07-18 22:08:44 CEST 
See http://fetchyahoo.twizzler.org/

fetchyahoo is now obsolete and no longer supported.
Feel free to close this bug as soon as the fetchyahoo rpm is removed.
Manuel Hiebel 2013-07-18 22:51:00 CEST

Keywords: Triaged => Junior_job
Version: 3 => Cauldron
Summary: 3: fetchyahoo-2.14.9 no longer works => fetchyahoo-2.14.9 no longer works, should be obsolete
Whiteboard: (none) => MGA3TOO

Jeff Robins 2013-09-21 06:00:09 CEST

CC: (none) => jeffrobinsSAE
Whiteboard: MGA3TOO => MGA3TOO'

Comment 2 Rémi Verschelde 2013-09-26 15:11:38 CEST 
Done: http://svnweb.mageia.org/packages/cauldron/fetchmail/current/SPECS/fetchmail.spec?r1=449543&r2=486687

Status: NEW => RESOLVED
CC: (none) => remi
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.