[SATLUG] Debian gpg keys
misteratomic at gmail.com
Sun Jul 8 15:45:24 CDT 2012
Sage advice from Sarge!
On Sun, Jul 8, 2012 at 2:26 PM, Don Wright <satlug at sbcglobal.net> wrote:
> As Sarge says, "If it's stupid but it works, it ain't stupid."
> High pucker factor for sure, but that's probably the best solution right
> short of backing up your custom settings and reinstalling the binaries.
> Just as most airplane crashes happen around takeoffs and landings, the
> testing archive is more likely to break as new release time grows near (as
> or just after release, as that's when packages move from unstable into
> on an expedited basis. [It's also when arguments that have lain untouched
> for a
> year and a half get resumed, but that's just the nature of the beast. And
> somebody always points out that it's been a year-and-a-half, so why...]
> Don Davis wrote:
> >Well, I did something unsafe but it worked...
> >I went ahead and upgraded 700+ packages sans recognized gpg signature...
> >Everything is OK now.... apparently...
> >Oh and the annoying (grammatically incorrect) - "There is XXX packages "
> >KDE message has been fixed. Which I would have fixed if I could figure
> >out how to compile changes to KDE packages.
> Migraine: All the fun of a hangover without the bother of
> getting drunk.
> SATLUG mailing list
> SATLUG at satlug.org
> http://alamo.satlug.org/mailman/listinfo/satlug to manage/unsubscribe
> Powered by Rackspace (www.rackspace.com)
More information about the SATLUG