Nabble - debian-ruby

[Future Icon Records] You've been added to our mailing list.

2009-11-28T19:59:03Z

Hi I represent KONVICT MUSIC recording artist COLBY O'DONIS (Just Dance Ft Colby O'Donis. Beautiful Ft Colby O'Donis) and we want to share with you His first Original Christmas song I made a radio edit of so happy here it is if you like it Radio Edit Of - So Happy https://rcpt.yousendit.com/782608652/9a8972b464bfc006aa5139a89722060d Instrumental Radio Edit - So Happy https://rcpt.yousendit.com/782608822/4c2efde9129f9900fe9782387ef48410 

--------
Get your free download from Future Icon Records here: http://fburls.com/65-VSuEJFbK
--------

You have been added to the Future Icon Records fan list!

If you would like to verify your info or add more to your fan profile, you can do so by clicking on the following link:

http://www.FanBridge.com/signup/fansignup.php?userid=129853&email=debian-ruby@...&confCode=3467PdXde62F145aBY6hUtkt44

--
This list is powered by FanBridge, the world's leading provider of fan relationship management services for artists.

With FanBridge your information is always secure.

For more information about FanBridge please visit http://www.FanBridge.com/learn/
--

***Important: Please be sure to add the email address (futureiconrecords@...) to your safe senders list.***

Here's how:

Gmail
1. Click Contacts along the left side of any Gmail page.
2. Click Add Contact.
3. In the primary email address box, type futureiconrecords@....
4. Click Save.

AOL (version 9.0 or higher)
1. Click the Mail menu and select Address Book.
2. In the pop up box, click the Add button.
3. In the "Other E-Mail" field, type futureiconrecords@....
4. Make our From address the "Primary E-Mail" address by checking the associated check box.
5. Click the Save button.

AOL 8.0
1. Open this confirmation email.
2. Click Add Address.
3. Verify the sender's contact information (futureiconrecords@...).
4. Click Save.

Yahoo!
1. Click the "addresses" button
2. Select "Add Contact"
3. Save the futureiconrecords@... to your contacts list.

Hotmail
1. Click Options.
2. On the left side of the page, click Mail, and then click Junk E-Mail Protection.
3. Click Safe List.
4. Type futureiconrecords@..., and then click Add.

Outlook
1. Right-click on a message from futureiconrecords@....
2. Point to Junk E-mail, and click Add Sender to Safe Senders List.

----------------------------------------
Future Icon Records sent this email to debian-ruby@...
Questions? Contact futureiconrecords@... or Future Icon Records, c/o FanBridge, Inc. - 14525 SW Millikan Way, #16910, Beaverton, Oregon 97005, United States

Update Your Information - http://fburls.com/32-oBPIIcjZ
Forward to a friend - http://fburls.com/94-BcZJurgI
Unsubscribe - http://fburls.com/43-pcuCdxn4
Privacy Policy - http://www.FanBridge.com/learn/privacy.php

This email message is powered by FanBridge:
http://www.FanBridge.com/b.php?id=129853
Powering Valuable Fan Relationships

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Ruby Enterprise Edition, Rails & Debian

2009-11-17T12:22:50Z

I just installed the REE Ubuntu .deb package from RubyForge on my Squeeze box and would like to know if its possible to point its gems to Debian gems. For example, my Rails app requires will_paginate and I have pointed my app to use Debian's packaged version. However, when I use REE it insists on using its own gems and wont recognize my will_paginate link in .../vendor/plugin.

My question is how do I get REE to use Debian's "gems" instead of manually install gems?

--
Richard Hurt
CEO KangarooBox, LLC.
e: rnhurt@...
p: 502-298-5422
w: http://KangarooBox.com

[rnhurt.vcf]

begin:vcard fn:Richard Hurt n:Hurt;Richard org:KangarooBox, LLC adr:Suite 220;;6801 Dixie Hwy.;Louisville;KY;40258;United States email;internet:rnhurt@... title:CEO tel;work:(502) 298-5422 x-mozilla-html:FALSE url:http://www.kangaroobox.com version:2.1 end:vcard

Re: Ruby 1.9.1 and Rails

2009-11-02T18:08:48Z

On 11/2/09 5:05 PM| Nov 2, 2009, Antonio Terceiro wrote:

Richard Hurt escreveu isso aí:

I am trying to move my Squeeze box over to Ruby1.9.1 and Rails and
am having a tough time finding information on how to proceed.  I've
install ruby1.9.1-full and pulled in rubygems1.9.1 from Sid but I
still can't get Rails to work.

Are there any guides, walkthroughs or tutorials for moving a Debian
system to Ruby 1.9.1?  Has anyone tried to run Rails under 1.9.1 on
Squeeze or am I the first?  Is this even the correct list for this
question?

I've just tried on Sid and it works fine.

AFAICT you only need that "ruby", "irb", "gem", etc in your PATH are the
1.9.1 versions. I did that by symlinking them in my ~/bin (which has
higher priority in my PATH than the system directories):

cd ~/bin/
ln -s /usr/bin/ruby1.9.1 ruby
ln -s /usr/bin/gem1.9.1 gem
ln -s /usr/bin/irb1.9.1 irb

I've also changed the PATH to include $HOME/.gem/ruby/1.9.1/bin, so that
after installing rails and stuff I can use the programs that come with
them.

But please note that doing this might break other ruby stuff you have
installed, specially packaged applications that are not compatible with
ruby 1.9.1 and refer to "ruby" instead of "ruby1.8" in their shebangs.

Antonio,

Thanks for the reply. I'm going to give it another try and see what happens and maybe I can get an exact error message. The difference is that I'm runing Squeeze and you are on Sid. I don't know how that will play out but hopefully I can get it running. I'm counting on the faster performance to help me out on a major project.

If I get it working I'll do a little write up and post it on my blog so that others don't have to go through the pain and suffering. :)

--
Richard Hurt
CEO KangarooBox, LLC.
e: rnhurt@...
p: 502-298-5422
w: http://KangarooBox.com

[rnhurt.vcf]

Re: Ruby 1.9.1 and Rails

2009-11-02T14:05:20Z

Richard Hurt escreveu isso aí:
> I am trying to move my Squeeze box over to Ruby1.9.1 and Rails and
> am having a tough time finding information on how to proceed. I've
> install ruby1.9.1-full and pulled in rubygems1.9.1 from Sid but I
> still can't get Rails to work.
>
> Are there any guides, walkthroughs or tutorials for moving a Debian
> system to Ruby 1.9.1? Has anyone tried to run Rails under 1.9.1 on
> Squeeze or am I the first? Is this even the correct list for this
> question?

I've just tried on Sid and it works fine.

AFAICT you only need that "ruby", "irb", "gem", etc in your PATH are the
1.9.1 versions. I did that by symlinking them in my ~/bin (which has
higher priority in my PATH than the system directories):

cd ~/bin/
ln -s /usr/bin/ruby1.9.1 ruby
ln -s /usr/bin/gem1.9.1 gem
ln -s /usr/bin/irb1.9.1 irb

I've also changed the PATH to include $HOME/.gem/ruby/1.9.1/bin, so that
after installing rails and stuff I can use the programs that come with
them.

