Re: with every small update comes a new problem...
Hi, Am Donnerstag, 6. April 2006 13:43 schrieb Michel Dänzer: > Also, if you had the apt-listchanges package installed and set up to > display changelogs, you should have seen this: > > xorg-x11 (6.9.0.dfsg.1-6) unstable; urgency=high > > * Disable new evdev driver patches to prevent FTBFS on mipsen. Thanks > Ryan Murray. (closes: #360540) > > -- David Nusinow <[EMAIL PROTECTED]> Mon, 3 Apr 2006 07:18:50 -0400 Ah, that's what i was looking for for some time now. Thanks for the hint! > The idea of this change is to expedite the transition to testing of the > last packages built from the monolithic X tree in order to allow the > upload of packages built from the modular X trees to sid, where the new > evdev driver will be available as a package of its own. Ah, i see. But what is with the number of buttons? Why're they sometimes 20, then 32 or 16? There's no Option "Buttons" for the evdev driver, which is sad, because i'd set it to 10 and would have never again problems with those long xmodmap lines ;) > I'm afraid some amount of vigilance is required for running sid or even > testing. Unless you like surprises, of course. :) I know. Over the years i learned to fix the problems myself. :) But there's something i don't understand. Like those problems with the number of buttons. Regards, Matthias PS: I'm really looking forward to xorg 7.0. :)
Re: with every small update comes a new problem...
On Thu, 2006-04-06 at 13:15 +0200, Matthias Heinz wrote: > > Please, if you change something like "Device" to "Phys", don't change it back. > (or is there something like a global news-mailinglist i could subscribe to, > where those small changes get posted? I looked around but couldn't find > something similar. It would be nice to be informed about such changes) This list gets an automated notice of every change made to the SVN repository. Also, if you had the apt-listchanges package installed and set up to display changelogs, you should have seen this: xorg-x11 (6.9.0.dfsg.1-6) unstable; urgency=high * Disable new evdev driver patches to prevent FTBFS on mipsen. Thanks Ryan Murray. (closes: #360540) -- David Nusinow <[EMAIL PROTECTED]> Mon, 3 Apr 2006 07:18:50 -0400 The idea of this change is to expedite the transition to testing of the last packages built from the monolithic X tree in order to allow the upload of packages built from the modular X trees to sid, where the new evdev driver will be available as a package of its own. I'm afraid some amount of vigilance is required for running sid or even testing. Unless you like surprises, of course. :) -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast| http://svcs.affero.net/rm.php?r=daenzer
with every small update comes a new problem...
Hi there, i know xorg is a big program and not easy to handle and you're all doing your best to update it. But with every minor version i get some new problems. Often because i'm using evdev for my mouse to get all buttons working just a small list: - numbers of Buttons for my mouse is changing. Sometimes 20, then 32, then 16, after the next update again 32... - then buttons are somtimes permuted. (today it's 1 for the left button, 2 for the right button and 3 for the middle mouse button. So 2 and 3 have to be swapped with xmodmap.) - or the next thing was: After an update X couldn't find my mouse device. I wrote a bug report and was told that Option "Device" isn't used anymore and i should use "Phys" instead. I did and it worked (with some minor things... if you rename your event device with udev Xorg can't find the device and wont start). Today Xorg didn't startup - again - and i found out that "Phys" isn't used anymore and i had to specify a device. Please, if you change something like "Device" to "Phys", don't change it back. (or is there something like a global news-mailinglist i could subscribe to, where those small changes get posted? I looked around but couldn't find something similar. It would be nice to be informed about such changes) Have a nice day, Matthias PS: I'm not on the list and wont get your answers if you don't CC me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
