Re: Some ports options is broken
Hi! > I have done a fast fix already, your patch is wrong is the way that > OPTIONS_SET > is a end user thing to put in make.conf where OPTIONS_DEFAULT is the one to be > used inside a port Ah, thanks for the hint. > Do you want the PR to remain open because you will add some modification on > top > of my "fast fix" or not? No, you can close the PR. -- p...@opsec.eu+49 171 3101372 8 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: [RFC/HEADSUP] portmaster default -w (preserve shared libraries)
Hi! > > (As maintainer) I'm proposing to make -w the default for portmaster. > > This will preserve old shared libraries when upgrading. This helps 2 things: > > > > [...] > > I have a few question about what happens if you always use this flag: > * Do you keep every version of the shlibs you ever built on your system? No, only those that still needed. > * Are there any method to clean the unused ones? sysutils/libchk or pkg_libchk from sysutils/bsdadminscripts. > * What do we do about libraries versions that have security issues > and that we need to get out asap? Currently: The admin decides how he wants to handle this. If there is a efficient way to handle this, most admins will use it. I do not see an time- and cpu-efficient way, right now 8-( -- p...@opsec.eu+49 171 3101372 8 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: [RFC/HEADSUP] portmaster default -w (preserve shared libraries)
Kurt Jaeger ha scritto: >> I have a few question about what happens if you always use this flag: >> * Do you keep every version of the shlibs you ever built on your system? > > No, only those that still needed. > >> * Are there any method to clean the unused ones? > > sysutils/libchk or pkg_libchk from sysutils/bsdadminscripts. Uh? One of the two: 1) it keeps all versions and you need to clean them up 2) it keeps only needed and so you shouldn't clean up The correct answer is 1) -- Alex Dupre ___ 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: Notes on upgrades after libpcre update
Kevin Oberman ha scritto: > As many of you noticed, the update of devel/pcre bumped hte version of > libpcre.so which is a dependency of LOTS of things. This was a very poor choice, we shouldn't have bumped the version. When there is a bump between two minor releases (8.31 -> 8.32) a red led should blink in port maintainer. The port should have defined: USE_AUTOTOOLS= libtool USE_GNOME= ltverhack to avoid bumbing the version. In fact this is the diff in configure.ac: -m4_define(libpcre_version, [1:1:0]) -m4_define(libpcre16_version, [0:1:0]) +m4_define(libpcre_version, [3:0:2]) +m4_define(libpcre16_version, [2:0:2]) It says that the new shared lib is compatible with the old lib (only new interfaces were added), since: 1 - 0 = 3 - 2 = 1 1 - 0 = 2 - 2 = 0 (from the [current:revision:age] version = current - age rule) -- Alex Dupre ___ 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: [RFC/HEADSUP] portmaster default -w (preserve shared libraries)
Kevin Oberman ha scritto: >> The main reason for keeping the libraries is that it reduces the >> number of breakages during the upgrade process, which can be a very >> serious inconvenience, particularly if the forced update fails to >> complete. In my experience the problem you describe is much less >> significant. > > It does eliminate the instant breakage of lots and lots of stuff, but > it can lead to hard to track down issues later. Exactly. Moreover the pcre version bump was not necessary, we created a problem where it wasn't. I'd say that when there are shared library bumps the commits should be checked and reviewed by multiple eyes. -- Alex Dupre ___ 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: [RFC/HEADSUP] portmaster default -w (preserve shared libraries)
On Wed, Dec 12, 2012 at 09:38:29AM +0100, Alex Dupre wrote: > Kurt Jaeger ha scritto: > >> I have a few question about what happens if you always use this flag: > >> * Do you keep every version of the shlibs you ever built on your system? > > > > No, only those that still needed. > > > >> * Are there any method to clean the unused ones? > > > > sysutils/libchk or pkg_libchk from sysutils/bsdadminscripts. > > Uh? One of the two: > 1) it keeps all versions and you need to clean them up > 2) it keeps only needed and so you shouldn't clean up > > The correct answer is 1) I think that Kurt answered the question "Do you - you personally - keep every version of the shlibs you ever built, as opposed to somehow - not necessarily automagically on port installation/upgrade or periodically - clean up the unused ones" :) You are correct that the original question was probably meant to differentiate between the two options you listed. G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@freebsd.org p.penc...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 This would easier understand fewer had omitted. signature.asc Description: Digital signature
[PATCH] pkgng forcing pkg register
Hi
I'm testing the new pkgng from 10-CURRENT but it seems to not having an
option for forcing registering a package. I have got a lot texlive-*
packages (more than 1000) but I cannot upgrade them, I still got:
Installing [pkg_name]: [pkg_name] conflicts with [other_pkg_name]
(installs files into the same place)
Googling through "(installs files into the same place)" shows that a lot
of people have such a problem with other ports. So I wonder why there is
no an option to force registering a port?
Below is a small patch for pkg, after setting FORCE_PKG_REGISTER env
variable you can force registering a port. May it should be other var
than FORCE_PKG_REGISTER?
--
Tomek
--- pkg-1.0.3.oryginal/libpkg/pkgdb.c 2012-12-12 11:19:29.0 +0100
+++ pkg-1.0.3/libpkg/pkgdb.c2012-12-12 11:33:05.0 +0100
@@ -1795,9 +1795,12 @@
lic_t licenselogic;
int64_t flatsize;
int64_t i;
+ bool force_register;
assert(db != NULL);
+ force_register = (getenv("FORCE_PKG_REGISTER") != 0);
+
if (pkg_is_valid(pkg) != EPKG_OK) {
pkg_emit_error("the package is not valid");
return (EPKG_FATAL);
@@ -1872,7 +1875,7 @@
const char *pkg_sum = pkg_file_cksum(file);
ret = run_prstmt(FILES, pkg_path, pkg_sum, package_id);
- if (ret == SQLITE_DONE)
+ if (force_register || ret == SQLITE_DONE)
continue;
if (ret != SQLITE_CONSTRAINT) {
ERROR_SQLITE(s);
___
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: [PATCH] pkgng forcing pkg register
On 12/12/2012 11:13, Tomasz Sowa wrote: > Googling through "(installs files into the same place)" shows that a lot > of people have such a problem with other ports. So I wonder why there is > no an option to force registering a port? The reason is simple. Packages that are meant to be installed together and that install files into the same place are broken[*]. Two or more packages fighting over the same file is fundamentally a bad thing in any package management system. pkg_tools let port maintainers get away with doing that, which is why it occurs in the ports. We (pkgng developers) don't like the idea of recreating all the bugs in pkg_tools, and suffering the consequences therefrom. While we do appreciate your interest (and patches), your energies would be better spent in fixing the broken ports/packages. Cheers, Matthew [*] It's OK for packages to conflict if they are never going to be installed together. The tricky part of that is 'never.' ___ 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: pkgng: sqlite: database is locked
(Please keep me CC'd as I'm not subscribed to the list) > ===> Registering installation for MuSE-0.9.2_14 > Installing MuSE-0.9.2_14... done > pkg: sqlite: database is locked > > which results in muse not being registered in the pkg database... This worries me. It appears to indicate that the installation of the package (i.e. sticking files into /usr/local) happens first, followed by an attempted exclusive lock of the pkg sqlite DB, which then failed -- thus leaving files laying around in /usr/local. If that is the case (and boy do I hope it isn't) then that logic is 100% backwards. The DB exlock should happen first, and if the DB exlock fails[1] then things should abort. Otherwise you'll end up with files installed on your filesystem which aren't registered in the pkg DB, and that is unacceptable. This also worries me: > ... This persists between reboots, and for fresh pkg runs. What kind of locking mechanism is being used here? flock(2) LOCK_EX would not survive a reboot, but a filesystem-based dotlock would. This really needs investigation and not be swept under the rug. And please don't tell me "you have the source, go look at it" -- I would much rather the authors who are familiar with the code look at it. :-) [1]: I don't advocate that the locking mechanism should block indefinitely, but there should be some kind of retry attempt at a specific interval (i.e. try 5 times, with 1 second delays) before giving up -- and something on-screen should be printed/shown every time an attempt to lock is made. Maybe that already happens, I don't know, I don't use pkg. This also makes me wonder if there's a SIGINT handler for a person hitting Ctrl-C in the middle of that operation and if proper clean-up is done afterward. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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/174308: security/cyrus-sasl2: cyrus-sasl-2.1.25_2 will not compile with PostgreSQL 9.1.3
Synopsis: security/cyrus-sasl2: cyrus-sasl-2.1.25_2 will not compile with PostgreSQL 9.1.3 Responsible-Changed-From-To: ume->ports Responsible-Changed-By: ume Responsible-Changed-When: Wed Dec 12 15:18:18 UTC 2012 Responsible-Changed-Why: It seems to me that this issue is not for individual ports such as cyrus-sasl2, but for VALID_PGSQL_VER in bsd.databases.mk. http://www.freebsd.org/cgi/query-pr.cgi?pr=174308 ___ 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: pkgng: sqlite: database is locked
On Wed, Dec 12, 2012 at 06:53:57AM -0800, Jeremy Chadwick wrote: > (Please keep me CC'd as I'm not subscribed to the list) > > > > ===> Registering installation for MuSE-0.9.2_14 > > Installing MuSE-0.9.2_14... done > > pkg: sqlite: database is locked > > > > which results in muse not being registered in the pkg database... > > This worries me. It appears to indicate that the installation of the > package (i.e. sticking files into /usr/local) happens first, followed by > an attempted exclusive lock of the pkg sqlite DB, which then failed -- > thus leaving files laying around in /usr/local. > > If that is the case (and boy do I hope it isn't) then that logic is 100% > backwards. The DB exlock should happen first, and if the DB exlock > fails[1] then things should abort. Otherwise you'll end up with files > installed on your filesystem which aren't registered in the pkg DB, and > that is unacceptable. > pkg install and pkg add doesn't do that at all. Just pkg2ng and installing from ports uses pkg register which does that, exactly the same way pkg_install does, pkg register knows how to do the clean way, just the ports tree doesn't know yet how to do it, I have patched for that unfortunatly it breaks compatibility with pkg_install (the solution is to use a stage directory inside the ports tree) If you are worried by this, do not ever have a look at how the pkg_install works :) > This also worries me: > > > ... This persists between reboots, and for fresh pkg runs. > > What kind of locking mechanism is being used here? flock(2) LOCK_EX > would not survive a reboot, but a filesystem-based dotlock would. It is the sqlite native lock system which is a flock so it should not survive the reboot > > This really needs investigation and not be swept under the rug. And > please don't tell me "you have the source, go look at it" -- I would > much rather the authors who are familiar with the code look at it. :-) > > [1]: I don't advocate that the locking mechanism should block > indefinitely, but there should be some kind of retry attempt at a > specific interval (i.e. try 5 times, with 1 second delays) before giving > up -- and something on-screen should be printed/shown every time an > attempt to lock is made. Maybe that already happens, I don't know, I > don't use pkg. This is already in, and we have a lot of work for a finer grain locking system. Anyway the reported issue is really strange and need way more details to be able to be investigated. regards, Bapt pgpKsiQI2IxDX.pgp Description: PGP signature
Re: ports/174308: [bsd.database.mk] cyrus-sasl-2.1.25_2 will not compile with PostgreSQL 9.1.3
Old Synopsis: security/cyrus-sasl2: cyrus-sasl-2.1.25_2 will not compile with PostgreSQL 9.1.3 New Synopsis: [bsd.database.mk] cyrus-sasl-2.1.25_2 will not compile with PostgreSQL 9.1.3 Responsible-Changed-From-To: ports->freebsd-ports-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Wed Dec 12 15:35:16 UTC 2012 Responsible-Changed-Why: reassign. http://www.freebsd.org/cgi/query-pr.cgi?pr=174308 ___ 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: Let's talk about subversion/svn
On Mon, Nov 19, 2012 at 12:51:01PM +0400, Lev Serebryakov wrote: > Hello, Jeremy. > You wrote 19 2012 ??., 11:16:07: > > JC> However, GDBM and Oracle/Sleepycat DB aren't (by default) enabled > JC> in 1.7.7 which is what's in ports currently: > They weren't enabled for 1.7.6 too, so it is strange, that > pointyhat-builded package require it. I need to investigate this. Lev, Politely: any update on this? I see the packages on the master are still the same date (October 2012), but I can confirm that building from ports/source doesn't pull in GDBM nor Oracle/SleepyCat DB. I imagine the security incident on the cluster, combined with 9.1-RELEASE rollout, has stalled some of this, but I just wanted to remind you of it in case you've forgotten. Also, this might interest you since subversion pulls in apr1 (note first paragraph): http://lists.freebsd.org/pipermail/freebsd-apache/2012-December/003008.html http://lists.freebsd.org/pipermail/freebsd-apache/2012-December/003010.html Seems there are many of us trying to get the dependency count down these days. :-) -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: need help with pkg - failed portupgrade
On 12/11/2012 10:24 PM, AN wrote: > FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #5 r244122: Tue Dec 11 > 15:24:02 EST 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 > > While running portupgrade due to (The pcre library has been updated to > version 8.32. Please rebuild all ports that depend on it.) I had the > following failure: > > The command I ran was :portupgrade -vfr devel/pcre > > and it failed with: > ===> Cleaning for gnome-screensaver-2.30.2_3 > ---> Removing temporary files and directories > ---> Removing old package' > ---> Installation of x11/gnome-screensaver ended at: Tue, 11 Dec 2012 > 23:01:06 -0500 (consumed 00:00:15) > ---> Cleaning out obsolete shared libraries > [Updating the pkgdb in /var/db/pkg ... USING PKGNG > - 798 packages found (-0 +1) . done] > ---> Reinstallation of x11/gnome-screensaver ended at: Tue, 11 Dec 2012 > 23:01:08 -0500 (consumed 00:01:40) > ---> ** Upgrade tasks 278: 200 done, 0 ignored, 7 skipped and 2 failed > ** No origin recorded: libreoffice-3.5.7 > ** Specify one with -o option, or run 'pkgdb -F' to interactively fix it. > ---> Session ended at: Tue, 11 Dec 2012 23:01:08 -0500 (consumed 04:51:07) > /usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:964:in > `initialize': ArgumentError (ArgumentError) > from /usr/local/sbin/portupgrade:1060:in `new' > from /usr/local/sbin/portupgrade:1060:in `do_upgrade' > from /usr/local/sbin/portupgrade:855:in `main' > from /usr/local/sbin/portupgrade:850:in `each' > from /usr/local/sbin/portupgrade:850:in `main' > from /usr/local/lib/ruby/1.8/optparse.rb:791:in `initialize' > from /usr/local/sbin/portupgrade:237:in `new' > from /usr/local/sbin/portupgrade:237:in `main' > from /usr/local/sbin/portupgrade:2371 > > > I deleted Libreoffice with: > pkg -d delete libreoffice-3.5.7 > > # pkgdb -vF > USING PKGNG > pkgdb -F not supported with PKGNG yet. Use 'pkg check' directly. > [root@FBSD10 ~]# pkg check > usage: pkg check [-Bdsr] [-vy] [-a | -gxX ] Sorry for the bad direction here. 'pkg check' only works on binary packages. I need to update 'pkg check' to support sending a list of problems back to stdout, so portupgrade can recompile/install the missing deps. > > For more information see 'pkg help check'. > > Not sure how to proceed now, any help is appreciated. > > Once I get this fixed, how can I restart portupgrade from where it ended > and not recompile the ports that were already updated? I'm not aware of a good way to do this. If you know which have already been rebuilt you can specify them with -x portupgrade -vfr devel/pcre -x 'pkg' -x 'pkg2' This might work to recompile anything touched not on yesterday, but I'm not confident: portupgrade -vfr devel/pcre -x '<2012-12-11' Try with -n to see what is listed. If you enable ccache, this becomes less of a problem. In your /etc/make.conf: WITH_CCACHE_BUILD=yes, and install devel/ccache -- Regards, Bryan Drewery bdrewery@freenode/EFNet signature.asc Description: OpenPGP digital signature
Re: A little OT: what about redports.org?
On 12/10/2012 4:19 PM, Fernando Apesteguía wrote: > Hi all, > > Redports has been down for a while. Is this related to the security > incident we have some weeks ago? If so, do we have an ETA for redports > to be brought up again? > > Thanks! Official status updates is being posted here: https://twitter.com/redports Bryan ___ 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"
net/liveMedia
1212 Wednesday, 12 December 2012 (EST) [15686] Build error encountered during build of multimedia/vlc: In file included from live555.cpp:61:0: /usr/local/live/liveMedia/include/liveMedia.hh:114:38: fatal error: ProxyServerMediaSession.hh: No such file or directory compilation terminated. Suggested patch: In the file: /usr/local/live/liveMedia/include/liveMedia.hh Suggest replacing the following line: #include "ProxyServerMediaSession.hh" With the following two lines: #include MediaSession.hh #include ServerMediaSession.hh --Austin Kim ___ 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: New port question JBoss 7.1.3
any progress with jboss 7.1.3 update? i checked ports tree and it is still not here. No need to create new port, just replace jboss7 port. ___ 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: net/liveMedia
On, Wed Dec 12, 2012, Австин Ким wrote: > 1212 Wednesday, 12 December 2012 (EST) [15686] > > Build error encountered during build of multimedia/vlc: > > In file included from live555.cpp:61:0: > /usr/local/live/liveMedia/include/liveMedia.hh:114:38: fatal > error: ProxyServerMediaSession.hh: No such file or > directory > compilation terminated. > > Suggested patch: > > In the file: /usr/local/live/liveMedia/include/liveMedia.hh > Suggest replacing the following line: > #include "ProxyServerMediaSession.hh" > With the following two lines: > #include MediaSession.hh > #include ServerMediaSession.hh net/liveMedia has been fixed already and all dependent ports should build fine again. Please update your ports tree. Thanks for reporting! Cheers Marcus pgpvtZQz6MknX.pgp Description: PGP signature
Re: New port question JBoss 7.1.3
2012/12/12 Radim Kolar > any progress with jboss 7.1.3 update? i checked ports tree and it is still > not here. No need to create new port, just replace jboss7 port. > No, let 7.1.1 be there. This release is last one whithc provided in binary form. jboss71 will be 7.1.3 (and if there will be updates in 7.1.x they will be in this port). And a bit later, I'll introduce new port jboss72. Until port isn't in ports tree you can get it here - https://www.box.com/s/1ffcipb3jx7ig9qqq5br P.S. Any committer who commit this port in ports tree of course will save the time :) -- Regards, Alexander Yerenkow ___ 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: Let's talk about subversion/svn
1) +1 for minimal svn stub, still too slow for ports so I must stick to portsnap... 2) Beware of serf! Last time I've swapped to it from neon, it was broken, but it manifested subtly, only when checking out larger projects (like FreeBSD). -- View this message in context: http://freebsd.1045724.n5.nabble.com/Let-s-talk-about-subversion-svn-tp5762138p5768918.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ 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: Let's talk about subversion/svn
Or was it neon?... Case in point was the default WebDAV was sane, the other one, not. -- View this message in context: http://freebsd.1045724.n5.nabble.com/Let-s-talk-about-subversion-svn-tp5762138p5768920.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ 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: Let's talk about subversion/svn
On 2012-12-12 23:01, Jakub Lach wrote: Or was it neon?... Case in point was the default WebDAV was sane, the other one, not. serf bad, neon good. ;-) ___ 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: Let's talk about subversion/svn
On 2012-12-12 23:01, Jakub Lach wrote: > Or was it neon?... Case in point was the default WebDAV was sane, > the other one, not. > It's a serf issue and there are already open tickets /reports upstream for serf and subversion. One special issue http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=2901999 Unfortunately serf will become the only supported HTTP client in subversion-1.8 (no neon support) which brings other issues on the server side. from http://subversion.apache.org/docs/release-notes/1.8.html - HTTP client support based on neon has been removed - FSFS format bump - http://mail-archives.apache.org/mod_mbox/subversion-dev/201211.mbox/%3C021c01cdc103$5c12a1c0$1437e540$@qqmail.nl%3E - no delta support, file will be transferred always complete - ... But also some goodies - Packing revision properties subversion-1.7.8 is in the pipe to fix some 1.7.7 issues (maybe it will released during the next days, so please give Lev the time to adopt 1.7.8) -- olli ___ 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"
fix kdelibs3 build after misplaced sasl-fix
Hi!
The build process hanged up on make patch stage, due to misplaced sasl fix.
---8<---
root@pandora-d kdelibs3# make patch
===> Patching for kdelibs-nocups-3.5.10_11
===> Applying FreeBSD patches for kdelibs-nocups-3.5.10_11
File to patch:
---8<---
The right place are kdebase3/files, see the attached patch. NOT YET
BUILD tested, only make patch tested. When it's compiled, then I send
a confirmation mail.
Have a nice day!
diff --git a/x11/kdelibs3/files/patch-kioslave_smtp_smtp.cc b/x11/kdelibs3/files/patch-kioslave_smtp_smtp.cc
deleted file mode 100644
index 59e00fb..000
--- a/x11/kdelibs3/files/patch-kioslave_smtp_smtp.cc
+++ /dev/null
@@ -1,12 +0,0 @@
-Index: kioslave/smtp/smtp.cc
-diff -u kioslave/smtp/smtp.cc.orig kioslave/smtp/smtp.cc
kioslave/smtp/smtp.cc.orig 2007-10-08 18:51:22.0 +0900
-+++ kioslave/smtp/smtp.cc 2012-12-12 15:29:29.604353297 +0900
-@@ -31,6 +31,7 @@
- #include
-
- #ifdef HAVE_LIBSASL2
-+#include
- extern "C" {
- #include
- }
___
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: fix kdelibs3 build after misplaced sasl-fix
On 12/13/12, Oliver Pinter wrote: > Hi! > > The build process hanged up on make patch stage, due to misplaced sasl fix. > > ---8<--- > root@pandora-d kdelibs3# make patch > ===> Patching for kdelibs-nocups-3.5.10_11 > ===> Applying FreeBSD patches for kdelibs-nocups-3.5.10_11 > File to patch: > ---8<--- > > The right place are kdebase3/files, see the attached patch. NOT YET > BUILD tested, only make patch tested. When it's compiled, then I send > a confirmation mail. Done. Compiled. > > Have a nice day! > ___ 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: fix kdelibs3 build after misplaced sasl-fix
Hi,
> On Thu, 13 Dec 2012 06:48:09 +0100
> Oliver Pinter said:
oliver.pntr> The build process hanged up on make patch stage, due to misplaced
sasl fix.
oliver.pntr> ---8<---
oliver.pntr> root@pandora-d kdelibs3# make patch
oliver.pntr> ===> Patching for kdelibs-nocups-3.5.10_11
oliver.pntr> ===> Applying FreeBSD patches for kdelibs-nocups-3.5.10_11
oliver.pntr> File to patch:
oliver.pntr> ---8<---
oliver.pntr> The right place are kdebase3/files, see the attached patch. NOT YET
oliver.pntr> BUILD tested, only make patch tested. When it's compiled, then I
send
oliver.pntr> a confirmation mail.
Oops, I committed it to kdelibs3 wrongly. I've just committed to move
it to kdebase3.
Thank you.
Sincerely,
--
Hajimu UMEMOTO
u...@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.mahoroba.org/~ume/
___
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"
