Hi!
I already ha d deep look at the current packaging included in upstream git,
basically the initscripts need to be rewritten as they are full of
redhadisms, but thats'it basically.
I think the debconf templates and the corresponding configuration parts in the
maintainer scripts should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I already ha d deep look at the current packaging included in upstream git,
basically the initscripts need to be rewritten as they are full of
redhadisms, but thats'it basically.
As far as I can tell, the packaging in upstream git (and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What would you think of applying for some space on alioth so that we can
maintain
ocfs2-tools collaboratively and finally upload a recent version of
ocfs2-tools?
I have moved the packaging to the collab-maint Subversion repository:
On Fri, Nov 21, 2008 at 09:35:13AM +0100, Frederik Schüler wrote:
Hi!
I already ha d deep look at the current packaging included in upstream git,
basically the initscripts need to be rewritten as they are full of
redhadisms, but thats'it basically.
Um, they use lsb bits, because
On Fri, Nov 21, 2008 at 08:38:02AM +0100, Jeremy Lainé wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frederik, Joel,
I have started putting together the packaging for ocfs2-tools here:
https://svn.jerryweb.org/public/packages/ocfs2-tools/
FYI, iceweasel reports:
On Fri, Nov 21, 2008 at 06:17:58PM +0100, Jeremy Lainé wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What would you think of applying for some space on alioth so that we can
maintain
ocfs2-tools collaboratively and finally upload a recent version of
ocfs2-tools?
I have
On Fri, Nov 21, 2008 at 10:06:32AM +0100, Jeremy Lainé wrote:
I already ha d deep look at the current packaging included in upstream git,
basically the initscripts need to be rewritten as they are full of
redhadisms, but thats'it basically.
As far as I can tell, the packaging in
Hi!
no, please, no way for cdbs.
Best regards
Frederik Schüler
On Friday 21 November 2008 22:31:53 Joel Becker wrote:
On Fri, Nov 21, 2008 at 06:17:58PM +0100, Jeremy Lainé wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What would you think of applying for some space on alioth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Joel!
Still don't know why an upstream debian/ tree is so frowned
upon.
I have no problem with upstream working on debian/ or even on with packaging
being hosted
upstream, I went with alioth for the sake of expediency. If you want to
On Fri, Nov 21, 2008 at 10:44:12PM +0100, Jeremy Lainé wrote:
I *do* have a problem with debian/ being included in release tarballs though,
it makes for
messy .diff.gz if for instance files get dropped or moved around from
packaging between
revision 1.4.1-1 and 1.4.1-2. Also, at times there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frederik, Joel,
I have started putting together the packaging for ocfs2-tools here:
https://svn.jerryweb.org/public/packages/ocfs2-tools/
What would you think of applying for some space on alioth so that we can
maintain
ocfs2-tools collaboratively
11 matches
Mail list logo
