[DRE-maint] Bug#848510: obs-api: fails to install: Sprockets::FileNotFound: couldn't find file 'jquery-ui/menu' with type 'application/javascript'

[Andreas Beckmann]

Package: obs-api
Version: 2.7.1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

[...]
  Selecting previously unselected package obs-api.
  (Reading database ... 
(Reading database ... 21653 files and directories currently installed.)
  Preparing to unpack .../obs-api_2.7.1-7_amd64.deb ...
  Unpacking obs-api (2.7.1-7) ...
  Setting up obs-api (2.7.1-7) ...
  Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
  dbconfig-common: writing config to /etc/dbconfig-common/obs-api.conf
  
  Creating config file /etc/dbconfig-common/obs-api.conf with new version
  
  Creating config file /etc/obs/api/config/database.yml with new version
  checking privileges on database obsapi for obs-api@localhost: user creation 
needed.
  granting access to database obsapi for obs-api@localhost: success.
  verifying access for obs-api@localhost: success.
  creating database obsapi: success.
  verifying database obsapi exists: success.
  populating database via sql...  done.
  dbconfig-common: flushing administrative password
  You are replacing the current local value of frozen, which is currently nil
  You are replacing the current local value of without, which is currently nil
  obsapi already exists
  I, [2016-12-15T21:56:49.431924 #30697]  INFO -- : Writing 
/usr/share/obs/api/public/assets/webui/application/cm2/index-d9309c3b5fe48e277e7ae61c3532b48b45863528cf21bd69abe99012ca693253.js
  I, [2016-12-15T21:56:49.432506 #30697]  INFO -- : Writing 
/usr/share/obs/api/public/assets/webui/application/cm2/index-d9309c3b5fe48e277e7ae61c3532b48b45863528cf21bd69abe99012ca693253.js.gz
  I, [2016-12-15T21:56:49.435578 #30697]  INFO -- : Writing 
/usr/share/obs/api/public/assets/dataTables/back_disabled-6950463a4f9db9435b8df01fa276eaf88aa65b8913b82e979317d741305bb5d6.png
[...]
  I, [2016-12-15T21:56:50.442162 #30697]  INFO -- : Writing 
/usr/share/obs/api/public/assets/transparency_grey_20-e28ff6ee88073ddf5fdfb9448a6279c53e70b19a0614b48e9bafdda39eaf3c99.png
  I, [2016-12-15T21:56:50.444206 #30697]  INFO -- : Writing 
/usr/share/obs/api/public/assets/voting-neutral-6fd6ae6c9aad7a50dacbb129c33d8c9df05c2be96ae1b7b3db763d67c41e5785.png
  I, [2016-12-15T21:56:50.445477 #30697]  INFO -- : Writing 
/usr/share/obs/api/public/assets/x-office-spreadsheet-038f5d23c95d21236c3a76885df7e598178c277bb2533e59bec6a099c93c2aab.png
  rake aborted!
  Sprockets::FileNotFound: couldn't find file 'jquery-ui/menu' with type 
'application/javascript'
  Checked in these paths: 
/usr/share/obs/api/app/assets/icons
/usr/share/obs/api/app/assets/images
/usr/share/obs/api/app/assets/javascripts
/usr/share/obs/api/app/assets/stylesheets
/usr/share/obs/api/vendor/assets/javascripts
/usr/share/ruby-font-awesome-rails/app/assets/fonts
/usr/share/ruby-font-awesome-rails/app/assets/stylesheets
/usr/share/ruby-jquery-ui-rails/app/assets/images
/usr/share/ruby-jquery-ui-rails/app/assets/javascripts
/usr/share/ruby-jquery-ui-rails/app/assets/stylesheets
/usr/share/ruby-jquery-rails/vendor/assets/javascripts
/usr/share/ruby-rails-tokeninput/app/assets/javascripts
/usr/share/ruby-rails-tokeninput/app/assets/stylesheets
/usr/share/ruby-codemirror-rails/vendor/assets/javascripts
/usr/share/ruby-codemirror-rails/vendor/assets/stylesheets

/usr/share/obs/api/vendor/gems/jquery-datatables-rails-1.12.2/app/assets/images

/usr/share/obs/api/vendor/gems/jquery-datatables-rails-1.12.2/app/assets/javascripts

/usr/share/obs/api/vendor/gems/jquery-datatables-rails-1.12.2/app/assets/media

/usr/share/obs/api/vendor/gems/jquery-datatables-rails-1.12.2/app/assets/stylesheets
/usr/share/ruby-flot-rails/vendor/assets/javascripts
/usr/share/ruby-cocoon/app/assets/javascripts
  /usr/share/obs/api/app/assets/javascripts/webui/application.js:14
  Tasks: TOP => assets:precompile
  (See full trace by running task with --trace)
  dpkg: error processing package obs-api (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   obs-api



cheers,

Andreas


obs-api_2.7.1-7.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#851356: obs-api: unowned files after purge (policy 6.8, 10.8): /var/log/obs/*, /etc/obs/api/config/*

[Andreas Beckmann]

Package: obs-api
Version: 2.7.1-9
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

>From the attached log (scroll to the bottom...):

2m36.6s ERROR: FAIL: Package purging left files on system:
  /etc/obs/  owned by: obs-api
  /etc/obs/api/  owned by: obs-api
  /etc/obs/api/config/   owned by: obs-api
  /etc/obs/api/config/database.yml   not owned
  /etc/obs/api/config/secret.key not owned
  /var/log/obs/  owned by: obs-api
  /var/log/obs/access.lognot owned
  /var/log/obs/backend_access.lognot owned
  /var/log/obs/clockworkd.clock.output   not owned
  /var/log/obs/delayed_job.log   not owned
  /var/log/obs/error.log not owned
  /var/log/obs/lastevents.access.log not owned
  /var/log/obs/production.lognot owned
  /var/log/obs/production.searchd.lognot owned
  /var/log/obs/production.searchd.query.log  not owned
  /var/log/obs/production.sphinx.pid not owned


cheers,

Andreas


obs-api_2.7.1-9.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#841583: ruby-dataobjects-mysql: FTBFS: mysql_install_db: [ERROR] unknown option '--force'

[Andreas Beckmann]

Followup-For: Bug #841583
Control: block -1 with 851131

The --force problem is specific to mysql, it does not happen with
mariadb. But it fails differently on mariadb:

[...]
2017-01-18 13:52:53 140102037378944 [Note] /usr/sbin/mysqld (mysqld 
10.1.20-MariaDB-3) starting as process 3768 ...
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Using mutexes to ref count 
buffer pool pages
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: The InnoDB memory heap is 
disabled
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Mutexes and rw_locks use GCC 
atomic builtins
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: GCC builtin 
__atomic_thread_fence() is used for memory barrier
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Compressed tables use zlib 
1.2.8
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Using Linux native AIO
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Using SSE crc32 instructions
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Initializing buffer pool, 
size = 128.0M
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Completed initialization of 
buffer pool
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Highest supported file 
format is Barracuda.
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: 128 rollback segment(s) are 
active.
2017-01-18 13:52:53 140102037378944 [Note] InnoDB: Waiting for purge to start
2017-01-18 13:52:53 140102037378944 [Note] InnoDB:  Percona XtraDB 
(http://www.percona.com) 5.6.34-79.1 started; log sequence number 1622838
2017-01-18 13:52:53 140102037378944 [Note] Plugin 'FEEDBACK' is disabled.
2017-01-18 13:52:53 140101342430976 [Note] InnoDB: Dumping buffer pool(s) not 
yet started
2017-01-18 13:52:53 140102037378944 [Note] /usr/sbin/mysqld: ready for 
connections.
Version: '10.1.20-MariaDB-3'  socket: '/tmp/tmp.mXSW0s03Pw/mysql.sock'  port: 0 
 Debian unstable
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root'@'localhost''
ERROR 1698 (28000): Access denied for user 'root'@'localhost'
debian/rules:19: recipe for target 'override_dh_auto_install' failed

which seems to be another instance of #851131


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#852808: diaspora-common: fails to upgrade from stretch: chown: cannot access '/var/lib/diaspora': No such file or directory

[Andreas Beckmann]

Package: diaspora-common
Version: 0.6.3.0+debian1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'sid' fails.

>From the attached log (scroll to the bottom...):

[...]
  Preparing to unpack .../24-diaspora-common_0.6.3.0+debian1_all.deb ...
  Unpacking diaspora-common (0.6.3.0+debian1) over (0.6.0.0+debian6) ...
[...]
  Setting up diaspora-common (0.6.3.0+debian1) ...
  Installing new version of config file /etc/diaspora/diaspora-common.conf ...
  Creating/updating diaspora user account...
  chown: cannot access '/var/lib/diaspora': No such file or directory
  dpkg: error processing package diaspora-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  Setting up nginx (1.10.2-4) ...
  Processing triggers for libc-bin (2.24-9) ...
  Errors were encountered while processing:
   diaspora-common


cheers,

Andreas


diaspora-common_0.6.3.0+debian1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#856606: gitlab: fails to upgrade from 'stretch': nginx example configuration file not found

[Andreas Beckmann]

Control: reopen -1

On 2017-03-03 05:40, Pirate Praveen wrote:
> On Thu, 02 Mar 2017 22:35:55 +0100 Andreas Beckmann  wrote:
>> during a test with piuparts I noticed your package fails to upgrade from
>> 'jessie'.
>> It installed fine in 'jessie', then the upgrade to 'stretch' fails.

Oops, wrong template.

It installed fine in 'stretch' (8.13.11+dfsg-2), then the upgrade to
'sid' (8.13.11+dfsg-4) fails.


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#856606: gitlab: fails to upgrade from 'stretch': nginx example configuration file not found

[Andreas Beckmann]

On 2017-03-04 08:22, Pirate Praveen wrote:
> On വെള്ളി 03 മാര്‍ച്ച് 2017 10:00 വൈകു, Andreas Beckmann wrote:
>> Oops, wrong template.
>>
>> It installed fine in 'stretch' (8.13.11+dfsg-2), then the upgrade to
>> 'sid' (8.13.11+dfsg-4) fails.
> 
> Can you please explain why you consider this a bug even after I closed
> the bug once? Are we supposed to support upgrading between versions in
> unstable? This is going to be the first version of gitlab in a stable
> release.

Yes, upgrading packages must work. And especially between versions in
testing (which will become relevant if 8.13.11+dfsg-4 migrates to
testing). And later on from stable to stable-pu (in case you need to
apply fixes after the release).

What else would you want to do with a gitlab installation in testing if
upgrading does not work?


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#856720: diaspora{, -installer}: fails to install: Errno::EEXIST: File exists @ dir_s_mkdir - /usr/share/diaspora/tmp

[Andreas Beckmann]

Package: diaspora,diaspora-installer
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 0.6.0.1+debian-1
Control: found -1 0.6.3.0+debian1

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

[...]
  Selecting previously unselected package diaspora.
  (Reading database ... 
(Reading database ... 35888 files and directories currently installed.)
  Preparing to unpack .../diaspora_0.6.0.1+debian-1_all.deb ...
  Unpacking diaspora (0.6.0.1+debian-1) ...
  Setting up diaspora (0.6.0.1+debian-1) ...
  /var/lib/dpkg/info/diaspora.postinst: 38: 
/var/lib/dpkg/info/diaspora.postinst: -e: not found
  Setting up environment varibales...
  Using /etc/diaspora.conf...
  export DB_NAME=diaspora_production
  RAILS_ENV=production DB=postgres ENVIRONMENT_URL=https://localhost
  Verifying we have all required libraries...
  Resolving dependencies..
  Using rake 10.5.0
  Using CFPropertyList 2.2.8
  Using i18n 0.7.0
  Using json 1.8.3
  Using minitest 5.9.0
  Using thread_safe 0.3.5
[...]
  -- add_foreign_key("o_auth_applications", "users")
 -> 0.0017s
  -- add_foreign_key("people", "pods", {:name=>"people_pod_id_fk", 
:on_delete=>:cascade})
 -> 0.0019s
  -- add_foreign_key("poll_participation_signatures", "poll_participations", 
{:name=>"poll_participation_signatures_poll_participation_id_fk", 
:on_delete=>:cascade})
 -> 0.0018s
  -- add_foreign_key("poll_participation_signatures", "signature_orders", 
{:name=>"poll_participation_signatures_signature_orders_id_fk"})
 -> 0.0018s
  -- add_foreign_key("posts", "people", {:column=>"author_id", 
:name=>"posts_author_id_fk", :on_delete=>:cascade})
 -> 0.0021s
  -- add_foreign_key("ppid", "o_auth_applications")
 -> 0.0017s
  -- add_foreign_key("ppid", "users")
 -> 0.0016s
  -- add_foreign_key("profiles", "people", {:name=>"profiles_person_id_fk", 
:on_delete=>:cascade})
 -> 0.0018s
  -- add_foreign_key("services", "users", {:name=>"services_user_id_fk", 
:on_delete=>:cascade})
 -> 0.0019s
  -- add_foreign_key("share_visibilities", "users", 
{:name=>"share_visibilities_user_id_fk", :on_delete=>:cascade})
 -> 0.0019s
  -- initialize_schema_migrations_table()
 -> 0.0064s
  Precompiling assets...
  Rack::SSL is enabled
  /usr/lib/ruby/vendor_ruby/i18n-inflector/api_strict.rb:60: warning: 
Enumerator.new without a block is deprecated; use Object#to_enum
  DEPRECATION WARNING: You are using the a deprecated processor interface 
#.
  Please update your processor interface:
  
https://github.com/rails/sprockets/blob/master/guides/extending_sprockets.md#supporting-all-versions-of-sprockets-in-processors
   (called from block in  at 
/usr/lib/ruby/vendor_ruby/js_image_paths/engine.rb:8)
  /usr/lib/ruby/vendor_ruby/i18n-inflector/api_strict.rb:60: warning: 
Enumerator.new without a block is deprecated; use Object#to_enum
  /usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data.rb:24: warning: 
Enumerator.new without a block is deprecated; use Object#to_enum
  /usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data.rb:25: warning: 
Enumerator.new without a block is deprecated; use Object#to_enum
  /usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data_strict.rb:42: 
warning: Enumerator.new without a block is deprecated; use Object#to_enum
  /usr/lib/ruby/vendor_ruby/i18n-inflector/backend.rb:331: warning: 
Enumerator.new without a block is deprecated; use Object#to_enum
  /usr/lib/ruby/vendor_ruby/i18n-inflector/api_strict.rb:60: warning: 
Enumerator.new without a block is deprecated; use Object#to_enum
  /usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data.rb:24: warning: 
Enumerator.new without a block is deprecated; use Object#to_enum
  /usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data.rb:25: warning: 
Enumerator.new without a block is deprecated; use Object#to_enum
  /usr/lib/ruby/vendor_ruby/i18n-inflector/inflection_data_strict.rb:42: 
warning: Enumerator.new without a block is deprecated; use Object#to_enum
  /usr/lib/ruby/vendor_ruby/i18n-inflector/backend.rb:331: warning: 
Enumerator.new without a block is deprecated; use Object#to_enum
  rake aborted!
  Errno::EEXIST: File exists @ dir_s_mkdir - /usr/share/diaspora/tmp
  
  Tasks: TOP => assets:precompile
  (See full trace by running task with --trace)
  dpkg: error processing package diaspora (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   diaspora


A similar failure happens in diaspora-installer.


cheers,

Andreas


diaspora_0.6.0.1+debian-1.log.gz
Description: application/gzip


diaspora-installer_0.6.3.0+debian1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintain

[DRE-maint] Bug#856606: gitlab: fails to upgrade from 'stretch': nginx example configuration file not found

[Andreas Beckmann]

On 2017-03-04 13:27, Pirate Praveen wrote:
> On ശനി 04 മാര്‍ച്ച് 2017 04:25 വൈകു, Andreas Beckmann wrote:
>> Yes, upgrading packages must work. And especially between versions in
>> testing (which will become relevant if 8.13.11+dfsg-4 migrates to
>> testing). And later on from stable to stable-pu (in case you need to
>> apply fixes after the release).
> I thought you need support upgrading between stable to next stable only.
> Can you show the relevant policy that says upgrading between versions in
> testing has to work?

I don't think that is written explicitly in the policy, but there seems
to be general understanding that you must be able upgrade from one
package version to the next package version within a suite (unstable,
testing, stable) as well as between suites (oldstable->stable,
stable->testing, testing->unstable). (This may not be true for packages
in experimental, but once the package gets uploaded to unstable ... you
want to be able to upgrade from the previous version in unstable to the
current one).
What is usually not supported are upgrades that skip stable releases
(e.g. upgrading directly from old-oldstable to stable without upgrading
from old-oldstable to oldstable first).

If you disagree, please take this to the tech-ctte.

>> What else would you want to do with a gitlab installation in testing if
>> upgrading does not work?
> Did you update /etc/gitlab/gitlab-debian.conf?

I didn't touch anything, I'm just doing automated upgrade tests with
piuparts, so all config files are at their defaults.

> This happened because a
> configuration file has changed. How am I supposed to make changes in
> configuration files then?

Use ucf? But you already use this.
Or what do you mean with "making changes in configuration files"?

Having briefly looked at the postinst script, it appears to me that all
the nginx_* variables are not set at all ...


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#856606: gitlab: fails to upgrade from 'stretch': nginx example configuration file not found

[Andreas Beckmann]

On 2017-03-09 10:27, Pirate Praveen wrote:
>> Having briefly looked at the postinst script, it appears to me that all
>> the nginx_* variables are not set at all ...
> 
> nginx_* variables are set in gitlab-debian.conf. Since this version of
> gitlab makes a change in those variables postinst should be looking at
> new locations, but ucf seems to be not installing the new version of
> config file.
> 
> These variables are set in line 45 of postinst. I tried moving ucf
> registration code before this line, but the result is same.

I checked for sourcing (.) other configs, didn't notice the
  export $(cat ...)

to make the error message more useful:
echo "nginx example configuration file ${nginx_conf_example} not found"

I think the problem is the paths to the templates being set in config
files. You load the existing config file, which contains paths from the
previous package version, but these files no longer exist.
nginx_conf_example (and all other similar variables) must be set in the
postinst itself (which should be the only user of them), they are not
user^Wadmin-configurable.


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#857375: ruby-jar-dependencies: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/ruby/vendor_ruby/rubygems_plugin.rb

[Andreas Beckmann]

Package: ruby-jar-dependencies
Version: 0.3.10-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ruby-jar-dependencies.
  Preparing to unpack .../ruby-jar-dependencies_0.3.10-1_all.deb ...
  Unpacking ruby-jar-dependencies (0.3.10-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-jar-dependencies_0.3.10-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/rubygems_plugin.rb', which is 
also in package yard 0.8.7.4-1
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-jar-dependencies_0.3.10-1_all.deb


cheers,

Andreas


yard=0.8.7.4-1_ruby-jar-dependencies=0.3.10-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#857534: ruby-haml: broken symlinks: /usr/share/doc/ruby-haml/yardoc/{css, js} -> ../../../yard/templates/default/fulldoc/html/{css, js}

[Andreas Beckmann]

Package: ruby-haml
Version: 4.0.7-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m48.2s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/ruby-haml/yardoc/css -> 
../../../yard/templates/default/fulldoc/html/css
  /usr/share/doc/ruby-haml/yardoc/js -> 
../../../yard/templates/default/fulldoc/html/js

The yard package (in sid) does not (or no longer) provide
/usr/share/yard/templates/default/fulldoc/html/*


cheers,

Andreas


ruby-haml_4.0.7-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#857821: ruby-rails-assets-punycode: broken symlink: /usr/share/ruby-rails-assets-punycode/app/assets/javascripts/punycode/punycode.js -> ../../../../../javascript/punycode/punycode.js

[Andreas Beckmann]

Package: ruby-rails-assets-punycode
Version: 1.3.2-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m39.6s ERROR: FAIL: Broken symlinks:
  
/usr/share/ruby-rails-assets-punycode/app/assets/javascripts/punycode/punycode.js
 -> ../../../../../javascript/punycode/punycode.js


Are you missing a Depends/Recommends/Suggests: libjs-punycode ?


cheers,

Andreas


ruby-rails-assets-punycode_1.3.2-2.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#857823: ruby-rails-assets-jquery-fullscreen: broken symlink: /usr/share/ruby-rails-assets-jquery-fullscreen/app/assets/javascripts/jquery-fullscreen/jquery.fullscreen-min.js -> ../../.

[Andreas Beckmann]

Package: ruby-rails-assets-jquery-fullscreen
Version: 1.1.4~dfsg-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m35.3s ERROR: FAIL: Broken symlinks:
  
/usr/share/ruby-rails-assets-jquery-fullscreen/app/assets/javascripts/jquery-fullscreen/jquery.fullscreen-min.js
 -> ../../../../../javascript/jquery-fullscreen/jquery.fullscreen.min.js

There is only /usr/share/javascript/jquery-fullscreen/jquery.fullscreen.js
in libjs-jquery-fullscreen, but no minified variant.


cheers,

Andreas


ruby-rails-assets-jquery-fullscreen_1.1.4~dfsg-2.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#857967: gitlab: postinst chokes on comments locally added to the configuration files

[Andreas Beckmann]

Package: gitlab
Version: 8.13.11+dfsg-2
Severity: serious

Hi,

the postinst uses several

  export $(cat $conffile)

constructs which are very fragile to the file content. This breaks on
comments, quoted multi-word strings, and probably many more things.

Since adding comments while making local modifications to configuration
files is quite common, an innocent change can easily break future
updates.

Here I just duplicated a line in /etc/gitlab/gitlab-debian.conf and
commented out the copy:

# DEBIAN_FRONTEND=noninteractive apt-get install gitlab --reinstall
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 6 not upgraded.
Need to get 0 B/26.4 MB of archives.
After this operation, 0 B of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 45601 files and directories currently installed.)
Preparing to unpack .../gitlab_8.13.11+dfsg-5_all.deb ...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of stop.
Unpacking gitlab (8.13.11+dfsg-5) over (8.13.11+dfsg-5) ...
/var/lib/dpkg/info/gitlab.postrm: 21: export: #gitlab_yml_example: bad variable 
name
dpkg: warning: subprocess old post-removal script returned error exit status 2
dpkg: trying script from the new package instead ...
/var/lib/dpkg/tmp.ci/postrm: 21: export: #gitlab_yml_example: bad variable name
dpkg: error processing archive 
/var/cache/apt/archives/gitlab_8.13.11+dfsg-5_all.deb (--unpack):
 subprocess new post-removal script returned error exit status 2
/var/lib/dpkg/tmp.ci/postrm: 21: export: #gitlab_yml_example: bad variable name
dpkg: error while cleaning up:
 subprocess new post-removal script returned error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/gitlab_8.13.11+dfsg-5_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


IMO, the correct solution would be
* use sourcing ('.') to load the content
* explicitly export the variables that need to be exported in the postinst


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#857967: closed by Pirate Praveen (Bug#857967: fixed in gitlab 8.13.11+dfsg-6)

[Andreas Beckmann]

On 2017-03-17 19:06, Debian Bug Tracking System wrote:
>  gitlab (8.13.11+dfsg-6) unstable; urgency=medium
>  .
>* Improve configuration file parsing by using source (Closes: #857967)

I checked the diff and it looks good, thanks.
piuparts didn't test the package, yet, and I don't plan to do manual
checks. :-)

You'll need to reopen the unblock bug and provide another debdiff.
And you probably can close the tech-ctte bug #857257.


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#858521: diaspora-common: does 'rm -rf /' on purge

[Andreas Beckmann]

Package: diaspora-common
Version: 0.6.3.0+debian3
Severity: critical
Justification: breaks the whole system
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package makes havoc in the
chroot.

>From the attached log (scroll to the bottom...):

1m47.3s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpOwZDY2', 'dpkg', 
'--purge', 'diaspora-common']
1m48.1s DUMP: 
  (Reading database ... 4707 files and directories currently installed.)
  Purging configuration files for diaspora-common (0.6.3.0+debian3) ...
  /var/lib/dpkg/info/diaspora-common.postrm: 63: 
/var/lib/dpkg/info/diaspora-common.postrm: rm: not found
  dpkg: error processing package diaspora-common (--purge):
   subprocess installed post-removal script returned error exit status 127
  Errors were encountered while processing:
   diaspora-common
1m48.1s DEBUG: Command failed (status=1), but ignoring error: ['chroot', 
'/tmp/piupartss/tmpOwZDY2', 'dpkg', '--purge', 'diaspora-common']
1m48.1s INFO: Running scripts post_purge
1m48.1s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpOwZDY2', 
'tmp/scripts/post_purge_exceptions']
1m48.1s DUMP: 
  chroot: failed to run command 'tmp/scripts/post_purge_exceptions': No such 
file or directory
1m48.1s ERROR: Command failed (status=127): ['chroot', 
'/tmp/piupartss/tmpOwZDY2', 'tmp/scripts/post_purge_exceptions']


This very much looks like an 'rm -rf /' in the chroot ... rm is gone, sh is 
gone, ...


cheers,

Andreas


diaspora-common_0.6.3.0+debian3.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#858954: diaspora-common: unowned directories after purge: /var/cache/diaspora/, /var/lib/diaspora-common/, /var/log/diaspora/

[Andreas Beckmann]

Package: diaspora-common
Version: 0.6.3.0+debian4
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned
directories on the system after purge, which is a violation of
policy 6.8:

https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

The maintainer scripts create (and later remove) a file in that
directory. Manual directory removal may be not appropriate as this
directory is shared between several packages.

If the package would ship this as an empty directory, dpkg would take
care of the creation and removal (if it's empty).

>From the attached log (scroll to the bottom...):

2m15.4s ERROR: FAIL: Package purging left files on system:
  /var/cache/diaspora/   not owned
  /var/lib/diaspora-common/  not owned
  /var/log/diaspora/ not owned


cheers,

Andreas


diaspora-common_0.6.3.0+debian4.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#856720: diaspora{, -installer}: fails to install: Errno::EEXIST: File exists @ dir_s_mkdir - /usr/share/diaspora/tmp

[Andreas Beckmann]

Followup-For: Bug #856720
Control: found -1 0.6.3.0+debian4

Hi,

and there we go again ...

[...]
  Precompiling assets...
  W, [2017-03-30T07:12:27.702004 #19736]  WARN -- : You are setting a key that 
conflicts with a built-in method OmniAuth::AuthHash::InfoHash#name defined at 
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/auth_hash.rb:34.
 This can cause unexpected behavior when accessing the key via as a property. 
You can still access the key via the #[] method.
  Expected string default value for '--serializer'; got true (boolean)
  Rack::SSL is enabled
  rake aborted!
  Errno::EEXIST: File exists @ dir_s_mkdir - /usr/share/diaspora/tmp
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/sprockets/cache/file_store.rb:25:in
 `[]='
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/sprockets/caching.rb:34:in
 `cache_set'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/sprockets/caching.rb:92:in
 `cache_set_hash'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/sprockets/caching.rb:63:in
 `cache_asset'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/sprockets/index.rb:93:in
 `build_asset'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/sprockets/base.rb:287:in
 `find_asset'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/sprockets/index.rb:61:in
 `find_asset'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/sprockets/manifest.rb:211:in
 `block in find_asset'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/sprockets/manifest.rb:257:in
 `benchmark'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/sprockets/manifest.rb:210:in
 `find_asset'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/sprockets/manifest.rb:119:in
 `block in compile'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/sprockets/manifest.rb:118:in
 `each'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/sprockets/manifest.rb:118:in
 `compile'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-rails-2.3.3/lib/sprockets/rails/task.rb:70:in
 `block (3 levels) in define'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-2.12.4/lib/rake/sprocketstask.rb:146:in
 `with_logger'
  
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sprockets-rails-2.3.3/lib/sprockets/rails/task.rb:69:in
 `block (2 levels) in define'
  /usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/rake-11.3.0/exe/rake:27:in 
`'
  Tasks: TOP => assets:precompile
  (See full trace by running task with --trace)
  dpkg: error processing package diaspora-installer (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   diaspora-installer


Andreas


diaspora-installer_0.6.3.0+debian4.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#861040: camping: broken symlink: /usr/share/doc/camping/rdoc/fonts/Lato-RegularItalic.ttf -> ../../../../fonts/truetype/lato/Lato-RegularItalic.ttf

[Andreas Beckmann]

Package: camping
Version: 2.1.580-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m47.8s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/camping/rdoc/fonts/Lato-RegularItalic.ttf -> 
../../../../fonts/truetype/lato/Lato-RegularItalic.ttf

   ^^^

The fonts-lato ships /usr/share/fonts/truetype/lato/Lato-Italic.ttf
instead.


cheers,

Andreas


camping_2.1.580-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#861676: ruby-prof: broken symlink: /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> ../../../fonts/truetype/lato/Lato-RegularItalic.ttf

[Andreas Beckmann]

Package: ruby-prof
Version: 0.16.2+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m20.4s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> 
../../../fonts/truetype/lato/Lato-RegularItalic.ttf

^^

The fonts-lato package ships

/usr/share/fonts/truetype/lato/Lato-Italic.ttf
   ^^^
instead.


cheers,

Andreas


ruby-prof_0.16.2+dfsg-2.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#861676: ruby-prof: broken symlink: /usr/share/doc/ruby-prof/fonts/Lato-RegularItalic.ttf -> ../../../fonts/truetype/lato/Lato-RegularItalic.ttf

[Andreas Beckmann]

On 2017-05-02 20:02, Antonio Terceiro wrote:
> Can you clarify exactly why you think a dangling symlink should warrant
> severity serious?

If the target is supposed to be there (because there is a
Depends: target-shipping-package), usually something will be broken if
the link was messed up. If the target is clearly optional (often
indicated by using Suggests: target-shipping-package), some missing
feature will not break stuff. And if I'm unsure, I start with higher
severity. In this case I missed that there was a /doc/ in the path ...
so downgrading is fine.


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#866862: diaspora-installer: installs world-writable ruby libraries

[Andreas Beckmann]

Package: diaspora-installer
Version: 0.6.6.0+debian1
Severity: grave
Tags: security
Justification: user security hole
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package installs
world-writable files, including a bunch of .rb scripts, allowing
unprivileged local users to "customize" your diaspora experience.

Since this is a downloader package, it needs to sanitize the
stuff it downloads and installs from the net.

>From the attached log (scroll to the bottom...):

  ERROR: BAD PERMISSIONS
  -rw-rw-rw- 1 diaspora nogroup 1935 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/configurate-0.3.1/lib/configurate/lookup_chain.rb
  -rw-rw-rw- 1 diaspora nogroup  154 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/.gitignore
  -rw-rw-rw- 1 diaspora nogroup  242 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/.travis.yml
  -rw-rw-rw- 1 diaspora nogroup   98 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/Gemfile
  -rw-rw-rw- 1 diaspora nogroup 1069 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/LICENSE.txt
  -rw-rw-rw- 1 diaspora nogroup 3354 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/README.md
  -rw-rw-rw- 1 diaspora nogroup  233 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/Rakefile
  -rw-rw-rw- 1 diaspora nogroup  918 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/lib/request_store.rb
  -rw-rw-rw- 1 diaspora nogroup  233 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/lib/request_store/middleware.rb
  -rw-rw-rw- 1 diaspora nogroup  785 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/lib/request_store/railtie.rb
  -rw-rw-rw- 1 diaspora nogroup   44 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/lib/request_store/version.rb
  -rw-rw-rw- 1 diaspora nogroup  943 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/request_store.gemspec
  -rw-rw-rw- 1 diaspora nogroup  981 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/test/middleware_test.rb
  -rw-rw-rw- 1 diaspora nogroup 1607 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/test/request_store_test.rb
  -rw-rw-rw- 1 diaspora nogroup  267 Jun 29 20:22 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/request_store-1.3.2/test/test_helper.rb
  -rw-rw-rw- 1 diaspora nogroup 3255 Jun 29 20:24 
/var/lib/diaspora/vendor/bundle/ruby/2.3.0/gems/twitter-text-1.14.5/README.md


cheers,

Andreas


diaspora-installer_0.6.6.0+debian1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#866877: diaspora: fails on being triggered

[Andreas Beckmann]

Package: diaspora
Version: 0.6.0.1+debian-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed when
triggered.

>From the attached log (scroll to the bottom...):

  Processing triggers for libc-bin (2.24-12) ...
  Processing triggers for diaspora (0.6.0.1+debian-1) ...
  /var/lib/dpkg/info/diaspora.postinst: 38: 
/var/lib/dpkg/info/diaspora.postinst: -e: not found
  postinst called with unknown argument `triggered'
  dpkg: error processing package diaspora (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


diaspora_0.6.0.1+debian-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#867031: schleuder: fails to upgrade wheezy -> jessie -> stretch -> buster

[Andreas Beckmann]

Package: schleuder
Version: 3.1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy' to 'jessie' to 'stretch' to 'buster'.
It installed fine in 'wheezy', and upgraded to 'jessie' and 'stretch'
successfully, but then the upgrade to 'buster' failed.

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../52-schleuder_3.1.1-1_all.deb ...
  mv: cannot stat '/var/lib/schleuder/*': No such file or directory
  dpkg: error processing archive 
/tmp/apt-dpkg-install-bo3dQQ/52-schleuder_3.1.1-1_all.deb (--unpack):
   subprocess new pre-installation script returned error exit status 1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-bo3dQQ/52-schleuder_3.1.1-1_all.deb


Since there was no schleuder in jessie and stretch, this is
effectively an upgrade from 2.2.1-2+deb7u1 to 3.1.1-1


cheers,


Andreas


schleuder_3.1.1-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

pkg-ruby-extras-maintainers@lists.alioth.debian.org

[Andreas Beckmann]

On Sat, 8 Jul 2017 08:28:17 +0200 Lucas Nussbaum  wrote:
> Source: ruby-rest-client
> Version: 1.8.0-3
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170707 qa-ftbfs
> Justification: FTBFS on amd64

Hi Lucas,

you files a bunch of ruby2.3 FTBFS bugs recently tagged "stretch sid".
Did you mean "buster sid" or "stretch buster sid"?

You probly need to update some scripts :-)


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#868839: ruby-mustermann, ruby-mustermann19: error when trying to install together

[Andreas Beckmann]

Package: ruby-mustermann,ruby-mustermann19
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1.0.0-2
Control: found -1 0.4.3+git20160621-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package ruby-mustermann19.
  Preparing to unpack .../ruby-mustermann19_0.4.3+git20160621-1_all.deb ...
  Unpacking ruby-mustermann19 (0.4.3+git20160621-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-mustermann19_0.4.3+git20160621-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/ruby/vendor_ruby/mustermann/ast/boundaries.rb', which is also in 
package ruby-mustermann 1.0.0-2
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-mustermann19_0.4.3+git20160621-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

usr/lib/ruby/vendor_ruby/mustermann.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/boundaries.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/compiler.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/expander.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/node.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/param_scanner.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/parser.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/pattern.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/template_generator.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/transformer.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/translator.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/validation.rb
usr/lib/ruby/vendor_ruby/mustermann/caster.rb
usr/lib/ruby/vendor_ruby/mustermann/composite.rb
usr/lib/ruby/vendor_ruby/mustermann/equality_map.rb
usr/lib/ruby/vendor_ruby/mustermann/error.rb
usr/lib/ruby/vendor_ruby/mustermann/expander.rb
usr/lib/ruby/vendor_ruby/mustermann/extension.rb
usr/lib/ruby/vendor_ruby/mustermann/identity.rb
usr/lib/ruby/vendor_ruby/mustermann/mapper.rb
usr/lib/ruby/vendor_ruby/mustermann/pattern.rb
usr/lib/ruby/vendor_ruby/mustermann/pattern_cache.rb
usr/lib/ruby/vendor_ruby/mustermann/regexp.rb
usr/lib/ruby/vendor_ruby/mustermann/regexp_based.rb
usr/lib/ruby/vendor_ruby/mustermann/regular.rb
usr/lib/ruby/vendor_ruby/mustermann/simple_match.rb
usr/lib/ruby/vendor_ruby/mustermann/sinatra.rb
usr/lib/ruby/vendor_ruby/mustermann/to_pattern.rb
usr/lib/ruby/vendor_ruby/mustermann/version.rb


This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


ruby-mustermann=1.0.0-2_ruby-mustermann19=0.4.3+git20160621-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#870293: gitlab: fails to install: Could not find gem 'net-ssh (>= 3.0.1, ~> 3.0)'

[Andreas Beckmann]

Package: gitlab
Version: 8.13.11+dfsg1-9
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package gitlab.
  (Reading database ... 
(Reading database ... 33615 files and directories currently installed.)
  Preparing to unpack .../gitlab_8.13.11+dfsg1-9_all.deb ...
  Unpacking gitlab (8.13.11+dfsg1-9) ...
  Setting up gitlab (8.13.11+dfsg1-9) ...
  Creating/updating gitlab user account...
  adduser: Warning: The home directory `/var/lib/gitlab' does not belong to the 
user you are currently creating.
  Making gitlab owner of /var/lib/gitlab...
  [ESC][31mCould not find gem 'net-ssh (>= 3.0.1, ~> 3.0)' in any of the gem 
sources listed
  in your Gemfile.[ESC][0m
  dpkg: error processing package gitlab (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   gitlab


cheers,

Andreas


gitlab_8.13.11+dfsg1-9.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#870410: gitlab: fails to install: could not find compatible versions for gem "nokogiri"

[Andreas Beckmann]

Package: gitlab
Version: 8.13.11+dfsg1-10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package gitlab.
  (Reading database ... 
(Reading database ... 33761 files and directories currently installed.)
  Preparing to unpack .../gitlab_8.13.11+dfsg1-10_all.deb ...
  Unpacking gitlab (8.13.11+dfsg1-10) ...
  Setting up gitlab (8.13.11+dfsg1-10) ...
  Creating/updating gitlab user account...
  adduser: Warning: The home directory `/var/lib/gitlab' does not belong to the 
user you are currently creating.
  Making gitlab owner of /var/lib/gitlab...
  [ESC][31mBundler could not find compatible versions for gem "nokogiri":
In Gemfile:
  omniauth-cas3 (>= 1.1.2, ~> 1.1) was resolved to 1.1.4, which depends on
nokogiri (>= 1.7.1, ~> 1.7)
  
  truncato (~> 0.7.8) was resolved to 0.7.8, which depends on
nokogiri (~> 1.6.1)
  
  Could not find gem 'nokogiri (~> 1.6.1)', which is required by gem
  'omniauth-cas3 (>= 1.1.2, ~> 1.1)', in any of the sources.[ESC][0m
  dpkg: error processing package gitlab (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   gitlab
  E: Sub-process /usr/bin/dpkg returned an error code (1)


cheers,

Andreas


gitlab_8.13.11+dfsg1-10.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#870684: gitlab: fails to install: could not find compatible versions for gem "mime-types"

[Andreas Beckmann]

Package: gitlab
Version: 8.13.11+dfsg1-10
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package gitlab.
  (Reading database ... 
(Reading database ... 33760 files and directories currently installed.)
  Preparing to unpack .../gitlab_8.13.11+dfsg1-10_all.deb ...
  Unpacking gitlab (8.13.11+dfsg1-10) ...
  Setting up gitlab (8.13.11+dfsg1-10) ...
  Creating/updating gitlab user account...
  adduser: Warning: The home directory `/var/lib/gitlab' does not belong to the 
user you are currently creating.
  Making gitlab owner of /var/lib/gitlab...
  [ESC][31mBundler could not find compatible versions for gem "mime-types":
In Gemfile:
  fog-azure (~> 0.0) was resolved to 0.0.2, which depends on
azure (~> 0.6) was resolved to 0.7.9, which depends on
  mime-types (< 4.0, >= 1)
  
  carrierwave (~> 0.10.0) was resolved to 0.10.0, which depends on
mime-types (>= 1.16)
  
  github-linguist (~> 4.7) was resolved to 4.7.2, which depends on
mime-types (>= 1.19)
  
  gollum-rugged_adapter (~> 0.4.2) was resolved to 0.4.2, which depends on
mime-types (>= 1.15)
  
  gitlab-flowdock-git-hook (>= 1.0.1, ~> 1.0) was resolved to 1.0.1, which
  depends on
grit (>= 2.4.1) was resolved to 2.5.0, which depends on
  mime-types (~> 2.6)[ESC][0m
  dpkg: error processing package gitlab (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   gitlab


cheers,

Andreas


gitlab_8.13.11+dfsg1-10.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#870841: obs-server: fails to install: ln: failed to create symbolic link '/etc/systemd/system/multi-user.target.wants/obsscheduler@i586.service': No such file or directory

[Andreas Beckmann]

Package: obs-server
Version: 2.7.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package obs-server.
  (Reading database ... 
(Reading database ... 9640 files and directories currently installed.)
  Preparing to unpack .../obs-server_2.7.4-1_all.deb ...
  Unpacking obs-server (2.7.4-1) ...
  Setting up obs-server (2.7.4-1) ...
  ln: failed to create symbolic link 
'/etc/systemd/system/multi-user.target.wants/obsscheduler@i586.service': No 
such file or directory
  dpkg: error processing package obs-server (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   obs-server


cheers,

Andreas


obs-server_2.7.4-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#875417: gitlab: fails to install: could not find compatible versions for gem "rack-test"

[Andreas Beckmann]

Package: gitlab
Version: 8.13.11+dfsg1-11
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package gitlab.
  (Reading database ... 
(Reading database ... 33745 files and directories currently installed.)
  Preparing to unpack .../gitlab_8.13.11+dfsg1-11_all.deb ...
  Unpacking gitlab (8.13.11+dfsg1-11) ...
  Setting up gitlab (8.13.11+dfsg1-11) ...
  Creating/updating gitlab user account...
  adduser: Warning: The home directory `/var/lib/gitlab' does not belong to the 
user you are currently creating.
  Making gitlab owner of /var/lib/gitlab...
  [ESC][31mBundler could not find compatible versions for gem "rack-test":
In Gemfile:
  rails (>= 4.2.7.1, ~> 4.2) was resolved to 4.2.9, which depends on
actionpack (= 4.2.9) was resolved to 4.2.9, which depends on
  rack-test (~> 0.6.2)
  
  Could not find gem 'rack-test (~> 0.6.2)', which is required by gem 
'actionpack
  (= 4.2.9)', in any of the sources.[ESC][0m
  dpkg: error processing package gitlab (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   gitlab


cheers,

Andreas


gitlab_8.13.11+dfsg1-11.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#875794: ruby-sentry-raven: /usr/bin/raven already provided by python3-raven

[Andreas Beckmann]

Package: ruby-sentry-raven
Version: 2.5.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ruby-sentry-raven.
  Preparing to unpack .../78-ruby-sentry-raven_2.5.3-1_all.deb ...
  Unpacking ruby-sentry-raven (2.5.3-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-J44vvD/78-ruby-sentry-raven_2.5.3-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/raven', which is also in package python3-raven 
6.0.0-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-J44vvD/78-ruby-sentry-raven_2.5.3-1_all.deb


cheers,

Andreas


python3-raven=6.0.0-1_ruby-sentry-raven=2.5.3-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#875965: ruby-net-ssh: FTBFS - test failures

[Andreas Beckmann]

Source: ruby-net-ssh
Version: 1:4.2.0-1
Severity: serious
Justification: fails to build from source

Hi,

the last upload of ruby-net-ssh does FTBFS:

https://buildd.debian.org/status/fetch.php?pkg=ruby-net-ssh&arch=all&ver=1%3A4.2.0-1&stamp=1505233484&raw=0

┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/<>/debian/ruby-net-ssh/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/ruby-net-ssh/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 -w  "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/test_all.rb" "test/test_buffer.rb" "test/test_buffered_io.rb" 
"test/test_config.rb" "test/test_key_factory.rb" "test/test_known_hosts.rb" 
"test/test_proxy_jump.rb" -v
/<>/test/transport/test_session.rb:305:in `': 
uninitialized constant Transport::TestSession::Logger (NameError)
from /<>/test/transport/test_session.rb:15:in 
`'
from /<>/test/transport/test_session.rb:13:in `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /<>/test/test_all.rb:11:in `block (2 levels) in '
from /<>/test/test_all.rb:11:in `each'
from /<>/test/test_all.rb:11:in `block in '
from /<>/test/test_all.rb:3:in `chdir'
from /<>/test/test_all.rb:3:in `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:15:in `block in 
'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `select'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:4:in `'
rake aborted!
Command failed with status (1): [ruby -w  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_all.rb" 
"test/test_buffer.rb" "test/test_buffered_io.rb" "test/test_config.rb" 
"test/test_key_factory.rb" "test/test_known_hosts.rb" "test/test_proxy_jump.rb" 
-v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-net-ssh 
returned exit code 1
debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1


Andreas
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#875970: ruby-fog-aws: FTBFS in experimental - test failures

[Andreas Beckmann]

Source: ruby-fog-aws
Version: 1.4.1-1
Severity: serious
Justification: fails to build from source

Hi,

the last upload of ruby-fog-aws to experimental did FTBFS: 

https://buildd.debian.org/status/fetch.php?pkg=ruby-fog-aws&arch=all&ver=1.4.1-1&stamp=1505064095&raw=0


++  
  Compute::AWS | parsers | describe_images (compute, aws, parser) +  
  AWS::EFS | file systems (aws, efs)   
  tests/requests/efs/file_system_tests.rb
success
AWS::EFS | file systems (aws, efs)
  - has proper format
  
  tests/requests/efs/file_system_tests.rb
  undefined method `group_id' for nil:NilClass (NoMethodError)
tests/requests/efs/file_system_tests.rb:84:in `block (3 levels) in '
tests/helpers/formats_helper.rb:92:in `block in formats'
/usr/lib/ruby/vendor_ruby/shindo.rb:140:in `instance_eval'
/usr/lib/ruby/vendor_ruby/shindo.rb:140:in `assert'
/usr/lib/ruby/vendor_ruby/shindo.rb:116:in `test'
tests/helpers/formats_helper.rb:85:in `formats'
tests/requests/efs/file_system_tests.rb:82:in `block (2 levels) in '
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `instance_eval'
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `tests'
tests/requests/efs/file_system_tests.rb:6:in `block in '
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `instance_eval'
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `tests'
/usr/lib/ruby/vendor_ruby/shindo.rb:38:in `initialize'
/usr/lib/ruby/vendor_ruby/shindo.rb:13:in `new'
/usr/lib/ruby/vendor_ruby/shindo.rb:13:in `tests'
tests/requests/efs/file_system_tests.rb:1:in `'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:61:in `load'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:61:in `block (2 levels) in 
run_in_thread'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:58:in `each'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:58:in `block in run_in_thread'
++  
  tests/requests/efs/file_system_tests.rb
  undefined method `group_id' for nil:NilClass (NoMethodError)
tests/requests/efs/file_system_tests.rb:98:in `block (3 levels) in '
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:7:in `block in wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `loop'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `wait_for'
tests/requests/efs/file_system_tests.rb:98:in `block (2 levels) in '
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `instance_eval'
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `tests'
tests/requests/efs/file_system_tests.rb:6:in `block in '
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `instance_eval'
/usr/lib/ruby/vendor_ruby/shindo.rb:79:in `tests'
/usr/lib/ruby/vendor_ruby/shindo.rb:38:in `initialize'
/usr/lib/ruby/vendor_ruby/shindo.rb:13:in `new'
/usr/lib/ruby/vendor_ruby/shindo.rb:13:in `tests'
tests/requests/efs/file_system_tests.rb:1:in `'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:61:in `load'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:61:in `block (2 levels) in 
run_in_thread'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:58:in `each'
/usr/lib/ruby/vendor_ruby/shindo/bin.rb:58:in `block in run_in_thread'
An error occurred outside of a test
rake aborted!
Command failed with status (1): [export FOG_MOCK=true && shindont...]
/<>/Rakefile:7:in `block in '
Tasks: TOP => test
(See full trace by running task with --trace)
debian/rules:18: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#876231: ruby-nmatrix: FTBFS with GCC 7: error: call of overloaded 'abs(nm::Rational&)' is ambiguous

[Andreas Beckmann]

Package: ruby-nmatrix
Version: 0.1.0~rc3-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

ruby-nmatrix FTBFS (at least) since GCC 7 was made the default compiler:

In file included from math.cpp:125:0:
math/idamax.h: In instantiation of 'int nm::math::idamax(size_t, DType*, int) 
[with DType = nm::Rational; size_t = long unsigned int]':
math/getrf.h:153:44:   required from 'int nm::math::getrf_nothrow(int, int, 
DType*, int, int*) [with bool RowMajor = true; DType = nm::Rational]'
math/getrf.h:211:37:   required from 'int nm::math::getrf(CBLAS_ORDER, int, 
int, DType*, int, int*) [with DType = nm::Rational]'
math/getrf.h:234:22:   required from 'int nm::math::clapack_getrf(CBLAS_ORDER, 
int, int, void*, int, int*) [with DType = nm::Rational]'
math.cpp:1295:3:   required from here
math/idamax.h:60:15: error: call of overloaded 'abs(nm::Rational&)' 
is ambiguous
 dmax = abs(dx[0]);
~~~^~~
In file included from /usr/include/c++/7/cstdlib:75:0,
 from /usr/include/c++/7/bits/stl_algo.h:59,
 from /usr/include/c++/7/algorithm:62,
 from math.cpp:116:
/usr/include/stdlib.h:735:12: note: candidate: int abs(int)
 extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
^~~
In file included from /usr/include/c++/7/cstdlib:77:0,
 from /usr/include/c++/7/bits/stl_algo.h:59,
 from /usr/include/c++/7/algorithm:62,
 from math.cpp:116:
/usr/include/c++/7/bits/std_abs.h:56:3: note: candidate: long int std::abs(long 
int)
   abs(long __i) { return __builtin_labs(__i); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:61:3: note: candidate: long long int 
std::abs(long long int)
   abs(long long __x) { return __builtin_llabs (__x); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:70:3: note: candidate: constexpr double 
std::abs(double)
   abs(double __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:74:3: note: candidate: constexpr float 
std::abs(float)
   abs(float __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:78:3: note: candidate: constexpr long double 
std::abs(long double)
   abs(long double __x)
   ^~~


Full log attached.

Andreas


ruby-nmatrix_0.1.0~rc3-2.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#876491: ruby-openid-connect: FTBFS: Could not find 'rack-oauth2' (>= 1.6.1) - did find: [rack-oauth2-1.4.0] (Gem::LoadError)

[Andreas Beckmann]

Source: ruby-openid-connect
Version: 1.1.3-1
Severity: serious
Justification: fails to build from source

Hi,

the last upload of ruby-openid-connect did FTBFS:

https://buildd.debian.org/status/fetch.php?pkg=ruby-openid-connect&arch=all&ver=1.1.3-1&stamp=1505764236&raw=0

This looks like an insufficiently versioned
  B-D: ruby-rack-oauth2 (>= 1.3.1)


┌──┐
│ Checking Rubygems dependency resolution on ruby2.3   │
└──┘

Invalid gemspec in [openid_connect.gemspec]: No such file or directory - git
GEM_PATH=debian/ruby-openid-connect/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -e gem\ \"openid_connect\"
/usr/lib/ruby/2.3.0/rubygems/dependency.rb:319:in `to_specs': Could not find 
'rack-oauth2' (>= 1.6.1) - did find: [rack-oauth2-1.4.0] (Gem::LoadError)
Checked in 
'GEM_PATH=debian/ruby-openid-connect/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all',
 execute `gem env` for more information
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1439:in `block in 
activate_dependencies'
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in `each'
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1428:in 
`activate_dependencies'
from /usr/lib/ruby/2.3.0/rubygems/specification.rb:1410:in `activate'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
in gem'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in 
`synchronize'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
from -e:1:in `'
activemodel (4.2.9)
activesupport (4.2.9)
addressable (2.5.1)
atomic (1.1.16)
attr_required (1.0.0)
bigdecimal (1.2.8)
bindata (2.3.5)
blankslate (3.1.3)
builder (3.2.2)
cookiejar (0.3.3)
crack (0.4.3)
did_you_mean (1.0.0)
diff-lcs (1.3)
domain_name (0.5.20160216)
em-http-request (1.1.5)
em-socksify (0.3.1)
escape_utils (1.1.0)
ethon (0.9.0)
eventmachine (1.0.7)
ffi (1.9.10)
hashdiff (0.2.3)
http-cookie (1.0.2)
http_parser.rb (0.6.0)
httpclient (2.8.3)
i18n (0.7.0)
io-console (0.4.5)
json (2.1.0, 1.8.3)
json-jwt (1.7.2)
mail (2.6.4)
mime-types (3.1)
mime-types-data (3.2015.1120)
minitest (5.10.3)
multi_json (1.12.1)
net-telnet (0.1.1)
power_assert (0.2.7)
psych (2.1.0)
public_suffix (2.0.5)
rack (1.6.4)
rack-oauth2 (1.4.0)
rake (12.0.0)
rdoc (4.2.1)
rspec (3.5.0)
rspec-core (3.5.3)
rspec-expectations (3.5.0)
rspec-its (1.2.0)
rspec-mocks (3.5.0)
rspec-support (3.5.0)
safe_yaml (1.0.4)
securecompare (1.0.0)
swd (1.0.1)
test-unit (3.2.5)
thread_order (1.1.0)
thread_safe (0.3.5)
typhoeus (1.1.2)
tzinfo (1.2.3)
unf (0.1.4)
unf_ext (0.0.7.4)
url_safe_base64 (0.2.2)
validate_email (0.1.6)
validate_url (1.0.2)
webfinger (1.0.2)
webmock (3.0.1)
ERROR: Test "ruby2.3" failed. Exiting.


Andreas
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#877257: ruby-grape: FTBFS ERROR: Test "ruby2.3" failed.

[Andreas Beckmann]

Source: ruby-grape
Version: 0.19.2-2
Severity: serious
Justification: fails to build from source

Hi,

ruby-grape/experimental FTBFS in a current sid+experimental environment.
Please see the attached build log for details.


Andreas


ruby-grape_0.19.2-2.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#877274: ruby-psych: broken symlink: /usr/lib/ruby/vendor_ruby/psych.jar -> ../../../share/java/psych.jar

[Andreas Beckmann]

Package: ruby-psych
Version: 2.2.4-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m27.6s ERROR: FAIL: Broken symlinks:
  /usr/lib/ruby/vendor_ruby/psych.jar -> ../../../share/java/psych.jar

Is ruby-psych missing a dependency on libpsych-java?


cheers,

Andreas


ruby-psych_2.2.4-6.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#877278: ruby-licensee: broken symlink: /usr/share/doc/ruby-licensee/README.md -> docs/README.md

[Andreas Beckmann]

Package: ruby-licensee
Version: 8.9.0-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

1m12.9s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/ruby-licensee/README.md -> docs/README.md


cheers,

Andreas


ruby-licensee_8.9.0-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#884514: ruby-fog-aws: fails to upgrade from 'sid' - trying to overwrite /usr/lib/ruby/vendor_ruby/fog/aws/service_mapper.rb

[Andreas Beckmann]

Package: ruby-fog-aws
Version: 2.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../ruby-fog-aws_2.0.0-1_all.deb ...
  Unpacking ruby-fog-aws (2.0.0-1) over (0.12.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-fog-aws_2.0.0-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/fog/aws/service_mapper.rb', 
which is also in package ruby-fog 1.38.0-1
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-fog-aws_2.0.0-1_all.deb


cheers,

Andreas


ruby-fog=1.38.0-1_ruby-fog-aws=2.0.0-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#884971: ruby-faraday: FTBFS in experimental: 2 tests failed

[Andreas Beckmann]

Source: ruby-faraday
Version: 0.13.1-1
Severity: serious
Justification: fails to build from source

Hi,

ruby-faraday/experimental recently started to FTBFS:

┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-faraday/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 debian/ruby-tests.rb
running test/adapters/default_test.rb test/adapters/em_http_test.rb 
test/adapters/em_synchrony_test.rb test/adapters/excon_test.rb 
test/adapters/logger_test.rb test/adapters/httpclient_test.rb 
test/adapters/net_http_persistent_test.rb test/adapters/net_http_test.rb 
test/adapters/rack_test.rb test/adapters/test_middleware_test.rb
Run options: --seed 10225

# Running:

.S...S..S.E..S...SS...E...F...F

Finished in 12.063750s, 21.1377 runs/s, 33.4888 assertions/s.

  1) Error:
Adapters::HttpclientTest#test_GET_with_body:
Faraday::ClientError: the server responded with status 411

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/response/raise_error.rb:13:in
 `on_complete'

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/response.rb:9:in
 `block in call'

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/response.rb:61:in
 `on_complete'

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/response.rb:8:in
 `call'

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/request/url_encoded.rb:15:in
 `call'

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/request/multipart.rb:15:in
 `call'

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/rack_builder.rb:141:in
 `build_response'

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/connection.rb:387:in
 `run_request'

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/connection.rb:137:in
 `get'
/usr/lib/ruby/2.3.0/forwardable.rb:204:in `get'
/build/ruby-faraday-0.13.1/test/adapters/integration.rb:102:in 
`test_GET_with_body'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:839:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:311:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `each'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest.rb:337:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest.rb:309:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `block in __run'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `map'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `__run'
/usr/lib/ruby/vendor_ruby/minitest.rb:136:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:63:in `block in autorun'

  2) Error:
Adapters::ExconTest#test_GET_with_body:
Faraday::ClientError: the server responded with status 411

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/response/raise_error.rb:13:in
 `on_complete'

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/response.rb:9:in
 `block in call'

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/response.rb:61:in
 `on_complete'

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/response.rb:8:in
 `call'

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/request/url_encoded.rb:15:in
 `call'

/build/ruby-faraday-0.13.1/debian/ruby-faraday/usr/lib/ruby/vendor_ruby/faraday/request/multipart.rb:15:in
 `call'

/build/ruby-faraday-0.13.1/deb

[DRE-maint] Bug#889510: ruby-rspec: FTBFS with ruby2.5

[Andreas Beckmann]

Source: ruby-rspec
Version: 3.5.0c3e0m0s0-1
Severity: serious
Tags: sid buster experimental
Justification: fails to build from source
Control: found -1 3.6.0c0e0m0s0-1~exp1
Control: block 888531 with -1

Hi,

ruby-rspec in both sid and experimental FTBFS due to test failures
with ruby2.5 as the default.

Please see attached sid buildlog for the details of the failures, it's
hard for me to provide a batter excerpt than

  ERROR: Test "ruby2.5" failed. Exiting.


Andreas


ruby-rspec.build.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#657541: ruby-blankslate: fails to upgrade from 'testing' - trying to overwrite ...

[Andreas Beckmann]

Package: ruby-blankslate
Version: 2.1.2.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ruby-blankslate.
  Unpacking ruby-blankslate (from .../ruby-blankslate_2.1.2.4-1_all.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/ruby-blankslate_2.1.2.4-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/blankslate.rb', which is also 
in package ruby-builder 3.0.0-1


cheers,

Andreas


ruby-gettext-rails_2.1.0-2.log.gz
Description: GNU Zip compressed data
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#657477: redmine: fails to install

[Andreas Beckmann]

Package: redmine
Version: 1.3.0+dfsg1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package redmine.
  (Reading database ... 9903 files and directories currently installed.)
  Unpacking redmine (from .../redmine_1.3.0+dfsg1-2_all.deb) ...
  Setting up redmine (1.3.0+dfsg1-2) ...
  dbconfig-common: writing config to 
/etc/dbconfig-common/redmine/instances/default.conf
  
  Creating config file /etc/dbconfig-common/redmine/instances/default.conf with 
new version
  
  Creating config file /etc/redmine/default/database.yml.new with new version
  creating database redmine_default: success.
  verifying database redmine_default exists: success.
  
  Creating config file /etc/redmine/default/database.yml with new version
  NOTE: Gem.source_index is deprecated, use Specification. It will be removed 
on or after 2011-11-01.
  Gem.source_index called from 
/usr/share/redmine/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21.
  rake aborted!
  uninitialized constant Gem::SyckDefaultKey
  
  (See full trace by running task with --trace)
  dpkg: error processing redmine (--configure):
   subprocess installed post-installation script returned error exit status 1
  configured to not write apport reports
  Errors were encountered while processing:
   redmine


cheers,

Andreas


redmine_1.3.0+dfsg1-2.log.gz
Description: GNU Zip compressed data
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#673814: ruby-pdf-writer: fails to upgrade from 'testing' - trying to overwrite /usr/bin/techbook

[Andreas Beckmann]

Package: ruby-pdf-writer
Version: 1.1.8+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ruby-pdf-writer.
  Unpacking ruby-pdf-writer (from .../ruby-pdf-writer_1.1.8+dfsg-2_all.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/ruby-pdf-writer_1.1.8+dfsg-2_all.deb (--unpack):
   trying to overwrite '/usr/bin/techbook', which is also in package 
libpdf-writer-ruby1.8 1.1.8+dfsg-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Preparing to replace libpdf-writer-ruby 1.1.8+dfsg-1 (using 
.../libpdf-writer-ruby_1.1.8+dfsg-2_all.deb) ...
  Unpacking replacement libpdf-writer-ruby ...
  Preparing to replace libpdf-writer-ruby1.8 1.1.8+dfsg-1 (using 
.../libpdf-writer-ruby1.8_1.1.8+dfsg-2_all.deb) ...
  Unpacking replacement libpdf-writer-ruby1.8 ...
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-pdf-writer_1.1.8+dfsg-2_all.deb

cheers,

Andreas


libpdf-writer-ruby_1.1.8+dfsg-2.log.gz
Description: GNU Zip compressed data
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#673984: ruby-activesupport-2.3: fails to upgrade from 'squeeze' - trying to overwrite /usr/lib/ruby/vendor_ruby/active_support/xml_mini.rb

[Andreas Beckmann]

Package: ruby-activesupport-2.3,ruby-activerecord-2.3
Version: 2.3.14-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'sid' fails
because it tries to overwrite files that are owned by other packages
without declaring a Breaks/Replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

This problem is exposed during the upgrade of the 'libgettext-rails-ruby1.8'
package, not by upgrading only the buggy package itself.
In order to have piuparts automatically track this problem, I'll mark
this bug as Affects/Found in the exposing package(s), too.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ruby-activesupport-2.3.
  Unpacking ruby-activesupport-2.3 (from 
.../ruby-activesupport-2.3_2.3.14-3_all.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/ruby-activesupport-2.3_2.3.14-3_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/active_support/xml_mini.rb', 
which is also in package ruby-activesupport-3.2 3.2.3-1
  configured to not write apport reports
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Selecting previously unselected package ruby-activerecord-2.3.
  Unpacking ruby-activerecord-2.3 (from 
.../ruby-activerecord-2.3_2.3.14-1_all.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/ruby-activerecord-2.3_2.3.14-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/active_record/fixtures.rb', 
which is also in package ruby-activerecord 3.2.3-1
  configured to not write apport reports
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)


cheers,

Andreas


libgettext-rails-ruby1.8_2.1.0-2.log.gz
Description: GNU Zip compressed data
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#674009: rdtool-elisp: fails to upgrade from squeeze: ln: failed to create symbolic link `./rd-mode.el': File exists

[Andreas Beckmann]

Package: rdtool-elisp
Version: 0.6.34-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'sid' fails.

>From the attached log (scroll to the bottom...):

  Setting up rdtool-elisp (0.6.34-3) ...
  Installing new version of config file 
/etc/emacs/site-start.d/50rdtool-elisp.el ...
  Install rdtool-elisp for emacs
  Install rdtool-elisp for emacs23
  install/rdtool-elisp: Handling install for emacsen flavor emacs23
  ln: failed to create symbolic link `./rd-mode.el': File exists
  /usr/lib/emacsen-common/packages/install/rdtool-elisp emacs23 emacs23 failed 
at /usr/lib/emacsen-common/lib.pl line 19,  line 1.
  dpkg: error processing rdtool-elisp (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


rdtool-elisp_0.6.34-3.log.gz
Description: GNU Zip compressed data
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#672177: libsdl-ruby: uninstallable in sid

[Andreas Beckmann]

Package: libsdl-ruby
Version: 2.1.1.1-1
Severity: grave
Tags: sid
Justification: renders package unusable
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

* ruby-sdl breaks libsdl-ruby (<< 2.1.1.1-2~)
* libsdl-ruby depends on ruby-sdl via libsdl-ruby1.8

As libsdl-ruby was renamed to ruby-sdl, but there is no transitional
package for libsdl-ruby, maybe libsdl-ruby should be removed from sid?


Cheers,

Andreas




___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#672251: haml-elisp: fails to upgrade from squeeze

[Andreas Beckmann]

Package: haml-elisp
Version: 1:3.0.15-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'squeeze'.
It installed fine in 'squeeze', then the upgrade to 'sid' fails.

>From the attached log (scroll to the bottom...):

  Setting up haml-elisp (1:3.0.15-3) ...
  Installing new version of config file /etc/emacs/site-start.d/50haml-elisp.el 
...
  Skipping byte-compilation for emacs: Not supported
  install/haml-elisp: Handling install of emacsen flavor emacs23
  install/haml-elisp: byte-compiling for emacs23
  cp: `haml-mode.el' and `/usr/share/emacs23/site-lisp/haml-elisp/haml-mode.el' 
are the same file
  emacs-package-install: /usr/lib/emacsen-common/packages/install/haml-elisp 
emacs23 emacs23 failed at /usr/lib/emacsen-common/emacs-package-install line 
30,  line 1.
  dpkg: error processing haml-elisp (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


haml-elisp_1:3.0.15-3.log.gz
Description: GNU Zip compressed data
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#672251: haml-elisp: fails to upgrade from squeeze

[Andreas Beckmann]

Source: haml-elisp
Followup-For: Bug #672251

Hi,

found another occurrence during the test of the sass-elisp
package in sid. That should be easier to reproduce.

  Setting up haml-elisp (1:3.0.15-3) ...
  Install haml-elisp for emacs
  Skipping byte-compilation for emacs: Not supported
  Install haml-elisp for emacs23
  install/haml-elisp: Handling install of emacsen flavor emacs23
  install/haml-elisp: byte-compiling for emacs23
  cp: `haml-mode.el' and `/usr/share/emacs23/site-lisp/haml-elisp/haml-mode.el' 
are the same file
  /usr/lib/emacsen-common/packages/install/haml-elisp emacs23 emacs23 failed at 
/usr/lib/emacsen-common/lib.pl line 19,  line 1.
  dpkg: error processing haml-elisp (--configure):
   subprocess installed post-installation script returned error exit status 1


Andreas


sass-elisp_3.0.15-1.log.gz
Description: GNU Zip compressed data
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#675365: chef: unowned directory after purge: /var/lib/chef/cookbook_index/

[Andreas Beckmann]

Package: chef
Version: 0.10.10-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned
directories on the system after purge, which is a violation of
policy 6.8:

http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

If the package would ship this as an empty directory, dpkg would take
care of the creation and removal.

>From the attached log (scroll to the bottom...):

0m40.5s ERROR: FAIL: Package purging left files on system:
  /var/lib/chef/ not owned
  /var/lib/chef/cookbook_index/  not owned


cheers,

Andreas


chef_0.10.10-1.log.gz
Description: GNU Zip compressed data
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#675370: libchef-ruby, libchef-ruby1.8: uninstallable in sid

[Andreas Beckmann]

Package: libchef-ruby,libchef-ruby1.8
Version: 0.10.10-1
Severity: grave
Tags: sid
Justification: renders package unusable
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

Package: libchef-ruby
Version: 0.10.10-1
Depends: chef

Package: libchef-ruby1.8
Version: 0.10.10-1
Depends: chef

Package: chef
Version: 0.10.10-1
Replaces: libchef-ruby, libchef-ruby1.8
Provides: libchef-ruby, libchef-ruby1.8
Conflicts: libchef-ruby, libchef-ruby1.8

The chef package needs to use versioned Breaks/Replaces on the old
versions of libchef-ruby and libchef-ruby1.8. The transitional packages
must be installable in wheezy and may be removed in wheezy+1.
Unstallable transitional packages will block the transition to testing.


Cheers,

Andreas



___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#675365: chef: unowned directory after purge: /var/lib/chef/

[Andreas Beckmann]

Package: chef
Version: 0.10.10-2
Followup-For: Bug #675365

Hi,

/var/lib/chef/ is still there ...

0m42.0s ERROR: FAIL: Package purging left files on system:
  /var/lib/chef/ not owned
 

Andreas


chef_0.10.10-2.log.gz
Description: GNU Zip compressed data
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#676452: bundler: unowned directory after purge: /var/lib/gems/

[Andreas Beckmann]

Package: bundler
Version: 1.1.4-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package left unowned
directories on the system after purge, which is a violation of
policy 6.8:

http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails

Filing this as important as having a piuparts clean archive is a release
goal since lenny.

The maintainer scripts create (and later remove) a file in that
directory. Manual directory removal may be not appropriate as this
directory is shared between several packages.

If the package would ship this as an empty directory, dpkg would take
care of the creation and removal (if it's empty).

>From the attached log (scroll to the bottom...):

0m21.7s ERROR: FAIL: Package purging left files on system:
  /var/lib/gems/ not owned


cheers,

Andreas


bundler_1.1.4-1.log.gz
Description: GNU Zip compressed data
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#679606: Bug #679606: ruby-hpricot and ruby-fast-xs: error when trying to install together

[Andreas Beckmann]

user debian...@lists.debian.org
usertag 679606 piuparts
clone 679606 -1
reassign 679606 ruby-hpricot 0.8.6-2
fixed 679606 0.8.6-3
reassign -1 ruby-fast-xs 0.8.0-2
reopen -1
thanks

cloning and reassigning to ruby-fast-xs which needs to add 
Breaks/Replaces since it takes over some files from ruby-hpricot.

Currently this happens on upgrades:

  Selecting previously unselected package ruby-fast-xs.
  Unpacking ruby-fast-xs (from .../ruby-fast-xs_0.8.0-2_amd64.deb) ...
  dpkg: error processing /var/cache/apt/archives/ruby-fast-xs_0.8.0-2_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/1.8/x86_64-linux/fast_xs.so', 
which is also in package ruby-hpricot 0.8.6-1
  Preparing to replace ruby-hpricot 0.8.6-1 (using 
.../ruby-hpricot_0.8.6-3_amd64.deb) ...
  Unpacking replacement ruby-hpricot ...
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-fast-xs_0.8.0-2_amd64.deb


Andreas



___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#681573: chef-solr: fails to install if policy-rc.d forbids to start services

[Andreas Beckmann]

Package: chef-solr
Version: 10.12.0+dfsg-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install.

>From the attached log (scroll to the bottom...):

[...]
  Setting up rabbitmq-server (2.8.4-1) ...
  Adding group `rabbitmq' (GID 103) ...
  Done.
  Adding system user `rabbitmq' (UID 101) ...
  Adding new user `rabbitmq' (UID 101) with group `rabbitmq' ...
  Not creating home directory `/var/lib/rabbitmq'.
  invoke-rc.d: policy-rc.d denied execution of start.
[...]
  Selecting previously unselected package chef-solr.
  (Reading database ... 16126 files and directories currently installed.)
  Unpacking chef-solr (from .../chef-solr_10.12.0+dfsg-1_all.deb) ...
  Setting up chef-solr (10.12.0+dfsg-1) ...
  Error: unable to connect to node rabbit@myhost: nodedown
  
  DIAGNOSTICS
  ===
  
  nodes in question: [rabbit@myhost]
  
  hosts, their running nodes and ports:
  - myhost: [{rabbitmqctl25570,35477}]
  
  current node details:
  - node name: rabbitmqctl25570@myhost
  - home dir: /var/lib/rabbitmq
  - cookie hash: hc48p+QivmdGXe7/xDH/rQ==
  
  Creating vhost "/chef" ...
  Error: unable to connect to node rabbit@myhost: nodedown
  
  DIAGNOSTICS
  ===
  
  nodes in question: [rabbit@myhost]
  
  hosts, their running nodes and ports:
  - myhost: [{rabbitmqctl25641,49226}]
  
  current node details:
  - node name: rabbitmqctl25641@myhost
  - home dir: /var/lib/rabbitmq
  - cookie hash: hc48p+QivmdGXe7/xDH/rQ==
  
  dpkg: error processing chef-solr (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   chef-solr


cheers,

Andreas


chef-solr_10.12.0+dfsg-1.log.gz
Description: GNU Zip compressed data
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#790537: tested on a clean machine

[Andreas Beckmann]

Control: found -1 0.5.3.0+debian1

On 2015-09-07 12:04, Pirate Praveen wrote:
> tested on jesse and sid machines and everything went fine.

I can still reproduce the problem in piuparts, are you sure you used a
fresh database server installation?

piuparts does its tests with DEBIAN_FRONTEND=noninteractive, so in case
you use debconf prompting (e.g. via dbconfig-common), only the defaults
will be used.


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#803222: RuntimeError: Incorrect MySQL client library version

[Andreas Beckmann]

control: tag -1 sid stretch

On Sat, 31 Oct 2015 13:06:55 -0500 Adam Majer  wrote:
> Furthermore, rebuilding does not fix the bug at root of the
> problem. If MySQL get upgraded to another minor version while keeping
> its soname as is (ie. ABI doesn't change), ruby-mysql will break
> again.

It's not as bad as it initially looks (the message emits
major.minor.patchlevel versions), because only the first two components
of the version (major.minor) are being compared, so it blows up on the
5.5->5.6 switch. The new upstream patchlevel releases frequently
uploaded to (old-)stable do not cause problems.


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#804116: ruby-mousetrap-rails: unhandled symlink to directory conversion: /usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap

[Andreas Beckmann]

Package: ruby-mousetrap-rails
Version: 1.4.6-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> sid

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

3m16.4s ERROR: FAIL: silently overwrites files via directory symlinks:
  
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap/dictionary.js
 (ruby-mousetrap-rails) != /usr/share/javascript/mousetrap/dictionary.js 
(libjs-mousetrap)
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap -> 
../../../../javascript/mousetrap
  /usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap/global.js 
(ruby-mousetrap-rails) != /usr/share/javascript/mousetrap/global.js 
(libjs-mousetrap)
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap -> 
../../../../javascript/mousetrap
  /usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap/pause.js 
(ruby-mousetrap-rails) != /usr/share/javascript/mousetrap/pause.js 
(libjs-mousetrap)
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap -> 
../../../../javascript/mousetrap
  
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap/plugins.js 
(ruby-mousetrap-rails) != /usr/share/javascript/mousetrap/plugins.js 
(libjs-mousetrap)
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap -> 
../../../../javascript/mousetrap
  /usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap/record.js 
(ruby-mousetrap-rails) != /usr/share/javascript/mousetrap/record.js 
(libjs-mousetrap)
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap -> 
../../../../javascript/mousetrap
3m16.4s DEBUG: Starting command: ['debsums', '--root', 
'/tmp/piupartss/tmplyxaro', '-ac']

3m17.2s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /usr/share/javascript/mousetrap/dictionary.js (from 
libjs-mousetrap package)
  debsums: missing file /usr/share/javascript/mousetrap/global.js (from 
libjs-mousetrap package)
  debsums: missing file /usr/share/javascript/mousetrap/pause.js (from 
libjs-mousetrap package)
  debsums: missing file /usr/share/javascript/mousetrap/plugins.js (from 
libjs-mousetrap package)
  debsums: missing file /usr/share/javascript/mousetrap/record.js (from 
libjs-mousetrap package)


cheers,

Andreas


ruby-mousetrap-rails_1.4.6-3.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#804641: ruby-gnome2: FTBFS during arch-indep-only buildd build

[Andreas Beckmann]

Source: ruby-gnome2
Version: 2.2.5-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

ruby-gnome2 FTBFS in the arch:all buildd:

https://buildd.debian.org/status/fetch.php?pkg=ruby-gnome2&arch=all&ver=2.2.5-2&stamp=1447078649

[...]
   debian/rules override_dh_fixperms
make[1]: Entering directory '/«PKGBUILDDIR»'
dh_fixperms
# Remove executable flag from some examples that aren't actually executable.
chmod -x debian/ruby-glib2/usr/share/doc/ruby-glib2/examples/type-register*.rb
chmod: cannot access 
'debian/ruby-glib2/usr/share/doc/ruby-glib2/examples/type-register*.rb': No 
such file or directory
debian/rules:27: recipe for target 'override_dh_fixperms' failed
make[1]: *** [override_dh_fixperms] Error 1
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:4: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Looks like this override needs to be
override_dh_fixperms-arch:
instead.


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#809560: ruby-activerecord-session-store: File conflict with ruby-devise

[Andreas Beckmann]

Control: severity -1 serious
Control: clone -1 -2
Control: reopen -2
Control: reassign -1 ruby-devise 3.5.2-2
Control: fixed -1 3.5.2-3

This bug needs a fix on the ruby-activerecord-session-store side, too,
by adding
  Breaks+Replaces: ruby-devise (<< 3.5.2-3~)
otherwise you can still run into it on stretch->sid upgrades.

Cloning+reassinging this bug accordingly.


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#808956: ruby-hpricot: uninstallable due to file overwrite conflict with direct dependency ruby-fast-xs

[Andreas Beckmann]

Control: retitle -1 ruby-hpricot: package contains fast_xs.so if built with 
DEB_BUILD_OPTIONS=nocheck
Control: tag -1 sid stretch

On Thu, 24 Dec 2015 20:40:28 + (UTC) Thorsten Glaser  wrote:
> Unpacking ruby-hpricot (0.8.6-5+b1) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/ruby-hpricot_0.8.6-5+b1_m68k.deb (--unpack):
>  trying to overwrite 
> '/usr/lib/m68k-linux-gnu/ruby/vendor_ruby/2.2.0/fast_xs.so', which is also in 
> package ruby-fast-xs 0.8.0-3+b1

At a first glance I thought this is m68k specific ... no release
architecture contains the conflicting file.

But it's also reproducible on amd64 if built with nocheck.

debian/ruby-tests.rb contains
  system("find -name fast_xs.so -delete")
which seems to be the wrong place to do this ...


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#806191: ruby-fast-xs: Missing Breaks or Conflicts with ruby-hpricot

[Andreas Beckmann]

On Wed, 25 Nov 2015 10:59:36 -0200 Antonio Terceiro
> according to
> https://packages.debian.org/search?searchon=contents&keywords=fast_xs.so&mode=filename&suite=unstable&arch=any
> sh4 is the only architecture where ruby-hpricot ships that file.

That output is seriously outdated (#810590), or did you see a ruby 2.2.0
path anywhere?


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#812156: dbconfig-common: talks about 'apparently missing Depends on dbconfig-pgqsl packages' which does not exist

[Andreas Beckmann]

No, you didn' get the point of this bug. Please install the package by
copy+pasting the name from the subject :-)

Andreas

PS: Query Structured Language

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#812951: gitlab: fails to install: gitlab.postinst: sudo: not found

[Andreas Beckmann]

Package: gitlab
Version: 8.4.0+dfsg~rc2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package gitlab.
  (Reading database ... 
(Reading database ... 33018 files and directories currently installed.)
  Preparing to unpack .../gitlab_8.4.0+dfsg~rc2-3_all.deb ...
  Unpacking gitlab (8.4.0+dfsg~rc2-3) ...
  Processing triggers for systemd (228-4+b1) ...
  Setting up gitlab (8.4.0+dfsg~rc2-3) ...
  Creating/updating gitlab user account...
  adduser: Warning: The home directory `/usr/share/gitlab' does not belong to 
the user you are currently creating.
  /var/lib/dpkg/info/gitlab.postinst: 41: /var/lib/dpkg/info/gitlab.postinst: 
sudo: not found
  dpkg: error processing package gitlab (--configure):
   subprocess installed post-installation script returned error exit status 127
  Processing triggers for systemd (228-4+b1) ...
  Errors were encountered while processing:
   gitlab


cheers,

Andreas


gitlab_8.4.0+dfsg~rc2-3.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#813271: diaspora-installer: fails to install: post-installation script returned error exit status 127

[Andreas Beckmann]

Package: diaspora-installer
Version: 0.5.3.0+debian1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package diaspora-installer.
  Preparing to unpack .../diaspora-installer_0.5.3.0+debian1_all.deb ...
  You already have a PostgreSQL database named 'diaspora_production'...
  Unpacking diaspora-installer (0.5.3.0+debian1) ...
  Setting up diaspora-installer (0.5.3.0+debian1) ...
  Download diaspora tarball version 0.5.3.0 from github.com...
  --2016-01-24 17:05:34--  
https://github.com/diaspora/diaspora/archive/v0.5.3.0.tar.gz
  Resolving github.com (github.com)... 192.30.252.128
  Connecting to github.com (github.com)|192.30.252.128|:443... connected.
  HTTP request sent, awaiting response... 302 Found
  Location: https://codeload.github.com/diaspora/diaspora/tar.gz/v0.5.3.0 
[following]
  --2016-01-24 17:05:34--  
https://codeload.github.com/diaspora/diaspora/tar.gz/v0.5.3.0
  Resolving codeload.github.com (codeload.github.com)... 192.30.252.163
  Connecting to codeload.github.com 
(codeload.github.com)|192.30.252.163|:443... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: unspecified [application/x-gzip]
  Saving to: '/var/cache/diaspora-installer/diaspora-0.5.3.0.tar.gz'
  
  
  /var/cach [<=> ]   0  --.-KB/s   
 /var/cache [ <=>]  83.87K   300KB/s   
/var/cache/ [  <=>   ] 546.67K  1.11MB/s   
   /var/cache/d [   <=>  ]   1.92M  2.82MB/s   
/var/cache/diaspora [<=> ]   2.65M  3.55MB/sin 0.7s
  
  2016-01-24 17:05:36 (3.55 MB/s) - 
'/var/cache/diaspora-installer/diaspora-0.5.3.0.tar.gz' saved [2776158]
  
  Extracting files...
  Copying files to /usr/share/diaspora...
  diaspora archive to copy: diaspora-0.5.3.0
  Copying source tarball to /usr/share/diaspora/public...
  Setting up environment varibales...
  Using /etc/diaspora.conf...
  export RAILS_ENV=production
  export DB=postgres
  RAILS_ENV=production DB=postgres ENVIRONMENT_URL=https://localhost
  Fetching: bundler-1.11.2.gem
Fetching: bundler-1.11.2.gem (  6%)
Fetching: bundler-1.11.2.gem ( 13%)
Fetching: bundler-1.11.2.gem ( 19%)
Fetching: bundler-1.11.2.gem ( 25%)
Fetching: bundler-1.11.2.gem ( 31%)
Fetching: bundler-1.11.2.gem ( 38%)
Fetching: bundler-1.11.2.gem ( 44%)
Fetching: bundler-1.11.2.gem ( 50%)
Fetching: bundler-1.11.2.gem ( 56%)
Fetching: bundler-1.11.2.gem ( 62%)
Fetching: bundler-1.11.2.gem ( 69%)
Fetching: bundler-1.11.2.gem ( 75%)
Fetching: bundler-1.11.2.gem ( 81%)
Fetching: bundler-1.11.2.gem ( 87%)
Fetching: bundler-1.11.2.gem ( 94%)
Fetching: bundler-1.11.2.gem (100%)
Fetching: bundler-1.11.2.gem (100%)
  Successfully installed bundler-1.11.2
  Parsing documentation for bundler-1.11.2
  Installing ri documentation for bundler-1.11.2
  Done installing documentation for bundler after 10 seconds
  1 gem installed
  Installing gems with rubygems ...
  Fetching gem metadata from https://rails-assets.org/...
  Fetching version metadata from https://rails-assets.org/..
  Fetching gem metadata from https://rails-assets.org/...
  Fetching gem metadata from https://rubygems.org/
  Fetching version metadata from https://rails-assets.org/..
  Fetching version metadata from https://rubygems.org/...
  Fetching dependency metadata from https://rails-assets.org/..
  Fetching dependency metadata from https://rubygems.org/..
  Resolving dependencies.
  Using rake 10.4.2
  Installing CFPropertyList 2.3.1
  Installing i18n 0.7.0
  Installing json 1.8.3 with native extensions
  Installing minitest 5.8.0
  Installing thread_safe 0.3.5
  Installing builder 3.2.2
  Installing erubis 2.7.0
  Installing mini_portile 0.6.2
  Installing rack 1.6.4
  Installing mime-types 2.6.1
  Installing arel 6.0.3
  Installing addressable 2.3.8
  Installing excon 0.45.4
  Installing formatador 0.2.5
  Installing net-ssh 2.9.2
  Installing multi_json 1.11.2
  Installing ipaddress 0.8.0
  Installing inflecto 0.0.2
  Installing unf_ext 0.0.7.1 with native extensions
  Installing execjs 2.6.0
  Installing coffee-script-source 1.9.1.1
  Installing eco-source 1.1.0.rc.1
  Installing ejs 1.1.1
  Installing thor 0.19.1
  Installing bcrypt 3.1.10 with native extensions
  Installing sass 3.4.16
  Installing buftok 0.2.0
  Using bundler 1.11.2
  Installing hitimes 1.2.2 with native extensions
  Installing nio4r 1.1.1

[DRE-maint] Bug#813265: ruby-bcat: postrm called with unknown argument `upgrade'

[Andreas Beckmann]

Package: ruby-bcat
Version: 0.6.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed the maintainer scripts of your
package don't support all the ways they are going to be called.

See policy 6.5 at
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-mscriptsinstact

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../ruby-bcat_0.6.2-4_all.deb ...
  Unpacking ruby-bcat (0.6.2-4) over (0.6.2-3) ...
  postrm called with unknown argument `upgrade'
  dpkg: warning: subprocess old post-removal script returned error exit status 1
  dpkg: trying script from the new package instead ...
  Removing 'diversion of /usr/bin/bcat to /usr/bin/bcat.diverted by ruby-bcat'
  dpkg: ... it looks like that went OK


Testing reinstallation in sid:

Preparing to unpack .../ruby-bcat_0.6.2-4_all.deb ...
Unpacking ruby-bcat (0.6.2-4) over (0.6.2-4) ...
postrm called with unknown argument `upgrade'
dpkg: warning: subprocess old post-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
Removing 'diversion of /usr/bin/bcat to /usr/bin/bcat.diverted by ruby-bcat'
dpkg: ... it looks like that went OK


Cheers,

Andreas


ruby-bcat_0.6.2-4.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#814621: diaspora-common: modifies conffiles (policy 10.7.3): /etc/diaspora.conf

[Andreas Beckmann]

Package: diaspora-common
Version: 0.5.6.3+debian1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also https://wiki.debian.org/DpkgConffileHandling

In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

  /etc/diaspora.conf


cheers,

Andreas


diaspora-common_0.5.6.3+debian1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#814645: ruby-mousetrap-rails: unhandled symlink to directory conversion: /usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap

[Andreas Beckmann]

Package: ruby-mousetrap-rails
Version: 1.4.6-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  testing -> sid

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

1m39.7s INFO: dirname part contains a symlink:
  
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap/dictionary.js
 (ruby-mousetrap-rails) != /usr/share/javascript/mousetrap/dictionary.js (?)
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap -> 
../../../../javascript/mousetrap
  /usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap/global.js 
(ruby-mousetrap-rails) != /usr/share/javascript/mousetrap/global.js (?)
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap -> 
../../../../javascript/mousetrap
  /usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap/pause.js 
(ruby-mousetrap-rails) != /usr/share/javascript/mousetrap/pause.js (?)
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap -> 
../../../../javascript/mousetrap
  
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap/plugins.js 
(ruby-mousetrap-rails) != /usr/share/javascript/mousetrap/plugins.js (?)
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap -> 
../../../../javascript/mousetrap
  /usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap/record.js 
(ruby-mousetrap-rails) != /usr/share/javascript/mousetrap/record.js (?)
/usr/share/ruby-mousetrap-rails/vendor/assets/javascripts/mousetrap -> 
../../../../javascript/mousetrap



cheers,

Andreas


ruby-mousetrap-rails_1.4.6-4.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#815242: passenger: FTBFS on kfreebsd: src/cxx_supportlib/BackgroundEventLoop.cpp:198:6: error: #error "This platform is not supported. Please add corresponding I/O polling code."

[Andreas Beckmann]

Source: passenger
Version: 5.0.22-1
Severity: important

Hi,

passenger FTBFS on kfreebsd-*:

https://buildd.debian.org/status/fetch.php?pkg=passenger&arch=kfreebsd-amd64&ver=5.0.22-1&stamp=1449534348
https://buildd.debian.org/status/fetch.php?pkg=passenger&arch=kfreebsd-i386&ver=5.0.22-1&stamp=1449530910

c++ -o buildout/support-binaries/CoreMain.o  -Isrc/agent -Isrc/cxx_supportlib 
-Isrc/cxx_supportlib/vendor-copy -Isrc/cxx_supportlib/vendor-modified 
-Isrc/cxx_supportlib/vendor-modified/libev 
-Isrc/cxx_supportlib/vendor-copy/libuv/include -D_REENTRANT 
-I/usr/local/include -Wall -Wextra -Wno-unused-parameter -Wno-parentheses 
-Wpointer-arith -Wwrite-strings -Wno-long-long -Wno-missing-field-initializers 
-feliminate-unused-debug-symbols -feliminate-unused-debug-types 
-fvisibility=hidden -DVISIBILITY_ATTRIBUTE_SUPPORTED -ggdb -DHAS_ALLOCA_H 
-DHAVE_ACCEPT4 -DHAS_SFENCE -DHAS_LFENCE -DPASSENGER_DEBUG 
-DBOOST_DISABLE_ASSERTS -Wno-unused-local-typedefs -DHASH_NAMESPACE="__gnu_cxx" 
-DHASH_MAP_HEADER="" -DHASH_MAP_CLASS="hash_map" 
-DHASH_FUN_H="" -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2 -c src/agent/Core/CoreMain.cpp
In file included from src/agent/Core/CoreMain.cpp:79:0:
src/cxx_supportlib/BackgroundEventLoop.cpp:198:6: error: #error "This platform 
is not supported. Please add corresponding I/O polling code."
 #error "This platform is not supported. Please add corresponding I/O 
polling code."
...


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#814645: not in stable yet

[Andreas Beckmann]

On 2016-02-25 08:36, Pirate Praveen wrote:
> ruby-mousetrap-rails is not part of any stable release. So should I
> really handle this upgrade case?

Yes. Especially since the fix should be trivial.


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#814645: not in stable yet

[Andreas Beckmann]

On 2016-03-01 06:13, Balasankar C wrote:
> On Thu, 25 Feb 2016 13:07:39 +0100 Andreas Beckmann 
> wrote:
>> On 2016-02-25 08:36, Pirate Praveen wrote:
>>> ruby-mousetrap-rails is not part of any stable release. So should
>>> I really handle this upgrade case?
> 
>> Yes. Especially since the fix should be trivial.
> 
> Hi,
> 
> This may be a silly doubt, but I didn't quite understand the issue
> here. Version 1.4.6-4 is in testing, 1.4.6-4 is in unstable. How will
> there be an upgrade from testing to sid when both have the same
> version? It is not in stable yet, so there is no upgrade path from
> stable to testing.

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
clean upgrade so far.

Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#814645: not in stable yet

[Andreas Beckmann]

On 2016-03-01 13:15, Pirate Praveen wrote:
> 
> 
> 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
>> clean upgrade so far.
> 
> But we don't support it. We support only upgrades between stable versions.

You don't support upgrading from testing (older version) to testing
(never version)?


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#720141: redminei-sqlite: fails to install: uninitialized constant Arel::Relation

[Andreas Beckmann]

Package: redmine-sqlite
Version: 2.3.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up redmine-sqlite (2.3.1-1) ...
  Setting up redmine (2.3.1-1) ...
  dbconfig-common: writing config to 
/etc/dbconfig-common/redmine/instances/default.conf
  
  Creating config file /etc/dbconfig-common/redmine/instances/default.conf with 
new version
  
  Creating config file /etc/redmine/default/database.yml.new with new version
  creating database redmine_default: success.
  verifying database redmine_default exists: success.
  
  Creating config file /etc/redmine/default/database.yml with new version
  
  Creating config file /etc/redmine/default/session.yml with new version
  A new secret session key has been generated in 
/etc/redmine/default/session.yml
  Populating database for redmine instance "default".
  This may take a while.
  rake aborted!
  An error has occurred, this and all later migrations canceled:
  
  uninitialized constant Arel::Relation
  Tasks: TOP => db:migrate
  (See full trace by running task with --trace)
  Error when running rake db:migrate, check database configuration.
  dpkg: error processing redmine (--configure):
   subprocess installed post-installation script returned error exit status 1


cheers,

Andreas


redmine-mysql_2.3.1-1.log.gz
Description: GNU Zip compressed data
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#726725: feed2imap: uninstallable in sid

[Andreas Beckmann]

Package: feed2imap
Version: 1.0-2
Severity: serious
Tags: sid jessie
User: debian...@lists.debian.org
Usertags: piuparts
Control: close -1 1.2-1

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

It depends on ruby-feedparser, but that breaks feed2imap (<< 1.2).
This is fixed in experimental.


Cheers,

Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#728243: redmine: fails to install: Please install the mysql adapter

[Andreas Beckmann]

Package: redmine
Version: 2.3.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + redmine-mysql

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

This was observed while testing the installation of redmine-mysql with 
installation of Recommends being enabled.

>From the attached log (scroll to the bottom...):

[...]
  Setting up redmine-mysql (2.3.3-2) ...
[...]
  Setting up redmine (2.3.3-2) ...
  dbconfig-common: writing config to 
/etc/dbconfig-common/redmine/instances/default.conf
  
  Creating config file /etc/dbconfig-common/redmine/instances/default.conf with 
new version
  
  Creating config file /etc/redmine/default/database.yml.new with new version
  granting access to database redmine_default for redmine@localhost: success.
  verifying access for redmine@localhost: success.
  creating database redmine_default: success.
  verifying database redmine_default exists: success.
  dbconfig-common: flushing administrative password
  
  Creating config file /etc/redmine/default/database.yml with new version
  
  Creating config file /etc/redmine/default/session.yml with new version
  A new secret session key has been generated in 
/etc/redmine/default/session.yml
  Populating database for redmine instance "default".
  This may take a while.
  rake aborted!
  Please install the mysql adapter: `gem install activerecord-mysql-adapter` 
(cannot load such file -- mysql)
  
  Tasks: TOP => db:migrate => environment
  (See full trace by running task with --trace)
  Error when running rake db:migrate, check database configuration.
  dpkg: error processing redmine (--configure):
   subprocess installed post-installation script returned error exit status 1
[...]

cheers,

Andreas


redmine-mysql_2.3.3-2.log.gz
Description: GNU Zip compressed data
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#735613: ruby-hoe: uninstallable in sid: Depends: rake (< 0.11) but 10.0.4-1 is to be installed

[Andreas Beckmann]

Package: ruby-hoe
Version: 3.8.0-1
Severity: serious
Tags: sid
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

0m16.1s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpWTr6TG', 
'apt-get', '-y', 'install', 'ruby-hoe=3.8.0-1']
0m16.4s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   ruby-hoe : Depends: rake (< 0.11) but 10.0.4-1 is to be installed
  E: Unable to correct problems, you have held broken packages.
0m16.4s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmpWTr6TG', 'apt-get', '-y', 'install', 'ruby-hoe=3.8.0-1']


Cheers,

Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#736409: ruby-prof: FTBFS nearly everywhere in a timing test

[Andreas Beckmann]

Source: ruby-prof
Version: 0.13.1-1
Severity: serious

Hi,

ruby-prof FTBFS on all architectures except powerpc:

https://buildd.debian.org/status/package.php?p=ruby-prof

Excerpt from
https://buildd.debian.org/status/fetch.php?pkg=ruby-prof&arch=i386&ver=0.13.1-1&stamp=1387838705

make "DESTDIR=" install
make[2]: Entering directory `/«PKGBUILDDIR»/ext/ruby_prof'
/usr/bin/install -c -m 0755 ruby_prof.so ./.gem.20131223-15730-1fqm95i
installing default ruby_prof libraries
make[2]: Leaving directory `/«PKGBUILDDIR»/ext/ruby_prof'
Rewriting shebang line of /«PKGBUILDDIR»/debian/ruby-prof/usr/bin/ruby-prof
/usr/bin/ruby1.9.1 -I/usr/lib/ruby/vendor_ruby 
/usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb
Loaded suite -e
Started
.F
===
Failure:
  <1.3801> -/+ <0.02> expected to include
  <1.400388697998>.
  
  Relation:
  <<1.3801>-<0.02>[1.36] <= 
<1.3801>+<0.02>[1.4001] < <1.400388697998>>
test_primes(MeasureProcessTimeTest)
/«PKGBUILDDIR»/test/measure_process_time_test.rb:45:in `test_primes'
 42: 
 43: # Check times
 44: assert_equal("MeasureProcessTimeTest#test_primes", 
methods[0].full_name)
  => 45: assert_in_delta(total_time, methods[0].total_time, 0.02)
 46: assert_in_delta(0.0, methods[0].wait_time, 0.01)
 47: assert_in_delta(0.0, methods[0].self_time, 0.01)
 48: 
===
.

Finished in 54.392949591 seconds.

89 tests, 741 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
98.8764% passed

1.64 tests/s, 13.62 assertions/s
ERROR: Test "ruby1.9.1" failed. Exiting.
dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-prof returned 
exit code 1
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory `/«PKGBUILDDIR»'
make: *** [binary-arch] Error 2


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#767842: ruby-actionpack-action-caching: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb

[Andreas Beckmann]

Package: ruby-actionpack-action-caching
Version: 1.1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ruby-actionmailer.
  Preparing to unpack .../ruby-actionmailer_2%3a4.1.6-2_all.deb ...
  Unpacking ruby-actionmailer (2:4.1.6-2) ...
  Replacing files in old package ruby-actionmailer-2.3 (2.3.14-3) ...
  Selecting previously unselected package ruby-actionpack-action-caching.
  Preparing to unpack .../ruby-actionpack-action-caching_1.1.1-1_all.deb ...
  Unpacking ruby-actionpack-action-caching (1.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-actionpack-action-caching_1.1.1-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb', which is also 
in package ruby-actionpack-2.3 2.3.14-5
  Selecting previously unselected package ruby-activemodel.
  Preparing to unpack .../ruby-activemodel_2%3a4.1.6-2_all.deb ...
  Unpacking ruby-activemodel (2:4.1.6-2) ...


cheers,

Andreas


redmine_3.0~20140825-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#749994: tdiary-mode: fails to upgrade from sid

[Andreas Beckmann]

Followup-For: Bug #749994
Control: found -1 4.0.5.1-1

  Install tdiary-mode for emacs24
  install/tdiary-mode: Handling install for emacsen flavor emacs24
  ERROR: install script from tdiary-mode package failed
  dpkg: error processing package emacs24-nox (--configure):
   subprocess installed post-installation script returned error exit status 1


Andreas


tdiary-mode_4.0.5.1-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#749994: tdiary-mode: fails to upgrade from sid

[Andreas Beckmann]

Control: notfound -1 4.0.5.1-1
Control: close -1 4.0.5.1-1

On 2014-11-04 11:31, Andreas Beckmann wrote:
>   Install tdiary-mode for emacs24
>   install/tdiary-mode: Handling install for emacsen flavor emacs24
>   ERROR: install script from tdiary-mode package failed
>   dpkg: error processing package emacs24-nox (--configure):
>subprocess installed post-installation script returned error exit status 1

darn, that was still the old package being installed ...


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#767842: ruby-actionpack-action-caching: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb

[Andreas Beckmann]

Followup-For: Bug #767842

Similar problems exist with ruby-actionpack-3.2:

  Selecting previously unselected package ruby-actionpack.
  Unpacking ruby-actionpack (from .../ruby-actionpack_2%3a4.1.6-2_all.deb) ...
  Replacing files in old package ruby-actionpack-3.2 ...
  Selecting previously unselected package ruby-actionpack-action-caching.
  Unpacking ruby-actionpack-action-caching (from 
.../ruby-actionpack-action-caching_1.1.1-1_all.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/ruby-actionpack-action-caching_1.1.1-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb', which is also 
in package ruby-actionpack-3.2 3.2.6-6+deb7u2
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-actionpack-action-caching_1.1.1-1_all.deb


Cheers,

Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#768160: ruby-twitter: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/ruby/vendor_ruby/twitter/version.rb

[Andreas Beckmann]

Package: ruby-twitter
Version: 5.11.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'jessie' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ruby-twitter.
  Unpacking ruby-twitter (from .../ruby-twitter_5.11.0-1_all.deb) ...
  dpkg: error processing /var/cache/apt/archives/ruby-twitter_5.11.0-1_all.deb 
(--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/twitter/version.rb', which is 
also in package ruby-twitter4r 0.7.0-3
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-twitter_5.11.0-1_all.deb


cheers,

Andreas


ruby-twitter4r=0.7.0-3_ruby-twitter=5.11.0-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#768850: ruby-activemodel, ruby-activesupport: needs Breaks for the packages it Replaces

[Andreas Beckmann]

Package: ruby-activemodel,ruby-activesupport
Version: 2:4.1.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package, leaving the other
package installed but crippled.
This is caused by using Replaces without corresponding Breaks.

This is a serious bug violating policy 7.6, see
http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
and also see the footnote that describes this incorrect behavior
http://www.debian.org/doc/debian-policy/footnotes.html#f53

The ruby-activemodel package has the following relevant relationships:

  Conflicts: N/A
  Breaks:N/A
  Replaces:  ruby-activemodel-3.2, ruby-activemodel-4.0

Since you intend to completely replace these packages, I suggest to add

  Breaks: ruby-activemodel-3.2, ruby-activemodel-4.0

(lintian may warn about a missing (<< $VER) clause - you can either ignore
that or make something up like (<< 2:4.1) - which should go to the Replaces
as well)

The same applies to the ruby-activesupport package which

  Replaces: ruby-activesupport-2.3, ruby-activesupport-3.2, 
ruby-activesupport-4.0

The other packages built from src:rails may have similar problems, I didn't
check in deep. They should be adjusted for consistency anyway.

But I could create test setups with crippled ruby-activemodel-3.2 and
ruby-activemodel-3.2 after installation and removal of the above two packages.
This may be an issue on wheezy -> jessie upgrades.


cheers,

Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#768850: ruby-activemodel, ruby-activesupport: needs Breaks for the packages it Replaces

[Andreas Beckmann]

On 2014-11-11 13:55, Antonio Terceiro wrote:
> The Breaks: relationships were there originally, but removing them was
> how I achieved a successfull upgrade from wheezy in the first place,
> after some hours of trial and error. aptitude would figure the upgrade
> out just fine, but apt-get wouldn't.

Maybe we need to add some more Breaks elsewhere to push apt into the
right direction ...

> Looking back, what I didn't do was upgrading apt first, then upgrading
> the rest of the system. Maybe that would help.

upgrades must work out successfully with the apt-get from wheezy.
Even if you Breaks: apt (<< jessie), apt will be upgraded first, but the
apt process running the dist-upgrade is still the old one from wheezy

If you can put packages (with a version > jessie) with the Breaks added
back somewhere (and add a Packages file, too) I could take a look at
what's happening there. Please describe your failing upgrade scenario
(wheezy + these packages: foo, bar, baz, ...  with/without recommends).


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#769359: ruby-fog-sakuracloud, ruby-fog: error when trying to install together

[Andreas Beckmann]

Package: ruby-fog-sakuracloud,ruby-fog
Version: 0.1.1-1
Severity: serious
Tags: sid
User: trei...@debian.org
Usertags: edos-file-overwrite

Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package ruby-fog.
  Preparing to unpack .../ruby-fog_1.22.0-2_all.deb ...
  Unpacking ruby-fog (1.22.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-fog_1.22.0-2_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/fog/sakuracloud/compute.rb', 
which is also in package ruby-fog-sakuracloud 0.1.1-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-fog_1.22.0-2_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/lib/ruby/vendor_ruby/fog/bin/sakuracloud.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/compute.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/plan.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/plans.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/server.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/servers.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/ssh_key.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/ssh_keys.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/zone.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/compute/zones.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/volume/archive.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/volume/archives.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/volume/disk.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/volume/disks.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/volume/plan.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/models/volume/plans.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/boot_server.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/create_server.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/delete_server.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/list_plans.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/list_servers.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/list_ssh_keys.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/list_zones.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/compute/stop_server.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/attach_disk.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/configure_disk.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/create_disk.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/delete_disk.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/list_archives.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/list_disks.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/requests/volume/list_plans.rb
  usr/lib/ruby/vendor_ruby/fog/sakuracloud/volume.rb

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.


Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.


ruby-fog-sakuracloud=0.1.1-1_ruby-fog=1.22.0-2.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#769788: ruby-simple-navigation: please remove dependency on ruby-rails-3.2

[Andreas Beckmann]

Package: ruby-simple-navigation
Version: 3.11.0-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

your package has
  Depends: ruby-rails-3.2 | ruby-sinatra
but ruby-rails-3.2 is not in jessie and will go away from sid at some
point eventually. Please make ruby-sinatra the default alternative or
completely remove ruby-rails-3.2.
ruby-simple-navigation is hard to install in sid (or if sid sources are
enabled), because the package manager will try the first alternative
first and then fails to resolve the resulting Conflicts tree ...
This causes the piuparts failure in sid.

Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#767842: ruby-actionpack-action-caching: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb

[Andreas Beckmann]

On 2014-11-17 19:03, gregor herrmann wrote:
> On Sun, 02 Nov 2014 22:52:13 +0100, Andreas Beckmann wrote:
>>   Unpacking ruby-actionpack-action-caching (1.1.1-1) ...
>>   dpkg: error processing archive 
>> /var/cache/apt/archives/ruby-actionpack-action-caching_1.1.1-1_all.deb 
>> (--unpack):
>>trying to overwrite 
>> '/usr/lib/ruby/vendor_ruby/action_controller/caching/actions.rb', which is 
>> also in package ruby-actionpack-2.3 2.3.14-5

> Is this the same as #769555 (fixed some days ago) or something
> different?

It's probably the same issue which has *not* been fixed properly in the
recent upload.
Bumping the Depends is not sufficient to control unpack ordering - I can
still reproduce the file overwrite error with 1.1.1-2.
Versioned Breaks+Replaces need to be added for the file takeover.


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#768850: ruby-activemodel, ruby-activesupport: needs Breaks for the packages it Replaces

[Andreas Beckmann]

On 2014-11-14 20:51, Antonio Terceiro wrote:
> The following packages will be REMOVED:
>   gcc-4.7-base
> The following packages have been kept back:
>   rails

The problematic package is ruby-activesupport-2.3 which gets a higher
score (score=21) than ruby-activesupport (score=11) (probably due to a high 
number of
rdepends in wheezy, the scoring seems to be fixed in jessie though):

  Investigating (0) ruby-activesupport [ amd64 ] < none -> 2:4.1.7-1 > ( ruby )
  Broken ruby-activesupport:amd64 Breaks on ruby-activesupport-2.3 [ amd64 ] < 
2.3.14-7 > ( ruby )
Considering ruby-activesupport-2.3:amd64 21 as a solution to 
ruby-activesupport:amd64 11
Holding Back ruby-activesupport:amd64 rather than change 
ruby-activesupport-2.3:amd64

and this starts a cascade of keeping the *-2.3 packages installed,
resulting in the old rails being kept.


So add a transitional dummy package that ensures the stack of *-2.3
packages gets removed:

Package: ruby-activesupport-2.3
Architecture: all
Depends: ruby-activesupport (>= 2:4),
 ${misc:Depends},
 ${shlibs:Depends}
Breaks:
 ruby-activesupport-3.2,
 ruby-activesupport-4.0,
 ruby-actionpack-2.3,
 ruby-activerecord-2.3,
 ruby-activeresource-2.3,
 ruby-rails-2.3,
Description: transitional dummy package
 Ensure the removal of rails 2.3 on upgrades from wheezy.
 This package can be safely removed.

and in ruby-activesupport use

Replaces: ruby-activesupport-2.3 (<< 2:4), ruby-activesupport-3.2, 
ruby-activesupport-4.0
Breaks: ruby-activesupport-2.3 (<< 2:4), ruby-activesupport-3.2, 
ruby-activesupport-4.0

It's important to have the Breaks directly in ruby-activesupport-2.3,
having them only transitively via ruby-activesupport does not work -
that seems to be the apt bug fixed in jessie.

The upgrade then looks like this:

  Investigating (0) ruby-activesupport-2.3 [ amd64 ] < 2.3.14-7 -> 2:4.1.7-1 > 
( ruby )
  Broken ruby-activesupport-2.3:amd64 Breaks on ruby-actionpack-2.3 [ amd64 ] < 
2.3.14-5 > ( ruby )
Considering ruby-actionpack-2.3:amd64 5 as a solution to 
ruby-activesupport-2.3:amd64 22
Added ruby-actionpack-2.3:amd64 to the remove list
  Broken ruby-activesupport-2.3:amd64 Breaks on ruby-activerecord-2.3 [ amd64 ] 
< 2.3.14-6 > ( ruby )
Considering ruby-activerecord-2.3:amd64 9 as a solution to 
ruby-activesupport-2.3:amd64 22
Added ruby-activerecord-2.3:amd64 to the remove list
  Broken ruby-activesupport-2.3:amd64 Breaks on ruby-activeresource-2.3 [ amd64 
] < 2.3.14-3 > ( ruby )
Considering ruby-activeresource-2.3:amd64 1 as a solution to 
ruby-activesupport-2.3:amd64 22
Added ruby-activeresource-2.3:amd64 to the remove list
  Broken ruby-activesupport-2.3:amd64 Breaks on ruby-rails-2.3 [ amd64 ] < 
2.3.14-4 > ( ruby )
Considering ruby-rails-2.3:amd64 -1 as a solution to 
ruby-activesupport-2.3:amd64 22
Added ruby-rails-2.3:amd64 to the remove list
Fixing ruby-activesupport-2.3:amd64 via remove of ruby-actionpack-2.3:amd64
Fixing ruby-activesupport-2.3:amd64 via remove of 
ruby-activerecord-2.3:amd64
Fixing ruby-activesupport-2.3:amd64 via remove of 
ruby-activeresource-2.3:amd64
Fixing ruby-activesupport-2.3:amd64 via remove of ruby-rails-2.3:amd64
  Investigating (0) ruby-actionmailer-2.3 [ amd64 ] < 2.3.14-3 > ( ruby )
  Broken ruby-actionmailer-2.3:amd64 Depends on ruby-actionpack-2.3 [ amd64 ] < 
2.3.14-5 > ( ruby ) (>= 2.3.14)
Considering ruby-actionpack-2.3:amd64 5 as a solution to 
ruby-actionmailer-2.3:amd64 1
Removing ruby-actionmailer-2.3:amd64 rather than change 
ruby-actionpack-2.3:amd64
  Done

The transitional package now causes a cascade of removals, not keeps :-)
(the score increased by one because the package now exists in the target 
release)

  The following packages will be REMOVED:
ruby-actionmailer-2.3 ruby-actionpack-2.3 ruby-activerecord-2.3
ruby-activeresource-2.3 ruby-rails-2.3
...


It's sufficient to have only one transitional package - the one that gets the 
highest score from apt.


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#770251: ruby-jbuilder, ruby-responders: error when trying to install together

[Andreas Beckmann]

Package: ruby-jbuilder,ruby-responders
Version: 2.0.2-1
Severity: serious
Tags: sid
User: trei...@debian.org
Usertags: edos-file-overwrite

Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package ruby-responders.
  (Reading database ... 9354 files and directories currently installed.)
  Preparing to unpack .../ruby-responders_2.0.2-1_all.deb ...
  Unpacking ruby-responders (2.0.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-responders_2.0.2-1_all.deb (--unpack):
   trying to overwrite 
'/usr/lib/ruby/vendor_ruby/generators/rails/templates/controller.rb', which is 
also in package ruby-jbuilder 2.1.3-1
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-responders_2.0.2-1_all.deb


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/lib/ruby/vendor_ruby/generators/rails/templates/controller.rb

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


ruby-jbuilder=2.1.3-1_ruby-responders=2.0.2-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#774969: ruby-fog, ruby-fog-xml: error when trying to install together

[Andreas Beckmann]

Package: ruby-fog,ruby-fog-xml
Version: 1.24.0-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 0.1.1-1

Architecture: amd64
Distribution: experimental

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package ruby-fog.
  Preparing to unpack .../ruby-fog_1.24.0-2_all.deb ...
  Unpacking ruby-fog (1.24.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-fog_1.24.0-2_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/fog/xml.rb', which is also in 
package ruby-fog-xml 0.1.1-1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-fog_1.24.0-2_all.deb


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/lib/ruby/vendor_ruby/fog/xml.rb
  usr/lib/ruby/vendor_ruby/fog/xml/connection.rb
  usr/lib/ruby/vendor_ruby/fog/xml/sax_parser_connection.rb

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


ruby-fog-xml=0.1.1-1_ruby-fog=1.24.0-2.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#774973: ruby-fog-voxel: fails to upgrade from 'sid' - trying to overwrite /usr/lib/ruby/vendor_ruby/fog/voxel/compute.rb

[Andreas Beckmann]

Package: ruby-fog-voxel
Version: 0.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ruby-fog-voxel.
  Preparing to unpack .../ruby-fog-voxel_0.0.1-1_all.deb ...
  Unpacking ruby-fog-voxel (0.0.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-fog-voxel_0.0.1-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/fog/voxel/compute.rb', which 
is also in package ruby-fog 1.22.0-2
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-fog-voxel_0.0.1-1_all.deb


cheers,

Andreas


ruby-fog=1.22.0-2_ruby-fog-voxel=0.0.1-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#776916: tdiary: new upstream release needed for tdiary/experimental

[Andreas Beckmann]

Source: tdiary
Version: 4.0.5.1-1
Severity: normal
Tags: experimental
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + tdiary-contrib

tdiary-contrib/experimental is not installable:

The following packages have unmet dependencies:
 tdiary-contrib : Depends: tdiary (>= 4.0) but 3.2.2-3 is to be
 installed


Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#779660: ruby-actionpack-page-caching: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/ruby/vendor_ruby/action_controller/caching/pages.rb

[Andreas Beckmann]

Package: ruby-actionpack-page-caching
Version: 1.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'wheezy'.
It installed fine in 'wheezy', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ruby-actionpack.
  Unpacking ruby-actionpack (from .../ruby-actionpack_2%3a2.3.14.2_all.deb) ...
  Selecting previously unselected package ruby-actionpack-page-caching.
  Unpacking ruby-actionpack-page-caching (from 
.../ruby-actionpack-page-caching_1.0.2-1_all.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/ruby-actionpack-page-caching_1.0.2-1_all.deb (--unpack):
   trying to overwrite 
'/usr/lib/ruby/vendor_ruby/action_controller/caching/pages.rb', which is also 
in package ruby-actionpack-2.3 2.3.14-5
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-actionpack-page-caching_1.0.2-1_all.deb

ruby-actionpack-2.3 is not part of jessie, but there is no upgrade path
guarantee that this obsolete package will be removed on upgrades to from
wheezy to jessie, so ruby-actionpack-page-caching (which will not be part
of jessie either) will have to add the corresponding
  Breaks+Replaces: ruby-actionpack-2.3
anyway to ensure this package gets removed during the jessie->stretch
upgrade path.


cheers,

Andreas


ruby-actionpack-2.3=2.3.14-5_ruby-actionpack-page-caching=1.0.2-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#787910: ruby-fog-storm-on-demand: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/ruby/vendor_ruby/fog/storm_on_demand/shared.rb

[Andreas Beckmann]

Package: ruby-fog-storm-on-demand
Version: 0.1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ruby-fog-storm-on-demand.
  Preparing to unpack .../ruby-fog-storm-on-demand_0.1.1-1_all.deb ...
  Unpacking ruby-fog-storm-on-demand (0.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-fog-storm-on-demand_0.1.1-1_all.deb (--unpack):
   trying to overwrite 
'/usr/lib/ruby/vendor_ruby/fog/storm_on_demand/shared.rb', which is also in 
package ruby-fog 1.22.0-2
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-fog-storm-on-demand_0.1.1-1_all.deb


cheers,

Andreas


ruby-fog=1.22.0-2_ruby-fog-storm-on-demand=0.1.1-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#788294: rex, rexical: error when trying to install together

[Andreas Beckmann]

Package: rex,rexical
Version: 1.0.5-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1.2.1-1

Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package rex.
  Preparing to unpack .../archives/rex_1.2.1-1_all.deb ...
  Unpacking rex (1.2.1-1) ...
  dpkg: error processing archive /var/cache/apt/archives/rex_1.2.1-1_all.deb 
(--unpack):
   trying to overwrite '/usr/bin/rex', which is also in package rexical 1.0.5-1
  Errors were encountered while processing:
   /var/cache/apt/archives/rex_1.2.1-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/bin/rex

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


rexical=1.0.5-1_rex=1.2.1-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#788544: ruby-fog-vmfusion: fails to upgrade from 'jessie' - trying to overwrite /usr/lib/ruby/vendor_ruby/fog/vmfusion.rb

[Andreas Beckmann]

Package: ruby-fog-vmfusion
Version: 0.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package ruby-fog-vmfusion.
  Preparing to unpack .../ruby-fog-vmfusion_0.1.0-1_all.deb ...
  Unpacking ruby-fog-vmfusion (0.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-fog-vmfusion_0.1.0-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/fog/vmfusion.rb', which is 
also in package ruby-fog 1.22.0-2
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-fog-vmfusion_0.1.0-1_all.deb


cheers,

Andreas


ruby-fog=1.22.0-2_ruby-fog-vmfusion=0.1.0-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#790510: rhc: uninstallable in sid: Depends: ruby-highline (< 1.7) but 1.7.2-1 is to be installed

[Andreas Beckmann]

Package: rhc
Version: 1.35.4-2
Severity: grave
Tags: sid
Justification: renders package unusable
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

0m24.1s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmpm1b0zg', 'apt-get', '-y', 'install', 'rhc=1.35.4-2']
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   rhc : Depends: ruby-highline (< 1.7) but 1.7.2-1 is to be installed
  E: Unable to correct problems, you have held broken packages.
 

Cheers,

Andreas

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#790537: diaspora-common: fails to install: ERROR: role "diaspora" does not exist

[Andreas Beckmann]

Package: diaspora-common
Version: 0.5.0.1+debian1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package diaspora-common.
  (Reading database ... 
(Reading database ... 13287 files and directories currently installed.)
  Preparing to unpack .../diaspora-common_0.5.0.1+debian1_all.deb ...
  Unpacking diaspora-common (0.5.0.1+debian1) ...
  Processing triggers for systemd (220-7) ...
  Setting up diaspora-common (0.5.0.1+debian1) ...
  SSL enabled, configuring nginx for localhost...
  dbconfig-common: writing config to /etc/dbconfig-common/diaspora-common.conf
  
  Creating config file /etc/dbconfig-common/diaspora-common.conf with new 
version
  creating postgres user diasporacommon:  success.
  verifying creation of user: success.
  creating database diasporacommon: success.
  verifying database diasporacommon exists: success.
  dbconfig-common: flushing administrative password
  Creating/updating diaspora user account...
  adduser: Warning: The home directory `/usr/share/diaspora' does not belong to 
the user you are currently creating.
  Make diaspora user owner of diaspora_production database...
  ERROR:  role "diaspora" does not exist
  dpkg: error processing package diaspora-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for systemd (220-7) ...
  Errors were encountered while processing:
   diaspora-common


This seems to be a regression in a dependency. According to my logs I had
a (last) successful test on 2015-06-01, rechecking on 2015-06-25 resulted
in a reproducible failure.


cheers,

Andreas


diaspora-common_0.5.0.1+debian1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#792768: ruby-fog-powerdns: /usr/bin/console already used by conserver-client

[Andreas Beckmann]

Package: ruby-fog-powerdns
Version: 0.1.1-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: affects -1 + conserver-client

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package ruby-fog-powerdns.
  Preparing to unpack .../ruby-fog-powerdns_0.1.1-1_all.deb ...
  Unpacking ruby-fog-powerdns (0.1.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-fog-powerdns_0.1.1-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/console', which is also in package 
conserver-client 8.1.18-2.2
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-fog-powerdns_0.1.1-1_all.deb


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/bin/console

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


conserver-client=8.1.18-2.2_ruby-fog-powerdns=0.1.1-1.log.gz
Description: application/gzip
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers