Bug#1064139: Bug #1064139 ogre-1.12: FTBFS: error: ‘BuildFontAtlas’ is not a member of ‘ImGuiFreeType’

[Flavien Bridault]

Dear maintainer(s),

I took a look at the latest version of Ogre which is probably compatible 
with latest ImGui and it seems this line is no longer necessary. It was 
removed before the release 13.0.0 when upgrading to ImGUI 1.83 : 
https://github.com/OGRECave/ogre/commit/17b7481057b97662a3752ee605ea77a9eb0c57db


Patching should be then fairly easy...

I can offer my help again, like I did to upgrade to 1.14 
(https://lists.debian.org/debian-devel-games/2023/11/msg1.html), 
which whould really be the best option in the end... Maybe I will have 
an official answer this time ? I don't want to be sarcastic at all, but 
I strongly depend on Ogre to build sight and this is annoying to get no 
answer from the devel games team. And currently my package sight is 
currently marked for autoremoval because of this bug 
(https://tracker.debian.org/pkg/sight)


Kind regards,

--

*Dr. Flavien BRIDAULT*
Director of Software Development
IRCAD France & IRCAD Africa

flavien.brida...@ircad.fr 
Tél. : +33 (0)3 88 119 201
IRCAD France
http://www.ircad.fr/
http://www.ircad.africa/ 

Suivez l'IRCAD sur Facebook 



*IRCAD France*
Hôpitaux Universitaires - 1, place de l'Hôpital - 67091 Strasbourg Cedex 
- FRANCE




OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065416: [Cross-toolchain-base-devs] Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Bastian Blank]

Hi Helmut

On Tue, Mar 05, 2024 at 09:50:27AM +0100, Helmut Grohne wrote:
> The problem arises in the reverse sense. If a file does not exist in
> one, it is searched in the second and erroneously may be found. That may
> make tests pass that should not pass and typically causes a link failure
> later.

But you want /usr/include to be found.  Otherwise you would not be able
to use most of the libraries for cross compiling.

>  . While I do not have a concrete example at hand, I have seen this
> pattern repeatedly and generally favour moving stuff out of /usr/include
> to avoid this kind of confusion that causes difficult to debug problems.
> This also motivates #798955 (in addition to the problem with file
> conflicts).

In this case here, this would just find kernel headers for a different
version.  Those are essentially a headers only library, nothing is
available for linking.  And all the headers provided in /usr/include are
the same for all architectures.

So moving stuff out of /usr/include might be a good idea if the -dev
package is itself arch dependent.

> The one case I really do remember quite well is sanitizers. These should
> not be enabled in the earlier toolchain stages and failing to disable
> them tends to cause linker failures. I don't think it matches the
> concrete situation exactly though. You also make a good case in your
> followup reporting that gcc-13-cross actually builds.

Yep.  My problem is: I tested stuff, not everything of course, and did
not see any breakage.  Also I checked the values I know could influence
that and they say it is fine.  So at some point I have to assume it is
not broken, as exhaustive search is simply not possible.

The only statement in this bug report is now: it is located in a
different location, so it is broken.  No single piece of evidence is
shown, like broken builds or some other ways to see the brokeness.

Regards,
Bastian

-- 
A princess should not be afraid -- not with a brave knight to protect her.
-- McCoy, "Shore Leave", stardate 3025.3

Bug#1064824: marked as done (node-d3: fails to export map and probably other functions)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 06:50:18 +
with message-id 
and subject line Bug#1064824: fixed in node-d3 5.16.0+~cs5.28.10-2
has caused the Debian Bug report #1064824,
regarding node-d3: fails to export map and probably other functions
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjs-d3-tip
Version: 0.7.1-5
Severity: important

I have tried to use d3-tip.min.js for a website in another package,
but it fails with the error: "Uncaught (in promise) TypeError: h.map
is not a function".  This comes from the index.js line "d3.map({
...".  Presumably d3 no longer ships a map function.  In more recent
versions of d3-tip (which is now archived), this has been resolved by
importing "map" from d3-collections.  So maybe the best way to fix
this bug is to upgrade the package.

Best wishes,

   Julian
--- End Message ---
--- Begin Message ---
Source: node-d3
Source-Version: 5.16.0+~cs5.28.10-2
Done: Julian Gilbey 

We believe that the bug you reported is fixed in the latest version of
node-d3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julian Gilbey  (supplier of updated node-d3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 06 Mar 2024 06:13:04 +
Source: node-d3
Architecture: source
Version: 5.16.0+~cs5.28.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Julian Gilbey 
Closes: 1064824
Changes:
 node-d3 (5.16.0+~cs5.28.10-2) unstable; urgency=medium
 .
   * Team upload
 .
   [Julian Gilbey]
 .
   * Fix lintian-overrides and add DEP-3 headers to patches
 .
   [Nilesh Patra]
 .
   * Do not export map from d3-array (which is a newer version than d3
 expects), so that the d3-collection version of map is exported
 (closes: #1064824)
Checksums-Sha1:
 d08f43eb1b233ac152cc029c0dc7791e892a8ecd 4044 node-d3_5.16.0+~cs5.28.10-2.dsc
 26bd77db36423d36f2bd01b9ebab8731251a10ad 6504 
node-d3_5.16.0+~cs5.28.10-2.debian.tar.xz
 5b1ed4939bdc0ed792724d4e46b2c452d8edc413 18031 
node-d3_5.16.0+~cs5.28.10-2_amd64.buildinfo
Checksums-Sha256:
 bb22cadb4312236e5586dc12eb44196de9ca910bcd6ff94ce0392575c3a4cfa0 4044 
node-d3_5.16.0+~cs5.28.10-2.dsc
 18d80bc1bea0f28a87eddb5a9bd19d15b248318a2e941e6924da3f02e8ccd447 6504 
node-d3_5.16.0+~cs5.28.10-2.debian.tar.xz
 78811b5f682cc1614f4061f1710b4c1c6c2fa1523e4bbed97f4cee28650ad0b2 18031 
node-d3_5.16.0+~cs5.28.10-2_amd64.buildinfo
Files:
 195254fb464f5e18ed328f2634aaf46f 4044 javascript optional 
node-d3_5.16.0+~cs5.28.10-2.dsc
 3428353dc382b67f69e0c6dcb1db0036 6504 javascript optional 
node-d3_5.16.0+~cs5.28.10-2.debian.tar.xz
 a634f67be1981ba0581a80452728c3a6 18031 javascript optional 
node-d3_5.16.0+~cs5.28.10-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmXoCuMPHGpkZ0BkZWJp
YW4ub3JnAAoJEGlcQpMWwHv+bI8P/0LmXM4p4DB/SYhGYumCInZFqZRDRpfwGcQh
MqSne7o/cBRJjh9c9sytXH66ULIvbJl+03oWBYMEmcJbynn45img9U7zjnQHN/bA
2Wjbkur5ExC/oKVyV8gmGzfA/d0YIccyNYIO7C3JEEYaSy7LNEAqtnjuLxWBPyrL
cBRC4gq8HwRrsPjbkB1bHnfW45gtaVa/S2bysjb20iwHUML67C0LLQ984TzJ7v5B
YGBBaoKu6nmV8BRGDuKWCs23WPixb85pDNYpzDapuM9TQX4bUccOoG3uBoQV1sY/
po0h4iFbs+WBunFmyMg+TMlves2oxuF/JwfREfNby4+BhrmzmmaTzwWnEYiHFuFb
c5C0HaN5ocigeY3+Nq0yyKyqRSD4DU2MbxAFmXoELjWm/ashwinVJt2R67Bkh/KR
hp+UO2/MnQi/neXOdaN8uQOFKSzgK5etIXN0U06LqAzS1CDbfxn4ezLGZij88OJ0
I1P53zQmRf4Groas+3vx0ePpk3a+76C1Izy1GF5B1KZ9WzWNZqab5Ai3Kxz7ASWU
t3s3ec6aAbRobIxVDqEh+8gCyzZbqAvp5IFxtPielRgVw/L44mNig97UUEhDkiaf
wacRL0wICPVeeQL6FauQENAC5HYUdnDZ24aE5DFICVAoslZlnZofPp9XElFFqTLW
TVu1KmHb
=cqlJ
-END PGP SIGNATURE-



pgpjAhKBURowO.pgp
Description: PGP signature
--- End Message ---

Bug#1057548: cloud-init: FTBFS: failing tests

[Ross Vandegrift]

Control: tags -1 pending

On Mon, Feb 19, 2024 at 01:47:24PM -0800, Ross Vandegrift wrote:
> On Tue, Dec 05, 2023 at 11:04:12PM +0100, Santiago Vila wrote:
> > During a rebuild of all packages in unstable, your package failed to build:
> 
> I started updating to the latest upstream release, which fixes this FTBFS.  
> But
> I'm reluctant to push to the team repo, due to an issue with the network
> nocloud datasource.
> 
> With a local webserver hosting cloud-init seed data, cloud-init 23.4.3 never
> hits my local http server.  The same setup with 23.3.1 from sid works fine.
> Disk based nocloud seeds work fine with 23.4.3.

Upstream found and fixed this issue in 23.4.4  But before I could get to
packaging it, they also released 24.1.  I just pushed updates with the new
version to salsa.  The new version is working for me.

I don't have upload access for cloud-init - we can work out an upload at the
team meeting next week.

Ross

Processed: Re: Bug#1057548: cloud-init: FTBFS: failing tests

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1057548 [src:cloud-init] cloud-init: FTBFS: failing tests
Added tag(s) pending.

-- 
1057548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1063596: flint: FTBFS on amd64: test segfault

[Paul Gevers]

Hi Julien,

On Sat, 24 Feb 2024 14:40:13 +0100 julien.pu...@gmail.com wrote:

A case of eigenbug where you compile three times and it only fails one?


If it's one in three that would be too much. For ci.d.n I'm having my 
"flaky" bug filing threshold between 1/5 and 1/8, but I think it should 
be below something like 1/20 to say it's acceptable if it's caused by 
the package itself. If not caused by the package itself, but toolchain 
issues, those really should get a decent bug and get fixed.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065395: spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space

[Paul Gevers]

Hi Andreas,

On 05-03-2024 10:16 a.m., Andreas Beckmann wrote:
But first I'd like to see the s390x build happen and your confirmation 
that this unbreaks the CI infrastructure. But at least ppc64 and sparc64 
built with 500MB instead of 40GB now ;-)

Feel free to block 15-17 temporarily, too.


Unfortunately the test still takes upto 33 GB at least (see below).

Paul
By the way, I just noticed this in the -14 log (judging from the name of 
the test I think that's intentional, but just checking (installing from 
the -16 package instead of the -14 one):
Get:2 http://deb.debian.org/debian unstable/main s390x spirv-headers all 
1.6.1+1.3.275.0-1 [118 kB]



root@ci-worker-s390x-01:~# while true ; do df -h /scratch/ | grep mapper 
; sleep 10 ; done
/dev/mapper/3600507630affd250004a  196G   27G  160G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   27G  160G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   27G  160G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   27G  160G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   27G  160G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   27G  160G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   27G  160G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   27G  159G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   28G  159G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   28G  159G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   28G  159G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   28G  159G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   29G  158G  16% 
/scratch
/dev/mapper/3600507630affd250004a  196G   29G  158G  16% 
/scratch
/dev/mapper/3600507630affd250004a  196G   29G  158G  16% 
/scratch
/dev/mapper/3600507630affd250004a  196G   29G  158G  16% 
/scratch
/dev/mapper/3600507630affd250004a  196G   29G  157G  16% 
/scratch
/dev/mapper/3600507630affd250004a  196G   29G  157G  16% 
/scratch
/dev/mapper/3600507630affd250004a  196G   30G  157G  16% 
/scratch
/dev/mapper/3600507630affd250004a  196G   30G  157G  16% 
/scratch
/dev/mapper/3600507630affd250004a  196G   28G  159G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   28G  159G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   28G  159G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   28G  159G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   29G  158G  16% 
/scratch
/dev/mapper/3600507630affd250004a  196G   34G  153G  19% 
/scratch
/dev/mapper/3600507630affd250004a  196G   44G  143G  24% 
/scratch
/dev/mapper/3600507630affd250004a  196G   53G  133G  29% 
/scratch
/dev/mapper/3600507630affd250004a  196G   62G  124G  34% 
/scratch
/dev/mapper/3600507630affd250004a  196G   70G  117G  38% 
/scratch
/dev/mapper/3600507630affd250004a  196G   28G  159G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   28G  159G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   28G  159G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   29G  158G  16% 
/scratch
/dev/mapper/3600507630affd250004a  196G   27G  160G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   27G  160G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   27G  160G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   27G  160G  15% 
/scratch
/dev/mapper/3600507630affd250004a  196G   27G  160G  15% 
/scratch


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1057549: crowdsec: FTBFS: FAIL: TestOneShot/permission_denied

[Cyril Brulebois]

Cyril Brulebois  (2024-02-15):
> Is that problem still current? I cannot reproduce it with a brand new
> sid environment, freshly created via either `pbuilder --create` or
> `sbuild-createchroot`.

For the record, I did receive a proposal to get access to such a system
back then (thanks!), but I couldn't get to it just yet.

Not sure about this though, received today (2024-03-06) for 3 packages:

crowdsec 1.4.6-6 is marked for autoremoval from testing on 2024-03-05 


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature

Bug#1053004: CVE-2019-10784 and CVE-2023-40619

[Leandro Cunha]

Hi,

On Sat, Nov 11, 2023 at 2:53 PM Leandro Cunha  wrote:
>
> Hi,
>
> According to a survey carried out, it was found that the OpenSUSE
> people resolved these CVEs and started distributing the fork
> https://github.com/ReimuHakurei/phpPgAdmin. According to the links
> below:
> https://lists.opensuse.org/archives/list/security-annou...@lists.opensuse.org/message/4YEBNCIRQOKETS4R7J5GXRP3TKF2YKFJ/
> https://build.opensuse.org/request/show/1123216
>
> I'm working on doing the same for Debian, currently testing and
> reviewing the package. At the same time, the libphp-adodb package will
> receive an NMU to be compatible with PHP 8.2 according to the website
> https://adodb.org/dokuwiki/doku.php?id=v5:php_compatibility_status and
> https://bugs.debian.org/ cgi-bin/bugreport.cgi?bug=1053525.
>
> --
> Cheers,
> Leandro Cunha

Just to add that in addition to OpenSUSE Tumbleweed and Leap
15.5/15.6, we have FreeBSD, AUR and Gentoo currently distributing this
package from the same source as can be seen in the links below. The
next job would be to make it available through backports and I would
choose to remove this package from stable. But I would only leave
bookworm backports due to other bugs found (this CVEs too) and fixed
in 7.14.7.
I have to search about the status of backports to oldstable. But I'm
also studying the possibility of working with patches for these two
versions.

[1] https://repology.org/project/phppgadmin/versions
[2] https://software.opensuse.org/package/phpPgAdmin
[3] https://build.opensuse.org/package/show/home%3Aecsos%3Aserver/phpPgAdmin
[4] https://build.opensuse.org/package/show/openSUSE%3AFactory/phpPgAdmin
[5] https://www.freshports.org/databases/phppgadmin
[6] https://packages.gentoo.org/packages/dev-db/phppgadmin

-- 
Cheers,
Leandro Cunha
-BEGIN PGP PUBLIC KEY BLOCK-

mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN
pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh
0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR
gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd
A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas
sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb
RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7
ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD
w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S
eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm
hjAM8s+rUtG40mcUWePd8kZtgE9IV1eQ+Qt8/SNpSdRnUunmIGl3JjHvEwARAQAB
tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT
AQoAOBYhBLT5oBCvKN3HzFEPK8LZ4zKUW9A8BQJf4EPIAhsDBQsJCAcCBhUKCQgL
AgQWAgMBAh4BAheAAAoJEMLZ4zKUW9A8FjAQAKWYqiLpLUD+DLB+NSy3DI3rf9z3
k0vE7TLaEjdEM5CQWN+j4vBqMnAckdcARvSWPndTjp8K+mtFF4PyfhNbS64z/a7L
F3DdhmX73n7LKFG8Ow9NZwcrkmPwH5WcP7mXTh6R+6/+OSL/K85NB8MLlxQTJOni
julVax9JEZjwBaP2HLCu53Zq9gZcvJlXoAoTHyTxKdp8Mh8V+Qit26E78o9c6SQD
Dq9eyMRG8hYCRfreDjKceRkYHjECySlk+VoI1ssVs07Dqvxg6qSyP4RnW+1+W74C
s0yIyuC/eRJpMAf1PBQEOOrVcTfRfpN+go955t21yIAvT58vqotTM5eaqXYIQn/y
sC4lThZai/ZBZHxl5Mbv42WkkYdjisLQOCALIMBpj5nq4oh2C+kvMupcuBKfERgV
dguU51MzfQktKb6d5y777zYnDaFMQDD2IfiD/C7ln5A9LP/L54ixlA3uRmWx/yAx
/m+Zusws98j4Eq/jw5T54XW655m6lMCTE9WXLJkgxrRcEonHSllbgRSsToEmWq0Z
doxcnpagHdcGQzW+cu2VOGi1da73ZFmrn+ptJgc8cW2suO06IeArOi0TzIg7e65j
Xp2DbJCpFrfzEuBb1u71WvB8V2MkAfJZx/uZJPCA936B4HT8YGPEMzlQRIHI2Y9C
+DloyzlBLTS1EMKuuQINBF/gQ8gBEAC47o9u1Wm9jZ6RC+lfxEDEvVS7MmI5VzSy
q04rFttWwbKix13pc65aDlk47LxWrb84N3Gnf1E/OTsLTXqC7u5JZ7YJkC6CsPbo
D1sQkfCiJCFCTgf7dydEVt8ujS/Uu1kz86ufdRwaMRcvBZAORGdB58LEsLB65WN4
hLRYF7xvcxu6t7FGrIYereaxUAWLA2B/ZnCEdOY94w7s0uaPjHdf4lfHebuZ7T08
iG5ACDvKBjgaFArGfdNYWchXJgbOEg14bGj40/8LuBKQMZASiFSqLPZxoporK9FY
xBw+D080dUWWD5g868TZ3pkM3DXO9bdq22IBKqKOep8CnuKgoDpUvA8dTEY/UDCn
sdOlBUK/Y9zTGVmD/90cO/xkvkV78suqiBnwBSddPzVS0EuiWwrLGu8gaY4EyM/X
7khlbTcMgh4njzUCAE6Tq+TbXSxn86wuOybVY5Y+I99LNdsocI5SIn2nDh2IOi00
4dE/iwO2MatWIOLFBC7pw8Xv4UHZY+WIf3Y/6XjExpllhUkeB6BwZpTr1SXk+cug
q5Dj5i4aGn2LrvQJ57terqUWYyDUBFgXTc4SPOzT5og8CavBgHfrQoFwSnRZ2oyX
xtZhEDI5Pk2j1qTbOhXZ29po4rPNWHMq2HQgM0I+BqQndsoVdkPOFzS2wKkdXjCz
bNYcyanusQARAQABiQI2BBgBCgAgFiEEtPmgEK8o3cfMUQ8rwtnjMpRb0DwFAl/g
Q8gCGwwACgkQwtnjMpRb0Dzh6g//ZjXaWSzKmG5ZS6XJa/ZOokkE2hFOFusWX8Qa
hEwLAnTFEy02dLfV54rKwmu2jHPDKLhE+iYtusvytueZAzVRyQahv0RE4BH8Emqw
gQdBwyJ/L+QhUp/lMdJ6Hh/2ZSZmzU29U24vnY+U+haoB1fLnA3lXgOP59kMLGud
lERR2Vluuc7TcpzvcaRWgrQRU2vSrrBBEp6y07iVKbRM/9yhE/aHJahLbhKh2Dk9
WJvHPnhYJY5yU+Y5vTl3BiW5+EuzMBdPUawOWKhqCq9dswn0GL1g/vlt/bdU/6DO
jECQ6fssTAtDjRClXySsS3X0mh8y8qlGvMPB4anfvOy4+4nUV6IESdJftKn2SMGd
CA3MaQ+S7frWn5v7GIWSC9vumCsiu1JTOugLmbVmu5m5nFsyllavm/k9LtOtswuF
fHM/SlXLFuGBWU6XceqaM2dpP8i5jGz0vIGMhqoFNgXWGO1NhwR1rmeU1CMpnM5e
Wue4h/+mJiuEzuZcmzOcwq3HGMUXO0jZDgLEmlnenO9czhrLuGZaMXGdwnIk0G3O
+SqH36v7blnDh96RXpgaa+ifTHd0qKeoVXVwSq/9jNtHSQrI+NJcTpMhu73xtxhX
UFPr/31+IFLWepC5GDwdu/gQm5E6ntGyxE2p2v76pcjz7SGdXjPFZjqekBveEJuW
fNdY6Ns=
=rdCA
-END PGP PUBLIC KEY BLOCK-

Bug#1064852: marked as done (incus: missing depends on iproute2)

[Debian Bug Tracking System]

Your message dated Wed, 06 Mar 2024 03:19:20 +
with message-id 
and subject line Bug#1064852: fixed in incus 0.6-2
has caused the Debian Bug report #1064852,
regarding incus: missing depends on iproute2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: incus
Version: 0.6-1
Severity: serious
Justification: missing dependency

After installing incus any "incus *" command (even incus info) just
hangs with no indication what's wrong. journalctl -u incus eventually
reveals:


Feb 26 16:47:45 testvm incusd[685]: Error: exec: "ip": executable file not 
found in $PATH

After installing iproute2, incus starts and incus commands start
working.

Helmut
--- End Message ---
--- Begin Message ---
Source: incus
Source-Version: 0.6-2
Done: Mathias Gibbens 

We believe that the bug you reported is fixed in the latest version of
incus, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mathias Gibbens  (supplier of updated incus package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 06 Mar 2024 02:48:38 +
Source: incus
Architecture: source
Version: 0.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Mathias Gibbens 
Closes: 1064852 1065174
Changes:
 incus (0.6-2) unstable; urgency=medium
 .
   * Fix incus-agent injection if $PATH is set in /etc/environment
 (Closes: #1065174)
   * d/control:
 - Add Depends on iproute2 (Closes: #1064852)
 - Suggest bash-completion in incus-client
 - Set minimum version of golang to aid backporting
   * d/rules:
 - Remove unneeded override of dh_installinit
   * Don't print install message on upgrades
Checksums-Sha1:
 9fd54b53ce4f7eebc3ebfd420217d11dcbd5087e 4378 incus_0.6-2.dsc
 27322e86b35309bd5d76cce69a6891e0013801c8 4178483 incus_0.6.orig.tar.gz
 34055f356811e3d7d46180ac9b81dc5b109ceadd 13700 incus_0.6-2.debian.tar.xz
 569672f61b71cf38686f494b77dd906565694df5 20565 incus_0.6-2_amd64.buildinfo
Checksums-Sha256:
 fffeab37de3f2d91682d51ca0a637f4453b219fd7e33c03d067297c302f4522a 4378 
incus_0.6-2.dsc
 c5f09016bcb4b2e3299e1d1bae3345071ca80ddc9f9f27eb6f873ae9f968e040 4178483 
incus_0.6.orig.tar.gz
 bfd9dc360837b09f48e079cf20a379cc5ee4b4b9f41c4a942d09f221359f0a44 13700 
incus_0.6-2.debian.tar.xz
 43c8eb5019d96076cbcfbca060f8b59ab7cb763d2f392f37d13eeefee6832857 20565 
incus_0.6-2_amd64.buildinfo
Files:
 ea8e8f6d00949c9d56131753ed8a35cb 4378 admin optional incus_0.6-2.dsc
 9b9c6b1723f5104787a102011feb696e 4178483 admin optional incus_0.6.orig.tar.gz
 d14250372fde3b9b583752e71ab57bfa 13700 admin optional incus_0.6-2.debian.tar.xz
 9a713dd28085652949c2f1de3f9972f4 20565 admin optional 
incus_0.6-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE1Bp60H32xfynSJ8cKe7i1uz0QvkFAmXn3RcSHGdpYm1hdEBk
ZWJpYW4ub3JnAAoJECnu4tbs9EL5ntwQAJU2BpsdSwpFLs2KO+1x7aQn7DNrmT3H
e2jHSq0HeHcHU5+LFta8QGAQzGZqLylQmfdvVfNhfeGluxOj20giCbhZXdacRJ5X
R8O8HIyA5PQuH59zl+BhDwIS1LBiPC0PYtlLWgbCJV+4Nf7Ig+4j2wbzdIxzkPre
31eA4zwom5h6SHs2zeDAMG53khubgXfgUu+RX1fQ2msJToHFQpCIszEEXT/nET9v
AoGsnOUmZ2/9BANptSko4JDe/3Vq6/ZKceVetno/QtdzJ401790qJQrEQBnlmusB
QPR9bzdNihDvTmbwNX/ccHp3QV0fqTRtbIaku1XIGMe3+NSGk3ZmJECdBrmc/3ND
aM9nopS2qjbJySz4BsBq76H5Lf+6xYbgLmYxtyFqgxSjCUNQGVw2Q/6G4y7n6h/5
EAmi6oM3G2nglzMFzeYdyRVyrErkitPw4401wH1tu4zgapRJwRDfwnCCuWjB0ApB
FvV86udSbaq8inmWsyj842m5BSB88+RDhATRzPJR/hRg7HvxMx0voQyN96X2FfT1
UOaT8BS5VjdLx80Q63XKfFywR827+4evS5hRvCfhB1rx1LqNC+ITv/zfGRbfzmX2
+W6Bj1OHQIYevxdVQh0VeQwqdbhr0UfnfJo7lNkRZGARB0XP6igUI+7w2lEOsHOp
m6q+puzt5f+e
=6UtP
-END PGP SIGNATURE-



pgpJ4XwScTnc0.pgp
Description: PGP signature
--- End Message ---

Bug#1064852: incus: missing depends on iproute2

[Mathias Gibbens]

On Tue, 2024-03-05 at 14:19 +0100, Helmut Grohne wrote:
> debvm-create --include=incus
> # This should have created a file named rootfs.ext4.
> debvm-run

  Thanks for sharing that!

> Rather than adding debvm on top of your testing, I think adding
> autopkgtests with isolation-machine should get you more automatic
> coverage. Possibly such tests need to be explicitly allowed by debci
> folks and currently are only available on amd64.

  Yes, it would be nice to get better autopkgtest coverage for incus,
lxc, and lxcfs. I'll add it to my todo list for these packages. :)

Mathias


signature.asc
Description: This is a digitally signed message part

Bug#1063484: libuv1: CVE-2024-24806

[Salvatore Bonaccorso]

Hi Dominique,

On Sun, Mar 03, 2024 at 03:51:28PM +0100, Dominique Dumont wrote:
> On Thu, 29 Feb 2024 21:53:07 +0100 Salvatore Bonaccorso  
> wrote:
> > libuv1 is as well affected in bullseye and it's still supported. Can
> > you have a look as well at this version? 
> 
> The same patch (with a refresh) applies to bullseye. I can also prepare an 
> upload.

The debdiff for bookworm-security looks good to me. Please do upload
to security-master (and make sure to build with -sa as the orig
tarball is not yet on security-master for 1.44.2).

So we just need as well the bullseye-security one, as per above, can
you prepare this one as well.

Regards,
Salvatore

Bug#1065477: [Pkg-owncloud-maintainers] Bug#1065477: owncloud-client: Uploads to unstable must have a higher version than present in unstable.

[Sebastian Ramacher]

On 2024-03-05 16:01:10 +0100, Sebastian Ramacher wrote:
> Hi
> 
> On 2024-03-05 15:42:49 +0100, Pierre-Elliott Bécue wrote:
> > Hello,
> > 
> > Sebastian Ramacher  wrote on 05/03/2024 at 
> > 09:38:13+0100:
> > 
> > > Source: owncloud-client
> > > Version: 4.2.0.11670+dfsg-1.1
> > > Severity: serious
> > > Tags: ftbfs
> > > X-Debbugs-Cc: sramac...@debian.org
> > >
> > > Version check failed:
> > > Your upload included the binary package dolphin-owncloud, version 
> > > 4.2.0.11670+dfsg-1.1, for amd64,
> > > however unstable already has version 5.0.0-1+b1.
> > > Uploads to unstable must have a higher version than present in unstable.
> > >
> > > Cheers
> > 
> > owncloud-client has been uploaded far before in the past, and was
> > shipping dolphin-owncloud, nautilus-owncloud, et al.
> > 
> > In client v5, upstream removed these packages from the owncloud-client
> > source, and therefore they're now packaged through dedicated source
> > packages.
> > 
> > These ones are the latest uploads.
> > 
> > I'll upload the v5 version of owncloud-client source package which won't
> > ship dolphin-owncloud et al anymore.
> > 
> > It's what's been suggested to me, and therefore I can't see a bug here.
> > 
> > Could you give me a bit more intel aobut why this would be a serious
> > bug?
> 
> The uploads by the buidds fail to be included in the archive since the
> constraints are not satisfied. You can check the reject files for the
> changes files from owncloud-client on coccia.d.o.
> 
> You can also see on
> https://buildd.debian.org/status/package.php?p=owncloud-client&suite=sid
> that the package is stuck in Uploaded state due to this issue.

FWIW, the dolphin-owncloud binary package is provided with a higher
version number by owncloud-client-desktop-shell-integration-dolphin. I
suppose the dolphin-owncloud package can just be dropped from
owncloud-client.

Cheers
-- 
Sebastian Ramacher

Bug#1064824: node-d3: fails to export map and other functions

[Julian Gilbey]

On Tue, Mar 05, 2024 at 05:39:00PM +0530, Nilesh Patra wrote:
> On Mon, Mar 04, 2024 at 09:18:01PM +, Julian Gilbey wrote:
> [...]
> > (!) Conflicting re-exports
> > "index.js" re-exports "map" from both 
> > "../../../usr/share/nodejs/d3-array/src/index.js" and 
> > "../../../usr/share/nodejs/d3-collection/src/index.js" (will be ignored).
> > created dist/d3.min.js in 4.2s
> > -
> 
> I have pushed a commit to salsa that hopefully fixes this - can you please 
> try with the same and see if that
> helps you somewhat?

That's perfect, thanks!  And such a simple solution :-) (Though I
don't pretend to understand how the patch works!)  The taskflow
webserver now works exactly as intended (as far as I can tell).

> > So it's specifically "map" that is problematic, and I just happen to
> > have stumbled upon it: d3 v5 depends on d3-array version 1, but the
> > version of node-d3-array in unstable is 3.2.0+~cs5.0.6-2, and this is
> > causing the conflict.
> > 
> > I don't know the best way to fix this.  node-d3-array version was
> > upgraded from 1.2.4 to 3.x about two years ago, so d3 would have had
> > this bug since then, but I'm the first one to stumble upon it :-/
> >
> > Perhaps we could package node-d3-array-1 (version 1.2.4) and have
> > node-d3 build-depends on that?
> 
> I tried to embed it and realised it is creating an unholy mess. I got it 
> working eventually
> but it can open a can of worms sometime later. Maybe packaging the older 
> version
> would be the way to go if my fix above does not work.
> 
> I've added yadd to the thread for more qualified advice.

It might be a good idea to do this anyway, but given that no-one else
has noticed a problem in > 2 years suggests it's not worth the effort.

Best wishes,

   Julian

Bug#1064852: incus: missing depends on iproute2

[Helmut Grohne]

On Tue, Mar 05, 2024 at 12:00:15PM +, Mathias Gibbens wrote:
> to add iproute2. I would be interested to know more about what
> environment Incus is being used in that doesn't have the `ip` command
> available.

debvm-create --include=incus
# This should have created a file named rootfs.ext4.
debvm-run

>   My normal testing setup for Incus is a fresh, minimal expert install
> of sid via the netinst iso. During the install of the VM, I only
> install the base system and deselect the "standard system utilities"
> group. I do use DHCP, which looks like that might be responsible for
> pulling in iproute2 for me. If there's a way to create an even more
> minimal install, I'd be happy to incorporate that into my testing
> routine.

Turns out your minimal expert install is not so minimal. debvm tends to
give you a smaller but still functional installation. I think adding
--variant=important to debvm-create roughly gets you the minimal expert
installation, but creating the machine takes slightly longer and uses
more disk space of course.

Rather than adding debvm on top of your testing, I think adding
autopkgtests with isolation-machine should get you more automatic
coverage. Possibly such tests need to be explicitly allowed by debci
folks and currently are only available on amd64.

Helmut

Bug#1065416: [Cross-toolchain-base-devs] Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Helmut Grohne]

Hi Bastian,

On Mon, Mar 04, 2024 at 11:04:22PM +0100, Bastian Blank wrote:
> > Arguably, a cross toolchain build should probably search
> > /usr/include/. I went back and forth a bit with Matthias
> > about whether we could add this and did not fully understand his
> > reasons, but there is one technical reason we want to avoid it for now.
> > We can have both libc6-dev:TARGET and libc6-dev-TARGET-cross installed
> > and these packages can have differing versions. When that happens and we
> > search both /usr//include and /usr/include/, we'd
> > mix two glibc versions with usually bad results (been there).
> 
> But this is a search path.  If a file exists in one, the second one is
> not found.  So nothing can happen even from version skew.

The problem arises in the reverse sense. If a file does not exist in
one, it is searched in the second and erroneously may be found. That may
make tests pass that should not pass and typically causes a link failure
later. While I do not have a concrete example at hand, I have seen this
pattern repeatedly and generally favour moving stuff out of /usr/include
to avoid this kind of confusion that causes difficult to debug problems.
This also motivates #798955 (in addition to the problem with file
conflicts).

> > The other aspect here is that it is not sufficient to add
> > /usr/include/ to the search path as you also need
> > /usr/include to get a complete linux kernel headers experience. We
> > definitely do not want to add /usr/include, because that is known to
> > misguide configure tests performed for the target architecture.
> 
> We are talking about the toolchain itself.  What configure tests could
> that be?  Or is that premature optimization of the gcc build?

The one case I really do remember quite well is sanitizers. These should
not be enabled in the earlier toolchain stages and failing to disable
them tends to cause linker failures. I don't think it matches the
concrete situation exactly though. You also make a good case in your
followup reporting that gcc-13-cross actually builds.

> You just said that the search path used during the build of the
> toolchain and the one for everything else are unrelated.  So you are
> free to create $BUILD/tmp-include with symlinks for asm, asm-generic,
> linux.
> 
> The toolchain as installed already finds all headers.  So I still don't
> see why we need this in the final system.

I find this argument fairly convincing and hope Matthias also does.

Thank you

Helmut

Bug#1065510: libnode108t64 is broken on !amd64

[Adrian Bunk]

Package: libnode108t64
Version: 18.19.1+dfsg-3.1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Benjamin Drung , Steve Langasek 

Control: affects -1 src:thunderbird

https://buildd.debian.org/status/logs.php?pkg=thunderbird&ver=1%3A115.8.1-1

...
 0:21.16 checking for nodejs... /usr/bin/node: error while loading shared 
libraries: libnode.so.108: cannot open shared object file: No such file or 
directory
...


This is due to:

$ cat debian/libnode108t64.install
usr/lib/libnode.so.* usr/lib/x86_64-linux-gnu/
$

Processed: libnode108t64 is broken on !amd64

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:thunderbird
Bug #1065510 [libnode108t64] libnode108t64 is broken on !amd64
Added indication that 1065510 affects src:thunderbird

-- 
1065510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065509: mysql-8.0 ftbfs with test failure on 32bit time_t64

[Matthias Klose]

Package: src:mysql-8.0
Version: 8.0.36-1
Severity: serious
Tags: sid trixie

here seen on armhf:

[...]
[ 58%] main.compare w4  [ pass ]   2171
[ 58%] main.func_unixtime_32bitsw1  [ fail ]
Test ended at 2024-03-05 17:31:14

CURRENT_TEST: main.func_unixtime_32bits

CURRENT_TEST: main.func_unixtime_32bits
--- /<>/mysql-test/r/func_unixtime_32bits.result	2023-12-12 
21:09:36.0 +0300
+++ 
/<>/builddir/mysql-test/var/1/log/func_unixtime_32bits.reject 
2024-03-05 20:31:13.393008921 +0300

@@ -12,7 +12,7 @@
 2038-01-19 06:14:07
 select from_unixtime(2147483648);
 from_unixtime(2147483648)
-NULL
+2038-01-19 06:14:08
 select from_unixtime(0);
 from_unixtime(0)
 1970-01-01 03:00:00
@@ -32,26 +32,26 @@
 2147483647
 select unix_timestamp(from_unixtime(2147483648));
 unix_timestamp(from_unixtime(2147483648))
-NULL
+2147483648
 # check for invalid dates
 # bad year
 select unix_timestamp('2039-01-20 01:00:00');
 unix_timestamp('2039-01-20 01:00:00')
-0
+2179087200
 select unix_timestamp('1968-01-20 01:00:00');
 unix_timestamp('1968-01-20 01:00:00')
 0
 # bad month
 select unix_timestamp('2038-02-10 01:00:00');
 unix_timestamp('2038-02-10 01:00:00')
-0
+2149365600
 select unix_timestamp('1969-11-20 01:00:00');
 unix_timestamp('1969-11-20 01:00:00')
 0
 # bad day
 select unix_timestamp('2038-01-20 01:00:00');
 unix_timestamp('2038-01-20 01:00:00')
-0
+2147551200
 select unix_timestamp('1969-12-30 01:00:00');
 unix_timestamp('1969-12-30 01:00:00')
 0
@@ -71,7 +71,7 @@
 # check bad date, close to the boundary (we cut them off in the very end)
 select unix_timestamp('2038-01-19 07:14:07');
 unix_timestamp('2038-01-19 07:14:07')
-0
+2147487247
 # -- 1. func_time.test   END
 # -- 2. time_zone.test   BEGIN
 #
@@ -84,20 +84,20 @@
 unix_timestamp('2038-01-19 04:14:07'),
 unix_timestamp('2038-01-19 04:14:08');
 unix_timestamp('1970-01-01 01:00:00')	unix_timestamp('1970-01-01 
01:00:01')	unix_timestamp('2038-01-19 04:14:07') 
unix_timestamp('2038-01-19 04:14:08')

-0  1   2147483647  0
+0  1   2147483647  2147483648
 set time_zone=default;
 # -- 2. time_zone.test   END
 # -- 3. time_zone2.test   BEGIN
 select convert_tz('2038-01-19 04:14:08', '+01:00', 'UTC');
 convert_tz('2038-01-19 04:14:08', '+01:00', 'UTC')
-2038-01-19 04:14:08
+2038-01-19 03:14:08
 select convert_tz('2103-01-01 04:00:00', 'MET', 'UTC');
 convert_tz('2103-01-01 04:00:00', 'MET', 'UTC')
-2103-01-01 04:00:00
+2103-01-01 03:00:00
 Will work on a 64 bits time system, no-op on 32 bits time
 select convert_tz('3001-01-18 23:59:59', 'UTC', '+01:00');
 convert_tz('3001-01-18 23:59:59', 'UTC', '+01:00')
-3001-01-18 23:59:59
+3001-01-19 00:59:59
 Will not work, beyond range of UNIX timestamp support
 select convert_tz('3001-01-19 00:00:00', 'UTC', '+01:00');
 convert_tz('3001-01-19 00:00:00', 'UTC', '+01:00')
@@ -123,12 +123,12 @@
 (32536771199.999);
 SELECT a, FROM_UNIXTIME(a) FROM t1;
 a  FROM_UNIXTIME(a)
-32536771199.990NULL
-32536771199.990NULL
-32536771199.991NULL
-32536771199.992NULL
-32536771199.993NULL
-32536771199.994NULL
+32536771199.9903001-01-18 23:59:59.99
+32536771199.9903001-01-18 23:59:59.99
+32536771199.9913001-01-18 23:59:59.99
+32536771199.9923001-01-18 23:59:59.99
+32536771199.9933001-01-18 23:59:59.99
+32536771199.9943001-01-18 23:59:59.99
 32536771199.995NULL
 32536771199.996NULL
 32536771199.997NULL
@@ -148,7 +148,7 @@
 FROM_UNIXTIME(32536771199) AS c4,
 FROM_UNIXTIME(32536771199.999) AS c5;
 c1 c2  c3  c4  c5
-2038-01-19 03:14:07NULLNULLNULLNULL
+2038-01-19 03:14:07	2038-01-19 03:14:08	2038-01-19 03:14:08.00 
3001-01-18 23:59:59	NULL

 SET time_zone=default;
 SELECT
 FROM_UNIXTIME(2147483647) AS c1,
@@ -157,7 +157,7 @@
 FROM_UNIXTIME(32536771199) AS c4,
 FROM_UNIXTIME(32536771199.999) AS c5;
 c1 c2  c3  c4  c5
-2038-01-19 06:14:07NULLNULLNULLNULL
+2038-01-19 06:14:07	2038-01-19 06:14:08	2038-01-19 06:14:08.00 
3001-01-19 02:59:59	NULL

 SET sql_mode=time_truncate_fractional;
 SET time_zone='+00:00';
 SELECT
@@ -167,7 +167,7 @@
 FROM_UNIXTIME(32536771199) AS c4,
 FROM_UNIXTIME(32536771199.999) AS c5;
 c1 c2  c3  c4  c5
-2038-01-19 03:14:07NULL2038-01-19 03:14:07.99  NULLNULL
+2038-01-19 03:14:07	2038-01-19 03:14:08	2038-01-19 03:14:07.99 
3001-01-18 23:59:59	3001-01-18 23:59:59.99

 SET time_zone=default;
 SELECT
 FROM_UNIXTIME(2147483647) AS c1,
@@ -176,7 +176,7 @@
 FROM_UNIXTIME(32536771199) AS c4,
 FROM_UNIXTIME(32536771199.999) AS c5;
 c1 c2  c3  c4  c5
-2038-01-19 06:14:07NULL2038-01-19 06:14:07.99  NULLNULL
+2038-01-19 06:14:07	2038-01-19 06:14:08	2038-01-19 06:14:07.99 
3001-01-19 02:59:59	3001-01-19 02:59:59.99

 SET sq

Bug#1064123: libgl1-mesa-dri: latest version crashes X, can't use mouse/keyboard

[Václav Ovsík]

I can confirm the problem on light system Fujitsu Futro S720
with Radeon HD 8280E (Kabini).

Downgrade mesa packages solved the problem
(
deb https://snapshot.debian.org/archive/debian/20240214T00Z/ sid main 
contrib non-free non-free-firmware
added to apt sources and then
aptitude -o Acquire::Check-Valid-Until=false
…
)

  Aptitude 0.8.13: log report
  Tue, Mar  5 2024 20:00:47 +0100
  
IMPORTANT: this log only lists intended actions; actions which fail
due to dpkg problems may not be completed.
  
  Will install 9 packages, and remove 0 packages.
  3869 kB of disk space will be freed
  
  [HOLD, DEPENDENCIES] libgtk2.0-common:amd64 2.24.33-3
  [HOLD, DEPENDENCIES] occt-misc:amd64 7.6.3+dfsg1-7
  [DOWNGRADE] libegl-mesa0:amd64 24.0.2-1 -> 23.3.5-1
  [DOWNGRADE] libgbm1:amd64 24.0.2-1 -> 23.3.5-1
  [DOWNGRADE] libgl1-mesa-dri:amd64 24.0.2-1 -> 23.3.5-1
  [DOWNGRADE] libglapi-mesa:amd64 24.0.2-1 -> 23.3.5-1
  [DOWNGRADE] libglx-mesa0:amd64 24.0.2-1 -> 23.3.5-1
  [DOWNGRADE] libxatracker2:amd64 24.0.2-1 -> 23.3.5-1
  [DOWNGRADE] mesa-va-drivers:amd64 24.0.2-1 -> 23.3.5-1
  [DOWNGRADE] mesa-vdpau-drivers:amd64 24.0.2-1 -> 23.3.5-1
  [DOWNGRADE] mesa-vulkan-drivers:amd64 24.0.2-1 -> 23.3.5-1
  

-- 
Zito
[   353.611] 
X.Org X Server 1.21.1.11
X Protocol Version 11, Revision 0
[   353.611] Current Operating System: Linux futro2 6.7.7-amd64 #1 SMP 
PREEMPT_DYNAMIC Debian 6.7.7-1 (2024-03-02) x86_64
[   353.611] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.7.7-amd64 
root=UUID=da2fd605-3371-4cba-b986-a2e2711eb69f ro
[   353.612] xorg-server 2:21.1.11-2 (https://www.debian.org/support) 
[   353.612] Current version of pixman: 0.42.2
[   353.612]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   353.612] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   353.612] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Mar  5 19:51:19 
2024
[   353.613] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   353.613] (==) No Layout section.  Using the first Screen section.
[   353.613] (==) No screen section available. Using defaults.
[   353.613] (**) |-->Screen "Default Screen Section" (0)
[   353.613] (**) |   |-->Monitor ""
[   353.614] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   353.614] (==) Automatically adding devices
[   353.614] (==) Automatically enabling devices
[   353.614] (==) Automatically adding GPU devices
[   353.614] (==) Automatically binding GPU devices
[   353.614] (==) Max clients allowed: 256, resource mask: 0x1f
[   353.614] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   353.614]Entry deleted from font path.
[   353.614] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   353.614] (==) ModulePath set to "/usr/lib/xorg/modules"
[   353.614] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   353.614] (II) Loader magic: 0x55cdf6a59f00
[   353.614] (II) Module ABI versions:
[   353.614]X.Org ANSI C Emulation: 0.4
[   353.614]X.Org Video Driver: 25.2
[   353.614]X.Org XInput driver : 24.4
[   353.614]X.Org Server Extension : 10.0
[   353.616] (++) using VT number 7

[   353.616] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[   353.619] (II) xfree86: Adding drm device (/dev/dri/card0)
[   353.619] (II) Platform probe for 
/sys/devices/pci:00/:00:01.0/drm/card0
[   353.628] (--) PCI:*(0@0:1:0) 1002:9837:1734:1202 rev 0, Mem @ 
0xc000/268435456, 0xd000/8388608, 0xfeb0/262144, I/O @ 
0xf000/256, BIOS @ 0x/131072
[   353.628] (II) LoadModule: "glx"
[   353.628] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   353.631] (II) Module glx: vendor="X.Org Foundation"
[   353.631]compiled for 1.21.1.11, module version = 1.0.0
[   353.631]ABI class: X.Org Server Extension, version 10.0
[   353.631] (II) Applying OutputClass "Radeon" to /dev/dri/card0
[   353.631]loading driver: radeon
[   353.631] (==) Matched radeon as autoconfigured driver 0
[   353.631] (==) Matched ati as autoconfigured driver 1
[   353.631] (==) Matched modesetting as autoconfigured driver 2
[   353.631] (==) Matched fbdev as autoconfigured driver 3
[   353.631] (==) Matched vesa as autoconfigured driver 4
[   353.631] (==) Assigned the driver to

Bug#1064739: marked as done (python-typing-extensions: FTBFS: AssertionError: Items in the first set but not the second:)

