debian-devel  

Messages by Thread

• Please Test Pam 1.7.0 from experimental Sam Hartman
• Is HURD's lack of HOST_NAME_MAX and PATH_MAX a good architectural approach Sam Hartman
  • Re: Is HURD's lack of HOST_NAME_MAX and PATH_MAX a good architectural approach Samuel Thibault
  • Re: Is HURD's lack of HOST_NAME_MAX and PATH_MAX a good architectural approach Sam Hartman
  • Re: Is HURD's lack of HOST_NAME_MAX and PATH_MAX a good architectural approach Samuel Thibault
  • Re: Is HURD's lack of HOST_NAME_MAX and PATH_MAX a good architectural approach Sam Hartman
  • Re: Is HURD's lack of HOST_NAME_MAX and PATH_MAX a good architectural approach Samuel Thibault
  • Re: Is HURD's lack of HOST_NAME_MAX and PATH_MAX a good architectural approach Guillem Jover
  • Re: Is HURD's lack of HOST_NAME_MAX and PATH_MAX a good architectural approach Janneke Nieuwenhuizen
  • Re: Is HURD's lack of HOST_NAME_MAX and PATH_MAX a good architectural approach Simon Josefsson
  • Re: Is HURD's lack of HOST_NAME_MAX and PATH_MAX a good architectural approach Julien Plissonneau Duquène
  • Re: Is HURD's lack of HOST_NAME_MAX and PATH_MAX a good architectural approach Samuel Thibault
• DEP-14 branches explained visually Otto Kekäläinen
• sbuild wiki page - cross compiling section query Phil Wyett
  • Re: sbuild wiki page - cross compiling section query Jochen Sprickerhof
  • Re: sbuild wiki page - cross compiling section query Phil Wyett
  • Re: sbuild wiki page - cross compiling section query Phil Wyett
  • Re: sbuild wiki page - cross compiling section query Andrey Rakhmatullin
  • Re: sbuild wiki page - cross compiling section query Jochen Sprickerhof
  • Re: sbuild wiki page - cross compiling section query Andrey Rakhmatullin
  • Re: sbuild wiki page - cross compiling section query Jochen Sprickerhof
  • Re: sbuild wiki page - cross compiling section query Phil Wyett
  • Re: sbuild wiki page - cross compiling section query Phil Wyett
  • Re: sbuild wiki page - cross compiling section query Andrey Rakhmatullin
• Bug#1093576: ITP: golang-github-opencoff-go-sieve -- SIEVE cache - simpler than LRU Eric Dorland
• Fwd: warzone2100_4.5.5-1_amd64.changes REJECTED Russell Coker
  • Re: Fwd: warzone2100_4.5.5-1_amd64.changes REJECTED Andrey Rakhmatullin
  • Re: Fwd: warzone2100_4.5.5-1_amd64.changes REJECTED Fabian Grünbichler
  • Re: Fwd: warzone2100_4.5.5-1_amd64.changes REJECTED Soren Stoutner
• Bug#1093427: ITP: td1.8.11 -- telegram database library (development headers, API/ABI v1.8.11) Mike Gabriel
  • Re: Bug#1093427: ITP: td1.8.11 -- telegram database library (development headers, API/ABI v1.8.11) Mike Gabriel
• Bug#1093417: (no subject) MuntasirSZN
• Mentors. Confirmed packages needing DD review and possible sponsorship Phil Wyett
  • Re: Mentors. Confirmed packages needing DD review and possible sponsorship Simon Josefsson
  • Re: Mentors. Confirmed packages needing DD review and possible sponsorship Phil Wyett
  • Re: Mentors. Confirmed packages needing DD review and possible sponsorship Phil Wyett
  • Mentors. Confirmed packages needing DD review and possible sponsorship Phil Wyett
