On Wed, 2022-01-19 at 18:43 +0200, Thomas Koch wrote:
> My package ships two convenience copies from autoconf-archive in it's
> m4 folder. Should I
In my experience with libpst, it had embedded copies of Python/boost
macros from autoconf-archive that were modified and the modifications
hadn't bee
On 1/19/22 3:13 PM, Bernhard Schmidt wrote:
I agree we should have a look at this (either ntpsec or chrony, both do
NTS), but I think this should be done completely independently of the
ntp.org->ntpsec migration.
+1 that promoting NTS is orthogonal.
If the bigger problems below are solved, it
* Richard Laager [220119 14:34]:
> On 1/19/22 9:49 AM, Bernhard Schmidt wrote:
> > AFAICT other than systemd-timesyncd being installed by default we don't
> > have a "default" NTP daemon in Debian.
>
> I'm not sure how much more "default" it can be than installed by default. So
> I'd say we do ha
On 19.01.22 20:44, Stephan Seitz wrote:
Am Mi, Jan 19, 2022 at 13:34:13 -0600 schrieb Richard Laager:
For people that want something more than systemd-timesyncd, e.g. to
get NTS, I think either are acceptable choices. It seems that the
consensus
Well, most people will use the default NTP se
On 19.01.22 20:34, Richard Laager wrote:
Hi Richard,
+1, except that my position is we already have that answer:
systemd-timesyncd | time-daemon
As default both ntpsec and chrony are challengers.
For people that want something more than systemd-timesyncd, e.g. to get
NTS, I think either ar
Am Mi, Jan 19, 2022 at 13:34:13 -0600 schrieb Richard Laager:
For people that want something more than systemd-timesyncd, e.g. to get
NTS, I think either are acceptable choices. It seems that the consensus
Well, most people will use the default NTP server of the package and
don’t have a NTP s
On 1/19/22 9:49 AM, Bernhard Schmidt wrote:
AFAICT other than systemd-timesyncd being installed by default we don't
have a "default" NTP daemon in Debian.
I'm not sure how much more "default" it can be than installed by
default. So I'd say we do have a default: systemd-timesyncd.
So we shoul
Jonas Smedegaard writes:
> Thanks for elaborating.
> The concern is not licensing, but maintenance. It is covered in Debian
> Policy § 4.13:
> https://www.debian.org/doc/debian-policy/ch-source.html#embedded-code-copies
Debian packages should not make use of these convenience copies unle
Am 19.01.22 um 18:44 schrieb Jonas Smedegaard:
Quoting Stefan Weil (2022-01-19 18:07:28)
As I wrote in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949119#15
autoconf-archive is not needed for building because the two required
files are also provided as part of the Tesseract source tree.
Quoting Stefan Weil (2022-01-19 18:07:28)
> Am 19.01.22 um 17:43 schrieb Thomas Koch:
>
> > I searched but apparently this has not yet been discussed anywhere below
> > lists.debian.org.
> >
> > My package ships two convenience copies from autoconf-archive in it's m4
> > folder. Should I
> >
> >
Am 19.01.22 um 17:43 schrieb Thomas Koch:
I searched but apparently this has not yet been discussed anywhere below
lists.debian.org.
My package ships two convenience copies from autoconf-archive in it's m4
folder. Should I
a) leave these files and add the corresponding data to d/copyright or
Quoting Thomas Koch (2022-01-19 17:43:39)
> I searched but apparently this has not yet been discussed anywhere below
> lists.debian.org.
>
> My package ships two convenience copies from autoconf-archive in it's m4
> folder. Should I
>
> a) leave these files and add the corresponding data to d/c
I searched but apparently this has not yet been discussed anywhere below
lists.debian.org.
My package ships two convenience copies from autoconf-archive in it's m4
folder. Should I
a) leave these files and add the corresponding data to d/copyright or
b) leave these files and don't bother about
Hi,
However, development for ntp.org is slow, upstream still using BitKeeper
is cumbersome, and even the testsuite needs to be fixes on some
architectures for new releases. Both ntpsec and chrony are (from my POV)
the better alternatives now. To a point where I would rather use chrony
for ne
Package: wnpp
Severity: wishlist
Owner: John Goerzen
* Package name: golang-github-kardianos-minwinsvc
Version : 1.0.0-1
Upstream Author : Daniel Theophanes
* URL : https://github.com/kardianos/minwinsvc
* License : BSD-3
Programming Lang: Go
Description
Package: wnpp
Severity: wishlist
Owner: John Goerzen
* Package name: golang-github-arceliar-ironwood
Version : 0.0~git20210619.6ad55ca-1
Upstream Author : Arceliar
* URL : https://github.com/Arceliar/ironwood
* License : MPL-2.0
Programming Lang: Go
Descrip
Package: wnpp
Severity: wishlist
Owner: John Goerzen
* Package name: wireguard-go
Version : 0.0.20220117-1
Upstream Author : Jason A. Donenfeld
* URL : https://git.zx2c4.com/wireguard-go/about/
* License : MIT
Programming Lang: Go
Description : Impleme
Package: wnpp
Severity: wishlist
Owner: John Goerzen
* Package name: golang-golang.zx2c4-go118-netip
Version : 0.0~git2021.a4a02ee-1
Upstream Author : The Go Authors
* URL : TODO
* License : BSD 3-clause
Programming Lang: Go
Description : An extract
Am 19.01.22 um 13:07 schrieb Marc Haber:
On Tue, 18 Jan 2022 21:49:53 +0100, Michael Biebl
wrote:
Fwiw, I'm with Marco here: If systemd-timesyncd (a simple SNTP client
which is enabled by default) doesn't fit your needs, chrony is a great
alternative.
The Beef I have with chrony is that they
On Tue, 18 Jan 2022 21:49:53 +0100, Michael Biebl
wrote:
>Fwiw, I'm with Marco here: If systemd-timesyncd (a simple SNTP client
>which is enabled by default) doesn't fit your needs, chrony is a great
>alternative.
The Beef I have with chrony is that they just implemented the parts of
the protoc
Richard Laager wrote on 19/01/2022:
> On 1/18/22 11:21 AM, Paride Legovini wrote:
> > I'd prefer making ntp a dummy package depending on ntpsec rather than
> > having src:ntpsec takeover bin:ntp.
>
> If I understand correctly, you're suggesting src:ntp builds bin:ntp that
> is a dummy package w
Thank you for your answer!
I still have another two questions:
for CVE-2021-43818 exists a page with information about the vulnerable package,
lxml.
It is written that the package is vulnerable and there is no fix.
This is the download link for one of the vulnerable version:
http://security-cdn.
Am Di, Jan 18, 2022 at 23:16:46 +0100 schrieb Marco d'Itri:
I have no objections if somebody wants to work on packaging ntpsec, but
I do not think that either ntp or ntpsec should be promoted over chrony
nowadays.
Besides from the fact that ntpsec is already packaged: Does chrony
support NTS?
Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: xrt
Version : 2.8.832
Upstream Author : Sonal Santan
* URL : https://github.com/Xilinx/XRT.git
* License : GPL-2.0
Programming Lang: C++
D
24 matches
Mail list logo
