Package: wnpp
Severity: wishlist
Owner: wnpp
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name : python3-sudoku
Version : 2.0.0-1
* URL : https://github.com/jeffsieu/py-sudoku
* License : Expat
Description : python3-sudoku -- Python package that generates and solves m x n
Sudoku puzzles
On Fri, Aug 15, 2025 at 08:03:14AM +0200, Salvo Tomaselli wrote:
However by default salsa will not send an email when you create a MR,
and I personally (like many others I suspect) never open the salsa
website.
May I ask why? Is that a political thing? Do you open the BTS web site,
or the pack
Hello,
> If I am understanding this email correctly, it sounds to me like you
> are saying that this is a "code dump" because I didn't email you first.
It's different for every maintainer.
However by default salsa will not send an email when you create a MR,
and I personally (like many others I
On Fri, Aug 15, 2025 at 07:20:29AM +0200, Ansgar 🙀 wrote:
On Fri, 2025-08-15 at 00:23 +0200, Antoine Le Gonidec wrote:
Opening an MR without having contacted me *prior to the fact* is the
definition of a code dump. I do not care about code, I can very well
write it myself in the first place.
[.
On 2025-08-14 16:23, Antoine Le Gonidec wrote:
Opening an MR without having contacted me *prior to the fact* is the
definition of a code dump. I do not care about code, I can very well
write it myself in the first place.
What I care about is people, especially people who want to fix or
improve a
Hi,
On Fri, 2025-08-15 at 00:23 +0200, Antoine Le Gonidec wrote:
> Opening an MR without having contacted me *prior to the fact* is the
> definition of a code dump. I do not care about code, I can very well
> write it myself in the first place.
[...]
> If sending an e-mail is too much for them, we
(The last message got signing messed up, sorry)
On 2025-08-14T22:21:56+0200, Salvo Tomaselli :
> Hello,
>
> I do not want merge requests from random people. I want a bugreport
> with an attached patch. How can I signal this to people? (without
> spending an inordinate amount of time in salsa to c
On Thu, Aug 14, 2025 at 10:32:58PM +0100, Wookey wrote:
If these MRs got turned into bugreports automagically that could be
helpful. Listing them on tracker.d.o would also work (eventually).
The suggested tool to just turn the MR feature off (for my packages)
so that the problem doesn't arise sou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2025-08-14T22:21:56+0200, Salvo Tomaselli :
> Hello,
>
> I do not want merge requests from random people. I want a bugreport
> with an attached patch. How can I signal this to people? (without
> spending an inordinate amount of time in salsa to c
Hi,
> > Later a further improvement could be to generate a default configuration
> > from d/upstream/metadata which would probably allow many packages to not
> > need a d/watch anymore.
>
> While I like the idea, isn't d/watch used by Debian tooling to check if
> new versions are available? I woul
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 1169 (new: 0)
Total number of packages offered up for adoption: 129 (new: 1)
Total number of packages reques
On Thu, Aug 14, 2025 at 08:40:18PM +0200, Jonas Smedegaard wrote:
> Quoting Otto Kekäläinen (2025-08-14 19:50:47)
> > I am not shaming. If I were shaming, I would post examples that show
> > who did what.
> You are right, and I apologize: You are only blindly accusing.
and
> > I am merely encour
Package: wnpp
Severity: wishlist
Owner: Arthur Diniz
* Package name: golang-go.yaml-yaml-v2
Version : 2.4.2-1
Upstream Author : The YAML Project
* URL : https://github.com/yaml/go-yaml
* License : Apache-2.0
Programming Lang: Go
Description : YAML Suppo
Package: wnpp
Severity: wishlist
Owner: Arthur Diniz
* Package name: golang-go.yaml-yaml-v3
Version : 3.0.4-1
Upstream Author : The YAML Project
* URL : https://github.com/yaml/go-yaml
* License : Apache-2.0
Programming Lang: Go
Description : YAML Suppo
On Thu, Aug 14, 2025 at 5:23 PM Antoine Le Gonidec wrote:
>
> Le Fri, Aug 15, 2025 at 03:08:20AM +0530, Nilesh Patra a écrit :
> > Opening PRs/MRs are typically how most of the git forges are used for
> > contributions.
>
> I have been using many of these forges for a decade and a half, I even
>
On 14/08/25 13:40, Julien Plissonneau Duquène wrote:
Later a further improvement could be to generate a default configuration
from d/upstream/metadata which would probably allow many packages to not
need a d/watch anymore.
While I like the idea, isn't d/watch used by Debian tooling to check if
Le Fri, Aug 15, 2025 at 03:08:20AM +0530, Nilesh Patra a écrit :
> Opening PRs/MRs are typically how most of the git forges are used for
> contributions.
I have been using many of these forges for a decade and a half, I even
self-hosted a GitLab instance for far too many years, and have been part
On 14/08/25 16:56, Ananthu C V wrote:
I haven't checked it in detail either, but I guess having an "Owner" field
would just suit both Author and Organization.
+1 for Owner, Author and Organization don't apply to one another.
Cheers!
On 2025-08-15 03:08:20 +0530 (+0530), Nilesh Patra wrote:
[...]
Opening PRs/MRs are typically how most of the git forges are used
for contributions.
Having salsa and allowing to open MRs and then saying that you
will accept a patch only if you file a bug report via BTS with
proper tags is som
On Thu, 14 Aug 2025 at 22:58:09 +0200, Michael Biebl wrote:
gir1.2-glib-2.0 provides multiple names, such as
gir1.2-{gobject,gmodule,glibunix,giounix,gio}-2.0
Should packages (Build-)Depend on those virtual packages or just use
gir1.2-glib-2.0?
Ideally use the systematic names, like a GIR ver
On 15/08/25 12:37 am, Antoine Le Gonidec wrote:
> To avoid confusion: I’m perfectly happy with Salsa being used as a way
> to send patches, even as a merge request if it is what the contributor
> would use (I would have been OK with a repo URL + branch name). But the
> patches are only part of a co
On 2025-08-14 10:07 -0700, Otto Kekäläinen wrote:
I have now witnessed several cases where a maintainer blatantly
ignored the MRs their package received. It is demotivating to new
aspiring Debian contributors to put in significant effort to learn the
complexities of Debian packaging and submit a
Hi Simon,
gir1.2-glib-2.0 provides multiple names, such as
gir1.2-{gobject,gmodule,glibunix,giounix,gio}-2.0
Should packages (Build-)Depend on those virtual packages or just use
gir1.2-glib-2.0?
How do I figure out, which gir* packages I need?
Michael
OpenPGP_signature.asc
Description: Op
On Wednesday, August 13, 2025 11:03:40 a.m. Central Daylight Saving Time
Raphael Hertzog wrote:
> To limit the risk of breakage in unstable, and have a wide QA coverage of
> your uploads, consider using debusine.debian.net for your uploads to
> Debian.
This sounds like an awesome service! I tr
Hi Otto,
Quoting Salvo Tomaselli (2025-08-14 22:21:56)
> I do not want merge requests from random people. I want a bugreport with an
> attached patch. How can I signal this to people? (without spending an
> inordinate amount of time in salsa to click around and disable merge requests
> entirely).
Otto Kekäläinen writes:
> For most people it is surely accidental, and sending a reminder to
> check for open MRs like I did today can help.
You didn't send a reminder. You sent a hostile message accusing anyone in
Debian who uploaded a package without looking at MRs first of
intentionally ignor
Hello,
I do not want merge requests from random people. I want a bugreport
with an attached patch. How can I signal this to people? (without
spending an inordinate amount of time in salsa to click around and
disable merge requests entirely).
Best
Il giorno gio 14 ago 2025 alle ore 21:44 Otto Kek
Hi,
> > I have now witnessed several cases where a maintainer blatantly
> > ignored the MRs their package received.
>
> As several of us have been noting for some time now, it is very easy to
> accidentally ignore Salsa MRs because the defaults don't send email to the
> maintainer when an MR is op
Hello Otto,
On Thu 14 Aug 2025 at 11:37am -07, Otto Kekäläinen wrote:
> Hi Yadd, Sean and Bas!
>
> Could you please stop pushing directly on 'main' in
> https://salsa.debian.org/debian/devscripts and instead publish Merge
> Requests?
>
> It would help avoid unnecessary mistakes from getting into
On 8/14/25 8:37 PM, Otto Kekäläinen wrote:
Could you please stop pushing directly on 'main' in
https://salsa.debian.org/debian/devscripts and instead publish Merge
Requests?
You'll need to enforce that with Protected branches.
I've committed the trixie changes directly because that's much fast
On Thu, Aug 14, 2025 at 07:54:39PM +0100, Richard Lewis wrote:
Jonas Smedegaard writes:
Quoting Otto Kekäläinen (2025-08-14 19:07:02)
I have now witnessed several cases where a maintainer blatantly
ignored the MRs their package received. It is demotivating
Sounds like what you really want
On Thu, Aug 14, 2025 at 08:52:16PM +0200, Carsten Schoenert wrote:
Am 14.08.25 um 20:32 schrieb Scott Talbert:
Has anyone thought about adding something like "Your package has XX open
Merge Requests on Salsa" to the "action needed" section on the Package
Tracker? That's something I almost alwa
Disclaimer: I don’t like the overhead of the merge request workflow, but
I’m OK with following it if some contributor really wants to use it.
Le Thu, Aug 14, 2025 at 10:07:02AM -0700, Otto Kekäläinen a écrit :
> It is demotivating to new
> aspiring Debian contributors to put in significant effort
On Thu, 14 Aug 2025, Carsten Schoenert wrote:
Hello Scott,
Am 14.08.25 um 20:32 schrieb Scott Talbert:
Has anyone thought about adding something like "Your package has XX open
Merge Requests on Salsa" to the "action needed" section on the Package
Tracker? That's something I almost always loo
Otto Kekäläinen writes:
> Could you please stop pushing directly on 'main' in
> https://salsa.debian.org/debian/devscripts and instead publish Merge
> Requests?
I really hope debian-devel is not going to turn into an ongoing discussion
of how the workflows of other maintainers are wrong.
For th
Hello Scott,
Am 14.08.25 um 20:32 schrieb Scott Talbert:
Has anyone thought about adding something like "Your package has XX open
Merge Requests on Salsa" to the "action needed" section on the Package
Tracker? That's something I almost always look at before doing a new
upload on a package.
t
Jonas Smedegaard writes:
> Quoting Otto Kekäläinen (2025-08-14 19:07:02)
>> I have now witnessed several cases where a maintainer blatantly
>> ignored the MRs their package received. It is demotivating
>
> Sounds like what you really wanted to say *in good faith* is that it is
> blatantly embarr
Scott Talbert writes:
> Has anyone thought about adding something like "Your package has XX open
> Merge Requests on Salsa" to the "action needed" section on the Package
> Tracker? That's something I almost always look at before doing a new
> upload on a package.
Oh! Yes, that would be incredib
On Thu, 14 Aug 2025, Russ Allbery wrote:
Jonas Smedegaard writes:
Sounds like what you really wanted to say *in good faith* is that it is
blatantly embarrassing that default settings at Salsa make a false
impression towards noecomers that Debian generally acceepts drive-by
patching similar to
Quoting Otto Kekäläinen (2025-08-14 19:50:47)
> Hi,
>
> > > ## Priority: Check MRs for your own packages
> > >
> > > Please remember to check if your package has open MRs *at least once*
> > > before the next upload!
> > >
> > > I have now witnessed several cases where a maintainer blatantly
> > >
Hi Yadd, Sean and Bas!
Could you please stop pushing directly on 'main' in
https://salsa.debian.org/debian/devscripts and instead publish Merge
Requests?
It would help avoid unnecessary mistakes from getting into the
repository and perhaps be more collaborative in spirit.
Yesterday there was 4 c
Hi,
On Thu, Aug 14, 2025 at 10:07:02AM -0700, Otto Kekäläinen wrote:
Please remember to check if your package has open MRs *at least once*
before the next upload!
This is good advice to put into an upload workflow, yes. For people who
have been around in Debian for longer than ten years this
Jonas Smedegaard writes:
> Sounds like what you really wanted to say *in good faith* is that it is
> blatantly embarrassing that default settings at Salsa make a false
> impression towards noecomers that Debian generally acceepts drive-by
> patching similar to Github and Gitlab.
I'm not sure tha
Otto Kekäläinen writes:
> I have now witnessed several cases where a maintainer blatantly
> ignored the MRs their package received.
As several of us have been noting for some time now, it is very easy to
accidentally ignore Salsa MRs because the defaults don't send email to the
maintainer when a
Hi,
> > ## Priority: Check MRs for your own packages
> >
> > Please remember to check if your package has open MRs *at least once*
> > before the next upload!
> >
> > I have now witnessed several cases where a maintainer blatantly
> > ignored the MRs their package received. It is demotivating
>
>
Quoting Otto Kekäläinen (2025-08-14 19:07:02)
> Hi!
>
> I encouraged DDs and DMs to review open Merge Requests on Salsa back in
> January:
> https://lists.debian.org/debian-devel/2025/01/msg00267.html. Hopefully
> folks can continue with doing reviews!
>
>
> ## Priority: Check MRs for your own
Hi!
I encouraged DDs and DMs to review open Merge Requests on Salsa back in January:
https://lists.debian.org/debian-devel/2025/01/msg00267.html. Hopefully
folks can continue with doing reviews!
## Priority: Check MRs for your own packages
Please remember to check if your package has open MRs *
Package: wnpp
Severity: wishlist
Owner: Aryan Karamtoth
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-asyncpraw
Version : 7.8.1
Upstream Author: Joel Payne
* URL : https://github.com/praw-dev/asyncprawcore [1]
* License : BSD-2-Clause
Pro
Package: wnpp
X-Debbugs-Cc: debian-devel@lists.debian.org
Owner: "Ying-Chun Liu (PaulLiu)"
Severity: wishlist
* Package name : python-sphinx-chango
Version : 0.5.0
Upstream Contact: https://github.com/Bibo-Joshi/chango/
* URL : https://chango.readthedocs.io/latest/sphi
Hi,
On Thu, Aug 14, 2025 at 03:10:49PM +0200, Michael Banck wrote:
> Isn't that usually called an organisation in Github? Sure, for personal
> repos, org == author, but not in general. Or are both supported (I did
> not check, sorry).
I haven't checked it in detail either, but I guess having an "
Package: wnpp
Severity: wishlist
Owner: Ananthu C V
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-r...@lists.debian.org
* Package name: rust-presenterm
Version : 0.15.1
Upstream Contact: Matias Fontanini
* URL : https://github.com/mfontanini/presenterm
* License
Hi,
On Thu, Aug 14, 2025 at 10:25:32AM +0200, Xavier wrote:
> uscan with new debian/watch format version 5 is ready (available in
> experimental).
> Of course this version of uscan is still able to read current formats. The
> main changes in version 5 are:
> - rfc822 style (like other debian fil
Hello,
On Thu 14 Aug 2025 at 01:43pm +02, Yadd wrote:
> Hi Sean,
>
> sure you can, thank you! I kept all version=4 tests to verify that there is no
> regression, so I think everything is OK
>
> Best regards,
> Xavier
Cool, thank you for the feedback.
--
Sean Whitton
signature.asc
Description
In trixie, we split up the libgirepository1.0-dev package into several
smaller packages to help to make cross-compiling possible, leaving
libgirepository1.0-dev as a transitional/compatibility package.
Now that the forky release cycle has started, I would like to look into
removing the libgirep
On 8/14/25 13:40, Julien Plissonneau Duquène wrote:
Le 2025-08-14 10:25, Xavier a écrit :
What do you think ?
Thank you for this work! It makes watch files much more readable.
Later a further improvement could be to generate a default configuration
from d/upstream/metadata which would proba
On 8/14/25 12:15, Sean Whitton wrote:
Hello,
On Thu 14 Aug 2025 at 10:25am +02, Xavier wrote:
Hi,
uscan with new debian/watch format version 5 is ready (available in
experimental).
Of course this version of uscan is still able to read current formats. The main
changes in version 5 are:
- rfc8
Le 2025-08-14 10:25, Xavier a écrit :
What do you think ?
Thank you for this work! It makes watch files much more readable.
Later a further improvement could be to generate a default configuration
from d/upstream/metadata which would probably allow many packages to not
need a d/watch anymor
This re-run became a bit boring so I went looking for relevant docs
instead. Which was far more entertaining.
Maybe time to do something about
https://www.debian.org/ports/i386/
https://www.debian.org/ports/
https://wiki.debian.org/SupportedArchitectures
etc?
A spider looking for dead links wo
Hello,
On Thu 14 Aug 2025 at 10:25am +02, Xavier wrote:
> Hi,
>
> uscan with new debian/watch format version 5 is ready (available in
> experimental).
> Of course this version of uscan is still able to read current formats. The
> main
> changes in version 5 are:
> - rfc822 style (like other debi
On Wed, 13 Aug 2025 22:10:26 +0100, Wookey
wrote:
>> plus giving people with tight budgets a shot at decent, up-to-date software.
>
>There is loads of old 64-bit hardware that can be had at freecycle prices to
>replace the power-hungry i386 kit you are still running.
Since one of the major compe
Hi,
uscan with new debian/watch format version 5 is ready (available in
experimental).
Of course this version of uscan is still able to read current formats. The main
changes in version 5 are:
- rfc822 style (like other debian files)
- "templates" that permit to calculate automatically sources.
Package: wnpp
Severity: wishlist
Owner: wnpp
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name : ascii-draw
Version : 1.1.0-1
* URL : https://github.com/Nokse22/ascii-draw/
* License : GPL-3+
Description : ascii-draw -- Create beautiful diagrams and artwork using only
ASCII characters
62 matches
Mail list logo
