perlbug (and parrotbug) upgrade
Finally, the moment you've all been waiting for is here! perlbug (http://rt.perl.org/rt3/) has been upgraded to the latest and greatest version (RT 3.6). Here are some changes you might notice: - a new shiny look - no more auth.perl.org, we now authenticate directly from bitcard.org - a public interface that doesn't require you to log in to see tickets - a much more powerful search interface - things that were slow before, are not quite so slow anymore - saved searches Likely, you'll discover some things are broken, or don't work the way they used to. Here's a few we know about: - Old bookmarked searches can't be used anymore. (Sorry!) - Some bitcard accounts (with accented characters in their names) can't login. - we have a mild performance issue related to CSS caching. If you run into issues, big or small, please send an email to perlbug-admin at perl.org. Your message will be answered in the order recieved. -R (special thanks to Jesse Vincent, Kevin Riggle, Thomas Sibley, and all the rest of the gang at Best Practical, for their help, patience, and for the rt.cpan.org customizations, which made this much easier than it might have been)
Re: languages/ Cleanup
I was going to suggest keeping an archive of this one outside the repository, but it's only 2 files, so I'll just keep a copy for myself. (I'd like to revive it at some point in PGE/TGE and the old implementation could be useful.) Nothing is actually _deleted_ from SVN... it just gets harder to find. So it'll be there later if you want it. -R
Re: libparrot.so.0.4.2
(If so, as a bit of background it's discussed at the bottom of #38217 on RT, and I tried to put together a patch in r11320 but I caused some breakage so it's been backed out. I need to revive it) Thank you, Nick. How do I get a username and password for RT? http://auth.perl.org/ or just use guest/guest. -R
Re: [perl x38598] [TODO] PIR Examples, Libraries, and Tests - Migrate to New Subroutine Attributes
Applied in 11755, 11756, and 11758. (Ticket not closed; I don't have permission.) You shouldn't say things like that. You have permission now. -R (pulling an Audrey.)
Re: Subversion Server Downtime
Upgrade complete. You shouldn't notice anything different, except some operations might be faster. -R At Tue, 21 Feb 2006 22:25:22 -0800, Robert Spier wrote: FYI - At some point later this week, or maybe this weekend, I will be taking the perl.org Subversion server down to move it to different hardware. This most likely won't happen until after the imminent Parrot release. From an end user perspective, nothing should change. (Although we are upgrading to a newer version of the server and associated programs.) The server will be there, and then it will be down for a few hours... and then it'll be back, bright, shiny and happy. More details once it is complete. -R (http:/log.perl.org)
Subversion Server Downtime
FYI - At some point later this week, or maybe this weekend, I will be taking the perl.org Subversion server down to move it to different hardware. This most likely won't happen until after the imminent Parrot release. From an end user perspective, nothing should change. (Although we are upgrading to a newer version of the server and associated programs.) The server will be there, and then it will be down for a few hours... and then it'll be back, bright, shiny and happy. More details once it is complete. -R (http:/log.perl.org)
svn performance
snapshots or releases. And, since a checkout takes about an hour (last time I checked) I tend to be too lazy to fetch one just to make a patch. Only if you're checking out to a Commodore 64. [EMAIL PROTECTED] /tmp$ time svn co http://svn.perl.org/parrot/trunk parrot-trunk /dev/null real1m4.827s user0m4.108s sys 0m2.852s (I did several other runs, using ssl, and it took less time, probably due to compression. I even did a checkout from 70ms of latency away from the server, and it was less as well.)
Re: svn performance
Sigh. I wish it were that simple, or that funny. $ time wget http://cvs.perl.org/snapshots/parrot/parrot-latest.tar.gz real0m16.84s user0m0.09s sys 0m0.20s $ time svn co http://svn.perl.org/parrot/trunk parrot-trunk real 2:01:50.3 user 1:02.0 sys44.9 It's something specific to svn. No, I don't know what. What version of subversion are you using? -R
Re: Svn Commit list...
... seems to be dead for about a day now, though I know commits are going through. Fixed. BCCing webmaster at perl dot org, where this will hopefully open a ticket. THANK YOU. This meant the message got seen much earlier than it otherwise would, and because of the BCC, no collateral damage. -R
blocked mime types
No, it isn't. =) The mail list strips out .t attachments (Robert? is this necessary?) We don't strip .t We strip troff attachments. Really, it's a bad mailer that is labeling the .t file a troff mime-type. I've removed the troff types from the bad mime list. -R
Re: merge release
We've actually done a merge. It is complete. All committed changes on the leo-ctx5 branch are now on trunk as of rev 9260. The leo-ctx5 branch was deleted as rev 9261. If you have any checkouts of the leo-ctx5 branch, you will need to switch them to trunk cd parrot-checkout-of-leo-ctx5-branch svn switch https://svn.perl.org/parrot/trunk/ -R
Re: Website still refers to 0.2.0 as latest version
Updated. (Sorry for the delay.) -R At Fri, 10 Jun 2005 20:18:38 +0100, Roger Browne wrote: By the way, the website http://www.parrotcode.org/ still refers to 0.2.0 as the latest version. Regards, Roger Browne
Re: [PATCH] More t/p6rules tests
The list server keeps eating my attached homework. Won't let me attach a .t file. This is because your mailer is declaring it to be an application/x-troff file.
Re: parrotcode.org needs some updating
Leopold Toetsch wrote: http://www.parrotcode.org/resources.html still has CVS and CVS instructions mentioned. Please replace it with equivalent SVN hints. ... which are at http://www.parrotcode.org/source.html Updated. As always, patches for this kind of thing are welcome. (You can patch against https://svn.perl.org/perl.org/docs/live/parrotcode/) -R
Re: Favicon.ico for http://www.parrotcode.org
I noticed that the favicon.ico for http://www.parrotcode.org is a Camel. Can we have a Parrot for that, in order to do the many non-Perl Parrot based languages justice? Good idea. I've put one in place. If someone wants to make a nicer one, I won't kick and scream too much. -R
Re: Takers wanted - a perl job
Robert Spier wrote: Doesn't work when svk is used to check out the copy. But in that case svk list -R does. Hmm. Maybe this should be a commit action and not a test. It was under CVS. I'm pretty sure everyone ignored it there :) Well, it always depends, how responds looks like: Committed revision 1234 * ATT MAINFEST ERROR missing bla.bla ... * That is a little harder to miss. :) In CVS, it was just.. manicheck: Not in MANIFEST: $file manicheck: No such file: $file (Anyway, as said before - if someone writes the script - we'll run it.) -R
Re: rsync has .svn directories?
The rsync off of cvs.perl.org::parrot-HEAD as suggested on parrotcode.org contains .svn directories. This doesn't seem right. Fixed.
forced manifest check
Well, it always depends, how responds looks like: Committed revision 1234 * ATT MAINFEST ERROR missing bla.bla ... * This is very similar to what it did under CVS, although maybe not quite as big. Anyway, if this is something the community wants, if someone could implement a first pass at the hook script, we can run it. It'll need to use svnlook cat to look at the Manifest, svnlook changed to detect new files or removed files, and then compare. Actual details are up to the implementer. Many thanks to Garrett Goebel who created our CVS implementation. -R
Re: Welcome to the land of Subversion
At Wed, 13 Apr 2005 02:07:05 -0400, Roger Hale wrote: Robert Spier wrote: Could that be added as 4th line? Good ideas, all of them. I've updated the page to add that, and to switch to bz2. -R Following Nicholas Clark: bzcat svk-mirror-dump.bz2 | svnadmin load --ignore-uuid ~/.svk/parrot presumably should be bzcat svk-bootstrap-dump.bz2 | svnadmin load --ignore-uuid ~/.svk/parrot (Although parrotcode.org is denying all knowledge of the file presently...) Thanks Roger... I really shouldn't update the website while watching TV. Distraction and all. Fixed and fixed. -R
Re: Takers wanted - a perl job
Doesn't work when svk is used to check out the copy. But in that case svk list -R does. Hmm. Maybe this should be a commit action and not a test. It was under CVS. I'm pretty sure everyone ignored it there :) -R
Re: Welcome to the land of Subversion
Could that be added as 4th line? Good ideas, all of them. I've updated the page to add that, and to switch to bz2. -R
Re: [svn:parrot] rev 7800 - trunk/t/perl
Fixed hopefully. $ find -name '*.t' | xargs svn ps svn:mime-type text/plain $ svn ci ... Yes, that'll fix it. Probably worth checking the mime-types for all the other files. and that dam.. check in runs for more then 10 minutes now Ick. The network pipe is a little congested today, and some cron jobs may have been running that were slowing the box. But - it was also a big commit. We've got another box that we'll move SVN to in a few weeks. Is there a way to specify the mime-type on a filetype basis? Would be good for new files. This is all client-side. -R
Re: CVS going away
I've disabled all CVS write permissions as part of the transition. (Yes, this means wheels are turning.) CVS will stay readable, but un-writable until tomorrow morning, when I hope to announce SVN being up. The import is running while I sleep. I caught I minor issue halfway into the previous import - but since there's only once chance to get this right - I started over. -R
Re: Welcome to the land of Subversion
The conversion is done. http://www.parrotcode.org/source.html Have fun! Sweet! Is there any particular reason why everyone should use https? Shouldn't http do for non-committers? Or am I nitpicking here? Not really. http is fine for non-committers. But it was easier to just document one of em. Other things worth sharing: - commit messages aren't moving right now. They are being sent, they're just sitting in the moderation queue. They'll start moving again soon. - http://svn.perl.org/rss/log/parrot.rss
CVS going away
I've disabled all CVS write permissions as part of the transition. (Yes, this means wheels are turning.)
Re: Monthly Release Schedule
It was on parrotcode or dev.perl.org at some point. Maybe that can be reused? Our tinderbox.perl.org volunteer is working on it. We've been nudging him, and he's got some cool stuff going on.
Subversion in the wings
Due to popular demand, among many other reasons, parrot will be switching to Subversion at some point in the next few days. I've placed a test conversion at https://svn.perl.org/parrot-test/ (It mirrors the state of the CVS repository as of this morning.) Please take a look at it, and make sure that everything looks ok, nothing important is missing, etc. If I don't hear anything by this weekend, I'll do the conversion. Actual downtime will be a few hours for the conversion and import. I'll send a note when I disable the CVS repository, and then another when it's all available in SVN. The final location will be https://svn.perl.org/parrot/. If you're currently using the CVS tracking repository that lives there, it won't anymore. (Because there won't be any CVS to track anymore.) For the next few days, you will want to not keep too many un-checked in changes around, because you'll have no fun once the CVS goes away. Any questions? -R
Re: Subversion in the wings
Any questions? I assume current committer bits will be transitioned over too? Actually, this would be a great time to get signed committer agreements from everyone. But, since that probably isn't going to happen, I'll just move over all the bits. -R
OSCON Call For Proposals Now Open
From: O'Reilly Conferences [EMAIL PROTECTED] Subject: OSCON Call For Proposals Now Open Date: Thu, 20 Jan 2005 11:30:03 -0800 The Call for Proposals has just opened for the 7th Annual O'Reilly Open Source Convention http://conferences.oreillynet.com/os2005/ OSCON is headed back to friendly, economical Portland, Oregon during the week of August 1-5, 2005. If you've ever wanted to join the OSCON speaker firmament, now's your chance to submit a proposal (or two) by February 13, 2005. Complete details are available on the OSCON web site, but we're particularly interested in exploring how software development is moving to another level, and how developers and businesses are adjusting to new business models and architectures. We're looking for sessions, tutorials, and workshops proposals that appeal to developers, systems and network administrators, and their managers in the following areas: - All aspects of building applications, services, and systems that use the new capabilities of the open source platform - Burning issues for Java, Mozilla, web apps, and beyond - The commoditization of software: who and/or what can show us the money? - Network-enabled collaboration - Software customizability, including software as a service - Law, licensing, politics, and how best to navigate other troubled waters Specific topics and tracks at OSCON 2005 include: Linux and other open source operating systems, Java, PHP, Python, Perl, Databases (including MySQL and PostgreSQL), Apache, XML, Applications, Ruby, and Security. Attendees have a wide range of experience, so be sure to target a particular level of experience: beginner, intermediate, advanced. Talks and tutorials should be technical; strictly no marketing presentations. Session presentations are 45 or 90 minutes long, and tutorials are either a half-day (3 hours) or a full day (6 hours). Feel free to spread the word about the Call for Proposals to your friends, family, colleagues, and compatriots. We want everyone to submit, from American women hacking artificial life into the Linux kernel to Belgian men building a better mousetrap from PHP and recycled military hardware. We mean everyone! Even if you don't want to participate as a speaker, send us your suggestions--topics you'd like to see covered, groups we should bring into the OSCON fold, extra-curricular activities we should organize--to [EMAIL PROTECTED] . This year, we're moving to the wide open spaces of the Oregon Convention Center. We've arranged for the nearby Doubletree Hotel to be our headquarters hotel--it's a short, free Max light rail ride (or a lovely walk) from the Convention Center. Registration opens in April 2005; hotel information will be available shortly. Deadline to submit a proposal is Midnight (PST), February 13. For all the conference details, go to: http://conferences.oreillynet.com/os2005/ Press coverage, blogs, photos, and news from the 2004 O'Reilly Open Source Convention can be found at: http://www.oreillynet.com/oscon2004/ Would your company like to make a big impression on the open source community? If so, consider exhibiting or becoming a sponsor. Contact Andrew Calvo at (707) 827-7176, or [EMAIL PROTECTED] for more info. See you Portland next summer, The O'Reilly OSCON Team
Re: CIA
Parrot is now listed on CIA (insert-at-point (spook)) Ooo. spook's phrasebook is strictly US-ASCII. That's totally CIA-compatible, isn't it? Probably. But they're still after those computer criminals. And folks who use laser pointers. -R
Re: svn
While I personally like the idea, I think it is unlikely given how much slower svn is on sizable repositories. Of course I have not tried it recently, so maybe that has changed... All that being said, I am in absolutely no position of authority about this... This is, and always has been, (since 1.0 at least), a myth. We have always been at war with Apache has moved most of their projects to SVN. It's probably ready. -R
Re: RT Ticket Summary
I'd like to see: ... http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Re: Streams and Filters (Ticket #31921)
(In my opinion, the line-ending issue isn't a problem for Parrot in terms of this test--it's legitimate to expect that you can process a particular file, not matter what platform you happen to be on, and no matter if the file happens to have been created on another platform.) Also, the proper way to set binary on a cvs file is to set -kb on it. -R
libjit
Is there anything that can be learned/reused from libjit? http://www.southern-storm.com.au/libjit.html -R
Re: [perl #32118] AutoReply: [PATCH] Update of documentation
- do not change viewcvs in glossary.doc to cvsweb, just correct the link Please _do_ change all references to cvsweb to viewcvs. Unless there is a compelling reason, we will continue to phase out use of cvsweb. viewcvs is faster, cleaner, and has more features. -R
Re: [perl #32118] [PATCH] Update of documentation
Maybe there are some good links to Tinderbox or Bonsai or ViewCVS or they are only temporarily down, I don't know, but having non-functional references in documentation is not very good. Tinderbox is temporarily down. Either Zach needs to fix it, or I need to finish my replacement for it. Bonsai is something I don't think anyone ever used. I have a Bonsai replacement on deck, although the front-end doesn't seem to work so well. (Bonsai is basically a searchable database of all checkins.) If a Bonsai-type tool is important to anyone, something can be made to happen. ViewCVS is a fully supported system. If it's ever down, something is wrong. Note that some of these apply to http://www.parrotcode.org/resources.html too. Patches for this can be generated against: https://svn.perl.org/perl.org/docs/live/parrotcode/ (guest/guest) Please send them to webmaster at perl.org. -R
Re: parrot cvs mirrored with svk
This now lives at http://svn.perl.org/parrot/cvs/ (use guest/guest) http://svn.perl.org/viewcvs/parrot/cvs/trunk/ It is updated from CVS once an hour. Have fun! -R At Sat, 7 Aug 2004 09:52:30 +0100, Chia-liang Kao wrote: [1 text/plain; us-ascii (7bit)] Hi, I've just setup a Subversion mirror of the parrot cvs repository with svk. Will try to keep it in sync until Robert have time to do similar setup on perl.org. So you could now use the Subversion repository (readonly) at: svn://svn.clkao.org/parrot/cvs/trunk web interface at http://svn.clkao.org/svnweb/parrot/ and for people with unfortunate per-minute metered ISDN, svk could be used to mirror the above url, create local branch and do commits locally. Later on generate a diff to apply to cvs, or if the development trunk switches to svn it would be even eaiser. Hopefully this could eventually allow more time for fine white wine while retaining the same excellent productivity. Cheers, CLK [2 application/pgp-signature (7bit)]
Re: PATCH for parrotcode.org
At Tue, 10 Aug 2004 22:05:34 -0400, William Coleda wrote: [1 text/plain; us-ascii (7bit)] Attached find a patch to http://www.parrotcode.org/examples/index.html that: (0) depends on a patch I sent to the webmaster folks earlier adding back in the docs/* hierarchy (a small shim of .html files that just points to everything that ends up in parrot's docs directory after a build. - goes against cvs-latest) I just wanted to publicly thank Will for the patches. They've made http://www.parrotcode.org/docs/ usable again. -R
Re: [CVS] meta
CVS ci rights for Jarkko would be fine, Please send all requests like (and including) this one to cvs at perl.org. -R
Re: Aaargh. The return of platforms
There's a directory platforms reappeared in parrot's CVS at the top level This breaks checkouts on any case insensitive file system, because CVS already knows about the file PLATFORMS We need the repository edited to expunge the directory platforms, don't we? Either that or the file PLATFORMS must go. But I'm not sure how CVS would cope with the sequencing of this. Whoops. I moved the directory back today as part of some fun experimental conversion stuff. I've rm -rf'ed it this time, so it can't come back. -R
Yet another Math Library
This might be useful... (thanks planetlisp!) Chris Double Wed Jun 30 17:22:09 2004 http://radio.weblogs.com/0102385/2004/07/01.html#a625 I came across a free portable arbitary precision integer and rational arithmentic library called [1]IMath that looks useful. It is under a BSD style license and it looks like it might be useful for implementing bignum support in languages. It may be a useful alternative to [2]GNU MP if the latters licensing is not compatible with your project. References 1. http://thayer.dartmouth.edu/~sting/sw/imath 2. http://swox.com/gmp/
Re: Please become ID verified.
At Tue, 25 May 2004 10:36:24 -0400, Aaron Sherman wrote: On Mon, May 24, 2004 at 09:48:45PM -0400, Uri Guttman wrote: is there a paypal PMC in the plans? will it be multi-accounted? will it have built in auth support? what about rounding errors? In case it was not obvious, the Paypal message was a scam to get people's passwords. The offending host appears to be 81.196.122.75. This particular email leaked through because at some point in the past [EMAIL PROTECTED] had gotten subscribed to the list. I've cleaned it up. We're in the (slow) process of changing our list subscription process to make this impossible. -R
Re: Outstanding parrot issues?
ICU somehow manages (optionally?) to suffix all it its symbols with the version number, automagically (meaning, they don't look that way in the source or the headers). We should figure out how they are doing that, and see if we can use the same approach. I don't know if it's linker magic, or compiler magic, or magic magic. The Linux kernel does this as well with compier/header/preprocessor magic.
Re: [perl #28915] parrotbug can only send mail
Speaking about parrotbug, are the [EMAIL PROTECTED] addresses
created? What do they currently do?
parrotbug@ sends to the tracker
status-{ok,nok}@ currently end up in mailboxes that nobody reads
-R
Re: RT
clarification on some others - outgoing emails were being eaten by a grue for a while, but Robert says it's fixed now - I'll be sending out To clarify. Only explicit CC's to the list were broken. All other outbound mail was fine. -R
Re: Tinderbox aniani brocken
about to cvs checkout parrot: /home/perlcvs: no such repository Ah, that's finally gone away. The repository path is /cvs/publoc. What you're using's very old, though there was a temporary symlink in for a while. It's been gone for months and months. And you mean /cvs/public.
Re: web site down?
http://www.parrotcode.org/ is not responding to http or ping. Yes. We knew. All happy now. -R
Re: cvs update problem.
I can't replicate this. At Tue, 16 Mar 2004 19:55:22 -0500, Will Coleda wrote: bash-2.05a$ rm -f languages/tcl/lib/match_close.imc bash-2.05a$ cvs update languages/tcl/lib/match_close.imc cvs: rcs.c:4091: RCS_checkout: Assertion `options[0] == '-' options[1] == 'k'' failed. cvs [server aborted]: received abort signal
Re: [offtopic] Fwd: ScanMail Message: To Sender virus found or matched file blocking setting.
At Thu, 11 Mar 2004 19:00:18 +0100, Jens Rieks wrote: [1 text/plain; us-ascii (7bit)] Hi, Am I the only one who receives this annoying message each time I send an .tgz attachment to the list? You're the only one who has complained. I'll unsubscribe the offender. -R
Re: parrotbug working...
But what should those addresses do when receiving a message? - parrotbug: should open a RT ticket? Yes. This is the new equivalent of bugs-parrot at rt.perl.org. Use of that address should be phased out in favor of the new one. - status-ok: ? - status-nok: should open a RT ticket? Right now both of these email addresses get dumped into files. We need a new system (sigh) for processing these. It's a very simple perl and database thing. We'll want to use it for perl5 and parrot. (I wonder if we can just use CPAN testers for this? http://testers.cpan.org/show/parrot.html) Anyone (Robert? :-) ) knows what [EMAIL PROTECTED] do? A little too well. -R
Re: news gateway through google not working?
That depends if google properly supports moderated newsgroups. Sounds like they don't ... In any case we don't currently support posting via nntp through anything but nntp.perl.org. Actually, I think we need to get the uunet.uu.net folks to setup some entries for us. But I can't find a contact address. -R
Re: news gateway through google not working?
That depends if google properly supports moderated newsgroups. Without knowing what they're doing, it's hard to guess what's going on or where your message got eaten. Your message _shouldn't_ show up on google unless it comes through a proper newsfeed. This might mean that google's upstream (stanford) is screwy. -R At Tue, 9 Mar 2004 10:51:06 -0800, Edward S. Peschko wrote: ( ps - on a side note, is the news gateway through google working in posting to the list? I tried posting via google, and although it shows up on google, it didn't show up in the archives... )
Re: www.parrotcode.org/ points to 0.0.10
In a similar(?) vein, www.parrotcode.org/faq/ currently has a number of broken links, including apocalypses, PDD6, and Java bytecode to Parrot bytecode. This is because the links are funny. The best way to get proper links is to do something like: LThis is CNN|http://www.cnn.com That's not great.. but it tends to render better. Our official Pod renderer is Pod::Simple::HTML, so you can test it out. I'm throwing this back to p6i, so somebody can fix it, and maybe take another pass through the FAQ, addming more F.. A... Q...s ;) -R
Re: [DOCS] Documentation tools
I'd like to remove non-modified, non-parrot Perl modules from lib and install them via CPAN.pm. No. Sorry, definitely not. Parrot's config isn't going to install perl modules off the 'net any more than it's going to run apt-get on systems that support it. We either provide it or do without. Huh? Dan, what are you smoking? Every project has dependencies. For now, perl5 and a handful of modules are one of parrot's prereqs. That's quite reasonable. If someone can't install a few perl5 modules, they probably shouldn't be building parrot. There's no reason to include large, independently maintained modules like Pod::Simple in the parrot CVS tree and tarball. It just turns into a maintenance nightmare, should we ever start modifying these things. And while the parrot tree is relatively small right now - it won't always be. Might as well keep it small while we can. I don't understand why you are insisting on including these things. Please clarify. -R
Re: [DOCS] Documentation tools
No. Sorry, definitely not. Parrot's config isn't going to install perl modules off the 'net any more than it's going to run apt-get on systems that support it. We either provide it or do without. What about ICU. There is already a new version pending (again). Since we haven't actually used ICU yet, I see no reason to integrate the new version until we use the old one. And personally, I'd rather rip it out of the tree and say we're just going to link against the installed version -R
Re: Dates and Times
I agree. That's why I'd like to see TAI be the default seconds since some epoch. It seems like we want the default to be the simplest and fastest one we can support. If someone wants something different, they can do the moral equivalent of: use Time::TAI; or use Time::UTC; or use Time::MacEpoch; -R
Re: parrotbug working...
The mails are indeed sent to parrotbug, parrotstatus-ok and parrotstatus-nok (at parrotcode.org) for resp. bug reports, ok reports or nok reports. And since I don't think those addresses are set up... Not yet. I'm nudging Ask regularly about this. -R
Re: [DOCS] Documentation tools
The determinism seems perhaps worth the bloat. It's quite localize bloat after all. I disagree. We _want_ a heterogeneous environment -- a homogeneous environment doesn't exist in the real world -- most of your concerns were with tracking down the issues. Since we have parrotbug now (or real soon) we can take a better snapshot of whats going on. If we want to require certain versions, that becomes a problem ot some people. But we can do it by providing URL's to where people can download the specific versions and instructions on how to set that up for parrot's use only. But we don't need to bundle it _with_ Parrot. -R
Re: MANIFEST problems (was: Re: cvs commit: parrot parrotbug)
This kind of bug shouldn't happen if people actually read the messages the cvs commit spits out. It will tell you that the manifest check it runs on every commit fails. Please don't ignore it. Maybe a silly proposal, but nevertheless: Why are files not added to MANIFEST automatically on cvs add? Removing them from there should be less troublesome than having to add entries by hand. It's generally considered bad (and difficult) to modify things on the server after a commit. Also, then you don't find accidental checkins. Maybe I should have it start emailing the committer when the manifest check fails. -R
Re: [DOCS] Documentation tools
But once we start expecting people in the real world to compile this thing on their boxes in order to install perl, it would be extremely foolish to make them manually download and install perl6 + parrot + icu + perl5 + cpan modules 1 through 10, all from different sources. Try building any other large system. We don't know what this is going to look like when perl6 is done. One thing we can always do is create a tarball of tarballs, or a web page that says: 1. click _here_ to download perl 5.12.1 2. click _here_ to download parrot 1.3 3. click _here_ to download perl 6.0.14 we've had enough trouble with ICU, keeping it up to date, and we're not even using it. (And I'd wager we never use it.) there are already existing, well known, methods for distributing all these things. Maybe I'm old school, but I'd rather download 5 small or medium sized things than one huge thing. It also makes it a lot easier to change/upgrade just one piece. Why are we reinventing wheels? Why are we shipping extra bits around? IMHO, the releases better include everything necessary to build the application, within reason. Consistency and simplicity counts for a lot. Why create headaches we don't need? within reason. Thats where we're way off right now. The development environment can of course be more fluid. Ok. So lets rip all the crap out, and in two years when it comes time to release 1.0, we can re-think what needs to go in. -R
Re: open issue review (easy stuff)
... and then I got bored. ;) Thanks, all those changes applied. -R
Re: More closeable tickets in RT
26898, 26904, 26927, 26939, 26941, 26945, 26953, 26956, 26964, 26976, 27097, 27098, 27143, 27150 -- spam already reported these and they are to be cleaned out soon ;) (there have been a few spam slippages lately) Killed. I still need to go back and do the monthly spam filter update. -R
Re: cvs commit: parrot parrotbug
parrotbug is missing in MANIFEST which causes a make test error. This kind of bug shouldn't happen if people actually read the messages the cvs commit spits out. It will tell you that the manifest check it runs on every commit fails. Please don't ignore it. -R
Re: open issue review (easy stuff)
willowBored now!/willow /me runs and hides. Applied! (I should just give you access.) -R On Wednesday, March 3, 2004, at 06:39 PM, Robert Spier wrote: ... and then I got bored. ;) Thanks, all those changes applied. -R -- Will Coke Coledawill at coleda dot com
Re: www.parrotcode.org/ points to 0.0.10
This is on my list for tonight. I've got something all ready to go but have been busy with a $NEW_JOB. -R At Tue, 2 Mar 2004 00:44:02 -0500, Mitchell N Charity wrote: The parrot homepage http://www.parrotcode.org/ currently says Periodic releases will appear on CPAN; the current release is version 0.0.10, and can be found in the CPAN source directory. And source directory is a link to parrot-0.0.10.tar.gz The similarity in release numbers is particularly unfortunate. Sorry I missed that when looking at the page. (Saw source directory, thought ah, users will see the more recent releases in the directory). Updating the homepage soon would seem desirable. Mitchell
Re: www.parrotcode.org/ points to 0.0.10
As promised. The new site is now live. -R This is on my list for tonight. I've got something all ready to go but have been busy with a $NEW_JOB. -R At Tue, 2 Mar 2004 00:44:02 -0500, Mitchell N Charity wrote: The parrot homepage http://www.parrotcode.org/ currently says Periodic releases will appear on CPAN; the current release is version 0.0.10, and can be found in the CPAN source directory. And source directory is a link to parrot-0.0.10.tar.gz
Re: [PATCH] parrotbug 0.0.1
- it only accepts -ok / -nok flags (no *real* bug reports to be edited) This may or may not be good. We need a new processing system (for perl5 too) to deal with the -ok reports. - I'm not sure about the reporting address (Robert, I need your advice on this one) I suppose, it should be something like parrotbugatparrotcode.org Anyone else want to brainstorm bug addresses for parrot? -R
Re: www.parrotcode.org
Given that the new webpage won't be replacing the old webpage in time for this upcoming release... I suggest we make a few simple modifications to the _existing website_. I'm not going to make any more changes to the existing website, but since you asked nicely, I made these. Also, are the patches you refer to something which Dan has to do, or can someone else take care of this for him? Someone else can take care of this for him. (And I know he'd love it if someone stepped forward to become official web content maintainer.) We'll provide that person with resources and support, and it'll be quite fun and easy for everyone. -R
Re: www.parrotcode.org
I brought this up several months ago and was told that a new webpage was in the works. Where in the works is it? Does it have an expected time to leave the works? I agree with Mitchell that it is important to maintain a public face (lest we send the wrong impression). It will be leaving the works very shortly. A certain person whose name I will not mention here, has been promising to write some of the infrastructure I needed to port stuff to the new system for many many months. I finally gave up and did it myself tonight. (As I'm sure he was hoping I would do.) Exactly when is it going to leave the works? I sent an email to Dan tonight asking him to complete the patches he's promised so we can have it leave about the same time as the 0.1.0 release. It's just a matter of actually having the new content there. Parrot is currently making some large leaps forward in internal documentation, but it would be nice if that could be reflected in our external documentation. Please send your patches against... http:/ /svn.perl.org/perl.org/docs/live/parrotcode/ -R
Re: [CVS ci] PLATFORMS
Better it get fixed in CVS. There could be more errors of this kind. Confused. What would you like me to do? Please purge the platforms directory on the server. It collides with the PLATFORMS file on these poor pseudo-OS, that have case-insensitive filenames. (There could also still be a directory called hints on the server, it did exist some time ago. If yes please rm it too) *POOF* -R
Re: [CVS ci] PLATFORMS
After a bit of self-education on the CVS FAQ, I've come to the conclusion that renaming (delete/add) PLATFORMS to PLATFORMS.txt is the best way to solve this. Better it get fixed in CVS. There could be more errors of this kind. Confused. What would you like me to do? Also. cvs update -dP should work just fine for this. at least it does for me. Unless -P doesn't work properly on case-insensitive filesystems. -R
Re: [DOCS] Documentation tools
Suppose I could make a few changes to Pod-Simple, then our problem would be solved. Pod::Simple is relatively easy to subclass. And Sean is pretty receptive to changes. never have occurred to me to shove all of that in CVS. It always surprised me a that ICU was there, rather than just what was needed to get it to work. I don't think ICU should be in there at all... but that's just my vote :) So, it seems just to be a question of adding a prerequisites phase to the config. I would propose that we leave Pod-Simple in CVS until I have time to implement that, then we can delete it (promise). I wasn't going to make any rash actions like deleting it on the CVS server side ;) It's there, there's no rush to get it out, but I think in general, we want to keep the parrot source from becoming immensely huge. -R
Re: [DOCS] Documentation tools
I can possibly help it, so it's ok by me to delete lib/Pod, if that's the consensus. I'm not sure what the consensus is. But we should probably come to one. -R
Re: Patch vaporized?
At Thu, 5 Feb 2004 11:25:22 -0500, Gordon Henriksen wrote: [1 text/plain; us-ascii (7bit)] I've submitted a patch to bugs-parrot, and it didn't seem to get posted to RT or otherwise handled. Anyone know where it might've gone? I'm the one who would know. Please email me off-list with the message-id, subject, from address, and time sent, and I'll track it down. It's possible it's in the moderation queue. The MyDoom crap has been making his life more difficult. http://www.parrotcode.org/openpatches http://www.parrotcode.org/openpatches isn't working (ERROR RETRIEVING DATA). This is on my list to fix. -R
Re: Patch vaporized?
Did it have an executable attachment? :-) If anyone wants some MyDoom, I've got over a gigabyte (from the past 19 or so hours) absorbed by the perl.org servers I'd be glad to share with you. I can arrange for them to be emailed one at a time, or all at once. -R
Re: Patch vaporized?
I think I've tracked this down, mostly. The patch was rejected from the mailing list because it was too big. (Several hundred k.) You can find it in RT as 26056: [PATCH] Unify PMC accessor macros 2 26057: [PATCH] Unified PMC/PObj accessors phase 2 (26057 is one that points to a URL. Gordon, should I merge the two tickets?) Don't be afraid to email perlbug dash admin at perl.org with problems like this. I'll track them down as quick as I can. -R I've submitted a patch to bugs-parrot, and it didn't seem to get posted to RT or otherwise handled. Anyone know where it might've gone?
Re: [DOCS] Documentation tools
I've added the Perl modules for the docs tools to lib/Parrot/IO and lib/Parrot/Docs. I've also added Pod-Simple (2.05) and Pod-Escapes (1.03) which they use. I probably blinked.. but why are we including CPAN modules that we are not likely to change into the parrot repository? -R
Re: Mail troubles
Melvin, We're having some issues at perl.org due to the worm/virus/bounce stuff. Slow delivery is just something we're going to have to deal with for a few more days... but bounces I don't like. If your legitamite email is getting bounced by the perl.org (develooper.com) servers, please let me know (off list) and I'll see what I can do. We've had to implement some ugly things, but they shouldn't be bouncing legit mail. -R At Fri, 30 Jan 2004 13:29:53 -0500, Melvin Smith wrote: Hopefully this makes it to p6i list this week. It seems with the recent worm activity, some ISPs have locked down mail servers even more. I have replied to several personal emails (WRT Parrot) and they are bouncing for various reasons, one of which is because my new ISP is on the DUL blacklist, and my mail server is getting rejections. (Not to mention my mail has been getting lost on the way to p6i as well) If you aren't getting replies from me (Tim Cory for example), I'm trying to resolve the issue. -Melvin
Re: open issue review (easy stuff)
Right, good point. In that case, if we could give our intrepid and possibly slightly mad volunteers Dave Pippenger (dpippen) and Stephane Peiry (stephane) privs on the bug and todo queue for parrot, that'd be great -- we can start handing out todo tickets to folks for doing. done-o. -R
Re: open issue review (easy stuff)
Is there any way to get RT to close tickets (or change their status) entirely via e-mail? That'd make this a lot easier if we could throw a: RT-Status: Closed or something like it in the reply to a bug report that notes the bug has been fixed. I could implement this, but there are authentication issues. The rt CLI is another option. At some point in the future, I will document this better on bugs.perl.org. (Redoing bugs.perl.org is on my short-list.) -R
Re: The todo list
In the mean time, if anyone else has todo list items, send them (*ONE* per e-mail!) to bugs-parrot at bugs6.perl.org to get 'em in the queue and we'll start sorting them out from there. If we're lucky and have sufficient web luck we might even get 'em into a web-accessible TODO list (so make sure the subjects are descriptive too!) I need to repair the web-accessible TODO list. Someone nag me periodically. -R
open issue review (easy stuff)
Here are 177 currently outstanding parrot issues in the RT system. You can see more detail on them by going to: http://rt.perl.org/ clicking on guest access, and then typing the number into the upper right hand corner box. what we're mostly looking for are issues that can already be marked as closed. Once that's done, we can then take another pass and look at the outstanding issues. If you respond to this message, with the ticket id and brief reason why it can be closed, i.e. patch applied, patch rejected, bad idea.. I'll do the labor of updating the ticketing system. -R 726: -fno-strict-aliasing (fwd) 760: Parrot_warn doesn't work with a NULL interpreter 801: [PATCH] PerlArray in scalar context 15267: example/pxs is broken 15308: Dans Feedback Integrated into Documentation 15357: Read write ops in core.ops are broken 15748: [SPAM=07.30] [PATCH] added function in pmc.c 15877: [SPAM=07.30] [PATCH] genclass.pl 15988: Make.pl might load the wrong Make.pm 16020: Re: Array vs. PerlArray 16087: [PATCH] Scratchpad pmc 16114: [PATCH] faster assembler 16237: [PATCH] register window flush for sparc 16258: [PATCH] The Great Renaming 16300: [BUG] hash clone hangs 16414: Interpreter PMC 16622: RE: [PATCH PDD07] Document struct naming conventions 16755: imcc requires Parrot_dlopen but HAS_DLOPEN is never defined 16763: parrot hash test fail on sparc Linux 16764: [PATCH] library building win32 16772: [PATCH] Add format for UINTVAL 16789: 'make test' for parrot fails 16797: make subs closures 16842: Solaris8/gcc warnings/errors 16935: [PATCH] more regex stack manipulation 17072: warnings while compiling parrot 17158: [PACTH] reduce size of core_ops_prederef.* by a fair amount 17159: imcc / Mac OS X problem 17244: [PACTH] hash ops at runtime for op_code() lookup 17405: [PATCH] correct make pdb on Win32 17490: Magic is useless unless verifiable. 17491: One-queens problem 17492: Leaning tower of Hanoi 17562: Segfault in stack handling code running ELIZA 17646: [PATCH] Add stone-age exception handling 17702: [PATCH] resources.c - growing allocations 17739: [PATCH] Tests for assign ops 17817: [PATCH] Parrot_sprintf-related stuff, part 2 17876: [PTACH] Parrot_snprintf writes 1 char too much 17931: [PATCH] DOD/GC related 17974: make clean removes lib/Parrot/PMC.pm 18003: Make test failures under Win32 MSVC++ 18044: Assembler doesn't return a useful exit status 18064: test 75 of t/pmc/pmc.t fails 18097: [PATCH] allow NULL interpreter in sprintf like functions 18142: [PACTH] Parrot_destroy 18170: [PATCH] very complete lexical scope implementation 18189: Test failures with 'long long' on i386/linux 18319: [PATCH] Re: How to portably link on Win32 (all flavors), OS/2 and VMS? 18320: PerlArray, GC or string bug 18637: PDD06: Incomplete sentence at end of section 18762: nci.t hates me 18782: [PTACH] long double support i386/linux 18832: [PATCH] nci test lib 18892: Perl_Parse from JNI Native code crashing... 18897: Error running Configure.pl 19090: [PATCH] make parrot_v[sfn]*printf behave itself 19143: Another GC bug? 19163: configure probe for va_list* 19183: languages/perl6/t/compiler.t -- multiple ways to spell Inf 19184: languages/perl6/t/rx/call test error 19192: JIT fails 3 tests on AMD K5 19328: bug/feature (?) in perlarray of perlarrays 19331: [PATCH]befunge 0.1.0 released 19356: [PATCH] creating string_destroy() 19467: [PATCH] win32.h - MinGW #pragma warnings 19516: imcc whitespace sensitive parsing error 19599: [pasm bug] PerlHash: cannot delete a key 19670: [PASM] bug in i/o (read on stdin) 19671: [PATCH] befunge debugger supports the delete instruction 19728: [PATCH] SPARC jit fix for restart 19834: [PATCH] sub, add, mul, div with combinations of INT, NUM, PMC 19871: Fwd: Introduction and cygwin results 19872: Fwd: Re: Introduction and cygwin results 19873: Fwd: perl6 testing on mingw32 19874: Patch for pdump 20298: Operators neg and abs in core.ops 20358: [BUG] disassemble still 20666: Assemble.pl Reports Incorrect Line Numbers after Removal of Macros 20707: Major packfile(?) breakage 21577: [PATCH] sun4 vtable jit support 21600: [PATCH] Enable buffer io in PIO 21665: [BUG] Incompatible return type in io/io_unix.c 21668: APL doesn't use sigils 21679: [PATCH] Implement use for P6C. 21729: IMCC doesn't handle scientific notation constants 21988: More Small Memory Leak Fixes 22119: [PATCH]Parrot PPC JIT: More ops and bugfixes. 22135: NCI and Jit push arguments in wrong order 22173: test t/native_pbc/number.t fails on powerpc linux 22174: [PATCH] snprintf link errors on Win32 22175: [PATCH] Static libparrot should built by target 'all' 22183: imcc doesn't support \e 22214: set Nx, Sx with non-numeric Sx results in number 22218: Segfault in Parrot_really_destroy 22281: fix rebuild_other so that it does not make chunks bigger than MAX_ITEMS 22316: [PATCH] Truncated entry in glossary.pod 22319: [PATCH] extra-large is too big for varargs 22321: [PATCH] debug tests when debugging 22324: [PATCH] fixed test and
Re: open issue review (easy stuff)
Thanks for taking this on. No problemo. 22558: Another Hack at constant propogation Aplied or Fixed and then applied (I forget which) 24847: [patch] simplify register stacks (remove code duplication) Reject (resubmitted late as a different patch which was applied) Noted. (FYI, for the future, I may not ack all the changes, although it depends how many there are.) -R
Re: Patch submission gone missing?
I submitted a patch yesterday to [EMAIL PROTECTED], and received the automated response (the ID is [perl #24789]), but it doesn't seem to have been forwarded to the mailing list. Is something up with the tracking system? Nothing is up. It's in the moderation queue. The list moderator is probably still recovering -- it is a holiday. Please give him a break. -R
Re: Patch submission gone missing?
I didn't realize there was moderation. (How was spam getting through?) Spam was getting through because when I upgraded RT, I didn't re-insert some of my envelope massaging magic, which meant that spam was looking as if it was coming from a valid address, when it really wasn't. Once I re-inserted that magic, the spam disappeared. -R
Re: threads and shared interpreter data structures
A marriage between Parrot and APR (Apache Portable Runtime) might be a marriage in heaven, in that respect. For those not in the know, APR contains most of the grotty low-level bits. It misses some things that are important to us, like fork(), and it's got this concept of memory pools, which seem pretty nifty, but not necessarily compatible with the parrot scheme... but it may get us 80% of the way there, leaving us only 20% to implement, which wouldn't be so bad. -R
Re: threads and shared interpreter data structures
At Tue, 23 Dec 2003 14:23:45 -0500, Dan Sugalski wrote: It's that last thing I'm worried about. That all thread related things in Parrot are forced to use an extra indirection and consequent performance penalty. They'll live. Python and Ruby both have a single global interpreter lock and nobody much cares. I really don't think thats true. People do care, and there are some brain cells out there working to fix it, last I checked. Its just not top of the list, because its non-trivial. -R
spam leakage
apologies for the recent spam leakage.. it looks like I need to do my bi-monthly tuning. I'll try and get to it as soon as I can. -R
Re: spam leakage
I've trained the filter with all of Novembers spam, and done a few tweaks, and removed the recent offending messages from the parrot queue. Sorry for the annoyance. -R # Ticket 24616 updated. # Ticket 24655 updated. # Ticket 24677 updated. # Ticket 24692 updated. # Ticket 24696 updated. # Ticket 24700 updated. # Ticket 24715 updated. # Ticket 24722 updated. At Sat, 20 Dec 2003 00:37:21 -0800, Robert Spier wrote: apologies for the recent spam leakage.. it looks like I need to do my bi-monthly tuning. I'll try and get to it as soon as I can. -R
Re: Segfault warning boxes on Win32
More important -- is the Segfault reported in any other manner. If not, thats bad. It's not, I'm afraid Then this shouldn't be off by default. Turn it off for automated testing. But in general use, I think you want this on. Oh look. My program just went away. I wonder why? -R
Re: Some PIR How do I? questions
I think separating the IMCC and parrot programming FAQs, or making the IMCC faq a section of a larger Parrot FAQ, would be better. The IMCC FAQ really ought to be about syntax rather than semantics. Patches welcome. :-J -R
Re: [PS] open patches
I resolved #24030 and #24038 by changing the Status field and hitting Save Changes, then I noticed there was a Resolve option on the top righthand side which asks for details for a notification email. I'm wondering which is the approved way? Either is fine. By default the Resolve page will only add a comment unless you change it to Correspondence. But if you don't enter any text in the big box, none will be recorded. -R
Re: [PS] open patches
My account (mikescott) at http://auth.perl.org/auth/account shows the correct email. The RT page assures me that I'm signed in as mikescott. I go to the Modify ticket #24030 and set Status to resolved, click Save Changes and get Status: Permission Denied. RT had a different idea of what your email address was. (There is an issue with propagation.) I've reeducated it. Try now. -R
Re: [PS] open patches
(24205) [PATCH] removing -mno-accumulate-outgoing-args for non x86 arch the last one was applied by Dan, but the Status wasn't updated on RT. I can't do it myself (permission denied). I've updated the ticket. RT thinks your email address is @perl.it, but the ticket was created from the @alos.it address. Thanks- -R
Re: [PS] open patches
Some of patches on that list that are mine. #24030 Obsolete #24038 Obsolete #24043 Applied #24063 Applied #24177 Rejected #24188 Applied I tried to update the status of #24177 but got Permission Denied. Any chance of that being changed so I could update them myself? You have to log in with an account that uses the same email address, and then you should be able to. (If you have an account that uses a different email address, then I need to match things up.)
Re: More file moves
Robert (the great god of CVS) is going to do the final set of big moves later on. Or possibly already has, depending on when you get this. This may, probably will, break things for a while. The scoop is: I have done this, and there is blood all over the walls. When this is done I'll fix up the MANIFEST and makefile programs to make this all work properly. Dan is off to clean this up now. I hope he's got lots of bleach and rubber gloves. (I recommend not doing a CVS update until Dan says he's reattached the head.) -R
Re: [COMMIT] imcc moves out of languages
So much for preserving repository history. (Dan! Where's the list of things to move?) -R At Wed, 22 Oct 2003 22:29:49 -0400, Melvin Smith wrote: IMCC has graduated from the parrot/languages/imcc directory to parrot/imcc. Please update your trees. We may still want to move the main up to the parrot directory and possibly do an include/imcc directory, but I'm not sure. Test builds on my machine, so I think everything is back to intact for now. -Melvin
Re: Website needs updating
Coming soon, a revised website that'll be easy for everyone to send patches to, and much easier for us to give others direct access to modifying it. The core is in place, but there are one or two technical chunks that need to get finished before I can call it done. (or at least feature/content equivalent) -R At Mon, 13 Oct 2003 14:45:56 -0600, [EMAIL PROTECTED] wrote: All~ I have noticed that the webpage seems to stay rather behind the current state. Perhaps replacing it with somehting that is easier to keep up-to-date like a wiki would be useful... I don't really know, but at the least it should be updated to state something truer then the current release is version 0.0.10
Re: You too can direct the Attack of the Unicode Monster!
Also, I'm working on OS X, so there is the library loading issue to be solved too. 10.3 should make this easier, as it has dlopen emulation. (While not necessarily the perfect long-term solution, it at least lets you get things done.) -R
Re: [PATCH] parrot-build-1: Build parrot incl. imcc files take 1
Then we've got patches to submit to IBM when we have 'em ready. We can't require GNU make -- it isn't available on some platforms, and I honestly don't see what reason there would be to require it over other make variants. I think this is energy spent in the wrong place. But we've discussed this already. ANYWAY- Before we spend more time on ICU, we should actually start using it. -R
