Re: [gentoo-user] Is sys-firmware/intel-microcode-20180108 complete?
> It looks as though my CPU hasn't been fixed yet. Is that right? It seems that patches are being pushed out as they are being received, so back when that one was released, no other updates were available. See https://bugs.gentoo.org/643430#c10 We should get the full range of updates in the next few days. -- Wolfgang Mueller / vehk.de / GPG 0xc543cfce9465f573 signature.asc Description: PGP signature
Re: [gentoo-user] Bringing mdocml to Gentoo, MANPATH woes
On Wed, Jan 04, 2017 at 16:32:02 +0100, Joerg Schilling wrote: > If you think about replacing "man" by "mandoc", please keep in mind that > "mandoc" displays many of the man pages incorrectly. > > This is caused by the fact that tables are not correctly understood by mandoc. Could you give me some example man pages for this? All tables I have found so far (about one or two, since I don't know exactly where to look) display correctly for me in mandoc. In any case, I was not aware of this, so thanks for mentioning. -- Wolfgang Mueller / vehk.de / GPG 0xc543cfce9465f573 signature.asc Description: PGP signature
Re: [gentoo-user] Bringing mdocml to Gentoo, MANPATH woes
> Try the -dev list for the MANPATH thing. Shall do that. > I think "cron" might be a better global USE flag than "sqlite". Users > will think "oh, of course I want the apropos/whatis database to be > updated nightly" with USE=cron. Unless they happen to know that those > databases are implemented in sqlite, they'll probably just guess at the > meaning of USE=sqlite. Good point. I have the USE description in metadata.xml, but even there did not comment that cron scripts would be installed. Not sure whether to call it cron, because users would assume it would only install the cron script and not need sqlite for database generation. > I would also suggest dropping the "+" defaults unless doing so severely > cripples the package. The whole point of USE flags is that I can set > them and all ebuilds will use them -- that stops working if developers > make their own preferences default in ebuilds. I thought about dropping the default for sqlite, and will probably do so. As for manpager: it has + even in man-db, so I thought it would be best to keep that consistent. > [snip] > This might be more appropriate in pkg_config(), because it modifies a > file that doesn't belong to the package manager, namely mandoc.db. That > could also solve your MANPATH issue by dumb luck; I'm not sure what the > environment will look like during emerge --config. I will try that out, thanks very much for the suggestions/fixes. -- Wolfgang Mueller / vehk.de / GPG 0xc543cfce9465f573 signature.asc Description: PGP signature
[gentoo-user] Bringing mdocml to Gentoo, MANPATH woes
Hello, list. For the past few days I have been working on bringing mdocml to Gentoo as a full alternative to man-db. In the course of writing the ebuild, I have come across some issues on which I would like to have some comments: 1. When submitting the ebuild through bugzilla, is it enough to note that virtual/man would need changes to reflect that mdocml satisfies it, or does that warrant a new bug (with depedency on the ebuild)? 2. I have asked about the next questions on freenode's #gentoo-dev-help channel already, but got no answer: What is the reasoning to suppress the MANPATH environment variable in ebuilds? Updating/creating the mandoc database in pkg_postinst will only pick up /usr/share/man, and fully ignore the gcc and binutils manpages that are correctly set in MANPATH. This also happens to man-db, which means that the manpages gcc and binutils bring will *never* show up in apropos or man -k. I'd be glad to open a bug about this, but wanted first to know if this is actually a feature. Note that MANPATH is also not set in the cron.daily script that man-db brings. You can easily verify this bug like so: $ man fsf-funding # this will correctly display the fsf-funding manpage $ apropos fsf # this will find fsfreeze/etc, but *not* fsf-funding On my testing system that has mdocml set up (and the correct paths fed into makewhatis), apropos indeed finds fsf-funding. I have not tested this with man-db yet, but I would assume that sourcing the environment or somehow setting MANPATH in the ebuild and the cron script would fix this and add the corresponding manpages to the man-db database. And with this, we come to... 3. What would be the best way to set the MANPATH in the ebuild and the cron script? It seems to me that sourcing /etc/profile in the ebuild's pkg_postinst is a terrible hack, and in my current ebuild (see end of this mail) I resolved to just let it run on /usr/share/man and to then alert the user. My cron.daily script indeed sources /etc/profile before running makewhatis. I post this on the -user list because it seems to me that I have issues relating to several distinct components. If this is better discussed somewhere else, I would appreciate some pointers :) You can find the ebuild (and corresponding files) here: https://github.com/vehk/pramantha/tree/mdocml-wip/sys-apps/mdocml -- Wolfgang Mueller / vehk.de / GPG 0xc543cfce9465f573 signature.asc Description: PGP signature
Re: [gentoo-user] anyone using postfix 3.0.0
Is anyone running it? I built it on a test machine but it doesn't seem to work. However, I don't use that machine much (and never for mail) so it is very possibly mis-configured for mail. Before I build the new postscript for my real machine I would like to hear that those postscript users on this list are not having problems. I updated to postfix 3.0 three hours ago on my production server - no problems whatsoever. No changes to main.cf or any other configuration file are needed (you may want to add `compatibility_level = x' as per: http://www.postfix.org/COMPATIBILITY_README.html, though). For changes, see http://www.postfix.org/announcements/postfix-3.0.0.html -- Wolfgang Mueller / vehk.de / 0xc543cfce9465f573 Ed is the standard text editor. signature.asc Description: PGP signature
Re: [gentoo-user] anyone using postfix 3.0.0
On Wed, Mar 25, 2015 at 22:34:10 -0400, gottl...@nyu.edu wrote:
Then I run for a while, check the logs and issue the appropriate
postconf commands.
Yes, exactly.
You can also manually go through the settings mentioned in the
Overview section of COMPATIBILITY_README, to see if anything needs
changing in main.cf/master.cf. That's what I did.
Not so clear is when do you turn off backwards compatibility (i.e. set
the level). Does postfix determine the level right away or should I let
it run for a few weeks so it sees a lot of mail?
The documentation is not clear on this, but I don't think there's any
kind of logic behind the compatibility level postfix mentions in its
log - it's just the hard-coded version specifier, the most recent
compatibility level.
You can turn off the safety net once you made sure that postfix is
configured the way you want; that is, once you made sure that no more
backwards-compatible default settings would need to be made permanent.
For example, relay_domains used to default to $mydestination. With
postfix 3.0.0, it defaults to:
relay_domains = ${{$compatibility_level} {2} ? {$mydestination} : {}}
If you rely on the default setting of relay_domains (i.e. you don't set
it explicitly in main.cf) you may need to change it now.
--
Wolfgang Mueller / vehk.de / 0xc543cfce9465f573
Ed is the standard text editor.
signature.asc
Description: PGP signature
Re: [gentoo-user] why you've chosen your desktop environment? (no war !)
Thanks for the reminder ! -- I do indeed have Mupdf installed, but had forgotten all about it : yes, it's quick easy for simple browsing. Evince has extra features, eg a side menu, but mb Mupdf is sufficient. If you're looking for a more feature-complete solution, check out llpp[1], which is based on mupdf. As a long time zathura user that switched to to mupdf because zathura's newest version now depends on =x11-libs/gtk+-3.2:3, I found that mupdf had a few limitations and annoyances. I'm quite happy with llpp now and wouldn't want to go back. [1] - http://repo.or.cz/w/llpp.git -- Wolfgang Mueller / vehk.de / 0xc543cfce9465f573 That gum you like is going to come back in style. signature.asc Description: Digital signature
