DebianDog Sid (without systemd) + build system (mklive-sid)

[fredx181]

No, it wouldn't have setup the EFI Multiboot correctly.
Sorry to say, but the included (full) installer is in fact terribly outdated, it makes use of grub4dos which doesn't work with EFI AFAIK, so you'd need GRUB2 to make it work.

[BobC]

Ok, thanks, I did the right thing by using grub2 from another installed distro to add it to the grub boot, then

[dcung]

I used mklive-sid last on 15 Dec 2022.
No problem then.

Later, I used it again to refresh my ISO (DDOG flavour), minor changes: like swap frisbee with peasywifi, add volumeicon-alsa and changed password.
Got errors. It wasn't urgent, so I waited 2 weeks, hoping it resolved 'itself'.

I just run it again today. Still same errors.
I could have removed peasyglue, but some other dependency issues may come up.
So, I thought to report it. Maybe, it's something that Fred needs to get involved (?)

Code: Select all

...
sysvinit-core is already the newest version (3.06-2).
whiptail is already the newest version (0.52.23-1+b1).
xkb-data is already the newest version (2.35.1-1).
xkb-data set to manually installed.
xz-utils is already the newest version (5.4.1-0.1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 obkey : Depends: python2 but it is not installable
 peasyglue : Depends: libnetpbm10 but it is not installable
E: Unable to correct problems, you have held broken packages.
Sorry, there are one or more errors, see above.
Could be a typo in a package name.
Exiting . . .
Unmounting mount binds in chroot
root@live:/mnt/sda4/Sid# 

[fredx181]

So, I thought to report it. Maybe, it's something that Fred needs to get involved (?)

Ok, I'll try to get involved
Well that the case with such "rolling" distro as Sid is.
Similar happened with Bookworm recently, python2 removed from Debian repository, completely replaced by python3.(and removed libnetpbm10).
I will look at this, probably adding these to the custom 'dog' repository for Sid should fix it (worked ok with Bookworm).

I'll get back later about this.

[fredx181]

@dcung Should be fixed now, can you try again ? I did the same as recently for Bookworm, tested now with the "Tint2" Desktop option and doesn't get stuck on obkey and peasyglue.
And ... very much appreciated your reports by the dog team

EDIT: note that the python2 is very minimal i.e. the many python modules for v2 (once in the repository) are not available (but possible perhaps to take them from earlier Debian version).

[dcung]

Should be fixed now, can you try again ?

Tested.
Successfully made DDOG & OBDOG iso.
Did my usual very minimal testing (frugal).
Connect to internet, youtube, okay.

I usually add Chrome when I make iso.
This is just FYI.
From time to time, when I made/refreshed isos Stretch/Buster/Bullseye/Sid, Chrome does not work - I didn't take note which flavour works, which doesn't.
It does not worry me since I know the reason and I only have to change puppy home (config) permission and it will work, it had read-only.
I could have changed it myself for my own ISOs, but since I refresh ISO frequently, often it got passed me until it's too late .

Since I just made DDOG & OBDOG iso, just letting you know Sid (DDOG & OBDOG) is one of these, in case you feel like updating the permission at the 'central' for next new person that use mklive and happen to select Chrome or whatever else that needs to write config files.

From this:

2023-02-03-003847_896x644_scrot.png (45.82 KiB) Viewed 8128 times

To this:

2023-02-03-004245_386x413_scrot.png (47.6 KiB) Viewed 8129 times

Thanks Fred!

[rcrsn51]

I don't understand this peasyglue situation. The original package just depends on netpbm. In Sid, that should automatically get you netpbm_11 and its dependency libnetpbm11.

How did it get locked into libnetpbm10?

[fredx181]

I don't understand this peasyglue situation. The original package just depends on netpbm. In Sid, that should automatically get you netpbm_11 and its dependency libnetpbm11.

How did it get locked into libnetpbm10?

It has libnetpbm10 in control file:
Depends: libc6, gtkdialog, netpbm, libnetpbm10, bc, poppler-utils
It's v2.2, not sure who package'd it, I think it was me long ago (don't see your name at the Maintainer line).
Probably best to remove libnetpbm10 from Depends line, so then should automatically install libnetpbm11, as you say.

@dcung Thanks, although it may work what you did, I think that's not the real issue, the permissions are already what it should be IMO, 755 for home/<user>.
I found that logging in as "puppy" didn't work, I suspect it is because the user id 1000 is wrong for /home/puppy, in reality the user id of puppy is 1002 (as it shows in /etc/passwd), check with id puppy and you probably get UID=1002(puppy) .... ...
I will investigate how this can happen and try to fix it, no idea yet.

[rcrsn51]

That libnetpbm10 dependency is not in my version of the package.

Here is v2.3 with a few minor changes and the correct dependency list.

[dcung]

... although it may work what you did, I think that's not the real issue,
I will investigate how this can happen and try to fix it, no idea yet.

I suspected that may not be the real issue.
Yes, id puppy gave uid=1002.
Hope you can get to the bottom of it.

[fredx181]

That libnetpbm10 dependency is not in my version of the package.

Here is v2.3 with a few minor changes and the correct dependency list.

Thanks, will add to repos later.

[fredx181]

... although it may work what you did, I think that's not the real issue,
I will investigate how this can happen and try to fix it, no idea yet.

I suspected that may not be the real issue.
Yes, id puppy gave uid=1002.
Hope you can get to the bottom of it.

Did a lot of checking if the (wrong) 1000 ownership of /home/puppy could be perhaps caused by something in the build process, but not, all good, the ownership is puppy:puppy in the built system, so that's OK.
So, my conclusion is that it happens (that ownership /home/puppy gets 1000) in the Debian boot process, something has changed (by Debian) in Bookworm and Sid, perhaps some useradd configuration, don't know yet.
Anyway, found a good workaround by adding a script (in the files copied to the build) /etc/profile.d/chownpuppy.sh that will set ownership of /home/puppy to puppy at boot (instead of 1000).

Problem should now be fixed for when doing a new build.
(edit; fixes a possible problem to be able to login as user 'puppy' and also when running run-as-user <some-application> and when running e.g. google-chrome or e.g. vlc from menu (which depends on 'run-as-user' as it cannot run as root).

For an existing build to fix, run this command chown -R puppy:puppy /home/puppy
AFAIK this issue is only for Bookworm and Sid (not Bullseye or/and earlier).

EDIT: Same fix for Bookworm, see here (and for additional info); https://forum.puppylinux.com/viewtopic. ... 564#p80564

[dcung]

...
Problem should now be fixed for when doing a new build.
...

I remade my Sid ISOs (DDOG, OBDOG).
Chrome works without needing me to change permission anymore.

Thanks, Fred.

[fredx181]

New mklive-sid build script attached + info at first post

[fredx181]

New mklive-sid build script attached at first post

Important change:
- Debian has now a separate repository for nonfree firmware: non-free-firmware
Added it in the script to be able to use it.
For an existing build, change in /etc/apt/sources.list:
deb http://deb.debian.org/debian sid main contrib non-free
To (add "non-free-firmware"):
deb http://deb.debian.org/debian sid main contrib non-free non-free-firmware
(also added this change to updated "repo-conf" (1.0.3) package in custom repository)

Other changes:
- No prompt anymore during build for yes/no overwriting (custom) /etc/rc.local
- The Desktop environment chosen (DE_CONFIG variable) now added to the "build_setup.conf" file.
EDIT: The "Bookworm Build script" is also updated with similar changes, see: viewtopic.php?p=48359#p48359

[rcrsn51]

Hi Fred: I ran mklive-sid today with "-cli" and "Skip" but I got a fuse3-related error. So I changed the package name "fuse" to "fuse3" in one place and it worked.

[fredx181]

Hi Fred: I ran mklive-sid today with "-cli" and "Skip" but I got a fuse3-related error. So I changed the package name "fuse" to "fuse3" in one place and it worked.

Thanks, new attached with fix at first post.
edit: also 'fixed' that user "puppy" gets uid 1000 (instead of previously being 1002)

[dcung]

Thanks, new attached with fix at first post.
edit: also 'fixed' that user "puppy" gets uid 1000 (instead of previously being 1002)

I run mklive-sid (OBDOG) today.
gnome-mplayer has dependency issue?
I took it out of my conf for the time being and it build ok without it.

Code: Select all

xkb-data set to manually installed.
xz-utils is already the newest version (5.4.1-0.2).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gnome-mplayer-1.0.6 : Depends: gconf-service but it is not installable
                       Depends: libgconf-2-4 but it is not installable
                       Depends: libncurses5 but it is not installable
E: Unable to correct problems, you have held broken packages.
Sorry, there are one or more errors, see above.
Could be a typo in a package name.
Exiting . . .
Unmounting mount binds in chroot

[fredx181]

gnome-mplayer has dependency issue?

Thanks, yes, because some of the dependencies are removed now from the Debian Sid repo (probably has to do with less support for gtk2).
Should be fixed now, added some (older) packages to the sid custom repo (gmplayer should work too now, had similar problem).

I may not continue maintaining the older stuff (e.g. gnome-mplayer and gmplayer from custom repo) in the future (kind of duct-taping ) .
Better perhaps only include the player software from Debian, e.g. there's gnome-mpv, mplayer-gui (similar as gmplayer), smplayer etc...

[dancytron]

I've built a couple just playing around at how small I can get them.

No errors.

[dcung]

I built a few more. Just testing.

Any DE that uses Thunar -> no Thunar.
Any DE that uses PCManFM -> okay.

2023-08-14-092310_820x219_scrot.png (50.48 KiB) Viewed 7642 times

[fredx181]

@dcung thanks again !
Rolling release as Sid is brings many changes.
Did repair by upgrading packages eudev and libeudev1 (provides libudev1) in custom repo, so thunar problem should be fixed.
(this only applies for a no-systemd build, a systemd build uses the standard udev and libudev1)

Found another problem: symlink /bin/sh should point to /bin/bash (in the DD setup), but is not (pointing to the default Debian /bin/dash), this causes problems with some gtkdialog based programs, so major problem.
Caused by the decision to not support anymore "dpkg-reconfigure dash" (which gave choice to run dash or bash as default shell) by the Debian devs.

New mklive-sid attached at first post should fix this issue.

On an existing Sid build, check from terminal the symlink /bin/sh ls -l /bin/sh if it points to dash /bin/sh -> dash then change by doing:
cd /bin; ln -sf bash sh

[dimkr]

Found another problem: symlink /bin/sh should point to /bin/bash (in the DD setup), but is not (pointing to the default Debian /bin/dash), this causes problems with some gtkdialog based programs, so major problem.
Caused by the decision to not support anymore "dpkg-reconfigure dash" (which gave choice to run dash or bash as default shell) by the Debian devs.

gtkdialog 0.8.5c can be built with -Dbash=true, which forces it to run actions using bash. This makes various Puppy scripts "just work" against dash without changes, unless they use #!/bin/sh.

https://github.com/puppylinux-woof-CE/g ... g/pull/154

[fredx181]

Found another problem: symlink /bin/sh should point to /bin/bash (in the DD setup), but is not (pointing to the default Debian /bin/dash), this causes problems with some gtkdialog based programs, so major problem.
Caused by the decision to not support anymore "dpkg-reconfigure dash" (which gave choice to run dash or bash as default shell) by the Debian devs.

gtkdialog 0.8.5c can be built with -Dbash=true, which forces it to run actions using bash. This makes various Puppy scripts "just work" against dash without changes, unless they use #!/bin/sh.

https://github.com/puppylinux-woof-CE/g ... g/pull/154

Thanks, but the thing is that many scripts do have #!/bin/sh on top and may include bashisms, so IMO having symlink sh > bash is the safest.

[dancytron]

Just built a 32 bit DD Sid with systemd and pipewire. using the same method as in Bookworm.

Works fine.

edit: Firefox youtube was very slow with lots of dropped frames on a Windows 7 era computer, even at low resolution, like there was no video acceleration at all. Not going to worry about it.

[dcung]

I refreshed my Sid iso sets.

The minimal DE (Openbox, XFCE4, Jwm) build okay.
The Full DE (DDog, ObDog) gave errors near end of builds.

Code: Select all

...
Hit:1 http://deb.debian.org/debian sid InRelease
Hit:2 http://dl.google.com/linux/chrome/deb stable InRelease
Get:3 https://github.com/doglinux/sidog/raw/master/amd64 ./ InRelease [2301 B]
Fetched 2301 B in 1s (2641 B/s)
Reading package lists...
[0;36mChecking packages . . .[0m
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package isomaster
[0;31mSorry, there are one or more errors, see above.[0m
[0;31mCould be a typo in a package name.[0m
[0;36mExiting . . .[0m
[0;36mUnmounting mount binds in chroot[0m

[fredx181]

E: Unable to locate package isomaster

I've noticed too (it's not anymore in Debian sid repo) and removed isomaster from the online configs, probably you used a local .conf, in that case just remove isomaster from the install list.

[dcung]

E: Unable to locate package isomaster

I've noticed too (it's not anymore in Debian sid repo) and removed isomaster from the online configs, probably you used a local .conf, in that case just remove isomaster from the install list.

Yes, I was using local .conf from recent/last build.
Removed now. Thanks Fred.

[fredx181]

*** mklive-sid updated ***, new script attached at first post

- Most important change IMO is that the sources.list contains now a snapshot.debian repository entry from 10 days ago, 26 sep 2023.
This is to prevent that a build may fail because of a package missing (recently removed from Debian repo), most recent is the removal from Debian of 'rox-filer' (and before that 'isomaster').
Does not mean that any package(s) will be downgraded, just for to support installing packages that were recently removed from the regular Sid repo.

- Other changes (in the repositories):
-- removed 'initscripts' from the package list configs, this fixes a build failure in case of a build with systemd activated.
-- removed 'gmplayer' from the custom repo (was custom build from years ago), alternative is "mplayer-gui" from Debian repo (apt install mplayer-gui mplayer-skin-blue)
-- peasymp3 depends now on mplayer (from Debian repo) instead of 'gmplayer'
-- gnome-mplayer ('gnome-mplayer-1.0.6' named on amd64) depends on mplayer now instead of the custom build mplayer binary (old version) that was included in the package
-- run-as-user package (similar to run-as-spot) updated, includes @jamesbond's newest improvements but modified for Debian dog.
-- edit: mklive-sid gets the package list configs now from 'configs-sid' https://debiandog.github.io/MakeLive/configs-sid (previously was same as configs for bookworm)

[fredx181]

Forgot to add info in previous post:
On Sid, pcmanfm, lxpanel and libfm are now GTK3 builds instead of GTK2 (may look a little different but works OK from what I tested).
(another step for the transition to GTK3 and deprecated GTK2)