The problem is caused by Unicode code points in keymap files, which were
made possible (and have to be used) for many locales after the
introduction of Unicode support with vt(4).
Am 28.08.2014 um 19:43 schrieb Stefan Esser:
> Am 28.08.2014 um 17:03 schrieb Filippo Moretti via freebsd-stable:
>> I
Ok, so what can we do right now to not have unicode characters in say,
the US keymap file?
(Just a local change, not committed anywhere - I agree it needs to be
fixed in the xorg code.)
-a
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd
Hi!
> The update is mostly some small changes to the code to eliminate clang++
> and recent g++ warnings along with Eric's typo, which has been
> languishing for a while. I know it's a small thing, but seeing those
> warnings when I compile the port makes me sad. Obviously you guys can
> reject
Am 31.08.2014 um 09:45 schrieb Adrian Chadd:
> Ok, so what can we do right now to not have unicode characters in say,
> the US keymap file?
The "normal" US keyboard (/usr/share/vt/keymaps/us.kbd) does not
contain characters >= 0x100.
There is no problem even with ISO8859-1 characters used in many
On 08/31/2014 08:53, Stefan Esser wrote:
The problem is caused by Unicode code points in keymap files, which were
made possible (and have to be used) for many locales after the
introduction of Unicode support with vt(4).
Am 28.08.2014 um 19:43 schrieb Stefan Esser:
Am 28.08.2014 um 17:03 schrie
I've filed a patch to amanda-server (and slave port amanda-client) to
add staging support and set me as maintainer:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193196
This is my first staging patch; I followed all the steps in the
wiki guide at https://wiki.freebsd.org/ports/StageDir but ha
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
On 20/08/2014 18:34, Bryan Drewery wrote:
On 9/21/2013 5:49 AM, Bryan Drewery wrote:
Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.
Support may be added for earlier i386 releases once all ports properly
respect LD
Hey,
since the update to tcl86-8.6.2, I’m getting this error trace:
can't find package msgcat 1.4
while executing
"package require msgcat 1.4"
("uplevel" body line 2)
invoked from within
"uplevel \#0 {
package require msgcat 1.4
if { $::tcl_platform(platform) eq {windows} } {
Am 31.08.2014 um 17:32 schrieb Stefan Bethke :
> Hey,
>
> since the update to tcl86-8.6.2, I’m getting this error trace:
> can't find package msgcat 1.4
>while executing
> "package require msgcat 1.4"
>("uplevel" body line 2)
>invoked from within
> "uplevel \#0 {
>package require
I discovered that:
* if I don't load kbdmap at boot-time as a module, the probe order
works in a way that xorg works;
* if I load kbdmap by hand after boot, or I don't load it at all, then
even the US keyboard map causes xorg to choke.
If I load kbdmap at boot-time then kbdcontrol reports inappro
Am 31.08.2014 um 17:40 schrieb Stefan Bethke :
>
> Am 31.08.2014 um 17:32 schrieb Stefan Bethke :
>
>> Hey,
>>
>> since the update to tcl86-8.6.2, I’m getting this error trace:
>> can't find package msgcat 1.4
>> while executing
>> "package require msgcat 1.4"
>> ("uplevel" body line 2)
>>
On Thu, Aug 28, 2014 at 8:26 AM, Erich Dollansky
wrote:
> Hi,
>
> I did not got through the full thread to see if you found a solution.
Yes, I did. In fact, freebsd-update provided the solution; I used it
to upgrade to FreeBSD 8.4-release:
root@kg-vm2# uname -a
FreeBSD kg-vm2 8.4-RELEASE-p14 Free
On Sun, Aug 31, 2014 at 12:50 AM, Kurt Jaeger wrote:
> Hi!
>
> > The update is mostly some small changes to the code to eliminate clang++
> > and recent g++ warnings along with Eric's typo, which has been
> > languishing for a while. I know it's a small thing, but seeing those
> > warnings when
On 2014-08-31 19:43, Torfinn Ingolfsen wrote:
> On Thu, Aug 28, 2014 at 8:26 AM, Erich Dollansky
> wrote:
>> Hi,
>>
>> I did not got through the full thread to see if you found a solution.
>
> Yes, I did. In fact, freebsd-update provided the solution; I used it
> to upgrade to FreeBSD 8.4-release
10-PRERELEASE
fresh portstree
# make
===> License PHP30 accepted by the user
===> pecl-pdflib-3.0.4 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by pecl-pdflib-3.0.4 for building
===> Extracting for pecl-pdflib-3.0.4
=> SHA256 Checksum mismatch for PECL/pdf
On 08/31/14 21:16, Per olof Ljungmark wrote:
> 10-PRERELEASE
> fresh portstree
>
> # make
> ===> License PHP30 accepted by the user
> ===> pecl-pdflib-3.0.4 depends on file: /usr/local/sbin/pkg - found
> ===> Fetching all distfiles required by pecl-pdflib-3.0.4 for building
> ===> Extracting f
Hi,
root@bolton:/usr/ports/distfiles/PECL # fetch
http://distcache.FreeBSD.org/ports-distfiles/PECL/pdflib-3.0.4.tgz
pdflib-3.0.4.tgz 100% of 26 kB 6627 kBps
00m00s
root@bolton:/usr/ports/distfiles/PECL # cd /usr/ports/print/pecl-pdflib
root@bolton:/usr/ports/pri
On 08/31/14 21:44, Daniel Austin via freebsd-ports wrote:
> Hi,
>
> root@bolton:/usr/ports/distfiles/PECL # fetch
> http://distcache.FreeBSD.org/ports-distfiles/PECL/pdflib-3.0.4.tgz
> pdflib-3.0.4.tgz 100% of 26 kB 6627 kBps
> 00m00s
> root@bolton:/usr/ports/distfil
On Sun, Aug 31, 2014 at 8:37 PM, olli hauer wrote:
>
> Hm, do you mean update with subversion to 8.4-stable or 8.4-current?
Yes, and 8.4-stable. There is no 8.4-current.
> Unless you have a non default kernel there is no need to rebuild to get
> 8.4-stable, just run `freebsd-update fetch instal
On 2014-08-31 22:38, Torfinn Ingolfsen wrote:
> On Sun, Aug 31, 2014 at 8:37 PM, olli hauer wrote:
>>
>> Hm, do you mean update with subversion to 8.4-stable or 8.4-current?
>
> Yes, and 8.4-stable. There is no 8.4-current.
>
>> Unless you have a non default kernel there is no need to rebuild to
21 matches
Mail list logo
