[suggest] Mercurial spec file

[Tim Dettrick]

Mercurial 1.6.4 is out, so I've updated my previously submitted spec file to incorporate the slight changes from the original spec file in its contrib area [1]. As with before, I've tried to maintain the same package structure as the existing RPMforge RPMs. Attached is the updated version.

Could I please get it validated for inclusion, or at least some feedback one what I need to do to get it included?

Given the bugfix list since 1.5 [2] I can't see any reason why anybody would want to stick with 1.5 in the long term. In my case there's a highly irritating subrepo bug [3] that's been fixed.

Thank you,

Tim Dettrick
Senior Software Engineer
Software Services
ITS, The University of Queensland

[1] http://selenic.com/repo/hg-stable/file/93d8bff78c96/contrib/mercurial.spec
[2] http://mercurial.selenic.com/wiki/WhatsNew
[3] http://mercurial.selenic.com/bts/issue2217

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mercurial.spec
Type: application/octet-stream
Size: 3478 bytes
Desc: mercurial.spec
Url : http://lists.repoforge.org/pipermail/users/attachments/20101005/f69b3bd7/attachment.obj

[Yury V. Zaytsev]

Post by Tim Dettrick
Could I please get it validated for inclusion, or at least some
feedback one what I need to do to get it included?

I had a look at it:

1) Dist tag is missing
2) Build requires one per line
3) SMP flags
4) Other small things

I have committed the SPEC, check it out here:

http://svn.rpmforge.net/svn/trunk/rpms/mercurial/

Thanks!

[Yury V. Zaytsev]

Post by Tim Dettrick
Mercurial 1.6.4 is out, so I've updated my previously submitted spec
file to incorporate the slight changes from the original spec file in
its contrib area [1]. As with before, I've tried to maintain the same
package structure as the existing RPMforge RPMs. Attached is the
updated version.

Any feedback so far?

The package only builds on EL5 for the obvious reason (Python 2.4+ is
only available on EL5+).

[Tim Dettrick]

Mercurial 1.6.4 is out, so I've updated my previously submitted spec file to incorporate the slight changes from the original spec file in its contrib area [1]. As with before, I've tried to maintain the same package structure as the existing RPMforge RPMs. Attached is the updated version.

Could I please get it validated for inclusion, or at least some feedback one what I need to do to get it included?

Given the bugfix list since 1.5 [2] I can't see any reason why anybody would want to stick with 1.5 in the long term. In my case there's a highly irritating subrepo bug [3] that's been fixed.

Thank you,

Tim Dettrick
Senior Software Engineer
Software Services
ITS, The University of Queensland

[1] http://selenic.com/repo/hg-stable/file/93d8bff78c96/contrib/mercurial.spec
[2] http://mercurial.selenic.com/wiki/WhatsNew
[3] http://mercurial.selenic.com/bts/issue2217

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mercurial.spec
Type: application/octet-stream
Size: 3478 bytes
Desc: mercurial.spec
Url : http://lists.repoforge.org/pipermail/users/attachments/20101005/f69b3bd7/attachment-0001.obj

[Yury V. Zaytsev]

Post by Tim Dettrick
Could I please get it validated for inclusion, or at least some
feedback one what I need to do to get it included?

I had a look at it:

1) Dist tag is missing
2) Build requires one per line
3) SMP flags
4) Other small things

I have committed the SPEC, check it out here:

http://svn.rpmforge.net/svn/trunk/rpms/mercurial/

Thanks!

[Yury V. Zaytsev]

Post by Tim Dettrick
Mercurial 1.6.4 is out, so I've updated my previously submitted spec
file to incorporate the slight changes from the original spec file in
its contrib area [1]. As with before, I've tried to maintain the same
package structure as the existing RPMforge RPMs. Attached is the
updated version.

Any feedback so far?

The package only builds on EL5 for the obvious reason (Python 2.4+ is
only available on EL5+).

[Tim Dettrick]

Mercurial 1.6.4 is out, so I've updated my previously submitted spec file to incorporate the slight changes from the original spec file in its contrib area [1]. As with before, I've tried to maintain the same package structure as the existing RPMforge RPMs. Attached is the updated version.

Could I please get it validated for inclusion, or at least some feedback one what I need to do to get it included?

Given the bugfix list since 1.5 [2] I can't see any reason why anybody would want to stick with 1.5 in the long term. In my case there's a highly irritating subrepo bug [3] that's been fixed.

Thank you,

Tim Dettrick
Senior Software Engineer
Software Services
ITS, The University of Queensland

[1] http://selenic.com/repo/hg-stable/file/93d8bff78c96/contrib/mercurial.spec
[2] http://mercurial.selenic.com/wiki/WhatsNew
[3] http://mercurial.selenic.com/bts/issue2217

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mercurial.spec
Type: application/octet-stream
Size: 3478 bytes
Desc: mercurial.spec
Url : http://lists.repoforge.org/pipermail/users/attachments/20101005/f69b3bd7/attachment-0002.obj

