https://github.com/resiprocate/resiprocate/commit/9a3abc0118e40805dd93a9ab2e6852ea640a0f64
Need to add a macro (upstream) to support backport builds on Debian
systems running stretch / asio 1.10
On 20/07/18 11:38, Thomas Goirand wrote:
> Hi,
>
> I tried applying the patch from upstream, unfortunately, the build still
> fails at the same moment. Maybe we should just disable this -Werror thing?
>
Thanks for testing it
I notice that the fix didn't change every file with this problem,
I've sent an email to query the upstream plans for OpenSSL 1.1
According to policy
/usr/share/doc/debian-policy/policy.txt.gz
"Non-conformance with
guidelines denoted by _should_ (or _recommended_) will generally be
considered a bug, but will not necessarily render a package unsuitable
for distribution."
and further down:
"If your
On 13/08/17 10:17, Petter Reinholdtsen wrote:
> This RC issue has caused virt-viewer to be thrown out of testing. Anyone
> got any idea how to fix it?
>
I did a full reboot of the physical host and the guest VM and after that
I was able to connect successfully from virt-viewer on stretch.
Package: xsane
Version: 0.999-5
Severity: serious
Since upgrading to stetch, the system won't scan with xsane.
scanimage works from the command line.
In gimp, I choose my device and the popup appears:
Title: xsane 0.999
Message: scanning for devices
and then after a few seconds:
Title:
On 23/06/17 13:45, Guido Günther wrote:
> On Fri, Jun 23, 2017 at 01:20:02PM +0200, Daniel Pocock wrote:
>> Package: virt-viewer
>> Version: 5.0-1
>> Severity: serious
>>
>>
>> I recently updated a Debian system, here are the new and old versions of
>
Package: virt-viewer
Version: 5.0-1
Severity: serious
I recently updated a Debian system, here are the new and old versions of
each package from dpkg.log
upgrade virt-viewer:amd64 1.0-1 5.0-1
upgrade virt-manager:all 1:1.0.1-5 1:1.4.0-5
upgrade spice-client-gtk:amd64 0.25-1+b1 0.33-3.3
upgrade
Control: tags -1 -moreinfo
On 15/04/17 17:55, Ivo De Decker wrote:
> Control: tags -1 moreinfo confirmed
>
> Hi Daniel,
>
> On Sat, Apr 15, 2017 at 01:21:05PM +0200, Daniel Pocock wrote:
>> Subject: unblock: resiprocate/1:1.11.0~beta1-2
>
>> This fixes
Package: logrotate
Version: 3.11.0-0.1
Severity: serious
Since updating one of my systems from jessie to stretch in January, the
cron.daily/logrotate cron job has been generating a large email every
day which appears to contain rather verbose output about everything it does.
I notice several
Hi Nish,
I created a branch for 4.1.5 from upstream:
https://anonscm.debian.org/cgit/pkg-monitoring/loganalyzer.git/log/?h=debian/sid-839789
I notice upstream now uses jquery and jquery-ui, some tweaks may be
needed to make sure nothing non-free has crept in to the tarball and
symlink to the
On 24/02/17 19:01, Nish Aravamudan wrote:
> On 24.02.2017 [18:37:41 +0100], Daniel Pocock wrote:
>>
>> Hi Nishanth,
>>
>> Thanks for the patch, is the fix for this bug[1] submitted upstream
>> and/or already fixed in another way in newer upstream releases?
>
Hi Nishanth,
Thanks for the patch, is the fix for this bug[1] submitted upstream
and/or already fixed in another way in newer upstream releases?
If so, maybe we should update the version of loganalyzer in Debian/Ubuntu
Regards,
Daniel
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839789
I use VirtualBox on stable (currently jessie) as part of my strategy for
testing anything that will run in future Debian releases (e.g. stretch).
It has been extremely useful for this purpose in the past.
How many other developers are working this way, either with VirtualBox
or one of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/01/17 17:34, Francesco Poli wrote:
> On Sun, 15 Jan 2017 10:28:40 +0100 Daniel Pocock wrote:
>
>>
>>
>> On 10/01/17 23:49, Christian Hofstaedtler wrote:
> [...]
>>> here are some test packages with a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/01/17 23:39, Francesco Poli wrote:
> On Fri, 6 Jan 2017 11:40:20 +0100 Francesco Poli wrote:
>
>> On Fri, 6 Jan 2017 11:05:50 +0100 Daniel Pocock wrote:
> [...]
>>> My UPS uses SNMP signalling, I wonder if that ma
On 10/01/17 23:49, Christian Hofstaedtler wrote:
> Hi,
>
> * Daniel Pocock <dan...@pocock.pro> [170106 11:06]:
>>> Is anyone able to reproduce the issue on current Debian testing?
>>>
>>
>> How long does it take for your apcupsd daemon to shutdown
package: nfs-kernel-server
version: 1:1.3.4-2
severity: serious
The blkmapd process looks for /run/rpc_pipefs/nfs/blocklayout
It fails to find it and the system boot doesn't complete, it asks for an
emergency login on the text console.
I don't see anything under /run/rpc_pipefs/nfs
Other NFS
On 06/01/17 11:03, Francesco Poli wrote:
> On Tue, 3 Jan 2017 22:33:53 +0100 Francesco Poli wrote:
>
>> On Mon, 26 Dec 2016 18:15:20 +0100 Daniel Pocock wrote:
>>
>> [...]
>>> apcupsd[10324]: A copy of the daemon is still running. If you
>>> just sto
Package: apcupsd
Version: 3.14.12-1.1
Severity: serious
apcupsd is correctly configured and running on my machine.
I decided to restart it by typing:
$ sudo systemctl restart apcupsd
and the command didn't report any errors.
Looking at the output of the 'ps' command, I couldn't find apcupsd
On 19/12/16 23:05, Kurt Roeckx wrote:
>
> You should use SSL_COMP_free_compression_methods() so that we can
> put the internal pointer to NULL.
>
Thanks for suggesting that, I notice that method is only available with
OpenSSL 1.0.2 and I'm also trying to build backports for jessie (OpenSSL
On 19/12/16 21:26, Sebastian Andrzej Siewior wrote:
> On 2016-12-19 09:40:38 [+0100], Daniel Pocock wrote:
>> Could this be a known issue on ppc64el or with libssl?
>
> Nothing comes to mind. But it explodes the same way (but without the
> fancy backtrace) on hur
Package: src:resiprocate
Version: 1:1.11.0~alpha8-3
Severity: serious
build fails in a unit test on ppc64el, double free or corruption, stack
suggests libssl
Full build log:
https://buildd.debian.org/status/fetch.php?pkg=resiprocate=ppc64el=1%3A1.11.0~alpha8-3=1482054136
Relevant section
Package: nfs-kernel-server
Version: 1:1.2.8-9.2
Severity: serious
Fixed: 1:1.3.4-1
The kernel looks[1] for nfsdcltrack in /sbin
The package released in jessie installs it to /usr/sbin
Fixed in the 1.3.4-1 upload.
This affects jessie users, a stable update may be necessary
1.
On 14/12/16 19:25, Andrey Rahmatullin wrote:
> On Wed, Dec 14, 2016 at 07:03:18PM +0100, Daniel Pocock wrote:
>> Can you clarify, did you manually mask the proc-fs-nfsd.mount
>> service and you expect dpkg to ignore that error and leave the
>> service as it is?
> I do
Is this still a bug for you with 1.3.4 in sid?
You can clone it from git and build the package on jessie to test it on
a jessie system.
Thanks for the bug report
Can you clarify, did you manually mask the proc-fs-nfsd.mount service
and you expect dpkg to ignore that error and leave the service as it is?
Or you believe the package is doing something really bad and
proc-fs-nfsd.mount should not be in that state at all?
Package: evolution
Version: 3.12.9~git20141130.241663-1+b1
Severity: serious
Editing a contact in Evolution, there is a section on the first tab,
"Instant Messaging" where it allows people to select options like "MSN"
or "Skype".
There is no apparent way to specify other contact types here.
Hi,
Can we verify at runtime whether it is a thread-safe client library?
People build the reSIProcate code on a wide range of systems, including
older Debian, Ubuntu and even RHEL boxes and I'm not sure if they may
encounter a non-thread-safe version of the MySQL client library by mistake.
On 03/11/16 10:11, Andreas Beckmann wrote:
> Package: libqpid-proton8-dev
> Version: 0.14.0-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package failed to install
> because it tries to overwrite other
I tried to make a build 0.14.0-3 to fix #843024
I encountered the same FTBFS caused by incompatibility with OpenSSL
1.1.0b headers in sid.
/tmp/buildd/qpid-proton-0.14.0/proton-c/src/ssl/openssl.c: In function
'get_dh2048':
/tmp/buildd/qpid-proton-0.14.0/proton-c/src/ssl/openssl.c:406:5:
On 19/07/16 12:54, Victor Seva wrote:
> Hi Daniel,
>
> are you aware of #825121 [0]? Do you have any plans to work on that?
>
The radcli package supercedes the radiusclient and freeradius-client
packages
If one of those other packages was on the box before, radcli
deliberately takes a copy
On 06/05/16 20:53, Jean-Michel Nirgal Vourgère wrote:
> Control: tags 812462 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for ganglia (versioned as 3.6.0-6.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
>
No need to delay it, you are
Package: kamailio-radius-modules
Severity: serious
Version: 4.2.0-2
kamailio-radius-modules depends on libfreeradius-client
libfreeradius-client has been deprecated in favor of radcli[1]
Please update the build dependency to use radcli. The API is fully
compatible, radcli is a fork of the
Package: monitoring-plugins-standard
Severity: serious
Version: 2.1.2-2
monitoring-plugins-standard depends on libfreeradius-client
libfreeradius-client has been deprecated in favor of radcli[1]
Please update the build dependency to use radcli. The API is fully
compatible, radcli is a fork of
Package: asterisk-modules
Severity: serious
Version: 1:11.13.1~dfsg-2+b1
asterisk-modules depends on libfreeradius-client
libfreeradius-client has been deprecated in favor of radcli[1]
Please update the build dependency to use radcli. The API is fully
compatible, radcli is a fork of the
Thanks for reporting this bug
I am orphaning this package, please see
https://qa.debian.org/popcon.php?package=turnserver
if you wish to adopt the package and release it with the patch.
On 28/09/15 18:18, Iñaki Baz Castillo wrote:
> 2015-09-24 15:14 GMT+02:00 Daniel Pocock <dan...@pocock.pro>:
>> Can anybody from the JsSIP team comment on this? How do you feel about
>> having node-nan 2.x in the dependency hierarchy? Will you continue
>> using
This is failing because node-nan 2.x is now in unstable
I've filed a bug upstream requesting support for node-nan 2.x
Maybe both old and new versions of node-nan will be needed in stretch?
https://packages.qa.debian.org/n/node-nan.html
On 24/09/15 14:58, Jérémy Lal wrote:
> 2015-09-24 14:53 GMT+02:00 Jérémy Lal <kapo...@melix.org
> <mailto:kapo...@melix.org>>:
>
> 2015-09-24 14:42 GMT+02:00 Daniel Pocock <dan...@pocock.pro
> <mailto:dan...@pocock.pro>>:
>
>
>
>
On 24/09/15 14:53, Jérémy Lal wrote:
> 2015-09-24 14:42 GMT+02:00 Daniel Pocock <dan...@pocock.pro
> <mailto:dan...@pocock.pro>>:
>
>
>
> This is failing because node-nan 2.x is now in unstable
>
> I've filed a bug upstream
On 24/09/15 15:16, Jérémy Lal wrote:
>
>
> 2015-09-24 14:59 GMT+02:00 Daniel Pocock <dan...@pocock.pro
> <mailto:dan...@pocock.pro>>:
>
>
>
> On 24/09/15 14:53, Jérémy Lal wrote:
> > 2015-09-24 14:42 GMT+02:00 Daniel Pocock <d
Given the nature of this package (phone number country, region and
network codes are volatile) we probably need to just update to the
latest upstream version but I haven't had time to get onto that while
doing other releases.
I started looking at updating the packages postbooks, openrpt and csvimp
to the latest upstream versions. My intention, as with previous
updates, is to put the latest upstream releases into unstable, wait for
them to propagate to testing and then upload them to backports.
As part of the GCC5
On 18/08/15 09:24, Andrew Shadura wrote:
Please do.
Thanks Julien. It would be good if you could commit and tag in our Git
repository too but if not, we can do that with your patch.
Upstream are now willing to keep some Debian artifacts in their
repositories, I'm currently looking at how
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/08/15 21:55, Antti Järvinen wrote:
peter green writes:
Antti, can you confirm who wrote this patch? was it you?
Correct, my patch. I'll Cc: Daniel Pocock if he has simple testing
instructions.
Is the patch intended
On 07/08/15 09:20, Carsten Schoenert wrote:
Hello Daniel,
On Thu, Aug 06, 2015 at 06:24:22PM +0200, Daniel Pocock wrote:
I did some more tests
I moved the following to a backup location:
~/.icedove
~/.thunderbird
~/.cache/icedove
so it should create a completely new profile
Ok, I finally found the root cause of this problem
On the NFS server, dmesg output included the line:
lockd: cannot monitor host1
repeated many times. It would appear several times each time I tried to
start icedove.
Looking in other logs, I found that /var had filled up on the NFS server
Package: icedove
Version: 31.8.0-1~deb8u1
Severity: serious
icedove is just not working any more
The host was shutdown yesterday (5 August) and when started up again, I
could only see messages up to 27 July
Normally at startup it asks for the master password, this prompt is not
appearing
I
I did some more tests
I moved the following to a backup location:
~/.icedove
~/.thunderbird
~/.cache/icedove
so it should create a completely new profile.
Then I run it in safe mode to avoid any plugins:
$ icedove -safe-mode
The main window appears but it is unresponsive to any
Package: gdm3
Version: 3.14.1-7
Severity: serious
This occurred on a jessie system using the default GNOME 3 desktop.
My laptop screen had been locked for a while. I typed the password and
nothing happened. After a few seconds, the screen went blank again.
Looking at journalctl I observed:
# lsof -n | wc -l
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Output information may be incomplete.
92842
# lsof -n | tr -s ' ' | cut -f2 -d' ' | uniq -c | sort -n | tail -10
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
Package: nfs-kernel-server
Version: 1:1.2.8-9
Severity: serious
Ever since upgrading the server from wheezy to jessie, I've been having
crashes every couple of weeks. Running wheezy, it had been stable and
running continuously for over a year. NFS configuration was not changed
when upgrading.
I've observed the same crash again but this time it was not preceded by
any message from gnome-session/gnome-shell/mutter in the log
Looking through the logs, I found the same message has been occurring
intermittently at different times, even when the machine didn't crash,
therefore, I would
Regardless of whether the gnome-shell/mutter log line means anything, I
don't think the NVIDIA driver should be failing with a seg fault, so I
also filed a copy of the stack on the NVIDIA forum:
https://devtalk.nvidia.com/default/topic/856765/linux/crash-report/
--
To UNSUBSCRIBE, email to
Package: gnome-session
Version: 3.14.0-2
Severity: serious
My whole desktop crashed and went back to the login screen. It happened
when I right clicked a link in a web site I was viewing with iceweasel.
This type of thing wasn't happening with wheezy / GNOME classic.
The log shows a message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
That looks like a crash in the Xorg server originating in the
(proprietary) nvidia driver.
Any reason you filed this against gnome-session?
The first line in the log comes from gnome-session and it is one
second before the Xorg crash:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/07/15 22:09, Michael Biebl wrote:
Am 15.07.2015 um 21:17 schrieb Daniel Pocock:
That looks like a crash in the Xorg server originating in the
(proprietary) nvidia driver.
Any reason you filed this against gnome-session
Package: ssl-cert
Version: 1.0.35
Severity: serious
I've marked this bug serious because it could lead to security problems
if people mix root certs and other certs in the same directory
This package provides the script /usr/sbin/make-ssl-cert
It creates certificates and puts the public key /
Package: ganglia-modules-linux
Version: 1.3.6-1
Severity: serious
During dist-upgrade, ganglia-modules-linux postinst configure is called
before the ganglia-monitor postinst configure
During ganglia-modules-linux postinst configure it calls the init script
restart method, starting the daemon
Package: libstrongswan-standard-plugins
Version: 5.2.1-6
Severity: serious
I've marked this bug serious because it can lead to a loss of
connectivity for remote users.
The system was running fine with strongSwan on wheezy using ECDSA
The system was upgraded to jessie using apt-get dist-upgrade
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/06/15 15:43, Yves-Alexis Perez wrote:
On Fri, Jun 05, 2015 at 12:31:46PM +0200, Daniel Pocock wrote:
Package: libstrongswan-standard-plugins Version: 5.2.1-6
Severity: serious
I've marked this bug serious because it can lead to a loss
On 04/06/15 18:43, Lisandro Damián Nicanor Pérez Meyer wrote:
Source: postbooks
Version: 4.7.0-2
Severity: serious
Justification: FTBFS due to missing dependency
Hi! Your package *build* depends on libqt4-webkit, which is no longer
available in the archive, and so it FTBFS.
Sadly I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/06/15 19:29, Lisandro Damián Nicanor Pérez Meyer wrote:
On Thursday 04 June 2015 19:18:57 Daniel Pocock wrote:
On 04/06/15 18:43, Lisandro Damián Nicanor Pérez Meyer wrote:
Source: postbooks Version: 4.7.0-2 Severity: serious
Package: gnome-session-bin
Version: 3.14.0-2
Severity: serious
I clicked the desktop chooser at the bottom right hand corner to try and
go to another desktop
The screen went light grey with a message in the middle telling me
Something went wrong and with a log out button
Instead of clicking
Package: gdm3
Version: 3.14.1-7
Severity: serious
After dist-upgrade to jessie, I encountered the problem described here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724731
Basically, the greeter screen appears but without any login field or
list of users.
In my case, Lucas's solution
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 26/04/15 10:45, Bastian Blank wrote:
Hi Daniel
On Sun, Apr 26, 2015 at 10:35:01AM +0200, Daniel Pocock wrote:
This should probably be released in an update to wheezy.
Well, if you can pursuade the release team. We have grub2 for Xen
Package: xen-utils-4.1
Version: 4.1.4-3+deb7u4
Severity: serious
Tags: patch
dom0 running wheezy
domU upgraded from wheezy to jessie. The domU doesn't boot any more,
errors:
Error code: Using class 'grub.GrubConf.Grub2ConfigFile' to parse
/grub/grub.cfg
Error parameters: Traceback (most recent
On 23/03/15 07:57, Debian Bug Tracking System wrote:
Processing commands for cont...@bugs.debian.org:
severity 718483 grave
Bug #718483 [simpleid] simpleid: transition towards Apache 2.4
Severity set to 'grave' from 'important'
thanks
Stopping processing here.
Please contact me if you
Package: systemd
Version: 215-8
Severity: serious
I have a server with many LVM logical volumes on top of the same RAID1
md device on two spindles.
At boot, fsck appeared to be starting on many of the LVs simultaneously.
There was a horrendous sound of disk head movement from the server.
This
Package: repro
Version: 1.9.7-1
Severity: serious
After discussion on debian-security, two specific issues have been
identified[1] that have an impact on security support and
interoperability with TLS:
a) avoiding the TLSv1_method in the OpenSSL API and just using SSLv23_method
b) not trying to
Package: libresiprocate-1.9
Version: 1.9.7-1
Severity: serious
Tags: security
Thanks to POODLE[1], CVE-2014-3566, many people want to disable SSL v3.0.
The existing reSIProcate library code offers developers a choice between
TLSv1_method() and SSLv23_method()
Using TLSv1_method() disables the
severity 772528 important
stop
After discussion on debian-security, it appears that SSLv3 is no longer
possible[1] with SSLv23_method so I'm reducing the severity.
1. https://lists.debian.org/debian-security/2014/12/msg00021.html
--
To UNSUBSCRIBE, email to
On 29/11/14 22:33, Moritz Muehlenhoff wrote:
Source: asterisk
Severity: grave
Tags: security
Please see
http://downloads.digium.com/pub/security/AST-2014-018.html
http://downloads.digium.com/pub/security/AST-2014-017.html
http://downloads.digium.com/pub/security/AST-2014-014.html
Package: icedove
Version: 24.7.0-1~deb7u1
Severity: serious
Tags: security
I've marked this serious and added the security tag because it is
possible that users confronted by this situation may be tempted to click
the confirm rather than cancel button when trying to get out of this
loop and then
On 11/11/14 15:11, Lucas Nussbaum wrote:
On 11/11/14 at 08:07 -0500, Darryl L. Pierce wrote:
I've fixed the cause for this by updating the dependency from
libsslcommon2 to libssl in 0.7-7. How do I get this update in the build
stream for Jessie?
Hi Darryl,
Get the fix in unstable, keeping
Control: severity -1 important
As this is being fixed in the next upstream release, I'm downgrading the
severity of the bug.
Users of jessie can workaround this by building the package from the Git
VCS and using
git clean -fd git checkout .
if they need to clean the source tree.
Package: libbind-dev
Version: 1:9.9.5.dfsg-5
Severity: serious
I marked this serious because it leads to FTBFS and other issues for the
dependent package dlz-ldap-enum
This issue appears to be fixed in upstream releases 9.9.6 and 9.10.1
In v9.9.5 in Debian, the file dlz_dlopen.h is not listed
Package: dlz-ldap-enum
Version: 1.0.2-2
Severity: serious
jessie has bind9 9.9.5
From 9.9.x onwards, there are extra arguments to the dlz_lookup method
and the ns_g_mctx variable is not accessible from a dynamically linked
module.
Upstream dlz-ldap-enum 1.0.3 contains fixes for this.
--
To
Tags: patch
Here is the patch against the debian/rules file
--- ../bind9-9.9.5.dfsg-orig/debian/rules 2014-11-11 13:37:54.0 +0100
+++ debian/rules 2014-11-11 19:01:13.867151938 +0100
@@ -127,6 +127,7 @@
dh_installdirs
$(MAKE) -C export install DESTDIR=`pwd`/debian/bind9
$(MAKE)
Aside from dlz_ldap_enum, the other main user of dlz_dlopen is Samba,
they provide dlz_bind9 for AD support[1] since 2010.
Samba users have also had various issues with bind9 9.9.x (some being
Samba itself) and will be helped greatly if the header is provided
Sample user issue:
Hi Andy, Timo,
This is a release critical bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749698
Do you know if it is completely fixed upstream?
Is this version of libmusicbrainz5 suitable for the jessie release or
are you aware of any other potential RC bugs that should also be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 11/11/14 21:00, Sebastian Ramacher wrote:
Hi
On 2014-11-11 20:25:47, Daniel Pocock wrote:
Hi Andy, Timo,
This is a release critical bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749698
Do you know if it is completely
Package: pynag
Severity: serious
Version: 0.8.9
PyNag is writing incorrect time stamps in the check result files for Nagios
This means Nagios silently ignores the check results submitted by
scripts that rely on PyNag
It is a known problem for users of syslog-nagios-bridge, which now
places a
Package: drupal7-mod-fontawesome
Version: 1.0-1
Severity: serious
Only the css directory is symlinked into Drupal
The other directories also need to be symlinked into Drupal
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: libjs-jscommunicator
Version: 2.0.0-1
Severity: serious
The version of drupal7 in Debian contains jQuery 1.4.4
JSCommunicator is using the prop method in jQuery, it only works with
jQuery 1.6 or later
To avoid breaking the DruCall method, we need to use the attr method
instead.
Package: drupal7-mod-drucall
Version: 2.1-1
Severity: serious
The new version of JSCommunicator requires some jQuery UI functionality
Drupal7 provides jQuery UI in the page but doesn't expose the API
automatically. Must use drupal_add_library to get it.
Fixed upstream in 2.2.
--
To
Package: drupal7-mod-jqueryi18nproperties
Version: 1.0.0-1
Severity: serious
Upstream bug:
https://www.drupal.org/node/2371299
There is a mismatch in a PHP function name. This makes the function
impossible to call.
Upstream v1.1 fixes it.
--
To UNSUBSCRIBE, email to
Package: drupal7-mod-jscommunicator
Version: 1.0.1-2
Severity: serious
The .info file needs to include all dependencies for Drupal to ensure
they are enabled correctly at runtime.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Package: drupal7-mod-drucall
Version: 2.0.1-1
Severity: serious
A newer JSCommunicator version was uploaded but the DruCall module could
not be uploaded earlier while waiting for the FTP masters to approve new
Drupal dependency wrapper packages drupal7-mod-jqueryi18nproperties and
Package: libjs-jscommunicator
Version: 2.0.0-1
Severity: serious
The font-awesome package has a ~ symbol in the dfsg version.
Therefore, depending on the constraint (= 4.2.0) doesn't match the
version 4.2.0~dfsg-1
Relax the dependency to depend on (= 4.1.0~dfsg)
--
To UNSUBSCRIBE, email to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/11/14 21:22, Jonas Smedegaard wrote:
Quoting Daniel Pocock (2014-11-06 20:43:48)
The font-awesome package has a ~ symbol in the dfsg version.
Therefore, depending on the constraint (= 4.2.0) doesn't match
the version 4.2.0~dfsg-1
Hi Clint, Palli,
Can you please let me know about the pynag 0.9.1 release? I notice you
still haven't uploaded it to Debian and this makes syslog-nagios-bridge
unusable, it is an RC bug.
Regards,
Daniel
On 29/09/14 12:59, Daniel Pocock wrote:
On 29/09/14 21:22, Aurelien Jarno wrote
.:
DATA
550 5.1.1 pa...@zimbra.okhysing.is: Recipient address rejected:
zimbra.okhysing.is
550 5.1.1 pa...@ok.is... User unknown
554 5.5.1 Error: no valid recipients
On 03/11/14 14:35, Daniel Pocock wrote:
Hi Clint, Palli,
Can you please let me know about the pynag 0.9.1 release? I
Package: libbind-dev
Severity: serious
Version: 9.9.5.dfsg-4.3
Users are complaining that dlz-ldap-enum is not working again
http://list.resiprocate.org/archive/repro-users/msg00780.html
I had a quick look and I notice that dlz_dlopen.h is still not installed
by the libbind-dev package.
--
On 25/10/14 01:35, Richard Saunders wrote:
Thanks for the suggestion; it built the binary version but
unfortunately it did not solve the 'undefined symbols' problem. The
.deb file was installed using this command:
dpkg -i ~/ws/dlz-ldap-enum/dlz-ldap-enum_1.0.2-1_amd64.deb
It installed
Package: network-manager
Version: 0.9.4.0-10
Severity: serious
I've rated this serious because it makes the network unusable when it
happens and it requires a user with root privileges to rectify it.
NetworkManager successfully connects to a WLAN
Some time after that, I start an OpenSWAN VPN,
On 11/10/14 16:56, Michael Tautschnig wrote:
Package: ganglia
Version: 3.6.0-5
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using
cowbuilder
and pbuilder) the build failed with the following error.
[...]
libtool: link:
|
| * Update pynag dependency to 0.9.1 or greater, fixing file_time bug.
|
| -- Daniel Pocock dan...@pocock.pro Sun, 03 Aug 2014 18:34:51 +0200
This makes syslog-nagios-bridge uninstallable as this version is not
available in debian (not even in experimental).
I pinged the maintainers a couple
On 14/09/14 23:12, Florian Schlichting wrote:
tags 740827 + moreinfo
thanks
Hi Daniel,
The actual errors that occur in the database (and error.log of Apache)
are below, although I would expect that for any error situation at all
DAViCal should not be returning 204, I will open a second
1 - 100 of 234 matches
Mail list logo
