Bug#988833: ITP: python-pyhcl -- HCL configuration parser for python

2021-05-20 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: python-pyhcl
  Version : 0.4.4
  Upstream Author : Dustin Spicuzza 
* URL : https://github.com/virtuald/pyhcl
* License : MPL-2.0
  Programming Lang: Python
  Description : HCL configuration parser for python

 This Python module implements a parser for HCL (HashiCorp Configuration
 Language: https://github.com/hashicorp/hcl). This implementation aims to be
 compatible with the original golang version of the parser.
 .
 The grammar and many of the tests/fixtures were copied/ported from the golang
 parser into pyhcl.

I'm intending to package python-hvac (ie: a python module to access
Hashicorp Vault), and this is a main dependency of it.



Re: How to commit a new architecture like RISC-V

2021-05-20 Thread Helmut Grohne
Hi,

On Thu, May 20, 2021 at 02:52:32PM +0800, zhangjialing wrote:
> the upstream is not support now , the patch is in our local repository.

I fear that this is a very bad basis to bootstrap Debian from. I
strongly recommend deferring a Debian port and upstreaming first.

If you want to proceed anyway, you'll pay a lot of maintenance cost.
You'll be maintaining a Debian derivative. You'll include your patches
and build it for a powerful existing architecture (most commonly amd64)
to cross bootstrap from. Then you can use the existing bootstrap
tooling (rebootstrap) and adapt it to use your derivative instead of
Debian.

So where does the maintenance cost come from? Debian is a moving target
and whenever it changes, you get to rebase your patches. rebootstrap
targets unstable. You'll be patching it. Either you'll be continuously
rebasing your rebootstrap fork or you'll be solving all of the generic
issues that I am solving yourself. Effectively, you'll be duplicating a
ton of work. Expect that it a full time employment just to keep in sync.
That's the overhead, not the development cost. Or you choose to not keep
in sync with Debian and then you'll have to effectively redo the whole
bootstrap once you start mainlining. Beyond this, you'll be unable to
use Debian infrastructure (e.g. jenkins.debian.net).

Or you may choose to go the significantly cheaper route and upstream
your patches now. Yes, it'll take time, but you're still faster that
way.

Helmut



Bug#988839: ITP: python-icmplib -- forge ICMP packets and make your own ping and traceroute

2021-05-20 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: python-icmplib
  Version : 2.1.1
  Upstream Author : Valentin BELYN 
* URL : https://github.com/ValentinBELYN/icmplib
* License : GPL-3
  Programming Lang: Python
  Description : forge ICMP packets and make your own ping and traceroute

 icmplib is an implementation of the ICMP protocol in Python. It is possible to
 use the built-in functions or to build your own. It features:
  * ready-to-use functions such as: ping, multiping and traceroute.
  * multithreaded functions (like multiping).
  * runs without root privileges.
  * ICMPv4 and ICMPv6 support.
  * Broadcast support.
  * No dependency.



Bug#988840: ITP: python-omegaconf -- hierarchical configuration from multiple sources

2021-05-20 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 
X-Debbugs-Cc: debian-devel@lists.debian.org

* Package name: python-omegaconf
  Version : 2.1.0~rc1
  Upstream Author : Omry Yadan 
* URL : https://github.com/omry/omegaconf
* License : BSD-3-clause
  Programming Lang: Python
  Description : hierarchical configuration from multiple sources

 OmegaConf is a hierarchical configuration system, with support for merging
 configurations from multiple sources (YAML config files, dataclasses/objects
 and CLI arguments) providing a consistent API regardless of how the
 configuration was created.



Bug#988864: ITP: emacs-doom-themes -- opinionated pack of modern Emacs color-themes

2021-05-20 Thread Raúl Benencia
Package: wnpp
Severity: wishlist
Owner: Raúl Benencia 
X-Debbugs-Cc: debian-devel@lists.debian.org, r...@kalgan.cc

* Package name: emacs-doom-themes
  Version : 2.1.6+git20210505.4d24728
  Upstream Author : Henrik Lissner 
* URL : https://github.com/hlissner/emacs-doom-themes
* License : MIT
  Programming Lang: Emacs Lisp
  Description : opinionated pack of modern Emacs color-themes

DOOM Themes is an opinionated UI plugin and pack of themes.

The flagship themes are:
 - doom-one: inspired by Atom's One Dark themes
 - doom-one-light: light version of doom-one
 - doom-vibrant: a slightly more vibrant version of doom-one

Additionally, DOOM Themes includes 40+ extra themes.

I intend to maintain this package as part of the Debian Emacsen team.

The “emacs-” prefix is left on the source package name to avoid
confusions with the Doom game. The binary package name will be
“elpa-doom-themes”.

-- 
Raúl Benencia

signature.asc
Description: PGP signature


Bug#988879: ITP: grengine -- engine for running and embedding Groovy in a Java virtual machine

2021-05-20 Thread Pierre Gruet
Package: wnpp
Severity: wishlist
Owner: Debian-java team 
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-j...@lists.debian.org

* Package name: grengine
  Version : 3.0.0
  Upstream Author : Alain Stalder
* URL : https://www.artecat.ch/grengine
* License : Apache-2.0
  Programming Lang: Java
  Description : engine for running and embedding Groovy in a Java virtual 
machine

Grengine allows one to run Groovy code in a Java VM, in a way that is quick,
highly configurable and thread-safe. When the default behavior does not suit
the users' needs, classes can be overridden to change the way the framework
behaves. Even without writing new classes, there are ways to configure the
engine quite a lot.

This package will be team-maintained inside the Debian-java team.
Right now it is needed as a dependency of nextflow.



Re: Bug#988864: ITP: emacs-doom-themes -- opinionated pack of modern Emacs color-themes

2021-05-20 Thread Adam Borowski
On Thu, May 20, 2021 at 08:01:24AM -0700, Raúl Benencia wrote:
> * Package name: emacs-doom-themes
> * URL : https://github.com/hlissner/emacs-doom-themes
>   Description : opinionated pack of modern Emacs color-themes
> 
> DOOM Themes is an opinionated UI plugin and pack of themes.
> Additionally, DOOM Themes includes 40+ extra themes.
[...]
> The “emacs-” prefix is left on the source package name to avoid
> confusions with the Doom game. The binary package name will be
> “elpa-doom-themes”.

