على الجمعـة 3 تشرين الثاني 2017 17:52، كتب Diane Trout:
> There was also symbols removed between 1.4.1 to 1.5 but upstream didn't
> change their SOVERSION.
>
> As an aside while I was looking at the missing symbols I found mfprintf
> was still listed in htslib 1.5's cram/mFILE.h, but the imple
Package: mixmaster
Version: 3.0.0-8.1
Followup-For: Bug #824827
Dear Maintainer,
> Mixmaster does not support 4k keys.
>
> It is not designed to support 4k keys.
>
> Closing the bug.
Hold on.. even if the project has decided that 1k keys is the way
forward, 2 bugs still remain:
bug 1: mixmast
Source: json-glib
Version: 1.4.2-1
Severity: serious
Forwarded: https://gitlab.gnome.org/GNOME/json-glib/issues/28
The test-suite fails on s390x:
1/14 array OK 0.01 s
2/14 boxed OK 0.01 s
3/14 builder
Package: bumblebee-nvidia
Version: 3.2.1-16
Severity: grave
Justification: renders package unusable
Dear Maintainer,
My system is a Thinkpad T440p, with both an Intel and an NVIDIA Optimus cards.
On Wednesday, upgrading both the Mesa libraries and the NVIDIA driver broke the
desktop ---i.e., afte
Source: json-glib
Version: 1.4.2-1
Severity: serious
Forwarded: https://gitlab.gnome.org/GNOME/json-glib/issues/27
The test-suite fails on i386:
1/14 array FAIL 0.01 s
2/14 boxed OK 0.01 s
3/14 builder
On Fri, Nov 03, 2017 at 02:52:11PM -0700, Diane Trout wrote:
> I restored it with git-revert and rebuilt 1.4.1 and 1.5 and discovered
> there were #MISSING# symbols in each rebuild
That's at most to be expected, there was a SONAME bump in the meantime.
> 1.2 -> 1.4.1 had missing symbols but there
Processing commands for cont...@bugs.debian.org:
> package mixmaster
Limiting to bugs with field 'package' containing at least one of 'mixmaster'
Limit currently set to 'package':'mixmaster'
> unarchive 824827
Bug #824827 {Done: Colin Tuckley } [mixmaster] Error:
Encryption failed!
Unarchived Bu
Package: myspell-de-de
Version: 20161207-2
Severity: grave
The transitional package myspell-de-de is not installable because its
dependency hunspell-de-de has an unversioned Conflicts with it. This
very much defeats the purpose of a transitional package.
-- System Information:
Debian Release:
Your message dated Fri, 3 Nov 2017 19:58:39 -0200
with message-id <20171103195839.1d038dd8d314cec6ac48a...@softwarelivre.org>
and subject line
has caused the Debian Bug report #877191,
regarding Package is not installing
to be marked as done.
This means that you claim that the problem has been de
Your message dated Fri, 3 Nov 2017 19:48:38 -0200
with message-id <20171103194838.8c93866b71d759ca89188...@softwarelivre.org>
and subject line
has caused the Debian Bug report #877193,
regarding Package is not installing
to be marked as done.
This means that you claim that the problem has been de
> I believe that adding the symbols file back in is the correct
solution.
> It should allow dpkg-shlibdeps to generate the correct libhst2
> dependencies version.
>
> Diane
>
>
Graham pointed out there was a symbols file from 1.2 that was removed.
I restored it with git-revert and rebuilt 1.
Viktor Jägersküpper:
> I confirm that with this change tor starts normally without apparmor
> installed.
Thanks a lot for testing & reporting back!
Hi Laurent,
Laurent Bigonville:
> My 2¢ here. Why is AppArmorProfile even needed here? Shouldn't apparmor
> figureout
> itself that it need to migrate to the system_tor domain(?)?
Good question, glad you're asking! :)
It's technically doable to have an AppArmor profile that will be
applied to a
Processing commands for cont...@bugs.debian.org:
> notforwarded 879002
Bug #879002 [src:libpam4j] Should the package be removed?
Unset Bug forwarded-to-address
> # added to the wrong bug should have been only for 879001
> tags 879002 - patch upstream
Bug #879002 [src:libpam4j] Should the package b
Am 03.11.2017 um 21:48 schrieb Salvatore Bonaccorso:
[...]
> It's likely that Red Hat just used the approeach as
> https://github.com/letonez/libpam4j/commit/84f32f4001fc6bdcc125ccc959081de022d18b6d
> and referenced from https://github.com/kohsuke/libpam4j/issues/18 .
>
> The issue arises because
Control: forwarded -1 https://github.com/kohsuke/libpam4j/issues/18
Control: tags -1 + patch upstream
Hi Raphael, Emmanuel and Markus,
On Fri, Nov 03, 2017 at 09:19:56PM +0100, Markus Koschany wrote:
> On Wed, 18 Oct 2017 13:29:19 +0200 Emmanuel Bourg wrote:
> > Upstream has moved to GitHub [1]
Processing control commands:
> forwarded -1 https://github.com/kohsuke/libpam4j/issues/18
Bug #879002 [src:libpam4j] Should the package be removed?
Set Bug forwarded-to-address to 'https://github.com/kohsuke/libpam4j/issues/18'.
> tags -1 + patch upstream
Bug #879002 [src:libpam4j] Should the pack
Processing control commands:
> forwarded -1 https://github.com/kohsuke/libpam4j/issues/18
Bug #879001 [src:libpam4j] CVE-2017-12197: libpam4j: Account check bypass
Set Bug forwarded-to-address to 'https://github.com/kohsuke/libpam4j/issues/18'.
> tags -1 + patch upstream
Bug #879001 [src:libpam4j]
On Friday 03 November 2017 1:27:24 PM Jonas Smedegaard wrote:
> Quoting Luke Dashjr (2017-11-03 11:25:23)
>
> > On Friday 03 November 2017 9:10:37 AM you wrote:
> >> I believe Bitcoin is now stable enough for stable release.
> >
> > Things have only gotten less stable upstream since 2013...
>
>
On Wed, 18 Oct 2017 13:29:19 +0200 Emmanuel Bourg wrote:
> Upstream has moved to GitHub [1] and the last update was released in
> 2014 but the security issue is still not fixed [2].
>
> This was a dependency of Jenkins which is now gone. There is a slim
> chance that this package could be useful
Your message dated Fri, 03 Nov 2017 19:48:54 +
with message-id
and subject line Bug#880039: fixed in bear 2.3.9-1
has caused the Debian Bug report #880039,
regarding beara fails without en_US.UTF-8 locale
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On 2017-11-03 Jan Kiszka wrote:
> Has this topics also been brought up upstream already? Didn't find a
> reference so far.
No, I have not yet done so. The OCB licenses is listed in GIT's LICENSES
file, it is just not listed in EXTRA_DIST and therefore missing in the
tarball.
Re Debian I think we
> Would adding a symbols file back to the htslib packaging be an
> alternative solution to manually overriding ${shlibs:Depends} in
> samtools, bcftools, and python-pysam? The build-depends in these
> packages are always versioned appropriately.
>
I believe that adding the symbols file back in is
On Fri, Nov 3, 2017 at 11:31 PM, Michael Biebl wrote:
> Am 03.11.2017 um 17:25 schrieb Michael Biebl:
>
>> It's a known issue, see https://bugzilla.gnome.org/show_bug.cgi?id=789625
>
> Let me rephrase that a little: I'm pretty sure it's the same underlying
> issue and it would be great if you can
Your message dated Fri, 03 Nov 2017 17:06:12 +
with message-id
and subject line Bug#877567: fixed in llvm-toolchain-5.0 1:5.0.1~+rc1-1~exp1
has caused the Debian Bug report #877567,
regarding llvm-toolchain-3.9 FTBFS on mipsel
to be marked as done.
This means that you claim that the problem h
Hendrik Tews:
>
>> Hi Hendrik, any progress on this? I notice in the ocaml transition tracker:
>
> I really spend more than 4 weeks in discussions with upstream
> about license and copyright clarifications. Now it is finished. I
> uploaded a new hol-light version to DOM git yesterday. Please
> re
Am 03.11.2017 um 17:25 schrieb Michael Biebl:
> It's a known issue, see https://bugzilla.gnome.org/show_bug.cgi?id=789625
Let me rephrase that a little: I'm pretty sure it's the same underlying
issue and it would be great if you can give the patch in the upstream
bug tracker a try.
--
Why is i
Processing control commands:
> forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=789625
Bug #880674 [libpango-1.0-0] libpango-1.0-0: Thai word break stops working
since 1.40.13
Set Bug forwarded-to-address to
'https://bugzilla.gnome.org/show_bug.cgi?id=789625'.
> tags -1 + patch
Bug #88067
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=789625
Control: tags -1 + patch
Am 03.11.2017 um 16:36 schrieb Jeremy Bicha:
> Control: severity -1 serious
>
> On Fri, Nov 3, 2017 at 11:25 AM, Theppitak Karoonboonyanan
> wrote:
>> Since Pango 1.40.13, Thai word break appears to
Hi,
same here, after upgrade to buster no X anymore. Normal start works, but
ends at terminal login. Manual startx makes the screen flicker briefly,
then back to terminal. X log contain no errors (EE).
Downgrade to stretch didn't change the situation in any way. Going back
from linux 4.13 to 4.8
Processing commands for cont...@bugs.debian.org:
> # this is caused by python-django 1.11 in buster/sid, which now has a breaks
> against the o-d version from stretch
> tags 867254 + sid buster
Bug #867254 {Done: Thomas Goirand } [openstack-dashboard]
openstack-dashboard: fails to install:
djan
Processing control commands:
> severity -1 serious
Bug #880674 [libpango-1.0-0] libpango-1.0-0: Thai word break stops working
since 1.40.13
Severity set to 'serious' from 'important'
--
880674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880674
Debian Bug Tracking System
Contact ow...@bug
Hi Aaron,
Thank you for reporting this. Autopkgtest's were not run in previous
versions of this package, and this shows that the new tests are
working :-) I have forwarded this bug upstream along with a couple of
questions about how to proceed.
Regards,
Nicholas
signature.asc
Description: PGP
Hi Aaron,
Thank you for reporting this. Autopkgtest's were not run in previous
versions of this package, and this shows that the new tests are
working :-) I have forwarded this bug upstream along with a couple of
questions about how to proceed.
Regards,
Nicholas
signature.asc
Description: PGP
Processing commands for cont...@bugs.debian.org:
> forwarded 880670 https://github.com/Sarcasm/irony-mode/issues/449
Bug #880670 [src:irony-mode] irony-mode: FTBFS on mips64el: FAILED 22/41
irony-iotask-schedule/task-update/invalid-msg
Set Bug forwarded-to-address to
'https://github.com/Sarcas
Processing commands for cont...@bugs.debian.org:
> forwarded 880669 https://github.com/Sarcasm/irony-mode/issues/449
Bug #880669 [src:irony-mode] irony-mode: FTBFS on arm64: timeout in
irony-iotask-schedule/task-update/invalid-msg
Set Bug forwarded-to-address to
'https://github.com/Sarcasm/irony
Source: irony-mode
Version: 1.2.0-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-m...@lists.debian.org
Usertags: mips64el
The latest build of irony-mode for mips64el encountered a test suite
failure in irony-iotask-sch
Source: irony-mode
Version: 1.2.0-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: arm64
The latest build of irony-mode for arm64 hit the autobuilder's
generous 150-minute inactivity timeou
The crash mentioned in this bug report has been fixed after packaging the
newest upstream source, version 2.11.1.
The new package is available from the code repository.
https://anonscm.debian.org/gitweb/?p=pkg-crosswire/bibletime.git
I will be asking for sponsorship for uploading this package.
Quoting Luke Dashjr (2017-11-03 11:25:23)
> On Friday 03 November 2017 9:10:37 AM you wrote:
>> I believe Bitcoin is now stable enough for stable release.
>
> Things have only gotten less stable upstream since 2013...
Please provide references supporting that.
> What is the plan for getting secu
Has this topics also been brought up upstream already? Didn't find a
reference so far.
The crash reported in this bug does not occur when building the newer
upstream version from source. That newer version, built from source,
behaves as expected.
Processing control commands:
> tags 853351 + pending
Bug #853351 [src:libmstoolkit] comet-ms: ftbfs with GCC-7
Bug #853498 [src:libmstoolkit] libmstoolkit: ftbfs with GCC-7
Added tag(s) pending.
Added tag(s) pending.
--
853351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853351
853498: htt
Control: tags 853351 + pending
Dear maintainer,
I've prepared an NMU for libmstoolkit (versioned as 77.0.0-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards,
_g.
diff -Nru libmstoolkit-77.0.0/debian/changelog
libmstoolkit-77.0.0/debian/changel
Your message dated Fri, 03 Nov 2017 12:19:05 +
with message-id
and subject line Bug#879848: fixed in cappuccino 0.5.1-7
has caused the Debian Bug report #879848,
regarding cappuccino: missing dependency on gir1.2-gtk-3.0
to be marked as done.
This means that you claim that the problem has bee
Package: src:snakemake
Followup-For: Bug #878498
The test also fails with the 3.13.3 version in the team repository.
I've had a short look at whether upgrading to 4.3.0 helps (minimal patch
refreshing and new build dependency on python3-configargparse as well as
the unpackaged ratelimiter module)
On 11/03/2017 11:25 AM, Julien Cristau wrote:
> Package: appstream
> Severity: grave
> X-Debbugs-Cc: ftpmas...@ftp-master.debian.org
>
> [filing this against the appstream package as a substitute for
> appstream.debian.org, feel free to reassign if there's a better place]
>
> Hi,
>
> there's som
On Friday 03 November 2017 9:10:37 AM you wrote:
> I believe Bitcoin is now stable enough for stable release.
Things have only gotten less stable upstream since 2013...
What is the plan for getting security and protocol change updates backported
to Debian stable?
Luke
Package: pinta
Version: 1.6-2
Followup-For: Bug #877106
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Using the paintbrush tool
* What exactly did you do (or not do) that was effective (or
ineffective)?
Package: appstream
Severity: grave
X-Debbugs-Cc: ftpmas...@ftp-master.debian.org
[filing this against the appstream package as a substitute for
appstream.debian.org, feel free to reassign if there's a better place]
Hi,
there's some archive breakage because
dists/sid/non-free/dep11/Components-amd
Your message dated Fri, 03 Nov 2017 10:10:37 +0100
with message-id <150970023769.11303.14727396047278104...@auryn.jones.dk>
and subject line Re: Bitcoin still not ready for stable release in Debian
has caused the Debian Bug report #718272,
regarding upstream does not support stable releases (block
Processing commands for cont...@bugs.debian.org:
> tags 880279 + pending
Bug #880279 [src:diffoscope] diffoscope: FTBFS: Test failures
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
880279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=8
tags 880279 + pending
thanks
Fixed in Git:
https://anonscm.debian.org/git/reproducible/diffoscope.git/commit/?id=d4ce05062e0368549ffe34276233f48f9ab68900
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Your message dated Fri, 03 Nov 2017 09:54:18 +0100
with message-id <150969925873.11303.7933683725030876...@auryn.jones.dk>
and subject line Re: Bug#877854: [Pkg-bitcoin-devel] Bug#877854: bitcoin-qt:
symbol lookup error: bitcoin-qt: undefined symbol: _ZNK8UniValueixEj
has caused the Debian Bug rep
Your message dated Fri, 03 Nov 2017 08:49:30 +
with message-id
and subject line Bug#880251: fixed in duplicity 0.7.14-2
has caused the Debian Bug report #880251,
regarding duplicity: FTBFS: Test failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 03 Nov 2017 07:19:40 +
with message-id
and subject line Bug#868975: fixed in horizon 3:12.0.0-2
has caused the Debian Bug report #868975,
regarding horizon: FTBFS: Test failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Your message dated Fri, 03 Nov 2017 07:19:40 +
with message-id
and subject line Bug#867254: fixed in horizon 3:12.0.0-2
has caused the Debian Bug report #867254,
regarding openstack-dashboard: fails to install:
django.core.exceptions.ImproperlyConfigured: AUTH_USER_MODEL refers to model
'ope
57 matches
Mail list logo
