Bug 1051816

What packages or groups did you install with the kickstart? Can you install anaconda.log and packaging.log from this install? (The files are in /tmp during the install or in /var/log/anaconda on the installed system)

Created attachment 849855 [details]
ks.cfg kickstart file used for installation

This is a typical kickstart file for a "big" installation.

I have hidden or substituted the password hashes and ip addresses for privacy reasons. I did this also for the log files (in the next attachments).
I have also removed the %post part of the kickstart file for the same reason (it doesn't change the behaviour of the %package part because %post will run after %package processing).

Created attachment 849856 [details]
anaconda.log from this installation

Created attachment 849857 [details]
anaconda.packaging.log from this installation

Created attachment 849859 [details]
Example: aspell languages packages: installed packages after kickstart

Created attachment 849860 [details]
Example: aspell languages packages: installed packages after explicit adding languages with yum langinstall

After kickstart installation I have done an explicit language installation with "yum langinstall ..." (for the language list see the kickstart file).

The package aspell is an example to see the difference because there are many language packages for aspell available.

Created attachment 849861 [details]
Output of "yum langlist" after explicit installation of the languages listed in ks.cfg with "yum langinstall" (after reboot...)

Gonna kill two birds with one stone here.

First, --instLangs (once it's hooked up in anaconda) isn't intended to act like yum langinstall. The `lang --addsupport' kickstart command should be used for that. --instLangs is intended to set the _install_langs rpm  macro, which *excludes* the languages installed for a given package to the specified list.

But --instLangs isn't actually implemented. Tracking that in bug 156477.

*** This bug has been marked as a duplicate of bug 156477 ***

Thanks for the feedback.
Ok, I understand that --instLangs is not implemented currently.

Now I have tried to use `lang --addsupport' as you have suggested.
But it seems that something is wrong with either yum or the kickstart option "lang".

I have installed Fedora 20 x86_64 using kickstart. I have used the following kickstart option (change to the kickstart file in the attachment):

lang de_DE.UTF-8 --addsupport=af,ar,as,ast,be,bg,bn,br,bs,ca,cs,cy,da,de,el,en,es,et,eu,fa,fi,fo,fr,ga,gl,gu,gv,he,hi,hr,hu,ia,id,is,it,ja,kl,kn,ko,ks,kw,ky,lo,lt,lv,mai,mk,ml,mr,ms,mt,nb,nds,ne,nl,nn,oc,or,pa,pl,pt,ro,ru,se,si,sk,sl,sq,sr,sv,ta,te,th,tl,tr,uk,ur,uz,wa,xh,zh,zu,af_ZA,ar_AE,ar_BH,ar_DZ,ar_EG,ar_IN,ar_IQ,ar_JO,ar_KW,ar_LB,ar_LY,ar_MA,ar_OM,ar_QA,ar_SA,ar_SD,ar_SY,ar_TN,ar_YE,as_IN,ast_ES,be_BY,bg_BG,bn_BD,bn_IN,br_FR,bs_BA,ca_ES,cs_CZ,cy_GB,da_DK,de_AT,de_BE,de_CH,de_DE,de_LU,el_GR,en_AU,en_BW,en_CA,en_DK,en_GB,en_HK,en_IE,en_IN,en_NZ,en_PH,en_SG,en_US,en_ZA,en_ZW,es_AR,es_BO,es_CL,es_CO,es_CR,es_DO,es_EC,es_ES,es_GT,es_HN,es_MX,es_NI,es_PA,es_PE,es_PR,es_PY,es_SV,es_US,es_UY,es_VE,et_EE,eu_ES,fa_IR,fi_FI,fo_FO,fr_BE,fr_CA,fr_CH,fr_FR,fr_LU,ga_IE,gl_ES,gu_IN,gv_GB,he_IL,hi_IN,hr_HR,hu_HU,ia_FR,id_ID,is_IS,it_CH,it_IT,ja_JP,kl_GL,kn_IN,ko_KR,ks_IN,kw_GB,ky_KG,lo_LA,lt_LT,lv_LV,mai_IN,mk_MK,ml_IN,mr_IN,ms_MY,mt_MT,nb_NO,nds_DE,ne_NP,nl_BE,nl_NL,nn_NO,oc_FR,or_IN,pa_IN,pl_PL,pt_BR,pt_PT,ro_RO,ru_RU,ru_UA,se_NO,si_LK,sk_SK,sl_SI,sq_AL,sr_RS,sv_FI,sv_SE,ta_IN,te_IN,th_TH,tl_PH,tr_TR,uk_UA,ur_PK,uz_UZ,wa_BE,xh_ZA,zh_CN,zh_HK,zh_TW,zu_ZA

%packages --ignoremissing --default


In file /var/log/anaconda/anaconda.packaging.log I have found lines like the following. For the complete list, see the new attachment file.

04:06:17,563 DEBUG yum.verbose.plugin: Adding de_DE.UTF-8 to language list
04:06:17,564 DEBUG yum.verbose.plugin: Adding af to language list
04:06:17,564 DEBUG yum.verbose.plugin: Adding ar to language list
04:06:17,564 DEBUG yum.verbose.plugin: Adding as to language list


It seems that all languages listed in lang --addsupport= was recognized by anaconda and used in the kickstart installation (see the list of hunspell-* packages, for example).

But yum tells me that NO languages are installed (empty list, see the following comment):

# yum -d 0 -e 0 langlist
Installed languages:
	German (Germany)
	Spanish (Spain)
	French (France)
	Italian (Italy)
	Polish (Poland)

This tells me that the list was really empty after kickstart installation, because the listed languages are the languages de_DE,en_US,es_ES,fr_FR,it_IT,pl_PL which was installed by a custom script written by myself using the command "yum langinstall LANGUAGE". If you remove these explicit installed languages the list is empty.

It seems that languages packages was installed for packages that was installed at kickstart time, but not for packages that was installed later (after reboot, my scripts install additional packages after the new installed system is running). See the package list for languages de and sv:

# yum -d 0 -e 0 langinfo de
Language-Id=de
  LabPlot-doc-de
  aspell-de
  autocorr-de
  calligra-l10n-de
  drascula-de
  eclipse-nls-de
  gcompris-sound-de
  gimp-help-de
  gnome-getting-started-docs-de
  hunspell-de
  hyphen-de
  kde-i18n-German
  kde-l10n-German
  kicad-doc-de
  libreoffice-langpack-de
  man-pages-de
  mythes-de
  nqc-doc-de
  sagemath-doc-de
  tagainijisho-dic-de
  tkgate-de

# yum -d 0 -e 0 langinfo sv
Language-Id=sv
  LabPlot-doc-sv
  aspell-sv
  autocorr-sv
  calligra-l10n-sv
  eclipse-nls-sv
  gcompris-sound-sv
  gimp-help-sv
  hunspell-sv
  hyphen-sv
  kde-i18n-Swedish
  kde-l10n-Swedish
  libreoffice-langpack-sv
  mythes-sv


After installing languages "sv" with "yum langinstall sv", then the package "tesseract-langpack-swe" was added:

# yum -d 0 -e 0 langinfo sv
Language-Id=sv
  LabPlot-doc-sv
  aspell-sv
  autocorr-sv
  calligra-l10n-sv
  eclipse-nls-sv
  gcompris-sound-sv
  gimp-help-sv
  hunspell-sv
  hyphen-sv
  kde-i18n-Swedish
  kde-l10n-Swedish
  libreoffice-langpack-sv
  mythes-sv


The list of available languages (output of "yum langavailable") tells me that there are other languages available that the system (yum?) thinks that they are not installed (as "yum langlist" differs).

To summarize:

- Kickstart option "lang ... --addsuport=..." works fine during kickstart installation, but the language list is not saved to be available for yum after reboot.

- I still have to add each languages explicit (using "yum langinstall ...") for each desired language after finishing kickstart installation (e.g. after reboot).


Question: Shall we reopen this bug to handle this problem, or shall we (I ?) create a new bug report for this problem ("lang --addsupport")?


PS: A note to the new kickstart option "lang --addsupport":
I would be helpful if changes to kickstart options will be noticed in future release notes too. Now I know that I have to check the wiki diffs of the Anaconda/Kickstart wiki page to see the changes, but other administrators may check only the release notes. Thanks!

Created attachment 867514 [details]
anaconda.packaging.log from the new installation with lang --addsupport=...

(In reply to Edgar Hoch from comment #9)
> Question: Shall we reopen this bug to handle this problem, or shall we (I ?)
> create a new bug report for this problem ("lang --addsupport")?

All anaconda actually does is write the addsupport list to /etc/yum/pluginconf.d/langpacks.conf and lets the yum langpacks plugin do the rest, so I suggest that you open a new bug against yum.

> PS: A note to the new kickstart option "lang --addsupport":
> I would be helpful if changes to kickstart options will be noticed in future
> release notes too. Now I know that I have to check the wiki diffs of the
> Anaconda/Kickstart wiki page to see the changes, but other administrators
> may check only the release notes.

Release notes are mainted separately from anaconda. You can email docs.org or open a bug against the release-notes component under Fedora Documentation.

It probably wouldn't hurt if we noted in the wiki in what version things were added, though.

David, thanks for the information and tips.

I have created bugs #1069976 and #1069985 .

(In reply to David Shea from comment #11)
> All anaconda actually does is write the addsupport list to
> /etc/yum/pluginconf.d/langpacks.conf and lets the yum langpacks plugin do
> the rest, so I suggest that you open a new bug against yum.



I'm going to move this to DNF and target rawhide. It'd be nice to have this working for F22.

(In reply to Matthew Miller from comment #13)
> (In reply to David Shea from comment #11)
> > All anaconda actually does is write the addsupport list to
> > /etc/yum/pluginconf.d/langpacks.conf and lets the yum langpacks plugin do
> > the rest, so I suggest that you open a new bug against yum.
> 
> 
> 
> I'm going to move this to DNF and target rawhide. It'd be nice to have this
> working for F22.


Ok this is bug is kind of a mess at this point. The original report was a misunderstanding of what --instLangs does, which I believe is being clarified in documentation. Then it became a problem of lang --addsupport not being linked up with yum langlist. Anaconda did its part by writing /etc/yum/pluginconf.d/langpacks.conf in the installed system, oh but except we changed something in the meantime and broke it and then we fixed it again, differently, anaconda-22.9-1 and anaconda-21.48.15-1 (astute readers will note the f21 fix went in, like, right now, haha, whoops). So, anaconda does its part, for yum. "what is yum's deal" is in bug 1069976.

So, dnf. We don't anything with dnf-langpacks. I'm going to assume that this is now what the bug is about.

Okay that works for me, although... didn't there also used to be something with setting rpm tsflags in a config file at some point?

(In reply to Matthew Miller from comment #15)
> Okay that works for me, although... didn't there also used to be something
> with setting rpm tsflags in a config file at some point?

That is the first I have heard of it. We set the flag during the transaction but don't save them anywhere.

(In reply to David Shea from comment #16)
> (In reply to Matthew Miller from comment #15)
> > Okay that works for me, although... didn't there also used to be something
> > with setting rpm tsflags in a config file at some point?
> 
> That is the first I have heard of it. We set the flag during the transaction
> but don't save them anywhere.

I think this is from the days of yore. Possibly... pre-anaconda? Oh yes, looks like Jeremy wontfixed putting that back in 2005 with bug #160903.

Okay, trip down memory lane over. I think that the langpack support is probably the better way forward. For now, gross hacks it is.

Just for laughs, I installed a fresh rawhide system to see what dnf thought about langpacks from the start

[anaconda root@localhost /]# dnf langlist
[Errno 2] No such file or directory: u'/var/lib/yum/plugins/langpacks/installed_langpacks'

So, I'm going to ask that dnf-langpacks add a not-crazy config file location and not do anything here until that happens.

(In reply to David Shea from comment #18)
> Just for laughs, I installed a fresh rawhide system to see what dnf thought
> about langpacks from the start
> 
> [anaconda root@localhost /]# dnf langlist
> [Errno 2] No such file or directory:
> u'/var/lib/yum/plugins/langpacks/installed_langpacks'
> 
> So, I'm going to ask that dnf-langpacks add a not-crazy config file location
> and not do anything here until that happens.

This is what used to happen when you work on something which is developed by some person and you don't cc him/her at all. 

Anyway the above problem exists for yum-langpacks also since langlist is added in yum-langpacks but never reported.

I will *re-iterate* /var/lib/yum/plugins/langpacks/installed_langpacks is not a config file.

(In reply to Parag from comment #19)
> (In reply to David Shea from comment #18)
> > Just for laughs, I installed a fresh rawhide system to see what dnf thought
> > about langpacks from the start
> > 
> > [anaconda root@localhost /]# dnf langlist
> > [Errno 2] No such file or directory:
> > u'/var/lib/yum/plugins/langpacks/installed_langpacks'
> > 
> > So, I'm going to ask that dnf-langpacks add a not-crazy config file location
> > and not do anything here until that happens.
> 
> This is what used to happen when you work on something which is developed by
> some person and you don't cc him/her at all. 
> 
> Anyway the above problem exists for yum-langpacks also since langlist is
> added in yum-langpacks but never reported.
> 
> I will *re-iterate* /var/lib/yum/plugins/langpacks/installed_langpacks is
> not a config file.

We're not using it as a config file. The issue of having a file to write to is in bug 1178969, which is assigned to you. I just opened bug 1195325 against dnf for having a configurable plugin config location, since I looked into using /etc/dnf/plugins/langpacks.conf (even if it doesn't do anything yet) and realized that writing to files to /etc is not something anaconda can do. I don't know yet where that discussion will go since it's just started. Presumably once all the pieces are in place, the handling of /var/lib/yum/plugins/langpacks will be handled by dnf-langpacks. In the meantime, anaconda will continue to do what it has been doing regarding dnf and langpacks, which is nothing.

I apologize if you feel you've been left out of the loop, but I'm not sure exactly what the problem is here?

I have not yet read this complete bug comments about langpacks plugin but the problem reported just here is of 
> > [anaconda root@localhost /]# dnf langlist
> > [Errno 2] No such file or directory:
> > u'/var/lib/yum/plugins/langpacks/installed_langpacks'

I find that this occurs when on a fresh installed system users directly run "dnf langlist". I never thought users will do this first. So it is a bug and need to be fixed. Will fix this in next release of {yum/dnf}-langpacks.

Thanks.

Oh, ok, I assumed it was anaconda's fault for not configuring langpacks yet. Sorry for hiding the bug 18 comments down in someone else's bug report.

Note: dnf-langpacks now installing /etc/dnf/plugins/langpacks.conf file. Anaconda need to write languages to this file similarly it is doing for yum-langpacks.

I confirm that this bug is fixed now. Thank you very much David for helping to add langpacks code for dnf-langpacks in anaconda.
Tested with Fedora 23 Alpha Server install DVD that selected additional languages which are getting written in /etc/dnf/plugins/langpacks.conf file.