Bug#847830: unblock: diaspora/0.6.0.0+debian-7

[Pirate Praveen]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package diaspora.  Fixes grave functionality bugs (breaks
user interface, core functionality. All buttons and drop downs broken,
cannot post anything.) #846916

It is also affected by breaking changes in
libjs-jquery-ui/ruby-jquery-ui-rails, as described in  #846961

debdiff attached

unblock diaspora/0.6.0.0+debian-7

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ml_IN.UTF-8, LC_CTYPE=ml_IN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru diaspora-0.6.0.0+debian/debian/changelog 
diaspora-0.6.0.0+debian/debian/changelog
--- diaspora-0.6.0.0+debian/debian/changelog2016-11-24 11:16:10.0 
+0530
+++ diaspora-0.6.0.0+debian/debian/changelog2016-12-12 11:18:48.0 
+0530
@@ -1,3 +1,15 @@
+diaspora (0.6.0.0+debian-7) unstable; urgency=medium
+
+  * Use jquery-ui 6 (See #846961) 
+
+ -- Pirate Praveen   Mon, 12 Dec 2016 11:18:48 +0530
+
+diaspora (0.6.0.0+debian-6) unstable; urgency=medium
+
+  * Switch back to jquery 2 (ruby-jquery-rails now provides jquery 2) 
+
+ -- Pirate Praveen   Wed, 07 Dec 2016 23:18:41 +0530
+
 diaspora (0.6.0.0+debian-5) unstable; urgency=medium
 
   * Remove dependency on ruby-rails-autolink (removed upstream)
diff -Nru diaspora-0.6.0.0+debian/debian/control 
diaspora-0.6.0.0+debian/debian/control
--- diaspora-0.6.0.0+debian/debian/control  2016-11-24 11:16:10.0 
+0530
+++ diaspora-0.6.0.0+debian/debian/control  2016-12-07 23:18:02.0 
+0530
@@ -101,7 +101,7 @@
  ruby-uglifier (>= 2.7.2~),
  ruby-backbone-on-rails (>= 1.2.0.0~),
  ruby-handlebars-assets (>= 2:0.23.1~),
- ruby-jquery-rails (>= 4.2.1~),
+ ruby-jquery-rails (>= 4.2.1-2~),
  ruby-jquery-ui-rails (>= 5.0.5~),
  ruby-js-image-paths (>= 0.1~),
  ruby-js-routes (>= 1.2.4~),
diff -Nru diaspora-0.6.0.0+debian/debian/patches/0120-jquery-ui-6.patch 
diaspora-0.6.0.0+debian/debian/patches/0120-jquery-ui-6.patch
--- diaspora-0.6.0.0+debian/debian/patches/0120-jquery-ui-6.patch   
1970-01-01 05:30:00.0 +0530
+++ diaspora-0.6.0.0+debian/debian/patches/0120-jquery-ui-6.patch   
2016-12-12 11:16:54.0 +0530
@@ -0,0 +1,24 @@
+--- a/Gemfile
 b/Gemfile
+@@ -96,7 +96,7 @@
+ gem "backbone-on-rails", "~> 1.2"
+ gem "handlebars_assets", "~> 0.23.1"
+ gem "jquery-rails",  "~> 4.1", ">= 4.1.1"
+-gem "jquery-ui-rails",   "~> 5.0", ">= 5.0.5"
++gem "jquery-ui-rails",   "~> 6.0"
+ gem "js_image_paths","~> 0.1.0"
+ gem "js-routes", "~> 1.2", ">= 1.2.9"
+ 
+--- a/app/assets/javascripts/main.js
 b/app/assets/javascripts/main.js
+@@ -15,8 +15,8 @@
+ //= require jquery.infinitescroll-custom
+ //= require jquery-ui/core
+ //= require jquery-ui/widget
+-//= require jquery-ui/mouse
+-//= require jquery-ui/sortable
++//= require jquery-ui/widgets/mouse
++//= require jquery-ui/widgets/sortable
+ //= require keycodes
+ //= require fileuploader-custom
+ //= require handlebars.runtime
diff -Nru diaspora-0.6.0.0+debian/debian/patches/0120-use-jquery-3.patch 
diaspora-0.6.0.0+debian/debian/patches/0120-use-jquery-3.patch
--- diaspora-0.6.0.0+debian/debian/patches/0120-use-jquery-3.patch  
2016-11-24 11:16:10.0 +0530
+++ diaspora-0.6.0.0+debian/debian/patches/0120-use-jquery-3.patch  
1970-01-01 05:30:00.0 +0530
@@ -1,67 +0,0 @@
-From 657d06c49061a499b93ca0e43f35b70cad785a3b Mon Sep 17 00:00:00 2001
-From: cmrd Senya 
-Date: Thu, 10 Nov 2016 17:46:31 +0200
-Subject: [PATCH] jQuery 3 integration
-

- app/assets/javascripts/jasmine-load-all.js | 2 +-
- app/helpers/application_helper.rb  | 8 +---
- config/application.rb  | 2 +-
- spec/helpers/application_helper_spec.rb| 2 +-
- 6 files changed, 12 insertions(+), 10 deletions(-)
-
-Index: diaspora/app/assets/javascripts/jasmine-load-all.js
-===
 diaspora.orig/app/assets/javascripts/jasmine-load-all.js
-+++ diaspora/app/assets/javascripts/jasmine-load-all.js
-@@ -1,4 +1,4 @@
--//= require jquery2
-+//= require jquery3
- //= require handlebars.runtime
- //= require templates
- //= require main
-Index: diaspora/app/helpers/application_helper.rb
-===
 diaspora.orig/app/helpers/application_helper.rb
-+++ diaspora/app/helpers/application_helper.rb
-@@ -52,11 +52,11 @@ module ApplicationHelper
-   def jquery_include_tag
- buf = []
- if AppConfig.privacy.jquery_cdn?
--  version = Jquery::Rails::JQUERY_2_VERSION
-+  version = Jquery::Rails::JQUERY_3_VERSION
-   buf << [ 

Bug#847828: unblock: jqueryui/1.12.1+dfsg-3

[Pirate Praveen]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package jqueryui.
This fixes grave bug #847353 (breaks core functionality/user interface
of gitlab and diaspora)

Please also unblock diaspora

debdiff attached

unblock jqueryui/1.12.1+dfsg-3

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ml_IN.UTF-8, LC_CTYPE=ml_IN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru jqueryui-1.12.1+dfsg/debian/changelog 
jqueryui-1.12.1+dfsg/debian/changelog
--- jqueryui-1.12.1+dfsg/debian/changelog   2016-12-01 00:25:30.0 
+0530
+++ jqueryui-1.12.1+dfsg/debian/changelog   2016-12-08 13:29:28.0 
+0530
@@ -1,3 +1,12 @@
+jqueryui (1.12.1+dfsg-3) unstable; urgency=medium
+
+  * Provide node-jquery-ui (Closes: #847353)
+  * Add minimum version of node-requirejs as 2.3.2
+   (r.js is now /usr/lib/nodejs/requirejs/r.js)
+  * Add myself to uploaders
+
+ -- Pirate Praveen   Thu, 08 Dec 2016 13:29:28 +0530
+
 jqueryui (1.12.1+dfsg-2) unstable; urgency=medium
 
   * Add target to build ui/i18n/jquery-ui-i18n.js (Closes: #845647)
diff -Nru jqueryui-1.12.1+dfsg/debian/control 
jqueryui-1.12.1+dfsg/debian/control
--- jqueryui-1.12.1+dfsg/debian/control 2016-12-01 00:25:30.0 +0530
+++ jqueryui-1.12.1+dfsg/debian/control 2016-12-08 13:29:28.0 +0530
@@ -5,9 +5,10 @@
 Uploaders:
  Marcelo Jorge Vieira (metal) ,
  Paul Gevers ,
+ Pirate Praveen 
 Build-Depends:
  debhelper (>= 10~),
- node-requirejs,
+ node-requirejs (>= 2.3.2~),
  node-uglify,
  nodejs,
  yui-compressor,
@@ -47,3 +48,16 @@
  to build highly interactive web applications.
  .
  This package provides examples as reference for developers.
+
+Package: node-jquery-ui
+Architecture: all
+Depends:
+ ${misc:Depends}
+ , nodejs
+Description: JavaScript UI library for dynamic web applications (NodeJs)
+ jQuery UI provides abstractions for low-level interaction and
+ animation, advanced effects and high-level, themeable widgets,
+ built on top of the jQuery JavaScript Library, that you can use
+ to build highly interactive web applications.
+ .
+ Node.js is an event-based server-side JavaScript engine.
diff -Nru jqueryui-1.12.1+dfsg/debian/files jqueryui-1.12.1+dfsg/debian/files
--- jqueryui-1.12.1+dfsg/debian/files   2016-12-01 00:25:30.0 +0530
+++ jqueryui-1.12.1+dfsg/debian/files   1970-01-01 05:30:00.0 +0530
@@ -1 +0,0 @@
-jqueryui_1.12.1+dfsg-2_source.buildinfo web optional
diff -Nru jqueryui-1.12.1+dfsg/debian/node-jquery-ui.install 
jqueryui-1.12.1+dfsg/debian/node-jquery-ui.install
--- jqueryui-1.12.1+dfsg/debian/node-jquery-ui.install  1970-01-01 
05:30:00.0 +0530
+++ jqueryui-1.12.1+dfsg/debian/node-jquery-ui.install  2016-12-08 
13:29:28.0 +0530
@@ -0,0 +1,3 @@
+package.json usr/lib/nodejs/jquery-ui/
+ui usr/lib/nodejs/jquery-ui/
+themes usr/lib/nodejs/jquery-ui/
diff -Nru jqueryui-1.12.1+dfsg/debian/rules jqueryui-1.12.1+dfsg/debian/rules
--- jqueryui-1.12.1+dfsg/debian/rules   2016-12-01 00:25:30.0 +0530
+++ jqueryui-1.12.1+dfsg/debian/rules   2016-12-08 13:29:28.0 +0530
@@ -25,7 +25,7 @@
cp $< $@
 
 jquery-ui.js: build.js
-   nodejs /usr/lib/nodejs/r.js -o build.js
+   nodejs /usr/lib/nodejs/requirejs/r.js -o build.js
sed -i -e 's/@VERSION/$(version)/; s/@DATE/$(timestamp)/' $@
@nodejs --check $@ || (mv $@ $@.failed; false)
 


signature.asc
Description: OpenPGP digital signature

Bug#847827: unblock: ruby-jquery-ui-rails/6.0.1-1

[Pirate Praveen]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Please unblock package ruby-jquery-ui-rails

Last update of libjs-jquery-ui introduced a breaking change which
introduced grave bugs in diaspora and gitlab (#846961). This update
adapts ruby-jquery-ui-rails to work with libjs-jquery-ui in the archive.

Please also unblock libjs-jquery-ui so ruby-jquery-ui-rails can migrate
to testing.

debdiff attached

unblock ruby-jquery-ui-rails/6.0.1-1

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ml_IN.UTF-8, LC_CTYPE=ml_IN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in second .changes but not in first
-
-rw-r--r--  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui.js
-rw-r--r--  root/root   
/usr/share/rubygems-integration/all/specifications/jquery-ui-rails-6.0.1.gemspec
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/data.js -> 
../../../../../javascript/jquery-ui/ui/data.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/disable-selection.js
 -> ../../../../../javascript/jquery-ui/ui/disable-selection.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effect.all.js 
-> ../../../../../javascript/jquery-ui/ui/effect.all.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effect.js -> 
../../../../../javascript/jquery-ui/ui/effect.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-blind.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-blind.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-bounce.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-bounce.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-clip.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-clip.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-drop.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-drop.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-explode.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-explode.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-fade.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-fade.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-fold.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-fold.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-highlight.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-highlight.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-puff.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-puff.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-pulsate.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-pulsate.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-scale.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-scale.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-shake.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-shake.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-size.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-size.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-slide.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-slide.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/effects/effect-transfer.js
 -> ../../../../../../javascript/jquery-ui/ui/effects/effect-transfer.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/escape-selector.js
 -> ../../../../../javascript/jquery-ui/ui/escape-selector.js
lrwxrwxrwx  root/root   
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts/jquery-ui/focusable.js 
-> ../../../../../javascript/jquery-ui/ui/focusable.js
lrwxrwxrwx  root/root   

Bug#847826: Subject: unblock: gitlab/8.13.6+dfsg1-2

[Pirate Praveen]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Please unblock package gitlab
This update fixes security bug #847157 and adapts gitlab for new
ruby-jquery-ui-rails #846961 (which is a grave bug - user interface is
broken, many core features does not work)

debdiff attached. Please unblock ruby-jquery-ui-rails too so gitlab can
really enter testing.

Forgot to set priority high in changelog, so if possible consider it as
high.

unblock gitlab/8.13.6+dfsg1-2

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ml_IN.UTF-8, LC_CTYPE=ml_IN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in second .changes but not in first
-
-rw-r--r--  root/root   DEBIAN/triggers

Control files: lines which differ (wdiff format)

Depends: debconf (>= 0.5) | debconf-2.0, init-system-helpers (>= 1.18~), ruby | 
ruby-interpreter, lsb-base (>= 3.0-6), git (>= 1:2.7.3~), rake, bundler, 
postgresql-client, adduser (>= 3.34~), bc, postgresql-contrib, redis-server (>= 
2:2.8~), nodejs (>= 4~), nginx | httpd, postfix | exim4 | mail-transport-agent, 
openssh-client, ucf, gitlab-shell (>= 3.6.6~), gitlab-workhorse (>= 0.8.5~), 
ruby-rails (>= 2:4.2.7~), ruby-rails (<< 2:5), ruby-rails-deprecated-sanitizer 
(>= 1.0.3~), ruby-responders (>= 2.0~), ruby-sprockets (>= 3.6~), 
ruby-sprockets-es6 (>= 0.9.2~), ruby-default-value-for (>= 3~), ruby-pg (>= 
0.18.4~), ruby-devise (>= 4.2~), ruby-doorkeeper (>= 4.0~), ruby-omniauth (>= 
1.3.1~), ruby-omniauth-auth0 (>= 1.4.1~), ruby-omniauth-azure-oauth2 (>= 
0.0.6~), ruby-omniauth-bitbucket (>= 0.0.2~), ruby-omniauth-cas3 (>= 1.1.2~), 
ruby-omniauth-facebook (>= 4.0~), ruby-omniauth-github (>= 1.1.1~), 
ruby-omniauth-gitlab (>= 1.0.2~), ruby-omniauth-google-oauth2 (>= 0.4.1~), 
ruby-omniauth-kerberos (>= 0.3.0-3~), ruby-omniauth-saml (>= 1.7.0~), 
ruby-omniauth-shibboleth (>= 1.2.0~), ruby-omniauth-twitter (>= 1.2.0~), 
ruby-omniauth-crowd (>= 2.2.0~), ruby-rack-oauth2 (>= 1.2.1~), ruby-recaptcha 
(>= 3.0~), ruby-akismet, ruby-devise-two-factor (>= 3.0~), ruby-rqrcode-rails3 
(>= 0.1.7~), ruby-attr-encrypted (>= 3.0~), ruby-u2f, ruby-browser (>= 2.2~), 
ruby-gitlab-git (>= 10.7~), ruby-omniauth-ldap (>= 1.0.4~), ruby-gollum-lib (>= 
4.2.1+debian~), ruby-github-linguist (>= 4.7.0~), ruby-grape (>= 0.16.2-2~), 
ruby-grape-entity (>= [-0.5~),-] {+0.6~),+} ruby-rack-cors (>= 0.4.0~), 
ruby-kaminari (>= 0.17~), ruby-hamlit (>= 2.7~), ruby-carrierwave (>= 0.9~), 
ruby-dropzonejs-rails (>= 0.7.1~), ruby-fog-aws (>= 0.9~), ruby-fog-azure, 
ruby-fog-core (>= 1.40~), ruby-fog-local (>= 0.3~), ruby-fog-google (>= 0.3~), 
ruby-fog-openstack (>= 0.1~), ruby-fog-rackspace, ruby-unf (>= 0.1.4-2~), 
ruby-six (>= 0.2.0-3~), ruby-seed-fu (>= 2.3.5~), ruby-htmlentities (>= 
4.3.3~), ruby-html-pipeline (>= 1.11.0), ruby-task-list (>= 1.0.5~), 
ruby-github-markup (>= 1.5~), ruby-redcarpet (>= 3.3.4~), ruby-redcloth (>= 
4.3.2-2~), ruby-org (>= 0.9.12-2~), ruby-creole (>= 0.5.0~), ruby-wikicloth (>= 
0.8.1~), asciidoctor (>= 1.5.2~), ruby-rouge (>= 2.0~), ruby-truncato, 
ruby-nokogiri (>= 1.6.7.2~), ruby-diffy (>= 3.0.3~), unicorn (>= 5.1~), 
ruby-unicorn-worker-killer (>= 0.4.4~), ruby-state-machines-activerecord (>= 
0.4.0~), ruby-after-commit-queue, ruby-acts-as-taggable-on (>= 4.0~), 
ruby-sinatra (>= 1.4.7-4~), ruby-sidekiq (>= 4.2~), ruby-sidekiq-cron (>= 
0.4.0~), ruby-redis-namespace, ruby-httparty (>= 0.13.3~), ruby-rainbow (>= 
2.1~), ruby-settingslogic (>= 2.0.9~), ruby-version-sorter (>= 2.1~), 
ruby-redis-rails (>= 4.0.0~), ruby-tinder (>= 1.10.1-2~), ruby-hipchat (>= 
1.5.0~), ruby-gitlab-flowdock-git-hook (>= 1.0.1-2~), 
ruby-gemnasium-gitlab-service (>= 0.2~), ruby-slack-notifier (>= 1.2.0~), 
ruby-asana (>= 0.4.0~), ruby-fogbugz (>= 0.2.1-3~), ruby-d3-rails (>= 3.1~), 
ruby-cal-heatmap-rails (>= 3.6.0~), ruby-underscore-rails (>= 1.4~), 
ruby-sanitize (>= 2.0~), ruby-babosa (>= 1.0.2~), ruby-loofah (>= 2.0.3~), 
ruby-licensee (>= 8.0.0-2~), ruby-rack-attack (>= 4.3.1~), ruby-ace-rails-ap 
(>= 4.1~), ruby-mousetrap-rails (>= 1.4.6~), ruby-charlock-holmes (>= 0.7.3~), 
ruby-oj (>= 2.17.4), ruby-chronic (>= 0.10.2-3~), ruby-chronic-duration, 
ruby-sass-rails (>= 5.0.6~), ruby-coffee-rails (>= 4.1.0~), 
ruby-coffee-script-source (>= 1.10.0~), ruby-uglifier (>= 2.7.2~), 
ruby-turbolinks (>= 2.5.0~), ruby-jquery-turbolinks (>= 2.1.0~), 
ruby-addressable (>= 2.3.8~), ruby-bootstrap-sass (>= 3.3.0~), 
ruby-font-awesome-rails (>= 4.6.1~), ruby-gemojione (>= 3.0~), ruby-gon (>= 
6.1~), ruby-jquery-atwho-rails (>= 1.3.2~), ruby-jquery-rails (>= 4.1~), 
ruby-jquery-scrollto-rails (>= 1.4.3~), 

Re: OpenSSL 1.1.0

[Sean Whitton]

Hello,

On Wed, Nov 16, 2016 at 04:03:04PM +, Jonathan Wiltshire wrote:
> On 2016-11-16 12:26, Ian Jackson wrote:
> > In the absence of input from the openssl maintainers, I would like to
> > ask the Release Team's opinion.
> > 
> > If we are going to wind back on this change we should do it ASAP.  We
> > should not allow ourselves to make the decision to press on, simply by
> > failing to decide otherwise.
> 
> Indeed it's been under discussion for the past week or so independent of the
> thread on -devel. I hope you'll forgive me for not breaking confidences just
> yet, but we expect to be able to resolve this very soon.

Sorry to resurrect an old thread, but did I miss an e-mail follow-up to this?

-- 
Sean Whitton


signature.asc
Description: PGP signature

Re: Release impact of introducing a new archive section?

[Josh Triplett]

On Sun, Dec 11, 2016 at 10:16:51PM +0100, Joerg Jaspert wrote:
> On 14518 March 1977, Josh Triplett wrote:
> >> (my first thought was a canonical online location, but these tools may
> >> not want that at runtime and can't rely on it at build time, but maybe
> >> that should be the source used for the package)
> > Packaging this data (section names, short descriptions, and long
> > descriptions) seems like a great idea.  Ideally, packages would have a
> > Depends on this and use the data at runtime, rather than using a
> > Build-Depends and compiling it in.  With some care, such a package could
> > also serve as the basis for the descriptions on packages.debian.org.
> 
> Does it need a package? Or just a file in the archive somewhere?

If we can get every package to handle this entirely at runtime, then
ideally I'd suggest archive metadata downloaded by apt.  That would have
the advantage of automatically handling new sections, including for
third-party archives.  Packaging it doesn't have that advantage, though
it also seems logistically simpler.

- Josh Triplett

Re: Release impact of introducing a new archive section?

[Joerg Jaspert]

On 14518 March 1977, Josh Triplett wrote:
>> (my first thought was a canonical online location, but these tools may
>> not want that at runtime and can't rely on it at build time, but maybe
>> that should be the source used for the package)
> Packaging this data (section names, short descriptions, and long
> descriptions) seems like a great idea.  Ideally, packages would have a
> Depends on this and use the data at runtime, rather than using a
> Build-Depends and compiling it in.  With some care, such a package could
> also serve as the basis for the descriptions on packages.debian.org.

Does it need a package? Or just a file in the archive somewhere?

-- 
bye, Joerg

Re: Release impact of introducing a new archive section?

[Josh Triplett]

On Sun, Dec 11, 2016 at 09:45:36AM +, Ian Campbell wrote:
> On Thu, 2016-12-08 at 21:39 -0800, Josh Triplett wrote:
> > I've now written and submitted all of these patches.
> 
> Might it be useful to have this list of names and descriptions in some
> canonical packaged location, such that updating these tools is just a
> version bump on a build dep, or even a runtime dep? Best case maybe it
> would be possible to arrange for it to be a simple binNMU.
> 
> (my first thought was a canonical online location, but these tools may
> not want that at runtime and can't rely on it at build time, but maybe
> that should be the source used for the package)

Packaging this data (section names, short descriptions, and long
descriptions) seems like a great idea.  Ideally, packages would have a
Depends on this and use the data at runtime, rather than using a
Build-Depends and compiling it in.  With some care, such a package could
also serve as the basis for the descriptions on packages.debian.org.

- Josh Triplett

Bug#847767: nmu: efl_1.18.1-2

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu efl_1.18.1-2 . ANY . experimental . -m "Rebuild against bullet 2.83.7"

there was a transition in sid recently ...


Andreas

Bug#847763: nmu: xtell_2.10.8

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu xtell_2.10.8 . i386 . unstable . -m "Rebuild against readline7."

Maintainer upload was built against readline6.


Andreas

Bug#847587: unblock diaspora and ruby-jquery-rails

[Pirate Praveen]

On Fri, 9 Dec 2016 22:07:51 +0530 Pirate Praveen  wrote:
> package: release.debian.org
> 
> ruby-jquery-rails 4.2.1-2 fixes grave bug #846916 (which affects
> diaspora)  and diaspora 0.6.0.0+debian-6 drops patches to use
> ruby-jquery-rails 4.2.1-2
> 

The core functionality is broken if jquery 3 is used. User interface
elements like buttons, drop downs are all broken. ruby-jquery-rails
4.2.1-2 now included jquery 2 so these two updates fixes the usability
issue.



signature.asc
Description: OpenPGP digital signature

Processed: withdrawing unblock requests

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was prav...@debian.org).
> usertags 847725 + unblock
Usertags were: unblock.
Usertags are now: unblock.
> usertags 847639 + unblock
There were no usertags set.
Usertags are now: unblock.
> usertags 847724 + unblock
Usertags were: unblock.
Usertags are now: unblock.
> close 847639
Bug #847639 [release.debian.org] unblock node-grunt-contrib-concat 1.0.1-2
Marked Bug as done
> close 847724
Bug #847724 {Done: Emilio Pozuelo Monfort } 
[release.debian.org] unblock node-repeat-element 1.1.2+github-2
Bug 847724 is already marked as done; not doing anything.
> close 847725
Bug #847725 {Done: Emilio Pozuelo Monfort } 
[release.debian.org] unblock node-extend-shallow 2.0.1-3
Bug 847725 is already marked as done; not doing anything.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
847639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847639
847724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847724
847725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847725: marked as done (unblock node-extend-shallow 2.0.1-3)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 12:52:10 +0100
with message-id <6f7ea788-9211-1143-b0f1-92efe54aa...@debian.org>
and subject line Re: Bug#847725: unblock node-extend-shallow 2.0.1-3
has caused the Debian Bug report #847725,
regarding unblock node-extend-shallow 2.0.1-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: release.debian.org

