Hi!
Can you please test if this is now fixed in latest Debcraft version 0.6.0?
If you find more issues or have improvement ideas, Merge Requests at
https://salsa.debian.org/debian/debcraft/-/merge_requests are very
welcome!
Hi LaMont Jones!
Are you still maintaining xdelta? Do you object if I salvage it?
Looking at the upload and commit histories you haven't touched the
package since 2009. Seems you haven't been active in Debian at all
since 2017. In effect, the real maintainers have been Antonio and
Andrej.
You pr
Hi!
> Globing pattern out of order above line 20
The warning above looks excellent; thanks for implementing it. Can we
please have this expanded to detect all cases of globbing pattern out
of order, so it works for the grep example too?
Control: reopen -1
Hi!
Thanks for trying to address this. However I reopened this as I just
tested licenserecon 8.0 and I don't see it emitting any warning about
misordered copyright stanzas.
Steps to reproduce:
1. check out the grep source version at
https://salsa.debian.org/debian/grep/-/merg
As the dependency golang-github-pingcap-errors entered to unstable,
this was now uploaded to NEW:
https://ftp-master.debian.org/new/golang-github-pingcap-failpoint_0.0~git20240528.b51a646-1.html
When using latest
https://salsa.debian.org/otto/dh-make-golang/-/jobs/8339383/artifacts/raw/debian/output/dh-make-golang_0.8+git20250820.a6fe7fa-1~otto+salsaci+20250923+43_amd64.deb
we get:
# dh-make-golang estimate github.com/ethereum/go-ethereum
2025/09/23 23:58:52
github.com/Azure/azure-sdk
Hi!
Please instead of the dh-make-version I posted above use this with
more improvements instead:
https://salsa.debian.org/otto/dh-make-golang/-/jobs/8339383/artifacts/raw/debian/output/dh-make-golang_0.8+git20250820.a6fe7fa-1~otto+salsaci+20250923+43_amd64.deb
Note also related
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107167 "ITP:
mev-boost -- MEV-Boost allows Ethereum validators to source high-MEV
blocks from a competitive builder marketplace"
Seems I was fast enough and got this a new version into Debian before
the RM ran:
https://tracker.debian.org/news/1664618/accepted-mydumper-0101-2-source-into-unstable/
Package: src:mariadb
Version: 1:11.8.3-1
Owner: o...@debian.org
The MariaDB client package has multiple Perl dependencies, which
should be reviewed and potentially lowered to 'Suggests'
Current control file:
Package: mariadb-client
Architecture: any
Depends:
debianutils (>=1.6),
libconfig-inif
Hi Shengjing!
This https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112166 is
blockin golang-1.24 from migrating to testing. As the uploaded of this
package for most of 2025, I wanted to check if you are planning to
look into it?
Overview: https://tracker.debian.org/teams/go-compiler/
Adoption in progress at
https://salsa.debian.org/debian/gkermit/-/merge_requests/2
Hi,
MariaDB in Debian still does not ship an AppArmor profile. Would any of you
want to contribute to test/maintain one?
Current Debian packaging sources:
https://salsa.debian.org/mariadb-team/mariadb
Package: galera-4
Version: 26.4.23-1
Forwarded: https://jira.mariadb.org/browse/MDEV-36926
Owner: o...@debian.org
Galera 4 currently builds with the embedded copy of ASIO. It would be
better to use the system version.
See
- https://jira.mariadb.org/browse/MDEV-36926
- https://github.com/codership
Control: reopen -1
The sources of the upload was now pushed to
https://salsa.debian.org/debian/xfireworks/-/commits/master
The commit that adds a watch file is
https://salsa.debian.org/debian/xfireworks/-/commit/3ac2c017e498914f7f4c7befba9bcf9b027e2d9d
and it was not part of the upload, thus this
I don't see a new version pushed or tagged at
https://salsa.debian.org/debian/xfireworks/-/commits/master
Hi,
> > $ dpkg-source --version
> > Debian dpkg-source version 1.22.21.
> > $ dpkg-source --extract bpfcc_0.31.0+ds-7.dsc
> > dpkg-source: warning: cannot verify inline signature for
> > ./bpfcc_0.31.0+ds-7.dsc: no acceptable signature found
> > dpkg-source: info: extracting bpfcc in bpfcc-0.31.0+
Control: retitle -1 failed to select a version for the requirement
`pyo3 = "^0.22"`
Hi Santiago!
I ran into the same problem about inline-verify you have in the titles
in this Bug#1114336 and some others, e.g. Bug#1114098, Bug#1114184,
which you filed recently.
However neither of the bug reports
Hi!
I am running into this same issue:
$ dpkg-source --version
Debian dpkg-source version 1.22.21.
$ dpkg-source --extract bpfcc_0.31.0+ds-7.dsc
usage: sopv-gpgv inline-verify [-h] [--debug] [--not-before TIMESTAMP]
[--not-after TIMESTAMP]
Control: retitle -1 debcraft: ERROR: failed to solve: failed to read
dockerfile: open Dockerfile: no such file or directory
Hi!
What Docker version are you using? When I try to reproduce this with
Podman I get:
$ cd $(mktemp -d)
$ apt source bpfcc
$ debcraft build bpfcc_0.31.0+ds-7.dsc
Building
Package: src:xfireworks
Version: 1.3-15
The watch file at
https://salsa.debian.org/debian/xfireworks/-/blob/master/debian/watch
is missing. There is also no
https://salsa.debian.org/debian/xfireworks/-/blob/master/debian/upstream/metadata
file.
Thus there is no way to see what is the upstream or
I did some further testing with the example
https://salsa.debian.org/debian/podman-toolbox
Lintian currently warns:
W: golang-github-containers-toolbox source:
globbing-patterns-out-of-order
debian/gocode/src/github.com/acobaugh/osrelease/* debian/*
debian/gocode/src/github.com/acobaugh/osrelease
Interesting finding by Ahmed, perhaps lrc does not need to complain about this.
-- Forwarded message -
Ahmad Khalifa commented on a discussion:
By the way, the check you're looking for in that lrc bug is picked up
by lintian globbing-patterns-out-of-order
(https://udd.debian.org/l
Hi!
This exact same build error is easily reproducible in CI, see
https://salsa.debian.org/debian/xfireworks/-/jobs/8286448
I intend to help Yukiharu have Salsa CI enabled for this repository
and use it to validate the fix to this issue before next upload.
As the dependency golang-github-dchest-bcrypt-pbkdf entered to
unstable, this was now uploaded to NEW:
https://ftp-master.debian.org/new/golang-github-scaleft-sshkeys_1.4.0-1.html
Hi Ben!
I didn't notice any message from you yet on this bug that is blocking
your package from migrating to testing:
https://tracker.debian.org/pkg/recastnavigation
What did you have planned as your next steps?
To me this symbol "_Z15rcBuildP..." looks like an internal private
symbol that shou
As golang-github-pingcap-errors entered to unstable, this was uploaded
to NEW some weeks ago:
https://ftp-master.debian.org/new/golang-github-pingcap-errors_0.11.4-1.html
The source directory is mounted and used from the host system, not
copied from host to inside the Docker/Podman container.
Hi Ritesh!
Can you share which commands exactly you ran? I can't debug this
unless I there are steps on how to reproduce.
Hi!
I fixed this in unstable now. If Lee wants to finalize the Bookworm
update, it is now possible.
The branch https://salsa.debian.org/debian/mydumper/-/commits/debian%2Fbookworm
(and debian/bullseye) is all yours, Lee. If you want changes on the
debian/latest branch, please submit MRs and I am
Hi!
Please don't remove mydumper from unstable.
There is a ITS bug in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109991 and I have
assigned it to myself.
The package is widely used and should remain in Debian. Removing it
from unstable makes adopting it a lot harder.
its code to
> salsa. I have no objections to anyone putting effort into it, no need
> to worry about stepping on my my toes.
I no longer have mpt hardware, but if Triston wants to maintain this
package I am happy to review/sponsor/upload his work.
- Otto
This is actionable, right? The tool could flag if copyright stanzas as
misordered so users know to fix that first before the rest of lrc can run
reliably.
Hi!
> I just saw in the the Mariadb Jira that someone has tested 10.11.14
> and it worked for them so far. As i said before i could test the debian
> packages on
> debian 12 and 13 before they are released. I should trigger the problem
> within an week if is still there.
You can test packages i
> I didn't yet get what is the upside of moving things is and what the
> proposals for
If we can agree to have the description of upstreams in this one file,
we can avoid duplicating the same configuration of for
git-buildpackage and uscan in two different places. The latest uscan
has started to r
To make any decisions here we would need the input from Guido, who is
for sure very busy at the moment, but hopefully can comment on this
some day.
Fixed in
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/48ef3c2dcd2fde4e747852f5c3fda1fcc18f0e11
and full details in Bug#1112499.
I will proceed to upload this to bookworm queue now and you can choose
to release it to bookworm-proposed-updates if you approve.
Actually I do see this warning in e.g.
https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/8130323
and https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/8130324
However, it is not preventing the service from starting nor does it
emit an exit code. Reproduction:
root@15f8cbad768d
Thanks for reporting!
Variable name is indeed wrongly cherry-picked, will fix it now. Weird that
our CI didn't catch this despite it starting and running the server in
every test.
Ack, I am investigating
If the submitter (or somebody else looking at this #1104463) does not
provide any additional information, I will need to close this issue.
Hi Daniel!
You filed this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1108553
and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105029, both
with with detailed investigations and a patch for upstream code. Did
you open PR(s) upstream, did they accept your fix?
- Otto
Ack, I will upload MariaDB maintenance releases for Trixie and Bookworm soon!
Hopefully we can also have Galera to latest version (Bug#1112140 and
Bug"1112141).
These have all been in unstable for a couple of weeks without issues,
and also upstream bug trackers do not seem to advertise any
regres
> Yes. Otherwise, with wildcards in play, it would not be possible to determine
> which license applies to which file.
> The syntax definition
>
> https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#files-field
> states;
>
> "Multiple Files stanzas are allowed.
> The last stanz
Hi Ritesh!
Can you share which commands exactly you ran?
Philip Hands wrote:
> If this feature were to be implemented as requested, I can imagine a
> scenario where someone who has until now not noticed salsa-CI might
> become aware of it only when git-debpush refuses to do what they want.
Please note what I wrote in
> 3. Check if the current git HEAD (
master/release-notes/release-notes-galera-26.4.22.txt
https://github.com/codership/documentation/blob/master/release-notes/release-notes-galera-26.4.21.txt
* New upstream release fixes garbd's -w/WORK_DIR parameter (Closes: #1088076)
-- Otto Kekäläinen Tue, 26 Aug 2025 14:47:38 -0700
deb
ed upstream
-- Otto Kekäläinen Tue, 26 Aug 2025 14:30:10 -0700
debian-26.4.23-0+deb13u1.debdiff.xz
Description: application/xz
debian-26.4.23-0+deb13u1.debdiff.stat.xz
Description: application/xz
Thanks for researching this!
So seems we shouldn't include the shell completion untill they get better
and handle file lookup nicely.
Control: block 1107484 by 1107502
Uploaded to NEW:
https://ftp-master.debian.org/new/golang-github-sethvargo-go-password_0.3.1-1.html
Uploaded to NEW:
https://ftp-master.debian.org/new/golang-github-pingcap-errors_0.11.4-1.html
see a bunch of errors now if running lrc on
https://salsa.debian.org/otto/grep/-/commits/676-repro
Seems that the ordering of the stanzas matter?
Do we have any tool that would reformat the debian/copyright file
automatically? Like wrap-and-sort is for debian/control but for
debian/control? If p
There seems to be 3 bug reports about checking upstream release tag signatures:
Bug#839866 import-orig: please make --upstream-vcs-tag=... verify tag signatures
Bug#871806: uscan: (dpkg, git-buildpackage) accept/mangle/store signed
git tags in cases where upstream does not publish detached sigs on
Thanks for reporting
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972273 in 2020. I
think this would be a useful feature.
I have in my ~/.gitconfig:
[tag]
gpgsign = true
[commit]
gpgsign = true
Thus all my tags are automatically signed. But it would be valuable
for Debian as a whole if git-
Hi,
I think this bug report could be closed.
The command `gbp tag` does tag and sign tags if gbp.conf has line
`sign-tags = True`. There is also git-debpush that creates the same
DEP-14 conformant tags and signs them (but with additional metadata
used by tag2upload).
It would be unnecessary for
>From
>https://salsa.debian.org/debian/devscripts/-/merge_requests/540#note_642316
I tried testing this on package
[glow](https://salsa.debian.org/go-team/packages/glow) that had the
Archive field added:
```diff
--- a/debian/upstream/metadata
+++ b/debian/upstream/metadata
@@ -3,3 +3,4 @@ Bug-Da
Thanks for looking into Debcraft!
All code is just shell script, so you can debug what the commands do by
injecting 'set -x' in the script. You can also run with --debug.
For me to be able to reproduce and investigate your report, can you share
which commands exactly you ran?
I see the outputs y
On the question if this gbp.conf option is really needed or if use of
signatures can be implied by the key:
> > - upstream-signatures
>
> One can already figure this out by checking the existence of
> debian/upstream/signing-key.asc. Why duplicate this here?
I wonder if we really can make this ass
After doing more research I realized I don't want to introduce this as
a new Debian package, as I don't want other packages to depend on it.
I will try to avoid it completely, or vendor it.
This package is based on the now-deprecated ioutil Go package. Its
functionality has been included in the Go
Uploaded to NEW:
https://ftp-master.debian.org/new/golang-github-pingcap-kvproto_6.1.0~alpha-1.html
Uploaded to NEW:
https://ftp-master.debian.org/new/golang-github-asaskevich-eventbus_0.0~git20200907.49d4230-1.html
Uploaded to NEW:
https://ftp-master.debian.org/new/golang-github-dchest-bcrypt-pbkdf_0.0~git20150205.83f37f9-1.html
Uploaded to NEW:
https://ftp-master.debian.org/new/golang-github-jeremywohl-flatten_1.0.1-1.html
Uploaded on Aug 15th to NEW:
https://ftp-master.debian.org/new/golang-github-lorenzosaino-go-sysctl_0.3.1+ds1-1.html
Later tried to upload an improved version but it won't replace the
existing one in the queue with the same version number.
If the current one in NEW queue passes, I need to revert
For the record, this was at the time of filing the ITP already in
Debian, actually since 2018 and maintained by Reinhard.
See https://tracker.debian.org/pkg/golang-gogottrpc in case someone
stumbles on this bug report and wonders what was the end result.
Control: owner -1 !
Control: retitle -1 ITP: golang-github-go-ethereum -- Official Go
implementation of the Ethereum
I plan to do this in collaboration with Leonardo Fonseca.
Work in progress at https://salsa.debian.org/go-team/packages/go-ethereum
Package: licenserecon
Version: 7.0
I am currently working on updating the `debian/copyright` file for the
`grep` package to ensure it is fully compliant and that `lrc` runs
cleanly. After making extensive updates to accurately document the
licenses of all source files, I've encountered some behavi
Hi,
> I'm using the one installed from
> https://salsa.debian.org/otto/dh-make-golang/-/jobs/7890897/artifacts/raw/debian/output/dh-make-golang_0.8+git20250727.a6fe7fa-1~otto+salsaci+20250729+35_amd64.deb
There is now a newer version:
https://salsa.debian.org/otto/dh-make-golang/-/j
Yes, all new versions are eventually published as stable updates as
you can see from the version histories at e.g.
https://tracker.debian.org/pkg/mariadb. I can't promise any schedule
right now though.
I will take over this package. I will update the Maintainer/Uploader
field in the next upload.
This would be a nice feature in git-buildpackage. There are two
potential places a user might need to remember to pull from:
- newer commits in the official git repository of the package
- newer versions in the official Debian archives in case of a NMU that
was not pushed to git
Right now users ne
Related, in
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmus-from-the-maintainer-s-point-of-view
we now have:
***
Note that easiest way to both check if your package has been NMUed,
and also automatically download and commit the changes into a
git-buildpackage maintained git
Hi!
I ran to this same error multiple times in past months when reviewing
Merge Requests about new upstream imports, and the submitter having
wrong/extra tags in their fork.
I see the error when I run the git fetch manually with `--quit` omitted:
± gbp pull --verbose --force twrightsman
gbp:info
In the Salsa CI pipeline, if git-buildpackage fails to fetch the
upstream tarball for whatever reason (git repository broken, missing
branches, pristine-tar mismatch) it will fall back to run the
origtargz command:
https://manpages.debian.org/unstable/devscripts/origtargz.1.en.html
I would be care
Package: git-buildpackage
Version: 0.9.38
For the past 2 years I have helped numerous people debug why their
Debian packaging git repo is messed up, or why imports or builds are
failing on various errors from git-buildpackage not finding branches
or tags or sources.
I would estimate that in 90% o
Hi,
Thanks for the suggestion, having those would indeed be good.
If you want to take a stab at adding them, I am happy to help with
testing/reviewing if you (or anyone else reading this bug report)
submit a Merge Request at
https://salsa.debian.org/go-team/packages/glow
Network calls are cheap, and it is already doing them to
salsa.debian.org. It is way more expensive to have humans -
potentially many of them - to debug what is going on when their work
got halted by interactions with a broken package in the Debian
archive. Doing cleanup type of work is also very d
Package: git-debpush
Version: 13.12
Severity: wishlist
Currently git-debpush has a bunch of checks, and options to --force
override those checks.
I would like it to have a new check that helps the average user avoid
tagging and uploading commits that did not pass the CI (typically
Salsa CI).
The
Hi,
I ran into this same issue today:
± git-debpush --gbp
git-debpush: found upstream tags: v0.1.0 upstream/0.1.0
git-debpush: use --upstream=TAG to say which one to use
Based on Ian's reply to Simon, the "upstream tag" that
git-debpush/git-deborig is looking for is the tag git-buildpackage put
> > I have one question about the design: How will this behave with
> > repackaged sources?
>
> I think it would behave exactly like non-repackaged origs. The
> upstream/ tag would contain the repackaged code, and the
> pristine-tar data would contain the usual binary diff. pristine-tar does
> not
Hi!
First of all thanks to Ian and Andrea for working on this tirelessly
since DebConf. For my packages having support for pristine-tar and
using real original tarballs is important and I am looking forward to
see https://salsa.debian.org/dgit-team/dgit/-/merge_requests/264
finished.
I have one q
Draft at
https://salsa.debian.org/go-team/packages/golang-github-lorenzosaino-go-sysctl/-/merge_requests/1
Latest status recorded in
https://salsa.debian.org/go-team/packages/golang-github-gohxs-readline/-/merge_requests/3
Package: ruby-mysql2
After uploading MariaDB 1:11.8.3-1 I saw the error below in debci at
https://ci.debian.net/packages/r/ruby-mysql2/testing/arm64/63206477/
There was this change in the Debian packaging:
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/cc276ff741c4d9e840ce59a3127ac
> >The git-buildpackage config includes these two attributes:
> >- upstream-vcs-tag
>
> I agree this would be useful to support as an upstream metadata field.
Great!
> >- upstream-signatures
>
> This seems to be more of a git workflow policy rather than an upstream
> metadata field.
> If upstrea
Package: git-buildpackage
Severity: normal
X-Debbugs-Cc: jel...@debian.org, sre4e...@free.fr
Hi!
The git-buildpackage config includes these two attributes:
- upstream-vcs-tag
- upstream-signatures
See in context at e.g.
https://salsa.debian.org/debian/dh-make/-/blob/master/lib/debian/gbp.conf.ex
Package: devscripts
Severity: normal
X-Debbugs-Cc: y...@debian.org, jel...@debian.org, sre4e...@free.fr
Hi!
The new templates feature in uscan for debian/watch contents greatly
streamlines things:
Example:
Version: 5
Template: Github
Author: guimard
Project: llng-docker
This is a grea
Package: lintian-brush
Thanks for maintaining lintian-brush, I use it all the time! Mostly I run this:
lintian-brush --no-update-changelog --modern --uncertain
After it ran I review manually and tweak what is needed, but most of
the time everything is great.
I also discovered the package ships
Hi!
Aquila (CC'd) would like to take over this package, but he never
commented this bug report so I am doing that now on this behalf.
New version and many improvements have been posted and approved at
https://salsa.debian.org/python-team/packages/persepolis-lib/-/merge_requests/1
I intend to spo
Hi!
Thanks for taking the time to use debugger to get the stack trace. As
this is not an issue in the Debian packaging, but more a upstream
MariaDB issues, could you please report this issue at
https://jira.mariadb.org/ ?
(and mark this Debian bug as 'forwarded')
Hi,
> with just
>
> Here is an example of the form the two values take for Debian's
> GitLab instance, salsa:
Sure, that makes sense. Updated accordingly at
https://salsa.debian.org/otto/policy/-/commits/vcs-example which you
can pull to your next/* branches wit
While we are waiting for segmentio asm to pass the NEW queue, would
you like to continue on Bug#1107561 and Bug#1107562?
We can work on them in parallel and do test builds using an extra
repository as I explained in a previous email.
Hi Leonardo!
While we are waiting for golang-github-offchainlabs-go-bitfield to
pass the NEW queue, would you like to continue on these other
packages?
We can work on them in parallel and do test builds using an extra
repository as I explained in a previous email.
uite sufficient for the branch
> targeted. A PR with MDEV-35904 would be much appreciated.
>
> On Tue, 10 Jun 2025 at 17:51, Daniel Black wrote:
>>
>>
>>
>> On Mon, 9 Jun 2025 at 16:48, Otto Kekäläinen via discuss
>> wrote:
>>>
>>> &
Control: forwarded -1 https://github.com/MariaDB/server/pull/4207
(updating Debian bug metadata - it should be able to update this bug
report automatically if upstream PR gets merged)
On Wed, 16 Jul 2025 at 13:23, Jean Weisbuch wrote:
>
> The upstream PR for the fix : https://github.com/MariaDB/
Hi!
> olaf$ ./mytop -h ""
>
> * username you specified "root" (default is "root")
>
> ...
>
> Access denied for user 'root'@'localhost'
What was your expectation here? Is there an account configured for
user 'olaf' to access using socket authentication or is there a my.cnf
file for user 'olaf'?
For the record, this was uploaded to Debian on May 13th, 2025, and has
been in proposed-updates pocket since June 11th:
https://tracker.debian.org/news/1648653/accepted-mariadb-1101113-0deb12u1-source-into-proposed-updates/
Control: fixed -1 mariadb/1:11.8.2-1
Indeed, this was fixed upstream in previous release and no builds in
Debian ever failed. Closing bug and discarding the patch.
d at
https://salsa.debian.org/otto/policy/-/commits/vcs-example
Hi,
> Ie, the key points
> - The signature shoud be made when importing a new upstream release
Check. The files PACKAGE_UPSTREAMVERSION.{id,xdelta,sig} are added by
pristine-tar in one single commit, at the time of import.
> - The signature should semanntically cover only that the
>informa
1 - 100 of 1372 matches
Mail list logo
