#trinity-desktop < 2023/01/15 >
[01:32]micheleC has joined
[02:50]Armanelgtron has quit (Ping timeout: 246 seconds)
[02:56]Armanelgtron has joined
[11:47]SlavekB has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org)
[12:04]BobSlacker has joined
[12:15]SlavekB has joined
[13:07]BobSlacker has quit (Remote host closed the connection)
[13:10]BobSlacker has joined
[13:53]BobSlacker has quit (Ping timeout: 264 seconds)
[15:32]BobSlacker has joined
[15:37]micheleC has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org)
[17:10]BobSlacker has quit (Ping timeout: 256 seconds)
[18:38]BobSlacker has joined
[23:03]a-865: is it normal for apt-get upgrade to report 10 or so trinity packages held back on debians, only to be upgraded when apt-get full-upgrade is run? what causes the "hold"?
[23:33]SlavekB has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org)
[23:56]Armanelgtron: a-865: maybe if, when you do the full-upgrade, packages are being removed
[23:57]Armanelgtron: otherwise not sure

#trinity-desktop < 2023/01/15 >