* [http://bcl.fedorapeople.org/scripts/git-changelog git-changelog] A simplified version of dcantrell's [http://git.fedorahosted.org/git/?p=anaconda.git;a=blob;f=scripts/makebumpver;hb=HEAD makebumpver] script, it prints a nice summary of commits since the specified tag, suitable for use in a rpm spec file %changelog section.

+

* [http://bcl.fedorapeople.org/ update images, logs, etc.]

== Anaconda Development ==

== Anaconda Development ==

Development System

Development System

−

* Fedora 12

+

* Fedora 18

−

* squid proxy to cache packages

+

* polipo proxy to cache packages

* lighttpd to serve up updates.img

* lighttpd to serve up updates.img

* tftpd to serve up pxe boot images

* tftpd to serve up pxe boot images

−

* mock + pungi for building

+

* mock or lorax for building packages and iso's

== mock setup ==

== mock setup ==

Line 37:

Line 46:

** <code>mock -r fedora-13-i386 --init</code>

** <code>mock -r fedora-13-i386 --init</code>

** <code>mock -r fedora-13-i386 --no-clean --install pungi</code>

** <code>mock -r fedora-13-i386 --no-clean --install pungi</code>

−

* Enter the chroot - <code> mock -r fedora-13-i386 --shell </code>

+

−

** Edit <code> /usr/lib/anaconda-runtime/buildinstall </code>

+

Now you have a mock chroot environment setup that will use the proxy cache for packages.

−

*** add <code> proxy=http://proxy.home:3128 </code> to the main section of the yum config embedded in it.

Boot your iso with the updates=http://url/of/your/updates.img and change to tty2. Run <code>ip addr</code> to find the IP of the system/virt.

+

+

When Anaconda hits the breakpoint run winpdb on your local system and use File->Attach to connect to the system and start debugging. The password (snakes) is set by the start_embedded_debugger call.

+

+

Anaconda's storage imports appear to interfere with rpdb2's import wrapper so don't expect to be able to step through the whole program, but it is very useful for examining the state of the system and looking at the local variables for all the running threads.

** grab a copy of the current anaconda*src.rpm from someplace and install the dependencies with:

** grab a copy of the current anaconda*src.rpm from someplace and install the dependencies with:

*** <code> yum-builddep anaconda*src.rpm </code>

*** <code> yum-builddep anaconda*src.rpm </code>

Line 127:

Line 159:

Now add <code> updates=http://proxy.home/updates/updates.img </code> to the kernel parameters when booting the install media.

Now add <code> updates=http://proxy.home/updates/updates.img </code> to the kernel parameters when booting the install media.

+

NOTE: By running yum inside the chroot you may mess up the rpmdb version, this depends on how close your host system is to the target system. So YMMV

== Build with a test anaconda.rpm ==

== Build with a test anaconda.rpm ==

Line 134:

Line 167:

Normally when a punji build is done it pulls anaconda from the repo/proxy cache. Instead you want it to use your new build (ie. when doing stage1 development which cannot be updated by updates= being passed to the kernel)

Normally when a punji build is done it pulls anaconda from the repo/proxy cache. Instead you want it to use your new build (ie. when doing stage1 development which cannot be updated by updates= being passed to the kernel)

* make sure mock is mounting your anaconda directory as described above. Again, do not use <code>mount -o bind</code> to do it.

* <code> mock -v -r fedora-13-i386-proxy --shell </code>

* <code> mock -v -r fedora-13-i386-proxy --shell </code>

* <code> cd /root/anaconda </code>

* <code> cd /root/anaconda </code>

* Removed the cached files. Otherwise it pull pull from there and not update to the latest

* Removed the cached files. Otherwise it pull pull from there and not update to the latest

** <code> rm -rf /13 </code>

** <code> rm -rf /13 </code>

−

** <code> rm -rf /extra/released/pungi/cache/local </code>

+

** <code> rm -rf /pungi/cache/local </code>

* <code> ./autogen.sh </code>

* <code> ./autogen.sh </code>

* <code> ./configure </code>

* <code> ./configure </code>

Line 161:

Line 194:

== Update boot.iso with new anaconda rpm ==

== Update boot.iso with new anaconda rpm ==

−

After you have a working boot.iso you can easily update it with the files from the new anaconda rpm you built above. Use the [[http://bcl.fedorapeople.org/scripts/upd_bootiso | upd_bootiso]] script to do this:

+

After you have a working boot.iso you can easily update it with the files from the new anaconda rpm you built above. Use the [[http://git.fedorahosted.org/git?p=anaconda.git;a=blob_plain;f=scripts/upd-bootiso;hb=HEAD upd_bootiso]] script to do this:

<code>upd_bootiso boot.iso anaconda-13.35-1.fc13.i686.rpm</code>

<code>upd_bootiso boot.iso anaconda-13.35-1.fc13.i686.rpm</code>

Line 170:

Line 203:

Note, this script currently only works with x86 due to the fact that I borrowed part of it from the <code>mk-images.x86</code> script and haven't built on other architectures yet.

Note, this script currently only works with x86 due to the fact that I borrowed part of it from the <code>mk-images.x86</code> script and haven't built on other architectures yet.

+

+

== Releasing anaconda ==

+

+

This requires permission to upload new anaconda files and a [https://fedora.transifex.net/projects/p/anaconda/ Transifex account] with access to the Anaconda project. The transifex client needs to be setup on your system. This is described in the [http://git.fedorahosted.org/git/?p=anaconda.git;a=blob;f=docs/transifex.txt;hb=HEAD doc/transifex.txt] file in the anaconda source tree:

+

+

* git clean -d -x -f

+

* <code>./autogen.sh && ./configure</code>

+

** If that fails for deps: <code>yum-builddep anaconda.src.rpm</code>

+

** Alternatively grab the srpm using <code> fedpkg srpm </code> and run yum-builddep on that.

+

* <code> make bumpver </code>

+

* Make sure anaconda.spec.in looks ok

+

* <code> git commit -m "New version." </code>

+

* <code> make release </code>

+

* <code> git push </code>

+

* <code> git push --tags </code>

+

+

In the fedora package then do:

+

* <code> fedpkg switch-branch fXX </code>

+

* Copy the anaconda.spec and anaconda-*tar.gz over to the package directory

+

* Make sure anaconda.spec looks ok

+

* <code> fedpkg new-sources anaconda-XX.XX-X.tar.gz </code>

+

* <code> fedpkg clog </code>

+

* Edit the clog to fix the first line, make it consistent with the "- [text]" changelog entries.

When Anaconda hits the breakpoint run winpdb on your local system and use File->Attach to connect to the system and start debugging. The password (snakes) is set by the start_embedded_debugger call.

Anaconda's storage imports appear to interfere with rpdb2's import wrapper so don't expect to be able to step through the whole program, but it is very useful for examining the state of the system and looking at the local variables for all the running threads.

Building updates

Anaconda includes the ability to update itself by passing updates=http://path/to/update.img to the kernel at boot time. This allows you to use the same boot media and test changes to stage2 of the installer.

This assumes a working mock chroot (ie. I built boot images with this one first)

You need a git repo of Anaconda, I branch for the build so I don't clutter up master with build by-products.

NOTE: By running yum inside the chroot you may mess up the rpmdb version, this depends on how close your host system is to the target system. So YMMV

Build with a test anaconda.rpm

NOTE: This doesn't actually seem to work when the released anaconda version matches that in the branch. buildinstall isn't letting the local repo override the one in the repo

Normally when a punji build is done it pulls anaconda from the repo/proxy cache. Instead you want it to use your new build (ie. when doing stage1 development which cannot be updated by updates= being passed to the kernel)

make sure mock is mounting your anaconda directory as described above. Again, do not use mount -o bind to do it.

mock -v -r fedora-13-i386-proxy --shell

cd /root/anaconda

Removed the cached files. Otherwise it pull pull from there and not update to the latest

NOTE: The removal of the local repo cache is needed because yum gets confused by its presence.

Update boot.iso with new anaconda rpm

After you have a working boot.iso you can easily update it with the files from the new anaconda rpm you built above. Use the [upd_bootiso] script to do this:

upd_bootiso boot.iso anaconda-13.35-1.fc13.i686.rpm

This will extract the files from initrd.img and install.img on the boot.iso, update the files and then re-build the boot.iso

This is considerably faster than using mock + pungi to compose a whole new iso from scratch.

Note, this script currently only works with x86 due to the fact that I borrowed part of it from the mk-images.x86 script and haven't built on other architectures yet.

Releasing anaconda

This requires permission to upload new anaconda files and a Transifex account with access to the Anaconda project. The transifex client needs to be setup on your system. This is described in the doc/transifex.txt file in the anaconda source tree:

git clean -d -x -f

./autogen.sh && ./configure

If that fails for deps: yum-builddep anaconda.src.rpm

Alternatively grab the srpm using fedpkg srpm and run yum-builddep on that.

make bumpver

Make sure anaconda.spec.in looks ok

git commit -m "New version."

make release

git push

git push --tags

In the fedora package then do:

fedpkg switch-branch fXX

Copy the anaconda.spec and anaconda-*tar.gz over to the package directory

Make sure anaconda.spec looks ok

fedpkg new-sources anaconda-XX.XX-X.tar.gz

fedpkg clog

Edit the clog to fix the first line, make it consistent with the "- [text]" changelog entries.