Torfinn Ingolfsen gmail.com> writes:
>
> Hello,
> I am updating the amule2 port to version 2.2.3, this is the first try.
> The patch is attached.
> There is (at least) one problem with the patch: it doesn't remove the
> file ./files/patch-amuleDlg.cpp. For now, just remove the file
> manually.
>
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
Hi,
On Mon, Dec 29, 2008 at 4:08 AM, Sevan / Venture37 wrote:
> matt donovan wrote:
>>
>> does your normal buildworld bomb out? I tend to do a make buildworld
>> outside of freesbie then just put NO_BUILDWORLD in my freesbie.conf.
>
> I don't have any problems running make buildworld when doing s
* Torfinn Ingolfsen (tin...@gmail.com) wrote:
> Ok, I have passed the first milestone or two - the aMule 2.2.3 port
> now compiles and installs.
> During the install step I see this:
> if test "amule" = "gettext" \
> && test '' = 'intl-compat.o'; then \
> /bin/sh `case "./mkinstal
* Torfinn Ingolfsen (tin...@gmail.com) wrote:
> Another question: how do I create a diff that removes one of the files
> in amule2/files?
> I tried
> diff -u amule2.org/files/patch-amuleDlg.cpp /dev/null >> amule2.diff
>
> And the diff looks ok:
> --- amule2.org/files/patch-amuleDlg.cpp 2006-01-0
Hello,
On Tue, Dec 30, 2008 at 11:20 AM, Bernhard Froehlich wrote:
> Looks like you are in the wrong folder. Patches are relative to the WRKSRC
> directory. (work/aMule-2.2.3 or something like that) So recreate the patch
> from
> within that directory and it should work.
I'm not really sure wha
On Dec 30, 2008, at 5:36, "Dominique Goncalves" > wrote:
Hi,
On Mon, Dec 29, 2008 at 4:08 AM, Sevan / Venture37 > wrote:
matt donovan wrote:
does your normal buildworld bomb out? I tend to do a make buildworld
outside of freesbie then just put NO_BUILDWORLD in my freesbie.conf.
I don't hav
Diego Depaoli píše v po 29. 12. 2008 v 20:49 +0100:
> On Mon, Dec 29, 2008 at 8:18 PM, Max Brazhnikov wrote:
> > On Mon, 29 Dec 2008 11:47:49 -0500, stan wrote:
> >> I'm building a new machine which I cvsup'd yesterday. I am having trouble
> >> getting the amarok port to compile. here is the end o
Hello,
On Tue, Dec 30, 2008 at 6:55 PM, Dmitry Marakasov wrote:
> But I assume what you need is -r option for diff - it compares 2
> directories recursively, processing all changes as well as new and
> removed files correctly.
I actually tried with the -r option to diff after sending mail to thi
* Torfinn Ingolfsen (tin...@gmail.com) wrote:
Something tells me that he meant to answer your previous message
about a patch that removes a file. I thought you're trying to make a
patch-* for ports's files/ too, before I understood that you're trying to
make a patch to a port itself.
This patch l
* Torfinn Ingolfsen (tin...@gmail.com) wrote:
> It stills says "hunk failed" but now it removes the empty file.
> So this is good then?
The patch you attached applies without any problems. `patch -E`:
--
|diff -ruN amule2.org/files/patch-amuleDlg.cpp amule2/files/patch-am
On Tue, December 30, 2008 7:04 pm, Torfinn Ingolfsen wrote:
> Hello,
>
> On Tue, Dec 30, 2008 at 11:20 AM, Bernhard Froehlich
> wrote:
>> Looks like you are in the wrong folder. Patches are relative to the
>> WRKSRC
>> directory. (work/aMule-2.2.3 or something like that) So recreate the
>> patch f
On Tue, Dec 30, 2008 at 7:33 PM, Dmitry Marakasov wrote:
> Something tells me that he meant to answer your previous message
> about a patch that removes a file. I thought you're trying to make a
> patch-* for ports's files/ too, before I understood that you're trying to
> make a patch to a port it
* Torfinn Ingolfsen (tin...@gmail.com) wrote:
> > This patch looks good at a first glance, I've scheduled it to be build
> > in a tinderbox.
>
> Which reminds me I have to fix my own tinderbox, after the last update
> it doesn't run anymore. Probably just ome config files that mut be
> changed.
>
On Tue, Dec 30, 2008 at 7:39 PM, Dmitry Marakasov wrote:
> The patch you attached applies without any problems. `patch -E`:
Nice!
> ensure that you're testing it on really original amule2 port (I guess
> that you're not, considering (offset 1 line) messages in the first
> chunk).
You were corre
* Torfinn Ingolfsen (tin...@gmail.com) wrote:
It builds OK, but plist (and Makefile.man I guess) is incorrect.
http://people.freebsd.org/~amdmi3/aMule-nooptimize-2.2.3.log
don't mind -nooptimize, I'm just testing it with different options.
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 95
On Tue, Dec 30, 2008 at 8:24 PM, Dmitry Marakasov wrote:
> * Torfinn Ingolfsen (tin...@gmail.com) wrote:
>
> It builds OK, but plist (and Makefile.man I guess) is incorrect.
I knew about plist - I haven't done too much updating of that. I need
to figure out a manageable way of maintaining it. Som
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
q...@freebsd.org wrote:
> Hi,
>
>
> The build which triggered this email is done under tinderbox-2.4.3, on
> 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
> and ccache support, with the "official" up-to-date Ports Tree, with the
> following vars set:
> NOPORTDOCS=yes, NO
Hi All,
*** Please note, the reply-to header is set to myself rather then the list.
I'm in the process of deprecating / removing devel/apr-svn in favor of
devel/apr now that 5.x is no longer supported. In addition to making things
simpler, this should fix at least a couple PRs in the
* Chess Griffin (ch...@chessgriffin.com) wrote:
> It looks like my new pkg-plist was not included in the commit. It is in
> my PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=130062
My bad, fixed.
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common probl
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
27 matches
Mail list logo
