New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 836041 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 834412
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

cros_sdk randomly clobbers chroot when not requested

Project Member Reported by allenwebb@google.com, Apr 23 2018

Issue description

This is a feature request, but it would be nice if the bash history inside the chroot was automatically transferred across a chroot update.
 

Comment 1 by vapier@chromium.org, Apr 24 2018

Components: -Tools>ChromeOS-Toolchain Infra>Client>ChromeOS>Build
what updates are you referring to? nothing that I know of is touching this file which means it should just work.
Sometimes after I reboot and do a repo sync and run cros_sdk it downloads the chroot again and clobbers my old one. It is possible it isn't unmounting properly or something. It looked to me like an update, but if there are not updates that would trigger this, is there a log for cros_sdk that might give some hints as to what is happening?

Comment 3 by vapier@chromium.org, Apr 25 2018

Cc: bmgordon@chromium.org
Labels: -Type-Feature -Pri-3 Pri-2 Type-Bug
Summary: cros_sdk randomly clobbers chroot when not requested (was: Please preserve $HOME/.bash_history across chroot updates)
that's a bug.  the sdk shouldn't be clobbered unless you specifically told it to do so (e.g. --delete).
I haven't ever seen this myself, but what you describe sounds similar to  crbug.com/834412 
Mergedinto: 834412
Status: Duplicate (was: Untriaged)
It indeed matches the description of the other bug. I will contribute there.

Sign in to add a comment