Prevu'ing a package should revert changelog after

Bug #70930 reported by Martin Meredith
2
Affects Status Importance Assigned to Milestone
Prevu
Fix Released
Medium
John Dong

Bug Description

When I've used prevu to test whether a newly (non-uploaded) package backports to edgy, I've had to change the changelog again afterwards so that I can upload the package to feisty...

prevu should revert the changelog, or something similar so that the package is left in the state it was put into prevu

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

+1, prevu shouldn't change the source package in the pwd. I'm going to modify BackportCurrentDir to copy the sources to the build area and do the changelog modification there.

Changed in prevu:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
assignee: nobody → jdong
Revision history for this message
John Dong (jdong) wrote :

Fixed in dev branch

------------------------------------------------------------
revno: 40
revision-id: <email address hidden>
parent: <email address hidden>
committer: John Dong <email address hidden>
branch nick: dev
timestamp: Wed 2006-11-08 15:31:02 -0500
message:
  When backporting current dir, copy it to working_path and build from there. Prevents unwanted changelog edits and extra packages in ../ (Closes bug 70930)

Changed in prevu:
status: Confirmed → Fix Committed
Revision history for this message
John Dong (jdong) wrote :

Fix released to sourceforge in 0.4.1-0ubuntu1

Changed in prevu:
status: Fix Committed → Fix Released
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.