Bug#989068: ITP: object-cloner -- Java Object cloning library with extensible strategies
Hi! On Mon, 2021-05-24 at 20:08:57 -0400, James Valleroy wrote: > Package: wnpp > Severity: wishlist > Owner: James Valleroy > X-Debbugs-Cc: debian-de...@lists.debian.org, jvalle...@mailbox.org > > * Package name: object-cloner > Version : 0.2 > Upstream Author : Kamran Zafar > * URL : https://github.com/kamranzafar/object-cloner > * License : Apache-2.0 > Programming Lang: Java > Description : Java Object cloning library with extensible strategies > > Java Object cloning library. Supports extensible shallow and deep object > cloning strategies. > > This is a dependency of jcl-core, which is needed for jitsi-videobridge > (#757769). The source package seems overly generic, could you namespace it please? Say name it to what I assume might end up being the binary name «libobject-cloner-java»? Thanks, Guillem
Bug#989101: ITP: libliftoff -- lightweight hardware composer library for libdrm
Package: wnpp Severity: wishlist Owner: Stephan Lachnit X-Debbugs-Cc: debian-de...@lists.debian.org, stephanlach...@debian.org * Package name: libliftoff Version : 0.0.0~git20210430.799 Upstream Author : Simon Ser <~emersion/public-in...@lists.sr.ht> * URL : https://github.com/emersion/libliftoff * License : MIT) Programming Lang: C Description : lightweight hardware composer library for libdrm Dependency for gamescope. Not sure where to maintain, will probably talk to the X Strike Force team. Description: libliftoff eases the use of KMS planes from userspace without standing in your way. Users create "virtual planes" called layers, set KMS properties on them, and libliftoff will pick planes for these layers if possible. Longer explaination: https://emersion.fr/blog/2019/xdc2019-wrap-up/#libliftoff - Stephan
Bug#989085: ITP: gamescope -- micro-compositor for games
Hi Sam, yes I know. I haven't come up with a good 3 line description yet. tl;dr: it's an application that allows to run programs in a nested environment originating from the SteamOS compositor. The main use is to run older games in their original resolution on a high dpi screen via upscaling. - Stephan On Tue, May 25, 2021 at 6:23 PM Sam Hartman wrote: > > > "Stephan" == Stephan Lachnit writes: > > Stephan> BSD-2-Clause Programming Lang: C Description : > Stephan> micro-compositor for games > > Stephan> Will maintain in Games team. > > Stephan> Description on GitHub: > > Stephan> In an embedded session usecase, gamescope does the same > Stephan> thing as steamcompmgr, but with less extra copies and > Stephan> latency: > > That description isn't good enough that I can tell what this is without > going and doing a bunch of additional research. > I'd recommend improving significantly so someone can tell from the > package description whether they want the package.
Processed: ITP: r-cran-fancova -- GNU R nonparametric analysis of covariance
Processing commands for cont...@bugs.debian.org: > owner 989097 Andreas Tille Bug #989097 [wnpp] ITP: r-cran-fancova -- GNU R nonparametric analysis of covariance Owner recorded as Andreas Tille . > End of message, stopping processing here. Please contact me if you need assistance. -- 989097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989097: ITP: r-cran-fancova -- GNU R nonparametric analysis of covariance
Package: wnpp Severity: wishlist Subject: ITP: r-cran-fancova -- GNU R nonparametric analysis of covariance Package: wnpp Owner: Andreas Tille Severity: wishlist * Package name: r-cran-fancova Version : 0.6 Upstream Author : Xiaofeng Wang, * URL : https://cran.r-project.org/package=fANCOVA * License : GPL-3 Programming Lang: GNU R Description : GNU R nonparametric analysis of covariance A collection of R functions to perform nonparametric analysis of covariance for regression curves or surfaces. Testing the equality or parallelism of nonparametric curves or surfaces is equivalent to analysis of variance (ANOVA) or analysis of covariance (ANCOVA) for one-sample functional data. Three different testing methods are available in the package, including one based on L-2 distance, one based on an ANOVA statistic, and one based on variance estimators. Remark: This package is maintained by Debian R Packages Maintainers at https://salsa.debian.org/r-pkg-team/r-cran-fancova
Processed: ITP: r-cran-cutpointr -- GNU R determine and evaluate optimal cutpoints in binary
Processing commands for cont...@bugs.debian.org: > owner 989093 Andreas Tille Bug #989093 [wnpp] ITP: r-cran-cutpointr -- GNU R determine and evaluate optimal cutpoints in binary Owner recorded as Andreas Tille . > End of message, stopping processing here. Please contact me if you need assistance. -- 989093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989093: ITP: r-cran-cutpointr -- GNU R determine and evaluate optimal cutpoints in binary
Package: wnpp Severity: wishlist Subject: ITP: r-cran-cutpointr -- GNU R determine and evaluate optimal cutpoints in binary Package: wnpp Owner: Andreas Tille Severity: wishlist * Package name: r-cran-cutpointr Version : 1.1.0 Upstream Author : Christian Thiele * URL : https://cran.r-project.org/package=cutpointr * License : GPL-3 Programming Lang: GNU R Description : GNU R determine and evaluate optimal cutpoints in binary Classification Tasks Estimate cutpoints that optimize a specified metric in binary classification tasks and validate performance using bootstrapping. Some methods for more robust cutpoint estimation are supported, e.g. a parametric method assuming normal distributions, bootstrapped cutpoints, and smoothing of the metric values per cutpoint using Generalized Additive Models. Various plotting functions are included. For an overview of the package see Thiele and Hirschfeld (2020) . Remark: This package is maintained by Debian R Packages Maintainers at https://salsa.debian.org/r-pkg-team/r-cran-cutpointr
Processed: ITP: r-cran-kableextra -- construct complex table with 'kable' and pipe syntax in GNU R
Processing commands for cont...@bugs.debian.org: > owner 989092 Andreas Tille Bug #989092 [wnpp] ITP: r-cran-kableextra -- construct complex table with 'kable' and pipe syntax in GNU R Owner recorded as Andreas Tille . > End of message, stopping processing here. Please contact me if you need assistance. -- 989092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989092 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#989092: ITP: r-cran-kableextra -- construct complex table with 'kable' and pipe syntax in GNU R
Package: wnpp Severity: wishlist Subject: ITP: r-cran-kableextra -- construct complex table with 'kable' and pipe syntax in GNU R Package: wnpp Owner: Andreas Tille Severity: wishlist * Package name: r-cran-kableextra Version : 1.3.4 Upstream Author : Hao Zhu, * URL : https://cran.r-project.org/package=kableExtra * License : MIT Programming Lang: GNU R Description : construct complex table with 'kable' and pipe syntax in GNU R Build complex HTML or 'LaTeX' tables using 'kable()' from 'knitr' and the piping syntax from 'magrittr'. Function 'kable()' is a light weight table generator coming from 'knitr'. This package simplifies the way to manipulate the HTML or 'LaTeX' codes generated by 'kable()' and allows users to construct complex tables and customize styles using a readable syntax. Remark: This package is maintained by Debian R Packages Maintainers at https://salsa.debian.org/r-pkg-team/r-cran-kableextra
Bug#989085: ITP: gamescope -- micro-compositor for games
> "Stephan" == Stephan Lachnit writes: Stephan> BSD-2-Clause Programming Lang: C Description : Stephan> micro-compositor for games Stephan> Will maintain in Games team. Stephan> Description on GitHub: Stephan> In an embedded session usecase, gamescope does the same Stephan> thing as steamcompmgr, but with less extra copies and Stephan> latency: That description isn't good enough that I can tell what this is without going and doing a bunch of additional research. I'd recommend improving significantly so someone can tell from the package description whether they want the package.
Bug#989085: ITP: gamescope -- micro-compositor for games
Package: wnpp Severity: wishlist Owner: Stephan Lachnit X-Debbugs-Cc: debian-de...@lists.debian.org, stephanlach...@debian.org.com * Package name: gamescope Version : 3.8.1 Upstream Author : Pierre-Loup A. Griffais * URL : https://github.com/Plagman/gamescope * License : BSD-2-Clause Programming Lang: C Description : micro-compositor for games Will maintain in Games team. Description on GitHub: In an embedded session usecase, gamescope does the same thing as steamcompmgr, but with less extra copies and latency: It's getting game frames through Wayland by way of Xwayland, so there's no copy within X itself before it gets the frame. It can use DRM/KMS to directly flip game frames to the screen, even when stretching or when notifications are up, removing another copy. When it does need to composite with the GPU, it does so with async Vulkan compute, meaning you get to see your frame quick even if the game already has the GPU busy with the next frame. It also runs on top of a regular desktop, the 'nested' usecase steamcompmgr didn't support. Because the game is running in its own personal Xwayland sandbox desktop, it can't interfere with your desktop and your desktop can't interfere with it. You can spoof a virtual screen with a desired resolution and refresh rate as the only thing the game sees, and control/resize the output as needed. This can be useful in exotic display configurations like ultrawide or multi-monitor setups that involve rotation. It runs on Mesa+AMDGPU, and could be made to run on other Mesa/DRM drivers with minimal work. Can support NVIDIA if/when they support accelerated Xwayland. - Stephan
Bug#989084: ITP: ruby-declarative-policy -- authorization library with a focus on declarative policy definitions
Package: wnpp Severity: wishlist Owner: Pirate Praveen Debian packaging of https://rubygems.org/gems/declarative_policy Dependency of gitlab 13.12.0
Bug#810890: ITP: caddy -- Fast, cross-platform HTTP/2 web server with automatic HTTPS
Hello, Plus a link to https://wiki.debian.org/SummerOfCode2021/Projects/PackagingCaddy I have been accepted to gsoc[1] with said »packaging caddy« project and would like to pick up this ITP. kind regards, peymaneh [1] https://summerofcode.withgoogle.com/projects/#6674433650982912 OpenPGP_signature Description: OpenPGP digital signature
Bug#814382: RFH: samba -- SMB/CIFS file, print, and login server for Unix
Le lun. 24 mai 2021 à 07:18, Abi a écrit :
>
> Hello again, thanks for responding.
>
> My skills include:
>
> An amateur understanding of Samba4 AD DC and file server. I manage a dozen or
> so installations ( addc and fs ), and I know how to spin up and manage
> installations as well as troubleshoot issues when they occur. I also read
> through the mailing list daily in order to have a better grasp possible
> issues.
> Identifying warnings/errors from log output within code. I wouldn't call
> myself an advanced C or Python developer ( I mostly write golang/php ),
> however I should be able to look through the source code and trace issues
> based off the output reporters provide.
>
> I'm also interested in debian packaging, but I know absolutely nothing apart
> from a few links I've read through. Would you be able to forward me some
> relevant reading so I'll be able to assist on that front ( if needed ) in the
> future?
You can take a look at https://wiki.debian.org/Packaging which starts
with basic guides up to advanced topics. Samba is a big package, using
recent packaging methods.
>
> By default, sending to n...@bugs.debian.org won't be sent to the submitter,
> carefully read https://www.debian.org/Bugs/Developer#followup to ensure that
> both submitter and maintainer (pkg-samba list) have the mail (nnn +
> nnn-submitter)
>
> I read through that section that you've linked and I think I understand.
> Since you are the maintainer and the person I am replying to, this message
> will actually get to you twice. However, if you were not a maintainer and
> just a user in the bug report I was replying to, you would receive this once.
> If I wanted to reply directly to the bug submitter and maintainer, I would
> tag 814...@bugs.debian.org ( so the maintainer receives it ) and
> 814382-submit...@bugs.debian.org ( so the submitter receives it ) - I'm
> assuming it will only be filed in the bug report once. Alternatively,
> couldn't I just send a reply to 814...@bugs.debian.org and {submitter email
> address} ? or should I stick with nnn-submitter?
You can send to submitter address directly, they may receive the mail
twice if you do and they have subscribed to the bug (but twice is
better than none).
>
> Debian's bug tracker is managed thru mails, you can look at
> https://www.debian.org/Bugs/ and
> https://www.debian.org/Bugs/server-control to start with.
>
> I've gone ahead and read through both links ( and the links within those
> links ), and I think I have a good understanding of the various levels/tags
> that should be assigned to a report and what the standard operating procedure
> is, as well as the control request server commands.
>
> Tagging bugs and closing with the relevant version of the fix would help a
> lot!
>
> Sure, where should I start? I looked through
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=samba#_0_4_4
> , and found: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765408 . I
> guess what needs to be changed is:
>
> Tag set to fixed-upstream
> Security level: important
> Add wheezy tag
Yes
> I'm assuming it's okay to close the bug report after that since the wheezy is
> EOL, and there is no hope for backporting?
Yes, you can also close jessie-only bugs for the same reason. For
stretch and buster, you can also close up to normal-severity bugs,
saying that we won't fix them. Having a list of commits that we should
cherry-pick for buster would be good (security fixes, stability fixes,
crashes). Also I think upgrade issues up to stretch can be closed.
> Am I on the right track, or totally off?
You're on the right track. Go ahead ! I'll receive notifications of
your changes and if you have any doubt, ask on the bug. Some users may
have created a bug and are no longer impacted, so pinging old bugs and
closing after a month without reply will also help.
Also, appart from samba, there are some bugs in cifs-utils (and one in
ldb, talloc, tevent):
https://qa.debian.org/developer.php?email=pkg-samba-maint%40lists.alioth.debian.org
>
> Let me know if there's a particular system you'd like me to follow when
> triaging. I can start right away.
You can sort by bug number, or by severity. Both ascending and
descending makes sense.
>
> Thanks!
>
>
> On 5/23/21 3:02 PM, Mathieu Parent wrote:
>
> Le dim. 23 mai 2021 à 04:33, Abi a écrit :
>
> Hello Mathieu,
>
> Hello Abi,
>
> I saw the help request submitted to the samba mailing list by A.
> Bartlett on 05/14 . I would love to help with triaging bug
> reports/improving tests . What steps would I need to take in order to
> get involved?
>
> Let me know. Thanks.
>
> Thanks for proposing your help.What are your skills?
>
> Debian's bug tracker is managed thru mails, you can look at
> https://www.debian.org/Bugs/ and
> https://www.debian.org/Bugs/server-control to start with.
>
> By default, sending to n...@bugs.debian.org won't be sent to the submitter,
> carefully read
