Download | Devuan.org | Git | Bugs | Packages

The officially official Devuan Forum!

You are not logged in.

Pages: 1 2 3

#1 Re: Installation » Add repositoy to daedalus? » 2023-04-26 11:39:45

brday
alexkemp wrote:

@brday:
If your code was copied from the terminal then you likely have a reason (speling), otherwise non-free & contrib are not available for deadalus, though they may be for daedalus.

I said that the repository this does work although it is insufficient:

http://deb.devuan.org/merged daedalus          main

But the non-free repository does not work, let's be clear.

deb http://deb.devuan.org/merged daedalus-security main contrib non-free

#2 Installation » Add repositoy to daedalus? » 2023-04-26 08:43:32

brday
Replies: 9

Good morning

To add the non-free repository in the daedalus test system, how do I proceed?

Edit:
In this way I tried to add, but it gave me error:

En /sources.list

deb http://deb.devuan.org/merged daedalus main non-free contrib non-free-firmware

Typographical correction in the manual copy of the terminal output.

# apt-get update 

E: The <<http://deb.devuan.org/merged daedalus Release>> file does not have a Publication file.

N:  It cannot be updated from such a repository in a secure way and is therefore disabled by default.

#

Now the default repositories are commented out like this:

# deb http://deb.devuan.org/merged daedalus-security main contrib non-free
# deb-src http://deb.devuan.org/merged daedalus-security main contrib non-free

The only repositories that work on the daedalus  test system are these, but it is insufficient!

deb http://deb.devuan.org/merged daedalus main
deb-src http://deb.devuan.org/merged daedalus main

#3 Re: Devuan Derivatives » JWM KIT love fest » 2023-04-25 18:28:33

brday
golinux wrote:

@brday . . . I don't understand your question. AFAIK weekly builds of the daedalus (testing) installer-iso are updated every Monday and available for download on our mirrors.

My question was about the repositories, latest or quarterly. In the system installation or already installed system, is there any way to modify the file containing the repositories, changing the quarterly repositories for latest repositories?

#4 Re: Devuan Derivatives » JWM KIT love fest » 2023-04-25 18:09:47

brday
golinux wrote:

The Devuan release following Chimaera. Have a look at:

https://www.devuan.org/os/releases

Is there a way to put with the latest repositories and not the quarterly ones? If so, how should I proceed?

Greetings

#5 Re: Devuan Derivatives » JWM KIT love fest » 2023-04-25 17:06:41

brday
JWM-Kit wrote:

I've done a little bit of testing with JWMKit in Daedalus.

What is Daedalus?

#6 Re: Devuan Derivatives » JWM KIT love fest » 2023-04-18 17:52:31

brday
JWM-Kit wrote:

I've never seen this before.  Does restarting jwm or signing out and back in seems to fix it?

Yes, I did all that, including resetting to factory default as indicated by the jwmkit_first_run command at the bottom of the JWM Kit menu, haha I have left it back to the 12 hour format and not 24 hours.

artix?

Yes, artix, the arch without systemd is called artix, artix takes the INIT in OpenRC,   artix also say that it is phenomenal. smile

#7 Re: Devuan Derivatives » List of Devuan derivatives » 2023-04-18 14:08:04

brday

And why haven't they included DevuanDog in that list of derivative systems? DevuanDog was a nice project, unfortunately it was discontinued.

#8 Re: Devuan Derivatives » JWM KIT love fest » 2023-04-18 13:51:31

brday

Hello JWM-Kit, very good what you say, I have been observing, when I change the time format to 24 hours, it is delaying the time, or the time remains paralyzed, of course through jwmkit_trays. On the other hand, for those who use the doas or sudo dependency for superuser, in this case as I am testing Hyperbola with doas, I have put in the JWM Kit configuration with the command jwmkit_first_run , in the JWM Kit Logout tab ==>> doas (no password), and for the JWM Kit Time tab==>>Do not ask permission, before that you must have configured the file /ect/doas.conf and uncomment ==>>> permit nopass :whell

In this way it made effect on the output graphic part on the buttons for reboot, shutdown.

Usually a Devuan or Debian based system.

Tell us how JWM Kit work on those systems you commonly use? The JWM Kit package is in the devuan, debian, ubuntu, artix, freebsd repositories? Is it the same process of installing the tarball package with the command I posted at the beginning of the conversation and it didn't work? I want to try it also on those systems mentioned.  smile

#9 Re: Devuan Derivatives » JWM KIT love fest » 2023-04-17 21:36:46

brday
JWM-Kit wrote:

     ......but I don’t use Hyperbola enough to be familiar with it’s software selection.

What system do you use with JWM Kit?  Very good your answers. By the way, from the graphical window of JWM Kit, in Logout user to exit or shutdown the system, why it does not take effect when you click Shutdown or Reboot?  It only takes effect in the Logout tab, which exits the window to the terminal.

To shutdown or reboot the system, I need to type commands in the terminal like doas halt or doas poweroff or doas reboot. big_smile

#10 Re: Devuan Derivatives » JWM KIT love fest » 2023-04-16 23:25:58

brday
JWM-Kit wrote:

I'm glad your'e making progress.

Place your themes in $HOME/.config/jwm/themes/

If you have the all_themes.zip just unzip it to that directory.  You can now start jwmkit_appearance and choose a theme.  Or edit a theme and save the changes as a new theme.  Or create your own.

Hi my friend JWM-Kit, I am happy with the installed repository JWM kit, although you said it is old. I have read enough of the wiky, I have put the themes in that directory you told me, however, the effect it does is to change the borders of the windows and nothing else.

On another note, the JWM themes and other JWM customization will not affect the internal parts of the windows.  The inner parts of the window are not handled by jwm, but by GTK, or Qt, etc.  If you need the to customize the inner part of the windows you must set the GTK theme.   You can learn to do this manually or use a simple theme switcher.  I recommend lxappearance as it is in the Hyperbola repository.  You will also need to install some GTK themes.

Regarding lxappearance, yes, I have had to install theme-styles and also theme-icons, that's where the system kicked in, being able to choose the style-theme  and the icon-hteme to taste and not fuck my eyes haha, of course dark theme with the help of lxappearance.

Also you can run the first run tool again if you need to configure permissions.  These are used by jwmkit_time and jwmkit_logout.  If you do not use these apps or they defaults work for you then no need to mess with it.

Regarding the JWM Kit configuration, with the command jwmkit_first_run, I set it to default, and in JWM Kit Logout permissions, I set it to elogind (loginctl), and JWM Kit time, I set it to sudo | Built in Prompt.

Will it be ok?

Because the window manager does not display the 24 hours? I have tried to change from the application menu (jwm kits configuration) it configures it but it does not change the time, for example 14 50, it displays 2:50, so, I do not know where I am doing wrong.

Another thing, how to add application launcher in the jwm taskbar? For example, I would like to add on the left side the battery icon, the audio volume icon, the network icon, on the right side, I would like to add, the iceweacel browser icon, the sakura terminal icon, the user folder icon.
What version of Hyperbola are you using?  Because in Hyperbola 0.4.2 many things have changed, you can no longer add the ARCH repository at the start of the system installation, I would like some application to display system information as neofetch or screenhoster did but no longer exists, and so other packages of external device automounting as gvfs or networkmanager that does not exist.   

Greetings

#11 Re: Devuan Derivatives » JWM KIT love fest » 2023-04-11 21:47:57

brday
JWM-Kit wrote:

brday

It seems I may of jumped ahead a step.  I didn't realize you had not even installed JWMKit yet. Although keep in mine that running  the First Run tool is a required step when we get there.  I am assuming you already have a working jwm system with xenocara and jwm installed? If not than you need more than just help with jwmkit.

