Puppy 4.3 pre-beta bug reports

[Sit Heel Speak]

I just spotted a few things, but have no idea whether these things are huge or inconsequential.

I decided to build pps-422 locally, by first doing a woof_2009-07-17 (puppy) build, with the intent to then use the 417-to-422 patch.

But after running 1download, before running 2createpackages, I carefully compared the contents of packages-pet-4 against the pet_packages-4/ repository on ibiblio.

The following discrepancies caught my eye:

1download placed bdb-4.4.20.pet in packages-pet-4. But I see that the repository additionally carries bdb-4.7.25.pet and bdb-DEV-4.7.25.pet. Note that name should be bdb_DEV-4.7.25.pet, to maintain consistency with the commonest form. (but, see next message)

1download placed curl-7.17.1.pet in packages-pet-4. But the repository carries curl-7.19.4-pup4.pet and curl_DEV-7.19.4-pup4.pet.

1download placed ffmpeg-20071007-1.pet and ffmpeg_DEV-20071007-1.pet in packages-pet-4, and these are the newest-timestamped versions in the repository, but I'm curious why we are not using ffmpeg-20080731-i486.pet and ffmpeg_DEV-20080731-i486.pet.

1download placed freetype-2.3.5.pet in packages-pet-4, but the repository carries freetype-2.3.8.pet and freetype_DEV-2.3.8.pet in addition to an apparent mistake, freetype-DEV-2.3.8.pet. (but, see next message)

Geany is missing from packages-pet-4 but I see we have replaced it with medit. I was away when that happened. I know that the End key in Geany in 4.21 works wrong, it takes the insertion point to the end of the paragraph rather than the line, so am not surprised that Geany is gone.

1download placed lame-3.97.pet and lame_DEV-3.97.pet in packages-pet-4, but the repository carries lame-3.98.2.pet and lame-DEV-3.98.2.pet. Note inconsistency in use of hyphen and underscore before DEV in the DEV package's naming.

1download placed neither libdvdnav-0.1.10.pet nor libdvdnav_DEV-0.1.10.pet in packages-pet-4. Shouldn't they be included?

1download placed libexif-0.6.16.pet and libexif_DEV-0.6.16.pet in packages-pet-4, but the repository also carries libexif-0.6.17.pet and libexif-DEV-0.6.17.pet (Note inconsistency in use of hyphen and underscore before DEV in the DEV package's naming).

There are several "Prescott" versions of libs in the repository, I have no idea what the distinction is, which are not placed in packages-pet-4 by 1download, for example 1download placed libglade-2.6.2.pet in packages-pet-4 but not libglade-2.6.3-prescott.pet nor libglade_DEV-2.6.3-prescott.pet. There is no libglade_DEV-2.6.2.pet.

1download placed libgnomecups-0.2.2-pup4.pet and libgnomecups_DEV-0.2.2-pup4.pet in packages-pet-4, and these do have the latest (June 28) timestamp, but I am curious why we are not using libgnomecups-0.2.3-pup4.pet and libgnomecups_DEV-0.2.3-pup4.pet.

1download placed libpng-1.2.22-patched1-pup4.pet and libpng_DEV-1.2.22-patched1-pup4.pet in packages-pet-4, and these do have the latest (June 28) timestamp, but I am curious why we are not using the repository's libpng-1.2.34.pet and libpng-1.2.34-dev.pet (note error in naming libpng_DEV-1.2.34.pet).

1download placed libsigc++-2.1.1.pet in packages-pet-4, but not libsigc++_DEV-2.1.1.pet.

lxrad both regular and DEV is entirely missing from packages-pet-4, don't know if this is intentional or not.

tcl-8.5.6-v1.pet and tcl-8.5.6-v1-DEV.pet are entirely missing from packages-pet-4, don't know if this is intentional or not. Note mistake in naming the DEV.

tk-8.5.6.pet and tk-8.5.6-v1-DEV.pet are entirely missing from packages-pet-4, don't know if this is intentional or not. Note mistake in naming the DEV.

xorg_xorg_full_dri_DEV-7.3.pet is missing from packages-pet-4, I know that the regular distro uses xorg_base, but wouldn't it be prudent to build full into the devx? --and, same argument about xvidcore_DEV-1.1.3-i486.pet?

Respectfully,
SHS the Meticulous

[Sit Heel Speak]

I should also here note, that both gposil and yours truly have observed, in this thread, that Puppy Package Manager has a tendency to choke on PET package names that have an underscore in them. I have no idea how relevant this is to Woof, but, with reference to the above message, perhaps the -DEV naming convention is the preferable one.

[charlie6]

Hi,
[ ppa422 live-cd + saved session ] do not boot on PC with GRUB multiboot.
details:
have burned cd-rw multisession with ppa-422.iso
boot OK on first live-cd boot
have set keyboard, GMT, etc...
have saved "save to cd" at shutdown

I do not understand why the PC does boot.

I boots on another PC with only windowsxp installed.
I already had the case on earlier 417.
Does anyone has an axplanation.
Cheers
Charlie

[01micko]

OK,

Decided to test cups over a wireless network to a windows printer, a Canon MP 180..

Hooray, works no problem at all! (ppa-422)

Cheers

[DC]

Hi
Full install of Puppy 422
Tried modprobe nfs - result

# modprobe nfs
FATAL: Error inserting nfs (/lib/modules/2.6.29.6/kernel/fs/nfs/nfs.ko): Unknown symbol in module, or unknown parameter (see dmesg

There also appears to be some related modules missing. (exportfs etc)

DC

P.S. Could JWM please be upgraded to include window re-sizing from the top.

[gposil]

kernel mode nfs is not enabled in Puppy. You can use the User Space nfs server without problems though.

[zigbert]

- Pcd freezes X if no disc is inserted. Fixed in version 1.0
- Several fixes for Pbackup
- and fixes for Pfind

Links via my signature


Sigmund

[ttuuxxx]

well I finally got around to testing it, so far its been stable and no issues, I reported in the last release that that a misspelled menu icon for /menu/multimedia/Embeddedbookmarks multimedia files and also that the default image viewer is terrible, it expands images to like 512x512px by default, click on a 16x16 icon and see what a mess that is, I even provided a link to 32kb gpicview bin that HairyWill put together with a slide show and that all got ignored in this release. http://www.murga-linux.com/puppy/viewto ... 71&t=37870

Ok on another note in the past I've packaged up gtkhash and it was like 200kb pet because I had all the hash files included in the compile of mhash about 15 or so, when really for most part we only use 2, md5 and SHA1. SO I just compiled it with the 2 formats only and added rox menu file links, now you can click rightclick on any iso, tar.gz, pet, sfs and at the top of list is gtkhash, select that and it will open. push the hash button and you have your file hash. 2 clicks and thats it. I can't make it any easier for you guys, lol Oh by the way the pet is 30kb, with all that function how good is that

ttuuxxx

Oh ya freememory applet lost its anchor again, flew off when I installed a pet, The most stable freememory applet was series 2 the blue one, could be because it was gtk1.2 maybe? I tried the newer better looking ones compiled on 2.14X and they all flew off the taskbar, but the old stable blue one never let go. So That might be helpfull somehow.

[GrumpyWolfe]

Hi all
Not sure if this is a bug or not, but when I download a program.sfs and put in in the working dir of say puppy pre beta 4.3 which is puppy422 the the sfs in not found nor recognized by Puppy Boot Manger.
The only way to get it to load is to put it at the top dir of the sda1, which is the only hd in the laptop. Now because grub point to the dir of the puppy422 the ppa-422.sfs loads just fine. I have a total right now of 4 different version of puppy Linux on the system and only want it to load for a single version of puppylinux. I know that I can rename it to the 422 designation and then can get it to load on one version but someone trying to get into running puppy on a window system may not know what it wrong and why it did not load.
BTW BerryK I really like prebeta 4.3.

[ttuuxxx]

Hi guys I packaged up the Seamonkey theme I put together for 4.2, so now you can install it, I've had a lot of pm request for it so here it is, also after installing install Monkey Menu and you can have the searchbox box , printer and home button back like in 4.2
https://addons.mozilla.org/en-US/seamonkey/addon/3767
ttuuxxx

[edoc]

4.21 can't support the ath9k drivers and Fatdog 112 appears to be buggy and without active support - at least not on the main thread that I found.

Is the pre-final 4.3 reasonably stable?

Does it support ath9k?

Does it support dual-core?

Thanks!

BTW: I need to still use Fatdog 112 to be productive but I "broke" the Seamonkey install - lost the ability to click on a URL - no response, the GUI is a mess as well. Will your update work for a Fatdog 112 install? (I have lost track of what is in what Puplet any more - way too many out there and each changing constantly!)

[charlie6]

Hi,

Maybe this could not be relevant for ppa-422.

It seems that problem occurs on a Fuji Siemens PC: it does not occur on another Compaq with also GRUB multiboot installed.
I tried to boot that live-cd with saved session on an identical Fuji Siemens with only WindowsXP installed (bios set for cd boot): it does not boot on that live-cd.
Live-cd without saved session do boot on both PC's instead.

The following was also on an identical Fuji Siemens.

Hi,
[ ppa422 live-cd + saved session ] do not boot on PC with GRUB multiboot.
details:
have burned cd-rw multisession with ppa-422.iso
boot OK on first live-cd boot
have set keyboard, GMT, etc...
have saved "save to cd" at shutdown

I do not understand why the PC does boot.

I boots on another PC with only windowsxp installed.
I already had the case on earlier 417.
Does anyone has an axplanation.
Cheers
Charlie

EDIT:
maybe part of explanation here under par 1.d)
thanks to Barry and developpers crew !
http://puppylinux.org/wikka/LiveDVD

Cheers
Charlie

[ttuuxxx]

I went to compile mupdf on 4.22 and the compiler/devx didn't have the jam library which is like make but was needed, so I compiled it and here it is, maybe it could be added to the devx? its only 34kb
ttuuxxx
jam-2.5-i386|jam|2.5-i386|||88K|pet_packages-4|jam-2.5-i386.pet||compile tools|puppy|4|official|

[BarryK]

I should also here note, that both gposil and yours truly have observed, in this thread, that Puppy Package Manager has a tendency to choke on PET package names that have an underscore in them. I have no idea how relevant this is to Woof, but, with reference to the above message, perhaps the -DEV naming convention is the preferable one.

You are referring to the old package manager. The Woof-built puppies have a package manager that is a complete rewrite. From scratch.

So any comments, of whatever nature, about the package manager in 4.21 and earlier do not apply.

The '-DEV' is incorrect. These packages were created for 4.21 and I do not use them. It must be '_DEV'.

[edoc]

Is 4.3 going to be the first WOOF-built Puppy?

[ttuuxxx]

Is 4.3 going to be the first WOOF-built Puppy?

Hi edoc that would be a question for Barry, but I'll still give a point a view Really it would come down to how Barry builds it, The updated packages have been compiled manually and not taken from another another linux os repo, So if he wanted to he could build it using the older unleashed script way, or he could use the woof build scripts. I would say its a woof build but not really a true woof, lol
ttuuxxx

[edoc]

Perhaps the "true" WOOF Puppy versions will begin at 5.0?

[shinobar]

Hi Barry
don't you allow remastered main sfs file named 'ppa-422a.sfs' for example.
i mean the line 409 in init script:

Code: Select all

FND_PUPXXXSFS="`find /mnt/data -maxdepth 2 -xdev -type f -name ${DISTRO_FILE_PREFIX}-${DISTRO_VERSION}.sfs | grep -v ' ' | sed -e 's%^/mnt/data%%g' | tr '\n' ' '`"

[ttuuxxx]

Perhaps the "true" WOOF Puppy versions will begin at 5.0?

well initially I think that was his plan, That the first official woof will be 5.0, but then he got all retro like and revisited 2.18 and 4.3, which I don't think was his initial objective, but made a lot of sense anyways. I guess we'll wait for the 4.3 official release and read the release notes
ttuuxxx

[esmourguit]

Bonjour à tous,
There is a problem with Remasterpup2. When viewing this window below and when i click OK button, the program seems to loop, it returns the same window. It was the same on 417 version.
Cordialement