I've noticed in the last week or so some of my podcasts are not being downloaded. I see no errors in the logs. I've checked the missing feeds with Rhythmbox and confirmed the feed is still valid.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Either:
1. You have the source code, debug it yourself and submit a patch.
OR
2. Give me some more information (like the feed URL) so that I can debug it and potentially come up with a fix.
So which would you like to do?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
FYI, I run podget on 3 PC's. One is running Xubuntu 14.04 with podget installed from their repo's. Today on that PC there were downloads. On my Manjaro PC there were none. I'm not sure what version of podget is running on the Buntu PC but Manjaro is using 0.8.1-1.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Doing some troubleshooting it seems podget stops when a feed url receives a 403 error. I found the culprit in my serverlist but this was not reported in the logs.
OK, I think I've found the issue. The problem was indirectly caused by changed made to enable both RSS and ATOM feeds which left 'errextit' enabled at the wrong time that caused the script to exit when wget received the 403 error. I've got a test version up in the dev branch on Github that appears to be working but it will take some more testing before I move it to the 'master' branch and release it.
I have a busy week coming up, and some time available today & tomorrow. So my goal is to test the 'dev' branch through a variety of feeds and then migrate those changes to the 'master' branch. When I do that, it will be ready for release. Github will obviously be ready and tagged with a new version. I will then package for it to be available on Sourceforge.
From that point, I can't make a good estimation of when it will make it into the various distributions. Now there are a few (and I believe Arch is one) that monitor the Github for when a new version is tagged and then shortly after that push out a new version to their repos. Unfortunately, that is hard to estimate because that work is done when they have time. It might be a bad week for them. We never know. I would hope for less than a week after I do a release but that's just a guess.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, testing went a lot faster this morning than I anticipated. I was approximately 50% done when I wrote the last message and almost flew through the rest getting amazing download speeds.
So I pushed out a new version with these fixes. Now the count starts for how long it takes the distributions to add it to their repos.
Now that is assuming I didn't miss anything during my testing...... any bets?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've noticed in the last week or so some of my podcasts are not being downloaded. I see no errors in the logs. I've checked the missing feeds with Rhythmbox and confirmed the feed is still valid.
OK, we have to make a choice here.
Either:
1. You have the source code, debug it yourself and submit a patch.
OR
2. Give me some more information (like the feed URL) so that I can debug it and potentially come up with a fix.
So which would you like to do?
Try these:
TIA for your help
FYI, I run podget on 3 PC's. One is running Xubuntu 14.04 with podget installed from their repo's. Today on that PC there were downloads. On my Manjaro PC there were none. I'm not sure what version of podget is running on the Buntu PC but Manjaro is using 0.8.1-1.
Doing some troubleshooting it seems podget stops when a feed url receives a 403 error. I found the culprit in my serverlist but this was not reported in the logs.
The offending feed: http://tipsfromtheserverroom.com/?feed=podcast
Last edit: Kevin Wisher 2016-07-10
Sorry for the delay. I had a busy weekend. With luck I will have some time this week and we will find the issue!
Good work narrowing down the offending feed!
OK, I think I've found the issue. The problem was indirectly caused by changed made to enable both RSS and ATOM feeds which left 'errextit' enabled at the wrong time that caused the script to exit when wget received the 403 error. I've got a test version up in the dev branch on Github that appears to be working but it will take some more testing before I move it to the 'master' branch and release it.
If you'd care to test it, feel free to download it and give it a go!
https://github.com/dvehrs/podget/tree/dev
Thanks reporting the issue!
Last edit: Dave Vehrs 2016-07-11
Happy to help with improving my most used application :)
How long do point releases take to make it into the Arch repo's?
I have a busy week coming up, and some time available today & tomorrow. So my goal is to test the 'dev' branch through a variety of feeds and then migrate those changes to the 'master' branch. When I do that, it will be ready for release. Github will obviously be ready and tagged with a new version. I will then package for it to be available on Sourceforge.
From that point, I can't make a good estimation of when it will make it into the various distributions. Now there are a few (and I believe Arch is one) that monitor the Github for when a new version is tagged and then shortly after that push out a new version to their repos. Unfortunately, that is hard to estimate because that work is done when they have time. It might be a bad week for them. We never know. I would hope for less than a week after I do a release but that's just a guess.
OK, testing went a lot faster this morning than I anticipated. I was approximately 50% done when I wrote the last message and almost flew through the rest getting amazing download speeds.
So I pushed out a new version with these fixes. Now the count starts for how long it takes the distributions to add it to their repos.
Now that is assuming I didn't miss anything during my testing...... any bets?
New version showed up today in the AUR.
Thanks for fixing this so fast :)