Re: New contributor experience

On Wed, 04 Jun 2025 at 17:44:52 +0200, Marc Haber wrote: Maybe we should not direct newcomers to wnpp but instead to a list of wishlist bugs tagged help (for newbies), and optionally to a list of RC bugs tagged help (with the warning "not for the faint of the heart"). The "newcomer" tag in th

Re: Question regarding Trixie and SFML

On Fri, 30 May 2025 at 20:15:47 +0200, Marc Haber wrote: If the libraries are not backwards compatible, you might want to talk to the Debian Games Team (pkg-games-de...@lists.alioth.debian.org) whether they plan to package the 3.0 series independently from the 2.x series in Debian 14/forky. B

Re: New contributor experience

On Fri, 30 May 2025 at 10:19:19 -0300, Antonio Terceiro wrote: On Fri, May 30, 2025 at 01:46:57PM +0100, Ahmad Khalifa wrote: What should you do in that situation where you have a no-response MR? Open a bug report pointing to the MR. Or, if there is a pre-existing bug report, send mail to it

Re: Questions about hard freeze and autopkgtests

On Wed, 28 May 2025 at 17:06:52 -0400, Richard Hansen wrote: * What does "autopkgtest bounty" mean in the table at ? When we aren't in a freeze, packages with successful non-superficial autopkgtests migrate sooner than packages w

Re: Dependency merging in APT

On Wed, 28 May 2025 at 10:33:26 +0200, Julian Andres Klode wrote: gnupg Depends: gpg (>= 2.4.7-19) overlaps Depends: gpg (<< 2.4.7-19.1~) - solutions: ['gpg=2.4.7-19'] - eliminated: [] ['gpg-from-sq=0.13.1-3'] Where gpg-from-sq would be considered a valid solution for the << depends as it prov

Re: Question about splitting a source package with an epoch

On Thu, 15 May 2025 at 13:39:32 -0700, Soren Stoutner wrote: The changelog indeed says the current epoch is 1: https://salsa.debian.org/debian/dutch/-/blob/master/debian/changelog? ref_type=heads#L1 Also, tracker.debian.org says the same thing: https://tracker.debian.org/pkg/dutch That's the

