Romain Francoise wrote:
> Do we really want the new wmaker in sarge? It's the result of several
> months of upstream development and it's apparently a bit rough around
> the edges, and it's even unusable for me because of bug #283240. This
> is by no means a critical bug by Debian standards but
On 2004-12-04 Jeff Teunissen <[EMAIL PROTECTED]> wrote:
> Andreas Metzler wrote:
[...]
> > I do not know what the best course of action is, there are 3
> > alternatives afaict:
> > 1) tempoarily remove wsoundserver and wsoundprefs from sarge to let
> > wmaker in.
> > 2) Quickly upload a new version
Andreas Metzler wrote:
[snip]
> However wsoundprefs depends on wsoundserver (which contains
> libwsound.so.1) and the maintainer of wsoundserver chose to not only
> switch to librwaster3 in 0.4.0-18 (or -19). Instead he uploaded a new
> version of libdockapp (bumped soname libdockapp2) at the sam
Andreas Metzler <[EMAIL PROTECTED]> writes:
> I was checking up on wmaker's status re sarge migration, and while I was
> at it, chose to mail it here.
Do we really want the new wmaker in sarge? It's the result of several
months of upstream development and it's apparently a bit rough around
the e
Hello,
I was checking up on wmaker's status re sarge migration, and while I was
at it, chose to mail it here.
The new wmaker brings a new libwraster, libwraster3 instead of
libwraster2. That in itself would be easily doable in short time, as
there are only 4 other packages linking[1] against it (w
5 matches
Mail list logo
