Bug#1062725: 64-bit time_t transition in progress

On Thu, 8 Feb 2024 at 13:06, Lisandro Damián Nicanor Pérez Meyer wrote: > > Hi! > > On Fri, 2 Feb 2024 at 13:22, Steve Langasek wrote: > > > > Dear developers, > > > > A number of you will have noticed already that the 64-bit time_t transition > >

Bug#1062725: 64-bit time_t transition in progress

be it Qt 5 or 6, you only need to modify libqtXcoreX. The rest of the packages will just follow suite, **nothing** in Qt does not depends upon libQtCoreX. In fact I would say that by doing that you get even the whole KDE stack in. -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/

Bug#1050313: kde-spectacle: crash because of missing dependencies

El martes, 22 de agosto de 2023 20:34:09 -03 Alexandre Detiste escribió: > Package: kde-spectacle > Version: 23.04.2-2 > Severity: important > > > specatecle needs "libqt5quickshapes5" & "qml-module-qtquick-shapes" installed. > > without these it will crash: This boils down to only the QML

Bug#1042297: qt6-virtualkeyboard: FTBFS: dh_missing: error: missing files, aborting

Version: 6.4.2+dfsg-3 Hi Lucas! This was actually fixed already in the archive by version -3, so closing. Thanks for your work, Lisandro. El miércoles, 26 de julio de 2023 17:14:13 -03 Lucas Nussbaum escribió: > Source: qt6-virtualkeyboard > Version: 6.4.2+dfsg-2 > Severity: serious >

Bug#1041300: qt6-base-dev: undeclared file conflict with libqt6opengl6-dev

El lunes, 17 de julio de 2023 01:31:04 -03 Helmut Grohne escribió: > Package: qt6-base-dev > Version: 6.4.2+dfsg-12 > Severity: serious > > The recent upload makes qt6-base-dev include a fair number of files also > contained in libqt6opengl6-dev. Is this some kind of packaging mistake? yeap,

Bug#1040496: qt6-virtualkeyboard FTBFS with parallel=1: qmlcachegen segfaults

follows: Interestingly enough I could only reproduce the issue by using sbuild. If I hand compile it using dpkg-buildpackage directly on a clean machine things just work. -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/

Bug#1035066: qt6-scxml-dev: Missing file

up. Thanks for the bug. Would you mind sending the CMake line that triggered this? Thanks in advance, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/

Bug#1031078: qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided

calls the relevant find_package() functions. . This patch simply adds them. Author: Lisandro Damián Nicanor Pérez Meyer Bug-Debian: https://bugs.debian.org/973795 Forwarded: no --- hyperborg-1.0.orig/node/CMakeLists.txt +++ hyperborg-1.0/node/CMakeLists.txt @@ -24,6 +24,8 @@ find_package(Qt6

Bug#1031078: marked as done (qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided)

reopen 1031078 thanks > Oh, please ignore: I realize now that debhelper does not yet cover Qt6 > and the failure relates to upstream-shipped pre-generated CMakefiles, > and I (until debhelper is improved) need to override dh_auto_configure > to call qmake6. > > Closing this as a non-bug.

Bug#1031078: qt6-speech-dev: library libqtexttospeech_mock.so referenced but not provided

Hi Jonas! El sábado, 11 de febrero de 2023 06:15:04 -03 Jonas Smedegaard escribió: > Package: qt6-speech-dev > Version: 6.4.2-2 > Severity: grave > Justification: renders package unusable > > When I try to build a project containing this line: > > find_package(Qt6 COMPONENTS TextToSpeech

Bug#1012786: libcamera: Fails to build from source

oid the deprecation warning). -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/

Bug#1012786: libcamera: Fails to build from source

Source: libcamera Version: 0~git20200629+e7aa92a-8 Severity: serious Justification: Fails to build form source X-Debbugs-Cc: lisan...@debian.org Trying to fix a bug in libcamera I found it's currently failing to build from source. Seems it's taking deprecation warnings as errors. Log follows.

Bug#1001128: Fixed in linux-image-5.16.0-rc5-amd64 5.16~rc5-1~exp1

This bug is not present in linux-image-5.16.0-rc5-amd64 5.16~rc5-1~exp1 I'm not tagging it on the BTS because I'm not sure how the versioning works for the kernel. -- Lisandro Damián Nicanor Pérez Meyer https://perezmeyer.com.ar/ <http://perezmeyer.com.ar/>

Bug#1001128: linux-image-5.15.0-2-amd64: Kernel crashes my GPU

Package: src:linux Version: 5.15.5-1 Followup-For: Bug #1001128 Forwarded: -1 https://gitlab.freedesktop.org/drm/intel/-/issues/4530#note_1166414 X-Debbugs-Cc: lisan...@debian.org I can reproduce this bug on my machine when I log into Plasma. The cause seems to be detected and fixed according

Bug#994906: FTBFS: missing plugins due to bug in libdrm-dev

Source: qtbase-opensource-src Version: 5.15.2+dfsg-10 Severity: serious Justification: Fails to build from source X-Debbugs-Cc: lisan...@debian.org This package is currently failing to build from source due to two things: - A change in libglvnd (or a compiler change that triggers this

Bug#986565: unusable with current git

reopen 986565 thanks Hi! Indeed it's not working again, so reopening the bug. On Wed, 21 Apr 2021 10:12:03 + Damyan Ivanov wrote: > Package: git-flow > Version: 1.12.3-2 > Followup-For: Bug #986565 > > Control: reopen -1 1.12.3-2 > > Sigh. Now git reverted to using /usr/lib again, and

Bug#980803: The examples don't show up in Qt Creator

severity 980803 normal thanks Hi! El vie., 22 ene. 2021 14:23, Limon Kiwi escribió: > Package: qtbase5-examples > Version: 5.15.2+dfsg-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Qt Creator 4.14.0 doesn't show the examples after installing the package

Bug#980757: python3-sugar3: trying to overwrite '/usr/bin/sugar-activity-web', which is also in package python-sugar3 0.112-3

Package: python3-sugar3 Version: 0.117-1 Severity: serious Justification: Tries to overwrite a file of another package X-Debbugs-Cc: lisan...@debian.org Hi! While updating a machine from Buster to Bullseye I've got: dpkg: error processing archive

Bug#979570: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

Hi (again)! On Sat, 9 Jan 2021 at 17:53, Vagrant Cascadian wrote: > > On 2021-01-09, Lisandro Damián Nicanor Pérez Meyer wrote: > > Oh, I have sadly forgotten to mention another thing. > > > > On Sat, 9 Jan 2021 at 15:53, Lisandro Damián Nicanor Pérez Meyer >

Bug#979570: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

Oh, I have sadly forgotten to mention another thing. On Sat, 9 Jan 2021 at 15:53, Lisandro Damián Nicanor Pérez Meyer wrote: > # __FILE__ is a public, well defined API According to: Adrian Bunks mentions it in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901#10 Holger Levsen in ht

Bug#979570: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

in dpkg and, after the release, starting to work on letting maintainers opting in. Regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

Bug#979570: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

On Fri, 8 Jan 2021 at 21:15, Lisandro Damián Nicanor Pérez Meyer wrote: > > Hi! Explicitely CCing my bug, since it seems it missed my previous reply. > > On Fri, 8 Jan 2021 at 20:49, Guillem Jover wrote: > > > > On Fri, 2021-01-08 at 19:23:13 -0300, Lisandro Damián Nicano

Bug#979570: Updating dpkg-buildflags to enable reproducible=+fixfilepath by default

Hi! Explicitely CCing my bug, since it seems it missed my previous reply. On Fri, 8 Jan 2021 at 20:49, Guillem Jover wrote: > > On Fri, 2021-01-08 at 19:23:13 -0300, Lisandro Damián Nicanor Pérez Meyer > wrote: > > [snip] > > > We did a full archive rebuild testing thi

Bug#979570: dpkg: Breaks perfectly valid usage of __FILE__

Source: dpkg Version: 1.20.6 Severity: serious Justification: Breaks well defined functionality X-Debbugs-Cc: pkg-kde-t...@alioth-lists.debian.net, reproducible-bui...@lists.alioth.debian.org Hi! As discussed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901 mangling __FILE__, even if

Bug#975129: qwt: FTBFS: qwt_painter_command.h:85:22: error: field ‘clipPath’ has incomplete type ‘QPainterPath’

> > Ping me if you need help! > > Sorry, I won't have any time until at least from now. Please go ahead. Thanks Gudjon! I've noticed the fix is in the repo, I'm doing a test build right now. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

Bug#975129: qwt: FTBFS: qwt_painter_command.h:85:22: error: field ‘clipPath’ has incomplete type ‘QPainterPath’

On Fri, 4 Dec 2020 13:01:53 -0800 tony mancill wrote: > On Wed, Nov 25, 2020 at 08:35:48AM +0100, Gudjon I. Gudjonsson wrote: > > This requires a quite simple fix. I will fix this before the weekend and > > then > > start looking into version 6.1.5. > > Hi Gudjon, > > Do you mind if I upload an

Bug#973607: Opened a MR

Hi! I have created a MR in order to fix this bug in https://salsa.debian.org/science-team/libqglviewer/-/merge_requests/2 Cheers, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

Bug#973607: libqglviewer: Depends upon removed package qt5-default

Source: libqglviewer Version: 2.6.3+dfsg2-6 Severity: serious Tags: patch Justification: autopkgtest depends upon removed package X-Debbugs-Cc: mity...@debian.org Hi! Your package's autopkgtests depends upon qt5-default, which has been removed in the last Qt upload (current transition going on).

Bug#972166: Rising severities

Hi! On Sun, 25 Oct 2020 at 20:34, Yaroslav Halchenko wrote: > > Feel welcome to NMU without delay. Sorry for being slow etc. > > Thank you! Thanks to you!!! -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

Bug#972163: Rising severities

Hi! On Sun, 25 Oct 2020 at 15:00, Sylvestre Ledru wrote: [snip] > Please upload your version, it is fine :) Done! Of course I'll keep an eye on the buildds in case something goes wrong. Thanks!!! -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

