Bug#1038001: librem-ec-acpi-dkms: module fails to build for Linux 6.3
Package: librem-ec-acpi-dkms Version: 0.9.1-4 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: piuparts DKMS make.log for librem_ec_acpi-0.9.1 for kernel 6.3.0-1-amd64 (x86_64) Thu Jun 15 10:09:49 UTC 2023 make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64' CC [M] /var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.o /var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:276:24: error: initialization of 'int (*)(struct power_supply *, struct acpi_battery_hook *)' from incompatible pointer type 'int (*)(struct power_supply *)' [-Werror=incompatible-pointer-types] 276 | .add_battery = librem_ec_battery_add, |^ /var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:276:24: note: (near initialization for 'librem_ec_battery_hook.add_battery') /var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:277:27: error: initialization of 'int (*)(struct power_supply *, struct acpi_battery_hook *)' from incompatible pointer type 'int (*)(struct power_supply *)' [-Werror=incompatible-pointer-types] 277 | .remove_battery = librem_ec_battery_remove, | ^~~~ /var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:277:27: note: (near initialization for 'librem_ec_battery_hook.remove_battery') /var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:773:27: error: initialization of 'void (*)(struct acpi_device *)' from incompatible pointer type 'int (*)(struct acpi_device *)' [-Werror=incompatible-pointer-types] 773 | .remove = librem_ec_remove, | ^~~~ /var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.c:773:27: note: (near initialization for 'librem_ec_driver.ops.remove') cc1: some warnings being treated as errors make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.build:257: /var/lib/dkms/librem_ec_acpi/0.9.1/build/librem_ec_acpi.o] Error 1 make: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050: /var/lib/dkms/librem_ec_acpi/0.9.1/build] Error 2 make: Leaving directory '/usr/src/linux-headers-6.3.0-1-amd64' Andreas
Bug#1037999: jool-dkms: module fails to build for Linux 6.3
Package: jool-dkms Version: 4.1.9-1 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: piuparts DKMS make.log for jool-dkms-4.1.9 for kernel 6.3.0-1-amd64 (x86_64) Thu Jun 15 10:07:23 UTC 2023 make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64' CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc7915/4to6.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc7915/6to4.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc7915/common.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/address_xlat.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc7915/core.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/dev.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/kernel_hook_netfilter.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/kernel_hook_iptables.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/log.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/address.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/atomic_config.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/icmp_wrapper.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/init.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/ipv6_hdr_iterator.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/joold.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/packet.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rfc6052.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/rtrie.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/stats.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/types.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/translation_state.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/route_out.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/skbuff.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/core.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/error_pool.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/timer.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/trace.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/wkmalloc.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/wrapper-config.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/wrapper-global.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/wrapper-types.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/xlator.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/steps/send_packet.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/address.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/atomic_config.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/attribute.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_handler.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_core.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/bib.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/denylist4.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/eam.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/global.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/instance.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/joold.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_common.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/pool4.o CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/session.o /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_handler.c:205:21: error: initialization of 'int (*)(const struct genl_split_ops *, struct sk_buff *, struct genl_info *)' from incompatible pointer type 'int (*)(const struct genl_ops *, struct sk_buff *, struct genl_info *)' [-Werror=incompatible-pointer-types] 205 | .pre_doit = pre_handle_request, | ^~ /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_handler.c:205:21: note: (near initialization for 'jool_family.pre_doit') /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_handler.c:206:22: error: initialization of 'void (*)(const struct genl_split_ops *, struct sk_buff *, struct genl_info *)' from incompatible pointer type 'void (*)(const struct genl_ops *, struct sk_buff *, struct genl_info *)' [-Werror=incompatible-pointer-types] 206 | .post_doit = post_handle_request, | ^~~ /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/nl_handler.c:206:22: note: (near initialization for 'jool_family.post_doit') CC [M] /var/lib/dkms/jool-dkms/4.1.9/build/src/mod/common/nl/stats.o cc1: some warnings being treated as errors make[1]: ***
Bug#1037998: gost-crypto-dkms: module fails to build for Linux 6.3: error: implicit declaration of function 'crypto_tfm_ctx'
Package: gost-crypto-dkms Version: 0.3.4-4 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: piuparts DKMS make.log for gost-crypto-0.3.4 for kernel 6.3.0-1-amd64 (x86_64) Thu Jun 15 10:04:49 UTC 2023 make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64' CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/gost28147_basic.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/gost28147_modes.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/gosthash94_generic.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/kuznyechik_generic.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/streebog_generic.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/testmgr.o CC [M] /var/lib/dkms/gost-crypto/0.3.4/build/gost-test-main.o /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c: In function 'magma_set_key': /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c:25:40: error: implicit declaration of function 'crypto_tfm_ctx' [-Werror=implicit-function-declaration] 25 | struct crypto_magma_ctx *ctx = crypto_tfm_ctx(tfm); |^~ /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c:25:40: warning: initialization of 'struct crypto_magma_ctx *' from 'int' makes pointer from integer without a cast [-Wint-conversion] /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c: In function 'magma_encrypt': /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c:39:46: warning: initialization of 'const struct crypto_magma_ctx *' from 'int' makes pointer from integer without a cast [-Wint-conversion] 39 | const struct crypto_magma_ctx *ctx = crypto_tfm_ctx(tfm); | ^~ /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c: In function 'magma_decrypt': /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.c:52:46: warning: initialization of 'const struct crypto_magma_ctx *' from 'int' makes pointer from integer without a cast [-Wint-conversion] 52 | const struct crypto_magma_ctx *ctx = crypto_tfm_ctx(tfm); | ^~ cc1: some warnings being treated as errors make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.build:257: /var/lib/dkms/gost-crypto/0.3.4/build/magma_generic.o] Error 1 make[1]: *** Waiting for unfinished jobs make: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050: /var/lib/dkms/gost-crypto/0.3.4/build] Error 2 make: Leaving directory '/usr/src/linux-headers-6.3.0-1-amd64' Andreas
Bug#1037997: evdi-dkms: module fails to build for Linux 6.3: error: implicit declaration of function 'drm_encoder_cleanup'
Package: evdi-dkms
Version: 1.12.0+dfsg-0.3
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts
DKMS make.log for evdi-1.12.0+dfsg for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 09:56:32 UTC 2023
make: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_drv.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_dev.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_sysfs.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_modeset.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_connector.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_fb.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_gem.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_painter.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_params.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_cursor.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_debug.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o
CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_ioc32.o
In file included from /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_connector.c:19:
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.h:196:72: warning: 'struct
i2c_msg' declared inside parameter list will not be visible outside of this
definition or declaration
196 | bool evdi_painter_i2c_data_notify(struct evdi_painter *painter, struct
i2c_msg *msg);
|
^~~
In file included from /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:21:
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.h:196:72: warning: 'struct
i2c_msg' declared inside parameter list will not be visible outside of this
definition or declaration
196 | bool evdi_painter_i2c_data_notify(struct evdi_painter *painter, struct
i2c_msg *msg);
|
^~~
In file included from
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_dev.c:30:
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.h:196:72: warning: 'struct
i2c_msg' declared inside parameter list will not be visible outside of this
definition or declaration
196 | bool evdi_painter_i2c_data_notify(struct evdi_painter *painter, struct
i2c_msg *msg);
|
^~~
In file included from /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_gem.c:24:
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.h:196:72: warning: 'struct
i2c_msg' declared inside parameter list will not be visible outside of this
definition or declaration
196 | bool evdi_painter_i2c_data_notify(struct evdi_painter *painter, struct
i2c_msg *msg);
|
^~~
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c: In function
'evdi_enc_destroy':
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:26:9: error: implicit
declaration of function 'drm_encoder_cleanup'; did you mean 'drm_crtc_cleanup'?
[-Werror=implicit-function-declaration]
26 | drm_encoder_cleanup(encoder);
| ^~~
| drm_crtc_cleanup
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c: At top level:
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:38:21: error: variable
'evdi_enc_helper_funcs' has initializer but incomplete type
38 | static const struct drm_encoder_helper_funcs evdi_enc_helper_funcs = {
| ^~~~
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:39:10: error: 'const struct
drm_encoder_helper_funcs' has no member named 'enable'
39 | .enable = evdi_encoder_enable,
| ^~
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:39:19: warning: excess
elements in struct initializer
39 | .enable = evdi_encoder_enable,
| ^~~
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:39:19: note: (near
initialization for 'evdi_enc_helper_funcs')
In file included from /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_cursor.c:33:
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.h:196:72: warning: 'struct
i2c_msg' declared inside parameter list will not be visible outside of this
definition or declaration
196 | bool evdi_painter_i2c_data_notify(struct evdi_painter *painter, struct
i2c_msg *msg);
|
^~~
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:40:10: error: 'const struct
drm_encoder_helper_funcs' has no member named 'disable'
40 | .disable = evdi_encoder_disable
| ^~~
/var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.c:40:20: warning: excess
elements in struct
Bug#1037995: digimend-dkms: module fails to build for Linux 6.3: error: implicit declaration of function 'hid_is_using_ll_driver'
Package: digimend-dkms
Version: 11-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts
DKMS make.log for digimend-11 for kernel 6.3.0-1-amd64 (x86_64)
Thu Jun 15 09:51:43 UTC 2023
make -C /lib/modules/6.3.0-1-amd64/build M=/var/lib/dkms/digimend/11/build
modules
make[1]: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
CC [M] /var/lib/dkms/digimend/11/build/hid-kye.o
CC [M] /var/lib/dkms/digimend/11/build/hid-uclogic-core.o
CC [M] /var/lib/dkms/digimend/11/build/hid-uclogic-rdesc.o
CC [M] /var/lib/dkms/digimend/11/build/hid-uclogic-params.o
CC [M] /var/lib/dkms/digimend/11/build/hid-polostar.o
CC [M] /var/lib/dkms/digimend/11/build/hid-viewsonic.o
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c: In function
'uclogic_params_init':
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1227:17: error: implicit
declaration of function 'hid_is_using_ll_driver'
[-Werror=implicit-function-declaration]
1227 | || !hid_is_using_ll_driver(hdev, _hid_driver)
| ^~
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1227:47: error:
'usb_hid_driver' undeclared (first use in this function); did you mean
'to_hid_driver'?
1227 | || !hid_is_using_ll_driver(hdev, _hid_driver)
| ^~
| to_hid_driver
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1227:47: note: each
undeclared identifier is reported only once for each function it appears in
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1349:20: warning: this
statement may fall through [-Wimplicit-fallthrough=]
1349 | if (bNumInterfaces != 3) {
|^
/var/lib/dkms/digimend/11/build/hid-uclogic-params.c:1367:9: note: here
1367 | case VID_PID(USB_VENDOR_ID_HUION,
| ^~~~
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-6.3.0-1-common/scripts/Makefile.build:257:
/var/lib/dkms/digimend/11/build/hid-uclogic-params.o] Error 1
make[2]: *** Waiting for unfinished jobs
make[1]: *** [/usr/src/linux-headers-6.3.0-1-common/Makefile:2050:
/var/lib/dkms/digimend/11/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.3.0-1-amd64'
make: *** [Makefile:25: modules] Error 2
Andreas
Bug#1037993: dahdi-dkms: module fails to build for Linux 6.3
Package: dahdi-dkms Version: 1:2.11.1.0.20170917~dfsg-8.4 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: piuparts DKMS make.log for dahdi-2.11.1.0.20170917 for kernel 6.3.0-1-amd64 (x86_64) Thu Jun 15 09:40:51 UTC 2023 make -C /lib/modules/6.3.0-1-amd64/build KBUILD_EXTMOD=/var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi DAHDI_INCLUDE=/var/lib/dkms/dahdi/2.11.1.0.20170917/build/include DAHDI_MODULES_EXTRA="dahdi_dummy.o dahdi_echocan_oslec.o " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m make[1]: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64' CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_adpcm_chan.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_channel.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_open.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_stats.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_conf_bridge.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_debug.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_events.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_interrupts.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_memory.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_miscellaneous.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_mixer.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_phasing_tsst.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_playout_buf.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_remote_debug.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tlv.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tone_detection.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsi_cnct.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsst.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/apilib/bt/octapi_bt0.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/apilib/largmath/octapi_largmath.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/apilib/llman/octapi_llman.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/oct612x-user.o LD [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/oct612x/oct612x.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wct4xxp/base.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wct4xxp/vpm450m.o LD [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wct4xxp/wct4xxp.o CC [M] /var/lib/dkms/dahdi/2.11.1.0.20170917/build/drivers/dahdi/wctc4xxp/base.o In file included from /usr/src/linux-headers-6.3.0-1-common/include/linux/string.h:254, from /usr/src/linux-headers-6.3.0-1-common/include/linux/bitmap.h:11, from /usr/src/linux-headers-6.3.0-1-common/include/linux/cpumask.h:12, from /usr/src/linux-headers-6.3.0-1-common/arch/x86/include/asm/paravirt.h:17, from /usr/src/linux-headers-6.3.0-1-common/arch/x86/include/asm/cpuid.h:62, from /usr/src/linux-headers-6.3.0-1-common/arch/x86/include/asm/processor.h:19, from /usr/src/linux-headers-6.3.0-1-common/arch/x86/include/asm/timex.h:5, from /usr/src/linux-headers-6.3.0-1-common/include/linux/timex.h:67, from /usr/src/linux-headers-6.3.0-1-common/include/linux/time32.h:13, from /usr/src/linux-headers-6.3.0-1-common/include/linux/time.h:60, from /usr/src/linux-headers-6.3.0-1-common/include/linux/stat.h:19, from /usr/src/linux-headers-6.3.0-1-common/include/linux/module.h:13, from
Bug#1037990: bookworm-pu: package nvidia-support/20220217+3~deb12u1
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] Upgrades from bullseye to bookworm may fail while building kernel modules with dkms if some obsolete nvidia-*-dkms packages (that have no successor in bookworm) are still installed. (The dkms hook in bookworm no longer returns success if building a module has failed.) Let's add some Breaks against them (to nvidia-installer-cleanup which has the highest score from apt in these scenarios), to ensure the obsolete packages (and anything depending on them) gets removed during the upgrade to bookworm. [ Impact ] upgrade failures [ Tests ] lots of piuparts upgrade tests in my local piuparts instance (which handles non-free, too) [ Risks ] low, only affect packages not in bookworm [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable [ Changes ] +nvidia-support (20220217+3) unstable; urgency=medium + + * nvidia-installer-cleanup: Add Breaks against obsolete nvidia-*-dkms +packages from bullseye that are incompatible with the bookworm kernel. [ Other info ] Andreas diff --git a/debian/changelog b/debian/changelog index 4fa6b49..15fda43 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,16 @@ +nvidia-support (20220217+3~deb12u1) bookworm; urgency=medium + + * Rebuild for bookworm. + + -- Andreas Beckmann Thu, 15 Jun 2023 10:37:21 +0200 + +nvidia-support (20220217+3) unstable; urgency=medium + + * nvidia-installer-cleanup: Add Breaks against obsolete nvidia-*-dkms +packages from bullseye that are incompatible with the bookworm kernel. + + -- Andreas Beckmann Mon, 12 Jun 2023 16:55:42 +0200 + nvidia-support (20220217+2) unstable; urgency=medium [ Andreas Beckmann ] diff --git a/debian/control b/debian/control index 3947885..e51c7f0 100644 --- a/debian/control +++ b/debian/control @@ -31,6 +31,9 @@ Conflicts: nvidia-current, nvidia-current-updates, nvidia-driver-binary, +Breaks: + nvidia-tesla-418-kernel-dkms (<< 418.226.00-9~), + nvidia-tesla-460-kernel-dkms (<< 460.106.00-9~), Description: cleanup after driver installation with the nvidia-installer This package ensures that no remnants of the non-free NVIDIA graphics drivers that were installed with the nvidia-installer remain on the
Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye
Control: unmerge -1 Control: reassign -1 debianutils 5.7-0.4 Control: affects -1 + src:9base Control: tag -1 patch pending On 13/06/2023 07.26, Helmut Grohne wrote: The entry is added by /usr/lib/usrmerge/convert-etc-shells (which is the policy violation this bug has been merged into). The merging strategy there is based on a knowledge of the symlinks that should exist rather than looking them up in the filesystem. So this is two distinct bugs actually. We also need to fix update-shells to properly deal with update-alternatives using the patch above. Let's use this bug for the debianutils side. I've prepared a NMU with three changes: https://salsa.debian.org/anbe/debianutils/-/commits/fix-update-shells * avoid creating duplicate entries in /etc/shells * handle /bin/sh as defined in the template file * fix canonicalization of shells that are symlinks Especially with the /bin/sh change in place, update-shells and convert-etc-shells should produce similar results. convert-etc-shells needs to call update-shells (before manipulating /etc/shells on its own, s.t. the statefile gets updated), and maybe it can be replaced entirely by update-shells. Andreas
Bug#1037928: libmsgpack-c-dev: missing Breaks+Replaces: libmsgpack-dev (<< 6)
Package: libmsgpack-c-dev Version: 6.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libmsgpack-c-dev_6.0.0-1_amd64.deb ... Unpacking libmsgpack-c-dev:amd64 (6.0.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libmsgpack-c-dev_6.0.0-1_amd64.deb (--unpack): trying to overwrite '/usr/include/msgpack/fbuffer.h', which is also in package libmsgpack-dev:amd64 4.0.0-3 Errors were encountered while processing: /var/cache/apt/archives/libmsgpack-c-dev_6.0.0-1_amd64.deb cheers, Andreas libmsgpack-dev=4.0.0-3_libmsgpack-c-dev=6.0.0-1.log.gz Description: application/gzip
Bug#1037924: systemd-dev: missing Breaks+Replaces: udev (<< 253-2~)
Package: systemd-dev Version: 253-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../systemd-dev_253-2_all.deb ... Unpacking systemd-dev (253-2) ... dpkg: error processing archive /var/cache/apt/archives/systemd-dev_253-2_all.deb (--unpack): trying to overwrite '/usr/share/pkgconfig/udev.pc', which is also in package udev 252.11-1 Errors were encountered while processing: /var/cache/apt/archives/systemd-dev_253-2_all.deb cheers, Andreas udev=252.11-1_systemd-dev=253-2.log.gz Description: application/gzip
Bug#1037917: gnutls28: leaves processes running after build: gnutls-serv, openssl s_server
Source: gnutls28 Version: 3.8.0+git20230529-1 Severity: serious Hi, after building gnutls28/experimental with pbuilder, there are a lot of gnutls-serv and a few openssl s_server processes running, preventing pbuilder to cleanup the chroot. Andreas
Bug#1037466: nmu: spirv-llvm-translator-16_16.0.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu spirv-llvm-translator-16_16.0.0-1 . ANY . experimental . -m "Rebuild against llvm 16.0.5" the updated llvm-16/gcc-13 combination causes symbol changes that I'd like to collect before uploading the package to unstable Andreas
Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye
Now I'm really confused: I start with an unmerged sid chroot, install 9base there. Then I remove /etc/unsupported-skip-usrmerge-conversion and install usrmerge. Now /etc/shells contains # /etc/shells: valid login shells /bin/sh /bin/bash /bin/rbash /bin/dash /bin/rc /usr/lib/plan9/bin/rc /usr/lib/plan9/bin/rc /usr/bin/sh /usr/bin/bash /usr/bin/rbash /usr/bin/dash /usr/bin/rc and /var/lib/shells.state /bin/bash /bin/rbash /bin/dash /bin/rc /usr/lib/plan9/bin/rc /usr/lib/plan9/bin/rc Then I run update-shells which does not modify /etc/shells, but the statefile now contains /bin/bash /usr/bin/bash /bin/rbash /usr/bin/rbash /bin/dash /usr/bin/dash /bin/rc /usr/lib/plan9/bin/rc /usr/lib/plan9/bin/rc So the /bin entries for bash/rbash/dash get their /usr counterparts added, but /bin/rc does not. OK, back to the minimal unmerged sid chroot, without 9base this time. After installation of usrmerge and successful conversio /etc/shells contains # /etc/shells: valid login shells /bin/sh /bin/bash /bin/rbash /bin/dash /usr/bin/sh /usr/bin/bash /usr/bin/rbash /usr/bin/dash and /var/lib/shells.state contains /bin/bash /bin/rbash /bin/dash Then I delete all /usr/bin entries from /etc/shells (sed -i /usr/d /etc/shells) and run update-shells, resulting in /etc/shells containing # /etc/shells: valid login shells /bin/sh /bin/bash /bin/rbash /bin/dash /usr/bin/bash /usr/bin/rbash /usr/bin/dash (i.e. only /usr/bin/sh is missing compared to the file made by usrmerge) and the statefile contains /bin/bash /usr/bin/bash /bin/rbash /usr/bin/rbash /bin/dash /usr/bin/dash This seems to imply that usrmerge could call update-shells to perform most of the changes it does to /etc/shells. (And to update /var/lib/shells.state at the same time) ... later ... much later ... After reading update-shells several times (and still not fully getting how it works (or at least should work)), I think its behavior is not well defined in the context of alternatives as used by 9base. At least this line seems to be wrong: realshell=$(dirname "$(dpkg-realpath --root "$ROOT" "$line")")/$(basename "$line") It resolves e.g. /usr/bin/clang++-14 to non-existant /usr/lib/llvm-14/bin/clang++-14 Shouldn't that rather be realshell=$(dpkg-realpath --root "$ROOT" "$(dirname "$line")")/$(basename "$line") Andreas
Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye
On 09/05/2023 16.55, Helmut Grohne wrote: Control: forcemerge 1033167 -1 Control: affects 1033167 + 9base Hi Andreas, On Tue, May 09, 2023 at 04:39:21PM +0200, Andreas Beckmann wrote: during a test with piuparts I noticed your package leaves modifications in /etc/shells after upgrading from bullseye to bookworm and purging the package. 9base/bullseye called add-shell/remove-shell in its postinst/postrm. 9base/bookworm no longer does that, but it also does not clean up the leftover entries from bullseye in its postinst. 9base/bookworm no longer does, because it now uses dpkg-triggers to perform the cleanup. It actually does clean up its entries. >From the attached log (scroll to the bottom...): 0m45.2s ERROR: FAIL: After purging files have been modified: /etc/shells not owned You should look closer: 0m45.2s DEBUG: Modified(user, group, mode, size, target): /etc/shells expected(root, root, - 100644, 128, None) != found(root, root, - 100644, 140, None) It's a 12 byte difference. That's not 9base's entries. What you see here is "/usr/bin/sh\n". So this is a /usr-merge bug. We already know it. Thus force-merging. No, it's "/usr/bin/rc\n". # cat /usr/share/debianutils/shells.d/plan9 /bin/rc /usr/lib/plan9/bin/rc If I install 9base in an unmerged-/usr sid chroot, I get # /etc/shells: valid login shells /bin/sh /bin/bash /bin/rbash /bin/dash /bin/rc /usr/lib/plan9/bin/rc /usr/lib/plan9/bin/rc who is responsible for the duplicate entry? If I install 9base in a merged-/usr sid chroot, I get # /etc/shells: valid login shells /bin/sh /bin/bash /usr/bin/bash /bin/rbash /usr/bin/rbash /bin/dash /usr/bin/dash /usr/bin/sh /bin/rc /usr/lib/plan9/bin/rc /usr/lib/plan9/bin/rc same duplication ... If I reconfigure usrmerge afterwards, I get # /etc/shells: valid login shells /bin/sh /bin/bash /usr/bin/bash /bin/rbash /usr/bin/rbash /bin/dash /usr/bin/dash /usr/bin/sh /bin/rc /usr/lib/plan9/bin/rc /usr/lib/plan9/bin/rc /usr/bin/rc Now we got the additional /usr/bin/rc entry Andreas
Bug#1037425: linux-kbuild-6.1: please add Breaks against obsolete *-dkms packages
Package: linux-kbuild-6.1 Version: 6.1.27-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, one change in dkms in bookworm is that it actually returns an error when failing to build a module, as a result /etc/kernel/header_postinst.d/dkms may fail and cause linux-headers---.postinst to fail. (Up to bullseye, dkms returned 0 on failure and the failure was only noticable when someone studied the install/upgrade log.) As a consequence, if cruft *-dkms packages are still installed, but fail to build the module for current kernels, this may result in upgrade failures. Therefore please add Breaks against cruft *-dkms packages that may be left over from previous releases to ensure they get removed. I chose linux-kbuild-6.1 for the addition of these Breaks since all linux-headers-* packages depend on that. I'm trying to build a list: Breaks: # in bullseye, not in bookworm: nvidia-tesla-418-kernel-dkms (<< 418.226.00-9~), nvidia-tesla-460-kernel-dkms (<< 460.106.00-9~), # in buster, not in bullseye sl-modem-dkms (<< 2.9.11~20110321-16.0), # in stretch, not in buster blktap-dkms (<< 2.0.93-0.10.0), # in jessie, not in stretch oss4-dkms (<< 4.2-build2020-1~), # in wheezy, not in jessie blcr-dkms (<< 0.8.6~b3-1.0), Maybe there are more, but I haven't seen them, yet. In case this was fixed in sid (but not in bookworm), I've used that version suffixed with '~', otherwise (i.e. not fixed in sid) I've invented a version based on the last version in sid with NMU suffix .0 The typical upgrade failure if one of these obsolete packages is still installed looks like this: ... Setting up linux-headers-6.1.0-9-amd64 (6.1.27-1) ... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.1.0-9-amd64. Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Certificate or key are missing, generating self signed certificate for MOK... openssl not found, can't generate key and certificate. Building module: Cleaning build area... make -j84 KERNELRELEASE=6.1.0-9-amd64 -C /lib/modules/6.1.0-9-amd64/build M=/var/lib/dkms/blcr/0.8.5/build...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-9-amd64 (x86_64) Consult /var/lib/dkms/blcr/0.8.5/build/make.log for more information. dkms autoinstall on 6.1.0-9-amd64/x86_64 failed for blcr(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.1.0-9-amd64 failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.1.0-9-amd64.postinst line 11. dpkg: error processing package linux-headers-6.1.0-9-amd64 (--configure): installed linux-headers-6.1.0-9-amd64 package post-installation script subprocess returned error exit status 1 Setting up gnupg (2.2.40-1.1) ... dpkg: dependency problems prevent configuration of linux-headers-amd64: linux-headers-amd64 depends on linux-headers-6.1.0-9-amd64 (= 6.1.27-1); however: Package linux-headers-6.1.0-9-amd64 is not configured yet. dpkg: error processing package linux-headers-amd64 (--configure): dependency problems - leaving unconfigured Processing triggers for systemd (252.6-1.1~deb12anbe1) ... Processing triggers for debianutils (5.7-0.4) ... Processing triggers for libc-bin (2.36-9) ... Errors were encountered while processing: linux-headers-6.1.0-9-amd64 linux-headers-amd64 while on bullseye the ignored failure looked like this: ... Setting up linux-headers-5.10.0-22-amd64 (5.10.178-3) ... /etc/kernel/header_postinst.d/dkms: Error! Bad return status for module build on kernel: 5.10.0-22-amd64 (x86_64) Consult /var/lib/dkms/blcr/0.8.5/build/make.log for more information. Andreas
Bug#1037339: cpl-plugin-visir-calib: visir-kit-4.3.10*.tar.gz is no longer downloadable
Package: cpl-plugin-visir-calib Version: 4.3.10+dfsg-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: fixed -1 4.3.11+dfsg-1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up cpl-plugin-visir-calib (4.3.10+dfsg-5) ... --2023-06-10 15:07:45-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10.tar.gz Connecting to 10.99.30.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2023-06-10 15:07:45 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2023-06-10 15:07:45-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-1.tar.gz Connecting to 10.99.30.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2023-06-10 15:07:45 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2023-06-10 15:07:45-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-2.tar.gz Connecting to 10.99.30.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2023-06-10 15:07:46 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2023-06-10 15:07:46-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-3.tar.gz Connecting to 10.99.30.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2023-06-10 15:07:46 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2023-06-10 15:07:46-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-4.tar.gz Connecting to 10.99.30.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2023-06-10 15:07:47 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2023-06-10 15:07:47-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-5.tar.gz Connecting to 10.99.30.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2023-06-10 15:07:47 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2023-06-10 15:07:47-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-6.tar.gz Connecting to 10.99.30.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2023-06-10 15:07:48 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2023-06-10 15:07:48-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-7.tar.gz Connecting to 10.99.30.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2023-06-10 15:07:48 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2023-06-10 15:07:48-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-8.tar.gz Connecting to 10.99.30.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2023-06-10 15:07:49 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now --2023-06-10 15:07:49-- ftp://ftp.eso.org/pub/dfs/pipelines/visir/visir-kit-4.3.10-9.tar.gz Connecting to 10.99.30.1:3128... connected. Proxy request sent, awaiting response... 404 Not Found 2023-06-10 15:07:49 ERROR 404: Not Found. gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now dpkg: error processing package cpl-plugin-visir-calib (--configure): installed cpl-plugin-visir-calib package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.31-13+deb11u6) ... Errors were encountered while processing: cpl-plugin-visir-calib cheers, Andreas cpl-plugin-visir-calib_4.3.10+dfsg-5.log.gz Description: application/gzip
Bug#1036033: upgrade-reports: bullseye -> bookworm kernel package upgrade fails when ddcci-dkms package installed
Control: tag -1 - moreinfo + upstream Control: retitle -1 dkms: throws up after digesting an empty "$arch" Control: forwarded -1 https://github.com/dell/dkms/pull/334 to reproduce in a sid chroot: # ln -s /bin/true /usr/bin/rpm # apt-get install dkms linux-headers-amd64 ... # apt-get install dkms-test-dkms ... # apt-get install --reinstall dkms-test-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 8 not upgraded. Need to get 0 B/9484 B of archives. After this operation, 0 B of additional disk space will be used. debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 78, <> line 1.) debconf: falling back to frontend: Readline (Reading database ... 31482 files and directories currently installed.) Preparing to unpack .../dkms-test-dkms_3.0.11-1_all.deb ... Unpacking dkms-test-dkms (3.0.11-1) over (3.0.11-1) ... Setting up dkms-test-dkms (3.0.11-1) ... debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 78.) debconf: falling back to frontend: Readline Removing old dkms_test-1.0 DKMS files... Loading new dkms_test-1.0 DKMS files... Error! DKMS tree already contains: dkms_test-1.0 You cannot add the same module/version combo more than once. dpkg: error processing package dkms-test-dkms (--configure): installed dkms-test-dkms package post-installation script subprocess returned error exit status 3 Errors were encountered while processing: dkms-test-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) # apt-get install --reinstall dkms-test-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 8 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. E: Internal Error, No file name for dkms-test-dkms:amd64 # apt-get remove dkms-test-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: dkms-test-dkms 0 upgraded, 0 newly installed, 1 to remove and 8 not upgraded. 1 not fully installed or removed. After this operation, 22.5 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 31650 files and directories currently installed.) Removing dkms-test-dkms (3.0.11-1) ... # apt-get install dkms-test-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: dkms-test-dkms 0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded. Need to get 0 B/9484 B of archives. After this operation, 22.5 kB of additional disk space will be used. Selecting previously unselected package dkms-test-dkms. (Reading database ... 31643 files and directories currently installed.) Preparing to unpack .../dkms-test-dkms_3.0.11-1_all.deb ... Unpacking dkms-test-dkms (3.0.11-1) ... Setting up dkms-test-dkms (3.0.11-1) ... Removing old dkms_test-1.0 DKMS files... Loading new dkms_test-1.0 DKMS files... Error! DKMS tree already contains: dkms_test-1.0 You cannot add the same module/version combo more than once. dpkg: error processing package dkms-test-dkms (--configure): installed dkms-test-dkms package post-installation script subprocess returned error exit status 3 Errors were encountered while processing: dkms-test-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) In the end I had to clean up with rm -rf /var/lib/dkms/dkms_test to get back to a sane state Andreas
Bug#1036641: gcc-12-base: please bump the Breaks: gnat (<< 12) for smoother upgrades from bullseye
Followup-For: Bug #1036641 Control: tag -1 patch I've been running bullseye->bookworm upgrade tests with the following change applied to src:gcc-12, this had the best results w.r.t. upgrading gnat related packages: --- gcc-12-12.2.0/debian/rules.conf 2023-01-02 14:06:37.0 +0100 +++ gcc-12-12.2.0/debian/rules.conf 2023-05-24 09:42:40.0 +0200 @@ -615,7 +615,7 @@ arch_gnutype_map = $(DEB_TARGET_ARCH)=$(TARGET_ALIAS) endif # cross compiler -BASE_BREAKS := gnat (<< 7) +BASE_BREAKS := gnat (<< 12), gnat-10 (<< 10.3) # these would need proper updates, and are only needed for upgrades ifneq (,$(filter $(distrelease),stretch jessie trusty xenial bionic)) BASE_BREAKS := The Breaks against gnat-10 is versioned in a way that gnat-10/sid stays installable in sid. Andreas
Bug#1036033: upgrade-reports: bullseye -> bookworm kernel package upgrade fails when ddcci-dkms package installed
Control: reassign -1 dkms Control: severity -1 important Hi Tim, thanks for tracking this down and the detailed description. I already have a fix to not use rpm at all on Debian based systems (mainly because it creates an empty unused rpm database), but that was a bit too late for being included in bookworm (right now available in experimental). I'll try to reproduce your issue and make dkms fail with a meaningful error message on empty $arch. Andreas
Bug#1037236: bullseye-pu: package gss/1.0.3-6+deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
libgss3 has a file conflict with libgss0, which may have remained
installed on a system originating from lenny
[ Impact ]
qa tests (piuparts with non-default config) fail
[ Tests ]
the piuparts test that exposed the bug passes with the updated package
[ Risks ]
low, only affects packages not in bullseye
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
(but differently)
[ Changes ]
adding Breaks+Replaces against the obsolete libgss0 package
[ Other info ]
Andreas
diff -Nru gss-1.0.3/debian/changelog gss-1.0.3/debian/changelog
--- gss-1.0.3/debian/changelog 2021-01-09 00:18:27.0 +0100
+++ gss-1.0.3/debian/changelog 2023-06-07 01:45:19.0 +0200
@@ -1,3 +1,10 @@
+gss (1.0.3-6+deb11u) bullseye; urgency=medium
+
+ * Non-maintainer upload.
+ * libgss3: Add Breaks+Replaces: libgss0 (<< 0.1). (Closes: #988172)
+
+ -- Andreas Beckmann Wed, 07 Jun 2023 01:45:19 +0200
+
gss (1.0.3-6) unstable; urgency=low
* Fix arch/indep-only builds.
diff -Nru gss-1.0.3/debian/control gss-1.0.3/debian/control
--- gss-1.0.3/debian/control2021-01-09 00:14:00.0 +0100
+++ gss-1.0.3/debian/control2023-06-07 01:45:19.0 +0200
@@ -50,6 +50,8 @@
Multi-Arch: same
Depends: libshishi-dev (>= 0.0.42), ${misc:Depends}, ${shlibs:Depends}
Suggests: shishi
+Breaks: libgss0 (<< 0.1),
+Replaces: libgss0 (<< 0.1),
Description: Library for Generic Security Services
The GNU Generic Security Service Library (GSSLib) is a free
implementation of the GSS-API security framework. GSSLib uses Shishi
Bug#1037234: Acknowledgement (node-babel7: missing Breaks+Replaces: node-babel-traverse (<< 7))
Control: affects -1 + node-babel-loader Another set of missing B+R is node-babel-generator (<< 7) Preparing to unpack .../170-node-babel7_7.20.15+ds1+~cs214.269.168-3_all.deb ... Unpacking node-babel7 (7.20.15+ds1+~cs214.269.168-3) over (7.12.12+~cs150.141.84-6) ... dpkg: error processing archive /tmp/apt-dpkg-install-OugExu/170-node-babel7_7.20.15+ds1+~cs214.269.168-3_all.deb (--unpack): trying to overwrite '/usr/share/doc/node-babel-generator/README.md', which is also in package node-babel-generator 6.26.0+dfsg-3 (exposed while testing node-babel-loader) Andreas
Bug#1037234: node-babel7: missing Breaks+Replaces: node-babel-traverse (<< 7)
Package: node-babel7 Version: 7.20.15+ds1+~cs214.269.168-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + node-babel-eslint Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster' to 'bullseye' to 'bookworm'. It installed fine in 'buster', and upgraded to 'bullseye' successfully, but then the upgrade to 'bullseye' failed because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces In case the package was not part of an intermediate stable release, the version from the preceding stable release was kept installed. >From the attached log (scroll to the bottom...): Preparing to unpack .../027-node-babel7_7.20.15+ds1+~cs214.269.168-3_all.deb ... Unpacking node-babel7 (7.20.15+ds1+~cs214.269.168-3) over (7.12.12+~cs150.141.84-6) ... dpkg: error processing archive /tmp/apt-dpkg-install-Dv7Dq8/027-node-babel7_7.20.15+ds1+~cs214.269.168-3_all.deb (--unpack): trying to overwrite '/usr/share/doc/node-babel-traverse/README.md', which is also in package node-babel-traverse 6.26.0+dfsg-3 node-babel-traverse (last released as a separate package in buster) survived the upgrade to bullseye without problems, but causes problems during the subsequent upgrade to bookworm. There may be more old packages needing Breaks+Replaces ... (But I have trouble building the package from git locally (gbp report local modifications), so cannot easily test that). You can test that starting with a minimal buster chroot, installing node-babel-eslint, dist-upgrading to bullseye, distupgrading to bookworm (fails with file overwrite errors in node-babel7), installing the fixed node-babel7 package. cheers, Andreas node-babel-eslint_None.log.gz Description: application/gzip
Bug#1009879: pypdf2: CVE-2022-24859: Manipulated inline images can cause Infinite Loop
Hi Markus, you took care of fixing this bug in stretch-lts. Can you look into fixing this in buster-lts, too? Right now buster(-lts) has a lower version than stretch-lts. pypdf2 | 1.26.0-2 | stretch | source pypdf2 | 1.26.0-2 | buster | source pypdf2 | 1.26.0-2+deb9u1 | stretch-security | source pypdf2 | 1.26.0-4 | bullseye | source (for bullseye there is pu request #1029008) Andreas
Bug#1037213: awstats: prompting due to modified conffiles which were not modified by the user: /etc/logrotate.d/httpd-prerotate/awstats
Package: awstats Version: 7.8-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded... This is a violation of policy 10.7.3, see https://www.debian.org/doc/debian-policy/ch-files.html#behavior, which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens." https://wiki.debian.org/DpkgConffileHandling should help with figuring out how to do this properly. In https://lists.debian.org/debian-devel/2009/08/msg00675.html and followups it has been agreed that these bugs are to be filed with severity serious. >From the attached log (scroll to the bottom...): Setting up awstats (7.8-3) ... Configuration file '/etc/logrotate.d/httpd-prerotate/awstats' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** awstats (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package awstats (--configure): end of file on stdin at conffile prompt This was observed on the upgrade path buster -> bullseye -> bookworm It does not show up on either buster -> bullseye or bullseye -> bookworm. There is something fancy happening here: a directory containing a conffile is to be replaced by a conffile. cheers, Andreas awstats_7.8-3.log.gz Description: application/gzip
Bug#1037192: sd: version is lower than in squeeze
Package: sd Version: 0.7.6-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts squeeze had a sd binary package built from (unrelated) src:sd at version 0.74-1 while bookworm has one built from src:rust-sd at version 0.7.6-1 which is lower, violating the archive property of monotonically increasing version numbers. The highest version of src:sd ever seen in the archive seems to be 0.75-1. Andreas
Bug#1037190: dhcpcd: version is lower than in wheezy
Package: dhcpcd Version: 9.4.1-22 Severity: serious User: debian...@lists.debian.org Usertags: piuparts wheezy had a dhcpcd binary package built from src:dhcpcd at version 1:3.2.3-11+deb7u1 while bookworm has one built from src:dhcpcd5 at version 9.4.1-22 which is lower, violating the archive property of monotonically increasing version numbers. Andreas
Bug#1037188: bullseye-pu: package git/2.30.2-1+deb11u3
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Jonathan Nieder
Control: affects -1 + src:git
Control: block 987264 with -1
Control: block 984931 with -1
[ Reason ]
git-el in bullseye is uninstallable in any sensible combination with
emacs/xemacs (it only installs fine in a minimal chroot w/o
--install-recommends).
The package was dropped from sid shortly after the bullseye release,
let's to the same in bullseye.
[ Impact ]
git-el stays uninstallable (noticed by QA tools)
[ Tests ]
once the package is gone, piuparts will no longer test it (and fail)
[ Risks ]
only unused broken code that gets removed
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
remove all packaging bits for git-el, add Breaks to ensure cleanup if
the package is still (partially) installed
[ Other info ]
bullseye needs a cruft removal run to get rid of the no longer built
binary package
Andreas
diff -Nru git-2.30.2/debian/changelog git-2.30.2/debian/changelog
--- git-2.30.2/debian/changelog 2023-02-22 10:51:09.0 +0100
+++ git-2.30.2/debian/changelog 2023-06-07 11:53:11.0 +0200
@@ -1,3 +1,16 @@
+git (1:2.30.2-1+deb11u3) bullseye; urgency=medium
+
+ * Non-maintainer upload.
+ * Backport git-el removal from 1:2.32.0~rc2-1.
+
+ [ Jonathan Nieder ]
+ * remove git-el package (closes: #987264, #984931). Since version
+1:2.18.0~rc2-1, it only contained modules that error out with a
+message pointing to other Emacs packages. Nowadays users can
+use the README.emacs file from the git package for that instead.
+
+ -- Andreas Beckmann Wed, 07 Jun 2023 11:53:11 +0200
+
git (1:2.30.2-1+deb11u2) bullseye-security; urgency=high
* Non-maintainer upload by the Security Team.
diff -Nru git-2.30.2/debian/control git-2.30.2/debian/control
--- git-2.30.2/debian/control 2021-03-10 02:40:56.0 +0100
+++ git-2.30.2/debian/control 2023-06-07 11:52:58.0 +0200
@@ -32,13 +32,14 @@
Pre-Depends: ${misc:Pre-Depends}
Recommends: ca-certificates, patch, less, ssh-client
Suggests: gettext-base, git-daemon-run | git-daemon-sysvinit,
- git-doc, git-el, git-email, git-gui, gitk, gitweb,
+ git-doc, git-email, git-gui, gitk, gitweb,
git-cvs, git-mediawiki, git-svn
Replaces: gitweb (<< 1:1.7.4~rc1),
git-core (<< 1:1.7.0.4-1.)
Breaks: bash-completion (<< 1:1.90-1), gitweb (<< 1:1.7.4~rc1),
dgit (<< 5.1~),
git-buildpackage (<< 0.6.5),
+ git-el (<< 1:2.32.0~rc2-1~),
cogito (<= 0.18.2+),
openssh-client (<< 1:6.8),
stgit (<< 0.15), stgit-contrib (<< 0.15), gitpkg (<< 0.15),
@@ -273,28 +274,6 @@
.
This package provides the gitk program, a tcl/tk revision tree visualizer.
-Package: git-el
-Architecture: all
-Multi-Arch: foreign
-Depends: ${misc:Depends}, git (>= 1:1.7.4.1-2~), emacs | emacsen
-Recommends: elpa-magit
-Replaces: git (<< 1:1.7.4.1-2~)
-Breaks: emacsen-common (<< 3.0.0~), git (<< 1:1.7.4.1-2~)
-Description: fast, scalable, distributed revision control system (emacs
support)
- Git is popular version control system designed to handle very large
- projects with speed and efficiency; it is used for many high profile
- open source projects, most notably the Linux kernel.
- .
- Git falls in the category of distributed source code management tools.
- Every Git working directory is a full-fledged repository with full
- revision tracking capabilities, not dependent on network access or a
- central server.
- .
- This transitional package provides two modules that previously could be
- used for integration with Emacs: git.el and git-blame.el. Now the
- modules print an error message with instructions that users can use to
- migrate to Emacs's VC-mode backend for Git or Magit.
-
Package: gitweb
Architecture: all
Multi-Arch: foreign
@@ -327,7 +306,7 @@
Architecture: all
Multi-Arch: foreign
Depends: ${misc:Depends}, git (>> ${source:Upstream-Version}), git (<<
${source:Upstream-Version}-.),
- git-doc, git-el, git-cvs, git-mediawiki, git-svn,
+ git-doc, git-cvs, git-mediawiki, git-svn,
git-email, git-gui, gitk, gitweb
Suggests: git-daemon-run | git-daemon-sysvinit
Description: fast, scalable, distributed revision control system (all
subpackages)
diff -Nru git-2.30.2/debian/git-el.emacsen-install
git-2.30.2/debian/git-el.emacsen-install
--- git-2.30.2/debian/git-el.emacsen-install2021-03-10 02:40:56.0
+0100
+++ git-2.30.2/debian/git-el.emacsen-install1970-01-01 01:00:00.0
+0100
@@ -1,27 +0,0 @@
-#!/bin/sh
-# Based on /usr/share/doc/emacsen-common/sample-package-install-foo.gz.
-#
-# Unlike the example, we place symlinks to the elisp source alongside
-# the compiled bytecode, so the .el sou
Bug#1037187: bullseye-pu: package libprelude/5.2.0-3+deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
Control: block 996878 with -1
Control: affects -1 + src:libprelude
Control: tag 996878 patch pending
[ Reason ]
'import prelude' fails in python3 due to some missing symbol, rendering
python3-prelude useless.
[ Impact ]
'import prelude' will not work, breaking some packages depending on that
[ Tests ]
manual 'import prelude' with the fixed package in bullseye worked
added superficial autopkgtest testing the import
[ Risks ]
Low. The patch cannot make the unusable pyton module worse.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
only backported python module fixes from sid
[ Other info ]
Andreas
diff -Nru libprelude-5.2.0/debian/changelog libprelude-5.2.0/debian/changelog
--- libprelude-5.2.0/debian/changelog 2020-11-26 19:53:39.0 +0100
+++ libprelude-5.2.0/debian/changelog 2023-06-07 12:52:40.0 +0200
@@ -1,3 +1,17 @@
+libprelude (5.2.0-3+deb11u1) bullseye; urgency=medium
+
+ * Non-maintainer upload.
+ * Backport Python module fixes from 5.2.0-4/5.2.0-5.
+
+ [ Thomas Andrejak ]
+ * d.patches: Add new patch 025-Fix-PyIOBase_Type.patch
+- Fix PyIOBase_Type for Python 3.10 compatibility
+ * d.patches: Update 025-Fix-PyIOBase_Type.patch because swig is not
+executed (Closes: #996878)
+ * d.tests: Add test to valid that we can load prelude as a python module
+
+ -- Andreas Beckmann Wed, 07 Jun 2023 12:52:40 +0200
+
libprelude (5.2.0-3) unstable; urgency=medium
* d.patches: Add new patch
diff -Nru libprelude-5.2.0/debian/patches/025-Fix-PyIOBase_Type.patch
libprelude-5.2.0/debian/patches/025-Fix-PyIOBase_Type.patch
--- libprelude-5.2.0/debian/patches/025-Fix-PyIOBase_Type.patch 1970-01-01
01:00:00.0 +0100
+++ libprelude-5.2.0/debian/patches/025-Fix-PyIOBase_Type.patch 2023-06-07
12:52:40.0 +0200
@@ -0,0 +1,170 @@
+Description: Fix PyIOBase_Type for Python 3.10 compatibility
+Author: Thomas Andrejak
+Last-Update: 2021-08-13
+Forwarded: yes, privately
+
+--- libprelude-5.2.0/bindings/python/libpreludecpp-python.i2020-09-09
16:30:32.51000 +0200
libprelude-5.2.0/bindings/python/libpreludecpp-python.i2021-08-13
23:20:11.672221930 +0200
+@@ -163,6 +163,26 @@
+ $1 = _cb_python_log;
+ };
+
++%{
++static PyObject *PyIOBase_TypeObj;
++
++static int init_file_emulator(void)
++{
++PyObject *io = PyImport_ImportModule("_io");
++if (io == NULL)
++return -1;
++PyIOBase_TypeObj = PyObject_GetAttrString(io, "_IOBase");
++if (PyIOBase_TypeObj == NULL)
++return -1;
++return 0;
++}
++%}
++
++%init %{
++if (init_file_emulator() < 0) {
++return NULL;
++}
++%}
+
+ /* tell swig not to cast void * value */
+ %typemap(in) void *nocast_file_p %{
+@@ -172,8 +192,7 @@
+
+ }
+ #else
+-extern PyTypeObject PyIOBase_Type;
+-if ( ! PyObject_IsInstance((PyObject *) $input, (PyObject *)
_Type) ) {
++if ( ! PyObject_IsInstance((PyObject *) $input, PyIOBase_TypeObj) ) {
+ SWIG_exception_fail(SWIG_RuntimeError, "Argument is not a
file object");
+ }
+ #endif
+@@ -186,8 +205,7 @@
+ #if PY_VERSION_HEX < 0x0300
+ $1 = PyFile_Check((PyObject *) $input);
+ #else
+-extern PyTypeObject PyIOBase_Type;
+-$1 = PyObject_IsInstance((PyObject *) $input, (PyObject *)
_Type);
++$1 = PyObject_IsInstance((PyObject *) $input, PyIOBase_TypeObj);
+ #endif
+ %}
+
+--- libprelude-5.2.0/bindings/python/_prelude.cxx
libprelude-5.2.0/bindings/python/_prelude.cxx
+@@ -2761,7 +2761,7 @@ SwigPyBuiltin_FunpackSetterClosure (PyObject *obj,
PyObject *val, void *closure)
+
+ SWIGINTERN void
+ SwigPyStaticVar_dealloc(PyDescrObject *descr) {
+- PyObject_GC_UnTrack(descr);
++ PyObject_GC_UnTrack(descr);
+ Py_XDECREF(PyDescr_TYPE(descr));
+ Py_XDECREF(PyDescr_NAME(descr));
+ PyObject_GC_Del(descr);
+@@ -4176,6 +4176,20 @@ static ssize_t _cb_python_read(prelude_io_t *fd, void
*buf, size_t size)
+ }
+
+
++static PyObject *PyIOBase_TypeObj;
++
++static int init_file_emulator(void)
++{
++PyObject *io = PyImport_ImportModule("_io");
++if (io == NULL)
++return -1;
++PyIOBase_TypeObj = PyObject_GetAttrString(io, "_IOBase");
++if (PyIOBase_TypeObj == NULL)
++return -1;
++return 0;
++}
++
++
+ void python2_return_unicode(int enabled)
+ {
+ _PYTHON2_RETURN_UNICODE = enabled;
+@@ -5291,13 +5305,19 @@ namespace swig
+ return const_reference(_seq, n);
+ }
+
+-bool check() const
++bool check(bool set_err = true) const
+ {
+ Py_ssize_t s = size();
+ for (Py_ssize_t i = 0; i < s; ++i) {
+ swig::SwigVar_PyObject i
Bug#1037182: bullseye-pu: package bmake/20200710-14+deb11u1
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
[ Reason ]
There is a directory vs. symlink conflict between bsdowl (buster, not in
bullseye) and bmake (buster), causing bsdowl files to and up in a
location behind a symlink from bmake.
bsdowl has been fixed in bookworm and sid, but that happened to late for
bullseye (was already autorm'ed, not reintroducible).
With the Conflicts against the unfixed bsdowl version added to bmake,
the old bsdowl package from buster gets removed on systems upgraded to
bullseye. If someone really need it, I can provide a backport of the
fixed bsdowl from bookworm in bullseye-backports.
[ Impact ]
QA tools warn about files installed over a directory symlink, maybe
silently overwriting other packages files.
[ Tests ]
manual piuparts tests
buster -> bullseye + fix
buster -> bullseye -> bullseye + fix
no longer fail with
ERROR: installs objects over existing directory symlinks:
/usr/share/mk/bps.autoconf.mk (bsdowl) !=
/usr/share/bmake/mk-bmake/bps.autoconf.mk (?)
/usr/share/mk -> bmake/mk-bmake
...
[ Risks ]
Low, only affects packages not part of bullseye.
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
- bsdowl ships the files in the new canonical location
- bmake verifies that no other package messes up its symlinks
[ Changes ]
add Conflict against unfixed bsdowl versions, i.e. the version from
buster that may have survived the upgrade to bullseye since bsdowl is
not part of bullseye.
[ Other info ]
n/a
Andreas
diff -Nru bmake-20200710/debian/changelog bmake-20200710/debian/changelog
--- bmake-20200710/debian/changelog 2021-04-02 12:53:47.0 +0200
+++ bmake-20200710/debian/changelog 2023-06-07 09:48:17.0 +0200
@@ -1,3 +1,11 @@
+bmake (20200710-14+deb11u1) bullseye; urgency=medium
+
+ * Non-maintainer upload.
+ * Add Conflicts: bsdowl (<< 2.2.2-1.2~) for directory vs. symlink conflict.
+(Closes: #985347)
+
+ -- Andreas Beckmann Wed, 07 Jun 2023 09:48:17 +0200
+
bmake (20200710-14) unstable; urgency=medium
* Remove the bsd.*.mk autodetection now that we actually ship symlinks.
diff -Nru bmake-20200710/debian/control bmake-20200710/debian/control
--- bmake-20200710/debian/control 2021-04-02 12:53:47.0 +0200
+++ bmake-20200710/debian/control 2023-06-07 09:48:17.0 +0200
@@ -13,6 +13,7 @@
Multi-Arch: foreign
Replaces: pmake
Provides: pmake
+Conflicts: bsdowl (<< 2.2.2-1.2~)
Breaks: pmake (<< 20200710-2)
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: NetBSD make
Bug#1037172: unixodbc-common,odbcinst: missing Breaks+Replaces: odbcinst1debian1
Package: unixodbc-common,odbcinst Version: 2.3.11-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + libsqliteodbc Hi, during a test with piuparts I noticed your package fails to upgrade from 'lenny' to 'squeeze' to 'wheezy' to 'jessie' to 'stretch' to 'buster' to 'bullseye' to 'bookworm'. It installed fine in 'lenny', and upgraded to 'squeeze', 'wheezy', 'jessie', 'stretch', 'buster', and 'bullseye' successfully, but then the upgrade to 'bookworm' failed. In case the package was not part of an intermediate stable release, the version from the preceding stable release was kept installed. >From the attached log (scroll to the bottom...): ... Selecting previously unselected package unixodbc-common. Preparing to unpack .../22-unixodbc-common_2.3.11-2_all.deb ... Unpacking unixodbc-common (2.3.11-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-JsWDst/22-unixodbc-common_2.3.11-2_all.deb (--unpack): trying to overwrite '/etc/odbc.ini', which is also in package odbcinst1debian1 2.2.11-16 ... Selecting previously unselected package odbcinst. Preparing to unpack .../25-odbcinst_2.3.11-2_amd64.deb ... Unpacking odbcinst (2.3.11-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-JsWDst/25-odbcinst_2.3.11-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/odbcinst', which is also in package odbcinst1debian1 2.2.11-16 ... Errors were encountered while processing: /tmp/apt-dpkg-install-JsWDst/22-unixodbc-common_2.3.11-2_all.deb /tmp/apt-dpkg-install-JsWDst/25-odbcinst_2.3.11-2_amd64.deb The mentioned Breaks+Replaces may have been there in the past, but on some upgrade paths originating in lenny the obsolete packages may have survived without being affected by B+R so far. (In the concrete case, libsqliteodbc/lenny had a dependency on odbcinst1debian1, libsqliteodbc/bookworm has a dependency on odbcinst while in all releases inbetween there was no pdenedency on an *odbc* package at all.) cheers, Andreas libsqliteodbc_0.9998-3+b1.log.gz Description: application/gzip
Bug#1037147: gclcvs: fails to install on i386: Unrecoverable error: frame stack overflow.
Package: gclcvs Version: 2.7.0-101 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: close -1 2.7.0-101+rm Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up gclcvs (2.7.0-101) ... Aborted (core dumped) Aborted (core dumped) gclcvs.sh Uninstalling clc image and purging object cache ... rm: cannot remove `Unrecoverable': Is a directory rm: cannot remove `error:': Is a directory rm: cannot remove `frame': Is a directory rm: cannot remove `stack': Is a directory rm: cannot remove `overflow.': Is a directory gclcvs.sh Installing clc as Unrecoverable error: frame stack overflow. ... basename: extra operand `frame' Try `basename --help' for more information. Unrecoverable error: frame stack overflow. Aborted (core dumped) Error building send-clc-command dpkg: error processing gclcvs (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: gclcvs configured to not write apport reports E: Sub-process /usr/bin/dpkg returned an error code (1) After injecting set -x into gclcvs.postinst: Setting up gclcvs (2.7.0-101) ... + CONFIGFILE=/etc/default/gclcvs + set -e + . /usr/share/debconf/confmodule + [ ! ] + PERL_DL_NONLAZY=1 + export PERL_DL_NONLAZY + [ ] + exec /usr/share/debconf/frontend /var/lib/dpkg/info/gclcvs.postinst configure + CONFIGFILE=/etc/default/gclcvs + set -e + . /usr/share/debconf/confmodule + [ ! 1 ] + [ -z ] + exec + [ ] + exec + DEBCONF_REDIR=1 + export DEBCONF_REDIR + [ configure = configure ] + [ ! -e /etc/default/gclcvs ] + db_get gclcvs/default_gcl_ansi + _db_cmd GET gclcvs/default_gcl_ansi + IFS= printf %s\n GET gclcvs/default_gcl_ansi + IFS= read -r _db_internal_line + RET= + return 0 + [ = true ] + DEFAULT_GCL_ANSI= + db_get gclcvs/default_gcl_prof + _db_cmd GET gclcvs/default_gcl_prof + IFS= printf %s\n GET gclcvs/default_gcl_prof + IFS= read -r _db_internal_line + RET= + return 0 + [ = true ] + DEFAULT_GCL_PROF= + cp -a -f /etc/default/gclcvs /etc/default/gclcvs.tmp + test -z + test -z + sed -e s/^ *DEFAULT_GCL_ANSI=.*/DEFAULT_GCL_ANSI=""/ -e s/^ *DEFAULT_GCL_PROF=.*/DEFAULT_GCL_PROF=""/ + mv -f /etc/default/gclcvs.tmp /etc/default/gclcvs + [ -e /usr/lib/common-lisp/bin/gclcvs.sh ] + register-common-lisp-implementation gclcvs Aborted (core dumped) Aborted (core dumped) gclcvs.sh Uninstalling clc image and purging object cache ... rm: cannot remove `Unrecoverable': Is a directory rm: cannot remove `error:': Is a directory rm: cannot remove `frame': Is a directory rm: cannot remove `stack': Is a directory rm: cannot remove `overflow.': Is a directory gclcvs.sh Installing clc as Unrecoverable error: frame stack overflow. ... basename: extra operand `frame' Try `basename --help' for more information. Unrecoverable error: frame stack overflow. Aborted (core dumped) Error building send-clc-command dpkg: error processing gclcvs (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: gclcvs cheers, Andreas gclcvs_2.7.0-101.log.gz Description: application/gzip
Bug#1037140: ia32-libs-gtk: uninstallable in wheezy-elts
Package: ia32-libs-gtk Version: 1:0.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: close -1 1:0.1+rm Hi, during a test with piuparts I noticed your package failed to install in wheezy-elts: The following packages have unmet dependencies: ia32-libs-gtk : Depends: ia32-libs-i386 Depends: ia32-libs-gtk-i386 In the end it seems to boil down to an unsatisfiable dependency on python:i386. cheers, Andreas
Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed
On 04/06/2023 07.03, Otto Kekäläinen wrote: What do you Andreas suggest we do now? I'd suggest uploading it to experimental immediately (for NEW processing) and filing a pre-approval bug and let the release team decide what to do. This fix will probably be delayed to the first point release. Should there be something about this issue in the release notes? Andreas
Bug#1037068: sysrepo: world-writable /etc/sysrepo/* after upgrade from 1.4.70-4 in bullseye
Package: sysrepo Version: 2.0.53-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package has world-writable configutation files after upgrading from 1.4.70-4 in bullseye to 2.0.53-6 in sid. >From the attached log (scroll to the bottom...): ERROR: BAD PERMISSIONS drwxrwxrwx 4 root root 100 Jun 2 14:28 /etc/sysrepo drwxrwxrwx 3 root root 240 Jun 2 14:28 /etc/sysrepo/data -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/ietf-datastores.startup -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/ietf-netconf-notifications.startup -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/ietf-netconf-with-defaults.startup -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/ietf-netconf.startup -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/ietf-origin.startup -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/ietf-yang-library.startup drwxrwxrwx 2 root root 40 Jun 2 14:28 /etc/sysrepo/data/notif -rw-rw-rw- 1 root root 388 Jun 2 14:28 /etc/sysrepo/data/sysrepo.startup -rw-rw-rw- 1 root root 7 Jun 2 14:28 /etc/sysrepo/data/yang.startup -rw-rw-rw- 1 root root 0 Jun 2 14:28 /etc/sysrepo/sr_main_lock drwxrwxrwx 2 root root 180 Jun 2 14:28 /etc/sysrepo/yang cheers, Andreas sysrepo_2.0.53-6+b3.log.gz Description: application/gzip
Bug#1037067: libocct-data-exchange-dev,libocct-foundation-dev: both ship /usr/lib/x86_64-linux-gnu/libTKXDE.so
Package: libocct-data-exchange-dev,libocct-foundation-dev Version: 7.7.1+dfsg1-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../125-libocct-data-exchange-dev_7.7.1+dfsg1-1~exp1_amd64.deb ... Unpacking libocct-data-exchange-dev:amd64 (7.7.1+dfsg1-1~exp1) ... dpkg: error processing archive /tmp/apt-dpkg-install-ENsvnk/125-libocct-data-exchange-dev_7.7.1+dfsg1-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libTKXDE.so', which is also in package libocct-foundation-dev:amd64 7.7.1+dfsg1-1~exp1 Errors were encountered while processing: /tmp/apt-dpkg-install-ENsvnk/125-libocct-data-exchange-dev_7.7.1+dfsg1-1~exp1_amd64.deb cheers, Andreas libocct-foundation-dev=7.7.1+dfsg1-1~exp1_libocct-data-exchange-dev=7.7.1+dfsg1-1~exp1.log.gz Description: application/gzip
Bug#1037033: clang-7-dbgsym: missing /usr/share/doc/clang-7-dbgsym -> clang-7
Package: clang-7-dbgsym Version: 1:7.0.1-8~deb9u3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 7.0.1-8~deb9u2 Control: fixed -1 7.0.1-8+deb10u1 Control: close -1 7.0.1-9 Hi, during a test with piuparts I noticed your package misses the /usr/share/doc/clang-7-dbgsym -> clang-7 symlink. >From the attached log (scroll to the bottom...): MISSING COPYRIGHT FILE: /usr/share/doc/clang-7-dbgsym/copyright # ls -lad /usr/share/doc/clang-7-dbgsym ls: cannot access '/usr/share/doc/clang-7-dbgsym': No such file or directory # ls -la /usr/share/doc/clang-7-dbgsym/ ls: cannot access '/usr/share/doc/clang-7-dbgsym/': No such file or directory cheers, Andreas clang-7-dbgsym_1:7.0.1-8~deb9u3.log.gz Description: application/gzip
Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed
Control: tag -1 patch
On 01/06/2023 12.31, Andreas Beckmann wrote:
That worked for me for zoph, but a new failure occurred in tt-rss.
I'm now trying a transitional mariadb-server-10.5 package which seems to
work for both these cases. Will do a complete set of piuparts upgrade
tests for all upgrade paths involving mariadb-server-10.5
First round of tests was successful, i.e. no new regressions so far.
(tests with apt-get upgrade && apt-get full-upgrade or
--install-recommends are still running)
I attach the mariadb-server-10.5 package I tested with, it is missing
adjustments of the description and a useful commit message.
Can you try that in your salsa setup?
AndreasFrom dab6d5731b4ca771f45852e825c906330417a97c Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Thu, 1 Jun 2023 11:39:59 +0200
Subject: [PATCH] add transitional mariadb-server-10.5 package
---
debian/control | 24 ++--
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git a/debian/control b/debian/control
index 6a35515d970..48328809812 100644
--- a/debian/control
+++ b/debian/control
@@ -293,7 +293,7 @@ Breaks: mariadb-client-10.0,
mariadb-server-10.2,
mariadb-server-10.3,
mariadb-server-10.4,
-mariadb-server-10.5,
+mariadb-server-10.5 (<< 1:10.11),
mariadb-server-10.6,
mysql-client-5.5,
mysql-client-5.6,
@@ -327,7 +327,7 @@ Replaces: mariadb-client-10.0,
mariadb-server-10.2,
mariadb-server-10.3,
mariadb-server-10.4,
- mariadb-server-10.5,
+ mariadb-server-10.5 (<< 1:10.11),
mariadb-server-10.6,
mysql-client-5.5,
mysql-client-5.6,
@@ -372,7 +372,7 @@ Breaks: mariadb-client-10.1,
mariadb-server-10.2,
mariadb-server-10.3,
mariadb-server-10.4,
-mariadb-server-10.5,
+mariadb-server-10.5 (<< 1:10.11),
mariadb-server-10.6,
mariadb-server-core-10.0,
mariadb-server-core-10.1,
@@ -400,7 +400,7 @@ Replaces: mariadb-client-10.1,
mariadb-server-10.2,
mariadb-server-10.3,
mariadb-server-10.4,
- mariadb-server-10.5,
+ mariadb-server-10.5 (<< 1:10.11),
mariadb-server-10.6,
mariadb-server-core-10.0,
mariadb-server-core-10.1,
@@ -484,7 +484,7 @@ Breaks: cqrlog (<< 1.9.0-5~),
mariadb-server-10.2,
mariadb-server-10.3,
mariadb-server-10.4,
-mariadb-server-10.5,
+mariadb-server-10.5 (<< 1:10.11),
mariadb-server-10.6,
mariadb-server-5.5,
mariadb-tokudb-engine-10.0,
@@ -506,7 +506,7 @@ Replaces: handlersocket-mysql-5.5,
mariadb-server-10.2,
mariadb-server-10.3,
mariadb-server-10.4,
- mariadb-server-10.5,
+ mariadb-server-10.5 (<< 1:10.11),
mariadb-server-10.6,
mariadb-server-5.5,
mariadb-tokudb-engine-10.0,
@@ -532,6 +532,18 @@ Description: MariaDB database server binaries
.
This package includes the server binaries.
+Package: mariadb-server-10.5
+Architecture: any
+Depends: mariadb-server (>= 1:10.11),
+ ${shlibs:Depends}
+Description: MariaDB database server binaries
+ MariaDB is a fast, stable and true multi-user, multi-threaded SQL database
+ server. SQL (Structured Query Language) is the most popular database query
+ language in the world. The main goals of MariaDB are speed, robustness and
+ ease of use.
+ .
+ This package includes the server binaries.
+
Package: mariadb-backup
Architecture: any
Breaks: mariadb-backup-10.1,
--
2.20.1
Bug#1035979: redmine-plugin-pretend: fails to install: rake aborted! LoadError: cannot load such file -- redmine_pretend
On 01/06/2023 14.16, Paul Gevers wrote: On Fri, 12 May 2023 09:16:32 +0200 Andreas Beckmann wrote: Package: redmine-plugin-pretend during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. If I look at the log, it's redmine itself that fails during installation. @anbe: why did you decide to file against the plugin? I'm guessing here, but if redmine is installed and configured before installing the plugin, everything's fine? redmine alone works fine, but there are two plugins that make redmine "blow up" if they are installed. If redmine is installed first (without errors), the plugin installation still blows redmine up: 0m56.6s DEBUG: Starting command: ['nsenter', '--net=/run/netns/piuparts-netns-13', '--uts=/srv/piuparts/tmp/tmp53VbkN/ns-uts', 'chroot', '/srv/piuparts/tmp/tmp53VbkN/chroot', 'apt-get', '-y', 'install', 'redmine-plugin-pretend=0.0.2+git20130821-5'] 1m2.6s DUMP: Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: redmine-plugin-pretend 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 6132 B of archives. After this operation, 38.9 kB of additional disk space will be used. Get:1 http://ftp.de.debian.org/debian bookworm/main amd64 redmine-plugin-pretend all 0.0.2+git20130821-5 [6132 B] debconf: delaying package configuration, since apt-utils is not installed Fetched 6132 B in 0s (207 kB/s) Selecting previously unselected package redmine-plugin-pretend. (Reading database ... 19234 files and directories currently installed.) Preparing to unpack .../redmine-plugin-pretend_0.0.2+git20130821-5_all.deb ... Unpacking redmine-plugin-pretend (0.0.2+git20130821-5) ... Setting up redmine-plugin-pretend (0.0.2+git20130821-5) ... Processing triggers for redmine (5.0.4-5) ... Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will break this application for all non-root users on this machine. dbconfig-common: flushing administrative password rake aborted! LoadError: cannot load such file -- redmine_pretend /usr/share/rubygems-integration/all/gems/zeitwerk-2.6.1/lib/zeitwerk/kernel.rb:35:in `require' /usr/share/rubygems-integration/all/gems/zeitwerk-2.6.1/lib/zeitwerk/kernel.rb:35:in `require' /usr/share/redmine/plugins/redmine_pretend/init.rb:1:in `' /usr/share/redmine/lib/redmine/plugin_loader.rb:31:in `load' /usr/share/redmine/lib/redmine/plugin_loader.rb:31:in `run_initializer' /usr/share/redmine/lib/redmine/plugin_loader.rb:108:in `each' /usr/share/redmine/lib/redmine/plugin_loader.rb:108:in `block in load' /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:427:in `instance_exec' /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:427:in `block in make_lambda' /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:198:in `block (2 levels) in halting' /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:604:in `block (2 levels) in default_terminator' /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:603:in `catch' /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:603:in `block in default_terminator' /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:199:in `block in halting' /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:512:in `block in invoke_before' /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:512:in `each' /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:512:in `invoke_before' /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:105:in `run_callbacks' /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/reloader.rb:88:in `prepare!' /usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/application/finisher.rb:124:in `block in ' /usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/initializable.rb:32:in `instance_exec' /usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/initializable.rb:32:in `run' /usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/initializable.rb:61:in `block in run_initializers' /usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/initializable.rb:60:in `run_initializers' /usr/share/rubygems-integration/all/gems/railties-6.1.7.3/lib/rails/application.rb:391:in `
Bug#1035949: mariadb: upgrade issue: mariadb-server-10.5 fails to stop after all other -10.5 packages were removed
On 26/05/2023 19.16, Otto Kekäläinen wrote:
I filed now
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/47
as an exploration to fix this issue.
That worked for me for zoph, but a new failure occurred in tt-rss.
I'm now trying a transitional mariadb-server-10.5 package which seems to
work for both these cases. Will do a complete set of piuparts upgrade
tests for all upgrade paths involving mariadb-server-10.5
If we don't fix this in 10.11 the alternative would be to patch 10.5
and 10.3 to simply never fail on missing mariadb-client-10.3/5
package. I already did
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/merge_requests/14
to make the problem have a proper error message users.
Proper error message is good. ;-)
Ignoring the failure not. :-(
While creating the transitional package I came across some
inconsistencies between Conflicts/Breaks/Replaces. I'm not sure whether
they are intentional, but I'm doing my tests with the three attached
patches applied. They didn't make a difference on their own.
AndreasFrom 9c7c48a0d6428535596665590c2e87b4a477abd4 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Thu, 1 Jun 2023 09:53:25 +0200
Subject: [PATCH 1/3] drop redundant Breaks+Conflicts
---
debian/control | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/debian/control b/debian/control
index d8b99443551..6f3aff563e3 100644
--- a/debian/control
+++ b/debian/control
@@ -88,10 +88,7 @@ Conflicts: libmariadb-client-lgpl-dev-compat,
libmysqlclient-dev
Provides: libmariadb-client-lgpl-dev-compat,
libmariadbclient-dev-compat
-Breaks: libmariadb-client-lgpl-dev-compat,
-libmariadbclient-dev (<< 1:10.3),
-libmariadbclient-dev-compat,
-libmysqlclient-dev
+Breaks: libmariadbclient-dev (<< 1:10.3)
Replaces: libmariadb-client-lgpl-dev-compat,
libmariadbclient-dev (<< 1:10.3),
libmariadbclient-dev-compat,
--
2.20.1
From c8fd52f3bbe17d888981652823a3e0ac19c9a657 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Thu, 1 Jun 2023 09:54:46 +0200
Subject: [PATCH 2/3] tighten server plugin dependencies
---
debian/control | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/debian/control b/debian/control
index 6f3aff563e3..ade3b98e256 100644
--- a/debian/control
+++ b/debian/control
@@ -652,7 +652,7 @@ Description: Spider storage engine for MariaDB
Package: mariadb-plugin-gssapi-server
Architecture: any
Depends: libgssapi-krb5-2,
- mariadb-server,
+ mariadb-server (= ${server:Version}),
${misc:Depends},
${shlibs:Depends}
Breaks: mariadb-gssapi-server-10.1,
@@ -696,7 +696,7 @@ Description: CrackLib Password Validation Plugin for MariaDB
Package: mariadb-plugin-hashicorp-key-management
Architecture: any
Depends: libcurl4,
- mariadb-server,
+ mariadb-server (= ${server:Version}),
${misc:Depends},
${shlibs:Depends}
Description: Hashicorp Key Management plugin for MariaDB
@@ -705,7 +705,7 @@ Description: Hashicorp Key Management plugin for MariaDB
Package: mariadb-plugin-provider-bzip2
Architecture: any
-Depends: mariadb-server (>= 1:10.11.1-1),
+Depends: mariadb-server (= ${server:Version}),
${misc:Depends},
${shlibs:Depends}
Description: BZip2 compression support in the server and storage engines
@@ -719,7 +719,7 @@ Description: BZip2 compression support in the server and storage engines
Package: mariadb-plugin-provider-lz4
Architecture: any
-Depends: mariadb-server (>= 1:10.11.1-1),
+Depends: mariadb-server (= ${server:Version}),
${misc:Depends},
${shlibs:Depends}
Description: LZ4 compression support in the server and storage engines
@@ -733,7 +733,7 @@ Description: LZ4 compression support in the server and storage engines
Package: mariadb-plugin-provider-lzma
Architecture: any
-Depends: mariadb-server (>= 1:10.11.1-1),
+Depends: mariadb-server (= ${server:Version}),
${misc:Depends},
${shlibs:Depends}
Description: LZMA compression support in the server and storage engines
@@ -747,7 +747,7 @@ Description: LZMA compression support in the server and storage engines
Package: mariadb-plugin-provider-lzo
Architecture: any
-Depends: mariadb-server (>= 1:10.11.1-1),
+Depends: mariadb-server (= ${server:Version}),
${misc:Depends},
${shlibs:Depends}
Description: LZO compression support in the server and storage engines
@@ -761,7 +761,7 @@ Description: LZO compression support in the server and storage engines
Package: mariadb-plugin-provider-snappy
Architecture: any
-Depends: mariadb-server (>= 1:10.11.1-1),
+Depends: mariadb-server (= ${server:Version}),
${misc:Depends},
${shlibs:Depends}
Description: Snappy compression support in the server and storage engines
--
2.20.1
From 07f654ffce74f75380065d447f76766d36cd06ea Mon S
Bug#1036992: r8168-dkms: Adding more information
[please keep the bug in Cc:] On 01/06/2023 04.06, Mohammed Anas wrote: Sorry to not mention it, But after purging the new driver , i did reboot the system. But the old driver was still not loaded. Weird. How did you purge the new driver? Please send the output of the following command: find /lib/modules /usr/src /var/lib/dkms -name '*r8168*' Andreas
Bug#1036992: r8168-dkms: Adding more information
On 31/05/2023 20.52, MA wrote: * What was the outcome of this action? ==> No expected changes and the driver for my Ethernet still shows as r8168 in lspci -k command * What outcome did you expect instead?==> i expected the installed driver to be removed and reload the kernel built in driver(which is currently nowhere to be found) which will happen upon reboot Replacing the network driver would require stopping the network (and all services using the network), unloading the kernel driver, loading the new kernel driver, bringing up the network again. That works best if done by a reboot. Andreas
Bug#1036987: libeccodes-data: fails to upgrade from sid: unable to install new version of '/usr/share/eccodes/definitions/bufr/tables/0/local/8/78/1/codetables/11199.table': No such file or directory
Package: libeccodes-data Version: 2.30.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails. >From the attached log (scroll to the bottom...): Preparing to unpack .../libeccodes-data_2.30.0-1_all.deb ... Unpacking libeccodes-data (2.30.0-1) over (2.28.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libeccodes-data_2.30.0-1_all.deb (--unpack): unable to install new version of '/usr/share/eccodes/definitions/bufr/tables/0/local/8/78/1/codetables/11199.table': No such file or directory Errors were encountered while processing: /var/cache/apt/archives/libeccodes-data_2.30.0-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This looks like there are some missing dpkg-maintscript-helper symlink_to_dir calls, since e.g. in sid there is /usr/share/eccodes/definitions/bufr/tables/0/local/8/78/1 -> 0 a symlink while in experimental it is directory containing files. While unpacking, dpkg seems to write a file over a dangling directory symlink, causing the above error. Quoting from the unhandled_symlink_to_directory_conversion template: """ an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. """ You seem to fall into the "anything interesting may happen" category, it's the first time that I've seen such an error while caring for piuparts. cheers, Andreas libeccodes-data_2.30.0-1.log.gz Description: application/gzip
Bug#1036986: libboost-json1.81-dev: missing Depends: libboost-json1.81.0 (= ${binary:Version})
Package: libboost-json1.81-dev Version: 1.81.0-5 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink: 0m41.1s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/libboost_json.so -> libboost_json.so.1.81.0 (libboost-json1.81-dev:amd64) Please also check the other -dev packages from src:boost1.81, even if I don't see more failures in piuparts. cheers, Andreas
Bug#1036967: fig2dev: insufficient Breaks+Replaces against transfig/jessie-elts
On 31/05/2023 14.26, Markus Koschany wrote: Hello Andreas, Neither fig2dev or transfig are supported in jessie-elts anymore. I appreciate the report though. Since Stretch is no longer supported by Debian I believe this issue is no longer actionable by the maintainer. Is fig2dev supported in stretch-elts? stretch-elts would be the natural dist-upgrade target for jessie-elts. Andreas
Bug#1036967: fig2dev: insufficient Breaks+Replaces against transfig/jessie-elts
Package: fig2dev Version: 1:3.2.6a-2+deb9u4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts X-Debbugs-Cc: Markus Koschany Hi, during a test with piuparts I noticed your package fails to upgrade from 'jessie-elts'. It installed fine in 'jessie-elts', then the upgrade to 'stretch-elts' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): ... Selecting previously unselected package fig2dev. Preparing to unpack .../fig2dev_1%3a3.2.6a-2+deb9u4_amd64.deb ... Unpacking fig2dev (1:3.2.6a-2+deb9u4) ... dpkg: error processing archive /var/cache/apt/archives/fig2dev_1%3a3.2.6a-2+deb9u4_amd64.deb (--unpack): trying to overwrite '/usr/bin/fig2dev', which is also in package transfig 1:3.2.6a-2~deb8u1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) .. The upload of a new upstream release (1:3.2.6a-2~deb8u1) of transfig to jessie-elts (ELA-493-1) invalidated the versions in the existing Breaks+Replaces: transfig (<< 1:3.2.6~beta-1~) in fig2dev (1:3.2.6a-2+deb9u4) in stretch, causing the above file overwrite errors on several jessie-elts -> stretch-elts upgrade tests. Ideally the Breaks+Replaces against transfig in fig2dev should be bumped to (<< 1:3.2.6a-2+deb9) in stretch-elts. cheers, Andreas fig2ps.elts.log.gz Description: application/gzip
Bug#1035499: crowdsec-custom-bouncer: fails to install with --install-recommends: open /etc/crowdsec/config.yaml: no such file or directory
On 30/05/2023 23.59, Cyril Brulebois wrote: My question is why that wouldn't show up for crowdsec-firewall-bouncer as well since the logic is essentially the same! (It does a little firewall detection, and there's basically a s/custom/firewall/ for a few filenames, but the cscli part is exactly the same. And they both only have crowdsec listed in Recommends.) You just got lucky in the configuration order: first crowdsec, thereafter crowdsec-firewall-bouncer This heavily depends on apt's serialization of the dependency dag ... installation of some unrelated packaged might influence the outcome. ... Selecting previously unselected package crowdsec. Preparing to unpack .../13-crowdsec_1.4.6-3+b2_i386.deb ... Unpacking crowdsec (1.4.6-3+b2) ... Selecting previously unselected package crowdsec-firewall-bouncer. Preparing to unpack .../14-crowdsec-firewall-bouncer_0.0.25-2+b1_i386.deb ... Unpacking crowdsec-firewall-bouncer (0.0.25-2+b1) ... Setting up libsqlite3-0:i386 (3.40.1-2) ... Setting up libssl3:i386 (3.0.8-1) ... Setting up libjansson4:i386 (2.14-2) ... Setting up libmnl0:i386 (1.0.4-3) ... Setting up libxtables12:i386 (1.8.9-2) ... Setting up netbase (6.4) ... Setting up openssl (3.0.8-1) ... Setting up libbsd0:i386 (0.11.7-2) ... Setting up libedit2:i386 (3.1-20221030-2) ... Setting up libnftnl11:i386 (1.2.4-2) ... Setting up ca-certificates (20230311) ... Updating certificates in /etc/ssl/certs... 140 added, 0 removed; done. Setting up crowdsec (1.4.6-3+b2) ... I: Registering to LAPI (/etc/crowdsec/local_api_credentials.yaml) W: Missing /etc/machine-id, initializing I: Registering to CAPI (/etc/crowdsec/online_api_credentials.yaml) I: Setting up offline hub (see README.Debian) I: Enabling upstream-recommended items, first installation (via symlinks from /etc/crowdsec) I: Enabling WAL for SQLite [fstype=] (see README.Debian) Setting up libnftables1:i386 (1.0.6-2) ... Setting up nftables (1.0.6-2) ... Setting up crowdsec-firewall-bouncer (0.0.25-2+b1) ... I: Configuring nftables [see README.Debian] To adjust the config: editor /etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.local && systemctl restart crowdsec-firewall-bouncer Processing triggers for libc-bin (2.36-9) ... Processing triggers for ca-certificates (20230311) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done.
Bug#1035499: crowdsec-custom-bouncer: fails to install with --install-recommends: open /etc/crowdsec/config.yaml: no such file or directory
On 30/05/2023 21.18, Andreas Beckmann wrote: On 30/05/2023 20.24, Cyril Brulebois wrote: Alright, with RC 4 out of the way, I'm looking at this issue again, and it seems the “sibling package” crowdsec-firewall-bouncer is affected by the exact same issue (not surprisingly). I'm curious as to whether it showed up in those piuparts tests, if you have bug reports yet to be filed, or something else. I have successful test logs from Apr 09 for crowdsec-firewall-bouncer, rescheduled them right now, will report later what happened. crowdsec-firewall-bouncer passed the test crowdsec-custom-bouncer always failed in sid (and testing) with --install-recommends, crowdsec-firewall-bouncer always succeeded The difference caused by --install-recommends is * crowdsec (which crowdsec-custom-bouncer Recommends) gets installed * but crowdsec-custom-bouncer gets configured first, i.e. after crowdsec got unpacked but before crowdsec could create the configuration file /etc/crowdsec/config.yaml * crowdsec-custom-bouncer.postinst only checks for cscli which is available after unpacacking Andreas
Bug#1035499: crowdsec-custom-bouncer: fails to install with --install-recommends: open /etc/crowdsec/config.yaml: no such file or directory
On 30/05/2023 20.24, Cyril Brulebois wrote: Alright, with RC 4 out of the way, I'm looking at this issue again, and it seems the “sibling package” crowdsec-firewall-bouncer is affected by the exact same issue (not surprisingly). I'm curious as to whether it showed up in those piuparts tests, if you have bug reports yet to be filed, or something else. I have successful test logs from Apr 09 for crowdsec-firewall-bouncer, rescheduled them right now, will report later what happened. Andreas
Bug#1036950: schleuder: fails to upgrade from 'buster': fails during apt-get upgrade
Package: schleuder Version: 3.6.0-3+deb11u1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster'. It installed fine in 'buster', then the upgrade to 'bullseye' fails. Note that this failure only occurs during a 2-stage upgrade (apt-get upgrade && apt-get distupgrade) in the apt-get upgrade step, while a single-stage upgrade (only apt-get dist-upgrade) works fine. >From the attached log (scroll to the bottom...): Setting up schleuder (3.6.0-3+deb11u1) ... Installing new version of config file /etc/schleuder/list-defaults.yml ... dpkg: error processing package schleuder (--configure): installed schleuder package post-installation script subprocess returned error exit status 1 I tried injecting 'set -x' into the postinst, but the output is not very helpful: Setting up schleuder (3.6.0-3+deb11u1) ... + set -e + id schleuder + chown schleuder /etc/schleuder + chown root:schleuder /etc/schleuder/schleuder.yml /etc/schleuder/list-defaults.yml + chmod 0640 /etc/schleuder/schleuder.yml /etc/schleuder/list-defaults.yml + chmod 0750 /var/lib/schleuder /var/log/schleuder + chown schleuder:schleuder /var/lib/schleuder /var/log/schleuder + [ -z 3.4.0-2+deb10u3 ] + dpkg --compare-versions 3.4.0-2+deb10u3 lt 3.0 + SCHEMA=SCHEMA=/dev/null + runuser -u schleuder -- sh -c SCHEMA=/dev/null schleuder install >/dev/null dpkg: error processing package schleuder (--configure): installed schleuder package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: schleuder Entering the chroot after the failure and runnign runuser -u schleuder -- sh -c 'SCHEMA=/dev/null schleuder install' does not give any output either. My guess is that there is some insufficiently versioned dependency that has not yet been upgraded during 'apt-get upgrade' is required for this comand to succeed. cheers, Andreas schleuder_3.6.0-3+deb11u1.log.gz Description: application/gzip
Bug#1036942: node-babel7: missing Breaks+Replaces: node-babel-code-frame (<< 7)
Package: node-babel7 Version: 7.20.15+ds1+~cs214.269.168-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + node-babel-eslint Hi, during a test with piuparts I noticed your package fails to upgrade from 'buster' to 'bullseye' to 'bookworm'. It installed fine in 'buster', and upgraded to 'bullseye' successfully, but then the upgrade to 'bullseye' failed because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces In case the package was not part of an intermediate stable release, the version from the preceding stable release was kept installed. >From the attached log (scroll to the bottom...): Preparing to unpack .../027-node-babel7_7.20.15+ds1+~cs214.269.168-2_all.deb ... Unpacking node-babel7 (7.20.15+ds1+~cs214.269.168-2) over (7.12.12+~cs150.141.84-6) ... dpkg: error processing archive /tmp/apt-dpkg-install-mHzAfl/027-node-babel7_7.20.15+ds1+~cs214.269.168-2_all.deb (--unpack): trying to overwrite '/usr/share/doc/node-babel-code-frame/README.md', which is also in package node-babel-code-frame 6.26.0+dfsg-3 node-babel-code-frame (last released as a separate package in buster) survived the upgrade to bullseye without problems, but causes problems during the subsequent upgrade to bookworm. cheers, Andreas node-babel-eslint_None.log.gz Description: application/gzip
Bug#1036920: systemd: please ship a placeholder in /usr/lib/modules-load.d/
On 29/05/2023 14.57, Luca Boccassi wrote: Side question first: does systemd evaluate both /usr/lib/modules-load.d/* and /lib/modules-load.d/* ? Otherwise all packages shipping something in /lib/modules-load.d/ are broken on unmerged-/usr because their config snippets are not being taken into account. The correct path since bullseye was /usr/lib/modules-load.d, see: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971282 I read this as these packages have been buggy on unmerged-/usr in bullseye. Why weren't there bugs filed? Anyway, we don't really care about what happens on unmerged installations, as they are no longer supported since Bookworm. Well, there is still limited support, e.g. for buildd usage. But probably (hopefully?) for the last time. Andreas
Bug#1036920: systemd: please ship a placeholder in /usr/lib/modules-load.d/
On 29/05/2023 14.57, Luca Boccassi wrote: Wouldn't the correct workaround be to list /usr/lib/modules-load.d in systemd.dirs so that dpkg leaves it alone? Seems way too late for Bookworm though? for dpkg, /usr/lib/modules-load.d is already owned by systemd, dpkg only accidentally deletes it while removing /lib/modules-load.d That's the reason for adding some placeholder file there, to prevent accidental removal of the (no longer empty) directory. Could be part of the first bookworm point release. Andreas
Bug#1036920: systemd: please ship a placeholder in /usr/lib/modules-load.d/
Package: systemd Version: 252.6-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships an empty directory (/usr/lib/modules-load.d/) which disappears after installation and removal of another package (e.g. multipath-tools) in a merged-/usr setup. This is not a bug in the other package, but an effect of our merged-/usr implementation. Side question first: does systemd evaluate both /usr/lib/modules-load.d/* and /lib/modules-load.d/* ? Otherwise all packages shipping something in /lib/modules-load.d/ are broken on unmerged-/usr because their config snippets are not being taken into account. This is happening to trigger the bug: systemd ships /usr/lib/modules-load.d/ (empty directory) multipath-tools ships /lib/modules-load.d/multipath.conf dpkg doesn't know that /lib/modules-load.d/ and /usr/lib/modules-load.d/ are the same, and therefore removal of multipath-tools causes removal of * /lib/modules-load.d/multipath.conf (OK) * /lib/modules-load.d/ (if it was the last owner of that directory), while it effectively is /usr/lib/modules-load.d/ getting removed When adding a placeholder file, it needs to be something that is ignored by the processing of the .d directory (the pattern could be *.conf, but I might be mistaken here). An alternative to shipping a placeholder file could be shipping /lib/modules-load.d/ as additional empty directory, but I don't know whether this would be allowed w.r.t. merged-/usr. >From the attached log (scroll to the bottom...): 0m39.2s ERROR: FAIL: After purging files have disappeared: /usr/lib/modules-load.d/ owned by: systemd This is not caught by default piuparts tests as there is no test with systemd explicitly installed. I could not reproduce this issue in bullseye (and haven't tried to reproduce it in earlier releases). cheers, Andreas PS: packages shipping files in modules-load.d/ (in sid): # apt-file search /lib/modules-load.d/ aoetools: /usr/lib/modules-load.d/aoetools.conf dlm-controld: /usr/lib/modules-load.d/configfs.conf drbd-utils: /lib/modules-load.d/drbd.conf ecryptfs-utils: /lib/modules-load.d/ecryptfs.conf fwupd: /usr/lib/modules-load.d/fwupd-msr.conf iwd: /usr/lib/modules-load.d/pkcs8.conf libddccontrol0: /usr/lib/modules-load.d/ddccontrol-i2c-dev.conf mbpfan: /lib/modules-load.d/mbpfan.depend.conf multipath-tools: /lib/modules-load.d/multipath.conf open-vm-tools-desktop: /usr/lib/modules-load.d/open-vm-tools-desktop.conf osspd: /lib/modules-load.d/osspd.conf zfsutils-linux: /lib/modules-load.d/zfs.conf systemd-modules-load.d.log.gz Description: application/gzip
Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed
On 28/05/2023 11.58, Jochen Sprickerhof wrote: The point of piuparts is that an upgraded system is different to a newly installed system, i.e. that the e2scrub_reap.service symlink lies in a different directory. Actually the difference is between the minimal bullseye chroot upgraded to bookworm and the bullseye chroot with some packages to be tested installed (here: systemd) and upgraded to bookworm. Ideally, after removing the packages to be tested and their dependencies, the two bookworm chroots should be identical ... Andreas
Bug#1036864: unblock: soapysdr/0.8.1-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: tony mancill
Control: tag -1 + src:soapysdr
Please unblock package soapysdr
[ Reason ]
The libsoapysdr0.7 (bullseye) and libsoapysdr0.8 (bookworm) library
stacks are not co-installable due to a package conflict deep in their
dependency tree. This is sometimes hard for apt to figure out and it
may prefer to keep some obsolete packages installed and hold some
upgradable packages at the bullseye version. This can be hinted into the
right direction (removing the whole obsolete tree, and installing all
the fancy new stuff) by adding some Breaks between the roots of the
dependency trees. The explicit Breaks at the root (which has usually a
sufficiently high score) easily propagates the removal through the whole
tree.
[ Impact ]
incomplete upgrades in some cases
[ Tests ]
Local piuparts bullseye -> bookworm tests using the fixed packages,
testing all upgrade paths that had libsoapysdr0.7 (transitively)
installed in bookworm.
[ Risks ]
the Breaks targets only packages not in bookworm
and that need to get removed on upgrades from bullseye
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
n/a
unblock soapysdr/0.8.1-3
Andreas
diff -Nru soapysdr-0.8.1/debian/changelog soapysdr-0.8.1/debian/changelog
--- soapysdr-0.8.1/debian/changelog 2021-09-07 00:29:41.0 +0200
+++ soapysdr-0.8.1/debian/changelog 2023-05-24 09:35:42.0 +0200
@@ -1,3 +1,11 @@
+soapysdr (0.8.1-3) unstable; urgency=medium
+
+ * Team upload
+ * libsoapysdr0.8: Add Breaks: libsoapysdr0.7 for smoother upgrades from
+bullseye. (Closes: #1036737)
+
+ -- Andreas Beckmann Wed, 24 May 2023 09:35:42 +0200
+
soapysdr (0.8.1-2) unstable; urgency=medium
* Upload to unstable
diff -Nru soapysdr-0.8.1/debian/control soapysdr-0.8.1/debian/control
--- soapysdr-0.8.1/debian/control 2021-08-25 22:17:31.0 +0200
+++ soapysdr-0.8.1/debian/control 2023-05-24 09:35:42.0 +0200
@@ -24,6 +24,7 @@
Multi-Arch: same
Depends: ${shlibs:Depends}, ${misc:Depends}
Recommends: soapysdr0.8-module-all | soapysdr0.8-module
+Breaks: libsoapysdr0.7
Description: software defined radio interface library
SoapySDR is a library providing a common interface to SDR (software
defined radio) hardware. Support for different hardware is added through
Bug#1036860: unblock: jupyter-notebook/6.4.12-2.2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Control: block -1 with 1036850 Control: affects -1 + src:jupyter-notebook Please unblock package jupyter-notebook [ Reason ] This is a followup to the cadabra2 unblock (#1036850) to restore /usr/lib/python3/dist-packages/notebook/static/components/codemirror as a symlink in case cadabra2 was installed first [ Impact ] /usr/lib/python3/dist-packages/notebook/static/components/codemirror being a (nearly) empty directory instead a symlink to a directory tree full of javascript might cripple python3-notebook functionality. [ Tests ] manual upgrade tests starting from the bad installation order [ Risks ] not worse than /usr/lib/python3/dist-packages/notebook/static/components/codemirror being an empty directory [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] unblock jupyter-notebook/6.4.12-2.2 Andreas diff -Nru jupyter-notebook-6.4.12/debian/changelog jupyter-notebook-6.4.12/debian/changelog --- jupyter-notebook-6.4.12/debian/changelog2022-10-15 11:04:20.0 +0200 +++ jupyter-notebook-6.4.12/debian/changelog2023-05-28 01:18:59.0 +0200 @@ -1,3 +1,13 @@ +jupyter-notebook (6.4.12-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * python3-notebook: Add Breaks: cadabra2 (<< 2.4.3.2-1.1~). + * Add python3-notebook.maintscript to restore the +/usr/lib/python3/dist-packages/notebook/static/components/codemirror +symlink in case buggy cadabra2 was installed first. (Closes: #1036021) + + -- Andreas Beckmann Sun, 28 May 2023 01:18:59 +0200 + jupyter-notebook (6.4.12-2.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru jupyter-notebook-6.4.12/debian/control jupyter-notebook-6.4.12/debian/control --- jupyter-notebook-6.4.12/debian/control 2022-10-01 00:58:58.0 +0200 +++ jupyter-notebook-6.4.12/debian/control 2023-05-28 00:58:48.0 +0200 @@ -102,6 +102,7 @@ Recommends: python3-ipykernel, python3-ipywidgets Suggests: python-notebook-doc Breaks: jupyter-nbextension-jupyter-js-widgets (<< 6.0.0-6~) + , cadabra2 (<< 2.4.3.2-1.1~) Description: Jupyter interactive notebook (Python 3) The Jupyter Notebook is a web application that allows you to create and share documents that contain live code, equations, visualizations, and diff -Nru jupyter-notebook-6.4.12/debian/python3-notebook.maintscript jupyter-notebook-6.4.12/debian/python3-notebook.maintscript --- jupyter-notebook-6.4.12/debian/python3-notebook.maintscript 1970-01-01 01:00:00.0 +0100 +++ jupyter-notebook-6.4.12/debian/python3-notebook.maintscript 2023-05-28 01:07:59.0 +0200 @@ -0,0 +1 @@ +dir_to_symlink /usr/lib/python3/dist-packages/notebook/static/components/codemirror ../../../../../../share/javascript/codemirror 6.4.12-2.2~
Bug#1036021: cadabra2,python3-notebook: undeclared file conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror
Followup-For: Bug #1036021 Control: tag -1 patch Here comes the followup patch for python3-notebook to restore the /usr/lib/python3/dist-packages/notebook/static/components/codemirror symlink in case buggy cadabra2 was installed first. 0-day NMU to get this into bookworm. Andreas diff -Nru jupyter-notebook-6.4.12/debian/changelog jupyter-notebook-6.4.12/debian/changelog --- jupyter-notebook-6.4.12/debian/changelog2022-10-15 11:04:20.0 +0200 +++ jupyter-notebook-6.4.12/debian/changelog2023-05-28 01:18:59.0 +0200 @@ -1,3 +1,13 @@ +jupyter-notebook (6.4.12-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * python3-notebook: Add Breaks: cadabra2 (<< 2.4.3.2-1.1~). + * Add python3-notebook.maintscript to restore the +/usr/lib/python3/dist-packages/notebook/static/components/codemirror +symlink in case buggy cadabra2 was installed first. (Closes: #1036021) + + -- Andreas Beckmann Sun, 28 May 2023 01:18:59 +0200 + jupyter-notebook (6.4.12-2.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru jupyter-notebook-6.4.12/debian/control jupyter-notebook-6.4.12/debian/control --- jupyter-notebook-6.4.12/debian/control 2022-10-01 00:58:58.0 +0200 +++ jupyter-notebook-6.4.12/debian/control 2023-05-28 00:58:48.0 +0200 @@ -102,6 +102,7 @@ Recommends: python3-ipykernel, python3-ipywidgets Suggests: python-notebook-doc Breaks: jupyter-nbextension-jupyter-js-widgets (<< 6.0.0-6~) + , cadabra2 (<< 2.4.3.2-1.1~) Description: Jupyter interactive notebook (Python 3) The Jupyter Notebook is a web application that allows you to create and share documents that contain live code, equations, visualizations, and diff -Nru jupyter-notebook-6.4.12/debian/python3-notebook.maintscript jupyter-notebook-6.4.12/debian/python3-notebook.maintscript --- jupyter-notebook-6.4.12/debian/python3-notebook.maintscript 1970-01-01 01:00:00.0 +0100 +++ jupyter-notebook-6.4.12/debian/python3-notebook.maintscript 2023-05-28 01:07:59.0 +0200 @@ -0,0 +1 @@ +dir_to_symlink /usr/lib/python3/dist-packages/notebook/static/components/codemirror ../../../../../../share/javascript/codemirror 6.4.12-2.2~
Bug#1036852: unblock: r-cran-pander/0.6.5+dfsg-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: Andreas Tille Please unblock package r-cran-pander [ Reason ] r-cran-pander needs jquery-1.7.2.js (it is unknown whether newer versions would work, too), but that is no longer available in the Debian archive, causing the package to ship a broken symlink. Therefore let the package ship a copy of the old jquery version. [ Impact ] Some r-cran-pander functionality may be missing and/or cause errors due to missing .js files. [ Tests ] piuparts stops reporting a broken symlink (in a lot of packages depending on this one). [ Risks ] testing/porting r-cran-pander for use with newer jquery versions might be more difficult and risky than using a known good version. The node-jquery-ui dependency might now be superfluous. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [ ] attach debdiff against the package in testing [ Other info ] $ diffstat r-cran-pander_0.6.5+dfsg-3.dsc.diff.xz changelog |8 missing-sources/jquery/get |2 missing-sources/jquery/jquery-1.7.2.js | 9404 + missing-sources/jquery/jquery-1.7.2.min.js | 23 rules |4 5 files changed, 9438 insertions(+), 3 deletions(-) (compressed diff is still > 90kb) $ filterdiff -x '*.js' r-cran-pander_0.6.5+dfsg-3.dsc.diff diff -Nru r-cran-pander-0.6.5+dfsg/debian/changelog r-cran-pander-0.6.5+dfsg/debian/changelog --- r-cran-pander-0.6.5+dfsg/debian/changelog 2023-02-21 21:25:31.0 +0100 +++ r-cran-pander-0.6.5+dfsg/debian/changelog 2023-05-19 12:38:06.0 +0200 @@ -1,3 +1,11 @@ +r-cran-pander (0.6.5+dfsg-3) unstable; urgency=medium + + * Provide source and compressed JS of jquery 1.7.2 since it is not +provided by any other package any more +Closes: #1035855 + + -- Andreas Tille Fri, 19 May 2023 12:38:06 +0200 + r-cran-pander (0.6.5+dfsg-2) unstable; urgency=medium * Pre-compress jcaption.js to avoid calling closure-compiler at diff -Nru r-cran-pander-0.6.5+dfsg/debian/missing-sources/jquery/get r-cran-pander-0.6.5+dfsg/debian/missing-sources/jquery/get --- r-cran-pander-0.6.5+dfsg/debian/missing-sources/jquery/get 1970-01-01 01:00:00.0 +0100 +++ r-cran-pander-0.6.5+dfsg/debian/missing-sources/jquery/get 2023-05-19 12:38:06.0 +0200 @@ -0,0 +1,2 @@ +wget http://code.jquery.com/jquery-1.7.2.js +yui-compressor jquery-1.7.2.js > jquery-1.7.2.min.js diff -Nru r-cran-pander-0.6.5+dfsg/debian/rules r-cran-pander-0.6.5+dfsg/debian/rules --- r-cran-pander-0.6.5+dfsg/debian/rules 2023-02-21 21:25:31.0 +0100 +++ r-cran-pander-0.6.5+dfsg/debian/rules 2023-05-19 12:38:06.0 +0200 @@ -8,6 +8,7 @@ override_dh_install: dh_install dh_install debian/missing-sources/jcaption/jcaption.min.js $(debRdir)/$(cranNameOrig)/includes/javascripts/ + dh_install debian/missing-sources/jquery/jquery-1.7.2.min.js $(debRdir)/$(cranNameOrig)/includes/javascripts/ dh_install debian/missing-sources/rapporter.net/*.gif $(debRdir)/$(cranNameOrig)/includes/images/ dh_install debian/missing-sources/stylesheets/*.css $(debRdir)/$(cranNameOrig)/includes/stylesheets/ sed -i \ @@ -18,6 +19,3 @@ -e '/html5shim/d' \ $(debRlib)/$(cranNameOrig)/includes/html/header.html find debian -name index.html | xargs sed -i 's|library|site-library|g' - -override_dh_link: - dh_link /usr/share/nodejs/jquery-ui/ui/jquery-1-7.min.js $(debRdir)/$(cranNameOrig)/includes/javascripts/jquery-1.7.2.min.js unblock r-cran-pander/0.6.5+dfsg-3 Andreas
Bug#1036021: cadabra2,python3-notebook: undeclared file conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror
Thanks. I applied this on top of cadabra2/experimental (which only had some useful metadata updates) and uploaded it to unstable. Unblock request filed. Do we still need some Breaks and dir_to_symlink in python3-notebook to recover from a bad installation order? probably something like - cadabra2 2.4.3.2-0.1 - python3-notebook 6.4.12-2.1 - cadabra2 2.4.3.2-1.1 Once we have fully solved this for bookworm, we should look into backporting the fixes to bullseye, too, which seems to have the same issue. Andreas
Bug#1036850: unblock: cadabra2/2.4.3.2-1.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: Martin Hostettler
Control: affects -1 + src:cadabra2
Please unblock package cadabra2
[ Reason ]
This is a rare case (i.e. only a single occurence in sid) of a
directory vs. symlink conflict: two different packages in a release
ship a path as either directory (containing files) or symlink.
(The typical case is where such a conflict happens is within the same
package on upgrades between releases if dpkg-maintscript-helper
dir_to_symlink/symlink_to_dir was forgotten.)
What ends up in the file system depends on the installation order of
cadabra2 and python3-notebook ...
This is fixed in cadabra2 by shipping the file in question directly in
the canonical location (i.e. where the symlink in python3-notebook
points to.).
[ Impact ]
Depending on the installation order
/usr/lib/python3/dist-packages/notebook/static/components/codemirror may
be
a) (the good case) a symlink to /usr/share/javascript/codemirror
containing a lot of javascript code or
b) (the bad case) a (nearly) empty directory, making python3-notebook
lose functionality
[ Tests ]
manual upgrade tests and debdiff inspection
[ Risks ]
It may well be that python3-notebook still needs some
Breaks: cadabra2 (<< 2.4.3.2-1.1~)
and
dpkg-maintscript-helper dir_to_symlink
to recover from bad installation order before the packages were fixed.
But making cadabra2 use the canonical location is mandatory for any
followup fixes.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
The effective binary debdiff is
[The following lists of changes regard files as different if they have
different names, permissions or owners.]
Files in second .deb but not in first
-
-rw-r--r-- root/root /usr/share/javascript/codemirror/mode/cadabra/cadabra.js
Files in first .deb but not in second
-
-rw-r--r-- root/root
/usr/lib/python3/dist-packages/notebook/static/components/codemirror/mode/cadabra/cadabra.js
Control files: lines which differ (wdiff format)
Installed-Size: [-14644-] {+14642+}
Version: [-2.4.3.2-0.1-] {+2.4.3.2-1.1+}
unblock cadabra2/2.4.3.2-1.1
Andreas
diff -Nru cadabra2-2.4.3.2/debian/changelog cadabra2-2.4.3.2/debian/changelog
--- cadabra2-2.4.3.2/debian/changelog 2023-02-06 23:21:08.0 +0100
+++ cadabra2-2.4.3.2/debian/changelog 2023-05-26 08:41:29.0 +0200
@@ -1,3 +1,21 @@
+cadabra2 (2.4.3.2-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Move codemirror integration to canonical path to
+avoid symlink/directory conflict on
+/usr/lib/python3/dist-packages/notebook/static/components/codemirror
+(Closes: 1036021)
+
+ -- Martin Hostettler Fri, 26 May 2023 06:41:29 +
+
+cadabra2 (2.4.3.2-1) experimental; urgency=medium
+
+ * d/control: Update Vcs fields.
+ * Bump standards version to 4.6.2.
+ * Acknowledge NMU, thanks to Adrian Bunk.
+
+ -- Gürkan Myczko Thu, 30 Mar 2023 11:44:14 +0200
+
cadabra2 (2.4.3.2-0.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru cadabra2-2.4.3.2/debian/control cadabra2-2.4.3.2/debian/control
--- cadabra2-2.4.3.2/debian/control 2022-08-14 20:25:58.0 +0200
+++ cadabra2-2.4.3.2/debian/control 2023-03-30 11:44:14.0 +0200
@@ -25,9 +25,9 @@
uuid-dev,
X-Python3-Version: >= 3.6
Rules-Requires-Root: no
-Standards-Version: 4.6.1
-Vcs-Git: https://salsa.debian.org/myczko-guest/cadabra2.git
-Vcs-Browser: https://salsa.debian.org/myczko-guest/cadabra2
+Standards-Version: 4.6.2
+Vcs-Git: https://salsa.debian.org/debian/cadabra2.git
+Vcs-Browser: https://salsa.debian.org/debian/cadabra2
Homepage: https://cadabra.science/
Package: cadabra2
diff -Nru cadabra2-2.4.3.2/debian/rules cadabra2-2.4.3.2/debian/rules
--- cadabra2-2.4.3.2/debian/rules 2022-10-13 09:06:04.0 +0200
+++ cadabra2-2.4.3.2/debian/rules 2023-05-26 08:41:29.0 +0200
@@ -27,6 +27,9 @@
dh_auto_install
sed -i s,python3.10,python3,g debian/cadabra2/usr/bin/cadabra2
sed -i s,site-,dist-,g debian/cadabra2/usr/bin/cadabra2
+ mv
debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static/components
debian/cadabra2/usr/share/javascript
+ rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static
+ rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook
override_dh_shlibdeps:
@echo test
Bug#1036846: unblock: isa-support/15.1
ncy-for-preinst diff -Nru isa-support-15/debian/armv7-support.maintscript isa-support-15.1/debian/armv7-support.maintscript --- isa-support-15/debian/armv7-support.maintscript 2022-09-12 12:52:10.0 +0200 +++ isa-support-15.1/debian/armv7-support.maintscript 2023-05-25 21:44:40.0 +0200 @@ -1 +1 @@ -dir_to_symlink /usr/share/doc/ARMv7-support isa-support 8~ \ No newline at end of file +dir_to_symlink /usr/share/doc/armv7-support isa-support 15.1~ diff -Nru isa-support-15/debian/armv8-support.lintian-overrides isa-support-15.1/debian/armv8-support.lintian-overrides --- isa-support-15/debian/armv8-support.lintian-overrides 2022-09-12 12:52:10.0 +0200 +++ isa-support-15.1/debian/armv8-support.lintian-overrides 2023-05-25 21:44:40.0 +0200 @@ -1,2 +1,2 @@ # debconf is optional, for nicer fail messages -ARMv8-support: missing-debconf-dependency-for-preinst +armv8-support: missing-debconf-dependency-for-preinst diff -Nru isa-support-15/debian/armv8-support.maintscript isa-support-15.1/debian/armv8-support.maintscript --- isa-support-15/debian/armv8-support.maintscript 2022-09-12 12:52:10.0 +0200 +++ isa-support-15.1/debian/armv8-support.maintscript 2023-05-25 21:44:40.0 +0200 @@ -1 +1 @@ -dir_to_symlink /usr/share/doc/ARMv8-support isa-support 8~ \ No newline at end of file +dir_to_symlink /usr/share/doc/armv8-support isa-support 15.1~ diff -Nru isa-support-15/debian/changelog isa-support-15.1/debian/changelog --- isa-support-15/debian/changelog 2022-09-12 12:53:47.0 +0200 +++ isa-support-15.1/debian/changelog 2023-05-25 21:44:40.0 +0200 @@ -1,3 +1,10 @@ +isa-support (15.1) unstable; urgency=high + + * Fix .maintscript generation for /usr/share/doc/$PACKAGE -> isa-support +symlink conversion. (Closes: #1035766). Thanks to Andreas Beckmann. + + -- Bastien Roucariès Thu, 25 May 2023 19:44:40 + + isa-support (15) unstable; urgency=high * Bug fix: "version 14 fails to install where version 13 installs fine diff -Nru isa-support-15/debian/neon-support.maintscript isa-support-15.1/debian/neon-support.maintscript --- isa-support-15/debian/neon-support.maintscript 2022-09-12 12:52:10.0 +0200 +++ isa-support-15.1/debian/neon-support.maintscript2023-05-25 21:44:40.0 +0200 @@ -1 +1 @@ -dir_to_symlink /usr/share/doc/neon-support isa-support 8~ \ No newline at end of file +dir_to_symlink /usr/share/doc/neon-support isa-support 15.1~ diff -Nru isa-support-15/debian/sse2-support.lintian-overrides isa-support-15.1/debian/sse2-support.lintian-overrides --- isa-support-15/debian/sse2-support.lintian-overrides2022-09-12 12:52:10.0 +0200 +++ isa-support-15.1/debian/sse2-support.lintian-overrides 2023-05-25 21:44:40.0 +0200 @@ -1,2 +1,2 @@ # debconf is optional, for nicer fail messages -SSE2-support: missing-debconf-dependency-for-preinst +sse2-support: missing-debconf-dependency-for-preinst diff -Nru isa-support-15/debian/sse2-support.maintscript isa-support-15.1/debian/sse2-support.maintscript --- isa-support-15/debian/sse2-support.maintscript 2022-09-12 12:52:10.0 +0200 +++ isa-support-15.1/debian/sse2-support.maintscript2023-05-25 21:44:40.0 +0200 @@ -1 +1 @@ -dir_to_symlink /usr/share/doc/SSE2-support isa-support 8~ \ No newline at end of file +dir_to_symlink /usr/share/doc/sse2-support isa-support 15.1~ diff -Nru isa-support-15/debian/sse3-support.lintian-overrides isa-support-15.1/debian/sse3-support.lintian-overrides --- isa-support-15/debian/sse3-support.lintian-overrides2022-09-12 12:52:10.0 +0200 +++ isa-support-15.1/debian/sse3-support.lintian-overrides 2023-05-25 21:44:40.0 +0200 @@ -1,2 +1,2 @@ # debconf is optional, for nicer fail messages -SSE3-support: missing-debconf-dependency-for-preinst +sse3-support: missing-debconf-dependency-for-preinst diff -Nru isa-support-15/debian/sse3-support.maintscript isa-support-15.1/debian/sse3-support.maintscript --- isa-support-15/debian/sse3-support.maintscript 2022-09-12 12:52:10.0 +0200 +++ isa-support-15.1/debian/sse3-support.maintscript2023-05-25 21:44:40.0 +0200 @@ -1 +1 @@ -dir_to_symlink /usr/share/doc/SSE3-support isa-support 8~ \ No newline at end of file +dir_to_symlink /usr/share/doc/sse3-support isa-support 15.1~ diff -Nru isa-support-15/debian/sse4.1-support.lintian-overrides isa-support-15.1/debian/sse4.1-support.lintian-overrides --- isa-support-15/debian/sse4.1-support.lintian-overrides 2022-09-12 12:52:10.0 +0200 +++ isa-support-15.1/debian/sse4.1-support.lintian-overrides2023-05-25 21:44:40.0 +0200 @@ -1,2 +1,2 @@ # debconf is optional, for nicer fail messages -SSE4.1-support: missing-debconf-dependency-for-preinst +sse4.1-support: missing-debconf-dependency-for-preinst diff -Nru isa-support-15/debian/sse4.1-support.maintscript isa-support-15.1/debian/sse4.1-support.maintscr
Bug#1036839: unblock: sane-backends/1.2.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package sane-backends [ Reason ] Some preinst script performed cleanup which resulted in deletion of files now owned by other packages. The preinst was unneccessary since the handled files were shipped by the package, so dpkg will perform all neccessary cleanup if the files get removed (or moved to another package), no manual cleanup is needed. [ Impact ] debsums reports missing files, manpages are missing. [ Tests ] Local piuparts tests showed clean bullseye->bookworm upgrades with the fixed packages. [ Risks ] [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] n/a unblock sane-backends/1.2.1-2 Andreas diff -Nru sane-backends-1.2.1/debian/changelog sane-backends-1.2.1/debian/changelog --- sane-backends-1.2.1/debian/changelog2023-02-13 19:25:08.0 +0100 +++ sane-backends-1.2.1/debian/changelog2023-05-16 18:49:09.0 +0200 @@ -1,3 +1,10 @@ +sane-backends (1.2.1-2) unstable; urgency=medium + + * Fix remove wrong remove manpage (Closes: #1035677): +- Remove debian/sane-utils.preinst. + + -- Jörg Frings-Fürst Tue, 16 May 2023 18:49:09 +0200 + sane-backends (1.2.1-1) unstable; urgency=medium * New upstream release: diff -Nru sane-backends-1.2.1/debian/sane-utils.preinst sane-backends-1.2.1/debian/sane-utils.preinst --- sane-backends-1.2.1/debian/sane-utils.preinst 2022-02-28 08:15:57.0 +0100 +++ sane-backends-1.2.1/debian/sane-utils.preinst 1970-01-01 01:00:00.0 +0100 @@ -1,27 +0,0 @@ -#!/bin/sh - -set -e - -MANPAGE=/usr/share/man/man5/sane-umax_pp.5.gz -MANLINK=/usr/share/man/man5/umax_pp.5.gz - - -if [ "$1" = upgrade ]; then - -## Remove obsolete manpages that are now provided by sane-common -if dpkg --compare-versions "$2" le "1.1.1-2"; then - - if [ -f "$MANLINK" ] && [ -L "$MANLINK" ]; then - rm -rf "$MANLINK" - fi - - - if [ -f "$MANPAGE" ]; then - rm -rf "$MANPAGE" - fi -fi -fi - - - -#DEBHELPER#
Bug#1036837: unblock: pyrlp/0.5.1-3.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Control: affects -1 + src:pyrlp Please unblock package pyrlp [ Reason ] /usr/share/doc/$PKG was changed from a diretory to a symlink, but the corresponding dpkg-maintscript-helper dir_to_symlnk call was missing. [ Impact ] /usr/share/doc/$PKG remaining as an empty directory, /usr/share/doc/$PKG/copyright missing. [ Tests ] Local piuparts tests showed clean bullseye->bookworm upgrades. [ Risks ] Low. One line source change, similar changes have been applied to dozens other packages in the past, fixing the same issue. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] n/a unblock pyrlp/0.5.1-3.1 Andreas >From 53cca3a3b1ba2992e9a4f5d298c1c5c3bc8398ad Mon Sep 17 00:00:00 2001 From: Andreas Beckmann Date: Sat, 27 May 2023 21:27:06 +0200 Subject: [PATCH] perform dir to symlink conversion of /usr/share/doc/python-rlp-doc --- debian/changelog | 8 debian/python-rlp-doc.maintscript | 1 + 2 files changed, 9 insertions(+) create mode 100644 debian/python-rlp-doc.maintscript diff --git a/debian/changelog b/debian/changelog index 8d50671..9d11f64 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +pyrlp (0.5.1-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Perform dir to symlink conversion of /usr/share/doc/python-rlp-doc. +(Closes: #1035765) + + -- Andreas Beckmann Sat, 27 May 2023 21:26:57 +0200 + pyrlp (0.5.1-3) unstable; urgency=medium * Update UScan configuration for changes in upstream releases page. diff --git a/debian/python-rlp-doc.maintscript b/debian/python-rlp-doc.maintscript new file mode 100644 index 000..3457c0e --- /dev/null +++ b/debian/python-rlp-doc.maintscript @@ -0,0 +1 @@ +dir_to_symlink /usr/share/doc/python-rlp-doc python3-rlp 0.5.1-3.1~ -- 2.20.1
Bug#1036836: unblock: curlpp/0.8.1-5.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Control: affects -1 + src:curlpp Please unblock package curlpp [ Reason ] Some path was changed from a symlink to a directory containing files, but the corresponding dpkg-maintscript-helper symlink_to_dir call was missing. [ Impact ] Files ending up at a location in the file system where dpkg does not track them, possibly silently overwriting other files. [ Tests ] Local piuparts tests showed clean bullseye->bookworm upgrades. [ Risks ] Low. One line source change, similar changes have been applied to dozens other packages in the past. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] n/a unblock curlpp/0.8.1-5.1 Andreas diff -Nru curlpp-0.8.1/debian/changelog curlpp-0.8.1/debian/changelog --- curlpp-0.8.1/debian/changelog 2021-09-03 09:36:39.0 +0200 +++ curlpp-0.8.1/debian/changelog 2023-05-25 15:39:56.0 +0200 @@ -1,3 +1,11 @@ +curlpp (0.8.1-5.1) unstable; urgency=medium + + * Non-maintainer upload. + * libcurlpp-dev: Perform symlink to directory conversion of +/usr/share/doc/libcurlpp-dev. (Closes: #1035631) + + -- Andreas Beckmann Thu, 25 May 2023 15:39:56 +0200 + curlpp (0.8.1-5) unstable; urgency=medium * Do not ship symbols at the moment. diff -Nru curlpp-0.8.1/debian/libcurlpp-dev.maintscript curlpp-0.8.1/debian/libcurlpp-dev.maintscript --- curlpp-0.8.1/debian/libcurlpp-dev.maintscript 1970-01-01 01:00:00.0 +0100 +++ curlpp-0.8.1/debian/libcurlpp-dev.maintscript 2023-05-25 15:38:51.0 +0200 @@ -0,0 +1 @@ +symlink_to_dir /usr/share/doc/libcurlpp-dev libcurlpp0 0.8.1-5.1~
Bug#1035691: python3-aiosmtpd: unhandled symlink to directory conversion: /usr/share/doc/python3-aiosmtpd/html/_sources -> ../rst
On 26/05/2023 14.21, Pierre-Elliott Bécue wrote: Could you upload the patch on salsa (branch=master)? Done Will you file the unblock bug or should I do it? Done Andreas
Bug#1036835: unblock: python-aiosmtpd/1.4.3-1.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Control: affects -1 + src:python-aiosmtpd Please unblock package python-aiosmtpd [ Reason ] Some path was changed from a symlink to a directory containing files, but the corresponding dpkg-maintscript-helper symlink_to_dir call was missing. [ Impact ] Files ending up at a location in the file system where dpkg does not track them, possibly silently overwriting other files. [ Tests ] Local piuparts tests showed clean bullseye->bookworm upgrades. [ Risks ] Low. One line source change, similar changes have been applied to dozens other packages in the past. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] n/a unblock python-aiosmtpd/1.4.3-1.1 Andreas >From 8d9d96a7dd7875670b96ace93c18de1b056d3111 Mon Sep 17 00:00:00 2001 From: Andreas Beckmann Date: Thu, 25 May 2023 16:10:24 +0200 Subject: [PATCH] perform symlink to directory conversion of /usr/share/doc/python3-aiosmtpd/html/_sources --- debian/changelog| 8 debian/python3-aiosmtpd.maintscript | 1 + 2 files changed, 9 insertions(+) create mode 100644 debian/python3-aiosmtpd.maintscript diff --git a/debian/changelog b/debian/changelog index 50c5ce5..72e5698 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +python-aiosmtpd (1.4.3-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Perform symlink to directory conversion of +/usr/share/doc/python3-aiosmtpd/html/_sources. (Closes: #1035691) + + -- Andreas Beckmann Thu, 25 May 2023 16:09:53 +0200 + python-aiosmtpd (1.4.3-1) unstable; urgency=medium * New upstream release 1.4.3 (Closes: #1026471, #1025019) diff --git a/debian/python3-aiosmtpd.maintscript b/debian/python3-aiosmtpd.maintscript new file mode 100644 index 000..265ff02 --- /dev/null +++ b/debian/python3-aiosmtpd.maintscript @@ -0,0 +1 @@ +symlink_to_dir /usr/share/doc/python3-aiosmtpd/html/_sources ../rst 1.4.3-1.1~ -- 2.20.1
Bug#1036603: libinventor1: broken symlinks: /usr/share/inventor/fonts/Century-Schoolbook-* -> /usr/share/fonts/X11/Type1/c0590*l.pfb
On 26/05/2023 05.01, Steven Robbins wrote: fonts-urw-base35 does not provide the old "numeric" font names gsfonts-x11 had. Thanks for this. Do you happen to know of a package that does ship those fonts, even if a different name? That should be fonts-urw-base35, at least that's what the transitional gsfonts-x11 package is depending on. If that does not contain all the fonts, we have an additional bug ... Andreas
Bug#1036789: libpython3.12-testsuite: fails to install: SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)?
Package: libpython3.12-testsuite Version: 3.12.0~b1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up libpython3.12-testsuite (3.12.0~b1-1) ... File "/usr/lib/python3.12/test/test_lib2to3/data/bom.py", line 2 print "BOM BOOM!" ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)? dpkg: error processing package libpython3.12-testsuite (--configure): installed libpython3.12-testsuite package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.36-9) ... Errors were encountered while processing: libpython3.12-testsuite cheers, Andreas libpython3.12-testsuite_3.12.0~b1-1.log.gz Description: application/gzip
Bug#1035765: python-rlp-doc: copyright file missing after upgrade (policy 12.5)
Followup-For: Bug #1035765 Control: tag -1 patch Hi, all that is needed is a dir_to_symlink call, please see the attached patch. I'll prepare a NMU and upload it with 0-day delay tomorrow to get this fix into bookworm. Andreas >From a046121a848d7f91cb0a81b91030ce4fb1119bdd Mon Sep 17 00:00:00 2001 From: Andreas Beckmann Date: Thu, 25 May 2023 19:18:52 +0200 Subject: [PATCH] perform dir to symlink conversion of /usr/share/doc/python-rlp-doc --- debian/changelog | 8 debian/python-rlp-doc.maintscript | 1 + 2 files changed, 9 insertions(+) create mode 100644 debian/python-rlp-doc.maintscript diff --git a/debian/changelog b/debian/changelog index 8d50671..72f6d22 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +pyrlp (0.5.1-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Perform dir to symlink conversion of /usr/share/doc/python-rlp-doc. +(Closes: #1035765) + + -- Andreas Beckmann Thu, 25 May 2023 19:17:55 +0200 + pyrlp (0.5.1-3) unstable; urgency=medium * Update UScan configuration for changes in upstream releases page. diff --git a/debian/python-rlp-doc.maintscript b/debian/python-rlp-doc.maintscript new file mode 100644 index 000..3457c0e --- /dev/null +++ b/debian/python-rlp-doc.maintscript @@ -0,0 +1 @@ +dir_to_symlink /usr/share/doc/python-rlp-doc python3-rlp 0.5.1-3.1~ -- 2.20.1
Bug#1035766: sse{2,3,4.2}-support: copyright file missing after upgrade (policy 12.5)
Followup-For: Bug #1035766 Control: tag -1 patch The .maintscript files are generated with an uppercase /usr/share/doc/NAME-support to be converted, that of course does not work. Andreas >From 14252f3d180c8ddf29449ac87d1db7b2855d0168 Mon Sep 17 00:00:00 2001 From: Andreas Beckmann Date: Thu, 25 May 2023 18:38:45 +0200 Subject: [PATCH] fix .maintscript generation --- debian/@lcn...@-support.maintscript.in | 2 +- debian/changelog | 7 +++ refresh-package| 1 + 3 files changed, 9 insertions(+), 1 deletion(-) diff --git a/debian/@lcn...@-support.maintscript.in b/debian/@lcn...@-support.maintscript.in index 773d275..40503e9 100644 --- a/debian/@lcn...@-support.maintscript.in +++ b/debian/@lcn...@-support.maintscript.in @@ -1 +1 @@ -dir_to_symlink /usr/share/doc/@NAME@-support isa-support 8~ \ No newline at end of file +dir_to_symlink /usr/share/doc/@LCNAME@-support isa-support 15.1~ diff --git a/debian/changelog b/debian/changelog index dde362f..ce3c4ac 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +isa-support (15.1) UNRELEASED; urgency=medium + + * Fix .maintscript generation for /usr/share/doc/$PACKAGE -> isa-support +symlink conversion. (Closes: #1035766) + + -- Andreas Beckmann Thu, 25 May 2023 18:35:12 +0200 + isa-support (15) unstable; urgency=high * Bug fix: "version 14 fails to install where version 13 installs fine diff --git a/refresh-package b/refresh-package index cec9240..8f6e4a9 100755 --- a/refresh-package +++ b/refresh-package @@ -15,6 +15,7 @@ sub file_replace close IN; s/[@]NAME[@]/$name/g; +s/[@]LCNAME[@]/$lcname/g; s/[@]DEB_HOST_MULTIARCH[@]/$DEB_HOST_MULTIARCH/g; open OUT, ">debian/$foutname" or die "Can't write debian/$foutname: $!\n"; -- 2.20.1
Bug#1035691: python3-aiosmtpd: unhandled symlink to directory conversion: /usr/share/doc/python3-aiosmtpd/html/_sources -> ../rst
Followup-For: Bug #1035691 Control: tag -1 patch pending I've uploaded a verified fix to DELAYED/1 to reach the bookworm deadline. Andreas >From 8d9d96a7dd7875670b96ace93c18de1b056d3111 Mon Sep 17 00:00:00 2001 From: Andreas Beckmann Date: Thu, 25 May 2023 16:10:24 +0200 Subject: [PATCH] perform symlink to directory conversion of /usr/share/doc/python3-aiosmtpd/html/_sources --- debian/changelog| 8 debian/python3-aiosmtpd.maintscript | 1 + 2 files changed, 9 insertions(+) create mode 100644 debian/python3-aiosmtpd.maintscript diff --git a/debian/changelog b/debian/changelog index 50c5ce5..72e5698 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +python-aiosmtpd (1.4.3-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Perform symlink to directory conversion of +/usr/share/doc/python3-aiosmtpd/html/_sources. (Closes: #1035691) + + -- Andreas Beckmann Thu, 25 May 2023 16:09:53 +0200 + python-aiosmtpd (1.4.3-1) unstable; urgency=medium * New upstream release 1.4.3 (Closes: #1026471, #1025019) diff --git a/debian/python3-aiosmtpd.maintscript b/debian/python3-aiosmtpd.maintscript new file mode 100644 index 000..265ff02 --- /dev/null +++ b/debian/python3-aiosmtpd.maintscript @@ -0,0 +1 @@ +symlink_to_dir /usr/share/doc/python3-aiosmtpd/html/_sources ../rst 1.4.3-1.1~ -- 2.20.1
Bug#1035631: libcurlpp-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Followup-For: Bug #1035631 Control: tag -1 patch pending I've uploaded a verified fix to DELAYED/1 to reach the bookworm deadline. Andreas diff -Nru curlpp-0.8.1/debian/changelog curlpp-0.8.1/debian/changelog --- curlpp-0.8.1/debian/changelog 2021-09-03 09:36:39.0 +0200 +++ curlpp-0.8.1/debian/changelog 2023-05-25 15:39:56.0 +0200 @@ -1,3 +1,11 @@ +curlpp (0.8.1-5.1) unstable; urgency=medium + + * Non-maintainer upload. + * libcurlpp-dev: Perform symlink to directory conversion of +/usr/share/doc/libcurlpp-dev. (Closes: #1035631) + + -- Andreas Beckmann Thu, 25 May 2023 15:39:56 +0200 + curlpp (0.8.1-5) unstable; urgency=medium * Do not ship symbols at the moment. diff -Nru curlpp-0.8.1/debian/libcurlpp-dev.maintscript curlpp-0.8.1/debian/libcurlpp-dev.maintscript --- curlpp-0.8.1/debian/libcurlpp-dev.maintscript 1970-01-01 01:00:00.0 +0100 +++ curlpp-0.8.1/debian/libcurlpp-dev.maintscript 2023-05-25 15:38:51.0 +0200 @@ -0,0 +1 @@ +symlink_to_dir /usr/share/doc/libcurlpp-dev libcurlpp0 0.8.1-5.1~
Bug#1036743: [Debian-med-packaging] Bug#1036743: kleborate: debsums reports modified files after apt-get upgrade && apt-get dist-upgrade
On 25/05/2023 14.42, Andreas Tille wrote: Am Thu, May 25, 2023 at 10:34:10AM +0200 schrieb Étienne Mollier: Installation of kleborate from sid and testing shown no issues. Installation of kleborate from bullseye on bullseye is okay too. Good. Maybe we should reflect in BTS that this bug is not relevant for bookworm? It is relevant for bookworm, it's just not happening in the upgrade tests on piuparts.d.o (because that does no 2-step upgrades) In the failing test kleborate got upgraded during 'apt-get upgrade' while ncbi-blast+ only got upgraded during the subsequent 'apt-get dist-upgrade'. So the kleborate.postinst from bookworm was actually running makeblastdb from bullseye, creating files in the "older" format. Are these "old format" files still correctly usable after the dist-upgrade has been performed? Or would that need some kind of trigger mechanism to regenerate these files with the newer makeblastdb version? I haven't checked closely yet, but I suspect the .ndb and .ntf should be removed from the .deb and rely entirely on mkaeblastdb to produce the files. Looking that up… Without checking this seems to be a sensible assumption. Yes. Either the file is created at build time or at installation time. Doing both does not look like a sensible idea to me. (And it didn't produce identical files, otherwise I wouldn't have noticed this bug) Andreas
Bug#1035677: sane-utils: preinst deletes file owned by libsane-common: /usr/share/man/man5/sane-umax_pp.5.gz
On Tue, 16 May 2023 19:09:26 +0200 =?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?= wrote: please can you check the changes from Sorry, I seem to have missed this mail ... The changes look good and I can confirm that the upgrade issues are resolved with the .prerm removed. I've uploaded that to DELAYED/1. Andreas
Bug#1033894: lintian: bad-distribution-in-changes-file bookworm
Followup-For: Bug #1033894 Shouldn't we release bookworm with a lintian that knows about bookworm? Time is quickly running out ... Andreas
Bug#1036746: lintian: package-contains-no-arch-dependent-files does not trigger if there is a header file with non-ascii (UTF-8) characters
Package: lintian Version: 2.116.3 Severity: normal I just looked into the spurious (dis-)appearance of X: libnvidia-ml-dev: package-contains-no-arch-dependent-files libnvidia-ml-dev is a header-only package: $ find 1* 11.8.0 11.8.0/usr 11.8.0/usr/include 11.8.0/usr/include/nvml.h 11.8.0/usr/share 11.8.0/usr/share/doc 11.8.0/usr/share/doc/libnvidia-ml-dev 11.8.0/usr/share/doc/libnvidia-ml-dev/changelog.Debian.gz 11.8.0/usr/share/doc/libnvidia-ml-dev/copyright 11.8.0/usr/share/lintian 11.8.0/usr/share/lintian/overrides 11.8.0/usr/share/lintian/overrides/libnvidia-ml-dev 12.0.0 12.0.0/usr 12.0.0/usr/include 12.0.0/usr/include/nvml.h 12.0.0/usr/share 12.0.0/usr/share/doc 12.0.0/usr/share/doc/libnvidia-ml-dev 12.0.0/usr/share/doc/libnvidia-ml-dev/changelog.Debian.gz 12.0.0/usr/share/doc/libnvidia-ml-dev/copyright 12.0.1 12.0.1/usr 12.0.1/usr/include 12.0.1/usr/include/nvml.h 12.0.1/usr/share 12.0.1/usr/share/doc 12.0.1/usr/share/doc/libnvidia-ml-dev 12.0.1/usr/share/doc/libnvidia-ml-dev/changelog.Debian.gz 12.0.1/usr/share/doc/libnvidia-ml-dev/copyright and the only difference I see is $ file 1*/usr/include/nvml.h 11.8.0/usr/include/nvml.h: C source, ASCII text 12.0.0/usr/include/nvml.h: C source, UTF-8 Unicode text 12.0.1/usr/include/nvml.h: C source, ASCII text The 11.8.0 package (in sid) does trigger package-contains-no-arch-dependent-files (but it is overridden), the 12.0.0 package (in experimental) does not trigger (therefore override removed), while 12.0.1 (not yet uploaded) again triggers the tag. The only non-ascii char seems to be '’' (e2 80 99) in a comment ... Andreas
Bug#1035361: sauce: Potentially dangerous mode on /etc/logrotate.d/sauce: 0755
Followup-For: Bug #1035361 Control: found -1 0.9.2 While the package works fine after a fresh install in sid or bookworm, the issue is still present after an upgrade from bullseye to bookworm. File permissions of conffiles do net seem to get updated on upgrades, this needs to be fixed manually in the postinst, e.g. (untested) if dpkg --compare-versions "$2" lt-nl "0.9.3~" then chmod -v -x /etc/logrotate.d/sauce fi Andreas
Bug#1036743: kleborate: debsums reports modified files after apt-get upgrade && apt-get dist-upgrade
Package: kleborate Version: 2.3.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed debsums reporting modified files after a 2-stage upgrade from bullseye to bookworm: apt-get upgrade apt-get dist-upgrade (It does not happen if only a single-stage apt-get dist-upgrade is used) kleborate gets upgraded during the first stage, 'apt-get upgrade'. >From the attached log (scroll to the bottom...): 2m4.4s ERROR: FAIL: debsums reports modifications inside the chroot: /usr/lib/python3/dist-packages/kleborate/data/CARD_v3.1.13.fasta.ndb /usr/lib/python3/dist-packages/kleborate/data/CARD_v3.1.13.fasta.ntf /usr/lib/python3/dist-packages/kleborate/data/Klebsiella_pneumoniae.fasta.ndb /usr/lib/python3/dist-packages/kleborate/data/Klebsiella_pneumoniae.fasta.ntf /usr/lib/python3/dist-packages/kleborate/data/MgrB_and_PmrB.fasta.ndb /usr/lib/python3/dist-packages/kleborate/data/MgrB_and_PmrB.fasta.ntf /usr/lib/python3/dist-packages/kleborate/data/OmpK.fasta.ndb /usr/lib/python3/dist-packages/kleborate/data/OmpK.fasta.ntf /usr/lib/python3/dist-packages/kleborate/data/QRDR_120.fasta.ndb /usr/lib/python3/dist-packages/kleborate/data/QRDR_120.fasta.ntf /usr/lib/python3/dist-packages/kleborate/data/clb_alleles.fasta.ndb /usr/lib/python3/dist-packages/kleborate/data/clb_alleles.fasta.ntf /usr/lib/python3/dist-packages/kleborate/data/iro_alleles.fasta.ndb /usr/lib/python3/dist-packages/kleborate/data/iro_alleles.fasta.ntf /usr/lib/python3/dist-packages/kleborate/data/iuc_alleles.fasta.ndb /usr/lib/python3/dist-packages/kleborate/data/iuc_alleles.fasta.ntf /usr/lib/python3/dist-packages/kleborate/data/rmpA2.fasta.ndb /usr/lib/python3/dist-packages/kleborate/data/rmpA2.fasta.ntf /usr/lib/python3/dist-packages/kleborate/data/rmp_alleles.fasta.ndb /usr/lib/python3/dist-packages/kleborate/data/rmp_alleles.fasta.ntf /usr/lib/python3/dist-packages/kleborate/data/wzi.fasta.ndb /usr/lib/python3/dist-packages/kleborate/data/wzi.fasta.ntf /usr/lib/python3/dist-packages/kleborate/data/ybt_alleles.fasta.ndb /usr/lib/python3/dist-packages/kleborate/data/ybt_alleles.fasta.ntf cheers, Andreas kleborate_2.3.1-1.log.gz Description: application/gzip
Bug#1036096: jed,xjed: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Followup-For: Bug #1036096 Control: found -1 1:0.99.20~pre.178+dfsg-5 The .maintscript files are missing the epoch in the version, therefore the cleanup is not performed on upgrades from bullseye. Please bump the version in the .maintscript files to 1:0.99.20~pre.178+dfsg-6~ s.t. the cleanup is also performed on upgrades from stable to testing (missed cleanup) to unstable (and later testing) (fixed cleanup) Andreas PS: I didn't spot the missing epoch when I had a quick look over the commit ...
Bug#1036737: libsoapysdr0.8: please add Breaks: libsoapysdr0.7 for smoother upgrades from bullseye
Package: libsoapysdr0.8
Version: 0.8.1-2
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
The soapysdr library stacks from bullseye and bookworm are not
co-installable, but the transitive conflict behind longer dependency
chains is not always easy detectable by apt. Therefore several upgrade
paths result in old libraries being kept installed and some upgradable
packages being kept at an older version.
Making the conflict explicit between higher scoring packages helps apt
finding a better upgrade path.
Please consider applying the attached patch.
Andreas
>From 25ca6005f2c4afec53e20d7f5cb2529e1887f218 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Wed, 24 May 2023 09:37:52 +0200
Subject: [PATCH] libsoapysdr0.8: add Breaks: libsoapysdr0.7 for smoother
upgrades from bullseye
---
debian/changelog | 7 +++
debian/control | 1 +
2 files changed, 8 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index c75c280..c78de26 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+soapysdr (0.8.1-3) UNRELEASED; urgency=medium
+
+ * libsoapysdr0.8: Add Breaks: libsoapysdr0.7 for smoother upgrades from
+bullseye. (Closes: #)
+
+ -- Andreas Beckmann Wed, 24 May 2023 09:35:42 +0200
+
soapysdr (0.8.1-2) unstable; urgency=medium
* Upload to unstable
diff --git a/debian/control b/debian/control
index 5971f7f..40193f8 100644
--- a/debian/control
+++ b/debian/control
@@ -24,6 +24,7 @@ Architecture: any
Multi-Arch: same
Depends: ${shlibs:Depends}, ${misc:Depends}
Recommends: soapysdr0.8-module-all | soapysdr0.8-module
+Breaks: libsoapysdr0.7
Description: software defined radio interface library
SoapySDR is a library providing a common interface to SDR (software
defined radio) hardware. Support for different hardware is added through
--
2.20.1
Bug#1036676: transition: nvidia-cuda-toolkit 12
On 24/05/2023 21.13, Cyril Brulebois wrote: Just for the avoidance of doubt since this topic came up during our meeting: this is definitely post-bookworm, right? Yes. Andreas
Bug#1036690: node-stylis: missing Breaks+Replaces: node-mermaid (<< 8.14.0+~cs11.4.14-2~)
Package: node-stylis Version: 4.1.3~11.10.7+ds1+~cs8.3.3-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces Selecting previously unselected package node-stylis. Preparing to unpack .../node-stylis_4.1.3~11.10.7+ds1+~cs8.3.3-3_all.deb ... Unpacking node-stylis (4.1.3~11.10.7+ds1+~cs8.3.3-3) ... dpkg: error processing archive /var/cache/apt/archives/node-stylis_4.1.3~11.10.7+ds1+~cs8.3.3-3_all.deb (--unpack): trying to overwrite '/usr/share/doc/node-stylis/README.md.gz', which is also in package node-mermaid 8.14.0+~cs11.4.14-1 Errors were encountered while processing: /var/cache/apt/archives/node-stylis_4.1.3~11.10.7+ds1+~cs8.3.3-3_all.deb 8.14.0+~cs11.4.14-2 is a guess, assuming the next maintainer upload will drop the copy of node-stylis from node-mermaid (#1036688). The conflicting files are usr/share/doc/node-stylis/README.md.gz usr/share/doc/node-stylis/copyright usr/share/nodejs/stylis/dist/stylis.mjs usr/share/nodejs/stylis/dist/stylis.mjs.map usr/share/nodejs/stylis/dist/umd/package.json usr/share/nodejs/stylis/dist/umd/stylis.js usr/share/nodejs/stylis/dist/umd/stylis.js.map usr/share/nodejs/stylis/index.js usr/share/nodejs/stylis/package.json usr/share/nodejs/stylis/pkgjs-lock.json usr/share/nodejs/stylis/src/Enum.js usr/share/nodejs/stylis/src/Middleware.js usr/share/nodejs/stylis/src/Parser.js usr/share/nodejs/stylis/src/Prefixer.js usr/share/nodejs/stylis/src/Serializer.js usr/share/nodejs/stylis/src/Tokenizer.js usr/share/nodejs/stylis/src/Utility.js cheers, Andreas
Bug#1036688: node-mermaid: node-stylis is now packaged separately
Package: node-mermaid Version: 8.14.0+~cs11.4.14-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts node-stylis is now available in a separate package. Please stop shipping a copy of node-stylis and depend on node-stylis instead. Andreas
Bug#1036685: librocthrust-dev: missing Conflicts: libthrust-dev
Package: librocthrust-dev Version: 5.3.3-2 Severity: serious Since both packages ship /usr/include/thrust/*, please add a Conflicts: libthrust-dev Andreas
Bug#1036684: tomopy: FTBFS with CUDA 12: nvcc fatal : Unsupported gpu architecture 'compute_35'
Source: tomopy Version: 1.10.4+ds1-9 Severity: important Tags: ftbfs sid Justification: fails to build from source Control: block 1036676 with -1 Hi, tomopy FTBFS with CUDA 12 in experimental: ... nvcc fatal : Unsupported gpu architecture 'compute_35' ... Andreas
Bug#1036683: starpu-contrib: FTBFS with CUDA 12: "It is an error to include both cublas.h and cublas_v2.h"
Source: starpu-contrib Version: 1.3.10+dfsg-1 Severity: important Tags: ftbfs sid Justification: fails to build from source Control: block 1036676 with -1 Hi, starpu-contrib FTBFS with CUDA 12 in experimental: ... In file included from ../../include/starpu_cublas_v2.h:22, from ../../src/drivers/cuda/starpu_cublas.c:24: /usr/include/cublas_v2.h:59:2: error: #error "It is an error to include both cublas.h and cublas_v2.h" 59 | #error "It is an error to include both cublas.h and cublas_v2.h" | ^ make[3]: *** [Makefile:2667: libstarpu_1.3_la-starpu_cublas.lo] Error 1 Andreas
Bug#1036682: slurm-wlm-contrib: FTBFS with CUDA 12: dh_install: warning: Cannot find "usr/lib/*/slurm-wlm/gpu_nvml.so"
Source: slurm-wlm-contrib Version: 22.05.8-4 Severity: important Tags: ftbfs sid Justification: fails to build from source Control: block 1036676 with -1 Hi, slurm-wlm-contrib FTBFS with CUDA 12 in experimental: dh_install -O--builddirectory dh_install: warning: Cannot find (any matches for) "usr/lib/*/slurm-wlm/gpu_nvml.so" (tried in ., debian/tmp) dh_install: warning: slurm-wlm-nvml-plugin missing files: usr/lib/*/slurm-wlm/gpu_nvml.so dh_install: warning: Cannot find (any matches for) "usr/lib/*/slurm-wlm/gpu_nvml.a" (tried in ., debian/tmp) dh_install: warning: slurm-wlm-nvml-plugin-dev missing files: usr/lib/*/slurm-wlm/gpu_nvml.a dh_install: error: missing files, aborting make: *** [debian/rules:17: binary] Error 25 Andreas
Bug#1036681: relion-cuda: FTBFS with CUDA 12: nvcc fatal : Value 'sm_35' is not defined for option 'gpu-architecture'
Source: relion-cuda Version: 3.1.3-2 Severity: important Tags: ftbfs sid Justification: fails to build from source Control: block 1036676 with -1 Hi, relion-cuda FTBFS with CUDA 12 in experimental: ... nvcc fatal : Value 'sm_35' is not defined for option 'gpu-architecture' CMake Error at relion_gpu_util_generated_cuda_backprojector.cu.o.Release.cmake:220 (message): Error generating /build/relion-cuda-3.1.3/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_backprojector.cu.o ... Andreas
Bug#1036680: pyhst2: FTBFS with CUDA 12: error: texture is not a template
Source: pyhst2 Version: 2020c-7 Severity: important Tags: ftbfs sid Justification: fails to build from source Control: block 1036676 with -1 Hi, pyhst2 FTBFS with CUDA 12 in experimental: ... PyHST/Cspace/cudamedianfilter.cu(55): error: texture is not a template ... (and tons of followup errors probably caused by this one). Andreas
Bug#1036679: magma: FTBFS with CUDA 12: error: 'csrsm2Info_t' does not name a type
Package: magma Version: 2.6.2-1 Severity: important Tags: ftbfs sid Justification: fails to build from source Control: block 1036676 with -1 Hi, magma FTBFS with CUDA 12 in experimental: ... In file included from ./sparse/include/magmasparse_z.h:16, from ./sparse/include/magmasparse.h:20, from ./sparse/control/magmasparse_internal.h:15, from sparse/blas/magma_z_blaswrapper.cpp:12: ./sparse/include/magmasparse_types.h:610:32: error: 'csrsm2Info_t' does not name a type; did you mean 'bsrsm2Info_t'? 610 | #define magma_solve_info_t csrsm2Info_t |^~~~ ... Andreas
Bug#1036677: astra-toolbox: FTBFS with CUDA 12: ../build/linux/../../cuda/2d/par_bp.cu(36): error: texture is not a template
Source: astra-toolbox Version: 2.1.0-2 Severity: important Tags: ftbfs sid Justification: fails to build from source Control: block 1036676 with -1 ... /usr/bin/nvcc -Wno-deprecated-gpu-targets -gencode=arch=compute_50,code=sm_50 -gencode=arch=compute_60,code=sm_60 -gencode=arch=compute_70,code=sm_70 -gencode=arch=compute_75,code=sm_75 -gencode=arch=compute_80,code=sm_80 -gencode=arch=compute_86,code=sm_86 -gencode=arch=compute_86,code=compute_86 -I../build/linux/../../include -DASTRA_CUDA -c ../build/linux/../../cuda/2d/par_bp.cu -Xcompiler -fPIC -DPIC -o cuda/2d/.libs/par_bp.o ../build/linux/../../cuda/2d/par_bp.cu(36): error: texture is not a template 1 error detected in the compilation of "../build/linux/../../cuda/2d/par_bp.cu". make[2]: *** [Makefile:373: cuda/2d/par_bp.lo] Error 2 Andreas
Bug#1036676: transition: nvidia-cuda-toolkit 12
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition The switch from CUDA 11 to CUDA 12 seems to have bigger impact on the dependencies, thus I'm going to block this bug with the corresponding FTBFS bugs. (There are no binNMUs to be scheduled by the release team as nvidia-cuda-toolkit is in non-free.) First rebuild test with 12.0.0: FAILamd64 astra-toolbox/sid OK amd64 bart-cuda/sid FAILamd64 eztrace-contrib/sid OK amd64 hwloc-contrib/sid FAILamd64 magma/sid OK amd64 mumax3/sid OK amd64 nvidia-nccl/sid OK amd64 pycuda/sid FAILamd64 pyhst2/sid OK amd64 pyvkfft/sid FAILamd64 relion-cuda/sid FAILamd64 slurm-wlm-contrib/sid FAILamd64 starpu-contrib/sid FAILamd64 tomopy/sid Ben file: https://release.debian.org/transitions/html/auto-nvidia-cuda-toolkit.html (there are some more packages that B-D: nvidia-cuda-toolkit but have no library dependencies) Andreas
Bug#1036663: unblock: onetbb/2021.8.0-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package onetbb
(Please provide enough (but not too much) information to help
the release team to judge the request efficiently. E.g. by
filling in the sections below.)
[ Reason ]
For smooth upgrades from bullseye we need to make some transitive
conflicts explicit s.t. apt has better chances of finding the perfect
upgrade path.
[ Impact ]
Bad upgrade experience: partially incomplete upgrades.
[ Tests ]
Various piuparts upgrade scenarios tested locally
(testing all packages that (transitively) depend/recommend libtbb2 in bullseye)
Together with similar Breaks added in other packages upgrades look much
better now ;-)
[ Risks ]
Low. Only affects packages in bullseye and not in bookworm, i.e. that
should get removed on upgrades anyway.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
The libraries removed from the .symbols file have been moved to a
separate package long ago, so the symbols were only cruft.
unblock onetbb/2021.8.0-2
Andreas
diff --git a/debian/changelog b/debian/changelog
index 7aa18445..3adae56e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+onetbb (2021.8.0-2) unstable; urgency=medium
+
+ * Team upload.
+ * libtbb12: Add explicit Breaks against libtbb2 for smoother upgrades from
+bullseye. The the existing transitive Breaks via libtbbmalloc2 is not
+sufficient for all upgrade paths. (Closes: #1036073)
+ * Drop duplicate symbols.
+
+ -- Andreas Beckmann Tue, 16 May 2023 12:23:01 +0200
+
onetbb (2021.8.0-1) unstable; urgency=medium
* New upstream version 2021.8.0
diff --git a/debian/control b/debian/control
index 81ee5679..9f5dbeb1 100644
--- a/debian/control
+++ b/debian/control
@@ -48,6 +48,8 @@ Depends: libtbbmalloc2 (= ${binary:Version}),
${shlibs:Depends},
${misc:Depends}
Pre-Depends: ${misc:Pre-Depends}
+Breaks:
+ libtbb2 (<< 2021),
Description: parallelism library for C++ - runtime files
TBB is a library that helps you leverage multi-core processor
performance without having to be a threading expert. It represents a
diff --git a/debian/libtbb12.symbols.amd64 b/debian/libtbb12.symbols.amd64
index 45ef0404..6cc620f6 100644
--- a/debian/libtbb12.symbols.amd64
+++ b/debian/libtbb12.symbols.amd64
@@ -98,61 +98,3 @@ libtbb.so.12 libtbb12 #MINVER#
_ZTVN3tbb6detail2r110user_abortE@Base 2021.4.0
_ZTVN3tbb6detail2r112missing_waitE@Base 2021.4.0
_ZTVN3tbb6detail2r114bad_last_allocE@Base 2021.4.0
-libtbbmalloc.so.2 libtbb12 #MINVER#
- MallocInitializeITT@Base 2017~U7
- _ZN3rml10pool_msizeEPNS_10MemoryPoolEPv@Base 2019~U4
- _ZN3rml10pool_resetEPNS_10MemoryPoolE@Base 2017~U7
- _ZN3rml11pool_createElPKNS_13MemPoolPolicyE@Base 2017~U7
- _ZN3rml11pool_mallocEPNS_10MemoryPoolEm@Base 2017~U7
- _ZN3rml12pool_destroyEPNS_10MemoryPoolE@Base 2017~U7
- _ZN3rml12pool_reallocEPNS_10MemoryPoolEPvm@Base 2017~U7
- _ZN3rml13pool_identifyEPv@Base 2017~U7
- _ZN3rml14pool_create_v1ElPKNS_13MemPoolPolicyEPPNS_10MemoryPoolE@Base 2017~U7
- _ZN3rml19pool_aligned_mallocEPNS_10MemoryPoolEmm@Base 2017~U7
- _ZN3rml20pool_aligned_reallocEPNS_10MemoryPoolEPvmm@Base 2017~U7
- _ZN3rml9pool_freeEPNS_10MemoryPoolEPv@Base 2017~U7
- __TBB_malloc_safer_aligned_msize@Base 2017~U7
- __TBB_malloc_safer_aligned_realloc@Base 2017~U7
- __TBB_malloc_safer_free@Base 2017~U7
- __TBB_malloc_safer_msize@Base 2017~U7
- __TBB_malloc_safer_realloc@Base 2017~U7
- scalable_aligned_free@Base 2017~U7
- scalable_aligned_malloc@Base 2017~U7
- scalable_aligned_realloc@Base 2017~U7
- scalable_allocation_command@Base 2017~U7
- scalable_allocation_mode@Base 2017~U7
- scalable_calloc@Base 2017~U7
- scalable_free@Base 2017~U7
- scalable_malloc@Base 2017~U7
- scalable_msize@Base 2017~U7
- scalable_posix_memalign@Base 2017~U7
- scalable_realloc@Base 2017~U7
-libtbbmalloc_proxy.so.2 libtbb12 #MINVER#
- _ZdaPv@Base 2017~U7
- _ZdaPvRKSt9nothrow_t@Base 2017~U7
- _ZdlPv@Base 2017~U7
- _ZdlPvRKSt9nothrow_t@Base 2017~U7
- _Znam@Base 2017~U7
- _ZnamRKSt9nothrow_t@Base 2017~U7
- _Znwm@Base 2017~U7
- _ZnwmRKSt9nothrow_t@Base 2017~U7
- __TBB_malloc_proxy@Base 2017~U7
- __libc_calloc@Base 2017~U7
- __libc_free@Base 2017~U7
- __libc_malloc@Base 2017~U7
- __libc_memalign@Base 2017~U7
- __libc_pvalloc@Base 2017~U7
- __libc_realloc@Base 2017~U7
- __libc_valloc@Base 2017~U7
- aligned_alloc@Base 2017~U7
- calloc@Base 2017~U7
- free@Base 2017~U7
- mallinfo@Base 2017~U7
- malloc@Base 2017~U7
- malloc_usable_size@Base 2017~U7
- mallopt@Base 2017~U7
- memalign@Base 2017~U7
- posix_memalign@Base 2017~U7
- pvalloc@Base 2017~U7
- realloc@Base 2017~U7
- valloc@Base 2017~U7
Bug#1036653: libworkflow0: broken symlink: /usr/lib//libworkflow.so.0.10.6 -> libworkflow.so.0
Package: libworkflow0 Version: 0.10.6-1.1 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Control: found -1 0.10.5-1 Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink: 0m13.7s ERROR: FAIL: Broken symlinks: /usr/lib/x86_64-linux-gnu/libworkflow.so.0.10.6 -> libworkflow.so.0 (libworkflow0:amd64) The package does not ship the shared library at all, only the broken link. I haven't checked the source, but my guess is that the symlink gets created in the wrong direction (link source and target swapped), owerwriting the actual library. cheers, Andreas
Bug#1036641: gcc-12-base: please bump the Breaks: gnat (<< 12) for smoother upgrades from bullseye
Package: gcc-12-base Version: 12.2.0-14 Severity: serious User: debian...@lists.debian.org Usertags: piuparts As usual, it is helpful to bump the Breaks against gnat (which is not co-installable) for smoother upgrades from bullseye to ensure the obsolete gnat-10 stack gets removed. Andreas
Bug#1036639: libost-base2.3: please add Breaks: libost-base2.2 for smoother upgrades from bullseye
Package: libost-base2.3
Version: 2.3.1-8
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
the openstructure library stacks from bullseye and bookworm are not
co-installable due to a transitive dependency conflict on
libboost-regex1.74.0-icu67 which is a virtual package provided by
libboost-regex1.74.0 in bullseye only, while the bookworm version
provides libboost-regex1.74.0-icu72. This is hard for apt to figure out
correctly and on some upgrade paths apt prefers to keep the obsolete
library stack installed instead of replacng it with the new one.
Adding a Breaks to the base package which is at the top of the
dependency tree helps apt making the right choice: removing the old
library stack s.t. it can upgrade libboost-regex1.74.0.
Please consider applying the attached patch.
Andreas
>From 69fc50fdf3bdc26ed5152a7d6ec3c264e279c143 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Tue, 23 May 2023 18:38:19 +0200
Subject: [PATCH] libost-base2.3: add Breaks: libost-base2.2 for smoother
upgrades from bullseye
---
debian/changelog | 7 +++
debian/control | 2 ++
2 files changed, 9 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index eda78fd..e6970ac 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+openstructure (2.3.1-9) UNRELEASED; urgency=medium
+
+ * libost-base2.3: Add Breaks: libost-base2.2 for smoother upgrades from
+bullseye. (Closes: #)
+
+ -- Andreas Beckmann Tue, 23 May 2023 18:37:03 +0200
+
openstructure (2.3.1-8) unstable; urgency=medium
* Install shlibs into multiarch locations using debian/rules.
diff --git a/debian/control b/debian/control
index f7340ea..310d73b 100644
--- a/debian/control
+++ b/debian/control
@@ -41,6 +41,8 @@ Section: libs
Depends:
${misc:Depends},
${shlibs:Depends},
+Breaks:
+ libost-base2.2,
Description: Open-Source Computational Structural Biology Framework
OpenStructure aims to provide an open-source, modular, flexible, molecular
modelling and visualization environment. It is targeted at interested method
--
2.20.1
Bug#1035920: cloud-initramfs-growroot: /usr/share/initramfs-tools/hooks/growroot fails in non-merged-/usr environment: expects /usr/bin/udevadm
Followup-For: Bug #1035920 Control: tag -1 patch The attached patch seems to fix this issue. The canonical path for udevadm in the udev package has been /bin/udevadm since jessie. Andreas >From b7839503f56aee1252b268401421fb90a69d5456 Mon Sep 17 00:00:00 2001 From: Andreas Beckmann Date: Tue, 23 May 2023 00:56:50 +0200 Subject: [PATCH] fix copy_exec /bin/udevadm /sbin --- debian/changelog| 6 ++ growroot/hooks/growroot | 2 +- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/debian/changelog b/debian/changelog index c1720fa..d4e2fd8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +cloud-initramfs-tools (0.18.debian13) UNRELEASED; urgency=medium + + * Fix copy_exec /bin/udevadm /sbin (Closes: #1035920). + + -- Andreas Beckmann Tue, 23 May 2023 00:54:39 +0200 + cloud-initramfs-tools (0.18.debian12) unstable; urgency=medium [ Martin Pitt ] diff --git a/growroot/hooks/growroot b/growroot/hooks/growroot index 5d06aa8..a8ee1ab 100644 --- a/growroot/hooks/growroot +++ b/growroot/hooks/growroot @@ -11,7 +11,7 @@ esac ## copy_exec /sbin/sfdisk /sbin copy_exec /usr/bin/growpart /sbin -copy_exec /usr/bin/udevadm /sbin +copy_exec /bin/udevadm /sbin copy_exec /usr/bin/flock /bin # vi: ts=4 noexpandtab -- 2.20.1
Bug#1036616: osmo-ggsn: broken symlink: /etc/osmocom/osmo-ggsn.cfg -> ../doc/examples/osmo-ggsn.cfg
Package: osmo-ggsn Version: 1.9.0-3 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink: 0m16.7s ERROR: FAIL: Broken symlinks: /etc/osmocom/osmo-ggsn.cfg -> ../doc/examples/osmo-ggsn.cfg (osmo-ggsn) Shouldn't that rather be a conffile than a symlink into documentation? cheers, Andreas
Bug#1036614: python3-lldb-15: broken symlinks: /usr/lib/llvm-15/lib/python3.11/dist-packages/lldb/_lldb.cpython-311-x86_64-linux-gnu.so, /usr/lib/llvm-15/lib/python3/dist-packages/lldb/libLLVM-15.so.1
Package: python3-lldb-15 Version: 1:15.0.6-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) broken symlinks: 0m35.3s ERROR: FAIL: Broken symlinks: /usr/lib/llvm-15/lib/python3.11/dist-packages/lldb/_lldb.cpython-311-x86_64-linux-gnu.so -> ../../../../../lib/liblldb.so (python3-lldb-15) /usr/lib/llvm-15/lib/python3.11/dist-packages/lldb/lldb-argdumper -> ../../../../../bin/lldb-argdumper (python3-lldb-15) /usr/lib/llvm-15/lib/python3/dist-packages/lldb/libLLVM-15.0.6.so.1 -> ../../../../../x86_64-linux-gnu/libLLVM-15.0.6.so.1 (python3-lldb-15) /usr/lib/llvm-15/lib/python3/dist-packages/lldb/libLLVM-15.so.1 -> ../../../../../x86_64-linux-gnu/libLLVM-15.0.6.so.1 (python3-lldb-15) lldb-argdumper has one level of '..' too much, otherwise it could be found. The correct target for libLLVM-15.0.6.so.1 would be /usr/lib//libLLVM-15.so.1 and _lldb.cpython-311-.so should be linked to /usr/lib/llvm-15/lib/python3/dist-packages/lldb/_lldb.so or /usr/lib//liblldb-15.so.1 cheers, Andreas
Bug#1036611: python3-lldb-13: broken symlinks: /usr/lib/llvm-13/lib/python3/dist-packages/lldb/libLLVM-13*.so.1 -> ../../../../..//libLLVM-13.0.1.so.1
Package: python3-lldb-13 Version: 1:13.0.1-11 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) broken symlinks: 0m38.1s ERROR: FAIL: Broken symlinks: /usr/lib/llvm-13/lib/python3/dist-packages/lldb/libLLVM-13.0.1.so.1 -> ../../../../../x86_64-linux-gnu/libLLVM-13.0.1.so.1 (python3-lldb-13) /usr/lib/llvm-13/lib/python3/dist-packages/lldb/libLLVM-13.so.1 -> ../../../../../x86_64-linux-gnu/libLLVM-13.0.1.so.1 (python3-lldb-13) The correct target would be /usr/lib//libLLVM-13.so.1 cheers, Andreas
