New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 1.1.0 status #266
Comments
Updated:
|
Fresh install to User home :
I wonder if the Invalid switch was expected here. |
@harijoe thank you for such a quick feedback. I should be more precise in the expected section but yes, it was expected, we just want to see if the package was installed correctly. arj does not have that switch |
@harijoe Thanks for testing, please let us know when you test all scenarios - the first scenario is the most important ;) |
Expected release date: in 1-2 days |
No errors during the upgrade from 1.0.1 to 1.0.2. I will test with another installation later tonight. |
To all beta testers, please report the results in the following format:
|
@tombujok I get an error message here: |
We are about to release ;) Would be great to hear back from @glennular. Any chance you could retest your case? |
@tombujok I agree, this scenario is rather unlikely to happen. I just tested a few admin related scenarios. Looks good to me |
@glennular Ok, perfect. We are waiting. I agree. Expected release date: 18.00 CET today |
@tombujok New error occurring with your recent changes when updating without admin rights
|
@glennular weird What do you get when you run this as a normal user?
What are the steps that you perform? For me it is:
|
@jlupi When i run that i get:
My Steps
|
@glennular Ok, I guess that when you run babun update you probably see a msg that your branch is behind XX commits right? The problem is that in normal scenario you do not switch branches, you always stay on the release branch. To workaround this issue, for the test purposes, we provided the bash-betatest-setup.sh, which does the branch switch and git pull (and afterwards some dos2unix and chmods just in case). You can do that manually, or just try running the script. |
@glennular BTW the chmod checks look good, based on this and having the new code you should not be able to perform 'babun update' |
just to let you know, I was able to update successfully yesterday with the steps I listed above. Where is the bash-betatest-setup.sh? |
@glennular I belive you :) It may work if you execute babun update multiple times, or if you do git pull in the source folder after branch switching (depending on your git autocrlf settings). The problem was fixed here 82c3484 The script itself:
|
@jlupi Nope it worked. i would run update once as normal user (get to permission error when updating the babun core plugin) and then run in admin mode and get a successful update. Testd on both win7x64 and win8x64 i will try the script |
OK tested with the beta script got the permission check did see this though: |
have you guys thought of opening a Gitter room for communication? https://gitter.im |
@glennular I know the test procedure is complex, (we will try to make it easier) but as I reckon you executed the betatest.sh script as admin, that's the reason why you see this error, am I right? I am sure that when you execute the following command even now as non-admin you will get permission denied: Could you check this chmod? and if possible try to rexecute this test case, but do it like this:
|
@tombujok I had to run the scripts as admin or else I get the following
Running your command:
|
@glennular Thanks for your tests! I think it's an extreme corner case. We've tested a lot this admin/non-admin problem and added two checks to make sure the user does not run into troubles. It's anyway the user's responsibility to control if they update with the same user that they've installed babun with - and it's easy to think of a case where sth may go wrong. We will add an entry to the FAQ to summarize what to do in case "permission denied" messages pop up during the update. I've just found a small bug which means that @jlupi and me have to run our acceptance tests again (sic!)... |
@glennular Now I understood, it went through but you saw OK guys we are ready for release! |
The release is ready, but tomorrow is Good Friday, so we will be offline. |
The newest babun has been just released! It's been a tremendous effort, but we believe that the newest version is a huge step forward. I would like to personally thank everybody who contributed to this release. Enough said, now execute babun update and enjoy the newest version with the newest cygwin! |
Have a look at the newest blog entry about 1.1.0: |
@tombujok Sadly I've run into some issues upgrading babun when behind a proxy (enterprise). The upgrade process doesn't appear to have honored the proxy settings defined in my .babunrc and while it references a proxy "switch", passing in /proxy http://user:passwd@proxyname:80 didn't appear to work either. I tried setting http_proxy manually and exporting http and https entries in .babunrc, but nothing has worked. I'll probably just grab the newest release, but it would be great to get the "seamless" upgrades working regardless of network environment. |
@dragon788 It should automatically read http_proxy from .babunrc - I am not sure why Passing the proxy in the following format to udate.bat should work too: (no username:password@ part). On Mon, Apr 6, 2015 at 10:24 PM, dragon788 notifications@github.com wrote:
|
@dragon788 Also see issue #273 . I had a similar issue and had to omit the |
I think part of my problem is I "moved" my home directory according to the cygwin documentation to C:\Users via /cygdrive/c/Users/ instead of /home/ But when I run with /proxy=proxyname:port or /proxy=http://proxyname:port it never prompts me for the password, and even if I hardcode with /proxy=(http://)username:password@proxyname:port it still fails to update correctly. Something similar to mkpasswd -l [-d] > /etc/passwd is what I used to change my "home". Starting cygwin install, version 2.870 Current Directory: C:/Users//.babun//dist |
After babun got itself in a bad way (opening to just sh4.1). I have been able to execute /bin/bash and then 'http_proxy=http://proxyname:port babun update' works and it prompts me for a username and password for the proxy for Cygwin. I'm not sure if it will sort itself out with my correct home directory again at this point, but its not too terribly hard to redirect my home directory and leave everything installed where it sits. Is there any code/tests around whether the user's current home directory is the default or has moved before performing an upgrade? |
@dragon788 Great that you managed to fix your babun instance. Yes, there is such code. |
Status of the critical 1.1.0 release:
Release will be performed when all steps have been completed.
Expected release date: 04.04.2015 - 10.00 CET
The text was updated successfully, but these errors were encountered: