Re: Marc Haber
> The actual version of the sudo in question isnt here.
1.9.15p5-3+b1.
Upgrading to 1.9.16-2 does not change the problem.
Christoph
On Fri, Nov 01, 2024 at 06:18:33PM +0100, Christoph Berg wrote:
> > It would probably help if you would give the information that reportbug
> > gives when you file a bug against sudo in the first place.
>
> -- System Information:
> Debian Release: trixie/sid
> APT prefers testing
> APT policy:
Re: Marc Haber
> >From the bug I only see that you're using testing. testing has a sudo
> version from january 2024. If this is a recent breakage, then it was
> another package causing it. PAM is a maze for me.
It's not that old, I would guess at most a few weeks. The way I
noticed is PostgreSQL's
Control: tags -1 help
thanks
On Thu, Oct 31, 2024 at 10:11:33PM +0100, Christoph Berg wrote:
> So `sudo -u postgres -i` opens a login shell as postgres and starts systemd.
>
> But `sudo su -`; `su - postgres` opens a login shell as postgres and does not
> start systemd.
>
> sudo shouldn't behav
On Thu, 31 Oct 2024 19:01:11 +0100 Marc Haber
wrote:
> Hi,
>
> Luca wrote:
> > reassign 1086509 sudo
>
> I find it pretty rude to just reassign without a single word of
> explanation. You (that means all of you reading this) have one week
to
> tell me what sudo can do here to fix this. After tha
So `sudo -u postgres -i` opens a login shell as postgres and starts systemd.
But `sudo su -`; `su - postgres` opens a login shell as postgres and does not
start systemd.
sudo shouldn't behave differently here; I guess there is some
difference somewhere in the pam configuration.
Christoph
Hi,
Luca wrote:
> reassign 1086509 sudo
I find it pretty rude to just reassign without a single word of
explanation. You (that means all of you reading this) have one week to
tell me what sudo can do here to fix this. After that, the bug will be
wontfixed or closed from the sudo side.
Other team
7 matches
Mail list logo
