Hi,
so I noticed this morning that jessie-updates is gone from the mirrors.
After some research, I found that this was kind of announced in
https://lists.debian.org/debian-devel-announce/2019/03/msg6.html.
Question is now, what should I put in my sources.list? I used
https://wiki.debian.org/LT
On Tue, 26 Mar 2019, Jakob Hirsch wrote:
> Hi,
>
> so I noticed this morning that jessie-updates is gone from the mirrors.
> After some research, I found that this was kind of announced in
> https://lists.debian.org/debian-devel-announce/2019/03/msg6.html.
> Question is now, what should I put
On 2019-03-26 11:37, Alexander Wirt wrote:
>> so I noticed this morning that jessie-updates is gone from the mirrors.
> Its deprecated and unsupported for sime time now, please stop using it.
You mean jessie-updates, right? So I will happily remove it from my
sources.list. So using just the remai
Hi Jakob,
I just stumbled on the same issue. I repported it on debian-user@
instead, in the thread [1]. I also found afterward that it was kind of
announced on debian-devel-announce@ but I would not have thought to
look there neither. But as you said, this is low traffic list, so I
suscribed to it
On Tue, 26 Mar 2019, Jakob Hirsch wrote:
so I noticed this morning that jessie-updates is gone from the mirrors.
After some research, I found that this was kind of announced in
https://lists.debian.org/debian-devel-announce/2019/03/msg6.html.
Question is now, what should I put in my sources.l
Hi,
On 25/03/2019 16:13, Sylvain Beucler wrote:
> On 25/03/2019 16:11, Sylvain Beucler wrote:
>> Hi,
>>
>> I prepared an update for ghostscript.
>> https://people.debian.org/~beuc/lts/ghostscript/
>>
>> Even if we recently rebased to the latest upstream in jessie, the
>> upstream patches did not a
Hi,
(late report, sorry for the delay)
During the month of February, I spent 20.5 hours working on LTS on the following
tasks:
- testing new install media
- CVE triaging
- coturn security update
- ghostscript security update
- firefox-esr security update
- thunderbird security update
- reviewed
On 25/03/2019 18:20, Ben Hutchings wrote:
> On Tue, 2019-03-05 at 22:00 +, Ben Hutchings wrote:
>> On Fri, 2019-03-01 at 14:05 +0100, Emilio Pozuelo Monfort wrote:
> [...]
>>> (It
>>> may be unlikely for old suites to have users with new hardware, however it's
>>> possible and users that don't
On Tue, 2019-03-26 at 17:51 +0100, Emilio Pozuelo Monfort wrote:
> On 25/03/2019 18:20, Ben Hutchings wrote:
> > On Tue, 2019-03-05 at 22:00 +, Ben Hutchings wrote:
> > > On Fri, 2019-03-01 at 14:05 +0100, Emilio Pozuelo Monfort wrote:
> > [...]
> > > > (It
> > > > may be unlikely for old suite
Le mar. 26 mars 2019 à 15:27, Matus UHLAR - fantomas
a écrit :
> It was working since jessie was released, so anyone using jessie will
> apparently have it in sources.list.
>
> I believe one of LTS goals was to continue without need for changing
> sources.list.
As being still active (as part of t
Hi,
Am 26.03.19 um 20:59 schrieb Pierre Fourès:
[...]
> I've got the same understanding of the situation and suspect I'm
> missing nothing as all updates are supposed to be included in the main
> repository of revision 8.11. Nonetheless, I would truly appreciate
> some clear feedback on it that al
Am 26.03.19 um 15:27 schrieb Matus UHLAR - fantomas:
>> On Tue, 26 Mar 2019, Jakob Hirsch wrote:
>>> so I noticed this morning that jessie-updates is gone from the mirrors.
>>> After some research, I found that this was kind of announced in
>>> https://lists.debian.org/debian-devel-announce/2019/03
Hi,
Am 26.03.19 um 15:55 schrieb Sylvain Beucler:
[...]
> Markus, I read in the archives that you backported fixes in earlier
> security uploads - any other tip? :)
I did all the testing myself by setting up a Jessie environment and then
I tested with the POCs and the command line tools to spot a
13 matches
Mail list logo
