Bug#1011752: [Debian-pan-maintainers] Bug#1011752: freesas: please make the build reproducible
Hi Chris, This patch looks good to me. Thanks for the fix -- Jérôme Kieffer upstream author of FreeSAS
Bug#1012077: linuxinfo FTBFS on riscv64
Hello Alan, On Sun, May 29, 2022 at 02:45:29PM -0400, Alan Beadle wrote: > Package: linuxinfo > Version: 3.3.3-1 > Severity: serious > Tags: ftbfs patch upstream > Justification: fails to build from source > X-Debbugs-Cc: ab.bea...@gmail.com > > Dear Maintainer, > > linuxinfo currently fails to build on riscv64 due to this architecture not > being > supported by upstream. I am attaching a patch which adds placeholder support > for > this architecture and allows building the riscv64 debian package from source. > > Please consider applying this patch (or similar) for the next upload. > In addition, the /proc information below is for a riscv64 VisionFive V1 SBC. Thanks a lot! This was on my wishlist already. I'll review and possibly ammend your patch next weekend and then will proceed with an upload. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ signature.asc Description: PGP signature
Bug#1012092: lists.debian.org: please close obsolete list debian-flash: obsolete technology, last legitimate mail 2014, some spam since then
Package: lists.debian.org Severity: wishlist X-Debbugs-CC: debian-fl...@lists.debian.org Please close the debian-flash mailing list: Flash is an obsolete technology that became EOL at the end of 2020. https://www.adobe.com/products/flashplayer/end-of-life.html The last legitimate mail to the debian-flash list was in 2014. https://lists.debian.org/debian-flash/2014/10/threads.html There has been a small amount of spam every year since then. https://lists.debian.org/debian-flash/ -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#1012090: riscv support in lintian tag binary-from-other-architecture
Package: lintian Version: 2.114.0 Severity: wishlist X-Debbugs-Cc: atzli...@sina.com Hi, I hope lintian support riscv arch. The binary-from-other-architecture tag is not support riscv arch now. There are some discusses in debian-riscv maillist: https://lists.debian.org/debian-riscv/2022/05/msg00083.html The lintian list of ELF arch regexes need to include one for riscv64: https://salsa.debian.org/lintian/lintian/-/blob/master/data/binaries/arch-regex A example of file command output: file /bin/bash /bin/bash: ELF 64-bit LSB pie executable, UCB RISC-V, RVC, double-float ABI, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-riscv64-lp64d.so.1, BuildID[sha1]=76d8296819bcc14a97fa7627b96c1cd0092e2d96, for GNU/Linux 4.15.0, stripped Thanks! -- System Information: Distributor ID: Atzlinux Description:Tongwandou (atzlinux) 11 Release:11.3 Codename: bullseye Architecture: riscv64 Kernel: Linux 5.18.0-starfive-5.18 (SMP w/2 CPU threads) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lintian depends on: ii binutils2.38-4 ii bzip2 1.0.8-5 ii diffstat1.64-1 ii dpkg1.21.8 ii dpkg-dev1.21.8 ii file1:5.41-4 ii gettext 0.21-6 ii gpg 2.2.35-2 ii intltool-debian 0.35.0+20060710.5 ii libapt-pkg-perl 0.1.40+b1 ii libarchive-zip-perl 1.68-1 ii libcapture-tiny-perl0.48-1 ii libclass-xsaccessor-perl1.19-3+b8 ii libclone-perl 0.45-1+b2 ii libconfig-tiny-perl 2.28-1 ii libconst-fast-perl 0.014-1.1 ii libcpanel-json-xs-perl 4.28-1 ii libdata-dpath-perl 0.58-1 ii libdata-validate-domain-perl0.10-1.1 ii libdata-validate-uri-perl 0.07-2 ii libdevel-size-perl 0.83-1+b3 ii libdigest-sha-perl 6.02-1+b4 ii libdpkg-perl1.21.8 ii libemail-address-xs-perl1.04-1+b4 ii libfile-basedir-perl0.09-1 ii libfile-find-rule-perl 0.34-1 ii libfont-ttf-perl1.06-1.1 ii libhtml-html5-entities-perl 0.004-1.1 ii libio-interactive-perl 1.023-1 ii libio-prompt-tiny-perl 0.003-1 ii libipc-run3-perl0.048-2 ii libjson-maybexs-perl1.004003-1 ii liblist-compare-perl0.55-1 ii liblist-someutils-perl 0.58-1 ii liblist-utilsby-perl0.12-1 ii libmoo-perl 2.005004-3 ii libmoox-aliases-perl0.001006-2 ii libnamespace-clean-perl 0.27-1 ii libpath-tiny-perl 0.122-1 ii libperlio-gzip-perl 0.19-1+b4 ii libperlio-utf8-strict-perl 0.009-1+b1 ii libproc-processtable-perl 0.634-1+b1 ii libsereal-decoder-perl 4.023+ds-1 ii libsereal-encoder-perl 4.023+ds-1 ii libsort-versions-perl 1.62-1 ii libsyntax-keyword-try-perl 0.27-1 ii libterm-readkey-perl2.38-1+b3 ii libtext-glob-perl 0.11-2 ii libtext-levenshteinxs-perl 0.03-4+b4 ii libtext-markdown-discount-perl 0.13-1+b1 ii libtext-xslate-perl 3.5.9-1+b1 ii libtime-duration-perl 1.21-1 ii libtime-moment-perl 0.44-1+b4 ii libtimedate-perl2.3300-2 ii libunicode-utf8-perl0.62-1+b3 ii liburi-perl 5.10-1 ii libxml-libxml-perl 2.0207+dfsg+really+2.0134-1 ii libyaml-libyaml-perl0.83+ds-1+b1 ii lzip1.23-3 ii lzop1.04-2 ii man-db 2.10.2-1 ii patchutils 0.4.2-1 ii perl [libencode-perl] 5.34.0-4 ii t1utils 1.41-4 ii unzip 6.0-26 ii xz-utils5.2.5-2.1 lintian recommends no packages. Versions of packages lintian suggests: pn binutils-multiarch ii libtext-template-perl 1.61-1 -- no debconf information
Bug#1012021: [Pkg-javascript-devel] Bug#1012021: unreproducible here
Il 29/05/22 21:34, Pirate Praveen ha scritto:
On തി, മേയ് 30 2022 at 12:56:53 രാവിലെ +05:30:00 +05:30:00, Pirate
Praveen wrote:
On ഞാ, മേയ് 29 2022 at 09:34:45 രാവിലെ +02:00:00 +02:00:00, Paolo
Greppi wrote:
Hi Andreas! thanks for your report. To try to reproduce it, I set
...
Finally there is more trouble ahead when building this package,
because I also tried:
apt install git
git clone
https://salsa.debian.org/pkg-security-team/greenbone-security-assistant
cd greenbone-security-assistant
yarnpkg
yarnpkg build
and the last command failed with:
...
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:67:19)
at Object.createHash (node:crypto:130:10)
at module.exports
(/greenbone-security-assistant/node_modules/webpack/lib/util/createHash.js:135:53)
at NormalModule._initBuildHash
(/greenbone-security-assistant/node_modules/webpack/lib/NormalModule.js:417:16)
at
/greenbone-security-assistant/node_modules/webpack/lib/NormalModule.js:452:10
at
/greenbone-security-assistant/node_modules/webpack/lib/NormalModule.js:323:13
at
/greenbone-security-assistant/node_modules/loader-runner/lib/LoaderRunner.js:367:11
at
/greenbone-security-assistant/node_modules/loader-runner/lib/LoaderRunner.js:233:18
at context.callback
(/greenbone-security-assistant/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
at
/greenbone-security-assistant/node_modules/babel-loader/lib/index.js:59:103
at processTicksAndRejections
(node:internal/process/task_queues:96:5) {
opensslErrorStack: [ 'error:0386:digital envelope
routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
error Command failed with exit code 1.
(this also happens on amd64 BTW).
According to the interwebs this should only occur with node v17
(whereas in unstable we have v16.15.0) and indeed the commonly
proposed workaround fails:
NODE_OPTIONS=--openssl-legacy-provider yarnpkg build
/usr/bin/node: --openssl-legacy-provider is not allowed in
NODE_OPTIONS
I was also seeing this error while looking at node-babel-loader
We might need to fix node-babel-loader
https://github.com/babel/babel-loader/issues/923
Even though the pull request is merged
https://github.com/babel/babel-loader/pull/924 I get same error on
master branch of upstream babel-loader repo with yarnpkg test.
It seems ad-hoc fixes may be required for each package, such as this
other one:
https://salsa.debian.org/js-team/node-cacache/-/commit/214b963bd02fd74d445789b184d344777dda8ee2
What is mysterious is that all that should only happen with nodejs v17 ...
P.
Bug#1012088: libsdl2-dev is possibly missing dependencies
Package: libsdl2-dev
Version: 2.0.20+dfsg-2build1
Severity: normal
X-Debbugs-Cc: woshilinmanfu+deb...@gmail.com
Dear Maintainer,
I think that libsdl-dev may possibly need its dependency list updating. I
noticed the issue in Ubuntu, but the dependencies in Ubuntu are essentially the
same as those in upstream Debian (apart from some things like libc and
pkg-config which presumably apply to all packages), so I am reporting it to you
too.
WHAT LED UP TO THE SITUATION?
I moved from Ubuntu 20.04 Focal Fossa to 22.04 Jammy Jellyfish. The Jammy
version of this package (2.2.20+dfsg-2build1) is behind the Debian Sid version,
but both versions have the same dependencies if there is a problem, then it is
still there.
(This is how I discovered the issue, but there is probably a much more minimal
reproduction case)
1. Downloaded the Simutrans-Extended repo:
https://github.com/jamespetts/simutrans-extended
2. Downloaded the dependencies, at a minimum libsdl2-dev
3. Followed the instructions there for building with autotools
EXPECTED RESULTS
Simutrans-Extended compiles correctly, as it did on Focal Fossa.
ACTUAL RESULTS
When I tried to build it on Jammy Jellyfish, the build failed with the
following errors from the linker:
/usr/bin/ld: cannot find -ldrm: No such file or directory
/usr/bin/ld: cannot find -lgbm: No such file or directory
/usr/bin/ld: cannot find -ldecor-0: No such file or directory
Installing Ubuntu's libdrm-dev, libgbm-dev, and libdecor-0-dev packages ("the
'missing' packages") solved that problem. But I wonder whether it might be a
packaging bug. I follow Simutrans-Extended development quite closely and we
have not intentionally introduced dependencies on those packages; I think they
have been brought in by SDL2.
If a program using sdl2-dev used to be able to compile without the 'missing'
packages, but now requires them, it seems to me that they are now dependencies
of sdl2-dev. Or at least should be 'suggests'. But I am not an expert on either
Debian packaging or SDL2.
COMMENTS
The 'missing' libraries are not direct dependencies of Simutrans. However, the
sdl2-0-0 packages in Debian and Ubuntu have recently added dependencies on
libgbm1, libdrm2, and libdecor-0-0.
Compare the Bullseye dependencies
https://packages.debian.org/bullseye/libsdl2-2.0-0
..with the Bookworm dependencies:
https://packages.debian.org/bookworm/libsdl2-2.0-0
However, the Bookworm and Sid libsdl2-dev packages do **not** list dependencies
on the 'missing' -dev packages: https://packages.debian.org/bookworm/libsdl2-dev
I notice that SDL's own build guide lists those packages as dependencies for
building SDL2 itself on Focal Fossa:
https://github.com/libsdl-org/SDL/blob/main/docs/README-linux.md
But that change was made in February 2021 so it affects Ubuntu's version of
SDL2 in Jammy, not Focal:
https://github.com/libsdl-org/SDL/commit/2f4e9294aa260635d876b5699846adc458f555db
That change was before Bullseye was released so I am not sure how that fits
with the Debian timescale.
I initially asked about this on AskUbuntu and a comment there confirmed that
the required .so files are in (for example) libgbm-dev, not lib-gbm1:
https://askubuntu.com/questions/1410876/is-ubuntus-libsdl2-dev-package-missing-dependencies-or-have-i-made-a-mistake?noredirect=1#comment2451919_1410876
That seemed to confirm that this might be a packaging/dependencies issue.
The downstream report for Ubuntu is here:
https://bugs.launchpad.net/ubuntu/+source/libsdl2/+bug/1976198
Thank you for your time. I hope this feedback is helpful and not just my
misunderstanding.
-- System Information:
Debian Release: bookworm/sid
APT prefers jammy-updates
APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy'),
(100, 'jammy-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-33-generic (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 libsdl2-dev depends on:
ii libasound2-dev1.2.6.1-1ubuntu1
ii libc6 2.35-0ubuntu3
ii libdbus-1-dev 1.12.20-2ubuntu4
ii libegl1-mesa-dev 22.0.1-1ubuntu2
ii libgl-dev 1.4.0-1
ii libgles-dev 1.4.0-1
ii libglu1-mesa-dev 9.0.2-1
ii libibus-1.0-dev 1.5.26-4
ii libopengl01.4.0-1
ii libpulse-dev 1:15.99.1+dfsg1-1ubuntu1
ii libsdl2-2.0-0 2.0.20+dfsg-2build1
ii libsndio-dev 1.8.1-1.1
ii libudev-dev 249.11-0ubuntu3.1
ii libwayland-dev1.20.0-1
ii libx11-6 2:1.7.5-1
ii libx11-dev2:1.7.5-1
ii libxcursor-dev1:1.2.0-2build4
ii libxext-dev 2:1.3.4-1build1
ii libxi-dev 2:1.8-1build1
ii libxinerama-dev 2:1.1.4-3
ii libxkbcommon-dev 1.4.0-1
ii libxrandr-dev
Bug#1012089: Mismatch of code version and reported version in yubikey-luks package
Package: yubikey-luks Version: 0.5.1 Severity: important Package contains code that is from an older version of the repo https://github.com/cornelinux/yubikey-luks. Specifically the ykluks.cfg and the key-script (renamed ykluks-keyscript after install) These 2 files facilitate the non-interactive 1 factor yubikey unlocking.
Bug#1001004: dkms: Fail to remove modules
Control: forcemerge 996104 1001004 1005928 1006431 1008474 fyi: I'm force merging duplicate reports to #996104. The bug was fixed upstream in 2.8.8, but Debian upgraded to 3.0.3 in the meantime (bullseye never had this bug, because it only has version 2.8.4). I assume folks tracking testing are going to have to manually downgrade to 2.8.4, or upgrade to 3.0.3, because I think it's unlikely that there will be a 2.8.8 release just for testing. -- - Norman Rasmussen - Email: nor...@rasmussen.co.za - Home page: http://norman.rasmussen.co.za/
Bug#1012084: systemd-zram-generator: Old version, please update 0.3.x -> 1.x.x
There are Debian packages for v1.1.0 from nabijaczleweli, if that would help: - https://debian.nabijaczleweli.xyz/README - https://github.com/nabijaczleweli/systemd-zram-generator.deb
Bug#1012087: Typo in package description (and it is too terse)
Source: lesana
Version: 0.9.1-3
Severity: minor
I see typo in package description: s/inventaries/inventories/
I also think this description is too terse. Please think about updating
it by copying description from https://pypi.org/project/lesana/ .
---
Description: manage collections of various kinds through yaml files
lesana is a python3 library to organize collections of various kinds. It
is designed to have a data storage / serialization format that is
friendly to git and other VCSs, but decent performances.
.
To reach this aim it uses yaml as its serialization format, which is
easy to store in a VCS, share between people and syncronize between
different computers, but it also keeps an index of this data in a local
xapian database in order to allow for fast searches.
.
lesana supports collections of any kind, as long as their entries can be
described with a mostly flat dictionary of fields of the types described
in the documentation file field_types.
.
Some example collection schemas are provided, but one big strenght of
lesana is the ability to customize your collection with custom fields by
simply writing a personalized settings.yaml.
---
("but decent performances" may be grammatically odd. Something like
"with decent performances" sounds better for me but it isn't essential.)
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.17.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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
Bug#1012086: debsign: Bash completion has incorrect handling for version option
Package: devscripts Version: 2.22.1 Severity: normal The Bash completion for the ‘debsign’ command is incorrectly defined. It incrrectly recognises a ‘-version’ option that does not exist; and fails to recognise the real ‘--version’ option. $ debsign -ve → debsign -version debsign: invalid option -- 'v' $ debsign --ve → (no completion)
Bug#1012084: systemd-zram-generator: Old version, please update 0.3.x -> 1.x.x
Package: systemd-zram-generator Version: 0.3.2-1 Severity: wishlist X-Debbugs-Cc: 4tn223y6z...@opayq.com Hello! Is it possible to update this package to a more recent version? Latest upstream version is 1.1.2. Best regards -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-33-generic (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages systemd-zram-generator depends on: ii libc6 2.33-7 ii libgcc-s1 12.1.0-2 systemd-zram-generator recommends no packages. systemd-zram-generator suggests no packages.
Bug#1012083: quickfix FTBFS on riscv64
Source: quickfix Version: 1.15.1+dfsg-4 Severity: serious Tags: ftbfs patch upstream Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: ab.bea...@gmail.com Dear Maintainer, Currently, quickfix fails to build on riscv64. The problem occues due to the inclusion of an old version of the double-conversion utility in the following subdirectory: src/C++/double-conversion/ You can view the (trivial) upstream commit to add riscv64 support here: https://github.com/google/double-conversion/commit/8316ed5bf405835558a476e528d8e1d0adf69dd9 You can review the failed build log here: https://buildd.debian.org/status/fetch.php?pkg=quickfix&arch=riscv64&ver=1.15.1%2Bdfsg-4&stamp=1652988337&raw=0 The least intrusive solution is to patch the included utility in the same way that the upstream source for this utility already has. I am including a patch which does this. I have confirmed that this patch allows building quickfix on actual riscv64 hardware (StatFive VisionFive V1). Please consider applying the included patch (or similar) for the next upload. Thank you, -Alan Beadle -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: riscv64 Kernel: Linux 5.18.0-starfive-5.18 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Index: quickfix-1.15.1+dfsg/src/C++/double-conversion/utils.h === --- quickfix-1.15.1+dfsg.orig/src/C++/double-conversion/utils.h +++ quickfix-1.15.1+dfsg/src/C++/double-conversion/utils.h @@ -69,7 +69,8 @@ defined(__sparc__) || defined(__sparc) || defined(__s390__) || \ defined(__SH4__) || defined(__alpha__) || \ defined(_MIPS_ARCH_MIPS32R2) || \ -defined(__AARCH64EL__) || defined(__aarch64__) +defined(__AARCH64EL__) || defined(__aarch64__) || \ +defined(__riscv) #define DOUBLE_CONVERSION_CORRECT_DOUBLE_OPERATIONS 1 #elif defined(__mc68000__) #undef DOUBLE_CONVERSION_CORRECT_DOUBLE_OPERATIONS
Bug#1011666: groff 1.23.0 build dependencies will change
On Fri, May 27, 2022 at 06:27:36PM -0500, G. Branden Robinson wrote:
> At 2022-05-26T13:13:44+0100, Colin Watson wrote:
> > Isn't this handled by passing PSPRINT=lpr to configure, as we do in
> > debian/rules? I generally prefer this approach over
> > build-dependencies in cases where the build-dependency would just be
> > for path detection and isn't actually used during the build.
> >
> > The fact that /usr/share/groff/1.22.4/font/devps/DESC ends with "print
> > lpr" suggests that this is working.
>
> You are quite right. I withdraw that suggestion. I guess if someone
> doesn't want a BSD-style print spooler installed but does have an lp(1)
> command and still wants to use 'groff -l', they'll have to edit the DESC
> files for the output devices...which aren't conffiles. Yuck.
>
> Maybe grops(1), grodvi(1), grolbp(1), and grolj4(1) (and gropdf(1)?)
> should grow an option to override the "print" directive in their DESC
> files.
>
> This is probably not urgent. The lack of bug reports from people
> satisfying the demographic sector I characterized above suggests that
> their numbers are few.
Quite ... I expect nowadays people probably just write the output to a
file and print it from there. ("groff -l" is an un-Unix-like
abomination anyway IMO, though you're probably now going to tell me that
it dates back to v7 or something.)
> > Would you like to co-maintain the package? You're already much more
> > active upstream than I am and you've been doing lots of bug
> > maintenance; I'd be happy for you to do that with a maintainer hat.
>
> Thank you for this gracious invitation! I've been looking for a way
> back into measurable Debian development activity. I accept.
Great. The git repository is under the "debian" group so you should
have commit access already, but please add yourself to Uploaders with
whatever address you prefer.
> > (My only conditions are that I'd like to keep using git-dpm for patch
> > maintenance and dgit for uploads.)
>
> Certainly. I have no revolutionary aspirations there. Nor, I'm ashamed
> to admit, a basic level of competence with git-gpm. I seem to remember
> using dgit and git-buildpackage the last time I uploaded a package,
> which was quite some time ago thanks to my upstream slowing WAY down.
https://alioth-lists.debian.net/pipermail/pkg-grub-devel/2014-January/013883.html
is an old email of mine that may help with the "basic level of
competence" question. (But I'm certainly happy to deal with the big
merge of 1.23.0 once that happens, since that can be rather more
complicated than day-to-day patch maintenance.)
> I would ask that you to take the decision about the man/mdoc/UTF-8 glyph
> contretemps[1] (which boils down to: patch {man,mdoc}.local or not?); as
> the upstream instigator of the controversial change, I'm afraid I'm
> conflicted out on the issue.
>
> Unless you agree with me but would prefer I wore the blame for it. 3;-)
I'm afraid I'm rather of the opinion that, despite being in generally
good health, I don't expect to live long enough to see all manual page
authors fix their pages, since that didn't happen very consistently with
the more common \- issue; and I like copy and paste of commonplace shell
commands and regular expressions and such to work. As such I'm inclined
to patch {man,mdoc}.local, though I'll probably defer a final decision
on that until we merge 1.23.0.
--
Colin Watson (he/him) [cjwat...@debian.org]
Bug#1010357: Solved
This problem is solved upstream at recent Debian version gtk4 4.6.4+ds-3
Bug#1012082: jboss-logging: FTBFS with OpenJDK 17 due to the removal of --no-module-directories javadoc option
Source: jboss-logging Version: 3.5.0-1 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 jboss-logging fails to build with OpenJDK 17, it uses the deprecated '--no-module-directories' javadoc option: [INFO] --- maven-javadoc-plugin:3.0.1:jar (default-cli) @ jboss-logging --- [WARNING] The POM for org.codehaus.plexus:plexus-interactivity-api:jar:debian is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [INFO] Adding the --ignore-source-errors option [INFO] Usage: javadoc [options] [packagenames] [sourcefiles] [@files] where options include: @ Read options and filenames from file --add-modules (,)* Root modules to resolve in addition to the initial modules, or all modules on the module path if is ALL-MODULE-PATH. -bootclasspath Override location of platform class files used for non-modular releases -breakiterator Compute first sentence with BreakIterator --class-path , -classpath , -cp Specify where to find user class files -doclet Generate output via alternate doclet -docletpath Specify where to find doclet class files --enable-preview Enable preview language features. To be used in conjunction with either -source or --release. ... [INFO] [INFO] [INFO] Skipping JBoss Logging 3 [INFO] This project has been banned from the build due to previous failures. [INFO] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.637 s [INFO] Finished at: 2022-05-26T01:46:45Z [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (default-cli) on project jboss-logging: MavenReportException: Error while generating Javadoc: [ERROR] Exit code: 1 - error: invalid flag: --no-module-directories [ERROR] 1 error [ERROR] [ERROR] Command line was: /usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc --no-module-directories @options @packages
Bug#1012081: jboss-classfilewriter: FTBFS with OpenJDK 17 due to test failures
Source: jboss-classfilewriter Version: 1.2.5-1 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 jboss-classfilewriter fails to build with OpenJDK 17, almost all the tests fail: [INFO] --- [INFO] T E S T S [INFO] --- [INFO] Running org.jboss.classfilewriter.test.simple.FieldTest [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.033 s <<< FAILURE! - in org.jboss.classfilewriter.test.simple.FieldTest [ERROR] testCreatingField(org.jboss.classfilewriter.test.simple.FieldTest) Time elapsed: 0.008 s <<< ERROR! java.lang.Error: java.lang.NoSuchFieldException: override at org.jboss.classfilewriter.test.simple.FieldTest.testCreatingField(FieldTest.java:45) Caused by: java.lang.NoSuchFieldException: override at org.jboss.classfilewriter.test.simple.FieldTest.testCreatingField(FieldTest.java:45) [INFO] Running org.jboss.classfilewriter.test.simple.MethodTest [ERROR] Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0 s <<< FAILURE! - in org.jboss.classfilewriter.test.simple.MethodTest [ERROR] testCreatingMethod(org.jboss.classfilewriter.test.simple.MethodTest) Time elapsed: 0 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.jboss.classfilewriter.DefaultClassFactory at org.jboss.classfilewriter.test.simple.MethodTest.testCreatingMethod(MethodTest.java:53) [ERROR] testExceptionTypes(org.jboss.classfilewriter.test.simple.MethodTest) Time elapsed: 0 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.jboss.classfilewriter.DefaultClassFactory at org.jboss.classfilewriter.test.simple.MethodTest.testExceptionTypes(MethodTest.java:79) [INFO] Running org.jboss.classfilewriter.test.simple.SimpleTest [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0 s <<< FAILURE! - in org.jboss.classfilewriter.test.simple.SimpleTest [ERROR] simpleTest(org.jboss.classfilewriter.test.simple.SimpleTest) Time elapsed: 0 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.jboss.classfilewriter.DefaultClassFactory at org.jboss.classfilewriter.test.simple.SimpleTest.simpleTest(SimpleTest.java:32) [ERROR] testAddingInterfaces(org.jboss.classfilewriter.test.simple.SimpleTest) Time elapsed: 0 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.jboss.classfilewriter.DefaultClassFactory at org.jboss.classfilewriter.test.simple.SimpleTest.testAddingInterfaces(SimpleTest.java:46) [ERROR] testDefaultInterface(org.jboss.classfilewriter.test.simple.SimpleTest) Time elapsed: 0 s <<< ERROR! java.lang.NoClassDefFoundError: Could not initialize class org.jboss.classfilewriter.DefaultClassFactory at org.jboss.classfilewriter.test.simple.SimpleTest.testDefaultInterface(SimpleTest.java:39) ... [INFO] [ERROR] Tests run: 177, Failures: 0, Errors: 171, Skipped: 0 [INFO] [INFO] [INFO] BUILD FAILURE [INFO]
Bug#1012046: References / previous reports
Hi, Friends pointed me out to older bugs reports of the quite same problem with libvte. Situation has changed since but it seems kept in the wrong choices to me... Problems are there since 09/2009 (vte-0.21.6). https://www.climagic.org/bugreports/libvte-scrollback-written-to-disk.html It is pointing out that the suggestion I made in previous comment was also made in 2015 and has drawbacks : [...] it is inherited by all child processed launched inside the terminal which is probably not what they want. https://bugzilla.gnome.org/show_bug.cgi?id=631685#c50 Someone pointed out inhttps://bugzilla.xfce.org/show_bug.cgi?id=8183: While setting TMPDIR to a shm or tmpfs based location is a nice workaround for those who definitely want their scrollback in memory, it is cumbersome: it is inherited by all child processed launched inside the terminal which is probably not what they want. Moreover, it's not feasible to set this in some global environment definition file. For these people it would be convenient to support VTETMPDIR - if defined, it would take precedence over the standard tmp dir locations. Regards,
Bug#789694: schroot: Please consider patch to fix it on hurd-i386
Control: tags 789694 moreinfo Gabriele Giacone wrote... > attached patch makes schroot working on hurd, has been being tested on > exodar porterbox since many months. > It works around #763932 bug. > > More info in threads at > https://lists.debian.org/debian-hurd/2014/09/msg00058.html > https://lists.debian.org/debian-hurd/2015/05/msg00063.html Greetings, schroot 1.6.10-13 was accepted to unstable a few moments ago and should contain the fix. Can you please check whether there's anything left to do here? Regards, Christoph signature.asc Description: PGP signature
Bug#1012080: RFS: dia/0.97.3+git20220525-1 [ITA] -- Diagram editor
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "dia": * Package name : dia Version : 0.97.3+git20220525-1 Upstream Author : [fill in name and email of upstream] * URL : https://wiki.gnome.org/Apps/Dia/ * License : GPL-2, GFDL-NIV-1.1+ * Vcs : https://salsa.debian.org/phsw/dia Section : graphics The source builds the following binary packages: dia-common - Diagram editor (common files) dia - Diagram editor To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dia/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dia/dia_0.97.3+git20220525-1.dsc Changes since the last upload: dia (0.97.3+git20220525-1) unstable; urgency=medium . [ Philippe SWARTVAGHER ] * Use gbp to manage the source package . [ Nicolas Boulenguez ] * Move desktop file from dia-common to dia * Remove obsolete debian/*.dirs * control: explicit Rules-Requires-Root * copyright: HTTPS URL for copyright format * copyright: embed full GFDL-1.1 * rules: remove explicit --as-needed * rules: include buildflags.mk * remove shlibs:Depends for dia-common . [ arriott NZ ] * mime: stop quoting %s placeholder. Closes: #987402 . [ Nicolas Boulenguez ] * Switch to debhelper 13 * rules: trivial optimisation * rules: only create the docbook symlink once * Style: format and order some debhelper files . [ Philippe SWARTVAGHER ] * clean: do not let dh_clean remove INSTALL * control: new maintainer (Closes: #982055) * control: add Vcs-* fields * watch: update URL * control: Bumped Standards-Version to 4.6.1 * New upstream snapshot - Adapt packaging to the new Meson build system - Closes: #885800, #936393, #905233, #492396, #945876 - Drop fix-libxml2-config.patch: not required anymore - Adapt fix-doc.patch - Adapt fix-helpdir.patch - Drop fix-psdoc.patch: not required anymore - Drop fix-makefile.patch: not required anymore - Drop add-thumbnailer.patch: fixed upstream in 9ff6f043c511f5cc0225e7903e72d9c48d979c40 - Adapt remove-backup-files.patch - Drop errors-to-stderr.patch: fixed upstream in a67db4890f859a660d88263102bd1f47d2c8cdba - Drop fix-cast-warnings.patch: fixed upstream in 69c0d45c50c3bda8388e4a044c06114f6c75dacb and 2c96a9401c73c42b8875b777e93c6946232385ab - Drop fix-fr-po.patch: fixed upstream in 7659c9a4bee1a77ffc2a858fe940e4f4aaf1c014 - Drop fix-code-messages-typo.patch: fixed upstream in b76cc87fad7f53a6a548a2ec870abb5fbd1c089d - Drop freetype.patch: freetype dependency was removed upstream in d2ccbfb0344d3c23719fcb9661e2623830a0142d - Add fix-libdia-instal-dir.patch - Add use-local-dbman.patch * Fix some lintian issues Regards, Philippe.
Bug#1012079: misses jars in the declared classpaths
Package: libapache-poi-java Version: 4.0.1-3 Severity: normal Dear Maintainer, In debian/libapache-poi-java.classpath in the source package, some jars are missing in the declared classpaths. For instance, because I got exceptions when running code with the two below-mentioned POI jars in my classpath, I see at least - /usr/share/java/commons-compress.jar and /usr/share/java/commons-collections4.jar are missing in the classpath of /usr/share/java/poi-ooxml.jar; - /usr/share/java/jaxb-api.jar is missing in the classpath of /usr/share/java/poi.jar. Thanks and best wishes, -- Pierre
Bug#1011945: version _3 of po-file
Dear Tatsuya, during proof-reading, it was noticed that in string rc.c:214 an "and" and the abbreviation "e.g." have not been translated into German. They have been translated in the attached version _3 of the message catalogue. A similar question has risen with rc.c:210. The list in parenthesis starts with "all". In case, this list contains values that are expected verbatim, translating "all" into "alle" would be misleading/wrong. To be on the safe side, the word has not been translated in version _3. Best regards Markus # German translation of w3m # Copyright (C) 2014 THE w3m'S COPYRIGHT HOLDER # This file is distributed under the same license as the w3m package. # Markus Hiereth , 2014,2022. msgid "" msgstr "" "Project-Id-Version: w3m 0.5.3\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2021-07-03 15:24+0900\n" "PO-Revision-Date: 2022-05-29 09:00+0100\n" "Last-Translator: Markus Hiereth \n" "Language-Team: German \n" "Language: de\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" "X-Generator: Virtaal 0.7.1\n" #: menu.c:269 msgid " Back (b) " msgstr " Zurück (b) " #: menu.c:270 msgid " Select Buffer(s) " msgstr " Puffer auswählen (s) " #: menu.c:272 msgid " Select Tab (t) " msgstr " Reiter auswählen (t) " #: menu.c:274 msgid " View Source (v) " msgstr " Codeansicht(v) " #: menu.c:275 msgid " Edit Source (e) " msgstr " Code bearbeiten(e) " #: menu.c:276 msgid " Save Source (S) " msgstr " Code speichern (S) " #: menu.c:277 msgid " Reload (r) " msgstr " Erneut laden (r) " #: menu.c:278 menu.c:285 menu.c:289 msgid " " msgstr " -- " #: menu.c:279 msgid " Go Link (a) " msgstr " Ziel öffnen.. (a) " #: menu.c:280 msgid " on New Tab (n) " msgstr " ..in neuem Reiter (n) " #: menu.c:281 msgid " Save Link(A) " msgstr " Ziel speichern (A) " #: menu.c:282 msgid " View Image (i) " msgstr " Bild anzeigen (i) " #: menu.c:283 msgid " Save Image (I) " msgstr " Bild speichern (I) " #: menu.c:284 msgid " View Frame (f) " msgstr " Frames zeigen (f) " #: menu.c:286 msgid " Bookmark (B) " msgstr " Lesezeichen(B) " #: menu.c:287 msgid " Help (h) " msgstr " Hilfe (h) " #: menu.c:288 msgid " Option (o) " msgstr " Einstellungen (o) " #: menu.c:290 msgid " Quit (q) " msgstr " Programm verlassen (q) " #: rc.c:62 msgid "External Viewer Setup" msgstr "Konfiguration für externe Anzeigeprogramme" #: rc.c:63 msgid "Tab width in characters" msgstr "Tabulatorbreite in Zeichen" #: rc.c:64 msgid "Indent for HTML rendering" msgstr "Einzug bei HTML-Darstellung" #: rc.c:65 msgid "Number of pixels per character (4.0...32.0)" msgstr "Anzahl von Pixeln pro Zeichen (4.0 bis 32.0)" #: rc.c:66 msgid "Number of pixels per line (4.0...64.0)" msgstr "Anzahl von Pixeln pro Zeile (4.0 bis 64.0)" # entsprechend Bescheibung aus MANUAL.html, mh 14.10.2014 #: rc.c:67 msgid "Number of remembered lines when used as a pager" msgstr "Anzahl gemerkter, über die Standardeingabe erhaltener Zeilen" #: rc.c:68 msgid "Use URL history" msgstr "URL-Chronik verwenden" #: rc.c:69 msgid "Number of remembered URL" msgstr "Anzahl von URLs in Chronik" #: rc.c:70 msgid "Save URL history" msgstr "URL-Chronik speichern" #: rc.c:71 msgid "Render frames automatically" msgstr "Frames selbstständig darstellen" #: rc.c:72 msgid "Treat argument without scheme as URL" msgstr "Eingabe ohne Protokoll-Präfix als URL auffassen" #: rc.c:73 msgid "Use _self as default target" msgstr "_self als Standard-Zielfenster verwenden" #: rc.c:74 msgid "Open link on new tab if target is _blank or _new" msgstr "" "Link in neuem Reiter öffnen, falls für Zielfenster _blank oder _new " "definiert ist" #: rc.c:75 msgid "Open download list panel on new tab" msgstr "Downloadliste in neuem Reiter öffnen" #: rc.c:76 msgid "Display link URL automatically" msgstr "URL der Links selbstständig anzeigen" #: rc.c:77 msgid "Display link numbers" msgstr "Linknummern anzeigen" #: rc.c:78 msgid "Display decoded URL" msgstr "URL entschlüsselt anzeigen" #: rc.c:79 msgid "Display current line number" msgstr "Aktuelle Zeilennummer anzeigen" #: rc.c:80 msgid "Display inline images" msgstr "Eingebettete Bilder anzeigen" #: rc.c:81 msgid "Display pseudo-ALTs for inline images with no ALT or TITLE string" msgstr "Pseudo-ALTs zu eingebetteten Bildern ohne ALT oder TITLE anzeigen" #: rc.c:83 msgid "Load inline images automatically" msgstr "Eingebettete Bilder selbstständig laden" #: rc.c:84 msgid "Maximum processes for parallel image loading" msgstr "Anzahl zulässiger Prozesse zum gleichzeitigen Laden von Bildern" #: rc.c:85 msgid "Use external image viewer" msgstr "Externen Bildbetrachter verwenden" #: rc.c:86 msgid "Scale of image (%)" msgstr "Bilder prozentual skalieren" #: rc.c:87 msgid "Exter
Bug#1012078: groff-base: eqn breaks tbl spacing/layout with inline equations, but not in T{ T}; nroff only?
Package: groff-base
Version: 1.22.4-6
Severity: normal
Dear Maintainer,
I'm attaching a cut-down manual that illustrates this.
In short:
cell $ equation $cellcell
welds everything since some point together
(i.e. either cell I[equation]cellcell or cellI[equation]cellcell),
but appears to render the equation correctly,
adding data before and after the equation explodes the table in a
different way, but embedding it in T{ T} (or T{ .EQ .EN T}) renders
correctly.
All render correctly in troff (-Tps).
The output is
-- >8 --
SYNOPSIS
HISTORY
Table 1
PlatformFlags API Source Notes
illumos/SPARC khx SunOSSPARC ID PROM Can be configured per-zone
illumos/x86 kHxpSunOS[M3]69(likewise)
NetBSD/SPARCkhs 4.4BSD SPARC ID PROM
Table 2
Platform Flags API
Source Notes
─
illumos/SPARCkhx SunOS
SPARC ID PROM Can be configured per-zone
illumos/x86 kHxpSunOSa [M3]69
b(likewise)
NetBSD/SPARC khs 4.4BSD
SPARC ID PROM
Table 3
PlatformFlags API Source Notes
illumos/SPARC khx SunOSSPARC ID PROM Can be configured per-zone
illumos/x86 kHxpSunOS[M3]69 (likewise)
NetBSD/SPARCkhs 4.4BSD SPARC ID PROM
Table 4
PlatformFlags API Source Notes
illumos/SPARC khx SunOSSPARC ID PROM Can be configured per-zone
illumos/x86 kHxpSunOS[M3]69 (likewise)
NetBSD/SPARCkhs 4.4BSD SPARC ID PROM
-- >8 --
with all "[M3]" instances italicised as expected.
Best,
наб
-- System Information:
Debian Release: 11.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-14-amd64 (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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 groff-base depends on:
ii libc6 2.31-13+deb11u3
ii libgcc-s1 10.2.1-6
ii libstdc++610.2.1-6
ii libuchardet0 0.0.7-1
groff-base recommends no packages.
Versions of packages groff-base suggests:
ii groff 1.22.4-6
-- no debconf information
'\" et
.\" SPDX-License-Identifier: 0BSD
.\"
.Dd
.Dt HOSTID 1
.Os
.
.Sh SYNOPSIS
.Nm
.
.EQ
delim $$
.EN
.
.Sh HISTORY
.Ss Table 1
.TS
lb lb lb lb lb
l lb l l l .
.
PlatformFlags API Source Notes
_
.\" git head 2022-05-29, also see [1]
illumos/SPARC khx SunOS SPARC ID PROM Can be configured per-zone
illumos/x86 kHxpSunOS $ "[M3]" sup 69 $ (likewise)
\ \&
.\" CVS head 2022-05-29
NetBSD/SPARCkhs 4.4BSD SPARC ID PROM
.TE
.
.Ss Table 2
.TS
lb lb lb lb lb
l lb l l l .
.
PlatformFlags API Source Notes
_
.\" git head 2022-05-29, also see [1]
illumos/SPARC khx SunOS SPARC ID PROM Can be configured per-zone
illumos/x86 kHxpSunOS a $ "[M3]" sup 69 $ b (likewise)
\ \&
.\" CVS head 2022-05-29
NetBSD/SPARCkhs 4.4BSD SPARC ID PROM
.TE
.
.Ss Table 3
.TS
lb lb lb lb lb
l lb l l l .
.
PlatformFlags API Source Notes
_
.\" git head 2022-05-29, also see [1]
illumos/SPARC khx SunOS SPARC ID PROM Can be configured per-zone
illumos/x86 kHxpSunOS T{
$ "[M3]" sup 69 $
T} (likewise)
\ \&
.\" CVS head 2022-05-29
NetBSD/SPARCkhs 4.4BSD SPARC ID PROM
.TE
.
.Ss Table 4
.TS
lb lb lb lb lb
l lb l l l .
.
PlatformFlags API Source Notes
_
.\" git head 2022-05-29, also see [1]
illumos/SPARC khx SunOS SPARC ID PROM Can be configured per-zone
illumos/x86 kHxpSunOS T{
.EQ
"[M3]" sup 69
.EN
T} (likewise)
\ \&
.\" CVS head 2022-05-29
NetBSD/SPARCkhs 4.4BSD SPARC ID PROM
.TE
signature.asc
Description: PGP signature
Bug#1011609: bogl-bterm: [PATCH] Several improvements
Hello,
Zhang Boyang, le dim. 29 mai 2022 14:23:19 +0800, a ecrit:
> Subject: [PATCH v2 1/8] Better quit handling
That looks good, applied!
> From 302952c64952197d694039358df407ec3ffa418a Mon Sep 17 00:00:00 2001
> From: Zhang Boyang
> Date: Mon, 23 May 2022 14:10:52 +0800
> Subject: [PATCH v2 2/8] Better font reload handling
>
> Previous font reload code will leak a mmap on each reload. This patch
> adds the ability to munmap old font after reload. However, this also
> introduces a bug, if font reload is triggered while drawing in progress,
> after signal handler returns, the drawing code will continue to use old
> font which has been freed, causing crash. This will be fixed in next
> patch.
Then is it not possible to exchange the patch order? So that whatever
the number of patches being applied, things work completely.
> - void *f;
> - struct bogl_font *font;
> + void *f = (void *)-1;
[...]
>f = mmap(0, buf.st_size, PROT_READ, MAP_SHARED, fd, 0);
>if (f == (void *)-1)
While at it, please use MAP_FAILED rather than the hardcoded (void*)-1
Otherwise it looks good.
> From 4b2e0651edf19cab4b162c686c21e81682c854a0 Mon Sep 17 00:00:00 2001
> From: Zhang Boyang
> Date: Tue, 24 May 2022 12:58:01 +0800
> Subject: [PATCH v2 3/8] Fix incorrect signal handling
>
> There are problems in signal handlers. Signal handlers must not call any
> non-async-signal-safe functions, and they must save-restore errno if
> errno is modified inside signal handlers. This patch fixes these
> problems by deferring real tasks to main loop. This also fixes crashes
> caused by font reloading which was mentioned in previous patch.
> diff --git a/bterm.c b/bterm.c
> index 28ccb53..b0a1189 100644
> --- a/bterm.c
> +++ b/bterm.c
> @@ -160,7 +160,6 @@ void sigchld(int sig)
>quit_status = status;
> quit = 1;
>}
> - signal(SIGCHLD, sigchld);
>errno = errsv;
> }
>
This looks unrelated and bogus?
Otherwise it looks good.
> From e7fe989fbbda4acfd9971604b7ffa84899cb343a Mon Sep 17 00:00:00 2001
> From: Zhang Boyang
> Date: Mon, 23 May 2022 22:07:37 +0800
> Subject: [PATCH v2 4/8] Use ioctl(FBIOPAN_DISPLAY) to update screen after
> drawing
>
> Some framebuffer driver like i915 need explicit notify after drawing,
> otherwise modifications in graphics buffer will not be reflected on
> screen, so use FBIOPAN_DISPLAY to do this notify.
Do you have a reference that documents this?
Otherwise it looks good.
> From 04d88a6ff7114750c67cdb58e07122bb430763a9 Mon Sep 17 00:00:00 2001
> From: Zhang Boyang
> Date: Tue, 24 May 2022 23:49:31 +0800
> Subject: [PATCH v2 5/8] Font scaler
[...]
> +bgf_scale_inline(struct bogl_bgf *bgf, int scale)
> +{
> + void *new_f = (void *)-1;
> + off_t new_size;
> + struct bogl_font new_font;
> +
> + /* old_size*pow(scale,2) should enough and have some waste here */
> + new_size = bgf->size * scale * scale;
> +
> + /* Allocate new memory */
> + new_f = mmap(0, new_size, PROT_READ | PROT_WRITE, MAP_PRIVATE |
> MAP_ANONYMOUS, -1, 0);
> + if (new_f == (void *)-1) {
MAP_FAILED here as well.
> +/* If memory allocation failed, skip scaling silently */
> +goto fail;
> + }
> +
> + /* Copy old font data to new memory */
> + memcpy(new_f, bgf->f, bgf->size);
> +
> + /* Set font metadata */
> + struct bogl_font *font = &new_font;
> + memcpy(font, new_f + 4, sizeof(*font));
> + font->name = ((void *)font->name - (void *)0) + new_f;
> + font->offset = ((void *)font->offset - (void *)0) + new_f;
> + font->index = ((void *)font->index - (void *)0) + new_f;
> + font->content = ((void *)font->content - (void *)0) + new_f;
Please make these an inline function rather than copy/pasting them from
bogl_mmap_font.
Otherwise it looks good.
> Subject: [PATCH v2 6/8] Fix character occasionally disappears from right edge
> of screen
That looks good, applied!
> Subject: [PATCH v2 7/8] Fix out-of-bound read in tcfb's cmap_lookup()
That looks good, applied!
> Subject: [PATCH v2 8/8] Fix rightmost pixel of each line not cleared by
> bogl_vga16_text()
That looks good, applied!
And thanks!
Samuel
Bug#890381: Fixed by unattended-upgrades commit e4d0f0bb17b843743f83ff5ee696ce5de0ede435
Fixed by unattended-upgrades commit e4d0f0bb17b843743f83ff5ee696ce5de0ede435 "Skip updates on metered connections" (Jul 11 2018), right? Regards
Bug#1012077: linuxinfo FTBFS on riscv64
Package: linuxinfo
Version: 3.3.3-1
Severity: serious
Tags: ftbfs patch upstream
Justification: fails to build from source
X-Debbugs-Cc: ab.bea...@gmail.com
Dear Maintainer,
linuxinfo currently fails to build on riscv64 due to this architecture not being
supported by upstream. I am attaching a patch which adds placeholder support for
this architecture and allows building the riscv64 debian package from source.
Please consider applying this patch (or similar) for the next upload.
In addition, the /proc information below is for a riscv64 VisionFive V1 SBC.
Thank you,
-Alan Beadle
-- Package-specific info:
/proc/cpuinfo:
processor : 0
hart: 1
isa : rv64imafdc
mmu : sv39
uarch : sifive,u74-mc
processor : 1
hart: 0
isa : rv64imafdc
mmu : sv39
uarch : sifive,u74-mc
Size of /proc/kcore:
-r 1 root root 18446744000862892032 May 25 19:58 /proc/kcore
/proc/meminfo:
MemTotal:7351200 kB
MemFree: 1778728 kB
MemAvailable:6685728 kB
Buffers: 75344 kB
Cached: 4719384 kB
SwapCached:0 kB
Active: 894708 kB
Inactive:4391724 kB
Active(anon):460 kB
Inactive(anon): 497556 kB
Active(file): 894248 kB
Inactive(file): 3894168 kB
Unevictable: 15396 kB
Mlocked: 15396 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 912 kB
Writeback: 0 kB
AnonPages:507140 kB
Mapped: 260068 kB
Shmem: 628 kB
KReclaimable: 204236 kB
Slab: 241012 kB
SReclaimable: 204236 kB
SUnreclaim:36776 kB
KernelStack:1696 kB
PageTables: 3264 kB
NFS_Unstable: 0 kB
Bounce:0 kB
WritebackTmp: 0 kB
CommitLimit: 3675600 kB
Committed_AS: 687620 kB
VmallocTotal: 67108864 kB
VmallocUsed:6316 kB
VmallocChunk: 0 kB
Percpu: 552 kB
CmaTotal: 655360 kB
CmaFree: 650112 kB
HugePages_Total: 0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize: 2048 kB
Hugetlb: 0 kB
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: riscv64
Kernel: Linux 5.18.0-starfive-5.18 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages linuxinfo depends on:
ii libc6 2.33-7
linuxinfo recommends no packages.
linuxinfo suggests no packages.
-- no debconf information
Index: linuxinfo-3.3.3/linuxinfo.h
===
--- linuxinfo-3.3.3.orig/linuxinfo.h
+++ linuxinfo-3.3.3/linuxinfo.h
@@ -103,6 +103,10 @@
#define system_avr32
#endif
+#if defined(__riscv)
+#define system_riscv
+#endif
+
#if (SIZEOF_LONG > 4)
#define LONGLONG long int
#define LONGSPEC "%ld"
Index: linuxinfo-3.3.3/linuxinfo_riscv.c
===
--- /dev/null
+++ linuxinfo-3.3.3/linuxinfo_riscv.c
@@ -0,0 +1,25 @@
+/*
+linuxinfo_riscv.c
+
+ This allows compilation on riscv
+
+*/
+
+#include
+#include "linuxinfo.h"
+
+#ifdef system_riscv
+
+void GetHardwareInfo(int fd, struct hw_stat *hw)
+{
+ sprintf(hw->hw_memory, LONGSPEC, 0);
+
+ hw->hw_processors = 0;
+
+ sprintf(hw->hw_cpuinfo, "%s", "Unknown");
+ sprintf(hw->hw_bogomips, "%0.2f", 0.0);
+ sprintf(hw->hw_megahertz, "?");
+ hw->hw_processors = 0;
+}
+
+#endif /* system_riscv */
Index: linuxinfo-3.3.3/Makefile.am
===
--- linuxinfo-3.3.3.orig/Makefile.am
+++ linuxinfo-3.3.3/Makefile.am
@@ -4,7 +4,8 @@ linuxinfo_SOURCES = linuxinfo.c linuxinf
linuxinfo_alpha.c linuxinfo_ia64.c linuxinfo_intel.c \
linuxinfo_m68k.c linuxinfo_ppc.c linuxinfo_sh.c \
linuxinfo_hppa.c linuxinfo_s390.c linuxinfo_avr.c \
- linuxinfo_sparc.c linuxinfo_mips.c linuxinfo_unknown.c
+ linuxinfo_sparc.c linuxinfo_mips.c linuxinfo_riscv.c \
+ linuxinfo_unknown.c
man_MANS = po4a/linuxinfo.1
EXTRA_DIST= config.rpath CREDITS
VERSION = 3.3.3
Bug#1012035: reprotest: Salsa CI randomly fails because dpkg-source can't change timestamp
Hello, Zhang Boyang, le dim. 29 mai 2022 14:10:35 +0800, a ecrit: > I found Salsa CI reprotest on my repo fails when "FAKETIME variation: > faketime = [balabala]" is decided. The relevant output is: > > dpkg-source: error: cannot change timestamp for > build-experiment-1/.pc/applied-patches: Invalid argument I have seen reprotest randomly fail in the salsa CI for various packages indeed. Samuel
Bug#1012076: varnish: Remove me as uploader
Package: varnish Severity: normal X-Debbugs-Cc: Tollef Fog Heen Hi, I haven't been active in maintaining Varnish for quite a few years, could you please remove me from uploaders? -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
Bug#1011360: python-scrapy 1.5.1-1+deb10u1 flagged for acceptance
package release.debian.org tags 1011360 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: python-scrapy Version: 1.5.1-1+deb10u1 Explanation: don't send authentication data with all requests [CVE-2021-41125]; don't expose cookies cross-domain when redirecting [CVE-2022-0577]
Bug#1011286: orca 3.30.1-2 flagged for acceptance
package release.debian.org tags 1011286 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: orca Version: 3.30.1-2 Explanation: fix use with WebKitGTK 2.36
Bug#1003293: postfix 3.4.23-0+deb10u1 flagged for acceptance
package release.debian.org tags 1003293 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: postfix Version: 3.4.23-0+deb10u1 Explanation: new upstream stable release; do not override user set default_transport; if-up.d: do not error out if postfix can't send mail yet; fix duplicate bounce_notice_recipient entries in postconf output
Bug#1011634: fixed in python-popcon 3.0.0
On Sun, 29 May 2022 09:37:06 +, Debian FTP Masters wrote: >* Improved output and added verbose output (Closes: #1011634) Thanks Gregor > Herrmann for the patch, I ended up using a different solution. Thanks alot for this quick and nice improvement! If I may add two tiny wishlist requests: 1) The tabular format doesn't work so well with long package names: % popcon libdancer2-plugin-passphrase-perl PACKAGE VALUE libdancer2-plugin-passphrase-perl 8 % popcon -v libdancer2-plugin-passphrase-perl PACKAGE VOTE OLDRECENT NO FILES libdancer2-plugin-passphrase-perl 2 5 1 0 2) Personally I'd find it nice to have to total number / the sum of the 4 categories in the verbose output as well; what do you think? Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Bug#1011198: needrestart 3.5-4+deb11u2 flagged for acceptance
package release.debian.org tags 1011198 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: needrestart Version: 3.5-4+deb11u2 Explanation: make cgroup detection for services and user sessions cgroup v2 aware
Bug#1010963: nginx 1.18.0-6.1+deb11u2 flagged for acceptance
package release.debian.org tags 1010963 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: nginx Version: 1.18.0-6.1+deb11u2 Explanation: mitigate application layer protocol content confusion attack in the Mail module [CVE-2021-3618]
Bug#1011022: htmldoc 1.9.11-4+deb11u3 flagged for acceptance
package release.debian.org tags 1011022 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: htmldoc Version: 1.9.11-4+deb11u3 Explanation: fix infinite loop [CVE-2022-24191], integer overflow issues [CVE-2022-27114] and heap buffer overflow issue [CVE-2022-28085]
Bug#1010924: node-eventsource 1.0.7-1+deb11u1 flagged for acceptance
package release.debian.org tags 1010924 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: node-eventsource Version: 1.0.7-1+deb11u1 Explanation: sttrip sensitive headers on redirect to different origin [CVE-2022-1650]
Bug#1010383: node-ejs 2.5.7-3+deb11u1 flagged for acceptance
package release.debian.org tags 1010383 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: node-ejs Version: 2.5.7-3+deb11u1 Explanation: fix server-side template injection issue [CVE-2022-29078]
Bug#1010211: grunt 1.3.0-1+deb11u1 flagged for acceptance
package release.debian.org tags 1010211 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: grunt Version: 1.3.0-1+deb11u1 Explanation: fix path traversal issue [CVE-2022-0436]
Bug#1012075: openvpn: OpenVPN - Debian/SID release '2.6.0~git20220518+dco-1' breaks connection buildup
Package: openvpn Version: 2.5.6-1 Severity: important Dear Debian OpenVPN Maintenaner, This is a pretty serious bug as it breaks the usage of VPN. The latest version of OpenVPN in Debian/SID repo '2.6.0~git20220518+dco-1' won't connect due to TLS errors during connection attempts. Only downgrade to version '2.5.6-1' solves the issue. I had to blur some characters like IP adresses. Destination is Sophos UTM Appliances. I attached a textfile which compare both outputs of each release. Best regards, Henrik -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 openvpn depends on: ii debconf [debconf-2.0] 1.5.79 ii iproute2 5.17.0-2 ii libc6 2.33-7 ii liblz4-1 1.9.3-2 ii liblzo2-2 2.10-2 ii libpam0g 1.4.0-13 ii libpkcs11-helper1 1.28-1+b1 ii libssl1.1 1.1.1o-1 ii libsystemd0251.1-1 ii lsb-base 11.2 Versions of packages openvpn recommends: ii easy-rsa 3.0.8-1 Versions of packages openvpn suggests: ii openssl 3.0.3-5 pn openvpn-systemd-resolved pn resolvconf -- debconf information: openvpn/create_tun: false Output latest OpenVPN Debian/SID release '2.6.0~git20220518+dco-1' in repo - This version doesn't connect to destination ! root@debian:/home/henrik/Downloads# openvpn hschoepel@ssl_vpn_config.ovpn 2022-05-29 19:07:47 WARNING: Compression for receiving enabled. Compression has been used in the past to break encryption. Sent packets are not compressed unless "allow-compression yes" is also set. 2022-05-29 19:07:47 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations. 2022-05-29 19:07:47 Cannot find ovpn_dco netlink component: Object not found 2022-05-29 19:07:47 Note: Kernel support for ovpn-dco missing, disabling data channel offload. 2022-05-29 19:07:47 OpenVPN 2.6_git x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] [DCO] built on May 20 2022 2022-05-29 19:07:47 library versions: OpenSSL 3.0.3 3 May 2022, LZO 2.10 Enter Auth Username: hschoepel 🔐 Enter Auth Password: ** 2022-05-29 19:08:08 TCP/UDP: Preserving recently used remote address: [AF_INET]*:8443 2022-05-29 19:08:08 Socket Buffers: R=[131072->131072] S=[16384->16384] 2022-05-29 19:08:08 Attempting to establish TCP connection with [AF_INET]*:8443 2022-05-29 19:08:08 TCP connection established with [AF_INET]*:8443 2022-05-29 19:08:08 Note: enable extended error passing on TCP/UDP socket failed (IPV6_RECVERR): Protocol not available (errno=92) 2022-05-29 19:08:08 TCP_CLIENT link local: (not bound) 2022-05-29 19:08:08 TCP_CLIENT link remote: [AF_INET]*:8443 2022-05-29 19:08:08 TLS: Initial packet from [AF_INET]*.35:8443, sid=2a3742bf 758117bf 2022-05-29 19:08:08 TLS error: Unsupported protocol. This typically indicates that client and server have no common TLS version enabled. This can be caused by mismatched tls-version-min and tls-version-max options on client and server. If your OpenVPN client is between v2.3.6 and v2.3.2 try adding tls-version-min 1.0 to the client configuration to use TLS 1.0+ instead of TLS 1.0 only 2022-05-29 19:08:08 OpenSSL: error:0A000102:SSL routines::unsupported protocol 2022-05-29 19:08:08 TLS_ERROR: BIO read tls_read_plaintext error 2022-05-29 19:08:08 TLS Error: TLS object -> incoming plaintext read error 2022-05-29 19:08:08 TLS Error: TLS handshake failed 2022-05-29 19:08:08 Fatal TLS error (check_tls_errors_co), restarting 2022-05-29 19:08:08 SIGUSR1[soft,tls-error] received, process restarting 2022-05-29 19:08:08 Restart pause, 5 second(s) 2022-05-29 19:08:13 TCP/UDP: Preserving recently used remote address: [AF_INET]*:8443 2022-05-29 19:08:13 Socket Buffers: R=[131072->131072] S=[16384->16384] 2022-05-29 19:08:13 Attempting to establish TCP connection with [AF_INET]*:8443 2022-05-29 19:08:13 TCP connection established with [AF_INET]*:8443 2022-05-29 19:08:13 Note: enable extended error passing on TCP/UDP socket failed (IPV6_RECVERR): Protocol not available (errno=92) 2022-05-29 19:08:13 TCP_CLIENT link local: (not bound) 2022-05-29 19:08:13 TCP_CLIENT link remote: [AF_INET]*:8443 2022-05-29 19:08:13 TLS: Initial packet from [AF_INET]*:8443, sid=eceadd8a 6679da5c 2022-05-29 19:08:13 TLS error: Uns
Bug#1008161: geeqie 1.6-9+deb11u1 flagged for acceptance
package release.debian.org tags 1008161 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: geeqie Version: 1.6-9+deb11u1 Explanation: fix Ctrl click inside of a block selection
Bug#1011942: php-guzzlehttp-psr7 1.7.0-1+deb11u1 flagged for acceptance
package release.debian.org tags 1011942 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: php-guzzlehttp-psr7 Version: 1.7.0-1+deb11u1 Explanation: fix improper header parsing [CVE-2022-24775]
Bug#1011426: tcpdump 4.99.0-2+deb11u1 flagged for acceptance
package release.debian.org tags 1011426 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: tcpdump Version: 4.99.0-2+deb11u1 Explanation: update AppArmor profile to allow access to *.cap files, and handle numerical suffix in filenames added by -W
Bug#1011331: node-raw-body 2.4.1-2+deb11u1 flagged for acceptance
package release.debian.org tags 1011331 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: node-raw-body Version: 2.4.1-2+deb11u1 Explanation: fix potential denial of service issue in node-express, by using node-iconv-lite rather than node-iconv
Bug#1010857: unrar-nonfree 6.0.3-1+deb11u1 flagged for acceptance
package release.debian.org tags 1010857 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: unrar-nonfree Version: 6.0.3-1+deb11u1 Explanation: fix directory traversal issue [CVE-2022-30333]
Bug#1010439: node-sqlite3 5.0.0+ds1-1+deb11u1 flagged for acceptance
package release.debian.org tags 1010439 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: node-sqlite3 Version: 5.0.0+ds1-1+deb11u1 Explanation: fix denial of service issue [CVE-2022-21227]
Bug#1009726: samba 4.13.13+dfsg-1~deb11u4 flagged for acceptance
package release.debian.org tags 1009726 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: samba Version: 4.13.13+dfsg-1~deb11u4 Explanation: fix winbind start failure when "allow trusted domains = no" is used; fix MIT Kerberos authentication; fix share escape issue via mkdir race condition [CVE-2021-43566]; fix possible serious data corruption issue due to Windows client cache poisoning; fix installation on non-systemd systems
Bug#1009363: ruby-net-ssh 6.1.0-2+deb11u1 flagged for acceptance
package release.debian.org tags 1009363 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: ruby-net-ssh Version: 6.1.0-2+deb11u1 Explanation: fix authentication against systems using OpenSSH 8.8
Bug#1009345: node-moment 2.29.1+ds-2+deb11u1 flagged for acceptance
package release.debian.org tags 1009345 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: node-moment Version: 2.29.1+ds-2+deb11u1 Explanation: fix path traversal issue [CVE-2022-24785]
Bug#1008168: node-url-parse 1.5.3-1+deb11u1 flagged for acceptance
package release.debian.org tags 1008168 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: node-url-parse Version: 1.5.3-1+deb11u1 Explanation: fix authentication bypass issues [CVE-2022-0686 CVE-2022-0691]
Bug#1008153: node-node-forge 0.10.0~dfsg-3+deb11u1 flagged for acceptance
package release.debian.org tags 1008153 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: node-node-forge Version: 0.10.0~dfsg-3+deb11u1 Explanation: fix signature verification issues [CVE-2022-24771 CVE-2022-24772 CVE-2022-24773]
Bug#1008162: node-minimist 1.2.5+~cs5.3.1-2+deb11u1 flagged for acceptance
package release.debian.org tags 1008162 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: node-minimist Version: 1.2.5+~cs5.3.1-2+deb11u1 Explanation: fix prototype pollution issue [CVE-2021-44906]
Bug#1008045: node-mermaid 8.7.0+ds+~cs27.17.17-3+deb11u1 flagged for acceptance
package release.debian.org tags 1008045 = bullseye pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian bullseye. Thanks for your contribution! Upload details == Package: node-mermaid Version: 8.7.0+ds+~cs27.17.17-3+deb11u1 Explanation: fix cross-site scripting issue [CVE-2021-23648]
Bug#1012025: nftables.conf: trying to import nftables.conf and get unexpected meta or ip6 when trying to start
Hi Arturo,
I changed that to inet and I had to change the line for my IPv6 to look
like this:
ICMPv6 packets which must not be dropped, see
https://tools.ietf.org/html/rfc4890#section-4.4.1
meta nfproto ipv6 icmpv6 type { destination-
unreachable, packet-too-big, time-exceeded, parameter-problem, echo-
reply, echo-request, nd-router-solicit, nd-router-advert, nd-neighbor-
solicit, nd-neighbor-advert, 148, 149 } accept
#ipv6 saddr fe80::/10
icmpv6 type { 130, 131, 132, 134, 143, 151, 152, 153
}accept
I'm not sure why I needed to comment out the local loopback in IPv6 but
it works now. I'll find out if the neighbor discovery packet quit
getting rejected now.
Thanks for the help,
Tim
On Sun, 2022-05-29 at 09:30 +0200, Arturo Borrero Gonzalez wrote:
>
>
> On Sun, May 29, 2022, 01:03 Tim McConnell
> wrote:
> > Package: nftables
> > Version: 1.0.2-1
> > Severity: important
> > File: nftables.conf
> > Tags: ipv6
> > X-Debbugs-Cc: tmcconnell...@gmail.com
> >
> > Dear Maintainer,
> >
> > What led up to the situation?
> > Trying to configure and enable nftables to stop ip6 neighbor
> > discovery packets
> > from being rejected by VPN
> >
> > What exactly did you do (or not do) that was effective (or
> > ineffective)? Attempted to use workstation.nft in examples
> > folder and
> > looked for documentation on the web.I couldn't find anything newer
> > than 2014
> > and asked on Debian Forums and Linuxquestions.org
> >
> > What was the outcome of this action?
> > Attempt to run 'sudo systemctl start nftables.service' and receive
> > this error:
> > Job for nftables.service failed because the control process exited
> > with error
> > code.
> > See "systemctl status nftables.service" and "journalctl -xeu
> > nftables.service"
> > for details.
> > tmick@DebianTim:~/recap$ sudo systemctl status nftables.service
> > × nftables.service - nftables
> > Loaded: loaded (/lib/systemd/system/nftables.service; enabled;
> > vendor
> > preset: enabled)
> > Active: failed (Result: exit-code) since Sat 2022-05-28
> > 16:39:05 CDT; 7s
> > ago
> > Docs: man:nft(8)
> > http://wiki.nftables.org
> > Process: 1704177 ExecStart=/usr/sbin/nft -f /etc/nftables.conf
> > (code=exited, status=1/FAILURE)
> > Main PID: 1704177 (code=exited, status=1/FAILURE)
> > CPU: 24ms
> >
> > May 28 16:39:05 DebianTim nft[1704177]:
> > ^^
> > May 28 16:39:05 DebianTim nft[1704177]: /etc/nftables.conf:18:3-6:
> > Error:
> > syntax error, unexpected meta
> > May 28 16:39:05 DebianTim nft[1704177]: meta
> > nexthdr ipv6
> > icmpv6 type { destination-unreachable, packet-too>
> > May 28 16:39:05 DebianTim nft[1704177]:
> > May 28 16:39:05 DebianTim nft[1704177]: /etc/nftables.conf:19:8-12:
> > Error:
> > syntax error, unexpected saddr, expecting string
> > May 28 16:39:05 DebianTim nft[1704177]: ipv6 saddr
> > fe80::/10
> > icmpv6 type { 130, 131, 132, 134, 143, 151, 15>
> > May 28 16:39:05 DebianTim nft[1704177]: ^
> > May 28 16:39:05 DebianTim systemd[1]: nftables.service: Main
> > process exited,
> > code=exited, status=1/FAILURE
> > May 28 16:39:05 DebianTim systemd[1]: nftables.service: Failed with
> > result
> > 'exit-code'.
> > May 28 16:39:05 DebianTim systemd[1]: Failed to start nftables.
> > I've tried other methods as inet etc and still get this type of
> > error.
> >
> > What outcome did you expect instead? For documentation to be clear
> > enough for
> > this not to be a problem and the nftables to be able to add this
> > filter.
> >
> >
> > -- System Information:
> > Debian Release: bookworm/sid
> > APT prefers testing
> > APT policy: (500, 'testing')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> >
> > Kernel: Linux 5.17.0-1-rt-amd64 (SMP w/2 CPU threads; PREEMPT)
> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 nftables depends on:
> > ii libc6 2.33-7
> > ii libedit2 3.1-20210910-1
> > ii libnftables1 1.0.2-1
> >
> > Versions of packages nftables recommends:
> > ii netbase 6.3
> >
> > Versions of packages nftables suggests:
> > pn firewalld
> >
> > -- Configuration Files:
> > /etc/nftables.conf changed:
> > flush ruleset
> > table enp1s0 filter {
>
> This table declaration is missing family specificiation, which
> defaults to IPv4. I think you canot use IPv6 stuff in v4 tables.
>
> I think you may want to use a table in the 'inet' family, which is
> dual-stack, and should accept both IPv4 and IPv6 stuff.
>
>
>
>
> > chain base_checks {
> > # Drop invalid connections and allow established/related
> > connections
> > ct state invalid drop
> > ct state {established, related} accept
>
Bug#1012074: python-rocksdb: FTBFS with rocksdb 7.2+
Source: python-rocksdb Version: 0.8.0~rc3-2 Severity: important Tags: ftbfs upstream bookworm sid Hi, RocksDB in Sid is outdated. Packaged its newest release and uploaded to experimental. Would like to do the library transition, but your package fails to build: creating build/temp.linux-x86_64-3.10/rocksdb x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -g -O2 -ffile-prefix-map=rocksdb/7.2/transition/python-rocksdb-0.8.0~rc3=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.10 -c rocksdb/_rocksdb.cpp -o build/temp.linux-x86_64-3.10/rocksdb/_rocksdb.o -std=c++11 -O3 -Wall -Wextra -Wconversion -fno-strict-aliasing -fno-rtti rocksdb/_rocksdb.cpp:733:10: fatal error: rocksdb/utilities/backupable_db.h: No such file or directory 733 | #include "rocksdb/utilities/backupable_db.h" | ^~~ compilation terminated. Indeed, that header is no longer present in the RocksDB source. Please inform your upstream and see if they can update their code soon. Regards, Laszlo/GCS
Bug#1012073: perl: restoring default signal handler may warn with 'SIGTERM handler "DEFAULT" not defined'
Package: perl
Version: 5.34.0-4
Severity: normal
Control: block 923829 by -1
Hi,
While infestigating a random FTBFS in starlet (#923829), it appeared to me that
the problem is actually in perl. To reproduce te issue, t/12bad_request_line.t
needs to be run in a loop with the following change:
(starlet packaging repo is at
ssh://g...@salsa.debian.org/perl-team/modules/packages/starlet.git)
---
diff --git a/t/12bad_request_line.t b/t/12bad_request_line.t
index 61b4e7b..bdc8368 100644
--- a/t/12bad_request_line.t
+++ b/t/12bad_request_line.t
@@ -22,7 +22,7 @@ test_tcp(
my $port = shift;
local $SIG{__WARN__} = sub {
ok 0, "No warnings";
-diag @_;
+diag Carp::longmess(@_);
};
my $loader = Plack::Loader->load('Starlet', port => $port);
$loader->run(sub { [200, ['Content-Type' => 'text/plain'], ['OK']] });
---
A sample loop is this:
while prove -l t/12bad_request_line.t; do date; done
Running this simultaneously in several terminals may help triggering the
failure.
Eventually it fails with:
# Failed test 'No warnings'
# at t/12bad_request_line.t line 24.
# SIGTERM handler "DEFAULT" not defined.
# at /usr/share/perl5/Parallel/Prefork.pm line 71.
# Parallel::Prefork::start(Parallel::Prefork=HASH(0x55cd856355b8)) called
at .../lib/Plack/Handler/Starlet.pm line 78
#
Plack::Handler::Starlet::run(Plack::Handler::Starlet=HASH(0x55cd849b0ad8),
CODE(0x55cd8562ac98)) called at t/12bad_request_line.t line 28
# main::__ANON__(33415) called at /usr/share/perl5/Test/TCP.pm line 100
# Test::TCP::start(Test::TCP=HASH(0x55cd8562aed8)) called at
/usr/share/perl5/Test/TCP.pm line 82
# Test::TCP::new("Test::TCP", "code", CODE(0x55cd8562aab8)) called at
/usr/share/perl5/Test/TCP.pm line 28
# Test::TCP::test_tcp("client", CODE(0x55cd854306b0), "server",
CODE(0x55cd8562aab8)) called at t/12bad_request_line.t line 31
# Looks like you failed 1 test of 2.
t/12bad_request_line.t .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/2 subtests
The lines in Parallel::Prefork where the warning comes from are:
https://salsa.debian.org/perl-team/modules/packages/libparallel-prefork-perl/-/blob/master/lib/Parallel/Prefork.pm#L71
...
68 unless ($pid) {
69 # child process
70 $self->{in_child} = 1;
71 $SIG{$_} = 'DEFAULT' for keys %{$self->trap_signals};
72 $SIG{CHLD} = 'DEFAULT'; # revert to original
73 exit 0 if $self->signal_received;
...
Seems perfectly normal to me - signal handlers are reset in the forked child.
The only plausible source I find is line 3522 of mg.c:
https://salsa.debian.org/perl-team/interpreter/perl/-/blob/debian-5.34/mg.c#L3522
and here my idea of what is going on vanishes. I hope this is enough as a clue.
-- Damyan
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'),
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.17.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages perl depends on:
ii dpkg 1.21.8
ii libperl5.345.34.0-4
ii perl-base 5.34.0-4
ii perl-modules-5.34 5.34.0-4
Versions of packages perl recommends:
ii netbase 6.3
Versions of packages perl suggests:
pn libtap-harness-archive-perl
ii libterm-readline-gnu-perl1.42-2+b1
ii libterm-readline-perl-perl 1.0303-2.1
ii make 4.3-4.1
ii perl-doc 5.34.0-4
-- no debconf information
Bug#977792: closed by Debian FTP Masters
found 977792 16.15.0+dfsg-1 thanks On Fri, 2022-05-27 at 14:54 +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the nodejs package: > > #977792: nodejs: install bash-completion script > > It has been closed by Debian FTP Masters > (reply to Jérémy Lal ). Thanks for working on this issue! Unfortunately, it does not appear to be fixed in 16.15.0+dfsg-1, as the /usr/share/bash-completion/completions directory is empty in this version: $ dget nodejs=16.15.0+dfsg-1 $ dpkg -c nodejs_16.15.0+dfsg-1_amd64.deb | grep bash-completion drwxr-xr-x root/root 0 2022-05-27 07:48 ./usr/share/bash-completion/ drwxr-xr-x root/root 0 2022-05-27 07:48 ./usr/share/bash-completion/completions/ The buildd log for amd64[1] includes: /bin/sh: 1: ./node: not found in debian/rules override_dh_auto_build-arch on line 1443. Which appears be the source of the problem. Apparently the error is not fatal because it occurs in a variable substitution? Was that intentional? Perhaps it could be fixed and made fatal with: --- a/debian/rules +++ b/debian/rules @@ -257,7 +257,7 @@ endif override_dh_auto_build-arch: deps_build dh_auto_build - $(shell ./node --completion-bash > ./debian/nodejs.bash-completion) + ./out/Release/node --completion-bash > ./debian/nodejs.bash-completion override_dh_auto_build-indep: deps_links mkdir -p $(DEBIAN_DOC_DEPS) It may also be worth considering adding nodejs.links with content: /usr/share/bash-completion/completions/node /usr/share/bash-completion/completions/nodejs So that users will get completion for `node ` in addition to `nodejs `. Thanks again, Kevin [1]: https://buildd.debian.org/status/fetch.php?pkg=nodejs&arch=amd64&ver=16.15.0%2Bdfsg-1&stamp=1653680475&raw=0
Bug#977792: closed by Debian FTP Masters
Le dim. 29 mai 2022 à 19:18, Kevin Locke a écrit : > found 977792 16.15.0+dfsg-1 > thanks > > On Fri, 2022-05-27 at 14:54 +, Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > > which was filed against the nodejs package: > > > > #977792: nodejs: install bash-completion script > > > > It has been closed by Debian FTP Masters < > ftpmas...@ftp-master.debian.org> (reply to Jérémy Lal >). > > Thanks for working on this issue! Unfortunately, it does not appear > to be fixed in 16.15.0+dfsg-1, as the > /usr/share/bash-completion/completions directory is empty in this > version: > > $ dget nodejs=16.15.0+dfsg-1 > $ dpkg -c nodejs_16.15.0+dfsg-1_amd64.deb | grep bash-completion > drwxr-xr-x root/root 0 2022-05-27 07:48 > ./usr/share/bash-completion/ > drwxr-xr-x root/root 0 2022-05-27 07:48 > ./usr/share/bash-completion/completions/ > > The buildd log for amd64[1] includes: > > /bin/sh: 1: ./node: not found > > in debian/rules override_dh_auto_build-arch on line 1443. Which > appears be the source of the problem. Apparently the error is not > fatal because it occurs in a variable substitution? Was that > intentional? Perhaps it could be fixed and made fatal with: > > --- a/debian/rules > +++ b/debian/rules > @@ -257,7 +257,7 @@ endif > > override_dh_auto_build-arch: deps_build > dh_auto_build > - $(shell ./node --completion-bash > ./debian/nodejs.bash-completion) > + ./out/Release/node --completion-bash > > ./debian/nodejs.bash-completion > > override_dh_auto_build-indep: deps_links > mkdir -p $(DEBIAN_DOC_DEPS) > > > It may also be worth considering adding nodejs.links with content: > /usr/share/bash-completion/completions/node > /usr/share/bash-completion/completions/nodejs > So that users will get completion for `node ` in addition to > `nodejs `. > Well, exactly ! And thank you ! The next update will fix this. Jérémy
Bug#1012071: igv: FTBFS with OpenJDK 17 due to removed java.net.URLDecoder public constructor
Source: igv
Version: 2.12.3+dfsg-1
Severity: important
Tags: ftbfs sid bookworm
User: debian-j...@lists.debian.org
Usertags: default-java17
igv fails to build with OpenJDK 17, it invokes the constructor of
java.net.URLDecoder
that was made private:
/<>/src/main/java/org/broad/igv/google/OAuthProvider.java:202:
error: URLDecoder() has private access in URLDecoder
params.put("redirect_uri", new URLDecoder().decode(redirect,
"utf-8"));
^
The decode() method is static and can be invoked directly without instantiating
the class.
Bug#1012070: simple-xml: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests
Source: simple-xml Version: 2.7.1-3 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 simple-xml fails to build with OpenJDK 17 due to a test failure. The cause isn't explicit in the log, but the JUnit report (report/TEST-org.simpleframework.xml.core.MixTest.txt) leads to an illegal reflective access: Testsuite: org.simpleframework.xml.core.MixTest Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.067 sec Testcase: testMix took 0.061 sec Caused an ERROR Unable to make field protected int[] java.util.Calendar.fields accessible: module java.base does not "opens java.util" to unnamed module @4cfaf581 java.lang.reflect.InaccessibleObjectException: Unable to make field protected int[] java.util.Calendar.fields accessible: module java.base does not "opens java.util" to unnamed module @4cfaf581 at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354) at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297) at java.base/java.lang.reflect.Field.checkCanSetAccessible(Field.java:178) at java.base/java.lang.reflect.Field.setAccessible(Field.java:172) at org.simpleframework.xml.core.FieldScanner.process(FieldScanner.java:247) at org.simpleframework.xml.core.FieldScanner.process(FieldScanner.java:228) at org.simpleframework.xml.core.FieldScanner.extract(FieldScanner.java:161) at org.simpleframework.xml.core.FieldScanner.scan(FieldScanner.java:99) at org.simpleframework.xml.core.FieldScanner.(FieldScanner.java:80) at org.simpleframework.xml.core.DetailExtractor.getFields(DetailExtractor.java:147) at org.simpleframework.xml.core.DetailExtractor.getFields(DetailExtractor.java:130) at org.simpleframework.xml.core.Support.getFields(Support.java:308) at org.simpleframework.xml.core.ObjectScanner.field(ObjectScanner.java:432) at org.simpleframework.xml.core.ObjectScanner.scan(ObjectScanner.java:371) at org.simpleframework.xml.core.ObjectScanner.(ObjectScanner.java:82) at org.simpleframework.xml.core.DefaultScanner.(DefaultScanner.java:64) at org.simpleframework.xml.core.ScannerFactory.getInstance(ScannerFactory.java:84) at org.simpleframework.xml.core.Support.getScanner(Support.java:357) at org.simpleframework.xml.core.Source.getScanner(Source.java:271) at org.simpleframework.xml.core.Source.getDecorator(Source.java:286) at org.simpleframework.xml.core.Composite.writeNamespaces(Composite.java:1272) at org.simpleframework.xml.core.Composite.writeElement(Composite.java:1232) at org.simpleframework.xml.core.Composite.writeUnion(Composite.java:1127) at org.simpleframework.xml.core.Composite.writeElements(Composite.java:1098) at org.simpleframework.xml.core.Composite.writeSection(Composite.java:1004) at org.simpleframework.xml.core.Composite.write(Composite.java:975) at org.simpleframework.xml.core.Composite.write(Composite.java:952) at org.simpleframework.xml.core.Traverser.write(Traverser.java:236) at org.simpleframework.xml.core.Traverser.write(Traverser.java:208) at org.simpleframework.xml.core.Traverser.write(Traverser.java:186) at org.simpleframework.xml.core.Persister.write(Persister.java:1180) at org.simpleframework.xml.core.Persister.write(Persister.java:1162) at org.simpleframework.xml.core.Persister.write(Persister.java:1140) at org.simpleframework.xml.core.Persister.write(Persister.java:1259) at org.simpleframework.xml.core.Persister.write(Persister.java:1241) at org.simpleframework.xml.core.Persister.write(Persister.java:1222) at org.simpleframework.xml.core.MixTest.testMix(MixTest.java:87) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Bug#1001603: rpmlint: diff for NMU version 2.3.0+ds1-0.1
Control: tags 1001603 + patch Control: tags 1001603 + pending Dear maintainer, I've prepared an NMU for rpmlint (versioned as 2.3.0+ds1-0.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards. diff -Nru rpmlint-2.2.0+ds1/configs/Fedora/users-groups.toml rpmlint- 2.3.0+ds1/configs/Fedora/users-groups.toml --- rpmlint-2.2.0+ds1/configs/Fedora/users-groups.toml 2021-12-12 09:54:14.0 -0500 +++ rpmlint-2.3.0+ds1/configs/Fedora/users-groups.toml 2022-05-29 12:46:55.0 -0400 @@ -1,5 +1,5 @@ # generated using tools/generate-fedora-users-groups.py on 2021-03-23 -StandardUsers = ['pkiuser', 'sshd', 'cyrus', 'keystone', 'squid', 'lp', 'root', 'dovecot', 'oprofile', 'ldap', 'arpwatch', 'retrace', 'vdsm', 'nut', 'hacluster', 'polkituser', 'mailman', 'saned', 'adm', 'mailnull', 'rtkit', 'postfix', 'cimsrvr', 'postgres', 'vhostmd', 'smmsp', 'dbus', 'rpcuser', 'nslcd', 'named', 'radvd', 'ntp', 'systemd-resolve', 'nova', 'tss', 'wildfly', 'ricci', 'mysql', 'apache', 'usbmuxd', 'systemd-network', 'vcsa', 'sabayon', 'quantum', 'katello', 'xfs', 'halt', 'tomcat', 'beagleindex', 'jbosson-agent', 'fax', 'haldaemon', 'pulse', 'hsqldb', 'cassandra', 'pegasus', 'clamav', 'piranha', 'mongodb', 'netdump', 'activemq', 'ovirtagent', 'bin', 'aeolus', 'sync', 'radiusd', 'rpm', 'webalizer', 'nocpulse', 'elasticsearch', 'games', 'pvm', 'wnn', 'snortd', 'privoxy', 'nscd', 'gdm', 'prelude-manager', 'cinder', 'shutdown', 'rpc', 'condor', '#systemd-journal-gateway', 'heat', 'qemu', 'myproxy', 'avahi', 'operator', 'majordomo', 'puppet', 'exim', 'sanlock', 'rhevm', 'swift', 'wallaby', 'ftp', 'ident', 'frontpage', 'ats', 'mail', 'ceilometer', 'news', 'distcache', 'ovirt', 'ceph', 'desktop', 'uucp', 'glance', 'jonas', 'haproxy', 'abrt', 'quagga', 'stap-server', 'dhcpd', 'nobody', 'luci', 'bacula', 'avahi-autoipd', 'gopher', 'tcpdump', 'daemon', 'amandabackup', 'jetty'] +StandardUsers = ['pkiuser', 'sshd', 'cyrus', 'keystone', 'squid', 'lp', 'root', 'dovecot', 'oprofile', 'ldap', 'arpwatch', 'retrace', 'vdsm', 'nut', 'hacluster', 'polkituser', 'mailman', 'saned', 'adm', 'mailnull', 'rtkit', 'postfix', 'cimsrvr', 'postgres', 'vhostmd', 'smmsp', 'dbus', 'rpcuser', 'nslcd', 'named', 'radvd', 'ntp', 'systemd-resolve', 'nova', 'tss', 'wildfly', 'ricci', 'mysql', 'apache', 'usbmuxd', 'systemd-network', 'vcsa', 'sabayon', 'quantum', 'katello', 'xfs', 'halt', 'tomcat', 'beagleindex', 'jbosson-agent', 'fax', 'haldaemon', 'pulse', 'hsqldb', 'cassandra', 'pegasus', 'clamav', 'piranha', 'mongodb', 'netdump', 'activemq', 'ovirtagent', 'bin', 'aeolus', 'sync', 'radiusd', 'rpm', 'webalizer', 'nocpulse', 'elasticsearch', 'games', 'pvm', 'wnn', 'snortd', 'privoxy', 'nscd', 'gdm', 'prelude-manager', 'cinder', 'shutdown', 'rpc', 'condor', '#systemd-journal-gateway', 'heat', 'qemu', 'myproxy', 'avahi', 'operator', 'majordomo', 'puppet', 'exim', 'sanlock', 'rhevm', 'swift', 'wallaby', 'ftp', 'ident', 'frontpage', 'ats', 'mail', 'ceilometer', 'news', 'distcache', 'ovirt', 'ceph', 'desktop', 'uucp', 'glance', 'jonas', 'haproxy', 'abrt', 'quagga', 'stap-server', 'dhcpd', 'nobody', 'luci', 'bacula', 'avahi-autoipd', 'gopher', 'tcpdump', 'daemon', 'amandabackup', 'jetty', 'ergo'] -StandardGroups = ['pkiuser', 'sshd', 'keystone', 'squid', 'pppusers', 'kvm', 'popusers', 'lp', 'root', 'dovecot', 'oprofile', 'disk', 'ldap', 'arpwatch', 'retrace', 'nut', 'polkituser', 'audio', 'mailman', 'stapusr', 'saned', 'adm', 'mailnull', 'rtkit', 'postfix', 'utmp', 'cimsrvr', 'wheel', 'postgres', 'vhostmd', 'smmsp', 'realtime', 'kmem', 'rpcuser', 'dbus', 'screen', 'utempter', 'video', 'named', 'radvd', 'ntp', 'man', 'systemd- resolve', 'nova', 'tss', 'sys', 'cdrom', 'wildfly', 'ricci', 'mysql', 'apache', 'usbmuxd', 'jbosson', 'systemd-network', 'vcsa', 'console', 'sabayon', 'quantum', 'katello', 'haclient', 'xfs', 'tomcat', 'beagleindex', 'fax', 'haldaemon', 'systemd-journal', 'pulse', 'hsqldb', 'cassandra', 'pegasus', 'clamav', 'piranha', 'mongodb', 'netdump', 'activemq', 'ovirtagent', 'bin', 'saslauth', 'aeolus', 'radiusd', 'mem', 'rpm', 'webalizer', 'floppy', 'nocpulse', 'elasticsearch', 'games', 'pvm', 'wnn', 'tty', 'snortd', 'slipusers', 'nscd', 'gdm', 'privoxy', 'mock', 'prelude- manager', 'cinder', 'dialout', 'rpc', 'condor', '#systemd-journal-gateway', 'heat', 'qemu', 'stapsys', 'avahi', 'myproxy', 'majordomo', 'tape', 'puppet', 'exim', 'sanlock', 'rhevm', 'swift', 'wallaby', 'ftp', 'ident', 'frontpage', 'ats', 'mail', 'ceilometer', 'news', 'distcache', 'stapdev', 'users', 'ovirt', 'ceph', 'desktop', 'uucp', 'glance', 'jonas', 'postdrop', 'haproxy', 'abrt', 'quagga', 'stap-server', 'lock', 'dhcpd', 'nobody', 'wbpriv', 'luci', 'quaggavt', 'bacula', 'avahi-autoipd', 'gopher', 'wine', 'tcpdump', 'dip', 'daemon', 'slocate', 'jetty'] +StandardGroups = ['pkiuser', 'sshd', 'keystone', 'squid', 'pppusers', 'kvm', 'popusers', 'lp', 'root', 'dovecot', 'oprofile', 'disk', 'ldap', 'arpwatch', 'retrace', 'nut', 'polkituser',
Bug#1012069: simgrid: FTBFS with OpenJDK 17 due to javadoc errors
Source: simgrid Version: 3.30+dfsg-1 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 simgrid fails to build with OpenJDK 17 due to javadoc errors: /<>/src/bindings/java/org/simgrid/msg/ProcessKilledError.java:10: error: unknown tag: beginrst * @beginrst ^ /<>/src/bindings/java/org/simgrid/msg/ProcessKilledError.java:22: error: unknown tag: endrst * @endrst ^
Bug#1012068: classmate: FTBFS with OpenJDK 17 due to test failures
Source: classmate Version: 1.3.4-1.1 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 classmate fails to build with OpenJDK 17, several tests fail: [INFO] --- [INFO] T E S T S [INFO] --- [INFO] Running com.fasterxml.classmate.TestSubtypeResolution [INFO] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.036 s - in com.fasterxml.classmate.TestSubtypeResolution [INFO] Running com.fasterxml.classmate.TestMemberGenericTypes [INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 s - in com.fasterxml.classmate.TestMemberGenericTypes [INFO] Running com.fasterxml.classmate.ResolvedTypeTest [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 s - in com.fasterxml.classmate.ResolvedTypeTest [INFO] Running com.fasterxml.classmate.TestSelfRefMemberTypes [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 s - in com.fasterxml.classmate.TestSelfRefMemberTypes [INFO] Running com.fasterxml.classmate.OddJDKTypesTest [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s - in com.fasterxml.classmate.OddJDKTypesTest [INFO] Running com.fasterxml.classmate.StdConfigurationTest [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.019 s - in com.fasterxml.classmate.StdConfigurationTest [INFO] Running com.fasterxml.classmate.TestReadme [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 s - in com.fasterxml.classmate.TestReadme [INFO] Running com.fasterxml.classmate.TestTypeResolver [INFO] Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 s - in com.fasterxml.classmate.TestTypeResolver [INFO] Running com.fasterxml.classmate.AnnotationsTest [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s - in com.fasterxml.classmate.AnnotationsTest [INFO] Running com.fasterxml.classmate.types.ResolvedPrimitiveTypeTest [INFO] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 s - in com.fasterxml.classmate.types.ResolvedPrimitiveTypeTest [INFO] Running com.fasterxml.classmate.types.ResolvedObjectTypeTest [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.002 s <<< FAILURE! - in com.fasterxml.classmate.types.ResolvedObjectTypeTest [ERROR] testGetStaticFields(com.fasterxml.classmate.types.ResolvedObjectTypeTest) Time elapsed: 0.002 s <<< FAILURE! junit.framework.AssertionFailedError: Expected 3 (JDK 1.6), 4 (1.7/1.8) or 6 (1.9) static fields, got 7; fields: [serialVersionUID, COMPACT_STRINGS, serialPersistentFields, REPL, CASE_INSENSITIVE_ORDER, LATIN1, UTF16] at com.fasterxml.classmate.types.ResolvedObjectTypeTest.testGetStaticFields(ResolvedObjectTypeTest.java:81) [INFO] Running com.fasterxml.classmate.types.ResolvedInterfaceTypeTest [INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in com.fasterxml.classmate.types.ResolvedInterfaceTypeTest [INFO] Running com.fasterxml.classmate.types.ResolvedRecursiveTypeTest [INFO] Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 s - in com.fasterxml.classmate.types.ResolvedRecursiveTypeTest [INFO] Running com.fasterxml.classmate.types.TypePlaceHolderTest [INFO] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s - in com.fasterxml.classmate.types.TypePlaceHolderTest [INFO] Running com.fasterxml.classmate.types.ResolvedArrayTypeTest [INFO] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s - in com.fasterxml.classmate.types.ResolvedArrayTypeTest [INFO] Running com.fasterxml.classmate.TypeBindingsTest [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in com.fasterxml.classmate.TypeBindingsTest [INFO] Running com.fasterxml.classmate.TestParameterAnnotations [INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 s - in com.fasterxml.classmate.TestParameterAnnotations [INFO] Running com.fasterxml.classmate.TestMemberResolver [ERROR] Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.004 s <<< FAILURE! - in com.fasterxml.classmate.TestMemberResolver [ERROR] testAddOverridesFromInterfaces(com.fasterxml.classmate.TestMemberResolver) Time elapsed: 0.001 s <<< FAILURE! junit.framework.AssertionFailedError: expected:<4> but was:<6> at com.fasterxml.classmate.TestMemberResolver.testAddOverridesFromInterfaces(TestMemberResolver.java:292) [INFO] Running com.fasterxml.classmate.ResolvedTypeWithMembersTest [INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 s - in com.fasterxml.classmate.ResolvedTypeWithMembersTest [INFO] Running com.fasterxml.classmate.TestTypeDescriptions [ERROR] Tests run:
Bug#1012067: jss: FTBFS with OpenJDK 17: no such provider SunJSSE
Source: jss Version: 5.1.0-1 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 jss fails to build with OpenJDK 17, there is an error during the tests (because libfakeroot-sysv.so can't be loaded?) cd build && ctest --output-on-failure Test project /<>/build Start 1: Clean_Data_Dir 1/75 Test #1: Clean_Data_Dir Passed 0.01 sec Start 2: Create_Data_Dir 2/75 Test #2: Create_Data_Dir ... Passed 0.01 sec Start 3: Clean_Setup_DBs 3/75 Test #3: Clean_Setup_DBs ... Passed 0.01 sec Start 4: Create_Setup_DBs 4/75 Test #4: Create_Setup_DBs .. Passed 0.01 sec Start 5: Setup_DBs 5/75 Test #5: Setup_DBs . Passed 0.18 sec Start 6: Clean_FIPS_Setup_DBs 6/75 Test #6: Clean_FIPS_Setup_DBs .. Passed 0.01 sec Start 7: Create_FIPS_Setup_DBs 7/75 Test #7: Create_FIPS_Setup_DBs . Passed 0.01 sec Start 8: Setup_FIPS_DBs 8/75 Test #8: Setup_FIPS_DBs Passed 0.14 sec Start 9: TestBufferPRFD 9/75 Test #9: TestBufferPRFD Passed 0.00 sec Start 10: Test_UTF-8_Converter 10/75 Test #10: Test_UTF-8_Converter .. Passed 0.04 sec Start 11: Test_Base64_Parsing 11/75 Test #11: Test_Base64_Parsing ... Passed 0.03 sec Start 12: JSS_DER_Encoding_of_Enumeration_regression_test 12/75 Test #12: JSS_DER_Encoding_of_Enumeration_regression_test ... Passed 1.68 sec Start 13: JSS_Test_DER_Encoding_Functionality 13/75 Test #13: JSS_Test_DER_Encoding_Functionality ... Passed 0.07 sec Start 14: JSS_Test_Empty_DER_Value 14/75 Test #14: JSS_Test_Empty_DER_Value .. Passed 0.03 sec Start 15: BigObjectIdentifier 15/75 Test #15: BigObjectIdentifier ... Passed 0.05 sec Start 16: JSS_Test_PR_FileDesc 16/75 Test #16: JSS_Test_PR_FileDesc .. Passed 0.06 sec Start 17: JSS_Test_Raw_SSL 17/75 Test #17: JSS_Test_Raw_SSL .. Passed 0.08 sec Start 18: JSS_Test_Buffer 18/75 Test #18: JSS_Test_Buffer ... Passed 0.06 sec Start 19: JSS_Test_GlobalRefProxy 19/75 Test #19: JSS_Test_GlobalRefProxy ... Passed 5.07 sec Start 20: JUnit_BMPStringTest 20/75 Test #20: JUnit_BMPStringTest ... Passed 0.26 sec Start 21: JUnit_IA5StringTest 21/75 Test #21: JUnit_IA5StringTest ... Passed 0.21 sec Start 22: JUnit_PrintableStringTest 22/75 Test #22: JUnit_PrintableStringTest . Passed 0.26 sec Start 23: JUnit_TeletexStringTest 23/75 Test #23: JUnit_TeletexStringTest ... Passed 0.18 sec Start 24: JUnit_UniversalStringTest 24/75 Test #24: JUnit_UniversalStringTest . Passed 0.29 sec Start 25: JUnit_UTF8StringTest 25/75 Test #25: JUnit_UTF8StringTest .. Passed 0.27 sec Start 26: buffer_size_1 26/75 Test #26: buffer_size_1 . Passed 0.00 sec Start 27: buffer_size_4 27/75 Test #27: buffer_size_4 . Passed 0.00 sec Start 28: JUnit_CertificateChainTest 28/75 Test #28: JUnit_CertificateChainTest Passed 0.25 sec Start 29: JUnit_ChainSortingTest 29/75 Test #29: JUnit_ChainSortingTest Passed 0.24 sec Start 30: Generate_known_RSA_cert_pair 30/75 Test #30: Generate_known_RSA_cert_pair .. Passed 3.87 sec Start 31: Generate_known_ECDSA_cert_pair 31/75 Test #31: Generate_known_ECDSA_cert_pair Passed 0.48 sec Start 32: Create_PKCS11_cert_to_PKCS12_rsa.pfx 32/75 Test #32: Create_PKCS11_cert_to_PKCS12_rsa.pfx .. Passed 1.80 sec Start 33: Create_PKCS11_cert_to_PKCS12_ecdsa.pfx 33/75 Test #33: Create_PKCS11_cert_to_PKCS12_ecdsa.pfx Passed 1.51 sec Start 34: List_CA_certs 34/75 Test #34: List_CA_certs . Passed 0.15 sec Start 35: SSLClientAuth 35/75 Test #35: SSLClientAuth . Passed 5.24 sec Start 36: Key_Generation 36/75 Test #36: K
Bug#1012066: buster-pu: package wireshark/2.6.20-0+deb10u3
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu X-Debbugs-Cc: a...@debian.org Hi, I would like to update and sync the version of wireshark in Buster. It is identical to the version in Stretch. Multiple CVE have been fixed. They are not severe enough for a DSA but still important enough to be addressed via a point-update. Please find attached the debdiff. All tests pass. Regards, Markus [ Checklist ] [x] *all* changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in (old)stable [x] the issue is verified as fixed in unstable wireshark.debdiff.gz Description: application/gzip
Bug#1010340: (no subject)
Apparently setting the GNUTLS_CPUID_OVERRIDE variable helps to work around the error. For more details please refer to this page. https://gnutls.org/manual/html_node/Debugging-and-auditing.html The error doesn't appear anymore when setting the GNUTLS_CPUID_OVERRIDE. GNUTLS_CPUID_OVERRIDE=0x1 git clone https://... With QEMU 7.0 and apt-get update the same error is also triggered, since also GnuTLS is used. sudo GNUTLS_CPUID_OVERRIDE=0x1 apt-get update So this is not really a bug in git, but a bug in GnuTLS when running QEMU with Windows as host (with Hyper-V acceleration hax or whpx). Best, Sascha On Sun, 29 May 2022 13:19:42 +0200 Sascha Scandella wrote: > I have unfortunately had to make the same experiences. with the accelerator hax or whpx it leads to the same error with QEMU (tested v6.2.x and > v7.0.x). Using tcg as accelerator is not an alternative, because it is extremely slow. > > What I could find out so far is that it leads to an error with Ubuntu 20.04 LTS and 22.04 LTS. Also when updating git. Strangely, the error does not > appear with Ubuntu 21.04. Therefore, I recently thought to repeat the test with Ubuntu 22.04 LTS where I unfortunately found that the same error occurs. > > What helps is compiling git with OpenSSL instead of GnuTLS (which is standard with git). > > See also https://github.com/paul-nelson-baker/git-openssl-shellscript. > > How could I get to the root cause of the error? > > Regards, > Sascha > > >
Bug#1012064: libsweble-common-java: FTBFS with OpenJDK 17: illegal escape character
Source: libsweble-common-java Version: 3.0.8-2 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 libsweble-common-java fails to build with OpenJDK 17, it looks like the range of valid unicode escape sequences is more restricted with Java 17: [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] Utils Parent POM [pom] [INFO] Utils [jar] [INFO] Parser Toolkit Parent POM [pom] [INFO] PTK - Common [jar] [INFO] Open Source Research Common Aggergator Project [pom] [INFO] [INFO] --< de.fau.cs.osr.utils:utils-parent >-- [INFO] Building Utils Parent POM 3.0.8 [1/5] [INFO] [ pom ]- [INFO] [INFO] -< de.fau.cs.osr.utils:utils >-- [INFO] Building Utils 3.0.8 [2/5] [INFO] [ jar ]- [INFO] [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ utils --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /<>/utils-parent/utils/src/main/resources [INFO] [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ utils --- [INFO] Changes detected - recompiling the module! [INFO] Compiling 46 source files to /<>/utils-parent/utils/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /<>/utils-parent/utils/src/main/java/de/fau/cs/osr/utils/XmlGrammar.java:[41,51] illegal escape character [INFO] 1 error [INFO] - [INFO] [INFO] Reactor Summary for Open Source Research Common Aggergator Project 3.0.8: [INFO] [INFO] Utils Parent POM ... SUCCESS [ 0.003 s] [INFO] Utils .. FAILURE [ 0.490 s] [INFO] Parser Toolkit Parent POM .. SKIPPED [INFO] PTK - Common ... SKIPPED [INFO] Open Source Research Common Aggergator Project . SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.560 s [INFO] Finished at: 2022-05-25T00:35:53Z [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project utils: Compilation failure [ERROR] /<>/utils-parent/utils/src/main/java/de/fau/cs/osr/utils/XmlGrammar.java:[41,51] illegal escape character [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :utils
Bug#1011426: bullseye-pu: package tcpdump/4.99.0-2+deb11u1
Hi Adam, On Sat, May 28, 2022 at 8:51 PM Adam D. Barratt wrote: > Please go ahead, thanks. Uploaded. Thanks!
Bug#1012063: cofoja: FTBFS with OpenJDK 17: module jdk.compiler does not export com.sun.tools.javac.processing to unnamed module
Source: cofoja Version: 1.3-4 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 cofoja fails to build with OpenJDK 17: dh_auto_build -- dist -Dcofoja.bare.jar=dist/cofoja.jar ant -Duser.name debian dist -Dcofoja.bare.jar=dist/cofoja.jar Buildfile: /<>/build.xml configure: [echo] Configuration [echo] - [echo] Snapshot: true [echo] Debug: true init: [tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been set to 1543526457 [mkdir] Created dir: /<>/obj [mkdir] Created dir: /<>/dist build: [mkdir] Created dir: /<>/obj/bare [ujavac] Compiling 86 source files to /<>/obj/bare [ujavac] Note: Some input files use or override a deprecated API. [ujavac] Note: Recompile with -Xlint:deprecation for details. [ujavac] Note: /<>/src/com/google/java/contract/util/Predicates.java uses unchecked or unsafe operations. [ujavac] Note: Recompile with -Xlint:unchecked for details. nobootstrap: [jar] Building jar: /<>/dist/cofoja.jar [jar] Building jar: /<>/dist/cofoja+asm-1.2-19700119.jar antinit: [mkdir] Created dir: /<>/obj/build [ujavac] Compiling 1 source file to /<>/obj/build [ujavac] [ujavac] [ujavac] An annotation processor threw an uncaught exception. [ujavac] Consult the following stack trace for details. [ujavac] java.lang.LinkageError: class com.google.java.contract.core.apt.AnnotationProcessor cannot access class com.sun.tools.javac.processing.JavacProcessingEnvironment (in module jdk.compiler) because module jdk.compiler does not export com.sun.tools.javac.processing to unnamed module @f4c0e4e [ujavac] at com.google.java.contract.core.apt.AnnotationProcessor.getJavacOptions(AnnotationProcessor.java:181) [ujavac] at com.google.java.contract.core.apt.AnnotationProcessor.setupPaths(AnnotationProcessor.java:268) [ujavac] at com.google.java.contract.core.apt.AnnotationProcessor.init(AnnotationProcessor.java:201) [ujavac] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$ProcessorState.(JavacProcessingEnvironment.java:701) [ujavac] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$DiscoveredProcessors$ProcessorStateIterator.next(JavacProcessingEnvironment.java:828) [ujavac] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:924) [ujavac] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1267) [ujavac] at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1382) [ujavac] at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1234) [ujavac] at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:916) [ujavac] at jdk.compiler/com.sun.tools.javac.main.Main.compile(Main.java:317) [ujavac] at jdk.compiler/com.sun.tools.javac.main.Main.compile(Main.java:176) [ujavac] at jdk.compiler/com.sun.tools.javac.Main.compile(Main.java:64) [ujavac] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [ujavac] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) [ujavac] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [ujavac] at java.base/java.lang.reflect.Method.invoke(Method.java:568) [ujavac] at org.apache.tools.ant.taskdefs.compilers.Javac13.execute(Javac13.java:57) [ujavac] at org.apache.tools.ant.taskdefs.Javac.compile(Javac.java:1352) [ujavac] at org.apache.tools.ant.taskdefs.Javac.execute(Javac.java:1092) [ujavac] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:299) [ujavac] at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) [ujavac] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [ujavac] at java.base/java.lang.reflect.Method.invoke(Method.java:568) [ujavac] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) [ujavac] at org.apache.tools.ant.Task.perform(Task.java:350) [ujavac] at org.apache.tools.ant.Target.execute(Target.java:449) [ujavac] at org.apache.tools.ant.Target.performTasks(Target.java:470) [ujavac] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1401) [ujavac] at org.apache.tools.ant.Project.executeTarget(Project.java:1374) [ujavac] at org.apache.tools.ant.helper.Defaul
Bug#1009733: src:exempi: fails to migrate to testing for too long: FTBFS on armel and armhf
Hi, On Sat, 16 Apr 2022 00:21:46 +0200 Michael Biebl wrote: Dear arm porters, > can you please take a look at this? Ping from the Release Team. This package is a key package (so the RC bug can't be "fixed" by removal from testing). Am 15.04.22 um 21:19 schrieb Paul Gevers: > Source: exempi > Version: 2.5.2-1 > Severity: serious > Control: close -1 2.6.1-1 > Tags: sid bookworm ftbfs > User: release.debian@packages.debian.org > Usertags: out-of-sync > > Dear maintainer(s), > > The Release Team considers packages that are out-of-sync between testing > and unstable for more than 60 days as having a Release Critical bug in > testing [1]. Your package src:exempi has been trying to migrate for 61 > days [2]. Hence, I am filing this bug. You package failed to build from > source on armel and armhf where it built successfully in the past. > > If a package is out of sync between unstable and testing for a longer > period, this usually means that bugs in the package in testing cannot be > fixed via unstable. Additionally, blocked packages can have impact on > other packages, which makes preparing for the release more difficult. > Finally, it often exposes issues with the package and/or > its (reverse-)dependencies. We expect maintainers to fix issues that > hamper the migration of their package in a timely manner. > > This bug will trigger auto-removal when appropriate. As with all new > bugs, there will be at least 30 days before the package is auto-removed. > > 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. I have also tagged this bug to only affect sid and bookworm, so > it doesn't affect (old-)stable. > > If you believe your package is unable to migrate to testing due to > issues beyond your control, don't hesitate to contact the Release Team. > > Paul > > [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html > [2] https://qa.debian.org/excuses.php?package=exempi Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1012062: gant: FTBFS with OpenJDK 17 due to unsupported javac source/target level 6
Source: gant Version: 1.9.11-8 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 gant fails to build with OpenJDK 17 because it invokes javac with the source/target options set to 6. Since OpenJDK 12 the minimum version supported is 7.
Bug#1012061: coq breaks coquelicot autopkgtest: Compiled library Coquelicot.Rcomplements makes inconsistent assumptions over library Coq.Init.Ltac
Source: coq, coquelicot Control: found -1 coq/8.15.1+dfsg-2 Control: found -1 coquelicot/3.2.0-2 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of coq the autopkgtest of coquelicot fails in testing when that autopkgtest is run with the binary packages of coq from unstable. It passes when run with only packages from testing. In tabular form: passfail coqfrom testing8.15.1+dfsg-2 coquelicot from testing3.2.0-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 of coq to testing [1]. 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 [1] https://qa.debian.org/excuses.php?package=coq https://ci.debian.net/data/autopkgtest/testing/amd64/c/coquelicot/22188156/log.gz File "./BacS2013.v", line 24, characters 0-112: Error: Compiled library Coquelicot.Rcomplements (in file /usr/lib/ocaml/coq/user-contrib/Coquelicot/Rcomplements.vo) makes inconsistent assumptions over library Coq.Init.Ltac autopkgtest [11:12:10]: test examples OpenPGP_signature Description: OpenPGP digital signature
Bug#1012060: coq breaks coq-bignums autopkgtest: Compiled library Bignums.BigN.BigN makes inconsistent assumptions over library Coq.Init.Ltac
Source: coq, coq-bignums Control: found -1 coq/8.15.1+dfsg-2 Control: found -1 coq-bignums/8.15.0-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of coq the autopkgtest of coq-bignums fails in testing when that autopkgtest is run with the binary packages of coq from unstable. It passes when run with only packages from testing. In tabular form: passfail coqfrom testing8.15.1+dfsg-2 coq-bignumsfrom testing8.15.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of coq to testing [1]. 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 [1] https://qa.debian.org/excuses.php?package=coq https://ci.debian.net/data/autopkgtest/testing/amd64/c/coq-bignums/22188155/log.gz make: Entering directory '/tmp/autopkgtest-lxc.1xnd4upm/downtmp/build.b30/src/tests' coqc success/NumberScopes.v File "./success/NumberScopes.v", line 7, characters 0-33: Error: Compiled library Bignums.BigN.BigN (in file /usr/lib/ocaml/coq/user-contrib/Bignums/BigN/BigN.vo) makes inconsistent assumptions over library Coq.Init.Ltac make: *** [Makefile:10: success/NumberScopes.vo] Error 1 make: Leaving directory '/tmp/autopkgtest-lxc.1xnd4upm/downtmp/build.b30/src/tests' autopkgtest [11:12:08]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Bug#1012059: bind9: autopkgtest regression on amd64 and armhf: connection refused
Source: bind9 Version: 1:9.18.3-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of bind9 the autopkgtest of bind9 fails in testing on amd64 and armhf when that autopkgtest is run with the binary packages of bind9 from unstable. It passes when run with only packages from testing. In tabular form: passfail bind9 from testing1:9.18.3-1 versioned deps [0] from testingfrom unstable 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 [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 bind9/1:9.18.3-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=bind9 https://ci.debian.net/data/autopkgtest/testing/amd64/b/bind9/22188154/log.gz ;; communications error to 127.0.0.1#53: connection refused autopkgtest [11:11:37]: test simpletest OpenPGP_signature Description: OpenPGP digital signature
Bug#1012058: debhelper: riscv64 needs THREADS_PREFER_PTHREAD_FLAG in cmake for atomics-related ftbfs
Package: debhelper Version: 13.7.1 Severity: important X-Debbugs-Cc: debian-ri...@lists.debian.org Dear Maintainer, On riscv64, many FTBFS issues share a root cause, and I believe it would be appropriate to address it in debhelper. This architecture lacks hardware support for small atomics. These operations must be implemented in software instead of as instructions. The pthreads library includes this support, but needs to be linked with "-pthread", and not "-lpthread" to use this functionality. There is also currently a gcc bug related to this, with ongoing discussion on what to do long-term. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358 The following cmake directive causes the build process to prefer -pthread over -lpthread, and in this case, makes it possible to use small atomic operations on riscv64. set(THREADS_PREFER_PTHREAD_FLAG ON) Rather than applying a patch for this flag to every affected package individually, it seems more sensible to apply it through debhelper. If the architecture is riscv64, then the above cmake directive should be set. I think this could be added in lib/Debian/Debhelper/Buildsystem/cmake.pm Below I have gathered several relevant lists of packages. These lists are probably incomplete. Likely affected with no patch pending: fairy-stockfish leela-zero muse neochat rust-jemalloc-sys wsclean zynaddsubfx Affected with a patch pending: simgear https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011260 thinkfan https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011953 warzone2100 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011367 Affected with a patch applied: ceph https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953003 webkit2gtk https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895969 yoshimi https://sources.debian.org/src/yoshimi/2.2.0-2/debian/patches/fix_ftbfs_on_risc64.patch/ Affected with a patch applied, but does not use cmake: libzstd https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895259 Similar unfixed problem, but not currently using -lpthread (need to use -latomic): numactl opentracing-cpp tiledb-r Also, see here for existing occurrences of this cmake directive in Debian packages: https://codesearch.debian.net/search?q=THREADS_PREFER_PTHREAD_FLAG Special thanks to Bo YU for help in preparing this bug report. -Alan Beadle -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: riscv64 Kernel: Linux 5.18.0-starfive-5.18 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages debhelper depends on: ii autotools-dev20220109.1 ii dh-autoreconf20 ii dh-strip-nondeterminism 1.13.0-1 ii dpkg 1.21.8 ii dpkg-dev 1.21.8 ii dwz 0.14-1 ii file 1:5.41-4 ii libdebhelper-perl13.7.1 ii libdpkg-perl 1.21.8 ii man-db 2.10.2-1 ii perl 5.34.0-4 ii po-debconf 1.0.21+nmu1 debhelper recommends no packages. Versions of packages debhelper suggests: pn dh-make -- no debconf information
Bug#992269: texlive-bibtex-extra: Missing beebe bst stiles like abstract.bst
Am 16.08.2021 um 16:54 teilte Simone Piccardi mit: Hi, Compiling latex book that was using abstract.bst Bibtex style do not give references, due to its absence. It was there on buster. Its reported as present in: https://packages.debian.org/search?suite=bullseye&arch=any&mode=path&searchon=contents&keywords=abstract.bst but is not there. Not sure what your real issue is: the fact that the file is gone (I do not know yet, why it happened) or the fact that it is still listed on packages.debian.org? The latter should rather be reported to www.debian.org as the file is really gone. Hilmar -- sigfault OpenPGP_signature Description: OpenPGP digital signature
Bug#1011365: bullseye-pu: package nvidia-cuda-toolkit/11.2.2-3+deb11u2
On Fri, 2022-05-20 at 23:44 +0200, Andreas Beckmann wrote: > the nvidia-cuda-toolkit 11.2.2-3+deb11u1 bullseye-pu update > unfortunately updated the bundled openjdk-8 binary snapshot to a > version > not runnable on bullseye since it added dependencies on versioned > symbols from a newer glibc. > That was not noticed at build time since dpkg-gensymbols (?) only > issued > a warning for the missing symbol version and not an error like for a > fully > missing symbol. > We now have a test to ensure the java binary is actually usable ;-) > For amd64 we use a newer binary snapshot built in stretch (lts), for > ppc64el we had to go back to a previously used snapshot and munge the > version a bit. > Unfortunately the amd64 upload got rejected: Version check failed: Your upload included the binary package nvidia-openjdk-8-jre, version 9.+8u332-ga-1~deb9u1~11.2.2-3+deb11u2, for amd64, however experimental already has version 9.+8u332-ga-1~11.5.1-2. Uploads to proposed-updates must have a lower version than present in experimental. Regards, Adam
Bug#1011339: [Pkg-openssl-devel] Bug#1011339: openssl: missing errors strings on mipsel
Le jeu. 26 mai 2022 à 19:23, Sebastian Andrzej Siewior < sebast...@breakpoint.cc> a écrit : > On 2022-05-26 13:49:13 [+0200], Jérémy Lal wrote: > > Thanks for the feedback. > np. > > > Indeed, the latest nodejs version (18.x) embeds an updated openssl.cnf, > > which is exactly the one > > of the openssl debian package, without the [ssl_sect] part at the end. > > > > Why this fails only on mipsel is a mystery to me, maybe some race > condition > > when initializing openssl, > > but this is not a bug. > > me, too. If there is anything you want me to look at, just yell. For now > I consider this handled. This succeeds: ./node test/parallel/test-crypto-key-objects.js This fails only on mipsel (tested on eller porterbox) OPENSSL_CONF=/etc/ssl/openssl.cnf ./node test/parallel/test-crypto-key-objects.js I suppose the problem comes from openssl: - nodejs code calling OPENSSL_init_ssl doesn't depend on mips - nodejs runs on other "slow" architectures, if it was a race condition we would see it there sometimes. Jérémy
Bug#1012057: giac: New version available : do you plan to package it ?
Source: giac Version: 1.7.0.39+dfsg2-1 Severity: wishlist Dear Maintainer, A new upstream version has been released this month. Getting it packaged in Debian could be useful ; I'm especially thinking of its increasing use in Sage, where it is now a standard package. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (650, 'testing'), (60, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1011146: upgrade-system is marked for autoremoval from testing
Hi all, As other dev/maintainers, I got a the autoremoval notification for package resource-agents-paf, which has nothing to do with nvidia things. Maybe what maintainers should do might be clarified here? Should we just sit & wait for the next notification about the false positive bug being fixed? Regards, On Thu, 26 May 2022 09:31:00 +0300 =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= wrote: > I'd really like to know how anyone could ever come to the conclusion > that a package that has nothing to do with graphic drivers needs to be > auto-removed. > > Martin-Éric > > On Thu, May 26, 2022 at 9:01 AM Debian testing autoremoval watch > wrote: > > > > upgrade-system 1.9.1.0 is marked for autoremoval from testing on 2022-06-30 > > > > It (build-)depends on packages with these RC bugs: > > 1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183, > > CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 > > https://bugs.debian.org/1011146 > > > > > > > > This mail is generated by: > > https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl > > > > Autoremoval data is generated by: > > https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl > >
Bug#992296: Acknowledgement (texlive-latex-recommended: index package warns that \markboth and \markright have changed)
Control: tags -1 + wontfix Am 29.05.2022 um 15:39 teilte Norman Ramsey mit: Hi, The issue could be fixed relatively easily by updating `index.sty` so that the `\CheckCommand` calls refer to the `\markboth` and `\markright` as defined in the current latex.ltx. But if nobody is interested in maintaining that one, let's just update this bug report to note that it is now recommended to use LaTeX package `imakeidx` instead of `index`. And I think `wontfix` seems appropriate. Tag it wontfix then and let it rot. H. -- sigfault OpenPGP_signature Description: OpenPGP digital signature
Bug#1012054: Also fails on 5.17.0.3
Bug#1005757: python-jsonschema: Please provide latest upstream release 4.4.0
Hello all, The recent releases of ansible-lint (>= 6.1.0) requires python-jsonschema >= 4.5.1, mainly due to the following bugfix (thought there might be other changes required from that release): https://github.com/python-jsonschema/jsonschema/pull/940 Thomas, are you aware of anything specific which will break openstack or is it because it hasn't been tested yet? Thank you, -- Samuel Henrique
Bug#1012055: FTBFS: build failure with libbtrfs-dev 5.18
Package: snapper
Version: 0.9.1-1
Severity: normal
Tags: ftbfs upstream
With libbtrfs-dev 5.18 (and above, I guess), snapper fails to be built
from source. Newer upstream version 0.10.2 fails, too.
Errors are below.
/usr/include/btrfs/list.h:78:9: error: expected primary-expression before
'volatile'
78 | WRITE_ONCE(list->next, list);
| ^~
/usr/include/btrfs/list.h:78:9: error: expected ')' before 'volatile'
78 | WRITE_ONCE(list->next, list);
| ^~
/usr/include/btrfs/list.h: In function 'void __list_add(list_head*, list_head*,
list_head*)':
/usr/include/btrfs/list.h:116:9: error: expected primary-expression before
'volatile'
116 | WRITE_ONCE(prev->next, xnew);
| ^~
/usr/include/btrfs/list.h:116:9: error: expected ')' before 'volatile'
116 | WRITE_ONCE(prev->next, xnew);
| ^~
/usr/include/btrfs/list.h: In function 'void __list_del(list_head*,
list_head*)':
/usr/include/btrfs/list.h:156:9: error: expected primary-expression before
'volatile'
156 | WRITE_ONCE(prev->next, next);
| ^~
/usr/include/btrfs/list.h:156:9: error: expected ')' before 'volatile'
156 | WRITE_ONCE(prev->next, next);
| ^~
In file included from /usr/include/btrfs/ctree.h:31,
from /usr/include/btrfs/send-utils.h:28,
from BtrfsUtils.cc:36:
/usr/include/btrfs/list.h: In function 'void list_del(list_head*)':
/usr/include/btrfs/list.h:190:23: error: invalid conversion from 'void*' to
'list_head*' [-fpermissive]
190 | entry->next = LIST_POISON1;
| ^~~~
| |
| void*
/usr/include/btrfs/list.h:191:23: error: invalid conversion from 'void*' to
'list_head*' [-fpermissive]
191 | entry->prev = LIST_POISON2;
| ^~~~
| |
| void*
In file included from /usr/include/btrfs/send-utils.h:27,
from BtrfsUtils.cc:36:
/usr/include/btrfs/list.h: In function 'int list_empty(const list_head*)':
/usr/include/btrfs/list.h:333:16: error: expected primary-expression before
'const'
333 | return READ_ONCE(head->next) == head;
|^
/usr/include/btrfs/list.h:333:16: error: expected ')' before 'const'
333 | return READ_ONCE(head->next) == head;
|^
/usr/include/btrfs/list.h:333:16: error: expected ')' before ';' token
333 | return READ_ONCE(head->next) == head;
|^
/usr/include/btrfs/list.h:333:16: note: to match this '('
333 | return READ_ONCE(head->next) == head;
|^
In file included from /usr/include/btrfs/ctree.h:31,
from /usr/include/btrfs/send-utils.h:28,
from BtrfsUtils.cc:36:
/usr/include/btrfs/list.h:333:38: error: invalid operands of types 'void' and
'const list_head*' to binary 'operator=='
333 | return READ_ONCE(head->next) == head;
| ^~
| |
| const list_head*
In file included from /usr/include/btrfs/send-utils.h:27,
from BtrfsUtils.cc:36:
/usr/include/btrfs/list.h: In function 'void list_del_init_careful(list_head*)':
/usr/include/btrfs/list.h:351:9: error: expected primary-expression before
'volatile'
351 | smp_store_release(&entry->next, entry);
| ^
/usr/include/btrfs/list.h:351:9: error: expected ')' before 'volatile'
351 | smp_store_release(&entry->next, entry);
| ^
/usr/include/btrfs/list.h: In function 'int list_empty_careful(const
list_head*)':
/usr/include/btrfs/list.h:369:34: error: expected primary-expression before
'const'
369 | struct list_head *next = smp_load_acquire(&head->next);
| ^~~~
/usr/include/btrfs/list.h:369:34: error: expected ')' before 'const'
369 | struct list_head *next = smp_load_acquire(&head->next);
| ^~~~
/usr/include/btrfs/list.h:369:34: error: expected ')' before ';' token
369 | struct list_head *next = smp_load_acquire(&head->next);
| ^~~~
/usr/include/btrfs/list.h:369:34: note: to match this '('
369 | struct list_head *next = smp_load_acquire(&head->next);
| ^~~~
/usr/include/btrfs/list.h:369:34: error: void value not ignored as it ought to
be
369 | struct list_head *next = smp_load_acquire(&head->next);
| ^~~~
/usr/include/btrfs/list.h: In funct
Bug#1012054: linux-headers-5.17.0-1-amd64: Sleep mode have stoped working with 5.17 version
Package: linux-headers-5.17.0-1-amd64 Version: 5.17.3-1 Severity: important X-Debbugs-Cc: martin+deb...@insulander.info Hi, I try to put the computer to sleep, with either closing the lid or pressing sleep (in kde menu). Expect it to sleep. What happens, since 5.17, it looks like the computer starts to sleep, but directly when screen blacks out, it starts again. This works well in 5.16 (selecting it from Grub at start). Brgds from Martin -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (401, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.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 linux-headers-5.17.0-1-amd64 depends on: ii linux-compiler-gcc-11-x86 5.17.3-1 ii linux-headers-5.17.0-1-common 5.17.3-1 ii linux-kbuild-5.17 5.17.3-1 linux-headers-5.17.0-1-amd64 recommends no packages. linux-headers-5.17.0-1-amd64 suggests no packages. -- no debconf information maj 29 14:18:19 zflip systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. maj 29 14:18:21 zflip xdg-desktop-portal-kde[1949]: xdp-kde-background: GetAppState called: no parameters maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.4499] manager: sleep: sleep requested (sleeping: no enabled: yes) maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.4501] device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') maj 29 14:18:45 zflip ModemManager[847]: [sleep-monitor] system is about to suspend maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.4510] manager: NetworkManager state is now ASLEEP maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.4513] device (wlp1s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') maj 29 14:18:45 zflip dbus-daemon[767]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=849 comm="/usr/sbin/NetworkManager --no-daemon") maj 29 14:18:45 zflip systemd[1]: Starting Network Manager Script Dispatcher Service... maj 29 14:18:45 zflip dbus-daemon[767]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' maj 29 14:18:45 zflip systemd[1]: Started Network Manager Script Dispatcher Service. maj 29 14:18:45 zflip kernel: wlp1s0: deauthenticating from a4:91:b1:61:80:b1 by local choice (Reason: 3=DEAUTH_LEAVING) maj 29 14:18:45 zflip wpa_supplicant[861]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=a4:91:b1:61:80:b1 reason=3 locally_generated=1 maj 29 14:18:45 zflip wpa_supplicant[861]: wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.5690] device (wlp1s0): supplicant interface state: completed -> disconnected maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.5693] device (wlp1s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.5699] dhcp4 (wlp1s0): canceled DHCP transaction maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.5699] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.5699] dhcp4 (wlp1s0): state changed no lease maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.5702] dhcp6 (wlp1s0): canceled DHCP transaction maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.5703] dhcp6 (wlp1s0): activation: beginning transaction (timeout in 45 seconds) maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.5703] dhcp6 (wlp1s0): state changed no lease maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.5747] device (wlp1s0): set-hw-addr: set MAC address to (scanning) maj 29 14:18:45 zflip systemd-resolved[663]: wlp1s0: Bus client reset search domain list. maj 29 14:18:45 zflip systemd-resolved[663]: wlp1s0: Bus client set default route setting: no maj 29 14:18:45 zflip systemd-resolved[663]: wlp1s0: Bus client reset DNS server list. maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.6097] device (wlp1s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') maj 29 14:18:45 zflip NetworkManager[849]: [1653826725.6128] device (wlp1s0): set-hw-addr: reset MAC address to (unmanage) maj 29 14:18:45 zflip wpa_supplicant[861]: p2p-dev-wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all maj 29 14:18:45 zflip wpa_supplicant[861]: p2p-dev-wlp1s0: CTRL-EVENT-DSCP-POLICY clear_all maj 29 14:18:45 zflip wpa_supplicant[861]: nl80211: deinit ifname=p2p-dev-wlp1s0 disabled_11b_rates=0 maj 29 14:18:45 zflip wpa_supplicant[861]: wlp1s0: CTRL
Bug#992296: Acknowledgement (texlive-latex-recommended: index package warns that \markboth and \markright have changed)
On 8/19/21 17:39, Norman Ramsey wrote: Hi Norman, I have learned that this issue was fixed upstream, but not until TeXLive 2021. The fix can be found at https://github.com/latex3/latex2e/pull/518/commits/ab0cb06c45dd7beca0569a1b4004e5a1d5de0a70 Are you sure this is the correct commit to address your issue? Even w/ TL 2022 the issue is still visible. According to [1] the usage of index is rather deprecated. I'm afraid we have to close the bug (or mark it as wontfix), as it will never be solved. Hilmar [1] https://tex.stackexchange.com/questions/503759/help-needed-what-is-wrong-with-my-code -- Testmail
Bug#1012052: French translate of partman_hfs template
package: partman-hfs severity: wishlist Tags: patch l10n Dear mainteners, hello, Please find attach the french templates translation proofread by the debian-l10n-french mailing list contributors. this file should be put as debian/fr.po in your package build tree kind regards, greatings, bubu fr.po.xz Description: application/xz
Bug#1012053: podman - fails to run container as root: container create failed (no logs from conmon)
Package: podman
Version: 4.1.0+ds2-2
Severity: important
X-Debbugs-Cc: wa...@debian.org
podman currently fails to create any container as root. It always fails
with:
| % sudo podman run --rm --network host debian:sid-slim
| Error: container create failed (no logs from conmon): conmon bytes "":
readObjectStart: expect { or n, but found , error found in #0 byte of ...||...,
bigger context ...||...
Internally, crun fails after a quick check of /proc/self/uid_map, but is
silent why.
| openat(AT_FDCWD,
"/sys/fs/cgroup/machine.slice/libpod-45964672ec0043cbf4908f23824ae0a4cf1b5d244fbd72e9ace8c396beb38b25.scope/container",
O_RDONLY|O_DIRECTORY) = 6
| geteuid() = 0
| openat(AT_FDCWD, "/proc/self/uid_map", O_RDONLY) = 7
| statx(7, "", AT_STATX_DONT_SYNC|AT_SYMLINK_NOFOLLOW|AT_EMPTY_PATH,
STATX_SIZE, {stx_mask=STATX_BASIC_STATS|STATX_MNT_ID, stx_attributes=0,
stx_mode=S_IFREG|0644, stx_size=0, ...}) = 0
| read(7, " 0 0 4294967295\n", 4096) = 33
| read(7, "", 8159) = 0
| close(7)= 0
| close(6)= 0
| kill(3729, SIGKILL) = 0
Bastian
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (700, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.17.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages podman depends on:
ii conmon 2.1.0+ds1-1
ii containernetworking-plugins 1.1.0+ds1-1+b1
ii crun 0.17+dfsg-1.1+b1
ii golang-github-containers-common 0.44.5+ds1-1
ii libc62.33-7
ii libdevmapper1.02.1 2:1.02.175-2.1
ii libgpgme11 1.16.0-1.2
ii libseccomp2 2.5.4-1
Versions of packages podman recommends:
ii buildah 1.23.1+ds1-2+b1
pn catatonit | tini | dumb-init
ii fuse-overlayfs1.8.2-1
pn golang-github-containernetworking-plugin-dnsname
ii slirp4netns 1.0.1-2
ii uidmap1:4.11.1+dfsg1-2
Versions of packages podman suggests:
pn containers-storage
pn docker-compose
ii iptables1.8.8-1
-- no debconf information
Bug#993957: closed by Christoph Biedl (Re: Bug#993957: (no subject))
On Sun, May 29, 2022 at 12:16 PM Debian Bug Tracking System wrote: > #993957: schroot: fails with non-existent subdirectory > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Christoph Biedl > by > replying to this email. christoph has misunderstood that i have provided the repro circumstances: sysvinit is required to be installed and utilised before this bug will occur. with sysvinit being a supported debian boot mechanism the closure of this bugreport is not the correct action to take. this bug is not unreproducible: the declaration that it is unreproducible is invalid. l.
Bug#1012034: dpkg: warning: unknown dpkg database file /var/lib/dpkg/format is not a misplaced alternative state
On Sun, May 29, 2022 at 2:47 PM Guillem Jover wrote: > On Sun, 2022-05-29 at 09:07:25 +0300, Martin-Éric Racine wrote: > > Package: dpkg > > Version: 1.21.8 > > Severity: normal > > > On a host running Testing, I got the message below this morning: > > > > Unpacking dpkg (1.21.8) over (1.21.7) ... > > Setting up dpkg (1.21.8) ... > > dpkg: warning: unknown dpkg database file /var/lib/dpkg/format is not a > > misplaced alternative state... leaving as is > > dpkg-db-backup.service is a disabled or a static unit not running, not > > starting it. > > > No amount of googling told me what the line about /var/lib/dpkg/format > > means or whether this is something to worry about. This probably needs > > to be documented, especially if it's expected to appear during an > > upgrade from Bullseye to Bookworm. > > This file is really not supposed to be there, and was not the target > of that check, which was added to fix a very short-lived mess up with > dpkg 1.21.0, so it should not affect bullseye users, but might catch > this kind of unrelated breakage, so I'm considering keeping the check > part (not the u-a fixing part) and integrating it properly into > «dpkg --audit» or similar. > > The only format file expected to be present in the dpkg db is > /var/lib/dpkg/info/format, but certainly not on the db root. What are > the contents for that file? $ ls -al /var/lib/dpkg/format -rw-r--r-- 1 root root 1 2011-03-15 18:38 /var/lib/dpkg/format $ cat /var/lib/dpkg/format 2 Martin-Éric
Bug#1009363: bullseye-pu: package ruby-net-ssh/1:6.1.0-2+deb11u1
On Sat, May 28, 2022 at 08:47:53PM +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Tue, 2022-04-12 at 09:40 -0300, Antonio Terceiro wrote: > > OpenSSH 8.8 disables RSA signatures using the SHA-1 hash algorithm, > > and > > that breaks clients that do not support stronger algorithms, which is > > the case of the ruby-net-ssh version in bullseye. > > > > [ Impact ] > > Users of vagrant and capistrano, for example, are not able to connect > > to hosts running OpenSSH 8.8, which includes Debian bookworm but also > > other distributions where OpenSSH 8.8. is already available. > > > [...] > > The patches are backports of the relevant upstream patches. The first > > adds support for client authentication with RSA + SHA-2. The second > > adds > > support for RSA+SHA-2 in host keys. > > > > Please go ahead. Uploaded. signature.asc Description: PGP signature
Bug#1012051: ITP: python-qpageview -- qpageview provides a page based document viewer widget for Qt5/PyQt5
Package: wnpp Severity: wishlist Owner: Jean Baptiste Favre X-Debbugs-Cc: debian-de...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: python-qpageview Version : 0.6.2 Upstream Author : Wilbert Berendsen * URL : https://github.com/frescobaldi/qpageview * License : GPL Programming Lang: Python Description : qpageview provides a page based document viewer widget for Qt5/PyQt5 qpageview is a versatile View widget with many optional mixin classes to cater for anything between basic or powerful functionality while preserving performances displaying large PDF document, rendering in a background thread with smart priority control. Qpageview was previously part of Frescobaldi. It has been removed from Frescobaldi 3.2 to be managed as a separate project and will become a dependency for future Frescobaldi Debian packages. -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEToRbojDLTUSJBphHtN1Tas99hzcFAmKTZIdfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRF ODQ1QkEyMzBDQjRENDQ4OTA2OTg0N0I0REQ1MzZBQ0Y3RDg3MzcACgkQtN1Tas99 hzdycA//Tzrzyol1eQB/azQc4AC/Mad33gJKKG7hoAmeLgXtUPZ/1F3YlD3fywFV iYHnxtSNXsRmmIFYKOkzd78sV0EpM0FDzMCHRkm35Kgz8A04D93H1CG3a4QbFA0D vX9Z8OkDbiE/ifEqfB9xe7zdtjKX+YIDa9zRvKEAaGB9spW71vwTQvmQIctqoZkj inJNbeVl0j490A3e1cLlF+i6iMyfacQChn6QrG+2qQt5JrXV+Gj074ymW+D//GLs Xd776oiwa4BuWPHe9wfGV5T3dJh0RrmbUYU6kaSn2YHXaifOhwxUYaihv5g7FQLr cwQdai6DHFsHKHK05YFmDrrp9an0iKvMQNaJgISeSxLh9hEVTfn8JuUnSbZd5bUK N1lGFW86zo957pACPz5yRjMmWy3gntyq3Wm24CXkqFsBKsPY6evRoJJsIPvGvoAs DnqGiZt8nLwsYh9AxUiOISIU4xEPTtZWBJseetPcauDV8wgdOwtwaZJ1Nqp18u3m OGrOCQ3W34NcYegAQJWhV+NENDw8S+P4VBR7hOsLNUkOb8YZKKbCGyNrK6t53beW s206itcAdN2Qdcf3u4btkXrIfLpdArwhu9AUJRXPsYYcJPGuXmjtWVHsdYCWE/cc tu1h1Yi+FUdyLO/hcq6mlQYhrbc+Ym+FmK9oOn3mPjg76gi/PyM= =+5ZH -END PGP SIGNATURE-
Bug#1012050: ITP: alpine-chroot-install -- bootstrap Alpine Linux into a chroot
Package: wnpp Severity: wishlist Owner: Adam Borowski X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: alpine-chroot-install Version : 0.13.3 Upstream Author : Jakub Kirutka * URL : https://github.com/alpinelinux/alpine-chroot-install * License : MIT Programming Lang: shell Description : bootstrap Alpine Linux into a chroot This script builds an Alpine Linux chroot, fetching packages from a network mirror. The installed system is quite minimal, but contains enough to let you install whatever you need using "apk". . In other words, it's alpine's debootstrap. This package will let us spy on the competition, steal their enablement of musl, and possibly similar naughty deeds. In theory it could also be used to port your stuff to Alpine, but that'd be treason, right?
Bug#1010026: qemu-system-x86: fails to start VM with "host" cpu missing features
Control: retitle -1 qemu-system-x86: fails to start: kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed. 28.05.2022 01:28, Bob Weber wrote: I have this same problem when I upgraded a testing system on May 24. I also installed: linux-image-5.17.0-2-amd64 from unstable This is the error from a (all) VM: vm: error: failed to set MSR 0xc104 to 0x1 kvm: ../../target/i386/kvm/kvm.c:2996: kvm_buf_set_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed. When I downgraded the kernel to: linux-image-5.15.0-3-amd64/now 5.15.15-2 amd64 (my previous kernel) Does it work with later kernels? What CPU do you have? /mjt
Bug#993957: (no subject)
On Sun, May 29, 2022 at 11:51 AM Christoph Biedl wrote: > No doubt about that, but my time is too precious for advocacy. > And since I can neither understand nor reproduce the issue, there's > nothing left to do here. you misunderstand. i wasn't speaking of advocacy, merely explaining exactly how and why the issue was detected, so that you are aware of the context. sysvinit is still officially supported by debian. therefore if a package breaks when sysvinit is installed and in use, that's serious. i described how to install it so that you could install it and thus reproduce the issue. therefore, closing this bugreport is the wrong action to take. i leave it with you to re-open it. my role and responsibility is completed in raising the issue and in responding to questions as best i am able. l.
Bug#1012034: dpkg: warning: unknown dpkg database file /var/lib/dpkg/format is not a misplaced alternative state
Hi! On Sun, 2022-05-29 at 09:07:25 +0300, Martin-Éric Racine wrote: > Package: dpkg > Version: 1.21.8 > Severity: normal > On a host running Testing, I got the message below this morning: > > Unpacking dpkg (1.21.8) over (1.21.7) ... > Setting up dpkg (1.21.8) ... > dpkg: warning: unknown dpkg database file /var/lib/dpkg/format is not a > misplaced alternative state... leaving as is > dpkg-db-backup.service is a disabled or a static unit not running, not > starting it. > No amount of googling told me what the line about /var/lib/dpkg/format > means or whether this is something to worry about. This probably needs > to be documented, especially if it's expected to appear during an > upgrade from Bullseye to Bookworm. This file is really not supposed to be there, and was not the target of that check, which was added to fix a very short-lived mess up with dpkg 1.21.0, so it should not affect bullseye users, but might catch this kind of unrelated breakage, so I'm considering keeping the check part (not the u-a fixing part) and integrating it properly into «dpkg --audit» or similar. The only format file expected to be present in the dpkg db is /var/lib/dpkg/info/format, but certainly not on the db root. What are the contents for that file? Thanks, Guillem
Bug#1011603: FTBFS with systemd v251 in dh_auto_test
On Wed, 25 May 2022 10:34:15 +0200 Michael Biebl wrote: Source: bolt Version: 0.9.2-1 Severity: serious bolt currently FTBFS during dh_auto_test and also fails its autopktest. This is due to a change in systemd v251. See https://github.com/systemd/systemd/issues/23499 where this is being discussed. I've created a MR. See https://salsa.debian.org/freedesktop-team/bolt/-/merge_requests/5 OpenPGP_signature Description: OpenPGP digital signature
Bug#1012049: photofilmstrip: unable to add pictures
Package: photofilmstrip Version: 3.7.3-2 Severity: important X-Debbugs-Cc: noreply+debian.reportbug.photofilmst...@adaptivetime.com Dear Maintainer, * What led up to the situation? Run program (GUI mode), create new project, add picture. * What was the outcome of this action? Program throws an uncaught exception before hanging: File "/home/gravis/pfs/photofilmstrip/gui/ImageSectionEditor.py", line 481, in OnResize self.__Scale() File "/home/gravis/pfs/photofilmstrip/gui/ImageSectionEditor.py", line 122, in __Scale self._imgProxy.Scale(newWidth, newHeight) File "/home/gravis/pfs/photofilmstrip/gui/ImageSectionEditor.py", line 675, in Scale img = self._wxImg.Scale(width, height) TypeError: Image.Scale(): argument 1 has unexpected type 'float' -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages photofilmstrip depends on: ii gstreamer1.0-libav 1.20.2-1 ii libjs-sphinxdoc 4.5.0-3 ii python3 3.10.4-1+b1 ii python3-gst-1.0 1.20.2-1 ii python3-pil 9.1.0-1 ii python3-wxgtk4.04.0.7+dfsg-13 photofilmstrip recommends no packages. photofilmstrip suggests no packages.
Bug#1010340: (no subject)
I have unfortunately had to make the same experiences. with the accelerator hax or whpx it leads to the same error with QEMU (tested v6.2.x and v7.0.x). Using tcg as accelerator is not an alternative, because it is extremely slow. What I could find out so far is that it leads to an error with Ubuntu 20.04 LTS and 22.04 LTS. Also when updating git. Strangely, the error does not appear with Ubuntu 21.04. Therefore, I recently thought to repeat the test with Ubuntu 22.04 LTS where I unfortunately found that the same error occurs. What helps is compiling git with OpenSSL instead of GnuTLS (which is standard with git). See also https://github.com/paul-nelson-baker/git-openssl-shellscript. How could I get to the root cause of the error? Regards, Sascha
Bug#1012046: Configuration solution
Hi, I just found a "solution" to get rid of the problem without recompiling anything : TMPFILE env var is taken into account. I have added a systemd override file for my user. It may be useful to have it globally by default in the distro. $ systemctl --user cat gnome-terminal-server.service | tail # /home/lpouzenc/.config/systemd/user/gnome-terminal-server.service.d/override.conf [Service] RuntimeDirectory=gnome-terminal-server Environment=TMPDIR=%t/gnome-terminal-server After closing and opening my gnome session again : $ tr '' 'n' < /proc/$(pidof gnome-terminal-server)/environ | grep TMP TMPDIR=/run/user/1000/gnome-terminal-server $ lsof -np $(pidof gnome-terminal-server) | tail -n5 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse.portal file system /run/user/1000/doc Output information may be incomplete. gnome-ter 15142 lpouzenc 12u unix 0xf567608e 0t0 252993 type=STREAM (CONNECTED) gnome-ter 15142 lpouzenc 13u CHR 5,2 0t0 85 /dev/ptmx gnome-ter 15142 lpouzenc 14u CHR 5,2 0t0 85 /dev/ptmx gnome-ter 15142 lpouzenc 15u REG 0,52 458752 674 /run/user/1000/gnome-terminal-server/#674 (deleted) gnome-ter 15142 lpouzenc 16u REG 0,52 65536 675 /run/user/1000/gnome-terminal-server/#675 (deleted) Hope it could help others, Cheers, Ludovic
Bug#1010663: RFS: strawberry/1.0.4-1 [ITP] -- Audio player and music collection organizer
On 28/05/2022 18:51, Jeroen Ploemen wrote: Paul, Thomas, thanks for digging up the old reject. Peter, I did some more digging and found one unresolved copyright issue from my previous comment as well as some fresh ones: * copyright holder Pascal Below for various scrobbler-related files is still missing * copyright holder Nick Lanham missing for savedgroupingmanager.cpp; note that copyright for both .cpp and .h is shared with Jonas Kvinge * missing entry for src/core/lazy.h * as the info for src/dbus/*.xml doesn't seem to exist anywhere in the sources, please add a comment field to that paragraph explaining what the entry is based on * the license paragraph for GPL-3 doesn't restrict the version to v3 only (other than the shortname suggesting so) and lacks a link to the full text of the license on debian systems I noticed you changed the build to qt6 and while that works fine, it does seem that at the moment qt5 is very much the standard qt release in the distribution. A quick comparison using `reverse-depends -b qt6-tools-dev` vs the same for qttools5-dev showed 6 packages build-depending on the former and around 300 on the latter. Is there any particular advantage to using qt6 for strawberry? Don't worry too much about the reprotest, sometimes these things throw a tantrum. Hi Jeroen, Updated copyright and reverted to Qt5
