Bug#1059264: qbs: ftbfs on riscv64: test timeout

2024-03-02 Thread Bo YU

Hi,
On Sat, Mar 02, 2024 at 09:47:08PM +0300, Dmitry Shachnev wrote:

Hi!

On Thu, Feb 29, 2024 at 02:59:28PM +0800, Bo YU wrote:

Thanks for the hint. It seems it works once I enable
QTEST_FUNCTION_TIMEOUT. The value of it I just follow the [2] to set
`90` milliseconds (15 mins). But I am not sure the value is okay
for you.:)


Well, a test running for 15 minutes is not good, but as I said, it is
better than disabling it completely.


Thanks. The situation should be improved if we have more power riscv64
buildd, but unfortunately, we have to wait this for time.




I do not attend one debdiff file because now I have trouble to build
it on sid-riscv64-sbuild. Once done, I will update it here.


Looking forward to that.


Due to 2.1.2-2.1 was t64 transition related, so I have to generate
debdiff based on 2.1.2-2. So please let me know if any issue.

I should wait the 64 trsansition to finish but not sure how long it will
to achive this.


--
Dmitry Shachnev


--
Regards,
--
  Bo YU

diff -Nru qbs-2.1.2/debian/changelog qbs-2.1.2/debian/changelog
--- qbs-2.1.2/debian/changelog  2023-12-08 10:54:19.0 +
+++ qbs-2.1.2/debian/changelog  2024-02-28 07:19:35.0 +
@@ -1,3 +1,11 @@
+qbs (2.1.2-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Increase the timeout of qtest with QTEST_FUNCTION_TIMEOUT
+for riscv64. (Closes: #1059264)
+
+ -- Bo YU   Wed, 28 Feb 2024 07:19:35 +
+
 qbs (2.1.2-2) unstable; urgency=medium
 
   * Update debian/libqbscore2.1.symbols for loong64 (closes: #1057757).
diff -Nru qbs-2.1.2/debian/rules qbs-2.1.2/debian/rules
--- qbs-2.1.2/debian/rules  2023-12-08 10:54:19.0 +
+++ qbs-2.1.2/debian/rules  2024-02-28 07:19:35.0 +
@@ -3,6 +3,11 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
+CPU_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH_CPU)
+ifeq (riscv64,$(CPU_ARCH))
+export QTEST_FUNCTION_TIMEOUT=90
+endif
+
 include /usr/share/dpkg/default.mk
 
 BUILDPATH ?= obj-$(DEB_HOST_GNU_TYPE)


signature.asc
Description: PGP signature


Re: It's impossible to install KDE in unstable

2024-03-02 Thread Andrey Rahmatullin
On Sat, Mar 02, 2024 at 11:14:33AM +0100, Valerio Passini wrote:
> Hello,
> 
> I'm having a lot of troubles to install KDE in unstable, apt tells there
> are held packages but I've checked and there are not.
> 
> sudo apt install plasma-desktop
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  kactivitymanagerd : Depends: libqt5sql5 (>= 5.15.2~) but it is not
> installable
>  libkf5plasma5 : Depends: libqt5sql5 (>= 5.15.2~) but it is not installable
#1065154

>   Recommends: kio-extras but it is not installable
This can additionally be caused by kio-extras not rebuilt against
libsmbclient0 if you have libsmbclient0 installed.

> Is it a known problem?
sid is currently broken in general because of the ongoing t64 transitions
and problems caused by it.

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Re: It's impossible to install KDE in unstable

2024-03-02 Thread Patrick Franz
Hej Valerio,

Am Samstag, 2. März 2024, 11:14:33 CET schrieb Valerio Passini:
> Hello,
> 
> I'm having a lot of troubles to install KDE in unstable, apt tells
> there are held packages but I've checked and there are not.
[...]
> Is it a known problem?

Yes, this is due to the ongoing 64-bit time_t transition. Unstable is a 
bit broken while thousands of packages are rebuilt. Everything will 
hopefully sort itself out soon.

As a general advice: Be very careful with updates right now if you're 
running Unstable while this transition is going on.


-- 
Med vänliga hälsningar

Patrick Franz




Re: It's impossible to install KDE in unstable

2024-03-02 Thread Marc Haber
Hi,

On Sat, Mar 02, 2024 at 11:14:33AM +0100, Valerio Passini wrote:
> I'm having a lot of troubles to install KDE in unstable, apt tells there
> are held packages but I've checked and there are not.

it is called unstable for a reason. Unstable is going through a major
migration these days. It is perfectly normal for a huge package group
like KDE to be out of sync for some days. I'd start worrying if it's
still the same in two weeks.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421



It's impossible to install KDE in unstable

2024-03-02 Thread Valerio Passini
Hello,

I'm having a lot of troubles to install KDE in unstable, apt tells there
are held packages but I've checked and there are not.

sudo apt install plasma-desktop
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 kactivitymanagerd : Depends: libqt5sql5 (>= 5.15.2~) but it is not
installable
 libkf5plasma5 : Depends: libqt5sql5 (>= 5.15.2~) but it is not installable
 plasma-desktop : Depends: plasma-workspace (>= 4:5.27.10~) but it is not
installable
  Depends: libkf5activitiesstats1 (>= 5.102.0~) but it is
not installable
  Depends: libqt5sql5 (>= 5.15.2~) but it is not installable
  Recommends: kinfocenter (>= 4:5.27.10~) but it is not
installable
  Recommends: kio-extras but it is not installable
  Recommends: plasma-workspace-wayland (>= 4:5.27.10~) but
it is not installable
E: Unable to correct problems, you have held broken packages.

dpkg --get-selections | grep hold
gives nothing
Is it a known problem?

--