Bug#1023344: eggdrop: Please upgrade debian package to Eggdrop Release v1.9.3 *STABLE*

Package: eggdrop Version: 1.8.4+repack1-0.1 Severity: wishlist Dear Maintainers, Eggdrop v1.9.3 *STABLE* has been released on Aug 11, 2022 It would be awesome to have that version in Debian as well. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500,

Bug#1023342: eggdrop dns module does not work on ipv6-only hosts

Package: eggdrop Version: 1.8.4+repack1-0.1 Severity: important Tags: ipv6 Dear maintainer, using the eggdrop dns module on an ipv6-only host fails with an "no valid dns servers found" error. This happens, if * /etc/resolv.conf contains only an IPv6 DNS Server * and/or the system is ipv6-only *

Bug#1019267: lprint: wrong path in lprint.service definition

Package: lprint Version: 1.1.0-1 Severity: normal Dear Maintainers, the systemd service file for lprint.service refers to /usr/local/bin/lprint instead of /usr/bin/lprint which leads to a non working service state. Error Message: Failed to locate executable /usr/local/bin/lprint: No such file

Bug#1006622: network-manager: Upgrade from 1.34.0-2 to any higher version breaks IPv6 config on mobile broadband

Package: network-manager Version: 1.36.0-2 Severity: important Tags: ipv6 Dear Maintainer, after upgrading network-manager from version 1.34.0-2 to 1.35.91-1 or higher, NetworkManager fails to set the IPv6 addresses, received via mobile boradband connection. * Downgrading to 1.34.0-2

Bug#1004447: modemmanager: Sierra Wireless EM7455 stops working after upgrade to 1.18.4-1 (stays in FCC lock)

Package: modemmanager Version: 1.18.4-1 Severity: normal Hi, after upgrading to the latest unstable version of modemmanager to 1.18.4-1, the Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A in my Lenovo Thinkpad T470 stopped working. I have a rough idea, what's going on, but not enough

Bug#947776: python3-nautilus 1.2.3-3 solved the problem

Hi, updating python3-nautilus to version 1.2.3-3 from unstable solved the problem for me. Cheers, Björn

Bug#947776: Same problem also with nautilus-nextcloud 2.6.4-1

Hi, I have the same problem with nautilus-nextcloud 2.6.4-1. When I start nautilus from the command line I get this warning: ** (org.gnome.Nautilus:36227): WARNING **: 21:34:08.527: /usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libnautilus- python.so: undefined symbol:

Bug#951207: python3-xapian-haystack: Broken compatibility with pre-2.0 haystack

Package: python3-xapian-haystack Version: 2.1.0-3 Severity: important Dear Maintainer, commit d3f1e011da3d9bebd88c78fe7a87cd6171ae650c of xapian-haystack removed the "commit" keyword which e.g. is used by python3-django-hyperkitty / python3-django-haystack In commit

Bug#942540: removing some files should help

see https://lists.mailman3.org/archives/list/mailman-us...@mailman3.org/thread/PAMC4L5LALDRWXTUNJMQCL4AQRJEMEVF/ But afterwards, it crashes with another issue: Traceback (most recent call last): File "/usr/bin/django-admin", line 21, in management.execute_from_command_line() File

Bug#926660: Patch to make webfs stoppable again

attached patch for the init script fixes this. As the package maintainer does not pop up here, can some Debain Deveoper please make a NMU based on this patch? --- debian/webfs.init.old 2019-11-04 22:48:01.637076220 +0100 +++ debian/webfs.init 2019-11-04 22:49:19.481197962 +0100 @@ -73,13 +73,13 @@

Bug#932935: System refuses to boot, logsave not found - requires manual a fsck

Package: linux-image-4.19.0-5-amd64 Version: 4.19.37-6 I run Debian sid, with the latest Kernel. If I try to boot the system I end up in BusyBox with following message: " Resuming from hibernation /init: line 398: logsave: not found The root filesystem /dev/mapper/potato-vg-root requires a

Bug#930648: exim4-daemon-heavy: Weird leakage of unrelated data like /etc/aliases into /var/spool/exim4/input/*-H

Hi, short update: * Bjoern Buerger (b.buer...@pengutronix.de) [190625 12:08]: > * Andreas Metzler (ametz...@bebt.de) [190621 09:58]: > > On 2019-06-19 Bjoern Buerger wrote: > > > * Andreas Metzler (ametz...@bebt.de) [190618 19:15]: > > [...] > > > > Cou

Bug#883393: jool Debian packaging

Hi @all Am Sat, 13 Jul 2019 schrieb Vincent Bernat: > ❦ 13 juillet 2019 12:29 -05, Alberto Leiva : > > I sent him another email on 2018-05-28, and then another one two days > > ago. Both of them have gone unanswered as of now. > > OK, if he disagrees, he still have a bit of time to make us

Bug#930648: exim4-daemon-heavy: Weird leakage of unrelated data like /etc/aliases into /var/spool/exim4/input/*-H

* Andreas Metzler (ametz...@bebt.de) [190621 09:58]: > On 2019-06-19 Bjoern Buerger wrote: > > * Andreas Metzler (ametz...@bebt.de) [190618 19:15]: > [...] > > > Could you try > > > a) disabling BDAT (set chunking_advertise_hosts = ) > > > b) try a bac

Bug#930648: exim4-daemon-heavy: Weird leakage of unrelated data like /etc/aliases into /var/spool/exim4/input/*-H

* Andreas Metzler (ametz...@bebt.de) [190618 19:15]: > On 2019-06-17 Bjoern Buerger wrote: > > Am Mon, 17 Jun 2019 schrieb Andreas Metzler: > [...] > > > what version did you upgrade from, the previous bpo-version (4.92-2) or > > > the original stretch release?

Bug#930648: exim4-daemon-heavy: Weird leakage of unrelated data like /etc/aliases into /var/spool/exim4/input/*-H

Am Mon, 17 Jun 2019 schrieb Andreas Metzler: > On 2019-06-17 Bjoern Buerger wrote: > > Package: exim4-daemon-heavy > > Version: 4.92-7 > > Severity: important > > [...] > > We did update to 4.92-7 from bpo before we saw the problem for > > the first

Bug#930648: exim4-daemon-heavy: Weird leakage of unrelated data like /etc/aliases into /var/spool/exim4/input/*-H

Package: exim4-daemon-heavy Version: 4.92-7 Severity: important Dear Maintainer, The following is currently just an observation, as we haven't been able to reproduce the problem yet. It might be caused by faulty memory on the affected server but it could also be related to CVE-2019-10149 fixes,

Bug#920304: Acknowledgement (mailman3-web: mailman3web / django does not like python3-pymysql)

d both pymysql and mysqlclient. The former is used by Mailman core and the latter by Django. These can be installed with pip via pip3 install pymysql pip3 install mysqlclient or apt via apt install python3-pymysql python3-mysqldb" Kind regards Bjoern

Bug#920304: mailman3-web: mailman3web / django does not like python3-pymysql

Package: mailman3-web Version: 0+20180916-2~bpo9+1 Severity: grave Justification: renders package unusable Dear Maintainer, upgrading mailman3-web lead to File "/usr/lib/python3/dist-packages/django/db/backends/mysql/base.py", line 30, in 'Did you install mysqlclient or

Bug#911661: xdebug should support all available PHP versions

Package: php-xdebug Version: 2.7.0 The current php-xdebug package in sid only contains xdebug for PHP 7.3 while Debian sid still comes with PHP 7.1, PHP 7.2 and PHP 7.3 I think the package should contain xdebug for all available PHP versions or alternatively there should be multiple php-xdebug

Bug#906012: libxcursor: CVE-2015-9262

On 31/08/18 23:46, Julien Cristau wrote: Process questions are very much off-topic for this bug report, but... On 08/30/2018 09:43 AM, Bjoern wrote: As I am clearly unfamiliar with your processes, I really would appreciate the clarification to better my understanding and perhaps quell my

Bug#906012: libxcursor: CVE-2015-9262

On 27/08/18 18:22, Moritz Muehlenhoff wrote: On Mon, Aug 27, 2018 at 05:40:01PM +0800, Bjoern wrote: -- Begin Quote: -- From: Chris Lamb To: 906...@bugs.debian.org Cc: t...@security.debian.org Subject: Re: libxcursor: CVE-2015-9262 Date: Mon, 13 Aug 2018 08:18:27 +0100

Bug#906012: libxcursor: CVE-2015-9262

