Re: Removing packages no longer required for gitlab 11.x

Hi, The following packages were initially packaged for gitlab, but from 11.4.9, gitlab does not require it. I'm going to file removal requests for them if no one is interested to keep them. There are no reverse dependencies. ruby-sidekiq-limit-fetch ruby-peek-sidekiq ruby-dropzonejs-rails

Re: autopkgtest Rubygems dependency resolution: "No such file or directory - dpkg-parsechangelog"

On 12/17/18 12:02 AM, Georg Faerber wrote: > Hi all, > > Today I've worked on two packages, ruby-gpgme and ruby-sequel, and ran into > the > following error for both of them during autopkgtest: > > Checking Rubygems dependency resolution on ruby2.5 │ > >

Re: Removing packages no longer required for gitlab 11.x

On 11/26/18 5:42 PM, Pirate Praveen wrote: > Hi, > > The following packages are no longer a dependency of gitlab and there > are no other reverse dependencies. Removal request filed for the following packages, > ruby-grape-route-helpers #915697 > ruby-gemnasium-gitlab-servic

Removing packages no longer required for gitlab 11.x

Hi, The following packages are no longer a dependency of gitlab and there are no other reverse dependencies. ruby-grape-route-helpers ruby-gemnasium-gitlab-service ruby-allocations ruby-d3-rails So I'd like to request their removal as soon the current version in unstable migrates to testing. If

ruby-rainbow 2.x -> 3.x transition

Hi, I have uploaded ruby-rainbow 3.0 to experimental and will be uploading it to unstable soon when gitlab 11.3.10 is ready. The only breaking changes seem to be dropping support for ruby 1.9.3 and 2.0 [1]. Since it is a major update, the gemspec files of reverse dependencies will need to be

Re: advise on name for packaging json_schema gem...

On 2018, നവംബർ 7 2:50:08 AM IST, "Cédric Boutillier" wrote: >Do you have suggestions for naming for the binary package for the gem >json_schema? ruby-brandur-json-schema ? (from the github username which is common for forks) -- Sent from my Android device with K-9 Mail. Please excuse my

Re: gitlab for stretch-backports - call for testing

On 02/05/18 6:30 PM, Pirate Praveen wrote: > Hi team, > > I have rebuilt gitlab and all dependencies for stretch-backports and > uploaded here https://people.debian.org/~praveen/gitlab/ (about 157 ruby > packages were rebuilt). An update on the current status of this effort. Af

Re: help with ruby-redis test failure

On 10/11/18 11:50 PM, Joseph Herlant wrote: > Could it be due to the fact that you have sha1 certs? > https://salsa.debian.org/ruby-team/ruby-redis/blob/master/test/support/ssl/trusted-cert.crt > Not sure if it's still accepted with openssl 1.1. Thanks for the tip, these tests were running fine

help with ruby-redis test failure

Hi, Can someone help with ruby-redis test failure? Tests are failing in debian ci as well https://ci.debian.net/data/packages/unstable/amd64/r/ruby-redis/latest-autopkgtest/log.gz Thanks Praveen signature.asc Description: OpenPGP digital signature

Rails 5 transition plan - help needed

Hi team, Rails 5 is in experimental and we need to complete compatibility check of all reverse dependencies before it can be in unstable. We have started a wiki page to track progress, https://salsa.debian.org/ruby-team/rails/wikis/Transition-to-Rails-5.2-for-Debian-Buster This is manual now,

jekyll 3.8.3 is in experimental - testing requested

Hi, I have uploaded jekyll 3.8.3 to experimental (I wanted to update ruby-rouge, ruby-gollum-lib and ruby-sanitize), since I don't use jekyll myself if you can test it and confirm it before I upload to unstable, that would be great. Thanks Praveen signature.asc Description: OpenPGP digital

Re: Jekyll package test failing

On 26/07/18 10:53 PM, Pirate Praveen wrote: > On 26/07/18 7:37 PM, Manas Kashyap wrote: >> i did ITP for this package , plus this package is also failing ruby2.5 >> tests http://paste.debian.net/1035280/ .  > > Go through https://wiki.debian.org/Teams/Ruby/Packaging/Tests t

Re: Jekyll package test failing

On 26/07/18 7:37 PM, Manas Kashyap wrote: > i did ITP for this package , plus this package is also failing ruby2.5 > tests http://paste.debian.net/1035280/ .  Go through https://wiki.debian.org/Teams/Ruby/Packaging/Tests to understand common problems when running tests. signature.asc

Planning to remove more packages (was Re: Planning to remove ruby-underscore-rails)

On Tuesday 26 June 2018 11:39 AM, Pirate Praveen wrote: > On Tuesday 19 June 2018 03:26 PM, Pirate Praveen wrote: >> ruby-tinder is no longer required for gitlab and it has no other reverse >> (build) dependencies. It is affected by rc bug >> https://bugs.debian.org/cgi-

Planning to remove ruby-underscore-rails (was Re: Planning to remove ruby-tinder)

On Tuesday 19 June 2018 03:26 PM, Pirate Praveen wrote: > ruby-tinder is no longer required for gitlab and it has no other reverse > (build) dependencies. It is affected by rc bug > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890696 > > Please reply, take over maintenance and

Planning to remove ruby-tinder (was Re: planning to request removal of ruby-sprockets-es6)

On Thursday 03 May 2018 09:11 PM, Pirate Praveen wrote: > Hi team, > > I packaged ruby-sprockets-es6 (its dependencies > ruby-babel-transpiler, ruby-babel-source packaged by Sruthi) as it was a > dependency of gitlab earlier. Now they have moved to using babel via &

Re: gitlab for stretch-backports - call for testing

On Friday 15 June 2018 02:48 PM, Dominik George wrote: >>> I was able to update from gitlab 8 in stretch to gitlab 10 in my repo >>> (https://people.debian.org/~praveen/gitlab/) without any issues. >> >> Tested again - same error as before (which I expected, as the migration >> scripts did not

Re: gitlab for stretch-backports - call for testing

On Tuesday 05 June 2018 12:19 PM, Dominik George wrote: > Hi, > >> I was able to install it on a new machine and test basic functionality. >> Next in my TODO list is testing updgrade from stretch version. > > Did anything except the suite change? Because upgrade from the stretch > version is

Re: gitlab for stretch-backports - call for testing

On Monday 04 June 2018 08:01 PM, Dominik George wrote: > Any news about that migration, so I could test again? Please try again from (update apt url, stretch changed to stretch-backports) https://people.debian.org/~praveen/gitlab/ Many dependencies are now in official stretch-backports, but it

Re: A Debian Ruby Sprint in Europe (France?) during the fourth semester 2018?

On May 29, 2018 2:19:46 AM GMT+05:30, "Cédric Boutillier" wrote: >On Sun, May 27, 2018 at 09:01:47PM -0300, Lucas Kanashiro wrote: > >> Did you already think about the agenda of this sprint? > >Not really, I must admit :) I am sure that we could come up a list of a >few points. Already

ruby-http and openssl 1.1 issues

Hi team, While trying to update ruby-http to 3.3 we noticed this issue and it turns out ruby-http 2.2 is failing as well. Upstream issue https://github.com/httprb/http/issues/465 Any ideas? Thanks Praveen

Re: gitlab for stretch-backports - call for testing

On ചൊവ്വ 08 മേയ് 2018 09:25 വൈകു, Pirate Praveen wrote: > gitaly required ruby-rugged 0.27 and hence I updated ruby-rugged to > 0.27. I'm in the process of updating gitlab to 10.7.3 which will work > with ruby-rugged 0.27. I have uploaded gitlab 10.7.3 and installation should work now, p

Re: gitlab for stretch-backports - call for testing

On ചൊ, മേയ് 8, 2018 at 8:21 വൈകു, Dominik George wrote: Hi, I cannot install gitlab from your repository: Thanks for the report. I'm aware of this particular issue. See https://salsa.debian.org/ruby-team/gitlab/wikis/stretch-backports Could not find gem

Re: gitlab for stretch-backports - call for testing

On ബു, മേയ് 2, 2018 at 6:30 വൈകു, Pirate Praveen <prav...@onenetbeyond.org> wrote: I have rebuilt gitlab and all dependencies for stretch-backports and uploaded here https://people.debian.org/~praveen/gitlab/ (about 157 ruby packages were rebuilt). I'm tracking the blockers here

planning to request removal of ruby-sprockets-es6

Hi team, I packaged ruby-sprockets-es6 (its dependencies ruby-babel-transpiler, ruby-babel-source packaged by Sruthi) as it was a dependency of gitlab earlier. Now they have moved to using babel via webpack/nodejs. There are no reverse dependencies. If anyone is still interested in these

Re: gitlab for stretch-backports - call for testing

On വ്യാ, മേയ് 3, 2018 at 11:46 രാവിലെ, Leopold Palomo-Avellaneda wrote: Are you asking help for testing the package right? The bugs found reported via bugs in debian or mails to the list? You can report them as bugs. I have already found some more ruby packages for

Re: gitlab for stretch-backports - call for testing

[dropping -backports] On ബുധന്‍ 02 മേയ് 2018 06:30 വൈകു, Pirate Praveen wrote: > Hi team, > > I have rebuilt gitlab and all dependencies for stretch-backports and > uploaded here https://people.debian.org/~praveen/gitlab/ (about 157 ruby > packages were rebuilt). Bundler::Ge

Unblock ruby-hamlit (bd missing for armel)

On tracker.debian. org/gitlab, one of the items blocking testing migration is ruby-hamlit missing build on armel. This is caused by nodejs dropping support for armel. Dependency installability problem for ruby-hamlit on armel: ruby-hamlit build-depends on: - ruby-coffee-script:armel

Re: The future of rails

On March 29, 2018 2:51:52 PM GMT+05:30, Georg Faerber <ge...@riseup.net> wrote: >Hi Pirate, > >Thanks for your mail: > >On 18-03-29 12:00:38, Pirate Praveen wrote: >> On March 29, 2018 12:31:29 AM GMT+05:30, Georg Faerber ><ge...@riseup.net> wrote: >>

Re: The future of rails

On March 29, 2018 12:31:29 AM GMT+05:30, Georg Faerber wrote: >Hi all, > >We're developing a web interface for schleuder, to ease administration >of schleuder lists for users etc. This is currently using rails 4. > >We would like to get this into Debian as well. > >The release

gitlab-workhorse on salsa is moved to go-team/packages from ruby-team

Hi, Initially this was the only gitlab dependency using go and I thought it better to have it under ruby team so its easier to manage. Now golang-gitaly-proto, gitaly and their dependencies are already under go team and it is natural to move gitlab-workhorse there. Please update your local repos.

Re: Renaming ruby-factory-girl to ruby-factory-bot

On ചൊവ്വ 27 മാർച്ച് 2018 04:17 വൈകു, Georg Faerber wrote: > Sure -- I was just wondering, if this package is still used? Popcon > seems quite low, and there are no (build) rdepends. > This is a test dependency of diaspora. https://salsa.debian.org/ruby-team/diaspora/blob/master/Gemfile#L285 We

Re: build failing with sbuild for ruby-flipper

On ഞായര്‍ 18 മാർച്ച് 2018 08:25 വൈകു, Balasankar C wrote: > However, I now confirm the build fails and this is a valid issue. Update: git usage from all gemspecs had to be patched, not just the one's explicitly selected by DH_RUBY_GEMSPEC. signature.asc Description: OpenPGP digital signature

Re: build failing with sbuild for ruby-flipper

On വെള്ളി 16 മാർച്ച് 2018 01:05 വൈകു, Pirate Praveen wrote: > I'm combining all flipper-* gems to a single source package built from > github tarballs. But build with sbuild fails with the following error. > Unit193 on IRC mentioned it was building fine in pbuilder. All files in >

Re: Switching to gitlab-grit fork for ruby-grit

On വെള്ളി 16 മാർച്ച് 2018 05:01 വൈകു, Pirate Praveen wrote: > Hi, > > grit is dead upstream and I think it makes sense to use gitlab-grit > tarballs directly than maintaining a patch. > > Only ruby-gitlab-flowdock-git-hook depends on ruby-grit (this switch > will allow

Re: orphaned and to be removed packages

On ശനി 17 മാർച്ച് 2018 07:26 വൈകു, Hleb Valoshka wrote: > * ruby-little-plugger (ruby-logging) > * ruby-logging (ruby-googleauth, ruby-logging-rail) I need these two for gitlab so I'll take care of them. Added myself as uploader for both. signature.asc Description: OpenPGP digital signature

Switching to gitlab-grit fork for ruby-grit

Hi, grit is dead upstream and I think it makes sense to use gitlab-grit tarballs directly than maintaining a patch. Only ruby-gitlab-flowdock-git-hook depends on ruby-grit (this switch will allow us to remove a patch as well). If there is no objection, I'm planning to do it in the coming days.

build failing with sbuild for ruby-flipper

I'm combining all flipper-* gems to a single source package built from github tarballs. But build with sbuild fails with the following error. Unit193 on IRC mentioned it was building fine in pbuilder. All files in salsa. Can someone help? debian/rules override_dh_auto_install make[1]: Entering

Re: Planning to file a removal request for ruby-mustermann19

On ശനി 03 മാർച്ച് 2018 10:10 വൈകു, Pirate Praveen wrote: > Now that gitlab 9.5 is in unstable, there are no more reverse > dependencies for this package. > > To fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868851 I think > the best way is to remove ruby-mustermann

Planning to file a removal request for ruby-mustermann19

Now that gitlab 9.5 is in unstable, there are no more reverse dependencies for this package. To fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868851 I think the best way is to remove ruby-mustermann19. Just asking on the list because I was not the original uploader. signature.asc

Re: Uploading gitlab 9.5 to unstable

On വ്യാഴം 22 ഫെബ്രുവരി 2018 11:13 വൈകു, Pirate Praveen wrote: > gitlab depends on ruby-grape (>= 0.19.2~) - needs to fix test failure This is now ready for upload and now the only outstanding issue to be solved is failure in gitlab installation. See https://bugs.debian.org/cgi-bin/bugrepo

Re: Uploading gitlab 9.5 to unstable

On ചൊവ്വ 20 ഫെബ്രുവരി 2018 03:16 വൈകു, Pirate Praveen wrote: > Hi, > > I'm planning to upload gitlab to unstable in the coming days. It will > involve uploading the following packages currently in experimental along > with gitlab. This is the remaining packages, help is welcom

Re: Uploading gitlab 9.5 to unstable

On ബുധന്‍ 21 ഫെബ്രുവരി 2018 06:51 വൈകു, Héctor Orón Martínez wrote: > OK, sounds fine. > On other matters can we get rails 5 into experimental now? That is the next item in my TODO list after moving gitlab to unstable. signature.asc Description: OpenPGP digital signature

Re: Uploading gitlab 9.5 to unstable

On ചൊവ്വ 20 ഫെബ്രുവരി 2018 03:42 വൈകു, Pirate Praveen wrote: >> obs-api: >> gitlab depends on ruby-kaminari (>= 1.0~); however: >> Version of ruby-kaminari on system is 0.17.0-3. > > This package does not have any autopkgtests (copied its maintainers). > > And

Re: Uploading gitlab 9.5 to unstable

[copying maintainers of affected packages] On ചൊവ്വ 20 ഫെബ്രുവരി 2018 03:16 വൈകു, Pirate Praveen wrote: > berkshelf-api: > gitlab depends on ruby-grape (>= 0.19.2~); however: > Version of ruby-grape on system is 0.16.2-2. It's autopkgtest is already failing with a previous uplo

Uploading gitlab 9.5 to unstable

Hi, I'm planning to upload gitlab to unstable in the coming days. It will involve uploading the following packages currently in experimental along with gitlab. I think only ruby-grape and ruby-kaminari uploads need a deeper look. Let me know if you see nay potential problem with any other

Re: Package: gitlab (8.13.11+dfsg1-8) -- Stretch stable, FEEDBACK

Hi Chip, Thanks for the feedback, sorry for the late reply. On വ്യാഴം 21 ഡിസംബര്‍ 2017 10:04 രാവിലെ, Chip Frank wrote: > > To Whom It May Concern: > > > I like to try new software from time-to-time. I've seen some of the > awesomeness of Gitlab (in-action). That said, using a clean install of >

Re: Alioth repository becoming R/O and moving to salsa.debian.org

On 2018, ജനുവരി 6 5:15:38 AM IST, "Cédric Boutillier" wrote: > cost of the >effort was very small anyway. > >Since the VCS entry is used by debcheckout and similar tools, as long >as >stretch is supported, I think it is a good thing that these tools reach >the correct git

Re: Migrating off alioth

On 12/26/2017 09:12 PM, Chris Hofstaedtler wrote: >> I'd prefer if tracker.debian.org allows creation of teams [1] though it >> is only in discussion stage. I'm worried about the volume of mails, but >> if that is the only option, we may have to go for it. > > For now this appears to be our only

Re: Migrating off alioth

On 12/26/2017 09:12 PM, Chris Hofstaedtler wrote: > Right. So before reading this I've gone ahead and got us > https://salsa.debian.org/debian-ruby > > From what I see we could also have gotten ruby-team or just plainly > ruby (see qa, postgresql teams). > I think we can get another rename, but

Re: Migrating off alioth

On 12/26/2017 08:28 PM, Chris Hofstaedtler wrote: > Hey *, > > Hope your holidays have been going well. > > As you're all hopefully aware, Alioth has an expiration date [1]: > 2018-05-01, with incoming mail service ending 2018-02-01. > > Therefore we must take action soon, on at least these two

Re: Renaming ruby-factory-girl to ruby-factory-bot

On വെള്ളി 01 ഡിസംബര്‍ 2017 04:44 രാവിലെ, Georg Faerber wrote: > Hi all, > > Upstream decided [1] to rename factory-girl to factory-bot, because "The > name "Factory Girl" was confusing to some developers who encountered > this library, and offensive or problematic to others." [2] > > We're using

Re: Packing a RoR-Application

On ശനി 30 സെപ്റ്റംബര്‍ 2017 08:50 വൈകു, Jan Luehr wrote: > - Will the Ruby On Rails stack in Stretch receive security fixes during > Stretch's lifetime? I'd think it follows the same policy as any other package in stretch. > - Can you recommend a template or howto for packing ror-applications

Re: RFS: ruby-gitlab 4.2.0

On 09/21/2017 06:47 PM, Lucas Kanashiro wrote: > After had a look in the spec/spec_helper.rb file I realized that it > tries to use require with a relative path, and this will not work in a > installed version. So, I think that you could create a patch to fix it, > could you do it please? > >

help with non-C ext folder in rainbow

Hi, rainbow 2.2.2 introduced an 'ext' folder (this was not present in earlier versions and this seems to be removed in git master) which makes gem2deb think it is a native extension and creates an empty directory causing lintian to report an error E: ruby-rainbow:

Re: help/ideas for debugger-ruby_core_source

On തിങ്കള്‍ 11 സെപ്റ്റംബര്‍ 2017 01:46 രാവിലെ, Antonio Terceiro wrote: > I didn't look into details, but I could gather a few facts: > Thanks! > 1) rblineprof is a _development_ tool, you > should not have to package it to have gitlab in the archive. > gitlab mentions peek-rblineprof as a

help/ideas for debugger-ruby_core_source

Hi, I have just created ruby-debugger-ruby-core-source in alioth (it is a dependency of rblineprof which in turn is a dependency of gitlab 9.5.x). Would it be enough to just use the .h files we ship in ruby2.3-dev? Or can we include .inc files too in -dev package? I can see many more files in

updating ruby-kaminari to 1.0.1

Hi, I have just uploaded ruby-kaminari 1.0.1 to experimental. But since this is a major update I'd like some help with updating/testing its reverse dependencies. obs-api, ruby-rails-admin and reverse build dependencies * open-build-service * ruby-api-pagination * ruby-rails-admin Thanks

Re: scaling down my participation in the Ruby team

On 2017, ഓഗസ്റ്റ് 26 3:12:28 AM IST, Antonio Terceiro wrote: >I still consider myself part of the team, and will still help fixing >stuff now and then (specially in the case of packages that I use), but >my participation will be reduced so that I can focus on other things

Re: help with building ruby-grpc

On ചൊവ്വ 08 ആഗസ്റ്റ് 2017 02:20 രാവിലെ, Antonio Terceiro wrote: > You can try something like this in debian/ruby-tests.rake (untested): > > unless ENV['ADTTMP'] > # during the build, look for library in the source tree > ENV['LD_LIBRARY_PATH'] = path_to_local_dir_containing_libgrpc_a > end >

help with building ruby-grpc

Hi, I have been trying to build ruby-grpc for last many weeks without success. Current work can be found at https://git.fosscommunity.in/praveen/grpc (under branch ruby). RUBYLIB=.

updating rails to 4.2.6

Hi, I have uploaded rails 4.2.9 to experimental because autopkgtests for a lot of reverse dependencies failed. Some of them may be unrelated failures. A list of all packages that failed is at rails-4.2.9.txt in https://wiki.debian.org/gobby.debian.org under Teams/RubyExtras Please see if you can

breaking changes in unstable and suggestion to use experimental

Hi, I think we should use experimental for breaking changes (major updates) and give time and notice for people to fix incompatibilites. I'm referring to ruby-webmock and ruby-net-ssh updates, which should have been uploaded to experimental and given people chance to fix dependencies. Now gitlab

Re: dealing with test failures caused by new webmock

On വ്യാഴം 20 ജൂലൈ 2017 01:52 വൈകു, Lucas Nussbaum wrote: > Have you tried to rebuild that one in a local sbuild environment created > by the setup script in pkg-ruby-extras ? It also fail for me in that > case. > > I haven't tried the others -- I wanted to check if it was specific to > the AWS

dealing with test failures caused by new webmock

Hi, Many tests are not failing because of newer webmock. at least 4 dependencies of gitlab failed (so I noticed) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867645 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867649 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867654

Re: DH_RUBY_GEMSPEC and check_dependencies in gem2deb-test-runner

On ചൊവ്വ 18 ജൂലൈ 2017 12:49 വൈകു, Cédric Boutillier wrote: > Do you have an idea? see #867739 it is already implemented in git. If debian/gemspec is available gem2deb will use that. You can just add a symlink. signature.asc Description: OpenPGP digital signature

Re: Problem installing GitLab

On തിങ്കള്‍ 17 ജൂലൈ 2017 10:05 വൈകു, David Goodenough wrote: > Can I install two versions of ruby-asana at once (sorry I am a ruby newbie) > or does gitlab need to be upgraded? Thanks for the report. I did not consider this issue when updating ruby-asana. New version of gitlab needs asana 0.6.0

Re: Use MIT license in gem2deb copyright template

On 06/28/2017 12:40 PM, Balasankar C wrote: > Hi all, > > Currently, the template copyright file that is generated by gem2deb uses > GPL-2.0+ as a placeholder license. Since a majority of the Ruby gems are > under MIT/Expat license, can we use that instead? I had opened a bug[0] > long back about

can anyone review diaspora-installer?

Hi team, A review will help with unblock request. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858180#37 Losing diaspora-installer after putting years long effort would be very demotivating. thanks Praveen signature.asc Description: OpenPGP digital signature

looking for some help with backporting git 2.11 support to gitlab 8.13.11

Hi team, I tried backporting git 2.11 support from gitlab 8.15.x series to 8.13.11, but its more complicated than I initially thought. With help from Balasankar, we tried to find more commits that would need to be backported as well, but we are not able to fix it fully. See

Re: Switching to gitlab-turbolinks-classic (gitlab fork) for ruby-turbolinks source

Sorry, my firefox os email client swallowed the contents of my previous mail, it seems :( Switching back to turbolinks in buster would be just a matter of changing watch file and removing copy-gemspec file. Maintaining a patch is comparatively more work for the same result, but I will do it

ruby-pg 0.19 and multiple gemspec files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I'm trying to build ruby-pg 0.19 (for diaspora 0.6.2.0 targeted for experimental) but in sbuild there were two gemfiles, pg.gemspec and pg-0.19.gemspec (second one manually created in debian/rules) I added DH_RUBY_GEMSPEC to specify

Re: Switching to gitlab-turbolinks-classic (gitlab fork) for ruby-turbolinks source

Antonio Terceiro wrote: > On Sun, Jan 15, 2017 at 10:03:40PM +0530, Pirate Praveen wrote:>> On ഞായര്‍ > 15 ജനുവരി 2017 09:42 വൈകു, Antonio Terceiro wrote:>>> I would prefer to not > do that this close to a freeze. Is there a good >>> reason for the fork?

Re: Please test reverse dependencies before uploading new versions (ruby-grape-entity broke gitlab)

On ബുധന്‍ 30 നവംബര്‍ 2016 06:01 വൈകു, Antonio Terceiro wrote: > I support your request, and urge people uploading libraries (or anything > with reverse dependencies, really) to test their reverse dependencies. > > *However*, looking at the diff between the latest ruby-grape-entity and > the one

Please test reverse dependencies before uploading new versions (ruby-grape-entity broke gitlab)

Hi Lucas, Last upload of ruby-grape-entity broke gitlab[1][2]. Your last update of ruby-grape also broke gitlab [3]. Please run build-and-upload script from pkg-ruby-extras before uploading new version. If it was a stable library with SemVer compliance we could declare more relaxed dependency on

Re: jquery 3.x uploaded to unstable

[adding debian-ruby] On Sunday 23 October 2016 04:23 AM, Antonio Terceiro wrote: > jQuery 3.0 was release back in June, so in principle affected upstreams > had at least a few months to deal with any fallout. If that's not the > case, you can refer upstream to this upgrade guide, which documents

Re: help needed to fix ruby-carrierware FTBFS

On ബുധന്‍ 09 നവംബര്‍ 2016 12:08 രാവിലെ, Pirate Praveen wrote: > Hope someone from mysql maintainers team can help here. > 161109 12:04:57 [ERROR] /usr/sbin/mysqld: unknown option '--initialize-insecure' 161109 12:04:57 [ERROR] Aborting So it seems mariadb is not a drop in replacement for

Re: help needed to fix ruby-carrierware FTBFS

[adding pkg-mysql-maint] On Monday 07 November 2016 06:51 PM, Scott Leggett wrote: > On 2016-11-06.22:48, Pirate Praveen wrote: >> With the recent upload of mysql-server 5.7, mysql_install_db is >> deprecated, we are supposed to use mysqld --initialize. >> >> I tr

Re: [pkg-go] help fixing gitlab-workhorse build failure on s390x

On Friday 04 November 2016 04:30 PM, Michael Hudson-Doyle wrote: > Go only works on z196, which is only one of the buildds, is that the > problem here? It is failing on zemlinsky, earlier successfull build was on zandonai. So it looks like buildd issue. How do I get it to build with the correct

help fixing gitlab-workhorse build failure on s390x

[cc me on replies from s390 list] gitlab-workhorse is blocking gitlab 8.12.3 migration to testing for sometime now. I fixed two issues with powerpc build but this issue seems hard to crack. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843148 for details Any help fixing this issue would

Re: trying to update unicorn to 5.1, build failure: VERSION= must be specified

On Friday 28 October 2016 05:53 AM, Eric Wong wrote: > I understand olddoc may not be worth the effort to package in > Debian. (I already tried to reduce dependencies in olddoc > compared to wrongdoc, but a package is a package...) > > Anyways, I suggest you guys grab the generated gemspec from

Symlinks to packaged assets when using gem-install option

Hi, Before gem-install option was introduced, we were using debian/links to symlink js files from /usr/share/javascript/foo to /usr/share/ruby-rails-assets-foo/app/assets/javascripts. But with gem-install option, version of the gem is added to the directory in

trying to update unicorn to 5.1, build failure: VERSION= must be specified

Hi, Its pushed to alioth. Can someone check? Error below: $ clean dh clean --buildsystem=ruby --with ruby,systemd dh_testdir -O--buildsystem=ruby dh_auto_clean -O--buildsystem=ruby dh_ruby --clean dh_ruby --clean VERSION= must be specified dh_auto_clean: dh_ruby --clean

enabling contrib and non-free in build-and-upload

Hi, Currently build-and-upload checks only main for dependencies so it is missing diaspora (it is moved to contrib). Can we add contrib and non-free to build-and-upload? Praveen signature.asc Description: OpenPGP digital signature

Re: Using build-and-upload for packages targeted at experimental

Do we really need to generate keys for sbuild? sudo sbuild-update --keygen signature.asc Description: OpenPGP digital signature

Using build-and-upload for packages targeted at experimental

Hi, Is this change ok? It will not work when build dependencies from experimental are required but will work in the simple case of just stashing packages in experimental to not break dependencies in unstable. diff --git a/build-and-upload b/build-and-upload index 1a41c68..66fd4d1 100755 ---

Re: ruby-gemojione and gem-install

On 2016, ആഗസ്റ്റ് 26 12:35:33 AM IST, Antonio Terceiro <terce...@debian.org> wrote: >On Thu, Aug 25, 2016 at 04:01:11PM -0300, Antonio Terceiro wrote: >> On Thu, Aug 25, 2016 at 01:31:48PM +0530, Pirate Praveen wrote: >> > On Tuesday 23 August 2016 07:58 PM

Re: ruby-gemojione and gem-install

On Tuesday 23 August 2016 07:58 PM, Antonio Terceiro wrote: > On Tue, Aug 23, 2016 at 06:48:01PM +0530, Pirate Praveen wrote: >> Thanks, this is working. I can fix ruby-fog-openstack autopkgtest >> failures easily once this is uploaded (it would be helpful to remove >> patch

Re: Accepted ruby-handlebars-assets 2:0.23.0-3 (source all) into unstable, unstable

On 2016, ആഗസ്റ്റ് 23 7:52:24 PM IST, Antonio Terceiro <terce...@debian.org> wrote: >On Mon, Aug 22, 2016 at 10:00:20PM +0000, Pirate Praveen wrote: >> Format: 1.8 >> Date: Mon, 22 Aug 2016 13:16:51 +0530 >> Source: ruby-handlebars-assets >> Binary: ruby-handleba

Re: RFS: ruby-rack-oauth2

On Tuesday 23 August 2016 05:19 PM, s...@disroot.org wrote: > Hi, > > I updated the packaging ruby-rack-oauth2 from 1.2.1 to 1.4.0. I tested it > with build-and-upload script from pkg-ruby-extras repo. > > It is pushed to Alioth repo (my ssh access started working). > > Please review and

Re: ruby-gemojione and gem-install

On Tuesday 16 August 2016 06:38 PM, Antonio Terceiro wrote: > On Tue, Aug 16, 2016 at 11:43:54AM +0530, Pirate Praveen wrote: >> On 08/16/2016 11:43 AM, Pirate Praveen wrote: >>> hi, >>> >>> I'm trying to update gemojione to 3.1.0. I thought moving to DH_RUBY

Re: RFS: ruby-fog-cloudatcost

On Monday 22 August 2016 09:04 PM, s...@disroot.org wrote: > Hi, > > I prepared the packaging of ruby-fog-cloudatcost. It is lintian clean and I > tested it with build-and-upload script from pkg-ruby-extras repo. > > > I am still unable to ssh to git.debian.org and I have logged a support >

Re: RFS: ruby-bootstrap-switch-rails

On Thursday 18 August 2016 10:34 PM, Abhijith PA wrote: > Hello team, > > The following package is IMHO ready to be uploaded > > * ruby-bootstrap-switch-rails-3.3.3-1 > > Please review and upload it. Uploaded, thanks! signature.asc Description: OpenPGP digital signature

Re: RFS: ruby-fog-core

On Thursday 18 August 2016 11:55 AM, s...@disroot.org wrote: > Hi, > > I updated the packaging ruby-fog-core from 1.40 to 1.42. I tested it with > build-and-upload script from pkg-ruby-extras repo. Two packages > (ruby-openstack and ruby-rackspace) failed tests, but they were unrelated >

ruby-gemojione and gem-install

hi, I'm trying to update gemojione to 3.1.0. I thought moving to DH_RUBY = --gem-install would be better than maintaining patches, but 'config' folder does not get installed (the overrides in rules method or install file also fails). gem2deb bug? Can someone help? signature.asc Description:

Re: build-and-install fails to setup apt archive (looks like a gpg2 migration issue)

On 08/13/2016 06:06 PM, Christian Hofstaedtler wrote: > * Pirate Praveen <prav...@onenetbeyond.org> [160813 13:57]: >> gpg: /<>/resolver-qbYTZz/gpg/trustdb.gpg: trustdb created >> gpg: Warning: not using 'Sbuild Signer' as default key: No secret key >> gpg: al

build-and-install fails to setup apt archive (looks like a gpg2 migration issue)

This happened after I ran a dist-upgrade in my local sid system today. +--+ | Install build-essential | +--+ Setup apt archive

Re: using npm_assets instead of browserify

https://medium.com/technically-speaking/rails-react-browserify-e315001d5974#.you4k7h14 browserify-rails seems another method but node-browserify has long list of dependencies as well. On 2016, ജൂലൈ 28 12:24:28 AM IST, Pirate Praveen <prav...@onenetbeyond.org> wrote: >https://g

using npm_assets instead of browserify

https://github.com/GoodGuide/npm_assets/blob/master/README.markdown Can anyone comment if this can be used instead of browserified js? For example, can we directly use node-handlebars instead of ruby-rails-assets-handlebars for diaspora using this method? -- Sent from my Android device with

gitlab, rails and stretch

Hi, Just wanted to share this here. https://gitlab.com/gitlab-org/gitlab-ce/issues/14286#note_13369583 gitlab is planning to move to rails 5, but stretch is going to release with rails 4.2, I'm asking gitlab upstream to support gitlab 4.2 release until at least stretch release. After stretch

<    1   2   3   4   5   6   7   8   >