Re: Coq packages in Debian : difficult transitions

2022-08-02 Thread Holger Levsen 
On Sun, Jul 31, 2022 at 01:00:03PM +0200, julien.pu...@gmail.com wrote:
> > Please file a transition bug. The mailing list has a high volume and
> > non-bug mails may be overlooked.
> Well, I would file a bug for a specific transition, but first I would
> like to discuss how to handle transitions for Coq-related packages in
> general.

file a general bug against release.debian.org then. The mailing list has a
high volume and non-bug mails may be overlooked. ;)


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

If you upload your address book to "the cloud", I don't want to be in it.


signature.asc
Description: PGP signature

Bug#1016531: ITP: node-ky -- tiny and elegant HTTP client based on the browser Fetch API

2022-08-02 Thread Jonas Smedegaard 
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 
X-Debbugs-Cc: debian-devel@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: node-ky
  Version : 0.31.1
  Upstream Author : Sindre Sorhus 
* URL : https://github.com/sindresorhus/ky
* License : Expat
  Programming Lang: JavaScript
  Description : tiny and elegant HTTP client based on the browser Fetch API

 Ky is a tiny and elegant HTTP client
 based on the browser Fetch API.
 Ky targets modern browsers and Deno.
 For older browsers,
 you will need to transpile and use fetch and globalThis polyfills.
 For use only with Node.js, check out Got.
 For isomorphic needs (like server-side rendering),
 check out ky-universal.
 .
 It's just a tiny file with no dependencies.
 .
 Benefits over plain fetch:
  * Simpler API
  * Method shortcuts ( ky.post() )
  * Treats non-2xx status codes as errors (after redirects)
  * Retries failed requests
  * JSON option
  * Timeout support
  * URL prefix option
  * Instances with custom defaults
  * Hooks
 .
 Deno is a runtime for JavaScript and TypeScript
 that is based on the V8 JavaScript engine
 and the Rust programming language.
 .
 A polyfill is code that implements a feature
 on web browsers that do not support the feature.
 .
 Node.js is an event-based server-side JavaScript engine.

This package is needed by solid-server (bug#910111).
It will be maintained in the js-team section of Salsa, here:
.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmLpFZUACgkQLHwxRsGg
ASHPtQ/9Hq6XvMbuH1z4Txj9XfbGvasPTEw7oS78CWaDe9pWmuE6LvBD1BPDMlw6
rk7aZGsxndQaIBCk1zsimcV7i6Q0nkl4tkVy6bB18M2ivpDi99oiaTkPYtHVcinN
KG1aX4KX0U5qHghQAdCUPjrCKFIM4qaLlgoLSN+H+GNWOnqHok87Bh1dgkiaJBjE
AYGTwlVYA+2/OPhcJQGbwhed4vvODhraPzXwME4f0KMj7wfDXB1hjxgJX/lou0Yd
4OTTYnILme0yPIiobUyTqtcYWNDRGpRCiHZdIx5KtvGPz+1MgdimB8t9ZckU+of4
ZYw3FTftL09FAvZDtDntRlyrvomUxloa/XjTa88BKe3r+OLFgBWS9EiR02tzOx2J
35OMPCMdo+vx41EpTjQUeVg5co8UAKDEG+htJhE9XYYKSdfNPWUvYFj9wh4eUlnj
yG4GNzvDJDT6frYeDcKEtYNNLQUQ3yJlRYoXSNFK8owJB2SPkjs3AfAorGRG6Qku
GNASgHKanuV39HFjq8a1YmQlmKeRgtPp/E0SCMHDAxYLVzdLlNJfjqoTen93dKWs
XinxRrRyREPKNO3qpe2M210qYPlbn6lOA8/ILpEgdgu4To8SSTK+9PXu5ZMffiAd
JHVV9pKJdIo9GVmHx6vPFqOGcACoWPt6V5hee/dgPgSierKf5Jg=
=9jb1
-END PGP SIGNATURE-

Re: Idea: autopkgtest on big-endian for 'Architecture: all' packages to catch endian bugs

2022-08-02 Thread Didier 'OdyX' Raboud 
Le mardi, 2 août 2022, 18.00:40 h CEST Edward Betts a écrit :
> I recently packaged a Python module called sqlite-fts4 written by Simon
> Willison. The package is pure Python, so is 'Architecture: all', but it
> fails on big-endian architectures. The test suite catches this failure.
> 
> The bug was spotted by OpenSUSE because they tried to run the test suite on
> s390x. They filed a bug which upstream has fixed.
> 
> https://github.com/simonw/sqlite-fts4/issues/6
> 
> Simon has written some posts about this problem.
> 
> https://til.simonwillison.net/python/struct-endianness
> https://til.simonwillison.net/docker/emulate-s390x-with-qemu
> 
> It would be nice if the Debian infrastructure could catch this class of bug.
> 
> Building the sqlite-fts4 Debian package runs the test suite, and I've
> configured it to run the tests via autopkgtest.

If these tests are run at build-time, errors halt the build and that provides 
the largest coverage. It's also usually easier to iterate and test than 
autopkgtest.

-- 
OdyX

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

Re: Idea: autopkgtest on big-endian for 'Architecture: all' packages to catch endian bugs

2022-08-02 Thread David Prévot 

Hi,

Le 02/08/2022 à 18:00, Edward Betts a écrit :
[…]

I wonder if it would be possible to routinely run the autopkgtests on s390x,
or another big-endian architecture, for 'Architecture: all' packages and make
the results available.


AFAICT, they already are. E.g. .

Regards

taffit


OpenPGP_signature
Description: OpenPGP digital signature

Re: Idea: autopkgtest on big-endian for 'Architecture: all' packages to catch endian bugs

2022-08-02 Thread Paul Gevers 

Hi Edward,

On 02-08-2022 18:00, Edward Betts wrote:

I wonder if it would be possible to routinely run the autopkgtests on s390x,
or another big-endian architecture, for 'Architecture: all' packages and make
the results available.


We run all autopkgtests on all architectures we have available. A 
failure on s390x should block you package from migrating already. 
Unfortunately, we enabled s390x about two months after your package 
migrated.



Has this been suggested or attempted before?


It's being done, and the result shows that indeed your package fails on 
s390x: https://ci.debian.net/packages/s/sqlite-fts4/ (as you already 
reported in a later message.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016563: debhelper: Should dh_dwz be dropped?

2022-08-02 Thread Adrian Bunk 
Package: debhelper
Version: 13.8
Severity: serious
X-Debbugs-Cc: debian-devel@lists.debian.org

[ debian-devel is in Cc for getting further input. ]

dh_dwz is part of the standard sequence in dh since debhelper compat 12.

dwz offers small optimizations of debug info, the typical benefit
seems to be ~ 3% size reduction.

These optimizations are only in the -dbgsym packages that nearly
noone installs and nearly noone uses.

Debug info is super useful when needed, but it is not installed by
default and dwz optimizations have little practical relevance in the
cases when it is used.

OTOH, the cases where dh_dwz has created additional work for maintainers
are many.[1]

dwz is processing debug info from several producers on many architectures,
and this sometimes breaks in various ways.

On arm64, gcc in stable sometime produces debug info that dwz in
stable cannot handle.[2]

C++ code can result in huge debuginfo, resulting in dwz exhausting
the address space on 32bit architectures, requiring workarounds from
maintainers.[3]

clang 14 which is now default in instable defaults to DWARF 5,
and dwz in unstable has some problems with that.[4,5]

Scroll through [1] for more workarounds for problems in dwz.

The track record of such bugs in dwz getting fixed swiftly is not good.
This is a real problem if dwz is a core toolchain tool most packages
are using by default, and usually maintainers are forced to use
override_dh_dwz whenever dwz chokes on what it is supposed to process.

IMHO the small benefits of dh_dwz are not worth the constant extra work
it causes, and it should be dropped from the standard sequence in dh.

Dropping dh_dwz from the standard sequence in dh could also be done
in the compat levels 12 and 13 since such a change should not cause
user-visible changes (except for a slight size increase of -dbgsym)

Ignoring errors from dh_dwz by default might work if we can trust
that dwz does not touch the file in case of errors, but it feels
wrong to ignore errors.


[1] https://codesearch.debian.net/search?q=override_dh_dwz&literal=1
[2] 
https://sources.debian.org/src/qt6-base/6.2.4%2Bdfsg-10~bpo11%2B1/debian/rules/#L97
[3] https://sources.debian.org/src/qtcreator/8.0.0-2/debian/rules/#L66
[4] https://bugs.debian.org/1016329
[5] https://bugs.debian.org/1016330