Open Nardol opened 2 years ago
May I suggest to maintain this package in pkg-iot debian team
https://salsa.debian.org/debian-iot-team
I see this file is not sync with debian archive
https://github.com/eclipse/mosquitto/blob/debian/debian/changelog
https://tracker.debian.org/pkg/mosquitto
Cc: @ralight
Bump, I'd like to help to fix:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993400
Feedback welcome
@rzr Thanks for the bump. I'd be very happy for the pkg-iot team to take over maintaining mosquitto in Debian. It doesn't help specifically with providing arm64 support in repo.mosquitto.org, but would definitely take a load off.
Excellent, let me prepare the work, maybe I'll need you and your sponsor to make a last upload as maintainer, let's keep in touch.
Do you have a git history of current package, I didnt see in the public tree:
OLD: VCS is behind the version in the archive: 2.0.8-2 < 2.0.11-1.2.
https://qa.debian.org/cgi-bin/vcswatch?package=mosquitto
Mean Let me try to rebuild the current release using gbp (I'll rebase later)
I don't have the git history, sorry, just the uploaded versions.
Ok no problem I have sorted it out
Please review and let's cooperate at:
https://salsa.debian.org/debian-iot-team/mosquitto/-/merge_requests/1
Meanwhile for ARM64 packages It seems to build:
https://build.opensuse.org/package/show/home:rzrfreefr/mosquitto
I am also reachable as rzr at:
irc://irc.debian.org/#debian-iot
Is it ok for you that I follow the ITS procedure as explained at:
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#package-salvaging
Nitpicking: May I suggest @ralight to export key to suppress this warning:
I: mosquitto source: public-upstream-key-not-minimal has 6 extra signature(s) for keyid 779B22DFB3E717B7 [debian/upstream/signing-key.asc]
N:
N: The package contains a public upstream signing key with extra signatures. The signatures are unnecessary and take up space in the archive.
N:
N: Please export the upstream key again with the command:
N:
N: $ gpg --armor --export --export-options export-minimal,export-clean
N:
N: and use that key instead of the key currently in the source package.
N:
N: Please refer to the uscan(1) manual page for details.
N:
N: Visibility: info
N: Show-Always: no
N: Check: debian/upstream/signing-key
Then I'll pick it from upstream (here) to debian-iot
By the way remaining warnings are:
Now running lintian mosquitto_2.0.15-1_amd64.changes ...
I: mosquitto source: public-upstream-key-not-minimal has 6 extra signature(s) for keyid 779B22DFB3E717B7 [debian/upstream/signing-key.asc]
X: mosquitto: systemd-service-file-missing-hardening-features [lib/systemd/system/mosquitto.service]
X: mosquitto source: very-long-line-length-in-source-file 1881 > 512 [doc/joss-paper/paper.bib:66]
X: mosquitto source: very-long-line-length-in-source-file 701 > 512 [.travis.yml:18]
Finished running lintian.
Let's me jump to this generic issue, and keep this one for specific arm64 debs
Thanks for providing an arm64 package for Debian starting with Bookworm
(Debian 12) in mosquitto.org's repo.
The latest 2 releases 2.0.19 and 2.0.20 are not provided for arm64 but only for amd64/i386 .
The Mosquitto project Debian repository does not provide ARM64 package and official Debian repositories provide a quite outdated version even for Debian testing.
I know #815 was opened and the only solution is to compile from source. But could it be possible to add ARM64 architecture to http://repo.mosquitto.org/debian repositories? Or to update it for Bullseye on Debian itself or if not possible, update it for testing then create a package for bullseye-backports.