I was hoping to meet Hypatia and her man tonight, but maybe next time. In any case, many of the linuxchix met up at Boom Noodle, and ate a delicious meal. Then we walked up East Pike to Caffe Vita, and shared delicious coffee and tech talk. Although I connected to the Boom Noodle wireless without a problem, it was impossible to connect here at Caffe Vita. I finally was able to connect through Kevin's tethered iPhone! And download nmap. :-)
I'm not entirely sure what's up with my wireless card, but it must not be toast, because it eventually worked.
Meryll Larkin taught us how to test our security with nmap, and helped me set up a firewall with hosts.allow and hosts.deny files. Then she tried to hack me -- without success. :-)
Also, I started up Amarok and successfully scrobbled to Last.fm, so my hosts.allow file is working well.
Life is good.
Linuxchix is at http://www.linuxchix.org, Amarok at http://amarok.kde.org, Last.fm at http://last.fm.
Tuesday, June 8, 2010
Wednesday, May 5, 2010
Girls Using *Buntu -- Win a Netbook!
Ubuntu Women has launched another competition!
http://wiki.ubuntu-women.org/Events/Competitions/WorldPlayDay
Nine days left to enter -- get the word out to any *buntu-using girls! Posters and such are available.
If you're interested in spreading the word throughout the twitter and
status.net circles, the original status updates are:
http://twitter.com/elkbuntu/statuses/12112708587
http://identi.ca/notice/28397262
A quick howto for entering:
http://wiki.ubuntu-women.org/Events/Competitions/WorldPlayDay/HowToEnter
Win that little girl a netbook or other cool geeky stuff. :-)
http://wiki.ubuntu-women.org/Events/Competitions/WorldPlayDay
Nine days left to enter -- get the word out to any *buntu-using girls! Posters and such are available.
If you're interested in spreading the word throughout the twitter and
status.net circles, the original status updates are:
http://twitter.com/elkbuntu/statuses/12112708587
http://identi.ca/notice/28397262
A quick howto for entering:
http://wiki.ubuntu-women.org/Events/Competitions/WorldPlayDay/HowToEnter
Win that little girl a netbook or other cool geeky stuff. :-)
Friday, April 23, 2010
Locked out of my own website!
I tried to ssh into our server, now hosted at linode.net. I got a notice, all scary-like:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for zimres.net has changed,
and the key for the corresponding IP address 74.207.247.190
is unchanged. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
Offending key for IP in /home/valorie/.ssh/known_hosts:4
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
Of course, that last bit is the important part. The host key has been changed. How to fix that at my end? My son said to edit out the line in my ~/.ssh/known_hosts file. However, when I opened Kate to edit it, I saw:
|1|2ZZc4RXTORIrgsDBWb2zqWRRw8s=|ZJCjvrfPLAEPwVQ6lGdYtVhoAK0= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAqp3hNrWz5ZWwogg1In70rBynezwkleYbOAgtDdbR7dfrcGJC/deLeprn+bXgfeO058EeHqAeU0be5tn1siui+GWm9rQ1PEfrT46fZCgSWeZVYVcQ5vRQItN/a6XFe00WPWrYEhXwgmM6la2gm8kOa5kCTSDOIN8v5XcqA85Pbnd57zmAcVWejaYndk1SkO9V1ctrxz8yGM6NuN+ThawQaLa1tWuj4aKFNWj2DBc3Dyx1IztUFdN0GcIRRg47qwU7KQGqv/2g77gsRmSvVILrRy1CR82lrsxpo5SdvMkqFJQSz/jyTN1x/6FbGJjAwkhIBQXkpQyxmQwzFb/Hf/pgMw==
|1|qZ+nY7U1kgMnDp26n6sdtbh+lmQ=|KGnxdNek7Rs137p3NgH3ZaLijdI= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAqp3hNrWz5ZWwogg1In70rBynezwkleYbOAgtDdbR7dfrcGJC/deLeprn+bXgfeO058EeHqAeU0be5tn1siui+GWm9rQ1PEfrT46fZCgSWeZVYVcQ5vRQItN/a6XFe00WPWrYEhXwgmM6la2gm8kOa5kCTSDOIN8v5XcqA85Pbnd57zmAcVWejaYndk1SkO9V1ctrxz8yGM6NuN+ThawQaLa1tWuj4aKFNWj2DBc3Dyx1IztUFdN0GcIRRg47qwU7KQGqv/2g77gsRmSvVILrRy1CR82lrsxpo5SdvMkqFJQSz/jyTN1x/6FbGJjAwkhIBQXkpQyxmQwzFb/Hf/pgMw==
|1|U+ZwcJShMD52Hxfk+BnxgfDnH4o=|QepSzrHlsR1vchO12+soBb1mAwo= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAysa2byLN+E1SeM8Wo7kMGLE+BPAg3nkKg5OhKmssRj945kKuqCBy3wvwVcrfe4zSvVMfotN06tAvmdflFokNXv9ANZJ9qu42HeFxNwkIz04w5E9YeHEG4rTtUW0dSsp13kcaU5Jp3z60C4QNUfZuNOGQmV+yYlOCiLXgR6eYmtkC+/hKZhPkO4GbxwLlEzW5Rzd8vy5czN87Pnr4Z1a/g+T+xKil8B2K41160+GQQNIPfYUCGnA9ccw1kRmWIYV+omJieXiigawUvhnQoHmWRllUhOq6y5jhvQVseO7S+EVFobMFxZ/P2+SzOlg2KaZu/8M0YZtxcrSM8NHnZLq+iw==
|1|b6NemVdIE2FvkU5/cH5FXaDbUks=|Hr4ppmN0hOhCb5ey2NS1yaeuits= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAysa2byLN+E1SeM8Wo7kMGLE+BPAg3nkKg5OhKmssRj945kKuqCBy3wvwVcrfe4zSvVMfotN06tAvmdflFokNXv9ANZJ9qu42HeFxNwkIz04w5E9YeHEG4rTtUW0dSsp13kcaU5Jp3z60C4QNUfZuNOGQmV+yYlOCiLXgR6eYmtkC+/hKZhPkO4GbxwLlEzW5Rzd8vy5czN87Pnr4Z1a/g+T+xKil8B2K41160+GQQNIPfYUCGnA9ccw1kRmWIYV+omJieXiigawUvhnQoHmWRllUhOq6y5jhvQVseO7S+EVFobMFxZ/P2+SzOlg2KaZu/8M0YZtxcrSM8NHnZLq+iw==
What the heck? I went to #linuxchix to seek counsel, and rik was around to tell me that that's a hash of the hostnames. He said, "the idea of hashing the hostnames was to stop an exploit [of someone who] got in as one user then using your keys (if you had then in an agent) to ssh in to every other host in your known_hosts file." Which would be a bad thing!
So in the console, I ran ssh-keygen -R zimres.net
and got back: /home/valorie/.ssh/known_hosts updated.
Original contents retained as /home/valorie/.ssh/known_hosts.old
and wooooohooooooooooo I'm in!
Thank you Thomas, rik and the linuxchix!
Thanks to all my commenters, too. Once I knew what was going on, the error message made more sense to me. That's the problem with error messages the first time you see them; you don't know enough to make sense of them. Often I google the error feedback in quotes, and sometimes that gets me the answer I need. Perhaps I should have tried that this time, but whining in IRC worked faster. :-)
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for zimres.net has changed,
and the key for the corresponding IP address 74.207.247.190
is unchanged. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
Offending key for IP in /home/valorie/.ssh/known_hosts:4
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
Of course, that last bit is the important part. The host key has been changed. How to fix that at my end? My son said to edit out the line in my ~/.ssh/known_hosts file. However, when I opened Kate to edit it, I saw:
|1|2ZZc4RXTORIrgsDBWb2zqWRRw8s=|ZJCjvrfPLAEPwVQ6lGdYtVhoAK0= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAqp3hNrWz5ZWwogg1In70rBynezwkleYbOAgtDdbR7dfrcGJC/deLeprn+bXgfeO058EeHqAeU0be5tn1siui+GWm9rQ1PEfrT46fZCgSWeZVYVcQ5vRQItN/a6XFe00WPWrYEhXwgmM6la2gm8kOa5kCTSDOIN8v5XcqA85Pbnd57zmAcVWejaYndk1SkO9V1ctrxz8yGM6NuN+ThawQaLa1tWuj4aKFNWj2DBc3Dyx1IztUFdN0GcIRRg47qwU7KQGqv/2g77gsRmSvVILrRy1CR82lrsxpo5SdvMkqFJQSz/jyTN1x/6FbGJjAwkhIBQXkpQyxmQwzFb/Hf/pgMw==
|1|qZ+nY7U1kgMnDp26n6sdtbh+lmQ=|KGnxdNek7Rs137p3NgH3ZaLijdI= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAqp3hNrWz5ZWwogg1In70rBynezwkleYbOAgtDdbR7dfrcGJC/deLeprn+bXgfeO058EeHqAeU0be5tn1siui+GWm9rQ1PEfrT46fZCgSWeZVYVcQ5vRQItN/a6XFe00WPWrYEhXwgmM6la2gm8kOa5kCTSDOIN8v5XcqA85Pbnd57zmAcVWejaYndk1SkO9V1ctrxz8yGM6NuN+ThawQaLa1tWuj4aKFNWj2DBc3Dyx1IztUFdN0GcIRRg47qwU7KQGqv/2g77gsRmSvVILrRy1CR82lrsxpo5SdvMkqFJQSz/jyTN1x/6FbGJjAwkhIBQXkpQyxmQwzFb/Hf/pgMw==
|1|U+ZwcJShMD52Hxfk+BnxgfDnH4o=|QepSzrHlsR1vchO12+soBb1mAwo= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAysa2byLN+E1SeM8Wo7kMGLE+BPAg3nkKg5OhKmssRj945kKuqCBy3wvwVcrfe4zSvVMfotN06tAvmdflFokNXv9ANZJ9qu42HeFxNwkIz04w5E9YeHEG4rTtUW0dSsp13kcaU5Jp3z60C4QNUfZuNOGQmV+yYlOCiLXgR6eYmtkC+/hKZhPkO4GbxwLlEzW5Rzd8vy5czN87Pnr4Z1a/g+T+xKil8B2K41160+GQQNIPfYUCGnA9ccw1kRmWIYV+omJieXiigawUvhnQoHmWRllUhOq6y5jhvQVseO7S+EVFobMFxZ/P2+SzOlg2KaZu/8M0YZtxcrSM8NHnZLq+iw==
|1|b6NemVdIE2FvkU5/cH5FXaDbUks=|Hr4ppmN0hOhCb5ey2NS1yaeuits= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAysa2byLN+E1SeM8Wo7kMGLE+BPAg3nkKg5OhKmssRj945kKuqCBy3wvwVcrfe4zSvVMfotN06tAvmdflFokNXv9ANZJ9qu42HeFxNwkIz04w5E9YeHEG4rTtUW0dSsp13kcaU5Jp3z60C4QNUfZuNOGQmV+yYlOCiLXgR6eYmtkC+/hKZhPkO4GbxwLlEzW5Rzd8vy5czN87Pnr4Z1a/g+T+xKil8B2K41160+GQQNIPfYUCGnA9ccw1kRmWIYV+omJieXiigawUvhnQoHmWRllUhOq6y5jhvQVseO7S+EVFobMFxZ/P2+SzOlg2KaZu/8M0YZtxcrSM8NHnZLq+iw==
What the heck? I went to #linuxchix to seek counsel, and rik was around to tell me that that's a hash of the hostnames. He said, "the idea of hashing the hostnames was to stop an exploit [of someone who] got in as one user then using your keys (if you had then in an agent) to ssh in to every other host in your known_hosts file." Which would be a bad thing!
So in the console, I ran ssh-keygen -R zimres.net
and got back: /home/valorie/.ssh/known_hosts updated.
Original contents retained as /home/valorie/.ssh/known_hosts.old
and wooooohooooooooooo I'm in!
Thank you Thomas, rik and the linuxchix!
Thanks to all my commenters, too. Once I knew what was going on, the error message made more sense to me. That's the problem with error messages the first time you see them; you don't know enough to make sense of them. Often I google the error feedback in quotes, and sometimes that gets me the answer I need. Perhaps I should have tried that this time, but whining in IRC worked faster. :-)
Saturday, April 17, 2010
Kaudiocreator Returns in KDE4
UPDATE on Kaudiocreator:
Thanks to Apachelogger, the KaudioCreator package is now available as part of kdemultimedia https://launchpad.net/ubuntu/+search?text=kaudiocreator. This is the BEST cd-ripper I've ever used, and I hope the wonderfulness came across to KDE4.
The programmer can be contacted on KDE-Apps: http://kde-apps.org/content/show.php/KAudioCreator?content=107645
Audex is also available; somewhat of a fork of this wonderful program. Thanks so much to the programmer to porting to KDE4. I appreciate it very much!
PS: Audex can be found here: http://kde-apps.org/content/show.php/Audex?content=77125
I also like Sound Juicer, but reinstalling it would have pulled in about 20 other packages, so no! I'm now happily ripping a classical CD, by the way. :-)
Oh, and by the way, I know I can rip CDs inside of Amarok, and I'm glad for that capability. But I'm pretty picky about tags, and like to rip to a directory outside of my collection, so I can check the tags before moving the files inside my collection. That way Amarok displays everything correctly from first play.
Followup note: While I still try KAudioCreator first, I have to use Sound Juicer about a quarter of the time in Lucid. While K "allows" edits to what it finds from Freedb, some those edits aren't used! Also, if the CD has any scratches, it tends to go into a tizzy, and have to be killed. Audex now crashes on startup every time, and leaves me no backtrace. I guess I could run in gdb, but really, no debugging package available? So Sound Juicer is a good fallback, even with all those dependencies. I also tried RipperX again -- still UGH! and also the CLI program abcde. Not only too techie for me, also no choices of tracks or tags.
Thanks to Apachelogger, the KaudioCreator package is now available as part of kdemultimedia https://launchpad.net/ubuntu/+search?text=kaudiocreator. This is the BEST cd-ripper I've ever used, and I hope the wonderfulness came across to KDE4.
The programmer can be contacted on KDE-Apps: http://kde-apps.org/content/show.php/KAudioCreator?content=107645
Audex is also available; somewhat of a fork of this wonderful program. Thanks so much to the programmer to porting to KDE4. I appreciate it very much!
PS: Audex can be found here: http://kde-apps.org/content/show.php/Audex?content=77125
I also like Sound Juicer, but reinstalling it would have pulled in about 20 other packages, so no! I'm now happily ripping a classical CD, by the way. :-)
Oh, and by the way, I know I can rip CDs inside of Amarok, and I'm glad for that capability. But I'm pretty picky about tags, and like to rip to a directory outside of my collection, so I can check the tags before moving the files inside my collection. That way Amarok displays everything correctly from first play.
Followup note: While I still try KAudioCreator first, I have to use Sound Juicer about a quarter of the time in Lucid. While K "allows" edits to what it finds from Freedb, some those edits aren't used! Also, if the CD has any scratches, it tends to go into a tizzy, and have to be killed. Audex now crashes on startup every time, and leaves me no backtrace. I guess I could run in gdb, but really, no debugging package available? So Sound Juicer is a good fallback, even with all those dependencies. I also tried RipperX again -- still UGH! and also the CLI program abcde. Not only too techie for me, also no choices of tracks or tags.
Friday, April 16, 2010
Lucid beta, bugs, and Alsamixer
The ongoing saga of running a beta release, I guess. Everything was pretty cool for 10 days or so, but then......
A few days ago, my laptop lost its voice. After doing some update or another, there was NO sound, except an occasional odd clicking noise when instead it should have been playing a music track. In KDE, one can test various sound devices and services in System Settings > Multimedia. This is also, by the way, where you see what backends are available to you, such as Gstreamer, Xine or VLC. This same window is used in Amarok to configure Playback > Phonon. Once sound disappeared, this configuration window in System Settings started crashing, so I filed a bug about that. Actually, it's still crashing, even now that I have sound back.
The nice part about filing that bug is that the crash handler AKA Dr. Konqui now asks you, if certain debugging packages would help display a more helpful backtrace, if you would like to install them. Then it searches the database, fetches the packages and installs them for you. Be sure to reload your report after the installations, of course!
Finally, I went over to Launchpad and filed a bug there about the sound issue, since my tests have revealed that this was a general problem, not a KDE one. https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/558910 if you are interested in this issue.
Salient points: aplay -l displays your sound equipment.
Of course first, I always checked Kmix. Often some channels were muted, but unmuting made no difference. I must have done that 20 times or so. I uninstalled Pulseaudio, which made no difference. I tried booting into next older kernel, still no sound. I used the TTY to run a sound file from Music123, which runs below X. It gave no error message; but appeared to be playing the file. No sound.
I also removed the phonon config in ~/.kde/share/config - no change. Rebooting into my original Kubuntu Lucid beta LiveCD, I heard sound again! After days. More updates, but still no sound.
In desperation, I asked in #unbuntu+1 (Freenode). The kindly folks there commiserated, and one person asked about Alsamixer. I remembered using it in opensuse, so I consulted my blog post here, and opened alsamixer in the console, and then used Ksnapshot to take a screenshot of it.
See where it says Speaker, and MM? Jordan_U kindly pointed out that that meant MUTE, and that I could change that by using the arrow keys to highlight the speaker column, and then use the M key to change to unmuted, which is 00 -- none of which makes any sense to me. However, sound now works! I updated my bug with the new information, because while my problem is solved, there is still a venomous bug, crawling around and biting random people!
Now I can get back to work in Amarok. Wonderful IRC people to the rescue once more! Thanks to Jordan_U and the rest of the helpful folks in #ubuntu+1.
A few days ago, my laptop lost its voice. After doing some update or another, there was NO sound, except an occasional odd clicking noise when instead it should have been playing a music track. In KDE, one can test various sound devices and services in System Settings > Multimedia. This is also, by the way, where you see what backends are available to you, such as Gstreamer, Xine or VLC. This same window is used in Amarok to configure Playback > Phonon. Once sound disappeared, this configuration window in System Settings started crashing, so I filed a bug about that. Actually, it's still crashing, even now that I have sound back.
The nice part about filing that bug is that the crash handler AKA Dr. Konqui now asks you, if certain debugging packages would help display a more helpful backtrace, if you would like to install them. Then it searches the database, fetches the packages and installs them for you. Be sure to reload your report after the installations, of course!
Finally, I went over to Launchpad and filed a bug there about the sound issue, since my tests have revealed that this was a general problem, not a KDE one. https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/558910 if you are interested in this issue.
Salient points: aplay -l displays your sound equipment.
Of course first, I always checked Kmix. Often some channels were muted, but unmuting made no difference. I must have done that 20 times or so. I uninstalled Pulseaudio, which made no difference. I tried booting into next older kernel, still no sound. I used the TTY to run a sound file from Music123, which runs below X. It gave no error message; but appeared to be playing the file. No sound.
I also removed the phonon config in ~/.kde/share/config - no change. Rebooting into my original Kubuntu Lucid beta LiveCD, I heard sound again! After days. More updates, but still no sound.
In desperation, I asked in #unbuntu+1 (Freenode). The kindly folks there commiserated, and one person asked about Alsamixer. I remembered using it in opensuse, so I consulted my blog post here, and opened alsamixer in the console, and then used Ksnapshot to take a screenshot of it.
See where it says Speaker, and MM? Jordan_U kindly pointed out that that meant MUTE, and that I could change that by using the arrow keys to highlight the speaker column, and then use the M key to change to unmuted, which is 00 -- none of which makes any sense to me. However, sound now works! I updated my bug with the new information, because while my problem is solved, there is still a venomous bug, crawling around and biting random people!
Now I can get back to work in Amarok. Wonderful IRC people to the rescue once more! Thanks to Jordan_U and the rest of the helpful folks in #ubuntu+1.
Friday, April 9, 2010
Chmod, and rebuilding from scratch
Before I forget, just a brief note about what I learned yesterday. After some odd errors both in Amarok and during an Amarok re-build, both of which involved permissions, I did a $ sudo chmod 777 /home -R command,* blew away my old Amarok build (going back to empty folders) and successfully rebuilt.
Also, all those tracks with previously un-editable tags -- now editable. So, sudo is no longer required to do a make in $HOME. Perhaps using sudo for that in the first place created some of the problems, so in future, I'll check permissions first!
*I've been advised (thanks, Mamarok!) that 777 is a bad idea, since it gives permission to any and all. chown -R username folder/ is better.
Also, all those tracks with previously un-editable tags -- now editable. So, sudo is no longer required to do a make in $HOME. Perhaps using sudo for that in the first place created some of the problems, so in future, I'll check permissions first!
*I've been advised (thanks, Mamarok!) that 777 is a bad idea, since it gives permission to any and all. chown -R username folder/ is better.
Thursday, April 8, 2010
Scripts, Not Just for Making Movies
A few months ago, I offered to write the Handbook for Amarok, my favorite music software. Along the way to that goal, I began publishing the Amarok Insider, which had been on hiatus for awhile. I've heard it said that the best way to learn something is to teach it to someone else, and this has proven true for me at least in technical writing. I wanted to learn how to build from source, because the more people do this, the more testing can be done before release, instead of after. This makes for more stable releases, and for the newsletter editor, provides advance experience with new features.
We have wonderful help for building Amarok from source should you be interested in doing so, here: http://blogs.fsfe.org/myriam/2009/09/compiling-amarok-from-git-locally-full-summary/. Right now developers are working on a new backend for Amarok, because Xine and Gstreamer, the two available now, are not satisfactory. VLC has the additional advantage of being cross-platform, and Amarok is available for Linux, Windows and Mac. Phonon-VLC, the new backend, is in rapid development like Amarok is, so testers need to build from source in much the same way. Again, Myriam has written the essential guide to installing and updating: http://blogs.fsfe.org/myriam/2010/04/want-to-test-the-phonon-vlc-backend-here-you-go/.
After using her guides to install Amarok, VLC and Phonon-VLC from source (with invaluable personal support from her, and other developers), I decided to make myself a shortened version, with just the commands I need to update and build, since I have all the dependencies installed, and the proper directory structure built. I realized once I had the short list written, that it looked a bit like a script! Here is my list:
Clean build?
rm ~/kde/build/amarok/CMakeCache.txt
rm ~/kde/src/phonon-vlc/build/CMakeCache.txt
Update phonon-vlc
cd ~/kde/src/phonon-vlc/build
git pull
cmake -DCMAKE_INSTALL_PREFIX=$HOME/kde/ -DCMAKE_INCLUDE_PATH=$HOME/kde/include/ -DCMAKE_LIBRARY_PATH=$HOME/kde/lib/ -DCMAKE_BUILD_TYPE=debugfull $HOME/kde/src/phonon-vlc/
make -j3 && sudo make install
Update Amarok
cd $HOME/kde/src/amarok
git pull
cd $HOME/kde/build/amarok
cmake -DCMAKE_INSTALL_PREFIX=$HOME/kde -DCMAKE_BUILD_TYPE=debugfull $HOME/kde/src/amarok
make install
kbuildsycoca4 --noincremental
After this stroke of inspiration, I looked around for some help in building a bash script, but found only tutorials which didn't seem to apply. When I asked on #linuxchix, rik, chf and joh6nn offered to help. We eventually came up with a Makefile, which unfortunately doesn't really work yet, although I don't understand why yet. Here is our product:
# Makefile for updating and building
.PHONY: all install clean all-clean phonon-vlc-clean phonon-vlc-update phonon-vlc-build phonon-vlc-install amarok-clean amarok-update amarok-build amarok-install
.DEFAULT: install
phonon-vlc-clean:
rm ${HOME}/kde/src/phonon-vlc/build/CMakeCache.txt
phonon-vlc-update:
cd ${HOME}/kde/src/phonon-vlc/build
git pull
phonon-vlc-build: phonon-vlc-update
cd ${HOME}/kde/src/phonon-vlc/build
cmake -DCMAKE_INSTALL_PREFIX=${HOME}/kde/ -DCMAKE_INCLUDE_PATH=${HOME}/kde/include/ -DCMAKE_LIBRARY_PATH=${HOME}/kde/lib/ -DCMAKE_BUILD_TYPE=debugfull ${HOME}/kde/src/phonon-vlc/
phonon-vlc-install: phonon-vlc-build
make -j3
sudo make install
amarok-clean:
rm ${HOME}/kde/build/amarok/CMakeCache.txt
amarok-update:
cd ${HOME}/kde/src/amarok
git pull
amarok-build: amarok-update
cd ${HOME}/kde/build/amarok
cmake -DCMAKE_INSTALL_PREFIX=${HOME}/kde -DCMAKE_BUILD_TYPE=debugfull ${HOME}/kde/src/amarok
amarok-install: amarok-build
make install
kbuildsycoca4 --noincremental
all: phonon-vlc-install amarok-install
install: amarok-install
clean: amarok-clean phonon-vlc-clean
all-clean: amarok-clean amarok-install phonon-vlc-clean phonon-vlc-install
Two reasons this isn't finished and working: I had a meeting, and rik had to sleep! I did a make -d all and got a TON of output, the end of which is at http://pastie.org/908564 . My console buffer was full of output! Later I hope to have a finished script to present to those who are interested in building packages from source. The problem so far is that the script seems to skip over or error out on the git pull step. Updates later.
We have wonderful help for building Amarok from source should you be interested in doing so, here: http://blogs.fsfe.org/myriam/2009/09/compiling-amarok-from-git-locally-full-summary/. Right now developers are working on a new backend for Amarok, because Xine and Gstreamer, the two available now, are not satisfactory. VLC has the additional advantage of being cross-platform, and Amarok is available for Linux, Windows and Mac. Phonon-VLC, the new backend, is in rapid development like Amarok is, so testers need to build from source in much the same way. Again, Myriam has written the essential guide to installing and updating: http://blogs.fsfe.org/myriam/2010/04/want-to-test-the-phonon-vlc-backend-here-you-go/.
After using her guides to install Amarok, VLC and Phonon-VLC from source (with invaluable personal support from her, and other developers), I decided to make myself a shortened version, with just the commands I need to update and build, since I have all the dependencies installed, and the proper directory structure built. I realized once I had the short list written, that it looked a bit like a script! Here is my list:
Clean build?
rm ~/kde/build/amarok/CMakeCache.txt
rm ~/kde/src/phonon-vlc/build/CMakeCache.txt
Update phonon-vlc
cd ~/kde/src/phonon-vlc/build
git pull
cmake -DCMAKE_INSTALL_PREFIX=$HOME/kde/ -DCMAKE_INCLUDE_PATH=$HOME/kde/include/ -DCMAKE_LIBRARY_PATH=$HOME/kde/lib/ -DCMAKE_BUILD_TYPE=debugfull $HOME/kde/src/phonon-vlc/
make -j3 && sudo make install
Update Amarok
cd $HOME/kde/src/amarok
git pull
cd $HOME/kde/build/amarok
cmake -DCMAKE_INSTALL_PREFIX=$HOME/kde -DCMAKE_BUILD_TYPE=debugfull $HOME/kde/src/amarok
make install
kbuildsycoca4 --noincremental
After this stroke of inspiration, I looked around for some help in building a bash script, but found only tutorials which didn't seem to apply. When I asked on #linuxchix, rik, chf and joh6nn offered to help. We eventually came up with a Makefile, which unfortunately doesn't really work yet, although I don't understand why yet. Here is our product:
# Makefile for updating and building
.PHONY: all install clean all-clean phonon-vlc-clean phonon-vlc-update phonon-vlc-build phonon-vlc-install amarok-clean amarok-update amarok-build amarok-install
.DEFAULT: install
phonon-vlc-clean:
rm ${HOME}/kde/src/phonon-vlc/build/CMakeCache.txt
phonon-vlc-update:
cd ${HOME}/kde/src/phonon-vlc/build
git pull
phonon-vlc-build: phonon-vlc-update
cd ${HOME}/kde/src/phonon-vlc/build
cmake -DCMAKE_INSTALL_PREFIX=${HOME}/kde/ -DCMAKE_INCLUDE_PATH=${HOME}/kde/include/ -DCMAKE_LIBRARY_PATH=${HOME}/kde/lib/ -DCMAKE_BUILD_TYPE=debugfull ${HOME}/kde/src/phonon-vlc/
phonon-vlc-install: phonon-vlc-build
make -j3
sudo make install
amarok-clean:
rm ${HOME}/kde/build/amarok/CMakeCache.txt
amarok-update:
cd ${HOME}/kde/src/amarok
git pull
amarok-build: amarok-update
cd ${HOME}/kde/build/amarok
cmake -DCMAKE_INSTALL_PREFIX=${HOME}/kde -DCMAKE_BUILD_TYPE=debugfull ${HOME}/kde/src/amarok
amarok-install: amarok-build
make install
kbuildsycoca4 --noincremental
all: phonon-vlc-install amarok-install
install: amarok-install
clean: amarok-clean phonon-vlc-clean
all-clean: amarok-clean amarok-install phonon-vlc-clean phonon-vlc-install
Two reasons this isn't finished and working: I had a meeting, and rik had to sleep! I did a make -d all and got a TON of output, the end of which is at http://pastie.org/908564 . My console buffer was full of output! Later I hope to have a finished script to present to those who are interested in building packages from source. The problem so far is that the script seems to skip over or error out on the git pull step. Updates later.
Subscribe to:
Posts (Atom)