debian-devel  

Messages by Thread

• • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Lucas Nussbaum
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Ian Jackson
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Lucas Nussbaum
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Simon McVittie
  • RE: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] PICCA Frederic-Emmanuel
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Simon McVittie
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Otto Kekäläinen
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Lucas Nussbaum
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Ian Jackson
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Lucas Nussbaum
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Otto Kekäläinen
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Simon Josefsson
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Ian Jackson
  • Please don't stop using uscan (Re: Include git commit id and git tree id in *.changes files when uploading?) Otto Kekäläinen
  • Re: Please don't stop using uscan (Re: Include git commit id and git tree id in *.changes files when uploading?) Simon Josefsson
  • Re: Please don't stop using uscan (Re: Include git commit id and git tree id in *.changes files when uploading?) Otto Kekäläinen
  • Re: Please don't stop using uscan (Re: Include git commit id and git tree id in *.changes files when uploading?) Simon Josefsson
  • Re: Please don't stop using uscan (Re: Include git commit id and git tree id in *.changes files when uploading?) Otto Kekäläinen
  • Re: Please don't stop using uscan (Re: Include git commit id and git tree id in *.changes files when uploading?) Jérémy Lal
  • Re: Please don't stop using uscan (Re: Include git commit id and git tree id in *.changes files when uploading?) Lucas Nussbaum
  • Re: Please don't stop using uscan (Re: Include git commit id and git tree id in *.changes files when uploading?) Simon Josefsson
  • Re: Please don't stop using uscan (Re: Include git commit id and git tree id in *.changes files when uploading?) Sean Whitton
  • Re: Please don't stop using uscan (Re: Include git commit id and git tree id in *.changes files when uploading?) Colin Watson
  • Re: Please don't stop using uscan (Re: Include git commit id and git tree id in *.changes files when uploading?) Sean Whitton
  • Re: Please don't stop using uscan (Re: Include git commit id and git tree id in *.changes files when uploading?) Ian Jackson
  • Re: Please don't stop using uscan (Re: Include git commit id and git tree id in *.changes files when uploading?) Lucas Nussbaum
  • uscan and tag2upload Simon Richter
  • Re: uscan and tag2upload Ian Jackson
  • Re: uscan and tag2upload Simon Richter
  • Re: uscan and tag2upload Maytham Alsudany
  • Please use uscan in particular for packages with Files-Excluded (Re: Please don't stop using uscan) Otto Kekäläinen
  • Re: Include git commit id and git tree id in *.changes files when uploading? Nikolaus Rath
  • Re: Include git commit id and git tree id in *.changes files when uploading? Sean Whitton
  • Re: Include git commit id and git tree id in *.changes files when uploading? G. Branden Robinson
  • Re: Include git commit id and git tree id in *.changes files when uploading? Otto Kekäläinen
  • Re: Include git commit id and git tree id in *.changes files when uploading? Ian Jackson
  • Re: Include git commit id and git tree id in *.changes files when uploading? Lucas Nussbaum
  • Re: Include git commit id and git tree id in *.changes files when uploading? Russ Allbery
  • Re: Include git commit id and git tree id in *.changes files when uploading? Sean Whitton
  • Re: Include git commit id and git tree id in *.changes files when uploading? Otto Kekäläinen
  • Re: Include git commit id and git tree id in *.changes files when uploading? Simon Richter
  • Re: Include git commit id and git tree id in *.changes files when uploading? Sean Whitton
  • Re: Include git commit id and git tree id in *.changes files when uploading? Ian Jackson
  • legacy crap, we must all switch to dgit else we are stupid (was Re: Include git commit id and git tree id in *.changes files when uploading?_ Holger Levsen
  • Re: legacy crap, we must all switch to dgit else we are stupid (was Re: Include git commit id and git tree id in *.changes files when uploading?_ Ian Jackson
  • Re: legacy crap, we must all switch to dgit else we are stupid (was Re: Include git commit id and git tree id in *.changes files when uploading?_ Salvo Tomaselli
  • Re: legacy crap, we must all switch to dgit else we are stupid (was Re: Include git commit id and git tree id in *.changes files when uploading?_ Jonathan Dowland
  • Re: legacy crap, we must all switch to dgit else we are stupid (was Re: Include git commit id and git tree id in *.changes files when uploading?_ Sean Whitton
  • Re: legacy crap, we must all switch to dgit else we are stupid Antoine Le Gonidec
  • Re: legacy crap, we must all switch to dgit else we are stupid Ian Jackson
  • traditional workflows? (Re: legacy crap, we must all switch to dgit else we are stupid) Holger Levsen
  • Re: legacy crap, we must all switch to dgit else we are stupid Antoine Le Gonidec
  • Re: Include git commit id and git tree id in *.changes files when uploading? Santiago Vila
  • Re: Include git commit id and git tree id in *.changes files when uploading? Guillem Jover
  • Re: Include git commit id and git tree id in *.changes files when uploading? Guillem Jover
  • Re: Include git commit id and git tree id in *.changes files when uploading? Adrian Bunk
  • Re: Include git commit id and git tree id in *.changes files when uploading? Bastian Blank
  • Re: Include git commit id and git tree id in *.changes files when uploading? Lucas Nussbaum
  • Re: Include git commit id and git tree id in *.changes files when uploading? Sean Whitton
  • Re: Include git commit id and git tree id in *.changes files when uploading? Lucas Nussbaum
  • Re: Include git commit id and git tree id in *.changes files when uploading? Sean Whitton
  • Re: Bug#1123842: Include git commit id and git tree id in *.changes files when uploading? Chris Hofstaedtler
  • Re: Bug#1123842: Include git commit id and git tree id in *.changes files when uploading? Ian Jackson
  • Re: Include git commit id and git tree id in *.changes files when uploading? Lucas Nussbaum
  • Re: Include git commit id and git tree id in *.changes files when uploading? Ian Jackson
  • Re: Include git commit id and git tree id in *.changes files when uploading? Otto Kekäläinen
  • Re: Include git commit id and git tree id in *.changes files when uploading? Lucas Nussbaum
  • Re: Include git commit id and git tree id in *.changes files when uploading? Sean Whitton
  • Re: Include git commit id and git tree id in *.changes files when uploading? Iustin Pop
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Ian Jackson
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Iustin Pop
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Ian Jackson
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Iustin Pop
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Russ Allbery
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Joseph Beckenbach
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Russ Allbery
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Iustin Pop
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Ian Jackson
  • Re: Include git commit id and git tree id in *.changes files when uploading? [and 1 more messages] Ian Jackson
  • Re: Include git commit id and git tree id in *.changes files when uploading? Daniel Gröber
  • Re: Include git commit id and git tree id in *.changes files when uploading? Santiago Vila
  • Re: Include git commit id and git tree id in *.changes files when uploading? Adrian Bunk
  • Re: Include git commit id and git tree id in *.changes files when uploading? Simon Richter
  • Re: Include git commit id and git tree id in *.changes files when uploading? Sean Whitton
  • tag2upload's support of pristine-tar missing and potential regression in upstream signature verification (Re: Include git commit id and git tree id in *.changes files when uploading?) Otto Kekäläinen
  • Re: tag2upload's support of pristine-tar missing and potential regression in upstream signature verification (Re: Include git commit id and git tree id in *.changes files when uploading?) Marco d'Itri
  • Re: tag2upload's support of pristine-tar missing and potential regression in upstream signature verification (Re: Include git commit id and git tree id in *.changes files when uploading?) Sean Whitton
  • Re: tag2upload's support of pristine-tar missing and potential regression in upstream signature verification (Re: Include git commit id and git tree id in *.changes files when uploading?) Otto Kekäläinen
  • Re: tag2upload's support of pristine-tar missing and potential regression in upstream signature verification (Re: Include git commit id and git tree id in *.changes files when uploading?) Sean Whitton
  • Re: tag2upload's support of pristine-tar missing and potential regression in upstream signature verification (Re: Include git commit id and git tree id in *.changes files when uploading?) Simon Josefsson
  • Re: tag2upload's support of pristine-tar missing and potential regression in upstream signature verification (Re: Include git commit id and git tree id in *.changes files when uploading?) Sean Whitton
  • Re: tag2upload's support of pristine-tar missing and potential regression in upstream signature verification (Re: Include git commit id and git tree id in *.changes files when uploading?) Simon Josefsson
  • Re: tag2upload's support of pristine-tar missing and potential regression in upstream signature verification (Re: Include git commit id and git tree id in *.changes files when uploading?) Sean Whitton
  • Re: tag2upload's support of pristine-tar missing and potential regression in upstream signature verification (Re: Include git commit id and git tree id in *.changes files when uploading?) Adrian Bunk
  • Re: tag2upload's support of pristine-tar missing and potential regression in upstream signature verification (Re: Include git commit id and git tree id in *.changes files when uploading?) Ian Jackson
  • Re: Include git commit id and git tree id in *.changes files when [SUMMARY] uploading? Lucas Nussbaum
  • Re: Include git commit id and git tree id in *.changes files when [SUMMARY] uploading? Ian Jackson
  • Re: Include git commit id and git tree id in *.changes files when [SUMMARY] uploading? Lucas Nussbaum
  • "AI" is fractally terrible and should be beyond our pale Ian Jackson
  • Re: "AI" is fractally terrible and should be beyond our pale Sean Whitton
  • Re: Include git commit id and git tree id in *.changes files when [SUMMARY] uploading? Antoine Le Gonidec
• Bug#1122966: ITP: qogir-icon-theme -- Flat colorful design icon theme for linux desktops debian
• Should request of binary package removals include ports ? Charles Plessy
  • Re: Should request of binary package removals include ports ? Sebastiaan Couwenberg
  • Re: Should request of binary package removals include ports ? Charles Plessy
  • Re: Should request of binary package removals include ports ? Samuel Thibault
  • Re: Should request of binary package removals include ports ? Paul Gevers
  • Re: Should request of binary package removals include ports ? Samuel Thibault
  • Re: Should request of binary package removals include ports ? John Paul Adrian Glaubitz
• Bug#1122953: ITP: jellyfin-desktop -- Native desktop client for Jellyfin using jellyfin-web with embedded MPV player Nicolas Peugnet
• LibreOffice Online Editing .odt/.ods files anywhere online instantly - Intention for 2026 Lukasz Szybalski
• Bug#1122925: RFP: rocmlir -- MLIR-based GPU kernel generator for AMD ROCm Utkarsh Raj
• Bug#1122923: ITP: hyprwire-protocols -- Wayland protocol specifications for Hyprwire and Hyprtavern Carl Keinath
• Alternative to single-file plugin binary packages Andreas Metzler
  • Re: Alternative to single-file plugin binary packages Gioele Barabucci
  • Re: Alternative to single-file plugin binary packages Marco d'Itri
  • Re: Alternative to single-file plugin binary packages Andreas Metzler
• Bug#1122893: ITP: age-plugin-tpm -- a TPM 2.0 plugin for age Simon Josefsson
• Bug#1122867: RFH: qcontrol Ian Campbell
• Bug#1122852: ITP: swan -- The PDF Swiss-Army CLI Uddhav
• What is the preferred way to ask for large numbers of arch-specific removals? Charles Plessy
  • Re: What is the preferred way to ask for large numbers of arch-specific removals? Sebastiaan Couwenberg
  • Re: What is the preferred way to ask for large numbers of arch-specific removals? Thorsten Alteholz
  • Re: What is the preferred way to ask for large numbers of arch-specific removals? Bill Allombert
  • Re: What is the preferred way to ask for large numbers of arch-specific removals? Andreas Tille
  • Re: What is the preferred way to ask for large numbers of arch-specific removals? Charles Plessy
  • Re: What is the preferred way to ask for large numbers of arch-specific removals? Simon McVittie
  • Re: What is the preferred way to ask for large numbers of arch-specific removals? Sebastiaan Couwenberg
  • Re: What is the preferred way to ask for large numbers of arch-specific removals? Andrey Rakhmatullin
• Bug#1122810: ITP: emacs-one-tab-per-project -- One tab per project, with unique names Arto Jantunen
• Bug#1122808: ITP: fluent-gtk-themes -- Fluent design gtk theme for linux desktops. debian
• Bug#1122659: ITP: rust-ossl -- Low-level Rust bindings to the OpenSSL library, focusing on the modern OpenSSL 3+ APIs. Fabian Grünbichler
• Bug#1122656: ITP: hyprtavern -- A modern, simple and consistent session bus for IPC discovery Carl Keinath
• Work-needing packages report for Dec 12, 2025 wnpp
• Bug#1122632: ITP: vimix-gtk-themes -- Flat Material Design theme for GNOME/GTK+ based desktop environments debian
• Bug#1122577: ITP: debsbom -- Software Bill of Materials generator for distributions based on Debian Felix Moessbauer
• Bug#1122576: ITP: webdar -- Web interface to dar John Goerzen
• Bug#1122537: ITP: golang-github-tink-crypto-tink-go-hcvault -- Extension to Tink Go that provides HashiCorp Vault integration Simon Josefsson
• Bug#1122518: ITP: documentdb -- MongoDB-compatible open source document database built on PostgreSQL Lena Voytek
• Bug#1122334: ITP: nextgroove -- Play music from Nextcloud Aryan Karamtoth
• Automatic binNMUs for packages which recommend/suggest a library undergoing a SONAME bump transition Gard Spreemann
  • Re: Automatic binNMUs for packages which recommend/suggest a library undergoing a SONAME bump transition Andrey Rakhmatullin
  • Re: Automatic binNMUs for packages which recommend/suggest a library undergoing a SONAME bump transition Sebastiaan Couwenberg
  • Re: Automatic binNMUs for packages which recommend/suggest a library undergoing a SONAME bump transition Gard Spreemann
  • Re: Automatic binNMUs for packages which recommend/suggest a library undergoing a SONAME bump transition Gard Spreemann
• Bug#1122275: ITP: golang-github-letsencrypt-boulder -- ACME-based certificate authority in Go Simon Josefsson
• Bug#1122278: ITP: rust-xleak -- A fast terminal Excel viewer with an interactive TUI Nadzeya Hutsko
• Bug#1122187: ITP: tree-sitter-ini -- Parser for INI files using the tree-sitter parser generator Antonin Delpeuch
• Building package twice Giovanni Mascellani
  • Re: Building package twice Jérémy Lal
  • Re: Building package twice Giovanni Mascellani
  • Re: Building package twice Konstantin Demin
  • Re: Building package twice Gioele Barabucci
  • Re: Building package twice Simon Richter
  • Re: Building package twice Bastian Blank
• Bug#1122152: ITP: ishmael -- ebook dumper for many formats Ken Gilmer
• Bug#1122145: ITP: xmpp-ap-bridge -- chat between XMPP and ActivityPub Martin
• Bug#1122134: ITP: mini-init-asm -- tiny PID 1 for containers tar
• Bug#1122131: ITP: spike -- lightweight secrets store using SPIFFE as identity control plane Simon Josefsson
• Bug#1122130: ITP: golang-github-spiffe-spike-sdk-go -- SPIKE Go SDK Simon Josefsson
• ITS process as a means to orphan packages Tobias Frost
  • Re: ITS process as a means to orphan packages Jonas Smedegaard
  • Re: ITS process as a means to orphan packages Sean Whitton
  • Re: ITS process as a means to orphan packages Sean Whitton
  • Re: ITS process as a means to orphan packages Holger Levsen
  • Re: ITS process as a means to orphan packages Matthias Geiger
  • Re: ITS process as a means to orphan packages Andreas Tille
  • Re: ITS process as a means to orphan packages Jonas Smedegaard
  • Re: ITS process as a means to orphan packages Tobias Frost
• Bug#1122098: ITP: python-pykakasi -- Kana kanji simple inversion library YOKOTA Hiroshi
• Bug#1122097: ITP: python-jaconv -- Interconverter for Hiragana, Katakana, Hankaku and Zenkaku YOKOTA Hiroshi
• [MBF] Please remove/replace usage of dh_movetousr Michael Biebl
  • Re: [MBF] Please remove/replace usage of dh_movetousr Emilio Pozuelo Monfort
  • Re: [MBF] Please remove/replace usage of dh_movetousr Gioele Barabucci
  • Re: [MBF] Please remove/replace usage of dh_movetousr Colin Watson
  • Re: [MBF] Please remove/replace usage of dh_movetousr Michael Biebl
  • Re: [MBF] Please remove/replace usage of dh_movetousr Michael Biebl
• [MBF] Update udeb packages to use non-aliased paths Michael Biebl
  • Re: [MBF] Update udeb packages to use non-aliased paths Michael Biebl
  • testing migration, udd, lintian and udebs [Re: [MBF] Update udeb packages to use non-aliased paths] Michael Biebl
  • Re: testing migration, udd, lintian and udebs [Re: [MBF] Update udeb packages to use non-aliased paths] Paul Gevers
• Bug#1122047: ITP: octave-datatypes -- extra data types for GNU Octave Rafael Laboissière
• 56 High Blood
• Bug#1121986: ITP: yuki -- Tiny Web Server implementation in pure C codes Yuki Kurosawa
• Work-needing packages report for Dec 5, 2025 wnpp
• Bug#1121923: ITP: tree-sitter-powershell -- Powershell parser for use with tree-sitter Antonin Delpeuch
• Debian Technical Committee: Bug#1113774: Disabling -fcf-protection in sudo for bookworm Christoph Berg
• Bug#1121904: ITP: python-asciimatics -- Python cross platform package to do curses-like operations Seyed Mohamad Amin Modaresi
• Re: utmp in trixie Michael Tokarev
  • Re: utmp in trixie Craig Small
  • Re: utmp in trixie Andrew Bower
• Restarting systemd user units on package upgrade Sean Whitton
  • Re: Restarting systemd user units on package upgrade Simon McVittie
  • Re: Bug#1117735: Restarting systemd user units on package upgrade Sven Joachim
  • Re: Restarting systemd user units on package upgrade Holger Levsen
  • Re: Bug#1117735: Restarting systemd user units on package upgrade Simon Josefsson
  • Re: Bug#1117735: Restarting systemd user units on package upgrade Peter Pentchev
  • Re: Bug#1117735: Restarting systemd user units on package upgrade Sean Whitton
  • Re: Bug#1117735: Restarting systemd user units on package upgrade Sean Whitton
  • Re: Bug#1117735: Restarting systemd user units on package upgrade Ian Jackson

• Earlier messages
• Later messages