Bug#972163: Rising severities

Hi! El dom., 25 oct. 2020 11:07, Sylvestre Ledru escribió: > Hello, > > Le 25/10/2020 à 14:57, Lisandro Damián Nicanor Pérez Meyer a écrit : > > severity 972163 serious > > severity 972166 serious > > block 972176 by 972163 > > block 972176 by 972166 > > t

Bug#968438: Should this really be RC?

severity 968438 normal thanks The problem might also come from previous configuration, both a fellow co maintainer and I tried to create annotations and they worked. Yes, they are now presented as a toolbar, but they are there. And moreover the buttons do what they are intended to do. I would

Bug#968438: Should this really be RC?

Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

Bug#875243: [yagf] Future Qt4 removal from Buster

gt; 15)). > > As I see yagf package is still in Debian repo. > And now I have enough free time for updating it... > So I am going to upload updated version ported to Qt5 today if no-one objects. Qt 4 has been removed form the archive last saturday, so the fastest the better. -- L

Bug#952464: clazy: flaky arm64 autopkgtest: unable to execute command: Segmentation fault

On 20/02/25 01:46, Lisandro Damián Nicanor Pérez Meyer wrote: > On 20/02/24 09:10, Paul Gevers wrote: > > Source: clazy > > Version: 1.6-2 > > Severity: serious > > Tags: sid bullseye > > X-Debbugs-CC: debian...@lists.debian.org > > User: debian.

Bug#952464: clazy: flaky arm64 autopkgtest: unable to execute command: Segmentation fault

On 20/02/24 09:10, Paul Gevers wrote: > Source: clazy > Version: 1.6-2 > Severity: serious > Tags: sid bullseye > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: flaky > > Dear maintainer(s), Hi Paul, thanks for the bug report. > With a recent upload of

Bug#950396: libqtcore4: libcore4 and 5

Hi Preston! El vie., 31 ene. 2020 23:36, preston escribió: > Package: libqtcore4 > Version: libqtcore4 > Severity: serious > Tags: newcomer ftbfs > Justification: fails to build from source > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate > ***

Bug#875184: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

Hi! El lun., 20 ene. 2020 16:38, Moritz Mühlenhoff escribió: > On Sat, Sep 21, 2019 at 08:42:14AM +0200, Andreas Tille wrote: > > Hi, > > > > On Fri, Sep 20, 2019 at 11:55:03PM +0200, Moritz Mühlenhoff wrote: > > > On Fri, Sep 20, 2019 at 06:41:05PM -0300, Lisandr

Bug#949239: ktp-contact-runner: FTBFS on various archs

Source: ktp-contact-runner Version: 17.08.3-1 Severity: serious Tags: ftbfs sid Justification: FTBFS on various archs Hi! During a package rebuild your package FTBFS:

Bug#949238: ktp-text-ui: FTBFS on various archs

Source: ktp-text-ui Version: 17.08.3-2 Severity: serious Justification: FTBFS on various archs Hi! During a package rebuild your package FTBFS:

Bug#949237: ktp-accounts-kcm: FTBFS on various archs

Source: ktp-accounts-kcm Version: 17.08.3-1 Severity: serious Tags: ftbfs Justification: FTBFS on various archs Hi! During a rebuild your package FTBFS:

Bug#949236: ktp-common-internals: FTBFS on various archs

Source: ktp-common-internals Version: 17.08.3-1 Severity: serious Justification: FTBFS on various archs Hi! During a rebuild your package FTBFS on various archs:

Bug#945225: cppreference-doc: Fails to build from source: tries to install not generated qch file.

I'm on it. On Thu, 16 Jan 2020 at 06:56, Povilas Kanapickas wrote: > > Hi, > > I've uploaded the fixed package to mentors. It would be great if you > could sponsor it. > > Thank you, > Povilas > > On 1/14/20 3:40 PM, Lisandro Damián Nicanor Pérez Meyer wrote: >

Bug#866965: re: dosemu: DPMI unhandled exception instability back again

tag 866965 moreinfo unreproducible thanks Hi everyone! Can you still reproduce this bug? I'm running stretch's dosemu under buster and I have found no issues so far :-/ Thanks for checking!

Bug#948940: FTBFS: /plugins/owncloud-ui/owncloud.cpp:54:23: error: invalid use of incomplete type ‘class QWindow’

Source: kaccounts-providers Version: 4:17.08.3-1 Severity: serious Tags: ftbfs Justification: FTBFS on all archs Hi! During a rebuild of your package it FTBFS with the following error: /plugins/owncloud-ui/owncloud.cpp:54:23: error: invalid use of incomplete type ‘class QWindow’ The build logs

Bug#948939: FTBFS: rkward/windows/rkworkplace.cpp:71:2: error: ‘QVBoxLayout’ was not declared in this scope

Source: rkward Version: 0.7.0b-1.1 Severity: serious Tags: ftbfs Justification: FTBFS on all archs Hi! During a rebuild of your package it FTBFS with the following error: /<>/rkward/windows/../dataeditor/twintable.h:117:7: warning: ‘virtual void TwinTable::objectMetaChanged(RObject*)’ can be

Bug#948917: FTBFS: No rule to make target '/usr/lib/x86_64-linux-gnu/libglib-2.0.so'

Source: screengrab Version: 1.101-1 Severity: serious Justification: FTBFS on all archs Hi! During a rebuild your package FTBFS on all affected archs:

Bug#948914: FTBFS: The qmake executable '/usr/bin/qmake' failed with exit code 1.

Source: qmath3d Version: 0~1.0-2) Severity: serious Justification: FTBFS on all archs Hi Wookey! During a rebuild of your package it FTBFS: The error seems to be: WARNING: Error setting up Qt for

Bug#948913: FTBFS: No rule to make target 'QtWebKit/QWebView', needed by 'ui_report.h'. Stop

Source: sleepyhead Version: 1.0.0-beta-2+dfsg-7 Severity: serious Justification: FTBFS: can not complete target Hi! During a rebuild your package FTBFS: The error seems to be:

Bug#948912: FTBFS: can not find boost >= 1.55

Source: regina-normal Version: 5.1-6 Severity: serious Justification: Fails to build from source: can't find boost During a rebuild your package failed to build form source: CMake outputs the following

Bug#948911: klog: FTBFS on mipsel: {standard input}:107582: Error: branch out of range

Source: klog Version: 0.9.8.1-1.1 Severity: serious Justification: Fails to build from source on mipsel Hi! During a rebuild your package FTBFS: The bug

Bug#945225: cppreference-doc: Fails to build from source: tries to install not generated qch file.

