Package: kdm
Version: 4:4.4.5-7+squeeze1
Severity: normal
After enabling plymouth with the squeeze theme, to the delight of
the user of a laptop, with uvesafb (due to her requirement of the
fglrx drivers for X proper), kdm doesn’t start any more.
This is related to the following bug in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Hi,
I’m the new maintainer of CVS in Debian. The package has been
totally replaced by a new one, which differs quite a lot from
the old package. For example, no repositories are managed au-
tomatically any more, PAM is gone, Kerberos is there (but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Hi,
I’m the new maintainer of CVS in Debian. The package has been
totally replaced by a new one, which differs quite a lot from
the old package. For example, no repositories are managed au-
tomatically any more, PAM is gone, Kerberos is there (but
2012-02-25 16:52:05.0 +0100
@@ -1,3 +1,10 @@
+qt4-x11 (4:4.7.4-2+m68k.1) unreleased; urgency=low
+
+ * Apply patch from upstream bugtracker to fix FTBFS with generic arch
+and possibly sparc64. (Closes: #647265) (Closes: #660963)
+
+ -- Thorsten Glaser t...@mirbsd.de Sat, 25 Feb 2012 15
Pino Toscano dixit:
please attach the output of this last readelf command.
52: 853010 FUNCGLOBAL DEFAULT 13 _Z13f_size_t_typej
53: 856210 FUNCGLOBAL DEFAULT 13 _Z15f_quintptr_typej
54: 854410 FUNCGLOBAL DEFAULT 13 _Z14f_int64_t_typex
55:
Hi,
just to reconfirm, this patch is still needed in 4:4.8.1-1 so
please apply.
Thanks,
//mirabilos
--
15:41⎜Lo-lan-do:#fusionforge Somebody write a testsuite for helloworld :-)
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
+builtins (from debian-ports GCC) like avr32 (Closes: #660963)
+
+ -- Thorsten Glaser t...@mirbsd.de Sun, 29 Jul 2012 21:33:38 +0200
+
qt4-x11 (4:4.8.2-1) unstable; urgency=low
* New upstream release.
diff -Nru qt4-x11-4.8.2/debian/patches/m68k.diff
qt4-x11-4.8.2/debian/patches/m68k.diff
Package: kde-window-manager
Version: 4:4.8.4-3
Severity: serious
Justification: Policy 7.4
Hi,
there’s a file conflict that aborts the dist-upgrade into a state
that needs manual intervention (dpkg --purge --force-all, then
apt-get -f install, etc).
Preparing to replace kde-window-manager
Package: konqueror
Version: 4:4.8.4-1
Severity: serious
Justification: Policy 7.4
Hi,
second conflict that aborted the dist-upgrade:
Preparing to replace konqueror 4:4.6.5-1 (using
.../konqueror_4%3a4.8.4-1_amd64.deb) ...
Unpacking replacement konqueror ...
dpkg: error processing
Pino Toscano dixit:
second conflict that aborted the dist-upgrade:
When did you dist-upgrade last?
Several weeks ago.
Say hello to checking BTS beforehand.
Oh, sorry. My apologies, I’ve indeed not checked that
for this bugreport. Must have been the heat.
bye,
//mirabilos
--
“Having a
@@ -1,3 +1,9 @@
+qt4-x11 (4:4.8.2+dfsg-3+m68k.2) unreleased; urgency=low
+
+ * Add atomics glue for m68k, reusing avr32 support (Closes: #660963).
+
+ -- Thorsten Glaser t...@mirbsd.de Sun, 25 Nov 2012 16:33:39 +0100
+
qt4-x11 (4:4.8.2+dfsg-3) unstable; urgency=medium
* Apply disable-SSL
Dixi quod…
My kde-workspace build is at 80% so I’ll likely follow up
with another screenshot.
So, enjoy kde-plasma-desktop with kdepim (and I’m only about
three more source package builds, two of which have started,
removed from having kde-standard installable). (FSVO enjoy;
I personally am
Ivo De Decker dixit:
I tried on amd64 with pbuilder in wheezy and sid, and manually in a clean
sid chroot (running debian/rules build-arch ; debian/rules binary-arch). Those
3 runs finished without failures.
My guess is that the lines that say
Package: knode
Version: 4:4.10.2-1
Severity: serious
Tags: experimental
Justification: uninstallable
When trying to upgrade KDE from sid to experimental
(by means of installing the metapackages kde-full
kde-plasma-desktop kdepim) I got a missing Replaces:
Preparing to replace knode
Lisandro Damián Nicanor Pérez Meyer dixit:
This package will dissapear (or become a transitional package) with KDE 4.10.
It's being superseded by print-manager_4.10.2-1.
Oh good, thanks! Will try that next.
bye,
//mirabilos
--
“It is inappropriate to require that a time represented as
fail
moc: /«PKGBUILDDIR»/obj-m68k-linux-gnu/kfilereplace/knewprojectdlgs.h: No such
file
The file is apparently attempted to be generated, has empty
content and is then deleted instead of created as zero-length,
if this is the same problem I saw elsewhere in qt/kde stuff.
--
To UNSUBSCRIBE,
Thiago Macieira dixit:
[…]
That means xcb-xkb is missing. You should make sure it's present.
[…]
Please install xkbcommon's development files to avoid the depending on the
bundled copy, which can't be upgraded without upgrading Qt itself.
I built this in a clean, minimal chroot with only the
Lisandro Damián Nicanor Pérez Meyer dixit:
Congratulations! Please add this info to the bug report and please point to
the correct patch in it (marking it as patch available is a plus too).
The bugreport is already
Tags: confirmed, patch
The correct patch to use is:
Source: qtwebkit
Severity: wishlist
Hi,
as Lisandro asked, here’s a bugreport that m68k should please
be added to the list of architectures that don’t build full
debugging information due to memory and time to link the
shared libraries becoming insane then.
Thanks,
//mirabilos
--
Support mksh
Source: qtwebkit-opensource-src
Severity: wishlist
Hi,
as Lisandro asked, here’s a bugreport that m68k should please
be added to the list of architectures that don’t build full
debugging information due to memory and time to link the
shared libraries becoming insane then.
Thanks,
//mirabilos
--
Lisandro Dami�n Nicanor P�rez Meyer dixit:
Thanks Thorsten! Anyway this build log should be now in the backports archive,
No, it’s not in backports. And not in debian-ports either.
so it will get downloaded by getbuildlogs next time I update the package. The
It won’t.
There is currently no
Source: qtjsbackend-opensource-src
Version: 5.1.1-1
Severity: important
Justification: fails to build from source (and was never built before)
cd mkv8snapshot/ ( test -e Makefile || /usr/lib/m68k-linux-gnu/qt5/bin/qmake
http://buildd.debian-ports.org/status/fetch.php?pkg=kdepimlibsarch=m68kver=4%3A4.11.5-4stamp=1391599601
symbol file mismatch:
_ZTIN5boost16exception_detail10clone_baseE@Base
_ZTSN5boost16exception_detail10clone_baseE@Base
_ZTVN5boost16exception_detail10clone_baseE@Base
not provided on m68k (our
Lisandro Damián Nicanor Pérez Meyer dixit:
The build logs are available in http://buildd.debian-ports.org, so be sure
that the next upload will include fixed symbols files. Except an unwanted
omission, we always get and process the symbols from the ports too.
Okay, wonderful, thanks!
bye,
On Fri, 9 May 2014, Thorsten Glaser wrote:
a bunch of HTML crap inside it. See attached screenshot. I’ve
Turns out I had Rich Text editing enabled (forgot to re-disable
after using it exactly *once*). But still… setting an external
editor should probably disable that implicitly.
bye
Package: kmail
Version: 4:4.12.4-1
Severity: normal
Hi *,
if sending an Inline PGP message from an MUA which sets the header
charset to ASCII (see #754262 for an example), Kontact/KMail wrongly
uses the MIME header as charset/encoding indicator for the PGP body.
This is wrong: with Inline PGP,
Hi krfb maintainers,
you might want to have a look at this, and patch krfb to not
produce such invalid packets any more.
-- Forwarded message --
From: Dominik George n...@naturalnet.de
Message-ID: 20140721115759.14202.10015.report...@dgeorg.lan.tarent.de
Package: avahi-daemon
Package: kontact
Version: 4:4.13.3-1
Followup-For: Bug #751753
Hi,
this still happens with 4:4.13.3-1, which is a tad annoying
because of the ABI change in libkontactinterface4a…
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
# bug also found on x32 in…
found 754265 4:4.11.5-1
# bug also found on i386 in…
found 754265 4:4.13.3-1
thanks
Hi,
this bug is still occurring. It is not good for using Kontact
in an enterprise environment. (My coworkers are bugging me for
writing mails with “weird characters”.) This also
Source: kde4libs
Version: 4:4.14.0-1
Severity: normal
Tags: patch
Hi,
please find the patch below to update the symbols files.
Thanks!
--- alt/libkde3support4.symbols 2014-08-20 05:25:38.0 +0200
+++ neu/libkde3support4.symbols 2014-09-03 02:48:30.0 +0200
@@ -1316,7 +1316,8 @@
found 760333 4:4.14.1-1
thanks
Still fails:
http://buildd.debian-ports.org/status/fetch.php?pkg=kde4libsarch=x32ver=4%3A4.14.1-1stamp=1410954066
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: kate-data
Version: 4:4.14.1-1
Severity: serious
Justification: Policy 7.6.1
Unpacking kate-data (4:4.14.2-1) over (4:4.14.1-1) ...
dpkg: error processing archive
/var/cache/apt/archives/kate-data_4%3a4.14.2-1_all.deb (--unpack):
trying to overwrite
-10-24
18:05:49.0 +0200
@@ -1,3 +1,10 @@
+qt4-x11 (4:4.8.6+git64-g5dc8b2b+dfsg-2+x32.1) unreleased; urgency=medium
+
+ * Reapply patch from Daniel Schepler
+ * Refresh these patches
+
+ -- Thorsten Glaser t...@mirbsd.de Fri, 24 Oct 2014 18:05:39 +0200
+
qt4-x11 (4:4.8.6+git64-g5dc8b2b
: #760333)
+
+ -- Thorsten Glaser t...@mirbsd.de Fri, 24 Oct 2014 21:05:42 +0200
+
kde4libs (4:4.14.2-3) unstable; urgency=medium
* Manually fix symbols files.
diff -Nru kde4libs-4.14.2/debian/libkde3support4.symbols
kde4libs-4.14.2/debian/libkde3support4.symbols
--- kde4libs-4.14.2/debian
On Fri, 24 Oct 2014, Thorsten Glaser wrote:
I’ll start a build now and mail back later.
Builds fine, please apply ;)
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID
Lisandro Damián Nicanor Pérez Meyer dixit:
The patch won't work because on the next upload we will be using the system's
double-conversion lib. Just check that the lib builds on m68k and problem
fixed.
Turns out it does not, but it just needs either the patch
or a newer upstream version *plus*
Lisandro Damián Nicanor Pérez Meyer dixit:
m68k is not a release arch so the severity should be at most normal.
No: for non-release archs, “important” is the cap, and FTBFS are
RC if the package built before (means important due to the cap)
and important if it did not build before.
The patch
) unreleased; urgency=medium
+
+ * Add support for m68k.
+
+ -- Thorsten Glaser t...@mirbsd.de Mon, 16 Feb 2015 15:51:13 +0100
+
qtdeclarative-opensource-src (5.3.2-4) unstable; urgency=medium
* Remove CMake files for plugins, we don't need to ship them.
diff -Nru qtdeclarative-opensource-src-5.3.2
+dfsg-3+m68k.2) unreleased; urgency=medium
+
+ * fix_double-conversion_for_m68k.diff: Fix dtoa for m68k (see #778644)
+ * fix_alignment.diff: Make implicit alignment assumptions explicit
+
+ -- Thorsten Glaser t...@mirbsd.de Mon, 09 Mar 2015 23:21:54 +
+
qtwebkit-opensource-src (5.3.2+dfsg-3
Source: qtwebkit
Version: 2.3.4.dfsg-3
Severity: important
Justification: fails to build from source (but built successfully in the past)
on non-release arch
/tmp/buildd/qtwebkit-2.3.4.dfsg/Source/JavaScriptCore/assembler/MacroAssembler.h:62:2:
error: #error The MacroAssembler is not supported
fail
symbols file mismatch
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/pine.bsm.4.64l.1504021220560.5...@herc.mirbsd.org
On Mon, 1 Jun 2015, Lisandro Damián Nicanor Pérez wrote:
I'm afraid that build was made with a broken version of dpkg-dev which
corrupted the diffs so I can't apply it directly :(
Aww :(
dpkg-dev has been fixed last week. Is there any chance for you to re do the
build log with an
Hi,
any progress? I would kinda like to get the updated qt4-x11…
the patch I posted earlier works, FWIW.
Thanks,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT):
On Tue, 26 May 2015, Lisandro Damián Nicanor Pérez wrote:
Thorsten: an hour ago I uploaded the latest Qt4 upstream release. Can you get
me an x32 build log with your patch? You can also use
git://git.debian.org/git/pkg-kde/qt/qt4-x11.git
The master branch has the patches in it.
OK
On Tue, 26 May 2015, Lisandro Damián Nicanor Pérez wrote:
So basically we are not able to upstream this anymore.
Arrrgh… okay…
I'm reluctant to keep this as a delta...
… in this case still? The patch is really manageable,
even less than what we had for m68k, basically just
says “there is
Source: qtwebkit-opensource-src
Version: 5.4.2+dfsg-2
Followup-For: Bug #780430
Hi Lisandro,
please remember submitters don’t get bugmail… or ping them ;)
Anyway, here you are:
- We need the original author of the patches.
The patches were written by myself.
- We need the original author to
Package: plasma-desktop-data
Version: 4:5.3.2-2
Severity: normal
Tags: patch
Hi,
the file /usr/share/kdisplay/app-defaults/XTerm.ad is new with KDE 5
and causes my ~/.Xresources to be no longer honoured.
After figuring out what is done here, I found that the aforementioned
file uses “instance”
Package: konqueror
Version: 4:15.04.3-1
Severity: grave
Tags: security
Justification: user security hole
I was just typing a geocaching log in a konqueror that popped up
when activating a link in a mail (to the cache listing) and noticed
small decimal digits scrolling by, one on a line, in the
-- Forwarded message --
From: Andreas Schwab <sch...@linux-m68k.org>
Message-ID: <87vbap8cle@igel.home>
Date: Fri, 02 Oct 2015 18:22:21 +0200
Subject: Re: Log for attempted build of qtwebkit_2.3.4.dfsg-5 on m68k
(dist=unstable)
Thorsten Glaser <t...@mi
Package: konqueror
Version: 4:15.08.3-1
Severity: important
Where’s the menu bar gone? (See screenshot.)
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.3.0-1-amd64
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
retitle 809979 kate: mishandles coupled BDF fonts (probably a Qt5 issue though…)
thanks
Meh, let me re-sign that… reportbug ate my signature.
tg@fish:~ $ cksum -a md5 -a sha1 -a sha256 pub/tmp/xfonts-base_3_all.deb
MD5
Package: kate
Version: 4:15.08.3-1
Severity: normal
Hi again,
this is similar to #808801 in that I believe the cause to be
related, although the symptoms differ. Again, this is most
likely an issue caused by the move to Qt5.
When I load my keyboard layout (US-based, Escape is left to
the number
Subject: kate: mishandles coupled BDF fonts (probably a Qt5 issue though…)
Package: kate
Version: 4:15.08.3-1
Severity: normal
First off, this is probably a Qt5 issue, sorry about that, but given
that the KDE/Qt maintainers are one team, and I can reproduce it with
Kate (but apparently also
Package: kate
Version: 4:15.08.3-1
Severity: important
I’m doing a VNC connection to localhost (“vncviewer :2”)
then start kate and begin to type “asd”. The text edit
window shows “abf”.
This is the same behaviour ARAnyM has under VNC, but t̲h̲a̲t̲’s
an SDL application, while I’d expect KDE/Qt
affects 808801 musescore
thanks
This also affects musescore, but not Konqueror.
I notice a common pattern: affected programs are linked
against Qt5, unaffected ones against Qt4.
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228
Package: kio-extras
Version: 4:16.04.1-1
Trying to upgrade from 4:15.08.3-2 wants to remove plasma-workspace
(and thus plasma-desktop and kde-plasma-desktop), because the latter
Depends on kactivities which the newer kio-extras version Breaks but
does not Provides.
bye,
//mirabilos
--
tarent
Package: konqueror
Version: 4:15.08.3-1
Severity: grave
Tags: security
Justification: user security hole
See attached screenshot – konqueror does not error out when the
certificate is expired and even shows a green checkbox. (I may
or may not have ACK’d the certificate in an earlier session, I
Package: kontact
Version: 4:4.14.10-2
Severity: normal
See attached screenshot. The checkboxes in particular are extremely
irritating as they differ only in colour, not graphics.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Hi again,
I now copy the halfwidth part of the FixedMisc font as FixedMiscHW.
When I select that font in Kate, it works… funnily enough, fullwidth
glyphs are also drawn, I have no idea from what fonts though (there
are several; some fit into the height, some extend the lines). This
all smells
Hi,
this just happened on another system for me.
I figured out a workaround:
Right-click on the navigation bar, then “Configure Toolb̲ars…”
then hit the 「D̲efaults」 button.
Unfortunately, after I press ^T to get a new tab, the menu
bar is gone again, reproducibly, and independent on which
tab
Package: kmail
Version: 4:16.04.3-1
Severity: important
As can be seen in the attached screenshots, the message headers
are missing from the message detail view.
The message preview in the main window also lacks them.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
On Tue, 26 Jul 2016, Sandro Knauß wrote:
> please install kdepim-addons. There you find all message header styles.
OK, but if without there are no header styles, it should
be in Depends.
Also, how can I customise it? The fancy one looks almost
like before, but it has empty (for most messages)
Package: kmail
Version: 4:16.04.3-1
Severity: normal
While the last batch of updates improved the situation on amd64
it worsened on x32 (at least, but that’s what I have): it doesn’t
start at all any more, with an error from a GNOME library out of
all things:
-BEGIN cutting here may damage
On Wed, 13 Jul 2016, Maximiliano Curia wrote:
> You haven't upgraded kmail, so it seems that you haven't a fully upgraded
> kdepim. Make sure that you have the version 4:16.04.2-2 installed.
Ah okay… … … damn:
Dependency installability problem for [159]kdepim on x32:
Package: akonadiconsole
Version: 4:4.14.10-2
Severity: serious
Justification: makes the package unusable
While trying to debug #830762 (to see if the new messages are in fact
downloaded) I tried to start akonadiconsole, with, well, limited success:
-BEGIN cutting here may damage your screen
Package: kmail
Version: 4:4.14.10-2
Severity: serious
Justification: makes the package unusable
After the recent KDEPIM-related updates (including involving a wallet
migration, which seems to have worked, and a reboot, so the last traces
of old Akonadi/KDEPIM are gone from the process table),
Package: ksnapshot
Version: 4:16.08.2-1
Severity: wishlist
I can never remember the name of the new utility (and, to add
insult to injury, it’s listed as “kde-spectacle” in the package
description but its binary is actually “spectacle”), so please
add the following script…
#!/bin/sh
echo >&2 W:
Package: kontact
Version: 4:16.04.3-1
Severity: important
Kontact does not start. It outputs the following to
.xsession-errors while that:
-cutting here may damage your screen surface-
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-tglase'
QDBusObjectPath
Lisandro Damián Nicanor Pérez Meyer dixit:
>Andreas: did you made the patch? Has it been submitted upstream? What's the
>license for it? I can't just blindy apply it without that info.
Patches usually share the licence of the patched files;
as it is, there’s nothing copyright-relevant in it
Package: systemsettings
Version: 4:5.8.4-1
Severity: normal
I cannot select the X11 “core” cursor theme in KDE, and it ignores
the Debian x-cursor-theme alternatives choice too.
This is especially annoying when connecting to a KDE full desktop or
even application via rdesktop (client side) to
Package: kde-spectacle
Version: 16.08.3-1
Severity: important
File: /usr/bin/spectacle
An important regression:
tglase@tglase:~ $ echo $DISPLAY
:2
tglase@tglase:~ $ spectacle
Qt: XKEYBOARD extension not present on
Hi *,
has anyone done anything on this?
I noticed that Trinity themselves have a “PPA” on “the only functional
Launchpad instance outside of Canonical”, in which they offer packages
for Debian releases even. AIUI these are actively maintained and even
security-fixed.
I was considering reviewing
Package: kde-spectacle
Version: 16.08.3-2
Severity: normal
tglase@tglase:~ $ spectacle
Qt: XKEYBOARD extension not present on the X server.
The X11 connection broke: Unsupported extension used (code 2)
XIO: fatal IO
Package: libqt5core5a
Version: 5.9.1+dfsg-11
Severity: normal
Reproduction steps:
• start MuseScore, load any score that has at least a note in it
or create a new empty score then insert a note, any (black) note
• select the note
• press F8 to let the inspector show on the right-hand side of
Source: gpgme1.0
Version: 1.9.0-6
Severity: important
Justification: fails to build from source (but built successfully in the past),
on d-ports arch
https://buildd.debian.org/status/fetch.php?pkg=gpgme1.0=x32=1.9.0-6=1507702170=0
points out the problem: Qt wants to be compiled with -fPIC and
John David Anglin dixit:
> On 2018-07-29 9:59 PM, Lisandro Damián Nicanor Pérez Meyer wrote:
>> if(qwebview arch)
>> echo/usr/${DEB_HOST_MULTIARCH}/qt5/qwebview >> debian/qttools5-dev-
>> tools.install
>> if(qdoc arch)
>> echo qdoc >> debian/qttools5-dev-tools.install
> That looks like it
Source: qttools-opensource-src
Version: 5.11.1-3
Severity: important
Justification: fails to build from source (but built successfully in the past),
on d-ports arches
https://buildd.debian.org/status/package.php?p=qttools-opensource-src
LLVM/clang simply is not available for many Debian
John Paul Adrian Glaubitz dixit:
>Resource files (docs, images etc) are normally architecture-independent, so
>they should be separable from the binary packages.
True. MuseScore does that too, but not from qdoc AFAICT.
Can we unbundle the resources but still make them available
in a way that
affects 894476 src:musescore
retitle 894476 rcc: please honour SOURCE_DATE_EPOCH
thanks
Hi *,
I just got bitten by this in an FTBR of src:musescore which I tracked
down to this bug.
On Tue, 3 Apr 2018, Sune Vuorela wrote:
> If S_D_E gets used, rather than the data.xml modified date in the
>
Hi Chris,
> It is not required.
I’m parsing this as “you were not incorrect”, right?
(Sorry, non-English-native speaker here.)
> Does the canonical specification not explain?
>
> https://reproducible-builds.org/specs/source-date-epoch/
>
> I pedantically refer you to that /only/ because if it
On Mon, 9 Jul 2018, Chris Lamb wrote:
> far easier and clearer IMHO to statelessly state that clamping is not
> required when using SOURCE_DATE_EPOCH. :)
OK, now I do not understand _that_…
Doesn’t matter as long as this bug gets fixed, though ☻☺
Have a nice day,
//mirabilos
--
>> Why don't
Package: libqt5qml5
Version: 5.10.1-3
Hi,
during package build of, for example, qtwebsockets-opensource-src
(5.10.1-2) its testsuite gets a segfault.
I can get a backtrace; unfortunately, most values for inspection
are optimised out though:
(gdb) bt
#0 0xf7f96035 in ?? ()
#1 0x02290450 in ??
Source: qtwebsockets-opensource-src
Version: 5.10.1-2
Severity: important
Justification: FTBFS but on non-release architecture
https://buildd.debian.org/status/fetch.php?pkg=qtwebsockets-opensource-src=hurd-i386=5.10.1-2=1523796345=0
FAIL! : tst_QWebSocket::tst_errorString() QTestLib: This test
Source: qtmultimedia-opensource-src
Version: 5.10.1-2
Severity: important
Justification: FTBFS on non-release architecture
Excerpt from the build log:
* Finished testing of tst_QAudioNamespace *
make[4]: Leaving directory '/<>/tests/auto/unit/qaudionamespace'
cd qcamera/ && (
affects 895375 src:qtwebsockets-opensource-src
affects 895375 src:qtscript-opensource-src
affects 895375 src:qtgraphicaleffects-opensource-src
thanks
Aaron M. Ucko dixit:
>Builds of qtwebsockets-opensource-src for sparc64 and x32 (admittedly
>not release architectures) have been failing lately,
Source: qtdeclarative-opensource-src
Version: 5.11.3-2
Severity: important
See also:
https://buildd.debian.org/status/fetch.php?pkg=qtdeclarative-opensource-src=x32=5.11.3-2=1545865790=0
src/qml/jsruntime/qv4global_p.h line 94 always triggers,
because x32 is detected as amd64 (Q_PROCESSOR_X86
Hi Dmitry,
> On Mon, Jan 07, 2019 at 12:15:25PM +0100, Thorsten Glaser wrote:
> > src/qml/jsruntime/qv4global_p.h line 94 always triggers,
> > because x32 is detected as amd64 (Q_PROCESSOR_X86 and
> > Q_PROCESSOR_X86_64 are defined and QT_POINTER_SIZE is 8)
> > by qtba
Source: qt3d-opensource-src
Version: 5.11.3+dfsg-2
Severity: important
Justification: FTBFS on non-release architecture
https://buildd.debian.org/status/fetch.php?pkg=qt3d-opensource-src=x32=5.11.3%2Bdfsg-2=1547070693=0
Apparently, x32 behaves like amd64 for some of the symbols.
Package: libpolkit-qt-1-1, libpolkit-qt5-1-1
Version: 0.112.0-6
Severity: wishlist
Hi,
please bring back the “| consolekit” in Depends. I am aware that
the package is no longer shipped, but people still have it installed
from previous Debian releases, and this is an important part of having
a
Dear maintainers,
a new upload (0.112.0-7) was done, but without applying the
patch from this report.
Please do so, to unbreak installability. I’m considering an
NMU upload if not done within two weeks or so.
Thanks,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn •
On Sat, 28 Sep 2019, Cristian Ionescu-Idbohrn wrote:
> 1. install sysvinit-core; that removes systemd-sysv but nothing else
>systemd related
> Souldn't that work?
It would, if but for libpam-systemd having a (somewhat questionable
but understandable) dependency on systemd-sysv. This is
Source: qtscript-opensource-src
Version: 5.12.5+dfsg-2
Severity: important
Justification: FTBFS on non-release architecture but built successfully in the
past
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=qtscript-opensource-src=x32=5.12.5%2Bdfsg-2=1571650729=0
Two failures:
===
+instead of libpam-systemd (Closes: #925344)
+
+ -- Thorsten Glaser Wed, 09 Oct 2019 19:22:38 +0200
+
polkit-qt-1 (0.112.0-7) unstable; urgency=medium
* Teamp upload.
diff -Nru polkit-qt-1-0.112.0/debian/control polkit-qt-1-0.112.0/debian/control
--- polkit-qt-1-0.112.0/debian/control 2019-08
Hi Bernhard,
you seem to be triaging a lot of segfault bugs recently ;-)
>Usually when a segfault happens in 'dmesg' output should
>appear two lines about this event. Maybe you could forward
>these to the report too.
We debugged this together, as it just happened when we were
discussing the
Samuel Thibault dixit:
>I guess in your case what you expected was that at the very least
>applications started after orca got started should be accessible, even
>if orca is only started by hand. This would work if Qt was not only
>looking at org.a11y.Status ScreenReaderEnabled (the control panel
# same issue
forcemerge 879014 870383
retitle 879014 gpgme1.0: FTBFS on some arches: Qt needs a compile with -fPIC
(PIE is not enough), hardening downgrades to PIE
# it still persists
found 879014 1.13.1-6
thanks
Hi,
> points out the problem: Qt wants to be compiled with -fPIC and sets up
> the
On Mon, 9 Mar 2020, Lisandro Damián Nicanor Pérez Meyer wrote:
> PIE implies PIE so (and here is what I miss wrote above) PIE should
> not be added if PIC was used.
PIC implies PIE ;)
> Moreover PIC is more suitable for libraries, so it should be the right
> choice here.
The problem is that
Package: kde-spectacle
Version: 20.04.1-1
Followup-For: Bug #849012
$ spectacle
qt.qpa.xcb: XKeyboard extension not present on the X server
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought
Pino Toscano dixit:
>In data mercoledì 1 luglio 2020 14:10:36 CEST, Thorsten Glaser ha scritto:
>> $ spectacle
>>
>> qt.qpa.xcb: XKeyboard extension not present on the X server
>
>Th
Hi Dmitry,
> "Warning: This module is not actively developed. It is provided for backwards
ah, okay. It’s depended on by some things, pyqt5 IIRC, which is
why I thought it more important. I’ve uploaded with nocheck for
now.
Thanks,
//mirabilos
--
«MyISAM tables -will- get corrupted eventually.
1 - 100 of 104 matches
Mail list logo