Hi,
I can't upload source file for the upgrade of port slrn devel.
Here's the ticket with the portfile patch
https://svn.macosforge.org/projects/macports/ticket/13357
Sources are ~1Mb and maximum attachment size is < 300K. If someone wants
to commit this, can he please drop me a mail so I'll send
On 18/11/07 02:57, Ryan Schmidt wrote:
> Here are the maintainers who my script currently thinks need to fix their
> ports (I'm not sending them an email just yet):
> [EMAIL PROTECTED] (1)
Sorry, here's the patch for the abook port
https://svn.macosforge.org/projects/macports/ticket/13338
Gufo
Hi,
here's the ticket with the diff for the postfix portfile.
https://svn.macosforge.org/projects/macports/ticket/13196
Please apply, thanks.
Gufo
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinf
On 06/11/07 15:28, Weissmann Markus wrote:
> would it be possible to supply a diff? The attached files has practically
> nothing in common with the Portfile in trunk:
> $ slrn-devel> diff -u Portfile slrn-devel.portfile | wc -l
> 92
> $ slrn-devel> wc -l *
> 50 Portfile
> 43 slrn
On 06/11/07 15:28, Weissmann Markus wrote:
> Hi,
>
> would it be possible to supply a diff? The attached files has practically
> nothing in common with the Portfile in trunk:
> $ slrn-devel> diff -u Portfile slrn-devel.portfile | wc -l
> 92
> $ slrn-devel> wc -l *
> 50 Portfile
>
Hi,
I tried to file this on trac, but after pushing "preview and submit
changes" the connection hangs and the ticket fails to be uploaded.
I'm the maintainer of the slrn-devel package but I don't have the commit bit.
Can
someone please upgrade this for me?
I'm not also used to upload sources tar
Hi,
I wrote a portfile for slrn pre0.9.9-30, which is the latest develpment
release of slrn. The sources tarball used is taken from a checkout of
the snv server.
I don't have the commit bit on the macports svn, and I don't know which
is the right way of dealing with this sort of things.
If a develo
On 11/08/07 16:58, N_Ox wrote:
>> []
>> ---> Verifying checksum(s) for slrn-devel
>> DEBUG: Executing org.macports.checksum (slrn-devel)
>> ---> Extracting slrn-devel
>> DEBUG: Executing org.macports.extract (slrn-devel)
>> DEBUG: Executing org.macports.patch (slrn-devel)
>> ---> Configuring
On 10/08/07 20:17, Ryan Schmidt wrote:
> Why are you adding such a variant? Under which circumstances might a user
> want, or not want, to select it? I'm trying to figure out why you don't just
> fetch from CVS all the time, as that would seem to simplify things, wouldn't
> it? Variants are not
Hi,
I'm trying to add a cvs variant to the slrn-devel portfile.
As now i can fetch the sources with this:
variant cvs {
fetch.type cvs
cvs.root:pserver:[EMAIL PROTECTED]:/cvsroot/slrn
cvs.module slrn
cvs.password
cvs.date20070717
Hi,
This is a ticket for a the aircrack-ng port
http://trac.macports.org/projects/macports/ticket/12181
No driver is available to capture and inject packets under osx, but the
cracking library should work as on linux and other systems.
Can someone please review and commit it?
Thanks,
Gufo
__
On 23/06/07 09:36, Ryan Schmidt wrote:
> Ok. I just tried installing the slang port (1.4.9_0) and it worked for me,
> on Intel Core 2 Duo. The slang2 port (2.1.0_0) worked, too.
Ok
> This leads me to continue to suspect a rogue readline library somewhere on
> your system. First, is your MacPort
rror 1
>> make: *** [static] Error 2
>
> _SLrline_* seem to be readline functionality. Do you have a non-MacPorts
> readline installation in /usr/local/lib perhaps?
No, all programs are installed through macports.
[sbranzo] gufo ~ $ l /usr/local/
total 0
drwxr-xr-x 4 root wheel 136 2007-01-12
Can someone confirm that the slang2 port works?
I get this error upgrading slang2 from 2.0.4_0 to 2.1.0_0 on os x
10.4.10 and 10.4.9 ppc.
---> Building slang2 with target all
Error: Target com.apple.build returned: shell command " cd
"/opt/local/var/db/dports/build/_opt_local_var_db_dports_source
On 02/05/07 23:21, Olaf Foellinger wrote:
> Here is
>
> $ which md5
> /sbin/md5
>
> Is /sbin in your path? Are you on Mac OS X? Which version? Is there
> another md5 tool in your path?
[sbranzo] root ~ # /opt/local/bin/port upgrade mutt-devel
---> Fetching mutt-devel
Maybe someone could help me with mutt-devel.
After forcing portindex update I was trying to port upgrade mutt-devel
but:
sudo port upgrade outdated
Password:
---> Building mutt-devel with target all
Error: Target com.apple.build returned: shell command " cd
"/opt/local/var/db/dports/build/_opt_lo
On 29/04/07 22:02, Ryan Schmidt wrote:
> >Can someone confirm this bug?
>
> I think the correct syntax is:
>
> $ port info --maintainer mutt
> maintainer: [EMAIL PROTECTED]
You're right. Sorry for the false allarm.
Thanks,
Gufo
___
macports-dev mailin
Hi,
I dont' know if my installation is broken, because I'm facing a new
problem. Macports is updated at today (version 1.430).
I was trying to spot the mutt-devel maintainer, because 1.5.15 is out,
using port maintanier but:
[sbranzo] gufo ~ $ port maintainers mutt-devel
Unrecogni
On 27/04/07 08:17, Boey Maun Suang wrote:
> The only thing that comes to my mind is that port outdated won't pick
> up that there's a new version of a port available until PortIndex is
> updated, and that happens every twelve hours on the MacPorts rsync
> repository. In between such index up
Hi,
I'm running macports 1.4.3, which seems to be confused by programs with
"unusual" versions.
For example tor, on my system was version 0.1.1.26, and port outdated
never noticed version 0.1.2.13 was available.
Bye,
Gufo
___
macports-dev mailing list
ma
On 18/03/07 13:55, Sbranzo wrote:
> A new version of mutt-devel is available:
> http://trac.macports.org/projects/macports/ticket/11553
>
> I received no response so far from the maintainer, can someone commit
> the (trivial) patch?
On 20/03/07 17:24, Elias Pipping wrote:
> I've submitted your patch in r22957.
>
> http://trac.macports.org/projects/macports/changeset/22957
>
> I've made some additional changes, too. These are:
>
> * declare dependency on gettext, libiconv
> * make sure gettext, libiconv, ncurses, readl
Hi all,
abook port is outdated and without maintainer. I'd like to take over the
maintainership if possible and to update it to 0.5.6 (now 0.5.3).
A couple days ago I filed a new ticket
http://trac.macports.org/projects/macports/ticket/11579 with a patch to
correct dependencies, bump version and se
On 18/03/07 19:13, Ryan Schmidt wrote:
> Had you already sent an email to the maintainer? If you only
> submitted the ticket, the maintainer may not have seen it yet; Trac
> does not send email unless you list the address in the CC field,
> which I have now done.
Yes, I forgot to mention I a
A new version of mutt-devel is available:
http://trac.macports.org/projects/macports/ticket/11553
I received no response so far from the maintainer, can someone commit
the (trivial) patch?
Bye,
Gufo
___
macports-dev mailing list
macports-dev@lists.maco
On 17/02/07 21:32, Juan Manuel Palacios wrote:
> Committed in r22124, thanks for the contribution! Notes of interest:
>
> 2) Number of files should be kept to a minimum, so a patch like that is
> unnecessary as users using the port are already using MacPorts, no need
> to instruct them to type p
Just a head-up for a new port submitted a while ago:
http://trac.macports.org/projects/macports/ticket/11299
Gufo
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-dev
On 23/01/07 18:19, Mark Duling wrote:
> phase. I think it is ugly but I don't know of a better way. Does anyone
> else? I attached your patch to to
> http://trac.macports.org/projects/macports/ticket/10679. I want to see if
> anyone has a better idea and if you want to try to deal with the .tur
On 22/01/07 06:09, Randall Wood wrote:
> rhwood$ sudo port upgrade outdated
> ---> Deactivating bzip2 1.0.3_0
> ---> Fetching bzip2
> ---> Attempting to fetch bzip2-1.0.4.tar.gz from http://www.bzip.org/
> 1.0.4/
> ---> Verifying checksum(s) for bzip2
> ---> Extracting bzip2
> ---> Applying
On 21/01/07 12:02, Daniel J. Luke wrote:
> It finds an appropriate tar when you install it.
>
> I would move aside fink (or at least remove it from your path) and
> reinstall macports from source.
It worked flawlessy. Thanks a lot.
Gufo
___
macports-
I used to have fink installed, because I needed a working postfix. Now
postfix is ok under macports so I want to remove fink.
If I move /sw to /sw-old, for example, here's what I have If I try to
install some new program in macports:
sudo port -vc install unix2dos
[...]
---> Extracting unix2dos-2
Hi,
I'm trying to write a new slrn-dev port using the same cvs snapshot used
in debian-unstable.
To do this I think I need to execute some commands between the
various phases of the automated process:
1) The name of the sources tarball is
slrn_0.9.8.1pl2~cvs20061116.orig.tar.gz, but the enclosed
32 matches
Mail list logo
