Bug#430961: libjack sets rpath for amd64

Hi, > > Package: libjack-dev > > Version: 0.103.0-6 > > Severity: serious > > > > /usr/lib64 is not used in Debian, and this enters each .la file, which > > in turn results in rpath being set in resulting binaries, please fix > > it, rather than using chrpath to work around it. > > Hi, > > Do y

RFP: MuseScore ?

Hi, Is anybody working on muse score package for Debian ? I've done some preliminary work (wrote a manpage and made debian/rules that builds and installs) on this so that I can get minimal package working, and it looks quite pretty. http://mscore.sf.net/ attached is a diff.gz. regards,

Bug#430961: libjack sets rpath for amd64

Package: libjack-dev Version: 0.103.0-6 Severity: serious /usr/lib64 is not used in Debian, and this enters each .la file, which in turn results in rpath being set in resulting binaries, please fix it, rather than using chrpath to work around it. diff -Nur jack-audio-connection-kit-0.103.0-or

Re: [FWD] Re: [Jackit-devel] parallel installs to die

> JU> Can you wait until etch release please ? This will mean binaries > JU> compiled on sid will have a different SONAME requirements, so will no > JU> longer work on etch. Right ? > > No they will still work, as the SONAME is unchanged with respect to > the jack version in etch, it's st

Re: [FWD] Re: [Jackit-devel] parallel installs to die

Hi, > I've doubled checked the new packages, both on amd64 and i386, and I > confirm that the work fine, without breaking other packages (this > 0.102.20 upstream release was also includedin the recent 1.0 64 > Studio release, and no bug reports have come so far). > > So if everybo

Re: [FWD] Re: [Jackit-devel] parallel installs to die

Hi, > http://svn.debian.org/wsvn/demudi/jack-audio-connection-kit/trunk/debian/?rev=0&sc=0 > > and tested the new packages on amd64. Everything seems to work fine, > and upgrades from the previous packages are possible through the dummy > packages I've added in debian/control. > > If everythin

Re: Do we really need the laspa- prefix?

Hi, > I'd like to sponsor the upload this package, but before I need to > clear the naming convention of ladspa related packages. > > Generally speaking I think that Debian packages names should try to > match exactly the upstream project name. In this case the upstream > name is "vcf

Bug#375585: rosegarden-data: missing replaces on rosegarden4

Package: rosegarden-data Version: 1:1.2.3-1 Severity: grave Some files overlap, but it's not declaring replaces on rosegarden4. regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Troubl

Re: we got our first bugs filed against rosegarden

Hi, > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=373885 Congratulations, and welcome to the club :) Good luck in fixing all the older bugs also. regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subjec

Re: rosegarden_1.2.3-1_amd64.changes is NEW

> th> That answers my previous question. > > All right. The decision of replacing the old rosegarden and > rosegarden2 packages have been taken because the upstream of these is > now completely discontinued. Anyway, kudos for getting the ball rolling for rosegarden. regards,

Bug#370080: O: gamix -- Graphical sound mixer for ALSA

Package: wnpp It doesn't work well and it's not maintained well in upstream. Recently, it was just fighting against bit-rotting. gnome-alsamixer etc. will work better. Package: gamix Priority: extra Section: sound Installed-Size: 196 Maintainer: Junichi Uekawa <[EMAIL PROTECTED]&

Re: annoyances with sound/video in Debian.

Hi, > > I've discussed this with Herman Robak in Hacklab2 today: > > 1. What is expected from group audio ? > > 2. /dev/raw1394 is owned by disks group. > > 3. artsd / esd grabbing /dev/dsp is annoying ! > > 4. 1394 / DV / v4l / v4l2 needs consolidation! > > did you file bugs for these issues (or

annoyances with sound/video in Debian.

I've discussed this with Herman Robak in Hacklab2 today: 1. What is expected from group audio ? local users would always want audio access from /dev/dsp. However, you don't want to give realtime scheduling by default. 2. /dev/raw1394 is owned by disks group. Can be disk or video. Can ude

Re: group maintenance (was Re: RFS: ladspa-omins / ladspa-vcf)

Hi, > > http://qa.debian.org/[EMAIL PROTECTED] > > > > We have a SVN repository here: > > > > http://svn.debian.org/wsvn/demudi/ > > > > I'd like to include ther source packagein this repo, are you > > subscribed to Alioth? Just let me know your user name and I'll include > > you in t

