Package: dino-im
Version: 0.4.4-1~bpo12+1
Severity: normal
Dear Maintainer,
when the pcspkr module is loaded (was the default on my machine), dino
uses it
to beep when I press backspace on an empty input line.
To reproduce:
- execute `modprobe pcspkr` if it is not loaded
- open a chat in din
I can try importing latest upstream and run reverse builds for all
dependants.
One challenge I have at the moment is that upstream is not responding on
GitHub PRs and ignoring fixes and also not publishing any policy of which
RocksDB version is likely good for long-term maintenance. Thus there is
Currently in NEW queue since Dec 27th, 2024:
https://ftp-master.debian.org/new/glow_2.0.0-1.html
> > Hi folks!
> >
> > Can we now in 2025 agree that `wrap-and-sort -vast` is what we should
> > recommend new people joining Debian to use?
>
> I feel this question has become moot now that we have X-Style.
The X-Style is used by 'deputy reformat' only. This bug report is
about updating defaults i
Hi folks!
Can we now in 2025 agree that `wrap-and-sort -vast` is what we should
recommend new people joining Debian to use?
This proposal (--wrap-always, --short-indent, --trailing-comma) has
been open since 2018. If we can at least in principle agree that this
is best practice, the next discussi
For additional context, the build log
https://people.debian.org/~sanvila/build-logs/202412/golang-golang-x-net_0.27.0-1_amd64-20241206T201010.312Z
contains the error (which was missing from this bug report):
...
--- PASS: TestNodeLabel (0.00s)
=== RUN TestFind
--- PASS: TestFind (0.00s)
=== RUN
Package: debmake
Version debmake/4.5.1-1
Hi!
While using latest debmake I noticed that the debian/upstream/metadata
it produces seems to only consist of a citation block and nothing
else. All the "normal" fields are missing. In particular the
"Repository:" field is missing, which is important for
Hi!
I am happy to sponsor the upload of any package that has prior to
upload been proven to not have any easily testable regressions by
running Salsa CI on it. Would you be willing to put a bit of extra
work in and adopt Salsa CI as it is in the latest pkg-go-tools?
See https://salsa.debian.org/g
Forwarded: https://github.com/cli/cli/pull/10151
Hi!
I submitted fix upstream in https://github.com/cli/cli/pull/10151 and will
backport into Debian and coming days.
This could be a bit faster if the existing package maintainer replies to
email this week. I don't feel confident doing changes in
Package has now landed in NEW queue:
https://ftp-master.debian.org/new/prometheus-phpfpm-exporter_0.6.0-1.html
Yay!
Thanks Nicolas for your work to help Debian!
Forwarded: https://jira.mariadb.org/browse/MDEV-34788?
This seems to be flaky tests and not inherently a blocker for the i386 rebuild.
These issues seem like a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052838 "mariadb:
FTBFS multiple archs: Post-build tests randomly fail on
Fix pending review at https://github.com/Debian/dh-make-golang/pull/235
, feel free to check out the
package status and file Merge Requests with whatever improvements you
wish to see in Godot.
- Otto
Hi,
> Before we move on, please allow me to ask what problem the nproc tool is
> supposed to solve. Of course it tells you the number of processors, but
> that is not a use case on its own. If you search for uses, "make
> -j$(nproc)" (with varying build systems) is the immediate hit. This use
> i
Hi!
This was discussed on Go team mailing list a couple weeks ago before
uploading. I will submit a fix for this and also gh in a couple of days.
Hi!
Thanks for updating the package. On a quick look seems you updated
branch structure to follow DEP-14, but you nothing else. I am curious
to know why you don't see value in having Salsa CI running on the
pipeline?
You don't have to add it, I am just curious. I the package is good
enough to be
> It is somewhat unusual for multiple versions of an app to be available
> in a single Debian release. Why do you want to do it in this case?
>
> If you do think it's necessary, I consider it best practice to package
> the newer version with the unversioned package name. In other words,
> latest go
Package: python3-fastapi
Version: 0.115.5-2
Using latest version of FastAPI, it refuses to start and wants to be
re-installed via pip. This does not seem right?
# dpkg -l | grep fastapi
ii python3-fastapi 0.115.5-2 all
modern, fast, web framework for buil
Package: debmake
Version: debmake/4.5.1-1
Severity: wishlist
When I package something for Debian the starting point is often a git
repository, not a tarball. Debmake supports this, but it is very
unintuitive currently, and e.g. #948844 exists partially because of
the confusion.
Steps to reproduc
Package: debmake
Version: debmake/4.5.1-1
Severity: wishlist
Debmake creates a lot of useful template files, and has a bunch of
automation to ensure debian/control etc are correct. List of files
debmake creates on default setting currently:
README.Debian
README.source
changelog
clean
control
copy
://launchpad.net/~otto/+archive/ubuntu/ppa/+builds?build_text=&build_state=all,
which also allows the built binaries to be downloaded and run locally
if anyone wants to test.
On Sat, 14 Dec 2024 at 17:08, Otto Kekäläinen wrote:
>
> Hi,
>
> Sorry for cross-posting to both bug, package maintai
repositories
in parallel at least in of Trixie. Details of our plan for that will
follow later. This email was sent for the purpose of heads-up of
imminent upload.
- Otto
PS. While doing this packaging we leveraged as much as possible of all
state-of-the-art tooling in Debian, such as git
Hi Jonas,
Is this something you could help with as the maintainer of Oxigraph?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088523
Hi!
> > I noted this in
> > https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/97#note_556179
>
> Hi! Thanks and I hope 11.4.4 will get released sooon.
If you add your review/LGTM comment to the MR I can proceed with merging it.
Hi!
Thanks for reporting!
I noted this in
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/97#note_556179
Thanks Simon for working on this!
Can you point to a man page or blog post or README to help people like
me learn what this is and how it is designed to be used?
Hi!
> Ah, right, I was wondering why this isn't the case over here but turns
> out my scripts are running "gbp dch -R -- debian/" since years.
>
> > Maybe gbp dch could have this automatically if debian/source/format
> > `3.0 (quilt)`?
>
> Or rather make it the default and only include the full hi
> On Sun, Dec 01, 2024 at 09:44:17PM -0800, Otto Kekäläinen wrote:
> > My intent here was to suggest specifically that the version of form
> > 0.0~git20130606.b00ec39-1 would be elevated as the Policy recommended
> > form, as it makes sense and is already most popular.
>
&g
Hi,
> This would not constitute any sort of rejection for which maintainers of
> packages would need to be concerned. It does not mean anyone's
> practices should change.
>
> It does not mean that there is no policy (lowercase 'p') for these
> version strings in Debian.
What I am trying to expre
> > On Wed, Nov 27, 2024 at 01:11:14PM -0800, Otto Kekäläinen wrote:
> >> Package: debian-policy
> >> Found: 4.7.0.1
> >>
> >> I would like to suggest the Debian Policy to recommend a specific
> >> Debian package version string scheme in cases wh
A new version 3.2 has been uploaded to unstable.
Could you please assist the maintainer by checking if this bug can
still be reproduced with latest version?
> > The changelog is easy to update to only include Debian changes with:
> >
> > gbp dch -- debian
>
> That's not needed as gbp-dch looks at the packaging branch so commits
> from upstream vcs aren't included.
Yes it is needed when gbp import-orig --uscan runs with
gbp.conf:upstream-vcs-tag co
Hi,
> > Additionally, there should be a new config option
> > `upstream-git-signatures`, which if set would make the warnings errors
> > and refuse to import if tag was not signed, or the key didn't match.
>
> +1
>
> I think upstream tag signature verification failures should be an error,
> not a
The changelog is easy to update to only include Debian changes with:
gbp dch -- debian
Maybe gbp dch could have this automatically if debian/source/format
`3.0 (quilt)`?
For context, I have this workflow for all my packages:
git fetch --verbose upstreamvcs
# Note latest tag, e.g. r3
Isn't this feature already implemented?
I have in gbp.conf the line `sign-tags = True` and after each upload I
just run these commands that does the tagging and signing
automatically:
gbp tag --verbose
gbp push --verbose
CC: to Simon who has special interest in supply-chain security
This is a comment to both
Bug#839866 import-orig: please make --upstream-vcs-tag=... verify tag signatures
Bug#980927 import-ref: Check tag signatures
The function to verify git tags is already in
https://salsa.debian.org/agx/git-buil
See also related bug report in
dh-make-golang:https://github.com/Debian/dh-make-golang/issues/233
Potential fix posted at
https://salsa.debian.org/agx/git-buildpackage/-/merge_requests/19
I am happy to review and sponsor this.
I created https://salsa.debian.org/debian/crazy-complete and invited
n-peugnet there.
Package: ftp.debian.org
Severity: normal
Hi,
Please remove src:mylvmbackup from unstable.
There hasn't been any new releases from upstream for 10 years
(https://lenzg.net/mylvmbackup/) and it has multiple bugs nobody seems
to have interest in, and probably people are not using this anymore
since
Hi,
...
> But I suppose this is an issue because other versions don't have
> the versioning tag and the linker accidentally picked a symbol that
> I don't know, doesn't really exist? I don't know how this happens.
Thanks for looking into this issue and filing follow-up against gcc14!
I see that
> The commit hash. 007c9af.
OK, thanks.
I disagree here - to me the git commit hash is the single most
important identifier for the software version if there are no actual
releases.
look at
the CI run and full log at
https://salsa.debian.org/otto/rocksdb/-/jobs/6664708/raw
I need the help of the Oxigraph maintainer to debug this.
running 13 tests
test sparql::algebra::tests::test_send_sync ... ok
test sparql::model::tests::test_send_sync ... ok
test sparql::eval::tests::uuid
Hi!
Thanks for reviewing build logs. Can you please double-check what log
and version you looked at and from what year?
The bug report was filed on a very old version. Latest version of this
package in 10.5 series is 1:10.5.26-0+deb11u2.
I am 98% confident MariaDB never built using WolfSSL in De
> Please recommend only putting this information into the changelog entry.
> It has no place in the version value.
Sorry, I don't understand, can you elaborate?
In the case of say for example canid 0.0~git20180613.007c9af-2, which
part of this version string do you think does not belong there and
Package: debian-policy
Found: 4.7.0.1
I would like to suggest the Debian Policy to recommend a specific
Debian package version string scheme in cases where upstream has no
releases, but they do have git commit ids to refer to:
***
In case your upstream does not use version numbers, the Debian pac
Hi!
Did you notice Debian build is failing in CI?
https://salsa.debian.org/jas/gitsign/-/jobs/6661378
> Another solution could be a debian/not-installed file, if you prefer to
> not override dh_auto_install like the above.
That file is actually only to allowlist files that are built, but not
included in the package. Normally in modern Debhelper builds the
packages fail on file mismatches if there
Perhaps some pre-depends relationship is missing and upgrades fail due
to mismatching ABI..?
I am only seeing this issue on upgrades. Bootstrapping a system from
scratch does not have this issue.
> > If any of you have have spare time, I'd appreciate a review of
> > https://salsa.debian.org/go-team/packages/golang-github-muesli-mango-pflag
> > before I upload.
>
> Looks good to me.
>
> Instead of the patch I would have added in debian/rules:
>
> override_dh_auto_install:
> dh_auto_i
ate -q": error while running
runtime: exit status 100
Please take a look what is going on.
Please also consider using better CI before uploads.
I don't know if the root cause of these are the same, but a simple
Salsa CI test run at
https://salsa.debian.org/otto/python-apt/-/pipeli
Packaging in progress at
https://salsa.debian.org/go-team/packages/golang-github-muesli-mango-cobra
Feedback/reviews welcome!
Packaging in progress at https://salsa.debian.org/go-team/packages/glow
Feedback welcome!
This depends on also on golang-golang-x-text being re-uploaded to Debian.
Hi!
It works, thanks!
If any of you have have spare time, I'd appreciate a review of
https://salsa.debian.org/go-team/packages/golang-github-muesli-mango-pflag
before I upload.
Commits:
https://salsa.debian.org/go-team/packages/golang-github-muesli-mango-pflag/-/commits/debian/latest
CI:
https
Bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073803 is a
duplicate of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064050.
I am however unable to merge them because of:
> unblock 1073803 by 1073804
Bug #1073803 [wnpp] ITP: zellij -- terminal workspace with batteries included
No va
Package: wnpp
Severity: wishlist
Owner: Otto Kekäläinen
* Package name: golang-github-muesli-mango-cobra
Version : 1.2.0-1
Upstream Author : Christian Muehlhaeuser
* URL : https://github.com/muesli/mango-cobra
* License : Expat
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Otto Kekäläinen
* Package name: golang-github-muesli-mango-pflag
Version : 0.1.0-1
Upstream Author : Christian Muehlhaeuser
* URL : https://github.com/muesli/mango-pflag
* License : Expat
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Otto Kekäläinen
* Package name: glow
Version : 1.2.0-1
Upstream Author : Charm
* URL : https://github.com/charmbracelet/glow
* License : Expat
Programming Lang: Go
Description : Render Markdown on the CLI
Glow
Hi Paul!
Thanks for reporting. This is actually already fixed but upload is
pending a second pair of eyes to say LGTM on
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/97
and later
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/98
if no bugs surface i
> This was already reported (without details but with the same 1-character
> fix) in PR #641: https://github.com/codership/galera/pull/641 in June 2023
> but no response ever happened. That's what I initially wrote in this bug
> report and why I wasn't eager to report it (again) to upstream. I hesi
Hi!
> First of all - the mariadb packages are really great, and the new
> passwordless root setup is awesome, thanks for all your work.
Thanks! We debuted it in Debian 10 years ago, and since both upstream
MariaDB and MySQL started using it everywhere.
> One small thing though - If you use `mysq
Hi,
Thanks for investigating this. Now when I see that this is purely an
upstream regression and only a patch in Debian, I suggest you submit this
first and foremost upstream and mark the Debian bug Forwarded.
Upstream github.com/codership/galera is very responsive to PRs and you have
here good r
ll
> syntax is allowed and what it means.
>
> Patch from https://salsa.debian.org/otto/policy/-/tree/vcs-example attached.
> FWIW: On my KDE system, ``README.source`` gets opened in Kate, while a
> file ending with ``.md`` gets opened in Okular, which renders Markdown.
Like wise with both Bat (rust) and Glow (go), the most popular
command-line "colorized" viewers: only files ending with .md will be
correctly rendered
Hi!
Thanks for investigating! If you have a fix, submit it targeting
debian/latest.
If all reviewers agree and it is merged, I can later cherry-pick it on the
other branches. You don't need and should not send the same thing for
multiple branches.
Hi!
> Are there tools that automatically locate README.source and would need to be
> adapted to
> find README.source.md instead ?
Not to my knowledge. This file is consumed by humans / Debian
maintainers to learn about the source package. Most likely it is
accessed by typing $EDITOR debian/READM
Package: debian-policy
Found: 4.7.0.1
Currently
https://www.debian.org/doc/debian-policy/ch-source.html#source-package-handling-debian-readme-source
talks about `README.source`.
I suggest we would allow this file to alternatively be in Markdown
format, and spell the filename as `README.source(.m
>From https://peps.python.org/pep-0594/#pipes
> The pipes module provides helpers to pipe the input of one command into the
> output of another
> command. The module is built on top of os.popen. Users are encouraged to use
> the subprocess
> module instead.
Hi!
I merged your submission. Thanks!
I also fixed the CI so that it can run again, and it uncovered a
regression: https://salsa.debian.org/mariadb-team/galera-4/-/jobs/6581726
/var/lib/dpkg/tmp.ci/preinst: line 12: adduser: command not found
Do you want to take a look and do a follow-up su
Hi Laszlo!
I have not merge anything new on RocksDB as I have kind of been
waiting for your comments/review. Should I continue to wait?
On Mon, 1 Jul 2024 at 14:37, Otto Kekäläinen wrote:
>
> Hi!
>
> > > Are you OK if I push this to https://salsa.debian.org/debian/rocksdb ?
Hi,
Just for awareness: Debian already has Debcraft, which builds Debian
packages in an isolated Docker environment. It supports both Docker
and Podman, and it also has a bunch of other automation to help do
quick rebuilds of packages after modifications, and compare how the
end result changed, do
Hi!
Thanks for the patch Rebecca. Would you like to submit it directly
upstream in https://jira.mariadb.org/browse/MDEV-35088 or at
github.com/mariadb/server?
Hi,
Status regarding https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069895
- the 10.11.9 upload to stable-proposed was done in September but
release team didn't clear it until Oct 27 in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080370
- new upstream 10.11.10 was released on Nov 1st,
-team/mariadb-server/-/merge_requests/97.
Everything seems to work and no regressions were found.
- Otto
s.
* Add Lintian overrides for new upstream documentation JavaScript files
-- Otto Kekäläinen Tue, 05 Nov 2024 21:14:47 -0800
Hi!
Your suggestion makes sense. Do you want to work on implementing it
and submit a Merge Request at
https://salsa.debian.org/mariadb-team/galera-4 ?
- Otto
Hi,
On Wed, 19 Jun 2024 at 11:15, Sam Bull wrote:
>
> Package: mariadb-server
> Version: 1:10.11.6-0+deb12u1
> Severity: important
>
> Dear Maintainer,
>
> After an OOM kill, the process is not restarted by systemd.
>
> In the service file is:
> Restart=on-abort
>
> I believe this should be:
> Re
Hi,
The fmtlib version 10.0 and 10.1 is known to have a broken thousands
separator, which breaks at least MariaDB and possibly other packages
as well.
Can you either transition directly to fmtlib 10.2 or 11.0, or
cherry-pick either of these fixes to 10.1?
https://github.com/fmtlib/fmt/issues/383
latest libfmt version in
https://salsa.debian.org/otto/mariadb-server/-/jobs/6534951
Hi!
On Thu, 31 Oct 2024 at 23:56, Adam D. Barratt wrote:
>
> On Mon, 2024-09-02 at 17:16 -0700, Otto Kekäläinen wrote:
> > /edit
> >
> > I propose that the latest minor maintenance version of MariaDB be
> > included in
> > the stable release update of D
Hi!
MariaDB 11.11.9 was uploaded to Debian stable updates proposed on September 2nd:
https://tracker.debian.org/news/1580461/accepted-mariadb-110119-0deb12u1-source-into-proposed-updates/
https://tracker.debian.org/pkg/mariadb
It may or may not be included in the next point release (scheduled fo
For the record, this issue is no longer visible on amd64 autopkgtests
at https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines/756431
nor at https://ci.debian.net/packages/m/mariadb/, only armhf and that
probably only because the arch is dropping jobs and no rerunning the
test despite th
Hi
Please try the latest version in stable updates/proposed updates that was
uploaded two month or so ago.
On Sun, 27 Oct 2024 at 20:58, Santiago Vila wrote:
>
> El 27/10/24 a las 21:09, Otto Kekäläinen escribió:
> > Do you Faustin want to dive into why the timezone started to behave
> > differently recently in Debian?
> >
> > Sergei and Daniel already looked at
>
Do you Faustin want to dive into why the timezone started to behave
differently recently in Debian?
Sergei and Daniel already looked at
https://jira.mariadb.org/browse/MDEV-35088, but you could help find
out what changed in Debian Sid recently.
On Tue, 8 Oct 2024 at 06:45, Otto Kekäläinen wrote
.
Patch from https://salsa.debian.org/otto/policy/-/tree/vcs-example attached.
From aabf7692ce50d3ab3a01bb334ed38cacfd909fad Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Otto=20Kek=C3=A4l=C3=A4inen?=
Date: Thu, 10 Oct 2024 17:05:07 -0700
Subject: [PATCH] Add an example of Vsc-* usage to make section
Forwarded: https://jira.mariadb.org/browse/MDEV-34318
Hi,
This is most likely not related to the Debian packaging, so I
recommend filing a bug directly at upstream jira.mariadb.org instead -
and check first if it is already filed there.
Forwarded: https://jira.mariadb.org/browse/MDEV-35088
Hi,
I did notice this already a couple days ago. It is visible both in
Debian CI and in Salsa CI. I don't know what changed in Debian (it is
not a change in MariaDB), and I don't know if the MariaDB test should
be adapted/updated to be more ro
/edit
I propose that the latest minor maintenance version of MariaDB be included in
the stable release update of Debian. This bug report is to make it visible and
trackable to the release team that this update is available and work is in
progress.
The update is currently being worked on and revie
o maintain
* Add NEWS item to explain new `mariadb-dump` option `--sandbox`
-- Otto Kekäläinen Fri, 24 May 2024 22:02:01 -0700
/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.19.txt
* Adopt gbp.conf from 'debian/latest' but adopt it for 'debian/11-bullseye'
* Salsa CI: Update and unify with debian/latest and debian/bookworm
-- Otto Kekäläinen Sat, 31 Aug 2024 00:36:04 -0700
/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.19.txt
* Adopt gbp.conf from 'debian/latest' but adopt it for 'debian/12-bookworm'
-- Otto Kekäläinen Sat, 31 Aug 2024 00:26:53 -0700
Thanks for expressing that you are inclined and not objecting such a
change. I will put time in making an MR and technical proposal with details.
aming the package to dbconfig-mariadb in coming months?
- Otto
Hi!
I saw this again today in a container but when I tried to reproduce it
didn't happen again..
Yes to finalizing DEP-14 soon, but first I think we need to complete the
technical work to have git-buildpackage use DEP-14 branch names by default.
I tried implementing it but turned out a bit too involved..
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829444
Use DEP14 branch layout by defa
Hi!
Note that MySQL 8.0 will be end-of-life in 2026, so not only will it
be FTBFS during trixie, it will also be out of support. However,
Debian only releases with MariaDB - the package mysql-8.0 is only in
unstable and will never be promoted to testing/trixie.
As long as MariaDB is 2038 compatib
Package: bash
Version: 5.2.21-2.1
Hi!
I noticed CI failing on:
Preparing to unpack .../bash_5.2.21-2.1_amd64.deb ...
Unpacking bash (5.2.21-2.1) over (5.0-4) ...
Setting up bash (5.2.21-2.1) ...
dpkg (subprocess): unable to execute installed bash package
post-installation script (/var/lib/dpkg/i
Fix pending review at
https://salsa.debian.org/debian/debcraft/-/merge_requests/13
1 - 100 of 1090 matches
Mail list logo
