#61 2024-07-08 11:47:48

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

Dillo working on wayland

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

I've built a dillo-3.1.1 from here:
https://github.com/dillo-browser/dillo
https://github.com/dillo-browser/dillo/ … tag/v3.1.1
PR sent: https://github.com/01micko/01micko.github.io/pull/5

Already had it uploaded before you posted
I get emails notifications from github, thats enough.

Cool! So that answers my question about whether to post here.

carbon-trixie, trixie, carbon, doesn't matter.

OK

3) The .changes file lists .buildinfo along with the others in the set, so I included it although it's not mentioned in your user guide. Any preference there?

Actually, the .changes is the most important one!

Sorry, I could have expressed myself better. I meant that because .buildinfo is listed in the (important) .changes file, maybe reprepro would expect it (.buildinfo) also to be present. I guess it won't hurt to provide all the files listed in .changes - you can just delete any that get in the way?

I ask because your suggested command:

user@domain:~/my-package-dir$ ver=$(grep Version ${mypkg}*.changes|cut -d " " -f2)
user@domain:~/my-package-dir$ for f in $(ls | grep $ver | grep -v 'build') *orig*tar*; do cp $f ${mypkg}/;done

would leave out any package named *build*.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

https://i.imgur.com/Ij2zz5Ft.png
Dillo working on wayland

Great news!

