debian-devel  

Messages by Thread

• Bug#1100409: ITP: golang-github-microsoft-hcsshim -- Windows - Host Compute Service Shim Roland Mas
• Bug#1100411: ITP: python-cleware-traffic-light -- CLI tool to control the cleware USB traffic light Mike Gabriel
• Bug#1100410: ITP: jsoncons -- C++ header-only library for constructing JSON and JSON-like data formats Shengqi Chen
• Bug#1100406: ITP: golang-github-cyberphone-json-canonicalization -- JSON Canonicalization Scheme (JCS) Roland Mas
• Bug#1100388: ITP: golang-github-titanous-rocacheck -- Go package that checks if RSA keys are vulnerable to ROCA Luca Soler
• Bug#1100367: ITP: python-proton-vpn-gtk-app -- Proton VPN GTK app Josenilson Ferreira da Silva
• Bug#1100361: ITP: ec2-instance-connect -- Configures ssh daemon to accept EC2 Instance Connect ssh keys Miguel Landaeta
• Bug#1100340: ITP: zope.sqlalchemy -- Minimal Zope/SQLAlchemy transaction integration Maximilian Engelhardt
• Bug#1100186: ITP: mkdocs-glightbox -- MkDocs extension that supports image lightbox with GLightbox. Karsten Schöke
• Should GPU shaders be considered firmware? Stephan Verbücheln
  • Re: Should GPU shaders be considered firmware? Hakan Bayındır
  • Re: Should GPU shaders be considered firmware? Marco d'Itri
  • Re: Should GPU shaders be considered firmware? Hakan Bayındır
  • Re: Should GPU shaders be considered firmware? Marco d'Itri
  • Re: Should GPU shaders be considered firmware? Hakan Bayındır
  • Re: Should GPU shaders be considered firmware? Stephen Kitt
  • Re: Should GPU shaders be considered firmware? Dirk Lehmann
  • Re: Should GPU shaders be considered firmware? Stephan Verbücheln
  • Re: Should GPU shaders be considered firmware? Dirk Lehmann
  • Re: Should GPU shaders be considered firmware? Bastian Blank
• how to automatically generate a backtrace from within sbuild PICCA Frederic-Emmanuel
  • Re: how to automatically generate a backtrace from within sbuild Jochen Sprickerhof
  • Re: how to automatically generate a backtrace from within sbuild PICCA Frederic-Emmanuel
  • Re: how to automatically generate a backtrace from within sbuild Jochen Sprickerhof
• Bug#1100170: ITP: libayatana-appindicator-glib -- Ayatana Application Indicators (Glib-2.0-only reimplementation) Mike Gabriel
• Bug#1100167: ITP: tclthread3 -- Tcl extension implementing script level access to Tcl threading capabilities (version 3 for Tcl 9) Sergei Golovan
• Re: Binary conflict between Midnight Commander and MinIO Client Helmut Grohne
• Bug#1100156: ITP: inkcut -- GUI for controlling vinyl cutters Alexander Sulfrian
• Bug#1100155: ITP: magnum-capi-helm -- Helm driven Cluster API driver for Magnum Guillaume Boutry
• Re: MiniDebConf Hamburg 2025 Matthias Geiger
• Re: Bug reports for Uploaders Blair Noctis
  • Re: Bug reports for Uploaders Raphael Hertzog
  • Re: Bug reports for Uploaders Blair Noctis
  • Re: Bug reports for Uploaders Raphael Hertzog
• Re: Revisiting the idea of pre-NEW peer review? (Re: Bits from DPL) Charles Plessy
  • Re: Revisiting the idea of pre-NEW peer review? (Re: Bits from DPL) Philip Hands
  • Re: Revisiting the idea of pre-NEW peer review? (Re: Bits from DPL) Charles Plessy
  • Re: Revisiting the idea of pre-NEW peer review? (Re: Bits from DPL) Simon Josefsson
  • Re: Revisiting the idea of pre-NEW peer review? (Re: Bits from DPL) Charles Plessy
  • Re: Revisiting the idea of pre-NEW peer review? (Re: Bits from DPL) Maytham Alsudany
  • Re: Revisiting the idea of pre-NEW peer review? (Re: Bits from DPL) Simon Josefsson
  • Re: Revisiting the idea of pre-NEW peer review? (Re: Bits from DPL) Charles Plessy
• Re: Improvement of headless server upgrades Marc Haber
  • Re: Improvement of headless server upgrades Marc Haber
