Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#49098 - [shntool] shnsplit unable to split big files
Attached to Project:
Community Packages
Opened by Viktor (tmplt) - Tuesday, 26 April 2016, 18:27 GMT
Last edited by Jakob Gruber (schuay) - Saturday, 24 September 2016, 07:22 GMT
Opened by Viktor (tmplt) - Tuesday, 26 April 2016, 18:27 GMT
Last edited by Jakob Gruber (schuay) - Saturday, 24 September 2016, 07:22 GMT
|
Detailsshnsplit (v3.0.10) is unable to split a 3.1GB flac-file with an attached cue-file.
The command in question is the following: $ shnsplit -f cuefile.cue -o flac audiofile.flac shnsplit: warning: failed to read data from input file using format: [flac] shnsplit: + you may not have permission to read file: [Endless Forms Most Beautiful.flac] shnsplit: + arguments may be incorrect for decoder: [flac] shnsplit: + verify that the decoder is installed and in your PATH shnsplit: + this file may be unsupported, truncated or corrupt shnsplit: error: cannot continue due to error(s) shown above This bug is fixed in Debian: <http://metadata.ftp-master.debian.org/changelogs//main/s/shntool/shntool_3.0.10-1_changelog>. Can these patches be merged into the Arch build? Thanks in advance. |
This task depends upon
Closed by Jakob Gruber (schuay)
Saturday, 24 September 2016, 07:22 GMT
Reason for closing: No response
Saturday, 24 September 2016, 07:22 GMT
Reason for closing: No response
Comment by Jakob Gruber (schuay) -
Tuesday, 03 May 2016, 17:46 GMT
Thanks, please test 3.0.10-4.
Comment by Viktor (tmplt) -
Thursday, 05 May 2016, 14:49 GMT
3.0.10-4 does not fix this issue, it would seem; I get the same output.
Comment by Jakob Gruber (schuay) -
Thursday, 05 May 2016, 15:04 GMT
3.0.10-4 should include the patches from debian though. On the other hand, your error message is different than the one from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684600. Perhaps you're running into a different problem?