Re: Initial squid 3.5 port
Hi! Sorry, my fault. Not a patch for existing port, but a shar file to create new port, which was attached to original message. Just in case, I uploaded it here https://yadi.sk/d/EcRxwc6BevgDc I've created https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089 with that shar and I'm build-testing it right now. Can I put your mail address in the maintainer field ? -- p...@opsec.eu+49 171 3101372 5 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: Initial squid 3.5 port
Ok, I'll do my best. 2015-02-28 14:08 GMT+03:00 Kurt Jaeger li...@opsec.eu: Hi! Just in case, I uploaded it here https://yadi.sk/d/EcRxwc6BevgDc I've created https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089 with that shar and I'm build-testing it right now. build testing: works on 10.1a, fails on 9.3a, 8.4i. poudriere build logs can be found at http://people.freebsd.org/~pi/logs/www__squid35* Older builds are with a custom config, newer builds with the generic config. Can you investigate the cause of the issue ? -- p...@opsec.eu+49 171 3101372 5 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: Initial squid 3.5 port
Well, in general, I don't mind, but I'm afraid I'm not a skillful person. 2015-02-28 11:00 GMT+03:00 Kurt Jaeger li...@opsec.eu: Hi! Sorry, my fault. Not a patch for existing port, but a shar file to create new port, which was attached to original message. Just in case, I uploaded it here https://yadi.sk/d/EcRxwc6BevgDc I've created https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089 with that shar and I'm build-testing it right now. Can I put your mail address in the maintainer field ? -- p...@opsec.eu+49 171 3101372 5 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
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 +-+ science/gramps | 3.4.8 | 4.1.2 +-+ 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: Initial squid 3.5 port
Hi! Just in case, I uploaded it here https://yadi.sk/d/EcRxwc6BevgDc I've created https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198089 with that shar and I'm build-testing it right now. build testing: works on 10.1a, fails on 9.3a, 8.4i. poudriere build logs can be found at http://people.freebsd.org/~pi/logs/www__squid35* Older builds are with a custom config, newer builds with the generic config. Can you investigate the cause of the issue ? -- p...@opsec.eu+49 171 3101372 5 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
FreeBSD Ports failing to build with clang 3.6
Dear maintainer, The FreeBSD project is working on updating llvm and clang to 3.6.0 in head [1]. The following ports you maintain fail to build after this update: security/libtomcrypt http://pb2.nyi.freebsd.org/data/headi386PR197395-default/2015-02-27_12h37m23s/logs/errors/libtomcrypt-1.17_4.log http://package18.nyi.freebsd.org/data/headamd64PR197395-default/2015-02-27_12h37m16s/logs/errors/libtomcrypt-1.17_4.log mail/milter-manager http://pb2.nyi.freebsd.org/data/headi386PR197395-default/2015-02-27_12h37m23s/logs/errors/milter-manager-2.0.4.log http://package18.nyi.freebsd.org/data/headamd64PR197395-default/2015-02-27_12h37m16s/logs/errors/milter-manager-2.0.4.log games/stepmania-devel http://pb2.nyi.freebsd.org/data/headi386PR197395-default/2015-02-27_12h37m23s/logs/errors/stepmania-devel-5.0.a3_4,1.log http://package18.nyi.freebsd.org/data/headamd64PR197395-default/2015-02-27_12h37m16s/logs/errors/stepmania-devel-5.0.a3_4,1.log If you have a patch to fix the ports, please submit them in FreeBSD Bugzilla [2]. [1] https://bugs.freebsd.org/197395 [2] https://bugs.freebsd.org/submit/ Cheers, Antoine on behalf of portmgr@ ___ 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: Enlightenment
Hi Chris, I have been using Enlightenment for a while now and I do like it the best of all Window Managers. However as you already know it has some quirks, so it would be great if someone takes the trouble of trying to fix them. I can send bug reports or related inputs if it helps. Regards Amit ___ 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
pkg wondering...
No pkg failures , but quirks: . 1. Backing up pkgng database: pkg: Ignoring bad configuration entry in /etc/pkg/pkg.conf: /usr/cache/pkg pkg: Ignoring bad configuration entry in /etc/pkg/pkg.conf: INDEX-10 pkg: Ignoring bad configuration entry in /etc/pkg/pkg.conf: freebsd:10:x86:32 Can pkg be smarter and suggest a proper configuration upon error, test a new one locally before suggesting it, or have one firmly tested as working... hesitant to remove the improper entries because then oftentimes, IIRC, what remains causes, or has caused, pkg-* failures with not solution suggested... BTW that series of messages obscures day to day portupgrade updates locally... ten or so lines to each one of the upgrade by portupgrade ... leaving the latter not in context. Something like a sysinstall for pkg (all its files) parsing each one for errors... would be useful for new installs as well as existing ones maybe? .. 2. Another feature maybe missng in pkg-install and pkg-upgrade is the skip this upgrade? new dependencies ; for instance audio/mous is qt4 so I do upgrades with ... | grep -v mous | ... an xargs pipe... However the particular port has to be tested locally of all the list passing through the pipe to xargs. Slows it down some. 3. 4. Less relevant, do not remember them right now... ... A. Don't know if this should fit in this email, but every boot libexpect.so.1 not found required by dbus-daemon ... and another (uuid* ) ... persists even after reinstall of everything known relevant. Ignorable here, but... .. ___ 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
New message from SoundCloud PR
[letter.png] Hey, [1]SoundCloudPR sent you a message: The SoundCloud Promotional Service offers Artists, DJs, Singers and Managers a simple, cost-effective way to reach targeted followers, sales, comments, plays and downloads on SoundCloud. We target like-minded users who are interested in your new tracks, releases and sets. This means that each new user we will follow, will receive a notification from you (like this message), saying that you have followed him or her. In return, these users will check out your profile, follow you back, play, comment, and download your music. By increasing your visibility on SoundCloud, you also improve your chances of getting noticed by records labels, club owners and talent scouts, who might all be looking for the next big catch. Many of our clients have signed records deals, DJ gigs, or simply found new collaboration partners after using our services. Artists that generate a lot of honest consistent feedbacks and traffic to their profiles are the ones who stand out from the crowd. To check this new service, go directly to the [2]SoundCloud Promotion Page - © 2007 - 2015 SoundCloud Ltd. All rights reserved [postman-email-convo-message_sent] [3]Unsubscribe[4] | Manage Notifications | [5]Support | [6]Terms of Use | [7]Community Guidelines | [8]Imprint | [9]Privacy Policy References 1. http://bit.ly/soundcloud-now 2. http://bit.ly/soundcloud-now 3. http://bit.ly/sc-unsubscribe 4. http://soundcloud.com/settings/email 5. http://help.soundcloud.com/ 6. http://soundcloud.com/terms-of-use 7. http://soundcloud.com/community-guidelines 8. http://soundcloud.com/imprint 9. https://soundcloud.com/pages/privacy ___ 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: Generating port changes easily
On Sat, 28 Feb 2015 18:34:40 +1100 Kubilay Kocak ko...@freebsd.org wrote On 28/02/2015 3:35 AM, Patrick Powell wrote: I have made some modifications to a port - couple of lines in the Makefile, and an updated pkg-plist. Once upon a time I was shown a script (run_this_script?) to help with updating a port. 1. Copy the original files in the port to XXX.orig (or something) For example cp Makefile Makefile.orig 2. Make your changes For example: vi Makefile 3. Now run this script which will generate a DIFF file which can be posted: run_this_script ... /tmp/changes.shar ? run_this_script ... /tmp/diffs ? 4. Post the generated file to bugzilla with an update request. Ummm... is there such a 'run_this_script' or am I indulging in wishful thinking? If the changes you make are in the ports files, porttools has a 'port diff' command (which uses a reference ports tree to create diffs against. You can use /usr/ports as that reference, and in fact I believe that is the default. You can then just port diff path-to-patch-file.diff, ready for attachment into a new bugzilla issue. If the patch is against WRKSRC source code, you can a) cp WRKSRC/file WRKSRC/file.orig b) edit file c) make makepatch (from the port dir) makepatch recursively searches WRKSRC for *.orig files, and automatically creates correctly named patch-foo patch files in /files for you. Hope that helps koobs' reply got me to thinking. So I did a little searching around in ports/Tools/scripts and found, I think, exactly what you were referring/hoping for; update-patches Give it a look. It's intended to work almost exactly as you described. HTH --Chris -- koobs ___ 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
[no subject]
D.CAIN ___ 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: Enlightenment
On 2015-02-28 07:21, Amit Sengupta wrote: Hi Chris, I have been using Enlightenment for a while now and I do like it the best of all Window Managers. However as you already know it has some quirks, so it would be great if someone takes the trouble of trying to fix them. I can send bug reports or related inputs if it helps. Regards Amit ___ 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 Send issues on the github project named EPorts please. so once of us can fix them. ___ 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
