Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Build provenance and patch mapping for python 3.13.15 h254dcb4_103_cp313 on win-64

Cerrado
  • ¿Algo no está bien?
#956 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
build-system

Línea de trabajo

Start by locating the historical recipe and build records for python-3.13.15-h254dcb4_103_cp313 on win-64, then check whether the requested recipe commit, rendered variant, source digests, ordered patches, post-processing, CI identity, and output digest were recorded. Identify whether the CVE-2026-82049 fix was backported and where its change appears; report each requested record as available, unrecoverable, not generated, or unknown.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

question
Comment:

Hello, could you help identify the actual build inputs for the Python 3.13.15 Windows build103 and target SHA256 listed below? We have a historical candidate recipe, but cannot establish that it produced this artifact merely from its timestamp and build number. We are not asserting a confirmed exploitable issue in this build.

Could you provide the actual full recipe commit, rendered variant and recipe, source digests, ordered patches and any post-processing, together with the CI identity and output digest? In particular, please clarify whether the publicly documented tar hard-link fix for CVE-2026-82049 was backported and where the corresponding change can be found.

Existing build log exports or manifests with the output digest are welcome; an attestation is not required, and we are not requesting a rebuild. Please explicitly identify records that were not generated, are unrecoverable, or remain unknown. No package files, private source, or credentials are needed. Thank you.

Public release context (metadata only; archive not acquired):

  • product: FreeCAD
  • tag: 26.3rc2
  • commit: 9fb16e7f981adb09f7d7f130ce085d68e9825358
  • asset: FreeCAD_26.3rc2-Windows-x86_64.7z
  • asset_id: 652999133
  • metadata_size_bytes: 357086397
  • expected_sha256: cd75d3eb2ea27756f2b4677e0e356040765c4db41eda041d1bf94b555a7629d0
  • release_run_id: 39105123445
  • run_attempt: 1
  • windows_x64_job_id: 117609718862

Specific public target:

  • version: 3.13.15
  • build: h254dcb4_103_cp313
  • platform: win-64
  • filename: python-3.13.15-h254dcb4_103_cp313.conda
  • expected_sha256: 097e081574bf96282082915f78a83480361285137370c8cc35e2c51d693a0690
Lenguaje dominante
Shell
Estrellas
47
Forks
115
Merge medio
2 d 4 h
PR fusionados (30 d)
18

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de conda-forge/python-feedstock

Todos los issues de conda-forge/python-feedstock

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.