On 2019-02-20 06:19, Adam Borowski wrote:
> On Tue, Feb 19, 2019 at 11:52:49PM +0100, W. Martin Borgert wrote:
> > In my case, it's only 3.3 MiB. And it is only in the source package
> > anyway.
>
> So you can just ship it then.
After clarifying the license(s).
On 2019-02-19 23:41, Holger Levsen wrote:
> On Wed, Feb 20, 2019 at 12:06:30AM +0100, Chris Lamb wrote:
> > Noted, but it is not the size that is the concern, but rather the
> > licensing.
>
> once those (licencing concerns) are resolved, I wonder whether it makes
> sense to provide a fate-testdata
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: r-cran-deoptimr
Version : 1.0
Upstream Author : Eduardo L. T. Conceicao, Martin Maechler
* URL : https://cran.r-project.org/package=DEoptimR
* License : GPL-2+
Programming Lang: GNU R
Des
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: kmerresistance
Version : 2.0+git20180205.26467e9
Upstream Author : , Philip Clausen, Technical University of Denmark
* URL : https://bitbucket.org/genomicepidemiology/kmerresistance
* License
Le lun. 18 févr. 2019 à 21:16, Sebastian Andrzej Siewior
a écrit :
> On 2019-02-18 11:08:30 [+0100], Jérémy Lal wrote:
> > hi !
> Hi,
>
> > It happens that that api breakage has been reverted and is merged in
> > openssl 1.1.1 stable branch:
> >
> https://github.com/openssl/openssl/commit/37857e9
Package: wnpp
Severity: wishlist
Owner: Hanno Stock
* Package name: pandoc-plantuml-filter
Version : 0.1.1
Upstream Author : Timo Furrer
* URL : https://github.com/timofurrer/pandoc-plantuml-filter
* License : MIT
Programming Lang: Python
Description :
[Followups to debian-devel with CC to me, please, as I'm not
subscribed.]
Currently, while the majority of daemons support logging to syslog
and/or journald, a small handful of software ships configured to use its
own logfiles by default. For instance, update-alternatives logs to
/var/log/alternat
Josh Triplett writes:
> While there are *absolutely* configurations in which system
> administrators want to log to arbitrary locations and files, I would
> like to propose that for consistency we should configure software to
> unify logging into syslog and/or journald by default. In particular,
On Wed, Feb 20, 2019 at 02:19:02PM -0800, Russ Allbery wrote:
> Josh Triplett writes:
> > While there are *absolutely* configurations in which system
> > administrators want to log to arbitrary locations and files, I would
> > like to propose that for consistency we should configure software to
>
On Wed, 2019-02-20 at 14:19:02 -0800, Russ Allbery wrote:
> Josh Triplett writes:
> > While there are *absolutely* configurations in which system
> > administrators want to log to arbitrary locations and files, I would
> > like to propose that for consistency we should configure software to
> > un
Hi!
On Mon, 2019-02-18 at 19:37:38 +, Dmitry Bogatov wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Dmitry Bogatov
>
> * Package name : build-alternative
> Version : 0.0.1
> Upstream Author : Dmitry Bogatov
> * Url : https://salsa.debian.org/kaction/buil
On Wed, Feb 20, 2019 at 11:53:24PM +0100, Guillem Jover wrote:
> * The log data is "chroot" specific. This applies to all of the package
> management logs. Logging into syslog would by default not do the right
> thing and would be extremely confusing. I could see adding options
> for dpkg and
Josh Triplett writes:
> Both syslog and journald support multi-line log messages
syslog does not support multi-line log messages in any reasonable way. It
just escapes the newline (if you're lucky) and jams all the lines
together, and is rather likely to break whatever log parser you have on
th
On Wed, Feb 20, 2019 at 02:03:08PM -0800, Josh Triplett wrote:
> While there are *absolutely* configurations in which system
> administrators want to log to arbitrary locations and files, I would
> like to propose that for consistency we should configure software to
> unify logging into syslog and/
On Wed, Feb 20, 2019 at 03:38:41PM -0800, Russ Allbery wrote:
> Josh Triplett writes:
> > Both syslog and journald support multi-line log messages
>
> syslog does not support multi-line log messages in any reasonable way. It
> just escapes the newline (if you're lucky) and jams all the lines
> t
Hi ,
How do you think your readers would benefit from more business education and
career knowledge? We have a free resource that we would like to share on your
website. We would appreciate the opportunity to be a guest contributor and
provide content for your website.
Study.com is an onlin
16 matches
Mail list logo