I packaged this dillo because the Debian one is still at 3.0.5-7+b1 and doesn't have the TLS support needed to browse the Debian or BL sites, among others.
https://bugs.debian.org/cgi-bin/bugrepo … ug=1022726
https://forums.bunsenlabs.org/viewtopic.php?id=8285
https://forums.bunsenlabs.org/viewtopic … 46#p124046
https://forums.bunsenlabs.org/viewtopic … 92#p135292
( typical version number tangle: https://forums.bunsenlabs.org/viewtopic … 54#p124154 )

The only reason I'm messing with dillo at all is that it's very fast and great for underpowered machines. It could be that there's no real need for 64bit builds though - most of the target audience are likely to be 32bit.

Maybe we can leave it on your repo for a while, and if no-one reports issues I'll put it in BL trixie-backports.

P.S. The Debian dillo maintainer Axel Beckert seems to be very busy, so it wouldn't be that surprising if he didn't see switching dillo's upstream source and bringing the package up to date as a high priority.

Last edited by johnraff (2024-07-09 05:39:23)

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

Bearded_Blunder

Dodging A Bullet

From: Seat: seat0; vc7

Registered: 2015-09-29

Posts: 1,146

Re: BunsenLabs-wayland repository - in development

The only reason I'm messing with dillo at all is that it's very fast and great for underpowered machines. It could be that there's no real need for 64bit builds though - most of the target audience are likely to be 32bit.

There are some underpowered 64 bit machines out there which choke somewhat on Firefox, there were 64 bit EEE PC Netbook variants, & I'm in possession of a 64 bit capable P4... So most but maybe not all of the target audience, though it must be said I tend to add Netsurf when a machine won't cut it for Firefox as the default & keep Firefox around for those odd "one page per browser session" type instances where neither Dillo nor Netsurf are enough.

Last edited by Bearded_Blunder (2024-07-09 13:18:36)

---

Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

^fair enough. Shipping amd64 builds as well as i386 is no extra work really.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

@hhh

See this issue 01micko.github.io#9

hyprlang clashes with libhyprlang2

Why we have to tread carefully

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,032

Website

Re: BunsenLabs-wayland repository - in development

^ I saw that this morning. If you feel like rebuilding it, be my guest. I think it won't be too long until hyprpicker is packaged for Debian, the list of hypr packages is significantly longer than it was just a month ago...

https://packages.debian.org/search?sear … words=hypr

---

No, he can't sleep on the floor. What do you think I'm yelling for?!!!

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

I might just remove the hypr* stuff. Strangely enough it broke hyprlock but hyprpicker is still working. As you say, lots of hypr* is landing in testing so only a matter of time before it's all up.

EDIT: removed them.

Last edited by micko01 (2024-09-09 03:59:02)

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

I reinstated 'hyprpicker'. It doesn't depend on anything but the manpage and the install routine are severely broken! Probably why debian hasn't packaged yet even though almost everything else hypr is there. I had to resort to some nasty hacks that lintian still picks up, even though the package is sane. EDIT: the manpage bug was fixed in #86 but version 0.4.0 adds 2 more dependencies.

I figured out a cheeky way to give some color feedback in the zenity return GUI with Pango markup. This one still falls back to yad if zenity isn't installed.

#!/usr/bin/env bash

find_color() {
    printf "%d" "0x${1}"
}

_get() {
    col_in="$1"
    if ! type zenity >/dev/null 2>&1 || [ "$PICK" == 'y' ] ; then
      echo -e '<?xml version="1.0" encoding="UTF-8"?>
<svg xmlns="http://www.w3.org/2000/svg" version="1.1"  height="48px" width="48px" viewBox="0 0 48 48">
  <path d="m 0 0 48 0 0 48 -48 0 z" style="fill:'$col_in';stroke:none;"/>
</svg>' > $TEMPDIR/col.svg
    fi
    BCOL=${col_in/\#/}
    BR=${BCOL:0:2}; BG=${BCOL:2:2}; BB=${BCOL:4:2};
    BHR=$(find_color $BR)
    BHG=$(find_color $BG)
    BHB=$(find_color $BB)
    ZC='rgb('$BHR','$BHG','$BHB')'
    BHR=$(dc -e'3k '$BHR' 255 / p')
    BHG=$(dc -e'3k '$BHG' 255 / p')
    BHB=$(dc -e'3k '$BHB' 255 / p')
    X=''
    [ ${BHR:0:1} = '.' ] && X=0
    [ ${BHG:0:1} = '.' ] && X=0
    [ ${BHB:0:1} = '.' ] && X=0
    ZF=''$X$BHR' '$X$BHG' '$X$BHB''
    if type zenity >/dev/null 2>&1 && ! [ "$PICK" == 'y' ] ; then
      out=$(zenity --title="Color Picker" --icon="select-color" --list --editable --print-column=2 \
      --text="<span bgcolor=\""\#$BCOL"\"  fgcolor=\""\#$BCOL"\" font='sans 22'>....</span>"" Copy color" \
      --column="Color Space" --column="Copy Color" \
     "Color Hex" "$col_in" \
     "Color RGB" "$ZC" \
     "Color sRGB" "$ZF" \
     --ok-label="Color")
    case "$out"  in
       '#'*|rgb*)zenity --title="Color Picker" --color-selection --color="$out" >/dev/null 2>&1;;
       ?*)zenity --info --title="Info" --text="Only Hex or rgb() is supported to show the Color dialog" >/dev/null 2>&1;;
       '');;
    esac   
    else
      yad --title="Color Picker" --name="select-color" --form \
      --image="$TEMPDIR/col.svg" --text=" Copy and paste color found\n to your application:" \
      --field="Color Hex" "$col_in" \
      --field="Color RGB" "$ZC" \
      --field="Color sRGB" "$ZF" \
      --button="Color!select-color":'sh -c "yad --color --init-color='$col_in'" >/dev/null 2>&1' \
      --button="Ok!gtk-ok":0 >/dev/null 2>&1
    fi 
    return 0
}

export -f find_color _get

[ -r "$HOME/.config/blz-hyprpicker.cfg" ] && . $HOME/.config/blz-hyprpicker.cfg

if ! type zenity >/dev/null 2>&1 || [ "$PICK" == 'y' ] ; then
    export TEMPDIR
    TEMPDIR=$(mktemp -d /tmp/colpickXXXX)
fi

# cleanup
trap "rm -rf $TEMPDIR" EXIT

_get $(hyprpicker)

Last edited by micko01 (2024-10-07 08:14:02)

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

Removed azote

Official trixie has a newer version of the wayland nitrogen wannabe so no need to hang on to rotting bits.

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

Removed nwg-look. Same version now in trixie. Lots of the nwg* apps now there.

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

Updated labwc-tweaks-gtk_0.0.0-3

fixes a missing dependency

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

lightdm

Another possible addition to the dev repo?

Lightdm's last release was on  18 Jul 2022 1.32.0 and in Debian 1.32.0-6 but since then development has continued. The last commit 3abc9fb was in 20 Jun 2024 https://github.com/canonical/lightdm/commits/main/ The main dev said a while ago that he likely wouldn't make any more releases, but that if people wanted the latest code, then what was on GitHub was generally stable. https://discourse.ubuntu.com/t/current- … htdm/29048

Currently no releases are being made, you can either use the most recent release 32 or use the main git branch. The main branch should always be usable.

Hoping for a fix to the blackscreen (fixed with 1s sleep) and double-cursor (no fix yet) issues, I built lightdm 1.32.0+git240823-6+bl1 a little while ago from the github code + Debianization from Debian (adjusted patches etc). It built OK, and installed on a Trixie VM, but made no difference to those issues - or anything else I could see - so I went back to 1.32.0-6.

But a lot of commits went in between then and 3abc9fb, so it's not out of the question that something in there might fix a issue we hit in the future.

@Micko, for devs to play with, happy to upload the source and binary files if you approve? I've got a full set here from pbuilder.

Last edited by johnraff (2024-11-10 07:02:07)

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

lightdm

Another possible addition to the dev repo?
---
@Micko, for devs to play with, happy to upload the source and binary files if you approve? I've got a full set here from pbuilder.

Source code is on GitHub, carbon-trixie branch: https://github.com/johnraff/lightdm/tree/carbon-trixie

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

^Nice. I'll have a go at building tomorrow. If successful I'll put it in.

BTW I've fixed the labwc-tweaks-gtk segfault. It was a bug. Fixed upstream in PR now. I'll wait for @malms "LGTM" before I merge it but in the meantime it's patched in my repo. He may not like my idea but that's fine, it's on the radar.

Also finally figured out the 'bad-distribution' shenanigans in lintian - had to put my profile in $HOME/.lintian/[profiles,vendors].. No more 'bad-distribution' lintian errors for me! (had a look at the perl source).

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

^Nice. I'll have a go at building tomorrow. If successful I'll put it in.

Thanks! It builds for me OK, but good to get confirmation. I've tweaked the package version to 1.32.0+git240823-6.1~bl1 to avoid a lintian warning about the version not being suitable for an NMU.

There are a couple more lintian warnings, mostly "pedantic" but they all seem very Debian-specific to me.

Also finally figured out the 'bad-distribution' shenanigans in lintian - had to put my profile in $HOME/.lintian/[profiles,vendors].. No more 'bad-distribution' lintian errors for me! (had a look at the perl source).

Er, we discussed this before. You didn't notice this?
https://forums.bunsenlabs.org/viewtopic … 16#p138616
I use ~/.local/share/lintian/ but if ~/.lintian works for you I guess that's OK too.

BTW I've fixed the labwc-tweaks-gtk segfault. It was a bug.

Unfortunately just having XKB_DEFAULT_LAYOUT set in the environment wasn't enough to prevent the segfault for me.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 492

Website

Re: BunsenLabs-wayland repository - in development

lightdm added

lightdm
    ├── gir1.2-lightdm-1_1.32.0+git240823-6.1~bl1_amd64.deb
    ├── liblightdm-gobject-1-0-dbgsym_1.32.0+git240823-6.1~bl1_amd64.deb
    ├── liblightdm-gobject-1-0_1.32.0+git240823-6.1~bl1_amd64.deb
    ├── liblightdm-gobject-dev_1.32.0+git240823-6.1~bl1_amd64.deb
    ├── liblightdm-qt5-3-0-dbgsym_1.32.0+git240823-6.1~bl1_amd64.deb
    ├── liblightdm-qt5-3-0_1.32.0+git240823-6.1~bl1_amd64.deb
    ├── liblightdm-qt5-3-dev_1.32.0+git240823-6.1~bl1_amd64.deb
    ├── lightdm-dbgsym_1.32.0+git240823-6.1~bl1_amd64.deb
    ├── lightdm-vala_1.32.0+git240823-6.1~bl1_amd64.deb
    ├── lightdm_1.32.0+git240823-6.1~bl1.debian.tar.xz
    ├── lightdm_1.32.0+git240823-6.1~bl1.dsc
    ├── lightdm_1.32.0+git240823-6.1~bl1_amd64.deb
    └── lightdm_1.32.0+git240823.orig.tar.gz

Er, we discussed this before. You didn't notice this?
https://forums.bunsenlabs.org/viewtopic … 16#p138616
I use ~/.local/share/lintian/ but if ~/.lintian works for you I guess that's OK too.

.local/share/lintian didn't work
.config/lintian didn't work (that's in the perl code)
.lintian did work  (that's in the perl code)

Unfortunately just having XKB_DEFAULT_LAYOUT set in the environment wasn't enough to prevent the segfault for me.

That must be a different bug. I'll see if I can reproduce but I change GTK themes a lot in testing (especially when mucking about with that Yaru bug).

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

I use ~/.local/share/lintian/ but if ~/.lintian works for you I guess that's OK too.

.local/share/lintian didn't work
.config/lintian didn't work (that's in the perl code)
.lintian did work  (that's in the perl code)

That's strange. I thought .local/share/lintian was in the docs (can't find it now) but it works for me.

Unfortunately just having XKB_DEFAULT_LAYOUT set in the environment wasn't enough to prevent the segfault for me.

That must be a different bug. I'll see if I can reproduce but I change GTK themes a lot in testing (especially when mucking about with that Yaru bug).

The segfault is triggered when I hit "apply" trying to change the gtk theme.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

I use ~/.local/share/lintian/ but if ~/.lintian works for you I guess that's OK too.

.local/share/lintian didn't work
.config/lintian didn't work (that's in the perl code)
.lintian did work  (that's in the perl code)

That's strange. I thought .local/share/lintian was in the docs (can't find it now) but it works for me.

I searched around and eventually found these:

https://www.chiark.greenend.org.uk/doc/ … d-location

The filename for the profile is derived from the name by simply concatenating it with .profile, Lintian will then look for a file with that name in the following directories:

    $XDG_DATA_HOME/lintian/profiles
    $HOME/.lintian/profiles
    /etc/lintian/profiles
    $LINTIAN_BASE/profiles

Note that an implication of the handling of default vendor profiles implies that profiles must be in subdirectories of the directories above for Lintian to recognise them.

The directories are checked in the listed order and the first file matching the profile will be used. This allows users to override a system profile by putting one with the same filename in $XDG_DATA_HOME/lintian/profiles or $HOME/.lintian/profiles.

(I guess the same is intended to apply for lintian/vendors)

https://linux.debian.bugs.dist.narkive. … upport-xdg

... and for "data":

$XDG_DATA_HOME/lintian
(default: $HOME/.local/share/lintian)
$HOME/.lintian *
/etc/lintian *
$XDG_DATA_DIRS/lintian
(default: /usr/local/share/lintian:/usr/share/lintian)
LINTIAN_ROOT
(default: /usr/share/lintian)

(entries marked with * are compatibility locations)

...which suggested that lintian - at least at some point in time - was intended to check those locations for the lintian/{profiles,vendors} directories, and $XDG_DATA_HOME - which defaults to $HOME/.local/share - comes first in the list.

Anyway, I'll add a note to the OP on this topic, saying that at least one developer found that $HOME/.local/share/lintian didn't work.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,550

Website

Re: BunsenLabs-wayland repository - in development

(stuff about wallpaper setters)

We really should split this out to a new thread

Done: https://forums.bunsenlabs.org/viewtopic.php?id=9229

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop