Update x11-wm/vtwm to the recently released 5.5.0-rc7. This new release features new png support, plus some new keywords in the rc file. Despite the "release candidate" tag, it appears to be quite stable, and is a very worthwhile upgrade. Some of the new keywords are quite useful (the "Immutable" keyword in particular). Note to maintainer: the patches of the "sprintf" statements in util.c needed correcting (removing both the comma and the "star"), and since the package now includes a configure script, the Makefile.bsd you had in the files directory is no longer necessary. I also removed the pkg-plist file and just added the files to PLIST_FILES in the Makefile. Incidentally, if you'd like me to take over as the port's maintainer, just let me know. Fix: patch below How-To-Repeat: N/A
Responsible Changed From-To: freebsd-ports-bugs->ak Over to maintainer (via the GNATS Auto Assign Tool)
On Sat, Mar 10, 2012 at 11:42:44PM -0600, Conrad J. Sabatier wrote: > > >Description: > Update x11-wm/vtwm to the recently released 5.5.0-rc7. > This new release features new png support, plus some new > keywords in the rc file. Despite the "release > candidate" tag, it appears to be quite stable, and is a > very worthwhile upgrade. Some of the new keywords are > quite useful (the "Immutable" keyword in particular). > > Note to maintainer: the patches of the "sprintf" > statements in util.c needed correcting (removing both > the comma and the "star"), and since the package now > includes a configure script, the Makefile.bsd you had > in the files directory is no longer necessary. I also > removed the pkg-plist file and just added the files to > PLIST_FILES in the Makefile. Thanks for your hard work. Please check next version of update. I commented only key changes so please ask if You don't understand something: - this is not 5.5.0rc7, which was released 2011-02-26, but snapshot, so I added DATESTAMP - s/HAS_CONFIGURE/GNU_CONFIGURE/, vtwm uses autotools now. - use REINPLACE instead of patch-Makefile.in, You need to change only datadir line, configure will set up all others. - add patch-sound.c It's a bug in vtwm code, I will contact upstream. - The '*' in patch-util.c still needed, because we want to return success on partial matches i.e. not only on -*-*-medium-r-normal-*-15-*-*-*-p-*-iso10646-1 but also on -*-*-medium-r-normal-*-*-*-*-*-*-*-*-* aka -*-*-medium-r-normal* -- Adios
On Sun, 11 Mar 2012 12:51:30 +0200 Alex Kozlov <spam@rm-rf.kiev.ua> wrote: > On Sat, Mar 10, 2012 at 11:42:44PM -0600, Conrad J. Sabatier wrote: > > > > >Description: > > Update x11-wm/vtwm to the recently released > > 5.5.0-rc7. This new release features new png support, plus some new > > keywords in the rc file. Despite the "release > > candidate" tag, it appears to be quite stable, and > > is a very worthwhile upgrade. Some of the new keywords are > > quite useful (the "Immutable" keyword in > > particular). > > > > Note to maintainer: the patches of the "sprintf" > > statements in util.c needed correcting (removing > > both the comma and the "star"), and since the package now > > includes a configure script, the Makefile.bsd you > > had in the files directory is no longer necessary. I also > > removed the pkg-plist file and just added the files > > to PLIST_FILES in the Makefile. > Thanks for your hard work. Please check next version of update. > I commented only key changes so please ask if You don't understand > something: > - this is not 5.5.0rc7, which was released 2011-02-26, but snapshot, > so I added DATESTAMP > - s/HAS_CONFIGURE/GNU_CONFIGURE/, vtwm uses autotools now. > - use REINPLACE instead of patch-Makefile.in, You need to change only > datadir line, configure will set up all others. > - add patch-sound.c It's a bug in vtwm code, I will contact upstream. > - The '*' in patch-util.c still needed, because we want to return > success on partial matches i.e. not only on > -*-*-medium-r-normal-*-15-*-*-*-p-*-iso10646-1 but also on > -*-*-medium-r-normal-*-*-*-*-*-*-*-*-* aka -*-*-medium-r-normal* OK, I think I understand all of the above. I'm just really puzzled, though, as to what those commas were doing up in there in the first place. I can't imagine how anyone could have gotten the program to work with them. When I tried to use the unpatched source, vtwm exited immediately with a bunch of error messages re: missing fonts. So, I followed your lead and patched util.c to remove the commas. Still the fonts weren't being found. It wasn't until I removed both the commas *and* the asterisks that I was able to get vtwm to start up. What am I not getting here? Anyway, thanks for such a quick followup on this. I've really been enjoying using vtwm this last week or so, since trying out the new version and spending a bit of time tweaking my .vtwmrc, adding a set of desktop "doors" at the bottom-left corner (this was where the new "Immutable" setting really came in handy; I use it on both my set of doors and the panner, so they won't be moved or otherwise altered accidentally), and playing with some of the other variables to get things more to my tastes. This is really a rather nice window manager; lightweight, unobtrusive and flexible. I wanted to do a little more with the port, such as installing some of the stuff from the contrib directory, but I was getting tired after working on the computer all day, so I took a shortcut. :-) I did have the port installing the nexpm program, which is a handy little tool for setting the background of the desktop panner (and other windows as well, even the root). I think it would be nice to include the README file for nexpm, and also the contrib/vtwmrc directory. But I'll leave that to you. :-) Regards, Conrad -- Conrad J. Sabatier conrads@cox.net
On Sun, Mar 11, 2012 at 07:12:42AM -0500, Conrad J. Sabatier wrote: > On Sun, 11 Mar 2012 12:51:30 +0200 > Alex Kozlov <spam@rm-rf.kiev.ua> wrote: > > On Sat, Mar 10, 2012 at 11:42:44PM -0600, Conrad J. Sabatier wrote: > > > > > > >Description: > > > Update x11-wm/vtwm to the recently released > > > 5.5.0-rc7. This new release features new png support, plus some new > > > keywords in the rc file. Despite the "release > > > candidate" tag, it appears to be quite stable, and > > > is a very worthwhile upgrade. Some of the new keywords are > > > quite useful (the "Immutable" keyword in > > > particular). > > > > > > Note to maintainer: the patches of the "sprintf" > > > statements in util.c needed correcting (removing > > > both the comma and the "star"), and since the package now > > > includes a configure script, the Makefile.bsd you > > > had in the files directory is no longer necessary. I also > > > removed the pkg-plist file and just added the files > > > to PLIST_FILES in the Makefile. > > Thanks for your hard work. Please check next version of update. > > I commented only key changes so please ask if You don't understand > > something: > > - this is not 5.5.0rc7, which was released 2011-02-26, but snapshot, > > so I added DATESTAMP > > - s/HAS_CONFIGURE/GNU_CONFIGURE/, vtwm uses autotools now. > > - use REINPLACE instead of patch-Makefile.in, You need to change only > > datadir line, configure will set up all others. > > - add patch-sound.c It's a bug in vtwm code, I will contact upstream. > > - The '*' in patch-util.c still needed, because we want to return > > success on partial matches i.e. not only on > > -*-*-medium-r-normal-*-15-*-*-*-p-*-iso10646-1 but also on > > -*-*-medium-r-normal-*-*-*-*-*-*-*-*-* aka -*-*-medium-r-normal* > OK, I think I understand all of the above. I'm just really puzzled, > though, as to what those commas were doing up in there in the first > place. I can't imagine how anyone could have gotten the program to > work with them. It's should work, because XCreateFontSet accepts list of fonts, so ',*' is actually -*-*-*-*-*-*-*-*-*-*-*-*-*-* > When I tried to use the unpatched source, vtwm exited > immediately with a bunch of error messages re: missing fonts. Something strange here. In vanilla vtwm should exit with missing fonts error only if there are no fonts installed at all. Can You show your installed fonts list and exact error? > So, I followed your lead and patched util.c to remove the commas. > Still the fonts weren't being found. It wasn't until I removed both > the commas *and* the asterisks that I was able to get vtwm to start > up. What am I not getting here? Original problem that I tried to solve is a slow startup in case if XCreateFontSet don't find match for basename font. Because of fallback to -*-*-*-*-*-*-*-*-*-*-*-*-*-* XCreateFontSet searches in entire fonts namespace and in case of modulare X11R7, when some fonts families can be missing, it's means tens of seconds delay. -- Adios
On Sun, 11 Mar 2012 15:38:23 +0200 Alex Kozlov <spam@rm-rf.kiev.ua> wrote: > On Sun, Mar 11, 2012 at 07:12:42AM -0500, Conrad J. Sabatier wrote: > > On Sun, 11 Mar 2012 12:51:30 +0200 > > Alex Kozlov <spam@rm-rf.kiev.ua> wrote: > > > > > > - The '*' in patch-util.c still needed, because we want to return > > > success on partial matches i.e. not only on > > > -*-*-medium-r-normal-*-15-*-*-*-p-*-iso10646-1 but also on > > > -*-*-medium-r-normal-*-*-*-*-*-*-*-*-* aka -*-*-medium-r-normal* > > OK, I think I understand all of the above. I'm just really puzzled, > > though, as to what those commas were doing up in there in the first > > place. I can't imagine how anyone could have gotten the program to > > work with them. > It's should work, because XCreateFontSet accepts list of fonts, so > ',*' is actually -*-*-*-*-*-*-*-*-*-*-*-*-*-* I thought that might be the case, but wasn't really sure. > > When I tried to use the unpatched source, vtwm exited > > immediately with a bunch of error messages re: missing fonts. > Something strange here. In vanilla vtwm should exit with missing fonts > error only if there are no fonts installed at all. > Can You show your installed fonts list and exact error? Well, I would have to go back and install from the unpatched source again. What I saw was just a series of "lacking font" messages. Sorry, they've already been overwritten now in my .xsession-errors file. Could this possibly be an indicator of bad or missing fonts.dir files or a bad fonts cache? Not sure that my current X installation is totally up to snuff at the moment. I was doing a lot of experimenting for a while with bleeding edge versions of various components, some from the FreeBSD xorg-devel repo, and some versions even beyond those that I installed on my own. I've only just recently started reverting back to the current versions in ports. So it's quite possible something is messed up somewhere here. :-) > > So, I followed your lead and patched util.c to remove the commas. > > Still the fonts weren't being found. It wasn't until I removed both > > the commas *and* the asterisks that I was able to get vtwm to start > > up. What am I not getting here? > Original problem that I tried to solve is a slow startup in case > if XCreateFontSet don't find match for basename font. > Because of fallback to -*-*-*-*-*-*-*-*-*-*-*-*-*-* XCreateFontSet > searches in entire fonts namespace and in case of modulare X11R7, > when some fonts families can be missing, it's means tens of seconds > delay. I see. Makes a lot of sense. Sorry I tried to undo your earlier work. Didn't fully appreciate what was going on there. So, how do you feel about my earlier suggestion re: the contrib stuff? I think it would be a great help, especially for newcomers to vtwm, to have the vtwmrc directory available under ${SHAREDIR}/vtwm, don't you? Would add a lot of "value" to the package, I think. :-) Thanks for all the communication, Conrad -- Conrad J. Sabatier conrads@cox.net
On Sun, Mar 11, 2012 at 09:29:03AM -0500, Conrad J. Sabatier wrote: > On Sun, 11 Mar 2012 15:38:23 +0200 > Alex Kozlov <spam@rm-rf.kiev.ua> wrote: > > On Sun, Mar 11, 2012 at 07:12:42AM -0500, Conrad J. Sabatier wrote: > > > On Sun, 11 Mar 2012 12:51:30 +0200 > > > > > > When I tried to use the unpatched source, vtwm exited > > > immediately with a bunch of error messages re: missing fonts. > > Something strange here. In vanilla vtwm should exit with missing fonts > > error only if there are no fonts installed at all. > > Can You show your installed fonts list and exact error? > Well, I would have to go back and install from the unpatched source > again. What I saw was just a series of "lacking font" messages. Sorry, > they've already been overwritten now in my .xsession-errors file. It would be great to know what's going on here, so if you have time please check it out. > Could this possibly be an indicator of bad or missing fonts.dir files > or a bad fonts cache? Yes, it's possible. You can use x11-fonts/xfontsel to check this. > Not sure that my current X installation is > totally up to snuff at the moment. I was doing a lot of experimenting > for a while with bleeding edge versions of various components, some > from the FreeBSD xorg-devel repo, and some versions even beyond those > that I installed on my own. I've only just recently started reverting > back to the current versions in ports. So it's quite possible something > is messed up somewhere here. :-) Personally, I always create a separate PREFIX for the experiments: cp -Rp $prefix $newprefix cp -Rp $pkgdb $newpkgdb cp -Rp $portdb $newportdb export PREFIX=$newprefix export LOCALBASE=$newprefix export PKG_DBDIR=$newpkgdb export PORT_DBDIR=$newportdb > > > So, I followed your lead and patched util.c to remove the commas. > > > Still the fonts weren't being found. It wasn't until I removed both > > > the commas *and* the asterisks that I was able to get vtwm to start > > > up. What am I not getting here? > > Original problem that I tried to solve is a slow startup in case > > if XCreateFontSet don't find match for basename font. > > Because of fallback to -*-*-*-*-*-*-*-*-*-*-*-*-*-* XCreateFontSet > > searches in entire fonts namespace and in case of modulare X11R7, > > when some fonts families can be missing, it's means tens of seconds > > delay. > I see. Makes a lot of sense. Sorry I tried to undo your earlier > work. Didn't fully appreciate what was going on there. No problem. Your patch is also ok, just more strict. > So, how do you feel about my earlier suggestion re: the contrib stuff? > I think it would be a great help, especially for newcomers to vtwm, to > have the vtwmrc directory available under ${SHAREDIR}/vtwm, don't you? > Would add a lot of "value" to the package, I think. :-) Don't worry, I haven't forgotten about this, I just need a little time to check this contrib. I will reply soon. -- Adios
On Sun, 11 Mar 2012 17:21:05 +0200 Alex Kozlov <spam@rm-rf.kiev.ua> wrote: > On Sun, Mar 11, 2012 at 09:29:03AM -0500, Conrad J. Sabatier wrote: > > On Sun, 11 Mar 2012 15:38:23 +0200 > > Alex Kozlov <spam@rm-rf.kiev.ua> wrote: > > > On Sun, Mar 11, 2012 at 07:12:42AM -0500, Conrad J. Sabatier > > > wrote: > > > > On Sun, 11 Mar 2012 12:51:30 +0200 > > > > > > > > When I tried to use the unpatched source, vtwm exited > > > > immediately with a bunch of error messages re: missing fonts. > > > Something strange here. In vanilla vtwm should exit with missing > > > fonts error only if there are no fonts installed at all. > > > Can You show your installed fonts list and exact error? > > Well, I would have to go back and install from the unpatched source > > again. What I saw was just a series of "lacking font" messages. > > Sorry, they've already been overwritten now in my .xsession-errors > > file. > It would be great to know what's going on here, so if you have time > please check it out. I'll try to get to that later today. Been up all night working on various things (vtwm included), and am just too dog-tired at the moment. :-) > > Could this possibly be an indicator of bad or missing fonts.dir > > files or a bad fonts cache? > Yes, it's possible. You can use x11-fonts/xfontsel to check this. I'm seeing indicators of a generalized font issue here from other programs as well. Working on straightening it out now. > > Not sure that my current X installation is > > totally up to snuff at the moment. I was doing a lot of > > experimenting for a while with bleeding edge versions of various > > components, some from the FreeBSD xorg-devel repo, and some > > versions even beyond those that I installed on my own. I've only > > just recently started reverting back to the current versions in > > ports. So it's quite possible something is messed up somewhere > > here. :-) > Personally, I always create a separate PREFIX for the experiments: > cp -Rp $prefix $newprefix > cp -Rp $pkgdb $newpkgdb > cp -Rp $portdb $newportdb > export PREFIX=$newprefix > export LOCALBASE=$newprefix > export PKG_DBDIR=$newpkgdb > export PORT_DBDIR=$newportdb Yes, I really do need to start practicing a more conscientious approach to experimenting with ports. Mostly been lucky so far, and haven't shot myself in the foot yet, but why risk it needlessly? Experience has shown that it pays to be methodical and consistent, and saves a great deal of time in the long run, for only a minor extra investment in the beginning. > > > > So, I followed your lead and patched util.c to remove the > > > > commas. Still the fonts weren't being found. It wasn't until I > > > > removed both the commas *and* the asterisks that I was able to > > > > get vtwm to start up. What am I not getting here? > > > Original problem that I tried to solve is a slow startup in case > > > if XCreateFontSet don't find match for basename font. > > > Because of fallback to -*-*-*-*-*-*-*-*-*-*-*-*-*-* > > > XCreateFontSet searches in entire fonts namespace and in case of > > > modulare X11R7, when some fonts families can be missing, it's > > > means tens of seconds delay. > > I see. Makes a lot of sense. Sorry I tried to undo your earlier > > work. Didn't fully appreciate what was going on there. > No problem. Your patch is also ok, just more strict. Yes, I can be somewhat of a stickler at times. :-) > > So, how do you feel about my earlier suggestion re: the contrib > > stuff? I think it would be a great help, especially for newcomers > > to vtwm, to have the vtwmrc directory available under > > ${SHAREDIR}/vtwm, don't you? Would add a lot of "value" to the > > package, I think. :-) > Don't worry, I haven't forgotten about this, I just need a little time > to check this contrib. I will reply soon. Cool. Take your time. No big rush on that. Thanks! It's nice to encounter a fellow port maintainer who's so responsive and interested. Catch up with you later (after a nice long nap!), Conrad -- Conrad J. Sabatier conrads@cox.net
Alex, I tried sending you a mail just now, and got this back (I'll mail postmaster@cox.net to let them know they need to support the VRFY command): Reporting-MTA: dns; eastrmfepo202.cox.net Arrival-Date: Mon, 12 Mar 2012 12:25:46 -0400 Received-From-MTA: dns; eastrmimpo109.cox.net (68.230.241.222) Final-Recipient: RFC822; <spam@rm-rf.kiev.ua> Action: failed Status: 5.1.1 Remote-MTA: dns; rm-rf.kiev.ua (94.244.131.95) Diagnostic-Code: smtp; 550-Callback setup failed while verifying <conrads@cox.net> 550-(result of an earlier callout reused). 550-The initial connection, or a HELO or MAIL FROM:<> command was 550-rejected. Refusing MAIL FROM:<> does not help fight spam, disregards 550-RFC requirements, and stops you from receiving standard bounce 550-messages. This host does not accept mail from domains whose servers 550-refuse bounces. 550 Sender verify failed [ This was the message I sent ] OK, now I'm *really* confused. Yesterday, I reinstalled all of my xorg ports, including fonts and font utils. This eliminated some runtime errors re: fonts that I was seeing not only from vtwm, but also from some other packages. This morning, I started testing running vtwm and capturing the error messages. Oddly, none of the "font is lacking" messages were appearing anymore, but I was still seeing "Couldn't load font "fixed" or "fixed". vtwm would shutdown on startup. So, I went into the port and fiddled with the patch-util.c patch some more. It wasn't until I totally disabled the patch and used util.c "as is" that vtwm finally started up, and with no error messages at all. Could it be that we should just leave util.c alone and not patch it? -- Conrad J. Sabatier conrads@cox.net
On Mon, Mar 12, 2012 at 05:00:37PM +0000, Conrad J. Sabatier wrote: > The following reply was made to PR ports/165913; it has been noted by GNATS. > > From: "Conrad J. Sabatier" <conrads@cox.net> > To: Alex Kozlov <spam@rm-rf.kiev.ua> > Cc: bug-followup@FreeBSD.org > Subject: Re: ports/165913: [patch] x11-wm/vtwm: update to 5.5.0-rc7 > Date: Mon, 12 Mar 2012 11:50:57 -0500 > > Alex, > > I tried sending you a mail just now, and got this back (I'll mail > postmaster@cox.net to let them know they need to support the VRFY > command): > > Reporting-MTA: dns; eastrmfepo202.cox.net > Arrival-Date: Mon, 12 Mar 2012 12:25:46 -0400 > Received-From-MTA: dns; eastrmimpo109.cox.net (68.230.241.222) > > Final-Recipient: RFC822; <spam@rm-rf.kiev.ua> > Action: failed > Status: 5.1.1 > Remote-MTA: dns; rm-rf.kiev.ua (94.244.131.95) > Diagnostic-Code: smtp; 550-Callback setup failed while verifying > <conrads@cox.net> > 550-(result of an earlier callout reused). > 550-The initial connection, or a HELO or MAIL FROM:<> command was > 550-rejected. Refusing MAIL FROM:<> does not help fight spam, > disregards > 550-RFC requirements, and stops you from receiving standard bounce > 550-messages. This host does not accept mail from domains whose servers > 550-refuse bounces. > 550 Sender verify failed > > [ This was the message I sent ] > OK, now I'm *really* confused. Your MTA opened smtp session to my MTA. My MTA tried to verify your address by opening smtp session to your MTA with MAIL FROM:<> (it's reserved for robots) but your MTA don't accepts MAIL FROM:<> 2012-03-12 18:13:40 H=eastrmfepo202.cox.net [68.230.241.217] sender verify fail for <conrads@cox.net>: response to "MAIL FROM:<>" from mx.east.cox.net [68.1.17.3] was: 550 5.1.0 <> sender rejected - Refer to Error Codes section at http://postmaster.cox.net/confluence/display/postmaster/Error+Codes for more information. 2012-03-12 18:13:40 H=eastrmfepo202.cox.net [68.230.241.217] F=<conrads@cox.net> rejected RCPT <spam@rm-rf.kiev.ua>: Sender verify failed Therefore sender verify failed and my MTA rejects your mail. > Yesterday, I reinstalled all of my xorg ports, including fonts and font > utils. This eliminated some runtime errors re: fonts that I was seeing > not only from vtwm, but also from some other packages. > > This morning, I started testing running vtwm and capturing the error > messages. Oddly, none of the "font is lacking" messages were appearing > anymore, but I was still seeing "Couldn't load font "fixed" or "fixed". > vtwm would shutdown on startup. > > So, I went into the port and fiddled with the patch-util.c patch some > more. It wasn't until I totally disabled the patch and used util.c "as > is" that vtwm finally started up, and with no error messages at all. > > Could it be that we should just leave util.c alone and not patch it? I don't think so. basename,* just masked the problem, your fixed font was never found and XCreateFontSet fallback to * aka -*-*-*-*-*-*-*-*-*-*-*-*-*-* and accepts first given font. Can You please show your .vtwmrc? p.s. I checked vtwm's contrib directory and think that I can add it to the port as an option. Is it ok with You? -- Adios
Begin forwarded message: Date: Mon, 12 Mar 2012 12:58:20 -0500 From: "Conrad J. Sabatier" <conrads@cox.net> To: Alex Kozlov <spam@rm-rf.kiev.ua> Subject: Re: ports/165913: [patch] x11-wm/vtwm: update to 5.5.0-rc7 On Mon, 12 Mar 2012 19:35:11 +0200 Alex Kozlov <spam@rm-rf.kiev.ua> wrote: > On Mon, Mar 12, 2012 at 05:00:37PM +0000, Conrad J. Sabatier wrote: > > The following reply was made to PR ports/165913; it has been noted > > by GNATS. > > > > From: "Conrad J. Sabatier" <conrads@cox.net> > > To: Alex Kozlov <spam@rm-rf.kiev.ua> > > Cc: bug-followup@FreeBSD.org > > Subject: Re: ports/165913: [patch] x11-wm/vtwm: update to 5.5.0-rc7 > > Date: Mon, 12 Mar 2012 11:50:57 -0500 > > > > Alex, > > > > I tried sending you a mail just now, and got this back (I'll mail > > postmaster@cox.net to let them know they need to support the VRFY > > command): > > > > Reporting-MTA: dns; eastrmfepo202.cox.net > > Arrival-Date: Mon, 12 Mar 2012 12:25:46 -0400 > > Received-From-MTA: dns; eastrmimpo109.cox.net (68.230.241.222) > > > > Final-Recipient: RFC822; <spam@rm-rf.kiev.ua> > > Action: failed > > Status: 5.1.1 > > Remote-MTA: dns; rm-rf.kiev.ua (94.244.131.95) > > Diagnostic-Code: smtp; 550-Callback setup failed while verifying > > <conrads@cox.net> > > 550-(result of an earlier callout reused). > > 550-The initial connection, or a HELO or MAIL FROM:<> command was > > 550-rejected. Refusing MAIL FROM:<> does not help fight spam, > > disregards > > 550-RFC requirements, and stops you from receiving standard bounce > > 550-messages. This host does not accept mail from domains whose > > servers 550-refuse bounces. > > 550 Sender verify failed > > > > [ This was the message I sent ] > > OK, now I'm *really* confused. > Your MTA opened smtp session to my MTA. My MTA tried to verify your > address by opening smtp session to your MTA with MAIL FROM:<> (it's > reserved for robots) but your MTA don't accepts MAIL FROM:<> > > 2012-03-12 18:13:40 H=eastrmfepo202.cox.net [68.230.241.217] sender > verify fail for <conrads@cox.net>: response to "MAIL FROM:<>" from > mx.east.cox.net [68.1.17.3] was: 550 5.1.0 <> sender rejected - Refer > to Error Codes section at > http://postmaster.cox.net/confluence/display/postmaster/Error+Codes > for more information. 2012-03-12 18:13:40 H=eastrmfepo202.cox.net > [68.230.241.217] F=<conrads@cox.net> rejected RCPT > <spam@rm-rf.kiev.ua>: Sender verify failed > > Therefore sender verify failed and my MTA rejects your mail. Yes, exactly. I doubt that Cox will be very responsive in correct this, though. Annoying! > > Yesterday, I reinstalled all of my xorg ports, including fonts and > > font utils. This eliminated some runtime errors re: fonts that I > > was seeing not only from vtwm, but also from some other packages. > > > > This morning, I started testing running vtwm and capturing the > > error messages. Oddly, none of the "font is lacking" messages were > > appearing anymore, but I was still seeing "Couldn't load font > > "fixed" or "fixed". vtwm would shutdown on startup. > > > > So, I went into the port and fiddled with the patch-util.c patch > > some more. It wasn't until I totally disabled the patch and used > > util.c "as is" that vtwm finally started up, and with no error > > messages at all. > > Could it be that we should just leave util.c alone and not patch > > it? > I don't think so. basename,* just masked the problem, your fixed font > was never found and XCreateFontSet fallback to * aka > -*-*-*-*-*-*-*-*-*-*-*-*-*-* and accepts first given font. > Can You please show your .vtwmrc? > > > p.s. I checked vtwm's contrib directory and think that I can add it > to the port as an option. Is it ok with You? Sure, that would be great. I've attached my current .vtwmrc. I was fiddling with the fonts settings in it yesterday, but never really finished up with it. P.S. Is my mail reaching your address? Or did you see this on the website? -- Conrad J. Sabatier conrads@cox.net -- Conrad J. Sabatier conrads@cox.net
Author: ak Date: Mon Dec 9 12:32:44 2013 New Revision: 335974 URL: http://svnweb.freebsd.org/changeset/ports/335974 Log: - Update to 20130906 snapshot [1] - Use options helpers - Remove NLS knob, now it's runtime option PR: ports/165913 (based on) [1] Submitted by: Conrad J. Sabatier <conrads@cox.net> [1] Deleted: head/x11-wm/vtwm/files/ Modified: head/x11-wm/vtwm/Makefile head/x11-wm/vtwm/distinfo (contents, props changed) Modified: head/x11-wm/vtwm/Makefile ============================================================================== --- head/x11-wm/vtwm/Makefile Mon Dec 9 12:18:28 2013 (r335973) +++ head/x11-wm/vtwm/Makefile Mon Dec 9 12:32:44 2013 (r335974) @@ -2,39 +2,39 @@ # $FreeBSD$ PORTNAME= vtwm -PORTVERSION= 5.4.7 -PORTREVISION= 4 +PORTVERSION= 5.4.99.20130906 CATEGORIES= x11-wm -MASTER_SITES= SF http://www.vtwm.org/downloads/ +MASTER_SITES= ${MASTER_SITE_GOOGLE_CODE} +PROJECTHOST= ak-various-projects MAINTAINER= ak@FreeBSD.org COMMENT= Twm with a virtual desktop and optional Motif-like features LICENSE= MIT -USE_XORG= x11 xext xpm xmu -MAKEFILE= ${FILESDIR}/Makefile.bsd +LIB_DEPENDS= libpng.so:${PORTSDIR}/graphics/png -ETCDIR?= ${PREFIX}/etc +USE_XZ= yes + +USES= pkgconfig + +GNU_CONFIGURE= yes +USE_XORG= x11 xext xft xinerama xpm xmu xrandr + +WRKSRC= ${WRKDIR}/vtwm-20130906 PLIST_FILES= bin/vtwm \ + bin/nexpm \ etc/system.vtwmrc \ man/man1/vtwm.1.gz -OPTIONS_DEFINE= SOUND NLS -OPTIONS_DEFAULT= SOUND NLS +OPTIONS_DEFINE= SOUND +SOUND_DESC= Sound support (via rplay) -.include <bsd.port.options.mk> +SOUND_CONFIGURE_ENABLE= sound +SOUND_LIB_DEPENDS= librplay.so:${PORTSDIR}/audio/rplay -.if ${PORT_OPTIONS:MSOUND} -LIB_DEPENDS+= librplay.so:${PORTSDIR}/audio/rplay -MAKE_ENV+= SOUND=yes -.else -MAKE_ENV+= SOUND=no -.endif - -.if ! ${PORT_OPTIONS:MNLS} -CFLAGS+= -DNO_I18N_SUPPORT -.endif +pre-patch: + @${REINPLACE_CMD} -e 's|\$${datadir}/X11/vtwm|\$${prefix}/etc|' ${WRKSRC}/Makefile.in .include <bsd.port.mk> Modified: head/x11-wm/vtwm/distinfo ============================================================================== --- head/x11-wm/vtwm/distinfo Mon Dec 9 12:18:28 2013 (r335973) +++ head/x11-wm/vtwm/distinfo Mon Dec 9 12:32:44 2013 (r335974) @@ -1,2 +1,2 @@ -SHA256 (vtwm-5.4.7.tar.gz) = c62f692c42420666920a23cd489633e91789b379fed13561321b44d9ffa8c9e9 -SIZE (vtwm-5.4.7.tar.gz) = 1021160 +SHA256 (vtwm-5.4.99.20130906.tar.xz) = 90a9edc39bc5b43ae22d1eb3dfaf8890ad501fe79be5aabb8bb5476e4cfe08d9 +SIZE (vtwm-5.4.99.20130906.tar.xz) = 963540 _______________________________________________ svn-ports-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-ports-all To unsubscribe, send any mail to "svn-ports-all-unsubscribe@freebsd.org"
State Changed From-To: open->closed Fresh snapshot committed. Sorry for the delay and thanks for your work!