bazeldnf icon indicating copy to clipboard operation
bazeldnf copied to clipboard

Build multi-arch base containers based on RPM with bazel.

Results 15 bazeldnf issues
Sort by recently updated
recently updated
newest added

Public repos pass certificate verification using the system's trusted root certificates. Private repos may require a Certificate Authority that is not in the system's trusted root certificates. Although some users...

I have a repo where rpm files are kept at a separate location from the metadata: ```yaml repositories: - arch: x86_64 baseurl: https://REPO_URL/ name: qemu-kvm-x86_64 gpgcheck: 0 repo_gpgcheck: 0 ```...

Inspired in https://github.com/rmohr/bazeldnf/pull/61, I'll migrate to bazel 7 while keeping both bzlmod and non bzlmod support working, only updating the minimal amount of packages to not make the MR too...

When upgrading to bazeldnf v0.5.9-rc2 cross building for different arches fails to find included header files. I specifically tested this when building kubevirt with https://github.com/kubevirt/kubevirt/pull/10490: ``` INFO: From ImageLayer cmd/libguestfs/version-container-layer.tar:...

I'm in the process of planning a migration of my teams monorepo from bazel WORKSPACE to [bzlmod](https://bazel.build/docs/bzlmod). Bazeldnf is one dependency that does not yet support bzlmod. If you are...

This is the first step towards enabling bzlmod support. On this branch, you can add the following to your .bazelrc (or add it to your `bazel build` flags): .bazelrc ```...

A colleague has reported hitting the following error: ``` INFO[0004] Resolving repomd.xml from http:///repodata/repomd.xml INFO[0004] Loading primary file from http:///repodata/-primary.xml.gz Error: failed to fetch primary.xml for : failed to get...

Bumps [golang.org/x/net](https://github.com/golang/net) from 0.5.0 to 0.7.0. Commits 8e2b117 http2/hpack: avoid quadratic complexity in hpack decoding 547e7ed http2: avoid referencing ResponseWrite.Write parameter after returning 39940ad html: parse comments per HTML spec...

dependencies

Set proper Typeflag and Size when handling hardlinks and regular files. Noticed that by visual code inspection: in the original code, `tarHeader.Typeflag` was overwritten with `tar.TypeReg` when handling an entry...

Fedora mirrors tend to remove outdated packages relatively quickly. Is there an established workflow for caching those to a mirror?