Hi Tobias!
On 2024-02-05 10:43, Tobias Heider wrote:
> On Sat, Jan 26, 2013 at 12:38:07AM +, Stuart Prescott wrote:
>>
>> The maintainer for the "nvi" package has indicated that he is unable to
>> maintain this package for the time being. I'm marking this package as
>> orphaned
>> now.
>
> Lo
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
X-Debbugs-Cc: debian-devel@lists.debian.org, par...@debian.org, d...@frign.de
* Package name: libgrapheme
Version : 2.0.2
Upstream Author : Laslo Hunhold
* URL : https://libs.suckless.org/libgrapheme/
* License
Vincent Bernat wrote on 25/07/2022:
> Would it be possible to also make it available on port 465 without
> STARTTLS?
I'd also prefer "full TLS" over STARTTLS, as it is simpler (encryption
from the beginning instead starting with a plaintext session) and
somehow more secure than STARTTLS, see [1],
Richard Laager wrote on 23/01/2022:
> On 1/19/22 15:04, Bernhard Schmidt wrote:
>> On 19.01.22 20:34, Richard Laager wrote:
>>> 2. I create transitional binary packages in src:ntpsec:
>
> I got to thinking about this more. This won't work, because src:ntp is
> 1:4.2.8p15+dfsg-1 and src:ntpsec is
Richard Laager wrote on 19/01/2022:
> On 1/18/22 11:21 AM, Paride Legovini wrote:
> > I'd prefer making ntp a dummy package depending on ntpsec rather than
> > having src:ntpsec takeover bin:ntp.
>
> If I understand correctly, you're suggesting src:ntp builds bin
Marco d'Itri wrote on 18/01/2022:
> On Jan 18, Michael Biebl wrote:
>
>> If "ntp" the binary package would become a transitional package that
>> installs chrony, that'd be fine with me if that eases the transition.
> I am not sure that this would be practical since they cannot share the
> same c
Bernhard Schmidt wrote on 17/01/2022:
> ntpsec and ntp should be largely configuration compatible, so even a
> takeover of the binary package names might be practical.
I played a bit with ntpsec some time ago, I remember being very pleased
with it, and I think it can very well replace ntp in Book
Stephan Lachnit wrote on 25/02/2021:
I had a discussion with someone who wants to contribute to Debian,
but doesn't want to publish their real name in fear of getting doxed.
I never really thought of this, and I'm not sure how much one can
contribute to Debian without posting some kind of real n
[Resent as debian-devel doesn't allow attachments.]
Hello,
I tried to do a synthesis of past August/September thread on the
finalization of DEP-14 [1], see:
https://salsa.debian.org/dep-team/deps/-/merge_requests/1/diffs
I took Raphaël's proposal [1] and integrated the following changes:
(1
f two or three) and the
branch name (sans vendor) _always_ matches the changelog.
Proposal "B":
Raphael Hertzog, Russ Allbery, et al. upload to unstable or experimental
depending on various factors, which notably may not be known a priori.
In this case, it would be annoying busywork to h
Raphael Hertzog wrote on 04/09/2020:
Hi,
On Fri, 04 Sep 2020, Paride Legovini wrote:
As the name of the development branch is not specified anymore, should dep14
ask for it to be the repository default branch? Otherwise there's no safe
I took this as granted. But maybe we should ma
Raphael Hertzog wrote on 29/08/2020:
@@ -200,7 +204,7 @@ developers and the package maintainers are not the same set
of persons.
When upstream is Debian (or one of its derivative), the upstream vendor
should not use the usual `/` prefix (but all others vendors should
-do so). The main d
Raphael Hertzog wrote on 31/08/2020:
> Hi,
>
> On Mon, 31 Aug 2020, Paride Legovini wrote:
>> A tl;dr version of my idea is: let's remove the special treatment for
>> development releases, treating e.g. debian/unstable like a stable
>> release. Optionally
Raphael Hertzog wrote on 31/08/2020:
> On Mon, 31 Aug 2020, Paride Legovini wrote:
>> What I propose is to require for dep14 compliance that uploads to
>> are to be cut from debian/ branches, unless
>> is experimental. This allows to checkout the "maintainer
>> v
Hi,
The Wanderer wrote on 31/08/2020:
> On 2020-08-31 at 06:49, Paride Legovini wrote:
>
>> Simon McVittie wrote on 30/08/2020:
>>
>>> On Sun, 30 Aug 2020 at 15:36:53 +0200, Raphael Hertzog wrote:
>>>
>>>> If I know that the next upstream releas
Raphael Hertzog wrote on 30/08/2020:
> On Sat, 29 Aug 2020, Richard Laager wrote:
>> That said, I do understand we give a lot of deference to developers'
>> workflows. So I have no objection to DEP-14 supporting this workflow
>> with debian/latest. But I would like to see it (debian/latest)
>> rech
Simon McVittie wrote on 30/08/2020:
> On Sun, 30 Aug 2020 at 15:36:53 +0200, Raphael Hertzog wrote:
>> If I know that the next upstream release
>> breaks backwards compatitibly and that it will have to mature a long time
>> in experimental until all other packages are ready, I might start to
>> pac
Thomas Goirand wrote on 27/04/2020:
> On 4/27/20 12:18 AM, Paride Legovini wrote:
>> It's still one static shared secret you need to enter every time. If it
>> gets stolen, because your browser or your computer is compromised, or in
>> a MITM attack where the attacke
Thomas Goirand wrote on 26/04/2020:
> On 4/25/20 11:14 PM, Bernd Zeimetz wrote:
>> Actually I think 2FA should be enforced for everybody.
>> Even debian.org related passwords might get lost.
>
> I use strong password, stored with keepassxc, with the password db
> encrypted using the HMAC of my yub
Michael Biebl wrote on 26/04/2020:
> Am 26.04.20 um 14:36 schrieb Mattia Rizzolo:
>> On Sun, Apr 26, 2020 at 02:07:54PM +0200, Bernd Zeimetz wrote:
>>> There are even cli tools that do the same stuff. I'd guess there is at
>>> least one on Debian.
>>
>> Indeed, after I first lost a phone, and a se
Geert Stappers wrote on 17/03/2020:
> On Mon, Mar 16, 2020 at 07:40:40PM -0400, Peter Silva wrote:
>> On Mon, Mar 16, 2020 at 7:27 PM Guus Sliepen wrote:
>>> On Mon, Mar 16, 2020 at 01:02:47PM +, Wookey wrote:
>>>
I hadn't realised how fat nano is (not the only consideration of
course
Bagas Sanjaya wrote on 25/06/2019:
> Hello Debian Developers,
>
> Debian provides more than 51000 packages. From those packages, some are
> appropriate for every ages, and some others are
> only for specific age groups for some reasons.
>
> In order to inform to users, especially parents, about
Hello Adrian,
Adrian Bunk wrote on 08/03/2019:
> On Thu, Mar 07, 2019 at 10:11:41PM +0100, Paride Legovini wrote:
>> Michael Stone wrote on 07/03/2019:
>>> On Thu, Mar 07, 2019 at 09:02:23PM +0100, Holger Wansing wrote:
>>>>> I'm actually wondering if this
Michael Stone wrote on 07/03/2019:
> On Thu, Mar 07, 2019 at 09:02:23PM +0100, Holger Wansing wrote:
>>> I'm actually wondering if this is a good idea..
>>>
>>> There are lot of other packages installing cronjobs and people, I would
>>> assume, expect that they will run.
cronjobs run even without
Hi Peter,
Peter Pentchev wrote on 04/02/2019:
> So these days I decided that DEP-14[1] actually seems to be a Good
> Thing(tm) and I started thinking about switching my packages' Git
> repositories to this layout. However, I immediately hit a snag:
> in some of my repositories the upstream branch
Lars Wirzenius wrote on 03/10/2018:
> The problem: when a .deb package is installed, upgraded, or removed,
> the maintainer scripts are run as root and can thus do anything.
>
> Sometimes what they do is an unwelcome surprise to the user. For
> example, the Microsoft Skype .deb and the Google Chro
Tobias Frost wrote on 26/09/2018:
> The yesteday uploaded Developer's Reference has now got a chapter
> about "Package Salvaging".
Thanks Tobias for this work, I truly think Debian will benefit a lot
from it. I already filed an ITS: #909663. The Developer's Reference was
smooth to follow, I just
Adam Borowski wrote on 14/09/2018:
> On Thu, Sep 13, 2018 at 11:28:36PM +0200, Thomas Goirand wrote:
>>> For example, in the Rust team, we have been discussing about packaging
>>> fd (a find alternative developed using rust [1]). We are planning to
>>> install it in /usr/bin/fd .. but this conflic
Russ Allbery wrote on 09/09/2018:
> Oh, hm, yes, I rather like this idea too, particularly combined with
> putting those symlink packages in their own namespace (and maybe their > own
> section).
Totally makes sense.
> Maybe this is overkill for the relatively small number of these packages
> we
Russ Allbery wrote on 09/09/2018:
> Paride Legovini writes:
>
>> However, there are clearly cases where renaming binaries makes several
>> people unhappy (most likely: the package maintainers, upstream, people
>> writing scripts, users of different distributions), whil
Hello Sean,
Sean Whitton wrote on 08/09/2018:
> Hello Sylvestre,
>
> On Sat 08 Sep 2018 at 08:18PM +0200, Sylvestre Ledru wrote:
>
>> Renaming binaries is a big pain, it is confusing for the user, making the
>> life of the maintainer
>> harder, the documentations won't reflect the Debian-realit
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: sacc
Version : 1.00
Upstream Author : Quentin Rameau
* URL : gopher://bitreich.org/1/scm/sacc
(lynx will do.)
* License : OpenBSD (~ISC)
Programming Lang: C
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: dtl
Version : 1.19
Upstream Author : Tatsuhiko Kubo
* URL : https://github.com/cubicdaiya/dtl
* License : BSD-3-clause
Programming Lang: C++
Description : diff template library
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: fontdiff
Version : 0.2.3
Upstream Author : Sascha Brawer
* URL : https://github.com/googlei18n/fontdiff
* License : Apache-2.0
Programming Lang: C++
Description : tool for
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: golang-github-gdamore-tcell
Version : 1.1.0
Upstream Author : Garrett D'Amore
* URL : https://github.com/gdamore/tcell
* License : Apache-2.0
Programming Lang: Go
Descri
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: golang-github-gdamore-encoding
Version : 0.0~git20151215.b23993c-1
Upstream Author : Garrett D'Amore
* URL : https://github.com/gdamore/encoding
* License : Apache-2.0
Programming
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: golang-github-lucasb-eyer-go-colorful
Version : 1.0-1
Upstream Author : Lucas Beyer
* URL : https://github.com/lucasb-eyer/go-colorful
* License : MIT
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: golang-github-ulule-limiter
Version : 2.2.0-1
Upstream Author : Ulule
* URL : https://github.com/ulule/limiter
* License : MIT
Programming Lang: Go
Description : Dead simple rate
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: golang-github-shibukawa-configdir
Version : 0.0~git20170330.e180dbd-1
Upstream Author : Yoshiki Shibukawa
* URL : https://github.com/shibukawa/configdir
* License : MIT
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: browsh
Version : 1.4.6
Upstream Author : Thomas Buckley-Houston
* URL : https://www.brow.sh/
* License : LGPL-2.1
Programming Lang: Go
Description : Fully interactive, realtime
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: spm
Version : 1.5.0
Upstream Author : Klemens Nanni
* URL : https://notabug.org/kl3/spm
* License : GPL-3+
Programming Lang: sh
Description : simple password manager
spm is a
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: imv
Version : 3.0.0
Upstream Author : Harry Jeffery
* URL : https://github.com/eXeC64
* License : Expat or GPL-2+
Programming Lang: C
Description : A command line image viewer
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: snore
Version : 0.1
Upstream Author : Claudio Alessi
* URL : https://github.com/clamiax/snore/
* License : Expat
Programming Lang: C
Description : sleep with feedback
This tool
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: fscrypt
Version : 0.2.3
Upstream Author : Joe Richey
Copyright : 2017-2018 Google Inc.
* URL : https://github.com/google/fscrypt
* License : Apache-2.0
Programming Lang: Go
On 2018-03-01 18:17, Steffen Nurpmeso wrote:
>
> But last week Paride committed "fixes"[1] after having been
> prodded by some third party, and indeed, now S-nail is
> reproducible on all Debian test boxes. The fix was to set the
> built-in identification for the OS build environment to all
> "De
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: sfnt2woff-zopfli
Version : 1.1.0
Upstream Author : Bram Stein
* URL : https://github.com/bramstein/sfnt2woff-zopfli
* License : Apache and (MPL or GPL or LGPL)
Programming Lang: C
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: quark
Version : soon to be tagged
Upstream Author : Laslo Hunhold
* URL : https://tools.suckless.org/quark/
* License : ISC
Programming Lang: C
Description : An extremely small
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: sac2mseed
Version : 1.12
Upstream Author : Chad Trabant (IRIS Consortium)
* URL : https://ds.iris.edu/ds/nodes/dmc/software/
* License : GPL-3
Programming Lang: C
Description
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: mseed2sac
Version : 2.2
Upstream Author : Chad Trabant (IRIS Consortium)
* URL : https://ds.iris.edu/ds/nodes/dmc/software/
* License : GPL-3
Programming Lang: C
Description
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: vis
Version : 0.2(+git)
Upstream Author : Marc André Tanner
* URL : https://github.com/martanne/vis
* License : ISC
Programming Lang: C
Description : Modern, legacy free, simple
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: fonts-hack
Version : 2.010
Upstream Author : Christopher Simpkins
* URL : https://github.com/chrissimpkins/Hack
* License : Modified SIL Open Font License, Version 1.1
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Paride Legovini
* Package name: PCL (Point Cloud Library)
Version : 1.6
Upstream Author : Open Perception, Inc. (http://www.openperception.org/)
* URL : http://www.pointclouds.org/
* License : BSD-3-clause
Programming
52 matches
Mail list logo
