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 3.x development tree branch, master, updated. 0e7e5f640bdf39c5d79f85be2d3f1b621a69ef32
Date: Mon, 04 Mar 2013 17:29:02 +0100	[thread overview]
Message-ID: <20130304162948.A1E9F2010D@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2707 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 3.x development tree".

The branch, master has been updated
       via  0e7e5f640bdf39c5d79f85be2d3f1b621a69ef32 (commit)
      from  da24a140617beda783dde94534c0c3871144011a (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 0e7e5f640bdf39c5d79f85be2d3f1b621a69ef32
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Mon Mar 4 17:28:31 2013 +0100

    pakfire: Fix database inst_size error.

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

Summary of changes:
 pakfire/pakfire.nm                                 |  2 +-
 ...d-inst_size-column-when-creating-new-data.patch | 24 ++++++++++++++++++++++
 2 files changed, 25 insertions(+), 1 deletion(-)
 create mode 100644 pakfire/patches/0001-database-Add-inst_size-column-when-creating-new-data.patch

Difference in files:
diff --git a/pakfire/pakfire.nm b/pakfire/pakfire.nm
index eda7d6f..406be21 100644
--- a/pakfire/pakfire.nm
+++ b/pakfire/pakfire.nm
@@ -5,7 +5,7 @@
 
 name       = pakfire
 version    = 0.9.25
-release    = 1
+release    = 2
 
 maintainer = Michael Tremer <michael.tremer(a)ipfire.org>
 groups     = System/Packaging
diff --git a/pakfire/patches/0001-database-Add-inst_size-column-when-creating-new-data.patch b/pakfire/patches/0001-database-Add-inst_size-column-when-creating-new-data.patch
new file mode 100644
index 0000000..f366f21
--- /dev/null
+++ b/pakfire/patches/0001-database-Add-inst_size-column-when-creating-new-data.patch
@@ -0,0 +1,24 @@
+From 0d6d6fd2b89c609a6f8daff225c6c98b54a041cc Mon Sep 17 00:00:00 2001
+From: Michael Tremer <michael.tremer(a)ipfire.org>
+Date: Mon, 4 Mar 2013 17:18:52 +0100
+Subject: [PATCH] database: Add inst_size column when creating new databases.
+
+---
+ python/pakfire/repository/database.py | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/python/pakfire/repository/database.py b/python/pakfire/repository/database.py
+index fc8a1a9..d8751e9 100644
+--- a/python/pakfire/repository/database.py
++++ b/python/pakfire/repository/database.py
+@@ -190,6 +190,7 @@ class DatabaseLocal(Database):
+ 				groups		TEXT,
+ 				filename	TEXT,
+ 				size		INTEGER,
++				inst_size	INTEGER,
+ 				hash1		TEXT,
+ 				provides	TEXT,
+ 				requires	TEXT,
+-- 
+1.7.11.7
+


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

                 reply	other threads:[~2013-03-04 16:29 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=20130304162948.A1E9F2010D@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