But please note that doing this might break other ruby stuff you have
installed, specially packaged applications that are not compatible with
ruby 1.9.1 and refer to "ruby" instead of "ruby1.8" in their shebangs.

--
Antonio Terceiro <terceiro@...>
http://softwarelivre.org/terceiro

signature.asc (205 bytes) Download Attachment

Ruby 1.9.1 and Rails

2009-10-31T12:37:16Z

I am trying to move my Squeeze box over to Ruby1.9.1 and Rails and am having a tough time finding information on how to proceed. I've install ruby1.9.1-full and pulled in rubygems1.9.1 from Sid but I still can't get Rails to work.

Are there any guides, walkthroughs or tutorials for moving a Debian system to Ruby 1.9.1? Has anyone tried to run Rails under 1.9.1 on Squeeze or am I the first? Is this even the correct list for this question?

Thanx!

--
Richard Hurt
CEO KangarooBox, LLC.
e: rnhurt@...
p: 502-298-5422
w: http://KangarooBox.com

[rnhurt.vcf]

NS caminho para Deus

2009-10-26T08:48:05Z

Olá, neste e-mail eu venho falar sobre as suas escolhas; Na vida a cada
instante você tem podido escolher o que ira fazer, e se for sábio, muitas
vezes pensa bem antes de escolher, pois sabe que uma má escolha pode trazer
péssimas consequências, pois a vida é assim, causa e efeito, ação e reação;
Existe coisas que ao você escolher bem ou não não vai fazer muita diferença,
tal como escolher o que comer no café da manhã, mas e quanto as decisões
vitais? As que podem ter consequências por toda a eternidade? Tem tomado a
escolha certa?

Marcos 16:16 Quem crer e for batizado será salvo; quem, porém, não crer será
condenado.

Atos 13:47 Porque o Senhor assim no-lo determinou: Eu te constituí para
luz dos gentios, a fim de que sejas para salvação até aos confins da terra.

Condenação, ou salvação, a qual tem escolhido?

Deus é santo, e importa que os que queiram agradar a Ele sejam santos
também.

1 Pedro 1:13 Portanto, cingindo os lombos do vosso entendimento, sede
sóbrios, e esperai inteiramente na graça que se vos ofereceu na revelação de
Jesus Cristo;
14 Como filhos obedientes, não vos conformando com as concupiscências
que antes havia em vossa ignorância;
15 Mas, como é santo aquele que vos chamou, sede vós também santos em
toda a vossa maneira de viver;
16 Porquanto está escrito: Sede santos, porque eu sou santo.

E ao seguir a santificação (a pratica da justiça) se consegue estar no
caminho da salvação.

Mateus 5:20Porque vos digo que, se a vossa justiça não exceder em muito a
dos escribas e fariseus, jamais entrareis no reino dos céus.

Deuteronômio 16.20 A justiça, somente a justiça seguirás; para que vivas, e
possuas em herança a terra que te dará o SENHOR teu Deus.

Provérbios 21.21 O que segue a justiça e a beneficência achará a vida, a
justiça e a honra.

Isaías 32.17 E o efeito da justiça será paz, e a operação da justiça,
repouso e segurança para sempre.

claro que existe o livre-arbítrio, você pode escolher entre estar com Deus
ou sem Ele. Mas escolhendo estar com Deus você também tem as vantagens de
estar com Ele,, mas pode escolher estar contra Ele também.
o livre arbítrio é poder decidir o que quer (entre as opções existentes), e
não criar um novo universo.
Se quer estar na luz, escolha a luz,se quer estar nas trevas, escolha as
trevas (mas é logico que nas trevas está a solidão e a amargura do abismo,
que é cheio de trevas; e na luz esta a abundancia de vida e alegria, pois a
verdadeira vida esta na luz)
....
mas veja.., tua boca também te deu livre arbítrio, você pode escolher entre
comer pão ou comer pedras, pois as duas passam pela garganta,, mas uma ira
lhe matar de fome, e outra ira lhe fazer viver,,, mas ainda assim você pode
escolher.
Voce acha ruim o fato de você escolher? você pode viver ou morrer. mas se
escolher morrer, então morre, se escolher viver então vive. a mesma coisa é
com a vida eterna, se escolher viver(paraíso) vive, se escolher
morrer(abismo) morre.
pra comer teu pão você tem que ir buscar o pão ou o dinheiro pra comprá-lo,
e então mastigá-lo, e assim só que você pode come-lo e viver. Se quiser
alimentar seu espirito para que ele tenha em si a vida eterna deve buscar a
fonte da vida eterna ;) que é o Criador da vida.

Ele tem nele a vida, se quiser busque-o, se não quiser, isso obviamente vai
lhe causar a morte(a do espirito). Por isso nem só de pão viverá o homem,
mas de toda palavra que sai da boca de Deus.
Jesus não é Deus, mas tem também em si a vida, ele é o pão que desceu do
céu,, ou seja, os ensinos que ele trouxe alimentam o espirito(pois ele
ensinou a pratica da justiça), e fazem os seguidores dos ensinos ter em si a
vida eterna também, e passarem de estar na morte de espirito para a
verdadeira vida, que é com Deus.

Por esses motivos venho até você para lhe incentivar a buscar estar com
aquele que verdadeiramente criou os céus e a terra e criou o sol e a lua e
as estrela; de maneira correta, ou seja, em justiça e santidade que são
frutos da verdade e obras da verdadeira luz.
neste site tem mais algumas informações a respeito:
www.caminhodoaltissimo.com/google

e se tiver duvida envie um e-mail com a sua pergunta que tentarei responder
:)
levi@...
Por favor, não veja essa mensagem como se fosse um spam, isso não tem
sentido comercial, eu não lhe pedi dinheiro e nem tentei lhe vender algo,
apenas me coloquei a disposição para ensinar e ajudar :)
Obrigado.
Mas caso tenha gostado da mensagem fique a vontade pra repassa-la para seus
contatos :)
Esta mensagem não tem o intuito de violar algum de seus direitos, caso não
queira receber mais mensagens minhas, apenas
retorne esta mensagem com o título no assunto "remover" para não receber
mais emails meus.

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

RFS: tokyocabinet-ruby

2009-10-22T13:28:56Z

Hi,

I am looking for a sponsor for my package "tokyocabinet-ruby".

* Package name : tokyocabinet-ruby
Version : 1.21-1
Upstream Author : Mikio Hirabayashi <mikio@...>
* URL : http://1978th.net/tokyocabinet/
* License : GNU Lesser General Public Licence
Section : libs

It builds these binary packages:
libtokyocabinet-ruby-doc - Documentation for Ruby Binding of Tokyo
Cabinet Database
libtokyocabinet-ruby1.8 - Ruby Binding of Tokyo Cabinet Database (ruby 1.8)
libtokyocabinet-ruby1.9 - Ruby Binding of Tokyo Cabinet Database (ruby 1.9)

The package appears to be lintian clean.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/t/tokyocabinet-ruby
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget
http://mentors.debian.net/debian/pool/main/t/tokyocabinet-ruby/tokyocabinet-ruby_1.21-1.dsc

I would be glad if someone uploaded this package for me.

Kind regards
Laurent

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Bug#548917: Please use alternatives system to manage the ruby symlink

2009-10-04T11:23:12Z

On 04/10/09 at 10:27 +0900, akira yamada / ?????? wrote:

> Hi,
>
> > The existing ruby package simply sticks a symlink into /usr/bin/ruby
> > to point to ruby1.8. I was surprised to find that this was not
> > using the alternatives system, so that you can manage this yourself.
>
> I have a rough idea about ruby* packages.
>
> ruby package:
> now:
> provides /usr/bin/ruby file
> depends on ruby1.8 package
> new:
> does not provides /usr/bin/ruby* file
> depends on latest version of ruby* packages
> (for current testing: Depends: ruby1.9.1 | ruby1.8 | jruby1.1 | ...
> for after squeeze?: Depends: ruby1.9.2 | jruby1.2 | ...)
> (description points out latest version of ruby* packges)
>
> ruby1.8 package:
> now:
> provides /usr/bin/ruby1.8 file
> no alternatives
> new:
> provides /usr/bin/ruby1.8 file (no change)
> alternatives for /usr/bin/ruby
>
> ruby1.9 package:
> now:
> provides /usr/bin/ruby1.9 file
> no alternatives
> new:
> provides /usr/bin/ruby1.9.0 file
> alternatives for /usr/bin/ruby/1.9 and /usr/bin/ruby
>
> ruby1.9.1 package:
> now:
> provides /usr/bin/ruby1.9.1 file
> no alternatives
> new:
> provides /usr/bin/ruby1.9.1 file (no change)
> alternatives for /usr/bin/ruby1.9 and /usr/bin/ruby
>
> I think that packages using Ruby language
> should not use /usr/bin/ruby in the above package design.
> (Users can use them freely of course.)
>
>
> Note: there are some software that
> don't depend on specified version/variant of Ruby.
> So it may be better to provide symlinks
> such as /usr/bin/ruby-compat-<compat-level>
> for compatibility.
> (Here comapt-level is "1.9.1" for Ruby 1.9.1 and 1.9.2.)
>
>
> Note2:
> I know that lucas have a new policy plan.
> And I think that we should have more time to discuss about it.
> During that time we should have small and minor update about current policy.
> I think the above idea is part of such minor updates.

Hi,

I agree with the plan to use alternatives. However, I fear that
switching to alternatives will break many ruby applications (packaged in
Debian) that use /usr/bin/ruby instead of /usr/bin/ruby1.8. So that
change isn't that minor, since we need to advertise that using
/usr/bin/ruby is not allowed unless your application is really
compatible with all ruby versions (that means that you need to depend on
libfoo-ruby1.8 and libfoo-ruby1.9, currently, too).

I think that the first step is really to provide a way for libraries to
support several ruby versions at the same time (so we can remove those
1.8, 1.9, 1.9.1 suffixes). That means something like ruby-support
(though I agree that we could discuss it more ; also, I don't have time
to work on it currently). Once this is done, it will be easier for
applications to support several ruby versions at the same time, so the
switch to alternatives will also be easier.

I'll try to talk to some people to see if they could work on
ruby-support themselves. Also, I've talked with a release team member,
and the plans for squeeze seems to be to freeze in february. We have to
decide whether we want to push things a lot, and do it before squeeze,
or postpone them and do them for squeeze+1.
--
| Lucas Nussbaum
| lucas@... http://www.lucas-nussbaum.net/ |
| jabber: lucas@... GPG: 1024D/023B3F4F |

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Bug#548917: Please use alternatives system to manage the ruby symlink

2009-10-03T18:27:18Z

Hi,

> The existing ruby package simply sticks a symlink into /usr/bin/ruby
> to point to ruby1.8. I was surprised to find that this was not
> using the alternatives system, so that you can manage this yourself.

I have a rough idea about ruby* packages.

ruby package:
now:
provides /usr/bin/ruby file
depends on ruby1.8 package
new:
does not provides /usr/bin/ruby* file
depends on latest version of ruby* packages
(for current testing: Depends: ruby1.9.1 | ruby1.8 | jruby1.1 | ...
for after squeeze?: Depends: ruby1.9.2 | jruby1.2 | ...)
(description points out latest version of ruby* packges)

ruby1.8 package:
now:
provides /usr/bin/ruby1.8 file
no alternatives
new:
provides /usr/bin/ruby1.8 file (no change)
alternatives for /usr/bin/ruby

ruby1.9 package:
now:
provides /usr/bin/ruby1.9 file
no alternatives
new:
provides /usr/bin/ruby1.9.0 file
alternatives for /usr/bin/ruby/1.9 and /usr/bin/ruby

ruby1.9.1 package:
now:
provides /usr/bin/ruby1.9.1 file
no alternatives
new:
provides /usr/bin/ruby1.9.1 file (no change)
alternatives for /usr/bin/ruby1.9 and /usr/bin/ruby

I think that packages using Ruby language
should not use /usr/bin/ruby in the above package design.
(Users can use them freely of course.)

Note: there are some software that
don't depend on specified version/variant of Ruby.
So it may be better to provide symlinks
such as /usr/bin/ruby-compat-<compat-level>
for compatibility.
(Here comapt-level is "1.9.1" for Ruby 1.9.1 and 1.9.2.)

Note2:
I know that lucas have a new policy plan.
And I think that we should have more time to discuss about it.
During that time we should have small and minor update about current policy.
I think the above idea is part of such minor updates.

--
ay

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: RFS packages for Capistrano

2009-09-12T02:00:34Z

On 11/09/09 at 19:08 -0400, Christopher Lunsford wrote:
> >Would it make sense to run the test suite during the build?
>
> The tests that I always see rely on too many gems beings installed so
> I have always opted out on running them. Should I not opt out on
> running tests? The other packages should be fixed in the latest
> revision in trunk. Again thank you for your time

libnet-sftp2-ruby uploaded.
libnet-scp-ruby uploaded.
libnet-ssh-gateway-ruby uploaded.
capistrano uploaded.

Thanks a lot for all the good work!
--
| Lucas Nussbaum
| lucas@... http://www.lucas-nussbaum.net/ |
| jabber: lucas@... GPG: 1024D/023B3F4F |

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: RFS packages for Capistrano

2009-09-11T16:08:41Z

>Would it make sense to run the test suite during the build?

The tests that I always see rely on too many gems beings installed so
I have always opted out on running them. Should I not opt out on
running tests? The other packages should be fixed in the latest
revision in trunk. Again thank you for your time

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: RFS packages for Capistrano

2009-09-09T02:12:52Z

On 25/08/09 at 17:51 -0400, Christopher Lunsford wrote:

> If anyone has the time to review and possibly upload the following
> packages I would be eternally grateful :D
> I packaged net-ssh2 and net-sftp2 because of the incompatibilities
> with prior versions.
>
> * Package name : libnet-ssh2-ruby
> Version : 2.0.13-1
> Upstream Author : Jamis Buck <jamis@...>
> * URL : http://net-ssh.rubyforge.org
> * License : MIT
> Section : ruby
> It builds these binary packages:
> libnet-ssh2-ruby - Ruby implementation of the SSH2 client protocol
> libnet-ssh2--ruby1.8 - Ruby implementation of the SSH2 client protocol
> libnet-ssh2-ruby1.9 - Ruby implementation of the SSH2 client protocol
> The package appears to be lintian clean.
> The upload would fix these bugs: 543302
> The package can be found on the pkg-ruby-extras SVN server:
> - URL: http://svn.debian.org/wsvn/pkg-ruby-extras/trunk/libnet-ssh2-ruby/

Uploaded.
Would it make sense to run the test suite during the build?

> * Package name : libnet-sftp2-ruby
> Version : 2.0.2-1
> Upstream Author : Jamis Buck <jamis@...>
> * URL : http://net-ssh.rubyforge.org
> * License : MIT
> Section : ruby
> It builds these binary packages:
> libnet-ssh2-ruby - Ruby implementation of the SFTP protocol
> libnet-ssh2--ruby1.8 - Ruby implementation of the SFTP protocol
> libnet-ssh2-ruby1.9 - Ruby implementation of the SFTP protocol
> The package appears to be lintian clean.
> The upload would fix these bugs: 543319
> The package can be found on the pkg-ruby-extras SVN server:
> - URL: http://svn.debian.org/wsvn/pkg-ruby-extras/trunk/libnet-sftp2-ruby/

Watch file broken

> * Package name : libnet-scp-ruby
> Version : 1.0.2-1
> Upstream Author : Jamis Buck <jamis@...>
> * URL : http://net-ssh.rubyforge.org
> * License : MIT
> Section : ruby
> It builds these binary packages:
> libnet-scp-ruby - pure ruby implementation of the SCP protocol
> libnet-scp--ruby1.8 - pure ruby implementation of the SCP protocol
> libnet-scp-ruby1.9 - pure ruby implementation of the SCP protocol
> The package appears to be lintian clean.
> The upload would fix these bugs: 500335
> The package can be found on the pkg-ruby-extras SVN server:
> - URL: http://svn.debian.org/wsvn/pkg-ruby-extras/trunk/libnet-scp-ruby/

Watch file broken? the downloaded tgz is empty.

> * Package name : libnet-ssh-gateway-ruby
> Version : 1.0.1-1
> Upstream Author : Jamis Buck <jamis@...>
> * URL : http://net-ssh.rubyforge.org
> * License : MIT
> Section : ruby
> It builds these binary packages:
> libnet-ssh-gateway-ruby - Ruby library for tunneling connections
> to servers with ssh
> libnet-ssh-gateway-ruby1.8 - Ruby library for tunneling connections to
> servers with ssh
> libnet-ssh-gateway-ruby1.9 - Ruby library for tunneling connections to
> servers with ssh
> The package appears to be lintian clean.
> The upload would fix these bugs: 500275
> The package can be found on the pkg-ruby-extras SVN server:
> - URL: http://svn.debian.org/wsvn/pkg-ruby-extras/trunk/libnet-ssh-gateway-ruby/

FTBFS:
if [ -f ./.config ]; then mv -f ./.config
./.config-libnet-ssh-gateway-ruby1.8; fi
dh_installdirs -plibnet-ssh-gateway-ruby1.9
if [ -f ./.config-libnet-ssh-gateway-ruby1.9 ]; then mv -f
./.config-libnet-ssh-gateway-ruby1.9 ./.config; fi
cd .
if [ ! -L debian-setup.rb ] ; then if [ -f debian-setup.rb ] ; then mv
debian-setup.rb debian-setup.rb.moved_away_by_debian_build ; fi ; ln -s
/usr/lib/ruby/1.8/setup.rb debian-setup.rb ; fi
/usr/bin/ruby1.9 debian-setup.rb config --installdirs=std
make: /usr/bin/ruby1.9: Command not found
make: *** [install/libnet-ssh-gateway-ruby1.9] Error 127
dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary gave
error exit status

Did you test in a clean chroot?

> * Package name : capistrano
> Version : 2.5.5-1
> Upstream Author : Jamis Buck <jamis@...>
> * URL : http://www.capify.org
> * License : MIT
> Section : ruby
> It builds these binary packages:
> capistrano - execute commands in parallel on multiples servers
> The package appears to be lintian clean.
> The upload would fix these bugs: 500275
> The package can be found on the pkg-ruby-extras SVN server:
> - URL: http://svn.debian.org/wsvn/pkg-ruby-extras/trunk/capistrano/

Can't be uploaded without the others.
--
| Lucas Nussbaum
| lucas@... http://www.lucas-nussbaum.net/ |
| jabber: lucas@... GPG: 1024D/023B3F4F |

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Hi from Portugal!

2009-08-26T12:22:53Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi folks!

I'm Marco Rodrigues and I live in Portugal. I subscribed to be a member of Debian-Ruby, because I
want to participate more in Debian Ruby to have more packages in good shape and try to collaborate
with the team to update them. First of all, I need to learn about Debian Ruby packaging.

I'm not an Ruby hardcore programmer. I just have done some Ruby on Rails little website and some
small Ruby hacking in Debian QA (hi lucas :-p), nothing special :)

Let's hope we can improve Ruby on Debian and it's derivatives distributions.

Thank you

- --
Marco Rodrigues

http://Marco.Tondela.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQIcBAEBCAAGBQJKlYuNAAoJENDqNB6bSPIzIYcQAMBW4t10/HQCMmTzhBHmqNc7
967CJ2tat6+yWcyBrOMLKzx4z9Xy2eybtU36ARbDW3PpRqH19jiNYOhdHxhnvyMf
sbAK2YrDqYdOYRIgHE2zAMmS975TghtzNhQzef3NSYegOTvcf6BUcoCy3cvHtneQ
RWwuSgryvuW/d8zimULPip8FR1aiyS/H/HkUp70sfxOslKzgt4c8qFm+GSvb94P2
3ui8j8WnvhdzR/AqQHeY2akTH5+pugHP60iElz9P/EoI2Q7g/u/V6uy+VYLKiFa4
9meqtfIrCf4Q/CSuLHBjwAtSZwrey+CF3z7WBAKd4nwQbbAyyG8wcNKe0xiRkwm8
l7/X034SHLmsyO6olXQDiKtcYI9XFXpZxiV8K3ChuLwRy4MqVe2SwJ3M0r124Syl
g9K0Elldgz4DfhdE7i5eAIqEK4iy9GqybgxpasO8+e0gJ2nKZWV10e3/PAYYo+px
Afh3LK56xQdepHdKZ75yYm5hFhxrwXhYnCArPq9HFRgWBMSR54HVuYE+qMlWRsSl
/yegqOZn+J7QZHlfhOEK5sIwiRw3QfNCEBA28HpED5XehQpz7t2UBJLDtAAfqcKn
sGlsNb40oFX5LiRHdZat3HxcL+p5dtqQxObAaSKqOKiP7tPlbNz67mz2n71Rn2O1
F64JNrq+DMfJUBu9Bggw
=Zghc
-----END PGP SIGNATURE-----

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

RFS packages for Capistrano

2009-08-25T14:51:22Z

If anyone has the time to review and possibly upload the following
packages I would be eternally grateful :D
I packaged net-ssh2 and net-sftp2 because of the incompatibilities
with prior versions.

* Package name : libnet-ssh2-ruby
Version : 2.0.13-1
Upstream Author : Jamis Buck <jamis@...>
* URL : http://net-ssh.rubyforge.org
* License : MIT
Section : ruby
It builds these binary packages:
libnet-ssh2-ruby - Ruby implementation of the SSH2 client protocol
libnet-ssh2--ruby1.8 - Ruby implementation of the SSH2 client protocol
libnet-ssh2-ruby1.9 - Ruby implementation of the SSH2 client protocol
The package appears to be lintian clean.
The upload would fix these bugs: 543302
The package can be found on the pkg-ruby-extras SVN server:
- URL: http://svn.debian.org/wsvn/pkg-ruby-extras/trunk/libnet-ssh2-ruby/

* Package name : libnet-sftp2-ruby
Version : 2.0.2-1
Upstream Author : Jamis Buck <jamis@...>
* URL : http://net-ssh.rubyforge.org
* License : MIT
Section : ruby
It builds these binary packages:
libnet-ssh2-ruby - Ruby implementation of the SFTP protocol
libnet-ssh2--ruby1.8 - Ruby implementation of the SFTP protocol
libnet-ssh2-ruby1.9 - Ruby implementation of the SFTP protocol
The package appears to be lintian clean.
The upload would fix these bugs: 543319
The package can be found on the pkg-ruby-extras SVN server:
- URL: http://svn.debian.org/wsvn/pkg-ruby-extras/trunk/libnet-sftp2-ruby/

* Package name : libnet-scp-ruby
Version : 1.0.2-1
Upstream Author : Jamis Buck <jamis@...>
* URL : http://net-ssh.rubyforge.org
* License : MIT
Section : ruby
It builds these binary packages:
libnet-scp-ruby - pure ruby implementation of the SCP protocol
libnet-scp--ruby1.8 - pure ruby implementation of the SCP protocol
libnet-scp-ruby1.9 - pure ruby implementation of the SCP protocol
The package appears to be lintian clean.
The upload would fix these bugs: 500335
The package can be found on the pkg-ruby-extras SVN server:
- URL: http://svn.debian.org/wsvn/pkg-ruby-extras/trunk/libnet-scp-ruby/

* Package name : libnet-ssh-gateway-ruby
Version : 1.0.1-1
Upstream Author : Jamis Buck <jamis@...>
* URL : http://net-ssh.rubyforge.org
* License : MIT
Section : ruby
It builds these binary packages:
libnet-ssh-gateway-ruby - Ruby library for tunneling connections
to servers with ssh
libnet-ssh-gateway-ruby1.8 - Ruby library for tunneling connections to
servers with ssh
libnet-ssh-gateway-ruby1.9 - Ruby library for tunneling connections to
servers with ssh
The package appears to be lintian clean.
The upload would fix these bugs: 500275
The package can be found on the pkg-ruby-extras SVN server:
- URL: http://svn.debian.org/wsvn/pkg-ruby-extras/trunk/libnet-ssh-gateway-ruby/

* Package name : capistrano
Version : 2.5.5-1
Upstream Author : Jamis Buck <jamis@...>
* URL : http://www.capify.org
* License : MIT
Section : ruby
It builds these binary packages:
capistrano - execute commands in parallel on multiples servers
The package appears to be lintian clean.
The upload would fix these bugs: 500275
The package can be found on the pkg-ruby-extras SVN server:
- URL: http://svn.debian.org/wsvn/pkg-ruby-extras/trunk/capistrano/

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Férias em Santa Catarina à Beira Mar - Descontos

2009-08-24T15:49:37Z

Férias de fim de ano na Pousada Pedra da Ilha

Problemas para visualizar a mensagem? Acesse este link.

IMPERDÍVEL
Natal, Reveillon, Janeiro, Carnaval

Passe suas férias em Santa Catarina, um estado paradisíaco, curtindo o sol, a praia e o mar, aproveitando a mega estrutura do maior parque temático da América Latina, o BETO CARRERO WORLD, tudo isso à beira-mar, sossego e conforto na POUSADA PEDRA DA ILHA, em Penha.

Preço Especial
No mês de agosto, adquirindo o Pacote de Natal, Reveillon, Carnaval e mínimo de 7 diárias em janeiro, você ganha um desconto de 15%, em até 10 vezes no cartão.

O que oferecemos
Localização privilegiada, próxima das principais cidades do estado, duas piscinas externas e uma interna aquecida com duas spa's família, quiosques, serviços na praia e piscinas, guarda sóis, toalhas, bar, café da manhã climatizado e vista do mar, living em madeira com vários ambientes, apartamentos finamente decorados e suítes temáticas, estacionamento fechado.

Aproveite essa grande oportunidade!
acesse o nosso site e saiba mais.

Rua Abraão João Francisco, n° 46 • Praia Alegre, Penha • Santa Catarina
Fone/Fax: 47 3345.0542 • 47 9652.3797
www.pedradailha.com.br • pousada@...

Não deseja mais receber nossas mensagens? Cancele o recebimento aqui.

Re: pkg-ruby-extras SVN reorganized to layout 2

2009-08-10T07:00:40Z

Lucas Nussbaum dijo [Sat, Aug 08, 2009 at 06:32:14PM +0200]:

> I've just finished reorganizing the pkg-ruby-extras SVN to layout 2. The
> big benefit is that now, you can checkout only trunk/, which contains
> the current version of all packages, without having to checkout all
> tags.
>
> To transition your local copy, just svn update. It might also be a good
> idea to remove all 'deb-layout' files, to let svn-buildpackage
> auto-detect them again:
> find . -name 'deb-layout' -exec rm {} \+
> should do the trick.

Yay!

I owe you a (yet another?) ${prefered_drink}, to be paid in New York
next year.

Good job!

--
Gunnar Wolf • gwolf@... • (+52-55)5623-0154 / 1451-2244

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: [DRE-maint] Rubygems

2009-08-10T06:51:36Z

Lucas Nussbaum dijo [Tue, Jul 28, 2009 at 11:01:07AM +0200]:
> (Added a Cc on debian-ruby@..., some interested people
> might not be subscribed to pkg-ruby-maintainers)

(And following the list usage policy we have just been discussing, I
dropped pkg-ruby-maintainers ;-) )

> Hi,
>
> First, thank you for contacting us on that topic.

I must also thank you, Yehuda. We _do_ need to work closer to our
upstream community, and strongly welcome you!

> > 2) You want a simple way to install packages without needing the full
> > rubygems. To be honest, while you can appeal to the community to provide
> > setup.rb, it would in fact be easier for us to provide you with a tiny
> > subset of rubygems that can help you extract the installation information
> > from the gem specification. You can then find the bin directories, as well
> > as instructions for installing any binary gems. This will enable you to
> > install the parts of the gem where you want, and make it trivial to make
> > debian packages from rubygems. I would be willing to write something that
> > could serve as the base for a Rubygems=>Debian package converter if one does
> > not already exist.
>
> The point of setup.rb is that it enforces a layout that is sane. Of
> course, the same could be achieved by looking into the gem specification
> to extract the relevant info, as you suggested. I'm not very familiar
> with rubygems, but I have the impression that this solution might not
> apply to all current gems: it will still require a special organization
> of the files inside the gem to work. Can you give an example of the
> information from the gem spec that we will be able to use?

FWIW, in most cases what our group does is to drop a known-good
version of setup.rb in the build directory at build time, and it (most
often) works as it should. However, there are several examples where
setup.rb must be hand-helped to do the right thing (and even there, I
am not sure if my hand-helping is correct). As an example:

http://svn.debian.org/wsvn/pkg-ruby-extras/trunk/libprawn-ruby/debian/rules

Disregard the portion where I discard a bunch of images (as they are
not DFSG-free) and ensure they stay discarded by comparing their MD5s
to my files'; what I am doing in this debian/rules file (which is the
instructions to build the Debian packages) is:

• In the clean and makebuilddir targets, I deal with ttfunk and pdf,
modules developed by the same author but under separate
repositories, which he explicitly requested me _not_ to ship as
separate packages; fortunately, it is enough to drop a link from
lib/ to ../vendor/ and setup.rb will do the right thing.

• Fonts and common files which do not really belong to either the 1.8
or the 1.9 packages (and which would cause conflicts if
simultaneously installed) are moved to a third package in which both
depend: libprawn-ruby-common. This is ugly, but the best way I could
work out.

FWIW, after talking with Lucas during DebConf9, there is huge hope
for simplification here, as we will most probably be moving to a
model where Ruby revisions will not have to be specified as part of
the binary package names... So things will be easier then :)

> > I understand that in a perfect world the Ruby community would conform with
> > Debian's desires here. In practice though, I think we can work toward a
> > solution that works for both communities with minimal fuss. I'm also
> > probably not the first person who's attempted this dialog. Some in the Ruby
> > community have decided to effectively write off Debian but I'm not willing
> > to do so.
>
> Well, I tried to start this conversation some time ago, and then decided
> to stay away from this topic as much as possible, since several
> "poisonous people" in the Ruby community (like Austin Ziegler) totally
> discouraged me from continuing. But we can try again, of course.

Yes, same experience over here, although I am more active among
Railsers and Lucas is a straight Rubyist. I have voiced some times the
needs we have¹, and got all kinds of results from the Ruby community -
including some very positive collaboration (such as the DebGem one²).

¹ http://gwolf.org/blog/its-just-different-mindset-not-necessarily-sane-one-though
http://gwolf.org/blog/apt-get-and-gems-different-planets-right-it-must-not-be-war-worlds
http://gwolf.org/blog/ruby-has-distribution-problem
http://gwolf.org/debian%20rails

² http://gwolf.org/blog/debgem-its-way

--
Gunnar Wolf • gwolf@... • (+52-55)5623-0154 / 1451-2244

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: pkg-ruby-extras-maintainers@ -> debian-ruby@?

2009-08-10T06:16:15Z

Lucas Nussbaum dijo [Thu, Aug 06, 2009 at 05:16:15PM +0200]:

> Hi,
>
> OK, let's do the following:
> - pkg-ruby-maintainers@:
> + Maintainer/Uploaders: field
> + machine-generated emails (dak, etc) about packages
> + short discussions about package-specific issues, especially when they
> originate from a machine-generated email. If they generalize, they
> should be moved to debian-ruby@
> - debian-ruby@:
> + the 'default' list for discussions about ruby packaging in Debian
> + RFS, messages from new team members, etc.
>
> Of course, every team member should be subscribed to both lists, so
> cross-posting is useless and discouraged.

Fully agree with you. And we should make explicit that we are all
encouraged to be subscribed to p-r-m in order not to miss the bug
reports or any important system announcements - although separating
them in mailboxes will be easier.

Greetings!

--
Gunnar Wolf • gwolf@... • (+52-55)5623-0154 / 1451-2244

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: pkg-ruby-extras-maintainers@ -> debian-ruby@?

2009-08-09T05:18:20Z

Lucas Nussbaum wrote:

> OK, let's do the following:
> - pkg-ruby-maintainers@:
> + Maintainer/Uploaders: field
> + machine-generated emails (dak, etc) about packages
> + short discussions about package-specific issues, especially when they
> originate from a machine-generated email. If they generalize, they
> should be moved to debian-ruby@
> - debian-ruby@:
> + the 'default' list for discussions about ruby packaging in Debian
> + RFS, messages from new team members, etc.
>
> Of course, every team member should be subscribed to both lists, so
> cross-posting is useless and discouraged.
>
> Does someone object to the above?

This is perfect for me. And to exemplify the above, I'm dropping
pkg-ruby in the reply ;-)...

Vincent

--
Vincent Fourmond, Debian Developer
http://vince-debian.blogspot.com/

I have always wished for my computer to be as easy to use as my
telephone; my wish has come true because I can no longer figure out
how to use my telephone.
-- Bjarne Stroustrup

Vincent, not listening to anything for now

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: pkg-ruby-extras SVN reorganized to layout 2

2009-08-08T12:55:48Z

Awesome, thank you :)

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

pkg-ruby-extras SVN reorganized to layout 2

2009-08-08T09:32:14Z

Hi,

I've just finished reorganizing the pkg-ruby-extras SVN to layout 2. The
big benefit is that now, you can checkout only trunk/, which contains
the current version of all packages, without having to checkout all
tags.

To transition your local copy, just svn update. It might also be a good
idea to remove all 'deb-layout' files, to let svn-buildpackage
auto-detect them again:
find . -name 'deb-layout' -exec rm {} \+
should do the trick.

The tools/ and website/ dirs have also been moved to trunk/.
--
| Lucas Nussbaum
| lucas@... http://www.lucas-nussbaum.net/ |
| jabber: lucas@... GPG: 1024D/023B3F4F |

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: [DRE-maint] pkg-ruby-extras-maintainers@ -> debian-ruby@?

2009-08-07T01:44:27Z

On Thu, Aug 06, 2009 at 05:16:15PM +0200, Lucas Nussbaum wrote:

Actually, that almost how I was doing it already. So, no
objections here!

Paul

--
PhD Student @ Eindhoven | email: paulvt@...
University of Technology, The Netherlands | JID: paul@...
>>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: pkg-ruby-extras-maintainers@ -> debian-ruby@?

2009-08-06T08:16:15Z

Hi,

OK, let's do the following:
- pkg-ruby-maintainers@:
+ Maintainer/Uploaders: field
+ machine-generated emails (dak, etc) about packages
+ short discussions about package-specific issues, especially when they
originate from a machine-generated email. If they generalize, they
should be moved to debian-ruby@
- debian-ruby@:
+ the 'default' list for discussions about ruby packaging in Debian
+ RFS, messages from new team members, etc.

Of course, every team member should be subscribed to both lists, so
cross-posting is useless and discouraged.

Does someone object to the above?

- Lucas

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: packaging of phusion passenger?

2009-08-04T13:24:54Z

On Tue, Aug 04, 2009 at 01:20:10PM -0700, Ryan Niebur wrote:
>
> there's already an ITP, and people have already uploaded it during
> debconf. it's being maintained inside of DRE.

So there is. I managed to miss it when looking previously...

Thanks
noah

signature.asc (196 bytes) Download Attachment

Re: packaging of phusion passenger?

2009-08-04T13:20:10Z

On Tue, Aug 04, 2009 at 03:52:33PM -0400, Noah Meyerhans wrote:
> Has anybody put any effort into packaging phusion passenger yet? It's
> got some rake rules to generate a .deb file from upstream source, but
> the result isn't something I'd consider distributing. I'm working on
> improving the packaging of passenger for work, and was wondering if it's
> worth filing an ITP.
>

there's already an ITP, and people have already uploaded it during
debconf. it's being maintained inside of DRE.

--
_________________________
Ryan Niebur
ryanryan52@...

signature.asc (204 bytes) Download Attachment

packaging of phusion passenger?

2009-08-04T12:52:33Z

Has anybody put any effort into packaging phusion passenger yet? It's
got some rake rules to generate a .deb file from upstream source, but
the result isn't something I'd consider distributing. I'm working on
improving the packaging of passenger for work, and was wondering if it's
worth filing an ITP.

noah

signature.asc (196 bytes) Download Attachment

Re: pkg-ruby-extras-maintainers@ -> debian-ruby@?

2009-08-03T15:40:30Z

Vincent Fourmond dijo [Mon, Aug 03, 2009 at 09:23:22PM +0200]:

> Hmmm. No. Unless I completely misunderstood Lucas's post (which is
> very possible, I have basic understanding problems ;-)...), what Lucas
> proposes is to drop pkg-ruby-extras-maintainers altogether. To this I
> strongly object.
>
> See the quotation from <20090729082834.GC28178@...>
>
> Lucas's initial proposition:
> > The ruby-extras team currently uses pkg-ruby-extras-maintainers as
> > Maintainer: or Uploaders:. I find it annoying to have two Debian/Ruby
> > lists, which often requires adding Ccs between the list.
> >
> > I think that we should switch to using only debian-ruby@ for everything
> > except commit logs (which go to pkg-ruby-extras-commits@). This matches
> > what the perl team does, and it seems to be totally bearable even for
> > bigger teams.
>
> Unless I'm very wrong, that means dropping pkg-ruby-extras-maintainers
> ? Could you clarify, please, Lucas, if you're around ?

That would be terribly burdensome(?), to say the least. It is the main
maintainer contact address for most of our packages. However, moving
all human discussion to one cleaner, easily followable list
(debian-ruby) and leaving machine-generated mails on the other is a
clear win for me. Of course, I will set some filters up to pick up
anything not coming from the usual suspects (DEHS, Dak et al) in _my_
copy of the lists from pkg-ruby-extras-blah to the human one because,
as you say, users might write directly to it. But for _archival_ and
discussion purposes, it's best.

--
Gunnar Wolf â¢ gwolf@... â¢ (+52-55)5623-0154 / 1451-2244

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: pkg-ruby-extras-maintainers@ -> debian-ruby@?

2009-08-03T12:23:22Z

Gunnar Wolf wrote:

> Vincent Fourmond dijo [Sun, Aug 02, 2009 at 10:26:14PM +0200]:
>>> I think that we should switch to using only debian-ruby@ for everything
>>> except commit logs (which go to pkg-ruby-extras-commits@). This matches
>>> what the perl team does, and it seems to be totally bearable even for
>>> bigger teams.
> Umm… That is precisely what Lucas is suggesting :-}
>
> The current situation is that we have two lists (debian-ruby@...
> and pkg-ruby-extras-maintainers@...). The first list is
> for «Discussion of issues related to Ruby on Debian systems with a
> stress on packaging standards. Therefore relevant for maintainers of
> Ruby related packages.»¹. The second one is for «Maintainers of the
> Debian Ruby Extras packages». There is a clear overlap here, as I have
> often seen pkg-ruby-extras discussions in the second, but those
> discussions are quite relevant to Ruby packaging maintainers outside
> our group. Even more, I realized I was not even subscribed to the
> first one!

Hmmm. No. Unless I completely misunderstood Lucas's post (which is
very possible, I have basic understanding problems ;-)...), what Lucas
proposes is to drop pkg-ruby-extras-maintainers altogether. To this I
strongly object.

See the quotation from <20090729082834.GC28178@...>

Lucas's initial proposition:
> The ruby-extras team currently uses pkg-ruby-extras-maintainers as
> Maintainer: or Uploaders:. I find it annoying to have two Debian/Ruby
> lists, which often requires adding Ccs between the list.
>
> I think that we should switch to using only debian-ruby@ for everything
> except commit logs (which go to pkg-ruby-extras-commits@). This matches
> what the perl team does, and it seems to be totally bearable even for
> bigger teams.

Unless I'm very wrong, that means dropping pkg-ruby-extras-maintainers
? Could you clarify, please, Lucas, if you're around ?

> So, basically, we are suggesting moving most, if not all, human
> interaction to debian-ruby (which is also way easier on the eyes), and
> leave the pkg-ruby-extras group one for dak announcement and bug
> reports. Of course, the group members are expected to be in both, but
> they can be sent to different folders - and we will not get so lost
> regarding human discussions (which matter most).

For me, this is perfect.

The main problem is the following: sometime users write directly to
pkg-ruby-extras-maintainers, and they expect an answer. Maybe a proper
footer to the list would help ?

Cheers,

Vincent

--
Vincent Fourmond, Debian Developer
http://vince-debian.blogspot.com/

The moon was high now, in a sky as black as a cup of coffee that
wasn't very black at all.
-- Terry Pratchet, Men at arms

Vincent, listening to Fin de Siecle (Noir Desir)

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: pkg-ruby-extras-maintainers@ -> debian-ruby@?

2009-08-02T14:56:28Z

On Wed, Jul 29, 2009 at 10:28:34AM +0200, Lucas Nussbaum wrote:

> Hi,
>
> The ruby-extras team currently uses pkg-ruby-extras-maintainers as
> Maintainer: or Uploaders:. I find it annoying to have two Debian/Ruby
> lists, which often requires adding Ccs between the list.
>
> I think that we should switch to using only debian-ruby@ for everything
> except commit logs (which go to pkg-ruby-extras-commits@). This matches
> what the perl team does, and it seems to be totally bearable even for
> bigger teams.
>

no, this doesn't match what the Perl team does. what we currently have
matches the Perl team.
pkg-perl-maintainers@... is in Maintainer:
debian-perl@... is for discussion and stuff.
then we have some other commit list that I don't know the email
address of..

this doesn't change my opinion about combining debian-ruby and
pkg-ruby-extras-maintainers. tho I guess it does make sense to have
them separate for people who don't want bug reports and such...it does
seem like we do a lot more cross posting than the Perl group tho, not
sure why this happens...

--
_________________________
Ryan Niebur
ryanryan52@...

signature.asc (204 bytes) Download Attachment

Re: pkg-ruby-extras-maintainers@ -> debian-ruby@?

2009-08-02T13:26:14Z

Hello !

