https://packages.gentoo.org/packages/updated # last update was Sun, 15 Oct 2017 06:30 So it are has the brokens now.
On infra-status: packages.gentoo.org hardware issues There are hardware problems on the host where packages.gentoo.org is hosted. For the duration, updates may be delayed and/or the site may be unavailable.
*** Bug 640086 has been marked as a duplicate of this bug. ***
The short story is that the existing deployment is years out of date in terms of elasticsearch. The code doesn't support newer versions and a fair amount of work has gone into updating the codebase for elasticsearch 6. The longer story: The es-6-update has mostly concluded. The service doesn't have great test coverage, so updates basically involve code deployment and manual feature verification. Currently the list of broken features is: - changelogs do not show up (I believe this is due to the way my containers are constructed; as changelogs currently require git.) - local use flags do not work properly. Unsure what the root cause is here. - Searches are no longer partial matching . I believe this is caused by ES compat changes moving from fulltext search to keywords. I think this is fixable with some updated index mappings. There are a few other deployment related changes that need to occur as well. Until then I don't think we can move the service; so it continues to operate poorly on its existing host.
I think development is mostly complete on ES 6. Working on deploying a version to packagetest, and then we can get folks to use it. Once it appears to be working we can switch over. -A
Please try the version on 'packagestest.gentoo.org'. Don't rely on it yet (it is not "productionalized") but I want to see if folks can spot anything broken. -A
List of stuff left to make ptest into p.g.o. 1) Networking. There was a regression in IP tables I spotted earlier in deployment. I think it was config management or cron related, waiting to see if it triggers again. 2) Logging. The existing p.g.o doesn't do log rotation sufficiently. 3) starting-on-boot. I think ES doesn't start on boot; but we need it to. 4) Moving ES to specific disks. This is simply a configuration change in the ES config. 5) Moving ES configs to source control. Right now its a bespoke setup, should be config managed.
(In reply to Alec Warner from comment #5) > Please try the version on 'packagestest.gentoo.org'. > > Don't rely on it yet (it is not "productionalized") but I want to see if > folks can spot anything broken. > > -A Looks like there is some peculiar duplication (which did occur in p.g.o originally too) on packages like https://packagestest.gentoo.org/packages/dev-libs/protobuf . What's weirder is what's going on with the sparc stable/unstable flag at the top .. Otherwise, much snappier, and thanks for the efforts!
https://packagestest.gentoo.org/packages/updated not working, but the atom feed does! Is there a 'hook' for Removed Packages at the bottom of the Added/Updated/<here> list? If just for completeness?! The atom feeds are quite useful, in addition to robbat's emails on the -dev ML! HTH & TIA!
(In reply to Michael Everitt (IRC: veremitz) from comment #7) > (In reply to Alec Warner from comment #5) > > Please try the version on 'packagestest.gentoo.org'. > > > > Don't rely on it yet (it is not "productionalized") but I want to see if > > folks can spot anything broken. > > > > -A > > Looks like there is some peculiar duplication (which did occur in p.g.o > originally too) on packages like > https://packagestest.gentoo.org/packages/dev-libs/protobuf . What's weirder > is what's going on with the sparc stable/unstable flag at the top .. > > Otherwise, much snappier, and thanks for the efforts! Querying the underlying data: irb(main):007:0> Package.find_by(:atom, 'dev-libs/protobuf').versions[1] => #<Version {created_at: 2018-02-17 09:01:27 UTC, updated_at: 2018-02-17 09:01:27 UTC, version: "3.5.1.1", package: "dev-libs/protobuf", atom: "dev-libs/protobuf-3.5.1.1", sort_key: 0, slot: "0", subslot: "15", eapi: nil, keywords: ["~alpha", "~amd64", "~arm", "~arm64", "~hppa", "~ia64", "~mips", "~ppc", "~ppc64", "~sh", "sparc", "x86", "~amd64-linux", "~arm-linux", "~x86-linux", "~x64-macos", "~x86-macos"], masks: [], use: ["emacs", "examples", "static-libs", "test", "zlib", "abi_x86_32", "abi_x86_64", "abi_x86_x32", "abi_mips_n32", "abi_mips_n64", "abi_mips_o32", "abi_ppc_32", "abi_ppc_64", "abi_s390_32", "abi_s390_64"], restrict: [], properties: [], metadata_hash: "c361fb78fe436e5b36d5a811d8f3efa3", id: "t4D_omEBVmcq-e-aK2Gx"}> irb(main):008:0> Package.find_by(:atom, 'dev-libs/protobuf').versions[0] => #<Version {created_at: 2018-02-17 00:54:00 UTC, updated_at: 2018-02-17 00:54:00 UTC, version: "3.5.1.1", package: "dev-libs/protobuf", atom: "dev-libs/protobuf-3.5.1.1", sort_key: 0, slot: "0", subslot: "15", eapi: nil, keywords: ["~alpha", "~amd64", "~arm", "~arm64", "~hppa", "~ia64", "~mips", "~ppc", "~ppc64", "~sh", "~sparc", "x86", "~amd64-linux", "~arm-linux", "~x86-linux", "~x64-macos", "~x86-macos"], masks: [], use: ["emacs", "examples", "static-libs", "test", "zlib", "abi_x86_32", "abi_x86_64", "abi_x86_x32", "abi_mips_n32", "abi_mips_n64", "abi_mips_o32", "abi_ppc_32", "abi_ppc_64", "abi_s390_32", "abi_s390_64"], restrict: [], properties: [], metadata_hash: "61a0ee90b0c79eed5a636034aa5fe07f", id: "eH9AoWEBVmcq-e-a5AN0"}> So possibly the difference in metadata_hash values is causing the duplication.
(In reply to Michael Everitt (IRC: veremitz) from comment #8) > https://packagestest.gentoo.org/packages/updated not working, but the atom > feed does! > > Is there a 'hook' for Removed Packages at the bottom of the > Added/Updated/<here> list? If just for completeness?! The atom feeds are > quite useful, in addition to robbat's emails on the -dev ML! > > HTH & TIA! I'm not planning on adding features right now; I'd like to get it working first. -A
(In reply to Michael Everitt (IRC: veremitz) from comment #8) > https://packagestest.gentoo.org/packages/updated not working, but the atom > feed does! This url should be fixed. > > Is there a 'hook' for Removed Packages at the bottom of the > Added/Updated/<here> list? If just for completeness?! The atom feeds are > quite useful, in addition to robbat's emails on the -dev ML! > > HTH & TIA!
(In reply to Alec Warner from comment #6) > List of stuff left to make ptest into p.g.o. > > 1) Networking. There was a regression in IP tables I spotted earlier in > deployment. I think it was config management or cron related, waiting to see > if it triggers again. Could not repro, deferred. > > 2) Logging. The existing p.g.o doesn't do log rotation sufficiently. Solveable with logrorate rules, so not a blocker for deploy. > > 3) starting-on-boot. I think ES doesn't start on boot; but we need it to. Fixed. > > 4) Moving ES to specific disks. This is simply a configuration change in the > ES config. ES was already on the right disks, so I'll incur a brief downtime at a later date to move it to the 'right location'. > > 5) Moving ES configs to source control. Right now its a bespoke setup, > should be config managed. Mostly done via 3; I need to document how to prep the ES container.
