Le mer. 10 avr. 2019 à 13:24, Emilio Pozuelo Monfort
a écrit :
>
> JFTR, jessie-updates is back.
>
Thanks !
On 26/03/2019 11:08, 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 4/2/19 12:59 PM, Andy Smith wrote:
Hi Miroslav,
On Tue, Apr 02, 2019 at 11:53:50AM +0200, Miroslav Skoric wrote:
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
Hi Ben,
On Wed, Apr 03, 2019 at 03:32:10PM +0100, Ben Hutchings wrote:
> On Wed, 2019-04-03 at 00:02 +, Andy Smith wrote:
> > Personally I'm not bothered either way about whether
> > "-updates" remains something that can be in sources.list
> > without causing update errors, but I am more
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
On Wed, 2019-04-03 at 00:02 +, Andy Smith wrote:
> Hi Ben,
>
> On Wed, Apr 03, 2019 at 12:23:46AM +0100, Ben Hutchings wrote:
> > Debian LTS is a team within Debian. It's separate from the main
> > security team and the stable release managers, but it is no less
> > part
> > of Debian.
>
>
Hey Andy,
Andy Smith:
> Clearly the LTS team cannot provide the same level of support, so
> wouldn't you agree that it is important that users realise when they
> go from one state to another?
I don't think I follow here. In my eyes, it's perfectly fine if Debian
users who don't follow any
On 2019-04-03 02:02, Andy Smith wrote:
c) if getting warnings from "apt update" does seem to be an
effective final way to reach such users, would it be a good idea
to find a way to have apt tell them about their transition into
LTS?
On 03.04.19 09:54, Jan Ingvoldstad wrote:
So, sort
On 2019-04-03 02:02, Andy Smith wrote:
c) if getting warnings from "apt update" does seem to be an
effective final way to reach such users, would it be a good idea
to find a way to have apt tell them about their transition into
LTS?
So, sort of a variant on Pierre Fourès's
Hi Ben,
On Wed, Apr 03, 2019 at 12:23:46AM +0100, Ben Hutchings wrote:
> Debian LTS is a team within Debian. It's separate from the main
> security team and the stable release managers, but it is no less part
> of Debian.
Sure, I do understand that. My employer is one of the LTS sponsors.
On Tue, 2019-04-02 at 19:30 +, Andy Smith wrote:
> Hi Matus,
>
> On Tue, Apr 02, 2019 at 08:17:54PM +0200, Matus UHLAR - fantomas wrote:
> > > On Tue, Apr 02, 2019 at 03:09:03PM +0200, Matus UHLAR - fantomas wrote:
> > > > On 02.04.19 10:59, Andy Smith wrote:
> > > So are you really saying
Hi Matus,
On Tue, Apr 02, 2019 at 08:17:54PM +0200, Matus UHLAR - fantomas wrote:
> >On Tue, Apr 02, 2019 at 03:09:03PM +0200, Matus UHLAR - fantomas wrote:
> >>On 02.04.19 10:59, Andy Smith wrote:
> >So are you really saying that your proposed solution is just to tell
> >people who aren't
On Tue, Apr 02, 2019 at 03:09:03PM +0200, Matus UHLAR - fantomas wrote:
On 02.04.19 10:59, Andy Smith wrote:
>The alternative is that those users continue using Debian without
>realising that their packages stopped being supported by the
>maintainers and security team and are now supported by
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 main" even if it's not
> a "security" update per se ?
Yes. tzdata and other such updates go into jessie-security
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
Hi Matus,
On Tue, Apr 02, 2019 at 03:09:03PM +0200, Matus UHLAR - fantomas wrote:
> On 02.04.19 10:59, Andy Smith wrote:
> >The alternative is that those users continue using Debian without
> >realising that their packages stopped being supported by the
> >maintainers and security team and are
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 seen in a lot of places,
>but… I can't help thinking that although it is bad that
Hi Miroslav,
On Tue, Apr 02, 2019 at 11:53:50AM +0200, Miroslav Skoric wrote:
> 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
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 seen in a lot of places,
but… I can't help thinking that although it is bad that
On 2019-04-01 20:14, Andy Smith wrote:
I don't know what the answer is other than having apt itself show a
warning about the levels of support changing, but until we work out
a better solution, isn't having the -updates suite go away at
least a final chance to get the user's attention?
I
On 4/1/19 3:50 PM, Matus UHLAR - fantomas wrote:
We have asked if it's going to be re-added, even if empty, to avoid people
using jessie from seeing errors when updateing package lists.
do I have to fill a bugreport to get it back?
Yes, do it please.
Hello,
On Mon, Apr 01, 2019 at 03:50:05PM +0200, Matus UHLAR - fantomas wrote:
> On 01.04.19 13:40, Holger Levsen wrote:
> >this is gone:
> >
> >deb http://deb.debian.org/debian/ jessie-updates main
>
> formerly volatile.
>
> We have asked if it's going to be re-added, even if empty, to avoid
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 main" even if it's not
> > a "security"
On 01/04/2019 15:50, Matus UHLAR - fantomas wrote:
>> this is gone:
>>
>> deb http://deb.debian.org/debian/ jessie-updates main
>
> formerly volatile.
>
> We have asked if it's going to be re-added, even if empty, to avoid people
> using jessie from seeing errors when updateing package lists.
>
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 main" even if it's not
> a "security" update per se ?
Yes. tzdata and other such updates go into jessie-security
Thanks Holger,
If I understood good, this mean that tzdata will get updated through
"deb http://security.debian.org/ jessie/updates main" even if it's not
a "security" update per se ?
So, to Jessie users, everything work as expected (we still get not
security updates) even if it doesn't goes
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 won't be any other updates to tzdata, clamav, or
similar (timely dependent's) packages ?
no.
good.
Or if still updated, where does we got
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 won't be any other updates to tzdata, clamav, or
> similar (timely dependent's) packages ?
no.
> Or if still updated, where does we got them
Thanks a lot Adam for the clarification.
Now that Jessie is in LTS and that jessie-updates/ is gone, does this
also mean there won't be any other updates to tzdata, clamav, or
similar (timely dependent's) packages ?
Or if still updated, where does we got them from ? I guess it's not
from
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 that all « updates » goes
> into -proposed-updates/, but the one who need to be quickly applied
> into the distribution (but aren't
On 27.03.19 11:20, Bernie Elbourn wrote:
I am very grateful for all the work done here. You are all heroes!
Can I gently ask if we can just blank the stretch-updates archive next
time
round please. Otherwise every stable machine out there now will need a
change.
Am 27.03.19 um 12:50 schrieb
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 -
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 - fantomas wrote:
I wonder if it wasn't blank already. All of its contents was
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
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
On 2019-03-27 11:50, Matus UHLAR - fantomas wrote:
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.
I wonder if it wasn't blank already. All of its contents was
On 27/03/2019 13:33, Markus Koschany wrote:
> Hi,
>
> adding Jörg to the loop who is our responsible FTP master and the only
> one who can make that happen.
Actually there are three ftp-masters, not just one :-)
> Am 27.03.19 um 12:50 schrieb Matus UHLAR - fantomas:
>> On 27.03.19 11:20, Bernie
Hi,
adding Jörg to the loop who is our responsible FTP master and the only
one who can make that happen.
Am 27.03.19 um 12:50 schrieb Matus UHLAR - fantomas:
> On 27.03.19 11:20, Bernie Elbourn wrote:
>> I am very grateful for all the work done here. You are all heroes!
>>
>> Can I gently ask if
On 27.03.19 11:20, Bernie Elbourn wrote:
I am very grateful for all the work done here. You are all heroes!
Can I gently ask if we can just blank the stretch-updates archive next time
round please. Otherwise every stable machine out there now will need a
change.
That's what I meant too. I
I am very grateful for all the work done here. You are all heroes!
Can I gently ask if we can just blank the stretch-updates archive next time
round please. Otherwise every stable machine out there now will need a change.
If it is possible to wiz up a blank jessie-updates this will save me
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
>>>
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
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
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
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
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
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
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
49 matches
Mail list logo
