libeatmydata release-105

Milestone information

Project:
libeatmydata
Series:
trunk
Version:
release-105
Released:
2014-10-29  
Registrant:
Stewart Smith
Release registered:
2014-10-29
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon libeatmydata-105.tar.gz (md5, sig) Source Tarball 3,366
last downloaded today
Total downloads: 3,366

Release notes 

This release does not have release notes.

Changelog 

View the full changelog

------------------------------------------------------------
revno: 105
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Thu 2014-10-30 10:02:34 +1100
message:
  tag version 105
------------------------------------------------------------
revno: 104
author: Mattia Rizzolo <email address hidden>
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Thu 2014-10-30 10:00:37 +1100
message:
  Fix executable-not-elf-or-script lintian warning
------------------------------------------------------------
revno: 103
author: Mattia Rizzolo <email address hidden>
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Thu 2014-10-30 09:59:45 +1100
message:
  Fix multiarch issue

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765810
------------------------------------------------------------
revno: 102 [merge]
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Thu 2014-10-30 09:54:17 +1100
message:
  merge remove install-exec hook
------------------------------------------------------------
revno: 101
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Thu 2014-10-30 09:43:36 +1100
message:
  update AUTHORS
------------------------------------------------------------
revno: 100
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Thu 2014-10-30 09:41:27 +1100
message:
  Some test suite updates.

  Add tst-key4 from libc, although we need to deal with 1 less pthread key
  than normal due to something that's going on with pthread when libeatmydata
  is present that I don't quite know what's going on.

  We also update tst-cancel and the test run script so that we better capture
  errors from the test suite.
------------------------------------------------------------
revno: 99
author: Mattia Rizzolo <email address hidden>
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Thu 2014-10-30 09:32:44 +1100
message:
  open() returns -EFAULT when program doesn't run ctor

  https://bugs.launchpad.net/libeatmydata/+bug/1374862

  bug forwarded from debian, see the remote tracker.

  I encountered some mysterious errors with eatmydata. For example, when installing gnunet-server (as a build dependency of some source package), the following error happens:

  Fatal: can't open /dev/urandom: Bad address

  In fact, you can easily reproduce this (also on other arches like amd64) with:

  # eatmydata gnunet-arm
  Fatal: can't open /dev/urandom: Bad address
  Aborted
  #

  This is due to the assumption that normally, eatmydata_init() is called as a constructor before main():

  void __attribute__ ((constructor)) eatmydata_init(void)

  However, some programs like gnunet-arm for some reason don't run ctors of our SO's ctor eatmydata_init(). While it might be a good idea to fix this in gnunet also, I propose a workaround in eatmydata to even run programs like gnunet-arm
  with this issue more transparently (as run without eatmydata).

  Consider the attached patch: It fixes the issue by detecting directly if we are just in the process of eatmydata_init() already. This is already done by checking for !libc_open but this also happens in the above case: eatmydata_init() not been called previously, leading to the assumption in open() that we are catching the case of just initing and coming back from
  dlsym() to open(). But here, this branch catches the wrong state, because in gnunet-arm, eatmydata_init() wasn't called at all.

  So the patch issues EFAULT only in case of actually just eatmydata_init()ing. Otherwise, eatmydata_is_hungry() and therefore eatmydata_init() can be called just as usual.

  FWIW, the case of eatmydata_init() not being run as a ctor is already handled by running it in eatmydata_is_hungry() but this doesn't work in case of open() being called before one of the other triggering functions.

  Note that gnunet-server is just an example. I encountered the same issue in some other occasions also.

  Furthermore, this bug affects the new release of gnutls, and thus every package that use it. This makes impossible to use gnutls with eatmydata.

  Please consider the patch attached, which is tested by various people and soon will be uploaded to Debian.
------------------------------------------------------------
revno: 98
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Thu 2014-10-30 09:32:01 +1100
message:
  update copyright headers
------------------------------------------------------------
revno: 97
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Thu 2014-10-30 09:30:05 +1100
message:
  whitespace cleanup
------------------------------------------------------------
revno: 96
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Tue 2013-11-19 11:21:53 +1100
message:
  remove traces of sphinx from build
------------------------------------------------------------
revno: 95
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Tue 2013-11-19 11:19:57 +1100
message:
  remove pandora_run_cpplint
------------------------------------------------------------
revno: 94
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Tue 2013-11-19 11:19:21 +1100
message:
  remove traces of C++ from autotools/pandora
------------------------------------------------------------
revno: 93
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Tue 2013-11-19 11:12:39 +1100
message:
  remove pandora sasl
------------------------------------------------------------
revno: 92
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Tue 2013-11-19 11:11:15 +1100
message:
  remove pandora check for gcc atomics
------------------------------------------------------------
revno: 91
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Tue 2013-11-19 11:10:09 +1100
message:
  remove pandora check for clock_gettime
------------------------------------------------------------
revno: 90
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Tue 2013-11-19 11:08:40 +1100
message:
  remove some unused pandora files
------------------------------------------------------------
revno: 89
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Tue 2013-11-19 11:07:47 +1100
message:
  update automake test options so that we function in most places correctly, using parallel test run if possible
------------------------------------------------------------
revno: 88
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Fri 2013-08-09 17:04:25 +1000
message:
  sync() isn't a cancellation point - per Aurelien Jarno in debian bug 713035
------------------------------------------------------------
revno: 87
author: Jaroslav Kortus <email address hidden>
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Fri 2013-08-09 17:00:25 +1000
message:
  Update SPEC file to meet Fedora packaging guidelines. Thanks to Jaroslav Kortus for the patch.
------------------------------------------------------------
revno: 86
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Fri 2013-06-28 16:35:36 +1000
message:
  last bunch of rpm package fixes, along with some makefile fixes. Don't do versioned .so anymore, don't package .la, don't build static libs, fix up rpm spec for all supported RPM distros that build.opensuse.org builds
------------------------------------------------------------
revno: 85
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Fri 2013-06-28 14:32:36 +1000
message:
  fix up GPL-3 license string
------------------------------------------------------------
revno: 84
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Fri 2013-06-28 14:29:12 +1000
message:
  fix up some spec file things: don't autoreconf, it's unneeded and breaks on old distros. Also, capitalize summary (rpmlint)
------------------------------------------------------------
revno: 83
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Fri 2013-06-28 14:14:49 +1000
message:
  update spec file to be configured correctly with version and be buildable by build.opensuse.org
------------------------------------------------------------
revno: 82
tags: libeatmydata-82
committer: Stewart Smith <email address hidden>
branch nick: libeatmydata
timestamp: Fri 2013-06-28 11:32:20 +1000
message:
  bump version number for release
------------------------------------------------------------
Use --include-merged or -n0 to see merged revisions.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.