So I read this with half on an eye while watching something else,
get excited... then I see "emacs".  Boo :( :p


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ Being wise is hard, but wise-ass... ooh, this one I can deliver!
⠈⠳⣄
y



Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net

2021-05-20 Thread Calum McConnell
You may have noticed that you didn't get any responses.  Your message was
caught by my spamfilter, and was furthermore not very clear.

As for your error, it seems likely that there is an error with the
internet connection.  Why and how I cannot tell you, as there is not
enough information


signature.asc
Description: This is a digitally signed message part


Work-needing packages report for May 21, 2021

2021-05-20 Thread wnpp
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.

Total number of orphaned packages: 1227 (new: 0)
Total number of packages offered up for adoption: 206 (new: 0)
Total number of packages requested help for: 61 (new: 0)

Please refer to https://www.debian.org/devel/wnpp/ for more information.



No new packages have been orphaned, but a total of 1227 packages are
orphaned.  See https://www.debian.org/devel/wnpp/orphaned
for a complete list.



No new packages have been given up for adoption, but a total of 206 packages
are awaiting adoption.  See https://www.debian.org/devel/wnpp/rfa_bypackage
for a complete list.



For the following packages help is requested:

   apache2 (#910917), requested 950 days ago
 Description: Apache HTTP Server
 Reverse Depends: apache2 apache2-ssl-dev apache2-suexec-custom
   apache2-suexec-pristine backuppc bfh-container-server
   courier-webadmin cvsweb debbugs-web doc-central (139 more omitted)
 Installations reported by Popcon: 95952
 Bug Report URL: https://bugs.debian.org/910917

   asciio (#968843), requested 271 days ago
 Description: dynamically create ASCII charts and graphs with GTK+2
 Installations reported by Popcon: 77
 Bug Report URL: https://bugs.debian.org/968843

   aufs (#963191), requested 334 days ago
 Description: driver for a union mount for Linux filesystems
 Reverse Depends: fsprotect
 Installations reported by Popcon: 12255
 Bug Report URL: https://bugs.debian.org/963191

   autopkgtest (#846328), requested 1632 days ago
 Description: automatic as-installed testing for Debian packages
 Reverse Depends: debci-worker sbuild-qemu
 Installations reported by Popcon: 1231
 Bug Report URL: https://bugs.debian.org/846328

   balsa (#642906), requested 3525 days ago
 Description: An e-mail client for GNOME
 Installations reported by Popcon: 664
 Bug Report URL: https://bugs.debian.org/642906

   cargo (#860116), requested 1500 days ago
 Description: Rust package manager
 Reverse Depends: dh-cargo
 Installations reported by Popcon: 2253
 Bug Report URL: https://bugs.debian.org/860116

   courier (#978755), requested 140 days ago
 Description: Courier mail server
 Reverse Depends: courier-faxmail courier-filter-perl courier-imap
   courier-ldap courier-mlm courier-mta courier-pcp courier-pop
   courier-webadmin couriergrey (3 more omitted)
 Installations reported by Popcon: 1007
 Bug Report URL: https://bugs.debian.org/978755

   cron (#984736), requested 74 days ago
 Description: new maintainer need
 Reverse Depends: apticron autolog backintime-common btrfsmaintenance
   buildd checksecurity clamtk cricket email-reminder exim4-base (20
   more omitted)
 Installations reported by Popcon: 203125
 Bug Report URL: https://bugs.debian.org/984736

   cyrus-imapd (#921717), requested 832 days ago
 Description: Cyrus mail system - IMAP support
 Reverse Depends: cyrus-admin cyrus-caldav cyrus-clients cyrus-dev
   cyrus-imapd cyrus-murder cyrus-nntpd cyrus-pop3d cyrus-replication
 Installations reported by Popcon: 424
 Bug Report URL: https://bugs.debian.org/921717

   cyrus-sasl2 (#799864), requested 2066 days ago
 Description: authentication abstraction library
 Reverse Depends: 389-ds-base adcli autofs-ldap cyrus-caldav
   cyrus-clients cyrus-common cyrus-dev cyrus-imapd cyrus-imspd
   cyrus-murder (78 more omitted)
 Installations reported by Popcon: 202597
 Bug Report URL: https://bugs.debian.org/799864

   dbad (#947550), requested 509 days ago
 Description: dnsmasq-based ad-blocking using pixelserv
 Bug Report URL: https://bugs.debian.org/947550

   debtags (#962579), requested 344 days ago
 Description: Debian Package Tags support tools
 Reverse Depends: packagesearch
 Installations reported by Popcon: 1494
 Bug Report URL: https://bugs.debian.org/962579

   dee (#831388), requested 1770 days ago
 Description: model to synchronize mutiple instances over DBus
 Reverse Depends: dee-tools gir1.2-dee-1.0 gir1.2-unity-7.0
   libdee-dev libunity-dev libunity-protocol-private0 libunity-tools
   libunity9 zeitgeist-core
 Installations reported by Popcon: 26598
 Bug Report URL: https://bugs.debian.org/831388

   developers-reference (#759995), requested 2455 days ago
 Description: guidelines and information for Debian developers
 Installations reported by Popcon: 4618
 Bug Report URL: https://bugs.debian.org/759995

   devscripts (#800413), requested 2060 days ago
 Description: scripts to make the life of a Deb

Re: How to commit a new architecture like RISC-V

2021-05-20 Thread zhangjialing



在 2021/5/20 下午5:42, Helmut Grohne 写道:

Hi,

On Thu, May 20, 2021 at 02:52:32PM +0800, zhangjialing wrote:

the upstream is not support now , the patch is in our local repository.

I fear that this is a very bad basis to bootstrap Debian from. I
strongly recommend deferring a Debian port and upstreaming first.


Hi, I have known upstreaming first , I will make a plan for this debian 
port .


Please, when we upstreaming our patch , Is there a version limit for the 
soft like gcc ,glibc


when the upstream work done , what is the next.


If you want to proceed anyway, you'll pay a lot of maintenance cost.
You'll be maintaining a Debian derivative. You'll include your patches
and build it for a powerful existing architecture (most commonly amd64)
to cross bootstrap from. Then you can use the existing bootstrap
tooling (rebootstrap) and adapt it to use your derivative instead of
Debian.

So where does the maintenance cost come from? Debian is a moving target
and whenever it changes, you get to rebase your patches. rebootstrap
targets unstable. You'll be patching it. Either you'll be continuously
rebasing your rebootstrap fork or you'll be solving all of the generic
issues that I am solving yourself. Effectively, you'll be duplicating a
ton of work. Expect that it a full time employment just to keep in sync.
That's the overhead, not the development cost. Or you choose to not keep
in sync with Debian and then you'll have to effectively redo the whole
bootstrap once you start mainlining. Beyond this, you'll be unable to
use Debian infrastructure (e.g. jenkins.debian.net).

Or you may choose to go the significantly cheaper route and upstream
your patches now. Yes, it'll take time, but you're still faster that
way.

Helmut




Re: How to commit a new architecture like RISC-V

2021-05-20 Thread Geert Stappers
On Fri, May 21, 2021 at 09:07:10AM +0800, zhangjialing wrote:
> 在 2021/5/20 下午5:42, Helmut Grohne 写道:
> > Hi,
> > 
> > On Thu, May 20, 2021 at 02:52:32PM +0800, zhangjialing wrote:
> > > the upstream is not support now , the patch is in our local repository.
> > I fear that this is a very bad basis to bootstrap Debian from. I
> > strongly recommend deferring a Debian port and upstreaming first.
> 
> Hi,
> 
> I have known upstreaming first , I will make a plan for this debian port.

OK


> Please, when we upstreaming our patch , Is there a version limit for the
> soft like gcc ,glibc

New features  (new architectures)  are added to latest version.
Talk and keep talking with upstream project members, become upstream
project member. In general talk and keep talking with project members,
become a project member. Express that you are stakeholder, express that
that you are aware of the mutual benefit of having another instruction
set architecture added.

So yes, there is a limit for the software version of gcc and glibc.
It most be recent.
 

Groeten
Geert Stappers
-- 
Silence is hard to parse