Bug#746715: Init system fallout draft resolution
Here is the resolution text that I think we agreed at the last meeting. I formally propose this text: The issue of init system support recently came to the Technical Committee's attention again.[1] For the record, the TC expects maintainers to continue to support the multiple available init systems in Debian. That includes merging reasonable contributions, and not reverting existing support without a compelling reason. [1] See #746715 for background. As discussed I deleted the contextual and motivational paragraphas and replaced them with the vague intro sentence from IRC and put the bug reference in a footnote. Hopefully this will get consensus. I intend to call for a vote no earlier than after the end of the relevant item in tomorrow's meeting. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636783: supermajority bug
Russ Allbery writes (Bug#636783: supermajority bug): Ian Jackson ijack...@chiark.greenend.org.uk writes: The fix to the constitutional supermajority bug has been delayed rather. Sorry about that. I have drafted what I think is an implementation of our conclusions here and in the TC. Opinions welcome. I haven't reviewed the wording in detail, but the general discussion and intent looks right to me. Thank you for drafting this! You're welcome. I'd appreciate it if _someone_ would review the wording in detail, and post to say that they'd done so. (That doesn't have to be a TC member, of course.) It would be embarassing to have to fix this _again_ ... Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751856: libav FTBFS on arm64
Tags 751856 +patch thanks peter green wrote: This should be a better patch: https://git.libav.org/?p=libav.git;a=commitdiff;h=34fb994d9340313b0d247899a4a7a97cc010df92;hp=e780c3daafe0588e035e752c771ebfcd2201746a Can you verify that patch works for you? The build without neon is currently still in progress. The reduced feature build without neon built successfully and was uploaded to debian-ports arm64 unreleased. I'll probablly try your patch later when I come to do a full-feature build. Since the reduced feature build was uploaded build-depends for libav have become installable (partly due to the availability of the reduced feature build, some other issues also had to be dealt with). As expected the autobuild failed with the same error as my first attempt at a reduced feature build. I then applied the patch you linked and was able to successfully perform a build. Debdiff attatched and uploaded to debian-ports arm64 unreleased. Please include the patch in your next upload diff -Nru libav-10.1/debian/changelog libav-10.1/debian/changelog --- libav-10.1/debian/changelog 2014-05-11 16:31:13.0 + +++ libav-10.1/debian/changelog 2014-06-23 11:57:10.0 + @@ -1,3 +1,9 @@ +libav (6:10.1-1+arm641) unreleased; urgency=medium + + * Apply upstream patch to fix build on aarch64 with neon and pic. + + -- Peter Michael Green plugw...@debian.org Mon, 23 Jun 2014 11:56:46 + + libav (6:10.1-1) unstable; urgency=low * New upstream release 10: diff -Nru libav-10.1/debian/patches/fix-aarch64-pic.patch libav-10.1/debian/patches/fix-aarch64-pic.patch --- libav-10.1/debian/patches/fix-aarch64-pic.patch 1970-01-01 00:00:00.0 + +++ libav-10.1/debian/patches/fix-aarch64-pic.patch 2014-06-23 11:56:03.0 + @@ -0,0 +1,33 @@ +From: Martin Storsjö mar...@martin.st +Date: Thu, 29 May 2014 11:37:31 + (+0300) +Subject: aarch64: Use the correct syntax for relocations +X-Git-Url: https://git.libav.org/?p=libav.git;a=commitdiff_plain;h=34fb994d9340313b0d247899a4a7a97cc010df92;hp=e780c3daafe0588e035e752c771ebfcd2201746a + +aarch64: Use the correct syntax for relocations + +This fixes building in PIC mode with gas. The examples in the gas +manual showed using a # here even though gas itself actually didn't +support that syntax (and the gas test suite only tests it without +the extra hash sign). + +CC: libav-sta...@libav.org +Signed-off-by: Martin Storsjö mar...@martin.st +(cherry picked from commit 08cd92144e73195eecc28ed0348e66e255516b82) +Signed-off-by: Martin Storsjö mar...@martin.st +--- + +diff --git a/libavutil/aarch64/asm.S b/libavutil/aarch64/asm.S +index 94e5a84..6608472 100644 +--- a/libavutil/aarch64/asm.S b/libavutil/aarch64/asm.S +@@ -55,8 +55,8 @@ ELF .size \name, . - \name + + .macro movrel rd, val + #if CONFIG_PIC +-adrp\rd, #:pg_hi21:\val +-add \rd, \rd, #:lo12:\val ++adrp\rd, :pg_hi21:\val ++add \rd, \rd, :lo12:\val + #else + ldr \rd, =\val + #endif diff -Nru libav-10.1/debian/patches/series libav-10.1/debian/patches/series --- libav-10.1/debian/patches/series2014-05-11 16:31:13.0 + +++ libav-10.1/debian/patches/series2014-06-23 11:55:02.0 + @@ -1 +1,2 @@ 03-disable-configuration-warnings.patch +fix-aarch64-pic.patch
Bug#736878: python-django: Please provide python3-django
On 25 June 2014 16:27, Raphael Hertzog hert...@debian.org wrote:
Not tested, but you get the idea I guess. And obviously we need strong (=
${binary:Version}) dependency between python*-django and
python-django-common.
# find -type f debian/python3-django/usr/lib/python3/dist-packages/ -not
-name '*.py'
find: paths must precede expression:
debian/python3-django/usr/lib/python3/dist-packages/
Usage: find [-H] [-L] [-P] [-Olevel] [-D
help|tree|search|stat|rates|opt|exec] [path...] [expression]
Am glad I am not the only one who makes this particular mistake. :-)
In the above /usr/share/pyshared/ needs to be replaced with the correct
directory as I don't think we get that directory with the new build
system.
Will see if I can get it to autodetect /usr/lib/python2.7/dist-packages/
or /usr/share/pyshared/ somehow.
As I like being able to build this on wheezy with no changes, as well as
sid :-).
--
Brian May br...@microcomaustralia.com.au
Bug#752735: webkitgtk FTBFS on arm64
Package: webkitgtk Version: Severity: important X-debbugs-cc: iain.l...@canonical.com (note: Ian Lane in cc because he appears to be the effective maintainer of the ubuntu webkitgtk package which does appear to build on arm64 and about which I have some questions) webkitgtk failed to build on arm64, the following was the final error in the build log (there were a load of others before it too) In file included from ../Source/WTF/wtf/FastMalloc.h:28:0, from ../Source/JavaScriptCore/config.h:60, from ../Source/JavaScriptCore/llint/LLIntOffsetsExtractor.cpp:26: ../Source/WTF/wtf/StdLibExtras.h: In instantiation of 'ToType WTF::bitwise_cast(FromType) [with ToType = JSC::JSCell*; FromType = int]': ../Source/JavaScriptCore/interpreter/Register.h:185:47: required from here ../Source/WTF/wtf/StdLibExtras.h:137:5: error: static assertion failed: bitwise_cast size of FromType and ToType must be equal! static_assert(sizeof(FromType) == sizeof(ToType), bitwise_cast size of FromType and ToType must be equal!); ^ ../Source/WTF/wtf/StdLibExtras.h: In instantiation of 'ToType WTF::bitwise_cast(FromType) [with ToType = JSC::Instruction*; FromType = int]': ../Source/JavaScriptCore/interpreter/CallFrame.h:192:81: required from here ../Source/WTF/wtf/StdLibExtras.h:137:5: error: static assertion failed: bitwise_cast size of FromType and ToType must be equal! ../Source/WTF/wtf/StdLibExtras.h: In instantiation of 'ToType WTF::bitwise_cast(FromType) [with ToType = int; FromType = JSC::Instruction*]': ../Source/JavaScriptCore/interpreter/CallFrame.h:197:75: required from here ../Source/WTF/wtf/StdLibExtras.h:137:5: error: static assertion failed: bitwise_cast size of FromType and ToType must be equal! GNUmakefile:77705: recipe for target 'Source/JavaScriptCore/llint/Programs_LLIntOffsetsExtractor-LLIntOffsetsExtractor.o' failed make[1]: *** [Source/JavaScriptCore/llint/Programs_LLIntOffsetsExtractor-LLIntOffsetsExtractor.o] Error 1 Ubuntu had a successful build on arm64 so I went looking through their package to see what changes should be cherry picked (a debdiff between the latest debian version and the latest ubuntu version is attatched), unfortunately one patch still left me questioning whether it's related. The list of changes with comments/questions is below geoclue depedency switched back to 1.0: this seems to be a ubuntuism and not relavent for debian. debian-branch changed, maintainer changed: definate ubuntuisms debian/patches/aarch64.patch, debian/patches/fix-aarch64.patch: from their title and description these are obviously arm64 related. debian/patches/bugzilla_clear_surface.patch: appears to be a generic non-arch related bugfix related to an upstream bug looks to my untrained eye like it may be appropriate for debian too but i'm not a webkit expert. debian/patches/disable-jit-harder.patch: This is the one i'm unsure about, I can't find any comments in the patch itself or in the ubuntu changelog as to what it does or what architectures it's relavent for other than that it's something to do with disabling jit. Theres a subversion revision listed but I haven't figured out what repository it reffers to. debian/patches/gtkdoc-remove-Wcast-align.patch in Debian, debian/patches/no-gtkdoc-warning-fail.patch in ubuntu This seems to be a case of Debian and Ubuntu solving the same problem in slightly different ways. debian/patches/ppc64el.patch: obviously ppc64el related debian/rules: changes to list of no-jit architectures ubuntu added arm64 and ppc64el but I wonder if it would make more sense to have a list of architectures on which to enable jit than a list of architectures on which to disable it. diff -Nru webkitgtk-2.4.3/debian/changelog webkitgtk-2.4.3/debian/changelog --- webkitgtk-2.4.3/debian/changelog2014-06-09 13:35:50.0 +0100 +++ webkitgtk-2.4.3/debian/changelog2014-06-06 09:36:24.0 +0100 @@ -1,15 +1,30 @@ -webkitgtk (2.4.3-2) unstable; urgency=medium +webkitgtk (2.4.3-2~ubuntu2) utopic; urgency=medium + * Don't fail the build on gtk-doc warnings. + + -- Iain Lane iain.l...@canonical.com Fri, 06 Jun 2014 09:36:07 +0100 + +webkitgtk (2.4.3-2~ubuntu1) utopic; urgency=medium + + [ Alberto Garcia ] * debian/rules: + Move -Wl,--as-needed from CFLAGS to LDFLAGS. * debian/control: + Build depend on libegl1-mesa-dev and libgles2-mesa-dev on armel and armhf (Closes: #749700). - * debian/patches/gtkdoc-remove-Wcast-align.patch: -+ Remove -Wcast-align during gtk-doc generation. Fixes FTBFS on hppa - and others (Closes: #750839). - -- Alberto Garcia be...@igalia.com Mon, 09 Jun 2014 15:35:44 +0300 + [ Iain Lane ] + * Merge with unreleased Debian git. Remaining changes: +- Build for ppc64el and arm64 +- bugzilla_clear_surface.patch: Take patch to fix upstream bug#123480 + which was a crash affecting software-center in Ubuntu. +- Don't
Bug#750090: Need more information
Hi, Looking at http://www.gnu.org/software/gettext/manual/html_node/autopoint-Invocation.html it does seem that autopoint could be needed to build shadow, since a AM_GNU_GETTEXT_VERSION does show up in configure.in. The autopoint dependency is probably usually satisfied due to a Recommends in gettext, which in turn shadow does build-dep on. However since it is only a recommends, this won't always be the case. Nevertheless, when I dpkg -r autopoint on a wheezy chroot and build shadow, the package succesfully builds. Thomas, could you please tell us exactly how the build broke for you without autopoint? I.e show us the full build logs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748385: Fixed in June 23 version?
The install bug in the May 12 version of Jessie was gone in the June 23 version. Install of debian-testing-amd64-DVD-1.iso worked on the same machine that failed with the May 12 version. -- cgi...@surfnaked.ca (Charlie Gibbs) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752716: ming: hardcodes /usr/lib/perl5
Control: tags -1 + pending Fixed in git. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749617: Having the same issue after dist-upgrade on jessie
Performed dist-upgrade on Debian jessie system (from jessie to jessie, not changing releases). Same problem, evolution is online, connects to IMAP accounts, reports offline for ews account. Bill West -- Cell: 877-567-7451 Skype: bill.west9 DESTWIN, LLC. 887 Main Street, Suite D Monroe, Connecticut 06468-2800 Toll Free: 877-DESTWIN (877-337-8946) Local: 203-459-0619 FAX: 203-261-5061 sa...@destwin.com http://www.destwin.com DESTWIN is a registered trademark of DESTWIN, LLC. Fuel Dealer Solution is a trademark of DESTWIN, LLC. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740801: zathura: Ligatures, like fi, are not rendered. (fwd)
Hi there, fonts-texgyre maintainers.
I am forwarding this (see below, from bug 740801) as the upstream poppler
maintainers believe that there is a bug in TeX Gyre Termes.
I have not yet verified the source code to see if the ligature is
incorrectly implemented, but temporarily uninstalling fonts-texgyre makes
the problem go away for programs that use poppler (like qpdfview, evince,
atril).
To avoid having the font blacklisted in fontconfig (which would simply kill
the font for all purposes), perhaps a small patch could be implemented?
When contacting me, please, keep me in CC's, as I am not subscribed to the
bug, nor to the mailing list.
Thanks,
Rogério.
- Forwarded message from Florian fb...@gmx.net -
Date: Mon, 02 Jun 2014 17:07:55 +0200
From: Florian fb...@gmx.net
To: Debian Bug Tracking System 740...@bugs.debian.org
Subject: Re: zathura: Ligatures, like fi, are not rendered.
X-Mailer: reportbug 6.5.0
Message-ID: 20140602150755.21588.54814.report...@arne.uni-graz.at
Package: libpoppler-glib8
Version: 0.24.5-4
Followup-For: Bug #740801
This bug report seems to be related:
https://bugs.freedesktop.org/show_bug.cgi?id=73291
There is also a fix (or workaround, in fontconfig) mentioned in
that bug report, and linked to a commit:
http://cgit.freedesktop.org/fontconfig/commit/?id=c6aa4d4bfcbed14f39d070fe7ef90a4b74642ee7
Since this bug affects most of the pdfs I am using for quite some
time now, I would be happy if this patch could be applied.
Thanks for your work, Florian
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libpoppler-glib8 depends on:
ii libc6 2.18-7
ii libcairo2 1.12.16-2
ii libfreetype6 2.5.2-1
ii libglib2.0-0 2.40.0-3
ii libpoppler44 0.24.5-4
ii libstdc++6 4.9.0-5
ii multiarch-support 2.18-7
libpoppler-glib8 recommends no packages.
libpoppler-glib8 suggests no packages.
-- no debconf information
- End forwarded message -
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750906: gentle: Please update to use wxwidgets3.0
On Wed, Jun 25, 2014 at 02:09:29PM +0200, Andreas Tille wrote: thanks for your effort to move to wxwidgets 3.0 and the provided patch. I injected it into gentle SVN svn+ssh://svn.debian.org/svn/debian-med/trunk/packages/gentle/trunk/ but I realised that it does not apply cleanly. Could you please verify that `quilt push -a` applies to the source code since I personally do not have any idea how to do the wx migration. I can quilt pop -a and quilt push -a and everything's clean. Comparing the patches in your repo with those in my unpacked tree, I notice that you've stripped \r from wx3.0-compat.patch - perhaps that's why it doesn't apply cleanly? The upstream code seems to have a random smattering of files with CR+LF line endings. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636783: minimum discussion period
I would like to present an improved proposal for a minimum TC discussionn period, which will allow the committee to move quickly when there is consensus (at least, procedural consensus) within the committee: * Constitution 6.3(1), delete - There is no minimum discussion period; and replace it with a new paragraph inserted into the end of 6.3(1): + There is a minimum discussion period of 5 days. + However, the persion calling a vote may waive the minimum + discussion period; in that case the vote may be cancelled by + any member of the committee, if they do so within 5 days of + the vote being called. Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752275: torbrowser-launcher: downgrade and indefinite freeze attacks [was: several possible/probably security issues]
Hi, Micah Lee wrote (25 Jun 2014 18:35:45 GMT) : Rather than replying in-line to everything, I'll just summarise: Thanks, that was a good read. In case torbrowser-launcher doesn't have a security design doc yet, this should be a pretty good start :) * TLS/x.509 security: torbrowser-launcher doesn't rely on the CA infrastructure. The only TLS it does is make HTTPS requests to check.torproject.org and (if you haven't set a mirror) www.torproject.org. When it connects to these hostnames, it uses a hardcoded certificate. So none of the TLS PKI issues apply at all here. I like the idea of using the Debian archive as a side-channel, presumably already somewhat trusted, to distribute the included certificate. @Debian maintainers: it might be nice to make the stable release team aware that this package will most likely need to be updated in stable point-releases, when the certificate changes. @Micah: I hope you've got a good, automated way to promptly detect changes in the certificate(s) used by www.torproject.org. And if you have one, I'd be glad to steal and re-use it :) * Downgrade attacks shouldn't be possible, unless they're committed by Tor devs themselves. If an attacker captures a valid old request to https://check.torproject.org/RecommendedTBBVersions that claims that the current version is an older version than what's currently installed, torbrowser-launcher prevents it from installing. (And by installing I mean extracting to the user's home dir.) However, there is the scenereo where the user has set a third-party mirror to download from instead of the default. The third-party mirror could serve a tarball and sig that have filenames of the latest version, but are actually an older version. This attack is mitigated by [...] When we've thought Tails incremental upgrades through, the best defense we've found against downgrade attacks is to encode the version information about a given target file (using the TUF specification nomenclature [1] here) as part of what's strongly authenticated (in this case, with OpenPGP), instead of trusting filenames in any way. That's what our upgrade-description files [2] are for. But even then, against an adversary who controls the web space that hosts the upgrade-description files, or who can break TLS, Indefinite freeze attacks are still possible. The only way I've see to mitigate it is short-lived signatures on meta-data. In the case of tor-launcher, it may be possible to drop the indirection layer (upgrade-description files), and protect against downgrade attacks simply by comparing the currently running version, with the version information that is, I guess, present in the target files, once they've been downloaded and authenticated. [I'm now realizing that the TUF spec has changed since last time I've read it. And Tor Browser's upcoming self-upgrade super-power may be a game changer.] [1] https://github.com/theupdateframework/tuf/blob/develop/docs/tuf-spec.txt [2] https://tails.boum.org/contribute/design/incremental_upgrades/ Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752731: info: clarify in 'man info' that 'info info' is in a separate package
tags 752731 + pending thanks Thanks, I have added something similar, slithly different wording. Will be in the next upload, already in the git repo. Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750001: freedink-dfarc: Please update to wxwidgets3.0
# blocks the on-going wxwidgets3.0 transition severity 750001 serious thanks On Sat, May 31, 2014 at 04:23:12PM +0200, b...@debian.org wrote: I (as upstream) do not wish to update to wxWidgets2.8 yet because wxGlade (used to generate the *_Base.cpp files) doesn't support it, and because MXE (for the Windows cross-build) doesn't seem to either (though it builds 2.9 already). In what way does wxGlade not handle the patched code? The changes I made in that area were just updating things which were deprecated in 2.8 and have been removed in 3.0; if wxGlade doesn't handle them, it's likely broken for wx2.8 too. As upstream, you don't have to drop wx2.8 support to add wx3.0 support (the patch I sent should work with both), but FWIW MXE appears to support wx3.0: https://github.com/mxe/mxe/blob/master/src/wxwidgets.mk So while such a move is planned, it's too early to make it. Please consider supporting both 2.8 and 3.0 in Jessie (as with 2.6/2.8). It will also make backports easier. It's really not feasible to support two different wx releases in Jessie - there are only two people in the wx team who have been at all active in recent times. Since there's no upstream interest in wx2.8, and a number of packages actually require wx3.0, wx3.0 is the sane choice. Having 2.6 and 2.8 in a release together didn't work out well - bugs in 2.6 just piled up because upstream weren't interested. That's not what we want in a large and complex library package. Last, I (as package maintainer) would object to Debian diverging from upstream, especially with forwarded:no patches, so no NMU please. Since you are upstream maintainer, we can now consider the patch as forwarded. The patch I sent doesn't break compatibility with wx2.8 - I did a test build to verify this. Note that in wx2.8 wxTHICK_FRAME is just defined to wxRESIZE_BORDER, so changing wxRESIZE_BORDER|wxTHICK_FRAME to wxRESIZE_BORDER makes no different to behaviour. Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736878: python-django: Please provide python3-django
On 26 June 2014 10:36, Brian May br...@microcomaustralia.com.au wrote:
On 25 June 2014 16:27, Raphael Hertzog hert...@debian.org wrote:
Not tested, but you get the idea I guess. And obviously we need strong (=
${binary:Version}) dependency between python*-django and
python-django-common.
# find -type f debian/python3-django/usr/lib/python3/dist-packages/ -not
-name '*.py'
find: paths must precede expression:
debian/python3-django/usr/lib/python3/dist-packages/
Usage: find [-H] [-L] [-P] [-Olevel] [-D
help|tree|search|stat|rates|opt|exec] [path...] [expression]
Am glad I am not the only one who makes this particular mistake. :-)
I committed a working version to subversion.
+override_dh_python3:
+ dh_python3
+ find debian/python3-django/usr/lib/python3/dist-packages/ -type f
-not -name '*.py' | \
+ (while read file; do \
+
relname=$${file##debian/python3-django/usr/lib/python3/dist-packages/}; \
+ reldirname=$$(dirname $$relname); \
+ mkdir -p
debian/python-django-common/usr/share/python-django-common/$$reldirname; \
+ mv $$file
debian/python-django-common/usr/share/python-django-common/$$reldirname/; \
+ ln -sf /usr/share/python-django-common/$$relname $$file; \
+ if test -e
debian/python-django/usr/share/pyshared/$$relname; then \
+ rm debian/python-django/usr/share/pyshared/$$relname; \
+ ln -sf /usr/share/python-django-common/$$relname
debian/python-django/usr/share/pyshared/$$relname; \
+ else \
+ rm
debian/python-django/usr/lib/python2.7/dist-packages/$$relname; \
+ ln -sf /usr/share/python-django-common/$$relname
debian/python-django/usr/lib/python2.7/dist-packages/$$relname; \
+ fi \
+ done)
+
I had to use override_dh_python3 not override_dh_install, because the
directory name is debian/python3-django/usr/lib/python3.4 then.
The only problem with the package I can see only shows up when compiling
against wheezy, suspect it might be because the dh-python I am using is old
(1.20131021-1~bpo70+1) - I had problems building the latest version on
wheezy. Whatever is doing it, it is kind of weird.
$ cat debian/django-admin
#!/bin/sh
if test -x /usr/bin/python3 test -e
/usr/lib/python3/dist-packages/django/bin/django-admin.py
then
exec python3 /usr/lib/python3/dist-packages/django/bin/django-admin.py
$@
elif test -x /usr/bin/python2.7 test -e
/usr/lib/python2.7/dist-packages/django/bin/django-admin.py
then
exec python2.7
/usr/lib/python2.7/dist-packages/django/bin/django-admin.py $@
else
echo Cannot find installed version of python-django or
python3-django. 2
exit 1
fi
$ cat /usr/bin/django-admin
#! /usr/bin/python3 test -e
/usr/lib/python3/dist-packages/django/bin/djan
if test -x /usr/bin/python3 test -e
/usr/lib/python3/dist-packages/django/bin/django-admin.py
then
exec python3 /usr/lib/python3/dist-packages/django/bin/django-admin.py
$@
elif test -x /usr/bin/python2.7 test -e
/usr/lib/python2.7/dist-packages/django/bin/django-admin.py
then
exec python2.7
/usr/lib/python2.7/dist-packages/django/bin/django-admin.py $@
else
echo Cannot find installed version of python-django or
python3-django. 2
exit 1
fi
--
Brian May br...@microcomaustralia.com.au
Bug#678446: util-linux needs updating to the latest upstream release (version 2.24+)
According to one duplicate bug report[1], even Theodore Ts'o wants to test the fresh experimental package version :) [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738269#54 Best wishes, Bob -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719763: QT4 FTBFS on mips64(el) and mipsn32(el)
This patch has been accepted by upstream, and released with 4.8.6. Now, this tiny patch can make it work. On Tue, Sep 17, 2013 at 5:29 AM, Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com wrote: tag 719763 pending thanks On Tuesday 10 September 2013 12:59:39 YunQiang Su wrote: On Tue, Sep 10, 2013 at 9:47 AM, Lisandro Damián Nicanor Pérez Meyer [snip] https://codereview.qt-project.org/#change,64279 This is the one for qt5. Cool, thanks a lot! I have saw that the patch has already been ACKed by upstream, it only needs Thiago having some time to +1 it. I'm so adding it as a patch for now, it will be included on next upload. Thanks a lot for your effort! -- Los promotores del software privativo demonizan algo tan básico y ético como el hecho de compartir imponiendo términos como el de 'pirata'. Equiparan ayudar al prójimo con atacar barcos. Cuando me preguntan qué pienso de la piratería musical e informática digo que atacar barcos es muy malo y, que yo sepa, los piratas no usan computadoras.” Richard Stallman, 05/11/2008, anexo de la Cámara de Diputados, Argentina Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ -- Yunqiang Su diff -Nru qt4-x11-4.8.6+dfsg/debian/patches/07_trust_dpkg-arch_over_uname-m.diff qt4-x11-4.8.6+dfsg/debian/patches/07_trust_dpkg-arch_over_uname-m.diff --- qt4-x11-4.8.6+dfsg/debian/patches/07_trust_dpkg-arch_over_uname-m.diff 2013-05-24 23:55:38.0 +0800 +++ qt4-x11-4.8.6+dfsg/debian/patches/07_trust_dpkg-arch_over_uname-m.diff 2014-06-26 09:34:44.0 +0800 @@ -45,7 +45,7 @@ + lpia) + UNAME_MACHINE=i686 + ;; -+ mipsel) ++ mips*) + UNAME_MACHINE=mips + ;; + powerpc) diff -Nru qt4-x11-4.8.6+dfsg/debian/rules qt4-x11-4.8.6+dfsg/debian/rules --- qt4-x11-4.8.6+dfsg/debian/rules 2014-06-16 10:02:27.0 +0800 +++ qt4-x11-4.8.6+dfsg/debian/rules 2014-06-26 09:33:58.0 +0800 @@ -67,7 +67,7 @@ endif ifeq ($(DEB_HOST_ARCH_OS),linux) - ifneq (,$(filter $(DEB_HOST_ARCH),alpha ia64)) + ifneq (,$(filter $(DEB_HOST_ARCH),alpha ia64 mips64 mips64el)) platform_arg = linux-g++ else ifeq ($(DEB_HOST_ARCH_BITS),64) platform_arg = linux-g++-64
Bug#752736: nkf.1j is broken
Package: nkf Version: 2.13-1 Severity: normal Dear Maintainer, nkf.1j is broken. nkf.1j is man page for Japanese. When I run 'man nkf' on Japanese environment, all Japanese character is replaced with 'X'. And, what the man file is the same state. Best regards, Nobuhiro -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf armel Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nkf depends on: ii libc6 2.19-1 nkf recommends no packages. nkf suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752280: RM: haskell-attempt haskell-attoparsec-conduit haskell-base64-conduit haskell-blaze-builder-conduit haskell-filesystem-conduit haskell-network-conduit haskell-pool-conduit haskell-wai-even
Hi, Am Samstag, den 21.06.2014, 23:19 -0700 schrieb Joachim Breitner: the latest release of the conduit- and wai-related libraries caused some reorganisation, and hence obsoletion of some packages. Please remove the mentioned source packages from unstable at some time. (This is not yet critical for a testing migration, but will eventually. I’ll come back to you when that happens.) we are nearing the transition, and according to dak on coccoia, there are no more # Broken Depends: on RC architectures, so from my POV, this looks like it’s good to go. Thanks, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#696950: Mentoring python-fdb
Hi Philippe, I've contacted you about this in other ways, but in retrospect I should have done it here so they is a public record of it. On Tue, 01 Jan 2013 17:10:37 +0100, Philippe Makowski write: I am looking for a sponsor for my package python-fdb I'd like to see python-fdb in Debian. I am happy to mentor and sponsor you, if you are still interested. Please let me know. I'd want to ensure it gets into jessie. As the freeze approaching if I haven't heard from you by 2014-07-24 (ie one month's time), I'll package fdb myself. signature.asc Description: This is a digitally signed message part
Bug#752737: ITP: patchclamp -- basic tool for patch clamping physiology recordings
Package: wnpp Severity: wishlist Owner: Yaroslav Halchenko deb...@onerussian.com * Package name: patchclamp Version : 1.0 Upstream Author : Vadim Alexeenko v.a.alexee...@gmail.com * URL : http://patchclamp.net * License : GPL Programming Lang: C++ Description : basic tool for patch clamping physiology recordings Will be maintained by upstream with help of the NeuroDebian team. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752736: nkf.1j is broken
Hi,
This already fixed in upstream.
Please see:
http://sourceforge.jp/ticket/browse.php?group_id=248tid=32546
Best regards,
Nobuhiro
2014-06-26 11:14 GMT+09:00 Nobuhiro Iwamatsu iwama...@debian.org:
Package: nkf
Version: 2.13-1
Severity: normal
Dear Maintainer,
nkf.1j is broken.
nkf.1j is man page for Japanese. When I run 'man nkf' on Japanese environment,
all Japanese character is replaced with 'X'.
And, what the man file is the same state.
Best regards,
Nobuhiro
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf
armel
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nkf depends on:
ii libc6 2.19-1
nkf recommends no packages.
nkf suggests no packages.
-- no debconf information
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719763: QT4 FTBFS on mips64(el) and mipsn32(el)
There are still some problem in debian/rules and one of our patch to build system. See the patch for details. On Thu, Jun 26, 2014 at 11:13 AM, Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com wrote: Version: 4:4.8.6+dfsg-1 On Thursday 26 June 2014 09:48:31 you wrote: This patch has been accepted by upstream, and released with 4.8.6. Then there is no need to apply it, we have 4.8.6 since 24 Apr 2014. I'm so closing this bug. -- Combata las características. Si una característica no es absolutamente esencial, descártela, especialmente si tiene el mismo efecto que se puede alcanzar mediante la combinación de otras características. Andrew S. Tanenbaum, de su libro Computer Networks Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ -- Yunqiang Su -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748279: RFS: janeclone/1.1.4 [ITP] -- friendly greeter
Hi,
If you want to find a sponsor, you should not be using it this bug.
You must register the bug of RFS.
http://mentors.debian.net/sponsor/rfs-howto
You seemed to read this, but Subject seems to be different. You must
not include a bug number in this.
So, I could check your package.
1. Please add debian version.
Debain version is not included in your package. Please add it.
https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version
2. Please delete the template file.
Package has some in template file in debian dirtectory.
For example, README, README.source, init.d.ex and other.
A file having EX to extension is the template file which is
unnecessary with many packages.
3. Please write copyright file exactly.
Please see
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile.
4. Please include ITP bug number into changelog.
Please see
https://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog.
5. Please write control file exactly.
1 Source: janeclone
2 Section: net
3 Priority: extra
4 Maintainer: hiroyuki nagata newserver...@gmail.com
5 Build-Depends: debhelper (= 8.0.0), autotools-dev, libatk1.0-0
(= 1.29.3), libc6 (= 2.7), libcairo2 (= 1.2.4), libdbus-1-3 (=
1.1.1), libfontconfig1 (= 2.8.0), libfreetype6 (= 2.2.1),
libgcc1 (= 1:4.1.1), libglib2.0-0 (= 2.12.0), libpango1.0-0 (=
1.14.0), libstdc++6 (= 4.1.1),libwxbase3.0-0, libwxgtk3.0-0,
libxml2-dev (= 2.8.0), fonts-mona, libcurl4-openssl-dev
You dont need set all build-depend packages. For example, libc6,
libgcc1 and libstdc++6
are unnecessary. Also, here lists the packages required to build.
For example, libatk1.0-0 is not necessary to build, it is a required
package to run this
software. Perhaps, you should set libatk1.0-dev instead of this.
Please see
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-sourcebinarydeps.
6 Standards-Version: 1.1.4
It is not a section to set a version of the software here. You set a
version in Debian Policy.
Please see
https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Standards-Version.
7 Homepage: https://github.com/Hiroyuki-Nagata/JaneClone
8
9 Package: janeclone
10 Architecture: any
11 Depends: ${shlibs:Depends}, ${misc:Depends}
12 Description: Cross Platform 2ch browser
13 JaneClone is a plain browser dedicated to read 2ch thread. Using
a library called wxWidgets.
14 It will work on Windows, Linux, Mac. It will keep the
platform-specific user interface.
Please write more descripiton of this package. For example, you
should write a different characteristic as other 2ch browser.
If you have not read the following documents, I recommend that you read earlier.
- https://www.debian.org/doc/manuals/maint-guide/
- https://www.debian.org/doc/manuals/developers-reference/
- packaging-tutorial / please do 'apt-get install packaging-tutorial'
- https://www.debian.org/doc/debian-policy/
BTW, have you who signed the GPG key with someone?
If you have not yet, you need.
Best regards,
Nobuhiro
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package janeclone
* Package name: janeclone
Version : 1.1.4
Upstream Author : newserver...@gmail.com
* URL : https://github.com/Hiroyuki-Nagata/JaneClone
* License : GPL v2
Section : net
It builds those binary packages:
janeclone - Cross Platform 2ch browser
To access further information about this package, please visit the
following URL:
http://mentors.debian.net/package/janeclone
Alternatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/j/janeclone/janeclone_1.1.4.dsc
More information about janeclone can be obtained from
wiki: https://github.com/Hiroyuki-Nagata/JaneClone/wiki
doxygen : http://hiroyuki-nagata.github.io/JaneClone/
There is only the Japanese explanation to either site,
but there is a screen shot of the application towards the wiki.
Description about package
JaneClone is a simple browser for the Internet bulletin board.
, like the 2ch.net or other thread float style bulletin board systems.
Feature
It will work on Linux, Windows, Mac. It will keep the
platform-specific user interface.
And it has functions for bulletin board system ( for example, post
a thread or response,
read thread, search user ID, download Images. etc.)
Regards,
Hiroyuki Nagata
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719763: QT4 FTBFS on mips64(el) and mipsn32(el)
reopen 719763 tag 719763 pending thanks On Thursday 26 June 2014 11:34:20 Yunqiang Su wrote: There are still some problem in debian/rules and one of our patch to build system. See the patch for details. Now I understand. Sorry, but I didn't get it from the previous mail. The patch looks fine, so I've applied it in our repo. It will be included on the next upload. Kinds regards, Lisandro. -- Sólo porque un mensaje pueda no ser recibido no implica que no valga la pena enviarlo. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
On Thursday 26 June 2014 12:16:22 Yunqiang Su wrote: I refreshed this patch for mips64el Yunqiang: again, when we are talking about symbols files, a simple patch for just one arch is not enough. The best way to solve this is to let mips64[el] build logs be available trough debian-ports. Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#752738: sikuli-ide throws java.lang.NoClassDefFoundError on start
Package: sikuli-ide Version: 1.0~x~rc3.tesseract3-dfsg1-7 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, the default install of sikuli-ide in testing (Jessie) running on OpenJDK throws a java.lang.NoClassDefFoundError due to missing jars on the classpath. Exception in thread main java.lang.NoClassDefFoundError: com/google/common/collect/MapMaker. Adding the following to the classpath solves the issue and allows sikuli-ide to start /usr/share/maven-repo/com/google/guava/guava/debian/guava-debian.jar:/usr/share /maven-repo/org/jruby/ext/posix/jnr-posix/debian/jnr-posix- debian.jar:/usr/share/java/jaffl.jar Please see patch attached. Regards. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.15.1-slimjim (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sikuli-ide depends on: ii default-jre [java6-runtime] 2:1.7-52 ii junit 3.8.2-8 ii libcommons-cli-java 1.2-3 ii libjson-simple-java 1.1.1-2 ii libjxgrabkey-java 0.3.2-7 ii libmac-widgets-java 0.9.5+svn369-dfsg1-3 ii libsikuli-script-java 1.0~x~rc3.tesseract3-dfsg1-7 ii libswing-layout-java 1.0.4-4 ii libswingx-java1:1.6.2-2 ii openjdk-7-jre [java6-runtime] 7u55-2.4.7-2 ii oracle-java6-jdk [java6-runtime] 6u45 ii oracle-java7-jre [java6-runtime] 7u60 sikuli-ide recommends no packages. sikuli-ide suggests no packages. -- no debconf information *** /home/simon/sikuli-ide.diff --- a/sikuli-ide2014-06-26 15:56:46.833192680 +1200 +++ b/sikuli-ide2014-06-26 15:56:06.262192574 +1200 @@ -1,2 +1,2 @@ #!/bin/sh *** /home/simon/sikuli-ide.diff --- a/sikuli-ide2014-06-26 15:56:46.833192680 +1200 +++ b/sikuli-ide2014-06-26 15:56:06.262192574 +1200 @@ -1,2 +1,2 @@ #!/bin/sh -LC_NUMERIC=C exec /usr/bin/java -cp /usr/share/java/jna.jar:/usr/share/java/asm3.jar:/usr/share/java/asm3-commons.jar:/usr/share/java/antlr3-runtime.jar:/usr/share/java/libconstantine-java.jar:/usr/share/java/jython.jar:/usr/share/java/commons-cli.jar:/usr/share/java/JXGrabKey.jar:/usr/share/java/json_simple.jar:/usr/share/java/swing-layout.jar:/usr/share/java/swingx-core.jar:/usr/share/java/forms.jar:/usr/share/java/jgoodies-common.jar:/usr/share/java/mac_widgets.jar:/usr/share/java/junit.jar:/usr/share/sikuli/sikuli-ide.jar:/usr/share/java/sikuli-script.jar -Dsikuli.console=true -Dsikuli.debug=0 -Xms64M -Xmx512M -Dfile.encoding=UTF-8 -Dpython.home=/usr/share/jython -Dpython.path=/usr/share/sikuli/Lib -Dpython.cachedir=$HOME/.jython-cache org.sikuli.ide.SikuliIDE $@ +LC_NUMERIC=C exec /usr/bin/java -cp /usr/share/maven-repo/com/google/guava/guava/debian/guava-debian.jar:/usr/share/maven-repo/org/jruby/ext/posix/jnr-posix/debian/jnr-posix-debian.jar:/usr/share/java/jaffl.jar:/usr/share/java/jna.jar:/usr/share/java/asm3.jar:/usr/share/java/asm3-commons.jar:/usr/share/java/antlr3-runtime.jar:/usr/share/java/libconstantine-java.jar:/usr/share/java/jython.jar:/usr/share/java/commons-cli.jar:/usr/share/java/JXGrabKey.jar:/usr/share/java/json_simple.jar:/usr/share/java/swing-layout.jar:/usr/share/java/swingx-core.jar:/usr/share/java/forms.jar:/usr/share/java/jgoodies-common.jar:/usr/share/java/mac_widgets.jar:/usr/share/java/junit.jar:/usr/share/sikuli/sikuli-ide.jar:/usr/share/java/sikuli-script.jar -Dsikuli.console=true -Dsikuli.debug=0 -Xms64M -Xmx512M -Dfile.encoding=UTF-8 -Dpython.home=/usr/share/jython -Dpython.path=/usr/share/sikuli/Lib -Dpython.cachedir=$HOME/.jython-cache org.sikuli.ide.SikuliIDE $@ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746900: qtdeclarative-opensource-src: ftbfs with GCC-4.9
On Thu, Jun 26, 2014 at 12:35 PM, Lisandro Damián Nicanor Pérez perezme...@gmail.com wrote: Note: I'm sending yuou a copy because I mistakenly sent it to the original bug reporter. On Thursday 26 June 2014 12:16:22 Yunqiang Su wrote: I refreshed this patch for mips64el Yunqiang: again, when we are talking about symbols files, a simple patch for just one arch is not enough. The best way to solve this is to let mips64[el] build logs be available trough debian-ports. Yes, of course, while we are still waiting for the debian-ports guys to let us in. For now, you can get the buildlog from http://mips64el.debian.net/debian/buildlog Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ -- Yunqiang Su -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752739: plymouth (0.9.0-3): VT1 login incorrect, VT7 issue
Package: plymouth Version: 0.9.0-3 Severity: important Dear Maintainer, Since upgrade from 0.8.8-17 to 0.9.0-3 login as root or as user to vt1 (tty1) is no longer possible. After typing the (correct) password and pressing enter the login screen shows 'Login incorrect'. After stopping lightdm it's also not possible to login to vt7, 'Debian login:' is not shown. Login to other vertual terminals (vt2 - vt6) works. No such login issues using plymouth 0.8.8-17. -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: 3.14-8.dmz.1-liquorix-amd64 Systemd, udev: 208-3 Kind regards, Jos v. Wolput -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718272: BDB
Scott said: one more thing: debian is discussion dropping libdb (the db the node, but not the wallet, uses). That might force our hand as well: either ship and support upstream's included libdb or drop the node and just ship the wallet. libdb long-term security maintenance might be challenging. -- Actually, it's the other way around. Since version 0.8, BDB is *only* used for the wallet, not anything else. IIRC it was also used by the node component until 0.8, where it was replaced with LevelDB. In fact, if you configure with --disable-wallet, BDB isn't needed at all. But yes, as someone mentioned, BDB is not backwards compatible. If you've been shipping with any version newer than 4.8 (which is not recommended and throws a a warning when configuring for this reason) you need to take responsibility for ensuring that that version or newer remains available.
Bug#720953: Bug#742767: fonts-texgyre: Termes font in does not render ligatures in evince
Am Dienstag, den 20.05.2014, 06:33 +0200 schrieb Fabian Greffrath: In my opinion, either the font should get fixed (prefered) or poppler should get fixed/hacked to include a workaround and be less picky about the glyph names - it worked in previous releases after all. Last week I provided fixes for both. What will happen with these? - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730600: [pkg-kolab] Bug#730600: libkolabxml: New upstream version available
It seems like the packages in the debian git repository look quite close to being ready. I'm pretty sure they need symbols files, libkolab also probably needs a __init__.py file to be created. (I've been working on those) The packages then need to be tested against kdepim. Diane On Wednesday, June 25, 2014 16:56:53 Franz Schrober wrote: What is the current state? The missing update of this package seems to block the upload of the new kdepim packages to unstable. ___ pkg-kolab-devel mailing list pkg-kolab-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kolab-devel
