Upgrade deb "stable" repository packages to foreman 1.8?

Support
#1

I have on my servers the following configuration:

root@foreman:~# cat /etc/apt/sources.list.d/foreman.list

Foreman

deb http://localmirror/foreman trusty stable
deb http://localmirror/foreman plugins stable
root@foreman:~#

After more or less a week after foreman 1.8 release, the "stable" flavour
still has not the 1.8 version, is this normal or should I change to "1.8"?

$ curl -s http://deb.theforeman.org/dists/trusty/stable/binary-amd64/Packages
> egrep -A1 "Package: foreman$"
Package: foreman
Version: 1.7.0~rc1-1

··· -- Package: foreman Version: 1.7.0~rc2-1 -- Package: foreman Version: 1.7.0-1 -- Package: foreman Version: 1.7.1-1 -- Package: foreman Version: 1.7.2-1 -- Package: foreman Version: 1.7.3-1 -- Package: foreman Version: 1.7.4-1 -- Package: foreman Version: 1.7.5-1 $
#2

It's normal that we forget! I'll add it to our release process for next
time. I've repointed the symlinks and the freight archives are just
regenerating, should be done in a few minutes.

I would generally recommend using the versioned archives unless you know
what you're doing. We started moving this way by default because people
were upgrading without checking or reading release announcements/notes.

Cheers,

··· On 06/05/15 11:19, Félix Barbeira wrote: > I have on my servers the following configuration: > > > > root@foreman:~# cat /etc/apt/sources.list.d/foreman.list > # Foreman > deb http://localmirror/foreman trusty stable > deb http://localmirror/foreman plugins stable > root@foreman:~# > > > > After more or less a week after foreman 1.8 release, the "stable" > flavour still has not the 1.8 version, is this normal or should I change > to "1.8"?

–
Dominic Cleal
Red Hat Engineering