On Tue, Nov 25, 2003 at 05:12:24PM -0500, Enrique Robledo Arnuncio wrote:
>...
> Meanwhile, since fftw3 seems to keep failing to build in some archs
> due to test bench errors, I should probably rebuild freqtweak using
> fftw2...
Looking at the log of the failed ftw3 builds on arm and powerpc, the
[Please CC: me, I am not subscribed to these lists.]
On Tue, Nov 25, 2003 at 11:02:17AM +0100, guenter geiger wrote:
> Do we agree on removing packages in order to get JACK into testing ?
> As we have to discuss this with the affected maintainers, I'm CC'ing
> this to Enrique, who is the maintaine
> Do we have a plan how to handle this with future JACK packages ?
>
> I think that it would be better to include the strict dependency rules
> in the packages instead of forcing them by the naming scheme of
> the JACK libraries. Several of the packages that rely on JACK only
> use a subset of i
On Fri, 21 Nov 2003, Junichi Uekawa wrote:
> Hi, fellow debian audio developers, and release managers.
>
>
> > > I think jack-audio-connection-kit and related packages should enter
> > > mini-freeze,
> > > to get something released to testing.
>
>
> This is my (3rd?) update on the freeze status.
On Fri, Nov 21, 2003 at 05:37:36AM +0900, Junichi Uekawa wrote:
> From the look of it, jack-audio-connection-kit is waiting for
>
> ecasound2.2 -- latex2html problem (uploaded at urgency=HIGH, but python
> seems to be broken)
> removing this from testing will remove ecamegaped
Hi, fellow debian audio developers, and release managers.
> > I think jack-audio-connection-kit and related packages should enter
> > mini-freeze,
> > to get something released to testing.
This is my (3rd?) update on the freeze status.
From the look of it, jack-audio-connection-kit is waiti
+++ Andreas Metzler [03-11-14 22:46 +0100]:
> On Fri, Nov 14, 2003 at 01:51:30PM -0600, Steve Langasek wrote:
> [...]
> > What criteria are you using to classify this as a grave bug, given
> > that the vast majority of sarge users will be running 2.4 kernels?
> [...]
>
> I doubt the "vast majority
On Sat, Nov 15, 2003 at 01:58:22PM +1000, Anthony Towns wrote:
>
> Blahblahblah. The bug doesn't make it unusable for everyone, therefore it's
> not grave. Stop arguing about severities and fix the bug instead. If you're
> not able to do that, do something else that's productive instead.
There ar
> > On the contrary, it would help everyone interested in having an
> > up-to-date jack-audio-connection-kit in sarge. If it becomes clear
> > later that full 2.6 support should be considered RC, the severity can
> > be raised again, assuming the bug still hasn't been fixed; but at this
> > point,
On Fri, Nov 14, 2003 at 09:04:10PM +0100, Adrian Bunk wrote:
> On Fri, Nov 14, 2003 at 01:51:30PM -0600, Steve Langasek wrote:
> >...
> > What criteria are you using to classify this as a grave bug, given that
> > the vast majority of sarge users will be running 2.4 kernels? I don't
> > recall see
On Fri, Nov 14, 2003 at 03:09:30PM -0600, Steve Langasek wrote:
> On Fri, Nov 14, 2003 at 08:57:28PM +0100, Adrian Bunk wrote:
[...]
> > I consider it ridiculous to say a bug isn't RC if it will for sure still
> > hit people using 2.6.0 - you could decrease the severity today and
> > increase the
On Fri, Nov 14, 2003 at 01:51:30PM -0600, Steve Langasek wrote:
[...]
> What criteria are you using to classify this as a grave bug, given
> that the vast majority of sarge users will be running 2.4 kernels?
[...]
I doubt the "vast majority". Who is running woody with 2.2? Lots of
people were runn
On Fri, Nov 14, 2003 at 08:57:28PM +0100, Adrian Bunk wrote:
> > > > > * wine -- which has a grave bug that it doesn't work on 2.6.0, I
> > > > > posted a workaround patch
> > > > Why would this be considered grave? 2.6.0 hasn't even been officially
> > > > released, has it?
> > > Don't be ri
On Fri, Nov 14, 2003 at 08:32:37PM +0100, Adrian Bunk wrote:
> On Fri, Nov 14, 2003 at 11:42:31AM -0600, Steve Langasek wrote:
> > On Fri, Nov 14, 2003 at 07:11:14AM +0900, Junichi Uekawa wrote:
> > > Update:
> > > From the look of it, jack-audio-connection-kit is waiting only for
> > > * wine
On Fri, Nov 14, 2003 at 01:51:30PM -0600, Steve Langasek wrote:
>...
> What criteria are you using to classify this as a grave bug, given that
> the vast majority of sarge users will be running 2.4 kernels? I don't
> recall seeing anything that made 2.6 support a "must" for sarge, so I
> don't see
On Fri, 14 Nov 2003, Steve Langasek wrote:
> On Fri, Nov 14, 2003 at 10:02:15AM +0100, guenter geiger wrote:
> > > > From the look of it, jack-audio-connection-kit is waiting only for
>
> > > > * gem -- which seems to have experienced build failure for powerpc and
> > > > hppa
>
> > For my part,
On Fri, Nov 14, 2003 at 07:47:08PM +, Colin Watson wrote:
> On Fri, Nov 14, 2003 at 08:32:37PM +0100, Adrian Bunk wrote:
> > On Fri, Nov 14, 2003 at 11:42:31AM -0600, Steve Langasek wrote:
> > > On Fri, Nov 14, 2003 at 07:11:14AM +0900, Junichi Uekawa wrote:
> > > > * wine -- which has a grave
On Fri, Nov 14, 2003 at 08:32:37PM +0100, Adrian Bunk wrote:
> On Fri, Nov 14, 2003 at 11:42:31AM -0600, Steve Langasek wrote:
> > On Fri, Nov 14, 2003 at 07:11:14AM +0900, Junichi Uekawa wrote:
> > > * wine -- which has a grave bug that it doesn't work on 2.6.0, I
> > > posted a workaround patch
On Fri, Nov 14, 2003 at 11:42:31AM -0600, Steve Langasek wrote:
> On Fri, Nov 14, 2003 at 07:11:14AM +0900, Junichi Uekawa wrote:
> > Update:
>
> > From the look of it, jack-audio-connection-kit is waiting only for
>
> > * wine -- which has a grave bug that it doesn't work on 2.6.0, I
> > post
On Fri, Nov 14, 2003 at 10:02:15AM +0100, guenter geiger wrote:
> > > From the look of it, jack-audio-connection-kit is waiting only for
> > > * gem -- which seems to have experienced build failure for powerpc and
> > > hppa
> For my part, I would prefer that jack gets pushed in and gem stays
>
On Fri, Nov 14, 2003 at 07:11:14AM +0900, Junichi Uekawa wrote:
> Update:
> From the look of it, jack-audio-connection-kit is waiting only for
> * wine -- which has a grave bug that it doesn't work on 2.6.0, I
> posted a workaround patch
Why would this be considered grave? 2.6.0 hasn't even
On Fri, Nov 14, 2003 at 04:14:34PM +0100, guenter geiger wrote:
> pthread.h includes time.h
> linux/videodev2.h includes linux/time.h
Do not use anything in /usr/include/linux from userspace directly;
they're for internal use by glibc. You should make your own copy of the
relevant headers instead
On Fri, 14 Nov 2003, Matt Kraai wrote:
> > For my part, I would prefer that jack gets pushed in and gem stays
> > uninstallable for some days, than having jack to wait another 10
> > days. ... So feel free to remove gem from testing, I will try to
> > figure out whats happening on ppc and hppa and
On Fri, Nov 14, 2003 at 10:02:15AM +0100, guenter geiger wrote:
>
> On Fri, 14 Nov 2003, Adrian Bunk wrote:
> > On Fri, Nov 14, 2003 at 07:11:14AM +0900, Junichi Uekawa wrote:
> > > Update:
> > >
> > >
> > > From the look of it, jack-audio-connection-kit is waiting only for
> > >
> > > * gem -- w
On Fri, 14 Nov 2003, Adrian Bunk wrote:
> On Fri, Nov 14, 2003 at 07:11:14AM +0900, Junichi Uekawa wrote:
> > Update:
> >
> >
> > From the look of it, jack-audio-connection-kit is waiting only for
> >
> > * gem -- which seems to have experienced build failure for powerpc and hppa
For my part, I
On Fri, Nov 14, 2003 at 07:11:14AM +0900, Junichi Uekawa wrote:
> Update:
>
>
> From the look of it, jack-audio-connection-kit is waiting only for
>
> * gem -- which seems to have experienced build failure for powerpc and hppa
> * wine -- which has a grave bug that it doesn't work on 2.6.0, I
Update:
From the look of it, jack-audio-connection-kit is waiting only for
* gem -- which seems to have experienced build failure for powerpc and hppa
* wine -- which has a grave bug that it doesn't work on 2.6.0, I posted a
workaround patch
and it will be ready for install.
regards,
On Sun, Nov 09, 2003 at 07:29:43AM +0900, Junichi Uekawa wrote:
> > > From the look of it, jack-audio-connection-kit is waiting only for
> > >
> > > puredata: Too young, only 7 of 10 days old
> > >
> > >
> > > and it will be ready for install.
> >
> >
> > You missed at least Wine and #21847
> > From the look of it, jack-audio-connection-kit is waiting only for
> >
> > puredata: Too young, only 7 of 10 days old
> >
> >
> > and it will be ready for install.
>
>
> You missed at least Wine and #218476.
Yes, indeed.
Interesting that the tools failed to show this as a problem.
On Sun, Nov 09, 2003 at 06:44:11AM +0900, Junichi Uekawa wrote:
> Hi, fellow debian audio developers, and release managers.
>
>
> > I think jack-audio-connection-kit and related packages should enter
> > mini-freeze,
> > to get something released to testing.
>
>
>
> From the look of it, jack-
Hi, fellow debian audio developers, and release managers.
> I think jack-audio-connection-kit and related packages should enter
> mini-freeze,
> to get something released to testing.
From the look of it, jack-audio-connection-kit is waiting only for
puredata: Too young, only 7 of 10 days
On Mon, Oct 20, 2003 at 06:25:23PM +0200, guenter geiger wrote:
> On Sat, 18 Oct 2003, Junichi Uekawa wrote:
> > Hi, fellow debian audio developers, and release managers.
> > I think jack-audio-connection-kit and related packages should enter
> > mini-freeze, to get something released to testing.
On Sat, 18 Oct 2003, Junichi Uekawa wrote:
> Hi, fellow debian audio developers, and release managers.
>
>
> I think jack-audio-connection-kit and related packages should enter
> mini-freeze, to get something released to testing.
>
> python2.3, which was one of the largest stumbling blocks has now
Hi, fellow debian audio developers, and release managers.
I think jack-audio-connection-kit and related packages should enter mini-freeze,
to get something released to testing.
python2.3, which was one of the largest stumbling blocks has now
entered testing.
regards,
junichi
34 matches
Mail list logo
