[gentoo-proxy-maint] Testing environment

[gentoo-proxy-maint] Testing environment

[David Denoncin]

[-- Attachment #1: Type: text/plain, Size: 868 bytes --]

Dear all,

I would like to understand how to set up an acceptable testing environment for amd64 packages as per
https://wiki.gentoo.org/wiki/Package_testing

and would like to go the chroot way. Is the following setup acceptable
to test an ebuild for pkg-cat/pkg-name ?

1- download stage3, unpack it in /mnt/gentoo
2- chroot in /mnt/gentoo 
3- emerge --sync, select stable profile default/linux/amd64/17.1
4- update the @world set 
5- add to make.conf the variables from https://wiki.gentoo.org/wiki/Package_testing (with multilib-strict added to FEATURES)
6- emerge portage with the gentoo_dev use flag 
7- emerge pkg-cat/pkg-name (ebuild test)
8- runtime test the package if needed

I'm happy to amend the above checklist however appropriate and
contribute to the wikipage related to chroot.

Thanks in advance,
Best regards,
David Denoncin.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

Re: [gentoo-proxy-maint] Testing environment

[Joonas Niilola]

[-- Attachment #1.1: Type: text/plain, Size: 1922 bytes --]

Hey,

On 5/22/20 9:17 AM, David Denoncin wrote:
> Dear all,
>
> I would like to understand how to set up an acceptable testing environment for amd64 packages as per
> https://wiki.gentoo.org/wiki/Package_testing
>
> and would like to go the chroot way. Is the following setup acceptable
> to test an ebuild for pkg-cat/pkg-name ?

If you have no plans to keep on contributing, but want to test just one
change/ebuild, you can do that in a local overlay and by prepending
those settings to your emerge once. Setting up a chroot, container/etc
is time-consuming and in my opinion not worth it for a single package.
However if you intend to keep on writing ebuilds, then go for it, but
bear in mind you have then two "systems" to keep updated.

You may also be interested in dev-python/ebuildtester for random
occassional, but thorough testings.

>
> 1- download stage3, unpack it in /mnt/gentoo
> 2- chroot in /mnt/gentoo 
> 3- emerge --sync, select stable profile default/linux/amd64/17.1
> 4- update the @world set 
> 5- add to make.conf the variables from https://wiki.gentoo.org/wiki/Package_testing (with multilib-strict added to FEATURES)

Note that if you plan on keeping the chroot alive, these will become
your default settings when you update @world, or emerge dependencies.
Which will most likely become a painful road.

I have a "testmerge.sh" shell script that runs "emerge -1av --onlydeps
--with-test-deps "$@"", then sources a different make.conf (with
stricter FEATURES etc) before running "emerge -1av "$@"".


> 6- emerge portage with the gentoo_dev use flag 
> 7- emerge pkg-cat/pkg-name (ebuild test)
> 8- runtime test the package if needed
>
> I'm happy to amend the above checklist however appropriate and
> contribute to the wikipage related to chroot.
>
> Thanks in advance,
> Best regards,
> David Denoncin.


Overall sounds good.

-- juippis



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 642 bytes --]

Re: [gentoo-proxy-maint] Testing environment

[David Denoncin]

[-- Attachment #1: Type: text/plain, Size: 2222 bytes --]

On 20-05-22 16:17:20, Joonas Niilola wrote:
> If you have no plans to keep on contributing, but want to test just one
> change/ebuild, you can do that in a local overlay and by prepending
> those settings to your emerge once. Setting up a chroot, container/etc
> is time-consuming and in my opinion not worth it for a single package.
> However if you intend to keep on writing ebuilds, then go for it, but
> bear in mind you have then two "systems" to keep updated.
Hopefully I will be able to make time to continue to contribute, that is the plan anyway :-). I have a spare machine for my
personal tests that I keep up to date or reinstall anyway ^^.

> You may also be interested in dev-python/ebuildtester for random
> occassional, but thorough testings.
Thanks, I overlooked this one.

> > 1- download stage3, unpack it in /mnt/gentoo
> > 2- chroot in /mnt/gentoo 
> > 3- emerge --sync, select stable profile default/linux/amd64/17.1
> > 4- update the @world set 
> > 5- add to make.conf the variables from https://wiki.gentoo.org/wiki/Package_testing (with multilib-strict added to FEATURES)

> Note that if you plan on keeping the chroot alive, these will become
> your default settings when you update @world, or emerge dependencies.
> Which will most likely become a painful road.
That would have been my second question. I tried that, and had to add 
tons of '-test' to package.use to get dev-python/quantities to be merged due to circular dependencies of several dev-python/? packages. 

In doing that I remarked that tests for python3.7 fails with '/dev/tty : No such device or address'. Am I missing something before chrooting ? (I did follow https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base before chrooting)

> I have a "testmerge.sh" shell script that runs "emerge -1av --onlydeps
> --with-test-deps "$@"", then sources a different make.conf (with
> stricter FEATURES etc) before running "emerge -1av "$@"".
Thanks for the tip. I am also writing some bash scripts to automate the overall process :-)

> Overall sounds good.
Thanks, I'll test that and post the relevant parts on https://wiki.gentoo.org/wiki/Chroot_for_package_testing

Best regards,
David.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

Re: [gentoo-proxy-maint] Testing environment

[Joonas Niilola]

[-- Attachment #1.1: Type: text/plain, Size: 476 bytes --]


On 5/22/20 5:42 PM, David Denoncin wrote:
>
> In doing that I remarked that tests for python3.7 fails with '/dev/tty : No such device or address'. Am I missing something before chrooting ? (I did follow https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base before chrooting)
>
Sorry I don't know (remember) about chroots, but it seems like a general
error. Maybe you can use mount -o rbind /dev and mount --make-rslave on
your hosts's /dev.

-- juippis



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 642 bytes --]