smime.p7s
Comments about this user:
No comment entered about this user This user's 10 highest priority tickets:
|
|
| # | Tue Jun 09 12:49:56 2009 | burt@fnal.gov - Ticket created | [Reply] | |||||||||
Just in time to miss the glexec security release we have GIP 1.1.2! - B Changelog: * Include both old (voname) and new (VO:voname) ABCRs in GlueSA ACBRs * Now correctly identify the default SE to eliminate false "UNKNOWN" values for the Classic SE * Fixed setting clusters and cesebind in config_ini and blank acbrs in the SA * Fix to allow multiple SE's for a single CE * Added new unittests for CESEBind and Cluster overides * Unittests now will run without any outside configuration dependencies |
||||||||||||
| # | Tue Jun 09 13:19:32 2009 | roy - Taken | ||
| # | Tue Jun 09 13:20:37 2009 | roy - Correspondence added | [Reply] | |
|
On Tue Jun 09 12:49:56 2009, burt@fnal.gov wrote: > Just in time to miss the glexec security release we have GIP 1.1.2! Well, it's just as well not to blend security updates with non-security updates. Just to clarify: 1) This should go into VDT 1.10.1 and VDT 2.0.0, right? 2) How urgent is the update? Should it go out when it's convenient, or should I push it out soon? Thanks, -alain |
||||
| # | Tue Jun 09 13:20:37 2009 | RT_System - Status changed from 'new' to 'open' | ||
| # | Tue Jun 09 14:23:56 2009 | burt@fnal.gov - Correspondence added | [Reply] | |||||||||
Alain Roy via RT wrote: > On Tue Jun 09 12:49:56 2009, burt@fnal.gov wrote: >> Just in time to miss the glexec security release we have GIP 1.1.2! > > Well, it's just as well not to blend security updates with non-security > updates. > > Just to clarify: > > 1) This should go into VDT 1.10.1 and VDT 2.0.0, right? > 2) How urgent is the update? Should it go out when it's convenient, or > should I push it out soon? Yes, 1.10.1. Soon. Some parts of SE publishing are broken without one of the patches in this release. - B |
||||||||||||
| # | Tue Jun 09 15:51:56 2009 | roy - Correspondence added | [Reply] | |||||||||
Burt-- I didn't see an attachment. Can you send us the tarball, or point us to where we can find it? Thanks, -alain |
||||||||||||
| # | Tue Jun 09 15:52:23 2009 | roy - Correspondence added | [Reply] | |||||||||
On Jun 9, 2009, at 2:23 PM, burt@fnal.gov via RT wrote: > Yes, 1.10.1. > Soon. Some parts of SE publishing are broken without one of the > patches > in this release. OK. We'll give the glexec update a few days to settle, then release it. -alain |
||||||||||||
| # | Tue Jun 09 15:56:23 2009 | burt@fnal.gov - Correspondence added | [Reply] | |||||||||
Alain Roy via RT wrote: > Burt-- > > I didn't see an attachment. Can you send us the tarball, or point us > to where we can find it? Right, of course. http://home.fnal.gov/~burt/gip/gip_1_1_2.tgz - B |
||||||||||||
| # | Tue Jun 09 16:34:44 2009 | roy - Comments added | [Reply] | |||||||
Commit comment: Updated GIP from 1.1.1 to 1.1.2. Changed files: U vdt/branches/vdt-1.10.1/defs To generate a diff: svn diff -c 9347 file:///p/vdt/workspace/svn |
||||||||||
| # | Tue Jun 09 16:42:55 2009 | roy - Correspondence added | [Reply] | |||||||||
Hi Burt, We have the new GIP in a test cache: pacman -get http://vdt.cs.wisc.edu/vdt_11099_cache:Generic-Information-Provider Let me know if you find any problems. By the way: how do I verify from an unpackaged GIP distribution what version I have? I didn't find the version number anywhere, but maybe I didn't look hard enough. Thanks, -alain ----------------------------------------------------------------- Alain Roy vdt-support@opensciencegrid.org VDT Support http://vdt.cs.wisc.edu/support.html |
||||||||||||
| # | Tue Jun 09 16:45:32 2009 | roy - Comments added | [Reply] | |||||||
Commit comment: Updated GIP from 1.1.1 to 1.1.2. Changed files: U vdt/branches/vdt-2.0.0/defs To generate a diff: svn diff -c 9348 file:///p/vdt/workspace/svn |
||||||||||
| # | Tue Jun 09 16:46:23 2009 | roy - Comments added | [Reply] | |||||||
Commit comment: Updated Generic-Information-Provider's revision number to 3 to match release. Changed files: U vdt/branches/vdt-2.0.0/Generic-Information-Provider/defs To generate a diff: svn diff -c 9349 file:///p/vdt/workspace/svn |
||||||||||
| # | Tue Jun 09 16:55:23 2009 | burt@fnal.gov - Correspondence added | [Reply] | |||||||||
Alain Roy via RT wrote: > Hi Burt, > > We have the new GIP in a test cache: > > pacman -get http://vdt.cs.wisc.edu/vdt_11099_cache:Generic-Information-Provider > > Let me know if you find any problems. > > By the way: how do I verify from an unpackaged GIP distribution what > version I have? I didn't find the version number anywhere, but maybe I > didn't look hard enough. We don't have a way to currently do that. I can add it into the release process easily though -- what's your preferred method? One-line textfile in gip/etc ok ? - B |
||||||||||||
| # | Tue Jun 09 16:57:23 2009 | burt@fnal.gov - Correspondence added | [Reply] | |||||||||
Alain Roy via RT wrote: > Hi Burt, > > We have the new GIP in a test cache: > > pacman -get http://vdt.cs.wisc.edu/vdt_11099_cache:Generic-Information-Provider > > Let me know if you find any problems. > > By the way: how do I verify from an unpackaged GIP distribution what > version I have? I didn't find the version number anywhere, but maybe I > didn't look hard enough. Actually, we do capture the changeset # from the SVN repository, so it is possible to do a grep Revision gip/providers/osg_info_gip_version.py and backtrack to the GIP version (3120 = 1.1.2, etc -- see http://t2.unl.edu:8094/browser/gip/tags) - B |
||||||||||||
| # | Tue Jun 09 16:59:21 2009 | roy - Correspondence added | [Reply] | |||||||||
On Jun 9, 2009, at 4:55 PM, burt@fnal.gov via RT wrote: > We don't have a way to currently do that. I can add it into the > release > process easily though -- what's your preferred method? One-line > textfile in gip/etc ok ? I don't have a strong preference. I just figured I would double-check that the tarball you gave me corresponded to version 1.1.2 and realized that I couldn't do it. Thanks, -alain |
||||||||||||
| # | Tue Jun 09 16:59:55 2009 | roy - Correspondence added | [Reply] | |||||||||
On Jun 9, 2009, at 4:57 PM, burt@fnal.gov via RT wrote: > Actually, we do capture the changeset # from the SVN repository, so it > is possible to do a > > grep Revision gip/providers/osg_info_gip_version.py > > and backtrack to the GIP version (3120 = 1.1.2, etc -- see > http://t2.unl.edu:8094/browser/gip/tags) If a user ever wanted to verify that they had the correct version of the GIP, that would be the complex and roundabout way to do it. :) -alain |
||||||||||||
| # | Tue Jun 09 17:02:23 2009 | burt@fnal.gov - Correspondence added | [Reply] | |||||||||
Alain Roy via RT wrote: > On Jun 9, 2009, at 4:57 PM, burt@fnal.gov via RT wrote: >> Actually, we do capture the changeset # from the SVN repository, so it > >> is possible to do a >> >> grep Revision gip/providers/osg_info_gip_version.py >> >> and backtrack to the GIP version (3120 = 1.1.2, etc -- see >> http://t2.unl.edu:8094/browser/gip/tags) > If a user ever wanted to verify that they had the correct version of > the GIP, that would be the complex and roundabout way to do it. :) The good news is that as of GIP 1.1 we do publish the vdt-version of GIP as well as the SVN tag number. So we can tell from here on out what version people are running without having to even bother the site admin - B |
||||||||||||
| # | Tue Jun 09 17:22:55 2009 | roy - Correspondence added | [Reply] | |||||||||
On Jun 9, 2009, at 5:02 PM, burt@fnal.gov via RT wrote: > The good news is that as of GIP 1.1 we do publish the vdt-version of > GIP > as well as the SVN tag number. So we can tell from here on out what > version people are running without having to even bother the site > admin But the question is whether the thing I ship matches the version I claim it to be. -alain |
||||||||||||
| # | Wed Jun 10 09:14:14 2009 | burt@fnal.gov - Correspondence added | [Reply] | |||||||||
Alain Roy via RT wrote: > On Jun 9, 2009, at 5:02 PM, burt@fnal.gov via RT wrote: >> The good news is that as of GIP 1.1 we do publish the vdt-version of > >> GIP >> as well as the SVN tag number. So we can tell from here on out what >> version people are running without having to even bother the site >> admin > But the question is whether the thing I ship matches the version I > claim it to be. Right. I'll add a small textfile to gip/etc for future releases. - B |
||||||||||||
| # | Wed Jun 10 10:29:22 2009 | roy - Correspondence added | [Reply] | |||||||||
On Jun 10, 2009, at 9:14 AM, burt@fnal.gov via RT wrote: > Alain Roy via RT wrote: >> On Jun 9, 2009, at 5:02 PM, burt@fnal.gov via RT wrote: >>>> The good news is that as of GIP 1.1 we do publish the vdt-version of >>>>> GIP >>> as well as the SVN tag number. So we can tell from here on out what >>> version people are running without having to even bother the site >>> admin >> But the question is whether the thing I ship matches the version I >> claim it to be. > Right. I'll add a small textfile to gip/etc for future releases. Sounds great. Thanks! -alain |
||||||||||||
| # | Tue Sep 15 13:03:26 2009 | kronenfe - Comments added | [Reply] | |
|
Cleaning up old tickets. We released GIP 1.1.2 in VDTs 1.10.1y and 2.0.0p3 (although it has since been superseded by a newer version) |
||||
| # | Tue Sep 15 13:03:27 2009 | kronenfe - Status changed from 'open' to 'resolved' | ||
Time to display: 2.969918
»|« RT 3.8.2 Copyright 1996-2008 Best Practical Solutions, LLC.