#Error messages when trying to uninstall LibC

44 messages · Page 1 of 1 (latest)

vagrant sentinel
#

Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
apt : Depends: adduser but it is not going to be installed
(lot of similar messages)
util-linux : PreDepends: libblkid1 (>= 2.37.2) but it is not going to be installed
PreDepends: libc6 (>= 2.34) but it is not going to be installed
PreDepends: libcap-ng0 (>= 0.7.9) but it is not going to be installed
PreDepends: libmount1 (>= 2.38) but it is not going to be installed
PreDepends: libpam0g (>= https://urldefense.com/v3/__http://0.99.7.1__;!!LRBgvYU!mh_MtAsXVeE9ZQZrmLZIwt2NRt3cCA4LL9PUdpbKmiapVuaU9lrUIMGoh8gZAo7r1_OANdnpkGCxhTKQNAgFIY0uEw$ ) but it is not going to be installed
PreDepends: libselinux1 (>= 3.1~) but it is not going to be installed
PreDepends: libsmartcols1 (>= 2.38) but it is not going to be installed
PreDepends: libsystemd0
PreDepends: libtinfo6 (>= 6) but it is not going to be installed
PreDepends: libudev1 (>= 183) but it is not going to be installed
PreDepends: libuuid1 (>= 2.16) but it is not going to be installed
PreDepends: zlib1g (>= 1:1.1.4) but it is not going to be installed
Depends: util-linux-extra

pulsar brook
#

At first glance, why do you want to Uninstall libc? change it to another package? libc itself is very important package/library, without it, even simple command like bash won't work because the absence of libc (AKA; GNU C Standard Library)

stark wharf
#

@vagrant sentinel ^

#

why

vagrant sentinel
#

was going to uninstall/reinstall it as part of trying to see why another package won't install. IIRC i installed "libc6" when a package refused to find libc and running apt-get libc found nothing

fallow ingot
#

dpkg purge?

barren gulch
vagrant sentinel
barren gulch
#

@vagrant sentinel I have an idea for you to try to do this in a way that might be easier, this is how I would do this in your situation and if you want I can test it for you.

#
  1. install the Debian 12 proot-distro like you have been
#
  1. upgrade it to Debian 13 testing using the steps on the Debian wiki to get testing
#
  1. add deb-src entries to the /etc/apt/sources.list or /etc/apt/sources.list.d/*.sources files and then use apt update to get access to the apt source and apt build-dep commands
#
  1. install dependencies for compiling the Debian testing blender 4.3 package using apt build-dep blender
#
  1. download and compile the unmodified blender 4.3 Debian testing package as a test using apt source blender and cd blender-*, and apt install devscripts and debuild -b -uc -us
#
  1. if the blender 4.3 package compiles successfully, you probably now have 100% of the same dependencies that would be necessary to successfully compile vanilla blender 4.4 / blender git master, already set up by this process,
#

so you could then use apt install git-lfs, then git clone https://github.com/blender/blender.git and then follow the blender upstream manual build steps to get the "very newest" version of blender that you need

vagrant sentinel
#

ive managed to install a bunch of dependancies manually, Imma see if what i have compiles and if not I'll give your way a try

#

if i don't need the bleeding edge 4.4 ( i really just need to get across the 4.0 line) can i skip the 12-13 upgrade?

vagrant sentinel
#

I'm not clear what deb-src entries exactly to put in those files

barren gulch
#

it should look like this

#
tacokoneko@debian:~$ cat /etc/apt/sources.list.d/debian.sources 
# Modernized from /etc/apt/sources.list
Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: trixie
Components: main contrib non-free non-free-firmware 
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb deb-src
URIs: http://security.debian.org/debian-security/
Suites: trixie-security
Components: main contrib non-free non-free-firmware 
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: trixie-updates
Components: main contrib non-free non-free-firmware 
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

#

you can remove references to non-free and non-free-firmware

barren gulch
#

also note: blender will run extremely, extremely slowly with probably less than 1 FPS if you don't connect the GPU, and to connect the GPU requires setting up a graphics driver that supports at least OpenGL 4.3.

#

there is a discussion we are having about this recently here:

vagrant sentinel
#

would those same commands be likely to work for a Galaxy S10 5G, model SM-G977U?

vagrant sentinel
#

tried to build the dependancies and...yeah.

barren gulch
#

because I have Galaxy S9 SM-G960U and it doesn't need that

vagrant sentinel
#

suddenly hardware accelleration wont work in proot, says something about a missing libopenxr

And when I tried to uninstall/reinstall the Termux packages I get this?

barren gulch
#

mesa-zink is a very old package, it is only really for Mali devices and you have an Adreno device so you wouldn't need it, and those other packages also shouldn't be necessary

barren gulch
#
pkg upgrade
pkg install x11-repo
pkg install xfce termux-x11-nightly mesa-vulkan-icd-freedreno
export DISPLAY=:0 TERMUX_X11_XSTARTUP=xfce4-session
LIBGL_ALWAYS_SOFTWARE=1 termux-x11 &
#

if you are having a hard time with connecting the GPU inside of the proot (which is definitely harder because for inside of proot, unlike outside of proot, you're supposed to patch and compile your own mesa build),

#

then ideally what needs to happen is, a new blender package needs to be uploaded to TUR or to the main repository that is the newest blender 4 release, not blender 3

#

i'll do that if i get a chance to, since it would help you out a lot because using blender inside the proot seems to be really unstable for you.

barren gulch
#

@vagrant sentinel ok now I've created a new blender 4 package for TUR,

#

if you are still having trouble with getting blender 4 to work in proot-distro, please test the artifact of blender 4 for outside of proot-distro from my PR

#

the exact commands to launch it after installing the PR artifact are posted in both the issue and the PR, which would be run starting from Termux immediately after restarting Android (so with no Termux sessions inside proot-distro still running)