Hi,
Over the last couple of weeks we had repeatedly commits that broke the dependency chain. This usually results in errors when building the daily iso images. So here's another reminder to be conscious about commits to rocketfuel and especially check depending packages on version upgrades. It usually takes me about 2-3 days to fix all the introduced broken dependencies. Right now we're trying to get a release together. So there should not be a version update unless it's required for a feature we're missing for the release. And even if you do update you should consider the repercussions and include builds of depending packages as well. If you're unsure on how to do that here's a suggested method: Install VirtualBox and install a yoper system that has the standard live cd + the packages you're working on. This way you can safely upgrade your system without breaking your production environment. Next step is to check depending packages. If you've upgraded a package I suggest to use the script in the yoper svn tree : projects/errata/bump-buildreq.sh . ( e.g. : cd ~/yopersvn/3.1/rocketfuel projects/errata/bump-buildreq.sh wireless-tools wireless-tools-devel This will do 2 things, bump the release in the spec file of any matched package that has the package from the argument list in it's build requirements . Collate a nice output for you to either use rrebuild.sh or run straight for a testbuild on the buildserver. ) So please be fair to the rest of the team and me as we're trying to fix things up not break them. Thanks -- Tobias Gerschner Yoper Linux - www.yoper.com Knowing is not enough; we must apply. Willing is not enough; we must do. _______________________________________________ yoper-dev mailing list yoper-dev@lists.yoper.com http://lists.frank-hosting.de/cgi-bin/mailman/listinfo/yoper-dev
