New package naming broke dbdeployer.
General
Escalation
General
Escalation
Description
Environment
None
Smart Checklist
Activity
Show:
Evgeniy Patlan February 24, 2020 at 7:17 AM
Hello !
Thanks for the report. The issue is fixed now and shouldn't appear in next release
Done
Created February 15, 2020 at 6:56 PM
Updated March 6, 2024 at 11:20 AM
Resolved February 24, 2020 at 7:18 AM
Hi,
the new package names (Percona-Server-8.0.18-9-Linux.x86_64.ssl102.deb.tar.gz) breaks dbdeployer:
$ p="https://www.percona.com/downloads/Percona-Server-8.0"
$ l="Linux.x86_64.ssl102.deb.tar.gz"
$ p2="Percona-Server-8.0.18-9"
$ wget $p/$p2/binary/tarball/${p2}-$l
[...]
$ dbdeployer unpack --prefix=ps_ ${p2}-${l}
validation for Percona-Server-8.0.18-9-Linux.x86_64.ssl102.deb.tar.gz failed: inner directory name different from tarball name
Expected: Percona-Server-8.0.18-9-Linux.x86_64.ssl102.deb - Found: Percona-Server-8.0.18-9-Linux.x86_64.ssl102
This could be considered a bug in dbdeployer, but it could also be argued that this is a package naming problem.
Related: https://github.com/datacharmer/dbdeployer/issues/103
Many thanks for looking into that,
JFG