On Sun, Dec 01, 2024 at 09:16:03PM -0600, G. Branden Robinson wrote:
> These things are ugly, which is why I suppose they haven't caught on
> despite being around for decades, but I would guess that this problem
> space is such that there are no non-ugly solutions apart from "just
> stick to ASCII"
nick black left as an exercise for the reader:
> it's my understanding that Punycode's objective is to be "clean"
> with regards to things that match against the hostname character
> set, hence its pickup for IDN (where it's expected that DNS
> will be traversing all kinds of network middleware). a
G. Branden Robinson left as an exercise for the reader:
> It sounds like you want something isomorphic, if not identical, to,
> Punycode.
>
> https://en.wikipedia.org/wiki/Punycode
it's my understanding that Punycode's objective is to be "clean"
with regards to things that match against the hostn
On Mon, Dec 02, 2024 at 09:38:28AM +0800, kindusmith wrote:
> 1. First, root and ordinary users will not be able to use commands in each
> other's directories, which will greatly increase their security
(typical level of argumentation)
--
WBR, wRAR
signature.asc
Description: PGP signature
Hi nick (and Marc),
At 2024-12-01T18:43:28-0500, nick black wrote:
> Gioele Barabucci left as an exercise for the reader:
> > You may have misunderstood that phrase. I was not referring to the
> > fact that there are no standardized normalization forms for Unicode
> > (I explicitly mention Annex 1
At 2024-12-02T09:38:28+0800, kindusmith wrote:
> 1. First, root and ordinary users will not be able to use commands in
> each other's directories, which will greatly increase their security
>
> 2. If /usr is partitioned separately instead of a unified / partition,
> ordinary users can also use com
1. First, root and ordinary users will not be able to use commands in
each other's directories, which will greatly increase their security
2. If /usr is partitioned separately instead of a unified / partition,
ordinary users can also use commands in /usr/bin, which increases
convenience
Of c
Package: wnpp
Severity: wishlist
Owner: g...@jdknight.me
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: releng-tool
Version : 1.4.0
Upstream Contact: James Knight
* URL : https://releng.io/
* License : BSD-2-Clause
Programming Lang: Python
Desc
Package: wnpp
Severity: wishlist
Owner: Mathias Gibbens
X-Debbugs-CC: debian-devel@lists.debian.org, debian...@lists.debian.org
* Package name: golang-github-minio-cli
Version : 1.24.2-1
Upstream Author : MinIO
* URL : https://github.com/minio/cli
* License : E
Gioele Barabucci left as an exercise for the reader:
> You may have misunderstood that phrase. I was not referring to the fact that
> there are no standardized normalization forms for Unicode (I explicitly
> mention Annex 15 in [1]), but to the fact that there is no standard that
> specifies which
Marc Haber left as an exercise for the reader:
> > * any upstream tool could say "bad idea" and refuse patches,
> >requiring their long term management,
>
> Depending of how important this tool is, we could get away without
> patching and probably not even documenting this failure.
This kind
On 28/11/24 11:28, Michal Politowski wrote:
POSIX explicitly limits itself of a subset of ASCII, so it is not going to
mandate any normalization form. Are there other standards (or initiatives)
in this area that you know of?
What about RFC 8265?
"Preparation, Enforcement, and Comparison of Inte
On 2024-12-01 12:11:55, Otto Kekäläinen wrote:
> Hi,
>
> > > Wouldn't another option be to allow for multiple ways to write things,
> > > as long as they are consistently written in the same style for the same
> > > purpose?
> > >
> > > I prefer writing DEP 4711 in text.
> > >
> > > I prefer writi
Hi,
> > Wouldn't another option be to allow for multiple ways to write things,
> > as long as they are consistently written in the same style for the same
> > purpose?
> >
> > I prefer writing DEP 4711 in text.
> >
> > I prefer writing https://example.org/dep4711.txt in URLs.
> >
> > I prefer writ
Le dimanche 01 décembre 2024 à 11:42 +0100, Paul Gevers a écrit :
> Hi,
>
> On 12/1/24 11:36, Julien Puydt wrote:
> > Can you try:
> >
> > sbuild --build-dir=~/Debian/repo --extra-package=~/Debian/repo
> >
> > This should save all binary packages to the directory and use
> > them in
I made a mistake, this is already packaged. I'm closing the ITP.
https://tracker.debian.org/pkg/dataclasses-json
--
Edward
Package: wnpp
Severity: wishlist
Owner: Edward Betts
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-pyt...@lists.debian.org
* Package name: dataclasses-json
Version : 0.6.7
Upstream Author : Charles Li
* URL : https://github.com/lidatong/dataclasses-json
* Licens
Package: wnpp
Severity: wishlist
Owner: Danial Behzadi
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: plattenalbum
Version : 2.2.1
Upstream Contact: Martin Wagner
* URL : https://github.com/SoongNoonien/plattenalbum
* License : GPL-3+
Programmi
Otto Kekäläinen writes:
> Basically you can start by forking
> https://salsa.debian.org/agx/git-buildpackage on Salsa and then start
> hacking away on the things you want to improve.
>
> If you want to do Python coding, fixing this issue could be an easy
> one to start with:
> https://bugs.debian
Hi,
On 12/1/24 11:36, Julien Puydt wrote:
Can you try:
sbuild --build-dir=~/Debian/repo --extra-package=~/Debian/repo
This should save all binary packages to the directory and use them in
subsequent runs.
It doesn't: it fails saying BUILD_DIR doesn't exist.
Does it still me
Hi
Le dim. 1 déc. 2024, 11:14, Jochen Sprickerhof a
écrit :
>
> Can you try:
>
> sbuild --build-dir=~/Debian/repo --extra-package=~/Debian/repo
>
> This should save all binary packages to the directory and use them in
> subsequent runs.
>
It doesn't: it fails saying BUILD_DIR doesn't exist.
I
Hi Julien,
* Julien Puydt [2024-12-01 10:59]:
My use case isn't with a single package, but with a bunch of them. For
example, updating the coq package means about fifty packages in seven
stages. That means I compile all packages of one of the stages
(sometimes in parallel), move the results to
Hi,
Le samedi 23 novembre 2024 à 22:20 +0100, Philipp Kern a écrit :
>
> https://wiki.debian.org/sbuild
>
I tried to update my DD setup to this new kind of sbuild using the
above documentation, and there is something I don't manage to replicate
from my previous setup.
My use case isn't with a
23 matches
Mail list logo
