Bug#950475: ITP: puppet-module-puppetlabs-augeas-core -- Puppet module for Augeas Core

2020-02-02 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: puppet-module-puppetlabs-augeas-core
  Version : 1.0.5
  Upstream Author : Puppet Labs
* URL : https://github.com/puppetlabs/puppetlabs-augeas_core
* License : Apache-2.0
  Programming Lang: Puppet, Ruby
  Description : Puppet module for Augeas Core

 Puppet lets you centrally manage every important aspect of your system using a
 cross-platform specification language that manages all the separate elements
 normally aggregated in different files, like users, cron jobs, and hosts,
 along with obviously discrete elements like packages, services, and files.
 .
 The augeas_core module is used to manage configuration files using Augeas.
 This module is suitable for any host for which there are Augeas libraries and
 ruby bindings.

Note: This package will be needed to switch to Puppet 6, as Puppet 5 and
lower used to have it embedded.



Bug#950480: ITP: puppet-module-puppetlabs-cron-core -- Puppet module for installing and managing cron resources

2020-02-02 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: puppet-module-puppetlabs-cron-core
  Version : 1.0.3
  Upstream Author : Puppet labs Inc.
* URL : https://github.com/puppetlabs/puppetlabs-cron_core
* License : Apache-2.0
  Programming Lang: Puppet, Ruby
  Description : Puppet module for installing and managing cron resources

 Puppet lets you centrally manage every important aspect of your system using a
 cross-platform specification language that manages all the separate elements
 normally aggregated in different files, like users, cron jobs, and hosts,
 along with obviously discrete elements like packages, services, and files.
 .
 The cron_core module installs and manages cron resources.

Note: This package is needed to transition to the Puppet 6 release.



Re: Heads up: persistent journal has been enabled in systemd

2020-02-02 Thread Simon khng
Hi,

Not sure if stated in any documentation, but I will ask here since it is
easier to get clarification.

Why was rsyslog used as the persistent storage instead of journald for
previous Debian distribution?

I did not check but is the current journald temp session log storing data
in binary format maybe? Since it was stated in the email that users can use
other log package if text format is preferable.

On that topic, why use the network manager package instead of the networkd?
This is actually a similar situation for current stable of Debian.

Simon

On Sat, Feb 1, 2020, 11:24 AM Michael Biebl  wrote:

> Hi,
>
> with today's upload of systemd 244.1-2 I finally enabled persistent
> journal by default [1]. It has been a long requested feature.
>
> The package will create a directory /var/log/journal on upgrades and new
> installs, which enables persistent journal in so called auto mode.
>
> If you decide, that you want to disable the persistent journal again,
> you can run:
> journalctl --relinquish-var; rm -rf /var/log/journal
>
> Future package updates will respect this choice and not re-create the
> directory. You can, of course, also configure this explicitly via the
> Storage= option in journald.conf.
>
> Depending on how it goes, I might ask the ftp-masters to lower the
> priority of rsyslog from important to optional, so it would no longer be
> installed by default on new bullseye installations.
> This would avoid, that we store log messages twice on disk.
> Users that prefer text logs can of course still install rsyslog by
> default (or their syslogger of choice).
> Alternative init systems might consider adding a Recommends on a syslog
> implementation of their choice or creating a task, which would pull in a
> syslogger.
>
> Here are some resources that you might find useful:
> - man journald.conf
>   https://www.freedesktop.org/software/systemd/man/journald.conf.html#
> - man journalctl
>   https://www.freedesktop.org/software/systemd/man/journalctl.html#
> - man systemd-journald.service
>   https://www.freedesktop.org/software/systemd/man/systemd-journald.html#
>
> Regards,
> Michael
>
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717388
>
>


Bug#950492: ITP: notcurses -- Character-mode graphics and TUI library

2020-02-02 Thread Nick Black
Package: wnpp
Severity: wishlist
Owner: Nick Black 

* Package name: notcurses
  Version : 1.1.4
  Upstream Author : Nick Black 
* URL : https://nick-black.com/dankwiki/index.php/notcurses
* License : Apache-2.0
  Programming Lang: C, C++, Python
  Description : Character-mode graphics and TUI library

 notcurses facilitates the creation of modern TUI programs,
 making full use of Unicode and 24-bit direct color. It presents
 an API similar to that of Curses, and rides atop libtinfo.

Work on notcurses began in November of 2019, and it has had Debian-compatible
infrastructure (debhelper compat level 12) from the beginning. As of February
2020, it is rapidly stabilizing, and being used in several tools. I've
rewritten my "growlight" disk management tool using notcurses instead of
ncurses, cutting out several thousand lines of UI code along the way. Nestopia
is about to merge notcurses support (coming out of maintenance mode to do so).
I'm working on a console SDR visualization tool that will make working with
remote SDRs much more pleasant, and expect to release it soon.

Sid/unstable debs are available (and have been available for weeks) in my repo
at https://www.dsscaw.com/apt (this repo is available in Wouter Verhelst's
extrepo tool). The Debian packaging that I currently have can be seen here:
https://github.com/dankamongmen/notcurses/tree/master/debian

Notcurses can be regarded as a successor to ncurses. It provides much of the
functionality of that package, with major improvements IMHO regarding Unicode,
multithreading, and color support. 24-bit RGB with two bits of transparency is
the fundamental color space, and input/output are entirely based off UTF8 and
Unicode's Extended Grapheme Clusters. I've written many thousand lines of
ncurses code in my life, and expect to write no more--notcurses will entirely
supplant it in my projects. ncurses is a venerable, robust library, with a
fantastic maintainer in Thomas E. Dickey, but it's fundamentally bound to
X/OSI. It's time to move past 90s-era TUI APIs.

As for maintaining the package, I've written 90%+ of the code in notcurses, and
intend to maintain it for the long haul. I'm actively committed to maintaining
the Debian/Ubuntu packaging, and indeed hope to use it as a springboard towards
Debian Developer status.

notcurses has been included in Arch's AUR since its 0.4.0 release in November
2019.



Re: Heads up: persistent journal has been enabled in systemd

2020-02-02 Thread Anthony DeRobertis



On February 2, 2020 12:02:33 PM UTC, Simon khng  
wrote:

>Why was rsyslog used as the persistent storage instead of journald for
>previous Debian distribution?

rsyslog has been the default Debian log storage since before switching to 
systemd, possibly since before systemd existed (it was syslogd, but would have 
to check if it was rsyslog or some other implementation).



Re: Heads up: persistent journal has been enabled in systemd

2020-02-02 Thread Michael Stone

On Sun, Feb 02, 2020 at 02:35:19PM +, Anthony DeRobertis wrote:

On February 2, 2020 12:02:33 PM UTC, Simon khng  
wrote:

Why was rsyslog used as the persistent storage instead of journald for
previous Debian distribution?


rsyslog has been the default Debian log storage since before switching to 
systemd, possibly since before systemd existed (it was syslogd, but would have 
to check if it was rsyslog or some other implementation).


Way back at the beginning there was syslogd, that got combined early on 
with klogd into the sysklogd package, rsyslogd replaced it on default 
installs in lenny (released 2009). So yes, the reason is that it 
predates systemd. :)




Re: News about the debhelper toolchain

2020-02-02 Thread Niels Thykier
Paul Wise:
> On Sat, Feb 1, 2020 at 2:39 PM Niels Thykier wrote:
> 
>>  * debhelper generate a temporary writable directory for $HOME
>>and $XDG_RUNTIME_DIR plus clear all remaining XDG_* variables.
>>This simplifies packaging of tools that insist on writing to
>>$HOME.
> 
> What is the right approach for disabling this locally (in
> sbuild/pbuilder rather than in the package) in case someone wants to
> detect and fix such problems rather than papering over them with this
> workaround?
> 

Currently, there is no way do this for package using compat 13.  I am
happy to review patches for adding such a feature (e.g. via
DEB_BUILD_OPTIONS).



Bug#950497: ITP: puppet-module-puppetlabs-host-core -- Puppet module for managing /etc/hosts file

2020-02-02 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: puppet-module-puppetlabs-host-core
  Version : 1.0.3
  Upstream Author : Puppet labs Inc.
* URL : https://github.com/puppetlabs/puppetlabs-host_core
* License : Apache-2.0
  Programming Lang: Puppet, Ruby
  Description : Puppet module for managing /etc/hosts file

 Puppet lets you centrally manage every important aspect of your system using a
 cross-platform specification language that manages all the separate elements
 normally aggregated in different files, like users, cron jobs, and hosts,
 along with obviously discrete elements like packages, services, and files.
 .
 The host_core module is used to manage host entries in a hosts file. For most
 systems, the hosts file is located in /etc/hosts.

Note: this package will be needed for puppet 6, which is not embedding this
code anymore.



Bug#950523: ITP: golang-gopkg-hlandau-acmeapi.v2 -- ACME v2 (RFC 8555) client library for Go

2020-02-02 Thread Peter Colberg
Package: wnpp
Severity: wishlist
Owner: Peter Colberg 

* Package name: golang-gopkg-hlandau-acmeapi.v2
  Version : 2.0.1-1
  Upstream Author : Hugo Landau
* URL : https://github.com/hlandau/acmeapi
* License : Expat
  Programming Lang: Go
  Description : ACME v2 (RFC 8555) client library for Go

This library implements the final version of the ACME specification.

https://tools.ietf.org/html/rfc8555



Re: binutils: add host64-target32 package

2020-02-02 Thread YunQiang Su
On Mon, 3 Feb 2020 14:22:49 +0800 YunQiang Su 
wrote:
> Package: binutils
> Version: 2.34-2
> X-Debug-Cc: debian-devel@lists.debian.org
> 
> Since we meet lots of packages ftbfs on 32bit ports due to 2GB/3GB
> and then virtual memory exhausted
> 
> We had some discuss here:
>https://lists.debian.org/debian-devel/2019/08/msg00171.html
> 
> The patch is attached and submit as a PR
> https://salsa.debian.org/toolchain-team/binutils/merge_requests/5
> 
> 
> This package is built with multilib, and with option --host 64bit
> --target 32bit It diverts non-multiarch programs with dpkg-divert as
> c++filt dwp elfedit ld.bfd ld.gold Add a with_host64 option --
default
> off
> 
> We will have a src:binutils64, while will use these code.

For gcc we also need gcc64 package.

> 
> 
> -- 
> YunQiang Su