Puppy Linux Discussion Forum

[sc0ttman]

Further to the above,

Possible bug in petget/0setup:

I'm using a pretty bog standard Slacko 6.9.x build..

I'm trying to get Slacko to install wpa_supplicant 2.6, which has fixes against a big security problem in wifi (as far as I understand it)...

This wpa_supplicant 2.6 is in the Slackware patches repo.

The 0setup script, used in Woof and Petget, merges the latest pkgs from the "Slackware patches" into
the main *-official repo files, when updating/building Puppys repo files... (as I understand it)..

That's pretty cool, hat's off

However, while Petget successfully lists wpa_supplicant 2.6 in the repo after an update, it wrongly shows (ALREADY INSTALLED)..
Cos I actually only have 2.5 installed..

Even worse, trying to install any new pkgs added from the patches repo (and merged into "Packages-slackware14.2-official" in Petget) fails..
It says "missing libraries".. Even if I download them in the browser and ldd them (none missing)..

Anyone else have (or can anyone reproduce) the same problem?

(I'm well aware I don't understand Woof very well, so don't wanna just start logging spurious Github issues, so am asking here if I have this all correct...)


[As a side note, after updating the repos, my own pkg manager was able to download and install the wpa_supplicant 2.6, and the new bash
listed in patches without a problem (had to use the --force option to override existing pkgs]

-----------

A feature request

On a very related note, if there are new pkgs in the repos, I would love Puppy to print to the console (or terminal emulator) on first run of each boot
the names of all the new pkgs in the repos, just like Ubuntu does...

Especially if it's security fixes.. To that end it might NOT be better to merge the patches/fixes/security pkgs into the main repo files...

Ideally puppy would check for new pkgs at boot, and if new pkgs found, booting to X would be delayed i until after i had seen the msg and
chosen to install/ignore/etc.. and then X loads up.. (so, more like apt-get/ubuntu)

(this could actually be achieved with my pkg manager fairly easily, if puppy didn't merge the new pkgs into the main repo files and instead
kept the patches/fixes repos in their own files, like all the other repos..)

And wouldn't it be less code and hackery in woof to simply treat the patches (etc) repos like normal repos - with their own repo files...?

Again, I don't know enough about Woof to do this a 'proper' way (using Petget, root-fs skeleton, etc) ...

...Any thoughts?

[xpio]

Hi sc0ttman

If it's of any help to you, I am using stock slacko6.9.9.9 as found @ ibiblio, and have updated wpa_supplicant this morning.

I didn't use any of the command line tools, just Puppy Package Manager, and it too listed wpa_supplicant as "already installed", but I think it's normal behavior for PPM, and that it labels app by name, not by version, as such. (It displayed a warning that installed apps are not normally shown in the list, but updates are, with "already installed" label.)

While installing this, it downloaded heaps of other stuff, as qt-4.8.7 is a dependency of wpa_supplicant 2.6. In the end, installer reported that there are missing libraries, but these are from dependencies further down the chain. When checking, it seems that:

[Sailor Enceladus]

[sc0ttman]

[01micko]

[xpio]

[norgo]

@xpio

[sc0ttman]

Hi guys,

Well, the existence of wpa_gui clears up my large deps list query.. Not norgos though...

I forgot about the gui (as it wasn't installed), and hadn't checked the FIXUP hack, to be honest..

But even so, I still didn't get 2.6 installed using PPM.. not sure why...

If you did though xpio, (and considering the above info) then I'll assume it's my bad..

And I will look into how Petget handles FIXUP hacks (if at all), and think about some way to get something similar into Pkg..
(A list of blacklisted files, associated with their pkg, might be the simplest alternative? Something like:

~/.packages/blacklisted_files:

[norgo]

@sc0ttman

Hi Scotty,

Yes, PPM is a little bit strange sometimes.

Example:
search for smplayer gives me three hits
1. smplayer-17.8.0
2. smplayer-17.10.2
3. smplayer-17.4.2

see pic 1

three different versions from three different servers.
This means, PPM is showing what available is ( not the installed version )
These information come from ~/.packages/Packages-...14.2
That's why from time to time PPM database should become updated.

Btw. in my case smplayer-17.7.0 was installed.
If PPM is starting and a different version of the desired application is installed
a window pops up with the appropriate information.
That's absolutely okay.

see pic 2

But !!!
If a builtin package becomes deleted, PPM is showing nevertheless (ALREADY INSTALLED)
This is definitively wrong.
I have no idea from where PPM takes this information.

[norgo]

apropos wpa_supplicant 2.6

It is possible to compile wpa_supplicant without qt gui.
I did this three days ago under Slacko 6.9.9.9 ('testing;bdab886;2017-07-29 17:54:31 +0800')

following patches have been applied:

rebased-v2.6-0001-hostapd-Avoid-key-reinstallation-in-FT-handshake
rebased-v2.6-0002-Prevent-reinstallation-of-an-already-in-use-group-ke
rebased-v2.6-0003-Extend-protection-of-GTK-IGTK-reinstallation-of-WNM
rebased-v2.6-0004-Prevent-installation-of-an-all-zero-TK
rebased-v2.6-0005-Fix-PTK-rekeying-to-generate-a-new-ANonce
rebased-v2.6-0006-TDLS-Reject-TPK-TK-reconfiguration
rebased-v2.6-0007-WNM-Ignore-WNM-Sleep-Mode-Response-without-pending-r
rebased-v2.6-0008-FT-Do-not-allow-multiple-Reassociation-Response-fram

assoc-timeout
dbus-service-file-args
flush-debug-output
quiet-scan-results-message

I took the original Slackware build as template from here
( unneeded features have been commented out before compilation )

please note, this is only a test version !

wpa_supplicant-2.6-slk700-i686.pet ( size: 709 k , md5: 4ddaef8ce86dfedab36f14000630a8eb )

Brave tester are welcome

[peebee]

[norgo]

[radky]

If anyone is interested, the following iso is available for testing this weekend.

Dpup stretch-7.0.0a2-O4Nov2017.iso

Woof-CE build, testing branch 04-Nov-2017

Changelog since 20-Oct-2017:

- Add modified 'Places' category in JWM XDG menu, including common options such as clickable Drives, Recently used applications, Search files, and quick-links to common directories. The 'Recently used' option automatically deletes items from the list if they point to files that no longer exist on your drive. (thanks to MochiMoppel and zigbert for the original Places menu)
- Add/Fix help files for Abiword (online link), Cgtkcalc, Gnumeric, mtPaint, Sylpheed
- Add missing system libraries (thanks OscarTalks)
- Add inxi utility for concise system information (go to PupSysInfo -> Sys-Apps tab) or (go to PupControl -> System tab -> SysInfo Utilities)
- Add xclose utility to close multiple windows gracefully with wmctrl. Find it in the Utility menu, or you can add it to the tray or desktop as a quick-launch item to easily dismiss all desktop windows. (thanks MochiMoppel and mfb)
- Add emelfm2 two-pane file manager (thanks plinej)
- Add Engrampa archive manager to menu (thanks wdlkmpx)
- Add Deadbeef audio player 0.7.2
- Add Asunder CD ripper 2.8
- Add pequalizer (thanks 01micko)
- Add MMview file viewer (thanks MochiMoppel)
- Add Planer application for project management
- Add weX screen recorder and Precord audio player, modified for Dpup (thanks wiak)
- Add getflash (install FlashPlayer)
- Add duplex scrollbar steppers to Polished Blue GTK theme (thanks mfb)
- Add Polished-Blue JWM theme to complement the default GTK theme
- Add optional cursor themes (aero, lil-polar, Obsidian, PolarCursors, Premium, whiteglass, wonderland)
- Adjust urxvt default appearance. Note: urxvt is also configured with perl plugins which support multiple tabbed windows, plus convenient highlighting, copying and pasting (thanks belham2)
- Adjust D-Bus (system message bus); Remove old usr/lib/libdbus-1.so.3 -> libdbus-1.so.3.4.0, but retain offical debian /lib/libdbus-1.so.3 -> libdbus-1.so.3.14.13 (thanks OscarTalks)
- Adjust default Leafpad configuration to show line numbers
- Remove problematic %U suffix from executables in uget, hexchat and pcmanfm desktop files (thanks Sailor Enceladus)
- Update base kernel 4.1.38 to 4.1.45-i686-pae
- Update Ghostscript to 9.21 for CUPS printing
- Update Palemoon browser to 27.5.1
-Update gtkdialog to 0.8.4
- Update inkscapelite, patched to correctly show horizontal and vertical rulers (thanks OscarTalks)
- Update gpicview 0.2.5, patched to support animated GIFs
- Update ROX-Filer 2.11, patched to support moveable treeview columns in the detail view (thanks Rocket) and add 'Force' checkbox to the ROX-Filer copy/move dialogs (thanks jun7). Please see note below.
- Update peasy apps and add peasyDiff (thanks rcrsn51)
- Update default wallpapers
- Update PupMates
- Security: update wpa_supplicant (wpasupplicant_2.4-1+deb9u1_i386.deb). This addresses the KRACK WiFi vulnerability in the WPA2 protocol: https://www.debian.org/security/2017/dsa-3999
- Security: update openssl (openssl_1.1.0g-1_i386.deb). This addresses the OpenSSL Security Advisory of 02 Nov 2017: https://www.openssl.org/news/secadv/20171102.txt
- Bugfix: prevent X-server crash when launching xcalc calcuator (thanks goingnuts)

Note: The default action of the updated ROX-Filer copy/move dialog (Quiet checkbox ticked, Newer checkbox unticked and Force checkbox unticked) requires user confirmation before overwriting existing destination files. However, this behavior may be tedious for some users when copying or moving multiple files. In this scenario, the Force option (if also ticked) enables immediate overwriting of destination files without serial confirmation dialogs. Importantly, the Force checkbox defaults to the unticked state each time the copy/move dialog is called, and must be manually ticked if you wish to copy/move multiple files without confirmation.

If the 'Newer' checkbox is ticked (and Force unticked), ROX-Filer will only overwrite if source is newer than destination. User confirmation is still required if source is older than destination or if source and destination dates are identical. However, the Force option (if also ticked) will override the Newer option and forcefully overwrite destination files without regard for the file date. Consequently, the Force option should be used with an understanding of its purpose and power.

In the Options Configuration GUI of ROX-Filer there is another 'Force' checkbox which applies to the confirmation dialog you may see when deleting non-writeable items. This option does not control the Force option of the copy/move dialog.

Thanks

Edit: iso removed

[belham2]

[peebee]