| fsmithred | Guest43, if you're the same as Guest84 I can tell you that I have chromium 131.0.6778.85-1~deb12u1 from daedalus-security. | 00:27 |
|---|---|---|
| Guest43 | i am | 00:27 |
| fsmithred | oh, there's a newer version. I just did an update and I see 131.0.6778.108-1~deb12u1 | 00:28 |
| fsmithred | I'll upgrade and see if I get it | 00:28 |
| Guest43 | fsmithred: yeah, i have that one too. if it upgrades let me know | 00:28 |
| fsmithred | he following packages have been kept back: | 00:29 |
| fsmithred | chromium chromium-common chromium-sandbox | 00:29 |
| Guest43 | ok, so i've not broken something on my end | 00:29 |
| fsmithred | nope. You're fine. | 00:29 |
| Guest43 | good to know, thanks fsmithred :-) | 00:29 |
| fsmithred | it'll probably get fixed in a couple days. I've seen a lot of updates on ff and chromium lately | 00:30 |
| Guest43 | yeah, it gets a lot of security updates compared to the other browsers. i only install the latest kernel from the backports and i'm very careful, but i still doubted i messed up somehow | 00:31 |
| Guest43 | i'll wait for it then! thanks again! | 00:32 |
| gnarface | if coyotes4ys comes back someone tell them to try #devuan-arm and stick around for longer | 02:24 |
| systemdlete | apt update tells me 3 packages are upgradable, but apt upgrade says they are "held back." | 03:29 |
| systemdlete | held back upgradable. Seriously. | 03:30 |
| rustyaxe | apt full-upgrade | 03:30 |
| debdog | chromium chromium-common chromium-sandbox | 03:30 |
| debdog | I guess? | 03:30 |
| systemdlete | debdog, yep those 3 | 03:30 |
| debdog | read the log hee | 03:30 |
| debdog | *her | 03:30 |
| debdog | e | 03:30 |
| systemdlete | the doge log? | 03:31 |
| systemdlete | :D | 03:31 |
| systemdlete | It sounds like acceleration while riding on the brake at the same time. | 03:31 |
| debdog | hmm, I do not understand that joke | 03:31 |
| rustyaxe | just did apt full-upgrade and they went fine here | 03:31 |
| rustyaxe | ohh not so much | 03:32 |
| systemdlete | well, the jumble of lines you wrote, combined with recent news events here in the us, made my brain jump immediately to "doge" | 03:32 |
| systemdlete | either the package (1) can be upgraded, or (2) cannot be upgraded. | 03:33 |
| systemdlete | what is "full upgrade?" | 03:33 |
| rustyaxe | It wont fix it anyways in this case | 03:34 |
| * systemdlete resigns himself to debdog's advice and goes back to read the log... | 03:34 | |
| systemdlete | so this probably originates at debian's end? | 03:36 |
| systemdlete | or chromium (google or whom/whatever) | 03:36 |
| Xenguy | systemdlete, It may or may not apply to you, but whenever I see 'held back' I just 'apt-get install' those packages | 03:39 |
| FatPhil | trying to diagnose an unknown problem with one of the lusers on one of my remote machines. I ssh in as a luser, su - to root, then su - to his account, but then I can't resume his screen session because "Cannot open your terminal '/dev/pts/2' - please check.". that's device is obviously owned by my luser account. | 14:55 |
| FatPhil | alas, the luser knows nothing about linux, and is giving me no indication of what's failing and how. | 14:57 |
| FatPhil | so I just want to go in as him and do what he normally does (i.e. run irssi) | 14:57 |
| fsmithred | systemdlete, the chromium package that's held back is in proposed-updates and security. The libraries it needs are only in proposed-updates. You can either enable that repo or wait until the libs move into either security or main repo. | 15:45 |
| fsmithred | fwiw, proposed-updates is for things that should get a little more testing. | 15:45 |
| LucentW | fatphil: is it a OpenVZ/Virtuozzo container? because I'm pretty sure it's a permission issue as in the user while owning the pts it can't read/write to it | 15:54 |
| joerg | man screen -> "BUGS: A weird imagination is most useful to gain full advantage of all the features." ;-) | 16:32 |
| rwp | FatPhil, Instead of using "su -" try using "sudo -i" and then "sudo -i -u luser" as sudo allocates a new pty for the new user and avoids the problem of the pty being owned by a different user. | 17:46 |
| joerg | TIL | 22:05 |
| FatPhil | joerg: weird works as an explanation | 23:25 |
| FatPhil | rwp: I will probably forget that next time its useful. | 23:26 |
| FatPhil | but thanky-thanky | 23:26 |
| joerg | FatPhil: I actually am quite ignorant re `screen` but I found some permission management commands in manpage, for multi-user access. Dunno if that's maybe useful | 23:28 |
| joerg | maybe take it to *-offtopic? | 23:29 |
| FatPhil | the luser in question still hadn't changed his "change me" password from about 5 years ago | 23:29 |
| FatPhil | I went in, and I did the dumb shit, and he's happy now | 23:29 |
| FatPhil | I even offered him the chance of changeing his p/w from "changeme42066669", and he said "no I'm happy with that one" | 23:30 |
| rrq | FatPhil: you can "chmod 777" your login /dev/pts/? and then screen should be happy (I think) | 23:47 |
| rrq | (the issue is that screen owned by luser cannot IO with the root pts you attach with) | 23:48 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!