Hi!
On Wed, 27 Sept 2023 at 13:27, Lucas Nussbaum wrote:
>
> Hi,
>
> #1042428 is the bug for "no explanation for lintian tags on UDD"
>
> On 26/09/23 at 21:35 -0700, Otto Kekäläinen wrote:
> > I know Lintian tag info is available via command line, but I
> &
> > This issue still exists. I would now have the need to send the url
> > https://lintian.debian.org/tags/service-file-is-not-a-file to upstream
> > developers to learn about this Lintian issue, but the URL does not
> > serve any contents nor does it redirect to a new location.
> >
> > I am still
> >> I finally fixed this. Sorry for the delay.
> >>
> >> https://udd.debian.org/lintian?packages=entr has a link for each lintian
> >> tag, that points to (e.g.)
> >> https://udd.debian.org/lintian-tag.cgi?tag=superfluous-file-pattern
> >> That page includes a description of the tag as well as al
tents as-is without doing a source build first?
I am exploring this in order to get my text editor to nag about findings
immediately without separate source build steps.
Otto
[1] https://manpages.debian.org/bookworm/lintian/lintian.1.en.html
> Paul already answered the lintian part, so I will skip that. But I also
> wanted to suggest looking into integrated spell-checking in your editor
> if possible. Having integrated spell-check will enable a much faster
> feedback loop.
Thanks the reply, but basic spell checking is pretty much alre
Hi Abou!
I can't help with the issue at hand, but as general advice for the
future: if you had Salsa-CI enabled at
https://salsa.debian.org/pascal-team/fpc/-/pipelines the build-all and
build-any jobs would have probably caught this before upload.
Just open https://salsa.debian.org/pascal-team/fp
Hi!
I've noticed that the most recent LLMs are actually very good at
finding information, summarizing and giving code examples about Debian
already without extra training. One just needs to double check that
the answer was correct to not fall for when they are simply making up
plausible sounding s
yntax issues which a static
analyzer / linter could easily pick up so I was wondering if it could
be automated. For example in one case[5] exporting
DPKG_GENSYMBOLS_CHECK_LEVEL did not take effect due to easily
detectable incorrect (but not fatal) syntax.
- Otto
[1]
https://salsa.debian.org/mariadb
Package: wnpp
Severity: wishlist
Owner: Otto Kekäläinen
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: pulsar-edit
Version : 1.112.1
Upstream Contact: ad...@pulsar-edit.dev
* URL : https://pulsar-edit.dev/
* License : MIT
Programming Lang
ork is so laboursome. One small
thing that could ease the burden could be better editor integrations
that help people write and maintain the debian/* files with less
effort.
- Otto
[1]
https://www.debian.org/doc/manuals/developers-reference/developers-reference.en.html
[2] https://optimizedbyotto.
Hi!
Thanks for the tip, Niels!
It would be cool if dh_assistant had some kind of generic command like
"dh_assistant validate" which would attempt to introspect all
information silently and emit output only if it fails to parse
something. Additionally it could emit a non-zero exit code on errors.
> I looked into better tooling/editor support in general for Debian
> languages in general. I think the industry answer is that "someone"
> ought to build a "language (LSP) server" for the Debian languages, which
> would enable editors with LSP support[1] to get the same basic features.
True - LSP
Hi!
> Thats beginning to look like the history of check-all-the-things.
Yeah, I remember looking into cats some years back as a place to learn
what commands exist. Similarly I also occasionally browse
https://pre-commit.com/hooks.html.
The challenge with having all possible checkers is that they
sources inside a throwaway container.. ;)
https://salsa.debian.org/otto/debcraft
> Re: Steve Langasek
> > Christoph Berg
> >postgresql-16 (U)
>
> Please do not upload postgresql-16 before I ack the diff.
>
> I'll also note that *ALL* nmu diffs I've seen so far are using the
> wrong version number in debian/changelog, missing the "~exp1" upload
> from the actual upload. I'v
> $ grep mariadb results/*
> results/results_dumped.txt:libmariadb-dev
> results/results_failed.txt:libmariadbd-dev
> results/results_none.txt:libmariadb-dev
> $
>
> There was nothing unintentional here. libmariadb-dev is clean wrt time_t.
> libmariadbd-dev failed to be analyzed because it has hea
Thanks Steve for uploading a fixed curl on Saturday. Just checking did you
notice amel/armhf are still not building due to secondary issues and n
dependencies?
https://buildd.debian.org/status/package.php?p=curl
Hi Benjamin!
You recently uploaded openssl 3.1.5-1.1.
Are you tracking the effect it had on reverse dependencies?
Do you have plans to do any follow-up uploads or +b1 rebuilds of other packages?
For example curl is unable to satisfy build dependencies on
armhf/armel at the moment:
https://build
Hi!
Is anyone perhaps planning to fix cargo?
For example curl isn't building on armel/armhf now and numerous packages
that depend of curl are not building on armel/armhf.
Thanks in advance to the person who steps up.
Hi!
pe 15. maalisk. 2024 klo 6.56 Fabian Grünbichler
kirjoitti:
> On Thu, Mar 14, 2024 at 10:03:57PM -0700, Otto Kekäläinen wrote:
> > Hi!
> >
> > Is anyone perhaps planning to fix cargo?
> >
> > For example curl isn't building on armel/armhf now and num
opers, perhaps via a new review tool.
- Otto
[1] https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/342
(missing git tags after upload)
[2] https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/343
(misconfigured upstream git branches)
27;ll just stop contributing.
I am doing all my builds inside a (Podman) container with the sources
loop-mounted. Thus I can use git and visual code editor directly on
sources with full access, but when the build runs, it is fully inside
a container that has no host access nor even network access. To
achieve this I wrote a tool which you might want to check out:
https://salsa.debian.org/otto/debcraft
dependencies and build the
> package ?
Can you give me an example of a package you want to build and what is
the starting point, and I can tell you what command to issue to
https://salsa.debian.org/otto/debcraft to achieve it?
It supports running Podman in user mode (=no root permissions n
Hi!
ti 7. toukok. 2024 klo 23.01 Charles Plessy kirjoitti:
> Le Tue, May 07, 2024 at 08:17:31PM -0700, Otto Kekäläinen a écrit :
> >
> > Can you give me an example of a package you want to build and what is
> > the starting point, and I can tell you what command
an archive from needless
widespread failures.
Thanks,
Otto
ou try it out, and still think Salsa is bad for Debian, then I am
more willing to accept your stanze.
- Otto
Thanks for reply Jonas,
> > You could go to
> > https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/19 and
> > conduct a code review?
> >
> > You might discover that GitLab is useful and is not duplicating
> > Debbugs or anything else in Debian - it is currently the only platform
> > to
On Sat, 23 Mar 2024 at 01:32, Ansgar 🙀 wrote:
>
> Hi,
>
> Debian 10 "buster" has moved to archive.debian.org in order to free
> space on the main mirror network. We plan to start removing files for
> non-LTS architectures in about two weeks; the existing Release files
> will then refer to no long
> > Ideally debbugs should be made non-native so that some else could
> > maintain the Debian package.
>
> I'm happy to review patches that get the 2.6 branch of debbugs in shape
> where it can be released into Debian again if someone wants to take that
> effort. I've just assumed that anyone using
Hi!
> > If I am successful, then lintian can specialize its efforts into issues only
> > visible in packaged artifacts and thereby reduce it scope a bit.
>
> Perfect. I'd love to have some policy checking at "the right point in
> time". I'd love to support this but as far as I understand even yo
s not see value in granting more people commit
permissions. If we learn how these maintainers think, perhaps we can
come up with a model to facilitate having more co-maintenance that can
apply to the exact cases where co-maintenance is missing.
- Otto
Hi!
On Sun, 19 May 2024 at 20:48, Don Armstrong wrote:
>
> On Sun, 19 May 2024, Bill Allombert wrote:
> > Also debbugs is a special case:
> > The debbugs Debian package (as opposed to the debbugs software) have never
> > been
> > really maintained. I am actually one of the very few users of this
Hi!
So just to clarify, are you saying that a copy of
https://security.debian.org/debian-security/dists/buster/ will never
be archived at https://archive.debian.org/debian-security/dists/ like
previous releases have been so far?
This is not about getting *new security updates*, but purely a
quest
Plus one to this initiative!
I also wanted to share the tip to use libfaketime as the easiest way
to test if a build or test suite works on an arbitrary future date. I
am currently testing that the MariaDB upstream test suite passes in
2037 and 2028 using libfaketime like this:
https://salsa.debia
adb-10.5
commits : 197
authors :
187 Otto Kekäläinen 94.9%
2 Christian Göttsche 1.0%
2 Helmut Grohne 1.0%
1 Aurelien Jarno 0.5%
1 Bastian Germann 0.5%
1 Christian Ehrhardt 0.5%
1 Daniel Black0.5%
1 Faustin Lammler 0.5%
to 26. marrask. 2020 klo 18.45 Thomas Goirand kirjoitti:
> Hi Otto,
>
> On 11/26/20 4:44 PM, Otto Kekäläinen wrote:
> > Hello!
> >
> > MariaDB 10.5 release 1:10.5.8-3 finally entered Debian testing
> > today[1]. It has been in unstable since early September, and
> So, if I understand well, if I have 3 MariaDB Buster nodes in a cluster,
> I just need to dist-upgrade them to Bullseye, and it will automagically
> just work and upgrade to Galera 4? If so, that's just great, because
> during our last discussion in Brazil, you told me about something a way
> mor
particular interested in generic from the point of view that
they would work well in different shells and terminal connections, and
support a wide array of log file formats or program outputs, and thus
would best serve an average Linux distro user.
- Otto
[1] https://tracker.debian.org/pkg/ccze
[2
On Fri, 8 Jan 2021 at 04:01, Seth Arnold wrote:
>
> On Thu, Jan 07, 2021 at 11:02:24PM +0200, Otto Kekäläinen wrote:
> > Do you have any tips about generic command-line coloring programs?
>
> The bat package provides a batcat program that'll add colour to a lot of
&
anually and repackaging them with 'ar' is not an
option that would make life easier).
Thanks for any tips you have on the topic!
- Otto
Thanks David, using --with-sources is exactly what I needed.
As a starting point I have the *.deb I've built. In the same directory
I create a Packages file with:
apt-ftparchive packages . > ./Packages
Then I install using it:
apt install --with-source ./Packages -s mariadb-server mariadb-client
Hello!
In MariaDB we have over the years moved files around. A file that was first
in e.g. mariadb-server-10.3 might have been moved to
mariadb-server-core-10.3 and some years later to mariadb-client-core-10.5.
The result is a massive debian/control file with a lot of
Conflicts/Breaks/Replaces [1]
Hell!
On Sun, Apr 4, 2021 at 4:54 AM Andreas Metzler wrote:
>
> On 2021-04-03 Otto Kekäläinen wrote:
> > Hello!
>
> > In MariaDB we have over the years moved files around. A file that was first
> > in e.g. mariadb-server-10.3 might have been moved to
> > mariad
Hello!
> For me, this whole situation seems wrong though. Why do you have
> versioned package names (mariadb-server-*) when they are all mutually
> exclusive with one another due to all shipping the same binary?
This is how the MySQL packaging has been structured for the past 10
years or so. Ther
g new interesting features and you could have
your say in them.
If you are at all keen to do FOSS and MariaDB full-time, or if you
have friends who might be interested, please check out
https://mariadb.org/debian-ubuntu-packaging-expert/ or reach out to
dan...@mariadb.org for more info.
- Otto
PS.
Hello!
I noticed that Lintian has recently started erroring on
https://lintian.debian.org/tags/systemd-service-in-odd-location
I can't find this requirement anywhere in the Debian Policy, e.g.
https://www.debian.org/doc/debian-policy/ch-opersys.html#starting-system-services
does not mention anyth
ebug_info
(or https://paste.debian.net/1220493/ with no line breaks)
Any suggestions how to debug this locally so I can validate if various
changes in debian/rules fixes it or not?
- Otto
On Sat, Nov 27, 2021 at 5:30 AM Simon McVittie wrote:
>
> On Fri, 26 Nov 2021 at 22:10:45 -0800, Otto Kekäläinen wrote:
> > Lintian in Debian unstable has a new test that my package is failing on:
> > https://lintian.debian.org/tags/no-code-sections
>
> As with any Lintia
anually trying to manage TMPDIR env variable in various
places, we should have a standardized way to run maintainer scripts in
clean shell sessions that have all env variables set automatically
correctly.
More proposals on how to handle this are welcome at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests
:)
- Otto
=noautodbgsym` be opt-in
> or enabled by default?
The proposal to make it opt-in makes sense to me.
- Otto
Hi!
Lintian just started erroring on 'depends-on-obsolete-package
lsb-base' on many of my packages yesterday. There are no new uploads
of lsb-base recently and I did not find any news about this topic. The
Lintian page https://lintian.debian.org/tags/depends-on-obsolete-package
is only about the e
Hi!
On Wed, 18 Jan 2023 at 09:00, Andreas Metzler wrote:
>
> On 2023-01-18 Otto Kekäläinen wrote:
> > Lintian just started erroring on 'depends-on-obsolete-package
> > lsb-base' on many of my packages yesterday. There are no new uploads
> [...]
> >
ved:
$ lintian-brush --version
lintian-brush 0.145
$ lintian-brush --allow-reformatting --uncertain --yolo --modern
$ git show
commit a0a2bf5d6972348114b6d6d489619353c539bd74 (HEAD -> dev-otto)
Add missing dependency on lsb-base.
Changes-By: lintian-brush
Fixes: lintian: init.d-script-
e NEWS for 10.11 requires no coding skills:
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/37
- Otto
Hi!
On Thu, 23 Feb 2023 at 08:22, Otto Kekäläinen wrote:
>
> Hello!
>
> (Stop reading if you don't use MariaDB)
>
> I am currently preparing the upload of MariaDB 10.11.2-2 to Debian
> unstable and aim for the highest possible quality. I am currently
> doing the bulk
https://tracker.debian.org/pkg/mariadb and post MRs to fix whatever
you found and want to fix yourself.
4. Review and triage/close open bug reports at
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=mariadb&src=mariadb-10.6&src=mariadb-10.5&src=mariadb-10.3&src=mariadb-10.1
- Otto
Hello!
It seems devscripts cannot be installed in Sid at the moment. I was
not able to find a bug report about this on bugs.debian.org and I
cannot follow up the dependencies on what package actually is stopping
it.
Anybody else experiencing this as well?
$ docker run -it debian:sid bash
root@
Hello!
I've seen many times before statements like these so I'd like to raise
some discussion around the topic:
pe 13. syysk. 2019 klo 16.36 Bastian Blank (wa...@debian.org) kirjoitti:
> On Sun, Sep 08, 2019 at 05:35:10PM -0400, Sam Hartman wrote:
> > The Salsa CA pipeline is recommended.
>
> For
bug tracker at salsa/support..
Thanks again for everybody maintaining and developing Salsa, the CI
and all that comes with them. That has been a huge boost in my
motivation to continue Debian work and makes me much more productive
than ever before.
- Otto
ndle the debian/changelog file and a
couple of other details. I would be very keen to learn from others
before inventing too much of new.
- Otto
ion strings. This is something I seek to find an
elegant solution for..
- Otto
life much easier for the Debian
maintainer, and in general all distros and the whole upstream code
base benefits of the extra QA.
- Otto
projects I maintain in Debian if the upstreams trust
me enough to give write access. The closer a maintainer is to the
upstream, the better everything will be I reason.
- Otto
>From
>https://janitor.debian.net/lintian-fixes/#i-dont-find-this-useful-how-do-i-stop-it
>I don’t find this useful. How do I stop it?
>If you ignore or close the first merge proposal, there won't be any more for
>the same maintainer.
>You can also just comment on the merge proposal that you don
Hello!
Do we have Debian devs here who have pimped their shell heavily with custom
prompts, colors, command line fonts, shell window title hacks, perhaps
using zsh etc? Have you written blogs about you experiences, can you share
some good reads (with screenshots) of what you have done?
I've read
an yet:
https://towardsdatascience.com/rust-powered-command-line-utilities-to-increase-your-productivity-eea03a4cf83a
- Otto
Hello!
Just my 2 cents: I hope Debian would not rush to any changes here.
Lets just stay neutral for now. The subject seems very US-centric and
there is a risk that it is creating division among people forcing them
to take sides on issues that previously were not political at all.
Here is some ba
Hello!
> > Imagemagick in Debian is extremely outdated (6.9.10.23 vs 7.0.10-21),
> > causing some FTBFS on packages that depend on it.
..
> It doesn't need a one time NMU, but an additional 1-3 active maintainers.
> Failing that, we should rather drop it for bullseye.
Personally I prefer the drop
Hello!
Finalizing and publishing DEP-14 would be nice.
I have been using git-buildpackage for all of my packages for many years
already, and thus been automatically following these guidelines as they are
followed by git-buildpackage.
There are only two diversions I've noted:
- in git-buildpackag
Hello!
ma 8. kesäk. 2020 klo 12.04 Arturo Borrero Gonzalez
(art...@debian.org) kirjoitti:
>
> On 5/27/20 9:06 PM, Otto Kekäläinen wrote:
> > Hello!
> >
> > Do we have Debian devs here who have pimped their shell heavily with custom
> > prompts, colors, command line f
2016-07-08 17:55 GMT+03:00 :
> I value stability of a FS over other considerations like shiny new features
> and performance. I know that Debian Stable includes only that versions of
> software that were considered rock-solid and mostly bug-free. But on the
> other hand I read documentation for
asonable time
otherwise.
If you wish to participate in testing or finalizing this scheme,
please reply to this thread or write to pkg-mysql-maint@.
On behalf ot the pkg-mysql team,
- Otto
Hello!
2016-08-16 7:44 GMT+03:00 Rene Engelhard :
> On Sun, Jul 10, 2016 at 05:22:22PM +0300, Otto Kekäläinen wrote:
>> Hello maintainers of packages that depend in MySQL/MariaDB!
>
> Not everyone is required to read -devel. Mailing them where they read
> it (and be it Cc&
s metapackages.
I would be fine by doing what you suggest. What does Robie and others
who are more vested in maintaining Oracle packages think about this?
- Otto
explanation about mirroring that repo.
I don't know about other official sources, but our mirror also offers
the debian-debug repo:
http://ftp.halifax.rwth-aachen.de/debian-debug
ftp://ftp.halifax.rwth-aachen.de/debian-debug
rsync://ftp.halifax.rwth-aachen.de/debian-debug
Bye,
Carsten
--
Hi!
On Tue, 15 Oct 2024 at 00:05, Joachim Zobel wrote:
>
> Hi.
>
> DEP-14 states under "About repacked upstream sources" that files that
> are removed from repacked sources should not be in the upstream
> branches.
>
> This does however create modify/delete conflicts when upstream modifies
> the
Hi!
...
> That setup sounds nice! What is your workflow to import a new upstream
> release?
>
> I see the watch file still points to the tarball:
>
> https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/watch
>
> Would it be possible to extend the debian/watch syntax t
ails, see gbp.conf in the package
(https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/gbp.conf).
- Otto
PS. Massive thanks to Guido for maintaining git-buildpackage, it is a gem!
Hi!
...
> > FWIW, I'm happy to administer the service and if Otto also signs up
> > for this with me, we would be two DDs.
> >
> > I think Nicolas has done great job working on this and I've proved I
> > was motivated in helping fixing things in Lintia
Hi,
ma 28. lokak. 2024 klo 4.27 Sean Whitton kirjoitti:
>
> Hello,
>
> On Sun 27 Oct 2024 at 05:29pm GMT, Otto Kekäläinen wrote:
>
> > Hi!
> >
> >> > Seems this is still the most optimal way to ensure git is correct:
> >> >
> >> >
Hi!
> > Seems this is still the most optimal way to ensure git is correct:
> >
> >gbp import-dsc --verbose --pristine-tar apt:j4-dmenu-desktop/sid
> >
> > Also, dgit pull can be used to get the latest source automatically, but
> > unfortunately those
> > git commits are made as a custom "Debi
Hi!
On Mon, 11 Nov 2024 at 11:37, Andrey Rakhmatullin wrote:
>
> On Mon, Nov 11, 2024 at 06:03:22PM +0100, Alexandre GRIVEAUX wrote:
> > Hello,
> >
> > Some time ago I created some merge request on salsa for debian-xen:
> >
> > https://salsa.debian.org/xen-team/debian-xen/-/merge_requests?scope=a
Hi!
...
> > - The number of contributors/maintainers is low everywhere. Ending
> > single-person maintainership is not going to happen any soon, but hopefully,
> > we can work towards first increasing the pool of contributors who
> > participate, and then expand on practices around Merge Requests
Hi!
Thanks for following up. Based on the feedback about the goal/scope I
decided to rewrite the DEP-18 almost completely, and published a new
draft at https://salsa.debian.org/dep-team/deps/-/merge_requests/12
On Tue, 5 Nov 2024 at 03:14, Jonathan Dowland wrote:
>
> It's been a while since -dev
eview that your current
usage is optimal.
We also added a RUNNERS.md for those who want to experiment with
customer runners or donate CI capacity to Debian.
Feedback and improvement suggestions are also welcome as Merge
Requests are via email.
- Otto
Hi!
On Fri, 27 Sept 2024 at 09:38, Iustin Pop wrote:
...> I just added a barebone config for one of my packages, and while the
> pipeline worked, I got an error for the arm64 cross-compile that seems
> to be due to tooling issues:
In addition to what Johannes replied about cross-builds having is
for helping us get lintian.debian.org recreated!
Otto
rbose --pristine-tar apt:j4-dmenu-desktop/sid
This will both check if there are any newer uploads than what git
knows about, and if needed, also download, apply and commit the
uploads using the uploader as the git author. The result of this
particular example is visible in
https://salsa.debian.org/ot
Thanks for all the comments!
Trying to summarize and expand on the points raised:
Seems this is still the most optimal way to ensure git is correct:
gbp import-dsc --verbose --pristine-tar apt:j4-dmenu-desktop/sid
Also, dgit pull can be used to get the latest source automatically, but
unfort
Hi!
On Tue, 15 Oct 2024 at 05:47, Joachim Zobel wrote:
>
> Am Dienstag, dem 15.10.2024 um 00:09 -0700 schrieb Otto Kekäläinen:
> > I suspect you have something wrong with the branch structure, perhaps
> > you are trying to remove files in actual upstream branch and not the
&g
> > I'm still trying to understand if it's a good idea to contact
> > upstream authors and tell them their software is being worked on to
> > be included in Debian, or not.
..
> So my advice is to go for it, maintaining software in Debian is much
> more fun when there is a positive exchange with th
> I believe that Otto's lets-standardize-on-salsa effort is fundamentally
> a good thing. Let's help him flesh out the details.
Thanks!
Please also help Guido iterate on git-buildpackage so that it works
well, is easy to debug, has good docs etc. Based on discussions in
this thread there are a l
Thanks Gioele for the stats. I noticed that 90% of the votes came in
the first two days.
In this system you can unvote and put your thumbs up on another
proposal if you want to change your mind now after letting the
question sink in for a few weeks, but please make sure you have voted
only on one
754abaefe7ca7ebf79
fatal: the remote end hung up unexpectedly
± gbp export-orig --pristine-tar
gbp:info: Creating
/home/otto/debian/js-team/node-cacache_17.0.3+~cs10.3.7.orig.tar.gz
gbp:info: Creating
/home/otto/debian/js-team/node-cacache_17.0.3+~cs10.3.7.orig-fs-minipass.tar.gz
gbp:info: Creati
Hi!
> With all the recent talk about increasing the use of git for
> packaging, I'd like to address one thing: git-buildpackage is very
> complex to use. As an alternative, I'd like to propose a simpler
> setup:
..
> sick of it and I can tell you it only makes me want to ignore you. If
> you ask
Your are right Simon, the body actually says "DEP0" and only title has
DEP-0 (
https://salsa.debian.org/dep-team/deps/-/blob/master/web/deps/dep0.mdwn#L1).
The changelog even has "DEP 0".
Front page of dep-team.pages.debian.net spells it with a space.. The role
model https://peps.python.org/pep-00
this way of working, and hopefully doing it in a way that it
does not stifle work for maintainers who prefer to continue their
single-maintainer habits, so nobody feels at loss.
On Tue, 27 Aug 2024 at 19:13, Otto Kekäläinen wrote:
>
> Hi!
>
> While I intend to continue on iterating
Thanks for the comments!
Let's implement this. Please vote on which variant you prefer by
giving a thumbs up at
https://salsa.debian.org/dep-team/deps/-/merge_requests/13
Unify DEP spelling with a dash instead of a space (e.g. "DEP-0")
OR
https://salsa.debian.org/dep-team/deps/-/mer
> > collecting stats from Debian packages, using for example data points
> > that 13573 packages in Debian have explicitly a debian/gbp.conf file
> > already.
>
> I guess those data points include how many packages use salsa, with
> various Gitlab features enabled.
>
> Since various Gitlab features
Hi!
> fwiw, I'm also not using git-buildpackage and I don't want to. (Step learning
> curve, too much magic, hard to debug and I dont see benefits for the packages
> I maintain.) I'm also not a beginner. And I love gbp-dch.
I think git-buildpackage is great, and I am a happy user. However, it
too
101 - 200 of 294 matches
Mail list logo