• Bug#1100019: ITP: graphite-editor -- Graphite-Editor a modern, vector graphics tool Carl Keinath
• Re: Bits from DPL Pierre-Elliott Bécue
• Re: Processing times for the NEW queue (was Re: Bits from DPL) Faidon Liambotis
  • Re: Processing times for the NEW queue (was Re: Bits from DPL) Wookey
  • Re: Processing times for the NEW queue (was Re: Bits from DPL) Pirate Praveen
  • Re: Processing times for the NEW queue (was Re: Bits from DPL) Jeremy Stanley
  • Re: Processing times for the NEW queue (was Re: Bits from DPL) Timo Röhling
• Bug#1100047: ITP: flashmq -- A high-performance, light-weight MQTT broker/server Matthias Urlichs
• Bug#1100042: ITP: python-casttube -- Interact with the YouTube Chromecast API Edward Betts
• Bug#1100034: ITP: golang-github-astromechza-etcpwdparse -- Golang library for parsing /etc/passwd entries Roland Mas
• Bug#1100046: ITP: python3-asyncclick -- Python package for creating beautiful command line interfaces, async version Matthias Urlichs
• Bug#1100127: ITP: python-enamlx -- Additional Qt Widgets for Enaml Alexander Sulfrian
• Bug#1100131: ITP: golang-github-eggsampler-acme -- Go client library implementation for ACME v2 (RFC8555) Luca Soler
• Bug#1100128: ITP: golang-github-letsencrypt-borp -- Boulder's version of go-gorp/gorp Luca Soler
• Bug#1100121: ITP: golang-github-poy-onpar -- Parallel testing framework for Go Luca Soler
• Bug#1100112: ITP: golang-github-ashcrow-osrelease -- Go library/binary for parsing osrelease Thomas Goirand
• Bug#1100106: ITP: golang-go4-netipx -- extra stuff from inet.af/netaddr that didn't make it into Go's net/netip Thomas Goirand
• Bug#1100099: ITP: python-elastcsearch8 -- Python client for Elasticsearch8 Karsten Schöke
• Bug#1100098: ITP: golang-github-yalue-merged-fs -- compose Multiple Go Filesystems Thomas Goirand
• General Questions about Translations and what a package maintainer has to do Marc Haber
  • General Questions about Translations and what a package maintainer has to do Simon Richter
  • Re: General Questions about Translations and what a package maintainer has to do Marc Haber
  • Re: General Questions about Translations and what a package maintainer has to do Dirk Lehmann
  • Re: General Questions about Translations and what a package maintainer has to do Julien Plissonneau Duquène
  • Re: General Questions about Translations and what a package maintainer has to do Marc Haber
  • Re: General Questions about Translations and what a package maintainer has to do Maytham Alsudany
  • Re: General Questions about Translations and what a package maintainer has to do Marc Haber
  • Re: General Questions about Translations and what a package maintainer has to do Marc Haber
  • Re: General Questions about Translations and what a package maintainer has to do Julien Plissonneau Duquène
  • Re: General Questions about Translations and what a package maintainer has to do Marc Haber
  • Re: General Questions about Translations and what a package maintainer has to do Julien Plissonneau Duquène
  • Re: General Questions about Translations and what a package maintainer has to do Marc Haber
  • Documentation for Package Maintainers regarding Translations (was: General Questions about Translations and what a package maintainer has to do) Marc Haber
  • Re: Documentation for Package Maintainers regarding Translations (was: General Questions about Translations and what a package maintainer has to do) Helge Kreutzmann
  • Re: Documentation for Package Maintainers regarding Translations (was: General Questions about Translations and what a package maintainer has to do) Marc Haber
  • Re: Documentation for Package Maintainers regarding Translations (was: General Questions about Translations and what a package maintainer has to do) Helge Kreutzmann
  • Re: Documentation for Package Maintainers regarding Translations (was: General Questions about Translations and what a package maintainer has to do) Marc Haber
  • Re: General Questions about Translations and what a package maintainer has to do Dirk Lehmann
  • Re: General Questions about Translations and what a package maintainer has to do Marc Haber
  • Re: General Questions about Translations and what a package maintainer has to do Bill Allombert
  • Re: General Questions about Translations and what a package maintainer has to do Marc Haber
• Bug#1100095: ITP: golang-github-tredoe-osutil -- access to operating system functionality Thomas Goirand
• Bug#1100090: ITP: didder -- An extensive, fast, and accurate command-line image dithering tool. Nicolas Peugnet
• Re: Debian on /usr (Re: TC decision on ownership of top-level filesystem aliases - #1091995) Matthias Urlichs
• Re: New appointment for the Debian Technical Committee: Paul Tagliamonte <paultag> Sean Whitton
  • Re: New appointment for the Debian Technical Committee: Paul Tagliamonte <paultag> Andreas Tille
• NEW review & revision process (or lack thereof) (Re: Growing new FTP-masters (Re: Bits from DPL)) Luke Faraone
  • Re: NEW review & revision process (or lack thereof) (Re: Growing new FTP-masters (Re: Bits from DPL)) Simon Josefsson
  • Re: NEW review & revision process (or lack thereof) (Re: Growing new FTP-masters (Re: Bits from DPL)) Philip Hands
  • Re: NEW review & revision process (or lack thereof) (Re: Growing new FTP-masters (Re: Bits from DPL)) Jonathan Dowland
• Bug#1099948: ITP: doxysphinx -- A lightweight Doxygen extension for Sphinx Christian Bayle
• Re: Change the expectation that emails should wrap at 80 characters Philip Hands
  • Re: Change the expectation that emails should wrap at 80 characters The Wanderer
  • Re: Change the expectation that emails should wrap at 80 characters Bjørn Mork
  • Re: Change the expectation that emails should wrap at 80 characters Jonas Smedegaard
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan McDowell
  • Re: Change the expectation that emails should wrap at 80 characters James Lu
  • Re: Change the expectation that emails should wrap at 80 characters Charles Plessy
  • Re: Change the expectation that emails should wrap at 80 characters Julien Plissonneau Duquène
  • Re: Change the expectation that emails should wrap at 80 characters Marc Haber
  • please do not use text/markdown Timo Röhling
  • Re: please do not use text/markdown Jonas Smedegaard
  • Re: please do not use text/markdown Timo Röhling
  • Re: Change the expectation that emails should wrap at 80 characters Jeremy Stanley
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: Change the expectation that emails should wrap at 80 characters Timo Röhling
  • Re: Change the expectation that emails should wrap at 80 characters Stephan Verbücheln
  • Re: Change the expectation that emails should wrap at 80 characters Blair Noctis
  • Re: Change the expectation that emails should wrap at 80 characters Mario Limonciello
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Tollef Fog Heen
  • Re: Change the expectation that emails should wrap at 80 characters Christoph Berg
  • Re: Change the expectation that emails should wrap at 80 characters Antonio Terceiro
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Andrea Pappacoda
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Stephan Verbücheln
  • Re: Change the expectation that emails should wrap at 80 characters Carsten Schoenert
  • Re: Change the expectation that emails should wrap at 80 characters Paul Tagliamonte
  • Re: Change the expectation that emails should wrap at 80 characters Philipp Kern
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Jonathan Dowland
  • Re: Change the expectation that emails should wrap at 80 characters Stephan Verbücheln
  • Re: Change the expectation that emails should wrap at 80 characters Soren Stoutner
  • Re: Change the expectation that emails should wrap at 80 characters Guillem Jover
  • Re: Change the expectation that emails should wrap at 80 characters Guillem Jover
  • BTS not unmangling quoting markers with format=flowed (was: Re: Change the expectation that emails should wrap at 80 characters) Guillem Jover
• Re: Need advice on coordinating libkdumpfile update and introducing pykdumpfile Breno Leitao
  • Re: Need advice on coordinating libkdumpfile update and introducing pykdumpfile Michel Lind
  • Re: Need advice on coordinating libkdumpfile update and introducing pykdumpfile Matthias Urlichs
  • Re: Need advice on coordinating libkdumpfile update and introducing pykdumpfile Michel Lind
  • Re: Need advice on coordinating libkdumpfile update and introducing pykdumpfile Breno Leitao
• Bug#1099977: ITP: python3-hostlist -- A Python library and command-line toolset for managing, expanding, and manipulating host lists Gennaro Oliva
• Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Simon Josefsson
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Marc Haber
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Simon Richter
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Andrey Rakhmatullin
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Simon Richter
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Marc Haber
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Jonas Smedegaard
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Michael Stone
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Geert Stappers
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Simon Josefsson
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Bjørn Mork
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Andrey Rakhmatullin
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Jeremy Stanley
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Michael Stone
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Andrey Rakhmatullin
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Andrey Rakhmatullin
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Andrew M.A. Cater
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Marc Haber
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Simon Josefsson
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Marc Haber
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Aurélien COUDERC
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Simon Josefsson
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Jonathan McDowell
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Soren Stoutner
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Andrey Rakhmatullin
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Soren Stoutner
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Andrey Rakhmatullin
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Philip Hands
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Simon Josefsson
  • Re: Salsa pipeline limit Peter B
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Steve McIntyre
  • Building live images without non-free-firmware (Was: Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion) Roland Clobus
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Ansgar 🙀
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Pirate Praveen
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Ansgar 🙀
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Stephan Verbücheln
• Bug#1099951: ITP: mpire -- A Python package for easy multiprocessing, but faster than multiprocessing Christian Bayle
• Bug#1099939: ITP: sphinx-external-toc -- A sphinx extension that allows the site-map to be defined in a single YAML file Christian Bayle

• Later messages