Re: RFS: ruby-*

[Georg Faerber]

On 19-08-28 10:07:34, Utkarsh Gupta wrote:
> I did complete fixing the pending test failures (as an attempt to
> enable tests in all the packages), thus requesting you to review and
> upload the same (since they are NEW).
> 
> ruby-benchmark-memory
> ruby-ammeter
> ruby-arbre (thanks to terceiro :D)

I'll do this within the next hours.

Re: RFS: ruby-*

[Georg Faerber]

Hi,

On 19-08-28 10:07:34, Utkarsh Gupta wrote:
> ruby-benchmark-memory

Doesn't build for me, the last log lines read:

Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...
Initializing package states...
Writing extended state information...
Building tag database...
(I)StdLoaders: Parsing and normalizing...
(I)Packages: Parsing Packages file -...
(I)Format822: total packages 59697
(I)Distcheck: Cudf Universe: 59697 packages
(I)Distcheck: --checkonly specified, consider all packages as background 
packages
(I)Distcheck: Solving...
output-version: 1.2
native-architecture: amd64
report:
 -
  package: sbuild-build-depends-main-dummy
  version: 0.invalid.0
  architecture: amd64
  status: broken
  reasons:
   -
missing:
 pkg:
  package: sbuild-build-depends-main-dummy
  version: 0.invalid.0
  architecture: amd64
  unsat-dependency: ruby-memory-profiler:amd64 (>= 0.9)
 
background-packages: 59696
foreground-packages: 1
total-packages: 59697
broken-packages: 1

I didn't looked further.

> ruby-ammeter

This looks good in principle, just two minor nitpicks, and a general question:

- Testsuite: autopkgtest-pkg-ruby in debian/control is obsolete.
- The current version of debian/watch is 4.

Is this software still maintained? The last commit was done in 2016, and also
the issue tracker doesn't seem that active. If you're positive about this, I'm
happy to do the upload.

> ruby-arbre (thanks to terceiro :D)

Looks good, except:
- Testsuite: autopkgtest-pkg-ruby in debian/control is obsolete.
- Please run wrap-and-sort on debian/control.
- The description contains just two sentences, both of which are repeated.
  Could you fix this, and probably extend the description a bit?

Once done, I'm happy to do the upload.
 
Thanks for your work,
cheers,
Georg

Re: RFS: ruby-*

[Antonio Terceiro]

On Wed, Aug 28, 2019 at 01:25:15PM +, Georg Faerber wrote:
> - Testsuite: autopkgtest-pkg-ruby in debian/control is obsolete.

What's obsolete/unnecessary is `Testsuite: autopkgtest`, when you have
debian/tests/control, because dpkg-source will add `Testsuite:
autopkgtest` for you.

Any other value of `Testsuite:`, including but not limited  to
`autopkgtest-pkg-ruby`, is definitively not obsolete.


signature.asc
Description: PGP signature

Re: RFS: ruby-*

[Georg Faerber]

On 19-08-28 11:06:07, Antonio Terceiro wrote:
> What's obsolete/unnecessary is `Testsuite: autopkgtest`, when you have
> debian/tests/control, because dpkg-source will add `Testsuite:
> autopkgtest` for you.
> 
> Any other value of `Testsuite:`, including but not limited  to
> `autopkgtest-pkg-ruby`, is definitively not obsolete.

Thanks for your mail Antonio; seems I mixed stuff.
Sorry for the noise, Utkarsh!

Re: RFS: ruby-*

[Utkarsh Gupta]

Hey,

On 28/08/19 6:55 pm, Georg Faerber wrote:
> Hi,
>
> On 19-08-28 10:07:34, Utkarsh Gupta wrote:
>> ruby-benchmark-memory
> Doesn't build for me, the last log lines read:
>
> missing:
>  pkg:
>   package: sbuild-build-depends-main-dummy
>   version: 0.invalid.0
>   architecture: amd64
>   unsat-dependency: ruby-memory-profiler:amd64 (>= 0.9)
>
> I didn't looked further.

That is because ruby-memory-profiler[1] was uploaded a couple of days
back (thus not in the archive yet).
You can either pass it's deb (after building locally to check that
everything's fine) or you can rely on me here :)

>> ruby-ammeter
> This looks good in principle, just two minor nitpicks, and a general question:
>
> - Testsuite: autopkgtest-pkg-ruby in debian/control is obsolete.
> - The current version of debian/watch is 4.
>
> Is this software still maintained? The last commit was done in 2016, and also
> the issue tracker doesn't seem that active. If you're positive about this, I'm
> happy to do the upload.

Hah, doing the manual editing of version=4 is a little pain.
Fixed here. Should be good to go now.
While at it, I'll also patch gem2deb to do the same by default.

About the second half, while it may be unmaintained upstream, I can't
help it because this is a dependency of a couple of gem's tests. So we
either don't run the tests or have this package maintained myself.
And I definitely do not want to skip tests like that :D

>> ruby-arbre (thanks to terceiro :D)
> Looks good, except:
> - Testsuite: autopkgtest-pkg-ruby in debian/control is obsolete.
> - Please run wrap-and-sort on debian/control.
> - The description contains just two sentences, both of which are repeated.
>   Could you fix this, and probably extend the description a bit?

Fixed description and ran wrap-and-sort. Good to go now.
Thanks for looking into it with such detail (description didn't really
make sense to me myself :/).


Best,
Utkarsh
---
[1]: https://salsa.debian.org/ruby-team/ruby-memory-profiler




signature.asc
Description: OpenPGP digital signature

Re: RFS: ruby-*

[Georg Faerber]

On 19-08-28 10:07:34, Utkarsh Gupta wrote:
> ruby-benchmark-memory
> ruby-ammeter
> ruby-arbre (thanks to terceiro :D)

All uploaded, now in NEW.

Re: RFS: ruby-*

[Utkarsh Gupta]

Hey,

On 29/08/19 6:25 pm, Georg Faerber wrote:
> On 19-08-28 10:07:34, Utkarsh Gupta wrote:
>> ruby-benchmark-memory
>> ruby-ammeter
>> ruby-arbre (thanks to terceiro :D)
> All uploaded, now in NEW.

Thank you so much, Georg.

Also, I patched gem2deb to use version=4 in d/watch by default.
Gotta wait for it's next upload.


Best,
Utkarsh




signature.asc
Description: OpenPGP digital signature

Re: RFS: ruby-mocha

[Lucas Nussbaum]

On 31/03/11 at 10:52 -0700, Antonio Terceiro wrote:
> Hi,
> 
> I need one DD to upload ruby-mocha. It is in our new set of git
> repositories, more specifically at:
> 
> git+ssh://git.debian.org/git/pkg-ruby-extras/ruby-mocha.git
> 
> I will be able to do further uploads on my on as a DM.
> 
> After the package enters the archive, I will request the removal of
> the libmocha-ruby*. 

Looks quite good.
Have you tested upgrades? I'm wondering whether we shouldn't add
transition packages (and have have an helper too that generates the
debian/control entry for those metapackages, since we will have lots of
them).

 - Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110401205222.ga12...@xanadu.blop.info

Re: RFS: ruby-mocha

[Antonio Terceiro]

Hi,

Lucas Nussbaum escreveu isso aí:
> On 31/03/11 at 10:52 -0700, Antonio Terceiro wrote:
> > Hi,
> > 
> > I need one DD to upload ruby-mocha. It is in our new set of git
> > repositories, more specifically at:
> > 
> > git+ssh://git.debian.org/git/pkg-ruby-extras/ruby-mocha.git
> > 
> > I will be able to do further uploads on my on as a DM.
> > 
> > After the package enters the archive, I will request the removal of
> > the libmocha-ruby*. 
> 
> Looks quite good.
> Have you tested upgrades? I'm wondering whether we shouldn't add
> transition packages (and have have an helper too that generates the
> debian/control entry for those metapackages, since we will have lots of
> them).

Good point. Actually, using transitional packages would be the only way
to get the packages upgraded automatically in the case they were
installed directly (as opposed to installed as a dependency of other
package).

On the other hand, having the transitional packages will defeat one of
our objectives: to have no lib*-ruby packages in the archive. Also, if
we do use transitional packages you will end up with *a lot* of them in
the archive.

I saved the list of binary packages listed in the output of your UDD CGI
script on /tmp/packages and checked how many transitional packages we
would need:

$ sed -e '/^lib/!d; s/1.8//; s/1.9.1//' /tmp/packages | sort -u | wc -l
363

Since ruby-foo would Replace/Provide/Conflict with libfoo-ruby,
libfoo-ruby1.8 and libfoo-ruby1.9.1, then I removed the version suffixes
and then obtained the list of unique library names.

IMO using transitional packages would be OK for a few packages, but
having 363 transitional packages seems dirty to me.

Alternatively, we could do the following for every ruby-foo packages
that gets in the archive:

  0) Ping maintainers of reverse dependencies and ask them to depend on
  ruby-foo instead of libfoo-ruby

  1) Request removal of libfoo-ruby from the archive. Even non-updated
  dependencies on libfoo-ruby will then be provided by ruby-foo anyway.

Additionally, we could also provide a tool (update-debian-ruby?) that
detects all lib*-ruby* installed on the system and proposes the user to
install the equivalent ruby.* packages (what would then trigger the
removal of lib*-ruby* packages).

-- 
Antonio Terceiro 
http://softwarelivre.org/terceiro




signature.asc
Description: Digital signature

Re: RFS: ruby-mocha

[Lucas Nussbaum]

On 02/04/11 at 17:14 -0700, Antonio Terceiro wrote:
> Hi,
> 
> Lucas Nussbaum escreveu isso aí:
> > On 31/03/11 at 10:52 -0700, Antonio Terceiro wrote:
> > > Hi,
> > > 
> > > I need one DD to upload ruby-mocha. It is in our new set of git
> > > repositories, more specifically at:
> > > 
> > > git+ssh://git.debian.org/git/pkg-ruby-extras/ruby-mocha.git
> > > 
> > > I will be able to do further uploads on my on as a DM.
> > > 
> > > After the package enters the archive, I will request the removal of
> > > the libmocha-ruby*. 
> > 
> > Looks quite good.
> > Have you tested upgrades? I'm wondering whether we shouldn't add
> > transition packages (and have have an helper too that generates the
> > debian/control entry for those metapackages, since we will have lots of
> > them).
> 
> Good point. Actually, using transitional packages would be the only way
> to get the packages upgraded automatically in the case they were
> installed directly (as opposed to installed as a dependency of other
> package).
> 
> On the other hand, having the transitional packages will defeat one of
> our objectives: to have no lib*-ruby packages in the archive. Also, if
> we do use transitional packages you will end up with *a lot* of them in
> the archive.
> 
> I saved the list of binary packages listed in the output of your UDD CGI
> script on /tmp/packages and checked how many transitional packages we
> would need:
> 
> $ sed -e '/^lib/!d; s/1.8//; s/1.9.1//' /tmp/packages | sort -u | wc -l
> 363
> 
> Since ruby-foo would Replace/Provide/Conflict with libfoo-ruby,
> libfoo-ruby1.8 and libfoo-ruby1.9.1, then I removed the version suffixes
> and then obtained the list of unique library names.
> 
> IMO using transitional packages would be OK for a few packages, but
> having 363 transitional packages seems dirty to me.
> 
> Alternatively, we could do the following for every ruby-foo packages
> that gets in the archive:
> 
>   0) Ping maintainers of reverse dependencies and ask them to depend on
>   ruby-foo instead of libfoo-ruby
> 
>   1) Request removal of libfoo-ruby from the archive. Even non-updated
>   dependencies on libfoo-ruby will then be provided by ruby-foo anyway.
> 
> Additionally, we could also provide a tool (update-debian-ruby?) that
> detects all lib*-ruby* installed on the system and proposes the user to
> install the equivalent ruby.* packages (what would then trigger the
> removal of lib*-ruby* packages).

I think that the only correct Debian way to ensure clean upgrades is to
provide transition packages, unfortunately. Of course, we should also
ensure that r-deps use the ruby-foo packages, but there are many ruby
packages that have no r-deps, or that are often used without r-deps.

The good thing is that the transitional packages can go away as soon as
wheezy is released...

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110403072855.ga12...@xanadu.blop.info

Re: RFS: ruby-mocha

[Antonio Terceiro]

Lucas Nussbaum escreveu isso aí:
> I think that the only correct Debian way to ensure clean upgrades is to
> provide transition packages, unfortunately. Of course, we should also
> ensure that r-deps use the ruby-foo packages, but there are many ruby
> packages that have no r-deps, or that are often used without r-deps.
> 
> The good thing is that the transitional packages can go away as soon as
> wheezy is released...

ok, let's go there then. For what I understood from
http://wiki.debian.org/Renaming_a_Package, using transitional packages
has the advantage that the old source package is removed automatically.
Is that correct?

We still need to update the tracking UDD scripts to ignore the
transitional packages in migrated packages.

I've just updated ruby-mocha adding the transitional packages. I've
tested the upgrade and it works fine. Can you please upload it?

-- 
Antonio Terceiro 
http://softwarelivre.org/terceiro




signature.asc
Description: Digital signature

Re: RFS: ruby-mocha

[Lucas Nussbaum]

On 03/04/11 at 14:24 -0700, Antonio Terceiro wrote:
> Lucas Nussbaum escreveu isso aí:
> > I think that the only correct Debian way to ensure clean upgrades is to
> > provide transition packages, unfortunately. Of course, we should also
> > ensure that r-deps use the ruby-foo packages, but there are many ruby
> > packages that have no r-deps, or that are often used without r-deps.
> > 
> > The good thing is that the transitional packages can go away as soon as
> > wheezy is released...
> 
> ok, let's go there then. For what I understood from
> http://wiki.debian.org/Renaming_a_Package, using transitional packages
> has the advantage that the old source package is removed automatically.
> Is that correct?
> 
> We still need to update the tracking UDD scripts to ignore the
> transitional packages in migrated packages.
> 
> I've just updated ruby-mocha adding the transitional packages. I've
> tested the upgrade and it works fine. Can you please upload it?

Hi,

Uploaded.
I've reverted your debian/rules hack and used debian/ruby-tests.rb
instead.

Thanks!

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110404060433.gb28...@xanadu.blop.info

Re: RFS: ruby-mocha

[Lucas Nussbaum]

On 03/04/11 at 14:24 -0700, Antonio Terceiro wrote:
> Lucas Nussbaum escreveu isso aí:
> > I think that the only correct Debian way to ensure clean upgrades is to
> > provide transition packages, unfortunately. Of course, we should also
> > ensure that r-deps use the ruby-foo packages, but there are many ruby
> > packages that have no r-deps, or that are often used without r-deps.
> > 
> > The good thing is that the transitional packages can go away as soon as
> > wheezy is released...
> 
> ok, let's go there then. For what I understood from
> http://wiki.debian.org/Renaming_a_Package, using transitional packages
> has the advantage that the old source package is removed automatically.
> Is that correct?

I'm not sure. It's possible that we will have to ask for removals
anyway. Let's wait for a package to reach testing before we ask.

> We still need to update the tracking UDD scripts to ignore the
> transitional packages in migrated packages.

I'll do that when the packages are accepted, so there's a way to test
that it works.

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110404060907.ga31...@xanadu.blop.info

Re: RFS: ruby-mocha

[Antonio Terceiro]

Lucas Nussbaum escreveu isso aí:
> On 03/04/11 at 14:24 -0700, Antonio Terceiro wrote:
> > Lucas Nussbaum escreveu isso aí:
> > > I think that the only correct Debian way to ensure clean upgrades is to
> > > provide transition packages, unfortunately. Of course, we should also
> > > ensure that r-deps use the ruby-foo packages, but there are many ruby
> > > packages that have no r-deps, or that are often used without r-deps.
> > > 
> > > The good thing is that the transitional packages can go away as soon as
> > > wheezy is released...
> > 
> > ok, let's go there then. For what I understood from
> > http://wiki.debian.org/Renaming_a_Package, using transitional packages
> > has the advantage that the old source package is removed automatically.
> > Is that correct?
> > 
> > We still need to update the tracking UDD scripts to ignore the
> > transitional packages in migrated packages.
> > 
> > I've just updated ruby-mocha adding the transitional packages. I've
> > tested the upgrade and it works fine. Can you please upload it?
> 
> Hi,
> 
> Uploaded.

Thanks. :)

> I've reverted your debian/rules hack and used debian/ruby-tests.rb
> instead.

Another way to do that that occurred to me, and that does not duplicate
upstreams' logic abouth which are the test cases to run, is:

  ARGV.unshift('test') # skip if upstream default rake target is reasonable
  require 'rake'
  Rake.application.run