[Debian Bug Tracking System]

Your message dated Tue, 05 Mar 2024 19:19:13 +
with message-id 
and subject line Bug#1064739: fixed in python-typing-extensions 4.10.0-1
has caused the Debian Bug report #1064739,
regarding python-typing-extensions: FTBFS: AssertionError: Items in the first 
set but not the second:
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-typing-extensions
Version: 4.9.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.12 with "build" 
> module
> I: pybuild base:305: python3.12 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.12_typing-extensions  
> * Building wheel...
> Successfully built typing_extensions-4.9.0-py3-none-any.whl
> I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with 
> "installer" module
> I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:305: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_typing-extensions  
> * Building wheel...
> Successfully built typing_extensions-4.9.0-py3-none-any.whl
> I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.11 with 
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.12_typing-extensions/build; python3.12 
> -m unittest discover -v --start-directory /<>/src
> test_all_names_in___all__ 
> (test_typing_extensions.AllTests.test_all_names_in___all__) ... ok
> test_drop_in_for_typing 
> (test_typing_extensions.AllTests.test_drop_in_for_typing) ... ok
> test_typing_extensions_compiles_with_opt 
> (test_typing_extensions.AllTests.test_typing_extensions_compiles_with_opt) 
> ... ok
> test_typing_extensions_defers_when_possible 
> (test_typing_extensions.AllTests.test_typing_extensions_defers_when_possible) 
> ... ok
> test_typing_extensions_includes_standard 
> (test_typing_extensions.AllTests.test_typing_extensions_includes_standard) 
> ... ok
> test_annotated_in_other_types 
> (test_typing_extensions.AnnotatedTests.test_annotated_in_other_types) ... ok
> test_attr_passthrough 
> (test_typing_extensions.AnnotatedTests.test_attr_passthrough) ... ok
> test_cannot_check_instance 
> (test_typing_extensions.AnnotatedTests.test_cannot_check_instance) ... ok
> test_cannot_check_subclass 
> (test_typing_extensions.AnnotatedTests.test_cannot_check_subclass) ... ok
> test_cannot_getattr_typevar 
> (test_typing_extensions.AnnotatedTests.test_cannot_getattr_typevar) ... ok
> test_cannot_instantiate_forward 
> (test_typing_extensions.AnnotatedTests.test_cannot_instantiate_forward) ... ok
> test_cannot_instantiate_type_var 
> (test_typing_extensions.AnnotatedTests.test_cannot_instantiate_type_var) ... 
> ok
> test_cannot_subclass 
> (test_typing_extensions.AnnotatedTests.test_cannot_subclass) ... ok
> test_flatten (test_typing_extensions.AnnotatedTests.test_flatten) ... ok
> test_hash_eq (test_typing_extensions.AnnotatedTests.test_hash_eq) ... ok
> test_instantiate (test_typing_extensions.AnnotatedTests.test_instantiate) ... 
> ok
> test_instantiate_generic 
> (test_typing_extensions.AnnotatedTests.test_instantiate_generic) ... ok
> test_pickle (test_typing_extensions.AnnotatedTests.test_pickle) ... ok
> test_repr (test_typing_extensions.AnnotatedTests.test_repr) ... ok
> test_special_form_containment 
> (test_typing_extensions.AnnotatedTests.test_special_form_containment) ... ok
> test_specialize (test_typing_extensions.AnnotatedTests.test_specialize) ... ok
> test_subst (test_typing_extensions.AnnotatedTests.test_subst) ... ok
> test_can_subclass (test_typing_extensions.AnyTests.test_can_subclass) ... ok
> test_instantiation (test_typing_extensions.AnyTests.test_instantiation) ... ok
> test_isinstance (test_typing_extensions.AnyTests.test_isinstance) ... ok
> test_repr (test_typing_extensions.AnyTests.test_repr) ... ok
> test_repr_on_Any_subclass 
> (test_typing_ex

Bug#1064816: marked as done (python-wikkid: FTBFS: ModuleNotFoundError: No module named 'tzlocal')

[Debian Bug Tracking System]

Your message dated Tue, 5 Mar 2024 18:28:12 +
with message-id 
and subject line Re: Bug#1064816: python-wikkid: FTBFS: ModuleNotFoundError: No 
module named 'tzlocal'
has caused the Debian Bug report #1064816,
regarding python-wikkid: FTBFS: ModuleNotFoundError: No module named 'tzlocal'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-wikkid
Version: 0.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240226 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> FAILED (errors=42, skipped=18)
> E: pybuild pybuild:391: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.12/build; python3.12 -m unittest 
> discover -v 
> I: pybuild base:305: cd /<>/.pybuild/cpython3_3.11/build; 
> python3.11 -m unittest discover -v 
> test_blockquote 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_blockquote)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_blockquote 
> ... 
> /<>/.pybuild/cpython3_3.11/build/wikkid/tests/formatters/test_markdown.py:31:
>  DeprecationWarning: Only valid in 1.8.1 and earlier. Use skipTest instead.
>   self.skip('markdown formatter not available')
> skipped 'markdown formatter not available'
> test_code 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_code)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_code ... 
> skipped 'markdown formatter not available'
> test_code_blocks 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_code_blocks)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_code_blocks 
> ... skipped 'markdown formatter not available'
> test_detailed_headings 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_detailed_headings)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_detailed_headings
>  ... skipped 'markdown formatter not available'
> test_emphasis 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_emphasis)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_emphasis ... 
> skipped 'markdown formatter not available'
> test_hr (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_hr)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_hr ... 
> skipped 'markdown formatter not available'
> test_inline_link 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_inline_link)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_inline_link 
> ... skipped 'markdown formatter not available'
> test_lists 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_lists)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_lists ... 
> skipped 'markdown formatter not available'
> test_reference_link 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_reference_link)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_reference_link
>  ... skipped 'markdown formatter not available'
> test_simple_headings 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_simple_headings)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_simple_headings
>  ... skipped 'markdown formatter not available'
> test_unicode 
> (wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_unicode)
> wikkid.tests.formatters.test_markdown.TestMarkdownFormatter.test_unicode ... 
> skipped 'markdown formatter not available'
> test_default_exists 
> (wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_default_exists)
> wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_default_exists 
> ... ok
> test_default_missing 
> (wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_default_missing)
> wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_default_missing
>  ... ok
> test_specify_extra_params 
> (wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_specify_extra_params)
> wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_specify_extra_params
>  ... ok
> test_specify_extra_whitespace 
> (wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_specify_extra_whitespace)
> wikkid.tests.formatters.test_registry.TestGetWikiFormtter.test_specify_extra_whitespace
>  ... ok
> test_specify_missing 
> (wikkid.t

Bug#1061754: python-json-log-formatter ftbfs with Python 3.12 as default

[Colin Watson]

Control: tag -1 moreinfo

On Mon, Jan 29, 2024 at 01:10:20PM +0100, Matthias Klose wrote:
> With python3-defaults from experimental, the package fails to build:
> 
> [...]
> = test session starts
> ==
> platform linux -- Python 3.12.1, pytest-7.4.4, pluggy-1.4.0
> cachedir: .tox/py312/.pytest_cache
> rootdir: /<>
> collected 29 items
> 
> tests.py ...FF
> 
> === FAILURES
> ===
> _ 
> JSONFormatterTest.test_message_and_time_and_extra_are_in_json_record_when_extra_is_provided
> _
> 
> self =  testMethod=test_message_and_time_and_extra_are_in_json_record_when_extra_is_provided>
> 
> def 
> test_message_and_time_and_extra_are_in_json_record_when_extra_is_provided(self):
> logger.info('Sign up', extra={'fizz': 'bazz'})
> json_record = json.loads(log_buffer.getvalue())
> expected_fields = set([
> 'message',
> 'time',
> 'fizz',
> ])
> >   self.assertEqual(set(json_record), expected_fields)
> E   AssertionError: Items in the first set but not the second:
> E   'taskName'

While it looks like this was fixed upstream in
https://github.com/marselester/json-log-formatter/commit/74f04ee4f6aa8e461fcb2d688459888b7279fc73
and I guess we could cherry-pick that, I also can't reproduce this
failure in current unstable with Python 3.12.  Can you still reproduce
this?

Thanks,

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Processed: Re: Bug#1061754: python-json-log-formatter ftbfs with Python 3.12 as default

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #1061754 [src:python-json-log-formatter] python-json-log-formatter ftbfs 
with Python 3.12 as default
Added tag(s) moreinfo.

-- 
1061754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065158: marked as done (postfix: FTBFS: missing build-dep on libnsl-dev)

[Debian Bug Tracking System]

Your message dated Tue, 05 Mar 2024 16:20:38 +
with message-id 
and subject line Bug#1065158: fixed in postfix 3.8.6-1
has caused the Debian Bug report #1065158,
regarding postfix: FTBFS: missing build-dep on libnsl-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postfix
Version: 3.8.5-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-gl...@lists.debian.org
Usertags: libnsl-dev

Dear maintainer,

Starting with glibc 2.31, support for NIS (libnsl library) has been
moved to a separate libnsl2 package. In order to allow a smooth
transition, a libnsl-dev has been added to the libc6-dev package.

This dependency has been temporarily dropped in the 2.37-15.1 NMU, as
part of the 64-bit time_t transition. This causes postfix to FTBFS in
sid with:

| gcc -fPIC -I. -I../../include -DDEBIAN -DHAS_PCRE=2 -DHAS_LDAP 
-DUSE_LDAP_SASL -DHAS_SQLITE -DMYORIGIN_FROM_FILE -DHAS_CDB -DHAS_LMDB 
-DHAS_MYSQL -I/usr/include/mysql -DHAS_PGSQL -I/usr/include/postgresql 
-DHAS_SQLITE -DHAS_SSL -I/usr/include/openssl -DUSE_SASL_AUTH 
-I/usr/include/sasl -DUSE_CYRUS_SASL -DUSE_TLS -DHAS_DEV_URANDOM 
-DDEF_DAEMON_DIR=\"/usr/lib/postfix/sbin\" 
-DDEF_HTML_DIR=\"/usr/share/doc/postfix/html\" 
-DDEF_MANPAGE_DIR=\"/usr/share/man\" 
-DDEF_README_DIR=\"/usr/share/doc/postfix\" -DUSE_DYNAMIC_LIBS 
-DUSE_DYNAMIC_MAPS -Wmissing-prototypes -Wformat -Wno-comment -fno-common -fPIC 
 -Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -g -O2 
-ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -flto=auto -ffat-lto-objects 
-Wl,-z,relro -Wl,-z,now -I. -DLINUX6 -c dict_nis.c
| dict_nis.c:42:10: fatal error: rpcsvc/ypclnt.h: No such file or directory
|42 | #include 
|   |  ^
| compilation terminated.
| make: *** [Makefile:220: dict_nis.o] Error 1
| make: *** Waiting for unfinished jobs
| make: Leaving directory '/<>/src/util'
| make[2]: *** [Makefile:114: update] Error 1
| make[2]: Leaving directory '/<>'
| dh_auto_build: error: make -j3 "INSTALL=install --strip-program=true" 
returned exit code 2
| make[1]: *** [debian/rules:90: override_dh_auto_build] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:63: binary] Error 2

This could be fixed by adding an explicit Build-Depends on libnsl-dev.
The glibc change will likely be reverted in the short term, but given
its a change we want to do for Trixie, this will only lower the severity
of the bug.

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 3.8.6-1
Done: Scott Kitterman 

We believe that the bug you reported is fixed in the latest version of
postfix, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated postfix package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 05 Mar 2024 10:24:36 -0500
Source: postfix
Architecture: source
Version: 3.8.6-1
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Scott Kitterman 
Closes: 1059760 1061564 1065158
Changes:
 postfix (3.8.6-1) unstable; urgency=medium
 .
   [Scott Kitterman]
 .
   * Remove lib/systemd/system-generators from d/postfix.dirs.  Closes: #1059760
   * Update with wrap-and-sort
   * Refactor d/p/Sort-list-of-AUXLIBS-for-reproducible-builds.patch based on
 upstream feedback
   * Mark d/p/Sort-list-of-AUXLIBS-for-reproducible-builds.patch as forwarded
   * Add libnsl-dev to build-depends, split from libc6-dev.  Closes: #1065158
   * Build-depend on pkgconf instead of obsolete pkg-config
 .
   [localization folks]
 .
   * l10n: Updated Swedish debconf translations. (Martin Bagge, Anders
 Jonsson).  Closes: #1061564
 .
   [Wietse Venema]
 .
   * 3.8.6
Checksums-Sha1:
 05cb69e4a8

Bug#999908: marked as pending in celery-haystack-ng

[Colin Watson]

Control: tag -1 pending

Hello,

Bug #08 in celery-haystack-ng 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/python-team/packages/celery-haystack-ng/-/commit/5b561e1cbe481c67b3241e19898a528d34a236b6


Breaks/Replaces: python3-django-celery-haystack

Closes: #08


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/08

Processed: Bug#999908 marked as pending in celery-haystack-ng

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #08 [python3-celery-haystack-ng] python3-celery-haystack-ng: missing 
Breaks+Replaces: python3-django-celery-haystack (<< 0.20)
Added tag(s) pending.

-- 
08: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=08
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065501: qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb

[Sebastiaan Couwenberg]

Control: tags -1 confirmed

On 3/5/24 4:44 PM, Adrian Bunk wrote:

https://buildd.debian.org/status/logs.php?pkg=qgis&ver=3.34.4%2Bdfsg-3


Nothing we can do about that until the dependency chain has been rebuilt 
for the ongoing t64 transition.


The builds prior to the t64 transition succeeded.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: Bug#1065501: qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #1065501 [src:qgis] qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb
Added tag(s) confirmed.

-- 
1065501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065501: qgis FTBFS: FAILED: src/crssync/CMakeFiles/synccrsdb

[Adrian Bunk]

Source: qgis
Version: 3.34.4+dfsg-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=qgis&ver=3.34.4%2Bdfsg-3

...
FAILED: src/crssync/CMakeFiles/synccrsdb 
/<>/debian/build/src/crssync/CMakeFiles/synccrsdb 
cd /<>/debian/build/src/crssync && 
/<>/debian/build/output/bin/crssync
Could not execute: INSERT INTO tbl_srs(srs_id, 
description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type)
 VALUES (63561, 'MSL UK & Ireland VORF08 depth','','','+vunits=m 
+no_defs',520003561,'EPSG','10150',0,0,'Vertical') [UNIQUE constraint failed: 
tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id]

Could not execute: INSERT INTO tbl_srs(srs_id, 
description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type)
 VALUES (63562, 'CD UK & Ireland VORF08 depth','','','+vunits=m 
+no_defs',520003562,'EPSG','10151',0,0,'Vertical') [UNIQUE constraint failed: 
tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id]

Could not execute: INSERT INTO tbl_srs(srs_id, 
description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type)
 VALUES (63563, 'ETRS89 + MSL UK & Ireland VORF08 
depth','longlat','longlat','+proj=longlat +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 
+vunits=m +no_defs',520003563,'EPSG','10156',0,0,'Compound') [UNIQUE constraint 
failed: tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id]

Could not execute: INSERT INTO tbl_srs(srs_id, 
description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type)
 VALUES (63564, 'ETRS89 + CD UK & Ireland VORF08 
depth','longlat','longlat','+proj=longlat +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 
+vunits=m +no_defs',520003564,'EPSG','10157',0,0,'Compound') [UNIQUE constraint 
failed: tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id]

Could not execute: INSERT INTO tbl_srs(srs_id, 
description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type)
 VALUES (63565, 'S34J-IRF','longlat','longlat','+proj=longlat +ellps=intl 
+no_defs',520003565,'EPSG','10158',1,0,'Geographic2d') [UNIQUE constraint 
failed: tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id]

Could not execute: INSERT INTO tbl_srs(srs_id, 
description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type)
 VALUES (63566, 'S34J reconstruction 
east-orientated','tmerc','tmerc','+proj=tmerc +lat_0=0 +lon_0=10.37 +k=1 
+x_0=-210327 +y_0=-6034310 +ellps=intl +units=m 
+no_defs',520003566,'EPSG','10160',0,0,'Projected') [UNIQUE constraint failed: 
tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id]

Could not execute: INSERT INTO tbl_srs(srs_id, 
description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type)
 VALUES (63567, 'JGD2011 / Japan Plane Rectangular CS I + JGD2011 (vertical) 
height','tmerc','tmerc','+proj=tmerc +lat_0=33 +lon_0=129.5 +k=0. +x_0=0 
+y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +vunits=m 
+no_defs',520003567,'EPSG','10162',0,0,'Compound') [UNIQUE constraint failed: 
tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id]

Could not execute: INSERT INTO tbl_srs(srs_id, 
description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type)
 VALUES (63568, 'JGD2011 / Japan Plane Rectangular CS II + JGD2011 (vertical) 
height','tmerc','tmerc','+proj=tmerc +lat_0=33 +lon_0=131 +k=0. +x_0=0 
+y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +vunits=m 
+no_defs',520003568,'EPSG','10163',0,0,'Compound') [UNIQUE constraint failed: 
tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id]

Could not execute: INSERT INTO tbl_srs(srs_id, 
description,projection_acronym,ellipsoid_acronym,parameters,srid,auth_name,auth_id,is_geo,deprecated,srs_type)
 VALUES (63569, 'JGD2011 / Japan Plane Rectangular CS III + JGD2011 (vertical) 
height','tmerc','tmerc','+proj=tmerc +lat_0=36 +lon_0=132.1667 
+k=0. +x_0=0 +y_0=0 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +vunits=m 
+no_defs',520003569,'EPSG','10164',0,0,'Compound') [UNIQUE constraint failed: 
tbl_srs.srs_id/UNIQUE constraint failed: tbl_srs.srs_id]
...

Processed: unarchiving 1056147, tagging 1065435, tagging 1065486, found 1053196 in 2.0.24-2, tagging 1053195 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 1056147
Bug #1056147 {Done: Andreas Beckmann } [src:midge] midge 
possibly contains non-DFSG-free examples 
Unarchived Bug 1056147
> tags 1065435 + sid trixie
Bug #1065435 [src:aptitude] aptitude: FTBFS on armhf and armel: deduced 
conflicting types for parameter ‘const T’ (‘long int’ and ‘__suseconds64_t’ 
{aka ‘long long int’})
Added tag(s) sid and trixie.
> tags 1065486 + sid trixie
Bug #1065486 [src:sbd] sbd: FTBFS due to hardcoded libaio SONAME used in 
dlopen()
Added tag(s) trixie and sid.
> found 1053196 2.0.24-2
Bug #1053196 [uwsgi] Please remove librados-dev build-depends on all 32 bits 
arch
Marked as found in versions uwsgi/2.0.24-2.
> tags 1053195 + sid trixie
Bug #1053195 [src:nfs-ganesha] Please remove librados-dev build-depends on all 
32 bits arch
Added tag(s) trixie and sid.
> tags 1053169 + sid trixie
Bug #1053169 [src:tcmu] Please remove librbd-dev build-depends on all 32 bits 
arch
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1053169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053169
1053195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053195
1053196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053196
1056147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056147
1065435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065435
1065486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057717: marked as done (libuv1: io_uring support randomly segfaults after signal on ppc64el/ppc64)

[Debian Bug Tracking System]

Your message dated Tue, 5 Mar 2024 17:38:15 +0200
with message-id 
and subject line Re: Bug#1057717: cmake ftbfs on ppc64el (and ppc64)
has caused the Debian Bug report #1057717,
regarding libuv1: io_uring support randomly segfaults after signal on 
ppc64el/ppc64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1057717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:cmake
Version: 3.28.0-1
Severity: serious
Tags: sid trixie

cmake ftbfs on ppc64el (and ppc64):

[...]
99% tests passed, 5 tests failed out of 697

Label Time Summary:
CMake  = 1205.59 sec*proc (290 tests)
CUDA   =  90.91 sec*proc (11 tests)
HIP=  17.89 sec*proc (6 tests)
ISPC   =  60.92 sec*proc (6 tests)
Label1 =   0.06 sec*proc (1 test)
Label2 =   0.06 sec*proc (1 test)
Qt5= 678.18 sec*proc (49 tests)
command=   6.93 sec*proc (23 tests)
policy =  81.42 sec*proc (42 tests)
run= 1198.66 sec*proc (267 tests)

Total Test time (real) = 436.62 sec

The following tests FAILED:
108 - LibName (SEGFAULT)
241 - CMakeCommands.add_link_options (SEGFAULT)
264 - CTestTestDepends (Failed)
393 - RunCMake.FPHSA (SEGFAULT)
467 - RunCMake.cmake_path (SEGFAULT)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8
make[2]: Leaving directory '/<>/Build'
--- End Message ---
--- Begin Message ---
Version: 1.48.0-1

On Sat, Jan 13, 2024 at 03:49:17PM +0100, John Paul Adrian Glaubitz wrote:
> Control: tags -1 +patch
> 
> On Fri, 2024-01-12 at 01:31 +0100, John Paul Adrian Glaubitz wrote:
> > This has now been tracked down to the libuv upstream change that introduced 
> > support
> > for io_uring [1]. This regression is tracked now in a new issue for libuv 
> > [2].
> 
> The attached patch disables io_uring on ppc64 and ppc64el for the time being 
> until
> the upstream issue has been resolved.

This patch has been included in upstream 1.48.0, which fixed this issue.

Disabling misses out on the performance improvements by this change,
but it still works as good as before io_uring support was added.

> Adrian
>...

cu
Adrian--- End Message ---

Bug#1065126: marked as done (libelk0t64 has an undeclared file conflict)

[Debian Bug Tracking System]

Your message dated Tue, 05 Mar 2024 15:34:10 +
with message-id 
and subject line Bug#1065126: fixed in elk 3.99.8-6
has caused the Debian Bug report #1065126,
regarding libelk0t64 has an undeclared file conflict
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libelk0t64
Version: 3.99.8-5
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libelk0

libelk0t64 has an undeclared file conflict. This may result in an unpack
error from dpkg.

The files
 * /usr/lib/x86_64-linux-gnu/libelk-xlib.so.0
 * /usr/lib/x86_64-linux-gnu/libelk-xlib.so.0.0.0
 * /usr/lib/x86_64-linux-gnu/libelk-xt.so.0
 * /usr/lib/x86_64-linux-gnu/libelk-xt.so.0.0.0
 * /usr/lib/x86_64-linux-gnu/libelk.so.0
 * /usr/lib/x86_64-linux-gnu/libelk.so.0.0.0
are contained in the packages
 * libelk0/3.99.8-4.2+b1 as present in bookworm|bullseye|trixie|unstable
 * libelk0t64/3.99.8-5 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: elk
