sysutils/apachetop needs a commiter
Hi, I'm the apachetop maintainter, there's a pending update (and compile fix) that I approved. Can someone commit it please? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227865 Thank you in advance. -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Removal of www/apache22
W dniu 2018-04-11 o 20:29, Bernard Spil pisze: > You are all maintainer of a port that depends on www/apache22. The > Apache 2.2 port has been marked EXPIRED for almost a year. I was about > to delete it but didn't want to go ahead without informing you. My > analysis of the dependent ports can be found in the FreeBSD wiki > https://wiki.freebsd.org/Apache#Apache_2.2 [...] > www/mod_macro22 luk...@wasikowski.net This is apache 2.2 only version. Feature provided by this port is included in apache 2.4 , so feel free to bury www/mod_macro22. -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PRs commit request
W dniu 2017-09-13 o 16:46, Kurt Jaeger pisze: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220902 > > Done. If you describe the topic of the PR, it makes it easier > to decide if I can work on it. Thank you, I'll describe it next time. -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
PRs commit request
Hi, I'm looking for a good soul with a commit bit to push those PRs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220112 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220902 Thank you in advance. -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Looking for good sould with a commit bit
I'm looking for someone with a commit bit to look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208147 - new port [sysutils/modman] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219825 - maintainer approves [security/rkhunter] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219726 - maintainer update [www/mod_mpm_itk] Thank you! -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Looking for good sould with a commit bit
I'm looking for someone with a commit bit to look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208148 It has maintainer approval. -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Looking for commiter: dns/dnstracer: Build fails on 10.2-RELEASE-p2 amd64
W dniu 2016-02-17 o 05:41, Kurt Jaeger pisze: >> I'm looking for a commiter for this PR (working patch is included): >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202824 > > Done. Thank you. -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Looking for commiter: dns/dnstracer: Build fails on 10.2-RELEASE-p2 amd64
Hi, I'm looking for a commiter for this PR (working patch is included): https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202824 -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Looking for a commiter
W dniu 2015-09-22 o 22:20, Kurt Jaeger pisze: >> Could someone with commit bit to ports tree look at those: >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203067 - security fix >> (maintainer update) > > Done. > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195147 >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202930 >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203141 > > I can't promise anything... Thank you :) -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Looking for a commiter
Hi, Could someone with commit bit to ports tree look at those: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195147 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202930 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203067 - security fix (maintainer update) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203141 -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Rkhunter
W dniu 2014-10-06 o 14:35, Philippe Audéoud pisze: > On Mon, 06 Oct 2014, Frank Seltzer wrote: > >> Is rkhunter still actively maintained? I run it nightly and I can't >> remember the last time there was an update to any of the database files. >> >> Thanks, >> Frank > > Hello, > > $ svn log security/rkhunter > r364732 | cs | 2014-08-12 20:31:26 +0200 (Tue, 12 Aug 2014) | 8 lines > > - unbreak > - added some FreeBSD defaults regarding SSH > - made port more PREFIX aware > - changed maintainer > > PR: 191842 > Submitted by: Gerard J. Cerchio and Lukasz Wasikowski (maintainer) > > > It's the last update. You can mail maintainer to ask him if an update is > planned. I'm port maintainter, not rkhunter itself, so I can't say if there are any updates planned. Look at http://rkhunter.sourceforge.net/ for rkhunter developers. -- 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...
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: Who was the mental genius
W dniu 2014-06-05 23:43, Paul Schmehl pisze:
> --On June 5, 2014 at 11:18:31 PM +0200 "A.J. 'Fonz' van Werven"
> wrote:
>
>> Paul Schmehl wrote:
>>
>>> That decided it was a good idea to completely break ports to force
>>> people to upgrade? You couldn't come up with a warning system instead
>>> of outright breaking ports? The idiots are apparently running the
>>> asylum. {{sigh}}
>>
>> It might help to know exactly what you're talking about... What is it
>> that
>> broke?
>>
>
> The change to make that causes this when you run pkg commands or try to
> build ports:
>
> Unknown modifier 't'
>
> It was done deliberately to break ports so that people would be forced
> to upgrade to a supported version.
>
>
This change was needed 8 months ago, but was hold until the EOL of 8.3
arrived [1].
Freeze your ports on revision 352985 until you upgrade base system to
supported version.
[1] https://www.mail-archive.com/freebsd-ports@freebsd.org/msg57884.html
--
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: PORT META: Installed files conflict between ports
W dniu 2014-05-21 03:53, Robert Backhaus pisze: > The fact that those two ports install conflicting binaries isn't a problem. > The problem is that you were allowed to install the second port. > > With mplayer, there is a correct CONFLICTS line in mplayer2, but does not > appear to be one in mplayer. But both samba ports seem to have the correct > CONFLICTS line, but that may have been fixed after you installed the port. Try installing security/openssl and sysutils/moreutils together - that is one fine example of naming collision. -- 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: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
W dniu 2014-05-10 17:47, Bryan Drewery pisze: >> You are receiving this mail as it affects FreeBSD ports that you maintain. >> > > You can see the full list here: > > http://people.freebsd.org/~bapt/notstaged.txt For mail/postfixadmin I've send PR [1] including staging and security fix some time ago. [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/189248 -- 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: What happend to www/mod_macro24
W dniu 2014-02-27 17:55, Serpent7776 pisze: >> I wonder what happend to >> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/177413 - it was in >> ports tree for a while and now it's gone. > according to /usr/ports/MOVED: > > www/mod_macro24||2013-08-03|Has expired: part of Apache 2.4.6 and newer > > /usr/ports/MOVED is the first place to look when port disappear. Thank you. -- 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"
What happend to www/mod_macro24
Hi, I wonder what happend to http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/177413 - it was in ports tree for a while and now it's gone. -- 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: [FreeBSD-Ports-Announce] Time to bid farewell to the old pkg_ tools
W dniu 2014-02-06 14:04, John Marino pisze: > On 2/6/2014 13:58, Rick Miller wrote: >> On Thu, Feb 6, 2014 at 7:23 AM, Daniel Nebdal wrote: >>> I suspect he meant "a certain version, and *not* newer" - sometimes >>> you might want to hold back a package. >> Correct. My wish is the functionality be extended further to mean "a >> certain version *or* newer", encompassing both features. Thus, allowing >> him to say "port-1.1", while I say "port-1.4 or newer" or even "port-1.0 or >> newer". > As an observer, all I can say is "Don't get your hopes up" on this one. > Hundreds of ports are bumped with majority dependency changes for a > reason. The tree is treated as an integrated entity, not 25,000 > interchangeable parts. > > It would take major technology shift, something closer to what PC-BSD's > pbi things do/did. Ports itself isn't geared for this. Maybe some kind > of package archive could be used though, if "pkg" solvers could be made > to handle such requests. Sounds like an extremely difficult request to > me though. Gentoo's portage has this capability and it works quite well. I'd love to see it in FreeBSD. -- 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: something messed up with latest pkg update?
W dniu 2013-11-27 10:55, Ruslan Makhmatkhanov pisze: > Got some warnings: > pkg-static: PACKAGESITE in pkg.conf is deprecated. Please create a > repository configuration file > pkg-static: Warning: expecting a boolean for the 'enabled' key of the > 'FreeBSD' repo, the value has been correctly converted, please consider > fixing > pkg-static: unable to open vulnxml file, try running 'pkg audit -F' first > > Fixed 1st and 3rd. What it is supposed to do with 2nd one? Try enabled: yes (without quotes) in pkg.conf. -- 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: pkg 1.2 lots of messages about enabled key.
W dniu 2013-11-26 17:15, Johan Hendriks pisze: > I just updated pkg to pkg 1.2 > > But when i usr pkg it gives me a lot of messages like below: > > pkg: Warning: expecting a boolean for the 'enabled' key of the 'FreeBSD' > repo, the value has been correctly converted, please consider fixing [...] > enabled: "YES" > } > > something i missed? Get rid of " signs. It should be: enabled: yes -- 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: State of the Porters' Handbook
W dniu 2013-10-28 09:41, Dominic Fandrey pisze: > Neither staging nor license management are described in the Porters' > Handbook. > > Why again should we bother to support it? > > What happened to "the feature that is not documented doesn't exist"? Lack of good documentation is real problem for me to convert ports to staging. Porter's Handbook is seriously lagging behind recent changes - staging, license management, shabang fixes, etc. -- 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"
portsnap corruption
Hi, I've tried to update ports on few servers, got this: # portsnap fetch extract Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found. Fetching public key from ec2-eu-west-1.portsnap.freebsd.org... done. Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done. Fetching snapshot metadata... done. Fetching snapshot generated at Thu Oct 24 02:04:53 CEST 2013: c54e7bf053e2425753affcd01e2c4ebf11f411ecbcff15100% of 69 MB 2138 kBps 00m33s Extracting snapshot... done. Verifying snapshot integrity... done. Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done. Fetching snapshot metadata... done. Updating from Thu Oct 24 02:04:53 CEST 2013 to Thu Oct 24 09:34:07 CEST 2013. Fetching 4 metadata patches... done. Applying metadata patches... done. Fetching 4 metadata files... gunzip: (stdin): unexpected end of file metadata is corrupt. -- 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: portsnap fetch failed on FreeBSD 8.2
W dniu 2013-05-28 17:51, Xu Zhe pisze: > I got a task to port Java to a private-built FreeBSD system which is > branched from FreeBSD 8.2. As a start of this, I tried to learn port > stuffs, and did 'portsnap fetch' but failed. After that, I tried to > change portsnap server, and I even tried a generic FreeBSD 8.2 version, > which failed too with merely the same error. Here is what I got in most > of the cases (not totally the same for each time, but I suppose they are > familiar): Please take a look at this: http://lists.freebsd.org/pipermail/freebsd-ops-announce/2013-May/06.html Problem you've described should be fixed by now. If it's not please wait for a few more hours. -- 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: Where has all the groupware gone.....
W dniu 2013-05-06 16:30, Paul Pathiakis pisze: > Also, where is the sogo.conf file supposed to be located? That is, what > directory? /var/lib doesn't exist on a BSD machine. All third party software should have configuration in $PREFIX/etc/, which in most cases is /usr/local/etc/ - please don't put any configuration files in places like /var/lib or /usr/local/GNUstep/Local/Library/SOGo mentioned before. -- 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: [BRAINSTORM] shebang fixing framework
W dniu 2013-05-02 20:29, Oliver Heesakkers pisze: > Op do 02 mei 2013 16:22:41 schreef Łukasz Wąsikowski: >> /usr/bin/env is not good in all the situation. Look at >> www.freebsd.org/cgi/query-pr.cgi?pr=177481 - /usr/bin/env is not working >> when using 'service' to start daemons. We should change PATH used by >> 'service' to include /usr/local/bin and /usr/local/sbin or stop using >> /usr/bin/env to start rc.d scripts. > > > A question that arises from reading that pr is why service doesn't include > /usr/local/bin and /usr/local/sbin in its PATH, if it does your problem would > probably dissapear. That would probably be the best fix. > I have no /usr/bin/perl symlink, in the pure-ftpd port directory I do: > > make extract > head -n1 work/pure-ftpd-1.0.36/configuration-file/pure-config.pl.in > #! @PERL@ > > > After installation the shebang reads: > #! /usr/local/bin/perl > > and I can use service to start or stop the daemon without any hacking. That is interesting. service(8) clearly states that PATH is set to /sbin:/bin:/usr/sbin:/usr/bin, so perl interpreter in /usr/local/bin should not work (like it doesn't in my case). -- 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: [BRAINSTORM] shebang fixing framework
W dniu 2013-05-01 21:18, Oliver Heesakkers pisze: > Op di 30 apr 2013 12:38:21 schreef Baptiste Daroussin: >> For a while now: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/51152 we >> are looking for a framework/helpers to help patching scripts shebang so >> that they fit where the interpreters is on FreeBSD. >> > (...) > > In there you wrote a patch using /usr/bin/env. Why not stick with that? I'm > quite fond of this technique as it's clean and portable. > > Portability might not be that important when working on a fix for ports > alone, > but still makes sense to me. /usr/bin/env is not good in all the situation. Look at www.freebsd.org/cgi/query-pr.cgi?pr=177481 - /usr/bin/env is not working when using 'service' to start daemons. We should change PATH used by 'service' to include /usr/local/bin and /usr/local/sbin or stop using /usr/bin/env to start rc.d scripts. -- 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: Dropbox on FreeBSD
W dniu 2013-03-05 20:20, Wojciech Puchar pisze: > got into webpage, and it looks like detailless advert just like plenty > of others. > > Found that it "simplify sharing", get quite bored after trying to find > out WHAT and HOW it actually provides. I'm using Dropbox with boxcryptor (files gets encrypted on device and then sent to the Dropbox cloud) - it's nice synchronization tool between my home pc, work pc, netbook and android smartphone. Also auto upload of photos from the phone and easy sharing of files with non-tech people is a neat feature. I'm not saying it's the best of them all, but it does it job good and it's quite popular. I'd love to see FreeBSD client of it. -- 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: FreeBSD Port: pecl-APC-3.1.13
W dniu 2013-02-01 09:32, Lev Serebryakov pisze: > FD> I use this extension on several servers (4 with php5.4 and 2 with php5.3 > FD> with the same configuration) and since you've update apc to 3.1.14 it stop > FD> working with some apps in php 5.3. > Same problem here: apache22 (2.2.23_4), php53 (5.3.21), and some > sites stop working with pecl-APC-3.1.14 (server drops connection right > after request, no messages in any log). I got it with Kohana script. With 3.1.13 it worked fine, with 3.1.14 connection close and empty logs. -- 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: [PKGNG] how about remember repository used for installation?
W dniu 2013-01-31 17:10, Baptiste Daroussin pisze: > That will work as you expect as soon as the new > solver is in, no there is currently no schedule for that Good to hear that this feature is planned, thank you. -- 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: [PKGNG] how about remember repository used for installation?
W dniu 2013-01-30 10:16, Alex Keda pisze: > I have some servers, with standard soft settings, and can use general > repository > but, one/two applications have another settings (for example, samba, > apache...) > > may be add to installed pkg some options, about 'install repository', > and use it for update? +1, that feature would be awesome. Now I have poudriere jails building the same 40 packages just to do one different. It's a waste of resources. -- 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: Portscout Notification Emails
W dniu 2012-11-27 19:38, Olli Hauer pisze: > For example the following 42 ports are removed since 2012-01-01 but are listed > for apache@. > > apache-contrib apache13 apache13+ipv6 apache13-modperl apache13-ssl auth_ldap > mod_access_identd mod_access_referer mod_accounting mod_auth_cookie_mysql > mod_auth_external mod_auth_imap mod_auth_kerb mod_auth_mysql mod_auth_pam > mod_auth_pgsql mod_auth_useragent mod_backhand mod_bandwidth mod_bf > mod_blowchunks mod_bunzip2 mod_cgi_debug mod_color mod_curb mod_dav > mod_extract_forwarded_ap13 mod_filter mod_index_rss mod_layout mod_log_spread > mod_mp3 mod_mylo mod_perl mod_proxy_add_forward mod_put mod_python mod_sed > mod_sequester mod_shapvh mod_sqlinclude mod_ticket mod_trigger > > mod_cvs -> removed but sends update requests for mod_cvs2 > mod_macro -> removed but sends updates for mod_macro22 I'm maintaining mod_macro22 and I'm fine with e-mail updates. -- 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: security/sudo: make fails after update to 1.8.6p3
W dniu 2012-09-26 13:57, Herbert J. Skuhra pisze: >> After update of security/sudo to 1.8.6p3, make fails on 9.0-RELEASE as >> following: >> >> [Several lines removed] >> >> Are there anyone alse experienced this? > > Yes, the port obviously builds only on amd64. True, I've installed it successfully on amd64 and got the same error on i386 box. -- 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: again, ports that stop daemons
W dniu 2011-12-09 22:25, Doug Barton pisze: > I previously described what I thought was a pretty good way to handle > this question that addressed the needs expressed by all of the posters > on the previous thread, but my suggestion didn't get any responses. > Since this has come up again, it would be helpful (to me at least) if > people would think about my idea, and if nothing else tell me why I'm > wrong. :) +1 to the idea. -- 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: PHP segmentation faults
W dniu 2011-09-29 19:29, Moggie pisze: > mhash Are you using apache-worker? Try to disable that module. -- 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: Re-starting daemons across upgrades?
W dniu 2011-09-28 23:12, Matthias Andree pisze: > So basically, we need a lever the operator can flip, and that typical > ports running daemons, respect - that can state whether ports > auto-restart deamons previously running (which would entail complaining > the if needs manual intervention, like chasing configuration language > changes, or other), or whether not to and just collect their names and > list them so the operator can do it at a convenient time -- assuming the > daemons are up to that task (continue running). That solution would satisfy most of the use cases. -- 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: Re-starting daemons across upgrades?
W dniu 2011-09-28 20:53, Matthias Andree pisze: >> We shouldn't go that way at all. Restarting service right after it's >> update is not a good thing. In many cases service will not start, >> because of needed configuration changes od other ports not recompiled or >> updated. The safe way is to not stop service at all. Let the system >> operator restart service manually when he finish all the needed update >> tasks. > > Well, the maintainer should know if the service can be restarted or > needs manual intervention. For patch level upgrades - pathological cases > like OpenLDAP or Cyrus-SASL interactions aside - you normally can > restart the service without further ado. That's true. Still, I often like to update software during the work hours and restart it in the middle of the night. It's not as annoying to customers as restarting critical service during peak hours. Restart time should be left for operator to decide. -- 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: Re-starting daemons across upgrades?
W dniu 2011-09-17 11:08, Matthias Andree pisze: >>> - discuss whether we want/need to support this (a) in the framework that >>> we currently use, (b) only in pkgng, (c) in portmaster and portupgrade >>> where necessary. >> Or we could have a facility to check whether services are running. For >> example, I have some cron scripts, which are similar for all of the >> services that I'm watching. They run periodically and restart services >> if they are down. It does not matter if they are down because of an >> upgrade or a failure, so this solution is more general. Here's an >> example that I have for MySQL: > Before we go that way, we should consider using runit by Gerrit Pape > (smarden.org), Upstart, or port systemd. We shouldn't go that way at all. Restarting service right after it's update is not a good thing. In many cases service will not start, because of needed configuration changes od other ports not recompiled or updated. The safe way is to not stop service at all. Let the system operator restart service manually when he finish all the needed update tasks. -- 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: Re-starting daemons across upgrades? (was: Thank you (for making the ports less boring).)
W dniu 2011-09-16 20:25, Chris Rees pisze: > However, having services not restarted after an upgrade can leave you > with a) a vulnerable older service and b) a nasty shock when you > decide to reboot six months later and it breaks :) I know that I should restart service after update and I will do it, I promise :) But I like to do it when I'm prepared for it, not when monitoring system starts screaming about a down service ;) -- 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: Re-starting daemons across upgrades? (was: Thank you (for making the ports less boring).)
W dniu 2011-09-16 18:17, Eric pisze: > Just for ref regarding (c) on the portupgrade wiki page[1] it mentions using > AFTERINSTALL in pkgtools.conf for doing automatic stop/start/restart. I'm using it for a long time on my personal box and it's not that great. After some updates there is need to prepare the daemon - adjust configuration for example. Automatic restart will do much harm in that case. Another example: update when there's apache and php in new versions, system has also eaccelerator and some pecl's installed. If php was updated before apache, then apache restart via AFTERINSTALL will leave you with not working www server (because eaccelerator and pecl's were not recompiled). Updating ports should never turn off or restart service - thats my $0.02. -- 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: overlays
W dniu 2011-09-16 08:24, Klaus T. Aehlig pisze: > Now I'm really curios what magic device gentoo has. Once thing I > most appreciate about FreeBSD is how flexible it is in precisely > this manner. [...] > Could you please elaborate, which additional features gentoo's overlay > system brings on top of that? Simplicity. I'm not familiar with FreeBSD's way of doing overlays, quick googling and quick testing may be not enough to say anything in that matter, so I'll just describe how I do it in Gentoo. I've got ca. 70 Gentoo servers and I want my own portage overlay. So I've set up svn server with my ports. Each of 70 servers has a script in /etc/portage/postsync.d which retrives my ports from svn server during the synchronization of portage tree. Each server have a line in /etc/make.conf: PORTDIR_OVERLAY=/some/local/directory Let's say I've wrote a new ebuild for a new category, for example: my-category/my-port/my-port-1.0.ebuild. Now I have to do prepare it for "shipping", so: cd my-category/my-port && ebuild my-port-1.0.ebuild digest && svn ci That's all, after next portage update (via emerge --sync) I'll end with up-to-date official portage tree and up-to-date my overlay. Ports from my overlay will work with emerge out of the box (checking for new USE flags, checking if port needs updating, etc.) Summarize: Enable overlay: - one simple script in postsync.d - one line in make.conf Prepare port for tree: - one command to make ebuild - one command to commit it to svn Sync and install/update: - one command to update portage tree on each server - one command to install/update port(s) How would it look like on FreeBSD? -- 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: Thank you (for making the ports less boring).
W dniu 2011-09-15 20:37, Chad Perrin pisze: > On Thu, Sep 15, 2011 at 08:46:10PM +0200, Łukasz Wąsikowski wrote: >> W dniu 2011-09-15 20:08, Chad Perrin pisze: >>> >>> If there was something broken with a FreeBSD port (a relative >>> rarity), it would fail to install, leaving me with the older >>> version. If there was something wrong with a Gentoo port, I'd end >>> up with a broken install. >> >> That's true. But I've got probably less then 5 situations when Gentoo >> port broke that way. Overall experience of every day portage use is >> just plain better. I hope for some changes in FreeBSD's ports system, >> we know where to look for some good ideas. > > It seems we have different priorities. I *hate* having a software update > break my software. I would rather go through an extra step or two when > updating my software if it means I won't get an update that makes the > software unusable. I'm not saying that portage is perfect, I'm just saying FreeBSD could grab some good things from it. Recent gdbm update broke some systems, because IIRC maintainer forgot to check all dependencies or mention it in UPDATING. Shared library bumps in Gentoo always comes with "after install" info about necessary revdep-rebuild run, so those kinds of trouble are avoided. BTW: You hate having a software update break your software. I hate when software updates turn off services on my servers. That's another thing portage do better - update won't turn off any service. You are supposed to restart services manually after doing etc-update. Speaking of which - another good idea worth adopting. -- 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: Thank you (for making the ports less boring).
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 W dniu 2011-09-15 20:08, Chad Perrin pisze: > On Thu, Sep 15, 2011 at 07:00:47PM +0200, Łukasz Wąsikowski wrote: >> W dniu 2011-09-14 18:15, Christopher J. Ruwe pisze: >>> >>> Came as Gentoo user, abandoned Gentoo because of to many quirks >>> with updating packages (ebuilds). From my perspective, the >>> situation is better here (FreeBSD). >> >> Really? I've been using FreeBSD for over 10 years now, Gentoo for >> half of that time and I can surely say that Gentoo's portage is >> much better than FreeBSD's ports. > > There are some nice things that portage does, and my experience > with Gentoo is a few years out of date by now, but I remember one > difference that made software management on FreeBSD much better > than on Gentoo: > > If there was something broken with a FreeBSD port (a relative > rarity), it would fail to install, leaving me with the older > version. If there was something wrong with a Gentoo port, I'd end > up with a broken install. That's true. But I've got probably less then 5 situations when Gentoo port broke that way. Overall experience of every day portage use is just plain better. I hope for some changes in FreeBSD's ports system, we know where to look for some good ideas. - -- best regards Lukasz Wasikowski -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5yR/IACgkQXlaUxx+udUXOKACfTusKK6NZ3NRvH2TPY6iVGGI7 cjkAnRYKjy5mqLROarl8AGN32467NlGi =UhL1 -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: Thank you (for making the ports less boring).
W dniu 2011-09-14 18:15, Christopher J. Ruwe pisze: > Matthias Andree wrote: > > [...] > >> I think you mentioned Arch Linux, further suggestions would be >> Gentoo Linux (you might like emerge), and further options are >> Debian GNU/kFreeBSD and using a FreeBSD base system with pkgsrc >> (rather than ports) on top. > > Came as Gentoo user, abandoned Gentoo because of to many quirks > with updating packages (ebuilds). From my perspective, the > situation is better here (FreeBSD). Really? I've been using FreeBSD for over 10 years now, Gentoo for half of that time and I can surely say that Gentoo's portage is much better than FreeBSD's ports. 1. If there's a need for sysadmin to perform some tasks after updating a port: FreeBSD - look up UPDATING and search for any of the ports you're about to update. Gentoo - update whatever you need, at the end of the process you'll get all the information you need right on the screen. 2. Libraries bumps: FreeBSD: pkg_libchk likes to show false positives. Gentoo: revdep-rebuild works like a charm. 3. Someone deleted port I like to use / I want my personal ports tree: FreeBSD: I wish :/ Gentoo: overlays works well. 4. Port's options: FreeBSD: per port options in /var/db/ports or global in /etc/make.conf. It's hard to tell during update what options are set for the port. Also if I won't look in the Makefile of a specific port I won't be able to tell if WITH_SOMETHING will work with it. Gentoo: USE flags (global and per port) are nice to use and you see all the options set in one place during the update. 5. Port's versioning: FreeBSD: most ports available in one version, hard to downgrade if new version is not what I wanted for whatever reason. Gentoo: most ports available in at least few versions, update / downgrade is not a problem. -- 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"
