[Slackbuilds-users] deb2tgz deletes user's files!

dchmelik at gmail.com dchmelik at gmail.com
Wed Jan 8 04:49:00 UTC 2025


On 1/7/25 8:05 PM, B. Watson wrote:
> On Tue, 7 Jan 2025, dchmelik at gmail.com wrote:
>> http://download.gigabyte.com/FileList/Utility/AI_TOP_Utility_ver_2_0_1_release.zip?v=3dcfb2d63a787c71cc8e34dea4db58c0 
>>
> [...]
> ...I tried running deb2tgz on it the same way you did, but got different
> results (also failure):
>
> # deb2tgz AI_TOP_Utility_ver_2_0_1/gigabyte-ai-top-utility-2.0.1.deb 
> ERROR: ar failed. (maybe 
> AI_TOP_Utility_ver_2_0_1/gigabyte-ai-top-utility-2.0.1.deb is not an 
> DEB?)
I see.
> However, if you cd into the directory and run it with just the filename:
>
> # cd AI_TOP_Utility_ver_2_0_1
> # deb2tgz gigabyte-ai-top-utility-2.0.1.deb
> # ls -l *.t?z
> -rw-r--r-- 1 root root 275757980 Jan  8 03:53 
> gigabyte-ai-top-utility-2.0.1.txz
>
> So it worked. It seems to hate having a relative path to the .deb
> file. I don't know why. In any case, I didn't get results like you
> got.
It worked when I did it that way.
> Your output included "Making symbolic link creation script". That's
> normally printed by makepkg. *Nothing* in /usr/bin/deb2tgz has that
> text or calls makepkg. All it does it deduce the compression type
> (from looking at the output of 'ar'), extract the data.tar.*, and
> rename it to match the original .deb filename.
Okay.
>
> Are you sure your deb2tgz command is actually the /usr/bin/deb2tgz one
> from SBo?
>
> # which deb2tgz
> /usr/bin/deb2tgz
Yes, but I also had one in /usr/local/bin (says from ZenWalk, which I 
never used, but don't recall where I got that).
>
> When I run it with no arguments, I get:
>
> # deb2tgz /usr/bin/deb2tgz:  Converts DEB format to standard GNU tar + 
> (GZ/XZ/LZ/BZ) format.
>    (view converted packages with "less", install and remove
>    with "installpkg", "removepkg", "pkgtool", or manually
>    with "tar")
>
> Usage:    /usr/bin/deb2tgz <file.deb>
>    (Outputs "file.t*z")
>
> What output do you get from the above two commands? If it's the same
> as mine, your original email is missing whatever 'makepkg' command you
> ran, to produce the "Making symbolic link creation script". We can't
> try to diagnose the problem if we can't see it.
The same, but I didn't run that; deb2tgz (both versions) do, and it 
scrolls off the screen fast.  I can't do it again unless I setup to test 
somehow, because I don't want it removing /root symbolic links and a lot 
of stuff in /root/chroot-current I now had to reinstall that whole chroot.



More information about the SlackBuilds-users mailing list