invalid package name in package.provided, while building glibc after busybox

[edannenberg]

invalid package name in package.provided, while building glibc after busybox

[UralZima]

these messages repeating for every newly built container, containing error about every newly installed packages. Maybe it is because of ::gentoo tag?

[edannenberg]

Those are just warnings from portage so it didn't affect the build. As to why, I'm not sure, the duplicated en_US.UTF-8 UTF-8 warning suggests something is up with the build container state. Try:

$ ./build.sh clean
$ ./build.sh -C build bb

This should rebuild everything from scratch. If the issue persists it might be related to your namespace rename, which would be a bug. Can you push your changes to a fork so I can take a closer look?

[UralZima]

I did a clean before building.
I issued a command ./build.sh build bb/mariadb
I am very sorry, I don't learned git and it is hard for me to commit, fork, push etc.
I just gzipped my folder and uploaded it here: https://www.sendspace.com/file/k7qmew
What was changed:
0. Removed all unnecessary packages folders. Renamed namespace to bb

1. Added lines to bob's build.sh to upgrade gcc
2. removed --clean and --strict from flaggie, it caused errors when I updated_keywords to (maybe) insexistent packages
3. created php5.6 container separately
4. updated mariadb to ~amd64 version
5. busybox changed builder to bob
6. etc
   For you it's easier to diff and see what changed.

P.S. you have a bug in nginx-php5.6 container, the etc folder inside contains php-fpm5.5 folder with php-fpm.conf, and it fails to start

Thank you for help

[UralZima]

I can't rebuild everything, because it is still building all the day... very long time. Even right now I am only at openssl

[edannenberg]

Ok, no worries. I'll take a look tomorrow. Thanks for the php5.6 hint, will fix.

Try to learn git sometime in the future, makes live so much easier and takes no time at all. :)

Some resources:

https://guides.github.com/activities/hello-world/
https://wildlyinaccurate.com/a-hackers-guide-to-git/

[UralZima]

Thanks for links. Will take a look. I hope this package.provides errors will not fail my build and I don't need to build it again from scratch... I get bunch of such errors after each container was built. I think it is because ::gentoo tag is added to this file, on my host I don't have any tag after package name. Can't find it where it can add in your code

[edannenberg]

Once you have all the binary packages in your local cache a rebuild should be much quicker. Out of curiosity, what are your build host specs? (cpu/ram)

[UralZima]

amd 4 core/16GB, gentoo hardened. Running inside KVM/Qemu right now temporarily...

[edannenberg]

Ah the KVM stuff might be the bottle neck then. As I said, for every installed package a binary package is placed in ./gentoo-bb/tmp/packages. This is mounted by all build containers as Portage's PACKAGES folder, so unless you switch use flags there shouldn't be any compiling on rebuilds except for new packages.

[UralZima]

Yeah I know, very useful feature :) ok will see how it will finish and run. Thanks
P.S. right now it is building bash, it includes coreutils package as dep, so it seems I can remove busybox from my packages. Will try to rebuild all.. In that way, it must use binary packages too, I think

[UralZima]

Hi. I tried again to build all from scratch, removed tmp and did clean. Renamed namespace back to gentoobb. I receive same package.provided errors, right after building busybox with bob. And receive errors for every package. Seems to be a bug

[UralZima]

Hm. Maybe it is because I added -v to emerge default flags. I think this is issue

[UralZima]

Hi. Sorry about to be confused with that issue. I just wanted emerge to be more verbose and this caused an error.
Also, wanted to add, in file I uploaded to sendspace, I have modified nginx container, coz in mwa overlay it don't have all modules, and pagespeed outdated. I modified it to use ~amd64 nginx and download and compile latest pagespeed. Please take a look. You may commit these changes to your nginx package, just need to add pagespeed version to some variable and get version online. It builds and runs successfully, latest nginx with latest pagespeed.