Bug 726271 - Regression: Mock does no longer provide ttys required for openpty(3)
Summary: Regression: Mock does no longer provide ttys required for openpty(3)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mock
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Clark Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-28 01:52 UTC by Robert Scheck
Modified: 2011-10-14 03:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-14 03:34:52 UTC
Type: ---


Attachments (Terms of Use)

Description Robert Scheck 2011-07-28 01:52:30 UTC
Description of problem:
Mock does no longer provide ttys required for openpty(3). This causes a
failure of the tests in %check of the mksh package.

Version-Release number of selected component (if applicable):
mock-1.1.8-1

How reproducible:
Everytime, just use mock-1.1.8-1 to rebuild a mksh package that does not
use './test.sh -v -C regress:no-ctty' in %check.

Actual results:
Build will never end and somewhen killed after 24 hours by the buildsys.

Expected results:
Working rebuild by providing ttys to satisfy openpty(3).

Additional info:
This should be an issue for other shells with test sections, too.

Running mock 1.1.12 locally, things worked locally. But Fedora buildsys
is running 1.1.8 because there was another pty problem with the current
version somehow...

Comment 1 Robert Scheck 2011-07-28 01:54:01 UTC
May you clarify with dgilmore regarding his other/further pty issues? Thanks.

Comment 2 Henrik Nordström 2011-09-21 11:25:39 UTC
1.1.12 have worked fine on all pty related packages I have seen in the armv7hl secondary arch.

Comment 3 Clark Williams 2011-09-22 17:16:56 UTC
Robert,

Have you seen this problem with 1.1.14?  I did a pretty extensive rework for pty issues and just wondering if I have more work yet to do...

Comment 4 Clark Williams 2011-09-23 19:03:03 UTC
Marking this as fixed with 1.1.15. If not please reopen


Note You need to log in before you can comment on or make changes to this bug.