Re: BuildProfileSpec example equivalence question

2024-10-16 Thread Timo Röhling
Hi Josch, * Johannes Schauer Marin Rodrigues [2024-10-16 * 09:21]: The third example on https://wiki.debian.org/BuildProfileSpec is: I now changed the example to one that is actually used in the wild. I hope I didn't mess up the wording. Hope this makes things clearer. The final sentence in

Bug#1085206: ITP: evalidate -- Validation and secure evaluation of untrusted Python expressions

2024-10-16 Thread Colin Watson
Package: wnpp Severity: wishlist Owner: Colin Watson X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: evalidate Version : 2.0.3 Upstream Contact: Yaroslav Polyakov * URL : https://github.com/yaroslaff/evalidate * License : MIT Programming Lang: Py

Re: BuildProfileSpec example equivalence question

2024-10-16 Thread Johannes Schauer Marin Rodrigues
Hi Feri, Quoting Ferenc Wágner (2024-10-12 19:39:27) > The third example on https://wiki.debian.org/BuildProfileSpec is: > > Build-Depends: foo > > In this case, the source package would build depend on foo if either > both, nocheck and cross are active or if the profile nocheck is

Private code: to forge, or not to forge?

2024-10-16 Thread Iustin Pop
Hi all, this is offtopic (sorry!), but since we kept discussing Salsa - I wonder, what are people doing for private code? I have around 40 git repositories of private code that I keep, and while a subset of them are somewhat managed (living under a common `gitroot` directory), not all are. Plus, a

Re: Will i386 released for Trixie and if no can we stop working on it now?

2024-10-16 Thread Andrey Rakhmatullin
On Thu, Oct 17, 2024 at 10:48:21AM +0800, Sean Whitton wrote: > Hello, > > I hadn't heard of these architecture-is-64-bit and not-supported-on > metapackages(?). Would someone who knows how they are meant to work > consider submitting a patch for Policy? Thanks. I think they, just like isa-supp

Re: Private code: to forge, or not to forge?

2024-10-16 Thread Jan-Benedict Glaw
On Wed, 2024-10-16 19:24:32 +0200, Daniel Baumann wrote: > On 10/16/24 18:18, Iustin Pop wrote: > > Gitea/Forgejo are common recommended solutions for "home hosting", but > > neither is packaged. > > (jftr) I'm currently working with Forgejo upstream to get one last > feature implemented that we

Re: Will i386 released for Trixie and if no can we stop working on it now?

2024-10-16 Thread Sean Whitton
Hello, I hadn't heard of these architecture-is-64-bit and not-supported-on metapackages(?). Would someone who knows how they are meant to work consider submitting a patch for Policy? Thanks. -- Sean Whitton signature.asc Description: PGP signature

Re: BuildProfileSpec example equivalence question

2024-10-16 Thread Johannes Schauer Marin Rodrigues
Hi Timo, Quoting Timo Röhling (2024-10-16 10:00:25) > >> The third example on https://wiki.debian.org/BuildProfileSpec is: > >I now changed the example to one that is actually used in the wild. > >I hope I didn't mess up the wording. Hope this makes things > >clearer. > The final sentence in the

file-roller old bugs

2024-10-16 Thread Mina
hi i noticed that there is a lot of very old( > 13 years old) outstanding bugs in file-roller bugs page and some of then i confirmed that it's n longer reproducible most probably fix is it ok to close it and archive it or what is your suggestion on that -- Best Regards Mina

Re: file-roller old bugs

2024-10-16 Thread Andrew M.A. Cater
On Wed, Oct 16, 2024 at 11:43:59PM +0300, Mina wrote: > hi > i noticed that there is a lot of very old( > 13 years old) > outstanding bugs in file-roller bugs page and some of then i confirmed > that it's n longer reproducible most probably fix > is it ok to close it and archive it or what is your

Re: Private code: to forge, or not to forge?

2024-10-16 Thread Daniel Baumann
On 10/16/24 18:18, Iustin Pop wrote: > Gitea/Forgejo are common recommended solutions for "home hosting", but > neither is packaged. (jftr) I'm currently working with Forgejo upstream to get one last feature implemented that we'll need at work to switch to it, and then finish the packaging of it