-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reopen 318123
thanks
Hi all--
sorry i haven't kept up with this bug. Thanks for all the work that
everyone has put into it. I'm still using libpam-opensc version
0.9.6-3 (which is in testing). i haven't switched over to
libpam-p11-opensc (which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Subject: libpam-p11: it works for me...
Followup-For: Bug #347957
Package: libpam-p11
Version: 0.1.2-2
i just did a bit of testing (moved a workstation to pam-p11 today,
from pam-opensc), and i can't duplicate this error.
Are you sure that your card
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On February 3, [EMAIL PROTECTED] said:
Well, I first received that error as I deinstalled libpam-opensc and
installed libpam-p11 instead. Then I started to get that error. So I
don't think it has to do with wrong PIN input
*IIRC* I
Package: mime-codecs
Version: 7.19-7
Severity: grave
Tags: patch
Justification: renders package unusable
It appears that the buffering recently introduced to base64-decode has
some major flaws in it that render of all base64-encoded files that
are larger than the input buffer size (~36K)
just wanted to chime in and report that this is indeed a problem. An
example of such breakage is bug 341634 [0], filed against evince.
If a user of beast encounters this problem, it looks like it can be
repaired with:
update-mime-database /usr/share/mime
as suggested by Sebastien Bacher
Hi there--
This bug (and its merged fellow) appears to be the only thing keeping
Thunderbird 1.5 out of etch. It has now been tagged pending since 19
March, which is well over a month ago. Can we expect a version with
this simple dependency change to go into sid soon? If there are other
things
Perhaps i'm not following the thread on bug #367610 properly, but it
sounds to me like this isn't actually a subversion bug any more, but
rather an apache bug. Is this correct?
If so, can bug 367610 be closed (or reassigned)? Or does svn 1.4.0
still failing on ia64, even with the libapr fix?
I'm seeing the same problem: upgrading to the security release
4.5.3-6.1sarge1 broke my drupal installation because of this missing
semicolon.
Here's the diff in unified-diff format:
--- /usr/share/drupal/includes/file.inc~2006-07-17 09:43:29.0
-0400
+++
On October 20, [EMAIL PROTECTED] said:
A new upload has been made that i believe solves the problem. Check
under incoming.debian.org
Yep. That does it for me. I'll remember the versioned Conflicts:
approach for next time i see something like this. Thanks, Jesus.
--dkg
--
To
Package: trac
Version: 0.10-3dkg1
Severity: grave
Tags: security
Justification: user security hole
Trac 0.10.1 is now available. It contains a fix for a CSRF
vulnerability:
http://trac.edgewall.org/wiki/TracDownload
It would be great if this new version could make it into debian soon.
if dspam build-depends on:
libmysqlclient15-dev | libmysqlclient14-dev
instead of just
libmysqlclient15-dev
it makes the source package easier to backport to sarge (which many
mailservers are running, i think).
This is just a suggestion for the near future, until etch becomes
stable.
clone 487016 -1
retitle -1 fontforge: segfaults when building ttf-fifthhorseman-dkg-handwriting
reassign -1 fontforge
found -1 0.0.20080429-1
thanks
On Thu 2008-06-19 04:32:59 -0400, Lucas Nussbaum wrote:
During a rebuild of all packages in sid,
[ttf-fifthhorseman-dkg-handwriting] failed to
Hey there--
sorry to be a nag, but i'm curious what's going on with bug #473682.
fakechroot hasn't worked properly in lenny for nearly three months
now. Does anything need doing to help the process along?
Thanks,
--dkg
pgpXes2txY40G.pgp
Description: PGP signature
Hi Piotr--
On Wed 2008-07-02 10:11:40 -0400, Piotr Roszatycki wrote:
Hi. The new version is almost ready. I didn't have enough time for
testing :(
I know the feeling :P
If you want to help, could you download the newest SVN snapshot from
svn://svn.debian.org/fakechroot/ and try if it work
Package: openssl-blacklist
Version: 0.3
Severity: serious
Justification: Policy 9.1.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please move openssl-vulnkey from /usr/sbin to /usr/bin.
The FHS [0] says:
usr/sbin : Non-essential standard system binaries
Purpose : This directory contains
severity 42158 grave
retitle 42158 pax: hard linked files from cpio archives restored with zero
size (can cause data loss)
thanks
Hi there--
Feels weird touching on an 8-year-old bug, but i've stumbled into a
simple use case for #42158 which i found while reviewing #466771. I'm
upgrading the
Hey good people--
I got bit by this bug, and fixed it with:
aptitude install db4.6-util db4.5-util
TMPDB=$(mktemp -d)/listchanges.db
db4.6_dump /var/lib/apt/listchanges.db | db4.5_load $TMPDB
ln /var/lib/apt/listchanges.db /var/lib/apt/listchanges.db.old
mv $TMPDB
i tried to upgrade my instance of trac today from 0.10-1 to 0.10-2,
and apt wants to remove libapache2-mod-python (i have version 3.2.10-1
installed, which is the etch version).
i'm not sure i understand why the removal is being requested, but if i
were to agree with it, it would make trac
tags 556411 +moreinfo +unreproducible
thanks
Hi Felipe--
On 11/15/2009 04:19 PM, Felipe Sateler wrote:
Trying to load the firegpg extension fails with the following popup
message:
Error : FireGPG cannot access to the IPC library. If you're using
Firefox 2, you have to upgrade to the
On 11/16/2009 03:00 PM, Felipe Sateler wrote:
Bad news... I can't reproduce it anymore either. After a reboot I seem
to have a working firegpg
:/
(mostly... I can configure it but not
integrate with gmail yet).
This may be due to a newer version of firegpg (0.7.10) being available.
I just
On 06/03/2010 06:16 PM, Wouter Verhelst wrote:
On Thu, Jun 03, 2010 at 10:30:22AM -0400, Daniel Kahn Gillmor wrote:
Unfortunately, the latest version of xdotool (2.20100602.2915, which has
a substantially overhauled test suite geared to address these concerns)
*also* FTBFS on the buildd
On 06/15/2010 10:30 AM, Wouter Verhelst wrote:
On Tue, Jun 15, 2010 at 08:16:51AM -0400, Daniel Kahn Gillmor wrote:
Wouter, you seem to be offering assistance in getting access to a build
directory (meaning to a live buildd itself? or something else?) -- can
i take you up on that? I'm
hi Marc--
xdotool upstream has changed the test suites as of version 20091231.03
so that they don't hit the particular race condition i think your buildd
ran into on debian bug #561217.
but the latest sparc build attempt appears to fail because of some
dependency trouble:
Hi Florian--
What's the status on copyright clearance for the boilerplate included in
xml2rfc? It would be useful to me to have the latest version available
through the repositories (even if it means moving it to non-free, though
i hope that wouldn't be necessary).
I don't know if yet another
On 12/02/2009 02:00 PM, Florian Weimer wrote:
I misread the document. non-free is definitely a possibility.
If you think non-free is a reasonable choice for now, could you package
up 1.34 and put it there while the request for DFSG-free licensing winds
its way through whatever red tape it needs
On 12/02/2009 04:41 PM, Florian Weimer wrote:
I don't want to maintain packages in non-free. But apart from that,
I think it's fine.
I don't really either, but i think i'm willing to compromise on this
one, because i'd like to collaborate with other debian users with these
tools, and they seem
On 12/02/2009 04:41 PM, Florian Weimer wrote:
Some of the example RFCs are non-free under Debian's policy. Some
parts of contrib were not DFSG-compliant, either, and if there were
parts that were free software, I simply missed them.
contrib/alex.rousskov/xml2rfcpp.pl is a 4K perl script
On 12/10/2009 04:38 PM, Cyril Brulebois wrote:
Package: xdotool
Version: 20090815-2
Severity: serious
Justification: FTBFS
What about checking your package prior to uploading it?
| ./test.rc: line 14: xterm: command not found
| …
| test_set_window.sh: line 17: xprop: command not found
On 12/14/2009 03:59 PM, Florian Weimer wrote:
I think I already gave my blessing, but I gladly give it again.
ah, ok. i was hoping for a signed message to be sure, as i wrote in
#77, but i guess i'll take this as a confirmation anyway.
I think this is simplifying things too much. Nowadays,
block 561217 by 521075
thanks
On 12/15/2009 03:07 AM, Marc 'HE' Brockschmidt wrote:
Your package failed to build on my buildd:
[...]
| preparing for test_set_window.sh
| Xvfb failed to start
| make[1]: *** [test] Error 1
| make[1]: Leaving directory
On 05/27/2010 02:25 PM, Alexander Sack wrote:
Well, the sponsoring is the blocker for me too ;) ...
Why is the sponsoring a blocker for you, Alexander?
You appear to be a debian developer, according to
https://db.debian.org/search.cgi
What kind of sponsorship do you need?
--dkg
re: debian bug 583551:
e2fsprogs 1.41.12-1 says it Pre-Depends on libblkid1 (= 1.34-1).
However, it appears to actually need libblkid1 (= 2.17-1) to run mkfs.ext3.
--dkg
signature.asc
Description: OpenPGP digital signature
On 06/03/2010 06:15 AM, Lucas Nussbaum wrote:
Source: xdotool
Version: 1:1.20100318.2737-1
Severity: serious
Tags: squeeze sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20100602 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package
Package: tvtime
Severity: normal
tvtime was just missing a Depends: perl-modules
see attached patch to resolve. I might NMU this to a delayed queue to
resolve the RC bug, unless you want to do the update soon.
Thanks for keeping tvtime in debian!
--dkg
-- System Information:
Debian
I'm trying to debug debian bug #567337 --
I've narrowed it down to this use case, which fails on amd64:
/sbin/mkfs.msdos -i deb1 -C boot.img 244736
mdir -i boot.img ::
(the -i deb1 is only to make the image invariant, otherwise a few
bytes change in the generated file).
What i've
tags 567337 + patch
thanks
whoops, i back my earlier remark -- i could succeed only because i had
an ~/.mtoolsrc on the i386 box that contained:
mtools_skip_check=1
silly of me to have forgotten that. Removing that config file showed
the error as usual.
Here's the actual fix (many thanks to
I just uploaded the patched dosfstools (fixing #567337) as a 3-day
delayed NMU, as 3.0.8-1.1
Hopefully that'll help get the d-i builds running again on unstable soon.
Thanks again for dosfstools,
--dkg
signature.asc
Description: OpenPGP digital signature
confdefs.h so that rebuilds do not
+produce variant diffs.
+ * debian/control: add misc:Depends, fix section for libopie-dev (thanks,
+lintian!)
+
+ -- Daniel Kahn Gillmor d...@fifthhorseman.net Sun, 31 Jan 2010 23:48:32 -0500
+
opie (2.32.dfsg.1-0.1) unstable; urgency=high
* Non
Hi folks--
More notes about licensing for opie:
looking at
http://www.inner.net/pub/opie/test/
it appears that an update to 2.4.1-test1 was made only two weeks ago
(the -fixes.diff has a datestamp of 2010-01-16), removing the NOT FOR
REDISTRIBUTION flags in the files, from cmetz according to
for those just getting looped in, this discussion is archived in the
thread starting at:
http://lists.alioth.debian.org/pipermail/pkg-mozext-maintainers/2010-April/000487.html
On 04/13/2010 03:46 AM, Mike Hommey wrote:
On Mon, Apr 12, 2010 at 06:13:38PM -0400, Daniel Kahn Gillmor wrote
package xml2rfc
tags 506652 + pending
tags 555288 + pending
thanks
i've prepared a package for upload into non-free that states (as clearly
as i can) the state of the licensing situation, which is that the IETF
doesn't appear to grant modification of its material for purposes
outside the IETF
Hi Laszlo--
Thanks for the fix and the feedback! I just built 0.28.4-2 from the
sources in unstable for i386, and it solves the problem against both
etch and lenny svn servers. (i'm running kernel 2.6.26, so i don't have
SOCK_CLOEXEC).
Thank you very much for your quick attention to this!
found 545432 1.97~beta3-1
thanks
just wanted to note that grub-ieee1275 continues to be a problem. You
can see this directly from a powerpc machine without actually using grub
as the bootloader, with grub-emu.
just launching grub-emu puts the following text in the terminal:
I was using gpg-agent (from the gnupg-agent package) in conjunction with
gpg version 1, and had a functional workflow with icedove + enigmail. I
had deliberately set use-agent in my gpg.conf, and had ticked the never
ask for any passphrase checkbox in the enigmail configuration. The
agent itself
i moved to enigmail 0.95.7-1 to test another bug (#508766), and the
regression i experienced from the fix for #506631 went away. I don't
know if this is because the fix that broke things for me is not
included in 0.95.7-1, or if there was another change which resolved things.
Other people
On 12/15/2008 12:09 PM, Alexander Sack wrote:
notfound 506631 0.95.7-1
thanks
I'm not sure that this is an accurate summary of my earlier message. To
clarify, i never experienced the problem originally reported as #506631.
gpg-agent and engimail were working fine for me in lenny already.
Package: monkeysphere
Version: 0.23.1-1
Severity: grave
Monkeysphere 0.23 introduced a significant change to the way that system
data is stored in /var. However, the transition script (which is
triggered on postinst) is known to fail for certain classes of host.
In particular, it seems to fail
On 09/20/2009 07:13 PM, Joey Hess wrote:
Luckily, I see in the bug report that vorbis upstream seems to have
fixed the FTBFS.
I'm hoping to get a new version of libvorbisidec pulled from upstream's
svn r16259 packaged and uploaded in the next day or so. When i get that
sorted, i'll see if that
On 09/21/2009 07:13 AM, Martin Guy wrote:
On 9/21/09, Martin Guy martinw...@gmail.com wrote:
I just tried this, and it's doing a misaligned word access:
Sorry, my mistake. It's pumping misaligned half-word (16-bit)
accesses, which again returns some form of garbage, probably either
the
On 09/20/2009 07:13 PM, Joey Hess wrote:
ARM hardware certianly has floating point hardware, and with EABI
binaries can be built that use it on the otherwise softfloat system.
But different ARM systems have different FPUs, and so it would be very
hard to get coverage for all/most of them.
Hi folks--
It looks like the main thing holding up coreutils 7.1 from propagating
into squeeze is a bad /etc/group file in the chroot on malo.
I tried building coreutils on my own powerpc system and it built
properly and passed all tests that were run. (in particular, it passed
this is just a note that i've mailed Joao roughly about this issue
weekly for the last six weeks (since March 8) and haven't gotten a
response. since firegpg is no longer in debian, i'm planning on filing
an ITP to effectively take over the package (and push it through NEW
again) sometime in the
On 6 Feb 2009, Moritz wrote:
I think we should rather remove it altogether. The above's likely only the tip
of the iceberg.
I agree with this assessment. The version of iceweasel-firegpg that is
currently in debian sid should be removed due to its insecure writing of
data (including both
On 03/08/2009 09:11 PM, Daniel Kahn Gillmor wrote:
If we want to continue to maintain firegpg in lenny,
Sorry, i meant to say debian instead of lenny here (since firegpg is
not in lenny). While i think that there are some problems with firegpg
(and in particular problems with the current
tags 507211 + pending
thanks
I've prepared an NMU for #502711 (hi, AM!). It's based on the simple
patch included in the initial bug report. I've placed the prepared NMU
here:
http://lair.fifthhorseman.net/~dkg/src/mrd6/
the .dsc and .changes files are signed, and i've provided an interdiff
tags 441490 + patch
thanks
Hi ivtools people (and hi, AM!)--
Attached please find a patch which gets ivtools to not FTBFS any more.
Interestingly, i couldn't replicate the specific errors reported in
#441490, and the FTBFS that i ran into building ivtools on an up-to-date
sid system looked a
( also Cc'ing Kari Pahula, who signalled an intent to adopt ivtools in
http://bugs.debian.org/164800 )
On 03/24/2009 11:23 AM, Günter Geiger wrote:
Thanks for the patch. You are right about the new upstream version, I should
have done that a long time ago but I just can' t find the time to do
People who may be interested in FireGPG in debian--
I'm not sure how much impetus there is to get firegpg back into the
archive right now. But i'd like to see the tool get wider exposure
where possible, and inclusion in debian could help that.
After talking with Patrick Brunschwig (on
.
+ * Add #includes to avoid FTBFS
+(Closes: #441490)
+
+ -- Daniel Kahn Gillmor d...@fifthhorseman.net Wed, 25 Mar 2009 18:43:00 +
+
ivtools (1.1.3-5.4) unstable; urgency=low
* Non-maintainer upload.
only in patch2:
unchanged:
--- ivtools-1.1.3.orig/src/Unidraw-common/geomobjs.c
+++ ivtools
tags 509381 +pending
thanks
On 06/15/2009 01:45 PM, Guido Günther wrote:
This results in libs being included in the initramfs in nested/ and so
booting fails. Patch attached.
Thanks for the patch, Guido. I'm testing it here on an amd64 machine,
and hope to have a new version in unstable in
It looks like with this fix, debirf now works for amd64 when i build a
sid instance (by setting DEBIRF_SUITE=sid), though there appear to be
other issues building a lenny debirf instance *from* a sid machine, and
logins in the sid debirf don't appear to work how i expect them to.
Those will be
Package: crunchyfrog
Version: 0.4.1-1
Severity: grave
Justification: renders package unusable
crunchyfrog doesn't appear to depend on python-xdg. I get this when i
run 0.4.1-1 on a system without python-xdg:
0 dkg@pip:~$ crunchyfrog jobs/urban/imagesurvey/imagesurvey.db
Traceback (most recent
On 01/29/2011 01:12 PM, Christoph Anton Mitterer wrote:
On Sat, 2011-01-29 at 18:47 +0100, Stefan Fritsch wrote:
This has to be balanced between compatibility and security. Currently
less than 50% of the servers on the internet are patched. So it is
sensible to not deny renegotiation for
i'm able to reproduce debian bug #591118 (monkeysphere FTBFS in test
suite) by using a reasonably fast machine (i used a quadcore amd64
machine with 4000 bogomips per core according to /proc/cpuinfo), which
is not under heavy load. I did:
git clone git://git.monkeysphere.info/monkeysphere
cd
On 10/19/2010 05:26 PM, intrigeri wrote:
Jameson Rollins wrote (19 Oct 2010 13:46:09 GMT) :
but maybe we can find some other ways to reduce entropy consumption
I don't know if this would be considered good-practice, or even
allowed by the Debian policy, but build-depending on haveged would
Package: epiphany-browser
Severity: normal
I'm currently visiting
https://i.broke.the.internet.and.all.i.got.was.this.t-shirt.phreedom.org/ with
epiphany-browser (version 2.30.6-1), and i see a broken
lock in the right-hand side of the address bar, and in the lower-left corner of
the status
block 590827 with 589103
thanks
On 07/29/2010 11:47 AM, Petr Salinger wrote:
Package: xdotool
Version: 1:2.20100602.2915-1
Severity: serious
Tags: patch
User: debian-...@lists.debian.org
Usertags: kfreebsd
Hi,
the current version fails to build on GNU/kFreeBSD.
It looks like lsof
Cc'ing xdotool-users, as upstream might be interested here.
for those just now seeing it, the bug discussed is:
http://bugs.debian.org/590827
xdotool: FTBFS on GNU/kFreeBSD (due to unsatisfied Build-Depends on lsof)
On 07/29/2010 01:54 PM, Petr Salinger wrote:
But it looks like the usage of
tags 591118 + unreproducible
thanks
On 08/02/2010 08:20 AM, Jameson Rollins wrote:
Hey, dkg et. al. It looks like this FTBFS is due to one of the keytrans
tests failing: test working with two primary keys. I don't see this
failure when I run the tests on my own system. Has anyone else been
Package: libreoffice-base
Version: 1:3.3.1-1
Severity: grave
Justification: causes non-serious data loss
The data loss here is non-serious only because this is a trival
database. If i had this happen to a database that i cared about, i
would be unhappy.
To reproduce:
0) run libreoffice
1)
Package: xscreensaver
Version: 5.11-1+b1
Severity: grave
Tags: security
Justification: user security hole
on i386, xscreensaver 5.11-1+b1 (currently in wheezy/testing) is
linked against libssl and libcrypto version 1.0.0.
libp11-1 0.2.7-3 (also currently in wheezy/testing) links against libssl
tags 619065 + moreinfo
thanks
Hi Hilko--
On 03/20/2011 06:03 PM, Hilko Bengen wrote:
a symlink (/dev/etherd/e1.1 - /path/to/file) is created from the script
/usr/share/vblade-persist/vblade-run. This is problematic: /dev/etherd
is the directory in which the Linux kernel-based AoE initiator
On 03/21/2011 02:00 PM, Hilko Bengen wrote:
Please consider the following scenario consisting of two servers, A
and B, with interfaces to a common Ethernet broadcast domain x. B
additionally has an interface in a separate broadcast domain y that is
shared with other machines. A provides a
On 03/21/2011 07:12 PM, Hilko Bengen wrote:
(1) A shelf/slot address should uniquely identify a target in a
broadcast domain.
(2) A shelf/slot address should uniquely identify a target reachable
from a host via any network interface that is configured for AoE. (Your
example above violates
tags 619065 - moreinfo
thanks
On 03/22/2011 10:47 AM, Hilko Bengen wrote:
Here is another example that I didn't even think of when I first wrote
the bug report. This is what I have been running successfully for a few
years, using vblade and home-grown wrappers:
On 03/22/2011 11:38 AM, Daniel Kahn Gillmor wrote:
On 03/22/2011 10:47 AM, Hilko Bengen wrote:
A server exports identical but separate AoE targets to a number of
rather dumb clients, each on a separate VLAN. Separation using VLANs
puts each client into its own broadcast domain, so I am able
Jonathan Nieder's patch for runit's debian bug #603827 looks good to me.
I'm willing to NMU it if there are no objections.
--dkg
signature.asc
Description: OpenPGP digital signature
Attached is the patch i used against runit 2.1.1-6 for NMUing #603827
(uploaded just now on 2010-12-26).
Thanks, Jonathan Nieder for the diagnosis and the fix.
Regards,
--dkg
diff --git a/debian/changelog b/debian/changelog
index b0a6f1f..06f185c 100644
--- a/debian/changelog
+++
tags 634598 + help
thanks
On Sun, 14 Aug 2011 10:56:56 +0200, Christoph Egger christ...@debian.org
wrote:
libcrypt-gcrypt-perl still FTBFS due to testsuite errors on hurd-i386
kfreebsd-amd64 mips(el) powerpc and s390. It's also still claiming (no
library found for -lgcrypt): so reopening
On 01/23/2012 06:07 PM, Guido Günther wrote:
I can't seem to reproduct this in a clean amd64 sid chroot. Are you
still seeing this?
Hm, this is still reproducible for me in an up-to-date sid i386 system
that i've been keeping updated for several months now.
But i made a fresh chroot on the
retitle 654849 gtk-vnc FTBFS if /etc/alternatives/valac uses valac-0.12
thanks
On 01/24/2012 05:23 PM, Guido Günther wrote:
I'd assume that this is somehow related to the installed vala packages.
We have valac 0.14 and 0.12 in the archives. Could you check if the non
chroot build picks up
reopen 652888
thanks
I can confirm that even with libnss3-1d version 3.12.11 installed,
iceweasel 9 does not work for https web sites; the browser simply
doesn't load anything or produce any messages on stderr.
upgrading libnss3-1d to 3.13.1.with.ckbi.1.88 lets iceweasel 9 work with
https sites
Package: fontforge
Severity: serious
On 03/03/2012 07:48 AM, Nicholas Bamber wrote:
We have a package libimager-perl where we have had to remove a few
adobe-related test files as being non-DFSG. See
http://cpansearch.perl.org/src/TONYC/Imager-0.88/adobe.txt .
However given a comment in the
block 635879 with 624500
thanks
On 07/29/2011 02:06 PM, Jonas Smedegaard wrote:
If clicking the yes button regarding restart during upgrade of
underlying packages, I am thrown out of my awesome session.
This is how it appears in ps:
/usr/bin/perl -wT
On 06/07/2011 07:38 PM, Christoph Egger wrote:
Package: src:xdotool
Version: 1:2.20110530.1-1
Severity: serious
Tags: sid wheezy
Justification: fails to build from source (but built successfully in the past)
Yep, i'm aware of this. There are several build failures that the
debian buildd
On 06/12/2011 05:36 PM, Dominic Hargreaves wrote:
On Fri, May 13, 2011 at 07:38:41PM +0200, Dominique Dumont wrote:
Le vendredi 13 mai 2011 00:31:52, Dominic Hargreaves a écrit :
This bug is caused by the fact that pperl names its socket files based
on the full path of the perl program being
On 01/18/2012 01:33 PM, Theppitak Karoonboonyanan wrote:
Package: fontforge
Version: 0.0.20110222-6
Severity: grave
Fontforge consistently crashes (segmentation fault) when pressing any
modifier key (Ctrl, Alt or Shift) or arrow key if more than 4 points are
currently selected. This is
Hi fontforge folks--
over on Debian, we've just gotten http://bugs.debian.org/656359, which
appears to contain a reproducible segfault.
Some folks have suggested that it may be due to more recent versions of
dependent libraries, but i haven't been able to track it down in more
detail, i'm
On 01/19/2012 01:08 AM, Christian PERRIER wrote:
Anyone in the pkg-fonts team wanting to take responsibility on getting
in touch with fontforge upstream about this issue?
i've just written to the fontforge-devel list, cc'ing this bug report,
and marked this bug as forwarded to
On 01/19/2012 02:21 AM, Khaled Hosny wrote:
I can't reproduce this with fontforge built from git master running
under Ubuntu 10.04.
hmm, just trying to build from upstream's git master
(265be01a4ce5978fbb2c1a6ecf6402af0ea54115) with a ./configure make
on sid yields me this error:
cvdgloss.c:
On 01/19/2012 06:15 AM, Khaled Hosny wrote:
I use FontForge extensively I never encountered this, and generally it
is less crashy than it used to be. May be it is 64bit specific bug?
nope. as i've said, i'm able to replicate it in i386.
--dkg
signature.asc
Description: OpenPGP
!
So, let's apply it to the debian package.
agreed, it also fixes the bug for me. i don't apparently have access to
scm_pkg-fonts on svn.debian.org; maybe someone else can apply the
attached patch?
thanks,
--dkg
commit fb91b231818fd320a2b662abf7236c0fbd8773bd
Author: Daniel Kahn Gillmor
close 642404 1:2.20110530.1-6
thanks
I've disabled all of the relevant symbol typing tests with this new version.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Control: severity 619065 normal
On 10/23/2012 01:52 PM, Gianluca Ciccarelli wrote:
It seems that this bug is very old, and also that the activity upstream
is low. Do you confirm the bug is still there, or do you think it can be
closed or otherwise be dealt with?
I'm upstream and the debian
On 11/09/2012 07:30 PM, Tobias Hansen wrote:
some bugs are only reproducable with sbuild. Did you try using sbuild
yourself?
No, i have not tried with sbuild myself yet. are you able to reproduce
these bugs with sbuild?
--dkg
signature.asc
Description: OpenPGP digital signature
On 11/14/2012 02:59 PM, Timo Juhani Lindfors wrote:
Hi,
yes I can reproduce the bug with sbuild:
1) Failure:
test_de_symbol_typing(XdotoolTypingTests)
[test_typing.rb:58:in `_test_typing'
test_typing.rb:118:in `test_de_symbol_typing']:
`12345678990-=~
On 06/12/2012 07:15 AM, Helmut Grohne wrote:
severity 674911 serious
thanks
Setting severity to serious, because xml2rfc's prerm overwrites user
configuration (similar to #477751).
On Mon, May 28, 2012 at 05:01:32PM +0200, Helmut Grohne wrote:
Your package manually calls update-catalog.
On 06/21/2012 10:03 AM, Helmut Grohne wrote:
On Fri, Jun 15, 2012 at 06:10:02PM +0200, Helmut Grohne wrote:
Please review my changes. Can I also ask you to upload them?
I updated the .debdiff with some remarks from Jakub Wilk. In the absence
of any further response from you I will seek a
On 07/13/2012 11:34 AM, Hideki Yamane wrote:
We could probably make a new dfsg-free clean upstream tarball that is
still capable of building fontforge binaries by ripping out big chunks
of this file (i haven't tried it yet), but i don't know what that would
do to fontforge's ability to do
On 07/26/2012 01:21 PM, gregor herrmann wrote:
Find a patch attached.
thanks for the nudge, gregor. I've just uploaded this fix as
0.6.0+svn10787-2.
What worries me a bit is the change in the python dependencies:
From the package in the archive:
Depends: python2.7 | python2.6, python (=
1 - 100 of 451 matches
Mail list logo
