Package: flactag
Version: 2.0.4-6+b2
Severity: important

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


-- System Information:
Debian Release: 12.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages flactag depends on:
ii libc6 2.36-9+deb12u4
ii libdiscid0 0.6.2-3
ii libflac++10 1.4.2+ds-2
pn libflac12t64 <none>
ii libgcc-s1 12.2.0-14
ii libjpeg62-turbo 1:2.1.5-2
ii libmusicbrainz5cc2v5 5.1.0+git20150707-10
ii libslang2 2.3.3-3
ii libstdc++6 12.2.0-14
ii libunac1 1.8.0-10

Versions of packages flactag recommends:
ii cdparanoia 3.10.2+debian-14
ii cdrdao 1:1.2.4-3
ii cuetools 1.4.1-0.2
ii flac 1.4.2+ds-2

flactag suggests no packages.

-- debconf-show failed

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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


On 13/04/2024 10:53 am, sok wrote:

Package: flactag
Version: 2.0.4-6+b2
Severity: important

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

-- System Information:
Debian Release: 12.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages flactag depends on:
ii libc6 2.36-9+deb12u4
ii libdiscid0 0.6.2-3
ii libflac++10 1.4.2+ds-2
pn libflac12t64 <none>
ii libgcc-s1 12.2.0-14
ii libjpeg62-turbo 1:2.1.5-2
ii libmusicbrainz5cc2v5 5.1.0+git20150707-10
ii libslang2 2.3.3-3
ii libstdc++6 12.2.0-14
ii libunac1 1.8.0-10

Versions of packages flactag recommends:
ii cdparanoia 3.10.2+debian-14
ii cdrdao 1:1.2.4-3
ii cuetools 1.4.1-0.2
ii flac 1.4.2+ds-2

flactag suggests no packages.

-- debconf-show failed

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format.
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
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Dear Andy,<br>
<br>
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, <span
_d-id="5696" class="--l --r sentence_highlight">especially when it
affects the overall functionality of the package so much.</span><br>
<br>
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.<br>
<br>
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.<br>
<br>
Again: thank you very much for flactag. I really appreciate it a
lot!<br>
<br>
<br>
Best,<br>
sok<br>
</body>
</html>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)