[Yury V. Zaytsev]

Post by Tim Dettrick
Could I please get it validated for inclusion, or at least some
feedback one what I need to do to get it included?

I had a look at it:

1) Dist tag is missing
2) Build requires one per line
3) SMP flags
4) Other small things

I have committed the SPEC, check it out here:

http://svn.rpmforge.net/svn/trunk/rpms/mercurial/

Thanks!

[Yury V. Zaytsev]

Post by Tim Dettrick
Mercurial 1.6.4 is out, so I've updated my previously submitted spec
file to incorporate the slight changes from the original spec file in
its contrib area [1]. As with before, I've tried to maintain the same
package structure as the existing RPMforge RPMs. Attached is the
updated version.

Any feedback so far?

The package only builds on EL5 for the obvious reason (Python 2.4+ is
only available on EL5+).

[Tim Dettrick]

Mercurial 1.6.4 is out, so I've updated my previously submitted spec file to incorporate the slight changes from the original spec file in its contrib area [1]. As with before, I've tried to maintain the same package structure as the existing RPMforge RPMs. Attached is the updated version.

Could I please get it validated for inclusion, or at least some feedback one what I need to do to get it included?

Given the bugfix list since 1.5 [2] I can't see any reason why anybody would want to stick with 1.5 in the long term. In my case there's a highly irritating subrepo bug [3] that's been fixed.

Thank you,

Tim Dettrick
Senior Software Engineer
Software Services
ITS, The University of Queensland

[1] http://selenic.com/repo/hg-stable/file/93d8bff78c96/contrib/mercurial.spec
[2] http://mercurial.selenic.com/wiki/WhatsNew
[3] http://mercurial.selenic.com/bts/issue2217

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mercurial.spec
Type: application/octet-stream
Size: 3478 bytes
Desc: mercurial.spec
Url : http://lists.repoforge.org/pipermail/users/attachments/20101005/f69b3bd7/attachment-0003.obj

[Yury V. Zaytsev]

Post by Tim Dettrick
Could I please get it validated for inclusion, or at least some
feedback one what I need to do to get it included?

I had a look at it:

1) Dist tag is missing
2) Build requires one per line
3) SMP flags
4) Other small things

I have committed the SPEC, check it out here:

http://svn.rpmforge.net/svn/trunk/rpms/mercurial/

Thanks!

[Yury V. Zaytsev]

Post by Tim Dettrick
Mercurial 1.6.4 is out, so I've updated my previously submitted spec
file to incorporate the slight changes from the original spec file in
its contrib area [1]. As with before, I've tried to maintain the same
package structure as the existing RPMforge RPMs. Attached is the
updated version.

Any feedback so far?

The package only builds on EL5 for the obvious reason (Python 2.4+ is
only available on EL5+).

[Tim Dettrick]

Mercurial 1.6.4 is out, so I've updated my previously submitted spec file to incorporate the slight changes from the original spec file in its contrib area [1]. As with before, I've tried to maintain the same package structure as the existing RPMforge RPMs. Attached is the updated version.

Could I please get it validated for inclusion, or at least some feedback one what I need to do to get it included?

Given the bugfix list since 1.5 [2] I can't see any reason why anybody would want to stick with 1.5 in the long term. In my case there's a highly irritating subrepo bug [3] that's been fixed.

Thank you,

Tim Dettrick
Senior Software Engineer
Software Services
ITS, The University of Queensland

[1] http://selenic.com/repo/hg-stable/file/93d8bff78c96/contrib/mercurial.spec
[2] http://mercurial.selenic.com/wiki/WhatsNew
[3] http://mercurial.selenic.com/bts/issue2217

-------------- next part --------------
A non-text attachment was scrubbed...
Name: mercurial.spec
Type: application/octet-stream
Size: 3478 bytes
Desc: mercurial.spec
URL: <http://lists.repoforge.org/pipermail/users/attachments/20101005/f69b3bd7/attachment-0004.obj>

[Yury V. Zaytsev]

Post by Tim Dettrick
Could I please get it validated for inclusion, or at least some
feedback one what I need to do to get it included?

I had a look at it:

1) Dist tag is missing
2) Build requires one per line
3) SMP flags
4) Other small things

I have committed the SPEC, check it out here:

http://svn.rpmforge.net/svn/trunk/rpms/mercurial/

Thanks!

[Yury V. Zaytsev]

Post by Tim Dettrick
Mercurial 1.6.4 is out, so I've updated my previously submitted spec
file to incorporate the slight changes from the original spec file in
its contrib area [1]. As with before, I've tried to maintain the same
package structure as the existing RPMforge RPMs. Attached is the
updated version.

Any feedback so far?

The package only builds on EL5 for the obvious reason (Python 2.4+ is
only available on EL5+).