current layout for stable is mostly links to 3.3 dir:
# tree
.
|-- iso -> /var/www/html/releases/3.2/iso
|-- rpm
| |-- EL -> /var/www/html/releases/3.3/rpm/EL
| `-- Fedora
| |-- 17 -> /var/www/html/releases/3.1/rpm/Fedora/17
| |-- 18 -> /var/www/html/releases/3.2/rpm/Fedora/18
| `-- 19 -> /var/www/html/releases/3.3/rpm/Fedora/19
|-- src -> /var/www/html/releases/3.3/src
`-- tools -> /var/www/html/releases/3.3/tools
so i guess the links should be updates to point to 3.3.2 dir instead of 3.3
Eyal.
----- Original Message -----
From: "Itamar Heim" <iheim(a)redhat.com>
To: "Alon Bar-Lev" <alonbl(a)redhat.com>, "infra"
<infra(a)ovirt.org>, "Kiril Nesenko" <kiril(a)redhat.com>
Cc: "Sandro Bonazzola" <sbonazzo(a)redhat.com>
Sent: Sunday, January 5, 2014 7:55:19 PM
Subject: Re: release repo structure and 3.3.2
On 01/01/2014 11:42 AM, Alon Bar-Lev wrote:
> Hi,
>
> For some reason there 3.3.2 z-stream was released in its own repository so
> people that are subscribed to stable[1] did not get it.
>
> There is no much sense in releasing fix release that people do not get in
> simple "yum update".
>
> Also the following is now broken of most packages' spec:
> Source0:
>
http://ovirt.org/releases/stable/src/@PACKAGE_NAME@-@PACKAGE_VERSION@.tar.gz
>
> For each minor we should have rolling repository, to reduce noise and
> provide service.
>
> All released tarballs (sources) should be stored at fixed location to allow
> distro specific code to fetch, the location must be synced with what we
> publish.
>
> Immediate action is to move the 3.3.2 content into the stable directory.
>
> Regards,
> Alon Bar-Lev.
>
> [1]
http://resources.ovirt.org/releases/stable/
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/infra
>
kiril - was this fixed?
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra