I'm gonna decline the nomination to gutsy for this bug because it's a
lot of effort for not much benefit. Since the use of prevu already
strongly relies on backports, the newest versions of prevu are available
in the backports repository. If anyone disagrees feel free to speak up.
--
PREVU
Thank you Fred.
I have installed both the patched prevu and the pbuilder package and
things work fine now :-)
--
PREVU failed under Gutsy
https://bugs.launchpad.net/bugs/157196
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
prevu (1:0.4.2-0ubuntu1) hardy; urgency=low
* New release (LP: #157870)
* Add support for Hardy
* Fix build failure condition on =Gutsy (LP: #157196)
* Add ability to use lp: URL's that get source packages directly
from Launchpad
-- John Dong [EMAIL PROTECTED] Sat, 27 Oct 2007
Chandra :
Here is a patched prevu. You just have to replace the original prevu under
/usr/bin/prevu.
And here is a patched pbuilder package for the bug with
XSBC-Original-Maintainer see :
https://bugs.launchpad.net/ubuntu/+source/prevu/+bug/157196/comments/2
and
** Attachment added: Patched pbuilder package
http://launchpadlibrarian.net/10253771/pbuilder_0.170ubuntu1.1%7E7.10prevu1_all.deb
--
PREVU failed under Gutsy
https://bugs.launchpad.net/bugs/157196
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Fix committed in revision 52 of prevu/dev
** Changed in: prevu (Ubuntu)
Status: New = Fix Committed
--
PREVU failed under Gutsy
https://bugs.launchpad.net/bugs/157196
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I have looked at the code.
The packages created by the pdebuild command are already in the right folder
(/var/cache/prevu/src/{PID}).
So pdebuild doesn't need to copy the packages elsewhere.
But I doesn't understand how PREVU code tells pdebuild to do that.
The pdebuild command line argument do
Prevu uses --use-pdebuild-internal, which implicitly sets the
destination directory to ../ and ignores other directives. Apart from a
minor bug with XSBC-Original-Maintainer in gutsy pbuilder, I have tested
it to work out of the box in Gutsy. However, I cannot guarantee that
non-Ubuntu builds of
In that case, I don't understand what is happening : I am using a fresh Gutsy
install.
I use the original pbuilder : pbuilder 0.170ubuntu1
--
PREVU failed under Gutsy
https://bugs.launchpad.net/bugs/157196
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Hmm let me give another shot at reproducing on a fresh Gutsy -- I built like
10 packages in prevu over the weekend and assumed it worked :)
--
PREVU failed under Gutsy
https://bugs.launchpad.net/bugs/157196
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
John, I just found the following change in prevu code :
http://codebrowse.launchpad.net/~ubuntu-backporters/prevu/dev/revision/43
Here is your comment for that change :
Fix bug where no packages show up after build succeeds.
After --use-pdebuild-internal, pdebuild no longer respects
Thanks for your investigatory work on this. I'll apply a workaround for
pbuilder so that it sets --buildresult explicitly to the working
directory, so that the shutil.move command will work properly (this way
prevu would work with both the case where --buildresult is assumed AND
the cases where
I have experienced the same problem on a fresh Gutsy install:
Output on stdout is:
---
- cleaning the build env
- removing directory /var/cache/prevu/builds/29762 and its subdirectories
cp: cannot create regular file
`/var/cache/pbuilder/result/tex-common_1.9~7.10prevu1.dsc':
13 matches
Mail list logo
