You are not logged in.
I'll delete those posts from that other thread.
The first one has a different name, the second one is named as you show it. Are you using auto.mirror.devuan.org or pkgmaster.devuan.org?
aptitude search libevent
...
i A libevent-2.0-5 - Asynchronous event notification library
p libevent-2.1-6 - Asynchronous event notification library
...
apt-cache policy libevent-2.0-5
libevent-2.0-5:
Installed: 2.0.21-stable-2+deb8u1
Candidate: 2.0.21-stable-2+deb8u1
Version table:
2.0.21-stable-3 0
100 http://pkgmaster.devuan.org/merged/ ascii/main amd64 Packages
100 http://pkgmaster.devuan.org/merged/ ceres/main amd64 Packages
10 http://debian.csail.mit.edu/debian/ stretch/main amd64 Packages
10 http://debian.csail.mit.edu/debian/ buster/main amd64 Packages
10 http://debian.csail.mit.edu/debian/ sid/main amd64 Packages
*** 2.0.21-stable-2+deb8u1 0
500 http://auto.mirror.devuan.org/merged/ jessie/main amd64 Packages
500 http://auto.mirror.devuan.org/merged/ jessie-security/main amd64 Packages
500 http://debian.csail.mit.edu/debian/ jessie/main amd64 Packages
100 /var/lib/dpkg/statusapt-cache policy libzstd1
libzstd1:
Installed: (none)
Candidate: 1.3.2+dfsg-1
Version table:
1.3.2+dfsg-1 0
100 http://pkgmaster.devuan.org/merged/ ceres/main amd64 Packages
10 http://debian.csail.mit.edu/debian/ buster/main amd64 Packages
10 http://debian.csail.mit.edu/debian/ sid/main amd64 Packages
1.1.2-1 0
100 http://pkgmaster.devuan.org/merged/ ascii/main amd64 Packages
10 http://debian.csail.mit.edu/debian/ stretch/main amd64 PackagesI'm sure there were changes upstream from 1.6 to 1.75 in debian. I think the only changes that devuan made to 1.75 was to remove the dependency on libsystemd0, but it may have been more involved than that. The only way to know for sure what changes were made would be to compare the source code of both packages.
One possible simple solution is to try one of the generic drivers. I think you'll find them at the end of the list of drivers when you're adding a printer in the cups admin. (http://localhost:631)
Right now, all the devs are focused on ascii, so getting changes/fixes in jessie or doing anything with wheezy packages is unlikely to happen. There may be a way to get your printer working by editing some cups config files, but I don't know my way around that enough to even give you a hint.
Looking under /devuan, there doesn't seem to be anything in jessie-proposed-security or jessie-proposed-backports. And there's almost nothing in jessie-proposed-updates - I think it's just an old version of desktop-base. I think it makes sense to use only the /merged sources unless you know there's a particular package in the /devuan sources that you need. (like you're testing a new build for a packager.)
You probably need the netboot files.
https://packages.devuan.org/merged/dist … s/netboot/
https://packages.devuan.org/merged/dist … s/netboot/
NO! Don't do it. (Not sure exactly what the package manager is trying to do there, but it looks bad.)
There's no python3.5 in jessie or jessie backports. You can get 3.4 from the regular jessie repo.
apt-get install python3Comment out the backports lines and run 'apt-get update' again. Then install python3. If you did a full desktop install, you probably already have it.
If you want to see a list of all the python packages that are installed, run
dpkg -l | grep pythonThe need for nomodeset is fairly common. It depends on the video card. I got a black screen without it on my old nvidia card and a black screen with it on my new nvidia card.
I looked at refractainstaller-uefi and found some errors. It won't see the mmc drive for the grub selection, but it should see it for /, /home and /boot choices. What does fdisk show for the drive's device name? I would expect something like /dev/mmcblk0p1 for the first partition on the first drive. I'd like to know if I need to change my search pattern. Thanks.
If you want to try a corrected version of the script, I can post it somewhere.
I can think of some other options. When I was adding support for nvme disks in refractainstaller, I didn't have any nvme disks to test it, so I also made it aware of mmc devices. I know it sees them and displays them as choices for partitions/drives, but I've never tested an actual install to one. Nothing here will boot from mmc. So there are a couple of options for using that installer.
1. Try the devuan desktop-live uefi iso. It's jessie, but since the installer will see your drive, it might work.
https://files.devuan.org/devuan_jessie/desktop-live/
2. Try a refracta iso with the same installer.
Those are here - https://sourceforge.net/projects/refrac … isohybrid/
3. If you really do need a newer kernel, I made a devuan desktop-live iso with 4.9 kernel from backports.
That's here - http://distro.ibiblio.org/refracta/files/experimental/
Also in that same directory is ascii with openrc and eudev. That one is more experimental and was made for testing purposes. It's probably not your best choice.
4. Try a refracta-ascii no-X iso - https://sourceforge.net/projects/refrac … s/testing/
That one has the same installer, cli version. It's labeled as pre-alpha, but keep in mind that ascii is based on stretch, so it's really pretty stable. Refracta is a re-spin of Devuan and uses Devuan repositories for packages.
5. Use a refracta iso to do a debootstrap install of ascii.
In Debian and Devuan (and many other derivatives), runlevels 2-5 are the same.
To disable wicd in all runlevels:
update-rc.d -f wicd removeTo reverse the above:
update-rc.d wicd defaultsAnother way to do it is to install sysv-rc-conf and un-check all runlevels on the wicd line. (use arrow keys and space bar)
Are you gonna show us your script? How do you get the window to stay up when you make a selection?
apt-get install hddtemp libxfcegui4-4 ristretto xfce4-artwork xfce4-battery-plugin...and any other packages from the autoremoval list that you want to keep. They will then be marked as manually installed.
Those libraries are only jessie. Find out why they are there.
aptitude why libgnutls-deb0-28Maybe apt can fix the breakage...
apt-get -f installor re-run the dist-upgrade. (I had to do that on a couple of jessie to ascii upgrades.)
Maybe tell apt which chromium you want.
apt-get install chromium=62.0.3202.89-1~deb9u1xclock is part of x11-apps, which has other cool stuff like xeyes and xcalc. That's just there to have something non-essential to kill. Break the line up into multiple lines, and it will make more sense. The numbers set the exit code for each button, the ans="$?" stores the exit code, then you test to see which action to perform based on the exit code.
xclock &
yad --button="Kill panel":0 --button="Say hello":1 ; ans="$?" ; if [[ $ans = 0 ]] ; then killall xclock ; elif [[ $ans = 1 ]] ; then echo "Hi" ; else echo "Bye" ; fiThe second way is easier. The first way should work, but I can never do it correctly.
The devuan live isos are made with live-config and live-boot, same as debian, so the options are the same.
One thing different from the debian-live isos - the current (jessie) devuan-live isos have a pre-configured user, so you should not use "config" or "components" (live-config or live-components) on the command line. If you do use that option, you will only get the components that you named. (i.e. you must name every component that you want. See /var/log/live/config during a live session. That will show you which ones were used.)
If you use the hookscript, it will create a file, /etc/profile.d/zz_locale.sh (or maybe tt_locale.sh) which will contain:
export LANG=fr_FR.UTF-8
export LC_ALL=fr_FR.UTF-8Every user on the system will get French. If you want only one user to have French, remove that file and put those lines in ~/.profile for that user.
I've seen that happen, but I don't know what causes it. It hasn't happened in a long time. Tell me more about your setup. Is there another OS installed? Did you start with a new hard drive with nothing on it? How did you partition it?
And are you the same person who was telling me about this in irc a couple days ago?
Yes, devuan is following debian releases. Most of the packages in devuan are unchanged from debian. The plan is to change as little as possible to provide a debian-based system without systemd.
Here's a more memorable url where you can find those package lists:
https://pkgmaster.devuan.org/
had to replace the native LXQt shutdown options with Obsession since none of them worked
I have an lxqt install, and all the logout buttons work. We have the same policykit packages installed (except you included the l10n package). Mine started out as openbox with lxpanel. You have libpam-gnome-keyring. I don't. Other libpam stuff is the same.
Maybe it's in the 'power' packages. I have libupower-glib3 that you don't have, and I see that xfce4-power-manager is running in mine. Not saying you need to do anything about it. All the logout buttons work in your iso. But since so many people run into problems with logout buttons, I figured this was a good place to drop my observations.
The ascii kernel version was finalized when stretch went into freeze. I think that was around a year ago. But your point about the documentation is spot on. Most of the debian documentation applies to devuan. (Except the systemd stuff). And even wheezy docs are mostly accurate for devuan jessie.
Howtos are supposed to go in the Documentation section. It even says so.
How-tos and Tips & Tricks contributed by Devuan users
There isn't much official documentation yet, but I think the idea was that some of the howtos might develop into official docs.
The way to get around needing different versions of grub for uefi vs bios is to include grub packages so you can install what you need. Support for this is in the installer (more or less, depending on the version.) Another way to deal with it is to skip installing the bootloader. This will work if you already have a working bootloader and can add another entry. (i.e. multiboot linux setup.)
Oops. You asked about making a snapshot, not installing. OK, refractasnapshot has an option called force_efi. It will work if grub-efi-amd64 was installed and then replaced with grub-pc without autoremoving the associated packages. (use apt-get, not aptitude to remove grub-efi)
More (edit2): Refracta isos have grub-pc installed and grub-efi packages included in the iso. The devuan desktop-live-uefi iso has grub-efi installed and the grub-pc packages were included (somewhat accidentally.)
A link to the wiki should be added to the announcement post that was linked above.
I don't think the documentation section needs to be broken into categories. Maybe later.
I can confirm that it boots on uefi hardware.
Suspend works from the menu. On lid closure, all it does is turn off the screen. I could still log in through ssh (I added the server).
If you want to get ahead of the repo, there are newer versions of refractainstaller-base and refractasnapshot-base.The cli installer script can now do uefi install, and both -base packages have additional rsync excludes for /lib as a symlink to /usr/lib.
https://sourceforge.net/projects/refracta/files/tools/
Symlink /lib not an issue if you upgrade from jessie, but if you do a debootstrap install of ascii or install from an ascii installer iso (soon to be real) then you'll end up with /lib as a symlink. If you don't exclude some stuff in /usr/lib/live you end up with an extra copy of the system. You'll know this happened because your iso will be a lot bigger than you expected.
...in this locked thread: http://dev1galaxy.org/viewtopic.php?pid=5934#p5934
I thought that, too. Then I posted on it. I guess the OP meant to mark it 'solved' instead of 'closed'. When you enter the thread, look on the right side, just above the message, it says 'post reply' instead of 'topic closed'. Also, subject says (Closed) instead of Closed: