This week's URLs:

   The build system:
   to login see:
       kinit <account>@FEDORAPROJECT.ORG
       klist -A

   The account system, login here first?

   The FRYSK package and who is maintaining it:

   Pushing updates (seems to have replaced admin.):

Fixing Fedora so it can do local and remote builds:

- install fedora-packager

For a local native build:

   $ fedpkg compile

To do a scratch build in the build system:

   $ fedpkg srpm
   $ fedpkg scratch-build --srpm BLAH.src.rpm

If you get this:

   $ fedpkg scratch-build ...
   Could not execute scratch_build: [('SSL routines', 'SSL3_READ_BYTES', 'sslv3 alert certificate expired'), ('SSL routines', 'SSL3_READ_BYTES', 'ssl handshake failure')]

try this:

    $ fedora-cert
    Certificate has expired, getting a new one
    FAS Password:

To build in a local chroot aka mock, start with:

    gmake help

Updating the frysk rpm in Fedora (by Sami)

Before doing this make sure you have a fedora account and that your
environment has been set up by following the instructions described

- Check out frysk cvs modules (You probably already did this if you
  have followed the instructions above) But anyhow follow how to set
  up fedora cvs.

- If a tarball has not already been created, follow the instructions
  on the release page:

- Move the created tarball into the frysk cvs directory for distro you
  want to update; for example, for f8 move the tarball to frysk/F-8

- Run make new-sources FILES=frysk-0.4.tar.bz2

  This will upload the tarball to koji so you dont need to upload this
  tarball again.

  It will also update the sources file to point to the newly uploaded

- Edit spec file updating:

  * version
  * release
  * Changelog
  * dependencie's versions
  * etc 

- Clean up patches which have been pushed upstream

  * Remove the patch from cvs
  * delete the patch from the spec file 

- Do a local build with

     make local

  (fix build problems)

- cvs remove/add files then build/commit:

     make clog
     cvs commit
     make tag
     make build

  This should kick off the koji build always make sure that devel is
  newer or as new as the other releases.

  You can now go to the koji webpage to watch the build at:

  also koji will output the specific url to command line you can view
  the output through the web page or using:

      koji watch-logs <ID>

- When the build is done you will be notified

  If the build fails fix it, create a patch and try again other wise
  you are done and must now create an update using the rpm you have

- Go to:

  Click on 'New Update' and push the rpm to the appropriate

Comments welcome