Re: git branches vs debian specific git tools (Re: RFC for changes regarding NMU in developers reference

On Wed, 14 May 2025 at 09:47:18 +0100, Sean Whitton wrote: On Wed 14 May 2025 at 10:41am +02, PICCA Frederic-Emmanuel wrote: So where do we put the upstream git URL If I read this part of DEP-14, I have the information that the remote should be named 'upstreamvcs' but nothing about where to put

Re: git branches vs debian specific git tools (Re: RFC for changes regarding NMU in developers reference

7;t strictly need that -- we could just import all debian/ sub-directories from all source packages into one monolithic git repository, and work together there -- but it would simplify syncing the same information in several files under debian/ and reduce the number of small files we have to manage. /Simon signature.asc Description: PGP signature

Re: Dropping awk?

Holger Levsen writes: > On Wed, May 14, 2025 at 09:30:25AM +0200, Simon Josefsson wrote: >> Are there any guarantees on semantics for package removals? Will the >> user/group be removed from /etc/{passwd,group} or not? Will it remove >> the home directory? What happens

Re: Dropping awk?

mpty? Will it remove files owned by that user/group elsewhere? I recall different packages have different preferences on these topics. /Simon signature.asc Description: PGP signature

Re: Upcoming d-i release vs. hard freeze

On Mon, 12 May 2025 at 19:58:10 +0200, Cyril Brulebois wrote: For various reasons, I'll be trying to get D-I Trixie RC 1 out this week, and I might freeze udeb-producing packages right away, or in the very next few hours/days. As a general rule, would you prefer maintainers of udeb-producing p

Re: Dropping awk?

Marco d'Itri writes: > On May 12, Simon Josefsson wrote: > >>Having some mechanism to create package-specific users seems like one >>useful goal, and I don't understand why each package has to write >>scripts to invoke 'adduser' and deal with a

Re: ITN procedure - more words, fewer acronyms please?

On Sat, 10 May 2025 at 11:20:41 +0100, Wookey wrote: ITM Modernise ITU Update ITR Revamp move-to-collective-maintainership (failing to think a good short name here - maybe:) ITC Collectivise ? ITPM Publically Maintain Whichever conventional name is chosen (one of these or something else), m

Re: Dropping awk?

Having some mechanism to create package-specific users seems like one useful goal, and I don't understand why each package has to write scripts to invoke 'adduser' and deal with all the complexity around that on their own. There could be a declarative interface a package can use an

Re: FTBFS when /bin is before /usr/bin in PATH?

Vincent Lefevre writes: > On 2025-05-07 18:18:25 +0200, Simon Josefsson wrote: >> Vincent Lefevre writes: >> >> > On 2025-05-07 14:40:01 +0200, Simon Josefsson wrote: >> >> I think a reasonable conservative system policy is PATH=/usr/bin and >> >&g

Re: FTBFS when /bin is before /usr/bin in PATH?

Santiago Vila writes: > El 7/5/25 a las 21:44, Simon McVittie escribió: >> That's not clear. Different developers have different > interpretations of what "packages must build successfully from source" > means - as a minimum they need to be buildable on our of

Re: FTBFS when /bin is before /usr/bin in PATH?

On Wed, 07 May 2025 at 20:43:24 +0200, Simon Josefsson wrote: Simon McVittie writes: I hope that packages don't assume that /usr/games is in the PATH at build time in any case. Is it a bug if they do? Buildd's have /usr/games in the default PATH so I don't think we notice no

Re: FTBFS when /bin is before /usr/bin in PATH?

Simon McVittie writes: > On Wed, 07 May 2025 at 14:40:01 +0200, Simon Josefsson wrote: >>I think we should give up on /usr/games and move those >>executables to /usr/bin, renaming any binaries that conflict. > > This seems somewhat off-topic for a discussion of FTBFS - I

Re: FTBFS when /bin is before /usr/bin in PATH?

On Wed, 07 May 2025 at 14:40:01 +0200, Simon Josefsson wrote: I think we should give up on /usr/games and move those executables to /usr/bin, renaming any binaries that conflict. This seems somewhat off-topic for a discussion of FTBFS - I hope that packages don't assume that /usr/games

Re: FTBFS when /bin is before /usr/bin in PATH?

Vincent Lefevre writes: > On 2025-05-07 14:40:01 +0200, Simon Josefsson wrote: >> I think a reasonable conservative system policy is PATH=/usr/bin and >> anything beyond that is something the user or system administrator have >> to add. I think we should give up on /usr

Re: FTBFS when /bin is before /usr/bin in PATH?

On Wed, 07 May 2025 at 15:21:43 +0200, Santiago Vila wrote: El 7/5/25 a las 13:40, Simon Josefsson escribió: I think we need to separate: ... 2) Removing the /bin symlink. ... (I don't think anybody is proposing 2) right now). My understanding is that the compatibility symlinks /bin,

Re: FTBFS when /bin is before /usr/bin in PATH?

have to add. I think we should give up on /usr/games and move those executables to /usr/bin, renaming any binaries that conflict. /Simon signature.asc Description: PGP signature

Re: FTBFS when /bin is before /usr/bin in PATH?

d that the 'gradle' behaviour buggy and the 'setpriv --reset-env' default PATH value surprising. Both of these issues can be resolved without doing anything about /etc/login.defs PATH, but it seems we may also think about /etc/login.defs changes too, because the gradle/setpriv problem

Re: FTBFS when /bin is before /usr/bin in PATH?

fixed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104784 4) The policy manual or developers reference could be amended to say that packages MUST only assume that /usr/bin and /usr/games (+ /usr/sbin for su/root) are in PATH and MUST handle being invoked as another alias. /Simon signature.asc Description: PGP signature

Re: FTBFS when /bin is before /usr/bin in PATH?

uired to make both work together is not worth it. Simon

Re: FTBFS when /bin is before /usr/bin in PATH?

rogram needs to know a path to supporting files, this path > should be known at build time of that program (here: gradle), and then > be baked into it (and maybe also be configurable at runtime). Agreed. /Simon signature.asc Description: PGP signature

Re: FTBFS when /bin is before /usr/bin in PATH?

Johannes Schauer Marin Rodrigues writes: > Hi, > > Quoting Simon Josefsson (2025-05-06 11:34:47) >> The problem seems that it is generating a relative path to its own command >> expanded via PATH, which doesn't work because there is no /share symlink but >> there

FTBFS when /bin is before /usr/bin in PATH?

ils/build/debian-bookworm-arm64-20250407-stage0/-/jobs/9927466433 /Simon signature.asc Description: PGP signature

Re: Adding Pre-Depends from linux-image packages to linux-base

On Sun, 04 May 2025 at 15:58:55 +, Bill Allombert wrote: Le Sat, May 03, 2025 at 04:08:55PM +0200, Ben Hutchings a écrit : I'm proposing to add a linux-run-hooks command to the linux-base package [1] that will then be used in all maintainer scripts of linux-image packages [2]. This requires

Re: Need advice on architecture exclusion when arch: all packages are involved.

On Mon, 28 Apr 2025 at 09:11:51 +0900, Charles Plessy wrote: on my side I have added a --64 option to the `routine-update` script (from the same-named package) that adds a build-dependency on architecture-is-64-bits, and plan to do the same for little-endian architectures. This seems like a suf

Re: Is it worth spending more time on adduser?

ny I work for) uses "adduser" to create users on shared machines, because it works, and allows us to actually get on with our main goals. That is actual value. Simon

