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

Closed
tombujok opened this Issue Mar 30, 2015 · 64 comments

Comments

Projects
None yet
9 participants
@tombujok
Contributor

tombujok commented Mar 30, 2015

Status of the critical 1.1.0 release:

  • candidate release prepared [OK]
  • candidate release smoke-tested [OK]
  • update from 1.0.1 to 1.1.0 tested [OK]
  • install of fresh 1.1.0 [OK]
  • acceptance tests by volunteers [IN PROGRESS]

Release will be performed when all steps have been completed.
Expected release date: 04.04.2015 - 10.00 CET

@tombujok

This comment has been minimized.

Contributor

tombujok commented Mar 30, 2015

Updated:

  • install of fresh 1.1.0 [EXPERIENCING PROBLEMS] -> [OK]
@harijoe

This comment has been minimized.

harijoe commented Mar 31, 2015

Fresh install to User home :
Everything okay except

{ ~ }  » arj --version                                                                        ~ 7
ARJ32 v 3.10, Copyright (c) 1998-2004, ARJ Software Russia. [28 Dec 2009]


Invalid switch: --version

I wonder if the Invalid switch was expected here.

@jlupi

This comment has been minimized.

Contributor

jlupi commented Mar 31, 2015

@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

@tombujok

This comment has been minimized.

Contributor

tombujok commented Mar 31, 2015

@harijoe Thanks for testing, please let us know when you test all scenarios - the first scenario is the most important ;)

@tombujok

This comment has been minimized.

Contributor

tombujok commented Mar 31, 2015

Expected release date: in 1-2 days

@ghost

This comment has been minimized.

ghost commented Mar 31, 2015

No errors during the upgrade from 1.0.1 to 1.0.2. I will test with another installation later tonight.

@tombujok

This comment has been minimized.

Contributor

tombujok commented Mar 31, 2015

To all beta testers, please report the results in the following format:
Thanks for your tests!

Test Scenario Status Comments
Scenario 1 OK / NOK ...
Scenario 2 OK / NOK ...
Scenario 3 OK / NOK ...
Own scenario OK / NOK ...
@v-yadli

This comment has been minimized.

Contributor

v-yadli commented Apr 2, 2015

@tombujok I get an error message here: zsh: permission denied: babun with nothing else printed out.
Executing permcheck=$( chmod 777 /etc/passwd /usr/local/bin/babun 2> /dev/null || echo "FAILED" ) manually does echo "FAILED" back to me. So I think it never reached there.

@tombujok

This comment has been minimized.

Contributor

tombujok commented Apr 2, 2015

@v-yadli ok, but your case is really specific, with these BitLocker hacks and the fact the you are using a differen user. It's an edge case - either update as admin or change the permissions in windows. @jlupi WDYT?

@tombujok

This comment has been minimized.

Contributor

tombujok commented Apr 2, 2015

We are about to release ;) Would be great to hear back from @glennular. Any chance you could retest your case?

@jlupi

This comment has been minimized.

Contributor

jlupi commented Apr 2, 2015

@tombujok I agree, this scenario is rather unlikely to happen. I just tested a few admin related scenarios. Looks good to me

@glennular

This comment has been minimized.

glennular commented Apr 2, 2015

@tombujok not at a computer at the moment. Give me ~2 hours

I want to make sure I don't get the same error as @v-yadli

Side note, we need better support for development off of forks. Better documentation or the ability to specify repo. I'd like to help for the next release

@tombujok

This comment has been minimized.

Contributor

tombujok commented Apr 2, 2015

@glennular Ok, perfect. We are waiting. I agree.

Expected release date: 18.00 CET today

@glennular

This comment has been minimized.

glennular commented Apr 2, 2015

@tombujok New error occurring with your recent changes when updating without admin rights

Executing babun update
  upstream  [candidate]
  installed [1.0.1]
  newest    [1.1.0]
error: unable to unlink old '.gitignore' (Permission denied)
error: unable to unlink old 'README.adoc' (Permission denied)
error: unable to unlink old 'babun-core/core.groovy' (Permission denied)
error: unable to unlink old 'babun-core/plugins/cacert/install.sh' (Permission denied)
error: unable to unlink old 'babun-core/plugins/cacert/install_home.sh' (Permission denied)
...
error: unable to unlink old 'babun-packages/packages.groovy' (Permission denied)
error: unable to unlink old 'babun-packages/wget.exe' (Permission denied)
error: unable to unlink old 'babun.version' (Permission denied)
error: unable to unlink old 'build.groovy' (Permission denied)
fatal: Could not reset index file to revision 'HEAD'.
Error on or near line 41, last command 'git --git-dir="$babun/source/.git" --work-tree="$babun/source" reset --hard';
@jlupi

This comment has been minimized.

Contributor

jlupi commented Apr 2, 2015

@glennular weird

What do you get when you run this as a normal user?

chmod 777 /etc/passwd /usr/local/bin/babun

What are the steps that you perform?

For me it is:

  • download 1.0.1 from the website
  • install 1.0.1 as administrator
  • download and execute the test_setup_script.sh as described in scenarios (here I tried both, running the sh as administrator and as a normal user)
  • exit babun
  • start babun as a normal user
  • babun check - expected File permissions [FAILED]
  • babun update - expected: RROR: The update has failed! You don't have write permission to / filesystem!
@glennular

This comment has been minimized.

glennular commented Apr 2, 2015

@jlupi When i run that i get:

{ ~ }  » chmod 777 /etc/passwd /usr/local/bin/babun
chmod: changing permissions of `/etc/passwd': Permission denied
chmod: changing permissions of `/usr/local/bin/babun': Permission denied

My Steps

  • download 1.0.1 from the website
  • install 1.0.1 as administrator
  • exit babun
  • start babun as normal user
  • export BABUN_BRANCH=candidate
  • babun update
@jlupi

This comment has been minimized.

Contributor

jlupi commented Apr 2, 2015

@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.
In 1.0.1 there was a small issue that the update fetched changes but did not pull them when branches were switched. This is why you probably do not even have the code that @tombujok checked in recently.

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.

@jlupi

This comment has been minimized.

Contributor

jlupi commented Apr 2, 2015

@glennular BTW the chmod checks look good, based on this and having the new code you should not be able to perform 'babun update'

@glennular

This comment has been minimized.

glennular commented Apr 2, 2015

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?

@jlupi

This comment has been minimized.

Contributor

jlupi commented Apr 2, 2015

@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:

wget http://static.reficio.org/babun/babun-betatest-setup.sh

dos2unix babun-betatest-setup.sh

chmod 755 babun-betatest-setup.sh

./babun-betatest-setup.sh

source ~/.babunrc
@glennular

This comment has been minimized.

glennular commented Apr 2, 2015

@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

@glennular

This comment has been minimized.

glennular commented Apr 2, 2015

OK tested with the beta script got the permission check

did see this though: error: Unable to append to .git/logs/HEAD: Permission denied

@glennular

This comment has been minimized.

glennular commented Apr 2, 2015

have you guys thought of opening a Gitter room for communication? https://gitter.im

@tombujok

This comment has been minimized.

Contributor

tombujok commented Apr 2, 2015

@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:
chmod 777 /etc/passwd /usr/local/bin/babun

Could you check this chmod? and if possible try to rexecute this test case, but do it like this:

  • as admin -> only install babun and close it
  • as non admin: open babun and then
wget http://static.reficio.org/babun/babun-betatest-setup.sh
dos2unix babun-betatest-setup.sh
chmod 755 babun-betatest-setup.sh
./babun-betatest-setup.sh
source ~/.babunrc
babun update
@glennular

This comment has been minimized.

glennular commented Apr 2, 2015

@tombujok I had to run the scripts as admin or else I get the following

{ ~ }  » dos2unix babun-betatest-setup.sh
dos2unix: converting file babun-betatest-setup.sh to Unix format...
{ ~ }  » chmod 755 babun-betatest-setup.sh
{ ~ }  » ./babun-betatest-setup.sh
error: unable to unlink old '.gitignore' (Permission denied)
error: unable to unlink old 'README.adoc' (Permission denied)
error: unable to unlink old 'babun-core/core.groovy' (Permission denied)
error: unable to unlink old 'babun-core/plugins/cacert/install.sh' (Permission denied)
error: unable to unlink old 'babun-core/plugins/cacert/install_home.sh' (Permission denied)
error: unable to unlink old 'babun-core/plugins/cacert/plugin.desc' (Permission denied)
error: unable to unlink old 'babun-core/plugins/core/install.sh' (Permission denied)
...
dos2unix: Failed to change the owner and group of temporary output file /usr/local/etc/babun/source/.git/d2utmpuOG9zM: Permission denied
dos2unix: converting file /usr/local/etc/babun/source/.git/config to Unix format...
dos2unix: problems converting file /usr/local/etc/babun/source/.git/config
dos2unix: Failed to change the owner and group of temporary output file /usr/local/etc/babun/source/.git/d2utmpyIKKM6: Permission denied
...
chmod: changing permissions of `/usr/local/etc/babun/source/babun-core/plugins/cacert/install.sh': Permission denied
chmod: changing permissions of `/usr/local/etc/babun/source/babun-core/plugins/cacert/install_home.sh': Permission denied
chmod: changing permissions of `/usr/local/etc/babun/source/babun-core/plugins/core/install.sh': Permission denied

Running your command:

{ ~ }  » chmod 777 /etc/passwd /usr/local/bin/babun
chmod: changing permissions of `/etc/passwd': Permission denied
chmod: changing permissions of `/usr/local/bin/babun': Permission denied
@tombujok

This comment has been minimized.

Contributor

tombujok commented Apr 2, 2015

@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!)...

@tombujok

This comment has been minimized.

Contributor

tombujok commented Apr 2, 2015

@glennular Now I understood, it went through but you saw error: Unable to append to .git/logs/HEAD: Permission denied -> So this is OK!

OK guys we are ready for release!

@tombujok

This comment has been minimized.

Contributor

tombujok commented Apr 2, 2015

The release is ready, but tomorrow is Good Friday, so we will be offline.
The release is scheduled for Saturday 10.00 CET.

@tombujok

This comment has been minimized.

Contributor

tombujok commented Apr 4, 2015

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.
I would like to menton @jlupi in the first place, since he was the main driver of this release.
Many thanks also to our beta testers and all other people who submitted contributions or pull requests!

Enough said, now execute babun update and enjoy the newest version with the newest cygwin!

@tombujok tombujok closed this Apr 4, 2015

@tombujok

This comment has been minimized.

Contributor

tombujok commented Apr 4, 2015

Have a look at the newest blog entry about 1.1.0:
http://babun.github.io/blog/

@dragon788

This comment has been minimized.

dragon788 commented Apr 6, 2015

@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.

@tombujok

This comment has been minimized.

Contributor

tombujok commented Apr 6, 2015

@dragon788 It should automatically read http_proxy from .babunrc - I am not sure why
it did not work for you.
Could you show the output of :
grep 'export http_proxy=' ~/.babunrc | grep -v '#' | sed 's/export
http_proxy=//g' | cut -d "@" -f 2

Passing the proxy in the following format to udate.bat should work too:
/proxy http://proxyname:80

(no username:password@ part).
If the proxy requires authentication a popup will be shown.

On Mon, Apr 6, 2015 at 10:24 PM, dragon788 notifications@github.com wrote:

@tombujok https://github.com/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.


Reply to this email directly or view it on GitHub
#266 (comment).

@igitur

This comment has been minimized.

Contributor

igitur commented Apr 7, 2015

@dragon788 Also see issue #273 . I had a similar issue and had to omit the http:// part from the proxy parameter. Does that work for you?

@dragon788

This comment has been minimized.

dragon788 commented Apr 7, 2015

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
User has backup/restore rights
io_stream_cygfile: fopen(/etc/setup/setup.rc) failed 2 No such file or directory

Current Directory: C:/Users//.babun//dist
Could not open service McShield for query, start and stop. McAfee may not be ins
talled, or we don't have access.
root: C:/Users//.babun/\cygwin system
Selected local directory: C:/Users//.babun//dist
net: Proxy
Cached mirror list unavailable
get_url_to_membuf http://cygwin.com/mirrors.lst
getUrlToStream http://cygwin.com/mirrors.lst
getUrlToStream failed!
get_url_to_membuf failed!
Defaulting to empty mirror list
site: http://mirrors.kernel.org/sourceware/cygwin/

@dragon788

This comment has been minimized.

dragon788 commented Apr 7, 2015

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?

@tombujok

This comment has been minimized.

Contributor

tombujok commented Apr 7, 2015

@dragon788 Great that you managed to fix your babun instance. Yes, there is such code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment