On Sat, Feb 28, 2009 at 08:02:14PM -0600, Mark Linimon wrote:
> With 8.0 coming up, it's time to take a look at the ports that have
> been broken by some recent changes to freebsd-current. I have put
> a list of these ports, categorized by which change, on the wiki at
> http://wiki.freebsd.org/Por
On Mon, Mar 02, 2009 at 06:20:33PM -0500, Michael Proto wrote:
> What about non-ports breakage, ie- /bin/sh read builtin failing after
> the tty changes :)
You can see a list of all the PRs with regressions (not just -current) at
http://people.freebsd.org/~linimon/studies/prs/prs_for_tag_regressio
On Mon, Mar 02, 2009 at 08:53:53AM +0100, Hans Petter Selasky wrote:
> I added this one:
>
> /usr/ports/graphics/sane-backends
>
> To whom can we commit patches to fix the broken issues?
Since it's unmaintained (maintainer=po...@freebsd.org), just send-pr
with the patches.
mcl
_
k Linimon -
>
> From: Mark Linimon
> To: po...@freebsd.org
> Subject: [headsup] call for assistance with ports broken on -current
>
> With 8.0 coming up, it's time to take a look at the ports that have
> been broken by some recent changes to freebsd-current. I have put
On Mon, Mar 02, 2009 at 04:52:28PM +0100, Lars Engels wrote:
> On Sun, Mar 01, 2009 at 06:45:39PM -0600, Mark Linimon wrote:
> > FYI, here's what I posted to ports@ yesterday. Any help fixing these
> > would be appreciated. (We've already knocked off several of the ones
> > I initially posted.)
>
On Sun, Mar 01, 2009 at 06:45:39PM -0600, Mark Linimon wrote:
> FYI, here's what I posted to ports@ yesterday. Any help fixing these
> would be appreciated. (We've already knocked off several of the ones
> I initially posted.)
>
> mcl
Does someone have problems building net/libdnet? It is list
* Mark Linimon wrote:
> These changes are: tty changes, jail changes, import of strndup(3),
^^^
> ARP v2, libusb20, and possibly VFS. (libusb20 has not yet been run
> through pointyhat, and its list is probably incomplete.)
Working on it.
--
Ed Schouten
WWW: htt
On Mon, 2009-03-02 at 08:53 +0100, Hans Petter Selasky wrote:
> On Monday 02 March 2009, Mark Linimon wrote:
> > http://wiki.freebsd.org/PortsBrokenOnCurrent
>
> I added this one:
>
> /usr/ports/graphics/sane-backends
>
> To whom can we commit patches to fix the broken issues?
Best thing to do
2009/3/2 Eygene Ryabinkin :
> Florent, good day.
>
> Mon, Mar 02, 2009 at 11:03:38AM +, Florent Thoumie wrote:
>> On Mon, Mar 2, 2009 at 9:34 AM, Eygene Ryabinkin
>> wrote:
>> > Could you or someone else add ports/129881 as the ARPv2 changes
>> > resolution fix for the ospfd? I am not eligib
Florent, good day.
Mon, Mar 02, 2009 at 11:03:38AM +, Florent Thoumie wrote:
> On Mon, Mar 2, 2009 at 9:34 AM, Eygene Ryabinkin wrote:
> > Could you or someone else add ports/129881 as the ARPv2 changes
> > resolution fix for the ospfd? I am not eligible to edit the wiki
> > pages, so can't
On Mon, Mar 2, 2009 at 9:34 AM, Eygene Ryabinkin wrote:
> Mark, good day.
>
> Sun, Mar 01, 2009 at 06:45:39PM -0600, Mark Linimon wrote:
>> With 8.0 coming up, it's time to take a look at the ports that have
>> been broken by some recent changes to freebsd-current. I have put
>> a list of these p
Mark, good day.
Sun, Mar 01, 2009 at 06:45:39PM -0600, Mark Linimon wrote:
> With 8.0 coming up, it's time to take a look at the ports that have
> been broken by some recent changes to freebsd-current. I have put
> a list of these ports, categorized by which change, on the wiki at
> http://wiki.f
On Monday 02 March 2009, Mark Linimon wrote:
> http://wiki.freebsd.org/PortsBrokenOnCurrent
I added this one:
/usr/ports/graphics/sane-backends
To whom can we commit patches to fix the broken issues?
--HPS
___
freebsd-ports@freebsd.org mailing list
h
Mark Linimon wrote:
> With 8.0 coming up, it's time to take a look at the ports that have
> been broken by some recent changes to freebsd-current. I have put
> a list of these ports, categorized by which change, on the wiki at
> http://wiki.freebsd.org/PortsBrokenOnCurrent.
>
> These changes ar
With 8.0 coming up, it's time to take a look at the ports that have
been broken by some recent changes to freebsd-current. I have put
a list of these ports, categorized by which change, on the wiki at
http://wiki.freebsd.org/PortsBrokenOnCurrent.
These changes are: tty changes, jail changes, impo
15 matches
Mail list logo