debian-devel  

Messages by Thread

• • Re: Can anyone help with telegram-desktop? Andrey Rakhmatullin
  • Re: Can anyone help with telegram-desktop? Salvo Tomaselli
  • Re: Can anyone help with telegram-desktop? Wookey
  • Re: Can anyone help with telegram-desktop? Leandro Cunha
• dh-shell-completions: simple debhelper addon to install shell completions Blair Noctis
  • Re: dh-shell-completions: simple debhelper addon to install shell completions M. Zhou
  • Re: dh-shell-completions: simple debhelper addon to install shell completions Blair Noctis
  • Re: keybindings (was: dh-shell-completions: ...) Jonas Smedegaard
  • Re: dh-shell-completions: simple debhelper addon to install shell completions Matthias Geiger
  • Re: dh-shell-completions: simple debhelper addon to install shell completions Nicolas Peugnet
• Re: salsa.debian.org maintenance Manuel Choorly
• Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Roberto C . Sánchez
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Tollef Fog Heen
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Andrey Rakhmatullin
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Jeremy Bícha
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Roberto C . Sánchez
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Otto Kekäläinen
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Jonas Smedegaard
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Otto Kekäläinen
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Jonas Smedegaard
  • mostly just +1 (Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package?) Holger Levsen
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Wookey
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Otto Kekäläinen
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? G. Branden Robinson
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Otto Kekäläinen
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? G. Branden Robinson
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Wookey
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Marc Haber
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Roberto C . Sánchez
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Pierre-Elliott Bécue
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Marco d'Itri
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? gregor herrmann
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Andreas Tille
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Tobias Frost
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Otto Kekäläinen
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Jonas Smedegaard
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Jonathan Dowland
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Andreas Tille
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Sam Hartman
  • Re: Should uncoordinated NMUs unilaterally choose Salsa as the VCS for a package? Andreas Tille
• Bug#1100579: general: After latest update problems with super key Andrey
• Bug#1100571: ITP: mgmt -- next generation config management Thomas Goirand
  • Re: Bug#1100571: ITP: mgmt -- next generation config management Simon Richter
  • Re: Bug#1100571: ITP: mgmt -- next generation config management Jonathan Dowland
• Bug#1100052: ITP: python-enaml -- Declarative DSL for building rich user interfaces in Python Alexander Sulfrian
• Bug#1100491: ITP: blazar-nova -- Nova scheduler filter used for the host reservation feature Thomas Goirand
• Re: Call for participation in tag2upload closed beta Simon Josefsson
  • Re: Call for participation in tag2upload closed beta Sean Whitton
  • Re: Call for participation in tag2upload closed beta Simon Josefsson
  • Re: Call for participation in tag2upload closed beta Sean Whitton
  • Re: Call for participation in tag2upload closed beta Simon Josefsson
  • Re: Call for participation in tag2upload closed beta Sean Whitton
  • Re: Call for participation in tag2upload closed beta Simon Josefsson
  • Re: Call for participation in tag2upload closed beta Johannes Schauer Marin Rodrigues
  • Re: Call for participation in tag2upload closed beta Sean Whitton
• Bug#1100501: ITP: blazar-dashboard -- Horizon plugin for the Blazar Reservation Service for OpenStack Thomas Goirand
• Bug#1100490: ITP: blazar -- resource reservation service for OpenStack Thomas Goirand
• Bug#1100469: ITP: golang-github-apptainer-apptainer -- Apptainer: Application containers for Linux Roland Mas
• Bug#1100420: ITP: wireguard-initramfs -- WireGuard initramfs integration Alexander Sulfrian
• Bug#1100417: ITP: golang-github-adxgun-registry-auth -- a package to implement private docker registry token authentication server Roland Mas
• 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
  • Re: Binary conflict between Midnight Commander and MinIO Client Mathias Gibbens
• 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
• Bug#1100019: ITP: graphite-editor -- Graphite-Editor a modern, vector graphics tool Carl Keinath
• 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: 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
• Bug#1099948: ITP: doxysphinx -- A lightweight Doxygen extension for Sphinx Christian Bayle
• Bug#1099977: ITP: python3-hostlist -- A Python library and command-line toolset for managing, expanding, and manipulating host lists Gennaro Oliva
• 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
• Bug#1099895: ITP: qtpyvcp -- Framework for LinuxCNC virtual control panels Steffen Möller
• Bug#1099862: ITP: passim -- A local caching server Mario Limonciello
• Bug#1099859: ITP: python-local-agent-rs -- Proton VPN local agent for managing connections Josenilson Ferreira da Silva
• Re: The Project Gutenberg license, packages using its books as testdata Soren Stoutner
  • Re: The Project Gutenberg license, packages using its books as testdata Maytham Alsudany
• Bug#1099857: ITP: qtpyvcp -- Framework for LinuxCNC virtual control panels Steffen Moeller
• Bug#1099848: ITP: greaseweazle -- Host tools for Greaseweazle Stephen Kitt
• Bug#1099808: ITP: golang-github-jesseduffield-gocui -- minimalist console user interfaces Go library Jongmin Kim
• Bug#1099783: ITP: golang-github-jesseduffield-minimal -- Worse versions of packages that already exist (library) Maytham Alsudany
• Bug#1099782: ITP: golang-github-jesseduffield-kill -- simple package for killing processes (library) Maytham Alsudany
• Bug#1099779: ITP: rust-oid-registry -- object identifier (OID) database Jonas Smedegaard
• Bug#1099778: ITP: golang-github-gosimple-unidecode -- Unicode transliterator in Golang - Replaces non-ASCII characters with their ASCII approximations. Luca Soler
• Bug#1099776: ITP: golang-github-humanlogio-api -- internal libraries for humanlog (library) Maytham Alsudany
• Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion pandya
  • 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 Josefsson
  • 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 Leandro Cunha
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Mario Limonciello
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Bill Allombert
  • 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 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 Andrew M.A. Cater
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Matthias Urlichs
  • 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 Ansgar 🙀
  • 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 Ansgar 🙀
  • 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 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
  • 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 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 Michael Stone
  • Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion Andrew M.A. Cater

• Earlier messages
• Later messages