On Mon, 15 Jun 2009 19:13:54 +0200 Thomas Bächler wrote:

Dieter Plaetinck schrieb:

...

error: failed to prepare transaction (could not satisfy dependencies) /core.db.tar.gz: Unsupported scheme. make: *** [core-pkgs] Error 1

According to Aaron, this in an error in URL parsing.

Thanks for both of your mails. Any idea how to fix this issue? Dieter

On Mon, 15 Jun 2009 19:34:39 +0200 Thomas Bächler wrote:

Dieter Plaetinck schrieb:

...

On Mon, 15 Jun 2009 19:13:54 +0200 Thomas Bächler wrote:

...

Dieter Plaetinck schrieb:

...

error: failed to prepare transaction (could not satisfy dependencies) /core.db.tar.gz: Unsupported scheme. make: *** [core-pkgs] Error 1 According to Aaron, this in an error in URL parsing.

Thanks for both of your mails.

Any idea how to fix this issue?

There must be a wrong URL somewhere in the pacman.conf that is generated by mkarchiso.

Hmm my work/root-image/etc/pacman.conf looks quite sane. http://pastebin.ca/1461273 good thing mkarchiso is only 315 lines. i'll poke around a bit. Dieter

On Mon, 15 Jun 2009 20:00:22 +0200 Thomas Bächler wrote:

Dieter Plaetinck schrieb:

...

Hmm my work/root-image/etc/pacman.conf looks quite sane. http://pastebin.ca/1461273

good thing mkarchiso is only 315 lines. i'll poke around a bit.

How sane does the mirrorlist look? Which one does it use anyway? It looks like "/core.db.tar.gz" is the whole URL, so there must be something like an empty Server entry.

Heh. egrep -v '^#|^$' root-image/etc/pacman.d/mirrorlist -> 0 lines. egrep -v '^#|^$' /etc/pacman.d/mirrorlist Server = ftp://mir1.archlinuxfr.org/archlinux/$repo/os/i686 (...)

On Mon, 15 Jun 2009 21:17:04 +0200 Dieter Plaetinck wrote:

On Mon, 15 Jun 2009 20:30:25 +0200 Dieter Plaetinck wrote:

...

On Mon, 15 Jun 2009 20:00:22 +0200 Thomas Bächler wrote:

...

Dieter Plaetinck schrieb:

...

Hmm my work/root-image/etc/pacman.conf looks quite sane. http://pastebin.ca/1461273

good thing mkarchiso is only 315 lines. i'll poke around a bit.

How sane does the mirrorlist look? Which one does it use anyway? It looks like "/core.db.tar.gz" is the whole URL, so there must be something like an empty Server entry.

Heh.

egrep -v '^#|^$' root-image/etc/pacman.d/mirrorlist -> 0 lines.

egrep -v '^#|^$' /etc/pacman.d/mirrorlist Server = ftp://mir1.archlinuxfr.org/archlinux/$repo/os/i686 (...)

Okay, here's the deal (thanks Aaron for the help): packages.list contains pacman. pacman depends on pacman-mirrorlist. pacman-mirrorlist contains /etc/pacman.d/mirrorlist. So when you're building the iso, it will install all the packages listed and their deps. that includes pacman-mirrorlist. the default mirrorlist file now only contains commented-out entries (this has been introduced recently, Aaron told me) When building the images, an overlay is used. the overlay contains a mirrorlist file with some commented out entries (good), but apparently this gets undone by the package.

Now, you have to know that apparently the mirrorlist file used during package building == mirror list file ending up on the livecd, eg the one you'll see at runtime when having the image booted.

I have now tried this quick hack: in mkarchiso, after: _pacman "${PKGLIST}" put: cp /etc/pacman.d/mirrorlist "${work_dir}/root-image/etc/pacman.d/mirrorlist"

but the error stayed exactly the same. stay tuned while i figure this out :)

Dieter

For the interested ones: In the makefile i had to change: ./download-repo.sh core "$(WORKDIR)/core-pkgs" to ./download-repo.sh testing "$(WORKDIR)/core-pkgs" Otherwise it would only use core packages. not good. But now i get `No such file `testing.db.tar.gz'` at the end of download.sh.. stay tuned Dieter

On Wed, 17 Jun 2009 13:14:42 +0200 Gerhard Brauer wrote:

Am Montag, den 15.06.2009, 22:07 +0200 schrieb Dieter Plaetinck:

...

...

