2:42 p.m.
I still can not get mythtv 0.24.2 to build for Fedora 15. For whatever
reason configure doesn't find perl-Format-DateTime-ISO8601 even though
it's installed. I can build it locally using mock so I have to assume
it's some sort of kernel issue with the build server.
So my question is: Can I do the builds and have someone upload them to
the repository this one time?
Thanks,
Richard
3:18 p.m.
2012/4/10 Richard Shaw <hobbes1069(a)gmail.com>:
I still can not get mythtv 0.24.2 to build for Fedora 15. For
whatever
reason configure doesn't find perl-Format-DateTime-ISO8601 even though
it's installed. I can build it locally using mock so I have to assume
it's some sort of kernel issue with the build server.
So my question is: Can I do the builds and have someone upload them to
the repository this one time?
There is an override repository that is used to upload fedora package
that are not yet updates or updates-testing repository.
Where is the perl-Format-DateTime-ISO8601 package currently ? Are you
sure it's not already there from the root.log ?
Thx
Nicolas (kwizart).
3:22 p.m.
On Tue, Apr 10, 2012 at 10:18 AM, Nicolas Chauvet <kwizart(a)gmail.com> wrote:
2012/4/10 Richard Shaw <hobbes1069(a)gmail.com>:
> I still can not get mythtv 0.24.2 to build for Fedora 15. For whatever
> reason configure doesn't find perl-Format-DateTime-ISO8601 even though
> it's installed. I can build it locally using mock so I have to assume
> it's some sort of kernel issue with the build server.
>
> So my question is: Can I do the builds and have someone upload them to
> the repository this one time?
There is an override repository that is used to upload fedora package
that are not yet updates or updates-testing repository.
Where is the perl-Format-DateTime-ISO8601 package currently ? Are you
sure it's not already there from the root.log ?
Yes, the package builds fine locally for F15 in mock on a F16 host.
I've also setup a minimal CentOS 6 virtual machine and was able to
build a package that way as well but the build still fails on the
build server and I've verified the package is installed in the root
log[1].
I filed an infrastructure bug[2] a while ago but I'm not sure anyone
knows what to do with it.
Thanks,
Richard
[1]
http://buildsys.rpmfusion.org/logs/fedora-15-rpmfusion_free/12699-mythtv-...
[2] https://bugzilla.rpmfusion.org/show_bug.cgi?id=2185
3:34 p.m.
On Tue, Apr 10, 2012 at 10:22:59AM -0500, Richard Shaw wrote:
Yes, the package builds fine locally for F15 in mock on a F16 host.
I've also setup a minimal CentOS 6 virtual machine and was able to
build a package that way as well but the build still fails on the
build server and I've verified the package is installed in the root
log[1].
One reason for failings build which are works fine locally may be
an SMP compilant issue in the upstream make files.
In this case I will suggest to remove the %{?_smp_mflags} in the
SPEC file. If the build works fine after then, you should open an
upstream bug report.
Best Regards:
Jochen Schmitt
3:41 p.m.
On Tue, Apr 10, 2012 at 10:34 AM, Jochen Schmitt <Jochen(a)herr-schmitt.de> wrote:
On Tue, Apr 10, 2012 at 10:22:59AM -0500, Richard Shaw wrote:
> Yes, the package builds fine locally for F15 in mock on a F16 host.
> I've also setup a minimal CentOS 6 virtual machine and was able to
> build a package that way as well but the build still fails on the
> build server and I've verified the package is installed in the root
> log[1].
One reason for failings build which are works fine locally may be
an SMP compilant issue in the upstream make files.
In this case I will suggest to remove the %{?_smp_mflags} in the
SPEC file. If the build works fine after then, you should open an
upstream bug report.
In this case the failure is happening in "configure". Basically the
configure script does a simple perl module import test to make sure
the needed perl modules are available and for some reason this is only
failing on the build server and only for F15 whereas it succeeds
locally in mock as well as on a CentOS 6 virtual machine using mock.
Thanks,
Richard
3:44 p.m.
2012/4/10 Richard Shaw <hobbes1069(a)gmail.com>:
On Tue, Apr 10, 2012 at 10:34 AM, Jochen Schmitt
<Jochen(a)herr-schmitt.de> wrote:
> On Tue, Apr 10, 2012 at 10:22:59AM -0500, Richard Shaw wrote:
>
>> Yes, the package builds fine locally for F15 in mock on a F16 host.
>> I've also setup a minimal CentOS 6 virtual machine and was able to
>> build a package that way as well but the build still fails on the
>> build server and I've verified the package is installed in the root
>> log[1].
>
> One reason for failings build which are works fine locally may be
> an SMP compilant issue in the upstream make files.
>
> In this case I will suggest to remove the %{?_smp_mflags} in the
> SPEC file. If the build works fine after then, you should open an
> upstream bug report.
In this case the failure is happening in "configure". Basically the
configure script does a simple perl module import test to make sure
the needed perl modules are available and for some reason this is only
failing on the build server and only for F15 whereas it succeeds
locally in mock as well as on a CentOS 6 virtual machine using mock.
Which failure
?
You can do a
./configure || cat config.log
It might depend on the locale used by the builder or some options.
BTW Does it really worth to update mythtv in F-15 ?
Nicolas (kwizart)
4:05 p.m.
On Tue, Apr 10, 2012 at 10:44 AM, Nicolas Chauvet <kwizart(a)gmail.com> wrote:
Which failure ?
You can do a
./configure || cat config.log
Since it only happens on the build server I can't run configure
manually but if you do a search for the first instance of DateTime in
the build log[3] then you'll see what I'm talking about. Here's the
snippet:
+ ./configure --prefix=/builddir/build/BUILD/MythTV-mythtv-c239b59/fakeroot/usr
--libdir=/usr/lib --libdir-name=lib --enable-mytharchive
--enable-mythbrowser --enable-mythgallery --enable-exif
--enable-new-exif --enable-mythgame --enable-mythmusic
--enable-mythnews --enable-mythvideo --enable-mythweather
--enable-mythzoneminder --enable-mythnetvision --enable-opengl
--enable-libvisual --enable-fftw --enable-sdl
WARNING: disabling MythWeather; missing DateTime::Format::ISO8601
It might depend on the locale used by the builder or some options.
BTW Does it really worth to update mythtv in F-15 ?
No, it's not a requirement but as 0.25 was just released I'd like to
leave a decently up-to-date version in F15 and I don't like leaving
problems like this because you never know when you might run into it
again.
Thanks,
Richard
[3]
http://buildsys.rpmfusion.org/logs/fedora-15-rpmfusion_free/12699-mythtv-...
6:02 p.m.
On 04/10/2012 06:05 PM, Richard Shaw wrote:
On Tue, Apr 10, 2012 at 10:44 AM, Nicolas
Chauvet<kwizart(a)gmail.com> wrote:
> Which failure ?
> You can do a
> ./configure || cat config.log
Since it only happens on the build server I can't run configure
manually but if you do a search for the first instance of DateTime in
the build log[3] then you'll see what I'm talking about. Here's the
snippet:
+ ./configure --prefix=/builddir/build/BUILD/MythTV-mythtv-c239b59/fakeroot/usr
--libdir=/usr/lib --libdir-name=lib --enable-mytharchive
--enable-mythbrowser --enable-mythgallery --enable-exif
--enable-new-exif --enable-mythgame --enable-mythmusic
--enable-mythnews --enable-mythvideo --enable-mythweather
--enable-mythzoneminder --enable-mythnetvision --enable-opengl
--enable-libvisual --enable-fftw --enable-sdl
WARNING: disabling MythWeather; missing DateTime::Format::ISO8601
[cut]
For what it's worth, I can confirm that the SRPM builds on a "real"
F15/x86_64 and using mock/i386/rpmfusion_free on the same host.
What happens if you run the perl test directly in the spec file?
Something like
%prep
...
perl -e 'use DateTime::Format::ISO8601;'
echo "Found, status: $?"
This should hopefully give a hint about the availability of the perl
package (?)
6:46 p.m.
On Tue, Apr 10, 2012 at 1:02 PM, Alec Leamas <leamas.alec(a)gmail.com> wrote:
What happens if you run the perl test directly in the spec file?
Something
like
%prep
...
perl -e 'use DateTime::Format::ISO8601;'
echo "Found, status: $?"
Well I just tried but now for some reason I'm getting an ssl handshake
error when I try "make build":
OpenSSL.SSL.Error: [('SSL routines', 'SSL3_READ_BYTES', 'sslv3 alert
certificate expired'), ('SSL routines', 'SSL3_WRITE_BYTES', 'ssl
handshake failure')]
make: *** [plague] Error 1
I haven't changed anything on my end so I'm not sure what's going on.
Richard
6:52 p.m.
On Tue, Apr 10, 2012 at 1:46 PM, Richard Shaw <hobbes1069(a)gmail.com> wrote:
On Tue, Apr 10, 2012 at 1:02 PM, Alec Leamas
<leamas.alec(a)gmail.com> wrote:
> What happens if you run the perl test directly in the spec file? Something
> like
>
> %prep
> ...
> perl -e 'use DateTime::Format::ISO8601;'
> echo "Found, status: $?"
Well I just tried but now for some reason I'm getting an ssl handshake
error when I try "make build":
OpenSSL.SSL.Error: [('SSL routines', 'SSL3_READ_BYTES', 'sslv3 alert
certificate expired'), ('SSL routines', 'SSL3_WRITE_BYTES', 'ssl
handshake failure')]
make: *** [plague] Error 1
Ok, my .rpmfusion.cert expired but the error message isn't terribly
helpful. Building now.
Richard
7:13 p.m.
Thanks to Alec for suggesting a way to capture the error message!
Here it is:
+ perl -e 'use DateTime::Format::ISO8601;'
The 'regex' parameter ("(?x-ism:^ (\d{4}) (\d\d) (\d\d) $)") to
DateTime::Format::Builder::Parser::create_single_parser was an
'unknown', which is not one of the allowed types: scalarref
at /usr/lib/perl5/vendor_perl/Params/ValidatePP.pm line 650
Params::Validate::__ANON__('The \'regex\' parameter ("(?x-ism:^
(\d{4}) (\d\d) (\d\d) $)"...') called at
/usr/lib/perl5/vendor_perl/Params/ValidatePP.pm line 494
Params::Validate::_validate_one_param('Regexp=REGEXP(0xa3de900)',
'HASH(0xa3ec050)', 'HASH(0xa3aab08)', 'The \'regex\'
parameter
("(?x-ism:^ (\d{4}) (\d\d) (\d\d) $)")') called at
/usr/lib/perl5/vendor_perl/Params/ValidatePP.pm line 353
Params::Validate::validate('ARRAY(0xa386368)', 'HASH(0xa385c98)')
called at /usr/share/perl5/vendor_perl/DateTime/Format/Builder/Parser.pm
line 311
DateTime::Format::Builder::Parser::create_single_parser(undef,
'params', 'ARRAY(0xa3de890)', 'length', 8, 'regex',
'Regexp=REGEXP(0xa3de900)') called at
/usr/share/perl5/vendor_perl/DateTime/Format/Builder/Parser.pm line
501
DateTime::Format::Builder::Parser::sort_parsers('DateTime::Format::Builder::Parser',
'HASH(0xa38d760)', 'ARRAY(0xa38cd20)') called at
/usr/share/perl5/vendor_perl/DateTime/Format/Builder/Parser.pm line
397
DateTime::Format::Builder::Parser::create_multiple_parsers('DateTime::Format::Builder::Parser',
'HASH(0xa38d760)', 'HASH(0xa3de8e0)', 'HASH(0xa3de9c0)',
'HASH(0xa3dea70)', 'HASH(0xa3deb10)', 'HASH(0xa3debc0)',
'HASH(0xa3dece0)', 'HASH(0xa3dedf0)', ...) called at
/usr/share/perl5/vendor_perl/DateTime/Format/Builder/Parser.pm line
600
DateTime::Format::Builder::Parser::create_parser('DateTime::Format::Builder::Parser',
'ARRAY(0xa2ac098)', 'HASH(0xa3de8e0)', 'HASH(0xa3de9c0)',
'HASH(0xa3dea70)', 'HASH(0xa3deb10)', 'HASH(0xa3debc0)',
'HASH(0xa3dece0)', 'HASH(0xa3dedf0)', ...) called at
/usr/share/perl5/vendor_perl/DateTime/Format/Builder.pm line 156
DateTime::Format::Builder::create_parser('DateTime::Format::Builder',
'ARRAY(0xa3e9f28)') called at
/usr/share/perl5/vendor_perl/DateTime/Format/Builder.pm line 174
DateTime::Format::Builder::create_end_parser('DateTime::Format::Builder',
'ARRAY(0xa3e9f28)') called at
/usr/share/perl5/vendor_perl/DateTime/Format/Builder.pm line 104
DateTime::Format::Builder::create_class(undef, 'parsers',
'HASH(0xa3eb750)') called at
/usr/share/perl5/vendor_perl/DateTime/Format/ISO8601.pm line 175
require DateTime/Format/ISO8601.pm called at -e line 1
main::BEGIN() called at
/usr/share/perl5/vendor_perl/DateTime/Format/ISO8601.pm line 0
eval {...} called at
/usr/share/perl5/vendor_perl/DateTime/Format/ISO8601.pm line 0
Compilation failed in require at -e line 1.
BEGIN failed--compilation aborted at -e line 1.
Thanks,
Richard
1:48 p.m.
On Tue, 10 Apr 2012 14:13:25 -0500
Richard Shaw <hobbes1069(a)gmail.com> wrote:
Thanks to Alec for suggesting a way to capture the error message!
Here it is:
+ perl -e 'use DateTime::Format::ISO8601;'
The 'regex' parameter ("(?x-ism:^ (\d{4}) (\d\d) (\d\d) $)") to
DateTime::Format::Builder::Parser::create_single_parser was an
'unknown', which is not one of the allowed types: scalarref
at /usr/lib/perl5/vendor_perl/Params/ValidatePP.pm line 650
Params::Validate::__ANON__('The \'regex\' parameter
("(?x-ism:^ (\d{4}) (\d\d) (\d\d) $)"...') called at
/usr/lib/perl5/vendor_perl/Params/ValidatePP.pm line 494
https://rt.cpan.org/Public/Bug/Display.html?id=74725
Which version of Params::Validate is the builder using?
perl -MParams::Validate -e 'print "$Params::Validate::VERSION\n"'
Latest stable version for F-15 is 0.99, which I think should be OK, but
there's a broken 1.01 in updates-testing. The builders aren't pulling
that one in, are they?
Paul.
2:22 p.m.
On Wed, Apr 11, 2012 at 7:48 AM, Paul Howarth <paul(a)city-fan.org> wrote:
Latest stable version for F-15 is 0.99, which I think should be OK,
but
there's a broken 1.01 in updates-testing. The builders aren't pulling
that one in, are they?
They do pull from updates-testing. RPM Fusion (kwizart) frequently
rebuilds all the kmods against each of the new kernels that land in
updates-testing, so if I were to guess, that's probably why the
builders are set up the way they are. One of the confusing factors in
this situation is that the local mock-rpmfusion-free/nonfree packages
do not include updates-testing, so it wasn't obvious how to duplicate
this error locally with mock.[1]
Paul, do you think it's feasible that we can fix Params::Validate for
F15? Check out Ralf's comment in Bodhi[2]. I'm trying to figure out
what breaks with 1.02.
- Ken
[1] https://bugzilla.rpmfusion.org/2270
[2] https://admin.fedoraproject.org/updates/FEDORA-2012-1417
2:37 p.m.
2012/4/11 Ken Dreyer <ktdreyer(a)ktdreyer.com>:
On Wed, Apr 11, 2012 at 7:48 AM, Paul Howarth
<paul(a)city-fan.org> wrote:
> Latest stable version for F-15 is 0.99, which I think should be OK, but
> there's a broken 1.01 in updates-testing. The builders aren't pulling
> that one in, are they?
They do pull from updates-testing. RPM Fusion (kwizart) frequently
rebuilds all the kmods against each of the new kernels that land in
updates-testing, so if I were to guess, that's probably why the
This is wrong,
the kernel is fetched from a dedicated override repo.
But indeed, updates-testing is enabled by default on the builder to
save maintenance when a new RPM Fusion package need to be rebuilt
against a new fedora package (thinking about all the freeworld variant
and etc).
This has to stay like that until there is a per-users way to handle
overrides (using bodhi).
I can only agree this is not ideal.
builders are set up the way they are. One of the confusing factors
in
this situation is that the local mock-rpmfusion-free/nonfree packages
do not include updates-testing, so it wasn't obvious how to duplicate
this error locally with mock.[1]
You make the assumption that mock-rpmfusion-free
is only aimed to
reproduce RPM Fusion builder behaviour.
This is wrong, one can expect to build only with fully validated
packages from both fedora and rpmfusion.
Reproducing the buildsys behaviour is only one way to use the mock cfg
and is not the default.
So I'm closing the bug.
Paul, do you think it's feasible that we can fix Params::Validate
for
F15? Check out Ralf's comment in Bodhi[2]. I'm trying to figure out
what breaks with 1.02.
If one package is broken in f15 updates-testing it can also
be withdrawn.
Nicolas (kwizart)
3:52 p.m.
On Wed, 11 Apr 2012 08:22:09 -0600
Ken Dreyer <ktdreyer(a)ktdreyer.com> wrote:
On Wed, Apr 11, 2012 at 7:48 AM, Paul Howarth
<paul(a)city-fan.org>
wrote:
> Latest stable version for F-15 is 0.99, which I think should be OK,
> but there's a broken 1.01 in updates-testing. The builders aren't
> pulling that one in, are they?
They do pull from updates-testing. RPM Fusion (kwizart) frequently
rebuilds all the kmods against each of the new kernels that land in
updates-testing, so if I were to guess, that's probably why the
builders are set up the way they are. One of the confusing factors in
this situation is that the local mock-rpmfusion-free/nonfree packages
do not include updates-testing, so it wasn't obvious how to duplicate
this error locally with mock.[1]
Paul, do you think it's feasible that we can fix Params::Validate for
F15? Check out Ralf's comment in Bodhi[2]. I'm trying to figure out
what breaks with 1.02.
It'll be hard to update F-15 to 1.02 as it requires
Module::Implementation, which requires an updated Module::Runtime,
which includes some incompatible changes that would necessitate
updating a bunch of other modules too.
I think the simplest solution would be to get Ralf to unpush the 1.01
update so it disappears from updates-testing.
Paul.
9:15 p.m.
On Wed, 2012-04-11 at 14:48 +0100, Paul Howarth wrote:
On Tue, 10 Apr 2012 14:13:25 -0500
Richard Shaw <hobbes1069(a)gmail.com> wrote:
> Thanks to Alec for suggesting a way to capture the error message!
>
> Here it is:
> + perl -e 'use DateTime::Format::ISO8601;'
> The 'regex' parameter ("(?x-ism:^ (\d{4}) (\d\d) (\d\d) $)") to
> DateTime::Format::Builder::Parser::create_single_parser was an
> 'unknown', which is not one of the allowed types: scalarref
> at /usr/lib/perl5/vendor_perl/Params/ValidatePP.pm line 650
> Params::Validate::__ANON__('The \'regex\' parameter
> ("(?x-ism:^ (\d{4}) (\d\d) (\d\d) $)"...') called at
> /usr/lib/perl5/vendor_perl/Params/ValidatePP.pm line 494
https://rt.cpan.org/Public/Bug/Display.html?id=74725
Which version of Params::Validate is the builder using?
perl -MParams::Validate -e 'print "$Params::Validate::VERSION\n"'
Latest stable version for F-15 is 0.99, which I think should be OK, but
there's a broken 1.01 in updates-testing. The builders aren't pulling
that one in are they?
after update my vm with F15 to update testing I hit the same error .
And not in F15 update .
--
Sérgio M. B.
11:06 p.m.
On Wed, 11 Apr 2012 22:15:57 +0100
Sérgio Basto <sergio(a)serjux.com> wrote:
On Wed, 2012-04-11 at 14:48 +0100, Paul Howarth wrote:
> On Tue, 10 Apr 2012 14:13:25 -0500
> Richard Shaw <hobbes1069(a)gmail.com> wrote:
>
> > Thanks to Alec for suggesting a way to capture the error message!
> >
> > Here it is:
> > + perl -e 'use DateTime::Format::ISO8601;'
> > The 'regex' parameter ("(?x-ism:^ (\d{4}) (\d\d) (\d\d) $)")
to
> > DateTime::Format::Builder::Parser::create_single_parser was an
> > 'unknown', which is not one of the allowed types: scalarref
> > at /usr/lib/perl5/vendor_perl/Params/ValidatePP.pm line 650
> > Params::Validate::__ANON__('The \'regex\' parameter
> > ("(?x-ism:^ (\d{4}) (\d\d) (\d\d) $)"...') called at
> > /usr/lib/perl5/vendor_perl/Params/ValidatePP.pm line 494
>
> https://rt.cpan.org/Public/Bug/Display.html?id=74725
>
> Which version of Params::Validate is the builder using?
>
> perl -MParams::Validate -e 'print "$Params::Validate::VERSION\n"'
>
> Latest stable version for F-15 is 0.99, which I think should be OK,
> but there's a broken 1.01 in updates-testing. The builders aren't
> pulling that one in are they?
after update my vm with F15 to update testing I hit the same error .
And not in F15 update .
Ralf seems to have deleted the 1.01 update now so it should disappear
from updates-testing after the next push.
Anyone with the updates-testing build will need to downgrade.
Paul.
11:18 p.m.
On Thu, 2012-04-12 at 00:06 +0100, Paul Howarth wrote:
On Wed, 11 Apr 2012 22:15:57 +0100
Sérgio Basto <sergio(a)serjux.com> wrote:
> On Wed, 2012-04-11 at 14:48 +0100, Paul Howarth wrote:
> > On Tue, 10 Apr 2012 14:13:25 -0500
> > Richard Shaw <hobbes1069(a)gmail.com> wrote:
> >
> > > Thanks to Alec for suggesting a way to capture the error message!
> > >
> > > Here it is:
> > > + perl -e 'use DateTime::Format::ISO8601;'
> > > The 'regex' parameter ("(?x-ism:^ (\d{4}) (\d\d) (\d\d)
$)") to
> > > DateTime::Format::Builder::Parser::create_single_parser was an
> > > 'unknown', which is not one of the allowed types: scalarref
> > > at /usr/lib/perl5/vendor_perl/Params/ValidatePP.pm line 650
> > > Params::Validate::__ANON__('The \'regex\' parameter
> > > ("(?x-ism:^ (\d{4}) (\d\d) (\d\d) $)"...') called at
> > > /usr/lib/perl5/vendor_perl/Params/ValidatePP.pm line 494
> >
> > https://rt.cpan.org/Public/Bug/Display.html?id=74725
> >
> > Which version of Params::Validate is the builder using?
> >
> > perl -MParams::Validate -e 'print
"$Params::Validate::VERSION\n"'
> >
> > Latest stable version for F-15 is 0.99, which I think should be OK,
> > but there's a broken 1.01 in updates-testing. The builders aren't
> > pulling that one in are they?
>
> after update my vm with F15 to update testing I hit the same error .
> And not in F15 update .
Ralf seems to have deleted the 1.01 update now so it should disappear
from updates-testing after the next push.
Anyone with the updates-testing build will need to downgrade.
I read in https://rt.cpan.org/Public/Bug/Display.html?id=74725 Fixed in
1.02, if 1.02 fixed this, why not update to 1.02 ?
--
Sérgio M. B.
12:49 p.m.
On Thu, 12 Apr 2012 00:18:15 +0100
Sérgio Basto <sergio(a)serjux.com> wrote:
On Thu, 2012-04-12 at 00:06 +0100, Paul Howarth wrote:
> On Wed, 11 Apr 2012 22:15:57 +0100
> Sérgio Basto <sergio(a)serjux.com> wrote:
>
> > On Wed, 2012-04-11 at 14:48 +0100, Paul Howarth wrote:
> > > On Tue, 10 Apr 2012 14:13:25 -0500
> > > Richard Shaw <hobbes1069(a)gmail.com> wrote:
> > >
> > > > Thanks to Alec for suggesting a way to capture the error
> > > > message!
> > > >
> > > > Here it is:
> > > > + perl -e 'use DateTime::Format::ISO8601;'
> > > > The 'regex' parameter ("(?x-ism:^ (\d{4}) (\d\d) (\d\d)
$)")
> > > > to DateTime::Format::Builder::Parser::create_single_parser
> > > > was an 'unknown', which is not one of the allowed types:
> > > > scalarref at /usr/lib/perl5/vendor_perl/Params/ValidatePP.pm
> > > > line 650 Params::Validate::__ANON__('The \'regex\'
parameter
> > > > ("(?x-ism:^ (\d{4}) (\d\d) (\d\d) $)"...') called at
> > > > /usr/lib/perl5/vendor_perl/Params/ValidatePP.pm line 494
> > >
> > > https://rt.cpan.org/Public/Bug/Display.html?id=74725
> > >
> > > Which version of Params::Validate is the builder using?
> > >
> > > perl -MParams::Validate -e 'print
> > > "$Params::Validate::VERSION\n"'
> > >
> > > Latest stable version for F-15 is 0.99, which I think should be
> > > OK, but there's a broken 1.01 in updates-testing. The builders
> > > aren't pulling that one in are they?
> >
> > after update my vm with F15 to update testing I hit the same
> > error . And not in F15 update .
>
> Ralf seems to have deleted the 1.01 update now so it should
> disappear from updates-testing after the next push.
>
> Anyone with the updates-testing build will need to downgrade.
I read in https://rt.cpan.org/Public/Bug/Display.html?id=74725 Fixed
in 1.02, if 1.02 fixed this, why not update to 1.02 ?
As mentioned in an earlier message, it'll be hard to update F-15 to
1.02 as it requires Module::Implementation, which requires an updated
Module::Runtime, which includes some incompatible changes that would
necessitate updating a bunch of other modules too.
The broken build has now disappeared from updates-testing anyway, at
least on the master mirror.
Paul.
3:27 p.m.
On Tue, Apr 10, 2012 at 05:18:37PM +0200, Nicolas Chauvet wrote:
There is an override repository that is used to upload fedora
package
that are not yet updates or updates-testing repository.
Where is the perl-Format-DateTime-ISO8601 package currently ? Are you
sure it's not already there from the root.log ?
A package must be in the update repository to be visible for the
builder. Pakcages which are not in the updates repositroy will get
accessable to the builder after a buildroot overrides. A buildroot
overrides can be initiate on the web interface of bodhi. To initiate
a buildroot overirides, you must be the (co-)maintainer of the package
or a provenpackager.
Best Regards:
Jochen Schmitt
3:47 p.m.
On Tue, Apr 10, 2012 at 8:42 AM, Richard Shaw <hobbes1069(a)gmail.com> wrote:
I still can not get mythtv 0.24.2 to build for Fedora 15. For
whatever
reason configure doesn't find perl-Format-DateTime-ISO8601 even though
it's installed. I can build it locally using mock so I have to assume
it's some sort of kernel issue with the build server.
So my question is: Can I do the builds and have someone upload them to
the repository this one time?
Looking at the configure script, the error in your build.log is misleading...
check_pl_lib "Date::Manip" || disable_weather "Date::Manip"
check_pl_lib "XML::Simple" || disable_weather "XML::Simple"
check_pl_lib "XML::XPath" || disable_weather "XML::XPath"
check_pl_lib "Image::Size" || disable_weather "Image::Size"
check_pl_lib "DateTime::Format::ISO8601" ||
disable_weather "DateTime::Format::ISO8601"
check_pl_lib "SOAP::Lite" || disable_weather "SOAP::Lite"
check_pl_lib "JSON" || disable_weather "JSON"
fi
if any of those libs are missing, the configure script will run
disable_weather "DateTime::Format::ISO8601" , even if
DateTime::Format::ISO8601 is not at fault.
Sounds like a bug in mythplugins.
3:49 p.m.
On Tue, Apr 10, 2012 at 9:47 AM, Ken Dreyer <ktdreyer(a)ktdreyer.com> wrote:
On Tue, Apr 10, 2012 at 8:42 AM, Richard Shaw
<hobbes1069(a)gmail.com> wrote:
> I still can not get mythtv 0.24.2 to build for Fedora 15. For whatever
> reason configure doesn't find perl-Format-DateTime-ISO8601 even though
> it's installed. I can build it locally using mock so I have to assume
> it's some sort of kernel issue with the build server.
>
> So my question is: Can I do the builds and have someone upload them to
> the repository this one time?
Looking at the configure script, the error in your build.log is misleading...
Actually, I misread the code, sorry for the noise :) It looks like it
would display the proper missing module. And on my F15 box here:
$ perl -e "use DateTime::Format::ISO8601" && echo module present
module present
So I'm not sure what's going wrong.
- Ken
4607
days inactive
4609
days old
rpmfusion-developers@lists.rpmfusion.org
21 comments
7 participants
participants (7)
-
Alec Leamas -
Jochen Schmitt -
Ken Dreyer -
Nicolas Chauvet -
Paul Howarth -
Richard Shaw -
Sérgio Basto