[Pkg-ia32-libs-maintainers] Helping with security support for ia32-libs

[Goswin von Brederlow]

"Thijs Kinkhorst" <thijs at debian.org> writes:

> Hi all,
>
> At the Debian Security Team meeting in Essen we discussed the situation of
> ia32-libs* and the way to best security support it for squeeze. (It's
> still expected that the packages become obsolete for wheezy as I
> understand.)
>
> The conclusion is that (a) the packages need to be as up to date as
> possible at time of release, and (b) we will release updates for
> ia32-libs* in any point release if there are changed packages. In
> emergencies we will release it in a security advisory.
>
> To ensure we keep up with this I've volunteered to do the work for this.
> This means I'll be uploading new releases of ia32-libs* on behalf of the
> security team. I will usually not change anything but refresh the included
> packages of course. Perhaps it makes sense for this if I'm officially
> added to the maintenance team. What do you think?
>
>
> Cheers,
> Thijs

I think that is a good idea. Request being added to the team on alioth
and (unless somone else objects) I will add you then.


As for building new versions I think it would be good to practice that.

Try checking out the git repository and prepare an upload now. The
procedure should be (from memory):

./fetch-and-build
git add versions/<the new version>
git rm versions/<old version>
git commit -a
edit <files that need bug fixing> [should not be needed]
git commit ...
debuild + test
git tag ia32-libs-<the new version>
git push --all
git push --tags
upload

There is also a debian/README.source you should read and suggest changes
to make it better.

Thanks for your interest.
       Goswin