Re: emulators/linux_base-f10 poudriere (3.1pre)
On Wed, 13 Aug 2014 21:16:43 +0200 Matthias Apitz g...@unixarea.de wrote: I' building my ports with poudriere 3.1pre on head. The port emulators/linux_base-f10 can not be build due to a problem with one file listed in the Makefile which seems to not exist anymore (or at least not with the correct SHA256 signature and filesize). What makes me wonder is that the file gamin-0.1.9-6.fc10.src.rpm itself is not used to build the port, poudriere only stops because it can not fetch this file; For GPLed binaries (RPMs) we have the obligation to provide the src (SRPMs). As such the src needs to be fetched on the FreeBSD ports build cluster and provided together with the binaries. If one builds the port normal (with make install) the missing file is not an issue and the port just installs fine. [...] If I comment out the single file, poudriere is happy. Why the normal 'make install' can build the port and poudriere can not? On a normal install PACKAGE_BUILDING is not defined. I assume poudriere is defining it. I don't know of PACAKGE_BULDING implies BATCH or if BATCH is enough to build non-interactively. So a quick solution could be to remove this PACKAGE_BULDING from non-FreeBSD-ports-build-cluster builds. The right solution is to check where the missing file can be found and commit a fix to the port. Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0xC773696B3BAC17DC http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0xC773696B3BAC17DC ___ 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 ports you maintain which are out of date
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 can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ net/openvswitch | 1.7.1 | 2.3.0 +-+ net-mgmt/pandorafms_agent | 4.0.1 | 5.1-140815 +-+ net-mgmt/pandorafms_console | 4.0.1 | 5.1-140815 +-+ net-mgmt/pandorafms_server | 4.0.1 | 5.1-140815 +-+ net-p2p/opendchub | 0.8.2 | 0.8.3 +-+ www/groupoffice | 3.7.24 | 6.0.16 +-+ www/mini_httpd | 1.19| 1.20 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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: Ports, pkg's confusion on upgrades...
W dniu 2014-08-13 o 11:45, Karl Pielorz pisze: We have a number of 10.x systems now - where we install packages (aka pkg install) some components, but other components we build from ports (as we need to add / remove options that the package gives you no choice over). Initially 'pkg upgrade' wanted to replace the port versions with pkg versions (which include options we don't want, and would have pulled in a lot of other dependencies). I seem to have fixed this by 'locking' them (i.e. pkg lock) - pkg upgrade doesn't want to touch them now, which is good. But, 'pkg upgrade' still wants to pull in more packages than are installed - i.e. 'pkg upgrade' shows entries under to be INSTALLED as well as to be UPGRADED. 'pkg info -a -d' displays the dependencies of all installed packages (none of which depend on the package it wants to install) - but I can't seem to find any way to get 'pkg upgrade' to tell me why it wants to install a new package (i.e. which *upgrade* is it doing that now requires the to be INSTALLED packages?) You could solve this by using your own poudriere - create repos with your own port's options and pkg upgrade everything. Your current approach - mixing packages and ports - is not supported IIRC. -- best regards, Lukasz Wasikowski ___ 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: Ports, pkg's confusion on upgrades...
--On 15 August 2014 12:52 +0200 Łukasz Wąsikowski luk...@wasikowski.net wrote: You could solve this by using your own poudriere - create repos with your own port's options and pkg upgrade everything. Your current approach - mixing packages and ports - is not supported IIRC. Thanks for the suggestion - and I take your point about not mixing ports packages... Setting up our own pkg repo though sounds like a lot of work (all for the sake of about probably 2 packages we need to change the options on) - I'd guess there's no way of telling pkg to use 'our' repo for these 2-3 packages, and the main one for everything else? I suppose the other option is just ignore packages, and stick to ports? (presuming ports will always be around :) I'd also still like to know if there's a way of getting 'pkg upgrade' to spit out why it wants to install a 'new package' - when none of the current packages have a dependency on it? This is going to happen at some point, even on a pkg only system (e.g. what happens when pkg upgrade says it's going to install X11 [which nothing currently 'depends' on] - but obviously some upgraded package does - you'd really want to know what's going to cause X to be installed? -Karl ___ 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: emulators/linux_base-f10 poudriere (3.1pre)
El día Friday, August 15, 2014 a las 12:12:53PM +0200, Alexander Leidinger escribió: For GPLed binaries (RPMs) we have the obligation to provide the src (SRPMs). As such the src needs to be fetched on the FreeBSD ports build cluster and provided together with the binaries. I understand. On a normal install PACKAGE_BUILDING is not defined. I assume poudriere is defining it. I don't know of PACAKGE_BULDING implies BATCH or if BATCH is enough to build non-interactively. So a quick solution could be to remove this PACKAGE_BULDING from non-FreeBSD-ports-build-cluster builds. The right solution is to check where the missing file can be found and commit a fix to the port. I spent hours in googling around and fetching files with that name gamin-0.1.9-6.fc10.src.rpm from servers all over the world. I could not find any which matches the SIZE and SHA256 signature. And, I'm not the authority to decide which one is the correct file. There are some with a size of around 650 KByte, while the distinfo file says some 10K: $ fgrep gamin-0.1.9-6.fc10.src.rpm distinfo.i386 SHA256 (rpm/i386/fedora/10/gamin-0.1.9-6.fc10.src.rpm) = cd3be5866aae06398e919eaa412af2d92b04b63139dc1a20e8377c5bf98c0e84 SIZE (rpm/i386/fedora/10/gamin-0.1.9-6.fc10.src.rpm) = 10649 Over to maintainer :-) Thanks matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ 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: Ports, pkg's confusion on upgrades...
By letting 'pkg upgrade' complete, then running 'pkg info --all -d' I was able to find out what package upgrade now requires an additional package to be INSTALLED. (In our case memcached-1.4.20_2 pkg now requires cyrus-sasl-2.1.26_8 - where as it didn't before). I still can't figure out how to get pkg upgrade to reveal *why* it needs to install this, *before* it does it (i.e. only by letting it do it, then running 'pkg info --all -d' did it then show memcached having a dependency on cyrus - where as the older version of memcached didn't. -Karl ___ 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: Ports, pkg's confusion on upgrades...
On 15 Aug 2014, at 14:43, Karl Pielorz kpielorz_...@tdx.co.uk wrote: --On 15 August 2014 12:52 +0200 Łukasz Wąsikowski luk...@wasikowski.net wrote: You could solve this by using your own poudriere - create repos with your own port's options and pkg upgrade everything. Your current approach - mixing packages and ports - is not supported IIRC. Thanks for the suggestion - and I take your point about not mixing ports packages... Setting up our own pkg repo though sounds like a lot of work (all for the sake of about probably 2 packages we need to change the options on) - I'd guess there's no way of telling pkg to use 'our' repo for these 2-3 packages, and the main one for everything else? If it's only about two or three ports and those are leave ports (things like nginx), mixing pkg and ports works ok in practice. I suppose the other option is just ignore packages, and stick to ports? (presuming ports will always be around :) I'd also still like to know if there's a way of getting 'pkg upgrade' to spit out why it wants to install a 'new package' - when none of the current packages have a dependency on it? This is going to happen at some point, even on a pkg only system (e.g. what happens when pkg upgrade says it's going to install X11 [which nothing currently 'depends' on] - but obviously some upgraded package does - you'd really want to know what's going to cause X to be installed? -Karl ___ 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-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: Ports, pkg's confusion on upgrades...
--On 15 August 2014 15:59 +0200 Michael Gmelin free...@grem.de wrote: If it's only about two or three ports and those are leave ports (things like nginx), mixing pkg and ports works ok in practice. This is currently the easiest option for us - I was hoping to install the ports, and just do 'pkg lock' to lock them... The thing that stumped me was why 'pkg upgrade' was trying to install additional packages (some of which on other machines will be 'locked' because they're built from ports). At this stage pkg upgrade -d would be good :) -Karl ___ 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
Bugzilla Restoration
Hi, Does anyone have any idea about possible restoration time of Bugzilla ? BR, Muhammad ___ 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
[CFT] New upstream snapshot of mplayer and mencoder
Hi folks,
I have prepared an update to our ports for multimedia/mplayer and mencoder.
You can find the drop-in replacements (just extract it in
${PORTSDIR}/multimedia) at this url:
https://people.freebsd.org/~riggs/m20140815.tar.xz
Changes
- Update to recent snapshot (2014-08-15) of mplayer and ffmpeg.
- GUI is no longer default OPTION. My perception is that most users
use mplayer from the command line only or through 3rd party UIs. Let
me know in case this is not true.
Feedback is appreciated, as always.
Best regards
RIggs
___
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: Does pkg automatically download INDEX?
On 08/12/14 14:11, Patrick Powell wrote: On 08/09/14 18:15, Naram Qashat wrote: On 08/09/14 19:45, Scot Hetzel wrote: On Fri, Aug 8, 2014 at 7:00 PM, Naram Qashat cyberb...@cyberbotx.com wrote: On 08/04/14 07:28, David Wolfskill wrote: On Mon, Aug 04, 2014 at 07:09:33AM -0400, Naram Qashat wrote: On 08/03/14 22:14, David Wolfskill wrote: On Sun, Aug 03, 2014 at 10:10:27PM -0400, Naram Qashat wrote: ... If there is a way to find out when any process is attempting to modify a file, that would probably help me narrow it down, but I'm not aware of anything that can do that, ... Well, chflags schg /usr/ports/INDEX* would *prevent* the modification ... This was a really good suggestion. Glad to help. :-) Peace, david OK, so while no programs have whined or complained, I get the feeling that something on my system is running portsnap without my knowledge. When I had set the schg flag on INDEX-9, an INDEX-9.bz2 file came up. I set the schg flag on that as well, and now I notice there are a bunch of files called .fetch.??.INDEX-9.bz2 (where ?? is a random string), as well as a file called .portsnap.INDEX. As far as I know, I don't have anything configured to run portsnap, but is there something that defaults to running portsnap occasionally? I couldn't find anything that would do that. Do your have a crontab entry that is running portsnap with the -I (update INDEX) option? http://www.pl.freebsd.org/doc/handbook/portsnap.html As far as I can tell, no, none of my crontabs have any references to portsnap in them. This is making me a bit stumped as to why it would be happening. I checked the main /etc/crontab, I checked the crontabs in /var/cron/tabs. I have searched inside of /etc and /usr/local/etc for anything related to portsnap. Nothing that would be doing this is coming up at all. Thanks, Naram Qashat ___ 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 ran into something similar once, and found out what was happening this way. 1. replace the portsnap executable with a shell script. Rename portsnap to something like /usr/sbin/portsnap.orig 2. This shell script should dump the current ENV and other stuff to a log file. Don't forget to put in a timestamp. And then do: exec /usr/sbin/portsnap.orig $* I did this and found that there was something in one of the .login scripts. G... I really liked this suggestion, and did just that. Unfortunately, it seems that portsnap may not be the culprit here, as I haven't had any log files created from my modified script nor is there a .portsnap.INDEX file being created after I deleted the one that was there, but I still have a bunch of .fetch.??.INDEX-9.bz2 files in /usr/ports. I've been trying to search for anything on my system that even references INDEX-9, but I can't find anything else that would cause this to happen. Thanks, Naram Qashat ___ 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: emulators/linux_base-f10 poudriere (3.1pre)
On Fri, Aug 15, 2014 at 03:49:47PM +0200, Matthias Apitz wrote: El día Friday, August 15, 2014 a las 12:12:53PM +0200, Alexander Leidinger escribió: For GPLed binaries (RPMs) we have the obligation to provide the src (SRPMs). As such the src needs to be fetched on the FreeBSD ports build cluster and provided together with the binaries. I understand. On a normal install PACKAGE_BUILDING is not defined. I assume poudriere is defining it. I don't know of PACAKGE_BULDING implies BATCH or if BATCH is enough to build non-interactively. So a quick solution could be to remove this PACKAGE_BULDING from non-FreeBSD-ports-build-cluster builds. The right solution is to check where the missing file can be found and commit a fix to the port. I spent hours in googling around and fetching files with that name gamin-0.1.9-6.fc10.src.rpm from servers all over the world. I could not find any which matches the SIZE and SHA256 signature. And, I'm not the authority to decide which one is the correct file. There are some with a size of around 650 KByte, while the distinfo file says some 10K: $ fgrep gamin-0.1.9-6.fc10.src.rpm distinfo.i386 SHA256 (rpm/i386/fedora/10/gamin-0.1.9-6.fc10.src.rpm) = cd3be5866aae06398e919eaa412af2d92b04b63139dc1a20e8377c5bf98c0e84 SIZE (rpm/i386/fedora/10/gamin-0.1.9-6.fc10.src.rpm) = 10649 Over to maintainer :-) Thanks matthias I still have that file, and it's not an rpm, it's html. (attached) SHA256 (/usr/ports/distfiles/rpm/i386/fedora/10/gamin-0.1.9-6.fc10.src.rpm) = cd3be5866aae06398e919eaa412af2d92b04b63139dc1a20e8377c5bf98c0e84 So probably the 650k one should be used instead... HTH, Juergen [1]SEARCH [2]NEWS [3]DIRECTORIES [4]ABOUT [5]FAQ [6]VARIOUS [7]BLOG [8]FORUM [9]DONATE [10]YUM REPOSITORY You have chosen search rpm in world FTP resources. Not enough search parameters. I'm using defaults. Display 1 - 2 hits of 2. Search took 0.01 seconds. 1 1 Search results for gamin-0.1.9-6.fc10.src.rpm : Filename Distribution File size [11]gamin-0.1.9-6.fc10.src.rpm Fedora 10 647 kB [12]gamin-0.1.9-6.fc10.src.rpm Fedora 10 647 kB 1 1 [13]internet katowice Designed by station75 References 1. http://rpm.pbone.net/ 2. file:///index.php3/stat/1/data/2012-06-26 3. file:///index.php3/stat/20 4. file:///index.php3/stat/5 5. file:///index.php3/stat/19 6. file:///index.php3/stat/8 7. file:///index.php3/stat/25 8. file:///phpBB2/ 9. file:///index.php3/stat/30 10. file:///index.php3/stat/39 11. file:///index.php3/stat/26/dist/65/size/662108/name/gamin-0.1.9-6.fc10.src.rpm 12. file:///index.php3/stat/26/dist/65/size/662268/name/gamin-0.1.9-6.fc10.src.rpm 13. http://www.3sdlafirm.pl/ ___ 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: emulators/linux_base-f10 poudriere (3.1pre)
On Fri, Aug 15, 2014 at 07:50:04PM +0200, Juergen Lock wrote: On Fri, Aug 15, 2014 at 03:49:47PM +0200, Matthias Apitz wrote: El día Friday, August 15, 2014 a las 12:12:53PM +0200, Alexander Leidinger escribió: For GPLed binaries (RPMs) we have the obligation to provide the src (SRPMs). As such the src needs to be fetched on the FreeBSD ports build cluster and provided together with the binaries. I understand. On a normal install PACKAGE_BUILDING is not defined. I assume poudriere is defining it. I don't know of PACAKGE_BULDING implies BATCH or if BATCH is enough to build non-interactively. So a quick solution could be to remove this PACKAGE_BULDING from non-FreeBSD-ports-build-cluster builds. The right solution is to check where the missing file can be found and commit a fix to the port. I spent hours in googling around and fetching files with that name gamin-0.1.9-6.fc10.src.rpm from servers all over the world. I could not find any which matches the SIZE and SHA256 signature. And, I'm not the authority to decide which one is the correct file. There are some with a size of around 650 KByte, while the distinfo file says some 10K: $ fgrep gamin-0.1.9-6.fc10.src.rpm distinfo.i386 SHA256 (rpm/i386/fedora/10/gamin-0.1.9-6.fc10.src.rpm) = cd3be5866aae06398e919eaa412af2d92b04b63139dc1a20e8377c5bf98c0e84 SIZE (rpm/i386/fedora/10/gamin-0.1.9-6.fc10.src.rpm) = 10649 Over to maintainer :-) Thanks matthias I still have that file, and it's not an rpm, it's html. (attached) SHA256 (/usr/ports/distfiles/rpm/i386/fedora/10/gamin-0.1.9-6.fc10.src.rpm) = cd3be5866aae06398e919eaa412af2d92b04b63139dc1a20e8377c5bf98c0e84 So probably the 650k one should be used instead... HTH, Juergen [1]SEARCH [2]NEWS [3]DIRECTORIES [4]ABOUT [5]FAQ [6]VARIOUS [7]BLOG [8]FORUM [9]DONATE [10]YUM REPOSITORY You have chosen search rpm in world FTP resources. Not enough search parameters. I'm using defaults. Display 1 - 2 hits of 2. Search took 0.01 seconds. 1 1 Search results for gamin-0.1.9-6.fc10.src.rpm : Filename Distribution File size [11]gamin-0.1.9-6.fc10.src.rpm Fedora 10 647 kB [12]gamin-0.1.9-6.fc10.src.rpm Fedora 10 647 kB 1 1 [13]internet katowice Designed by station75 References 1. http://rpm.pbone.net/ 2. file:///index.php3/stat/1/data/2012-06-26 3. file:///index.php3/stat/20 4. file:///index.php3/stat/5 5. file:///index.php3/stat/19 6. file:///index.php3/stat/8 7. file:///index.php3/stat/25 8. file:///phpBB2/ 9. file:///index.php3/stat/30 10. file:///index.php3/stat/39 11. file:///index.php3/stat/26/dist/65/size/662108/name/gamin-0.1.9-6.fc10.src.rpm 12. file:///index.php3/stat/26/dist/65/size/662268/name/gamin-0.1.9-6.fc10.src.rpm 13. http://www.3sdlafirm.pl/ ___ freebsd-emulat...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org Hmm looks like the list software mangled the file, I've put it here: https://people.freebsd.org/~nox/tmp/distfiles/gamin-0.1.9-6.fc10.src.rpm HTH, Juergen ___ 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
Cacti staged and migration issue (was Re: FreeBSD unmaintained ports which are currently scheduled for deletion)
Hi! Consequently, I have no idea how to set the owner/group on those directories in stagedir. As can be seen, with some help I was able to find a solution. I also changed the patches to shebangfixes 8-} But: There's a real issue coming up in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192618#c13 Can you have a look and probably provide a write-up on how to migrate a running cacti install to the new hier(7) setup ? -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ 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: emulators/linux_base-f10 poudriere (3.1pre)
On Fri, 15 Aug 2014 19:50:04 +0200 Juergen Lock n...@jelal.kn-bremen.de wrote: So probably the 650k one should be used instead... I'm looking into this right now. Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0xC773696B3BAC17DC http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0xC773696B3BAC17DC ___ 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: emulators/linux_base-f10 poudriere (3.1pre)
El día Friday, August 15, 2014 a las 07:50:04PM +0200, Juergen Lock escribió: I still have that file, and it's not an rpm, it's html. (attached) SHA256 (/usr/ports/distfiles/rpm/i386/fedora/10/gamin-0.1.9-6.fc10.src.rpm) = cd3be5866aae06398e919eaa412af2d92b04b63139dc1a20e8377c5bf98c0e84 So probably the 650k one should be used instead... I.e. I was searching hours in Internet because someone commited into the distfile the signatures of the nonsense of a HTML error page? Nice :-) matthias You have chosen search rpm in world FTP resources. Not enough search parameters. I'm using defaults. Display 1 - 2 hits of 2. Search took 0.01 seconds. Search results for gamin-0.1.9-6.fc10.src.rpm : Filename Distribution File size [11]gamin-0.1.9-6.fc10.src.rpm Fedora 10 647 kB [12]gamin-0.1.9-6.fc10.src.rpm Fedora 10 647 kB -- Matthias Apitz | /\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ 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: emulators/linux_base-f10 poudriere (3.1pre)
On Fri, 15 Aug 2014 22:16:52 +0200 Matthias Apitz g...@unixarea.de wrote: El día Friday, August 15, 2014 a las 07:50:04PM +0200, Juergen Lock escribió: I still have that file, and it's not an rpm, it's html. (attached) SHA256 (/usr/ports/distfiles/rpm/i386/fedora/10/gamin-0.1.9-6.fc10.src.rpm) = cd3be5866aae06398e919eaa412af2d92b04b63139dc1a20e8377c5bf98c0e84 So probably the 650k one should be used instead... I.e. I was searching hours in Internet because someone commited into the distfile the signatures of the nonsense of a HTML error page? I'm glad I entertained you... ;-) No, I didn't check if it was really me committing those entries. Nice :-) Fixed now. Would be nice if you could update and test. Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0xC773696B3BAC17DC http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0xC773696B3BAC17DC ___ 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
Fwd: [package - 84i386-default][cad/cura-engine] Failed for CuraEngine-14.03 in build
Hello :-) There seems to be a problem with CAD/Cura-Engine build on FreeBSD 8.4-RELEASE i386. I try to reproduce this bug on a fresh install... Build somehow requires CLANG to build, but the default compiler on 8.4 is the GCC. I did not set CLANG to be dependency, port can be built with GCC. Why GLANG is the default compiler? Any hints appreciated :-) Tomek -- Forwarded message -- From: pkg-fallout Date: Sat, Aug 16, 2014 at 1:39 AM Subject: [package - 84i386-default][cad/cura-engine] Failed for CuraEngine-14.03 in build To: cederom Cc: pkg-fallout You are receiving this mail as a port that you maintain is failing to build on the FreeBSD package build server. Please investigate the failure and submit a PR to fix build. Maintainer: cede...@tlen.pl Last committer: anto...@freebsd.org Ident: $FreeBSD: head/cad/cura-engine/Makefile 364532 2014-08-10 12:31:43Z antoine $ Log URL: http://beefy1.isc.freebsd.org/data/84i386-default/2014-08-15_14h18m35s/logs/CuraEngine-14.03.log Build URL: http://beefy1.isc.freebsd.org/build.html?mastername=84i386-defaultbuild=2014-08-15_14h18m35s Log: Building cad/cura-engine build started at Fri Aug 15 23:39:04 UTC 2014 port directory: /usr/ports/cad/cura-engine building for: FreeBSD 84i386-default-job-16 8.4-RELEASE-p14 FreeBSD 8.4-RELEASE-p14 i386 maintained by: cede...@tlen.pl Makefile ident: $FreeBSD: head/cad/cura-engine/Makefile 364532 2014-08-10 12:31:43Z antoine $ Poudriere version: 3.1-pre Host OSVERSION: 1100027 Jail OSVERSION: 804000 ---Begin Environment--- UNAME_m=i386 UNAME_p=i386 OSVERSION=804000 UNAME_v=FreeBSD 8.4-RELEASE-p14 UNAME_r=8.4-RELEASE-p14 FTP_PASSIVE_MODE=YES BLOCKSIZE=K MAIL=/var/mail/root STATUS=1 SAVED_TERM=screen MASTERMNT=/usr/local/poudriere/data/.m/84i386-default/ref PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin POUDRIERE_BUILD_TYPE=bulk PKGNAME=CuraEngine-14.03 OLDPWD=/root/poudriere PWD=/usr/local/poudriere/data/.m/84i386-default/ref/.p/pool MASTERNAME=84i386-default USER=root HOME=/root POUDRIERE_VERSION=3.1-pre LOCALBASE=/usr/local PACKAGE_BUILDING=yes ---End Environment--- ---Begin OPTIONS List--- ---End OPTIONS List--- --CONFIGURE_ARGS-- --End CONFIGURE_ARGS-- --CONFIGURE_ENV-- XDG_DATA_HOME=/wrkdirs/usr/ports/cad/cura-engine/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/cad/cura-engine/work HOME=/wrkdirs/usr/ports/cad/cura-engine/work TMPDIR=/tmp MAKE=gmake SHELL=/bin/sh CONFIG_SHELL=/bin/sh --End CONFIGURE_ENV-- --MAKE_ENV-- XDG_DATA_HOME=/wrkdirs/usr/ports/cad/cura-engine/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/cad/cura-engine/work HOME=/wrkdirs/usr/ports/cad/cura-engine/work TMPDIR=/tmp NO_PIE=yes SHELL=/bin/sh NO_LINT=YES ADDR2LINE=/usr/local/bin/addr2line AR=/usr/local/bin/ar AS=/usr/local/bin/as CPPFILT=/usr/local/bin/c++filt GPROF=/usr/local/bin/gprof LD=/usr/local/bin/ld NM=/usr/local/bin/nm OBJCOPY=/usr/local/bin/objcopy OBJDUMP=/usr/local/bin/objdump RANLIB=/usr/local/bin/ranlib READELF=/usr/local/bin/readelf SIZE=/usr/local/bin/size STRINGS=/usr/local/bin/strings PREFIX=/usr/local LOCALBASE=/usr/local LIBDIR=/usr/lib CC=/usr/local/bin/clang33 CFLAGS=-O2 -pipe -fno-strict-aliasing CPP=/usr/local/bin/clang-cpp33 CPPFLAGS= LDFLAGS= -B/usr/local/bin LIBS= CXX=/usr/local/bin/clang++33 CXXFLAGS=-O2 -pipe -fno-strict-aliasing MANPREFIX=/usr/local BSD_INSTALL_PROGRAM=install -s -o root -g wheel -m 555 BSD_INSTALL_LIB=install -s -o r oot -g w heel -m 444 BSD_INSTALL_SCRIPT=install -o root -g wheel -m 555 BSD_INSTALL_DATA=install -o root -g wheel -m 444 BSD_INSTALL_MAN=install -o root -g wheel -m 444 --End MAKE_ENV-- --PLIST_SUB-- OSREL=8.4 PREFIX=%D LOCALBASE=/usr/local PORTDOCS= PORTEXAMPLES= PORTDATA= LIB32DIR=lib DOCSDIR=share/doc/CuraEngine EXAMPLESDIR=share/examples/CuraEngine DATADIR=share/CuraEngine WWWDIR=www/CuraEngine ETCDIR=etc/CuraEngine --End PLIST_SUB-- --SUB_LIST-- PREFIX=/usr/local LOCALBASE=/usr/local DATADIR=/usr/local/share/CuraEngine DOCSDIR=/usr/local/share/doc/CuraEngine EXAMPLESDIR=/usr/local/share/examples/CuraEngine WWWDIR=/usr/local/www/CuraEngine ETCDIR=/usr/local/etc/CuraEngine --End SUB_LIST-- ---Begin make.conf--- ARCH=i386 MACHINE=i386 MACHINE_ARCH=i386 USE_PACKAGE_DEPENDS=yes BATCH=yes WRKDIRPREFIX=/wrkdirs ARCH=i386 MACHINE=i386 MACHINE_ARCH=i386 USE_PACKAGE_DEPENDS=yes BATCH=yes WRKDIRPREFIX=/wrkdirs PORTSDIR=/usr/ports PACKAGES=/packages DISTDIR=/distfiles /usr/local/etc/poudriere.d/make.conf WITH_PKGNG=yes # clean-restricted via poudriere.conf NO_RESTRICTED #NO_RESTRICTED=yes DISABLE_MAKE_JOBS=poudriere ---End make.conf--- ===phase: check-sanity === License AGPLv3 accepted by the user === ===phase: pkg-depends === CuraEngine-14.03 depends on file: /usr/local/sbin/pkg - not found ===Verifying install for
Re: Fwd: [package - 84i386-default][cad/cura-engine] Failed for CuraEngine-14.03 in build
CeDeROM wrote: Hello :-) There seems to be a problem with CAD/Cura-Engine build on FreeBSD 8.4-RELEASE i386. I try to reproduce this bug on a fresh install... Build somehow requires CLANG to build, but the default compiler on 8.4 is the GCC. I did not set CLANG to be dependency, port can be built with GCC. Why GLANG is the default compiler? Any hints appreciated :-) IIRC a few weeks back the default compiler was switched to CLANG across all ports - now you have to tell ports to specifically use GCC if it won't build with CLANG. Regards, Michelle Tomek -- Forwarded message -- From: pkg-fallout Date: Sat, Aug 16, 2014 at 1:39 AM Subject: [package - 84i386-default][cad/cura-engine] Failed for CuraEngine-14.03 in build To: cederom Cc: pkg-fallout You are receiving this mail as a port that you maintain is failing to build on the FreeBSD package build server. Please investigate the failure and submit a PR to fix build. Maintainer: cede...@tlen.pl Last committer: anto...@freebsd.org Ident: $FreeBSD: head/cad/cura-engine/Makefile 364532 2014-08-10 12:31:43Z antoine $ Log URL: http://beefy1.isc.freebsd.org/data/84i386-default/2014-08-15_14h18m35s/logs/CuraEngine-14.03.log Build URL: http://beefy1.isc.freebsd.org/build.html?mastername=84i386-defaultbuild=2014-08-15_14h18m35s Log: Building cad/cura-engine build started at Fri Aug 15 23:39:04 UTC 2014 port directory: /usr/ports/cad/cura-engine building for: FreeBSD 84i386-default-job-16 8.4-RELEASE-p14 FreeBSD 8.4-RELEASE-p14 i386 maintained by: cede...@tlen.pl Makefile ident: $FreeBSD: head/cad/cura-engine/Makefile 364532 2014-08-10 12:31:43Z antoine $ Poudriere version: 3.1-pre Host OSVERSION: 1100027 Jail OSVERSION: 804000 ---Begin Environment--- UNAME_m=i386 UNAME_p=i386 OSVERSION=804000 UNAME_v=FreeBSD 8.4-RELEASE-p14 UNAME_r=8.4-RELEASE-p14 FTP_PASSIVE_MODE=YES BLOCKSIZE=K MAIL=/var/mail/root STATUS=1 SAVED_TERM=screen MASTERMNT=/usr/local/poudriere/data/.m/84i386-default/ref PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin POUDRIERE_BUILD_TYPE=bulk PKGNAME=CuraEngine-14.03 OLDPWD=/root/poudriere PWD=/usr/local/poudriere/data/.m/84i386-default/ref/.p/pool MASTERNAME=84i386-default USER=root HOME=/root POUDRIERE_VERSION=3.1-pre LOCALBASE=/usr/local PACKAGE_BUILDING=yes ---End Environment--- ---Begin OPTIONS List--- ---End OPTIONS List--- --CONFIGURE_ARGS-- --End CONFIGURE_ARGS-- --CONFIGURE_ENV-- XDG_DATA_HOME=/wrkdirs/usr/ports/cad/cura-engine/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/cad/cura-engine/work HOME=/wrkdirs/usr/ports/cad/cura-engine/work TMPDIR=/tmp MAKE=gmake SHELL=/bin/sh CONFIG_SHELL=/bin/sh --End CONFIGURE_ENV-- --MAKE_ENV-- XDG_DATA_HOME=/wrkdirs/usr/ports/cad/cura-engine/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/cad/cura-engine/work HOME=/wrkdirs/usr/ports/cad/cura-engine/work TMPDIR=/tmp NO_PIE=yes SHELL=/bin/sh NO_LINT=YES ADDR2LINE=/usr/local/bin/addr2line AR=/usr/local/bin/ar AS=/usr/local/bin/as CPPFILT=/usr/local/bin/c++filt GPROF=/usr/local/bin/gprof LD=/usr/local/bin/ld NM=/usr/local/bin/nm OBJCOPY=/usr/local/bin/objcopy OBJDUMP=/usr/local/bin/objdump RANLIB=/usr/local/bin/ranlib READELF=/usr/local/bin/readelf SIZE=/usr/local/bin/size STRINGS=/usr/local/bin/strings PREFIX=/usr/local LOCALBASE=/usr/local LIBDIR=/usr/lib CC=/usr/local/bin/clang33 CFLAGS=-O2 -pipe -fno-strict-aliasing CPP=/usr/local/bin/clang-cpp33 CPPFLAGS= LDFLAGS= -B/usr/local/bin LIBS= CXX=/usr/local/bin/clang++33 CXXFLAGS=-O2 -pipe -fno-strict-aliasing MANPREFIX=/usr/local BSD_INSTALL_PROGRAM=install -s -o root -g wheel -m 555 BSD_INSTALL_LIB=install -s -o r oot -g w heel -m 444 BSD_INSTALL_SCRIPT=install -o root -g wheel -m 555 BSD_INSTALL_DATA=install -o root -g wheel -m 444 BSD_INSTALL_MAN=install -o root -g wheel -m 444 --End MAKE_ENV-- --PLIST_SUB-- OSREL=8.4 PREFIX=%D LOCALBASE=/usr/local PORTDOCS= PORTEXAMPLES= PORTDATA= LIB32DIR=lib DOCSDIR=share/doc/CuraEngine EXAMPLESDIR=share/examples/CuraEngine DATADIR=share/CuraEngine WWWDIR=www/CuraEngine ETCDIR=etc/CuraEngine --End PLIST_SUB-- --SUB_LIST-- PREFIX=/usr/local LOCALBASE=/usr/local DATADIR=/usr/local/share/CuraEngine DOCSDIR=/usr/local/share/doc/CuraEngine EXAMPLESDIR=/usr/local/share/examples/CuraEngine WWWDIR=/usr/local/www/CuraEngine ETCDIR=/usr/local/etc/CuraEngine --End SUB_LIST-- ---Begin make.conf--- ARCH=i386 MACHINE=i386 MACHINE_ARCH=i386 USE_PACKAGE_DEPENDS=yes BATCH=yes WRKDIRPREFIX=/wrkdirs ARCH=i386 MACHINE=i386 MACHINE_ARCH=i386 USE_PACKAGE_DEPENDS=yes BATCH=yes WRKDIRPREFIX=/wrkdirs PORTSDIR=/usr/ports PACKAGES=/packages DISTDIR=/distfiles /usr/local/etc/poudriere.d/make.conf WITH_PKGNG=yes # clean-restricted via poudriere.conf NO_RESTRICTED #NO_RESTRICTED=yes DISABLE_MAKE_JOBS=poudriere ---End make.conf---
Re: Bugzilla Restoration
On Fri, Aug 15, 2014 at 10:05:20PM +0600, Muhammad Moinur Rahman wrote: Does anyone have any idea about possible restoration time of Bugzilla ? It's working right now. Try deleting your cookies if it doesn't work. -- Denny Lin ___ 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: emulators/linux_base-f10 poudriere (3.1pre)
El día Friday, August 15, 2014 a las 11:03:11PM +0200, Alexander Leidinger escribió: I'm glad I entertained you... ;-) No, I didn't check if it was really me committing those entries. I did not checked it either. Fixed now. Would be nice if you could update and test. I did: # cd /usr/ports/emulators/linux_base-f10 # svn up Updating '.': Udistinfo.i386 UMakefile Actualizado a la revisión 365065. # cp distinfo.i386 Makefile /usr/local/poudriere/ports/ports-head/emulators/linux_base-f10/ # rm /usr/local/poudriere/data/packages/freebsd-head-ports-head/All/linux_base-f10-10_7.txz # poudriere bulk -j freebsd-head -p ports-head emulators/linux_base-f10 [00:00:00] Creating the reference jail... ... [00:02:01] [01][00:00:00] Starting build of emulators/linux_base-f10 [00:03:39] [01][00:01:38] Finished build of emulators/linux_base-f10: Success $ ls -l /usr/ports/distfiles/rpm/i386/fedora/10/gamin-* -rw-r--r-- 1 root wheel 127020 31 oct 2008 /usr/ports/distfiles/rpm/i386/fedora/10/gamin-0.1.9-6.fc10.i386.rpm -rw-r--r-- 1 root wheel 662268 31 oct 2008 /usr/ports/distfiles/rpm/i386/fedora/10/gamin-0.1.9-6.fc10.src.rpm i.e. it fetches the correct file now. Tested positiv. Thanks matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ 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
