Bug#910964: libprotobuf17 might need Breaks: libprotobuf10

On Sat, 20 Oct 2018 11:36:55 +0200 =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= wrote: > 2) Packages that depend on each other, need to be compiled with the > same ProtoBuf version. This should be expressed in those package > dependencies. You might want to comment here

Bug#910964: libprotobuf17 might need Breaks: libprotobuf10

On Sun, 21 Oct 2018 13:27:52 +0530 Pirate Praveen wrote: > I have also asked upstream for support here > https://github.com/protocolbuffers/protobuf/issues/5276 there is already > one person assigned to it. > Upstream confirmed it is debian specific and it seems this shou

Bug#900429: protobuf 3.5.2 transition and ignition-transport

On 10/22/18 12:27 AM, Jochen Sprickerhof wrote: > * Pirate Praveen [2018-10-22 00:19]: >> See point 2 of >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910964#29 >> >> May be you want to tighten the build dependency versions. > > Do you have

Bug#900429: protobuf 3.5.2 transition and ignition-transport

ersion 1.0.0+dfsg1-5+b1 for the transition ;) ) and it's building > again. Hi Jochen, See point 2 of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910964#29 May be you want to tighten the build dependency versions. Thanks Praveen signature.asc Description: OpenPGP digital signature

Bug#910964: libprotobuf17 might need Breaks: libprotobuf10

On Sat, 20 Oct 2018 11:36:55 +0200 =?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= wrote: > Let's break it to parts. > 1) Can libprotobuf10 and libprotobuf17 installed together and > independent packages working correctly with these libraries? Yes, > these are possible. I don't see the need

Bug#910964: libprotobuf17 might need Breaks: libprotobuf10

PATH AddPerson.java ListPeople.java com/example/tutorial/AddressBookProtos.java com/example/tutorial/AddressBookProtos.java:1077: error: cannot find symbol private com.google.protobuf.Timestamp lastUpdated_; full log, https://ci.debian.net/data/packages/unstable/amd64/p/protobuf/latest-autopkgtest/

Bug#909840: gitlab: not suitable for stable Debian releases

Control: severity -1 normal On 2018, സെപ്റ്റംബർ 29 5:36:44 PM IST, Adrian Bunk wrote: >Package: gitlab >Severity: serious > >Looking at #909315 I doubt we can security support >gitlab in buster until the non-LTS EOL of buster mid-2022. I don't think this is right. 1. 8.x to 9.x saw a big jump

Bug#876618: [Pkg-javascript-devel] Bug#876618: science.js build-depends on removed nodejs-legacy

On 2018, സെപ്റ്റംബർ 28 10:52:24 AM IST, Petter Reinholdtsen wrote: > >vows test/env-assert.js test/\*/\*-test.js >module.js:549 >throw err; >^ > >Error: Cannot find module 'glob' Just add node-glob as build dependency. -- Sent from my Android device with K-9 Mail. Please excuse my

Bug#890141: seems the bug is gone with nodejs 8.11.2

---+ Unpack source - Format: 3.0 (quilt) Source: node-dashdash Binary: node-dashdash Architecture: all Version: 1.14.1-1 Maintainer: Debian Javascript Maintainers Uploaders: Pirate Praveen Homepage: https://github.com/trentm/node-dashdash#readme Standards-V

Bug#909101: npm2deb create fails with Error downloading package %s@s\n" % (self.name, self.version)

package: npm2deb version: 0.2.8-1 severity: grave justification: fails to perform its core function of creating debs npm2deb create @ava/write-file-atomic Traceback (most recent call last): File "/usr/bin/npm2deb", line 7, in sys.exit(main(sys.argv)) File

Bug#907488: gitlab: post-inst fails: Could not find gem 'rugged (~> 0.26.0)'

want a working version, use people.debian.org/~praveen/gitlab until we fix this situation. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#904026: gitlab is blocked in NEW

Control: fixed -1 10.7.7+dfsg-1 Last two security updates are blocked in NEW because a previous upload included gitlab-common binary. It is stuck in NEW since 13 Jun 2018. signature.asc Description: OpenPGP digital signature

Bug#903780: unstable version is known broken

Control: fixed -1 10.7.3+dfsg-1 Control: blocke -1 by 901015 Waiting on protobuf and grpc in experimental to reach unstable to reupload the version in experimental (which fixes this) to unstable. signature.asc Description: OpenPGP digital signature

Bug#893610: closed by Pirate Praveen (Bug#893610: fixed in ruby-sanitize 4.6.5-1)

On 29/07/18 12:04 PM, Salvatore Bonaccorso wrote: > Any plans for moving this to unstable, or is anything blocking it? ruby-gollum-lib needs an update along with ruby-sanitize, but this ruby-gollum-lib update also needs a newer ruby-rouge. Updating ruby-rouge requires an update to jekyll, which

