qaz@lemmy.world to linuxmemes@lemmy.worldEnglish · 2 years agoPOV: you haven't updated in 3 days, and you're using a rolling release systemlemmy.worldimagemessage-square56linkfedilinkarrow-up1735arrow-down115
arrow-up1720arrow-down1imagePOV: you haven't updated in 3 days, and you're using a rolling release systemlemmy.worldqaz@lemmy.world to linuxmemes@lemmy.worldEnglish · 2 years agomessage-square56linkfedilink
minus-squareSanguine@sh.itjust.workslinkfedilinkarrow-up46·2 years agoDamn, how many packages you feeding that thing. Post the neofetch 🤣 Arch beenn feeling this way over last few weeks with all the kde updates basically adding “5” to end of their name.
minus-squareTb0n3@sh.itjust.workslinkfedilinkEnglisharrow-up9·2 years agoIt’s even worse when you have 60 packages to just hit enter to and then one that defaults to no for a conflict and you have to do it all over again.
minus-squareSanguine@sh.itjust.workslinkfedilinkarrow-up3·2 years agoOh yeah with that one update a few days ago that required --overwrite…forget which package it was.
minus-square/home/pineapplelover@lemm.eelinkfedilinkarrow-up3·2 years agoI have been ignoring virtualbox for months now because something about incompatible dependencies
minus-squarecygnuslinkfedilinkarrow-up1·1 year agoProbably a kernel 6.5 issue? I have to boot into 6.4 for it to work.
minus-squareHolzkohlen@feddit.delinkfedilinkarrow-up3·2 years agoDid I see that right: they added it and then removed it a few days later? Could be the other way round too.
Damn, how many packages you feeding that thing. Post the neofetch 🤣
Arch beenn feeling this way over last few weeks with all the kde updates basically adding “5” to end of their name.
It’s even worse when you have 60 packages to just hit enter to and then one that defaults to no for a conflict and you have to do it all over again.
Oh yeah with that one update a few days ago that required --overwrite…forget which package it was.
I have been ignoring virtualbox for months now because something about incompatible dependencies
Probably a kernel 6.5 issue? I have to boot into 6.4 for it to work.
Did I see that right: they added it and then removed it a few days later? Could be the other way round too.