[Pkg-cups-devel] Bug#427559: Bug#427559: cupsd "run as user" changes in 1.2.11-2 breaks existing installations (no printing)

[Martin-Éric Racine]

On 6/5/07, Kurt Pfeifle <kurt.pfeifle at infotec.com> wrote:
> What I indeed did want to make pretty clear are these current facts:
>
>  * your current way of upgrading to CUPS 1.2.11-2 from a previous
>    CUPS 1.2.x version breaks currently working installations

Correct and, at this early stage of Lenny development, something to be expected.


>  * if you do not change $whatever (code, documentation, buildtime
>    configure, startup script, postinstall-script, $wildcard) by the
>    time this upgrade happens in next stable, your users may be hit
>    quite unprepared by some printing b0rkenness

They will not, since the development cycle for Lenny leaves us with
enough time to iron things out.

> > In which case it's just a test server, not a system running a number
> > of  scripts and filters they noticably depend upon.
>
> They do not yet depend on these scripts and filters; but they will,
> once they migrate to Linux. And their decision to migrate will heavily
> depend on how well the current tests and pilots work.

Evaluating the relevance of migrating to Free Software based on the
constantly moving target that is Testing/Unstable is rather crazy, but
whatever... Their choice.

> > Start by triaging the bugs currently open against the package.
>
> In case you did not notice: I *did* already start. Last night. Even
> before I sent my first reply to you in this thread. And I suggested
> to close the bug in question (Bug #259774).

Good thing. Thank you for that. Would you care to run through the list
of open bugs against CUPS and regroup those pertaining to "my printer
doesn't work anymore" with a usertag of your choice?


> I'd like to see as little changes compared to upstream pristine sources
> as possible. Especially, if they are undocumented for the end user.

Documentation usually happens later in a Debian release's development
cycle. To expect this to be fully documented already at a stage where
we barely got these changes into Testing is just plain silly.


> Especially if they change some fundamental behaviour of the software.
> Especially if they do not explain how to get back the original behaviour.
> Especially if they disallow to get back the original behaviour.

Those choices tend to be explained in README.Debian, when they occur.
However, now is not a good time to ask for this documented, as we are
still testing the proper way to package newer CUPS releases.

-- 
Martin-Éric Racine
http://q-funk.iki.fi