Re: Bug#1036882: RFS: jimtcl/0.82-1 -- small-footprint implementation of Tcl - shared library
Hi,
On Fri, Jun 9, 2023 at 3:21 AM Andrej Shadura wrote:
>
> Hi,
>
> On Thu, 8 Jun 2023, at 18:23, Bo YU wrote:
> > jimtcl (0.82-1) experimental; urgency=medium
> > .
> >* New upstream release.
> >* set --full default build options from upstream.(Closes: #1016657)
> >* update symbols file
> >* add libssl-dev,pkg-config on B-D
> >
> > ```
> > The repo is here: https://salsa.debian.org/debian/jimtcl
> >
> > I am not sure It is okay to drop the dfsg because I do not see any
> > file licenses violation of Debian's dfsg.
> > please let me know if there is any issues.
> > Thanks again~
>
> Thanks!
>
> You need to disable network tests, as networking is not allowed at buildds:
>
> ssl-2.2 ERR https to google.com, read with cert verify
> /<>/tests/ssl.test:75:Error test failure
> Expected: rc={ok return} result={HTTP/1.0 200 OK*}
> Got : rc=error result={failed to verify the connection authenticity}
>
> ssl.test: Total 5 Passed 4 Skipped 0 Failed 1
>
> FAILED: 1
> /<>/tests/ssl.test:75 ssl-2.2
>
Got it. I disabled/ignored the test with the $(testreport) it at this
time. But I am wonder why it will not
be reproduced on my local build with sbuild. Need I to change some
modifies in ~/.sbuildrc?
Another serious issue is it fails to build on i386:
https://salsa.debian.org/debian/jimtcl/-/pipelines/535907
I hope it can be uploaded to experimental this time and to see the
issue if existed in others arch, this is to help upstream
to debug the issue also I think.
Could you help me to upload it in this situation?
[0]: https://mentors.debian.net/package/jimtcl/
[1]: https://salsa.debian.org/debian/jimtcl
```
Changelog
jimtcl (0.82-1) experimental; urgency=medium
.
* New upstream release.
* set --full default build options from upstream.(Closes: #1016657)
* update symbols file
* add libssl-dev,pkg-config on B-D
* disable network access test from ssl.test
```
Thanks!
>
> --
> Cheers,
> Andrej
Bug#1037241: RFS: php-fig-log-test/1.1.0-1 [ITP] -- Test utilities for the psr/log package that backs the PSR-3 specification
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "php-fig-log-test": * Package name : php-fig-log-test Version : 1.1.0-1 Upstream contact : Anton Ukhanev * URL : https://github.com/php-fig/log-test * License : Expat * Vcs : https://salsa.debian.org/athos/php-fig-log-test Section : php The source builds the following binary packages: php-fig-log-test - Test utilities for the psr/log package that backs the PSR-3 specification To access further information about this package, please visit the following URL: https://mentors.debian.net/package/php-fig-log-test/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/p/php-fig-log-test/php-fig-log-test_1.1.0-1.dsc Changes for the initial release: php-fig-log-test (1.1.0-1) experimental; urgency=medium . * Initial release. (Closes: #1037154) Note that, as stated in the ITP for this package, at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037154, this should be uploaded to experimental until symfony 6 is ready to land in unstable. Regards, -- Athos Ribeiro
Bug#1037237: RFS: php-doc/20230505~git.fcb83b7+dfsg-1 [ITP] -- Documentation for PHP
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "php-doc": * Package name : php-doc Version : 20230505~git.fcb83b7+dfsg-1 Upstream contact : gr...@php.net * URL : http://docs.php.net/manual/en/ * License : CC-BY-3.0 and Expat and BSD-2-Clause and PHP-3.01 and PHP-3.0 * Vcs : https://salsa.debian.org/athos/php-doc Section : doc Please, see the ITP bug discussion at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903999 for additional context. The source builds the following binary packages: php-doc - Documentation for PHP To access further information about this package, please visit the following URL: https://mentors.debian.net/package/php-doc/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/p/php-doc/php-doc_20230505~git.fcb83b7+dfsg-1.dsc Changes since the last upload: php-doc (20230505~git.fcb83b7+dfsg-1) UNRELEASED; urgency=medium
Re: Bug#1036882: RFS: jimtcl/0.82-1 -- small-footprint implementation of Tcl - shared library
Hi,
On Thu, 8 Jun 2023, at 18:23, Bo YU wrote:
> jimtcl (0.82-1) experimental; urgency=medium
> .
>* New upstream release.
>* set --full default build options from upstream.(Closes: #1016657)
>* update symbols file
>* add libssl-dev,pkg-config on B-D
>
> ```
> The repo is here: https://salsa.debian.org/debian/jimtcl
>
> I am not sure It is okay to drop the dfsg because I do not see any
> file licenses violation of Debian's dfsg.
> please let me know if there is any issues.
> Thanks again~
Thanks!
You need to disable network tests, as networking is not allowed at buildds:
ssl-2.2 ERR https to google.com, read with cert verify
/<>/tests/ssl.test:75:Error test failure
Expected: rc={ok return} result={HTTP/1.0 200 OK*}
Got : rc=error result={failed to verify the connection authenticity}
ssl.test: Total 5 Passed 4 Skipped 0 Failed 1
FAILED: 1
/<>/tests/ssl.test:75 ssl-2.2
--
Cheers,
Andrej
Re: Bug#1036882: RFS: jimtcl/0.82-1 -- small-footprint implementation of Tcl - shared library
Hi! On Thu, Jun 8, 2023 at 3:18 PM Andrej Shadura wrote: > > Hi, > > On Sun, 28 May 2023, at 17:44, Bo YU wrote: > > I am looking for a sponsor for my package "jimtcl": > > > > * Package name : jimtcl > >Version : 0.82-1 > >Upstream contact : [fill in name and email of upstream] > > * URL : http://jim.tcl.tk/ > > * License : BSD-2-clause, TCL > > * Vcs : https://salsa.debian.org/debian/jimtcl > >Section : devel > > > Changes since the last upload: > > > > jimtcl (0.82-1) experimental; urgency=medium > > . > >* New upstream release. > >* set --full default build options from upstream.(Closes: #1016657) > > I wanted to sponsor it, but noticed these changes are not in the Git > repository. It looks like you forgot to push? Thanks for sponsoring it. yeah, I forget to push these changes to gitlab. Given these change, I resend v2 to [mentor] (https://mentors.debian.net/package/jimtcl/): ``` Changelog jimtcl (0.82-1) experimental; urgency=medium . * New upstream release. * set --full default build options from upstream.(Closes: #1016657) * update symbols file * add libssl-dev,pkg-config on B-D ``` The repo is here: https://salsa.debian.org/debian/jimtcl I am not sure It is okay to drop the dfsg because I do not see any file licenses violation of Debian's dfsg. please let me know if there is any issues. Thanks again~ BR, bo > > -- > Cheers, > Andrej
Bug#1036751: RFS: mini-httpd/1.30-4 [ITA] -- Small HTTP server
Hello Nicholas, > Nice catch, and if someone using OpenRC is affected, I hope that person > will be willing to provide a patch for what sounds like a corner-case. Thanks, I hope so as well > 1. What is the purpose of the dh_installsystemd override? (hint: see the > dh_installsystemd man page about --name). I missed that, fixed now, thanks ! > 2. I found an inaccuracy in the upstream sections of debian/changelog; > please fix it. Plain old grep or manual header check should be enough > to spot this. Can you please elaborate a bit ? Are you referring to my changelog entry or any mistakes in upstream.changelog or older debian/changelog entries ? > 3. Do the patches have accurate filenames, subjects, and synopses? > Adopting a package is the perfect time to fix anything misleading. > Most of them are fine, I'd change the filename of "0006-fix-makefile", a bit too generic, it changes some install dirs and adds -lssl to a compile target, not exactly something obvious when you read "fix-makefile". I'll come up with a better name. > 4. Does everything in your changelog entry still accurately reflect the > package? (ie "not started by default"). Fixed, thank you ! > Would you please push your work to your personal Salsa namespace (fork > relationship optional), and provide the link to the repo? This way I Will do, it was a very busy week :) > P.S. It seems like Debian's copy might be the defacto upstream, as of > eight years ago, when someone wrote we were "doing a good job" > maintaining mini_httpd. Hah, I've heard the same thing from an OpenWRT maintainer a few years ago. We're their defacto upstream as well (and any OpenWRT based router firmwares such as Tomato, etc etc). Long live the red spiral, I guess :) Have a great day, Alexandru --- Original Message --- On Tuesday, June 6th, 2023 at 8:49 PM, Nicholas D Steeves wrote: > Hi Alexandru, > > Alexandru Mihail alexandru_mih...@protonmail.ch writes: > > > Turns out bullseye-backports lintian (2.115.1~bpo11+1) only checks for > > 4.6.1 Standards, therefore a more serious error > > (depends-on-obsolete-package lsb-base) was reported by sid lintian. > > Upon inspecting the situation (lsb-base is now a transitional empty > > package only here for debootstrap purposes mainly) and reading > > https://lists.debian.org/debian-devel/2023/01/msg00160.html I removed > > the package dependency entirely. This should be entirely safe. > > > Nice catch, and if someone using OpenRC is affected, I hope that person > will be willing to provide a patch for what sounds like a corner-case. > > > I also added Upstream-Contact into debian/copyright and stripped some > > trailing whitelines. Package should be lintian O.K. now. > > > Thank you. > > > Nicholas, my salsa account is verified now, waiting for push permission if > > that is ok. Is there anything else I should do now about that ? > > > 1. What is the purpose of the dh_installsystemd override? (hint: see the > dh_installsystemd man page about --name). > > 2. I found an inaccuracy in the upstream sections of debian/changelog; > please fix it. Plain old grep or manual header check should be enough > to spot this. > > 3. Do the patches have accurate filenames, subjects, and synopses? > Adopting a package is the perfect time to fix anything misleading. > > 4. Does everything in your changelog entry still accurately reflect the > package? (ie "not started by default"). > > Would you please push your work to your personal Salsa namespace (fork > relationship optional), and provide the link to the repo? This way I > can responsibly grant you permissions, because I will have reviewed how > you work in git :) I can also review from git, if you prefer > > Regards, > Nicholas > > P.S. It seems like Debian's copy might be the defacto upstream, as of > eight years ago, when someone wrote we were "doing a good job" > maintaining mini_httpd.
how to tell dpkg to not remove some files on package removal/purge
Hello mentors, The runit-services package ships "metafiles" that are parsed by a noawait trigger in runit package; the purpose of the trigger is to perform actions like (oversimplified) enable/start or stop/disable a service when the correspondent binary is installed or removed [1]. The problem is that when the package is removed, the trigger runs after files removal happens so actions like disable/stop (and purge too) are skipped; is there a way to have those files not removed other than making a copy somewhere? I think dpkg doesn't remove at least the postrm script of packages, else I'm not sure how it could perform a purge action at all.. so I'm looking for a way to treat my "metafiles" the same way. Best Regards, Lorenzo [1] Usually debhelper takes care of writing snippets in maintscripts to perform such actions, but the design works only when the service file and the binary are produced from the same source package and this is not the case of runit-services.
Re: Bug#1036882: RFS: jimtcl/0.82-1 -- small-footprint implementation of Tcl - shared library
Hi, On Sun, 28 May 2023, at 17:44, Bo YU wrote: > I am looking for a sponsor for my package "jimtcl": > > * Package name : jimtcl >Version : 0.82-1 >Upstream contact : [fill in name and email of upstream] > * URL : http://jim.tcl.tk/ > * License : BSD-2-clause, TCL > * Vcs : https://salsa.debian.org/debian/jimtcl >Section : devel > Changes since the last upload: > > jimtcl (0.82-1) experimental; urgency=medium > . >* New upstream release. >* set --full default build options from upstream.(Closes: #1016657) I wanted to sponsor it, but noticed these changes are not in the Git repository. It looks like you forgot to push? -- Cheers, Andrej
