Bug#1011549: openrocket needs newer jogl
Hi Bdale,
On Tue, May 24, 2022 at 01:56:05PM -0600, Bdale Garbee wrote:
> Package: libjogl2-java
> Version: 2.3.2+dfsg-9
>
> I'm working on re-packaging openrocket so that it can go back into
> Debian main. A big part of the work is eliding all the embedded class
> library jar files and replacing those with Debian library packages.
>
> One of the class libraries is jogl, for which openrocket apparently
> needs jogl 2.4 with patches applied by Sibo:
>
> https://github.com/openrocket/openrocket/issues/1156
> https://github.com/openrocket/openrocket/pull/1157
>
> Is there any chance we could freshen the Debian package? I see that
> jogamp.org still shows 2.3.2 as the most recent "stable" release, but
> that's about 7 years old.
>
> I'm linking against the 2.3.2 package now, and the core of openrocket is
> working ok, but none of the 3d rendering features will work until we get
> to a fresher jogl version.
I'm not able to find a tag for 2.4.0 in any of these:
https://jogamp.org/cgit/jogl.git/
https://github.com/sgothel/jogl/tags
There is a source tarball here:
https://jogamp.org/deployment/v2.3.2/archive/Sources/
But I only see binary artifacts in the v2.4.0-rc-${date} directories
here:
https://jogamp.org/deployment/
Probably the best we can do is create our own source tarball from the
latest commit on the master branch of (which does have commits within
the past 2 years) from either:
https://jogamp.org/cgit/jogl.git
or
https://github.com/JogAmp/jogl/tags
However, I read the openrocket issue. It seems to end with someone
using a binary jar from an Astro Pixel Processor release. I was curious
to see if the binary jar perhaps includes sources, but the
jogamp-fat.jar in the astropixelprocessor.deb contains class files and a
number of libjogl.so files for multiple architectures.
In other words, it seems to be non-free blobs all the way down. If the
patched version of jogl is required for openrocket, we would need
someone to come up with some DFSG sources for the patches.
Cheers,
tony
signature.asc
Description: PGP signature
Bug#995289: foolscap: ready for upload
Hi Andrius, Andrius Merkys writes: > Hello, > > I have removed unneeded files from python3-foolscap binary package. > Furthermore, there was an issue with building package with > git-buildpackage, which I solved by updating the certificates used for > tests. > > The package is ready for the upload now. If it is OK, I can upload it > myself. Sorry this message some how missed my inbox and did not notice till today. I'm new to python team and I will let you do the upload. I will wait for couple of days for your response else I will prepare and upload the same. Thanks and Regards, Vasudev
Bug#1006530: mariadb-10.6: FTBFS on x32: undefined reference to misc functions and files (regression from MariaDB 10.5)
Thanks! I just wanted to follow up and notify that x32 now indeed builds and test suite passed too: https://buildd.debian.org/status/package.php?p=mariadb-10.6
Bug#1011174: marked as pending in controlsfx
Hi Emmanuel, On Tue, May 24, 2022 at 06:43:59PM +0200, Emmanuel Bourg wrote: > Hi Tony, > > Sorry for that, there are so many Java packages and so few maintainers > that we rarely have concurrency issues and I'm not used to check the > ownership of the bugs. I assumed you were working on netty following > your comment on #1011135 yesterday, and I picked controlsfx instead. > I'll try to be more careful. I hope you'll be able to rebase your work > without too much trouble. It certainly is true that we have plenty of packages to go around and that concurrency issues are rare. The rebase is no problem, of course; we were doing the same freshening and I can just reset --hard. Since you're doing a lot of heavy lifting detecting and triaging all of these Java 17 bugs, my primary motivation for mentioning it is the hope that we can help you squash them by claiming them. I have been poking at netty for a while (more for the open CVEs). I will claim that one. :) Cheers, tony
Bug#891748: all-numeric usernames
Control: tags -1 patch Hi! I've added a patch[0] that rejects all-numeric usernames in adduser.. feedback welcome! Cheers, Matt [0] https://salsa.debian.org/debian/adduser/-/merge_requests/21
Bug#679746: system users @ /nonexistent
Control: tags -1 patch This patch [0] implements the default system user home dir as /nonexistent. Feedback welcome! Cheers, Matt [0] https://salsa.debian.org/debian/adduser/-/merge_requests/20
Bug#1008081: SYS_DIR_MODE
Control: tags -1 patch Hi! I've created a patch[0] which implements SYS_DIR_MODE as described in this bug; any feedback is welcome! One thing I just wanted to confirm: the default for regular accounts *should* have setgid? I only ask because this was previously documented as causing issues (in adduser.conf.5). Cheers! Matt' [0] https://salsa.debian.org/debian/adduser/-/merge_requests/19
Bug#824520: RFP: subsurface -- scuba diving logbook
On Sun, May 22, 2022 at 10:45 PM Salvo Tomaselli wrote: > My advice is to forget this. Upstream is really uncooperative and > Torvalds went to conferences to talk about this (conveniently > forgetting to mention he was depending an unstable library whose > author said "Don't use this yet") Well also had some interactions with upstream in the past and it felt indeed a bit "difficult". So I can kinda understand your frustration. Nevertheless, that upstream may be a bit distribution-unfriendly doesn't make subsurface itself less usable. I'd say it's still among the "best" software for diving in the FLOSS world - and that "market" isn't so big, so people cannot just easily choose any other random software (none if which would be packaged for Debian either). In the end, divers will just resort to some unofficial packages (security issues) or IMO questionable systems like snap. So I think there would be some value to get that officially packaged. Thanks, Philippe
Bug#824520: RFP: subsurface -- scuba diving logbook
On Sun, May 22, 2022 at 2:09 PM David Bremner wrote: > To be honest, I doubt that helps, since the hard part is not just making > packages (my repo on salsa already does that), but making them in a way > acceptable to debian policy, which is unlikely to be a priority for a > PPA. Were there any specific concerns in terms of policies left? subsurface seems rather simple to me, the only bigger point perhaps being the issue with libdivecomputer. But not since the "official" one is even gone from Debian, it shouldn't be to hard to make a point for a libdivecomputer-subsurface or so, when one could argue that this is really a fork and thus acceptable for Debian.
Bug#1011595: mutt: Index is garbled in GNU Screen due to U+061C ARABIC LETTER MARK characters in the subject
Package: mutt Version: 2.2.4-1 Severity: important Tags: upstream Forwarded: https://gitlab.com/muttmua/mutt/-/issues/413 I've received a spam with U+061C ARABIC LETTER MARK characters in the subject, which makes the index garbled in GNU Screen. I don't know what they are, but they should probably be filtered out. This can be tested on the attached mailbox, e.g. screen mutt -F /dev/null -f mscreen-202205.mbox The status line is 2 lines above the correct position. When such a message is in a real mailbox, the index is garbled, though if one doesn't pay attention, the index may look fine and there is a risk to delete wrong messages, because some index lines are shifted compared to the cursor (so, one thinks that one deletes some message, but it is actually another message that is deleted). -- Package-specific info: Mutt 2.2.5+22 (1066be97) vl-138565 (2022-05-21) Copyright (C) 1996-2022 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 5.17.0-2-amd64 (x86_64) ncurses: ncurses 6.3.20220423 (compiled with 6.3) libidn: 1.38 (compiled with 1.38) Compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 11.3.0-3' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-11 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-11-6lTGZp/gcc-11-11.3.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-6lTGZp/gcc-11-11.3.0/debian/tmp-gcn/usr --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=2 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 11.3.0 (Debian 11.3.0-3) Configure options: --prefix=/home/vinc17 --enable-debug --enable-pop --enable-imap --with-ssl --enable-compressed --with-exec-shell=/home/vinc17/bin/sh.screen --enable-gpgme --with-system-dotlock=/usr/bin/mutt_dotlock CC=gcc 'CFLAGS=-g -O3 -march=native -fsanitize=undefined -fno-sanitize-recover' Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O3 -march=native -fsanitize=undefined -fno-sanitize-recover Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_FUTIMENS +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN -HAVE_LIBIDN2 +HAVE_GETSID -USE_HCACHE -USE_SIDEBAR +USE_COMPRESSED +USE_INOTIFY ISPELL="/usr/bin/ispell" SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/home/vinc17/share/mutt" SYSCONFDIR="/home/vinc17/etc" EXECSHELL="/home/vinc17/bin/sh.screen" -MIXMASTER To contact the developers, please mail to . To report a bug, please contact the Mutt maintainers via gitlab: https://gitlab.com/muttmua/mutt/issues patch-20200424.vl.pretty_size.1 patch-20200505.vl.simplesearchkw.1 patch-20200424.pdmef.progress.vl.1 patch-20201129.vl.address_all_patt.1 patch-20201130.tamovl.sysdotlock.1 -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=POSIX, LC_CTYPE=C.UTF-8
Bug#1004118: E1187: Failed to source defaults.vim
On Mon, May 23, 2022 at 04:29:49PM +0100, Dagfinn Ilmari Mannsåker wrote: > James McCoy wrote: > > On Tue, Feb 01, 2022 at 06:19:43PM +0100, Diederik de Haas wrote: > >> $ vim.tiny .ssh/authorized_keys > >> E1187: Failed to source defaults.vim > >> Press ENTER or type command to continue > > > > The binary vim.tiny is an implementation detail. I tried to move > > them under /usr/libexec, but that caused the alternatives to reset their > > priorities for existing installs, so it had to be reverted. > > > > The intended use is to invoke the binary through the named alternatives > > (vi, view, ex, editor). > > > > When invoked as vi it doesn't, because that triggers Debian's patch to > > only use the tiny config. > > Given that `vim.tiny` registers itself for the `view` and `editor` > alternatives, it really should not throw any errors or warnings when > invoked via them (I noticed this because `sudoedit` falls back to > `editor` if the `$EDITOR` and `$VISUAL` environment variables aren't > set). Agreed. I intend to update the vim.tiny patch so that it would avoid this message. I just haven't gotten to it yet. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1011594: Please import new upstream snapshot (currently at 0.0~git20220518.60ebf56)
Package: kotlin-mode Version: 0.0~git20210917.3e0c340-1 Severity: normal X-Debbugs-Cc: s...@debian.org Hi Joshua, Upstream has released bugfixes, so please import them into your package :) Also, your package doesn't yet declare a team maintainer. To make it officially team maintained, please apply the following diff: diff --git a/debian/control b/debian/control index 41ade1f..ad10a0b 100644 --- a/debian/control +++ b/debian/control @@ -1,7 +1,8 @@ Source: kotlin-mode Section: editors Priority: optional -Maintainer: Joshua Peisach +Maintainer: Debian Emacsen team +Uploaders: Joshua Peisach Build-Depends: debhelper-compat (= 13), dh-elpa Standards-Version: 4.6.0 Sorry I forgot to ask if you intended for this package to be team-maintained during the initial sponsorship process. Don't forget to close this bug from the changelog, and please let me know when you're ready for me to sponsor. Regards, Nicholas P.S. I'm not sure if you noticed, but kotlin-mode didn't upgrade to testing because you didn't request a -2 (second Debian release) source-only upload. Uploading this new version as a source-only upload will resolve this issue.
Bug#1011526: pidgin: fails to start on sway
I really don't know. Are other GTK apps working? If so, GTK 2 apps specifically? -- Richard
Bug#1011593: RM: colorclass -- ROM; leaf package, no longer needed
Package: ftp.debian.org Severity: normal I packaged this Python library as a dependency for an ITP that I eventually dropped because of its large number of dependencies. I files an RFA for colorclass a long time ago (#929658) and emailed the team list but have had no takers. There are no reverse dependencies, so I think we should rm colorclass.
Bug#1011592: plexus-utils2: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests
Source: plexus-utils2 Version: 3.3.0-1 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 plexus-utils2 fails to build with OpenJDK 17, the tests make an illegal reflective accesses into java.base/java.lang: [INFO] Running org.codehaus.plexus.util.ReflectionUtilsTest [ERROR] Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.001 s <<< FAILURE! - in org.codehaus.plexus.util.ReflectionUtilsTest [ERROR] testComplexVariableAccess(org.codehaus.plexus.util.ReflectionUtilsTest) Time elapsed: 0.001 s <<< ERROR! java.lang.reflect.InaccessibleObjectException: Unable to make field private static final int java.lang.Class.ANNOTATION accessible: module java.base does not "opens java.lang" to unnamed module @4cfaf581 at org.codehaus.plexus.util.ReflectionUtilsTest.testComplexVariableAccess(ReflectionUtilsTest.java:49)
Bug#1011590: RM: plowshare -- ROM; effectively unmaintained upstream
Package: ftp.debian.org Severity: normal Plowshare is a tool for interacting with file sharing websites. The plowshare package itself contains only the framework (implemented in shell scripts) but separate "modules" are needed to actually implement support for specific websites. The modules need to change rapidly to keep up with developments on the file sharing websites, and as such are not a great fit for Debian packaging (I tried in the past but eventually removed them). The upstream-endorsed way to get the modules is to use a bundled script to download them, but there are security concerns with downloading a bunch of shell scripts from the internet and blindly executing them. There is also a security concern with the use of a javascript engine to interact with the sometimes sketchy file sharing sites that resulted in a Debian patch to disable this feature by default. With the JS engine disabled, many modules don't work. Upstream development on these modules has essentially stopped, and presumably many are now broken. In theory you can write your own modules, in which case the plowshare package has some value by itself. I suspect that few people would do this though, especially without any public place to share modules and the burden of maintaining them. Popcon stats show a decline in reports for plowshare since the removal of the modules. It is a leaf package with no reverse dependencies.
Bug#1011589: Updating the transcend Uploaders list
Source: transcend Version: 0.3.dfsg2-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the transcend package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011588: Updating the taoframework Uploaders list
Source: taoframework Version: 2.1.svn20090801-14.1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the taoframework package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011587: Updating the supertuxkart Uploaders list
Source: supertuxkart Version: 1.2+ds2-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the supertuxkart package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011586: Updating the powermanga Uploaders list
Source: powermanga Version: 0.93.1-4 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the powermanga package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011585: Updating the pangzero Uploaders list
Source: pangzero Version: 1.4.1+git20121103-5 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the pangzero package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011584: Updating the nikwi Uploaders list
Source: nikwi Version: 0.0.20120213-4 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the nikwi package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011582: Updating the kxl Uploaders list
Source: kxl Version: 1.1.7-17 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the kxl package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011583: Updating the libsdl2 Uploaders list
Source: libsdl2 Version: 2.0.14+dfsg2-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the libsdl2 package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011581: Updating the ketm Uploaders list
Source: ketm Version: 0.0.6-25 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the ketm package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011580: Updating the kanatest Uploaders list
Source: kanatest Version: 0.4.8-4 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the kanatest package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011579: Updating the hex-a-hop Uploaders list
Source: hex-a-hop Version: 1.1.0+git20140926-1.1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the hex-a-hop package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011578: Updating the freealut Uploaders list
Source: freealut Version: 1.1.0-6 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the freealut package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011577: Updating the clanlib Uploaders list
Source: clanlib Version: 1.0~svn3827-8 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the clanlib package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011576: Updating the chromium-bsu Uploaders list
Source: chromium-bsu Version: 0.9.16.1-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the chromium-bsu package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011574: O: zzuf -- transparent application fuzzer
Package: wnpp The current maintainer of zzuf, Sam Hocevar , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: zzuf Binary: zzuf Version: 0.15-1 Maintainer: Sam Hocevar Build-Depends: debhelper (>= 9.0), dh-autoreconf Architecture: any Standards-Version: 3.9.7 Format: 3.0 (quilt) Files: 048fd6378308968f168d54b2491826c7 1617 zzuf_0.15-1.dsc 660781890c98a394c7d5996d1d4259b2 493559 zzuf_0.15.orig.tar.gz 6cff2d47b6aee561d26df084d8168de5 2972 zzuf_0.15-1.debian.tar.xz Checksums-Sha256: 98b0f16e2071828acd4f78bc78a62284b1a817d137c47be526e63c99ad493150 1617 zzuf_0.15-1.dsc a34f624503e09acd269c70d826aac2a35c03e84dc351873f140f0ba6a792ffd6 493559 zzuf_0.15.orig.tar.gz 4326410bf40142b1784292240d95d44903b8873e14f78aaef6133f8b9be015fb 2972 zzuf_0.15-1.debian.tar.xz Package-List: zzuf deb devel optional arch=any Directory: pool/main/z/zzuf Priority: source Section: devel Package: zzuf Source: zzuf (0.15-1) Version: 0.15-1+b1 Installed-Size: 175 Maintainer: Sam Hocevar Architecture: amd64 Depends: libc6 (>= 2.15) Description-en: transparent application fuzzer Zzuf is a transparent fuzzer. It works by intercepting applications' file and network operations and changing random bits in their input. Its behaviour is deterministic, making it easy to reproduce bugs. . Zzuf has support for variable fuzzing ratio, character filtering, fuzzing decision based on filenames and optional network fuzzing. It can also stop processes that run for too long or that output too much data. Description-md5: 27dbe1f74dc9503e917a86ba5a96a833 Tag: implemented-in::c, role::program Section: devel Priority: optional Filename: pool/main/z/zzuf/zzuf_0.15-1+b1_amd64.deb Size: 62246 MD5sum: 51f2e27b3b819b276078135dc3793375 SHA256: 30947ff9d6d7b55b337848e1440d3119ac4deb45f021c6d588f34f914347051a -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011575: Updating the asc Uploaders list
Source: asc Version: 2.6.1.0-7 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Sam Hocevar has not been working on the asc package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011573: O: yasm -- modular assembler with multiple syntaxes support
Package: wnpp The current maintainer of yasm, Sam Hocevar , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: yasm Binary: yasm Version: 1.3.0-2.1 Maintainer: Sam Hocevar Build-Depends: debhelper (>= 9.0), dh-autoreconf, bison, gettext, xmlto, python2 Architecture: any Standards-Version: 3.9.6 Format: 3.0 (quilt) Files: cc3fda7934f6a0285e44bafd2d395b8b 1895 yasm_1.3.0-2.1.dsc fc9e586751ff789b34b1f21d572d96af 1492156 yasm_1.3.0.orig.tar.gz c8cce265f0cfad7b3955ad98e6fb892e 8256 yasm_1.3.0-2.1.debian.tar.xz Vcs-Browser: http://svn.debian.org/wsvn/sam-hocevar/pkg-misc/unstable/yasm/ Vcs-Svn: svn://svn.debian.org/sam-hocevar/pkg-misc/unstable/yasm Checksums-Sha256: 35f87f5d8f8f123643a244d76006b6f772af72c5148ab87ec4e189aec9b37373 1895 yasm_1.3.0-2.1.dsc 3dce6601b495f5b3d45b59f7d2492a340ee7e84b5beca17e48f862502bd5603f 1492156 yasm_1.3.0.orig.tar.gz 473e9f318bd274dee92db4ee3247f7e64cd709a569ce1825fdf935cd01490409 8256 yasm_1.3.0-2.1.debian.tar.xz Homepage: http://www.tortall.net/projects/yasm/ Package-List: yasm deb devel optional arch=any Directory: pool/main/y/yasm Priority: source Section: devel Package: yasm Version: 1.3.0-2.1 Installed-Size: 2131 Maintainer: Sam Hocevar Architecture: amd64 Depends: libc6 (>= 2.14) Description-en: modular assembler with multiple syntaxes support Yasm is a complete rewrite of the NASM assembler. It supports multiple assembler syntaxes (eg, NASM, GAS, TASM, etc.) in addition to multiple output object formats (binary objects, COFF, Win32, ELF32, ELF64) and even multiple instruction sets (including AMD64). It also has an optimiser module. Description-md5: dea64a38f47da6fb51ac8a3e78582601 Multi-Arch: foreign Homepage: http://www.tortall.net/projects/yasm/ Tag: devel::compiler, devel::machinecode, implemented-in::c, role::program Section: devel Priority: optional Filename: pool/main/y/yasm/yasm_1.3.0-2.1_amd64.deb Size: 409260 MD5sum: 1c1c1f750d842763a319a26aef05ed36 SHA256: 0298de20ea7666c31ea2d085d9a140263405cef81db8c9fae0497cf2b5ff5b85 -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011572: O: toilet -- display large colourful characters in text mode
Package: wnpp The current maintainer of toilet, Sam Hocevar , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: toilet Binary: toilet, toilet-fonts Version: 0.3-1.3 Maintainer: Sam Hocevar Build-Depends: debhelper (>= 5.0), pkg-config, libcaca-dev (>= 0.99.beta18), zlib1g-dev, autotools-dev Architecture: any all Standards-Version: 3.9.3 Format: 3.0 (quilt) Files: df4a4353207597e5dc1996f331f17204 1907 toilet_0.3-1.3.dsc 9b72591cb22a30c42a3184b17cabca6f 864880 toilet_0.3.orig.tar.gz ccb48027e0dbd3b483784bfcf7b166a8 3440 toilet_0.3-1.3.debian.tar.xz Vcs-Browser: http://svn.debian.org/wsvn/sam-hocevar/pkg-misc/unstable/toilet/ Vcs-Svn: svn://svn.debian.org/sam-hocevar/pkg-misc/unstable/toilet Checksums-Sha256: a780abc711b6e7a9fe1f758f049b00ce35b542e39edc4af8017875bc2df2d83f 1907 toilet_0.3-1.3.dsc 89d4b530c394313cc3f3a4e07a7394fa82a6091f44df44dfcd0ebcb3300a81de 864880 toilet_0.3.orig.tar.gz 18a7abb885ac16a23e136f4a73ae8ce0841a5ad6d0bd42eb8b0e908e1d9fbd50 3440 toilet_0.3-1.3.debian.tar.xz Package-List: toilet deb text optional arch=any toilet-fonts deb text optional arch=all Directory: pool/main/t/toilet Priority: source Section: text -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011571: O: rinetd -- Internet TCP redirection server
Package: wnpp The current maintainer of rinetd, Sam Hocevar , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: rinetd Binary: rinetd Version: 0.62.1sam-1.1 Maintainer: Sam Hocevar Build-Depends: debhelper (>= 9.0), dh-autoreconf Architecture: any Standards-Version: 3.9.6 Format: 3.0 (quilt) Files: 2848490a1633f63ed987cb3f53843499 1715 rinetd_0.62.1sam-1.1.dsc 9bfd549eda816d7ca05ef33d1db663c7 115120 rinetd_0.62.1sam.orig.tar.gz 69ea4a30e05002b7717e8cb53e2aa0aa 4024 rinetd_0.62.1sam-1.1.debian.tar.xz Checksums-Sha256: 72a4e225232ad1e7847dcf2ba10e685a1295a5572efbdcac4bd3da3fb9d90c3e 1715 rinetd_0.62.1sam-1.1.dsc fd04fd75d0035349c6210957d1cf964c22e8daac58f96e4e7cdbc3d4795699fb 115120 rinetd_0.62.1sam.orig.tar.gz 8382179cfcaad05283de1b729e2662d3cc2548a2f4942f5d2a6d79690b970083 4024 rinetd_0.62.1sam-1.1.debian.tar.xz Package-List: rinetd deb net optional arch=any Directory: pool/main/r/rinetd Priority: source Section: net Package: rinetd Version: 0.62.1sam-1.1 Installed-Size: 73 Maintainer: Sam Hocevar Architecture: amd64 Depends: libc6 (>= 2.15) Description-en: Internet TCP redirection server rinetd redirects TCP connections from one IP address and port to another, with basic IP-based access control. . rinetd is a single-process server which handles any number of connections to the address/port pairs specified in the file /etc/rinetd.conf. Since rinetd runs as a single process using nonblocking I/O, it is able to redirect a large number of connections without a severe impact on the machine. This makes it practical to run services on machines inside an IP masquerading firewall. Description-md5: c779dc6fda8c28eb8fd8878f71d69c09 Tag: interface::daemon, network::server, network::service, role::program, use::proxying Section: net Priority: optional Filename: pool/main/r/rinetd/rinetd_0.62.1sam-1.1_amd64.deb Size: 22236 MD5sum: 6f7740540f0f94422188f7d8608fec29 SHA256: ea7462047c7b3fa7e694bbfebb5f3832af6201947ec35d9bba4c61cd9756a552 -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011568: O: gtkgl2 -- OpenGL context support for GTK+ (development files)
Package: wnpp The current maintainer of gtkgl2, Sam Hocevar , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: gtkgl2 Binary: libgtkgl2.0-dev, libgtkgl2.0-1 Version: 2.1.0-0.3 Maintainer: Sam Hocevar Build-Depends: debhelper-compat (= 13), libgl-dev, libgtk2.0-dev Architecture: any Standards-Version: 4.5.0 Format: 3.0 (quilt) Files: ea16ab8c25f583dad61ed798ce006c2a 1904 gtkgl2_2.1.0-0.3.dsc 8d9c2008dff97c7ada0e416025ea0e79 57136 gtkgl2_2.1.0.orig.tar.xz 65919dcc6aa2b7a5de6929753bae5b5a 6740 gtkgl2_2.1.0-0.3.debian.tar.xz Checksums-Sha256: 7fabb978b746e69f002575cb67cc836e987478a1a69dfce70b4417b7a33aee52 1904 gtkgl2_2.1.0-0.3.dsc 8a4aa97b39fdefdf6d9f133afbecb9c198acf467da8de4a5eb04727a59965c1a 57136 gtkgl2_2.1.0.orig.tar.xz 0f62424a248d619bf5835e12e25f4bdb4753166977251dae290533b9fff19164 6740 gtkgl2_2.1.0-0.3.debian.tar.xz Homepage: http://www.mono-project.com/GtkGLArea Package-List: libgtkgl2.0-1 deb libs optional arch=any libgtkgl2.0-dev deb libdevel optional arch=any Testsuite: autopkgtest Testsuite-Triggers: gcc, pkg-config, xauth, xvfb Directory: pool/main/g/gtkgl2 Priority: source Section: libs -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011569: O: elk -- scheme interpreter
Package: wnpp The current maintainer of elk, Sam Hocevar , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: elk Binary: elk, libelk0, libelk0-dev, elkdoc Version: 3.99.8-4.2 Maintainer: Sam Hocevar Build-Depends: debhelper (>= 9.0), dh-autoreconf, groff, libelf-dev, libx11-dev, libxext-dev, libxmu-dev, libxt-dev, libice-dev, libsm-dev, libmotif-dev, libgdbm-dev, libxaw7-dev Architecture: any all Standards-Version: 3.9.6 Format: 3.0 (quilt) Files: cd8714fe75a00a8041ca911732d0cb2b 2086 elk_3.99.8-4.2.dsc 1e929fc5159dcb81d1c747f2351a6a19 879908 elk_3.99.8.orig.tar.gz 460e84869f4cffd3ad86685a60c70c3c 8156 elk_3.99.8-4.2.debian.tar.xz Vcs-Browser: https://salsa.debian.org/debian/elk Vcs-Git: https://salsa.debian.org/debian/elk.git Checksums-Sha256: 19fcee63132a88837e12e13e66b14bdd600a5428fd1e0e316f782e376b53e287 2086 elk_3.99.8-4.2.dsc 1db2b6b92a693b056c597aaf5cddc617a640bd6b24a218a725286d7490117cf9 879908 elk_3.99.8.orig.tar.gz afd4c595a19db8798f7afdde22c90fbf1a49df3574db1792da22f368d5fa5376 8156 elk_3.99.8-4.2.debian.tar.xz Homepage: http://sam.zoy.org/elk/ Package-List: elk deb interpreters optional arch=any elkdoc deb doc optional arch=all libelk0 deb libs optional arch=any libelk0-dev deb libdevel optional arch=any Directory: pool/main/e/elk Priority: source Section: lisp -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011570: O: libcaca -- development files for libcaca
Package: wnpp The current maintainer of libcaca, Sam Hocevar , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: libcaca Binary: libcaca-dev, libcaca0, caca-utils Version: 0.99.beta19-2.2 Maintainer: Sam Hocevar Build-Depends: debhelper (>= 8.1.3~), dh-autoreconf, pkg-config, libncursesw5-dev, libslang2-dev, libx11-dev, libimlib2-dev, freeglut3-dev, texlive-fonts-recommended, doxygen-latex Architecture: any Standards-Version: 3.9.3 Format: 3.0 (quilt) Files: cca202f9263a97fd8a5b0bc59da60e4b 2379 libcaca_0.99.beta19-2.2.dsc a3d4441cdef488099f4a92f4c6c1da00 1203495 libcaca_0.99.beta19.orig.tar.gz 20672594f1b274f7dfef1ac3ff7c758a 15020 libcaca_0.99.beta19-2.2.debian.tar.xz Vcs-Browser: http://svn.debian.org/wsvn/sam-hocevar/pkg-misc/unstable/libcaca/ Vcs-Svn: svn://svn.debian.org/sam-hocevar/pkg-misc/unstable/libcaca Checksums-Sha256: 104441468035910d534efea7cfb3f297ebbea634debf5fcb042101d6eb44e2bd 2379 libcaca_0.99.beta19-2.2.dsc 128b467c4ed03264c187405172a4e83049342cc8cc2f655f53a2d0ee9d3772f4 1203495 libcaca_0.99.beta19.orig.tar.gz 98eef7fc803224cbabc226f1e6488b25316f0b6282077db02d8cb490a5a919dc 15020 libcaca_0.99.beta19-2.2.debian.tar.xz Homepage: http://caca.zoy.org/wiki/libcaca Package-List: caca-utils deb utils optional arch=any libcaca-dev deb libdevel optional arch=any libcaca0 deb libs optional arch=any Testsuite: autopkgtest Testsuite-Triggers: build-essential, pkg-config Directory: pool/main/libc/libcaca Priority: source Section: libs -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for principles than to live up to them. signature.asc Description: PGP signature
Bug#1011567: android-framework-23: FTBFS with OpenJDK 17 due to com.sun.javadoc removal
Package: android-framework-23 Version: 6.0.1+r72-6 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 android-framework-23 fails to build with OpenJDK 17, Doclava no longer works due to the removal of the com.sun.javadoc API: :android:stubs Putting task artifact state for task ':android:stubs' into context took 0.013 secs. :uiautomator:processResources (Thread[Task worker for ':' Thread 2,5,main]) started. :uiautomator:processResources Putting task artifact state for task ':uiautomator:processResources' into context took 0.0 secs. Up-to-date check for task ':android:stubs' took 0.004 secs. It is not up-to-date because: No history is available. file or directory '/<>/debian/out/uiautomator/src/main/resources', not found Skipping task ':uiautomator:processResources' as it has no source files and no previous output files. :uiautomator:processResources NO-SOURCE :uiautomator:processResources (Thread[Task worker for ':' Thread 2,5,main]) completed. Took 0.011 secs. :uiautomator:debianMavenPom (Thread[Task worker for ':' Thread 2,5,main]) started. :uiautomator:debianMavenPom Putting task artifact state for task ':uiautomator:debianMavenPom' into context took 0.0 secs. file or directory '/<>/debian/out/android/src/forStubs/java', not found Up-to-date check for task ':uiautomator:debianMavenPom' took 0.001 secs. It is not up-to-date because: No history is available. Generating pom file /<>/debian/out/uiautomator/build/debian/uiautomator.pom :uiautomator:debianMavenPom (Thread[Task worker for ':' Thread 2,5,main]) completed. Took 0.104 secs. Loading the Maven rules... Passing through com.google.doclava:doclava:jar:debian Passing through com.google.guava:guava:jar:debian Passing through com.google.guava:guava-parent:jar:debian Passing through com.google.jsilver:jsilver:jar:debian Passing through org.antlr:antlr-runtime:jar:3.x Passing through org.antlr:antlr-master:jar:3.x Passing through org.ccil.cowan.tagsoup:tagsoup:jar:debian Passing through org.jsr-305:jsr305:jar:0.x Error: Unable to initialize main class com.google.doclava.Doclava Caused by: java.lang.NoClassDefFoundError: com/sun/javadoc/Doc :android:stubs FAILED :android:stubs (Thread[Task worker for ':',5,main]) completed. Took 0.478 secs. FAILURE: Build failed with an exception.
Bug#1011566: cglib: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests
Source: cglib Version: 3.2.12-1 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 cglib fails to build with OpenJDK 17, the tests make an illegal reflective access into java.base/java.lang: [INFO] --- [INFO] T E S T S [INFO] --- [INFO] Running net.sf.cglib.reflect.TestReflectPerf iteration count: 100 [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.046 s <<< FAILURE! - in net.sf.cglib.reflect.TestReflectPerf [ERROR] testReflectPerf(net.sf.cglib.reflect.TestReflectPerf) Time elapsed: 0.033 s <<< ERROR! java.lang.IllegalStateException: Unable to load cache item at net.sf.cglib.reflect.TestReflectPerf.testReflectPerf(TestReflectPerf.java:37) Caused by: java.lang.ExceptionInInitializerError at net.sf.cglib.reflect.TestReflectPerf.testReflectPerf(TestReflectPerf.java:37) Caused by: net.sf.cglib.core.CodeGenerationException: java.lang.reflect.InaccessibleObjectException-->Unable to make protected final java.lang.Class java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) throws java.lang.ClassFormatError accessible: module java.base does not "opens java.lang" to unnamed module @4cfaf581 at net.sf.cglib.reflect.TestReflectPerf.testReflectPerf(TestReflectPerf.java:37) Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make protected final java.lang.Class java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) throws java.lang.ClassFormatError accessible: module java.base does not "opens java.lang" to unnamed module @4cfaf581 at net.sf.cglib.reflect.TestReflectPerf.testReflectPerf(TestReflectPerf.java:37)
Bug#1011563: O: ftgl -- development files for libftgl
Package: wnpp The current maintainer of ftgl, Sam Hocevar , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: ftgl Binary: libftgl-dev, libftgl2 Version: 2.4.0-2.1 Maintainer: Sam Hocevar Uploaders: Manuel A. Fernandez Montecelo Build-Depends: debhelper (>= 11~), freeglut3-dev, libgl1-mesa-dev | libgl-dev, libglu1-mesa-dev | libglu-dev, libfreetype6-dev (>> 2.0.9), libcppunit-dev, doxygen-latex, ghostscript, imagemagick, pkg-config, texlive-fonts-recommended Architecture: any Standards-Version: 4.2.1 Format: 3.0 (quilt) Files: 82eafe9657162d8db1721bde68e60a22 2110 ftgl_2.4.0-2.1.dsc d040f3e78f34f5ebd1db2d2fd5c25501 529408 ftgl_2.4.0.orig.tar.xz a689c11e1d7c8e9b97168c3a67d48d1c 9236 ftgl_2.4.0-2.1.debian.tar.xz Vcs-Browser: https://salsa.debian.org/ftgl-team/ftgl Vcs-Git: https://salsa.debian.org/ftgl-team/ftgl.git Checksums-Sha256: d2e7044812b978d5e20ab9e0d0761e49a244744843617d57d78c95610aa2d19b 2110 ftgl_2.4.0-2.1.dsc e3e07a4b4aa5db98d69c621887001dc21b0cfce607868c0e0e4e37bcc7558676 529408 ftgl_2.4.0.orig.tar.xz 9f0151ea6dcc4913fd217a9425f4917dc765743feb960e90a4b4ba5891d9b1aa 9236 ftgl_2.4.0-2.1.debian.tar.xz Homepage: https://github.com/frankheckenbach/ftgl Package-List: libftgl-dev deb libdevel optional arch=any libftgl2 deb libs optional arch=any Directory: pool/main/f/ftgl Priority: source Section: devel
Bug#1011565: O: clif -- C language interpreter
Package: wnpp The current maintainer of clif, Sam Hocevar , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: clif Binary: clif Version: 0.93-9.1 Maintainer: Sam Hocevar Build-Depends: debhelper (>= 5.0), libx11-dev, libxt-dev, texlive, libelf-dev Architecture: any Standards-Version: 3.8.3 Format: 3.0 (quilt) Files: e1b991c0998d69291315a0c216d36eff 1318 clif_0.93-9.1.dsc a8df47654860fb1fcf6833c716b2a3ee 537384 clif_0.93.orig.tar.gz 6025625e75e3ea058e9ba048551c7c77 19564 clif_0.93-9.1.debian.tar.xz Checksums-Sha256: 97b90f942e06da1e4afc00eb67ca70ea4fe353f2b435bbeedf7a20b259fbc24c 1318 clif_0.93-9.1.dsc e15075c1279cf2f85de27ae599f0fee2a4f11737ea96a26c055660662f15be69 537384 clif_0.93.orig.tar.gz 547a58c0cbcd2f6505a027aa35aac1debd37a2fcc99fc4cb96fc61feee8758f5 19564 clif_0.93-9.1.debian.tar.xz Package-List: clif deb interpreters optional arch=any Directory: pool/main/c/clif Priority: source Section: interpreters Package: clif Source: clif (0.93-9.1) Version: 0.93-9.1+b1 Installed-Size: 1424 Maintainer: Sam Hocevar Architecture: amd64 Depends: libc6 (>= 2.14), libelf1 (>= 0.131), libx11-6 Description-en: C language interpreter Clif, a C-like Interpreter Framework, is and open-ended system for fast development of programs with C syntax. The program is compiled and if syntactically correct, code is immediately generated. The code is generated for a virtual machine. The virtual machine is a part of the framework. Description-md5: 9a25d6e0da8cf54ff392b50fd5fa344a Tag: devel::interpreter, devel::lang:c, devel::library, implemented-in::c, interface::commandline, role::devel-lib, role::program, scope::utility, works-with::software:source Section: interpreters Priority: optional Filename: pool/main/c/clif/clif_0.93-9.1+b1_amd64.deb Size: 1199388 MD5sum: 6505ca9064b4c886482941e6c7e79ed8 SHA256: ba9165674b72ffa1e49fb581c5357137d83aa98a662c6ebd8af7dbddd870e1b2
Bug#1011564: O: bvi -- binary file editor
Package: wnpp The current maintainer of bvi, Sam Hocevar , is apparently not active anymore. Therefore, I orphan this package now. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see https://www.debian.org/devel/wnpp/#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: bvi Binary: bvi Version: 1.4.0-1 Maintainer: Sam Hocevar Build-Depends: debhelper (>= 9.0), dh-autoreconf, libncurses5-dev Architecture: any Standards-Version: 3.9.6 Format: 3.0 (quilt) Files: c456c5e02f8194f01c1e66843f81a3d9 1777 bvi_1.4.0-1.dsc aa83eb8b2b6b0bb6cdd8e6beef12b775 139202 bvi_1.4.0.orig.tar.gz b4fa29bdabcd64c12c0b36603097d55a 2676 bvi_1.4.0-1.debian.tar.xz Vcs-Browser: http://svn.debian.org/wsvn/sam-hocevar/pkg-misc/unstable/bvi/ Vcs-Svn: svn://svn.debian.org/svn/sam-hocevar/pkg-misc/unstable/bvi Checksums-Sha256: 300b714e2cfb233c31333ee4da79ae37d00ee72c965f5833b42f5dc0f57e0bb0 1777 bvi_1.4.0-1.dsc 015a3c2832c7c097d98a5527deef882119546287ba8f2a70c736227d764ef802 139202 bvi_1.4.0.orig.tar.gz 959c7e0ff5e09a0e892e51fee2a157e3a61fff0cb185f8398dacfdcdc8cfbb85 2676 bvi_1.4.0-1.debian.tar.xz Package-List: bvi deb editors optional arch=any Directory: pool/main/b/bvi Priority: source Section: editors Package: bvi Source: bvi (1.4.0-1) Version: 1.4.0-1+b3 Installed-Size: 275 Maintainer: Sam Hocevar Architecture: amd64 Depends: libc6 (>= 2.14), libncurses6 (>= 6), libtinfo6 (>= 6) Description-en: binary file editor The bvi is a display-oriented editor for binary files, based on the vi text editor. If you are familiar with vi, just start the editor and begin to edit! If you never heard about vi, maybe bvi is not the best choice for you. Description-md5: 82e028998d9812c24a56e1a511b425cd Tag: interface::text-mode, role::program, scope::utility, uitoolkit::ncurses, use::editing, works-with::file Section: editors Priority: optional Filename: pool/main/b/bvi/bvi_1.4.0-1+b3_amd64.deb Size: 58272 MD5sum: 5b4e2f002b9ac1bd2da075bc70c7eb7e SHA256: 1fe1c58c49b4a11c44f5b624eacd656a0a4756d68d29c9b6cb4d9cbb4f6f36de
Bug#1011562: openhft-chronicle-threads: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests
Source: openhft-chronicle-threads Version: 1.1.6-2 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 openhft-chronicle-threads fails to build with OpenJDK 17, the tests make illegal reflective accesses into java.base/java.lang: [INFO] --- [INFO] T E S T S [INFO] --- [INFO] Running net.openhft.chronicle.threads.EventGroupTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.048 s <<< FAILURE! - in net.openhft.chronicle.threads.EventGroupTest [ERROR] testSimpleEventGroupTest(net.openhft.chronicle.threads.EventGroupTest) Time elapsed: 0.017 s <<< ERROR! java.lang.ExceptionInInitializerError at net.openhft.chronicle.threads.EventGroupTest.testSimpleEventGroupTest(EventGroupTest.java:21) Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make field private java.lang.ThreadGroup java.lang.Thread.group accessible: module java.base does not "opens java.lang" to unnamed module @ 4cfaf581 at net.openhft.chronicle.threads.EventGroupTest.testSimpleEventGroupTest(EventGroupTest.java:21) [INFO] Running net.openhft.chronicle.threads.LightPauserTest Average time to unpark was 2 ns Average time to unpark was 3 ns Average time to unpark was 2 ns [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.141 s - in net.openhft.chronicle.threads.LightPauserTest [INFO] [INFO] Results: [INFO] [ERROR] Errors: [ERROR] EventGroupTest.testSimpleEventGroupTest:21 » ExceptionInInitializer [INFO] [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0 [INFO] [INFO] [INFO] BUILD FAILURE [INFO]
Bug#1011561: jnr-enxio: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests
Source: jnr-enxio Version: 0.32.3-2 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 jnr-enxio fails to build with OpenJDK 17, the tests make an illegal reflective access into java.base/java.io: [INFO] --- [INFO] T E S T S [INFO] --- [INFO] Running jnr.enxio.channels.NativeTest [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.057 s <<< FAILURE! - in jnr.enxio.channels.NativeTest [ERROR] closeThrowsOnNativeError(jnr.enxio.channels.NativeTest) Time elapsed: 0.007 s <<< ERROR! java.lang.reflect.InaccessibleObjectException: Unable to make field private int java.io.FileDescriptor.fd accessible: module java.base does not "opens java.io" to unnamed module @4cfaf581 at jnr.enxio.channels.NativeTest.closeThrowsOnNativeError(NativeTest.java:20) [INFO] [INFO] Results: [INFO] [ERROR] Errors: [ERROR] NativeTest.closeThrowsOnNativeError:20 » InaccessibleObject Unable to make fie... [INFO] [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 [INFO] [INFO] [INFO] BUILD FAILURE [INFO] This can be fixed by adding this parameter to debian/maven.properties: argLine=--add-opens java.base/java.io=ALL-UNNAMED
Bug#1011559: ITP: lcsync -- librecast file and data syncing tool
Package: wnpp Owner: Vagrant Cascadian Severity: wishlist * Package name: lcsync Version : 0.0 Upstream Author : Brett Sheffield * URL or Web page : https://librecast.net/lcsync.html * License : GPL-2, GPL-3 Description : librecast file and data syncing tool Kind of like an ipv6 multicast rsync tool. Initial packaging available at https://salsa.debian.org/vagrant/lcsync signature.asc Description: PGP signature
Bug#1011560: rxtx: FTBFS with OpenJDK 17 due to javadoc errors
Source: rxtx Version: 2.2pre2+dfsg1-2 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 rxtx fails to build with OpenJDK 17 due to a javadoc error. The javadoc should be removed from librxtx-java anyway. /usr/bin/make docs make[2]: Entering directory '/<>' mkdir api cd api && /usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc /<>/./src/gnu/io/CommDriver.java /<>/./src/gnu/io/CommPort.java /<>/./src/gnu/io/CommPortEnumerator.java /<>/./src/gnu/io/CommPortIdentifier.java /<>/./src/gnu/io/CommPortOwnershipListener.java /<>/./src/gnu/io/Configure.java /<>/./src/gnu/io/I2C.java /<>/./src/gnu/io/I2CPort.java /<>/./src/gnu/io/I2CPortEvent.java /<>/./src/gnu/io/I2CPortEventListener.java /<>/./src/gnu/io/LPRPort.java /<>/./src/gnu/io/N oSuchPortException.java /<>/./src/gnu/io/ParallelPort.java /<>/./src/gnu/io/ParallelPortEvent.java /<>/./src/gnu/io/ParallelPortEventListener.java /<>/./sr c/gnu/io/PortInUseException.java /<>/./src/gnu/io/RS485.java /<>/./src/gnu/io/RS485Port.java /<>/./src/gnu/io/RS485PortEvent.java /<>/./src/gnu/io/RS485Por tEventListener.java /<>/./src/gnu/io/RXTXCommDriver.java /<>/./src/gnu/io/RXTXPort.java /<>/./src/gnu/io/RXTXVersion.java /<>/./src/gnu/io/Raw.java /<>/./src/gnu/io/RawPort.java /<>/./src/gnu/io/RawPortEvent.java /<>/./src/gnu/io/RawPortEventListener.java /<>/./src/gnu/io/SerialPort.java /<>/./sr c/gnu/io/SerialPortEvent.java /<>/./src/gnu/io/SerialPortEventListener.java /<>/./src/gnu/io/UnSupportedLoggerException.java /<>/./src/gnu/io/UnsupportedCommOperationEx ception.java /<>/./src/gnu/io/Zystem.java Loading source file /<>/./src/gnu/io/CommDriver.java... Loading source file /<>/./src/gnu/io/CommPort.java... Loading source file /<>/./src/gnu/io/CommPortEnumerator.java... Loading source file /<>/./src/gnu/io/CommPortIdentifier.java... Loading source file /<>/./src/gnu/io/CommPortOwnershipListener.java... Loading source file /<>/./src/gnu/io/Configure.java... Loading source file /<>/./src/gnu/io/I2C.java... Loading source file /<>/./src/gnu/io/I2CPort.java... Loading source file /<>/./src/gnu/io/I2CPortEvent.java... Loading source file /<>/./src/gnu/io/I2CPortEventListener.java... Loading source file /<>/./src/gnu/io/LPRPort.java... /<>/./src/gnu/io/LPRPort.java:375: error: invalid use of a restricted identifier 'yield' yield(); ^ (to invoke a method called yield, qualify the yield with a receiver or type name) Loading source file /<>/./src/gnu/io/NoSuchPortException.java... Loading source file /<>/./src/gnu/io/ParallelPort.java... Loading source file /<>/./src/gnu/io/ParallelPortEvent.java... Loading source file /<>/./src/gnu/io/ParallelPortEventListener.java... Loading source file /<>/./src/gnu/io/PortInUseException.java... Loading source file /<>/./src/gnu/io/RS485.java... Loading source file /<>/./src/gnu/io/RS485Port.java... Loading source file /<>/./src/gnu/io/RS485PortEvent.java... Loading source file /<>/./src/gnu/io/RS485PortEventListener.java... Loading source file /<>/./src/gnu/io/RXTXCommDriver.java... Loading source file /<>/./src/gnu/io/RXTXPort.java... Loading source file /<>/./src/gnu/io/RXTXVersion.java... Loading source file /<>/./src/gnu/io/Raw.java... Loading source file /<>/./src/gnu/io/RawPort.java... Loading source file /<>/./src/gnu/io/RawPortEvent.java... Loading source file /<>/./src/gnu/io/RawPortEventListener.java... Loading source file /<>/./src/gnu/io/SerialPort.java... Loading source file /<>/./src/gnu/io/SerialPortEvent.java... Loading source file /<>/./src/gnu/io/SerialPortEventListener.java... Loading source file /<>/./src/gnu/io/UnSupportedLoggerException.java... Loading source file /<>/./src/gnu/io/UnsupportedCommOperationException.java... Loading source file /<>/./src/gnu/io/Zystem.java... 1 error make[2]: *** [Makefile:871: docs] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:3: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Bug#1011413: inn2: nnrpd as distributed does not support $modify_headers, recompiled does
On May 22, Marc SCHAEFER wrote: > Package: inn2 > Version: 2.6.3-1+deb10u2 Sorry, I have no plans to spend time debugging oldstable but please let me know if this affects stable too. -- ciao, Marco signature.asc Description: PGP signature
Bug#1011558: extrepo: configuration set to bookworm even when installed on sid
Package: extrepo Version: 0.10 Severity: normal The default /etc/extrepo/config/yaml sets "version: bookworm", even when installed on sid, so newer entries to the repo list aren't available. Setting "version: sid" makes them available - shouldn't this be the default for the sid version of the package? -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-2-amd64 (SMP w/4 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 extrepo depends on: ii gpgv 2.2.35-2 ii libcryptx-perl0.076-1+b1 ii libdpkg-perl 1.21.7 ii libwww-perl 6.66-1 ii libyaml-libyaml-perl 0.83+ds-1+b1 ii perl 5.34.0-4 Versions of packages extrepo recommends: ii apt [apt-transport-https] 2.5.0 extrepo suggests no packages. -- Configuration Files: /etc/extrepo/config.yaml changed [not included] -- no debconf information
Bug#994944: libgtk-4-bin: gtk4-broadwayd not available
Hello Debian, Someone in Debian can take a look for this bug or it will be never fixed ? I'm very interested to use Cambalache and you had the good idea to disable this backend. Thanks,
Bug#1011542: Assist in Development of Patch for Bug 1011542 - Missing phy-gmii-sel.ko Module in Debian Bullseye Installer for Armhf
On 2022-05-24, David Kaiser wrote: > I am interested in assisting in the development and testing of a patch > for this bug report. Thanks for looking into this! > I am assuming that the patch may be very simple; > e.g., simply editing a list of included module names. Probably just adding phy-gmii-sel to installer/modules/armhf-armmp/nic-modules or installer/modules/armhf-armmp/kernel-image in the linux kernel package: https://salsa.debian.org/kernel-team/linux Building the kernel package can definitely be very time consuming and a little unusual as packages go, but you should be able to cross-build it on an amd64 machine... Sounds like you'll also want to get this added into bullseye's kernel, though normally the process is to first get it fixed in unstable, and then backport the fix to stable. > I will need some direction as to where to begin looking for the > relevant patch source repository and source file. Getting your custom kernel into a custom-built installer image is a little trickier... live well, vagrant signature.asc Description: PGP signature
Bug#1011557: ITP: pagmo -- library for massively parallel optimisation
Package: wnpp Severity: wishlist Owner: Pierre Gruet User: debian-scie...@lists.debian.org Usertags: field..science X-Debbugs-Cc: debian-de...@lists.debian.org, debian-scie...@lists.debian.org * Package name: pagmo Version : 2.18.0 Upstream Author : Francesco Biscani * URL : https://github.com/esa2/pagmo * License : GPL-3+ or LGPL-3+ Programming Lang: C++ Description : library for massively parallel optimisation pagmo is a C++ scientific library built around the idea of providing an unified interface to optimization algorithms and to optimization problems and to make their deployment in massively parallel environments easy. This package is needed as a dependency of openturns, which is maintained in the Debian science team -- which I also plan to do with pagmo.
Bug#1011556: dh-octave: provide dh-sequence-octave virtual package, dh_auto_install to debian/tmp
Package: dh-octave
Severity: wishlist
Tags: patch
Hello.
The attached suggestions may simplify the use of dh-octave, especially
for source packages building several binary packages.
>From 8f56b92d51e122a8c50e12c0c14da0c37bba6acb Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez
Date: Tue, 24 May 2022 21:13:45 +0200
Subject: [PATCH 1/4] d/control: let dh-octave provide dh-sequence-octave
Debhelper recognizes this special formal packages in Build-Depends and
adds --with=octave to the dh parameters.
This is quite convenient when the dependency is restricted to
architecture-independent builds or by profiles. In such scenarios,
several non-trivial conditionals can be avoided in debian/rules.
---
debian/control | 1 +
1 file changed, 1 insertion(+)
diff --git a/debian/control b/debian/control
index 8cc3d4a..280752f 100644
--- a/debian/control
+++ b/debian/control
@@ -16,6 +16,7 @@ Vcs-Git: https://salsa.debian.org/pkg-octave-team/dh-octave.git
Rules-Requires-Root: no
Package: dh-octave
+Provides: dh-sequence-octave
Architecture: all
Depends: octave-dev,
debhelper-compat (= 13),
--
2.30.2
>From e67ffe5ff0858c3722e8c100bd71b1ffed975b09 Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez
Date: Tue, 24 May 2022 22:13:54 +0200
Subject: [PATCH 2/4] =?UTF-8?q?install-pkg.m:=20implement=20non-octave=20p?=
=?UTF-8?q?arts=20with=20perl=E2=80=99s=20Dh=5FLib?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
The effect should be equivalent, with a slight improvement when
debhelper verbose option is enabled.
---
buildsystem.pm | 22 +-
install-pkg.m | 23 +--
2 files changed, 22 insertions(+), 23 deletions(-)
diff --git a/buildsystem.pm b/buildsystem.pm
index 974b275..ffd3dab 100644
--- a/buildsystem.pm
+++ b/buildsystem.pm
@@ -10,13 +10,33 @@ sub DESCRIPTION {
sub install {
my $this = shift;
+my $destdir = "debian/" . sourcepackage();
+my $arch = dpkg_architecture_value("DEB_HOST_MULTIARCH");
+my $mpath = "$destdir/usr/share/octave/packages";
+my $bpath = "$destdir/usr/lib/$arch/octave/packages";
+
$this->doit_in_sourcedir ("octave",
"--no-gui",
"--no-history",
"--silent",
"--no-init-file",
"--no-window-system",
- "/usr/share/dh-octave/install-pkg.m")
+ "/usr/share/dh-octave/install-pkg.m",
+ $mpath, $bpath);
+
+doit ("rmdir", "--ignore-fail-on-non-empty", "-p", "$mpath", "$bpath");
+
+# Remove unnecessary documentation files
+doit ("rm", "-fr", "$mpath/*/doc");
+doit ("rm", "-f", "$mpath/*/packinfo/COPYING");
+
+# Fix permission of installed *.oct and *.mex files, as per FHS 3.0
+# sections 4.6 and 4.7 (see Bug#954149)
+doit ("chmod", "-x", "$bpath/*/*/*.oct");
+doit ("chmod", "-x", "$bpath/*/*/*.mex");
+
+# Remove left over files *-tst
+doit ("rm", "-f", "$bpath/*/*/*-tst");
}
sub clean {
diff --git a/install-pkg.m b/install-pkg.m
index 0a343ad..d586c13 100644
--- a/install-pkg.m
+++ b/install-pkg.m
@@ -24,12 +24,7 @@ if (exist ("./PKG_ADD") == 2)
movefile ("PKG_ADD", "PKG_ADD.bak");
endif
-package = sysout ("grep ^Source: debian/control | cut -f2 -d\\ ");
-debpkg = [pwd(), "/debian/", package];
-mpath = [debpkg, "/usr/share/octave/packages"];
-arch = sysout ("dpkg-architecture -qDEB_HOST_MULTIARCH");
-bpath = [debpkg, "/usr/lib/", arch, "/octave/packages"];
-pkg ("prefix", mpath, bpath);
+pkg ("prefix", argv(){1}, argv(){2});
pkg ("local_list", fullfile (pwd (), "local-list"));
pkg ("global_list", fullfile (pwd (), "global-list"));
@@ -41,19 +36,3 @@ if (exist ("PKG_ADD.bak") == 2)
endif
pkg -verbose -nodeps install .
-
-system (sprintf ("rmdir --ignore-fail-on-non-empty -p %s %s",
- mpath, bpath));
-
-### Remove unnecessary documentation files
-pkgdir = "debian/*/usr/share/octave/packages/*";
-system (sprintf ("rm -rf %s/doc", pkgdir));
-system (sprintf ("rm -f %s/packinfo/COPYING", pkgdir));
-
-### Fix permission of installed *.oct and *.mex files, as per FHS 3.0
-### sections 4.6 and 4.7 (see Bug#954149)
-system ("chmod -x debian/*/usr/lib/*/octave/packages/*/*/*.oct");
-system ("chmod -x debian/*/usr/lib/*/octave/packages/*/*/*.mex");
-
-### Remove left over files *-tst
-system ("rm -f debian/*/usr/lib/*/octave/packages/*/*/*-tst");
--
2.30.2
>From 215fc37d39001e56833b20e80a7c23bc0511af16 Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez
Date: Tue, 24 May 2022 22:17:02 +0200
Subject: [PATCH 3/4] =?UTF-8?q?buildsystem.pm:=20use=20debhelper=E2=80=99s?=
=?UTF-8?q?=20tmpdir=20instead=20of=20debian/sourcepackage?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
This change is intrusive, but may simplify source packages
Bug#1004971: pythonpy: diff for NMU version 0.4.11b-3.1
Sending the forgotten source debdiff... -- Pierre diff -Nru pythonpy-0.4.11b/debian/changelog pythonpy-0.4.11b/debian/changelog --- pythonpy-0.4.11b/debian/changelog 2016-05-20 22:29:58.0 +0200 +++ pythonpy-0.4.11b/debian/changelog 2022-05-24 20:37:28.0 +0200 @@ -1,3 +1,11 @@ +pythonpy (0.4.11b-3.1) unstable; urgency=medium + + * Non-maintainer upload. + * Importing Collections abstract classes from collections.abc +(Closes: #1004971, #1011468) + + -- Pierre Gruet Tue, 24 May 2022 20:37:28 +0200 + pythonpy (0.4.11b-3) unstable; urgency=medium * Avoid 'pycompleter' as a system-wide executable: diff -Nru pythonpy-0.4.11b/debian/patches/fix_collections_Python3_10.patch pythonpy-0.4.11b/debian/patches/fix_collections_Python3_10.patch --- pythonpy-0.4.11b/debian/patches/fix_collections_Python3_10.patch 1970-01-01 01:00:00.0 +0100 +++ pythonpy-0.4.11b/debian/patches/fix_collections_Python3_10.patch 2022-05-24 20:37:06.0 +0200 @@ -0,0 +1,18 @@ +Description: importing Collections abstract classes from collections.abs +Author: Pierre Gruet +Origin: upstream, https://bugs.launchpad.net/ubuntu/+source/pythonpy/+bug/1878935/comments/1 +Bug-Debian: https://bugs.debian.org/1004971 +Forwarded: not-needed +Last-Update: 2022-05-24 + +--- a/pythonpy/__main__.py b/pythonpy/__main__.py +@@ -13,7 +13,7 @@ + import argparse + import json + import re +-from collections import Iterable ++from collections.abc import Iterable + + try: + from . import __version__ diff -Nru pythonpy-0.4.11b/debian/patches/series pythonpy-0.4.11b/debian/patches/series --- pythonpy-0.4.11b/debian/patches/series 2016-05-20 22:29:58.0 +0200 +++ pythonpy-0.4.11b/debian/patches/series 2022-05-24 20:31:10.0 +0200 @@ -1,2 +1,3 @@ 0001-remove-entry-points-scripts.patch 0002-fix-bash-completion.patch +fix_collections_Python3_10.patch OpenPGP_signature Description: OpenPGP digital signature
Bug#1011555: libpicocontainer1-java: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests
Package: libpicocontainer1-java Version: 1.3-3 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 libpicocontainer1-java fails to build with OpenJDK 17, the tests make illegal reflective accesses into java.base/java.io: [INFO] Running org.picocontainer.defaults.ConstructorInjectionComponentAdapterTestCase [ERROR] Tests run: 24, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.122 s <<< FAILURE! - in org.picocontainer.defaults.ConstructorInjectionComponentAdapterTestCase [ERROR] testSER_isXStreamSerializableWithPureReflection(org.picocontainer.defaults.ConstructorInjectionComponentAdapterTestCase) Time elapsed: 0.114 s <<< ERROR! java.lang.ExceptionInInitializerError at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.instantiateUsingSerialization(PureJavaReflectionProvider.java:113) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.newInstance(PureJavaReflectionProvider.java:88) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.instantiateNewInstance(AbstractReflectionConverter.java:580) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.unmarshal(AbstractReflectionConverter.java:276) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:72) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1391) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1376) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1261) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1252) at org.picocontainer.tck.AbstractComponentAdapterTestCase.testSER_isXStreamSerializableWithPureReflection(AbstractComponentAdapterTestCase.java:241) 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) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at junit.framework.TestCase.runTest(TestCase.java:164) at org.jmock.core.VerifyingTestCase.runBare(VerifyingTestCase.java:39) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at jdk.internal.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:100) at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:140) at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:113) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345) at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418) Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make java.lang.Object java.io.ObjectStreamClass.newInstance() throws java.lang.InstantiationException,java.lang.reflect.InvocationTargetException,java.lang.UnsupportedOperationException accessible: module java.base does not "opens java.io" 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.Method.checkCanSetAccessible(Method.java:199) at
Bug#1011554: electric: FTBFS with OpenJDK 17 due to type inference changes
Source: electric Version: 9.07+dfsg-6 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 electric fails to build with Java 17: [javac] /<>/com/sun/electric/database/CellRevisionConn0.java:964: error: incompatible types: List cannot be converted to List [javac] return i < j ? new ImmutableArrayList(arcs, i, j) : Collections.emptyList(); [javac] ^
Bug#1011553: perfmark-java: FTBFS with OpenJDK 17 due to unsupported javac source/target level 6
Source: perfmark-java Version: 0.21.0+ds-2 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 perfmark-java 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. Compiling with JDK Java compiler API. error: Source option 6 is no longer supported. Use 7 or later. error: Target option 6 is no longer supported. Use 7 or later. :perfmark-api:compileJava FAILED :perfmark-api:compileJava (Thread[Task worker for ':' Thread 4,5,main]) completed. Took 0.411 secs.
Bug#997827: new version 056-3 available
Please check if this bug is fixed in the new version 056-3. The NEWS files says already for 052 - **plymouth:** install binaries with dependencies -- regards Thomas
Bug#1004971: pythonpy: diff for NMU version 0.4.11b-3.1
Control: tags 1004971 + patch Control: tags 1004971 + pending Control: tags 1009115 + patch Control: tags 1009115 + pending Dear maintainer, I've prepared an NMU for pythonpy (versioned as 0.4.11b-3.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should cancel it. Best, -- Pierre OpenPGP_signature Description: OpenPGP digital signature
Bug#1011552: ITP: python-exceptiongroup -- backport of the BaseExceptionGroup and ExceptionGroup classes from Python 3.11
Package: wnpp Severity: wishlist Owner: Agathe Porte X-Debbugs-Cc: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org, deb...@microjoe.org * Package name: python-exceptiongroup Version : 1.0.0~rc7 Upstream Author : Alex Grönholm * URL : https://github.com/agronholm/exceptiongroup * License : MIT + PSFLv2 Programming Lang: Python Description : backport of the BaseExceptionGroup and ExceptionGroup classes from Python 3.11 This library contains backport of BaseException for Python versions before 3.11. Since 3.11 is not released yet and that new software [1] is already using this compat layer, I think we should package it even in release-candidate form. [1] It is required for python-cattrs source package update. I intent to maintain this package under the umbrella of the Debian Python Team.
Bug#1011551: libjdom2-intellij-java: FTBFS with OpenJDK 17 due to unsupported javac source/target level 6
Package: libjdom2-intellij-java Version: 2.0.6+git20180529-2 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 libjdom2-intellij-java 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. Compiling with JDK Java compiler API. error: Source option 6 is no longer supported. Use 7 or later. error: Target option 6 is no longer supported. Use 7 or later. :core:compileJava FAILED :core:compileJava (Thread[Task worker for ':' Thread 7,5,main]) completed. Took 0.522 secs.
Bug#1011550: dom4j: FTBFS with OpenJDK 17 due to javadoc errors
Source: dom4j Version: 2.1.3-1 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 dom4j fails to build with OpenJDK 17 due to a javadoc error: :javadoc Putting task artifact state for task ':javadoc' into context took 0.0 secs. Up-to-date check for task ':javadoc' took 0.056 secs. It is not up-to-date because: No history is available. Starting process 'command '/usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc''. Working directory: /<> Command: /usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc @/<>/build/tmp/javadoc/javadoc.options Successfully started process 'command '/usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc'' /<>/src/main/java/org/dom4j/io/DOMSAXContentHandler.java:46: error: unexpected end tag: * ^
Bug#1011549: openrocket needs newer jogl
Package: libjogl2-java Version: 2.3.2+dfsg-9 I'm working on re-packaging openrocket so that it can go back into Debian main. A big part of the work is eliding all the embedded class library jar files and replacing those with Debian library packages. One of the class libraries is jogl, for which openrocket apparently needs jogl 2.4 with patches applied by Sibo: https://github.com/openrocket/openrocket/issues/1156 https://github.com/openrocket/openrocket/pull/1157 Is there any chance we could freshen the Debian package? I see that jogamp.org still shows 2.3.2 as the most recent "stable" release, but that's about 7 years old. I'm linking against the 2.3.2 package now, and the core of openrocket is working ok, but none of the 3d rendering features will work until we get to a fresher jogl version. Regards, Bdale signature.asc Description: PGP signature
Bug#1011542: Assist in Development of Patch for Bug 1011542 - Missing phy-gmii-sel.ko Module in Debian Bullseye Installer for Armhf
Hello, I am interested in assisting in the development and testing of a patch for this bug report. I am assuming that the patch may be very simple; e.g., simply editing a list of included module names. I will need some direction as to where to begin looking for the relevant patch source repository and source file. Thank you, Dave Kaiser
Bug#1011548: jameica-h2database: FTBFS with OpenJDK 17 due to com.sun.javadoc removal
Source: jameica-h2database
Version: 1.4.197-6
Severity: important
Tags: ftbfs sid bookworm
User: debian-j...@lists.debian.org
Usertags: default-java17
jameica-h2database fails to build with OpenJDK 17 because it uses classes from
the com.sun.javadoc package which was removed. The doclet is propably useless
and could be disabled.
Compiling 781 classes
src/tools/org/h2/build/doclet/Doclet.java:19: error: package com.sun.javadoc
does not exist
import com.sun.javadoc.ClassDoc;
^
src/tools/org/h2/build/doclet/Doclet.java:20: error: package com.sun.javadoc
does not exist
import com.sun.javadoc.ConstructorDoc;
^
src/tools/org/h2/build/doclet/Doclet.java:21: error: package com.sun.javadoc
does not exist
import com.sun.javadoc.ExecutableMemberDoc;
^
src/tools/org/h2/build/doclet/Doclet.java:22: error: package com.sun.javadoc
does not exist
import com.sun.javadoc.FieldDoc;
^
src/tools/org/h2/build/doclet/Doclet.java:23: error: package com.sun.javadoc
does not exist
import com.sun.javadoc.LanguageVersion;
^
src/tools/org/h2/build/doclet/Doclet.java:24: error: package com.sun.javadoc
does not exist
import com.sun.javadoc.MethodDoc;
^
src/tools/org/h2/build/doclet/Doclet.java:25: error: package com.sun.javadoc
does not exist
import com.sun.javadoc.ParamTag;
^
src/tools/org/h2/build/doclet/Doclet.java:26: error: package com.sun.javadoc
does not exist
import com.sun.javadoc.Parameter;
^
src/tools/org/h2/build/doclet/Doclet.java:27: error: package com.sun.javadoc
does not exist
import com.sun.javadoc.RootDoc;
^
src/tools/org/h2/build/doclet/Doclet.java:28: error: package com.sun.javadoc
does not exist
import com.sun.javadoc.Tag;
^
src/tools/org/h2/build/doclet/Doclet.java:29: error: package com.sun.javadoc
does not exist
import com.sun.javadoc.ThrowsTag;
^
src/tools/org/h2/build/doclet/Doclet.java:30: error: package com.sun.javadoc
does not exist
import com.sun.javadoc.Type;
^
src/tools/org/h2/build/doclet/Doclet.java:52: error: cannot find symbol
public static boolean start(RootDoc root) throws IOException {
^
symbol: class RootDoc
location: class Doclet
src/tools/org/h2/build/doclet/Doclet.java:56: error: cannot find symbol
private boolean startDoc(RootDoc root) throws IOException {
^
symbol: class RootDoc
location: class Doclet
src/tools/org/h2/build/doclet/Doclet.java:73: error: cannot find symbol
private static String getClass(ClassDoc clazz) {
^
symbol: class ClassDoc
location: class Doclet
src/tools/org/h2/build/doclet/Doclet.java:81: error: cannot find symbol
private void processClass(ClassDoc clazz) throws IOException {
^
symbol: class ClassDoc
location: class Doclet
src/tools/org/h2/build/doclet/Doclet.java:283: error: cannot find symbol
private void writeFieldDetails(PrintWriter writer, ClassDoc clazz,
^
symbol: class ClassDoc
location: class Doclet
src/tools/org/h2/build/doclet/Doclet.java:284: error: cannot find symbol
FieldDoc field) {
^
symbol: class FieldDoc
location: class Doclet
src/tools/org/h2/build/doclet/Doclet.java:307: error: cannot find symbol
private void writeMethodDetails(PrintWriter writer, ClassDoc clazz,
^
symbol: class ClassDoc
location: class Doclet
src/tools/org/h2/build/doclet/Doclet.java:308: error: cannot find symbol
ExecutableMemberDoc method, String signature) {
^
symbol: class ExecutableMemberDoc
location: class Doclet
src/tools/org/h2/build/doclet/Doclet.java:403: error: cannot find symbol
private static String getLink(ClassDoc clazz, int line) {
^
symbol: class ClassDoc
location: class Doclet
src/tools/org/h2/build/doclet/Doclet.java:412: error: cannot find symbol
private String getFieldLink(String text, String constant, ClassDoc clazz,
^
symbol: class ClassDoc
location: class Doclet
src/tools/org/h2/build/doclet/Doclet.java:442: error: cannot find symbol
private static boolean skipField(ClassDoc clazz, FieldDoc field) {
^
symbol: class ClassDoc
location: class Doclet
src/tools/org/h2/build/doclet/Doclet.java:442: error: cannot find symbol
private static boolean skipField(ClassDoc clazz, FieldDoc field) {
Bug#1011547: autopkgtest-build-lxc: need to set LANG=C.UTF-8 when calling lxc-create
Package: autopkgtest Version: 5.22 Severity: normal It turns out that the lxc containers built by autopkgtest-build-lxc depend on the LANG setting. An example of where this made a difference is below. Suggested patch: just add "export LANG=C.UTF-8" somewhere early in /usr/bin/autopkgtest-build-lxc Here's an example of where this caused an issue. I was trying to patch pymca. Version 5.7.1+dfsg-1 was in the archive and was recorded as passing its autopkgtests on ci.debian.net. But when I tried to run autopkgtest on it on my system (using an lxc container created with autopkgtest-build-lxc), it failed. The reason for this was that one of the Python test scripts effectively did the following: import locale current_locale = locale.getlocale() locale.setlocale(locale.LC_ALL, current_locale) Now, the autopkgtest script is run with LANG, LANGUAGE and LC_* all unset, so Python sets current_locale to the default, which would be C.UTF-8, except that this is translated into en_US.UTF-8. Then locale.setlocale() failed because I don't have the en_US.UTF-8 locale in my container: it was built with LANG=en_GB.UTF-8, so the only locale I had was this (and C.UTF-8). Presumably, therefore, the ci.debian.net containers were built with either LANG unset or set to C.UTF-8 or to en_US.UTF-8 (see line 128 onwards of /usr/share/lxc/templates/lxc-debian), so they ran this Python code with no difficulty, whereas I couldn't. A solution for this package was for the tests to depend on locales-all, but it just highlighted the sensitivity of the tests to the locale installed in the container. Best wishes, Julian
Bug#1011546: FTBFS: echo "You forgot to fix the VERSION in configure.ac!"
Source: tmpreaper Version: 1.6.16 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi! I'm afraid your package fails to build, with: dh_testdir ./tmpreaper -h 2>&1 | grep 'tmpreaper -- Version: '1.6.16-DEB || (echo "You forgot to fix the VERSION in configure.ac!"; exit 1) You forgot to fix the VERSION in configure.ac! make: *** [debian/rules:42: build-stamp] Error 1 Full log attached. Meow! -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (120, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-00017-g251fbd8b0fa2 (SMP w/64 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) sbuild (Debian sbuild) 0.83.1 (26 April 2022) on valinor.angband.pl +==+ | tmpreaper (amd64)Tue, 24 May 2022 16:01:14 + | +==+ Package: tmpreaper Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: binary I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-a7cddd52-2cb9-4f29-a54a-d58c611b5747' with '<>' I: NOTICE: Log filtering will replace 'build/tmpreaper-XX34zY/resolver-fy7iiL' with '<>' +--+ | Update chroot| +--+ Hit:1 http://apt-rosy.angband.pl:3142/debian unstable InRelease Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. +--+ | Fetch source files | +--+ Check APT - Checking available source versions... Download source files with APT -- Reading package lists... Need to get 160 kB of source archives. Get:1 http://apt-rosy.angband.pl:3142/debian unstable/main tmpreaper 1.6.16 (dsc) [1437 B] Get:2 http://apt-rosy.angband.pl:3142/debian unstable/main tmpreaper 1.6.16 (tar) [159 kB] Fetched 160 kB in 0s (475 kB/s) Download complete and in download only mode I: NOTICE: Log filtering will replace 'build/tmpreaper-XX34zY/tmpreaper-1.6.16' with '<>' I: NOTICE: Log filtering will replace 'build/tmpreaper-XX34zY' with '<>' +--+ | Install package build dependencies | +--+ Setup apt archive - Merged Build-Depends: debhelper (>= 5), e2fslibs-dev, po-debconf, libmount-dev, build-essential, fakeroot Filtered Build-Depends: debhelper (>= 5), e2fslibs-dev, po-debconf, libmount-dev, build-essential, fakeroot dpkg-deb: building package 'sbuild-build-depends-main-dummy' in '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. Ign:1 copy:/<>/apt_archive ./ InRelease Get:2 copy:/<>/apt_archive ./ Release [957 B] Ign:3 copy:/<>/apt_archive ./ Release.gpg Get:4 copy:/<>/apt_archive ./ Sources [387 B] Get:5 copy:/<>/apt_archive ./ Packages [470 B] Fetched 1814 B in 0s (129 kB/s) Reading package lists... Reading package lists... Install main build dependencies (apt-based resolver) Installing build dependencies Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: comerr-dev libblkid-dev libext2fs-dev libmount-dev libpcre2-16-0 libpcre2-32-0 libpcre2-dev libpcre2-posix3 libselinux1-dev libsepol-dev uuid-dev Suggested packages: doc-base The following NEW packages will be installed: comerr-dev libblkid-dev libext2fs-dev libmount-dev libpcre2-16-0 libpcre2-32-0 libpcre2-dev libpcre2-posix3 libselinux1-dev libsepol-dev sbuild-build-depends-main-dummy uuid-dev 0 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 2662 kB of archives. After this operation, 9079 kB of additional disk space will be used. Get:1 copy:/<>/apt_archive ./ sbuild-build-depends-main-dummy 0.invalid.0 [896 B] Get:2 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 comerr-dev amd64 2.1-1.46.5-2 [109 kB] Get:3 http://apt-rosy.angband.pl:3142/debian unstable/main amd64
Bug#1011343: WISHLIST: Offical ALL-IN-ONE images?
Hi, for now it looks like the merged ISO works as fat DVD-1. I installed a Debian 11.2.0 system from the merged DVD-1+ DVD-2 ISO in a qemu VM via option -cdrom. Installation went smoothly. During reboot i aborted the VM to next deface the El Torito boot sector of the ISO. I removed the -net options from the qemu start command, hopefully simulating a pulled network adapter. Then i booted from the virtual -hda, having the -cdrom present too. I removed from sources.list the deb and deb-src entries with http. ping debian.org gets no replies. So the network is effectively down, although ip addr shows some "ens3" with "altname enp0s3", which looks much like the "nnp5s0" of the host machine except that the latter has no "altname". To make sure that i can install stuff, i did as superuser dpkg -s apt-file dpkg -s lame dpkg -s xorriso which all three indicated that the packages are not yet installed. Then i tried to install them: # From pool of DVD-1 apt-get install apt-file # From pool of DVD-2 apt-get install lame # Not in the two DVD images apt-get install xorriso The first two succeeded and behaved as i know from apt-get. The third did not succeed, as expected. -- But apt-file update fails with E: The repository 'cdrom://[Debian GNU/Linux 11.2.0 _Bullseye_ - Official amd64 DVD Binary-1 20211218-11:13] bullseye Release' does not have a Release file N: Update [...] can't be done securely [...] disabled by default. N: See apt-secure(8) [...] Suspecting a flaw with my merge procedure, i booted with the original DVD-1 ISO as -cdrom. I had to run apt-cdrom add before the repo was accepted (i'm riddling a lot) but then i could prove that it works by apt-get install needrestart which is on DVD-1. Nevertheless apt-file update tells the same "E:" and "N:" lines. So the shortcomming seems already to be in DVD-1. Anything known about it ? (I learned that it was not necessary to deface El torito on DVD-1+2. DVD-1 with El Torito at -cdrom does not keep -hda from booting.) -- What shall i further test to challenge the merged ISO whether it has any shorcommings compared to the original DVD-1 ? Have a nice day :) Thomas
Bug#1011545: please version the Conflicts: with gitsome
Package: gh Version: 2.4.0+dfsg1-2 Severity: serious I have fixed gitsome so that it doesn't ship a /usr/bin/gh binary in gitsome/0.8.0+ds-7.1 (which closed #1005858). Please fix the Conflicts: so that it is versioned << 0.8.0+ds-7.1. This is marked as "serious" because I believe that conflicting with an unrelated package is a policy violation. I understand this is somewhat open to interpretation, but since this package has been added to the blocking hints anyways, I figured it was better to file an RC bug, remove the hint, and fix this, than keeping things kind of hidden the way they are now. :) -- System Information: Debian Release: 11.3 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), (1, 'unstable'), (1, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-14-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.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 gh depends on: ii libc6 2.31-13+deb11u3 gh recommends no packages. gh suggests no packages.
Bug#1011544: uncommons-maths: FTBFS with OpenJDK 17 due to unsupported javac source/target level 6
Source: uncommons-maths Version: 1.2.3-2 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 uncommons-maths 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. :compileJava Putting task artifact state for task ':compileJava' into context took 0.0 secs. file or directory '/<>/debian/src/main/java', not found file or directory '/<>/debian/src/main/java', not found Up-to-date check for task ':compileJava' took 0.018 secs. It is not up-to-date because: No history is available. All input files are considered out-of-date for incremental task ':compileJava'. file or directory '/<>/debian/src/main/java', not found Compiling with JDK Java compiler API. error: Source option 6 is no longer supported. Use 7 or later. error: Target option 6 is no longer supported. Use 7 or later. :compileJava FAILED :compileJava (Thread[Task worker for ':' Thread 2,5,main]) completed. Took 0.23 secs. FAILURE: Build failed with an exception.
Bug#1011543: libobject-cloner-java: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests
Source: libobject-cloner-java Version: 0.2~git95dba2c-2 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 libobject-cloner-java fails to builds with OpenJDK 17, a test case makes an illegal reflective access and triggers an error: [INFO] --- [INFO] T E S T S [INFO] --- [INFO] Running org.kamranzafar.commons.cloner.ObjectClonerTest [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.034 s <<< FAILURE! - in org.kamranzafar.commons.cloner.ObjectClonerTest [ERROR] deepClone(org.kamranzafar.commons.cloner.ObjectClonerTest) Time elapsed: 0.009 s <<< ERROR! java.lang.reflect.InaccessibleObjectException: Unable to make field private final byte[] java.lang.String.value accessible: module java.base does not "opens java.lang" to unnamed module @4cfaf581 at org.kamranzafar.commons.cloner.ObjectClonerTest.deepClone(ObjectClonerTest.java:56) [INFO] [INFO] Results: [INFO] [ERROR] Errors: [ERROR] ObjectClonerTest.deepClone:56 » InaccessibleObject Unable to make field privat... [INFO] [ERROR] Tests run: 2, Failures: 0, Errors: 1, Skipped: 0 [INFO] [INFO] [INFO] BUILD FAILURE [INFO] This can be fixed by adding this parameter to debian/maven.properties: argLine=--add-opens java.base/java.lang=ALL-UNNAMED
Bug#1011542: installation-reports: Armhf Installer Missing phy-gmii-sel.ko Module Required on BeagleBone Black
Package: installation-reports Severity: important Tags: d-i X-Debbugs-Cc: dwkai...@hotmail.com, vagr...@debian.org (Please provide enough information to help the Debian maintainers evaluate the report efficiently - e.g., by filling in the sections below.) Boot method: SD-Card Image Image version: http://ftp.debian.org/debian/dists/bullseye/main/installer-armhf/20210731+deb11u3/images/netboot/SD-Card-images/ 2022-03-22 [firmware.BeagleBoneBlack.img + partition.img] Date: May 22, 2022 Machine: Circuitco BeagleBone Black, Rev C Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [ ] Detect media: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: The d-i program fails to identify the network card and, therefore, cannot complete. I can resolve this issue by manually editting the initrd.gz image, provided by the default installer, and appending the drivers/phy/ti/phy-gmii-sel.ko module from linux-image-5.10.0-13-armmp. This same issue has been validated in each Bullseye release prior to Update 3, and in the previous major release. Please make sure that any installation logs that you think would be useful are attached to this report. Please compress large files using gzip. -- Package-specific info: == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="11 (bullseye) - installer build 20210731+deb11u3" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux BBBlack 5.10.0-13-armmp #1 SMP Debian 5.10.106-1 (2022-03-17) armv7l GNU/Linux lsmod: Module Size Used by lsmod: fuse 122880 0 lsmod: dm_mod114688 0 lsmod: md_mod147456 0 lsmod: jfs 180224 0 lsmod: btrfs1339392 0 lsmod: libcrc32c 16384 1 btrfs lsmod: xor16384 1 btrfs lsmod: xor_neon 16384 1 xor lsmod: raid6_pq 106496 1 btrfs lsmod: vfat 24576 0 lsmod: fat69632 1 vfat lsmod: ext4 729088 2 lsmod: crc16 16384 1 ext4 lsmod: mbcache16384 1 ext4 lsmod: jbd2 114688 1 ext4 lsmod: crc32c_generic 16384 4 lsmod: usb_storage57344 0 lsmod: scsi_mod 196608 1 usb_storage lsmod: sdhci_omap 24576 0 lsmod: sdhci_pltfm16384 1 sdhci_omap lsmod: sdhci 61440 2 sdhci_pltfm,sdhci_omap lsmod: smsc 16384 1 lsmod: phy_gmii_sel 20480 1 lsmod: davinci_mdio 16384 0 lsmod: ti_cpsw73728 0 lsmod: cpts 24576 1 ti_cpsw lsmod: cpsw_common16384 1 ti_cpsw lsmod: ptp24576 1 cpts lsmod: pps_core 24576 1 ptp lsmod: omap_rng 16384 0 lsmod: rng_core 20480 1 omap_rng lsmod: musb_dsps 24576 0 lsmod: musb_hdrc 131072 1 musb_dsps lsmod: udc_core 45056 1 musb_hdrc lsmod: usbcore 225280 2 usb_storage,musb_hdrc lsmod: phy_am335x 16384 9 lsmod: phy_generic20480 1 phy_am335x lsmod: phy_am335x_control 16384 1 phy_am335x lsmod: leds_gpio 16384 0 df: Filesystem 1K-blocks Used Available Use% Mounted on df: tmpfs4995260 49892 0% /run df: devtmpfs229472 0229472 0% /dev df: /dev/mmcblk0p229527944 2900368 25102280 10% /target df: /dev/mmcblk0p1 480618 61220394464 13% /target/boot df: /dev/mmcblk0p229527944 2900368 25102280 10% /dev/.static/dev df: devtmpfs229472 0229472 0% /target/dev free: totalusedfree shared buff/cache available free: Mem: 499500 68996 194436 65580 236068 374060 free: Swap:487420 62208 425212 /proc/cmdline: console=ttyO0,115200n8 /proc/cpuinfo: processor: 0 /proc/cpuinfo: model name : ARMv7 Processor rev 2 (v7l) /proc/cpuinfo: BogoMIPS : 995.32 /proc/cpuinfo: Features : half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpd32 /proc/cpuinfo: CPU implementer : 0x41 /proc/cpuinfo: CPU architecture: 7 /proc/cpuinfo: CPU variant : 0x3 /proc/cpuinfo: CPU part : 0xc08 /proc/cpuinfo:
Bug#1011174: marked as pending in controlsfx
Hi Tony, Sorry for that, there are so many Java packages and so few maintainers that we rarely have concurrency issues and I'm not used to check the ownership of the bugs. I assumed you were working on netty following your comment on #1011135 yesterday, and I picked controlsfx instead. I'll try to be more careful. I hope you'll be able to rebase your work without too much trouble. Emmanuel Bourg
Bug#1011541: src:jellyfish1: fails to migrate to testing for too long: autopkgtest regression
Source: jellyfish1 Version: 1.1.11-6 Severity: serious Control: close -1 1.1.11-7 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1008944 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:jellyfish1 has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package introduced an autopkgtest regression for which I filed bug #1008944 a while back. 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=jellyfish1 OpenPGP_signature Description: OpenPGP digital signature
Bug#1011540: burp: autopkgtest regression with openssl 3
Source: burp Version: 2.4.0-3 Severity: serious Tags: sid bookworm burp's autopkgtest fail with openssl 3: make[2]: Entering directory '/tmp/autopkgtest-lxc.lg0p9u2a/downtmp/build.c19/src' FAIL: runner Testsuite summary for Burp 2.4.0 # TOTAL: 1 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 See ./test-suite.log Please report to https://github.com/grke/burp/issues make[2]: *** [Makefile:8640: test-suite.log] Error 1 make[2]: Leaving directory '/tmp/autopkgtest-lxc.lg0p9u2a/downtmp/build.c19/src' make[1]: *** [Makefile:8748: check-TESTS] Error 2 make[1]: Leaving directory '/tmp/autopkgtest-lxc.lg0p9u2a/downtmp/build.c19/src' make: *** [Makefile:8959: check-am] Error 2 autopkgtest [09:14:37]: test burp-unit-test: ---] See https://ci.debian.net/data/autopkgtest/testing/amd64/b/burp/22058117/log.gz Cheers -- Sebastian Ramacher
Bug#1005858: gitsome: diff for NMU version 0.8.0+ds-7.1
On 2022-05-24 14:32:45, Antoine Beaupre wrote: > Control: tags 1005858 + patch > Control: tags 1005858 + pending > > Dear maintainer, > > I've prepared an NMU for gitsome (versioned as 0.8.0+ds-7.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should delay it longer. Sigh. I actually messed up and forgot to pass --delayed=2 to dput. I realized to late to cancel. I hope it's still okay... a. -- We must learn to live together as brothers or perish together as fools. - Martin Luther King, Jr.
Bug#968507: O: icon-naming-utils -- script for maintaining backwards compatibility of Tango Project
Control: retitle -1 ITA: icon-naming-utils -- script for maintaining backwards compatibility of Tango Project Control: owner -1 Matteo Bini See https://mentors.debian.net/package/icon-naming-utils/ for the upload triggering this ITA.
Bug#1005858: gitsome: diff for NMU version 0.8.0+ds-7.1
Control: tags 1005858 + patch Control: tags 1005858 + pending Dear maintainer, I've prepared an NMU for gitsome (versioned as 0.8.0+ds-7.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. I have also pushed this patch to GitLab, but haven't pushed a tag in case we want to revert. Regards. diff -Nru gitsome-0.8.0+ds/debian/changelog gitsome-0.8.0+ds/debian/changelog --- gitsome-0.8.0+ds/debian/changelog 2022-04-16 11:48:49.0 -0400 +++ gitsome-0.8.0+ds/debian/changelog 2022-05-24 10:49:06.0 -0400 @@ -1,3 +1,11 @@ +gitsome (0.8.0+ds-7.1) unstable; urgency=medium + + * Non-maintainer upload. + * remove the gh binary to avoid conflicting with GitHub's more +well-known gh (Closes: #1005858) + + -- Antoine Beaupré Tue, 24 May 2022 10:49:06 -0400 + gitsome (0.8.0+ds-7) unstable; urgency=medium * Add support for python 3.10 (Closes: #1008844) diff -Nru gitsome-0.8.0+ds/debian/install gitsome-0.8.0+ds/debian/install --- gitsome-0.8.0+ds/debian/install 2018-09-19 02:07:55.0 -0400 +++ gitsome-0.8.0+ds/debian/install 1969-12-31 19:00:00.0 -0500 @@ -1 +0,0 @@ -scripts/gh_complete.sh /usr/share/bash-completion/completions/ diff -Nru gitsome-0.8.0+ds/debian/rules gitsome-0.8.0+ds/debian/rules --- gitsome-0.8.0+ds/debian/rules 2019-04-08 23:03:05.0 -0400 +++ gitsome-0.8.0+ds/debian/rules 2022-05-24 10:49:06.0 -0400 @@ -4,9 +4,8 @@ dh $@ --with python3 --buildsystem=pybuild override_dh_install-indep: - # redirect python library - sed -i "/import sys/ a sys.path.insert(1,'/usr/lib/python3/dist-packages/python-sigmavirus24-urltemplate/')" \ - debian/gitsome/usr/bin/gh + # do not ship a gh binary, see https://bugs.debian.org/1005858 + rm debian/gitsome/usr/bin/gh override_dh_missing: dh_missing --fail-missing signature.asc Description: PGP signature
Bug#1011538: RM: bind9-libs -- ROM; end-of-life, not needed anymore for isc-dhcp
Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 - -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, src:isc-dhcp has switched to bundled libraries in #942502, so this package can finally be removed. The only unsolved thing is #942501 in orphaned milter-greylist, so I bumped the severity to serious. I can do the NMU, but the package is orphaned and has other problems (links with obsoleted libgeoip), so it might be just better to remove it as well. Thanks, Ondrej - -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmKNIXBfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u WcLjQRAApFcG+duoxGfYyRO5llc9vKg50pwnuwVSsulhfSThrsXoZP985nDAspdj cn/q5cu2ULQAMsbcQBPkO30iJIVGwGyEJxOLvLLvv3ow4EDBtpfMnKveYk/QzMMd Px/Y8gsRWI8yoiRcqzsaiuuq1vPkRADu6uv3qdb+/J6T2o4Hf+hNIOrodRMxhMxq A4IWerlsPQN8yZr6hx2+W0qu7OCpXzIyQjwp2Kk6/+ay7RnixCS6t5PhdK+RCMIn LyeMMzS2yajIL5VSMdEOzwlnXhicEJ1PO5Jz0jFmLpK48yQ1sgtP0o5SoeMK9neu oO6IQkwl+oiRXybVmPMrCZbwxkklQZaRqNraTRF07gILJX9DcKdOZYZarIGkmAyC piI3MIlOSz7i7/rlJxGeu2iX0eEoGrDxC9wXMU0CRstavgxiAQ7Gs9KBvwUWG5VR qSKroQRN9WMTlf2e/a2r034pI6EvIfccGcqFkfRTrxvTZ35gel1BPe46JWFSZ2uo UxjTp7s3oQzv10uR7djElq/qaZGvPIJAmsi9fWbcr3b2a8nlvTUOVLyrk2kXA9V2 kho6Plw3YSeS8gqppqtAf2nXvJPAHixcNEXNy5DlR+GA9CZU+qQswauews+TubuH HjmtwzSzuugkF6CLMXA2P/ZgkRs7paARFcqyMwHMqR7D6LTdxfI= =aPbM - -END PGP SIGNATURE- -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmKNIhNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u WcLPVw//fbdcOsFZd0ysSfbK7opnXefy8KGvYB0dYlgtmSSVgHnbuNysxNDhmhIF 1lZSWZWADqoKKs1MMaDQLj22mXrLjeH0Vg3nhcHcCKLZ0GDGCixjKoAThvv+plnj CNQEOynf0GD9+kQnVEd8JvPW80w/cUznA8jm0ae2Cln7RGkE57us35KW4JgClCkO RJ1nEdEbDA1uzmz4VbYHTjA458bwVl3AWPod2Lxb2ybKH9pgwNJT859JU0WCrctW JmGvnVwwUb/m9WfYNSvWi7/A7/Aubcfz5UMmgjm6ewkaKPLxQQ1xSW+onZVBpdn6 c7Bz3O+uZSGZ1y9Uiu1oOC2c1aybM8/WjSGAGltHYBSWckwh3htA/yv6/WuipucG afsu3fYi6kYdVYO+wuLJKb6NVzRQQkNN5AfFQwFgXbtb5jUHo+UJ/GxUMLF515kt aSQCGc1yl4sgpq/1VLqOze4P+a31mbjoKIpNG18Po6nnKHL+gbEQ2mZ+Y6rYB7fg y9NhcFxOati1yOwt4R5RfzPrdObo+1SBcumg/5Qna5OaVadACt/gT32r4eRiaff3 1QZoFHCPrv13R3Z0d0RCu7TiQPLcgI5jewz2KbV9ZZAQzF9bNPXy63bgZqNS3w81 TuRr3WNtqhdnTpwBteVL788yP8ewMAVWqIGW/EyxV5L4p+qys9E= =j9XB -END PGP SIGNATURE-
Bug#1011533: chrony: kdevops reboot-limit fails between 50-12,000 reboots
On Tue, May 24, 2022 at 10:19:31AM -0700, Luis Chamberlain wrote: > On Tue, May 24, 2022 at 05:07:56PM +, Luis Chamberlain wrote: > > kernel | reboots | with-fix > > - > > > > > > v5.10.105 | 500 | not-tested-yet > > v5.17-rc7 | 1,200 | 2,000+ > > 5.17.0-1-amd64 | 3,300+ | first-run-stil-running > > Cc'ing Amir so he's aware. The subject is off, it should be between > 500-1,200 reboots. > > Each kdevops reboot-limit digit bump on the .kernel-ci.ok file > after runnning 'make reboot-limit-baseline-loop' represents > 100 tests run, su just multiply the number on the file with 100. > > Note that if you don't enable the CONFIG_WORKFLOW_LINUX_CUSTOM=y > you will just use the default distro kernel and there seems to be > no failures there yet. The patch I proposed could probably be simplified by using systemd logic for dependencies matching. What that is, is not clear, but clearly there is a race which the hack seems to resolve. Luis
Bug#1011313: RFS: python-decouple/3.6-3 -- Helps you to organize your Django/Flask settings
Control: tags -1 - moreinfo Thanks! The fixed 3.6-1 files are up on mentors now. ~m On Fri, 2022-05-20 at 11:27 +0200, Bastian Germann wrote: > Control: reopen -1 > Control: tags -1 moreinfo > > Am 20.05.22 um 11:17 schrieb Bastian Germann: > > You have to make this a NMU, which means mentioning it in the > > changelog and making the version 3.6-0.1. > > However, you did not give the maintainer a chance to act on this. > > Please file a bug asking for the new > > version and when it is not acted upon in a month, come back with > > your NMU and include a Closes: tag in > > your changelog for that bug. > > I did not see #986939. You have to close the ITA via your changelog. > Please keep -1 revision as long as this is not sponsored. > On reuploading please untag moreinfo. >
Bug#1011533: chrony: kdevops reboot-limit fails between 50-12,000 reboots
On Tue, May 24, 2022 at 05:07:56PM +, Luis Chamberlain wrote: > kernel | reboots | with-fix > - > > > v5.10.105 | 500 | not-tested-yet > v5.17-rc7 | 1,200 | 2,000+ > 5.17.0-1-amd64 | 3,300+ | first-run-stil-running Cc'ing Amir so he's aware. The subject is off, it should be between 500-1,200 reboots. Each kdevops reboot-limit digit bump on the .kernel-ci.ok file after runnning 'make reboot-limit-baseline-loop' represents 100 tests run, su just multiply the number on the file with 100. Note that if you don't enable the CONFIG_WORKFLOW_LINUX_CUSTOM=y you will just use the default distro kernel and there seems to be no failures there yet. Luis
Bug#1011536: apiguardian: FTBFS with OpenJDK 17 due to JDK detection error
Source: apiguardian Version: 1.1.0-3 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 apiguardian fails to build with OpenJDK 17, it requires OpenJDK 11 but the check can probably be bypassed: FAILURE: Build failed with an exception. * Where: Settings file '/<>/settings.gradle' line: 6 * What went wrong: A problem occurred evaluating settings 'apiguardian-api'. > The @API Guardian build requires Java 11. Currently executing with Java 12. * Try: Run with --debug option to get more log output. Run with --scan to get full insights.
Bug#1011535: openjfx: FTBFS with OpenJDK 17 due to javadoc errors
Package: openjfx
Version: 11.0.11+1-1
Severity: important
Tags: ftbfs sid bookworm
User: debian-j...@lists.debian.org
Usertags: default-java17
openjfx fails to build with OpenJDK 17 due to javadoc errors:
Starting process 'command '/usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc''.
Working directory: /<> Command:
/usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc
@/<>/build/tmp/javadoc/j>
Successfully started process 'command
'/usr/lib/jvm/java-17-openjdk-amd64/bin/javadoc''
/<>/modules/javafx.base/src/main/java/com/sun/javafx/property/PropertyReference.java:28:
warning: [removal] AccessController in java.security has been deprecated and
marked for removal
import static java.security.AccessController.doPrivileged;
^
/<>/modules/javafx.base/src/main/java/javafx/beans/value/WritableObjectValue.java:31:
error: invalid use of @param
* @param T
^
/<>/modules/javafx.base/src/main/java/javafx/beans/property/adapter/JavaBeanObjectPropertyBuilder.java:59:
error: invalid use of @param
* @param T the type of the wrapped {@code Object}
^
/<>/modules/javafx.base/src/main/java/javafx/beans/property/adapter/ReadOnlyJavaBeanObjectPropertyBuilder.java:58:
error: invalid use of @param
* @param T the type of the wrapped {@code Object}
^
/<>/modules/javafx.base/src/main/java/javafx/beans/property/adapter/JavaBeanObjectProperty.java:90:
error: invalid use of @param
* @param T type of the wrapped {@code Object}
^
/<>/modules/javafx.base/src/main/java/javafx/beans/property/adapter/ReadOnlyJavaBeanObjectProperty.java:82:
error: invalid use of @param
* @param T the type of the wrapped {@code Object}
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/Node.java:227:
error: heading used out of sequence: , compared to implicit preceding
heading:
* String ID
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/input/MouseEvent.java:52:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Dragging gestures
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/input/DragEvent.java:54:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Drag sources: initiating a drag and drop gesture
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/layout/Pane.java:61:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Resizable Range
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/layout/VBox.java:77:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Resizable Range
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/layout/HBox.java:79:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Resizable Range
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/layout/AnchorPane.java:45:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Anchor Constraints
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/layout/TilePane.java:108:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Resizable Range
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/layout/BorderPane.java:85:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Resizable Range
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/layout/StackPane.java:70:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Resizable Range
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/layout/GridPane.java:84:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Grid Constraints
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/layout/FlowPane.java:101:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Resizable Range
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/shape/Shape.java:95:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Interaction with coordinate systems
^
/<>/modules/javafx.graphics/src/main/java/javafx/scene/text/TextFlow.java:113:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Resizable Range
^
/<>/modules/javafx.controls/src/main/java/javafx/scene/control/TreeView.java:101:
error: heading used out of sequence: , compared to implicit preceding
heading:
* TreeView Selection / Focus APIs
^
/<>/modules/javafx.controls/src/main/java/javafx/scene/control/Pagination.java:54:
error: heading used out of sequence: , compared to implicit preceding
heading:
* Styling the page indicators
^
/<>/modules/javafx.controls/src/main/java/javafx/scene/control/Cell.java:190:
error: heading used out of sequence: , compared to
Bug#1011534: opsin: FTBFS with OpenJDK 17 due to new javadoc layout
Source: opsin Version: 2.6.0-2 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 opsin fails to build with OpenJDK 17 because the dh_installdocs override in debian/rules attempts to replace the embedded copy of jQuery, but the layout of the javadoc has changed: dh_installdocs ln -fs /usr/share/javascript/jquery/jquery.js /<>/debian/libopsin-java-doc/usr/share/doc/libopsin-java/api/jquery/external/jquery/jquery.js ln: failed to create symbolic link '/<>/debian/libopsin-java-doc/usr/share/doc/libopsin-java/api/jquery/external/jquery/jquery.js': No such file or directory make[1]: *** [debian/rules:17: override_dh_installdocs] Error 1 The javadoc packages are rarely used (the popcon of libopsin-java-doc has never exceeded 5 in 10 years) and they induce a maintenance burden, I strongly recommend removing this package.
Bug#1011533: chrony: kdevops reboot-limit fails between 50-12,000 reboots
Package: chrony Version: 4.2-2 Severity: important Tags: patch X-Debbugs-Cc: mcg...@kernel.org Dear Maintainer, When using the new kdevops [0] reboot-limit [1] test to see how may reboots can happen with debian-testing without a failure I ran have ran 3 tests with different kernels with the following observations. The point of the test is to simply instantiate vagrant debian-testing guests, and then reboot them and detect with ansible if ssh access to the guest is possible. The test fails upon an ssh timeout or crash. In the list below a + indicates the test is still running. A single digit expresses how many times reboots completed successfully. kernel | reboots | with-fix - v5.10.105 | 500 | not-tested-yet v5.17-rc7 | 1,200 | 2,000+ 5.17.0-1-amd64 | 3,300+ | first-run-stil-running Upon inspection on the failed boots on v5.10.105 and v5.17-rc7 I noticed the following on both systems: root@rebootlimit ~ # sudo systemctl list-units --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● ifup@eth0.service loaded failed failed ifup for eth0 I can see then (scraped from a console, sorry about formatting): ]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 ]: DHCPOFFER of 192.168.121.240 from 192.168.121.1 ]: DHCPREQUEST for 192.168.121.240 on eth0 to 255.255.255.255 port 67 ]: DHCPACK of 192.168.121.240 from 192.168.121.1 ]: bound to 192.168.121.240 -- renewal in 1699 seconds. nd to 192.168.121.240 -- renewal in 1699 seconds. -parts: /etc/network/if-up.d/chrony exited with return code 1 p: failed to bring up eth0 ifup@eth0.service: Main process exited, code=exited, status=1/FAILURE ifup@eth0.service: Failed with result 'exit-code'. The important line is: May 21 10:58:58 rebootlimit sh[693]: run-parts: /etc/network/if-up.d/chrony exixited with return code 1 Using $(virsh net-dhcp-leases vagrant-libvirt) I see no takers of the IP address and so there has not been clashes. So my next best guesss given the lack of output from chrony is that this is a race on bootup. I'm still testing things but the following adjustment seems to have helped so far. --- /etc/network/if-up.d/chrony.old 2022-05-24 16:40:53.112439882 + +++ /etc/network/if-up.d/chrony 2022-05-24 16:41:23.452471796 + @@ -5,6 +5,7 @@ [ -x /usr/sbin/chronyd ] || exit 0 if [ -e /run/chrony/chronyd.pid ]; then +systemctl is-system-running --wait chronyc onoffline > /dev/null 2>&1 fi [0] https://github.com/linux-kdevops/kdevops [1] https://github.com/linux-kdevops/kdevops/blob/master/workflows/demos/reboot-limit/Kconfig -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.105 (SMP w/8 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chrony depends on: ii adduser 3.121 ii init-system-helpers 1.62 ii iproute2 5.17.0-2 ii libc62.33-7 ii libcap2 1:2.44-1 ii libedit2 3.1-20210910-1 ii libgnutls30 3.7.4-2 ii libnettle8 3.7.3-1 ii libseccomp2 2.5.4-1 ii tzdata 2022a-1 ii ucf 3.0043
Bug#1011532: icedtea-web: FTBFS with OpenJDK 17 due to pack200 removal
Source: icedtea-web Version: 1.8.8-1 Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 icedtea-web fails to build with OpenJDK 17 due to the removal of the pack200 tool and API: checking for pack200... checking for pack200... /usr/lib/jvm/default-java/bin/pack200 configure: WARNING: "pack200 not found so custom part of run-netx-dist will fail" checking for hg... no checking for distribution package version... 1.8.8 checking what version string to use... 1.8.8 (1.8.8) checking whether to build the browser plugin... no checking whether make supports the include directive... yes (GNU style) checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking whether to build plugin jar for javaws -html... no checking if java.util.jar.Pack200 is available from some.pkg (module "")... no configure: error: java.util.jar.Pack200 not found. make[1]: *** [debian/rules:12: override_dh_auto_configure] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:8: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Bug#1011506: libpmemobj-cpp: FTBFS with onetbb/2021.5.0-9 in experimental
On Tue, May 24, 2022 at 08:35:31AM +0300, Andrius Merkys wrote: > Source: libpmemobj-cpp > tbb/onetbb transition (#1007222) is currently in the planning. During > test rebuild of libtbb-dev reverse dependencies with onetbb/2021.5.0-9 > in experimental, current source failed to build with the following: TBB is used in this package only for some tests, just dropping the B-Dep is enough to skip them. I've reported upstream: https://github.com/pmem/libpmemobj-cpp/issues/1252 so we can get a proper patch but it's not urgent. If you upload onetbb to unstable before then, please let me know, I'll skip the tests immediately. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ Eight legs good, four legs bad! -- when your drider pwns a ⣾⠁⢠⠒⠀⣿⡁ smelly goodie centaur. ⢿⡄⠘⠷⠚⠋⠀ Rearkick OP -- my grandpa's brother-in-law got one-shotted ⠈⠳⣄ from full hp in RL, please nerf!
Bug#1011531: lcov: The lcov script reports version 1.14 whereas the package is 1.15
Package: lcov Version: 1.15-1 Severity: normal X-Debbugs-Cc: ed.go...@free.fr Dear Maintainer, I wanted to check if the lcov script was the latest released one available online (ie: 1.15). I decided to check the version with two different methods. The first one was to check using the tool's --version command line argument, and the second checking the package version. To my surprise these didn't match: one reporting 1.14 wheras the other reporting 1.15 (if leaving aside the -1 debian packaging revision). Here are the outputs of both command lines: $ lcov --version lcov: LCOV version 1.14 $ apt policy lcov lcov: Installed: 1.15-1 Candidate: 1.15-1 Version table: *** 1.15-1 500 500 http://deb.debian.org/debian sid/main amd64 Packages 500 http://deb.debian.org/debian sid/main i386 Packages 100 /var/lib/dpkg/status 1.14-2 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages 500 http://deb.debian.org/debian bullseye/main i386 Packages Both versions should match, shouldn't they ? Regards. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.9 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages lcov depends on: ii gcc 4:11.2.0-2 ii libjson-perl 4.04000-1 ii libperlio-gzip-perl 0.19-1+b8 ii perl 5.34.0-4 Versions of packages lcov recommends: ii libgd-perl [libgd-gd2-perl] 2.76-2+b1 lcov suggests no packages. -- no debconf information
Bug#1011530: FTBFS: fails to include system headers
Source: mac-fdisk
Version: 0.1-18
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi!
I'm afraid that mac-fdisk fails to build with the toolchain in current
unstable. It doesn't include public headers, which results in a lot
of warnings like:
pdisk.c:156:5: warning: implicit declaration of function ‘exit’
[-Wimplicit-function-declaration]
156 | exit(err);
| ^~~~
pdisk.c:52:1: note: include ‘’ or provide a declaration of ‘exit’
pdisk.c:469:13: warning: implicit declaration of function ‘strncmp’
[-Wimplicit-function-declaration]
469 | if (strncmp(type_name, kFreeType, DPISTRLEN) == 0) {
| ^~~
pdisk.c:52:1: note: include ‘’ or provide a declaration of ‘strncmp’
dpme.h:48:25: warning: ‘strncmp’ argument 3 type is ‘int’ where ‘unsigned int’
is expected in a call to built-in function declared without prototype
[-Wbuiltin-declaration-mismatch]
dump.c:319:21: warning: incompatible implicit declaration of built-in function
‘malloc’ [-Wbuiltin-declaration-mismatch]
319 | data = (DPME *) malloc(PBLOCK_SIZE);
| ^~
dump.c:319:21: note: include ‘’ or provide a declaration of ‘malloc’
and some fatal errors:
errors.c: In function ‘fatal’:
errors.c:118:30: error: ‘sys_nerr’ undeclared (first use in this function)
118 | if (value > 0 && value < sys_nerr) {
| ^~~~
errors.c:118:30: note: each undeclared identifier is reported only once for
each func
tion it appears in
errors.c:119:37: error: ‘sys_errlist’ undeclared (first use in this function)
119 | fprintf(stderr, " (%s)\n", sys_errlist[value]);
| ^~~
Full log attached.
Meow!
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'),
(120, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.18.0-00017-g251fbd8b0fa2 (SMP w/64 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
sbuild (Debian sbuild) 0.83.1 (26 April 2022) on valinor.angband.pl
+==+
| mac-fdisk (i386) Tue, 24 May 2022 15:36:21 + |
+==+
Package: mac-fdisk
Distribution: unstable
Machine Architecture: amd64
Host Architecture: i386
Build Architecture: i386
Build Type: binary
I: NOTICE: Log filtering will replace
'var/run/schroot/mount/unstable-i386-sbuild-c89c94f3-c7e0-4819-8956-a172ad00da2c'
with '<>'
I: NOTICE: Log filtering will replace 'build/mac-fdisk-SIbUU1/resolver-pC5EEC'
with '<>'
+--+
| Update chroot|
+--+
Hit:1 http://apt-rosy.angband.pl:3142/debian unstable InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+--+
| Fetch source files |
+--+
Check APT
-
Checking available source versions...
Download source files with APT
--
Reading package lists...
NOTICE: 'mac-fdisk' packaging is maintained in the 'Git' version control system
at:
git://github.com/glaubitz/mac-fdisk-debian.git
Please use:
git clone git://github.com/glaubitz/mac-fdisk-debian.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 78.1 kB of source archives.
Get:1 http://apt-rosy.angband.pl:3142/debian unstable/main mac-fdisk 0.1-18
(dsc) [2010 B]
Get:2 http://apt-rosy.angband.pl:3142/debian unstable/main mac-fdisk 0.1-18
(tar) [55.8 kB]
Get:3 http://apt-rosy.angband.pl:3142/debian unstable/main mac-fdisk 0.1-18
(diff) [20.3 kB]
Fetched 78.1 kB in 0s (299 kB/s)
Download complete and in download only mode
I: NOTICE: Log filtering will replace 'build/mac-fdisk-SIbUU1/mac-fdisk-0.1'
with '<>'
I: NOTICE: Log filtering will replace 'build/mac-fdisk-SIbUU1' with
'<>'
+--+
| Install package build dependencies |
+--+
Setup apt archive
-
Merged Build-Depends: debhelper, build-essential, fakeroot
Filtered Build-Depends:
Bug#1011529: On MacBook Pro (P8600) wifi card with BCM4322 chipset does not work
Source: broadcom-sta Version: 6.30.223.271-19 Followup-For: Bug #973365 Dear Maintainer, I'm using this driver since performance with b43 are worst (ie with wl dl:36Mbit/s, U:20Mbits/s with b43 DL:9Mbits/s,UL 2Mbits/s). After boot running "nmcli d w l" list no network, if I close lid reopen and rerun the command wifi network are listed. When no wifi network are listed I got in dmesg these lines: [ 125.605989] ERROR @wl_notify_scan_status : [ 125.606003] wlp2s0 Scan_results error (-22) after sleep/wake I got these lines, when wifi connection works: [ 669.401258] wl :02:00.0 wlp2s0: Current addr: 00 26 bb 0e ae 9b> [ 669.401270] wl :02:00.0 wlp2s0: Expected addr: 00 00 00 00 00 00> [ 669.401273] [ cut here ] [ 669.401275] netdevice: wlp2s0: Incorrect netdev->dev_addr [ 669.401303] WARNING: CPU: 1 PID: 545 at net/core/dev_addr_lists.c:51> and here complete log(two sleep?wake cycles): [ 26.373248] rfkill: input handler disabled [ 28.336234] kauditd_printk_skb: 16 callbacks suppressed [ 28.336239] audit: type=1400 audit(1653263808.353:28): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=1099 comm="cups-browsed" capability=23 capname="sys_nice" [ 28.438008] NFSD: Using nfsdcld client tracking operations. [ 28.438019] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f000) [ 40.479907] rfkill: input handler enabled [ 40.750326] nouveau :04:00.0: firmware: failed to load nouveau/nvaf_fuc084 (-2) [ 40.750337] nouveau :04:00.0: Direct firmware load for nouveau/nvaf_fuc084 failed with error -2 [ 40.750356] nouveau :04:00.0: firmware: failed to load nouveau/nvaf_fuc084d (-2) [ 40.750360] nouveau :04:00.0: Direct firmware load for nouveau/nvaf_fuc084d failed with error -2 [ 40.750363] nouveau :04:00.0: msvld: unable to load firmware data [ 40.750366] nouveau :04:00.0: msvld: init failed, -19 [ 44.050440] rfkill: input handler disabled [ 111.077930] ERROR @wl_notify_scan_status : [ 111.077943] wlp2s0 Scan_results error (-22) [ 124.502609] wlan0: Broadcom BCM432b 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) [ 124.508835] wl :02:00.0 wlp2s0: renamed from wlan0 [ 124.542969] wl :02:00.0 wlp2s0: Current addr: 00 26 bb 0e ae 9b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 124.542981] wl :02:00.0 wlp2s0: Expected addr: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 124.542984] [ cut here ] [ 124.542986] netdevice: wlp2s0: Incorrect netdev->dev_addr [ 124.543009] WARNING: CPU: 0 PID: 545 at net/core/dev_addr_lists.c:517 dev_addr_check.cold+0x43/0x7d [ 124.543017] Modules linked in: wl(POE) rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device qrtr bnep btusb btrtl btbcm btintel btmtk bluetooth jitterentropy_rng nls_ascii nls_cp437 sha512_ssse3 vfat fat sha512_generic coretemp kvm_intel snd_hda_codec_hdmi ctr joydev drbg snd_hda_codec_cirrus snd_hda_codec_generic ledtrig_audio ansi_cprng kvm applesmc irqbypass uvcvideo snd_hda_intel pcspkr efi_pstore videobuf2_vmalloc snd_intel_dspcfg videobuf2_memops snd_intel_sdw_acpi snd_hda_codec ecdh_generic ecc videobuf2_v4l2 videobuf2_common snd_hda_core snd_hwdep videodev snd_pcm mc bcm5974 snd_timer apple_mfi_fastcharge sg snd soundcore sbs acpi_als industrialio_triggered_buffer kfifo_buf evdev sbshc industrialio ac apple_bl acpi_cpufreq cfg80211 nfsd auth_rpcgss rfkill nfs_acl lockd ipmi_devintf ipmi_msghandler grace msr parport_pc ppdev lp parport sunrpc fuse configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 btrfs blake2b_generic zstd_compress efivarfs raid10 raid456 [ 124.543113] async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod uas usb_storage hid_appleir hid_apple hid_generic usbhid hid sd_mod t10_pi crc_t10dif crct10dif_generic sr_mod crct10dif_common cdrom ohci_pci nouveau ahci libahci tg3 mxm_wmi wmi i2c_algo_bit libata drm_ttm_helper ttm drm_kms_helper cec rc_core libphy drm ohci_hcd ehci_pci ehci_hcd usbcore firewire_ohci firewire_core ptp pps_core crc_itu_t scsi_mod scsi_common usb_common video button [last unloaded: wl] [ 124.543174] CPU: 0 PID: 545 Comm: NetworkManager Tainted: PW OE 5.17.0-1-amd64 #1 Debian 5.17.3-1 [ 124.543179] Hardware name: Apple Inc. MacBookPro7,1/Mac-F222BEC8, BIOS 68.0.0.0.0 06/13/2019 [ 124.543181] RIP: 0010:dev_addr_check.cold+0x43/0x7d [ 124.543185] Code: 01 e8 76 3e fc ff 0f 0b 49 c7 c4 c3 76 b6 bd 80 3b 00 75 30 48 c7 c6 ce 76 b6 bd 4c 89 e2
Bug#1010396: ITP: tsn-scripts -- Tool set for Time Sensitive Networking testing
On Fri, May 13, 2022 at 08:04:46AM +0200, Sebastian Andrzej Siewior wrote: > On 2022-04-30 15:51:00 [+0300], Vladimir Oltean wrote: > > This is my first Intent To Package. I am the upstream maintainer of the > > project, would like to be the maintainer of the Debian package as well, > > and would need a sponsor and mentor to help with review and walk me > > through the packaging process. I am flexible in making changes to the > > upstream project if this makes Debian packaging easier. In fact, in > > expectation of changes to come, I've marked "v0.8" as the version of the > > software to package, as opposed to the currently latest "v0.7". > > If there is anything, just let me know. > There are some manuals at >https://www.debian.org/doc/devel-manuals > > I would suggest to peek at >Debian Developer's Reference >Debian New Maintainers' Guide > > depending on how much you already know. The "mentors" page also > references a few of them. >https://mentors.debian.net/qa/ > > In general I would suggest to use a "simple" dh based package. > > Sebastian I've ended up doing quite a bit of cleanup to the upstream repository. This includes a rename of the repo from "tsn-scripts" to the more specific "isochron" name. Along with this, my belief is that the debian package name should also be "isochron", but I'm not clear whether I should close this ITP and open a new one for that? In any case, the sources for the debian package are now included in the upstream source itself: https://github.com/vladimiroltean/isochron It builds and installs cleanly on armhf, aarch64 and x86_64. It's just that lintian shows these warnings which I'm not sure what to do about? W: isochron: improbable-bug-number-in-closes 1010396 W: isochron source: missing-license-paragraph-in-dep5-copyright gpl-2.0 (line 9) W: isochron source: no-debian-changes I looked at the documentation, and it appears that apart from some review, the next step should be uploading to salsa, basically? Not sure how that's supposed to happen, though. I haven't been subscribed to debian-devel for more than 1 week, but in the other ITPs posted so far, I don't think I saw any activity on them?
Bug#1011528: Incompatible with PHP 8.1
Package: fusiondirectory Version: 1.3-5 Severity: grave fusiondirectory is not able to run on php8.1 environment. https://gitlab.fusiondirectory.org/fusiondirectory/fd/-/issues/6175 -- ISHIKAWA Mutsumi ,
Bug#988540: im-config: breaks the keyboard configuration
On 2022-05-24 22:54:01 +0900, Osamu Aoki wrote:
> > > Users may no longer be able to use xterm **reliably for some
> > > non-ASCII inputs** when ibus is **activated**.
> >
> > I'm wondering what you mean by that. I recall that:
> >
> > 1. If im-config is run after my XKB settings, then my keyboard
> >configuration is broken (probably overridden by im-config's
> >own settings). This means that ibus is activated, right?
>
> Yes. (To be precise, your XKB settings are *ignored*. Since keyboard
> inputs goes through ibus to reach xterm. ibus is not run under your
> XKB settings nor under its influence. I guess this is the situation
> but I haven't investigated exact situation.)
This is incorrect. XKB settings are ignored when running im-config,
but they are not ignored by changing them with xkbcomp after that.
> ibus activation may be by the default setting of im-config or by the
> Desktop environment such as recent GNOME.
I recall that I do not use any desktop environment. But im-config
provides /etc/X11/Xsession.d/70im-config_launch, which is sourced
automatically when one logs in, and there is *no way* for the end
user to disable it. The user's $HOME/.xsessionrc file is sourced
before 70im-config_launch, so that this could be a way to let the
user choose (if properly documented), e.g. via setting or not some
shell variable. However, "im-config -n none" may be sufficient.
> If you want to use classic XKB setting, just don't activate ibus.
> (or don't install ibus.)
If "im-config -n none" has the effect that ibus is not activated,
this is fine. Otherwise, there would be issues on multiuser machines,
where ibus and im-config may be installed for users who need them.
> > So, if ibus is activated (see (1)), this would
> >mean that it shouldn't affect xterm, even for most non-ASCII
> >inputs (I recall that I use accented letters, possibly via
> >dead keys, and math symbols: xterm is receiving the Unicode
> >character correctly, so I wonder why it would depend on the
> >code point).
>
> I don't know what do you mean by code point.
Unicode code point. This is how XKB maps the keyboard, with
translations from a key code to a Unicode character (given
by some name or in hexadecimal). For instance, I have:
[...]
key { [ a, A, ae, AE ] };
key { [ s, S, ssharp, U2211 ] };
key { [ d, D, dagger, downarrow ] };
key { [ f, F, U2500, U2502 ] };
key { [ g, G, U250C, U251C ] };
key { [ h, H, U2510, U2524 ] };
key { [ j, J, U2514, U252C ] };
key { [ k, K, U2518, U2534 ] };
key { [ l, L, sterling, U253C ] };
[...]
> Some particular keyboard inputs may cause problem but mostly
> functional for keyboard -> ibus -> XIM -> xterm path. If you re-read
> my updated page, I describe this subtle situation carefully. Please
> read https://wiki.debian.org/Keyboard .
This is not satisfactory. What do you mean by "pass processed data"
for XIM clients? i.e. what kind of data? And why non-ASCII?
BTW, do you have an example of bug for something that works with XKB
but not with XIM?
What is described under "There have been frequent and persistent bugs
around this combination as discussed in Red Hat Bugzilla – Bug 2013610."
is off-topic, because such input methods are not possible with XKB.
> Especially, I
> address your concern at
> https://wiki.debian.org/Keyboard#Multi-language_keyboard_configuration_strategy
But if some applications start to support ibus only because XKB is
obsolete, "im-config -n none" is not a long-term solution.
> XIM bug for ibus seems to impact particular combination of input sequences
> anyway.
>
> > [*] in case of testing, bug 661295 needs to be taken into account,
> > i.e. one should test by starting xterm after any config change.
>
> No no no... let's not create unmanageable system.
??? I'm just saying that if you want to test the behavior and see
that xterm doesn't work, you must not blindly deduce that this is
a bug in XIM or whatever, because xterm or libx11 has its own bugs
and you may actually see that.
--
Vincent Lefèvre - Web:
Bug#1005858: gh,gitsome: File conflict, both ship /usr/bin/gh
On 2022-05-24 21:52:55, SZ Lin (林上智) wrote: > Hi, > > Antoine Beaupré 於 2022年5月19日 週四 下午10:11寫道： >> [...] >> SZ, do you agree with removing the `gh` binary from the `gitsome` binary >> package? I'd be happy to send a NMU to do this if you agree, which would >> unblock `gh` from migrating into testing. > > Yes, please go ahead :-) Great, that's really good to hear. I'm going to make a NMU and MR this very morning to solve this. Thanks for doing the right thing! -- Premature optimization is the root of all evil - Donald Knuth
Bug#1011527: libgl1-nvidia-glvnd-glx:i386: bad README.txt file does not allow coexisting between amd64 and i386 versions.
Package: libgl1-nvidia-glvnd-glx Version: 470.129.06-1 Severity: normal Dear maintainer. The /usr/share/doc/libgl1-nvidia-glvnd-glx/README.txt.gz file differs between the i386 and AMD64 versions of this package, making DPKG error out at install: Preparing to unpack .../libgl1-nvidia-glvnd-glx_470.129.06-1_amd64.deb ... Unpacking libgl1-nvidia-glvnd-glx:amd64 (470.129.06-1) over (470.103.01-4) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-nvidia-glvnd-glx_470.129.06-1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgl1-nvidia-glvnd-glx/README.txt.gz', which is different from other instances of package libgl1-nvidia-glvnd-glx:amd64 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) This is because the file in the i386 version of the package is smaller, missing the entire Appendix 6: ~$ diff -u README.txt-i386 README.txt-amd64 | head -20 --- README.txt-i386 2022-05-24 10:15:26.121674482 -0400 +++ README.txt-amd64 2022-05-24 10:15:30.781609187 -0400 @@ -9180,6 +9180,166 @@ GRID K520118AD + +A6. The 470.xx driver still supports the following set of GPUs: + + + NVIDIA GPU product Device PCI ID* VDPAU features + --- -- -- + GeForce GTX 650 0FC6D + GeForce GT 740 0FC8D + GeForce GT 730 0FC9C + GeForce GT 755M 0FCDD + GeForce GT 640M LE 0FCEC + GeForce GT 650M 0FD1D + GeForce GT 640M 0FD2D + GeForce GT 640M LE 0FD2 1028 0595 C Thank you, -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libgl1-nvidia-glvnd-glx:i386 depends on: ii libgl1 1.4.0-1 ii libglx-nvidia0 470.129.06-1 libgl1-nvidia-glvnd-glx:i386 recommends no packages. libgl1-nvidia-glvnd-glx:i386 suggests no packages. -- no debconf information
Bug#1011174: marked as pending in controlsfx
Hi Emmanuel, On Tue, May 24, 2022 at 11:12:54AM +, Emmanuel Bourg wrote: > Control: tag -1 pending > > Hello, > > Bug #1011174 in controlsfx reported by you has been fixed in the > Git repository and is awaiting an upload. You can see the commit > message below and you can check the diff of the fix at: > > https://salsa.debian.org/java-team/controlsfx/-/commit/cc9cb1cddad4ba2b272eca096c6270f16c8f12ed Thank you for filing these Java 17 FTBFS bug reports and also for fixing them. I have tried to help the effort by using the BTS to tag myself as an owner for some of the reports, including this bug on May 19th [1]. Obviously I am not as quick as you are, but I did have work in progress on controlfx on my local machine. Since this is a team-maintained package, and what's useful for users is what is important, I don't want to make a big deal out of it. That is, this is not about me. However, duplicated efforts dilute our impact. Because I have a limited amount of time that I can dedicate to Debian, I will take the opportunity to request that Java Team members to use the BTS for coordination on team-maintained packages. The `bts` command in the devscripts package is a convenient way to manipulate bugs, express your intent, and avoid duplicated effort. For example: bts owner ! bts noowner bts tag +help etc... Thanks, tony [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011174#6 signature.asc Description: PGP signature
Bug#1005858: gh,gitsome: File conflict, both ship /usr/bin/gh
Hi, Antoine Beaupré 於 2022年5月19日 週四 下午10:11寫道： > > On 2022-02-27 10:09:32, Paul Wise wrote: > > Control: forwarded -1 https://github.com/donnemartin/gitsome/issues/177 > > > > On Sat, 26 Feb 2022 23:43:14 +0800 SZ Lin (林上智) wrote: > > > >> The "gitsome" has used "gh" since 2017, and thus would you mind renaming > >> the "gh" in your package to avoid the conflict issue? > > > > Since gh is the official GitHub client, probably it should retain "gh" > > and gitsome should move to "git some" or similar, as I have suggested > > in the above upstream issue. The only commentor there agreed with me. > > And I agree with you. The gitsome package already installs two binaries: > one is called "gh" and the other is called "gitsome". It seems to me it > could simply drop the "gh" alias and none would be the worse. > > SZ, in your February 26 message[1], you explicitly asked the gh package > maintainers to rename their package, which was refused. It seems the > concensus that has developped in the following thread is that it is > instead your package, gitsome, that should have its binary renamed. > > Pabs suggested `gitsome` could also be renamed to `git-some` which would > make it visible as a `git some` subcommand, from what I understand. It > seems like the `gh` alias is kind of an alias unrelated with the main > functionality of the package. > > SZ, do you agree with removing the `gh` binary from the `gitsome` binary > package? I'd be happy to send a NMU to do this if you agree, which would > unblock `gh` from migrating into testing. Yes, please go ahead :-) > > Otherwise, how can we reach consensus on this? The policy says that if > we can't reach consensus, *both* packages need to be renamed, and that > seems like a situation where we would all lose. > > I'll also point out that the upstream issue hasn't seen any activity > since pabs commented on it in February, so it doesn't seem like we can > count on upstream to fix this for us. The issue has been open for 2 > years now. Yeah, it seems like the upstream is inactive somehow. SZ > > Thank you for your time! > > [1]: > https://lists.debian.org/msgid-search/CAFk6z8Mw0kFHehm_a7=0bmdt6mzff03sewx+y93xy42bkq7...@mail.gmail.com > > -- > Tu connaîtras la vérité de ton chemin à ce qui te rend heureux. > - Aristote >
Bug#988540: im-config: breaks the keyboard configuration
Hi, > -Original Message- > From: Vincent Lefevre > To: Osamu Aoki > Cc: Gunnar Hjalmarsson , 988...@bugs.debian.org, brian m. > carlson > Subject: Re: Bug#988540: im-config: breaks the keyboard configuration > Date: Tue, 24 May 2022 12:54:54 +0200 > > On 2022-05-23 11:49:21 +0900, Osamu Aoki wrote: > > Users may no longer be able to use xterm **reliably for some > > non-ASCII inputs** when ibus is **activated**. > > I'm wondering what you mean by that. I recall that: > > 1. If im-config is run after my XKB settings, then my keyboard >configuration is broken (probably overridden by im-config's >own settings). This means that ibus is activated, right? Yes. (To be precise, your XKB settings are *ignored*. Since keyboard inputs goes through ibus to reach xterm. ibus is not run under your XKB settings nor under its influence. I guess this is the situation but I haven't investigated exact situation.) ibus activation may be by the default setting of im-config or by the Desktop environment such as recent GNOME. > 2. If after that, I apply my XKB settings again, then things work >as usual (even for xterm), possibly except for applications >that are currently running (in particular xterm, but this is >not related to ibus, as this is an issue I reported in 2012: >bug 661295). To be honest, I don't want to create nor deal such a complicated situation. If you want to use classic XKB setting, just don't activate ibus. (or don't install ibus.) > So, if ibus is activated (see (1)), this would >mean that it shouldn't affect xterm, even for most non-ASCII >inputs (I recall that I use accented letters, possibly via >dead keys, and math symbols: xterm is receiving the Unicode >character correctly, so I wonder why it would depend on the >code point). I don't know what do you mean by code point. > Or did you mean that if I want to remap the keyboard with ibus > instead of XKB, then it would not work with xterm[*]? You make it sounds total breakage. problem was rare. Some particular keyboard inputs may cause problem but mostly functional for keyboard -> ibus -> XIM -> xterm path. If you re-read my updated page, I describe this subtle situation carefully. Please read https://wiki.debian.org/Keyboard . Especially, I address your concern at https://wiki.debian.org/Keyboard#Multi-language_keyboard_configuration_strategy XIM bug for ibus seems to impact particular combination of input sequences anyway. > [*] in case of testing, bug 661295 needs to be taken into account, > i.e. one should test by starting xterm after any config change. No no no... let's not create unmanageable system. Osamu
Bug#1003037: astra-toolbox: FTBFS: error: parameter packs not expanded with '...'
On 23/05/2022 19.30, Andreas Beckmann wrote: On Mon, 03 Jan 2022 03:07:39 +0100 Andreas Beckmann wrote: /usr/include/c++/11/bits/std_function.h:435:145: error: parameter packs not expanded with '...': 435 | function(_Functor&& __f) I've now switched back the default compiler for nvidia-cuda-toolkit 11.4.3 in sid to g++-10 which does not have this problem. There are also some autopkgtests in place that should notice regressions when compiling stl headers with nvcc. To make use of that, you need to Build-Depend on nvidia-cuda-toolkit-gcc (instead of nvidia-cuda-toolkit) and you should probably build with CXX=cuda-g++ (and maybe CC=cuda-gcc) to automatically use the default compiler used by the cuda tookit. Andreas
