Re: Heimdal Bugs re update-alternatives

2025-02-15 Thread Brian May
Gabor Gombas writes: > This one is nothing special - some commands behaving differently based > on argv[0] is a traditional Unix thing. "(exec -a klist klist.heimdal)" > should work. Sorry, not 100% sure what you are trying to say here. Are you suggesting that https://bugs.debian.org/cgi-bin/bu

Re: Heimdal Bugs re update-alternatives

2025-02-15 Thread Brian May
Gabor Gombas writes: > Exactly - that's why making the KDC package Conflicts: with the other > implementation would be a quick fix. There aren't many KDC > implementations, and I think Shishi does not use kadmin (I'm not sure, I > never used it), so maintaining such Conflicts: does not sound like

Re: Upstreams with "official" tarballs differing from their git

2025-02-15 Thread Sean Whitton
Hello, On Sat 15 Feb 2025 at 12:10pm +01, Stéphane Glondu wrote: > Summary to other debian-devel readers: we are facing some upstreams that > publish "official" tarballs that differ from what is in their git. The > differences may include: variable substitutions, generated files... I guess > this

Re: ostree

2025-02-15 Thread Christian Kastner
On 2025-02-15 23:13, Simon McVittie wrote: > On Sat, 15 Feb 2025 at 21:08:03 +0100, Christian Kastner wrote: >> I read somewhere that Fedora can do full rollbacks because the make use >> of "ostree". See [1] for example. We have ostree in our Archive [2]. >> >> I'm not familiar with it yet, but had

Re: A 2025 NewYear present: make dpkg --force-unsafe-io the default?

2025-02-15 Thread Preuße , Hilmar
On 13.02.2025 08:13, Bálint Réczey wrote: Hello, I could not make it for New Year's Eve, buth thanks to FTP Masters kindly accepting the package it arrived for Valentine's day. :-) https://balintreczey.hu/blog/supercharge-your-installs-with-apt-eatmydata-because-who-needs-crash-safety-anyway/ I

Re: ostree (was: Filesystem snapshotting in dpkg)

2025-02-15 Thread Simon McVittie
On Sat, 15 Feb 2025 at 21:08:03 +0100, Christian Kastner wrote: > On 2024-12-28 15:21, Guillem Jover wrote: > > In this case (filesystem snapshotting), I do think dpkg is (currently at > > least) really the wrong place, for at least the following reasons: > > I read somewhere that Fedora can do fu

Re: Filesystem snapshotting in dpkg (was Re: A 2025 NewYear present: make dpkg --force-unsafe-io the default?)

2025-02-15 Thread Christian Kastner
Hi, I have not been monitoring this thread but this new Subject popped up, and then something came to mind: On 2024-12-28 15:21, Guillem Jover wrote: > Port-specific or hardware specific optimizations might make sense in > dpkg, but that depends on the type, semantics, testability and > intrusive

Re: Upstreams with "official" tarballs differing from their git

2025-02-15 Thread Marco d'Itri
On Feb 15, Stéphane Glondu wrote: > On the other hand, insisting on using upstream VCS contents can lead to ugly > hacks in Debian packaging, such as what you are describing. I must admit I > usually use "official" tarballs to avoid these hacks (and maybe a little out > of laziness). In my own pa

Re: Packages with a history of security issues and whose packaged version is not up to date

2025-02-15 Thread Chris Hofstaedtler
* Colin Watson [250214 18:13]: > On Fri, Feb 14, 2025 at 03:28:35PM +0100, Marc Haber wrote: > > Especially if the list just goes the (wrong) way of so many commercial > > security tools and/or consultants who just compare version numbers and > > flag our stable versions as vulnerable regardless w

Re: Upstreams with "official" tarballs differing from their git

2025-02-15 Thread Julien Puydt
Hi, Le samedi 15 février 2025 à 12:10 +0100, Stéphane Glondu a écrit : > > My approach to this specific problem would be to add to dune the > possibility to use some configuration file (or environment variables) > as input for the substitutions, instead of directly querying the > VCS. This con

Re: Upstreams with "official" tarballs differing from their git

2025-02-15 Thread Julien Plissonneau Duquène
Hi, Le 2025-02-15 13:39, kpcyrd a écrit : Diff between those two: https://whatsrc.org/diff-right-trimmed/sha256:146d2d673358b7927d9a3c74e22b6b0e7f9a1aee2a4307afbe6ac07f12764130/sha256:599ff98cbab933a8b3640a084b12a5308a20795c192855ee454a8c1c16fa4dac That divergence is reflected between the off

Re: Upstreams with "official" tarballs differing from their git

2025-02-15 Thread Jeremy Stanley
On 2025-02-15 12:33:16 +0100 (+0100), Daniel Gröber wrote: [...] > FYI: If all upstream wants is git metadata I like to introduce them to the > wonderful, but obscure, git `export-subst` feature. See git-attributes(1). > > Works with forges, git-archive and everything. > > Example: > https://gith

Bug#1096035: ITP: hare-json -- JSON support for hare

2025-02-15 Thread Guilherme Puida Moreira
Package: wnpp Severity: wishlist Owner: Guilherme Puida Moreira X-Debbugs-Cc: debian-devel@lists.debian.org, guilhe...@puida.xyz * Package name: hare-json Version : 0.24.2 Upstream Contact: Drew DeVault * URL : https://git.sr.ht/~sircmpwn/hare-json * License :

Re: Upstreams with "official" tarballs differing from their git

2025-02-15 Thread kpcyrd
On 2/15/25 12:10 PM, Stéphane Glondu wrote: I realize my previous email was a bit short: I was wondering if this .tbz still source code because in the autotools world, package sources come with configure scripts ready to run, but the good practice in Debian is to regenerate those from configure.a

Re: Building packages in the future.

2025-02-15 Thread Bastian Blank
On Sun, Jan 05, 2025 at 11:58:40PM +0100, Chris Hofstaedtler wrote: > Maybe you can consider using a time namespace (unshare -T) and > change the system date/time in that namespace. As those jobs already run in throw away VM, just change the system time. You have to change it back to be able to ta

Re: Building packages in the future.

2025-02-15 Thread Santiago Vila
El 15/2/25 a las 10:44, Paul Gevers escribió: Can the Release Managers suggest a calendar for raising those bugs, first to important, then to serious? What I had in mind was that you'd file the bugs and after some time (say, one or two months) raised them, giving maintainers a bit more time th

Re: Upstreams with "official" tarballs differing from their git

2025-02-15 Thread Daniel Gröber
On Sat, Feb 15, 2025 at 12:10:06PM +0100, Stéphane Glondu wrote: > > I fixed the elpi package by using something a bit hackish: I added git > > as dep, and if I don't see a .git in the build directory, I create one! > > > > Here is what the execute_before_dh_auto_build target does: > > if

Upstreams with "official" tarballs differing from their git

2025-02-15 Thread Stéphane Glondu
Hi, Le 15/02/2025 à 10:08, Julien Puydt a écrit : Usually, projects using this trick publish tarballs with substitutions applied:    https://github.com/LPCIC/elpi/releases/tag/v2.0.7 (here, elpi-2.0.7.tbz). I realize my previous email was a bit short: I was wondering if this .tbz still sour

Re: Building packages in the future.

2025-02-15 Thread Paul Gevers
Hi Santiago Sorry for dropping the ball on this. On 05-01-2025 17:56, Santiago Vila wrote: I was told that it was ok to consider those bugs as "RC for trixie" but I was also requested to be nice when reporting those bugs, so I have been reporting them as severity:normal (except when the future