[Pkg-cups-devel] cupsys: bug triaging
Kenshi Muto
kmuto at debian.org
Mon Aug 15 03:00:37 UTC 2005
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Martin and folks,
At Sun, 14 Aug 2005 20:27:42 +0300 (EEST),
Martin-ノric Racine wrote:
> Following the recent flood of bugs (some of which were raised to RC) on cupsys,
> I have taken a quick look at outstanding bugs. We have *that* many bugs? Yikes!
Yep, sorry for my late work. I just backed from busy days.
> ***
> First, the issue that keeps on popping since a few days: the missing dependency
> on 'gs-esp'. Am I correct to assume that the only reason why it is in Recommends
> instead of Depends is because not all printers are of the Postscript variety and
> therefore won't necessarily all require Postscript preprocessing?
Right. It's changed since 1.1.22-0.experimental4.
I got some same bugs/direct mails, "Hey, I don't want gs-esp!!".
> Would it be fair to assume that all modern printer *are* Postscript-compatible
> and to move 'gs-esp' to Depends just to avoid that sort of noisy bug report?
> If yes, then I could logon to SVN and fix this now.
Well, gs-esp is used as pstoraster in CUPS. pstoraster is used by some
PPDs. So, I thought that each PPD deb for CUPS should depend gs-esp, instead
of CUPS depends gs-esp.
But yes, making strict dependency with gs-esp on cupsys is easier.
I'm not against you change dependency.
> ***
> On the more general bug triaging issue, I'd like to ask Kenshi how he wants us
> to proceeed. I suppose that I could immediately prod submitters of bugs dating
> back to Woody to verify whether their old issue still applies, but what else?
It's first time for me to consist a team in Debian.org.
Infrastructure is ready; we have ML and Subversion, and if we want we
can get wiki page on wiki.debian.net or somewhere.
Next step, how to collaborate? Well, I haven't so strong idea.
I'd like to allow each commiters commit when they want. Of course it's
better to negotiate at ML before commit if fix is very big or functional.
Generally, I should make next upload target date and TODO to fix them.
It's too first to upload CUPS 1.2 to unstable, so I think we'll keep 1.1.23.
I think following are rough target for CUPS:
- - solve important bugs if we can.
- - use debconf to maintain cupsd.conf (if we can)
- - LSB? (if we can)
- - library transition. drop libcupsys2-gnutls10, back
libcupsys2. And use gnutls12. (big target)
Thanks,
- --
Kenshi Muto
kmuto at debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iEYEARECAAYFAkMABVIACgkQQKW+7XLQPLHdhgCfdlzLwwP3D4ott/cFjv2KEUtD
7g0AoIavKiua/+gKqF/GEyFsVk3I/yl6
=K5pS
-----END PGP SIGNATURE-----
More information about the Pkg-cups-devel
mailing list