Source-Version: 3.99.8-6
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
elk, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated elk package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 05 Mar 2024 16:08:09 +0100
Source: elk
Architecture: source
Version: 3.99.8-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1065126
Changes:
 elk (3.99.8-6) unstable; urgency=medium
 .
   * QA upload.
   * Fix Breaks+Replaces for the 64-bit time_t transition.  (Closes: #1065126)
   * Set Rules-Requires-Root: no.
Checksums-Sha1:
 2d3185a41c9222a948cee70b65d0df6b49ff4ddc 2108 elk_3.99.8-6.dsc
 e84748903f2cfec702762bf388e9cc3d41cd55b1 8940 elk_3.99.8-6.debian.tar.xz
 78d1a002047933302e05192b7f962cdb2fb18fe1 7423 elk_3.99.8-6_source.buildinfo
Checksums-Sha256:
 4098897c3346fd9c716624e03c6de76929f51736366e5a1edf6ef1f81cbf29d7 2108 
elk_3.99.8-6.dsc
 9aee532e6db34d523a58f80e2caad2ca224656043990c312040d55c4f76cfa8f 8940 
elk_3.99.8-6.debian.tar.xz
 1b0e54f33734d9c75dda3a93f102ae6475b08aea93f80a44c1c65412e2df9f0a 7423 
elk_3.99.8-6_source.buildinfo
Files:
 201b56fb95964bd6d5bd6a2ab1738dec 2108 devel optional elk_3.99.8-6.dsc
 7f9369b6e403bd31c30375a8652fd288 8940 devel optional elk_3.99.8-6.debian.tar.xz
 2ad3740a33d4b50573f1cc444f4868ea 7423 devel optional 
elk_3.99.8-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmXnNdgQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCC78D/9t8WleGNleKjPjoIjr6mwlbD4mTejBdLDB
RP7gqNkI0d8Y0oAYfL3d+dIXiGNAASH2QkF6n+D7XtrQhROP+Y9l9eCDgdBOCDoQ
sSDon9SRkvsH+bXSBeDObtXiz/Mv/wHDATMJuxhDCwkDOcYoWP1xZJTwYPPtphWl
fFfto6If55nOtGJ7nJMuqV8duCvfKJcl1uKE/WBJWWOP/le1oVhCKGWVvBISffd+
I/A9u2jK5c1+hpBA2fE474UOYS1UVUQOZjCtwu73ZZip/Ks4k/tqYDOZiYqbyik5
DkC2yVInQ2oR72h49FqTOOWguxIWd8WUADYO3oXy5Mg5encIIh3bYVXRIvqQXKBC
eVd/u97p572Sa5LVSpdzHUNPlc63qAv9Dn8aA3inji16HLgI6SNwioP0A0YoBDet
dYshic2G83DJAeApw6qIvcVQd5zsdzB3UrUTrXEWamMDvmIA42a3guBmqLOgLBYy
YJa5jiF+jG6ohnNMqvBMftDMukeW8X/Kz6dNs5T14PeuMSYf9NJYjzddB3O5kLzU
0K9C9ntARqemxzE0pP1Ipxq9P7BxeGSfvtjGSKzqR7PaPc8xaCtf2a9gKCRjaXnP
Qxe14vr6GYLPg047DGJUDneu2tCShDCMrP91hxdyKJfk+QvFq6oi0QEErR/wgj6u
GP4QwNmI8w==
=RGHv
-END PGP SIGNATURE-



pgp8VgHineLce.pgp
Description: PGP signature
--- End Message

Processed: Re: Bug#1065500: orc: liborc-0.4-dev-bin depends on both liborc-0.4-0 and liborc-0.4-0t64

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1065500 serious
Bug #1065500 [src:orc] orc: liborc-0.4-dev-bin depends on both liborc-0.4-0 and 
liborc-0.4-0t64
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1065500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065477: [Pkg-owncloud-maintainers] Bug#1065477: owncloud-client: Uploads to unstable must have a higher version than present in unstable.

[Sebastian Ramacher]

Hi

On 2024-03-05 15:42:49 +0100, Pierre-Elliott Bécue wrote:
> Hello,
> 
> Sebastian Ramacher  wrote on 05/03/2024 at 
> 09:38:13+0100:
> 
> > Source: owncloud-client
> > Version: 4.2.0.11670+dfsg-1.1
> > Severity: serious
> > Tags: ftbfs
> > X-Debbugs-Cc: sramac...@debian.org
> >
> > Version check failed:
> > Your upload included the binary package dolphin-owncloud, version 
> > 4.2.0.11670+dfsg-1.1, for amd64,
> > however unstable already has version 5.0.0-1+b1.
> > Uploads to unstable must have a higher version than present in unstable.
> >
> > Cheers
> 
> owncloud-client has been uploaded far before in the past, and was
> shipping dolphin-owncloud, nautilus-owncloud, et al.
> 
> In client v5, upstream removed these packages from the owncloud-client
> source, and therefore they're now packaged through dedicated source
> packages.
> 
> These ones are the latest uploads.
> 
> I'll upload the v5 version of owncloud-client source package which won't
> ship dolphin-owncloud et al anymore.
> 
> It's what's been suggested to me, and therefore I can't see a bug here.
> 
> Could you give me a bit more intel aobut why this would be a serious
> bug?

The uploads by the buidds fail to be included in the archive since the
constraints are not satisfied. You can check the reject files for the
changes files from owncloud-client on coccia.d.o.

You can also see on
https://buildd.debian.org/status/package.php?p=owncloud-client&suite=sid
that the package is stuck in Uploaded state due to this issue.

Cheers
-- 
Sebastian Ramacher

Bug#1065477: [Pkg-owncloud-maintainers] Bug#1065477: owncloud-client: Uploads to unstable must have a higher version than present in unstable.

[Pierre-Elliott Bécue]

Hello,

Sebastian Ramacher  wrote on 05/03/2024 at 09:38:13+0100:

> Source: owncloud-client
> Version: 4.2.0.11670+dfsg-1.1
> Severity: serious
> Tags: ftbfs
> X-Debbugs-Cc: sramac...@debian.org
>
> Version check failed:
> Your upload included the binary package dolphin-owncloud, version 
> 4.2.0.11670+dfsg-1.1, for amd64,
> however unstable already has version 5.0.0-1+b1.
> Uploads to unstable must have a higher version than present in unstable.
>
> Cheers

owncloud-client has been uploaded far before in the past, and was
shipping dolphin-owncloud, nautilus-owncloud, et al.

In client v5, upstream removed these packages from the owncloud-client
source, and therefore they're now packaged through dedicated source
packages.

These ones are the latest uploads.

I'll upload the v5 version of owncloud-client source package which won't
ship dolphin-owncloud et al anymore.

It's what's been suggested to me, and therefore I can't see a bug here.

Could you give me a bit more intel aobut why this would be a serious
bug?
-- 
PEB


signature.asc
Description: PGP signature

Bug#1065485: marked as done (file conflict with qemu-system-common / failure during upgrade)

[Debian Bug Tracking System]

Your message dated Tue, 5 Mar 2024 17:34:09 +0300
with message-id <98402efd-67a5-45cf-97ae-1abb2b6d5...@tls.msk.ru>
and subject line Re: Bug#1065485: file conflict with qemu-system-common / 
failure during upgrade
has caused the Debian Bug report #1065485,
regarding file conflict with qemu-system-common / failure during upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-system-data
Version: 1:8.2.1+ds-2
Severity: serious

During the lastest upgrade, I get
Preparing to unpack .../qemu-system-data_1%3a8.2.2+ds-1_all.deb ...
Unpacking qemu-system-data (1:8.2.2+ds-1) over (1:8.2.1+ds-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/qemu-system-data_1%3a8.2.2+ds-1_all.deb (--unpack):
 trying to overwrite 
'/usr/share/doc/qemu-system-common/system/arm/aspeed.html', which is also in 
package qemu-system-common 1:8.2.1+ds-2
Errors were encountered while processing:
 /var/cache/apt/archives/qemu-system-data_1%3a8.2.2+ds-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
--- End Message ---
--- Begin Message ---

Version: 1:8.2.2+ds-2

05.03.2024 14:13, Michael Biebl wrote:

Package: qemu-system-data
Version: 1:8.2.1+ds-2


This seems to be a wrong version.  Actual buggy version is 8.2.2+ds-1


During the lastest upgrade, I get
Preparing to unpack .../qemu-system-data_1%3a8.2.2+ds-1_all.deb ...
Unpacking qemu-system-data (1:8.2.2+ds-1) over (1:8.2.1+ds-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/qemu-system-data_1%3a8.2.2+ds-1_all.deb (--unpack):
  trying to overwrite 
'/usr/share/doc/qemu-system-common/system/arm/aspeed.html', which is also in 
package qemu-system-common 1:8.2.1+ds-2


This is already fixed in 8.2.2+ds-2 (#1065469) earlier today.

/mjt--- End Message ---

Bug#1063631: closing 1063631

[Roland Mas]

close 1063631 5.0.0.3381-2
thanks

Processed: closing 1063631

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 1063631 5.0.0.3381-2
Bug #1063631 [src:hkl] hkl FTBFS with libcglm-dev 0.9.2-1
The source 'hkl' and version '5.0.0.3381-2' do not appear to match any binary 
packages
Marked as fixed in versions hkl/5.0.0.3381-2.
Bug #1063631 [src:hkl] hkl FTBFS with libcglm-dev 0.9.2-1
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1063631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1062352: marked as done (libgsmme1t64 has an undeclared file conflict)

[Debian Bug Tracking System]

Your message dated Tue, 5 Mar 2024 15:06:16 +0100
with message-id <9683feb7-5761-62f2-9ee2-0bbe59add...@debian.org>
and subject line Re: libgsmme1t64 has an undeclared file conflict
has caused the Debian Bug report #1062352,
regarding libgsmme1t64 has an undeclared file conflict
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1062352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgsmme1t64
Version: 1.10+20120414.gita5e5ae9a-2.1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libgsmme1v5
X-Debbugs-Cc: Graham Inggs , vor...@debian.org

libgsmme1t64 has an undeclared file conflict. This may result in an
unpack error from dpkg.

The files
 * /usr/lib/x86_64-linux-gnu/libgsmext.so.1
 * /usr/lib/x86_64-linux-gnu/libgsmext.so.1.0.4
 * /usr/lib/x86_64-linux-gnu/libgsmme.so.1
 * /usr/lib/x86_64-linux-gnu/libgsmme.so.1.0.4
are contained in the packages
 * libgsmme1t64/1.10+20120414.gita5e5ae9a-2.1~exp1 as present in experimental
 * libgsmme1v5
   * 1.10+20120414.gita5e5ae9a-2+b1 as present in bookworm|trixie|unstable
   * 1.10+20120414.gita5e5ae9a-2~bpo11+1 as present in bullseye-backports

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---

Version: 1.10+20120414.gita5e5ae9a-3

That seems to be fixed now:

Package: libgsmme1t64
Source: gsmlib
Version: 1.10+20120414.gita5e5ae9a-3
Installed-Size: 608
Maintainer: Debian QA Group 
Architecture: amd64
Replaces: libgsmme1c102, libgsmme1c2, libgsmme1c2a, libgsmme1v5
Provides: libgsmme1v5 (= 1.10+20120414.gita5e5ae9a-3)
Depends: libc6 (>= 2.33), libgcc-s1 (>= 3.0), libstdc++6 (>= 13.1)
Conflicts: libgsmme1, libgsmme1c102, libgsmme1c2, libgsmme1c2a
Breaks: libgsmme1v5 (<< 1.10+20120414.gita5e5ae9a-3)


Andreas--- End Message ---

Processed: Re: Bug#1065493: libgtk2.0-0t64: 64-bit time_t transition breaks gtk+2.0 immodule cach

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1065494 serious
Bug #1065494 [libgtk-3-0t64] libgtk-3-0t64: 64-bit time_t transition breaks 
gtk+3.0 immodule cache
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1065494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065496: mysql-8.0 builds with the embedded zlib library

[Matthias Klose]

Package: src:mysql-8.0
Version: 8.0.36-1
Severity: serious
Tags: sid trixie

mysql-8.0 builds with the embedded zlib library

[...]
-- Adding -DWITH_CURL=system
-- Adding -DWITH_EDITLINE=system
-- Adding -DWITH_ICU=system
-- Adding -DWITH_LIBEVENT=system
-- Adding -DWITH_LZ4=system
-- Adding -DWITH_PROTOBUF=system
-- Adding -DWITH_SSL=system
-- Adding -DWITH_ZSTD=system
-- Found WITH_FIDO=bundled on command line
-- ZLIB_VERSION (bundled) is 1.2.13
-- ZLIB_INCLUDE_DIR /<>/extra/zlib/zlib-1.2.13

it should not do that, please use the system zlib.

But building with the embedded zlib for time64:

[...]
DLZ4_DISABLE_DEPRECATE_WARNINGS -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE 
-D_LARGEFILE64_SOURCE=1 -D_USE_MATH_DEFINES -D__STDC_FORMAT_MACROS 
-D__STDC_LIMIT_MACROS -I/<>/builddir 
-I/<>/builddir/include -I/<> 
-I/<>/include -isystem 
/<>/builddir/extra/zlib/zlib-1.2.13 -isystem 
/<>/extra/zlib/zlib-1.2.13 -fno-omit-frame-pointer -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-stack-clash-protection 
-fdebug-prefix-map=/<>=/usr/src/mysql-8.0-8.0.36-1build2 
-fdebug-prefix-map=/<>/=./ 
-fdebug-prefix-map=/<>/builddir=./obj -ffunction-sections 
-fdata-sections -O2 -g -DNDEBUG -fPIC   -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 
-Wno-missing-profile -fvisibility=hidden -MD -MT 
extra/zlib/zlib-1.2.13/CMakeFiles/zlib_objlib.dir/gzclose.c.o -MF 
CMakeFiles/zlib_objlib.dir/gzclose.c.o.d -o 
CMakeFiles/zlib_objlib.dir/gzclose.c.o -c 
/<>/extra/zlib/zlib-1.2.13/gzclose.c

In file included from /usr/include/features.h:394,
 from 
/usr/include/arm-linux-gnueabihf/bits/libc-header-start.h:33,

 from /usr/include/stdio.h:28,
 from ../../../../extra/zlib/zlib-1.2.13/gzguts.h:21,
 from ../../../../extra/zlib/zlib-1.2.13/gzclose.c:6:
/usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is 
allowed only with _FILE_OFFSET_BITS=64"

   26 | #   error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
  | ^
make[4]: *** 
[extra/zlib/zlib-1.2.13/CMakeFiles/zlib_objlib.dir/build.make:135: 
extra/zlib/zlib-1.2.13/CMakeFiles/zlib_objlib.dir/gzclose.c.o] Error 1

make[4]: Leaving directory '/<>/builddir'
make[3]: *** [CMakeFiles/Makefile2:5761: 
extra/zlib/zlib-1.2.13/CMakeFiles/zlib_objlib.dir/all] Error 2

Processed (with 1 error): Re: Bug#1065493: libgtk2.0-0t64: 64-bit time_t transition breaks gtk+2.0 immodule cache

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1065493 serious
Bug #1065493 [libgtk2.0-0t64] libgtk2.0-0t64: 64-bit time_t transition breaks 
gtk+2.0 immodule cache
Severity set to 'serious' from 'normal'
> severity 105494 serious
Failed to set severity of Bug 105494 to serious: Not altering archived bugs; 
see unarchive.

>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1065493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1065489, bug 1065489 is forwarded to https://jira.mongodb.org/browse/CDRIVER-5493

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1065489 + fixed-upstream
Bug #1065489 [src:mongo-c-driver] mongo-c-driver: FTBFS on armhf: format ‘%ld’ 
expects argument of type ‘long int’, but argument 4 has type ‘__suseconds64_t’ 
{aka ‘long long int’}
Added tag(s) fixed-upstream.
> forwarded 1065489 https://jira.mongodb.org/browse/CDRIVER-5493
Bug #1065489 [src:mongo-c-driver] mongo-c-driver: FTBFS on armhf: format ‘%ld’ 
expects argument of type ‘long int’, but argument 4 has type ‘__suseconds64_t’ 
{aka ‘long long int’}
Set Bug forwarded-to-address to 'https://jira.mongodb.org/browse/CDRIVER-5493'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1065489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1064282: poppler: NMU diff for 64-bit time_t transition

[Sune Stolborg Vuorela]

On Sunday, March 3, 2024 7:40:52 AM CET Steve Langasek wrote:
> (Particularly irrelevant for poppler, whose soname changes ~ monthly.)

Please note that the poppler frontends, that applications are supposed to be 
using does only very rarely change SONAME. the glib frontend haven't since 
it's introduction. Neither have the cpp frontend. The qt5 frontend has changed 
once. 

The Poppler Core library, which is meant to be a private shared thing between 
the frontends is changing SONAME monthly. But poppler core and the frontends 
are all in the same source, so it shouldn't affect anyone who behaves with 
poppler as documented. 

/Sune
 - who has been hacking on poppler over the last year and kept the api and abi 
of the frontends, but broken the internal api and abi multiple times.
-- 
I didn’t stop pretending when I became an adult, it’s just that when I was a 
kid I was pretending that I fit into the rules and structures of this world. 
And now that I’m an adult, I pretend that those rules and structures exist.
   - zefrank

Bug#1042031: marked as done (jruby-utils-clojure: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Tue, 05 Mar 2024 12:51:11 +
with message-id 
and subject line Re:  jruby-utils-clojure: FTBFS: E: Build killed with signal 
TERM after 150 minutes of inactivity
has caused the Debian Bug report #1042031,
regarding jruby-utils-clojure: FTBFS: E: Build killed with signal TERM after 
150 minutes of inactivity
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jruby-utils-clojure
Version: 4.0.3-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230724 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> expected: nil
>   actual: org.jruby.exceptions.NoMethodError: (NoMethodError) undefined 
> method `load_defaults' for Gem::Specification:Class
>  at RUBY. (/usr/share/jruby/lib/ruby/stdlib/rubygems.rb:1338)
> org.jruby.RubyKernel.require (org/jruby/RubyKernel.java:1017)
> RUBY. (uri:classloader:/jruby/kernel/gem_prelude.rb:3)
> org.jruby.RubyKernel.load (org/jruby/RubyKernel.java:1052)
> RUBY. (file:/usr/share/java/jruby-base.jar!/jruby/preludes.rb:4)
> 
> lein test puppetlabs.services.jruby-pool-manager.jruby-locking-test
> 
> lein test :only 
> puppetlabs.services.jruby-pool-manager.jruby-locking-test/with-lock-with-timeout-test
> 
> ERROR in (with-lock-with-timeout-test) (JRubyPool.java:368)
> Uncaught exception, not in assertion.
> expected: nil
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2023/07/24/jruby-utils-clojure_4.0.3-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230724;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230724&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 5.1.0-2

Hello,

I believe this bug is now fixed in the latest version of the package
(and JRuby) in sid.

Thanks,

-- Jérôme--- End Message ---

Processed: Re: Bug#1002789 closed by Debian FTP Masters (reply to Thomas Goirand ) (Bug#1002789: fixed in python-pycdlib 1.12.0+ds1-5)

[Debian Bug Tracking System]

Processing control commands:

> reopen 1002789
Bug #1002789 {Done: Thomas Goirand } [src:python-pycdlib] 
python-pycdlib: FTBFS: failed tests
Bug reopened
Ignoring request to alter fixed versions of bug #1002789 to the same values 
previously set
> found 1002789 1.12.0+ds1-5
Bug #1002789 [src:python-pycdlib] python-pycdlib: FTBFS: failed tests
Ignoring request to alter found versions of bug #1002789 to the same values 
previously set
> retitle 1002789 python-pycdlib: FTBFS during tests if /tmp is not a tmpfs
Bug #1002789 [src:python-pycdlib] python-pycdlib: FTBFS: failed tests
Changed Bug title to 'python-pycdlib: FTBFS during tests if /tmp is not a 
tmpfs' from 'python-pycdlib: FTBFS: failed tests'.
> severity 1002789 important
Bug #1002789 [src:python-pycdlib] python-pycdlib: FTBFS during tests if /tmp is 
not a tmpfs
Severity set to 'important' from 'serious'

-- 
1002789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1002789: closed by Debian FTP Masters (reply to Thomas Goirand ) (Bug#1002789: fixed in python-pycdlib 1.12.0+ds1-5)

[Lucas Nussbaum]

Control: reopen 1002789
Control: found 1002789 1.12.0+ds1-5
Control: retitle 1002789 python-pycdlib: FTBFS during tests if /tmp is not a 
tmpfs
Control: severity 1002789 important

On 03/03/24 at 23:29 +0100, Thomas Goirand wrote:
> On 3/1/24 15:36, Lucas Nussbaum wrote:
> > Control: reopen 1002789
> > Control: found 1002789 1.12.0+ds1-5
> > 
> > Hi all,
> > 
> > Unfortunately, I can still reproduce this failure with version
> > 1.12.0+ds1-5, as shown in the attached build log.
> > Sorry about that.
> > 
> > Let us (Santiago or myself) know if it would be useful to provide a VM
> > to reproduce this issue.
> > 
> > Lucas
> 
> Hi Lucas,
> 
> How do you explain that the package builds fine on my laptop, and on the
> Debian buildd servers, as 1.12.0+ds1-6 (that only contains a cosmetic
> clean-up of .pytest_cache on clean, compared to -5) built find after I
> uploaded it? See:
> https://buildd.debian.org/status/package.php?p=python-pycdlib&suite=sid
> 
> I'm therefore closing this bug again.
> 
> It's frustrating, I would have like to understand. Maybe something related
> to /tmp mounted as tmpfs vs a "real" partition?

Right, it looks like it only builds fine if /tmp is a tmpfs. Which looks
like a valid bug, isn't it? (I can reproduce the failure on my laptop
with /tmp on the same filesystem as the build dir, and then the failure
disapears if I mount -o bind /dev/shm /tmp).

Note that closing a bug just because you don't understand it does not
look right.

I'm setting the severity to important since we know how to make it
build.

Lucas

Processed: retitle 1065435 to aptitude: FTBFS on armhf and armel: deduced conflicting types for parameter ‘const T’ (‘long int’ and ‘__suseconds64_t’ {aka ‘long long int’}) ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 1065435 aptitude: FTBFS on armhf and armel: deduced conflicting types 
> for parameter ‘const T’ (‘long int’ and ‘__suseconds64_t’ {aka ‘long long 
> int’})
Bug #1065435 [src:aptitude] aptitude: FTBFS on armhf and armel (probably 
-Werror=implicit-function-declaration related)
Changed Bug title to 'aptitude: FTBFS on armhf and armel: deduced conflicting 
types for parameter ‘const T’ (‘long int’ and ‘__suseconds64_t’ {aka ‘long long 
int’})' from 'aptitude: FTBFS on armhf and armel (probably 
-Werror=implicit-function-declaration related)'.
> reassign 1065407 cdimage.debian.org
Bug #1065407 [debian-dvd-1] debian-dvd-1: To enable Japanese input using anthy 
and uim, uim-anthy package is neccessary for Debian-DVD-1 installation media
Warning: Unknown package 'debian-dvd-1'
Bug reassigned from package 'debian-dvd-1' to 'cdimage.debian.org'.
No longer marked as found in versions 12.5.0.
Ignoring request to alter fixed versions of bug #1065407 to the same values 
previously set
> reassign 1062802 src:pam 1.5.3-2
Bug #1062802 {Done: Sam Hartman } [libpam0t64] libpam0t64: 
file loss during upgrade due to /usr-move DEP17
Warning: Unknown package 'libpam0t64'
Bug reassigned from package 'libpam0t64' to 'src:pam'.
No longer marked as found in versions pam/1.5.3-2.
No longer marked as fixed in versions pam/1.5.3-4 and pam/1.5.3-3.
Bug #1062802 {Done: Sam Hartman } [src:pam] libpam0t64: 
file loss during upgrade due to /usr-move DEP17
Marked as found in versions pam/1.5.3-2.
> fixed 1062802 1.5.3-4
Bug #1062802 {Done: Sam Hartman } [src:pam] libpam0t64: 
file loss during upgrade due to /usr-move DEP17
Marked as fixed in versions pam/1.5.3-4.
> fixed 1062802 1.5.3-3
Bug #1062802 {Done: Sam Hartman } [src:pam] libpam0t64: 
file loss during upgrade due to /usr-move DEP17
Marked as fixed in versions pam/1.5.3-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062802
1065407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065407
1065435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065435
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1064824: node-d3: fails to export map and other functions

[Nilesh Patra]

On Mon, Mar 04, 2024 at 09:18:01PM +, Julian Gilbey wrote:
> index.js → dist/d3.js...
> (!) Conflicting re-exports
> "index.js" re-exports "map" from both 
> "../../../usr/share/nodejs/d3-array/src/index.js" and 
> "../../../usr/share/nodejs/d3-collection/src/index.js" (will be ignored).
> created dist/d3.js in 1.9s
> 
> index.js → dist/d3.min.js...
> (!) Conflicting re-exports
> "index.js" re-exports "map" from both 
> "../../../usr/share/nodejs/d3-array/src/index.js" and 
> "../../../usr/share/nodejs/d3-collection/src/index.js" (will be ignored).
> created dist/d3.min.js in 4.2s
> -

I have pushed a commit to salsa that hopefully fixes this - can you please try 
with the same and see if that
helps you somewhat?

> So it's specifically "map" that is problematic, and I just happen to
> have stumbled upon it: d3 v5 depends on d3-array version 1, but the
> version of node-d3-array in unstable is 3.2.0+~cs5.0.6-2, and this is
> causing the conflict.
> 
> I don't know the best way to fix this.  node-d3-array version was
> upgraded from 1.2.4 to 3.x about two years ago, so d3 would have had
> this bug since then, but I'm the first one to stumble upon it :-/
>
> Perhaps we could package node-d3-array-1 (version 1.2.4) and have
> node-d3 build-depends on that?

I tried to embed it and realised it is creating an unholy mess. I got it 
working eventually
but it can open a can of worms sometime later. Maybe packaging the older version
would be the way to go if my fix above does not work.

I've added yadd to the thread for more qualified advice.

Best,
Nilesh


signature.asc
Description: PGP signature

Processed: Re: Bug#1064852: incus: missing depends on iproute2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1064852 [incus] incus: missing depends on iproute2
Added tag(s) pending.

-- 
1064852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1064852: incus: missing depends on iproute2

[Mathias Gibbens]

Control: tags -1 + pending

  It's easy enough to add iproute2 as a dependency, so I've done so.
Incus already has quite a number of dependencies, and I'd like to keep
that list as small as possible, which is why I was initially reluctant
to add iproute2. I would be interested to know more about what
environment Incus is being used in that doesn't have the `ip` command
available.

  My normal testing setup for Incus is a fresh, minimal expert install
of sid via the netinst iso. During the install of the VM, I only
install the base system and deselect the "standard system utilities"
group. I do use DHCP, which looks like that might be responsible for
pulling in iproute2 for me. If there's a way to create an even more
minimal install, I'd be happy to incorporate that into my testing
routine.

Mathias


signature.asc
Description: This is a digitally signed message part

Bug#1065185: marked as done (zfs-fuse: missing build-dep on libtirpc-dev)

[Debian Bug Tracking System]

Your message dated Tue, 05 Mar 2024 11:55:10 +
with message-id 
and subject line Bug#1065185: fixed in zfs-fuse 0.7.0-27
has caused the Debian Bug report #1065185,
regarding zfs-fuse: missing build-dep on libtirpc-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zfs-fuse
Version: 0.7.0-26
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-gl...@lists.debian.org
Usertags: libtirpc-dev

Dear maintainer,

Starting with glibc 2.31, support for NIS (libnsl library) has been
moved to a separate libnsl2 package. In order to allow a smooth
transition, a libnsl-dev, which depends on libtirpc-dev, has been added
to the libc6-dev package.

The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1
NMU, as part of the 64-bit time_t transition. This causes zfs-fuse to
FTBFS in sid with:

| gcc -o lib/libnvpair/build-user/nvpair.o -c -pipe -Wall -std=c99 -Wno-switch 
-Wno-unused -Wno-missing-braces -Wno-parentheses -Wno-uninitialized 
-fno-strict-aliasing -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT 
-DTEXT_DOMAIN=\"zfs-fuse\" -ggdb -DNDEBUG -O2 -DLINUX_AIO 
-Ilib/libnvpair/include -Ilib/libsolcompat/include -I/usr/include/tirpc 
lib/libnvpair/nvpair.c
| lib/libnvpair/nvpair.c:33:10: fatal error: rpc/types.h: No such file or 
directory
|33 | #include 
|   |  ^
| compilation terminated.
| scons: *** [lib/libnvpair/build-user/nvpair.o] Error 1
| scons: building terminated because of errors.
| make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:38: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This could be fixed by adding an explicit Build-Depends on libtirpc-dev.
The glibc change will likely be reverted in the short term, but given
its a change we want to do for Trixie, this will only lower the severity
of the bug.

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: zfs-fuse
Source-Version: 0.7.0-27
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
zfs-fuse, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated zfs-fuse package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 05 Mar 2024 12:23:25 +0100
Source: zfs-fuse
Architecture: source
Version: 0.7.0-27
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1065185
Changes:
 zfs-fuse (0.7.0-27) unstable; urgency=medium
 .
   * QA upload.
   * Add libtirpc-dev build-dependency.  (Closes: #1065185)
   * Set Rules-Requires-Root: no.
   * Bump debhelper-compat to 13.
   * Do not reinvent dh_update_autotools_config etc.
Checksums-Sha1:
 f9c9a866b118f34eb6eb15a8029a73a1294bb35f 2050 zfs-fuse_0.7.0-27.dsc
 ebd91fb9fddbf1a860ece6b11a152862070301c9 28668 zfs-fuse_0.7.0-27.debian.tar.xz
 e4ba8cf4451566c164c9675220a00ca3e5a65173 6812 
zfs-fuse_0.7.0-27_source.buildinfo
Checksums-Sha256:
 c6e0f75892cdfd08f25e37b082fde9e3a8c038e9a3cc07e05116787a2e0decdb 2050 
zfs-fuse_0.7.0-27.dsc
 ac95ba629198181fe9510d91867148184ea99983992a919799820b537988a56e 28668 
zfs-fuse_0.7.0-27.debian.tar.xz
 f319e317c7dcd118c2759b3f5f7bcc07e572ea19722ec25f77add734f73d0854 6812 
zfs-fuse_0.7.0-27_source.buildinfo
Files:
 e7592c0d1a0190e9090ab91c72a431d7 2050 otherosfs optional zfs-fuse_0.7.0-27.dsc
 3683067169c59c5813f9c4090f03ecb5 28668 otherosfs optional 
zfs-fuse_0.7.0-27.debian.tar.xz
 e90c2988556aab35e6c9fc7e57f7f882 6812 otherosfs optional 
zfs-fuse_0.7.0-27_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmXnAVAQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCC6+EACMNNgihV1VDB2tS5cIiQ5O7Dg4+5OWdiID
UWBpXiO9D4lWzn6X5xv6wZMvb7R8E5c2f9ekaDMGcPqeWBEyPrU+8H4FlBYoyrOR
SLuDQQFzVxEQ3W5UGHW3UZuJx6dy0Q

Bug#1056243: django-assets autopkg tests fail with Python 3.12

[Emmanuel Arias]

Hi!

I worked on this package to fix py3.12 bug but I had some tests with the
tests. Also, I noted that upstream seems to be not active for the last 4
years (there are some PR trying to resolve py3.11 bugs). It has
webassets as b-depends that seems to be not active as well.

So, maybe is time to remove it from Debian?


-- 
cheers,
Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eam...@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
 ⠈⠳⣄


signature.asc
Description: PGP signature

Bug#1065489: mongo-c-driver: FTBFS on armhf: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘__suseconds64_t’ {aka ‘long long int’}

[Emanuele Rocca]

Source: mongo-c-driver
Version: 1.26.0-1.1
Severity: serious
Tags: ftbfs
User: debian-...@lists.debian.org
Usertags: time-t

Dear Maintainer,

mongo-c-driver fails to build from source on armhf. The failure may be
explained with the build flags introduced for the time64 migration,
which are on by default on armhf:

 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 
-Werror=implicit-function-declaration

[ 37%] Building C object 
src/libmongoc/CMakeFiles/mongoc_static.dir/src/mongoc/mongoc-error.c.o
cd /<>/obj-arm-linux-gnueabihf/src/libmongoc && /usr/bin/cc 
-DBSON_STATIC -DHAVE_STDARG_H -DHAVE_UNISTD_H -DKMS_MESSAGE_ENABLE_CRYPTO 
-DKMS_MESSAGE_ENABLE_CRYPTO_LIBCRYPTO -DKMS_MESSAGE_LITTLE_ENDIAN 
-DKMS_MSG_STATIC -DMCOMMON_NAME_PREFIX=_mongoc_mcommon -DMONGOC_COMPILATION 
-DMONGOC_STATIC -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=700 
-I/<>/src/libmongoc/../kms-message/src 
-I/<>/obj-arm-linux-gnueabihf/src/libmongoc/src 
-I/<>/obj-arm-linux-gnueabihf/src/libmongoc/src/mongoc 
-I/<>/src/libmongoc/src 
-I/<>/src/libmongoc/src/mongoc 
-I/<>/src/libmongoc/../../src/common 
-I/<>/obj-arm-linux-gnueabihf/src/libmongoc/../../src 
-I/<>/obj-arm-linux-gnueabihf/src/libmongoc/../../src/common 
-I/<>/src/libbson/src 
-I/<>/obj-arm-linux-gnueabihf/src/libbson/src 
-I/<>/src/common 
-I/<>/obj-arm-linux-gnueabihf/src/common -g -O2 
-Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Werror=implicit 
-Werror=return-type -Werror=incompatible-pointer-types -Werror=int-conversion 
-Werror=discarded-qualifiers -Werror=uninitialized -Werror -pedantic -Wall 
-Wempty-body -Wexpansion-to-defined -Wformat -Wformat-nonliteral 
-Wformat-security -Winit-self -Wmissing-include-dirs -Wredundant-decls -Wshadow 
-Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef -Wuninitialized 
-Wno-strict-aliasing -fPIC -DUTF8PROC_EXPORTS -MD -MT 
src/libmongoc/CMakeFiles/mongoc_static.dir/src/mongoc/mongoc-error.c.o -MF 
CMakeFiles/mongoc_static.dir/src/mongoc/mongoc-error.c.o.d -o 
CMakeFiles/mongoc_static.dir/src/mongoc/mongoc-error.c.o -c 
/<>/src/libmongoc/src/mongoc/mongoc-error.c
/<>/src/libmongoc/src/mongoc/mongoc-log.c: In function 
‘mongoc_log_default_handler’:
/<>/src/libmongoc/src/mongoc/mongoc-log.c:215:21: error: format 
‘%ld’ expects argument of type ‘long int’, but argument 4 has type 
‘__suseconds64_t’ {aka ‘long long int’} [-Werror=format=]
  215 | "%s.%04ld: [%5d]: %8s: %12s: %s\n",
  | ^
  | |
  | long int
  | %04lld
  216 | nowstr,
  217 | tv.tv_usec / 1000L,
  | ~~
  ||
  |__suseconds64_t {aka long long int}
cc1: all warnings being treated as errors
make[3]: *** [src/libmongoc/CMakeFiles/mongoc_shared.dir/build.make:765: 
src/libmongoc/CMakeFiles/mongoc_shared.dir/src/mongoc/mongoc-log.c.o] Error 1

Bug#1065486: sbd: FTBFS due to hardcoded libaio SONAME used in dlopen()

[Guillem Jover]

Source: sbd
Source-Version: 1.5.2-1
Severity: serious
Tags: patch upstream

Hi!

For the time64 transition I've done a local SONAME bump. This will
make this package FTBFS (once the mass binNMUs are triggered) due to
its test suite hardcoding the libaio SONAME for a dlopen() call.

Because the package is already explicitly linking against -laio (which
I guess also means there's a missing Build-Depends here), we are
guaranteed to have libaio.so available, so we can use that to avoid
hardcoding the SONAME. Of course dlopen()ing a shared library like
this is dangerous as the code might use the wrong ABI and that might
go unnoticed at build time, so perhaps it might also be worth
investigating in the future whether the dlopen is really necessary at
all (the test case is already being linked also against -laio).

The attached patch fixes the build for me with the new libaio.

Thanks,
Guillem
Description: Do not hardcode libaio SONAME
 The SONAME might change, and then the dlopen() fails. This just happened now
 as part of the time64 transition. The package is already linking explicitly
 against -laio, thus libaio.so will be guaranteed to be present, so instead
 of hardcoding the current SONAME at this point in time, simply use libaio.so.
Author: Guillem Jover 
Last-Update: 2024-03-05

---
 tests/sbd-testbed.c |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- a/tests/sbd-testbed.c
+++ b/tests/sbd-testbed.c
@@ -154,9 +154,9 @@ init (void)
 orig_fopen= (orig_fopen_f_type)dlsym_fatal(RTLD_NEXT,"fopen");
 orig_fclose   = (orig_fclose_f_type)dlsym_fatal(RTLD_NEXT,"fclose");
 
-handle = dlopen("libaio.so.1",  RTLD_NOW);
+handle = dlopen("libaio.so",  RTLD_NOW);
 if (!handle) {
-fprintf(stderr, "Failed opening libaio.so.1\n");
+fprintf(stderr, "Failed opening libaio.so\n");
 exit(1);
 }
 orig_io_setup = (orig_io_setup_f_type)dlsym_fatal(handle,"io_setup");

Bug#1062218: marked as done (libaio: NMU diff for 64-bit time_t transition)

[Debian Bug Tracking System]

Your message dated Tue, 05 Mar 2024 11:19:54 +
with message-id 
and subject line Bug#1062218: fixed in libaio 0.3.113-6
has caused the Debian Bug report #1062218,
regarding libaio: NMU diff for 64-bit time_t transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1062218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libaio
Version: 0.3.113-5
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainer,

As part of the 64-bit time_t transition required to support 32-bit
architectures in 2038 and beyond
(https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
libaio as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).

To ensure that inconsistent combinations of libraries with their
reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.

Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is
important that libraries affected by this ABI change all be uploaded close
together in time.  Therefore I have prepared a 0-day NMU for libaio
which will initially be uploaded to experimental if possible, then to
unstable after packages have cleared binary NEW.

Please find the patch for this NMU attached.

If you have any concerns about this patch, please reach out ASAP.  Although
this package will be uploaded to experimental immediately, there will be a
period of several days before we begin uploads to unstable; so if information
becomes available that your package should not be included in the transition,
there is time for us to amend the planned uploads.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libaio-0.3.113/debian/changelog libaio-0.3.113/debian/changelog
--- libaio-0.3.113/debian/changelog 2023-08-06 19:12:34.0 +
+++ libaio-0.3.113/debian/changelog 2024-01-31 19:35:56.0 +
@@ -1,3 +1,10 @@
+libaio (0.3.113-5.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Wed, 31 Jan 2024 19:35:56 +
+
 libaio (0.3.113-5) unstable; urgency=medium
 
   * Wrap fields in debian/tests/control.
diff -Nru libaio-0.3.113/debian/control libaio-0.3.113/debian/control
--- libaio-0.3.113/debian/control   2023-01-12 22:35:46.0 +
+++ libaio-0.3.113/debian/control   2024-01-31 19:35:56.0 +
@@ -11,7 +11,10 @@
  debhelper-compat (= 13),
  debhelper (>= 13.10),
 
-Package: libaio1
+Package: libaio1t64
+Provides: ${t64:Provides}
+Replaces: libaio1
+Breaks: libaio1 (<< ${source:Version})
 Architecture: linux-any
 Multi-Arch: same
 Pre-Depends:
@@ -47,7 +50,7 @@
 Multi-Arch: same
 Depends:
  ${misc:Depends},
- libaio1 (= ${binary:Version}),
+ libaio1t64 (= ${binary:Version}),
 Description: Linux kernel AIO access library - development files
  This library enables userspace to use Linux kernel asynchronous I/O
  system calls, important for the performance of databases and other
diff -Nru libaio-0.3.113/debian/libaio1.install 
libaio-0.3.113/debian/libaio1.install
--- libaio-0.3.113/debian/libaio1.install   2021-10-09 15:26:37.0 
+
+++ libaio-0.3.113/debian/libaio1.install   1970-01-01 00:00:00.0 
+
@@ -1,2 +0,0 @@
-usr/lib/*/libaio.so.1
-usr/lib/*/libaio.so.1.*
diff -Nru libaio-0.3.113/debian/libaio1.symbols 
libaio-0.3.113/debian/libaio1.symbols
--- libaio-0.3.113/debian/libaio1.symbols   2019-04-11 20:10:55.0 
+
+++ libaio-0.3.113/debian/libaio1.symbols   1970-01-01 00:00:00.0 
+
@@ -1,18 +0,0 @@
-libaio.so.1 libaio1 #MINVER#
-* Build-Depends-Package: libaio-dev
- LIBAIO_0.1@LIBAIO_0.1 0.3.9
- LIBAIO_0.4@LIBAIO_0.4 0.3.93
- LIBAIO_0.5@LIBAIO_0.5 0.3.112
- io_cancel@

Bug#1065485: file conflict with qemu-system-common / failure during upgrade

[Michael Biebl]

Package: qemu-system-data
Version: 1:8.2.1+ds-2
Severity: serious

During the lastest upgrade, I get
Preparing to unpack .../qemu-system-data_1%3a8.2.2+ds-1_all.deb ...
Unpacking qemu-system-data (1:8.2.2+ds-1) over (1:8.2.1+ds-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/qemu-system-data_1%3a8.2.2+ds-1_all.deb (--unpack):
 trying to overwrite 
'/usr/share/doc/qemu-system-common/system/arm/aspeed.html', which is also in 
package qemu-system-common 1:8.2.1+ds-2
Errors were encountered while processing:
 /var/cache/apt/archives/qemu-system-data_1%3a8.2.2+ds-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Bug#1065480: marked as done (FTBFS: error TS2307: Cannot find module 'undici-types' or its corresponding type declarations.)

[Debian Bug Tracking System]

Your message dated Tue, 05 Mar 2024 11:05:12 +
with message-id 
and subject line Bug#1065480: fixed in node-recast 0.23.4-2
has caused the Debian Bug report #1065480,
regarding FTBFS: error TS2307: Cannot find module 'undici-types' or its 
corresponding type declarations.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-recast
Version: 0.23.4-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
X-Debbugs-Cc: sweetyf...@deepin.org

Hi,

During a rebuild of node-recast, your package failed to build.

Relevant part:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
tsc
node_modules/@types/node/ts4.8/globals.d.ts(325,84): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(326,85): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(327,85): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(328,84): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(330,22): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(336,35): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(337,35): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(338,32): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(339,39): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(340,42): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(341,35): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(342,38): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(343,34): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(344,37): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(360,21): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(367,21): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(374,21): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(381,21): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
make[1]: *** [debian/rules:7: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2

Thanks!

Best regards,
Tianyu Chen @ deepin

-- System Information:
Distributor ID: Deepin
Description:Deepin 23
Release:23
Codename:   beige
Architecture: x86_64

Kernel: Linux 6.6.7-amd64-desktop-hwe (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: node-recast
Source-Version: 0.23.4-2
Done: Yadd 

We believe that the bug you reported is fixed in the latest version of
node-recast, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

De

Processed: Bug#1062218 in package libaio marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 1062218 pending
Bug #1062218 [src:libaio] libaio: NMU diff for 64-bit time_t transition
Added tag(s) pending.

-- 
1062218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1062218: in package libaio marked as pending

[Guillem Jover]

Control: tag 1062218 pending

Hi!

Bug #1062218 that you reported in package libaio has been fixed
in the debian/pkgs/libaio.git git repository. You can see the changelog below,
and you can check the diff of the fix at:

https://git.hadrons.org/cgit/debian/pkgs/libaio.git/diff/?id=8d2d6c2

---
commit 8d2d6c2930be1e34cb357ab4f1b8d42471a16f77
Author: Guillem Jover 
Date:   Tue Mar 5 11:33:36 2024 +0100

Add time64 support

- Remove dead code for syscall handling.
- Refactor code to use an internal implementation for public functions
  that handle timespec, by switching them to always use __kernel_timespec,
  and add conversion functions to map from 'struct timespec' to
  'struct __kernel_timespec', and from 'struct __kernel_timespec' to
  'struct __kernel_old_timespec'.
- Add support for io_pgetevents_time64() Linux syscall, but disable it
  for now as it only works on 32-bit kernels, but not on the compat
  mode in 64-bit kernels running 32-bit userland, will be fixed in Linux
  in parallel, as the timeouts used are supposed to be relative anyway,
  and this does not and will not break ABI.
- Add dual time32/time64 ABI support by adding io_getevents_time64() and
  io_pgetevents_time64() library functions on 32-bit architectures, that
  get redirected from the io_getevents() and io_pgetevents() functions
  when the user sets _TIME_BITS=64.
- Perform a SONAME bump to avoid stomping on upstream SONAME. Once and if
  the new symbols are accepted by upstream then we can merge that back
  into libaio.so.1 and drop the t64 packages and temporarily provide
  a compat symlink for the t64 SONAME for a smooth transition back. This
  should also be an easier way to revert this transition when there are
  no file conflicts involved, and does not block on upstream support.
- Do not rename the udeb from libaio1-udeb, as d-i does not care, and
  that would require a pointless trip through NEW. But update the shlibs
  references for the libaio1t64 rename.
- We do not need a dependency on a newer dpkg-dev nor gcc as we are
  explicitly handling the time64 dual-ABI independently of the toolchain.

Closes: #1062218

diff --git a/debian/changelog b/debian/changelog
index 4163262..5eb83fb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,34 @@ libaio (0.3.113-6) UNRELEASED; urgency=medium
 
   * Switch from future=+lfs to abi=+lfs build flags feature, and Build-Depends
 on dpkg-dev >= 1.22.0.
+  * Add time64 support:
+- Remove dead code for syscall handling.
+- Refactor code to use an internal implementation for public functions
+  that handle timespec, by switching them to always use __kernel_timespec,
+  and add conversion functions to map from 'struct timespec' to
+  'struct __kernel_timespec', and from 'struct __kernel_timespec' to
+  'struct __kernel_old_timespec'.
+- Add support for io_pgetevents_time64() Linux syscall, but disable it
+  for now as it only works on 32-bit kernels, but not on the compat
+  mode in 64-bit kernels running 32-bit userland, will be fixed in Linux
+  in parallel, as the timeouts used are supposed to be relative anyway,
+  and this does not and will not break ABI.
+- Add dual time32/time64 ABI support by adding io_getevents_time64() and
+  io_pgetevents_time64() library functions on 32-bit architectures, that
+  get redirected from the io_getevents() and io_pgetevents() functions
+  when the user sets _TIME_BITS=64.
+- Perform a SONAME bump to avoid stomping on upstream SONAME. Once and if
+  the new symbols are accepted by upstream then we can merge that back
+  into libaio.so.1 and drop the t64 packages and temporarily provide
+  a compat symlink for the t64 SONAME for a smooth transition back. This
+  should also be an easier way to revert this transition when there are
+  no file conflicts involved, and does not block on upstream support.
+- Do not rename the udeb from libaio1-udeb, as d-i does not care, and
+  that would require a pointless trip through NEW. But update the shlibs
+  references for the libaio1t64 rename.
+- We do not need a dependency on a newer dpkg-dev nor gcc as we are
+  explicitly handling the time64 dual-ABI independently of the toolchain.
+Closes: #1062218
 
  -- Guillem Jover   Wed, 17 Jan 2024 02:57:39 +0100
 

Processed: Bug#1065480 marked as pending in node-recast

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1065480 [src:node-recast] FTBFS: error TS2307: Cannot find module 
'undici-types' or its corresponding type declarations.
Added tag(s) pending.

-- 
1065480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065480: marked as pending in node-recast

[Yadd]

Control: tag -1 pending

Hello,

Bug #1065480 in node-recast 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/js-team/node-recast/-/commit/ed9f83c667ea92023a07a207aee5c873af02a925


Fix build links

Closes: #1065480


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065480

Bug#1065483: perl-base: should provide perlapi-5.38.2 on i386

[Sven Joachim]

Package: perl-base
Version: 5.38.2-3.1
Severity: serious
X-Debbugs-Cc: Sven Joachim , Steve Langasek 

On i386, perl-base provides perlapi-5.38.2t64 rather than
perlapi-5.38.2.  This makes tons of packages uninstallable or
unbuildable and is not what has been agreed upon in #1060246.

The reason is a bad check in debian/rules, line 31:

,
| # If nonempty, this will determine $Config{debian_abi} and Provides: entries
| # (otherwise, the Provides: entries will be generated by debian/mkprovides)
| perlabi =
| ifeq (,$(filter $(DEB_HOST_GNU_TYPE),i386 hurd-i386))
|   ifeq ($(DEB_HOST_ARCH_BITS),32)
| perlabi = 5.38.2t64
|   endif
| endif
`

Unfortunately DEB_HOST_GNU_TYPE does not match i386 or hurd-i386 on
these architectures:

,
| $ dpkg-architecture -ai386 -qDEB_HOST_GNU_TYPE 2>/dev/null
| i686-linux-gnu
| $ dpkg-architecture -ahurd-i386 -qDEB_HOST_GNU_TYPE 2>/dev/null
| i686-gnu
`

You may want to filter on DEB_HOST_ARCH instead (make sure it is
defined).  A quick fix would be appreciated, because reverse
dependencies are likely going to pick up the wrong perlapi Provides.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Processed: raise bug severity, as Ceph 18.2.1 is now in unstable without 32 bits support

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1053195 serious
Bug #1053195 [src:nfs-ganesha] Please remove librados-dev build-depends on all 
32 bits arch
Severity set to 'serious' from 'important'
> severity 1053169 serious
Bug #1053169 [src:tcmu] Please remove librbd-dev build-depends on all 32 bits 
arch
Severity set to 'serious' from 'important'
> severity 1053196 serious
Bug #1053196 [uwsgi] Please remove librados-dev build-depends on all 32 bits 
arch
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1053169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053169
1053195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053195
1053196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1064377: marked as done (tcl-expect: identified for time_t transition but no ABI in shlibs)

[Debian Bug Tracking System]

Your message dated Tue, 5 Mar 2024 13:34:19 +0300
with message-id 

and subject line Re: Bug#1064377: tcl-expect: identified for time_t transition 
but no ABI in shlibs
has caused the Debian Bug report #1064377,
regarding tcl-expect: identified for time_t transition but no ABI in shlibs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1064377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tcl-expect
Version: 5.45.4-2build1
Severity: serious
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainers,

Analysis of the archive for the 64-bit time_t transition[0][1] identifies
tcl-expect as an affected package, on the basis that the headers could
not be compiled and analyzed out of the box using abi-compliance-checker[2],
so we have to assume it's affected.

However, tcl-expect' shlibs file declares a dependency on a library
package name that contains no ABI information:

$ cat DEBIAN/shlibs
libexpect 5.45 tcl-expect
$

It is therefore not obvious that we should rename the package to
'tcp-expect-t64' as part of this transition.

Looking at the archive, there is a package built from a separate source
package, 'skycat', which depends on this library

Since there is no self-evident thing to do with the library package name
here, we will not be handling this package as part of the mass NMUs.
Instead I am filing a serious bug because partial upgrades from bookworm to
trixie on 32-bit architectures (upgrading tcl-expect without also upgrading
skycat) will result in ABI skew and may result in broken behavior.

Cheers,
mwh

[0] https://wiki.debian.org/ReleaseGoals/64bit-time
[1] https://lists.debian.org/debian-devel/2024/01/msg00041.html
[2] 
https://adrien.dcln.fr/misc/armhf-time_t/2024-02-16T21%3A19%3A00/logs/tcl-expect-dev/base/log.txt


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-17-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hi Steve,

On Mon, Feb 26, 2024 at 1:12 AM Steve Langasek  wrote:
>
> Control: severity -1 normal
>
> Note that there are no reverse-dependencies in the archive that link against
> libexpect, so I think we can downgrade this bug (or close wontfix, at the
> maintainer's discretion).

Also, as far as I can see, libexpect does not expose time_t (it uses
it only internally), so I'm
closing this bug.

Cheers!
-- 
Sergei Golovan--- End Message ---

Bug#1065395: spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space

[Paul Gevers]

Hi

On 05-03-2024 10:16 a.m., Andreas Beckmann wrote:

Feel free to block 15-17 temporarily, too.


I already did that ;).

I'll try when I see 14 in the archive on s390x.

Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065480: FTBFS: error TS2307: Cannot find module 'undici-types' or its corresponding type declarations.

[Tianyu Chen]

Source: node-recast
Version: 0.23.4-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
X-Debbugs-Cc: sweetyf...@deepin.org

Hi,

During a rebuild of node-recast, your package failed to build.

Relevant part:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
tsc
node_modules/@types/node/ts4.8/globals.d.ts(325,84): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(326,85): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(327,85): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(328,84): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(330,22): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(336,35): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(337,35): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(338,32): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(339,39): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(340,42): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(341,35): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(342,38): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(343,34): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(344,37): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(360,21): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(367,21): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(374,21): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
node_modules/@types/node/ts4.8/globals.d.ts(381,21): error TS2307: 
Cannot find module 'undici-types' or its corresponding type declarations.
make[1]: *** [debian/rules:7: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:4: binary] Error 2

Thanks!

Best regards,
Tianyu Chen @ deepin

-- System Information:
Distributor ID: Deepin
Description:Deepin 23
Release:23
Codename:   beige
Architecture: x86_64

Kernel: Linux 6.6.7-amd64-desktop-hwe (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1065395: spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space

[Andreas Beckmann]

On 05/03/2024 07.45, Paul Gevers wrote:
In the upstream report you mention it's the same across all versions and 
yesterday we had the same problem with -15. Will you fix the other 
versions too? Do you want me to clone this bug for that?


I'll update all 4 branches over the next days, no need for extra bugs ;-)
But first I'd like to see the s390x build happen and your confirmation 
that this unbreaks the CI infrastructure. But at least ppc64 and sparc64 
built with 500MB instead of 40GB now ;-)

Feel free to block 15-17 temporarily, too.

Andreas

Bug#1065461: libreoffice-common: disabling libreoffice-evolution has moved evolocal.odb to libreoffice-common

[Andreas Beckmann]

On 05/03/2024 06.40, Rene Engelhard wrote:
But I need to do the Replaces: libreoffice-common in -evolution anyways 
now?


You added some, and it's probably better to be safe than sorry ;-)
On a quick glance I also didn't spot a strictly enough versioned 
dependency on -common that would ensure the new -common getting 
unpackged first.


Andreas

Bug#1065477: owncloud-client: Uploads to unstable must have a higher version than present in unstable.

[Sebastian Ramacher]

Source: owncloud-client
Version: 4.2.0.11670+dfsg-1.1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: sramac...@debian.org

Version check failed:
Your upload included the binary package dolphin-owncloud, version 
4.2.0.11670+dfsg-1.1, for amd64,
however unstable already has version 5.0.0-1+b1.
Uploads to unstable must have a higher version than present in unstable.

Cheers
-- 
Sebastian Ramacher