I have now tried this quick hack: in mkarchiso, after: _pacman "${PKGLIST}" put: cp /etc/pacman.d/mirrorlist "${work_dir}/root-image/etc/pacman.d/mirrorlist"

but the error stayed exactly the same. stay tuned while i figure this out :)

Dieter

For the interested ones: In the makefile i had to change: ./download-repo.sh core "$(WORKDIR)/core-pkgs" to ./download-repo.sh testing "$(WORKDIR)/core-pkgs"

Otherwise it would only use core packages. not good. But now i get `No such file `testing.db.tar.gz'` at the end of download.sh..

I could not confirm your problems here. Have build a ftp-iso with 2.6.30 without a problem on mirrorlist. I use archiso with the latest commits. Also the change in makefile is not necessary, you have only to activate testing repo in your build-host's pacman.conf and make sure testing is above the other repos (After ISO builing - if you don't have a VM for this - you could disable testing to stay your build-host clean).

Other hint when using such a test-iso: you must also enable testing repo in the installation which you boot with your test iso - otherwise your iso has ex. 2.6.30 and your system will get installed with 2.6.29.

...

stay tuned

Dieter

Gerhard

Hi G I was doing make core-iso, can you try that? i have testing enabled in my real pacman.conf, yet i got these problems. download.sh will by default only core packages, so I don't really understand how you can get the kernel from testing without modifying Btw, my last problem: download.sh downloaded packages first from testing, then core, then extra. so baseurl was set with 'extra' in it. it tried to download http://lalala/extra/.../testing.tar.gz which is incorrect. I also haven't applied your patches yet (http://www.archlinux.org/pipermail/arch-releng/2009-June/000504.html) do we stil need to do this? Dieter

Am Mittwoch, den 17.06.2009, 13:53 +0200 schrieb Gerhard Brauer:

Am Mittwoch, den 17.06.2009, 13:46 +0200 schrieb Dieter Plaetinck:

...

Hi G I was doing make core-iso, can you try that?

Ok, will try this....

Ok, also talked with Dieter on IM. IMHO it's too much work to put testing repo/packages also on a core-iso. We have either to modify dowmload-repo.sh to mix core and testing packages (and build a actual core.db.tar.gz with repo-add therein to get all packages in db). Or we must build own squashfs testing-pkg which get mounted on the iso, but then we must also modify the installer/ais to get this during package installation.... Too much work IMHO.... If we build isos for testing purpose (alpha,private,...) we should build only ftp images. All we have to test could be done easily with these. Core-isos (or RC core-isos) should be build only when we don't need testing packages (most time it's the kernel+depends....) Gerhard

On Thu, 18 Jun 2009 21:48:17 +0200 Dieter Plaetinck wrote:

On Wed, 17 Jun 2009 14:42:29 +0200 Gerhard Brauer wrote:

...

Am Mittwoch, den 17.06.2009, 13:53 +0200 schrieb Gerhard Brauer:

...

Am Mittwoch, den 17.06.2009, 13:46 +0200 schrieb Dieter Plaetinck:

...

Hi G I was doing make core-iso, can you try that?

Ok, will try this....

Ok, also talked with Dieter on IM. IMHO it's too much work to put testing repo/packages also on a core-iso. We have either to modify dowmload-repo.sh to mix core and testing packages (and build a actual core.db.tar.gz with repo-add therein to get all packages in db). Or we must build own squashfs testing-pkg which get mounted on the iso, but then we must also modify the installer/ais to get this during package installation.... Too much work IMHO....

If we build isos for testing purpose (alpha,private,...) we should build only ftp images. All we have to test could be done easily with these. Core-isos (or RC core-isos) should be build only when we don't need testing packages (most time it's the kernel+depends....)

Gerhard

Ugh. When i undid most of my patches (all, except the kernel version in Makefile and slight package changes in packages.list) I could build the ftp-iso but Virtualbox would crash while trying to boot it.

When I undid literally everything I would get: error: 'lshwd': not found in sync db

Which looks fairly obvious to me, since this package is in AUR. Eg i needed these patches to get a few steps further, did you really mean you don't need any changes in the most recent archiso?

Dieter

seems like problem 1 is a vbox problem. (I use virtualbox_bin 2.2.4-1, not ose because i had a lot of problems getting it running on my system) the iso works fine in qemu... So, to conclude you can build 2.6.30 iso's with the latest archiso by enabling testing on your host system, changing the kernel version in Makefile and updating the package.list and running sudo make ftp-iso Dieter