public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, thirteen, updated. 5e374e547d153a8998110275ec2f5720e559d5b6
Date: Sat, 24 Nov 2012 13:04:34 +0100	[thread overview]
Message-ID: <20121124120434.8F94B20376@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2417 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, thirteen has been updated
       via  5e374e547d153a8998110275ec2f5720e559d5b6 (commit)
       via  1f7e3a1c2fd0b2d1165a39e74aef542b1581091f (commit)
      from  f579ed457c077db1707993fd90f7bc77a3757f58 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 5e374e547d153a8998110275ec2f5720e559d5b6
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Sat Nov 24 13:01:29 2012 +0100

    Ship vi in update.
    
    Problem is:
    
    > [root(a)ipfire ~]# vim <some file>
    > vim: Symbol `ospeed' has different size in shared object, consider re-linking

commit 1f7e3a1c2fd0b2d1165a39e74aef542b1581091f
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Sat Nov 24 12:59:14 2012 +0100

    Remove preloading libsafe.
    
    libsafe has been used to protect against string (printf)
    formatting errors that could be a security threat.
    This is not needed anymore because glibc does it on its own.

-----------------------------------------------------------------------

Summary of changes:
 config/rootfiles/{oldcore/44 => core/65}/filelists/vim | 0
 config/rootfiles/core/65/update.sh                     | 3 +++
 2 files changed, 3 insertions(+)
 copy config/rootfiles/{oldcore/44 => core/65}/filelists/vim (100%)

Difference in files:
diff --git a/config/rootfiles/core/65/filelists/vim b/config/rootfiles/core/65/filelists/vim
new file mode 120000
index 0000000..9861317
--- /dev/null
+++ b/config/rootfiles/core/65/filelists/vim
@@ -0,0 +1 @@
+../../../common/vim
\ No newline at end of file
diff --git a/config/rootfiles/core/65/update.sh b/config/rootfiles/core/65/update.sh
index 2677936..dbd38c4 100644
--- a/config/rootfiles/core/65/update.sh
+++ b/config/rootfiles/core/65/update.sh
@@ -169,6 +169,9 @@ if [ -e /var/ipfire/qos/enable ]; then
 	/usr/local/bin/qosctrl start
 fi
 
+# Remove preloading libsafe.
+rm -f /etc/ld.so.preload
+
 #
 # Modify grub.conf
 #


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2012-11-24 12:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121124120434.8F94B20376@argus.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox