Leap 15.0 oss repo w/odd location (boot/x86_64) for a font repo in primary.xml
In the repodata dir for the oss repo, the primary.xml file usually lists all the packages and their locations for that repo. In the repo D/l area, its listed as some long hex# "<hex#>-primary.xml.gz" in the "oss/repodata/" dir. The rpm package referred to is has name "arphic-uming-fonts" of type "noarch". Files in the oss repo are in the x86_64 or noarch subdirs. One file, a chinese font file (that usually would be under 'noarch') is under "oss/boot/x86_64/". 1) why is a file in the oss repo referring to a "boot" dir? 2) why is a font under an x86_64 dir (under a boot dir) instead of a 'noarch' dir? 2a) Does it have executable code in the rpm package? (unlikely) But why, at least, not under "boot/noarch", but that is given that it is also under some dir named 'boot'. Weird location: <location href="boot/x86_64/arphic-uming-fonts.rpm"/> I don't know about anyone else, but if I look for a pkg in a distro, I usually look under 'oss/x86_64|noarch', never under 'oss/boot/x86_64' for a package with no ver/rel in its pathname. Other data in primary.xml indicates it's version is: <version epoch="0" ver="0.2.20080216.1" rel="lp150.1.7"/> Anyway, likely no big deal, but seemed odd.
On 06/03/2021 21.25, L A Walsh wrote:
In the repodata dir for the oss repo, the primary.xml file usually lists all the packages and their locations for that repo. In the repo D/l area, its listed as some long hex# "<hex#>-primary.xml.gz" in the "oss/repodata/" dir. The rpm package referred to is has name "arphic-uming-fonts" of type "noarch".
Files in the oss repo are in the x86_64 or noarch subdirs.
One file, a chinese font file (that usually would be under 'noarch') is under "oss/boot/x86_64/".
1) why is a file in the oss repo referring to a "boot" dir? 2) why is a font under an x86_64 dir (under a boot dir) instead of a 'noarch' dir? 2a) Does it have executable code in the rpm package? (unlikely) But why, at least, not under "boot/noarch", but that is given that it is also under some dir named 'boot'. Weird location:
<location href="boot/x86_64/arphic-uming-fonts.rpm"/>
I don't know about anyone else, but if I look for a pkg in a distro, I usually look under 'oss/x86_64|noarch', never under 'oss/boot/x86_64' for a package with no ver/rel in its pathname. Other data in primary.xml indicates it's version is: <version epoch="0" ver="0.2.20080216.1" rel="lp150.1.7"/>
Anyway, likely no big deal, but seemed odd.
My guess, it is /also/ needed for boot, and missing elsewhere. Bug? -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On Sat, Mar 06, 2021 at 12:25:11PM -0800, L A Walsh wrote:
In the repodata dir for the oss repo, the primary.xml file usually lists all the packages and their locations for that repo. In the repo D/l area, its listed as some long hex# "<hex#>-primary.xml.gz" in the "oss/repodata/" dir. The rpm package referred to is has name "arphic-uming-fonts" of type "noarch".
Files in the oss repo are in the x86_64 or noarch subdirs.
One file, a chinese font file (that usually would be under 'noarch') is under "oss/boot/x86_64/".
1) why is a file in the oss repo referring to a "boot" dir? 2) why is a font under an x86_64 dir (under a boot dir) instead of a 'noarch' dir? 2a) Does it have executable code in the rpm package? (unlikely) But why, at least, not under "boot/noarch", but that is given that it is also under some dir named 'boot'. Weird location:
<location href="boot/x86_64/arphic-uming-fonts.rpm"/>
I don't know about anyone else, but if I look for a pkg in a distro, I usually look under 'oss/x86_64|noarch', never under 'oss/boot/x86_64' for a package with no ver/rel in its pathname. Other data in primary.xml indicates it's version is: <version epoch="0" ver="0.2.20080216.1" rel="lp150.1.7"/>
Anyway, likely no big deal, but seemed odd.
it is likely needed like this on the installer medium (DVD). There is no specific noarch folder for it for this boot hierarchy on the medium. Ciao, Marcus
On 2021/03/06 22:09, Andrei Borzenkov wrote:
On 07.03.2021 08:58, Marcus Meissner wrote:
it is likely needed like this on the installer medium (DVD).
There is no specific noarch folder for it for this boot hierarchy on the medium.
Do you happen to know where is source for boot/x86_64/config (which references these files)?
--- I'd guess it was on the server. I was only downloading packages listed in: <susebase>/distribution/leap/15.0/repo/oss/repodata/<hexnum>-primary.xml.gz (the non-languaged version), also listed in: <susebase>/distribution/leap/15.0/repo/oss/repodata/repomd.xml so for server download.opensuse.org: http://download.opensuse.org/distribution/leap/15.0/repo/oss/repodata/repomd... lists an oss-based href as: "repodata/71f2322fdc7f69beb4cf24e709ca73eba3a2ce7077df1451b579c3e3871de702-primary.xml.gz" gunzip'ing that file to 'primary.xml', at line #30011 is the beginning of the <package type="rpm"> data for that font. At line #30032 is the location line: <location href="boot/x86_64/arphic-uming-fonts.rpm"/> The next file showing "boot/x86_64/", is cracklib-dict @ #82752, "boot/x86_64/cracklib-dict-full.rpm". My script only downloaded rpms, but a bunch more files in boot/x86_64 can be seen @ http://download.opensuse.org/distribution/leap/15.0/repo/oss/boot/x86_64/ The config file, you asked about is in there as well (attached). root: common root cracklib-dict-full.rpm bind ?yast2-trans-<lang>.rpm ?configfiles rescue: common rescue ?cracklib-dict-full.rpm configfiles: control.xml?copy=1 yast2-trans-ar.rpm: yast2-trans-ar.rpm yast2-trans-bn.rpm: yast2-trans-bn.rpm yast2-trans-gu.rpm: yast2-trans-gu.rpm yast2-trans-hi.rpm: yast2-trans-hi.rpm yast2-trans-ja.rpm: yast2-trans-ja.rpm ipa-gothic-fonts.rpm yast2-trans-km.rpm: yast2-trans-km.rpm yast2-trans-ko.rpm: yast2-trans-ko.rpm un-fonts.rpm?list=*/UnDotum.ttf yast2-trans-mr.rpm: yast2-trans-mr.rpm yast2-trans-pa.rpm: yast2-trans-pa.rpm yast2-trans-si.rpm: yast2-trans-si.rpm yast2-trans-ta.rpm: yast2-trans-ta.rpm yast2-trans-th.rpm: yast2-trans-th.rpm yast2-trans-zh_CN.rpm: yast2-trans-zh_CN.rpm arphic-uming-fonts.rpm yast2-trans-zh_TW.rpm: yast2-trans-zh_TW.rpm arphic-uming-fonts.rpm yast2-trans-ar_EG.rpm: yast2-trans-ar.rpm yast2-trans-bn_BD.rpm: yast2-trans-bn.rpm yast2-trans-bs_BA.rpm: yast2-trans-bs.rpm yast2-trans-cy_GB.rpm: yast2-trans-cy.rpm yast2-trans-et_EE.rpm: yast2-trans-et.rpm yast2-trans-fa_IR.rpm: yast2-trans-fa.rpm yast2-trans-gl_ES.rpm: yast2-trans-gl.rpm yast2-trans-gu_IN.rpm: yast2-trans-gu.rpm yast2-trans-hi_IN.rpm: yast2-trans-hi.rpm yast2-trans-hr_HR.rpm: yast2-trans-hr.rpm yast2-trans-id_ID.rpm: yast2-trans-id.rpm yast2-trans-jv_ID.rpm: yast2-trans-jv.rpm yast2-trans-ka_GE.rpm: yast2-trans-ka.rpm yast2-trans-km_KH.rpm: yast2-trans-km.rpm yast2-trans-ko_KR.rpm: yast2-trans-ko.rpm yast2-trans-lo_LA.rpm: yast2-trans-lo.rpm yast2-trans-lt_LT.rpm: yast2-trans-lt.rpm yast2-trans-mk_MK.rpm: yast2-trans-mk.rpm yast2-trans-mr_IN.rpm: yast2-trans-mr.rpm yast2-trans-pa_IN.rpm: yast2-trans-pa.rpm yast2-trans-ro_RO.rpm: yast2-trans-ro.rpm yast2-trans-si_LK.rpm: yast2-trans-si.rpm yast2-trans-sr_CS.rpm: yast2-trans-sr.rpm yast2-trans-ta_IN.rpm: yast2-trans-ta.rpm yast2-trans-th_TH.rpm: yast2-trans-th.rpm yast2-trans-tr_TR.rpm: yast2-trans-tr.rpm yast2-trans-uk_UA.rpm: yast2-trans-uk.rpm yast2-trans-vi_VN.rpm: yast2-trans-vi.rpm yast2-trans-wa_BE.rpm: yast2-trans-wa.rpm yast2-trans-xh_ZA.rpm: yast2-trans-xh.rpm yast2-trans-zu_ZA.rpm: yast2-trans-zu.rpm
participants (4)
-
Andrei Borzenkov
-
Carlos E. R.
-
L A Walsh
-
Marcus Meissner