)]}' { "log": [ { "commit": "c64ea4f213afebd1602d05cdd4d5bc14eaf5356b", "tree": "90370d709a99472a34b450efe80cc92643e38d7b", "parents": [ "d380858b2de619d7712ebd84c7d9c5114a4405fe" ], "author": { "name": "yatinkarel", "email": "ykarel@redhat.com", "time": "Wed Apr 20 12:30:09 2022 +0530" }, "committer": { "name": "Dr. Jens Harbott", "email": "frickler@offenerstapel.de", "time": "Wed May 25 06:34:30 2022 +0000" }, "message": "Fix doc and user create script to set homedir permissions\n\nRHEL based distros set homedir permissions to 700,\nand Ubuntu 21.04+ to 750[1], i.e missing executable\npermission for group or others, this results into failures\nas defined in the below bug.\n\nSince in doc we add useradd command, it\u0027s good to\nadd instructions to fix the permissions there itself\ninstead of getting failures during installation and then\nfixing it.\n\nAlso update user create script to fix permissions\nby adding executable bit to DEST directory if missing.\n\n[1] https://discourse.ubuntu.com/t/private-home-directories-for-ubuntu-21-04-onwards/19533\n\nCloses-Bug: #1966858\nChange-Id: Id2787886433281238eb95ee11a75eddeef514293\n" }, { "commit": "5e2d0e0bb5beffc23087383e7923dabaa2004a98", "tree": "b206e6d6065f08343d435c446560c226fd0cc28d", "parents": [ "9ffa41ac39441bd7180496e42af28b3b692a2fc9" ], "author": { "name": "Alex Monk", "email": "krenair@gmail.com", "time": "Tue Jun 04 01:21:44 2019 +0100" }, "committer": { "name": "Alex Monk", "email": "krenair@gmail.com", "time": "Tue Jun 04 01:23:37 2019 +0100" }, "message": "Permit use of sudo-ldap instead of sudo package\n\nIf the sudo-ldap package is providing the sudo command instead of the plain\nsudo package, accept that instead of breaking the system and requiring direct\nroot login intervention to fix things.\n\nChange-Id: I45d7e4617bd59e72b4f0bf2e91750a6830e2a010\n" }, { "commit": "7710e7fc273dd9af6799ea565bbd21ce03745a44", "tree": "46bee50accf6f4c0ada1d89382ab92de5d0eebea", "parents": [ "2cb3db338a17bd26fef1f56fc155be5d01a6ef7e" ], "author": { "name": "Ian Wienand", "email": "iwienand@redhat.com", "time": "Wed Aug 27 16:15:32 2014 +1000" }, "committer": { "name": "Ian Wienand", "email": "iwienand@redhat.com", "time": "Tue Jan 12 09:23:35 2016 +1100" }, "message": "Only use lsb_release for distro tags\n\nThe existing GetOSVersion has a lot of unused code which is wrong in\nseveral ways\n\n - the only path tested in upstream CI is with lsb_release, because\n it\u0027s pre-installed on all nodes\n\n - the /etc/redhat-release checking probably still works, but is\n unnecessary\n\n - If using lsb_release, os_UPDATE has never actually been set.\n\n - the /etc/SuSE-release branch checking is broken if the lsb package\n is actually installed. lsb checking does not set os_UPDATE but yet\n the SuSE DISTRO setting relies on this to set a patch level (and so\n does some of the rpm tags). SuSE 11 is up to update 3, but the rpm\n matching is stuck hard-coded to update 2. I\u0027m guessing\n installation is actually broken there.\n\n - the debian checking branch is broken. The VERSION tags have been\n removed and were not supposed to be relied on anyway (see notes in\n [1])\n\nThis simplifies things:\n\n - remove OSX checking (moved here after discussions in\n I31d0fdd30928ecc8d959a95838b1d3affd28ac6f)\n\n - only use the output of lsb_release.\n\n - A small best-effort check to pre-install lsb packages if not\n detected (that avoids chicken-egg-problem of package-install\n wrappers relying on os_* flags).\n\n - The unset os_UPDATE is removed. It\u0027s only previous use was for\n setting separate suse versions in the DISTRO element for matching\n during package installs (since removed)\n\n - DISTRO setting is modified to use the parts of os_RELEASE it wants.\n Per-above, this is the correct place to parse out specifics.\n\n - Call out the is_* functions, which are a better way to detect\n platforms\n\n - Export the variables as read-only, since they shouldn\u0027t be reset\n\n[1] http://sources.debian.net/src/base-files/7.5/debian/changelog/\n\nChange-Id: I46a2c36d95327087085df07cb797eb91249a893c\n" }, { "commit": "dc97cb71e85fc807d2cce6f054c785922d322eb9", "tree": "86affcfbc7054c209c2ab0a4c3f7955d5e1bf16f", "parents": [ "9720239618189c13734aa32aabee9252707f2db9" ], "author": { "name": "Dean Troyer", "email": "dtroyer@gmail.com", "time": "Sat Mar 28 08:20:50 2015 -0500" }, "committer": { "name": "Dean Troyer", "email": "dtroyer@gmail.com", "time": "Sat Mar 28 14:35:12 2015 -0500" }, "message": "Mostly docs cleanups\n\nFix documentation build errors and RST formatting\n\nChange-Id: Id93153400c5b069dd9d772381558c7085f64c207\n" }, { "commit": "010959de403660e13eca54c6ef306ef5df24b436", "tree": "4f1e1ac44455c99a5eb96d84e9d9b913211a421e", "parents": [ "535e0089e0656fd4fcaa36ad5abc3653a9a45ff0" ], "author": { "name": "Jim Rollenhagen", "email": "jim@jimrollenhagen.com", "time": "Tue Feb 18 13:17:58 2014 -0600" }, "committer": { "name": "Jim Rollenhagen", "email": "jim@jimrollenhagen.com", "time": "Sun Feb 23 18:27:22 2014 -0800" }, "message": "Perform safety checks in create-stack-user.sh\n\nThis adds some safety checks to the stack user creation script.\n\nThis includes:\n- Using set -o errexit to exit early on errors\n- Make sure STACK_USER is set before doing anything with it\n\nChange-Id: If027daddd03e32c5ba3c2ebb05ad5b27d2868b0a\n" }, { "commit": "cb961597cc30f9d8ece17529f09a8291454827e3", "tree": "542d144cffde414f2c54eab747f6ff4908d675df", "parents": [ "897f48a897f9404a6825275c97ae386f0994c0e6" ], "author": { "name": "Adam Spiers", "email": "aspiers@suse.com", "time": "Sat Oct 05 12:11:07 2013 +0100" }, "committer": { "name": "Adam Spiers", "email": "aspiers@suse.com", "time": "Thu Oct 24 15:43:05 2013 +0100" }, "message": "Fix shocco errors and warnings\n\nA few Markdown-oriented issues were causing Docutils errors to\nleak into the end-user docs on http://devstack.org\n\nChange-Id: I51fa9698afb1bfb48596478d83bd1fdcd84ac52e\n" }, { "commit": "105c6e8718da2db50e48cb4a68be8522a80e101e", "tree": "290ad04b9305c01f011f41c17410b28efc4ac33a", "parents": [ "481593d8537bc2434e8dbfbfb470c60246621dda" ], "author": { "name": "Bob Ball", "email": "bob.ball@citrix.com", "time": "Fri Oct 18 15:33:26 2013 +0100" }, "committer": { "name": "Bob Ball", "email": "bob.ball@citrix.com", "time": "Fri Oct 18 15:33:26 2013 +0100" }, "message": "Create-stack-user script should have execute permissions\n\nCurrently running stack.sh as root advises you about this script, which is not\nexecutable\n\nChange-Id: I674af044b8f3c31bcc86be5c6552e8086453d5cd\n" }, { "commit": "23f69d83e5564ece0308535117cc6d224fcc3557", "tree": "80f8bd2c66f4a44dd0310dcc370fd4dca94e095e", "parents": [ "af2b982842c79e8d7f320893d4d2552b3adeb114" ], "author": { "name": "Dean Troyer", "email": "dtroyer@gmail.com", "time": "Fri Oct 04 12:35:24 2013 -0500" }, "committer": { "name": "Dean Troyer", "email": "dtroyer@gmail.com", "time": "Fri Oct 04 16:36:00 2013 -0500" }, "message": "Split the creation of $STACK_USER account out of stack.sh\n\nAutomatically creating a new user account is not always the right course\nof action when stack.sh is running as root. Plus, the re-exec did not\nwork correctly in some cases.\n\n* Create tools/create-stack-user.sh to set up a suitable user\n for running DevStack\n* Abort stack.sh and unstack.sh if running as root and suggest creating a\n suitable user account.\n\nChange-Id: I5d967c00c89f32e861449234ea8fe19261cd9ae3\n" } ] }