Bug#580606: marked as done (per-rule option to disable logging)
Your message dated Tue, 23 Feb 2021 08:46:47 +0100 with message-id and subject line Re: Bug#580606: can be done differently has caused the Debian Bug report #580606, regarding per-rule option to disable logging to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 580606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sudo Version: 1.7.2p6-1 Severity: wishlist For certain rules, it might make sense to inhibit logging. I run a command via sudo from cron every minute, and every minute this gets logged into syslog. I can disable logging altogether, but I really just want t inhibit it for this rule. How about something like: myuser ALL=(root) NOPASSWD NOLOGGIN: /path/to/my/command ? -- System Information: Debian Release: squeeze/sid Architecture: amd64 (x86_64) Kernel: Linux 2.6.33-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sudo depends on: ii libc6 2.10.2-7 Embedded GNU C Library: Shared lib ii libpam-modules1.1.1-3Pluggable Authentication Modules f ii libpam0g 1.1.1-3Pluggable Authentication Modules l sudo recommends no packages. sudo suggests no packages. -- Configuration Files: /etc/sudoers.d/README [Errno 13] Permission denied: u'/etc/sudoers.d/README' -- no debconf information -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/) --- End Message --- --- Begin Message --- Version: 1.8.10p3 On Tue, Feb 23, 2021 at 09:48:14AM +1300, martin f krafft wrote: > Regarding the following, written by "Marc Haber" on 2021-02-22 at 17:22 Uhr > +0100: > > On Fri, May 21, 2010 at 01:37:00PM +0200, martin f krafft wrote: > > > Anyway, I think it would make more sense to do this analogously to > > > NOPASSWD. > > > > So this issue can be closed now? > > If you think so. I am not sure about this, but since what you want can be done in sudo post-lenny (hence closing with the version in jessie), the direct issue seems to be solved for me. I agree that the notation is somewhat clumsy, but since Debian is unlikely to invent and implement its own configuration file options and I can only make a weak point on the upstream mailing lists, your wishlist item is most likely to be fulfilled if you talk to upstream yourself. I am sure that you can do that ;-) Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421--- End Message ---
Bug#978365: marked as done (fonts-inter: FTBFS: fontmake: Error: In 'src/Inter.glyphs' -> 'master_ufo/Inter.designspace' -> 'master_ufo/instance_ufo/Inter-Thin.ufo': Compiling UFO failed: master_ufo/i
Your message dated Tue, 23 Feb 2021 07:18:31 + with message-id and subject line Bug#978365: fixed in fonts-inter 3.15+ds-3 has caused the Debian Bug report #978365, regarding fonts-inter: FTBFS: fontmake: Error: In 'src/Inter.glyphs' -> 'master_ufo/Inter.designspace' -> 'master_ufo/instance_ufo/Inter-Thin.ufo': Compiling UFO failed: master_ufo/instance_ufo/Inter-Thin.ufo/features.fea:73:8: The following feature file should be included but cannot be found: features/ccmp.fea to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 978365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fonts-inter Version: 3.15+ds-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > fontmake -i -o otf -g src/Inter.glyphs > INFO:fontmake.font_project:Building master UFOs and designspace from Glyphs > source > INFO:glyphsLib.classes:Parsing "src/Inter.glyphs" file into > WARNING:glyphsLib.builder.components:Glyph 'A': All components of the > background layer of 'Black' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'Lambda': All components of the > background layer of 'Regular' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'Lambda': All components of the > background layer of 'Black' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'AE': All components of the > background layer of 'Regular' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'AE': All components of the > background layer of 'Black' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'AE': All components of the > background layer of 'Italic' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'C': All components of the > background layer of 'Regular' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'C': All components of the > background layer of 'Black' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'C': All components of the > background layer of 'Black Italic' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'F': All components of the > background layer of 'Regular' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'F': All components of the > background layer of 'Black' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'G': All components of the > background layer of 'Regular' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'G': All components of the > background layer of 'Black' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'G': All components of the > background layer of 'Black Italic' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'G.1': All components of the > background layer of 'Regular' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'G.1': All components of the > background layer of 'Black' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'uni01F6': All components of the > background layer of 'Regular' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'uni01F6': All components of the > background layer of 'Black' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'Khook': All components of the > background layer of 'Regular' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'Khook': All components of the > background layer of 'Black' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'Khook': All components of the > background layer of 'Italic' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'Khook': All components of the > background layer of 'Black Italic' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'Rx': All components of the > background layer of 'Regular' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'Rx': All components of the > background layer of 'Italic' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'Thook': All components of the > background layer of 'Regular' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'Thook': All components of the > background layer of 'Black' will be decomposed. > WARNING:glyphsLib.builder.components:Glyph 'ae': All components of the > background layer of 'Regular' will be decomposed. >
Bug#226774: marked as done (sudo: Reorganize manpage for sudoers)
Your message dated Tue, 23 Feb 2021 07:46:35 +0100 with message-id and subject line Re: Bug#226774: sudo: Reorganize manpage for sudoers has caused the Debian Bug report #226774, regarding sudo: Reorganize manpage for sudoers to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 226774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=226774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sudo Version: 1.6.6-1.1 Severity: wishlist The manpage for sudoers is somewhat difficult to use because there is a long list of flags and parameters in the middle: To get an overview over the syntax of the sudoers file, one has to move many times between the EBNF sections before and behind the list. I propose that the sections called "Flags:" up to "Lists that can be used in a boolean context" are moved to the end of the manpage, just before the "EXAMPLES" section. -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux daedalus 2.2.20 #1 Sat Apr 20 11:45:28 EST 2002 i686 Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro Versions of packages sudo depends on: ii libc6 2.2.5-11.5 GNU C Library: Shared libraries an ii libpam-modules0.72-35Pluggable Authentication Modules f ii libpam0g 0.72-35Pluggable Authentication Modules l --- End Message --- --- Begin Message --- Version: 1.8.27 On Mon, Feb 22, 2021 at 09:47:07PM +0100, Markus Redeker wrote: > It looks as if the rework took place: The man page now contains a lot > of explanations and examples besides the EBNF. > > So let us close the bug report. Thanks for reporting back. Closing the bug for the version in buster. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421--- End Message ---
Bug#983213: marked as done (ukui-control-center: Missing dependency on libglib2.0-bin)
Your message dated Tue, 23 Feb 2021 06:26:16 + with message-id and subject line Bug#983213: fixed in ukui-control-center 3.0.2-2 has caused the Debian Bug report #983213, regarding ukui-control-center: Missing dependency on libglib2.0-bin to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ukui-control-center Version: 3.0.2-1 Severity: serious https://piuparts.debian.org/sid/fail/ukui-control-center_3.0.2-1.log ... Setting up ukui-control-center (3.0.2-1) ... /var/lib/dpkg/info/ukui-control-center.postinst: 5: glib-compile-schemas: not found dpkg: error processing package ukui-control-center (--configure): installed ukui-control-center package post-installation script subprocess returned error exit status 127 ... --- End Message --- --- Begin Message --- Source: ukui-control-center Source-Version: 3.0.2-2 Done: handsome_feng We believe that the bug you reported is fixed in the latest version of ukui-control-center, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. handsome_feng (supplier of updated ukui-control-center package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Feb 2021 06:44:50 + Source: ukui-control-center Architecture: source Version: 3.0.2-2 Distribution: unstable Urgency: medium Maintainer: Kylin Team Changed-By: handsome_feng Closes: 983213 Changes: ukui-control-center (3.0.2-2) unstable; urgency=medium . * debian/control: Add libglib2.0-bin to depends. (Closes: #983213) Checksums-Sha1: 3f37965d656d2b1efc30f36c27b87a3d8f7dc433 2626 ukui-control-center_3.0.2-2.dsc 97dddf9d5ab450632dd098dd9a7f571ffd1ec61a 5762344 ukui-control-center_3.0.2.orig.tar.gz 5821f8618192389375e2a8b1f66dd4a393b5 3768 ukui-control-center_3.0.2-2.debian.tar.xz 80180d8d98112582c4dcf09388e13556fc22f239 19769 ukui-control-center_3.0.2-2_source.buildinfo Checksums-Sha256: b487d7e7de10e7c00d44ce2c1b7a8b22720c808248f6c0ff7a0e2a272fc191fe 2626 ukui-control-center_3.0.2-2.dsc d7237c5c50958bc108805473c451f92ee5e7d51a4b19298554fc63262f04c2e5 5762344 ukui-control-center_3.0.2.orig.tar.gz 0cf534acca780bd21bbe27b78c5bf51943b455a6639d9bf6d8dce5d316f74fa6 3768 ukui-control-center_3.0.2-2.debian.tar.xz a98af5d68d4d9d20683b5759d743dceff9397fb69a348356ffa4ee1938198f73 19769 ukui-control-center_3.0.2-2_source.buildinfo Files: 05f80e488330497807dfaf2280228100 2626 x11 optional ukui-control-center_3.0.2-2.dsc a847a2b7156147941411393b4aad39ba 5762344 x11 optional ukui-control-center_3.0.2.orig.tar.gz 357e44dce31d427564b81aea98c9e79d 3768 x11 optional ukui-control-center_3.0.2-2.debian.tar.xz 0c2f35211e83a0b82fff00fb48d78ddf 19769 x11 optional ukui-control-center_3.0.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJPBAEBCAA5FiEEhsgAHpUwnacZWWSCm7hQwBMRHwwFAmA0l2gbHGppYW5mZW5n bGlAdWJ1bnR1a3lsaW4uY29tAAoJEJu4UMATER8MMUIP/jTWv85h/EEeK2DZsiow PPPJ1ERMkMipmH54Z2K1I3nI9BmSEEJH+6932KkK5sNk+ZMtDTNNDXRhc1pVYRi+ cyHnvKXXxjB3Ql2Iw7PhvLIs9FjcykwiLaP6WowAZMFTGFifsg9Z5G6ghQdXHED8 zFZW8KEpMfdh6/C06jTSI4iAT43tfplTjK08MyqXR29p+hICzPvvEZ9pzoARtIeD Z39azII9ltpnw8+WvvInDu2jTVgV6UYL+I3XMsKIE6hg18XQgKpoPFEj27Z/BW+c ZcDGgu7QiWSJoOwE/gFOPEO8ijdcUwjKR32R0Vpjh3yRYgkEDM1lwPXsPPRAc/5e BHuoChbYZ+8VoR8TaEOZ8LPbQs85nKqPDG+PuxpNeyukHCllJKiX8WZdDh/beeY2 DiJzWfq1iwXrygv2qBVHtSurUHDJ3HICWwQcq56OpUXu91czGbMP/jrZGo1No1t7 H7GYVAk+5U0EJrLfhW1MWcApQa7v6AYQkGO6GOLz9wvr0+JHLaAwy54ln21nl2fx iGRuYEsyQgrkBzJSUbDDQ8Kn2q9T/0JNjsXbuR5+9SqEbzu6G4z8/zlkJMB8Sp6k dToCP6uU+aBn7vVah4tF/bRyWIz+d2RLaZmB2ec6DrYh3jZqJ2dPtJVB61I+tq/O Mk4OUgFWwtxVBvHWVe3xq2Tw =5/57 -END PGP SIGNATURE End Message ---
Bug#983300: marked as done (new upstream (4.6.0))
Your message dated Tue, 23 Feb 2021 05:18:37 + with message-id and subject line Bug#983300: fixed in twitter-bootstrap4 4.6.0+dfsg1-1 has caused the Debian Bug report #983300, regarding new upstream (4.6.0) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: twitter-bootstrap4 Severity: normal Hi, bootstrap was updated to 4.6.0, it would be nice to have this in bullseye if possible, but at "least" in experimental, it fixes a bunch of issues I'm using locally (and would like to depend on the package, rather than to embedd bootstrap). Regards, Daniel --- End Message --- --- Begin Message --- Source: twitter-bootstrap4 Source-Version: 4.6.0+dfsg1-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of twitter-bootstrap4, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated twitter-bootstrap4 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Feb 2021 05:57:14 +0100 Source: twitter-bootstrap4 Architecture: source Version: 4.6.0+dfsg1-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 983300 Changes: twitter-bootstrap4 (4.6.0+dfsg1-1) experimental; urgency=medium . * Ignore beta versions * New upstream version 4.6.0+dfsg1 (Closes: #983300) * Update doc Checksums-Sha1: 4eae1eb506826ff7f50386681d439783061dcca9 2353 twitter-bootstrap4_4.6.0+dfsg1-1.dsc 775f6d15720f799530f7c15ef1ce11e5b25744dd 2326844 twitter-bootstrap4_4.6.0+dfsg1.orig.tar.xz 85a40cdfeb01e9b7b9f694b30eec09875c07c786 18868 twitter-bootstrap4_4.6.0+dfsg1-1.debian.tar.xz Checksums-Sha256: 59cbfa17a052f1cab1fe0e7bda6e69e64d70569cb5599b5ed74edde1a0a77c7d 2353 twitter-bootstrap4_4.6.0+dfsg1-1.dsc 9e32c087b9c979d7fe088b82630bab50c4bed0fd7c91ec9e0639efbd467e8bdc 2326844 twitter-bootstrap4_4.6.0+dfsg1.orig.tar.xz ccf3204f5b540577e969ef1fe3b58c09ac5c33840e356556b4ea93b2f06cdc6f 18868 twitter-bootstrap4_4.6.0+dfsg1-1.debian.tar.xz Files: c6abe65b5eac351db160d8739d10105e 2353 javascript optional twitter-bootstrap4_4.6.0+dfsg1-1.dsc b83099d46aff96e88b708ccfa07cfa66 2326844 javascript optional twitter-bootstrap4_4.6.0+dfsg1.orig.tar.xz 2eb87a303ab798cbcf91abeb15beff57 18868 javascript optional twitter-bootstrap4_4.6.0+dfsg1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmA0i7AACgkQ9tdMp8mZ 7ulxqw//eVbIfcKxoXjhsENuSkCVraou8VwelPAnv3pAhT/mrCTLmpDjLkO1mzyY L7cAn/qfF4NEOraPbcS6WUwoMqjAlQuJGf9OTNn5OMcQ7ML4CFQF4aOXdMcCrOQ9 M8ULTzeoovVu+sbi+5Q3T1w8QR+mxdaxJir1mzcuAEKyc3wk7CQDhA8QRNM9Tfdu ODLSWNqyCGWL59CbhS0dMPAIqY0vmjFmR0C/wDLcrp4E+1bZBvclqOYSk+RcxaDN /uewwuZxHcyBvbktHp8i8K81+j697ETPwJR5oku/Z18QB8txHIw5JCWEVHZuG76f Qy9D+DaSfB/OUGKA7LzOdr6GNvrbEJ61+xDWHxH0bSK+mmRJYwhnWDY9uLFCVTer VoOflWjuABkgRTpkT3a4BDrK4kqyWHsGbuDgeaejZIrUI8t2niZQdThNld2oMkFd IQmOU4Bm6RXWSTv2qP/RtPy/UaAss7IhM1GSr4sZsXOSymON93Cn3n/3Ez8RxuQb RXdRY43o18nS/8Tc40nwRBSiAjaM5GwGaXF8FH7Szt/s5qNG20FaTj1W0ohR1V5d q/GAOG08nYJna/XcuWuBce4tNVoPVMUWAgiKp7IP/nHKPja5eJ8RTlbTuVlfMImS zNQk7q3H9wS/SRGN7HsoWQFbFbNk0BDdX3IKL1hfHHBzsVwpfQw= =He58 -END PGP SIGNATURE End Message ---
Bug#982992: marked as done (node-regjsparser breaks node-regexpu-core autopkgtest: Missing expected exception (Error).)
Your message dated Tue, 23 Feb 2021 05:46:08 +0100 with message-id <4cac9906-78fb-94f1-c5fd-01dfe3903...@debian.org> and subject line Fixed has caused the Debian Bug report #982992, regarding node-regjsparser breaks node-regexpu-core autopkgtest: Missing expected exception (Error). to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-regjsparser, node-regexpu-core Control: found -1 node-regjsparser/0.6.6+ds-1 Control: found -1 node-regexpu-core/4.7.1-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of node-regjsparser the autopkgtest of node-regexpu-core fails in testing when that autopkgtest is run with the binary packages of node-regjsparser from unstable. It passes when run with only packages from testing. In tabular form: passfail node-regjsparser from testing0.6.6+ds-1 node-regexpu-core from testing4.7.1-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of node-regjsparser to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=node-regjsparser https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-regexpu-core/10530585/log.gz 718 passing (816ms) 1 failing 1) unicodePropertyEscapes throws without the `u` flag: AssertionError [ERR_ASSERTION]: Missing expected exception (Error). at Context. (tests/tests.js:592:10) at callFn (/usr/share/nodejs/mocha/lib/runnable.js:364:21) at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:352:5) at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:677:10) at /usr/share/nodejs/mocha/lib/runner.js:801:12 at next (/usr/share/nodejs/mocha/lib/runner.js:594:14) at /usr/share/nodejs/mocha/lib/runner.js:604:7 at next (/usr/share/nodejs/mocha/lib/runner.js:486:14) at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:572:5) at processImmediate (internal/timers.js:461:21) OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 23284--- End Message ---
Bug#983370: marked as done (uim-anthy: does not respect UTF-8)
Your message dated Tue, 23 Feb 2021 04:18:31 + with message-id and subject line Bug#983370: fixed in uim 1:1.8.8-8 has caused the Debian Bug report #983370, regarding uim-anthy: does not respect UTF-8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: uim-anthy Version: 1:1.8.8-7 Severity: important Dear Maintainer, uim-anthy installs EUC-JP (anthy) and UTF-8 (anthy-utf8) modules. However, the module order does not respect UTF-8: currently anthy EUC-JP module is the default. This is critical to normal UTF-8 installations. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/1 CPU thread) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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 uim-anthy depends on: ii anthy 1:0.4-2 ii uim 1:1.8.8-7 ii uim-data 1:1.8.8-7 uim-anthy recommends no packages. uim-anthy suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: uim Source-Version: 1:1.8.8-8 Done: HIGUCHI Daisuke (VDR dai) We believe that the bug you reported is fixed in the latest version of uim, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. HIGUCHI Daisuke (VDR dai) (supplier of updated uim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 23 Feb 2021 12:33:54 +0900 Source: uim Architecture: source Version: 1:1.8.8-8 Distribution: unstable Urgency: medium Maintainer: HIGUCHI Daisuke (VDR dai) Changed-By: HIGUCHI Daisuke (VDR dai) Closes: 983370 Changes: uim (1:1.8.8-8) unstable; urgency=medium . [ YOSHINO Yoshihito ] * uim-anthy: prefer UTF-8 module (Closes: #983370) Checksums-Sha1: ad98734e6292bbc70c9cfce2ebec551c59fcff64 3639 uim_1.8.8-8.dsc 61e46504c24a5cf9811ad576201578957808c3a5 38768 uim_1.8.8-8.debian.tar.xz Checksums-Sha256: 8435715608363d7c1ed2b4721c5558a50660629ba3e432ad3d6662f7c4c3f3c2 3639 uim_1.8.8-8.dsc 07ae968e5f29489c626a6637ab856596c9c21a19a6710e54ba8783b1c9431946 38768 uim_1.8.8-8.debian.tar.xz Files: 7c673c8d4bf40a8aaf08b433d71071d2 3639 libs optional uim_1.8.8-8.dsc b2a480aaea82a78b4f470aab44c7894e 38768 libs optional uim_1.8.8-8.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEECynYjkLmt2W42OpQeDlhndQ5Zo4FAmA0fcQACgkQeDlhndQ5 Zo6dDxAAsJwmxeWNGFw7e2chjaojTuXBDzh26AEzRYrhjSpgagfdQo6rartZ8RBC 4z5WlKasakkMzuzzY43i8ncCRadIASVjGQMz97umVh4fP3OuYGhJUNhwnKsrKOS5 CpZ5HfC5wL3FMSk0TvKydJu5dSQFhYwrItsu4ci59441F/BQAiw63c0ZVHbAoIw0 qwAAMFW/atKKmSrKcC8jE/20thO0vHIlrNoqyd3nG0YG0Zf7JDoEBclCIgqCB7nc pVilMy59DE6lMSeQ0qTBX3PZN4bIveaMntLa65P/pHmOQEsEOUY/S3x//iNrvY4Z voC9q1BjD70Uanhc4GsRD4cAZ7AxLc7b/5SJWSoFCdDdZH2OsPOYI+cvoJAxTqQr 2F0ZuXCWPvYkEq9nDDzppVR1bY0mTc1ZzgKJXCsxd88SSYQQXuRJcPYMsBrmwbIT ESpaovnecr9pgxILRS4TYQQjRTF1MTlUt9zDKHKtwCXrxP7Coa/uovwitNHdcOOy 8Gqp6Skemsx/LvL9epei2SNM6gl0+X2EbqoIxGPTjXAYLJLSAayqLYuRfdvgi3nf pJXBufN2By1M0+sZuoHk2pt+P20ZgvH19X8xUDJiFQhsaa5EvUIQpOp4EN7Yr6kr wRju3WYlSfHRVwKIDrQ9ZNoJIiIiGCpwJutv1l0MURkKPktA9KU= =lTv2 -END PGP SIGNATURE End Message ---
Bug#980686: marked as done (ldc: FTBFS: dh_auto_configure: error: cd bootstrap-stage2 && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCAL
Your message dated Tue, 23 Feb 2021 02:17:48 + with message-id and subject line Bug#980686: fixed in ldc 1:1.24.0-2 has caused the Debian Bug report #980686, regarding ldc: FTBFS: dh_auto_configure: error: cd bootstrap-stage2 && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DD_COMPILER=/<>/bootstrap-stage1/bin/ldmd2 -DBUILD_SHARED_LIBS=OFF -DINCLUDE_INSTALL_DIR=/usr/lib/ldc/x86_64-linux-gnu/include/d .. returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ldc Version: 1:1.24.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/bootstrap-stage1' > [ 93%] Linking C shared library ../lib/libphobos2-ldc-shared.so > cd /<>/bootstrap-stage1/runtime && /usr/bin/cmake -E > cmake_link_script CMakeFiles/phobos2-ldc-shared.dir/link.txt --verbose=1 > /usr/bin/cc -fPIC -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_UNISTD_H > -Wl,-z,relro -shared -Wl,-soname,libphobos2-ldc-shared.so.94 -o > ../lib/libphobos2-ldc-shared.so.2.0.94 objects/etc/c/curl.o > objects/etc/c/odbc/sql.o objects/etc/c/odbc/sqlext.o > objects/etc/c/odbc/sqltypes.o objects/etc/c/odbc/sqlucode.o > objects/etc/c/sqlite3.o objects/etc/c/zlib.o > objects/std/algorithm/comparison.o objects/std/algorithm/internal.o > objects/std/algorithm/iteration.o objects/std/algorithm/mutation.o > objects/std/algorithm/package.o objects/std/algorithm/searching.o > objects/std/algorithm/setops.o objects/std/algorithm/sorting.o > objects/std/array.o objects/std/ascii.o objects/std/base64.o > objects/std/bigint.o objects/std/bitmanip.o objects/std/compiler.o > objects/std/complex.o objects/std/concurrency.o objects/std/container/array.o > objects/std/container/binaryheap.o objects/std/container/dlist.o > objects/std/container/package.o objects/std/container/rbtree.o > objects/std/container/slist.o objects/std/container/util.o objects/std/conv.o > objects/std/csv.o objects/std/datetime/date.o objects/std/datetime/interval.o > objects/std/datetime/package.o objects/std/datetime/stopwatch.o > objects/std/datetime/systime.o objects/std/datetime/timezone.o > objects/std/demangle.o objects/std/digest/crc.o objects/std/digest/digest.o > objects/std/digest/hmac.o objects/std/digest/md.o > objects/std/digest/murmurhash.o objects/std/digest/package.o > objects/std/digest/ripemd.o objects/std/digest/sha.o objects/std/encoding.o > objects/std/exception.o > objects/std/experimental/allocator/building_blocks/affix_allocator.o > objects/std/experimental/allocator/building_blocks/aligned_block_list.o > objects/std/experimental/allocator/building_blocks/allocator_list.o > objects/std/experimental/allocator/building_blocks/ascending_page_allocator.o > objects/std/experimental/allocator/building_blocks/bitmapped_block.o > objects/std/experimental/allocator/building_blocks/bucketizer.o > objects/std/experimental/allocator/building_blocks/fallback_allocator.o > objects/std/experimental/allocator/building_blocks/free_list.o > objects/std/experimental/allocator/building_blocks/free_tree.o > objects/std/experimental/allocator/building_blocks/kernighan_ritchie.o > objects/std/experimental/allocator/building_blocks/null_allocator.o > objects/std/experimental/allocator/building_blocks/package.o > objects/std/experimental/allocator/building_blocks/quantizer.o > objects/std/experimental/allocator/building_blocks/region.o > objects/std/experimental/allocator/building_blocks/scoped_allocator.o > objects/std/experimental/allocator/building_blocks/segregator.o > objects/std/experimental/allocator/building_blocks/stats_collector.o > objects/std/experimental/allocator/common.o > objects/std/experimental/allocator/gc_allocator.o > objects/std/experimental/allocator/mallocator.o > objects/std/experimental/allocator/mmap_allocator.o > objects/std/experimental/allocator/package.o >
Bug#983101: marked as done (ceres-solver FTBFS: rm: cannot remove 'debian/tmp/usr/share/doc/ceres/html/_static/js/html5shiv-printshiv.min.js': No such file or directory)
Your message dated Mon, 22 Feb 2021 23:18:33 + with message-id and subject line Bug#983101: fixed in ceres-solver 1.14.0-14 has caused the Debian Bug report #983101, regarding ceres-solver FTBFS: rm: cannot remove 'debian/tmp/usr/share/doc/ceres/html/_static/js/html5shiv-printshiv.min.js': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ceres-solver Version: 1.14.0-13 Severity: serious Tags: ftbfs ceres-solver fails to build from source in unstable. A build ends with: | rm debian/tmp/usr/share/doc/ceres/html/_static/js/html5shiv-printshiv.min.js | rm: cannot remove 'debian/tmp/usr/share/doc/ceres/html/_static/js/html5shiv-printshiv.min.js': No such file or directory | make[1]: *** [debian/rules:77: override_dh_installdocs] Error 1 | make[1]: Leaving directory '/build/1st/ceres-solver-1.14.0' | make: *** [debian/rules:50: binary] Error 2 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 This is also reproducible by reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ceres-solver_1.14.0-13.rbuild.log.gz Given that ceres-solver is messing with sphinx-induces javascript files, I wonder whether dh_sphinxdoc could help here. If you intend to use it, please request it via "Build-Depends-Indep: dh-sequence-sphinxdoc". Helmut --- End Message --- --- Begin Message --- Source: ceres-solver Source-Version: 1.14.0-14 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of ceres-solver, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated ceres-solver package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 21:34:16 +0100 Source: ceres-solver Architecture: source Version: 1.14.0-14 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Anton Gladky Closes: 983101 Changes: ceres-solver (1.14.0-14) unstable; urgency=medium . * [9cb79f7] Disable failure on file remove. (Closes: #983101) Checksums-Sha1: 5c2ec20564378dcc51ec00227b593c62055da800 2453 ceres-solver_1.14.0-14.dsc d1330c5391aacac162dce8b190365bc79a0a194c 7428 ceres-solver_1.14.0-14.debian.tar.xz 494df490c85e4747a33bd51e008a73c573be5244 9192 ceres-solver_1.14.0-14_source.buildinfo Checksums-Sha256: fefd59fee99f8b42facbf74bc2fcd04a5423297fe6c8ea5d4a7ad899ec3320de 2453 ceres-solver_1.14.0-14.dsc 3a1717620bdf3192f4b76b1eaed1550327a82c29d80b43519990ba5055df7e7f 7428 ceres-solver_1.14.0-14.debian.tar.xz f168e22d1f26eaa568fed34c8701025dd7e28694f5328cf6e1d720bb18564587 9192 ceres-solver_1.14.0-14_source.buildinfo Files: 1bf1fbe8c1998605428fdf962691f3ea 2453 math optional ceres-solver_1.14.0-14.dsc c4affe1030bdbe42302425e2654c8325 7428 math optional ceres-solver_1.14.0-14.debian.tar.xz ac05d9cbdabfee58c2449ebcc766fe75 9192 math optional ceres-solver_1.14.0-14_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmA0OUQACgkQ0+Fzg8+n /waRCw/+NUGNRHEVyfMFV9Vhw7OaqdTSSzgBtalZP92mtVxM6UcShyGuxdRyY8Jh Ctyj8Ch1FXfaWAQZeQBSKmQ1gUhvyZOuhOX9Sq5jeDmQJjyX9kGWs1FgDLRNgaZG ZV3VQEpPyF9QmUi/MaCYUcqdJZp3WE3+ba/7Gh7FvVgUYqsRNiHWCXeVmWHk9rbg CMgoVlTkh1E//luAakjj0aMvcV1kWJLkQg9aF7l01DmLjyKXUS2iIrQI3Tz9qCMl HWqYUWV6bm07jaix1yZryDOEbMhTpIfHMBSpDgq6rWJVGTFxwSXmUFIlVNM9uuFO +MpFdPlVEFxaE3Y457bKY9xjzNY0MUIx9NioidhnoCbBT8LR74o+gaNhzD35F4JR sysMHoQB+DAoqVjO/hA5oKr3hC25uDK22OF4dT/GEdSO4RbEzC3zMAPoE8VX5NzX GYsMWuMQ/xgzxuzMfPC8uigrXN4mckgkxUUOagUf254gE1MS5xoizUCqiTVjY9uG Z8eFt7MstL7xadyeX5FZSihlss5/MY4iNF97xNiZ8Qw73x+sJYqf8iZZr8LcvFqX YlGzey6OMTEF/CZHsbNS/B8iNJntH2XPjkSVvgdZIuPc81K4kLdACdVX9BXBgvSD e6I/02ljFG09/pL1wy/I7qKAX0+AIAtYLEOONX2VgBSp3K1pzto= =qN/C -END PGP SIGNATURE End Message ---
Bug#804078: marked as done (pssh manpages: bad descriptions in NAME sections)
Your message dated Mon, 22 Feb 2021 23:18:55 + with message-id and subject line Bug#804078: fixed in pssh 2.3.1-4 has caused the Debian Bug report #804078, regarding pssh manpages: bad descriptions in NAME sections to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 804078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804078 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pssh Version: 2.3.1-1 Severity: minor $ for k in rsync scp slurp; do man parallel-$k | sed -n -e 4p; done parallel-rsync -- parallel process kill program parallel-scp -- parallel process kill program parallel-slurp -- parallel process kill program But these tools are for file copying, not for killing... -- Jakub Wilk --- End Message --- --- Begin Message --- Source: pssh Source-Version: 2.3.1-4 Done: Hilmar Preusse We believe that the bug you reported is fixed in the latest version of pssh, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 804...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilmar Preusse (supplier of updated pssh package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Feb 2021 00:02:07 +0100 Source: pssh Architecture: source Version: 2.3.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Hilmar Preusse Closes: 803940 804077 804078 Changes: pssh (2.3.1-4) unstable; urgency=medium . * Fix typos in manual pages, thanks to Jakub Wilk (Closes: #803940, #804077). * Get commit 86e308c6bd62b3422d3e5a95ef1d330ce167171d from upstream (and adapt it for Debian specific man pages) (Closes: #804078). Checksums-Sha1: 717b403801b7a8a0686ab053f3236321370c 2072 pssh_2.3.1-4.dsc 9c3cd227d041735a049900f0569dbef3485b9d31 9476 pssh_2.3.1-4.debian.tar.xz 252973599ac999a6e1bba7636beeaf4563a02042 6164 pssh_2.3.1-4_source.buildinfo Checksums-Sha256: 3d61b7fe368d0e4c4297163769583cf8282e7c22c5a066a9b8695cc9a30d517e 2072 pssh_2.3.1-4.dsc b430295e83a2b19258b3f1c369182f6925db467fa74adadd2615f158f5744d74 9476 pssh_2.3.1-4.debian.tar.xz 16f49694a22cc7feedae20091b95016f41e043c659f5dd00ba7e946da1f50299 6164 pssh_2.3.1-4_source.buildinfo Files: 52c4f1f5846c59f0d3b6b6c4a295aea9 2072 net optional pssh_2.3.1-4.dsc cc3e2c02b427518cf3f4826f0b9846c1 9476 net optional pssh_2.3.1-4.debian.tar.xz d25027d69b897722431a201c676523d6 6164 net optional pssh_2.3.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEaXGmC/nkbIhxf16kxiZYRqvgLIsFAmA0OChfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY5 NzFBNjBCRjlFNDZDODg3MTdGNUVBNEM2MjY1ODQ2QUJFMDJDOEIACgkQxiZYRqvg LIuwvg/8C5LoRmiWpYxooTW1ysg3Y5WFFokGRCHz6/KrOI+PNwhGwpBuOr8Rn5e4 56P5TfyMNNuOxwZ/ppG03px9ssnptYWyPwTUdkYp8TB3ihk/jXnragU/1dCUQQiH 46tGl/9WAwQbGpGtIDWH5uZ8Xg55bmeSfXoMTHkz2qK3vZQaGQfSWFAMgJMhD8DO swwJj3WQXJj0eVgikpXEG8soCETGy2oiWyY2LZsF3CVUsaT5bEh+Y+u46E1Z5gN2 lZLzf0FmbtdaPw/JovA8Wg5Zl5ZISVOjgNrUV2Vs5FPMxlHOlo3chU8Dw1p0NjBp lsxvXJmKF+a3H9WfMKqxnypHiiG88QTklsfd9RyVqIGj3XwrmY5e7tOGNYzBjthM mclWmIznsAeNjeIT3+XweFWbqmRQgrcb3WxrVJVE4ka4wXeAVx17MbAp6Q0JHPRA dw5nhIq2fBt/lrvNGSPzxVuVCjG8EGzBnNAvlAQ9pk/6aghM7j43oQ2fwt6/ZJZl 2MPsEYXuoWxefAnHeXx28iAPFqjjKLKfWtii41/Bxci86Ww9O4R8bL9KXz76kWB6 tHE9seBNgCZfL3GYcg547kYvZFmmgujpjc6tmpru23gKnBohOorV+ckrk5GoS3xA YLZjxH35M+k2bkxTgOOB0KOy/3Hbw3Ex33teOxwDMThd5E9ydhM= =1GFg -END PGP SIGNATURE End Message ---
Bug#804077: marked as done (parallel-ssh manpage: typo: paralllel -> parallel)
Your message dated Mon, 22 Feb 2021 23:18:55 + with message-id and subject line Bug#804077: fixed in pssh 2.3.1-4 has caused the Debian Bug report #804077, regarding parallel-ssh manpage: typo: paralllel -> parallel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 804077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pssh Version: 2.3.1-1 Severity: minor $ man parallel-ssh | grep lll paralllel-ssh(1)General Commands Manual paralllel-ssh(1) paralllel-ssh -- parallel ssh program paralllel-ssh [-vAiIP] [-h hosts_file] [-H [user@]host[:port]] [-l paralllel-ssh -I [-vAiIP] [-h hosts_file] [-H [user@]host[:port]] [-l paralllel-ssh is a program for executing ssh in parallel on a number of given (the -h option is used more than once), then paralllel-ssh host is specified multiple times, then paralllel-ssh will con- With a value of 0, paralllel-ssh will not timeout any connec- The exit status codes from paralllel-ssh are as follows: January 24, 2012 paralllel-ssh(1) Of course it should be s/lll/ll/. -- Jakub Wilk --- End Message --- --- Begin Message --- Source: pssh Source-Version: 2.3.1-4 Done: Hilmar Preusse We believe that the bug you reported is fixed in the latest version of pssh, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 804...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilmar Preusse (supplier of updated pssh package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Feb 2021 00:02:07 +0100 Source: pssh Architecture: source Version: 2.3.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Hilmar Preusse Closes: 803940 804077 804078 Changes: pssh (2.3.1-4) unstable; urgency=medium . * Fix typos in manual pages, thanks to Jakub Wilk (Closes: #803940, #804077). * Get commit 86e308c6bd62b3422d3e5a95ef1d330ce167171d from upstream (and adapt it for Debian specific man pages) (Closes: #804078). Checksums-Sha1: 717b403801b7a8a0686ab053f3236321370c 2072 pssh_2.3.1-4.dsc 9c3cd227d041735a049900f0569dbef3485b9d31 9476 pssh_2.3.1-4.debian.tar.xz 252973599ac999a6e1bba7636beeaf4563a02042 6164 pssh_2.3.1-4_source.buildinfo Checksums-Sha256: 3d61b7fe368d0e4c4297163769583cf8282e7c22c5a066a9b8695cc9a30d517e 2072 pssh_2.3.1-4.dsc b430295e83a2b19258b3f1c369182f6925db467fa74adadd2615f158f5744d74 9476 pssh_2.3.1-4.debian.tar.xz 16f49694a22cc7feedae20091b95016f41e043c659f5dd00ba7e946da1f50299 6164 pssh_2.3.1-4_source.buildinfo Files: 52c4f1f5846c59f0d3b6b6c4a295aea9 2072 net optional pssh_2.3.1-4.dsc cc3e2c02b427518cf3f4826f0b9846c1 9476 net optional pssh_2.3.1-4.debian.tar.xz d25027d69b897722431a201c676523d6 6164 net optional pssh_2.3.1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEaXGmC/nkbIhxf16kxiZYRqvgLIsFAmA0OChfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY5 NzFBNjBCRjlFNDZDODg3MTdGNUVBNEM2MjY1ODQ2QUJFMDJDOEIACgkQxiZYRqvg LIuwvg/8C5LoRmiWpYxooTW1ysg3Y5WFFokGRCHz6/KrOI+PNwhGwpBuOr8Rn5e4 56P5TfyMNNuOxwZ/ppG03px9ssnptYWyPwTUdkYp8TB3ihk/jXnragU/1dCUQQiH 46tGl/9WAwQbGpGtIDWH5uZ8Xg55bmeSfXoMTHkz2qK3vZQaGQfSWFAMgJMhD8DO swwJj3WQXJj0eVgikpXEG8soCETGy2oiWyY2LZsF3CVUsaT5bEh+Y+u46E1Z5gN2 lZLzf0FmbtdaPw/JovA8Wg5Zl5ZISVOjgNrUV2Vs5FPMxlHOlo3chU8Dw1p0NjBp lsxvXJmKF+a3H9WfMKqxnypHiiG88QTklsfd9RyVqIGj3XwrmY5e7tOGNYzBjthM mclWmIznsAeNjeIT3+XweFWbqmRQgrcb3WxrVJVE4ka4wXeAVx17MbAp6Q0JHPRA dw5nhIq2fBt/lrvNGSPzxVuVCjG8EGzBnNAvlAQ9pk/6aghM7j43oQ2fwt6/ZJZl 2MPsEYXuoWxefAnHeXx28iAPFqjjKLKfWtii41/Bxci86Ww9O4R8bL9KXz76kWB6 tHE9seBNgCZfL3GYcg547kYvZFmmgujpjc6tmpru23gKnBohOorV+ckrk5GoS3xA YLZjxH35M+k2bkxTgOOB0KOy/3Hbw3Ex33teOxwDMThd5E9ydhM= =1GFg -END PGP SIGNATURE End Message ---
Bug#803940: marked as done (pssh manpages: typo: "... and \ options")
Your message dated Mon, 22 Feb 2021 23:18:55 + with message-id and subject line Bug#803940: fixed in pssh 2.3.1-4 has caused the Debian Bug report #803940, regarding pssh manpages: typo: "... and \ options" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 803940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pssh Version: 2.3.1-1 Severity: minor Tags: patch Description of the --verbose option in the manpage reads: "Include error messages from ssh with the -i and \ options." It should be: "... with the -i and -e options." -- Jakub Wilk diff --git a/debian/parallel-nuke.1 b/debian/parallel-nuke.1 --- a/debian/parallel-nuke.1 +++ b/debian/parallel-nuke.1 @@ -188,7 +188,7 @@ Include error messages from ssh with the .B \-i and -.B \e +.B \-e options. diff --git a/debian/parallel-rsync.1 b/debian/parallel-rsync.1 --- a/debian/parallel-rsync.1 +++ b/debian/parallel-rsync.1 @@ -191,7 +191,7 @@ Include error messages from rsync with the .B \-i and -.B \e +.B \-e options. .TP diff --git a/debian/parallel-scp.1 b/debian/parallel-scp.1 --- a/debian/parallel-scp.1 +++ b/debian/parallel-scp.1 @@ -189,7 +189,7 @@ Include error messages from ssh with the .B \-i and -.B \e +.B \-e options. .TP diff --git a/debian/parallel-slurp.1 b/debian/parallel-slurp.1 --- a/debian/parallel-slurp.1 +++ b/debian/parallel-slurp.1 @@ -191,7 +191,7 @@ Include error messages from ssh with the .B \-i and -.B \e +.B \-e options. .TP diff --git a/debian/parallel-ssh.1 b/debian/parallel-ssh.1 --- a/debian/parallel-ssh.1 +++ b/debian/parallel-ssh.1 @@ -233,7 +233,7 @@ Include error messages from ssh with the .B \-i and -.B \e +.B \-e options. .TP diff --git a/man/man1/pnuke.1 b/man/man1/pnuke.1 --- a/man/man1/pnuke.1 +++ b/man/man1/pnuke.1 @@ -188,7 +188,7 @@ Include error messages from ssh with the .B \-i and -.B \e +.B \-e options. diff --git a/man/man1/prsync.1 b/man/man1/prsync.1 --- a/man/man1/prsync.1 +++ b/man/man1/prsync.1 @@ -191,7 +191,7 @@ Include error messages from rsync with the .B \-i and -.B \e +.B \-e options. .TP diff --git a/man/man1/pscp.1 b/man/man1/pscp.1 --- a/man/man1/pscp.1 +++ b/man/man1/pscp.1 @@ -189,7 +189,7 @@ Include error messages from ssh with the .B \-i and -.B \e +.B \-e options. .TP diff --git a/man/man1/pslurp.1 b/man/man1/pslurp.1 --- a/man/man1/pslurp.1 +++ b/man/man1/pslurp.1 @@ -191,7 +191,7 @@ Include error messages from ssh with the .B \-i and -.B \e +.B \-e options. .TP diff --git a/man/man1/pssh.1 b/man/man1/pssh.1 --- a/man/man1/pssh.1 +++ b/man/man1/pssh.1 @@ -233,7 +233,7 @@ Include error messages from ssh with the .B \-i and -.B \e +.B \-e options. .TP --- End Message --- --- Begin Message --- Source: pssh Source-Version: 2.3.1-4 Done: Hilmar Preusse We believe that the bug you reported is fixed in the latest version of pssh, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 803...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilmar Preusse (supplier of updated pssh package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 23 Feb 2021 00:02:07 +0100 Source: pssh Architecture: source Version: 2.3.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Hilmar Preusse Closes: 803940 804077 804078 Changes: pssh (2.3.1-4) unstable; urgency=medium . * Fix typos in manual pages, thanks to Jakub Wilk (Closes: #803940, #804077). * Get commit 86e308c6bd62b3422d3e5a95ef1d330ce167171d from upstream (and adapt it for Debian specific man pages) (Closes: #804078). Checksums-Sha1: 717b403801b7a8a0686ab053f3236321370c 2072 pssh_2.3.1-4.dsc 9c3cd227d041735a049900f0569dbef3485b9d31 9476 pssh_2.3.1-4.debian.tar.xz 252973599ac999a6e1bba7636beeaf4563a02042 6164 pssh_2.3.1-4_source.buildinfo Checksums-Sha256: 3d61b7fe368d0e4c4297163769583cf8282e7c22c5a066a9b8695cc9a30d517e 2072 pssh_2.3.1-4.dsc b430295e83a2b19258b3f1c369182f6925db467fa74adadd2615f158f5744d74 9476 pssh_2.3.1-4.debian.tar.xz
Bug#898177: marked as done (cron doesn't support MAILFROM)
Your message dated Mon, 22 Feb 2021 23:03:29 + with message-id and subject line Bug#898177: fixed in cron 3.0pl1-137 has caused the Debian Bug report #898177, regarding cron doesn't support MAILFROM to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 898177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cron Version: 3.0pl1-128+deb9u1 Debian/Ubuntu's cron version doesn't support setting MAILFROM to set the "From:" header of cron generated emails. This feature would be nice to have and bring parity with RHEL/CentOS which has it since RHEL 6: $ cat /etc/redhat-release CentOS release 6.6 (Final) $ man 5 crontab | grep -1 FROM doesn´t do aliasing, and UUCP usually doesn´t read its mail. If MAIL- FROM is defined (and non-empty), it will be used as the envelope sender address, otherwise, ‘‘root’’ will be used. This bug was created first under ubuntu launchpad, but as the package is maintained in Debian project i open this bug issue. for Ubuntu the report and comments is here: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1750051 a patch has been submitted too https://launchpadlibrarian.net/369246026/patch_v2.txt this patch is heavily inspired by the cronie project https://github.com/cronie-crond/cronie/blob/master/src/do_command.c --- End Message --- --- Begin Message --- Source: cron Source-Version: 3.0pl1-137 Done: Christian Kastner We believe that the bug you reported is fixed in the latest version of cron, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 898...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Kastner (supplier of updated cron package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 23:43:24 +0100 Source: cron Architecture: source Version: 3.0pl1-137 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña Changed-By: Christian Kastner Closes: 898177 1750051 Changes: cron (3.0pl1-137) unstable; urgency=medium . [ Laurent Combe ] * Add patch Add-MAILFROM-environment-variable.patch (Closes: #898177, #1750051) . [ Christian Kastner ] * Modify the above patch to use cronie's safe_p() function for email validation * Remove myself from Uploaders Checksums-Sha1: 4f1598ada5e36ba5ed28181338768e1538413810 1898 cron_3.0pl1-137.dsc 073669dcc7793131fbceaf9c1fe307aa408fc632 107268 cron_3.0pl1-137.debian.tar.xz b687b4f08790f26c710b86758899fe820c939b7e 5403 cron_3.0pl1-137_source.buildinfo Checksums-Sha256: 3c9fbc0f0a4aa8d44ba871aa527af80dd562825db5a28073c3d816b1c04e983b 1898 cron_3.0pl1-137.dsc 031b6d906e94255e4e6e3ee55fba084c1cdd21cf23d7744bb6353e0ad2c5dcee 107268 cron_3.0pl1-137.debian.tar.xz df86f3710b42253b8d1e8f0d9732708ca379d50b723865cdf25b7c83c81327b5 5403 cron_3.0pl1-137_source.buildinfo Files: 527c540ff423540e109a082a7879e852 1898 admin important cron_3.0pl1-137.dsc 3129002e8546bc5b0aba6b2e1f86f857 107268 admin important cron_3.0pl1-137.debian.tar.xz db73b3c817f202e45ccd352a0943d221 5403 admin important cron_3.0pl1-137_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEQZ9+mkfDq5UZ8bCjOZU6N95Os2sFAmA0M6kPHGNra0BkZWJp YW4ub3JnAAoJEDmVOjfeTrNrM2gQALglR9YnMyRNJJC8sQnhCe+pr0BInzDSIpZe ItDOdrRj3zQ7ZMxjdmwXM035jNHObwz9vLstv+NUJcsSiE6PNN1qK43GSStlwmZP Gy2j1AxPLNHRNSWBvWW+oE8f8FE4yLhdUjtB8WrnP2RrAnX50cH46yO4rcfU0z+6 oJBvJ5sip44bzIu6YZT7MuZ5Udt8sRobVTLkK9cMfznhDKLWw7ptmcIGBE06vnxm V1N2naG1WO7JUuZT/uNASIr6ds5rbXREXVpDNzw5ohb66dTwm3LCakKMHCycwCDF gOjI89bxuXm60aYA+QdkiOPx2oE7HXXDFgwLNj4eL69VxUpPBCivECFEe6v5Ajdn lCahT9QM6SAz6b61e49wqZ2W2UU2u/FsjCjave+/oc32U1sTkgP4gyLVbApSJ2xK iyWN9sRWiaITIMxdaPXN605L0UeMzxejhR9NN4ggvpNIJaxfyQRhfn8jQpCUlFW/ rR5W9nOECwYhySiScfrT4QnQF/dMgUwhgxxMvChtNFUzjHvyyt9qWVLhk5bX326G 1hnoWROM3tE9uFmVQOVjyJCKPs9VCsffwHp9hEJ1k5+3VLLUuPQajOajFoymoWMN pJUliNXBtgJClVyOd41MNsi+lxFI45TyJX5XL+gqJsgDtmU9QqWjKjrLxBVzko8O OPd8mOfC =VKwq -END PGP SIGNATURE End Message ---
Bug#983238: marked as done (libbio-db-biofetch-perl: test failure if internet available)
Your message dated Mon, 22 Feb 2021 22:18:46 + with message-id and subject line Bug#983238: fixed in libbio-db-ncbihelper-perl 1.7.6-3 has caused the Debian Bug report #983238, regarding libbio-db-biofetch-perl: test failure if internet available to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbio-db-biofetch-perl Version: 1.7.3-3 Severity: serious Tags: ftbfs Justification: fails to build from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As seen on ci.debian.net: https://ci.debian.net/data/autopkgtest/testing/amd64/libb/libbio-db-biofetch-perl/10589851/log.gz the test suite can fail with: t/BioFetch.t .. ok 1 ok 2 ok 3 - An object of class 'Bio::Seq::RichSeq' isa 'Bio::SeqI' ok 4 ok 5 ok 6 - - EXCEPTION - MSG: BioFetch Error 12: No entries found. STACK Bio::DB::BioFetch::postprocess_data /usr/share/perl5/Bio/DB/BioFetch.pm:450 STACK Bio::DB::WebDBSeqI::_stream_request /usr/share/perl5/Bio/DB/WebDBSeqI.pm:769 STACK Bio::DB::WebDBSeqI::get_seq_stream /usr/share/perl5/Bio/DB/WebDBSeqI.pm:476 STACK Bio::DB::BioFetch::get_Stream_by_acc /usr/share/perl5/Bio/DB/BioFetch.pm:525 STACK Bio::DB::WebDBSeqI::get_Seq_by_acc /usr/share/perl5/Bio/DB/WebDBSeqI.pm:194 STACK toplevel t/BioFetch.t:32 - - - - EXCEPTION - MSG: acc J02231 does not exist STACK Bio::DB::WebDBSeqI::get_Seq_by_acc /usr/share/perl5/Bio/DB/WebDBSeqI.pm:203 STACK toplevel t/BioFetch.t:32 - - # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 6. Dubious, test returned 255 (wstat 65280, 0xff00) All 6 subtests passed Test Summary Report - --- t/BioFetch.t (Wstat: 65280 Tests: 6 Failed: 0) Non-zero exit status: 255 Parse errors: No plan found in TAP output Files=1, Tests=6, 2 wallclock secs ( 0.03 usr 0.00 sys + 0.21 cusr 0.03 csys = 0.27 CPU) Result: FAIL Trying locally, I get 1) no test failure during build, as my cowbuilder doesn't allow internet access, which is gracefully caught: t/BioFetch.t . skipped: no host: www.google.com All tests successful. 2) The same test failure during autopkgtests: t/BioFetch.t .. ok 1 ok 2 ok 3 - An object of class 'Bio::Seq::RichSeq' isa 'Bio::SeqI' ok 4 ok 5 ok 6 - - EXCEPTION - MSG: BioFetch Error 12: No entries found. STACK Bio::DB::BioFetch::postprocess_data /usr/share/perl5/Bio/DB/BioFetch.pm:450 STACK Bio::DB::WebDBSeqI::_stream_request /usr/share/perl5/Bio/DB/WebDBSeqI.pm:769 STACK Bio::DB::WebDBSeqI::get_seq_stream /usr/share/perl5/Bio/DB/WebDBSeqI.pm:476 STACK Bio::DB::BioFetch::get_Stream_by_acc /usr/share/perl5/Bio/DB/BioFetch.pm:525 STACK Bio::DB::WebDBSeqI::get_Seq_by_acc /usr/share/perl5/Bio/DB/WebDBSeqI.pm:194 STACK toplevel t/BioFetch.t:32 - - - - EXCEPTION - MSG: acc J02231 does not exist STACK Bio::DB::WebDBSeqI::get_Seq_by_acc /usr/share/perl5/Bio/DB/WebDBSeqI.pm:203 STACK toplevel t/BioFetch.t:32 - - # Tests were run but no plan was declared and done_testing() was not seen. # Looks like your test exited with 255 just after 6. Dubious, test returned 255 (wstat 65280, 0xff00) Cheers, gregor - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmAyV/JfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZRvQ/9HkQkcPQMcLkkQbTxEvybji3N98WcIheZ5d0IGPGtzdq/48SGG0bbQf0S 1+dPjVMTl/DO5iTtSSOgenPC+QTftOlw8mUoX13IV7RrPMGLtq4ukyE9c612gus7 1hkFsFAP65/+1SWRatb/jCkVasw/0c2n5rjE+LD/Rd11wFSdYuW8go1wgYFeQjWR W7n9oqeR4t1J7aT6XVkJNNFSl8mAe0B5eLinnglJ2mA/WWT4jDE27sac2msV+8WO
Bug#946882: marked as done (blkdeactive hardcodes wrong path to sort)
Your message dated Mon, 22 Feb 2021 22:18:51 + with message-id and subject line Bug#946882: fixed in lvm2 2.03.11-2.1 has caused the Debian Bug report #946882, regarding blkdeactive hardcodes wrong path to sort to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 946882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lvm2 Version: 2.03.02-3 Severity: grave Justification: causes non-serious data loss Dear Maintainer, On systems upgraded from stretch and without the usrmerge package installed, /sbin/blkdeactivate (ExecStop= of blk-availability.service) gives the following error during system shutdown: blkdeactivate[12003]: /sbin/blkdeactivate: line 345: /bin/sort: No such file or directory Despite the error, I have not observed any adverse behavior. However, on new installations or systems upgraded from stretch WITH the usrmerge package installed, the error does not occur. Instead, filesystems may be unmounted prematurely, for example those given as RequiresMountsFor= in other units. I have observed data loss in this case where a required mount was unmounted before the unit requiring it had properly saved its state during shutdown. I am not sure the best course of action to resolve this latter problem. Is it necessary for blkdeactivate to be unmounting filesystems? Could the dependency ordering be adjusted to avoid unmounting filesystems too soon? -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lvm2 depends on: ii dmeventd 2:1.02.155-3 ii dmsetup 2:1.02.155-3 ii libaio1 0.3.112-3 ii libblkid1 2.33.1-0.1 ii libc6 2.28-10 ii libdevmapper-event1.02.1 2:1.02.155-3 ii libdevmapper1.02.12:1.02.155-3 ii libreadline5 5.2+dfsg-3+b13 ii libselinux1 2.8-1+b1 ii libsystemd0 241-7~deb10u2 ii libudev1 241-7~deb10u2 ii lsb-base 10.2019051400 Versions of packages lvm2 recommends: ii thin-provisioning-tools 0.7.6-2.1 lvm2 suggests no packages. -- Configuration Files: /etc/lvm/lvm.conf changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Source: lvm2 Source-Version: 2.03.11-2.1 Done: Ivo De Decker We believe that the bug you reported is fixed in the latest version of lvm2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ivo De Decker (supplier of updated lvm2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Feb 2021 21:39:14 + Source: lvm2 Binary: dmeventd dmeventd-dbgsym dmsetup dmsetup-dbgsym dmsetup-udeb libdevmapper-dev libdevmapper-event1.02.1 libdevmapper-event1.02.1-dbgsym libdevmapper1.02.1 libdevmapper1.02.1-dbgsym libdevmapper1.02.1-udeb liblvm2-dev liblvm2cmd2.03 liblvm2cmd2.03-dbgsym lvm2 lvm2-dbgsym lvm2-dbusd lvm2-lockd lvm2-lockd-dbgsym lvm2-udeb Architecture: source Version: 2.03.11-2.1 Distribution: unstable Urgency: medium Maintainer: Debian LVM Team Changed-By: Ivo De Decker Description: dmeventd - Linux Kernel Device Mapper event daemon dmsetup- Linux Kernel Device Mapper userspace library dmsetup-udeb - Linux Kernel Device Mapper userspace library (udeb) libdevmapper-dev - Linux Kernel Device Mapper header files libdevmapper-event1.02.1 - Linux Kernel Device Mapper event support library libdevmapper1.02.1 - Linux Kernel Device Mapper userspace library libdevmapper1.02.1-udeb - Linux Kernel Device Mapper userspace library (udeb) liblvm2-dev - LVM2 libraries - development files liblvm2cmd2.03 - LVM2 command library lvm2
Bug#983239: marked as done (libbio-db-ncbihelper-perl: (autopkg)test failures when network is available)
Your message dated Mon, 22 Feb 2021 23:12:17 +0100 with message-id and subject line closing 983239 affecting libbio-db-ncbihelper-perl has caused the Debian Bug report #983239, regarding libbio-db-ncbihelper-perl: (autopkg)test failures when network is available to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbio-db-ncbihelper-perl Version: 1.7.6-2 Severity: serious Justification: autopkgtest is relevant, network access is a policy violation -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As seen on ci.d.n: https://ci.debian.net/data/autopkgtest/testing/amd64/libb/libbio-db-ncbihelper-perl/10589853/log.gz we have a test failure: not ok 44 # Failed test at t/Taxonomy.t line 102. # got: 'Actinomycetia' # expected: 'Actinobacteria' This happens because internet access is available, and internet using tests are disabled during not disabeld. I think they are supposed to be disabled during build, but this doesn't seem to work either: t/EntrezGene.t . skipped: no host: www.google.com t/GenBank.t skipped: no host: www.google.com t/GenPept.t skipped: no host: www.google.com t/Query-Genbank.t .. skipped: no host: www.google.com t/RefSeq.t . skipped: no host: www.google.com t/Taxonomy.t ... skipped: no host: www.google.com means that libtest-requiresinternet-perl doesn't find internet access (expected in my chroot), whereas it would output something different if NO_NETWORK_TESTING was respected. (Also: what is --network supposed to do?) With override_dh_auto_test: NO_NETWORK_TESTING=1 dh_auto_test we get: t/EntrezGene.t . skipped: NO_NETWORK_TESTING t/GenBank.t skipped: NO_NETWORK_TESTING t/GenPept.t skipped: NO_NETWORK_TESTING t/Query-Genbank.t .. skipped: NO_NETWORK_TESTING t/RefSeq.t . skipped: NO_NETWORK_TESTING t/Taxonomy.t ... skipped: NO_NETWORK_TESTING Summary: - - the tests try to go out to the internet (policy violation during build) - - if this succeeds the build fails (which doesn't happen in restricted chroots) - - autopkgtests fail - - setting NO_NETWORK_TESTING=1 in d/rules help - - doing the same in debian/tests/pkg-perl/smoke-env fixes the autopkgtest failure Cheers, gregor - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmAyWqJfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgZpqg//QFq38bzNVQzMtyxMbWHQ7rHWERS2IcdGdsu0PIkluPTX86dn/XOvGZgG XlTSJVlhoaZLU9/+O6D+IGUTMGrMCMskNW7sDfB3Q5eTISCCf25ua93iXQaD8iz9 HFScCQx/oc9lAhXyxZwa9qvgMOjNkyFGvz0chjJhqhwsBp9o7mnFFwMd9a675xgv CgXSecGvbkO2ri951Qj42rHblEC1GI1dh12aDZKPuopFkmF43TT5Encem5Ekbw5N ShP2LJsw9+kJ0MEnzClHSYZSetrkqDise/bgkC0icxARzFz7FZVsskwJQq/fx4jm JUjTtiZTDPZlFym3bw2eN2x46187UpdEYF7x1Ez6RxxwUMYOxdZTWf+EzGkXgnQA 5Nd8PC907tzHYsz3U17ABIRZn1pploxwn4S0Rt58m/Z1d4UIhywpdJPw8Ioq3o+6 KvWqdO2mWQxOX0UucvURSNjlMqyX3qifqPvj8yCQRBuPEu2oL3ai3vlN6rzuYVq4 qgWoWofLe+l6OUFt95ZSzRfUw7E9n+XJGjrfcL5hkvdmRa73LAWDkLcgyyqcB7th nwshKOA7h1/IvRSdQJbBenddEL6UtsE6auhkw0300ifF3PHhVxwz1H7zDTKF1JLx z9Bmlqh9cjNx+G4wyXK5LZA83NCgsF9vSzOBwb1KLtc/lx9OgUI= =abvI -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Version: 1.7.6-3 The build time test is now done with NO_NETWORK_TESTING=1, so that prevents the test to fetch data over the Internet, thus fixing the policy violation. -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/3, please excuse my verbosity. signature.asc Description: PGP signature --- End Message ---
Bug#982970: marked as done (offlineimap3: broken folderincludes config option)
Your message dated Mon, 22 Feb 2021 22:03:58 +
with message-id
and subject line Bug#982970: fixed in offlineimap3
0.0~git20210218.76c7a72+dfsg-1
has caused the Debian Bug report #982970,
regarding offlineimap3: broken folderincludes config option
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
982970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: offlineimap3
Version: 0.0~git20210105.00d395b+dfsg-3
Severity: normal
Tags: upstream
Dear Sudip,
offlineimap3 is not able to handle the folderincludes config, that
worked with offlineimap. I got this when trying to sync (tested with two
different accounts):
'str' object has no attribute 'decode'
Traceback:
File "/usr/share/offlineimap3/offlineimap/accounts.py", line 298, in
syncrunner
self.__sync()
File "/usr/share/offlineimap3/offlineimap/accounts.py", line 374, in __sync
remoterepos.getfolders()
File "/usr/share/offlineimap3/offlineimap/repository/IMAP.py", line 695, in
getfolders
imapobj.select(imaputil.utf8_IMAP(foldername),
File "/usr/share/offlineimap3/offlineimap/imaputil.py", line 360, in utf8_IMAP
return foldername.decode('utf-8').encode('imap4-utf-7')
Attached a sample config. Tell me if you need a full log.
Cheers,
-- Santiago
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500,
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.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 offlineimap3 depends on:
ii python3 3.9.1-1
ii python3-distro1.5.0-1
ii python3-imaplib2 2.57-5.2
offlineimap3 recommends no packages.
offlineimap3 suggests no packages.
-- no debconf information
[general]
accounts = Example
ui = Blinkenlights
metadata = ~/.var/offlineimap
ignore-readonly = no
maxsyncaccounts = 3
[mbnames]
enabled = yes
filename = ~/.var/offlineimap/mailboxes
header = "mailboxes "
peritem = "+%(accountname)s/%(foldername)s"
#sep = '\n'
sep = ' '
footer = '\n'
[Account Example]
localrepository = Example-Local
remoterepository = Example-Remote
autorefresh = 15
quick = 16
[Repository Example-Local]
type = Maildir
localfolders = ~/Mail/Example/
[Repository Example-Remote]
type = IMAP
ssl=yes
sslcacertfile = /etc/ssl/certs/ca-certificates.crt
remotehost = imap.example.net
remoteport = 993
remoteuser = myuser
folderincludes = ['debian']
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: offlineimap3
Source-Version: 0.0~git20210218.76c7a72+dfsg-1
Done: Sudip Mukherjee
We believe that the bug you reported is fixed in the latest version of
offlineimap3, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 982...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sudip Mukherjee (supplier of updated offlineimap3
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Feb 2021 21:45:56 +
Source: offlineimap3
Architecture: source
Version: 0.0~git20210218.76c7a72+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Sudip Mukherjee
Closes: 981949 982970 983249
Changes:
offlineimap3 (0.0~git20210218.76c7a72+dfsg-1) unstable; urgency=medium
.
* New upstream version 0.0~git20210218.76c7a72+dfsg
- Remove upstream applied patches.
- Update fixes broken folderincludes. (Closes: #982970)
- Update fixes remoteusereval config. (Closes: #983249)
* Fix reading password from Curses Blinkenlights. (Closes: #981949)
* Fix gmail fetch with synclabels enabled.
Checksums-Sha1:
4725cc3b1336f30ead3633aa6000e329f519e44a 2345
Bug#983249: marked as done (offlineimap3: sequence item 1: expected str instance, bytes found)
Your message dated Mon, 22 Feb 2021 22:03:58 +
with message-id
and subject line Bug#983249: fixed in offlineimap3
0.0~git20210218.76c7a72+dfsg-1
has caused the Debian Bug report #983249,
regarding offlineimap3: sequence item 1: expected str instance, bytes found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: offlineimap3
Version: 0.0~git20210105.00d395b+dfsg-3
Severity: important
Dear Maintainer,
offlineimap fails with:
sequence item 1: expected str instance, bytes found
while trying to sync an imap folder with
pythonfile = ~/.config/offlineimap.py
that looks up username and password:
remoteusereval = get_username("account")
while get_username returns a string, the value gets converted into bytes in
/usr/share/offlineimap3/offlineimap/repository/IMAP.py
...
def getuser(self):
...
if user is not None:
return localeval.eval(user).encode('UTF-8')
due to that, the following fails:
/usr/share/offlineimap3/offlineimap/imapserver.py
...
def __plainhandler(self, response):
tries to mix bytes and strings:
retval = NULL.join((authz, authc, passwd))
This has been fixed upstream in
https://github.com/OfflineIMAP/offlineimap3/pull/50
in the same way it was fixed for passwords in
debian/patches/0001-Right-format-for-password-from-remotepassfile.patch
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages offlineimap3 depends on:
ii python3 3.9.1-1
ii python3-distro1.5.0-1
ii python3-imaplib2 2.57-5.2
offlineimap3 recommends no packages.
offlineimap3 suggests no packages.
-- no debconf information
>From fa080b8d92944a1692a44e982292ffde8066950a Mon Sep 17 00:00:00 2001
From: Konstantinos Natsakis <5933427+knatsa...@users.noreply.github.com>
Date: Mon, 8 Feb 2021 23:40:32 +0200
Subject: [PATCH] BUG: Right format for username using remoteusereval
Similarly to 7a4285370f338a6653e8bb1a8fb99e3703683b6f, reading the username
using remoteusereval returns a bytes objects instead an utf-8 string.
This patch includes support for both string and bytes objects.
Signed-off-by: Konstantinos Natsakis
<5933427+knatsa...@users.noreply.github.com>
---
offlineimap/repository/IMAP.py | 17 ++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/offlineimap/repository/IMAP.py b/offlineimap/repository/IMAP.py
index b732243..e90d30c 100644
--- a/offlineimap/repository/IMAP.py
+++ b/offlineimap/repository/IMAP.py
@@ -206,12 +206,23 @@ def getuser(self):
Returns: Returns the remoteusereval or remoteuser or netrc user value.
"""
-localeval = self.localeval
-
if self.config.has_option(self.getsection(), 'remoteusereval'):
user = self.getconf('remoteusereval')
if user is not None:
-return localeval.eval(user).encode('UTF-8')
+l_user = self.localeval.eval(user)
+
+# We need a str username
+if isinstance(l_user, bytes):
+return l_user.decode(encoding='utf-8')
+elif isinstance(l_user, str):
+return l_user
+
+# If is not bytes or str, we have a problem
+raise OfflineImapError("Could not get a right username format
for"
+ " repository %s. Type found: %s. "
+ "Please, open a bug." %
+ (self.name, type(l_user)),
+ OfflineImapError.ERROR.FOLDER)
if self.config.has_option(self.getsection(), 'remoteuser'):
# Assume the configuration file to be UTF-8 encoded so we must not
--- End Message ---
--- Begin Message ---
Source: offlineimap3
Source-Version: 0.0~git20210218.76c7a72+dfsg-1
Done: Sudip Mukherjee
We believe that the bug you reported is fixed in the latest version of
offlineimap3, which is due to be installed in the Debian FTP archive.
A summary of the changes between this
Bug#981949: marked as done (offlineimap3: broken passwd input via Curses and Blinkenlights)
Your message dated Mon, 22 Feb 2021 22:03:58 +
with message-id
and subject line Bug#981949: fixed in offlineimap3
0.0~git20210218.76c7a72+dfsg-1
has caused the Debian Bug report #981949,
regarding offlineimap3: broken passwd input via Curses and Blinkenlights
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
981949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981949
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: offlineimap3
Version: 0.0~git20210105.00d395b+dfsg-2
Severity: important
Dear offlineimap3 maintainer,
After the recent upgrade, I cannot input my password to sync mail.
offlineimap3 fails with:
sequence item 2: expected str instance, bytes found
This is a full log using a dummy account I created just to reproduce the
bug:
2021-02-05 11:14:15 INFO: OfflineImap 7.3.0 starting...
Python: 3.9.1 Platform: linux
Args: /usr/bin/offlineimap -a Example -d ALL -l /tmp/offlineimap.log
2021-02-05 11:14:15 INFO: OfflineIMAP 7.3.0
Licensed under the GNU GPL v2 or any later version (with an OpenSSL exception)
2021-02-05 11:14:15 INFO: imaplib2 v3.05, Python v3.9.1+, OpenSSL 1.1.1i 8 Dec
2020
2021-02-05 11:14:15 DEBUG: Now debugging for imap: IMAP protocol debugging
2021-02-05 11:14:15 DEBUG: Now debugging for maildir: Maildir repository
debugging
2021-02-05 11:14:15 DEBUG: Now debugging for thread: Threading debugging
2021-02-05 11:14:15 DEBUG: Now debugging for : Other offlineimap related sync
messages
2021-02-05 11:14:15 DEBUG: [thread]: Register new thread 'Account sync Example'
(account 'Example')
2021-02-05 11:14:15 DEBUG: [imap]: Using authentication mechanisms ['GSSAPI',
'XOAUTH2', 'CRAM-MD5', 'PLAIN', 'LOGIN']
2021-02-05 11:14:15 DEBUG: [maildir]: MaildirRepository initialized, sep is '.'
2021-02-05 11:14:15 INFO: *** Processing account Example
2021-02-05 11:14:15 INFO: Establishing connection to imap.example.net:993
(LPB-Remote)
2021-02-05 11:14:15 DEBUG: [imap]: LPB-Remote: level 'tls_compat', version
'None'
2021-02-05 11:14:15 DEBUG: [imap]: 14:15.82 Account sync Example imaplib2
version 3.05
2021-02-05 11:14:15 DEBUG: [imap]: 14:15.82 Account sync Example imaplib2
debug level 5, buffer level 3
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.05 Account sync Example connected to
imap.example.net on port 993
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.05 imap.example.net writer starting
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.05 imap.example.net reader starting
using poll
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.06 Account sync Example
_request_push(continuation, welcome, {}) = b'CJOD0'
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.06 Account sync Example
welcome:b'CJOD0'.ready.wait
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.09 imap.example.net reader poll =>
[(5, 1)]
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.10 imap.example.net reader rcvd 18
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.10 imap.example.net reader < b'* OK
IMAP4 ready\r\n'
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.15 imap.example.net handler starting
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 imap.example.net handler
_put_response(b'* OK IMAP4 ready')
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 imap.example.net handler
untagged_responses[OK] 0 += ["b'IMAP4 ready'"]
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 imap.example.net handler
_request_pop(continuation, (False, b'* OK IMAP4 ready')) [0] = b'CJOD0'
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 imap.example.net handler
welcome:b'CJOD0'.ready.set
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 Account sync Example
_get_untagged_response(OK) => [b'IMAP4 ready']
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 Account sync Example state =>
NONAUTH
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 Account sync Example [async]
CAPABILITY ()
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 Account sync Example
state_change_pending.acquire
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 Account sync Example
state_change_pending.release
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 imap.example.net handler
state_change_free.set
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 Account sync Example
_request_push(b'CJOD1', CAPABILITY, {}) = b'CJOD1'
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 Account sync Example data=b'CJOD1
CAPABILITY'
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 Account sync Example
CAPABILITY:b'CJOD1'.ready.wait
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.16 imap.example.net writer > b'CJOD1
CAPABILITY\r\n'
2021-02-05 11:14:16 DEBUG: [imap]: 14:16.21 imap.example.net reader poll =>
[(5, 1)]
Bug#970081: marked as done (lxdm: missing Depends on gtk2-engines)
Your message dated Mon, 22 Feb 2021 21:33:41 + with message-id and subject line Bug#970081: fixed in lxdm 0.5.3-4 has caused the Debian Bug report #970081, regarding lxdm: missing Depends on gtk2-engines to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 970081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lxdm Version: 0.5.3-3 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The default config that ships with LXDM uses the Clearlooks GTK2 theme. This is not installed by default on a GTK3 system. LXDM must therefore Depends on gtk2-engines which provides the Clearlooks theme. - -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (1000, 'testing-debug'), (1000, 'testing'), (500, 'stable') Architecture: i386 (i586) Kernel: Linux 5.7.0-3-686 (SMP w/1 CPU thread) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxdm depends on: ii debconf [debconf-2.0] 1.5.74 ii gtk2-engines-pixbuf2.24.32-4 ii iso-codes 4.5.0-1 ii libc6 2.31-3 ii libcairo2 1.16.0-4 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libglib2.0-0 2.64.4-1 ii libgtk2.0-02.24.32-4 ii libpam-modules 1.3.1-5 ii libpam-runtime 1.3.1-5 ii libpam0g 1.3.1-5 ii libpango-1.0-0 1.46.1-1 ii libpangocairo-1.0-01.46.1-1 ii librsvg2-common2.48.7-1 ii libx11-6 2:1.6.10-3 ii libxcb11.14-2 ii lsb-base 11.1.0 ii x11-utils 7.7+5 Versions of packages lxdm recommends: ii desktop-base 10.0.3 Versions of packages lxdm suggests: pn lxde-common - -- Configuration Files: /etc/lxdm/lxdm.conf changed: [base] greeter=/usr/lib/lxdm/lxdm-greeter-gtk [server] [display] gtk_theme=Adwaita bg=/usr/share/images/desktop-base/login-background.svg bottom_pane=1 lang=1 keyboard=0 theme=Industrial [input] [userlist] disable=0 white= black= - -- debconf information: * shared/default-x-display-manager: lxdm -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAl9bMEwACgkQrh+Cd8S0 17ZRmA//eTWDeJMJpHYuRu90gboqwhQkQdJ3fu5dhnZ3XqTLWjdU5Ta8JQGOqTYu s7tsiKB0qAT1lCVNwmYLOzP2oxRmoP7FoHZoiCHGoCat/dDAs9vlZnTSEkbgRwJB JmYtjbFUcWKtoEej2SKXdufNUDGo1/apq7AtJF/jVFN54eV+V52UW63L9vJSi9tM fsZ3gE4urAAJU+a3NpVpz9dviT/7FX7QlggjFsJOqTlwJ9yALAssQxvIwvS6BQbJ 6U+3he7k57LFKCiHEaKmr5ngtUa/mllfqX9haNKs3lYotr1cJD3aALzZOPzsAiPe InE6xdPulTIgdm9twrRFGKEKslVbxY0wiIoUjuxjyL0psu6b88hk4sFbBJxYAYGQ iFOyO0WRNQKa1HyAIcjkmoU2sqdszFquNmllfsXV74PnaPFpOwo7fxBj0+oq9a2r rek2v/Z+i4kOaSqw7p6NE9SXL5+JOmare1CbpchNC4LkMWSJaGX8VwnXAMSCSANw wyd5LidGkoXelQcAFFlbOAQPBCCz5lEb6g18STck66fAJpkwOiH4oVeduK454hs9 YB8pnsoVTgiX6aToqKVyIgfQ1XckwiVcpwKAP49b+AF1Mr9RQGpKaNmkJYlJdz3k CXSl3eH0sSVZbW7ZOYa24w9PwAtgHIJ0xwyvyp+lVVkaj8saoU8= =hzSo -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: lxdm Source-Version: 0.5.3-4 Done: Andriy Grytsenko We believe that the bug you reported is fixed in the latest version of lxdm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andriy Grytsenko (supplier of updated lxdm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 23:03:39 +0200 Source: lxdm Architecture: source Version: 0.5.3-4 Distribution: unstable Urgency: medium Maintainer: Debian LXDE Maintainers Changed-By: Andriy Grytsenko Closes: 738023 970081 Changes: lxdm (0.5.3-4) unstable; urgency=medium . * Reposition Vcs-* to the Debian Salsa. * Adding 'Rules-Requires-Root: no' header. * Adding Depend on gtk2-engines (Closes: #970081). * Fixing changelog. * Adding 43-fix-session-pam.patch (Closes: #738023). * Converting some debian/po/ files to UTF-8 encoding. Checksums-Sha1: 2932fd01242d7093784427ea9e82f1201e067b53 1980
Bug#966529: marked as done (Please switch from pk-update-icon to package-update-indicator)
Your message dated Mon, 22 Feb 2021 21:33:35 + with message-id and subject line Bug#966529: fixed in lxde-metapackages 11 has caused the Debian Bug report #966529, regarding Please switch from pk-update-icon to package-update-indicator to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966529 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lxde Version: 10 Severity: normal Hello, The lxde package currently suggests pk-update-icon which is a transitional package. Please switch to package-update-indicator instead which is the real one. Kind regards, Laurent Bigonville -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy Versions of packages lxde depends on: ii gnome-calculator 3.36.0-1 pn gpicview pn leafpad | mousepad pn lxappearance pn lxappearance-obconf pn lxde-core pn lxde-icon-theme pn lxhotkey-gtk pn lxinput pn lxrandr pn lxsession-edit pn lxterminal pn xarchiver Versions of packages lxde recommends: pn clipit ii evince [pdf-viewer] 3.36.7-1 ii firefox [www-browser] 79.0-1 ii gdm3 [x-display-manager] 3.36.2-1 ii gnome-disk-utility3.36.3-1 pn gnome-system-tools pn gucharmap pn lxmusic | audacious pn lxpolkit pn menu-xdg ii network-manager-gnome 1.18.0-1 ii transmission-gtk 3.00-1 pn usermode ii vlc 3.0.11-4+b1 ii xserver-xorg 1:7.7+20 Versions of packages lxde suggests: ii gimp 2.10.18-1 pn libreoffice pn lxlauncher pn lxtask ii pidgin 2.13.0-2.2+b1 pn pk-update-icon pn xfce4-power-manager --- End Message --- --- Begin Message --- Source: lxde-metapackages Source-Version: 11 Done: Andriy Grytsenko We believe that the bug you reported is fixed in the latest version of lxde-metapackages, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andriy Grytsenko (supplier of updated lxde-metapackages package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 22:33:03 +0200 Source: lxde-metapackages Architecture: source Version: 11 Distribution: unstable Urgency: medium Maintainer: Debian LXDE Maintainers Changed-By: Andriy Grytsenko Closes: 916042 928692 960111 966529 Changes: lxde-metapackages (11) unstable; urgency=medium . * Reposition Vcs-* to the Debian Salsa. * Bump Standards-Version to 4.5.1. * Dropping customized compression options from debian/source/options file. * Adding 'Rules-Requires-Root: no' header. * Bump debhelper to version 12. * Dropping leafpad as a dependency of lxde package (Closes: #916042). * Recommending gnome-colors and numlockx (Related: #923796). * Adding parcellite and copyq as alternatives for clipit (Closes: #960111). * Switching from pk-update-icon to package-update-indicator (Closes: #966529). * Replacing default recommendation on wicd with connman-gtk (Closes: #928692). Checksums-Sha1: a15e76f6a4eab7cc12d4c5d732191f4ae808e66d 1757 lxde-metapackages_11.dsc 79a7f9f66ed8dd888ec6bded08a57abaf786429e 4052 lxde-metapackages_11.tar.xz 142c7e368f0541c440b19620e3f693c60711f074 4885 lxde-metapackages_11_amd64.buildinfo Checksums-Sha256: b3aa6ddcb210f19f7f804a2da588183711cc5f42e750d102b2d827b536731f3d 1757 lxde-metapackages_11.dsc
Bug#960111: marked as done (lxde: recommends deprecated clipit)
Your message dated Mon, 22 Feb 2021 21:33:35 + with message-id and subject line Bug#960111: fixed in lxde-metapackages 11 has caused the Debian Bug report #960111, regarding lxde: recommends deprecated clipit to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 960111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lxde Version: 10 Hello, lxde recommends clipit, which is now deprecated. It should be upgraded to a current package, e.g. diodon. Regards, Gabriele Stilli --- End Message --- --- Begin Message --- Source: lxde-metapackages Source-Version: 11 Done: Andriy Grytsenko We believe that the bug you reported is fixed in the latest version of lxde-metapackages, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andriy Grytsenko (supplier of updated lxde-metapackages package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 22:33:03 +0200 Source: lxde-metapackages Architecture: source Version: 11 Distribution: unstable Urgency: medium Maintainer: Debian LXDE Maintainers Changed-By: Andriy Grytsenko Closes: 916042 928692 960111 966529 Changes: lxde-metapackages (11) unstable; urgency=medium . * Reposition Vcs-* to the Debian Salsa. * Bump Standards-Version to 4.5.1. * Dropping customized compression options from debian/source/options file. * Adding 'Rules-Requires-Root: no' header. * Bump debhelper to version 12. * Dropping leafpad as a dependency of lxde package (Closes: #916042). * Recommending gnome-colors and numlockx (Related: #923796). * Adding parcellite and copyq as alternatives for clipit (Closes: #960111). * Switching from pk-update-icon to package-update-indicator (Closes: #966529). * Replacing default recommendation on wicd with connman-gtk (Closes: #928692). Checksums-Sha1: a15e76f6a4eab7cc12d4c5d732191f4ae808e66d 1757 lxde-metapackages_11.dsc 79a7f9f66ed8dd888ec6bded08a57abaf786429e 4052 lxde-metapackages_11.tar.xz 142c7e368f0541c440b19620e3f693c60711f074 4885 lxde-metapackages_11_amd64.buildinfo Checksums-Sha256: b3aa6ddcb210f19f7f804a2da588183711cc5f42e750d102b2d827b536731f3d 1757 lxde-metapackages_11.dsc 07087ebf2a37f3d7e44d16dba08f0b9327eecbdf61643579ecddd9526923a04c 4052 lxde-metapackages_11.tar.xz 89fe5dd38be3045fd4ec81234fb16ec93bdc3634378bf01b70fb5850fbfe38c0 4885 lxde-metapackages_11_amd64.buildinfo Files: 4e251d13ce81935199b9872af54b5b3a 1757 metapackages optional lxde-metapackages_11.dsc 8cb9750bf5f0aace4c5de4acb9bdca3f 4052 metapackages optional lxde-metapackages_11.tar.xz 3d65a858f83d80360d6f19c25d26499c 4885 metapackages optional lxde-metapackages_11_amd64.buildinfo -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJgNB54AAoJEAV2MC/hidTSkPsP/jDCtvgy1tc8sY7YtqYO9Olo k3b4hAftgVV/+zDQ2CWF8iEwgegxdRAiEWbK3K7rOpwBNweBi06W8hVV92C/pO0C 7CE4Qo+BI6mjN0wGH5dDYhXhp/3qRPwtzhcouMZM153ANq2wfmYE2wPR7mrq4mBk JolX4PqFvUM968CqQDDmg9+XGObxI/v+l09ofZEtq+2vXbg+lI0y/YmeHPtv6ORg J7PoIKHmS3Lbf9wVrqggXWU37pn6kC0kJwvYo3vicp2QXFcBjSyBJRhe+oRJVGEZ rtUheC28XirjqnJEvP4OvO5pxD+VpOgcaLhjKxTuDEXCF9oZek066VnELcbkosrU /gzNUC2OwlViCAUmwjVgRF0VElQO76J+B6mF2QjrvbWa4GHfXndMiI4DMn8lz89O MqBH7VVmNvughJKAcvu+EHCJj27COyosCbKoUQ7QEjaulmnGqbQRm0BV0FAgNbty cd5Ki0Mir9pZ6tyE1lNNVUSkJ9D90jxXrDLdjNCkrd+InkS8yyiVL14sHfbgoG4L 8aNrtt7oYSyVMDA4lIF4UOCnYjz7uxeTDQBKS+9GCF3ItBIXI70woQLLdECSBQII j+L9gQLOY9HTaRUmXMwpUqfkHX2qQ0pJ7v6zHgv3nWxH9atXxv7jnY0uURDcoi0j Wwrj/5MGywbEGK1Rthgo =0ew+ -END PGP SIGNATURE End Message ---
Bug#928692: marked as done (lxde: Wicd no longer maintained upstream - should not be default any longer)
Your message dated Mon, 22 Feb 2021 21:33:35 + with message-id and subject line Bug#928692: fixed in lxde-metapackages 11 has caused the Debian Bug report #928692, regarding lxde: Wicd no longer maintained upstream - should not be default any longer to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 928692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lxde Version: 10 Severity: wishlist Dear Maintainer, Wicd currently gets installed as the default network management daemon and tool when LXDE is selected during Debian install. It has a number of bugs that affect basic usability, and the upstream devs are no longer maintaining it. I think network-manager should be the default instead. One of those basic usability bugs is that Wicd fails to connect to insecure wifi for a bunch of users (bug reported multiple times, for the past several years). The reason is that Wicd still uses "ifconfig", instead of "ip", and the ifconfig interface is no longer working the same (at least for some hardware). I've submitted a patch for this, but the Wicd devs haven't responded to that, or other patches and bugs, for quite some time. Anyway - failing to connect to insecure wifi will definitely be a bad user experience for many people. Wicd should no longer be the default. Thanks, and thank you for maintaining LXDE. -Karl -- System Information: Debian Release: stable Architecture: amd64 (x86_64) I actually tested this just tonight on a fresh VM net install from the default amd64 install ISO. -- no debconf information --- End Message --- --- Begin Message --- Source: lxde-metapackages Source-Version: 11 Done: Andriy Grytsenko We believe that the bug you reported is fixed in the latest version of lxde-metapackages, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 928...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andriy Grytsenko (supplier of updated lxde-metapackages package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 22:33:03 +0200 Source: lxde-metapackages Architecture: source Version: 11 Distribution: unstable Urgency: medium Maintainer: Debian LXDE Maintainers Changed-By: Andriy Grytsenko Closes: 916042 928692 960111 966529 Changes: lxde-metapackages (11) unstable; urgency=medium . * Reposition Vcs-* to the Debian Salsa. * Bump Standards-Version to 4.5.1. * Dropping customized compression options from debian/source/options file. * Adding 'Rules-Requires-Root: no' header. * Bump debhelper to version 12. * Dropping leafpad as a dependency of lxde package (Closes: #916042). * Recommending gnome-colors and numlockx (Related: #923796). * Adding parcellite and copyq as alternatives for clipit (Closes: #960111). * Switching from pk-update-icon to package-update-indicator (Closes: #966529). * Replacing default recommendation on wicd with connman-gtk (Closes: #928692). Checksums-Sha1: a15e76f6a4eab7cc12d4c5d732191f4ae808e66d 1757 lxde-metapackages_11.dsc 79a7f9f66ed8dd888ec6bded08a57abaf786429e 4052 lxde-metapackages_11.tar.xz 142c7e368f0541c440b19620e3f693c60711f074 4885 lxde-metapackages_11_amd64.buildinfo Checksums-Sha256: b3aa6ddcb210f19f7f804a2da588183711cc5f42e750d102b2d827b536731f3d 1757 lxde-metapackages_11.dsc 07087ebf2a37f3d7e44d16dba08f0b9327eecbdf61643579ecddd9526923a04c 4052 lxde-metapackages_11.tar.xz 89fe5dd38be3045fd4ec81234fb16ec93bdc3634378bf01b70fb5850fbfe38c0 4885 lxde-metapackages_11_amd64.buildinfo Files: 4e251d13ce81935199b9872af54b5b3a 1757 metapackages optional lxde-metapackages_11.dsc 8cb9750bf5f0aace4c5de4acb9bdca3f 4052 metapackages optional lxde-metapackages_11.tar.xz 3d65a858f83d80360d6f19c25d26499c 4885 metapackages optional lxde-metapackages_11_amd64.buildinfo -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJgNB54AAoJEAV2MC/hidTSkPsP/jDCtvgy1tc8sY7YtqYO9Olo k3b4hAftgVV/+zDQ2CWF8iEwgegxdRAiEWbK3K7rOpwBNweBi06W8hVV92C/pO0C 7CE4Qo+BI6mjN0wGH5dDYhXhp/3qRPwtzhcouMZM153ANq2wfmYE2wPR7mrq4mBk
Bug#916042: marked as done (lxde: leafpad is not fit for default editor)
Your message dated Mon, 22 Feb 2021 21:33:35 + with message-id and subject line Bug#916042: fixed in lxde-metapackages 11 has caused the Debian Bug report #916042, regarding lxde: leafpad is not fit for default editor to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lxde Version: 10 Severity: normal X-Debbugs-Cc: kretc...@gmail.com, sfkrys...@gmail.com, and...@rep.kiev.ua Hi, The metapackage lxde currently depends on "leafpad | mousepad" which in practice makes leafpad the default text editor for lxde. I think leafpad is not suitable to be a default editor because of its long-standing bugs: - UTF-8 mishandling https://bugs.debian.org/913838 https://bugs.launchpad.net/ubuntu/+bug/800059 - data loss when used with ssh/sftp/samba https://bugs.debian.org/890416 https://bugs.launchpad.net/ubuntu/+bug/708829 - middle click paste not working https://bugs.debian.org/511827 - UTF-16 encoded file not displayed https://bugs.debian.org/819909 - last line of selection is not indented https://bugs.launchpad.net/ubuntu/+bug/1460311 I think any of those is not a problem for the two alternative editors, mousepad and featherpad. Please consider dropping the dependency on leafpad from lxde. Thanks, -- Juhani --- End Message --- --- Begin Message --- Source: lxde-metapackages Source-Version: 11 Done: Andriy Grytsenko We believe that the bug you reported is fixed in the latest version of lxde-metapackages, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andriy Grytsenko (supplier of updated lxde-metapackages package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 22:33:03 +0200 Source: lxde-metapackages Architecture: source Version: 11 Distribution: unstable Urgency: medium Maintainer: Debian LXDE Maintainers Changed-By: Andriy Grytsenko Closes: 916042 928692 960111 966529 Changes: lxde-metapackages (11) unstable; urgency=medium . * Reposition Vcs-* to the Debian Salsa. * Bump Standards-Version to 4.5.1. * Dropping customized compression options from debian/source/options file. * Adding 'Rules-Requires-Root: no' header. * Bump debhelper to version 12. * Dropping leafpad as a dependency of lxde package (Closes: #916042). * Recommending gnome-colors and numlockx (Related: #923796). * Adding parcellite and copyq as alternatives for clipit (Closes: #960111). * Switching from pk-update-icon to package-update-indicator (Closes: #966529). * Replacing default recommendation on wicd with connman-gtk (Closes: #928692). Checksums-Sha1: a15e76f6a4eab7cc12d4c5d732191f4ae808e66d 1757 lxde-metapackages_11.dsc 79a7f9f66ed8dd888ec6bded08a57abaf786429e 4052 lxde-metapackages_11.tar.xz 142c7e368f0541c440b19620e3f693c60711f074 4885 lxde-metapackages_11_amd64.buildinfo Checksums-Sha256: b3aa6ddcb210f19f7f804a2da588183711cc5f42e750d102b2d827b536731f3d 1757 lxde-metapackages_11.dsc 07087ebf2a37f3d7e44d16dba08f0b9327eecbdf61643579ecddd9526923a04c 4052 lxde-metapackages_11.tar.xz 89fe5dd38be3045fd4ec81234fb16ec93bdc3634378bf01b70fb5850fbfe38c0 4885 lxde-metapackages_11_amd64.buildinfo Files: 4e251d13ce81935199b9872af54b5b3a 1757 metapackages optional lxde-metapackages_11.dsc 8cb9750bf5f0aace4c5de4acb9bdca3f 4052 metapackages optional lxde-metapackages_11.tar.xz 3d65a858f83d80360d6f19c25d26499c 4885 metapackages optional lxde-metapackages_11_amd64.buildinfo -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJgNB54AAoJEAV2MC/hidTSkPsP/jDCtvgy1tc8sY7YtqYO9Olo k3b4hAftgVV/+zDQ2CWF8iEwgegxdRAiEWbK3K7rOpwBNweBi06W8hVV92C/pO0C 7CE4Qo+BI6mjN0wGH5dDYhXhp/3qRPwtzhcouMZM153ANq2wfmYE2wPR7mrq4mBk JolX4PqFvUM968CqQDDmg9+XGObxI/v+l09ofZEtq+2vXbg+lI0y/YmeHPtv6ORg J7PoIKHmS3Lbf9wVrqggXWU37pn6kC0kJwvYo3vicp2QXFcBjSyBJRhe+oRJVGEZ rtUheC28XirjqnJEvP4OvO5pxD+VpOgcaLhjKxTuDEXCF9oZek066VnELcbkosrU /gzNUC2OwlViCAUmwjVgRF0VElQO76J+B6mF2QjrvbWa4GHfXndMiI4DMn8lz89O
Bug#738023: marked as done ([experimental] policykit-1: workaround for lxdm)
Your message dated Mon, 22 Feb 2021 21:33:41 + with message-id and subject line Bug#738023: fixed in lxdm 0.5.3-4 has caused the Debian Bug report #738023, regarding [experimental] policykit-1: workaround for lxdm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 738023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:policykit-1 Version: 0.112-2 Severity: critical Hello comrades. Upgrade packages libpolkit-gobject-1-0 and libpolkit-agent-1-0 from stable (0.105-3) to experimental (0.112-2) totally breaks all PolicyKit agents. $ /usr/lib/x86_64-linux-gnu/lxpolkit ** (lxpolkit:4329): CRITICAL **: polkit_agent_listener_register_with_options: assertion 'POLKIT_IS_SUBJECT (subject)' failed (lxpolkit:4329): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Ошибка сегментирования 'Ошибка сегментирования' in English sounds as 'Segmentation fault'. I have installed debuggins symbols and found that: $ gdb -q /usr/lib/x86_64-linux-gnu/lxpolkit Reading symbols from /usr/lib/x86_64-linux-gnu/lxpolkit...Reading symbols from /usr/lib/debug/.build-id/7f/5a89c28fa91f97674a9d9a159d4e98c057f14a.debug...done. done. (gdb) run Starting program: /usr/lib/x86_64-linux-gnu/lxpolkit warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". ** (lxpolkit:5460): CRITICAL **: polkit_agent_listener_register_with_options: assertion 'POLKIT_IS_SUBJECT (subject)' failed (lxpolkit:5460): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Program received signal SIGSEGV, Segmentation fault. 0x0040220c in main (argc=1, argv=0x7fffe778) at lxpolkit.c:85 I also check other PolicyKit agents: $ /usr/lib/x86_64-linux-gnu/polkit-mate/polkit-mate-authentication-agent-1 (polkit-mate-authentication-agent-1:5803): polkit-mate-1-WARNING **: Unable to determine the session we are in: No session for pid 5803 $ /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 (polkit-gnome-authentication-agent-1:5913): polkit-gnome-1-WARNING **: Unable to determine the session we are in: No session for pid 5913 Downgrade libpolkit-gobject-1-0 and libpolkit-agent-1-0 to stable versions solve the problem. --- End Message --- --- Begin Message --- Source: lxdm Source-Version: 0.5.3-4 Done: Andriy Grytsenko We believe that the bug you reported is fixed in the latest version of lxdm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 738...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andriy Grytsenko (supplier of updated lxdm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 23:03:39 +0200 Source: lxdm Architecture: source Version: 0.5.3-4 Distribution: unstable Urgency: medium Maintainer: Debian LXDE Maintainers Changed-By: Andriy Grytsenko Closes: 738023 970081 Changes: lxdm (0.5.3-4) unstable; urgency=medium . * Reposition Vcs-* to the Debian Salsa. * Adding 'Rules-Requires-Root: no' header. * Adding Depend on gtk2-engines (Closes: #970081). * Fixing changelog. * Adding 43-fix-session-pam.patch (Closes: #738023). * Converting some debian/po/ files to UTF-8 encoding. Checksums-Sha1: 2932fd01242d7093784427ea9e82f1201e067b53 1980 lxdm_0.5.3-4.dsc df393c27e421e6aa0c5e4557a6bf87f888a11b3a 27260 lxdm_0.5.3-4.debian.tar.xz acd78d7e7ad64139078c71efaf3182c183dedb64 10900 lxdm_0.5.3-4_amd64.buildinfo Checksums-Sha256: 800c24a760dd84aacb72979abec1dc707c0e56286dd303779c5ee9b590acb8f6 1980 lxdm_0.5.3-4.dsc 63ad49be3fe057a42116ff2b7d0ae48d27a0598a0cc2e94f753137dc07733f6a 27260 lxdm_0.5.3-4.debian.tar.xz 2cc5cc1bd16fcb72397d71407de029063ac6bd376a808d3751dfe47002e8d9f2 10900 lxdm_0.5.3-4_amd64.buildinfo Files: aef77fc75b77480b34ed3921c247095e 1980 x11 optional lxdm_0.5.3-4.dsc a99372fa8f68a05359ec58745f31ec38 27260 x11 optional lxdm_0.5.3-4.debian.tar.xz
Bug#983054: marked as done (ruby-kramdown-rfc2629: new upstream version 1.3.34)
Your message dated Mon, 22 Feb 2021 21:04:15 + with message-id and subject line Bug#983054: fixed in ruby-kramdown-rfc2629 1.3.35-1 has caused the Debian Bug report #983054, regarding ruby-kramdown-rfc2629: new upstream version 1.3.34 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-kramdown-rfc2629 Version: 1.3.28-1 Upstream has released version 1.3.34, which contains a helpful transformation for a document i'm working on. updating the debian packaging to that version would be great! (i note that 1.3.28 is a day away from transitioning to testing, so maybe either an upload to experimental, or a delayed upload would be wise so that at least 1.3.28 transitions) thanks for maintaining ruby-kramdown-rfc2629 in debian! --dkg signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-kramdown-rfc2629 Source-Version: 1.3.35-1 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-kramdown-rfc2629, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-kramdown-rfc2629 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 17:51:21 +0100 Source: ruby-kramdown-rfc2629 Architecture: source Version: 1.3.35-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Cédric Boutillier Closes: 983054 983057 Changes: ruby-kramdown-rfc2629 (1.3.35-1) unstable; urgency=medium . * New upstream version 1.3.35 (Closes: #983054) * fix version parsing from gemspec (Closes: #983057) Checksums-Sha1: 31d41ee41188e46f7c3af82e4516a9d26c374c19 1842 ruby-kramdown-rfc2629_1.3.35-1.dsc 4be6b6e77890874d2664890b4122248ae72861c3 39225 ruby-kramdown-rfc2629_1.3.35.orig.tar.gz 72da383fac19daf19d0942bf9c2cc152f239c74f 5392 ruby-kramdown-rfc2629_1.3.35-1.debian.tar.xz 4b0bb7e6bd6c0b63f9512f2da41e08fff2dd1bbf 8724 ruby-kramdown-rfc2629_1.3.35-1_amd64.buildinfo Checksums-Sha256: 0de48001272c47fd9263004b3efb307c58412726a30529fcec83478623716b41 1842 ruby-kramdown-rfc2629_1.3.35-1.dsc 4fcdd802f68c18348ddf5fa1ce7cc69217703bd0ae2ce7d2700202ab5758a57f 39225 ruby-kramdown-rfc2629_1.3.35.orig.tar.gz e51f6bfa0a33c923e8f9ded095b2ef405636e74eeca2c3ce9fb7dc0808223cea 5392 ruby-kramdown-rfc2629_1.3.35-1.debian.tar.xz 4a291679175361aa236445c720d8118a25aa1c40f6e3fb090424ea530fb3d0a4 8724 ruby-kramdown-rfc2629_1.3.35-1_amd64.buildinfo Files: 2e46b7aabfb1e76b010d9d0ca94da521 1842 ruby optional ruby-kramdown-rfc2629_1.3.35-1.dsc d32c76e27333aa19b080d1e43358d1b4 39225 ruby optional ruby-kramdown-rfc2629_1.3.35.orig.tar.gz 6eeea12e50dfce7d0989fb0f2dab7969 5392 ruby optional ruby-kramdown-rfc2629_1.3.35-1.debian.tar.xz 0eac58fef7c52747a5f4a4350e78dedf 8724 ruby optional ruby-kramdown-rfc2629_1.3.35-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAmA0FqgACgkQia+CtznN IXrPDggAj3xKPCcricBV3Qmk5BNVwVR2KislARC2cAbGsdIqaCbJZEkIIBShn64e rHo5BFY4spZEWFs3rK8Qx7UwNrHhI1fq3SpwXfdpzQy5XnFCo952Yo30BngTGLmb 49+yC9DBvCBEqftTxiwT7Dhu23SYeKvFYMNevhFdv9bxAhahbsZPdLGlwhmxQps4 pVm9A6itkXPvEvnyD8Tf1pvdoe11C/CoIsb3862j/i7Pf0JgGzyoHMv6A20/jiNX 1nDPx1SaJMyemZEEwkO6xnYbp5J4m+wcTmrd/6c1DfWfJzJFWy3IjQKHIFU174+v HqBNJr0qIWqAzBQGIESr/LzW88wFYw== =VIdb -END PGP SIGNATURE End Message ---
Bug#983057: marked as done (ruby-kramdown-rfc2629: kramdown-rfc2629 --version produces "unknown-version")
Your message dated Mon, 22 Feb 2021 21:04:15 + with message-id and subject line Bug#983057: fixed in ruby-kramdown-rfc2629 1.3.35-1 has caused the Debian Bug report #983057, regarding ruby-kramdown-rfc2629: kramdown-rfc2629 --version produces "unknown-version" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-kramdown-rfc2629 Version: 1.3.28-1 I would have expected "kramdown-rfc2629 --version" to report either the upstream version (1.3.28) or the debian revision (1.3.28-1), but instead i get "unknown-version": 0 dkg@alice:~$ kramdown-rfc2629 --version kramdown-rfc2629 unknown-version 0 dkg@alice:~$ I haven't dug deep enough to know whether this is an upstream bug or an issue with an impedence mismatch between debian packages and ruby gems, but i do note that from irb i see the same issue. kramdown-rfc2629 has this source: KDRFC_VERSION=Gem.loaded_specs["kramdown-rfc2629"].version rescue "unknown-version" and from irb: irb(main):001:0> require 'kramdown-rfc2629' => true irb(main):002:0> Gem.loaded_specs["kramdown-rfc2629"] => nil irb(main):003:0> Gem.loaded_specs["kramdown-rfc2629"].version Traceback (most recent call last): 4: from /usr/bin/irb:23:in `' 3: from /usr/bin/irb:23:in `load' 2: from /usr/lib/ruby/gems/2.7.0/gems/irb-1.2.6/exe/irb:11:in `' 1: from (irb):3 NoMethodError (undefined method `version' for nil:NilClass) irb(main):004:0> Gem.loaded_specs["kramdown-rfc2629"].version rescue 'unknown-version' => "unknown-version" irb(main):005:0> I defer to debian ruby packagers who have much deeper knowledge than i do about how this stuff all works. Upstream is pretty responsive, fwict, so if it's an upstream issue, please forward it to https://github.com/cabo/kramdown-rfc2629/issues Regards, --dkg signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-kramdown-rfc2629 Source-Version: 1.3.35-1 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-kramdown-rfc2629, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-kramdown-rfc2629 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 17:51:21 +0100 Source: ruby-kramdown-rfc2629 Architecture: source Version: 1.3.35-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Cédric Boutillier Closes: 983054 983057 Changes: ruby-kramdown-rfc2629 (1.3.35-1) unstable; urgency=medium . * New upstream version 1.3.35 (Closes: #983054) * fix version parsing from gemspec (Closes: #983057) Checksums-Sha1: 31d41ee41188e46f7c3af82e4516a9d26c374c19 1842 ruby-kramdown-rfc2629_1.3.35-1.dsc 4be6b6e77890874d2664890b4122248ae72861c3 39225 ruby-kramdown-rfc2629_1.3.35.orig.tar.gz 72da383fac19daf19d0942bf9c2cc152f239c74f 5392 ruby-kramdown-rfc2629_1.3.35-1.debian.tar.xz 4b0bb7e6bd6c0b63f9512f2da41e08fff2dd1bbf 8724 ruby-kramdown-rfc2629_1.3.35-1_amd64.buildinfo Checksums-Sha256: 0de48001272c47fd9263004b3efb307c58412726a30529fcec83478623716b41 1842 ruby-kramdown-rfc2629_1.3.35-1.dsc 4fcdd802f68c18348ddf5fa1ce7cc69217703bd0ae2ce7d2700202ab5758a57f 39225 ruby-kramdown-rfc2629_1.3.35.orig.tar.gz e51f6bfa0a33c923e8f9ded095b2ef405636e74eeca2c3ce9fb7dc0808223cea 5392 ruby-kramdown-rfc2629_1.3.35-1.debian.tar.xz 4a291679175361aa236445c720d8118a25aa1c40f6e3fb090424ea530fb3d0a4 8724 ruby-kramdown-rfc2629_1.3.35-1_amd64.buildinfo Files: 2e46b7aabfb1e76b010d9d0ca94da521 1842 ruby optional ruby-kramdown-rfc2629_1.3.35-1.dsc d32c76e27333aa19b080d1e43358d1b4 39225 ruby optional ruby-kramdown-rfc2629_1.3.35.orig.tar.gz 6eeea12e50dfce7d0989fb0f2dab7969 5392 ruby optional ruby-kramdown-rfc2629_1.3.35-1.debian.tar.xz 0eac58fef7c52747a5f4a4350e78dedf 8724 ruby optional
Bug#963319: marked as done (ruby-em-synchrony: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Mon, 22 Feb 2021 20:34:13 + with message-id and subject line Bug#963319: fixed in ruby-em-synchrony 1.0.5-3.1 has caused the Debian Bug report #963319, regarding ruby-em-synchrony: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-em-synchrony Version: 1.0.5-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /<>/spec/connection_pool_spec.rb:4: warning: already initialized > constant QUERY > /<>/spec/activerecord_spec.rb:11: warning: previous definition > of QUERY was here > /<>/spec/http_spec.rb:5: warning: already initialized constant > DELAY > /<>/spec/connection_pool_spec.rb:3: warning: previous definition > of DELAY was here > /<>/spec/inlinesync_spec.rb:6: warning: already initialized > constant URL > /<>/spec/http_spec.rb:3: warning: previous definition of URL was > here > /<>/spec/inlinesync_spec.rb:7: warning: already initialized > constant DELAY > /<>/spec/http_spec.rb:5: warning: previous definition of DELAY > was here > /<>/spec/keyboard_spec.rb:4: warning: already initialized > constant DELAY > /<>/spec/inlinesync_spec.rb:7: warning: previous definition of > DELAY was here > /<>/spec/mysql2_spec.rb:6: warning: already initialized constant > DELAY > /<>/spec/keyboard_spec.rb:4: warning: previous definition of > DELAY was here > /<>/spec/mysql2_spec.rb:7: warning: already initialized constant > QUERY > /<>/spec/connection_pool_spec.rb:4: warning: previous definition > of QUERY was here > ****..FFF..F > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2020/06/20/ruby-em-synchrony_1.0.5-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: ruby-em-synchrony Source-Version: 1.0.5-3.1 Done: Ivo De Decker We believe that the bug you reported is fixed in the latest version of ruby-em-synchrony, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ivo De Decker (supplier of updated ruby-em-synchrony package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Feb 2021 20:12:04 + Source: ruby-em-synchrony Binary: ruby-em-synchrony Architecture: source Version: 1.0.5-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Ivo De Decker Description: ruby-em-synchrony - fiber aware EventMachine libraries Closes: 963319 Changes: ruby-em-synchrony (1.0.5-3.1) unstable; urgency=medium . * Non-maintainer upload. * Disable tests for now. The mysql tests don't work under fakeroot anymore (Closes: #963319) Checksums-Sha1: 52171473edd0f0e1c67e73ee03f67e80d4eca575 2431 ruby-em-synchrony_1.0.5-3.1.dsc e8b688498091bc3c7d98e2df3ebc9e67f92b02f3 7676 ruby-em-synchrony_1.0.5-3.1.debian.tar.xz Checksums-Sha256: c2989fe9f13415145a477ed8a6863c9e353fd3227b90bc7c02a3072c4a3a620a 2431 ruby-em-synchrony_1.0.5-3.1.dsc 8908edb4afaf478103aad8247a15207abf51ad93f93a72108933adf1210f26c1 7676 ruby-em-synchrony_1.0.5-3.1.debian.tar.xz Files: 9809b52aab66b7eca7ac036eae4755d9 2431 ruby optional ruby-em-synchrony_1.0.5-3.1.dsc 6e2c4663d7736b35b0f1141e3dc6e6cf 7676 ruby optional ruby-em-synchrony_1.0.5-3.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEE9GM4QTXwpzdLbkGwrEC7WJcE6vwFAmA0EUoWHGl2by5kZWRl
Bug#983337: marked as done (dictionaries-common-dev: please add Provides: dh-sequence-aspell-simple)
Your message dated Mon, 22 Feb 2021 20:18:20 +
with message-id
and subject line Bug#983337: fixed in dictionaries-common 1.28.4
has caused the Debian Bug report #983337,
regarding dictionaries-common-dev: please add Provides:
dh-sequence-aspell-simple
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dictionaries-common-dev
Version: 1.28.3
Severity: normal
Hi,
please add
Provides: dh-sequence-aspell-simple
to dictionaries-common-dev. This will allow to simplify
'B-D: dictionaries-common-dev (>= ...)' and 'dh --with aspell-simple'
to 'B-D: dh-sequence-aspell-simple'
Could we have this in bullseye, please?
Thanks
Andreas
--- End Message ---
--- Begin Message ---
Source: dictionaries-common
Source-Version: 1.28.4
Done: Agustin Martin Domingo
We believe that the bug you reported is fixed in the latest version of
dictionaries-common, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Agustin Martin Domingo (supplier of updated
dictionaries-common package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 22 Feb 2021 19:03:21 +0100
Source: dictionaries-common
Architecture: source
Version: 1.28.4
Distribution: unstable
Urgency: medium
Maintainer: Agustin Martin Domingo
Changed-By: Agustin Martin Domingo
Closes: 983337
Changes:
dictionaries-common (1.28.4) unstable; urgency=medium
.
* Make dictionaries-common-dev provide dh-sequence-aspell-simple. Thanks
Andreas Beckmann (Closes: #983337).
* {a,i}spell-autobuiildhash: Show compat info in one more place in debug
mode.
* 470_ispell.el_XEmacs-non-unified-chars-latin01.patch: Fix typo in
description.
* debian/control:
- Add Rules-Requires-Root: no
- Bump Standards-Version.
* Recode some files to UTF-8.
- debian/README.Debian.
- debian-ispell.el and startup.el.in.
- debian/po/es.po.
- support/mutt/ispell-init.
* debian/dictionaries-common.lintian-overrides: More overrides.
Checksums-Sha1:
4c34bbb68f2affaa210e41509c88f3c811df78be 1902 dictionaries-common_1.28.4.dsc
f2d904135b731938aa177d2b0fe6025add3cfa06 284224
dictionaries-common_1.28.4.tar.xz
f6315ca024768b6a2979b7d2fcf654fae9d6c6d4 6625
dictionaries-common_1.28.4_amd64.buildinfo
Checksums-Sha256:
cf293191d12825be62d6d572143de199ea2ffac1efc22647a4564cfcef7c680d 1902
dictionaries-common_1.28.4.dsc
6c5a9cb4b6ad8e61cd856273cbcad0f36343d55cd43fc5c8eba44414744bafb4 284224
dictionaries-common_1.28.4.tar.xz
0819c0e4ef97d5b5a6a16f5855a0018625b4dcb51f09a0529d77de091fa1f574 6625
dictionaries-common_1.28.4_amd64.buildinfo
Files:
f5865d1d3f7d1f5e9a07ea086352ce72 1902 text optional
dictionaries-common_1.28.4.dsc
8a2adbb345c045828179813ccfed4c9e 284224 text optional
dictionaries-common_1.28.4.tar.xz
2d6fc0fcf98accd3f445452d5c0d50f5 6625 text optional
dictionaries-common_1.28.4_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEEehey7p+gYd346SEFJrCLeiggvwFAmA0C2cACgkQFJrCLeig
gvzgUw/+I/8aMZIrxLE7IHrqzSh/vFjb/YJmcBiguZUYvazngp4jqOHCaptXxpOS
23uNWA+YHdjU0aIMnh4/BxXgRt4fsdx+zUSqNsGQRZ2GsNiaXX2/TBvsUi/POWq7
WEViY8QwCRs2/AOgXzzsWkdZNXho1iUcoOGXKjo9zQkQC3xj8qqheuHq6eC111ZY
Nu7TBOfaVMQX9THbo0NQz/VhsoESCyIlqJ8eN/MnEzblimXwfZM6pS0Sxpjeq2zi
JxDDffgRYxqm/bbHSGjap22WDwfVW8QRxkfEEIF4pK7Vfc3qazXbdzcWF/yuYl4L
Bk2n7A7RxlfsrVy+6V4l8FqHxmYloNw7RT0UKbS7bz783sqM2vN33t49+ZgMD4h2
TL5C0pCae/Ptrd60YRr/hfXIBahs+vMpNhrlg370q5Rw0ahGvO6KP2Sz+g5+T6Gt
ikkMEKEMZP48HEBbhHpIUKnczTtPHt6X2seh/xG2btHtuBMHreh0gDbnmUIFf5rF
/xGBNybpdB0GO2SzBRWUzCrW6hI8Ujx8s8R2GutGjBdgbLPml1Jmp4hfx+ImgIgY
wSHRRV49OibLGhIe1rVGtp6K2egH9PidyIfXDnqWFN/Eif78+8/qeoz1b3vVqdiM
NWVg6wQDQfP8W/HbcetnvrPSiRDyhYZzH1OrMZO94JO/5S3UCyM=
=Vz5T
-END PGP SIGNATURE End Message ---
Bug#973135: marked as done (plexus-io: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmav
Your message dated Mon, 22 Feb 2021 19:33:37 + with message-id and subject line Bug#973135: fixed in plexus-io 3.2.0-1.1 has caused the Debian Bug report #973135, regarding plexus-io: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode test returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 973135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973135 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: plexus-io Version: 3.2.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201027 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package plexus-io > dpkg-buildpackage: info: source version 3.2.0-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by tony mancill > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean >dh_auto_clean > bash -c "for dir in \$(find . -name target -type d); do if [ -f \$(echo > \$dir | sed -e s/target\$/pom.xml/) ]; then rm -Rf \$dir; fi done" > mh_unpatchpoms -plibplexus-io-java >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building plexus-io using existing > ./plexus-io_3.2.0.orig.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building plexus-io in plexus-io_3.2.0-1.debian.tar.xz > dpkg-source: info: building plexus-io in plexus-io_3.2.0-1.dsc > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > mh_patchpoms -plibplexus-io-java --debian-build --keep-pom-version > --maven-repo=/<>/debian/maven-repo >dh_auto_build > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > -DskipTests -Dnotimestamp=true -Dlocale=en_US > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by > com.google.inject.internal.cglib.core.$ReflectUtils$1 > (file:/usr/share/maven/lib/guice.jar) to method > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain) > WARNING: Please consider reporting this to the maintainers of > com.google.inject.internal.cglib.core.$ReflectUtils$1 > WARNING: Use --illegal-access=warn to enable warnings of further illegal > reflective access operations > WARNING: All illegal access operations will be denied in a future release > [INFO] Scanning for projects... > [INFO] > [INFO] ---< org.codehaus.plexus:plexus-io > > > [INFO] Building Plexus IO Components 3.2.0 > [INFO] [ jar > ]- > [WARNING] The artifact org.codehaus.plexus:plexus-container-default:jar:1.5.5 > has been relocated to org.codehaus.plexus:plexus-container-default:jar:debian > [INFO] > [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ > plexus-io --- > [WARNING] Using platform encoding (UTF-8 actually) to copy filtered > resources, i.e. build is platform dependent! > [INFO] Copying 1 resource > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ plexus-io > --- > [INFO] Changes detected - recompiling the module! > [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. > build is platform dependent! > [INFO] Compiling 52 source files to /<>/target/classes > [INFO] >
Bug#970839: marked as done (psychtoolbox-3: please move away from libdc1394-22-dev to libdc1394-dev)
Your message dated Mon, 22 Feb 2021 19:19:55 + with message-id and subject line Bug#970839: fixed in psychtoolbox-3 3.0.17.9.dfsg1-1 has caused the Debian Bug report #970839, regarding psychtoolbox-3: please move away from libdc1394-22-dev to libdc1394-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 970839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: psychtoolbox-3 Version: 3.0.16.20200326.dfsg1-1.1 Severity: important tags: patch Hello, please do the switch, the old libdc1394-22 source packages will be removed, and reverse-dependencies should move to the new libdc1394 package. The old libdc1394-22-dev is now provided by the new source package as transitional package, but I presume it will go away eventually, so please adapt to the new versionless dev scheme thanks Gianfranco --- End Message --- --- Begin Message --- Source: psychtoolbox-3 Source-Version: 3.0.17.9.dfsg1-1 Done: Yaroslav Halchenko We believe that the bug you reported is fixed in the latest version of psychtoolbox-3, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yaroslav Halchenko (supplier of updated psychtoolbox-3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Feb 2021 13:03:01 -0500 Source: psychtoolbox-3 Architecture: source Version: 3.0.17.9.dfsg1-1 Distribution: unstable Urgency: medium Maintainer: NeuroDebian Team Changed-By: Yaroslav Halchenko Closes: 970839 Changes: psychtoolbox-3 (3.0.17.9.dfsg1-1) unstable; urgency=medium . * New upstream release * debian/rules - use DFSG version of the splash screen without pixabay frog - build also 11 13 14 15 extensions * debian/control + libopenhmd-dev build-dependency + libvulkan-dev (>= 1.1~) build-dependency + added 1.8~ as minimal version for gstreamer (plugins base) - made libdc1394-dev to be of preference over libdc1394-22-dev in B-Depends (Closes: #970839). Left old libdc1394-22-dev as an alternative for easier backports Checksums-Sha1: 35ef6399758b41c9d507b5347227c8157a51e6d8 3198 psychtoolbox-3_3.0.17.9.dfsg1-1.dsc 0ffa75a58f5e3909116b4e60100fb81ee825c732 34682558 psychtoolbox-3_3.0.17.9.dfsg1.orig.tar.gz 1b2a705b46c2d19a580680f62e133227a0057e66 52148 psychtoolbox-3_3.0.17.9.dfsg1-1.debian.tar.xz f8879cec94fddbc8dd88682a8f6eaf680e09615c 28010 psychtoolbox-3_3.0.17.9.dfsg1-1_source.buildinfo Checksums-Sha256: b3015361844f1f82530c5d30f6e9f1565b7e9e2c610532214c60ede5307acdec 3198 psychtoolbox-3_3.0.17.9.dfsg1-1.dsc 5927657995b616db50505fa6555352aacac432b99950c53fbbf4bf462e4f2965 34682558 psychtoolbox-3_3.0.17.9.dfsg1.orig.tar.gz 56f2cafe5a7e67e338eab321a6d66822cf022f47fa8afd84cff39dbabb0e55ac 52148 psychtoolbox-3_3.0.17.9.dfsg1-1.debian.tar.xz fa32d27d0bc7dd5866bc9eb2650a668a914b92a138a1c19539b45809f9b5c91f 28010 psychtoolbox-3_3.0.17.9.dfsg1-1_source.buildinfo Files: d2136cf71718a5c041b47b6c589be4d8 3198 science optional psychtoolbox-3_3.0.17.9.dfsg1-1.dsc 6f2ef85efb29f8e1973b5ddffc1c501f 34682558 science optional psychtoolbox-3_3.0.17.9.dfsg1.orig.tar.gz 76394847157c0b9802ab12eb28ba75ec 52148 science optional psychtoolbox-3_3.0.17.9.dfsg1-1.debian.tar.xz 093a997f49f34832859f645d811cded0 28010 science optional psychtoolbox-3_3.0.17.9.dfsg1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEExbkF8OjZ/ZZo/zZvot4jUGLaM/oFAmAz8ooACgkQot4jUGLa M/oXMBAAjtiASFdoBlVOjLivVW/h2CQJZ6VTLUS3xa/udh91DAtZaGkZIxyE66Bk LV02oU62GxA31xDWWW1WPr3PVubJK9wXGtzGs9t7IWLIRjsb+DUhVCETyS8Q0Hb+ v6CWnwviBWjsaUh7ipEW2wDIYYIS8uL6XXoXpPrQ2rsJbV49OjoaDwhHj+0SEhiK 4eWuM5ObqPaRj/tLzOh63Rn25tRV4tnnPsqKY0oOf8tiH1PhV24JzXosohgmlIFi EjrXMtdfz5FqnLeLP6Ipa8bhbwlOM5Z/IDVt6AkDEUkHhlgAdQIAr/EIuB7OD1Zw T8L+hIYCyYz7l9KPq2xITBQn+1tuAoBocFE3Tvl6zuvmcipUuM9ttSAHEU8o2x7s KdYl4bg0kn0CeuAsJ7ZOjftmhE+ruF4xyQ+NztMNGYAFMFSNtoDffA6CUoK0tJjG vDJfqRFlnAU2/qqi+PKivy3LRWRh/lRWEtGXu8hIk49bOiSdXeZLtMKDWmF5rQ5q JuBjz5aFCha80yO168vgkv8fbfta9DJAtuKrQBtaWBsYGOpsEiOJQm4rw87BcOYE
Bug#941867: marked as done (qt-gstreamer FTBFS: error: invalid cast from type ‘const CapsPtr’ to type ‘GstMiniObject*’)
Your message dated Mon, 22 Feb 2021 19:04:30 +
with message-id
and subject line Bug#941867: fixed in qt-gstreamer 1.2.0-5.1
has caused the Debian Bug report #941867,
regarding qt-gstreamer FTBFS: error: invalid cast from type ‘const CapsPtr’ to
type ‘GstMiniObject*’
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
941867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941867
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qt-gstreamer
Version: 1.2.0-5
Severity: serious
Tags: ftbfs
qt-gstreamer fails to build from source in unstable on amd64. A build in
sbuild ends with:
| [ 22%] Building CXX object src/QGst/CMakeFiles/Qt5GStreamer.dir/caps.cpp.o
| cd /<>/obj-x86_64-linux-gnu/src/QGst && /usr/bin/c++
-DGST_DISABLE_LOADSAVE -DGST_DISABLE_XML
-DQTGLVIDEOSINK_NAME=\"qt5glvideosink\" -DQTVIDEOSINK_NAME=\"qt5videosink\"
-DQT_CORE_LIB -DQT_NO_DEBUG -DQT_NO_KEYWORDS
-DQWIDGETVIDEOSINK_NAME=\"qwidget5videosink\" -DQt5GStreamer_EXPORTS
-I/<>/obj-x86_64-linux-gnu/src/QGst -I/<>/src/QGst
-I/<>/obj-x86_64-linux-gnu/src/QGst/Qt5GStreamer_autogen/include
-I/<>/src -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem
/usr/include/x86_64-linux-gnu/qt5 -isystem
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra
-Wformat-security -Wundef -Wpointer-arith -fno-common -fvisibility=hidden
-fvisibility-inlines-hidden -std=c++0x -O2 -g -DNDEBUG -fPIC -pthread
-I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -fPIC -std=gnu++11 -o
CMakeFiles/Qt5GStreamer.dir/caps.cpp.o -c /<>/src/QGst/caps.cpp
| In file included from /usr/include/gstreamer-1.0/gst/gstbuffer.h:30,
| from /usr/include/gstreamer-1.0/gst/gstpad.h:70,
| from /usr/include/gstreamer-1.0/gst/gstelement.h:87,
| from /usr/include/gstreamer-1.0/gst/gstbin.h:27,
| from /usr/include/gstreamer-1.0/gst/gst.h:35,
| from /<>/src/QGst/caps.cpp:22:
| /<>/src/QGst/caps.cpp: In member function ‘void
QGst::Caps::append(const CapsPtr&)’:
| /usr/include/gstreamer-1.0/gst/gstminiobject.h:33:65: error: invalid cast
from type ‘const CapsPtr’ {aka ‘const QGlib::RefPointer’} to type
‘GstMiniObject*’ {aka ‘_GstMiniObject*’}
|33 | #define GST_MINI_OBJECT_CAST(obj) ((GstMiniObject*)(obj))
| | ^
| /usr/include/gstreamer-1.0/gst/gstcaps.h:35:47: note: in definition of macro
‘GST_CAPS_CAST’
|35 | #define GST_CAPS_CAST(obj)((GstCaps*)(obj))
| | ^~~
| /usr/include/gstreamer-1.0/gst/gstcaps.h:249:29: note: in expansion of macro
‘GST_CAPS’
| 249 | #define gst_caps_copy(caps) GST_CAPS (gst_mini_object_copy
(GST_MINI_OBJECT_CAST (caps)))
| | ^~~~
| /usr/include/gstreamer-1.0/gst/gstcaps.h:249:61: note: in expansion of macro
‘GST_MINI_OBJECT_CAST’
| 249 | #define gst_caps_copy(caps) GST_CAPS (gst_mini_object_copy
(GST_MINI_OBJECT_CAST (caps)))
| |
^~~~
| /<>/src/QGst/caps.cpp:57:40: note: in expansion of macro
‘gst_caps_copy’
|57 | gst_caps_append(object(), gst_caps_copy(caps2));
| |^
| make[4]: *** [src/QGst/CMakeFiles/Qt5GStreamer.dir/build.make:122:
src/QGst/CMakeFiles/Qt5GStreamer.dir/caps.cpp.o] Error 1
| make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[3]: *** [CMakeFiles/Makefile2:352:
src/QGst/CMakeFiles/Qt5GStreamer.dir/all] Error 2
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[2]: *** [Makefile:144: all] Error 2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 all returned exit code 2
| make[1]: *** [debian/rules:18: override_dh_auto_build-arch] Error 255
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:36: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Reproducible by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/qt-gstreamer_1.2.0-5.rbuild.log.gz
Helmut
--- End Message ---
--- Begin Message ---
Source: qt-gstreamer
Source-Version:
Bug#924482: marked as done (cyrus-imapd: Invisible subfolders for admins after upgrade from 2.5 to 3.0)
Your message dated Mon, 22 Feb 2021 19:51:34 +0100 with message-id <4285f6c3-0918-d103-ca66-55a92c8e5...@debian.org> and subject line Re: cyrus-imapd: Invisible subfolders for admins after upgrade from 2.5 to 3.0 has caused the Debian Bug report #924482, regarding cyrus-imapd: Invisible subfolders for admins after upgrade from 2.5 to 3.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 924482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cyrus-imapd Version: 3.0.8-4 Severity: normal Dear Maintainer, * What led up to the situation? - Package upgrade from 2.5.11-1+b2 to 3.0.8-4. * What exactly did you do (or not do) that was effective (or ineffective)? - Just regular apt upgrade * What was the outcome of this action? - One of my users, who is configured as admin in imapd.conf, lost visibility of all his subfolders after the upgrade. Inbox works normally though. This is not a client issue, the subfolders are not visible in ThunderbirdAndroid Gmail client, Alpine and cyradm. Reconstructing does not fix the issue. After removing this user from the admins config option, all subfolders reappear in all clients. * What outcome did you expect instead? - Having a working mailbox including subfolders for all my users, admin or not. Thanks, Robbert -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (102, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cyrus-imapd depends on: ii cyrus-common 3.0.8-4 ii dpkg 1.19.5 ii libc6 2.28-8 ii libcom-err2 1.44.5-1 ii libsasl2-22.1.27+dfsg-1 ii libssl1.1 1.1.1b-1 ii libwrap0 7.6.q-28 ii zlib1g1:1.2.11.dfsg-1 cyrus-imapd recommends no packages. cyrus-imapd suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Le 22/02/2021 à 11:32, Yadd a écrit : >> This bug is definitely still open. I ran into the same exact issue >> today. > > Hi, > > did you find this issue in versions 3.2.x or only in 3.0.x ? > > Cheers, > Xavier Upstream response: " The documentation in imapd.conf for admins: says it: Note that accounts used by users should not be administrators. Administrative accounts should not receive mail. That is, if user "jbRo" is a user reading mail, he should not also be in the admins line. Some problems may occur otherwise, most notably the ability of administrators to create top-level mailboxes visible to users, but not writable by users. The text is present there since at leas 2003. "--- End Message ---
Bug#982290: marked as done (disulfinder FTCBFS: hard codes the build architecture compiler g++)
Your message dated Mon, 22 Feb 2021 18:33:34 +
with message-id
and subject line Bug#982290: fixed in disulfinder 1.2.11-10
has caused the Debian Bug report #982290,
regarding disulfinder FTCBFS: hard codes the build architecture compiler g++
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
982290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: disulfinder
Version: 1.2.11-9
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
disulfinder fails to cross build from source, because one of its many
Makefiles hard codes the build architecture compiler g++. After making
it substitutable, disulfinder cross builds successfully. Please consider
applying the attached patch.
Helmut
--- disulfinder-1.2.11.orig/disulfind/src/Common/Makefile
+++ disulfinder-1.2.11/disulfind/src/Common/Makefile
@@ -12,13 +12,13 @@
lib : libCommon.a
Eig: Decomposition.o ${OBJECTFILES}
- g++ -o $@ $+ ${LIBS}
+ $(CXX) -o $@ $+ ${LIBS}
Norm: Norm.o ${OBJECTFILES}
- g++ -o $@ $+ ${LIBS}
+ $(CXX) -o $@ $+ ${LIBS}
%.o: %.cpp
- g++ $(CPPFLAGS) $(CXXFLAGS) -c $< -o $@
+ $(CXX) $(CPPFLAGS) $(CXXFLAGS) -c $< -o $@
clean:
$(MAKE) -C eig clean
--- End Message ---
--- Begin Message ---
Source: disulfinder
Source-Version: 1.2.11-10
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
disulfinder, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 982...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nilesh Patra (supplier of updated disulfinder package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Feb 2021 23:39:27 +0530
Source: disulfinder
Architecture: source
Version: 1.2.11-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Nilesh Patra
Closes: 982290
Changes:
disulfinder (1.2.11-10) unstable; urgency=medium
.
* Team Upload.
* Fix FTCBFS by not hardcoding build arch compiler
- Thank you, Helmut Grohne! (Closes: #982290)
* Remove useless .dirs where no data is installed
* Migrate to secure URLs
Checksums-Sha1:
03253bb51268701702907e249d209b1ceafe8660 2194 disulfinder_1.2.11-10.dsc
cb9a6599e2ed8664524d82cba91ae1cbc6e02911 8144
disulfinder_1.2.11-10.debian.tar.xz
6f2307490893bd4478990b9c4460523419ba7dea 6545
disulfinder_1.2.11-10_amd64.buildinfo
Checksums-Sha256:
ac41c612dc02cc39f661df98a7343f08d90a647e8d07ccfc5114b13e891cb3b8 2194
disulfinder_1.2.11-10.dsc
76935477245fbf7688de920881c28e1909ac391b000b4b83a75535f73cc20b0c 8144
disulfinder_1.2.11-10.debian.tar.xz
1f75a72211ffa14947a3d615d757903b7ce0d3c29f874dee8ad0db250e067d36 6545
disulfinder_1.2.11-10_amd64.buildinfo
Files:
a94d3eb6664f5cc1d374bd58101408c4 2194 science optional
disulfinder_1.2.11-10.dsc
8f728e09b3cac3710dd02486831d67a1 8144 science optional
disulfinder_1.2.11-10.debian.tar.xz
d61dddfc835d69a1c30e8c4d60b9 6545 science optional
disulfinder_1.2.11-10_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmAz9XIUHG5wYXRyYTk3
NEBnbWFpbC5jb20ACgkQALrnSzQzafGFtRAAoKuUvowK8IypJ0OVGaR42yYt1AeJ
cwWl1rszSHsIkUYK8vap0umndg83Q134hqeb0SjsM51GfIX5kneHIemY/u2dNgFT
R92FjHRkIMCranJImpxJ75Ax8S4bxj5PuS7E5+VMwrOwTdw/bJ8xqlu1KkVd2fLx
24VQZDjs05jly1xBKmLEQ/gnlP7BBGvuOraUSXEKQu0+c0E90+IOOZnnsGXPLmGe
QP2UkOoJn/XiNMuqt75Z/zXm73JXyeilEnS8gedvm+kb6QZNZHuplyQd69D1FVFU
a9IXdKqEGLS2xZeThki3PVs3aInQ0WiZ318Gml3WMOQbZsDTgz9aGFdq/Xx9C5+J
5TDvfpTsFHty1msOdzObhG83EwQwBK+TZQt7d3+BKAwpH1EH3V+vf5ihZKLmk5aj
7dvq99dwiK0u1XciltC2gFxmy9iOvOHUpQtqYElFoiirX5Swav7h/VGgZAW/Xruq
Nw7t1F23Za5wHAV0O3mEpSvxsqzvz60MhAm8LyRtJjdLo1rtBXgkCiRbWH7COeIU
GAEmBO+5mZQ0Mls1oZw1lYaw2bKLThn1sfHjYfiSEPSfCJy/RbFGlFjdg2sMWaze
twzjOLe/Z6ALO3ZsU+Tl4D1X68I9LDfAWKtgxk/YIfX6PbnSpuXiQb9GbXSNQb30
bS7MmbsgY76EjME=
=D8vG
-END PGP SIGNATURE End Message ---
Bug#983298: marked as done (unblock: ocserv/1.1.2-2)
Your message dated Mon, 22 Feb 2021 19:30:25 +0100
with message-id
and subject line Re: Bug#983298: unblock: ocserv/1.1.2-2
has caused the Debian Bug report #983298,
regarding unblock: ocserv/1.1.2-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal
Dear release team,
This is a pre-approval request that please unblock package ocserv/1.1.2-2, which
is a version with cherry picked upstream bug fixes.
unblock ocserv/1.1.2-2
Regards,
Aron
diff -Nru ocserv-1.1.2/debian/changelog ocserv-1.1.2/debian/changelog
--- ocserv-1.1.2/debian/changelog 2020-12-17 18:38:57.0 +0800
+++ ocserv-1.1.2/debian/changelog 2021-02-22 11:37:07.0 +0800
@@ -1,3 +1,9 @@
+ocserv (1.1.2-2) unstable; urgency=medium
+
+ * d/patches: cherry-pick upstream post 1.1.2 bug fixes
+
+ -- Aron Xu Mon, 22 Feb 2021 11:37:07 +0800
+
ocserv (1.1.2-1) unstable; urgency=medium
* New upstream version 1.1.2
diff -Nru
ocserv-1.1.2/debian/patches/0009-update_auth_time_stats-cast-operations-to-avoid-over.patch
ocserv-1.1.2/debian/patches/0009-update_auth_time_stats-cast-operations-to-avoid-over.patch
---
ocserv-1.1.2/debian/patches/0009-update_auth_time_stats-cast-operations-to-avoid-over.patch
1970-01-01 08:00:00.0 +0800
+++
ocserv-1.1.2/debian/patches/0009-update_auth_time_stats-cast-operations-to-avoid-over.patch
2021-02-22 11:33:03.0 +0800
@@ -0,0 +1,27 @@
+From e035221030f8fdfbb38483889631916fef9d9798 Mon Sep 17 00:00:00 2001
+From: Nikos Mavrogiannopoulos
+Date: Wed, 9 Dec 2020 15:05:24 +0100
+Subject: [PATCH 09/36] update_auth_time_stats: cast operations to avoid
+ overflows
+
+Signed-off-by: Nikos Mavrogiannopoulos
+---
+ src/sec-mod-auth.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/sec-mod-auth.c b/src/sec-mod-auth.c
+index c769643c..b4b2f3fd 100644
+--- a/src/sec-mod-auth.c
b/src/sec-mod-auth.c
+@@ -131,7 +131,7 @@ static void update_auth_time_stats(sec_mod_st * sec,
time_t secs)
+
+ if (secs > sec->max_auth_time)
+ sec->max_auth_time = secs;
+- sec->avg_auth_time =
(sec->avg_auth_time*(sec->total_authentications-1)+secs) /
sec->total_authentications;
++ sec->avg_auth_time =
((uint64_t)sec->avg_auth_time*((uint64_t)(sec->total_authentications-1))+secs)
/ (uint64_t)sec->total_authentications;
+ }
+
+ static
+--
+2.20.1
+
diff -Nru
ocserv-1.1.2/debian/patches/0020-ocserv-worker-renamed-loop-to-worker_loop.patch
ocserv-1.1.2/debian/patches/0020-ocserv-worker-renamed-loop-to-worker_loop.patch
---
ocserv-1.1.2/debian/patches/0020-ocserv-worker-renamed-loop-to-worker_loop.patch
1970-01-01 08:00:00.0 +0800
+++
ocserv-1.1.2/debian/patches/0020-ocserv-worker-renamed-loop-to-worker_loop.patch
2021-02-22 11:35:22.0 +0800
@@ -0,0 +1,131 @@
+From 47c6638286a694b4d278e01b278f64f9368b3e1a Mon Sep 17 00:00:00 2001
+From: Nikos Mavrogiannopoulos
+Date: Sat, 12 Dec 2020 22:41:50 +0100
+Subject: [PATCH 20/36] ocserv-worker: renamed loop to worker_loop
+
+This avoids warnings and static analyzers complains about
+the libev functions hiding the global 'loop' variable
+
+Signed-off-by: Nikos Mavrogiannopoulos
+---
+ src/worker-vpn.c | 34 +-
+ 1 file changed, 17 insertions(+), 17 deletions(-)
+
+Index: ocserv/src/worker-vpn.c
+===
+--- ocserv.orig/src/worker-vpn.c
ocserv/src/worker-vpn.c
+@@ -95,7 +95,7 @@ struct worker_st *global_ws = NULL;
+ static int terminate = 0;
+ static int terminate_reason = REASON_SERVER_DISCONNECT;
+
+-static struct ev_loop *loop = NULL;
++static struct ev_loop *worker_loop = NULL;
+ ev_io command_watcher;
+ ev_io tls_watcher;
+ ev_io tun_watcher;
+@@ -433,8 +433,8 @@ static int setup_dtls_connection(struct
+ dtls->dtls_session = session;
+ ev_init(>io, dtls_watcher_cb);
+ ev_io_set(>io, dtls->dtls_tptr.fd, EV_READ);
+- ev_io_start(loop, >io);
+- ev_invoke(loop, >io, EV_READ);
++ ev_io_start(worker_loop, >io);
++ ev_invoke(worker_loop, >io, EV_READ);
+
+ return 0;
+ fail:
+@@ -2609,7 +2609,7 @@ static int test_for_tcp_health_probe(str
+
+ static void syserr_cb (const char *msg)
+ {
+- struct worker_st * ws = ev_userdata(loop);
++ struct worker_st * ws = ev_userdata(worker_loop);
+
Bug#983347: marked as done (lintian-brush: postrm is skipped by the fixer of maintainer-script-without-set-e)
Your message dated Mon, 22 Feb 2021 18:19:34 + with message-id and subject line Bug#983347: fixed in lintian-brush 0.99 has caused the Debian Bug report #983347, regarding lintian-brush: postrm is skipped by the fixer of maintainer-script-without-set-e to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lintian-brush Version: 0.97 Severity: normal Dear Maintainer, I launched lintian-brush 0.97 in the tree of my package jalview and it fixed the maintainer-script-without-set-e by modifying debian/config and debian/postinst but not debian/postrm, although the three of them were starting with #!/bin/sh -e and then a blank line. To reproduce, you may clone the jalview Salsa repository and be back to revision HEAD^^^ as of today (after commit 936ed870: Updating changelog) on the master branch, then run lintian-brush from there. Thanks for all the work on lintian-brush which is definitely a precious tool, Cheers, Pierre -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (90, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 lintian-brush depends on: ii devscripts 2.20.5 ii ognibuild0.0.1~git20201031.4cbc8df-1.1 ii python3 3.9.1-1 ii python3-breezy 3.1.0-8 ii python3-debian 0.1.39 ii python3-debmutate0.20 ii python3-distro-info 1.0 ii python3-dulwich 0.20.15-1 ii python3-iniparse 0.4-3 ii python3-ruamel.yaml 0.16.12-2 ii python3-upstream-ontologist 0.1.9-1 Versions of packages lintian-brush recommends: ii decopy 0.2.4.4-0.1 ii dos2unix 7.4.1-1 ii gpg 2.2.20-1 ii libdebhelper-perl13.3.3 ii lintian 2.104.0 ii python3-asyncpg 0.21.0-1+b2 ii python3-bs4 4.9.3-1 ii python3-levenshtein 0.12.1-1 ii python3-pyinotify0.9.6-1.3 ii python3-toml 0.10.1-1 Versions of packages lintian-brush suggests: pn breezy-debian pn gnome-pkg-tools ii po-debconf 1.0.21+nmu1 pn postgresql-common -- no debconf information --- End Message --- --- Begin Message --- Source: lintian-brush Source-Version: 0.99 Done: Jelmer Vernooij We believe that the bug you reported is fixed in the latest version of lintian-brush, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated lintian-brush package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 17:53:37 + Source: lintian-brush Architecture: source Version: 0.99 Distribution: unstable Urgency: medium Maintainer: Jelmer Vernooij Changed-By: Jelmer Vernooij Closes: 983347 Changes: lintian-brush (0.99) unstable; urgency=medium . * Also update 'set -e' in postrm files. Closes: #983347 Checksums-Sha1: e8ab741a0b812234505aa294a67c0be25aedaf51 2172 lintian-brush_0.99.dsc 439e008650db089525657d8b534df4f51548c91e 903888 lintian-brush_0.99.tar.xz 9f9250129fd0e5d9a7d06a9b61f3f35a35b299fb 12366 lintian-brush_0.99_amd64.buildinfo Checksums-Sha256: 85e4aea0c5e542987c278048cb0eb4f77567e5a6083c780b3c740fdd5554d8fb 2172 lintian-brush_0.99.dsc b585c23d32ef09fb50dc57d759f136bc1268f1d17714ccb2351fc21b2bb1be8d 903888 lintian-brush_0.99.tar.xz ad545bbbed6250b535c2300e3092632d49db1cf453c9ca0e2be9d42259be2df9 12366 lintian-brush_0.99_amd64.buildinfo Files: 0a24297f9a95fb2089021e74b9dd708f 2172 devel optional lintian-brush_0.99.dsc 22341a6b1cb7ee73f87257b7e2afa45c 903888 devel optional lintian-brush_0.99.tar.xz 55dd8f49cff51023884001740b960ea8 12366 devel optional
Bug#976002: marked as done (tigervnc-common: MaxDisconnectionTime is only respected before the first connection)
Your message dated Mon, 22 Feb 2021 18:03:49 + with message-id and subject line Bug#976002: fixed in tigervnc 1.11.0+dfsg-1 has caused the Debian Bug report #976002, regarding tigervnc-common: MaxDisconnectionTime is only respected before the first connection to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tigervnc-common Version: 1.10.1+dfsg-9 Severity: important X-Debbugs-Cc: modem93+deb...@gmail.com Dear maintainer, Due to a bug in v1.10, MaxDisconnectionTime is not respected. This is fixed in v1.11 by [1]. Please include the patch, or upload a new package based on v1.11. I apologise if this request is unnecessary or misplaced. Thank you. [1]: https://github.com/TigerVNC/tigervnc/commit/38726ce083db1a9227325bf87989513499bfa698 -- System Information: Debian Release: bullseye/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.17-1rodete4-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tigervnc-common depends on: ii libc6 2.31-3 ii libgcc-s1 10.2.0-9 ii libstdc++6 10.2.0-9 ii libx11-62:1.6.10-3+build1 tigervnc-common recommends no packages. tigervnc-common suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: tigervnc Source-Version: 1.11.0+dfsg-1 Done: Joachim Falk We believe that the bug you reported is fixed in the latest version of tigervnc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joachim Falk (supplier of updated tigervnc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Feb 2021 18:19:01 +0100 Source: tigervnc Architecture: source Version: 1.11.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: TigerVNC Packaging Team Changed-By: Joachim Falk Closes: 976002 Changes: tigervnc (1.11.0+dfsg-1) unstable; urgency=medium . [ Joachim Falk ] * Fresh upstream TigerVNC 1.11.0 (Closes: #976002). . [ Debian Janitor ] * Use correct machine-readable copyright file URI. * Fix field name case in debian/copyright (COpyright => Copyright). * Remove obsolete field Name from debian/upstream/metadata (already present in machine-readable debian/copyright). Checksums-Sha1: 572545ace95b1d81cd38981dc61882da10c30a48 3967 tigervnc_1.11.0+dfsg-1.dsc 779820f0f1b10d4ed51484a83a2de4a6bd191a8b 899484 tigervnc_1.11.0+dfsg.orig.tar.xz 97cc0c2756420e84cadbc5821a0e33887e9d5c6d 66900 tigervnc_1.11.0+dfsg-1.debian.tar.xz dcb9332a45b6eaaa382a5a0274da0227d1ae9337 7452 tigervnc_1.11.0+dfsg-1_source.buildinfo Checksums-Sha256: f94200249c1497eab64bdb0136a7ea02ff7b83cfebe84aef6d2d8cb441eb5ba5 3967 tigervnc_1.11.0+dfsg-1.dsc 22f06dcbac3bd7247b53233e11455cc295caecfe9349f27869371b31062e3dcb 899484 tigervnc_1.11.0+dfsg.orig.tar.xz 1b117821bef73fad670a43604eddc42b3fabdb42f8c45f9a4d003faad9f5a099 66900 tigervnc_1.11.0+dfsg-1.debian.tar.xz 647dbf3b938d5610d46528d25f013d9ef8776b8d6234ff90d526920c4e587fd2 7452 tigervnc_1.11.0+dfsg-1_source.buildinfo Files: 1dabccfc7e4191535d51cb314a7def9b 3967 x11 optional tigervnc_1.11.0+dfsg-1.dsc dae900327ece376b22bb2accc3c58034 899484 x11 optional tigervnc_1.11.0+dfsg.orig.tar.xz 30941e0b5effeb08fd6878b624ca9a4d 66900 x11 optional tigervnc_1.11.0+dfsg-1.debian.tar.xz bac90181ea28edb4ffd02ca73ea0d5d4 7452 x11 optional tigervnc_1.11.0+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEd0JxOxv4oYU15116MFSGLSVGoYAFAmAz59QUHGpvYWNoaW0u ZmFsa0BnbXguZGUACgkQMFSGLSVGoYBDyRAApBQizm5IVIJr+p0iGF72JrXhat8A EyRK7b2hd1pntbWhR06mYF9PVuATKJOvZv0UBm3CGMKabjFpCOqGwSzgMo/JQZZ1 Y3iiwOLxoNm72MY39WRdC7dEeLdD7xJz9AX4Ljy1uCSD02R3EgawgBdzt9Hx2hER Cd9eltcD/1l4XJ/L2WPGSGMMT/nnnK0ggosRP3YtnCg2/BAf3+DKvRSc29ajhB1u
Bug#980607: marked as done (netcfg: FTBFS: test/test_inet_mton.c:12:15: error: too many arguments for format [-Werror=format-extra-args])
Your message dated Mon, 22 Feb 2021 17:18:58 + with message-id and subject line Bug#980607: fixed in netcfg 1.171 has caused the Debian Bug report #980607, regarding netcfg: FTBFS: test/test_inet_mton.c:12:15: error: too many arguments for format [-Werror=format-extra-args] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netcfg Version: 1.169 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -c -W -Wall -Werror -DNDEBUG -DNETCFG_VERSION="\"1.169\"" -I. -DWIRELESS > -DNM -Os -fomit-frame-pointer -o test/test_inet_mton.o test/test_inet_mton.c > In file included from test/srunner.h:1, > from test/test_inet_mton.c:1: > test/test_inet_mton.c: In function ‘test_inet_mton_v4_24_fn’: > test/test_inet_mton.c:12:15: error: too many arguments for format > [-Werror=format-extra-args] >12 | "Mask address wasn't 24 bits"); > | ^ > test/test_inet_mton.c: In function ‘test_inet_mton_v4_22_fn’: > test/test_inet_mton.c:24:15: error: too many arguments for format > [-Werror=format-extra-args] >24 | "Mask address wasn't 22 bits"); > | ^ > test/test_inet_mton.c: In function ‘test_inet_mton_v6_64_fn’: > test/test_inet_mton.c:38:15: error: too many arguments for format > [-Werror=format-extra-args] >38 | "Mask address wasn't 64 bits"); > | ^ > test/test_inet_mton.c: In function ‘test_inet_mton_v6_60_fn’: > test/test_inet_mton.c:52:15: error: too many arguments for format > [-Werror=format-extra-args] >52 | "Mask address wasn't 60 bits"); > | ^ > cc1: all warnings being treated as errors > make[1]: *** [Makefile:60: test/test_inet_mton.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/01/20/netcfg_1.169_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: netcfg Source-Version: 1.171 Done: Holger Wansing We believe that the bug you reported is fixed in the latest version of netcfg, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Wansing (supplier of updated netcfg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 17:58:31 +0100 Source: netcfg Architecture: source Version: 1.171 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Holger Wansing Closes: 980607 Changes: netcfg (1.171) unstable; urgency=medium . * Team upload . [ Francisco Vilmar Cardoso Ruviaro ] * Update testcases to work with current Check API, patch from Dennis Filder . (Closes: #980607) * Satisfy GCC pedantery for strncpy() calls, patch from Dennis Filder . . [ Updated translations ] * Catalan (ca.po) by d * Danish (da.po) by Michael Millet * Galician (gl.po) by mantinan * Hindi (hi.po) by KushagraKarira * Kannada (kn.po) by Yogesh * Latvian (lv.po) by Tranzistors * Romanian (ro.po) by Sergiu * Albanian
Bug#586264: marked as done (libpam-fprint does not work with sudo)
Your message dated Mon, 22 Feb 2021 17:36:58 +0100 with message-id and subject line Re: SV: Bug#586264: probably belongs to sudo has caused the Debian Bug report #586264, regarding libpam-fprint does not work with sudo to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 586264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-fprint Version: 20080330+git-5 Severity: normal *** Please type your report below this line *** libpam-fprint does no longer work with sudo. It did in the past (a month or two ago) but with an sudo update, it stopped working. This was the old experimental version. In the meantime I have got the new version installed (in testing) and the same problem happens. I no longer have fprint configured in pam manually but automatically with "dpkg-reconfigure libpam-fprint" - this gives the same behaviour. If I disable unix authentication, sudo just skips to say that it cannot find a suitable authentication mechanism. fprint works perfectly well with su, gdm (versions 2 and 3) and console login, eg.: moffe@hactar:~$ su - moffe Scan right index finger on UPEK TouchStrip moffe@hactar:~$ exit logout moffe@hactar:~$ sudo bash [sudo] password for moffe: root@hactar:~# Notice how sudo goes directly to password authentication while su does only if fingerprint fails. This is, of course, just annoying (I know my password :-), but sudo is probably the authentication I use the most. I have no idea what the actual problem is, but I am almost sure this sudo update is the problem: sudo (1.7.2p6-1) unstable; urgency=low * new upstream version fixing CVE-2010-1163, closes: #578275, #570737 -- Bdale Garbee Mon, 19 Apr 2010 10:45:47 -0600 Note that I only *assume* this is an fprint problem - feel free to reassign to sudo if you think it is the problem... Regards /Rasmus Bøg Hansen -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34 (SMP w/2 CPU cores) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to da_DK.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpam-fprint depends on: ii libc6 2.11.1-3 Embedded GNU C Library: Shared lib ii libfprint0 20081125git-4 async fingerprint library of fprin ii libpam-runtime 1.1.1-3 Runtime support for the PAM librar ii libpam0g 1.1.1-3 Pluggable Authentication Modules l libpam-fprint recommends no packages. libpam-fprint suggests no packages. -- no debconf information -- Rasmus Bøg Hansen || mo...@zz9.dk C.F. Møllers Allé 46, 3tv || http://www.zz9.dk 2300 København S || --- End Message --- --- Begin Message --- Version: 1.8.27-1 On Mon, Feb 22, 2021 at 05:30:09PM +0100, Rasmus Bøg Hansen wrote: > I can, unfortunately, not. My laptop from back then has been buried since a > long time ago and my current one does not have a driver for the fingerprint > reader, so I have not been using fprint for years. Thanks for the quick answer. I'm marking this issue as resolved for the version currently in buster. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421--- End Message ---
Bug#982001: marked as done (lucene-solr: FTBFS with OpenJDK 17 due to rmic removal)
Your message dated Mon, 22 Feb 2021 16:33:42 + with message-id and subject line Bug#982001: fixed in lucene-solr 3.6.2+dfsg-23 has caused the Debian Bug report #982001, regarding lucene-solr: FTBFS with OpenJDK 17 due to rmic removal to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lucene-solr Severity: important Tags: ftbfs sid bookworm User: debian-j...@lists.debian.org Usertags: default-java17 lucene-solr fails to build with OpenJDK 17 due to the removal of rmic: common.compile-core: [mkdir] Created dir: /<>/lucene/build/contrib/remote/classes/java [javac] Compiling 3 source files to /<>/lucene/build/contrib/remote/classes/java [javac] warning: [options] bootstrap class path not set in conjunction with -source 7 [javac] warning: [options] source value 7 is obsolete and will be removed in a future release [javac] warning: [options] target value 7 is obsolete and will be removed in a future release [javac] warning: [options] To suppress warnings about obsolete options, use -Xlint:-options. [javac] Note: /<>/lucene/contrib/remote/src/java/org/apache/lucene/search/RemoteSearchable.java uses or overrides a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] 4 warnings compile-core: [rmic] RMI Compiling 1 class to /<>/lucene/build/contrib/remote/classes/java BUILD FAILED /<>/lucene/build.xml:580: The following error occurred while executing this line: /<>/lucene/common-build.xml:1051: The following error occurred while executing this line: /<>/lucene/contrib/contrib-build.xml:58: The following error occurred while executing this line: /<>/lucene/contrib/remote/build.xml:30: rmic does not exist under Java 15 and higher, use rmic of an older JDK and explicitly set the executable attribute --- End Message --- --- Begin Message --- Source: lucene-solr Source-Version: 3.6.2+dfsg-23 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of lucene-solr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated lucene-solr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 17:02:39 +0100 Source: lucene-solr Architecture: source Version: 3.6.2+dfsg-23 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Closes: 581435 800983 840827 842402 842706 931845 956464 982001 Changes: lucene-solr (3.6.2+dfsg-23) unstable; urgency=medium . * Declare compliance with Debian Policy 4.5.1. * Switch to debhelper-compat = 13. * Drop solr-tomcat, solr-jetty, solr-common and libsolr-java. The version of solr in Debian is outdated and newer versions are not viable to maintain. An alternative version packaged with jdeb or similar tools may be available via the contrib repository in the future. (Closes: #982001, #581435, #800983, #840827, #842402, #842706, #931845, #956464) Checksums-Sha1: 95ec9f0a86beed2bce88891468fe89edd284bcc9 3040 lucene-solr_3.6.2+dfsg-23.dsc 90ee1c073378076196de54c3290394bd7a74b618 50264 lucene-solr_3.6.2+dfsg-23.debian.tar.xz bcdd41af247e7668d8951c157e9ee638031b9439 11440 lucene-solr_3.6.2+dfsg-23_amd64.buildinfo Checksums-Sha256: 22057ff4932abbc51210a5d86a270f86c2345073b7006ff93aac024a32689bd2 3040 lucene-solr_3.6.2+dfsg-23.dsc 408e0a16b43195c76c6731f0583e2509fc0a87d19389fb01d6b19101ae5d7998 50264 lucene-solr_3.6.2+dfsg-23.debian.tar.xz 4231f4bc4da1c27e234161347910547278fd6bb632e5a48196e544b195f0aef2 11440 lucene-solr_3.6.2+dfsg-23_amd64.buildinfo Files: bbbaa2087b15e2f67c42de1962c82208 3040 java optional lucene-solr_3.6.2+dfsg-23.dsc c2dfa2c977add05a9762cae15fd1bc5d 50264 java optional lucene-solr_3.6.2+dfsg-23.debian.tar.xz 6eb48317778fcbdd08ad6fc58bf363dc 11440 java optional
Bug#931845: marked as done (Cannot install solr-tomcat when building docker image)
Your message dated Mon, 22 Feb 2021 16:33:42 + with message-id and subject line Bug#931845: fixed in lucene-solr 3.6.2+dfsg-23 has caused the Debian Bug report #931845, regarding Cannot install solr-tomcat when building docker image to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 931845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: solr-tomcat Version: 3.6.2+dfsg-20 I am building docker image with solr-tomcat inside using Debian Buster. When installing solr-tomcat in Dockerfile, installation fails because Setting up solr-tomcat (3.6.2+dfsg-20) ... System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down dpkg: error processing package solr-tomcat (--configure): installed solr-tomcat package post-installation script subprocess returned error exit status 1 It's not possible to have systemd available during docker build, especially as PID 1. Kind regards, Aki Tuomi --- End Message --- --- Begin Message --- Source: lucene-solr Source-Version: 3.6.2+dfsg-23 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of lucene-solr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 931...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated lucene-solr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 17:02:39 +0100 Source: lucene-solr Architecture: source Version: 3.6.2+dfsg-23 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Closes: 581435 800983 840827 842402 842706 931845 956464 982001 Changes: lucene-solr (3.6.2+dfsg-23) unstable; urgency=medium . * Declare compliance with Debian Policy 4.5.1. * Switch to debhelper-compat = 13. * Drop solr-tomcat, solr-jetty, solr-common and libsolr-java. The version of solr in Debian is outdated and newer versions are not viable to maintain. An alternative version packaged with jdeb or similar tools may be available via the contrib repository in the future. (Closes: #982001, #581435, #800983, #840827, #842402, #842706, #931845, #956464) Checksums-Sha1: 95ec9f0a86beed2bce88891468fe89edd284bcc9 3040 lucene-solr_3.6.2+dfsg-23.dsc 90ee1c073378076196de54c3290394bd7a74b618 50264 lucene-solr_3.6.2+dfsg-23.debian.tar.xz bcdd41af247e7668d8951c157e9ee638031b9439 11440 lucene-solr_3.6.2+dfsg-23_amd64.buildinfo Checksums-Sha256: 22057ff4932abbc51210a5d86a270f86c2345073b7006ff93aac024a32689bd2 3040 lucene-solr_3.6.2+dfsg-23.dsc 408e0a16b43195c76c6731f0583e2509fc0a87d19389fb01d6b19101ae5d7998 50264 lucene-solr_3.6.2+dfsg-23.debian.tar.xz 4231f4bc4da1c27e234161347910547278fd6bb632e5a48196e544b195f0aef2 11440 lucene-solr_3.6.2+dfsg-23_amd64.buildinfo Files: bbbaa2087b15e2f67c42de1962c82208 3040 java optional lucene-solr_3.6.2+dfsg-23.dsc c2dfa2c977add05a9762cae15fd1bc5d 50264 java optional lucene-solr_3.6.2+dfsg-23.debian.tar.xz 6eb48317778fcbdd08ad6fc58bf363dc 11440 java optional lucene-solr_3.6.2+dfsg-23_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmAz2XNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HknSAQAMprnXkNbVMVAbGa5erciWplapEnY6IQUz7l VzNhGMGnsyPH7KzPAjFIoL7W7N/obO+UItVLmFvS+dFeeky23dJHS5h8INJWA2qw k/FQrdsd0EPJsFcMX1pInlIE0VVvohVz5tVdw2zuUKcTDJ97HFIwg/ZHtsARe791 0WQhZSbVuYHAlGF1AIjAIWrBFZpyfVIFB0ovlW3bq3rPQnhKHrllpl/NR5ju9IZ2 ZhMLv9Pm+Wud4SJCEWIiawNoT+/2wJH+fU2J/WJOB2BcvkOIVIt4XT5UtLPqq4aQ ClbAWq0WUsbxbyLng8ffQf+uvMESxrz64dFyVpaazhrUCLhmcSoQumZue8zT+JOS PMgCH3wduYwMn58ODdT8xAl+G6dA+y1EK/wrLVfuUA9LtCm665nQg+yv2HI+M6UO pQrnVEsy1NZKoWm3kd7NU4pQ3ncNbUACPSzetJWx0BroaQ0eFuLxtuq/BU2KBAhG TmSN0YyGYFuSZpTNbC7L6Mh8EyJWYqusWXKV24S2Ayo/3RGl1SvN4ppKUCsho+a1 ajsRMxSuPkzt1Phg8JZRq0gVtuZmRZPLy0NyGP0BkhkEqwXXsatjOtr8GdqAwztF /G8J3gGK0TmC4FISnYpIfRFIoifN0vBc/L2BBv7TpVJjZZJa4+a2GYdOeZduCJIM
Bug#956464: marked as done (solr-tomcat: Unable to perform replication as slave)
Your message dated Mon, 22 Feb 2021 16:33:42 + with message-id and subject line Bug#956464: fixed in lucene-solr 3.6.2+dfsg-23 has caused the Debian Bug report #956464, regarding solr-tomcat: Unable to perform replication as slave to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 956464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: solr-tomcat Version: 3.6.2+dfsg-20+deb10u1 Severity: normal Dear Maintainer, Solr running under Tomcat is unable to perform replication as a slave. This is because during replication it tries to create a temporary directory within its configuration directory (normally /etc/solr/conf, but could also be others if running multiple cores). The problem is the same as that fixed in #919638, which is that even if write permissions are temporarily given to that directory (as I have done on previous systems) the sandbox still does not allow write access. This is made worse by the poor error message that solr gives (not specifying the error or full path). A day of debugging and rebuilding the application was required to work out the cause! I fixed the problem by adding the path to solr-permissions.conf as below. -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages solr-tomcat depends on: ii solr-common 3.6.2+dfsg-20+deb10u1 ii tomcat9 9.0.16-4 solr-tomcat recommends no packages. solr-tomcat suggests no packages. -- Configuration Files: /etc/systemd/system/tomcat9.service.d/solr-permissions.conf changed: [Service] ReadWritePaths=/var/lib/solr/ ReadWritePaths=/etc/solr -- no debconf information --- End Message --- --- Begin Message --- Source: lucene-solr Source-Version: 3.6.2+dfsg-23 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of lucene-solr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated lucene-solr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 17:02:39 +0100 Source: lucene-solr Architecture: source Version: 3.6.2+dfsg-23 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Closes: 581435 800983 840827 842402 842706 931845 956464 982001 Changes: lucene-solr (3.6.2+dfsg-23) unstable; urgency=medium . * Declare compliance with Debian Policy 4.5.1. * Switch to debhelper-compat = 13. * Drop solr-tomcat, solr-jetty, solr-common and libsolr-java. The version of solr in Debian is outdated and newer versions are not viable to maintain. An alternative version packaged with jdeb or similar tools may be available via the contrib repository in the future. (Closes: #982001, #581435, #800983, #840827, #842402, #842706, #931845, #956464) Checksums-Sha1: 95ec9f0a86beed2bce88891468fe89edd284bcc9 3040 lucene-solr_3.6.2+dfsg-23.dsc 90ee1c073378076196de54c3290394bd7a74b618 50264 lucene-solr_3.6.2+dfsg-23.debian.tar.xz bcdd41af247e7668d8951c157e9ee638031b9439 11440 lucene-solr_3.6.2+dfsg-23_amd64.buildinfo Checksums-Sha256: 22057ff4932abbc51210a5d86a270f86c2345073b7006ff93aac024a32689bd2 3040 lucene-solr_3.6.2+dfsg-23.dsc 408e0a16b43195c76c6731f0583e2509fc0a87d19389fb01d6b19101ae5d7998 50264 lucene-solr_3.6.2+dfsg-23.debian.tar.xz 4231f4bc4da1c27e234161347910547278fd6bb632e5a48196e544b195f0aef2 11440 lucene-solr_3.6.2+dfsg-23_amd64.buildinfo Files: bbbaa2087b15e2f67c42de1962c82208 3040 java optional lucene-solr_3.6.2+dfsg-23.dsc c2dfa2c977add05a9762cae15fd1bc5d 50264 java optional lucene-solr_3.6.2+dfsg-23.debian.tar.xz 6eb48317778fcbdd08ad6fc58bf363dc 11440 java optional
Bug#842706: marked as done (solr-jetty: packaged version is ancient)
Your message dated Mon, 22 Feb 2021 16:33:42 + with message-id and subject line Bug#842706: fixed in lucene-solr 3.6.2+dfsg-23 has caused the Debian Bug report #842706, regarding solr-jetty: packaged version is ancient to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 842706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: solr-jetty Version: 3.6.2+dfsg-9 Severity: normal Dear Maintainer, The package version of Solr is 3.6.2, released in December 2012. The current Solr release is 6.2.1, release in September 2016. Are there any plans to upgrade the package? Thanks! -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: lucene-solr Source-Version: 3.6.2+dfsg-23 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of lucene-solr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 842...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated lucene-solr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 17:02:39 +0100 Source: lucene-solr Architecture: source Version: 3.6.2+dfsg-23 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Closes: 581435 800983 840827 842402 842706 931845 956464 982001 Changes: lucene-solr (3.6.2+dfsg-23) unstable; urgency=medium . * Declare compliance with Debian Policy 4.5.1. * Switch to debhelper-compat = 13. * Drop solr-tomcat, solr-jetty, solr-common and libsolr-java. The version of solr in Debian is outdated and newer versions are not viable to maintain. An alternative version packaged with jdeb or similar tools may be available via the contrib repository in the future. (Closes: #982001, #581435, #800983, #840827, #842402, #842706, #931845, #956464) Checksums-Sha1: 95ec9f0a86beed2bce88891468fe89edd284bcc9 3040 lucene-solr_3.6.2+dfsg-23.dsc 90ee1c073378076196de54c3290394bd7a74b618 50264 lucene-solr_3.6.2+dfsg-23.debian.tar.xz bcdd41af247e7668d8951c157e9ee638031b9439 11440 lucene-solr_3.6.2+dfsg-23_amd64.buildinfo Checksums-Sha256: 22057ff4932abbc51210a5d86a270f86c2345073b7006ff93aac024a32689bd2 3040 lucene-solr_3.6.2+dfsg-23.dsc 408e0a16b43195c76c6731f0583e2509fc0a87d19389fb01d6b19101ae5d7998 50264 lucene-solr_3.6.2+dfsg-23.debian.tar.xz 4231f4bc4da1c27e234161347910547278fd6bb632e5a48196e544b195f0aef2 11440 lucene-solr_3.6.2+dfsg-23_amd64.buildinfo Files: bbbaa2087b15e2f67c42de1962c82208 3040 java optional lucene-solr_3.6.2+dfsg-23.dsc c2dfa2c977add05a9762cae15fd1bc5d 50264 java optional lucene-solr_3.6.2+dfsg-23.debian.tar.xz 6eb48317778fcbdd08ad6fc58bf363dc 11440 java optional lucene-solr_3.6.2+dfsg-23_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmAz2XNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HknSAQAMprnXkNbVMVAbGa5erciWplapEnY6IQUz7l VzNhGMGnsyPH7KzPAjFIoL7W7N/obO+UItVLmFvS+dFeeky23dJHS5h8INJWA2qw k/FQrdsd0EPJsFcMX1pInlIE0VVvohVz5tVdw2zuUKcTDJ97HFIwg/ZHtsARe791 0WQhZSbVuYHAlGF1AIjAIWrBFZpyfVIFB0ovlW3bq3rPQnhKHrllpl/NR5ju9IZ2 ZhMLv9Pm+Wud4SJCEWIiawNoT+/2wJH+fU2J/WJOB2BcvkOIVIt4XT5UtLPqq4aQ ClbAWq0WUsbxbyLng8ffQf+uvMESxrz64dFyVpaazhrUCLhmcSoQumZue8zT+JOS PMgCH3wduYwMn58ODdT8xAl+G6dA+y1EK/wrLVfuUA9LtCm665nQg+yv2HI+M6UO pQrnVEsy1NZKoWm3kd7NU4pQ3ncNbUACPSzetJWx0BroaQ0eFuLxtuq/BU2KBAhG TmSN0YyGYFuSZpTNbC7L6Mh8EyJWYqusWXKV24S2Ayo/3RGl1SvN4ppKUCsho+a1 ajsRMxSuPkzt1Phg8JZRq0gVtuZmRZPLy0NyGP0BkhkEqwXXsatjOtr8GdqAwztF /G8J3gGK0TmC4FISnYpIfRFIoifN0vBc/L2BBv7TpVJjZZJa4+a2GYdOeZduCJIM
Bug#840827: marked as done (lucene-solr: Network tests are performed using public IP instead of 127.0.0.1)
Your message dated Mon, 22 Feb 2021 16:33:42 + with message-id and subject line Bug#840827: fixed in lucene-solr 3.6.2+dfsg-23 has caused the Debian Bug report #840827, regarding lucene-solr: Network tests are performed using public IP instead of 127.0.0.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 840827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lucene-solr Version: 3.6.2+dfsg-8 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed: [...] debian/rules build-indep dh build-indep --with maven_repo_helper dh_testdir -i dh_update_autotools_config -i debian/rules override_dh_auto_configure make[1]: Entering directory '/<>/lucene-solr-3.6.2+dfsg' # Link in jars from /usr/share/java rather # than patching the build process for pkg in `cat debian/build-jars`; \ do \ ln -sf `echo $pkg | cut -d : -f 1` `echo $pkg | cut -d : -f 2`; \ done ln: failed to create symbolic link './lucene/lib/ant.jar': No such file or directory [... snipped ...] [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:535) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1182) [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1033) [junit] Caused by: java.net.NoRouteToHostException: No route to host [junit] at java.net.PlainSocketImpl.socketConnect(Native Method) [junit] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) [junit] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) [junit] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) [junit] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) [junit] at java.net.Socket.connect(Socket.java:589) [junit] at java.net.Socket.connect(Socket.java:538) [junit] at java.net.Socket.(Socket.java:434) [junit] at java.net.Socket.(Socket.java:211) [junit] at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40) [junit] at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148) [junit] at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613) [junit] ... 44 more [junit] [junit] [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 5.301 sec [junit] [junit] - Standard Error - [junit] NOTE: reproduce with: ant test -Dtestcase=TestRemoteCachingWrapperFilter -Dtestmethod=testTermRemoteFilter -Dtests.seed=360d91d04c9e1cb5:-d1bf13dc331d343:-5a995359e653cf8b -Dargs="-Dfile.encoding=ANSI_X3.4-1968" [junit] NOTE: reproduce with: ant test -Dtestcase=TestRemoteCachingWrapperFilter -Dtestmethod=testTermRemoteFilter -Dtests.seed=360d91d04c9e1cb5:-d1bf13dc331d343:-5a995359e653cf8b -Dargs="-Dfile.encoding=ANSI_X3.4-1968" [junit] NOTE: test params are: locale=it, timezone=Pacific/Enderbury [junit] NOTE: all tests run in this JVM: [junit] [TestRemoteCachingWrapperFilter] [junit] NOTE: Linux 4.7.0-1-amd64 amd64/Oracle Corporation 1.8.0_102 (64-bit)/cpus=1,threads=1,free=86734984,total=95354880 [junit] - --- [junit] Test org.apache.lucene.search.TestRemoteCachingWrapperFilter FAILED BUILD FAILED /<>/lucene-solr-3.6.2+dfsg/lucene/build.xml:584: The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:1051: The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/lucene/contrib/contrib-build.xml:61: The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:692: The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed! The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed! The following error occurred while executing this line: /<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed! The following error occurred
Bug#842402: marked as done (error installing)
Your message dated Mon, 22 Feb 2021 16:33:42 + with message-id and subject line Bug#842402: fixed in lucene-solr 3.6.2+dfsg-23 has caused the Debian Bug report #842402, regarding error installing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 842402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: solr-tomcat Version: 3.6.2+dfsg-8 Severity: normal When I try to install solr-tomcat on stretch. I get the following error: Setting up solr-tomcat (3.6.2+dfsg-8) ... chown: invalid user: ‘tomcat7:tomcat7’ dpkg: error processing package solr-tomcat (--configure): subprocess installed post-installation script returned error exit status 1 Setting up libcommons-digester-java (1.8.1-4) ... Errors were encountered while processing: solr-tomcat -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.5.161003 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages solr-tomcat depends on: ii solr-common 3.6.2+dfsg-8 ii tomcat7-user 7.0.72-1 solr-tomcat recommends no packages. solr-tomcat suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: lucene-solr Source-Version: 3.6.2+dfsg-23 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of lucene-solr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 842...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated lucene-solr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 17:02:39 +0100 Source: lucene-solr Architecture: source Version: 3.6.2+dfsg-23 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Closes: 581435 800983 840827 842402 842706 931845 956464 982001 Changes: lucene-solr (3.6.2+dfsg-23) unstable; urgency=medium . * Declare compliance with Debian Policy 4.5.1. * Switch to debhelper-compat = 13. * Drop solr-tomcat, solr-jetty, solr-common and libsolr-java. The version of solr in Debian is outdated and newer versions are not viable to maintain. An alternative version packaged with jdeb or similar tools may be available via the contrib repository in the future. (Closes: #982001, #581435, #800983, #840827, #842402, #842706, #931845, #956464) Checksums-Sha1: 95ec9f0a86beed2bce88891468fe89edd284bcc9 3040 lucene-solr_3.6.2+dfsg-23.dsc 90ee1c073378076196de54c3290394bd7a74b618 50264 lucene-solr_3.6.2+dfsg-23.debian.tar.xz bcdd41af247e7668d8951c157e9ee638031b9439 11440 lucene-solr_3.6.2+dfsg-23_amd64.buildinfo Checksums-Sha256: 22057ff4932abbc51210a5d86a270f86c2345073b7006ff93aac024a32689bd2 3040 lucene-solr_3.6.2+dfsg-23.dsc 408e0a16b43195c76c6731f0583e2509fc0a87d19389fb01d6b19101ae5d7998 50264 lucene-solr_3.6.2+dfsg-23.debian.tar.xz 4231f4bc4da1c27e234161347910547278fd6bb632e5a48196e544b195f0aef2 11440 lucene-solr_3.6.2+dfsg-23_amd64.buildinfo Files: bbbaa2087b15e2f67c42de1962c82208 3040 java optional lucene-solr_3.6.2+dfsg-23.dsc c2dfa2c977add05a9762cae15fd1bc5d 50264 java optional lucene-solr_3.6.2+dfsg-23.debian.tar.xz 6eb48317778fcbdd08ad6fc58bf363dc 11440 java optional lucene-solr_3.6.2+dfsg-23_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmAz2XNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HknSAQAMprnXkNbVMVAbGa5erciWplapEnY6IQUz7l VzNhGMGnsyPH7KzPAjFIoL7W7N/obO+UItVLmFvS+dFeeky23dJHS5h8INJWA2qw k/FQrdsd0EPJsFcMX1pInlIE0VVvohVz5tVdw2zuUKcTDJ97HFIwg/ZHtsARe791 0WQhZSbVuYHAlGF1AIjAIWrBFZpyfVIFB0ovlW3bq3rPQnhKHrllpl/NR5ju9IZ2 ZhMLv9Pm+Wud4SJCEWIiawNoT+/2wJH+fU2J/WJOB2BcvkOIVIt4XT5UtLPqq4aQ
Bug#800983: marked as done (lucene-solr: depends on obsolete libcommons-httpclient-java library)
Your message dated Mon, 22 Feb 2021 16:33:42 + with message-id and subject line Bug#800983: fixed in lucene-solr 3.6.2+dfsg-23 has caused the Debian Bug report #800983, regarding lucene-solr: depends on obsolete libcommons-httpclient-java library to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 800983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lucene-solr Severity: normal User: pkg-java-maintain...@lists.alioth.debian.org Usertags: oldlibs libcommons-httpclient-java Hi, lucene-solr depends on libcommons-httpclient-java, which is obsolete and was replaced by libhttpclient-java. It has reached EOL status in 2011! It is no longer supported upstream [1] and was affected by multiple security issues in the recent past. lucene-solr should be ported to the new libhttpclient-java version, so that we can remove the old, unmaintained one. Please forward this issue upstream, if you can't migrate the package yourself. We would like to see libcommons-httpclient-java removed during the Stretch release cycle but due to the large number of reverse-dependencies the outcome depends more than ever on your help. Please help us to accomplish this goal. We will bump this issue to important when the list of rdeps is getting smaller and we think that the removal is possible. We will eventually raise the severity to serious when the number of rdeps is small. If you have any questions don't hesitate to ask and contact us on debian-j...@list.debian.org Regards, Markus [1] https://hc.apache.org/httpclient-3.x/ [2] https://security-tracker.debian.org/tracker/source-package/commons-httpclient --- End Message --- --- Begin Message --- Source: lucene-solr Source-Version: 3.6.2+dfsg-23 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of lucene-solr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 800...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated lucene-solr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 17:02:39 +0100 Source: lucene-solr Architecture: source Version: 3.6.2+dfsg-23 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Closes: 581435 800983 840827 842402 842706 931845 956464 982001 Changes: lucene-solr (3.6.2+dfsg-23) unstable; urgency=medium . * Declare compliance with Debian Policy 4.5.1. * Switch to debhelper-compat = 13. * Drop solr-tomcat, solr-jetty, solr-common and libsolr-java. The version of solr in Debian is outdated and newer versions are not viable to maintain. An alternative version packaged with jdeb or similar tools may be available via the contrib repository in the future. (Closes: #982001, #581435, #800983, #840827, #842402, #842706, #931845, #956464) Checksums-Sha1: 95ec9f0a86beed2bce88891468fe89edd284bcc9 3040 lucene-solr_3.6.2+dfsg-23.dsc 90ee1c073378076196de54c3290394bd7a74b618 50264 lucene-solr_3.6.2+dfsg-23.debian.tar.xz bcdd41af247e7668d8951c157e9ee638031b9439 11440 lucene-solr_3.6.2+dfsg-23_amd64.buildinfo Checksums-Sha256: 22057ff4932abbc51210a5d86a270f86c2345073b7006ff93aac024a32689bd2 3040 lucene-solr_3.6.2+dfsg-23.dsc 408e0a16b43195c76c6731f0583e2509fc0a87d19389fb01d6b19101ae5d7998 50264 lucene-solr_3.6.2+dfsg-23.debian.tar.xz 4231f4bc4da1c27e234161347910547278fd6bb632e5a48196e544b195f0aef2 11440 lucene-solr_3.6.2+dfsg-23_amd64.buildinfo Files: bbbaa2087b15e2f67c42de1962c82208 3040 java optional lucene-solr_3.6.2+dfsg-23.dsc c2dfa2c977add05a9762cae15fd1bc5d 50264 java optional lucene-solr_3.6.2+dfsg-23.debian.tar.xz 6eb48317778fcbdd08ad6fc58bf363dc 11440 java optional lucene-solr_3.6.2+dfsg-23_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmAz2XNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
Bug#581435: marked as done (500 error when trying to search for highlighted fields.)
Your message dated Mon, 22 Feb 2021 16:33:42 + with message-id and subject line Bug#581435: fixed in lucene-solr 3.6.2+dfsg-23 has caused the Debian Bug report #581435, regarding 500 error when trying to search for highlighted fields. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 581435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581435 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jetty-solr Version: 1.4.0+ds1-2 When I try to search for an exact phrase by typing "exact phrase" with double quotes and enable highlighting and input a highlighted field, I get the following error: I have downloaded and tested it using the standalone version of solr and jetty and it works correctly there. Please fix this ASAP. ERROR DETAILS - HTTP ERROR 500 Problem accessing /solr/select. Reason: org/apache/lucene/index/memory/MemoryIndex java.lang.NoClassDefFoundError: org/apache/lucene/index/memory/MemoryIndex at org.apache.lucene.search.highlight.WeightedSpanTermExtractor.getReaderForField(WeightedSpanTermExtractor.java:361) at org.apache.lucene.search.highlight.WeightedSpanTermExtractor.extractWeightedSpanTerms(WeightedSpanTermExtractor.java:282) at org.apache.lucene.search.highlight.WeightedSpanTermExtractor.extract(WeightedSpanTermExtractor.java:149) at org.apache.lucene.search.highlight.WeightedSpanTermExtractor.getWeightedSpanTerms(WeightedSpanTermExtractor.java:414) at org.apache.lucene.search.highlight.QueryScorer.initExtractor(QueryScorer.java:216) at org.apache.lucene.search.highlight.QueryScorer.init(QueryScorer.java:184) at org.apache.lucene.search.highlight.Highlighter.getBestTextFragments(Highlighter.java:226) at org.apache.solr.highlight.DefaultSolrHighlighter.doHighlighting(DefaultSolrHighlighter.java:335) at org.apache.solr.handler.component.HighlightComponent.process(HighlightComponent.java:89) at org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:195) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:131) at org.apache.solr.core.SolrCore.execute(SolrCore.java:1317) at org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:338) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:241) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) I am using Debian GNU/Linux 5.0 --- End Message --- --- Begin Message --- Source: lucene-solr Source-Version: 3.6.2+dfsg-23 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of lucene-solr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 581...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated lucene-solr package) (This message
Bug#983295: marked as done (libpam-modules: pam_mkhomedir is disabled for noninteractive sessions (e.g. samba))
Your message dated Mon, 22 Feb 2021 16:03:30 +0100 with message-id <20210222160330.3caa9...@erker.lan> and subject line Re: Bug#983295: libpam-modules: pam_mkhomedir is disabled for noninteractive sessions (e.g. samba) has caused the Debian Bug report #983295, regarding libpam-modules: pam_mkhomedir is disabled for noninteractive sessions (e.g. samba) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpam-modules Version: 1.4.0-4 Severity: normal Dear Maintainer, = Description of the use-case = I am using pam_mkhomedir on a file server (samba). Users are managed via LDAP (configured in smbd). The home directories of users are supposed to be created, as soon as the user accesses the corresponding personal share via samba. This works well, if `pam_mkhomedir` is enabled in "common-session" and "common-session-noninteractive". Additionally "obey pam restrictions = yes" needs to be specified in /etc/samba/smbd.conf. = Description of the issue = In theory, this works well together with the configuration distributed in the pam package. But one missing piece is missing, since /usr/share/pam-configs/mkhomedir contains the following line: Session-Interactive-Only: yes I am not sure, whether this line is necessary. For my specific use-case I need to remove this line in order to allow users to create their home directory via samba (non-interactively). # Description of local workarounds = In order to prevent my local modification from being overridden during package upgrades, I decided to create an adjusted copy of /usr/share/pam-configs/mkhomedir in that directory. Now I can select this custom module via "pam-auth-update" (and disable the original "mkhomedir"). This approach is obviously not good, since I changed the content of /usr/share/pam-configs (instead of some file below /etc). An alternative approach would be to change /etc/pam.d/common-session-noninteractive and tell "pam-auth-update" to stop managing the files below /etc/pam.d/. This is obviously not desirable. I am inclined to think, that enabling "mkhomedir" for non-interactive sessions as part of the "mkhomedir" configuration shipped by the pam package would not hurt its users. But maybe I am overlooking something ovious? Thank you for your time! Cheers, Lars --- End Message --- --- Begin Message --- Hello Sam, Am Mon, 22 Feb 2021 00:46:16 -0500 schrieb Sam Hartman : > It might tend to create home directories on mail servers and web servers > in cases where they are really not wanted. This is a very good point. In this case it seems like a change would not be desirable, thus I am closing this bug report. > In your case I'd either modify /etc/pam.d/common-session-noninteractive or > /etc/pam.d/samba. Creating a new separate profile you install in > /usr/share/pam-configs also seems reasonable. Ah - I was not aware of /etc/pam.d/samba. This sounds like the proper approach for solving the issue for my use case. Thank you for your thoughts! Cheers, Lars--- End Message ---
Bug#619101: marked as done (sudo: warning on apt-get dist-upgrade using sudo)
Your message dated Mon, 22 Feb 2021 16:09:47 +0100 with message-id and subject line Re: Bug#619101: sudo: warning on apt-get dist-upgrade using sudo has caused the Debian Bug report #619101, regarding sudo: warning on apt-get dist-upgrade using sudo to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 619101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sudo Version: 1.7.4p4-2.squeeze.2 Priority: minor Tags: I'm not sure if this is a bug, I just noticed this when upgrading today: $ sudo apt-get dist-upgrade ... Setting up sudo (1.7.4p4-2.squeeze.2) ... mv: cannot move `/var/run/sudo/username' to `/var/lib/sudo/username': Directory not empty rmdir: failed to remove `/var/run/sudo': Directory not empty Maybe the sudo upgrade script doesn't count on being run under sudo and that's why it fails to move the directory. Regards, ~~helix84 --- End Message --- --- Begin Message --- Version: 1.8.21-1 On Mon, Mar 21, 2011 at 10:33:23AM +0100, helix84 wrote: > Maybe the sudo upgrade script doesn't count on being run under sudo > and that's why it fails to move the directory. This looks to me like a valid conclusion. I apologize for having this issue unreplied for almost a decade. The code in question has been removed in 2017. Closing the bug. Greetings Marc--- End Message ---
Bug#965699: marked as done (libxml-java: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Mon, 22 Feb 2021 15:04:22 + with message-id and subject line Bug#965699: fixed in libxml-java 1.1.7-1 has caused the Debian Bug report #965699, regarding libxml-java: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 965699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libxml-java Version: 1.1.6.dfsg-3 Severity: normal Usertags: compat-5-6-removal Hi, The package libxml-java uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: libxml-java Source-Version: 1.1.7-1 Done: Emmanuel Bourg We believe that the bug you reported is fixed in the latest version of libxml-java, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated libxml-java package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 15:40:27 +0100 Source: libxml-java Architecture: source Version: 1.1.7-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 965699 Changes: libxml-java (1.1.7-1) unstable; urgency=medium . * Team upload. * New upstream release * Build with the DH sequencer instead of CDBS * Converted debian/copyright to the Copyright Format 1.0 * Added a watch file * Standards-Version updated to 4.5.1 * Switch to debhelper level 13 (Closes: #965699) * Use salsa.debian.org Vcs-* URLs * Added the Homepage field Checksums-Sha1: 4f69aa602d18ed99db5d58eb7f327930a089556e 2155 libxml-java_1.1.7-1.dsc 3678f21a5a3a7ded3354953524ae87768c6ad290 61020 libxml-java_1.1.7.orig.tar.xz 7cb8d9c2a2462de6045f2d2cc07d0b7eb30d5312 2472 libxml-java_1.1.7-1.debian.tar.xz 04938f9039ca742c2aa301b9c7f5d0d695c6439a 12727 libxml-java_1.1.7-1_source.buildinfo Checksums-Sha256: af4bb67c90a4e0cbaf6dd9af89844a6191abf81de4cc7ecad6a969ca2bda7047 2155 libxml-java_1.1.7-1.dsc 0b5447c7263d011f9affafd02a663fbafc7695b3f4bc0ae7cb22003052619b82 61020 libxml-java_1.1.7.orig.tar.xz 5dbd1fb824718f4e5e37ef9625ec145e67e05e02fef261f0cd2190d77e1fe069 2472 libxml-java_1.1.7-1.debian.tar.xz 14cf58e210f43d2b0c80d623220fc3445ae8ac43d6321ebf4f224799ab161ab4 12727 libxml-java_1.1.7-1_source.buildinfo Files: 7350f8700cbb6f6ceb7e5b0cbf411697 2155 java optional libxml-java_1.1.7-1.dsc 31b50d02c8d31dc7b66e92ee7018b717 61020 java optional libxml-java_1.1.7.orig.tar.xz bbf1aad969ae55e8277dca65e16e0806 2472 java optional libxml-java_1.1.7-1.debian.tar.xz 7fb43a97f44cd1b4ddce1e663987352f 12727 java optional libxml-java_1.1.7-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmAzwqoSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCsAj4P/0+U+8cnSvnr61sYYDPSB007HUQH0uqW Ac4UHByI94CnvnNobLXChJabIV1hp0JD7Ps9Sv2JbARZZWUtN1tBXEMNjaYvyPQH /A44wucD7Afct6qHIvRGjC3fkZZ5BA6+XFpoEzNx0i62qJ7k2ufiyZOFI7o6ltgF 0Bopn9w3XVx7VBNq5927Ptzt7L3P0StZ3LzSJc9KcZsk6D7mSWkJZGbg4d0PmIRw
Bug#982955: marked as done (greenbone-security-assistant.service: Start request repeated too quickly.)
Your message dated Mon, 22 Feb 2021 15:04:15 + with message-id and subject line Bug#982955: fixed in greenbone-security-assistant 20.8.0-2 has caused the Debian Bug report #982955, regarding greenbone-security-assistant.service: Start request repeated too quickly. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 982955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: greenbone-security-assistant Version: 20.8.0-1 Severity: important Dear Maintainer, greenbone-security-assistant.service fails with "Start request repeated too quickly." if gvmd.service takes to long to create /run/gvm/ (RuntimeDirectory=gvm). gsad requires the directory to exist for its PID file. Adding After=gvmd.service resolves the issue. *** gsad.log gsad main:MESSAGE:2021-02-17 09h28.17 utc:435: Starting GSAD version 20.08.0~git gsad main:CRITICAL:2021-02-17 09h28.17 utc:484: main: Could not write PID file. gsad main:CRITICAL:2021-02-17 09h28.17 utc:485: main: Could not write PID file. gsad main:MESSAGE:2021-02-17 09h28.18 utc:487: Starting GSAD version 20.08.0~git gsad main:CRITICAL:2021-02-17 09h28.18 utc:488: main: Could not write PID file. gsad main:CRITICAL:2021-02-17 09h28.18 utc:489: main: Could not write PID file. gsad main:MESSAGE:2021-02-17 09h28.18 utc:497: Starting GSAD version 20.08.0~git gsad main:CRITICAL:2021-02-17 09h28.18 utc:498: main: Could not write PID file. gsad main:CRITICAL:2021-02-17 09h28.18 utc:499: main: Could not write PID file. gsad main:MESSAGE:2021-02-17 09h28.18 utc:501: Starting GSAD version 20.08.0~git gsad main:CRITICAL:2021-02-17 09h28.18 utc:502: main: Could not write PID file. gsad main:CRITICAL:2021-02-17 09h28.18 utc:503: main: Could not write PID file. gsad main:MESSAGE:2021-02-17 09h28.19 utc:505: Starting GSAD version 20.08.0~git gsad main:CRITICAL:2021-02-17 09h28.19 utc:506: main: Could not write PID file. gsad main:CRITICAL:2021-02-17 09h28.19 utc:507: main: Could not write PID file. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-cloud-amd64 (SMP w/8 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages greenbone-security-assistant depends on: ii greenbone-security-assistant-common 20.8.0-1 ii gvmd 20.8.0+git2020-2 ii libc62.31-9 ii libgcrypt20 1.8.7-2 ii libglib2.0-0 2.66.7-1 ii libgnutls30 3.7.0-5 ii libgvm20 20.8.0-2 ii libmicrohttpd12 0.9.71-1 ii libxml2 2.9.10+dfsg-6.3+b1 ii lsb-base 11.1.0 greenbone-security-assistant recommends no packages. greenbone-security-assistant suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: greenbone-security-assistant Source-Version: 20.8.0-2 Done: Raphaël Hertzog We believe that the bug you reported is fixed in the latest version of greenbone-security-assistant, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphaël Hertzog (supplier of updated greenbone-security-assistant package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 15:45:39 +0100 Source: greenbone-security-assistant Architecture: source Version: 20.8.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Raphaël Hertzog Closes: 982955 Changes: greenbone-security-assistant (20.8.0-2) unstable; urgency=medium . * Team upload. . [ Sophie Brun ] * Fix debian/copyright: some files are GPL-2+ * Fix greenbone-security-assistant.service (Closes: #982955) Checksums-Sha1: 3f4099449b4aa9b64cc40aa99199da06b496bfb0 2147
Bug#953599: marked as done (aspell-cs: Mismatched source format vs source version)
Your message dated Mon, 22 Feb 2021 15:03:34 +
with message-id
and subject line Bug#953599: fixed in aspell-cs 0.51.0-1.2
has caused the Debian Bug report #953599,
regarding aspell-cs: Mismatched source format vs source version
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
953599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aspell-cs
Version: 0.51.0-1
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing and subverts the semantics of both the
source and version formats.
This currently produces a lintian error, and with dpkg-dev 1.20.1 it
will start producing warnings, but my intention is to eventually make
it error out.
Please, either use a non-native source format, or a native version,
so that these are coherent.
It would appear as if this was built with a missing orig tarball so
the 1.0 format "support" considered it a native format. Rebuilding
with the correct orig should fix this I guess.
Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: aspell-cs
Source-Version: 0.51.0-1.2
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
aspell-cs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 953...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated aspell-cs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 22 Feb 2021 15:45:32 +0100
Source: aspell-cs
Architecture: source
Version: 0.51.0-1.2
Distribution: unstable
Urgency: medium
Maintainer: Miroslav Kure
Changed-By: Andreas Beckmann
Closes: 638425 736856 953599
Changes:
aspell-cs (0.51.0-1.2) unstable; urgency=medium
.
[ Andreas Beckmann ]
* Non-maintainer upload.
* Bump debhelper dependency to 9 to match compat level. (Closes: #736856)
* Whitespace cleanup.
* Add watch file.
* Recover .orig tarball, this is not a native package.
.
[ Baptiste Beauplat ]
* Leave rws and compat file generation to aspell-autobuildhash
(Closes: #638425):
- Bump dictionaries-common-dev version to 1.23 in Build-Depends, required
to automatically create symlinks and clean files
- Replace aspell and dictionaries-common Depends by ${aspell:Depends}
- Drop .rws and .compat files and links from the package, now generated
at installation time, by aspell-autobuildhash trigger
- Add Auto-Compat field in info-aspell to trigger .compat file
generation
* Convert package format to 3.0 (quilt) (Closes: #953599)
Checksums-Sha1:
0f54d863370518c281b9cab83896dc5c1541039e 1793 aspell-cs_0.51.0-1.2.dsc
fe4a85d87366fbfb840e915e71ca2cc0589e8117 626618 aspell-cs_0.51.0.orig.tar.bz2
13d8297f6e1cec93a3baecad1d1afecd257ad9c5 2876
aspell-cs_0.51.0-1.2.debian.tar.xz
8dde1ca6265156bca938b1833ba05a4aa360820f 5622
aspell-cs_0.51.0-1.2_source.buildinfo
Checksums-Sha256:
19bdde3795f058c5ad022d38f9d22319d50654d52a540f2eb240309d00096d6a 1793
aspell-cs_0.51.0-1.2.dsc
7c56c5cd6e74d60749e68effa9dc45cb282cb3bb6a9c56b51f7594a72216ea47 626618
aspell-cs_0.51.0.orig.tar.bz2
df72336ab3c41fcdf856e459e15175949349cd1d49498c04bdef5fb9b3ab709f 2876
aspell-cs_0.51.0-1.2.debian.tar.xz
a68fdb67ec198fe0349321286d22f5575b78b0ebb00dd2caeedf445a66d1b1f5 5622
aspell-cs_0.51.0-1.2_source.buildinfo
Files:
70dc38335536a6b1785cec6b761a1c08 1793 text optional aspell-cs_0.51.0-1.2.dsc
4be28bef4385ef46e80547ce8cdc4535 626618 text optional
aspell-cs_0.51.0.orig.tar.bz2
e8b0cbaec2ad249a93849e9246d9224b 2876 text optional
aspell-cs_0.51.0-1.2.debian.tar.xz
87543d1df6e66b0a1d07a2bcee1247ac 5622 text optional
aspell-cs_0.51.0-1.2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmAzw+QQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCJPWD/4rRJIkcL82MftF8A14derYh1isFO8r03b1
QZ8w/pZr0qJHBI3ZBQZSXOD3YIqWTzwD3G+3CxT7dZR8zmBHCUtpKwrLNbfNpywE
Bug#736856: marked as done (aspell-cs: d/compat=9 but B-D only on debhelper>4)
Your message dated Mon, 22 Feb 2021 15:03:33 +
with message-id
and subject line Bug#736856: fixed in aspell-cs 0.51.0-1.2
has caused the Debian Bug report #736856,
regarding aspell-cs: d/compat=9 but B-D only on debhelper>4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
736856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aspell-cs
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
d/compat says 9
d/control says B-D debhelper >= 4.0
I think the later needs to be also >= 9...
- -- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCAAGBQJS5quXAAoJEJFk+h0XvV02clUP/A9es37DyumJOdko20cZv2o5
YGMWK/H0JLXX7YSssXNjAaCbF63ogXXc5HN2mTZ119HJvEqJ166odyGZQRyUFec1
hD1l7Nkvtzcbcrub6Nz+E5u3I84lMtj3HkixS47gmhS991oMt6YL5ect/hgwCTMm
aXNql2uYbCsqJ59XbE3LlDWAFmqZ9QL/p62B/tnrmq0iKjbVxg8MBjetIw0c8fYn
kL3BFj65ZBt8TSQ2jRkMRAAjKXk7O8EMoX89em6lb/QRcBy9aov3vuNThwZJIRFo
8Cm5sYbPz4QI+7QPgbYRaXZDgEXYQSE043w79Lxrrwxjmh4+ugMoxj9mKpqdbYN5
yBvvnFhWCDVAMRJH+IFjgrwR4aNIJgNq0ccnY/c2/m+PqZ9l5Y7NRzrKLi+r6+jb
gE/ngaUJImnkmZPZooL3GMhbnNawaapJKf1MSvLnCI5UvXNvexyFzLKtZC4In4oh
jln6UVSqB8k39RdPE3p4kUmOm5oasdhywM+s4tQLMhk6iVBPoLHTFhhigGwy6Mrz
kVu5e5spThsQVkXjfoY2edD0D6G9MhFAOoykoCe4AbWrvjvIoe7M6MABkw9OKP6i
WUeO4zqpeVa85aFWzZIRoAU2NYY8ICwTuc1ML4udq4E79vh26z0U9I8FvlGEDkax
2KjogwJgMxHDBeZONBWH
=XttS
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: aspell-cs
Source-Version: 0.51.0-1.2
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
aspell-cs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 736...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated aspell-cs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 22 Feb 2021 15:45:32 +0100
Source: aspell-cs
Architecture: source
Version: 0.51.0-1.2
Distribution: unstable
Urgency: medium
Maintainer: Miroslav Kure
Changed-By: Andreas Beckmann
Closes: 638425 736856 953599
Changes:
aspell-cs (0.51.0-1.2) unstable; urgency=medium
.
[ Andreas Beckmann ]
* Non-maintainer upload.
* Bump debhelper dependency to 9 to match compat level. (Closes: #736856)
* Whitespace cleanup.
* Add watch file.
* Recover .orig tarball, this is not a native package.
.
[ Baptiste Beauplat ]
* Leave rws and compat file generation to aspell-autobuildhash
(Closes: #638425):
- Bump dictionaries-common-dev version to 1.23 in Build-Depends, required
to automatically create symlinks and clean files
- Replace aspell and dictionaries-common Depends by ${aspell:Depends}
- Drop .rws and .compat files and links from the package, now generated
at installation time, by aspell-autobuildhash trigger
- Add Auto-Compat field in info-aspell to trigger .compat file
generation
* Convert package format to 3.0 (quilt) (Closes: #953599)
Checksums-Sha1:
0f54d863370518c281b9cab83896dc5c1541039e 1793 aspell-cs_0.51.0-1.2.dsc
fe4a85d87366fbfb840e915e71ca2cc0589e8117 626618 aspell-cs_0.51.0.orig.tar.bz2
13d8297f6e1cec93a3baecad1d1afecd257ad9c5 2876
aspell-cs_0.51.0-1.2.debian.tar.xz
8dde1ca6265156bca938b1833ba05a4aa360820f 5622
aspell-cs_0.51.0-1.2_source.buildinfo
Checksums-Sha256:
19bdde3795f058c5ad022d38f9d22319d50654d52a540f2eb240309d00096d6a 1793
aspell-cs_0.51.0-1.2.dsc
7c56c5cd6e74d60749e68effa9dc45cb282cb3bb6a9c56b51f7594a72216ea47 626618
aspell-cs_0.51.0.orig.tar.bz2
df72336ab3c41fcdf856e459e15175949349cd1d49498c04bdef5fb9b3ab709f 2876
aspell-cs_0.51.0-1.2.debian.tar.xz
a68fdb67ec198fe0349321286d22f5575b78b0ebb00dd2caeedf445a66d1b1f5 5622
aspell-cs_0.51.0-1.2_source.buildinfo
Files:
70dc38335536a6b1785cec6b761a1c08 1793 text optional
Bug#638425: marked as done (debsums reports that some aspell-cs files have changed)
Your message dated Mon, 22 Feb 2021 15:03:33 +
with message-id
and subject line Bug#638425: fixed in aspell-cs 0.51.0-1.2
has caused the Debian Bug report #638425,
regarding debsums reports that some aspell-cs files have changed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
638425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aspell-cs
Version: 0.0.20040614.1-2
Severity: normal
Install aspell-cs and immediately run 'debsums -s aspell-cs'. The output is:
debsums: changed file /var/lib/aspell/cs.rws (from aspell-cs package)
debsums: changed file /var/lib/aspell/cs.compat (from aspell-cs package)
This means these files were changed by aspell-cs itself, thus making it impossib
le to check for tampering (or file corruption), and casting doubt on the entire
system for administrators who depend on the output of debsums.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages aspell-cs depends on:
ii aspell 0.60.7~20110707-1 GNU Aspell spell-checker
ii dictionaries-common1.11.5Common utilities for spelling dict
aspell-cs recommends no packages.
aspell-cs suggests no packages.
-- no debconf information
-- debsums errors found:
debsums: changed file /var/lib/aspell/cs.rws (from aspell-cs package)
debsums: changed file /var/lib/aspell/cs.compat (from aspell-cs package)
--- End Message ---
--- Begin Message ---
Source: aspell-cs
Source-Version: 0.51.0-1.2
Done: Andreas Beckmann
We believe that the bug you reported is fixed in the latest version of
aspell-cs, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 638...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated aspell-cs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 22 Feb 2021 15:45:32 +0100
Source: aspell-cs
Architecture: source
Version: 0.51.0-1.2
Distribution: unstable
Urgency: medium
Maintainer: Miroslav Kure
Changed-By: Andreas Beckmann
Closes: 638425 736856 953599
Changes:
aspell-cs (0.51.0-1.2) unstable; urgency=medium
.
[ Andreas Beckmann ]
* Non-maintainer upload.
* Bump debhelper dependency to 9 to match compat level. (Closes: #736856)
* Whitespace cleanup.
* Add watch file.
* Recover .orig tarball, this is not a native package.
.
[ Baptiste Beauplat ]
* Leave rws and compat file generation to aspell-autobuildhash
(Closes: #638425):
- Bump dictionaries-common-dev version to 1.23 in Build-Depends, required
to automatically create symlinks and clean files
- Replace aspell and dictionaries-common Depends by ${aspell:Depends}
- Drop .rws and .compat files and links from the package, now generated
at installation time, by aspell-autobuildhash trigger
- Add Auto-Compat field in info-aspell to trigger .compat file
generation
* Convert package format to 3.0 (quilt) (Closes: #953599)
Checksums-Sha1:
0f54d863370518c281b9cab83896dc5c1541039e 1793 aspell-cs_0.51.0-1.2.dsc
fe4a85d87366fbfb840e915e71ca2cc0589e8117 626618 aspell-cs_0.51.0.orig.tar.bz2
13d8297f6e1cec93a3baecad1d1afecd257ad9c5 2876
aspell-cs_0.51.0-1.2.debian.tar.xz
8dde1ca6265156bca938b1833ba05a4aa360820f 5622
aspell-cs_0.51.0-1.2_source.buildinfo
Checksums-Sha256:
19bdde3795f058c5ad022d38f9d22319d50654d52a540f2eb240309d00096d6a 1793
aspell-cs_0.51.0-1.2.dsc
7c56c5cd6e74d60749e68effa9dc45cb282cb3bb6a9c56b51f7594a72216ea47 626618
aspell-cs_0.51.0.orig.tar.bz2
df72336ab3c41fcdf856e459e15175949349cd1d49498c04bdef5fb9b3ab709f 2876
aspell-cs_0.51.0-1.2.debian.tar.xz
a68fdb67ec198fe0349321286d22f5575b78b0ebb00dd2caeedf445a66d1b1f5 5622
aspell-cs_0.51.0-1.2_source.buildinfo
Files:
70dc38335536a6b1785cec6b761a1c08 1793 text optional aspell-cs_0.51.0-1.2.dsc
Bug#983280: marked as done (cpl-plugin-xshoo: demote sphinx dependency to B-D-I)
Your message dated Mon, 22 Feb 2021 14:22:59 +
with message-id
and subject line Bug#983280: fixed in cpl-plugin-xshoo 3.5.0+dfsg-2
has caused the Debian Bug report #983280,
regarding cpl-plugin-xshoo: demote sphinx dependency to B-D-I
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpl-plugin-xshoo
Version: 3.5.0+dfsg-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
cpl-plugin-xshoo cannot be cross built from source, because its sphinx
dependency is not satisfiable. Since the documentation is already split
to an arch:all package and the documentation is only built during an
arch-only build, all that needs doing is restricting the usage of the
shpinxdoc addon to the indep part. Please consider applying the attached
patch.
Helmut
diff --minimal -Nru cpl-plugin-xshoo-3.5.0+dfsg/debian/changelog
cpl-plugin-xshoo-3.5.0+dfsg/debian/changelog
--- cpl-plugin-xshoo-3.5.0+dfsg/debian/changelog2020-07-01
09:03:17.0 +0200
+++ cpl-plugin-xshoo-3.5.0+dfsg/debian/changelog2021-02-21
22:34:11.0 +0100
@@ -1,3 +1,10 @@
+cpl-plugin-xshoo (3.5.0+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Request sphinxdoc addon via B-D-I. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 21 Feb 2021 22:34:11 +0100
+
cpl-plugin-xshoo (3.5.0+dfsg-1) unstable; urgency=low
* New upstream version 3.5.0+dfsg. Rediff patches
diff --minimal -Nru cpl-plugin-xshoo-3.5.0+dfsg/debian/control
cpl-plugin-xshoo-3.5.0+dfsg/debian/control
--- cpl-plugin-xshoo-3.5.0+dfsg/debian/control 2020-07-01 09:02:38.0
+0200
+++ cpl-plugin-xshoo-3.5.0+dfsg/debian/control 2021-02-21 22:34:09.0
+0100
@@ -9,7 +9,8 @@
python3,
python3-astropy,
python3-cpl,
- python3-sphinx
+Build-Depends-Indep: dh-sequence-sphinxdoc,
+ python3-sphinx
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/debian-astro-team/cpl-plugin-xshoo
Vcs-Git: https://salsa.debian.org/debian-astro-team/cpl-plugin-xshoo.git
diff --minimal -Nru cpl-plugin-xshoo-3.5.0+dfsg/debian/rules
cpl-plugin-xshoo-3.5.0+dfsg/debian/rules
--- cpl-plugin-xshoo-3.5.0+dfsg/debian/rules2020-07-01 09:02:38.0
+0200
+++ cpl-plugin-xshoo-3.5.0+dfsg/debian/rules2021-02-21 22:33:57.0
+0100
@@ -11,7 +11,7 @@
sh ./debian/repackage.sh
%:
- dh $@ --with sphinxdoc
+ dh $@
debian_files:
if [ -d calib/cal ] ; then \
@@ -40,11 +40,6 @@
sphinx-build sphinx sphinx/html
dh_installdocs
-override_dh_sphinxdoc:
- if [ -d sphinx ] ; then \
- dh_sphinxdoc ; \
- fi
-
override_dh_clean:
dh_clean
rm -rf debian/${DEB_SOURCE}.install \
--- End Message ---
--- Begin Message ---
Source: cpl-plugin-xshoo
Source-Version: 3.5.0+dfsg-2
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
cpl-plugin-xshoo, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated cpl-plugin-xshoo
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Feb 2021 14:40:19 +0100
Source: cpl-plugin-xshoo
Architecture: source
Version: 3.5.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers
Changed-By: Ole Streicher
Closes: 983280
Changes:
cpl-plugin-xshoo (3.5.0+dfsg-2) unstable; urgency=medium
.
[ Helmut Grohne ]
* Request sphinxdoc addon via B-D-I (Closes: #983280)
Checksums-Sha1:
fa8d7a9c50970d925d0a0ecc36b1867aa9d501c8 2439 cpl-plugin-xshoo_3.5.0+dfsg-2.dsc
05d07ce6e7e6ab00d2b087b8bbd4d3f56118d872 11216
cpl-plugin-xshoo_3.5.0+dfsg-2.debian.tar.xz
Checksums-Sha256:
5c7e16fcc155157001e04323188741c754a4b2ea7b44f72488a334cf35edce95 2439
cpl-plugin-xshoo_3.5.0+dfsg-2.dsc
30c3cfec53cffd37453c758172ffc4a7b971c66ab9c6f933154eac87a0630c27 11216
Bug#983277: marked as done (cpl-plugin-muse: demote sphinx dependency to B-D-I)
Your message dated Mon, 22 Feb 2021 14:21:22 +
with message-id
and subject line Bug#983277: fixed in cpl-plugin-muse 2.8.3+dfsg-2
has caused the Debian Bug report #983277,
regarding cpl-plugin-muse: demote sphinx dependency to B-D-I
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpl-plugin-muse
Version: 2.8.3+dfsg-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
cpl-plugin-muse cannot be cross built from source, because its sphinx
dependency is not satisfiable. Since the documentation is already split
to an arch:all package and the documentation is only built during an
arch-only build, all that needs doing is restricting the usage of the
shpinxdoc addon to the indep part. Please consider applying the attached
patch.
Helmut
diff --minimal -Nru cpl-plugin-muse-2.8.3+dfsg/debian/changelog
cpl-plugin-muse-2.8.3+dfsg/debian/changelog
--- cpl-plugin-muse-2.8.3+dfsg/debian/changelog 2020-06-29 10:06:35.0
+0200
+++ cpl-plugin-muse-2.8.3+dfsg/debian/changelog 2021-02-21 22:25:23.0
+0100
@@ -1,3 +1,10 @@
+cpl-plugin-muse (2.8.3+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Request sphinxdoc addon via B-D-I. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 21 Feb 2021 22:25:23 +0100
+
cpl-plugin-muse (2.8.3+dfsg-1) unstable; urgency=low
* New upstream version 2.8.3+dfsg
diff --minimal -Nru cpl-plugin-muse-2.8.3+dfsg/debian/control
cpl-plugin-muse-2.8.3+dfsg/debian/control
--- cpl-plugin-muse-2.8.3+dfsg/debian/control 2020-06-29 10:06:35.0
+0200
+++ cpl-plugin-muse-2.8.3+dfsg/debian/control 2021-02-21 22:25:21.0
+0100
@@ -8,7 +8,8 @@
python3,
python3-astropy,
python3-cpl,
- python3-sphinx
+Build-Depends-Indep: dh-sequence-sphinxdoc,
+ python3-sphinx
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/debian-astro-team/cpl-plugin-muse
Vcs-Git: https://salsa.debian.org/debian-astro-team/cpl-plugin-muse.git
diff --minimal -Nru cpl-plugin-muse-2.8.3+dfsg/debian/rules
cpl-plugin-muse-2.8.3+dfsg/debian/rules
--- cpl-plugin-muse-2.8.3+dfsg/debian/rules 2020-06-29 10:06:35.0
+0200
+++ cpl-plugin-muse-2.8.3+dfsg/debian/rules 2021-02-21 22:25:07.0
+0100
@@ -11,7 +11,7 @@
sh ./debian/repackage.sh
%:
- dh $@ --with sphinxdoc
+ dh $@
debian_files:
if [ -d calib/cal ] ; then \
@@ -40,11 +40,6 @@
sphinx-build sphinx sphinx/html
dh_installdocs
-override_dh_sphinxdoc:
- if [ -d sphinx ] ; then \
- dh_sphinxdoc ; \
- fi
-
override_dh_clean:
dh_clean
rm -rf debian/${DEB_SOURCE}.install \
--- End Message ---
--- Begin Message ---
Source: cpl-plugin-muse
Source-Version: 2.8.3+dfsg-2
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
cpl-plugin-muse, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated cpl-plugin-muse package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Feb 2021 14:54:27 +0100
Source: cpl-plugin-muse
Architecture: source
Version: 2.8.3+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team
Changed-By: Ole Streicher
Closes: 983277
Changes:
cpl-plugin-muse (2.8.3+dfsg-2) unstable; urgency=medium
.
[ Helmut Grohne ]
* Request sphinxdoc addon via B-D-I (Closes: #983277)
Checksums-Sha1:
8fc1989e0fefa0ef8ed611b393c7442f8c345a7e 2396 cpl-plugin-muse_2.8.3+dfsg-2.dsc
8b527de0e2d17a179b87e773111c40439c4e63ec 13692
cpl-plugin-muse_2.8.3+dfsg-2.debian.tar.xz
Checksums-Sha256:
200becc1fd0c3c4e6da42707d3cf1332b8601ee9a178a7c5b52fe993980ca508 2396
cpl-plugin-muse_2.8.3+dfsg-2.dsc
868f8ebfde8599e3db7561fe292914caa3659c5b6b1da33b9b4d3a8926964ae3 13692
cpl-plugin-muse_2.8.3+dfsg-2.debian.tar.xz
Files:
Bug#983283: marked as done (cpl-plugin-uves: demote sphinx dependency to B-)
Your message dated Mon, 22 Feb 2021 13:48:59 +
with message-id
and subject line Bug#983283: fixed in cpl-plugin-uves 6.1.3+dfsg-3
has caused the Debian Bug report #983283,
regarding cpl-plugin-uves: demote sphinx dependency to B-
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983283
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpl-plugin-uves
Version: 6.1.3+dfsg-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
cpl-plugin-uves cannot be cross built from source, because its sphinx
dependency is not satisfiable. Since the documentation is already split
to an arch:all package and the documentation is only built during an
arch-only build, all that needs doing is restricting the usage of the
shpinxdoc addon to the indep part. Please consider applying the attached
patch.
Helmut
diff --minimal -Nru cpl-plugin-uves-6.1.3+dfsg/debian/changelog
cpl-plugin-uves-6.1.3+dfsg/debian/changelog
--- cpl-plugin-uves-6.1.3+dfsg/debian/changelog 2020-07-02 09:39:10.0
+0200
+++ cpl-plugin-uves-6.1.3+dfsg/debian/changelog 2021-02-21 22:30:39.0
+0100
@@ -1,3 +1,10 @@
+cpl-plugin-uves (6.1.3+dfsg-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Request sphinxdoc addon via B-D-I. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 21 Feb 2021 22:30:39 +0100
+
cpl-plugin-uves (6.1.3+dfsg-2) unstable; urgency=low
* Increase tolerance in hdrl_fpn_tests
diff --minimal -Nru cpl-plugin-uves-6.1.3+dfsg/debian/control
cpl-plugin-uves-6.1.3+dfsg/debian/control
--- cpl-plugin-uves-6.1.3+dfsg/debian/control 2020-07-02 08:47:01.0
+0200
+++ cpl-plugin-uves-6.1.3+dfsg/debian/control 2021-02-21 22:28:04.0
+0100
@@ -11,7 +11,8 @@
python3,
python3-astropy,
python3-cpl,
- python3-sphinx
+Build-Depends-Indep: dh-sequence-sphinxdoc,
+ python3-sphinx
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/debian-astro-team/cpl-plugin-uves
Vcs-Git: https://salsa.debian.org/debian-astro-team/cpl-plugin-uves.git
diff --minimal -Nru cpl-plugin-uves-6.1.3+dfsg/debian/rules
cpl-plugin-uves-6.1.3+dfsg/debian/rules
--- cpl-plugin-uves-6.1.3+dfsg/debian/rules 2020-07-02 08:43:17.0
+0200
+++ cpl-plugin-uves-6.1.3+dfsg/debian/rules 2021-02-21 22:27:51.0
+0100
@@ -11,7 +11,7 @@
sh ./debian/repackage.sh
%:
- dh $@ --with sphinxdoc
+ dh $@
debian_files:
if [ -d calib/cal ] ; then \
@@ -40,11 +40,6 @@
sphinx-build sphinx sphinx/html
dh_installdocs
-override_dh_sphinxdoc:
- if [ -d sphinx ] ; then \
- dh_sphinxdoc ; \
- fi
-
override_dh_clean:
dh_clean
rm -rf debian/${DEB_SOURCE}.install \
--- End Message ---
--- Begin Message ---
Source: cpl-plugin-uves
Source-Version: 6.1.3+dfsg-3
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
cpl-plugin-uves, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated cpl-plugin-uves package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Feb 2021 14:28:18 +0100
Source: cpl-plugin-uves
Architecture: source
Version: 6.1.3+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers
Changed-By: Ole Streicher
Closes: 983283
Changes:
cpl-plugin-uves (6.1.3+dfsg-3) unstable; urgency=medium
.
[ Helmut Grohne ]
* Request sphinxdoc addon via B-D-I (Closes: #983283)
Checksums-Sha1:
f899e4ab0850ffe91dc7ee7204ad857404465ddf 2449 cpl-plugin-uves_6.1.3+dfsg-3.dsc
e282a8d40a9f0c599b72db6c83206cbe19579f30 11248
cpl-plugin-uves_6.1.3+dfsg-3.debian.tar.xz
Checksums-Sha256:
929f135042614ecf8ec9a118beb5119f1623bdb9dd3413dee27a56af60746291 2449
cpl-plugin-uves_6.1.3+dfsg-3.dsc
c957341518a4f4517fb29197711d3f8b9ccda0ff15cddacf925d24eea1367f1e 11248
cpl-plugin-uves_6.1.3+dfsg-3.debian.tar.xz
Files:
Bug#983281: marked as done (cpl-plugin-vimos: demote sphinx dependency to B-D-I)
Your message dated Mon, 22 Feb 2021 13:49:04 +
with message-id
and subject line Bug#983281: fixed in cpl-plugin-vimos 4.1.1+dfsg-2
has caused the Debian Bug report #983281,
regarding cpl-plugin-vimos: demote sphinx dependency to B-D-I
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpl-plugin-vimos
Version: 4.1.1+dfsg-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
cpl-plugin-vimos cannot be cross built from source, because its sphinx
dependency is not satisfiable. Since the documentation is already split
to an arch:all package and the documentation is only built during an
arch-only build, all that needs doing is restricting the usage of the
shpinxdoc addon to the indep part. Please consider applying the attached
patch.
Helmut
diff --minimal -Nru cpl-plugin-vimos-4.1.1+dfsg/debian/changelog
cpl-plugin-vimos-4.1.1+dfsg/debian/changelog
--- cpl-plugin-vimos-4.1.1+dfsg/debian/changelog2020-11-19
13:51:18.0 +0100
+++ cpl-plugin-vimos-4.1.1+dfsg/debian/changelog2021-02-21
22:30:22.0 +0100
@@ -1,3 +1,10 @@
+cpl-plugin-vimos (4.1.1+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Request sphinxdoc addon via B-D-I. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 21 Feb 2021 22:30:22 +0100
+
cpl-plugin-vimos (4.1.1+dfsg-1) unstable; urgency=medium
* New upstream version 4.1.1+dfsg
diff --minimal -Nru cpl-plugin-vimos-4.1.1+dfsg/debian/control
cpl-plugin-vimos-4.1.1+dfsg/debian/control
--- cpl-plugin-vimos-4.1.1+dfsg/debian/control 2020-07-02 08:24:29.0
+0200
+++ cpl-plugin-vimos-4.1.1+dfsg/debian/control 2021-02-21 22:30:07.0
+0100
@@ -10,7 +10,8 @@
python3,
python3-astropy,
python3-cpl,
- python3-sphinx
+Build-Depends-Indep: dh-sequence-sphinxdoc,
+ python3-sphinx
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/debian-astro-team/cpl-plugin-vimos
Vcs-Git: https://salsa.debian.org/debian-astro-team/cpl-plugin-vimos.git
diff --minimal -Nru cpl-plugin-vimos-4.1.1+dfsg/debian/rules
cpl-plugin-vimos-4.1.1+dfsg/debian/rules
--- cpl-plugin-vimos-4.1.1+dfsg/debian/rules2020-11-19 13:51:18.0
+0100
+++ cpl-plugin-vimos-4.1.1+dfsg/debian/rules2021-02-21 22:29:53.0
+0100
@@ -11,7 +11,7 @@
sh ./debian/repackage.sh
%:
- dh $@ --with sphinxdoc
+ dh $@
debian_files:
if [ -d calib/cal ] ; then \
@@ -40,11 +40,6 @@
sphinx-build sphinx sphinx/html
dh_installdocs
-override_dh_sphinxdoc:
- if [ -d sphinx ] ; then \
- dh_sphinxdoc ; \
- fi
-
override_dh_clean:
dh_clean
rm -rf debian/${DEB_SOURCE}.install \
--- End Message ---
--- Begin Message ---
Source: cpl-plugin-vimos
Source-Version: 4.1.1+dfsg-2
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
cpl-plugin-vimos, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated cpl-plugin-vimos
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Feb 2021 14:31:15 +0100
Source: cpl-plugin-vimos
Architecture: source
Version: 4.1.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers
Changed-By: Ole Streicher
Closes: 983281
Changes:
cpl-plugin-vimos (4.1.1+dfsg-2) unstable; urgency=medium
.
[ Helmut Grohne ]
* Request sphinxdoc addon via B-D-I (Closes: #983281)
Checksums-Sha1:
91de3a8f552ba9651059e1075f37b8fa13cc8ae2 2447 cpl-plugin-vimos_4.1.1+dfsg-2.dsc
000c618b88b081405cd5ec8708cd77e095476908 11256
cpl-plugin-vimos_4.1.1+dfsg-2.debian.tar.xz
Checksums-Sha256:
c80e76febea55e118df761cf140d6d8bef113abf73ca4af0a17222094cb38af1 2447
cpl-plugin-vimos_4.1.1+dfsg-2.dsc
42f40833cfa105941d0359e17d2fae3d691b75f3556dca9e7eef44e3582a1eeb 11256
Bug#983279: marked as done (cpl-plugin-naco: demote sphinx dependency to B-D-I)
Your message dated Mon, 22 Feb 2021 13:48:54 +
with message-id
and subject line Bug#983279: fixed in cpl-plugin-naco 4.4.9+dfsg-2
has caused the Debian Bug report #983279,
regarding cpl-plugin-naco: demote sphinx dependency to B-D-I
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpl-plugin-naco
Version: 4.4.9+dfsg-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
cpl-plugin-naco cannot be cross built from source, because its sphinx
dependency is not satisfiable. Since the documentation is already split
to an arch:all package and the documentation is only built during an
arch-only build, all that needs doing is restricting the usage of the
shpinxdoc addon to the indep part. Please consider applying the attached
patch.
Helmut
diff --minimal -Nru cpl-plugin-naco-4.4.9+dfsg/debian/changelog
cpl-plugin-naco-4.4.9+dfsg/debian/changelog
--- cpl-plugin-naco-4.4.9+dfsg/debian/changelog 2020-06-30 10:25:31.0
+0200
+++ cpl-plugin-naco-4.4.9+dfsg/debian/changelog 2021-02-21 22:28:13.0
+0100
@@ -1,3 +1,10 @@
+cpl-plugin-naco (4.4.9+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Request sphinxdoc addon via B-D-I. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 21 Feb 2021 22:28:13 +0100
+
cpl-plugin-naco (4.4.9+dfsg-1) unstable; urgency=low
* New upstream version 4.4.9+dfsg
diff --minimal -Nru cpl-plugin-naco-4.4.9+dfsg/debian/control
cpl-plugin-naco-4.4.9+dfsg/debian/control
--- cpl-plugin-naco-4.4.9+dfsg/debian/control 2020-06-30 10:25:20.0
+0200
+++ cpl-plugin-naco-4.4.9+dfsg/debian/control 2021-02-21 22:26:10.0
+0100
@@ -9,7 +9,8 @@
python3,
python3-astropy,
python3-cpl,
- python3-sphinx
+Build-Depends-Indep: dh-sequence-sphinxdoc,
+ python3-sphinx
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/debian-astro-team/cpl-plugin-naco
Vcs-Git: https://salsa.debian.org/debian-astro-team/cpl-plugin-naco.git
diff --minimal -Nru cpl-plugin-naco-4.4.9+dfsg/debian/rules
cpl-plugin-naco-4.4.9+dfsg/debian/rules
--- cpl-plugin-naco-4.4.9+dfsg/debian/rules 2020-06-30 10:25:20.0
+0200
+++ cpl-plugin-naco-4.4.9+dfsg/debian/rules 2021-02-21 22:25:57.0
+0100
@@ -11,7 +11,7 @@
sh ./debian/repackage.sh
%:
- dh $@ --with sphinxdoc
+ dh $@
debian_files:
if [ -d calib/cal ] ; then \
@@ -40,11 +40,6 @@
sphinx-build sphinx sphinx/html
dh_installdocs
-override_dh_sphinxdoc:
- if [ -d sphinx ] ; then \
- dh_sphinxdoc ; \
- fi
-
override_dh_clean:
dh_clean
rm -rf debian/${DEB_SOURCE}.install \
--- End Message ---
--- Begin Message ---
Source: cpl-plugin-naco
Source-Version: 4.4.9+dfsg-2
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
cpl-plugin-naco, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated cpl-plugin-naco package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Feb 2021 14:24:42 +0100
Source: cpl-plugin-naco
Architecture: source
Version: 4.4.9+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers
Changed-By: Ole Streicher
Closes: 983279
Changes:
cpl-plugin-naco (4.4.9+dfsg-2) unstable; urgency=medium
.
[ Helmut Grohne ]
* Request sphinxdoc addon via B-D-I (Closes: #983279)
Checksums-Sha1:
a99be868cba05671aee6e4a3637a242cb0d7fa8f 2416 cpl-plugin-naco_4.4.9+dfsg-2.dsc
0e80ce02911bc0da42e7a3952cdfd7994826817e 11104
cpl-plugin-naco_4.4.9+dfsg-2.debian.tar.xz
Checksums-Sha256:
2b468f0dfbc236c6fb5ffef5db5a47b700f32e09d79aefba50fa06738c780c46 2416
cpl-plugin-naco_4.4.9+dfsg-2.dsc
19b8f215fb54dad76aed30fd9dcf342f11355ff51e138f27201282b3568885c0 11104
cpl-plugin-naco_4.4.9+dfsg-2.debian.tar.xz
Files:
Bug#983274: marked as done (cpl-plugin-visir: demote sphinx dependency to B-D-I)
Your message dated Mon, 22 Feb 2021 13:49:09 +
with message-id
and subject line Bug#983274: fixed in cpl-plugin-visir 4.3.10+dfsg-3
has caused the Debian Bug report #983274,
regarding cpl-plugin-visir: demote sphinx dependency to B-D-I
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpl-plugin-visir
Version: 4.3.10+dfsg-2
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
cpl-plugin-visir cannot be cross built from source, because its sphinx
dependency is not satisfiable. Since the documentation is already split
to an arch:all package and the documentation is only built during an
arch-only build, all that needs doing is restricting the usage of the
shpinxdoc addon to the indep part. Please consider applying the attached
patch.
Helmut
diff --minimal -Nru cpl-plugin-visir-4.3.10+dfsg/debian/changelog
cpl-plugin-visir-4.3.10+dfsg/debian/changelog
--- cpl-plugin-visir-4.3.10+dfsg/debian/changelog 2020-08-02
16:41:42.0 +0200
+++ cpl-plugin-visir-4.3.10+dfsg/debian/changelog 2021-02-21
22:32:29.0 +0100
@@ -1,3 +1,10 @@
+cpl-plugin-visir (4.3.10+dfsg-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Request sphinxdoc addon via B-D-I. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 21 Feb 2021 22:32:29 +0100
+
cpl-plugin-visir (4.3.10+dfsg-2) unstable; urgency=medium
* Don't build swarp convenience copy. Closes: #957105
diff --minimal -Nru cpl-plugin-visir-4.3.10+dfsg/debian/control
cpl-plugin-visir-4.3.10+dfsg/debian/control
--- cpl-plugin-visir-4.3.10+dfsg/debian/control 2020-08-02 16:41:42.0
+0200
+++ cpl-plugin-visir-4.3.10+dfsg/debian/control 2021-02-21 22:32:27.0
+0100
@@ -8,7 +8,8 @@
python3,
python3-astropy,
python3-cpl,
- python3-sphinx
+Build-Depends-Indep: dh-sequence-sphinxdoc,
+ python3-sphinx
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/debian-astro-team/cpl-plugin-visir
Vcs-Git: https://salsa.debian.org/debian-astro-team/cpl-plugin-visir.git
diff --minimal -Nru cpl-plugin-visir-4.3.10+dfsg/debian/rules
cpl-plugin-visir-4.3.10+dfsg/debian/rules
--- cpl-plugin-visir-4.3.10+dfsg/debian/rules 2020-08-02 16:38:57.0
+0200
+++ cpl-plugin-visir-4.3.10+dfsg/debian/rules 2021-02-21 22:32:14.0
+0100
@@ -11,7 +11,7 @@
sh ./debian/repackage.sh
%:
- dh $@ --with sphinxdoc
+ dh $@
debian_files:
if [ -d calib/cal ] ; then \
@@ -40,11 +40,6 @@
sphinx-build sphinx sphinx/html
dh_installdocs
-override_dh_sphinxdoc:
- if [ -d sphinx ] ; then \
- dh_sphinxdoc ; \
- fi
-
override_dh_clean:
dh_clean
rm -rf debian/${DEB_SOURCE}.install \
--- End Message ---
--- Begin Message ---
Source: cpl-plugin-visir
Source-Version: 4.3.10+dfsg-3
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
cpl-plugin-visir, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated cpl-plugin-visir
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Feb 2021 14:37:15 +0100
Source: cpl-plugin-visir
Architecture: source
Version: 4.3.10+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team
Changed-By: Ole Streicher
Closes: 983274
Changes:
cpl-plugin-visir (4.3.10+dfsg-3) unstable; urgency=medium
.
[ Helmut Grohne ]
* Request sphinxdoc addon via B-D-I (Closes: #983274)
Checksums-Sha1:
c788fa3d7ff49e7d1505ec4a855f78caec54b526 2423
cpl-plugin-visir_4.3.10+dfsg-3.dsc
9cf39d590a294cb03831ee70a779d561a82ff6e9 11832
cpl-plugin-visir_4.3.10+dfsg-3.debian.tar.xz
Checksums-Sha256:
c6d6a3ba334382f77069c9daa6532de389aac327460c7832daff52c87f12d583 2423
cpl-plugin-visir_4.3.10+dfsg-3.dsc
Bug#983282: marked as done (cpl-plugin-giraf: demote sphinx dependency to B-D-I)
Your message dated Mon, 22 Feb 2021 13:33:41 +
with message-id
and subject line Bug#983282: fixed in cpl-plugin-giraf 2.16.7+dfsg-2
has caused the Debian Bug report #983282,
regarding cpl-plugin-giraf: demote sphinx dependency to B-D-I
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpl-plugin-giraf
Version: 2.16.7+dfsg-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
cpl-plugin-giraf cannot be cross built from source, because its sphinx
dependency is not satisfiable. Since the documentation is already split
to an arch:all package and the documentation is only built during an
arch-only build, all that needs doing is restricting the usage of the
shpinxdoc addon to the indep part. Please consider applying the attached
patch.
Helmut
diff --minimal -Nru cpl-plugin-giraf-2.16.7+dfsg/debian/changelog
cpl-plugin-giraf-2.16.7+dfsg/debian/changelog
--- cpl-plugin-giraf-2.16.7+dfsg/debian/changelog 2020-06-29
10:20:20.0 +0200
+++ cpl-plugin-giraf-2.16.7+dfsg/debian/changelog 2021-02-21
20:26:46.0 +0100
@@ -1,3 +1,10 @@
+cpl-plugin-giraf (2.16.7+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Request sphinxdoc addon via B-D-I.
+
+ -- Helmut Grohne Sun, 21 Feb 2021 20:26:46 +0100
+
cpl-plugin-giraf (2.16.7+dfsg-1) unstable; urgency=low
* New upstream version 2.16.7+dfsg
diff --minimal -Nru cpl-plugin-giraf-2.16.7+dfsg/debian/control
cpl-plugin-giraf-2.16.7+dfsg/debian/control
--- cpl-plugin-giraf-2.16.7+dfsg/debian/control 2020-06-29 10:19:53.0
+0200
+++ cpl-plugin-giraf-2.16.7+dfsg/debian/control 2021-02-21 20:25:25.0
+0100
@@ -8,7 +8,8 @@
python3,
python3-astropy,
python3-cpl,
- python3-sphinx
+Build-Depends-Indep: dh-sequence-sphinxdoc,
+ python3-sphinx
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/debian-astro-team/cpl-plugin-giraf
Vcs-Git: https://salsa.debian.org/debian-astro-team/cpl-plugin-giraf.git
diff --minimal -Nru cpl-plugin-giraf-2.16.7+dfsg/debian/rules
cpl-plugin-giraf-2.16.7+dfsg/debian/rules
--- cpl-plugin-giraf-2.16.7+dfsg/debian/rules 2020-06-29 10:19:53.0
+0200
+++ cpl-plugin-giraf-2.16.7+dfsg/debian/rules 2021-02-21 20:25:11.0
+0100
@@ -11,7 +11,7 @@
sh ./debian/repackage.sh
%:
- dh $@ --with sphinxdoc
+ dh $@
debian_files:
if [ -d calib/cal ] ; then \
@@ -40,11 +40,6 @@
sphinx-build sphinx sphinx/html
dh_installdocs
-override_dh_sphinxdoc:
- if [ -d sphinx ] ; then \
- dh_sphinxdoc ; \
- fi
-
override_dh_clean:
dh_clean
rm -rf debian/${DEB_SOURCE}.install \
--- End Message ---
--- Begin Message ---
Source: cpl-plugin-giraf
Source-Version: 2.16.7+dfsg-2
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
cpl-plugin-giraf, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated cpl-plugin-giraf
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Feb 2021 14:19:58 +0100
Source: cpl-plugin-giraf
Architecture: source
Version: 2.16.7+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers
Changed-By: Ole Streicher
Closes: 983282
Changes:
cpl-plugin-giraf (2.16.7+dfsg-2) unstable; urgency=medium
.
[ Helmut Grohne ]
* Request sphinxdoc addon via B-D-I (Closes: #983282)
Checksums-Sha1:
e8eec661c2ebc4f427cf479e88029e2ac55d430a 2452
cpl-plugin-giraf_2.16.7+dfsg-2.dsc
53f0c25a4d3d6d90f3d77eb78dc5252c310f70f0 9592
cpl-plugin-giraf_2.16.7+dfsg-2.debian.tar.xz
Checksums-Sha256:
9817a5505d96fb1a12f626b75dd54e6e0a26ad40cb541986fdb81c280103c866 2452
cpl-plugin-giraf_2.16.7+dfsg-2.dsc
7576da4f014add0c26b87a120dbe8054e9b732155dc890ae2c1e46ad5f9a81a7 9592
Bug#983276: marked as done (cpl-plugin-fors: demote sphinx dependency to B-D-I)
Your message dated Mon, 22 Feb 2021 13:33:36 +
with message-id
and subject line Bug#983276: fixed in cpl-plugin-fors 5.5.6+dfsg-2
has caused the Debian Bug report #983276,
regarding cpl-plugin-fors: demote sphinx dependency to B-D-I
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpl-plugin-fors
Version: 5.5.6+dfsg-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
cpl-plugin-fors cannot be cross built from source, because its sphinx
dependency is not satisfiable. Since the documentation is already split
to an arch:all package and the documentation is only built during an
arch-only build, all that needs doing is restricting the usage of the
shpinxdoc addon to the indep part. Please consider applying the attached
patch.
Helmut
diff --minimal -Nru cpl-plugin-fors-5.5.6+dfsg/debian/changelog
cpl-plugin-fors-5.5.6+dfsg/debian/changelog
--- cpl-plugin-fors-5.5.6+dfsg/debian/changelog 2020-10-15 16:17:22.0
+0200
+++ cpl-plugin-fors-5.5.6+dfsg/debian/changelog 2021-02-21 20:23:38.0
+0100
@@ -1,3 +1,10 @@
+cpl-plugin-fors (5.5.6+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Request sphinxdoc addon via B-D-I. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 21 Feb 2021 20:23:38 +0100
+
cpl-plugin-fors (5.5.6+dfsg-1) unstable; urgency=medium
* New upstream version 5.5.6+dfsg. Rediff patches
diff --minimal -Nru cpl-plugin-fors-5.5.6+dfsg/debian/control
cpl-plugin-fors-5.5.6+dfsg/debian/control
--- cpl-plugin-fors-5.5.6+dfsg/debian/control 2020-10-15 16:17:17.0
+0200
+++ cpl-plugin-fors-5.5.6+dfsg/debian/control 2021-02-21 20:23:37.0
+0100
@@ -10,7 +10,8 @@
python3,
python3-astropy,
python3-cpl,
- python3-sphinx
+Build-Depends-Indep: dh-sequence-sphinxdoc,
+ python3-sphinx
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/debian-astro-team/cpl-plugin-fors
Vcs-Git: https://salsa.debian.org/debian-astro-team/cpl-plugin-fors.git
diff --minimal -Nru cpl-plugin-fors-5.5.6+dfsg/debian/rules
cpl-plugin-fors-5.5.6+dfsg/debian/rules
--- cpl-plugin-fors-5.5.6+dfsg/debian/rules 2020-06-30 10:34:21.0
+0200
+++ cpl-plugin-fors-5.5.6+dfsg/debian/rules 2021-02-21 20:23:21.0
+0100
@@ -11,7 +11,7 @@
sh ./debian/repackage.sh
%:
- dh $@ --with sphinxdoc
+ dh $@
debian_files:
if [ -d calib/cal ] ; then \
@@ -40,11 +40,6 @@
sphinx-build sphinx sphinx/html
dh_installdocs
-override_dh_sphinxdoc:
- if [ -d sphinx ] ; then \
- dh_sphinxdoc ; \
- fi
-
override_dh_clean:
dh_clean
rm -rf debian/${DEB_SOURCE}.install \
--- End Message ---
--- Begin Message ---
Source: cpl-plugin-fors
Source-Version: 5.5.6+dfsg-2
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
cpl-plugin-fors, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated cpl-plugin-fors package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Feb 2021 14:16:15 +0100
Source: cpl-plugin-fors
Architecture: source
Version: 5.5.6+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers
Changed-By: Ole Streicher
Closes: 983276
Changes:
cpl-plugin-fors (5.5.6+dfsg-2) unstable; urgency=medium
.
[ Helmut Grohne ]
* Request sphinxdoc addon via B-D-I (Closes: #983276)
Checksums-Sha1:
0089d7820d8c7b8c63038658c60fa0e736e0e184 2431 cpl-plugin-fors_5.5.6+dfsg-2.dsc
e09316fda1ca65e0cd92f4bfb8f5aa183e055d2d 12796
cpl-plugin-fors_5.5.6+dfsg-2.debian.tar.xz
Checksums-Sha256:
d0d6d0ce64ec1e495b772bfb2845a78b268925d4db0b0d8cda37c4870ee87961 2431
cpl-plugin-fors_5.5.6+dfsg-2.dsc
ba24c2d5c1913f7eb6b02d9959f65cd3f30714f31b71f8b51ec9fe5a91984768 12796
Bug#983275: marked as done (cpl-plugin-hawki: demote sphinx dependency to B-D-I)
Your message dated Mon, 22 Feb 2021 13:33:46 +
with message-id
and subject line Bug#983275: fixed in cpl-plugin-hawki 2.4.8+dfsg-2
has caused the Debian Bug report #983275,
regarding cpl-plugin-hawki: demote sphinx dependency to B-D-I
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpl-plugin-hawki
Version: 2.4.8+dfsg-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
cpl-plugin-hawki cannot be cross built from source, because its sphinx
dependency is not satisfiable. Since the documentation is already split
to an arch:all package and the documentation is only built during an
arch-only build, all that needs doing is restricting the usage of the
shpinxdoc addon to the indep part. Please consider applying the attached
patch.
Helmut
diff --minimal -Nru cpl-plugin-hawki-2.4.8+dfsg/debian/changelog
cpl-plugin-hawki-2.4.8+dfsg/debian/changelog
--- cpl-plugin-hawki-2.4.8+dfsg/debian/changelog2020-06-30
10:09:16.0 +0200
+++ cpl-plugin-hawki-2.4.8+dfsg/debian/changelog2021-02-21
20:34:20.0 +0100
@@ -1,3 +1,10 @@
+cpl-plugin-hawki (2.4.8+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Request sphinxdoc addon via B-D-I. (Closes: #-1)
+
+ -- Helmut Grohne Sun, 21 Feb 2021 20:34:20 +0100
+
cpl-plugin-hawki (2.4.8+dfsg-1) unstable; urgency=low
[ Debian Janitor ]
diff --minimal -Nru cpl-plugin-hawki-2.4.8+dfsg/debian/control
cpl-plugin-hawki-2.4.8+dfsg/debian/control
--- cpl-plugin-hawki-2.4.8+dfsg/debian/control 2020-06-30 10:08:50.0
+0200
+++ cpl-plugin-hawki-2.4.8+dfsg/debian/control 2021-02-21 20:34:19.0
+0100
@@ -10,7 +10,8 @@
python3,
python3-astropy,
python3-cpl,
- python3-sphinx
+Build-Depends-Indep: dh-sequence-sphinxdoc,
+ python3-sphinx
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/debian-astro-team/cpl-plugin-hawki
Vcs-Git: https://salsa.debian.org/debian-astro-team/cpl-plugin-hawki.git
diff --minimal -Nru cpl-plugin-hawki-2.4.8+dfsg/debian/rules
cpl-plugin-hawki-2.4.8+dfsg/debian/rules
--- cpl-plugin-hawki-2.4.8+dfsg/debian/rules2020-06-30 10:08:50.0
+0200
+++ cpl-plugin-hawki-2.4.8+dfsg/debian/rules2021-02-21 20:30:04.0
+0100
@@ -8,7 +8,7 @@
PIPELINE ?= $(shell echo '$(DEB_SOURCE)' | sed -e 's/cpl-plugin-//')
%:
- dh $@ --with sphinxdoc
+ dh $@
debian_files:
if [ -d calib/cal ] ; then \
@@ -37,11 +37,6 @@
sphinx-build sphinx sphinx/html
dh_installdocs
-override_dh_sphinxdoc:
- if [ -d sphinx ] ; then \
- dh_sphinxdoc ; \
- fi
-
override_dh_clean:
dh_clean
rm -rf debian/${DEB_SOURCE}.install \
--- End Message ---
--- Begin Message ---
Source: cpl-plugin-hawki
Source-Version: 2.4.8+dfsg-2
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
cpl-plugin-hawki, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated cpl-plugin-hawki
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Feb 2021 14:22:04 +0100
Source: cpl-plugin-hawki
Architecture: source
Version: 2.4.8+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers
Changed-By: Ole Streicher
Closes: 983275
Changes:
cpl-plugin-hawki (2.4.8+dfsg-2) unstable; urgency=medium
.
[ Helmut Grohne ]
* Request sphinxdoc addon via B-D-I (Closes: #983275)
Checksums-Sha1:
ebc5355056769b4bfd6356d1a0f8b8cb4fa30772 2433 cpl-plugin-hawki_2.4.8+dfsg-2.dsc
c88601a20aa7b6eeea6121d610f3c2bfbc882724 9992
cpl-plugin-hawki_2.4.8+dfsg-2.debian.tar.xz
Checksums-Sha256:
c4cd88ca059fa7936fc2a7757ee9abb99d37deec332b2c6c506fef81a76c3e22 2433
cpl-plugin-hawki_2.4.8+dfsg-2.dsc
ac76b17163379d26c665870ae969166edc0baee4ec889ee990a3e5d5ed11db82
Bug#983315: marked as done (r-cran-plotly: autopkgtest regression)
Your message dated Mon, 22 Feb 2021 13:19:01 + with message-id and subject line Bug#983315: fixed in r-cran-plotly 4.9.3+dfsg-2 has caused the Debian Bug report #983315, regarding r-cran-plotly: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-bioc-plotly Version: 4.9.3+dfsg-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of 4.9.3+dfsg-1, r-cran-ploty has been failing its own autopkgtests [1] with the output below. Unfortunately, version 4.9.2.1+dfsg-2 had already regressed in bullseye, and 4.9.3+dfsg-1 was allowed to migrate. Regards Graham [1] https://ci.debian.net/packages/r/r-cran-plotly/testing/amd64/ == Failed tests -- Error (test-ggplot-hex.R:7:3): geom_hex - Error: there is no package called 'hexbin' Backtrace: x 1. \-plotly:::expect_doppelganger_built(g, "hex-basic") test-ggplot-hex.R:7:2 2. +-plotly::plotly_build(p) helper-vdiffr.R:71:2 3. \-plotly:::plotly_build.gg(p) 4. +-plotly::plotly_build(ggplotly(p)) 5. +-plotly::ggplotly(p) 6. \-plotly:::ggplotly.ggplot(p) 7. \-plotly::gg2list(...) 8. \-plotly:::layers2traces(data, prestats_data, layout, plot) 9. +-plotly::to_basic(...) 10. \-plotly:::to_basic.GeomHex(...) 11. \-hexbin::hexcoords 12. \-base::getExportedValue(pkg, name) 13. \-base::asNamespace(ns) 14. \-base::getNamespace(ns) 15. \-base::loadNamespace(name) 16. \-base::withRestarts(stop(cond), retry_loadNamespace = function() NULL) 17. \-base:::withOneRestart(expr, restarts[[1L]]) 18. \-base:::doWithOneRestart(return(expr), restart) -- Error (test-ggplot-hex.R:14:3): geom_hex with bins -- Error: there is no package called 'hexbin' Backtrace: x 1. \-plotly:::expect_doppelganger_built(g, "hex-bins") test-ggplot-hex.R:14:2 2. +-plotly::plotly_build(p) helper-vdiffr.R:71:2 3. \-plotly:::plotly_build.gg(p) 4. +-plotly::plotly_build(ggplotly(p)) 5. +-plotly::ggplotly(p) 6. \-plotly:::ggplotly.ggplot(p) 7. \-plotly::gg2list(...) 8. \-plotly:::layers2traces(data, prestats_data, layout, plot) 9. +-plotly::to_basic(...) 10. \-plotly:::to_basic.GeomHex(...) 11. \-hexbin::hexcoords 12. \-base::getExportedValue(pkg, name) 13. \-base::asNamespace(ns) 14. \-base::getNamespace(ns) 15. \-base::loadNamespace(name) 16. \-base::withRestarts(stop(cond), retry_loadNamespace = function() NULL) 17. \-base:::withOneRestart(expr, restarts[[1L]]) 18. \-base:::doWithOneRestart(return(expr), restart) -- Error (test-ggplot-hex.R:20:3): geom_hex with binwidth -- Error: there is no package called 'hexbin' Backtrace: x 1. \-plotly:::expect_doppelganger_built(g, "hex-binwidth") test-ggplot-hex.R:20:2 2. +-plotly::plotly_build(p) helper-vdiffr.R:71:2 3. \-plotly:::plotly_build.gg(p) 4. +-plotly::plotly_build(ggplotly(p)) 5. +-plotly::ggplotly(p) 6. \-plotly:::ggplotly.ggplot(p) 7. \-plotly::gg2list(...) 8. \-plotly:::layers2traces(data, prestats_data, layout, plot) 9. +-plotly::to_basic(...) 10. \-plotly:::to_basic.GeomHex(...) 11. \-hexbin::hexcoords 12. \-base::getExportedValue(pkg, name) 13. \-base::asNamespace(ns) 14. \-base::getNamespace(ns) 15. \-base::loadNamespace(name) 16. \-base::withRestarts(stop(cond), retry_loadNamespace = function() NULL) 17. \-base:::withOneRestart(expr, restarts[[1L]]) 18. \-base:::doWithOneRestart(return(expr), restart) [ FAIL 3 | WARN 47 | SKIP 41 | PASS 1103 ] Error: Test failures Execution halted autopkgtest [14:35:23]: test run-unit-test: ---] autopkgtest [14:35:23]: test run-unit-test: - - - - - - - - - - results - - - - - - - - - -
Bug#983278: marked as done (cpl-plugin-amber: demote sphinx dependency to B-D-I)
Your message dated Mon, 22 Feb 2021 13:18:34 +
with message-id
and subject line Bug#983278: fixed in cpl-plugin-amber 4.4.0+dfsg-2
has caused the Debian Bug report #983278,
regarding cpl-plugin-amber: demote sphinx dependency to B-D-I
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
983278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpl-plugin-amber
Version: 4.4.0+dfsg-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
cpl-plugin-amber cannot be cross built from source, because its sphinx
dependency is not satisfiable. Since the documentation is already split
to an arch:all package and the documentation is only built during an
arch-only build, all that needs doing is restricting the usage of the
shpinxdoc addon to the indep part. Please consider applying the attached
patch.
Helmut
diff --minimal -Nru cpl-plugin-amber-4.4.0+dfsg/debian/changelog
cpl-plugin-amber-4.4.0+dfsg/debian/changelog
--- cpl-plugin-amber-4.4.0+dfsg/debian/changelog2020-07-01
08:36:18.0 +0200
+++ cpl-plugin-amber-4.4.0+dfsg/debian/changelog2021-02-21
12:50:08.0 +0100
@@ -1,3 +1,10 @@
+cpl-plugin-amber (4.4.0+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Request sphinxdoc addon via B-D-I.
+
+ -- Helmut Grohne Sun, 21 Feb 2021 12:50:08 +0100
+
cpl-plugin-amber (4.4.0+dfsg-1) unstable; urgency=low
* New upstream version 4.4.0+dfsg
diff --minimal -Nru cpl-plugin-amber-4.4.0+dfsg/debian/control
cpl-plugin-amber-4.4.0+dfsg/debian/control
--- cpl-plugin-amber-4.4.0+dfsg/debian/control 2020-07-01 08:35:13.0
+0200
+++ cpl-plugin-amber-4.4.0+dfsg/debian/control 2021-02-21 12:50:08.0
+0100
@@ -10,7 +10,8 @@
python3,
python3-astropy,
python3-cpl,
- python3-sphinx
+Build-Depends-Indep: dh-sequence-sphinxdoc,
+ python3-sphinx
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/debian-astro-team/cpl-plugin-amber
Vcs-Git: https://salsa.debian.org/debian-astro-team/cpl-plugin-amber.git
diff --minimal -Nru cpl-plugin-amber-4.4.0+dfsg/debian/rules
cpl-plugin-amber-4.4.0+dfsg/debian/rules
--- cpl-plugin-amber-4.4.0+dfsg/debian/rules2020-07-01 08:35:13.0
+0200
+++ cpl-plugin-amber-4.4.0+dfsg/debian/rules2021-02-21 12:50:07.0
+0100
@@ -11,7 +11,7 @@
sh ./debian/repackage.sh
%:
- dh $@ --with sphinxdoc
+ dh $@
debian_files:
if [ -d calib/cal ] ; then \
@@ -40,11 +40,6 @@
sphinx-build sphinx sphinx/html
dh_installdocs
-override_dh_sphinxdoc:
- if [ -d sphinx ] ; then \
- dh_sphinxdoc ; \
- fi
-
override_dh_clean:
dh_clean
rm -rf debian/${DEB_SOURCE}.install \
--- End Message ---
--- Begin Message ---
Source: cpl-plugin-amber
Source-Version: 4.4.0+dfsg-2
Done: Ole Streicher
We believe that the bug you reported is fixed in the latest version of
cpl-plugin-amber, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ole Streicher (supplier of updated cpl-plugin-amber
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Feb 2021 13:54:38 +0100
Source: cpl-plugin-amber
Architecture: source
Version: 4.4.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers
Changed-By: Ole Streicher
Closes: 983278
Changes:
cpl-plugin-amber (4.4.0+dfsg-2) unstable; urgency=medium
.
[ Helmut Grohne ]
* Request sphinxdoc addon via B-D-I (Closes: #983278)
Checksums-Sha1:
6d06401994a88685f8c1c6391a4a782cd401adef 2443 cpl-plugin-amber_4.4.0+dfsg-2.dsc
7eafa0313012bb4f1a846e875b5fc1aff2c9d9d9 9376
cpl-plugin-amber_4.4.0+dfsg-2.debian.tar.xz
Checksums-Sha256:
1607c91b34196b103a218c5584e4f624b3a33efc624774bb5774ec01535a901d 2443
cpl-plugin-amber_4.4.0+dfsg-2.dsc
6d48db7ec0fe0f41e504b0e4ff50538599ea2a0c765b5a48ea181eb099b8f68c 9376
Bug#833269: marked as done (LXDE: screenshot key bound to launch gnome-screenshot, no dependency)
Your message dated Mon, 22 Feb 2021 15:04:49 +0200 with message-id <20210222130448.ga...@rep.kiev.ua> and subject line Re: LXDE: screenshot key bound to launch gnome-screenshot, no dependency has caused the Debian Bug report #833269, regarding LXDE: screenshot key bound to launch gnome-screenshot, no dependency to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 833269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833269 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: task-lxde-desktop Version: 3.31+deb8u1 Severity: important X-Debbugs-CC: pkg-maintain...@lists.alioth.debian.org Control: clone -1 -2 -3 Control: retitle -2 LXDE: screenshot key bound to launch gnome-screenshot, no dependency Control: severity -2 normal Control: retitle -3 LXDE: poor text wrapping for Wastebasket icon in default install Control: severity -3 minor I've just installed an LXDE desktop via task-lxde-desktop/the LXDE d-i jessie LXDE spin CD1 with no networking during install. The resulting desktop does not have a graphical web browser installed. www-browser is being provided by w3m. Clicking on the web browser in LXDE results in a pop-up "invalid desktop entry file: '/usr/share/applications/lxde-x-www-browser.desktop' I discovered this because I noticed that the desktop had one icon on it labelled "Wastebasket" but the text was wrapped on the last character, e.g. "Wastebaske\nt". I wanted to report this as an unfortunate wrapping. So I tried to take a screenshot by hitting "print screen". This resulted in a pop up complaining that gnome-screenshot did not exist. I would argue this was a missing dependency of the LXDE desktop task if it's bound to the print screen key by default. So I thought I'd do a quick web search to find an alternative way or package to install to take a screenshot of the desktop, hence I clicked on the web browser icon and discovered the above. The above are all visible here: https://jmtd.net/tmp/lxde.png -- System Information: Debian Release: 8.4 APT prefers stable APT policy: (990, 'stable'), (650, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-x86_64-linode63 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Jonathan Dowland Please do not CC me, I am subscribed to the list. signature.asc Description: Digital signature --- End Message --- --- Begin Message --- This issue appears to be fixed back in released 0.99.1-1 version. Let close it. If you happen to find any further issues with it then reopen it, please, with appropriate word about that. Thank you.--- End Message ---
Bug#978201: marked as done (autobahn-cpp: FTBFS: wamp_websocketpp_websocket_transport.ipp:55:113: error: ‘::_1’ has not been declared)
Your message dated Mon, 22 Feb 2021 13:03:32 + with message-id and subject line Bug#978201: fixed in autobahn-cpp 17.5.1+git7cc5d37-2.1 has caused the Debian Bug report #978201, regarding autobahn-cpp: FTBFS: wamp_websocketpp_websocket_transport.ipp:55:113: error: ‘::_1’ has not been declared to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 978201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: autobahn-cpp Version: 17.5.1+git7cc5d37-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux-gnu/examples && /usr/bin/c++ > -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK > -DBOOST_RANDOM_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK > -I/<> -std=c++11 -Wall -Werror -Wno-unused-variable > -fdiagnostics-color=auto -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security > -DMSGPACK_DEFAULT_API_VERSION=1 -Wdate-time -D_FORTIFY_SOURCE=2 -o > CMakeFiles/provide_prefix.dir/callee.cpp.o -c > /<>/examples/callee.cpp > In file included from > /<>/autobahn/wamp_websocketpp_websocket_transport.hpp:103, > from /<>/examples/websocket_callee.cpp:34: > /<>/autobahn/wamp_websocketpp_websocket_transport.ipp: In > constructor > ‘autobahn::wamp_websocketpp_websocket_transport::wamp_websocketpp_websocket_transport(autobahn::wamp_websocketpp_websocket_transport::client_type&, > const string&, bool)’: > /<>/autobahn/wamp_websocketpp_websocket_transport.ipp:55:113: > error: ‘::_1’ has not been declared >55 | > m_client.set_message_handler(bind(_websocketpp_websocket_transport::on_ws_message, > this, ::_1, ::_2)); > | > ^~ > /<>/autobahn/wamp_websocketpp_websocket_transport.ipp:55:113: > note: suggested alternatives: > In file included from /usr/include/boost/mpl/aux_/include_preprocessed.hpp:37, > from /usr/include/boost/mpl/placeholders.hpp:43, > from /usr/include/boost/iterator/iterator_categories.hpp:16, > from /usr/include/boost/iterator/iterator_facade.hpp:13, > from /usr/include/boost/range/iterator_range_core.hpp:27, > from /usr/include/boost/lexical_cast.hpp:30, > from /<>/autobahn/wamp_event.ipp:31, > from /<>/autobahn/wamp_event.hpp:208, > from /<>/autobahn/autobahn.hpp:40, > from /<>/examples/websocket_callee.cpp:33: > /usr/include/boost/mpl/aux_/preprocessed/gcc/placeholders.hpp:29:16: note: > ‘mpl_::_1’ >29 | typedef arg<1> _1; > |^~ > In file included from /usr/include/boost/system/error_code.hpp:19, > from /usr/include/boost/asio/detail/throw_error.hpp:19, > from /usr/include/boost/asio/detail/impl/posix_event.ipp:23, > from /usr/include/boost/asio/detail/posix_event.hpp:172, > from /usr/include/boost/asio/detail/event.hpp:25, > from > /usr/include/boost/asio/execution/blocking_adaptation.hpp:19, > from /usr/include/boost/asio/execution.hpp:22, > from /usr/include/boost/asio/any_io_executor.hpp:22, > from /usr/include/boost/asio/basic_socket_acceptor.hpp:19, > from /usr/include/boost/asio/ip/tcp.hpp:19, > from /<>/examples/parameters.hpp:34, > from /<>/examples/websocket_callee.cpp:31: > /usr/include/c++/10/functional:221:34: note: ‘std::placeholders::_1’ > 221 | extern const _Placeholder<1> _1; > | ^~ > In file included from /usr/include/boost/mpl/aux_/include_preprocessed.hpp:37, > from /usr/include/boost/mpl/placeholders.hpp:43, > from /usr/include/boost/iterator/iterator_categories.hpp:16, > from /usr/include/boost/iterator/iterator_facade.hpp:13, > from /usr/include/boost/range/iterator_range_core.hpp:27, > from /usr/include/boost/lexical_cast.hpp:30, > from /<>/autobahn/wamp_event.ipp:31, > from /<>/autobahn/wamp_event.hpp:208, > from
Bug#936530: marked as done (flatpak-builder: Python2 removal in sid/bullseye)
Your message dated Mon, 22 Feb 2021 12:18:33 + with message-id and subject line Bug#936530: fixed in flatpak-builder 1.0.12-1 has caused the Debian Bug report #936530, regarding flatpak-builder: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:flatpak-builder Version: 1.0.8-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:flatpak-builder If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: flatpak-builder Source-Version: 1.0.12-1 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of flatpak-builder, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated flatpak-builder package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 22 Feb 2021 08:42:42 + Source: flatpak-builder Architecture: source Version: 1.0.12-1 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Simon McVittie Closes: 936530 Changes: flatpak-builder (1.0.12-1) unstable; urgency=medium . * New upstream bugfix release - Make --run work if manifest has --metadata in build-finish - Don't extract git submodules if they're disabled - Make debug messages more understandable * Standards-Version: 4.5.1 (no changes required) * Drop autopkgtest that uses python2 (Closes: #936530) Checksums-Sha1: 14c65562cb219e187a40ae10a40985a796f3d662 2923 flatpak-builder_1.0.12-1.dsc 71b27eb92ba69c41a2ba24f4c10229b3948431f2 459764 flatpak-builder_1.0.12.orig.tar.xz 9247d75b87edc9914cf2befa61c174e4e4a9dbc6 6636 flatpak-builder_1.0.12-1.debian.tar.xz 892462b35632463fc3ccbb3aad6ff05a5a5814dd 10469
Processed: RFS: udfclient/0.8.11-2 [RC] -- userland implementation of the UDF filesystem
Processing commands for cont...@bugs.debian.org: > close 983312 Bug #983312 [sponsorship-requests] RFS: udfclient/0.8.11-2 [RC] -- userland implementation of the UDF filesystem Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 983312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976192: marked as done (ncal: incorrect week numbers for 2021)
Your message dated Mon, 22 Feb 2021 11:18:38 + with message-id and subject line Bug#976192: fixed in bsdmainutils 12.1.7+nmu2 has caused the Debian Bug report #976192, regarding ncal: incorrect week numbers for 2021 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976192 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ncal Version: 12.1.7 Severity: important Dear Maintainer, it seems that the output for week numbers for 2021 is incorrect: $ LC_TIME=de_DE.UTF-8 ncal -w3 November 2020 Dezember 2020 Januar 2021 Mo 2 9 16 23 30 7 14 21 284 11 18 25 Di 3 10 17 24 1 8 15 22 295 12 19 26 Mi 4 11 18 25 2 9 16 23 306 13 20 27 Do 5 12 19 26 3 10 17 24 317 14 21 28 Fr 6 13 20 27 4 11 18 251 8 15 22 29 Sa 7 14 21 28 5 12 19 262 9 16 23 30 So 1 8 15 22 29 6 13 20 273 10 17 24 31 44 45 46 47 48 49 49 50 51 52 1 1 2 3 4 5 Here January 2021 starts with week 1 on Friday, the 1st of January. The manpage for ncal(1) mentions: STANDARDS [...] The week number computed by -w is compliant with the ISO 8601 specification. ISO 8601 computes the week number depending on the year in which Thursday occurs, so 2020 should end on a Thursday with week 53. The same call on a system with bsdmainutils 11.1.2+b1 displays the correct week numbers, with week 53 spanning over the two years, and week 1 starting with 2021-01-04. - Roland -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.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 ncal depends on: ii libc6 2.31-3 ii libtinfo6 6.2+20200918-1 ncal recommends no packages. ncal suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: bsdmainutils Source-Version: 12.1.7+nmu2 Done: Uwe Kleine-König We believe that the bug you reported is fixed in the latest version of bsdmainutils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Uwe Kleine-König (supplier of updated bsdmainutils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 15 Feb 2021 11:31:35 +0100 Source: bsdmainutils Architecture: source Version: 12.1.7+nmu2 Distribution: unstable Urgency: medium Maintainer: Debian Bsdmainutils Team Changed-By: Uwe Kleine-König Closes: 976192 Changes: bsdmainutils (12.1.7+nmu2) unstable; urgency=medium . * Non-maintainer upload. * Fix ISO week calculation (Closes: #976192), thanks to Kate for the initial patch. Checksums-Sha1: f0e575ba89c6c65fcf60eeb3c2a40f57ec5f2e29 1434 bsdmainutils_12.1.7+nmu2.dsc 5a0f4ee812ed4372f1511e3d4670f2841e6e2213 173036 bsdmainutils_12.1.7+nmu2.tar.xz a43a89c6b9eea1c45a068672b509ebd6280bb5f1 6419 bsdmainutils_12.1.7+nmu2_amd64.buildinfo Checksums-Sha256: b8d9058f3a19169466d88ccf25dec13fc2e312e9a95ca9c451dd7564016778d2 1434 bsdmainutils_12.1.7+nmu2.dsc 00cb3eb3ef1d0f559669aed16a688abebb26bfbdf98bc38e5c24cddd3780de2b 173036 bsdmainutils_12.1.7+nmu2.tar.xz 244bcf32937f12763fde89baa88df11360bcb54592be4e77b5075ae04bfe7ef9 6419 bsdmainutils_12.1.7+nmu2_amd64.buildinfo Files: a5fc7ba105e0b1be46fd88a4cab71264 1434 utils optional bsdmainutils_12.1.7+nmu2.dsc b7388c77ed025d6585aad081de453edd 173036 utils optional bsdmainutils_12.1.7+nmu2.tar.xz 28f349fc952a1296cdfcf2a33863731d 6419 utils optional bsdmainutils_12.1.7+nmu2_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#982717: marked as done (udfclient: FTBFS: bmake[1]: no target to make.)
Your message dated Mon, 22 Feb 2021 11:03:45 +
with message-id
and subject line Bug#982717: fixed in udfclient 0.8.11-2
has caused the Debian Bug report #982717,
regarding udfclient: FTBFS: bmake[1]: no target to make.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
982717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: udfclient
Version: 0.8.11-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --buildsystem=bmake
>dh_update_autotools_config -O--buildsystem=bmake
> install -d debian/.debhelper/bucket/files
> cp -an --reflink=auto config.guess
> debian/.debhelper/bucket/files/420138cb266d63505ec54f169a34e1cc9aba80dc20a1eeac76b7bf5c9e5ff74e.tmp
> mv
> debian/.debhelper/bucket/files/420138cb266d63505ec54f169a34e1cc9aba80dc20a1eeac76b7bf5c9e5ff74e.tmp
>
> debian/.debhelper/bucket/files/420138cb266d63505ec54f169a34e1cc9aba80dc20a1eeac76b7bf5c9e5ff74e
> cp -f /usr/share/misc/config.guess ./config.guess
> cp -an --reflink=auto config.sub
> debian/.debhelper/bucket/files/6585881331b69439aec3e94b9167983f9c3609b1b5dca9fa77d6941a3f79ccc2.tmp
> mv
> debian/.debhelper/bucket/files/6585881331b69439aec3e94b9167983f9c3609b1b5dca9fa77d6941a3f79ccc2.tmp
>
> debian/.debhelper/bucket/files/6585881331b69439aec3e94b9167983f9c3609b1b5dca9fa77d6941a3f79ccc2
> cp -f /usr/share/misc/config.sub ./config.sub
>dh_autoreconf -O--buildsystem=bmake
> find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*'
> -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f
> -exec md5sum {} + -o -type l -printf "symlink %p
> " > debian/autoreconf.before
> grep -q ^XDT_ configure.ac
> autoreconf -f -i
> find ! -ipath "./debian/*" -a ! \( -path '*/.git/*' -o -path '*/.hg/*'
> -o -path '*/.bzr/*' -o -path '*/.svn/*' -o -path '*/CVS/*' \) -a -type f
> -exec md5sum {} + -o -type l -printf "symlink %p
> " > debian/autoreconf.after
>dh_auto_configure -O--buildsystem=bmake
>dh_auto_build -O--buildsystem=bmake
> bmake
> bmake[1]: no target to make.
>
> bmake[1]: stopped in /<>
> dh_auto_build: error: bmake returned exit code 2
> make: *** [debian/rules:8: build] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/02/13/udfclient_0.8.11-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: udfclient
Source-Version: 0.8.11-2
Done: Pali Rohár
We believe that the bug you reported is fixed in the latest version of
udfclient, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 982...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Pali Rohár (supplier of updated udfclient package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Feb 2021 11:12:33 +0100
Source: udfclient
Architecture: source
Version: 0.8.11-2
Distribution: unstable
Urgency: medium
Maintainer: Pali Rohár
Changed-By: Pali Rohár
Closes: 982717
Changes:
udfclient (0.8.11-2) unstable; urgency=medium
.
* Call autoconf in debian/rules to fix compile issues (Closes: #982717)
(Patch by Dennis Filder)
Checksums-Sha1:
4a95998a6265f73ec8d191f9d6523d8d64df413a 1753 udfclient_0.8.11-2.dsc
Processed: RFS: logswan/2.1.10-1 -- fast Web log analyzer using probabilistic data structures
Processing commands for cont...@bugs.debian.org: > close 983037 Bug #983037 [sponsorship-requests] RFS: logswan/2.1.10-1 -- fast Web log analyzer using probabilistic data structures Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 983037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: RFS: sasm/3.12.1-1 -- simple IDE for NASM, GAS and FASM assembly languages
Processing commands for cont...@bugs.debian.org: > close 983036 Bug #983036 [sponsorship-requests] RFS: sasm/3.12.1-1 -- simple IDE for NASM, GAS and FASM assembly languages Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 983036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: RFS: ansilove/4.1.5-1 -- ANSI and ASCII art to PNG converter
Processing commands for cont...@bugs.debian.org: > close 983038 Bug #983038 [sponsorship-requests] RFS: ansilove/4.1.5-1 -- ANSI and ASCII art to PNG converter Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 983038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> close 913585 3.6.4-2
Bug #913585 [src:dcmtk] warning: format '%ld' expects argument of type 'long
int', but argument 3 has type 'Sint32' {aka 'int'} [-Wformat=]
Ignoring request to alter fixed versions of bug #913585 to the same values
previously set
Bug #913585 [src:dcmtk] warning: format '%ld' expects argument of type 'long
int', but argument 3 has type 'Sint32' {aka 'int'} [-Wformat=]
Marked Bug as done
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
913585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > close 913227 3.6.4-2 Bug #913227 [src:dcmtk] dcmqrcbm.cc:319:38: warning: '%d' directive writing between 1 and 11 bytes into a region of size between 0 and 128 Marked as fixed in versions dcmtk/3.6.4-2. Bug #913227 [src:dcmtk] dcmqrcbm.cc:319:38: warning: '%d' directive writing between 1 and 11 bytes into a region of size between 0 and 128 Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 913227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913227 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fixed since scanlogd 2.2.5-3.2
Processing control commands:
> close -1
Bug #353547 [scanlogd] Can't dpkg-reconfigure scanlogd
Marked Bug as done
> fixed -1 2.2.5-3.2
Bug #353547 {Done: Mike Gabriel } [scanlogd]
Can't dpkg-reconfigure scanlogd
Marked as fixed in versions scanlogd/2.2.5-3.2.
--
353547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=353547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#982650: marked as done (mark golang-github-dcso-fluxline-dev Multi-Arch: foreign)
Your message dated Mon, 22 Feb 2021 08:33:41 +
with message-id
and subject line Bug#982650: fixed in golang-github-dcso-fluxline
0.0~git20200907.78686e5-2
has caused the Debian Bug report #982650,
regarding mark golang-github-dcso-fluxline-dev Multi-Arch: foreign
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
982650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-dcso-fluxline-dev
Version: 0.0~git20200907.78686e5-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability
Control: affects -1 + src:ethflux src:fever
The affected packages cannot satisfy their cross Build-Depends, because
their dependency on golang-github-dcso-fluxline-dev is not satisfiable.
In general, Architecture: all packages can never satisfy cross
Build-Depends unless marked Multi-Arch: foreign or annotated :native. In
this case, the foreign marking is reasonable, because
golang-github-dcso-fluxline-dev entirely lacks maintainer scripts and
all of its dependencies are already marked Multi-Arch: foreign. Please
consider applying the attached patch.
Helmut
diff --minimal -Nru
golang-github-dcso-fluxline-0.0~git20200907.78686e5/debian/changelog
golang-github-dcso-fluxline-0.0~git20200907.78686e5/debian/changelog
--- golang-github-dcso-fluxline-0.0~git20200907.78686e5/debian/changelog
2020-09-07 09:02:12.0 +0200
+++ golang-github-dcso-fluxline-0.0~git20200907.78686e5/debian/changelog
2021-02-12 18:04:00.0 +0100
@@ -1,3 +1,10 @@
+golang-github-dcso-fluxline (0.0~git20200907.78686e5-1.1) UNRELEASED;
urgency=medium
+
+ * Non-maintainer upload.
+ * Mark golang-github-dcso-fluxline-dev Multi-Arch: foreign. (Closes: #-1)
+
+ -- Helmut Grohne Fri, 12 Feb 2021 18:04:00 +0100
+
golang-github-dcso-fluxline (0.0~git20200907.78686e5-1) unstable;
urgency=medium
* New upstream snapshot.
diff --minimal -Nru
golang-github-dcso-fluxline-0.0~git20200907.78686e5/debian/control
golang-github-dcso-fluxline-0.0~git20200907.78686e5/debian/control
--- golang-github-dcso-fluxline-0.0~git20200907.78686e5/debian/control
2020-09-06 17:20:58.0 +0200
+++ golang-github-dcso-fluxline-0.0~git20200907.78686e5/debian/control
2021-02-12 18:03:59.0 +0100
@@ -17,6 +17,7 @@
Package: golang-github-dcso-fluxline-dev
Architecture: all
+Multi-Arch: foreign
Depends: ${shlibs:Depends},
${misc:Depends},
golang-github-showmax-go-fqdn-dev
--- End Message ---
--- Begin Message ---
Source: golang-github-dcso-fluxline
Source-Version: 0.0~git20200907.78686e5-2
Done: Sascha Steinbiss
We believe that the bug you reported is fixed in the latest version of
golang-github-dcso-fluxline, which is due to be installed in the Debian FTP
archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 982...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sascha Steinbiss (supplier of updated
golang-github-dcso-fluxline package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 22 Feb 2021 09:18:16 +0100
Source: golang-github-dcso-fluxline
Architecture: source
Version: 0.0~git20200907.78686e5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team
Changed-By: Sascha Steinbiss
Closes: 982650
Changes:
golang-github-dcso-fluxline (0.0~git20200907.78686e5-2) unstable;
urgency=medium
.
* Mark Multi-Arch: foreign (Closes: #982650)
Thanks to Helmut Grohne for the hint.
* Bump Standards-Version.
* Use watchfile version 4.
Checksums-Sha1:
9a0b190a01bf203fe5e1f8783f59d5840d1aa92d 2389
golang-github-dcso-fluxline_0.0~git20200907.78686e5-2.dsc
2cd9f1e6699e10d642a689dbbf597a6487f7a8f2 2992
golang-github-dcso-fluxline_0.0~git20200907.78686e5-2.debian.tar.xz
be38d94fc6e04df7ad87f968546dc04ebc3d9f25 6325
golang-github-dcso-fluxline_0.0~git20200907.78686e5-2_amd64.buildinfo
Checksums-Sha256:
d919c2430985283ee154e99831e94fca18ec6b7311ca26518de8073397209d31 2389
golang-github-dcso-fluxline_0.0~git20200907.78686e5-2.dsc
1678f493d7d76676cd8483300ae95e804d35efa2dbe9dc0f677fe2ebb757fa09 2992
Bug#983163: marked as done (golang-github-viant-toolbox: please make the build reproducible)
Your message dated Mon, 22 Feb 2021 08:16:24 + with message-id and subject line Bug#983163: fixed in golang-github-viant-toolbox 0.33.2-2 has caused the Debian Bug report #983163, regarding golang-github-viant-toolbox: please make the build reproducible to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 983163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-viant-toolbox Version: 0.33.2-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Hi, Whilst working on the Reproducible Builds effort [0] we noticed that golang-github-viant-toolbox could not be built reproducibly. This is becuase it ships files generated during the test phase that contain the build path. Patch attached that strips these, although please check that source.go is a test-related file; from a very quick glance it looks like it is. [0] https://reproducible-builds.org/ Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- --- a/debian/rules 2021-02-20 09:43:23.451310506 + --- b/debian/rules 2021-02-20 09:56:40.535574216 + @@ -20,3 +20,7 @@ dh_auto_test endif endif + +override_dh_auto_install: + dh_auto_install + find debian/ \( -name "*.stdout" -or -name "*.stdin" -or -name "source.go" \) -delete --- End Message --- --- Begin Message --- Source: golang-github-viant-toolbox Source-Version: 0.33.2-2 Done: Aloïs Micard We believe that the bug you reported is fixed in the latest version of golang-github-viant-toolbox, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 983...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aloïs Micard (supplier of updated golang-github-viant-toolbox package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Feb 2021 00:45:14 +0100 Source: golang-github-viant-toolbox Architecture: source Version: 0.33.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Aloïs Micard Closes: 983163 Changes: golang-github-viant-toolbox (0.33.2-2) unstable; urgency=medium . * Make the build reproducible, thanks to Chris Lamb! (Closes: #983163) * Bump Standards-Version. Checksums-Sha1: 70ff4f8e6732a137b58a9b5f7550bc4e917514e1 2614 golang-github-viant-toolbox_0.33.2-2.dsc 5edb7a1e860940a63af68389210d25ba6ac7d521 3832 golang-github-viant-toolbox_0.33.2-2.debian.tar.xz 72bdd5f6cb2ea1e90c679379abece6852d7f623e 8488 golang-github-viant-toolbox_0.33.2-2_amd64.buildinfo Checksums-Sha256: 53a1c5f6b345d82eabc113b22d33419fd59a972a1709f4ae2dedd3a3fc8c9412 2614 golang-github-viant-toolbox_0.33.2-2.dsc 0ad44487f92eeadaa95cc4abbf3d032028fefefd6e73ffd2a28d2c15a1920134 3832 golang-github-viant-toolbox_0.33.2-2.debian.tar.xz fd36821e1ceb60a3831e42afdb60777ef63f8a57a590833494e4350f47918611 8488 golang-github-viant-toolbox_0.33.2-2_amd64.buildinfo Files: 357bd5eb03b63611d204c8cca5289cae 2614 devel optional golang-github-viant-toolbox_0.33.2-2.dsc aa3db22299cecc190100ff7da8be83fb 3832 devel optional golang-github-viant-toolbox_0.33.2-2.debian.tar.xz 6c1e46355e03e8a2b2d495222ae462f9 8488 devel optional golang-github-viant-toolbox_0.33.2-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEECYc16JDXWgmzZBaOGg64LwcfXv4FAmAzX+wQHGFsb2lzQG1p Y2FyZC5sdQAKCRAaDrgvBx9e/gQfD/0b1XCvH4C7bkMvgHaQnnbdkOXVOpHLcIcs GZIOgqv3NpJ9r+USfLxfCkdZfYmpj2Ux/7TqcnCTXcZ0hB6Fw1qtpJ+tdPo1JC24 P5J0opt5hKp+ksOlEZXg9O5IIZ+2jgx67pX3QnzAQpFIjfrNiPOuXxeIvFpZYvBe DoBu4lLbsBiC94IHANh5FAn6ITCliEbyOgB0pXtvtbz0+5glGGAhqmAfap+4z42T Qf2ymjVtNUXaDCHj3rXbhZlVYzuKJeNwZwSJEUY3MhDALxHX9rfGsprzPQslf4Jv BTAzE1/qdHDsiZpkZVp3mA6Lrcljm3fXkFuR0hBIX/XZIhYGM+xo9Cv6gWxvv8Ti omCilMw3mWYwozUW3l+e7gNv2Ugm3Qqu8igu0td2wnc1w0S3otalIzd/Z6fUNe77 RkCaHzzuDz/Xr9/uiWd2P0yP162zRpcf8r21mCCOqOl1VGth4zwQn1otVLwZCsb8 B5/XAkAmXUvp+reAbsnv+CycbWovzq1ufWSseOljf0FRA4voX8ghtx8y8WDpSwiQ
