Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3132 - New system install has no pango.modules file.

Attached to Project: Arch Linux
Opened by Anonymous Submitter - Wednesday, 31 August 2005, 00:06 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 02 November 2005, 10:12 GMT
Task Type Bug Report
Category Installation
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

On an ftp install (via cd-base iso 0.7) to fresh hd:

Pango installed, but /etc/pango/pango.modules NOT installed.

This task depends upon

Closed by  arjan timmerman (blaasvis)
Wednesday, 22 March 2006, 23:28 GMT
Reason for closing:  Fixed
Additional comments about closing:  i am sure this is fixed, i had 3 friends install through ftp install with 0.7.1, no problems.
Comment by Jan de Groot (JGC) - Wednesday, 31 August 2005, 17:44 GMT
Did you also get error messages about chroot not being found?

This can't be a pango package issue, since whatever happens in that postinstall, there should be a pango.modules file. The postinstall isn't executed at all on your system.
Comment by Anonymous Submitter - Thursday, 01 September 2005, 03:20 GMT
Please explain why you are asking about an error with "chroot not being found ?"
Comment by Jan de Groot (JGC) - Saturday, 03 September 2005, 23:32 GMT
because most users are not having the "chroot" binary on their system when they install stuff with pacman. Pacman always uses chroot to go to / or whatever you give as -r option to do its .install processing.
Comment by Anonymous Submitter - Sunday, 04 September 2005, 03:57 GMT
I am sorry I do not understand your use of english.

But *IF* I understand you correctly: you are saying that pacman, as used in a fresh install, will not run install scripts such as the one for pango.

O.K.....so this *IS* a bug, in as much as the system install should *not* behave this way by design. <- Please pass this on to whomever would like to fix it.

Very best regards;
Comment by Jan de Groot (JGC) - Tuesday, 06 September 2005, 17:34 GMT
pacman runs fine on a clean install, but it requires the package 'coreutils'. If you didn't install that package on your system, then pacman won't run .install scripts. By default, this package is installed on every system by the installer or the quickinst script, since it is in the base category.
Comment by Anonymous Submitter - Tuesday, 06 September 2005, 20:06 GMT
Huh ?......

Yes the base catagory was installed by the installer. Yes, coreutils is on said and effected system, and was placed there during install. And yes the bug was still there , i.e. no pango.modules file.

Gee Jan, what is it going to take to convince you that this is a real bug that requires squashing ?

Very best regards,
Comment by Jan de Groot (JGC) - Wednesday, 07 September 2005, 19:58 GMT
I am totally unable to reproduce this bug. Installed my system from scratch two days ago, without any problems. The pango.modules file gets created without problems on my system.
Comment by Anonymous Submitter - Wednesday, 07 September 2005, 23:52 GMT
You did do an "ftp" install to a balnk hard drive right ?

Very best regards;

Bob Finch
Comment by Jan de Groot (JGC) - Saturday, 10 September 2005, 22:54 GMT
I installed from the 0.7 CD, did a CD install, then upgraded straight to testing/current/extra without any problems.
Comment by Anonymous Submitter - Sunday, 11 September 2005, 01:50 GMT
Yes Jan, that is undoubtably WHY you had no problems.

To wit: in my very first message on this bug, I pointed out that this was a ftp install (from the 0.7 cd). As such the bug shows up. On the other hand: As you did the install, there well may have been a pango.modules file created during an upgrade cycle. The ftp install would not have such an upgrade cycle.

If you are in charge of the install process, please continue to test, this time reading my first message about this bug to recreate it.

If you are not in charge of the install scripting/process, I would think you should now turn this bug over to whomever is the person assigned to such matters.

Thank you for your attention up until this point.


Very best regards;

Bob Finch

Loading...