I await for input from @zapper here for verification, but I believe Hyperbola 4.2 is still part of the "Milky Way" branch and is still Linux (arch) based.  It should continue to operate as the other Milky Way 4.x releases.  Which means JWMKit is in the repository and you can also use the build scripts provided at my sourceforge site.  @zapper, please confirm.

You should be able to install jwmkit from the package manager with this simple command. This is not the most current version, but it will work.

pacman -Syu jwmkit

EDIT : The command above requires you to be root, or use doas/sudo/etc.

Once you have installed it you can run the jwmkit_first_run and select the default configuration and configure app permissions.

If you want the most current version visit this sourceforge page for the build script and instructions.  As mentioned in my previous post.

How good looks the customization and configuration of  JWM Kit,I apologize for saying that the repository of JWM Kit was not in Hiperbola is version 0.4.2, the truth I have been blushing. I do not know how I have done before trying o install JWM Kit but did not give result, now JWM Kit has me happy, I copied and pasted the package installation command without reading the part below that has been to make as superuser, and was installed very well and then I did the steps to save by default.

I'm trying to configure the effects to make the directories and folders look dark, so my eyes don't get screwed up. I don't know how to do it from the configuration, but from the brief look of the JWM Kit appearance  I only see dark color for the window borders.

Your JWM Kit package looks great, one question, is it possible to do some additional configuration outside the JWM Kit package like putting a dark theme or adding some command or comment in the original jwm file?

Ah I was forgetting, not installed the package of the JWM Kit themes, how would be to proceed or commands to execute?  Greetings.

#12 Re: Devuan Derivatives » JWM KIT love fest » 2023-04-11 16:03:53

brday
JWM-Kit wrote:

@brday

I know the question was target at zapper, but allow me to answer as  I am the author of JWMKit.

Once you've installed JWMKit you need to run jwmkit_first_run.  This will allow you to create a default configuration and also configure how the logout and time tool request permission.  I recommend using the "Default" option for the JWM config and then you can use the various apps to customize it as needed.

JWMKit Wiki - First Run

You can get the newest package/build scripts here. For Hyperbola look under the BUILD directory for Hyperbola.  The readme provides build Instructions (to create a package to be installed) or just scroll down and they are underneath the downloads.

Best of luck!

EDIT : JWMKit is provided in the Hyperbola repository.  I only pointed out my sourceforge page in case you were interested in the newest version.

Hello JWM-kit

I don't know what I am doing wrong, please correct me, there are two packages, one is JWM_Kit-20220826.tar.gz    and the other  all_themes.zip.   This is the way I have proceeded.