Re: Associating .texi files to the media type text/prs.texi?

.types still the state of the art for MIME mappings, or should applications better use some other method? /Simon signature.asc Description: PGP signature

Re: Associating .texi files to the media type text/prs.texi?

Jakub Wilk writes: > * Simon Josefsson , 2025-04-23 10:45: >>https://www.iana.org/assignments/media-types/application/texinfo > > The "Published specification" link is: > https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#Info-Format-Specification &g

Re: Associating .texi files to the media type text/prs.texi?

Simon Josefsson writes: > Charles Plessy writes: > >> And the situation could be easily reverted by somebody declaring >> `text/texinfo` to the IANA. > > I did so now. There was a bunch of discussion back and forth with IANA and eventually application/texinf

Re: Dropping awk?

On Sun, 20 Apr 2025 at 12:48:08 +0200, Simon Josefsson wrote: has anyone considered if Debian should have official containers without apt and dpkg? What would those containers be useful for? I would have expected that in any use-case for a container without apt and dpkg, what you would really

Re: Dropping awk?

you want to have installed (which is usually not necessary), so something like this should be possible. /Simon signature.asc Description: PGP signature

Re: POSIX sh compatibility (Re: Dropping awk?)

mization pattern -- it is often combined with replacing copyleft software with non-copyleft implementations (GPL -> LGPL/MIT) -- but I can't deny that I find minimal containers really useful. /Simon signature.asc Description: PGP signature

Dropping awk?

sible to drop 'mawk' from the set of default tools in trixie? If not, what are the blockers? What is the method to find out what the blockers are? /Simon signature.asc Description: PGP signature

Re: MBF: Packages which break with nocheck

On Wed, 16 Apr 2025 at 19:59:47 +0200, Santiago Vila wrote: I wish reproducible-builds people would activate DEB_BUILD_OPTIONS=nocheck for the second build https://bugs.debian.org/786644 smcv

Re: MBF: Packages which break with nocheck

