El jueves, 29 de marzo de 2018 14:07:02 -03 Vladimir Berezenko escribió:
> > Hi! I definitely can't reproduce this bug. Can you still reproduce it?
> > Which Qt version are you currently using?
>
> This is definitely reproducible. The current Qt5 version is 5.9.2-2 on my
> quad G5, and 5.8.4 on G4
Hi Thomas,
> Maybe the solution is then not in rcc but in whatever generate the files
> that the qrc that rcc processes refer to. For instance in the case of
> ultracopier lrelease could have a mean if generating .qm files with the
> same modified timestamp as the .ts file it processes
That so
On April 3, 2018 10:15:42 PM GMT+01:00, "Lisandro Damián Nicanor Pérez Meyer"
wrote:
>El mar., 3 de abr. de 2018 16:42, Sune Vuorela
>escribió:
>
>> On Tuesday, April 3, 2018 9:24:58 PM CEST Chris Lamb wrote:
>> > I'm not /entirely/ sure what the difference is as I'm not in the
>> > Qt/RCC world
El mar., 3 de abr. de 2018 16:42, Sune Vuorela escribió:
> On Tuesday, April 3, 2018 9:24:58 PM CEST Chris Lamb wrote:
> > I'm not /entirely/ sure what the difference is as I'm not in the
> > Qt/RCC world too often these days (alas !), but why just not use
> > SOURCE_DATE_EPOCH *iff* it is export
Package: plasma-workspace
Version: 4:5.12.4-1
Severity: important
Tags: upstream
Dear Maintainer,
Plasmashell freezes when showing a notification. I can use everything else like
the menu, tooltips and tray apps but if any app, like plasma-nm, pops up a
notification the notification starts to dr
On Tuesday, April 3, 2018 9:24:58 PM CEST Chris Lamb wrote:
> I'm not /entirely/ sure what the difference is as I'm not in the
> Qt/RCC world too often these days (alas !), but why just not use
> SOURCE_DATE_EPOCH *iff* it is exported?
>
> Normal systems simply do not have this envvar set, so ther
On April 3, 2018 8:20:22 PM GMT+01:00, Sune Vuorela wrote:
>On Tuesday, April 3, 2018 9:14:23 PM CEST Chris Lamb wrote:
>> Hi Sune!
>>
>> > I don't think honouring SOURCE_DATE_EPOCH is the right idea under
>normal
>> > circumstances
>>
>> Can you elaborate on what you mean by "normal circumstanc
Package: kcharselect
Version: 4:16.08.0-1+b1
Severity: important
Dear Maintainer,
Going to "Mathematical Symbols > Mathematical Operators" character block
crashes the application. The crash happens only when a specific font is set
(tested on Noto Sans, on many other fonts this bug is not reprod
Hi Sune,
> "normal circumstances" is rcc on a source file, as opposed
> to an autogenerated file
I'm not /entirely/ sure what the difference is as I'm not in the
Qt/RCC world too often these days (alas !), but why just not use
SOURCE_DATE_EPOCH *iff* it is exported?
Normal systems simply do not
On Tuesday, April 3, 2018 9:14:23 PM CEST Chris Lamb wrote:
> Hi Sune!
>
> > I don't think honouring SOURCE_DATE_EPOCH is the right idea under normal
> > circumstances
>
> Can you elaborate on what you mean by "normal circumstances"? :)
"normal circumstances" is rcc on a source file, as opposed
Hi Sune!
> I don't think honouring SOURCE_DATE_EPOCH is the right idea under normal
> circumstances
Can you elaborate on what you mean by "normal circumstances"? :)
How about e use S_D_E if it is setup/exported, otherwise use the mtime
of the file as before?
(This is the pattern/logic used ext
On Tuesday, April 3, 2018 8:46:51 PM CEST Thomas Preud'homme wrote:
> The problematic files are Qt message files (ie .qm files) generated at build
> time via lrelease from translation files (ie .ts files). Therefore two
Right. I didn't think about autogenerated files during build.
> I think it wo
On Saturday, March 31, 2018 12:05:02 PM CEST Chris Lamb wrote:
> > While investigating ultracopier's lack of build reproducibility, I found
> > out that rcc encodes the timestamp of the files the QRC file being
> > compiled references
I don't actually see why this should be a problem. If input cha
On April 3, 2018 7:25:03 PM GMT+01:00, Sune Vuorela wrote:
>On Saturday, March 31, 2018 12:05:02 PM CEST Chris Lamb wrote:
>> > While investigating ultracopier's lack of build reproducibility, I
>found
>> > out that rcc encodes the timestamp of the files the QRC file being
>> > compiled references
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Apr 2018 19:24:24 +0200
Source: kdepim-addons
Binary: kdepim-addons
Architecture: source
Version: 17.12.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers
Changed-By: Sandro Knauß
Desc
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 03 Apr 2018 19:24:24 +0200
Source: kdepim-addons
Binary: kdepim-addons
Architecture: source
Version: 17.12.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers
Changed-By: Sandr
Your message dated Tue, 03 Apr 2018 17:50:35 +
with message-id
and subject line Bug#894587: fixed in kdepim-addons 17.12.3-2
has caused the Debian Bug report #894587,
regarding kdepim-addons: File conflict with akonadi-contacts-data 4:17.08.3-2
to be marked as done.
This means that you claim
kdepim-addons_17.12.3-2_source.changes uploaded successfully to localhost
along with the files:
kdepim-addons_17.12.3-2.dsc
kdepim-addons_17.12.3-2.debian.tar.xz
kdepim-addons_17.12.3-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Control: tag -1 wontfix
Hi Pier!
El viernes, 30 de marzo de 2018 17:18:49 -03 Pier Luigi Fiorini escribió:
> Package: libqt5waylandclient5-dev
> Version: 5.10.1-2
> Severity: normal
>
> Dear Maintainer,
>
> Please include both QtWaylandClient and QtWaylandCompositor private headers
> as they mi
Processing commands for cont...@bugs.debian.org:
> severity 894472 wishlist
Bug #894472 [libqt5waylandclient5-dev] libqt5waylandclient5-dev: Missing
QtWayland private headers
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing control commands:
> tag -1 wontfix
Bug #894472 [libqt5waylandclient5-dev] libqt5waylandclient5-dev: Missing
QtWayland private headers
Added tag(s) wontfix.
--
894472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894472
Debian Bug Tracking System
Contact ow...@bugs.debian.org wit
Your message dated Wed, 4 Apr 2018 01:01:26 +0900
with message-id <20180403160126.gd28...@bulldog.preining.info>
and subject line Re: Bug#894725: baloo-kf5: auto-starts on unrelated DE
has caused the Debian Bug report #894725,
regarding baloo-kf5: auto-starts on unrelated DE
to be marked as done.
Processing commands for cont...@bugs.debian.org:
> forwarded 894726 https://bugreports.qt.io/browse/QTBUG-56264
Bug #894726 [libqt5qml5] libqt5qml5: QQmlEngine segfaults on sparc64
Set Bug forwarded-to-address to 'https://bugreports.qt.io/browse/QTBUG-56264'.
> kthxbye
Stopping processing here.
P
Processing commands for cont...@bugs.debian.org:
> forward 894726 https://bugreports.qt.io/browse/QTBUG-56264
Unknown command or malformed arguments to command.
> block 839134 by 894726
Bug #839134 [src:qbs] qbs: FTBFS on sparc64: Testsuite failures
839134 was not blocked by any bugs.
839134 was n
While checking a failure of a local QT application, I ran into 894726
(QQmlEngine segfaults on sparc64)
Looking at the failing qtmultimedia test case, it also tries to create
a QQmlEngine instance in the audioRole test case, so it seems likely
that it's hitting the same bug.
Package: libqt5qml5
Version: 5.9.2-3
Severity: important
Trying to track down why a QT program was failing, I found that the qt5qml5
package is currently broken on sparc64.
The following simple example segfaults when run on sparc64, before reaching the
"QQmlComponent" line, while working as expe
Package: baloo-kf5
Version: 5.44.0-1
Severity: important
Hi all,
I am running Cinnamon, but also have a KDE in case I want to switch or
play around.
Unfortunately, dolphin depends on baloo-kf5, and baloo-kf5 auto-starts
in Cinnamon, taking up about 20% of CPU time for A***GES.
Please disabl
27 matches
Mail list logo