Bug#904004: libgit2 FTBFS on armhf internal compil,er error: Segmentation fault

On 18/07/18 6:39 PM, John Paul Adrian Glaubitz wrote: > I don't think your last upload was a good idea as you apparently > didn't test your change on all affected architectures. The testsuite > still fails on mips64el and ppc64el. The previous upload was failing only on amrhf so thought fixing

Bug#904004: libgit2 FTBFS on armhf internal compil,er error: Segmentation fault

On 18/07/18 4:20 PM, John Paul Adrian Glaubitz wrote: > Did you run the testsuite? > testsuite is run during build. I ran dpkg-buildpackage with gcc-8 in build depends and export CC=gcc-8 in rules. signature.asc Description: OpenPGP digital signature

Bug#904004: libgit2 FTBFS on armhf internal compil,er error: Segmentation fault

On 18/07/18 2:57 PM, John Paul Adrian Glaubitz wrote: >> So I think it gives a us bit more time until these switch away from gcc-6. > > No, it won't because any package that does not build with gcc-8 is considered > an RC bug. There is no way around this other than fixing the build on gcc-8. I

Bug#904004: libgit2 FTBFS on armhf internal compil,er error: Segmentation fault

On 18/07/18 2:29 PM, John Paul Adrian Glaubitz wrote: > On 07/18/2018 10:34 AM, Pirate Praveen wrote: >> I was able to build it with gcc-6 installed and 'export CC=gcc-6' added >> to debian/rules. >> >> Is it a good idea to build with gcc-6 in the short term? &

Bug#904004: libgit2 FTBFS on armhf internal compil,er error: Segmentation fault

Control: block 901011 by -1 On Wed, 18 Jul 2018 09:58:36 +0530 Pirate Praveen wrote: > package: libgit2 > version: 0.27.0+dfsg.1-0.7 > severity: serious > > On harris.debian.org (armhf porterbox) I got this error. > > /home/praveen/libgit2-0.27.0+dfsg.1/tests/checkou

Bug#904004: libgit2 FTBFS on armhf internal compil,er error: Segmentation fault

package: libgit2 version: 0.27.0+dfsg.1-0.7 severity: serious On harris.debian.org (armhf porterbox) I got this error. /home/praveen/libgit2-0.27.0+dfsg.1/tests/checkout/tree.c: In function 'test_che ckout_tree__target_directory_from_bare': /home/praveen/libgit2-0.27.0+dfsg.1/tests/checkout

Bug#898884: fixed in python-pygit2 0.27.0-1

On Thu, 17 May 2018 10:51:01 + =?utf-8?b?T25kxZllaiBOb3bDvQ==?= wrote: > Source: python-pygit2 > Source-Version: 0.27.0-1 Please upload this to unstable, libgit2 0.27 is in unstable now. signature.asc Description: OpenPGP digital signature

Bug#899324: closing 899324

close 899324 thanks

Bug#899324: ruby-font-awesome-rails: broken with fonts-font-awesome 5

On Tue, 22 May 2018 16:49:12 -0300 Antonio Terceiro wrote: > My suggestion would be to: > > - base the CSS template on > /usr/share/fonts-font-awesome/css/font-awesome.css which is a modified > version of the FontAwesome v5 stylesheet adding backwards > compatibility for usage of

Bug#902726: 2018/06/25 security release

Control: tags -1 pending Control: fixed -1 10.7.6+dfsg-1 On Fri, 29 Jun 2018 23:09:22 +0200 Moritz Muehlenhoff wrote: > https://about.gitlab.com/2018/06/25/security-release-gitlab-11-dot-0-dot-1-released/ 10.7.6 is already uploaded, but it is stuck in NEW, because last upload introduced a new

Bug#892742: rollup FTBFS with node-rollup-plugin-commonjs 9.0

On Tue, 19 Jun 2018 16:16:15 +0530 Pirate Praveen wrote: > Latest version of rollup is 0.60.7 and it has already moved to > rollup-plugin-commonjs 9.x > > https://github.com/rollup/rollup/blob/6e004184ede79832e658c22983de439aa5c30462/package.json > Using node-rollup-plugin-t

Bug#892742: rollup FTBFS with node-rollup-plugin-commonjs 9.0

On Mon, 12 Mar 2018 18:41:36 +0530 Pirate Praveen wrote: > Package: src:node-rollup > Version: 0.50.0-1 Latest version of rollup is 0.60.7 and it has already moved to rollup-plugin-commonjs 9.x https://github.com/rollup/rollup/blob/6e004184ede79832e658c22983de439aa5c30462/packag

Bug#888095: [debian-mysql] Bug#888095: Bug#888095:

On Monday 18 June 2018 04:09 AM, Otto Kekäläinen wrote: > If you want to help, please make a pull request on Salsa or even at > upstream. I would prefer nobody forces a substandard version of > MariaDB 10.3 into Debian because the cost of fixing it afterwards > becomes so high. > I think you are

Bug#888095: [debian-mysql] Bug#888095:

On Thu, 14 Jun 2018 15:57:18 +0800 Andy Li wrote: > I'm sure you have been busy, but this issue has been there unfixed for > several months. > I would appreciate if you can spend a few minutes to answer our questions. > If you lack the time to maintain the package, would you let the Debian >

Bug#880276: ruby-encryptor: FTBFS: ERROR: Bug is still present?

On Wed, 28 Mar 2018 14:45:42 +0200 =?UTF-8?B?RGF2aWQgTMOzcGV6IFphamFyYSAoRXJfTWFxdWkp?= wrote: > Hi, > > Are this bug still present with ruby2.5? Yes, fails in ruby 2.5. This has been open for a long time with no response from upstream :(

Bug#895107: ruby-kaminari: FTBFS: InvalidSpecificationException

fixed 895107 1.0.1-4 thanks On Fri, 6 Apr 2018 23:25:13 -0700 Steve Langasek wrote: > Source: ruby-kaminari > Version: 1.0.1-3 > Severity: serious > User: ubuntu-de...@lists.ubuntu.com > Usertags: origin-ubuntu bionic > > Hi Pirate, > > The ruby-kaminari package fails to build in a clean,

Bug#901223: [pkg-go] Bug#901223: gitaly: FTBFS: prometheus.Observer does not implement prometheus.Histogram

On Wed, 13 Jun 2018 10:48:11 +0100 =?UTF-8?Q?Mart=c3=adn_Ferrari?= wrote: > I think the problem is the latest upload of > golang-github-prometheus-client-golang-dev, which had some incompatible > changes. It also affected docker go-metrics (#900597). > > Sadly, the only solution is to update to

Bug#901223: gitaly: FTBFS: prometheus.Observer does not implement prometheus.Histogram

On Sun, 10 Jun 2018 11:10:48 +0200 Andreas Beckmann wrote: > Justification: fails to build from source (but built successfully in the past) seems broken by golang-github-prometheus-common-dev 0+git20180518.7600349-1 signature.asc Description: OpenPGP digital signature

Bug#900677: ruby-google-protobuf: does not install pure ruby files

On Sun, 3 Jun 2018 15:06:44 +0530 Pirate Praveen wrote:> Adding > X-DhRuby-Root: ruby > > to ruby-google-protobuf binary section in debian/control fixes this. > with the above change, I still get another error LoadError: cannot load such file -- google/protobuf/timestamp_

Bug#900677: ruby-google-protobuf: does not install pure ruby files

On Sun, 3 Jun 2018 14:50:55 +0530 Pirate Praveen wrote: > package: ruby-google-protobuf > version: 3.6.0~rc2-1 > severity: grave > justification: makes package unusable > > When trying to use ruby-google-protobuf, I get this error > > LoadError: cannot load such

Bug#900677: ruby-google-protobuf: does not install pure ruby files

package: ruby-google-protobuf version: 3.6.0~rc2-1 severity: grave justification: makes package unusable When trying to use ruby-google-protobuf, I get this error LoadError: cannot load such file -- google/protobuf if you compare with previous versions of ruby-google-protobuf (

Bug#900615: osmosis FTBFS Could not resolve all dependencies for configuration ':osmosis-hstore-jdbc:compileClasspath'

package: osmosis version: 0.46-3 severity: serious While building with protobuf 3.5.2 from experimental, this build failed, but I think this is unrelated to protobuf change. FAILURE: Build failed with an exception. * What went wrong: Could not resolve all dependencies for configuration

Bug#876707: fixed in golang-gopkg-libgit2-git2go.v26 0.26+git20170903.0.eb0bf21-1

On Sat, 03 Mar 2018 21:00:13 + Maximiliano Curia wrote:> We believe that the bug you reported is fixed in the latest version of golang-gopkg-libgit2-git2go.v26, which is due to be installed in the Debian FTP archive. I think golang-git2go package should be removed from

Bug#898228: ruby-gitaly: Required dependency not specified on deb package

On Wed, 09 May 2018 10:39:31 +0530 Pirate Praveen <prav...@onenetbeyond.org> wrote:> I'm aware of this issue and ruby-grpc 1.11 is ready for upload. I'm waiting for libgrpc6 to clear NEW. It also needs ruby-rugged >= 0.27 which needs libgit2 0.27 in NEW. signature.asc Descript

Bug#898228: ruby-gitaly: Required dependency not specified on deb package

Control: tag -1 pending On May 9, 2018 4:06:28 AM GMT+05:30, David L wrote: >Gitaly gem requires grpc gem in version 1.10 to work, but, deb package >doesn't force installation of this package. >In that case, ruby-gitaly is unusable. > >Error message: > >Bundler could not

Bug#892656: even more tests fail with version 2.0.2

On April 12, 2018 2:48:32 AM GMT+05:30, Paolo Greppi wrote: >Normally you'd expect to fix bugs with a new version, in this case >while trying to update node-define-property 1.0.0-1 -> 2.0.2 the >failing tests actually increased from 1 to 4. > >What puzzled me was that

Bug#894277: gitaly is not configured and not starting with a custom configuration

Package: gitaly Version: 0.91.0+debian-1 Severity: grave Control: forwarded -1 https://gitlab.com/gitlab-org/gitaly/issues/1119 Control: affects -1 gitlab This breaks gitlab. signature.asc Description: OpenPGP digital signature

Bug#894138: gitlab: 10.5.6 Problem compiling assets on post-install

Control: severity -1 important Reducing severity because it appears a local setup issue. On ചൊവ്വ 27 മാർച്ച് 2018 06:33 വൈകു, David López Zajara (Er_Maqui) wrote: > @praveen > > I leave you here the "mostly" complete debug of a uninstall - purge - > reinstall of 10.5.6 ve

Bug#894138: gitlab: 10.5.6 Problem compiling assets on post-install

On തിങ്കള്‍ 26 മാർച്ച് 2018 11:01 വൈകു, David L wrote: > > Installing gitlab 10.5.6 do not work because a problem on sprockets. > > This error is also on old 10.5.5 and 9.5.4 versions. Is this a problem in a purge - reinstall as well or only when updating from 9.5? I was able to install

Bug#894072: gitlab: postinst fails with "/var/lib/gitlab/yarn/node_modules/.bin/yarn: not found"

Control: severity -1 important On തിങ്കള്‍ 26 മാർച്ച് 2018 08:52 വൈകു, David López Zajara (Er_Maqui) wrote: > This are referenced at this bug: #893867 > > @Praveen: > > This bug appears from uploading from 9.5.4 installation. If you do a > purge && reinstall, it solves t

Bug#894072: gitlab: postinst fails with "/var/lib/gitlab/yarn/node_modules/.bin/yarn: not found"

On Mon, 26 Mar 2018 17:29:58 +1100 Dmitry Smirnov wrote:> Installation of GitLab failed in postinst as follows: > > > Installing node modules... > npm WARN package.json compression-webpack-plugin@0.3.2 No license field. > npm WARN package.json dropzone@4.3.0 No license

Bug#893867: Bug #893867 in gitlab marked as pending

Control: tag -1 pending Hello, Bug #893867 in gitlab reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#860939: node-diffie-hellman: Please clarify security concerns

On Sun, 23 Apr 2017 14:58:58 +0200 roucaries bastien wrote: > control: forwarded -1 > https://github.com/crypto-browserify/diffie-hellman/issues/22 Since there is no progress on this upstream, I think removing dh support is the way to go. Since this

Bug#882476: gitaly FTBFS: repo.go:11:9: repo.GetPath undefined (type *gitaly.Repository has no field or method GetPath)

I'm trying to update it to latest upstream release, repo here https://anonscm.debian.org/cgit/pkg-go/packages/gitaly.git But getting this error. # gitlab.com/gitlab-org/gitaly/internal/rubyserver src/gitlab.com/gitlab-org/gitaly/internal/rubyserver/rubyserver.go:144:34: cannot use conn (type

Bug#891209: ruby-github-api: Depends: ruby-faraday (< 0.10) but 0.13.1-2 is to be installed

On Fri, 23 Feb 2018 14:05:36 +0200 Adrian Bunk wrote:> The following packages have unmet dependencies: > ruby-github-api : Depends: ruby-faraday (< 0.10) but 0.13.1-2 is to be > installed This is blocking testing migration of ruby-faraday. There is a new upstream release which

Bug#892798: ruby-crack FTBFS uninitialized constant SafeYAML::Parse::Date::DateTime (NameError)

Package: ruby-crack version: 0.4.3-2 Severity: serious Autopkgtest also fails https://ci.debian.net/data/packages/unstable/amd64/r/ruby-crack/latest-autopkgtest/log.gz ┌──┐ │ Run tests for ruby2.5 from

Bug#892133: [Pkg-javascript-devel] Bug#892133: Bug#892133: node-rollup: does not work after a no-change rebuild (the one in the archive is not suitable for main?)

On Tue, 6 Mar 2018 18:18:05 +0530 Pirate Praveen <prav...@onenetbeyond.org> wrote: > On ചൊവ്വ 06 മാർച്ച് 2018 04:17 വൈകു, Gianfranco Costamagna wrote: > > Hello, > > I can reproduce with both Debian and Ubuntu, with clean environments in > > both cases. > > (

Bug#892742: rollup FTBFS with node-rollup-plugin-commonjs 9.0

Package: src:node-rollup Version: 0.50.0-1 Severity: serious dh_auto_build echo 0.50.0-1 > .commithash \ && rollup -c src/node-entry.js → dist/rollup.js, dist/rollup.es.js... [!] (commonjs plugin) TypeError: parse is not a function in /<>/src/node-entry.js src/node-entry.js TypeError: parse is

Bug#888508: gitlab: multiple CVEs from GitLab Security Release: 10.3.4, 10.2.6, and 10.1.6 advisory

On ശനി 10 മാർച്ച് 2018 11:25 വൈകു, Pirate Praveen wrote: > I will attach a debdiff tomorrow with the CVEs we already backported. debdiff attached. diff -Nru gitlab-8.13.11+dfsg/debian/changelog gitlab-8.13.11+dfsg/debian/changelog --- gitlab-8.13.11+dfsg/debian/changelog2017-03-23 17

Bug#888508: gitlab: multiple CVEs from GitLab Security Release: 10.3.4, 10.2.6, and 10.1.6 advisory

On Mon, 5 Mar 2018 17:18:00 +0530 Pirate Praveen <prav...@debian.org> wrote: > On ഞായര്‍ 04 മാർച്ച് 2018 10:29 വൈകു, Moritz Mühlenhoff wrote: > > We're now almost two months in after the upstream security > > release. If this still isn't ready, that's a sign to me > &

Bug#892133: [Pkg-javascript-devel] Bug#892133: Bug#892133: node-rollup: does not work after a no-change rebuild (the one in the archive is not suitable for main?)

tags -1 confirmed On ചൊവ്വ 06 മാർച്ച് 2018 04:17 വൈകു, Gianfranco Costamagna wrote: > Hello, > I can reproduce with both Debian and Ubuntu, with clean environments in both > cases. > (I use pbuilder clean environments) I could not reproduce it using sbuild and then sbuild --extra-package

Bug#892133: [Pkg-javascript-devel] Bug#892133: node-rollup: does not work after a no-change rebuild (the one in the archive is not suitable for main?)

On March 6, 2018 3:54:36 AM GMT+05:30, Gianfranco Costamagna wrote: >Package: node-rollup >Version: 0.50.0-1 >Severity: serious > > >Hello, seems that a simple no-change rebuild of the package, makes the >program stop working completely with this error: > >just no

Bug#888508: gitlab: multiple CVEs from GitLab Security Release: 10.3.4, 10.2.6, and 10.1.6 advisory

On ഞായര്‍ 04 മാർച്ച് 2018 10:29 വൈകു, Moritz Mühlenhoff wrote: > We're now almost two months in after the upstream security > release. If this still isn't ready, that's a sign to me > that we can' reasonably support it, so the next best option > is to end-of-life it and eventually ask for it's

Bug#892018: [Pkg-javascript-devel] Bug#892018: Won't work without grunt!

Control: severity -1 normal On ഞായര്‍ 04 മാർച്ച് 2018 01:57 വൈകു, Julien Puydt wrote: > It is really depending on grunt -- but doesn't, so it's possible to > install the package in a broken state. I think that is expected. node-grunt-cli is a dependency of grunt (not the other way around). I

Bug#887586: node-chokidar: build hangs with mocha 4.0.1-3

Control: affects -1 -src:node-webpack On Sun, 4 Feb 2018 17:32:36 +0200 Adrian Bunk wrote:> This is actually an issue that seems to affect more build-rdeps of mocha > (build logs are in the reproducible builds of the affected packages). test/Compiler.test.js was hanging in case

Bug#891724: gitlab: Use libjs-uglify from sid

On വ്യാഴം 01 മാർച്ച് 2018 07:54 വൈകു, Viktar Vauchkevich wrote: > Use libjs-uglify 2.8.29-3 from sid instead of 3.3.10-1 from experimental > Thanks a lot. I did try downgrading node-uglify but it did not occur to me libjs-uglify was used. signature.asc Description: OpenPGP digital signature

Bug#891724: rake assets:precompile fails with 'ExecJS::ProgramError: TypeError: UglifyJS.Compressor is not a function'

Package: gitlab Version: 9.5.4+dfsg-6 Severity: grave Control: tag -1 help gitlab currently fails to install, it was working earlier so the issue was likely introduced by a regression in one of the dependencies. But so far I'm unable to track it down. Precompiling assets... I,

Bug#891630: Missing dep making it unusable

On Tue, 27 Feb 2018 07:18:00 -0700 TheSin wrote: > After upgrading, and trying to bundle gitlab I get > > Could not find gem 'deckar01-task_list (>= 1.0.5, ~> 1.0)' in any of the gem > sources listed in your Gemfile. > > From >

Bug#890391: libjs-jquery-atwho: ReferenceError: Controller is not defined

On Sun, 25 Feb 2018 14:47:19 +1100 Ben Finney wrote: > On 25-Feb-2018, Balasankar C wrote: > > > Note: I have enabled the atwho JS file from cloudflare CDN in it. > > How is that related to the upstream source? These days most browser libraries are developed in a node.js

Bug#890391: libjs-jquery-atwho: ReferenceError: Controller is not defined

On Sun, 25 Feb 2018 15:03:45 +1100 Ben Finney <bign...@debian.org> wrote: > On 15-Feb-2018, Pirate Praveen wrote: > > > wget `npm view at.js dist.tarball` will get you the dist tarball. > > Compare dist/js/jquery.atwho.js in the tarball with the file installed &

Bug#890391: libjs-jquery-atwho: ReferenceError: Controller is not defined

[copying the javascript maintainers list] On Fri, 23 Feb 2018 11:37:31 +1100 Ben Finney wrote: > Control: tags -1 + unreproducible I don't think this really a productive way of collaboration when two people already reproduced this issue. > On 16-Feb-2018, Ben Finney wrote:

Bug#873440: Bug #873440 in ruby-grpc marked as pending

Control: tag -1 pending Hello, Bug #873440 in ruby-grpc reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Bug#889024: This is already fixed in experimental

On Thu, 8 Feb 2018 22:54:16 +0200 Adrian Bunk wrote:> This is already fixed in experimental: > > https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/ruby-hamlit.html Tests are just disabled, not fixed. It should be fixed when uploading to unstable.

Bug#850719: Fixed in last upload

Control: fixed -1 0.50.0-1 It does not use npm anymore to build. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#888508: gitlab: multiple CVEs from GitLab Security Release: 10.3.4, 10.2.6, and 10.1.6 advisory

On വ്യാഴം 15 ഫെബ്രുവരി 2018 12:07 രാവിലെ, Moritz Mühlenhoff wrote: > What's the status? > Cheers, > Moritz Some cve patches are backported, but help is welcome, https://salsa.debian.org/ruby-team/gitlab/tree/master-8-13 https://pad.disroot.org/p/gitlab_security_bp signature.asc

Bug#890391: libjs-jquery-atwho: ReferenceError: Controller is not defined

On വ്യാഴം 15 ഫെബ്രുവരി 2018 01:10 രാവിലെ, Ben Finney wrote: > This bug report (bug#890391) begins with that message, and no > information on the error or steps to reproduce. > > For reference in this bug report, can you please give complete steps > to reproduce with the current Debian package? >

Bug#890391: libjs-jquery-atwho: ReferenceError: Controller is not defined

Package: libjs-jquery-atwho Version: 1.5.3+dfsg.1-1 Severity: grave Justification: makes the package unuseable Control: block 890333 by -1 Originally reported with full error log at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890333 and I was able to reproduce it in my system. gulp is now

Bug#888945: ruby-uglifier FTBFS with node-source-map 0.7

Package: ruby-uglifier Version: 2.7.2+dfsg-2 Severity: serious Control: block 888926 by -1 1) Uglifier should be able to handle an input source map # Needs UglifyJS >= 2.5 to work Failure/Error: @context.call(Uglifier::JS, options) JSON::ParserError: 765: unexpected token

Bug#888944: node-css FTBFS with node-source-map 0.7

Package: node-css Version: 2.1.0-2 Severity: serious Control: block 888926 by -1 108 passing (432ms) 1 failing 1) stringify(obj, {sourcemap: true}) should generate source maps alongside when using identity compiler: TypeError: map.originalPositionFor is not a function at

Bug#888943: node-concat-with-sourcemaps FTBFS with node-source-map 0.7

Package: node-concat-with-sourcemaps Version: 1.0.4-2 Severity: serious Control: block 888926 by -1 # should concatenate content with source maps with "\n" and produce combined source map /<>/index.js:58 upstreamSM.eachMapping(function(mapping) { ^ TypeError:

Bug#888942: node-combine-source-map FTBFS with node-source-map 0.7

Package: node-combine-source-map Version: 0.8.0+ds-4 Severity: serious Control: block 888926 by -1 # should concatenate content with source maps with "\n" and produce combined source map /<>/index.js:58 upstreamSM.eachMapping(function(mapping) { ^ TypeError:

Bug#888846: node-webpack-sources FTBFS with node-source-map 0.7.0+dfsg-1

Package: node-webpack-sources Version: 1.0.1-1 Severity: serious Control: forwarded -1 https://github.com/webpack/webpack-sources/issues/34 Control: tag -1 help With the last upload of node-source-map, node-webpack-sources has 2 tests failing and hence FTBFS. 0.7 has many breaking changes

Bug#886816: Removing golang-go.uber-zap or zap

On 2018, ജനുവരി 29 9:00:58 AM IST, Alexandre Viau wrote: >Hello, > >I have uploaded a duplicate of src:zap as src:golang-go.uber-zap. > >I don't know why I missed src:zap. Probably because it didn't follow >the >pkg-go naming guidelines, but even then, dh-make-golang should

Bug#888508: gitlab: multiple CVEs from GitLab Security Release: 10.3.4, 10.2.6, and 10.1.6 advisory

On വെള്ളി 26 ജനുവരി 2018 07:32 വൈകു, Salvatore Bonaccorso wrote: > See > https://about.gitlab.com/2018/01/16/gitlab-10-dot-3-dot-4-released/ > for which several go back to 8.9.0 versions. > > There are three CVEs out of > https://security-tracker.debian.org/tracker/source-package/gitlab >

Bug#887583: [Pkg-javascript-devel] Bug#887583: Bug#887583: libjs-fetch FTBFS with mocha 4.0.1-3

On ഞായര്‍ 21 ജനുവരി 2018 11:08 വൈകു, Pirate Praveen wrote: > My logs were from before mocha 4 is uploaded to unstable. Now we need to fix > the tests for mocha 4 (this bug), as well as chai 4 (the other bug I > reported). > mocha.{css,js,min.js} files were missing from mocha bi

Bug#887583: [Pkg-javascript-devel] Bug#887583: libjs-fetch FTBFS with mocha 4.0.1-3

On 2018, ജനുവരി 21 10:19:24 PM IST, Ghislain Vaillant <ghisv...@gmail.com> wrote: >cc'd to Pirate Praveen who reported a similar issue for a version on >experimental? > >Do you have an idea what's going on? Why is Adrian's log different to >yours? > My logs were from be

Bug#887069: node-node-uuid installs a broken link and making dependencies like npm broken

package: node-node-uuid version: 1.4.7-1 severity: grave it also breaks packages that depend on it like npm. node -e "require('node-uuid');" module.js:538 throw err; ^ Error: Cannot find module 'node-uuid' at Function.Module._resolveFilename (module.js:536:15) at

Bug#874420: [Pkg-javascript-devel] Bug#874420: poking the bugs to delay autorm

On 2017, ഡിസംബർ 22 12:52:05 AM IST, Mattia Rizzolo wrote: >[08:18:54 PM] if it migrates by then, the issues should be >fixed >[08:20:03 PM] ivodd: ack, will do that. This is blocked by nodejs >= 6 not migrating to testing (one of node-babel dependencies, node-regexpu-core

Bug#884913: [Pkg-javascript-devel] Bug#884913: node-gulp-babel: fails immediately because of undeclared dependency “babel-core”

Control: severity -1 normal On 2017, ഡിസംബർ 21 3:28:29 PM IST, Ben Finney wrote: >Package: node-gulp-babel >Version: 7.0.0-2 >Severity: serious >Justification: Policy 3.5 > >Attempting to run a Gulp build that uses ‘gulp-babel’ fails >immediately: > >= >module.js:327

Bug#872305: marked as pending

494820c925706ed82b3948b2dd7c4224f94f627b Author: Pirate Praveen <prav...@debian.org> Date: Mon Dec 11 20:32:53 2017 +0530 update changelog diff --git a/debian/changelog b/debian/changelog index 0579627..7221f15 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,14 @@ -diaspora (0.6.0.1+de

Bug#866877: marked as pending

494820c925706ed82b3948b2dd7c4224f94f627b Author: Pirate Praveen <prav...@debian.org> Date: Mon Dec 11 20:32:53 2017 +0530 update changelog diff --git a/debian/changelog b/debian/changelog index 0579627..7221f15 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,8 +1,14 @@ -diaspora (0.6.0.1+de

Bug#883409: webpack: depends on non-existing package node-uglifyjs-webpack-plugin

On Sun, 03 Dec 2017 17:44:20 +0100 Jonas Smedegaard wrote: > The binary package webpack depends on non-existing package > node-uglifyjs-webpack-plugin, making the former impossible to install. Both webpack and node-uglifyjs-webpack-plugin was in NEW, but webpack was accepted

Bug#880290: node-grunt-babel: FTBFS: Test failures

On Mon, 30 Oct 2017 21:09:50 +0100 Lucas Nussbaum wrote:> > Running "babel:compile" (babel) task > > Warning: Couldn't find preset "env" relative to directory "test/fixtures" > > Use --force to continue. I will add node-babel-preset-env to build deps to fix this, but it is

Bug#879923: [!] (commonjs plugin) TypeError: Cannot read property 'parse' of undefined

package: node-rollup-plugin-commonjs version: 8.2.4-1 severity: serious When building rollup using node-rollup-plugin-commonjs, it fails with error (with npm installed rollup-plugin-commonjs, build succeeds). src/node-entry.js → dist/rollup.js, dist/rollup.es.js... [!] (commonjs plugin)

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

On ബുധന്‍ 25 ഒക്ടോബര്‍ 2017 07:08 വൈകു, Pirate Praveen wrote: > I can reach the segfaulting point faster by setting break point at > thread creation > > b pthread_create.c:333 > > after 8 c, I reach the segfault point. > > > hopefully more useful bt (gd

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

I can reach the segfaulting point faster by setting break point at thread creation b pthread_create.c:333 after 8 c, I reach the segfault point. signature.asc Description: OpenPGP digital signature

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

On Mon, 16 Oct 2017 21:06:34 +0530 Pirate Praveen <prav...@onenetbeyond.org> wrote: > On തിങ്കള്‍ 16 ഒക്ടോബര്‍ 2017 08:54 വൈകു, Jérémy Lal wrote: > > > > Can you attach the whole failing sbuild log please ? > >Attached. > > The diff between the current git master

Bug#877314: marked as pending

8956f61ac7bf00f93884c63c4b9e2a1c44744590 Author: Pirate Praveen <prav...@debian.org> Date: Mon Oct 23 13:40:29 2017 +0530 update changelog diff --git a/debian/changelog b/debian/changelog index 8401145..268c0d0 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +ruby-premailer (1

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

On തിങ്കള്‍ 16 ഒക്ടോബര്‍ 2017 07:13 വൈകു, Jérémy Lal wrote: > A memory allocation failure... is it possible you ran out of memory ? Very unlikely, I have 16 GB ram. > Anyway i tried typing the same commands as in debian/rules of node-d3-zoom, > but this time using webpack, babel-cli,

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

On 10/16/2017 04:32 PM, Pirate Praveen wrote: > I'm using libuv1 1.11 (built locally) and still seeing the segfault, I > think more dbgsym packages need to be installed. after zlib1g-dbg installed (gdb) bt #0 0x18df10069fc8 in ?? () #1 0x18df105deecf in ?? () #2 0x00

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

On 10/16/2017 03:21 PM, Jérémy Lal wrote: > > Update: i uploaded libuv1 1.11.0 to experimental. > I strongly suspect the bug you see will be fixed with that version. > > Jérémy I'm using libuv1 1.11 (built locally) and still seeing the segfault, I think more dbgsym packages need to be

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

On 10/16/2017 01:18 PM, Jérémy Lal wrote: > > > 2017-10-16 9:43 GMT+02:00 Pirate Praveen <prav...@onenetbeyond.org > <mailto:prav...@onenetbeyond.org>>: > > On 10/16/2017 12:47 PM, Jérémy Lal wrote: > > You could get a more useful stack trace by inst

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

On 10/16/2017 12:47 PM, Jérémy Lal wrote: > You could get a more useful stack trace by installing nodejs-dbgsym > package from > deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main I have installed it, but the output is still the same, no extra details. signature.asc

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

On 10/16/2017 12:47 PM, Jérémy Lal wrote: > You could get a more useful stack trace by installing nodejs-dbgsym > package from > deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main > > Jérémy I will try that, meanwhile I tried, NODE_PATHocal/lib/node_modules node debug

Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: nodejs segfaults when building d3-* with webpack

On 10/16/2017 10:32 AM, Pirate Praveen wrote: > I don't think any of them is a C++ addon, probably one of their > dependencies. > > > After using segfault-handler node module, I get this message, PID 21070 received SIGSEGV for address: 0x0 /usr/local/lib/node_modules/segfaul

Bug#878674: [Pkg-javascript-devel] Bug#878674: nodejs segfaults when building d3-* with webpack

On ഞായര്‍ 15 ഒക്ടോബര്‍ 2017 11:39 വൈകു, Jérémy Lal wrote: > Do you know if any dependency is a c++ addon ? These are the direct dependencies, Depends: ${misc:Depends} , nodejs , node-acorn (>= 5.0~) , node-acorn-dynamic-import (>= 2.0~) , node-ajv (>= 5.0~) , node-ajv-keywords (>= 2.0~) ,

<    1   2   3   4   5   6   7   8   9   10   >