[7760] in Release_7.7_team
RE: Pushing out printing-config now?
daemon@ATHENA.MIT.EDU (Anne Silvester)
Fri May 4 17:07:42 2012
From: Anne Silvester <silvesa@MIT.EDU>
To: Jonathon Weiss <jweiss@MIT.EDU>, Jonathan D Reed <jdreed@MIT.EDU>
CC: Jonathon Weiss <jweiss@MIT.EDU>,
"release-team@mit.edu"
<release-team@MIT.EDU>
Date: Fri, 4 May 2012 21:07:33 +0000
Message-ID: <72674087ABE1C74EBCD0AAE2DB83653D107118F6@OC11expo28.exchange.mit.edu>
In-Reply-To: <201205042045.q44Kj4gg024649@outgoing.mit.edu>
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
I agree with Jonathon.
Anne
Anne Silvester
Sr. Manager, Distributed IT Resources
Information Services and Technology, MIT
Office: (617) 324-5912
silvesa@mit.edu
http://ist.mit.edu/about/org/ds
____________________
Important: IS&T IT staff will *NEVER* ask you for your password, nor will MIT send you email requesting your password information. Please continue to ignore any email messages that claim to require you to provide such information.
-----Original Message-----
From: Jonathon Weiss [mailto:jweiss@MIT.EDU]
Sent: Friday, May 04, 2012 4:45 PM
To: Jonathan D Reed
Cc: Jonathon Weiss; release-team@mit.edu
Subject: Re: Pushing out printing-config now?
OK, my gut reaction would be not to push it out until after finals, but I'm willing to be overrulled, or out-voted or whatever.
--
Jonathon
Jonathan Reed <jdreed@MIT.EDU> wrote:
> The change is r25463 (http://diswww.mit.edu/menelaus.mit.edu/source-commits/26223), which should be minimal because:
> - All it does is whine at you on stderr if you're using LPRng syntax
> - It only affects printing invoked via command-line LPRng
>
> It's quite conceivable that some program somewhere tries to call out to 'lpr' and explodes if it sees anything on stderr. But this will not affect any GTK+ printing, or anything that goes directly through the CUPS subsystem, unless users deliberately try to use "Print to LPR". Unaffected programs should include: Firefox, Evince, LibreOffice. Probably unaffected programs include MATLAB and Acrobat.
>
> The backout strategy is revert the commit, rebuild, deploy. Since this is a change to a single package, and not a dependency, and doesn't involve the updater, we should be able to recover within 6 hours of catastrophe.
>
> -Jon
>
>
> On May 3, 2012, at 6:17 PM, Jonathon Weiss wrote:
>
> >
> > What's the risk? If this were to completely explode, would people
> > be unable to print? unable to print via lpr but cups would work?
> > What's the backout strategy in case of disaster?
> >
> > --
> >
> > Jonathon
> >
> >
> >
> > Jonathan Reed <jdreed@MIT.EDU> wrote:
> >
> >> Despite it being well past drop-date, I would really like to push printing-config (from -dev) out now, so that we catch anybody who is still trying to use LPRng. That way we can remove it from the release when we upgrade to Precise. Thoughts?
> >>
> >> The alternative would be to deploy the new printing config this summer, and then pull debathena-lprng from the release over IAP.
> >>
> >> -Jon
>
