Finally, all the packages included in F20 have been imported into Conary packages. That took rather longer than I had anticipated.
We ran into several interesting issues along the way that we have chronicled here. We have a list of packages that contain conflicting file contents that we should review after we import updates to see whether they have been fixed upstream. I suspect that Fedora wouldn't want to do bug fix releases just for those issues, but they might want to fix them for F21. We just need to determine whether they have been fixed already before reporting them. Next steps: 1) Create groups 2) Create new repository f20.flnx.org 3) Promote packages and groups to f20.flnx.org@f:20 and to f20.flnx.org@f:20-c 4) Start processing updates, building on f20.flnx.org@f:20 5) Modify genmodel to write a model for an F20 system 6) Build an "adoption" tarball and instructions Brett, in order to make that promote work, I think we might need to promote packages by source before we promote the group, because otherwise we'll end up with a huge promote. It took long enough to commit just the texlive build with all its subpackages. I'm guessing that somewhere in mirrorball is code that creates a map from source components to binary packages. Am I right? _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
