Bug#997810: RFS: rednotebook/2.22+ds-3 -- Modern desktop diary and personal journaling tool
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "rednotebook": * Package name: rednotebook Version : 2.22+ds-3 Upstream Author : Jendrik Seipp * URL : https://rednotebook.app * License : GPL-3+, GPL-2+, CC0-1.0, PSF-2, LGPL-3+ * Vcs : https://github.com/jendrikseipp/rednotebook Section : text It builds those binary packages: rednotebook - Modern desktop diary and personal journaling tool To access further information about this package, please visit the following URL: https://mentors.debian.net/package/rednotebook/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/r/rednotebook/rednotebook_2.22+ds-3.dsc Changes since the last upload: rednotebook (2.22+ds-3) unstable; urgency=medium . * Add upstream patches: - 001-prevent-main-window-crash-cf2970e-no-changelog.patch - 002-workaround-save-fail-on-cloud-drives-754a821-no-changelog.patch * Update standards-version to 4.6.0.1 - No changes required. * Add upstream contact to d/copyright. Regards Phil -- *** Playing the game for the games own sake. *** WWW: https://kathenas.org Twitter: @kathenasorg IRC: kathenas GPG: 724AA9B52F024C8B signature.asc Description: This is a digitally signed message part
Re: Bug#997016: RFS: swtpm/0.7.0-rc2-1 [ITA] -- Libtpms-based TPM emulator
On Sun, 2021-10-24 at 14:24 +0200, wf...@niif.hu wrote: > libraries (like libswtpm_libtpms.a) This library sounds like an embedded code copy, if it is one, please follow the advice on this wiki page. libtpms is already in Debian. https://wiki.debian.org/EmbeddedCopies -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#995566: RFS: golang-github-bytedance-gopkg/0.0~git20210910.e4efae9-1 [ITP] -- Universal Utilities for Go (library)
Hi Aloïs Micard, Thanks for reply, Yes, I've built it in newly created vagrant debian vm using pbuilder, and it works well. According to the failed log you provided, I wonder if your cpu has something special. Could you please provide the lscpu -v output so I can send it to upstream and find out the reason it failed to test. On Wed, Oct 13, 2021 at 3:21 PM Aloïs Micard wrote: > > On Sat, 2 Oct 2021 18:41:42 +0800 Yanhao Mo wrote: > > Package: sponsorship-requests > > Severity: wishlist > > > > Dear mentors, > > > > I am looking for a sponsor for my package "golang-github-bytedance-gopkg": > > > > * Package name: golang-github-bytedance-gopkg > >Version : 0.0~git20210910.e4efae9-1 > >Upstream Author : [fill in name and email of upstream] > > * URL : https://github.com/bytedance/gopkg > > * License : Apache-2.0 > > * Vcs : > > https://salsa.debian.org/go-team/packages/golang-github-bytedance-gopkg > >Section : golang > > > > It builds those binary packages: > > > > golang-github-bytedance-gopkg-dev - Universal Utilities for Go (library) > > > > To access further information about this package, please visit the > > following URL: > > > > https://mentors.debian.net/package/golang-github-bytedance-gopkg/ > > > > Alternatively, one can download the package with dget using this command: > > > > dget -x > > https://mentors.debian.net/debian/pool/main/g/golang-github-bytedance-gopkg/golang-github-bytedance-gopkg_0.0~git20210910.e4efae9-1.dsc > > > > Changes for the initial release: > > > > golang-github-bytedance-gopkg (0.0~git20210910.e4efae9-1) unstable; > > urgency=medium > > . > >* Initial release (Closes: #995564) > > > > Regards, > > -- > > Yanhao Mo > > > > > > Hello there! > > I have tried building your package in an up-to-date chroot (amd64) but > the build has failed during the dh_auto_test phase. > Here's the relevant output: > > ``` > === RUN TestLen0_16 > --- PASS: TestLen0_16 (0.00s) > === RUN TestLen17_128 > --- PASS: TestLen17_128 (0.00s) > === RUN TestLen129_240 > --- PASS: TestLen129_240 (0.00s) > === RUN TestLen240_1024 > --- PASS: TestLen240_1024 (0.00s) > === RUN TestLen1025_1048576_scalar > --- PASS: TestLen1025_1048576_scalar (0.00s) > === RUN TestLen1024_1048576_AVX2 > SIGILL: illegal instruction > PC=0x512f99 m=0 sigcode=2 > instruction bytes: 0xc5 0xfe 0x6f 0x8 0xc5 0xfe 0x6f 0x50 0x20 0xc4 0xe2 0x7d > 0x59 0x5 0x81 0x6e > > goroutine 23 [running]: > github.com/bytedance/gopkg/util/xxhash3.accumAVX2(0x660e80, 0xc00018, > 0x619740, 0x400) > > /<>/_build/src/github.com/bytedance/gopkg/util/xxhash3/avx2.s:30 > +0x19 fp=0xc39698 sp=0xc39690 pc=0x512f99 > github.com/bytedance/gopkg/util/xxhash3.xxh3HashLarge(0xc00018, 0x400, > 0x1ad20e5fd78cde6e) > > /<>/_build/src/github.com/bytedance/gopkg/util/xxhash3/hash.go:127 > +0x537 fp=0xc396e8 sp=0xc39698 pc=0x50f0b7 > github.com/bytedance/gopkg/util/xxhash3.Hash(0xc00018, 0x400, 0x20186a0, > 0x1ad20e5fd78cde6e) > > /<>/_build/src/github.com/bytedance/gopkg/util/xxhash3/hash.go:33 > +0x52 fp=0xc39710 sp=0xc396e8 pc=0x50e912 > github.com/bytedance/gopkg/util/xxhash3.TestLen1024_1048576_AVX2(0xc01e00) > > /<>/_build/src/github.com/bytedance/gopkg/util/xxhash3/correctness_test.go:105 > +0xb7 fp=0xc39780 sp=0xc39710 pc=0x510a77 > testing.tRunner(0xc01e00, 0x5591e8) > /usr/lib/go-1.16/src/testing/testing.go:1193 +0xef fp=0xc397d0 > sp=0xc39780 pc=0x4cd84f > runtime.goexit() > /usr/lib/go-1.16/src/runtime/asm_amd64.s:1371 +0x1 fp=0xc397d8 > sp=0xc397d0 pc=0x46c6e1 > created by testing.(*T).Run > /usr/lib/go-1.16/src/testing/testing.go:1238 +0x2b3 > > goroutine 1 [chan receive]: > testing.(*T).Run(0xc01e00, 0x553458, 0x18, 0x5591e8, 0x47f101) > /usr/lib/go-1.16/src/testing/testing.go:1239 +0x2da > testing.runTests.func1(0xc01380) > /usr/lib/go-1.16/src/testing/testing.go:1511 +0x78 > testing.tRunner(0xc01380, 0xc89de0) > /usr/lib/go-1.16/src/testing/testing.go:1193 +0xef > testing.runTests(0xc0c048, 0x62fc20, 0xe, 0xe, 0xc051c0102355a113, > 0x8bd496be5e, 0x633900, 0x550c81) > /usr/lib/go-1.16/src/testing/testing.go:1509 +0x2fe > testing.(*M).Run(0xca8000, 0x0) > /usr/lib/go-1.16/src/testing/testing.go:1417 +0x1eb > main.main() > _testmain.go:71 +0x138 > > rax0x660e80 > rbx0x619740 > rcx0xc00018 > rdx0x619740 > rdi0x18e82621e5dca703 > rsi0x400 > rbp0xc396d8 > rsp0xc39690 > r8 0x3fd7867397525a9a > r9 0x43f2905c46cd412f > r100xff7aa508c0f63fe5 > r110x9e3779b185ebca87 > r120xc39708 > r130x0 > r140x578284 > r150x0 > rip0x512f99 > rflags 0x10202 > cs 0x33 > fs 0x0 > gs 0x0 > FAILgithub.com/bytedance/gopkg/util/xxhash3 0.575s > ?
Bug#997793: RFS: libcxx-serial/1.2.1-5 [RC] -- Cross-platform, Serial Port library written in C++ (runtime)
Control: tags -1 moreinfo Hi Alec, There was a NMU of libcxx-serial [1] . This NMU is not included in your updated package --> You need to include the changed of this MMU in the package and possibly into your git repo... [1] See https://deb.debian.org/debian/pool/main/libc/libcxx-serial/libcxx-serial_1.2.1-4.1.dsc -- tobi
Bug#997016: RFS: swtpm/0.7.0-rc2-1 [ITA] -- Libtpms-based TPM emulator
Hello Feri, Thank you for your advice. > The upstream version number should be 0.7.0~rc2 with a tilde instead of > a hyphen to ensure proper ordering (as Lintian warns about). To do such > transformations automatically, put something like this in the watch file: > > uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/ > I will update the watch file following your advice soon. > > swtpm - Libtpms-based TPM emulator > > swtpm-dev - Include files for the TPM emulator's CUSE interface > > swtpm-libs - Common libraries for TPM emulators > > Why do you deviate from the usual libswtpm-dev/libswtpm0 package names? > Including the SO version in the package name enables installing > incompatible versions side-by-side, which is useful. > > Also, shipping static libraries (like libswtpm_libtpms.a) is generally > recommended against in Debian. Does this package warrant it? The upstream version already has some debian-related files, and I changed them to adopt the package. The author of it wants to name it like libswtpm0, so I used the name. The static libraries are also involved in upstream debian files. Should I change the name like libswtpm instead of libswtpm0 and remove static libraries from the package? > > > swtpm-tools - Tools for the TPM emulator > > Why do you put swtpm-create-tpmca, swtpm-create-user-config-files and > swtpm-localca into /usr/share/swtpm instead of /usr/bin? (This emits > several Lintian information tags.) The author of the upstream project wanted to put them to /usr/share/swtpm. The files are just for the initialization and don't be used for TPM operations directly, so maybe he wanted to put /usr/share/swtpm instead of /usr/bin. Should I move them to /usr/bin? Best regards, Seunghun
Bug#997793: RFS: libcxx-serial/1.2.1-5 [RC] -- Cross-platform, Serial Port library written in C++ (runtime)
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "libcxx-serial": * Package name: libcxx-serial Version : 1.2.1-5 Upstream Author : wjww...@gmail.com * URL : http://wjwwood.io/serial/ * License : Expat, BSD-3-clause * Vcs : https://gitlab.com/leamas/cxx-serial Section : libs It builds two binary packages: libcxx-serial-dev - Cross-platform, Serial Port library written in C++ (devel) libcxx-serial1 - Cross-platform, Serial Port library written in C++ (runtime) More info at: https://mentors.debian.net/package/libcxx-serial/ or using dget -x https://mentors.debian.net/debian/pool/main/libc/libcxx-serial/libcxx-serial_1.2.1-5.dsc Changes since the last upload: libcxx-serial (1.2.1-5) unstable; urgency=medium . * Handle uninstalled cmake configuration files. Closes: #997732 This is simple, bugfix release. Regards, -- Alec Leamas
Re: Bug#997016: RFS: swtpm/0.7.0-rc2-1 [ITA] -- Libtpms-based TPM emulator
Seunghun Han writes: > * Package name: swtpm >Version : 0.7.0-rc2-1 Hi, The upstream version number should be 0.7.0~rc2 with a tilde instead of a hyphen to ensure proper ordering (as Lintian warns about). To do such transformations automatically, put something like this in the watch file: uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/ > swtpm - Libtpms-based TPM emulator > swtpm-dev - Include files for the TPM emulator's CUSE interface > swtpm-libs - Common libraries for TPM emulators Why do you deviate from the usual libswtpm-dev/libswtpm0 package names? Including the SO version in the package name enables installing incompatible versions side-by-side, which is useful. Also, shipping static libraries (like libswtpm_libtpms.a) is generally recommended against in Debian. Does this package warrant it? > swtpm-tools - Tools for the TPM emulator Why do you put swtpm-create-tpmca, swtpm-create-user-config-files and swtpm-localca into /usr/share/swtpm instead of /usr/bin? (This emits several Lintian information tags.) -- Thanks for you work! Regards, Feri
