Packaging of Bugzilla 2.18 in Debian

Alexis Sukrieh sukria at
Tue Jan 18 18:43:48 UTC 2005

* Gervase Markham (gerv at disait :
> This was the thing that (may have) caused the problems with the older 
> package. Probably the best thing for you to do is to get Bugzilla 
> working with the new layout, and then make a list of what you had to 
> change. We can then see if it's possible to parameterise those things in 
> some way.

Well, the very first thing I need to do (and I have no choice here, else
the package would not be Policy compliant), is to split CGIs from other

    - quite everything go in /usr/share/bugzilla (less confusing than
      the old package I think).
    - *.cgi in /usr/lib/cgi-bin/bugzilla
    - and the Bugzilla/ dir in /usr/share/perl5/Bugzilla

If this is an effort for you to change the way tempaltes work,
nevermind, I can make a patch and keep it as a patch file. When building
the package, the build process will then first apply the patch.

That would allow us to keep the same source tree.

The only thing I need to know is if this is possible only by patching
the template files?

Moreover, I noticed that the CVS dirs and files are provided by the
official 2.18 tarball. For the debian package to be lintian valid, CVS
files must be removed. Is it necessary to keep them in the tarball?

Using a cvs export can provide a nice tarball without the CVS stuff
inside ;)



                                  Alexis Sukrieh <sukria at>

« Quidquid latine dictum sit, altum sonatur. » 
Whatever is said in Latin sounds profound.

More information about the developers mailing list