[user@localhost~$ cd Downloads

[user@localhost Downloads]$ ls
all_themes.zip  jwm_kit  JWM_Kit-20220826.tar.gz  JWM_Kit-20220826.zip

[user@localhost Downloads]$ cd jwm_kit

[user@localhost jwm_kit]$ ls
BASH  BUILD  doc  freedesktop  icons  man1  PYTHON  README.md

[user@localhost jwm_kit]$ doas pacman -S binutils make gcc pkg-config fakeroot

doas (user@localhost) password: 
warning: binutils-2.34-2 is up to date -- reinstalling
warning: make-4.3-3 is up to date -- reinstalling
warning: gcc-8.4.0-5 is up to date -- reinstalling
warning: pkg-config-0.29.2-2 is up to date -- reinstalling
warning: fakeroot-1.24-5 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (5) binutils-2.34-2  fakeroot-1.24-5  gcc-8.4.0-5  make-4.3-3
             pkg-config-0.29.2-2

Total Installed Size:  868.37 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n] 
(5/5) checking keys in keyring                     [######################] 100%
(5/5) checking package integrity                   [######################] 100%
(5/5) loading package files                        [######################] 100%
(5/5) checking for file conflicts                  [######################] 100%
(5/5) checking available disk space                [######################] 100%
warning: could not get file information for usr/share/locale/bg/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/bg/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/bg/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/ca/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/da/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/da/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/da/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/da/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/da/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/de/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/de/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/de/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/eo/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/es/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/es/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/es/LC_MESSAGES/gas.mo
warning: could not get file information for usr/share/locale/es/LC_MESSAGES/gold.mo
warning: could not get file information for usr/share/locale/es/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/es/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/es/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/fi/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/fi/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/fi/LC_MESSAGES/gas.mo
warning: could not get file information for usr/share/locale/fi/LC_MESSAGES/gold.mo
warning: could not get file information for usr/share/locale/fi/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/fi/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/fi/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/fr/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/fr/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/fr/LC_MESSAGES/gas.mo
warning: could not get file information for usr/share/locale/fr/LC_MESSAGES/gold.mo
warning: could not get file information for usr/share/locale/fr/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/fr/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/fr/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/ga/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/ga/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/ga/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/hr/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/hr/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/hu/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/id/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/id/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/id/LC_MESSAGES/gas.mo
warning: could not get file information for usr/share/locale/id/LC_MESSAGES/gold.mo
warning: could not get file information for usr/share/locale/id/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/id/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/id/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/it/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/it/LC_MESSAGES/gold.mo
warning: could not get file information for usr/share/locale/it/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/it/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/it/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/ja/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/ja/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/ja/LC_MESSAGES/gas.mo
warning: could not get file information for usr/share/locale/ja/LC_MESSAGES/gold.mo
warning: could not get file information for usr/share/locale/ja/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/ja/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/ms/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/nl/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/nl/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/pt/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/pt/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/pt_BR/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/pt_BR/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/pt_BR/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/ro/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/ro/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/ro/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/ro/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/ru/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/ru/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/ru/LC_MESSAGES/gas.mo
warning: could not get file information for usr/share/locale/ru/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/ru/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/rw/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/rw/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/rw/LC_MESSAGES/gas.mo
warning: could not get file information for usr/share/locale/rw/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/sk/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/sr/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/sr/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/sr/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/sr/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/sr/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/sv/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/sv/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/sv/LC_MESSAGES/gas.mo
warning: could not get file information for usr/share/locale/sv/LC_MESSAGES/gold.mo
warning: could not get file information for usr/share/locale/sv/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/sv/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/sv/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/tr/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/tr/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/tr/LC_MESSAGES/gas.mo
warning: could not get file information for usr/share/locale/tr/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/tr/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/tr/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/uk/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/uk/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/uk/LC_MESSAGES/gas.mo
warning: could not get file information for usr/share/locale/uk/LC_MESSAGES/gold.mo
warning: could not get file information for usr/share/locale/uk/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/uk/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/uk/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/vi/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/vi/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/vi/LC_MESSAGES/gold.mo
warning: could not get file information for usr/share/locale/vi/LC_MESSAGES/gprof.mo
warning: could not get file information for usr/share/locale/vi/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/vi/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/zh_CN/LC_MESSAGES/bfd.mo
warning: could not get file information for usr/share/locale/zh_CN/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/zh_CN/LC_MESSAGES/gas.mo
warning: could not get file information for usr/share/locale/zh_CN/LC_MESSAGES/gold.mo
warning: could not get file information for usr/share/locale/zh_CN/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/zh_CN/LC_MESSAGES/opcodes.mo
warning: could not get file information for usr/share/locale/zh_TW/LC_MESSAGES/binutils.mo
warning: could not get file information for usr/share/locale/zh_TW/LC_MESSAGES/ld.mo
warning: could not get file information for usr/share/locale/be/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/bg/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/cs/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/da/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/de/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/es/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/fi/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/fr/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/ga/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/gl/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/he/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/hr/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/id/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/it/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/ja/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/ko/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/lt/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/nl/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/pl/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/pt/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/pt_BR/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/ru/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/sr/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/sv/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/tr/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/uk/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/vi/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/zh_CN/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/zh_TW/LC_MESSAGES/make.mo
warning: could not get file information for usr/share/locale/be/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/be/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/ca/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/da/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/da/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/de/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/de/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/el/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/el/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/eo/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/es/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/es/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/fi/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/fi/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/fr/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/fr/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/hr/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/id/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/id/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/ja/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/ja/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/nl/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/nl/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/pt_BR/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/ru/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/ru/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/sr/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/sr/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/sv/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/sv/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/tr/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/tr/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/uk/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/uk/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/vi/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/vi/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/zh_CN/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/zh_CN/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/locale/zh_TW/LC_MESSAGES/cpplib.mo
warning: could not get file information for usr/share/locale/zh_TW/LC_MESSAGES/gcc.mo
warning: could not get file information for usr/share/man/de/
warning: could not get file information for usr/share/man/de/man1/
warning: could not get file information for usr/share/man/de/man1/faked.1.gz
warning: could not get file information for usr/share/man/de/man1/fakeroot.1.gz
warning: could not get file information for usr/share/man/es/man1/faked.1.gz
warning: could not get file information for usr/share/man/es/man1/fakeroot.1.gz
warning: could not get file information for usr/share/man/fr/
warning: could not get file information for usr/share/man/fr/man1/
warning: could not get file information for usr/share/man/fr/man1/faked.1.gz
warning: could not get file information for usr/share/man/fr/man1/fakeroot.1.gz
warning: could not get file information for usr/share/man/nl/
warning: could not get file information for usr/share/man/nl/man1/
warning: could not get file information for usr/share/man/nl/man1/faked.1.gz
warning: could not get file information for usr/share/man/nl/man1/fakeroot.1.gz
warning: could not get file information for usr/share/man/pt/
warning: could not get file information for usr/share/man/pt/man1/
warning: could not get file information for usr/share/man/pt/man1/faked.1.gz
warning: could not get file information for usr/share/man/pt/man1/fakeroot.1.gz
warning: could not get file information for usr/share/man/sv/
warning: could not get file information for usr/share/man/sv/man1/
warning: could not get file information for usr/share/man/sv/man1/faked.1.gz
warning: could not get file information for usr/share/man/sv/man1/fakeroot.1.gz
:: Processing package changes...
(1/5) reinstalling binutils                        [######################] 100%
(2/5) reinstalling make                            [######################] 100%
(3/5) reinstalling gcc                             [######################] 100%
(4/5) reinstalling pkg-config                      [######################] 100%
(5/5) reinstalling fakeroot                        [######################] 100%
:: Running post-transaction hooks...
(1/1) Updating the info directory file...
[user@localhost jwm_kit]$ 
[user@localhost jwm_kit]$

This command jwmkit_first_run does not execute neither as user nor as superuser, I don't know how you do it, here I put the output of this command:

[user@localhost jwm_kit]$ jwmkit_first_run
bash: jwmkit_first_run: command not found
[user@localhost jwm_kit]$
[user@localhost jwm_kit]$ 

[user@localhost jwm_kit]$ doas jwmkit_first_run
doas (user@localhost) password: 
doas: jwmkit_first_run: command not found
[user@localhost jwm_kit]$ 
[user@localhost jwm_kit]$

The JWMKit repository is not on the Hyperbola 64-bit system version 0.4.2.  As I have followed previous guides for installation, many things have changed in Hyperbola that is changing from the same basis to BSD, which is no longer present repositories for ARCH and D-Bus packages as many related to the automount of external devices or applications essential  for day to day use, call whatsapp, telegram, others as network manager.

#13 Re: Hardware & System Configuration » Devuan does not detect Huawei smartphone hardware! » 2023-04-09 23:57:04

brday
tylerdurden wrote:

The image you posted is no longer available but from what I've gathered you're using XFCE, right?
I'm assuming you want to access not just the phone's SD card but also its internal storage, correct?

As dice said, make sure you have these installed:

gvfs-fuse
gvfs-backends

And make sure you're connecting your phone in "data transfer" mode or something along those lines.

Do repost the screenshot.

Hi tylerdurden, I'm sorry, sometimes I use in desktop environment like xfce or lxde, sometimes in window manager, and it's complicated when by default it doesn't detect external devices, I don't know what other packages there may be apart from these gvfs-fuse and gvfs-backends for it to detect automatically, in hyperbola linux, those packages are discarded.

#14 Re: Devuan Derivatives » JWM KIT love fest » 2023-04-09 23:42:34

brday
zapper wrote:
brday wrote:
zapper wrote:

As I have said before, I myself prefer JWM.

The JWM  for 64 bits ? Can you post here a screenshot that displays in the terminal data and consumption of the machine with the command neofetch ? It would be nice if you could leave the link of  jwm kit to test with devuan.

I could post a screenshot, but I would have to reboot to get a good idea of how much is actually consumed.  then go into a terminal and type in free -m

I am using 64 bit, so no worries there.

https://codeberg.org/jwmkit

I recommend checking the consumption for yourself though, RAM is used more on machines with more RAM.

So what I mean I guess is, I have 16GB RAM on this laptop. Well on my comp with 8GB it uses less of the RAM.

Andyprough can correct me if he wants, but I think he said it used like somewhere from 60-70 megabytes to use it, even with jwmkit.

Or maybe jwmkit said that? anywho, it uses less the dwm according to Andyprough for sure. I recall he said that on a forum. wink

On boot though, it uses less than 70mb for me though for my 16GB T430 with coreboot + me cleaner.

I can reboot to check if you are interested. I will do so now...

Interesting... It seems on one of my laptops its like 110mb total usage including jwm being used. That one has Hyperbola though, 16gb or not. I will try my devuan one and see what that shows.

Here is a picture of it, https://upload.disroot.org/r/KhKbZ0Vd#3 … I4v3+DbPs=

just download it to see it.

Btw, I looked and Hyperbola uses 89mb without any wm/DE.

so that means... 21mb for jwm? insane... it has 16gb of ram so I didn't expect this lol.

I will check devuan now.

Fascinating... it uses 141mb on Devuan ceres...
https://upload.disroot.org/r/t6xNspMs#U … 2o+y6X8Ic=

Without a wm it uses close to that number.  Anywho, those links seem to indicate to me, that JWM is ultra lightweight. Anywho, that's all folks! smile

Except I should mention I am using 5.15.xx linux-libre kernel on the devuan laptop and 5.10.xx on the hyperbola one.

wink  just a heads up! smile

Hello zapper

I have tried to install your JWM Kit Linux package but it did not transform the window manager appearance, I don't know how you do it, I like JWM, but I don't know how to configure and customized it in Hyperbola Linux, can you tell me where I am failing?  I installed it with this command:

$ doas pacman -S binutils make gcc pkg-config fakeroot

#15 Re: Devuan Derivatives » JWM KIT love fest » 2023-02-11 14:19:25

brday
andyprough wrote:

Hey zap, check out my setup today - Hyperbola (testing) with jwm, jwm kit, and I got the latest abrowser from Trisquel running.

I'll look for your email - I think they've been getting sent to the spam folder for some reason. I'll email you my phone number so you can text me.

https://trisquel.info/files/HyperbolaJwmKit5.jpg

Unbelievable, the consumption of the machine with JWM is very low, how can you achieve all that? There is no clear guide showing how to configure and customize the system with the jwm window manager.

#16 Re: Off-topic » Show your desktop (rebooted) » 2021-11-26 00:54:10

brday
andyprough wrote:
hevidevi wrote:

andy, you cant really compare the progress of Devuan to hyperbola. I do understand where you are coming from and respect that hyperbola have talented people coding there, but im just pessimistic in regards to forking openbsd to hyperbola.

I don't know, I'm just a hack Devuan user that's doing some distro-hopping for fun. They are sending new packages to their repo at a pretty quick pace right now. They are not just a random tiny group of developers - they are an FSF approved fully libre distro, and a subproject under Arch. They probably have access to some money and resources and a dedicated dev and user base. 
https://trisquel.info/files/hyperbola-lumina-green.jpg

Is it the Iceweasel browser ?

#17 Re: Devuan Derivatives » [MiyoLinux] New Releases Uploaded » 2021-11-07 07:37:22

brday
golinux wrote:

We're all waiting for fsmithred's HOWTO.  wink

Was it published the HOWTO ?

#18 Re: Devuan Derivatives » JWM KIT love fest » 2021-11-07 07:29:47

brday
zapper wrote:

As I have said before, I myself prefer JWM.

The JWM  for 64 bits ? Can you post here a screenshot that displays in the terminal data and consumption of the machine with the command neofetch ? It would be nice if you could leave the link of  jwm kit to test with devuan.

#19 Re: Off-topic » Show your desktop (rebooted) » 2021-11-07 02:26:34

brday
Nili wrote:

All right! good job posting it here. Here we're like a big family of photographers smile

Hope you post other custom photos shortly as i like watching members posting their scrots.

Also, i wish Devuan made you feel comfortable and happy.

Best regards!

Thanks Nili, the idea is to spread Devuan to the world and many users will use it.  I wish I could  developers will be encouraged to make ultralight distributions as shown in this nice picture.

#20 Re: Off-topic » Show your desktop (rebooted) » 2021-11-07 01:23:36

brday

A beautiful image of Devuan with IceWM in another language !

Hello

Devuan chimaera with IceWM minimalist, consumes very low resources of the machine, it is to thank, an installation so customized and configured. That's why the success of MX Linux, some years it leads the DistroWatch as number one, and Antix is not far behind, it's light and is rising like the foam in the ranking of the distrowatch, hopefully the developers of Devuan, are encouraged by default to make minimalist distributions with JWM or IceWM, here I publish a beautiful image of Devuan with IceWM in another language.

IMAG2.jpg

Greetings

#21 Re: Off-topic » Show your desktop (rebooted) » 2021-11-06 07:42:20

brday

69 RAM consumption? But what do you do to consume so little resources the system of the machine?  big_smile

#22 Re: Hardware & System Configuration » Devuan does not detect Huawei smartphone hardware! » 2021-06-10 16:31:25

brday
dice wrote:

so you only see the storage device?

Id say you need to look into the desktop settings and enable view volumes on the desktop.

 

As shown in the pictures, that's all you can see. How to enable it? In the desktop settings, Removable devices is enabled in the default icons section,

#23 Re: Hardware & System Configuration » Devuan does not detect Huawei smartphone hardware! » 2021-06-10 16:09:42

brday
dice wrote:

do you see it as a device inside thunar file manager?

edit: also what is your purpose, why do you want to detect your smartphone, to detect files or to use it as a network device?

In devuan I do not see the device RNE L03 which is Huawei, only the Huawei disk is there. And logically the devices are used for what is needed, not for networking.

#24 Re: Hardware & System Configuration » Devuan does not detect Huawei smartphone hardware! » 2021-06-10 15:55:23

brday
dice wrote:

what do you mean by hardware?

Ive only ever needed to detect the storage medium.

If you look at the images of the two systems? In Linux mint it detects RNE L03 which is the hardware of the Huawei phone, while in Devuan it only detects the disk, and does not detect RNE L03 of the Huawei hardware phone.

#25 Hardware & System Configuration » Devuan does not detect Huawei smartphone hardware! » 2021-06-10 15:39:35

brday
Replies: 11

Good afternoon!

It only detects the Huawei disk, as shown in the images, in linux mint system if it detects the huawei hardware and disk, any solution to detect Huawei in devuan?

Screenshot.png

Pages: 1 2 3

Board footer

Forum Software