Ticket #1298 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

paludis hangs during install of app-text/po4a

Reported by: markus Owned by:
Priority: Sometime Milestone:
Component: clients/cave Version: 1.4.2
Keywords: Cc: c.apeltauer@…, xiangrong.ma@…
Blocked By: Blocking:
Distribution: Gentoo

Description

Trying to merge app-text/po4a::gentoo results in a non-terminating execution. This is paludis-specific and does not occur with portage. This was first filed as Gentoo Bug #484298. Please advise as to how to proceed.

Attachments

resolve-po4a.log Download (2.9 KB) - added by markus 5 years ago.
build log until paludis hangs
7730-strace.tar.gz Download (30.1 KB) - added by maxr 5 years ago.
strace output of process 7730

Change History

Changed 5 years ago by markus

build log until paludis hangs

comment:1 follow-up: ↓ 2 Changed 5 years ago by ciaranm

You can use 'ps', 'strace' etc to see what's going on. Also, are your Portage and Paludis configs identical (e.g. wrt linguas)?

Changed 5 years ago by maxr

strace output of process 7730

comment:2 in reply to: ↑ 1 Changed 5 years ago by maxr

1:configs are identical. my linguas is :

*/* LINGUAS: -* en_US zh_CN zh_TW zh_HK

2:the related process is:

root      7724  2.3  0.0  54388 18460 pts/2    S+   12:38   0:00 /usr/bin/perl5.16.3 ./Build build

root      7730 96.7  0.0  57492 20780 pts/2    R+   12:38   0:29 perl po4a --previous --no-translations --msgid-bugs-address po4a-devel@lists.alioth.debian.org --package-name po4a --package-version 0.45 po/pod.cfg

3:strace is somehow too large(30MB),the attachment is from

strace -f -o po4a.log cave resolve po4a -x -1
grep ^7730 po4a.log 

where 7730 is the process which hangs

Replying to ciaranm:

You can use 'ps', 'strace' etc to see what's going on. Also, are your Portage and Paludis configs identical (e.g. wrt linguas)?

Last edited 5 years ago by maxr (previous) (diff)

comment:3 Changed 5 years ago by dleverton

I've tracked this down to an issue with determining the PTY width causing po4a's output wrapping to go into an infinite loop, will look into fixing shortly.

comment:4 Changed 5 years ago by dleverton

  • Status changed from new to closed
  • Resolution set to fixed

Fixed in 58560c8. As a workaround until the next release, exporting COLUMNS in the environment with a sensible value before running cave should make it work.

Note: See TracTickets for help on using tickets.