On 27/08/18 18:22, Moritz Muehlenhoff wrote: On Mon, Aug 27, 2018 at 05:40:01PM +0800, Bjoern wrote: -- Begin Quote: -- From: Chris Lamb To: 906...@bugs.debian.org Cc: t...@security.debian.org Subject: Re: libxcursor: CVE-2015-9262 Date: Mon, 13 Aug 2018 08:18:27 +0100

Bug#906012: libxcursor: CVE-2015-9262

have been patched. May I seek your enlightenment on this matter? My kindest regards, Bjoern.

Bug#894256: [Pkg-mailman-hackers] Bug#894256: mailman3 wants to take away mailman.cfg from mailman3-core

ible > that all people having installed -core will have to handle manually the > transition and its side effects. > Any news on this issue? Regards Bjoern

Bug#894256: mailman3 wants to take away mailman.cfg from mailman3-core

Package: mailman3 Version: 3.1.1-8~bpo9+1 Severity: normal Dear Maintainer, 2 root@srv20 /etc/mailman3 # apt-get remove mailman3-core :( Reading package lists... Done Building dependency tree Reading state

Bug#893780: [Pkg-mailman-hackers] Bug#893780: mailman3-suite: depends on incompatible version of python-django

something wrong with python-django-allauth from backports so it does not depend on python-django from backports? Regards Bjoern

Bug#893780: mailman3-suite: depends on incompatible version of python-django

Package: mailman3-suite Version: 0+20170523-9~bpo9+1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installing mailman3-suite * What exactly did you do (or not do) that was effective (or

Bug#884311: Bug#884358: Bug#884311: Gajim: problem with latest python-openssl

n favor of porting it to unstable. > > thanks, > > dimitris. > > > On 12/15/2017 03:01 PM, W. Martin Borgert wrote: > > Dear Bjoern, dear Dimitris, > > > > thank you for your bug reports! I ask you for a favour: > > > > Could you please try G

Bug#884358: gajim: broken dependencies, gajim no longer starts

Package: gajim Version: 0.16.8-5 Severity: grave Justification: renders package unusable Dear Maintainer, I'm running Debian unstable with the latest gajim version (0.16.8-5). If I try to start gajim I get this error message: Traceback (most recent call last): File "gajim.py", line 307, in

Bug#883393: ITP: jool -- Open Source SIIT and NAT64 Translator for Linux

Package: wnpp Severity: wishlist Owner: Bjoern Buerger <b...@penguin.de> * Package name: jool Version : 3.5.5 Upstream Author : Jool Dev Team <j...@nic.mx> * URL : http://jool.mx/ * License : GPLv3+, GPL Programming Lang: C Description :

Bug#850155: keystone: postinst throws error

Package: keystone Version: 2:9.0.0-2~bpo8+1 Severity: normal Dear Maintainer, during installation of keystone on a plain host the following error occurs: Setting up keystone (2:9.0.0-2~bpo8+1) ... PKG-Openstack now calling: dbc_go keystone configure Determining localhost credentials from

Bug#847557: /usr/sbin/exportfs: exportfs cannot handle IPv6 addresses

Package: nfs-kernel-server Version: 1:1.2.8-9.2 Severity: important File: /usr/sbin/exportfs Tags: ipv6 Dear Maintainer, when trying to export/unexport a path i cannot give IPv6 addresses to exportfs. # showmount -e Export list for testhost: /path/sub fe80::%eth0/10 # exportfs -u

Bug#846077: sudo: compile sudo with zlib support

Package: sudo Version: 1.8.10p3-1+deb8u3 Severity: wishlist Dear Maintainer, I've tried using 'Defaults compress_io' but it seems sudo ain't compiled with zlib support? Would be great to enable that build-dep! Cheers B -- System Information: Debian Release: 8.6 APT prefers stable-updates

Bug#841163: [debian-mysql] Upload of MySQL 5.7.16 security update to unstable

Thank you!! On Wed, Nov 9, 2016 at 7:55 AM Lars Tangvald wrote: > > > On 11/08/2016 10:53 PM, Dominic Hargreaves wrote: > > > > Hi Lars, > > > > Now uploaded. > > > > Cheers, > > Dominic. > Great, thanks! > > -- > Lars > >

Bug#841345: [debian-mysql] Bug#841345: mysql-server-5.7: Unable to switch from mariadb to mysql, "downgrade" is aborted

Hi, thanks for your bug report. when it comes to switching between mysql and mariadb versions this might get tricky as we have to define which versions can be switched and which not. To be honest I have no clue which mariadb version could be replaced by mysql and vica versa. Maybe some team

Bug#840855: [debian-mysql] Bug#840855: Bug#840855: mysql-server: MySQL 5.7?

Ty very much! Lars Tangvald schrieb am Di., 18. Okt. 2016, 18:54: > MySQL 5.7 is available in unstable now :) > > -- > Lars > > ___ > pkg-mysql-maint mailing list > pkg-mysql-ma...@lists.alioth.debian.org >

Bug#837883: [debian-mysql] Bug#837883: Bug#837883: mysql-server-5.7: Please upgrade to 5.7.15+ to fix recently discovered security issues

No, I did not. afaik I'd need KVM to run those tests? basically I'm not familiar with dep8 :/ On Thu, Sep 15, 2016 at 1:01 PM Lars Tangvald <lars.tangv...@oracle.com> wrote: > Thanks, Bjoern. Did you run the dep8 test suite as well (I just started a > full test run now, so no big dea

Bug#837883: [debian-mysql] Bug#837883: mysql-server-5.7: Please upgrade to 5.7.15+ to fix recently discovered security issues

Hi, I've updated the git repo after I did a successful build on jessie. Someone with upload rights just needs to create a ~experimental tag and upload it. @pkg-mysql: what's the plan for uploading mysql-5.7 to unstable? Cheers B On Thu, Sep 15, 2016 at 9:54 AM Eric Valette

Bug#823865: phpsysinfo: missing copyright

Hi, I did not recieve any reply yet. Please reply until 2016-06-25. Otherwise I have to choose a copyright on my own. See also. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823865 Cheers B On Thu, May 26, 2016 at 1:59 PM Bjoern Boschman <bjo...@boschman.de> wrote: > Hi, > >

Bug#823865: phpsysinfo: missing copyright

Hi, as the current maintainer of phpsysinfo I'd like to ask you if GPL-2 is ok for you for all files within debian/ folder. Cheers B

Bug#821628: phpsysinfo: PHP 7.0 Transition

Hi Ondrej, thanks for your work! is somethings like this valid? Depends: php | php5, php-xml | php5-xsl Cheers B

Bug#801247: Info received (pinentry-gnome3: No PIN dialog)

* Debian Bug Tracking System (ow...@bugs.debian.org) [160205 10:39]: > If you wish to submit further information on this problem, please > send it to 801...@bugs.debian.org. I can confirm, that purging pinentry-gnome3:amd64 0.9.7-1 does in fact work around this bug. Installing it, immediately

Bug#801247: pinentry-gnome3: No PIN dialog

I got hit by the very same bug, while using the yubikey with ssh: Package: pinentry-gnome3 Version: 0.9.7-1 Debian Release: stretch/sid Architecture: amd64 (x86_64) Probably interesting: - Neither pinentry for the yubi-key, nor ask-pass for a classic ssh key with passphrase show up, so

Bug#810808: initramfs-tools: lvm on NVMe boot drives brakes mkinitramfs

Package: initramfs-tools Version: 0.120 Severity: normal Tags: d-i patch Dear Maintainer, while trying installing debian 8.2 onto a PCIe SSD (NVMe device) the creation of the initrd is failing. root@holodeck10:~# apt-get install -f. Reading package

Bug#809228: boost: new upstream version (1.60)

Package: boost-defaults Hi, please upload an updated version as >= 1.59 is mandatory for build mysql-5.7 Thank you! -- Mit freundlich Grüßen / Kind regards Björn Boschman

Bug#805828: [debian-mysql] Bug#805828: mysql-server-5.6: upgrade didn't work, package unusable, mysql does not start

Hi JP, thank you for your bugreport. Have you tried setting your datadir to the absolute folder (without any symlinks?) The log msg you reported states that your mysql database is missing. Can you provide older log messages? Cheers B 2015-11-22 22:02 GMT+01:00 jpp : >

Bug#802564: [debian-mysql] Bug#802564: mysql-5.5: Multiple security fixes from the October 2015 CPU

Hi, why are the changes not pushed on git? Cheers B On Fri, Oct 23, 2015 at 1:45 PM Salvatore Bonaccorso wrote: > > Hi MySQL team, > > FTR, I have now an update ready which I would push to security-master > soon for wheezy- and jessie-security. > > Regards, > Salvatore > >

Bug#802563: [debian-mysql] Bug#802563: mysql-5.6: Multiple security fixes from the October 2015 CPU

Hi, someone just has to tag and upload mysql-5.6 All work has already been done on git. Cheers B On Wed, Oct 21, 2015 at 7:30 AM Salvatore Bonaccorso wrote: > Source: mysql-5.6 > Version: 5.6.25-4 > Severity: grave > Tags: security upstream fixed-upstream > > Hi > > As

Bug#800455: icecc: icecream does not support IPv6

Package: icecc Version: 1.0.1-2 Severity: normal Dear Maintainer, as we are moving from dualstack to ipv6-only systems, missing ipv6 support in icecc / icecream is becoming a real showstopper for the sysadmins. Please consider adding ipv6 support to icecc. -- System Information: Debian

Bug#662963: [debian-mysql] Bug#662963: mysql-proxy: new upstream release 0.8.5

Hi, I've seen nobse has updated the sources in SVN http://anonscm.debian.org/viewvc/pkg-mysql/mysql-proxy/trunk/debian/changelog?view=markup There's only someone missing to upload it to unstable? Cheers B On Sun, Aug 16, 2015 at 2:54 PM Petr Vorel petr.vo...@gmail.com wrote: Package:

Bug#795258: heirloom-mailx: fails to send mails when called from anacron

is placed in cron.daily, cron.weekly or cron.monthly. Best regards Bjoern -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG

Bug#783688: serverstats: please make the build reproducible

Hi, an updated pkg wouldd be available here https://mentors.debian.net/package/serverstats I have no power to upload to debian :( Cheers B On Wed, Apr 29, 2015 at 10:03 AM Chris Lamb la...@debian.org wrote: Source: serverstats Version: 0.8.2-10 Severity: wishlist Tags: patch User:

Bug#508161: Status of this Bug is unclear

Dear Maintainer, Could you please clarify the status of this Bug? As of now, my observation w/ Debian Wheezy is: greylistd: Installed: 0.8.8 Candidate: 0.8.8 * IPv6 Connections seem to be recognized and greylisting _seems_ to be applied accordingly. After a while, consecutive

Bug#508161: Status of this Bug is unclear

Am Thu, 16 Apr 2015 schrieb Bjoern Buerger: Can I expect greylistd to behave sanely if confronted with lots of IPv6 Traffic (currently ~40-50 % of our incoming mail), or is there some hidden problem one should know about? Ah, short answer: No, it is still not IPv6 capable. * The assigned

Bug#782704: amispammer is configured to use some dead blacklists

Package: amispammer Version: 3.3-1 Severity: normal Dear Maintainer, The List of RBLs in amispammer is outdated, which leads to false positives. Example: amispammer -i some ipv6 address [...] Checking IP: some ipv6 address * bl.spamcop.net Blacklisted! REASON: v=spf1 -all *

Bug#778678: mysql-server: still some bashism

Package: mysql-server Version: 5.5.42-1 Severity: important Hi guys, unfortunatelly i found some bashism still used. additions/echo_stderr:#!/bin/bash additions/mysql-systemd-start:#!/bin/bash additions/debian-start:#!/bin/bash additions/debian-start.inc.sh:#!/bin/bash

Bug#778678: [debian-mysql] Bug#778678: mysql-server: still some bashism

+0100, Bjoern Boschman bjo...@boschman.de wrote: Package: mysql-server Version: 5.5.42-1 Severity: important Hi guys, unfortunatelly i found some bashism still used. additions/echo_stderr:#!/bin/bash additions/mysql-systemd-start:#!/bin/bash additions/debian-start:#!/bin/bash additions

Bug#773701: Acknowledgement (libreoffice: will not open files on a gvfs share)

/glib2.0/+bug/1214352 which is in a header file, thus would require a full rebuild of all rdepends of glib and so would be very hard to fix properly on a stable release. Best, Bjoern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble

Bug#601011: any update?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I could supply an lxc container if requested Am 07.08.2014 12:26, schrieb Cyril Brulebois: -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iEYEARECAAYFAlPnXxAACgkQABMWRpwdNungEACgwCbt2IyhO/L08Sa7PyHchhqS

Bug#601011: any update?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I could supply an lxc container if requested Am 07.08.2014 12:26, schrieb Cyril Brulebois: While I haven't tried to reproduce this bug, the patch looks like something that could indeed be merged. -BEGIN PGP SIGNATURE- Version: GnuPG

Bug#601011: any update?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, this bug is still valid with debbotstrap 1.0.48+deb7u1 is there any chance that this patch will be introduced or denied? Cheers B -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird -

Bug#711147: lvm2 still doesn't active volume group at boot time

Dear Maintainers of lvm2 and initramfs-tools. For the second time since mid-2013, I got hit by the lvm2 still doesn't active volume group at boot time bug: lvm2 version is 2.02.104-2 in both cases. Please at least try to merge some of the outstanding bug-reports: 742962, 711147, 715184 are

Bug#682232: [debian-mysql] Bug#682232: mysql-server-5.5: Fails to upgrade squeeze - wheezy, does not start

Hi, have you configured --log-error within my.cnf? See [0] What does the error log says? This is most likely due to custom configuriation below /etc/mysql/conf.d/ [0] http://dev.mysql.com/doc/refman/5.5/en/error-log.html Cheers B -- To UNSUBSCRIBE, email to

Bug#731076: [debian-mysql] Bug#731076: mysql-server: query cache not used when InnoDB tables and name with special chars

Hi, I've addressed this for the next upcoming release (somewhere in the future :) http://anonscm.debian.org/gitweb/?p=pkg-mysql/pkg-mysql.git;a=commitdiff;h=73fee5070078f92079141cddeca9723a4943689a Cheers B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject

Bug#580188: Contribution of patch

Hi, i like to contribute a patch for both init-scripts and common-functions. The patch just replace some lsb functions with the start-stop-daemon and uses ps aux to get pid of the daemon. Hope that help and I don't miss anything :) Greetings, Björn init.patch Description: Binary data

Bug#721487: [debian-mysql] Bug#721487: mysql-server: standard mysql server installation does not listen on tcp6 protocol

Hi Adrian, letting mysql-server listen on localhost only is the default debian configuration. This was done as a security enhancement. Unfortunatelly you can only supply a single IP address to bind-address So there are only: bind-address = 127.0.0.1 # IPv4 localhost only bind-address = ::1

Bug#720537: ITP: r-bioc-iranges -- GNU R low-level containers for storing sets of integer ranges

Puuuh, darios Geschenke sind auch da. Ha, ich mag die Sprüche in den Karten :) 2013/8/23 Andreas Tille ti...@debian.org Package: wnpp Severity: wishlist Owner: Andreas Tille ti...@debian.org * Package name: r-bioc-iranges Version : 1.18.3 Upstream Author : H. Pages * URL