Hi! On 20/01/14 02:03, Michael Crusoe wrote: > On Wed, 27 Nov 2019 16:00:05 +0200 Povilas Kanapickas > wrote: > > On 11/27/19 1:19 PM, Michael Crusoe wrote: > > > Maybe this patch from Ubuntu will help? > > > >

Bug#947679: qsynth: FTBFS on s390x: lrelease error: Parse error ... qsynth_sr.ts:734:29: Premature end of document.

Hi! El mié., 8 ene. 2020 18:08, Sebastian Ramacher escribió: > Control: tags -1 + help moreinfo > > On 2019-12-28 22:12:34, Lisandro Damián Nicanor Pérez Meyer wrote: > > Source: qsynth > > Version: 0.6.0-1 > > Severity: serious > > Justification: FTBFS on s390

Bug#947679: qsynth: FTBFS on s390x: lrelease error: Parse error ... qsynth_sr.ts:734:29: Premature end of document.

Source: qsynth Version: 0.6.0-1 Severity: serious Justification: FTBFS on s390x Hi! Your package failed to build from source on s390x with the following error: lrelease error: Parse error at src/translations/qsynth_sr.ts:734:29: Premature end of document. make[1]: *** [Makefile:102:

Bug#947678: FTBFS: /usr/bin/ld: cannot find -lGL

Source: mlt Version: 6.18.0-3 Severity: serious Justification: FTBFS on all archs Hi! Your package failed to build form source on all archs: The error seems to be: g++ -shared -o ../libmltopengl.so factory.o consumer_xgl.o

Bug#875250: Intend to port to Qt 5

And attached is the NMU patch. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ From 90c200f506436898e5d64766c0fb7a031e151cc9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lisandro=20Dami=C3=A1n=20Nicanor=20P=C3=A9rez=20Meyer?= Date: Sat, 28 Dec 2019

Bug#875250: Intend to port to Qt 5

I'm about to upload an NMU just with the Qt 4 drop changes, as the package has received another NMU in the meantime. Tz-Huan and Benda: Rolf, the main maintainer, seems unactive since ~ april 2018. If you want you might consider using the salvaging process to take over maintenance. If you are not

Bug#875250: Intend to port to Qt 5

Hi! El vie., 27 dic. 2019 18:28, Moritz Mühlenhoff escribió: > On Thu, Dec 05, 2019 at 11:50:53AM +0800, Benda Xu wrote: > > Hi Moritz, > > > > I started to work on qt5 port of SCIM. There is some remaining blocks. > > I will work on it for another 10 days. > > > > I want to postpone to

Bug#947492: FTBFS: on mips64el and mipsel: tests failing

Source: kdiagram Version: 2.6.1-1+b1 Severity: serious Justification: FTBFS on mipsel and mips64el Hi! Your package's tests are failing on mipsel andmips64el. You can see the build logs at https://buildd.debian.org/status/package.php?p=kdiagram Kinds regards, Lisandro. -- System Information:

Bug#947490: FTBFS: CMake can't find X11

Source: kadu Version: 4.1-1.1 Severity: serious Justification: FTBFS in various architectures Hi! While binNMUing your package it FTBFS with the following error: -- Looking for archive_write_set_compression_xz in /usr/lib/x86_64-linux-gnu/libarchive.so - found CMake Error at

Bug#947487: FTBFS: various C++ errors

Source: grantlee5 Version: 5.1.0-2.1 Severity: serious Justification: FTBFS in various architectures Hi! While rebuilding your package due to a binNMU it failed to build from source: https://buildd.debian.org/status/package.php?p=grantlee5 The forst error I see is: from

Bug#936483: FTBFS due to this?

Control: tag -1 ftbfs Apparently this is also causing a FTBFS: https://buildd.debian.org/status/package.php?p=enki-aseba

Bug#947475: FTBFS: make[1]: *** No rule to make target 'lowered_tree_view.h', needed by 'ui_datovka.h'. Stop.

Source: datovka Version: 4.9.3-2 Severity: serious Justification: FTBFS on all archs Hi! During a binNMU rebuild your package FTBFS with the following error: make[1]: Entering directory '/<>' make[1]: *** No rule to make target 'lowered_tree_view.h', needed by 'ui_datovka.h'. Stop. make[1]:

Bug#947474: FTBFS: various C++ related errors

Source: cloudcompare Version: 2.10.3-3 Severity: serious Justification: FTBFS on amd64, arm64 and others Hi! during a binNMU rebuild of your package it FTBFS with various C++ related errors. You can see the build logs in https://buildd.debian.org/status/package.php?p=cloudcompare Thanks,

Bug#947329: FTBFS: debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory

Hi! El mié., 25 dic. 2019 08:34, Andreas Tille escribió: > Hi Lisandro, > > On Wed, Dec 25, 2019 at 07:05:22AM -0300, Lisandro Damián Nicanor Pérez > Meyer wrote: > > > > Sorry, I forgot to mention that the build failures came directly from > > buildds, so I would

Bug#947329: FTBFS: debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory

Hi Andreas! El mié., 25 dic. 2019 04:24, Andreas Tille escribió: > Control: tags -1 unreproducible > Control: tags -1 moreinfo > > Hi, > > On Tue, Dec 24, 2019 at 03:56:45PM -0300, Lisandro Damián Nicanor Pérez > Meyer wrote: > > > > Hi! During a

Bug#947330: FTBFS: *** No rule to make target 'libc2b.a', needed by '../bin/cb2bib'. Stop.

Source: cb2bib Version: 1.9.9-1 Severity: serious Justification: FTBFS Hi! During a rebuild of your package it FTBFS with the following error: g++ -pipe -g -O2 -fdebug-prefix-map=/<>/debian/build/src=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=.

Bug#947329: FTBFS: debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory

Source: bppphyview Version: 0.6.1-1 Severity: serious Justification: FTBFS Hi! During a rebuild of your package it FTBFS with the following error: dh_installman: mv debian/bppphyview/usr/share/man/man1/phyview.1.dh-new debian/bppphyview/usr/share/man/man1/phyview.1: No such file or directory

Bug#947328: FTBFS: dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new: No such file or directory

Source: xca Version: 2.1.2-2 Severity: serious Justification: FTBFS Hi! During a rebuild your package FTBFS with the following error: dh_installman: mv debian/xca/usr/share/man/man1/xca.1.dh-new debian/xca/usr/share/man/man1/xca.1: No such file or directory Thanks for your work! -- System

Bug#947327: FTBFS: /usr/bin/env: ‘python’: No such file or directory

Source: poppler Version: 0.71.0-6 Severity: serious Justification: FTBFS Hi! During a rebuild of your package it FTBFS with the following error: [ 58%] Generating glib-docs-build.stamp cd /<>/obj-x86_64-linux-gnu/glib/reference && ../../../make-glib-api-docs --src-dir=/<>

Bug#947326: dh: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC

Source: antimony Version: 0.9.3-1 Severity: serious Justification: FTBFS Hi! While rebuilding your package against a new Qt version it FTBFS due to some python error: dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean --with python3 --buildsystem=cmake dh:

Bug#875250: Intend to port to Qt 5

Hi Benda! On Thu, 05 Dec 2019 11:50:53 +0800 Benda Xu wrote: > Hi Moritz, > > I started to work on qt5 port of SCIM. There is some remaining blocks. > I will work on it for another 10 days. > > I want to postpone to deadline to Dec 15, if that does not drag the QT5 > migration too much. > >

Bug#946721: python-levenshtein: tries to overwrite '/usr/share/doc-base/python-levenshtein'

Source: python-levenshtein Version: 0.12.0-4 Severity: serious Justification: Fails to upgrade Hi! While updateting the package I get: Preparing to unpack .../python3-levenshtein_0.12.0-4_amd64.deb ... Unpacking python3-levenshtein (0.12.0-4) over (0.12.0-3+b2) ... dpkg: error processing archive

Bug#945489: closed by Sylvestre Ledru (Bug#945489: fixed in llvm-toolchain-9 1:9.0.1~+rc2-1~exp1)

Hy Sylvestre! On 19/12/07 04:15, Debian Bug Tracking System wrote: [snip] > Format: 1.8 > Date: Tue, 03 Dec 2019 07:56:16 +0100 > Source: llvm-toolchain-9 > Architecture: source > Version: 1:9.0.1~+rc2-1~exp1 > Distribution: experimental > Urgency: medium > Maintainer: LLVM Packaging Team >

Bug#945225: cppreference-doc: Fails to build from source: tries to install not generated qch file.

Source: cppreference-doc Version: 20170409-1 Severity: serious Justification: FTBFS Hi! Your package is currently trying to install a file no longer created since Qt4 support was dropped. There seems to be Qt5 build dependencies, so maybe something else is going on. If you need help please pin

Bug#875250: Bug#875258: [scim] Future Qt4 removal from Buster

Hi Rolf! On 19/11/10 10:41, Moritz Mühlenhoff wrote: > On Sun, Sep 08, 2019 at 03:31:29AM +0800, Tz-Huan Huang wrote: [snip] > > Hi Rolf, > could you have a look/do an upload? Once the qscintilla migration is complete, > scim will be the last remaining key package blocking the removal of Qt4 >

Bug#907231: Ping - ktp-contact-list FTBFS

Hi! El vie., 15 nov. 2019 10:45, John Scott escribió: > ktp-contact-list has been kept out of testing for over a year, though this > issue is fixed by the patch and new upstream version. If help is wanted > with this, please let it be known. > I'll be happy to sponsor a fix, feel free to send

Bug#943331: qgis: FTBFS with Qt 5.12.5

Source: qgis Version: 3.4.12+dfsg-1 Severity: serious Justification: FTBFS Hi! Your package FTBFS while rebuilding it against Qt 5.12.5, although from the build log I can not tell for sure if the problem lies in Qt itself. An excerpt from it: FAILED:

Bug#875065: [odin] Future Qt4 removal from Buster -> odin is ready for Qt5

Hi! El sáb., 12 oct. 2019 03:09, Andreas Tille escribió: > I can do so not before November 4th, Andreas. I'm really under scheduled with sofa, but whenever I have time I'll try too

Bug#939687: clazy: FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'

Hi! El sáb., 5 oct. 2019 07:27, Graham Inggs escribió: > Hi Lisandro > > I believe this may be related to the recent switch from GCC 8 to 9. > > "GCC 9 also passes the linker option --as-needed by default; typical > build issues are passing libraries before object files to the linker, > or

Bug#875184: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

I've created a WIP merge request at https://salsa.debian.org/med-team/sofa-framework/merge_requests/1 I could solve TinyXML (at least in the aspect of finding it, I might need to adjust something else later on) but came across libgtest-dev... It ships static libraries! I would have to check

Bug#875184: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

On 19/09/17 10:17, Andreas Tille wrote: > On Tue, Sep 17, 2019 at 01:26:17PM -0300, Lisandro Damián Nicanor Pérez Meyer > wrote: > > > > Is the embedded stuff all in extlibs/? or is there some other 3rdparty code? > > A lot is excluded in advance from the packaging

Bug#875195: [stretchplayer] Future Qt4 removal from Buster

Hi! El mié., 18 sep. 2019 13:18, Reiner Herrmann escribió: > Control: tags -1 + patch > > Dear maintainers, > > porting stretchplayer to Qt5 was straightforward. > You can find a merge request on salsa [0]. > The patch looks great. I'll happy NMU it if you (the maintainer) agree. I'll also NMU

Bug#875184: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

Hi! El mar., 17 sep. 2019 17:17, Andreas Tille escribió: > On Tue, Sep 17, 2019 at 01:26:17PM -0300, Lisandro Damián Nicanor Pérez > Meyer wrote: > > > > Is the embedded stuff all in extlibs/? or is there some other 3rdparty > code? > > A lot is excluded in adv

Bug#875029: closed by Yves-Alexis Perez (Bug#875029: fixed in lightdm 1.26.0-6)

**Thanks**

Bug#939687: Help needed

tag 939687 + help thanks Hi! I'm afraid I'll need help with this one. -latomic is being passed, but it is still failing to build when it previously did. The only change was clang itself (and I wonder why clang is not automatically passing -latomic, as the arch seems to need it). Any help will be

Bug#875029: Ping!

Hi again! On Tue, 17 Sep 2019 at 13:23, Yves-Alexis Perez wrote: > > Yes I mind. I’m sorry my schedule doesn’t align with yours, but I honestly > don’t see the urgency here. I’m not asking you to wait for months, I’m just > trying to find some time to properly review and integrate Moritz

Bug#875184: Help needed for medical imaging framework sofa (Was: Bug#875184: [sofa-framework] Future Qt4 removal from Buster)

Hi! On 19/09/12 09:40, Andreas Tille wrote: > Control: tags -1 help > > On Sun, Sep 08, 2019 at 11:00:34PM +0200, Moritz Mühlenhoff wrote: > > On Sun, Sep 08, 2019 at 08:41:40AM +0200, Andreas Tille wrote: > > > On Sat, Sep 07, 2019 at 10:43:53PM +0200, Moritz Mühlenhoff wrote: > > > > > > > >

Bug#875029: Ping!

Hi! On Tue, 17 Sep 2019 at 12:49, Yves-Alexis Perez wrote: > > Please don’t, I already told Moritz I’ll handle it when I have time. That's just great! Do you mind if, once we get out of testing the two other blockers, we ask the RT to remove lightdm from testing? It will still re enter testing

Bug#875219: Should we file a removal bug?

Hi! We have seen no activity in this bug, should we file a removal bug? Cheers, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

Bug#875150: Should we file a removal bug?

Hi! It seems there is no activity on this bug, should we file a removal bug? Thanks, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

Bug#875144: Ping!

Hi Gudjon! Can you procede with this? It's one of the packages holding qt4 in testing. Thanks! -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

Bug#875029: Ping!

Hi Yves-Alexis! lightdm is now one of the three packages holding qt4 in testing. Would it be possible for you to apply the patch Moritz sent? If you can't I'll be happy to NMU it. Cheers, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

Bug#875029: [lightdm] Future Qt4 removal from Buster

On Mon, 16 Sep 2019 08:12:10 +0200 Yves-Alexis Perez wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Sun, 2019-09-15 at 23:26 +0200, Moritz Mühlenhoff wrote: > > > Attached is a patch which drops Qt4 support. It's only used by > > > src:razorqt, > > > which is already RC-buggy

Bug#874907: [hydrogen] Future Qt4 removal from Buster

Hi! El dom., 15 sep. 2019 09:49, Jonas Smedegaard escribió: > Quoting Lisandro Damián Nicanor Pérez Meyer (2019-09-12 23:54:32) > > On Thu, 12 Sep 2019 at 17:37, Lisandro Damián Nicanor Pérez Meyer > > wrote: > > > > > > On Mon, 30 Jul 2018 19:01:

Bug#874907: [hydrogen] Future Qt4 removal from Buster

On Thu, 12 Sep 2019 at 17:37, Lisandro Damián Nicanor Pérez Meyer wrote: > > On Mon, 30 Jul 2018 19:01:50 +0200 Reiner Herrmann wrote: > > Control: tags -1 + fixed-upstream > > > > The current upstream beta release supports Qt5. > > https://github.com/hydrogen-mus

Bug#874907: [hydrogen] Future Qt4 removal from Buster

On Mon, 30 Jul 2018 19:01:50 +0200 Reiner Herrmann wrote: > Control: tags -1 + fixed-upstream > > The current upstream beta release supports Qt5. > https://github.com/hydrogen-music/hydrogen/releases/tag/1.0.0-beta1 I'll see if I can tackle it during the weekend.

Bug#939687: clazy: FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'

On 19/09/07 08:58, Paul Gevers wrote: > Source: clazy > Version: 1.5-1 > Severity: serious > Tags: ftbfs > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Dear maintainer, > > During a binNMU of clazy during the llvm-defaults transition, you package > FTBFS > on armel. Can you please

Bug#939687: clazy: FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'

ke[1]: Leaving directory '/<>/obj-arm-linux-gnueabi' > dh_auto_build: cd obj-arm-linux-gnueabi && make -j4 "INSTALL=install > --strip-program=true" returned exit code 2 > make: *** [debian/rules:19: build-arch] Error 255 According to the web this seems to be lacking an -latomic flag to the linker, but I do wonder why it happens *now* and only on armel :-/ Has clang changed anything wrt armel? -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

Bug#939687: clazy: FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'

: cd obj-arm-linux-gnueabi && make -j4 "INSTALL=install > --strip-program=true" returned exit code 2 > make: *** [debian/rules:19: build-arch] Error 255 According to the web this seems to be lacking an -latomic flag to the linker, but I do wonder why it happens *now* and only on armel :-/ Has clang changed anything wrt armel? -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

  1   2   3   4   5   6   >