Bug#1040513: wireplumber: non-installable due to hardcoded Depends: dbus-user-session
Package: wireplumber Version: 0.4.14-3 Severity: grave Hi! In version 0.4.14-3, you added a hard dependency on a specific session model of dbus, rather than the virtual package defined by the Policy (dbus-session-bus). This makes it non-installable on any box where a dependency of that package is non-functional or unwanted. As of policy 4.3.0, the expected dependency is: default-dbus-session-bus | dbus-session-bus We have two implementations of in Debian: * dbus-user-session: + works with wayland - no multiseat support - requires systemd * dbus-x11 - requires x11 + allows multiple sessions + portable even to non-linux I confirm that, as of 0.4.14-2 wireplumber works well with dbus-x11, and earlier versions did so for quite a while too. Meow! -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (120, 'experimental'), (1, 'experimental-debug') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.2-00035-g5920c330f094 (SMP w/64 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages wireplumber depends on: ii init-system-helpers 1.65.2 ii libc6 2.37-4 ii libglib2.0-0 2.74.6-2 ii libpipewire-0.3-0 0.3.73-1 ii libwireplumber-0.4-0 0.4.14-2 ii pipewire 0.3.73-1 Versions of packages wireplumber recommends: ii pipewire-pulse 0.3.73-1 Versions of packages wireplumber suggests: pn libspa-0.2-bluetooth pn wireplumber-doc -- no debconf information
Bug#1036424: sylpheed: replying to an email you sent doesn't set account accordingly
On Wed, 14 Jun 2023 16:00:12 +0900 Hideki Yamane wrote: [...] > As I wrote in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036388, > please describe your environment and reproducible way step by step. Hello, I am another user of Sylpheed (in Debian). Personally, I can reproduce the reported issue, but with a difference. In order to reproduce, configure at least two e-mail accounts in Sylpheed. Let's call them: * Albert AtWork * Bert BeachBum Let's say that "Albert AtWork" is the default account. Send an e-mail message from "Bert BeachBum" to your friend "Frank Friend". Now reply to your own e-mail message, with the intent to write again from "Bert BeachBum" to "Frank Friend". The original bug reporter claims that the reply is prepared from the default account "Albert AtWork", instead of from the previously used account "Bert BeachBum". What I experience personally, is that the reply is prepared from the currently selected account (not necessarily from the default account). If you select "Bert BeachBum" (menu entry 'Configuration' → 'Change current account'), and then use the 'Reply' command, the reply will be prepared from "Bert BeachBum", as intended. On the other hand, if you select "Albert AtWork" as current account, the reply will be prepared from "Albert AtWork". Well, this may make sense, after all. If I have selected an account as current, I mean that I want to send e-mail messages from that account. On the other hand, when I reply to an e-mail message sent to one of my accounts (for instance from "Frank Friend" to "Bert BeachBum"), that account is automatically selected, when I use the 'Reply' command, even if it was not the current account. Hence, what the original bug reporter is asking may be considered as useful feature. But I would not consider it as a bug of severity "grave". Maybe the severity should be set to "important" or "normal", or even "wishlist"... I hope this helps. Bye! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpi5shkhV12V.pgp Description: PGP signature
Bug#1040507: golang-1.21-go: downloads and runs binaries from the Internet without permission
Package: golang-1.21-go Version: 1.21~rc2-2 Severity: grave Tags: security Go 1.21 provides the `GOTOOLCHAIN` environment variable and associated functionality[0]. As part of this code, if go.mod indicates that a newer version of Go is required than the current toolchain supports, it proceeds by default to attempt to download a toolchain from the Internet and runs it without prompting the user. It is unclear what, if any cryptographic verification it performs, especially if the user has disabled GOPROXY and GOSUMDB for privacy reasons. As far as I know, the Go core team does not sign Linux binaries cryptographically, so at best the data would be verified by a hash, which is not sufficient. Debian itself uses a strong cryptographic signature for APT archives. In addition, it's possible that a newer version of the toolchain might contain some vulnerability which is not present in the current toolchain, and therefore might expose the user to new vulnerabilities that are not patched. This is not at all far-fetched, since Go is known to have regressions all the time, so security-based regressions are not at all out of the question. I don't believe this is an appropriate way for software distributed in Debian to behave, especially by default, and I'd like to request that it be patched out for security reasons. Steps to reproduce: 1. Clone a Go project (e.g., Git LFS). 2. Update go.mod to state "go 1.22". 3. Run /usr/lib/go-1.21/bin/go build 4. Notice the following output: go: downloading go1.22 (linux/amd64) go: download go1.22 for linux/amd64: toolchain not available [0] https://tip.golang.org/doc/toolchain -- System Information: Debian Release: trixie/sid APT prefers oldstable-security APT policy: (500, 'oldstable-security'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.3.0-1-amd64 (SMP w/20 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER, TAINT_WARN Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages golang-1.21-go depends on: ii golang-1.21-src 1.21~rc2-2 Versions of packages golang-1.21-go recommends: ii g++ 4:12.3.0-1 ii gcc 4:12.3.0-1 ii libc6-dev 2.37-3 ii pkg-config1.8.1-1 ii pkgconf [pkg-config] 1.8.1-1 Versions of packages golang-1.21-go suggests: pn bzr | brz ii ca-certificates 20230311 ii git 1:2.40.1+next.20230427-1 pn mercurial pn subversion -- no debconf information -- brian m. carlson (he/him or they/them) Toronto, Ontario, CA signature.asc Description: PGP signature
Processed: update bug meta info
Processing commands for cont...@bugs.debian.org:
> # r-cran-pammtools took "ownership"
> reassign 1039510 src:r-cran-pammtools 0.5.8-1
Bug #1039510 {Done: Andreas Tille } [src:mvtnorm,
src:r-cran-pammtools] mvtnorm breaks r-cran-pammtools autopkgtest: missing
Breaks and/or versioned (test) Depends?
Bug reassigned from package 'src:mvtnorm, src:r-cran-pammtools' to
'src:r-cran-pammtools'.
No longer marked as found in versions r-cran-pammtools/0.5.8-1 and
mvtnorm/1.2-2-1.
No longer marked as fixed in versions r-cran-pammtools/0.5.91-3.
Bug #1039510 {Done: Andreas Tille } [src:r-cran-pammtools]
mvtnorm breaks r-cran-pammtools autopkgtest: missing Breaks and/or versioned
(test) Depends?
Marked as found in versions r-cran-pammtools/0.5.8-1.
> fixed 1039510 0.5.91-3
Bug #1039510 {Done: Andreas Tille } [src:r-cran-pammtools]
mvtnorm breaks r-cran-pammtools autopkgtest: missing Breaks and/or versioned
(test) Depends?
The source 'r-cran-pammtools' and version '0.5.91-3' do not appear to match any
binary packages
Marked as fixed in versions r-cran-pammtools/0.5.91-3.
> affects 1039510 src:r-cran-mvtnorm
Bug #1039510 {Done: Andreas Tille } [src:r-cran-pammtools]
mvtnorm breaks r-cran-pammtools autopkgtest: missing Breaks and/or versioned
(test) Depends?
Added indication that 1039510 affects src:r-cran-mvtnorm
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1039510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1040479: 104079: devices from extern FC-Raid only map if the have no partitions
Package: multipath-tools Version: 0.9.4-3+deb12u1 Severity: critical Tags: upstream Justification: breaks unrelated software X-Debbugs-Cc:t...@security.debian.org Hallo Chris, if the device has _one_ partition Version: 0.9.4-3+deb12u1 solve the problem, but if it has multiple partitions the problem stay. with regards On Thu, 6 Jul 2023 15:18:52 +0200 Chris Hofstaedtler wrote: > Version: 0.9.4-3+deb12u1 > > Should be the same as #1037539, already fixed in deb12u1. > > > > -- Dipl.-Phys. Andreas Matthus Netzwerkadministrator Technische Universität Dresden Fakultät Architektur 01062 Dresden Tel.: +49 (351) 463-33909 Fax: +49 (351) 463-36120 E-Mail:andreas.matt...@tu-dresden.de smime.p7s Description: S/MIME Cryptographic Signature
Processed: [bts-link] source package src:kjs
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:kjs > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1000115 (http://bugs.debian.org/1000115) > # Bug title: kjs: depends on obsolete pcre3 library > # * http://bugs.kde.org/show_bug.cgi?id=457338 > # * remote status changed: UNCONFIRMED -> RESOLVED > # * remote resolution changed: (?) -> UNMAINTAINED > # * closed upstream > tags 1000115 + fixed-upstream Bug #1000115 [src:kjs] kjs: depends on obsolete pcre3 library Bug #1000112 [src:kjs] kjs: depends on obsolete pcre3 library Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. > usertags 1000115 - status-UNCONFIRMED Usertags were: status-UNCONFIRMED. There are now no usertags set. > usertags 1000115 + status-RESOLVED resolution-UNMAINTAINED There were no usertags set. Usertags are now: resolution-UNMAINTAINED status-RESOLVED. > # remote status report for #1000115 (http://bugs.debian.org/1000115) > # Bug title: kjs: depends on obsolete pcre3 library > # * http://bugs.kde.org/show_bug.cgi?id=457338 > # * remote status changed: UNCONFIRMED -> RESOLVED > # * remote resolution changed: (?) -> UNMAINTAINED > # * closed upstream > tags 1000115 + fixed-upstream Bug #1000115 [src:kjs] kjs: depends on obsolete pcre3 library Bug #1000112 [src:kjs] kjs: depends on obsolete pcre3 library Ignoring request to alter tags of bug #1000115 to the same tags previously set Ignoring request to alter tags of bug #1000112 to the same tags previously set > usertags 1000115 - status-UNCONFIRMED Usertags were: resolution-UNMAINTAINED status-RESOLVED. Usertags are now: resolution-UNMAINTAINED status-RESOLVED. > usertags 1000115 + status-RESOLVED resolution-UNMAINTAINED Usertags were: status-RESOLVED resolution-UNMAINTAINED. Usertags are now: status-RESOLVED resolution-UNMAINTAINED. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000112 1000115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000115 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040496: qt6-virtualkeyboard FTBFS with parallel=1: qmlcachegen segfaults
Source: qt6-virtualkeyboard Version: 6.4.2+dfsg-2 Severity: serious Tags: ftbfs qt6-virtualkeyboard fails to build from source in unstable when passing DEB_BUILD_OPTIONS=parallel=1. A build ends as follows: | [110/301] cd /<>/obj-x86_64-linux-gnu/src/components && /usr/bin/cmake -E make_directory /<>/obj-x86_64-linux-gnu/src/components/.rcc/qmlcache && /usr/lib/qt6/libexec/qmlcachegen --bare --resource-path /qt-project.org/imports/QtQuick/VirtualKeyboard/Components/Keyboard.qml -I /<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/qt6/qml -I /usr/lib/x86_64-linux-gnu/qt6/qml -i /<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/qt6/qml/QtQuick/VirtualKeyboard/Components/qmldir --resource /<>/obj-x86_64-linux-gnu/src/components/.rcc/qmake_QtQuick_VirtualKeyboard_Components.qrc --resource /<>/obj-x86_64-linux-gnu/src/components/.rcc/qtvkbcomponentsplugin_raw_qml_0.qrc -o /<>/obj-x86_64-linux-gnu/src/components/.rcc/qmlcache/qtvkbcomponentsplugin_Keyboard_qml.cpp /<>/src/components/Keyboard.qml | FAILED: src/components/.rcc/qmlcache/qtvkbcomponentsplugin_Keyboard_qml.cpp /<>/obj-x86_64-linux-gnu/src/components/.rcc/qmlcache/qtvkbcomponentsplugin_Keyboard_qml.cpp | cd /<>/obj-x86_64-linux-gnu/src/components && /usr/bin/cmake -E make_directory /<>/obj-x86_64-linux-gnu/src/components/.rcc/qmlcache && /usr/lib/qt6/libexec/qmlcachegen --bare --resource-path /qt-project.org/imports/QtQuick/VirtualKeyboard/Components/Keyboard.qml -I /<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/qt6/qml -I /usr/lib/x86_64-linux-gnu/qt6/qml -i /<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/qt6/qml/QtQuick/VirtualKeyboard/Components/qmldir --resource /<>/obj-x86_64-linux-gnu/src/components/.rcc/qmake_QtQuick_VirtualKeyboard_Components.qrc --resource /<>/obj-x86_64-linux-gnu/src/components/.rcc/qtvkbcomponentsplugin_raw_qml_0.qrc -o /<>/obj-x86_64-linux-gnu/src/components/.rcc/qmlcache/qtvkbcomponentsplugin_Keyboard_qml.cpp /<>/src/components/Keyboard.qml | Segmentation fault (core dumped) | ninja: build stopped: subcommand failed. | dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 -v returned exit code 1 | make: *** [debian/rules:12: binary] Error 25 | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 This originally was a cross build failure, but it also reproduces natively. Therefore, I know that it also fails on an arm64 machine. In all of my testing, all parallel=1 builds reliably failed while all builds that weren't parallel=1 succeeded (cross or native). This is not necessarily a bug in qt6-virtualkeyboard itself. I'll leave it up to you to reassign as necessary. Helmut
Processed: force merge duplicate bugs
Processing commands for cont...@bugs.debian.org: > reassign 1037467 src:ruby-gollum-lib Bug #1037467 [ruby-gollum-lib] ruby-gollum-lib not compatible with ruby-rouge 4.1 Bug reassigned from package 'ruby-gollum-lib' to 'src:ruby-gollum-lib'. No longer marked as found in versions ruby-gollum-lib/4.2.7.10~gitlab.2+dfsg-1. Ignoring request to alter fixed versions of bug #1037467 to the same values previously set > forcemerge 1040405 1037467 Bug #1040405 [src:ruby-gollum-lib] ruby-gollum-lib: incompatible with newer ruby-rouge Bug #1037467 [src:ruby-gollum-lib] ruby-gollum-lib not compatible with ruby-rouge 4.1 Severity set to 'serious' from 'important' 1037467 was not blocked by any bugs. 1037467 was not blocking any bugs. Added blocking bug(s) of 1037467: 1040461 Marked as found in versions ruby-gollum-lib/4.2.7.10~gitlab.2+dfsg-1. Merged 1037467 1040405 > thanks Stopping processing here. Please contact me if you need assistance. -- 1037467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037467 1040405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1039920: marked as done (ruby-browser: autopkgtest regression: No such file or directory @ rb_sysopen - /usr/share/rubygems-integration/all/gems/browser-5.3.1/test/ua.yml)
Your message dated Thu, 06 Jul 2023 17:19:34 + with message-id and subject line Bug#1039920: fixed in ruby-browser 5.3.1-3 has caused the Debian Bug report #1039920, regarding ruby-browser: autopkgtest regression: No such file or directory @ rb_sysopen - /usr/share/rubygems-integration/all/gems/browser-5.3.1/test/ua.yml to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1039920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-browser Version: 5.3.1-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of ruby-browser the autopkgtest of ruby-browser fails in testing when that autopkgtest is run with the binary packages of ruby-browser from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-browser from testing5.3.1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=ruby-browser https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-browser/34928920/log.gz 32s 32s ┌──┐ 32s │ Checking Rubygems dependency resolution on ruby3.1 │ 32s └──┘ 32s 32s GEM_PATH= ruby3.1 -e gem\ \"browser\" 32s 32s ┌──┐ 32s │ Run tests for ruby3.1 from debian/ruby-tests.rake │ 32s └──┘ 32s 32s RUBYLIB=. GEM_PATH= ruby3.1 -S rake -f debian/ruby-tests.rake 32s mv lib ./.gem2deb.lib 32s /usr/bin/ruby3.1 -w -I"lib:lib:test" /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb "test/browser_test.rb" "test/middleware_test.rb" "test/rails_test.rb" 33s /usr/share/rubygems-integration/all/gems/activesupport-6.1.7.3/lib/active_support/core_ext/class/subclasses.rb:30: warning: method redefined; discarding old subclasses 33s /usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/nokogiri-1.13.10/lib/nokogiri/version/info.rb:85: warning: possibly useless use of a variable in void context 33s Run options: --seed 27888 33s 33s # Running: 33s 33s .E..E.E.EE...EE.E.EE.. 33s 33s1) detects meta aliased as to a 33s Errno::ENOENT: No such file or directory @ rb_sysopen - /usr/share/rubygems-integration/all/gems/browser-5.3.1/test/ua.yml 33s # test/browser_test.rb:144 33s 33s2) removes duplicate items 33s Errno::ENOENT: No such file or directory @ rb_sysopen - /usr/share/rubygems-integration/all/gems/browser-5.3.1/test/ua.yml 33s # test/browser_test.rb:139 33s 33s3) detects core media 33s Errno::ENOENT: No such file or directory @ rb_sysopen - /usr/share/rubygems-integration/all/gems/browser-5.3.1/test/ua.yml 33s # test/browser_test.rb:78 33s 33s4) detects android tablet 33s Errno::ENOENT: No such file or directory @ rb_sysopen - /usr/share/rubygems-integration/all/gems/browser-5.3.1/test/ua.yml 33s # test/browser_test.rb:47 33s 33s5) detects phantom.js 33s Errno::ENOENT: No such file or directory @ rb_sysopen - /usr/share/rubygems-integration/all/gems/browser-5.3.1/test/ua.yml 33s # test/browser_test.rb:88 33s 33s6) detects android 33s Errno::ENOENT: No such file or directory @ rb_sysopen - /usr/share/rubygems-integration/all/gems/browser-5.3.1/test/ua.yml 33s # test/browser_test.rb:36 33s 33s7) detects quicktime 33s Errno::ENOENT: No such file or directory @ rb_sysopen - /usr/share/rubygems-integration/all/gems/browser-5.3.1/test/ua.yml 33s # test/browser_test.rb:68 33s 33s8) detects surface tablet 33s Errno::ENOENT: No such file or directory @ rb_sysopen - /usr/share/rubygems-integration/all/gems/browser-5.3.1/test/ua.yml 33s # test/browser_test.rb:58 33s 33s9) renders json 33s Errno::ENOENT: No such file or directory @ rb_sysopen -
Processed (with 1 error): force merge duplicate bugs
Processing commands for cont...@bugs.debian.org: > forcemerge 1040405 1037467 Bug #1040405 [src:ruby-gollum-lib] ruby-gollum-lib: incompatible with newer ruby-rouge Unable to merge bugs because: package of #1037467 is 'ruby-gollum-lib' not 'src:ruby-gollum-lib' Failed to forcibly merge 1040405: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037467 1040405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1026433, tagging 1038641, found 1038641 in 1.8.2-1
Processing commands for cont...@bugs.debian.org: > tags 1026433 + sid trixie Bug #1026433 [src:mercurial-buildpackage] RM: mercurial-buildpackage -- RoQA; no users left Added tag(s) trixie and sid. > tags 1038641 + sid trixie Bug #1038641 [src:ganv] RM: ganv -- RoQA; depends on gtk2 Added tag(s) sid and trixie. > found 1038641 1.8.2-1 Bug #1038641 [src:ganv] RM: ganv -- RoQA; depends on gtk2 Marked as found in versions ganv/1.8.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026433 1038641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1032071: ARM firmware packages included in amd64 installation images
Processing control commands: > severity 1035382 grave Bug #1035382 [debian-live] Bookworm amd64 live install ISO RC1 and RC2 install pointless raspi-firmware package Ignoring request to change severity of Bug 1035382 to the same value. -- 1035382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035382: Bug#1032071: ARM firmware packages included in amd64 installation images
Control: severity 1035382 grave On Thu, Jul 06, 2023 at 06:29:49PM +0200, Magnus Wallin wrote: > >Hi Magnus, and thanks for the heads-up > >[ . . . ] > >Just because the raspi-firmware package is included on the d-i >installation media, it shouldn't necessarily be installed on an amd64 >host. Or is this coming from live images? > >Hi Steve! > >Speaking for myself: I installed from a live image on the release day of Debian >12. OK, that explains it. Let's try to get this fixed before 12.1... I can see that there is already #1035382 open on the live side, let's bump the severity on that. -- Steve McIntyre, Cambridge, UK.st...@einval.com “Why do people find DNS so difficult? It’s just cache invalidation and naming things.” -– Jeff Waugh (https://twitter.com/jdub)
Processed: Re: Bug#1032071: ARM firmware packages included in amd64 installation images
Processing control commands: > severity 1035382 grave Bug #1035382 [debian-live] Bookworm amd64 live install ISO RC1 and RC2 install pointless raspi-firmware package Severity set to 'grave' from 'normal' -- 1032071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032071 1035382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040438: marked as done (libmail-dkim-perl: missing dependency on libgetopt-long-descriptive-perl)
Your message dated Thu, 06 Jul 2023 16:04:21 + with message-id and subject line Bug#1040438: fixed in libmail-dkim-perl 1.20230212-2 has caused the Debian Bug report #1040438, regarding libmail-dkim-perl: missing dependency on libgetopt-long-descriptive-perl to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1040438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmail-dkim-perl Version: 1.20230212-1 Severity: serious Justification: Policy 3.5 $ dkimproxy-verify Can't locate Getopt/Long/Descriptive.pm in @INC (you may need to install the Getopt::Long::Descriptive module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl) at /usr/bin/dkimproxy-verify line 13. BEGIN failed--compilation aborted at /usr/bin/dkimproxy-verify line 13. Installing libgetopt-long-descriptive-perl fixes it, but this should clearly be in Depends. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-8-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libmail-dkim-perl depends on: ii libcrypt-openssl-rsa-perl 0.33-3+b1 ii liberror-perl 0.17029-2 ii libmail-authenticationresults-perl 2.20230112-1 ii libmailtools-perl 2.21-2 ii libnet-dns-perl 1.36-1 ii perl [libdigest-sha-perl] 5.36.0-7 libmail-dkim-perl recommends no packages. libmail-dkim-perl suggests no packages. -- no debconf information Thanks, -- Colin Watson (he/him) [cjwat...@debian.org] --- End Message --- --- Begin Message --- Source: libmail-dkim-perl Source-Version: 1.20230212-2 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libmail-dkim-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libmail-dkim-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 06 Jul 2023 17:38:48 +0200 Source: libmail-dkim-perl Architecture: source Version: 1.20230212-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 1040438 Changes: libmail-dkim-perl (1.20230212-2) unstable; urgency=medium . * Team upload. * Add scripts to autopkgtest's syntax.t. Cf. #1040438. * Add a runtime dependency on libgetopt-long-descriptive-perl. Thanks to Colin Watson for the bug report. (Closes: #1040438) Checksums-Sha1: 76c48f244e4e4f2f1d0843f0fa3b76675c343b81 2707 libmail-dkim-perl_1.20230212-2.dsc a4dd04372a7f27437ff84060b794fd7429dd1cc4 5680 libmail-dkim-perl_1.20230212-2.debian.tar.xz Checksums-Sha256: 6e404469f9dbc51a1005b2cf0491e8faafca9fdf8152947dd7e3208c08fa7eb8 2707 libmail-dkim-perl_1.20230212-2.dsc edfdeacf8f21616c4f70ddd938da62b7e82d8ccc7a9fd678d06254ec7d2562cc 5680 libmail-dkim-perl_1.20230212-2.debian.tar.xz Files: 48bed0e67ce24672829c1c425d5bbc76 2707 perl optional libmail-dkim-perl_1.20230212-2.dsc ffc9c7ebd580a53629b921c29f8379c9 5680 perl optional libmail-dkim-perl_1.20230212-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmSm4JpfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgaOYg/+Lh1RlF+eESbhT8aci1fuO2oeBN3j9xFWq9eIysCv5hi6HL0HzlAVFoWy
Processed: found 1040438 in 1.20220520-1
Processing commands for cont...@bugs.debian.org: > found 1040438 1.20220520-1 Bug #1040438 [libmail-dkim-perl] libmail-dkim-perl: missing dependency on libgetopt-long-descriptive-perl Marked as found in versions libmail-dkim-perl/1.20220520-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040477: [Pkg-rust-maintainers] Bug#1040477: librust-syn-1-dev fails to coinstall
I'd be very interested in knowing what this self-conflict is supposed to achieve. It is common upstream for there to be multiple semver-incompatible versions of each rust crate in use at a given time. Incompatibilities can range from minor corner cases that are easily patched away to complete redesigns We try to only package one version of each crate at a time, but sometimes that isn't practical. When it becomes impractical we crate semver-suffix packages. The convention in the rust team is that the un-suffixed packages are used for the latest version and suffixed versions are used for any older versions. When packaged crates are installed on a Debian system. They are installed in a path that depends on the upstream version of a crate. This creates a problem though, if the same version is packaged as both a non-suffixed and suffixed version. Something that happens fairly frequently when a new version is introduced e.g. Before: librust-foo-dev version 1.23-1 After: librust-foo-1-dev version 1.23-2 librust-foo-dev version 2.34-1 This doesn't always happen, indeed it didn't happen in the case of syn, because a new upstream release of syn 1.x at the same time at the same time the semver suffix was introduced. However debcargo works on one crate at a time. so it doesn't know if this has happened or not. When this happens, it leads to a file conflict. In an attempt to fix this breaks+replaces were added. Unfortunately these proved to be insufficient because while breaks against virtual packages work, replaces apparently don't. We are in the process of considering several options to fix this, but overall switching to conflicts+replaces seems the least likely to be problematic. Do you encounter the same problem if you replace the breaks with conflicts? if so we would need to do something about it. I think the easiest would probablly be to put a version constraint on the conflicts/replaces. It would mean we would have to take care that semver-suffixed packages had a higher Debian revision than their un-suffixed counterparts, but I think that is managable.
Bug#1040451: marked as done (schleuder: incompatible with newer ruby-mail)
Your message dated Thu, 6 Jul 2023 17:29:33 +0200 with message-id and subject line Re: schleuder: incompatible with newer ruby-mail has caused the Debian Bug report #1040451, regarding schleuder: incompatible with newer ruby-mail to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1040451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: schleuder Version: 4.0.3-9 Severity: serious Hello, the last ruby-mail upload broke this package autopkgtests, please see e.g. 340s GEM_PATH= ruby3.1 -e gem\ \"schleuder\" 340s /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'mail' (~> 2.7.1) among 126 total gem(s) (Gem::MissingSpecError) 340s Checked in 'GEM_PATH=/root/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/arm-linux-gnueabihf/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/arm-linux-gnueabihf/rubygems-integration/3.1.0' at: /usr/share/rubygems-integration/all/specifications/schleuder-4.0.3.gemspec, execute `gem env` for more information 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block in activate_dependencies' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `activate_dependencies' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in `activate' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem' 340sfrom -e:1:in `' 340s /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not find 'mail' (~> 2.7.1) - did find: [mail-2.8.1] (Gem::MissingSpecVersionError) 340s Checked in 'GEM_PATH=/root/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/arm-linux-gnueabihf/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/arm-linux-gnueabihf/rubygems-integration/3.1.0' , execute `gem env` for more information 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1411:in `block in activate_dependencies' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `activate_dependencies' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in `activate' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem' 340sfrom -e:1:in `' 340s abbrev (default: 0.1.0) 340s activemodel (6.1.7.3) Can you please have a look? thanks Gianfranco OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- For some reasons they pass now. Closing G. On Thu, 6 Jul 2023 07:06:38 +0200 Gianfranco Costamagna wrote: Source: schleuder Version: 4.0.3-9 Severity: serious Hello, the last ruby-mail upload broke this package autopkgtests, please see e.g. 340s GEM_PATH= ruby3.1 -e gem\ \"schleuder\" 340s /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in `rescue in block in activate_dependencies': Could not find 'mail' (~> 2.7.1) among 126 total gem(s) (Gem::MissingSpecError) 340s Checked in 'GEM_PATH=/root/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/arm-linux-gnueabihf/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/arm-linux-gnueabihf/rubygems-integration/3.1.0' at: /usr/share/rubygems-integration/all/specifications/schleuder-4.0.3.gemspec, execute `gem env` for more information 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1410:in `block in activate_dependencies' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `activate_dependencies' 340sfrom /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in `activate' 340sfrom
Bug#1039510: marked as done (mvtnorm breaks r-cran-pammtools autopkgtest: missing Breaks and/or versioned (test) Depends?)
Your message dated Thu, 06 Jul 2023 15:19:57 +
with message-id
and subject line Bug#1039510: fixed in r-cran-pammtools 0.5.91-3
has caused the Debian Bug report #1039510,
regarding mvtnorm breaks r-cran-pammtools autopkgtest: missing Breaks and/or
versioned (test) Depends?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mvtnorm, r-cran-pammtools
Control: found -1 mvtnorm/1.2-2-1
Control: found -1 r-cran-pammtools/0.5.8-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of mvtnorm the autopkgtest of r-cran-pammtools
fails in testing when that autopkgtest is run with the binary packages
of mvtnorm from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
mvtnormfrom testing1.2-2-1
r-cran-pammtools from testing0.5.8-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing
I note that with both versions from unstable the test also passes, which
hints at either a missing *versioned* test dependency in
r-cran-pammtools (if it *only* breaks the test), or missing versioned
Breaks in mvtnorm *and* a missing versioned Depends in r-cran-pammtools
if r-cran-pammtools is really broken with the wrong version of mvtnorm.
I copied some of the output at the bottom of this report.
Currently this regression is blocking both the migration of mvtnorm to
testing [1] and the migration of r-cran-pammtools to testing [2]. Due to
the nature of this issue, I filed this bug report against both packages.
Can you please investigate the situation and reassign the bug to the
right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
mvtnorm/1.2-2-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=mvtnorm
[2] https://qa.debian.org/excuses.php?package=r-cran-pammtools
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-pammtools/34886689/log.gz
46s BEGIN TEST testthat.R
46s 46s R version 4.3.1 (2023-06-16) -- "Beagle Scouts"
46s Copyright (C) 2023 The R Foundation for Statistical Computing
46s Platform: x86_64-pc-linux-gnu (64-bit)
46s 46s R is free software and comes with ABSOLUTELY NO WARRANTY.
46s You are welcome to redistribute it under certain conditions.
46s Type 'license()' or 'licence()' for distribution details.
46s 46s R is a collaborative project with many contributors.
46s Type 'contributors()' for more information and
46s 'citation()' on how to cite R or R packages in publications.
46s 46s Type 'demo()' for some demos, 'help()' for on-line help, or
46s 'help.start()' for an HTML browser interface to help.
46s Type 'q()' to quit R.
46s 46s > Sys.setenv("R_TESTS" = "") # see
https://github.com/hadley/testthat/issues/86
46s > library(testthat)
46s > library(checkmate)
46s > library(dplyr)
47s 47s Attaching package: ‘dplyr’
47s 47s The following object is masked from ‘package:testthat’:
47s 47s matches
47s 47s The following objects are masked from ‘package:stats’:
47s 47s filter, lag
47s 47s The following objects are masked from ‘package:base’:
47s 47s intersect, setdiff, setequal, union
47s 47s > library(purrr)
47s 47s Attaching package: ‘purrr’
47s 47s The following object is masked from ‘package:testthat’:
47s 47s is_null
47s 47s > library(tidyr)
47s 47s Attaching package: ‘tidyr’
47s 47s The following object is masked from ‘package:testthat’:
47s 47s matches
47s 47s > # library(pammtools)
47s > 47s > test_check("pammtools")
47s Loading required package: pammtools
48s 48s Attaching package: ‘pammtools’
48s 48s The following object is masked from ‘package:stats’:
48s 48s filter
48s 59s [ FAIL 2 | WARN 8 | SKIP 0 | PASS 341 ]
59s 59s ══ Failed tests
59s ── Error ('test-cumulative-effect.R:29'): LL helpers and as_ped
produce equivalent LL windows ──
59s Error in `vectbl_assign(x[[j]],
Bug#1040375: reply
[Petter Reinholdtsen] It is unclear to me why you believe this should work. Can you tell me where you got the idea to run the shared library like this? 1. /usr/bin/ssr-glinject from simplescreenrecorder package sets LD_PRELOAD=/usr/$LIB/simplescreenrecorder/libssr-glinject.so which also segmentation faults 2. LD_PRELOAD=/path/to/libssr-glinject.so works if simplescreenrecorder is compiled from source from https://github.com/MaartenBaert/ssr [Petter Reinholdtsen] I only use the package by starting simplescreenrecorder, so I have never seen the problem you are reporting before, and do not understand when it would occur in normal use. How do you "Record OpenGL" glxgears? When I try to launch anything using "OpenGL settings..." silent segmentation fault happens. I know it's segmentation fault (launched "ls") because "sudo dmesg -c" outputs: [ 261.486120] ls[3859]: segfault at ffe8 ip 7f315ab2fd9a sp 7ffc03c91e50 error 5 in libstdc++.so.6.0.30[7f315aa99000+101000] likely on CPU 2 (core 2, socket 0) [ 261.486134] Code: ff eb b4 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 08 48 8b 06 48 89 77 08 c6 07 00 <48> 8b 78 e8 48 01 f7 48 8b 87 d8 00 00 00 8b 77 20 48 85 c0 74 2a
Bug#1039649: marked as done (r-cran-ggridges: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 14:42:51 +
with message-id
and subject line Bug#1039649: fixed in r-cran-ggridges 0.5.4-2
has caused the Debian Bug report #1039649,
regarding r-cran-ggridges: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-ggridges
Version: 0.5.4-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
45s [ FAIL 5 | WARN 2 | SKIP 0 | PASS 58 ]
45s
45s == Failed tests
45s -- Error ('test_geom_density_ridges.R:9'): geom_density_ridges draws
correctly --
45s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
45s always_valid)`: Graphics API version mismatch
45s Backtrace:
45s x
45s 1. \-ggridges:::expect_doppelganger("geom_density_ridges basic", p) at
test_geom_density_ridges.R:9:2
45s 2. \-vdiffr::expect_doppelganger(title, fig, path = path, ...) at
autopkgtest_tmp/testthat/helper-vdiffr.R:3:2
45s 3. \-vdiffr (local) writer(fig, testcase, title)
45s 4. \-vdiffr:::svglite(file)
45s 5. \-vdiffr:::svglite_(...)
45s -- Error ('test_geom_gradient.R:10'): visual appearance of gradient geoms
--
45s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
45s always_valid)`: Graphics API version mismatch
45s Backtrace:
45s x
45s 1. \-ggridges:::expect_doppelganger(...) at test_geom_gradient.R:10:2
45s 2. \-vdiffr::expect_doppelganger(title, fig, path = path, ...) at
autopkgtest_tmp/testthat/helper-vdiffr.R:3:2
45s 3. \-vdiffr (local) writer(fig, testcase, title)
45s 4. \-vdiffr:::svglite(file)
45s 5. \-vdiffr:::svglite_(...)
45s -- Error ('test_geom_vridgeline.R:9'): visual appearance of
geom_vridgeline
45s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
45s always_valid)`: Graphics API version mismatch
45s Backtrace:
45s x
45s 1. \-ggridges:::expect_doppelganger("geom_vridgeline basic use", p) at
test_geom_vridgeline.R:9:2
45s 2. \-vdiffr::expect_doppelganger(title, fig, path = path, ...) at
autopkgtest_tmp/testthat/helper-vdiffr.R:3:2
45s 3. \-vdiffr (local) writer(fig, testcase, title)
45s 4. \-vdiffr:::svglite(file)
45s 5. \-vdiffr:::svglite_(...)
45s -- Error ('test_scale_cyclical.R:49'): visual appearance of
scale_*_cyclical ---
45s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
45s always_valid)`: Graphics API version mismatch
45s Backtrace:
45s x
45s 1. \-ggridges:::expect_doppelganger(...) at test_scale_cyclical.R:49:2
45s 2. \-vdiffr::expect_doppelganger(title, fig, path = path, ...) at
autopkgtest_tmp/testthat/helper-vdiffr.R:3:2
45s 3. \-vdiffr (local) writer(fig, testcase, title)
45s 4. \-vdiffr:::svglite(file)
45s 5. \-vdiffr:::svglite_(...)
45s -- Error ('test_theme_ridges.R:25'): theme_ridges draws correctly
--
45s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
45s always_valid)`: Graphics API version mismatch
45s Backtrace:
45s x
45s 1. \-ggridges:::expect_doppelganger("theme_ridges default", p +
theme_ridges()) at test_theme_ridges.R:25:2
45s 2. \-vdiffr::expect_doppelganger(title, fig, path = path, ...) at
autopkgtest_tmp/testthat/helper-vdiffr.R:3:2
45s 3. \-vdiffr (local) writer(fig, testcase, title)
45s 4. \-vdiffr:::svglite(file)
45s 5. \-vdiffr:::svglite_(...)
45s
45s [ FAIL 5 | WARN 2 | SKIP 0 | PASS 58 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-ggridges/34918108/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-ggridges
Source-Version: 0.5.4-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-ggridges, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-ggridges package)
(This message was generated automatically at their
Bug#1039652: marked as done (r-cran-gridtext: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 14:42:59 +
with message-id
and subject line Bug#1039652: fixed in r-cran-gridtext 0.1.5-2
has caused the Debian Bug report #1039652,
regarding r-cran-gridtext: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-gridtext
Version: 0.1.5-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
62s [ FAIL 3 | WARN 0 | SKIP 1 | PASS 231 ]
62s
62s ══ Skipped tests
═══
62s • On CRAN (1)
62s
62s ══ Failed tests
62s ── Error ('test-grid-renderer.R:80'): visual tests
─
62s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
62s always_valid)`: Graphics API version mismatch
62s Backtrace:
62s ▆
62s 1. └─gridtext:::expect_doppelganger(...) at test-grid-renderer.R:80:2
62s 2. └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at
autopkgtest_tmp/testthat/helper-vdiffr.R:3:2
62s 3. └─vdiffr (local) writer(fig, testcase, title)
62s 4. └─vdiffr:::svglite(file)
62s 5. └─vdiffr:::svglite_(...)
62s ── Error ('test-richtext-grob.R:120'): visual tests
62s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
62s always_valid)`: Graphics API version mismatch
62s Backtrace:
62s ▆
62s 1. └─gridtext:::expect_doppelganger("Various text boxes", draw_labels())
at test-richtext-grob.R:120:2
62s 2. └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at
autopkgtest_tmp/testthat/helper-vdiffr.R:3:2
62s 3. └─vdiffr (local) writer(fig, testcase, title)
62s 4. └─vdiffr:::svglite(file)
62s 5. └─vdiffr:::svglite_(...)
62s ── Error ('test-textbox-grob.R:34'): visual tests
──
62s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
62s always_valid)`: Graphics API version mismatch
62s Backtrace:
62s ▆
62s 1. └─gridtext:::expect_doppelganger(...) at test-textbox-grob.R:34:2
62s 2. └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at
autopkgtest_tmp/testthat/helper-vdiffr.R:3:2
62s 3. └─vdiffr (local) writer(fig, testcase, title)
62s 4. └─vdiffr:::svglite(file)
62s 5. └─vdiffr:::svglite_(...)
62s
62s [ FAIL 3 | WARN 0 | SKIP 1 | PASS 231 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-gridtext/34907249/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-gridtext
Source-Version: 0.1.5-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-gridtext, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-gridtext package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 15:12:26 +0200
Source: r-cran-gridtext
Architecture: source
Version: 0.1.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1039652
Changes:
r-cran-gridtext (0.1.5-2) unstable; urgency=medium
.
* Rebuild with r-graphics-engine set by r-base
Closes: #1039652
* Standards-Version: 4.6.2 (routine-update)
* Remove trailing whitespace in debian/changelog (routine-update)
Checksums-Sha1:
d783d1d2a2958f3ebbc30de5d3cd8ee75d730580 2240 r-cran-gridtext_0.1.5-2.dsc
90cf861f9a483fbd33a6aded2948ec139c81973a 2720
r-cran-gridtext_0.1.5-2.debian.tar.xz
60e2b304ef36c411433761699eb58e64a3a5e6c8 11389
r-cran-gridtext_0.1.5-2_amd64.buildinfo
Checksums-Sha256:
906f4e78607dd9a0364e5666c421b238a63cc0ad11c2c0e910d099cad6c13056 2240
r-cran-gridtext_0.1.5-2.dsc
Bug#1039647: marked as done (r-cran-ggplot2: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 14:42:36 +
with message-id
and subject line Bug#1039647: fixed in r-cran-ggplot2 3.4.2+dfsg-2
has caused the Debian Bug report #1039647,
regarding r-cran-ggplot2: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-ggplot2
Version: 3.4.1+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
84s [ FAIL 54 | WARN 4 | SKIP 95 | PASS 1450 ]
84s
84s ══ Skipped tests
═══
84s • On CRAN (94)
84s • stringsAsFactors only affects R <4.0 (1)
84s
84s ══ Failed tests
85s ── Error ('test-aes.r:198'): aesthetics are drawn correctly
85s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
85s always_valid)`: Graphics API version mismatch
85s Backtrace:
85s ▆
85s 1. └─vdiffr::expect_doppelganger(...) at test-aes.r:198:2
85s 2. └─vdiffr (local) writer(fig, testcase, title)
85s 3. └─vdiffr:::svglite(file)
85s 4. └─vdiffr:::svglite_(...)
85s ── Error ('test-aes.r:214'): alpha is drawn correctly
──
85s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
85s always_valid)`: Graphics API version mismatch
85s Backtrace:
85s ▆
85s 1. └─vdiffr::expect_doppelganger(...) at test-aes.r:214:2
85s 2. └─vdiffr (local) writer(fig, testcase, title)
85s 3. └─vdiffr:::svglite(file)
85s 4. └─vdiffr:::svglite_(...)
85s ── Error ('test-annotate.r:28'): segment annotations transform with scales
─
85s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
85s always_valid)`: Graphics API version mismatch
85s Backtrace:
85s ▆
85s 1. └─vdiffr::expect_doppelganger("line matches points", plot) at
test-annotate.r:28:2
85s 2. └─vdiffr (local) writer(fig, testcase, title)
85s 3. └─vdiffr:::svglite(file)
85s 4. └─vdiffr:::svglite_(...)
85s ── Error ('test-coord_sf.R:17'): basic plot builds without error
───
85s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
85s always_valid)`: Graphics API version mismatch
85s Backtrace:
85s ▆
85s 1. └─vdiffr::expect_doppelganger(...) at test-coord_sf.R:17:2
85s 2. └─vdiffr (local) writer(fig, testcase, title)
85s 3. └─vdiffr:::svglite(file)
85s 4. └─vdiffr:::svglite_(...)
85s ── Error ('test-coord_sf.R:30'): graticule lines can be removed via theme
──
85s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
85s always_valid)`: Graphics API version mismatch
85s Backtrace:
85s ▆
85s 1. └─vdiffr::expect_doppelganger("no panel grid", plot) at
test-coord_sf.R:30:2
85s 2. └─vdiffr (local) writer(fig, testcase, title)
85s 3. └─vdiffr:::svglite(file)
85s 4. └─vdiffr:::svglite_(...)
85s ── Error ('test-coord-cartesian.R:23'): cartesian coords draws correctly
with limits ──
85s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
85s always_valid)`: Graphics API version mismatch
85s Backtrace:
85s ▆
85s 1. └─vdiffr::expect_doppelganger(...) at test-coord-cartesian.R:23:2
85s 2. └─vdiffr (local) writer(fig, testcase, title)
85s 3. └─vdiffr:::svglite(file)
85s 4. └─vdiffr:::svglite_(...)
85s ── Error ('test-coord-cartesian.R:54'): cartesian coords draws correctly
with clipping on or off ──
85s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
85s always_valid)`: Graphics API version mismatch
85s Backtrace:
85s ▆
85s 1. └─vdiffr::expect_doppelganger(...) at test-coord-cartesian.R:54:2
85s 2. └─vdiffr (local) writer(fig, testcase, title)
85s 3. └─vdiffr:::svglite(file)
85s 4. └─vdiffr:::svglite_(...)
85s ── Error ('test-coord-flip.R:3'): secondary labels are correctly turned
off
85s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
85s always_valid)`: Graphics API version mismatch
85s Backtrace:
85s ▆
85s 1. └─vdiffr::expect_doppelganger(...) at test-coord-flip.R:3:2
85s 2. └─vdiffr (local) writer(fig, testcase, title)
85s 3. └─vdiffr:::svglite(file)
85s 4. └─vdiffr:::svglite_(...)
85s ──
Bug#1039648: marked as done (r-cran-ggrepel: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 14:42:43 +
with message-id
and subject line Bug#1039648: fixed in r-cran-ggrepel 0.9.3-2
has caused the Debian Bug report #1039648,
regarding r-cran-ggrepel: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-ggrepel
Version: 0.9.3-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
100s [ FAIL 5 | WARN 0 | SKIP 0 | PASS 72 ]
100s
101s == Failed tests
101s -- Error ('test-just-with-angle.R:11'): center with rotation
---
101s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
101s always_valid)`: Graphics API version mismatch
101s Backtrace:
101s x
101s 1. \-vdiffr::expect_doppelganger(...) at test-just-with-angle.R:11:2
101s 2. \-vdiffr (local) writer(fig, testcase, title)
101s 3. \-vdiffr:::svglite(file)
101s 4. \-vdiffr:::svglite_(...)
101s -- Error ('test-just-with-angle.R:51'): inward with rotation
---
101s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
101s always_valid)`: Graphics API version mismatch
101s Backtrace:
101s x
101s 1. \-vdiffr::expect_doppelganger(...) at test-just-with-angle.R:51:2
101s 2. \-vdiffr (local) writer(fig, testcase, title)
101s 3. \-vdiffr:::svglite(file)
101s 4. \-vdiffr:::svglite_(...)
101s -- Error ('test-just-with-angle.R:91'): outward with rotation
--
101s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
101s always_valid)`: Graphics API version mismatch
101s Backtrace:
101s x
101s 1. \-vdiffr::expect_doppelganger(...) at test-just-with-angle.R:91:2
101s 2. \-vdiffr (local) writer(fig, testcase, title)
101s 3. \-vdiffr:::svglite(file)
101s 4. \-vdiffr:::svglite_(...)
101s -- Error ('test-just-with-angle.R:130'): zero one with rotation
101s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
101s always_valid)`: Graphics API version mismatch
101s Backtrace:
101s x
101s 1. \-vdiffr::expect_doppelganger(...) at test-just-with-angle.R:130:2
101s 2. \-vdiffr (local) writer(fig, testcase, title)
101s 3. \-vdiffr:::svglite(file)
101s 4. \-vdiffr:::svglite_(...)
101s -- Error ('test-just-with-angle.R:174'): other just with rotation
--
101s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
101s always_valid)`: Graphics API version mismatch
101s Backtrace:
101s x
101s 1. \-vdiffr::expect_doppelganger(...) at test-just-with-angle.R:174:2
101s 2. \-vdiffr (local) writer(fig, testcase, title)
101s 3. \-vdiffr:::svglite(file)
101s 4. \-vdiffr:::svglite_(...)
101s
101s [ FAIL 5 | WARN 0 | SKIP 0 | PASS 72 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-ggrepel/34907248/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-ggrepel
Source-Version: 0.9.3-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-ggrepel, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-ggrepel package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 16:06:06 +0200
Source: r-cran-ggrepel
Architecture: source
Version: 0.9.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1039648
Changes:
r-cran-ggrepel (0.9.3-2) unstable; urgency=medium
.
* Team upload.
* Rebuild with r-graphics-engine set by r-base
Closes: #1039648
Checksums-Sha1:
0c5a0283f0a5859a613c882cd0e89204ea70c19d 2424 r-cran-ggrepel_0.9.3-2.dsc
Bug#1039646: marked as done (r-cran-ggally: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 14:42:23 +
with message-id
and subject line Bug#1039646: fixed in r-cran-ggally 2.1.2-2
has caused the Debian Bug report #1039646,
regarding r-cran-ggally: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-ggally
Version: 2.1.2-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
88s [ FAIL 1 | WARN 6 | SKIP 7 | PASS 530 ]
88s
88s == Skipped tests
===
88s * !rq(intergraph) is TRUE (1)
88s * On CRAN (3)
88s * broom.helpers cannot be loaded (2)
88s * crosstalk cannot be loaded (1)
88s
88s == Failed tests
88s -- Error ('test-ggparcoord.R:218'): missing
88s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of native symbols
88s Backtrace:
88s x
88s 1. +-base::`[<-`(`*tmp*`, 3, 1, value = ``) at
test-ggparcoord.R:218:2
88s 2. \-tibble:::`[<-.tbl_df`(`*tmp*`, 3, 1, value = ``) at
test-ggparcoord.R:218:2
88s 3. \-tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
88s 4. \-tibble:::tbl_subassign_row(xj, i, value, i_arg, value_arg)
88s 5. +-base::withCallingHandlers(...)
88s 6. \-tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
88s
88s [ FAIL 1 | WARN 6 | SKIP 7 | PASS 530 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-ggally/34918507/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-ggally
Source-Version: 2.1.2-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-ggally, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-ggally package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 16:09:53 +0200
Source: r-cran-ggally
Architecture: source
Version: 2.1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1039646
Changes:
r-cran-ggally (2.1.2-2) unstable; urgency=medium
.
* Rebuild with r-graphics-engine set by r-base
Closes: #1039646
* Standards-Version: 4.6.2 (routine-update)
* dh-update-R to update Build-Depends (routine-update)
Checksums-Sha1:
be9d92719c2e473c27d625c27b2a56449d198d1b 2379 r-cran-ggally_2.1.2-2.dsc
7b5cadb5047c0babe42e440f0e592ce7bdda1769 3160
r-cran-ggally_2.1.2-2.debian.tar.xz
d87001d49f2bf4323c8714d41809812bf0987874 11773
r-cran-ggally_2.1.2-2_amd64.buildinfo
Checksums-Sha256:
eac9ff79d2550e406c9b5274efdbba2a2edfc1a3ab57bd6a6c3a04d7a8d574fe 2379
r-cran-ggally_2.1.2-2.dsc
de1e865cc3c1282c8543805019393e65a03d892ad690c3d948d5fd6c0611cb7a 3160
r-cran-ggally_2.1.2-2.debian.tar.xz
3dcab7cb63b417cfa7e35701c2b0e0c0b58f7f17a83f5a908dfb0e56edfaef5c 11773
r-cran-ggally_2.1.2-2_amd64.buildinfo
Files:
c458b82d98e0bbce6148ef11835dc612 2379 gnu-r optional r-cran-ggally_2.1.2-2.dsc
f26d36ab0ad75501c56d74ca042229cd 3160 gnu-r optional
r-cran-ggally_2.1.2-2.debian.tar.xz
2e1e2c8bd65b3c994516f8012a88de59 11773 gnu-r optional
r-cran-ggally_2.1.2-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmzFwRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEi+Q//c6qlgLtJ7ZzM5jO3KGwXgZAGE0gUxtOL
Rq0ly0NN+lWDnHM7QAt53LjYBCKPY4VOJETLUUXypyq8uRxzv4GCOLSUYbPyj6EU
8Vt9wcz38YHi5mIw1BaS2O+eHnWCU43MxB+nT/RpIu1aNQjXGW0i2QiPHoGhUpsp
61GaCg+3iCWEliO0MOvpfQdD7VNC0Vs1nPmoXPfqrhrgI0W3WCYvChrB/KIOqrY4
uvwRjd2FyN8ZuDSPBhk7kyhvJcgA11Ts8+AkHhr1uA0jGeKHGL9Tem9kfQNzSIqO
PrCWw7D8b8tr1vwjaWO7O0cGOaww092NYLTfvoZOQqganGQMc+Y+W7Eb+lNC1Dwc
6mEpBeOeA25Fn8aeGCOlT929X/ZPcvp8BTtGDfAMk7vK0mkVs0rbLAEyJdBnQPao
Bug#1040477: librust-syn-1-dev fails to coinstall
Hi, Quoting Helmut Grohne (2023-07-06 13:27:19) > librust-syn-1-dev has (among other things) the following metadata: > > Provides: librust-syn-1.0.109-dev > Breaks: librust-syn-1.0.109-dev > Multi-Arch: same this looks very bad. > If apt and dose were refusing this situation this were a normal bug at > best. But since dpkg fails badly and leaves the system in an > inconsistent state, I am raising this to rc-severity. Even if we deem > this to be an apt bug or dpkg bug in the end, librust-syn-1-dev must > still be changed since we cannot depend on fixed versions of package > managers being used to install packages. I'd be very interested in knowing what this self-conflict is supposed to achieve. Depending on the answer it might be worth adding a Lintian check so that this doesn't happen again in the future. Thanks! cheers, josch signature.asc Description: signature
Bug#1040479: marked as done (multipath-tools: devices from extern FC-Raid only map if the have no partitions)
Your message dated Thu, 6 Jul 2023 15:18:52 +0200
with message-id
<5vjrplofrou22bgl4qs52mdxaksebrs26q6lgrsb2lqc56a4ss@dybruzgdwdxg>
and subject line 1040478: devices from extern FC-Raid only map if the have no
partitions
has caused the Debian Bug report #1040478,
regarding multipath-tools: devices from extern FC-Raid only map if the have no
partitions
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1040478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: multipath-tools
Version:0.9.4-3
Severity: critical
Tags: upstream
Justification: breaks unrelated software
X-Debbugs-Cc:t...@security.debian.org
Ohh sorry, the version failed is stable0.9.4 the version below is the working
on from oldstable.
Am 06.07.23 um 13:47 schrieb Andreas Matthus:
Package: multipath-tools
Version: 0.8.5-2+deb11u1
Severity: critical
Tags: upstream
Justification: breaks unrelated software
X-Debbugs-Cc:t...@security.debian.org
-- Package-specific info:
Contents of /etc/multipath.conf:
defaults {
polling_interval 10
max_fds 8192
}
devices {
device {
vendor "FUJITSU"
product "ETERNUS_DX(H|L|M|100)"
path_grouping_policy "group_by_prio"
prio "alua"
failback "immediate"
no_path_retry 10
}
}
blacklist {
wwid "360e00zensort29237d0005"
wwid "360e00zensort29237d0006"
}
-- System Information:
Debian Release: 12.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-10-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages multipath-tools depends on:
ii kpartx 0.9.4-3
ii libaio10.3.113-4
ii libc6 2.36-9
ii libdevmapper1.02.1 2:1.02.185-2
ii libjson-c5 0.16-2
ii libreadline8 8.2-1.3
ii libsystemd0252.6-1
ii libudev1 252.6-1
ii liburcu6 0.12.2-1
ii lsb-base 11.6
ii sg3-utils-udev 1.46-3
ii sysvinit-utils [lsb-base] 3.06-4
ii udev 252.6-1
multipath-tools recommends no packages.
Versions of packages multipath-tools suggests:
pn multipath-tools-boot
-- no debconf information
The multipath.conf was only a try to isolate the error. Normaly I don't have
this file and it can removed.
All devices on external FC-RAID which have partitions no get a mapper-path and
fails with message in syslog:
2023-07-06T12:41:04.353150+02:00 alac0903 multipathd[161807]:
360e00zensort29237d0009: ignoring map
2023-07-06T12:41:04.354918+02:00 alac0903 multipathd[161807]:
360e00zensort29237d0009: addmap [0 4294967296 multipath 1
queue_if_no_path 1 alua 2 1 service-time 0 1 1 65:48 1 service-time 0 1 1 65:96
1]
2023-07-06T12:41:04.355304+02:00 alac0903 multipathd[161807]: libdevmapper:
ioctl/libdm-iface.c(1980): device-mapper: reload ioctl on
360e00zensort29237d0009 (254:10) failed: Device or resource busy
In this way lvms having one or more pvs on such device can't mount.
Ultimatly I add oldstable and pining multipath-tools and lvm2 on this and now
the system works (after 7 hours searching for solution).
Maybe the problem is in conjuction with the lvm2-package. Only downgrade
multipath-tools not solve the problem and only downgrade lvm2 too.
with regards
--
Dipl.-Phys. Andreas Matthus
Netzwerkadministrator
Technische Universität Dresden
Fakultät Architektur
01062 Dresden
Tel.: +49 (351) 463-33909
Fax: +49 (351) 463-36120
E-Mail:andreas.matt...@tu-dresden.de
smime.p7s
Description: S/MIME Cryptographic Signature
--- End Message ---
--- Begin Message ---
Version: 0.9.4-3+deb12u1
Should be the same as #1037539, already fixed in deb12u1.--- End Message ---
Bug#1039655: marked as done (r-cran-knitr: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 13:20:03 +
with message-id
and subject line Bug#1039655: fixed in r-cran-knitr 1.43+dfsg-2
has caused the Debian Bug report #1039655,
regarding r-cran-knitr: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-knitr
Version: 1.42+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
80s autopkgtest [23:10:44]: test run-unit-test: [---
81s
81s R version 4.3.1 (2023-06-16) -- "Beagle Scouts"
81s Copyright (C) 2023 The R Foundation for Statistical Computing
81s Platform: x86_64-pc-linux-gnu (64-bit)
81s
81s R is free software and comes with ABSOLUTELY NO WARRANTY.
81s You are welcome to redistribute it under certain conditions.
81s Type 'license()' or 'licence()' for distribution details.
81s
81s R is a collaborative project with many contributors.
81s Type 'contributors()' for more information and
81s 'citation()' on how to cite R or R packages in publications.
81s
81s Type 'demo()' for some demos, 'help()' for on-line help, or
81s 'help.start()' for an HTML browser interface to help.
81s Type 'q()' to quit R.
81s
81s > library(testit)
81s > test_pkg("knitr")
82s Quitting from lines 4-5 (knit-tikzDevice.Rnw)
82s Error in tikzDevice::tikz(..., packages = c("\n\\nonstopmode\n", packages,
:
82s Graphics API version mismatch
82s Calls: test_pkg ... chunk_device -> do.call -> ->
82s In addition: Warning message:
82s In intersect(names(.tweak.bib), x) :
82s strings not representable in native encoding will be translated to UTF-8
82s Error from do.call(tikz_dev, dargs)
82s Execution halted
82s autopkgtest [23:10:46]: test run-unit-test: ---]
82s autopkgtest [23:10:46]: test run-unit-test: - - - - - - - - - - results -
- - - - - - - - -
82s run-unit-testFAIL non-zero exit status 1
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-knitr/34916802/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-knitr
Source-Version: 1.43+dfsg-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-knitr, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-knitr package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 15:06:09 +0200
Source: r-cran-knitr
Architecture: source
Version: 1.43+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1039655
Changes:
r-cran-knitr (1.43+dfsg-2) unstable; urgency=medium
.
* Rebuild with r-graphics-engine set by r-base
Closes: #1039655
Checksums-Sha1:
ed922f5251008044e28e57e76c79a025aaceaf02 2664 r-cran-knitr_1.43+dfsg-2.dsc
cf8a61b246f2f9b470de2cecdff413fe8effe846 5056
r-cran-knitr_1.43+dfsg-2.debian.tar.xz
0fb04a66b20159bff759c51234e7801f69d54b0a 10881
r-cran-knitr_1.43+dfsg-2_amd64.buildinfo
Checksums-Sha256:
e960bfb772a40fc683b02ef13ffe6c7d6ca0875fcc1527d8c0669e69c2c73798 2664
r-cran-knitr_1.43+dfsg-2.dsc
c74f3f8663926df0e3cfacd2084bc0b529e831e69f65e426de886a85aeab2b78 5056
r-cran-knitr_1.43+dfsg-2.debian.tar.xz
81849a8d549148f4f27218282808e267c347e530c3e3c1ed2a98fe28433c574f 10881
r-cran-knitr_1.43+dfsg-2_amd64.buildinfo
Files:
13f0eaeb196ca3326a740c2d87cb36f2 2664 gnu-r optional
r-cran-knitr_1.43+dfsg-2.dsc
d0f77c629bd3cc3ff4e3f7b4dcbefb53 5056 gnu-r optional
r-cran-knitr_1.43+dfsg-2.debian.tar.xz
bf212f89b51b6ebf6089e4c36939eb9f 10881 gnu-r optional
r-cran-knitr_1.43+dfsg-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmvOgRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtG6OA/9Gy8JYWd4K46rCaVbaAFPCGCJ8JnPqOB5
QYjjYm11xZ6Cg5iaFQxcmb/nP9qexQXSQuU6PHV1Qj1DiH20YBX9oSp1yUXyrXHS
Xsh2L9fjo9ivxuLgmJwGqgxS+GPPfz34yfoKHQYixNRV+35xn7sBJJj7w/xmMK8Y
Bug#1040478: marked as done (multipath-tools: devices from extern FC-Raid only map if the have no partitions)
Your message dated Thu, 6 Jul 2023 15:18:52 +0200
with message-id
<5vjrplofrou22bgl4qs52mdxaksebrs26q6lgrsb2lqc56a4ss@dybruzgdwdxg>
and subject line 1040478: devices from extern FC-Raid only map if the have no
partitions
has caused the Debian Bug report #1040478,
regarding multipath-tools: devices from extern FC-Raid only map if the have no
partitions
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1040478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: multipath-tools
Version: 0.8.5-2+deb11u1
Severity: critical
Tags: upstream
Justification: breaks unrelated software
X-Debbugs-Cc: t...@security.debian.org
-- Package-specific info:
Contents of /etc/multipath.conf:
defaults {
polling_interval 10
max_fds 8192
}
devices {
device {
vendor "FUJITSU"
product "ETERNUS_DX(H|L|M|100)"
path_grouping_policy "group_by_prio"
prio "alua"
failback "immediate"
no_path_retry 10
}
}
blacklist {
wwid "360e00zensort29237d0005"
wwid "360e00zensort29237d0006"
}
-- System Information:
Debian Release: 12.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-10-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages multipath-tools depends on:
ii kpartx 0.9.4-3
ii libaio10.3.113-4
ii libc6 2.36-9
ii libdevmapper1.02.1 2:1.02.185-2
ii libjson-c5 0.16-2
ii libreadline8 8.2-1.3
ii libsystemd0252.6-1
ii libudev1 252.6-1
ii liburcu6 0.12.2-1
ii lsb-base 11.6
ii sg3-utils-udev 1.46-3
ii sysvinit-utils [lsb-base] 3.06-4
ii udev 252.6-1
multipath-tools recommends no packages.
Versions of packages multipath-tools suggests:
pn multipath-tools-boot
-- no debconf information
The multipath.conf was only a try to isolate the error. Normaly I don't have
this file and it can removed.
All devices on external FC-RAID which have partitions no get a mapper-path and
fails with message in syslog:
2023-07-06T12:41:04.353150+02:00 alac0903 multipathd[161807]:
360e00zensort29237d0009: ignoring map
2023-07-06T12:41:04.354918+02:00 alac0903 multipathd[161807]:
360e00zensort29237d0009: addmap [0 4294967296 multipath 1
queue_if_no_path 1 alua 2 1 service-time 0 1 1 65:48 1 service-time 0 1 1 65:96
1]
2023-07-06T12:41:04.355304+02:00 alac0903 multipathd[161807]: libdevmapper:
ioctl/libdm-iface.c(1980): device-mapper: reload ioctl on
360e00zensort29237d0009 (254:10) failed: Device or resource busy
In this way lvms having one or more pvs on such device can't mount.
Ultimatly I add oldstable and pining multipath-tools and lvm2 on this and now
the system works (after 7 hours searching for solution).
Maybe the problem is in conjuction with the lvm2-package. Only downgrade
multipath-tools not solve the problem and only downgrade lvm2 too.
with regards
--- End Message ---
--- Begin Message ---
Version: 0.9.4-3+deb12u1
Should be the same as #1037539, already fixed in deb12u1.--- End Message ---
Bug#1039657: marked as done (r-cran-pammtools: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 13:20:19 +
with message-id
and subject line Bug#1039657: fixed in r-cran-pammtools 0.5.91-2
has caused the Debian Bug report #1039657,
regarding r-cran-pammtools: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-pammtools
Version: 0.5.8-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
59s [ FAIL 2 | WARN 8 | SKIP 0 | PASS 341 ]
59s
59s ══ Failed tests
59s ── Error ('test-cumulative-effect.R:29'): LL helpers and as_ped produce
equivalent LL windows ──
59s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of native symbols
59s Backtrace:
59s ▆
59s 1. ├─pammtools::sim_pexp(...) at test-cumulative-effect.R:29:2
59s 2. │ ├─base::suppressMessages(ped <- ped %>% left_join(reduce(df2,
full_join)))
59s 3. │ │ └─base::withCallingHandlers(...)
59s 4. │ └─ped %>% left_join(reduce(df2, full_join))
59s 5. ├─dplyr::left_join(., reduce(df2, full_join))
59s 6. ├─pammtools:::left_join.ped(., reduce(df2, full_join))
59s 7. │ └─pammtools:::ped_classes(y)
59s 8. │ └─class(ped) %in% ...
59s 9. └─purrr::reduce(df2, full_join)
59s 10. └─purrr:::reduce_impl(.x, .f, ..., .init = .init, .dir = .dir)
59s 11. ├─dplyr (local) fn(out, elt, ...)
59s 12. └─dplyr:::full_join.data.frame(out, elt, ...)
59s 13. └─dplyr:::join_mutate(...)
59s 14. ├─base::`[<-`(`*tmp*`, new_rows, names(y_key), value =
``)
59s 15. └─tibble:::`[<-.tbl_df`(`*tmp*`, new_rows, names(y_key),
value = ``)
59s 16. └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
59s 17. └─tibble:::tbl_subassign_row(xj, i, value, i_arg,
value_arg)
59s 18. ├─base::withCallingHandlers(...)
59s 19. └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
59s ── Error ('test-simple-transform.R:50'): Transformation of regular
survival data works ──
59s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of native symbols
59s Backtrace:
59s ▆
59s 1. ├─base::`[<-`(`*tmp*`, 6, "days", value = ``) at
test-simple-transform.R:50:2
59s 2. └─tibble:::`[<-.tbl_df`(`*tmp*`, 6, "days", value = ``) at
test-simple-transform.R:50:2
59s 3. └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
59s 4. └─tibble:::tbl_subassign_row(xj, i, value, i_arg, value_arg)
59s 5. ├─base::withCallingHandlers(...)
59s 6. └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
59s
59s [ FAIL 2 | WARN 8 | SKIP 0 | PASS 341 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-pammtools/34918508/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-pammtools
Source-Version: 0.5.91-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-pammtools, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-pammtools package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 15:00:42 +0200
Source: r-cran-pammtools
Architecture: source
Version: 0.5.91-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1039657
Changes:
r-cran-pammtools (0.5.91-2) unstable; urgency=medium
.
* Rebuild with r-graphics-engine set by r-base
Closes: #1039657
Checksums-Sha1:
2086dac2964d5bad7c9827753888069cebcca1a0 2360 r-cran-pammtools_0.5.91-2.dsc
a92fbe8179cdc6d86e428e665ea428d6819c1943 3380
r-cran-pammtools_0.5.91-2.debian.tar.xz
cba80a6f2db7bbd8bfcd8ee0e1c61e3760f1ca53 16000
r-cran-pammtools_0.5.91-2_amd64.buildinfo
Checksums-Sha256:
Bug#1039656: marked as done (r-cran-ncdfgeom: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 13:20:11 +
with message-id
and subject line Bug#1039656: fixed in r-cran-ncdfgeom 1.1.5+dfsg-2
has caused the Debian Bug report #1039656,
regarding r-cran-ncdfgeom: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-ncdfgeom
Version: 1.1.4+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
60s [ FAIL 1 | WARN 1 | SKIP 3 | PASS 637 ]
60s
60s ══ Skipped tests
═══
60s • On CRAN (3)
60s
60s ══ Failed tests
60s ── Error ('test_line.R:62'): shapefile line data works
─
60s Error in `vectbl_assign(x[[j]], cells[[j]], value)`: DLL requires the use
of native symbols
60s Backtrace:
60s ▆
60s 1. ├─base::`[<-`(`*tmp*`, is.na(lineData[name]), value = ``) at
test_line.R:62:4
60s 2. └─tibble:::`[<-.tbl_df`(`*tmp*`, is.na(lineData[name]), value =
``) at test_line.R:62:4
60s 3. └─tibble:::tbl_subassign_matrix(x, j, value, j_arg,
substitute(value))
60s 4. ├─base::withCallingHandlers(...)
60s 5. └─tibble:::vectbl_assign(x[[j]], cells[[j]], value)
60s
60s [ FAIL 1 | WARN 1 | SKIP 3 | PASS 637 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-ncdfgeom/34918116/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-ncdfgeom
Source-Version: 1.1.5+dfsg-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-ncdfgeom, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-ncdfgeom package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 15:02:34 +0200
Source: r-cran-ncdfgeom
Architecture: source
Version: 1.1.5+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1039656
Changes:
r-cran-ncdfgeom (1.1.5+dfsg-2) unstable; urgency=medium
.
* Rebuild with r-graphics-engine set by r-base
Closes: #1039656
Checksums-Sha1:
1bed0b8156cbe87d0441030eb02ea3aaf680eb3a 2339 r-cran-ncdfgeom_1.1.5+dfsg-2.dsc
8e0587237d747f0ab701a5c3c6f29fc596b8666e 5072
r-cran-ncdfgeom_1.1.5+dfsg-2.debian.tar.xz
e7e90e9cfb14fa965282eea293f5ed0658d7ba53 13043
r-cran-ncdfgeom_1.1.5+dfsg-2_amd64.buildinfo
Checksums-Sha256:
564bb4b80153367101be1b871ca484464b100ff8cdd6ec50d9f45150cd95f557 2339
r-cran-ncdfgeom_1.1.5+dfsg-2.dsc
c2c6f0e1cc218d3f34929842d07be99b4bf80b529c2482f0e42caedd6f001fd2 5072
r-cran-ncdfgeom_1.1.5+dfsg-2.debian.tar.xz
1dda142890d2fb4b34d121f70266e2d9800755f5231414eb77dbddbcb3518123 13043
r-cran-ncdfgeom_1.1.5+dfsg-2_amd64.buildinfo
Files:
e5cf5be668ee05e64ee8492975801b35 2339 gnu-r optional
r-cran-ncdfgeom_1.1.5+dfsg-2.dsc
3d8897487b2a6aa81979bde77cb7690a 5072 gnu-r optional
r-cran-ncdfgeom_1.1.5+dfsg-2.debian.tar.xz
a5a8b982c649401dfa34bf52aa821e28 13043 gnu-r optional
r-cran-ncdfgeom_1.1.5+dfsg-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmvFARHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGg9Q//f9pV1NkrOGSlxd0FGjsKwOwOv6l2ZAsp
+IBgZg95oFOVXPUU3RC7bxiT7o2pFQF8+C6IPLD0oRmhAWs4SA/TYiS2HYF6+cTA
Qtn5yzfbF9OGetSacRYXQC3AD5NyFemGnDLx8titqinKrPRJoe40YWjO7RVc+MFG
Xs4k32pDPAMDFT6l2CPApDBRHukOyUAXx8HJY2oZoqp50utg3r6DluITllbwzqkv
XiXegIHPVxqDbwEjgdqOYN1Bo1ug8v4Wtn1+QNOG68PAec26sPHlz5Kr42UEZraK
0pqyrhDnWuUV1ur/2tkC4S789+vDqQ2T/GrAcvXWoEJwnx9eSgMJ1QWoxz4Nf89s
c9czLMj3AzIiQNs3D6Katugqi1K65ormrxm+TyVQRtiGg0ddJioNsCYRBSgnMHnN
tB7hIdI8c94pNTnYNcLKBOAqM1xlur33yMcvkiB7YkJWXsSxqfO/n+tAXX/SqkJb
TGXvx5kcjkVZA2JasfEbVD/RMh0y9r11WDaOWpqsa1yq9NRS3v+Jy1UfH0oZNx1c
dg87PcxwiM5wzc+DQB53vxWdjfAdrvMGNbTHAoznf+418J1AeuR9nT889f3ZwG7+
Bug#1039481: marked as done (libgupnp-igd-doc: missing Breaks+Replaces: libgupnp-igd-1.0-doc (<< 1.6))
Your message dated Thu, 06 Jul 2023 13:19:09 + with message-id and subject line Bug#1039481: fixed in gupnp-igd 1.6.0-2 has caused the Debian Bug report #1039481, regarding libgupnp-igd-doc: missing Breaks+Replaces: libgupnp-igd-1.0-doc (<< 1.6) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1039481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgupnp-igd-doc Version: 1.6.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 because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid' installed while installing the package from 'experimental'. 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 .../libgupnp-igd-doc_1.6.0-1_all.deb ... Unpacking libgupnp-igd-doc (1.6.0-1) ... dpkg: error processing archive /var/cache/apt/archives/libgupnp-igd-doc_1.6.0-1_all.deb (--unpack): trying to overwrite '/usr/share/gtk-doc/html/gupnp-igd/ch01.html', which is also in package libgupnp-igd-1.0-doc 1.2.0-3 Errors were encountered while processing: /var/cache/apt/archives/libgupnp-igd-doc_1.6.0-1_all.deb cheers, Andreas libgupnp-igd-1.0-doc=1.2.0-3_libgupnp-igd-doc=1.6.0-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gupnp-igd Source-Version: 1.6.0-2 Done: Jeremy Bícha We believe that the bug you reported is fixed in the latest version of gupnp-igd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1039...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jeremy Bícha (supplier of updated gupnp-igd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 06 Jul 2023 08:57:33 -0400 Source: gupnp-igd Built-For-Profiles: noudeb Architecture: source Version: 1.6.0-2 Distribution: experimental Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Jeremy Bícha Closes: 1039481 Changes: gupnp-igd (1.6.0-2) experimental; urgency=medium . * Add Breaks/Replaces for -doc package rename (Closes: #1039481) Checksums-Sha1: 524f6192fc1828e284bb1fd8df67d60a209b81a7 2464 gupnp-igd_1.6.0-2.dsc f5582c3a689bbc6e3a76640775d04657c933bb02 6324 gupnp-igd_1.6.0-2.debian.tar.xz 01f88707ee7238a387d597f1411a1bfdcb59dfd6 11901 gupnp-igd_1.6.0-2_source.buildinfo Checksums-Sha256: 4d61771229d392b6d4d79eae093ef52bd624e34153beaa050647e48e88c4f0c4 2464 gupnp-igd_1.6.0-2.dsc 10bfaab152a32c81ed3c251586f2fe77f24edd786d3e6258446c8a01da546d1e 6324 gupnp-igd_1.6.0-2.debian.tar.xz f52a586aededeedd955a28b9adacfa66d6fdbfd6ba16204c3669d8fe6a0cbb28 11901 gupnp-igd_1.6.0-2_source.buildinfo Files: 14e4e55cd7c3a295b795bd41835249ab 2464 libs optional gupnp-igd_1.6.0-2.dsc 06ea6afe1e935d8764c8146e4bacbe11 6324 libs optional gupnp-igd_1.6.0-2.debian.tar.xz e42365f9f93d3337830ff323729f65bd 11901 libs optional gupnp-igd_1.6.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmSmulAACgkQ5mx3Wuv+ bH0VEQ//UJ2IJ/SUVniBJLbylsznSPnUTSzAvmHxKQe9nm6fiaaN3pNiYmR/a5Pz UxOzEJ2/KeUzOlK2oLzWgG/hIatXIlqEX0aesMCkIHU+Ay6nX7/Af2K4k3QVClrt t87qwldyuHmZDzjiHtmIf9peBNp2hNK8yb4oYzfdwRIyrj7YxBljN1J2UJpLoBnE /dwHcLw1RTHheq/NiFnunxmEi6eewtRpTHzrQ54UfOzHmEGa2vQNlzCXpqmbzac1 DgOvJZtf2Rbkdt0F2SYdubNdN1V5oKuvWkuMeApRcrOdqDuTl4KhNVSNtgpQPdb6 xam5w050aMaeVM3XeExf5ez3MHUR4/TOMIs9bBmJcM+vKBwIyrx9kqGA9O40cFQM bjlICyPWzg1z7wvTYhWYrL6NvouT7Ax3KAdHU9TU0WM9Fe97jmhcxNjoTdANHkWM /YTmC+CZvelqIAqyBLkshpYY/c1klTS1bzoMi1+lD8eb4YOyDkhcn2tgcOSPecOX ErmBwlxdPoBdmSGPNWx6kjee9pgQSD4oi8TPS88c3xM71lSFegbfw3EjSTjY0XnL GCXRVhuwEzwB4Bhk6CrYwH6G5vtLyiwni9o9gvTEJ3m+KVMTKeegq2+TENneyJrL A3Noo4qYgUhNQDbaZe1ZvZ2qQE015a3DFNNHC3jHuIg4FVtKSfs= =0ipx -END
Bug#1034348: at: autopkgtest regression on arm64
On 2023-07-05 18:58:13 +0200, Johannes Christ wrote:
> Is there another way to reproduce this issue?
I'm wondering whether there is a race condition in the test:
# use at command to schedule a job.
echo "echo `date` > ${WORKDIR}/${TMPFILE}" | at now + 1 minute
So the file is expected to be created 1 minute later.
Then in the script:
sleep 2
[...]
sleep 58
if grep -Fq "UTC" $WORKDIR/$TMPFILE
[...]
So the script waits for 1 minute (and some other fast commands)
before checking the existence of the file, which is the wait time
given to "at".
I can see 2 possible issues:
1. The system is a bit slow, and the job execution will take a bit
more time.
2. Time inaccuracies. What are the guaranties given by the system?
--
Vincent Lefèvre - Web:
Processed: dup bug
Processing commands for cont...@bugs.debian.org: > forcemerge 1040478 1040479 Bug #1040478 [multipath-tools] multipath-tools: devices from extern FC-Raid only map if the have no partitions Bug #1040479 [multipath-tools] multipath-tools: devices from extern FC-Raid only map if the have no partitions Marked as found in versions multipath-tools/0.8.5-2+deb11u1. Bug #1040478 [multipath-tools] multipath-tools: devices from extern FC-Raid only map if the have no partitions Marked as found in versions multipath-tools/0.9.4-3. Merged 1040478 1040479 > thanks Stopping processing here. Please contact me if you need assistance. -- 1040478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040478 1040479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1039659: marked as done (r-cran-pkgdown: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 13:07:22 +
with message-id
and subject line Bug#1039659: fixed in r-cran-pkgdown 2.0.7-2
has caused the Debian Bug report #1039659,
regarding r-cran-pkgdown: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039659
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-pkgdown
Version: 2.0.7-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
95s [ FAIL 24 | WARN 0 | SKIP 78 | PASS 516 ]
95s
95s ══ Skipped tests
═══
95s • dir_exists(path)[[1]] is not TRUE (1)
95s • dir_exists(test_path("assets/site-dot-github/.github")) is not TRUE (2)
95s • empty test (1)
95s • On CRAN (74)
95s
95s ══ Failed tests
96s ── Error ('test-build-articles.R:32'): warns about missing images
──
96s `build_articles(pkg)` threw an unexpected error.
96s Message: i In index: 1.
96s Caused by error in `render_rmarkdown()`:
96s ! Failed to render RMarkdown
96s Caused by error:
96s ! in callr subprocess.
96s Caused by error:
96s ! Graphics API version mismatch
96s Class: purrr_error_indexed/rlang_error/error/condition
96s ── Error ('test-build-articles.R:86'): can set width
───
96s Error in `render_rmarkdown(pkg, input = input, output = output_file,
output_format = format,
96s output_options = options, quiet = quiet)`: Failed to render RMarkdown
96s Caused by error:
96s ! in callr subprocess.
96s Caused by error:
96s ! Graphics API version mismatch
96s Backtrace:
96s ▆
96s 1. ├─testthat::expect_output(path <- build_article("width", pkg)) at
test-build-articles.R:86:2
96s 2. │ └─testthat:::quasi_capture(...)
96s 3. │ ├─testthat (local) .capture(...)
96s 4. │ │ └─testthat::capture_output_lines(code, print, width = width)
96s 5. │ │ └─testthat:::eval_with_output(code, print = print, width =
width)
96s 6. │ │ ├─withr::with_output_sink(path, withVisible(code))
96s 7. │ │ │ └─base::force(code)
96s 8. │ │ └─base::withVisible(code)
96s 9. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
96s 10. └─pkgdown::build_article("width", pkg)
96s 11. └─pkgdown:::render_rmarkdown(...)
96s 12. └─base::tryCatch(...)
96s 13. └─base (local) tryCatchList(expr, classes, parentenv, handlers)
96s 14. └─base (local) tryCatchOne(expr, names, parentenv,
handlers[[1L]])
96s 15. └─value[[3L]](cond)
96s 16. └─rlang::abort("Failed to render RMarkdown", parent = cnd)
96s ── Error ('test-build-articles.R:168'): pkgdown deps are included only
once in articles ──
96s Error in `render_rmarkdown(pkg, input = input, output = output_file,
output_format = format,
96s output_options = options, quiet = quiet)`: Failed to render RMarkdown
96s Caused by error:
96s ! in callr subprocess.
96s Caused by error:
96s ! Graphics API version mismatch
96s Backtrace:
96s ▆
96s 1. ├─testthat::expect_output(path <- build_article("html-deps", pkg)) at
test-build-articles.R:168:2
96s 2. │ └─testthat:::quasi_capture(...)
96s 3. │ ├─testthat (local) .capture(...)
96s 4. │ │ └─testthat::capture_output_lines(code, print, width = width)
96s 5. │ │ └─testthat:::eval_with_output(code, print = print, width =
width)
96s 6. │ │ ├─withr::with_output_sink(path, withVisible(code))
96s 7. │ │ │ └─base::force(code)
96s 8. │ │ └─base::withVisible(code)
96s 9. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
96s 10. └─pkgdown::build_article("html-deps", pkg)
96s 11. └─pkgdown:::render_rmarkdown(...)
96s 12. └─base::tryCatch(...)
96s 13. └─base (local) tryCatchList(expr, classes, parentenv, handlers)
96s 14. └─base (local) tryCatchOne(expr, names, parentenv,
handlers[[1L]])
96s 15. └─value[[3L]](cond)
96s 16. └─rlang::abort("Failed to render RMarkdown", parent = cnd)
96s ── Error ('test-build-home-index.R:3'): title and description come from
DESCRIPTION by default ──
96s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of native symbols
96s Backtrace:
96s ▆
96s 1. ├─testthat::expect_equal(data_home(pkg)$pagetitle, "A test package")
at
Bug#1039688: marked as done (r-cran-projpred: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 13:07:46 +
with message-id
and subject line Bug#1039688: fixed in r-cran-projpred 2.6.0+dfsg-2
has caused the Debian Bug report #1039688,
regarding r-cran-projpred: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-projpred
Version: 2.3.0+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
90s [ FAIL 14 | WARN 0 | SKIP 97 | PASS 1186 ]
90s
90s ══ Skipped tests
═══
90s • On CRAN (3)
90s • run_cvvs is not TRUE (18)
90s • run_prj is not TRUE (35)
90s • run_prll is not TRUE (3)
90s • run_vs is not TRUE (38)
90s
90s ══ Failed tests
90s ── Failure ('test_datafit.R:202'): init_refmodel(): `object` of class
"datafit" works ──
90s Names of `fam_orig` ('family', 'link', 'linkfun', 'linkinv', 'variance',
'dev.resids', 'aic', 'mu.eta', 'initialize', 'validmu', 'valideta',
'dispersion') don't match 'family', 'link', 'linkfun', 'linkinv', 'variance',
'dev.resids', 'aic', 'mu.eta', 'initialize', 'validmu', 'valideta'
90s rstanarm.glm.gauss.stdformul.with_wobs.with_offs
90s Backtrace:
90s ▆
90s 1. └─projpred:::refmodel_tester(...) at test_datafit.R:202:4
90s 2. └─projpred:::extfam_tester(...)
90s 3. └─testthat::expect_named(fam_orig, fam_orig_nms, info = info_str)
90s ── Failure ('test_datafit.R:202'): init_refmodel(): `object` of class
"datafit" works ──
90s Names of `fam_orig` ('family', 'link', 'linkfun', 'linkinv', 'variance',
'dev.resids', 'aic', 'mu.eta', 'initialize', 'validmu', 'valideta', 'simulate',
'dispersion') don't match 'family', 'link', 'linkfun', 'linkinv', 'variance',
'dev.resids', 'aic', 'mu.eta', 'initialize', 'validmu', 'valideta', 'simulate'
90s rstanarm.glm.brnll.stdformul.without_wobs.without_offs
90s Backtrace:
90s ▆
90s 1. └─projpred:::refmodel_tester(...) at test_datafit.R:202:4
90s 2. └─projpred:::extfam_tester(...)
90s 3. └─testthat::expect_named(fam_orig, fam_orig_nms, info = info_str)
90s ── Failure ('test_datafit.R:202'): init_refmodel(): `object` of class
"datafit" works ──
90s Names of `fam_orig` ('family', 'link', 'linkfun', 'linkinv', 'variance',
'dev.resids', 'aic', 'mu.eta', 'initialize', 'validmu', 'valideta',
'dispersion') don't match 'family', 'link', 'linkfun', 'linkinv', 'variance',
'dev.resids', 'aic', 'mu.eta', 'initialize', 'validmu', 'valideta'
90s rstanarm.glmm.gauss.spclformul.with_wobs.with_offs
90s Backtrace:
90s ▆
90s 1. └─projpred:::refmodel_tester(...) at test_datafit.R:202:4
90s 2. └─projpred:::extfam_tester(...)
90s 3. └─testthat::expect_named(fam_orig, fam_orig_nms, info = info_str)
90s ── Failure ('test_datafit.R:202'): init_refmodel(): `object` of class
"datafit" works ──
90s Names of `fam_orig` ('family', 'link', 'linkfun', 'linkinv', 'variance',
'dev.resids', 'aic', 'mu.eta', 'initialize', 'validmu', 'valideta',
'dispersion') don't match 'family', 'link', 'linkfun', 'linkinv', 'variance',
'dev.resids', 'aic', 'mu.eta', 'initialize', 'validmu', 'valideta'
90s rstanarm.gam.gauss.spclformul.with_wobs.without_offs
90s Backtrace:
90s ▆
90s 1. └─projpred:::refmodel_tester(...) at test_datafit.R:202:4
90s 2. └─projpred:::extfam_tester(...)
90s 3. └─testthat::expect_named(fam_orig, fam_orig_nms, info = info_str)
90s ── Failure ('test_datafit.R:202'): init_refmodel(): `object` of class
"datafit" works ──
90s Names of `fam_orig` ('family', 'link', 'linkfun', 'linkinv', 'variance',
'dev.resids', 'aic', 'mu.eta', 'initialize', 'validmu', 'valideta', 'simulate',
'dispersion') don't match 'family', 'link', 'linkfun', 'linkinv', 'variance',
'dev.resids', 'aic', 'mu.eta', 'initialize', 'validmu', 'valideta', 'simulate'
90s rstanarm.gamm.brnll.stdformul.without_wobs.without_offs
90s Backtrace:
90s ▆
90s 1. └─projpred:::refmodel_tester(...) at test_datafit.R:202:4
90s 2. └─projpred:::extfam_tester(...)
90s 3. └─testthat::expect_named(fam_orig, fam_orig_nms, info = info_str)
90s ── Failure ('test_extend_family.R:13'): `family` works
─
90s Names of `fam_orig` ('family', 'link', 'linkfun', 'linkinv', 'variance',
'dev.resids', 'aic', 'mu.eta', 'initialize', 'validmu', 'valideta',
'dispersion') don't match 'family', 'link', 'linkfun',
Bug#1039660: marked as done (r-cran-proc: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 13:07:38 +
with message-id
and subject line Bug#1039660: fixed in r-cran-proc 1.18.2-2
has caused the Debian Bug report #1039660,
regarding r-cran-proc: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-proc
Version: 1.18.0-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
72s [ FAIL 14 | WARN 51 | SKIP 32 | PASS 8973 ]
72s
72s ══ Skipped tests
═══
72s • Breaks everything for some reason... (1)
72s • microbenchmark cannot be loaded (1)
72s • Skipping error-prone Rcpp version check (1)
72s • Slow test skipped (29)
72s
72s ══ Failed tests
72s ── Error ('test-ggroc.R:9'): Ggroc screenshot looks normal
─
72s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
72s always_valid)`: Graphics API version mismatch
72s Backtrace:
72s ▆
72s 1. └─pROC:::expect_doppelganger("ggroc.screenshot",
test_ggplot_screenshot) at test-ggroc.R:9:8
72s 2. └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at
tests/testthat/helper-vdiffr.R:5:8
72s 3. └─vdiffr (local) writer(fig, testcase, title)
72s 4. └─vdiffr:::svglite(file)
72s 5. └─vdiffr:::svglite_(...)
72s ── Error ('test-ggroc.R:16'): Ggroc list screenshot looks normal
───
72s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
72s always_valid)`: Graphics API version mismatch
72s Backtrace:
72s ▆
72s 1. └─pROC:::expect_doppelganger("ggroc.list.screenshot",
test_ggplot_list_screenshot) at test-ggroc.R:16:8
72s 2. └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at
tests/testthat/helper-vdiffr.R:5:8
72s 3. └─vdiffr (local) writer(fig, testcase, title)
72s 4. └─vdiffr:::svglite(file)
72s 5. └─vdiffr:::svglite_(...)
72s ── Error ('test-ggroc.R:23'): Ggroc list can take multiple aes
─
72s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
72s always_valid)`: Graphics API version mismatch
72s Backtrace:
72s ▆
72s 1. └─pROC:::expect_doppelganger("ggroc.list.multi.aes",
test_ggplot_list_screenshot) at test-ggroc.R:23:8
72s 2. └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at
tests/testthat/helper-vdiffr.R:5:8
72s 3. └─vdiffr (local) writer(fig, testcase, title)
72s 4. └─vdiffr:::svglite(file)
72s 5. └─vdiffr:::svglite_(...)
72s ── Error ('test-ggroc.R:30'): Ggroc list extra aestetics screenshot looks
normal ──
72s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
72s always_valid)`: Graphics API version mismatch
72s Backtrace:
72s ▆
72s 1. └─pROC:::expect_doppelganger(...) at test-ggroc.R:30:8
72s 2. └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at
tests/testthat/helper-vdiffr.R:5:8
72s 3. └─vdiffr (local) writer(fig, testcase, title)
72s 4. └─vdiffr:::svglite(file)
72s 5. └─vdiffr:::svglite_(...)
72s ── Error ('test-ggroc.R:39'): Ggroc list with group facet screenshot looks
normal ──
72s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
72s always_valid)`: Graphics API version mismatch
72s Backtrace:
72s ▆
72s 1. └─pROC:::expect_doppelganger(...) at test-ggroc.R:39:8
72s 2. └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at
tests/testthat/helper-vdiffr.R:5:8
72s 3. └─vdiffr (local) writer(fig, testcase, title)
72s 4. └─vdiffr:::svglite(file)
72s 5. └─vdiffr:::svglite_(...)
72s ── Error ('test-ggroc.R:47'): Ggroc aesthetics can be modified with
scale_colour_manual ──
72s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
72s always_valid)`: Graphics API version mismatch
72s Backtrace:
72s ▆
72s 1. └─pROC:::expect_doppelganger(...) at test-ggroc.R:47:8
72s 2. └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at
tests/testthat/helper-vdiffr.R:5:8
72s 3. └─vdiffr (local) writer(fig, testcase, title)
72s 4. └─vdiffr:::svglite(file)
72s 5. └─vdiffr:::svglite_(...)
72s ── Error ('test-ggroc.R:55'): Ggroc screenshot looks normal with
Bug#1039675: marked as done (r-cran-posterior: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 13:07:30 +
with message-id
and subject line Bug#1039675: fixed in r-cran-posterior 1.4.1+dfsg-2
has caused the Debian Bug report #1039675,
regarding r-cran-posterior: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-posterior
Version: 1.4.0+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
60s [ FAIL 1 | WARN 0 | SKIP 5 | PASS 1497 ]
60s
60s ══ Skipped tests
═══
60s • On CRAN (5)
60s
60s ══ Failed tests
60s ── Error ('test-summarise_draws.R:18'): summarise_draws works correctly
60s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of native symbols
60s Backtrace:
60s ▆
60s 1. ├─base::`[<-`(`*tmp*`, 1, 1, value = ``) at
test-summarise_draws.R:18:2
60s 2. └─tibble:::`[<-.tbl_df`(`*tmp*`, 1, 1, value = ``) at
test-summarise_draws.R:18:2
60s 3. └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
60s 4. └─tibble:::tbl_subassign_row(xj, i, value, i_arg, value_arg)
60s 5. ├─base::withCallingHandlers(...)
60s 6. └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
60s
60s [ FAIL 1 | WARN 0 | SKIP 5 | PASS 1497 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-posterior/34916805/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-posterior
Source-Version: 1.4.1+dfsg-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-posterior, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-posterior package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 14:11:47 +0200
Source: r-cran-posterior
Architecture: source
Version: 1.4.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1039675
Changes:
r-cran-posterior (1.4.1+dfsg-2) unstable; urgency=medium
.
* Rebuild with r-graphics-engine set by r-base
Closes: #1039675
Checksums-Sha1:
b99814f83534acc1ea3eb75e520dae22a3dac4fe 2464 r-cran-posterior_1.4.1+dfsg-2.dsc
2e7875b9aaee77995ce7a6127b5dee9897384e9e 3728
r-cran-posterior_1.4.1+dfsg-2.debian.tar.xz
e458512333a27c726acf1e15db6613cea3dbbbd8 11547
r-cran-posterior_1.4.1+dfsg-2_amd64.buildinfo
Checksums-Sha256:
0c93b9b48b97af9cac73c2c40395e9917eb34d9dfa3c399a34e8dec8830b22a7 2464
r-cran-posterior_1.4.1+dfsg-2.dsc
39e8fdd6390beeb376f1c510d225bf5bbb2036b53f4605c86ed522d74aa01096 3728
r-cran-posterior_1.4.1+dfsg-2.debian.tar.xz
e1d3a58043285293ccece4867483739d33208b7eb7e662bbead4eed644e60d03 11547
r-cran-posterior_1.4.1+dfsg-2_amd64.buildinfo
Files:
d4a059885eb7b149a6ee338a6b567e5f 2464 gnu-r optional
r-cran-posterior_1.4.1+dfsg-2.dsc
b90acf640ecb65e0b6e04b4357e2c8a9 3728 gnu-r optional
r-cran-posterior_1.4.1+dfsg-2.debian.tar.xz
e59c890a7c2a41b092f89d1f7ed3be27 11547 gnu-r optional
r-cran-posterior_1.4.1+dfsg-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmsHkRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtENWw//fy+Ivm/p5R+WPMwbMxqGakMaoWmJmk1V
yr56ZGp/IpVy3hAz0ki0v3Iz7NnKy6tmKt4HgndMWe0onxP/vwNmO7aVP9M/bYhn
5R0kmVo4SQdpRsU/HllrL/yOFRTrkCAe7rGLAgrfCHC9s/PMxwHUTiuPv/YQWx81
QcRZSBMlQ+kjMTOnK1lIjE0+fAvnLdzfAbKsoGMj0L0ijQ9CDa35P/0fGgKRglCF
SUOSe0iw9sl5/ZVWhkgMUT7OE6BJs72wqWqbXJpX/nbVgnUgNdfYgfN7WCDJnLGT
lONW75YCoRBtz9cwEbGUPJm9BGJf/XNL35hdXUWJSKcOyF8TfNzkVMjadevt1Wu9
PC1qHFY/FH8OB0RpSAqQfEMs7rGgKFoDdaoYhrRgAQcnBgBOv+OMnV3e0/tI92YO
SiCLGAK0snv6/YvRmtlMsO2emVoG2Cr0FVLzf4mJks554TCTTGoR6YgLUhhptvMt
Mfxlr6jTlcynq9HBUDIEof/HW3iYaEaVENOgWJfl1HeCc09MK00d9Me79XzXcD4a
Bug#1039658: marked as done (r-cran-patchwork: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 13:07:13 +
with message-id
and subject line Bug#1039658: fixed in r-cran-patchwork 1.1.2-2
has caused the Debian Bug report #1039658,
regarding r-cran-patchwork: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039658
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-patchwork
Version: 1.1.2-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
47s [ FAIL 7 | WARN 0 | SKIP 0 | PASS 0 ]
47s
47s ══ Failed tests
48s ── Error ('test-arithmetic.R:2'): `+` works
48s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
48s always_valid)`: Graphics API version mismatch
48s Backtrace:
48s ▆
48s 1. └─vdiffr::expect_doppelganger(...) at test-arithmetic.R:2:2
48s 2. └─vdiffr (local) writer(fig, testcase, title)
48s 3. └─vdiffr:::svglite(file)
48s 4. └─vdiffr:::svglite_(...)
48s ── Error ('test-arithmetic.R:28'): `-` works
───
48s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
48s always_valid)`: Graphics API version mismatch
48s Backtrace:
48s ▆
48s 1. └─vdiffr::expect_doppelganger(...) at test-arithmetic.R:28:2
48s 2. └─vdiffr (local) writer(fig, testcase, title)
48s 3. └─vdiffr:::svglite(file)
48s 4. └─vdiffr:::svglite_(...)
48s ── Error ('test-arithmetic.R:38'): `|` and `/` works
───
48s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
48s always_valid)`: Graphics API version mismatch
48s Backtrace:
48s ▆
48s 1. └─vdiffr::expect_doppelganger(...) at test-arithmetic.R:38:2
48s 2. └─vdiffr (local) writer(fig, testcase, title)
48s 3. └─vdiffr:::svglite(file)
48s 4. └─vdiffr:::svglite_(...)
48s ── Error ('test-arithmetic.R:53'): `&` and `*` works
───
48s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
48s always_valid)`: Graphics API version mismatch
48s Backtrace:
48s ▆
48s 1. └─vdiffr::expect_doppelganger(...) at test-arithmetic.R:53:2
48s 2. └─vdiffr (local) writer(fig, testcase, title)
48s 3. └─vdiffr:::svglite(file)
48s 4. └─vdiffr:::svglite_(...)
48s ── Error ('test-layout.R:2'): The grid can be controlled
───
48s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
48s always_valid)`: Graphics API version mismatch
48s Backtrace:
48s ▆
48s 1. └─vdiffr::expect_doppelganger(...) at test-layout.R:2:2
48s 2. └─vdiffr (local) writer(fig, testcase, title)
48s 3. └─vdiffr:::svglite(file)
48s 4. └─vdiffr:::svglite_(...)
48s ── Error ('test-layout.R:33'): Fixed aspect plots behave
───
48s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
48s always_valid)`: Graphics API version mismatch
48s Backtrace:
48s ▆
48s 1. └─vdiffr::expect_doppelganger(...) at test-layout.R:33:2
48s 2. └─vdiffr (local) writer(fig, testcase, title)
48s 3. └─vdiffr:::svglite(file)
48s 4. └─vdiffr:::svglite_(...)
48s ── Error ('test-layout.R:58'): Insets looks as they should
─
48s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
48s always_valid)`: Graphics API version mismatch
48s Backtrace:
48s ▆
48s 1. └─vdiffr::expect_doppelganger(...) at test-layout.R:58:2
48s 2. └─vdiffr (local) writer(fig, testcase, title)
48s 3. └─vdiffr:::svglite(file)
48s 4. └─vdiffr:::svglite_(...)
48s
48s [ FAIL 7 | WARN 0 | SKIP 0 | PASS 0 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-patchwork/34918476/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-patchwork
Source-Version: 1.1.2-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-patchwork, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution
Bug#1040485: raspi-firmware breaks kernel upgrade
Package: raspi-firmware Severity: serious Justification: 6 X-Debbugs-Cc: okgomdjgbm...@gmail.com Dear Maintainer, I tried to upgrade the kernel today( bookworm amd64), and it failed because of raspi-firmware scripts. I had to rm manually files and purge raspi-firmware so that the kernel can complete the install. The messy removal is a second agravating problem. The package was included accidentally in the live CD for amd64. This problem affect every one that installed with the live CD. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages raspi-firmware depends on: ii dosfstools 4.2-1 ii dpkg1.21.22 raspi-firmware recommends no packages. Versions of packages raspi-firmware suggests: ii bluez-firmware 1.2-9 ii firmware-brcm80211 20230210-5 ii firmware-misc-nonfree 20230210-5
Processed: severity of 1038139 is normal
Processing commands for cont...@bugs.debian.org: > severity 1038139 normal Bug #1038139 [debci] debci-worker: Process leaks authentication data via amqp-tools Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1038139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 1039664 in r-cran-tikzdevice/0.12.4-3, fixed 1039661 in r-cran-ragg/1.2.5-3 ...
Processing commands for cont...@bugs.debian.org:
> fixed 1039664 r-cran-tikzdevice/0.12.4-3
Bug #1039664 {Done: Andreas Tille } [src:r-cran-tikzdevice]
r-cran-tikzdevice: autopkgtest failure with r-base (4.3.1-1)
Marked as fixed in versions r-cran-tikzdevice/0.12.4-3.
> fixed 1039661 r-cran-ragg/1.2.5-3
Bug #1039661 {Done: Andreas Tille } [src:r-cran-ragg]
r-cran-ragg: autopkgtest failure with r-base (4.3.1-1)
Marked as fixed in versions r-cran-ragg/1.2.5-3.
> fixed 1039672 r-cran-svglite/2.1.1-3
Bug #1039672 {Done: Andreas Tille } [src:r-cran-svglite]
r-cran-svglite: autopkgtest failure with r-base (4.3.1-1)
Marked as fixed in versions r-cran-svglite/2.1.1-3.
> fixed 1039664 r-cran-tikzdevice/0.12.4-3
Bug #1039664 {Done: Andreas Tille } [src:r-cran-tikzdevice]
r-cran-tikzdevice: autopkgtest failure with r-base (4.3.1-1)
Marked as fixed in versions r-cran-tikzdevice/0.12.4-3; no longer marked as
fixed in versions r-cran-tikzdevice/0.12.4-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1039661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039661
1039664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039664
1039672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1039663: marked as done (r-cran-stars: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 12:20:03 + with message-id and subject line Bug#1039663: fixed in r-cran-stars 0.6-1-1 has caused the Debian Bug report #1039663, regarding r-cran-stars: autopkgtest failure with r-base (4.3.1-1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1039663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-stars Version: 0.6-0-4 Severity: serious Justification: autopkgtest failure Dear Maintainer, The autopkgtest of your package fails with r-base (4.3.1-1): 104s STFDF> x = stfdf[stfdf[1:2,],] 104s Error in .local(from, to, ...) : DLL requires the use of native symbols 104s Calls: example ... .local -> which_nearest -> which_nearest -> .local -> .Call https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-stars/34919701/log.gz --- End Message --- --- Begin Message --- Source: r-cran-stars Source-Version: 0.6-1-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-cran-stars, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1039...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-stars package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 06 Jul 2023 13:53:33 +0200 Source: r-cran-stars Architecture: source Version: 0.6-1-1 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 1039663 Changes: r-cran-stars (0.6-1-1) unstable; urgency=medium . * New upstream version * Reorder sequence of d/control fields by cme (routine-update) * Sync Test-Depends with Suggests * Rebuild with r-graphics-engine set by r-base Closes: #1039663 * Since package exactextractr is not available yet (but in new) one test (and its output) needs to be patched Checksums-Sha1: ce804f60aaafe761b7dd14ab36cffcc4d53c3bc8 2730 r-cran-stars_0.6-1-1.dsc 56a557fdb1b361110b19bb308484616f8845251a 3572040 r-cran-stars_0.6-1.orig.tar.gz 0833d2838d8b7e4874b4b94c58d94764582923cd 4356 r-cran-stars_0.6-1-1.debian.tar.xz d4448a4860015ef02b3ae9b1eccb2e14cbce87bf 12343 r-cran-stars_0.6-1-1_amd64.buildinfo Checksums-Sha256: ae55e6e4937e41f5c38e2a01c89a97f77f55f85ba933da162bde845b25f759cb 2730 r-cran-stars_0.6-1-1.dsc 1f78db3adab9ebbfc9d98c6cc592708d893b5d7fd7fd876af454042ef42204a7 3572040 r-cran-stars_0.6-1.orig.tar.gz 1564c05eba611ad280c2d39a23c0187c64f5d564216166dcc7193d53d334ddcf 4356 r-cran-stars_0.6-1-1.debian.tar.xz bf61eea164dab53a970d286a6bfad555e27a13200f19a70f42787fb80e8ff8b6 12343 r-cran-stars_0.6-1-1_amd64.buildinfo Files: 817802be7061c4b8157fe9361a6e1574 2730 gnu-r optional r-cran-stars_0.6-1-1.dsc 6142124acb826319288e049fff6d4fed 3572040 gnu-r optional r-cran-stars_0.6-1.orig.tar.gz d1f36211ee907a7661923460a7832bbf 4356 gnu-r optional r-cran-stars_0.6-1-1.debian.tar.xz 1b839bbaec757de49197bfc4a3fb3584 12343 gnu-r optional r-cran-stars_0.6-1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmrH8RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtH2iw/8DqQr00ODs2Z5UhHxSbng9xwwrbXUpUth zYFULcuC5oN+AuDe6d6B4Wryjws7V1nu/Okxu2N/VXwKrNZ/GxPl+D7LaKcic8ht yGBYQk09ttoRl6sUCxKkaJFgB/Uoi3sRQ0OmLd0WZgQBbiaLiLyaS1kJMuF3MvbK PK55gyMec916LmnkV06XmKyHKqruwlslHIgIQw8qoRl7T/uCfFjCCIhZzeZRYOI5 KXXT/KsK/0p4NXm6whUWIsAX+nHPmjyMZh+lPIly9wgS+ewweHkRmQxFDVJp4t/q EhAf3I1VnV1eAXVNuoC48+w6U+gmVNaGMrocCSxMvjI9C73GD1SLPPNWpeqyzr/y D0025Mgh3Sio8+bpo2tGr79m4Jhn8zdKgOrWpfwUO6MtVGC9JCyrG0EXecYIynww BZh/KHv1LytvGskXmIAcGxMcePPRk1VU+B8dwldk0N8eSBxC4hTp9j+Zh65YW0iZ SZfMAv7jMoO4o58RBefkfXokHq++w5Ydoh96Aj9GHC3wd/XBW+M9o7zjHpWqLCdE hSgDQHZ4CnBAahDhwbafDNJXD3fQdexPaxO805y24tWr4JYNV39Z4gkdXqgqBvSc V9AsLStHbrnRt7Q2yL0p4wN9bR5y5eTSTWZdnyywZn7BmQNWGrUoVBXb3ztojpNM 8MccRJS+Y68= =UNsF -END PGP SIGNATURE End Message ---
Bug#1040479: multipath-tools: devices from extern FC-Raid only map if the have no partitions
Package: multipath-tools
Version:0.9.4-3
Severity: critical
Tags: upstream
Justification: breaks unrelated software
X-Debbugs-Cc:t...@security.debian.org
Ohh sorry, the version failed is stable0.9.4 the version below is the working
on from oldstable.
Am 06.07.23 um 13:47 schrieb Andreas Matthus:
Package: multipath-tools
Version: 0.8.5-2+deb11u1
Severity: critical
Tags: upstream
Justification: breaks unrelated software
X-Debbugs-Cc:t...@security.debian.org
-- Package-specific info:
Contents of /etc/multipath.conf:
defaults {
polling_interval 10
max_fds 8192
}
devices {
device {
vendor "FUJITSU"
product "ETERNUS_DX(H|L|M|100)"
path_grouping_policy "group_by_prio"
prio "alua"
failback "immediate"
no_path_retry 10
}
}
blacklist {
wwid "360e00zensort29237d0005"
wwid "360e00zensort29237d0006"
}
-- System Information:
Debian Release: 12.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-10-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages multipath-tools depends on:
ii kpartx 0.9.4-3
ii libaio10.3.113-4
ii libc6 2.36-9
ii libdevmapper1.02.1 2:1.02.185-2
ii libjson-c5 0.16-2
ii libreadline8 8.2-1.3
ii libsystemd0252.6-1
ii libudev1 252.6-1
ii liburcu6 0.12.2-1
ii lsb-base 11.6
ii sg3-utils-udev 1.46-3
ii sysvinit-utils [lsb-base] 3.06-4
ii udev 252.6-1
multipath-tools recommends no packages.
Versions of packages multipath-tools suggests:
pn multipath-tools-boot
-- no debconf information
The multipath.conf was only a try to isolate the error. Normaly I don't have
this file and it can removed.
All devices on external FC-RAID which have partitions no get a mapper-path and
fails with message in syslog:
2023-07-06T12:41:04.353150+02:00 alac0903 multipathd[161807]:
360e00zensort29237d0009: ignoring map
2023-07-06T12:41:04.354918+02:00 alac0903 multipathd[161807]:
360e00zensort29237d0009: addmap [0 4294967296 multipath 1
queue_if_no_path 1 alua 2 1 service-time 0 1 1 65:48 1 service-time 0 1 1 65:96
1]
2023-07-06T12:41:04.355304+02:00 alac0903 multipathd[161807]: libdevmapper:
ioctl/libdm-iface.c(1980): device-mapper: reload ioctl on
360e00zensort29237d0009 (254:10) failed: Device or resource busy
In this way lvms having one or more pvs on such device can't mount.
Ultimatly I add oldstable and pining multipath-tools and lvm2 on this and now
the system works (after 7 hours searching for solution).
Maybe the problem is in conjuction with the lvm2-package. Only downgrade
multipath-tools not solve the problem and only downgrade lvm2 too.
with regards
--
Dipl.-Phys. Andreas Matthus
Netzwerkadministrator
Technische Universität Dresden
Fakultät Architektur
01062 Dresden
Tel.: +49 (351) 463-33909
Fax: +49 (351) 463-36120
E-Mail:andreas.matt...@tu-dresden.de
smime.p7s
Description: S/MIME Cryptographic Signature
Bug#1040478: multipath-tools: devices from extern FC-Raid only map if the have no partitions
Package: multipath-tools
Version: 0.8.5-2+deb11u1
Severity: critical
Tags: upstream
Justification: breaks unrelated software
X-Debbugs-Cc: t...@security.debian.org
-- Package-specific info:
Contents of /etc/multipath.conf:
defaults {
polling_interval 10
max_fds 8192
}
devices {
device {
vendor "FUJITSU"
product "ETERNUS_DX(H|L|M|100)"
path_grouping_policy "group_by_prio"
prio "alua"
failback "immediate"
no_path_retry 10
}
}
blacklist {
wwid "360e00zensort29237d0005"
wwid "360e00zensort29237d0006"
}
-- System Information:
Debian Release: 12.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-10-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages multipath-tools depends on:
ii kpartx 0.9.4-3
ii libaio10.3.113-4
ii libc6 2.36-9
ii libdevmapper1.02.1 2:1.02.185-2
ii libjson-c5 0.16-2
ii libreadline8 8.2-1.3
ii libsystemd0252.6-1
ii libudev1 252.6-1
ii liburcu6 0.12.2-1
ii lsb-base 11.6
ii sg3-utils-udev 1.46-3
ii sysvinit-utils [lsb-base] 3.06-4
ii udev 252.6-1
multipath-tools recommends no packages.
Versions of packages multipath-tools suggests:
pn multipath-tools-boot
-- no debconf information
The multipath.conf was only a try to isolate the error. Normaly I don't have
this file and it can removed.
All devices on external FC-RAID which have partitions no get a mapper-path and
fails with message in syslog:
2023-07-06T12:41:04.353150+02:00 alac0903 multipathd[161807]:
360e00zensort29237d0009: ignoring map
2023-07-06T12:41:04.354918+02:00 alac0903 multipathd[161807]:
360e00zensort29237d0009: addmap [0 4294967296 multipath 1
queue_if_no_path 1 alua 2 1 service-time 0 1 1 65:48 1 service-time 0 1 1 65:96
1]
2023-07-06T12:41:04.355304+02:00 alac0903 multipathd[161807]: libdevmapper:
ioctl/libdm-iface.c(1980): device-mapper: reload ioctl on
360e00zensort29237d0009 (254:10) failed: Device or resource busy
In this way lvms having one or more pvs on such device can't mount.
Ultimatly I add oldstable and pining multipath-tools and lvm2 on this and now
the system works (after 7 hours searching for solution).
Maybe the problem is in conjuction with the lvm2-package. Only downgrade
multipath-tools not solve the problem and only downgrade lvm2 too.
with regards
Bug#1040375: /usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: Segmentation fault when used with anything
[B] > * What led up to the situation? > Trying to "Record OpenGL" in simplescreenrecorder. > * What exactly did you do (or not do) that was effective (or ineffective)? > LD_PRELOAD=/usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so > /usr/bin/true It is unclear to me why you believe this should work. Can you tell me where you got the idea to run the shared library like this? Note, I am able to reproduce the crash. I only use the package by starting simplescreenrecorder, so I have never seen the problem you are reporting before, and do not understand when it would occur in normal use. Can you explain? I tried running from valgrind, but it did not work. I get the segfault, but no information about where the segfault happen. valgrind --trace-children=yes dash -c "LD_PRELOAD=/usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so /usr/bin/true" Same problem with gdb: (gdb) set environment LD_PRELOAD /usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so (gdb) run Starting program: /usr/bin/true During startup program terminated with signal SIGSEGV, Segmentation fault. (gdb) bt No stack. (gdb) I have no idea how to debug this. -- Happy hacking Petter Reinholdtsen
Bug#1040477: librust-syn-1-dev fails to coinstall
Package: librust-syn-1-dev Version: 1.0.109-2 Severity: serious Justification: fails to (co)install Control: affects -1 + src:rust-fd-find User: debian-cr...@lists.debian.org Usertags: ftcbfs X-Debbugs-Cc: de...@lists.debian.org librust-syn-1-dev has (among other things) the following metadata: Provides: librust-syn-1.0.109-dev Breaks: librust-syn-1.0.109-dev Multi-Arch: same It is not clear to me what this is supposed to mean. Can you shed some light on what this is supposed to achieve? In any case, apt and dpkg disagree about what this shall mean. apt thinks that self-breaks are to be ignored and asks dpkg to configure both of these packages, but dpkg doesn't like that: | dpkg: dependency problems prevent configuration of librust-syn-1-dev:amd64: | librust-syn-1-dev:arm64 (1.0.109-2) breaks librust-syn-1.0.109-dev and is unpacked but not configured. | librust-syn-1-dev:amd64 (1.0.109-2) provides librust-syn-1.0.109-dev. | | dpkg: error processing package librust-syn-1-dev:amd64 (--configure): | dependency problems - leaving unconfigured You can reproduce the installation failure using: mmdebstrap unstable /dev/null --architectures=amd64,arm64 --variant=apt --include=librust-syn-1-dev:amd64,librust-syn-1-dev:arm64 If apt and dose were refusing this situation this were a normal bug at best. But since dpkg fails badly and leaves the system in an inconsistent state, I am raising this to rc-severity. Even if we deem this to be an apt bug or dpkg bug in the end, librust-syn-1-dev must still be changed since we cannot depend on fixed versions of package managers being used to install packages. Helmut
Processed: librust-syn-1-dev fails to coinstall
Processing control commands: > affects -1 + src:rust-fd-find Bug #1040477 [librust-syn-1-dev] librust-syn-1-dev fails to coinstall Added indication that 1040477 affects src:rust-fd-find -- 1040477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040477 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1040199 to xtrx-dkms, forcibly merging 1038003 1040199
Processing commands for cont...@bugs.debian.org: > reassign 1040199 xtrx-dkms Bug #1040199 [src:linux] linux-image-6.3.0-1-amd64: kernel panic during boot Bug reassigned from package 'src:linux' to 'xtrx-dkms'. No longer marked as found in versions linux/6.3.7-1. Ignoring request to alter fixed versions of bug #1040199 to the same values previously set > forcemerge 1038003 1040199 Bug #1038003 [xtrx-dkms] xtrx-dkms: module fails to build for Linux 6.3: error: assignment of read-only member 'vm_flags' Bug #1040199 [xtrx-dkms] linux-image-6.3.0-1-amd64: kernel panic during boot Set Bug forwarded-to-address to 'https://github.com/myriadrf/xtrx_linux_pcie_drv/pull/17'. Severity set to 'serious' from 'grave' Marked as found in versions xtrx-dkms/0.0.1+git20190320.5ae3a3e-3.2. Added tag(s) trixie and sid. Merged 1038003 1040199 > thanks Stopping processing here. Please contact me if you need assistance. -- 1038003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038003 1040199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040473: python-click: FTBFS after new pytest
Source: python-click
Version: 8.1.3-2
Severity: serious
Hello, after new pytest went in sid (or some other python updates), the package
started FTBFS
I: Logging to /home/pbuilder/sid_result/python-click_8.1.3-2_amd64.build
D: cmdline: build --distribution sid --buildresult /home/pbuilder/sid_result
--basetgz /home/pbuilder/sid-base.tgz --logfile
/home/pbuilder/sid_result/python-click_8.1.3-2_amd64.build --mirror
http://deb.debian.org/debian --debootstrapopts
--keyring=/usr/share/keyrings/debian-archive-keyring.gpg --aptcache
/home/pbuilder/aptcache/debian --components main contrib non-free
../python-click_8.1.3-2.dsc
W: cgroups are not available on the host, not using them.
I: pbuilder: network access will be disabled during build
I: Current time: Thu Jul 6 12:17:33 CEST 2023
I: pbuilder-time-stamp: 1688638653
I: Building the build Environment
I: extracting base tarball [/home/pbuilder/sid-base.tgz]
I: copying local configuration
W: No local /etc/mailname to copy, relying on /tmp/build/356573/etc/mailname to
be correct
W: --override-config is not set; not updating apt.conf Read the manpage for
details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d already exists
D: no hooks of type H found -- ignoring
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [../python-click_8.1.3-2.dsc]
I: copying [../python-click_8.1.3.orig.tar.gz]
I: copying [../python-click_8.1.3-2.debian.tar.xz]
I: Extracting source
gpgv: Signature made Tue Jan 10 06:12:58 2023 UTC
gpgv:using RSA key B9FAD3192AF3E4A5309D9D39879F3C993801A94F
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify inline signature for
./python-click_8.1.3-2.dsc: no acceptable signature found
dpkg-source: info: extracting python-click in python-click-8.1.3
dpkg-source: info: unpacking python-click_8.1.3.orig.tar.gz
dpkg-source: info: unpacking python-click_8.1.3-2.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying docs-Use-local-Python-intersphinx-inventary.patch
I: Not using root during the build.
I: Installing the build-deps
I: user script /tmp/build/356573/tmp/hooks/D20update starting
Hit:1 http://deb.debian.org/debian sid InRelease
Reading package lists...
I: user script /tmp/build/356573/tmp/hooks/D20update finished
-> Attempting to parse the build-deps
-> Considering build-depdebhelper-compat (= 13)
-> Trying to add debhelper-compat=13
-> Considering build-dep dh-sequence-python3
-> Trying to add dh-sequence-python3
-> Considering build-dep python3-all
-> Trying to add python3-all
-> Considering build-dep python3-doc
-> Trying to add python3-doc
-> Considering build-dep python3-colorama
-> Trying to add python3-colorama
-> Considering build-dep python3-docutils
-> Trying to add python3-docutils
-> Considering build-dep python3-pallets-sphinx-themes (>= 2.0.1)
-> Trying to add python3-pallets-sphinx-themes
-> Considering build-dep python3-pytest
-> Trying to add python3-pytest
-> Considering build-dep python3-requests
-> Trying to add python3-requests
-> Considering build-dep python3-setuptools
-> Trying to add python3-setuptools
-> Considering build-dep python3-sphinx
-> Trying to add python3-sphinx
-> Considering build-dep python3-sphinx-issues
-> Trying to add python3-sphinx-issues
-> Considering build-dep python3-sphinx-tabs
-> Trying to add python3-sphinx-tabs
-> Considering build-dep python3-sphinxcontrib-log-cabinet
-> Trying to add python3-sphinxcontrib-log-cabinet
-> Installing debhelper-compat=13 dh-sequence-python3 python3-all python3-doc
python3-colorama python3-docutils python3-pallets-sphinx-themes python3-pytest
python3-requests python3-setuptools python3-sphinx python3-sphinx-issues
python3-sphinx-tabs python3-sphinxcontrib-log-cabinet
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
autoconf automake autopoint autotools-dev bsdextrautils ca-certificates
dh-autoreconf dh-strip-nondeterminism docutils-common dwz file gettext
gettext-base groff-base intltool-debian libarchive-zip-perl
libdebhelper-perl libelf1 libexpat1 libfile-stripnondeterminism-perl
libicu72 libjs-jquery libjs-sphinxdoc libjs-underscore libjson-perl
libmagic-mgc libmagic1 libncursesw6 libpipeline1 libpython3-stdlib
libpython3.11-minimal libpython3.11-stdlib libreadline8 libsqlite3-0
libsub-override-perl libtool libuchardet0 libxml2 m4 man-db media-types
openssl po-debconf python-babel-localedata python3 python3-alabaster
python3-babel python3-certifi python3-chardet python3-charset-normalizer
python3-distutils python3-idna python3-imagesize python3-iniconfig
python3-jinja2 python3-lib2to3 python3-markupsafe python3-minimal
Bug#1040405: ruby-gollum-lib: incompatible with newer ruby-rouge
On Wed, 5 Jul 2023 16:44:31 +0200 Gianfranco Costamagna wrote: > Can you please have a look? We no longer need ruby-gollum-lib for gitaly, so requested removal of ruby-gollum-lib in #1040461.
Bug#1039677: marked as done (r-cran-sftime: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 09:57:19 + with message-id and subject line Bug#1039677: fixed in r-cran-sftime 0.2-0-6 has caused the Debian Bug report #1039677, regarding r-cran-sftime: autopkgtest failure with r-base (4.3.1-1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1039677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-sftime Version: 0.2-0-5 Severity: serious Justification: autopkgtest failure Dear Maintainer, The autopkgtest of your package fails with r-base (4.3.1-1): 47s STI> all.equal(stidf, stidf[stidf,]) 47s Error in .local(from, to, ...) : DLL requires the use of native symbols 47s Calls: example ... .local -> which_nearest -> which_nearest -> .local -> .Call https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-sftime/34911625/log.gz --- End Message --- --- Begin Message --- Source: r-cran-sftime Source-Version: 0.2-0-6 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-cran-sftime, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1039...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-sftime package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 06 Jul 2023 11:28:03 +0200 Source: r-cran-sftime Architecture: source Version: 0.2-0-6 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 1039677 Changes: r-cran-sftime (0.2-0-6) unstable; urgency=medium . * Rebuild with r-graphics-engine set by r-base Closes: #1039677 * dh-update-R to update Build-Depends (routine-update) * Remove trailing whitespace in debian/changelog (routine-update) Checksums-Sha1: cc34ab092fb9c99f7d84d9cde7518e71938ccb7d 2257 r-cran-sftime_0.2-0-6.dsc cf12495737fef639760f58a312aef3d3a07d963b 2804 r-cran-sftime_0.2-0-6.debian.tar.xz 07b06d1aae9aed39db1ae329405b61017d5c7426 12266 r-cran-sftime_0.2-0-6_amd64.buildinfo Checksums-Sha256: 10a9e159f6c93065f230840f49de1a0c3d574fa0533beff0c95c0818e26c89a2 2257 r-cran-sftime_0.2-0-6.dsc fb61c1b1eb384b87eb6c42858b03083aa3832cc6a2764fb06be4074d96b634ce 2804 r-cran-sftime_0.2-0-6.debian.tar.xz c882872083dc5e97ec7dc4119ae9636298225a45a0287b3ed569a117f11474e5 12266 r-cran-sftime_0.2-0-6_amd64.buildinfo Files: 30a77a7ec3b799cf23e8b64372ddb767 2257 gnu-r optional r-cran-sftime_0.2-0-6.dsc 2314fdbb7a215b3f442bc6fc4dd65852 2804 gnu-r optional r-cran-sftime_0.2-0-6.debian.tar.xz 4d1e3ce0e765afa81a1c91a09ad27e62 12266 gnu-r optional r-cran-sftime_0.2-0-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmiqsRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtFtqQ/+NheXW7po33jbzoTuuMPQPEMZToQavzm6 rZEnS+/S8LFvcftEyr9gCOl3NKGR2Lk31YU0ZEqpVytqP29jm05nf6QqT56F0aRd ojjS5ufwFkew9mTbvWZhc7aKdHK7D2ZiY4p8kH5rYrPMH48+6y80eqlnCh4xUwB6 oUsS5MZhbAsnchqgXce/MoiLUDdlSPyD/VFpw6ohG/sl2u0/Orb2w2Z2WuX1ZaRc r4UpnALfyRKXiRd62iBsAGXlVRoTIY4OEnHba4fD+Hxbqe32q5b3aZk1+7IQR2+D MA8CaWrYECUhVZR2u3uJHUtXzCDwdUAdZKNw6NoYfkEzN6z4tW/O0pHAzWv9ChvN 5r0WOXnqXl+AaO3KjWp9EhidSY9Pcbqw2sgeXXeXiSBXVSJCBYZpagqQ12roiLYq CMEfna6kChvbt0EVPQpZgNcZrj3c/COAyK/NCBZQWNGr4GnKIIlRvqJrvTCl9t2p eDZcPKEiwQ0El9bunoW9Zpx9vA8xWruvbJ53FvsZiJ98NktbuYWt+A/duPgfa3UI AUbD5Cxt70a0g2kT0Cu4VWkBEA8zfbdLW5ulCEyrpKJh2nm+yODv6eBoyieS0V7k r/M1riGqqpiYJEMNb/5GQPk81eIMQU5M1Ewuoh1Khlbn5ZyzoY4BpGPgMYnMKnY0 dp8fMa6OO0E= =3B5O -END PGP SIGNATURE End Message ---
Bug#1039662: marked as done (r-cran-sjmisc: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 09:23:05 +
with message-id
and subject line Bug#1039662: fixed in r-cran-sjmisc 2.8.9-2
has caused the Debian Bug report #1039662,
regarding r-cran-sjmisc: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-sjmisc
Version: 2.8.9-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
93s [ FAIL 10 | WARN 2 | SKIP 9 | PASS 148 ]
93s
93s ══ Skipped tests
═══
93s • empty test (6)
93s • On CRAN (3)
93s
93s ══ Failed tests
93s ── Error ('test-frq-weights.R:16'): frq-weights
93s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of native symbols
93s Backtrace:
93s ▆
93s 1. └─sjmisc::frq(efc, e16sex) at test-frq-weights.R:16:2
93s 2. └─sjmisc:::frq_helper(...)
93s 3. ├─base::suppressMessages(dplyr::full_join(dat, dat2))
93s 4. │ └─base::withCallingHandlers(...)
93s 5. ├─dplyr::full_join(dat, dat2)
93s 6. └─dplyr:::full_join.data.frame(dat, dat2)
93s 7. └─dplyr:::join_mutate(...)
93s 8. ├─base::`[<-`(`*tmp*`, new_rows, names(y_key), value =
``)
93s 9. └─tibble:::`[<-.tbl_df`(`*tmp*`, new_rows, names(y_key),
value = ``)
93s 10. └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
93s 11. └─tibble:::tbl_subassign_row(xj, i, value, i_arg,
value_arg)
93s 12. ├─base::withCallingHandlers(...)
93s 13. └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
93s ── Error ('test-frq.R:9'): frq
─
93s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of native symbols
93s Backtrace:
93s ▆
93s 1. ├─testthat::expect_is(frq(efc$e42dep), class = "list") at
test-frq.R:9:2
93s 2. │ └─testthat::quasi_label(enquo(object), label, arg = "object")
93s 3. │ └─rlang::eval_bare(expr, quo_get_env(quo))
93s 4. └─sjmisc::frq(efc$e42dep)
93s 5. └─sjmisc:::frq_helper(...)
93s 6. ├─base::suppressMessages(dplyr::full_join(dat, dat2))
93s 7. │ └─base::withCallingHandlers(...)
93s 8. ├─dplyr::full_join(dat, dat2)
93s 9. └─dplyr:::full_join.data.frame(dat, dat2)
93s 10. └─dplyr:::join_mutate(...)
93s 11. ├─base::`[<-`(`*tmp*`, new_rows, names(y_key), value =
``)
93s 12. └─tibble:::`[<-.tbl_df`(`*tmp*`, new_rows, names(y_key),
value = ``)
93s 13. └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
93s 14. └─tibble:::tbl_subassign_row(xj, i, value, i_arg,
value_arg)
93s 15. ├─base::withCallingHandlers(...)
93s 16. └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
93s ── Error ('test-frq.R:13'): frq
93s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of native symbols
93s Backtrace:
93s ▆
93s 1. ├─testthat::expect_is(frq(efc$e42dep, sort.frq = "asc"), class =
"list") at test-frq.R:13:2
93s 2. │ └─testthat::quasi_label(enquo(object), label, arg = "object")
93s 3. │ └─rlang::eval_bare(expr, quo_get_env(quo))
93s 4. └─sjmisc::frq(efc$e42dep, sort.frq = "asc")
93s 5. └─sjmisc:::frq_helper(...)
93s 6. ├─base::suppressMessages(dplyr::full_join(dat, dat2))
93s 7. │ └─base::withCallingHandlers(...)
93s 8. ├─dplyr::full_join(dat, dat2)
93s 9. └─dplyr:::full_join.data.frame(dat, dat2)
93s 10. └─dplyr:::join_mutate(...)
93s 11. ├─base::`[<-`(`*tmp*`, new_rows, names(y_key), value =
``)
93s 12. └─tibble:::`[<-.tbl_df`(`*tmp*`, new_rows, names(y_key),
value = ``)
93s 13. └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
93s 14. └─tibble:::tbl_subassign_row(xj, i, value, i_arg,
value_arg)
93s 15. ├─base::withCallingHandlers(...)
93s 16. └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
93s ── Error ('test-frq.R:17'): frq
93s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of
Bug#1039671: marked as done (r-cran-thematic: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 09:05:28 +
with message-id
and subject line Bug#1039671: fixed in r-cran-thematic 0.1.2.1-4
has caused the Debian Bug report #1039671,
regarding r-cran-thematic: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-thematic
Version: 0.1.2.1-3
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
51s [ FAIL 12 | WARN 1 | SKIP 4 | PASS 27 ]
51s
51s ══ Skipped tests
═══
51s • gridExtra cannot be loaded (1)
51s • On CRAN (1)
51s • patchwork cannot be loaded (1)
51s • sf cannot be loaded (1)
51s
51s ══ Failed tests
51s ── Error ('test-base.R:9'): base baselines
─
51s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
51s always_valid)`: Graphics API version mismatch
51s Backtrace:
51s ▆
51s 1. └─thematic:::expect_doppelganger(...) at test-base.R:9:2
51s 2. └─vdiffr::expect_doppelganger(name, p, ...) at
tests/testthat/helper-vdiffr.R:12:2
51s 3. └─vdiffr (local) writer(fig, testcase, title)
51s 4. └─vdiffr:::svglite(file)
51s 5. └─vdiffr:::svglite_(...)
51s ── Error ('test-ggplot.R:31'): ggplot baselines
51s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
51s always_valid)`: Graphics API version mismatch
51s Backtrace:
51s ▆
51s 1. └─thematic:::expect_doppelganger(...) at test-ggplot.R:31:2
51s 2. └─vdiffr::expect_doppelganger(name, p, ...) at
tests/testthat/helper-vdiffr.R:12:2
51s 3. └─vdiffr (local) writer(fig, testcase, title)
51s 4. └─vdiffr:::svglite(file)
51s 5. └─vdiffr:::svglite_(...)
51s ── Error ('test-ggplot.R:149'): Scale defaults can be overridden
───
51s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
51s always_valid)`: Graphics API version mismatch
51s Backtrace:
51s ▆
51s 1. └─thematic:::expect_doppelganger(...) at test-ggplot.R:149:2
51s 2. └─vdiffr::expect_doppelganger(name, p, ...) at
tests/testthat/helper-vdiffr.R:12:2
51s 3. └─vdiffr (local) writer(fig, testcase, title)
51s 4. └─vdiffr:::svglite(file)
51s 5. └─vdiffr:::svglite_(...)
51s ── Error ('test-ggplot.R:225'): element_blank() inherits properly
──
51s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
51s always_valid)`: Graphics API version mismatch
51s Backtrace:
51s ▆
51s 1. └─thematic:::expect_doppelganger(...) at test-ggplot.R:225:2
51s 2. └─vdiffr::expect_doppelganger(name, p, ...) at
tests/testthat/helper-vdiffr.R:12:2
51s 3. └─vdiffr (local) writer(fig, testcase, title)
51s 4. └─vdiffr:::svglite(file)
51s 5. └─vdiffr:::svglite_(...)
51s ── Error ('test-ggthemes.R:12'): works as expected with global ggthemes
51s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
51s always_valid)`: Graphics API version mismatch
51s Backtrace:
51s ▆
51s 1. └─thematic:::expect_doppelganger("ggtheme-void", qplot(1:10)) at
test-ggthemes.R:12:2
51s 2. └─vdiffr::expect_doppelganger(name, p, ...) at
tests/testthat/helper-vdiffr.R:12:2
51s 3. └─vdiffr (local) writer(fig, testcase, title)
51s 4. └─vdiffr:::svglite(file)
51s 5. └─vdiffr:::svglite_(...)
51s ── Error ('test-ggthemes.R:27'): works as expected with plot-specific
themes ───
51s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
51s always_valid)`: Graphics API version mismatch
51s Backtrace:
51s ▆
51s 1. └─thematic:::expect_doppelganger("purple-strip", p) at
test-ggthemes.R:27:2
51s 2. └─vdiffr::expect_doppelganger(name, p, ...) at
tests/testthat/helper-vdiffr.R:12:2
51s 3. └─vdiffr (local) writer(fig, testcase, title)
51s 4. └─vdiffr:::svglite(file)
51s 5. └─vdiffr:::svglite_(...)
51s ── Error ('test-ggthemes.R:56'): Global ggthemes are respected
─
51s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
51s always_valid)`: Graphics API version mismatch
51s Backtrace:
51s ▆
51s 1.
Bug#1039670: marked as done (r-cran-unitizer: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 09:05:53 +
with message-id
and subject line Bug#1039670: fixed in r-cran-unitizer 1.4.19-2
has caused the Debian Bug report #1039670,
regarding r-cran-unitizer: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-unitizer
Version: 1.4.18-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
47s --- t-get.Rout.save_ 2023-06-28 00:18:14.856968786 +
47s +++ t-get.Rout_2023-06-28 00:18:14.860968876 +
47s @@ -39,7 +39,7 @@
47s Error in set_unitizer.character(letters) :
47sArgument `store.id` must be a 1 length character vector
47s > try(set_unitizer("a"))
47s -Error in is(unitizer, "unitizer") :
47s +Error in set_unitizer.character("a") :
47sargument "unitizer" is missing, with no default
47s > try(set_unitizer("a", "blergh"))
47s Error in set_unitizer.character("a", "blergh") :
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-unitizer/34918112/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-unitizer
Source-Version: 1.4.19-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-unitizer, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-unitizer package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 10:21:54 +0200
Source: r-cran-unitizer
Architecture: source
Version: 1.4.19-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1039670
Changes:
r-cran-unitizer (1.4.19-2) unstable; urgency=medium
.
* Rebuild with r-graphics-engine set by r-base
Closes: #1039670
Checksums-Sha1:
20c546380672256959e435f246145aff957a0cd9 2152 r-cran-unitizer_1.4.19-2.dsc
6272b67213fedcc73891cbfc21cbcc5877af3bf1 3388
r-cran-unitizer_1.4.19-2.debian.tar.xz
d085006327d7349c9a8affce5731771b6409ab3e 10455
r-cran-unitizer_1.4.19-2_amd64.buildinfo
Checksums-Sha256:
5b153c6d38572f36cebc90b414e3cee1e2f58a5affd216a17dc7aa33bc12b299 2152
r-cran-unitizer_1.4.19-2.dsc
28ba57d9f3e31930825dc42b006aa23e6fb12f0d4131a4cc628d08133232 3388
r-cran-unitizer_1.4.19-2.debian.tar.xz
9990b3c12b693783d2b10f810ffaf0fd36cded52f66ed7fd4ab1f3d532b78c7e 10455
r-cran-unitizer_1.4.19-2_amd64.buildinfo
Files:
6110ce9017421f6cabc6c0610eec 2152 gnu-r optional
r-cran-unitizer_1.4.19-2.dsc
66461e0ac7c8398f4be7a3e6f20f9e01 3388 gnu-r optional
r-cran-unitizer_1.4.19-2.debian.tar.xz
5c75d835fefb1a71f2143df139ce1242 10455 gnu-r optional
r-cran-unitizer_1.4.19-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmfRcRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGydA//Terc9r9Tp4ObuFqa/iXEmi/kR1jeJe4O
94Zee+FYuhnU4QORdIfkz/qblMsTDQOu16qiwzJrlK3qDfCtHidPfhhtZECvje0I
mKkysMlCjrY2p64PSo/AX0RypstgzGTtcTnZfX08YufrVe3O9EYgdobp1u4wlO3x
Yir5toUXyQuoJKBaM0vRhiDZ2D5MsMHju84AH9j5ySlZ1mwW81/QmMdsmH6n8YPv
Ed/TFqHMmy465WPLrZehWA0nf6RwDiUJo2Et9FiYBeRRTK8ZHNwd3g8faMLzzFtk
Okes6rcA6ndry8aodGnIn2InNZvfZ9bz/qbWJbwUjmtoBE5vPS5zqd/UbA93DfPa
weW11UcXF2YtYcKCBCPRJGUImK6ip+3J2iz9jcmrP5McYY7U4x8u5kdRm+PuKuRt
xekaAFwSL6J0SbUMI0dXoyP9OxpUVjzSncve1CjgZNMwtqJoOyX7biqmI9cR50uR
w5FMzYqibJKtzNtx6ahh81uGfj9zwr1pdx/1rWWm8aYY/OtSdkdxDwCSUW54QVlh
65+dbGhjhKzWYKW57eW3z7HlvQapHNS137A6I8/qc0+o1bcrFa3EKRaFuIt1Iu5h
OeQIDMUq4byC+TfIiyNm7jgK+ygY3XAJdUDhQNaP2/D95UsJ5CYAp7wo3w5nsrvn
L/xPNtL/eoE=
=vZa3
-END PGP SIGNATURE End Message ---
Bug#1039665: marked as done (r-cran-treespace: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 09:05:44 +
with message-id
and subject line Bug#1039665: fixed in r-cran-treespace 1.1.4.2+dfsg-2
has caused the Debian Bug report #1039665,
regarding r-cran-treespace: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-treespace
Version: 1.1.4.1+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
82s [ FAIL 2 | WARN 0 | SKIP 0 | PASS 45 ]
82s
82s == Failed tests
83s -- Failure ('testbasics.R:120'): error is given if lambda is outside of
[0,1] --
83s `medTree(trees, -1)` did not throw an error.
83s -- Failure ('testbasics.R:121'): error is given if lambda is outside of
[0,1] --
83s `medTree(trees, 2)` did not throw an error.
83s
83s [ FAIL 2 | WARN 0 | SKIP 0 | PASS 45 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-treespace/34918485/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-treespace
Source-Version: 1.1.4.2+dfsg-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-treespace, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-treespace package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 10:22:33 +0200
Source: r-cran-treespace
Architecture: source
Version: 1.1.4.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1039665
Changes:
r-cran-treespace (1.1.4.2+dfsg-2) unstable; urgency=medium
.
* Rebuild with r-graphics-engine set by r-base
Closes: #1039665
Checksums-Sha1:
baf327abc4a8b69b58550d0983c4815678a8e525 2460
r-cran-treespace_1.1.4.2+dfsg-2.dsc
6d598bfa632666c2dac9e3c0f699f9366f04d353 3692
r-cran-treespace_1.1.4.2+dfsg-2.debian.tar.xz
77126ad7bddb4758c6254cad25efa8cba08ff70e 17891
r-cran-treespace_1.1.4.2+dfsg-2_amd64.buildinfo
Checksums-Sha256:
bc66f9e60fa84289ce846dd355a6d8573e20244fffce72a0aad9776168950963 2460
r-cran-treespace_1.1.4.2+dfsg-2.dsc
43162c53b07a61a23ad6558b4820df33dbac3a997da73b6fdd1aa07c8ca89e44 3692
r-cran-treespace_1.1.4.2+dfsg-2.debian.tar.xz
5becaf409d94c36605088b50ee7263e922a2c7acb3e722cfd0bcb16e1945b6b8 17891
r-cran-treespace_1.1.4.2+dfsg-2_amd64.buildinfo
Files:
6cbf67eed5f27155ad462cf31ce57765 2460 gnu-r optional
r-cran-treespace_1.1.4.2+dfsg-2.dsc
f23727f58518d3b46eb86ee004fd66fe 3692 gnu-r optional
r-cran-treespace_1.1.4.2+dfsg-2.debian.tar.xz
ba5d9778b1cbb2c7e5580e6940846e87 17891 gnu-r optional
r-cran-treespace_1.1.4.2+dfsg-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmfKwRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtF7Fw//coD222+S8sPa+9YjmXjF9h+NHyLe8Dij
l05vQdORt7suCuJFkNGWfu3wyg9lgLmoCkrr3D0RSpkiZ0xpcs5H532ipNzmPdqE
RPVWrnUYaHcL1rT8STvQQpG6c6HqG2IzZi2kkhWIY/bIEy5+zY3yLR0MsVMF+Vwg
c7BQ/EVnBesgZIu3anbEx1DB5FmcjHPjVW0ovhTnG6J8o9j4zH+3ra3nJyn6k6Z3
YYw+QZ8fGhKQ2wlWLC71tXojUoTZXd1rahltalKMoHPTiYX5GcRCj/xFkIpb5Wjd
8QGa563qoH8bgf/Pr+mVd9XvsYQHmX1evmlKAAZec8ehQdnt7Ku7TjBJ7wXrr+oz
zFi8vO93E/s32ATfioTcvqIf+XlD9gzscPEQrBnWF/EdmcIJEzbGy5p998HNPduK
T0fr9avoBYC4cYSQ+d0TtlhtRBM3rEpaATBDWcXxZjh/ljpcIV1vneS1SygpPRpi
BSqjaqPY2+qn9Ew4SFjUJktZIzpTSw3Bwlst4kHGIiJWB6NDcg8TXT9SVH57hwNg
vT35hgn3JcYnjdoG+ebqqa8/kxdVhUN9iBYHxVHbdJ5kbuaPVKiyndEUlNrjlwlA
p59SfjsGA4CZ0bGSbc5/oJqvuG937Up1W6yv7Z35fN2cq0CboWQQu6UjpJAsF23V
XpItDwxtBGA=
=//uV
-END PGP SIGNATURE End Message ---
Bug#1040375: libssr-glinject.so from newest git version works
sudo apt build-dep simplescreenrecorder sudo apt install git mesa-utils simplescreenrecorder git clone --depth=1https://github.com/MaartenBaert/ssr cd ssr sudo --reset-timestamp ENABLE_32BIT_GLINJECT=FALSE ./simple-build-and-install # press Ctrl+C when it asks password LD_PRELOAD=build-release/glinject/libssr-glinject.so /usr/bin/true # no segmentation fault! build-release/src/simplescreenrecorder & LD_PRELOAD=build-release/glinject/libssr-glinject.so glxgears # works and can record opengl simplescreenrecorder & LD_PRELOAD=build-release/glinject/libssr-glinject.so glxgears # simplescreenrecorder from apt also works and can record opengl
Bug#1040297: gnome: Gnome fails to start on login and falls back to GDM3
On Wed, 05 Jul 2023 at 22:44:40 +0200, Bastian Venthur wrote: > Start-Date: 2023-07-03 09:06:13 Unfortunately this upgrade was sufficiently large that it's hard to spot which package might have triggered this. Nothing jumps out at me as a particularly likely trigger. Maaaybe glibc, or the evolution family of packages? > Here are also two outputs of coredumpctl that appeared after a crash: > Stack trace of thread 3960: ... > #3 0x7f134cbbb0ff g_log (libglib-2.0.so.0 + 0x5c0ff) > #4 0x7f134cbb96a2 g_malloc (libglib-2.0.so.0 + 0x5a6a2) > #5 0x7f134cbe97ce g_utf8_collate_key (libglib-2.0.so.0 > + 0x8a7ce) > #6 0x7f134ccee180 e_source_set_display_name > (libedataserver-1.2.so.27 + 0x57180) Well, this is messed up - something is setting the display name of an ESource (a calendar or address book or something similar) to a value that is, apparently, so long that allocating memory for its collation key (a version that has been modified to sort in the correct locale-sensitive order) will fail. A display name that large is clearly absurd, so all I can think of is that the `result_len` or `xfrm_len` in g_utf8_collate_key() (depending which code path we're in) might have been calculated incorrectly? > Stack trace of thread 3710: ... > #7 0x7f539ead20ff g_log (libglib-2.0.so.0 + 0x5c0ff) > #8 0x7f539ead06a2 g_malloc (libglib-2.0.so.0 + 0x5a6a2) > #9 0x7f539eb007ce g_utf8_collate_key (libglib-2.0.so.0 > + 0x8a7ce) > #10 0x7f539ee22d65 _shell_app_set_app_info > (libgnome-shell.so + 0x22d65) Similarly this one is setting up a collation key for the name of an app (a fairly short string like "LibreOffice Writer", and again reaching OOM as a result of that is clearly absurd. Please could you try retracing these with debug symbols installed? You can either install appropriate -dbgsym packages manually, or export DEBUGINFOD_URLS=https://debuginfod.debian.net coredumpctl gdb $PID to download appropriate symbols automatically and cache them in ~/.cache/debuginfod_client. See https://wiki.debian.org/HowToGetABacktrace for more details. If you're setting this up manually, we would want to see debug symbols for at least GLib (libglib2.0-0-dbgsym) and glibc (libc6-dbg), preferably also gnome-shell-dbgsym and libedataserver-1.2-27-dbgsym. Thanks, smcv
Bug#1040406: closed by Debian FTP Masters (reply to Luca Boccassi ) (Bug#1040406: fixed in python-azure 20230705+git-1)
On Thu, 6 Jul 2023 at 09:42, Bastian Blank wrote: > > On Thu, Jul 06, 2023 at 09:39:43AM +0100, Luca Boccassi wrote: > > Yes I will bump the dependency in the next azcli upload, but I wanted > > to push the fix immediately. > > Okay. Any reason for not just merging the two into one source? Can be > automated and you don't need to think about it again. Any time python-azure is updated to a new revision it can also break azure-cli, so I'd rather keep it separate and fixed and change it only when something is actually detected that needs an uprev.
Bug#1039674: marked as done (r-cran-uwot: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 08:41:53 + with message-id and subject line Bug#1039674: fixed in r-cran-uwot 0.1.16-2 has caused the Debian Bug report #1039674, regarding r-cran-uwot: autopkgtest failure with r-base (4.3.1-1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1039674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-uwot Version: 0.1.14-2 Severity: serious Justification: autopkgtest failure Dear Maintainer, The autopkgtest of your package fails with r-base (4.3.1-1): 35s Error in FNN::get.knn(X, k) : DLL requires the use of native symbols 35s Calls: test_check ... eval -> create_data -> find_nn -> FNN_nn -> https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-uwot/34918501/log.gz --- End Message --- --- Begin Message --- Source: r-cran-uwot Source-Version: 0.1.16-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-cran-uwot, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1039...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-uwot package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 06 Jul 2023 10:08:42 +0200 Source: r-cran-uwot Architecture: source Version: 0.1.16-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 1039674 Changes: r-cran-uwot (0.1.16-2) unstable; urgency=medium . * Rebuild with r-graphics-engine set by r-base Closes: #1039674 Checksums-Sha1: b054e4f5e6f26aeb850f90ada1863de3c857e57a 2246 r-cran-uwot_0.1.16-2.dsc f3fa0663f1bc9278b87cf6e2e7136773b8856a83 3148 r-cran-uwot_0.1.16-2.debian.tar.xz ccadbdc00ce03f10c19a7123b4bfed34ef0b4869 11252 r-cran-uwot_0.1.16-2_amd64.buildinfo Checksums-Sha256: 835ea0519c54c9424c45f379983884d49be7b818db6229f0bf5089456b24ce89 2246 r-cran-uwot_0.1.16-2.dsc 19de2696d65ba3df730779d5b85efa9e9314a78479e404a0356715244410def8 3148 r-cran-uwot_0.1.16-2.debian.tar.xz 7a6a114698695986acac28d217804d5ed03fc7bf2b138496c6dfb66c2c4e8f0b 11252 r-cran-uwot_0.1.16-2_amd64.buildinfo Files: d16595264a4e6303dc346d5872d9366f 2246 gnu-r optional r-cran-uwot_0.1.16-2.dsc 35f153bb9b94d7a653c27b46e7ff1410 3148 gnu-r optional r-cran-uwot_0.1.16-2.debian.tar.xz 84332d1b6f49f6b77062910ab71a8744 11252 gnu-r optional r-cran-uwot_0.1.16-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmd6cRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGTdhAAiTU1NzLMf8F7m7xIKSWRPPQA00Ygw0c4 JeaNk8XpAG69EmOnnnP+RNOJ4PjcFVRFT/VB1LUzSgHZzRF69ao+fDmb2LvzTxOR veHXrRe5VNp0c+X1UAGu1qTYyejh7qV1J7PBYhLcIhFWTAkGf9GxA98j8lnHmddT 59zcQ0730BDneSalzz1pQN1jg/wZ66VKpwPox3xYQ4mCBoWSqaK9/vhOk7VZQ9xX iVeHTRXjOyIVRnrlNfOoUW5AuRZ+zJKmnnTXj8DKGNJZa8mCZKSAORoDIaa/9MAo ACsHFgOatbGRJ5bEYhRP2ewJgv3kBMFmhBSnOZJ6w65N/Q5sXmBb6yOt73NWNt6B q8YkmDfrjE0Kjh1PtnRHxmqudPInHo2MzlrEI8aRxsepX20dYmst/5uYHYDj6fW3 M6NKfksv/CBJRiN1MUXDA9mgeKAUTf66wHbUJQy7MTCwDlNKRr6HKEA0l/ySu7Ws sHTX43qn04Ax5gSbRhaC+qVm3aeZOpR2EcLdV5JXvV3Q46zycNNBR4vB+QwPjsqq mRMGAmUBjJoSkGtqbhLQ8IiR/jgy/vaRDI+mNqmKBC9JObzoTziAe8/XIJQukNnd jpqY/LewPkZafPzxi18J9vF9HLMbgiw5P/yNh0b8Il8nE0670VPLLaj5pT8DOSez 1rOfR+qXOVY= =9Fpw -END PGP SIGNATURE End Message ---
Bug#1039667: marked as done (r-cran-xopen: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 08:42:32 +
with message-id
and subject line Bug#1039667: fixed in r-cran-xopen 1.0.0+dfsg-1
has caused the Debian Bug report #1039667,
regarding r-cran-xopen: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-xopen
Version: 1.0.0-2
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
30s == Failed
==
30s -- 1. Error ('test.R:4'): (code run outside of `test_that()`)
--
30s Error in `not_null(.Call("psll_connections", p))`: DLL requires the use of
native symbols
30s Backtrace:
30s 1. testthat::test_that(...)
30sat test.R:4:0
30s 2. testthat:::test_code(desc, code, env = parent.frame(), reporter =
reporter)
30s 3. reporter$start_test(context = reporter$.context, test = test)
30s 4. testthat:::o_apply(self$reporters, "start_test", context, test)
30s 5. base::lapply(objects, f)
30s 6. testthat (local) FUN(X[[i]], ...)
30s 7. x$start_test(...)
30s 8. ps::ps_connections(ps_handle())
30s 9. ps:::psl_connections(p)
30s 10. ps:::not_null(.Call("psll_connections", p))
30s
30s == DONE
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-xopen/34916789/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-xopen
Source-Version: 1.0.0+dfsg-1
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-xopen, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-xopen package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 10:11:01 +0200
Source: r-cran-xopen
Architecture: source
Version: 1.0.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 969765 1039667
Changes:
r-cran-xopen (1.0.0+dfsg-1) unstable; urgency=medium
.
* Team upload.
.
[ Dylan Aïssi ]
* Remove embedded xdg-open and link to xdg-utils instead (closes: #969765)
.
[ Andreas Tille ]
* Rebuild with r-graphics-engine set by r-base
Closes: #1039667
* Standards-Version: 4.6.2 (routine-update)
* debhelper-compat 13 (routine-update)
* Reorder sequence of d/control fields by cme (routine-update)
Checksums-Sha1:
e792f9177e02e0a0cc11c72a9f9e82d4d80984ca 2124 r-cran-xopen_1.0.0+dfsg-1.dsc
eb299785893eaca1023f29edf8b2aa12337ddbb5 4192
r-cran-xopen_1.0.0+dfsg.orig.tar.xz
f93191939bd1f5ce0ff61ab38d17c2d4623705c5 2668
r-cran-xopen_1.0.0+dfsg-1.debian.tar.xz
df39198627a05ff26bf88f81ff170820b13a6124 10472
r-cran-xopen_1.0.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
1077d14a56fe249fa351490c430ad5b3a8d5ad8a49f622828ed0b2f020e193ce 2124
r-cran-xopen_1.0.0+dfsg-1.dsc
4dd1bba6f3c718e4ebf133ef5ecf9a666315c4c1e226c99d47d4ca7118821b01 4192
r-cran-xopen_1.0.0+dfsg.orig.tar.xz
37c12469bf98b766b2bc3cf266510deda29d3c33d9f17005985644bc326dba0c 2668
r-cran-xopen_1.0.0+dfsg-1.debian.tar.xz
5b67464cf2110be07e61dc86e3ec9772e86a4a4e247f0ec73c9393a57f8da68f 10472
r-cran-xopen_1.0.0+dfsg-1_amd64.buildinfo
Files:
79a85b82be6b8c6fd42b25abb3bf3592 2124 gnu-r optional
r-cran-xopen_1.0.0+dfsg-1.dsc
2065cb3131eae4e82536320411f5a04a 4192 gnu-r optional
r-cran-xopen_1.0.0+dfsg.orig.tar.xz
5e862cdfa7ae2bc84eea964adeaa4be9 2668 gnu-r optional
r-cran-xopen_1.0.0+dfsg-1.debian.tar.xz
8e5ae2b55bcdef9e5bc534be352cbf27 10472 gnu-r optional
r-cran-xopen_1.0.0+dfsg-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmd3oRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtG0Sg/+ONIBOvZ8y+OQFigUobHAswd9UQtD44m3
+YFXIgvKULWyiUr43p68jlLXW42z/xeyAswNiCKrFzBi4Ioi+hqq1Qhf1ElI9u0p
Bug#1040406: closed by Debian FTP Masters (reply to Luca Boccassi ) (Bug#1040406: fixed in python-azure 20230705+git-1)
On Thu, Jul 06, 2023 at 09:39:43AM +0100, Luca Boccassi wrote: > Yes I will bump the dependency in the next azcli upload, but I wanted > to push the fix immediately. Okay. Any reason for not just merging the two into one source? Can be automated and you don't need to think about it again. Bastian -- Intuition, however illogical, is recognized as a command prerogative. -- Kirk, "Obsession", stardate 3620.7
Processed: RM: ruby-gollum-lib -- ROM; incompatible with newer ruby-rouge
Processing control commands: > affects -1 + src:ruby-gollum-lib Bug #1040461 [ftp.debian.org] RM: ruby-gollum-lib -- ROM; incompatible with newer ruby-rouge Added indication that 1040461 affects src:ruby-gollum-lib > block 1040405 by -1 Bug #1040405 [src:ruby-gollum-lib] ruby-gollum-lib: incompatible with newer ruby-rouge 1040405 was not blocked by any bugs. 1040405 was not blocking any bugs. Added blocking bug(s) of 1040405: 1040461 -- 1040405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040405 1040461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1039664: closed by Andreas Tille (Re: Bug#1039664: r-cran-tikzdevice: autopkgtest failure with r-base (4.3.1-1))
Andreas Tille wrote: Done in 0.12.4-3 This does not mark the bug as fixed in that version. Use a version header at the top of your email: Version: 0.12.4-3 Or use the control commands: https://www.debian.org/Bugs/server-control#fixed Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1039881: marked as done (r-cran-rsample: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 08:39:41 +
with message-id
and subject line Bug#1039881: fixed in r-cran-rsample 1.1.1+dfsg-2
has caused the Debian Bug report #1039881,
regarding r-cran-rsample: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-rsample
Version: 1.1.1+dfsg-1
Severity: serious
Tags: sid trixie
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
64s [ FAIL 2 | WARN 0 | SKIP 41 | PASS 2818 ]
64s
64s ══ Skipped tests (41)
══
64s • On CRAN (41): 'test-boot.R:121:3', 'test-boot.R:147:3',
'test-boot.R:158:3',
64s 'test-bootci.R:18:3', 'test-bootci.R:137:3', 'test-bootci.R:236:3',
64s 'test-clustering.R:41:3', 'test-clustering.R:52:3',
64s 'test-compat-vctrs.R:125:5', 'test-compat-vctrs.R:134:5',
64s 'test-initial.R:35:3', 'test-initial.R:110:3', 'test-labels.R:19:3',
64s 'test-loo.R:25:3', 'test-make_groups.R:41:5', 'test-mc.R:81:3',
64s 'test-mc.R:99:3', 'test-mc.R:145:3', 'test-mc.R:214:3',
'test-mc.R:218:3',
64s 'test-misc.R:17:3', 'test-misc.R:129:5', 'test-misc.R:154:3',
64s 'test-nesting.R:42:3', 'test-nesting.R:81:3', 'test-permutations.R:33:3',
64s 'test-permutations.R:44:3', 'test-rsplit.R:37:3', 'test-rsplit.R:52:3',
64s 'test-strata.R:37:3', 'test-validation.R:58:3',
'test-validation.R:109:3',
64s 'test-validation.R:207:3', 'test-vfold.R:72:3', 'test-vfold.R:81:3',
64s 'test-vfold.R:91:3', 'test-vfold.R:113:3', 'test-vfold.R:206:3',
64s 'test-vfold.R:249:3', 'test-vfold.R:349:3', 'test-vfold.R:353:3'
64s
64s ══ Failed tests
65s ── Error ('test-compat-dplyr.R:357:5'): right_join() restores to the type
of first input ──
65s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of native symbols
65s Backtrace:
65s ▆
65s 1. ├─rsample:::expect_s3_class_bare_tibble(right_join(y, x, by = "id"))
at test-compat-dplyr.R:357:4
65s 2. │ └─testthat::expect_s3_class(...) at
autopkgtest_tmp/testthat/helpers-rsample.R:11:2
65s 3. │ └─testthat::quasi_label(enquo(object), arg = "object")
65s 4. │ └─rlang::eval_bare(expr, quo_get_env(quo))
65s 5. ├─dplyr::right_join(y, x, by = "id")
65s 6. └─dplyr:::right_join.data.frame(y, x, by = "id")
65s 7. └─dplyr:::join_mutate(...)
65s 8. ├─base::`[<-`(`*tmp*`, new_rows, names(y_key), value =
``)
65s 9. └─tibble:::`[<-.tbl_df`(`*tmp*`, new_rows, names(y_key), value =
``)
65s 10. └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
65s 11. └─tibble:::tbl_subassign_row(xj, i, value, i_arg, value_arg)
65s 12. ├─base::withCallingHandlers(...)
65s 13. └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
65s ── Error ('test-compat-dplyr.R:373:5'): full_join() can lose rset class if
rows are added ──
65s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of native symbols
65s Backtrace:
65s ▆
65s 1. ├─rsample:::expect_s3_class_bare_tibble(full_join(x, y, by = "id"))
at test-compat-dplyr.R:373:4
65s 2. │ └─testthat::expect_s3_class(...) at
autopkgtest_tmp/testthat/helpers-rsample.R:11:2
65s 3. │ └─testthat::quasi_label(enquo(object), arg = "object")
65s 4. │ └─rlang::eval_bare(expr, quo_get_env(quo))
65s 5. ├─dplyr::full_join(x, y, by = "id")
65s 6. └─dplyr:::full_join.data.frame(x, y, by = "id")
65s 7. └─dplyr:::join_mutate(...)
65s 8. ├─base::`[<-`(`*tmp*`, new_rows, names(y_key), value =
``)
65s 9. └─tibble:::`[<-.tbl_df`(`*tmp*`, new_rows, names(y_key), value =
``)
65s 10. └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
65s 11. └─tibble:::tbl_subassign_row(xj, i, value, i_arg, value_arg)
65s 12. ├─base::withCallingHandlers(...)
65s 13. └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
65s
65s [ FAIL 2 | WARN 0 | SKIP 41 | PASS 2818 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-rsample/34931855/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-rsample
Source-Version: 1.1.1+dfsg-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-rsample, which is due
Bug#1039880: marked as done (r-cran-plotly: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 08:39:01 +
with message-id
and subject line Bug#1039880: fixed in r-cran-plotly 4.10.2+dfsg-2
has caused the Debian Bug report #1039880,
regarding r-cran-plotly: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-plotly
Version: 4.10.1+dfsg-2
Severity: serious
Tags: sid trixie
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
130s [ FAIL 1 | WARN 11 | SKIP 48 | PASS 1093 ]
130s
130s == Skipped tests
===
130s * Just ignore this test (2)
130s * On CRAN (4)
130s * empty test (31)
130s * ggalluvial cannot be loaded (1)
130s * has_mapbox() is not TRUE (9)
130s * rgeos cannot be loaded (1)
130s
130s == Failed tests
130s -- Error ('test-plotly-group.R:13'): (code run outside of `test_that()`)
---
130s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires
the use of native symbols
130s Backtrace:
130s x
130s 1. +-base::`[<-`(`*tmp*`, isMissing, , value = ``) at
test-plotly-group.R:13:0
130s 2. \-tibble:::`[<-.tbl_df`(`*tmp*`, isMissing, , value = ``) at
test-plotly-group.R:13:0
130s 3. \-tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
130s 4. \-tibble:::tbl_subassign_row(x, i, value, i_arg, value_arg)
130s 5. +-base::withCallingHandlers(...)
130s 6. \-tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
130s
130s [ FAIL 1 | WARN 11 | SKIP 48 | PASS 1093 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-plotly/34941374/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-plotly
Source-Version: 4.10.2+dfsg-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-plotly, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-plotly package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 09:59:33 +0200
Source: r-cran-plotly
Architecture: source
Version: 4.10.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1039880
Changes:
r-cran-plotly (4.10.2+dfsg-2) unstable; urgency=medium
.
* Rebuild with r-graphics-engine set by r-base
Closes: #1039880
Checksums-Sha1:
a641dccfb0a3936db0e022df5453d84745227dd6 2644 r-cran-plotly_4.10.2+dfsg-2.dsc
57b80bff7dcc54a3038bee593a97062ad2089d2d 1508236
r-cran-plotly_4.10.2+dfsg-2.debian.tar.xz
8a4b500277753057f406688ee0af65df46cbc519 13863
r-cran-plotly_4.10.2+dfsg-2_amd64.buildinfo
Checksums-Sha256:
89411b209c94bfa53368b00d347f27cd7fedd4f740c07cdb72733c830c6c9ec1 2644
r-cran-plotly_4.10.2+dfsg-2.dsc
d2d074d2217d934b921efc5b9526dc05f1699dff1989e889d64c9f6239b84346 1508236
r-cran-plotly_4.10.2+dfsg-2.debian.tar.xz
96dac58fca0e66084217cef59adba2f10eba97a17a6cd7036a63f4a740cc5c1f 13863
r-cran-plotly_4.10.2+dfsg-2_amd64.buildinfo
Files:
f414f93e1e4d3ed6815860b8ed71838c 2644 gnu-r optional
r-cran-plotly_4.10.2+dfsg-2.dsc
ea061c7f453327afe99b1bda5882a67a 1508236 gnu-r optional
r-cran-plotly_4.10.2+dfsg-2.debian.tar.xz
57283ad1308e3b3e5fd40409b17c96d7 13863 gnu-r optional
r-cran-plotly_4.10.2+dfsg-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmdTsRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGKtA/9EBip5bpSMlgtbOBo9Utl78imvbzBPYwi
Gieqlr4Djq2OctnJTunqOozw8wq7UcB0NWmk/Zv7X/AcHM3SAuB1Hgm9MRQKjowa
8PoVoOsvcCIZ9cMqUgbcffpt9I82PhNr0Zhnus7Kwi/zIoEJYdm/V4W3QQo7HcLT
Q3Vfp9SJSvozF8t0J6p8TYJZ+jwfirDUy0hZVDWY71+DnAcQqp2fOr8me2Qe5xf6
jUXJLpBCGTOUn5XHExhTIr6HLuUlKlWvE5oVrdGOqwv+ktVEh4O0rA8Uw/LxLDOc
Q+fK1xQg7cmjuzY1+0NkKQjX03D2J9GJstZ1Nk5yNlwXs3l1fgIWSl9vBVLWTapj
Bug#1039676: marked as done (r-cran-forecast: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 08:38:40 +
with message-id
and subject line Bug#1039676: fixed in r-cran-forecast 8.21-2
has caused the Debian Bug report #1039676,
regarding r-cran-forecast: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039676
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-forecast
Version: 8.20-1
Severity: serious
Justification: autopkgtest failure
Control: close -1 8.21-1
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
134s [ FAIL 2 | WARN 86 | SKIP 1 | PASS 778 ]
134s
134s ══ Skipped tests
═══
134s • On CRAN (1)
134s
134s ══ Failed tests
134s ── Failure ('test-modelAR.R:173'): Tests for modelAR
───
134s identical(f1$upper, f2$upper) is not TRUE
134s
134s `actual`: FALSE
134s `expected`: TRUE
134s ── Failure ('test-modelAR.R:174'): Tests for modelAR
───
134s identical(f1$lower, f2$lower) is not TRUE
134s
134s `actual`: FALSE
134s `expected`: TRUE
134s
134s [ FAIL 2 | WARN 86 | SKIP 1 | PASS 778 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-forecast/34918886/log.gz
I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing.
--- End Message ---
--- Begin Message ---
Source: r-cran-forecast
Source-Version: 8.21-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-forecast, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-forecast package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 10:00:56 +0200
Source: r-cran-forecast
Architecture: source
Version: 8.21-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1039676
Changes:
r-cran-forecast (8.21-2) unstable; urgency=medium
.
* Rebuild with r-graphics-engine set by r-base
Closes: #1039676
Checksums-Sha1:
a563d466d3026d0bd0ca2226c45ea9d1858f0d78 2339 r-cran-forecast_8.21-2.dsc
568ed6ad7a357f53e88f9a92b47e6dee577f7968 3212
r-cran-forecast_8.21-2.debian.tar.xz
87296276eaa29d284f76ad2069efd4f0922749d6 12093
r-cran-forecast_8.21-2_amd64.buildinfo
Checksums-Sha256:
64baa728d66e31ad4fd4631c85bcc7c8090df07e3e5b0797eae40e5d19b48daf 2339
r-cran-forecast_8.21-2.dsc
b4e3c237976ceb95fc6be2928eec2064a5e26a4201c3d50fb568bbe37e169182 3212
r-cran-forecast_8.21-2.debian.tar.xz
8eb2947394019ebb8edb113037c59961c920a3fde764988dced329b0caa8f789 12093
r-cran-forecast_8.21-2_amd64.buildinfo
Files:
2126283d8d8d6e113deed611593f508c 2339 gnu-r optional r-cran-forecast_8.21-2.dsc
7583dbf39021d3c4f46b1f5d2a650893 3212 gnu-r optional
r-cran-forecast_8.21-2.debian.tar.xz
9c042469841e04463dac0b6351f12c5a 12093 gnu-r optional
r-cran-forecast_8.21-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmdZoRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGZGA//Vum0KJuNXQXlZ40YJmRLgMX5XZwjaSyL
ql4BNsMuj3iQS4X1zcEFXJaX3/u+yomweOdPFrvZbd0VqTL0gtIzT5E8A8JxgX+G
Q9+lAcY7IYRwx9lTYQYdWvAOinpgd7tzdMkzP4AXWRrEjaO+6AQIT58a55csaO5B
WaaG2u+ApIeJE/rEff9RXsS4bRfceyLVRf8etO14Spq+VN9gQd+RODEigmGLBWsG
REsJlYZJpg7RIgIk8w13iEXPLzZqsEHM8Ar9Wgbepzm0mUEOwr8H/OMUKEPtxvCv
RyHHpTcCvnIxqAI3+SaJ3lwJp/OLvPymgfSyktHTC28shZbjl+b8yTcRZxULcouU
MLnMhepX/ItmqVnWODCEondvTHIKIVaLw6Al9pawdiYwblEFXI0W7nj/DzkoSS8p
IogOz3cxWP+wi3eu+6J9nZLcA5nrpsNJh5+FDXpvPCMRTVrHvC6HDVdjRa23KwgF
Wfbc6fBEtzyZyOEYTdx6MqEzh1o7WQmvstfI9/M/PnK+lmxNhNIhUzZ0WBsLTK4T
vAEWpcBEpN5DiopP7qZiBGINB7HMxv8MWNhK8blaFB+yWUzaVK3h2zVmtKR6K1sF
8gd7BZ/wP1L5ceXAhepYkw+TNQ5tdVJO+SiOuRDggJqMK2xaLyDAAEqcoVf/wNdf
NTgEKKX/SyU=
=8yl2
-END PGP SIGNATURE End Message ---
Bug#1040406: closed by Debian FTP Masters (reply to Luca Boccassi ) (Bug#1040406: fixed in python-azure 20230705+git-1)
On Thu, 6 Jul 2023 at 09:14, Bastian Blank wrote: > > Hi Luca > > >* New upstream version 20230705+git (Closes: #1040406) > > Could you please describe how a new version of the azure module can fix > that? The dependency needs to be updated as well at least. > > Also, how can it be that azure-cli is updated without the corresponding > azure? Because the upstream projects are sadly an absolute mess. The mass of code in python-azure (upstream azure-sdk-for-python) is an amorphous blob without any logic or reason, with hundreds of modules that get thrown in the repository incoherently. At any give commit these modules can be incompatible with each other in unpredictable ways, so updating python-azure is like playing russian roulette, so I avoid doing it unless it becomes obviously necessary (as you noticed for the 'az vm' subcommand in the bug you filed). And to top it all, upstream azure-cli just bumps its requirements.txt on every release to whatever is available on the developer's machine that day, so it is completely unreliable and needs to be ignored. Yes I will bump the dependency in the next azcli upload, but I wanted to push the fix immediately. Honestly, if I didn't need this for $work, I'd have filed an RM bug long ago. But the upstream 'releases' are even worse and vendor everything including the full python interpreter and openssl, without any security maintenance guarantees, so I don't want to have to rely on them. Kind regards, Luca Boccassi
Bug#1039661: marked as done (r-cran-ragg: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 6 Jul 2023 10:32:36 +0200
with message-id
and subject line Re: Bug#1039661: r-cran-ragg: autopkgtest failure with r-base
(4.3.1-1)
has caused the Debian Bug report #1039661,
regarding r-cran-ragg: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-ragg
Version: 1.2.5-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
40s [ FAIL 15 | WARN 0 | SKIP 3 | PASS 0 ]
40s
40s ══ Skipped tests
═══
40s • On CRAN (3)
40s
40s ══ Failed tests
40s ── Error ('test-circle.R:11'): circle stroke works
─
40s Error in `agg_capture()`: Graphics API version mismatch
40s Backtrace:
40s ▆
40s 1. ├─base::table(render_circle(NA, "black", 2, "solid")) at
test-circle.R:11:2
40s 2. └─ragg (local) render_circle(NA, "black", 2, "solid")
40s 3. └─ragg::agg_capture() at test-circle.R:2:2
40s ── Error ('test-circle.R:28'): circle fill works
───
40s Error in `agg_capture()`: Graphics API version mismatch
40s Backtrace:
40s ▆
40s 1. ├─base::table(render_circle("black", NA, 2, "solid")) at
test-circle.R:28:2
40s 2. └─ragg (local) render_circle("black", NA, 2, "solid")
40s 3. └─ragg::agg_capture() at test-circle.R:2:2
40s ── Error ('test-jpeg.R:3'): agg_jpeg generates file
40s Error in `agg_jpeg(file)`: Graphics API version mismatch
40s Backtrace:
40s ▆
40s 1. └─ragg::agg_jpeg(file) at test-jpeg.R:3:2
40s ── Error ('test-line.R:12'): line stroke works
─
40s Error in `agg_capture()`: Graphics API version mismatch
40s Backtrace:
40s ▆
40s 1. ├─base::table(render_line("black", 14, "solid")) at test-line.R:12:2
40s 2. └─ragg (local) render_line("black", 14, "solid")
40s 3. └─ragg::agg_capture() at test-line.R:2:2
40s ── Error ('test-path.R:17'): path stroke works
─
40s Error in `agg_capture()`: Graphics API version mismatch
40s Backtrace:
40s ▆
40s 1. ├─base::table(render_path(NA, "black", 14, "solid", "round")) at
test-path.R:17:2
40s 2. └─ragg (local) render_path(NA, "black", 14, "solid", "round")
40s 3. └─ragg::agg_capture() at test-path.R:2:2
40s ── Error ('test-path.R:35'): path fill works
───
40s Error in `agg_capture()`: Graphics API version mismatch
40s Backtrace:
40s ▆
40s 1. ├─base::table(render_path("black", NA, 4, "solid", "round")) at
test-path.R:35:2
40s 2. └─ragg (local) render_path("black", NA, 4, "solid", "round")
40s 3. └─ragg::agg_capture() at test-path.R:2:2
40s ── Error ('test-png.R:3'): agg_png 8bit generates file
─
40s Error in `agg_png(file)`: Graphics API version mismatch
40s Backtrace:
40s ▆
40s 1. └─ragg::agg_png(file) at test-png.R:3:2
40s ── Error ('test-png.R:14'): agg_png 16bit generates file
───
40s Error in `agg_png(file, bitsize = 16)`: Graphics API version mismatch
40s Backtrace:
40s ▆
40s 1. └─ragg::agg_png(file, bitsize = 16) at test-png.R:14:2
40s ── Error ('test-polyline.R:13'): polyline stroke works
─
40s Error in `agg_capture()`: Graphics API version mismatch
40s Backtrace:
40s ▆
40s 1. ├─base::table(render_polyline("black", 14, "solid", "round", "round"))
at test-polyline.R:13:2
40s 2. └─ragg (local) render_polyline("black", 14, "solid", "round", "round")
40s 3. └─ragg::agg_capture() at test-polyline.R:2:2
40s ── Error ('test-ppm.R:3'): agg_ppm generates file
──
40s Error in `agg_ppm(file)`: Graphics API version mismatch
40s Backtrace:
40s ▆
40s 1. └─ragg::agg_ppm(file) at test-ppm.R:3:2
40s ── Error ('test-raster.R:12'): raster works
40s Error in `agg_capture()`: Graphics API version mismatch
40s Backtrace:
40s ▆
40s 1. ├─base::table(render_raster(image, FALSE, 0)) at test-raster.R:12:2
40s 2. └─ragg (local) render_raster(image, FALSE, 0)
40s 3. └─ragg::agg_capture() at test-raster.R:2:2
40s ── Error ('test-rect.R:12'): rect stroke works
─
40s Error in `agg_capture()`:
Processed: bug 1040256 is forwarded to https://github.com/jcelaya/hdrmerge/pull/217, tagging 1040256
Processing commands for cont...@bugs.debian.org: > forwarded 1040256 https://github.com/jcelaya/hdrmerge/pull/217 Bug #1040256 [src:hdrmerge] hdrmerge FTBFS with libraw 0.21.1 Set Bug forwarded-to-address to 'https://github.com/jcelaya/hdrmerge/pull/217'. > tags 1040256 + upstream fixed-upstream Bug #1040256 [src:hdrmerge] hdrmerge FTBFS with libraw 0.21.1 Added tag(s) fixed-upstream and upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1039672: marked as done (r-cran-svglite: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 6 Jul 2023 10:24:51 +0200
with message-id
and subject line Re: Bug#1039672: r-cran-svglite: autopkgtest failure with
r-base (4.3.1-1)
has caused the Debian Bug report #1039672,
regarding r-cran-svglite: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-svglite
Version: 2.1.1-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
42s [ FAIL 50 | WARN 0 | SKIP 0 | PASS 2 ]
42s
42s ══ Failed tests
43s ── Error ('test-clip.R:4'): regression test for no clipping
43s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
43s aliases, web_fonts, id, fix_text_size, scaling, always_valid)`:
Graphics API version mismatch
43s Backtrace:
43s ▆
43s 1. └─svglite::svglite("test-no-clip.svg", 4, 4, user_fonts = bitstream)
at test-clip.R:4:2
43s 2. └─svglite:::svglite_(...)
43s ── Error ('test-clip.R:14'): regression test for clipping
──
43s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
43s aliases, web_fonts, id, fix_text_size, scaling, always_valid)`:
Graphics API version mismatch
43s Backtrace:
43s ▆
43s 1. └─svglite::svglite("test-clip.svg", 4, 4, user_fonts = bitstream) at
test-clip.R:14:2
43s 2. └─svglite:::svglite_(...)
43s ── Error ('test-colour.R:5'): transparent blacks are written
───
43s Error in `svgstring_(env, width = width, height = height, bg = bg,
pointsize = pointsize,
43s standalone = standalone, aliases = aliases, webfonts = web_fonts,
43s id = id, fix_text_size, scaling)`: Graphics API version mismatch
43s Backtrace:
43s ▆
43s 1. └─svglite::xmlSVG(...) at test-colour.R:5:2
43s 2. └─svglite:::inlineSVG(...)
43s 3. └─svglite::svgstring(width = dim[1], height = dim[2], ...)
43s 4. └─svglite:::svgstring_(...)
43s ── Error ('test-colour.R:19'): transparent colours are not written
─
43s Error in `svgstring_(env, width = width, height = height, bg = bg,
pointsize = pointsize,
43s standalone = standalone, aliases = aliases, webfonts = web_fonts,
43s id = id, fix_text_size, scaling)`: Graphics API version mismatch
43s Backtrace:
43s ▆
43s 1. └─svglite::xmlSVG(...) at test-colour.R:19:2
43s 2. └─svglite:::inlineSVG(...)
43s 3. └─svglite::svgstring(width = dim[1], height = dim[2], ...)
43s 4. └─svglite:::svgstring_(...)
43s ── Error ('test-devSVG.R:12'): adds default background
─
43s Error in `svgstring_(env, width = width, height = height, bg = bg,
pointsize = pointsize,
43s standalone = standalone, aliases = aliases, webfonts = web_fonts,
43s id = id, fix_text_size, scaling)`: Graphics API version mismatch
43s Backtrace:
43s ▆
43s 1. └─svglite::xmlSVG(plot.new()) at test-devSVG.R:12:2
43s 2. └─svglite:::inlineSVG(...)
43s 3. └─svglite::svgstring(width = dim[1], height = dim[2], ...)
43s 4. └─svglite:::svgstring_(...)
43s ── Error ('test-devSVG.R:17'): adds background set by device driver
43s Error in `svgstring_(env, width = width, height = height, bg = bg,
pointsize = pointsize,
43s standalone = standalone, aliases = aliases, webfonts = web_fonts,
43s id = id, fix_text_size, scaling)`: Graphics API version mismatch
43s Backtrace:
43s ▆
43s 1. └─svglite::xmlSVG(plot.new(), bg = "red") at test-devSVG.R:17:2
43s 2. └─svglite:::inlineSVG(...)
43s 3. └─svglite::svgstring(width = dim[1], height = dim[2], ...)
43s 4. └─svglite:::svgstring_(...)
43s ── Error ('test-devSVG.R:22'): default background respects par
─
43s Error in `svgstring_(env, width = width, height = height, bg = bg,
pointsize = pointsize,
43s standalone = standalone, aliases = aliases, webfonts = web_fonts,
43s id = id, fix_text_size, scaling)`: Graphics API version mismatch
43s Backtrace:
43s ▆
43s 1. └─svglite::xmlSVG(...) at test-devSVG.R:22:2
43s 2. └─svglite:::inlineSVG(...)
43s 3. └─svglite::svgstring(width = dim[1], height = dim[2], ...)
43s 4. └─svglite:::svgstring_(...)
43s ── Error ('test-devSVG.R:30'): if bg is transparent in par(), use device
driver background ──
Bug#1039664: marked as done (r-cran-tikzdevice: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 6 Jul 2023 10:23:56 +0200
with message-id
and subject line Re: Bug#1039664: r-cran-tikzdevice: autopkgtest failure with
r-base (4.3.1-1)
has caused the Debian Bug report #1039664,
regarding r-cran-tikzdevice: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-tikzdevice
Version: 0.12.4-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
160s [ FAIL 6 | WARN 0 | SKIP 32 | PASS 49 ]
160s
160s ══ Skipped tests
═══
160s • empty test (32)
160s
160s ══ Failed tests
160s ── Error ('test_error_handling.R:59'): tikzNode warns about more than one
X coordinate value ──
160s Error in `tikz()`: Graphics API version mismatch
160s Backtrace:
160s ▆
160s 1. └─tikzDevice::tikz() at test_error_handling.R:59:2
160s ── Error ('test_error_handling.R:70'): tikzNode warns about more than one
Y coordinate value ──
160s Error in `tikz()`: Graphics API version mismatch
160s Backtrace:
160s ▆
160s 1. └─tikzDevice::tikz() at test_error_handling.R:70:2
160s ── Error ('test_error_handling.R:81'): symbolicColors warns about wrong
filename ──
160s Error in `tikz(symbolicColors = T, colorFileName = "/")`: Graphics API
version mismatch
160s Backtrace:
160s ▆
160s 1. └─tikzDevice::tikz(symbolicColors = T, colorFileName = "/") at
test_error_handling.R:81:2
160s ── Error ('test_error_handling.R:91'): symbolicColors warns about too
many colors ──
160s Error in `tikz(symbolicColors = T, maxSymbolicColors = 2)`: Graphics API
version mismatch
160s Backtrace:
160s ▆
160s 1. └─tikzDevice::tikz(symbolicColors = T, maxSymbolicColors = 2) at
test_error_handling.R:91:2
160s ── Failure ('test_misc.R:9'): ggsave should save a *.tex file when used
with 'device=tikzDevice::tikz ──
160s `ggplot2::ggsave(ggsave_path, g, device = tikzDevice::tikz)` threw an
error.
160s Message: Graphics API version mismatch
160s Class: simpleError/error/condition
160s Backtrace:
160s ▆
160s 1. ├─testthat::expect_error(...) at test_misc.R:9:2
160s 2. │ └─testthat:::quasi_capture(...)
160s 3. │ ├─testthat (local) .capture(...)
160s 4. │ │ └─base::withCallingHandlers(...)
160s 5. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
160s 6. └─ggplot2::ggsave(ggsave_path, g, device = tikzDevice::tikz)
160s 7. └─ggplot2 (local) dev(...)
160s 8. ├─rlang::inject(device(!!!args))
160s 9. └─tikzDevice (local) device(width = 7, height = 7, bg = "white",
file =
"/tmp/autopkgtest-lxc.7pnb7fpu/downtmp/autopkgtest_tmp/testthat/test_output/ggsave.tex")
160s ── Error ('test_misc.R:14'): closing tikz device with no error
─
160s Error in `tikzDevice::tikz(onefile = FALSE)`: Graphics API version
mismatch
160s Backtrace:
160s ▆
160s 1. └─tikzDevice::tikz(onefile = FALSE) at test_misc.R:14:2
160s
160s [ FAIL 6 | WARN 0 | SKIP 32 | PASS 49 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-tikzdevice/34907195/log.gz
--- End Message ---
--- Begin Message ---
Done in 0.12.4-3
--
http://fam-tille.de--- End Message ---
Bug#1040406: closed by Debian FTP Masters (reply to Luca Boccassi ) (Bug#1040406: fixed in python-azure 20230705+git-1)
Hi Luca >* New upstream version 20230705+git (Closes: #1040406) Could you please describe how a new version of the azure module can fix that? The dependency needs to be updated as well at least. Also, how can it be that azure-cli is updated without the corresponding azure? Bastian -- Men will always be men -- no matter where they are. -- Harry Mudd, "Mudd's Women", stardate 1329.8
Bug#1040316: python3-minimal fails to install
This is now fixed :) Den tis 4 juli 2023 kl 21:27 skrev Eli Schwartz : > > This bug seems to have been caused by > https://salsa.debian.org/cpython-team/python3-defaults/-/commit/8e243207fee371a7335674fc77db63044b62cb29 > > It migrated from imp to importlib, but importlib doesn't imply > importlib.util -- you cannot and AFAIK never have been able to import > the top-level package and assume the nested modules are available. > > That being said, it did work for me in my (non-Debian :P) 3.11 > environment, purely because I had a .pth file that caused importlib.util > to be imported at startup. (It is the stock setuptools one for namespace > packages. You can isolate the interpreter a bit with -IS to catch this.) > > So a similar problem may explain why this wasn't caught during local > testing. It probably makes sense to generally test this sort of thing > with minimal packages installed, because sneaky .pth files will cause > you issues all the time. >
Bug#969907: Bug#969537: epdfinfo crashing with mismatched libpoppler102 and libpoppler-glib8
On Sunday, May 14, 2023 3:20:39 PM CEST Andreas Metzler wrote: > Something like attached patch. https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/1425 /Sune -- I didn’t stop pretending when I became an adult, it’s just that when I was a kid I was pretending that I fit into the rules and structures of this world. And now that I’m an adult, I pretend that those rules and structures exist. - zefrank
Bug#1039882: marked as done (r-cran-sf: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 07:50:22 + with message-id and subject line Bug#1039882: fixed in r-cran-sf 1.0-13+dfsg-2 has caused the Debian Bug report #1039882, regarding r-cran-sf: autopkgtest failure with r-base (4.3.1-1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1039882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-sf Version: 1.0-9+dfsg-1 Severity: serious Tags: sid trixie Justification: autopkgtest failure Dear Maintainer, The autopkgtest of your package fails with r-base (4.3.1-1): 83s Error in vectbl_assign(x[[j]], i, recycled_value[[j]]) : 83s DLL requires the use of native symbols 83s Calls: right_join ... tbl_subassign_row -> withCallingHandlers -> vectbl_assign https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-sf/34940919/log.gz The autopkgtest for 1.0-13+dfsg-1 fails on i386: 147s Error in vectbl_assign(x[[j]], i, recycled_value[[j]]) : 147s DLL requires the use of native symbols 147s Calls: right_join ... tbl_subassign_row -> withCallingHandlers -> vectbl_assign https://ci.debian.net/data/autopkgtest/testing/i386/r/r-cran-sf/34929272/log.gz --- End Message --- --- Begin Message --- Source: r-cran-sf Source-Version: 1.0-13+dfsg-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of r-cran-sf, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1039...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-sf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 06 Jul 2023 09:14:29 +0200 Source: r-cran-sf Architecture: source Version: 1.0-13+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Closes: 1039882 Changes: r-cran-sf (1.0-13+dfsg-2) unstable; urgency=medium . * Rebuild with r-graphics-engine set by r-base Closes: #1039882 Checksums-Sha1: d3f4fecdf15a70a20a63278ea8a275798da2fa63 2525 r-cran-sf_1.0-13+dfsg-2.dsc 086efab7714de0501f11c5de21d61085f33ce13d 4952 r-cran-sf_1.0-13+dfsg-2.debian.tar.xz 2fa33aa297d068e66dddab80efd8f52dd5497c61 14771 r-cran-sf_1.0-13+dfsg-2_amd64.buildinfo Checksums-Sha256: 4abcf758309c5cc6949176a8b00906e718f02dc462e73238bad3f897a1323a20 2525 r-cran-sf_1.0-13+dfsg-2.dsc dd8b61134aa25d7153f777221ef8873876de4415f79b607bc58d4264be8dd56e 4952 r-cran-sf_1.0-13+dfsg-2.debian.tar.xz 848524891b1e4b80a27885c22fb35a0b5753b758d4be10e139017c88a92a92fe 14771 r-cran-sf_1.0-13+dfsg-2_amd64.buildinfo Files: c47339a8e41dec835d137acdb9fb02d8 2525 gnu-r optional r-cran-sf_1.0-13+dfsg-2.dsc 5afdab6cd73628f43e45b1002a216cfb 4952 gnu-r optional r-cran-sf_1.0-13+dfsg-2.debian.tar.xz 21f1f23d6cce1f7f61adfa665f0029c1 14771 gnu-r optional r-cran-sf_1.0-13+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmax4RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtFHyQ//VtY+YbG2/MU/VPnNvI3ls/29GAJCm9dT Ui48pMmF+kBIHyQhjEc0KDxPXrBb1ZhpAvSqFKOuyr6nARtVa3cBbK7mGOQwLWJ2 eSJWMLMsmmeEKZd6/4fInyMaRcqGBCXXKKq6KjMbBu6H/IgnYkOw1hm5Tf+7wF8z FopYhIMUwm5P0UcOZyMigR3VgnIQhuVKrFqNe2Shm/ySPNaKE79UDI3A8gg5uAfG yomkH9L0Evsdk6ID93v9BBwh7OiZGkOOTbiraSl91aqGpXAXOOiI//QTRY+Dejyo rPs5OVliL40fQSNrFtVJH9HlScxaRzcNzJubTg/v82reMfszbJcu6ZHwoWriF2uB a1y8bEj9QjuAlhd9y4jIgOr6rUh6IPyscNAszIsUA0PirN6PcmDrnV7m0zDduLIr pfT89VXvcwyxJx17+gRH8nBu+DhFzDxajtF9jOXjOuuCr+/2vaFt/hP79ZJ18Iqc smfnn4a2sQg2qMruhudYv6iq80t0qZ8/maU+ba5SpYWpDUOJTGOutac2sY6HXVI/ nMcOj4LWrQ7eVzXRT9T2OuVy6DFcL+pscXUIGoBhD5mNvrYNpoYbe/B0d9vsMrnR RUgUvMbYRxFV2M1dnZM4jOXaa+oDONeyXIg4O9BjyvC3ZSim4yX9vCYTP0ZRJ4OT eeUfDW+JNwU= =dN6f -END PGP SIGNATURE End Message ---
Bug#1000113: kodi: depends on obsolete pcre3 library
Hi, On 06/07/2023 06:33, Vasyl Gello wrote: Yes I definitely see the bug. However, Kodi extensively uses pcrecpp and the only replacement I see for pcre2 is jpcre2 [1] There is an ITP bug about it since 2017 but no package. Matthew, from your experience, is jpcre2 the only C++ wrapper for pcre2 or there is something more recommended / maintainable? I did the search but found only jpcre2. I should say that I'm not C++ expert; jpcre2 is the only wrapper I find by web-searching. I think, though, that it should be possible to use the pcre2 libraries from C++ in the usual way that you can call C libraries from C++ (and the headers have the usual extern "C" magic)... Regards, Matthew
Bug#1039884: marked as done (r-cran-tibble: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 07:34:39 +
with message-id
and subject line Bug#1039884: fixed in r-cran-tibble 3.2.1+dfsg-2
has caused the Debian Bug report #1039884,
regarding r-cran-tibble: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-tibble
Version: 3.1.8+dfsg-1
Severity: serious
Tags: sid trixie
Justification: autopkgtest failure
Control: close -1 3.2.1+dfsg-1
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
92s [ FAIL 11 | WARN 1 | SKIP 144 | PASS 1287 ]
92s
92s ══ Skipped tests
═══
92s • All of them (1)
92s • Do we want an .as_row argument? (1)
92s • On CRAN (44)
92s • packageVersion("pillar") >= "1.4.99" is TRUE (3)
92s • packageVersion("tibble") >= "2.99.99" is TRUE (95)
92s
93s ══ Failed tests
93s ── Error ('test-subsetting-matrix.R:15'): [<-.tbl_df supports subsetting
with a logical matrix (#649) ──
93s Error in `vectbl_assign(x[[j]], cells[[j]], value)`: DLL requires the use
of native symbols
93s Backtrace:
93s ▆
93s 1. ├─base::`[<-`(`*tmp*`, m, value = ``) at
test-subsetting-matrix.R:15:2
93s 2. └─tibble:::`[<-.tbl_df`(`*tmp*`, m, value = ``) at
test-subsetting-matrix.R:15:2
93s 3. └─tibble:::tbl_subassign_matrix(x, j, value, j_arg,
substitute(value))
93s 4. ├─base::withCallingHandlers(...)
93s 5. └─tibble:::vectbl_assign(x[[j]], cells[[j]], value)
93s ── Error ('test-subsetting.R:416'): can use classed integer indexes (#778)
─
93s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of native symbols
93s Backtrace:
93s ▆
93s 1. ├─testthat::expect_silent(df[mylgl(TRUE), ] <- df) at
test-subsetting.R:416:2
93s 2. │ └─testthat:::quasi_capture(enquo(object), NULL, evaluate_promise)
93s 3. │ ├─testthat (local) .capture(...)
93s 4. │ │ ├─withr::with_output_sink(...)
93s 5. │ │ │ └─base::force(code)
93s 6. │ │ ├─base::withCallingHandlers(...)
93s 7. │ │ └─base::withVisible(code)
93s 8. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
93s 9. ├─base::`[<-`(`*tmp*`, mylgl(TRUE), , value = ``)
93s 10. └─tibble:::`[<-.tbl_df`(`*tmp*`, mylgl(TRUE), , value =
``)
93s 11. └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
93s 12. └─tibble:::tbl_subassign_row(x, i, value, i_arg, value_arg)
93s 13. ├─base::withCallingHandlers(...)
93s 14. └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
93s ── Error ('test-subsetting.R:425'): can use classed logical indexes (#778)
─
93s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of native symbols
93s Backtrace:
93s ▆
93s 1. ├─testthat::expect_silent(df[mylgl(TRUE), mylgl(TRUE)] <- df) at
test-subsetting.R:425:2
93s 2. │ └─testthat:::quasi_capture(enquo(object), NULL, evaluate_promise)
93s 3. │ ├─testthat (local) .capture(...)
93s 4. │ │ ├─withr::with_output_sink(...)
93s 5. │ │ │ └─base::force(code)
93s 6. │ │ ├─base::withCallingHandlers(...)
93s 7. │ │ └─base::withVisible(code)
93s 8. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo))
93s 9. ├─base::`[<-`(`*tmp*`, mylgl(TRUE), mylgl(TRUE), value =
``)
93s 10. └─tibble:::`[<-.tbl_df`(`*tmp*`, mylgl(TRUE), mylgl(TRUE), value =
``)
93s 11. └─tibble:::tbl_subassign(x, i, j, value, i_arg, j_arg,
substitute(value))
93s 12. └─tibble:::tbl_subassign_row(xj, i, value, i_arg, value_arg)
93s 13. ├─base::withCallingHandlers(...)
93s 14. └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
93s ── Error ('test-subsetting.R:458'): [[<-.tbl_df with two indexes assigns
───
93s Error in `vectbl_assign(x[[j]], i, recycled_value[[j]])`: DLL requires the
use of native symbols
93s Backtrace:
93s ▆
93s 1. ├─base::`[[<-`(`*tmp*`, 1, "x", value = ``) at
test-subsetting.R:458:2
93s 2. └─tibble:::`[[<-.tbl_df`(`*tmp*`, 1, "x", value = ``) at
test-subsetting.R:458:2
93s 3. └─tibble:::tbl_subassign(...)
93s 4. └─tibble:::tbl_subassign_row(xj, i, value, i_arg, value_arg)
93s 5. ├─base::withCallingHandlers(...)
93s 6. └─tibble:::vectbl_assign(x[[j]], i, recycled_value[[j]])
93s ── Error ('test-subsetting.R:532'): [<-.tbl_df
Bug#1039886: marked as done (r-cran-truncnorm: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 07:19:00 +
with message-id
and subject line Bug#1039886: fixed in r-cran-truncnorm 1.0-9-2
has caused the Debian Bug report #1039886,
regarding r-cran-truncnorm: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-truncnorm
Version: 1.0-8-3:
Severity: serious
Tags: sid trixie
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
36s [ FAIL 1 | WARN 0 | SKIP 0 | PASS 13 ]
36s
36s ══ Failed tests
36s ── Error ('test-sanity_checks.R:22:1'): (code run outside of
`test_that()`)
36s Error in `etruncnorm(a, b, mean, sd)`: DLL requires the use of native
symbols
36s Backtrace:
36s ▆
36s 1. └─truncnorm (local) check_dev(-3, Inf, 0, 1) at
test-sanity_checks.R:22:0
36s 2. └─truncnorm::etruncnorm(a, b, mean, sd) at test-sanity_checks.R:7:2
36s
36s [ FAIL 1 | WARN 0 | SKIP 0 | PASS 13 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-truncnorm/34931922/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-truncnorm
Source-Version: 1.0-9-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-truncnorm, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-truncnorm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 09:00:16 +0200
Source: r-cran-truncnorm
Architecture: source
Version: 1.0-9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1039886
Changes:
r-cran-truncnorm (1.0-9-2) unstable; urgency=medium
.
* Rebuild with r-graphics-engine set by r-base
Closes: #1039886
Checksums-Sha1:
621f3161f81b2f3cac1d6357e1054780b232d358 2123 r-cran-truncnorm_1.0-9-2.dsc
2ea44545d906a6954d4fed81b579b8f05ba3f238 2660
r-cran-truncnorm_1.0-9-2.debian.tar.xz
94092bc0b49253e44d2c354ae486149b3cc773b1 10708
r-cran-truncnorm_1.0-9-2_amd64.buildinfo
Checksums-Sha256:
e6d34f04446c356a27948f4fd124029f0eb91627e98524cb4b64668ec1b9a560 2123
r-cran-truncnorm_1.0-9-2.dsc
da9790a8a9f3149cf521b5dcdeaa16747983c640c6fd2dc38062dd34742ca863 2660
r-cran-truncnorm_1.0-9-2.debian.tar.xz
017a2aa79192f38f0d1a733102d29413173557aadcb7572cc44b3048f1a7 10708
r-cran-truncnorm_1.0-9-2_amd64.buildinfo
Files:
34c2a1cc86a50b78d1e75177313996f2 2123 gnu-r optional
r-cran-truncnorm_1.0-9-2.dsc
91b31845908cc9bc06f33d6c9336bb6c 2660 gnu-r optional
r-cran-truncnorm_1.0-9-2.debian.tar.xz
2bb1c1d00f847d0f205b441cdda63384 10708 gnu-r optional
r-cran-truncnorm_1.0-9-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmSmZ34RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtG7RA/8DVflqGXxJrLKzEdP9Bf/qH4H6lLYzEGV
c9k5T5pwDSDWS3xSRYIC+BV9xJhkZP2MoY99YKcFNVug+cneHDsBksHJagrI+h6i
Kpwl0EDC5ke2V5Lv/cjTo31DQTgCNIpXzL4f9unNDJB9MoUDzIOKAxLquQBU0HUC
oCRuKfRbM7O2e9w5ahuGkBjXYtu8omeBdHIVLnbb5lPmA09qbsv5w2y8tl1Isxxa
Uldm1qWRiHqcFt0WMz51DHQXZiWHwh8K8lptQFQUEpGo5kHABHzN7ur2IAI1zUXw
yKLbdvOJQG4DFJOmK6p7jWbysE4RlCD+UmFXobCosMPEwhJ+XTfMP1vdTmlS5v/A
MbxoBiTl2LEHzQHGYMwnb4IG3AEfwy9bLqkKGo1jUGzeKQZpihuaJDtUCRPtKFur
fRyN+vn1sJ8J+d6lvOpKMQspRUcYuNuHbZyHbgah2Psn2qWjI78nIqWWel/QXalo
+/xV/tGNXRkfjV1lqWJ8k0ogk8pYDE3HVPYNS2uRXTRxztuzOmuq4kebgu4DtOWl
J54EnlCXf3PPbh5LDBxzhbS6YUZOLGYEjYr4AJeo2Jc6Q7USEGQ4PCJEOFIdRc2r
A3DoCFUjm2y1EC9tAS9JX28a9c8L74Ase2O3iAYsHD43AprBoGqkYPt7UQgz1o34
jLn5i2PeMa8=
=7hDa
-END PGP SIGNATURE End Message ---
Bug#1039885: marked as done (r-cran-tidytext: autopkgtest failure with r-base (4.3.1-1))
Your message dated Thu, 06 Jul 2023 07:18:54 +
with message-id
and subject line Bug#1039885: fixed in r-cran-tidytext 0.4.1-2
has caused the Debian Bug report #1039885,
regarding r-cran-tidytext: autopkgtest failure with r-base (4.3.1-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1039885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-tidytext
Version: 0.4.1-1
Severity: serious
Tags: sid trixie
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
51s [ FAIL 3 | WARN 0 | SKIP 20 | PASS 143 ]
51s
51s ══ Skipped tests
═══
51s • data.table cannot be loaded (3)
51s • empty test (2)
51s • hunspell cannot be loaded (2)
51s • On CRAN (4)
51s • quanteda cannot be loaded (4)
51s • stm cannot be loaded (1)
51s • stopwords cannot be loaded (1)
51s • tm cannot be loaded (3)
51s
51s ══ Failed tests
51s ── Error ('test-reorder-within.R:29'): Can make a plot
─
51s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
51s always_valid)`: Graphics API version mismatch
51s Backtrace:
51s ▆
51s 1. └─vdiffr::expect_doppelganger("reordered boxplot", p) at
test-reorder-within.R:29:2
51s 2. └─vdiffr (local) writer(fig, testcase, title)
51s 3. └─vdiffr:::svglite(file)
51s 4. └─vdiffr:::svglite_(...)
51s ── Error ('test-reorder-within.R:47'): Can make a plot with custom labels
──
51s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
51s always_valid)`: Graphics API version mismatch
51s Backtrace:
51s ▆
51s 1. └─vdiffr::expect_doppelganger("custom label boxplot", p) at
test-reorder-within.R:47:2
51s 2. └─vdiffr (local) writer(fig, testcase, title)
51s 3. └─vdiffr:::svglite(file)
51s 4. └─vdiffr:::svglite_(...)
51s ── Error ('test-reorder-within.R:64'): Can make a multi-facet plot
─
51s Error in `svglite_(filename, bg, width, height, pointsize, standalone,
51s always_valid)`: Graphics API version mismatch
51s Backtrace:
51s ▆
51s 1. └─tidytext (local) expect_doppelganger("reordered multi-facet
boxplot", p) at test-reorder-within.R:64:2
51s 2. └─vdiffr::expect_doppelganger(title, fig, ...) at
test-reorder-within.R:55:4
51s 3. └─vdiffr (local) writer(fig, testcase, title)
51s 4. └─vdiffr:::svglite(file)
51s 5. └─vdiffr:::svglite_(...)
51s
51s [ FAIL 3 | WARN 0 | SKIP 20 | PASS 143 ]
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-tidytext/34938075/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-tidytext
Source-Version: 0.4.1-2
Done: Andreas Tille
We believe that the bug you reported is fixed in the latest version of
r-cran-tidytext, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated r-cran-tidytext package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 06 Jul 2023 08:59:00 +0200
Source: r-cran-tidytext
Architecture: source
Version: 0.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Andreas Tille
Closes: 1039885
Changes:
r-cran-tidytext (0.4.1-2) unstable; urgency=medium
.
* Rebuild with r-graphics-engine set by r-base
Closes: #1039885
Checksums-Sha1:
d2659b4054b40b1e3e196d0203aa4a9a27931453 2348 r-cran-tidytext_0.4.1-2.dsc
94915badf4261be4d502c51d92c550ab81b5bb41 3452
r-cran-tidytext_0.4.1-2.debian.tar.xz
cbba55df0e851c56f8e5a42c87b88fb304c34c48 11206
r-cran-tidytext_0.4.1-2_amd64.buildinfo
Checksums-Sha256:
f9dd5716329c364670384f5d2e55ae18985aec18aa2f94606ba36c4efee18fec 2348
r-cran-tidytext_0.4.1-2.dsc
1d571fb252a9400976b50fc64b688d44035e236495d0597e9075d9353d24d903 3452
r-cran-tidytext_0.4.1-2.debian.tar.xz
