Bug#956205: gitlab: Problem installing 12.8.8-6
Package: gitlab
Version: 12.8.8-6+fto10+1
Severity: grave
Justification: renders package unusable
Hi,
Gitlab 12.8.8 installation fails.
Log:
Bundle complete! 198 Gemfile dependencies, 362 gems now installed.
Gems in the groups development and test were not installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
Running final rake tasks and tweaks...
gitlab_production database is not empty, skipping gitlab setup
Precompiling assets...
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Attention: used pure ruby version of MurmurHash3
/usr/share/gitlab/lib/gitlab.rb:38: warning: already initialized constant
Gitlab::COM_URL
/usr/share/gitlab/lib/gitlab.rb:38: warning: previous definition of COM_URL was
here
/usr/share/gitlab/lib/gitlab.rb:39: warning: already initialized constant
Gitlab::APP_DIRS_PATTERN
/usr/share/gitlab/lib/gitlab.rb:39: warning: previous definition of
APP_DIRS_PATTERN was here
/usr/share/gitlab/lib/gitlab.rb:40: warning: already initialized constant
Gitlab::SUBDOMAIN_REGEX
/usr/share/gitlab/lib/gitlab.rb:40: warning: previous definition of
SUBDOMAIN_REGEX was here
/usr/share/gitlab/lib/gitlab.rb:41: warning: already initialized constant
Gitlab::VERSION
/usr/share/gitlab/lib/gitlab.rb:41: warning: previous definition of VERSION was
here
/usr/share/gitlab/lib/gitlab.rb:42: warning: already initialized constant
Gitlab::INSTALLATION_TYPE
/usr/share/gitlab/lib/gitlab.rb:42: warning: previous definition of
INSTALLATION_TYPE was here
/usr/share/gitlab/lib/gitlab.rb:43: warning: already initialized constant
Gitlab::HTTP_PROXY_ENV_VARS
/usr/share/gitlab/lib/gitlab.rb:43: warning: previous definition of
HTTP_PROXY_ENV_VARS was here
yarn install v1.22.4
[1/4] Resolving packages...
success Already up-to-date.
$ node ./scripts/frontend/postinstall.js
success Dependency postinstall check passed.
Done in 1.45s.
rake aborted!
SassC::SyntaxError: Error: Top-level selectors may not contain the parent
selector "&".
on line 6:9 of node_modules/@gitlab/ui/src/scss/components.scss
from line 13:9 of node_modules/@gitlab/ui/src/scss/gitlab_ui.scss
from line 5:9 of app/assets/stylesheets/framework.scss
from line 19:9 of app/assets/stylesheets/application.scss
>> &.gl-avatar-identicon-bg#{$i} {
--^
/usr/share/gitlab/node_modules/@gitlab/ui/src/scss/../components/base/avatar/avatar.scss:82
/usr/share/rubygems-integration/all/gems/sassc-2.2.1/lib/sassc/engine.rb:49:in
`render'
/usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in `'
Tasks: TOP => assets:precompile
(See full trace by running task with --trace)
dpkg: error processing package gitlab (--configure):
installed gitlab package post-installation script subprocess returned error
exit status 1
Thanks,
-- System Information:
Debian Release: bullseye/sid
APT prefers buster-fasttrack
APT policy: (500, 'buster-fasttrack'), (500, 'buster-backports'), (500,
'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.62-mod-std-ipv6-64-rescue (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gitlab depends on:
ii asciidoctor 2.0.10-2
ii bc 1.07.1-2+b2
ii bundler 2.1.4-1
ii bzip2 1.0.8-2
ii dbconfig-pgsql 2.0.13
ii debconf [debconf-2.0] 1.5.73
ii exim4-daemon-light [mail-transport-agent] 4.93-13
ii gitlab-common 12.8.8-6+fto10+1
ii gitlab-workhorse8.30+debian-1
ii libjs-bootstrap4 [node-bootstrap] 4.4.1+dfsg1-2
ii libjs-popper.js [node-popper.js]1.16.0+ds2-1
ii libjs-uglify2.8.29-6
ii lsb-base11.1.0
ii nginx 1.16.1-3
ii nginx-full [nginx] 1.16.1-3
ii node-autosize 4.0.2~dfsg1-3
ii node-axios 0.19.0+dfsg-2
ii node-brace-expansion1.1.11-1
ii node-cache-loader 2.0.1-2
ii node-chart.js 2.9.3+dfsg-2
ii node-clipboard 2.0.6+ds-1
ii node-core-js3.6.1-3
ii node-css-loader 1.0.1+repack-1
ii node-d3
Bug#944596: gitlab: Upgrading to 12.2.9-1 fails
Package: gitlab
Version: 12.2.9-1+fto10+1
Followup-For: Bug #944596
More info about the bug:
- Deleting file active_record_mysql_timestamp.rb, fails on
active_record_mysql_timestamp.rb, because the same error, "undefined method
mysql?".
Error MSG:
NoMethodError: undefined method `mysql?' for Gitlab::Database:Module
/usr/share/gitlab/config/initializers/ar_mysql_jsonb_support.rb:9:in `'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in
`load'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in
`block in load'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in
`load_dependency'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:285:in
`load'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:657:in
`block in load_config_initializer'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/notifications.rb:170:in
`instrument'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:656:in
`load_config_initializer'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:614:in
`block (2 levels) in '
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:613:in
`each'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/engine.rb:613:in
`block in '
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:32:in
`instance_exec'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:32:in
`run'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:61:in
`block in run_initializers'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:50:in
`each'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:50:in
`tsort_each_child'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/initializable.rb:60:in
`run_initializers'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/application.rb:361:in
`initialize!'
/usr/share/gitlab/config/environment.rb:6:in `'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in
`require'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in
`block in require'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:257:in
`load_dependency'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies.rb:291:in
`require'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/application.rb:337:in
`require_environment!'
/usr/share/rubygems-integration/all/gems/railties-5.2.3/lib/rails/application.rb:520:in
`block in run_tasks_blocks'
Tasks: TOP => db:migrate => db:load_config => environment
Deleting this file too, continue on db:migrate task, but this one fails too.
Error MSG:
(some output ommited)
== 20190723105753 AddIndexOnIdentitiesLowerExternUidAndProvider: migrating
-- transaction_open?()
-> 0.s
-- index_exists?(:identities, "lower(extern_uid), provider",
{:name=>"index_on_identities_lower_extern_uid_and_provider",
:algorithm=>:concurrently})
-> 0.0033s
-- execute("SET statement_timeout TO 0")
-> 0.0005s
-- add_index(:identities, "lower(extern_uid), provider",
{:name=>"index_on_identities_lower_extern_uid_and_provider",
:algorithm=>:concurrently})
-- execute("RESET ALL")
-> 0.0004s
rake aborted!
StandardError: An error has occurred, all later migrations canceled:
PG::UndefinedColumn: ERROR: column "lower(extern_uid), provider" does not exist
: CREATE INDEX CONCURRENTLY
"index_on_identities_lower_extern_uid_and_provider" ON "identities"
("lower(extern_uid), provider" )
/usr/share/rubygems-integration/all/gems/activerecord-5.2.3/lib/active_record/connection_adapters/postgresql/database_statements.rb:75:in
`async_exec'
/usr/share/rubygems-integration/all/gems/activerecord-5.2.3/lib/active_record/connection_adapters/postgresql/database_statements.rb:75:in
`block (2 levels) in execute'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies/interlock.rb:48:in
`block in permit_concurrent_loads'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/concurrency/share_lock.rb:187:in
`yield_shares'
/usr/share/rubygems-integration/all/gems/activesupport-5.2.3/lib/active_support/dependencies/interlock.rb:47:in
`permit_concurrent_loads'
/usr/share/rubygems-integration/all/gems/activerecord-5.2.3/lib/active_record/connection_adapters/postgresql/database_statements.rb:74:in
`block in execute'
Bug#944596: gitlab: Upgrading to 12.2.9-1 fails
Package: gitlab Version: 12.2.9-1+fto10+1 Followup-For: Bug #944596 Hi, I have exactly the same problem. Installation are originally on gitlab 8, until yesterday working without problem on 12.1 NoMethodError: undefined method `mysql?' for Gitlab::Database:Module /usr/share/gitlab/config/initializers/active_record_mysql_timestamp.rb:7:in `' Tasks: TOP => db:migrate => db:load_config => environment Maybe this file needs to be deleted...? -- System Information: Debian Release: bullseye/sid APT prefers buster-fasttrack APT policy: (500, 'buster-fasttrack'), (500, 'buster-backports'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.62-mod-std-ipv6-64-rescue (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gitlab depends on: ii asciidoctor 2.0.10-2 ii bc 1.07.1-2+b2 ii bundler 1.17.3-3 ii bzip21.0.8-2 ii dbconfig-pgsql 2.0.13 ii debconf [debconf-2.0]1.5.73 ii exim4-daemon-light [mail-transport-agent]4.92.3-1 ii gitlab-common12.2.9-1+fto10+1 ii gitlab-workhorse 8.8.1+debian-1~bpo10+1 ii libjs-bootstrap4 [node-bootstrap]4.3.1+dfsg2-4 ii libjs-pdf1.5.188+dfsg-1~bpo10+1 ii libjs-popper.js [node-popper.js] 1.14.6+ds2-2 ii libjs-uglify 2.8.29-6 ii lsb-base 11.1.0 ii nginx1.16.1-2 ii nginx-full [nginx] 1.16.1-2 ii node-autosize4.0.2~dfsg1-3 ii node-axios 0.19.0+dfsg-2 ii node-brace-expansion 1.1.8-1 ii node-cache-loader2.0.1-2 ii node-chart.js2.7.3+dfsg-5 ii node-core-js 2.4.1-2 ii node-css-loader 1.0.1-1 ii node-d3 4.13.0-10 ii node-d3-array1.2.4-2 ii node-d3-axis 1.0.12-2 ii node-d3-brush1.0.6-3 ii node-d3-ease 1.0.5-2 ii node-d3-scale1.0.7-6 ii node-d3-selection1.4.0-5 ii node-d3-shape1.3.5-2 ii node-d3-time 1.0.11-3 ii node-d3-time-format 2.1.3-2 ii node-d3-transition 1.2.0-4 ii node-dateformat 3.0.0-1 ii node-exports-loader 0.7.0-2 ii node-file-loader 3.0.1-1 ii node-fuzzaldrin-plus 0.5.0+dfsg-3 ii node-glob7.1.3-2 ii node-imports-loader 0.8.0-2 ii node-jed 1.1.1-1 ii node-jquery 3.4.0+dfsg-1 ii node-jquery-ujs 1.2.2-2 ii node-jquery.waitforimages2.4.0+ds-1 ii node-js-cookie 2.2.0-2 ii node-jszip 3.2.2+dfsg-1 ii node-jszip-utils 0.0.2+dfsg-1 ii node-mousetrap 1.6.1+ds-1 ii node-pikaday 1.8.0-1 ii node-raven-js3.22.1+dfsg-2 ii node-raw-loader 1.0.0-2 ii node-three-orbit-controls82.1.0-2 ii node-three-stl-loader1.0.6-2 ii node-timeago.js 3.0.2+dfsg-5 ii node-underscore 1.9.1~dfsg-1 ii node-url-loader 1.1.2-1 ii node-vue-resource1.5.1+dfsg-5 ii node-webpack-stats-plugin0.2.1-1 ii node-worker-loader 2.0.0-2 ii nodejs 10.17.0~dfsg-2 ii openssh-client
Bug#914496: gitlab-shell: Fail on gitlab-shell on git push
Package: gitlab-shell Version: 8.3.3+dfsg-1 Severity: grave Justification: renders package unusable Doing a git push on a repository connected to gitlab, I receive this error: BloudFire:repository maqui$ git push origin /usr/share/gitlab-shell/bin/gitlab-shell:10:in `require_relative': cannot load such file -- /usr/share/gitlab-shell/bin/gitlab_init (LoadError) from /usr/share/gitlab-shell/bin/gitlab-shell:10:in `' fatal: No se pudo leer del repositorio remoto. Testing on gitlab server, the file gitlab_init does not exist on this repository. They are a gitlab_init.rb on /usr/lib/ruby/vendor_ruby folder. With this fail, gitlab is unusable, because I cannot commit to the repository or download from it. Thanks, -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.23--grs-ipv6-64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968), LANGUAGE=en_GB:en (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gitlab-shell depends on: ii libc6 2.27-8 ii ruby 1:2.5.1 gitlab-shell recommends no packages. gitlab-shell suggests no packages. -- debconf-show failed
Bug#898228: ruby-gitaly: Required dependency not specified on deb package
Package: ruby-gitaly Version: 0.99.0+dfsg-1 Severity: grave Justification: renders package unusable Gitaly gem requires grpc gem in version 1.10 to work, but, deb package doesn't force installation of this package. In that case, ruby-gitaly is unusable. Error message: Bundler could not find compatible versions for gem "grpc": In Gemfile: grpc (~> 1.3) gitaly-proto (~> 0.88) was resolved to 0.99.0, which depends on grpc (~> 1.10) Could not find gem 'grpc (~> 1.10)', which is required by gem 'gitaly-proto (~> 0.88)', in any of the sources. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ruby-gitaly depends on: ii ruby 1:2.5.1 ii ruby-google-protobuf 3.2.0-2+b2 ii ruby-grpc 1.3.2+debian-4+b1 ruby-gitaly recommends no packages. ruby-gitaly suggests no packages. -- no debconf information
Bug#894138: gitlab: 10.5.6 Problem compiling assets on post-install
Package: gitlab Version: 10.5.6+dfsg-1 Severity: grave Justification: renders package unusable Hi, Installing gitlab 10.5.6 do not work because a problem on sprockets. This error is also on old 10.5.5 and 9.5.4 versions. Thanks, Precompiling assets... /usr/lib/ruby/vendor_ruby/builder/xchar.rb:111: warning: constant ::Fixnum is deprecated rake aborted! Sprockets::Error: manifest requires environment for compilation /var/lib/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/manifest.rb:178:in `compile' /var/lib/gems/2.5.0/gems/rake-12.3.1/exe/rake:27:in `' Tasks: TOP => assets:precompile (See full trace by running task with --trace) dpkg: error processing package gitlab (--configure): installed gitlab package post-installation script subprocess returned error exit status 1 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii adduser 3.117 ii asciidoctor 1.5.5-1 ii bc1.07.1-2 ii bundler 1.16.1-1 ii dbconfig-pgsql2.0.9 ii debconf [debconf-2.0] 1.5.66 ii git 1:2.16.3-1 ii gitlab-shell 6.0.4-1 ii gitlab-workhorse 3.8.0+debian-1 ii libjs-chartjs 1.0.2-1 ii libjs-clipboard 1.4.2-1 ii libjs-graphael0.5+dfsg-1 ii libjs-jquery-atwho1.5.4+dfsg.1-2 ii libjs-jquery-caret.js 0.3.1+dfsg.1-2 ii libjs-jquery-nicescroll 3.6.6-1 ii libjs-pdf 1.5.188+dfsg-1 ii libjs-xterm 2.7.0+ds1-1 ii lsb-base 9.20170808 ii nginx 1.13.10-1 ii nginx-full [nginx]1.13.10-1 ii node-babel-core 6.26.0+dfsg-3 ii node-babel-eslint 7.2.3-2 ii node-babel-loader 7.1.2-4 ii node-babel-plugin-transform-define1.3.0-2 ii node-babel-preset-latest 6.26.0+dfsg-3 ii node-babel-preset-stage-2 6.26.0+dfsg-3 ii node-bootstrap-sass 3.3.7-1 ii node-core-js 2.4.1-2 ii node-d3-array 1.2.1-3 ii node-d3-axis 1.0.8-3 ii node-d3-brush 1.0.4-3 ii node-d3-scale 1.0.6-3 ii node-d3-selection 1.1.0-3 ii node-d3-shape 1.2.0-2 ii node-d3-time 1.0.7-2 ii node-d3-time-format 2.0.5-2 ii node-debug3.1.0-1 ii node-exports-loader 0.6.4-1 ii node-file-loader 0.11.2-1 ii node-glob 7.1.2-5 ii node-imports-loader 0.7.1-1 ii node-jed 1.1.1-1 ii node-jquery 2.2.4+dfsg-2 ii node-js-cookie2.2.0-1 ii node-jszip3.1.4+dfsg-1 ii node-jszip-utils 0.0.2+dfsg-1 ii node-katex0.8.3+dfsg-1 ii node-lie 3.1.1+dfsg-1 ii node-marked 0.3.9+dfsg-1 ii node-mousetrap1.6.1+ds-1 ii node-raw-loader 0.5.1-1 ii node-stats-webpack-plugin 0.6.1-1 ii node-underscore 1.8.3~dfsg-1 ii node-url-loader 0.5.9-1 ii nodejs8.9.3~dfsg-12 ii npm 1.4.21+ds-2 ii openssh-client1:7.6p1-4 ii postfix [mail-transport-agent]3.3.0-1 ii postgresql-client 10+190 ii postgresql-client-10 [postgresql-client] 10.3-2 ii postgresql-contrib10+190 ii rake 12.3.1-1 ii redis-server 5:4.0.8-2 ii ruby 1:2.5.1 ii ruby-ace-rails-ap 4.1.1-1 ii ruby-acts-as-taggable-on 5.0.0-2 ii ruby-addressable 2.5.2-1 ii ruby-akismet
Bug#893867: gitlab: Dpkg fail to configure gitlab package. Problem with some Ruby Gems on 10.5
Package: gitlab Version: 10.5.5+dfsg-2 Severity: grave Justification: renders package unusable Gitlab 10.5.5+dfsg-1 and 10.5.5+dfsg-2 fails to install. The machine have a gitlab 9.5.4 installed (since Experimental upload), upgrading to 10.5.5 on unstable. This is the error on installation: Running final rake tasks and tweaks... gitlab_production database is not empty, skipping gitlab setup /usr/lib/ruby/vendor_ruby/builder/xchar.rb:111: warning: constant ::Fixnum is deprecated rake aborted! NameError: uninitialized constant Rouge::Lexers::Plantuml /usr/share/gitlab/config/initializers/plantuml_lexer.rb:2:in `' /usr/share/gitlab/config/environment.rb:5:in `' /var/lib/gems/2.5.0/gems/rake-12.3.1/exe/rake:27:in `' Tasks: TOP => db:migrate => environment (See full trace by running task with --trace) dpkg: error processing package gitlab (--configure): installed gitlab package post-installation script subprocess returned error exit status 1 The xchar.rb message appears from 9.5.4 version. Also, if it's relevant, the latest 9.5.4+dfsg-7 does not install too, with another error: Precompiling assets... /usr/lib/ruby/vendor_ruby/builder/xchar.rb:111: warning: constant ::Fixnum is deprecated DEPRECATION WARNING: `jws_private_key` has been replaced by `signing_key` and will be removed in a future version, please remove it from config/initializers/doorkeeper_openid_connect.rb rake aborted! Sprockets::Error: manifest requires environment for compilation /var/lib/gems/2.5.0/gems/sprockets-3.7.1/lib/sprockets/manifest.rb:178:in `compile' /var/lib/gems/2.5.0/gems/rake-12.3.1/exe/rake:27:in `' Tasks: TOP => assets:precompile (See full trace by running task with --trace) dpkg: error processing package gitlab (--configure): installed gitlab package post-installation script subprocess returned error exit status 1 10.5.5 tested only on one machine. 9.5.4 error is tested on two different installations. None of them are clear machines without any old gitlab version installed. Thanks, -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii adduser 3.117 ii asciidoctor 1.5.5-1 ii bc1.07.1-2 ii bundler 1.16.1-1 ii dbconfig-pgsql2.0.9 ii debconf [debconf-2.0] 1.5.66 ii git 1:2.16.2-1 ii gitlab-shell 6.0.4-1 ii gitlab-workhorse 3.8.0+debian-1 ii libjs-chartjs 1.0.2-1 ii libjs-clipboard 1.4.2-1 ii libjs-graphael0.5+dfsg-1 ii libjs-jquery-atwho1.5.4+dfsg.1-2 ii libjs-jquery-caret.js 0.3.1+dfsg.1-2 ii libjs-jquery-nicescroll 3.6.6-1 ii libjs-pdf 1.5.188+dfsg-1 ii libjs-xterm 2.7.0+ds1-1 ii lsb-base 9.20170808 ii nginx 1.13.10-1 ii nginx-full [nginx]1.13.10-1 ii node-babel-core 6.26.0+dfsg-3 ii node-babel-eslint 7.2.3-2 ii node-babel-loader 7.1.2-4 ii node-babel-plugin-transform-define1.3.0-2 ii node-babel-preset-latest 6.26.0+dfsg-3 ii node-babel-preset-stage-2 6.26.0+dfsg-3 ii node-bootstrap-sass 3.3.7-1 ii node-core-js 2.4.1-2 ii node-d3-array 1.2.1-3 ii node-d3-axis 1.0.8-3 ii node-d3-brush 1.0.4-3 ii node-d3-scale 1.0.6-3 ii node-d3-selection 1.1.0-3 ii node-d3-shape 1.2.0-2 ii node-d3-time 1.0.7-2 ii node-d3-time-format 2.0.5-2 ii node-debug3.1.0-1 ii node-exports-loader 0.6.4-1 ii node-file-loader 0.11.2-1 ii node-glob 7.1.2-5 ii node-imports-loader 0.7.1-1 ii node-jed 1.1.1-1 ii node-jquery 2.2.4+dfsg-2 ii node-js-cookie2.2.0-1 ii node-jszip3.1.4+dfsg-1 ii
Bug#763148: Prevent migration to jessie
On 14Oct05:2254+0200, Andreas Barth wrote: Also, the re-evaluation happened. It however didn't had the outcome you wanted (basically because the web browser needs so many security updates which only could be done by backporting all of it that the embedded copy doesn't make any difference - this is an exceptional thing which does happen but not very often. I can understand it, and of course it's the call of the security team how to ensure that Debian has security updates. I hadn't know that at the time I though about the possibility, otherwise I would have already achived at that moment at the conclusion). Where are the minutes of the re-evaluation? -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep24:1951+0200, Michael Biebl wrote: Am 24.09.2014 um 18:45 schrieb Michael Biebl: Craig was so kind and provided me with access to the VM images. With that image I was able to reproduce the upgrade failure. I checked the systemd state before the upgrade and noticed that sstemd-logind.service had failed to start due to dbus not being installed. So I made a second test-upgrade and I installed the dbus package beforehand. With dbus being installed and dbus.service running, the dist-upgrade was successful. There might be an issue with the internal dbus socket, that systemd uses for communication. My guess is, that with dbus.service running, it can fall back to the system bus for communication in case there is something wrong with that internal dbus socket. One more observation: The udev package is configured before systemd, i.e. udev.postinst runs before systemd.postinst (systemd.postinst run daemon-reexec). The restart of udev (invoke-rc.d udev restart) is what's failing. I tried it manually via root@vp9cb:~# systemctl restart udev.service Failed to wait for response: Success If I manually reexec systemd via systemctl daemon-reexec, I can successfully finish the dist-upgrade via dpkg --configure -a and apt-get -f install Full typescript attached Maybe I should be a full-time tester--I seem to be pretty good at it. I built another vm from the D-I beta, pointed sources.list at sid, and ran aptitude update, all as before. This time, though, I held all updates while installing dbus 1.8.8-1 and libcap-ng0 0.7.4-2 with nominal results, then unheld the updates again (aptitude : if it matters) and ran the aptitude dist-upgrade, which failed as before. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep24:1424-0400, David L. Craig wrote: Maybe I should be a full-time tester--I seem to be pretty good at it. I built another vm from the D-I beta, pointed sources.list at sid, and ran aptitude update, all as before. This time, though, I held all updates while installing dbus 1.8.8-1 and libcap-ng0 0.7.4-2 with nominal results, then unheld the updates again (aptitude : if it matters) and ran the aptitude dist-upgrade, which failed as before. Then I reran the entire test except I added a reboot after the apt-get install dbus and, even though the download of libdbus-1-3 failed, the rest of the dist-upgrade was fine. So I perceive the start of the dbus.service is not automatic. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep23:0023+0200, Michael Biebl wrote: Yeah, this would be perfect By way of a feasibility test, I had virt-manager Shut Down == Save the a762146 vm at its ready for first login state and have put the tarball of the 124MB file it created in /var/lib/libvirt/qemu/save up at http://dlc.casita.net/~dlc/762146/a762146.vmsave.test.tar for you to retrieve. I expect you will also need the hard drive image which compressed into 5.3 GB, so we have a logistical difficulty there. I am attaching the domain xml and parted print free output in sectors for the virtual disk. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ a762146.xml.tar Description: Unix tar archive Model: ATA QEMU HARDDISK (scsi) Disk /dev/sdb: 4096s Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start EndSize File system Name Flags 34s2047s 2014s Free Space 1 2048s 3905535s 3903488s linux-swap(v1) VS 2 3905536s 40957951s 37052416s ext4VV 40957952s 40959966s 2015s Free Space signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep23:0956-0400, David L. Craig wrote: By way of a feasibility test, I had virt-manager Shut Down == Save the a762146 vm at its ready for first login state and have put the tarball of the 124MB file it created in /var/lib/libvirt/qemu/save up at http://dlc.casita.net/~dlc/762146/a762146.vmsave.test.tar for you to retrieve. I expect you will also need the hard drive image which compressed into 5.3 GB, so we have a logistical difficulty there. I am attaching the domain xml and parted print free output in sectors for the virtual disk. Scratch that--those files were taking up too much space. Instead, I offer you an invitation to send me an encrypted email to which I will likewise reply with the details of how to SFTP the files (522MB, but you should get at least 4 MB/sec bandwidth from this end) for the actual vm condition you requested (even better--I did an aptitude --download-only --dist-upgrade prior to the save). Also, I ran it beforehand in the constrained configuration (1 GB root, no swap) to ensure this fails identically, and it obliged me. I hope this works, er, you can get a successful test. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
Another datum: I decided to try switching back to systemd-sysv on my primary bare-metal Sid and the update was textbook: ii libpam-systemd:amd64 215-4 ii libsystemd-id128-0:amd64 215-4 ii libsystemd-journal0:amd64 215-4 ii libsystemd-login0:amd64 215-4 ii libsystemd-login0:i386215-4 ii libsystemd0:amd64 215-4 ii libsystemd0:i386 215-4 ii systemd 215-4 ii systemd-shim 8-2 ii systemd-sysv 215-4 ii systemd-ui3-2 -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep23:1719-0400, David L. Craig wrote: Another datum: I decided to try switching back to systemd-sysv on my primary bare-metal Sid and the update was textbook: ii libpam-systemd:amd64 215-4 ii libsystemd-id128-0:amd64 215-4 ii libsystemd-journal0:amd64 215-4 ii libsystemd-login0:amd64 215-4 ii libsystemd-login0:i386215-4 ii libsystemd0:amd64 215-4 ii libsystemd0:i386 215-4 ii systemd 215-4 ii systemd-shim 8-2 ii systemd-sysv 215-4 ii systemd-ui3-2 So I tried running the test case on the bare metal again, but it still fails. :-( -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep21:2011+0200, Michael Biebl wrote: What were the exact error messages you got? Please provide the dpkg log and the output from journalctl -alb I ran the test case again and obtained the same results from aptitude dist-upgrade and began receiving the kernel messages about journald as well; however, the system performed a telinit 6 nominally after I had executed your requested journalctl -alb redirecting stdout and stderr to a file. When in single user mode, did you also try to run dpkg --configure -a or apt-get -f install to fix the broken package state? While dpkg --configure -a complained about nothing, acl and systemd remained broken; however, apt-get -f install was successful. Attached are the dpkg and apt logs. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ a762146.journalctl-alb.out.gz Description: application/gzip a762146.dpkg.log.gz Description: application/gzip a762146.apt-term.log.gz Description: application/gzip a762146.apt-history.log.gz Description: application/gzip signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep23:0016+0200, Michael Biebl wrote: Am 22.09.2014 um 23:23 schrieb David L. Craig: On 14Sep21:2011+0200, Michael Biebl wrote: What were the exact error messages you got? Please provide the dpkg log and the output from journalctl -alb I ran the test case again and obtained the same results from aptitude dist-upgrade and began receiving the kernel messages about journald as well; however, the system performed a telinit 6 nominally after I had executed your requested journalctl -alb redirecting stdout and stderr to a file. I wasn't able to reproduce the failure. Would it be possible for you to create a VM image I can download? Hmmm... Probably, once I figure out how. You want it just before the dist-upgrade command? -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
On 14Sep22:0005+0200, Michael Biebl wrote: Am 21.09.2014 um 23:28 schrieb David L. Craig: No, but, as the report mentioned, the vm failure was preceded by a similar result doing the daily update of the main non-vm Sid instance on the box, which is why I reproduced it using reproducible and minimal inputs. Are you too resource-challenged to run it yourselves? No, I've done dozens of test-upgrades on bare metal and VMs (vbox, vmware) and haven't run into this. So we either need someone who can reproduce the problem or exact steps how to reproduce it. It seems most likely to me the difference will be found in the processor, or perhaps its firmware. The box is from Gigabyte but it's configured for reliability, not speed. The work-in-process cookbook I've been putting together will walk you through what was being done with screenshots in case that is useful information. I put the current document snapshot up for this bug. You can download the 35 MB tarball from http://dlc.casita.net/~dlc/762146/vp9cb-20140921.tar or just click through the HTML by going to http://dlc.casita.net/~dlc/762146/vp9cb/index.html and see what happened in subsection 2-3. Let me know if there is a specific test case you want me to exercise and I'll do my best to get you the data. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
Package: udev Version: 215-4 Severity: grave Installed Beta 1 D-I amd64 netinst without mirror or standard utils in preparation for dist-upgrade to Sid using aptitude with sources.list: deb ftp://debian.csail.mit.edu/debian/ sid main udev and aptitude reported replacing 208-6. udev fails first during configure after systemd incurs systemd-journald.service watchdog timeout! Next systemd fails to configure, then cron does the same. At the conclusion of dist-upgrade, all three are broken and reportbug cannot be force installed. In single, used aptitude to uninstall systemd-sysv and install systemd-shim, enabling all other updates to install nominally. Platform is a virtual machine under current Sid using qemu and kvm on a quad-core Intel. That system incurred a similar outcome from its daily update roughly 12 hours previously and recovered with the same remediation used for the virtual machine. -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron
Correction: udev and systemd reported replacing 208-6. ^^^ not aptitude -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ signature.asc Description: Digital signature
Bug#684952: nvidia-glx: startx blackens screen, keyboard ineffective save for altSysReq
On 12Aug15:1037+0200, Andreas Beckmann wrote: On 2012-08-15 09:48, David L. Craig wrote: I updated all the nvidia packages when I saw the new versions but the problem persists. I am including the most recent kern.log Kernel: Linux 3.2.0-3-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Please try the non-rt kernel. That is working, albeit differently than under Linux Mint XFCE 13. Please try a minimal xorg.conf as described in /usr/share/doc/nvidia-glx/README.Debian.gz and test using a single display without twinview first. If that works, slowly add more options (if you need them). That option was necessary to get nvidia to work under Mint. It causes a problem under Sid with 3.2.0-3-rt-amd64 and 3.2.0-3-amd64. 3.2.0-3-amd64 works with 1024x768 but not with 1152x864. However, I had to comment-out my console-setup VGA 8x8 defaults because nvidia doesn't show all 50 lines as nouveau does. Where is that dark magic documented? 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV43 [GeForce 6600] [10de:0141] (rev a2) (prog-if 00 [VGA controller]) That's an old card that should also work with nvidia-glx-legacy-173xx Do you want me to explore the behavior of nvidia-glx-legacy-173xx? What was the last working version? Appended is hopefully sufficient diagnostic information about the Mint environment. If nothing of the above helps, Nvidia's bug reporting instructions are here: http://www.nvnews.net/vbulletin/showthread.php?t=46678 Please post a link to a thread in their forum to this Debian bug. I'm a tad confused. Is 3.2.0-3-rt-amd64 unsupported by nVidia or Debian? That is, should I report the rt bug there or not? Andreas Thank you so much for your support of this software!!! -- May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your beliefs, then. Because you certainly can't rearrange the universe. __--from_Nightfall_by_Asimov/Silverberg_ # dlc@dlc-dt[LMDX]~/Desktop $ uname -a Linux dlc-dt 3.2.0-23-lowlatency #31-Ubuntu SMP PREEMPT Wed Apr 11 02:24:03 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux dlc@dlc-dt[LMDX]~/Desktop $ ll /usr/lib/nvidia-current /lib/nvidia-current /lib/nvidia-current: total 12K drwxr-xr-x 2 root root 4.0K Jul 26 17:37 ./ drwxr-xr-x 22 root root 4.0K Jul 26 19:59 ../ -rw-r--r-- 1 root root 316 Apr 12 15:15 modprobe.conf /usr/lib/nvidia-current: total 72M drwxr-xr-x 6 root root 4.0K Jul 26 17:37 ./ drwxr-xr-x 217 root root 52K Aug 2 02:26 ../ -rw-r--r-- 1 root root 27 Apr 12 15:15 XvMCConfig -rw-r--r-- 1 root root0 Apr 12 15:15 alt_ld.so.conf drwxr-xr-x 2 root root 4.0K Jul 26 17:37 bin/ -rw-r--r-- 1 root root 50 Apr 12 15:15 ld.so.conf lrwxrwxrwx 1 root root 10 Apr 12 15:15 libGL.so - libGL.so.1 lrwxrwxrwx 1 root root 15 Apr 12 15:15 libGL.so.1 - libGL.so.295.40 -rw-r--r-- 1 root root 1.1M Apr 12 15:15 libGL.so.295.40 lrwxrwxrwx 1 root root 14 Apr 12 15:15 libOpenCL.so - libOpenCL.so.1 lrwxrwxrwx 1 root root 16 Apr 12 15:15 libOpenCL.so.1 - libOpenCL.so.1.0 lrwxrwxrwx 1 root root 18 Apr 12 15:15 libOpenCL.so.1.0 - libOpenCL.so.1.0.0 -rw-r--r-- 1 root root 21K Apr 12 15:15 libOpenCL.so.1.0.0 lrwxrwxrwx 1 root root 23 Apr 12 15:15 libXvMCNVIDIA.so - libXvMCNVIDIA.so.295.40 lrwxrwxrwx 1 root root 23 Apr 12 15:15 libXvMCNVIDIA.so.1 - libXvMCNVIDIA.so.295.40 -rw-r--r-- 1 root root 156K Apr 12 15:15 libXvMCNVIDIA.so.295.40 lrwxrwxrwx 1 root root 23 Apr 12 15:15 libXvMCNVIDIA_dynamic.so.1 - libXvMCNVIDIA.so.295.40 lrwxrwxrwx 1 root root 17 Apr 12 15:15 libcuda.so - libcuda.so.295.40 lrwxrwxrwx 1 root root 17 Apr 12 15:15 libcuda.so.1 - libcuda.so.295.40 -rw-r--r-- 1 root root 8.3M Apr 12 15:15 libcuda.so.295.40 lrwxrwxrwx 1 root root 15 Apr 12 15:15 libnvcuvid.so - libnvcuvid.so.1 lrwxrwxrwx 1 root root 20 Apr 12 15:15 libnvcuvid.so.1 - libnvcuvid.so.295.40 -rw-r--r-- 1 root root 2.2M Apr 12 15:15 libnvcuvid.so.295.40 lrwxrwxrwx 1 root root 18 Apr 12 15:15 libnvidia-cfg.so - libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 23 Apr 12 15:15 libnvidia-cfg.so.1 - libnvidia-cfg.so.295.40 -rw-r--r-- 1 root root 134K Apr 12 15:15 libnvidia-cfg.so.295.40 lrwxrwxrwx 1 root root 23 Apr 12 15:15 libnvidia-compiler.so - libnvidia-compiler.so.1 lrwxrwxrwx 1 root root 28 Apr 12 15:15 libnvidia-compiler.so.1 - libnvidia-compiler.so.295.40 -rw-r--r-- 1 root root 27M Apr 12 15:15 libnvidia-compiler.so.295.40 -rw-r--r-- 1 root root 34M Apr 12 15:15 libnvidia-glcore.so.295.40 lrwxrwxrwx 1 root root 17 Apr 12 15:15 libnvidia-ml.so - libnvidia-ml.so.1 lrwxrwxrwx 1 root root 22 Apr 12 15:15 libnvidia-ml.so.1 - libnvidia-ml.so.295.40 -rw-r--r-- 1 root root 243K Apr 12 15:15 libnvidia-ml.so.295.40 -rw-r--r-- 1 root root 12K Apr 12 15
Bug#684952: nvidia-glx: startx blackens screen, keyboard ineffective save for altSysReq
Package: nvidia-glx Version: 302.17-3 Severity: critical Justification: breaks the whole system I had installed Sid into an available partition and X was happy with nouveau. nvidia was functioning well under Linux Mint Xfce 13. After installing the nvidia packages and porting the Mint xorg.conf into /etc/X11, I found I had a guaranteed to manifest problem. After dozens of tests and changes, it is clear the impact is to more than just the keyboard/monitor (ssh sessions receive some setterm -msg on -msglevel 8 outputs) but altSysReq REISUB doesn't provide much diagnostic output. Mint works using 1152x864, Sid works with neither that or 1024x768. -- Package-specific info: uname -a: Linux dlc-dt 3.2.0-3-rt-amd64 #1 SMP PREEMPT RT Mon Jul 23 03:37:45 UTC 2012 x86_64 GNU/Linux /proc/version: Linux version 3.2.0-3-rt-amd64 (Debian 3.2.23-1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP PREEMPT RT Mon Jul 23 03:37:45 UTC 2012 /proc/driver/nvidia/version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 302.17 Tue Jun 12 16:03:22 PDT 2012 GCC version: gcc version 4.6.3 (Debian 4.6.3-8) lspci 'VGA compatible controller [0300]': 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV43 [GeForce 6600] [10de:0141] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Device [196e:021f] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 4 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at f000 (32-bit, non-prefetchable) [size=64M] Region 1: Memory at e000 (64-bit, prefetchable) [size=256M] Region 3: Memory at f600 (64-bit, non-prefetchable) [size=16M] [virtual] Expansion ROM at f400 [disabled] [size=128K] Capabilities: access denied Kernel driver in use: nvidia dmesg: [0.00] No AGP bridge found [0.00] No AGP bridge found [0.00] Console: colour VGA+ 80x25 [0.474228] vgaarb: device added: PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none [0.474228] vgaarb: loaded [0.474228] vgaarb: bridge control possible :01:00.0 [0.984332] Linux agpgart interface v0.103 [7.365727] nvidia: module license 'NVIDIA' taints kernel. [7.567856] nvidia :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [7.567863] nvidia :01:00.0: setting latency timer to 64 [7.567870] vgaarb: device changed decodes: PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem [7.567993] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 302.17 Tue Jun 12 16:03:22 PDT 2012 OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Aug 13 21:00 /etc/alternatives/glx - /usr/lib/nvidia lrwxrwxrwx 1 root root 43 Aug 13 21:00 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Aug 13 21:00 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 51 Aug 13 21:00 /etc/alternatives/glx--libXvMCNVIDIA.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 59 Aug 13 21:00 /etc/alternatives/glx--libXvMCNVIDIA_dynamic.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 51 Aug 13 21:00 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 25 Aug 13 21:00 /etc/alternatives/glx--linux-libglx.so - /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 36 Aug 13 21:00 /etc/alternatives/glx--nvidia-bug-report.sh - /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 29 Aug 13 21:00 /etc/alternatives/glx--nvidia_drv.so - /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 23 Aug 13 21:00 /etc/alternatives/nvidia - /usr/lib/nvidia/current lrwxrwxrwx 1 root root 51 Aug 13 21:00 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 51 Aug 13 21:00 /etc/alternatives/nvidia--libGL.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1 lrwxrwxrwx 1 root root 59 Aug 13 21:00 /etc/alternatives/nvidia--libXvMCNVIDIA.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libXvMCNVIDIA.so.1 lrwxrwxrwx 1 root root 67 Aug 13 21:00 /etc/alternatives/nvidia--libXvMCNVIDIA_dynamic.so.1-x86_64-linux-gnu - /usr/lib/x86_64-linux-gnu/nvidia/current/libXvMCNVIDIA_dynamic.so.1 lrwxrwxrwx 1 root root 33 Aug 13 21:00 /etc/alternatives/nvidia--libglx.so - /usr/lib/nvidia/current/libglx.so lrwxrwxrwx 1 root root 59 Aug 13 21:00
Bug#326416: kimdaba: build-depends on LIBRARIES and Priority: required packages
Debian is a cooperative project based on volunteer work, and this is precisely this is what it makes sucht a great endeavour. Just like in any other volunteer community, progress is based on mutual respect and appreciation of individual work. The disrespectful manners in which this bug report was redacted show It's author's lack of appreciation for the work of others. Disrespect, bigotry and rudeness do much more harm to a cooperative project like Debian than a FTBFS bug. I highly appreciate the work of Adeodato Simó, he does an invaluable contribution to Debian by contributing his time and knowledge. So does my sponsor, and so do I. Respect is the glue that binds this community. This bug report lacks any proper description of the problem and no hints of how to solve it. This is especially relevant as it comes from an experienced Debian Developer, from whom I would have expected a helpuful bug report. This bug will be fixed when the new upstream version is packaged and uploaded, I expect this process to last no more than five days. Thank you for reporting this bug, David L. Moreno On 9/3/05, Adeodato Simó [EMAIL PROTECTED] wrote: Package: kimdaba Version: 2.0-4 Severity: serious Justification: FTBFS Maintainer, please fix your moronic Build-Depends line, kthxbye. Sponsor, shame on you for uploading such package to our archive. -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 He has never been known to use a word that might send a reader to the dictionary. -- William Faulkner (about Ernest Hemingway) -- David L. Moreno. http://www-gsi.dec.usc.es/~dave
