On 04/04/2014 23:02, sindrome wrote:
> So I still keep my source, ports and docs in sync via svn update. Here's
> where the issue comes in. After I have done the pkg upgrade and it tells me
> all is up-to-date, the 'pkg_version -v |grep needs' command shows me dozens
> of ports that are not up-to
On 04/04/2014 23:49, Robert Huff wrote:
> "pkgng" can do almost everything the old system can, and does it
> better.
s/almost//
pkg(8) does a damn sight more than the old pkg_tools.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpke
On 05/04/2014 00:44, sindrome wrote:
> foo:109:/home/foobar# pkg_version -v |grep needs it shows 240 ports that need
> updating.
It shows that you have out-of-date data in the remains of the old-style
/var/db/pkg that pkg2ng leaves in place.
Please execute the following command to clean up /var/
Op 5 apr. 2014 om 05:48 heeft Shane Ambler het volgende
geschreven:
> On 04/04/2014 22:42, Willem Jan Withagen wrote:
>> Hi,
>>
>> I've tried to upgrade my python 2.7 which did not work.
>> Then I deinstalled all python stuff and tried to install python3 (aka 3.3)
>
> You can install both ve
Matthew Seaman writes:
> pkg(8) does a damn sight more than the old pkg_tools.
Granted, though much of it I currently have little use for. :-)
>> "pkgng" can do almost everything the old system can, and does it
>> better.>
>
> s/almost//
OK, Obi-wan - what's the replacemen
On Sat, 05 Apr 2014 07:55:48 -0400
Robert Huff wrote:
> Matthew Seaman writes:
>
> > pkg(8) does a damn sight more than the old pkg_tools.
>
> Granted, though much of it I currently have little use
> for. :-)
>
> >> "pkgng" can do almost everything the old system can, and does it
>
-Original Message-
From: Robert Huff
OK, Obi-wan - what's the replacement for:
a) "portsclean" with the C, D (single and double), and L
options? (Use no more than two commands.)
b) "pkg_sort" ?
With these, I will cheerfully delete portupgrade.
portupgrade != pkg_old
Actually, fo
Hello :-)
I have noted a problem with accessing the optical disk recorders with
cdrecord - it gets stuck at start and cannot be killed (-9), probably
at the device access/detect stage. Any hints welcome :-)
# cdrecord -scanbus
Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd10.0) Copyright
On Sat, 5 Apr 2014 14:22:45 +0200, CeDeROM wrote:
> Hello :-)
>
> I have noted a problem with accessing the optical disk recorders with
> cdrecord - it gets stuck at start and cannot be killed (-9), probably
> at the device access/detect stage. Any hints welcome :-)
You could try to forcedly deta
Yes, this is exactly when accessing the drive:
% cdrecord lubuntu-13.10-desktop-i386.iso
cdrecord: No write mode specified.
cdrecord: Assuming -sao mode.
cdrecord: If your drive does not accept -sao, try -tao.
cdrecord: Future versions of cdrecord may have different drive
dependent defaults.
Cdrec
Dear client, We're pleased to inform you that, with months of research, we've
introduced our new R4 products to market. We offer an over 50% discount on all
our R4/R4i 3DS Cards. http://www.ggnds.com/nds-card-list.html You can get an
additional discount of 15% with coupon code "ggnds.com".
On Sat, Apr 5, 2014 at 3:58 PM, Polytropon wrote:
> You could try to forcedly detach it from the SCSI bus by
> using "camcontrol stop ". Maybe resetting the
> bus also helps. It will then maybe be possible to kill the
> cdrecord process from another terminal. See "man camcontrol"
> for details.
T
when i try to install the ktorrent it's always stop with an error.
So I decided that will install the full kde4 meta ports, but this
error occur ever time i type make install command. My solution
(I think have some problem with makefile) was change the version
number 4.12.3 -> 4.12.4, and the
> Hi all,
> I get the following error when running mnemosyne (games/py-mnemosyne):
> % mnemosyne
> An unexpected error has occurred.
> Please forward the following info to the developers:
> Traceback (innermost last):
> File "/usr/local/bin/mnemosyne", line 155, in
> debug_file=options.de
Scanning dependencies of target kwin
gmake[11]: Saindo do diretório `/usr/ports/x11/kde4-workspace/work/.build'
gmake[11]: Entrando no diretório `/usr/ports/x11/kde4-workspace/work/.build'
[ 98%] Building CXX object kwin/CMakeFiles/kwin.dir/kwin_dummy.cpp.o
Linking CXX executable kwin
[ 98%] Bui
On 5/04/2014 9:12 PM, Willem Jan Withagen wrote:
>
>
> Op 5 apr. 2014 om 05:48 heeft Shane Ambler het
> volgende geschreven:
>
>> On 04/04/2014 22:42, Willem Jan Withagen wrote:
>>> Hi,
>>>
>>> I've tried to upgrade my python 2.7 which did not work.
>>> Then I deinstalled all python stuff and
16 matches
Mail list logo
