On Tue, 22 Dec 2020, Emilio Pozuelo Monfort wrote:
> I have released this to stretch and jessie (after some testing on the latter).
Thanks!
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (
On Wed, 2 Dec 2020, Emilio Pozuelo Monfort wrote:
> Let me know how those tests go and we can proceed from there.
It builds, with the usual “most tests pass”, and the test
program I threw at it also works.
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tar
1/debian/changelog2020-12-02 09:51:35.0
+0100
+++ openjdk-8-8u275-b01/debian/changelog2020-12-02 11:15:53.0
+0100
@@ -1,3 +1,10 @@
+openjdk-8 (8u275-b01-1~deb9u1) stretch-security; urgency=medium
+
+ * Team upload.
+ * Provide 8u275-b01 (GA) regression fixes
+
+ --
Hi (E)LTS-people,
I’ve just uploaded an OpenJDK 8 regression update to sid,
sponsored by my employer (as below). (I’m also building locally
for buster, wheezy and various *buntu releases, so all possible
systems I may encounter are covered, which is why I’m invested.)
Would it help if I also prep
On Tue, 22 Jan 2019, Julian Andres Klode wrote:
> > jessie/updates! Using stable/updates will break the system
> > and keep back apt!
>
> Sorry, I missed that bit while updating the email from the DSA :(
Don't worry, this happens, we're all humans, but please
send an updated announcement quickly
On Tue, 22 Jan 2019, Julian Andres Klode wrote:
> This is known to break some proxies when used against security.debian.org. If
> that happens, people can switch their security APT source to use:
>
> deb http://cdn-fastly.deb.debian.org/debian-security stable/updates main
jessie/updates! Using
Hi!
Frank Richter wrote:
> --- a/sesman/libscp/libscp_v0.c 2017-12-12 14:07:58.0 +0100
> +++ b/sesman/libscp/libscp_v0.c 2017-12-12 14:09:16.0 +0100
> @@ -203,7 +203,7 @@
>
> /* reading username */
> in_uint16_be(c->in_s, sz);
> -buf[sz]=g_new0(char, sz);
.13+real/debian/changelog cvs-1.12.13+real/debian/changelog
--- cvs-1.12.13+real/debian/changelog
+++ cvs-1.12.13+real/debian/changelog
@@ -1,3 +1,9 @@
+cvs (2:1.12.13+real-9+deb7u1) wheezy-security; urgency=high
+
+ * Fix CVE-2017-12836 (Closes: #871810)
+
+ -- Thorsten Glaser Sat, 12 Aug 2017 19:23:10 +0200
+
cvs (2:1.12.13+real-9) unstable; urgency=low
* Fix watch file: mange Epoch away, too
On Thu, 27 Jul 2017, Adam Weremczuk wrote:
> deb http://ftp.debian.org/debian wheezy-backports main
No. Not backports, just the regular LTS updates.
https://wiki.debian.org/LTS
> How to I hard prove it and convince the external company flagging it on our
> server?
Tell them to not look at upst
On Thu, 27 Jul 2017, Adam Weremczuk wrote:
> These are the vulnerability I'm referring to and they have been addressed in
> OpenSSH versions 6.6 and 7.2p2:
That’s *upstream* version numbers. As Roberto said, the LTS team
will take those changes (and *only* those security-related fixes),
backport
Brian May dixit:
>Am I correct in my understanding that upstream Lynx development has no
>publicly accessible revision control system (cvs, svn, git, etc) for
>hosting their source code?
Yes, Tom Dickey (lynx, ncurses, xterm, cdk, …) uses PRCS, which
is a single-user system like RCS AIUI and does
On Fri, 20 May 2016, Moritz Muehlenhoff wrote:
> mediawiki has a new maintainer (Kunal Mehta), the new LTS version is
> currently in NEW.
>
> Kunal is one of the core upstream developers of mediawiki.
That’s good to hear!
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bon
On Tue, 17 May 2016, Antoine Beaupré wrote:
> >> Actually, before we do that: did we actually agree that we would not
> >> support mediawiki in wheezy? That's news to me, and it's part of the
> >> sponsored packages list...
The version of mediawiki used is hopelessly outdated, unfortunately.
But
13 matches
Mail list logo
