more man issues?

more man issues?

[Allen Hewes]

Hi,

Did the recent update(s) clobber a previously existing file or symlink in /etc for man?

$ man man
man: can't open the manpath configuration file /etc/man_db.conf

$ cygcheck -c | grep ^man
man-db                        2.9.3-4                         OK
man-db-create-index           2.9.3-4                         OK
man-db-index-synchronously    2.9.3-4                         OK

$ cygcheck -p man_db.conf
Found 2 matches for man_db.conf
man-db-2.7.6.1-1 - man-db: Man page viewer
man-db-2.9.3-4 - man-db: Man page viewer

$ cygcheck -l man-db | grep '/etc/man_db.conf'
/etc/defaults/etc/man_db.conf

$ uname -a
CYGWIN_NT-10.0 FOUREYES 3.1.7(0.340/5/3) 2020-08-22 17:48 x86_64 Cygwin

On my other not-updated Windows 10 machine, there is an /etc/man_db.conf file. I don't think I put it there (e.g. copy from /etc/defaults).

Shouldn't man "Just Work" post install?

/allen

________________________________

Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.

Re: more man issues?

[ASSI]

Allen Hewes via Cygwin writes:
> Did the recent update(s) clobber a previously existing file or symlink in /etc for man?

The preremove script will remove that file if it's unchanged from the
default.  So that part seems to have worked.

> $ man man
> man: can't open the manpath configuration file /etc/man_db.conf

The postinstall script should have reinstated that file as a copy from
/etc/defaults/etc/man_db.conf.  Can you check if you've got an error in
/var/log/setup.log.full from /etc/postinstall/man-db.sh and what it was?
You should be able to re-install man-db to have that script run again.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

RE: more man issues?

[Allen Hewes]

>
> The postinstall script should have reinstated that file as a copy from
> /etc/defaults/etc/man_db.conf.  Can you check if you've got an error in
> /var/log/setup.log.full from /etc/postinstall/man-db.sh and what it was?
> You should be able to re-install man-db to have that script run again.
>

2021/01/05 09:53:46 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/0p_update-info-dir.dash"
2021/01/05 09:53:47 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/man-db.sh"
2021/01/05 09:53:47 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/man-db-create-index.dash"
2021/01/05 09:53:47 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/man-db-index-synchronously.dash"
2021/01/05 09:53:48 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_adwaita-icon-theme.sh"
2021/01/05 09:53:48 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_desktop-file-utils.sh"
2021/01/05 09:53:48 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_fontconfig_cache_1.sh"
2021/01/05 09:53:50 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/zp_fontconfig_dtd.dash"
2021/01/05 09:53:50 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_glib2.0.sh"
2021/01/05 09:53:50 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_hicolor-icon-theme.sh"
2021/01/05 09:53:50 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/zp_man-db-update-index.dash"
  ManDB index update starting...
  ... ManDB index update complete.
/etc/postinstall/zp_man-db-update-index.dash: 14: exec: 3: not found
2021/01/05 09:56:07 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/zp_shared-mime-info.sh"
2021/01/05 09:56:08 Changing gid to Administrators

I ran C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/man-db.sh" manually at a bash prompt and I got back the /etc/man_db.conf file.

I don't know if this has any bearing, but there's *.done files for the post install man scripts:
ls -al /etc/postinstall/ | grep man
-rwxr-xr-x  1 allen Domain Users  258 Jan  7 14:44 man-db.sh*
-rwxr-xr-x  1 allen Domain Users  258 Jan  4 09:55 man-db.sh.done*
-rwxr-xr-x  1 allen Domain Users   78 Jan  7 14:44 man-db-create-index.dash*
-rwxr-xr-x  1 allen Domain Users   78 Jan  4 09:55 man-db-create-index.dash.done*
-rwxr-xr-x  1 allen Domain Users   56 Jan  7 14:44 man-db-index-synchronously.dash*
-rwxr-xr-x  1 allen Domain Users   56 Jan  4 09:55 man-db-index-synchronously.dash.done*
-rwxr-xr-x  1 allen Domain Users  775 Jan  7 14:44 zp_man-db-update-index.dash*

/allen

________________________________

Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.

Re: more man issues?

[ASSI]

Allen Hewes via Cygwin writes:
> 2021/01/05 09:53:50 running: C:\cygwin64\bin\dash.exe "/etc/postinstall/zp_man-db-update-index.dash"
>   ManDB index update starting...
>   ... ManDB index update complete.
> /etc/postinstall/zp_man-db-update-index.dash: 14: exec: 3: not found

