Post your bugs finding
Bug report
2016/08/19
Sometimes yaourt fail to install obmenu-generator for openbox config because it don't find the dependancy linux-desktop-files. Obviously, the script stop. This is not depend of the script, simply launch again the script and pick the number 9 to resume the installation. The installation should restart to the last package fail installation and continue as usual.
Sometimes yaourt fail to install obmenu-generator for openbox config because it don't find the dependancy linux-desktop-files. Obviously, the script stop. This is not depend of the script, simply launch again the script and pick the number 9 to resume the installation. The installation should restart to the last package fail installation and continue as usual.
4 years later
install fails when trying to format a xfs partition:
because normally, formatting an already existing partition into xfs requires -f (force flag), formatting into such in obarun-install will kick you out when doing so.
because normally, formatting an already existing partition into xfs requires -f (force flag), formatting into such in obarun-install will kick you out when doing so.
strange because the -f option is used when you ask for a xfs filesystem: https://framagit.org/Obarun/obarun-install/-/blob/master/install/partition.sh# L19
So i need to make test to see what happens
So i need to make test to see what happens
- Edited
its probably not about the -f then, but i really ddnt look closely. i only notice this when formatting partitions as xfs
edit: just confirmed, ${FS_FLAGS[$fs]} does not includes any flag in part_format()
edit: just confirmed, ${FS_FLAGS[$fs]} does not includes any flag in part_format()
RE: color issue similar to pacopts:
there is also this which is the first error that breaks the text box in the installer:
but i cant find that specific line. should be that green color as well.
obarun-install: tracing: Clone repository from 33[0;32m[https://framagit.org/Obarun/obarun-install-themes.git]33[0m
Cloning into 'obarun-install-themes'...
bad line : oblog -t "Clone repository from ${green}[$_address]${reset}", in pac.shthere is also this which is the first error that breaks the text box in the installer:
obarun-install: tracing: Check update for obarun-install
obarun-install: tracing: Clone repository from 33[0;32m[https://framagit.org/Obarun/obarun-install.git]33[0m
Cloning into 'obarun-install'...
remote: Enumerating objects: 37, done.
remote: Counting objects: 100% (37/37), done.

but i cant find that specific line. should be that green color as well.
thanks for the reports.
about obarun-libs: https://framagit.org/Obarun/obarun-libs/-/commit/3655186c19f9bfc1d09f0f0083b01df8862a0e8a
the last issue, you can find the text here: https://framagit.org/Obarun/obarun-install/-/blob/master/install/dg_menu.sh# L10
The color expected is yellow.
about obarun-libs: https://framagit.org/Obarun/obarun-libs/-/commit/3655186c19f9bfc1d09f0f0083b01df8862a0e8a
the last issue, you can find the text here: https://framagit.org/Obarun/obarun-install/-/blob/master/install/dg_menu.sh# L10
The color expected is yellow.
im actually refering to the broken text-box (shows letters instead of box) in the last screenshot, which is probably caused by the color error in the SS above it (hence this line, "Clone repository from" which i cannot find)eric wrotethanks for the reports.
about obarun-libs: https://framagit.org/Obarun/obarun-libs/-/commit/3655186c19f9bfc1d09f0f0083b01df8862a0e8a
the last issue, you can find the text here: https://framagit.org/Obarun/obarun-install/-/blob/master/install/dg_menu.sh# L10
The color expected is yellow.
it's a glibc issue. The default mirror is completely broken and install an old version of glibc which cause the issue.
Bug with setting root password i should have reported about it here first.
For me not able to set root password during sudo obarun-install, but i changed mirrorlist to Bulgary and marked every worldwide mirror with # , and then before sudo obarun-install i did pacman -Sy pam and last set sudo obarun-install, everything installed fine
For me not able to set root password during sudo obarun-install, but i changed mirrorlist to Bulgary and marked every worldwide mirror with # , and then before sudo obarun-install i did pacman -Sy pam and last set sudo obarun-install, everything installed fine
2 months later
Couldn't update install theme without [--overwrite '*'] option workaround.
error: failed to commit transaction (conflicting files)
obarun-install-themes: /var/lib/obarun/obarun-install/config/jwm/rootfs/etc/skel/.config/picom.conf exists in filesystem
obarun-install-themes: /var/lib/obarun/obarun-install/config/openbox/rootfs/etc/skel/.config/picom.conf exists in filesystem
Errors occurred, no packages were upgraded.
# pacman -Su --overwrite '*'
hum
% sudo pacman -Sy obarun-install-themes
:: Synchronizing package databases...
init-toolchain is up to date
obcore-testing is up to date
obcore is up to date
obextra-testing is up to date
obextra is up to date
obcommunity-testing is up to date
obcommunity is up to date
obmultilib is up to date
observice-testing is up to date
observice is up to date
core 129.2 KiB 923 KiB/s 00:00 [----------------------] 100%
extra 1631.8 KiB 1854 KiB/s 00:01 [----------------------] 100%
community 5.2 MiB 2.80 MiB/s 00:02 [----------------------] 100%
multilib 155.3 KiB 3.23 MiB/s 00:00 [----------------------] 100%
resolving dependencies...
looking for conflicting packages...
Package (1) Old Version New Version Net Change
obextra/obarun-install-themes 0.1.8+56+g450b36d-1 0.2.0-1 0.00 MiB
Total Installed Size: 4.30 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [----------------------] 100%
(1/1) checking package integrity [----------------------] 100%
(1/1) loading package files [----------------------] 100%
(1/1) checking for file conflicts [----------------------] 100%
(1/1) checking available disk space [----------------------] 100%
:: Processing package changes...
(1/1) upgrading obarun-install-themes [----------------------] 100%
obarun@ S6 ~ %
Someone else have the same issue ?a year later
obarun-installer fails when trying to test the network connection in qemu, it is a qemu issue (https://wiki.qemu.org/Documentation/Networking# Network_Basics). I made a patch to fix this, check https://codeberg.org/Enocstocks/obarun-install/src/branch/qemu-fix.
5 days later
Hi Enoc,
thanks for this one. Maybe you can make a pull request at https://framagit.org/obarun/obarun-install.
thanks for this one. Maybe you can make a pull request at https://framagit.org/obarun/obarun-install.
5 days later
I had a small issue that would might confuse someone not so used to more technical distributions but was easy enough to circumvent. In regards to the automatic partitioning thingy on my NVME SSD. It got confused and was looking for "/dev/nvme0n11" instead of "/dev/nvme0n1p1" as the formula for NVME drives is nvme0n1p*
Sorry, I should have saved the exact error, I don't know if that is enough information to be helpful at all. It was reproducible every time, but now that my system works I don't really want to reproduce it lol.
Sorry, I should have saved the exact error, I don't know if that is enough information to be helpful at all. It was reproducible every time, but now that my system works I don't really want to reproduce it lol.
5 days later
Without any logs of the trouble it will be difficult to know what to do :/
9 months later
- Edited
RE: regarding issue about xfs unable to source appropriate flags FS_FLAGS[] causing formatting with xfs to fail due to missing -f option, not entirely sure why this script fails to source from the said array, but since there is only one section using this (part_format()), why not just make the "mkfs.$fs" and its flags from FS_FLAGS[] as a case statement? its not taht xfs was the only one having issue, no flags was getting passed thourh when accessing this array regardless of FSTYLE, it just so happens that xfs needs that -f option else formatting on an already existing partition will fail.
https://framagit.org/Obarun/obarun-install/-/blob/master/install/partition.sh# L213
${FS_FLAGS[$fs]} always returns blank.
https://framagit.org/Obarun/obarun-install/-/blob/master/install/partition.sh# L213
${FS_FLAGS[$fs]} always returns blank.
6 months later
eric unstickied the discussion .