Custom Query (1145 matches)

Reported by jdreed, 13 years ago.

It is now time to start ramping down support for Hardy. Lucid has been out for 7 months, and Canonical's support for Hardy on the desktop ends in April with the release of Natty.

The most important step here is communication, so we should consider sending mail to debathena-announce early in IAP encouraging users to start investigating upgrades.

I'm aware that "Server" support for Hardy continues into 2013, however discussion at release-team suggests that "Server" does not necessarily mean what we think it means. Regardless, we can stop building for hardy without pulling the archive entirely, right? (Right?)

Reported by jdreed, 13 years ago.

In theory, LPRng queues will no longer exist after June. There is therefore no reason to ever invoke "mit-lpr". I'd like to do a phased transition away from printing-config, with the following stages:

• Eliminate support for LPRng queues, and begin warning when converting LPRng-style arguments
• Break LPRng-style arguments

Until the F5 issues suck less, we still can't use stock CUPS, but hopefully this eliminates some complexity.

Reported by jdreed, 12 years ago.

athinfo generates tracebacks if you pipe its output into a pager. This in turn triggers apport. This is dumb and annoying. Athinfo should gracefully catch and handle KeyboardInterrupt? and IOError (EPIPE, specifically).