If so, probably an old file in my /etc. If so, you're right Savvas. Invaliding
the bug.
Thanks for the help!
Igor Gomes
** Changed in: pbuilder (Ubuntu)
Status: In Progress => Invalid
--
pbuilder: Invalid Release file, no valid components
https://bugs.launchpad.net/bugs/364808
You rec
And I think that in order to properly use --othermirror I think you need
--override-config *before* each call:
sudo pbuilder create --override-config --distribution jaunty
--othermirror "deb http://br.archive.ubuntu.com/ubuntu jaunty main
restricted multiverse universe"
--
pbuilder: Invalid Rele
You probably kept your /etc/ (?)
This is a clean install (formatted root "/" partition, except my "/home"
partition) of the most current daily ubuntu iso (yesterday's):
$ cat /etc/pbuilderrc
# this is your configuration file for pbuilder.
# the file in /usr/share/pbuilder/pbuilderrc is the defaul
I got the reason:
There's a pbuilder config file on /etc/pbuilderrc that defines the
incorrect repository on Canonical (http://archive.canonical.com/ubuntu).
It contains only "partner" for Jaunty.
By changing it to http://archive.ubuntu.com/ubuntu, it works perfectly
as expected (sudo pbuilder c
Again, this is NOT a bug in ubuntu-dev-tools. At most it is in pbuilder,
debootstrap or some other package.
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: In Progress => Invalid
** Changed in: pbuilder (Ubuntu)
Status: New => In Progress
** Changed in: pbuilder (Ubuntu)
Assi
Sorry Savvras! I was working on the bug report and the debugging. Exactly, it
works indeed.
So, as workaround:
sudo pbuilder --create --distribution jaunty --components "main
restricted universe multiverse" --mirror
"http://br.archive.ubuntu.com/ubuntu";
Instead of using the othermirrors optio
I've debugged the whole procedure and got the following:
If started as I stated on the bug I got the attached debug trace. Notice
the comparison (my command/debug line):
pbuilder create --distribution jaunty --othermirror "deb
http://br.archive.ubuntu.com/ubuntu/ jaunty main restricted multiver
Igor, did you see the command I said above?
try this one, it does what you need (create a jaunty pbuilder for
http://br.archive.ubuntu.com/ubuntu):
sudo pbuilder --create --distribution jaunty --components "main restricted
universe multiverse" --mirror "http://br.archive.ubuntu.com/ubuntu";
--
Debugged.
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: Confirmed => In Progress
--
pbuilder: Invalid Release file, no valid components
https://bugs.launchpad.net/bugs/364808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I've done a clean install and performed the same command. All packages updated.
All most recent ones.
igorgo...@guarana ~> apt-cache policy pbuilder debootstrap
pbuilder:
Installed: 0.183ubuntu1
Candidate: 0.183ubuntu1
Version table:
*** 0.183ubuntu1 0
500 http://br.archive.ubuntu
Try this:
sudo pbuilder --create --distribution jaunty --components "main restricted
universe multiverse" --mirror "http://br.archive.ubuntu.com/ubuntu";
--
pbuilder: Invalid Release file, no valid components
https://bugs.launchpad.net/bugs/364808
You received this bug notification because you a
BTW:
igorgo...@guarana ~> apt-cache policy debootstrap
debootstrap:
Installed: 1.0.12
Candidate: 1.0.12
Version table:
*** 1.0.12 0
500 http://br.archive.ubuntu.com jaunty/main Packages
100 /var/lib/dpkg/status
This is the latest one available.
Igor Gomes
--
pbuilder: I
> Are you on Jaunty? If not, you probably need a newer version of package
> "debootstrap".
Yes I'm... With all latest updates Siegfried... Any hints?
Igor Gomes
--
pbuilder: Invalid Release file, no valid components
https://bugs.launchpad.net/bugs/364808
You received this bug notification becau
This is not a bug in ubuntu-dev-tools.
Are you on Jaunty? If not, you probably need a newer version of package
"debootstrap".
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: New => Invalid
--
pbuilder: Invalid Release file, no valid components
https://bugs.launchpad.net/bugs/364808
You
14 matches
Mail list logo
