[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#909395: marked as done (upgrade-reports: missing sbin in root path)

Your message dated Sun, 21 Apr 2019 19:57:32 +0200
with message-id <110d2366-70ad-0725-5aa7-a7a0fd891b86@debian.org>
and subject line Re: Bug#909395: upgrade-reports: missing sbin in root path
has caused the Debian Bug report #909395,
regarding upgrade-reports: missing sbin in root path
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
909395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909395
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: upgrade-reports
Severity: important

Dear Maintainer,

Not really sure where to submit this but upgrading to buster via instructions at
https://wiki.debian.org/DebianTesting
resulted in a system that would boot fine, but when i went back in to aptitude afterwards I noticed
/sbin (and its subdirectories, eg /usr/local/sbin:/usr/sbin:/sbin ) was not in root's path.  This meant 
if I used 'su' to log in to root, to install/upgrade/whathaveyou ...ldconfig, 'shutdown' among other 
things was not in the path.

I've now upgraded 2 systems from stable to buster and both did the same thing.

adding 

PATH=$PATH:/usr/local/sbin:/usr/sbin:/sbin

to .bashrc for root (which was empty) made at least installing/upgrading via aptitude work...but there
wasn't much indication that I had to do this anywhere.  

If this is something new that we have to do for buster, it should be in the instructions

-- System Information: 
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message --- 
Hi Jeff,

On Tue, 25 Sep 2018 18:08:00 +0000 Niels Thykier <niels@thykier.net> wrote:
> Are you perhaps using "su" (instead of "su -") when changing to root?
> If so, then there is a Stretch -> Buster specific change specifically
> for "su" about that in util-linux's NEWS file.  It will probably be
> written in the release-notes for buster (once we start writing those for
> buster).

This ended being tracked and fixed in bug 923644.

https://salsa.debian.org/ddp-team/release-notes/commit/fc73173

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: