Re: rxvt question

William A. Mahaffey III wrote: > ( rxvt -sl 5000 -fn > -*-lucidatypewriter-bold-r-normal-sans-17-*-100-100-*-100-*-* & ) > [wam@kabini1, ~, 10:18:43am] 303 % rxvt: No match. Try escaping the asterisks in the font string. HTH, Fonz -- I'm not completely useless, I can be used as a bad

Re: astro/boinc-setiathome-v7 - is a v8 in the works?

Torfinn Ingolfsen wrote: > Is a v8 port in the works? That port doesn't have a maintainer, so someone will have to volunteer to upgrade it. If you like, I can try to find some time to have a shot at it. Fonz -- I'm not completely useless, I can be used as a bad example. signature.asc

Re: License info Q

Roger Marquis wrote: > Perhaps easier than spending developer resources on administrative metadata > perhaps an automated monthly email to port maintainers who have missing or > inaccurate LICENSE= data, requesting this variable be added to makefiles and > manifests, would improve things? Yes

Re: License info Q

Eitan Adler wrote: >> Now, I don't mind drafting a section for the Handbook based on what I can >> find in /usr/ports/Mk *IF* someone who is familiar with the details of the >> license framework is willing to a) check my work before I submit it to the >> docs@ team and b) answer any questions I

Re: phpMyAdmin port upgrade

Jos Chrispijn wrote: > > The answer is 42, alledgedly. AvW -- Sent from my fridge signature.asc Description: PGP signature

Re: Speedup ports install

Baptiste Daroussin wrote: > IIRC portmaster only creates packages as backup of the installed version > just in case the new package will fail it can reinstall the old one [snip] > Note that the backup thing of portmaster could now possibly be removed > since the ports tree support staging because

How to make a port require at least one option?

Hi all, I'm working on a port that has two options, of which at least one must be selected, but selecting both is OK too. Can somebody please point me to an existing port (surely there must be some already) that has this, so I can see how to use the options framework in this case? Thanks in

Re: php5-phar-5.4.45

The Stupid One wrote: > PHP 5.4 and related ports are set to expire on Jan 15 2015 That should be 2016, obviously. I guess my signature is quite appropriate. AvW -- I'm not completely useless, I can be used as a bad example. signature.asc Description: PGP signature

Re: php5-phar-5.4.45

Jos Chrispijn wrote: > Dear port maintainer, You're aware that is not an actual person, right? It's the general-purpose ports mailing list. When is mentioned as a port's maintainer, that means the port in question doesn't (currently) have a maintainer.

Re: Help needed: ports builds on 10.X but breaks on 9.X

Kubilay Kocak wrote: > Set merge-quarterly to ? in the bugzilla issue report, and ask (in a > comment) for the committer who resolved it in ports HEAD to kindly merge > it :) Thanks to you and Kurt Jaeger for the help. The committer in question has now reassigned it to the security team so I'll

Re: php5-phar-5.4.45

Miroslav Lachman wrote: > It is right, because previously there was only one (moving target) port > "lang/php5" and no php51, php52, php53. Then this was changed to support > more than one version of PHP and lang/php5 is leftover from the past era. That I understand, but I'd expect that now with

Re: Help needed: ports builds on 10.X but breaks on 9.X

Kubilay Kocak wrote: > The real question that informs the decision is: Might/Do the people > using the quarterly want/need this? [snip] > A really way to get a better feel is to browse the quarterly commit log: > > https://svnweb.freebsd.org/ports/branches/2015Q4/?view=log > > However, if

Re: php5-phar-5.4.45

Kurt Jaeger wrote: > Is there an application that does not cope with newer versions of PHP ? A quick survey on Freshports reveals: - 651 ports build-/lib-/run-depending explicitly on *php56*; - 67 ports build-/lib-/run-depending explicitly on *php55*; - 0 ports build-/lib-/run-depending

Re: Help needed: ports builds on 10.X but breaks on 9.X

Thanks to two helpful responses I've been able to patch the port and I'm no longer receiving pkg-fallout messages for the default build, but I am still getting them for the quarterly build. I suspect that the latter is built from a ports tree that gets updated less frequently, so my two remaining

Re: How to close bug which should be reported upstream?

Lev Serebryakov wrote: > How to close bug which should be reported upstream and is not easily > fixable by port maintainer? If I understand your question correctly, you or somebody else has submitted a bug that can only (or almost only) be fixed by the upstream vendor. My suggestion would be

Re: Help needed: ports builds on 10.X but breaks on 9.X

Christian Weisgerber wrote: > As I wrote here two weeks ago... > http://docs.freebsd.org/cgi/mid.cgi?slrnmvro62.94q.naddy I'm not sure how I missed that. Thanks for the pointer. Fonz -- I'm not completely useless, I can be used as a bad example. signature.asc Description: PGP signature

Re: Help needed: ports builds on 10.X but breaks on 9.X

Olivier Duchateau wrote: > devel/gettext-tools is missing (according to build log). Good catch. > There're 2 ways to resolv your problem: > - Patch Makefile (probably search subdir word, where doc directory is > mentioned) > - Add USES=gettext-tools, but don't explicitly disable NLS I'll

Help needed: ports builds on 10.X but breaks on 9.X

Hi all, The port x11-servers/Xfstt, which I maintain, apparently breaks on FreeBSD 9.3-RELEASE while building just fine on 10.X-RELEASE. Initially I thought it was just a random glitch, but I got a second pkg-fallout message, so perhaps something is actually wrong indeed. Unfortunately I don't

Re: tn5250 port

Bob Dobbs wrote: One critical application I need is tn5250 (for connecting to our AS/400s). I've built tn5250 from both ports and installed the package from the repository. It core dumps every time I run both tn5250 and xt5250. I've run it as normal user and as root - still core dumping. Is

Re: revive wmmemload port

Marco Beishuizen wrote: Adding sys/types.h results in less, but fatal errors as well: [snip] --- mem_freebsd.o --- In file included from mem_freebsd.c:18: /usr/include/vm/vm_param.h:94:2: error: unknown type name 'u_int' u_int xsw_version; ^

Re: revive wmmemload port

Marco Beishuizen wrote: But the build stops with a lot of errors: ... In file included from mem_freebsd.c:18: /usr/include/vm/vm_param.h:94:2: error: unknown type name 'u_int' u_int xsw_version; ^ /usr/include/vm/vm_param.h:95:2: error: unknown type name 'dev_t'; did

Re: FreeBSD ports you maintain which are out of date

portsc...@freebsd.org wrote: Port| Current version | New version +-+ science/gromacs | 5.0.5 | 5.1

Re: audio/bristol needs some work

Hans de hartog wrote: Can somebody fix this please? Have you tried asking the maintainer of this port? % make -C /usr/ports/audio/bristol maintainer pierrejacques.mimi...@gmail.com Port maintainers aren't required to provide end-user support (that's optional), but they are the first people

Re: tlmgr on FreeBSD

Carmel NY wrote: although I fail to see why it has been disabled in the port version. As stated previously (although on freebsd-tex@ instead of freebsd-ports@) it hasn't been disabled, it's a separate port (print/texlive-tlmgr). AvW -- I'm not completely useless, I can be used as a bad

Re: FreeBSD ports you maintain which are out of date

portsc...@freebsd.org wrote: science/gromacs I'll have a look at this one and submit a patch if I can make it work. AvW -- I'm not completely useless, I can be used as a bad example. pgpwr2SCglX2v.pgp Description: PGP signature

Re: FreeBSD ports you maintain which are out of date

Yours truly wrote: science/gromacs I'll have a look at this one and submit a patch if I can make it work. No rush, but BR #201921 has been filed. AvW -- I'm not completely useless, I can be used as a bad example. pgpt3UY16l5Ts.pgp Description: PGP signature

Re: Question: License

Larry Rosenman wrote: Portlint suggested I set LICENSE for sysutils/lsof. What is the appropriate value for the following: License === Lsof has no license. Its use and distribution are subject to these terms and conditions, found in each lsof source file. (The copyright year in

Re: freebsd-update causes inconveniences

Carsten Jensen wrote: Installing updates... install: ///usr/src/crypto/openssl/util/mkbuildinf.pl: No such file or directory [snip] mkdir -p /usr/src/crypto/openssl/util/ fixes the problem when trying to run freebsd-update install again. do I need to create a PR for this

Re: FreeBSD Port: valgrind-3.10.0.20150126_1,1

Bryan Drewery wrote: Is there a valgrind port for mips64/freebsd platform? There is only devel/valgrind. There is the ONLY_FOR_ARCHS line in the Makefile. There's also devel/valgrind-devel ;-) But it has the same ONLY_FOR_ARCHS line. Unfortunately both are unmaintained, but perhaps whoever

Re: Time to be real

Mark Linimon wrote: to waste either your time, or valuable electrons. Come now, electrons are overrated. They come with every occurance of beta(-negative) decay. In fact, the intermediate negative W-boson that gives you said electron also gives you an electron antineutrino, entirely free of

Re: x11/xscreensaver-gnome port question

Gerrit wrote: how can I lock the screen by keystroke or button? That has nothing to do with FreeBSD. Or even with PC-BSD, for that matter. It's part of the configuration of whatever window manager and/or desktop environment you're using. AvW -- I'm not completely useless, I can be used as a

Re: [HEADSUP] WIP on fonts

Chris H wrote: P.S. Thanks for doing this. Consistency is nice! :) Seconded. It has already been bugging me somewhat (not enough to complain, but still) that different font ports are/were doing the exact same things differently. Also, kudos for making the announcement so maintainers of font

Re: Philip Brown...United Way of Manatee County

Dave Horsfall wrote: In other words, the FreeBSD lists, by permitting non-subscribers to post to them, are spam-magnets. And the spammers know this. Yep. Most FreeBSD mailing lists do not use e.g. greylisting or something along those lines. And as a result, a lot of spam gets through.

Re: [x11-wm/fvwm2] Build failure with Clang

Dimitry Andric wrote: now building x11-wm/fvwm2 with Clang fails with a linking error at FvwmGtk. But with lang/gcc48 it rather strangely builds just fine. I've tried building this port with various options enabled and disabled, but I cannot reproduce your linking errors. If I would have

Re: reports down?

Mathieu Arnold wrote: should be back sometime in January when the migration to poudriere is complete. That's great news. Thanks for the update. AvW -- Imbibo, ergo sum. pgphZ5WcdzPvO.pgp Description: PGP signature

Re: How do I recover from misc/gnomehier removal??

Bob Willcox wrote: With the removal/deletion of the misc/gnomehier from ports a bunch of my ports now won't update (via portupgrade). How do I recover from this without removing and reinstalling the 41 ports that I have installed that were dependent on it? I use portmaster rather than

Re: gnomehier

Jos Chrispijn wrote: === The misc/gnomehier port has been deleted: [snip] gnomehier deinstall won't work anymore as its portfolder is gone... Even with the port *directory* gone, either pkg delete gnomehier or pkg_delete gnomehier-version (if you're still on the old pkg_* tools) should

Re: gnomehier

Jos Chrispijn wrote: Reason why I asked is because I ran into problems some months ago when I used pkg to delete a port and promised myself to only use portmanager to upgrade and the port folder [sic] itself (cd /portdirectory and port deinstall -clean-) to deinstall a port. It just might be

[x11-wm/fvwm2] Build failure with Clang

Hi everybody, Before asking the maintainer and/or submitting a PR, perhaps someone here knows what's up with the following. Since I rebuilt several ports due to graphics/imlib having been deleted and graphics/png having been updated, now building x11-wm/fvwm2 with Clang fails with a linking error

Commit Request: Bug # 192681

Bugzilla link: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192681 Can a committer please have a look at this? This Bug has been open since August, waiting for either a patch from the submitter or the upstream vendor to commit a GitHub pull request. Neither have happened so far, so I

Re: removing a dir, regardless of content

Dan Langille wrote: A webapp, www/bacula-web puts cache files at %%BASE%%/application/view/cache and on deinstall, that directory should be removed, even though there are files there. Can that be done? I???ve tried this in pkg-plist: @unexec rm -rf %%BASE%%/application/view/cache Just

Re: removing a dir, regardless of content

Dan Langille wrote: Just to be sure: did you remember to add BASE to PLIST_SUB in the Makefile? You probably did, but I figured I'd ask anyway. Is this what you mean? $ grep PLIST_SUB Makefile PLIST_SUB=WWWOWN=${WWWOWN} WWWGRP=${WWWGRP} BASE=${BASE} Yes. And it seems to be okay, but

Re: Resetting maintainership

Koop Mast wrote: [snip] ports.txt This one sounds fun, can I have it? :) [snip] Not if you blindly quote an entire message just to insert one single line, you can't ;-) AvW -- Imbibo, ergo sum. pgpOFC3sOukR9.pgp Description: PGP signature

Re: dirmngr-1.1.0_12 conflicts with gnupg-2.1.0_1 (installs files into the same place)

Carmel NY wrote: I just updated, or rather tried to update the gnupg port. it failed with a message that it conflicts with the dirmngr port. We're aware of it: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=526796+0+archive/2014/freebsd-ports/20141130.freebsd-ports But you might want to read

Re: Update of security/gnupg fails because of conflict with security/dirmngr

Yuri wrote: === Registering installation for gnupg-2.1.0_1 as automatic pkg-static: gnupg-2.1.0_1 conflicts with dirmngr-1.1.0_12 (installs files into the same place). Problematic file: /usr/local/bin/dirmngr Yes, that sort of thing seems to be happening a lot lately. I found out that it

Re: Update of security/gnupg fails because of conflict with security/dirmngr

Jerry wrote: The nvidia-driver port had a similar problem. That problem has been corrected. Perhaps applying the same methodology here would be fruitful. If doing that would fix it, then at least I think it's good news that the problems are with individual ports and not with the ports

Re: latex-texmf required-by