Bug#703452: [pkg-php-pear] php5-redis

Hi, Am 18.08.2013 23:15, schrieb Jonas Genannt: is there any progress on this task? - If you are busy, an other dd member of pkg-php-pear team could check and upload this package. towards whom is this posted? :-) B -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with

Bug#703452: [pkg-php-pear] php5-redis

Hi, Am 27.06.2013 12:04, schrieb Jonas Genannt: I have done initial packaging of redis. Please have a look at: http://anonscm.debian.org/gitweb/?p=pkg-php/php-redis.git;a=summary Clean builds with PHP 5.5 from sid and seems to be lintian clean. also I haven't build it yet due to missing

Bug#703452: php5-redis

Hi folks, I'd like to ask the pkg-php-pear group if they might assist by getting php5-redis into the debian repo. As far as I can read the ITP most work is already done by Cyril There's still a license issue which must be handled, but imho it should not be a big deal as it is licensed under

Bug#622119: [debian-mysql] Bug#622119: Bug#622119: mysql-server: logrotatescript fails, nothing to do

Hi, thanks for the pproposed fix, but I'd say that running some logrotate scripts with enhanced privilege (root) might be against debian policy? Cheers B Am 22.05.2013 20:39, schrieb Fabián Bonetti: Solved: nano /etc/logrotate.d/mysql-server /var/log/mysql.log

