Aaaaaargh!

April 01, 2009 — BarryK

Aaaaaaaaargh!!!! Aaaaaaaaargh!!!!

I have been experimenting with porting Puppy 4.1.2 to build in Woof, when I made a discovery...

Puppy 4.1.2 uses PET package 'jwm2-2.0.1-9.pet', in directory 'pet_packages-4' at ibiblio.

One of the 4.2 developers has done some work on the JWM package, modifying it somewhat, but, and this is what upsets me, they did not change its name. It has remained as 'jwm2-2.0.1-9.pet', which has been uploaded to ibiblio, overwriting the previous file. What this has done is broken the Unleashed build system for Puppy 4.1.2.

This is a major headache. I can fix it I suppose, but I need to know, immediately, from all 4.2 developers who updated a previous package, did you also change the version numbering, or not. I need to know any more cases like JWM.

What I am going to have to ask WhoDo to do, is make sure all changed PET packages have new package names. He can then upload them.

I will reupload whatever packages have got overwritten.

Note, that '-9' in 'jwm2-2.0.1-9.pet' is my own revision numbering system. A 4.2 developer can use any other revision numbering to suit themselves.

Comments

Changed names
Username: BarryK
Oh, I had better spell it out... you can't just change the name of 'jwm2-2.0.1-9.pet' to 'jwm2-2.0.1-ted1.pet', you have to change the name of the directory when the package is expanded. Which is why it is probably best if WhoDo does it.

Check sum?
Username: PaulBx1
"I wonder if there is a way for you to log into ibiblio, run a little script that generates a file with all the checksums of the pets there, and then run the same script locally? Then you could just compare the two checksum files, to find what has been changed. Have no idea how much work this would be, or even if it is possible at all.

php script
Username: Raffy
"Well, the date can tell the difference, but if a script is essential, here is a page, call it ckmd5.php: <html> <head> <meta name="keywords" content="Package md5sum"> <meta name="Package md5sum"> <title>Package md5sum</title> <STYLE type=text/css> .title {font: 16px verdana, arial, sans-serif; } .maintext {font: 12px verdana, arial, sans-serif; } </STYLE> </head> <body class="maintext"> <span class="title">Package md5sum</span><br /><br /> <? $dontdisplay = array ("." , "..","index.php",".ftpquota","ckmd5.php"); ////////// Place here the files or directories not to be displayed ////// $i=0; if ($handle = opendir('.')) { while (false !== ($file = readdir($handle))) { if (!in_array($file,$dontdisplay)) { $selectedfiles[$i] = $file; $i++; } } } closedir($handle); sort ($selectedfiles); for ($j = 0; $j < $i; $j++) { echo $selectedfiles[$j]." - ".md5_file($selectedfiles[$j])."<br />"; } ?> </body> </html>

ckmd5.php
Username: Raffy
"Ah, place it in a package directory then call up the file in a browser. This assumes that PHP is supported by the server. It will read all files in the directory and get all the md5sums.

No version number
Username: BarryK
"Hmmm, looking on ibiblio, I see at least 5 packages that don't have any version number, for example 'Set-Time-Date.pet'. Developers, a fundamental principle of creating a package is that you assign it a version number.

Never mind
Username: BarryK
"Another thing for developers to take note of. Unlike some other distros, I don't ask for stringent rules for naming of pet packages. However, one thing I have requested, which the 'dir2pet' utility does, is name 'dev', 'doc' and 'nls' packages like this: abiword-1.2.3.pet abiword_DEV-1.2.3.pet abiword_DOC-1.2.3.pet abiword_NLS-1.2.3.pet The scripts in Unleashed and Woof need the '_DEV' to go immediately after the package-name. The '_' is required, some people have named their packages like 'abiword-DEV-1.2.3.pet'. I used to ask that a hyphen be used between package-name and version, which is standard practice. Woof doesn't need that, but it is consistent to stick with it. At least one package does not have a hyphen between name and version. Anyway, I'll fix it all. WhoDo has uploaded the puppy-unleashed-core-420.tar.gz that I am now downloading, plus all the 420 PET packages. There is only one thing that stops me from fixing all the package names, and putting corrections into packages.txt inside the unleashed tarball, and creating the 'devx' file, and that is I need to know what packages were changed without the pet pkg name being changed, as per my complaint at start of this thread. It is far to difficult for me to look inside each package to figure out which ones are the culprits. I need help on that.

md5sums
Username: big_bass
" BarryK you may remember a thread I posted about woof 2 asking for confirmation of md5sums for the same reason your have now puppy unleashed already does this for you so ask WhoDo do this file here is an example on my box /mnt/sda4/root/puppy-unleashed/0md5sums-pet-packages I know you wrote all the scripts but maybe you forgot about that file I wish you would include a md5sum in woof also for the same reason some of my hair fell out too :D big_bass

Ouch
Username: Pizzasgood
"I submitted some patches for 0rootfs_skeleton, syslinux, and petget. So if WhoDo forgot to rename the packages, that would mean: 0rootfs_skeleton-412, syslinux-3.63, and petget-411. I have an archive of all the packages prior to 4.20, so I just uploaded a list of checksums here: http://www.browserloadofcoolness.com/tmp-stuff/compressed_pets.md5 [b]WhoDo:[/b] You can save Barry some time by going into your directory of .pet files and running 'md5sum -c compressed_pets.md5' on that list, so that he doesn't have to download the entire thing with his slow connection.

TOTALLY off-topic
Username: Subito Piano
"After a long day, i thought maybe you would enjoy this -- from Toshiba's website. Don't know if you saw it--? I hope it comes pre-loaded with PUPPY, of course! http://explore.toshiba.com/petbook

Tags: puppy