Russell L. Carter wrote: I do not love the 2+ hours it takes to build the text/latex-texmf port. I use pkg(8) to maintain a cluster of machines, and I've checked the major culprits and I don't see how the latex-texmf dependency occurs. (I don't specify it explicitly.) [snip] What is the

Re: Getting rid of my ports

Paul Schmehl wrote: I will no longer be able to maintain ports [snip] so I need volunteers to take them over. [snip] Port: byaccj-1.15 Port: chaosreader-0.94_1 I'd be happy to adopt the above two. Regards, AvW -- Imbibo, ergo sum. pgpT3Z5CEgyKN.pgp Description: PGP signature

Re: Getting rid of my ports

Kurt Jaeger wrote: Port: byaccj-1.15 Port: chaosreader-0.94_1 I'd be happy to adopt the above two. You have those two. Thanks. I can submit PRs tomorrow (new maintainer address, additional distfile mirror, etc.) if you want. AvW -- Imbibo, ergo sum. pgpRtqAHl9U82.pgp

Re: libGLE conflicts with nvidia-driver

Maxim V FIlimonov wrote: The question is: what can I do to resolve this conflict? https://lists.freebsd.org/pipermail/freebsd-ports/2014-November/096440.html It's also on the Forums (https://forums.freebsd.org)... AvW -- Imbibo, ergo sum. pgpdjEXuQQ8u2.pgp Description: PGP signature

Re: Xtide Broken on X86 X64 current

Manfred Antar wrote: [begin (sic)] /usr/ports/astro/xtide doesn't complie on amd64 or i386 current for me [snip] [end (sic)] I'm not the maintainer of this port, but I'm running some exploratory diagnostics on it right now. AvW -- Imbibo, ergo sum. pgp0ZwAhHnfZu.pgp Description: PGP

Re: How does a port maintainer use the bug database?

Kimmo Paasiala wrote: I submitted the PR with a different email than the one on the maintainer field [snip] Is it now just a case of waiting till someone with commit rights picks up this PR or something else? Do you have a Bugzilla account for the address listed as maintainer? If so, log in

Re: How does a port maintainer use the bug database?

Kimmo Paasiala wrote: My only Bugzilla account is on this address I???m now posting from. I think I got, change the flags on the patch to maintainer-approval plus (+), is that all? Even with maintainer-approval the PR (or bug, as Bugzilla calls it) still has to be picked up by a committer,

Re: Xtide Broken on X86 X64 current

Manfred Antar wrote: [begin (sic)] /usr/ports/astro/xtide doesn't complie on amd64 or i386 current for me It uses /usr/local/bin/gcc48 for compiler. [snip] If you: vi ./work/xtide-2.13.2/xxGlobal.cc and add to top of file: extern C int isnan (double); It will compile. [end (sic)]

Re: Redports and leftovers calculation

Fernando Apestegu??a wrote: While working on a new port, my builds report leftovers as if I'm wiping out /usr/local on package removal: [snip] Can anyone please confirm these? It's a known problem. The main suspicion is that the recent changes to ports-mgmt/pkg have broken Tinderbox, which in

Re: pkg 1.3.8 requested but not available?

Patrick Gibson wrote: Either way, something seems broken or not well thought out. It also appears to have broken Tinderbox, BTW. If I got that wrong, forget I said anything. But if it's right: nice job! AvW -- Imbibo, ergo sum. pgpj_I26hh29b.pgp Description: PGP signature

Re: Lusca off from ports

EnioRM wrote: Have you any information about why lusca was removed from ports/pkg If you mean www/lusca-head, it was removed because nobody converted it to support STAGEDIR. You could have found that information on Freshports. If you feel like resurrecting it, you'll need to either retrieve

Re: require root priveleges for port build

Jan Beich wrote: NEED_ROOT seems to an undocumented hack for staging. Can someone suggest a way to force build be performed under root? A quick grep in /usr/ports/Mk/ indeed doesn't turn up any documentation on NEED_ROOT. According to the Porter's Handbook section 3.4: Make sure that make

Re: FreeBSD unmaintained ports which are currently marked broken

lini...@freebsd.org wrote: portname: astro/wmmoonclock broken because: No public disfiles build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=astroportname=wmmoonclock [snip] portname: games/wmfortune broken because:

Re: FreeBSD unmaintained ports which are currently marked broken

Thierry Thomas wrote: wmmoonclock is still available from the author's page: http://www.cs.mun.ca/~gstarkes/wmaker/dockapps/time.html#wmmoonclock wmfortune is available at GNU/Darwin: http://www.gnu-darwin.org/distfiles/wmfortune-0.241.tar.gz and wmblob from SourceFiles:

Re: xemacs (zombie port, but worked)

George Michaelson wrote: Did it have to die? (pkg removed it) If I understand Baptiste's commit message correctly, it was no longer maintained upstream. I suppose you could keep the port alive locally, but this will probably take some effort (adding STAGEDIR support, for example). AvW --

Re: XEmacs

[Removed completely unnecessary CC to stable@] Dan Andersen wrote: What happened to XEmacs? http://www.freshports.org/editors/xemacs AvW -- Imbibo, ergo sum. pgpaGJUujWxhq.pgp Description: PGP signature

Re: package availability

Robert Huff wrote: I'm looking for a package of fftw3-3.3.3_2, built for amd64 with default options. pkg search fftw3 reports 3.3.3_1. When is 3.3.3_1 likely to become available? You probably meant: when is 3.3.3_2 likely to become available? That sounds like something you

[TeX] Migrating from teTeX to TeX Live

Howdy, As we all know the old teTeX ports are now pretty much obsolete and TeX Live should be used instead. Yesterday we received a question on the FreeBSD Forums about exactly how to migrate from teTeX to TeX Live. First things first: is there an easy path using e.g. Portupgrade or Portmaster,

Re: Tor web browser

Kurt Jaeger wrote: Is there a port of the Tor web browser https://www.torproject.org/ available? The site lists one for BSD, but I would prefer to get it via the port's system I'm not aware of a port, but would like to have one, as well. Same here. I only knew there was a Windows version;

Can someone please commit PR 186638?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186638 The proposed patch has been examined and slightly reworked. The new patch is maintainer approved. Thanks in advance, AvW -- Imbibo, ergo sum. pgp8sP7Wm69F_.pgp Description: PGP signature

[Bugzilla] How to approve patches?

Hi all, A helpful someone submitted a PR with a patch for a port I maintain. I remember that back in the GNATS days, when this happened I had to reply to an e-mail if I approved of the patch. But with Bugzilla I'm not sure. I added a comment to the PR that said Maintainer approved, but I don't

Re: [Bugzilla] How to approve patches?

Tijl Coosemans wrote: So, in short: with the new Bugzilla system, how does a maintainer (who is not a committer) respond to a PR in order to get the patch committed? Set Status field to Patch Ready. I've had a long, hard look at the Bugzilla page, but I can't find any way to change the

Re: [Bugzilla] How to approve patches?

Kurt Jaeger wrote: A short mail to ports@ with can some committer please commit PR ... is one way to find one. It might get noisy in the future 8-} That sounds a bit cumbersome, but I'll give it a try. Thanks. AvW -- Imbibo, ergo sum. pgpJIxZgYfre6.pgp Description: PGP signature

Can someone please commit PR 191725?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191725 I am the maintainer of said port and approve the patch that comes with this PR, so I'd appreciate it if somebody can commit it. Thanks in advance, AvW -- Imbibo, ergo sum. pgpbunNbioHD1.pgp Description: PGP signature

Re: Can someone please commit PR 191725?

Kurt Jaeger wrote: Done. Thanks. So the PR can be closed now. AvW -- Imbibo, ergo sum. pgp34tsF0taGp.pgp Description: PGP signature

[Portlint] Staging warning

[CC: Portlint maintainer] Presently, running Portlint on an unstaged port results in a *warning* that says Consider adding STAGE support. I'd surmise that a fatal error along the lines of STAGE support will be mandatory pretty damn soon would be more appropriate. Just a thought, AvW --

Re: please set math/gnuplot PDF=off by default, or resolve texlive vs teTeX

[Added CC to freebsd-tex@] Baptiste Daroussin wrote: On Mon, Jul 07, 2014 at 07:32:23PM +0100, Anton Shterenlikht wrote: # make -C /usr/ports/math/gnuplot/ showconfig === The following configuration options are available for gnuplot-4.6.5_3: CAIRO=on: Cairo graphics library support

Re: FreeBSD Port: observium-0.11.5.2261_1

David Hunt wrote: [[root@NAS /usr/ports/net-mgmt/observium]# pkg search -f observium [root@NAS /usr/ports/net-mgmt/observium]# pkg update Updating repository catalogue [root@NAS /usr/ports/net-mgmt/observium]# pkg search -f observium [root@NAS /usr/ports/net-mgmt/observium]# The above

Re: FreeBSD Port: observium-0.11.5.2261_1

David Hunt wrote: Should this port install using pkgng? [root@NAS ~]# pkg info observium pkg: No package(s) matching observium That only means the port hasn't been installed yet, that's what pkg info is for. It displays information about *installed* packages. For packages you haven't

Re: FreeBSD ports that you maintain require staging updates

portmgr-feedb...@freebsd.org wrote: Ports that you maintain that are currently unstaged (NO_STAGE=yes): [snip] emulators/nonpareil I offer to take a look at this, but I do seem to remember that there are some other issues with this port so I might need some help at some point.

Re: FreeBSD ports that you maintain require staging updates

Bryan Drewery wrote: If you see a port in here that you use and wish to keep working please consider becoming maintainer of it. Submit a PR with a patch to stage it and take maintainership of it. [snip the rest] Will do (read: am doing). Unfortunately some of these ports require more than

[Stagedir] x11-fonts/sgifonts pending issues

Attempting to stagify x11-fonts/sgifonts I'm still stuck with two issues: -1- No license is specified. There's no clue in the distfile and the WWW only reveals that this port is part of a collection of things that are either GPL or LGPL, but it doesn't specify which is which. And the authors can

Re: [Stagedir] x11-fonts/sgifonts pending issues

Rainer Hurling wrote: So, is it permissible-although-undesirable to leave LICENSE unspecified? Or is there another recommended solution? One possibility could be LICENSE=GPLv2 LGPL21 LICENSE_COMB= dual 'dual' means OR, 'multi' means AND, see Mk/bsd.licenses.mk Okay, thanks!

Re: How are ports built now

[snip snipperdy snip] Olli, was it really necessary to quote all 236 (!) of those lines? AvW -- I'm not completely useless, I can be used as a bad example. pgpQMWtVlnLfC.pgp Description: PGP signature

Re: pkg 2 ng conversion

Jim Pazarena wrote: this process is a little confusing. do I still need to run portsnap fetch ? PKGNG is a packaging system, not a building system. If you need a ports tree (usually for BUILDING ports/packages from source, although there are other reasons occasionally), then yes, you need to

Re: How are ports built now

Paul Schmehl wrote: Recently I upgraded two servers to 8.4 and implemented the pkgng system. [snip] Is portmaster not the appropriate method for updating ports with pkgng? It depends whether you're talking about *building* packages from the ports tree or installing binary packages. As for

Re: Who was the mental genius

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

Re: drop maintainership of 6 ports

Torsten Zuehlsdorff wrote: 3. If you can, mirror the distfile and add your site to MASTER_SITES. I could easily mirror the distfile. But i'm unsure where to add the entry. There is an entry MASTER_SITE_NETLIB in /usr/ports/Mk/bsd.sites.mk, which definies the url for the distfiles. But if i

Re: drop maintainership of 6 ports

Torsten Zuehlsdorff wrote: Thank you very much! You're welcome. And, of course, welcome to maintainerhood :-) I think it's a nice and productive way of getting involved with FreeBSD. AvW -- I'm not completely useless, I can be used as a bad example. pgp3ofo0dRI56.pgp Description: PGP

[games/oneko] Maintainer timeout

PR ports/189050 was submitted at 27 April, with a patch for a trivial problem. So far, over a month later, said PR is still stuck on awaiting maintainer feedback so I'd say this qualifies as a maintainer timeout. Could a committer at least have a quick look at this? Furthermore, if (and only if)

Re: drop maintainership of 6 ports

Torsten Zuehlsdorff wrote: devel/fpp Whats the next step? Writing a patch to change maintainer? In a nutshell: 1. Check upstream to see if there's no newer version. If there is, try to update the port. 2. Change MAINTAINER, indeed. 3. If you can, mirror the distfile and add your site to

Re: drop maintainership of 6 ports

A.J. 'Fonz' van Werven wrote: Whats the next step? Writing a patch to change maintainer? In a nutshell: [snip] Which reminds me: if this is the first time you're actually going to be a maintainer, there's a thread on the Forums that you may find useful: https://forums.freebsd.org

[PATCH] Re: drop maintainership of 6 ports

Anton Shterenlikht wrote: I can no longer maintain these ports: astro/xearth [snip] Please reset I'm willing to take that one. The attached patch modifies MAINTAINER and adds my own distfiles mirror to MASTER_SITES. AvW -- I'm not completely useless, I can be used as a bad example. ---

[graphics/gegl] Incorrectly stagified?

Building graphics/gimp breaks on graphics/gegl. It builds fine, but fails to install. The complete build log can be found at http://www.skysmurf.nl/~fonz/tmp/gegl.log but the last lines (see below) suggest to me that graphics/gegl hasn't been entirely correctly stagified. Any suggestions? AvW

Re: Nowhere to be found: pciids-20140526.tar.xz (misc/pciids)

Beeblebrox wrote: How come your # make fetch looked up distcache.FreeBSD.org, while mine does not. Do you have a special PKGSITE defiend? No, not at all. However, this distcache bussiness is mentioned in /usr/ports/Mk/{port,sites}.mk, the former of which appears to have been updated yesterday.

Re: License

Jerry wrote: I am trying to create a new port. If I put: LICENSE= BSD portlint is happy; however, running make makeplist reports an error: LICENSE must not contain BSD, instead use BSD[234]CLAUSE There's no such thing as the BSD license, you have to choose one of a few varieties.

Re: [x11-fonts/sgifonts] Dynamic plist and double pkg-message

Matthew Seaman wrote: -1- [snip] Dynamic plist generation is fine. Okay, thanks. -2- When testing whether it works with portmaster -g I noticed that pkg-message is being displayed twice. Is this normal behaviour, or did I do something wrong? Come to think of it, it appears to be

[x11-fonts/sgifonts] Dynamic plist and double pkg-message

L.S., While seeing if I can prevent ports I'm using from being taken out and executed by a firing squad for not having been stagified yet (and yes, I'm willing to take maintainership of orphaned ones) I stumbled across the following two issues involving x11-fonts/sgifonts: -1- This port uses a

