[DSE-Dev] New development packages staged to people.debian.org

[Manoj Srivastava]

Hi,

        I have been refraining from packaging the development releases
 of SELinux user land packages while Lenny was frozen, but now that
 release is imminent, I have packaged the latest development release and
 put it up on people.debian.org. What we have is:

 |-----------------+---------|
 | Package         | Version |
 |-----------------+---------|
 | libsepol1       |  2.0.32 |
 | libselinux      |  2.0.71 |
 | libsemanage     |  2.0.27 |
 | policycoreutils |  2.0.55 |
 | sepolgen        |  1.0.13 |
 |-----------------+---------|

        In order to get these packages, add to the sources.list:
--8<---------------cut here---------------start------------->8---
deb      http://newpeople.debian.org/~srivasta/ packages/ 
deb-src  http://newpeople.debian.org/~srivasta/ packages/
--8<---------------cut here---------------end--------------->8---

        The archive key is attached below. These packages have all been
 tested locally, and each has been built twice in a row by my new
 automation, which did catch a bug. Please test. (Note that the ruby
 bindings for libselinux are new, so would require NEW processing when
 we do upload post Lenny).


         I have not updated the reference policy on my git  repo, but I
 hope to do that this weekend, and then Russell can fix things I mess up
 :-).

        The URL to the source code, and how to browse the repo, are
 detailed below as well. To get libsepol, for example, using git, do the
 following (tested): 
--8<---------------cut here---------------start------------->8---
git clone git://git.debian.org/~srivasta/debian/libsepol.git   
cd libsepol
git submodule init  
git submodule update 
cd debian
git submodule init  
git submodule update 
--8<---------------cut here---------------end--------------->8---

        In the past, I had been somewhat lax about pushing out my
 repositories in a timely fashion, but right now, they are all in sync,
 so cloning the directory structure should not be an issue.

--8<---------------cut here---------------start------------->8---
Vcs-Browser: http://git.debian.org/git/?p=users/srivasta/debian/libsepol.git
Vcs-Git: git://git.debian.org/~srivasta/debian/libsepol.git

VCS-Browser: http://git.debian.org/git/?p=users/srivasta/debian/libselinux.git
Vcs-Git:     git://git.debian.org/~srivasta/debian/libselinux.git

Vcs-Browser: http://git.debian.org/git/?p=users/srivasta/debian/libsemanage.git
Vcs-Git:     git://git.debian.org/~srivasta/debian/libsemanage.git

Vcs-Browser: http://git.debian.org/git/?p=users/srivasta/debian/policycoreutils.git
Vcs-Git:     git://git.debian.org/~srivasta/debian/policycoreutils.git

Vcs-Browser: http://git.debian.org/git/?p=users/srivasta/debian/sepolgen.git
Vcs-Git:     git://git.debian.org/~srivasta/debian/sepolgen.git
--8<---------------cut here---------------end--------------->8---



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 306 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/selinux-devel/attachments/20090212/f20cc522/attachment.pgp 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: arch-key.asc
Url: http://lists.alioth.debian.org/pipermail/selinux-devel/attachments/20090212/f20cc522/attachment.asc