Re: Bug#363108: ITP: ladspa-vcf -- audio EQ biquad filters for LADSPA

Hi, > > ladspa could do the same with > > > > ladspa- > > > > i.e. your initial choice sounds like the most logical solution. > > okay, I'll go with this. > Maybe on the long term other ladspa packages should also switch name. The more important part is 'Provides: ladspa-plugin', and the na

Re: Bug#363108: ITP: ladspa-vcf -- audio EQ biquad filters for LADSPA

Hi, > > What would be the binary package name? > > > > Currently, the practice seems like: > > *-plugins > > (which might be a bit too generic, looking at it now). > > My current package uses ladspa-vcf. > Indeed the -plugins seems not very good to me. > > I'd prefer ladspa-vcf or perhaps ladspa

Re: Bug#363108: ITP: ladspa-vcf -- audio EQ biquad filters for LADSPA

Hi, > Package: wnpp > Owner: Joost Yervante Damad <[EMAIL PROTECTED]> > Severity: wishlist > X-Debbugs-CC: debian-multimedia@lists.debian.org > > *** Please type your report below this line *** > > * Package name: ladspa-vcf > Version : 0.0.5 > Upstream Author : Matthias Nagorni

Debian FreeBoB Package introduction.

Hi, > Sorry for big latency :). Packages are prepared. And are working. > > deb http://pkg-freebob.alioth.debian.org/debian unstable/ > deb-src http://pkg-freebob.alioth.debian.org/debian unstable/ http://pkg-freebob.alioth.debian.org/debian/unstable/ 1. your changes file gives me 'Forbidden' h

Re: debian-multimedia-BOF at debconf6/MX?

Hi, > > https://debconf6.debconf.org/comas/general/proposals/6 > > > > Paul Brossier is apparently planning to present a BOF on DeMuDi at > > Debconf. Is this confirmed? If this is going to be held, we can just > > turn up there, which simplifies the logistics a lot, and gives much > > fuzzy fee

Re: [Fwd: RFC/RFS: rosegarden4: music editor and MIDI/audio sequencer]

Hi, > > You're added, could you do svn-inject ? > > OK, I ran svn-inject. its in: > > svn://svn.debian.org/svn/demudi/rosegarden Okay, checked out. > Here are the things people should be aware of: > > The previous build of rosegarden4 build-deps on gcc3.4 for 3 arches that > were previously

Re: debian-multimedia-BOF at debconf6/MX?

Hi, > > How many people will be attending debconf in Mexico in May 2006 ? I'd > > like to have maybe a session of sitting down and talking with a few > > people. > > +1 > > I would love to exchange wishes and assumptions, and have assumptions > shot out of the water. The devil is in the corner

debian-multimedia-BOF at debconf6/MX?

