[7758] in Release_7.7_team
Re: Pushing out printing-config now?
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Fri May 4 16:45:07 2012
Message-Id: <201205042045.q44Kj4gg024649@outgoing.mit.edu>
To: Jonathan Reed <jdreed@MIT.EDU>
cc: Jonathon Weiss <jweiss@MIT.EDU>, release-team@MIT.EDU
In-reply-to: <5FB0A2B0-457A-411A-B354-FEA26E15F93F@mit.edu>
Date: Fri, 04 May 2012 16:45:04 -0400
From: Jonathon Weiss <jweiss@MIT.EDU>
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
>
