Allow lpi to extract information from debian control files to support a package that is not installed

Bug #534968 reported by Philip Peitsch on 2010-03-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
launchpad-integration
Undecided
Unassigned

Bug Description

Currently launchpad-integration (lpi) only supports packages that are installed. This limits the ability to test lpi functionality in an application under development without installing the package.

It would be desirable to allow lpi to extract the information from a source control file (package/debian/control). Ideally, this would be something that could be activated through setting an environment variable or something, such that it could easily be set within a development environment, but deactivated for production code.

I am spending a bit of time looking at this, and may craft a patch hopefully sooner or later. This will help improve the lp integration we're offering in the Quickly dev environment through use of this (lpi) fabulous library.

Related branches

Michael Terry (mterry) wrote :

Whoops, I left off the bug number in my changelog. This is in natty now:

launchpad-integration (0.1.43) natty; urgency=low

  [ Michael Terry ]
  * debian/rules:
    - Fix FTBFS by installing the gtk3 library even on non-i386 builds

  [ Philip Peitsch ]
  * launchpadintegration/packageinfo.py:
    - Allow overriding STATUSFILE by specifying LPI_PACKAGE_FILE env var
  * launchpad-integration.in:
    - Allow overriding PYTHONPATH for easier testing

Changed in launchpad-integration:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers