Package Details: perl-mojolicious 9.39-1

Git Clone URL: https://aur.archlinux.org/perl-mojolicious.git (read-only, click to copy)
Package Base: perl-mojolicious
Description: Real-time web framework
Upstream URL: https://metacpan.org/release/Mojolicious
Licenses: GPL, PerlArtistic
Submitter: Athaba
Maintainer: CommodoreCrunch
Last Packager: CommodoreCrunch
Votes: 57
Popularity: 0.000969
First Submitted: 2010-07-15 08:25 (UTC)
Last Updated: 2024-11-23 22:40 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

Martchus commented on 2020-11-14 20:46 (UTC) (edited on 2020-11-14 20:46 (UTC) by Martchus)

Please keep the tests. Upstream might test against different versions of dependencies so it is best to run tests after building the package. Tests can be easily skipped via makepkg's --nocheck flag if they are not wanted.

The build time of this package is actually not very long, even with the checks. But if you really want to avoid it, my binary repo contains this package: https://martchus.no-ip.biz/repo/arch/ownstuff

realh commented on 2020-11-14 20:30 (UTC)

Is there any chance you could skip the tests in the package build? They take far more time than all the other stages in upgrading the package put together, and it gets updated fairly often. I would have thought the tests should be unnecessary for end users as long as they've passed upstream and the package dependencies etc are correct.

zebulon commented on 2018-03-18 07:36 (UTC)

Well this is bizarre, this morning the package has compiled fine. The tst wich failed yesterday t/mojo/ioloop.t is now succeeding.

zebulon commented on 2018-03-17 20:24 (UTC) (edited on 2018-03-17 20:26 (UTC) by zebulon)

Test fails on my machine:

t/mojo/ioloop.t ............................ 32/?

Failed test 'stream has been resumed'
at t/mojo/ioloop.t line 246.
Failed test 'full message has been written'
at t/mojo/ioloop.t line 248.
got: undef
expected: 'works!'
Looks like you failed 2 tests of 50.
Test Summary Report

t/mojo/ioloop.t (Wstat: 512 Tests: 50 Failed: 2) Failed tests: 33, 35 Non-zero exit status: 2 Files=97, Tests=10890, 27 wallclock secs ( 0.69 usr 0.03 sys + 20.43 cusr 0.99 csys = 22.14 CPU) Result: FAIL Failed 1/97 test programs. 2/10890 subtests failed.

Anyone else sees that?

dracorp commented on 2017-09-25 19:54 (UTC)

https://gist.githubusercontent.com/dracorp/b4ad81e047c584c866b1345e94fd4381/raw/6e32a24d37909597b048af835b4dc557d8cfb398/PKGBUILD.perl-mojolicious

magnade commented on 2017-08-26 01:50 (UTC)

so some tips to save some time in the package updating you can replace the below 2 lines and then only have to update the pkgver and the hashs could also drop the md5sum and just use sha512 and again save some update time other than that works fine with version 7.43 source=('http://search.cpan.org/CPAN/authors/id/S/SR/SRI/Mojolicious-$pkgver.tar.gz') _distdir="Mojolicious-$pkgver"

jnbek commented on 2017-08-09 15:18 (UTC)

@all, I apologize regarding the status of this pkgbuild. My build server suffered a serious drive failure and has been out of commission. I have a temporary build server nearly ready and will update this and the others of my packages soon(tm)

Yurashina commented on 2017-08-08 10:44 (UTC)

Current version is 7.39, it's still work with the PKGBUILD of the 7.31 pkgver='7.39' source=('http://search.cpan.org/CPAN/authors/id/S/SR/SRI/Mojolicious-7.39.tar.gz') md5sums=('1c12d80f55ffef9d3ae01fe85839843e') sha512sums=('cbfaafb5b8356ee7ee1c6cbd2f370a59d61a27df7aad76a81ea5bfd9fb99fd01d86f1e583af381deac6b19d38a1970b678de4efe308ac0a19d1cba310d350b9d') _distdir="Mojolicious-7.39"

kyndair commented on 2017-07-31 15:40 (UTC)

current version is 7.37 the following changes in PKGBUIILD will work pkgver='7.37' source=('http://search.cpan.org/CPAN/authors/id/S/SR/SRI/Mojolicious-7.37.tar.gz') md5sums=('3c4ad17338465e9edc463f18619f15d8') sha256sums=('f73278c359e2eb3f8f5415e0e5dce418d5ef73adee96d53ae331ba876e360eea') _distdir="Mojolicious-7.37"

zebulon commented on 2017-05-07 21:56 (UTC)

Hi, Mojolicious has been updated to 7.31. 7.30 is not available anymore, leading to this PKGBUILD not to build.

« First ‹ Previous 1 2 3 4 5 6 Next › Last »