Bug#622119: [debian-mysql] Bug#622119: mysql-server: logrotatescript fails, nothing to do

Hi, the problem comes from mysqladmin flush-logs that logs have the wrong owner this is somehow done wrong by the safe_mysqld script this script reads my.cnf, identifies error_log and creates it as user root solution: chown them as user mysql Cheers B Am 21.05.2013 18:01, schrieb Fabián

Bug#708380: [debian-mysql] Bug#708380: mysql-server-5.5: Upgrade from squeeze to wheezy fails due deprecated replication config

hi, those config options are user-supplied and in the meatime deprecated. as far as I know there is no my.cnf config checker / tester which could point the user that he has to manual do config update but in terms of debian packaging it is not real our job to care about user defined config

Bug#565308: Will we see MariaDB in Jessie?

hi, Just my two 2 cent: I would like to have an virtual package Database, to resolve some deps. So there hasn't be a question of what database someone have to use. Okay, the mainproblem here is not all packages have interface for every database, but it could solve these questions Greetings,

Bug#706160: 706160submit...@bugs.debian.org

hi, I've read this and like to give another perspective. Let me first introduce myself to let you know, what my point of view is. I use Debian since Potato was released. My first package was done with Etch. The packages I've created were packages just for my own. It has been 5 since then. So,

