Bug#1036751: RFS: mini-httpd/1.30-4 [ITA] -- Small HTTP server
Greetings again, #1 Changes rejected: mini-httpd_1.30-4.dsc: Invalid size hash for mini- httpd_1.30.orig.tar.gz: According to the control file the size hash should be 43469, but mini-httpd_1.30.orig.tar.gz has 43889. If you did not include mini-httpd_1.30.orig.tar.gz in your upload, a different version might already be known to the archive software. #2 > until you receive the "accepted" email before pushing your tag to > g...@salsa.debian.org:debian/mini-httpd.git, and please push the > master > branch there at your earliest convenience. > Just to recap here: following our previous mail's logic, namely: git clone g...@salsa.debian.org:debian/mini-httpd.git cd mini-httpd git remote add alex g...@salsa.debian.org:alexandru_mihail/mini- httpd.git git fetch alex # just so you have another backup dch -r git commit debian/changelog -m "Release 1.30-4 to unstable." # do your tagging procedure git push --delete alex debian/1.30-4 git push -f alex master debian/1.30-4 This results in: worker@Debian:~/git/mini-httpd$ git diff origin/master..HEAD diff --git a/debian/changelog b/debian/changelog index ad0073c..73a286b 100644 --- a/debian/changelog +++ b/debian/changelog @@ -14,7 +14,7 @@ mini-httpd (1.30-4) unstable; urgency=medium * Clarified NCSA origins of mini-httpd htpasswd* by adding a corresponding copyright entry with proper attribution. - -- Alexandru Mihail Tue, 04 Jul 2023 23:49:19 +0300 + -- Alexandru Mihail Tue, 05 Sep 2023 01:29:43 +0300 mini-httpd (1.30-3) unstable; urgency=medium worker@Debian:~/git/mini-httpd$ git show origin commit 1c8f17316e8f1f787c478e0428cfdd27b5c9ca1b (origin/master, origin/HEAD) Merge: d736d78 acfc103 Author: Nicholas D Steeves <2201-s...@users.noreply.salsa.debian.org> Date: Wed Aug 23 21:50:16 2023 + Merge branch 'master' into 'master' Merge 1.30-4 release from new maintainer See merge request debian/mini-httpd!2 Pushing tag & master would just amount to: git push origin debian/1.30-4 git push ? Going to sleep, looking forward to hearing from you tomorrow (its 3AM here :D) Have a nice $part_of_day ! > Congratulations, and enjoy your holidays! :) > > Cheers, > Nicholas Thank you ! All the best, Alexandru signature.asc Description: This is a digitally signed message part
Bug#1036751: RFS: mini-httpd/1.30-4 [ITA] -- Small HTTP server
Hi Alexandru, Alexandru Mihail writes: >> # Fix git config email and gpg identity, then [snip] >> > I fixed my git config and redid the tag as discussed above Thanks! >> Sorry I only noticed this when I manually inspected and compared the >> tag > Yeah, sorry too :) > I'll be going on vacation for two weeks so I will be available via mail > but won't be able to push unless we coordinate that tomorrow (roughly > 14 Hrs from now would be when I have to leave. If not I'll happily push > afterwards (14th September). > Tag is in the usual spot: > https://salsa.debian.org/alexandru_mihail/mini-httpd/-/tags/debian%2F1.30-4 I just uploaded and sent you an invitation that grants Maintainer permissions for this repository. You will receive two emails from the FTP Masters (Debian archive). The first will be a "processing" email that says the release was uploaded successfully, and the second will be that mini-httpd was accepted into Debian unstable/sid. Please wait until you receive the "accepted" email before pushing your tag to g...@salsa.debian.org:debian/mini-httpd.git, and please push the master branch there at your earliest convenience. Congratulations, and enjoy your holidays! :) Cheers, Nicholas signature.asc Description: PGP signature
Bug#1036751: RFS: mini-httpd/1.30-4 [ITA] -- Small HTTP server
Hello Nicholas, > Did you realise that you're still committing using your protonmail.ch > address (and presumably GPG identity)? Early in this process you > switched to a gmail address, and I understood that that was the one > that > you would be using for for your Debian work. Damn, it seems the web GUI tricked us both..I was convinced I sorted that out (GPG was already O.K but mail was not *sigh*) Many thanks for your attention to detail :D > # Fix git config email and gpg identity, then > git clone g...@salsa.debian.org:debian/mini-httpd.git > cd mini-httpd > git remote add alex g...@salsa.debian.org:alexandru_mihail/mini- > httpd.git > git fetch alex # just so you have another backup > dch -r > git commit debian/changelog -m "Release 1.30-4 to unstable." > # do your tagging procedure > git push --delete alex debian/1.30-4 > git push -f alex master debian/1.30-4 > I fixed my git config and redid the tag as discussed above > Sorry I only noticed this when I manually inspected and compared the > tag Yeah, sorry too :) I'll be going on vacation for two weeks so I will be available via mail but won't be able to push unless we coordinate that tomorrow (roughly 14 Hrs from now would be when I have to leave. If not I'll happily push afterwards (14th September). Tag is in the usual spot: https://salsa.debian.org/alexandru_mihail/mini-httpd/-/tags/debian%2F1.30-4 > Cheers, > Nicholas > Have a great one, Alexandru > P.S. FYI, to get Salsa's Gitlab instance to show green verified > commits > and tags you may also need to update your email address and gpg key > there. I don't care about this so long as the actual git data is > correct, but you (and/or others) might. Did that too, no reason not to :) signature.asc Description: This is a digitally signed message part
Bug#1051125: RFS: a2d/2.0.0-1 [ITP] -- APRS to DAPNET portal
On Sun, 3 Sep 2023 01:50:40 -0400 Yogu NY3W wrote: Changes for the initial release: a2d (2.0.0-1) unstable; urgency=medium You should really file an ITP for this package and reference it in the changelog.
Bug#1036751: RFS: mini-httpd/1.30-4 [ITA] -- Small HTTP server
Hello Alexandru, Thank you for the ping :) Alexandru Mihail writes: > I've commited and pushed the changes to the remote I was using for the > MR so far: > commit: > https://salsa.debian.org/alexandru_mihail/mini-httpd/-/commit/fc7c4f664dc1369b1bf5d46c8c9b7aa11de68407 > > > But I think I may have not commited where I was supposed to, granted > you've already closed the MR. You committed in the right place, and yes, as requested pushed to the remote in your personal namespace rather than to the collaborative space where mini-httpd is maintained. Yes, this is what I asked for, because I wanted to make sure everything was in good order before uploading to the archive and asking you to push to the actual project (thus making it permanent). I'm pulling from your remote directly rather than using the gitlab now. Tags on the actual project are immutable (or should be treated thus), and should only be pushed after an upload has been accepted, and this is why I wanted to check that everything was 100% good. Yes, I had already merged your MR, and MRs are automatically closed when they're merged. > I've already created a GPG signed tag accessible at: > https://salsa.debian.org/alexandru_mihail/mini-httpd/-/tags/debian%2F1.30-4 Thanks! > The commit is not visible in the previous MR: > https://salsa.debian.org/debian/mini-httpd/-/merge_requests/2? This is because the MR was merged already (and thus already closed and not open for updates). > Is there something I've glanced over here ? Did you realise that you're still committing using your protonmail.ch address (and presumably GPG identity)? Early in this process you switched to a gmail address, and I understood that that was the one that you would be using for for your Debian work. You'll need to update your git config to use the new gmail address and gpg identity (try #debian-mentors on irc.oftc.net if you can't make sense of the docs). Also, at this time please base your work on debian/mini-httpd.git rather than alexandru_mihail/mini-httpd.git. # Fix git config email and gpg identity, then git clone g...@salsa.debian.org:debian/mini-httpd.git cd mini-httpd git remote add alex g...@salsa.debian.org:alexandru_mihail/mini-httpd.git git fetch alex # just so you have another backup dch -r git commit debian/changelog -m "Release 1.30-4 to unstable." # do your tagging procedure git push --delete alex debian/1.30-4 git push -f alex master debian/1.30-4 Sorry I only noticed this when I manually inspected and compared the tag and release commit on the CLI...I feel like the web-thing hid this information from me, and that might be confirmation bias, but it seems like the same thing happened to you ;) Cheers, Nicholas P.S. FYI, to get Salsa's Gitlab instance to show green verified commits and tags you may also need to update your email address and gpg key there. I don't care about this so long as the actual git data is correct, but you (and/or others) might. signature.asc Description: PGP signature
Bug#1051188: marked as done (RFS: jimtcl/0.82-4 -- small-footprint implementation of Tcl - shared library)
Your message dated Mon, 04 Sep 2023 15:10:54 -0400 with message-id <7677e1e2678ef4be90e1ceb2b4527e0e73456e48.ca...@debian.org> and subject line Re: RFS: jimtcl/0.82-4 -- small-footprint implementation of Tcl - shared library has caused the Debian Bug report #1051188, regarding RFS: jimtcl/0.82-4 -- small-footprint implementation of Tcl - shared library to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1051188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "jimtcl": * Package name : jimtcl Version : 0.82-4 Upstream contact : [fill in name and email of upstream] * URL : http://jim.tcl.tk/ * License : TCL, BSD-2-clause * Vcs : https://salsa.debian.org/debian/jimtcl Section : devel The source builds the following binary packages: jimsh - small-footprint implementation of Tcl named Jim libjim-dev - small-footprint implementation of Tcl - development files libjim0.82 - small-footprint implementation of Tcl - shared library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/jimtcl/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/j/jimtcl/jimtcl_0.82-4.dsc Changes since the last upload: jimtcl (0.82-4) unstable; urgency=medium . * upload to unstable --->--- The upload is ready for transition to unstable. see #1050987. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050987 -- Regards, -- Bo YU signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Hi, On Mon, 4 Sep 2023 16:48:10 +0800 Bo YU wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "jimtcl": > > * Package name : jimtcl > Version : 0.82-4 > Upstream contact : [fill in name and email of upstream] > * URL : http://jim.tcl.tk/ > * License : TCL, BSD-2-clause > * Vcs : https://salsa.debian.org/debian/jimtcl > Section : devel > > The source builds the following binary packages: > > jimsh - small-footprint implementation of Tcl named Jim > libjim-dev - small-footprint implementation of Tcl - development files > libjim0.82 - small-footprint implementation of Tcl - shared library > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/jimtcl/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x >https://mentors.debian.net/debian/pool/main/j/jimtcl/jimtcl_0.82-4.dsc > > Changes since the last upload: > > jimtcl (0.82-4) unstable; urgency=medium > . > * upload to unstable > > --->--- > The upload is ready for transition to unstable. > see #1050987. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050987 Uploaded. Some comments: * In debian/rules, Please avoid parsing the output of ls. This is non-portable and fragile whenever a space appears in the filename. Using asterisk as shell glob should be good already. * I am wondering why you decided to discard original .so file and do the soft linking by yourself. Ideally we want to enforce dh_missing --fail-missing. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#1051213: RFS: debianutils/5.12 [ITA] -- Miscellaneous utilities specific to Debian
Control: owner -1 ! Ileana Dumitrescu: Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "debianutils": [..] Niels Thykier and I will be co-maintaining this package. I got this. :) Best regards, Niels
Re: Q16 compile for the general CPU, and Illegal instruction
On Mon, Sep 04, 2023 at 10:33:12AM -0400, Tong Sun wrote: > With current cloud-compiling approaches, how should we make sure that > the built package works for the older x86_64 CPUs possible, and especially > about this Q16 compilation for ImageMagick? > > PS, the compilation is done via https://github.com/SoftCreatR/imei/. If it's not related to Debian packaging it shouldn't be on d-mentors@.
Bug#1051213: RFS: debianutils/5.12 [ITA] -- Miscellaneous utilities specific to Debian
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "debianutils": * Package name : debianutils Version : 5.12 Upstream contact : [fill in name and email of upstream] * URL : [fill in URL of upstream's web site] * License : public-domain, GPL-2+, SMAIL-GPL * Vcs : https://salsa.debian.org/debian/debianutils Section : utils The source builds the following binary packages: debianutils - Miscellaneous utilities specific to Debian To access further information about this package, please visit the following URL: https://mentors.debian.net/package/debianutils/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/d/debianutils/debianutils_5.12.dsc Changes since the last upload: debianutils (5.12) unstable; urgency=medium . * d/control: - Add myself as maintainer and Niels Thykier as uploader (Closes: #1050806). - Bump standards version from 4.6.0 to 4.6.2. * d/prerm: Make script executable. * d/postinst: Use 'set -e' in the body of the script. * d/tests/control: Use 'set -e' in the body of the script. * d/source/lintian-overrides: Ignore upstream metadata warning for Debian native package. * ischroot.c: Add missing newline in version output. * ischroot.1: Fix to say detection is possible for exit status 0. Niels Thykier and I will be co-maintaining this package. -- Ileana Dumitrescu GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354 OpenPGP_0x6570EA01146F7354.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Q16 compile for the general CPU, and Illegal instruction
Hi, The ImageMagick has stayed in V6 for too long and I tried to compile its V7 myself to see what the problem might be, and indeed I found a big problem -- I got "Illegal instruction" when I tried to install the built package elsewhere. At first it is almost like *"the built packages cannot be used in other machines, but only to the built machine itself"*, and it took me quite a while to get to the bottom of it. In summary, - I tried to build with two cloud providers, and none of the built packages can be used in my VPS. - I then build in my VPS and the built packages can be used in my VPS (ubuntu:22.04). - however, it cannot be used in my Debian. I now believe the "Illegal instruction" is because of not the distro but the CPU instruction set the compiler decided to use, based on the CPU of the machine. It turns out that my Debian has the oldest CPU and least CPU flags, and the package built there can be used anywhere else. So here comes my question, With current cloud-compiling approaches, how should we make sure that the built package works for the older x86_64 CPUs possible, and especially about this Q16 compilation for ImageMagick? PS, the compilation is done via https://github.com/SoftCreatR/imei/. thanks
Re: Intend to update gnome-authenticator 3.32.2 to 4.3.1
Thanks for the feedback on the blog post, I'll update it. Regarding the last error: there might be a feature you need to patch out or some benchmarks On Mon, 4 Sept 2023, 14:36 Axel Kittenberger, < axel.kittenber...@univie.ac.at> wrote: > Hello thanks for the heads up. > > > In the meantime you can try to get the other missing dependencies for > > authenticator into debian. scrypt, search-provider and aes-gcm seem > > like good starting points. I can recommend reading > > https://blog.hackeriet.no/packaging-a-rust-project-for-debian/ to get > > started. Feel free to ask on the #debian-rust IRC channel on the OFTC > > network if you run into any questions. > > This is getting more out of hand than I expected :) > > Anyway, I tried to go with scrypt: Issues with said instructions I > encounter: > > 1) CHROOT > > It tells me to set CHROOT=unstable-amd64-sbuild but later at 9) it > builds debcargo-unstable-amd64-sbuild I guess it should be rather that? > > 4) ./update.sh crate-name > > yields > > ./update.sh: abort: debcargo not found, run `cargo install debcargo` or > set DEBCARGO to point to it > > fixable by putting in exactly that command (or should rather a matching > debian package be installed?) > > 13) Push your branch to your fork > > Well if I follow the instructions there is no fork. (I registered for > salsa and awaiting approval to create a fork). While I can redirect git > remotes later on, would be more practical to clone the fork right away. > > 10) ./build.sh scrypt > > Gets me this error: > > E: The value 'unstable' is invalid for APT::Default-Release as such a > release is not available in the sources > ./build.sh: abort: couldn't generate dpkg-dummy/status, is Debian > unstable in your APT sources? > > Wait I have to put unstable in /etc/apt/sources.list of the building > system? (Its a trixie VM I thought that would be enough) > > 10) ./build.sh salsa20 (a dependency of scrypt) > > Gets me an error of quilt not been installed (yes fixable with apt > install quilt) > > Fixing that I get: > > error[E0554]: `#![feature]` may not be used on the stable release channel > --> benches/mod.rs:1:12 >| > 1 | #![feature(test)] >| > > So this is from upstream. Honestly I don't understand enough of Rust to > say if the build did something wrong, or upstream ought to fix this. (I > wrote a Rust script as git extension a while ago, but that's about it) > > Kind regards, Axel > > >
Re: Intend to update gnome-authenticator 3.32.2 to 4.3.1
Hello thanks for the heads up. In the meantime you can try to get the other missing dependencies for authenticator into debian. scrypt, search-provider and aes-gcm seem like good starting points. I can recommend reading https://blog.hackeriet.no/packaging-a-rust-project-for-debian/ to get started. Feel free to ask on the #debian-rust IRC channel on the OFTC network if you run into any questions. This is getting more out of hand than I expected :) Anyway, I tried to go with scrypt: Issues with said instructions I encounter: 1) CHROOT It tells me to set CHROOT=unstable-amd64-sbuild but later at 9) it builds debcargo-unstable-amd64-sbuild I guess it should be rather that? 4) ./update.sh crate-name yields ./update.sh: abort: debcargo not found, run `cargo install debcargo` or set DEBCARGO to point to it fixable by putting in exactly that command (or should rather a matching debian package be installed?) 13) Push your branch to your fork Well if I follow the instructions there is no fork. (I registered for salsa and awaiting approval to create a fork). While I can redirect git remotes later on, would be more practical to clone the fork right away. 10) ./build.sh scrypt Gets me this error: E: The value 'unstable' is invalid for APT::Default-Release as such a release is not available in the sources ./build.sh: abort: couldn't generate dpkg-dummy/status, is Debian unstable in your APT sources? Wait I have to put unstable in /etc/apt/sources.list of the building system? (Its a trixie VM I thought that would be enough) 10) ./build.sh salsa20 (a dependency of scrypt) Gets me an error of quilt not been installed (yes fixable with apt install quilt) Fixing that I get: error[E0554]: `#![feature]` may not be used on the stable release channel --> benches/mod.rs:1:12 | 1 | #![feature(test)] | So this is from upstream. Honestly I don't understand enough of Rust to say if the build did something wrong, or upstream ought to fix this. (I wrote a Rust script as git extension a while ago, but that's about it) Kind regards, Axel OpenPGP_0x7AC320FF153B3A9D.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Question about upload
On 04.09.2023 13:30, Preuße, Hilmar wrote: Hi, I signed the package now correctly, the processing E-Mail said: dvisvgm_3.1.1+ds-1.debian.tar.xz has incorrect size; deleting it Do I have to re-upload or remove the "associated files" in any way? The ACCEPTED mail just rolled in. Many thanks! Hilmar -- sigfault OpenPGP_signature Description: OpenPGP digital signature
Re: Question about upload
On 04.09.2023 12:42, Andrey Rakhmatullin wrote: On Mon, Sep 04, 2023 at 12:28:01PM +0200, Preuße, Hilmar wrote: Hi all, I'm trying to upload a new package for dvisvgm[1]. Unfortunately this does not work: the dput command runs fine, but I did not even got the E-Mail that the upload was successful and the package is processed. In the meantime I could upload a new revision of texlive-bin, so there is no general issue with my account. I'm using the upload server "ftp.eu.upload.debian.org". From usper:/srv/upload.debian.org/queued/run/log: Sep 3 22:22:33 processing /dvisvgm_3.1.1+ds-1_source.changes Sep 3 22:22:33 GnuPG signature check failed on dvisvgm_3.1.1+ds-1_source.changes Sep 3 22:22:33 (Exit status 2) Sep 3 22:22:33 /dvisvgm_3.1.1+ds-1_source.changes has bad PGP/GnuPG signature! Sep 3 22:22:33 Removing /dvisvgm_3.1.1+ds-1_source.changes, but keeping its associated files for now. Which is indeed the most frequent cause of "I did not even got the E-Mail". Umm, ooh. I just typed dput, which in turn called debsign to sign the package. Unfortunately it used the wrong key. Not sure why; DEBSIGN_KEYID in ~/.devscripts has the correct value. I signed the package now correctly, the processing E-Mail said: dvisvgm_3.1.1+ds-1.debian.tar.xz has incorrect size; deleting it Do I have to re-upload or remove the "associated files" in any way? Hilmar -- sigfault OpenPGP_signature Description: OpenPGP digital signature
Re: Question about upload
On Mon, Sep 4, 2023 at 6:43 AM Andrey Rakhmatullin wrote: > On Mon, Sep 04, 2023 at 12:28:01PM +0200, Preuße, Hilmar wrote: > > Hi all, > > > > I'm trying to upload a new package for dvisvgm[1]. Unfortunately this > does > > not work: the dput command runs fine, but I did not even got the E-Mail > that > > the upload was successful and the package is processed. > > In the meantime I could upload a new revision of texlive-bin, so there > is no > > general issue with my account. I'm using the upload server > > "ftp.eu.upload.debian.org". > > >From usper:/srv/upload.debian.org/queued/run/log: > > Sep 3 22:22:33 processing /dvisvgm_3.1.1+ds-1_source.changes > Sep 3 22:22:33 GnuPG signature check failed on > dvisvgm_3.1.1+ds-1_source.changes > Sep 3 22:22:33 (Exit status 2) > Sep 3 22:22:33 /dvisvgm_3.1.1+ds-1_source.changes has bad PGP/GnuPG > signature! > "has bad PGP/GnuPG signature!" Did you digitally sign the package? > Sep 3 22:22:33 Removing /dvisvgm_3.1.1+ds-1_source.changes, but keeping > its associated files for now. > The package is removed due to the bad signature. > Which is indeed the most frequent cause of "I did not even got the > E-Mail". > > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
Re: Question about upload
On Mon, Sep 04, 2023 at 12:28:01PM +0200, Preuße, Hilmar wrote: > Hi all, > > I'm trying to upload a new package for dvisvgm[1]. Unfortunately this does > not work: the dput command runs fine, but I did not even got the E-Mail that > the upload was successful and the package is processed. > In the meantime I could upload a new revision of texlive-bin, so there is no > general issue with my account. I'm using the upload server > "ftp.eu.upload.debian.org". >From usper:/srv/upload.debian.org/queued/run/log: Sep 3 22:22:33 processing /dvisvgm_3.1.1+ds-1_source.changes Sep 3 22:22:33 GnuPG signature check failed on dvisvgm_3.1.1+ds-1_source.changes Sep 3 22:22:33 (Exit status 2) Sep 3 22:22:33 /dvisvgm_3.1.1+ds-1_source.changes has bad PGP/GnuPG signature! Sep 3 22:22:33 Removing /dvisvgm_3.1.1+ds-1_source.changes, but keeping its associated files for now. Which is indeed the most frequent cause of "I did not even got the E-Mail".
Question about upload
Hi all, I'm trying to upload a new package for dvisvgm[1]. Unfortunately this does not work: the dput command runs fine, but I did not even got the E-Mail that the upload was successful and the package is processed. In the meantime I could upload a new revision of texlive-bin, so there is no general issue with my account. I'm using the upload server "ftp.eu.upload.debian.org". How should I proceed? Thanks! Hilmar [1] https://tracker.debian.org/pkg/dvisvgm -- sigfault OpenPGP_signature Description: OpenPGP digital signature
Re: Intend to update gnome-authenticator 3.32.2 to 4.3.1
On 04.09.23 00:38, Arnaud Ferraris wrote:
Hi Axel,
Le 01/09/2023 à 13:11, Axel Kittenberger a écrit :
Question 3) Taking the old package as base and after setting up
sbuild modifying it, I currently have following control file:
If fixed this, by taking the rules file from:
https://wiki.debian.org/Gnome/Rust_Packaging
instead of a plain dh file, now I get:
---
[43/46] /usr/bin/env
CARGO_HOME=/<>/obj-x86_64-linux-gnu/cargo-home
/usr/share/cargo/bin/cargo build --manifest-path
/<>/Cargo.toml --target-dir
/<>/obj-x86_64-linux-gnu/src --release && cp
src/release/authenticator src/authenticator
Updating crates.io index
error: failed to get `libadwaita` as a dependency of package
`authenticator v4.3.1 (/<>)`
---
The joke is libadwaita is literally the example on said instruction
page:
> For instance adw = {package = "libadwaita", version = "0.4",
features = ["v1_3"]} translates to librust-libadwaita+v1_3-dev (>=
0.4).
But such package does not exist, not any other package with adwaita
and rust in its name, except librust-sctk-adwaita-dev, but I get from
the description it is "adwaita like" and not adwaita itself?
The libadwaita crate isn't in Debian yet, so very few Rust-based GNOME
apps can be packaged for now. This is being worked on by Matthias
(CC'ed in this mail as I'm not sure he is subscribed to this ML), but
still needs some time before all the required deps make their way into
Debian, IIRC.
Actually I'm working on updating the gtk-rs stack to the latest version
(with regenerated code) and this should enable libadwaita to go through new.
In the meantime, feel free to check whether other required crates are
missing from Debian, and ideally join the Rust team to help packaging
those. You can also join #debian-rust to discuss those matters.
Thanks Arnaud for bringing this to my attention.
Hi Axel, libadwaita has indeed not yet been uploaded to the debian
archive. This is due to some disagreement with ftp-masters, it couldn't
be uploaded for the longest time, but that has been somewhat resolved.
In the meantime you can try to get the other missing dependencies for
authenticator into debian. scrypt, search-provider and aes-gcm seem like
good starting points. I can recommend reading
https://blog.hackeriet.no/packaging-a-rust-project-for-debian/ to get
started. Feel free to ask on the #debian-rust IRC channel on the OFTC
network if you run into any questions.
best,
werdahias
OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
Re: How long should I wait before reposting RFS?
Thanks for for the couple replies I got! On 2023-09-03 08:23, Bo YU wrote: > Hi Antonio！ > > On Sun, Sep 3, 2023 at 2:30 AM Antonio Russo wrote: >> >> Hello, >> >> I opened an ITP-closing RFS bug about a month and a half ago. It's got 0 >> replies. >> > >>From my past experience, It is rare for an RFS to get 0 replies. But > unfortunately, > It's quite possible that when you opened the RFS, there was a flood of > RFS here but > your RFS was buried. > >> Is it OK for me to try to bump this? I would have at least hoped to get >> someone to say >> "I don't think this is fit for debian." before giving up on it. > > I would like to suggest you ping the RFS once a/two week until a DD > picks up your package. > All Debian participants are volunteers, so please relax :) I'll re-post the RFS on a day it looks like the list is quiet. I also got a suggestion to contact related DDs directly. I'll try that as well. > Thanks for your contributions to Debian. > > BR, > Bo Antonio OpenPGP_0xB01C53D5DED4A4EE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1051188: RFS: jimtcl/0.82-4 -- small-footprint implementation of Tcl - shared library
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "jimtcl": * Package name : jimtcl Version : 0.82-4 Upstream contact : [fill in name and email of upstream] * URL : http://jim.tcl.tk/ * License : TCL, BSD-2-clause * Vcs : https://salsa.debian.org/debian/jimtcl Section : devel The source builds the following binary packages: jimsh - small-footprint implementation of Tcl named Jim libjim-dev - small-footprint implementation of Tcl - development files libjim0.82 - small-footprint implementation of Tcl - shared library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/jimtcl/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/j/jimtcl/jimtcl_0.82-4.dsc Changes since the last upload: jimtcl (0.82-4) unstable; urgency=medium . * upload to unstable --->--- The upload is ready for transition to unstable. see #1050987. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050987 -- Regards, -- Bo YU signature.asc Description: PGP signature
