Hello everyone,
I was surprised to see the reaction my comments generated and like
Gianfranco, I also want to ask Marc to consider rethinking his decision.
I do not think you are spoiling the fun or that insisting on
oldfashioned keeping is a bad thing. I apologize that my choice of
words made y
Control: block 784451 by 832420
On 11/10/2016 09:13 PM, Andreas Tille wrote:
> I take the freedom to turn this discussion into a public one
> and CC the relevant bugs to leave a record there that something is
> happening.
Hello Andreas,
that is fine with me. I'll keep the bugs in CC too.
> Hmm
On 11/11/2016 02:29 PM, Andreas Tille wrote:
> Start 197: AmberFF_test
> 197/334 Test #197: AmberFF_test .***Failed
> 0.19 sec
> (...)
> (line 511 TEST_REAL_EQUAL(r4_r1 - r4_i, r1_r4 - r1_i): got -145.471,
> expected -103.957) -
> (line 513 TES
Hello Andreas,
On 11/12/2016 05:25 PM, Andreas Tille wrote:
> I'd prefer to skip this test anyway (or let the test suite pass even
> if it fails.
I looked into the source, and I guess excluding the test from the set is
the easiest and most straightforward way to achive the effect.
> Sure. If yo
Control: reopen -1
On Sun, 13 Nov 2016 09:18:53 + Danny Edel wrote:
> We believe that the bug you reported is fixed in the latest version of
> ball, which is due to be installed in the Debian FTP archive.
Hello Andreas, hello Steffen,
it seems like the fixes were indeed only effect
On 11/13/2016 05:55 PM, Andreas Tille wrote:
> Hi Danny,
>
> I fully agree that we should ignore test results on other than amd64
> architecture. Please let me know if you intend to implement the needed
> change or whether you suggest that I should do so.
>
> Kind regards
>
> Andreas.
>
On 05/18/2016 08:45 AM, Andreas Tille wrote:
> Could you please add your changes to debian/changelog? If you use
>
> dch
>
> it injects a separate section for your ID.
Hi Andreas,
I updated the changelog with dch and it tagged the changes with my name.
The commit is in master.
I hope its
Hello List,
I'm looking into this aswell, since I want to use digikam again and got
some free time to fix it. I hope I can provide a source-patch in the
next few days that allows the currently packaged version of digikam to
build again.
In case I get it to work, where do I send the patch? It wo
Control: tags -1 patch
Hi List,
I've tried to reproduce the build failure and it turns out that the
FindMarble.cmake file is in a path that is not in the default cmake
module search path.
If the search path is passed to cmake with EXTRA_CMAKE_ARGS, digikam
compiles successfully again.
Also the
Package: wnpp
Severity: wishlist
Owner: Danny Edel
* Package name: dspdfviewer
Version : 1.13
Upstream Author : Danny Edel
* URL : http://dspdfviewer.danny-edel.de/
* License : GPL
Programming Lang: C++
Description : Dual-Screen PDF Viewer for LaTeX
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "dspdfviewer"
* Package name: dspdfviewer
Version : 1.13-1
Upstream Author : Danny Edel
* URL : http://dspdfviewer.danny-edel.de
* License : G
On Sat, 08 Aug 2015 00:56:48 +0200 Christoph Anton Mitterer
wrote:
> Hey.
>
> Anything new here? That blocks upgrading to to current libstdc++6
> (without removing a large number of packages) and thus also prevents
> other packages (that already depend on newer libstdc++6) with important
> securi
On Sat, 27 Feb 2016 12:27:44 +0100 Danny Edel wrote:
> I will investigate further and report back here.
I cannot determine the exact cause why it fails on big-endian emulation.
Also, trying to load any GUI through the emulator just results in a
blank window, so I cannot even check if
Control: fixed -1 dspdfviewer/1.15-1
With dspdfviewer/1.15-1 uploaded to unstable and the testsuite disabled
on big-endian, it no longer fails to build from source[1], hence the
downgrade of severity and "fixed".
Howver, I'd like to keep the ticket open until the underlying problem is
identified,
Package: wnpp
Severity: wishlist
Owner: Danny Edel
* Package name: pytest-benchmark
Version : 3.0.0
Upstream Author : Ionel Cristian Mărieș
* URL : https://github.com/ionelmc/pytest-benchmark
* License : BSD-2-Clause
Programming Lang: Python
Description
Hi,
I would like to try one of the patches from upstream, but I can't figure
out how to apply them to the sourcecode I grab with "apt-get source
clang-".
In particular, neither the patch from
https://llvm.org/bugs/attachment.cgi?id=14874 nor the newer one from
http://reviews.llvm.org/D18035?downl
Source: libnetfilter-queue
Severity: wishlist
Dear maintainer,
this library can provide documentation in doxygen format, but it is not
currently built or included in a -doc package.
If you execute "doxygen doxygen.cfg" after running the normal Debian
build (which does generate this file) the doc
On 05/04/2016 02:19 PM, Andreas Tille wrote:
> Any success with you alioth commits? Did you possibly pinged alioth
> admins via IRC? I'd love to get you properly working as any normal
> Debian Med member. If not I'd try to investigate.
Hello Andreas,
sorry for the late reply, but I have been a
On 05/10/2016 07:13 PM, Andreas Tille wrote:
> Thanks a lot. Your work is really appreciated. Please also be bold and
> commit to master. I have no time to look the next 2-3 days - but I'd
> like to see the changes in master since I see no point in deriving for
> this package what we are doing a
Package: puppet-module-puppetlabs-apache
Version: 1.1.1-1
Severity: important
Tags: patch
Dear Maintainer,
using the puppet/apache module to configure an SSL-enabled site currently fails
on jessie.
The check in the file
/usr/share/puppet/modules.available/puppetlabs-apache/manifests/mod/ssl.pp
tags 777833 patch
thanks
Hello all,
I tried to rebuild digikam on sid today. The current version still
misses libsoprano-dev dependency and fails with:
> make[3]: *** No rule to make target '/usr/lib/libsoprano.so', needed
by 'lib/libkvkontakte.so.1.0.0'. Stop.
Once a build-time dependency on
On Sat, 11 Jul 2015 12:57:54 +0200 Marc Haber
wrote:
> I have stitched together a quick package and pushed it to collab-maint,
> ssh://git.debian.org/git/collab-maint/borgbackup.git
>
> I do not intend to upload until a team of at least two active people
> maintaining the package has formed.
Hel
Hi,
I have been investigating the differences of "upstream release tarball"
versus "upstream git tag/github tarball" and I noticed that "upstream
release" differs a bit:
(1) Release tarball ships .c files compiled from python sources with
cython (examples: borg/crypto.c, borg/chunker.c)
(2) Rele
On 11/29/2015 12:10 AM, Gianfranco Costamagna wrote:
> sure, I like this too, but only when some brain is added, not when the stuff
> is a result
> of some magic command :D
>
Hi everyone,
for reference: The new "magic command" basically calls the upstream
"make man" in the docs/ subdirectory: (
On 12/01/2015 05:50 PM, Marc Haber wrote:
> Package: borgbackup
> Version: 0.28.2-1
> Severity: important
>
> Hi,
>
> when invoking debuild in the same source tree twice, the second try
> fails with "unrepresentable changes to source". debian/rules clean
> should return the package in the complet
Package: libboost-program-options-dev
Version: 1.58.0.1
Dear maintainer,
I cannot link against recent boost_program_options with clang++, while
it works fine with g++. I have attached a small test program that
demonstrates the bug.
$ g++ -o options options.cpp -lboost_program_options
$ ./options
On Thu, 3 Sep 2015 17:45:27 + (UTC) Gianfranco Costamagna
wrote:
> according to [1] there might be no fix.
>
This may not be a permanent fix, but Debian could take up the "dual-abi"
idea that gcc upstream does with their libstdc++.so.6.
Example:
$ nm -D /usr/lib/x86_64-linux-gnu/libstdc++.
On 04/09/15 11:23, Gianfranco Costamagna wrote:
>
> I guess clang is not useful for cxx11 projects until llvm folks finds
> a way to make it use the new ABI.
>
Hi everyone,
I just want to make clear that this is *not* specific to c++11 projects.
Even if you don't use any c++11 features, clang c
On Mon, 31 Aug 2015 14:14:35 +0200 Danny Edel wrote:
> I am currently working on a proof-of-concept version of d/rules doing
> all of that, I will report back here once I've got a working draft.
I have pushed a working packaging to github. It's not of
release-quality, but it s
On Tue, 08 Sep 2015 09:23:51 -0400 Antoine Beaupré wrote:
>
> How does it differ from the package that Gianfranco and Marc have been
> working on? (In cc.)
>
> A.
It doesn't necessarily "differ" in the sense that it would be a
different from-scratch packaging. It is 95% their package, plus a fe
Source: dspdfviewer
Version: 1.14-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
After xorg got bumped to 1.18 in unstable, the testsuite started failing
with "floating point exception" on the parts where xvfb-run is used to
emulate a GUI.
The Q
Control: merge 814579 814581
On 13/02/16 09:41, Chris Lamb wrote:
> Dear Maintainer,
>
> dspdfviewer fails to build from source in unstable/amd64:
Hello Chris,
thank you for reporting this. I have deduced that the most likely
reason is the switch xorg 1.17->1.18. I am investigating how to fix
Package: xvfb
Version: 2:1.18.1-1
Severity: important
Control: fixed -1 2:1.18.0-3
Dear maintainer,
after running the testsuite from my package failed with the xvfb version
currently in sid, I found that the same problem also happens with the qt5
examples, so it may be a bug in the new xvfb versi
Control: forwarded -1 https://github.com/borgbackup/borg/issues/665
On 02/16/2016 01:37 AM, Mike Hommey wrote:
> Dear Maintainer,
>
> See the screencast from
> https://asciinema.org/a/28691?autoplay=1&speed=2
>
> See what output adding --stats should be presenting. It doesn't
> happen, neither
Control: block -1 by 814607
Hi,
since it seems to be not just dspdfviewer's test suite, but any qt5
program (even the qt5 examples) that brings the "Floating point
exception" when run via xvfb-run, I have reported a bug against the xvfb
package.
Until this is fixed or a workaround known, we cann
Hi Daniel,
1.0.0~rc1 is in Debian unstable now, with the testsuite deactivated for
now. If there are no issues, it'll reach stretch in five days. If any
changes are required to accomodate for the jessie backport, a heads-up
would be appreciated, so we don't have to wait for the testing migration
Control: tags -1 upstream
Control: forwarded -1 https://github.com/borgbackup/borg/issues/669
On Tue, 16 Feb 2016 13:11:19 +0100 Danny Edel wrote:
> I have forwarded this to the upstream bugtracker.
Since the program works as documented in the manpage, the behaviour will
not be changed,
Package: borgbackup
Version: 1.0.0~rc1-2
Severity: wishlist
Tags: patch
Hi Gianfranco, hi Daniel,
I want to re-activate the testsuite of borgbackup, but without the
problems that occured the last time, so I CC'd both of you, I hope
that's all right.
I have prepared a patch, and verified it again
On 02/22/2016 06:46 PM, Gianfranco Costamagna wrote:
> (I'm just wondering: is fakeroot installed by default everywhere?)
> at lest with a pbuilder-dist sid login I don't have it, maybe having in
> build-dependencies
> is better?
>
> we can add it later if needed, ppa and debomatic seems to have
On 02/23/2016 07:31 PM, Daniel Reichelt wrote:
> Interesting. On a current jessie (plain + git/master-testsuite-enabled's
> build-deps from bpo) I get an error about python3.4's unittest not
> recognizing arguments from PYBUILD_TEST_ARGS - see attached build.log.
>
> Which version of libpython3.4-
Package: dspdfviewer
Version: 1.14-2
Severity: serious
Tags: upstream help
Justification: fails to build from source (but built successfully in the past)
On big-endian architectures, dspdfviewer currently fails to build from
source.
The error messages contain the decimal numbers, but "decoding" t
On Sat, 27 Feb 2016 11:02:00 +0100 Danny Edel wrote:
> On big-endian architectures, dspdfviewer currently fails to build from
> source.
I can reproduce this with cowbuilder-dist from the ubuntu-dev-tools
package and the qemu-user-static emulator, with a mips chroot.
However, the proble
Package: ubuntu-dev-tools
Version: 0.155
Severity: important
Hi,
I use cowbuilder-dist as a frontend to qemu-user-static, to track down a
build failure on mips.
the commands I used are:
export UBUNTUTOOLS_DEBIAN_MIRROR=http://10.x.x.x:3142/debian
(Note: this is my local apt-cacher-ng. If I sp
Hello Andreas,
I have had some spare time and spent it on the ball package. I hope
that helps you in getting the package back into Debian.
Some notes regarding the patch:
* I dropped the gcc5.patch, since it created an ambiguous overload of
getline -- Upstream added one themselves in the meanti
On 01/27/2016 04:49 PM, justysia wrote:
> [12.695075] bluetooth hci0: firmware: failed to load
> brcm/BCM43142A0-4ca-2009.hcd (-2)
> Please help me fix it.
> Best regards,
> Justysia
Hello Justysia,
I had the same problem on an Acer Notebook that came with this card
pre-installed.
If you cannot
Control: retitle -1 Block borgbackup migration to stable for now
Hello everyone,
I have thought a lot about this situation and I still think that
blocking migration to stable *for now* is the sensible solution. I do
not want to remove borgbackup from Debian, or keep this blocker alive
indefinite
Hello Antoine,
thank you for your detailed answer. I will try to address inline.
On 01/08/2016 10:45 PM, Antoine Beaupré wrote:
> Borg has actually shown great API stability since it forked from
> Attic. The change that occured was necessary, and was well documented
> in the release notes and th
Hello Andreas, hello list(s),
I tried to reproduce this build failure on a current sid and investigate
a bit. On my machine it outputs the same basic error messages (although
the line numbers in the basic_string template file are a bit different).
I try to quote the error message partially so it
Hello everyone,
after our discussions and the clarifications from anarcat, it seems that
the only sensible way to solve this is by trying to inform the end-user
as much as possible to help her/him make an informed decision whether
they should use the 0.x software or wait for the 1.0 version.
On f
Hi Antoine,
On 01/13/2016 07:50 PM, anar...@debian.org wrote:
> The readme is not quite accurate: *some* borg versions are actually
> compatible across the network. It's only on the 0.29 boundary that there
> is a problem.
Is this[1] wording acceptable? Then I would prepare it for upload as
0.29
On 14/03/16 19:43, Technicien Informatique wrote:
> Hi,
>
> Is there a reason the borgbackup package installs borg in two
> different places (/usr/bin/borg & /usr/bin/borgbackup) ?
>
> I have to say this is a little bit confusing. The documentation says
> you should call "borg", but your packag
On 03/21/2016 11:36 AM, Nicholas Cheng wrote:
> Dear Maintainer,
>
> I installed borgbackup, made a backup of my ~/Documents folder and
> attempted to restore it in another folder I created in my home
> directory. BorgBackup restored a few files before finally stopping.
Hello Nicholas,
I cannot
On 03/22/2016 11:26 AM, Nicholas Cheng wrote:
> # Creating a new test backup The backup went well, there was no
> output indicating an I/O error with the --verbose flag on.
>
> # Mounted the newly created test backup I simply created a folder in
> my home directory named 'test' and mounted the bac
Package: borgbackup
Version: 1.0.0~rc2-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)
On hppa, the borgbackup test suite failed on 1.0.0~rc2-3 [1] but built
successfully on 1.0.0~rc2-1 [2]. This may be a regression in
dependencies, since the dur
Package: borgbackup-doc
Version: 1.0.0~rc2-3
Severity: wishlist
Currently, the package borgbackup-doc does not build 100% reproducible.
The only problem is api.html, which embeds the current date/time and I/O
charset from the buildd. The problem occurs when parsing function
default arguments.
T
On 12/27/2015 02:42 PM, Marc Haber wrote:
> The workaround suggested by upstream seriously is to have all
> incompatible versions of the server installed and having the client
> choose which server to use.
>
> So debian would need to have a borgbackup-0.28 package and a
> borgbackup-0.29 package a
Package: apt-cacher-ng
Version: 0.8.8-1~bpo8+1
Dear Maintainer,
I am getting this message from my apt-cacher-ng cron job:
/etc/cron.daily/apt-cacher-ng:
Error: cannot fetch
http://localhost:3142/acng-report.html?doExpire=Start+Expiration&abortOnErrors=aOe,
HTTP/1.0 404 Not Found
If I log in on
Hi Antoine,
Now that borgbackup is clear to enter and stay in testing again, it may
be time to revisit the backport to stable : )
On 01/09/2016 04:57 PM, Antoine Beaupré wrote:
> from what i understand, there are two dependencies that need to be
> backported:
>
> * setuptools-scm: backported by
On 01/23/2016 09:42 PM, Vincent Blut wrote:
> mix archives created by an unpriviledged user and
> root inside a single backup repository… and it seems borg doesn’t
> like that experiment. :-)
>
> PermissionError: [Errno 13] Permission denied:
> '/mnt/backup/lamella/data/0/6148'
>
> Platform: Linu
On Sun, 20 Nov 2016 13:37:46 +0100 Hilko Bengen wrote:
> after searching for "AC_CHECK_LIB(ssl, SSL_library_init" using
> codesearch.debian.net and rebuilding with OpenSSL 1.1, I found that the
> OpenSSL is no longer detected and thus no longer used when building the
> package.
Hello,
is anyone
On Sun, 08 Mar 2015 10:42:34 -0500 Peter Gallagher
wrote:
> Attempting to install the winrm GEM manually does not change the behaviour.
> The
> DEB package provided at https://www.vagrantup.com/download-archive/v1.6.5.html
> does not display this behaviour and works as expected.
Hello,
I came a
00:00:00 2001
From: Danny Edel
Date: Sun, 10 Apr 2016 11:57:18 +0200
Subject: [PATCH] Rework patches for sid
This fixes FTBFS. Also, enable tests in d/rules.
---
debian/patches/0001-missingSigned.patch| 32 --
.../adjust-PoseClustering_Test-boost-1.58.patch| 13 +++
.../di
On Mon, 11 Apr 2016 17:54:03 +0200 Andreas Tille wrote:
> Did you created a new repository on collab-maint for this purpose?
> It seems you did not used a clone of the packaging Git
>
> git://anonscm.debian.org/debian-med/ball.git
>
Hi Andreas,
sorry for the miswording -- I did use the git rep
On Sat, 9 Jul 2016 23:51:52 +0200 Matthias Klose wrote:
> patch at
> http://launchpadlibrarian.net/271939349/llvm-toolchain-3.8_1%3A3.8.1-2ubuntu1_1%3A3.8.1-2ubuntu2.diff.gz
Hello Matthias,
thank you very much! This patch solves the issue for me, clang++ now
compiles *and* links against abi-tag
On 7/7/20 2:21 AM, John Scott wrote:
> Rebuilding dspdfviewer to see how it would fare with Poppler in
> experimental, I found it FTBFS in unstable unconditionally.
>
> /<>/pdfviewerwindow.cpp: In member function
> ‘void PDFViewerWindow::reposition()’:
> /<>/pdfviewerwindow.cpp:119:89: error: ‘con
65 matches
Mail list logo
