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 t
Till, would you be willing to explore that option?
** Changed in: cups (Ubuntu)
Status: Won't Fix => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/301594
Title:
FHS violation?
To ma
This is ridiculous.
Upstream is clearly confused about the difference between "state" and
"configuration", but has at least suggested that packages be configured
using --with-serverroot (much like many other daemon packages in
debiuntu).
Please package with this option and stop cups pooping in my
Mike Sweet (upstream author of CUPS) did not accept your suggestion for
two times now. As we do not want to have maintenance nightmares with an
overpatched CUPS (or any other overpatched packages) we try to keep the
packages as close as possible to upstream and therefore we will not
implement your
And filed a new bug upstream, complete with firefox vs itsalltext
fallout:
http://www.cups.org/str.php?L3067
lamont
--
FHS violation?
https://bugs.launchpad.net/bugs/301594
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
Better yet, how about we develop a patch to move the STATE information
out of the CONFIG file, and into /var/lib/cups or so where it properly
belongs, and then file a new bug upstream with the patch, since upstream
decided that they won't fix this bug, since they see no difference
between configura
Agreed. Thanks for sending upstream
** Changed in: cups (Ubuntu)
Importance: Undecided => Low
Status: New => Triaged
--
FHS violation?
https://bugs.launchpad.net/bugs/301594
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have filed this upstream at http://www.cups.org/str.php?L3018 but
Launchpad does not appear to want to link directly to that bug,
presumably because cups use a weird bug tracker that LP does not
recognise.
Either way, I do not thing the bug should be marked Invalid in Ubuntu,
since the bug does
This is an upstream problem of CUPS, not specific to Ubuntu. CUPS will
behave the same way on any other Linux distribution and also on Mac OS
X. Please report this problem on the upstream bug tracker
http://www.cups.org/str.php.
** Changed in: cups (Ubuntu)
Status: New => Invalid
--
FHS