Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
IntrusionCM5895183dThe package installs files to /usr/local/bin
The package only knows about it's own package files.
When uninstall happens, from the point of view of the package the /usr/local/bin directory should be empty.
Hence it tries to nuke it. Default behaviour of dpkg packages. -
Linux44437183d
-
IntrusionCM5895183d@Linux Nope. It's default behaviour.
Afaik for any non protected path.
Eg /opt.
Would need to check dpkg / debian pages, but this is definitely 100 % a thing. -
myss4557183d@IntrusionCM funny, I've never noticed this kind of warning while in upgrade or remove process. But then again, there's a chance I didn't pay attention it it 🤷♂️
-
IntrusionCM5895183dI think linux and I are both right.
If I remember correctly you could state sny directory in... Debian/files ? I think.
And if it's stated there and an non protected path, the *rm stage will nuke it.
(prerm I think)
Regular pathes like /usr/bin, /bin ... should be protected afaik. -
netikras26414183d@IntrusionCM or just some classic sloppy script bug without failsafes in the pre/post-install
bin_dir=/usr/local/bin
rm -f "${bin_dir}/${file}"
and if ${file} ir empty - this happens -
IntrusionCM5895183d@netikras of all the fuckery...
Does this still exist Oo
I thought stuff like that was bombed away by QA long time ago -
Linux44437183d
-
faheel2984183d@kejojedi Never. Even if a faulty upgrade script screwed up my system I would first fix my system, and then try to fix the script and maybe send it's dev's the patch, but I wouldn't buy a Mac. No matter how much money I made.
WTF was dpkg trying to do here?!
random
apt upgrade
dpkg