Summary: | app-text/master-pdf-editor-5.1.00 fails to download with ERROR 404: Not Found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrei Slavoiu <ansla80> |
Component: | Current packages | Assignee: | João Santos <joaompssantos> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | grozin, jstein, proxy-maint, samurai.no.dojo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=657650 https://bugs.gentoo.org/show_bug.cgi?id=664742 https://bugs.gentoo.org/show_bug.cgi?id=691002 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andrei Slavoiu
2018-07-28 15:41:17 UTC
confirmed with $ GENTOO_MIRRORS="" ebuild master-pdf-editor-5.0.15.ebuild fetch Thanks for the feedback. Just added a new pull request to fix this. Due to some mistakes on my part the previous couldn't be merged. Hopefully everything will be faster now. 5.1.0 is affected too - today. (In reply to Toralf Förster from comment #3) > 5.1.0 is affected too - today. Seems to be working, tested on different networks. Version 5.1.00 seems to be no longer available. It looks like it has been replaced by 5.1.30 (https://code-industry.net/public/master-pdf-editor-5.1.30_qt5.amd64.tar.gz) Error message: >>> Downloading 'http://code-industry.net/public/master-pdf-editor-5.1.00_qt5.amd64.tar.gz' --2018-08-22 22:27:35-- http://code-industry.net/public/master-pdf-editor-5.1.00_qt5.amd64.tar.gz Resolving code-industry.net... 136.243.89.42 Connecting to code-industry.net|136.243.89.42|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://code-industry.net/public/master-pdf-editor-5.1.00_qt5.amd64.tar.gz [following] --2018-08-22 22:27:35-- https://code-industry.net/public/master-pdf-editor-5.1.00_qt5.amd64.tar.gz Connecting to code-industry.net|136.243.89.42|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-08-22 22:27:35 ERROR 404: Not Found. (In reply to Fred Kastl from comment #5) > Version 5.1.00 seems to be no longer available. It looks like it has been > replaced by 5.1.30 > (https://code-industry.net/public/master-pdf-editor-5.1.30_qt5.amd64.tar.gz) > > Error message: > > >>> Downloading 'http://code-industry.net/public/master-pdf-editor-5.1.00_qt5.amd64.tar.gz' > --2018-08-22 22:27:35-- > http://code-industry.net/public/master-pdf-editor-5.1.00_qt5.amd64.tar.gz > Resolving code-industry.net... 136.243.89.42 Connecting to > code-industry.net|136.243.89.42|:80... connected. HTTP request sent, > awaiting response... 301 Moved Permanently Location: > https://code-industry.net/public/master-pdf-editor-5.1.00_qt5.amd64.tar.gz > [following] --2018-08-22 22:27:35-- > https://code-industry.net/public/master-pdf-editor-5.1.00_qt5.amd64.tar.gz > Connecting to code-industry.net|136.243.89.42|:443... connected. HTTP > request sent, awaiting response... 404 Not Found 2018-08-22 22:27:35 ERROR > 404: Not Found. Thanks for your feedback. It seems that they are quickly deleting previous versions as new ones are becoming available. Already made a pull request to handle the situation. I will try to be quicker to fix these kind of situations. Was this bug really fixed? I can not see any change since 2018-08-08. Please do not close tickets, if the bug is not yet fixed in the tree. (In reply to Jonas Stein from comment #7) > Was this bug really fixed? I can not see any change since 2018-08-08. > Please do not close tickets, if the bug is not yet fixed in the tree. You are right I shouldn't have closed it so soon, but I expected it to be quickly resolved. However, I have been waiting for approval for the past few weeks. Renaming master-pdf-editor-5.1.00.ebuild -> master-pdf-editor-5.1.30.ebuild works (In reply to Andrey Grozin from comment #9) > Renaming master-pdf-editor-5.1.00.ebuild -> master-pdf-editor-5.1.30.ebuild > works Yes in the mean time you can use that (you could also try version 5.1.36), I am waiting for my pull request to be approved. *** Bug 664742 has been marked as a duplicate of this bug. *** any news? (In reply to Jonas Stein from comment #12) > any news? I have marked the bug as resolved, it has been for a while now but I forgot to mark it as such. Thanks. |