Bug#599267: More Infos

hi, maybe I could help, if you provide more infos. What I think: Renaming is a move (create a new hardlink and delete the old one; on condition that is the same volume), that why you need write access to this dir. Further more the new hardlink will be created with the primary group of the user.

Bug#693981: Solved to me

hi, I've solved it by myself. I took the source of the package, also the build-deps. Patched the source with this: https://attachments.samba.org/attachment.cgi?id=6869 and built the package. Works like a charme :) Greatings Björn -- To UNSUBSCRIBE, email to

Bug#693981: Confirmed

hi, I can confirm this bug and reproduce it. In which version it is fixed? Upstream fixed it as a backport to 3.5.x. Thanks for helping. Greetings Björn -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#702630: [debian-mysql] Bug#702630: mysql 5.6?

Hi Joy, there's already some work within pkg-mysql SVN repo which is after all not that much usable :-) When you *really* need it you can test this http://boschman.de/~jesusch/debian/src/mysql/pkg-mysql/mysql-5.6/build-area/mysql-5.6.10-deb/ but there are still issues with upgrading and

Bug#698684: libcityhash0: cityhash compiled without -fPIC

Package: libcityhash0 Version: 1.1.0-1 Severity: normal Tags: upstream Dear Maintainer, The package is compiled without -fPIC, preventing relocation. -- System Information: Debian Release: wheezy/sid APT prefers precise-updates APT policy: (500, 'precise-updates'), (500,

Bug#693874: convmv can delete data on case-insensitive filesystems

Package: convmv Version: 1.12 Owner: bubu...@debian.org there is a posible data loss bug in the convmv versions = 1.14 which are in Debian distris. from the changelog: - fix a bug where on case-insensitive filesystems --upper and --lower did not work because we thought the new file would

Bug#692868: boost::unordered_multimap::erase(iterator, iterator) broken in boost1.49

/+attachment/3271642/+files/lp1017125.cxx Upstream reports this to be fixed with: https://svn.boost.org/trac/boost/ticket/7471 in boost 1.52 -- so likely boost1.50 and boost1.51 are affected as well. Best, Bjoern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

Bug#692050: munin-cgi-graph dies due to =begin: command not found

Package: munin Version: 2.0.6-1 Severity: important Dear Maintainer, munin-cgi-graph dies: root@ensis:/# su - munin --shell=/bin/bash /usr/lib/munin/cgi/munin-cgi-graph /usr/lib/munin/cgi/munin-cgi-graph: line 4: =begin: command not found /usr/lib/munin/cgi/munin-cgi-graph: line 6: syntax error

Bug#685382: [debian-mysql] Bug#685382: mysql-server: bind :: results in listening to IPv6 only

Hi, a socket listening on :::3306 listens on v4 *and v6 so it's already working as it should :-) Cheers Bjoern -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#664639: mysql and logging

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Nicholas, the basic problem can be reproduced as follows: configure error logging: [mysqld] log-error = /var/log/mysql/error.log and restart mysql-server chown root /var/log/mysql/error.log mysqladmin --defaults-file=/etc/mysql/debian.cnf

Bug#664846: skip name resolving

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Nicholas, my mysql.user table still includes 'user'@'%' records. - From 8.9.8 I can read the following: To disable DNS host name lookups, start the server with the - --skip-name-resolve option. This in my ears sound like: disable any

Bug#664639: Re: [debian-mysql] Bug#664639: mysqladmin flush-logs fails: more debugging output required?

an idea how to fix this, but I'll stay on track Cheers Bjoern -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/gQXYACgkQABMWRpwdNungwACgvgafRpyB1Npa2jK6OL2vV+72 a5YAoL2sZzYZUSJwGHHGVunpxheahVUG =wKnm

Bug#664639: [debian-mysql] Bug#664639: Re: Bug#664639: mysqladmin flush-logs fails: more debugging output required?

at all. I have done a patch (r2162 within subversion) which changes this behaviour (currently mysql-server-5.5 only) Cheers Bjoern -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk

Bug#664639: mysqladmin flush-logs fails: more debugging output required?

could also start mysqladmin more verbose or via strace if this would help? Would be great to hear from anybody! Cheers Bjoern -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk

Bug#678010: rdiff-backup does not start

Package: rdiff-backup Version: 1.2.8-6 Severity: important rdiff-backup does not start on Debian Squeeze: $ rdiff-backup -V Traceback (most recent call last): File /usr/bin/rdiff-backup, line 20, in module import rdiff_backup.Main ImportError: No module named rdiff_backup.Main All

Bug#677225: cron-apt crashes with buffer overflow (caused by liblockfile)

Package: liblockfile cron-apt crasheѕ with a buffer overflow when PID counter is 100 See https://bugs.launchpad.net/ubuntu/+source/liblockfile/+bug/1011477 for details and a patch attached. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#674142: make it possible to disable ssl compression in apache2 mod_ssl

Package: apache2 Version: 2.2.16 Owner: debian-apa...@lists.debian.org Some browsers like Chrome/Chromium but also cmdline clients using openssl like wget support ssl compression. This is a big problem for ssl enabled servers when they offer big files. Pulling for example a (already compressed)

Bug#664846: mysql-server-5.1: MySQL Server does DNS-PTR lookups even when skip-name-resolve is active

Package: mysql-server-5.1 Version: 5.1.61-0+squeeze1 Severity: important Hi folks, I'm running my MySQL server with the --skip-name-resolve. I verified that this option is enabled via: mysql show variables LIKE 'skip_name_resolve'\G *** 1. row ***

Bug#664632: libsoap-lite-perl: sysread() not working while using this lib with mod_perl

Package: libsoap-lite-perl Version: 0.712-2 Severity: normal Hi folks, SOAP::Transport::HTTP fails when it is called from mod_perl A patch is attached -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux

Bug#664639: mysql-client-5.1: mysqladmin flush-logs fails

Package: mysql-client-5.1 Version: 5.1.61-0+squeeze1 Severity: normal Hi folks, I have a fresh installed 5.1.61 mysql-server logrotate.d runs a daily mysqladmin flush-logs this fails with the following error: /usr/bin/mysqladmin: refresh failed; error: 'Unknown error' Somehow this is not

Bug#659687: [debian-mysql] Bug#659687: Multiple security issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Moritz, for mysql-5.5 in experimental there's currently a discussion ongoing if mysql shall be replaced by MariaDB http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/2012-February/003866.html I'm not sure about security policy in

Bug#657445: openssh-server: Forced Command handling leaks private information to ssh clients

Package: openssh-server Version: 1:5.5p1-6+squeeze1 Severity: normal The handling of multiple forced commands in ~/.ssh/authorized key leaks information about other configured forced commands to the user. This affects tools lile gitolite, which makes heavy use of forced commands (For gitolite,

Bug#657448: gitolite: openssh-server bug leaks configured gitolite usernames to client

Package: gitolite Severity: normal Dear Maintainer, Gitolite users should be aware, that some or all configured usernames show up in the debug output of any ssh client, depending on the position of the accessing user's forced command in the gitolite authorized_keys configuration. e.G. if the

Bug#649491: Bug#651032: /usr/sbin/rpc.idmapd: rpc.idmapd referring to none existing library

Am Mo, 05 Dez 2011 schrieb Anibal Monsalve Salazar: I added the upstream patches to add the --with-pluginpath configuration option. Please test libnfsidmap 0.24-4 and post your results. Yes, 0.24-4 solves the issue for my system. # systemctl status nfs-common.service nfs-common.service - LSB:

  1   2   3   >