Bug#815133: gitlab installation fails with LoadError: cannot load such file -- /usr/share/gitlab/config/application

Hi Josch, You'll have to do a fresh install as directory structure has changed significantly. 1. apt-get purge gitlab (removes files, so new version can add symlinks) 2. rm -rf /usr/share/gitlab (config, tmp, log were not empty). 3. userdel -r gitlab (/var/lib/gitlab is new home or .gitconfig

Bug#815133: gitlab installation fails with LoadError: cannot load such file -- /usr/share/gitlab/config/application

On Sat, 20 Feb 2016 22:37:20 +0530 Pirate Praveen <prav...@onenetbeyond.org> wrote: > Hi Josch, > > You'll have to do a fresh install as directory structure has changed > significantly. > > 1. apt-get purge gitlab (removes files, so new version can add symlinks) >

Bug#818073: confirmed: only happens in chroots

control: severity -1 normal Just tested outside chroot and captcha is working. signature.asc Description: OpenPGP digital signature

Bug#818054: eye is failing to load

sudo -E -H -u diaspora bundle exec loader_eye -st -c config/eye.rb ruby2.3: symbol lookup error: /usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sigar-0.7.3/lib/sigar.so: undefined symbol: sigar_skip_token signature.asc Description: OpenPGP digital signature

Bug#818054: diaspora fails to start with ruby2.3: symbol lookup error:...sigar.so: undefined symbol: sigar_skip_token

package: diaspora-installer version: 0.5.6.3+debian1 severity: grave justification: makes package unusable # sudo -H -E -u diaspora ./script/server start Starting Diaspora in production mode with 1 Sidekiq worker(s). ruby2.3: symbol lookup error:

Bug#818073: possibly a chroot issue

same error appears in diaspora-installer too, both running in cowbuilder --login chroots signature.asc Description: OpenPGP digital signature

Bug#818073: captcha not working in sign up

package: diaspora severity: grave justification: makes package unusable production log has this error. [2016-03-13T11:00:13] INFO PID-7890 TID-19665120 ActionController::Base: Completed 200 OK in 615ms (Views: 355.1ms | ActiveRecord: 46.2ms) [2016-03-13T11:00:13] INFO PID-7887 TID-19665120

Bug#820178: reassigning to libre2-1v5

Control: reassign -1 libre2-1v5 Control: found -1 20160401+dfsg-1 Control: notfound -1 20160201+dfsg-1 Control: block -1 by 820349 Control: retitle -1 new upload broke ruby-re2 (in turn broke gitlab) libre2-1v5 upload should have ensured reverse dependencies are not broken during new upload. And

Bug#820349: FTBFS: #error This file requires compiler and library support for the ISO C++ 2011 standard.

package: ruby-re2 severity: serious ┌──┐ │ Build native extensions for ruby2.3 │ └──┘ /usr/bin/ruby2.3

Bug#820184: you will need to remove gitlab user and add it again

Hi Josch, gitlab users home directory is now /var/lib/gitlab. I suspect you have gitlab user created before the move to /var. Can you confirm the home directory of gitlab user? Thanks Praveen signature.asc Description: OpenPGP digital signature

Bug#820178:

Downgrading libre2-1v5 fixes this issue. Some ruby libraries may need a rebuild. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#818733: cryptsetup failes in luksFormat: Failed to open key file

package: cryptsetup severity: grave version: 2:1.6.6-5 # cryptsetup luksFormat /dev/data/diaspora diaspora WARNING! This will overwrite data on /dev/data/diaspora irrevocably. Are you sure? (Type uppercase yes): YES Failed to open key file. # apt-cache policy cryptsetup cryptsetup:

Bug#814645: not in stable yet

Control: severity -1 wishlist On 2016, മാർച്ച് 1 5:19:35 PM IST, Andreas Beckmann wrote: >The test was done upgrading from the previous version in testing to sid >before the current one migrated. >So anyone having that version installed and upgraded will not have had >a

Bug#817011: ruby-domain-name: missing RubyGems integration, breaks other softwares like Vagrant

On Mon, 07 Mar 2016 15:15:38 +0900 =?UTF-8?Q?Marc_Dequ=C3=A8nes_=28duck=29?= wrote: > I'm in the team but I don't have time or tools at the moment to get into > more details why this file is missing (I remember gem2deb to already > have all the necessary magic and this

Bug#832490: gitlab: fails to install if it was previously installed

Control: fixed -1 8.9.0+dfsg-8 On Tue, 26 Jul 2016 10:56:21 +1000 Dmitry Smirnov wrote: > Package: gitlab > Version: 8.9.0+dfsg-7 > Severity: serious > > > Creating runtime directories for gitlab... > mkdir: cannot create directory ‘/var/lib/gitlab/.ssh’: File

Bug#832133: Checklist for uploading new versions

On 07/22/2016 10:41 PM, Lucas Nussbaum wrote: > The failure you quoted is about a strict dependency. Do you know if it's > justified? The changes on ruby-json's side are fairly small. Also it > seems that the strict dependency was dropped from the gemspec (it's not > there anymore in version 1.0.2

Bug#832133: Checklist for uploading new versions

On 07/22/2016 11:50 PM, Pirate Praveen wrote: > I think the solution is to build rails on a system which still has > ruby-json 1.8.3 and upload that version to archive. > I have built rails locally without strict dependency on ruby-json. If someone can confirm its okay to upload, I c

Bug#832133: Checklist for uploading new versions

On 07/22/2016 10:41 PM, Lucas Nussbaum wrote: > Hi, > > yesterday on IRC: > 23:29 < lucas> long time without doing any ruby packaging, let's hope I > didn't break the world > > Looks like I did :/ I guessed :) > The failure you quoted is about a strict dependency. Do you know if it's >

Bug#832133: Checklist for uploading new versions

On 07/22/2016 11:46 PM, Pirate Praveen wrote: > On 07/22/2016 11:22 PM, Pirate Praveen wrote: >> The failure is at: >> ruby-activesupport : Depends: ruby-json (< 2.0) but 2.0.1+dfsg-1 is to >> be installed > > I tried relaxing the requirement in rails package and

Bug#832133: ruby-json 2.0 broke rails: metabug to prevent testing migration

package: ruby-json version: 2.0.1+dfsg-1 severity: grave ruby-json upload just broke rails and a whole lot of dependencies. The following packages have unmet dependencies: ruby-activesupport : Depends: ruby-json (< 2.0) but 2.0.1+dfsg-1 is to be installed One sample failure

Bug#832133: Checklist for uploading new versions

On 07/22/2016 11:22 PM, Pirate Praveen wrote: > The failure is at: > ruby-activesupport : Depends: ruby-json (< 2.0) but 2.0.1+dfsg-1 is to > be installed I tried relaxing the requirement in rails package and build, but it fails to build because of circular dependencies :( s

Bug#832649: multi-display is broken (menu and panel appears only on external display)

package: systemsettings version: 4:5.7.0-1 severity: grave I have connected an HDMI monitor to my laptop and the menu and panel appears on the HDMI monitor, but when I remove the HDMI cable, the menu and panel does not appear on the laptop screen. I have to use run command and alt tab as a

Bug#830987: libjs-handlebars: missing source

On Wed, 13 Jul 2016 15:44:34 +0100 Ansgar Burchardt wrote: > I briefly looked into the package due to the discussion on -devel@ and > the ctte bug.  The source for the javascript code seems to be missing: > it contains generated lexer/parser code, see the upstream source at >

Bug#832133: Checklist for uploading new versions

On 07/23/2016 01:43 AM, Antonio Terceiro wrote: > On Sat, Jul 23, 2016 at 12:12:16AM +0530, Pirate Praveen wrote: >> On 07/22/2016 11:50 PM, Pirate Praveen wrote: >>> I think the solution is to build rails on a system which still has >>> ruby-json 1.8.3 and upl

Bug#834401: sddm cannot set per user desktop choices

package: sddm version: 0.13.0-1 severity: grave I have two users in my system and when using sddm, each user has to select their preferred desktop session **EVERY** single time. One user wants KDE/Plasma and another GNOME. When first users selects GNOME and logout, the second user also gets

Bug#831448: gitlab: fails to install database

Control: severity -1 important On Sat, 16 Jul 2016 08:09:01 + cl...@jhcloos.com wrote: > Package: gitlab > Version: 8.9.0+dfsg-4 > Severity: grave > Justification: renders package unusable > > installing gitlab via apt with LANG=en_US.UTF-8 results in this: > > Create database if not

Bug#830988: Fails to reinstall grub in efi system

package: grub2-common severity: grave Version: 2.02~beta2-22+deb8u1 After installing debian 8.5 jessie, I installed Windows. It removed grub from mbr, so booted into rescue mode using the same cd 1 image, but grub-install failed with this error. grub-install: error

Bug#829254: asset:precompile error when updating diaspora to 0.5.9.1

On Thursday 07 July 2016 01:28 PM, Antonio Terceiro wrote: > On Thu, Jul 07, 2016 at 07:44:00AM +0530, Pirate Praveen wrote: >> >> >> On 2016, ജൂലൈ 7 1:38:54 AM IST, Antonio Terceiro <terce...@debian.org> wrote: >>> This is a very shitty way of making things wo

Bug#829254: asset:precompile error when updating diaspora to 0.5.9.1

On Friday 08 July 2016 08:48 PM, Cédric Boutillier wrote: > On Fri, Jul 08, 2016 at 04:59:17PM +0530, Pirate Praveen wrote: > >> The problem is libjs-handlebars is a node module (it should be changed >> to node-handlebars I think) and handlebars_assets expects a browserified >

Bug#829254: seems the older version is broken too

I thought of using 0.21 as a workaround, but that is also failing with diaspora 0.5.7.1 from experimental. signature.asc Description: OpenPGP digital signature

Bug#829254: asset:precompile error when updating diaspora to 0.5.9.1

[will drop debian-ruby from further updates] On Wednesday 06 July 2016 09:07 PM, Pirate Praveen wrote: > I was able to successfully install 0.5.5.1 in unstable but 0.5.7.1 in > experimental is failing with same error. So it could be either new code > in diaspora or one of the changed dep

Bug#829254: asset:precompile error when updating diaspora to 0.5.9.1

On 2016, ജൂലൈ 7 1:38:54 AM IST, Antonio Terceiro <terce...@debian.org> wrote: >On Wed, Jul 06, 2016 at 11:18:09PM +0530, Pirate Praveen wrote: >> So I replaced ruby-handlebars-assets deb package with >handlebars_assets >> gem and it is also working. > >This is a ve

Bug#829254: asset:precompile error when updating diaspora to 0.5.9.1

On 2016, ജൂലൈ 7 1:38:54 AM IST, Antonio Terceiro wrote: >This is a very shitty way of making things work. So your approach is, >instead of fixing the Debian package, adding an embedded copy of the >upstream sources? No, you are just shouting baseless things that does not

Bug#820073: diaspora-common: modified shipped files: /usr/share/diaspora-common/{database.yml, diaspora.conf}

On Sun, 03 Jul 2016 18:48:36 +0200 Andreas Beckmann wrote: > Followup-For: Bug #820073 > Control: found -1 0.5.9.1+debian1 > > Hi, > > now the problem has shifted to > > 1m24.6s ERROR: FAIL: debsums reports modifications inside the chroot: >

Bug#830680: grape 0.16.2 broke gitlab

package: ruby-grape version: 0.16.2-1 severity: grave Justification: breaks reverse dependencies. See https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/4601 Hopefully, the upstream will come up with a patch soon. signature.asc Description: OpenPGP digital signature

Bug#830111: it is not just gemspec change

Control: forwarded -1 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/4691 Since its a major release, gitlab should be changed as well. Fortunately, upstream is already working on it. signature.asc Description: OpenPGP digital signature

Bug#817092: this browserified

Control: severity -1 wishlist This is not a minified file, only browserified. Though ideally we should browserify it in debian, grunt is still not packaged. Since its still a human readable and modifiable format, I don't think DFSG applies here. When node-grunt is available in the archive, we

Bug#817092: [Pkg-javascript-devel] Bug#817092: this browserified

Control: severity -1 wishlist On Sun, 10 Jul 2016 19:41:17 +0200 Jonas Smedegaard <d...@jones.dk> wrote: > Quoting Pirate Praveen (2016-07-10 18:40:53) > > This is not a minified file, only browserified. Though ideally we > > should browserify it in debian, grunt is still no

Bug#830793: en.yml should be installed in /usr/share

package: ruby-validate-email version: 0.1.6-1 severity: serious ruby-validate-url is in NEW. $ sudo dpkg -i /home/pravi/forge/debian/pbuilder/results/ruby-validate-url_1.0.2-1_all.deb Selecting previously unselected package ruby-validate-url. (Reading database ... 338427 files and directories

Bug#832213: No such file or directory @ rb_sysopen - lib/VERSION

package: ruby-swd version: 1.0.1-1 severity: serious adt-run [17:23:01]: test command1: gem2deb-test-runner --autopkgtest --check-dependencies 2>&1 adt-run [17:23:01]: test command1: [--- ┌──┐ │

Bug#832184: test failure log

┌──┐ │ Checking Rubygems dependency resolution on ruby2.3 │ └──┘ GEM_PATH= ruby2.3 -e gem\ \"gelf\"

Bug#832172: test failure log

Two tests are failing with ruby-json 2.0.1+dfsg-1 in the archive. Full log attached. === Failure: test_parse_malformed(TestConfig) /usr/share/pcsd/test/test_config.rb:125:in `test_parse_malformed' 122: ] 123:

Bug#853131: override_dh_fixperms not working

On തിങ്കള്‍ 30 ജനുവരി 2017 06:10 വൈകു, Jérémy Lal wrote: > Sorry I forgot about that. Lintian should tell us about those things... > Anyway i just rebuilt node-browserify-lite from vcs and lintian > doesn't complain, and > /usr/lib/nodejs/browserify-lite/cli.js has +x correctly set. > > What's

Bug#853131: override_dh_fixperms not working

I tried fixing it like #845745 (updated in git) but it seems to be not working even though permission is changed in debian/node-browserify-lite/usr/lib/nodejs/browserify-lite/cli.js, it get stripped when deb file is generated. signature.asc Description: OpenPGP digital signature

Bug#853131: override_dh_fixperms not working

On തിങ്കള്‍ 30 ജനുവരി 2017 03:08 വൈകു, Jérémy Lal wrote: > Try like > https://anonscm.debian.org/cgit/pkg-javascript/node-tap.git/commit/?id=ef02a554da492283f8ba363ba7297a4d7d938c9f > > ? But doesn't it make it non-reproduceable? as per #845745 signature.asc Description: OpenPGP digital

Bug#704303: violates Debian Policy 2.3 Copyright considerations

On Sun, 19 Feb 2017 12:43:30 +0530 Pirate Praveen <prav...@debian.org> wrote: > On Sun, 1 Jan 2017 16:55:52 +0500 Andrey Rahmatullin <w...@debian.org> > wrote: > > Note that since Policy 3.9.9 MPL should be in common-licenses. > > Reassigning to firefox, which

Bug#704303: violates Debian Policy 2.3 Copyright considerations

Control: reassign -1 firefox, firefox-esr On Sun, 1 Jan 2017 16:55:52 +0500 Andrey Rahmatullin wrote: > Note that since Policy 3.9.9 MPL should be in common-licenses. Reassigning to firefox, which also has the same issue. When is Policy 3.9.9 expected to be released, would it

Bug#772795: grub installation fails on a fakeraid/sataraid/dmraid system

Niels Thykier wrote: > On Sun, 16 Aug 2015 08:45:37 +0200 Felix Zielcke <fziel...@z-51.de> wrote:>> > Am Donnerstag, den 11.12.2014, 12:49 +0530 schrieb Pirate Praveen:>>> > package: grub-pc >>> version: 1.99-27+deb7u2 >>> severity: critical

Bug#856036: screen sharing is not working and vino is segfaulting when started manually

package: vino version: 3.22.0-1 severity: grave justification: makes the package unuseable I'm not able to share desktop using vino (5900 socket is not open) and when I manually start vino-server I get segmentation fault Here is a backtrace from gdb. pravi@nishumbha:~$ gdb

Bug#832649: multi-display is broken (menu and panel appears only on external display)

On 2017, ഫെബ്രുവരി 26 3:40:00 PM IST, Niels Thykier wrote: >Hi Pirate, > >Did you have a chance to test whether this bug still persists? Sorry I won't be able to confirm it as I'm traveling and also I switched to gnome. >Thanks, >~Niels -- Sent from my Android device

Bug#836437: FTBFS: Could not find 'gemojione' (>= 2.2.1, ~> 2.2) - did find: [gemojione-3.1.0]

package: ruby-gitlab-emoji version: 0.3.1-2 severity: serious gitlab 8.10.5 now depends on ruby-gemojione directly. Once gitlab 8.10.5 enters testing, ruby-gitlab-emoji can be removed. GEM_PATH= ruby2.3 -e gem\ \"gitlab_emoji\" /usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could

Bug#832649: multi-display is broken (menu and panel appears only on external display)

On 09/06/2016 12:06 PM, Maximiliano Curia wrote: > This should be handled by kscreen, so I'm reassigning the issue. I can't > reproduce the issue here (with an Intel HD Graphics 3000), I'm not sure > if this is somehow fixed in 5.7.4 or it was caused by something external > (hardware or

Bug#835078: this is a trivial test failure

Control: severity -1 important This is caused by graphicsmagick version in debian being strange. This test is disabled in last upload. signature.asc Description: OpenPGP digital signature

Bug#835749: This package can be removed

This was packaged as a dependency for gitlab and recent versions of gitlab does not need it any more (it was removed from Gemfile, but debian/control was not updated). There are no other reverse dependencies, so this can be removed, once I upload a new version of gitlab which does not depend on

Bug#837644: ruby-devise-async is not compatible with devise >= 4.0

package: ruby-devise-async version: 0.9.0-1 severity: serious This was introduced as a dependency for gitlab, but gitlab does not depend on it anymore (removed from Gemfile). We can safely remove the dependency in gitlab's debian/control. Once that version enters testing, we can remove

Bug#840170: some modules has package.yaml instead of package.json

package: npm2deb version: 0.2.5-1 severity: grave justification: breaks package build So npm2deb should use the correct file in debian/install dh_install: Cannot find (any matches for) "package.json" (tried in "." and "debian/tmp") dh_install: node-jju missing files: package.json dh_install:

Bug#839598: unable to build gitlab-workhorse with gccgo-6

Control: severity -1 important The original build failure is solved by removing vendor and using system libs. On Wed, 5 Oct 2016 09:12:54 +0200 Emilio Pozuelo Monfort wrote: > Is gcc-6_6.1.1-11 (the one in testing) affected by this? It seems so from the upstream bug

Bug#840170: some modules has package.yaml instead of package.json

On ഞായര്‍ 09 ഒക്ടോബര്‍ 2016 04:43 വൈകു, Chris Lamb wrote: > Hi, > >> some modules has package.yaml instead of package.json > > Could you provide an existing package name and/or simple testcase for this? > node-jju package has package.yaml. Similarly colors.js does not have a package.json

Bug#840207: dependency formats are not converted

package: npm2deb version: 0.2.5-1 severity: grave justification: it breaks build ^1.1.0 and similar should be converted to debian format like >= 1.1.0 dpkg-gencontrol: warning: can't parse dependency node-jju (^1.1.0) dpkg-gencontrol: error: error occurred while parsing Depends field: , nodejs

Bug#840170: some modules has package.yaml instead of package.json

On ഞായര്‍ 09 ഒക്ടോബര്‍ 2016 05:59 വൈകു, Chris Lamb wrote: > Pirate Praveen wrote: > >> node-jju package has package.yaml. > > Can't seem to find this package in the archive! This was accepted only a few hours back. See https://anonscm.debian.org/cgit/pkg-javas

Bug#838216: Could not find 'chef-zero' (~> 4.5) - did find: [chef-zero-5.0.0] (Gem::LoadError)

package: chef,chef-zero version: 12.10.24-1 severity: serious Update of chef-zero without testing reverse dependency compatibility caused the issue. adt-run [18:55:42]: test command1: gem2deb-test-runner --check-dependencies --autopkgtest adt-run [18:55:42]: test command1:

Bug#835661: drop dependency on libjs-handlebars

package: prometheus version: 1.0.1+ds-1 severity: serious libjs-handlebars is missing source (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830986 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830978). I'm planning to drop this package (other option is to keep in non-free) soon.

Bug#834843: ruby-doorkeeper: CVE-2016-6582

On Thu, 25 Aug 2016 21:44:23 +0200 Salvatore Bonaccorso wrote: > Control: fixed -1 4.2.0-1 > Hi > > This seems to have been addressed in 4.2.0 upstream (which was > uploaded to experimental), but the debian/changelog does not mention > the bug closer nor the CVE id; any reason

Bug#835661: [pkg-go] Bug#835661: drop dependency on libjs-handlebars

On 2016, ആഗസ്റ്റ് 29 8:40:00 AM IST, "Martín Ferrari" <tin...@debian.org> wrote: >Hi, > >On 28/08/16 08:33, Pirate Praveen wrote: > >> libjs-handlebars is missing source (see >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830986 and >> htt

Bug#839598: unable to build gitlab-workhorse with gccgo-6

package: gccgo-6 version: 6.2.0-5 severity: serious justification: this is causing ftbfs on powrpc src/gitlab.com/gitlab-org/gitlab-workhorse/vendor/github.com/getsentry/raven-go/client.go:25:30: error: import file 'github.com/certifi/gocertifi' not found "github.com/certifi/gocertifi"

Bug#840170: some modules has package.yaml instead of package.json

On Sat, 29 Oct 2016 13:13:51 + shana...@disroot.org wrote: > All npm modules should have a package.json. > > The issue is npm2deb retrieves module source from git repo instead of npm > registry. > > This will be fixed with #842465 >

Bug#841617: gitlab-workhorse: FTBFS: src/gitlab.com/gitlab-org/gitlab-workhorse/internal/api/api.go:136: undefined: jwt.NewWithClaims

Control: tags -1 pending On Fri, 21 Oct 2016 15:46:23 +0200 Lucas Nussbaum wrote: > > src/gitlab.com/gitlab-org/gitlab-workhorse/internal/api/api.go:136: > > undefined: jwt.NewWithClaims > > src/gitlab.com/gitlab-org/gitlab-workhorse/internal/api/api.go:136: > > undefined:

Bug#841543: help needed to fix ruby-carrierware FTBFS

With the recent upload of mysql-server 5.7, mysql_install_db is deprecated, we are supposed to use mysqld --initialize. I tried replacing mysql_init_db with /usr/sbin/mysqld --initialize, but the options are not a one to one map. Can anyone help with this? signature.asc Description: OpenPGP

Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)

On Sun, 4 Sep 2016 13:35:32 +0200 (CEST) Santiago Vila wrote: All failures have this in common, are you sure other tests (from other packages) are not using the same port at the same time? Errno::EADDRINUSE: Address already in use - bind(2) for "127.0.0.1" port 12345

Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)

On 2016, നവംബർ 9 10:22:53 PM IST, Santiago Vila wrote: >I don't think so, because I always build a package at a time. Can you try to reproduce it in another setup? May be sbuild on local system.

Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)

Control: forwarded -1 https://github.com/celluloid/celluloid-io/issues/180 On Wed, 9 Nov 2016 23:56:59 +0100 (CET) Santiago Vila wrote: > I tried building this package a lot of times today to be sure. > It failed 14 times out of 50, so it fails approximately of 28% the time.

Bug#842607: ruby-fog-rackspace: FTBFS (undefined method `flavors')

Control: forwarded -1 https://github.com/fog/fog-rackspace/issues/18 On Sun, 30 Oct 2016 19:47:14 +0100 (CET) Santiago Vila wrote: # Fog::Rackspace::DNS | zone (rackspace) > > Fog::Rackspace::Networking | virtual_interface (rackspace) > undefined method `flavors' for

Bug#841286: jison depends on contrib packages (node-ebnf-parser, node-cjson)

On Wed, 19 Oct 2016 12:56:08 +0200 Jakub Wilk wrote: > This package is in main, but it depends on node-ebnf-parser and node-cjson, > which are both in contrib. These were uploaded in contrib because they were built using jison from npm (bootstrapping circular dependency). Now

Bug#840760: node-livescript: FTBFS (npm: Command not found)

Control: -1 tags pending On Fri, 14 Oct 2016 14:10:01 + Santiago Vila wrote: > npm install jison > make[1]: npm: Command not found jison is just uploaded to debian, so npm is no longer required. Once it clears NEW, I'll upload a fixed version that uses jison package via

Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

Control: -1 tags pending On Friday 14 October 2016 07:29 PM, Aaron M. Ucko wrote: > Automatic builds of node-lex-parser all failed with either > > npm ERR! Error: Attempt to unlock jison@0.4.x, which hasn't been locked > npm ERR! at unlock (/usr/share/npm/lib/utils/locker.js:44:11) >

Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

On വെള്ളി 14 ഒക്ടോബര്‍ 2016 07:29 വൈകു, Aaron M. Ucko wrote: > depending on the architecture. For whatever reason, the problem was with > jison@0.4.x on arm64, armhf, mips, powerpc, ppc64el, s390x, and the > non-release architecture kfreebsd-amd64, and test@* on i386, mips64el, > mipsel, and the

Bug#842023: update jsdom to a version that does not require contextify

package: node-jsdom version: 0.8.10+dfsg1-1 severity: serious Justification: depends on a package that is planned to be removed Control: block 842022 by -1 contextify has rc bugs and is going to be removed. It is required for node < 0.12 only. jsdom should be updated to a version that does not

Bug#808517: ruby-rails-autolink: FTBFS: uninitialized constant ActionDispatch::Assertions::DomAssertions (NameError)

On Sun, 20 Dec 2015 15:29:18 + "Chris West (Faux)" wrote: > > Dear Maintainer, > > The package fails to build: This was packaged as a dependency of diaspora, but it no longer depends on it. I have uploaded a new version of diaspora which does not declare a

Bug#845379: [Pkg-javascript-devel] Bug#845379: node-fuzzaldrin-plus: FTBFS: Npm module "grunt-contrib-coffee" not found.

Control: tags -1 pending On Wednesday 23 November 2016 03:04 AM, Chris Lamb wrote: > Warning: Task "coffee" not found. Use --force to continue. missed builddeps on node-grunt-contrib-coffee. Fixed. But node-grunt-contrib-coffee needs to clear NEW. signature.asc Description:

Bug#845169: ruby-carrierwave: FTBFS in testing (unknown option '--initialize-insecure')

On Mon, 21 Nov 2016 00:42:58 + Santiago Vila wrote: > Maybe some build-depends needs to be versioned? It was building fine with mysql-5.7 in unstable, this version is not yet migrated to testing. I think I will disable the tests until mysql-5.7 can enter testing. These

Bug#846076: node-cross-spawn-async dependencies are too strict

age Subject: Re: [Pkg-javascript-devel] node-lru-cache_4.0.2-1_amd64.changes ACCEPTED into unstable Date: Mon, 28 Nov 2016 11:18:00 +0100 From: Jérémy Lal <kapo...@melix.org> To: Pirate Praveen <prav...@onenetbeyond.org> CC: Debian Javascript Maintainers <pkg-javascript-de...@lists

Bug#844905: node-nan: FTBFS: Tests failures

On Sat, 19 Nov 2016 08:02:29 +0100 Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. From upstream discussion, "The bug is that the Global destructor runs at process exit and tries to free the object slot but that

Bug#839333: ruby-prof: FTBFS: ERROR: Test "ruby2.3" failed.

On Sat, 1 Oct 2016 10:41:49 +0200 Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. I'm unable to reproduce it on a clean chroot, tests went fine during build with sbuild and during autopkgtest. signature.asc

Bug#840170: some modules has package.yaml instead of package.json

Control: severity -1 important On Sun, 9 Oct 2016 11:32:47 +0530 Pirate Praveen <prav...@debian.org> wrote: > severity: grave > justification: breaks package build reducing severity to important, this does not have to block the release as it happens only in a few packages and whic

Bug#840664: ruby-faker: FTBFS randomly (failing tests)

On Mon, 31 Oct 2016 13:06:09 +0100 (CET) Santiago Vila wrote: what's wrong while trying. > > Stupid question: Should this really be [^.].+\. or maybe [^.]+\. ? I'm not good with ruby either, ccing Balu. Also asking upstream for help https://github.com/stympy/faker/issues/737

Bug#840664: ruby-faker: FTBFS randomly (failing tests)

Control: tags -1 pending On Thu, 13 Oct 2016 18:08:12 +0200 (CEST) Santiago Vila wrote: > At least the following tests seem to be wrongly designed: > > => 14: assert Faker::Internet.email.match(/.+@[^.].+\.\w+/) I don't see a reason for this to fail randomly. > => 70:

Bug#840207: dependency formats are not converted

Control: severity -1 important On Sun, 9 Oct 2016 20:36:06 +0530 Pirate Praveen <prav...@debian.org> wrote: > severity: grave > justification: it breaks build Only affects newly created packages signature.asc Description: OpenPGP digital signature

Bug#843148: gitlab-workhorse failing to build on s390x

package: gitlab-workhorse severity: serious version: 0.8.5+debian-2 It fails weirdly without much useful error message than this, dh_auto_build -a -O--buildsystem=golang -O--builddirectory=_build go install -v -p 1 dh_auto_build: go install -v -p 1 died with signal 4 debian/rules:9:

Bug#843148: [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

Bug#843148: its working on s390x porterbox

on zelenka.debian.org, dpkg-buildpackage on a sid chroot is building fine dh_auto_install -O--buildsystem=golang -O--builddirectory=_build mkdir -p /home/praveen/gitlab-workhorse-0.8.5\+debian/debian/gitlab-work horse/usr cp -r bin

Bug#840207: dependency formats are not converted

On Sun, 9 Oct 2016 20:36:06 +0530 Pirate Praveen <prav...@debian.org> wrote: > ^1.1.0 and similar should be converted to debian format like >= 1.1.0 node-formatio uses >= 1.x for samsam dependency, it should be converted to 1.0 signature.asc Description: OpenPGP digital signature

Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

On Sun, 16 Oct 2016 00:20:31 -0400 u...@debian.org (Aaron M. Ucko) wrote: > Is there some reason node-lex-parser has an Architecture value of any > rather than all? Its contents all appear to be architecture-independent > at first glance. Because it was created by dh-make as npm2deb was crashing

Bug#847353: [Pkg-javascript-devel] help with node-grunt-contrib-requirejs

[adding debian-ruby and #847353] On വ്യാഴം 08 ഡിസംബര്‍ 2016 10:34 രാവിലെ, Pirate Praveen wrote: > I think you are only checking for jquery-ui.js and not all the other files > like jquery-ui/widgets/datepicker.js > > I did not see any error in gitlab when using the embedded copy

Bug#847789: [Pkg-javascript-devel] Bug#847789: On the new problem

On 2016, ഡിസംബർ 13 7:13:24 PM IST, Julien Puydt wrote: >Hi, > >I found the time to compile the deps to check for myself, as it would >be >easier than having you report issues one by one, but I'm stuck with >node-glob-stream, which build-depends on node-extend (>=

Bug#846961: [Pkg-javascript-devel] Bug#846961: recent update of libjs-jquery-ui broke gitlab

On 2016, ഡിസംബർ 6 3:16:09 PM IST, Andrew Lee wrote: >I am packaging a complax package called Open Build Service. I also got >hitted by this. Seems a simple fix https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7964/diffs You need to patch application.js to use new

Bug#846961: [Pkg-javascript-devel] Bug#846961: Bug#846961: recent update of libjs-jquery-ui broke gitlab

On 2016, ഡിസംബർ 7 1:11:14 AM IST, Paul Gevers wrote: >To be honest, I don't have a clue what ruby-jquery-ui-rails is doing >(never heard of the package before), so I can't answer that question >yet. One thing, the latest version of upstream ruby-jquery-ui-rails is >also

Bug#847353: [Pkg-javascript-devel] Bug#846961: recent update of libjs-jquery-ui broke gitlab

On Wed, 7 Dec 2016 17:12:12 +0530 Pirate Praveen <prav...@debian.org> wrote: > I tested the patch, but that was not enough., I still get the same error :( I tested using embedded copy of jquery-ui in ruby-jquery-ui-rails and it is working. So it is not an upstream issue, but debian speci

Bug#847353: [Pkg-javascript-devel] Bug#846961: recent update of libjs-jquery-ui broke gitlab

Control: forwarded -1 https://bugs.jqueryui.com/ticket/15112 On Wed, 7 Dec 2016 19:24:10 +0530 Pirate Praveen <prav...@debian.org> wrote: > Though when I tried using grunt, I got this error, > > jqueryui$ grunt > Loading "Gruntfile.js" tasks...ERROR > &

Bug#846961: [Pkg-javascript-devel] Bug#846961: recent update of libjs-jquery-ui broke gitlab

On Wed, 07 Dec 2016 08:22:15 +0530 Pirate Praveen <prav...@onenetbeyond.org> wrote: > Seems a simple fix > https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7964/diffs > > You need to patch application.js to use new paths. I will update > ruby-jquery-ui-rails to 6.0.1

Bug#847789: [Pkg-javascript-devel] Bug#847789: Possible fix

On തിങ്കള്‍ 12 ഡിസംബര്‍ 2016 03:22 വൈകു, Julien Puydt wrote: > Hi, > > can you check the attached patch fixes the bug? I couldn't test it > properly since several of node-vinyl-fs build-deps are not available in > Debian yet and I'm a bit short on time this morning for a compilation > spree. The

<    1   2   3   4   5   6   7   8   9   >