When to submit regression in a PR

2013-06-21 Thread Aymeric Mansoux
Hello everyone,

I am a FreeBSD newbie. I started to use it regularly for the first time
a couple of weeks ago and at the moment I am happily running
10.0-CURRENT with a custom kernel on my Thinkpad x61. 

One of the software that I also started to use a couple of weeks ago
(acme from the plan9port port) was recently updated and this introduced
two regressions. One of them is mentioned but not really solved in the
upstream bug tracker (compose key broken), the other is not (constant
CPU usage). This make the current port quite unusable. As a personal
workaround I used portdowngrade to compile the previous commit.

I was thinking about making a PR for this issue, however I read the
following in the handbook:

 Individual applications that are not in the base system but are
 instead part of the FreeBSD Ports Collection (category ports). Most of
 these applications are not written by FreeBSD developers; what FreeBSD
 provides is merely a framework for installing the application.
 Therefore, you should only report a problem to the FreeBSD developers
 when you believe the problem is FreeBSD-specific; otherwise, you
 should report it to the authors of the software.

My question therefore is: while I will mention these problems upstream,
should I also make the PR? Contact the port maintainer directly? 
I understand it is not FreeBSD specific (same issue on Debian Sid)
however it really make the current port unusable for those working on
laptops and those needing to input characters only reachable with the
compose key.

Thanks!
a.
--
http://su.kuri.mu
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Problem in installing textproc/asciidoc

2013-06-21 Thread Olivier Nicole
Hi,

On new 9.1 systems, textproc/asciidoc is being installed as dependency
to many other ports.

But the make install fails with the error:

installing Vim files in //usr/local/share/vim/vimfiles
cp: /usr/local/ETC/asciidoc.conf.sample: No such file or directory
*** [post-install] Error code 1

It is consistent on all the machines.

I can install the 20 or so files xxx.conf.sample by hand, it's
tedious, but it works.

But then, any other port that depend on asciidoc will fail to install,
saying that asciidoc have not been installed properly.

The version of asciidoc in the ports is asciidoc-8.6.8

I could not find any answer an Google, so I ask the question here:
what do I do wrong? Or is there something to tweak to make asciidoc
install and work normally?

Thanks in advance,

Olivier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Problem in installing textproc/asciidoc

2013-06-21 Thread Polytropon
On Fri, 21 Jun 2013 15:36:35 +0700 (ICT), Olivier Nicole wrote:
 Hi,
 
 On new 9.1 systems, textproc/asciidoc is being installed as dependency
 to many other ports.
 
 But the make install fails with the error:
 
 installing Vim files in //usr/local/share/vim/vimfiles
  ^
Two slashes here?

 cp: /usr/local/ETC/asciidoc.conf.sample: No such file or directory
 ^^^

Is this correct? In my opinion, the correct path name
should be /usr/local/etc/, _not_ in caps!



 It is consistent on all the machines.

Maybe an error in the port's configuration?



 I can install the 20 or so files xxx.conf.sample by hand, it's
 tedious, but it works.

That step should be completed by the post-install target
in /usr/ports/textproc/asciidoc/Makefile. Is there some
variable, like ${ETCDIR}, set wrongly?



 But then, any other port that depend on asciidoc will fail to install,
 saying that asciidoc have not been installed properly.

You could forcedly register the installation of the port that
you have manually completed.



 I could not find any answer an Google, so I ask the question here:
 what do I do wrong? Or is there something to tweak to make asciidoc
 install and work normally?

Check if you have anything suspicious set in /etc/make.conf
or in your environment that might override the logic of the
Makefile. Check the Makefile as well (I've checked 8.6.6's
on my 8.2 home system).

Just to be sure, make clean and re-checkout the port, then
try again.


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


problems with MAC labels on files

2013-06-21 Thread mohamed
Hi,?

I'm trying to set up an Biba policy but I'm unable to label files

 
This is the command : # setfsmac cy but I'm unable to label files-ef ut
/etc/policy-biba.context /s???$?AC???

 

This is the error :  setfsmac:   /etc/policy-biba.context: need label 

 

# uname -a

FreeBSD localhost.localdomain 9.0-RELEASE FreeBSD 9.0-RELEASE 

# setfmac biba/high test
setfmac: labeling not supported in test
 
I've read all the documentation and man pages but I cannot find what 
else do I have to do to get it working. Could you please tell what can I do
?
 
thanks in advance 
Mohamed ALsheikh
 

 

 

 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


setting VGA output from laptop

2013-06-21 Thread Xavier
Hi,

Is there any way to configure VGA width output from one laptop ?

Thanks.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: setting VGA output from laptop

2013-06-21 Thread Robert Bonomi

 Date: Fri, 21 Jun 2013 19:24:26 +0200
 Subject: setting VGA output from laptop
 From: Xavier xavierfreebsdquesti...@gmail.com

 Hi,

 Is there any way to configure VGA width output from one laptop ?


Authoritative answer: Maybe

It's not clear =exactly= what you're asking.

The standard FreeBSD video driver supports 80 and 90 column wide text
displays, with the caveat that 90-colum mode may not be usable on some
laptops.  

If you're dealing with a graphics display, minimal VGA is 640x480 pixels.
virtually every even remotely moddern display supports 800x600 as well, 
many support 1024x768, and a fair number go to even higher resolutions.