That indicates you didn't install the latest version of the package yet,
although that doesn't explain what happened to the configuration file.

> I ran C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/man-db.sh" manually at a bash prompt and I got back the /etc/man_db.conf file.

Please update to the latest version of man-db so you get the bugfixed
perpetual postinstall file.

> I don't know if this has any bearing, but there's *.done files for the
> post install man scripts:

That is basicall to give you a hint of what has been done before the
latest install (if anything).  Not sure if that is still useful, but in
any case that isn't an issue here.

> -rwxr-xr-x  1 allen Domain Users   56 Jan  7 14:44 man-db-index-synchronously.dash*

You'll probably want to de-install the man-db-index-synchronously
package so the index update is done in the background.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

RE: more man issues?

[Allen Hewes]

> > 2021/01/05 09:53:50 running: C:\cygwin64\bin\dash.exe
> "/etc/postinstall/zp_man-db-update-index.dash"
> >   ManDB index update starting...
> >   ... ManDB index update complete.
> > /etc/postinstall/zp_man-db-update-index.dash: 14: exec: 3: not found
>
> That indicates you didn't install the latest version of the package yet,
> although that doesn't explain what happened to the configuration file.
>

Based on https://cygwin.com/packages/summary/man-db-src.html, I have the latest installed:
cygcheck -c | grep ^man
man-db                        2.9.3-4                         OK
man-db-create-index           2.9.3-4                         OK

(after removing the man-db-index-synchronously package)

I installed those on 01/07/2021.

> > I ran C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/man-
> db.sh" manually at a bash prompt and I got back the /etc/man_db.conf file.
>
> Please update to the latest version of man-db so you get the bugfixed
> perpetual postinstall file.
>

Meh, while there's churn in the man packaging, I'll either run the postinstall script(s) myself or use MANOPT. I need working man pages.

> > I don't know if this has any bearing, but there's *.done files for the
> > post install man scripts:
>
> That is basicall to give you a hint of what has been done before the latest
> install (if anything).  Not sure if that is still useful, but in any case that isn't an
> issue here.
>
> > -rwxr-xr-x  1 allen Domain Users   56 Jan  7 14:44 man-db-index-
> synchronously.dash*
>
> You'll probably want to de-install the man-db-index-synchronously package
> so the index update is done in the background.

Done:
2021/01/05 09:53:34 Uninstalling man-db-index-synchronously

I also removed the leftovers not handled by setup:
rm -rf /etc/postinstall/man-db-index-synchronously.dash.done

/allen

________________________________

Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.

Re: more man issues?

[ASSI]

Allen Hewes via Cygwin writes:
>> That indicates you didn't install the latest version of the package yet,
>> although that doesn't explain what happened to the configuration file.
>>
>
> Based on https://cygwin.com/packages/summary/man-db-src.html, I have the latest installed:
> cygcheck -c | grep ^man
> man-db                        2.9.3-4                         OK
> man-db-create-index           2.9.3-4                         OK
>
> (after removing the man-db-index-synchronously package)
>
> I installed those on 01/07/2021.

But your setup.log snippet was from January 5… and not setup.log.full as
I had asked about.  I have to go by the things you show, not the things
I don't know about.  :-)


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

RE: more man issues?

[Allen Hewes]

> >
> > (after removing the man-db-index-synchronously package)
> >
> > I installed those on 01/07/2021.
>
> But your setup.log snippet was from January 5… and not setup.log.full as I
> had asked about.  I have to go by the things you show, not the things I don't
> know about.  :-)
>
>

How odd indeed. Those are the last lines by date in the log file...

Cygcheck -c says I have the latest man-db packages installed.

I didn't write it, I'm just an end-user. :shrugs:

/allen

________________________________

Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.

RE: more man issues?

[Allen Hewes]

> > > (after removing the man-db-index-synchronously package)
> > >
> > > I installed those on 01/07/2021.
> >
> > But your setup.log snippet was from January 5… and not setup.log.full
> > as I had asked about.  I have to go by the things you show, not the
> > things I don't know about.  :-)
> >
> >
>
> How odd indeed. Those are the last lines by date in the log file...
>
> Cygcheck -c says I have the latest man-db packages installed.
>
> I didn't write it, I'm just an end-user. :shrugs:
>
> /allen

Gah! I sent you lines from /var/log/setup.log and not /var/log/setup.log.full because the later had no lines in it for man-db.

Now that I know what to look for, my other machines don't have this man-db update. I'll check those and report back if I find anything.

/allen

________________________________

Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.