In gmane.comp.window-managers.ion.general, you wrote:
> Since Tuomo has symbols/pc/pc, I feel he is using old xkbdata instead of
> xkeyboard-config. So first thing he should do is upgrading to some
> recent version of xkeyboard-config. Otherwise our fixes would not make
> sense.
I'm using whatever
On 2007-09-23 19:46 +0200, Mohammed Adnène Trojette wrote:
> I forwarded your bug upstream. And upstream is asking to try commenting
> the lines
>
> key {[ NoSymbol, Super_L ] };
> modifier_map Mod4 { };
>
> in symbols/pc
>
> (please see http://bugs.freedesktop.org/
(Quoting full post, because Cc:ing to the Ion list.)
On 2007-09-23 03:01 +0200, Mohammed Adnène Trojette wrote:
> tag 409612 moreinfo
> thanks
>
> On Sun, Feb 04, 2007, tuomov wrote:
> > The modifier mappings in stock keyboard layouts are broken.
> > For details, I'll just attach the Ion FAQ entr
On 2007-03-11 01:19 -0800, Frank Bauer wrote:
> I do understand that Ion3 is not finished yet and you as the author of this
> gem should know the best when the software is "stable", but as I mentioned
> earlier, some features from Ion3 are huge usability improvement over Ion2
> and current snapshot
> This is quite unfortunate for me. I, for one, am using officially packaged
> Ion3 on current stable and intended to use Ion3 also in upcomming Etch.
> I can't be bothered to install all those development packages just to
> compile the curent versions
Why do you want a random broken and unsuppo
On 2007-03-09 09:51 -0500, Jeremy Hankins wrote:
> Assuming the answer is yes (or roughly yes), there are probably solutions
> short of not permitting ion3 in stable. For example, how about a big flashy
> banner (e.g., xmessage) on startup saying that the release of ion3 running is
> old and compl
On 2007-03-09 14:14 +0100, Josselin Mouette wrote:
> Besides, you can only do that if you are the sole author of the current
> code. Otherwise, you'll need approval from all past patch contributors.
> As you probably won't get it, it would make the entire software
> impossible to distribute.
Ion i
On 2007-03-09 14:08 +0100, Norbert Tretkowski wrote:
> You can't force us to completely remove the current release from
> Debian.
But I can stop you from distributing new releases, and possibly
get a few users complaining to you too over the ancient releases
in unstable as well. And I can hope th
It is starting to seem, that it will be easier to just change the
license, than beat some sense into your heads. Obviously, since
you so desperately want to have ancient development releases in
Debian, you do not need newer releases at all.
--
Tuomo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTE
On 2007-03-07 19:54 -0500, Clint Adams wrote:
> This would mean that any sarge users upgrading to etch would be stuck
> at ion3 20050502 instead of 20061223. Is that preferable to
> allowing fresh installs to have ion3?
Yes: at least there won't be new users with ancient releases.
--
Tuomo
-
On 2007-03-06 14:50 +0200, Tuomo Valkonen wrote:
> They have their bug report, and chose to ignore it.
And besides, it's the job of the package maintainer to not include
unstable/development software in a "stable" distribution. The
upstream can not be expected to track the relea
On 2007-03-06 14:44 +0200, Riku Voipio wrote:
> Please don't overreact with such horrible licencing change.
> It is possible to have development version removed from stable/testing,
> while it is still available in unstable for powerusers and
> bleeding edge fanciers.
They have their bug report, a
On 2007-03-05 17:28 +0100, Bernhard R. Link wrote:
> Having things not mega-freezed means
> either having to watch for important changes (like, say,
> no longer starting in default configuration) throughout
> the whole year, or just throwing unusual stuff out of the
> supported pre-installed pool
On 2007-03-05 15:53 +0100, Norbert Tretkowski wrote:
> * Tuomo Valkonen wrote:
> > And once you do that for every development/unstable package, you're
> > halfway to having switched away from the megafreeze model to a
> > stable base + extra packages model.
>
On 2007-03-05 15:01 +0100, Holger Levsen wrote:
> there is http://backports.org for updates in stable... (As Nobse knows :)
If it only was easier and better documented to start using
backports.org, automatically by apt*. But it still doesn't
solve the problem of users complaining about old versio
On 2007-02-22 18:54 +0100, Loïc Minier wrote:
> I'm afraid it took a long time before this was considered. Can you
> confirm you still get this bug?
No, I haven't seen it in ages.
--
Tuomo
Hmm... I didn't get CC'd the reply. In any case, as you can see from
my report, I'm _not_ using amd64, but plain old i386. And, no, I
can't be bothered to manually compile anything. I'll just stick
to mplayer then... Bah.
--
Tuomo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject o
Forget the example. 'gcc prog.o bar.a lib.a' does actually work, but
achieveing such a _meticulous_ ordering isn't always a simple task in
a real program with a big list of files to link, constructed by rules
in Makefiles and scripts. Thus the bug stands: the linker is too stupid,
the order of f
Package: binutils
Version: 2.16.1cvs20060413-1
Severity: important
The linker's (or GCC's) dependency handling is too stupid.
Suppose we have the files prog.o, mod.a and lib.a, and
only the following dependencies:
prog.o: mod.a lib.a
mod.a: lib.a
with the mod.a depending on sym
Package: xorg
Version: 1:7.0.20
Severity: critical
Justification: breaks the whole system
Thank you very much for moving everything from under /usr/X11R6 to the mess
known as the /usr hierarchy. Now nothing works. After spending a lot of time
to even manage to get X install after upgrade _removed
Package: bash
Version: 3.1-2
Severity: wishlist
The ssh completion stuff should be moved from /etc/bash_completion
to /etc/bash_completion.d/ssh or something like that. That way I can
load those few useful "advanced" completion features from my .bashrc
that I want, but skip loading the other ann
Package: exim
Version: 3.36-18
Severity: important
After recent upgrade exim stopped working at all. 'mail' and 'mutt'
simply report
"Can't send mail: sendmail process failed with error code 1"
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'te
I want to chime in and add that if this issue is not fixed by the time
the new firefox hits testing, I will be forced to switch to non-free
software: Opera. It's the only semi-usable graphical browser left then.
It is in many ways better than Firefox. The only reason I've been
using Firefox is the
On a closer look, the font in that screenshot for which part the text is
actually readable is infact _not_ Helvetica, but probably some TTF font
then. In programs that do actually use Helvetica (e.g. Firefox), there are
no problems. I think I forced Firefox to use Helvetica with its own
configurat
Package: libgtk2.0-0
Version: 2.8.9-2
Severity: important
I'm not actually sure of the package, but various gtk applications have
started to print out just point clouds instead of text recently. Not
all the time, but possibly alternating between point clouds and proper
text between updates. An im
On 2005-12-13 14:19 -0800, Debian Bug Tracking System wrote:
>[ Thomas Hood ]
>* Remove obsolete .asoundrc example for enabling dmix. dmix is now
> enabled by default for all sound cards that support it
> (Closes: #340763, #342026)
How's this supposed to fix the problem? IIRC th
Package: cryptsetup
Version: 20050111-4
Severity: normal
The /etc/init.d/cryptdisks script should check that a (x86) hard disk
partition device is marked as a swap partition in the partition table
before running mkswap on it. This is to avoid overwriting useful data
in case the hard disks get swa
Package: alsa-utils
Version: 1.0.9a-4
Severity: important
After an upgrade today, the dmix plugin stopped working.
$ mocp # or any other program trying to use alsa
ALSA lib pcm_direct.c:812:(snd_pcm_direct_initialize_slave) requested or
auto-format is not available
ALSA lib pcm
Package: aptitude
Version: 0.2.15.9-6
Severity: important
Aptitude dist-upgrade reinstalls packages removed with dpkg -r or other
package tools. Although perhaps intended, this behaviour seriously hinders
the usability of the package. If I remove a package -- with any tool -- I
most certainly do
Package: general
Severity: grave
Justification: causes non-serious data loss
Apt-get upgrade just moments ago removed my /usr/local/ symlink and
replaced it with a hierarchy of empty directories. The contents of
the proper /usr/local/ on another disk seem to be intact.
The contents of the new /u
30 matches
Mail list logo
