Package: zfs-dkms
Version: 2.2.6-2
Severity: important
Tags: upstream
The build log shows a warning: "kmem_cache_create" redefined so I suspect an
upstream fix is required.
CC [M] /var/lib/dkms/zfs/2.2.6/build/module/os/linux/spl/spl-xdr.o
In file included from /var/lib/dkms/zfs/2.2.6/build/mo
Source: php-dompdf
Version: 3.0.0+dfsg-2
Severity: important
Sometime between November 14 and November 27, the autopkgtest began failing.
The error message is:
44s autopkgtest [21:13:58]: test phpunit: [---
45s phpab %development% - Copyright (C) 2009 - 2024 by Arne Blankerts
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: geomv...@packages.debian.org
Control: affects -1 + src:geomview
User: ftp.debian@packages.debian.org
Usertags: remove
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: digi...@packages.debian.org
Control: affects -1 + src:digikam
User: ftp.debian@packages.debian.org
Usertags: remove
The most recent upstream release of Digikam has made use of Qt Webengine
mandatory. Therefore, Digikam can only be built o
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: m...@packages.debian.org
Control: affects -1 + src:mgt
User: ftp.debian@packages.debian.org
Usertags: remove
This package hasn't had an upstream release since 1996, has few users according
to popcon, and needs work to build with modern com
Package: wnpp
Severity: normal
X-Debbugs-Cc: m...@packages.debian.org
Control: affects -1 + src:mgt
This package hasn't had an upstream release since 1996, so may be
long past its usefulness.
I intend to orphan the mgt package.
The package description is:
Mgt allows the user to examine Go game
Package: nvidia-smi
Version: 535.183.01-1
Severity: normal
A couple months ago, I ran "nvidia-smi" command without issue.
I ran it again today and the machine simply locked up.
Recently, the hard limit of file descriptors was raised for debian:
https://lists.debian.org/debian-devel/2024/06/msg00
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: gri...@packages.debian.org
Control: affects -1 + src:gringo
User: release.debian@packages.debian.org
Usertags: binnmu
nmu gringo_5.6.2-1 . ANY . unstable . -m "Rebuild against updated python3.11
for 64-bit time transition"
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: pstot...@packages.debian.org
Control: affects -1 + src:pstotext
The pstotext package was removed from testing in 2018 due to grave bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: mriconv...@packages.debian.org
Control: affects -1 + src:mriconvert
The functionality of this software is provided by dcm2niix. Upstream has
stopped maintaining the software and provid
Source: passwordsafe
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
I saw autopkgtest failure for passwordsafe
133s /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions
less than C++14 are not supported.
133s 27
Package: libkf5screen8
Version: 4:5.27.0-1
Severity: normal
Tags: patch upstream
This is to note that the upstream bug titled "On X11 with proprietary NVIDIA
GPU drivers, external monitor disabled after reboot or wake-from-sleep" applies
to Debian package 4.27.0-1.
See https://bugs.kde.org/show_b
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: 1013...@bugs.debian.org, 1020...@bugs.debian.org
Note: I'm not technically the maintainer of matrix-mirage, but I didn't see a
more fitting category and it is orphaned.
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: 1004...@bugs.debian.org
See https://github.com/wang-
bin/QtAV/commit/fdc613dc99304f208cff0bb25b3ded14bb993237
Package: libopencv-java
Version: 4.6.0+dfsg-6+b1
Severity: important
This bug makes the build of (unrelated) package libsis-jhdf5-java fail.
$ dpkg --search /usr/share/java/opencv.jar
libopencv-java: /usr/share/java/opencv.jar
$ file /usr/share/java/opencv.jar
/usr/share/java/opencv.jar: broken
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu minc-tools_2.3.00+dfsg-9 . ANY . unstable . -m "rebuild against updated
libminc"
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu elastix_5.0.1-3+b1 . ANY . unstable . -m "Rebuild against updated
insighttoolkit5"
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu insighttoolkit5_5.2.1-5 . ANY . unstable . -m "Rebuild against updated
libminc"
Package: lldb-14
Version: 1:14.0.6-2
Severity: normal
Dear Maintainer,
There is a misconfiguration somewhere in the build, that embeds a non-existent
python path:
$ lldb -P
/usr/lib/local/lib/python3.10/dist-packages
This causes lldb to emit an error when starting:
$ lldb
Traceback (most r
Package: libidn12
Version: 1.40-1
Severity: important
Dear Maintainer,
I had version 1.38-4 installed until I ran apt upgrade today. After the
upgrade, mail that originated
outside of my system seems to vanish. The mail logs show a normal delivery (by
postfix). But kmail shows
no sign of the
Package: ftp.debian.org
Severity: normal
The ITK v5 package only builds for amd64, so the elastix i386 binaries need
removing to allow it to get to testing.
At least that's how I understand the excuse output
https://qa.debian.org/excuses.php?package=elastix
Thanks,
-Steve
Package: kmail
Version: 4:20.08.3-1
Severity: normal
Dear Maintainer,
Today KMail decided to colour unread messages (in the message list) bright
pink. It was not pink previously.
-Steve
-- System Information:
Debian Release: 11.0
APT prefers testing
APT policy: (500, 'testing'), (200, 'u
Package: debianutils
Version: 5.0.1-1
Severity: important
Dear Maintainer,
The /etc/XSession script uses tempfile, so removal of that package breaks
logging into X.
-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (200, 'unstable')
Architecture: amd64 (x86_64)
F
Package: git-buildpackage
Version: 0.9.22
Severity: normal
File: /usr/lib/python3/dist-packages/gbp/scripts/supercommand.py
Dear Maintainer,
I attempted to import a new version into 'experimental' branches using: "gbp
import-orig --pristine-tar --upstream-branch=upstream-experimental
--debian-b
Package: samba-common-bin
Version: 2:4.13.2+dfsg-2+b1
Severity: important
Dear Maintainer,
Install failed as follows. This was a second attempt so apt reports samba
"already the newest version".
But the first attempt had the same errors about /run/samba; I would have
expected one of these pa
Source: seqan3
Severity: normal
Dear Maintainer,
The autopkg tests need to be updated for the new googletest. There are
failures such as
/tmp/autopkgtest-lxc.u2mymoo7/downtmp/autopkgtest_tmp/unit/alphabet/cigar/../alphabet_test_template.hpp:86:
Failure
Type parameterized test suite alphabet i
Source: ms-gsl
Severity: normal
Dear Maintainer,
A new version of googletest has been uploaded and shortly thereafter I received
word that ms-gsl autopkgtest has failed on arm64. See https://ci.debian.net/
data/autopkgtest/testing/arm64/m/ms-gsl/7637851/log.gz
The error in that log looks like
Source: seqan
Severity: normal
Dear Maintainer,
Hi,
Just uploaded a newer googletest and seqan is reporting autopkgtest failures.
However, at least some failures appear to be due to changes in googletest that
require
adapting the test code. For example, the following [from
https://ci.debian
Package: libdcmtk-dev
Version: 3.6.4-2.1+b1
Severity: normal
Dear Maintainer,
I just attempted to install libcharls-dev, which failed:
E: /var/cache/apt/archives/libcharls-dev_2.1.0+dfsg-1_amd64.deb: trying to
overwrite '/usr/lib/x86_64-linux-gnu/libcharls.so', which is also in package
libdc
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
New upstream, new soversion.
Ben file:
title = "exiv2";
is_affected = .depends ~ "libexiv2-14" | .depends ~ "libexiv2-27";
is_good = .depends ~ "libexiv2-27";
is_bad = .depends ~ "libex
Package: kmail
Version: 4:17.12.3-1
Severity: normal
In the folder list, KMail is able to display several columns: Name,
Unread, Total, and Size. I have turned off all but Name.
Kmail regularly seems to ignore my wishes and displays all four
columns when I re-start. But this does not happen all
gency=medium
+
+ * Non-maintainer upload
+ * Update build-deps for googletest. Closes: #897171.
+
+ -- Steve M. Robbins Tue, 01 May 2018 22:59:58 -0500
+
synergy (1.8.8-stable+dfsg.1-1) unstable; urgency=low
* New upstream version.
diff -Nru synergy-1.8.8-stable+dfsg.1/debian/control sy
On Sun, Apr 29, 2018 at 07:41:26AM -0500, Steve M. Robbins wrote:
> 1. Modify the build to look for headers in /usr/src/googletest.
Below is a patch to achieve this.
--- meson-0.46.0.orig/mesonbuild/dependencies/dev.py2018-03-03
16:02:02.0 -0600
+++ meson-0.46.0/mesonbu
On Sun, Apr 29, 2018 at 01:36:08PM +0200, David Kalnischkies wrote:
> Not really knowledgeable enough about cmake through to know if that is
> the best we can do ??? it looks kinda ugly/dirty.
Your patch looks fine to me. A slight improvement below avoids
repeating the /usr/src path.
> We cou
Package: src:cctz
Severity: serious
Justification: fails to build from source (but built successfully in the past)
control: block 897104 by -1
Hi,
The googletest package provides full sources -- including header files
-- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of
the hea
Package: src:fmtlib
Severity: serious
Justification: fails to build from source (but built successfully in the past)
control: block 897104 by -1
Hi,
The googletest package provides full sources -- including header files
-- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of
the h
Package: src:meson
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
The googletest package provides full sources -- including header files
-- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of
the headers was mistakenly installe
Package: src:synergy
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
The googletest package provides full sources -- including header files
-- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of
the headers was mistakenly instal
Package: src:aff4
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
The googletest package provides full sources -- including header files
-- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of
the headers was mistakenly installed
Hi,
The googletest package provides full sources -- including header files
-- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of
the headers was mistakenly installed into /usr/include.
All the listed packages rely on this behaviour and now fail to build
since googletest version 1
Package: src:flightcrew
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Subject: Package erroneously expects googletest headers in /usr/include
Package: apt
Version: 1.6.1
Severity: serious
Justification: fails to build from source (but built succes
Package: src:protobuf
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
The googletest package provides full sources -- including header files
-- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy of
the headers was mistakenly insta
Package: apt
Version: 1.6.1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
control: block 897104 by -1
Hi,
The googletest package provides full sources -- including header files
-- in /usr/src/googletest. Prior to version 1.8.0-9, a second copy
Source: ros-catkin
Version: 0.7.11-1
Severity: serious
Justification: fails to build from source
Debian's googletest package used to ship only sources, not a compiled
libgtest. The ros-catkin package has a build-dep on libgtest-dev.
However: at build time libgtest is probed for, not found, and C+
* Non-maintainer upload.
+ * Tweak 00-tests.patch to ignore system libgtest (Closes: #895707)
+
+ -- Steve M. Robbins Sat, 14 Apr 2018 18:20:28 -0500
+
gumbo-parser (0.10.1+dfsg-2.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru gumbo-parser-0.10.1+dfsg/debian/patches/00-tests.patch
On Fri, Mar 23, 2018 at 03:52:38PM +0100, Nicolas Dandrimont wrote:
> I've looked at the upstream history, but this source file has been imported
> as-is in SVN 7 years ago and hasn't been touched since, therefore I couldn't
> find the upstream rationale for this resolution order.
Did you ask ups
Package: fenics
Version: 1:2017.1.0.1
Severity: minor
Hi,
I tried to install the Suggested and Recommended packages, but found two are
non-existent.
python-scitools: appears to have existed at one time, but now removed from
Debian; see
https://packages.qa.debian.org/s/scitools/news/20160506T0
Package: lintian
Version: 2.5.66
Severity: normal
I agree with suggestion by Niels Thykier (on debian-devel):
Andrey Rahmatullin:
> On Mon, Jan 01, 2018 at 05:26:35PM +, Sean Whitton wrote:
>> IMO the point of the field is to ensure that you /don't/ have to upgrade
>> to the latest version of
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu berkeley-express_1.5.1-3 . ANY . unstable . -m "Rebuild with current Boost
libraries"
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unsta
On Tue, Oct 24, 2017 at 02:04:44PM +0100, Dimitri John Ledkov wrote:
> On 24 October 2017 at 04:00, Steve M. Robbins wrote:
> > If I re-enable the doc packages and build, lintian spews dozens of
> > errors of three kinds: privacy-breach-logo, privacy-breach-generic,
> >
On Sun, Apr 23, 2017 at 11:55:15AM +0200, Klaus-J. Wolf wrote:
> Package: libboost1.62-doc
> Version: 1.62.0+dfsg-4
> Followup-For: Bug #844268
>
> Dear Maintainer,
>
> I have observed that the actual documentation is completely missing in
> this documentation package. In duplicate bug report #8
Package: wnpp
Severity: wishlist
Owner: "Steve M. Robbins"
* Package name: libmediawiki
Upstream Author : Team maintained; see
https://github.com/KDE/libmediawiki/blob/master/AUTHORS
* URL : https://cgit.kde.org/libmediawiki.git
* License : GPL
Programmi
gelog
@@ -1,3 +1,11 @@
+kino (1.3.4-2.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+
+ * Use distinct document names for doc-base (Closes: #727148).
+
+ -- Steve M. Robbins Tue, 15 Aug 2017 23:07:19 -0500
+
kino (1.3.4-2.2) unstable; urgency=medium
* Non-maintainer upload.
di
Source: boost1.61
Severity: grave
Package has been superceded by later Boost. Should not be in testing.
In fact, was removed from testing earlier [1] but returned because I
did not file this bug soon enough. Package is also marked for removal
from unstable [2].
-Steve
[1] https://packages.qa.de
Package: ftp.debian.org
Severity: normal
Hi,
This package was removed from testing during a transition to boost1.62
[1] but was mistakenly re-introduced into testing recently. Please
remove the package from the archive -- both unstable and testing.
[1] https://packages.qa.debian.org/b/boost1.61
Package: python-dolfin
Version: 2016.2.0-2
Severity: normal
The second tutorial script 'ft02_poisson_membrane.py' [1] fails to run because
the
python module 'mshr' is missing:
$ python ft02_poisson_membrane.py
Traceback (most recent call last):
File "ft02_poisson_membrane.py", line 12, in
Package: python-sfepy
Version: 2016.2-2
Severity: normal
I tried to run the examples using:
sfepy-run simple examples/diffusion/poisson_short_syntax.py
and obtained:
sfepy: left over: ['verbose', '__builtins__', '__file__', '__doc__',
'__name__', 'data_dir', '__package__', '_filename']
s
On Wednesday, December 21, 2016 1:30:39 PM CST Lisandro Damián Nicanor Pérez
Meyer wrote:
> Well, the FRP was not done by a team member nor, as far as I know, anyone
> one the team is thinking in packaging it.
>
> I'm CCing the RFP bug to see if he's still interested in packaging it. El se
> I w
Peter,
You raise a lot of interesting questions about the general handling of
DEB_BUILD_OPTIONS in the various tools. I haven't got any real answer for the
general question -- and, truthfully, your questions lead me to think it needs
to be considered on a case-by-case basis -- so I'd like to c
On Monday, December 12, 2016 10:57:20 AM CST Peter Pentchev wrote:
> On Sun, Dec 11, 2016 at 08:22:09PM -0600, Steve M. Robbins wrote:
> > Alternatively: if the logic was all in dh (to skip both dh_auto_test
> > and override_dh_auto_test), then it would not need to be in
> >
I, too, think this would be a valuable addition.
On Tue, Feb 09, 2010 at 02:38:34PM -0500, Joey Hess wrote:
> If I did this, I would need to also make override_dh_strip to be
> skipped when DEB_BUILD_OPTIONS=nostrip.
Yes, would also be nice.
> One reason to dislike this is it would mean redun
Control: retitle -1 gtest-port_test fails on m68k
On Friday, December 9, 2016 12:40:59 PM CST David Kalnischkies wrote:
> On Wed, Dec 07, 2016 at 11:28:09PM -0600, Steve M. Robbins wrote:
> Given that this is proven to be false by now I think we can all move on
> more or less pretending
Hi,
Executive summary: the build failures are mostly solved -- save for one test
failure on m68k.
On Thursday, December 1, 2016 1:16:43 PM CST David Kalnischkies wrote:
> So @googletest maintainers, please state what you can/want to do about
> it or not. Being a build-dependency of apt provide
On Tue, Nov 29, 2016 at 04:32:21PM +0100, Thorsten Alteholz wrote:
> building the alljoyn packages (alljoyn-core-1504, alljoyn-core-1509,
> alljoyn-core-1604) with googletest and gcc-6 gives the following compile
> error. I guess the "#include " jusst needs to be replaced by
> "#include " for gcc-
Thanks Adam + Aurelien,
On Saturday, November 26, 2016 3:11:21 PM CST Aurelien Jarno wrote:
> On 2016-11-26 11:02, Adam D. Barratt wrote:
> > On Sat, 2016-11-26 at 01:02 -0600, Steve M. Robbins wrote:
> > > I don't know how to make sense of these "breaks" version
Package: libc6
Version: 2.24-7
Severity: normal
Tried to install libc6:i386 but cannot.
$ sudo apt-get install libc6:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an
Package: ftp.debian.org
Severity: normal
The binaries produced by source package gtest are now produced by
source package googletest. So the former is obsolete and can be
removed.
Thanks,
-Steve
On Sunday, November 20, 2016 1:13:32 PM CST David Kalnischkies wrote:
> On Sat, Nov 19, 2016 at 10:06:17PM -0600, Steve M. Robbins wrote:
> > On Fri, Nov 18, 2016 at 01:29:07PM +0100, David Kalnischkies wrote:
> > > You should also update your README.Debian and the descriptions
On Wednesday, November 16, 2016 9:11:56 AM CST you wrote:
> On 16/11/16 06:49, Steve M. Robbins wrote:
> > On Tuesday, November 15, 2016 2:05:27 PM CST Simon Frei wrote:
> >> I second this request. Please make konqueror a suggested package instead
> >> of a recommended
Hi,
On Mon, Jul 04, 2016 at 05:51:20PM -0700, Afif Elghraoui wrote:
> Package: src:gtest
> Version: 1.7.0-4
> Severity: important
The googletest package has recently been updated to 1.8.0
and built with gcc 6. So I expect this issue is gone, but
I'd like you to test it and let me know because I
On Wednesday, November 16, 2016 12:16:22 PM CST Thibaut Paumard wrote:
> Control: tags 844490 +pending
> Control: severity 844495 normal
>
> For the record, the bug appears when doing:
>
> acos(cos(alpha100)*cos(delta100));
>
> where the type of alpha100 and delta100 is
> boost::multiprecision::
On Fri, Nov 18, 2016 at 01:29:07PM +0100, David Kalnischkies wrote:
> libgtest-dev contains in 1.8.0-1 a symlink to the new on-disk location.
> That works for new installs, but doesn't on upgrades ??? a user ends up
> with an empty /usr/src/gtest in that case. You need to work with
> maintainersc
On Tuesday, November 15, 2016 2:05:27 PM CST Simon Frei wrote:
> I second this request. Please make konqueror a suggested package instead
> of a recommended. Digikam is aiming to be a cross-platform/-DE
> applications, especially since version 5 where many parts have been
> ported to QT from KDE fr
On Tuesday, November 15, 2016 1:02:10 AM CST Santiago Vila wrote:
> Package: librospack-dev,libgtest-dev,src:ros-image-common
> Severity: serious
>
> Dear maintainer:
>
> I tried to build ros-image-common in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do
On Thu, Oct 20, 2016 at 07:13:38PM +0900, Nobuhiro Iwamatsu wrote:
> Source: digikam
> Version: 5.2.0-1
> Severity: important
> Justification: fails to build from source
>
> Dear Maintainer,
>
> I am scheduled to transition of opencv.
>https://release.debian.org/transitions/html/auto-opencv.h
On Wed, Jul 06, 2016 at 08:38:14PM +0200, Luc Castermans wrote:
> I observe similar behaviour, also with CPU remaining at 100%. Below I used
> strace(). You can see
> I needed to kill the process to get rid of it.
Was this with Digikam version 4.4.0, as the original poster?
-Steve
signature.a
On Sat, Sep 17, 2016 at 09:50:12PM +0200, Eike von Seggern wrote:
> after installing digikam with kipi-plugins on a non-KDE system, I cannot
> export files via 'Export->Export to remote storage'. On stderr, I get
> messages similar to:
> "klauncher not running"
> "no service file for klauncher
On Thursday, November 10, 2016 8:20:12 PM CST you wrote:
> I had the same issue on my setup.
> Installing kipi-plugins package solved the problem for me.
> Shouldn't kipi-plugins be in dependencies of digikam package?
Thank you! I un-installed kipi-plugins and now I can reproduce the problem.
On Wednesday, November 2, 2016 12:46:41 PM CDT Khoyo wrote:
> Package: libboost-python1.62.0
>
> Version: 1.62.0+dfsg-2
>
> This fails with libboost-python 1.62, but works with 1.61:
>
> % g++ -I/usr/include/python3.5m/ conftest.cc -lboost_python-py35
> -lpython3.5m /tmp/cc6JvhrE.o: In function
Hi Martin & Simon,
In my testing yesterday, I found that before the "fix", NONE of my video
files played on digikam. After I built with ENABLE_MEDIAPLAYER=ON, then
at least some of my videos played. But not all of them.
I wanted to ask whether this matches your experience.
On Tue, Nov 01, 20
Control: tags + moreinfo
On Wednesday, October 26, 2016 12:12:05 AM CDT you wrote:
> Package: digikam
> Version: 4:5.2.0-2
> Severity: normal
>
> In the top menubar the Export dropbdown menu does not open. It gets selected
> as all the other menus, but nothing is shown. This also happens on a cle
My understanding is that you have to first build boost with the
pie-enabled compiler chain, then build your package with the new
boost.
c.f. https://wiki.ubuntu.com/SecurityTeam/PIE
Note that using -fPIC on static libs is against current Debian Policy.
-Steve
On Mon, Oct 24, 2016 at 08:19:13P
On Mon, Sep 12, 2016 at 01:18:32AM +0200, Balint Reczey wrote:
> /usr/bin/ld:
> /usr/lib/gcc/x86_64-linux-gnu/6/../../../../lib/libPapyrus3.a(PapyError3.c.o):
> relocation
> R_X86_64_32 against `.rodata.str1.8' can not be used when making a
> shared object; recompile with -fPIC
> ...
The Ubuntu
On Mon, Sep 12, 2016 at 01:18:32AM +0200, Balint Reczey wrote:
> During a rebuild of all packages in sid, gdcm
> failed to build on amd64 with patched GCC and dpkg. The root
> cause seems to be that libPapyrus3.a is shipped as a non-PIC library.
That cannot be the root cause. Debian Policy [1] i
Hello Nobuhiro,
On Thursday, October 20, 2016 7:13:38 PM CDT you wrote:
> I am scheduled to transition of opencv.
>https://release.debian.org/transitions/html/auto-opencv.html
> This package is target to transition. I tested build with opencv 3.1.
Thanks for checking the build!
In the lo
On Sunday, October 16, 2016 11:48:32 AM CDT Paul Wise wrote:
> On Sun, Oct 16, 2016 at 10:24 AM, Steve M. Robbins wrote:
> > My suggestion is that the ones with "snapshots" in the path are simply
> > filtered out from list displayed by the reflector as these are not
>
Package: qa.debian.org
Severity: normal
The uscan download from sourceforge doesn't download what you expect
for boost. The reason is that the link provided by the reflector page
[1] is incorrect: it leads to a "snapshot" url [2]. The correct
URL is [3].
Paul Wise indicated [4] that the reflect
Hello,
Thanks for the bug report.
On Saturday, October 15, 2016 3:35:24 PM CDT you wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'jessie'.
The output you quoted doesn't indicate WHY it was to be removed. Do you know?
> # ok, lets try to install it in str
Package: ftp.debian.org
Severity: normal
Thanks,
-Steve
On Monday, September 26, 2016 1:35:52 PM CDT you wrote:
> I attach the patch against the current svn, maybe it helps.
Yes, that's fantastic, thanks! Just applied it to SVN. Hope to have the
debian upload done shortly.
-Steve
signature.asc
Description: This is a digitally signed message part
On Saturday, September 24, 2016 11:28:43 PM CDT Evgeny Kapun wrote:
> Package: libboost1.61-doc
> Version: 1.61.0+dfsg-2.1
>
> The package libboost1.61-doc is supposed to include Boost documentation. It
> doesn't.
Yes, unfortunately. My best advice to you is use the online docs at http://
www.b
On Sunday, September 18, 2016 10:51:16 AM CDT Ghislain Vaillant wrote:
> > but it is in conflict with the well-established standard way
> > of how libraries are distributed in Debian.
>
> This is incorrect. Header-only libraries are present in the Debian
> archive, such as libboost-dev or libei
Package: wnpp
Severity: wishlist
Owner: "Steve M. Robbins"
* Package name: itktools
Version : 0.3.2
Upstream Author : Marius Staring, Stefan Klein, David Doria
* URL : https://github.com/ITKTools/ITKTools
* License : Apache 2.0
Programmi
Hi,
I'll switch it back shortly.
On Friday, August 12, 2016 7:37:33 PM CDT Mattia Rizzolo wrote:
> for some reason you swapped your build-dependency on the metapackage
> libboost-graph-dev to the versioned libboost-graph1.60-dev.
Here's the story: I worked on digikam 5.0.0 a month ago, when the
Package: libpng-tools
Version: 1.6.24-1
Severity: normal
Cannot co-install with pngtools:
Preparing to unpack .../libpng-tools_1.6.24-1_amd64.deb ...
Unpacking libpng-tools (1.6.24-1) over (1.6.23-1) ...
dpkg: error processing archive
/var/cache/apt/archives/libpng-tools_1.6.24-1_amd64.deb (--un
On Wednesday, August 3, 2016 10:59:30 PM CDT you wrote:
> Hi,
>
> First a big thanks at Steve for packaging digikam!
> I proposed an information on the welcome page about the configuration
> transition. I hope this is included before 5.1.0:
> https://bugs.kde.org/show_bug.cgi?id=364258#c18
Thank
Help me reproduce the problem. I can't find "alljoyn" sources:
steve@riemann{NMU}apt source alljoyn
Reading package lists... Done
E: Unable to find a source package for alljoyn
-Steve
signature.asc
Description: This is a digitally signed message part.
On Monday, July 11, 2016 5:38:52 PM CDT Lisandro Damián Nicanor Pérez Meyer
wrote:
> On domingo, 10 de julio de 2016 2:01:04 P. M. ART Steve M. Robbins wrote:
> > Hi,
> >
> > I wanted to make people aware that I have uploaded Digikam 5.0.0 packages
> > to Debian earli
Hi,
I wanted to make people aware that I have uploaded Digikam 5.0.0 packages to
Debian earlier today.
I uploaded to experimental for staging for a few reasons:
1. To work through the build issues on various architectures.
2. The configuration files are in a new location, but digikam does no
On Sunday, July 10, 2016 5:07:08 PM CDT you wrote:
> Package: digikam
> Version: 4:4.14.0-5+b1
> Severity: normal
>
> Dear Maintainer,
>
> Digikam is missing a dependancy on libjasper. Without this package
> installed, it will not start:
>
> digikam: error while loading shared libraries: libjasp
1 - 100 of 1200 matches
Mail list logo
