2013/1/3 Jordon Bedwell :
> I would hold off on pushing out 362 into experimental for now:
> https://bugs.ruby-lang.org/issues/7629
>
> I know it's experimental but still, I hope it's not this experimental!
I've updated my github clone of the team repo to 1.9.3p374 (on the
experimental branch).
J
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/01/13 17:09, Antonio Terceiro wrote:
> Can you check the others? I did a quick check on two of the
> rb_path_* and it seems to be ok.
There are a few matches in the source package adanaxisgpl, but it
looks like a naming conflict as the package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Antonio,
On 03/01/13 19:38, Antonio Terceiro wrote:
> Also, I am suspicious of those symbols changes. Those dropped
> symbols might break compiled extensions who use them. Can you
> investigate whether we are agoing to have problems with that?
I
Hi folks,
I've updated my github copy[1] of the team's MRI repo to the latest
release, 1.9.3p362.
I'd love to see the latest MRI available in experimental during the
wheezy freeze. Is it possible to have my work reviewed? Hopefully it's
a good base to work from.
cheers
James
[1] https://github
On 16 November 2012 18:47, James Healy wrote:
> * there are 7 vendored C libraries in vendor/. 5 of them look like
> they're used during compilation. Some are available in debian, but it
> looks like their might be some non-standard modifications to at least
> some of them. What&
On 27 November 2012 00:02, Antonio Terceiro wrote:
> Note that -4 is not in testing yet due to a problem on sparc, so -5 will
> hit the archive pretty soon.
regarding the sparc failures, has anyone else noticed this pattern to
the sparc build logs for the ruby1.9.1 source package?
stadler - 32 c
Hi,
I had planned to have a go at packaging MRI 2.0~preview1, however
after watching some rubyconf videos I got interested in rubinius again
so I looked into updating the existing packaging work to the 2.0.0~rc1
release. The latest work is in my github account at [1].
It's more or less at the sam
Hi folks,
I've updated my github version [1] of the teams MRI git repo to the
latest stable release of 1.9.3.
I'm still quite new to packaging C libraries, so there's a commit [2]
that seems a little strange to me. I had to update the
debian/libruby1.9.1.symbols file because some symbols had been
On 04/11/2012 11:51 AM, "Lucas Nussbaum" wrote:
> It depends on the 'ruby compatibility version' for that release. Is it
> 1.9.1 or something else?
How do I tell?
James
Hi folks,
I'm interested to trying out the MRI 2.0 preview release so I thought I'd
try and package it for experimental at the same time.
Should it be an upgrade to the 1.9.1 packages or a new package that can be
installed in parallel? My guess is a new package due to syntax changes in
the langua
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi folks,
I've updated my github version [1] of the teams MRI git repo to the
latest stable release of 1.9.3.
While the wheezy freeze is in place is it possible to upload the new
version to experimental? It would be helpful to have it available for
Hi folks,
I'm an Australian ruby dev that dabbles in Debian packaging [1]. I'm
holidaying in Europe until the end of January 2013 and would like to
get a few cross signatures on my GPG key to assist with any future
Debain work. Australia is far enough from everywhere that it makes
sense to take ad
On 28 May 2012 09:54, Antonio Terceiro wrote:
> Your changes are pretty good, thanks. I've merged then and will upload
> this version soon.
Great, thanks for reviewing my work.
James
--
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Con
On 16 May 2012 01:01, Lucas Nussbaum wrote:
> After re-cloning your repo, I can build the package (well at least it
> did not fail during dpkg-source. I did not look further).
> Strange.
Thanks - I think I had the upstream/1.9.4.194 tag pointing to the wrong ref.
The current repo on my github ac
On 15 May 2012 20:46, Lucas Nussbaum wrote:
>> You can see the results of my work at https://github.com/yob/debian-ruby
>
> But when I gbp-clone'd your repo, I did not get a pristine-tar branch.
> Did you forget to push it?
I forgot to create it. I re-imported 1.9.3p194 and forced pushed my
work
Hi folks,
I'm keen to see MRI 1.9.3p194 make it into unstable before the wheezy
freeze and thought I'd help out by trying to update the current
packaging in git.
I made some progress, but unfortunately I can't get it to build with
git-buildpackage. Are there any guides to the way MRI is maintaine
> I'm new to ruby and rubygems. I installed the debian rubygems package
> (from debian testing) and I'm trying to configure it to have gems in my
> $HOME dir as this is a shared server.
You should be able to install gems to your home dir by adding the following to
~/.gemrc
gem: --user-install
17 matches
Mail list logo
