Porteus

good to know , i'll mark this as solved..

hmm, maybe there's more needed.. i suggest getting the full slackware firmware package: getpkg kernel-firmware if you extract it(an archive manager will do) you'll see some folders in the ar3k directory, in particular: 3101 and 3101coex maybe they have some function too... or just go the whole way a...

ah, ok i see now, ..so where did you get the .dfu from? it's part of the kernel-firmware package in slackware: in /lib/firmware/ar3k/ , so that's where it should be placed, either in 000-kernel.xzm or in it's own module: (as root) mkdir /tmp/patch/lib/firmware/ar3k/ cp AthrBT_0x31010000.dfu /tmp/pat...

same place it's always been... ?/boot/docs

welcome :) , I have installed bluez, bluez-firmware and blueman with getpkg. you're using Porteus v5 rc2 KDE, right? bluez is already in core, and kde has it's own client: bluedevil, so i don't think adding blueman will help.. bluez-firmware couldn't hurt i suppose.. i don't know why the plugin erro...

Rava wrote: ↑

23 Nov 2020, 12:38

brilliant idea! Adding a parameter that makes the script only tell the user the download URL - without downloading.

that's not what i wrote...

new version uploaded: now it just makes a module from the extracted .deb, without making a slackware package first, so your issues with running out of space should be dealt with. also found a better source for the version info, that shouldn't get blocked. Can your script be hacked so that it only do...

Rava wrote: ↑

23 Nov 2020, 11:20

I thought I explained above: I manually downloaded all named dependencies,

yes, but where from? for what version of slackware were these package built?

So what can l do getting my module? :cry: And how to prevent update-browser from deleting the downloaded file, google-chrome-stable_current_amd64.deb in this case? if you go to <whereever-the-heck-google-keeps-it> grab it directly, put it in the folder you're using as a work directory and the scrip...

I tried manually more information please :) like for instance, if it's a package, from where does it come? note 3.1 series uses slackware 14.1 packages and using newer packages would lead to the above issues.. afaiui, slackonly didn't start packaging sbo till 14.2 .. so the best option would be to ...

Why trying to create google-chrome-87.0.4280.66-x86_64-en-GB-1.xzm from a path where the files sit in /tmp/txz2xzm19934/ instead e.g. /Porteus_modules/5.0/chrome/update/tmp/txz2xzm19934 ? because that's where txz2xzm does it's thing.. as it always has.. basicly makes the working directory option us...

infania wrote: ↑

20 Nov 2020, 13:58

Hey we run a mirror in Sweden

thanks , much appreciated
now included on our http://porteus.org/porteus-mirrors.html and http://porteus.org/porteus-mirrors.txt

Rava wrote: ↑

20 Nov 2020, 19:33

WTF gøøgle-chrøme? No German aka de locale?

apparently not , when the script was written .. there is now: de, en-GB, and fa(farsi) ... fixed on our server, mirrors will update some time later...
thanks for reporting

Or does the txz2xzm script support converting multiple txz files into one xzm file at once, such as in: not quite, i don't think: /usr/bin/txz2xzm package.txz /usr/bin/txz2xzm package1.txz package2.txz package3.txz /usr/bin/txz2xzm /folder/with_packages/* i presume the output is package1.xzm packag...

Could you then please change the help text for chrome and chromium that it no longer states --target dir Extract directly to a target directory (absolute or relative)? That would be great. no, because when you run update-chrome/chromiun- live --help directly, like you did, you get the makeself help...