** Branch linked: lp:ubuntu/python2.5
--
packaging backend crashes with "Interrupted system call"
https://bugs.launchpad.net/bugs/87292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
This patch factorize the present _no_intr patch, merges the py25-maint r65475
and protect the returned iostreams (stdin, stdout, stderr) read and write (in
fact, all callables in the iostream).
It is ok for common usage but it breakes the python 2.2 compat.
** Attachment added: "subprocess-retry
mark as wontfix for python2.4, unless a patch appears.
** Changed in: python2.4 (Ubuntu)
Status: New => Won't Fix
--
packaging backend crashes with "Interrupted system call"
https://bugs.launchpad.net/bugs/87292
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: python2.4 (Ubuntu)
Importance: Undecided
Status: New
--
packaging backend crashes with "Interrupted system call"
https://bugs.launchpad.net/bugs/87292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
I don't suppose you could backport this patch for python2.4 as well?
--
packaging backend crashes with "Interrupted system call"
https://bugs.launchpad.net/bugs/87292
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
We fixed it for all Python programs in python itself now, thus this
automatically applies to apport, too.
** Changed in: apport (Ubuntu)
Status: In Progress => Rejected
--
packaging backend crashes with "Interrupted system call"
https://launchpad.net/bugs/87292
--
ubuntu-bugs mailing li
python2.5 (2.5-5ubuntu10) feisty; urgency=low
.
* Add debian/patches/subprocess-eintr-safety.dpatch:
- Create and use wrappers around read(), write(), and os.waitpid() in the
subprocess module which retry the operation on an EINTR (which happens
if e. g. an alarm was raised
Grr, why wasn't this attached with the previous comment?
** Attachment added: "updated debdiff"
http://librarian.launchpad.net/6820346/python2.5.87292.debdiff
--
packaging backend crashes with "Interrupted system call"
https://launchpad.net/bugs/87292
--
ubuntu-bugs mailing list
ubuntu-bugs
** Attachment added: "updated patch suitable for upstream"
http://librarian.launchpad.net/6820347/subprocess-eintr-safety.patch
--
packaging backend crashes with "Interrupted system call"
https://launchpad.net/bugs/87292
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
New debdiff:
- Remove _read_all(), we don't need it. This also reverts the removal of the 1
MB exception limitation.
- Apply the patch in debian/rules (yay shiny build system)
- Give credit for the original patch in the changelog
--
packaging backend crashes with "Interrupted system call"
htt
** Changed in: apport (Ubuntu)
Assignee: (unassigned) => Martin Pitt
Status: Confirmed => In Progress
--
packaging backend crashes with "Interrupted system call"
https://launchpad.net/bugs/87292
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
** Attachment added: "patch suitable for upstream"
http://librarian.launchpad.net/6807594/subprocess-eintr-safety.patch
--
packaging backend crashes with "Interrupted system call"
https://launchpad.net/bugs/87292
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.
I really want to fix this for Feisty. If a general Python fix is deemed
too risky, I can alternatively put that new subprocess module into
apport. That will leave other applications to the same trap, though.
** Changed in: python2.5 (Ubuntu)
Target: None => ubuntu-7.04
--
packaging backen
** Attachment added: "proposed debdiff"
http://librarian.launchpad.net/6806142/python2.5.87292.debdiff
--
packaging backend crashes with "Interrupted system call"
https://launchpad.net/bugs/87292
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listi
I developed a fix and a test case for this, based on the old patch
attached to the upstream bug.
** Changed in: python2.5 (Ubuntu)
Status: Confirmed => Fix Committed
--
packaging backend crashes with "Interrupted system call"
https://launchpad.net/bugs/87292
--
ubuntu-bugs mailing list
I'll attempt to work around the problem in apport itself, but it'll get
a bit ugly.
** Changed in: apport (Ubuntu)
Importance: Undecided => Medium
--
packaging backend crashes with "Interrupted system call"
https://launchpad.net/bugs/87292
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Google finds lots of similar bug reports; although this does not seem to
be an actual subprocess bug (it should rather get fixed at a lower
level), subprocess seems to be particularly affected by the effect. I'll
link the upstream bug report.
** Also affects: python2.5 (Ubuntu)
Importance: Unde
Confirmed by a duplicate.
** Summary changed:
- [apport] apport-qt crashed with OSError in _execute_child()
+ packaging backend crashes with "Interrupted system call"
** Changed in: apport (Ubuntu)
Status: Unconfirmed => Confirmed
--
packaging backend crashes with "Interrupted system ca
18 matches
Mail list logo