Hi, How many people will be attending debconf in Mexico in May 2006 ? I'd like to have maybe a session of sitting down and talking with a few people. (of course, I'd be sitting down and coding also, which hopefully will advance some parts of debian-multimedia) regards, junichi -- [EMAI

Re: [Fwd: RFC/RFS: rosegarden4: music editor and MIDI/audio sequencer]

Hi, > > > > Cool. I didn't realize that rosegarden4 was orphaned at all. > > > > I am interested in getting this thing updated in Debian. > > > > > > > > I prefer working out of a svn/cvs repos rather than shifting around > > > > whole packages. > > > > > > I ran svn-inject, and my package is

Re: [Jackit-devel] [CVS COMMIT] 0.101.0 FreeBob backend inclusion

Hi, > Not yet AFAIK, but: > > http://demudi.agnula.org/wiki/DocumentsTipsFreebob > http://pkg-freebob.alioth.debian.org/ It's not clear if the maintainer is still around. The package may enter Debian iff 1. package complies policy. 2. has an active maintainer with firewire hardware. I'm cc

Re: [Jackit-devel] [CVS COMMIT] 0.101.0 FreeBob backend inclusion

From jackit-devel: > I committed the freebob backend code to jackd CVS. Tested both with and > without freebob libraries. > > CVS log: > > - Added FreeBob backend code > - Modified autoconf/automake files to include FreeBob backend > - Bumped version to 0.101.0 > > Modified: > configure.ac > d

Re: [Fwd: RFC/RFS: rosegarden4: music editor and MIDI/audio sequencer]

Hi, > > Cool. I didn't realize that rosegarden4 was orphaned at all. > > I am interested in getting this thing updated in Debian. > > > > I prefer working out of a svn/cvs repos rather than shifting around > > whole packages. > > I ran svn-inject, and my package is here: > > svn://svn.vireo.o

Re: [Fwd: RFC/RFS: rosegarden4: music editor and MIDI/audio sequencer]

Hi, > > This package strikes me as an ideal candidate for Debian-multimedia to > > sponsor / co-maintain, this requires at least one DD on this list to be > > enthusiastic about the idea. Rosegarden4 is one of Linux Audio's > > flagship apps IMO and it has always looked bad that Debian constant

Re: multimedia-policy: DSSI and related packages?

Hi, > > I've been casually glancing over linux-audio-user mailing list and > > noticed that there's something called DSSI. It's even packaged in > > Debian, although I don't know if any apps actually use it. > > > > Things I'd like to see: > > > > 1. package dependency information to signify who

Re: [a-users] Re: QA - multimedia orphanage

Hi > > I've noticed that agnula pages require logging in before editing, > > maybe wiki.debian.org also does. I've added a link to that page from > > http://wiki.debian.org/DebianMultimedia, but I think the wiki is > > better located into somewhere like > > http://wiki.debian.org/DebianMultimedia

Re: Bug#356472: ITP: netjack -- realtime audio transport over IP networks with JACK

Hi, > * Package name: netjack > Version : 0.8 > Upstream Author : Torben Hohn <[EMAIL PROTECTED]> > * URL : http://netjack.sourceforge.net/ > * License : GPL > Description : realtime audio transport over IP networks with JACK > > Netjack is a Realtime A

Re: problem with ISA SB16 sound card

Hi, > sarge's default kernel can't use my SB16! > > I have used my SB16 ever since kernel 2.0, 2.2, and > 2.4 in woody. They all work. But with sarge's kernel > 2.4, it can't work. When I modprobe sb, it complains > no such device. > > Does sarge's kernel 2.4 support non-PNP ISA card? > > Why d

Re: Questions on video related multimedia standards

Hi, Thanks for the response and updates on the wiki :) > > 2. Do we have any video codec standards ? Where they are put, what > >kind of interfaces they provide. Or are they independent of the > >encoder/decoder? (ffmpeg?) > > Each framework (mplayer, xine, vlc, gstreamer) has its own c

Re: multimedia-policy: DSSI and related packages?

Hi, > > I've packaed dssi-vst, see: > > > > http://svn.debian.org/wsvn/demudi/dssi-vst/?rev=0&sc=0 > > > > but couldn't make it buil with wine 0.9.7 from Debian/testing, it's > > working only with wine from stable. > > From memory, VST was non-free, it disallowed modification (like most > other

Questions on video related multimedia standards

Hi, I have a few questions on video standards. 1. We do have some kind of standard for video, called video4linux2, is that correct ? I gathered that it has some interface for configuring TV input and tuner I/O, and some standard on /dev/video devices. 2. Do we have any video codec standa

Re: QA - multimedia orphanage

Hi, > I have now uploaded an updated list of multimedia WNPPs - packages that > need help getting into or staying in Debian/DeMuDi please check it out: > > http://demudi.agnula.org/wiki/DevelopPackaging > > Let me know about errors or omissions etc. > Hope it's useful. Having a RFP, or ITP bug

Re: New packages I'm planning to work on

Hi, > But I do agree, and I am here now, and any efforts I make will go into > Debian first, I hope. I have to learn on what the processes are, as I > understand that Debian has no such thing as REVU, but rather use email > for communication, and various methods for package collaboration, such > a

Re: "state of multimedia" (audio)

Hi, > > This could be a starting point: > > > > http://qa.debian.org/developer.php?login=debian-multimedia%40lists.debian.org&comaint=yes > > > > at least as far as uploaded packages are concerned. > > Thanks. I'm thinking more about tracking packages before they get to > this point. I'm inter

Re: current state of MIDI in Debian

Hi, Slow reply, but I'm only slowly gaining insight into this area of Debian. > > 1. casual user playing back SMF file > > > > A web browser invoking some player. Handled via MIME. Currently it > > probably invokes timidity, since timidty+freepats is probably the only > > thing in Debian support

Re: multimedia-policy: DSSI and related packages?

