I've just hit a bug whilst on brasstacks, that will either be fixed in newer Mercurial versions, or else if not I will be able to report upstream iff we've on a newer version. I ran |hg status| as root, on the orangefactor repo - which failed with: Not trusting file /home/webtools/apps/orangefactor/src/orangefactor/.hg/hgrc from untrusted user webtools, group webtools Not trusting file /home/webtools/apps/orangefactor/src/orangefactor/.hg/hgrc from untrusted user webtools, group webtools Fair enough to not trust the file - however, that left behind ./hg/dirstate which had a user+group of root, so once I switched back to webtools I got: [firstname.lastname@example.org orangefactor]$ hg status abort: Permission denied: /home/webtools/apps/orangefactor/src/orangefactor/.hg/dirstate ...and had to chown it back to webtools:webtools. Now I guess the correct solution is to set the sticky bit on the repo, so files created have the correct permissions, but either way IMO Mercurial shouldn't abort with a "from untrusted user" error and still leave behind files. I'm not sure whether updating Mercurial is something we'll have to do ourselves, or if brasstacks is IT managed, so filing in the OrangeFactor component for now...
[email@example.com ~]# hg --version Mercurial Distributed SCM (version 1.4)
[firstname.lastname@example.org orangefactor]# yum update mercurial Loaded plugins: downloadonly, rhnplugin, security This system is receiving updates from RHN Classic or RHN Satellite. Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package mercurial.x86_64 0:1.4-3.el6 will be updated ---> Package mercurial.x86_64 0:2.5.4-0 will be an update --> Finished Dependency Resolution Dependencies Resolved ======================================================================================================================== Package Arch Version Repository Size ======================================================================================================================== Updating: mercurial x86_64 2.5.4-0 mozilla 3.0 M Transaction Summary ======================================================================================================================== Upgrade 1 Package(s) Total download size: 3.0 M Is this ok [y/N]: y Downloading Packages: mercurial-2.5.4-0.x86_64.rpm | 3.0 MB 00:00 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Updating : mercurial-2.5.4-0.x86_64 1/2 Cleanup : mercurial-1.4-3.el6.x86_64 2/2 Verifying : mercurial-2.5.4-0.x86_64 1/2 Verifying : mercurial-1.4-3.el6.x86_64 2/2 Updated: mercurial.x86_64 0:2.5.4-0 Complete! [email@example.com ~]# hg --version Mercurial Distributed SCM (version 2.5.4)
Assignee: nobody → emorley
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.