Bug#1023477: ITP: libtypec -- user-space library for accessing USB-C/USB-PD metadata

2022-11-04 Thread Jelmer Vernooij
Package: wnpp
Severity: wishlist
Owner: Jelmer Vernooij 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: libtypec
  Version : 0.1
  Upstream Author : Rajaram Regupathy 
* URL : https://github.com/Rajaram-Regupathy/libtypec/
* License : MIT
  Programming Lang: C
  Description : User-space library for accessing USB-C/USB-PD metadata

USB-Type C and USB Power Delivery systems are with multiple specification
versions, platform designs and microcontroller vendors to manage data, power
and display.

This library defines a generic way for userspace System Software on Linux,
Android, Chrome OS or Other OSes to build developer tools or other management
applications for USB-Type C and USB Power Delivery class devices.



Bug#1023474: ITP: check-logfiles -- Nagios plugin check_logfiles

2022-11-04 Thread Hilmar Preusse
Package: wnpp
Severity: wishlist
Owner: Hilmar Preusse 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: check-logfiles
  Version : 4.1
  Upstream Author : Gerhard Laußer 
* URL : https://labs.consol.de/nagios/check_logfiles/
* License : GPL
  Programming Lang: Perl
  Description : Nagios plugin check_logfiles

 check_logfiles is a Plugin for Nagios which scans log files for specific 
patterns.
 Features:
 - Detection of rotations - usually nightly logfiles are rotated and
   compressed. Each operating system or company has it’s own naming
   scheme. If this rotation is done between two runs of check_logfiles
   also the rotated archive has to be scanned to avoid gaps. The most
   common rotation schemes are predefined but you can describe any
   strategy (shortly: where and under which name is a logfile
   archived).
 - More than one pattern can be defined which again can be classified
   as warning patterns and critical patterns.
 - Triggered actions - Usually nagios plugins return just an exit code
   and a line of text, describing the result of the check. Sometimes,
   however, you want to run some code during the scan every time you
   got a hit. Check_logfiles lets you call scripts either after every
   hit or at the beginning or the end of it’s runtime.
 - Exceptions - If a pattern matches, the matched line could be a very
   special case which should not be counted as an error. You can
   define exception patterns which are more specific versions of your
   critical/warning patterns. Such a match would then cancel an alert.
 - Thresholds - You can define the number of matching lines which are
   necessary to activate an alert.
 - Protocol - The matching lines can be written to a protocol file the
   name of which will be included in the plugin’s output.
 - Macros - Pattern definitions and logfile names may contain macros,
   which are resolved at runtime.
 - Performance data - The number of lines scanned and the number of
   warnings/criticals is output.
 - Windows - The plugin works with Unix as well as with Windows
   (e.g. with ActiveState Perl).

Further information:

 - check_logfiles is widely used in the Nagios / Icinga world
   for log file monitoring.
 - Maintenance will be done by me. It is just a small package,
   no need to have a team for this.


Bug#1023449: ITP: furo -- clean customisable Sphinx documentation theme

2022-11-04 Thread Georges Khaznadar
Package: wnpp
Severity: wishlist
Owner: Georges Khaznadar 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: furo
  Version : 2022.9.29
  Upstream Author : Pradyun Gedam 
* URL : https://github.com/pradyunsg/furo
* License : MIT
  Programming Lang: Python
  Description : clean customisable Sphinx documentation theme

 Furo is a clean customisable Sphinx documentation theme ...
  - Intentionally minimal — the most important thing is the content,
not the scaffolding around it.
  - Responsive — adapting perfectly to the available screen space,
to work on all sorts of devices.
  - Customisable — change the color palette, font families, logo and more!
  - Easy to navigate — with carefully-designed sidebar navigation and
inter-page links.
  - Good looking content — through clear typography and well-stylised elements.
  - Good looking search — helps readers find what they want quickly.
  - Biased for smaller docsets — intended for smaller documentation sets,
where presenting the entire hierarchy in the sidebar is not overwhelming.

I am maintaining the package sympy (Python package for symbolic calculations),
whose popcon is currently about 5k. Its new upstream version will depend on
packages furo and sphinx-basic-ng, authored by Pradyun Gedam.
The source of the package are available at
https://salsa.debian.org/debian/furo


Bug#1023447: ITP: sphinx-basic-ng -- modern base for Sphinx themes

2022-11-04 Thread Georges Khaznadar
Package: wnpp
Severity: wishlist
Owner: Georges Khaznadar 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: sphinx-basic-ng
  Version : 1.0.0~beta1
  Upstream Author : Pradyun Gedam 
