Le mer. 10 avr. 2019 à 13:24, Emilio Pozuelo Monfort
a écrit :
>
> JFTR, jessie-updates is back.
>
Thanks !
Le mer. 3 avr. 2019 à 12:44, Jonas Meurer a écrit :
> Informing users about ending security support (e.g. by local
> notifications) could definitely be improved - but that's a separate topic.
>
We should definitely fork this discussion into a new subject. However
I wonder if it should be created
Le mar. 2 avr. 2019 à 15:09, Matus UHLAR - fantomas
a écrit :
>
> >> On 4/1/19 8:14 PM, Andy Smith wrote:
> >> >I do understand that re-adding an empty jessie-updates directory
> >> >will silence a lot of warnings from apt update, and thus would avoid
> >> >the questions from end users that I have
Le lun. 1 avr. 2019 à 16:04, Emilio Pozuelo Monfort a écrit :
>
> On 01/04/2019 15:51, Pierre Fourès wrote:
> > Thanks Holger,
> >
> > If I understood good, this mean that tzdata will get updated through
> > "deb http://security.debian.org/ jessie/updates mai
) even if it doesn't goes through the way it used to ?
Le lun. 1 avr. 2019 à 15:40, Holger Levsen a écrit :
>
> On Mon, Apr 01, 2019 at 02:29:23PM +0200, Pierre Fourès wrote:
> > Now that Jessie is in LTS and that jessie-updates/ is gone, does this
> > also mean there
#x27;s not
from security updates ?
Regards,
Pierre.
Le ven. 29 mars 2019 à 17:02, Adam D. Barratt
a écrit :
>
> On Fri, 2019-03-29 at 11:13 +0100, Pierre Fourès wrote:
> > The way I understand it, but I asked for clarification and
> > confirmation in my previous message [1], is t
Le ven. 29 mars 2019 à 10:11, Matus UHLAR - fantomas
a écrit :
>
> >>On 27.03.19 11:20, Bernie Elbourn wrote:
> >>>If it is possible to wiz up a blank jessie-updates this will save me
> >>>visiting a bunch of systems throwing apt errors in next few days.
>
> >On 2019-03-27 11:50, Matus UHLAR - fan
Le mer. 27 mars 2019 à 14:52, Adam D. Barratt
a écrit :
>
> Packages aren't moved from -updates to (old)stable, they're moved from
> p-u. Packages only get removed from -updates following manual action
> from a Release Team member.
>
> In the case of jessie, it appears there was still at least an
Le mer. 27 mars 2019 à 14:02, Emilio Pozuelo Monfort
a écrit :
> Yes, I talked to them earlier today and they agreed to bringing it back to
> avoid
> these problems on users that have jessie-updates on their sources.list.
That would be wonderful to ease the transition in the LTS phase of Jessie.
Le mar. 26 mars 2019 à 23:33, Markus Koschany a écrit :
> You only need the following lines in your sources.list. The -proposed
> and -updates repositories are not used in LTS. We publish all our
> updates via jessie-security.
> I agree that this change should have been better communicated on the
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 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
12 matches
Mail list logo
