Hi Leandro,
On Wed, Jun 5, 2024 at 10:00 AM Leandro Cunha wrote:
> The package has a release critical bug with FTBFS requiring an urgent
> upload, it has no recent upload history (since 2021), it is not
> compatible with version 3.1/3.2 of Ruby (so much so that we have an rc
> bug because fails
Hi Cédric,
On Sun, Dec 4, 2022 at 3:52 PM Cédric Boutillier wrote:
> I would like to know if you are interested in joining a Ruby Sprint
> either the week before (January 30 - Feb 3) or after (Feb 6 - Feb 10).
> It would take place in the center of Paris, in the campus of Sorbonne
> Université
Hey,
On Thu, Sep 22, 2022 at 1:32 PM Ajayi Olatunji O
wrote:
> Thank you very much.
> But I seem not to find the right homepage after hours of searching,
> kindly point it to me if you don't mind.
The very link you mentioned redirects to another project which has the
very first set of words:
Hey,
On Wed, Sep 21, 2022 at 9:25 PM Ajayi Olatunji O
wrote:
> In order to update git lab to version 15.3.0, ruby-oauth2 must be
> updated from version 1.4.4 to version 2.0, and ruby-oauth requires a
> ruby gem version-gem, but because of the absence of version-gem in the
> Debian archive I had
Hellu,
On Tue, Sep 13, 2022 at 3:52 PM Utkarsh Gupta
wrote:
> FWIW, I'll take care of this RFS. I am waiting for rails to settle and
> then take a look at redmine.
I've done a bunch of more stuff in the package and fixed a bunch of
things. Uploaded v5.0.2-2, which will shortly be in testi
On Tue, Sep 13, 2022 at 11:10 PM Ravi wrote:
> > Ravi: can you also take a look at ruby-json-jwt?
> > ruby-rack-oauth2 is never gonna migrate unless
> > ruby-json-jwt migrates. So before we upload that, I want to make sure
> > that -json-jwt is through.
>
> There is a rc bug in ruby-json-jwt
Hi Sven,
On Tue, Sep 13, 2022 at 12:50 PM Sven Eckelmann wrote:
>
> On Monday, 12 September 2022 18:54:36 CEST Utkarsh Gupta wrote:
> > I have fixed the regression and uploaded the binaries here:
> > https://people.debian.org/~utkarsh/lts/rails/
>
> Thanks.
>
> &g
Hey,
FWIW, I'll take care of this RFS. I am waiting for rails to settle and
then take a look at redmine.
- u
Hiya,
On Mon, Sep 5, 2022 at 6:48 PM Ravi wrote:
> The following packages are ready to be uploaded (I also verified the
> points listed on
> http://wiki.debian.org/Teams/Ruby/Packaging#Requesting_Sponsorship).
>From IRC:
Ravi: can you also take a look at ruby-json-jwt?
ruby-rack-oauth2 is
Hi Jude and Sven,
On Tue, Sep 6, 2022 at 10:00 AM Jude Hungerford
wrote:
> Since then, loading any of our Redmine pages returns the following error:
> """
> Internal error
> An error occurred on the page you were trying to access.
> If you continue to experience problems please contact your
Hey,
On Sun, Aug 14, 2022 at 6:35 AM 'Tunji wrote:
> Hello, I made recommended changes to this package and it is now Lintian
> clean.
It still lacks the reason. :)
- u
Hey,
Thanks for all your work in the past weeks but all (or at least most)
of your emails are missing an important aspect of the RFS mail: the
main intent behind the work. For instance, you say package X is
updated and is lintian clean so here's an RFS, but WHY was this
package X updated in the
Hey,
On Wed, Aug 24, 2022 at 1:06 AM Gabriela Pivetta wrote:
> I've pushed the changes to its salsa repo:
> https://salsa.debian.org/ruby-team/rails
>
> Please consider to review and upload it.
Thank you, uploaded! \o/
- u
Hey,
On Wed, Aug 24, 2022 at 1:00 AM Gabriela Pivetta wrote:
> I've pushed the changes to its salsa repo:
> https://salsa.debian.org/ruby-team/ruby-selenium-webdriver
>
> Please consider to review and upload it.
Uploaded, thanks for your help! \o/
- u
Hey,
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 propose
Hi Jérôme,
On Mon, Jun 20, 2022 at 4:02 AM Jérôme Charaoui wrote:
> I would like to request to join the Debian Ruby team. I've submitted the
> request on GitLab.
Granted access, welcome, good sir. :)
> I have prepared an update to the Hiera package, and I also would like to
> help out getting
Hi Rajesh,
On Wed, Jun 8, 2022 at 9:21 PM Rajesh Simandalahi
wrote:
> I'm new to debian and the ruby team and already made some merge
> requests on the salsa repos for ruby-image-processing (CVE patch),
> asciidoctor, and asciiart (upstream imports and patch updates).
Thank you. I've merged in
Hi Praveen,
On Wed, Jun 1, 2022 at 1:08 PM Pirate Praveen wrote:
> We have a long standing rc bug (we have not updated to
> latest upstream for long)
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981224#10
>
> Also it caused autopkgtest regression for node-source-map update
>
Hello,
On Mon, Apr 11, 2022 at 8:52 PM Lucas Kanashiro wrote:
> Should we submit our regular BoF to DebConf this year? Are people
> planning to attend in-person? Are there people willing to attend remotely?
I think we should, indeed. I plan to attend and can be co-speaker if need be.
- u
Hi Daniel,
On Sat, Oct 2, 2021 at 8:43 PM Daniel Leidert wrote:
> I have just been pointed to the folowing documents:
>
http://janitor.debian.net/lintian-fixes/#how-do-i-prevent-the-janitor-from-making-certain-changes
>
Hiya,
On Tue, Sep 28, 2021 at 6:42 PM Pirate Praveen
wrote:
> As discussed on matrix [...]
Wherever the conversation is happening, if it's not GitLab
related, moving it to #debian-ruby would be good, I guess.
- u
Hello,
We have our BoF scheduled on Thursday, 26th August, from 14:00 - 14:45
UTC. I look forward to seeing everybody there. Please let me (or
Kanashiro) know who all would like to join the Jitsi session and we'd
be happy to share the Jitsi meeting link.
- u
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-ruby@lists.debian.org
Hello,
Rails was recently affected by 3 CVEs (CVE-2021-2290{2,4} and CVE-2021-22885).
I'm attaching a filtered diff for your review; the diff is
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-ruby@lists.debian.org
Hello,
We had to bump ruby-marcel to a newer version because the mimemagic
dependency - which relies on GPL-licensed mime type data from
Hi Praveen,
On Fri, Apr 16, 2021 at 3:24 PM Pirate Praveen wrote:
> I think the separate package was introduced by mistake without seeing
> the copy embedded in ruby. I think the right way is to fix this in ruby
> and remove this separate package. But I'd like someone from ruby team
> to confirm
Hi Sebastian,
On Sat, Apr 17, 2021 at 3:08 PM Sebastian Ramacher wrote:
> Thanks, please go ahead and remove the moreinfo tag once the version is
> available in unstable.
Uploaded to unstable, thanks. And removed the tag as well.
- u
On Sun, Mar 7, 2021 at 10:49 PM Utkarsh Gupta wrote:
> On Sun, Mar 7, 2021 at 10:15 PM Pirate Praveen
> wrote:
> > It looks like we will have to remove ruby-vcr and we will have to
> > disable tests for the following packages. I don't think there is
> > another way, t
Hi Praveen,
On Sun, Mar 7, 2021 at 10:15 PM Pirate Praveen wrote:
> It looks like we will have to remove ruby-vcr and we will have to
> disable tests for the following packages. I don't think there is
> another way, thoughts?
Maybe worth opening an issue upstream and discuss the cons of this
/changelog2019-01-04 16:57:45.0 +0530
+++ ruby-mechanize-2.7.6/debian/changelog2021-02-19 22:47:27.0 +0530
@@ -1,3 +1,10 @@
+ruby-mechanize (2.7.6-1+deb10u1) buster; urgency=medium
+
+ * Team upload for buster-pu.
+ * Add patch to prevent OS command injection. (Fixes: CVE-20
Hi Klaumi,
On Sat, Jan 30, 2021 at 11:31 PM Klaumi Klingsporn wrote:
> So I think the package is ready for upload, BUT
> the autopkgtest-self initiated by the build-script fails,
> because it's unable to fetch and install an old and
> outdated version of apt-utils: 2.1.11. The
> autopkgtest-self
Hi Praveen,
On Thu, Feb 4, 2021 at 1:57 AM Pirate Praveen wrote:
> I have ruby 2.7.1 currently in buster-fasttrack (fasttrack.debian.net)
> and I'm trying to update it to 2.7.2
>
> The build went fine, but bundler (2.1.4-2~bpo10+1) seems broken now. Do
> I need to update bundler as well for this
Hi Klaumi,
On Sun, Nov 29, 2020 at 1:24 AM Klaumi Klingsporn wrote:
> O.K., if you think it will serve us both and my
> obligations will be limited to the few packages I want to
> maintain, so make me a team member.
Great, I've given you access to the Ruby team's namespace. Welcome aboard! \o/
Hey,
On Sat, Nov 28, 2020 at 7:35 AM Daniel Leidert wrote:
>
> JFTR: The minima theme doesn't know sub-pages or collections by default.
> We'll have to create something ourselves.
Perhaps we can post this in "parts". Like you did the daily reports
for the sprints. So something similar.
Part 1,
Hi Klaumi,
On Fri, Nov 27, 2020 at 5:20 AM Klaumi Klingsporn wrote:
> should be no problem to split up the text after the
> introduction ("...let's get started!") into 6 separate
> pages at every second level header and to put a table of
> content link-set at the end of the introduction page.
>
Hi Klaumi,
On Sat, Nov 14, 2020 at 7:18 PM Klaumi Klingsporn wrote:
> And again thanks for your help. I made a cheat sheet for
> the workflow and all the tips after all. So hopefully next
> time it will become easier ;-)
That's great! Do you think you can put together this thing in a
markdown
Hi,
We have a Ruby team meeting today, 06th November at 1630 UTC.
This will be held on Jitsi again since it worked out pretty nice last time! :)
Please put the topics that you want to discuss here:
https://wiki.debian.org/Teams/Ruby/IRCMeetings
- u
EBrick. (Fixes: CVE-2020-25613)
+
+ -- Utkarsh Gupta Tue, 13 Oct 2020 18:32:32 +0530
+
ruby2.5 (2.5.5-3+deb10u2) buster-security; urgency=high
* Non-maintainer upload by the Security Team.
diff -Nru ruby2.5-2.5.5/debian/patches/CVE-2020-25613.patch
ruby2.5-2.5.5/debian/patches/CVE-2020-25613.patch
--- ru
Hi,
We have a Ruby team meeting tomorrow, 02nd October at 1630 UTC.
This will be held on Jitsi again since it worked out pretty nice last time! :)
Please put the topics that you want to discuss here:
https://wiki.debian.org/Teams/Ruby/IRCMeetings
- u
Hiya,
On Thu, Aug 27, 2020 at 6:31 PM Pirate Praveen wrote:
> We don't need to package every development dependency, only those required
> for functional tests need to be packaged. So mutant-rspec may be used in
> tests, codecov could be ignored. But currently tests are not enabled. You can
>
Hi,
We have a Ruby team meeting tomorrow, 04th September at 1630 UTC.
This will *not* be *yet another* meeting, we'll try to be more
interactive, perhaps a Jitsi call (with, of course, discussions on IRC
as well for those don't want to join, etc).
Please put the topics that you want to discuss
Hi all,
On Fri, Aug 14, 2020 at 4:58 PM Utkarsh Gupta wrote:
> We have our BoF on August 25th, 1600 to 1645 UTC.
Just a reminder that this is happening really soon, in about 70 minutes.
Best,
Utkarsh
Hi all,
On Sat, Aug 22, 2020 at 11:23 PM Lucas Kanashiro wrote:
> Thanks for setting up this gobby document Utkarsh! I added some extra
> notes there but the agenda looks good.
Great, thanks!
More importantly, in case someone's willing to join the BoF (& speak
or interact), please contact me
Hi Cocoa,
On Fri, Aug 21, 2020 at 1:27 PM Cocoa wrote:
> Could you please sponsor them?
Wow, very nicely done! Uploaded, thanks!
Best,
Utkarsh
Hi Cocoa,
On Fri, Aug 21, 2020 at 12:45 PM Cocoa wrote:
> The tests for ruby-proc-to-ast were disabled because ruby-proc-to-ast as the
> following examples were
> failing in the upstream version.
> rspec ./spec/proc_to_ast_spec.rb:78 # Proc#to_ast proc variation inner array
> rspec
Hi Cocoa,
On Sun, Aug 16, 2020 at 7:51 PM Cocoa wrote:
> The tests for ruby-unparser were disabled because ruby-devtools is currently
> not packaged
> for Debian, and to do so would require packaging around 7 more packages.
That's the right thing to do. Whilst we do want to run tests but
Hello all,
On Thu, Jun 18, 2020 at 9:52 PM Utkarsh Gupta wrote:
> Perfect, I have submitted the talk with the note mentioning the
> preferred time and day (Friday).
We have our BoF on August 25th, 1600 to 1645 UTC.
For the preparations, I have created a gobby document (named "r
Hello,
The next Ruby team meeting is on Friday, 07th August at 1630 UTC.
(which is tomorrow for most timezones)
Please put the topics that you want to discuss here:
https://wiki.debian.org/Teams/Ruby/IRCMeetings
I look forward to (virtually) seeing y'all! \o/
Best,
Utkarsh
Hi Sylvain,
On Mon, Aug 3, 2020 at 6:02 PM Sylvain Beucler wrote:
> This version is now impacted by new security issues, such as
> CVE-2020-8163, so I would recommend upgrading anyway. There is no place
> to upload a new version (in particular, not in ELTS where neither rails
> nor redmine are
Hi Sylvain,
On Mon, Aug 3, 2020 at 5:15 PM Sylvain Beucler wrote:
> Then I realized that this is about Debian Jessie which reached
> end-of-life a month ago, so the solution is to upgrade to Debian 9.
Whilst I am totally fine by this suggestion, but still asking..
Would it make sense to fix
On 8/3/20 1:56 PM, Utkarsh Gupta wrote:
> On Tue, 07 Jul 2020 09:36:20 +0200 "s.jaekel" wrote:
>> Package: ruby-rails
>> Version: 2:4.1.8-1+deb8u7
>> Severity: important
>> Tags: upstream
>>
>> I updated the ruby-rails packages last week.
>&g
Hi
On Tue, 07 Jul 2020 09:36:20 +0200 "s.jaekel" wrote:
> Package: ruby-rails
> Version: 2:4.1.8-1+deb8u7
> Severity: important
> Tags: upstream
>
> I updated the ruby-rails packages last week.
> Since then i can use the also installed redmine (3.0~20140825-8~deb8u4)
> no longer link tickets
Hi Iain,
On Tue, Jul 21, 2020 at 2:10 AM Iain Parris wrote:
> I've pushed my first commits, and we now for the first time have a
> passing pipeline. :-)
> A review would be very appreciated, because I'm brand new to Debian
> packaging.
Wow, this is good! Thanks :)
> I haven't yet updated
Hi Iain,
On Mon, Jul 20, 2020 at 5:02 AM Iain Parris wrote:
> Wow! That was extremely fast. Thank you so much Utkarsh - very much
> appreciated. :-)
Hehe, you're welcome! \o/
> Excerpts from Utkarsh Gupta's message of 2020-07-20 04:28:33 +0530:
> Thank you (x5)! That's wonderful to hear. There
Hi Iain,
On Mon, Jul 20, 2020 at 3:47 AM Iain Parris wrote:
> I am a long-time Debian user (running for 12+ years continuously in
> production), but this is my very first post on a Debian mailing list.
> I'd like to say a *huge* thank you for all that you do, from a very
> happy user. :-)
Very
Hi Stefano,
On Sat, Jul 18, 2020 at 3:38 AM wrote:
> $ reverse-depends -b src:ruby-iso8601
> No reverse dependencies found
>
> RM?
I kinda need it so added (and uploaded) myself as an uploader!
Thanks for your work so far! \o/
Best,
Utkarsh
Hi Marc, Praveen,
On Wed, Jul 15, 2020 at 10:38 AM Marc Dequènes (duck) wrote:
> I'm so glad to hear this. I was trying to reach you through your anger
> but felt I just got things worse and it made me feel really bad.
All good now \o/
> Then it's fine and as you said there's nothing to act
Hi Marc,
This thread has taken a turn it shouldn't have.
And I am not going to fight fire by fire. I'll try to be more
empathetic, as we all should.
On Mon, Jul 13, 2020 at 1:14 PM Marc Dequènes (duck) wrote:
> You are totally twisting my words. I gave you my understanding about how
> things
Hi,
On 7/7/20 7:36 PM, Marc Dequènes (duck) wrote:
> Well I have to admit I do not agree with Praveen's conception. The
> general acceptance in Debian for as long I've been in is that once
> you're in the maint/uploaders fields you're responsible of the package
> wherever it is in Debian.
Well,
Hello,
The next Ruby team meeting is on Friday, 03rd July at 1630 UTC.
(which is 2 days from now)
Please put the topics that you want to discuss here:
https://wiki.debian.org/Teams/Ruby/IRCMeetings
I look forward to (virtually) seeing y'all \o/
Best,
Utkarsh
Hi Abraham,
On Tue, Jun 30, 2020 at 2:21 AM Abraham Raji wrote:
> Request for review and sponsorship.
Thanks, uploaded!
Best,
Utkarsh
Hi,
On Wed, Jun 17, 2020 at 11:45 PM Lucas Kanashiro wrote:
> >> Moreover, I think with an online BoF we can have more people
> >> participating than usual and collect better feedback. This is also a
> >> good opportunity to see each others' face again (not just IRC :).
> >> However, we need to
Hi all,
Finally, since it has been decided that DC20 will be held online, I am
going to submit this.
> Moreover, I think with an online BoF we can have more people
> participating than usual and collect better feedback. This is also a
> good opportunity to see each others' face again (not just
Hi everyone,
Thank you to everyone who joined!
And to those who couldn't, we look forward to seeing you in the next one! :)
We had a pretty nice (& a quick) meeting.
Here are the logs:
Minutes:
http://meetbot.debian.net/debian-ruby/2020/debian-ruby.2020-06-05-16.41.html
Minutes (text):
Hello,
This is a call for help!
Weirdly enough, test failures in rails don't cause FTBFS as it should.
This is reported as #919478.
One could simply reproduce this by building @master from the rails
repository in the ruby-team's namespace.
It'd be very nice if someone could take a look at it
00 +0530
+++ ruby2.3-2.3.3/debian/changelog2020-06-05 14:25:50.0 +0530
@@ -1,3 +1,11 @@
+ruby2.3 (2.3.3-1+deb9u8) stretch; urgency=high
+
+ * Non-maintainer upload.
+ * Add patch to fix unsafe object creation vulnerability.
+(Fixes: CVE-2020-10663)
+
+ -- Utkarsh Gupta F
12-06 05:03:24.0 +0530
+++ ruby-json-2.0.1+dfsg/debian/changelog2020-06-05 12:33:14.0 +0530
@@ -1,3 +1,10 @@
+ruby-json (2.0.1+dfsg-3+deb9u1) stretch; urgency=high
+
+ * Add patch to fix unsafe object creation vulnerability.
+(Fixes: CVE-2020-10663
+
+ -- Utkarsh Gupta F
02-25 23:03:06.0 +0530
+++ ruby-json-2.1.0+dfsg/debian/changelog2020-06-05 12:13:54.0 +0530
@@ -1,3 +1,10 @@
+ruby-json (2.1.0+dfsg-2+deb10u1) buster; urgency=high
+
+ * Add patch to fix unsafe object creation vulnerability.
+(Fixes: CVE-2020-10663)
+
+ -- Utkarsh Gupta F
Hello,
The next Ruby team meeting is on Friday, 05th June at 1630 UTC.
(which is 1 day from now)
Please put the topics that you want to discuss here:
https://wiki.debian.org/Teams/Ruby/IRCMeetings
I look forward to (virtually) seeing y'all \o/
Best,
Utkarsh
Hi,
On Sun, May 31, 2020 at 6:50 PM Utkarsh Gupta wrote:
> On Sun, May 31, 2020 at 3:42 PM Pirate Praveen
> wrote:
> > An error occurred while loading
> > ./spec/jira/resource/user_factory_spec.rb.
> > Failure/Error: require 'pry'
> >
> > ArgumentError:
Hi,
On Sun, May 31, 2020 at 3:42 PM Pirate Praveen wrote:
> An error occurred while loading
> ./spec/jira/resource/user_factory_spec.rb.
> Failure/Error: require 'pry'
>
> ArgumentError:
> non-absolute home
> # ./spec/spec_helper.rb:3:in `'
> # ./spec/jira/resource/user_factory_spec.rb:1:in `'
Hi all,
I finally revived and updated our Teams/Ruby/IRCMeetings wiki page.
It now has:
- details of the meeting (when, where, how).
- agenda of the upcoming meeting.
- logs of the previously hosted meeting.
Hope this looks nice and fresh. Feel free to add other details as you see fit :)
Hi all,
We had a discussion about Rails 6 transition during the meeting today.
Whilst the status is temporarily blocked, it was bought up that the
testing of reverse dependencies is yet to be done.
Given that the number of reverse-(build-)dependencies are huge, it
would be nice to have some help
Hiya,
> As per discussion on IRC, this is now live: KGB notifications for
> commits and CI pipeline stati are now send to #debian-ruby-changes.
I just added the details about #debian-ruby-changes channel to our
Ruby team wiki page :)
Best,
Utkarsh
Hi everyone,
Thank you to everyone who joined!
And to those who couldn't, we look forward to seeing you in the next one! :)
We had a pretty nice (& a quick) meeting.
Here are the logs:
Minutes:
http://meetbot.debian.net/debian-ruby/2020/debian-ruby.2020-05-08-16.53.html
Minutes (text):
Hi all,
On Mon, Mar 2, 2020 at 4:19 AM Utkarsh Gupta wrote:
> I hope to be around there and willing to facilitate the same.
> Would people be interested? Remotely or otherwise?
>
> Given that we have CfP for DC20 open, I'd be happy to propose this if
> we have a mutual consent ov
Hi all,
As the subject makes it very clear, the next Ruby team meeting is on
Friday, 08th May at 1630 UTC.
(which is 1 day from now)
I look forward to (virtually) seeing y'all :)
Best,
Utkarsh
Hi Praveen,
On Mon, Apr 13, 2020 at 8:00 PM Pirate Praveen wrote:
> ruby-thor 0.20.3 is required for rails 6 transition and was in
> experimental for a long time. I tested reverse dependencies today and
> found only ruby-coveralls is failing with this version (#956600 filed).
thor 1.0.1 has
Hi all,
On Mon, Apr 6, 2020 at 10:40 PM Utkarsh Gupta wrote:
> This won't break anything and I hope there's no problem with this.
> I'm sending this to the list so there's no overlapping of work and
> everyone is aware (also read as: head's up for everyone).
>
> Let me know
Hi all,
I started working on ruby-http and ruby-rack sometime back and here's
how I plan to upload them to unstable.
ruby-http (4.4.1 to unstable)
==
Once ruby-http-parser clears NEW, I'll upload ruby-http to unstable
with Breaks for ruby-twitter's version in sid (that's the
Hi Valentin,
On Mon, Apr 6, 2020 at 2:09 AM Valentin Vidić wrote:
> Yes, I've noticed the warning too, did not know it was related to the
> new Ruby version. I've uploaded a new version of pcs, so it should be
> fixed now.
Thank you very much!
The recent upload, indeed, fixes the problem :)
Hi Kiran,
On Sun, 5 Apr, 2020, 5:15 AM , wrote:
> https://salsa.debian.org/hacksk-guest/ruby-gem-isolator
>
> Consider to review and upload it.
Please also enable tests by pulling specs/ from g/h.
Best,
Utkarsh
>
Hi Kiran,
On Sun, 5 Apr, 2020, 4:18 AM , wrote:
> https://salsa.debian.org/hacksk-guest/ruby-ruby-dep
> Consider to review and upload it.
>
Please also enable tests by pulling the specs/ from g/h.
Best,
Utkarsh
>
Hi Valentin,
Ruby 2.7 has now been made default (previously Ruby 2.5).
We're working on making ruby-defaults migrate to testing which is
being blocked by a couple of packages, out of which, one is pcs.
As per the logs[1], it seems that you just need to add:
Restrictions: allow-stderr in
Hi Praveen,
On Fri, Apr 3, 2020 at 11:19 AM Pirate Praveen wrote:
> It'd be better to share the reverse dependencies that fail to give a better
> idea of the impact.
ruby-twitter and ruby-webmock fail. But I'll take care of them myself
before the upload of ruby-http.
About ruby-twitter,
Hi all,
I've prepared the major version update for ruby-http, that is, from
3.3.0-2 to 4.4.1-1.
I intend to upload this version to unstable (after checking its
rev-deps, of course) as soon as ruby-http-parser clears NEW (uploaded
just a few minutes ago).
Hopefully, this should buy everyone
On Thu, Apr 2, 2020 at 2:04 PM Pirate Praveen wrote:
> >> >I'll upload pry 0.13.0 into unstable.
> >> >Thanks for your commit.
> >> Did you also fix the two broken packages mentioned by Daniel ?
> >I think no need to be special care.
> All these should be uploaded at the same time.
FWIW,
Hi Praveen,
On Thu, Apr 2, 2020 at 11:54 AM Pirate Praveen wrote:
> Did you also fix the two broken packages mentioned by Daniel ?
a) pry has "Breaks" for respective packages.
b) ruby-guard has been fixed and uploaded.
c) ruby-pry-byebug is fixed in the git repository. Waiting for your
ack to
Hi all,
As the subject makes it very clear, we all agreed to meet for the next
Ruby team meeting on Friday, 3rd April at 1630 UTC.
(which is 2 days from now)
I look forward to (virtually) seeing y'all :)
Best,
Utkarsh
Hi Antonio,
On Mon, 30 Mar, 2020, 6:10 AM Antonio Terceiro, wrote:
> I just made an upload of ruby-vcr to fix a FTBFS against the new version
> of ruby-webmock (also just uploaded). I couldn't figure out what is
> the problem with the new ruby-excon, so I didn't fix that yet.
The problem with
Hi all,
On Sun, Mar 8, 2020 at 1:15 PM Hideki Yamane wrote:
> I've investigated it and it seems that failure happens with ruby-rspec
> 3.9.0c1e0m1s2-1, not 3.8.0c0e1m0s0-1 in buster.
Hm, interesting.
Could someone take a look at this whenever free?
I, myself, don't have enough time to take a
Hi Praveen,
On Sat, Mar 14, 2020 at 4:54 PM Pirate Praveen wrote:
> I have patched webpack to use uglifyjs-webpack-plugin till
> terser-webpack-plugin is availabel in the archive. I confirmed jekyll
> is building fine, I'll upload it soon.
Thank you very much for your quick fix!
Very much
Hi,
On Sat, Mar 14, 2020 at 4:19 PM Pirate Praveen wrote:
> How did you run the autopkgtest? I'm still seeing the failure. After
> bundle-bin-path there should be a testsuite which failed. Can anyone else
> confirm this?
I can confirm that the testsuite fails. There seems to be an
Hi,
On Fri, Mar 13, 2020 at 1:23 PM Pirate Praveen wrote:
> > Consider to review and upload it.
>
> Uploaded and pushed to ruby-team on salsa. I don't think mentioning it
> is a dependency of gitlab in description is useful (it is useful in an
> itp), so removed it.
The extended description is
Hi there,
Currently, Jekyll doesn't build. Here's why:
This commit[1] introduced using webpack. However this command:
```
cd debian/node_modules/livereload-js; webpack --entry ./lib/startup.js \
--output
../../../lib/jekyll/commands/serve/livereload_assets/livereload.js; cd
-
```
fails
Hi everyone,
Thank you to everyone who joined!
And to those who couldn't, we look forward to seeing you in the next one! :)
We had a pretty nice (& a quick) meeting.
Here are the logs:
Minutes:
http://meetbot.debian.net/debian-ruby/2020/debian-ruby.2020-03-13-16.35.html
Minutes (text):
Hi everyone,
On Thu, 12 Mar, 2020, 2:26 AM Utkarsh Gupta, wrote:
> So the results of both the poll bring us to the conclusion that..
>
> The meeting would be held on Friday, 13th March 2020 (consensus at
> [1]) and the time slot would be 1730 to 1830 CET / 1330 to 1430 BRT /
> 2
Hi all,
On Mon, Mar 2, 2020 at 2:36 AM Utkarsh Gupta wrote:
> Right. So after some permutation & combination, I propose the
> following time slots:
>
> 1. 1530 to 1630 CET / 1130 to 1230 BRT / 2000 to 2100 IST
> 2. 1630 to 1730 CET / 1230 to 1330 BRT / 2100 to 2200 IST
&g
Hi Kiran,
On Tue, Mar 10, 2020 at 12:45 PM wrote:
> both things are done
> can u review it
Uploaded with a minor fix. Check the last commit.
And thanks for your quick fix!
Best,
Utkarsh
---
ML Guidelines:
http://www.shakthimaan.com/downloads/glv/presentations/mailing-list-etiquette.pdf
Hi Praveen,
On Tue, Mar 10, 2020 at 10:44 AM Pirate Praveen
wrote:
>> I think new packages have an exception on this one.
> No exceptions, a source only upload is required to migrate to testing. For
> tests, it requires at least devtools from git repo, probably more, so I
> suggested to
Hi Kiran,
On Tue, Mar 10, 2020 at 3:03 AM wrote:
> Consider to review and upload it.
The extended description is too short. Could you please add a bit more
of an explanation to it?
Additionally, run `cme fix dpkg` and commit the result :)
Once these two things are done, I'll be happy to
1 - 100 of 301 matches
Mail list logo
