-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ralf Mardorf wrote: > Kevin Donnelly wrote: >> On Wednesday 07 October 2009 09:19, Ralf Mardorf wrote: >> >>> There seems to be a bug in the 64 Studio repository. >>> >> With respect, Ralf, this isn't true - Synfig starts OK here, and seems to >> run >> OK. >> >> I think you're ignoring the advice given to you by a number of people on a >> number of occasions in the past, namely - use the install as released, and >> only make changes if you know in advance what the likely outcome will be. > > Perhaps it's a problem of the packages. The Ubuntu version is fine, the > 64 Studio one isn't, there's no package for the GUI.
Weird since both Ubuntu and 64Studio are using the exact same version. In fact if you had actually bothered to look at the package, you might have noticed this little gem: Maintainer: Ubuntu MOTU Developers <[email protected]> This is what I mean when I talk about spurious reports later on. As a tester, it is expected that you do some homework. Perhaps actually make it easier for developers (upstream or otherwise) to fix real problems. Simply shouting "its broken, something is wrong... PLEASE FIX!" is not good enough. Part of being an effective tester is being able to report problems to the right people. The problem might be with 64Studio or it might lay upstream with the maintainer(s) or further upstream with the original source. Someone has to do that work and the system works best when the testers and QA people do that work, freeing up the developers time to spend it actually coding. This is not a set in stone rule, but one I have seen work very successfully both in open source projects and commercial ones. > >> If the install as released doesn't do what you want, then sorry - you have >> to >> go back to Microsoft Windows or Apple Mac OSX; obviously Linux is not yet >> sophisticated enough for your needs. >> > > This sucks :( ... I started with Linux on the PC, I'm not from Windows > or MacOS. IIRC your first posts to this list referenced Windows XP. > >> But if you decide to stick with Linux in spite of the shortcomings you have >> identified, you shouldn't start making changes willy-nilly (eg weird things >> like setting up chroots) - it then becomes impossible to know whether the >> issue you face is present in the release, or (more likely) is due to your >> tinkering, and in that case no-one on earth can tell you what you should do >> to revert. >> > > This sucks too :(. Chroot has no impact to Synfig, Fmit or any other > buggy stuff, it might has impact to a auto-mount problem, but anyway I have no idea what you are trying to accomplish here. Whenever I have problems (in life in general not just software), I find that the KISS principle has served me well. Especially when doing QA and testing work, instead of making things more complicated, it is usually best to simplify your process so that you can more easily zero in on the problem. YMMV. > note that I do changes level-headed. 64 Studio is a beta and that's why Adding Ubuntu and Debian sources and then doing some sort of tar backup and restore (seemingly at random) is not my idea of a level headed approach to software testing. > it's okay that there is a problem with the 64studio package, but this > isn't because I install software to my 64 Studio or because I set up my > machine to my needs, btw. similar changes had no bad effect when I did > them on other distros ;). > Just because you say that does not make it so. Do you actually know what the differences are between the distros so that you know exactly how and why certain changes behave differently between different distributions? This is a rhetorical question since your behavior has already answered that question for me. <snip> > 1. Linux is flexible, that's why people should be able to do changes. The corollary to this is that one then takes responsibility for the changes one makes. This is the key to Free Libre Open Source Software. > 2. For a beta there could be bugs and those bugs should be reported. > The only problem I have with your bug reports is that your system tends to not reflect the actual released beta which makes it difficult to sort out exactly where the bugs are. I can say that I have yet to reproduce any of the bugs that you have reported, though I have not had the time to test every single "report" that you have made. That is not to say that you may not be finding legitimate bugs, but they will get buried by the noise of your spurious reports. > Btw. I do have experiences with computers since around 20 years, this > grotesque wars only exists for Linux, I never noticed this for QL, > Commodore, Atari etc. ... > You obviously never used Usenet (NNTP) in the early '90s. This sort of thing goes with the territory with respect to Internet communities. My experience is that this is not specific to FLOSS communities, but it seems to plague any community that has a degree of anonymity to it. The loud mouth at the back of a large class for example. Anonymity brings out the worst of humanity. > Disgusting! I only speak well about 64 Studio, I'm not from Windows or > MacOS. Actually you have made many comparisons to Windows with respect to "professional" audio. Having said that, I don't care where you "came from". I applaud your enthusiasm and I look forward to your future contributions. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFK1CUfwRXgH3rKGfMRAtNAAJ0QkH3ey67Xn5MWTEMutLp/2TUmagCgkV6V q+jh2rAsSBVmcIpmO3Zg1hs= =l5qG -----END PGP SIGNATURE----- _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
