site  contact  subhomenews

Woof2 now online

November 27, 2011 — BarryK
I announced this in the previous blog post:
http://bkhome.org/archive/blog2/201111/woof2-fossil-is-back.html

I did a test download and build a x86 Dpup, it worked, so it all looks sane. I have modified some scripts since then, but hopefully it is still sane.

Woof2 is hosted in a Fossil Version Control System (or Content Management System):
http://bkhome.org/fossil/woof2.cgi/index

This wiki page explains how to download and install Woof2:
http://bkhome.org/fossil/woof2.cgi/wiki?name=Getting+Started+with+Woof

If you login as an 'anonymous' user, you can click on 'Files', then 'README-FIRST' to read some introductory notes about Woof2.

Comments

forum error
Username: previously known as aarf
[code]Searching for *aarf by Title... Software error: Quantifier follows nothing in regex; marked by <-- HERE in m/* <-- HERE aarf/ at bk_pplog.pl line 1059. For help, please send mail to the webmaster (we#b#mast#er@b#kho#me.pupp#yli#nux.com), giving this error message and the time and date of the error.[/code]

problems I fear...
Username: scsijon
"using your getting started page step3 after starting "# fossil clone --admin-user MrSmith http://bkhome.org/fossil/woof2.cgi woof2.fossil" it responded to a line 'waiting for server ....' and nothing more until the third block came down, then all appeared and went from there ok -maybe a warning to give it time to process is needed. step4 1/ fyi, the latest firefox 7/8 has moved to /usr/lib/firefox/firefox, there is nothing in /usr/local/bin anymore. and 2/ after entering "# fossil ui woof2.fossil" and going to admin settings, all i'm seeing is "invalid home directory: /root" in red. My builds live on their own separate partition, would that cause this? regards scsijon

logout
Username: scsijon
"Just found I can't logout either. oh well, back to woof1 :-)}

Woof Woof
Username: lobster
"Followed wiki info Have woof2 on my system - no problems Created Woof2 category on new forum http://puppylinux.info/topic.php?id=94#post-604

Re problems
Username: BarryK
"scsijon, If you follow the instructions exactly, it should work. It is irrelevant where Firefox is installed. The purpose of the symlink in /usr/local/bin is only in case of no 'firefox' executable, as Fossil defaults to needing firefox for web interface. It doesn't matter if you can't logout from the local web interface.

Woof2 cross-build
Username: BarryK
"It is important to know that Woof2 does not yet build an ARM Dpup. I am part-way there. Woof2 is designed to do a "cross build", that is, running on a x86 system, you can build for a ARM target. The only thing that I have tested successfully so far, as a sanity test, was an x86-host, x86-target Dpup, Debian Squeeze. What I hope to get going next, in the not-to-distant-future is a x86-host, arm1176jzf-s-target Dpup Debian Squeeze build.

woof3 (:o)
Username: mavrothal
"Fossil is a really nice step forward in woof ! Is not git/mercurial but is pretty easy to learn and has most/all the needed functions and some more ;) For woof3 you might want to consider build scripts instead of binaries (like iguleder's and your kernel scripts). The advantage would be that: - the whole process becomes transparent, - can easily keep up with development of upstreams and - the binaries can easily be modified at build time (something that could be important when building for other arches). Devices will be the only remaining non-text files, though they could be kept to 4-5 in the initrd if udev w/extras goes in the builds (actually is hardly 250k extra and may solve some/many issues with various hardware) We try to do something like that with the OLPC-XO builds (https://github.com/mavrothal/Pox_git) but at a much simpler scale and I find it pretty easy to maintain after the first build. Thanks again.

pctel Invalid module format error on both wary 5.2.2 and 5.1.4.1
Username: charlie6
"Hi Barry, I appreciate the later wary's. Many thanks for them! I got this: pctel Invalid module format module does not work on both wary 5.2.2 and 5.1.4.1 No error message when modprobing linmodem and pctel_hw yet. Got this messages when doing in a console on a fresh frugal install of wary 5.2.2 [code]# uname -r 2.6.32-uni # depmod # modprobe ndiswrapper # modprobe linmodem # modprobe pctel FATAL: Error inserting pctel (/lib/modules/2.6.32-uni/misc/pctel.ko): Invalid module format # modprobe pctel_hw # [/code] Nevertheless, as modules pctel_hw and linmodem are working, and are compiled together with pctel, pctel would work as well, wouldn't? Thanks for any help Cheers, Charlie

Re pctel
Username: BarryK
"Yeah, I would have thought pctel module would be ok. But, ess also creates linmodem.ko, and that may have overridden the one in pctel, depends which order I compiled them. The ess source maintaimer told me that his linmodem code is same as used in pctel project, so there should not be any problem. But, perhaps there is.

pctel dialup modem on wary 5.2.2 and 5.1.4.1
Username: charlie6
"Hi Barry, posting this using PCTel dialup modem on wary-5.1.4.1... so it actually works ! Thanks again ! Charlie

Re binaries in Woof2
Username: BarryK
"[i]For woof3 you might want to consider build scripts instead of binaries (like iguleder's and your kernel scripts). [/i] It would be nice to eliminate executable binaries. One significant problem is that Woof2 is designed to do cross-builds. For example, you can run Woof2 on a x86 PC and build a Puppy for a arm target. Thus, the binaries would have to be compiled with a cross-compiler. Some applications are difficult or maybe even not capable of being cross-compiled, unless a complete VM is setup. There are of course architecture-independent binary files in Woof2, such as some video, audio, document and image files.

binaries and cross-compiler.
Username: mavrothal
"I would think that exactly because of that (cross-compiling) and given that the ARM field is evolving fast, providing build scripts may facilitate and speedup development. There are many excellent "compilers" in the puppy community that could tinker with them and provide patches. Excluding firmware and images there are less than a 100 binaries. Still too many I think for a single person to optimize. But what do I know... ;-) Best

Can't push to server
Username: noryb009
"I am unable to push changes to Woof2. How are you supposed to? [code]# fossil push Server: http://bkhome.org/fossil/woof2.cgi Bytes Cards Artifacts Deltas Sent: 1740 36 0 0 Error: not authorized to write Received: 65 1 0 0 # fossil sync Server: http://bkhome.org/fossil/woof2.cgi Bytes Cards Artifacts Deltas Sent: 1843 38 0 0 Server says: pull only - not authorized to push Received: 1553 34 0 0 Total network traffic: 1147 bytes sent, 1192 bytes received [/code]

Re Woof2 push
Username: BarryK
"Ha ha, you expect that I would allow everyone to push to the online Woof server?!!! I will probably give 'developer' accounts to a few people sometime, but do not know when that will happen. I have to think how to set that up. I'm still a Fossil newbie.

allow-symlinks fixed
Username: BarryK
"In the Getting Started instructions for Woof, I advised that after running the "fossil clone ..." operation, it was necessary to run "fossil ui woof2.fossil" and tick the 'allow-symlinks' checkbox. This is a bug in Fossil 1.20. I raised this in the Fossil mail-list, and I am pleased that Dr. Hipp has committed a fix: http://www.fossil-scm.org/fossil/ci/82979bc210?sbs=1

Tickets
Username: mavrothal
"Is understandable/wise not to allow everyone to "push". What about generating a ticket though? Among other things, small patches could be submitted within tickets for "review".

re Woof1
Username: BarryK
"Woof1 is history.

Regarding the invalid home page: /root
Username: uten
"I just started fossil to get woof2. Had to compile version 1.22 to get it working on slacko. Did some testing for my own usage and encountered quite fast the invalid home page: /root message when I tried to get to settings. The explanation and a workaround to the problem can be found here: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg05805.html Make a folder called root in the repository folder. Make it available to all(? did not test anything else)

Re Fossil versions
Username: BarryK
"uten, Thanks for that information. I am running 1.20 without any problem. 01micko, the coordinator of Slacko, reported that he tried a later version of Fossil and encountered problems, so he used 1.20 and that worked. But, 01micko did not specify what the problem was with later version -- probably it was the same thing that you are reporting? I know that the problem that you report appeared in 1.19, but I see the author posted that he would fix it, so maybe there is a fix in 1.20, which disappeared again later? -- wild speculation!


Tags: woof