[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Bug 208250] Review Request: piklab - Development environment for applications based on PIC and dsPIC microcontrollers



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: piklab - Development environment for applications based on PIC and dsPIC microcontrollers


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=208250


mtasaka ioa s u-tokyo ac jp changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
         AssignedTo|nobody fedoraproject org    |mtasaka ioa s u-tokyo ac jp
OtherBugsDependingO|163776                      |163778
              nThis|                            |




------- Additional Comments From mtasaka ioa s u-tokyo ac jp  2006-09-29 04:16 EST -------
(In reply to comment #15)
> (In reply to comment #14)
> > The problem is to know if I have to add this BR or if this BR is missing in 
> a 
> > package from which pikloop depends.
> 
> piklab of course :-)

Well, configure requests the existence of -lcurses.
in FC5, this is in ncurses, which are installed by minimal buildroot.
However, in FC6, libcurses.so is moved to ncurses-devel.

So you have to add ncurses-devel to BuildRequires and the problem
for rebuilding is resolved.

I have not yet reviewed this fully, however,
* rpmlint complaints about long summary. It says that summary should
  have no longer than 79 characters.
* Please add "ncurses-devel" to BuildRequiers (this should be no problem
  for FC5, too).
* Perhaps /etc/security/consoles.perms.d/ should be
  /etc/security/console.perms.d/ ? (the latter is owned by pam)

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]