* URL : https://github.com/pradyunsg/sphinx-basic-ng
* License : MIT
  Programming Lang: Python
  Description : modern base for Sphinx themes

 Sphinx-basic-ng is a modern base for Sphinx themes, providing shared
 implementation of common components and a three-column layout to build upon.

I am maintaining the package sympy (Python package for symbolic calculations),
whose
popcon is currently about 5k. Its new upstream version will depend on packages
furo and
sphinx-basic-ng, authored by Pradyun Gedam. The source of the package are
available at
https://salsa.debian.org/debian/sphinx-basic-ng



Re: 回复: rebootstrap status update for Loongarch

2022-11-04 Thread 桑猛
Hi, Ning

Thank you for your support for Loongson powerfully and the previous work. 
We hope to cooperate more in the future, and we can promote the Loongarch 
architecture into the debian community together.


> -原始邮件-
> 发件人: "张 宁" 
> 发送时间:2022-11-04 14:13:02 (星期五)
> 收件人: "debian-devel@lists.debian.org" , 
> "sangm...@loongson.cn" , "Santiago Vila" 
> , "张 宁" , 
> "zhangdan...@loongson.cn" 
> 抄送: 
> 主题: 回复: rebootstrap status update for Loongarch
> 
> Hi, All
> 
> I have updated my rebootstrap fork[0], with fix for newt, base-passwd and 
> perl.
> rebootstrap finishes with report: 
> https://gist.github.com/zhangn1985/790c1ee011b264332ede1aa909b8d3e7
> 
> 
> I'm happy to see more Loongson employees join the process of enable Loongarch 
> in Debian upstream, not downstream fork. This is the main purpose of my 
> recent work.
> 
> With my rebootstrap fork[0], it's easy for Loongson to start, thus I can 
> handover my work to Loongson, and keep silent for a while.
> 
> Loongson, push the community, not pushed by.
> 
> BR.
> Ning.
> 
> [0] https://salsa.debian.org/zhangn1985/rebootstrap
> 
> 
> 
> 
> 
> 
> 
> 
> 发件人: Paul Wise
> 已发送: 2022 年 11 月 4 日 星期五 2:45
> 收件人: Zhang Ning; debian-devel@lists.debian.org; sangm...@loongson.cn; 
> Santiago Vila
> 主题: Re: rebootstrap status update for Loongarch
> 
> 
> 
> 
> On Thu, 2022-11-03 at 18:45 +0800, Zhang Ning wrote:
> 
> 
> 
> > 7, m4, diffutils: need help, I don't know where is correct
> 
> > upstream[1][2], the patch[3][4] is for generated files, but Debian
> 
> > source has these files, thus how can I submit these patch to Debian
> 
> > source? these two packages don't have VCS.
> 
> 
> 
> It is best not to patch generated files, instead they should be
> 
> regenerated from source (and probably removed from the upstream VCS).
> 
> 
> 
> It is best not to patch embedded code copies, instead they should be
> 
> removed from the upstream VCS and tarballs and the system version used.
> 
> 
> 
> In Debian, the dh-autoreconf package is used at build time to
> 
> automatically regenerate all files generated by autotools.
> 
> 
> 
> In Debian, the stack-direction.m4 file is provided by gnulib, but I am
> 
> not sure if that is the canonical place this file is maintained or if
> 
> it is just yet another copy of this file..
> 
> 
> 
>    $ apt-file search stack-direction.m4
> 
>    gnulib: /usr/share/gnulib/m4/stack-direction.m4
> 
> 
> 
> For m4, it seems Santiago Vila disabled dh-autoreconf in debian/rules,
> 
> but there is no indication of the reason for that. So I suggest you
> 
> test what happens when it is enabled and if the build succeeds and has
> 
> no warnings in the log, then open a bug asking for it to be enabled.
> 
>    
> 
> For diffutils, the same issue and solution applies.
> 
> 
> 
> Another solution would be to ask the upstream m4 and diffutils projects to
> 
> make new releases with updated configure and stack-direction.m4 files and
> 
> then file bugs in Debian asking for package updates to the new releases.
> 
> 
> 
> -- 
> 
> bye,
> 
> pabs
> 
> 
> 
> https://wiki.debian.org/PaulWise
> 


本邮件及其附件含有龙芯中科的商业秘密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制或散发)本邮件及其附件中的信息。如果您错收本邮件,请您立即电话或邮件通知发件人并删除本邮件。
 
This email and its attachments contain confidential information from Loongson 
Technology , which is intended only for the person or entity whose address is 
listed above. Any use of the information contained herein in any way 
(including, but not limited to, total or partial disclosure, reproduction or 
dissemination) by persons other than the intended recipient(s) is prohibited. 
If you receive this email in error, please notify the sender by phone or email 
immediately and delete it.