Hi!
Fanstatic news. Thanks!
Le Tue, Oct 05, 2021 at 09:36:18AM -0300, Lucas Kanashiro a écrit :
>
> I did rebuild the packages using ruby-all-dev from experimental and here you
> can find the results:
>
> https://people.debian.org/~kanashiro/ruby3.0/round2/builds/
>
> At the moment, almost 17%
Hi,
In order to help with the transition to ruby3, I packaged the standalone
webrick gem, which is not distributed as a part of the Ruby standard
library. I am about to upload it
https://salsa.debian.org/ruby-team/ruby-webrick
I was wondering if ruby2.7 should not be made to Provides: ruby-webric
Le Sun, Oct 10, 2021 at 03:52:33PM +0200, Cédric Boutillier a écrit :
> I was wondering if ruby2.7 should not be made to Provides: ruby-webrick
> (= 1.6.1), before we make the packages needing that Ruby
> library to actually (build)depend on a ruby-webrick package.
> What do you think?
The list of packages containing files with either
require "webrick"
or
require 'webrick'
is
avro-java
bazel-bootstrap
cgit
drkonqi
git
gitaly
gitlab
gitlab-shell
global
hiki
ifetch-tools
jekyll
jruby
nadoka
pcs
pdns
public-inbox
puppet
puppet-module-puppetlabs-vcsrepo
rabbit
ruby2.7
ruby3.0
rub
Hi,
I am packaging sorted_set, as it was extracted from the standard library
as an independent gem for ruby3.0. I stumbled on the following issue:
- sorted_set depends on set >= 1.0
- set is available as an independent gem but is also bundled with ruby
stdlib:
- as a bundled gem with ruby3.0
Le Wed, Oct 13, 2021 at 09:51:39PM -0300, Antonio Terceiro a écrit :
> On Wed, Oct 13, 2021 at 10:10:12PM +0200, Cédric Boutillier wrote:
> > Hi,
> >
> > I am packaging sorted_set, as it was extracted from the standard library
> > as an independent gem for ruby3.0.
Dear FTP masters,
In order to accelerate the transition from ruby2.7 to ruby3.0,
could you please prioritize the examination of the following three
packages:
- ruby-webrick 1.7.0-1
- ruby-sorted-set 1.0.3-1
- ruby-rbtree 0.4.4-1
the first two were bundled to the standard library with ruby2.7 but
Hi!
Le Wed, Oct 20, 2021 at 01:45:22PM +0900, Youhei SASAKI a écrit :
> Dear folks,
>
> I'm currently working on a fix some FTBFS related to Ruby 3.0.
>
> In the case of ruby-netcdf, ruby-lapack and ruby-fftw3, these packages
> depend on ruby-narray, but ruby-narray in unstable is not built for
Hi,
> > In the context of an installation under vendor_ruby, I would go for
> > VENDORHDRDIR, although I would have hoped for a path which does not depend
> > on the ruby version.
>
> nokogiri being a C extension, I think using a ruby version-specific path
> is the right directory to use. You wo
Hi Leandro
Quoting Leandro Cunha (2021-11-06 06:53:13)
> ruby-ox 2.14.6-1
Sorry for the late answer. Could you please push your changes to the team
repository
https://salsa.debian.org/ruby-team/ruby-ox
or open merge requests on the three branches of the repo with your
updates?
That would ease the
Hi again,
Le Wed, Nov 24, 2021 at 11:56:48AM +0100, Cédric Boutillier a écrit :
> Hi Leandro
>
> Quoting Leandro Cunha (2021-11-06 06:53:13)
> > ruby-ox 2.14.6-1
>
> Sorry for the late answer. Could you please push your changes to the team
> repository
> https://sals
Hi Leandro,
Quoting Leandro Cunha (2021-11-25 06:58:48)
> My fork is already merged upstream with master and I thought I would either
> send
> it to a different branch with tag or create a new fork.
I think you can simply continue to use the 'upstream' branch to import
the 'new' version from the
Hi Praveen,
Thanks for all the converted packages!
> ruby-stringex introduces an autopkgtest regression when switching to
> gem-install layout. I could not figure out why from the error messages.
> Can someone check the salsa repo?
I have checked ruby-stringex and could fix the autotests by ad
Hi,
you need to set the CI/CD config file to "debian/salsa-ci.yml" for your
project, under Settings / CI/CD/ General pipelines.
It should be set correctly by our
"setup-project"/"setup-project-mentors" script in the meta repository,
as the ci_config_path is set by the create_project function (see
Hi,
> [..]
> > I looked for example at:
> > https://salsa.debian.org/ruby-team/mentors/ruby-fixture-builder
> > for which the setting was at the default value (.gitlab-ci.yml).
> > I manually put it to debian/salsa-ci.yml, and pushed a trivial commit to
> > it. The pipeline started as expected.
>
Hi!
> On Sat, Aug 20, 2022 at 10:16 PM Antonio Terceiro wrote:
> > Given that 1) we don't really support packages not working with all
> > available Ruby versions, 2) multiple ruby versions are only present
> > simultaneously during transitions, and 3) we only release with a single
> > version, I
Dear team members,
We discussed at the Ruby BoF last summer the possibility to have a Ruby
Sprint in Paris in 2023 around FOSDEM. This Fall has gone too
fast, and I had no time to prepare anything. FOSDEM is scheduled in two
months: February 4 and 5, 2023.
https://fosdem.org/2023/
I would like to
Hi!
Edit: I wrote this email on Tuesday December 6, but for some reason, it
didn't leave my machine... Sorry.
I am Cc: David who participated in the 2020 edition of the Debian Ruby
Sprint. Since we all benefited a lot from your presence David, it is
natural to ask if you would be interested in jo
Quoting Cédric Boutillier (2022-12-06 00:03:28)
> Hi!
>
> I am Cc: David who participated in the 2020 edition of the Debian Ruby
> Sprint. Since we all benefited a lot from your presence David, it is
> natural to ask if you would be interested in joining the 2023 edition.
>
Dear all,
The Ruby team is planning to hold an in-person meeting in Paris, from
Monday 6th of February to Friday 10th of February.
https://wiki.debian.org/Teams/Ruby/Meeting/Paris2023
The date and location have been choosen so that this meeting becomes a
satellite event of FOSDEM, held in Bruss
Hi!
There was something like this required sometime ago from the nokogiri
package to build ruby-nokogumbo. You can have a look at commit
a3939406c9a1b7ef2d07942ea01d693057f50f47
in nokogiri git repo, dating from 2021-10-22.
I hope it helps at least a bit.
I don't know if the solution is optimal.
Le 23 décembre 2022 13:36:25 GMT+01:00, Nilesh Patra a
écrit :
>
>Th commit you point to tries installing a header file into ruby vendor
>dir /usr/include/ruby-$(ruby_version)/vendor_ruby/
>However in current scenario, oj.h file is not even available in the
>archive, which is vendored by "oj"
Dear Jonathan,
Le Tue, Jan 03, 2023 at 12:01:32PM +0200, Jonathan Carter a écrit :
> I'm going to trust that the organisers of this sprint believes that everyone
> on the wiki page listed for travel are expected to be useful at the sprint
> in some manner.
>
> Expense approved for up to €15000 fo
Dear team members,
Happy new year 2023!
The budget for our sprint has been approved. It is time to book your
plane tickets if you haven't done yet.
About accomodation:
We used last time the apparthotel Citadines Austerlitz
https://www.discoverasr.com/en/citadines/france/citadines-austerlitz-paris
Hi Daniel,
Thanks for your comments. Indeed, I have certainly underestimated housing
costs, and at the time when I asked for approval, the list in the wiki was
shorter than now.
So we need to stay alert.
Last time in 2020, I first asked for 9kEuros, then when the list grew, I asked
for 11-12kE
Hi team members,
When reading the email from the release team this morning, I realized
that the deadline to (re)introduce new packages in testing is just a
couple of days after the end of our workshop. Since jekyll and all its
plugins are now removed from testing, I am a bit worried that if we wai
Hi!
Quoting Daniel Leidert (2023-02-01 14:52:38)
> Hi everybody,
>
> be aware that there are currently walkouts/strikes in France that affect the
> public transportation, but also flights. As far as I have been informed,
> strikes will be unannounced and can potentially last for multiple days now
Hi Vinay,
Quoting Vinay (2023-02-05 09:52:00)
> Hello Team,
>
> the package ruby-fog-local [1] can be re-uploaded to unstable (all the
> breaking
> changes are fixed ) as gitlab 15.6 is uploaded to experimental
I uploaded the package, thanks! I made a small modification: set the
Rules-Requires-
Dear Vivek,
Quoting Vivek K J (2023-02-05 08:39:02)
> Hi,
>
> The package ruby-asciidoctor-kroki can be reupload to unstable as
> gitlab 15.6 is uploaded to experimental. Requesting for Sponsorship /
> Upload access.
>
> Also requesting to enable CI/CD on the repo.
>
Thanks for your wor
Hi!
I was trying to update ruby-adsf in experimental, as it uses rack3.0. It
requires rackup >= 2.1, uploaded in unstable by Lucas K a few weeks ago,
but the package did not build because of the missing build-dependency
rack3.0 in unstable (#1027339).
So I was wondering if reuploading rackup to e
Dear all,
I wanted to have your opinion on the status and the future of the
ruby-celluloid(-*) packages. My understanding is that the project is
unmaintained for several years (since 2016 it seems), and most project
using that moved away to something else (I saw a mention of
async-websocket).
The
Hi!
I won't be able to attend Debconf/debcamp this year either. I should be
able to help remotely during the week of DebCamp.
Side question: I seem to remember a proposition at DebConf23 to have a sprint in
Japan as a satellite event of a miniDebconf. Do we have the contact of
that person in case
Hi Lucas,
Thanks for your efforts on that!
I was wondering if you had a personal Debian repository with the
arch:any packages which successfully built with 3.3 we could add to your
sbuild receipe, or at least if you have some (semi)automatic way to
build them, that I can reproduce on my machine.
Quoting Antonio Terceiro (2024-07-19 15:52:01)
> Yes! The build page at
> https://people.debian.org/~kanashiro/debian/ruby3.3/builds/ does contain
> a repository with the built package, and it's mentioned at the very
> beginning of the page. :)
Dear Antonio,
Thank you! I really needed someone to
The Debconf24 pad web frontend does not seem to be available anymore.
I created an issue on salsa, on the model of what we had for the ruby3.0
transition.
https://salsa.debian.org/ruby-team/ruby/-/issues/3
Let us use this to track the progress of this transition.
Best wishes,
Cédric
Dear Piper,
On Tue Aug 20, 2024 at 9:11 PM CEST, Piper McCorkle wrote:
> Sorry to bother y'all again. My previous upload of ruby-build 20240727-1
> is failing autopkgtest in all arches other than amd64 and arm64, due to
> one of the tests relying on functionality that is only available in
> those
Hi,
On Sun Aug 25, 2024 at 10:28 PM CEST, Ananthu C V wrote:
> [1] - https://salsa.debian.org/ruby-team/ruby-blade
> [2] - https://salsa.debian.org/ruby-team//ruby-bullet
Thanks for your work! I uploaded ruby-blade and ruby-bullet.
Cheers,
Cédric
signature.asc
Description: PGP signature
Hi team,
with the help of Lucas, I ran a few more times the mass rebuild scripts
for some packages of the list
https://people.debian.org/~boutil/ruby3.3/mass-rebuild/builds/
We are down to 243 failures.
I am continuing to investigate failure patterns. One of them is the easy
MiniTest which shoul
On Sun Aug 25, 2024 at 10:28 PM CEST, Ananthu C V wrote:
> - ruby-bootsnap [3]
> - ruby-beaneater [4]
I've just uploaded the last two. Could you make sure that you forward
your minitest patch for ruby-beaneater to upstream? As it is not
Debian-specific, it could be useful for others.
Thanks for yo
Hi,
I have been looking at the gem dependency failure with nanoc
https://people.debian.org/~boutil/ruby3.3/mass-rebuild/builds/10/nanoc/nanoc_4.13.0-1+rebuild1724942411_amd64-2024-08-29T14:40:12Z.build
nanoc-core.gemspec asks base64 ~> 0.2
ruby3.1 ships base64 v 0.1.1
ruby3.3 ships base64 v 0.2.
Dear Pipier,
On Tue Sep 3, 2024 at 10:08 AM CEST, Piper McCorkle wrote:
> ruby-build recently updated to 20240903. I have pushed the update to the
> [package Salsa repo]. I would appreciate if someone could sponsor the
> upload to the archive.
>
I uploaded your package. Thanks for your work on ru
Hi,
I investigated this a little bit. The problem occurs during this call:
lambda { BCrypt::Password.create(nil) }.should_not
raise_error(BCrypt::Errors::InvalidSecret)
in the password_spec.rb test file.
It seems that the value (10) of the BCrypt::Engine::DEFAULT_COST constant
is to high (at
Dear members,
I would like very much to become a member of the Ruby-extras team, to
help maintaining Ruby libraries, especially during the transition to the
new packaging policy. I have a reasonable knowledge of Ruby
and know git basics. I was thinking that getting involved in this team
would be t
Dear Lucas,
On Fri, Jul 29, 2011 at 11:02:34AM +0200, Lucas Nussbaum wrote:
> Yay! \o/
> Any package listed on the transition page is OK, as well as those already
> migrated that need some work according to the PET report.
> It's easier if you join the IRC channel to coordinate.
Thank you for
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 m
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
>
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 corr
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?
Best wishes,
Cédric
signature.asc
Description:
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
Dear Dmitry,
As you may already know, a new policy is being established for the
packaging of Ruby libraries in Debian for Wheezy. See
http://wiki.debian.org/Teams/Ruby/Packaging
for details. In particular this implies a renaming of the packages (from
libfoo-ruby to ruby-foo), and gem2deb is the r
Hi!
I am trying to update markaby, and convert it to the new policy. I need
some advice for a dilemma I cannot solve.
The library markaby.rb tries to load dynamically from a file VERSION its
version number. The relative path between the library and this file
("../") is hardcoded in the file. With
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 copyright information in the old libmarkaby-ruby, but I found
no license/copyright info in the gem or i
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 packa
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
Hi,
I come again to you with probably a trivial question.
Some ruby libraries have a test suite that one can find in their
repository, but the tests are not shipped in the gem. Two such examples
are:
ruby-liquid: needed to run the tests of tilt;
ruby-pdf-reader: dependency for a new version of ru
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 a
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
On Mon, Sep 05, 2011 at 11:52:11AM +0200, Cédric Boutillier wrote:
> > > > 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 de
Hi!
I believe that ruby-pdf-reader 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.
Best wishes,
Cédric
signature.asc
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.
Best wishes,
Cédric
signature.asc
Desc
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 rea
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
Hi!
I am in the process of converting libprawn-ruby to gem2deb packaging
(and splitting it into smaller packages that have been released in the
mean time as independent projects: pdf-inspector (depending on
pdf-reader) and ttfunk.
The test suite for prawn uses test/spec, which is not yet packaged
Hi Antonio,
Thank you very much for your comments. I am learning a lot.
On Sun, Sep 11, 2011 at 10:38:55AM -0700, Antonio Terceiro wrote:
> You did not import a new pristine-tar entry for the 0.10.0+real version.
I believe I did. I have just checked out again ruby-pdf-reader
repository. There
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
Hi!
I think I discovered a tiny bug in gem2deb. If ruby1.8 test fail, then
when we want to proceed with the package construction, we go directly to
the packaging without trying to run the tests for 1.9.1
This is due to the loop in the run_tests function, in dh_ruby.rb. The
fact that non working v
Hi!
On Sun, Sep 11, 2011 at 11:44:10PM +0200, Cédric Boutillier wrote:
> On Sun, Sep 11, 2011 at 10:38:55AM -0700, Antonio Terceiro wrote:
> > If you do not ship the files under bin/, there is no reason to patch them
> > at all.
> You are right, I committed the patch before de
Package: wnpp
Severity: wishlist
Owner: "Cédric Boutillier"
Hi,
I would like to package ruby-test-unit, an improved version of Ruby 1.8
Test::Unit testing framework.
* Package name: ruby-test-unit
Version : 2.4.0
Upstream Author : Kouhei Sutou and ot
Hi!
I prepared the packaging of ruby-test-unit. I have checked all the
pointed listed on the wiki page, and the package is lintian-clean
(except a warning for missing upstream changelog).
Could you please review and possibly upload this package?
Thank you in advance!
Best,
Cédric
si
Hi Praveen,
On Tue, Sep 20, 2011 at 12:15:36PM +0530, Praveen A wrote:
> Upstream git has these files, but gem is missing the whole fixtures directory!
> I opened an issue with upstream https://github.com/djanowski/cutest/issues/3
> Can I add the whole fixtures directory as patch and proceed ti
Package: wnpp
Severity: wishlist
Owner: "Cédric Boutillier"
Hi,
I would like to package under the Ruby Extras Team the library
ruby-test-spec, which provides testing framework for behavior driven
developpement
on top of Test::Unit (bundled with Ruby1.8, or soon available in
ruby
Hi!
I prepared the packaging of ruby-test-spec. I have checked all the
pointed listed on the wiki page, and the package is lintian-clean
(except a warning for missing upstream changelog, which is included in
the README).
This package depends and build-depends on ruby-test-unit, which is also
read
Dear Praveen,
On Thu, Sep 22, 2011 at 10:12:46AM +0530, Praveen A wrote:
> Builds in clean chroot, it is lintian clean.
> I think you can remove the commented dependency section (only
> development dependencies are listed) in control file.
> Maybe you can add a comment to rules why you are over
On Thu, Sep 22, 2011 at 05:47:48PM +0530, Praveen A wrote:
> 2011/9/22 Cédric Boutillier :
> > Thank you very much for reviewing the package. I implemented your comments.
> Is /usr/bin/testrb exactly same as the one that comes with ruby?
Well spotted, thank you, that is something
On Sat, Sep 24, 2011 at 11:56:40AM -0700, Antonio Terceiro wrote:
> Cédric Boutillier escreveu isso aí:
> > Or I could mention in a README.Debian that one may expect some
> > changes in the behavior of testrb1.8 (more options, could be run with
> > ruby1.9.1) and testrb1.9
Dear Hrishi,
First I would like to apologize, as it turns out that I did not notice
your ITP for ruby-test-unit, and opened one myself (#642095) that has
been closed in the meantime.
May I ask what the status of your package is at the moment? I started to
work on this package under the umbrella o
owner 626792 Cédric Boutillier
thanks
Dear Hrishi,
Thank you very much for your message. I will thus with your agreement
take over this ITP, and I therefore become the owner of this bug
report.
With my best wishes,
Cédric
--
To UNSUBSCRIBE, email to debian-ruby-requ
Dear list,
Another ITP for ruby-test-unit had been submitted (#626792) before mine
(#642095). The
(ex-)owner accepted that I take over, so I changed the number of the bug
to close in changelog.
Moreover, upstream solved the encoding issue present in one of the tests
with LANG=C. I am now using i
Hi Praveen,
On Tue, Sep 27, 2011 at 01:52:36PM +0530, Praveen A wrote:
> 2011/9/22 Praveen A :
> It is quite handy to use {c,h} and the options I consider are,
> 1. I think it is lintian bug, I should report it, override it in the meantime
> 2. Change it to *.c *.h (space separated) and make lint
Hi Olivier,
On Sat, Oct 01, 2011 at 10:30:43AM +0200, Olivier Sallou wrote:
> I want to add a new package from an existing gem (I am upstream author).
> I'd like to know how to avoid the rubygems dependency in the ruby gem
> library. The package indeed depend on an other gem. If I remove the
>
On Mon, Oct 03, 2011 at 09:34:00AM +0200, Olivier Sallou wrote:
> This is a new package I am creating . My gem "Cassiopee" depends on gem
> "Text" (both are not yet packaged).
> The "problem" is with the gem2deb command on gem Cassiopee.
> I have for the moment, in my gem lib, a require "rubygems"
Dear Martin,
On Mon, Oct 03, 2011 at 07:29:50PM +0200, Martin Ueding wrote:
> I would like to use the ruby gem "ronn" as a build-dep in another
> package, therefore I try to package this as Debian package. In order to
> deal with the dependencies of ronn, I also created two more packages.
Thnak
Dear Olivier,
On Tue, Oct 04, 2011 at 11:25:47AM +0200, Olivier Sallou wrote:
> Hi,
> I have packaged ruby-text on alioth and it is ready for review/upload.
> It is lintian clean, tested, and built with pbuilder.
> Could someone review and upload it?
Thanks for packaging ruby-text. I cannot upl
Package: wnpp
Severity: wishlist
Owner: "Cédric Boutillier"
Hi,
I would like to package ruby-context under the umbrella of the Ruby
Extras Team.
* Package name: ruby-contest
Version : x.y.z
Upstream Author : Damian Janowski , Michel Martens
* URL
Dear Olivier,
On Tue, Oct 04, 2011 at 02:20:01PM +0200, Olivier Sallou wrote:
> Le 10/4/11 1:54 PM, Cédric Boutillier a écrit :
> > - debian/copyright: you could use a single standalone paragraph License:
> > GPL-2+, and refer to it in the two Files: paragraph.
> &
Hi!
On Sat, Sep 24, 2011 at 01:57:47PM -0700, Antonio Terceiro wrote:
> Hi Cédric,
> Cédric Boutillier escreveu isso aí:
> > This package depends and build-depends on ruby-test-unit, which is also
> > ready for review.
> Please ping again when ruby-test-unit is sorted out
On Tue, Oct 04, 2011 at 05:01:55PM +0200, Martin Ueding wrote:
> > You can put your name in the Maintainer field, but if you decide to
> > maintain these packages under the umbrella of the Ruby Extras Team,
> > which I am sure, is a good idea, then leave the name of the team as
> > the maintainer,
Hi everybody,
I prepared the packaging of ruby-context, which is a build dependency of
ruby-mustache, ruby-ronn and ruby-tilt (once its test suite is enabled).
The library is very simple (one file of ~100 lines), so the packaging is
almost trivial. The package builds fine in a clean chroot, and i
Hi Martin,
On Wed, Oct 05, 2011 at 11:12:28PM +0200, Martin Ueding wrote:
> I uploaded the ruby-ronn package. Did I do it right? If so, I'll upload
> the other two.
Looks fine. Go ahead with the other two packages.
Best wishes,
Cédric
signature.asc
Description: Digital signature
On Wed, Oct 05, 2011 at 11:30:17PM +0200, Cédric Boutillier wrote:
> Hi Martin,
> On Wed, Oct 05, 2011 at 11:12:28PM +0200, Martin Ueding wrote:
> > I uploaded the ruby-ronn package. Did I do it right? If so, I'll upload
> > the other two.
> Looks fine. Go ahead w
Hi,
On Sun, Oct 09, 2011 at 10:17:57AM +0200, Lucas Nussbaum wrote:
> On 09/10/11 at 10:01 +0200, Olivier Sallou wrote:
> > Hi,
> > My 2 new packages ruby-text and ruby-cassiopee do not appear in PET
> > http://pkg-ruby-extras.alioth.debian.org/cgi-bin/pet.cgi
> >
> >
> > ruby-text is ready f
Hi again,
On Sun, Oct 09, 2011 at 11:13:27AM +0200, Cédric Boutillier wrote:
> On Sun, Oct 09, 2011 at 10:17:57AM +0200, Lucas Nussbaum wrote:
> > On 09/10/11 at 10:01 +0200, Olivier Sallou wrote:
> > > Hi,
> > > My 2 new packages ruby-text and ruby-cassiopee do no
Hi!
I think the packages are almost ready. Find my comments below.
ruby-mustache:
lintian-clean (except missing upstream changelog) and builds in a clean
chroot.
I believe it is good to go. You could gain readability in
debian/copyright by using a standalone paragraph for the Expat Licens
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
Hi again,
On Sun, Oct 16, 2011 at 09:45:06AM +0200, Lucas Nussbaum wrote:
> 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 d
Hi,
I just wanted to mention that, in order to increase quality of our
repository, I am willing to fix the watch files of some repositories, in
order to eliminate some entries in the PET page.
Therefore I may commit to your repositories. I hope it will not annoy anybody.
Best regards,
C
Hi!
Upstream just released a version with only change the fix of the faulty
license header that made 0.10.0+real to be rejected from the archive.
The only changes from the package Antonio reviewed is:
- header or lib/pdf/reader/glyphlist.txt removed by upstream
- copyright entry for this file remo
On Thu, Oct 20, 2011 at 12:46:45PM -0500, Gunnar Wolf wrote:
> You have not updated the pristine-tar branch to include 0.10.1 :(
Please accept my apologies. I forgot to push it from a local repository.
It should be fixed now.
Cédric
signature.asc
Description: Digital signature
On Thu, Oct 20, 2011 at 09:39:22PM +0200, Cédric Boutillier wrote:
> Please accept my apologies. I forgot to push it from a local repository.
> It should be fixed now.
Gunnar, thank you for uploading ruby-pdf-reader.
Cédric
signature.asc
Description: Digital signature
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 - 100 of 846 matches
Mail list logo