Re: Repair pkgng

Adam McDougall wrote: A clean /var/db/pkg has these contents (or similar): auditfile local.sqlite repo-FreeBSD.sqlite vuln.xml A clean /var/db/ports directory has these contents */options That's it. No distfiles. I believe I've heard /var/db/pkg/something/distfiles is a

Re: FreeBSD ports which are currently scheduled for deletion

Tijl Coosemans wrote: For xmms there's xmms2 That's no comparison. Not even fracking close. I for one am very glad that Christian Weisgerber is having a look at the XMMS-related ports. AvW P.S. I do agree with your message as a whole, just not with this particular example. -- I'm not

[mail/xmailbopx] Exactly what does unmaintained mean?

Hi all, The port mail/xmailbox is set to be removed soon because it has been unmaintained since 2000. In this case, does unmaintained refer to just the FreeBSD port, or to the software itself? And in either case, is there anything that can be done to prevent removal? AvW -- I'm not completely

Re: [mail/xmailbopx] Exactly what does unmaintained mean?

Antoine Brodin wrote: Would you like to take maintainership of this port, and add stage support to it? In and of itself, sure, of course. But I'd need some time to thoroughly check and sort out this port: stagify, check for a newer upstream version, see if there's really no WWW, (as Kurt

Mysterious patches

Having a look at graphics/libgfx (I'm using that port but it's currently unmaintained so I might feel like taking maintainership), I noticed that there are two patches in /usr/ports/graphics/libgfx/files/ *BUT* I can't for the life of me find the files they are supposed to be applied to. Can

Re: Mysterious patches

Henry Hu wrote: They apply to src/raster-png.cxx and src/raster.cxx Note to self: look inside the actual patch files themselves, it says right there which files they apply to *oops*. However, this does leave me puzzled about the file names. If a patch applies to, say, src/foo/bar.c, shouldn't

  1   2   >