Dear Maintainer, when using flactag on flac files, no matter if they are created with ripflac or other means, or even if they were already tagged using flactag, the retrieved disk information is neither shown nor processed. There are no releases to select from, the normal window is displayed with no information on the upper side and only skeleton information on the disk/song structure on the lower side. As an "Exception: Fetch error: 403 Forbidden" is shown when running flactag I used wireshark to get information on the network traffic and that looked absolutely fine on the MusicBrainz part. There are two connections on which information was retrieved. I checked those URL in the browser for closer inspection and they were returning information as well. The 403 is caused when trying to get the disk cover. I am neither providing information on the disk images used to try tagging nor on the network traffic as the error should be replicable easily with any suitable flac file. My assumption is that while the information can still be accessed successfully the internal representation format must have changed so that it can no longer be interpreted by flactag. Best, sok
This is due to Amazon rejecting the request due to the user agent presented by flactag. It was fixed in the following upstream commit (in a version yet to be released). https://github.com/adhawkins/flactag/commit/570a80185bf6f02277585bc60091ddae06df9058 Any suggestions as to a better way to get around this are appreciated. Andy
Dear Andy, thank you very much (and once again) for flactag and also for your swift response. Sorry for not checking the GitHub repository right away. It would still be an exaggeration if I said that I very seldomly report bugs and so I assumed that any error fixed elsewhere would make it upstream into Debian relatively soon, especially when it affects the overall functionality of the package so much. About your workaround that is exactly the same way I use with much simplier BASH and Python scripts when running into user agent issues myself. Getting your user agent registered would at best only be a waste of time. I just put my even more seldomly used knowledge on building Debian packages to the test, reactivated the deb-src-entries, downloaded the Debian flactag source, "integrated" the patch you mentioned into the downloaded source code and have a working installation once more. Hopefully the patch will be integrated soon and become an additional reason to look forward on trixie. Again: thank you very much for flactag. I really appreciate it a lot! Best, sok