lp:ubuntu/precise/foomatic-db-engine

Created by James Westby and last modified
Get this branch:
bzr branch lp:ubuntu/precise/foomatic-db-engine
Members of Ubuntu branches can upload to this branch. Log in for directions.

Related bugs

Related blueprints

Branch information

Owner:
Ubuntu branches
Status:
Mature

Recent revisions

43. By Till Kamppeter

* debian/rules: Install the PPD updater without executable bits (644), it
  is not run by itself, but sourced into another script.
* debian/foomatic-db-engine.ppd-updater: Removed unneeded lines. The PPD
  updaters are only include files for shellscripts, not scripts by themselves.

42. By Till Kamppeter

* New upstream release
   - Improved printer entry searh algorithm letting the value of matching
     only manufacturer and model in the device ID bein higher than matching
     the make and model fields of the Foomatic entry but lower than a full
     device ID match and also scoring a printer with actual Foomatic entry
     higher than a printer only known by a driver entry.
   - Handle non-UTF-8 encodings in imported PPD files.

41. By Till Kamppeter

* New upstream release
   - lib/Foomatic/DB.pm: Avoid Perl crashing if a directory of the
     Foomatic database does not contain XML files (Upstream bug #613).
   - Fixed wrong quotes in error message which prevented a variable
     from being substituted by its value (Upstream bug #612).
   - Fixed typos in README (Upstream bug #608).
   - Several fixes and improvements in the build system (Upstream bugs
     #605, #609, and #610).
   - Silenced compiler warnibgs by consistent use of "const" (Upstream
     bug #604).
   - C code improvements (Upstream bugs #599, #600, #601).

40. By Till Kamppeter

* New upstream release
   - Rearranged gcc command line so that linking works with gcc 4.5.x
     (LP: #687973).
   - Allow generating a printer XML files also from more than one PPD file
     for the same printer with only one call of the foomatic-ppd-to-xml
     script.
   - When generating XML files, use exactly the same style as the
     OpenPrinting web server uses on daily synchronization. This avoids
     automatic BZR commits without real changes.
   - Personal comments and optional suppression of automatic driver
     assignments when generating printer XML files from PPDs with
     foomatic-ppd-to-xml.
   - Let the functions of the DB.pm Perl module not abort the whole program
     when a C helper program fails.
   - When generating PPDs with foomatic-ppdfile (also
     /usr/lib/cups/driver/foomatic) handle driver names with a dash (like
     "hpijs-pcl3") correctly.
   - Documented special entities for inserting job parameters into
     renderer command line code snippets, like "&job;", "&user;", "&host;",
     "&title;", "&options;", ...
* debian/patches/db-pm-do-not-die-on-c-helper-failure.patch,
  debian/patches/fix-ppd-generation-for-driver-name-with-dash.patch: Removed
  patches with upstream fixes.

39. By Till Kamppeter

debian/control: Do not recommend foomatic-db at all, as foomatic-db-engine
makes sense without foomatic-db to build packages, especially foomatic-db.
The system-installed foomatic-db-engine can also be used for inplace builds
of PPDs from Foomatic data, pointing to the Foomatic data with the
FOOMATICDB environment variable. This way we can install foomatic-db-engine
easily with apt-get also on desktop installations where foomatic-db cannot
be installed as it conflicts with foomatic-db-compressed-ppds. We put
foomatic-db into Suggests: now.

38. By Till Kamppeter

[ Till Kamppeter ]
* debian/control: Demoted foomatic-db from Depends: to Recommends:. We now
  also use foomatic-db-engine to pre-build the PPDs when building
  foomatic-db.
* debian/patches/db-pm-do-not-die-on-c-helper-failure.patch: Upstream fix
  to let the functions/methods of the DB.pm library not abort the program
  if one of the C helper programs foomatic-combo-xml or foomatic-perl-data
  fails.
* debian/patches/fix-ppd-generation-for-driver-name-with-dash.patch:
  Upstream fix to assure that printer and driver IDs in PPD URIs are
  separated correctly if the driver name contains a dash. Before,
  foomatic:Apollo-P-2100-hpijs-pcl3.ppd got interpreted as printer
  Apollo-P-2100-hpijs and driver pcl3.

[ Didier Raboud ]
* Let dh_link manage the links.

37. By Till Kamppeter

[ Didier Raboud ]
* debian/control: Bumped Standards to 3.9.1.0 without changes needed.
* debian/control, README.Debian: Text corrections.
* debian/foomatic-db-engine.lintian-overrides: Removed dummy lintian
  override.

36. By Till Kamppeter

debian/rules, debian/foomatic-db-engine.install: Corrected manual
installation of the CUPS PPD generator link.

35. By Till Kamppeter

debian/rules: Manually install the CUPS PPD generator link as the
"make install" process does not install it when running on the
build servers.

34. By Till Kamppeter

[ Till Kamppeter ]
* New upstream release
  - foomatic-printermap-to-gutenprint-xml: Use same XML indentation scheme
    as the MySQL data export on the OpenPrinting web site
  - When creating XML files from PPDs, do not add "lj5mono" to the driver
    list any more as this driver entry got removed.
  - Build system fixes.
  - Fixed some hyphen-used-as-minus lintian warnings caused by the man pages.
  - Support for new "fingerprint" parameter for the "<package>" tag.
* debian/patches/fixPerlModulesInstall.patch,
  debian/patches/manpagesFixes.patch: Removed patches for backported
  upstream fixes.
* debian/foomatic-db-engine.install: With the transitional package
  foomatic-filters-ppds re-introduced we need a .install file to tell the
  package build process which files should go into the foomatic-db-engine
  binary package.

[ Didier Raboud ]
* Re-introduce foomatic-filters-ppds as dummy package to ease migration away
  from it (Closes: #588093)
* Putting under Debian Printing Group umbrella.
* Update README.Debian.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:ubuntu/quantal/foomatic-db-engine
This branch contains Public information 
Everyone can see this information.

Subscribers