Re: [DRE-maint] [IMPORTANT] future of pkg-ruby-extras
Hi Lucas, Excerpts from Lucas Nussbaum's message of 2011-01-08 00:07:05 +0100: So, if you want to stay a member of the team (which is fine, I encourage you to continue to contribute to the team, and I'm also planning to stay a member for now!), please reply to this mail within the following two weeks, stating your alioth login. If you don't reply, you will be removed from the team. My login is mstapelberg-guest and I’m still in. I don’t maintain any packages yet but I plan to do so after the freeze is over. Best regards, Michael ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
Re: [DRE-maint] [IMPORTANT] future of pkg-ruby-extras
Even if I haven't been very active lately, I still care at least about the packages around RSpec and I'm currently working on packaging RSpec2 (Which might take some time...) tiber-guest / Tobias Grimm et...@debian.org libdifflcs-ruby libfakefs-ruby libheckle-ruby (U) libinline-ruby (U) libparsetree-ruby librspec-ruby libruby2ruby-ruby (U) libsexp-processor-ruby (U) ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#609275: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libxtemplate-ruby |0.8.0-5 | all libxtemplate-ruby1.8 |0.8.0-5 | source, alpha, amd64, armel, hppa, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc --- Reason --- ROM; Very low popcon usage, no real maintainer -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 609...@bugs.debian.org. The full log for this bug can be viewed at http://bugs.debian.org/609275 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain) ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#596351: Removing ohai and chef?
On Sat, 25 Dec 2010 21:53:40 +0100 Julien Cristau wrote: On Sun, Dec 19, 2010 at 17:16:46 +, Chris Butler wrote: If it's any use, I ran a quick git bisect on the upstream source, and discovered the commit which seems to have fixed the problem: https://github.com/flori/json/commit/dd06e48aa414674f52e81f9cdc7836b6456c04f8 However, this doesn't apply cleanly to v1.1.9, as it seems the code is now using a different string buffer implementation for its result. I've not looked much further to see how easy it would be to backport the change (it may not be too difficult if the two string buffer implementations have similar APIs). Is there any chance you could do that? :) Bearing in mind Chris' previous comment: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596351#40 If the above is not possible, I return to my previous suggestion of removing ohai chef from squeeze. Once wheezy is up and running, there should be no problem getting the new libjson-ruby package in. There's always the option of providing packages via backports.debian.org once squeeze is released. Personally, I'd say it's time for a pair of RM bugs to be filed at release.debian.org to remove ohai and chef from Squeeze. This bug doesn't warrant blocking Squeeze. I'll file those two tomorrow unless someone comes up with a patch for ohai (or the release team decide to add the hints anyway). -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpjaIkJqxS5M.pgp Description: PGP signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-ruby-extras-maintainers
