ation (or misuse) with now two
fields with slightly tighter definitions and some significant overlap.
In short this is a case of "now you have two problems".
--
Julien Plissonneau Duquène
Package: wnpp
Severity: wishlist
Owner: Julien Plissonneau Duquène
X-Debbugs-Cc: debian-devel@lists.debian.org, sre4e...@free.fr
* Package name: libgradle-fileevents-java
Version : 0.2.5
* URL : https://github.com/gradle/gradle-fileevents
* License : Apache-2.0
Package: wnpp
Severity: wishlist
Owner: Julien Plissonneau Duquène
X-Debbugs-Cc: debian-devel@lists.debian.org, sre4e...@free.fr
* Package name: libfastdoubleparser-java
Version : 2.0.1
Upstream Contact: Werner Randelshofer
* URL : https://github.com/wrandelshofer
On 14/11/2024 10:14, Niels Thykier wrote:
Surely, the short form of DEP--1 would be DEP+1 since
-(-1) is +1. This would also ensure maximum confusion.
Nay. DEP~1
To add some real value to this thread. I am fine with the DEP-X variant.
+1
Cheers,
--
Julien Plissonneau Duquène
-unsafe-io to the command
line.
Cheers,
--
Julien Plissonneau Duquène
al.
[2]: https://lists.debian.org/debian-devel/2024/12/msg00597.html
[3]:
https://sources.debian.org/src/dpkg/1.22.11/src/main/archives.c/#L1159
--
Julien Plissonneau Duquène
lp to alleviate some scaling issues like API rate limits on some
platforms, and make it easier for would-be contributors to maintain a
public fork for the platforms that make it complicated or impossible or
have unreasonable ToS.
Cheers,
--
Julien Plissonneau Duquène
://salsa.debian.org/kernel-team/linux/-/branches/active
--
Julien Plissonneau Duquène
own personal preferences, but if they are reasonable
that should not be much of an issue, and if that happens often enough
you may want to publicly document them somewhere to avoid repeating
yourself.
Cheers,
--
Julien Plissonneau Duquène
branch.
Branches named after version numbers also happen quite often upstream.
--
Julien Plissonneau Duquène
-by-case
basis for non-free packages or packages that have +dfsg repacking.
Cheers,
--
Julien Plissonneau Duquène
;not fully written" packages in
these cases, short of verifying all installed files of all
(re)installed/down/upgraded packages of recent runs of dpkg (which could
be a feature worth having on a recovery bootable image).
Cheers,
--
Julien Plissonneau Duquène
:
https://learn.microsoft.com/en-us/windows/win32/fileio/deprecation-of-txf
[2]: https://lwn.net/Articles/351422/
https://lwn.net/Articles/322823/
https://lwn.net/Articles/1001770/
--
Julien Plissonneau Duquène
h the system is vulnerable to a power loss) they
do not resolve the issue.
Cheers,
--
Julien Plissonneau Duquène
4/SSD with and without --force-unsafe-io to sort that out ;)
Cheers,
--
Julien Plissonneau Duquène
Hi,
Le 2024-12-24 10:54, Michael Tokarev a écrit :
How about turning this option - force-unsafe-io - to on by default
in 2025? That would be a great present for 2025 New Year! :)
That sounds like a sensible idea to me.
Cheers, and best wishes,
--
Julien Plissonneau Duquène
vironments.
In addition, providing an option to limit the computed result to the
number of available actual cpu cores (not vcpus/threads) and another one
to place an arbitrary upper limit of process beyond which no gains are
expected would be nice.
Cheers,
--
Julien Plissonneau Duquène
policy for this though, and if we do,
maybe a few additional words in the code of conduct could be enough.
Cheers,
--
Julien Plissonneau Duquène
Good morning,
Le 2025-01-07 09:41, Julien Plissonneau Duquène a écrit :
The MR above has additional links and descriptions of current
practices. I do not have a strong preference for a choice yet so
feedback would be appreciated.
I've updated the merge request at [1] to replace the in
7;m
planning to work on that later this year.
Cheers,
[1]: https://salsa.debian.org/gnome-team/gnome-2048
--
Julien Plissonneau Duquène
x27;m happy that someone is already working on
it, and might contribute to sort out issues later.
Cheers,
--
Julien Plissonneau Duquène
ing" issues in the future with
automated (AI) contributions in the future though
BTW I'm not sure that the Debian Machine Usage Policy covers online
services such as Salsa in its current form. This might be worth fixing,
and advertising on the services.
Cheers,
--
Julien Plissonneau Duquène
hey feature captchas.
Also, I'm not sure that some issues can really be cleared; see below.
Here I'm not sure the perceived issues are that much of an issue. We
would have no Internet today if network and system operators tried to
reach that level of safety back in the eighties and nineties.
Cheers,
--
Julien Plissonneau Duquène
r issues though.
In the case of pam above, I believe that patching it in a way that sets
an arbitrary high limit when there is none and documenting this as a
limitation could be appropriate.
Cheers,
--
Julien Plissonneau Duquène
Hi,
Le 2025-01-17 14:50, Chris Hofstaedtler a écrit :
* Julien Plissonneau Duquène [250116 19:09]:
Is there any existing "bootstrap essential" package that wasn't yet
approached by Helmut and that could be interested in hosting that new
tool?
Please just put it into a new p
Le 2025-01-22 18:37, Julien Plissonneau Duquène a écrit :
We need a name:
- E-...: other: .
And because Why Not, here is the contribution of a well-known LLM
service to the list of choices:
Sure! Here are some short and catchy names for your program:
ProcCalc
MemPro
CoreCount
s-link issues with the
BTS etc.
Would that make sense?
Cheers,
--
Julien Plissonneau Duquène
Le 2025-01-24 09:49, Gioele Barabucci a écrit :
On 24/01/25 09:00, Julien Plissonneau Duquène wrote:
Also note that the contents that really matter is the git
repositories
themselves.
I do not agree with this premise.
The Git repo is forever and `git log` is how you search its history
o.
Or maybe `debian/main` to keep up with the popular trend, and as `main`
is a better choice anyways, regardless of some popular controversial
arguments.
--
Julien Plissonneau Duquène
the Salsa admins to have
already realized that this history is just as important as the BTS
history, ML archives and other archives.
Cheers,
--
Julien Plissonneau Duquène
deprecation is still controversial
(e.g. should we deprecate "server" and "service" as well?).
Cheers,
--
Julien Plissonneau Duquène
--
Julien Plissonneau Duquène
well.
Cheers,
--
Julien Plissonneau Duquène
Le 2025-01-25 10:37, Phil Morrell a écrit :
On 25 January 2025 08:07:04 GMT, "Julien Plissonneau Duquène"
wrote:
That's one thing, but going one step further, NOT pushing upstream
branches to the packaging repositories may help here as well.
I'm going to have to disagree
uests with their entire
discussion histories to other repositories). From experience, when this
happens most maintainers are not going to care anyway and will just mass
close issues and MRs.
Cheers,
--
Julien Plissonneau Duquène
`devscripts`. Some are already partially done. Would
this get more support? This would not have as much potential for working
around some GitLab limitations though.
Cheers,
--
Julien Plissonneau Duquène
Le 2025-01-25 19:22, Julien Plissonneau Duquène a écrit :
Wayback Machine
FTR this project [1], according to this interview [2] (transcript [3]
search for "discussions") now aims to also archive the discussions
happening on merge requests and issues. So there is some hope for
fu
also provide
details about the underlying filesystem and storage stack, and the
effective mount options (cat /proc/fs/.../options)?
Cheers,
--
Julien Plissonneau Duquène
Le 2025-01-14 02:58, Ángel a écrit :
reading /proc/fs/ext4/*/options:
Thank you.
It appears that these options lack auto_da_alloc, which may (still
hypothetical at this point) explain the much better performance of
--force-unsafe-io in your case.
Cheers,
--
Julien Plissonneau Duquène
s,
[1]: https://salsa.debian.org/jpd/parallimit
--
Julien Plissonneau Duquène
Package: wnpp
Severity: wishlist
Owner: Julien Plissonneau Duquène
X-Debbugs-Cc: debian-devel@lists.debian.org, sre4e...@free.fr
* Package name: jackson-dataformats-binary
Version : 2.18.2
Upstream Contact: FasterXML, LLC, Seattle, USA
* URL : https://github.com
Package: wnpp
Severity: wishlist
Owner: Julien Plissonneau Duquène
X-Debbugs-Cc: debian-devel@lists.debian.org, sre4e...@free.fr
* Package name: jackson-dataformats-text
Version : 2.18.2
Upstream Contact: FasterXML, LLC, Seattle, USA
* URL : https://github.com
opriate
IMO. I would suggest 2 years with no activity on the MR before closing
for "staleness", but ideally some data points should be extracted from
Salsa before discussing this.
Cheers,
--
Julien Plissonneau Duquène
es and build scripts.
Cheers,
--
Julien Plissonneau Duquène
sting "bootstrap essential" package that
wasn't yet approached by Helmut and that could be interested in hosting
that new tool?
Cheers,
--
Julien Plissonneau Duquène
binary packages.
Best regards,
--
Julien Plissonneau Duquène
year with some housekeeping tasks.
Identifying merge requests that are clearly outdated and posting a
comment with a short explanation (e.g. "Obsolete MR: already fixed in
current package version") will also help in getting the count down.
Cheers,
--
Julien Plissonneau Duquène
the build a
lot less brittle, and that should be submitted upstream.
Cheers,
[1]: https://services.gradle.org/distributions/
[2]: https://github.com/gradle/gradle/tags
[3]:
https://salsa.debian.org/jpd/gradle/-/blob/287ae5c99790f266e242964321955f7c77f397df/debian/wip/delta-ghtar-gradlezip
--
Julien Plissonneau Duquène
Package: wnpp
Severity: wishlist
Owner: Julien Plissonneau Duquène
X-Debbugs-Cc: debian-devel@lists.debian.org, sre4e...@free.fr
Package name: kotlinx-serialization
Version : 1.8.0
Upstream Contact: Leonid Startsev
URL : https://github.com/Kotlin
anslation), even though they
missed the initial steps?
Cheers,
[1]: https://www.debian.org/international/french/
[2]: https://www.debian.org/international/french/po
--
Julien Plissonneau Duquène
when it comes to fixing things in this version of
the package (less steps and thus less risks that a later release of some
build tool behaves differently and breaks things).
Cheers,
--
Julien Plissonneau Duquène
nlikely to ever end up packaged.
Cheers,
[1]: https://tracker.debian.org/pkg/guess-concurrency
--
Julien Plissonneau Duquène
ation if we don't want to make this mandatory for all
packages the sponsored packages could be processed in priority by the
ftp masters.
Cheers,
--
Julien Plissonneau Duquène
version is reasonably small, and tools that can remember and
identify which parts of the upstream project were already reviewed and
when for the last time and eventually annotate them. But I'm not sure
there is much to gain here overall.
Cheers,
--
Julien Plissonneau Duquène
etf.org/arch/msg/ietf-822/7AZtGBeahWk_eHpJk9NS6kG-PrU/
[4]:
https://mailarchive.ietf.org/arch/msg/ietf-822/tFodnoYUlXNMmLB40bIjhoMQpnY/
--
Julien Plissonneau Duquène
s there an archive or a log somewhere that could be used to
estimate the rejection frequency and most common causes?
Cheers,
--
Julien Plissonneau Duquène
at all in some e.g. in
Roundcube 1.6.10 that my service provider is using. An old version of
Thunderbird displays it at text/plain.
Cheers,
--
Julien Plissonneau Duquène
reason to use quilt and patch
queues in this case (that would only further complicate things).
Cheers,
--
Julien Plissonneau Duquène
m stable.
That's a start, I guess. Maybe in these cases you can keep the .po file
as submitted for proposed updates, merge it in unstable and nicely ask
the translator to also please work on the upcoming version.
Cheers,
--
Julien Plissonneau Duquène
;s probably the way to go here. I would also suggest modifying
dune-release so the git release tags end up with the substitutions
already applied, to make it possible to simply export them and build
them outside of a git tree.
Cheers,
--
Julien Plissonneau Duquène
mented) is used to adjust a hardcoded
version number in some file somewhere at release time. But it's true
that if you're stranded somewhere you may have some free time at hand to
implement your own layer of templating ^ ^.
Cheers,
--
Julien Plissonneau Duquène
s://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/581
[11]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092800
[12]: https://salsa.debian.org/agx/git-buildpackage/-/merge_requests/38
[42]: https://archive.org/details/msdos_Bureaucracy_1987
--
Julien Plissonneau Duquène
tually happening and with [1]:
Note that enabling gitattributes will make the tree incompatible with
tag2upload.
Cheers,
[1]:
https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/581#note_587974
--
Julien Plissonneau Duquène
TH and lacks a way to pass a different launcher
path. I'm also planning to fix that later.
Thank you for reporting this.
Cheers,
--
Julien Plissonneau Duquène
the declared maintainer of the package. Such
defaults could still be overriden by gbp.conf the same way as current
gbp built-in defaults can be.
Cheers,
--
Julien Plissonneau Duquène
uot; while avoiding the exact name "upstream" could be enough?
Cheers,
--
Julien Plissonneau Duquène
ther terms what's in this field is primarily there to help
checking licensing compliance. In my view it's not meant to be kept
up-to-date unless there are changes that are relevant for evaluating
current licensing compliance.
Cheers,
--
Julien Plissonneau Duquène
ge, which seems workable.
Is there any way I could get a copy of a log file (current ones with 1%
sampling) for experimenting?
Cheers,
--
Julien Plissonneau Duquène
oc/packaging-manuals/copyright-format/1.0/#source-field
--
Julien Plissonneau Duquène
Le 2025-05-27 20:30, Ahmad Khalifa a écrit :
On 27/05/2025 17:46, Julien Plissonneau Duquène wrote:
0. keep all the e-mail features it currently offers
IMHO, this is a security flaw, not a feature. I hear that everyone
loves it, so at least the emails should be authenticated somehow
ld be modified to also process merge requests and add a
"patch" tag automatically?
Cheers,
--
Julien Plissonneau Duquène
On 28/05/2025 00:25, tho...@goirand.fr wrote:
Please do contribute this upstream, so we get it on our next upgrade !
Yes, that's also a possibility.
Cheers,
--
Julien Plissonneau Duquène
grating away from JIRA to GitHub
issues, but they also have a fairly different usage pattern than Debian.
For Debian maybe something like Redmine could work (I'm not suggesting a
change, but looking at alternatives may give some ideas).
Cheers,
--
Julien Plissonneau Duquène
n't too convenient to work with and lacks some features.
Anything else you know that could be improved?
Cheers,
--
Julien Plissonneau Duquène
UI, but I don't know if it's possible.
--
Julien Plissonneau Duquène
ould eventually be
tried later on a self-approval web UI, but that would indeed require
close collaboration and supervision by Salsa admins so they can pull the
plug at any time once abusers find their way through.
Cheers,
--
Julien Plissonneau Duquène
But the "Reply-To: " field of the bot message could certainly be
populated with the names and addresse(s) of the author and/or committer
(and NNN@b.d.o). Would that work for your case?
Cheers,
--
Julien Plissonneau Duquène
successors ... and SQL is not that great at recursivity
or working with graphs. Or handling large binary objects. Or doing
finely tunable full-text indexing and search. That's an implementation
detail anyway (well, maybe not right now, but that's how it should be
ideally).
Cheers,
-
there are backups, and incoming legitimate messages could be
replayed should such abuse occur, right?
--
Julien Plissonneau Duquène
gitlab/github feature.
--
Julien Plissonneau Duquène
is currently "understaffed".
Cheers,
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910917
--
Julien Plissonneau Duquène
contributor) time
frame.
Cheers,
--
Julien Plissonneau Duquène
trying to
package the project. They can also be referenced in blocks:
relationships with other RFPs or bugs (e.g. request to update a
package).
A review process with enough votes to keep or close stale RFPs could be
interesting, but they should not be closed arbitrarily.
--
Julien Plissonneau Duquène
83 matches
Mail list logo
