=== Eickmeyer[w] is now known as Eickmeyer
[05:15] <tarzeau> yurtesen: usually it's who is defined in debian/control (Maintainer and Uploader fields), depends on if it's a 0changed in ubuntu pkg or not, if it's fixed in debian but not ubuntu, requestsync is required (i don't know until when it's supported, 22.04 is short before release)
[06:47] <tarzeau> yurtesen: that maintainer (the team) is the one of debian, where it's fixed already. so since it's only an ubuntu related problem, the debian people should not have been bothered
[06:47] <tarzeau> i think the requestsync thing would have been enough, or asking someone else in here (sorry i'm no ubuntu expert)
[07:18] <yurtesen> tarzeau: it is not comopletely true that it is fixed in Debian, it just does not effect Debian. But I see from changelog that at least one other thing which did not effect Debian was backported to Debian also.
[07:24] <yurtesen> tarzeau: I could try requestsync it sounds like a good idea (I was just reading about the process) but then why did I do debdiff? The sponsorship queue wiki says in 1st step to check is that patch is in debdiff format... I am officially confused :)
[07:24] <yurtesen> I mean this wiki -> https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue
[07:28] <tarzeau> yurtesen: yeah debdiff is even better...
[07:28] <tarzeau> yurtesen: you did all well.
[08:44] <yurtesen> tarzeau: if in Ubuntu there is no maintainer for this package. Who should maintain it? it feels like this is falling through the cracks here.
[09:05] <schopin> yurtesen: universe is a best-effort place, there usually isn't any one person or group designated to care for a given package.
[09:12] <yurtesen> schopin: Is that a mild way of saying packages in universe are unmaintained? What if somebody wants to help maintain a package in universe? Is it even possible to help?
[10:13] <schopin> yurtesen: I haven't been around long enough to be able to tell you how one could maintain a specific package in Ubuntu. https://wiki.ubuntu.com/UbuntuDevelopers seems to imply there's a way to do that via delegated teams.
[10:16] <schopin> but as a first step, my guess is that you're already doing what's possible: providing patches and waiting for someone to sponsor them.
[10:18] <schopin> yurtesen: is your tomcat issue also relevant to impish?
[10:30] <yurtesen> schopin: yes it is, also indirectly focal as in focal as that package does not include any fixes related to the issue yet.
[10:30] <schopin> yurtesen: you're going to have to make your bug SRU-ready https://wiki.ubuntu.com/StableReleaseUpdates
[10:31] <schopin> yurtesen: I'm willing to help you but sadly I don't know anything about logrotate :/
[11:10] <rbasak> yurtesen: packages in Ubuntu are generally team-maintained. We don't usually nominate specific people to packages, only teams.
=== alan_g_ is now known as alan_g
[11:11] <rbasak> The problem here is that there aren't enough qualified people reviewing contributions from non-qualified people :-/
[11:11] <rbasak> Ideally, we'd get good contributions from non-qualified people and get them qualified to be able to fix things without further supervision.
[11:11] <rbasak> I did glance at your fix, but the problem is that it wasn't immediately obvious to me that it is the correct fix. It would take me some research to confirm that for myself. I've added it to my todo list but I'm quite busy.
[11:13] <rbasak> Ideally you'd join our set of trusted uploaders and then help others join too.
[11:24] <yurtesen> schopin: But it effects jammy also. I would be happy to get it fixed for jammy as a start. I think it would be an easier path since jammy is not released yet. If you can help, you do not need to know much about logrotate or syslog. I am willing to try to answer any questions you might have in a way that anybody can understand. Because if we do not try, we failed already. :)
[11:26] <schopin> Well, I do need to know about those, since it's their integration that is buggy. As a rule, I only upload patches that I understand :)
[11:27] <yurtesen> rbasak: I understand but since there are nobody reviewing my suggestion, It appears I can never become qualified enough to fix things without further supervision. Of course if there is something wrong with my fix, I would like to learn and make a better suggestion. But right now, I am getting no feedback so that is also impossible.
[11:29] <yurtesen> schopin: Well syslog writes log files and logrotate rotates them :p it is not rocket science. But in case of Ubuntu, somebody decided syslogd should run as `syslog` user. I wish I could find that person and get him to help me. :) is there a way to find who decided this? because in Debian syslog runs as `root` user...
[11:31] <schopin> yurtesen: as a rule you should be able to find out such stuff by looking at /usr/share/doc/logrotate/changelog.Debian.gz ;)
[11:33] <yurtesen> schopin: that was really useful comment :) thanks. It appears this change is actually quite new "Steve Langasek <steve.langasek@ubuntu.com>  Wed, 29 Dec 2021"
[11:35] <schopin> yurtesen: I see how you came to this conclusion, but actually no, this changelog entry is from a merge, so this lists all the differences from Debian that are *still* part of the packaging.
[11:38] <schopin> yurtesen: doing some more digging in the changelog, it appears this change has been introduced back in 2009, see LP: #388608 and LP: #250827
[11:38] <ubottu> Launchpad bug 388608 in Rsyslog "Don't run as root" [Wishlist, Confirmed] https://launchpad.net/bugs/388608
[11:38] <ubottu> Launchpad bug 250827 in rsyslog (Ubuntu) "rsyslog does not create a system user like sysklogd" [Undecided, Fix Released] https://launchpad.net/bugs/250827
[11:42] <yurtesen> schopin: thanks it seems as Michael Terry <michael.terry@canonical.com> but he seem to have left canonical in 2017 according to linkedin :D
[11:48] <yurtesen> I guess he won't be able to help with this. I guess if this change was also in upstream Debian, now we would not be here either. :(
[11:52] <yurtesen> At least nobody can say I did no try: "Your message to michael.terry@canonical.com couldn't be delivered. michael.terry wasn't found at canonical.com."
[12:28] <rbasak> yurtesen: you're in my TODO but a few days away yet unfortunately. But please remain active here and keep asking. The way to get priority treatment is to ensure that everyone knows you're around and won't just disappear. Then potential sponsors will feel that it's worth spending time on your contributions, and you can build your reputation up from there.
[12:28] <rbasak> It'd be good if it this wasn't necessary.
[12:41] <yurtesen> rbasak: I will be around. I am happy that you will have a look at it. Thank you. I am fine being here, as long as people do not start complaining about me begging daily :)
=== st13g is now known as crisdel