Hi,
today it occured to me due some power outage or something unexpected
like that caused filesystem breakage. fsck with journal was not able to
repair damage and the result was repeated restart. It is a virtual
machine on HyperV hypervisor, by the way, but that is irrelevant to the
problem I like
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 07/12/14 09:38, Milan Obuch wrote:
> # pkg check -s -a
> Checking all packages: 24%
> pkg: pkg_create_from_dir(lstat failed): No such file or directory
> Checking all packages: 100%
> #
>
> and no idea now which package needs reinstall.
Agreed. One need to use verbose output to identifiy the
On Sun, 07 Dec 2014 11:43:24 +0100
Xavier wrote:
> On 07/12/14 09:38, Milan Obuch wrote:
>
> > # pkg check -s -a
> > Checking all packages: 24%
> > pkg: pkg_create_from_dir(lstat failed): No such file or directory
> > Checking all packages: 100%
> > #
> >
> > and no idea now which package need
I just updated, or rather tried to update the "gnupg" port. it failed with a
message that it conflicts with the "dirmngr" port. I deleted that port and
then preceded to install "GNUPG". When I attempted to re-install the "dirmngr"
port, it issued this error message:
dirmngr-1.1.0_12 conflicts with
On Fri, Mar 07, 2014 at 01:45:38PM +, Alexey Dokuchaev wrote:
> On Fri, Mar 07, 2014 at 01:58:49PM +0100, Ren? Ladan wrote:
> > I noticed that linux_base-c6 and nvidia-driver conflict when one selects
> > the LINUX option in nvidia-driver (default on). The culprit is
> > /compat/linux/usr/lib/l
Carmel NY wrote:
> I just updated, or rather tried to update the "gnupg" port. it failed with a
> message that it conflicts with the "dirmngr" port.
We're aware of it:
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=526796+0+archive/2014/freebsd-ports/20141130.freebsd-ports
But you might want to r
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 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. The most common probl
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. The most common probl
Running CURRENT (FreeBSD 11.0-CURRENT #2 r275512: Fri Dec 5 16:00:34
CET 2014 amd64), I ran into some kind of obscurity I can not fathom.
Updating ports fails since a couple of days by now (I do updates on
a daily basis). fetch isn't capable of reaching any(!) server it tries
to download sourceco
13 matches
Mail list logo