Hi, > JU> Hi, > JU> I've been casually glancing over linux-audio-user mailing list and > JU> noticed that there's something called DSSI. It's even packaged in > JU> Debian, although I don't know if any apps actually use it. > > It entered Debian very recently. But AFAIK now plugins are

Re: [linux-audio-user] Re: info about demudi

Hi, I'm only reading this list very infrequently, > That is great news, for sure! > > >From the list of apps that I've collected, these don't appear to be in > debian yet: > -aeolus > -ceres > -ceres3 > -dssi-vst > -freecycle > -gmorgan > -hexter > -jdelay > -kaconnect > -linuxsampler > -mx44 >

multimedia-policy: DSSI and related packages?

Hi, I've been casually glancing over linux-audio-user mailing list and noticed that there's something called DSSI. It's even packaged in Debian, although I don't know if any apps actually use it. Things I'd like to see: 1. package dependency information to signify who supports dssi. Provides/

multimedia-policy: user/group information and PAM

Hi, I've added to the wiki page [1] a reference to 'audio' 'video' groups that seem to exist, but rarely documented. If you know where it is already documented, I'd like to add a pointer to that document, otherwise, multimedia policy will be the first document defining what it does (although it m

Re: portaudio in Debian, license updates?

Hi, > > However, portaudio looks non-free to me. > > > > http://www.portaudio.com/license.html: > > * Any person wishing to distribute modifications to the Software is > > requested to send the modifications to the original developer so that > > they can be incorporated into the canonical version

Re: "state of multimedia" (audio)

Hi, > > I've done a little presentation for Tokyo-area Debian meeting[1] last week. > > I've translated the resource into English[2]. > > > > It's a summary of what I've been doing and where I want to go from > > now, and an introduction to what the Debian scene currently looks like. > > > > I wou

"state of multimedia" (audio)

Hi, I've done a little presentation for Tokyo-area Debian meeting[1] last week. I've translated the resource into English[2]. It's a summary of what I've been doing and where I want to go from now, and an introduction to what the Debian scene currently looks like. I would be interested in what y

Re: [off-topic, kind of] How To report bugs regarding Ingo's rt patches?

Hi, > Sorry guys, does someone know how to report bugs regarding Ingo's > patches? I'm having problems since 2.6.14 on my amd64+LVM+xfs, it > panics, sends lots of debug output to the console and reboots. Unpatched > kernel works fine, It seems to do that when it's either loading device > mapper o

Re: portaudio in Debian, license updates?

Hi, > > However, portaudio looks non-free to me. > > According to my reading of the license (and according to the PortAudio > upstream authors), this clause is a non-binding request, and so it does > not make the license non-free. Please see this thread: > >http://lists.debian.org/debian-le

portaudio in Debian, license updates?

Hi, > > On Thursday 16 February 2006 22:49, Junichi Uekawa was like: > >>>>Audio on the other hand seems to have mostly settled for ALSA and jack. > >>>>(I'm not sure if portaudio is gone?) > > Things like portaudio and MIDIshare never really arrived

Re: Debian policy on multimedia ?

Hi, > > > I think if we are making policy here, then setting ALSA as the basic > > > sound system with JACK used in all cases where applications need to be > > > able to communicate about audio signals in realtime, is the only sensible > > > option. This will force everything else to be compatibl

Re: Debian policy on multimedia ?

Hi, > >> > Audio on the other hand seems to have mostly settled for ALSA and jack. > >> > (I'm not sure if portaudio is gone?) > >> > >> Yes. And I would suggest that the audio servers become deprecated. > >> They should get compability solutions, "proxies" if you like, so that > >> programs th

Re: Debian policy on multimedia ?

Hi, > I think if we are making policy here, then setting ALSA as the basic sound > system with JACK used in all cases where applications need to be able to > communicate about audio signals in realtime, is the only sensible option. > This will force everything else to be compatible, which is a

Re: starting audio applications via a common wrapper?

Hi, > EM> That is precisely the point I want to address. Using the argv[0] trick > EM> (diverting, let's say, hydrogen to hydrogen.real and > EM> symlinking /usr/bin/hydrogen to this wrapper application) we would have > EM> the advantage of being able to decide what CLI arguments to pass t

Re: Debian policy on multimedia ?

Hi, > > At least that's something worth documenting. It sounds like there is > > still a lot of upstream work to be done in video field. > > Indeed. A "video jack" architecure was proposed at Piksel5 in Bergen > last fall: http://www.piksel.no/pwiki/VideoJack > > The video scene is still f

current state of MIDI in Debian

Hi I'd like to do some research into current state of Debian MIDI support. The following is the different usage scenarios I have in mind. 1. casual user playing back SMF file A web browser invoking some player. Handled via MIME. Currently it probably invokes timidity, since timidty+freepats is

Re: starting audio applications via a common wrapper?

Hi, > What if we designed a wrapper to start audio applications accordingly? > > We have several applications that work with many sound daemons but > are unable to detect them or decide which one to use based on > priorities. hydrogen is one of them. > > This wrapper could be called instead of t

Re: Including a low-latency kernel images in Debian for use with CDD DeMuDi.

Hi, I'll cc debian-multimedia, since I didn't notice agnula lists were subscriber only. > > > Also, we don't need to rebuild all flavours, only a few ones for select > > > arches > > > and flavours. > > > > What do you mean? > > the idea is to build a few flavours with the -RT patches, not al

Re: Debian policy on multimedia ?

Hi, > > I'd expect the following kind of stuff to be documented. If it's not > > available, or it's not set in stone, that's what really needs > > documenting, and maybe further work. > > > > 1. how input info is configured. For TV info, xawtv seems like the de > >facto standard, but I'm not

Re: Debian policy on multimedia ?

Hi, > > A wiki could be useful for the more persistent kind of conversationneeded > > to pull the Debian Multimedia Policy together > > Yes. It is good for asynchronous work. However, there will be > need for some brainstorming sessions, lest the process become > really slow. Initial write

Re: Debian policy on multimedia ?

Hi, > What about the idea of setting up a wiki somewhere? We could write > something in advance, I've been thinking about some itens to be > suggested to the policy: I've noted down the discussion here, so that it's easier to discuss. http://wiki.debian.org/DebianMultimedia regards, ju

Re: Debian policy on multimedia ?

Hi, I'm preparing for notes on my LUG presentation, and I've been trying out most of multimedia applications in Debian which I could put my hands on. I have a clearer view of the current state now that I think I can comment much better. > What about the idea of setting up a wiki somewhere? We c

Re: Debian policy on multimedia ?

Hi, > > JU> Okay, so, time for a brainstorming session on IRC? > > JU> I think having a set time to brainstorm, and assemble the results > > would be interesting. > > JU> We could try discussing on mailing list, but let's see how it goes. > > > > I'm available for the IRC session, if decid

Re: collaborative maintenance with Maintainer: set to debian-multimedia?

Hi, > > I'm planning on doing some collaborative maintenance of some packages, > > I'd like to set Maintainer: field set to [EMAIL PROTECTED], and > > maybe set Uploaders: field set to individual maintainers. I have in > > mind Agnula developers (who are non-maintainers) here. > > > > The obvious

Re: Debian policy on multimedia ?

Hi, > > A wiki could be useful for the more persistent kind of conversationneeded > > to pull the Debian Multimedia Policy together > > Yes. It is good for asynchronous work. However, there will be > need for some brainstorming sessions, lest the process become > really slow. Okay, so, tim

Re: IRC presence?

Hi, > >> Is there an IRC channel that would be relevant for us > >> to join on a regular basis, or should we create one? > >> For example #debian-multimedia at Freenode? > > > > I'd prefer #debian-multimedia at OPN, but having a channel in both > > would be fine, even better would be a channel tha

Re: IRC presence?

Hi, > Is there an IRC channel that would be relevant for us > to join on a regular basis, or should we create one? > For example #debian-multimedia at Freenode? I'd prefer #debian-multimedia at OPN, but having a channel in both would be fine, even better would be a channel that is gated. I have p

collaborative maintenance with Maintainer: set to debian-multimedia?

Hi, I'm planning on doing some collaborative maintenance of some packages, I'd like to set Maintainer: field set to [EMAIL PROTECTED], and maybe set Uploaders: field set to individual maintainers. I have in mind Agnula developers (who are non-maintainers) here. The obvious problem I would see is

Re: Debian policy on multimedia ?

Hi, > In terms of classical Debian terms, we will probably require a policy > documenting the following. I'm a bit further away than I like from a > policy documentation at the moment, because not every piece is > available yet. After having posted this; I noticed that there isn't really a conv

Re: [a-users] But.. AGNULA is not dead!

Hi, > I think you all read the annoucement, if not have a look here: > > http://lists.agnula.org/pipermail/announce/2006-January/000102.html > > that's bad I know.. Condolences. I've just subscribed to the mailing list and the first major thread is this, a coincidence. Anyway, I'm interested

Re: Debian policy on multimedia ?

Hi, > > I usually don't have a MIDI keyboard around me, and I'm using software > > synthesizers. I have an impression that the software synthesizing defaults > > are: > > > > most applications -- timidity > > > > KDE applications (noteedit/kguitar) -- tse > > > > My thinking in the MIDI area was t

Re: Debian policy on multimedia ?

Hi, > > Considering MIDI, a pre-requirement of MIDI keyboard with ALSA > > configured is more than what most casual users would want. Most people > > would probably have a requirement of a playback of MIDI instrument, > > and probably a leap to a virtual MIDI keyboard before jumping into > > buyin

Re: Debian policy on multimedia ?

Hi, > > > This kind of thing will surely need some kind of policy document > > > specific to multimedia stuff, at least. > > > > > > I'm not sure if MIDI related stuff are mature enough for this, but I > > > think there needs to be some kind of usable sane default for > > > MIDI/virtual keyboards

Re: Debian policy on multimedia ?

Hi, > > I'm currently trying to do a write up for my local LUG on > > multimedia application in Debian, and stumbled upon this question: > > Is there currently a document that describes what should happen with > > debian multimedia packages? > > > > There are quite a few things that have inter-wor

Re: Debian policy on multimedia ?

Hi, > > I'm currently trying to do a write up for my local LUG on > > multimedia application in Debian, and stumbled upon this question: > > Is there currently a document that describes what should happen with > > debian multimedia packages? > > > > There are quite a few things that have inter-wor

Debian policy on multimedia ?

Hi, I'm currently trying to do a write up for my local LUG on multimedia application in Debian, and stumbled upon this question: Is there currently a document that describes what should happen with debian multimedia packages? There are quite a few things that have inter-working functionalities.

Re: building jack packages for sarge

Hi, > > > Is it possible to build a package of jack 0.100.0 that would satisfy > > > dependancies of other pacakges in sarge that depend on jack 0.99.0 / > > > libjack0.80.0? > > Hi, > > Seems that I am the last one on this list :) > > The short answer: No > > Longer explication: The change of th

Re: [a-devel] AGNULA/DeMuDi 1.1.1 and 2.6.x kernel

Hi, > Hmm. Looks like the Debian binaries are stripped. Drat! It should be possible to obtain a non-stripped library package with Download the source: apt-get source jack-audio-connection-kit Satisfy the build-dependency: apt-get build-dep jack-audio-connection-kit enter the directory and

Re: jack-audio-connection-kit 0.98.1

> I think it would be nice to have JACK 0.98 in sarge. Compatibility seems > to be really good. What is the general opinion about uploading JACK to > unstable now? IMO, go ahead if it's not going to be an ABI event (i.e. no package change). regards, junichi

Re: Update: Scheduling another freeze of Jack-related packages

Post-mortem reports on this, and slight updates. > > 11 Feb 2004 : All jack-related packages enter testing, or gets removed > > from testing. > > This is rather optimistic at this rate. We may delay by a few weeks. This wasn't delayed by too many weeks, and we have jack in testing. Congratu

Re: jack 0.94.0-2

> > I'd like the conflicts added so that only one version of libjack > > can be installed at the same time. > > > And a provides: line so that future version of libjack can > > provides: and conflicts: that virtual package to ensure > > incompatible libjack/jackd combinations aren't installed > >

Re: jack 0.94.0-2

Hi, > Opinions? I'd like the conflicts added so that only one version of libjack can be installed at the same time. And a provides: line so that future version of libjack can provides: and conflicts: that virtual package to ensure incompatible libjack/jackd combinations aren't installed at the

Re: Update: Scheduling another freeze of Jack-related packages

Updates; Timeline > 1 Feb 2004 : Final upload, or hinted 'remove' from testing We have already entered this point; and all uploads are done. The problem we currently have is that the buildd infrastructure has not been in a very good shape, and thus we have a lot of packages that are n

Re: Update: Scheduling another freeze of Jack-related packages

Updates; Timeline > 16 Jan 2004 : jack hits unstable Done Jack is now built on all architectures. > 18 Jan 2004 : Maintainer uploads are done by this date. The remaining packages are: libhydrogen0,libjack0.71.2-0 0.75.0 -- this package is going to be removed muse,libjack0.71.2-0 0.

Update: Scheduling another freeze of Jack-related packages

Updates; Timeline > 16 Jan 2004 : jack hits unstable Done Jack is now built on all architectures. > 18 Jan 2004 : Maintainer uploads are done by this date. The remaining packages are: gstreamer-jack,libjack0.71.2-0 0.75.0 -- 228784 libasound2-plugins,libjack0.71.2-0 0.75.0 -- 228785

Re: Bug#229318: Future FTBFS - libasound2-dev source incompatiblity

> Hello :) The Debian ALSA packaging team will shortly be uploading a new > version of libasound, which unfortunately includes a source-level > incompatibility introduced by upstream. We don't feel it's appropriate > to differ from other distributions in this respect, and the number of > affected p

To remove sted2 ? (Re: sted2 is adopted)

> * Junichi Uekawa <[EMAIL PROTECTED]> [2003-01-24 23:15]: > > I think this package has been adopted by mlang. > > This is the bug report marking the package as orphaned. > > * Mario Lang <[EMAIL PROTECTED]> [2003-01-27 15:24]: > > > I think this packag

Re: Scheduling another freeze of Jack-related packages

Hi, Okay, time to update what's been done with Jack. Timeline > 16 Jan 2004 : jack hits unstable Done All arches built except for m68k; this needs to be looked into, since we want to know if it's failing to build or not. Cc'ed to debian-m68k for this: could folks try building this packag

Re: Scheduling another freeze of Jack-related packages

> > It seems to be another round of large-scale dependency chain, > > close to release, thus we probably need a scheduled freezing > > to get this thing to be released in sarge at all. > > > > Here's a rough timeline that I came up with: > > > > > > 16 Jan 2004 : jack hits unstable > > 18 Jan 2004

Re: JACK 0.91.1-1

> > > Nice. JACK 0.94.0 is at , my > > > first tries to rebuild all the packages are at > > > . > > > > Yikes, I've noticed that you've actually done the upload. > > I said so in > >

Scheduling another freeze of Jack-related packages

Hi, It seems to be another round of large-scale dependency chain, close to release, thus we probably need a scheduled freezing to get this thing to be released in sarge at all. Here's a rough timeline that I came up with: 16 Jan 2004 : jack hits unstable 18 Jan 2004 : Maintainer uploads are

Re: JACK 0.91.1-1

> > > I support uploading of newer jack version. > > Nice. JACK 0.94.0 is at , my > first tries to rebuild all the packages are at > . Yikes, I've noticed that you've actually done the upload. ecasound2.2 is goi

please rebuild ecasound2.2 on s390

Hi, Please try rebuilding ecasound2.2 package on s390, it has previously failed with a strange error, failing to find aclocal on the path. Having ecasound2.2 built and released to testing is required before getting a new incompatible jack version. ecawave and ecamegapedal are in a uncomforta

Re: JACK 0.91.1-1

Hi, Nice to see jack has finally gone in to testing. I support uploading of newer jack version. However, I do doubt it's going to be the last ABI-incompatible release. regards, junichi

Re: [Agnula-Developers] Re: jack 0.75 mini-freeze

> Also notice that we are working on the following ToDo wrt to jack: > > http://devel.agnula.org/tracker/?func=detail&aid=37&group_id=8&atid=141 > > which is basically an advice from Fernando Lopez-Lezcano about > mounting a tempfs filesystem on /tmp/jack (or something like that) and >

Re: [Agnula-Developers] Re: jack 0.75 mini-freeze

> > ju> I've got an impression that by the time we actually get this > > ju> release in, we are probably going to be looking at 0.90, which > > ju> should be more stable, and then we'll probably be looking at > > ju> 1.0, which should be two more ABI changes; which isn't too > >

Re: jack 0.75 mini-freeze

> 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

Re: jack 0.75 mini-freeze

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

Re: jack 0.75 mini-freeze

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,

Re: jack 0.75 mini-freeze

> > 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.

Re: jack 0.75 mini-freeze

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

jack 0.75 mini-freeze

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

  1   2   >