• Bug#1093379: ITP: golang-github-santhosh-tekuri-jsonschema -- JSONSchema Validation using Go Simon Josefsson
• Bug#1093373: general: lots of dependencies missing fro upgrade on trixie Cristobal Lanzagorta
  • Re: Bug#1093373: general: lots of dependencies missing fro upgrade on trixie Soren Stoutner
  • Bug#1093373: marked as done (general: lots of dependencies missing fro upgrade on trixie) Debian Bug Tracking System
• Bug#1093319: ITP: golang-github-go-http-utils-headers -- HTTP header constants for Gophers (Go library) Simon Josefsson
• Bug#1093317: ITP: golang-github-saracen-fastzip -- opinionated Zip archiver with a focus on speed (Go library) Simon Josefsson
• Bug#1093316: ITP: golang-github-saracen-zipextra -- utils for ZIP archive format's "Extra Fields" (Go library) Simon Josefsson
• Bug#1093313: ITP: golang-gitlab-gitlab-org-fleeting-fleeting -- abstraction for cloud providers' instance groups for GitLab Simon Josefsson
• Bug#1093309: ITP: golang-github-sourcegraph-conc -- Better structured concurrency for go Simon Josefsson
• Bug#1093302: ITP: mage -- a Make/rake-like dev tool using Go Simon Josefsson
• Bug#1093298: ITP: golang-github-denisbrodbeck-machineid -- Get the unique machine id of any host Simon Josefsson
• Bug#1093280: ITP: pysequoia -- OpenPGP in Python using Sequoia PGP Jelmer Vernooij
• lintian.debian.org is ON (Re: lintian.debian.org off ?) Otto Kekäläinen
• Bug#1093266: ITP: golang-github-owenrumney-go-sarif -- Sarif: Static Analysis Results Interchange Format (Go library) Simon Josefsson
• Bug#1093262: ITP: golang-github-spdx-tools-golang -- Collection of Go packages to work with SPDX files Simon Josefsson
• Bug#1093261: ITP: golang-github-anchore-go-struct-converter -- help migrate between different versioned Go structs (Go library) Simon Josefsson
• Bug#1093260: ITP: golang-github-kimmachinegun-automemlimit -- Automatically set GOMEMLIMIT to match Linux cgroups(7) memory limit Daniel Swarbrick
• Bug#1093259: ITP: golang-github-spdx-gordf -- parse RDF files using RDF/XML format (Go library) Simon Josefsson
• Bug#1093257: ITP: golang-github-edwarnicke-gitoid -- Golang libraries for computing git object ids (gitoids) Simon Josefsson
• Bug#1093252: ITP: witness -- pluggable framework for software supply chain risk management Simon Josefsson
• Bug#1093250: ITP: golang-github-invopop-jsonschema -- Generate JSON Schemas from Go types Simon Josefsson
• Bug#1093249: ITP: golang-github-wk8-go-ordered-map -- Optimal implementation of ordered maps for Golang Simon Josefsson
• Bug#1093248: ITP: golang-github-bahlo-generic-list-go -- Go container/list but with generics Simon Josefsson
• Canonical way for a package to set an environment variable Soren Stoutner
  • Re: Canonical way for a package to set an environment variable Santiago Vila
  • Re: Canonical way for a package to set an environment variable Soren Stoutner
• Bug#1093226: ITP: golang-github-coder-quartz -- A Go time testing library for writing deterministic unit tests Daniel Swarbrick
• Bug#1093223: RFH: tbsync -- Thunderbird/Lightning Add-On to support MS Exchange Calendar etc. Mechtilde Stehmann
• How to conditionally patch a package based on architecture with debhelper? Chris Knadle
  • Re: How to conditionally patch a package based on architecture with debhelper? Andrey Rakhmatullin
  • How to conditionally patch a package based on architecture with debhelper? Simon Richter
  • Re: How to conditionally patch a package based on architecture with debhelper? Chris Knadle
  • Re: How to conditionally patch a package based on architecture with debhelper? Andrey Rakhmatullin
  • Re: How to conditionally patch a package based on architecture with debhelper? Chris Knadle
  • What is going on with atomics? (was: How to conditionally patch a package based on architecture with debhelper?) Johannes Schauer Marin Rodrigues
  • Re: What is going on with atomics? (was: How to conditionally patch a package based on architecture with debhelper?) Andrey Rakhmatullin
  • Re: What is going on with atomics? (was: How to conditionally patch a package based on architecture with debhelper?) Ángel
  • Re: What is going on with atomics? (was: How to conditionally patch a package based on architecture with debhelper?) Alexandre Rossi
  • Re: What is going on with atomics? Simon Richter
  • Re: What is going on with atomics? Wookey
  • Re: What is going on with atomics? Simon McVittie
  • Re: What is going on with atomics? Theodore Ts'o
  • Re: What is going on with atomics? Colin Watson
  • Re: What is going on with atomics? Matthias Klose
  • Re: What is going on with atomics? John Scott
  • Re: What is going on with atomics? Simon Richter
  • Re: What is going on with atomics? Johannes Schauer Marin Rodrigues
  • Re: What is going on with atomics? Simon Richter
  • Re: What is going on with atomics? Johannes Schauer Marin Rodrigues
  • Re: What is going on with atomics? Simon Richter
  • Re: What is going on with atomics? Vincent Danjean
  • Re: How to conditionally patch a package based on architecture with debhelper? Ben Collins
  • Re: How to conditionally patch a package based on architecture with debhelper? Chris Knadle
  • Re: How to conditionally patch a package based on architecture with debhelper? Andrey Rakhmatullin
  • Re: How to conditionally patch a package based on architecture with debhelper? Johannes Schauer Marin Rodrigues
  • Re: How to conditionally patch a package based on architecture with debhelper? Guillem Jover
