Bug#1053525: libphp-adodb too old for php8.2
Package: libphp-adodb Version: 5.21.4-1 PHP 8.2 requires 5.22.6 https://adodb.org/dokuwiki/doku.php?id=v5:php_compatibility_status Since 8.2 is in stable, that leaves libphp-adodb as unusable.
Bug#982998: chkrootkit chkproc uses incorrect value for max_pid
Confirming issue. Also still present in chkrootkit_0.55-1_amd64.deb
Bug#926729: Missing Breaks on ruby-bootsnap
Package: gitlab Version: 11.8.3-1 Once a fixed Gemfile so that ruby-pg was loading (needs to check for id postgresql not postgres for some weird reason) I ran into this bug. Removing ruby-bootsnap fixed as the maintainer pointed out to me in private. Creating this bug report so it doesn’t get forgotten as it’s not a trivial bug to track down at all. Bundle complete! 186 Gemfile dependencies, 315 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 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 rake aborted! LoadError: cannot load such file -- kubeclient/oidc_auth_provider /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in `block in require' /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:258:in `load_dependency' /usr/share/gitlab/vendor/gems/activesupport-5.1.6.1/lib/active_support/dependencies.rb:292:in `require' /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:81:in `block (2 levels) in require' /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:76:in `each' /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:76:in `block in require' /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:65:in `each' /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:65:in `require' /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler.rb:114:in `require' /usr/share/gitlab/config/application.rb:5:in `' /usr/share/gitlab/Rakefile:5:in `require' /usr/share/gitlab/Rakefile:5:in `' (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 Errors were encountered while processing: gitlab root:~# ls -l /usr/lib/ruby/vendor_ruby/kubeclient/ total 72 -rw-r--r-- 1 root root 22485 Mar 4 08:46 common.rb -rw-r--r-- 1 root root 5687 Mar 4 08:46 config.rb -rw-r--r-- 1 root root 483 Mar 4 08:46 entity_list.rb -rw-r--r-- 1 root root 1775 Mar 4 08:46 exec_credentials.rb -rw-r--r-- 1 root root 904 Mar 4 08:46 google_application_default_credentials.rb -rw-r--r-- 1 root root 657 Mar 4 08:46 http_error.rb -rw-r--r-- 1 root root 3408 Mar 4 08:46 missing_kind_compatibility.rb -rw-r--r-- 1 root root 1740 Mar 4 08:46 oidc_auth_provider.rb -rw-r--r-- 1 root root70 Mar 4 08:46 resource_not_found_error.rb -rw-r--r-- 1 root root 268 Mar 4 08:46 resource.rb -rw-r--r-- 1 root root78 Mar 4 08:46 version.rb -rw-r--r-- 1 root root 2594 Mar 4 08:46 watch_stream.rb root:~# head -n 11 /usr/lib/ruby/vendor_ruby/kubeclient.rb require 'json' require 'rest-client' require 'kubeclient/common' require 'kubeclient/config' require 'kubeclient/entity_list' require 'kubeclient/google_application_default_credentials' require 'kubeclient/exec_credentials' require 'kubeclient/http_error' require 'kubeclient/missing_kind_compatibility' require 'kubeclient/oidc_auth_provider’
Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing
Well I hope it comes to that personally, cause I think you have been doing a great job, it’s a TON of work to maintain all the depends you do for gitlab and honestly there are rarely issues and when they are you fix them very quickly after a report. It’s very upsetting that I now have 10 tickets in my queue because of things I can’t do on gitlab since this ticket broke everything! I have it working but barely and lots of important tasks like PRs aren’t working at all. Let me know if there is anything I can do, test or help with in any way. And thank you for all your hard work on this project! > On Mar 3, 2019, at 3:40 AM, Pirate Praveen wrote: > > On Mon, 25 Feb 2019 07:45:36 -0700 Justin Hallett > wrote: > > This ticket is bogus and should be closed and removed so that gitlab can be > > fixed in testing and restore the faith of its users. > > I think we have not received the same level of respect from the rest of the > project. Since everyone is pushing for strict interpretation of rules with no > regards to our contribution, I'm also forced to go by the strict > interpretation of rules. Once we get gitlab working with rails 5.2, and if > this bug is the only blocker, I will close this bug as bogus asserting my > rights as the maintainer. > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing
By keeping this out of testing you are really leaving those of us running it and depending on it in a real mess. To get rails 2.5 support I had to do some serious Debian badness, this really sucks, couldn’t it just be kept out of backports if that is the issue instead of causing harm to those of us that were happy with it? Not I have 3 companies that depends on this install that are all up a creek and I can’t even convert to omni (ce) cause you can’t restore a backup of a different version and type (Don’t get me started on this part). So those of us that happy using it and are now totally FUBARed, what’s the plan for us while everyone complains and discusses things and we have completely unusable installs now? Testing is for testing things after all, how could it go any place if it’s not being tested? Stable is always too old, heck it has rails 2.3 for heavens sake and php7.0. Testing is more work but it’s were I choose to run things so I can stay relevant, and in all my years running testing (over 15 years) I have never had a major package just get pulled. I couldn’t use the back ports version since it required rails 2.3, so I had to go to experimental which is nuts. Pirate Praveen has been doing a great job trying to keep up with countless depends and keeping things up to date and stable and now he is being blocked and in turn breaking every install of testing out there. This is just insane!! This ticket is bogus and should be closed and removed so that gitlab can be fixed in testing and restore the faith of its users.
Bug#918916: Unicorn not reporting proper version for gemfile?
Package: unicorn Version: 5.4.1-1 Preparing to unpack .../25-unicorn_5.4.1-1_amd64.deb ... Unpacking unicorn (5.4.1-1) over (5.4.0-1+b1) ... Setting up unicorn (5.4.1-1) ... insserv: warning: current start runlevel(s) (empty) of script `unicorn' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `unicorn' overrides LSB defaults (0 1 6). Processing triggers for gitlab (11.5.6+dfsg-1) ... Could not find gem 'unicorn (~> 5.1)' in any of the gem sources listed in your Gemfile. I tried to update the Gemfile, I even tried making the depend '>= 0’. But then dependancy have depends on it like Processing triggers for gitlab (11.5.6+dfsg-1) ... Bundler could not find compatible versions for gem "unicorn": In Gemfile: unicorn unicorn-worker-killer (~> 0.4.4) was resolved to 0.4.4, which depends on unicorn (< 6, >= 4) So I rolled back to unicorn_5.4.0-1+b1_amd64.deb and it works again. Seems something is wrong with how unicorn 5.4.1 reports its version.
Bug#914496: gitlab-shell: Fail on gitlab-shell on git push
I am also seeing the exact same issue with pull as well, I’d assume anything that uses gitlab-shell will see it. Looking at gitlab-shell it looks like it’s either missing or was renamed to /usr/lib/ruby/vendor_ruby/gitlab_init.rb And should not use require_relative? Changing line 10 of /usr/share/gitlab-shell/bin/gitlab-shell from require_relative to require fixes it. --- TS http://www.southofheaven.org/ Life begins and ends with chaos, live between the chaos!
Bug#912229: gitaly: gitlab not creating new project/repo
Is there an interim fix/patch I can do locally? The some bug seems to happen when you want to look at a commit diff as well. It seems that this line Err :connection error: desc = \"transport: Error while dialing dial unix gitaly-ruby://gitaly-ruby: connect: no such file or directory\” Is the issue, a google search tells me that should be the socket, for example transport: dial unix tmp/sockets/private/gitaly.socket: connect: no such file or directory Obviously that is a different error, but it’s pointed to the socket which makes more sense than gitaly-ruby://gitaly-ruby I’m no expert by far, so I have no idea where to look at why it’s trying to call Gitaly-ruby instead of the socket for the config, but maybe this will help someone that does understand it find a temp work around to get things running again since downgrading isn’t really an option anymore. - Justin
Bug#872838: No longer compiled with m-a as of 4.11+
Sadly it’s still not fixed. Here is an attempt on an fully updated buster system as of this morning. Different error point but still won’t compile. make -C /lib/modules/4.13.0-1-686-pae/build SUBDIRS=/usr/src/modules/dahdi/drivers/dahdi DAHDI_INCLUDE=/usr/src/modules/dahdi/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m make[3]: Entering directory '/usr/src/linux-headers-4.13.0-1-686-pae' CC [M] /usr/src/modules/dahdi/drivers/dahdi/dahdi-base.o CC [M] /usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.o /usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.c:273:2: error: unknown field ‘dev_attrs’ specified in initializer .dev_attrs = span_dev_attrs, ^ /usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.c:273:15: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .dev_attrs = span_dev_attrs, ^~ /usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.c:273:15: note: (near initialization for ‘spans_bus_type.probe’) /usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.c:711:2: error: unknown field ‘dev_attrs’ specified in initializer .dev_attrs = dahdi_device_attrs, ^ /usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.c:711:15: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .dev_attrs = dahdi_device_attrs, ^~ /usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.c:711:15: note: (near initialization for ‘dahdi_device_bus.probe’) cc1: some warnings being treated as errors /usr/src/linux-headers-4.13.0-1-common/scripts/Makefile.build:307: recipe for target '/usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.o' failed make[6]: *** [/usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.o] Error 1 /usr/src/linux-headers-4.13.0-1-common/Makefile:1529: recipe for target '_module_/usr/src/modules/dahdi/drivers/dahdi' failed make[5]: *** [_module_/usr/src/modules/dahdi/drivers/dahdi] Error 2 Makefile:145: recipe for target 'sub-make' failed make[4]: *** [sub-make] Error 2 Makefile:8: recipe for target 'all' failed make[3]: *** [all] Error 2 make[3]: Leaving directory '/usr/src/linux-headers-4.13.0-1-686-pae' Makefile:74: recipe for target 'modules' failed make[2]: *** [modules] Error 2 make[2]: Leaving directory '/usr/src/modules/dahdi' debian/rules:49: recipe for target 'binary-modules' failed make[1]: *** [binary-modules] Error 2 make[1]: Leaving directory '/usr/src/modules/dahdi' /usr/share/modass/include/common-rules.make:56: recipe for target 'kdist_build' failed make: *** [kdist_build] Error 2 BUILD FAILED! See /var/cache/modass/dahdi-source.buildlog.4.13.0-1-686-pae.1507813335 for details. Build failed. Press Return to continue… cat /var/cache/modass/dahdi-source.buildlog.4.13.0-1-686-pae.1507813335 dh clean debian/rules override_dh_auto_clean make[1]: Entering directory '/usr/src/modules/dahdi' rm -f include/dahdi/version.h rm -f dahdi/include/version.h [ ! -f Makefile ] || /usr/bin/make dist-clean || true make[2]: Entering directory '/usr/src/modules/dahdi' /usr/bin/make -C /lib/modules/4.13.0-1-686-pae/build SUBDIRS=/usr/src/modules/dahdi/drivers/dahdi DAHDI_INCLUDE=/usr/src/modules/dahdi/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes clean make[3]: Entering directory '/usr/src/linux-headers-4.13.0-1-686-pae' make[3]: Leaving directory '/usr/src/linux-headers-4.13.0-1-686-pae' /usr/bin/make -C drivers/dahdi/firmware clean make[3]: Entering directory '/usr/src/modules/dahdi/drivers/dahdi/firmware' rm -f dahdi-fw-*.o make[3]: Leaving directory '/usr/src/modules/dahdi/drivers/dahdi/firmware' /usr/bin/make -C /lib/modules/4.13.0-1-686-pae/build M='/usr/src/modules/dahdi/drivers/dahdi/oct612x' clean make[3]: Entering directory '/usr/src/linux-headers-4.13.0-1-686-pae' make[3]: Leaving directory '/usr/src/linux-headers-4.13.0-1-686-pae' make[3]: Entering directory '/usr/src/modules/dahdi/drivers/dahdi/firmware' rm -f dahdi-fw-*.o rm -f dahdi-fw-*.bin rm -f dahdi-fw-*.tar.gz rm -f dahdi-fwload-*.tar.gz rm -f make_firmware_object make[3]: Leaving directory '/usr/src/modules/dahdi/drivers/dahdi/firmware' make[2]: Leaving directory '/usr/src/modules/dahdi' make[1]: Leaving directory '/usr/src/modules/dahdi' dh_autoreconf_clean dh_clean /usr/bin/make -f debian/rules kdist_clean kdist_config binary-modules make[1]: Entering directory '/usr/src/modules/dahdi' dh clean debian/rules override_dh_auto_clean make[2]: Entering directory '/usr/src/modules/dahdi' rm -f include/dahdi/version.h rm -f dahdi/include/version.h [ ! -f Makefile ] || /usr/bin/make dist-clean || true make[3]: Entering directory '/usr/src/modules/dahdi' /usr/bin/make -C /lib/modules/4.13.0-1-686-pae/build SUBDIRS=/usr/src/modules/dahdi/drivers/dahdi DAHDI_INCLUDE=/usr/src/modules/dahdi/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes clean make[4]: Entering directory '/usr/src/linux-headers-4.13.0-1-686-pae' make[4]: Leaving directory
Bug#695943: libjs-jquery-fancybox: fancybox css using relative path and it should be absolute
Package: libjs-jquery-fancybox Version: 6-1 Severity: normal Dear Maintainer, The problem is in fancybox css and how it uses Alpha for IE, a good fix for debian is to change it to use absolute paths, so instead of fancy_shadow.png use /javascript/jquery-fancybox/fancy_shadow.png. In fink I'm using this regex to patch it, perl -pi -e s,DXImageTransform\.Microsoft\.AlphaImageLoader.src=',DXImageTransform.Microsoft.AlphaImageLoader\(src='/javascript/jquery-fancybox/,g fancybox/jquery.fancybox.css -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libjs-jquery-fancybox depends on: ii libjs-jquery 1.7.2+dfsg-1 ii libjs-jquery-easing 6-1 ii libjs-jquery-mousewheel 6-1 Versions of packages libjs-jquery-fancybox recommends: ii javascript-common 7 libjs-jquery-fancybox suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#343351: perl-base: Errno.pm has hardcoded system/arch line causes lots of problems
Package: perl-base Version: 5.8.7-9 Severity: minor this is the type or Error produced everytime I upgrade perl-base Error - Perl execution failed Errno architecture (i486-linux-gnu-thread-multi-2.6.14.3) does not match executable architecture (i386-linux-thread-multi-2.4.27-ti1211) at /usr/lib/perl/5.8/Errno.pm line 11. Compilation failed in require at /usr/lib/perl/5.8/IO/Socket.pm line 17. BEGIN failed--compilation aborted at /usr/lib/perl/5.8/IO/Socket.pm line 17. Compilation failed in require at /usr/share/perl5/IMAP/Admin.pm line 8. BEGIN failed--compilation aborted at /usr/share/perl5/IMAP/Admin.pm line 8. Compilation failed in require at imap-lib.pl line 7. BEGIN failed--compilation aborted at imap-lib.pl line 7. Compilation failed in require at /usr/share/webmin/imapadmin/index.cgi line 26. in this case the system things it's i386-linux-thread-multi-2.4.27-ti1211 on some of my other 12 servers it's i486-linux-gnu-thread-multi-2.6.14-rc4 regardless it never works and I have to login to each machien and do vi /usr/lib/perl/5.8/Errno.pm remove lines 11-14 so there maybe an easier way to use postinstall to detect the running arch/system and inject these files if it's on an acceptable arch/system list? Or maybe use a regex check here? -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686-smp Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages perl-base depends on: ii libc6 2.3.5-8GNU C Library: Shared libraries an perl-base recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#333374: php5: zend.ze1_compatibility_mode segfault
Package: php5 Version: 5.0.5-2 Severity: important zend.ze1_compatibility_mode segfaults in php5, it is fixed upstream in CVS. See the php.net report. http://bugs.php.net/bug.php?id=32080edit=1 to reproduce this just install sugarsales from sugarcrm.com, there are others but this is a good one. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317688: cacti: Fix for non standard snmp port in resource/script_queries
Package: cacti Version: 0.8.6f-2 Severity: normal This is to report an upstream bug where using resource/script_queries on and snmp host using a non standard port would fail. Here is the patch. --- host_cpu.xml.orig 2005-07-10 11:37:22.0 -0600 +++ host_cpu.xml2005-07-10 11:37:55.0 -0600 @@ -1,7 +1,7 @@ interface nameGet Host MIB CPU's/name script_path|path_php_binary| -q |path_cacti|/scripts/query_host_cpu.php/script_path - arg_prepend|host_hostname| |host_snmp_community| |host_snmp_version|/arg_prepend + arg_prepend|host_hostname|:|host_snmp_port| |host_snmp_community| |host_snmp_version|/arg_prepend arg_indexindex/arg_index arg_queryquery/arg_query arg_getget/arg_get --- host_disk.xml.orig 2005-07-10 11:37:32.0 -0600 +++ host_disk.xml 2005-07-10 11:38:02.0 -0600 @@ -1,7 +1,7 @@ interface nameGet Host MIB Partitions/name script_path|path_php_binary| -q |path_cacti|/scripts/query_host_partitions.php/script_path - arg_prepend|host_hostname| |host_snmp_community| |host_snmp_version|/arg_prepend + arg_prepend|host_hostname|:|host_snmp_port| |host_snmp_community| |host_snmp_version|/arg_prepend arg_indexindex/arg_index arg_queryquery/arg_query arg_getget/arg_get -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages cacti depends on: ii apache2-mpm-prefork [apache2 2.0.54-4traditional model for Apache2 ii debconf 1.4.51 Debian configuration management sy ii libapache2-mod-php4 4:4.3.10-15 server-side, HTML-embedded scripti ii libphp-adodb 4.52-1 The 'adodb' database abstraction l ii logrotate3.7-5 Log rotation utility ii mysql-client-4.1 [mysql-clie 4.1.11a-4 mysql database client binaries ii php4 4:4.3.10-15 server-side, HTML-embedded scripti ii php4-cli 4:4.3.10-15 command-line interpreter for the p ii php4-mysql 4:4.3.10-15 MySQL module for php4 ii php4-snmp4:4.3.10-15 SNMP module for php4 ii rrdtool 1.0.49-1Time-series data storage and displ ii snmp 5.1.2-6.1 NET SNMP (Simple Network Managemen ii ucf 1.18Update Configuration File: preserv Versions of packages cacti recommends: ii iputils-ping3:20020927-2 Tools to test the reachability of ii mysql-server-4.1 [mysql-ser 4.1.11a-4mysql database server binaries -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
