[04:30] <yurtesen> good morning
[04:31] <yurtesen> utkarsh2102: can the rsyslog change from 2009 be undone? I mean this one -> https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/388608
[06:13] <yurtesen> utkarsh2102: because that change makes Ubuntu rsyslog package different than Debian counterpart, and also cause tomcat9 package to need to be different.
[07:31] <mirespace> good morning everyone
[07:59] <utkarsh2102> yurtesen: I'm away till Tuesday but in general, not running it as root is a good idea, don't you think?
[07:59] <utkarsh2102> yurtesen: if we have to deviate for tomato, so be it! :)
[08:00] <utkarsh2102> tomcat9* 🤦‍♂️
[08:00] <utkarsh2102> r.i.p. autocorrect, heh 
[10:19] <yurtesen> utkarsh2102: I think you will find your answer if you suggest not running rsyslog as root to Debian. What do you think about that idea? This also would solve the problem for Ubuntu with packages imported from Debian. But I think rsyslog is a software which has feature to write files owned by different user/groups. So it seems it is a requirement that it runs as root. So to say, not 
[10:19] <yurtesen> running as root is causing problems. It is hard to find people who will solve them (eg. tomcat9 problem we have). So... is it better to just run it as root? or have a broken system? :)  
[13:55] <ShellcatZero2> Shellcat
[23:59] <camibohp> Hi: When ubuntu server 22.04 is available to upgrade from CLI ??? (Installed release: 20.04, Device: Raspberry Pi 3B+)