Bug#1037174: RFS: damo/1.8.4-1 [ITP] -- Data Access Monitoring Operator

2023-06-06 Thread Michel Alexandre Salim
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "damo":

 * Package name : damo
   Version  : 1.8.4-1
   Upstream contact : SeongJae Park 
 * URL  : https://damonitor.github.io/
 * License  : GPL-2
 * Vcs  : https://salsa.debian.org/python-team/packages/damo
   Section  : devel

The source builds the following binary packages:

  damo - Data Access Monitoring Operator

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/damo/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/d/damo/damo_1.8.4-1.dsc

Changes for the initial release:

 damo (1.8.4-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1037157)

Regards,

-- 
Michel Alexandre Salim
identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


signature.asc
Description: PGP signature


Re: Bug#1037099: RFS: lighttpd/1.4.71-1 -- light, fast, functional web server

2023-06-06 Thread Andrej Shadura
Hi,

On Sun, 4 Jun 2023, at 20:17, gs-bugs.debian@gluelogic.com wrote:
>  * Package name : lighttpd
>Version  : 1.4.71-1
>Upstream contact : team+light...@tracker.debian.org
>  * URL  : https://lighttpd.net/
>  * License  : BSD-3-Clause
>  * Vcs  : https://git.lighttpd.net/lighttpd/lighttpd1.4
>
> Similar to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036020
> for lighttpd 1.4.70, this currently targets experimental, though I
> would like to get this into testing and into Bookworm in due time.
> Please advise.

Glenn, Bookworm is due to be released this week, it is the deepest freeze now.
There’s absolutely no way to get this release into it. Sorry.

-- 
Cheers,
  Andrej



Bug#1036751: RFS: mini-httpd/1.30-4 [ITA] -- Small HTTP server

2023-06-06 Thread Nicholas D Steeves
Hi Alexandru,

Alexandru Mihail  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.


signature.asc
Description: PGP signature