On Wed, Jan 16, 2013 at 01:51:39AM +, RW wrote:
Reports are sent to ports@ every 2 weeks.
And I wonder how many people read carefully through all 478 entries.
And your suggestion is ... ?
mcl
___
freebsd-ports@freebsd.org mailing list
The build farm is still offline awaiting the code to be updated to a
point where it will pass a security review.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
On Sat, Mar 09, 2013 at 08:33:06PM +1030, Gavin McDonald wrote:
I'm happy to take maintainership of this one.
Done, thanks.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any
We should step back and define the problem.
The problem IMHO is that we have optimized for users who wish to save
the maximum space on their systems, at the expense of users who want
to install and upgrade ports with the minimum fuss.
IMHO we should do the opposite.
I think the number of users
On Wed, Jun 19, 2013 at 01:51:42AM +0200, Oliver Pinter wrote:
3) Is not it better to submit via PR (GNATS) rather than a mailing list?
That's what PRs are for...
Mail are faster than PR-s.
If we all go down that route, it means less and less people will try
to read all the traffic on
On Wed, Jun 19, 2013 at 04:03:36AM -0700, Thomas Mueller wrote:
Now I am a bit confused, should it be x...@freebsd.org or
freebsd-...@freebsd.org, or is one an alias for the other?
They are aliases.
mcl
___
freebsd-ports@freebsd.org mailing list
On Thu, Jul 18, 2013 at 10:04:52AM +0200, Erwin Lansing wrote:
You bet it is! Know you know what portmgr has been spending its time
on for all those years and why we keep sining the same old song about
quality control and pre-commit (and not post-commit) testing
ITYM singing :-)
In any
On Sun, Aug 04, 2013 at 09:14:32PM +0200, Marcin Wiśnicki wrote:
But didn't it use to show last successful builds too ? Now it just
says None which is not very helpful.
No, it doesn't have that information, sorry.
mcl
___
freebsd-ports@freebsd.org
Since the time that the RELEASE_4_EOL tag was applied to the Ports
Collection, much of the legacy support for 4.X has been removed from
individual ports (e.g., special-case code for old header layouts,
marking ports BROKEN, and removing the checks for the antique perl in
base). At this point
This is probably due to some piece of code that is special-case for 4.X
being removed. More is on the way (see my headsup from ~12 hours ago).
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
Hmm, I may have spoken too quickly, there is a report of this same problem
on 6.2. Never mind my noise.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL
On Fri, Mar 09, 2007 at 02:53:03PM -0800, Eric P. Scott wrote:
i386 and amd64 builds are failing as though something were forcing
USE_AUTOTOOLS=libtool:15
and bypassing the included libtool. What's the difference?
There was a checkin that indeed did just that, to try to work around
, it is almost certainly
either kern or bin (unless you think it is particular to a processor
or motherboard, in which case it is i386/amd64/etc.).
Thanks.
Mark Linimon, for the bugbusting team
*http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html
On Wed, Mar 21, 2007 at 04:51:08PM -0400, Alfredo Perez wrote:
Do I need to be the maintainer of Openssh to submit a PR with a diff?
No. We will forward your PR to the maintainer.
mcl
___
freebsd-ports@freebsd.org mailing list
On Wed, Mar 21, 2007 at 08:15:37PM -0400, Alfredo Perez wrote:
That is the thing, the port does not have a maintainer
Well, it will stay in the queue until a ports committer takes an interest
in it.
mcl
___
freebsd-ports@freebsd.org mailing list
On Fri, Mar 23, 2007 at 03:32:33PM +0100, Alexandre Brooks wrote:
I'm currently trying to install www/rt36 port, with apache22 and
mod_perl2, but this requires me to build the perl5 interface to
libapreq2 (www/p5-libapreq2). Only problem, it is broken.
You should mail the maintainer ([EMAIL
Until someone implements some kind of capabilities system, we're stuck
doing a bunch of logic in Makefiles.
One problem no one has come up with a good solution for is mixing
packages (with standard prerequisites) with installed ports (with
custom prerequisites).
mcl
gotten a bounce message; the messages are in the
queue waiting to be hand-processed.
I'll send an all-clear when the situation is resolved.
Thanks for your patience.
Mark Linimon
for bugmeister@
___
freebsd-ports@freebsd.org mailing list
http
It's now clear to send PRs again. It will take a little while to
clear out the backlog.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Wed, Apr 25, 2007 at 11:35:16AM +0530, Amarendra Godbole wrote:
I then queried the database to see if the PR was submitted, but nothing
turned up.
It takes 5-10 minutes for the automated processes all to run to process
the latest PRs before they will show up on the web page.
mcl
On Wed, May 02, 2007 at 11:36:03PM +0200, Gerald Pfeifer wrote:
Does this freeze apply to the whole ports tree, or only (relatively
directly) affected parts of the tree?
The latter is basically most of the tree :-)
mcl
___
freebsd-ports@freebsd.org
So, is it time to mark it as obsolete and pull it from ports?
Yep, sounds like. Just send-pr it and it will get assigned to the
maintainer (or this list if it's maintained by [EMAIL PROTECTED])
mcl
___
freebsd-ports@freebsd.org mailing list
The output from each port's make describe is documented at the
describe target in:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk
This is changed to a different format (a historical bug, too late to fix
now because of POLA) via make index from ports/Makefile by the following
script
On Tue, May 08, 2007 at 07:49:02AM +0200, [LoN]Kamikaze wrote:
Submit a PR and request a maintainer timeout. This will take a long time,
but it's the only way.
long time = 2 weeks
mcl
___
freebsd-ports@freebsd.org mailing list
On Tue, May 08, 2007 at 10:23:43AM +0200, [LoN]Kamikaze wrote:
The last time I requested a maintainer time out it was something like
two months.
I have been much more active in the last few months on enforcing the
maintainer-timeouts.
If you are having problems, please email portmgr@ directly.
On Tue, May 08, 2007 at 11:58:43AM -0500, Sam Stein wrote:
I've already submitted a pr with the update; before I read about the
maintainer timeout; should I just wait it out a while, and if nothing
happens, request one? Or do it right away?
Just wait it out for a while. At the moment, we're
On Thu, May 10, 2007 at 10:48:30AM +1000, [EMAIL PROTECTED] wrote:
The latest release of PHP is out (as at May 3) and I'm just wondering if
there's a schedule for updating the port - this release corrects some not
insignificant security vulnerabilities.
We are in an unusual ports freeze to do
On Thu, May 10, 2007 at 10:00:06AM +0200, [EMAIL PROTECTED] wrote:
Do you know that PHP 5.2.1 has a Security Enhancements and Fixes in
PHP 5.2.2 and PHP 4.4.7 as reported on www.php.net? When will be
available the PHP 5.2.2 in the ports?
Please go read the archives of this mailing list over
On Sat, May 19, 2007 at 01:51:02PM -0700, Garrett Cooper wrote:
Wouldn't it be sufficient to force major component testers (in this
case Xorg 7.2) to use periodic snapshots of the ports tree (possibly CVS
branching), while allowing continued development in the ports tree?
In this particular
On Mon, May 21, 2007 at 09:15:44AM +0200, Hans Lambermont wrote:
Do you happen to have a portmaster version of UPDATING:20070519 users of
x11/xorg ?
I think he may have gone to sleep already, so I'll step in and answer
for him that he is working on it and may have a patch shortly.
mcl
On Tue, May 22, 2007 at 02:20:43PM +0200, Dag-Erling Smørgrav wrote:
Then you need to run a kernel that corresponds to the newest userland
the tinderbox wants to run - or from a different perspective, configure
the tinderbox to only run userlands as old as or older than your kernel.
Yes,
On Tue, May 22, 2007 at 05:34:32PM +0400, Andrew Pantyukhin wrote:
A seemingly better way may be to make these system vars
available in make by default.
Doesn't help anyone who runs -RELEASE, so a non-starter.
mcl
___
freebsd-ports@freebsd.org
Synopsis: [PATCH] security/pam_per_user conflicts with security/courier-authlib
Responsible-Changed-From-To: freebsd-ports-freebsd-ports-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu May 24 11:15:30 UTC 2007
Responsible-Changed-Why:
Fix assignment.
On Thu, May 24, 2007 at 09:21:09AM -0400, Robert Huff wrote:
I'm having the same issue. Investigating a little reveals the
size as listed in distinfo as 190172 and the size of the downloaded
tarball as ~7200.
Generally mismatches like this are returning HTML pages instead of the
desired
On Thu, May 24, 2007 at 12:02:39PM -0700, Walter Ian Kaye wrote:
All right, who released my email address to spammers?
The mailing lists are public and mirrored all over the world. It's too
late for that address, sorry.
mcl
___
If you use 'make update', the default method is going to become portsnap.
Currently, if you do not define one of the Makevars PORTSNAP_UPDATE,
SUP_UPDATE, or CVS_UPDATE first, the code just complains at you and
does nothing.
This is one less thing that has to be set by default by an
On Mon, May 28, 2007 at 12:15:28AM +0200, Michel Talon wrote:
To gain some performance, a first idea would be to simplify
bsd.ports.mk. I am convinced that a substantial part of the 4000 lines
are historical crap which serve no useful purpose.
11272 of LOC in bsd.*.mk, but who's counting.
On Mon, May 28, 2007 at 10:16:11AM +1000, Edwin Groothuis wrote:
It has been discussed on IRC, and I'm pretty sure that flz@ has
been thinking about it during his sweat-shop-job. My opinion is:
let's do the upgrade to 7.2 and the new framework first, then see
what can be done about OPTIONizing
I can't build index after recent update of ports via portsnap:
wait..astk-client-1.5.0.1_2: /usr/ports/shells/bash2 non-existent --
dependency list incomplete
As a reminder to committers, when removing stale ports, you also have to
check the _optional_ dependencies in port Makefiles (yes,
On Thu, Jun 07, 2007 at 06:16:38PM +0200, Daniel Stefan Haischt wrote:
attached you will find an modified wzdftpd port. Included are just
changed files.
fwiw, if you're going to Cc: to the list, you may as well just file it
as a PR and then it will be auto-assigned to novel. Postings to the
On Sat, Jun 09, 2007 at 07:48:44AM +0200, [LoN]Kamikaze wrote:
So you better file a PR to step back from maintainership, so that volunteers
don't have to wait for a time out.
Already taken care of.
mcl
___
freebsd-ports@freebsd.org mailing list
On Sat, Jun 16, 2007 at 07:50:14AM -0500, Jack Stone wrote:
You could simply edit the Makefile in the samba port and reset the version
shown at the top to the old version.
Then, delete distinfo
Then 'make makesum'
Then 'make install clean'
If the old port still remains in your
On Sun, Jun 17, 2007 at 12:15:16AM -0600, M. Warner Losh wrote:
I want a list of all the ports in /usr/ports that install kernel modules.
IIRC they're all in misc/. Let me see if I can come up with a quick list.
mcl
___
freebsd-ports@freebsd.org
On Sun, Jun 17, 2007 at 12:42:01AM -0600, M. Warner Losh wrote:
I'd kinda hoped there was a pseudo category that I could key off of.
Kinda sounds like there should be.
Here's my list so far:
audio/aureal-kmod
audio/emu10kx
comms/hcfmdm
comms/ixj
comms/ltmdm
comms/uticom
comms/vpb-driver
ok, good luck on getting caught up.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Thu, Jun 28, 2007 at 06:38:24AM -0700, David Southwell wrote:
There is a difficulty when posting PR's when a large debug file is needed to
be posted to the PR as an attachment.
Do you mean, via the web form or via send-pr(1)? The latter has a limit
of 500k, via the FreeBSD.org email
On Mon, Jul 02, 2007 at 12:34:20PM +0200, Tim Rijavec wrote:
can you add this package for ChartDirector for php to FreeBSD ports?
that can be found at http://www.freebsd.org/ports/master-index.html
Please use send-pr to submit this so that it won't just get lost in the
mailing list traffic.
I have just updated portsmon to the most recent development code. Most of
this code has to do with the ability to create dependency graphs of failed
or broken ports, and is not yet totally automated; thus, it is not (yet)
visible to users. Other code has to do with internal schema changes.
The
On Fri, Jul 20, 2007 at 05:11:27PM +0200, Michel Talon wrote:
The only relevant info for determining what to install or build
previously is RUN_DEPENDS and BUILD_DEPENDS. Everything else is garbage.
The pointyhat error logs would tend to indicate that this isn't correct.
mcl
On Fri, Jul 20, 2007 at 12:40:02PM -0700, [EMAIL PROTECTED] wrote:
the INDEX files -- so many that I think that items common to both
build_deps and run_deps should be isolated and put into a new category
called 'common_deps':
How will this benefit us?
Doug
Reduce amount of processed
On Fri, Jul 20, 2007 at 08:58:55AM -0400, Bill Moran wrote:
Why? Is there a legitimate reason why the fetch process refuses to
download this?
The intention of the logic is to warn a user, as soon as possible, that
they are spending time on something that will wind up being IGNOREd if
it is
On Fri, Jul 20, 2007 at 04:07:49PM -0400, Bill Moran wrote:
Even better would be for make to realize that it's only doing the
fetching, and do it anyway.
That still doesn't help with the problem of a user who starts a 10MB
download that won't work on his architecture or OS release. The code
is
I assume that you've already emailed the person? If so, sending email
to portmgr@ is the right way to go. We'll attempt to find out if the
person is busy/on vacation/overloaded/etc.
mcl
___
freebsd-ports@freebsd.org mailing list
I'm actually doing a slight superset by looking at dependent ports
of (ignore/broken/forbidden/failed) ports, now that I have updated the
graph and can see it better.
It sounds like people are already working on the misc/compat3x dependents.
Most of these ports are antiques.
IMHO sysutils/eject
In general the way we want to assign maintainership is in conjunction
with a port update/fix. Please submit anything that you come up with
via GNATS.
Even if in the meantime the port gets deleted, it can easily be brought
back from the Attic.
Thanks for volunteering to help.
mcl
On Fri, Jul 27, 2007 at 12:39:51PM +0530, Alagarsamy A wrote:
can you please update it to latest version 0.80
(http://nsc-gothix.sourceforge.net/) ?
ports@ is the default maintainer. No update will happen until someone
(you?) submits a PR for it.
mcl
On Wed, Aug 01, 2007 at 03:17:24PM +0200, Mark Evenson wrote:
Which I would do but the [FreeBSD Bugs database][1] seems to not be
returning any matches to queries
Seems to be working fine for me now. However, I've seen a 'no PRs found'
page to be displayed sometimes, possibly due to some
On Sat, Aug 04, 2007 at 06:01:48PM -0700, Doug Barton wrote:
The following line was placed first in the file, instead of in
chronological order. Is there a reason that it needs to be first?
This is a bug. Fixed.
mcl
___
freebsd-ports@freebsd.org
These reports deal with package failures, adding together all packages
that are intentionally not made, packages that fail, and all the packages
that depend on them.
Initially I generated these as graphs via GraphViz. However, the
resulting images are so large that they take minutes to display
On Sun, Sep 02, 2007 at 01:50:36AM +0200, Nils Vogels wrote:
Since a little while, Debian has been using a popularity contest, that
sends anonymous usage details of various packages that Debian users have
installed.
See sysutils/bsdstats. It apparently has not yet been extended to
The refactoring that gabor has done to recreate bsd.perl.mk will be
imported soon, along with the many ports that it simplifies. Due to
the size of the patch, I expect there to be collisions that I will have
to adjust as I go, so expect the tree to be broken briefly while I work
through the
This should fix the remaining perl-related problems that people were seeing,
each related to ports that conditionally included perl.
The only remaining regressions that I can't yet explain are the following:
*/fpc-* fail to compile due some kind of flag failure. (They work on
my 6.2
On Sat, Oct 06, 2007 at 05:40:05PM +0200, Max Laier wrote:
On Sunday 30 September 2007, Mark Linimon wrote:
Despite the fact that this was tested on the cluster, this upgrade has
failed. Please hold off upgrading your ports tree until we can figure
out what the problem is. Thanks.
Did
(For those who are not familiar with the FreeBSD Ports Monitoring System,
or portsmon, that I wrote and maintain, you'll find more information at
portsmon.freebsd.org.)
To get ready for the 7.0 release, I've switched its model of the default
ports build environment from i386-6 to i386-7. This
When we upgraded the machine that hosts these reports, we missed some
files, and the reports came out null. I am currently working on testing
the corrected script. While I'm working on it, I'm going to make a few
tweaks. Let me know if you see anything odd in the results.
mcl
On Tue, Jul 04, 2006 at 05:27:55PM -0300, Márcio Luciano Donada wrote:
Port py-punjab (ports/net-im/py-punjab) has been removid from ports
collection?
cvsweb does not report it having been in the Ports Collection, nor is
there an entry in MOVED. There is a pending PR to create one, however:
On Thu, Jul 06, 2006 at 09:58:54PM +0300, Ion-Mihai IOnut Tetcu wrote:
Actually support for 4.x is gone already. We're only required to mark
the ports broken or incorporate patches from the users. Of curse, we
try to fix broken ports on 4-STABLE but that battle is going to be lost.
The latest
On Fri, Jul 07, 2006 at 02:45:02AM +0400, Boris Samorodov wrote:
I noticed a few days ago that the first site at FEDORA_CORE_SITES
(limestone.uoregon.edu) is acting not reliable. Your logs says the
same (most distributions were taken from the next site --
mirrors.kernel.org). I'd rather delete
On Thu, Jul 06, 2006 at 09:55:47PM -0700, Doug Barton wrote:
I think you're right about that, and my preferred method of operation for
the ports that I maintain has been to try and test on RELENG_4 whenever
possible, but not let not testing stop me from updating a port that works on
7-current
On Fri, Jul 07, 2006 at 11:02:20AM +0400, Boris Samorodov wrote:
I searched error messages at the last build at pointyhat. Strange
enough but the build for x11-toolkits/linux-gtk used rather old ports
tree. Current version is 1.2.10_3 (I committed a patch at Tue Jun 27
12:35:33 2006 UTC). The
On Thu, Jul 06, 2006 at 09:55:47PM -0700, Doug Barton wrote:
The way you break those numbers down is interesting. On i386 there are 206
errors on -4, 277 on -5, 119 on -6, and 151 on -7.
The key fact that I missed in my first reply to this is that the -5 run
was killed because there was some
On Fri, Jul 07, 2006 at 12:18:15PM -0500, Matt Sealey wrote:
I guess this has been completely looked over since BSD tar got very
clever about it. The worry is.. isn't 4.x totally obsolete, unsupported
now, and therefore not worth coding that fix for? :D
The policy is that we no longer require
On Fri, Jul 07, 2006 at 01:33:55PM -0500, Matt Sealey wrote:
Well this is a kind of internal-to-ports thing that needs a
small change, not really a fix linux-dri thing. It could happen
with plenty of packages, so who deals with that?
There is no individual who's on the hook for that, exactly.
On Fri, Jul 07, 2006 at 01:49:51PM -0500, Matt Sealey wrote:
Yeah wouldn't a solution be to have bsdtar have a PORT_REPLACES_BASE kind
of thing?
Or a use.tar like use.perl?
Well, it would be, if we were going to continue to support base systems
without bsdtar already in them :-)
mcl
This has already been fixed. Please re-cvsup and try again.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
BTW, I apologize for this is not at all a portupgrade issue, but an issue
of the ports system.
It is an issue with individual ports -- actually not the port (e.g.
Makefile framework, pkg-*) but the individual applications (IIUC).
Well, at least the ports system itself should not be broken
this is last call; please mail to me off-list if you are one of these
folks and wish to keep your ports, or you otherwise know that these folks
are still active. Thanks.
Mark Linimon
for [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL
All I see is the following update with the text update to version 9.3.7,
approved by: maintainer timeout by danfe (there were no PRs with libticables
in the Synopsis):
http://www.freebsd.org/cgi/cvsweb.cgi/ports/comms/libticables/Makefile?rev=1.16content-type=text/x-cvsweb-markup
danfe, any more
On Wed, Aug 16, 2006 at 01:28:36PM -0400, Kris Kennaway wrote:
I think someone (kuriyama?) was in fact already doing this, so getting
the project started would not involve much work.
Yes, that was already set up, but does not appear to be active. I don't
know if the link was supposed to be
On Fri, Aug 18, 2006 at 04:21:38PM +0400, Roman Bogorodskiy wrote:
There are severe logistical problems: Ports are currently expected to
build for at least 3 different src branches, with between 2 and 6
different architectures in each. Multiply this by over 15,000 ports
and that process
Some of the work that I'm currently doing to add the status of packages
to the portsmon reports has meant that I needed to push out some earlier
changes. For the first time, this has involved a Flag Day involving one
of the attribute names in the database. In _theory_ this should not
affect
On Tue, Sep 05, 2006 at 11:33:47AM -0400, Robert Huff wrote:
You get evidence supporting the hypothesis I'm an idiot.
Thanks.
No problem, there are plenty of ways to shoot your feet off, I've spent
the last few decades iterating over them.
mcl
Here is the result of a discussion amongst the portmgr members during the
past few weeks, in response to the large number of new ports added to the
Ports Collection in the last few months.
-
Recently we've seen evidence of an
On Thu, Sep 21, 2006 at 10:01:20AM +0200, Martin Schweizer wrote:
How can I help to do this? How it the corresponding person (the maintainer
is ports@).
[EMAIL PROTECTED] is the string used to indicate that a port is not
maintained by anyone; so until someone steps up and contributes (e.g. by
On Wed, Sep 20, 2006 at 09:27:21PM +0900, Akinori MUSHA wrote:
http://pointyhat.freebsd.org/errorlogs/i386-7-latest/ruby18-mysql-2.7.1.log
Note: Some of those logs may not exist depending on the timing.
The previous errorlogs are always archived. If you have access to pointyhat,
you can find
On Fri, Sep 22, 2006 at 04:21:15PM +0930, Daniel O'Connor wrote:
Is there an easy way to find when the ports tree was checked out for a given
package run?
I have now added a link to the cvsdone file which already existed, to
the page at http://pointyhat.freebsd.org/errorlogs/packagestats.html
On Sat, Oct 14, 2006 at 10:53:32PM -0700, Peter Thoenen wrote:
B) In line with A, has anybody thought about just marking ALL
[EMAIL PROTECTED] as scheduled for deletion on X date.
It turns out that a few of them are key pieces of infrastructure. Perhaps
we can generate a list of ports that we
On Wed, Oct 18, 2006 at 01:06:10PM -0600, Charlie Sorsby wrote:
What does this mean and why is it so?
Wednesday, 18 Oct, 2006 -- 12:59:41 MDT
=== compat3x-i386-4.4.20020925 is forbidden: FreeBSD-SA-03:05.xdr,
FreeBSD-SA-03:08.realpath - not fixed / no lib available.
It means there is no
On Mon, Oct 30, 2006 at 04:48:27PM -0600, Craig Boston wrote:
Is fixing broken ports eligible for commiting during the freeze?
Yes, with portmgr approval, of course.
mcl
___
freebsd-ports@freebsd.org mailing list
On Mon, Oct 30, 2006 at 06:42:45PM -0600, Craig Boston wrote:
Great, I'll file a PR later tonight unless somebody beats me to it.
Well, we just lifted the freeze, so it's too late for 6.2, but it can go
into the ports tree anyways.
mcl
___
On Tue, Oct 31, 2006 at 12:04:34PM -0600, Paul Schmehl wrote:
If I submit PRs for this, do I have to set PORTREVISION to 1? Or does it
matter for such a minor change?
Since it doesn't affect the package (install/deinstall), PORTREVISION
should not be bumped.
mcl
Synopsis: maintainer update: audio/kid3
Responsible-Changed-From-To: freebsd-ports-freebsd-ports-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Mon Nov 6 19:49:36 UTC 2006
Responsible-Changed-Why:
Canonicalize assignment.
http://www.freebsd.org/cgi/query-pr.cgi?pr=105220
On Tue, Nov 28, 2006 at 11:52:49AM -0800, Jeremy Chadwick wrote:
Something like this should do just fine:
.if ${OSVERSION} 504000
BROKEN= Requires FreeBSD 5.4 or later, for llrint(3)
.endif
s/BROKEN/IGNORE/. BROKEN=doesn't currently work. IGNORE=known not to
work now, nor
On Sat, Dec 02, 2006 at 05:47:58PM -0500, John Abrams wrote:
I'm trying to make index on a FreeBSD 4.11-STABLE box, and for some time
I keep getting this error (I have cvsupped several times):
You are seeing a side-effect from most of the ports maintainers and
committers having moved to 6.X,
On Mon, Dec 11, 2006 at 01:23:54PM -0500, Vivek Khera wrote:
Reading this PR more closely it seems I was not even notified, as
Oleg Gawriloff [EMAIL PROTECTED] is described as the maintainer
and is the one responding to maintainer queries, which he is not.
What isn't detected well is if
But you're right, this is not the way that it is supposed to work. Please
accept my apologies, and we'll look at the code.
Well, this looks to have been a combination of two human errors (on that
particular PR), which the code really doesn't know how to deal with. But
after looking at it, I'm
I'll echo pav here. For people that don't want to answer questions or deal
with reminder-email from portmgr, the best thing to do is turn the port over
to [EMAIL PROTECTED] and just submit PRs for updates.
That's the difference, in my view, between being a 'submitter' and being a
'maintainer'.
There seems to have been a temporary problem with the email system
either involving spasassassin or NFS. The message is queued and I
will rescue it tomorrow; I am simply too tired tonight.
I will note, again, that these problems should always be forwarded to
bugmeister@ rather than the public
On Mon, Jan 08, 2007 at 02:28:54AM +0200, Cristian KLEIN wrote:
I have contacted this e-mail address as this is what make maintainer
gave me for dns/djbdns.
[EMAIL PROTECTED] is the address that unmaintained ports are assigned
to, so you may or may not get a response.
If you wish, you can file
On Wed, Jan 31, 2007 at 05:19:33PM +0100, Michel Talon wrote:
In my experience the Debian system is far more reliable than the
FreeBSD one, but such reliability will never be accessible to FreeBSD
as long as *all* ports are not available as packages.
I have also been working on the 'packages
201 - 300 of 545 matches
Mail list logo
