Re: conky does not build
On 2012/03/06 20:56, Nikos Ntarmos wrote: FYI patch attached and also submitted as follow-up to ports/164893[1]. Cheers. \n\n Excuse me coming late, I was away and couldn't test. Everything is OK now. Many thanks to Nikos and Ivan. BR, Oli ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: databases/pglessog, databases/pg_rman problems after the last bsd.database.mk update
> I've just committed a fix that solves your INDEX problem for now [1], > but I'll still get kuriyama@ to use the new server:extract when it > comes in. I don't have INDEX generate testing environment for now, so can you commit a fix? -- Jun Kuriyama // FreeBSD Project // S2 Factory, Inc. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: databases/pglessog, databases/pg_rman problems after the last bsd.database.mk update
On 11 March 2012 08:51, Jun Kuriyama wrote: >> I've just committed a fix that solves your INDEX problem for now [1], >> but I'll still get kuriyama@ to use the new server:extract when it >> comes in. > > I don't have INDEX generate testing environment for now, so can you > commit a fix? Sure, thanks. Didn't realise you were CC'd in! I'll make sure I test it properly. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
portsnap not fetching
Portsnap isn't fetching new ports since yesterday. If I'm not wrong the last fetched is devel/xxdgb. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
portsnap problem
Hello, for a day already, portsnap fetch seems not to fetch newest changes. freshports shows lots of changes, port portsnap fetch says there everything is up to date. I checked that the ports are really newer in freshports than in my machine. I also removed everything in /usr/ports and /var/db/portsnap and issued portsnap fetch extract, but it did not help. Maybe some job that creates patches for portsnap died? Herby ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portsnap problem
On Sunday 11 March 2012 07:05:35 Herby Vojčík wrote: > Hello, > > for a day already, portsnap fetch seems not to fetch newest changes. > freshports shows lots of changes, port portsnap fetch says there > everything is up to date. > I checked that the ports are really newer in freshports than in my machine. > I also removed everything in /usr/ports and /var/db/portsnap and issued > portsnap fetch extract, but it did not help. > > Maybe some job that creates patches for portsnap died? > > Herby > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" I have the same "problem" on my 9.0-Release. Mitja http://jpgmag.com/people/lumiwa ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portsnap problem
Em Dom, 2012-03-11 às 07:38 -0500, ajtiM escreveu: > On Sunday 11 March 2012 07:05:35 Herby Vojčík wrote: > > Hello, > > > > for a day already, portsnap fetch seems not to fetch newest changes. > > freshports shows lots of changes, port portsnap fetch says there > > everything is up to date. > > I checked that the ports are really newer in freshports than in my machine. > > I also removed everything in /usr/ports and /var/db/portsnap and issued > > portsnap fetch extract, but it did not help. > > > > Maybe some job that creates patches for portsnap died? > > Or just that ports system is "frozen" because of the 8.3 release??? Occam's razor: when you have two or more competing theories that make exactly the same predictions, the simpler one is the better. [] Sergio ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portsnap problem
http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) 2012/3/11 Sergio de Almeida Lenzi : > Em Dom, 2012-03-11 às 07:38 -0500, ajtiM escreveu: > >> On Sunday 11 March 2012 07:05:35 Herby Vojčík wrote: >> > Hello, >> > >> > for a day already, portsnap fetch seems not to fetch newest changes. >> > freshports shows lots of changes, port portsnap fetch says there >> > everything is up to date. >> > I checked that the ports are really newer in freshports than in my machine. >> > I also removed everything in /usr/ports and /var/db/portsnap and issued >> > portsnap fetch extract, but it did not help. >> > >> > Maybe some job that creates patches for portsnap died? >> > > > Or just that ports system is "frozen" because of the 8.3 release??? > No, Herby's theory is far more likely. The ports system is open as ususal, except that no big changes can go in and all commits have to be tagged with the "Feature safe" tag (and actually be feature safe). René ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portsnap problem
On 11 March 2012 12:55, Sergio de Almeida Lenzi wrote: > Em Dom, 2012-03-11 às 07:38 -0500, ajtiM escreveu: > >> On Sunday 11 March 2012 07:05:35 Herby Vojčík wrote: >> > Hello, >> > >> > for a day already, portsnap fetch seems not to fetch newest changes. >> > freshports shows lots of changes, port portsnap fetch says there >> > everything is up to date. >> > I checked that the ports are really newer in freshports than in my machine. >> > I also removed everything in /usr/ports and /var/db/portsnap and issued >> > portsnap fetch extract, but it did not help. >> > >> > Maybe some job that creates patches for portsnap died? >> > > > Or just that ports system is "frozen" because of the 8.3 release??? > > Occam's razor: > > when you have two or more competing theories > that make exactly the same predictions, > the simpler one is the better. CC: portsnap maintainer Although that might be a reasonable explanation, it's much more likely that portsnap data is not being generated right now. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portsnap problem
On 11/03/2012 12:55, Sergio de Almeida Lenzi wrote: > Em Dom, 2012-03-11 às 07:38 -0500, ajtiM escreveu: > >> On Sunday 11 March 2012 07:05:35 Herby Vojčík wrote: >>> Hello, >>> >>> for a day already, portsnap fetch seems not to fetch newest changes. >>> freshports shows lots of changes, port portsnap fetch says there >>> everything is up to date. >>> I checked that the ports are really newer in freshports than in my machine. >>> I also removed everything in /usr/ports and /var/db/portsnap and issued >>> portsnap fetch extract, but it did not help. >>> >>> Maybe some job that creates patches for portsnap died? >>> > > Or just that ports system is "frozen" because of the 8.3 release??? > > Occam's razor: > > when you have two or more competing theories > that make exactly the same predictions, > the simpler one is the better. That's not it. Ports only gets frozen completely for a matter of an hour or so as part of the release process. Instead, it spends much of the period leading up to a release in "Slush" -- which is the case at the moment. Slush doesn't mean that ports stop being updated. On the contrary, there have been some twenty-odd ports updated just this morning as I can see from the cvs-ports@ mailing list. Slush does mean that changes with large scale ramifications are not permitted, so last week's perl-related updates for instance, would not be allowed right now. The portsnap thing is a real problem. No idea what or why or how long to fix, but I'd hazard a guess that the answer to the last is "by later today." Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: portsnap problem
On 03/11/12 06:00, Chris Rees wrote: > CC: portsnap maintainer Thanks! I don't regularly read freebsd-ports (funny for the portsnap maintainer to not be subscribed, I know, but I get way too much email already...). > Although that might be a reasonable explanation, it's much more likely > that portsnap data is not being generated right now. Almost correct -- I just restarted the portsnap builds a few minutes ago. They were broken for about 18 hours; I'm not entirely certain of the cause but I suspect a freebsd.org DNS glitch was at least partly responsible. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portsnap problem
On Sun, 11 Mar 2012 09:55:27 -0300 Sergio de Almeida Lenzi articulated: > Or just that ports system is "frozen" because of the 8.3 release??? > > Occam's razor: > > when you have two or more competing theories > that make exactly the same predictions, > the simpler one is the better. Actually, there are numerous "razors", Occam's being only one. Occam's razor (also written as Ockham's razor) is the English equivalent of the Latin lex parsimoniae --- the law of parsimony, economy or succinctness. It is a principle urging one to select among competing hypotheses that which makes the fewest assumptions and thereby offers the simplest explanation of the effect. It is usually translated as, "simpler explanations are, other things being equal, generally better than more complex ones". The key phase being "other things being equal". Personally, I am a strong believer in "Murphy's Law". -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portsnap problem
Em Dom, 2012-03-11 às 09:22 -0400, Jerry escreveu: > Actually, there are numerous "razors", Occam's being only one. Seems that "Murphy's Law". wins in this case... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD Port: skype-2.1.0.81,1
Hello;
After installing net-im/skpe, the application starts up fine, but when
I try to connect it times out after a few minutes and tells me "P2P
Connect failed". In syslog I see
Code:
kernel: linux: pid 3175 (skype): ioctl fd=11, cmd=0x564a ('V',74) is
not implemented.
% uname -a:
Code:
FreeBSD phe.ath.cx 8.3-RC1 FreeBSD 8.3-RC1 #0: Sun Mar 4 00:42:38 UTC
2012 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386.
% kldstat:
Code:
Id Refs AddressSize Name
1 39 0xc040 c68d94 kernel
21 0xc1069000 f9d4 if_iwi.ko
31 0xc1079000 7120 snd_ich.ko
42 0xc1081000 57908sound.ko
51 0xc10d9000 4f90 atapicam.ko
61 0xc10de000 4a64 cuse4bsd.ko
71 0xc575f000 8000 linprocfs.ko
81 0xc5777000 28000linux.ko
91 0xc581d000 4000 fdescfs.ko
101 0xc598b000 3iwi_bss.ko
111 0xc5c2d000 68000radeon.ko
121 0xc5c96000 14000drm.ko
net-im/skype-devel connects and generally seems to work fine, but
video unfortunately doesn't work with the devel port. I've tried
moving ~/.Skype, but no luck. I also tried creating a new skype
account from the client, but this also times out. Αm I doing something
wrong?
Cheers,
J
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
PHP 5.4.0 : lang/php54
Hello, please look http://www.freebsd.org/cgi/query-pr.cgi?pr=165933 -- Svyatoslav ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: skype-2.1.0.81,1
El día Sunday, March 11, 2012 a las 12:25:08PM -0300, Joseph Mingrone escribió:
> Hello;
>
> After installing net-im/skpe, the application starts up fine, but when
> I try to connect it times out after a few minutes and tells me "P2P
> Connect failed". In syslog I see
> Code:
>
> kernel: linux: pid 3175 (skype): ioctl fd=11, cmd=0x564a ('V',74) is
> not implemented.
This means only that one of the V4L2 ioctls is not supported in the
Linux emulation; it is perhaps unrelated to your connection problem;
are you using some proxy or Skype over HTTPS; see the protocol connect
and login sequence described in http://en.wikipedia.org/wiki/Skype_protocol
and watch with tcpdump what is going on during connect;
HIH
matthias
>
> % uname -a:
> Code:
>
> FreeBSD phe.ath.cx 8.3-RC1 FreeBSD 8.3-RC1 #0: Sun Mar 4 00:42:38 UTC
> 2012 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386.
>
> % kldstat:
> Code:
>
> Id Refs AddressSize Name
> 1 39 0xc040 c68d94 kernel
> 21 0xc1069000 f9d4 if_iwi.ko
> 31 0xc1079000 7120 snd_ich.ko
> 42 0xc1081000 57908sound.ko
> 51 0xc10d9000 4f90 atapicam.ko
> 61 0xc10de000 4a64 cuse4bsd.ko
> 71 0xc575f000 8000 linprocfs.ko
> 81 0xc5777000 28000linux.ko
> 91 0xc581d000 4000 fdescfs.ko
> 101 0xc598b000 3iwi_bss.ko
> 111 0xc5c2d000 68000radeon.ko
> 121 0xc5c96000 14000drm.ko
>
> net-im/skype-devel connects and generally seems to work fine, but
> video unfortunately doesn't work with the devel port. I've tried
> moving ~/.Skype, but no luck. I also tried creating a new skype
> account from the client, but this also times out. Αm I doing something
> wrong?
>
> Cheers,
>
> J
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e - w http://www.unixarea.de/
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PHP 5.4.0 : lang/php54
On Sunday 11 March 2012 19:29:09 Svyatoslav Lempert wrote:
> Hello,
> please look http://www.freebsd.org/cgi/query-pr.cgi?pr=165933
May be more correctly set PHP 5.4 by default to lang/php5, and repocopy
current lang/php5 into lang/php53?
Probably current maintainer of php (@ale) has the plan ;)
PS: It will be nice to add an option for build PHP with DTRACE support:
--- php54.orig/Makefile 2012-03-11 19:52:35.235493071 +0400
+++ php54/Makefile 2012-03-11 19:48:13.0 +0400
@@ -46,6 +46,7 @@
MULTIBYTE "Enable zend multibyte support" off \
IPV6 "Enable ipv6 support" on \
MAILHEAD "Enable mail header patch" off \
+ DTRACE "Build with DTrace probes" off
CONFLICTS= php4-4* php5-pcre-* php5-spl-* php52-*
@@ -132,6 +133,10 @@
CONFIGURE_ARGS+=--disable-ipv6
.endif
+.if defined(WITH_DTRACE)
+CONFIGURE_ARGS+=--enable-dtrace
+.endif
+
post-patch:
@${TOUCH} ${WRKSRC}/ext/php_config.h
@${REINPLACE_CMD} "s|^\(extension_dir\)|; \1|" ${WRKSRC}/php.ini-*
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PHP 5.4.0 : lang/php54
2012/3/12 Mr Dandy : >> please look http://www.freebsd.org/cgi/query-pr.cgi?pr=165933 > > May be more correctly set PHP 5.4 by default to lang/php5, and repocopy > current lang/php5 into lang/php53? > No, I wrote about this a few weeks ago to ports@ - PHP 5.4 is not compatible with PHP 5.3, depricated funtions now removed. > Probably current maintainer of php (@ale) has the plan ;) > > PS: It will be nice to add an option for build PHP with DTRACE support: > Of course all this discussion, I posted "actually draft" -- Svyatoslav ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: skype-2.1.0.81,1
Hi Matthia, ports; Thanks for you reply. I think I'm getting closer to finding out what's going on. I have a small LAN, which normally just has a single laptop and a skype phone behind a Buffalo wireless access point / router. The skype phone is usually on all the time and I haven't had problems with it for the two or three years I've owned it. Last night when I was testing the skype client on my laptop I turned the phone off. So this morning when I got your message, I uninstalled net-im/skype-devel and reinstalled net-im/skype and it signed in immediately. But now, the skype phone has the problem the client had last night: it won't sign in. Even when I sign out with both the client and the phone and try the phone it won't sign in, but the client has no problems at all today. I thought there must be a problem with the router, so I rebooted, but the result is the same: client has no problems, but no luck with the phone. Is this a networking issue on my end or is it something to do with skype? J ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: skype-2.1.0.81,1
El día Sunday, March 11, 2012 a las 02:23:56PM -0300, Joseph Mingrone escribió: > Hi Matthia, ports; > > Thanks for you reply. I think I'm getting closer to finding out > what's going on. > > I have a small LAN, which normally just has a single laptop and a > skype phone behind a Buffalo wireless access point / router. The > skype phone is usually on all the time and I haven't had problems with > it for the two or three years I've owned it. Last night when I was > testing the skype client on my laptop I turned the phone off. > > So this morning when I got your message, I uninstalled > net-im/skype-devel and reinstalled net-im/skype and it signed in > immediately. But now, the skype phone has the problem the client had > last night: it won't sign in. Even when I sign out with both the > client and the phone and try the phone it won't sign in, but the > client has no problems at all today. I thought there must be a > problem with the router, so I rebooted, but the result is the same: > client has no problems, but no luck with the phone. > > Is this a networking issue on my end or is it something to do with skype? This is difficult to guess and impossible to solve from remote. It sounds a bit like some NAT issue in the router and the first client connecting to Skype wins. No sure, though. HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Boost ports update
Folks, I've fixed devel/sdts++. The patch is here: http://alexanderchuranov.com/boost-port/devel-sdts++-boost-148-2012-03-11_20-23-23.diff Alexander Churanov, maintainer of devel/boost-* ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PHP 5.4.0 : lang/php54
Mr Dandy wrote: On Sunday 11 March 2012 19:29:09 Svyatoslav Lempert wrote: Hello, please look http://www.freebsd.org/cgi/query-pr.cgi?pr=165933 May be more correctly set PHP 5.4 by default to lang/php5, and repocopy current lang/php5 into lang/php53? It is to early to make it a default PHP port. 5.4 is not backward compatible with 5.3 and it will be really bad for users to accidentaly upgrade to 5.4 instead of just update 5.3 install. +1 for make it lang/php54 for those who need it / want it to testing and development. Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: skype-2.1.0.81,1
On Sun, Mar 11, 2012 at 14:33, Matthias Apitz wrote: > It sounds a bit like some NAT issue in the router and the first client > connecting to Skype wins. No sure, though. I'm going on a few assumptions that I'll have to verify, but a reboot of the router should flush the "first" client, but as of today,it's always the laptop client who wins and the phone who fails. Thanks for your help. J ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sysutils/dvdisaster coredumps on FreeBSD/amd64 RELENG_9
Hi C. P. and all,
@Carsten: I hope you can pinpoint the problem. I suspect
a change in FreeBSD's CAM layer API/ABI that causes some
sort of buffer overrun on RELENG_9. The patch points to the
exact line of code that causes dvdisaster 0.72.3 to crash.
Thanks for the report. You're right about the memory
corruption occurring in the line you commented out;
it's a data size mismatch triggered by a size change
in struct scsi_sense_data.
The attached patch corrects the problem.
A new upstream release will be made after some
more testing.
Cheers,
Carsten
--
Carsten Gnörlich * Project homepage http://www.dvdisaster.org
dvdisaster: Additional error correction for CD and DVD media.
GnuPG FP: 12B3 1535 AF90 3ADE 9E73 BA7E 5A59 0EFE F5F6 C46C
--- /dev/shm/dvdisaster-0.72.3/scsi-freebsd.c 2011-10-02 20:32:04.0 +0200
+++ scsi-freebsd.c 2012-03-11 18:19:09.0 +0100
@@ -177,7 +177,6 @@
Stop("illegal data_mode: %d", data_mode);
}
-
cam_fill_csio(&ccb->csio, 1, NULL, flags, CAM_TAG_ACTION_NONE,//MSG_SIMPLE_Q_TAG,
buf, size, sizeof(struct scsi_sense_data), cdb_size,
120*1000); /* 120 secs timeout */
@@ -194,7 +193,7 @@
/* Extract sense data */
- memcpy(sense, &(ccb->csio.sense_data), sizeof(struct scsi_sense_data));
+ memcpy(sense, &(ccb->csio.sense_data), sizeof(Sense));
if((ccb->ccb_h.status & CAM_STATUS_MASK) == CAM_REQ_CMP)
return 0;
@@ -204,8 +203,6 @@
status = ccb->csio.scsi_status;
return -1;
-
-
}
#endif /* SYS_FREEBSD */
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: sysutils/dvdisaster coredumps on FreeBSD/amd64 RELENG_9
That's excellent. Thank you, Carsten. I'll update the FreeBSD port to
include your patch, and will be watching for the new upstream release.
CPGhost: thank you for your work to track this down.
~crh
On 2012-03-11, Carsten Gnörlich wrote:
Hi C. P. and all,
@Carsten: I hope you can pinpoint the problem. I suspect
a change in FreeBSD's CAM layer API/ABI that causes some
sort of buffer overrun on RELENG_9. The patch points to the
exact line of code that causes dvdisaster 0.72.3 to crash.
Thanks for the report. You're right about the memory
corruption occurring in the line you commented out;
it's a data size mismatch triggered by a size change
in struct scsi_sense_data.
The attached patch corrects the problem.
A new upstream release will be made after some
more testing.
Cheers,
Carsten
--
Carsten Gnörlich * Project homepage http://www.dvdisaster.org
dvdisaster: Additional error correction for CD and DVD media.
GnuPG FP: 12B3 1535 AF90 3ADE 9E73 BA7E 5A59 0EFE F5F6 C46C
--- /dev/shm/dvdisaster-0.72.3/scsi-freebsd.c 2011-10-02 20:32:04.0
+0200
+++ scsi-freebsd.c 2012-03-11 18:19:09.0 +0100
@@ -177,7 +177,6 @@
Stop("illegal data_mode: %d", data_mode);
}
-
cam_fill_csio(&ccb->csio, 1, NULL, flags,
CAM_TAG_ACTION_NONE,//MSG_SIMPLE_Q_TAG,
buf, size, sizeof(struct scsi_sense_data), cdb_size,
120*1000); /* 120 secs timeout */
@@ -194,7 +193,7 @@
/* Extract sense data */
- memcpy(sense, &(ccb->csio.sense_data), sizeof(struct scsi_sense_data));
+ memcpy(sense, &(ccb->csio.sense_data), sizeof(Sense));
if((ccb->ccb_h.status & CAM_STATUS_MASK) == CAM_REQ_CMP)
return 0;
@@ -204,8 +203,6 @@
status = ccb->csio.scsi_status;
return -1;
-
-
}
#endif /* SYS_FREEBSD */
pgpxsFCzYwMY8.pgp
Description: PGP signature
Re: FreeBSD Port: skype-2.1.0.81,1
On 3/11/2012 18:59, Joseph Mingrone wrote: > On Sun, Mar 11, 2012 at 14:33, Matthias Apitz wrote: >> It sounds a bit like some NAT issue in the router and the first client >> connecting to Skype wins. No sure, though. > > I'm going on a few assumptions that I'll have to verify, but a reboot > of the router should flush the "first" client, but as of today,it's > always the laptop client who wins and the phone who fails. I've had issues like this when I was still using Skype. Very hard to trace, but I had the feeling that a login gets bound to a client-id or client version and that failed attempts to log in mark a client-id/client version invalid. When this happened to me, I used the website password reset feature and it would then let me sign on with the new client. It's a shot in the dark, but worth testing. -- Mel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: skype-2.1.0.81,1
El día Sunday, March 11, 2012 a las 02:59:11PM -0300, Joseph Mingrone escribió: > On Sun, Mar 11, 2012 at 14:33, Matthias Apitz wrote: > > It sounds a bit like some NAT issue in the router and the first client > > connecting to Skype wins. No sure, though. > > I'm going on a few assumptions that I'll have to verify, but a reboot > of the router should flush the "first" client, but as of today,it's > always the laptop client who wins and the phone who fails. You are sure that the Skype in the laptop is really down, are yoy? Sometimes it is only away from the desktop and sits (connected) in the background, depending how you close it ... HIH matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: skype-2.1.0.81,1
On Sun, Mar 11, 2012 at 15:39, Mel Flynn wrote: > I've had issues like this when I was still using Skype. Very hard to > trace, but I had the feeling that a login gets bound to a client-id or > client version and that failed attempts to log in mark a > client-id/client version invalid. When this happened to me, I used the > website password reset feature and it would then let me sign on with the > new client. Thanks Mel. This seems plausible, but for the moment won't be necessary because to reset anything because after about an hour the phone successfully signed in while the laptop client was already signed in. I'm starting to understand why you stopped using skype. Searching for alternatives has moved a few places up my priority list. Thanks again Mel and Matthias. J ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Building a port with math/superlu fails: linking a shared obj library adding archive superlu.a fails
I'm about to build a port of the AMES stereopipeline on FreeBSD. Regrettably, a portion of the sources expect to have superlu's library and this library is added as a shared object dependency in IsisIO. As expected, compiling fails with the error [...] IsisInterfaceMapLineScan.cc:92:11: warning: variable 'lon_lat_radius' set but not used [-Wunused-but-set-variable] CXXIsisAdjustCameraModel.lo CXXLD libaspIsisIO.la /usr/local/bin/ld: /usr/local/lib/libsuperlu.a(dgssvx.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libsuperlu.a: could not read symbols: Bad value collect2: ld returned 1 exit status *** [libaspIsisIO.la] Error code 1 [...] Well, the portion in the GNU automake Makefile.am controlling the build of the library in IsisIO looks like this: == # __BEGIN_LICENSE__ # Copyright (C) 2006-2011 United States Government as represented by # the Administrator of the National Aeronautics and Space Administration. # All Rights Reserved. # __END_LICENSE__ # # sources # if MAKE_MODULE_ISISIO include_HEADERS = BaseEquation.h Equation.h PolyEquation.h\ RPNEquation.h DiskImageResourceIsis.h \ IsisCameraModel.h\ IsisInterface.h IsisInterfaceFrame.h\ IsisInterfaceLineScan.h IsisInterfaceMapFrame.h \ IsisInterfaceMapLineScan.h IsisAdjustCameraModel.h libaspIsisIO_la_SOURCES = DiskImageResourceIsis.cc Equation.cc\ PolyEquation.cc RPNEquation.cc IsisInterface.cc \ IsisInterfaceFrame.cc IsisInterfaceLineScan.cc \ IsisInterfaceMapFrame.cc IsisInterfaceMapLineScan.cc \ IsisAdjustCameraModel.cc libaspIsisIO_la_LIBADD = @MODULE_ISISIO_LIBS@ lib_LTLIBRARIES = libaspIsisIO.la endif # # general # AM_CPPFLAGS = @ASP_CPPFLAGS@ AM_LDFLAGS = @ASP_LDFLAGS@ -version-info @LIBTOOL_VERSION@ SUBDIRS = . tests includedir = $(prefix)/include/asp/IsisIO include $(top_srcdir)/config/rules.mak == libaspIsisIO_la_LIBADD = @MODULE_ISISIO_LIBS@ seems the bad place causing the error, since MODULE_ISISIO_LIBS is expanded containing -lsuperlu, but the "lib" is an archive /usr/local/lib/superlu.a. Well, I didn't check how the thing called Linux is welding together this library and what they do by compiling the AMES Stereo Pipeline. Well, contact me by MAIL (do not subscribe this list!), if you have suggestions or tips and want to share with me. Regards, Oliver signature.asc Description: OpenPGP digital signature
Re: Building a port with math/superlu fails: linking a shared obj library adding archive superlu.a fails
On 3/11/2012 20:39, O. Hartmann wrote: > [...] > IsisInterfaceMapLineScan.cc:92:11: warning: variable 'lon_lat_radius' > set but not used [-Wunused-but-set-variable] > CXXIsisAdjustCameraModel.lo > CXXLD libaspIsisIO.la > /usr/local/bin/ld: /usr/local/lib/libsuperlu.a(dgssvx.o): relocation > R_X86_64_32 against `.rodata.str1.1' can not be used when making a > shared object; recompile with -fPIC > /usr/local/lib/libsuperlu.a: could not read symbols: Bad value > collect2: ld returned 1 exit status > *** [libaspIsisIO.la] Error code 1 Are you using USE_AUTOTOOLS=libtool but not automake? I'm seeing similar issues with zarafa if I do just that. If I let the port use the provided libtool *or* use the entire autotools toolchain, then all is well. Also, adding --with-pic to CONFIGURE_ARGS does not change either outcome. -- Mel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Upgrade port audit now!
Hey, If you have portaudit installed, you should upgrade sooner rather than later! Begin forwarded message: > From: "Simon L. Nielsen" > Subject: cvs commit: ports/ports-mgmt/portaudit Makefile pkg-plist > ports/ports-mgmt/portaudit/files portaudit-cmd.sh > Date: 11 March 2012 21:32:58 GMT > To: ports-committ...@freebsd.org, cvs-po...@freebsd.org, cvs-...@freebsd.org > > simon 2012-03-11 21:32:58 UTC > > FreeBSD ports repository > > Modified files: >ports-mgmt/portaudit Makefile pkg-plist >ports-mgmt/portaudit/files portaudit-cmd.sh > Log: > Portaudit 0.6.0: > > Fix remote code execution which can occur with a specially crafted > audit file. The attacker would need to get the portaudit(1) to > download the bad audit database, e.g. by performing a man in the > middle attack. > > Add signature verification of the portaudit database. The public key > is for the database generated for portaudit.FreeBSD.org is included > in the distribution. > > Submitted by: Michael Gmelin > Reported by:Michael Gmelin , Joerg Scheinert > Security: Remote code execution > Security: > http://vuxml.FreeBSD.org/6d329b64-6bbb-11e1-9166-001e4f0fb9b1.html > Feature safe: yes > With hat: so -- Simon L. B. Nielsen FreeBSD Deputy Security Officer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Building a port with math/superlu fails: linking a shared obj library adding archive superlu.a fails
On 03/11/12 21:47, Mel Flynn wrote: > On 3/11/2012 20:39, O. Hartmann wrote: > >> [...] >> IsisInterfaceMapLineScan.cc:92:11: warning: variable 'lon_lat_radius' >> set but not used [-Wunused-but-set-variable] >> CXXIsisAdjustCameraModel.lo >> CXXLD libaspIsisIO.la >> /usr/local/bin/ld: /usr/local/lib/libsuperlu.a(dgssvx.o): relocation >> R_X86_64_32 against `.rodata.str1.1' can not be used when making a >> shared object; recompile with -fPIC >> /usr/local/lib/libsuperlu.a: could not read symbols: Bad value >> collect2: ld returned 1 exit status >> *** [libaspIsisIO.la] Error code 1 > > Are you using USE_AUTOTOOLS=libtool but not automake? Neither, nor. I need to run a script called "autogen" in the root folder provided with the sources as a pre-configure tagged operation. I tried using USE_AUTOTOOLS= autogen, but this fails. I got it now working so far, except the described error. It isn't possible to compile xxx_la_LTLIBRARIES by merging different libraries with an archive. As of my understanding, the archive of superlu needs to be treated like an ordinary .o file that is compiled into a to-be-created shared object. And in this task I fail, since the whole build logic does not consider an archive. Could math/superlu be compiled that way that it produce a shared object instead of this clumsy ordinary superlu.a archive? > I'm seeing similar issues with zarafa if I do just that. If I let the > port use the provided libtool *or* use the entire autotools toolchain, > then all is well. Also, adding --with-pic to CONFIGURE_ARGS does not > change either outcome. signature.asc Description: OpenPGP digital signature
Re: Updating getmail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, Feb 28, 2012 at 03:55:17PM -0800, Jason Helfman thus spake: >>> Are there any plans to update getmail version 4.23.0 released:20 >>> November 2011 to version 4.25.0 released 1 February 2012? >> >>I am on a business trip right now, but if you want to submit a PR with >>the changes to the new version, I'm would greatly welcome that. I've just committed this update. Thanks for the report! - -jgh - -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (FreeBSD) iF4EAREIAAYFAk9dgYYACgkQXpKtZoyM+6XneQD+Icj/8bb5nnpzJqusFtxlDKqB Uiw5IcesexgvRy88WK4A/0aW37wIiUW3iSM6PEAukzGU0rTgfvBK+caF1Ip2gT5J =RUNB -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portupgrade -> portmaster Rosetta Stone?
On Feb 25, 2012, at 10:21 AM, Royce Williams wrote: > I noticed that the portupgrade port got returned to ports@ with this note: > > ports-mgmt/portupgrade > - Reassign to ports@ > please consider using ports-mgmt/portmaster > > Discussed with: bugmeister(eadler, linimon), ruby(swills, pgollucci) via > #bsdports > 22 Feb 2012 - pgollucci > http://www.freshports.org/ports-mgmt/portupgrade/ > > > To ease the transition, does anyone know of a Rosetta Stone table, or > "portmaster for native speakers of port upgrade" Please note, however, that this does not mean that port upgrade disappears. The latest version is available on the github and the portupgrade-devel port was set up to track the github version. Not sure what happened to that port since then. The recommendation to switch is just seems to be an opinion of the people listed on the "discussed with" line. The application itself was never supported by ports people and mostly is a work of two outstanding individuals, Akinori MUSHA and Sergey Matveychuk. I'm trying to keep it in a working shape as much as I could. -- ST4096-RIPE ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