This requires that upstream's Rakefile does not do things like 'require
"rubygems"', though.

-- 
Antonio Terceiro 
http://softwarelivre.org/terceiro




signature.asc
Description: Digital signature

Re: RFS: ruby-mocha

[Antonio Terceiro]

Lucas Nussbaum escreveu isso aí:
> > We still need to update the tracking UDD scripts to ignore the
> > transitional packages in migrated packages.
> 
> I'll do that when the packages are accepted, so there's a way to test
> that it works.

Great.

What do you think of centralizing all this transition tracking code on
http://git.debian.org/?p=pkg-ruby-extras/wheezy-transition-tracker.git;a=summary
?

-- 
Antonio Terceiro 
http://softwarelivre.org/terceiro




signature.asc
Description: Digital signature

Re: RFS: ruby-mocha

[Lucas Nussbaum]

On 04/04/11 at 10:34 -0700, Antonio Terceiro wrote:
> Lucas Nussbaum escreveu isso aí:
> > > We still need to update the tracking UDD scripts to ignore the
> > > transitional packages in migrated packages.
> > 
> > I'll do that when the packages are accepted, so there's a way to test
> > that it works.
> 
> Great.
> 
> What do you think of centralizing all this transition tracking code on
> http://git.debian.org/?p=pkg-ruby-extras/wheezy-transition-tracker.git;a=summary
> ?

I'll do that too, yes.

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110404191809.ga26...@xanadu.blop.info

Re: RFS: ruby-mocha

[Antonio Terceiro]

Lucas Nussbaum escreveu isso aí:
> On 04/04/11 at 10:34 -0700, Antonio Terceiro wrote:
> > Lucas Nussbaum escreveu isso aí:
> > > > We still need to update the tracking UDD scripts to ignore the
> > > > transitional packages in migrated packages.
> > > 
> > > I'll do that when the packages are accepted, so there's a way to test
> > > that it works.
> > 
> > Great.
> > 
> > What do you think of centralizing all this transition tracking code on
> > http://git.debian.org/?p=pkg-ruby-extras/wheezy-transition-tracker.git;a=summary
> > ?
> 
> I'll do that too, yes.

ok, great. :)

Please note that the json thing does not work when you open index.html
as a local file; you'll need to access the site through an actual web
server. I use the attached script to start a lighttpd instance with the
current directory as www root, but working under your ~/public_html/
with most webservers should work as well.

-- 
Antonio Terceiro 
http://softwarelivre.org/terceiro


#!/bin/sh

port=8080

use_php=false

create_config() {
  current_dir=$(pwd)
  cat > "$1" <<-EOF
server.document-root = "$current_dir"
server.port = $port
include_shell "/usr/share/lighttpd/create-mime.assign.pl"
dir-listing.encoding= "utf-8"
server.dir-listing  = "enable"
EOF

  if [ "$use_php" = 'true' ]; then
echo 'include "/etc/lighttpd/conf-available/10-fastcgi.conf"'   >> "$1"
echo 'include "/etc/lighttpd/conf-available/15-fastcgi-php.conf"'   >> "$1"
echo 'index-file.names = ("index.php", "index.html", "index.htm")'  >> "$1"
  else
echo 'index-file.names= ("index.html", "index.htm")'>> "$1"
  fi

}

run() {
  conffile="$1"
  echo "I: Go to: http://localhost:$port/";
  echo "I: Hit Control+C to stop"
  echo ""
  /usr/sbin/lighttpd -f "$conffile" -D
}

conffile=$(mktemp)

for opt in $@; do
  case "$opt" in
--php)
  use_php=true
  ;;
*)
  echo "Invalid option: $opt"
  exit 1
  ;;
  esac
done

create_config "$conffile"
run "$conffile"
rm -f "$conffile"


signature.asc
Description: Digital signature

Re: RFS: ruby-lapack

[Lucas Nussbaum]

On 06/04/11 at 04:40 +0900, Youhei SASAKI wrote:
> Hi,
> 
> The following packages are ready to be uploaded
> (I also verified the points listed on
> http://wiki.debian.org/Teams/Ruby/RubyExtras/RequestingSponsorship).
> 
> Could you please sponsor them?
> 
>   Vcs-git: git://git.debian.org/pkg-ruby-extras/ruby-lapack.git
>   Vcs-Browser: http://git.debian.org/?p=pkg-ruby-extras/ruby-lapack;a=summary
> 
>   source: ruby-lapack
>   packages:
>- ruby-lapack: library and documents
>- ruby-lapack-dbg: debug symbols
> 
> # I have started using gem2deb. It's very nice, wonderful!!

Hi,

I've done a quick review. I would appreciate if someone else would do
another one.

Small fix (committed):
-   dh $@ --buildsystem=ruby --with ruby --with quilt
+   dh $@ --buildsystem=ruby --with ruby
(--with quilt is not needed anymore)

Other question:
would it make sense to run the sample script at the end of the build, to
see if everything works fine? I'm a bit disturbed by the lack of test
suite.

Thanks,

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110406120948.gb13...@xanadu.blop.info

Re: RFS: ruby-mocha

[Lucas Nussbaum]

On 04/04/11 at 10:34 -0700, Antonio Terceiro wrote:
> Lucas Nussbaum escreveu isso aí:
> > > We still need to update the tracking UDD scripts to ignore the
> > > transitional packages in migrated packages.
> > 
> > I'll do that when the packages are accepted, so there's a way to test
> > that it works.
> 
> Great.
> 
> What do you think of centralizing all this transition tracking code on
> http://git.debian.org/?p=pkg-ruby-extras/wheezy-transition-tracker.git;a=summary
> ?

The script is a cgi, so it needs to live in cgi-bin. How do you think
that we should manage it?

In the meantime, it's available as:
alioth:/srv/home/groups/pkg-ruby-extras/cgi-bin/wheezy-transition.cgi
(group writable) or
http://pkg-ruby-extras.alioth.debian.org/cgi-bin/wheezy-transition.cgi

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110406123744.ga26...@xanadu.blop.info

Re: RFS: ruby-mocha

[Antonio Terceiro]

Lucas Nussbaum escreveu isso aí:
> On 04/04/11 at 10:34 -0700, Antonio Terceiro wrote:
> > Lucas Nussbaum escreveu isso aí:
> > > > We still need to update the tracking UDD scripts to ignore the
> > > > transitional packages in migrated packages.
> > > 
> > > I'll do that when the packages are accepted, so there's a way to test
> > > that it works.
> > 
> > Great.
> > 
> > What do you think of centralizing all this transition tracking code on
> > http://git.debian.org/?p=pkg-ruby-extras/wheezy-transition-tracker.git;a=summary
> > ?
> 
> The script is a cgi, so it needs to live in cgi-bin. How do you think
> that we should manage it?
>
> In the meantime, it's available as:
> alioth:/srv/home/groups/pkg-ruby-extras/cgi-bin/wheezy-transition.cgi
> (group writable) or
> http://pkg-ruby-extras.alioth.debian.org/cgi-bin/wheezy-transition.cgi

Thanks for sharing. :)

What I thought was to get the script's logic and make the whole thing
not depend on external CGI scripts, generating static files instead.

I've just updated the repository with this and updated the published
copy:

http://pkg-ruby-extras.alioth.debian.org/wheezy/

-- 
Antonio Terceiro 
http://softwarelivre.org/terceiro




signature.asc
Description: Digital signature

Re: RFS: ruby-mocha

[Antonio Terceiro]

Antonio Terceiro escreveu isso aí:
> I've just updated the repository with this and updated the published
> copy:
> 
> http://pkg-ruby-extras.alioth.debian.org/wheezy/

BTW: that is being updated once a day by a cron job run from my account.

-- 
Antonio Terceiro 
http://softwarelivre.org/terceiro




signature.asc
Description: Digital signature

Re: RFS: ruby-lapack

[Youhei SASAKI]

Hi,

At 6 Apr 2011 14:09:48 +0200,
"Lucas Nussbaum"  wrote:
>
> I've done a quick review. I would appreciate if someone else would do
> another one.
>
> Small fix (committed):
> -   dh $@ --buildsystem=ruby --with ruby --with quilt
> +   dh $@ --buildsystem=ruby --with ruby
> (--with quilt is not needed anymore)

How do you treat .pc? Should I use patch-queue manner on git-buildpackage?

> Other question:
> would it make sense to run the sample script at the end of the build, to
> see if everything works fine? I'm a bit disturbed by the lack of test
> suite.

Currently, I'm frequently using this library on amd64 and i386.
This library works fine. However, I think your comment is reasonable.

Ok. I'll create some test suite. Please wait for a while...

---
Youhei SASAKI 
  
GPG fingerprint:
  4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87zko2pnun.wl%uwab...@gfd-dennou.org

Re: RFS: ruby-mocha

[Lucas Nussbaum]

On 06/04/11 at 12:15 -0700, Antonio Terceiro wrote:
> Lucas Nussbaum escreveu isso aí:
> > On 04/04/11 at 10:34 -0700, Antonio Terceiro wrote:
> > > Lucas Nussbaum escreveu isso aí:
> > > > > We still need to update the tracking UDD scripts to ignore the
> > > > > transitional packages in migrated packages.
> > > > 
> > > > I'll do that when the packages are accepted, so there's a way to test
> > > > that it works.
> > > 
> > > Great.
> > > 
> > > What do you think of centralizing all this transition tracking code on
> > > http://git.debian.org/?p=pkg-ruby-extras/wheezy-transition-tracker.git;a=summary
> > > ?
> > 
> > The script is a cgi, so it needs to live in cgi-bin. How do you think
> > that we should manage it?
> >
> > In the meantime, it's available as:
> > alioth:/srv/home/groups/pkg-ruby-extras/cgi-bin/wheezy-transition.cgi
> > (group writable) or
> > http://pkg-ruby-extras.alioth.debian.org/cgi-bin/wheezy-transition.cgi
> 
> Thanks for sharing. :)
> 
> What I thought was to get the script's logic and make the whole thing
> not depend on external CGI scripts, generating static files instead.
> 
> I've just updated the repository with this and updated the published
> copy:
> 
> http://pkg-ruby-extras.alioth.debian.org/wheezy/

Nice. i've made a few changes (pushed). Could you update the live copy?
I also wanted to list the packages in NEW that are about ruby, but the
NEW UDD importer is currently broken. I've asked Andreas Tille to fix
it.

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110407073337.ga17...@xanadu.blop.info

Re: RFS: ruby-lapack

[Lucas Nussbaum]

On 07/04/11 at 15:38 +0900, Youhei SASAKI wrote:
> Hi,
> 
> At 6 Apr 2011 14:09:48 +0200,
> "Lucas Nussbaum"  wrote:
> >
> > I've done a quick review. I would appreciate if someone else would do
> > another one.
> >
> > Small fix (committed):
> > -   dh $@ --buildsystem=ruby --with ruby --with quilt
> > +   dh $@ --buildsystem=ruby --with ruby
> > (--with quilt is not needed anymore)
> 
> How do you treat .pc? Should I use patch-queue manner on git-buildpackage?

I don't commit it to the git repo. But we could decide to do the
opposite... It's mainly a matter of taste.

Anyway, debhelper now detects when quilt is used, that's why --with
quilt is not needed.

> > Other question:
> > would it make sense to run the sample script at the end of the build, to
> > see if everything works fine? I'm a bit disturbed by the lack of test
> > suite.
> 
> Currently, I'm frequently using this library on amd64 and i386.
> This library works fine. However, I think your comment is reasonable.

Well, the point is to ensure that we will know if the library breaks in
some months. :)

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110407083953.ga21...@xanadu.blop.info

Re: RFS: ruby-mocha

[Antonio Terceiro]

Lucas Nussbaum escreveu isso aí:
> On 06/04/11 at 12:15 -0700, Antonio Terceiro wrote:
> > Lucas Nussbaum escreveu isso aí:
> > > On 04/04/11 at 10:34 -0700, Antonio Terceiro wrote:
> > > > Lucas Nussbaum escreveu isso aí:
> > > > > > We still need to update the tracking UDD scripts to ignore the
> > > > > > transitional packages in migrated packages.
> > > > > 
> > > > > I'll do that when the packages are accepted, so there's a way to test
> > > > > that it works.
> > > > 
> > > > Great.
> > > > 
> > > > What do you think of centralizing all this transition tracking code on
> > > > http://git.debian.org/?p=pkg-ruby-extras/wheezy-transition-tracker.git;a=summary
> > > > ?
> > > 
> > > The script is a cgi, so it needs to live in cgi-bin. How do you think
> > > that we should manage it?
> > >
> > > In the meantime, it's available as:
> > > alioth:/srv/home/groups/pkg-ruby-extras/cgi-bin/wheezy-transition.cgi
> > > (group writable) or
> > > http://pkg-ruby-extras.alioth.debian.org/cgi-bin/wheezy-transition.cgi
> > 
> > Thanks for sharing. :)
> > 
> > What I thought was to get the script's logic and make the whole thing
> > not depend on external CGI scripts, generating static files instead.
> > 
> > I've just updated the repository with this and updated the published
> > copy:
> > 
> > http://pkg-ruby-extras.alioth.debian.org/wheezy/
> 
> Nice. i've made a few changes (pushed). Could you update the live copy?

Done. (did one more change on top of yours.

The new search criteria gave some movement to our graph. :)

> I also wanted to list the packages in NEW that are about ruby, but the
> NEW UDD importer is currently broken. I've asked Andreas Tille to fix
> it.

-- 
Antonio Terceiro 
http://softwarelivre.org/terceiro




signature.asc
Description: Digital signature

Re: RFS: ruby-mocha

[Lucas Nussbaum]

On 07/04/11 at 11:14 -0700, Antonio Terceiro wrote:
> Lucas Nussbaum escreveu isso aí:
> > On 06/04/11 at 12:15 -0700, Antonio Terceiro wrote:
> > > Lucas Nussbaum escreveu isso aí:
> > > > On 04/04/11 at 10:34 -0700, Antonio Terceiro wrote:
> > > > > Lucas Nussbaum escreveu isso aí:
> > > > > > > We still need to update the tracking UDD scripts to ignore the
> > > > > > > transitional packages in migrated packages.
> > > > > > 
> > > > > > I'll do that when the packages are accepted, so there's a way to 
> > > > > > test
> > > > > > that it works.
> > > > > 
> > > > > Great.
> > > > > 
> > > > > What do you think of centralizing all this transition tracking code on
> > > > > http://git.debian.org/?p=pkg-ruby-extras/wheezy-transition-tracker.git;a=summary
> > > > > ?
> > > > 
> > > > The script is a cgi, so it needs to live in cgi-bin. How do you think
> > > > that we should manage it?
> > > >
> > > > In the meantime, it's available as:
> > > > alioth:/srv/home/groups/pkg-ruby-extras/cgi-bin/wheezy-transition.cgi
> > > > (group writable) or
> > > > http://pkg-ruby-extras.alioth.debian.org/cgi-bin/wheezy-transition.cgi
> > > 
> > > Thanks for sharing. :)
> > > 
> > > What I thought was to get the script's logic and make the whole thing
> > > not depend on external CGI scripts, generating static files instead.
> > > 
> > > I've just updated the repository with this and updated the published
> > > copy:
> > > 
> > > http://pkg-ruby-extras.alioth.debian.org/wheezy/
> > 
> > Nice. i've made a few changes (pushed). Could you update the live copy?
> 
> Done. (did one more change on top of yours.
> 
> The new search criteria gave some movement to our graph. :)

Hi,

I did a few other changes. Could you update the live copy, and chmod it
g+w?

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110409081757.ga8...@xanadu.blop.info

Re: RFS: ruby-globalhotkeys

[Lucas Nussbaum]

On 08/04/11 at 02:16 +0200, Vincent Carmona wrote:
> Hi.
> 
> I have updated ruby-globalhotkeys git repository.
> http://git.debian.org/?p=pkg-ruby-extras/ruby-globalhotkeys.git;a=summary
> git://git.debian.org/pkg-ruby-extras/ruby-globalhotkeys.git
> 
> Can someone take a look at my works and eventually upload the new
> source package?

I fixed debian/copyright.

You did not push your local pristine-tar branch, apparently. Remember to
use git push --all ; git push --tags when pushing your changes.
(Please see if it's missing somewhere in the docs on the wiki)

> I have one lintian warning:
> ruby-globalhotkeys source: unknown-field-in-dsc ruby-versions
> Should I do something about it?

No, that's fine. Could you talk to the lintian team about adding an
exception for this field?

> Is it normal that lib/global-hotkeys.rb is shipped twice (under
> /usr/lib/ruby/vendor_ruby/ and
> /usr/lib/ruby/vendor_ruby/1.8/x86_64-linux/) ?

No, but I can't build the package without the pristine-tar branch, so I
can't test.

> Should I ask for a removal of the libglobalhotkeys-ruby source package?

We don't know yet. It's possible that they will get removed
automatically. Could you ask ftpmasters about that and let us know?

Thanks,

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110409101753.ga30...@xanadu.blop.info

Re: RFS: ruby-tokyocabinet

[Lucas Nussbaum]

On 09/04/11 at 14:33 +0200, Laurent Arnoud wrote:
> Hello,
> 
> I've updated the tokyocabinet-ruby package using now gem2deb and other minor
> update.
> 
> The packaging is now here:
> Browser: http://git.debian.org/?p=pkg-ruby-extras/tokyocabinet-ruby.git
> Git: git://git.debian.org/pkg-ruby-extras/tokyocabinet-ruby.git

Hi,

Why tokyocabinet-ruby and not ruby-tokyocabinet?

> I added myself as uploader for lintian, tell me if its not a good practice.

It is.

Review:
ruby-tokyocabinet-doc.rdoc: what's that file for?

Other fixes (committed to git):
--- a/debian/control
+++ b/debian/control
@@ -1,5 +1,5 @@
 Source: tokyocabinet-ruby
-Section: libs
+Section: ruby
 Priority: extra
 Maintainer: Debian Ruby Extras Maintainers 
, Marc Dequènes (Duck) 
,
@@ -12,12 +12,11 @@ Vcs-Browser: 
http://git.debian.org/?p=pkg-ruby-extras/tokyocabinet-ruby
 XS-Ruby-Versions: all
 
 Package: ruby-tokyocabinet
-Section: ruby
 Architecture: any
 XB-Ruby-Versions: ${ruby:Versions}
 Depends: ${shlibs:Depends}, ${misc:Depends}, ruby1.8 | ruby-interpreter
 Suggests: libtokyocabinet-ruby-doc
-Description: Ruby Binding of Tokyo Cabinet Database (ruby 1.8)
+Description: Ruby Binding of Tokyo Cabinet Database
  Tokyo Cabinet is an efficient database library like GDBM and NDBM.
  It features hash database and B+ tree database and is developed as the
  successor of QDBM, for the purpose of the following three points: higher

#   renamed:ruby-tokyocabinet-doc.exemples -> 
ruby-tokyocabinet-doc.examples

Please address the source package name change, and then I can upload.

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110409125119.ga28...@xanadu.blop.info

Re: RFS: ruby-tokyocabinet

[Laurent Arnoud]

On Sat, Apr 09, 2011 at 02:51:19PM +0200, Lucas Nussbaum wrote:
> On 09/04/11 at 14:33 +0200, Laurent Arnoud wrote:
> > Hello,
> > 
> > I've updated the tokyocabinet-ruby package using now gem2deb and other minor
> > update.
> > 
> > The packaging is now here:
> > Browser: http://git.debian.org/?p=pkg-ruby-extras/tokyocabinet-ruby.git
> > Git: git://git.debian.org/pkg-ruby-extras/tokyocabinet-ruby.git
> 
> Hi,
> 
> Why tokyocabinet-ruby and not ruby-tokyocabinet?
>

Just for keep the old, the qa page will be broken ?
http://packages.qa.debian.org/t/tokyocabinet-ruby.html

> > I added myself as uploader for lintian, tell me if its not a good practice.
> 
> It is.

Oki i will remove myself

> 
> Review:
> ruby-tokyocabinet-doc.rdoc: what's that file for?
> 
> Other fixes (committed to git):
> --- a/debian/control
> +++ b/debian/control
> @@ -1,5 +1,5 @@
>  Source: tokyocabinet-ruby
> -Section: libs
> +Section: ruby
>  Priority: extra
>  Maintainer: Debian Ruby Extras Maintainers 
>   Uploaders: Paul van Tilburg , Marc Dequènes (Duck) 
> ,
> @@ -12,12 +12,11 @@ Vcs-Browser: 
> http://git.debian.org/?p=pkg-ruby-extras/tokyocabinet-ruby
>  XS-Ruby-Versions: all
>  
>  Package: ruby-tokyocabinet
> -Section: ruby
>  Architecture: any
>  XB-Ruby-Versions: ${ruby:Versions}
>  Depends: ${shlibs:Depends}, ${misc:Depends}, ruby1.8 | ruby-interpreter
>  Suggests: libtokyocabinet-ruby-doc
> -Description: Ruby Binding of Tokyo Cabinet Database (ruby 1.8)
> +Description: Ruby Binding of Tokyo Cabinet Database
>   Tokyo Cabinet is an efficient database library like GDBM and NDBM.
>   It features hash database and B+ tree database and is developed as the
>   successor of QDBM, for the purpose of the following three points: higher
> 
> # renamed:ruby-tokyocabinet-doc.exemples -> 
> ruby-tokyocabinet-doc.examples
> 
> Please address the source package name change, and then I can upload.

I will do, thanks Lucas for the review.

-- 
Laurent


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110409131814.GB3910@af83-x201

Re: RFS: ruby-tokyocabinet

[Lucas Nussbaum]

On 09/04/11 at 15:18 +0200, Laurent Arnoud wrote:
> On Sat, Apr 09, 2011 at 02:51:19PM +0200, Lucas Nussbaum wrote:
> > On 09/04/11 at 14:33 +0200, Laurent Arnoud wrote:
> > > Hello,
> > > 
> > > I've updated the tokyocabinet-ruby package using now gem2deb and other 
> > > minor
> > > update.
> > > 
> > > The packaging is now here:
> > > Browser: http://git.debian.org/?p=pkg-ruby-extras/tokyocabinet-ruby.git
> > > Git: git://git.debian.org/pkg-ruby-extras/tokyocabinet-ruby.git
> > 
> > Hi,
> > 
> > Why tokyocabinet-ruby and not ruby-tokyocabinet?
> >
> 
> Just for keep the old, the qa page will be broken ?
> http://packages.qa.debian.org/t/tokyocabinet-ruby.html

We decided to rename the source packages too. The additional work isn't
that big given that everything is changing inside the package anyway.
And it allows to keep "source package name" == "name of main binary
package".

> > > I added myself as uploader for lintian, tell me if its not a good 
> > > practice.
> > 
> > It is.
> 
> Oki i will remove myself

It is a good practice, sorry :)

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110409133027.ga30...@xanadu.blop.info

Re: RFS: ruby-globalhotkeys

[Lucas Nussbaum]

On 09/04/11 at 22:08 +0200, Vincent Carmona wrote:
> 2011/4/9 Vincent Carmona :
> > 2011/4/9 Lucas Nussbaum :
> >> On 09/04/11 at 16:17 +0200, Vincent Carmona wrote:
> >>> 2011/4/9 Lucas Nussbaum :
> >>> > You did not push your local pristine-tar branch, apparently. Remember to
> >>> > use git push --all ; git push --tags when pushing your changes.
> >>> > (Please see if it's missing somewhere in the docs on the wiki)
> >>>
> >>> I guess something is missing or went wrong as I do not have a
> >>> pristine-tar branch.
> >>> $ git branch
> >>> * master
> >>>   upstream
> >>>
> >>> I guess git import-dsc should have created it. Is it created from the
> >>> gem package ?
> >>> pristine-tar package is not installed on my computer.
> >>
> >> Ouch. You need it installed. I'm not sure how to recover from this
> >> situation -- you need to add the pristine-tar meta-info to the
> >> repository. See if you can figure it out. If you don't, it's also
> >> possible to start over.
> >>
> >> - Lucas
> >>
> >
> > I think we need to change
> > git import-dsc
> > to
> > git import-dsc --pristine-tar
> > in documentations.
> >
> > I am trying to use git import-orig to get a functionnal pristine branch.
> 
> Done.

OK, I also added an override in debian/rules for the .rb file installed
in the arch-specific dir.

A better workaround would be to ship (upstream) the extension in an ext/
dir.

I also fixed your build-deps (see git log).

Uploaded.

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110410132435.ga9...@xanadu.blop.info

Re: RFS: ruby-mocha

[Antonio Terceiro]

Lucas Nussbaum escreveu isso aí:
> Hi,
> 
> I did a few other changes. Could you update the live copy, and chmod it
> g+w?

Sure, just did it.

BTW, the daily cronjob does a git pull before updating the data anyway.

-- 
Antonio Terceiro 
http://softwarelivre.org/terceiro




signature.asc
Description: Digital signature

Re: RFS: ruby-lapack

[Antonio Terceiro]

Lucas Nussbaum escreveu isso aí:
> On 07/04/11 at 15:38 +0900, Youhei SASAKI wrote:
> > Hi,
> > 
> > At 6 Apr 2011 14:09:48 +0200,
> > "Lucas Nussbaum"  wrote:
> > >
> > > I've done a quick review. I would appreciate if someone else would do
> > > another one.
> > >
> > > Small fix (committed):
> > > -   dh $@ --buildsystem=ruby --with ruby --with quilt
> > > +   dh $@ --buildsystem=ruby --with ruby
> > > (--with quilt is not needed anymore)
> > 
> > How do you treat .pc? Should I use patch-queue manner on git-buildpackage?
> 
> I don't commit it to the git repo. But we could decide to do the
> opposite... It's mainly a matter of taste.

Do you build with git buildpackage?

I was thinking that maybe we should somehow standardize/document How We
Build Packages (TM).

-- 
Antonio Terceiro 
http://softwarelivre.org/terceiro




signature.asc
Description: Digital signature

Re: RFS: ruby-lapack

[Lucas Nussbaum]

On 10/04/11 at 15:26 -0700, Antonio Terceiro wrote:
> Lucas Nussbaum escreveu isso aí:
> > On 07/04/11 at 15:38 +0900, Youhei SASAKI wrote:
> > > Hi,
> > > 
> > > At 6 Apr 2011 14:09:48 +0200,
> > > "Lucas Nussbaum"  wrote:
> > > >
> > > > I've done a quick review. I would appreciate if someone else would do
> > > > another one.
> > > >
> > > > Small fix (committed):
> > > > -   dh $@ --buildsystem=ruby --with ruby --with quilt
> > > > +   dh $@ --buildsystem=ruby --with ruby
> > > > (--with quilt is not needed anymore)
> > > 
> > > How do you treat .pc? Should I use patch-queue manner on git-buildpackage?
> > 
> > I don't commit it to the git repo. But we could decide to do the
> > opposite... It's mainly a matter of taste.
> 
> Do you build with git buildpackage?

Yes

> I was thinking that maybe we should somehow standardize/document How We
> Build Packages (TM).

Yes, and also how we use debian/changelog for packages that are not
ready for upload.

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110411050431.ga32...@xanadu.blop.info

Re: RFS: ruby-bundle

[Lucas Nussbaum]

On 18/04/11 at 12:18 +0530, Hemanth H.M wrote:
> Dear mentors,
> 
> I am looking for a sponsor for my package "ruby-bundle".
> 
> * Package name: ruby-bundle
>   Version : 0.0.1-1
>   Upstream Author : Andre Arko
> * URL : http://gembundler.com/
> * License : MIT License
>   Section : ruby
> 
> It builds these binary packages:
> ruby-bundle - s/bundle/bundler
> 
> The upload would fix these bugs: 622374
> 
> My motivation for maintaining this package is: Packing gems for diaspora,
> this is on of the major gems.
> 
> The package can be found on mentors.debian.net:
> - URL: http://mentors.debian.net/debian/pool/main/r/ruby-bundle
> - Source repository: deb-src http://mentors.debian.net/debian unstable main
> contrib non-free
> - dget
> http://mentors.debian.net/debian/pool/main/r/ruby-bundle/ruby-bundle_0.0.1-1.dsc
> 
> I would be glad if someone uploaded this package for me.

Hi,

The source package is empty.

Shouldn't this be a package for bundler rather than bundle?

Could you import the packaging into the pkg-ruby-extras git repository?

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110418065944.ga3...@xanadu.blop.info

Re: RFS: ruby-bundle

[Lucas Nussbaum]

On 18/04/11 at 22:35 +0530, Hemanth H.M wrote:
> Shall i remove it and re-dput ? Just gem2deb or gem fetch bundler, then
> gem2tgz, dh-make-ruby foo-1.2.tar.gz, edited the copyrights and controls
> file and used pbuilder to create the deb, sign the required files and then a
> dput?

I get this:
*** lucas@beothuk:/tmp/ruby-bundle-0.0.1$ debc
ruby-bundle_0.0.1-1_all.deb
---
 new debian package, version 2.0.
 size 1856 bytes: control archive= 523 bytes.
 429 bytes,12 lines  control  
 150 bytes, 2 lines  md5sums  
 Package: ruby-bundle
 Version: 0.0.1-1
 Architecture: all
 Maintainer: Debian Ruby Extras Maintainers 

 Installed-Size: 32
 Depends: ruby1.8 | ruby-interpreter
 Section: ruby
 Priority: optional
 Homepage: http://gembundler.com
 Description: s/bundle/bundler
  You really mean `gem install bundler`. It's okay. I'll fix it for you this 
one last time...
 Ruby-Versions: ruby1.8 ruby1.9.1
drwxr-xr-x root/root 0 2011-04-18 23:32 ./
drwxr-xr-x root/root 0 2011-04-18 23:32 ./usr/
drwxr-xr-x root/root 0 2011-04-18 23:32 ./usr/share/
drwxr-xr-x root/root 0 2011-04-18 23:32 ./usr/share/doc/
drwxr-xr-x root/root 0 2011-04-18 23:32 ./usr/share/doc/ruby-bundle/
-rw-r--r-- root/root   154 2011-04-16 18:58 
./usr/share/doc/ruby-bundle/changelog.Debian.gz
-rw-r--r-- root/root  1116 2011-04-16 19:02 
./usr/share/doc/ruby-bundle/copyright

So it's indeed empty. Are you really sure that you really want to package
bundle, not bundle*r*?

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110418213346.ga22...@xanadu.blop.info

Re: RFS: ruby-bundle

[Hemanth H.M]

/me had got the results as attached, true the package name must be
bundle*r*, rather than bundle. We remove the current package and redo it,
thank you.

Reconfirming steps :
Just gem2deb?
Or
gem fetch bundler, then gem2tgz, dh-make-ruby foo-1.2.tar.gz, edited the
copyrights and controls file and use pbuilder to create the deb, sign the
required files and then a dput?
Or
Is there a easier way with gem2deb to deviate from the last step, do the
required and pack?


On Tue, Apr 19, 2011 at 3:03 AM, Lucas Nussbaum wrote:

> On 18/04/11 at 22:35 +0530, Hemanth H.M wrote:
> > Shall i remove it and re-dput ? Just gem2deb or gem fetch bundler, then
> > gem2tgz, dh-make-ruby foo-1.2.tar.gz, edited the copyrights and controls
> > file and used pbuilder to create the deb, sign the required files and
> then a
> > dput?
>
> I get this:
> *** lucas@beothuk:/tmp/ruby-bundle-0.0.1$ debc
> ruby-bundle_0.0.1-1_all.deb
> ---
>  new debian package, version 2.0.
>  size 1856 bytes: control archive= 523 bytes.
> 429 bytes,12 lines  control
> 150 bytes, 2 lines  md5sums
>  Package: ruby-bundle
>  Version: 0.0.1-1
>  Architecture: all
>  Maintainer: Debian Ruby Extras Maintainers <
> pkg-ruby-extras-maintain...@lists.alioth.debian.org>
>  Installed-Size: 32
>  Depends: ruby1.8 | ruby-interpreter
>  Section: ruby
>  Priority: optional
>  Homepage: http://gembundler.com
>  Description: s/bundle/bundler
>  You really mean `gem install bundler`. It's okay. I'll fix it for you this
> one last time...
>  Ruby-Versions: ruby1.8 ruby1.9.1
> drwxr-xr-x root/root 0 2011-04-18 23:32 ./
> drwxr-xr-x root/root 0 2011-04-18 23:32 ./usr/
> drwxr-xr-x root/root 0 2011-04-18 23:32 ./usr/share/
> drwxr-xr-x root/root 0 2011-04-18 23:32 ./usr/share/doc/
> drwxr-xr-x root/root 0 2011-04-18 23:32
> ./usr/share/doc/ruby-bundle/
> -rw-r--r-- root/root   154 2011-04-16 18:58
> ./usr/share/doc/ruby-bundle/changelog.Debian.gz
> -rw-r--r-- root/root  1116 2011-04-16 19:02
> ./usr/share/doc/ruby-bundle/copyright
>
> So it's indeed empty. Are you really sure that you really want to package
> bundle, not bundle*r*?
>
> - Lucas
>



-- 
*'I am what I am because of who we all are'*
h3manth.com 
*-- Hemanth HM *


res
Description: Binary data

Re: RFS: ruby-bundle

[Lucas Nussbaum]

On 19/04/11 at 10:12 +0530, Hemanth H.M wrote:
> /me had got the results as attached, true the package name must be
> bundle*r*, rather than bundle. We remove the current package and redo it,
> thank you.
> 
> Reconfirming steps :
> Just gem2deb?
> Or
> gem fetch bundler, then gem2tgz, dh-make-ruby foo-1.2.tar.gz, edited the
> copyrights and controls file and use pbuilder to create the deb, sign the
> required files and then a dput?

gem2deb is equivalent to:
gem fetch, gem2tgz, dh-make-ruby.
Then, you need to look at each file in debian/ and make the necessary
change (possibly not just copyright and control). When the package is
ready, dput it to mentors, so that we can review it, and then upload it
to Debian (you can't upload directly to Debian yourself, you need to be
a DD for that).

Alternatively to uploading to mentors, you could add the package to the
pkg-ruby-extras git repository, and we could review it from there. But
maybe it's better to do a first package using mentors so we make sure
we agree on that part of the process.

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110419050203.ga26...@xanadu.blop.info

Re: RFS: ruby-bundle

[Hemanth H.M]

Okies, will be redone accordingly, thanks for the help Lucas.

On Tue, Apr 19, 2011 at 10:32 AM, Lucas Nussbaum
wrote:

> On 19/04/11 at 10:12 +0530, Hemanth H.M wrote:
> > /me had got the results as attached, true the package name must be
> > bundle*r*, rather than bundle. We remove the current package and redo it,
> > thank you.
> >
> > Reconfirming steps :
> > Just gem2deb?
> > Or
> > gem fetch bundler, then gem2tgz, dh-make-ruby foo-1.2.tar.gz, edited the
> > copyrights and controls file and use pbuilder to create the deb, sign the
> > required files and then a dput?
>
> gem2deb is equivalent to:
> gem fetch, gem2tgz, dh-make-ruby.
> Then, you need to look at each file in debian/ and make the necessary
> change (possibly not just copyright and control). When the package is
> ready, dput it to mentors, so that we can review it, and then upload it
> to Debian (you can't upload directly to Debian yourself, you need to be
> a DD for that).
>
> Alternatively to uploading to mentors, you could add the package to the
> pkg-ruby-extras git repository, and we could review it from there. But
> maybe it's better to do a first package using mentors so we make sure
> we agree on that part of the process.
>
> - Lucas
>



-- 
*'I am what I am because of who we all are'*
h3manth.com 
*-- Hemanth HM *

Re: RFS: ruby-polyglot

[Lucas Nussbaum]

On 19/04/11 at 08:56 +0530, Vasudev Kamath wrote:
> Dear mentors,
> 
> I am looking for a sponsor for my package "ruby-polyglot".
> 
> * Package name: ruby-polyglot
>   Version : 0.3.1-1
>   Upstream Author : Clifford Heath 
> * URL : http://polyglot.rubyforge.org/
> * License : MIT
>   Section : ruby
> 
> It builds these binary packages:
> ruby-polyglot - Custom language loaders for specified file extensions
> 
> The upload would fix these bugs: 623080
> 
> My motivation for maintaining this package is: This gem is one of the
> dependency for Diaspora packaging.
> 
> The package can be found on mentors.debian.net:
> - URL: http://mentors.debian.net/debian/pool/main/r/ruby-polyglot
> - Source repository: deb-src http://mentors.debian.net/debian unstable
> main contrib non-free
> - dget 
> http://mentors.debian.net/debian/pool/main/r/ruby-polyglot/ruby-polyglot_0.3.1-1.dsc
> 
> I would be glad if someone uploaded this package for me.

It looks quite good, thanks.
Comments:
- copyright:
  the license text is supposed to follow the first time the license is
  used in a License: field.
- Is there a reason why you don't want to maintain this inside the team?
  Maintaining packages in teams is usually a very good idea, since it
  allows us the share the workload in case you become too busy.
- in debian/control:
# hoe (>= 2.3.3, development)
remove that line, or integrate it in one of the (Build-)?Depends fields.

If you want to maintain this within the team, please import the package
to the team's git repo, and add the team in Maintainer or Uploaders.
If not, I will sponsor the upload after you fix the second problem
above.

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110419052146.ga29...@xanadu.blop.info

Re: RFS: ruby-polyglot

[Vasudev Kamath]

On Tue, Apr 19, 2011 at 10:51 AM, Lucas Nussbaum
 wrote:
> On 19/04/11 at 08:56 +0530, Vasudev Kamath wrote:
>> Dear mentors,
>>
>> I am looking for a sponsor for my package "ruby-polyglot".
>>
>> * Package name    : ruby-polyglot
>>   Version         : 0.3.1-1
>>   Upstream Author : Clifford Heath 
>> * URL             : http://polyglot.rubyforge.org/
>> * License         : MIT
>>   Section         : ruby
>>
>> It builds these binary packages:
>> ruby-polyglot - Custom language loaders for specified file extensions
>>
>> The upload would fix these bugs: 623080
>>
>> My motivation for maintaining this package is: This gem is one of the
>> dependency for Diaspora packaging.
>>
>> The package can be found on mentors.debian.net:
>> - URL: http://mentors.debian.net/debian/pool/main/r/ruby-polyglot
>> - Source repository: deb-src http://mentors.debian.net/debian unstable
>> main contrib non-free
>> - dget 
>> http://mentors.debian.net/debian/pool/main/r/ruby-polyglot/ruby-polyglot_0.3.1-1.dsc
>>
>> I would be glad if someone uploaded this package for me.
>
> It looks quite good, thanks.
Thanks for the review :)

> Comments:
> - copyright:
>  the license text is supposed to follow the first time the license is
>  used in a License: field.

Hmm bit of a doubt here. Till now for the 2 packages I'm maintaining I
was told to put common license text for multiple files using same
license but different copyright  together. i.e In my package the
package content and debian folder both are licensed as MIT but have
different copyrights so I put the license text at the end. If this is
not correct let me fix it.

> - Is there a reason why you don't want to maintain this inside the team?

No I would love to join the team and maintain it from there :). Since
I'm not part of the team I put my name as maintainer (my idea was to
first get a review and then request to join the team :) ) I will
request to join the team and make myself as Uploader.

>  Maintaining packages in teams is usually a very good idea, since it
>  allows us the share the workload in case you become too busy.
> - in debian/control:
> # hoe (>= 2.3.3, development)
> remove that line, or integrate it in one of the (Build-)?Depends fields.
Ok I'll remove this, I was not sure if its needed or not before
running pbuilder and forgot to remove before uploading :)
>
> If you want to maintain this within the team, please import the package
> to the team's git repo, and add the team in Maintainer or Uploaders.
> If not, I will sponsor the upload after you fix the second problem
> above.
Thanks I'm send a request to join the team right away. Tonight I'll
fix the above issues and add the package to pkg-ruby-extras repo.
>
> - Lucas
>

Thanks and Regards

-- 

Vasudev Kamath
http://vasudevkamath.blogspot.com
http://identi.ca/vasudev
http://twitter.com/vasudevkamath


--
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/BANLkTi=G6F=xRv=xHg=_g-cmk487ak6...@mail.gmail.com

Re: RFS: ruby-polyglot

[Vasudev Kamath]

Hi Lucas,
I made the changes you had told and have uploaded the package to
pkg-ruby-extras git repository[1]. Can you please review the package
and let me know If something needs to be fixed.

[1] git+ssh://git.debian.org/git/pkg-ruby-extras/ruby-polyglot.git

Kind Regards

On Tue, Apr 19, 2011 at 10:51 AM, Lucas Nussbaum
 wrote:
> On 19/04/11 at 08:56 +0530, Vasudev Kamath wrote:
>> Dear mentors,
>>
>> I am looking for a sponsor for my package "ruby-polyglot".
>>
>> * Package name    : ruby-polyglot
>>   Version         : 0.3.1-1
>>   Upstream Author : Clifford Heath 
>> * URL             : http://polyglot.rubyforge.org/
>> * License         : MIT
>>   Section         : ruby
>>
>> It builds these binary packages:
>> ruby-polyglot - Custom language loaders for specified file extensions
>>
>> The upload would fix these bugs: 623080
>>
>> My motivation for maintaining this package is: This gem is one of the
>> dependency for Diaspora packaging.
>>
>> The package can be found on mentors.debian.net:
>> - URL: http://mentors.debian.net/debian/pool/main/r/ruby-polyglot
>> - Source repository: deb-src http://mentors.debian.net/debian unstable
>> main contrib non-free
>> - dget 
>> http://mentors.debian.net/debian/pool/main/r/ruby-polyglot/ruby-polyglot_0.3.1-1.dsc
>>
>> I would be glad if someone uploaded this package for me.
>
> It looks quite good, thanks.
> Comments:
> - copyright:
>  the license text is supposed to follow the first time the license is
>  used in a License: field.
> - Is there a reason why you don't want to maintain this inside the team?
>  Maintaining packages in teams is usually a very good idea, since it
>  allows us the share the workload in case you become too busy.
> - in debian/control:
> # hoe (>= 2.3.3, development)
> remove that line, or integrate it in one of the (Build-)?Depends fields.
>
> If you want to maintain this within the team, please import the package
> to the team's git repo, and add the team in Maintainer or Uploaders.
> If not, I will sponsor the upload after you fix the second problem
> above.
>
> - Lucas
>



-- 

Vasudev Kamath
http://vasudevkamath.blogspot.com
http://identi.ca/vasudev
http://twitter.com/vasudevkamath


--
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/BANLkTi=nka29dtucvomkvwmi0qqj4jj...@mail.gmail.com

Re: RFS: ruby-polyglot

[Lucas Nussbaum]

On 19/04/11 at 23:21 +0530, Vasudev Kamath wrote:
> Hi Lucas,
> I made the changes you had told and have uploaded the package to
> pkg-ruby-extras git repository[1]. Can you please review the package
> and let me know If something needs to be fixed.
> 
> [1] git+ssh://git.debian.org/git/pkg-ruby-extras/ruby-polyglot.git

How did you push to alioth? You need to git push --all && git push --tags

I don't see the upstream and pristine-tar branch.

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110420151751.ga25...@xanadu.blop.info

Re: RFS: ruby-polyglot

[Vasudev Kamath]

On Wed, Apr 20, 2011 at 8:47 PM, Lucas Nussbaum
 wrote:
> On 19/04/11 at 23:21 +0530, Vasudev Kamath wrote:
>> Hi Lucas,
>> I made the changes you had told and have uploaded the package to
>> pkg-ruby-extras git repository[1]. Can you please review the package
>> and let me know If something needs to be fixed.
>>
>> [1] git+ssh://git.debian.org/git/pkg-ruby-extras/ruby-polyglot.git
>
> How did you push to alioth? You need to git push --all && git push --tags
Well I messed it up a bit :(.. Instead of following the guidelines on
the RubyInWheezy page I followed http://wiki.debian.org/Alioth/Git and
then used git-import-dsc to create repo from the .dsc of my package
(Actually I should have cloned empty repository and done this from
there).
>
> I don't see the upstream and pristine-tar branch.
I didn't use --all so upstream branch was on my system just now pushed
it but I forgot to give --pristine-tar option so that branch isn't
present :( Can I create that branch manually?
>
> - Lucas
>

Thanks and Regards


-- 

Vasudev Kamath
http://vasudevkamath.blogspot.com
http://identi.ca/vasudev
http://twitter.com/vasudevkamath


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktinemxrrqnmiyru1xo1rymuexnp...@mail.gmail.com

Re: RFS: ruby-polyglot

[Lucas Nussbaum]

On 20/04/11 at 21:51 +0530, Vasudev Kamath wrote:
> On Wed, Apr 20, 2011 at 8:47 PM, Lucas Nussbaum
>  wrote:
> > On 19/04/11 at 23:21 +0530, Vasudev Kamath wrote:
> >> Hi Lucas,
> >> I made the changes you had told and have uploaded the package to
> >> pkg-ruby-extras git repository[1]. Can you please review the package
> >> and let me know If something needs to be fixed.
> >>
> >> [1] git+ssh://git.debian.org/git/pkg-ruby-extras/ruby-polyglot.git
> >
> > How did you push to alioth? You need to git push --all && git push --tags
> Well I messed it up a bit :(.. Instead of following the guidelines on
> the RubyInWheezy page I followed http://wiki.debian.org/Alioth/Git and
> then used git-import-dsc to create repo from the .dsc of my package
> (Actually I should have cloned empty repository and done this from
> there).
> >
> > I don't see the upstream and pristine-tar branch.
> I didn't use --all so upstream branch was on my system just now pushed
> it but I forgot to give --pristine-tar option so that branch isn't
> present :( Can I create that branch manually?

You could just git push --all now, if you still have the local branch.

L.


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110420225303.ga30...@xanadu.blop.info

Re: RFS: ruby-polyglot

[Vasudev Kamath]

On Thu, Apr 21, 2011 at 4:23 AM, Lucas Nussbaum
 wrote:
> On 20/04/11 at 21:51 +0530, Vasudev Kamath wrote:
>> On Wed, Apr 20, 2011 at 8:47 PM, Lucas Nussbaum
>>  wrote:
>> > On 19/04/11 at 23:21 +0530, Vasudev Kamath wrote:
>> >> Hi Lucas,
>> >> I made the changes you had told and have uploaded the package to
>> >> pkg-ruby-extras git repository[1]. Can you please review the package
>> >> and let me know If something needs to be fixed.
>> >>
>> >> [1] git+ssh://git.debian.org/git/pkg-ruby-extras/ruby-polyglot.git
>> >
>> > How did you push to alioth? You need to git push --all && git push --tags
>> Well I messed it up a bit :(.. Instead of following the guidelines on
>> the RubyInWheezy page I followed http://wiki.debian.org/Alioth/Git and
>> then used git-import-dsc to create repo from the .dsc of my package
>> (Actually I should have cloned empty repository and done this from
>> there).
>> >
>> > I don't see the upstream and pristine-tar branch.
>> I didn't use --all so upstream branch was on my system just now pushed
>> it but I forgot to give --pristine-tar option so that branch isn't
>> present :( Can I create that branch manually?
>
> You could just git push --all now, if you still have the local branch.
Yeah I did git push --all and upstream branch is pushed to the
pkg-ruby-extras/ruby-polyglot.git. But I don't have pristine-tar
branch since I missed that option while doing git-import-dsc.
This is what I'm thinking of doing let me know if it works
git checkout -b pristine-tar # create prisitine-tar branch manually
git rm -f * # Remove all files
pristine-tar commit -m "Adding pristine-tar version version."
../program_version.orig.tar.gz

then commit all changes I done to pristine-tar branch and again do a
git push -all. If this is fine I'll do this tonight. Let me know if
its proper. Got this idea from this post
http://documentation.debian-projects.org/other/debian-packaging-git/

Also I've to delete current debian/0.3.1-1 tag and retag it since I
modified control file and committed yesterday. I'll do this tonight

Thanks and Regards
>
> L.
>



-- 

Vasudev Kamath
http://vasudevkamath.blogspot.com
http://identi.ca/vasudev
http://twitter.com/vasudevkamath


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktin5sqagq-eefo8fvxr4bkvkyjx...@mail.gmail.com

Re: RFS: ruby-polyglot

[Lucas Nussbaum]

On 21/04/11 at 08:28 +0530, Vasudev Kamath wrote:
> On Thu, Apr 21, 2011 at 4:23 AM, Lucas Nussbaum
>  wrote:
> > On 20/04/11 at 21:51 +0530, Vasudev Kamath wrote:
> >> On Wed, Apr 20, 2011 at 8:47 PM, Lucas Nussbaum
> >>  wrote:
> >> > On 19/04/11 at 23:21 +0530, Vasudev Kamath wrote:
> >> >> Hi Lucas,
> >> >> I made the changes you had told and have uploaded the package to
> >> >> pkg-ruby-extras git repository[1]. Can you please review the package
> >> >> and let me know If something needs to be fixed.
> >> >>
> >> >> [1] git+ssh://git.debian.org/git/pkg-ruby-extras/ruby-polyglot.git
> >> >
> >> > How did you push to alioth? You need to git push --all && git push --tags
> >> Well I messed it up a bit :(.. Instead of following the guidelines on
> >> the RubyInWheezy page I followed http://wiki.debian.org/Alioth/Git and
> >> then used git-import-dsc to create repo from the .dsc of my package
> >> (Actually I should have cloned empty repository and done this from
> >> there).
> >> >
> >> > I don't see the upstream and pristine-tar branch.
> >> I didn't use --all so upstream branch was on my system just now pushed
> >> it but I forgot to give --pristine-tar option so that branch isn't
> >> present :( Can I create that branch manually?
> >
> > You could just git push --all now, if you still have the local branch.
> Yeah I did git push --all and upstream branch is pushed to the
> pkg-ruby-extras/ruby-polyglot.git. But I don't have pristine-tar
> branch since I missed that option while doing git-import-dsc.
> This is what I'm thinking of doing let me know if it works
> git checkout -b pristine-tar # create prisitine-tar branch manually
> git rm -f * # Remove all files
> pristine-tar commit -m "Adding pristine-tar version version."
> ../program_version.orig.tar.gz

Wouldn't it be easier to delete the upstream tag, and re-use git
import-orig, this time with pristine-tar?

Or simply to restart from scratch?

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110421051224.ga32...@xanadu.blop.info

Re: RFS: ruby-polyglot

[Vasudev Kamath]

On Thu, Apr 21, 2011 at 10:42 AM, Lucas Nussbaum
 wrote:
> On 21/04/11 at 08:28 +0530, Vasudev Kamath wrote:
>> On Thu, Apr 21, 2011 at 4:23 AM, Lucas Nussbaum
>>  wrote:
>> > On 20/04/11 at 21:51 +0530, Vasudev Kamath wrote:
>> >> On Wed, Apr 20, 2011 at 8:47 PM, Lucas Nussbaum
>> >>  wrote:
>> >> > On 19/04/11 at 23:21 +0530, Vasudev Kamath wrote:
>> >> >> Hi Lucas,
>> >> >> I made the changes you had told and have uploaded the package to
>> >> >> pkg-ruby-extras git repository[1]. Can you please review the package
>> >> >> and let me know If something needs to be fixed.
>> >> >>
>> >> >> [1] git+ssh://git.debian.org/git/pkg-ruby-extras/ruby-polyglot.git
>> >> >
>> >> > How did you push to alioth? You need to git push --all && git push 
>> >> > --tags
>> >> Well I messed it up a bit :(.. Instead of following the guidelines on
>> >> the RubyInWheezy page I followed http://wiki.debian.org/Alioth/Git and
>> >> then used git-import-dsc to create repo from the .dsc of my package
>> >> (Actually I should have cloned empty repository and done this from
>> >> there).
>> >> >
>> >> > I don't see the upstream and pristine-tar branch.
>> >> I didn't use --all so upstream branch was on my system just now pushed
>> >> it but I forgot to give --pristine-tar option so that branch isn't
>> >> present :( Can I create that branch manually?
>> >
>> > You could just git push --all now, if you still have the local branch.
>> Yeah I did git push --all and upstream branch is pushed to the
>> pkg-ruby-extras/ruby-polyglot.git. But I don't have pristine-tar
>> branch since I missed that option while doing git-import-dsc.
>> This is what I'm thinking of doing let me know if it works
>> git checkout -b pristine-tar # create prisitine-tar branch manually
>> git rm -f * # Remove all files
>> pristine-tar commit -m "Adding pristine-tar version version."
>> ../program_version.orig.tar.gz
>
> Wouldn't it be easier to delete the upstream tag, and re-use git
> import-orig, this time with pristine-tar?
Yeah I'll try this one
>
> Or simply to restart from scratch?
This will be last resort :)
>

Thanks :)
> - Lucas
>



-- 

Vasudev Kamath
http://vasudevkamath.blogspot.com
http://identi.ca/vasudev
http://twitter.com/vasudevkamath


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktimnsq-2upzdda-q93vqkk9qmyg...@mail.gmail.com

Re: RFS: ruby-bundle

[Hemanth H.M]

Hello hackers,
Facing issue packing, have attached the pbuilder log. Please have a look and
let me know, i added rubygems to deps list in the control file, but also.
rspec-rails (2.5.0)  is not there in debian yet, is that the issue? Thank
you in advance.


On Tue, Apr 19, 2011 at 10:32 AM, Lucas Nussbaum
wrote:

> On 19/04/11 at 10:12 +0530, Hemanth H.M wrote:
> > /me had got the results as attached, true the package name must be
> > bundle*r*, rather than bundle. We remove the current package and redo it,
> > thank you.
> >
> > Reconfirming steps :
> > Just gem2deb?
> > Or
> > gem fetch bundler, then gem2tgz, dh-make-ruby foo-1.2.tar.gz, edited the
> > copyrights and controls file and use pbuilder to create the deb, sign the
> > required files and then a dput?
>
> gem2deb is equivalent to:
> gem fetch, gem2tgz, dh-make-ruby.
> Then, you need to look at each file in debian/ and make the necessary
> change (possibly not just copyright and control). When the package is
> ready, dput it to mentors, so that we can review it, and then upload it
> to Debian (you can't upload directly to Debian yourself, you need to be
> a DD for that).
>
> Alternatively to uploading to mentors, you could add the package to the
> pkg-ruby-extras git repository, and we could review it from there. But
> maybe it's better to do a first package using mentors so we make sure
> we agree on that part of the process.
>
> - Lucas
>



-- 
*'I am what I am because of who we all are'*
h3manth.com 
*-- Hemanth HM *


pbuilder.log
Description: Binary data

Re: RFS: ruby-bundle

[Lucas Nussbaum]

On 22/04/11 at 23:03 +0530, Hemanth H.M wrote:
> Hello hackers,
> Facing issue packing, have attached the pbuilder log. Please have a look and
> let me know, i added rubygems to deps list in the control file, but also.
> rspec-rails (2.5.0)  is not there in debian yet, is that the issue? Thank
> you in advance.

rspec should be packaged using gem2deb, yes.

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110422174415.gb2...@xanadu.blop.info

Re: RFS: ruby-bcrypt

[Lucas Nussbaum]

On 22/04/11 at 21:25 +0530, Vasudev Kamath wrote:
> Dear mentors,
> 
> I am looking for a sponsor for my package "ruby-bcrypt".
> 
> * Package name: ruby-bcrypt
>   Version : 2.1.4-1
>   Upstream Author : Coda Hale 
> * URL : http://bcrypt-ruby.rubyforge.org/
> * License : BSD
>   Section : ruby
> 
> It builds these binary packages:
> ruby-bcrypt - Ruby binding for the bcrypt() password hashing algorithm
> 
> The upload would fix these bugs: 623597
> 
> My motivation for maintaining this package is: One of the dependency
> for Diaspora packaging
> 
> The package can be found on mentors.debian.net:
> - URL: http://mentors.debian.net/debian/pool/main/r/ruby-bcrypt
> - Source repository: deb-src http://mentors.debian.net/debian unstable
> main contrib non-free
> - dget 
> http://mentors.debian.net/debian/pool/main/r/ruby-bcrypt/ruby-bcrypt_2.1.4-1.dsc
> 
> I would be glad if someone uploaded this package for me.

Could you enable tests?
I think that this could require updating rspec to gem2deb packaging
(yes, I know it's an hard process, but it's something someone must do
anyway :( )

Otherwise, it looks good.

Thanks,

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110422175141.ga3...@xanadu.blop.info

Re: RFS: ruby-bcrypt

[Vasudev Kamath]

On Fri, Apr 22, 2011 at 11:21 PM, Lucas Nussbaum
 wrote:
> On 22/04/11 at 21:25 +0530, Vasudev Kamath wrote:
>> Dear mentors,
>>
>> I am looking for a sponsor for my package "ruby-bcrypt".
>>
>> * Package name    : ruby-bcrypt
>>   Version         : 2.1.4-1
>>   Upstream Author : Coda Hale 
>> * URL             : http://bcrypt-ruby.rubyforge.org/
>> * License         : BSD
>>   Section         : ruby
>>
>> It builds these binary packages:
>> ruby-bcrypt - Ruby binding for the bcrypt() password hashing algorithm
>>
>> The upload would fix these bugs: 623597
>>
>> My motivation for maintaining this package is: One of the dependency
>> for Diaspora packaging
>>
>> The package can be found on mentors.debian.net:
>> - URL: http://mentors.debian.net/debian/pool/main/r/ruby-bcrypt
>> - Source repository: deb-src http://mentors.debian.net/debian unstable
>> main contrib non-free
>> - dget 
>> http://mentors.debian.net/debian/pool/main/r/ruby-bcrypt/ruby-bcrypt_2.1.4-1.dsc
>>
>> I would be glad if someone uploaded this package for me.
>
> Could you enable tests?
Ok I've a doubt here. How do I enable the tests? Is it by providing
rspec in Depends? (It was there but it was commented out in control
file ). This may be a silly question but since I'm not a ruby guy I
may need a bit of help :)

> I think that this could require updating rspec to gem2deb packaging
> (yes, I know it's an hard process, but it's something someone must do
> anyway :( )
>
How can I help here. I saw the package is now named as librspec-ruby.
Also its not maitained by pkg-ruby-extras! Let me know

> Otherwise, it looks good.
>
> Thanks,
>
> - Lucas
>

Regards

-- 

Vasudev Kamath
http://vasudevkamath.blogspot.com
http://identi.ca/vasudev
http://twitter.com/vasudevkamath


--
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktinccxrdttpo8saeag0bruoouxr...@mail.gmail.com

Re: RFS: ruby-bundle

[Hemanth H.M]

So first repec must be packed and uploaded then this?

On Fri, Apr 22, 2011 at 11:14 PM, Lucas Nussbaum
 wrote:
> On 22/04/11 at 23:03 +0530, Hemanth H.M wrote:
>> Hello hackers,
>> Facing issue packing, have attached the pbuilder log. Please have a look and
>> let me know, i added rubygems to deps list in the control file, but also.
>> rspec-rails (2.5.0)  is not there in debian yet, is that the issue? Thank
>> you in advance.
>
> rspec should be packaged using gem2deb, yes.
>
> - Lucas
>



-- 
'I am what I am because of who we all are'
h3manth.com
-- Hemanth HM


--
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktikbsfnpphqwl7ib_ufaemu74-p...@mail.gmail.com

Re: RFS: ruby-bcrypt

[Lucas Nussbaum]

On 22/04/11 at 23:35 +0530, Vasudev Kamath wrote:
> On Fri, Apr 22, 2011 at 11:21 PM, Lucas Nussbaum
>  wrote:
> > On 22/04/11 at 21:25 +0530, Vasudev Kamath wrote:
> >> Dear mentors,
> >>
> >> I am looking for a sponsor for my package "ruby-bcrypt".
> >>
> >> * Package name    : ruby-bcrypt
> >>   Version         : 2.1.4-1
> >>   Upstream Author : Coda Hale 
> >> * URL             : http://bcrypt-ruby.rubyforge.org/
> >> * License         : BSD
> >>   Section         : ruby
> >>
> >> It builds these binary packages:
> >> ruby-bcrypt - Ruby binding for the bcrypt() password hashing algorithm
> >>
> >> The upload would fix these bugs: 623597
> >>
> >> My motivation for maintaining this package is: One of the dependency
> >> for Diaspora packaging
> >>
> >> The package can be found on mentors.debian.net:
> >> - URL: http://mentors.debian.net/debian/pool/main/r/ruby-bcrypt
> >> - Source repository: deb-src http://mentors.debian.net/debian unstable
> >> main contrib non-free
> >> - dget 
> >> http://mentors.debian.net/debian/pool/main/r/ruby-bcrypt/ruby-bcrypt_2.1.4-1.dsc
> >>
> >> I would be glad if someone uploaded this package for me.
> >
> > Could you enable tests?
> Ok I've a doubt here. How do I enable the tests? Is it by providing
> rspec in Depends? (It was there but it was commented out in control
> file ). This may be a silly question but since I'm not a ruby guy I
> may need a bit of help :)

You need to edit debian/ruby-tests.rb. See other packages that use
gem2deb in the git repo.

> > I think that this could require updating rspec to gem2deb packaging
> > (yes, I know it's an hard process, but it's something someone must do
> > anyway :( )
> >
> How can I help here. I saw the package is now named as librspec-ruby.
> Also its not maitained by pkg-ruby-extras! Let me know

It is maintained by pgk-ruby-extras, but not using gem2deb and git.
Also, it's severely outdated.

So it needs to be transitioned to gem2deb. See my mail on this list
earlier this week, in a discussion with Vincent Fourmond.

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110422181004.ga5...@xanadu.blop.info

Re: RFS: ruby-bundle

[Lucas Nussbaum]

On 22/04/11 at 23:37 +0530, Hemanth H.M wrote:
> So first repec must be packed and uploaded then this?

rspec, yes.

L.


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110422181049.ga5...@xanadu.blop.info

Re: RFS: ruby-bcrypt

[Vasudev Kamath]

On Fri, Apr 22, 2011 at 11:40 PM, Lucas Nussbaum
 wrote:
> On 22/04/11 at 23:35 +0530, Vasudev Kamath wrote:
>> On Fri, Apr 22, 2011 at 11:21 PM, Lucas Nussbaum
>>  wrote:
>> > On 22/04/11 at 21:25 +0530, Vasudev Kamath wrote:
>> >> Dear mentors,
>> >>
>> >> I am looking for a sponsor for my package "ruby-bcrypt".
>> >>
>> >> * Package name    : ruby-bcrypt
>> >>   Version         : 2.1.4-1
>> >>   Upstream Author : Coda Hale 
>> >> * URL             : http://bcrypt-ruby.rubyforge.org/
>> >> * License         : BSD
>> >>   Section         : ruby
>> >>
>> >> It builds these binary packages:
>> >> ruby-bcrypt - Ruby binding for the bcrypt() password hashing algorithm
>> >>
>> >> The upload would fix these bugs: 623597
>> >>
>> >> My motivation for maintaining this package is: One of the dependency
>> >> for Diaspora packaging
>> >>
>> >> The package can be found on mentors.debian.net:
>> >> - URL: http://mentors.debian.net/debian/pool/main/r/ruby-bcrypt
>> >> - Source repository: deb-src http://mentors.debian.net/debian unstable
>> >> main contrib non-free
>> >> - dget 
>> >> http://mentors.debian.net/debian/pool/main/r/ruby-bcrypt/ruby-bcrypt_2.1.4-1.dsc
>> >>
>> >> I would be glad if someone uploaded this package for me.
>> >
>> > Could you enable tests?
>> Ok I've a doubt here. How do I enable the tests? Is it by providing
>> rspec in Depends? (It was there but it was commented out in control
>> file ). This may be a silly question but since I'm not a ruby guy I
>> may need a bit of help :)
>
> You need to edit debian/ruby-tests.rb. See other packages that use
> gem2deb in the git repo.
Oh fine I'll do that.
>
>> > I think that this could require updating rspec to gem2deb packaging
>> > (yes, I know it's an hard process, but it's something someone must do
>> > anyway :( )
>> >
>> How can I help here. I saw the package is now named as librspec-ruby.
>> Also its not maitained by pkg-ruby-extras! Let me know
>
> It is maintained by pgk-ruby-extras, but not using gem2deb and git.
> Also, it's severely outdated.
>
> So it needs to be transitioned to gem2deb. See my mail on this list
> earlier this week, in a discussion with Vincent Fourmond.
Ok let me read through.
>
> - Lucas
>



-- 

Vasudev Kamath
http://vasudevkamath.blogspot.com
http://identi.ca/vasudev
http://twitter.com/vasudevkamath


--
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/BANLkTi=ske7hxnbklqopokp42azm8so...@mail.gmail.com

Re: RFS: ruby-bcrypt

[Lucas Nussbaum]

On 22/04/11 at 23:52 +0530, Vasudev Kamath wrote:
> On Fri, Apr 22, 2011 at 11:40 PM, Lucas Nussbaum
>  wrote:
> > On 22/04/11 at 23:35 +0530, Vasudev Kamath wrote:
> >> On Fri, Apr 22, 2011 at 11:21 PM, Lucas Nussbaum
> >>  wrote:
> >> > On 22/04/11 at 21:25 +0530, Vasudev Kamath wrote:
> >> >> Dear mentors,
> >> >>
> >> >> I am looking for a sponsor for my package "ruby-bcrypt".
> >> >>
> >> >> * Package name    : ruby-bcrypt
> >> >>   Version         : 2.1.4-1
> >> >>   Upstream Author : Coda Hale 
> >> >> * URL             : http://bcrypt-ruby.rubyforge.org/
> >> >> * License         : BSD
> >> >>   Section         : ruby
> >> >>
> >> >> It builds these binary packages:
> >> >> ruby-bcrypt - Ruby binding for the bcrypt() password hashing algorithm
> >> >>
> >> >> The upload would fix these bugs: 623597
> >> >>
> >> >> My motivation for maintaining this package is: One of the dependency
> >> >> for Diaspora packaging
> >> >>
> >> >> The package can be found on mentors.debian.net:
> >> >> - URL: http://mentors.debian.net/debian/pool/main/r/ruby-bcrypt
> >> >> - Source repository: deb-src http://mentors.debian.net/debian unstable
> >> >> main contrib non-free
> >> >> - dget 
> >> >> http://mentors.debian.net/debian/pool/main/r/ruby-bcrypt/ruby-bcrypt_2.1.4-1.dsc
> >> >>
> >> >> I would be glad if someone uploaded this package for me.
> >> >
> >> > Could you enable tests?
> >> Ok I've a doubt here. How do I enable the tests? Is it by providing
> >> rspec in Depends? (It was there but it was commented out in control
> >> file ). This may be a silly question but since I'm not a ruby guy I
> >> may need a bit of help :)
> >
> > You need to edit debian/ruby-tests.rb. See other packages that use
> > gem2deb in the git repo.
> Oh fine I'll do that.
> >
> >> > I think that this could require updating rspec to gem2deb packaging
> >> > (yes, I know it's an hard process, but it's something someone must do
> >> > anyway :( )
> >> >
> >> How can I help here. I saw the package is now named as librspec-ruby.
> >> Also its not maitained by pkg-ruby-extras! Let me know
> >
> > It is maintained by pgk-ruby-extras, but not using gem2deb and git.
> > Also, it's severely outdated.
> >
> > So it needs to be transitioned to gem2deb. See my mail on this list
> > earlier this week, in a discussion with Vincent Fourmond.
> Ok let me read through.

FYI, I've packaged and uploaded rspec 2.5.

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110426140009.ga9...@xanadu.blop.info

Re: RFS: ruby-bcrypt

[Vasudev Kamath]

Thanks.. I'll try to write up the test case and finish the ruby-bcrypt.

Regards

On Tue, Apr 26, 2011 at 7:30 PM, Lucas Nussbaum
 wrote:
> On 22/04/11 at 23:52 +0530, Vasudev Kamath wrote:
>> On Fri, Apr 22, 2011 at 11:40 PM, Lucas Nussbaum
>>  wrote:
>> > On 22/04/11 at 23:35 +0530, Vasudev Kamath wrote:
>> >> On Fri, Apr 22, 2011 at 11:21 PM, Lucas Nussbaum
>> >>  wrote:
>> >> > On 22/04/11 at 21:25 +0530, Vasudev Kamath wrote:
>> >> >> Dear mentors,
>> >> >>
>> >> >> I am looking for a sponsor for my package "ruby-bcrypt".
>> >> >>
>> >> >> * Package name    : ruby-bcrypt
>> >> >>   Version         : 2.1.4-1
>> >> >>   Upstream Author : Coda Hale 
>> >> >> * URL             : http://bcrypt-ruby.rubyforge.org/
>> >> >> * License         : BSD
>> >> >>   Section         : ruby
>> >> >>
>> >> >> It builds these binary packages:
>> >> >> ruby-bcrypt - Ruby binding for the bcrypt() password hashing algorithm
>> >> >>
>> >> >> The upload would fix these bugs: 623597
>> >> >>
>> >> >> My motivation for maintaining this package is: One of the dependency
>> >> >> for Diaspora packaging
>> >> >>
>> >> >> The package can be found on mentors.debian.net:
>> >> >> - URL: http://mentors.debian.net/debian/pool/main/r/ruby-bcrypt
>> >> >> - Source repository: deb-src http://mentors.debian.net/debian unstable
>> >> >> main contrib non-free
>> >> >> - dget 
>> >> >> http://mentors.debian.net/debian/pool/main/r/ruby-bcrypt/ruby-bcrypt_2.1.4-1.dsc
>> >> >>
>> >> >> I would be glad if someone uploaded this package for me.
>> >> >
>> >> > Could you enable tests?
>> >> Ok I've a doubt here. How do I enable the tests? Is it by providing
>> >> rspec in Depends? (It was there but it was commented out in control
>> >> file ). This may be a silly question but since I'm not a ruby guy I
>> >> may need a bit of help :)
>> >
>> > You need to edit debian/ruby-tests.rb. See other packages that use
>> > gem2deb in the git repo.
>> Oh fine I'll do that.
>> >
>> >> > I think that this could require updating rspec to gem2deb packaging
>> >> > (yes, I know it's an hard process, but it's something someone must do
>> >> > anyway :( )
>> >> >
>> >> How can I help here. I saw the package is now named as librspec-ruby.
>> >> Also its not maitained by pkg-ruby-extras! Let me know
>> >
>> > It is maintained by pgk-ruby-extras, but not using gem2deb and git.
>> > Also, it's severely outdated.
>> >
>> > So it needs to be transitioned to gem2deb. See my mail on this list
>> > earlier this week, in a discussion with Vincent Fourmond.
>> Ok let me read through.
>
> FYI, I've packaged and uploaded rspec 2.5.
>
> - Lucas
>



-- 

Vasudev Kamath
http://vasudevkamath.blogspot.com
http://identi.ca/vasudev
http://twitter.com/vasudevkamath


--
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktinb7pnjb_4hrosjs7tfkfdyo1x...@mail.gmail.com

Re: RFS: ruby-globalhotkeys

[Lucas Nussbaum]

On 30/04/11 at 02:59 +0200, Vincent Carmona wrote:
> Hi.
> 
> I have update ruby-globalhotkeys repo.
> A quilt patch is added so require call loads globalhotkeys.rb file and so 
> file.
> It fixes a serious bug.
> Should I filled a debian bug and closes it or is it ok to upload this
> new version (0.3.2-3) as it is in git repo ?

It is OK to upload, no need to file a bug for that (it would have been
useful during a freeze to document the problem, but it is not needed
right now).

Uploaded.

Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110501165400.gc17...@xanadu.blop.info

Re: RFS: ruby-capybara

[Lucas Nussbaum]

On 30/04/11 at 14:03 +0530, Nishchay Mhatre wrote:
>1. Package: Ruby Capybara
>2. License:GPL v2
>3. Capybara is an intelligent systems integrator for Rack
>applications.Intelligent Rack application testing tool.
> Capybara aims to simplify the process of integration
> testing Rack applications, such as Rails, Sinatra or
> Merb. Capybara is an integration testing tool for rack
> based web applications. It simulates how a user would
> interact with a website.
>4. Package available at:
>http://mentors.debian.net/debian/pool/main/r/ruby-capybara

Hi,

Quick review:
debian/copyright contains incorrect copyright info for capybara.
debian/control: you need to uncomment or remove the comment lines
see FIXME in ruby-capybara.docs and ruby-tests.rb

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110501170409.gb21...@xanadu.blop.info

Re: RFS: ruby-bunny

[Lucas Nussbaum]

On 04/05/11 at 05:12 -0400, Varad Deshmukh wrote:
> Dear mentors,
> 
> I am looking for a sponsor for my package "ruby-bunny".
> 
> * Package name: ruby-bunny
>   Version : 0.6.0-1
>   Upstream Author : Chris Duncan 
> 
>   URL : https://github.com/celldee/bunny
> * License : MIT
>   Section : ruby
> 
> It builds these binary packages:
> ruby-bunny - A synchronous Ruby AMQP client.
> 
> The upload would fix these bugs: 624614
> 
> My motivation for maintaining this package is: Wanting to be a part of Debian.

Can you confirm that your motivation for packaging this is that you want
this software to be part of Debian, and not yourself to be part of
Debian?
If your motivation is to contribute to Debian, I would love to sponsor
one of the packages that need migration from ruby-pkg-tools to gem2deb
(see http://pkg-ruby-extras.alioth.debian.org/wheezy/details.html)
:-)

> The package can be found on mentors.debian.net:
> 
> - URL: http://mentors.debian.net/debian/pool/main/r/ruby-bunny
> - Source repository: deb-src http://mentors.debian.net/debian unstable
> main contrib non-free
> 
> - dget 
> http://mentors.debian.net/debian/pool/main/r/ruby-bunny/ruby-bunny_0.6.0-1.dsc

Review:
- There's a "2" file in debian/ that shouldn't be there
- There's an empty line in changelog
- Do you really want to maintain it on your own? Why not join the
  pkg-ruby-extras team? (if you want to join the team, add it as
  Maintainer and set you as Uploaders, and uncomment the Vcs-* lines)
- shouldn't homepage be https://github.com/celldee/bunny ?
- Description: what's AMQP ?
- trailing whitespace in control
- You should have a Files: debian/* paragraph in copyright (see other
  packages)
- address FIXMEs in ruby-bunny.docs  ruby-bunny.examples  ruby-tests.rb
  (enable tests)

  - Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110504092940.ga6...@xanadu.blop.info

Re: RFS: ruby-bunny

[Lucas Nussbaum]

(Please Cc -ruby@)

On 04/05/11 at 11:22 -0400, Varad Deshmukh wrote:
> Hi,
> I have replied to your corrections at the corresponding points.
> Should I also send another RFS with corrections? For example, the
> URL is wrong there also.

No, not needed.

> On Wed, May 4, 2011 at 5:29 AM, Lucas Nussbaum 
> wrote:
> 
> > On 04/05/11 at 05:12 -0400, Varad Deshmukh wrote:
> > > Dear mentors,
> > >
> > > I am looking for a sponsor for my package "ruby-bunny".
> > >
> > > * Package name: ruby-bunny
> > >   Version : 0.6.0-1
> > >   Upstream Author : Chris Duncan 
> > >
> > >   URL : https://github.com/celldee/bunny
> > > * License : MIT
> > >   Section : ruby
> > >
> > > It builds these binary packages:
> > > ruby-bunny - A synchronous Ruby AMQP client.
> > >
> > > The upload would fix these bugs: 624614
> > >
> > > My motivation for maintaining this package is: Wanting to be a part of
> > Debian.
> >
> > Can you confirm that your motivation for packaging this is that you want
> > this software to be part of Debian, and not yourself to be part of
> > Debian?
> >
> 
> My motivation is that 'I' want to a part of Debian maintenance.
> 
> 
> > If your motivation is to contribute to Debian, I would love to sponsor
> > one of the packages that need migration from ruby-pkg-tools to gem2deb
> > (see http://pkg-ruby-extras.alioth.debian.org/wheezy/details.html)
> > :-)
> >
> > > The package can be found on mentors.debian.net:
> > >
> > > - URL: http://mentors.debian.net/debian/pool/main/r/ruby-bunny
> > > - Source repository: deb-src http://mentors.debian.net/debian unstable
> > > main contrib non-free
> > >
> > > - dget
> > http://mentors.debian.net/debian/pool/main/r/ruby-bunny/ruby-bunny_0.6.0-1.dsc
> >
> >
> I have corrected the changes you have mentioned except the last one -
> changing the FIXME's.
> Will do that soon.

OK, waiting for that, before doing another review.

L.


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110505084041.ga13...@xanadu.blop.info

Re: RFS: ruby-cairo

[Lucas Nussbaum]

On 19/06/11 at 19:44 -0700, Antonio Terceiro wrote:
> The package is in our git repository:
> git.debian.org:/git/pkg-ruby-extras/ruby-cairo.git
> 
> This is another build dependency of ruby-gnome2

Replaces: libcairo-ruby (<< 0.1.0~FIXME-1~), libcairo-ruby1.8 (<<
0.1.0~FIXME-1~)
Breaks: libcairo-ruby (<< 0.1.0~FIXME-1~), libcairo-ruby1.8 (<<
0.1.0~FIXME-1~)

? :)

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110620053839.gb28...@xanadu.blop.info

Re: RFS: ruby-cairo

[Antonio Terceiro]

Lucas Nussbaum escreveu isso aí:
> On 19/06/11 at 19:44 -0700, Antonio Terceiro wrote:
> > The package is in our git repository:
> > git.debian.org:/git/pkg-ruby-extras/ruby-cairo.git
> > 
> > This is another build dependency of ruby-gnome2
> 
> Replaces: libcairo-ruby (<< 0.1.0~FIXME-1~), libcairo-ruby1.8 (<<
> 0.1.0~FIXME-1~)
> Breaks: libcairo-ruby (<< 0.1.0~FIXME-1~), libcairo-ruby1.8 (<<
> 0.1.0~FIXME-1~)

argh! Damn boilerplate content ... it's fixed now in git.

-- 
Antonio Terceiro 
http://softwarelivre.org/terceiro




signature.asc
Description: Digital signature

Re: RFS: ruby-cairo

[Lucas Nussbaum]

On 20/06/11 at 12:08 -0700, Antonio Terceiro wrote:
> Lucas Nussbaum escreveu isso aí:
> > On 19/06/11 at 19:44 -0700, Antonio Terceiro wrote:
> > > The package is in our git repository:
> > > git.debian.org:/git/pkg-ruby-extras/ruby-cairo.git
> > > 
> > > This is another build dependency of ruby-gnome2
> > 
> > Replaces: libcairo-ruby (<< 0.1.0~FIXME-1~), libcairo-ruby1.8 (<<
> > 0.1.0~FIXME-1~)
> > Breaks: libcairo-ruby (<< 0.1.0~FIXME-1~), libcairo-ruby1.8 (<<
> > 0.1.0~FIXME-1~)
> 
> argh! Damn boilerplate content ... it's fixed now in git.

Uploaded, thanks!

L.


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110621052930.ga14...@xanadu.blop.info

Re: RFS: ruby-lapack

[Youhei SASAKI]

Hi, 

> At 6 Apr 2011 14:09:48 +0200,
> "Lucas Nussbaum"  wrote:
> 
> > would it make sense to run the sample script at the end of the build, to
> > see if everything works fine? I'm a bit disturbed by the lack of test
> > suite.
 - snip -
> Ok. I'll create some test suite. Please wait for a while...

We (upstream author and me) create test suite about this library.
Could you please sponsor them?

  Vcs-git: git://git.debian.org/pkg-ruby-extras/ruby-lapack.git
  Vcs-Browser: http://git.debian.org/?p=pkg-ruby-extras/ruby-lapack;a=summary

  source: ruby-lapack
  packages:
   - ruby-lapack: library and documents
   - ruby-lapack-dbg: debug symbols

Best Wishes,
---
Youhei SASAKI 
  
GPG fingerprint:
  4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/871uxmnjto.wl%uwab...@gfd-dennou.org

Re: RFS: ruby-lapack

[Lucas Nussbaum]

On 20/07/11 at 04:37 +0900, Youhei SASAKI wrote:
> Hi, 
> 
> > At 6 Apr 2011 14:09:48 +0200,
> > "Lucas Nussbaum"  wrote:
> > 
> > > would it make sense to run the sample script at the end of the build, to
> > > see if everything works fine? I'm a bit disturbed by the lack of test
> > > suite.
>  - snip -
> > Ok. I'll create some test suite. Please wait for a while...
> 
> We (upstream author and me) create test suite about this library.
> Could you please sponsor them?

Do you mean that you have created it (but I don't find it in the git
repo), or that you will create it in the future, but that I should
sponsor the package in the meantime ?

Thank you,

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110720085905.ga25...@xanadu.blop.info

Re: RFS: ruby-lapack

[Youhei SASAKI]

Hi, lucas

At 20 Jul 2011 10:59:05 +0200,
"Lucas Nussbaum"  wrote:
- snip -
>
> > We (upstream author and me) create test suite about this library.
> > Could you please sponsor them?
> 
> Do you mean that you have created it (but I don't find it in the git
> repo), 
- snip 

Really? 

I already commit whole changes. Please check Git tag "debian/1.5-1".

Best Wishes,
---
Youhei SASAKI 
  
GPG fingerprint:
  4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/871uxjewiq.wl%uwab...@gfd-dennou.org

Re: RFS: ruby-lapack

[Lucas Nussbaum]

On 21/07/11 at 19:52 +0900, Youhei SASAKI wrote:
> Hi, lucas
> 
> At 20 Jul 2011 10:59:05 +0200,
> "Lucas Nussbaum"  wrote:
> - snip -
> >
> > > We (upstream author and me) create test suite about this library.
> > > Could you please sponsor them?
> > 
> > Do you mean that you have created it (but I don't find it in the git
> > repo), 
> - snip 
> 
> Really? 
> 
> I already commit whole changes. Please check Git tag "debian/1.5-1".

thanks, uploaded and pushed.

Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110724150645.gc5...@xanadu.blop.info

Re: RFS: ruby-hikidoc

[Lucas Nussbaum]

On 21/07/11 at 20:24 +0900, Youhei SASAKI wrote:
> Hi,
> 
> The following packages are ready to be uploaded.
> Could you please sponsor them?
> 
>   Vcs-Git: git://git.debian.org/pkg-ruby-extras/ruby-hikidoc.git
>   Vcs-Browser: 
> http://git.debian.org/?p=pkg-ruby-extras/ruby-hikidoc.git;a=summary
> 
>   source: ruby-hikidoc
>   packages:
>- ruby-hikidoc

Hi,

I guess you have seen
http://lists.debian.org/debian-ruby/2011/07/msg00025.html ?

Thanks,

- Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110724141155.gb5...@xanadu.blop.info

Re: RFS: ruby-hikidoc

[Youhei SASAKI]

Hi,

At 24 Jul 2011 16:11:55 +0200,
"Lucas Nussbaum"  wrote:
> > The following packages are ready to be uploaded.
> > Could you please sponsor them?
> > 
> >   Vcs-Git: git://git.debian.org/pkg-ruby-extras/ruby-hikidoc.git
> >   Vcs-Browser: 
> > http://git.debian.org/?p=pkg-ruby-extras/ruby-hikidoc.git;a=summary
> 
> Hi,
> 
> I guess you have seen
> http://lists.debian.org/debian-ruby/2011/07/msg00025.html ?

Ok.  I'll try to fix these task as far as possible.

Thanks,
---
Youhei SASAKI 
  
GPG fingerprint:
  4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87fwlvu2ir.wl%uwab...@gfd-dennou.org

Re: RFS: ruby-lapack

[Youhei SASAKI]

Hi, Lucas,

At 24 Jul 2011 17:06:45 +0200,
"Lucas Nussbaum"  wrote:
> 
> On 21/07/11 at 19:52 +0900, Youhei SASAKI wrote:
> > > > We (upstream author and me) create test suite about this library.
> > > > Could you please sponsor them?
> > > 
> > > Do you mean that you have created it (but I don't find it in the git
> > > repo), 
> > - snip 
> > 
> > Really? 
> > 
> > I already commit whole changes. Please check Git tag "debian/1.5-1".
> 
> thanks, uploaded and pushed.

Thank you so much!
---
Youhei SASAKI 
  
GPG fingerprint:
  4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/874o2acszb.wl%uwab...@gfd-dennou.org

Re: RFS: ruby-hikidoc

[Lucas Nussbaum]

On 25/07/11 at 00:22 +0900, Youhei SASAKI wrote:
> Hi,
> 
> At 24 Jul 2011 16:11:55 +0200,
> "Lucas Nussbaum"  wrote:
> > > The following packages are ready to be uploaded.
> > > Could you please sponsor them?
> > > 
> > >   Vcs-Git: git://git.debian.org/pkg-ruby-extras/ruby-hikidoc.git
> > >   Vcs-Browser: 
> > > http://git.debian.org/?p=pkg-ruby-extras/ruby-hikidoc.git;a=summary
> > 
> > Hi,
> > 
> > I guess you have seen
> > http://lists.debian.org/debian-ruby/2011/07/msg00025.html ?
> 
> Ok.  I'll try to fix these task as far as possible.

ruby-hikidoc uploaded, thanks!

By my record, ruby-ole is the only package from you still waiting for
sponsorship, but I'll let Antonio handle it since he already looked at
it.

Your help on the other packages has also been very much appreciated.
Please don't stop here and continue to help with maintaining the Ruby
packages! We need you! ;)

Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110728064814.gc20...@xanadu.blop.info

Re: RFS: ruby-hikidoc

[Youhei SASAKI]

Hi, Lucas,

At 28 Jul 2011 08:48:14 +0200,
"Lucas Nussbaum"  wrote:
> 
> On 25/07/11 at 00:22 +0900, Youhei SASAKI wrote:
> 
> ruby-hikidoc uploaded, thanks!

Thanks!!
 
> By my record, ruby-ole is the only package from you still waiting for
> sponsorship, but I'll let Antonio handle it since he already looked at
> it.

Ok. I wait Antonio's check.
 
> Your help on the other packages has also been very much appreciated.
> Please don't stop here and continue to help with maintaining the Ruby
> packages! We need you! ;)

---
Youhei SASAKI 
  
GPG fingerprint:
  4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/8762mmg6h6.wl%uwab...@gfd-dennou.org

Re: RFS: ruby-bluecloth

[Antonio Terceiro]

Cédric Boutillier escreveu isso aí:
> Hi!
> 
> I have just joined the team and I am working on my first ruby package: 
> ruby-bluecloth.
> I think the package is (almost?) ready. I have checked that it builds
> fine and works in a clean chroot environment.
> 
> I have not enabled the test since they all need ruby-tidy, which is not
> packaged at the moment. The tests contain some "require "rubygems" but I
> believe it is ok. Am I right?

When you are building in a clean chroot environment it is ok because
there will be no gems installed, but you need to take care when building
outside of a chroot to make sure the build did not use libraries
installed by rubygems -- you want to amek sure it works with
Debian-installed Ruby packages only.

> I have a few questions still:
> 
> 1/ I produced a simple manpage with pod2man. Is there a better way to
> produce simple manpages? Any tool on which the team agreed on?

IMO pod2man is good enough. That's what we use in gem2deb. Since pod2man
is part of perl and perl already comes in as a build dependency because
of debhelper, there is no extra dependency needed.

> 2/ Most of the tests contain a BEGIN {} block to change the LOAD_PATH
> to include some directory. This causes segfaults when running tests for
> ruby1.8, because the tests load from that directory a binary extension
> built for ruby1.9.1. When the dependencies for running the tests are
> available, should I create patch(es) to comment all these blocks, or is
> there a better/lighter way to do it?

I do not see other way of fixing this without patching the tests.
Ideally it would be nice to talk to upstream to get these patches also
applied by them, but keep in mind that no all Ruby upstreams understand
(or care) about Debian needs.

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Re: RFS: ruby-bluecloth

[Antonio Terceiro]

Antonio Terceiro escreveu isso aí:
> Cédric Boutillier escreveu isso aí:
> > Hi!
> > 
> > I have just joined the team and I am working on my first ruby package: 
> > ruby-bluecloth.
> > I think the package is (almost?) ready. I have checked that it builds
> > fine and works in a clean chroot environment.

After looking at the git repo ...

> > 1/ I produced a simple manpage with pod2man. Is there a better way to
> > produce simple manpages? Any tool on which the team agreed on?
> 
> IMO pod2man is good enough. That's what we use in gem2deb. Since pod2man
> is part of perl and perl already comes in as a build dependency because
> of debhelper, there is no extra dependency needed.

IMO it's better to keep the manpage in pod format in the source package
and generate the .1 file during package build, and remove it when
cleaning, than storing troff code in the repository since that is pretty
much gibberish for normal people.  :-)

When I convert existing packages I usually keep the original maintainers
as uploaders together with me, I don't known what others think about
that but I think this is a good thing to do.

lintian reports a spelling error in the manpage text, you could fix
that.

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Re: RFS: ruby-bluecloth

[Cédric Boutillier]

Hi Augusto!

On Thu, Aug 11, 2011 at 10:05:40AM -0700, Antonio Terceiro wrote:

> IMO it's better to keep the manpage in pod format in the source package
> and generate the .1 file during package build, and remove it when
> cleaning, than storing troff code in the repository since that is pretty
> much gibberish for normal people.  :-)

> When I convert existing packages I usually keep the original maintainers
> as uploaders together with me, I don't known what others think about
> that but I think this is a good thing to do.

> lintian reports a spelling error in the manpage text, you could fix
> that.

Thank you for your comments.

I followed your recommendations. I also added two patches to remove rubygems
requirements and $LOAD_PATH modifications in the tests, which are still
deactivated, waiting for depencies.

In the mean time, I think I slightly messed up with the git history. Sorry for
that :(

What do you think of the state of the package now?

Best regards,

Cédric



signature.asc
Description: Digital signature

Re: RFS: ruby-bluecloth

[Antonio Terceiro]

Cédric Boutillier escreveu isso aí:
> Hi Augusto!
> 
> On Thu, Aug 11, 2011 at 10:05:40AM -0700, Antonio Terceiro wrote:
> 
> > IMO it's better to keep the manpage in pod format in the source package
> > and generate the .1 file during package build, and remove it when
> > cleaning, than storing troff code in the repository since that is pretty
> > much gibberish for normal people.  :-)
> 
> > When I convert existing packages I usually keep the original maintainers
> > as uploaders together with me, I don't known what others think about
> > that but I think this is a good thing to do.
> 
> > lintian reports a spelling error in the manpage text, you could fix
> > that.
> 
> Thank you for your comments.
> 
> I followed your recommendations. I also added two patches to remove rubygems
> requirements and $LOAD_PATH modifications in the tests, which are still
> deactivated, waiting for depencies.
> 
> In the mean time, I think I slightly messed up with the git history. Sorry for
> that :(
> 
> What do you think of the state of the package now?

It looks like a lot of -- if not all -- files in ext/ are actually
'Copyright (C) 2007 David L Parsons', so debian/copyrigh must have an
entry for those files.

Also, you added a patch to remove the $LOAD_PATH manipulation mess in
the tests, but you didn't enable them to run at build time:
debian/ruby-tests.rb is all commented out.

Other thing: you added patches that are not applied in the Git
repository, so you need to make sure they are unapplied after build
(otherwise you cannot build the package again with git-buildpackage, for
example). See for example point 2 in Raphael's tips post:

https://raphaelhertzog.com/2010/11/18/4-tips-to-maintain-a-3-0-quilt-debian-source-package-in-a-vcs/

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Re: RFS: ruby-bluecloth

[Cédric Boutillier]

Hi!

On Sun, Aug 14, 2011 at 07:35:53PM -0700, Antonio Terceiro wrote:

> It looks like a lot of -- if not all -- files in ext/ are actually
> 'Copyright (C) 2007 David L Parsons', so debian/copyrigh must have an
> entry for those files.

I overlooked this indeed. I updated debian/copyright to correct the
copyright assignment to all files in ext/ except extconf.*, blucloth.*
and Makefile.

> Also, you added a patch to remove the $LOAD_PATH manipulation mess in
> the tests, but you didn't enable them to run at build time:
> debian/ruby-tests.rb is all commented out.

The problem is that the test suite cannot run because of missing
dependencies (in particular ruby-tidy). It was meant to be a preliminary
step when/if the dependencies are made available. But maybe I should
have not added the patches in the first place. Maybe can I just leave
them in the repository and comment them in debian/patches/series?
Or should I try to package the dependencies?

> Other thing: you added patches that are not applied in the Git
> repository, so you need to make sure they are unapplied after build
> (otherwise you cannot build the package again with git-buildpackage, for
> example). See for example point 2 in Raphael's tips post:

> https://raphaelhertzog.com/2010/11/18/4-tips-to-maintain-a-3-0-quilt-debian-source-package-in-a-vcs/

Thanks for the reference. I made the modification.


Best regards,

Cédric


signature.asc
Description: Digital signature

Re: RFS: ruby-bluecloth

[Antonio Terceiro]

Cédric Boutillier escreveu isso aí:
> Hi!
> 
> On Sun, Aug 14, 2011 at 07:35:53PM -0700, Antonio Terceiro wrote:
> 
> > It looks like a lot of -- if not all -- files in ext/ are actually
> > 'Copyright (C) 2007 David L Parsons', so debian/copyrigh must have an
> > entry for those files.
> 
> I overlooked this indeed. I updated debian/copyright to correct the
> copyright assignment to all files in ext/ except extconf.*, blucloth.*
> and Makefile.

Nice.

> > Also, you added a patch to remove the $LOAD_PATH manipulation mess in
> > the tests, but you didn't enable them to run at build time:
> > debian/ruby-tests.rb is all commented out.
> 
> The problem is that the test suite cannot run because of missing
> dependencies (in particular ruby-tidy). It was meant to be a preliminary
> step when/if the dependencies are made available. But maybe I should
> have not added the patches in the first place.

Yes, that was what I thought. :)

> Maybe can I just leave them in the repository and comment them in
> debian/patches/series?  Or should I try to package the dependencies?

I guess we want to push the "run tests during build" culture, so yes, we
should try to package the dependencies.

There is an existing libtidy-ruby package, and I was able to run the
ruby-bluecloth tests for Ruby 1.8 here with libtidy-ruby1.8 installed.
Let's do the following: for now, we build-depend on libtidy-ruby1.8,
ignore the test failure on 1.9 and upload the package.

After that you talk to the libtidy-ruby maintainer about upgrading it to
the new policy, and maybe moving it under the team's umbrella.

The next step would be to change the build-dependency to ruby-tidy, and
stop ignoring the test failure on Ruby 1.9, and upload an updated
ruby-blucloth.

What do you think?

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Re: RFS: ruby-bluecloth

[Cédric Boutillier]

Hi Augusto

On Thu, Aug 18, 2011 at 11:20:27AM -0700, Antonio Terceiro wrote:
[...]
> I guess we want to push the "run tests during build" culture, so yes, we
> should try to package the dependencies.

> There is an existing libtidy-ruby package, and I was able to run the
> ruby-bluecloth tests for Ruby 1.8 here with libtidy-ruby1.8 installed.
> Let's do the following: for now, we build-depend on libtidy-ruby1.8,
> ignore the test failure on 1.9 and upload the package.

> After that you talk to the libtidy-ruby maintainer about upgrading it to
> the new policy, and maybe moving it under the team's umbrella.

> The next step would be to change the build-dependency to ruby-tidy, and
> stop ignoring the test failure on Ruby 1.9, and upload an updated
> ruby-blucloth.

> What do you think?


I enabled the test suite for ruby1.8, and added a Build-depends: and a
Suggests: to libtidy-ruby. I got confused by the fact that this
package was not on the list of packaged maintained by the team (sic!).
The tests now run ok.  I will contact the maintainer of libtidy-ruby.
Thank you for your advice.

Best regards,

Cédric


signature.asc
Description: Digital signature

Re: RFS: ruby-bluecloth

[Antonio Terceiro]

Cédric Boutillier escreveu isso aí:
> I enabled the test suite for ruby1.8, and added a Build-depends: and a
> Suggests: to libtidy-ruby. I got confused by the fact that this
> package was not on the list of packaged maintained by the team (sic!).
> The tests now run ok.  I will contact the maintainer of libtidy-ruby.
> Thank you for your advice.

The package was missing a build dependency on ruby-rspec:

/usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby 
/usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb
./spec/bluecloth_spec.rb:16:in `require': no such file to load -- rspec 
(LoadError)
from ./spec/bluecloth_spec.rb:16
from debian/ruby-tests.rb:7:in `require'
from debian/ruby-tests.rb:7
from debian/ruby-tests.rb:7:in `each'
from debian/ruby-tests.rb:7
ERROR: Test "ruby1.8" failed. Exiting.
dh_auto_install: dh_ruby --install /tmp/buildd/ruby-bluecloth-2.1.0/debian/tmp 
returned exit code 1
make: *** [binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Failed autobuilding of package

You can catch this type of error by building packages under a clean chroot
(e.g. with `git buildpackage --git-pbuilder`)

I've added the build dependency and uploaded the package.

Regards,

(not Augusto)

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Re: RFS: ruby-hpricot

[Lucas Nussbaum]

On 19/08/11 at 12:59 +0200, Cédric Boutillier wrote:
> Hi!
> 
> I have just pushed to the git repository a proposition for ruby-hpricot
> packaging. The packages built are lintian clean and all the tests
> (except a deprecated benchmark against nokogiri) run without errors.
> 
> Would somebody have a look?

Looks good, uploaded.

Thanks

Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110822054950.gc6...@xanadu.blop.info

Re: RFS: ruby-markaby

[Praveen A]

Hi Cedric,

Thanks for your contribution. My comments.

1. Build is failing with 'cannot load such file -- test/unit/autorunner
(LoadError)'. Do you have test-unit installed locally? I suggest you use
pbuilder to catch this type of errors.

2. http://raa.ruby-lang.org/project/markaby mentions its license is same as
that of ruby's.

3. Your dep5 format url is not working. Use dep.debian.net url

Thanks
Praveen

On Sep 2, 2011 6:42 PM, "Cédric Boutillier" 
wrote:

Hi!

[By error I first sent this message to
pkg-ruby-extras-maintain...@lists.alioth.debian.org.]

I prepared a new version of ruby-markaby package, and pushed it to the
repository. I used the cop...

Re: RFS: ruby-markaby

[Cédric Boutillier]

Hi Praveen,

Thank you for your comments.

On Sat, Sep 03, 2011 at 11:05:03AM +0530, Praveen A wrote:

> 1. Build is failing with 'cannot load such file -- test/unit/autorunner
> (LoadError)'. Do you have test-unit installed locally? I suggest you use
> pbuilder to catch this type of errors.

The patch 03_no_require_test_unit_autorunner.diff is supposed to take
care about this because test/unit/autorunner is not present in the
standard ruby1.9.1 library. To check, I cloned again the git repo, did a
git-buildpackage --git-pbuilder and did not encounter any error.

> 2. http://raa.ruby-lang.org/project/markaby mentions its license is
> same as that of ruby's.

This is the website hosting version 0.4 of markaby. Version 0.5 is
hosted on rubyforge, but does not contain any info about the licence.
This version 0.5 was packaged by Paul van Tilburg where the MIT license
was indicated. Paul, if you read this, could you indicate where you get
the licence from?

> 3. Your dep5 format url is not working. Use dep.debian.net url

Indeed. This url was generated automatically by gem2deb. It is not clear
for me that we should use dep.debian.net right now. Althought dep-5 is
frozen, its status is just candidate, and not accepted yet. The example
given in DEP-5 refers to a version of the markdown file kept in the svn rep=
ository.
The problem with the url generated by gemdeb seems to come from the
op=file operand, which probably worked with wsvn, but does not with
viewvc. Changing it to view=co solves this issue, and allows to refer to
a specific version of this standard.

I have change the url for ruby-markaby in the repository.

A lot of other packages are affected by this problem (list below).
Should we consider a massive patching of the copyright files to have a
working url? In the mean time, the url should be corrected on line 432
of /usr/lib/ruby/vendor_ruby/gem2deb/dh_make_ruby.rb

Best wishes,

Cédric


list of affected packages with buggy Format: url in copyright:
--
$ grep -R -e"^Format:.*op=3Dfile" **/debian/copyright | cut -d/ -f1
addressable-ruby
cucumber
imagetooth
ruby-actionmailer-2.3
ruby-actionpack-2.3
ruby-activerecord-2.3
ruby-activeresource-2.3
ruby-activesupport-2.3
ruby-activesupport-dont-use
ruby-ascii85
ruby-barby
ruby-bio
ruby-bluecloth
ruby-cairo
ruby-cmdparse
ruby-color-tools
ruby-event-loop
ruby-ferret
rubygems
ruby-gherkin
ruby-gnuplot
ruby-gruff
ruby-hoe
ruby-hpricot
ruby-httpclient
ruby-ipaddress
ruby-json
ruby-liquid
ruby-log4r
ruby-markaby
ruby-minitest
ruby-mocha
ruby-net-ldap
ruby-ogginfo
ruby-ole
ruby-peach
ruby-pkg-config
ruby-policy
ruby-rails-2.3
ruby-rchardet
ruby-rmagick
ruby-rqrcode
ruby-rspec-core
ruby-rspec
ruby-rspec-expectations
ruby-rspec-mocks
ruby-shoulda-context
ruby-shoulda
ruby-shoulda-matchers
ruby-spreadsheet
ruby-taglib2
ruby-termios
ruby-test-declarative
ruby-tilt
ruby-tmail
ruby-transaction-simple
ruby-will-paginate
ruby-wirble


signature.asc
Description: Digital signature

Re: RFS: ruby-markaby

[Antonio Terceiro]

Cédric Boutillier escreveu isso aí:
> > 2. http://raa.ruby-lang.org/project/markaby mentions its license is
> > same as that of ruby's.
> 
> This is the website hosting version 0.4 of markaby. Version 0.5 is
> hosted on rubyforge, but does not contain any info about the licence.
> This version 0.5 was packaged by Paul van Tilburg where the MIT license
> was indicated. Paul, if you read this, could you indicate where you get
> the licence from?

This is very weird. You should probably contact the upstream developers
and ask them to add an explicity copyright message in the sources,
probably in the README.

> > 3. Your dep5 format url is not working. Use dep.debian.net url
> 
> Indeed. This url was generated automatically by gem2deb. It is not clear
> for me that we should use dep.debian.net right now. Althought dep-5 is
> frozen, its status is just candidate, and not accepted yet. The example
> given in DEP-5 refers to a version of the markdown file kept in the svn rep=
> ository.

Since 1) DEP's are not mandatory anyway and 2) DEP-5 format is not
likely to change radically anymore, IMO it's ok to point to
dep.debian.net.

> The problem with the url generated by gemdeb seems to come from the
> op=file operand, which probably worked with wsvn, but does not with
> viewvc. Changing it to view=co solves this issue, and allows to refer to
> a specific version of this standard.
> 
> I have change the url for ruby-markaby in the repository.
> 
> A lot of other packages are affected by this problem (list below).
> Should we consider a massive patching of the copyright files to have a
> working url?

Yes.

> In the mean time, the url should be corrected on line 432
> of /usr/lib/ruby/vendor_ruby/gem2deb/dh_make_ruby.rb

This was fixed some time ago in git, but didn't go into the archive
yet. Newly generated debian/copyright files will point to
http://dep.debian.net/deps/dep5

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Re: RFS: ruby-ascii85

[Antonio Terceiro]

Cédric Boutillier escreveu isso aí:
> Hi!
> 
> I am starting to push the dependencies for a new version of ruby-prawn.
> The first one is ruby-ascii85 (ITP #640110).
> 
> I have just pushed to the repository my proposition of packaging. The
> package obtained is lintian clean. I would be happy if someone could
> review, and possibly upload the package.
> 
> Thank you in advance for the feedback.

the URL in debian/watch is not valid, because the upstream project is
called Ascii85 (with an uppercase 'A'). It looks like this is also
caused by gem2deb, and since the package is OK otherwise I've fixed this
issue myself and uploaded.

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Re: RFS: ruby-ascii85

[Cédric Boutillier]

On Sun, Sep 04, 2011 at 09:16:13PM -0700, Antonio Terceiro wrote:

> the URL in debian/watch is not valid, because the upstream project is
> called Ascii85 (with an uppercase 'A'). It looks like this is also
> caused by gem2deb, and since the package is OK otherwise I've fixed this
> issue myself and uploaded.

Thank you very much, Antonio!

Best wishes,

  Cédric


signature.asc
Description: Digital signature

Re: RFS: ruby-markaby

[Cédric Boutillier]

On Sun, Sep 04, 2011 at 07:21:11PM -0700, Antonio Terceiro wrote:
> Cédric Boutillier escreveu isso aí:
> > > 2. http://raa.ruby-lang.org/project/markaby mentions its license is
> > > same as that of ruby's.
> > 
> > This is the website hosting version 0.4 of markaby. Version 0.5 is
> > hosted on rubyforge, but does not contain any info about the licence.
> > This version 0.5 was packaged by Paul van Tilburg where the MIT license
> > was indicated. Paul, if you read this, could you indicate where you get
> > the licence from?

> This is very weird. You should probably contact the upstream developers
> and ask them to add an explicity copyright message in the sources,
> probably in the README.

Did it already, but no answer so far.
https://github.com/markaby/markaby/issues/30

> > > 3. Your dep5 format url is not working. Use dep.debian.net url
> > 
> > Indeed. This url was generated automatically by gem2deb. It is not clear
> > for me that we should use dep.debian.net right now. Althought dep-5 is
> > frozen, its status is just candidate, and not accepted yet. The example
> > given in DEP-5 refers to a version of the markdown file kept in the svn rep=
> > ository.

> Since 1) DEP's are not mandatory anyway and 2) DEP-5 format is not
> likely to change radically anymore, IMO it's ok to point to
> dep.debian.net.

Ok.

> > The problem with the url generated by gemdeb seems to come from the
> > op=file operand, which probably worked with wsvn, but does not with
> > viewvc. Changing it to view=co solves this issue, and allows to refer to
> > a specific version of this standard.
> > 
> > I have change the url for ruby-markaby in the repository.
> > 
> > A lot of other packages are affected by this problem (list below).
> > Should we consider a massive patching of the copyright files to have a
> > working url?

> Yes.
Ok, I can try to do that.

Best wishes,

  Cédric


signature.asc
Description: Digital signature

Re: RFS: ruby-ttfunk

[Cédric Boutillier]

On Thu, Sep 08, 2011 at 11:04:02AM +0200, Cédric Boutillier wrote:
> Hi!

> I believe that ruby-ttfunk is ready to upload. I have checked all
> the points indicated on the wiki page, and the package is lintian-clean.

> Could you please review and enventually upload the package if ready?

> Thank you in advance for your feedback.

Hmmm... even if it is not in the binary package, there is still a copy
of the Comic Sans MS truetype font in the source package. I guess I need
to repack the sources to remove this non-free bit.

I found some doc [1] to use get-orig-source: target in debian/rules and
uscan to achieve this.

I will send an new request when I get it right.


[1] https://wiki.ubuntu.com/PackagingGuide/Examples/ChangingTheOrigTarball


signature.asc
Description: Digital signature

Re: RFS: ruby-ttfunk

[Cédric Boutillier]

On Thu, Sep 08, 2011 at 01:54:14PM +0200, Cédric Boutillier wrote:

> I will send an new request when I get it right.

I guess that now the package is in a better shape. Thank you.

Cédric



signature.asc
Description: Digital signature

Re: RFS: ruby-ttfunk

[Antonio Terceiro]

Cédric Boutillier escreveu isso aí:
> On Thu, Sep 08, 2011 at 01:54:14PM +0200, Cédric Boutillier wrote:
> 
> > I will send an new request when I get it right.
> 
> I guess that now the package is in a better shape. Thank you.

I could not found in the sources where did you get the upstream
copyright info you put in debian/copyright. the copyright notice in
debian/copyright must be (mostly) copied verbatim from upstreams
sources.

Other than that, the package seems fine.

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Re: RFS: ruby-ttfunk

[Cédric Boutillier]

On Sun, Sep 11, 2011 at 02:00:58PM -0700, Antonio Terceiro wrote:

> I could not found in the sources where did you get the upstream
> copyright info you put in debian/copyright. the copyright notice in
> debian/copyright must be (mostly) copied verbatim from upstreams
> sources.

The information is present in the gem file. In the repository on github,
there is a file LICENCE, starting with the following lines:

  ttfunk is copyrighted free software produced by Gregory Brown along with 
  community contributions.  See git log for authorship information.
  
  Licensing terms follow (License of Ruby):
  
  You can redistribute Prawn and/or modify it under either the terms of
  the GPLv2
  or GPLv3 (see GPLv2 and GPLv3 files), or the conditions below:

I checked out the repo and written down the names of all the authors of
the commits. Is it the thing to do when such a wording is used about the
authorship? Should I ask upstream to ship this LICENSE file within the
ruby gem?

Thank you for your advice.

Cédric


signature.asc
Description: Digital signature

Re: RFS: ruby-ttfunk

[Antonio Terceiro]

Hello debian-legal,

[please keep debian-ruby in Cc: on responses]

Cédric Boutillier escreveu isso aí:
> 
> On Sun, Sep 11, 2011 at 02:00:58PM -0700, Antonio Terceiro wrote:
> 
> > I could not found in the sources where did you get the upstream
> > copyright info you put in debian/copyright. the copyright notice in
> > debian/copyright must be (mostly) copied verbatim from upstreams
> > sources.
> 
> The information is present in the gem file. In the repository on github,
> there is a file LICENCE, starting with the following lines:
> 
>   ttfunk is copyrighted free software produced by Gregory Brown along with 
>   community contributions.  See git log for authorship information.
>   
>   Licensing terms follow (License of Ruby):
>   
>   You can redistribute Prawn and/or modify it under either the terms of
>   the GPLv2
>   or GPLv3 (see GPLv2 and GPLv3 files), or the conditions below:
> 
> I checked out the repo and written down the names of all the authors of
> the commits. Is it the thing to do when such a wording is used about the
> authorship? Should I ask upstream to ship this LICENSE file within the
> ruby gem?

I think the best is to ask upstream to distribute that LICENCE file in
the .gem, and to reproduce that original copyright notice verbatim (i.e.
not list data from the git repository).

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Re: RFS: ruby-contest

[Paul van Tilburg]

On Wed, Oct 05, 2011 at 10:23:30PM +0200, Cédric Boutillier wrote:
> Could someone have a look at the package and possibly upload it?

Will check and upload!

Paul

-- 
PhD Student @ Eindhoven | email: pau...@debian.org
University of Technology, The Netherlands   | JID: p...@luon.net
>>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181


signature.asc
Description: Digital signature

Re: RFS: ruby-commandline

[Lucas Nussbaum]

On 15/10/11 at 23:16 +0200, Cédric Boutillier wrote:
> Hi,
> 
> I prepared the transition of libcommandline-ruby to the new policy. I
> kept the previous package layout, with the documentation generated with
> rdoc shipped as a separate package.
> The package is lintian-clean (warnings about duplicate description
> overriden) and builds fine in a clean chroot. The library loads without error
> with ruby1.8 and ruby1.9 in a clean chroot.
> 
> Could someone review and possibly upload this package?

uploaded and tagged, thanks!

L.


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111016074506.ga11...@xanadu.blop.info

Re: RFS: ruby-liquid

[Lucas Nussbaum]

On 22/10/11 at 00:37 +0200, Cédric Boutillier wrote:
> Hi!
> 
> I have finished preparing the packaging of ruby-liquid, a necessary
> package to enable tests for ruby-tilt, as listed in the NeedPackaging
> file of the repository.
> 
> The package is lintian clean, builds fine in a clean chroot. I have
> loaded the library and tested several examples with 1.8 and 1.9.1 in a
> chroot with success. I checked I pushed all the branches and all the
> tags to the repository.
> 
> Could someone please have a look at the package, and possibly upload it?
> 
> Thank you very much in advance.

uploaded and tagged, thanks

L.


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111025062217.gb20...@xanadu.blop.info

Re: RFS: ruby-text

[Lucas Nussbaum]

On 14/10/11 at 16:16 +0200, Olivier Sallou wrote:
> Hi,
> new tentative to find a fellow DD to sponsor the package ruby-text
> (0.2.0-1). This is a dependency package for the ruby-cassiopee package
> (waiting in new packages for the moment).
> 
> Someone already had a first review on it, now I would need someone to
> check/upload it.

Hi,

The use of exec() in debian/ruby-tests.rb is wrong. it will only run the
first test script.
Use:
system("...") or raise
?

L.


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111025062512.gc20...@xanadu.blop.info

Re: RFS: ruby-text

[Olivier Sallou]

Le 10/25/11 8:25 AM, Lucas Nussbaum a écrit :
> On 14/10/11 at 16:16 +0200, Olivier Sallou wrote:
>> Hi,
>> new tentative to find a fellow DD to sponsor the package ruby-text
>> (0.2.0-1). This is a dependency package for the ruby-cassiopee package
>> (waiting in new packages for the moment).
>>
>> Someone already had a first review on it, now I would need someone to
>> check/upload it.
> Hi,
>
> The use of exec() in debian/ruby-tests.rb is wrong. it will only run the
> first test script.
> Use:
> system("...") or raise
> ?

I fixed this, thanks for info

> L.

-- 
Olivier Sallou
IRISA / University of Rennes 1
Campus de Beaulieu, 35000 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (pgp.mit.edu)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438



-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ea6631f.3090...@irisa.fr

Re: RFS: ruby-text

[Lucas Nussbaum]

On 25/10/11 at 09:19 +0200, Olivier Sallou wrote:
> 
> 
> Le 10/25/11 8:25 AM, Lucas Nussbaum a écrit :
> > On 14/10/11 at 16:16 +0200, Olivier Sallou wrote:
> >> Hi,
> >> new tentative to find a fellow DD to sponsor the package ruby-text
> >> (0.2.0-1). This is a dependency package for the ruby-cassiopee package
> >> (waiting in new packages for the moment).
> >>
> >> Someone already had a first review on it, now I would need someone to
> >> check/upload it.
> > Hi,
> >
> > The use of exec() in debian/ruby-tests.rb is wrong. it will only run the
> > first test script.
> > Use:
> > system("...") or raise
> > ?
> 
> I fixed this, thanks for info

Uploaded, updated the tag.

Thanks!

Lucas


-- 
To UNSUBSCRIBE, email to debian-ruby-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111027183010.gb32...@xanadu.blop.info