Re: Packages security updates in -stable

On 2017-09-09, Lukasz Jendrysik wrote: > Hello, > > Since the main goal of OpenBSD is security, I keep wondering about one > thing. > There are packages like irssi or Thunderbird that should be updated to > the newest upstream version. > For example irssi's upstream encourages

Re: Packages security updates in -stable

On Sat, 9 Sep 2017 21:16:36 +0200, Lukasz Jendrysik wrote: > Similar situation with Chromium etc. All of those packages exists in > newer versions in -current, but it's not an option in my case. > > I understand that -stable is not place for the latest packages > available

Re: Packages security updates in -stable

On 09/09/2017 22:23, Theo de Raadt wrote: For example irssi's upstream encourages all users to upgrade to the newest one, see: https://irssi.org/2017/07/07/irssi-1.0.4-released/ Similar situation with Chromium etc. All of those packages exists in newer versions in -current, but it's not an

Packages security updates in -stable

Hello, Since the main goal of OpenBSD is security, I keep wondering about one thing. There are packages like irssi or Thunderbird that should be updated to the newest upstream version. For example irssi's upstream encourages all users to upgrade to the newest one, see:

Re: Packages security updates in -stable

> >> I understand that -stable is not place for the latest packages available > >> and it's expected to be rock solid, but also secure. > The thing is that mentioned packages are already updated in MAIN. Twice the work == twice the work. > I'm curious how looks the process of merging package

Re: Packages security updates in -stable

> Since the main goal of OpenBSD is security, I keep wondering about one > thing. > There are packages like irssi or Thunderbird that should be updated to > the newest upstream version. These two sentences don't make sense together. You equate "update update" with security. That doesn't make