Lucas Nussbaum wrote:
> I think that we should switch to using only debian-ruby@ for everything
> except commit logs (which go to pkg-ruby-extras-commits@). This matches
> what the perl team does, and it seems to be totally bearable even for
> bigger teams.
>
> What do you think?

I don't like so much the idea. I can kinda follow debian-ruby. I just
accidentally read pkg-ruby-extra. I'm not interested in dak announcement
and bug reports of packages I don't maintain.

What is done in debian-java is the following - just like what was done
more or less here so far:

- general discussion on debian-java
- package-specific stuff on pkg-java, unless it needs wider attention,
in which case debian-java is the place to go.

This makes a clear distinction between both lists by potential
interest. I would sincerely wish to keep it like that. Maybe what is
missing is simply a clear statement in this way, on the pkg-ruby-extra
web page (or any other reference place), or maybe even on the
pkg-ruby-extra-maintainers@... footers.

What do you think about that ?

Of course, if the group prefer everything on debian-ruby, I'd give in
;-)...

Cheers,

Vincent

--
Vincent Fourmond, Debian Developer
http://vince-debian.blogspot.com/

find(1):
A `%' at the end of the format argument causes undefined behaviour
since there is no following character. In some locales, it may
hide your door keys, while in others it may remove the final page
from the novel you are reading.

Vincent, listening to Curly Headed Baby (Doc Watson)

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: [DRE-maint] pkg-ruby-extras-maintainers@ -> debian-ruby@?

2009-07-30T02:36:31Z

Micah Anderson dijo [Wed, Jul 29, 2009 at 04:49:08AM -0400]:

> > > The ruby-extras team currently uses pkg-ruby-extras-maintainers as
> > > Maintainer: or Uploaders:. I find it annoying to have two Debian/Ruby
> > > lists, which often requires adding Ccs between the list.
> > >
> > > I think that we should switch to using only debian-ruby@ for everything
> > > except commit logs (which go to pkg-ruby-extras-commits@). This matches
> > > what the perl team does, and it seems to be totally bearable even for
> > > bigger teams.
> > >
> > > What do you think?
> >
> > +1
>
> +3

*1.3055

--
Gunnar Wolf • gwolf@... • (+52-55)5623-0154 / 1451-2244

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: [DRE-maint] pkg-ruby-extras-maintainers@ -> debian-ruby@?

2009-07-29T01:49:08Z

* Ryan Niebur <ryanryan52@...> [2009-07-29 04:35-0400]:

> On Wed, Jul 29, 2009 at 10:28:34AM +0200, Lucas Nussbaum wrote:
> > Hi,
> >
> > The ruby-extras team currently uses pkg-ruby-extras-maintainers as
> > Maintainer: or Uploaders:. I find it annoying to have two Debian/Ruby
> > lists, which often requires adding Ccs between the list.
> >
> > I think that we should switch to using only debian-ruby@ for everything
> > except commit logs (which go to pkg-ruby-extras-commits@). This matches
> > what the perl team does, and it seems to be totally bearable even for
> > bigger teams.
> >
> > What do you think?
>
> +1

signature.asc (852 bytes) Download Attachment

Re: pkg-ruby-extras-maintainers@ -> debian-ruby@?

2009-07-29T01:35:15Z

On Wed, Jul 29, 2009 at 10:28:34AM +0200, Lucas Nussbaum wrote:

+1

--
_________________________
Ryan Niebur
ryanryan52@...

signature.asc (204 bytes) Download Attachment

pkg-ruby-extras-maintainers@ -> debian-ruby@?

2009-07-29T01:28:34Z

Hi,

The ruby-extras team currently uses pkg-ruby-extras-maintainers as
Maintainer: or Uploaders:. I find it annoying to have two Debian/Ruby
lists, which often requires adding Ccs between the list.

I think that we should switch to using only debian-ruby@ for everything
except commit logs (which go to pkg-ruby-extras-commits@). This matches
what the perl team does, and it seems to be totally bearable even for
bigger teams.

What do you think?
--
| Lucas Nussbaum
| lucas@... http://www.lucas-nussbaum.net/ |
| jabber: lucas@... GPG: 1024D/023B3F4F |

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: [DRE-maint] Rubygems

2009-07-28T02:01:07Z

(Added a Cc on debian-ruby@..., some interested people
might not be subscribed to pkg-ruby-maintainers)

Hi,

First, thank you for contacting us on that topic.

On 28/07/09 at 00:56 -0700, Yehuda Katz wrote:

> Hey guys,
> I recently read your position on Rubygems. I think we can probably find a
> way to solve the problem if we can get some help from Debian.
>
> It seems to me like you have the following problems:
>
> 1) People have libraries that rely on Rubygems. I agree with this issue:
> http://yehudakatz.com/2009/07/24/rubygems-good-practice/
>
> 2) You want a simple way to install packages without needing the full
> rubygems. To be honest, while you can appeal to the community to provide
> setup.rb, it would in fact be easier for us to provide you with a tiny
> subset of rubygems that can help you extract the installation information
> from the gem specification. You can then find the bin directories, as well
> as instructions for installing any binary gems. This will enable you to
> install the parts of the gem where you want, and make it trivial to make
> debian packages from rubygems. I would be willing to write something that
> could serve as the base for a Rubygems=>Debian package converter if one does
> not already exist.

The point of setup.rb is that it enforces a layout that is sane. Of
course, the same could be achieved by looking into the gem specification
to extract the relevant info, as you suggested. I'm not very familiar
with rubygems, but I have the impression that this solution might not
apply to all current gems: it will still require a special organization
of the files inside the gem to work. Can you give an example of the
information from the gem spec that we will be able to use?

> 3) Rubygems binaries have shebang lines that don't work on Debian or none at
> all. This is because Rubygems creates a wrapper file that points directly at
> the binary with the appropriate shebang. A rubygems=>deb converter could use
> the same technique and then stash the binary anywhere it wished. It could
> also copy the contents of the file out and replace or add the appropriate
> shebang. I'd note that /usr/bin/env ruby does not work on Windows and is
> therefore not considered a general purpose solution.

That problem is really not a severe problem (contrary to (1) and (2)).
Also, in the future, we might push (inside Debian) for a change from
/usr/bin/env ruby to /usr/bin/ruby1.{8,9,9.1}, so that it is written in
stone that one application wants to use a specific ruby version (and was
not tested/would not work with another ruby version).

> I understand that in a perfect world the Ruby community would conform with
> Debian's desires here. In practice though, I think we can work toward a
> solution that works for both communities with minimal fuss. I'm also
> probably not the first person who's attempted this dialog. Some in the Ruby
> community have decided to effectively write off Debian but I'm not willing
> to do so.

Well, I tried to start this conversation some time ago, and then decided
to stay away from this topic as much as possible, since several
"poisonous people" in the Ruby community (like Austin Ziegler) totally
discouraged me from continuing. But we can try again, of course.
--
| Lucas Nussbaum
| lucas@... http://www.lucas-nussbaum.net/ |
| jabber: lucas@... GPG: 1024D/023B3F4F |

--
To UNSUBSCRIBE, email to debian-ruby-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...