#(SOLVED) Suddenly, most of my packages are marked as dependency

89 messages · Page 1 of 1 (latest)

sturdy spade
#

(Abandoned) Package DB glitched

elfin bluff
#

this has nothing to do with the kernel for sure

sturdy spade
#

(Please Reinvestigate) Major Package DB glitch with pacman -Qtdq

elfin bluff
#

this is not a glitch but a misconfiguration

#

i don't know

#

then reinstall them

#

error?

#

if reinstalling the package doesn't fix the missing file then idk what's going on

#

no

#

these are not affected by package installations

#

no package will have ownership of anything in your home directory

#

that's also unrelated

sour rivet
#

What the fuck even happened for that to occur

#

Did you "unselect" all packages on your system ?

#

Can't possibly happen unless you ran some fucked up command

#

/var/log/pacman.log would help figuring out where things went south

#

Almost sure the pacman log doesn't clear itself

#

Okay so you messed up with trying to get a musl system didn't you ?

#

Oh yeah no I misread that my bad

unreal monolith
#

try sudo reflector --protocol https --sort rate --save /etc/pacman.d/mirrorlist && sudo pacman -Syyuu

#

maybe try sudo pacman -S linux linux-headers base base-devel or pacstrap them in with archiso

#

not sure how you got in this mess tbh

#

mount /mnt and /boot like you normally would to chroot in but don't chroot

#

pacstrap /mnt base base-devel linux linux-firmware linux-headers

#

make sure you got internet on archiso first,

#

kk

#

do you use ethernet or wifi?

#

so you'll have to manually network on archiso

#

why

#

I don't think it's an issue with that

#

wait you're on linux zen

#

sec

#

maybe try mkinitcpio -P linux-zen

unreal monolith
#

I think you have some packages mixed up between linux kernel and linux-zen kernel

#

probably has something to do with nvidia hook

#

did you install linux-zen-headers?

#

just a wild guess, could be wrong

#
[Trigger]
Operation=Install
Operation=Upgrade
Operation=Remove
Type=Package
Target=nvidia
Target=linux
# Change the linux part above if a different kernel is used

[Action]
Description=Update NVIDIA module in initcpio
Depends=mkinitcpio
When=PostTransaction
NeedsTargets
Exec=/bin/sh -c 'while read -r trg; do case $trg in linux*) exit 0; esac; done; /usr/bin/mkinitcpio -P'
#

notice the change the linux part if a different kernel is used

#

if you updated kernel and nvidia at the same time, this can cause issues

#

if you used linux there instead of linux-zen

unreal monolith
#

Do sudo pacman -Syyuu && sudo pacman -S linux-zen and confirm reinstall

#

Then try rebooting

cursive flare
#

did you wait for 10 min or longer?

nimble saffron
#

okay

#

show me output of pacman -Qdq and pacman -Qeq

#

don't worry, you don't have to show me everything

#

okay, thre's no fast wayto fix this other than manually picking packages from the output of the first command and pacman -D --asexplicit package-name said package

#

change the package's tag to "installed explicitly"

#

the opposite would be pacman -D --asdeps

#

tag the package as "installed as dependencies"

#

yes

#

you messed the explicit/deps tag of most of your packages

#

now most of them are tagged as deps

what were you doing anyways

#

pacman -D doesn't list packages

#

if you have refreshed the remote database and the package on the remote is a newer version, yes

#

no it wouldn't

#

explicit/deps tags are saved locally

#

not remotely

#

that would make everything be installed as explicit

#

so, 0 packages are deps

#

do you have a backup of your package list?

#

that would help

#

anyways, dunno what happened, but something you ran, ran pacman -D --asdeps on many of your packages

#

what were you doing?

#

that wouldn't affect local package db, so it's not that

#

also yeah, -Syu is the one you'd normally run, not -Syyu

#

-Syyu could wreak havoc on your system if you changed your mirrors

#

it's usually for debugging purposes

#

this is one of em

#

why were you running this?

#

not throwing shade, just wanna know context

#

yes it does

#

also a better title is

Suddenly, most of my packages are marked as dependency

sturdy spade
#

Suddenly, most of my packages are marked as dependency

nimble saffron
#

okay, backtrace, what were you doing before this

#

screw it, give me your pacman logs

#

i honestly doubt it's a bug/glitch and more user error

#

well, you sent a file right?

#

also yeah, mine has logs all the wayback to february

#

das weird

#

you're readin /var/log/pacman.log right?

river rapids
#

just find some meta packages and do -Syu --overwrite

#

whenever I bork a system beyond my capability to know what exactly went wrong, ive always ended up reinstalling, theres been times where I thought I fixed it, but end up dealing with odd issues until my patience runs out. Snap shots are nice, but they dont really help you recover from a fundamental mistake made during initial install. I prefer to make scripts to get a fresh install back to my baseline quickly

#

starting over has the advantage of ensuring there isnt some weird config you edited and forgot and is silently doing wrong stuff

#

I put all my user-dirs in $HOME/UserDirs/ to make wiping gooned up ~/.config easier without losing my normal files

#

probably my biggest gripe with KDE, too many fuckin configs