On Wed, 16 Apr 2025 at 18:40:00 +0200, Paul Gevers wrote: In one of the reports I read this: """ * When a package is built with the nocheck profile, it means: - DEB_BUILD_OPTIONS=nocheck (the tests should be skipped during the build) - DEB_BUILD_PROFILES=nocheck (Build-Depends marked are not

Re: Planning to remove team-based R packages from 32-bit and big-endian architectures.

On Wed, 16 Apr 2025 at 23:04:47 +0900, Charles Plessy wrote: If you need one of the team-maintained r-cran-* packages on a 32-bit or on a big endian architectures, which are not supported upstream, please contact me on the debian-r list and let's see how we can share the workload. It might be b

Re: Bug#1094969: git linked with OpenSSL

Henrik Ahlgren writes: > Simon Josefsson writes: > >> I think the idea behind the "proprietary system library" GPL exception >> is to make it possible to distribute GPL binaries linked to non-free >> system libraries on systems where that is pretty much unavoi

Re: Bug#1094969: git linked with OpenSSL

Michael Stone writes: > On Tue, Apr 15, 2025 at 03:38:38PM +0200, Simon Josefsson wrote: >>I believe that is a fairly new (~5 years?) approach within Debian. >>Debian used to treat OpenSSL incompatible with GPLv2 and that all code >>that link to OpenSSL has to have a GPL+Ope

Re: Bug#1094969: git linked with OpenSSL

ith GPLv2 and that all code that link to OpenSSL has to have a GPL+OpenSSL exception. Does anyone recall how and when this decision was made? Licensing wrt to libcurl and OpenSSL has been discussed before: https://lists.debian.org/debian-legal/2004/08/msg00221.html /Simon signature.asc Descrip

Re: Bug#1094969: git linked with OpenSSL

. I believe it would be better to work with rights holders to work out problems rather than to ignore requests and throw legal arguments at them. /Simon signature.asc Description: PGP signature

Re: MBF: Packages which break with nocheck

On Sun, 13 Apr 2025 at 13:22:21 +0200, Santiago Vila wrote: After building all the archive (trixie/sid) with nocheck, I only found 33 new packages which fail to build with nocheck that were not reported before. Admittedly a little bit more than I expected, but certainly not "hundreds" as some pe

Bug#1102652: ITP: golang-github-robinus2-golang-moving-average -- Moving average implementation for Go

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-robinus2-golang-moving-average Version : 1.0.0-1 Upstream Author : Robin Verlangen * URL : https://github.com/RobinUS2/golang-moving-average * License : Apache-2.0

Bug#1102649: ITP: golang-github-globocom-go-buffer -- Asynchronous data buffer for Go applications

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-globocom-go-buffer Version : 2.0.0-1 Upstream Author : Globo.com * URL : https://github.com/globocom/go-buffer * License : Expat Programming Lang: Go Description

Bug#1102648: ITP: golang-github-transparency-dev-trillian-tessera -- library for building tile-based transparency logs (tlogs)

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-transparency-dev-trillian-tessera Version : 0.1.1-1 Upstream Author : The Tessera authors * URL : https://github.com/transparency-dev/trillian-tessera * License : Apache-2.0

Bug#1102645: ITP: golang-github-transparency-dev-formats -- reusable formats related to transparency logs

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-transparency-dev-formats Version : 0.0~git20250403.313b830-1 Upstream Author : Google LLC * URL : https://github.com/transparency-dev/formats * License : Apache-2.0

Bug#1102291: ITP: lib1305 -- microlibrary for the Poly1305 one-time authenticator

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: lib1305 Version : 20250407 Upstream Author : Kaushik Nath, Daniel J. Bernstein, et al * URL : https://lib1305.cr.yp.to/ * License : public domain Programming Lang: C Description

Re: Proposal: drop libcrypt-dev dependency from libc6-dev

On Thu, 10 Apr 2025 at 07:37:32 +0200, Helmut Grohne wrote: how about libc6-dev stops depending on libcrypt-dev? I think this is a good idea for early in the forky cycle. I also investigated all apt-cache rdepends libcrypt1. That results in 151 source packages. ... * steam-installer This

Re: new archive signing keys for Debian 13/trixie

xternally held keys, what are the legal terms we use the keys under? What insight into key transparency questions do we have? What of those can we make public? How do they restrict what we are allowed to do? /Simon > These keys will *NOT* be put into use immediately; they have been

Re: Brief progress report on the Gatway to NEW project.

get, chances are lower that it doesn't contain serious mistakes. If you want to join the NEW team and do reviews there instead, I would be equally happy. /Simon signature.asc Description: PGP signature

Bug#1102169: ITP: landrun -- run any process in a secure unprivileged Landlock sandbox

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: landrun Version : 0.1.15-1 Upstream Author : Armin ranjbar * URL : https://github.com/zouuup/landrun * License : Expat Programming Lang: Go Description : Run any process in a

Bug#1101894: ITP: log-go -- Sigsum Transparency Log server implementation in Go

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: log-go Version : 0.15.2-1 Upstream Author : Sigsum * URL : https://git.glasklar.is/sigsum/core/log-go/ * License : BSD-2-Clause Programming Lang: Go Description : Sigsum

Bug#1101311: ITP: golang-github-openpubkey-openpubkey -- Reference implementation of OpenPubkey

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-openpubkey-openpubkey Version : 0.7.3-1 Upstream Author : EthanHeilman, jonnystoten, et al * URL : https://github.com/openpubkey/openpubkey * License : Apache-2.0

Re: popularity-contest and gpg

Jeremy Stanley writes: > On 2025-03-27 20:57:52 +0100 (+0100), Petter Reinholdtsen wrote: >> [Simon Josefsson] >> > Why does it need to encrypt data? >> >> To protect the users privacy. >> >> > Can't we just send telemetry over https like every

Re: popularity-contest and gpg

icies and transparency mechanisms in place, but the Debian PGP keys we have none of that. Which approach results in better outcome is probably a subjective opinion. /Simon signature.asc Description: PGP signature

Re: Bug#1101376: ITP: package-assembler -- CLI tool to create necessary files for a Debian package

Nicolas Peugnet writes: > On 27/03/2025 13:50, Simon Josefsson wrote: >> I've found the 'dh-make-golang make' tool incredibly useful to quickly >> get a suitable debian/* template for a project. I would find a similar >> tool that isn't Go-specific whi

Re: Bug#1101376: ITP: package-assembler -- CLI tool to create necessary files for a Debian package

t Go-specific which would could an upstream tarball and/or a URL to a homepage and attempt to create a debian/* template a missing tool to faciliate Debian package creation. /Simon signature.asc Description: PGP signature

Bug#1101362: ITP: golang-github-google-go-tspi -- TPM TSPI bindings for golang

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-google-go-tspi Version : 0.3.0-1 Upstream Author : Google * URL : https://github.com/google/go-tspi * License : Apache-2.0 Programming Lang: Go Description : TSPI

Bug#1101318: ITP: golang-github-awnumar-memguard -- Secure software enclave for storage of sensitive information in memory.

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-awnumar-memguard Version : 0.22.5-1 Upstream Author : Awn * URL : https://github.com/awnumar/memguard * License : Apache-2.0 Programming Lang: Go Description : Secure

Bug#1101317: ITP: golang-github-awnumar-memcall -- Cross-platform wrapper for memory-related system calls

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-awnumar-memcall Version : 0.4.0-1 Upstream Author : Awn * URL : https://github.com/awnumar/memcall * License : Apache-2.0 Programming Lang: Go Description : Cross

Bug#1101312: ITP: golang-filippo-bigmod -- constant-time library for big integers modulo a prime

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-filippo-bigmod Version : 0.0.3-1 Upstream Author : Filippo Valsorda * URL : https://github.com/FiloSottile/bigmod * License : BSD-3-clause Programming Lang: Go Description

Bug#1101310: ITP: opkssh -- opkssh (OpenPubkey SSH)

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: opkssh Version : 0.3.0-1 Upstream Author : * URL : https://github.com/openpubkey/opkssh * License : Apache-2.0 Programming Lang: Go Description : opkssh (OpenPubkey SSH) opkssh

Re: Bug#1101076: ITP: rsync -- rsync in Go! implements client and server, which can send or receive files (upload, download, all directions supported)

On Sat, 22 Mar 2025 at 21:50:00 +, Samuel Henrique wrote: * Package name: rsync This is going to need a different name, unless you are aiming for it to completely replace and supersede the original (samba.org) rsync. Upstream seems to call their main executable gokr-rsync, which seem

Bug#1101009: ITP: python-freezegun -- allow Python tests to travel through time via datetime

Package: wnpp Severity: wishlist Owner: Simon Josefsson X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org * Package name: python-freezegun Version : 1.5.1 Upstream Author : Steve Pulec * URL : https://github.com/spulec/freezegun/ * License

Bug#1100754: ITP: golang-github-tink-crypto-tink-go-awskms -- Extension to Tink Go that provides AWS KMS integration

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-tink-crypto-tink-go-awskms Version : 2.1.0-1 Upstream Author : Tink Cryptography Library * URL : https://github.com/tink-crypto/tink-go-awskms * License : Apache-2.0

Bug#1100752: ITP: golang-github-tink-crypto-tink-go -- Go implementation of Tink

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-tink-crypto-tink-go Version : 2.3.0-1 Upstream Author : Tink Cryptography Library * URL : https://github.com/tink-crypto/tink-go * License : Apache-2.0 Programming Lang: Go

Re: Call for participation in tag2upload closed beta

bian.org/testing/dgit/dgit-maint-gbp.7.en.html#UPLOADING I'm doing this on a laptop running Trisquel aramo (Ubuntu 22.04 clone) with plenty of packages installed from Guix, including GnuPG, git and even dpkg. I was positively surprised dgit didn't blow up, good job! /Simon signature.asc Description: PGP signature

Re: Call for participation in tag2upload closed beta

ball for this > -- please give one of those a try. It worked, thank you! For reference: dgit --gbp push-source --quilt=baredebian+tarball --deliberately-not-fast-forward How do I make the next upload using tag2upload? /Simon signature.asc Description: PGP signature

Re: Call for participation in tag2upload closed beta

mes. Are you sure you want to continue connecting (yes/no/[fingerprint])? /Simon signature.asc Description: PGP signature

Bug#1100812: ITP: golang-github-smallstep-scep -- Go SCEP server

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-smallstep-scep Version : 0.0~git20250221.171a5fa-1 Upstream Author : Smallstep * URL : https://github.com/smallstep/scep * License : Expat Programming Lang: Go

Bug#1100761: ITP: golang-github-tink-crypto-tink-go-gcpkms -- Extension to Tink Go that provides Google Cloud KMS integration

Package: wnpp Severity: wishlist Owner: Simon Josefsson * Package name: golang-github-tink-crypto-tink-go-gcpkms Version : 2.2.0-1 Upstream Author : Tink Cryptography Library * URL : https://github.com/tink-crypto/tink-go-gcpkms * License : Apache-2.0

Re: Bug#1100571: ITP: mgmt -- next generation config management

Hi, On 3/15/25 22:58, Thomas Goirand wrote: Description : next generation config management [...] Can you reword the description so that it reads less like an advertisement? "next generation", compared to what? Simon OpenPGP_0xEBF67A846AABE354.asc Description: Open

Re: Call for participation in tag2upload closed beta

imple 'dpkg -i' of 12.9 worked now, and I was able to run 'dgit build' in my existing libntlm git clone. I haven't been using dgit before this, but maybe this is sufficient to count me as a dgit user. Packages (for example): libntlm, cppi, git2cl, guile-fibers /Simon

Re: Revisiting the idea of pre-NEW peer review? (Re: Bits from DPL)

same checks as those that happen in the NEW > queue"). +1 -- that is the responsibility of the main Salsa pipeline, I think. > Let me know how I can help! I enjoy reviewing copyright files, so if any > arise, please send them my way :) I hope that we can find some problem to fix in the `litetlog` packaging when I submit it, arguing for the awesomeness of this effort :) /Simon signature.asc Description: PGP signature

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

especially companies that use our volunteer time without compensation -- we're the *free* software community, not the *gratis* software community. Simon

Re: Revisiting the idea of pre-NEW peer review? (Re: Bits from DPL)

thread, and the newgateway-team homepages, but I still don't understand how you think the process should work. Could we test the process by reviewing 'litetlog'? https://salsa.debian.org/go-team/packages/litetlog/ It is already in NEW queue, but maybe more eyes on it will catch mist

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

Aurélien COUDERC writes: > Le 10 mars 2025 11:56:28 GMT+01:00, Simon Josefsson a > écrit : > >>https://www.gnu.org/distros/optionally-free-not-enough.html >> >>https://www.gnu.org/philosophy/install-fest-devil.html > > … of course … that's where the cor

General Questions about Translations and what a package maintainer has to do

it to remove(!) locations on checkout and restore them from the pot file on commit, that solves the majority of conflicts.    Simon

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

in that one's own opinion is best as to try to >> prevent other people from making their own decisions by hiding even the >> existence of a mechanism to install debian on their machine. >> > > Simon, > > > Do know that is OK that there are differences in view, o

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

Philip Hands writes: > Hi Simon, > > Simon Josefsson writes: > >> While this may be fine to you it is not fine to me, and it is fine to >> disagree on that. > > If there were a method of building images that did not touch the > non-free components, I presume tha

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

nferior because you need to live with all the flaws they have -- and a large part of that is that the free software community is not apologizing for the experiences users have with closed-source drivers. Simon

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

to that the arguments for free software exists but not everyone is convinced by those arguments and instead prefer proprietary software. /Simon signature.asc Description: PGP signature

Re: NEW review & revision process (or lack thereof) (Re: Growing new FTP-masters (Re: Bits from DPL))

ange ftp-master's private review process but to have this public pre-review process to smoothen the process a bit. /Simon signature.asc Description: PGP signature

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

Ansgar 🙀 writes: > Hi, > > On Sun, 2025-03-09 at 15:58 +0100, Simon Josefsson wrote: >> Ansgar 🙀 writes: >> >> > Hi, >> > >> > On Sun, 2025-03-09 at 14:19 +0100, Simon Josefsson wrote: >> > > Our experience seems to differ, I now

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

"Andrew M.A. Cater" writes: > On Sun, Mar 09, 2025 at 03:58:59PM +0100, Simon Josefsson wrote: >> >> Agreed. However none of that hardware require me to load non-free >> firmware from my operating system, which is my point. That situation is >> sufficient

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

Ansgar 🙀 writes: > Hi, > > On Sun, 2025-03-09 at 14:19 +0100, Simon Josefsson wrote: >> Our experience seems to differ, I now run Trisquel and Guix on many of >> my home and machines and servers.  For my uses they all work without >> non-free firmware.  You ha

Re: Growing new FTP-masters (Re: Bits from DPL)

On Sun, 09 Mar 2025 at 19:32:32 +0800, Sean Whitton wrote: IMO it is the maintainer's responsibility to ensure that NEW+unstable together is always all installable, if you see what I mean. Do I assume correctly that this principle can be weakened for experimental-NEW? As a general principle

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

Matthias Urlichs writes: > On 08.03.25 21:09, Simon Josefsson wrote: >> I read this outcome as fairly clear message that, no, Debian does not >> want to provide a second set of installer images, and is not interested >> in contributions to make them. > > Another way t

Re: Growing new FTP-masters (Re: Bits from DPL)

Sean Whitton writes: > Hello, > > On Sun 09 Mar 2025 at 12:17pm +01, Simon Josefsson wrote: > >> Sean Whitton writes: >> >>> The docs are public: https://salsa.debian.org/ftp-team/manpages >> >> Those are helpful even for me as uploading packa

Re: Growing new FTP-masters (Re: Bits from DPL)

ike "we don't want to forbid it but it causes us more work so please don't do it" is perfectly fine too. Writing that down helps people do the right thing. The question has come up two times for me when sponsoring new Go package uploads. /Simon signature.asc Description: PGP signature

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

Aurélien COUDERC writes: > Le 8 mars 2025 21:09:00 GMT+01:00, Simon Josefsson a > écrit : > >>I read this outcome as fairly clear message that, no, Debian does not >>want to provide a second set of installer images, and is not interested >>in contributions to make

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

Ubuntu packages and maintain a debian-installer fork). /Simon signature.asc Description: PGP signature

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

Johannes Schauer Marin Rodrigues writes: > Hi, > > Quoting Simon Josefsson (2025-03-08 13:43:26) >> My point was that there is no reasonable way to gain confidence about >> security properties of any piece of non-free microcode. Everyone can now >> produce AMD m

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

Bill Allombert writes: > Le Fri, Mar 07, 2025 at 07:33:53PM +0100, Simon Josefsson a écrit : >> pan...@disroot.org writes: >> >> > I urge Debian to rethink its decision to officially include non-free >> > firmware and correct the social contract. Instead of

Re: Revisiting the idea of pre-NEW peer review? (Re: Bits from DPL)

eam/pipeline/-/issues/395 The difference of having a 'include' statement in debian/salsa-ci.yml is not that different from adding some 'variables:' to enable a lrc-job, so it is not critical to add it to the standard pipeline. Maybe if more people start to use it we gain

Re: Reconsidering Debian’s Inclusion of Non-Free Firmware - A Call for Discussion

firmware is not available. My perception is that the Debian developer community rejected this, and I'm not sure people are ready to reconsider just yet (the trend seems to be the opposite way). Fortunately there are good libre alternatives in Trisquel and Guix available for recommendation m

  1   2   3   4   5   6   7   8   9   10   >