'man vidcontrol' will tell you how to find out what is supported on _your_
machine.



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: setting VGA output from laptop

2013-06-21 Thread Xavier
On Fri, Jun 21, 2013 at 01:40:14PM -0500, Robert Bonomi wrote:

Hi Robert,


  Date: Fri, 21 Jun 2013 19:24:26 +0200
  Subject: setting VGA output from laptop
  From: Xavier xavierfreebsdquesti...@gmail.com
 
  Hi,
 
  Is there any way to configure VGA width output from one laptop ?
 

 Authoritative answer: Maybe

 It's not clear =exactly= what you're asking.

 The standard FreeBSD video driver supports 80 and 90 column wide text
 displays, with the caveat that 90-colum mode may not be usable on some
 laptops.

 If you're dealing with a graphics display, minimal VGA is 640x480 pixels.
 virtually every even remotely moddern display supports 800x600 as well,
 many support 1024x768, and a fair number go to even higher resolutions.

 'man vidcontrol' will tell you how to find out what is supported on _your_
 machine.




For example if I try to set 40x25 text mode with VIDCONTROL(1) it don't
work.
And 'vidcontrol -i mode | grep T' show this mode.

I don't understand why if 40x25 mode if supported, VIDCONTROL(1) don't
set it ?

Thanks, see you.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


mouse configuration question

2013-06-21 Thread Robert Bonomi


I have a ps/2 mouse attached to a HP mini-tower running FreeBSD 8.3, with
a stripped-down kernel (no loadable modules).  I've apparently removed 
something necessary for standard mouse functionality, but I have no clue as
to -what- is missing.

Gory details:
  1) '/dev/psm0' exists and +is+ the mouse,
  2) 'moused' detects the mouse:  psm0  sysmouse Intellimouse
  3) 'moused -d' properly reports mouse activity -- button press/release and
 mouse motion.
  4) 'vidcontrol -m on' reports inappropriate ioctl for device.
  5) *NO* '/dev/sysmouse' device present.

I'm building an ncurses-based app, and want to add mouse functionality.
The ncurses mouse-related functions return 'total failure' status (value 0).

I suspect that 5), above is the immediate issue, but can't find out 'who'
is (ir-)responsible for creating that psuedo-device.

Any/all pointers much appreciated.





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: mouse configuration question

2013-06-21 Thread Robert Bonomi

 Date: Fri, 21 Jun 2013 21:21:45 +0200
 Subject: Re: mouse configuration question
 From: Xavier xavierfreebsdquesti...@gmail.com

 On Fri, Jun 21, 2013 at 02:09:13PM -0500, Robert Bonomi wrote:

 Hi Robert,

  I have a ps/2 mouse attached to a HP mini-tower running FreeBSD 8.3, 
  with a stripped-down kernel (no loadable modules).  I've apparently 
  removed something necessary for standard mouse functionality, but I 
  have no clue as to -what- is missing.
 
  Gory details:
1) '/dev/psm0' exists and +is+ the mouse,
2) 'moused' detects the mouse:  psm0  sysmouse Intellimouse
3) 'moused -d' properly reports mouse activity -- button 
press/release and
   mouse motion.
4) 'vidcontrol -m on' reports inappropriate ioctl for device.

 Try another time out of any TMUX(1), SCREEN(1) or similar application, 
 and it work right.

Unfortunately, _not_ true.  I've made multiple attempts from multiple 
screen sessions, and even after multiple reboots.  No luck.

moused _is_ loaded on system boot, further there are multiple 
'vidcontrol: inappropriate ioctl for device' messages on the console
as the last thing before the login prompt is displayed.

I've tried sending SIGHUP and/or SIGUSR1 to moused, with no effect on the
issue.  no '/dev/sysmouse', curses mouse routines still report total failure,
and all the rest.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: How do I launch Calligra?

2013-06-21 Thread Eduardo Morras
On Thu, 20 Jun 2013 09:02:42 -0700
Ed Flecko edfle...@gmail.com wrote:

 I've installed Calligra Suite from package, but I'm struggling to figure
 out how to launch any of its programs???

These are my entries in the handwritten Fluxbox Menu:

/usr/local/kde4/bin/kexi
/usr/local/kde4/bin/calligrawords

HTH

 Ed

---   ---
Eduardo Morras emorr...@yahoo.es
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: When to submit regression in a PR

2013-06-21 Thread Shane Ambler

On 21/06/2013 17:12, Aymeric Mansoux wrote:


My question therefore is: while I will mention these problems
upstream, should I also make the PR? Contact the port maintainer
directly? I understand it is not FreeBSD specific (same issue on
Debian Sid) however it really make the current port unusable for
those working on laptops and those needing to input characters only
reachable with the compose key.


I would. While the ports are handled separately from the base system
they need to be maintained as well. If a version of a port has issues
then an older version could stay in place.

The pr system is used for ports as well as the base system.

Can't say I'm sure which key you refer to as compose - do you mean Alt
or Ctrl? I have heard of the ctrl key being remapped to the caps lock
for continuous use. You may also look into turning on sticky keys, it
keeps a modifier key active without holding it down so that the next key
pressed has the modifier included. see x11/xkbset


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org