- Release-team - mailman3.cels.anl.gov

Fwd: Request to share KBase Services
by Nomi Harris 25 Jan '13

25 Jan '13

Matthew Benedict is, as far as I know, a non-KBase person who has subscribed to the devel mailing list. He now wants access to the KBase Services mailing list. I am not inclined to grant this, unless any of you feel strongly that I should. Nomi Begin forwarded message: > From: "Matthew Benedict (Google Drive)" <matthew.n.benedict(a)gmail.com> > Subject: Request to share KBase Services > Date: January 25, 2013 7:24:16 AM PST > To: nlharris(a)lbl.gov > > Request to share > KBase Services > > You are the owner of this item and matthew.n.benedict(a)gmail.com has asked that you share this item with: > + matthew.n.benedict(a)gmail.com > Add these people in Sharing settings. > > Google Drive: create, share, and keep all your stuff in one place.

1 0

redeployment is complete.
by Dan Olson 25 Jan '13

25 Jan '13

---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055

1 0

Re: [Release-team] deployment errors
by Robert Olson 25 Jan '13

25 Jan '13

Oh I see - we were testing a change to the dev_container commit rules and a bad makefile change got pushed. I just fixed. On Jan 25, 2013, at 8:35 AM, Dan Olson wrote: > Ok.. This completely broke deployment. For all modules. I cannot proceed until this is fixed. > > /kb/deployment doesn't even get created. > > ----- Original Message ----- >> From: "Dan Olson" <dolson(a)mcs.anl.gov> >> To: release-team(a)kbase.us >> Cc: "Robert Olson" <olson(a)mcs.anl.gov> >> Sent: Friday, January 25, 2013 8:29:56 AM >> Subject: [Release-team] deployment errors >> >> How much this impacts the deployment remains to be seen, I haven't >> ran through each module yet >> but I'm getting errors on deployment, looks like mac DMG support? >> >> make: [deploy-user-env] Error 1 (ignored) >> echo "export PYTHONPATH=$q\$KB_PERL_PATH:\$PYTHONPATH$q" >> $dest; >> /bin/sh: cannot create >> /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory >> nonexistent >> /bin/sh: cannot create >> /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory >> nonexistent >> /bin/sh: cannot create >> /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory >> nonexistent >> /bin/sh: cannot create >> /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory >> nonexistent >> /bin/sh: cannot create >> /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory >> nonexistent >> /bin/sh: cannot create >> /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory >> nonexistent >> make: *** [deploy-user-env] Error 2 >> >> >> ---- >> Daniel Murphy-Olson >> Systems Administrator >> Mathematics & Computer Science Division >> Argonne National Laboratory >> 630-252-0055 >> >> _______________________________________________ >> Release-team mailing list >> Release-team(a)lists.kbase.us >> https://lists.kbase.us/mailman/listinfo/release-team >>

1 0

Re: [Release-team] deployment errors
by Robert Olson 25 Jan '13

25 Jan '13

Where are you seeing that? On Jan 25, 2013, at 8:29 AM, Dan Olson wrote: > How much this impacts the deployment remains to be seen, I haven't ran through each module yet > but I'm getting errors on deployment, looks like mac DMG support? > > make: [deploy-user-env] Error 1 (ignored) > echo "export PYTHONPATH=$q\$KB_PERL_PATH:\$PYTHONPATH$q" >> $dest; > /bin/sh: cannot create /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory nonexistent > /bin/sh: cannot create /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory nonexistent > /bin/sh: cannot create /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory nonexistent > /bin/sh: cannot create /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory nonexistent > /bin/sh: cannot create /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory nonexistent > /bin/sh: cannot create /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory nonexistent > make: *** [deploy-user-env] Error 2 > > > ---- > Daniel Murphy-Olson > Systems Administrator > Mathematics & Computer Science Division > Argonne National Laboratory > 630-252-0055 >

1 0

Re: [Release-team] deployment errors
by Dan Olson 25 Jan '13

25 Jan '13

Ok.. This completely broke deployment. For all modules. I cannot proceed until this is fixed. /kb/deployment doesn't even get created. ----- Original Message ----- > From: "Dan Olson" <dolson(a)mcs.anl.gov> > To: release-team(a)kbase.us > Cc: "Robert Olson" <olson(a)mcs.anl.gov> > Sent: Friday, January 25, 2013 8:29:56 AM > Subject: [Release-team] deployment errors > > How much this impacts the deployment remains to be seen, I haven't > ran through each module yet > but I'm getting errors on deployment, looks like mac DMG support? > > make: [deploy-user-env] Error 1 (ignored) > echo "export PYTHONPATH=$q\$KB_PERL_PATH:\$PYTHONPATH$q" >> $dest; > /bin/sh: cannot create > /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory > nonexistent > /bin/sh: cannot create > /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory > nonexistent > /bin/sh: cannot create > /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory > nonexistent > /bin/sh: cannot create > /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory > nonexistent > /bin/sh: cannot create > /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory > nonexistent > /bin/sh: cannot create > /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory > nonexistent > make: *** [deploy-user-env] Error 2 > > > ---- > Daniel Murphy-Olson > Systems Administrator > Mathematics & Computer Science Division > Argonne National Laboratory > 630-252-0055 > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team >

1 0

deployment errors
by Dan Olson 25 Jan '13

25 Jan '13

How much this impacts the deployment remains to be seen, I haven't ran through each module yet but I'm getting errors on deployment, looks like mac DMG support? make: [deploy-user-env] Error 1 (ignored) echo "export PYTHONPATH=$q\$KB_PERL_PATH:\$PYTHONPATH$q" >> $dest; /bin/sh: cannot create /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory nonexistent /bin/sh: cannot create /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory nonexistent /bin/sh: cannot create /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory nonexistent /bin/sh: cannot create /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory nonexistent /bin/sh: cannot create /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory nonexistent /bin/sh: cannot create /Volumes/KBase/KBase.app/deployment/user-env.sh: Directory nonexistent make: *** [deploy-user-env] Error 2 ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055

