Learn more about these different git repos.
Other Git URLs
build_composeinfo -h Usage: build_composeinfo [options] Directory
Options: -h, --help show this help message and exit -n NAME, --name=NAME Alternate name to use, otherwise we use family+version -v, --debug show debug messages -q, --quiet less messages
Directory is the top level directory to hold the .composeinfo file.
Example: [root@amd-dinar-07 16]# ls Everything Fedora Live [root@amd-dinar-07 16]# build_composeinfo Fedora
[root@amd-dinar-07 16]# cat Fedora/.composeinfo [variant-Fedora.x86_64] debuginfo = x86_64/debug os_dir = x86_64/os arch = x86_64 sources = source/SRPMS
[product] variants = Fedora version = 16 name = Fedora-16 family = Fedora
[variant-Fedora.i386] debuginfo = i386/debug os_dir = i386/os arch = i386 sources = source/SRPMS
[variant-Fedora] variants = arches = x86_64,i386 type = variant id = Fedora name = Fedora
script to generate .composeinfo from .treeinfo files. Allows setting a different distro name. like --name=Fedora-17-Beta-RC1 build_composeinfo
thanks, will do some testing with some of the rc trees from f17 beta and will get you to look and make sure that the data you want is all there and correct
http://dl.fedoraproject.org/pub/alt/stage/ can you check the 17-Beta directories. ive run the script and added .composeinfo files to each of the test and release candidate composes and make sure that the data is as you expect.
I noticed one anomaly. I didn't test with a trailing / and that causes a problem.
Following one line patch will fix it.
{{{ [bpeck@localhost bin]$ diff -u build_composeinfo build_composeinfo.1 --- build_composeinfo 2012-04-24 16:25:29.608944863 -0400 +++ build_composeinfo.1 2012-04-25 10:08:28.513179106 -0400 @@ -50,7 +50,7 @@ for treeinfo in treeinfos: logging.debug("treeinfo: %s", treeinfo) # treepath is relative from the composepath. - treepath = treeinfo.replace('/.treeinfo','').replace(composePath,'.') + treepath = treeinfo.replace('/.treeinfo','').replace(composePath,'./')
try: treeInfoParser.read(treeinfo)
}}}
Can you regenerate after that? Thanks!
patch applied and new .composeinfo files made.
Thanks! This worked great. Can you run against http://dl.fedoraproject.org/pub/fedora/linux/releases/test/17-Beta/Fedora/
created for F17 Alpha and Beta, Ill close this ticekt and integrate making .composeinfo into our processes thanks
This ticket is still listed as open. Just to confirm - this is happening for F18 milestones?
It is not happening for Milestones. http://dl.fedoraproject.org/pub/alt/stage/18-Alpha-RC3.1/Fedora/.composeinfo That returns a 404.
But it is happening automatically for development http://dl.fedoraproject.org/pub/fedora/linux/development/18/.composeinfo That returns valid data.
the RC3.1 release was not at all a release. and should not be used at all for anything i am going to go and remove it.
closing this ticket as we are creating .composinfo files for primary arches
Metadata Update from @bpeck: - Issue assigned to ausil - Issue set to the milestone: Fedora 17 Final
Login to comment on this ticket.