Doug Barton wrote:
> The problem with this is that dependencies are actually recorded as a
> pair. For example:
>
> @pkgdep pkg-config-0.25_1
> @comment DEPORIGIN:devel/pkg-config
>
> Someone else already was kind enough to mention 'portmaster
> --check-depends' which will prompt you to do t
On 02/26/2011 08:34, Sergio de Almeida Lenzi wrote:
I use this script to get rid of the problem
the script detects @pkgdep record without argument
and deletes it from the +CONTENTS file in the /var/db/pkg/* directory
===
for i in /var/db/pkg/*/+CONTENTS
do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Content-Transfer-Encoding: QUOTED-PRINTABLE
These are all very good suggestions but a simpler solution that someone
dearly known as Doug Barton (dougb@) has already put a lot of work into.
So instead of hacking it up and throwing a bunch of script
On 26/02/2011 17:34, Sergio de Almeida Lenzi wrote:
I use this script to get rid of the problem
the script detects @pkgdep record without argument
and deletes it from the +CONTENTS file in the /var/db/pkg/* directory
===
for i in /var/db/pkg/*/+CONTENTS
do
I use this script to get rid of the problem
the script detects @pkgdep record without argument
and deletes it from the +CONTENTS file in the /var/db/pkg/* directory
===
for i in /var/db/pkg/*/+CONTENTS
do
if grep -q "@pkgdep $" $i
then
On Sat, Feb 26, 2011 at 03:22:28PM +0100, David Demelier wrote:
> Hello,
>
> It seems I have a corrupted port on my system :
>
> $ pkg_info
> [...]
> dmxproto-2.3DMX extension headers
> pkg_info: corrupted record (pkgdep line without argument), ignoring
> pkg_info: corrupted record (pkgde
