Source: gpscorrelate
Version: 2.1-2
Severity: serious
Hi Shriram,
the test upstream-suite autopkgtest still fails on practically all the
architectures, even after disabling the valgrind support (#1071656):
- https://ci.debian.net/packages/g/gpscorrelate/testing/amd64/48755050/
- https://ci.debian
Source: qt6-base
Followup-For: Bug #1073480
X-Debbugs-Cc: pkg-llvm-t...@lists.alioth.debian.org
Control: reassign -1 llvm-17-dev
Control: severity -1 important
Hi,
after a big of debugging, I think I got to the actual reason for this
failure.
In particular, starting from LLVM 16, there is a ship
Source: amarok
Followup-For: Bug #1074670
X-Debbugs-Cc: pkg-mysql-ma...@lists.alioth.debian.org
Control: reassign -1 src:mariadb mariadb/1:11.4.2-1
Control: retitle -1 please build again the embedded server, needed by amarok
Control: affects -1 + src:amarok
Hi,
this dependency issue happens becau
Control: tag -1 pending
Hello,
Bug #1064672 in virt-manager reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/libvirt-team/virt-manager/-/commit/a8db17eb476ceab2f
Control: tag -1 pending
Hello,
Bug #1042147 in virt-manager reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/libvirt-team/virt-manager/-/commit/35d6d1eeea61ea361
Control: tag -1 pending
Hello,
Bug #1022339 in virt-manager reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/libvirt-team/virt-manager/-/commit/592f0810d6b06c3ce
Package: llvm-14-dev
Followup-For: Bug #1021857
Hi,
(sending properly again)
1:14.0.6-6 does some changes, however it does not fix all of it; this
is while trying to build qtcreator:
CMake Error at /usr/lib/llvm-14/lib/cmake/clang/ClangTargets.cmake:756
(message):
The imported target "diagto
reopen 1021857
thanks
1:14.0.6-6 does some changes, however it does not fix all of it; this
is while trying to build qtcreator:
CMake Error at /usr/lib/llvm-14/lib/cmake/clang/ClangTargets.cmake:756
(message):
The imported target "diagtool" references the file
"/usr/lib/llvm-14/bin/diag
p3guessenc-0.27.5+dfsg.1/debian/changelog 2020-09-20 21:50:00.0
+0200
+++ mp3guessenc-0.27.5+dfsg.1/debian/changelog 2022-09-07 08:12:34.0
+0200
@@ -1,3 +1,12 @@
+mp3guessenc (0.27.5+dfsg.1-2) UNRELEASED; urgency=medium
+
+ [ Pino Toscano ]
+ * Switch from "fgrep&q
Control: tag -1 pending
Hello,
Bug #1008358 in virt-manager reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/libvirt-team/virt-manager/-/commit/b8db30e00024b5a00
Source: lshw
Version: 02.19.git.2021.06.19.996aaad9c7-1
Severity: serious
Justification: reverts past changes
X-Debbugs-Cc: z...@debian.org
Hi,
the upload of lshw 02.19.git.2021.06.19.996aaad9c7-1 was done starting
from 02.18.85-0.5, meaning that neither 02.18.85-0.6 nor 02.18.85-0.7
are acknowle
. I remember having seen this in the past (when I
used to maintain poppler), but it happened once and indeed it was due
to an incomplete dist-upgrade. IMHO this will not happen in
oldstable->stable dist-upgrades, as everything will be build with the
newer libraries, and hopefully the dist-up
w
version suddently breaks software built against old versions of it.
Sorry if I seem harsh: LLVM is a key component in a modern Debian
system, so uploading new versions and providing almost no help on
problems does not seem like a good idea for the distribution.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
In data domenica 27 dicembre 2020 03:53:01 CET, Jonas Smedegaard ha scritto:
> Version: 9.53.3~dfsg-6
>
> Quoting Pino Toscano (2020-12-22 10:08:12)
> > In data lunedì 21 dicembre 2020 18:23:12 CET, Simon McVittie ha scritto:
> > > > On my side, rebuilding libspectr
e included from /usr/include/x86_64-linux-gnu/qt5/QtCore/QProcess:1,
> > from /<>/src/debfile.cpp:24:
> > /usr/include/x86_64-linux-gnu/qt5/QtCore/qprocess.h:168:10: note: declared
> > here
> > 168 | void start(const QString &command, OpenMode mode = ReadWrite);
> > | ^
> > In file included from /usr/include/apt-pkg/deblistparser.h:15,
> > from /<>/src/dependencyinfo.cpp:24:
> > /usr/include/apt-pkg/pkgcachegen.h:32:10: fatal error: xxhash.h: No such
> > file or directory
> >32 | #include
> > | ^~
It looks like a bug in one of the public headers of libapt-pkg, and
already fixed upstream:
https://salsa.debian.org/apt-team/apt/-/commit/ece7f5bb0afee0994a4fb4380e756ce725fe67a9
APT developers: please mark this bug as fixed in changelog.
Thanks,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
it needs a fixed SONAME and a fixed Debian package name matching
it. See also #977649 (which this bug will be merged to).
In the meanwhile, I will disable the kimageannotator-related features,
as at least there will be a functional Spectacle.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
x27;m reassigning this to llvm-toolchain-11, because there is a
behaviour change in the new version, and because its libraries cause too
loose dependencies. In the end, the clazy autopkgtest works properly,
and it looks like it caught actual issues in llvm-toolchain-11.
LLVM maintainers
linking).
https://tracker.debian.org/news/1203963/accepted-clazy-18-2-source-into-unstable/
--
Pino Toscano
kimageannotator0_0.3.2-2_amd64.deb
W: libkimageannotator0: package-name-doesnt-match-sonames
libkImageAnnotator0.3.2
I: libkimageannotator0: no-symbols-control-file
usr/lib/x86_64-linux-gnu/libkImageAnnotator.so.0.3.2
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
.cpp.o: in
> > function `KReportGroupTracker::~KReportGroupTracker()':
> > /usr/include/KReport3/KReportGroupTracker.h:15: undefined reference to
> > `vtable for KReportGroupTracker'
> > collect2: error: ld returned 1 exit status
Ops, I underestimated the symbols loss in kr
retitle 971879 "charset=Ascii" appears before the comment of the image
severity 971879 normal
thanks
In data giovedì 12 novembre 2020 23:33:17 CET, Vincent Lefevre ha scritto:
> On 2020-11-12 22:48:32 +0100, Pino Toscano wrote:
> > This is not how SONAME works, especially in a
e (a) happening, so (b) seems to me the only alternative. Sure,
it is not nice, but meh, not something else to do.
Because of the above, Vincent, what about closing this bug, since there
is nothing actionable in exiv2?
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
hon2 removal in
> sid/bullseye
> Severity set to 'serious' from 'normal'
This bug was already marked py2keep, as it depends only on
src:python2.7, and we want to ship it in the next stable for now
(it is not even fixed upstream).
Hence, lowering its severity to important.
the upstream script used for
testing).
Considering the situation described is already what happens, I'm
lowering the severity, and requesting for more information.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
om a -dev file, please
rebuild the reverse dependencies to check everything still works
(currently kdelibs4support has only 12 users in unstable).
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
I think, and for that reason I've
> marked this bug as Severity grave, "makes the package in question
> mostly unusable"
... I disagree with this statement: the package in question is _not_
mostly unusable.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
lazy 1.7 migrates to testing,
since there is no reason it should be prevented to migrate.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
port DEB_HOST_MULTIARCH=$(dpkg-architecture -qDEB_HOST_MULTIARCH)
-export XDG_RUNTIME_DIR="$AUTOPKGTEST_TMP"
+export XDG_RUNTIME_DIR="$AUTOPKGTEST_TMP/run"
+mkdir -m 700 "$XDG_RUNTIME_DIR"
WORKDIR=$(mktemp -d)
trap "rm -rf $WORKDIR" 0 INT QUIT ABRT PIPE
Package: libmount-dev
Version: 2.35.2-5
Severity: serious
Tags: patch
Justification: Policy 7.2
Hi,
util-linux 2.35.2-5 added support for dm-verify (#951048); apparently
this results in libmount requiring it as private dependency:
$ pkg-config --libs mount
-lmount
$ pkg-config --cflags mou
m pretty sure boost 1.67.0 can stay 3 months more around, especially
since I see it is still not the only package using the old boost.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
close 962172 5.70.0-2
thanks
--
Fixed in 5.70.0-2.
--
Pino Toscano
t; > -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles"
> > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_AUTOGEN_VERBOSE=ON
> > -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. returned exit code 1
> > make: *** [debian/rules:8: build] Error 2
>
> The full build log is availabl
#x27;m demoting the
severity of this bug to important. Also, Paul, please re-enable the
autopkgtest of clazy on ci.debian.net, as they will pass now.
Thanks,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
KDE
libraries/applications.
As I already asked you: Adrian Bunk, please stay away from Qt/KDE
stuff.
Thanks,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
ntime ones. Randomly chopping pieces without
checking what changes, and potentially what breaks, is generally a
big no-no from me. I do not see how "remove qtwebkit" is an excuse to
start messing up with packages, just for the sake of package removal.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
late:
$ reportbug --template kile
>* What was the outcome of this action?
> "kile: error while loading shared libraries: libnepomukutils.so.4:
> cannot open shared object file: No such file or directory"
It sounds like you still have kile 2.1.x installed.
--
Pino Toscano
signature
uld have uploaded it long ago.
I cannot work on it today, maybe tomorrow.
OTOH, this kind of non-helping attitude for you openssl guys (for
example not helping fixing these porting bugs, constant useless poking,
breakage of openssl 1.1 in unstable) certainly does not help.
If you want cooperation, then be ccoperative yourself, instead of just
expecting others to follow whatever you do.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
ugh to fix the build failure with Qt 5.11.
[1] https://savannah.gnu.org/bugs/?53978
[2] https://hg.savannah.gnu.org/hgweb/octave/rev/cdaa884568b1
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
s VCS:
https://salsa.debian.org/qt-kde-team/extras/libqaccessibilityclient
and noticing work on it, including this bug, and the Qt4 bug mentioned
above.
You could have also checked the kde-extras ML for possible uploads:
https://alioth-lists.debian.net/pipermail/pkg-kde-extras/2018-July/029275.ht
mments in
some random forum on the Internet made by some random/anonymous nick.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
in the packaging git, and
possibly I should land one/two more (although I have not worked on them
yet).
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
upstream uses phabricator [1] for patch reviews.
[1] https://phabricator.kde.org/
> I plan to NMU in a week or so and upload to DELAYED/10 unless I hear
> back from you.
I'd rather prefer to get first the feedback from upstream, so we can
possibly even just backport the upstream comm
tly; nobody did anything about that, so the
status is the same as before.
If the openssl maintainers want to get rid of openssl 1.0, why don't
they *cooperate* with *upstream* communities on the migration to the
newer version of openssl? That would certainly help, and surely way
more than useless "please migrate, ktnxbye" nagging.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
ess Ritesh says otherwise, leave this package as it is.
Also, for what it matters, please leave also QtWebKit as it is, since
it is under the Qt/KDE team wing, and removing it requires more work
than occasional people (like this email) think about.
Thanks,
--
Pino Toscano
signature.asc
Descriptio
th a patch for this, or mention some other source that
needed to do the same changes?
Thanks,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
The upload of kremotecontrol 4:17.08.3-1 drop the Plasma parts, so this
bug is back to "just" Qt4 porting concern.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
severity 883100 important
tag 883100 - patch
thanks
Since ksudoku was removed from unstable (and soon testing), this is no
more a blocking issue.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
severity 883626 important
tag 883626 - patch
thanks
Since kubrick was removed from unstable (and soon testing), this is no
more a blocking issue.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
On giovedì 4 gennaio 2018 15:03:38 CET Eric Valette wrote:
> On 01/04/2018 02:25 PM, Pino Toscano wrote:
> > On giovedì 4 gennaio 2018 14:17:59 CET Eric Valette wrote:
> >>> this is a duplicate of bug #850888, since the dependency in the -dev
> >>> package depends
o, what you said is not true, and partially does not make any sense.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
On mercoledì 3 gennaio 2018 20:48:25 CET Adrian Bunk wrote:
> On Wed, Jan 03, 2018 at 07:32:46PM +0100, Pino Toscano wrote:
> > On mercoledì 3 gennaio 2018 20:26:53 CET Adrian Bunk wrote:
> > > On Wed, Jan 03, 2018 at 07:14:58PM +0100, Pino Toscano wrote:
> > > > On
Dear user,
On mercoledì 3 gennaio 2018 14:54:08 CET Eric Valette wrote:
> severity 885111 serious
Please do not bump the severity of bugs with random criterias.
Thanks,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
ached for this.
Thanks.
--
Pino Toscano--- a/debian/control
+++ b/debian/control
@@ -122,7 +122,6 @@ Description: HP Printers PostScript Desc
Package: hplip-gui
Architecture: all
Depends: default-dbus-session-bus | dbus-session-bus,
- gksu | kdebase-bin (<< 4:4.4.0-1) | kde-runti
d phonon-vlc will migrate to testing tomorrow. You can pull it
from unstable, or just temporarily switch to phonon-gstreamer for today.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
crashing. For the moment I
> switched to gstreamer backend.
Do you still have crashes with phonon-backend-vlc 0.9.1-2?
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
d
(since kcalcore was fixed to properly use libical2, see #883921).
Since I don't see any other message in this bug regarding problems,
nor I see any bug filed in any part of the KDE stack, then I'm lowering
the severity of this bug, so this rushed doko-transition can be finally
unblocked (unblocking the marble+libkipi transition too).
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
Source: nomacs
Version: 3.8.0+dfsg-1
Severity: grave
Justification: renders package unusable
Control: block 875026 by -1
Hi,
it seems like nomacs is built against the Qt4 version of the quazip
library (libquazip-dev as build dependency, and links to libquazip1).
Considering nomacs uses Qt5, this
essful run of ktorrent?
> --- System information. ---
Unfortunately, this system information is not useful; please attach
inline the output of `reportbug --template ktorrent`.
Thanks,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
h
Qt 5). Obviously, you cannot use Qt4 plugins in Qt5 applications, and
vice versa.
This will be fixed once kio-audiocd is updated to version >= 17.08;
see also bug #874820.
(BTW: we still ship a dolphin4 package, which is the latest version of
dolphin for kdelibs 4.x; this version is able to u
h easier if you could *wait* for the
completion of Applications 17.08 in unstable/testing, so there will be
few more kdelibs4-using sources either dropped (like dolphin4) or
ported to Frameworks.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
Control: severity -1 important
(see below why...)
In data lunedì 20 novembre 2017 20:05:20 CET, Emilio Pozuelo Monfort ha scritto:
> Control: severity -1 serious
>
> On Wed, 06 Sep 2017 21:34:47 +0200 Pino Toscano wrote:
> > Hi,
> >
> > In data domenica 27 agosto 20
4:17.08.3-1
>
> kde-l10n-sr=4:16.04.3-3 lokalize=4:17.08.3-1
Sigh... OK, let's move this bug to kde-l10n, no point it staying as a
ktuberling bug. I'll fix kde-l10n and the other affected packages
tonight.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
x this in kde-l10n instead.
This affects only people using kde-l10n from experimental, and it will
not be a problem in the long term.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
In data lunedì 13 novembre 2017 12:06:01 CET, Steve Robbins ha scritto:
> On Sunday, November 12, 2017 7:21:30 PM CST Sebastian Ramacher wrote:
>
> > > [ Pino Toscano ]
> > >* Remove manual library and va-driver dependencies. (Closes: #880884)
> >
> >
In data sabato 30 settembre 2017 16:12:19 CEST, Adrian Bunk ha scritto:
> On Sat, Sep 30, 2017 at 02:04:58PM +0200, Pino Toscano wrote:
> > In data sabato 30 settembre 2017 14:55:34 CEST, Adrian Bunk ha scritto:
> >...
> > > Current status quo in Debian is that it is comple
In data sabato 30 settembre 2017 14:55:34 CEST, Adrian Bunk ha scritto:
> On Sat, Sep 30, 2017 at 01:28:54PM +0200, Pino Toscano wrote:
> > In data sabato 30 settembre 2017 13:17:43 CEST, Adrian Bunk ha scritto:
> > > libgpod-nogtk-dev was a transitional package removed
erious bugs on rdeps" modus operandi is *not* a good way of
cooperating with other packagers in Debian.
Filing a bug some time before, or even writing an email, would have
been a much nicer, and cooperative, way.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
Package: libappstreamqt-dev
Version: 0.11.4-1
Severity: grave
Justification: renders package unusable
Control: affects -1 src:frameworkintegration
Control: affects -1 src:plasma-discover
Hi,
in the new version 0.11.4, I guess because of the switch from cmake to
meson, the source got a template fo
e old
baloo libraries. Patching that source honestly requires more work than
what is worth spending.
> Should anyone file a RM request for src:baloo immediately?
No.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
e
> build dependency on libssl-dev completely removed.
That is because it is an optional dependency.
> Lisandro, maybe just dropping the build dependency on libssl-dev would be
> the best option if it's actually not used at all?
NACK.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
s is also a downstream-only issue, due
to the mixup of MariaDB versions currently in testing/unstable, and I
see the KDE bug was rightfully closed as DOWNSTREAM.
Thanks,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
over
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
Debian archive, so please
paste the output of:
$ dpkg -S /usr/lib/x86_64-linux-gnu/qt5/plugins/imageformats/libxfreeimage.so
Is it https://github.com/linuxdeepin/deepin-image-viewer by chance?
Another option is that the issue is in libfreeimage (src:freeimage),
which does not seem to do proper error c
execute
`thread apply all bt`
e) execute `quit` to exit gdb, confirming with yes when asked whether
kill the running application
Please attach/write the full backtrace, with all the threads included.
Thanks,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
build and most probably it was implicitly
pulled by one of the removed packages.
I'll most probably NMU/5 in a week, unless it is fixed before, or there
are objections/issues in NMUing.
Thanks,
--
Pino Toscano--- a/debian/control
+++ b/debian/control
@@ -4,41 +4,19 @@ Maintainer: Patryk Cise
In data lunedì 19 settembre 2016 11:32:18 CEST, John Paul Adrian Glaubitz ha
scritto:
> On 09/19/2016 09:08 AM, Pino Toscano wrote:
> > Looking further at this very issue (#811846), I don't think the
> > solution implemented is actually the correct one:
> >
> >
ut is clearly wrong at the end, where std::endl is most probably
what should be used; there are 5 occurrences of this in xbase64, all of
them in xblock.cpp.
Attached there is an actual patch fixing the issue: please integrate it,
and remove the -std=c++98 workaround.
Thanks,
--
Pino Toscano--
Hi,
what's the status of this bug (xbase64 that FTBFS with GCC 6)?
Because of it, xbase64 was removed from testing a couple of months ago,
and now it will prevent calligra (which ships a sybase access driver
for kexi) to migrate to testing.
Any way I can help with this?
Thanks,
--
Pino To
> regards
> calligra or something like that?
${shlibs:Depends} is the actual sauce of the dependencies: it contains
the list of libraries dependencies of the binaries & libraries in each
binary package. See the man pages of dh_shlibdeps & dpkg-shlibdeps to
know how they are filled, and dh_gencontrol & dpkg-gencontrol to know
how they are used.
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
up the rest of the packaging work
done already. Right now it's building on my machine, and will be
uploaded to NEW afterwards. As above, please do reach me directly for
any change until it's accepted in unstable again.
[1] https://anonscm.debian.org/cgit/pkg-kde/kde-std/krita.git
Regards,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
ecomes older than the current one in unstable...
Thanks,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
).
Before disabling the parallel build, what about trying to backport the
upstream commit 8a5ba082959b8439993f4d731445db12a4c5e301 (in tracker)?
It is also included in the new version 1.9.0, so upgrading to that will
provide that commit too.
--
Pino Toscano
7b76a0cf5b66508c6a89b199b024c5269a882451
Author: Pino Toscano
Date: Mon Apr 25 16:37:13 2016 +0200
fix a crash on invalid files; CVE-2015-8868 (#822578)
backport upstream commit b3425dd3261679958cd56c0f71995c15d2124433
diff --git a/debian/changelog b/debian/changelog
index cc47829..d7f7942 100644
--- a/debian
l log of the build, including all the installed
packages and their versions. Just tried rebuilding elektra in a clean
chroot (using builder), and it build fine.
Thanks,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
ca9d4b24657f8c84e9803d684258474e6672eada
Author: Pino Toscano
Date: Sat Aug 29 10:51:03 2015 +0200
handle new libstc++ ABI of GCC 5 on libpoppler-cpp (#796919)
- rename libpoppler-cpp0 to libpoppler-cpp0v5
- make libpoppler-cpp0v5 conflict/replace libpoppler-cpp0
diff --git a/debian/changelog b/debian
with more recent versions of poppler (0.26.x is not that new
anymore...).
Most probably not something fixable in stable.
Thanks for your report,
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
7929aa2d5ec9464fea755f622319d224787c4110
Author: Pino Toscano
Date: Sat Jul 25 19:34:57 2015 +0200
tighten libpopplerN dependencies (#767659)
diff --git a/debian/changelog b/debian/changelog
index f03b4e9..50bae0a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -5,6 +5,8 @@ poppler (0.26.5-3) UNRELEASED
Source: cg3
Version: 0.9.9~r10439-1
Severity: serious
Tags: patch
Justification: fails to build from source
Hi,
cg3 does not build on Debian buildds.
This is because among the build dependencies there is:
libboost1.48-dev | libboost-dev (>= 1.49.0)
given that on buildds only the first element
Source: apport
Version: 2.15.1-1
Severity: serious
Tags: patch
Justification: fails to build from source
Control: found -1 apport/2.14.2-2
Hi,
apport fails to build in arch-only builds (debian/rules build-arch),
as done e.g. on buildds [1].
This happens because python(3)-distutils and python(3)-
otherwise it is hard to debug such weird setup.
Thanks,
--
Pino Toscano
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
gle-like icon on
its right)
* after running `kgpg`, does the execution gets back to the terminal,
or it stays there?
* run `kdebugdialog`, enable the two areas for kgpg ("2100 kgpg" and
"kgpg") and close it, and try running `kgpg` again; paste the
*full* output here
this is not the right approach.
This bug *only* affects people which have upgraded just parts of
jessie/testing in the last two weeks, without all of it.
As I asked previously: please LET ME FIX IT. I *know* how to fix it,
just had no proper time to do this.
Thanks,
--
Pino Toscano
--
To UNSUB
s NMU, since the approach chosen (bumping shlibs for
everybody) is not correct.
And please leave me the _time_ to fix it... not even asking what is
the right approach, and just firing an NMU not even after one day I
received this bug, does not seem that polite to me.
--
Pino Toscano
--
To UNSUBS
prone to silent breakages.
--
Pino Toscano
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Source: onak
Version: 0.4.5-1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
Hi,
currently onak cannot be built on non-Linux architectures, because of
the systemd (Linux-specific) build dependencies.
Since the features they enable are
Package: iagno
Version: 1:3.14.0-1
Severity: serious
Tags: patch
Justification: Policy 7.6.1, Policy 10.1
Hi,
when upgrading iagno to 1:3.14.0-1 (i.e. today's upgrade in
testing) while gnome-accessibility-themes is still at 3.12.0-1, a file
conflict is reported:
Preparing to unpack .../iagno_1%3
Package: five-or-more
Version: 1:3.14.0-1
Severity: serious
Tags: patch
Justification: Policy 7.6.1, Policy 10.1
Hi,
when upgrading five-or-more to 1:3.14.0-1 (i.e. today's upgrade in
testing) while gnome-accessibility-themes is still at 3.12.0-1, a file
conflict is reported:
Unpacking five-or-m
Package: gnome-mines
Version: 1:3.14.0-1
Severity: serious
Tags: patch
Justification: Policy 7.6.1, Policy 10.1
Hi,
when upgrading gnome-mines to 1:3.14.0-1 (i.e. today's upgrade in
testing) while gnome-accessibility-themes is still at 3.12.0-1, a file
conflict is reported:
Preparing to unpack .
ot part of
DEB_CONFIGURE_EXTRA_FLAGS and thus not passed to configure.
Thanks,
--
Pino Toscano
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 2014-09-14 13:28, Yann Dirson wrote:
On Sun, Sep 14, 2014 at 10:12:41AM +0200, Pino Toscano wrote:
Hi,
first of all, the behaviour of update-mime-database is correct: it
deletes files in *generated* directories.
Yes, the various application, audio, text, subdirectories under
/usr/share
1 - 100 of 182 matches
Mail list logo