• Bug#1093218: ITP: image-garden -- tool for creating test virtual machines Zygmunt Krynicki
• Bug#1093213: ITP: teakra -- DSi/3DS DSP emulator, (dis)assembler, and tester Andrea Pappacoda
• Bug#1093183: ITP: libpdl-opt-simplex-perl -- PDL implementation of simplex optimization algorithm Ed J
• Bug#1093186: ITP: libpdl-io-hdf-perl -- PDL interface to read and write HDF4 files with the SD, VS, and V interfaces. Ed J
• Bug#1093185: ITP: libpdl-graphics-trid-perl -- PDL 3D interface Ed J
• Bug#1093184: ITP: libpdl-io-idl-perl -- Read IDL(tm) data files into PDL Ed J
• Bug#1093181: ITP: libpdl-transform-color-perl -- Useful color system conversions for PDL Ed J
• Bug#1093182: ITP: libpdl-transform-proj4-perl -- PDL::Transform interface to the PROJ library Ed J
• Bug#1093180: ITP: libpdl-io-gd-perl -- PDL interface to the GD image library Ed J
• Bug#1093179: ITP: libpdl-perldl2-perl -- Simple shell (version 2) for PDL using Devel::REPL Ed J
• Bug#1093177: ITP: libpdl-gsl-perl -- PDL interface to the GNU Scientific Library Ed J
• Bug#1093178: ITP: libpdl-io-envi-perl -- Read ENVI data into PDL Ed J
• Bug#1093176: ITP: libpdl-io-dicom-perl -- Read 16-bit gray level Dicom images into PDL. Ed J
• Bug#1093174: ITP: libpdl-graphics-simple-perl -- Simple backend-independent plotting for PDL Ed J
• Bug#1093172: ITP: libpdl-graphics-colorspace-perl -- PDL implementation of Graphics::ColorObject Ed J
• Bug#1093168: ITP: libpdl-fit-perl -- Fitting functions for PDL. Ed J
• Removing manpages from libpam-modules to improve multi-arch Sam Hartman
  • Documentation field? (Was: Removing manpages from libpam-modules to improve multi-arch) Gioele Barabucci
  • Re: Documentation field? (Was: Removing manpages from libpam-modules to improve multi-arch) Ben Collins
  • Re: Removing manpages from libpam-modules to improve multi-arch Marvin Renich
  • Re: Removing manpages from libpam-modules to improve multi-arch Sam Hartman
  • Re: Removing manpages from libpam-modules to improve multi-arch G. Branden Robinson
  • Re: Removing manpages from libpam-modules to improve multi-arch Sam Hartman
  • Re: Removing manpages from libpam-modules to improve multi-arch G. Branden Robinson
  • write the fine manual (was Re: Removing manpages from libpam-modules to improve multi-arch) Jonathan Dowland
  • Re: write the fine manual (was Re: Removing manpages from libpam-modules to improve multi-arch) G. Branden Robinson
  • Re: write the fine manual (was Re: Removing manpages from libpam-modules to improve multi-arch) Russ Allbery
  • Re: write the fine manual (was Re: Removing manpages from libpam-modules to improve multi-arch) Theodore Ts'o
  • Re: Removing manpages from libpam-modules to improve multi-arch Marvin Renich
  • Re: Removing manpages from libpam-modules to improve multi-arch Russ Allbery
  • Re: Removing manpages from libpam-modules to improve multi-arch Simon Richter
  • Re: Removing manpages from libpam-modules to improve multi-arch Russ Allbery
  • Re: Removing manpages from libpam-modules to improve multi-arch Simon Richter
  • Re: Removing manpages from libpam-modules to improve multi-arch Bálint Réczey
  • Re: Removing manpages from libpam-modules to improve multi-arch Russ Allbery
  • Re: Removing manpages from libpam-modules to improve multi-arch Sam Hartman
  • Re: Removing manpages from libpam-modules to improve multi-arch Helmut Grohne
  • Bug#1093222: Minimizing build-arch for pam Sam Hartman
  • Re: Bug#1093222: Minimizing build-arch for pam Simon McVittie
  • Re: Bug#1093222: Minimizing build-arch for pam Sam Hartman
  • Re: Bug#1093222: Minimizing build-arch for pam Niels Thykier
  • Re: Removing manpages from libpam-modules to improve multi-arch Guillem Jover
  • Re: Removing manpages from libpam-modules to improve multi-arch Sam Hartman
  • Re: Removing manpages from libpam-modules to improve multi-arch Simon McVittie
  • Re: Removing manpages from libpam-modules to improve multi-arch Sam Hartman
  • Re: Removing manpages from libpam-modules to improve multi-arch Simon Richter
  • Re: Removing manpages from libpam-modules to improve multi-arch Simon McVittie
  • Re: Removing manpages from libpam-modules to improve multi-arch Jonas Smedegaard
• Bug#1093128: ITP: rust-cargo-vendor-filterer -- `cargo vendor`, but with filtering for platforms and more Julian Andres Klode
• Debian/Linux's NPU support? M. Zhou
• Bug#1093076: ITP: openvino -- open-source toolkit for optimizing and deploying AI inference M. Zhou
• Re: New Delegation: tag2upload delegates Thorsten Glaser
  • Re: New Delegation: tag2upload delegates Andreas Tille
  • Re: New Delegation: tag2upload delegates Sean Whitton
  • Re: New Delegation: tag2upload delegates Johannes Schauer Marin Rodrigues
  • Re: New Delegation: tag2upload delegates Thorsten Glaser
  • Re: New Delegation: tag2upload delegates G. Branden Robinson
• Let's make 2025 a year when code reviews became common in Debian Otto Kekäläinen
  • Re: Let's make 2025 a year when code reviews became common in Debian Chris Hofstaedtler
  • Re: Let's make 2025 a year when code reviews became common in Debian Otto Kekäläinen
  • Re: Let's make 2025 a year when code reviews became common in Debian Andrey Rakhmatullin
  • Re: Let's make 2025 a year when code reviews became common in Debian Andreas Tille
  • Re: Let's make 2025 a year when code reviews became common in Debian Gioele Barabucci
  • Re: Let's make 2025 a year when code reviews became common in Debian Andreas Tille
  • Re: Let's make 2025 a year when code reviews became common in Debian gregor herrmann
  • Re: Let's make 2025 a year when code reviews became common in Debian Andreas Tille
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonas Smedegaard
  • Re: Let's make 2025 a year when code reviews became common in Debian Julien Plissonneau Duquène
  • Re: Let's make 2025 a year when code reviews became common in Debian Julien Plissonneau Duquène
  • Re: Let's make 2025 a year when code reviews became common in Debian Gioele Barabucci
  • Re: Let's make 2025 a year when code reviews became common in Debian Andreas Tille
  • Re: Let's make 2025 a year when code reviews became common in Debian Gioele Barabucci
  • Re: Let's make 2025 a year when code reviews became common in Debian Andreas Tille
  • Re: Let's make 2025 a year when code reviews became common in Debian Matthew Vernon
  • +1 (Re: Let's make 2025 a year when code reviews became common in Debian) Holger Levsen
  • Re: Let's make 2025 a year when code reviews became common in Debian Gioele Barabucci
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonas Smedegaard
  • Re: Let's make 2025 a year when code reviews became common in Debian Simon Josefsson
  • Re: Let's make 2025 a year when code reviews became common in Debian Philipp Kern
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonas Smedegaard
  • Re: Let's make 2025 a year when code reviews became common in Debian Simon McVittie
  • Re: Let's make 2025 a year when code reviews became common in Debian Julien Plissonneau Duquène
  • Re: Let's make 2025 a year when code reviews became common in Debian Julien Plissonneau Duquène
  • Re: Let's make 2025 a year when code reviews became common in Debian Otto Kekäläinen
  • Re: Let's make 2025 a year when code reviews became common in Debian Sam Hartman
  • Re: Let's make 2025 a year when code reviews became common in Debian Julien Plissonneau Duquène
  • Re: Let's make 2025 a year when code reviews became common in Debian Gioele Barabucci
  • Re: Let's make 2025 a year when code reviews became common in Debian Julien Plissonneau Duquène
  • Re: Let's make 2025 a year when code reviews became common in Debian Jeremy Stanley
  • Re: Let's make 2025 a year when code reviews became common in Debian Johannes Schauer Marin Rodrigues
  • Re: Let's make 2025 a year when code reviews became common in Debian Gioele Barabucci
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonathan Dowland
  • Re: Let's make 2025 a year when code reviews became common in Debian Colin Watson
  • Re: Let's make 2025 a year when code reviews became common in Debian Wookey
  • Re: Let's make 2025 a year when code reviews became common in Debian Otto Kekäläinen
  • Re: Let's make 2025 a year when code reviews became common in Debian Wookey
  • Re: Let's make 2025 a year when code reviews became common in Debian Sam Hartman
  • Re: Let's make 2025 a year when code reviews became common in Debian Colin Watson
  • +1 (Re: Let's make 2025 a year when code reviews became common in Debian) Holger Levsen
  • Re: Let's make 2025 a year when code reviews became common in Debian Gioele Barabucci
  • Re: Let's make 2025 a year when code reviews became common in Debian Sam Hartman
  • Re: Let's make 2025 a year when code reviews became common in Debian Jonas Smedegaard
  • Re: Let's make 2025 a year when code reviews became common in Debian Sam Hartman
  • Re: Let's make 2025 a year when code reviews became common in Debian Otto Kekäläinen
  • Re: Let's make 2025 a year when code reviews became common in Debian Wookey
  • Re: Let's make 2025 a year when code reviews became common in Debian Xiyue Deng
  • Re: Let's make 2025 a year when code reviews became common in Debian Colin Watson

• Earlier messages
• Later messages