Test bug 2

Bug #77846 reported by John Dong
2
Affects Status Importance Assigned to Milestone
Prevu
Invalid
Undecided
Unassigned

Bug Description

lprevu should be used to attempt a backport of compiz.

Revision history for this message
John Dong (jdong) wrote :

This is an automated build message from my prevu client.
BUILD STARTED.
 A build of package 'compiz' has been started. Upon the build finishing, another notification will be sent out with the results.

Revision history for this message
John Dong (jdong) wrote :

This is an automated build message from my prevu client.
BUILD SUCCESS.
 The build has succeeded.

Revision history for this message
John Dong (jdong) wrote :

This is an automated build message from my prevu client.
BUILD STARTED.
 A build of package 'compiz' has been started. Upon the build finishing, another notification will be sent out with the results.

Revision history for this message
John Dong (jdong) wrote :

This is an automated build message from my prevu client.
BUILD STARTED.
 A build of package 'goldfish' has been started. Upon the build finishing, another notification will be sent out with the results.

Revision history for this message
John Dong (jdong) wrote :

This is an automated build message from my prevu client.
BUILD FAILED.
 Unfortunately, the build has failed. Here's the last 10 lines:
I: Building against currently running distro: edgy
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to find a source package for goldfish
Traceback (most recent call last):
  File "/usr/bin/prevu", line 180, in ?
    BackportFromAPT(sys.argv[1],DIST).backport()

Revision history for this message
John Dong (jdong) wrote :

This is an automated build message from my prevu client.
BUILD STARTED.
 A build of package 'bzr' has been started. Upon the build finishing, another notification will be sent out with the results.

Revision history for this message
John Dong (jdong) wrote :

This is an automated build message from my prevu client.
BUILD FAILED.
 Unfortunately, the build has failed. Here's the last 10 lines:
I: Building against specified distro: dapper

...
E: Could not satisfy build-dependency.
 -> unmounting /var/cache/prevu/src/5642 filesystem
 -> unmounting /var/cache/prevu/dapper-debs filesystem
 -> unmounting dev/pts filesystem
 -> unmounting proc filesystem
 -> cleaning the build env
    -> removing directory /var/cache/prevu/builds/5721 and its subdirectories
Traceback (most recent call last):
  File "/usr/bin/prevu", line 180, in ?
    BackportFromAPT(sys.argv[1],DIST).backport()

Changed in prevu:
status: Unconfirmed → Rejected
Revision history for this message
John Dong (jdong) wrote :

This is an automated build message from my prevu client.
BUILD STARTED.
 A build of package 'bzr' has been started. Upon the build finishing, another notification will be sent out with the results.

Revision history for this message
John Dong (jdong) wrote :

This is an automated build message from my prevu client.
BUILD FAILED.
 Unfortunately, the build has failed. Here's the last 20 lines:
I: Building against specified distro: dapper

...
Unpacking pbuilder (from .../pbuilder_0.145ubuntu4.1_all.deb) ...
Setting up wget (1.10.2-1ubuntu1) ...

Setting up debootstrap (0.3.3.0ubuntu8~dapper1) ...
Setting up pbuilder (0.145ubuntu4.1) ...
Setting DEBBUILDOPTS=
 -> Attempting to parse the build-deps : pbuilder-satisfydepends,v 1.22 2005/12/04 05:16:40 dancer Exp $
 -> Considering debhelper (>= 5.0.37.2)
      Tried versions: 5.0.7ubuntu13
   -> Does not satisfy version, not trying
E: Could not satisfy build-dependency.
 -> unmounting /var/cache/prevu/src/5908 filesystem
 -> unmounting /var/cache/prevu/dapper-debs filesystem
 -> unmounting dev/pts filesystem
 -> unmounting proc filesystem
 -> cleaning the build env
    -> removing directory /var/cache/prevu/builds/5983 and its subdirectories
Traceback (most recent call last):
  File "/usr/bin/prevu", line 180, in ?
    BackportFromAPT(sys.argv[1],DIST).backport()

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.