Bug#611615: puppetmaster logrotate script conflicts with puppet's one

Package: puppetmaster Version: 2.6.2-4 Severity: normal puppetmaster installs a logrotate file that defines a rule for /var/log/puppet/masterhttp.log however, the puppet package installs a file, too, in which rules are set for /varl/log/puppet/*.log. This creates a conflict and logrotate exits

Bug#476544: Bug#475302: vz starts to early in boot process

xendomains) can use DRBD devices. -- Gabriel Filion -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#632797: Suppress information message about I/O scheduling class with -q

Hello, Just chipping in here for showing support for this issue: This has been discussed in bug #598957 which is now closed due to a package being pushed to testing/sid to fix this. It would be really nice to see this fix get in squeeze. -- Gabriel Filion -- To UNSUBSCRIBE, email

Bug#659331: nagios3: service restart should fail when there is a configuration error

Package: nagios3 Version: 3.2.1-2 Severity: normal The current behaviour of the init script is to quietly succeed a service restart when there is a configuration error, but without restarting the service. While this prevents the service from randomly stopping, it doesn't tell users that there is

Bug#580294: [Pkg-nagios-devel] Bug#580294: nagios3: fails to install when partial (bad) configuration exists

a configuration error preventing installation completion. -- Gabriel Filion -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#639941: Xen line 118: sigerr: command not found error for unassigned network interfaces

already has an IP assigned to it via /etc/network/interfaces but regardless of the error, the networking setup actually works. it's just annoying to have to wait so long for the command to complete during the boot process. -- Gabriel Filion -- To UNSUBSCRIBE, email to debian-bugs-dist-requ

Bug#614320: [debian-mysql] Bug#614320: Error when installing

MySQL database server binaries and system database setup ii mysql-server-core-5.1 5.1.49-3 MySQL database server binaries -- Gabriel Filion -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas

Bug#614320: Info received ([debian-mysql] Bug#614320: Error when installing)

I got the install to complete! I shutdown the domU, started it again, and SSH'ed in. Now 'apt-get -f install' did complete successfully (it didn't before rebooting). Now that's a weird problem resolution.. -- Gabriel Filion -- To UNSUBSCRIBE, email to debian-bugs-dist-requ

Bug#651704: puppet: hasstatus breaks dependency of named service resource

Package: puppet Version: 2.6.2-5+squeeze3 Severity: normal Using hasstatus with a service resource that redefines the name parameter makes puppet agent refuse to run with an error similar to: Could not find init script for 'nagios3' This issue has been taken care of by upstream and was

Bug#701744: [xen] Update to hypervisor 4.0.1-5.6 or linux-image-2.6.32-5-xen-amd64 2.6.32-48 causes networking (VIF) failures

could see this in the logs: [2601471.852025] TCP: Peer 74.94.211.209:31059/80 unexpectedly shrunk window 4233113998:4233124218 (repaired) [2601479.916025] TCP: Peer 74.94.211.209:31059/80 unexpectedly shrunk window 4233113998:4233124218 (repaired) -- Gabriel Filion signature.asc Description

Bug#659331: nagios3: service restart should fail when there is a configuration error

I just found out about bug report #680615 This looks like the root cause of this issue. I'll answer to that other issue, so you can close this one here. -- Gabriel Filion -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#680615: nagios3: init script confusion between 'check' and 'status'

:~# sed -i '209s/status/check/' /etc/init.d/nagios3 root@nagios0:~# /etc/init.d/nagios3 status checking /usr/sbin/nagios3...done (running). root@nagios0:~# /etc/init.d/nagios3 check [... nagios -v output] -- Gabriel Filion -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

Bug#643691: not reproducible on latest sid version

eat the cpu. -- Gabriel Filion -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#665487: dovecot-managesieved: Error upgrading dovecot with managesieved

to the current dovecot-managesieved.postrm file, so I marked it as unreproducible. -- Gabriel Filion -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#665487: dovecot-managesieved: Error upgrading dovecot with managesieved

On 2012-09-30 00:46, Jaldhar H. Vyas wrote: On Sun, 30 Sep 2012, Gabriel Filion wrote: This bug concerns a somewhat old version (current version in both squeeze-backports and wheezy is 1:2.1.7-2). Also, the package dovecot-managesieved doesn't exist in the squeeze archive. So I can't

Bug#695617: iotop crashes when locale not found on system

Package: iotop Version: 0.4-2+squeeze1 Severity: normal When invoked on a server that does not share my locale settings, iotop simply refuses to launch until I force the locale to something that exists on the system. Traceback (most recent call last): File /usr/bin/iotop, line 16, in module

Bug#728840: munin-plugins-extra: ipmi_sensor_ doesn't properly import os

Package: munin-plugins-extra Version: 2.0.6-4+deb7u1 Severity: normal with version 2.0.6-4 of munin-plugins-extra, I get the following stack trace when running the ipmi_sensor_ script: munin-run ipmi_sensor_u_degrees_c Traceback (most recent call last): File

Bug#728840: munin-plugins-extra: ipmi_sensor_ doesn't properly import os

On 06/11/13 03:06 PM, Steve Schnepp wrote: tags 728840 + upstream fixed-upstream done thanks for the quick response! On Wed, Nov 6, 2013 at 6:06 AM, Gabriel Filion gabs...@lelutin.ca wrote: simple fix would be to add a line import os before line 73 like this: Thx. Note that I just

Bug#706115: lighttpd bind to port 80 even though it's configured not to

Package: lighttpd Version: 1.4.28-2+squeeze1.3 Severity: important lighttpd on my setup is currently not configured to bind on port 80, but still does it. as a result, if something else started before it that has already bound to port 80, lighttpd simply refuses to start. in my case, I have

Bug#708865: spamassassin reload gives error msg about no Perl found

Hey there, I'm seeing this error too with package 3.3.2-5 in wheezy 7.2 also, since the daily cronjob in /etc/cron.daily/spamassassin calls invoke-rc.d spamassassin reload, I get an error message every night about the reload returning an error code. -- Gabriel Filion signature.asc

Bug#724006: Impossible to send out the email via MTA with some ISPs

to use port 587. or maybe just a documentation update to tell users how to use --no-mail and to pipe that into something that'd get the mail in the user's MUA. it gets complicated to document all the options, though. -- Gabriel Filion signature.asc Description: OpenPGP digital signature

Bug#724007: gitignore misses some products of setup.py

Package: monkeysign Version: 1.0 current .gitignore file does not ignore the man and build directories. since these two are products from the build process with setup.py, they should be ignored. -- Gabriel Filion signature.asc Description: OpenPGP digital signature

Bug#330885: postfix: default configuration should enable use of TLS for stmp as default

for smtp_tls_security_level. (sorry to revive this old issue, but it's such a simple change and it hasn't recieved any love for so long) -- Gabriel Filion signature.asc Description: OpenPGP digital signature

Bug#658896: Still an issue

. -- Gabriel Filion signature.asc Description: OpenPGP digital signature

Bug#741969: postfixadmin: please package version 2.3.7

Package: postfixadmin Version: 2.3.5-2 Severity: normal Hi there, version 2.3.7 was released on 2014-02-20 according to the project download page[1]. [1]: http://sourceforge.net/projects/postfixadmin/files/postfixadmin/ version 2.3.5 is now two years old. while there haven't been all that much

Bug#725113: monkeysign: please support monkeysign --version

, but it could easily be done. and with this info already in place, implementing --version is just a matter of printing __version__ ;) -- Gabriel Filion signature.asc Description: OpenPGP digital signature

Bug#725113: [PATCH] Implement --version option

On 30/07/14 01:37 AM, gabs...@lelutin.ca wrote: From: Gabriel Filion gabs...@lelutin.ca The version information is actually already available, so we just need to add the proper option to display it. oh, sorry I forgot to mention that this patch was based on current 2.x, e.g. commit

Bug#720050: monkeysign: -u should take full fingerprint

blob for the -u option? like this: monkeysign -u 1234 5678 9ABC ... --other-options the above seems to be working for me with the 2.x branch. -- Gabriel Filion signature.asc Description: OpenPGP digital signature

Bug#756540: monkeysign: no debugging info from smtp connection

Package: monkeysign Version: 2.x Severity: normal Hi there, I've been using monkeysign 2.x (from git repos) and by making a user error, I've actually hit some real uglyness from python's smtplib that crackles up all the way to the user: if you give some string that smtplib doesn't like as the

Bug#757170: fail2ban: sasl jail misbehaves and does not match most of the time

Package: fail2ban Version: 0.8.6-3wheezy2 Severity: normal Hello, I've configured a sasl jail to catch annoying ppl who abuse of SMTP auth. It uses the sasl filter provided with the package. However, it doesn't seem to be matching anything.. I tested the regexp from the jail on the configured

Bug#760717: monkeysign chokes when gpg wants user to run with --check-trustdb

Package: monkeysign Version: 2.x Severity: normal with current master (commit 5a8d12914a8d4388c6543056098276f6e756e483) when I try to sign a key, gpg emits an error message about needing to run with --check-trustdb, and apparently monkeysign is choking on this output with the following debug

Bug#756540: monkeysign: no debugging info from smtp connection

I've tested the patch and found a bug with it. The msg argument gets overridden by the new error handling code and provokes a traceback. You'll find a patch attached to fix said issue. -- Gabriel Filion From f0962aa6b8b539b04497bd3d3a71983a5ff67097 Mon Sep 17 00:00:00 2001 From: Gabriel Filion

Bug#756540: [PATCH] catching error from non-imported module

commit 1dbc8ce added more error handling around smtp connections but forgot to import the module socket to be able to catch exceptions defined in that module. --- monkeysign/ui.py | 1 + 1 file changed, 1 insertion(+) diff --git a/monkeysign/ui.py b/monkeysign/ui.py index 41f68fb..d51b319 100644

Bug#756540: one more patch and testing

of the output. we can see the debugging output from smtplib followed by the output from the error handling. with debugging turned off, I see only the error message about the connection being refused. so I guess we can say this is a mission complete :) -- Gabriel Filion signature.asc Description

Bug#767659: evince 3.14.1-1 gets undefined symbol with libpoppler46:i386 earlier than 0.26.5-2

the problem seems to be coming from the version difference between libpoppler46 and libpoppler-glib8, this bug report might be more suited to the library libpoppler-glib8, since that's the package that's depending on libpoppler46 -- Gabriel Filion signature.asc Description: OpenPGP digital

Bug#770348: munin-node: no means of disabling cron job

Package: munin-node Version: 2.0.6-4+deb7u2 Severity: normal There is currently no means of disabling the munin-node cronjob, which runs apt-get update every hardcoded X amount of time. For ppl who don't want to use the apt* plugins it is undesirable to run the cronjob at all. -- System

Bug#770348: closed by Holger Levsen hol...@layer-acht.org (Re: [Packaging] Bug#770348: munin-node: no means of disabling cron job)

On 20/11/14 11:57 AM, ow...@bugs.debian.org (Debian Bug Tracking System) wrote: On Donnerstag, 20. November 2014, Gabriel Filion wrote: There is currently no means of disabling the munin-node cronjob, which runs apt-get update every hardcoded X amount of time. For ppl who don't want

Bug#774643: verify_active_connections is not present in ruby-activerecord 4.1.8

one of the crucial modules, like mod_rewrite. We really do need to find a solution to this issue before jessie is released (or in the worst case, at first point release). -- Gabriel Filion signature.asc Description: OpenPGP digital signature

Bug#782169: mosh: bash_completion script does not complete hosts from known_hosts

was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Gabriel Filion gabs...@lelutin.ca To: Debian Bug Tracking System sub

Bug#782169: mosh: bash_completion script does not complete hosts from known_hosts

On 08/04/15 04:28 PM, Gabriel Filion wrote: Package: mosh Version: 1.2.4a-1+b2 Severity: normal Tags: patch Dear Maintainer, [...] argh, sorry about that content duplication. I was having issues with configuring reportbug correctly so I saved the former report trial as a file. and I'm

Bug#639698: reportbug: STARTTLS failure - continue without TLS

attacks that could happen with STARTTLS and other protocols that permit this kind of fallback. The best option here should be to have a clear error message of what didn't work. -- Gabriel Filion signature.asc Description: OpenPGP digital signature

Bug#772222: bup: bashism in /bin/sh script

Hi there, I've just submitted a patch to the upstream mailing list in order to fix this bug. hopefully it can get merged relatively soon. https://groups.google.com/d/msg/bup-list/E_vFEF_12zo/CuwMH3kQiCIJ -- Gabriel Filion signature.asc Description: OpenPGP digital signature

Bug#683469: xserver-xorg-video-intel: Graphical distortion and text / font corruption in X

a thinkpad x201. I can send more info about my setup if this can help. -- Gabriel Filion signature.asc Description: OpenPGP digital signature

Bug#768005: Please support xl xen management command

This would've been great to have for the jessie release. The lack of completion for xl makes using this command quite annoying. Since most of the commands are the same as with xm, we could start with cloning the completion file for xm and work out the differences from there. -- Gabriel Filion

Bug#803386: icedove: segfaults in MessageChannel.cpp

Package: icedove Version: 42.0~b1-1 Severity: important Hello, I'm experiencing random segfaults in icedove and it doesn't seem to correspond to the other ones that were reported. So far the only useful information I have is from syslog just before and during the crash: Oct 29 09:36:07 boohn

Bug#749315: Same issue with main screen temporarily

and clicking on "Apply". For some reason gnome was confused about the screen being the main one, and it got fixed by applying configuration. -- Gabriel Filion signature.asc Description: OpenPGP digital signature

Bug#803386: icedove: segfaults in MessageChannel.cpp

On 29/10/15 10:35 AM, Carsten Schoenert wrote: > On Thu, Oct 29, 2015 at 10:21:22AM -0400, Gabriel Filion wrote: >> I'm experiencing random segfaults in icedove and it doesn't seem to >> correspond >> to the other ones that were reported. >> >> So far the only

Bug#801425: dbus: upgrade from dbus 1.10.0-2 to 1.10.0-3 breaks policykit

Hi there, On 10/10/15 06:59 PM, Simon McVittie wrote: > On 10/10/15 17:38, Gabriel Filion wrote: > It would be really useful to see any systemd, policykit-1 (polkit) > and/or dbus warnings/errors from 2015-10-09, from your syslog. If you > would prefer not to send that day's syslo

Bug#801425: dbus: upgrade from dbus 1.10.0-2 to 1.10.0-3 breaks policykit

On 16/10/15 03:45 PM, Simon McVittie wrote: > Control: tags 801425 + unreproducible > Control: block 801425 by 801354 > > On 16/10/15 20:03, Gabriel Filion wrote: >> fwiw, dbus was upgraded again to 1.10.0-3 and later I downgraded >> policykit-1 to 0.105-12, the version

Bug#801425: dbus: upgrade from dbus 1.10.0-2 to 1.10.0-3 breaks policykit

Package: dbus Version: 1.10.0-3 Severity: grave Justification: renders package unusable Hi, I'm running sid and this morning I performed an apt-get upgrade and a dist-upgrade. This pulled in dbus 1.10.0-3. Upon restart, systemd was hanging for a bunch of time with messages like the following:

Bug#761985: Master.csv rotation

Hello there, I personally don't see a difference between a text file with lines that track web site visits and a text file with lines that track calls being made and received. The Master.csv file is enabled by default and never rotated. This means that ppl who don't know too much about how

Bug#778794: postfixadmin: Please change the dependencies/recommendations

The dependencies currently have mysql-server as a recommends only, so you can avoid installing it by using --no-install-recommends. the same would hold for dovecot-* There is however a dependency on mysql-client which would prevent one from using mariadb-client (and would cause a conflict with

Bug#819218: postfixadmin: A newer version, 2.93 should be packaged

Package: postfixadmin Version: 2.3.7-1 Severity: normal Dear Maintainer, A newer version of PostfixAdmin has been available for some time. The software author, Christian Boltz said recently[0] on the upstream mailing list that this version is considered stable. [0]:

Bug#811542: [Pkg-mailman-hackers] Bug#811542: mailman: Update configuration for Apache 2.4

> On Tue, January 19, 2016 18:37, David Magda wrote: > > Package: mailman > > Version: 1:2.1.18-2 > > Severity: important > > > > The current copy of /etc/mailman/apache.conf in the mailmain package > > has configuration items that are for Apache 2.2. For example: > > Thanks. This has been fixed

Bug#596668: mailman: newlist crashes

wow this has been laying around for sooo long. current jessie version is 2.1.18 and that same line that was bugging is now #739 however, I've tried to reproduce the issue in jessie with the same list@domain and with different ones and I couldn't. I don't know if it could be linked to locale or

Bug#837451: xserver-xorg-core: visual flashes followed by hard crash upon keyboard interaction with thinkpad x201

Package: xserver-xorg-core Version: 2:1.18.4-2 Severity: important Hi there, I've been having weird crashes that happen only when I interact with my keyboard. It also happens with a keyboard plugged in to USB port. I didn't know where exactly to look, so I "bisected" packages with the help of

Bug#778695: wheezy -> jessie: no gdm3 prompt, dependency loops and broken initrd

Hello, I've worked a little bit on this in the same setup as Anarcat used, here at koumbit. I've figured out why the users were not listed in gdm3. It was a line in /etc/pam.d/common-session that was missing: session optionalpam_systemd.so with this line users are listed. This problem

Bug#836984: parcimonie unable to call "gpg2" since sid switch to using gpg2 as main "gpg" command

Package: parcimonie Version: 0.10.2-1 Severity: grave Justification: renders package unusable Hi there, Ever since gnupg 2.1 was set to be the main "gpg" command in sid, parcimonie has been unable to do its bidding. >From the process list, we can see the following: gabster 6219 0.1 1.2

Bug#837451: xserver-xorg-core: visual flashes followed by hard crash upon keyboard interaction with thinkpad x201

Hello, intrigeri: > Gabriel Filion: > >> […] and found out that xserver-xorg-core version 1.18.3-2 was >> introducing this issue. Downgrading to 1.18.3-1 makes the visual flashes and >> hard crashes go away. > > /usr/share/doc/xserver-xorg-core/NEWS.Debian.gz reads

Bug#836266: dirmngr: Please disable "use-tor" by default.

Hi there, For what it's worth I've been experiencing the same issue up to now: impossible to search or get keys with "use-tor" enabled, which was forced into the config file seemingly by parcimonie. However it's just been resolved by an upgrade of gnupg/dirmngr to the latest version in sid,

Bug#845278: libxtables12: can't be installed

Hello, I've just exerienced the same during an upgrade of sid packages. The only way to break out of this mess is to force the upgrade of the package with: dpkg --force-overwrite -i /var/cache/apt/archives/libxtables12_1.6.0+snapshot20161117-2_amd64.deb then it becomes possible to continue

Bug#845278: libxtables12: can't be installed

Gabriel Filion: > I've just exerienced the same during an upgrade of sid packages. > > The only way to break out of this mess is to force the upgrade of the > package with: > > dpkg --force-overwrite -i > /var/cache/apt/archives/libxtables12_1.6.0+snapsho

Bug#847992: mysql-server-core-5.6 upgrade to stretch fails with file conflict on innochecksum.1.gz

Package: mysql-server Version: 5.5.53-0+deb8u1 Severity: important Hello, I'm trying to upgrade from jessie to stretch and I'm getting blocked on the mysql upgrade from 5.5 to 5.6 During the upgrade I get this error message: dpkg: mysql-client-5.5: dependency problems, but removing anyway as

Bug#847991: initramfs-tools: upgrade to stretch in kvm image fails when trying to copy 70-persistent-net.rules

Package: initramfs-tools Version: 0.120+deb8u2 Severity: important Hi there, I've tried upgrading a VM from jessie to stretch and I'm having an issue with initramfs-tools. The upgrade is from 0.120+deb8u2 to 0.125. The system is a KVM image of debian jessie (vanilla debian install with only

Bug#838533: [vagrant] vagrant cannot connect via ssh to the virtual machine

Hi there, I'm still experiencing this issue with a centos 7 box. I believe the fix was released in upstream version 1.9.0. bumping code version in package would probably fix this. signature.asc Description: OpenPGP digital signature

Bug#848492: broken tomcat6 package on wheezy

I am experiencing the same thing here. downgrading to deb7u3 does bring the service back online. I'm also seeing the same log messages than what's described in the mailing list discussion pointed out by brainpower. signature.asc Description: OpenPGP digital signature

Bug#837451: xserver-xorg-core: visual flashes followed by hard crash upon keyboard interaction with thinkpad x201

intrigeri: >> Also, when using the above-mentioned technique for forcing the driver to >> "intel" (I've confirmed that it loaded by looking at >> ~/.local/share/xorg/Xorg.log.0), I don't see visual flashes anymore. > … and no crashes either? right, no crashes either. I've been running with newest

Bug#837451: xserver-xorg-core: visual flashes followed by hard crash upon keyboard interaction with thinkpad x201

Hi there, bertagaz: > Uwe reported that with a newest release of xserver-xorg-core, the > bug disappeared. [1] > > There has been new uploads recently in Stretch and Sid, which now have > 2:1.19.2-1 and 2:1.19.3-1 respectively. > > Is one of this versions the one supposed to have "fixed" the

Bug#857444: [debian-mysql] Bug#857444: Bug#857444: mysql-server-5.5: upgrade from jessie to stretch leaves mysql server uninstalled

Otto Kekäläinen: >>> One way to make this an easier transition would be to have a >>> mysql-server package in stretch that's a dummy package that depends >>> on >>> default-mysql-server, and that has an upgrade notice about the >>> transition to mariadb that is happening. > > The transition is

Bug#857444: [debian-mysql] Bug#857444: mysql-server-5.5: upgrade from jessie to stretch leaves mysql server uninstalled

Lars Tangvald: > > - gabs...@lelutin.ca wrote: > >> Ugh, I fail at reportbug again :( >> >> real sorry about the initial report. >> >> here's the real description of the problem: >> >> >> when upgrading from jessie to stretch, the upgrade goes through >> without >> an error but the end

Bug#860362: release-notes: [stretch] wrong versions for OpenSSH in "what's new"

Package: release-notes Severity: normal Hello, The versions currently listed in the "What's new" section for OpenSSH do not correspond to reality. Please find attached a patch to correct the version numbers for OpenSSH in that section. -- System Information: Debian Release: 9.0 APT

Bug#816399: pass: Pass does not locate gpg secret key

Paul, When I migrated to gpg 2.1, I've had issues with "secret key not found" errors. This was caused by the fact that pass had installed gnupg2 as a dependency long ago but I was still using gpg 1.4 for a good while before migrating, so there were indeed keys missing. If this sounds like your

Bug#860353: pass: extraneous reencryptions

Package: pass Version: 1.6.5-4 Severity: normal Hello, Version 1.6.5 suffers from a small but irritating bug: some commands like init, mv are calling a check for whether or not a file needs to be reencrypted. That check has a bug that makes it always reencrypt files in certain circumstances.

Bug#860817: kedpm: Information leak via the command history file

Source: kedpm Version: 1.0 Severity: grave Tags: upstream security Justification: user security hole Hello, I've discovered an information leak that can give some hints about what ppl search and read in the password manager. kedpm is creating a history file in ~/.kedpm/history that is written

Bug#857444: mysql-server-5.5: upgrade from jessie to stretch leaves mysql server uninstalled

Package: mysql-server-5.5 Version: 5.5.54-0+deb8u1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was

Bug#857444: mysql-server-5.5: upgrade from jessie to stretch leaves mysql server uninstalled

Ugh, I fail at reportbug again :( real sorry about the initial report. here's the real description of the problem: when upgrading from jessie to stretch, the upgrade goes through without an error but the end result is that mysql-server-5.5 gets removed and mysql is not running anymore.

Bug#837451: xserver-xorg-core: visual flashes followed by hard crash upon keyboard interaction with thinkpad x201

Hi all, intrigeri: > Gabriel Filion: >> but yeah I could disable the force (, luke) and see if I can reproduce >> the bug again with the newer package versions. > >> I'll see if I can do that on sunday > > Ping? sorry it took me so much time. I upgraded xserver-x

Bug#857444: [debian-mysql] Bug#857444: Bug#857444: mysql-server-5.5: upgrade from jessie to stretch leaves mysql server uninstalled

Hi there, I've traced inter-package links (depends, conflicts et al) and I think I found the reason why the server gets removed. stretch still has a mysql-common package that has a "Replaces:" for mysql-server-5.5. during a dist-upgrade mysql-common will get upgraded to the stretch version,

Bug#860337: php7.0: No transition path from php5 to php7.0 when upgrading to stretch

Hello, for a little bit of additional information, the mysql to mariadb transition decided to use a meta-package called default-mysql-server to provide a path for the transition during the upgrade. Since php5 and php7 have a good number of differences, it might be desirable to have some kind of

Bug#865820: vim-common: Change of behaviour for default value of mouse is annoying

Package: vim-common Version: 2:8.0.0197-3 Severity: wishlist Hello, The default value for the mouse global variable has been changed from empty string to "a" starting from stretch. This is annoying and does not respect what is documented as the upstream default value: 'mouse'

Bug#470417: new upstream version out with ipv6 support

Hello, Just wanted to send a ping to this bug report. apparently 0.10.0 has finally been released with IPv6 support just a couple of days ago: https://github.com/fail2ban/fail2ban/releases/tag/0.10.0 maybe 0.10.0 should go to unstable? signature.asc Description: OpenPGP digital signature

Bug#861691: postfixadmin 3.0 not compatible with php 7

I've hit errors now on a fresh install of postfixadmin on stretch with php 7.0. The error says "MySQL 3.x / 4.0 functions not available! (php5-mysql installed?)" although php-mysql *is* installed. I've looked up in the source code what triggers that error and it's a test to ensure that function

Bug#861691: postfixadmin 3.0 not compatible with php 7

Gabriel Filion: > As this page [0] suggests that function was deprecated in php 5.5 and > completely removed in php 7, so that means that the postfixadmin > codebase is not even compatible with PHP 7. please disregard this comment.. apparently the issue is caused by the post-insta

Bug#858005: postfixadmin: upgrade.php fails at various places because of too long indexes

Hi there! I've replicated the issue when running setup.php right after an installation of postfixadmin. Then I've applied the patch linked to by Jascha and I can confirm that it does solve the issue. With the patch applied, the setup.php script calls upgrade.php and successfully creates the

Bug#881460: apparmor-profiles: dhclient set to enforce prevents getting an IPv4 with DHCP

intrigeri: > Let's sort this out first as there seems to be a misunderstanding. > IMO this bug is not RC because: > > 1. The profile this bug report is about is not enforced by default; >it's not even shipped in /etc/apparmor.d. It takes 2 manual steps >to enforce it, so thankfully, we're

Bug#881460: apparmor-profiles: dhclient set to enforce prevents getting an IPv4 with DHCP

Package: apparmor-profiles Version: 2.11.1-3 Severity: critical Justification: breaks unrelated software Hello, I've started using apparmor very recently, and when I rebooted to activate the kernel part, I didn't notice the issue below.. but a couple reboots afterwards I couldn't obtain a DHCP

Bug#878203: apparmor logs /proc//cmdline denials on vm shutdown

Hello, I can still see this in the apparmor file included in libvirt-daemon-system 3.9.0-1 FWIW according to this ubuntu bug they've added a line to the profile to permit access: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1693115 signature.asc Description: OpenPGP digital

Bug#879230: puppet-common: puppet warns about a duplicate key :queue_type in defaults.rb on every run

Package: puppet-common Version: 3.7.2-4+deb8u1 Severity: minor Tags: patch Hello, I'm running puppet 3.7 from jessie with ruby 2.3 in stretch (I know this is a bit convoluted, but that's because the master is still running 3.7) On every run of the puppet client, I'm getting the following

Bug#887395: vim-puppet: package vim plugin from rodjek

Package: vim-puppet Version: 3.8.5-2 Severity: normal Hello, The vim-puppet package has no package above debian jessie. I can understand why that happened: the puppetlabs vim plugin has not been maintained for so long! There is however an alternative that's available:

Bug#887395: vim-puppet: package vim plugin from rodjek

Stig Sandbeck Mathisen: >> On 15 Jan 2018, at 21:36, Gabriel Filion <gabs...@lelutin.ca> wrote: >> >> Package: vim-puppet >> Version: 3.8.5-2 >> Severity: normal >> >> Hello, >> >> The vim-puppet package has no package above debian jessi

Bug#888055: ikiwiki: Fenced code block rendering has been broken

Simon McVittie: >> [Fenced code blocks were] activated by an option when ikiwiki was >> calling discount, and >> for some reason that option was removed. So all fenced code block >> rendering was completely broken by that change. > You seem very sure that this was caused by an ikiwiki change. Can

Bug#889855: apticron: on each run, getting twice: W: --force-yes is deprecated

Package: apticron Version: 1.1.61 Severity: normal Hello, Ever since we have stretch servers using apticron, we're getting emails from the cron runs that show only two warning messages, twice the same line: W: --force-yes is deprecated, use one of the options starting with --allow instead.

Bug#826041: Bug#816391: tor: "systemctl status tor" does not provide useful output

On Wed, 1 Jun 2016 19:13:26 + Peter Palfrader wrote: > Michael Biebl schrieb am Donnerstag, dem 14. April 2016: > > Am 14.04.2016 um 00:46 schrieb Michael Biebl: > > > The tor.service afaics is only used, so you have a > > > systemctl restart/reload tor > > > shortcut which

Bug#889855: apticron: on each run, getting twice: W: --force-yes is deprecated

Gah! I did a little bit more research and found out that the warning was not replicating on stretch hosts managed elsewhere. This led me to find that the warning was *not* caused by aptitude itself but rather by an option in apt.conf.d/ that was configured by our configuration management (e.g. it

Bug#906444: vagrant: New upstream version 2.1.2 available

Package: vagrant Version: 2.0.2+dfsg-3 Severity: normal Hello, There is currently a new version available upstream, 2.1.2. It would be nice to have access to this version in debian sid, and potentially soon afterwards in buster. The 2.1.x branch adds some interesting features like triggers for

Bug#905752: smokeping: FPing target supports and prefers IPv6, preventing IPv4 pings

tags 905752 + upstream forwarded 905752 https://github.com/oetiker/SmokePing/issues/95 thanks Hi there, On 2018-08-08 08:49 PM, Mark Kamichoff wrote: > It appears that as of 3.16, FPing is no longer a multi-call binary and > /usr/bin/fping and /usr/bin/fping6 act the same. This ultimately >

Bug#824712: RFH: smokeping

Hi there! I've been doing some work on the smokeping package in the past few weeks/months with anarcat. Namely, * a new upstream release was packaged and sent to experimental, and we're trying to get it into sid very soon. * I've written and submitted a patch upstream in response to a bug

Bug#860264: Acknowledgement (nfs-kernel-server: NFS starts before DNS works, "exportfs: Failed to resolve ...")

Hi! I'm currently experiencing the exact same issue with an NFS mount for /home, and another nfs mount (from another server) that gets mounted under /srv/something: at boot, nfs mount times out, and afterwards when the boot is complete, if I ssh in and execute "mount -a" as root the mount points

Bug#888055: ikiwiki: Fenced code block rendering has been broken

Package: ikiwiki Version: 3.20170111 Severity: normal Hello, I've been using fenced code blocks for a while since I usually post about technical issues or howtos. That used to be available in Discount, used through ikiwiki, with a line that contains only a set of more than three ~ characters

Bug#892908: puppet 5 is now builtin to puppet since 4.9

Package: puppet Version: 5.4.0-1 Severity: minor Hello, Hiera version 5 is now built into puppet. It's been so since 4.9 ref: https://docs.puppet.com/hiera/#note-weve-released-a-major-update-to-hiera-called-hiera-5 It's now possible to perform a hiera lookup with: puppet lookup key_name

  1   2   3   >