Maintainer voiced his opinion, that's IMHO clear: this will not get fixed by a _very_ (and hard to maintain) invasive distribution-specific patch in Debian nor Ubuntu. Unless someone comes with a patch and some guarantees to maintain the patch on the long term, it will just not happen by painting that issue as ridiculous.
That said, there's still some hope for a future solution, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692791#101 from Michael Sweet, upstream author: > *If* we move to a non-editable format in the future (likely for CUPS 2.0) we > will definitely restructure things to put those files in /var/lib. > > I don't advise that you try to patch current CUPS to use /var/lib/cupsd for > cupsd stuff and /etc/cups for everything else since the current code assumes > that all CUPS configuration files are in one location. The patch will be > very very messy and hard to maintain. Cheers, OdyX, with his Debian Printing Team (including some cups fiddling) hat on ** Bug watch added: Debian Bug tracker #692791 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692791 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/301594 Title: FHS violation? Status in CUPS - Common Unix Printing System: Invalid Status in “cups” package in Ubuntu: Opinion Bug description: Binary package hint: cups From the CUPS documentation: 'The CUPS scheduler (cupsd) uses the /etc/cups/subscriptions.conf file to store the list of active subscriptions' /etc/ is an incorrect place to store (what is presumably) transient information like this, surely? To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/301594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp