You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apreq-dev@httpd.apache.org by Joe Schaefer <jo...@sunstarsys.com> on 2004/08/30 02:09:49 UTC
[VOTE] 2.04_03-dev release candidate
Release candidate #3, built from current-cvs,
is available
http://cvs.apache.org/~joes/libapreq2-2.04_03-dev.tar.gz
http://cvs.apache.org/~joes/libapreq2-2.04_03-dev.tar.gz.asc
Please double-check this tarball and signature,
(and committers please vote) as I'd like to send
this off to CPAN and the ASF mirrors as-is.
Thanks!
--
Joe Schaefer
Re: [VOTE] 2.04_03-dev release candidate
Posted by Stas Bekman <st...@stason.org>.
Joe Schaefer wrote:
> Release candidate #3, built from current-cvs,
> is available
>
> http://cvs.apache.org/~joes/libapreq2-2.04_03-dev.tar.gz
> http://cvs.apache.org/~joes/libapreq2-2.04_03-dev.tar.gz.asc
>
> Please double-check this tarball and signature,
> (and committers please vote) as I'd like to send
> this off to CPAN and the ASF mirrors as-is.
+1
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: [VOTE] 2.04_03-dev release candidate
Posted by Bojan Smojver <bo...@rexursive.com>.
Just a quick note that RPMS are available from the usual place:
ftp://ftp.rexursive.com/pub/libapreq2/
Also, a new version of mod_perl, with corrected dependencies is here:
ftp://ftp.rexursive.com/pub/mod-perl/
--
Bojan
Re: [VOTE] 2.04_03-dev release candidate
Posted by Joe Schaefer <jo...@sunstarsys.com>.
Joe Schaefer <jo...@sunstarsys.com> writes:
> I'll send it to pause.cpan.org and post the announcement.
Nevermind, PAUSE is at pause.perl.org, which *is* resolvable.
--
Joe Schaefer
Re: [VOTE] 2.04_03-dev release candidate
Posted by Joe Schaefer <jo...@sunstarsys.com>.
Geoffrey Young <ge...@modperlcookbook.org> writes:
[...]
> sorry it took so long for me to weigh in. I've been a little
> preoccupied :)
>
> the tarball looks good to me with 2.0 and 2.1 cvs - all tests pass.
Thanks Geoffrey- and Congratulations!
cvs is tagged, and the tarball is off for distribution through the ASF.
Once cpan.org's DNS server comes back up (AFAICT it's been down for
quite a while now), I'll send it to pause.cpan.org and post the
announcement.
--
Joe Schaefer
Re: [VOTE] 2.04_03-dev release candidate
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
Joe Schaefer wrote:
> Release candidate #3, built from current-cvs,
> is available
>
> http://cvs.apache.org/~joes/libapreq2-2.04_03-dev.tar.gz
> http://cvs.apache.org/~joes/libapreq2-2.04_03-dev.tar.gz.asc
>
> Please double-check this tarball and signature,
> (and committers please vote) as I'd like to send
> this off to CPAN and the ASF mirrors as-is.
sorry it took so long for me to weigh in. I've been a little preoccupied :)
the tarball looks good to me with 2.0 and 2.1 cvs - all tests pass.
+1
--Geoff
Re: [VOTE] 2.04_03-dev release candidate
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Sun, 29 Aug 2004, Joe Schaefer wrote:
> Randy Kobes <ra...@theoryx5.uwinnipeg.ca> writes:
>
> [...]
>
> > One note - on linux, I had to run ./buildconf first,
> > then ./configure.
>
> Oops, my boo-boo (I inadvertently did a VPATH build,
> which doesn't work yet).
>
> tarball+sig replaced, please test them again.
+1, on both linux and Win32 of the previous message.
Nice work, Joe!
The signature also checks OK.
--
best regards,
randy
Re: [VOTE] 2.04_03-dev release candidate
Posted by Joe Schaefer <jo...@sunstarsys.com>.
Randy Kobes <ra...@theoryx5.uwinnipeg.ca> writes:
[...]
> One note - on linux, I had to run ./buildconf first,
> then ./configure.
Oops, my boo-boo (I inadvertently did a VPATH build,
which doesn't work yet).
tarball+sig replaced, please test them again.
--
Joe Schaefer
Re: [VOTE] 2.04_03-dev release candidate
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Sun, 29 Aug 2004, Joe Schaefer wrote:
>
> Release candidate #3, built from current-cvs,
> is available
>
> http://cvs.apache.org/~joes/libapreq2-2.04_03-dev.tar.gz
> http://cvs.apache.org/~joes/libapreq2-2.04_03-dev.tar.gz.asc
>
> Please double-check this tarball and signature,
> (and committers please vote) as I'd like to send
> this off to CPAN and the ASF mirrors as-is.
>
> Thanks!
+1 for me, on both linux (Apache/2.0.50 prefork,
perl-5.8.5 mod_perl-1.99_16) and Win32 (Apache/2.0.50
winnt and perl-5.8.4 mod_perl-1.99_16). All tests
pass on both.
One note - on linux, I had to run ./buildconf first,
then ./configure.
--
best regards,
randy
Re: [VOTE] 2.04_03-dev release candidate
Posted by Joe Schaefer <jo...@sunstarsys.com>.
Bojan Smojver <bo...@rexursive.com> writes:
[...]
> So, this one will be:
>
> libapreq2-2.04_dev-2.3.src.rpm
> ^ ^
> | |
> | --------------> libapreq2 RC or intermediate version
> ----------------> RPM release
>
> How does that sit with you?
Cool, no objections here.
--
Joe Schaefer
Re: [VOTE] 2.04_03-dev release candidate
Posted by Bojan Smojver <bo...@rexursive.com>.
Quoting Joe Schaefer <jo...@sunstarsys.com>:
> > I'm trying to determine all this for the RPM spec file. The version of
> > the RPM should contain all the information it can (e.g. _dev_rc2),
>
> I recommend not including release candidate data in the spec file.
> Is it possible to just remove the "_03" from the tarball's name
> before building the rpm?
Actually, the easiest way to do this is to keep two version numbers inside the
spec file. One actual (as released by you) and one RPM specific (produced by
some sed-ing). This enables the script to be quickly adopted for new versions,
without the need to rename anything and with the ability to reference
externally avaliable tarballs. If the name of the tarball does not match, there
could errors when its being fetched.
RPMs cannot have dashes in version numbers, so this one will have to be called
2.04_dev, rather than 2.04-dev. Hope that's cool. I'll just use RPM versioning
of releases to compensate for RC or any other version number that may exist.
So, this one will be:
libapreq2-2.04_dev-2.3.src.rpm
^ ^
| |
| --------------> libapreq2 RC or intermediate version
----------------> RPM release
How does that sit with you?
--
Bojan
Re: [VOTE] 2.04_03-dev release candidate
Posted by Joe Schaefer <jo...@sunstarsys.com>.
Bojan Smojver <bo...@rexursive.com> writes:
> Just a question related to versioning. The RC2 was called
> 2.04-dev-rc2, where this one is 2.04_03-dev. Is this on purpose
> (i.e. a new naming convention)?
CPAN requires the version component of a developer tarball
to include a '_' character. We've been doing this munging
ever since 2.01, but this will thankfully be the last time.
See the RELEASE document in cvs for details on the process.
> What is the actually released one going to be called?
The tarball will be released as libapreq2-2.04_03-dev.tar.gz,
but it's going to be formally called the 2.04-dev release.
> I'm trying to determine all this for the RPM spec file. The version of
> the RPM should contain all the information it can (e.g. _dev_rc2),
I recommend not including release candidate data in the spec file.
Is it possible to just remove the "_03" from the tarball's name
before building the rpm?
--
Joe Schaefer
Re: [VOTE] 2.04_03-dev release candidate
Posted by Bojan Smojver <bo...@rexursive.com>.
Just a question related to versioning. The RC2 was called 2.04-dev-rc2, where
this one is 2.04_03-dev. Is this on purpose (i.e. a new naming convention)?
What is the actually released one going to be called?
I'm trying to determine all this for the RPM spec file. The version of the RPM
should contain all the information it can (e.g. _dev_rc2), but the tarball
expands to -dev directory in all cases, so there must be an algorithm in place
to convert one to the other within the spec file. It is always good to know the
convention so that the spec file does not have to be changed from release to
release.
Quoting Joe Schaefer <jo...@sunstarsys.com>:
>
> Release candidate #3, built from current-cvs,
> is available
>
> http://cvs.apache.org/~joes/libapreq2-2.04_03-dev.tar.gz
> http://cvs.apache.org/~joes/libapreq2-2.04_03-dev.tar.gz.asc
>
> Please double-check this tarball and signature,
> (and committers please vote) as I'd like to send
> this off to CPAN and the ASF mirrors as-is.
>
> Thanks!
> --
> Joe Schaefer
>
>
--
Bojan