The -z option for inkscape used to allow running inkscape in a headless
mode, but it seems to have been removed. I'm not sure what the equivalent
is now to be able to render SVG to raster formats using inkscape..
Jeremy
Thanks for the patch I will prepare an upload.
Cheers,
Jeremy
TLS guarantees you have established a secure connection to the host name
you requested, nothing else. If a host name resolves to cloudflare's
servers, that's the domain owner's decision. Almost every production
deployment involves reverse proxies at one point or another (terminating
TLS in the
I am having the same problem, and the symptoms match pretty well with this:
https://bugzilla.redhat.com/show_bug.cgi?id=1361157
On 26 Jul 2015 6:32 pm, MERLIN Philippe phil-deb1.mer...@laposte.net wrote:
actually it's impossible to install kde-full
apt-get -s install kde-full kde-standard
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Both packageName and appletId are optimised out in the crash trace, any
idea what plasmoid is causing the crash?
Cheers,
Jeremy
Hi Diederik,
What version of systemsettings are you running?
Cheers,
Jeremy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Installing kded5 reduces the number of error when launching
systemsetting5. I do however end up with totally frozen / unusable UI,
but that is possibly an entirely different issue.
Cheers,
Jeremy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
Recently the pypdf2 source package, was uploaded to unstable, and
forcibly took over the python-pypdf binary package. The problem is that
pypdf2 does not provide a pyPdf module, but PyPDF2 which broke all
the reverse dependencies. I would suggest:
- pypdf2 be changed to provide a python-pypdf2
tags 762083 +patch
thanks
Simply changing the import from pyPdf to PyPDF2 works. I am attaching a patch
which does
just that.
Cheers,
Jeremy
Description: Use PyPDF2 instead of pyPdf
--- a/pdfshuffler/pdfshuffler.py 2012-04-28 16:15:17.0 +0200
+++ b/pdfshuffler/pdfshuffler.py 2014-09-26
I have uploaded a new version of asterisk, which now Provides
asterisk-$$AST_BUILDOPT_SUM, so bug #689109 should now be fixable.
Cheers,
Jeremy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
It seems just linking against libfreeradius-client2 is not sufficient, we also
need to
change the default RADIUS configuration path in the asterisk code. If
libfreeradius-client2 tries to load the old configuration file
(/etc/radiusclient-ng/radiusclient.conf) it bombs with a segfault:
#0
tag 731971 + pending
stop
I have set the Breaks/Replaces version to 1:11.6.0~dfsg-1 in git, thanks for
reporting this.
Jeremy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
tags 721622 + pending
stop
Daniel, I have commited a modified version of your patch which allows building
against
FreeRADIUS-client or the older radiusclient-ng2 library. Hopefully this should
be
acceptable upstream.
Jeremy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
I tried applying the suggested patch, and while the build succeeded, the
resulting
asterisk-modules seem to be built without RADIUS support. I will take a closer
look when I
have a moment.
Jeremy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of
severity 685753 important
thanks
This bug was marked as grave, although it does not render the whole of
ocfs2-tools
unusable, just ocfs2-tools-pacemaker (for I do not have a test setup).
Jeremy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of
On a side note, upstream should probably stop using the deprecated PIL imports,
as I
suppose the python-imaging compatibility package won't be around forever.
For instance the bug with PngImagePlugin can be fixed with the attached
one-liner.
Jeremy
--- a/src/Texture.py 2013-11-10
On 10/02/2013 10:23 PM, Faidon Liambotis wrote:
Package: asterisk
Version: 1:11.5.1~dfsg-2
Severity: serious
I was surprised and initially happy to see Asterisk 11 uploaded into
sid. My happiness quickly diminished when I saw that the upload contains
the embedded pjproject as-is, despite
On 02/23/2013 02:33 PM, Adam D. Barratt wrote:
On Sun, 2013-02-17 at 13:59 +, Jonathan Wiltshire wrote:
Once 1.2-1+deb7u1 reaches wheezy (next 24 hours) we will be able to use
1.2-1+deb6u1 for any hypothetical DSA to slot in between squeeze and
wheezy.
Well, there's a 1.2.1+deb6u1 in
Hi Salvatore,
I have just uploaded the requested version to testing-proposed-updates and will
get in touch with the release team to allow it into wheezy.
For squeeze, the package will be exactly the same (squeeze / wheezy both have
pyrad 1.2-1), but what should the version number be?
Cheers,
Dear release team,
Yesterday the following security vulnerability in the pyrad package was
brought to my attention by Salvatore Bonaccorso:
https://security-tracker.debian.org/tracker/CVE-2013-0294
It is tracked in the following bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700669
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/17/2013 01:19 AM, Jonathan Wiltshire wrote:
It's traditional to seek approval *before* uploading; more so in this case
since adding a
patch system is a no-no. The change itself is fine, please upload with this
only. You will
have to bump
Le Sep 10, 2012 à 9:01 PM, Adam D. Barratt a écrit :
On Wed, 2012-08-15 at 13:46 +0100, Adam D. Barratt wrote:
On 15.08.2012 10:47, Jeremy Lainé wrote:
I have uploaded a new revision of ocfs2-tools to unstable which fixes
bug #682517
(inability to launch the ocfs2console GUI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, was away for a couple of days. Thanks for the diagnostics and the fix:
the patch
indeed had the opposite behaviour to the expected one!
I will be uploading the fixed package in a couple of minutes.
Jeremy
-BEGIN PGP SIGNATURE-
Dear release team,
I have uploaded a new revision of ocfs2-tools to unstable which fixes bug
#682517
(inability to launch the ocfs2console GUI):
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682517
The fix (thanks Sébastien Villemot) is straight-forward: drop a bad
Debian/Ubuntu specific
qxmpp 0.4.0-1 does build from source against multi-arch Qt 4.8, so I don't
think the bug
should be serious.
It doesn't however install its libs into /usr/lib/THE_ARCH, so I'll keep this
bug open to
track this.
Jeremy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with
No objection on my behalf, its definitely legacy.
On 04/03/2012 20:18 Antonio Terceiro wrote:
Package: mongrel-cluster
Version: 1.0.5-5
Severity: grave
Justification: renders package unusable
Having mongrel-cluster installed, running mongrel_rails in a mostly
empty rails app crashes:
Hi,
I have put together a patch (attached) which fixes all the warnings, except for
one on which I would need some help. The relevant information is here:
http://oss.oracle.com/pipermail/ocfs2-tools-devel/2011-October/004008.html
It's basically a case where custom printf handlers are
tag 633279 upstream
thanks
Was the file system mounted when you attempted the fsck? In any case this looks
like an upstream issue and would probably be better handled by the ocfs2-tools
developers.
Jeremy
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of
reassign 610530 linux-2.6
thanks
The bug report you submitted is a kernel bug, so I am reassigning it to the
linux-2.6 package. Also, expect the severity of your bug to be lowered, I
doubt it will remain critical.
Regards,
Jeremy
--
To UNSUBSCRIBE, email to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reassign 533620 linux-2.6
thanks
The problem described in bug 533620 is a kernel bug, so I am re-assigning it to
the
linux-2.6 package. What version of the kernel were you running when you
experienced the crash?
Jeremy
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I already ha d deep look at the current packaging included in upstream git,
basically the initscripts need to be rewritten as they are full of
redhadisms, but thats'it basically.
As far as I can tell, the packaging in upstream git (and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joel,
As stated in my previous email I am trying to revive the Debian packaging for
ocfs2-tools.
One of the things I noticed while building ocfs2-tools is that the configure
script
complains about these missing dependencies:
checking for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What would you think of applying for some space on alioth so that we can
maintain
ocfs2-tools collaboratively and finally upload a recent version of
ocfs2-tools?
I have moved the packaging to the collab-maint Subversion repository:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Joel!
Still don't know why an upstream debian/ tree is so frowned
upon.
I have no problem with upstream working on debian/ or even on with packaging
being hosted
upstream, I went with alioth for the sake of expediency. If you want to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frederik, Joel,
I have started putting together the packaging for ocfs2-tools here:
https://svn.jerryweb.org/public/packages/ocfs2-tools/
What would you think of applying for some space on alioth so that we can
maintain
ocfs2-tools collaboratively
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
as far as i see there was no security reason to remove this package.
The only other reason i could see is that there would be no possible
upgrade path from 1.2.x to 1.4.x. Maybe someone can explain me?
I think lenny without ocfs2 support at
Bug #447102 is marked as open but the comments seem to imply it should be
closed. What's the status on this bug as it is currently holding up kdesdk's
transition to testing?
Cheers,
Jeremy
signature.asc
Description: This is a digitally signed message part.
severity 409067 important
thanks
Ben,
I am setting the severity of this bug to important, as it does not
make the package unusable for everyone (a number of users are using
KDevelop 3.4.0 without encountering the bug you describe). You can
find more information on bug severities here:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Could you possibly elaborate on the circumstances in which the crash
occurs, for instance:
- - do you initially have a project loaded when you create the new project?
- - do you get a crash in other circumstances, for instance on opening
existing
Hi Bill,
Well spotted. The current use of Debconf by the postrm script serves
these purposes:
- check what web servers were auto-configured at install to deconfigure them
- check whether the user asked for site data to be delete on purge
- retrieve database credentials
Would it be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justification: renders package unusable
This bug does not render the package unusable, the grave severity is
excessive! Please refer to the following page if in doubt as to what
severity to assign to a bug report:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is the final version of the patch to build KDevelop 3.2.2. I will
be NMU'ing KDevelop shortly.
Kind regards,
Jeremy
- --
http://www.jerryweb.org/ : JerryWeb.org
http://sailcut.sourceforge.net/ : Sailcut CAD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dmitry!
Could you elaborate a bit on how you managed to get bug #315170? It
seems to me the problem only occurs if you are modifying a .pro file in
the top directory. I tried the following :
A/ A default QMake project
1. create a new QMake
44 matches
Mail list logo
