2014-04-16 12:23 GMT+05:30, Pirate Praveen :
> 2013-06-09 9:11 GMT+05:30, Praveen A :
>> Thanks Antonio!
>
> acts-as-taggable-on is still failing tests.
>
> http://anonscm.debian.org/gitweb/?p=pkg-ruby-extras/ruby-acts-as-taggable-on.git
>
> Can some one look into it?
I have created a usertag rail
2013-06-09 9:11 GMT+05:30, Praveen A :
> Thanks Antonio!
acts-as-taggable-on is still failing tests.
http://anonscm.debian.org/gitweb/?p=pkg-ruby-extras/ruby-acts-as-taggable-on.git
Can some one look into it?
Thanks
Praveen
--
പ്രവീണ് അരിമ്പ്രത്തൊടിയില്
You have to keep reminding your govern
Thanks Antonio!
On Jun 9, 2013 6:43 AM, "Antonio Terceiro" wrote:
Hi Praveen,
On Tue, Jun 04, 2013 at 08:09:10PM +0530, Praveen A wrote: > 2013/6/4
Antonio Terceiro
Hi Praveen,
On Tue, Jun 04, 2013 at 08:09:10PM +0530, Praveen A wrote:
> 2013/6/4 Antonio Terceiro :
> > You have to merge pristine and upstream as well before pushing.
>
> Hi Antonio,
>
> Please check if the repo is in a good state. I have manually merged
> all branches. If you think its okay,
2013/6/5 Sam Ruby :
>> sudo aptitude update
>> sudo aptitude safe-upgrade
>
>
> I used 'sudo apt-get update; sudo apt-get dist-upgrade' instead. Is that a
> problem?
that should be fine.
> What version of rack do you see? Rails 3.2 doesn't appear to like rack 1.5.
>
>> $ gem list rack
>>
>> ***
On 06/04/2013 03:43 PM, Praveen A wrote:
2013/6/4 Sam Ruby :
Don't apply the previous patch.
I can reproduce the above error with the following commands:
rails new foobar
cd foobar
rails generate scaffold Product title
rake db:migrate
rake test
Relevant line in testapp/test/test_helper.rb:
2013/6/4 Sam Ruby :
> Don't apply the previous patch.
>
> I can reproduce the above error with the following commands:
>
>> rails new foobar
>> cd foobar
>> rails generate scaffold Product title
>> rake db:migrate
>> rake test
>
>
> Relevant line in testapp/test/test_helper.rb:
>
>> require File.ex
On 06/04/2013 09:26 AM, Antonio Terceiro wrote:
On Mon, Jun 03, 2013 at 10:38:29AM -0400, Sam Ruby wrote:
On 06/03/2013 10:14 AM, Christian Hofstaedtler wrote:
Next thing on my list is rack, which also needs a new version.
Do you have an opinion on rack as well?
Currently, actionpack 3.2 wan
On 06/04/2013 12:46 PM, Sam Ruby wrote:
On 06/04/2013 12:19 PM, Sam Ruby wrote:
4) I haven't yet figured out how to run this. I keep getting errors
about local changes. I'm now off to learn quilt.
http://wiki.debian.org/Diaspora/Packaging/quilt
I can now run with this patch, and get furthe
On 06/04/2013 12:19 PM, Sam Ruby wrote:
4) I haven't yet figured out how to run this. I keep getting errors
about local changes. I'm now off to learn quilt.
http://wiki.debian.org/Diaspora/Packaging/quilt
I can now run with this patch, and get further. Next up: a series of
error messages
On 06/04/2013 11:07 AM, Praveen A wrote:
2013/6/4 Praveen A :
Sam,
You can just substitute the package name in the git clone url to get other
packages. So change ruby-shoulda-matchers to ruby-i18n to checkout i18n
debian package repo. Follow the same process for building it.
Praveen
Hi Sam,
2013/6/4 Praveen A :
> And with the changes Christian made, I was able to run rails new
> testapp, successfully. Also I had to add rubygems-integration to build
> deps, so it could find rails. I also added some more build deps so it
> has all the libraries it need to run tests (try git pull and
> g
2013/6/4 Praveen A :
> Sam,
>
> You can just substitute the package name in the git clone url to get other
> packages. So change ruby-shoulda-matchers to ruby-i18n to checkout i18n
> debian package repo. Follow the same process for building it.
>
> Praveen
Hi Sam,
Anyway these are already uploade
2013/6/4 Antonio Terceiro :
> You have to merge pristine and upstream as well before pushing.
Hi Antonio,
Please check if the repo is in a good state. I have manually merged
all branches. If you think its okay, you can upload the new version.
If not I can try to replay my changes on top of 0.6.0
On Mon, Jun 03, 2013 at 10:38:29AM -0400, Sam Ruby wrote:
> On 06/03/2013 10:14 AM, Christian Hofstaedtler wrote:
> >>>Next thing on my list is rack, which also needs a new version.
> >
> >Do you have an opinion on rack as well?
> >
> >Currently, actionpack 3.2 wants ~> 1.4.5, but
> >ac
On Mon, Jun 03, 2013 at 06:17:18PM +0200, Christian Hofstaedtler wrote:
> Hey everybody,
>
> The team repository has updated packages for:
> ruby-mail
> ruby-journey
> ruby-rack
> ruby-i18n
>
> It also carries patches to:
> ruby-actionpack-3.2
> ruby-activesupport-3.2
> ruby-activem
On Tue, Jun 04, 2013 at 01:21:18AM +0530, Praveen A wrote:
> 2013/6/3 Praveen A :
> >> Ah! I just uploaded 0.6.1! Just pull, before you update.
> >
> > There is conflict, I will just remove my upload instead.
>
> Before my dcut commands could remove it, it was already accepted. I
> merged the chan
2013/6/3 Praveen A :
>> Ah! I just uploaded 0.6.1! Just pull, before you update.
>
> There is conflict, I will just remove my upload instead.
Before my dcut commands could remove it, it was already accepted. I
merged the changes, but it won't let me push upstream or pristine-tar
branches, can I do
* Sam Ruby [130603 20:43]:
> On 06/03/2013 12:17 PM, Christian Hofstaedtler wrote:
[..]
> Looking for other 'repositories' I came across:
>
> http://wiki.debian.org/Teams/Ruby/Packaging#Obtaining_the_master_repository
>
> But that one doesn't appear to have been updated today:
>
> http://anonsc
Sam,
You can just substitute the package name in the git clone url to get other
packages. So change ruby-shoulda-matchers to ruby-i18n to checkout i18n
debian package repo. Follow the same process for building it.
Praveen
On Jun 4, 2013 12:12 AM, "Sam Ruby" wrote:
On 06/03/2013 12:17 PM, Chris
On 06/03/2013 12:17 PM, Christian Hofstaedtler wrote:
Hey everybody,
The team repository has updated packages for:
ruby-mail
ruby-journey
ruby-rack
ruby-i18n
It also carries patches to:
ruby-actionpack-3.2
ruby-activesupport-3.2
ruby-activemodel-3.2
If you could give these
Hey everybody,
The team repository has updated packages for:
ruby-mail
ruby-journey
ruby-rack
ruby-i18n
It also carries patches to:
ruby-actionpack-3.2
ruby-activesupport-3.2
ruby-activemodel-3.2
If you could give these a try (by building from the repo), that'd be
great.
FWIW:
rai
On 06/03/2013 10:14 AM, Christian Hofstaedtler wrote:
Sam,
* Sam Ruby [130603 16:05]:
On 06/03/2013 09:49 AM, Christian Hofstaedtler wrote:
Praveen, Sam,
* Praveen A [130603 15:45]:
2013/6/3 Praveen A :
I will update it as I would like you to spend time on things I can't
solve myself - ra
Sam,
* Sam Ruby [130603 16:05]:
> On 06/03/2013 09:49 AM, Christian Hofstaedtler wrote:
> >Praveen, Sam,
> >
> >* Praveen A [130603 15:45]:
> >>2013/6/3 Praveen A :
> >>>I will update it as I would like you to spend time on things I can't
> >>>solve myself - rails specific stuff :)
> >>
> >>Late
2013/6/3 Praveen A :
> 2013/6/3 Christian Hofstaedtler :
>> Praveen, Sam,
>> activesupport right now requires '= 0.6.1' for i18n. I'm working on
>> updating i18n to 0.6.4, and adding a patch to activesupport to say
>> '>= 0.6.1'.
>
> Christian,
>
> Ah! I just uploaded 0.6.1! Just pull, before you u
On 06/03/2013 09:49 AM, Christian Hofstaedtler wrote:
Praveen, Sam,
* Praveen A [130603 15:45]:
2013/6/3 Praveen A :
I will update it as I would like you to spend time on things I can't
solve myself - rails specific stuff :)
Latest version of i18n is 0.6.4. Should we update it to latest
ver
2013/6/3 Christian Hofstaedtler :
> Praveen, Sam,
> activesupport right now requires '= 0.6.1' for i18n. I'm working on
> updating i18n to 0.6.4, and adding a patch to activesupport to say
> '>= 0.6.1'.
Christian,
Ah! I just uploaded 0.6.1! Just pull, before you update.
> Next thing on my list i
Praveen, Sam,
* Praveen A [130603 15:45]:
> 2013/6/3 Praveen A :
> > I will update it as I would like you to spend time on things I can't
> > solve myself - rails specific stuff :)
>
> Latest version of i18n is 0.6.4. Should we update it to latest
> version? For now I'll update to 0.6.1 and if i
2013/6/3 Praveen A :
> I will update it as I would like you to spend time on things I can't
> solve myself - rails specific stuff :)
Latest version of i18n is 0.6.4. Should we update it to latest
version? For now I'll update to 0.6.1 and if it is better to update to
latest, I will update it later.
2013/6/3 Sam Ruby :
> I believe I only have 1.9.3p194 installed at this point.
>
> I probably didn't provide enough background. Knowing that the tests for
> shoulda-matchers depend on 'rails new testapp' working, I'm trying to see if
> that works before trying shoulda-matchers again.
>
> I presume
On 06/03/2013 08:04 AM, Praveen A wrote:
Only ruby 1.8 was not finding i18n, with ruby 1.9, it was showing only
missing rails. Did you notice that?
I believe I only have 1.9.3p194 installed at this point.
I probably didn't provide enough background. Knowing that the tests for
shoulda-matcher
Only ruby 1.8 was not finding i18n, with ruby 1.9, it was showing only
missing rails. Did you notice that?
On Jun 3, 2013 4:04 PM, "Sam Ruby" wrote:
On 06/03/2013 02:12 AM, Praveen A wrote: > > 2013/6/3 Praveen A <
prav...@gmail.com>: >> >> Hi Sam, >...
Getting further...
Resolving dependencies
On 06/03/2013 02:12 AM, Praveen A wrote:
2013/6/3 Praveen A :
Hi Sam,
There was a bug in actionpack which made it unavailable to rubygems and
bundler. It is fixed by a recent upload 3.2.13-6. Can you update actionpack
and try the tests again? As Christian said, we should remove any
Gemfile.lock
2013/6/3 Praveen A :
> Hi Sam,
>
> There was a bug in actionpack which made it unavailable to rubygems and
> bundler. It is fixed by a recent upload 3.2.13-6. Can you update actionpack
> and try the tests again? As Christian said, we should remove any
> Gemfile.lock and make bundler use versions av
Hi Sam,
There was a bug in actionpack which made it unavailable to rubygems and
bundler. It is fixed by a recent upload 3.2.13-6. Can you update actionpack
and try the tests again? As Christian said, we should remove any
Gemfile.lock and make bundler use versions available in debian. We might
need
On 06/02/2013 03:26 PM, Sam Ruby wrote:
On 06/02/2013 01:04 PM, Christian Hofstaedtler wrote:
Sam,
* Sam Ruby [130602 19:00]:
On 06/02/2013 12:46 PM, Christian Hofstaedtler wrote:
In fact, one doesn't even need shoulda-matchers at all to reproduce
this error. The following command also suffi
On 06/02/2013 01:04 PM, Christian Hofstaedtler wrote:
Sam,
* Sam Ruby [130602 19:00]:
On 06/02/2013 12:46 PM, Christian Hofstaedtler wrote:
In fact, one doesn't even need shoulda-matchers at all to reproduce
this error. The following command also suffices:
$ rails new foobar.
Well - this d
Sam,
* Sam Ruby [130602 19:00]:
> On 06/02/2013 12:46 PM, Christian Hofstaedtler wrote:
> In fact, one doesn't even need shoulda-matchers at all to reproduce
> this error. The following command also suffices:
>
> $ rails new foobar.
Well - this does work for me.
What exact error message do you
On 06/02/2013 12:46 PM, Christian Hofstaedtler wrote:
* Sam Ruby [130602 18:31]:
From what I can see in the shoulda-matchers tests, the test
application has a Gemfile.lock, which tries to pull in a version of
"i18n" that is not in the Debian archive.
For your tests to succeed, you'll need to B
* Sam Ruby [130602 18:31]:
> On 06/02/2013 11:55 AM, Praveen A wrote:
> >
> >We should not be using bundler or rubygems at all. So create a quilt
> >patch and comment out all usage of bundler and rubygems like require
> >'rubygems', require 'bundler/setup', Bundler.require etc.
>
> Forgive me, bu
On 06/02/2013 11:55 AM, Praveen A wrote:
We should not be using bundler or rubygems at all. So create a quilt
patch and comment out all usage of bundler and rubygems like require
'rubygems', require 'bundler/setup', Bundler.require etc.
Forgive me, but this seems like advice that is conflictin
2013/6/2 Sam Ruby :
> On 06/02/2013 11:16 AM, Christian Hofstaedtler wrote:
>> This does not include actually installing *rails*.
>>
>> This is a problem of broken build-dependencies in ruby-shoulda-matchers
>> (which needs to add ruby-rails-3.2).
>
> I'm getting conflicting input between you and P
On 06/02/2013 11:16 AM, Christian Hofstaedtler wrote:
* Sam Ruby [130602 16:34]:
On 06/02/2013 08:34 AM, Christian Hofstaedtler wrote:
[..]
Therefore, the right place to focus is on getting a version of
bundler which play's nice with Debian?
I am not sure what you mean with that. How does
2013/6/2 Sam Ruby :
> Where we go from here...
>
> Patching Rails to generate apps that don't, by default, use bundler will
> still require changes to shoulda_matchers. It furthermore will cause Rails
> to behave in ways different that it does in other environments.
>
> Therefore, the right place
* Sam Ruby [130602 16:34]:
> On 06/02/2013 08:34 AM, Christian Hofstaedtler wrote:
[..]
> >>Therefore, the right place to focus is on getting a version of
> >>bundler which play's nice with Debian?
> >
> >I am not sure what you mean with that. How does the existing
> >bundler package not help?
>
On 06/02/2013 08:34 AM, Christian Hofstaedtler wrote:
Hi,
* Sam Ruby [130602 13:43]:
On 05/28/2013 02:27 PM, Praveen A wrote:
Hi,
I have been getting stuck trying to build many rails based gems,
shoulda-matchers - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709431
[..]
Offlist, Prav
Hi,
* Sam Ruby [130602 13:43]:
> On 05/28/2013 02:27 PM, Praveen A wrote:
> >Hi,
> >
> >I have been getting stuck trying to build many rails based gems,
> >shoulda-matchers - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709431
> >
[..]
>
> Offlist, Praveen pointed me to
>
> git://anonscm.de
On 05/28/2013 02:27 PM, Praveen A wrote:
Hi,
I have been getting stuck trying to build many rails based gems,
shoulda-matchers - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709431
acts_as_api, nested_form etc I think they are too much dependent on
bundler and it is too complex to untangle
48 matches
Mail list logo