1 0

Re: [Release-team] Where do we stand?
by Dan Olson 25 Jan '13

25 Jan '13

The module owners are supposed to begin changing their docs/code as soon as they are notified. They should have been notified by you or Miriam over the last two days. I'm supposed to start redeploying now. ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055 ----- Nomi Harris <nlharris(a)lbl.gov> wrote: > Dear Release Team, > > I'm looking at the punch list (https://docs.google.com/document/d/1QxZtbKUtAp_7Dj6ArEEaQvUcyl92xn80PzIVm_K…) and it's unclear to me where we are. Has step 4 (redeploy/test) happened yet? > > Starting Thursday morning, merges into the master branch at git.kbase.us are allowed that address issues raised by tech documentation review. This should be completed by noon on Thursday. > Am I supposed to notify the owners of the modules that failed tech docs to do this, or is this part of some general mailing that's sent out about when developers are allowed to merge changes? > > Thanks, > Nomi >

1 0

Where do we stand?
by Nomi Harris 24 Jan '13

24 Jan '13

Dear Release Team, I'm looking at the punch list (https://docs.google.com/document/d/1QxZtbKUtAp_7Dj6ArEEaQvUcyl92xn80PzIVm_K…) and it's unclear to me where we are. Has step 4 (redeploy/test) happened yet? Starting Thursday morning, merges into the master branch at git.kbase.us are allowed that address issues raised by tech documentation review. This should be completed by noon on Thursday. Am I supposed to notify the owners of the modules that failed tech docs to do this, or is this part of some general mailing that's sent out about when developers are allowed to merge changes? Thanks, Nomi

1 0

Re: [Release-team] Self-cc behavior of [email protected]
by Dan Olson 24 Jan '13

24 Jan '13

Nomi, you do have nodupes set (actually it's set by default) http://support.tigertech.net/mailman-nodupes Did you try turning this off? ----- Original Message ----- > From: "Nomi Harris" <nlharris(a)lbl.gov> > To: "Miriam L. Land" <landml(a)ornl.gov> > Cc: release-team(a)lists.kbase.us > Sent: Thursday, January 24, 2013 10:41:51 AM > Subject: Re: [Release-team] Self-cc behavior of release-team(a)lists.kbase.us > > Thanks, Miriam. It already has "yes" for "Receive your own posts to > the list?", so that's not it. Maybe it's some filtering that lbl.gov > does. > Nomi > > On Jan 24, 2013, at 5:07 AM, "Land, Miriam L." <landml(a)ornl.gov> > wrote: > > > Nomi, > > > > You can set your personal preferences for each mail list. When you > > get to main page for the list (e.g., > > http://lists.kbase.us/mailman/listinfo/kbase-devel) at the very > > bottom, you enter your email address to change your options and/or > > password. The button has the words 'Unsubscribe or edit options'. > > It is below the option to see the list of subscribers. > > > > Miriam > > > > From: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> > > Date: Thursday, January 24, 2013 1:27 AM > > To: Dan Olson <dolson(a)mcs.anl.gov<mailto:[email protected]>> > > Cc: > > "release-team(a)lists.kbase.us<mailto:[email protected]>" > > <release-team(a)lists.kbase.us<mailto:[email protected]>> > > Subject: [Release-team] Self-cc behavior of > > release-team(a)lists.kbase.us<mailto:[email protected]> > > > > Hi Dan, > > > > The release-team mailing list, like all of our mailing lists, seems > > to default to NOT sending a copy of the message to the sender. I > > find this endlessly frustrating, as I usually DO want to keep a > > copy and forget to cc myself. If no one else minds, would it be > > possible to change the behavior so it DOES send the message back > > to the sender? > > > > Thanks, > > Nomi > > > > _______________________________________________ > Release-team mailing list > Release-team(a)lists.kbase.us > https://lists.kbase.us/mailman/listinfo/release-team >

1 0

Re: [Release-team] Self-cc behavior of [email protected]
by Nomi Harris 24 Jan '13

24 Jan '13

Thanks, Miriam. It already has "yes" for "Receive your own posts to the list?", so that's not it. Maybe it's some filtering that lbl.gov does. Nomi On Jan 24, 2013, at 5:07 AM, "Land, Miriam L." <landml(a)ornl.gov> wrote: > Nomi, > > You can set your personal preferences for each mail list. When you get to main page for the list (e.g., http://lists.kbase.us/mailman/listinfo/kbase-devel) at the very bottom, you enter your email address to change your options and/or password. The button has the words 'Unsubscribe or edit options'. It is below the option to see the list of subscribers. > > Miriam > > From: Nomi Harris <nlharris(a)lbl.gov<mailto:[email protected]>> > Date: Thursday, January 24, 2013 1:27 AM > To: Dan Olson <dolson(a)mcs.anl.gov<mailto:[email protected]>> > Cc: "release-team(a)lists.kbase.us<mailto:[email protected]>" <release-team(a)lists.kbase.us<mailto:[email protected]>> > Subject: [Release-team] Self-cc behavior of release-team(a)lists.kbase.us<mailto:[email protected]> > > Hi Dan, > > The release-team mailing list, like all of our mailing lists, seems to default to NOT sending a copy of the message to the sender. I find this endlessly frustrating, as I usually DO want to keep a copy and forget to cc myself. If no one else minds, would it be possible to change the behavior so it DOES send the message back to the sender? > > Thanks, > Nomi >

1 0