On Sun, Jul 01, 2012 at 10:01:28PM +0200, Sven Joachim wrote:
> > currently my source package v4l-utils builds lib32v4l-0 and
> > lib32v4l-dev packages on amd64. I'd like to get rid of them sooner
> > than later and provide a proper upgrade path to multiarch
> > packages. What's the best way to ach
On Sun, Jul 01, 2012 at 10:27:34PM +0200, Gregor Jasny wrote:
> Hello,
>
> On 7/1/12 10:01 PM, Sven Joachim wrote:
> > [ CC'ing ia32-libs maintainers for their opinion. ]
>
> Is the 20120616 or 20120701 version of ia32-libs supposed to go into Wheezy?
Yes, 20120616 is already unblocked and 20120
On Sun, Jul 01, 2012 at 10:01:28PM +0200, Sven Joachim wrote:
> [ CC'ing ia32-libs maintainers for their opinion. ]
>
> On 2012-07-01 16:04 +0200, Gregor Jasny wrote:
>
> > Hello,
> >
> > currently my source package v4l-utils builds lib32v4l-0 and
> > lib32v4l-dev packages on amd64. I'd like to g
Hello,
On 7/1/12 10:01 PM, Sven Joachim wrote:
> [ CC'ing ia32-libs maintainers for their opinion. ]
Is the 20120616 or 20120701 version of ia32-libs supposed to go into Wheezy?
On 2012-07-01 16:04 +0200, Gregor Jasny wrote:
currently my source package v4l-utils builds lib32v4l-0 and
lib32v4l
[ CC'ing ia32-libs maintainers for their opinion. ]
On 2012-07-01 16:04 +0200, Gregor Jasny wrote:
> Hello,
>
> currently my source package v4l-utils builds lib32v4l-0 and
> lib32v4l-dev packages on amd64. I'd like to get rid of them sooner
> than later and provide a proper upgrade path to multia
Hello,
currently my source package v4l-utils builds lib32v4l-0 and lib32v4l-dev
packages on amd64. I'd like to get rid of them sooner than later and
provide a proper upgrade path to multiarch packages. What's the best way
to achieve this?
As far as I can see this always involves manual actio
6 matches
Mail list logo
