Re: homebrew for debian or ubuntu
Jeffrey Walton wrote: > Homebrew only supports the last release or two on MacOS. Today, you > might see support for Version 13: "Ventura" and Version 12: > "Monterey". Anything else and you had to use MacPorts. Or pkgsrc*, which isn't quite as popular but supports (or can be made to support) pretty much everything and it's a good citizen. Sticks to its own prefix. On Debian I use it to use newer versions of a handful of command-line tools and libraries (for development and testing). I don't have it added to my PATH by default so it doesn't get in the way. It doesn't work so well for GUI apps though, doesn't pick op fonts and themes so it's tofu everywhere. Possibly something that can be fixed by tweaking some configuraton somwhere.. *) for disclosure, I maintain some packages on pkgsrc Sijmen
Vulnerable git in bullseye - what's the process?
Hi all, I was surprised to find that the recent git vulnerability hasn't yet been addressed in Bullseye: https://security-tracker.debian.org/tracker/CVE-2022-41903 My question isn't about the situation of this package per se but about the process. I found this diagram: https://wiki.debian.org/DebianReleases#Workflow It shows how packages go from unstable to testing, stable, etc. with 'security' having a direct route from the security team. Now what I wonder is, is that part of the process visible somewhere? Can I see if there are yet patches submitted, if there are builds failing, etc? Generally just interested in seeing what's going on there. Perhaps contribute. (Let me be clear - I am NOT demanding support from anyone or complaining.) Sijmen
Re: zwart op wit, constrastrijk
Hi Geert, Geert Stappers wrote: > Aanname: Er zijn hier mensen die dat ook hebben. Zeker! Ik doe dat ook. > Programmas die lichte kleuren als geel en lichtblauw gebruiken > om tekst te laten opvallen. Er zjn een aantal dingen die je kunt doen: 1. Als je eigenlijk helemaal niet zo'n behoefte hebt kun je programma's configurareren om geen kleur te gebruiken. Dat doe ik meestal. In het bijzonder heeft de standaard Debian ~/.bashrc een hele sectie die kleur configureert. Ik heb dat er allemaal uitgehaald. Je kunt ook NO_COLOR=1 in de omgeving definieren, een aantal programma's respecteren dat. 2. Veel programma's gebruiken het basispallet van 16 kleuren. Dit pallet kun je aanpassen in de voorkeuren van de terminal, dan kun je bijvoorbeeld een andere, leesbare, tint aangeven voor 'lichtblauw'. (In MATE Terminal vond ik het standaardkleurenschema al aardig.) 3. Andere programma's die 256 of 'ware kleuren' gebruiken moet je soms handmatig configureren. Hopelijk heb je hier wat aan. Sijmen
Re: Emoji fonts in Debian [WAS:] Re: How to NOT automatically mount a specific partition of an external device?
Celejar : > I'm curious: do most users of Debian on the desktop (who use MUA > software, as opposed to webmail via a browser) have such a font > installed, or do they see tofu? I too use Sylpheed and get tofu. I must have mistakenly assumed emoji fonts would be installed by default hence this being a Sylpheed limitation. Thanks for enlightening! Same issue with Sylpheed on Windows by the way, wonder if the same solution would work... Sijmen
Need to do 'swanctl --load-all' every boot
Hi all,
I've set up an IPsec + IKEv2 VPN server ('road warrior' set up) on
Debian 10 with StrongSwan. It was my understanding that
/etc/strongswan.d/swanctl.conf is the modern way to configure it
so that's what I did.
But now after every boot I have to run 'swanctl --load-all' to be able
to be able to authenticate with the VPN. I found a slightly related
Stack Exchange post[1] which talks about charon-systemd vs.
starter/chron and to be honest it's not quite clear to me what these
different parts are supposed to do.
These are the strongswan and charon packages I have installed:
charon-systemd
libcharon-extra-plugins
libstrongswan
libstrongswan-extra-plugins
libstrongswan-standard-plugins
strongswan-charon
strongswan-libcharon
strongswan-starter
strongswan-swanctl
So it looks like *both* the starter and charon-systemd are installed.
But when I remove the starter the service doesn't seem to work at all -
I can't initiate IPsec connections to the machine then.
There is of course the StrongSwan documentation but it didn't help me
in this aspect.
Any ideas?
Thanks,
Sijmen Mulder
1:
https://unix.stackexchange.com/questions/557032/how-to-start-a-swanctl-conf-configured-tunnel-automatically
Re: Return a Debian system to a pristine state
Marco Möller wrote: > > In the fairly large number of posts in this thread I don't recall seeing > > file system snapshots suggested. My current preference is ZFS, which I > > know from experience to be up to what I understand to be the goal here. > > (...) > I understand the OP to be in search for the uncomplicated removal of > installed packages considering package installation dates. > A fs snaphot tool is likely to return to a general system state which > would include also the return of the user data and system configurations > to a point of time in the past, instead of only treating package > installs. And if having to prepare sophisticated steps like requiring > special partitioning schemes, then this wouldn't be uncomplicated anymore. Agreed, but at risk of going a bit off track, I didn't find this to be a problem in practice on ZFS native systems like SmartOS. Separate volume on /usr/pkg, snapshot, done. Of course the situation in Debian is a bit different. Sijmen
Re: Return a Debian system to a pristine state
Victor Sudakov wrote: > A production system, especially a desktop system, tends to accumulate > unnecessary packages. Users install software for testing, then forget > about it, or it falls into disuse... > > In FreeBSD, you can always run "pkg delete -a" and return to the > post-install state (well, almost). This command will remove all the > third-party packages added to the base system after installation > (modified files under /usr/local/ will remain). > > What's the procedure for Debian? It helps to only look installed packages marked automatic but lots of system programs and libraries are marked as such. I'd expect a 'base' metapackage of some sort... ...which ties into the remark made a few times in this thread which is that there is no singular set of base packages. But then at least have tasksel do something like that. Admittedly I just don't know a lot about Debian packages but as a user I have the same concern as Victor. Sijmen
