Bug#1064605: [Pkg-rust-maintainers] rustup_1.26.0-5_source.changes ACCEPTED into unstable
On Sun, Mar 17, 2024 at 02:11:37PM +0100, Tobias Frost wrote: > Debian FTP Masters > > > > rustup_1.26.0-5.dsc: Refers to non-existing file 'rustup_1.26.0.orig.tar.xz' > > Perhaps you need to include the file in your upload? > > > > If the orig tarball is missing, the -sa flag for dpkg-buildpackage will be > > your friend. > > The problem was the the sponsoree's dsc included a different orig.tar, > (identical in content, but compressed with xz; If I'd had to guess maybe > gbp created that one.) > > I've reuploaded alrady with the one using the one in the archives, so > this should(tm) appear soon. > Yes, it did. - Forwarded message from Debian FTP Masters - Date: Sun, 17 Mar 2024 13:22:35 + From: Debian FTP Masters To: t...@debian.org, Zixing Liu , Debian Rust Maintainers Subject: [Pkg-rust-maintainers] rustup_1.26.0-5_source.changes ACCEPTED into unstable Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 24 Feb 2024 14:34:36 -0700 Source: rustup Architecture: source Version: 1.26.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Zixing Liu Closes: 1064564 Changes: rustup (1.26.0-5) unstable; urgency=medium . * Team upload. * d/debcargo.toml: declare additional conflict packages for: - rust-web-clippy - rustfmt-web - rust-mozilla-gdb - rust-mozilla-lldb - rust-web-gdb - rust-web-lldb ... so that users can correctly install rustup when those packages are present (by replacing them with rustup). (Closes: #1064564) * d/copyright: update copyright years. * d/control: update Conflicts using debcargo. Checksums-Sha1: e45316006bb96cac88f9df90024b9cf364ef2651 4019 rustup_1.26.0-5.dsc 68b311c6b0f2eae7fdaf1e9eed88ca86d2a92ba8 16984 rustup_1.26.0-5.debian.tar.xz 3533c0a2edbc169d33fc21c26c51b0c01018d94c 24868 rustup_1.26.0-5_amd64.buildinfo Checksums-Sha256: d65d71a09983e527a230711cf806cc3b5bce107c7bc34ec374070a2079155520 4019 rustup_1.26.0-5.dsc 799739439acccd871a2bf87a6f0ffb8bd6abd8514aa11d5c2a33ce14e50f9b66 16984 rustup_1.26.0-5.debian.tar.xz 18e8e8cfc5a92d468d4b8845c863e7a92583b9c84036fc69e317841dfb6dd969 24868 rustup_1.26.0-5_amd64.buildinfo Files: 3fa90be920ca43511b0ec6911456924b 4019 rust optional rustup_1.26.0-5.dsc 5077ba37f31ce8f96a41be7aa1e6a5db 16984 rust optional rustup_1.26.0-5.debian.tar.xz 5d61d24cbeb4c2da8cc77d4c3faba955 24868 rust optional rustup_1.26.0-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmX26Y8ACgkQkWT6HRe9 XTa1eBAAyU6GRradzzHpQMFSaJvxdAVX7Doxy3LGLrb8JD4pZPsgOZnjLw99tXMX hX8h1Q8/psSWci7ZC7uUf1pI3D7DNgMoOWDe5jcghqmc8m/CnKvq6DsGakKG/6Zb s+0A67Ah2ML6hmVnQ60LiRlsxADnw2b4YBqyX1+Y9Ifa4ubnHwBxGczwgKw9eFF2 3N12QkZUZKRi9A+CMgckvz8F8gkptLQQDkULDarNXg8PjZ3/qVu4MbGTzh7WjWn5 B9ws0cCd6b4NiKlhI/yq5DrcJx62ar9fJKQwZa9w+4lchqdAkkHn7CcZ9cElOyYJ ntGL+RFQCGP1+NE+jWEU5OIqBWBzxmv6g1xUl8ioDGf3dvvWyV/zCsiJItn81KNI +237ttrrzhHgUc63zHtxBqeffDj8J8uAD5NQFxXcDExlA6NDjOnmY/uq0Pea24dY IwEomAcYcbs/qvTEY0QukkaggwDwAuy5OslxupXJ/yJrDy9TF6NrgGLoTzMnWFJL j0tEApieKOPQxjoDU1xCqDrbDzkL09otJ0RC+Da117GUwacG6+86qyoNKshmjfYI 6awgteCl9LlTv/jXraTP6S8b3Z9M1NZZFQtBnapV5N5cNiZI+b8iJ0/2al3afIqL J4GTuj4S4g8Qlc+tMaiUxvQujV9agVLdzl1YE+sb7mE33Gxz1BI= =HpE8 -END PGP SIGNATURE- ___ Pkg-rust-maintainers mailing list pkg-rust-maintain...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers - End forwarded message - Thanks! Groeten Geert Stappers -- Silence is hard to parse
Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions
Control: tags -1 moreinfo On Sun, Mar 17, 2024 at 04:57:54PM +0100, Jörg Frings-Fürst wrote: > tags 1065193 - moreinfo > thanks > > Hi Tobias, > > > > Am Sonntag, dem 17.03.2024 um 14:39 +0100 schrieb Tobias Frost: > > Hi Jörg, > > > > "debcheckout libhx" still gives me 4.17-1 as head. > > > > After looking at your repo, I think I should point you to DEP-14 > > as a recommended git layout for packaging. > > As the branch name indicates you are using per-package-revision > > branches: > > IMHO It makes little sense to have one branch per debian package > > version/revision; (I had a similiar discussion on vzlogger lately, > > so to avoid repetiions: #1064344#28) > > > > Please clarify how you want to manage the package in git, as > > this needs to be reflected in d/control's VCS-* fields correctly. > > (this is now blocking the upload.) > > I have been using Vincent Driessen's branching model and the corresponding git > extension gitflow-avh for at least 7 years with Debian and for a long time at > work. > > The default branch is master and development takes place in the develop > branch. > > The release candidates are managed in the branch release. The extension > debian/debian-version is used as a tag during the transfer. > > The master branch always contains the last published executable version to > which > the git tag in debian/control points. > a> The procedure is described in the README.debian. ok, won't further argue about how to organize your git repo, but I can only tell the Debian perspective: It is breaking expectations as a debcheckout libhx does today NOT give me a state that represents the package in unstable. VCS-Git specifies where the (package) development is happening [1]. [1] Policy 5.6.26 But as I am not using the git repo as base for the sponsoring, lets put that topic to rest. > > > > (The current fields say the package is maintained in the default branch > > of your repo. I see a debian/ directory there, but that one is missing > > released (it is at 4.17-1, while unstable is at 4.19-1.1) > > > > The review is based on the .dsc, timestamped on mentors.d.n > > 2024-03-17 12:00 > > > > d/changelog is *STILL* changing history for the 4.19-1 changelog > > block. (This issue must be fixed before upload.) > > > > I think these were artifacts because my changes to the NMU were not adopted. > Has > been corrected. No it has not. I expect old changelog entries to be *identical* to the ones that have been uploaded, and they still are not, so I fear we are talking past each other. Please let me know what you think that you have fixed, so that we can spot the different expectations. For my perspective: This is the diff from debian/changelog from the current version in the archives and the dsc uploaded to mentors at 2024-03-17 14:45 You are still rewriting history (second hunk of this diff), this hunk should not exists. diff -Naur archive/libhx-4.19/debian/changelog mentors/libhx-4.23/debian/changelog --- archive/libhx-4.19/debian/changelog 2024-02-28 13:48:09.0 +0100 +++ mentors/libhx-4.23/debian/changelog 2024-03-17 15:23:31.0 +0100 @@ -1,3 +1,17 @@ +libhx (4.23-1) unstable; urgency=medium + + * New upstream release (Closes: #1064734). + * Add debian/.gitignore + * Remove not longer needed debian/libhx-dev.lintian-overrides. + * Fix debian/libhx32t64.lintian-overrides. + * debian/copyright: +- Add 2024 to myself. + * debian/control: +- Readd BD dpkg-dev (>= 1.22.5). + Thanks to Tobias Frost + + -- Jörg Frings-Fürst Sun, 17 Mar 2024 15:23:31 +0100 + libhx (4.19-1.1) unstable; urgency=medium * Non-maintainer upload. @@ -9,11 +23,8 @@ * New upstream release. - Refresh symbols files. - * Remove empty debian/libhx-dev.symbols. - * debian/rules: -- Remove build of libhx-dev.symbols. - -- Jörg Frings-Fürst Sun, 17 Dec 2023 14:44:39 +0100 + -- Jörg Frings-Fürst Tue, 21 Nov 2023 10:41:07 +0100 libhx (4.14-1) unstable; urgency=medium
Moving my packages to the debian namespace on salsa?
Hi, I was reading the discussion [1]"Question about the debian group on Salsa" because I wondered that myself for some time. Actually since my package [2]ssh-tools was moved into the debian namespace a while ago. I have no issue if my [3]other packages are moved there as well if that is considered best practice. What do I have to do for moving my packages into the debian namespace? [1] https://lists.debian.org/debian-mentors/2024/03/msg00021.html [2] https://salsa.debian.org/debian/ssh-tools [3] https://salsa.debian.org/users/swick/projects
Bug#1067048: RFS: cxxopts/3.2.1-1 [ITA] -- Lightweight C++ option parser library
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "cxxopts": * Package name : cxxopts Version : 3.2.1-1 Upstream contact : [fill in name and email of upstream] * URL : https://github.com/jarro2783/cxxopts * License : Expat, Boost-1.0 * Vcs : https://salsa.debian.org/debian/cxxopts Section : libs The source builds the following binary packages: libcxxopts-dev - Lightweight C++ option parser library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/cxxopts/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/c/cxxopts/cxxopts_3.2.1-1.dsc Changes since the last upload: cxxopts (3.2.1-1) unstable; urgency=medium . * New upstream version 3.2.1 * New maintainer (Closes: #1065748) * d/copyright: + Update copyright years + Add new maintainer to copyright * d/control: + Replace deprecated build-dep pkg-config with pkgconf + Add new maintainer to maintainer field * d/p/0001-install-pkgconfig-file-into-arch-indep-usr-share-pkg.patch: + Add Forwarded info to patch header Regards, -- Shriram Ravindranathan OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions
tags 1065193 - moreinfo thanks Hi Tobias, Am Sonntag, dem 17.03.2024 um 14:39 +0100 schrieb Tobias Frost: > Hi Jörg, > > "debcheckout libhx" still gives me 4.17-1 as head. > > After looking at your repo, I think I should point you to DEP-14 > as a recommended git layout for packaging. > As the branch name indicates you are using per-package-revision > branches: > IMHO It makes little sense to have one branch per debian package > version/revision; (I had a similiar discussion on vzlogger lately, > so to avoid repetiions: #1064344#28) > > Please clarify how you want to manage the package in git, as > this needs to be reflected in d/control's VCS-* fields correctly. > (this is now blocking the upload.) I have been using Vincent Driessen's branching model and the corresponding git extension gitflow-avh for at least 7 years with Debian and for a long time at work. The default branch is master and development takes place in the develop branch. The release candidates are managed in the branch release. The extension debian/debian-version is used as a tag during the transfer. The master branch always contains the last published executable version to which the git tag in debian/control points. The procedure is described in the README.debian. > > (The current fields say the package is maintained in the default branch > of your repo. I see a debian/ directory there, but that one is missing > released (it is at 4.17-1, while unstable is at 4.19-1.1) > > The review is based on the .dsc, timestamped on mentors.d.n > 2024-03-17 12:00 > > d/changelog is *STILL* changing history for the 4.19-1 changelog > block. (This issue must be fixed before upload.) > I think these were artifacts because my changes to the NMU were not adopted. Has been corrected. > Thanks for re-adding the B-D on dpkg-dev. > > > So, please elaborate on the git issue (so that the correct VCS-* can be > confirmed or specified) , and fix the rewriting history part, and I'll upload > > Remove the moreinfo tag when ready. > > Cheers, > -- > tobi > [...] CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Jörg Frings-Fürst D-54470 Lieser git: https://git.jff.email/cgit/ Skype:jff-skype@jff.email Jami: joergfringsfuerst Telegram: @joergfringsfuerst Matrix: @joergff:matrix.snct-gmbh.de My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Aw: Re: How to name a similiar package?
> Are the new tools replacements or additional? Additional > then ssh-tools-extra would make sense That's actually a good suggestion. Thank you > I don't see why adding a 3rd language > to the 2 already used makes things 'hard to package' The scripts are written with minimal dependency and tested with different OSes. So they are easy to package. Adding the Go ones I have some difficulties myself already: - 3rd party dependencies (which are packaged already luckily) - I am not yet familiar with packaging Go programs (just managed to create one yesterday) - I am not sure if that mixed package should then go to the [1] Go Packaging Team, and when, if they are OK with that mix of languages: So, yeah maybe after I have worked out these things, it is not that difficult anymore and actually I would also prefer to keep all in one upstream repo. I also don't want to make it any harder to package for [2]others [1] https://go-team.pages.debian.net [2] https://repology.org/project/ssh-tools/versions
Bug#1067037: RFS: batsignal/1.8.0-1 -- Lightweight battery daemon written in C
Control: tags -1 moreinfo Hi itd, (Policy requires that the "Maintainer" has "their correct name and a working email address", see Policy §3.3. I know that there are exceptions, but I'm not sure about the conditions they require (for DMs/DDs, at least DAM needs to know your name, but I don't know the rules for Debian Contributors. Due to that, I will not sponsor this package, but I can certainly review the package.) On Sun, Mar 17, 2024 at 12:17:52PM +0100, itd wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "batsignal": > > * Package name : batsignal >Version : 1.8.0-1 >Upstream contact : https://github.com/electrickite/batsignal > * URL : https://github.com/electrickite/batsignal > * License : ISC > * Vcs : https://salsa.debian.org/itd/batsignal >Section : utils > > The source builds the following binary packages: > > batsignal - Lightweight battery daemon written in C > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/batsignal/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/b/batsignal/batsignal_1.8.0-1.dsc > > Changes for the initial release: > > batsignal (1.8.0-1) unstable; urgency=medium > . >* Initial release. Inital releases needs an ITP bug. Please file one and add the appropiate Closes: # stanca. > I would like to move the Vcs to /debian/batsignal, whenever that is > convenient. Let me know your salsa username and I'll make that happen. A short, possibly incomplete review: - d/copyright: I suggest to have the same license for debian/* as for upstream, as this eases forwarding patches etc. Though ISC is considered by the FSF to be compatible with the GPL, this is likely fine too to keep it at is is. - d/watch / this dsc uscan download this: c8c2a048f4aa105aae389d9d765b76057d4998dbfc29a7dfeaf66351eaa7cba1 batsignal_1.8.0.orig.tar.gz your dsc contains: d02e5c821d41e72c30d00bb88759287f9b74225e1217158e5e59f11ba03d5a5b batsignal_1.8.0.orig.tar.xz when constructing your dsc, please make sure to use the same file as uscan would produce. (I've verified that the content of both orig files is identical) Package looks good, otherwise. Make sure to remove the moreinfo tag when the above issues are fixed. Cheers, -- tobi > Regards, > -- itd >
Re: How to name a similiar package?
On 2024-03-17 14:09 +0100, Sven Wick wrote: > Hi, > > I maintain the package **ssh-tools** > and upstream as well. > These are a mix of Bash and Perl scripts. > > Recently I do more stuff with Go > and have new tools written in Go > and don't want to mix them with the Bash and Perl Scripts > because that would be difficult to package (also for other Distros and OSes). > Currently it's ssh-toolz (with a "z") > since I found examples like **python3-toolz**. > But I also thought about ssh-tools2 sind there is **wget2**. > > Any suggestion what the best practice is to name similar packages? Are the new tools replacements or additional? I don't see why adding a 3rd language to the 2 already used makes things 'hard to package', but obviously if you want to have a separate upstream repository (e.g. because you want to supesede the old repository eventually) then that's up to you as upstream. > I am not sure how to name the new tools upstream repo > and therefore the package name. If the new stuff is intended to be a replacement then ssh-tools2 or ssh-tools-ng (for 'next generation') are typical patterns. If they are just more tools then ssh-tools-extra would make sense, or just keep them all in one package/repo as 'ssh-tools' which I think users would like best. ssh-toolz is fine as a name, but obviously users will have no idea what the difference between ssh-tools and ssh-toolz is, so at least be very clear in the long description, and give a clue in the short one if possible. And thanks for thinking about it before it's too late to fix. Names that are clear to users are definitely helpful. Wookey -- Principal hats: Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions
Hi Jörg, "debcheckout libhx" still gives me 4.17-1 as head. After looking at your repo, I think I should point you to DEP-14 as a recommended git layout for packaging. As the branch name indicates you are using per-package-revision branches: IMHO It makes little sense to have one branch per debian package version/revision; (I had a similiar discussion on vzlogger lately, so to avoid repetiions: #1064344#28) Please clarify how you want to manage the package in git, as this needs to be reflected in d/control's VCS-* fields correctly. (this is now blocking the upload.) (The current fields say the package is maintained in the default branch of your repo. I see a debian/ directory there, but that one is missing released (it is at 4.17-1, while unstable is at 4.19-1.1) The review is based on the .dsc, timestamped on mentors.d.n 2024-03-17 12:00 d/changelog is *STILL* changing history for the 4.19-1 changelog block. (This issue must be fixed before upload.) Thanks for re-adding the B-D on dpkg-dev. So, please elaborate on the git issue (so that the correct VCS-* can be confirmed or specified) , and fix the rewriting history part, and I'll upload Remove the moreinfo tag when ready. Cheers, -- tobi On Sun, Mar 17, 2024 at 01:48:57PM +0100, Jörg Frings-Fürst wrote: > Hello Tobias, > > thanks for your review. > > > Am Donnerstag, dem 14.03.2024 um 17:53 +0100 schrieb Tobias Frost: > > Control: tags -1 moreinfo > > > > Hi Jörg, > > > > d/copyright: > > you are changing history: > > > > diff -Naur archive/libhx-4.19/debian/changelog > > new/libhx-4.23/debian/changelog > > (...) > > * debian/rules: > > - Remove build of libhx-dev.symbols. > > > > - -- Jörg Frings-Fürst Sun, 17 Dec 2023 14:44:39 +0100 > > + -- Jörg Frings-Fürst Tue, 21 Nov 2023 10:41:07 +0100 > > > > libhx (4.14-1) unstable; urgency=medium > > > > - you git repository seems to missing commits. a debcheckout libhx > > gives me 4.17-1 in d/changelog. > > Sorry, that's my mistake. > > > > > - please don't drop the Build-Depends: dpkg-dev (>= 1.22.5), the > > time_t transition requires it, > > > > Ok. I have add it. > > > -- > > tobi > > > > CU > Jörg > > -- > New: > GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D > GPG key (long) : 09F89F3C8CA1D25D > GPG Key: 8CA1D25D > CAcert Key S/N : 0E:D4:56 > > > Jörg Frings-Fürst > D-54470 Lieser > > > git: https://git.jff.email/cgit/ > > Skype:jff-skype@jff.email > Jami: joergfringsfuerst > Telegram: @joergfringsfuerst > Matrix: @joergff:matrix.snct-gmbh.de > > My wish list: > - Please send me a picture from the nature at your home. > > > >
Bug#1064605: [ftpmas...@ftp-master.debian.org: [Pkg-rust-maintainers] rustup_1.26.0-5_source.changes REJECTED]
On Sun, Mar 17, 2024 at 01:46:39PM +0100, Geert Stappers wrote: > > Hi, > > > In an attempt to express my appreciation for working rustup in Debian, > this forwarded message. > > - Forwarded message from Debian FTP Masters - > > Date: Sun, 17 Mar 2024 11:32:47 + > From: Debian FTP Masters > To: Debian Rust Maintainers , > t...@debian.org, Zixing Liu > Subject: [Pkg-rust-maintainers] rustup_1.26.0-5_source.changes REJECTED > > > > rustup_1.26.0-5.dsc: Refers to non-existing file 'rustup_1.26.0.orig.tar.xz' > Perhaps you need to include the file in your upload? > > If the orig tarball is missing, the -sa flag for dpkg-buildpackage will be > your friend. The problem was the the sponsoree's dsc included a different orig.tar, (identical in content, but compressed with xz; If I'd had to guess maybe gbp created that one.) I've reuploaded alrady with the one using the one in the archives, so this should(tm) appear soon. > > === > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > > > > ___ > Pkg-rust-maintainers mailing list > pkg-rust-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers > > > - End forwarded message - > > > > > Regards > Geert Stappers > Should be working on making it possible to be ready > for the next RFS for rustup > -- > Silence is hard to parse >
How to name a similiar package?
Hi, I maintain the package **ssh-tools** and upstream as well. These are a mix of Bash and Perl scripts. Recently I do more stuff with Go and have new tools written in Go and don't want to mix them with the Bash and Perl Scripts because that would be difficult to package (also for other Distros and OSes). I am not sure how to name the new tools upstream repo and therefore the package name. Currently it's ssh-toolz (with a "z") since I found examples like **python3-toolz**. But I also thought about ssh-tools2 sind there is **wget2**. Any suggestion what the best practice is to name similar packages?
Bug#1065193: RFS: libhx/4.23-1 [RC] -- C library providing queue, tree, I/O and utility functions
Hello Tobias, thanks for your review. Am Donnerstag, dem 14.03.2024 um 17:53 +0100 schrieb Tobias Frost: > Control: tags -1 moreinfo > > Hi Jörg, > > d/copyright: > you are changing history: > > diff -Naur archive/libhx-4.19/debian/changelog new/libhx-4.23/debian/changelog > (...) > * debian/rules: > - Remove build of libhx-dev.symbols. > > - -- Jörg Frings-Fürst Sun, 17 Dec 2023 14:44:39 +0100 > + -- Jörg Frings-Fürst Tue, 21 Nov 2023 10:41:07 +0100 > > libhx (4.14-1) unstable; urgency=medium > > - you git repository seems to missing commits. a debcheckout libhx > gives me 4.17-1 in d/changelog. Sorry, that's my mistake. > > - please don't drop the Build-Depends: dpkg-dev (>= 1.22.5), the > time_t transition requires it, > Ok. I have add it. > -- > tobi > CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Jörg Frings-Fürst D-54470 Lieser git: https://git.jff.email/cgit/ Skype:jff-skype@jff.email Jami: joergfringsfuerst Telegram: @joergfringsfuerst Matrix: @joergff:matrix.snct-gmbh.de My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Bug#1064605: [ftpmas...@ftp-master.debian.org: [Pkg-rust-maintainers] rustup_1.26.0-5_source.changes REJECTED]
Hi, In an attempt to express my appreciation for working rustup in Debian, this forwarded message. - Forwarded message from Debian FTP Masters - Date: Sun, 17 Mar 2024 11:32:47 + From: Debian FTP Masters To: Debian Rust Maintainers , t...@debian.org, Zixing Liu Subject: [Pkg-rust-maintainers] rustup_1.26.0-5_source.changes REJECTED rustup_1.26.0-5.dsc: Refers to non-existing file 'rustup_1.26.0.orig.tar.xz' Perhaps you need to include the file in your upload? If the orig tarball is missing, the -sa flag for dpkg-buildpackage will be your friend. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. ___ Pkg-rust-maintainers mailing list pkg-rust-maintain...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers - End forwarded message - Regards Geert Stappers Should be working on making it possible to be ready for the next RFS for rustup -- Silence is hard to parse
Bug#1067037: RFS: batsignal/1.8.0-1 -- Lightweight battery daemon written in C
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "batsignal": * Package name : batsignal Version : 1.8.0-1 Upstream contact : https://github.com/electrickite/batsignal * URL : https://github.com/electrickite/batsignal * License : ISC * Vcs : https://salsa.debian.org/itd/batsignal Section : utils The source builds the following binary packages: batsignal - Lightweight battery daemon written in C To access further information about this package, please visit the following URL: https://mentors.debian.net/package/batsignal/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/b/batsignal/batsignal_1.8.0-1.dsc Changes for the initial release: batsignal (1.8.0-1) unstable; urgency=medium . * Initial release. I would like to move the Vcs to /debian/batsignal, whenever that is convenient. Regards, -- itd
Bug#1067038: RFS: notifymuch/0.1~git20151223.0.9d4aaf5-1 -- Display desktop notifications for unread mail in notmuch database
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "notifymuch": * Package name : notifymuch Version : 0.1~git20151223.0.9d4aaf5-1 Upstream contact : https://github.com/kspi/notifymuch/ * URL : https://github.com/kspi/notifymuch/ * License : GPL-3 * Vcs : https://salsa.debian.org/itd/notifymuch Section : utils The source builds the following binary packages: notifymuch - Display desktop notifications for unread mail in notmuch database To access further information about this package, please visit the following URL: https://mentors.debian.net/package/notifymuch/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/n/notifymuch/notifymuch_0.1~git20151223.0.9d4aaf5-1.dsc Changes for the initial release: notifymuch (0.1~git20151223.0.9d4aaf5-1) unstable; urgency=medium . * Initial release. I would like to move the Vcs to /debian/notifymuch, whenever that is convenient. Regards, itd
Bug#1067036: RFS: ii/2.0-1 -- minimalist FIFO and filesystem-based IRC client
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ii": * Package name : ii Version : 2.0-1 Upstream contact : https://suckless.org/community/ * URL : https://tools.suckless.org/ii/ * License : MIT/X-Consortium-License * Vcs : https://salsa.debian.org/debian/ii Section : net The source builds the following binary packages: ii - minimalist FIFO and filesystem-based IRC client To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ii/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/i/ii/ii_2.0-1.dsc Changes since the last upload: ii (2.0-1) unstable; urgency=medium . * New upstream version 2.0 Regards, -- itd
Bug#1065197: RFS: cevomapgen/31-1 [ITP] -- External Map Generator for C-Evo
Control: tags -1 moreinfo Hi Peter, (There was also #1040494, which seems not to have been sponsored. In this case, please reopen the old RFS bug and don't file new bugs.) Here's a very short review, (including copyright review) - lintian: - Comments should be directly over the overriden tag, otherwise the override justification is not correctly picked up - O: cevomapgen: no-manual-page [usr/games/cevomapgen] I disagree this should be overriden, and I disagree that gui programs don't need a manpage. - d/copyright I see that there are files with years from 1999-2023 and one 2024. Please review your d/copyright file and record the years correctly. -- tobi On Fri, Mar 01, 2024 at 07:53:12PM +, Peter Blackman wrote: > Package: sponsorship-requests > Severity: wishlist > > Dear mentors, > > I am looking for a sponsor for my package "cevomapgen": > > * Package name : cevomapgen > Version : 31-1 > Upstream contact : Peter Blackman > * URL : https://sourceforge.net/projects/cevomapgen/ > * License : GPL-3+ > * Vcs : https://salsa.debian.org/PeterB/cevomapgen > Section : games > > The source builds the following binary packages: > > cevomapgen - External Map Generator for C-Evo > > > cevomapgen is a tool for use with c-evo-dh > https://tracker.debian.org/pkg/c-evo-dh > a strategy game with some similarities to Freeciv > > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/cevomapgen/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/c/cevomapgen/cevomapgen_31-1.dsc > > Changes for the initial release: > > cevomapgen (31-1) unstable; urgency=medium > . > * Initial release (Closes: #1035747) > > Regards, > -- > Peter Blackman >
Bug#1065197: RFS: cevomapgen/31-1 [ITP] -- External Map Generator for C-Evo
> The source builds the following binary packages: > > cevomapgen - External Map Generator for C-Evo > > cevomapgen is a tool for use with c-evo-dh > https://tracker.debian.org/pkg/c-evo-dh Would it make sense to call it also c-evo-mapgen, to use the same scheme as the game package?
Bug#1065682: RFS: c-evo-dh/1.11-1 -- Empire Building Game (data files), C-evo: Distant Horizon
Control: tags -1 moreinfo Hi Peter, Some review - source packages do not have a Description: field, only binary packages. - note that changing previous d/changelog entries should be only done in rare circumtances, for example annotating CVEs to earlier uploads, not known then. I don't see the necassity for that history rewriting here, so please don't do that. Additional confusion can arise, if you change the timestamp of historical changelog entries. Don't do that either. Please revert those changes. Cheers, -- tobi On Fri, Mar 08, 2024 at 08:58:59PM +, Peter B wrote: > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "c-evo-dh": > > * Package name : c-evo-dh > Version : 1.11-1 > Upstream contact : Peter > * URL : https://sourceforge.net/projects/c-evo-eh/ > * License : CC0-1.0, GPL-2+, CC-BY-SA-3.0-US, CC-BY-3.0 > * Vcs : https://salsa.debian.org/PeterB/c-evo-dh > Section : games > > The source builds the following binary packages: > > c-evo-dh-gtk2 - Empire Building Game (GTK2), C-evo: Distant Horizon > c-evo-dh-stdai - Empire Building Game (AI module), C-evo: Distant Horizon > c-evo-dh-data - Empire Building Game (data files), C-evo: Distant Horizon > > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/c-evo-dh/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/c/c-evo-dh/c-evo-dh_1.11-1.dsc > > > Changes since the last upload: > > c-evo-dh (1.11-1) unstable; urgency=medium > . > * New Upstream Release > * Missing change in changlog for (1.10-1) > * Update d/copyright date > * Drop lintian override on missing man page for libexec binary > * Add source package description in d/control > * Strip trailing whitespace from d/c-evo-dh-gtk2.install > > Regards, > -- > Peter Blackman >
Bug#1066079: RFS: ddclient/3.11.2-1 -- address updating utility for dynamic DNS services
Control: tags -1 moreinfo Hi Richard, On Tue, Mar 12, 2024 at 12:52:09AM -0700, Richard Hansen wrote: > * Package name : ddclient >Version : 3.11.2-1 >Upstream contact : https://github.com/ddclient/ddclient > * URL : https://ddclient.net > * License : GPL-2.0+, Artistic or GPL-1+, Apache-2.0 > * Vcs : https://salsa.debian.org/debian/ddclient >Section : net > > > ddclient (3.11.2-1) unstable; urgency=medium > . >* Add curl build dependency to enable the -curl argument >* Suggest curl The package now "Depends" on curl, not "Suggests" it. As this conflicts with the d/ch entry, can you clarify? >* Bump Standards-Version to 4.6.2 (no changes needed) >* gbp.conf: Rename branches and tags to match current convention >* gbp.conf: Set upstream-vcs-tag (for import-orig) >* New upstream version 3.11.2 >* Refresh patches >* Update dependencies >* Use dh_installchangelogs to install ChangeLog.md >* debian/copyright: Set Upstream-Contact to project URL >* debian/copyright: Update copyright year for debian/* There are more changes, undocumented, like droping some B-Ds. Please expand on the "why" a change is made over the "what", as this helps reviewing. > Regards, -- Cheers, tobi
Bug#1064605: marked as done (RFS: rustup/1.26.0-5 [RC] [Team] -- The Rust toolchain installer)
Your message dated Sun, 17 Mar 2024 10:57:04 +0100 with message-id and subject line Re: Bug#1064605: RFS: rustup/1.26.0-5 [RC] [Team] -- The Rust toolchain installer has caused the Debian Bug report #1064605, regarding RFS: rustup/1.26.0-5 [RC] [Team] -- The Rust toolchain installer 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.) -- 1064605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important X-Debbugs-Cc: zixing@canonical.com Dear mentors, I am looking for a sponsor for my package "rustup": * Package name : rustup Version : 1.26.0-5 Upstream contact : Daniel Silverstone * URL : https://github.com/rust-lang/rustup * License : MIT or Apache-2.0, OFL-1.1-RFN * Vcs : https://salsa.debian.org/rust-team/rustup Section : rust The source builds the following binary packages: librust-rustup-dev - Manage multiple rust installations with ease - Rust source code rustup - The Rust toolchain installer To access further information about this package, please visit the following URL: https://mentors.debian.net/package/rustup/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/r/rustup/rustup_1.26.0-5.dsc Changes since the last upload: rustup (1.26.0-5) unstable; urgency=medium . * Team upload. * d/debcargo.toml: declare additional conflict packages for: - rust-web-clippy - rustfmt-web - rust-mozilla-gdb - rust-mozilla-lldb - rust-web-gdb - rust-web-lldb ... so that users can correctly install rustup when those packages are present (by replacing them with rustup). (Closes: #1064564) * d/copyright: update copyright years. * d/control: update Conflicts using debcargo. Regards, -- Zixing Liu --- End Message --- --- Begin Message --- Hi Zixing Liu, uploaded so that the RC bugs are fixed. Said that, please look at those lintian tags and see if you can fix, for example: W: rustup: description-synopsis-starts-with-article W: librust-rustup-dev: embedded-javascript-library please use libjs-normalize [usr/share/cargo/registry/rustup-1.26.0/www/normalize.css] Manpages would also be nice to have… There are also a lot of "I: package-contains-documentation-outside-usr-share-doc" tags, does the docu handling need polishing? -- Cheers, tobi On Sat, Feb 24, 2024 at 03:45:23PM -0700, Zixing Liu wrote: > Package: sponsorship-requests > Severity: important > X-Debbugs-Cc: zixing@canonical.com > > Dear mentors, > > I am looking for a sponsor for my package "rustup": > > * Package name : rustup >Version : 1.26.0-5 >Upstream contact : Daniel Silverstone > * URL : https://github.com/rust-lang/rustup > * License : MIT or Apache-2.0, OFL-1.1-RFN > * Vcs : https://salsa.debian.org/rust-team/rustup >Section : rust > > The source builds the following binary packages: > > librust-rustup-dev - Manage multiple rust installations with ease - Rust > source code > rustup - The Rust toolchain installer > > To access further information about this package, please visit the following > URL: > > https://mentors.debian.net/package/rustup/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/r/rustup/rustup_1.26.0-5.dsc > > Changes since the last upload: > > rustup (1.26.0-5) unstable; urgency=medium > . >* Team upload. >* d/debcargo.toml: declare additional conflict packages for: > - rust-web-clippy > - rustfmt-web > - rust-mozilla-gdb > - rust-mozilla-lldb > - rust-web-gdb > - rust-web-lldb > ... so that users can correctly install rustup when those packages are > present (by replacing them with rustup). (Closes: #1064564) >* d/copyright: update copyright years. >* d/control: update Conflicts using debcargo. > > Regards, > -- > Zixing Liu > --- End Message ---
Bug#1065442: marked as done (RFS: shaderc/2023.8-1 [RC] -- Library API for accessing glslc functionality - shared libraries)
Your message dated Sun, 17 Mar 2024 10:26:48 +0100 with message-id and subject line Re: Bug#1065442: RFS: shaderc/2023.8-1 [RC] -- Library API for accessing glslc functionality - shared libraries has caused the Debian Bug report #1065442, regarding RFS: shaderc/2023.8-1 [RC] -- Library API for accessing glslc functionality - shared libraries 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.) -- 1065442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "shaderc": * Package name : shaderc Version : 2023.8-1 Upstream contact : David Neto * URL : https://github.com/google/shaderc/ * License : Apache-2.0, BSD-3-clause * Vcs : https://salsa.debian.org/debian/shaderc Section : libs The source builds the following binary packages: glslc - Command line compiler for GLSL/HLSL to SPIR-V libshaderc-dev - Library API for accessing glslc functionality - static libraries and headers libshaderc1 - Library API for accessing glslc functionality - shared libraries To access further information about this package, please visit the following URL: https://mentors.debian.net/package/shaderc/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/s/shaderc/shaderc_2023.8-1.dsc Changes since the last upload: shaderc (2023.8-1) unstable; urgency=medium . * New upstream release - Refresh patches - Add patch to fix name of Python interpreter - Fix FTBFS (Closes: #1058397) - Refresh d/glslc.lintian-overrides * Fix linking of libshaderc.so, add autopkgtest (Closes: #1029939) * Add obj-x86_64-linux-gnu to d/clean * Use printf instead of echo to generate build-version.inc. Thanks to Vagrant Cascadian! (Closes: #1035324) * Build-Depends on pkgconf instead of pkg-config * d/copyright: update copyright year Regards, -- Philippe --- End Message --- --- Begin Message --- Hi Philippe, Seems so that upstream has released a new version last week, but as you package looks fine, lets upload that one first ;) d/copyright: - upstream years needs to include at least 2023 (e.g for glslc/test/option_fpreserve_bindings.py) - kokoro needs also 2023 for Google. Otherwise, it looks fine to me, and fixing the RC bugs has priority, so uploaded. Please fix the copyright years for the next upload nethertheless and take a look at the lintian stuff, for example if usr/bin/glslc needs hardening and whether it makes sense to install the examples into the -dev packagse, as well as there are two typos mentioned by linitan. Thanks for your contribution to Debian! -- cheers, tobi On Mon, Mar 04, 2024 at 09:19:57PM +0100, Philippe SWARTVAGHER wrote: > Package: sponsorship-requests > Severity: important > > Dear mentors, > > I am looking for a sponsor for my package "shaderc": > > * Package name : shaderc >Version : 2023.8-1 >Upstream contact : David Neto > * URL : https://github.com/google/shaderc/ > * License : Apache-2.0, BSD-3-clause > * Vcs : https://salsa.debian.org/debian/shaderc >Section : libs > > The source builds the following binary packages: > > glslc - Command line compiler for GLSL/HLSL to SPIR-V > libshaderc-dev - Library API for accessing glslc functionality - > static libraries and headers > libshaderc1 - Library API for accessing glslc functionality - shared > libraries > > To access further information about this package, please visit the > following URL: > > https://mentors.debian.net/package/shaderc/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/s/shaderc/shaderc_2023.8-1.dsc > > Changes since the last upload: > > shaderc (2023.8-1) unstable; urgency=medium > . >* New upstream release > - Refresh patches > - Add patch to fix name of Python interpreter > - Fix FTBFS (Closes: #1058397) > - Refresh d/glslc.lintian-overrides >* Fix linking of libshaderc.so, add autopkgtest (Closes: #1029939) >* Add obj-x86_64-linux-gnu to d/clean >* Use printf instead of echo to generate build-version.inc. Thanks to > Vagrant Cascadian! (Closes: #1035324) >* Build-Depends on pkgconf instead of pkg-config >* d/copyright: update copyrig
Bug#1065442: RFS: shaderc/2023.8-1 [RC] -- Library API for accessing glslc functionality - shared libraries
Hi Philippe, Seems so that upstream has released a new version last week, but as you package looks fine, lets upload that one first ;) d/copyright: - upstream years needs to include at least 2023 (e.g for glslc/test/option_fpreserve_bindings.py) - kokoro needs also 2023 for Google. Otherwise, it looks fine to me, and fixing the RC bugs has priority, so uploaded. Please fix the copyright years for the next upload nethertheless and take a look at the lintian stuff, for example if usr/bin/glslc needs hardening and whether it makes sense to install the examples into the -dev packagse, as well as there are two typos mentioned by linitan. Thanks for your contribution to Debian! -- cheers, tobi On Mon, Mar 04, 2024 at 09:19:57PM +0100, Philippe SWARTVAGHER wrote: > Package: sponsorship-requests > Severity: important > > Dear mentors, > > I am looking for a sponsor for my package "shaderc": > > * Package name : shaderc >Version : 2023.8-1 >Upstream contact : David Neto > * URL : https://github.com/google/shaderc/ > * License : Apache-2.0, BSD-3-clause > * Vcs : https://salsa.debian.org/debian/shaderc >Section : libs > > The source builds the following binary packages: > > glslc - Command line compiler for GLSL/HLSL to SPIR-V > libshaderc-dev - Library API for accessing glslc functionality - > static libraries and headers > libshaderc1 - Library API for accessing glslc functionality - shared > libraries > > To access further information about this package, please visit the > following URL: > > https://mentors.debian.net/package/shaderc/ > > Alternatively, you can download the package with 'dget' using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/s/shaderc/shaderc_2023.8-1.dsc > > Changes since the last upload: > > shaderc (2023.8-1) unstable; urgency=medium > . >* New upstream release > - Refresh patches > - Add patch to fix name of Python interpreter > - Fix FTBFS (Closes: #1058397) > - Refresh d/glslc.lintian-overrides >* Fix linking of libshaderc.so, add autopkgtest (Closes: #1029939) >* Add obj-x86_64-linux-gnu to d/clean >* Use printf instead of echo to generate build-version.inc. Thanks to > Vagrant Cascadian! (Closes: #1035324) >* Build-Depends on pkgconf instead of pkg-config >* d/copyright: update copyright year > > Regards, > -- > Philippe >
Bug#1064344: marked as done (RFS: vzlogger/0.8.3 ITP #864255)
Your message dated Sun, 17 Mar 2024 10:06:00 +0100 with message-id and subject line Re: Bug#1064344: RFS: vzlogger/0.8.3 ITP #864255 has caused the Debian Bug report #1064344, regarding RFS: vzlogger/0.8.3 ITP #864255 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.) -- 1064344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "vzlogger": * Package name : vzlogger Version : 3.1-4 Upstream contact : Joachim Zobel * URL : http://wiki.volkszaehler.org/software/controller/vzlogger * License : GPL-3 * Vcs : https://github.com/volkszaehler/vzlogger Section : net The source builds the following binary packages: vzlogger - program to read measurements from smart meters and log them to Influxdb or forward them via MQTT. vzlogger is a tool to read and log measurements of a wide variety of smart meters and sensors. It supports various commonly used protocols such as s0, d0, sml, oms and others. It can write these data to an Influxdb, forward them via MQTT, make them available via HTTP or eport them to a volkszaehler.org middleware. The package is maintained in the upstream repository. Upstream (which I am part of) currently builds native packages. These are patched (a switch from native to quilt, a different changelog and a version >= 3.0 for the dependency on openssl) to make them more suitable for debian. The package is therefore availabe in the upstream repo https://github.com/volkszaehler/vzlogger.git on branch debian-0.8.3-1. Alternatively, you can download the package with 'dget' using this command: dget -x http://www.heute-morgen.de/debian/repo/unstable/main/source/net/vzlogger_0.8.3-1.dsc Regards, -- Joachim Zobel --- End Message --- --- Begin Message --- Control: tags 864255 pending Hi Joachim, uploaded. Thanks for your contribution to Debian! As this is a new package, it will be in the NEW queue [1] until the package is accepted by the FTP masters. (As we are done with the RFS, I'll close the RFS bug with this mail too) Cheers, -- tobi [1] https://wiki.debian.org/NewQueue signature.asc Description: PGP signature --- End Message ---