Fixes RC bug #846700



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On 11/12/16 05:54, Pirate Praveen wrote:
> package: release.debian.org
> 
> Fixes RC bug #846700

nack. also next time please include a somewhat longer description of what you're
fixing and why you think it is justified to age your package.

Emilio--- End Message ---

Bug#847724: marked as done (unblock node-repeat-element 1.1.2+github-2)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 12:50:58 +0100
with message-id 
and subject line Re: Bug#847724: unblock node-repeat-element 1.1.2+github-2
has caused the Debian Bug report #847724,
regarding unblock node-repeat-element 1.1.2+github-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: release.debian.org

Fixes rc bug #846692 (it causes gitlab to be marked auto removal)



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On 11/12/16 05:48, Pirate Praveen wrote:
> package: release.debian.org
> 
> Fixes rc bug #846692 (it causes gitlab to be marked auto removal)

As said on your other bugs:

- Use reportbug to get the right metadata
- This can wait 2 more days

Emilio--- End Message ---

Bug#847726: marked as done (unblock node-normalize-path 2.0.1-2)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 17:17:54 +0530
with message-id <78d8db43-aed8-2504-06fd-5d7f6d8c7...@debian.org>
and subject line Re: Bug#847726: unblock node-normalize-path 2.0.1-2
has caused the Debian Bug report #847726,
regarding unblock node-normalize-path 2.0.1-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: release.debian.org

Fixes RC bug #846743 (causes gitlab to be marked for autoremoval)





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On ഞായര്‍ 11 ഡിസംബര്‍ 2016 05:09 വൈകു, Adam D. Barratt wrote:
> Sigh. :-(
> 
> I didn't say it doesn't affect the package, and of course it's still RC.
> 
> What I said is it doesn't affect _use_ of the package. You're asking for
> the migration time to be reduced, I'm asking for the rationale for that.
> The fix for the FTBFS needs to be in stretch, we both agree on that. My
> question is why it needs to be in stretch today rather than in two days
> time when the 10 day counter is up.

Like I said before, I was under the impression that all RC bugs qualify
for unblock requests. Since FTBFS is not severe, withdrawing unblock request



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#847636: marked as done (unblock node-cpr)

[Debian Bug Tracking System]

Your message dated Sun, 11 Dec 2016 17:13:54 +0530
with message-id 
and subject line since FTBFS is not severe, withdrawing unblock request
has caused the Debian Bug report #847636,
regarding unblock node-cpr
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: release-debian.org

Fixes serious bug #846010 and #847614



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
since FTBFS is not severe, withdrawing unblock request



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#847726: unblock node-normalize-path 2.0.1-2

[Adam D. Barratt]

On Sun, 2016-12-11 at 16:55 +0530, Pirate Praveen wrote:
> 
> On 2016, ഡിസംബർ 11 4:05:41 PM IST, "Adam D. Barratt" 
>  wrote:
> >On Sun, 2016-12-11 at 10:24 +0530, Pirate Praveen wrote:
> >> package: release.debian.org
> >
> >*Please* use the correct metadata here.
> >
> >> Fixes RC bug #846743 (causes gitlab to be marked for autoremoval)
> >
> >While this is true, the auto-removal date is in over a month from now.
> >On that basis, and given that the bug in node-normalize-path doesn't
> >affect use of the package in stretch, why should it not wait its full
> >10
> >days for migration?
> 
> If FTBFS is not considered to be affecting the package, can I reduce the 
> severity of that bug to normal?

Sigh. :-(

I didn't say it doesn't affect the package, and of course it's still RC.

What I said is it doesn't affect _use_ of the package. You're asking for
the migration time to be reduced, I'm asking for the rationale for that.
The fix for the FTBFS needs to be in stretch, we both agree on that. My
question is why it needs to be in stretch today rather than in two days
time when the 10 day counter is up.

Regards,

Adam

Bug#847636: Re: unblock node-cpr

[Pirate Praveen]

On ഞായര്‍ 11 ഡിസംബര്‍ 2016 04:59 വൈകു, Pirate Praveen wrote:
> Like my previous reply. Won't FTBFS be considered as affecting the
> package, then it needs to be documented.

The announcement said "Should your upload to unstable include security fixes or 
fixes for severe bugs, we file an unblock bug asking for us to lower the 
required age." I was under the impression that all RC bugs qualify. It would 
have been better if it said (severity grave or critical then there wouldn't 
have been any confusion).




signature.asc
Description: OpenPGP digital signature

Bug#847636: Re: unblock node-cpr

[Pirate Praveen]

On 2016, ഡിസംബർ 10 10:47:01 PM IST, "Adam D. Barratt" 
 wrote:
># bcc to control@
>user release.debian@packages.debian.org
>usertags 847636 + unblock
>tags 847636 + moreinfo
>
>On Sat, 2016-12-10 at 10:45 +0530, Pirate Praveen wrote:
>> package: release-debian.org
>
>Please either use reportbug or add the correct metadata yourself (and
>preferably use package names that exist :-p).
>
>> Fixes serious bug #846010 and #847614
>
>We're not frozen yet, so what you're asking for is for the upload to
>migrate to testing more quickly than the default 10 days.
>
>There is no node-cpr package in testing currently and, even if there
>were, neither of the cited bugs would affect the usability of the
>package there, so I'm not personally convinced that they merit a
>reduction in migration time.

Like my previous reply. Won't FTBFS be considered as affecting the package, 
then it needs to be documented.

>Regards,
>
>Adam

Bug#847726: unblock node-normalize-path 2.0.1-2

[Pirate Praveen]

On 2016, ഡിസംബർ 11 4:05:41 PM IST, "Adam D. Barratt"  
wrote:
>On Sun, 2016-12-11 at 10:24 +0530, Pirate Praveen wrote:
>> package: release.debian.org
>
>*Please* use the correct metadata here.
>
>> Fixes RC bug #846743 (causes gitlab to be marked for autoremoval)
>
>While this is true, the auto-removal date is in over a month from now.
>On that basis, and given that the bug in node-normalize-path doesn't
>affect use of the package in stretch, why should it not wait its full
>10
>days for migration?

If FTBFS is not considered to be affecting the package, can I reduce the 
severity of that bug to normal?

>Regards,
>
>Adam

Processed: user release.debian....@packages.debian.org, usertagging 846692, tagging 846692, usertagging 847726 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
a...@adam-barratt.org.uk).
> usertags 846692 - unblock
Usertags were: unblock.
Usertags are now: .
> tags 846692 - moreinfo
Bug #846692 {Done: Pirate Praveen } 
[src:node-repeat-element] node-repeat-element: FTBFS: Test failures
Removed tag(s) moreinfo.
> usertags 847726 + unblock
There were no usertags set.
Usertags are now: unblock.
> tags 847726 + moreinfo
Bug #847726 [release.debian.org] unblock node-normalize-path 2.0.1-2
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
846692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846692
847726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: user release.debian....@packages.debian.org, usertagging 846692, tagging 846692, usertagging 847725 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was 
a...@adam-barratt.org.uk).
> usertags 846692 + unblock
There were no usertags set.
Usertags are now: unblock.
> tags 846692 + moreinfo
Bug #846692 {Done: Pirate Praveen } 
[src:node-repeat-element] node-repeat-element: FTBFS: Test failures
Added tag(s) moreinfo.
> usertags 847725 + unblock
There were no usertags set.
Usertags are now: unblock.
> tags 847725 + moreinfo
Bug #847725 [release.debian.org] unblock node-extend-shallow 2.0.1-3
Added tag(s) moreinfo.
> usertags 847724 + unblock
There were no usertags set.
Usertags are now: unblock.
> tags 847724 + moreinfo
Bug #847724 [release.debian.org] unblock node-repeat-element 1.1.2+github-2
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
846692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846692
847724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847724
847725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847726: unblock node-normalize-path 2.0.1-2

[Adam D. Barratt]

On Sun, 2016-12-11 at 10:24 +0530, Pirate Praveen wrote:
> package: release.debian.org

*Please* use the correct metadata here.

> Fixes RC bug #846743 (causes gitlab to be marked for autoremoval)

While this is true, the auto-removal date is in over a month from now.
On that basis, and given that the bug in node-normalize-path doesn't
affect use of the package in stretch, why should it not wait its full 10
days for migration?

Regards,

Adam

Re: Release impact of introducing a new archive section?

[Ian Campbell]

On Thu, 2016-12-08 at 21:39 -0800, Josh Triplett wrote:
> I've now written and submitted all of these patches.

Might it be useful to have this list of names and descriptions in some
canonical packaged location, such that updating these tools is just a
version bump on a build dep, or even a runtime dep? Best case maybe it
would be possible to arrange for it to be a simple binNMU.

(my first thought was a canonical online location, but these tools may
not want that at runtime and can't rely on it at build time, but maybe
that should be the source used for the package)

Ian.