[Buildd-tools-devel] porting schroot to CentOS4

Dennis van Dok dennisvd at nikhef.nl
Wed Sep 12 21:22:32 UTC 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Roger Leigh schreef:
> Dennis van Dok <dennisvd at nikhef.nl> writes:
> 
>> just a short note to let you know I managed to port schroot to CentOS 4.
>> The porting was not entirely smooth, so I had to use some CentOS
>> specific patches; for details see
>> http://www.nikhef.nl/~dennisvd/chroot.html.
> 
> Do you have any diffs of the changes?  If you would like anything
> applying, please feel free to post patches to this list.  

I'll get to that later...
> 
> Regarding lockdev: The access(2) thing looks like a nasty bug.  Could
> you report a bug about it in CentOS/Fedora.
Done! It's #288461 [https://bugzilla.redhat.com/show_bug.cgi?id=288461]
and I've inspected it a little closer: the access call is in a Red Hat
specific patch (can you believe it). Has been there since 2001.

> Also note that (AFAICT)
> Debian is the de-facto upstream of lockdev since the upstream went
> away (I'm one of the part-time comaintainers as it happens).  You
> might want to ask them to update to the latest Debian version (1.0.3).

I hope they at least just drop the access(2) call.

> 
> Regarding PAM: The include mechanism in Debian is different from
> upstream (though both are as of last week supported).  I can supply
> both Debian- and Fedora/CentOS-specific variants.  The @include syntax
> is going to be sent upstream for consideration at some point, I
> believe.
That's good news; I'm not a pam expert, more of a copycat ;-)
> 
> Regarding the setup scripts: We can detect the locations of the
> binaries at configure time to improve portability here.
H'm, I wonder how to do that? Surely you wouldn't want to introduce a
build dependency on lvm... The simplest solution may be something like:

if test -x /sbin/lvcreate; then
  LVPATH=/sbin
elif test -x /usr/sbin/lvcreate; then
  LVPATH=/usr/sbin
else
  exit -1
fi

in the 05lvm script itself.

> 
> 
> BTW, there's a public SVN repo if you want to track development.  And,
> I'll be converting it to GIT over the next week, so you'll be able to
> clone your own repository and branch off it if you want to maintain
> your own changes. 
Wow. I just listened to a podcast about GIT the other day, and voilá,
there's a reason to start using it ;-)


 If you intend to maintain the CentOS port in the
> long term, I'm sure we can arrange access to the main GIT repository
> at some point as well.
I intend to ;-).

Cheers,

Dennis
- --
D.H. van Dok :: Software Engineer :: www.nikhef.nl :: www.vl-e.nl
Phone +31 20 592 50 12 :: http://www.nikhef.nl/~dennisvd/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG6FiYIITq5lEwLHcRAuIjAJ0U2QZwh0uqW+/78vcEIWLiP85RdwCcC5AE
5Tf4DWOmiXrd35CvQUc54f0=
=fFkR
-----END PGP SIGNATURE-----



More information about the Buildd-tools-devel mailing list