On Tuesday, 10 July 2018 11:04:55 CEST Youhei SASAKI wrote:
> Ok. I'm jekyll maintainer. I'll become maintainer of these packages.
I'm not part of new debian-ruby team. Can you remove me from the Uploaders
list ?
Thanks
signature.asc
Description: This is a digitally signed message part.
Hello
I've not been longer active in Ruby team for quite a while.
I've requested access to ruby project on Salsa to remove myself from Uploaders
of the following packages:
- ruby-jekyll-test-plugin
- ruby-kpeg
- ruby-pygments.rb
The first 2 packages were a dependency of jekyll a while ago. Thei
Hello
jekyll package [1] is FTBS and marked for auto-removal on July 7th.
I'm sorry to inform you that I can no longer maintain this package. I've
removed myself from the list of uploaders.
All the best
[1] https://tracker.debian.org/pkg/jekyll
--
https://github.com/dod38fr/ -o- http://se
Hello
Could someone have a look at the following RC bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768615
I don't know ruby enough to be able to fix this one.
All the best
--
https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/ -o- irc:
On Saturday 31 May 2014 16:08:31 Harlan Lieberman-Berg wrote:
> If I had to pick one, I think I'd probably go with #3, in the desperate
> hopes that the two "plugins" can simply be fixed at whatever version
> they are at the time of the main jekyll update and that we won't run
> into problems needi
Package: wnpp
Owner: Dominique Dumont
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-ruby@lists.debian.org
* Package name: ruby-kpeg
Version : 1.0.0
Upstream Author : Evan Phoenix
* URL : https://github.com/evanphx/kpeg
* License : BSD
On Friday 04 April 2014 01:29:59 Per Andersson wrote:
> The pull request actually removes Debian specific invokation. Check the
> comment for the python_binary method.
got it.
> I am using it to patch the Debian package. If upstream decides to
> include it: great!
> If not, we carry the patch.
F
On Thursday 03 April 2014 16:58:22 Sytse Sijbrandij wrote:
> Just to make sure, everyone is aware that GitLab no longer includes
> Pygments? We switched to Highlight.js in 6.6
Sure. But jekyll still needs ruby-pygments.rb
All the best
--
https://github.com/dod38fr/ -o- http://search.cpan.org
On Thursday 03 April 2014 00:28:46 Per Andersson wrote:
> I have created a fix and forwarded it for upstream inclusion
>
> https://github.com/tmm1/pygments.rb/pull/119
>
> When this is accepted upstream I intend to go forth with repackaging
> the upstream tarball and removing the vendor direc
Hello
Package build of ruby-pygments.rb version
91f0ef32d7accf4de83e099d164781c48d523a8f
works, well sort of works.
The package build and test do not return errors. But 2 pythons processes go
on running 100% CPU for tens of seconds after the package build is finished.
The running processes
On Monday 03 March 2014 23:17:22 Per Andersson wrote:
> There is also the issue of the custom lexer for github markup from
> pygments in vendors, I can't see that this is resolved in current packaging.
>
> Since the idea is to use this for GitLab where ruby-github-markup will
> use this custom lex
On Tuesday 25 February 2014 11:55:25 Cédric Boutillier wrote:
> The last point to do was renaming /usr/bin/launchy to something else
> (launchy-rb?) because there was already a binary with that name in the
> archive. If I remember well, the rest was more than OK.
I'm beginning to wonder if packagi
On Friday 28 February 2014 14:59:55 Axel Wagner wrote:
> I think the open issues should be fixed now. Could you please have a
> look and upload if appropriate?
I had a quick look. There are still some issues:
control:
- you should put yourself in uploader
- update standards version to 3.9.5
cop
Package: wnpp
Owner: Dominique Dumont
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-ruby@lists.debian.org
* Package name: ruby-jekyll-test-plugin
Version : 0.1.0
Upstream Author : Parker Moore
* URL : https://github.com/parkr/jekyll-test-gem
Hello Gioele
What is the status on your packaging work of ruby-launchy ?
There a TODO in the git repo mentioning work once ruby-spoon is packaged. This
is now done.
Is there something to be done before review and upload ?
All the best
--
https://github.com/dod38fr/ -o- http://search.c
On Monday 24 February 2014 00:09:10 Per Andersson wrote:
> > I suggests that we remove the complete sample_documents/ directory. We
> > can't run build tests anymore, but adding the copyright for every
> > wikipedia article seems to be a little bit PITA.
>
> I lost momentum with the packaging when
16 matches
Mail list logo
