Files are copied from .git

[noamgot]

Starting from v0.42.1, I noticed rattler-build tries to copy files from the .git folder, even though according to the docs they are not supposed to be copied (https://rattler.build/latest/internals/#general-file-filtering)

Here's a minimal reproducible example (using a small pixi project):

pixi.toml

[workspace]
channels = ["conda-forge"]
name = "rattler-build-bugs"
platforms = ["linux-64"]
version = "1.2.3"

[environments]
build = { features = ["build"], no-default-feature = true }

[dependencies]
numpy = ">=2.3.2,<3"
pandas = ">=2.3.1,<3"
requests = ">=2.32.4,<3"


## Build Feature
[feature.build.dependencies]
rattler-build = "0.42.*"

[feature.build.tasks]
_build-mkdir = "mkdir -p ./__localbuild__/conda/"

[feature.build.tasks.build]
cmd = "rattler-build build --package-format tar-bz2 -r recipe.yml --output-dir ./__localbuild__/conda/ --no-test"
depends-on = ["_build-mkdir"]
description = "build the conda package"

The recipe.yaml that I used:

context: {}

package:
  name: rattler-build-bugs
  version: 1.2.3

source:
  path: .

build:
  script: python -m pip install --no-deps --ignore-installed -vv .
  noarch: python

requirements:
  host:
  - python =3.11
  - pip
  - hatch

  run:
  - numpy >=2.3.2,<3
  - pandas >=2.3.1,<3
  - requests >=2.32.4,<3

about:
  homepage: https://www.example.com
  summary: amazing summary

To reproduce you should:

1. create a git repo with some commits
2. run pixi run build -vv - you should see many messages of this form:

2025-08-19T15:32:28.703505Z DEBUG rattler_build::source::copy_dir: Failed to copy metadata for ".../rattler-build-bugs/__localbuild__/conda/bld/rattler-build_rattler-build-bugs_1755617547/work/.git/objects/60/1c93b4c6c02c051b8d4736934fa93f4dcac8b8" Os { code: 13, kind: PermissionDenied, message: "Permission denied" }

3. downgrade rattler-build to 0.41.* and see that these logs are gone

p.s. - the build operation doesn't work for now on my machine (I'm trying to create an example for a different issue that I encountered), but it works just enough to make this point

[wolfv]

Just to be sure - the .git files should not have ended up in the package, for sure, and I assume that is the case, right?

We do filter these files here when copying to the package:

rattler-build/src/packaging/file_mapper.rs

Lines 73 to 74 in 1ec6fe5

	if relative_path.components().any(|c| {
	let s = c.as_os_str().to_string_lossy();

However, I agree, that for path sources we could also filter the .git folder.

[wolfv]

To put it in different words, I am not sure what the best behavior is here. Because IMO it's also confusing if the path source does not copy all the files. We could also introduce globs for the path source with some defaults, so that it can be overridden.

I'll have to think about it a bit.

[noamgot]

@wolfv correct, in my case there's no need to copy the .git files whatsoever.
However, I can think of cases where it will be needed - e.g. when using hatch-vcs to determine the version of the pakcage based on git tags. I'm not too familiar with the internals of this, but I think it makes sense to give some control to the user about it (either opt-in or opt-out)