Porteus Package Manager bug reports

[brokenman]

This thread will now be used to report PPM bugs and changelog. The original development thread has been closed. Thank you to everyone that contributed with ideas and suggestions. When reporting a bug please run the Bug Report feature of PPM and upload the log to http://www.pastebin.com for analysis and post a link here quoting your reference number supplied by the Bug report feature.

################

Thu Jan 12 16:15:10 UTC 2012
Added salix repo support
Added update Fido to main update menu
Added update Debian to main update menu
Added update Salix to main update menu
Added .gz support to LIBS.TXT and PACKAGES.TXT on Porteus server
Added edit config file for debian.conf
Added edit config file for salix.conf
Added edit config file for fidoslax.conf
Added 'release date' to About PPM page so you know you have updated.

Thu Jan 12 00:22:11 UTC 2012
Added debian repository functionality
Fixed fatal bug in 'unresolved libs' report that prevented report from showing.
Added 'update slackware database' function to update menu
Removed erroneous entry from /etc/slacky.conf
Fixed rootcopy function that failed to find porteus directory

The current version of PPM that shipped with Porteus-v1.1 has a small problem. When you update, the new version will be downloaded and placed into your chosen storage. If your 'storage' folder is not /porteus/modules then you will need to move the download file ppm-Porteus-v1.1-$ARCH-1.xzm into your modules folder and reboot.

The updated PPM addresses this problem and future updates will automatically be placed into your base folder.

[Rava]

If your 'storage' folder is not /porteus/modules then you will need to move the download file ppm-Porteus-v1.1-$ARCH-1.xzm into your modules folder and reboot.

You not meant /porteus/modules literally, or did you?

I presume you meant something like /mnt/sdXX/porteus/modules ... or am I wrong?

[Ahau]

@Rava, you're correct ... whenever we refer to /porteus/modules, we mean that in reference to the folder location inside the root of a real storage medium (not inside the live filesystem). /porteus/ does not exist at the root of the live filesystem and if you created it and placed a module there, the module would either disappear (if you're in always fresh mode) or fail to load automatically (if you have saved changes) on the next startup.

[Rava]

That's what I thought, and that is the only thing to make sense. I still wanted to be sure, and maybe my question even helps someone who lurks only in here and not asks such questions.

[Hamza]

This command should fix all problems with mistakes on root filesystem and the /porteus directory at root of filesystem.

Code: Select all

ln -sf /porteus /mnt/sdXX/porteus

Replace the sdXX by your porteus device ident.

[francois]

I am just begining using the most recent version under 1.2 rc1. It looks powerfull. PPM looks very good. We are talking about the major league.

Great job brokenman.

[brokenman]

Thanks Francois. Some bugs have been fixed in the 1.2rc1 release so the next release should be a little more stable but overall i am happy with the functionality. The code needs streamlining but i am too scared to start that right now as it induces insomnia, nausea, difficulty passing urine and occasional loss of vision.

[francois]

In this case, use mindfulness or stick to present moment. Do it non judgementally, one mindfully and effectively.

Breathe deeply. And think about fanthom with his broken arm.

[pumbaa2]

The main Repo for QT-4.7.0 doesn't download correctly because it attempts to get the txz file (which doesn't exist) instead of the xzm. The program complains that the file failed but attempts to activate the module anyway which results in another error... I went directly to the HTTP link for the repo and grabbed the module manually and inserted it, but I just wanted to point that out. Porteus Version 1.1 (32 bit) with the update installed.

[brokenman]

Thanks Pumbaa2 i will check it out.

[brokenman]

Bug fixed. Please update module database to fix this.

[francois]

I appreciate very much PPM.

However:

1) there is a big slowdown of the computer while PPM is converting a package into a xzm module. Is there something to do about that?

2) trying to download sane, that comes with many dependencies I get the download for qt-4.7.0_7abde40-i486-3.xzm failed. Is there something to do about it?

Thanks.

[fanthom]

qt module issue appeared when i was updating 32bit repo last week.
this was the first time when i was playing with 32bit repo and seems that one of my conversion scripts failed for this particular package (no idea why).

should be fixed in next 6hrs.

[brokenman]

Thanks for helping out Fanthom.

1) there is a big slowdown of the computer while PPM is converting a package into a xzm module. Is there something to do about that?

Unfortunately no. The bigger the package the more time it will take to convert. Do you think it is taking an unusual amount of time?

You can test by converting manually an prepending time to your commands.

Code: Select all

time installpkg -root /tmp/fakeroot package.txz && time dir2xzm /tmp/fakeroot /tmp/module.xzm

The qt-4 module has been replaced from backup and an anomoly removed from PACKAGES.TXT. After fixing a couple of other minor bugs i will push an update to PPM.

[stalane]

On 1.2 64bit with KDE4 I have noticed a pretty large CPU overhead from ktsuss while running the package manager. On a dual core machine it was between 7% and 8% which while manageable generates a lot of heat. Will look into it further tomorrow but thought I would just raise a flag here to see if anyone has already looked at it?