-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 21:29:45 -0700
Source: simple-cdd
Architecture: source
Version: 0.6.7
Distribution: unstable
Urgency: medium
Maintainer: Simple-CDD Developers
Changed-By: Vagrant Cascadian
Closes: 909561 918102 919572 928703
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 29 May 2019 18:05:30 -0400
Source: elpy
Binary: elpa-elpy
Architecture: source all
Version: 1.28.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team
Changed-By: Nicholas D Steeves
Description:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 30 May 2019 02:19:31 +
Source: zfs-linux
Architecture: source
Version: 0.8.0-2
Distribution: experimental
Urgency: high
Maintainer: Debian ZFS on Linux maintainers
Changed-By: Mo Zhou
Changes:
zfs-linux (0.8.0-2)
Hi,
On 2019-05-21 23:52, Paul Wise wrote:
> Has anyone repeated the training of Mozilla DeepSpeech for example?
By chance I found a paper from a pile of papers (that attacks AI models)
that Berkeley researchers have successfully attacked DeepSpeech:
https://arxiv.org/pdf/1801.01944.pdf
IHMO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 30 May 2019 10:38:52 +0900
Source: latexmk
Binary: latexmk
Architecture: source all
Version: 1:4.64a-0.1
Distribution: experimental
Urgency: medium
Maintainer: OHURA Makoto
Changed-By: Norbert Preining
Description:
latexmk
On Wed, May 29, 2019 at 8:46 PM Raphaël Halimi wrote:
> What would be the "cleanest" solution according to you ?
The cleanest solution would be to get this code into Linux mainline.
Some discussion of workarounds:
dak needs a way to restrict the availability of arch:all packages to
certain
On Wed, May 29, 2019 at 5:36 PM Mo Zhou wrote:
> For example, many years ago I proposed that we could hire some
> web developers to rewrite our homepage, to make it more good-looking
> (Generally I don't care about superficial stuff but our homepage
> is really old enough. Look at Gentoo's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 30 May 2019 10:28:24 +1000
Source: refpolicy
Binary: selinux-policy-default selinux-policy-dev selinux-policy-doc
selinux-policy-mls selinux-policy-src
Architecture: source all
Version: 2:2.20190201-4
Distribution: unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 19:26:44 -0500
Source: gmsh
Architecture: source
Version: 4.1.5+really4.1.3+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Kurt Kremitzki
Closes: 927808
Changes:
Ian Jackson writes:
> Can you please look through the table below and see if I have covered
> everything you do ?
You have covered the workflows I set up where I have the choice. Thanks.
--
\ “I am amazed, O Wall, that you have not collapsed and fallen, |
`\since you must
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 18:28:35 -0400
Source: gpgme1.0
Architecture: source
Version: 1.13.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian GnuPG Maintainers
Changed-By: Daniel Kahn Gillmor
Changes:
gpgme1.0 (1.13.0-2)
Le 29/05/2019 à 15:41, Ondřej Surý a écrit :
> can’t you just “skip” building the module in DKMS when on unsupported
> architecture?
>
> Install the package on that system would be noop then.
Well, I was so focused on trying to make the package unavailable on
non-ACPI architectures that I
Package: wnpp
Severity: wishlist
Owner: Steffen Moeller
* Package name: wham
* URL : http://www.cs.wisc.edu/wham/
* License : GPL
Programming Lang: C
Description : Wisconsin's High-Throughput Alignment Method
To be team-maintained on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 17:56:13 -0400
Source: fmit
Architecture: source
Version: 1.0.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: John Wright
Changed-By: Boyuan Yang
Closes: 890669
Changes:
fmit (1.0.0-1.1) unstable;
Version: 1:2.22.0~rc1+next.20190529-1
Distribution: experimental
Urgency: low
Maintainer: Gerrit Pape
Changed-By: Jonathan Nieder
Description:
git- fast, scalable, distributed revision control system
git-all- fast, scalable, distributed revision control system (all subpacka
git-cvs
Ian Jackson writes:
> Ian Jackson writes ("Re: Survey: git packaging practices / repository
> format"):
>> David Bremner writes ("Re: Survey: git packaging practices / repository
>> format"):
> ...
>> > With unmodified upstream files in the main branch, plus debian/*, but
>> > usually no
Ian Jackson writes:
> Hi. Thanks for your contributions which I am trying to capture, but I
> don't think I fully understand them.
>
> David Bremner writes ("Re: Survey: git packaging practices / repository
> format"):
>> With modified upstream files in the main branch, plus debian/*, but
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 22:36:54 +0200
Source: libmatroska
Architecture: source
Version: 1.5.2-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Matteo F. Vescovi
Changes:
libmatroska
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 13:02:07 -0700
Source: ltsp
Architecture: source
Version: 5.18.12-3
Distribution: unstable
Urgency: medium
Maintainer: Debian LTSP Maintainers
Changed-By: Vagrant Cascadian
Closes: 929735
Changes:
ltsp
Ian Jackson writes ("Re: Survey: git packaging practices / repository format"):
> David Bremner writes ("Re: Survey: git packaging practices / repository
> format"):
...
> > With unmodified upstream files in the main branch, plus debian/*, but
> > usually no d/patches, I use git-debcherry to
Hi. Thanks for your contributions which I am trying to capture, but I
don't think I fully understand them.
David Bremner writes ("Re: Survey: git packaging practices / repository
format"):
> With modified upstream files in the main branch, plus debian/*, but
> usually no d/patches I use a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 22:05:08 +0200
Source: firejail
Architecture: source
Version: 0.9.60-1
Distribution: experimental
Urgency: medium
Maintainer: Reiner Herrmann
Changed-By: Reiner Herrmann
Changes:
firejail (0.9.60-1)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 21:06:42 +0200
Source: firejail
Architecture: source
Version: 0.9.58.2-2
Distribution: unstable
Urgency: high
Maintainer: Reiner Herrmann
Changed-By: Reiner Herrmann
Closes: 929732 929733
Changes:
firejail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 20:19:55 +0200
Source: libebml
Architecture: source
Version: 1.3.9-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Matteo F. Vescovi
Changes:
libebml (1.3.9-1)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 19:09:43 +0200
Source: sbcl
Architecture: source
Version: 2:1.5.3-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Common Lisp Team
Changed-By: Sébastien Villemot
Changes:
sbcl (2:1.5.3-1)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 13:05:03 -0400
Source: dns-root-data
Architecture: source
Version: 2019052802
Distribution: unstable
Urgency: medium
Maintainer: dns-root-data packagers
Changed-By: Daniel Kahn Gillmor
Changes:
dns-root-data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 29 May 2019 15:47:03 +
Source: cockpit
Architecture: source
Version: 195-1
Distribution: experimental
Urgency: medium
Maintainer: Utopia Maintenance Team
Changed-By: Martin Pitt
Changes:
cockpit (195-1) experimental;
On Wed, May 29, 2019 at 12:20:23PM -0400, Sam Hartman wrote:
> >> Perhaps we should update policy to say that the .orig tarball may
> >> (or even "should") be generated from an upstream release tag
> >> where applicable.
> Andrey> This conflicts with shipping tarball signatures.
>
> "Andrey" == Andrey Rahmatullin writes:
Andrey> On Wed, May 29, 2019 at 02:14:09PM +0100, Ben Hutchings wrote:
>> [...] > My understanding is that this unusual difference between
>> the .orig > tarball and what's in git is an attempt to "square
>> the circle" between > two
On Wed, May 29, 2019 at 02:14:09PM +0100, Ben Hutchings wrote:
> [...]
> > My understanding is that this unusual difference between the .orig
> > tarball and what's in git is an attempt to "square the circle" between
> > two colliding design principles: "the .orig tarball should be upstream's
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 11:01:07 -0400
Source: tcptraceroute
Architecture: source
Version: 1.5beta7+debian-4.1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Martin Zobel-Helas
Changed-By: Boyuan Yang
Closes: 674577 681575
On Wed, 29 May 2019 at 14:14:09 +0100, Ben Hutchings wrote:
> On Wed, 2019-05-29 at 00:39 +0100, Simon McVittie wrote:
> [...]
> > My understanding is that this unusual difference between the .orig
> > tarball and what's in git is an attempt to "square the circle" between
> > two colliding design
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 29 May 2019 23:23:19 +0900
Source: groonga
Architecture: source
Version: 9.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Groonga Project
Changed-By: Kentaro Hayashi
Changes:
groonga (9.0.3-1) unstable;
> "Sam" == Sam Hartman writes:
ke the Software Freedom Conservancy (SFC)'s
Sam> position
Sam> https://sfconservancy.org/blog/2016/feb/25/zfs-and-linux/-UUU:**--F1
Sam> *unsent wide reply to Aron Xu* Bot L50 (Message SC:f MML Abbre
Ah, that's an interesting artifact of how cut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 24 May 2019 14:06:05 +0100
Source: libzorpll
Binary: libzorpll-7.0-1 libzorpll-7.0-1-dbgsym libzorpll-7.0-1-dev libzorpll-dev
Architecture: source amd64 all
Version: 7.0.1.0~alpha1-1.1
Distribution: unstable
Urgency: medium
Hi,
With my Debian ZoL maintainer hat + FTP trainee hat on, I didn't wish
to jump into this topic too early without a in-depth investigation...
On 2019-05-29 14:14, Sam Hartman wrote:
> And if you take the Software Freedom Conservancy (SFC)'s position
>
I hope that we do not choose to open the zfs discussion at this time.
If it does get opened, I think my approach would be to try and educate
the community about the various different viewpoints, find text for GRs
that would allow key stakeholders to believe their positions were
respected and
On Wed, 2019-05-29 at 13:43 +0200, Dan wrote:
> Hi Jonathan,
>
> On Tue, May 28, 2019 at 8:50 PM Jonathan Carter wrote:
> > On 2019/05/28 18:43, Dan wrote:
> > > ZFS 0.8 has been released with lots of improvements, notably encryption.
> >
> > Yep, it's an exciting feature.
> >
> > > Sadly the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 29 May 2019 14:56:05 +0200
Source: nova
Binary: nova-api nova-cells nova-common nova-compute nova-compute-ironic
nova-compute-kvm nova-compute-lxc nova-compute-qemu nova-conductor nova-console
nova-consoleauth
On Wed, May 29, 2019 at 8:55 PM Ian Jackson
wrote:
>
> Ansgar writes ("Re: ZFS in Buster"):
> > Ian Jackson writes:
> > > I think this would be both unwise legally (without seeking additional
> > > legal advice) and rather rude to the kernel upstream whose code is
> > > then being reused without
> On 29 May 2019, at 14:45, Raphaël Halimi wrote:
>
> Hi,
>
> I'm the maintainer of package acpi-call, which is a kernel module
> allowing a user to call ACPI methods. Its build is handled by DKMS.
>
> The module used to build on all architectures, even if it was obviously
> useless on those
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 29 May 2019 21:41:15 +0900
Source: w3m-el-snapshot
Binary: w3m-el-snapshot
Architecture: source all
Version: 1.4.632+0.20190528-1
Distribution: experimental
Urgency: low
Maintainer: Tatsuya Kinoshita
Changed-By: Tatsuya
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 14:55:09 +0200
Source: marsshooter
Architecture: source
Version: 0.7.6-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team
Changed-By: Markus Koschany
Closes: 929513
Changes:
marsshooter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 29 May 2019 14:33:07 +0200
Source: nova
Binary: nova-api nova-cells nova-common nova-compute nova-compute-ironic
nova-compute-kvm nova-compute-lxc nova-compute-qemu nova-conductor nova-console
nova-consoleauth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 13:18:14 +0100
Source: nautilus
Architecture: source
Version: 3.32.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers
Changed-By: Iain Lane
Changes:
nautilus (3.32.1-1)
On Wed, 2019-05-29 at 00:39 +0100, Simon McVittie wrote:
[...]
> My understanding is that this unusual difference between the .orig
> tarball and what's in git is an attempt to "square the circle" between
> two colliding design principles: "the .orig tarball should be upstream's
> official binary
On Tue, 2019-05-28 at 21:14 +0100, Ian Jackson wrote:
> Simon McVittie writes ("Re: Survey: git packaging practices / repository
> format"):
[...]
> > Debian Linux kernel
> > ===
> >
> > Tree contains: an incomplete debian/ directory, notably without d/control,
> > and no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 09 Mar 2019 05:38:15 -0500
Source: totem
Architecture: source
Version: 3.32.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GNOME Maintainers
Changed-By: Jeremy Bicha
Changes:
totem (3.32.0-1)
Package: wnpp
Severity: wishlist
Owner: Steffen Moeller
* Package name: python-geneimpacts
* URL : https://github.com/brentp/geneimpacts
* License : MIT/X
Programming Lang: Python
Description : wraps tools to assess variants in gene sequences
To be
Ansgar writes ("Re: ZFS in Buster"):
> Ian Jackson writes:
> > I think this would be both unwise legally (without seeking additional
> > legal advice) and rather rude to the kernel upstream whose code is
> > then being reused without permission - indeed, contrary to their
> > explicitly stated
> "Ian" == Ian Jackson writes:
Ian> Enrico Weigelt, metux IT consult writes ("Re: Survey: git
Ian> packaging practices / repository format"):
>> I'd call it the 'git-only-workflow' ;-)
Ian> ...
>> It's not in official Debian. I've announced it long go, but
>> nobody
Hi,
I'm the maintainer of package acpi-call, which is a kernel module
allowing a user to call ACPI methods. Its build is handled by DKMS.
The module used to build on all architectures, even if it was obviously
useless on those which don't support ACPI.
Starting with Linux 5.2, what used to be a
Enrico Weigelt, metux IT consult writes ("Re: Survey: git packaging practices /
repository format"):
> On 28.05.19 22:08, Ian Jackson wrote:
> > Please can we leave aside discussion of the merits or otherwise of
> > each of these formats/workflows.
> >
> > Perhaps we can talk about that (again!)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 12:47:33 +0100
Source: nautilus
Architecture: source
Version: 3.30.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers
Changed-By: Iain Lane
Closes: 928054
Changes:
nautilus
Enrico Weigelt, metux IT consult writes ("Re: Survey: git packaging practices /
repository format"):
> I'd call it the 'git-only-workflow' ;-)
...
> It's not in official Debian. I've announced it long go, but nobody
> here really cared. I couldn't even convice debian maintainers for
> little less
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 08:59:35 +
Source: zfs-linux
Architecture: source
Version: 0.8.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian ZFS on Linux maintainers
Changed-By: Mo Zhou
Closes: 928118
Changes:
[moving a discussion from -devel to -project where it belongs]
> "Mo" == Mo Zhou writes:
Mo> Hi,
Mo> On 2019-05-29 08:38, Raphael Hertzog wrote:
>> Use the $300,000 on our bank accounts?
So, there were two $300k donations in the last year.
One of these was earmarked for a DSA
Hi Jonathan,
On Tue, May 28, 2019 at 8:50 PM Jonathan Carter wrote:
> On 2019/05/28 18:43, Dan wrote:
> > ZFS 0.8 has been released with lots of improvements, notably encryption.
>
> Yep, it's an exciting feature.
>
> > Sadly the Linux Kernel has introduced a commit in kernel 4.19 and 5.0
> >
Enrico Weigelt, metux IT consult writes ("Re: Survey: git packaging practices /
repository format"):
> hmm, sounds quite complicated ... anyone here who could explain why
> exactly they're doing it that way ?
>
> by the way: that's IMHO an important information we should also collect:
> why
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 29 May 2019 12:58:48 +0200
Source: network-manager-applet
Architecture: source
Version: 1.8.22-1
Distribution: experimental
Urgency: medium
Maintainer: Utopia Maintenance Team
Changed-By: Michael Biebl
Changes:
On 28.05.19 18:43, Dan wrote:
> Sadly the Linux Kernel has introduced a commit in kernel 4.19 and 5.0> that
> prevents ZFS from using SIMD. The result is that ZFS won't be>
usable in Buster. See the following issue>
https://github.com/zfsonlinux/zfs/issues/8793
We recently had this discussion on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 29 May 2019 12:27:36 +0200
Source: gnome-control-center
Binary: gnome-control-center gnome-control-center-dev gnome-control-center-data
Architecture: source
Version: 1:3.32.2-1
Distribution: experimental
Urgency: medium
Ian Jackson writes:
>
> Main packaging Delta from upstream Tools for manipulating
> git branch represented as delta from upstream,
> contains building .dsc, etc.
>
> Unmodified debian/patches gbp, gbp pq
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 29 May 2019 12:17:37 +0200
Source: rsyslog
Architecture: source
Version: 8.1905.0-2
Distribution: experimental
Urgency: medium
Maintainer: Michael Biebl
Changed-By: Michael Biebl
Changes:
rsyslog (8.1905.0-2) experimental;
On 28.05.19 19:31, Simon McVittie wrote:
Hi,
> Debian Linux kernel
> ===
>
> Tree contains: an incomplete debian/ directory, notably without d/control,
> and no upstream source
> Changes to upstream source are: d/patches only
> Baseline upstream: changelog version => .orig
On 29.05.19 01:39, Simon McVittie wrote:
Hi,
> You might reasonably assume that, but no, they are not. mesa (and probably
> other xorg-team packages) uses v1.0 dpkg-source format combined with
> dh --with quilt, so deliberate Debian changes can be either direct
> changes to the upstream source
Hi,
On 2019-05-29 08:38, Raphael Hertzog wrote:
> Use the $300,000 on our bank accounts?
I totally support the idea that we should find more valuable usage
of our fund. For example, if developers don't have enough time or
don't want to do something difficult, we could hire somebody else
to fix
On 28.05.19 22:08, Ian Jackson wrote:
Hi,
> Please can we leave aside discussion of the merits or otherwise of
> each of these formats/workflows.
>
> Perhaps we can talk about that (again!) at some point, but it tends to
> derail any conversation about git packaging stuff and I don't want
>
On 28.05.19 22:30, Ian Jackson wrote:
> Hi, thanks for replying. You have an interesting workflow which I
> think I need to ask some questions about before I can document it
> fully.
I'd call it the 'git-only-workflow' ;-)
The main reasons behind are:
* i wanna be able to easily rebase onto
On Wed, 29 May 2019, Ansgar wrote:
> On Wed, 2019-05-29 at 10:38 +0200, Raphael Hertzog wrote:
> > On Wed, 29 May 2019, Andrey Rahmatullin wrote:
> > > One of the popular answers to this and some other problems is "nobody sat
> > > down and wrote the code". Not sure what can we do about this class
On Wed, 2019-05-29 at 10:38 +0200, Raphael Hertzog wrote:
> On Wed, 29 May 2019, Andrey Rahmatullin wrote:
> > One of the popular answers to this and some other problems is "nobody sat
> > down and wrote the code". Not sure what can we do about this class of
> > reasons.
>
> Use the $300,000 on
Hi,
On Wed, 29 May 2019, Andrey Rahmatullin wrote:
> One of the popular answers to this and some other problems is "nobody sat
> down and wrote the code". Not sure what can we do about this class of
> reasons.
Use the $300,000 on our bank accounts?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 29 May 2019 06:54:45 +
Source: dh-runit
Architecture: source
Version: 2.8.11
Distribution: experimental
Urgency: medium
Maintainer: Dmitry Bogatov
Changed-By: Dmitry Bogatov
Changes:
dh-runit (2.8.11) experimental;
Ian Jackson writes:
>> > Would it be possible to provide an alternative patched linux kernel
>> > that works with ZFS?
>
> I think this would be both unwise legally (without seeking additional
> legal advice) and rather rude to the kernel upstream whose code is
> then being reused without
On Wed, May 29, 2019 at 08:43:55AM +0200, Andreas Tille wrote:
> IMHO this touches another burning topic: Its not that we do not want to
> provide some PPA equivalent - its just that we do not realise it. I do
> not remember how many years ago we talked about bikesheds (and
> obviously we even
On Mon, May 27, 2019 at 07:54:20AM -0400, Sam Hartman wrote:
> As an example, Ubuntu makes it easy to add side-loaded channels (ppas).
> we don't.
IMHO this touches another burning topic: Its not that we do not want to
provide some PPA equivalent - its just that we do not realise it. I do
not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 29 May 2019 07:56:31 +0200
Source: openjdk-11
Architecture: source
Version: 11.0.4+4-1
Distribution: unstable
Urgency: medium
Maintainer: OpenJDK Team
Changed-By: Matthias Klose
Changes:
openjdk-11 (11.0.4+4-1) unstable;
77 matches
Mail list logo
