[not sending to the ITP bug, since it is off-topic for that]
On 2025-03-22 15:50, Samuel Henrique wrote:
Given the current status of the maintenance on rsync upstream, it's
going to be handy to have an alternative packaged in the repository just
in case.
Could you elaborate on the state of rsy
Hi!
> >But the core of my question here was about the apparent conflict of
> >signing up for LowThresholdNmu as an indication that you are open for
> >collaboration, yet not having the package in VCS, which would make the
> >collaboration easier. I am trying to understand why certain people
> >obj
At 2025-03-22T16:15:23-0700, Otto Kekäläinen wrote:
> Just out of curiosity, what email client and plugins do you use to
> achieve your optimal email-based workflow?
I don't see where Wookey made a claim that his workflow was "optimal",
merely that it was effective for him personally. Debian Deve
Quoting Otto Kekäläinen (2025-03-21 23:14:14)
> Even when doing a NMU you should communicate your intent ahead. For
> example https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu
> recommends specifically submitting your nmudiff to the bug report and
> waiting before proceeding to
Guillem Jover wrote...
> I'm happy to try to address anything that seems unclear, or get
> someone else who might be able to answer! And as Holger suggested
> elsewhere, we can probably also create a FAQ on the wiki with some of
> this to point to people.
Thanks for your explanations, things are
Hello Marc,
Am Wed, Mar 19, 2025 at 09:44:47AM +0100 schrieb Marc Haber:
> tl;dr: New Wiki Page https://wiki.debian.org/I18n/ForPackageMaintainers,
> please review
I just did it. I usually updated it right away, but at one or two
points it is more like a discussion. And due to my changes some
redu
On 2025-03-21 15:14 -0700, Otto Kekäläinen wrote:
But the core of my question here was about the apparent conflict of
signing up for LowThresholdNmu as an indication that you are open for
collaboration, yet not having the package in VCS, which would make the
collaboration easier. I am trying to u
On Saturday, March 22, 2025 1:09:29 PM Mountain Standard Time
Christopher Obbard wrote:
> Hi!
>
> For the package fluster, upstream at
> http://github.com/fluendo/fluster/, we have a slight mistake with
> the upstream versioning and I would like to add an epoch
>
> The current version in debian
Package: wnpp
Severity: wishlist
Owner: Daniel Gröber
X-Debbugs-Cc: debian-devel@lists.debian.org, d...@darkboxed.org
* Package name: golang-agwa-go-listener
Version : 0.6.1
Upstream Contact: Andrew Ayer
* URL : https://github.com/AGWA/go-listener
* License :
On Sat, Mar 22, 2025 at 08:24:34AM +0100, Jonas Smedegaard wrote:
> Some of us (me included) prefer Salsa over Github or Sourcehut or other
> forges, but what we use is its git hosting service without its optional
> web-centric services (regardless if accessed via a web browser or a web
> CLI tool)
> > Just out of curiosity, what email client and plugins do you use to
> > achieve your optimal email-based workflow?
>
> I don't see where Wookey made a claim that his workflow was "optimal",
> merely that it was effective for him personally. Debian Developers are
> a diverse bunch and approach p
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
On 2025-03-22 16:15 -0700, Otto Kekäläinen wrote:
Thanks for the explanation Wookey on why you prefer to not use VCS for
Debian packaging, and why others using VCS, and thus in Debian Salsa,
creates extra work for you.
Just out of curiosity, what email client and plugins do you use to
achieve
Package: wnpp
Severity: wishlist
Owner: Samuel Henrique
X-Debbugs-CC: debian-devel@lists.debian.org, debian...@lists.debian.org
* Package name: rsync
Version : 0.2.6-1
Upstream Author : Michael Stapelberg
* URL : https://github.com/gokrazy/rsync
* License : BS
14 matches
Mail list logo