Package: libldap-2.4-2
Version: 2.4.23-7.2
Severity: normal
Tags: patch
When using SASL authentication over TLS, if a request is larger than ~16k, the
client library will issue the error message Cannot connect to server. The
reason for this is that the SASL layer (which just passes the data for
Please note that the OpenLDAP maintainers don't have a lot of spare capacity
to go around, so it's unlikely that there will be a stable update to squeeze
for this bug.
Is there any way for me to help out? It basically is just a trivial
patch that has to be added to debian/patches/ of the
Package: syslog-ng-core
Version: 3.3.5-4
The syslog-ng init script for sysvinit contains the line
install -d /var/lib/syslog-ng
before calling start-stop-daemon to start the daemon. The unit file
does not. This causes syslog-ng to fail if installed on a Debian system
using systemd as init
I stumbled upon this bug while using a backported kernel on squeeze,
and in the process of trying to find a solution, I noticed that there
is also a bug report against Ubuntu kernels in launchpad. The patch
attached to a comment there that reverts a certain commit seems to
solve the problem for
Package: linux
Version: 3.2.35-2
Severity: wishlist
In the current Wheezy kernel, all EDAC modules are built save for the
one for
Intel's Sandy Bridge architecture. It would be nice if one could read
out
EDAC on Sandy Bridge systems, thanks!
The missing kernel configuration is:
Hi there,
Preface: I'm not involved with the Debian project directly other than as
a user. So while I personally have strong opinions when it comes to the
init system, so far I have just followed the debate because I didn't
feel it would be helpful to spam this bug with useless comments. That
Package: linux
Version: 3.2.54-2
Severity: wishlist
Some hardware vendor tools (e.g. HP Library and Tape Tools) still rely
on the
existence of /proc/scsi.
In Squeeze /proc/scsi was re-enabled in linux-2.6 (2.6.32-32) see also
#618258
and it is still default upstream:
path:
Hello,
I'm sorry if this seems pushy, but since it is trivial to implement
this
change, I'd like to ask if you've considered reenabling
CONFIG_SCSI_PROC_FS?
Thank you!
Regards,
Christian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Package: ocsinventory-reports
Version: 2.0.5-1.1
Severity: important
Dear Maintainer,
php5-mysqlnd is a compatible drop-in replacement for php5-mysql. The
API is identical. Depending on php5-mysql without an alternative
forcibly removes php5-mysqlnd and forces the installation of php5-mysql
Package: ocsinventory-reports
Version: 2.0.5-1.1
Severity: important
Dear Maintainer,
ocsinventory-reports oversanitizes GET and POST data. In
require/header.php there are the following three lines 179-181:
//SECURITY
$protectedPost=strip_tags_array($_POST);
Package: glpi
Version: 0.83.31-1
Severity: normal
Dear Maintainer,
php5-mysqlnd is a compatible drop-in replacement for php5-mysql. The
API is identical. Depending on php5-mysql with only php4-mysql an
alternative (which btw. was removed from Debian a long time ago, before
Squeeze even), causes
According to the upstream report, this was supposedly fixed in 2.0.10.
I haven't tested that specific version, but 2.0.21-2~bpo70+3 from
wheezy-backports does NOT contain this bug anymore, while I did have
the same problem as the bug submitter when using 2.0.6-4+deb7u2 from
wheezy.
Regards,
1.1.11-1
Description: Respect EDITOR and PAGER environment variables
Make crmsh properly respect EDITOR and PAGER environment variables,
which did not work properly before.
Author: Christian Seiler christ...@iwakd.de
Last-Update: 2014-05-26 18:04:00+0200
---
This patch header follows DEP-3
I've also submitted this issue to the upstream project:
https://github.com/crmsh/crmsh/issues/44
Regards,
Christian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I have also posted this bug upstream, together with a couple of other
issues:
https://bugs.launchpad.net/ocsinventory-ocsreports/+bug/1342210
(currently still private)
Regards,
Christian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Control: tags -1 fixed-upstream
FYI: This bug was just fixed upstream:
https://github.com/crmsh/crmsh/commit/b5962a2bb1d98d53ed559cb27be17e2041bab68c
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Confirmed that this bug is fixed with the following packages:
ii cgmanager 0.33-2 amd64
Central cgroup manager daemon
ii linux-image-3.17-1-amd643.17-1~exp1 amd64
Linux 3.17 for 64-bit PCs
ii
,
Christian Seiler
From e8e0163e981bb57ebe7edfdc758d6ce9e9a51b9b Mon Sep 17 00:00:00 2001
From: Christian Seiler christ...@iwakd.de
Date: Tue, 7 Oct 2014 15:28:46 +0200
Subject: [PATCH] Bugfix: make skipping savelog task actually work
---
lib/subroutines |4 ++--
1 file changed, 2 insertions(+), 2
Control: found -1 3.16.3-2
Hi,
Since the freeze for Jessie is around the corner, I wanted to ask if you
have considered enabling this again at least for Jessie?
Thank you!
Kind regards,
Christian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
also makes sure that if another
earlier hook made the call to skip savelog, this will also be honored.
Thanks!
From 8542d992bef188c3c58b649455bf24ee288b305e Mon Sep 17 00:00:00 2001
From: Christian Seiler christ...@iwakd.de
Date: Mon, 6 Oct 2014 17:43:56 +0200
Subject: [PATCH] On failure: also call
Package: fai-client
Version: 4.0.8~deb7u1
Severity: wishlist
Dear Maintainer,
Currently, if $FAI_ACTION is install, and the installation fails, bash
is run on the computer to be installed. This is not always ideal,
however, since some administrators might want to lock down local
computers as
Am 02.11.2014 06:59, schrieb Josh Triplett:
Apart from that, I would still request that someone with the ability to
produce a modified local mirror test the two critical cases mentioned in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746578#129 . If those
two cases work, then systemd
Am 04.11.2014 17:07, schrieb Josh Triplett:
This isn't a complete showstopper, since most of the time people seem to
debootstrap a standard system and then install additional packages.
However, it would affect a debootstrap with --include=task-desktop or
--include=gnome or similar.
Just as a
Source: linux
Version: 3.16.7-2
Severity: important
Tags: upstream patch
Dear Maintainer,
in certain circumstances, the kernel may busy-wait indefinitely after
processing a SIGKILL to a process when using NFS. There is a patch for
this
issue that went into 3.17:
Dear ctte,
after having watched this discussion from the sidelines a bit, I'd
like to offer a few thoughts on this topic.
First of all, as for the technical issue of how to NOT cause the init
system to be switched when updating from wheezy to jessie: all
proposed solution I've seen in this
Sorry, stupid webmail, sent my email to early...
and only to the mailing list, not the bugtracker... :(
To make sure it's recorded in the bug, and I also added something to
the end:
Am 2014-12-04 19:31, schrieb Christian Seiler:
Am 2014-12-04 18:21, schrieb Adam Borowski:
On Thu, Dec 04, 2014
Control: reopen -1
Control: found -1 2.0.5-1.2
Dear Maintainer(s),
Sorry to reopen this bug, but your updated package doesn't actually
really fix this. You followed my advice for adding the alternative
dependencies (for which I'm grateful), but you didn't consider my point
2 in my original
Hi again,
also, if I manually edit
/var/lib/dpkg/info/ocsinventory-reports.postinst and modify the line
apache2_invoke enmod php5
to
apache2_invoke enmod php5 || :
in order to make the package configure, the default configuration in
/etc still doesn't work properly (apache2 reload fails,
(Since I didn't get cc'd in the original reply, I'm replying here. Sorry
about that.)
Am 26.01.2015 um 16:12 schrieb Ritesh Raj Sarraf:
On 01/26/2015 07:54 PM, Michael Biebl wrote:
unblock open-iscsi/2.0.873+git0.3b4b4500-4
That patch doesn't look right.
Calling systemctl from an init script
Am 26.01.2015 um 08:47 schrieb Ritesh Raj Sarraf:
On 01/25/2015 09:43 PM, Christian Seiler wrote:
The same fix that was implemented for open-iscsi in principle also
applies for multipath-tools, i.e. make sure that for systemd systems
the unit is ordered before remote-fs-pre.target. I don't use
Hello Ritesh,
the system boot will hang for 90s because of systemd's default
timeout
when devices are not available.
Actually, from what I know so far, systemd aggressively backgrounds
any
processes that is taking time. And only processes that depend on it,
are
put on hold, again in the
Package: open-iscsi
Version: 2.0.873+git0.3b4b4500-4
Severity: normal
Dear Maintainer,
(as per discussion on bug #775778 I'm filing a separate bug report for
this issue)
If you have the following configuration:
- iSCSI disk
- LVM on top, vg configured in /etc/default/open-iscsi
- logical
)
+ * Add dh-systemd to build-deps.
+ * Reorder #DEBHELPER# in postinst to not break upgrades (dh-systemd's
+code has to be there before invoke-rc.d is called).
+
+ -- Christian Seiler christ...@iwakd.de Mon, 19 Jan 2015 19:45:05 +0100
+
open-iscsi (2.0.873+git0.3b4b4500-4) unstable; urgency
Hi again,
Btw, in case it wasn't clear from my first reply here:
- there is this needless 90s delay (or whatever other delay the admin
has configured) in waiting on the iSCSI targets
Have you had luck root causing in why there is the 90 sec delay ?
systemd actively complains at boot
Control: tags -1 + confirmed
Am 2015-02-10 16:15, schrieb David Lambert:
Setting up open-iscsi (2.0.873+git0.3b4b4500-4) ...
update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults
update-rc.d: warning: start and stop actions are no longer supported;
.
Author: Christian Seiler christ...@iwakd.de
Origin: backport
Applied-Upstream: 4d858e7d9f39038713f760d7acc64acf7bba2aa7, 11c6476a08af7a8a9ae6a2d0f8370587f7b31663
Last-Update: 2015-02-17
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/src/login/logind-user.c
+++ b/src/login
/ or w/o override), it now
works as expected. I also looked at the function to see if there
were some other surprises in there, but the the rest just parses
headers.
I've attached an updated patch. Any objections to that?
Christian
From: Christian Seiler christ...@iwakd.de
Date: Tue, 17 Feb 2015
Am 17.02.2015 um 13:04 schrieb Christian Seiler:
Thinking about it, perhaps we could use Documentation=? Just add a
Documentation=file:///etc/insserv/overrides/$NAME? Then at least
systemctl status will show the information. Not perfect, but
probably better than nothing...
Somehow I think we
Am 2015-02-17 12:31, schrieb Michael Biebl:
Am 17.02.2015 um 01:08 schrieb Christian Seiler:
Only minor issue is that SourcePath= is a single-valued entry in
systemd, so I can't just add the override if it exists, and
FragmentPath= is only ever dynamically filled by systemd when
parsing,
so I
as
SourcePath=, of course, I don't have a strong opinion on either one of
these solutions.)
We are pretty late into the freeze though, so this would
require an ack from our release managers.
Do you want me to ask for pre-approval?
Christian
From: Christian Seiler christ...@iwakd.de
Date: Tue
Package: systemd
Version: 215-12
Severity: normal
Tags: fixed-upstream patch
Dear Maintainers,
please consider backporting the fixes in upstream that make logind
work if CAP_SYS_ADMIN is not set, namely:
Am 27.01.2015 um 15:39 schrieb Michael Biebl:
Am 27.01.2015 um 13:07 schrieb Christian Seiler:
Am 27.01.2015 um 06:19 schrieb Michael Biebl:
- Drop $remote_fs from the open-isci LSB header and replace it with
$local_fs. That looks wrong anyway.
As I said before: that breaks sysvinit systems
Am 27.01.2015 um 06:19 schrieb Michael Biebl:
Of course, if you have a better idea of how to do this?
Aside from shipping real native unit files, that's probably the least
invasive change:
- Drop $remote_fs from the open-isci LSB header and replace it with
$local_fs. That looks wrong
Am 2015-01-25 16:47, schrieb Christian Seiler:
Btw. I noticed a small problem with my fix w.r.t open-iscsi here: my
fix currently does not cover the iscsi alias (Provides line in LSB
header), so on systemd systems (sysvinit is not affected) with my
fix,
anything ordered against iscsi
Am 2015-01-25 16:37, schrieb Ritesh Raj Sarraf:
I cut out the multipath stack just to see if there is some fix we
can
push. So yes, your patch works perfect in a non-multipath setup. I'll
ask release team for an exception.
For multipath, I need to figure out some time to root cause it. But
Control: reassign -1 multipath-tools
Control: found -1 0.5.0-5
Dear multipath-tools Maintainers,
this is bug, which is a clone of #775778, is essentially the same
problem as was discussed in #775778: the ordering of the
multipath-tools init script after after $remote_fs (see Should-Start
line
Am 2015-01-25 17:16, schrieb Michael Biebl:
Am 25.01.2015 um 15:43 schrieb Ritesh Raj Sarraf:
I've still kept the systemd folks in the loop, hopefully they may be
able to shed some light.
I'd start by looking at the fedora package and see how the package is
integrated into the systemd boot
keyring.
Thanks a lot for taking the time to investigate this so thoroughly!
Christian
Am 25. Januar 2015 10:32:21 MEZ, schrieb Ritesh Raj Sarraf
r...@researchut.com:
On 01/23/2015 05:25 PM, Christian Seiler wrote:
Next, I'll verify your fix. Hopefully by this weekend I'll get it
ready
Hi Ritesh,
Am 2015-01-23 09:35, schrieb Ritesh Raj Sarraf:
I was able to reproduce the problem on my local setup. I've put up a
video just to be sure we are both referring to the same problem.
http://youtu.be/cwcnk00Hwk0 [1]
Yes, that's the same problem, that it waits 90s for the devices
Am 31.01.2015 um 08:48 schrieb Ritesh Raj Sarraf:
This is a follow-up on the comments that were made on changes to open-iscsi.
Please review attached debdiff, which should have all changes included.
Hi Ritesh,
I think you made a mistake: you've now merged both changes (the initial
ones that
already exited).
.
With this patch, journald will no longer silently discard messages
that are supposed to be sent to syslog in these situations.
Author: Christian Seiler christ...@iwakd.de
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
Index: systemd-215/src/journal/journald
Package: libtirpc1
Version: 0.2.5-1
Severity: normal
Dear Maintainer,
If I have the following configuration:
- Jessie
- sysvinit as init system
- /usr separate on NFS
the system won't boot properly and be unable to mount /usr, because
/sbin/mount.nfs{,4} tries to load libtirpc1 (which is
/debian/changelog 2015-02-10
20:10:11.0 +0100
@@ -1,3 +1,53 @@
+open-iscsi (2.0.873+git0.3b4b4500-8) unstable; urgency=medium
+
+ * [e707e75] Exclude iscsid.conf from dh_fixperms. (Closes: #735773)
+
+ -- Christian Seiler christ...@iwakd.de Tue, 10 Feb 2015 18:00:54 +0100
+
+open-iscsi
Control: clone -1 -2
Control: retitle -1 libtirpc: breaks ABI compatibility w.r.t. libc6 on 64bit
Control: reassign -2 quota 4.01-7
Control: found -2 4.01-2
Control: retitle -2 quota: use libtirpc's headers when linking against it
Control: severity -2 important
Control: tags -2 + patch security
Package: init-system-helpers
Version: 1.22
Severity: important
Tags: patch
Dear Maintainers,
deb-systemd-helper doesn't handle drop-ins at all (only the main
service file is parsed) and it doesn't treat lists properly: when
creating links for Alias=, it doesn't properly treat multiple entries
Control: severity -1 important
Control: tags -1 + patch
Dear Maintainer,
(Cc systemd maintainers, because it's of interest to them.)
I have created a patch that implements the previously missing parts of
systemd integration into update-rc.d, following along the lines of the
patch I have
Am 2015-03-16 13:51, schrieb Michael Biebl:
It would be great, if Mateusz can confirm that this patch [1] does
indeed fix his issue.
Mateusz, if you are not versed in compiling packages yourself and you
would prefer if we provided you with a test package, please let us
know.
I can also
Control: severity -1 serious
Control: tags -1 + patch
Dear Maintainers,
this doesn't only affect libvirt/KVM somewhat, but it also breaks LXC,
which also uses its own cgropus. lxc-attach will stop working once
systemctl daemon-reload has been issued with a running LXC instance.
Since this
Note that this is not necessarily only #777601, there's also #777164.
The fix in systemd 215-12 fixes part of the problem, but the other
part still persists.
I have posted a backported patch to #777164 for this issue (it's
fixed in 219 upstream).
Am 2015-03-20 06:25, schrieb Michael Biebl:
You can probably trigger this by putting 12 modules into
/etc/modules-load.d. Each one will generate a message for the
journal
and after the 11th the service will hang. Jupp, just tried it,
deadlocks. Will, kind-of, because after ~15s it will somehow
Am 2015-03-20 15:01, schrieb Raphael Hertzog:
On Sun, 15 Mar 2015, Christian Seiler wrote:
Control: severity -1 important
Control: tags -1 + patch
I'm tempted to raise the severity to serious as the current behaviour
is really bad for packages that ship both native .service files and
init
(Sorry for the noise, pressed 'send' to soon...)
Am 2015-03-20 15:01, schrieb Raphael Hertzog:
On Sun, 15 Mar 2015, Christian Seiler wrote:
Control: severity -1 important
Control: tags -1 + patch
I'm tempted to raise the severity to serious as the current behaviour
is really bad for packages
Package: fai-client
Version: 4.3.1
Severity: important
Dear Maintainer,
when using dracut as initrd (default with current FAI version), the
dhclient script will set the kernel's IP lifetime value to the DHCP
lease time. This change was introduced into dracut in [1] to signal
network management
Am 2015-03-10 11:53, schrieb Thomas Lange:
On Mon, 09 Mar 2015 19:11:19 +0100, Christian Seiler
christ...@iwakd.de said:
/sbin/ip -4 addr change $addr dev $iface \
valid_lft forever preferred_lft forever
On a wheezy nfsroot using kernel 3.2 this does not work. It says
Package: systemd
Version: 215-12
Severity: normal
Dear Maintainers,
while I was trying to set a different log level for systemd via DBus, I
accidentally forgot that the 'Set' method for DBus properties expects a
variant as a data type. So when using the following (wrong) command:
dbus-send
On 03/31/2015 04:44 PM, Michael Biebl wrote:
Am 31.03.2015 um 15:52 schrieb Christian Seiler:
Package: systemd
Version: 215-12
Severity: normal
Dear Maintainers,
while I was trying to set a different log level for systemd via DBus, I
accidentally forgot that the 'Set' method for DBus
Am 2015-03-03 15:33, schrieb Michael Biebl:
Am 02.03.2015 um 15:42 schrieb Christian Seiler:
- SOLUTION (mostly the same as before, but SendBuffer is set on a
different unit and a Condition is added to the service):
1. Increase max_dgram_qlen to a reasonable value. The easiest
Am 2015-03-03 16:26, schrieb Michael Biebl:
I did a couple more reboots and did indeed run into the problem, that
systemd-sysctl.service was started after syslog.socket, so I got the
missed XXX messages again.
Adding the After=systemd-sysctl.service ordering to syslog.socket
fixed
that. In [1]
I did some more tests on this and there is one key thing that I
misunderstood: SO_SNDBUF of the socket that is used to send the
datagrams is used as a limit in the kernel, not of the socket syslog
uses to receive them.
I actually tried setting SendBuffer=1 and ReceiveBuffer=1 on
syslog.socket
Control: severity -1 serious
(justification for severity: breaks unrelated software, in this case
all syslog daemons on a default installation; could possibly be
considered grave or even criticial - data loss affecting nearly all
users)
This bug is actually much worse than it seems. In fact, on
it.
Thank you for considering!
Christian
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759001
[1]
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=106;filename=sysv-generator-add-support-for-etc-insserv-overrides.patch;att=1;bug=759001
From: Christian Seiler christ...@iwakd.de
Date: Tue, 17
Control: tags -1 - moreinfo
Am 2015-02-25 21:27, schrieb Michael Biebl:
Am 25.02.2015 um 18:59 schrieb Christian Seiler:
Control: severity -1 serious
Thoughts?
Those missing syslog messages (only) happen when systemd flushes the
initial boot kernel/messages to the syslog socket, right
Am 2015-02-25 23:26, schrieb Michael Biebl:
If you need that kind of throughput, using the imjournal module might
possibly be the better choice (would need some testing, how mature
imjournal is). Unfortunately, it's not really possible to ship a
default
rsyslog configuration, which uses
Am 2015-02-26 00:04, schrieb Michael Biebl:
Also: I'm not looking for a solution that solves this for any
possible amount of log messages, but I do think that the current
limit doesn't provide enough of a safety zone that one would like
to rely on.
If we can make the journald - syslog
Small correction to my previous observations:
Am 2015-02-25 18:59, schrieb Christian Seiler:
- SendBuffer=8M will increase the max size of a single log message
that may be sent via this socket (8M is probably at bit much)
Actually that's not true. I've misread the kernel source here
Package: snmp
Version: 5.7.2.1~dfsg-7
Severity: important
Dear Maintainers,
The preinst script of the 'snmp' (client tools) package contains the
following code (if 'install' or 'upgrade' is passed):
killall -u snmp 2/dev/null || true
This was added here:
Package: lxc
Version: 0.8.0~rc1-8+deb7u2
Severity: wishlist
Dear Maintainer,
LXC 1.0 is required to properly support Jessie containers with systemd
on Wheezy hosts. (It alone is not sufficient, but without it it will
definitely not work.) I've attached the patch required to make the
package
Package: open-iscsi
Version: 2.0.873+git0.3b4b4500-8
(I'm reporting this to keep track of the issue. I've found this by
chance while improving the packaging.)
udebs are currently only built for select architectures. Unfortunately,
there are two separate lists that have gotten out of sync.
The
- changing finger memory is difficult, so I keep entering
'halt' instead of 'poweroff' occasionally
I had the same problem, so I added the following to my /root/.bashrc on
Jessie so I can retrain my finger memory:
#
Control: tag -1 + moreinfo
I just looked at this and am a bit confused w.r.t. x32:
The udeb depends on iscsi-modules, which is built from the linux kernel
source package. However, looking at a recent build log on x32 (and also
current sid source for the linux package), it doesn't appear to be
On 05/13/2015 09:04 PM, Cyril Brulebois wrote:
The issue is fixed in unstable (-9) in such a way that it won't
resurface again if the control file is updated to build the udeb for
even more architectures in the future.
I suppose you mean 3ea68751abe4f3cf4c44a9695fff8742f80f43b4;
Yes.
but
)
+
+ -- Christian Seiler christ...@iwakd.de Wed, 13 May 2015 20:01:02 +0200
+
open-iscsi (2.0.873+git0.3b4b4500-8) unstable; urgency=medium
* [e707e75] Exclude iscsid.conf from dh_fixperms. (Closes: #735773)
diff -Nru open-iscsi-2.0.873+git0.3b4b4500/debian/rules
open-iscsi-2.0.873+git0.3b4b4500/debian
On 04/11/2015 03:28 PM, Michael Biebl wrote:
Am 11.04.2015 um 12:14 schrieb Christian Seiler:
Package: systemd
Version: 215-15
Severity: minor
Tags: patch
Dear Maintainers,
with 215-13, hwclock-save.service was added to sync the system clock
with the hardware clock on shutdown. This will fail
Package: systemd
Version: 215-15
Severity: minor
Tags: patch
Dear Maintainers,
with 215-13, hwclock-save.service was added to sync the system clock
with the hardware clock on shutdown. This will fail in containers which
don't have the appropriate privileges (which is annoying, but not
really
Control: severity -1 minor
Control: reassign -1 systemd 215-17
Control: retitle -1 systemd: sysv-generator overzealous with log level
Am 2015-05-19 14:50, schrieb Mathieu Malaterre:
Seems like there is something going on wrong with systemd and current
jessie package. My dmesg reveals:
[
On 06/08/2015 01:54 PM, Axel Beckert wrote:
Package: wnpp
Severity: wishlist
* Package name: gtk3-nocsd
Upstream Author : PCMan pcman.tw -AT- gmail.com
* URL or Web page : https://github.com/PCMan/gtk3-nocsd
* License : LGPL-2.1
Description : LD_PRELOADable library to
Hi Axel,
On 06/09/2015 06:24 PM, Axel Beckert wrote:
Christian Seiler wrote:
- While this preloadable library does get rid of the window manager
hints that disable server-side decorations, it does not get rid of
the humongous title bars themselves. I've attached a screenshot
(Ccing the bugtracker because it appears you've stumbled upon a bug
that also a few other people had, see below. Please don't reply to the
bugtracker yourself unless you feel it's relevant for the bug report.)
Link to thread on debian-user for people reading the bug report:
On 06/27/2015 08:02 PM, Jonas Meurer wrote:
Am 27.06.2015 um 16:07 schrieb Christian Seiler:
Could you try to do the following:
1. create a directory /etc/systemd/system/remote-fs-pre.target.d
2. create a file /etc/systemd/system/remote-fs-pre.target.d/nfs.conf
with the following contents
On 07/05/2015 09:15 AM, Jackson Doak wrote:
It might be possible to rename the binary and symlink drive to it, which
would allow you to give the binary name over easier
Personally, I think it would be best not to reserve such a generic name
'drive' for such a specific service. There could
Hi Axel,
On 06/09/2015 07:54 PM, Axel Beckert wrote:
Christian Seiler wrote:
and I found a fix for the crashes I saw. (I'll have to clean that up
a bit and create a pull request for upstream.)
Feel free to subscribe @xtaran on Github (i.e. me) to that issue/pull
request.
So it turns out
On 05/23/2015 11:19 AM, Adam D. Barratt wrote:
Control: tags -1 + confirmed
On Wed, 2015-05-13 at 20:33 +0200, Christian Seiler wrote:
The attached debdiff for stable fixes the immediate problem for Jessie
(but does not include other changes from unstable).
Please go ahead.
Thanks
Control: forwarded -1
https://groups.google.com/forum/#!topic/open-iscsi/whY9W9kygG0
Control: tags -1 upstream
I don't want to carry around a Debian patch for just a typo, so I've
forwarded this issue upstream.
Christian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Control: tags -1 + fixed-upstream
This bug has been fixed upstream and will be part of the next release:
https://github.com/mikechristie/open-iscsi/commit/3d044973ab444dd7ca9842c57d2cf9200bb58b94
Christian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Control: severity -1 important
I discussed this at DebConf15 with Ritesh (and partially with Guido) and
Ritesh and I came to the following conclusions:
- multipathd will synthesize events for all pre-existing devices on
startup nowadays - so it will pick up all devices that are already
Control: reassign -1 opensm 3.3.19-1
Control: retitle -1 opensm should be started at early-boot
open-iscsi needs to be started at early-boot, otherwise filesystems on
iSCSI will not be available for services that use them. Therefore,
opensm should also be started at early-boot, thus reassigning
Package: dbconfig-common
Version: 1.8.52
Severity: wishlist
Dear Maintainer,
If connection to the database server fails on postinst of a
dbconfig-common package, it currently just prints an error. It would be
great if dbconfig-common could write out a SQL file with all the
commands it wanted to
Control: merge 710148 710261
Control: tags -1 + confirmed
This patch adds ca. 1kLOC of generic python code to the open-iscsi
package for testing (testlib.py). The same code has been added to 3
other packages already just as a carbon-copy. I think it would be far
better to add testlib.py to the
Control: tags -1 + pending
This issue is now fixed in git on alioth, and I've also upstreamed
similar changes, so that a future upstream version will not need a patch
for this to work. The fix for this will be part of the next upload.
Christian
signature.asc
Description: OpenPGP digital
Control: tags -1 + confirmed
The previous way open-iscsi handled upgrades was wrong: it's perfectly
safe to restart iscsid even with active sessions - iscsid is only
responsible for recovery. (Of course, you should remain logged in to
those sessions, and NOT restart the open-iscsi init script,
1 - 100 of 461 matches
Mail list logo
