| Age | Commit message (Collapse) | Author |
|---|
|
The latest source on fluent-bit already applied the patch to fix the
issue.
|
|
|
|
The log from building this package is quite long, and when error occurred,
its quite hard to tell which command that cause it.
This changes add log before executing each command in build function
to help investigate any build error later.
|
|
Using java-environment will install JDK v20 which cause the package
failed to build with the following error:
Unknown Kotlin JVM target: 20
This changes set the java dependency to v17.
|
|
Since we generate the patch twice, while the git version is the same,
the signature will become invalid.
Hence, we need to increase the package release.
|
|
Previosly, the default config.yaml receivers for syslog is using
"type: files" that read /var/log/messages and /var/log/syslog.
In Arch Linux, those files are not exist anymore, so we replace the
with "type: systemd_journald" to make all the system logs forwarded to
Cloud Logging.
# Conflicts:
# .SRCINFO
# PKGBUILD
|
|
In the all task, use the long options and add --nobuild.
|
|
In the chrootpkg task, in case the _build/root already exist, the pacman
sync is not updated, so we need to update the chroot system
(root and $USER) to latest first before running makechrootpkg.
In the patch task, generate integrity checksum without extracting the
source and building the package.
|
|
Previosly, the default config.yaml receivers for syslog is using
"type: files" that read /var/log/messages and /var/log/syslog.
In Arch Linux, those files are not exist anymore, so we replace the
with "type: systemd_journald" to make all the system logs forwarded to
Cloud Logging.
|
|
Since v2.11.0, the collectd is not part of the git submodules anymore [1].
[1]: https://github.com/GoogleCloudPlatform/ops-agent/commit/a2778bd4cba3
|
|
This architecture tested by other Arch user [1].
[1] https://aur.archlinux.org/packages/google-cloud-ops-agent-git#comment-916934
|
|
This build is introduced on commit fcb087b5 [1].
[1] https://github.com/GoogleCloudPlatform/ops-agent/commit/fcb087b5fcab52541472fa2b66c438145d209eb2
|
|
Since PR #1038 merged to master, the build failed due to the $DESTDIR
now replaced with "/work" for building with docker. [1]
[1] https://github.com/GoogleCloudPlatform/ops-agent/pull/1038#discussion_r1106206200
|
|
When building with git v2.38.1 or latest version, the build will fail
with
fatal: transport 'file' not allowed
This is due to security issue in git submodule [1].
While at it, update the version to the latest one.
[1] https://lore.kernel.org/lkml/xmqq4jw1uku5.fsf@gitster.g/
|
|
Since the issue regarding this patch [1] has been fixed, we did not
need it anymore.
[1] https://github.com/GoogleCloudPlatform/ops-agent/issues/249#issuecomment-1075184604
|
|
|
|
Instead of uncompressing the final build output file (from build.sh),
we sync the staging to $pkgdir.
This require adding rsync to makedeps.
While at it, use single chown statement for all $pkgdir.
|
|
This reverts commit 62550ad000eff79f08d156c14bf672ddec63d45a.
The /usr directory exist, we just missing the systemd package when
testing build with chroot which cause all files that should be installed
under "pkg-config systemd --variable=systemdsystemunitdir"
installed under root.
|
|
The devtools allow package to build in clean chroot [1].
In this build, we bind the host go, go-build cache, and .gradle cache
to the chroot/build to minimize re-downloading Go and Java dependencies
on the next rebuild.
[1] https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot
|
|
The goal is to allow us to inspect the installed files and their
structure.
The DESTDIR directory contains installed files, similar to prefix.
If its not set, the directory will be created under /tmp with random
name.
This also fix build error due to META-INF directory exist on the second
or next build.
|
|
On latest version, the installed package does not populate the /usr
directory.
|
|
|
|
|
|
The java tools only required to build not to running ops-agent, unless
user want to monitor jmx stats on host.
|
|
|
|
|
|
|
|
This release update the patch format using "git diff".
|
|
Currently, running default otelopscol (opentelemetry-operations-collector)
will thrown the errors as described in [1].
This patch fix it by removing scraper "process" and "processes" from
hostmetrics and by changing default log level from "info" to "error".
[1] https://cloud.google.com/logging/docs/agent/ops-agent/troubleshooting#log-spam
|
|
This is the ops-agent that are part of the Google Cloud Operations
product suite (specifically Cloud Logging and Cloud Monitoring) [1].
This package replace stackdriver-collectd in the AUR [2].
[1] https://cloud.google.com/stackdriver/docs/solutions/agents/ops-agent/
[2] https://aur.archlinux.org/packages/stackdriver-collectd/
|