Hi,
I've finally found the solution! After a lot of trial and error with
the Makefile and removing all references to tech-notes.txt in the
pkg-plist, make check-plist found no errors.
Thanks for all the help!
Regards,
Marco
___
freebsd-ports@freebs
Hi!
> > The Bug 197843 is already awaiting for commit.
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197843
> Can some committer(tm) commit this?
Done. Thanks for the patch!
--
p...@opsec.eu+49 171 3101372 5 years to go !
On 2015-02-21 10:37, Alexander Moisseev wrote:
21.02.2015 19:20, Larry Rosenman пишет:
The current port doesn't support roundcube 1.1 (now in ports)
the following DOES work:
https://github.com/JohnDoh/Roundcube-Plugin-Context-Menu
Can you update the port?
The Bug 197843 is already awaiting
On Tue, 17 Feb 2015 23:14:34 + Olivier Duchateau
wrote:
> An update of sysutils/xfce4-power-manager is available for some time in
> Xfce devel repo. It's time to test it. Settings manager and panel were
> rewritten, support of FreeBSD (and DragonFly) was enhanced.
upower 0.99 dropped suppor
21.02.2015 19:20, Larry Rosenman пишет:
The current port doesn't support roundcube 1.1 (now in ports)
the following DOES work:
https://github.com/JohnDoh/Roundcube-Plugin-Context-Menu
Can you update the port?
The Bug 197843 is already awaiting for commit.
https://bugs.freebsd.org/bugzilla/sh
The current port doesn't support roundcube 1.1 (now in ports)
the following DOES work:
https://github.com/JohnDoh/Roundcube-Plugin-Context-Menu
Can you update the port?
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.o
This problem is caused by xml file corruption. I had over 4000 lines of
"" in my
folderlist.xml
I solved this problem by:
1. Move these elsewhere: ~/.claws-mail/RSSly, ~/.claws-mail/tagsdb/#rssly
2. Backup ~/.claws-mail/folderlist.xml and ~/.claws-mail/folderitemrc
3. Edit ~/.claws-mail/folderit
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. One common problem is
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. One common problem is
12 matches
Mail list logo
