[Buildd-tools-devel] [GIT] sbuild branch, master, updated. sbuild-0.57.5-357-gac4acf6

Sun Mar 8 16:02:31 UTC 2009

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 "sbuild".

The branch, master has been updated
  discards  713f26d056c714bd901d9c4cd77e4ce8e12a47b7 (commit)
  discards  c9c41ceb2101fed1ccffd41074b3f20f7ae83676 (commit)
  discards  89ae6bd10b78b905978bda3fd07953b5c0fa20fb (commit)
  discards  cd4c2edbc230dc76080937a2c7cfcdb6238a002f (commit)
  discards  ce276c60c0430442b35475b104fdaad37c7067f5 (commit)
  discards  5d44df9972bb619cc7af4f21f846be27a0431c44 (commit)
  discards  20a60963a2e81d069226787922d2da3a3486a523 (commit)
  discards  565a4009958cad4822176f68f1c105341eda2d99 (commit)
  discards  a6f8294e362f1d43c6f12120c6239a1d95ac1f78 (commit)
  discards  73c442bcfb66a253decebd5bbdbd2af517422b9e (commit)
  discards  66587a325725833b3890817212ca601fa061db3f (commit)
  discards  719eb92b69d04f1d21958d42112060a0318eca9f (commit)
       via  ac4acf683741eb2602fc0c6a383d4df9717723a1 (commit)
       via  7c538b99dd490295e93a7d38c1bc56bcbad033d2 (commit)
       via  ed1d0504b1457b081d528fbf9f36237691fa66a9 (commit)
       via  a1d33bd7650f8c7ad1afa6ad4698d92f74cd7135 (commit)
       via  0d0dbc8b27f7615d83a5b2393ae70c5b98f7141c (commit)
       via  3925f5712b726ec947cc10665c1c8cfbb389623d (commit)
       via  9703826459a9ff4e800acdf7d76e8f2d67685882 (commit)
       via  b099ba631062c23a26ca2c5558f5b0d1d3d255bb (commit)
       via  5e73ac9b178fbe6724b2988579775dbb64c705e2 (commit)
       via  2731512af04222f58a0b3f7af5b2b95cc1f30558 (commit)
       via  253d6d0514657eb69c006b785abbd2888843a70f (commit)
       via  b15007cd6a3273162315f54d3b02b87aa46a8513 (commit)
       via  a6075a18c1a05499d68f57623ab296b21a02c87b (commit)
       via  6d87fa6a3b94f15d945ecd53bc87c2098ad75fec (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (713f26d056c714bd901d9c4cd77e4ce8e12a47b7)
            \
             N -- N -- N (ac4acf683741eb2602fc0c6a383d4df9717723a1)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

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 ac4acf683741eb2602fc0c6a383d4df9717723a1
Author: Adeodato SimÃ³ <dato at net.com.org.es>
Date:   Sun Mar 8 15:59:17 2009 +0000

    [db] set_ctime: Add missing semicolon

    Signed-off-by: Roger Leigh <rleigh at debian.org>

commit 7c538b99dd490295e93a7d38c1bc56bcbad033d2
Author: Roger Leigh <rleigh at debian.org>
Date:   Sun Mar 8 15:52:50 2009 +0000

    [db] install.sql: Split database creation into a separate file

commit ed1d0504b1457b081d528fbf9f36237691fa66a9
Author: Adeodato SimÃ³ <dato at net.com.org.es>
Date:   Sun Mar 8 15:30:07 2009 +0000

    [db] Create a "suite_arches" table to list the architectures in a suite

    The database schema was missing a list of architectures in each suite.
    This is needed, because one can't simply use the "architectures" table
    to decide what arches to act on, eg. when importing packages
    information, or when creating a web interface: that table may contain no
    longer active architectures (which are kept around for build_logs), and
    many actions really need the list of architectures specific to a suite.

    This commit introduces a "suite_arches" table, with a relation of what
    architectures are available in each suite. It also adds foreign keys
    towards this table from suite_binaries and build_status; this way, it is
    ensured that dropping an architecture from a suite will clean up those
    tables from no longer relevant entries.

    Signed-off-by: Roger Leigh <rleigh at debian.org>

commit a1d33bd7650f8c7ad1afa6ad4698d92f74cd7135
Author: Adeodato SimÃ³ <dato at net.com.org.es>
Date:   Sun Mar 8 15:23:49 2009 +0000

    [db] Add triggers for build_status

    Triggers keep the ctime column up to date, validate the
    bin_nmu field and insert the record into build_status_history.

    Signed-off-by: Roger Leigh <rleigh at debian.org>

commit 0d0dbc8b27f7615d83a5b2393ae70c5b98f7141c
Author: Adeodato SimÃ³ <dato at net.com.org.es>
Date:   Sun Mar 8 15:14:55 2009 +0000

    [db] build_status.ctime defaults to 'epoch'

    Value will be set with a trigger.

    Signed-off-by: Roger Leigh <rleigh at debian.org>

commit 3925f5712b726ec947cc10665c1c8cfbb389623d
Author: Adeodato SimÃ³ <dato at net.com.org.es>
Date:   Sun Mar 8 15:13:50 2009 +0000

    [db] build_status.builder can be NULL

    This allows changes to be made by people as well as buildds.

    Signed-off-by: Roger Leigh <rleigh at debian.org>

commit 9703826459a9ff4e800acdf7d76e8f2d67685882
Author: Adeodato SimÃ³ <dato at net.com.org.es>
Date:   Sun Mar 8 15:12:37 2009 +0000

    [db] Add bin_nmu column to build_status and build_status_history

    Signed-off-by: Roger Leigh <rleigh at debian.org>

commit b099ba631062c23a26ca2c5558f5b0d1d3d255bb
Author: Adeodato SimÃ³ <dato at net.com.org.es>
Date:   Sun Mar 8 14:58:53 2009 +0000

    [db] Drop index on build_status.ctime

    Signed-off-by: Roger Leigh <rleigh at debian.org>

commit 5e73ac9b178fbe6724b2988579775dbb64c705e2
Author: Adeodato SimÃ³ <dato at net.com.org.es>
Date:   Sun Mar 8 14:57:25 2009 +0000

    [db] Rename build_state.state to build_state.status

    Also rename in build_status history.
    Reformat build_state.user.
    Update comments.

    Signed-off-by: Roger Leigh <rleigh at debian.org>

commit 2731512af04222f58a0b3f7af5b2b95cc1f30558
Author: Adeodato SimÃ³ <dato at net.com.org.es>
Date:   Sun Mar 8 14:48:14 2009 +0000

    [db] Remove job id number from build_status and build_status_history

    Also update build_status_properties to use the new primary key
    of build_status.

    Signed-off-by: Roger Leigh <rleigh at debian.org>

commit 253d6d0514657eb69c006b785abbd2888843a70f
Author: Roger Leigh <rleigh at debian.org>
Date:   Sat Mar 7 19:35:43 2009 +0000

    [db] Rename job_states to package_states (update comments)

commit b15007cd6a3273162315f54d3b02b87aa46a8513
Author: Roger Leigh <rleigh at debian.org>
Date:   Sat Mar 7 19:34:23 2009 +0000

    [db] Rename job_states to package_states

commit a6075a18c1a05499d68f57623ab296b21a02c87b
Author: Roger Leigh <rleigh at debian.org>
Date:   Sat Mar 7 19:31:41 2009 +0000

    [db] Duplicate build_status as build_status_history

    This will store a history of the changes in the build_status
    table.  Currently, it retains all of the constraints, but
    future commits will drop referential integrity on some of the
    columns.

commit 6d87fa6a3b94f15d945ecd53bc87c2098ad75fec
Author: Adeodato SimÃ³ <dato at net.com.org.es>
Date:   Sat Mar 7 19:10:52 2009 +0000

    [db] Rename build_jobs to build_status

    Also rename build_job_properties to build_status_properties.

    Signed-off-by: Roger Leigh <rleigh at debian.org>

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

Summary of changes:
 db/db.sql      |    8 ++------
 db/install.sql |   26 ++++++++++++++++++++++++++
 2 files changed, 28 insertions(+), 6 deletions(-)
 create mode 100644 db/install.sql

hooks/post-receive
-- 
sbuild