Processed: Bug#990708 marked as pending in mariadb-10.5
Processing control commands: > tag -1 pending Bug #990708 [mariadb-server-10.5,galera-4] mariadb-server-10.5: upgrade problems due to galera-3 -> galera-4 switch Ignoring request to alter tags of bug #990708 to the same tags previously set -- 990708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990708 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990708: marked as pending in mariadb-10.5
Control: tag -1 pending Hello, Bug #990708 in mariadb-10.5 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/8f7e9fbf5873ffa904f15bd3dc1823fd2240e08a Ease switching from galera-3 to galera-4 on upgrades from buster Add Breaks: galera-3 (<< 26.4) to mariadb-server-10.5 Closes: #990708 (this message was generated automatically) -- Greetings https://bugs.debian.org/990708
Processed: Re: Bug#991087: gir1.2-inputpad-1.0 has empty Depends
Processing control commands: > severity -1 normal Bug #991087 [gir1.2-inputpad-1.0] gir1.2-inputpad-1.0 has empty Depends Severity set to 'normal' from 'serious' > tags -1 pending Bug #991087 [gir1.2-inputpad-1.0] gir1.2-inputpad-1.0 has empty Depends Added tag(s) pending. -- 991087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991087: gir1.2-inputpad-1.0 has empty Depends
Control: severity -1 normal Control: tags -1 pending Thanks for your bug report! I committed the change to the repo: https://salsa.debian.org/input-method-team/input-pad/-/commit/6454fbca -- Rgds, Gunnar Hjalmarsson
Bug#990540: closing 990540
close 990540 2.1.2-3 thanks
Processed: closing 990540
Processing commands for cont...@bugs.debian.org: > close 990540 2.1.2-3 Bug #990540 [src:mruby] mruby: CVE-2020-36401 Ignoring request to alter fixed versions of bug #990540 to the same values previously set Bug #990540 [src:mruby] mruby: CVE-2020-36401 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 990540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991056: marked as done (foxtrotgps FTBFS with imagemagick with the #987504 change)
Your message dated Wed, 14 Jul 2021 00:18:29 + with message-id and subject line Bug#991056: fixed in foxtrotgps 1.2.2+bzr330-1 has caused the Debian Bug report #991056, regarding foxtrotgps FTBFS with imagemagick with the #987504 change 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.) -- 991056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: foxtrotgps Version: 1.2.1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/foxtrotgps.html ... Making all in doc make[3]: Entering directory '/build/foxtrotgps-1.2.1/doc' convert foxtrotgps-logo.png foxtrotgps-logo.eps convert screenshots/main-window.png screenshots/main-window.eps convert screenshots/map-download.png screenshots/map-download.eps convert screenshots/tracking.png screenshots/tracking.eps convert screenshots/found-route.png screenshots/found-route.eps convert screenshots/get-route.png screenshots/get-route.eps convert screenshots/route-planning.png screenshots/route-planning.eps convert cc-by-sa.png cc-by-sa.eps convert cc-by-sa_small.png cc-by-sa_small.eps make -C ../src foxtrotgps make[4]: Entering directory '/build/foxtrotgps-1.2.1/src' make[4]: 'foxtrotgps' is up to date. make[4]: Leaving directory '/build/foxtrotgps-1.2.1/src' help2man sh --output=foxtrotgps.1.in \ --help-option="-c \"../src/foxtrotgps \ --help | sed -e '1N;2s/\\n//'\"" \ --version-option="-c \"../src/foxtrotgps\ --version\"" \ --info-page=foxtrotgps \ --include=./foxtrotgps.h2m.in convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. make[3]: *** [Makefile:931: screenshots/map-download.eps] Error 1 See #987504 for background. --- End Message --- --- Begin Message --- Source: foxtrotgps Source-Version: 1.2.2+bzr330-1 Done: Paul Wise We believe that the bug you reported is fixed in the latest version of foxtrotgps, 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 991...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Wise (supplier of updated foxtrotgps 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: Wed, 14 Jul 2021 07:58:30 +0800 Source: foxtrotgps Architecture: source Version: 1.2.2+bzr330-1 Distribution: unstable Urgency: medium Maintainer: Paul Wise Changed-By: Paul Wise Closes: 991056 Changes: foxtrotgps (1.2.2+bzr330-1) unstable; urgency=medium . * New upstream snapshot. - Fixes FTBFS with new imagemagick (Closes: #991056) - Fixes use of deprecated gpsd API (see LP#1917998) Checksums-Sha1: 22900c85ac11cbdd4d95ebf5044459be2e3a67a8 2568 foxtrotgps_1.2.2+bzr330-1.dsc 782e05ceb4f137ac8da147cc9887e83ec1533f8e 44620 foxtrotgps_1.2.2+bzr330.orig-changelog.tar.gz 76488eb43999e37c1552764472837ffd57f00a7e 709066 foxtrotgps_1.2.2+bzr330.orig-screenshots.tar.gz 3e32fa3d478c5b5917792c5e990dc3acfa2a8a71 284131 foxtrotgps_1.2.2+bzr330.orig.tar.gz a7a0aa25064766e06120aa410d89bbceeb1f6b42 17836 foxtrotgps_1.2.2+bzr330-1.debian.tar.xz Checksums-Sha256: 2dde943d8e1d3c736fcf018468010af9c54f91b434f307f83e451bc50c4fc7f1 2568 foxtrotgps_1.2.2+bzr330-1.dsc 8c283df76b9edd1baed484362745f7c571da2408b27bbdbd3408f50287742ac0 44620 foxtrotgps_1.2.2+bzr330.orig-changelog.tar.gz 96c6c6dfc88273c3e8a909c35a2a9a88c3cc69bfaf5ce5cd3d8fade05e6df91a 709066 foxtrotgps_1.2.2+bzr330.orig-screenshots.tar.gz 4d71df7a161117c5c016137ca30c53eac0a6ee3a743c1c7ea5e62017d33f95f1 284131 foxtrotgps_1.2.2+bzr330.orig.tar.gz 4fcb64b6fbfecbb94b6f17395f95e40bf30611a34ee2aedefd1f67d76fc6100c 17836 foxtrotgps_1.2.2+bzr330-1.debian.tar.xz Files: b57910b101ff1e2e870a797557aacfbf 2568 comm optional foxtrotgps_1.2.2+bzr330-1.dsc 1387a85958b4cb640ed3f1f8010837ac 44620 comm optional foxtrotgps_1.2.2+bzr330.orig-changelog.tar.gz 924f4e68780268d3b9f1c6dd93fd4d75 709066 comm
Processed: fixed 990540 in 2.1.2-3
Processing commands for cont...@bugs.debian.org: > fixed 990540 2.1.2-3 Bug #990540 [src:mruby] mruby: CVE-2020-36401 Marked as fixed in versions mruby/2.1.2-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 990540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986686: missing b-d netpbm?
Hi Hilmar, > > @Norbert: do you have an opinion. Should be rather branch from 20200329-1, > > which is currently in testing? Seems to be ok. Documentation fixes are explicitly included in the freeze exception list. Please: - prepare a debdiff (even if it is long) - file a freeze exception bug report - include the *code* (debian/control) changes in the main email and state that the rest of the debdiff is documentation only changes - state that *no* functional changes are there, only ensuring that there is no FTBFS - after the ok, upload I guess that should do it Thanks a lot Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#986686: missing b-d netpbm?
On Tue, 13 Jul 2021, Hilmar Preuße wrote: > @Norbert: do you have an opinion. Should be rather branch from 20200329-1, > which is currently in testing? I asked on the IRC channel #debian-release. But I am not sure what the answer will be. Best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bug#991061: ns3 FTBFS with imagemagick with the #987504 change
Hello, thanks for the report. I've read through the bugs both in debian and ubuntu, and I found the location of the issue in the package (ns3 is quite a large package). ns-3.31/doc/models/Makefile reads (many lines omitted): ``` CONVERT = convert # specify figures from which .png and .pdf figures need to be # generated (all dia and eps figures) IMAGES_EPS = \ $(FIGURES)/lena-dual-stripe.eps \ %.png : %.eps @echo convert $(notdir $<) @$(CONVERT) $< $@ >/dev/null ``` Now, the question is about what is the best move from here. I cannot do as in the bug I've seen by Ubuntu where the eps doc was disabled, as we use(d) convert to move the other way around, eps -> png. Is there another way to convert eps to png that I could use (according to google, ImageMagik is THE way to go here), or shall I ship a broken documentation? Any advice would be welcome here. Thanks, Mt. - Le 13 Juil 21, à 15:59, Adrian Bunk b...@debian.org a écrit : > Source: ns3 > Version: 3.29+dfsg-3 > Severity: serious > Tags: ftbfs > > https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/ns3.html > > ... > convert lena-dual-stripe.eps > convert-im6.q16: attempt to perform an operation not allowed by the security > policy `PS' @ error/constitute.c/IsCoderAuthorized/408. > convert-im6.q16: no images defined `source-temp/figures/lena-dual-stripe.png' > @ > error/convert.c/ConvertImageCommand/3258. > make[2]: *** [Makefile:475: source-temp/figures/lena-dual-stripe.png] Error 1 > > > See #987504 for background.
Bug#986686: missing b-d netpbm?
Am 13.07.2021 um 23:27 teilte Adrian Bunk mit: On Tue, Jul 13, 2021 at 10:13:20PM +0200, Hilmar Preuße wrote: Hi, I am not a member of the release team. "It is just documentation" has a point, suggesting d85a1829 plus UNRELEASED -> unstable would sound reasonable to me. You could ask the release team by submitting an unblock request with reportbug release.debian.org containing a diff of debian/ between the version currently in testing and what you'd like to upload. Yes, yes. The debdiff has a size of 270KB and I don't even intend to read it. @Norbert: do you have an opinion. Should be rather branch from 20200329-1, which is currently in testing? Hilmar -- sigfault OpenPGP_signature Description: OpenPGP digital signature
Bug#986686: missing b-d netpbm?
On Tue, Jul 13, 2021 at 10:13:20PM +0200, Hilmar Preuße wrote: > Am 13.07.2021 um 16:13 teilte Adrian Bunk mit: >... > Hi Adrian, Hi Hilmar, > > > > > The Makefile has a fallback to netpbm, but this does not work as > > > > > we do not declare a B-D on netpbm. We could simply add it. > > > > > > > > > > What do you think? > > > > > > > > yes, that would be nice. Afaics, Ubuntu disabled that explicitly in > > > > https://launchpad.net/ubuntu/+source/imagemagick/8:6.9.10.23+dfsg-2.1ubuntu3 > > > > > > > Patch tested and committed to github, tag pending. > > > > Please upload, since this is now also a FTBFS in Debian: > > https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/texworks-manual.html > > > > See #987504 for background. > > > Will you accept a new upstream snapshot to fix the issue? > > In this case I'd branch from our commit > d85a18296e529ed7ba4af1945fab8c90670835a6 and use that one as starter. It is > just documentation so it should not break other packages. I am not a member of the release team. "It is just documentation" has a point, suggesting d85a1829 plus UNRELEASED -> unstable would sound reasonable to me. You could ask the release team by submitting an unblock request with reportbug release.debian.org containing a diff of debian/ between the version currently in testing and what you'd like to upload. > Hilmar cu Adrian
Bug#991082: gir1.2-gtd-1.0 has empty Depends
On Tue, Jul 13, 2021 at 10:52:06PM +0200, Andreas Henriksson wrote:
>...
> On Tue, Jul 13, 2021 at 09:35:24PM +0300, Adrian Bunk wrote:
> > Package: gir1.2-gtd-1.0
> > Version: 3.28.1-2
> > Severity: serious
> >
> > ${gir:Depends} needs "dh --with gir" in debian/rules.
>
> Sure, why not it looks like a possible oversight and could be added
> to the packaging at some point.
>...
> > Depends: gir1.2-glib-2.0, gir1.2-gtk-3.0 (>= 3.19.5)
>...
> I'm not sure which actual problem that solves though. Do you have
> a particular use-case that's affected by this?
>...
$ g-ir-inspect --print-typelibs Gtd
Failed to load typelib: Typelib file for namespace 'Gtk', version '3.0' not
found
$
This is caused by the empty Depends, and fixed when installing the
dependencies debhelper would generate with "--with gir" manually.
> Regards,
> Andreas Henriksson
cu
Adrian
Bug#991082: gir1.2-gtd-1.0 has empty Depends
Hello Adrian Bunk,
On Tue, Jul 13, 2021 at 09:35:24PM +0300, Adrian Bunk wrote:
> Package: gir1.2-gtd-1.0
> Version: 3.28.1-2
> Severity: serious
>
> ${gir:Depends} needs "dh --with gir" in debian/rules.
Sure, why not it looks like a possible oversight and could be added
to the packaging at some point.
>
> Something might still go wrong after that,
> when trying it did not generate dependencies
> on any library:
> Depends: gir1.2-glib-2.0, gir1.2-gtk-3.0 (>= 3.19.5)
There is no traditional shared object to depend on
The files that are being introspected (a) are part of the main program
executable (b) as can be seen in src/meson.build.
(a):
https://sources.debian.org/src/gnome-todo/3.28.1-6/src/meson.build/#L211
(b):
https://sources.debian.org/src/gnome-todo/3.28.1-6/src/meson.build/#L43
The easiest way to "solve" this would likely be to just set the
introspection build option (c) to false and drop the gir1.2-gtd-1.0
package as it has no reverse dependencies.
(c):
https://sources.debian.org/src/gnome-todo/3.28.1-6/meson_options.txt/#L11
I'm not sure which actual problem that solves though. Do you have
a particular use-case that's affected by this?
If this is only a theoretical correctness discussion, then I don't think
it deserves any attention before the release (or even future point
releases). I fear that if pushing through the suggested "solution",
next you'll find out that libgnome-todo-dev doesn't depend on
any shared object package either... then start filing bug reports
about libnome-todo lacking a sover in the name, not containing
a shared object, etc Is there anything that's actually breaking
in the real world caused by anything discussed in this bug report?
(Note libgnome-todo-dev has no rdeps either, and the content of
libgnome-todo could likely just be folded into the gnome-todo
binary package... and then why not merge gnome-todo-common as well
to really simplify the packaging making this a simple single-
binary package. OTOH changes like that are likely better done
during the next development cycle... and by someone who knows
what the future direction of gnome-todo might be, but feel free
to send a merge-request!)
Regards,
Andreas Henriksson
Processed: tagging 991040
Processing commands for cont...@bugs.debian.org: > tags 991040 + upstream confirmed Bug #991040 [varnish] Varnish VSV7 Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 991040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991040 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991086: marked as done (gir1.2-gtklayershell-0.1 has empty Depends)
Your message dated Tue, 13 Jul 2021 20:33:28 +
with message-id
and subject line Bug#991086: fixed in gtk-layer-shell 0.5.2-2
has caused the Debian Bug report #991086,
regarding gir1.2-gtklayershell-0.1 has empty Depends
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
991086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gir1.2-gtklayershell-0.1
Version: 0.5.2-1
Severity: serious
${gir:Depends} needs "dh --with gir" in debian/rules.
--- End Message ---
--- Begin Message ---
Source: gtk-layer-shell
Source-Version: 0.5.2-2
Done: Mike Gabriel
We believe that the bug you reported is fixed in the latest version of
gtk-layer-shell, 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 991...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mike Gabriel (supplier of updated gtk-layer-shell
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, 13 Jul 2021 22:12:02 +0200
Source: gtk-layer-shell
Architecture: source
Version: 0.5.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team
Changed-By: Mike Gabriel
Closes: 991086
Changes:
gtk-layer-shell (0.5.2-2) unstable; urgency=medium
.
* debian/rules:
+ Add '--with gir' to dh command. (Closes: #991086).
Checksums-Sha1:
358586da664848cb20c4d6d8d8de71bbe67e619e 2485 gtk-layer-shell_0.5.2-2.dsc
d1d7a40ac118cb470e2b54c7323ccf0385f248c8 9488
gtk-layer-shell_0.5.2-2.debian.tar.xz
a390746dd369510932c4fe1bc2b155ead1960629 14487
gtk-layer-shell_0.5.2-2_source.buildinfo
Checksums-Sha256:
899899c58392940f564d930494766ab00c71f5ed412b3964729c13203629a88a 2485
gtk-layer-shell_0.5.2-2.dsc
9000161f79fee710f34c87adef81e72f7a6c3a3dc11711e0580aa62909f96d49 9488
gtk-layer-shell_0.5.2-2.debian.tar.xz
e0cbf5a571da6140a0cad240a7559d21d846520e50febe1cdd581eb3bca72d0c 14487
gtk-layer-shell_0.5.2-2_source.buildinfo
Files:
01c21cda314019733cdb1aa3c35e8711 2485 libdevel optional
gtk-layer-shell_0.5.2-2.dsc
9369d1ed2fac1dba3d68e7c840fbe896 9488 libdevel optional
gtk-layer-shell_0.5.2-2.debian.tar.xz
7bbf360680da339c9b51f21bf500d9f8 14487 libdevel optional
gtk-layer-shell_0.5.2-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmDt9FwVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsx1MgP/2zONB2k254LaQ0vQfexEp2On4RM
WIHWBsGfgjuCjy/slCLAWtEz6JYzFGfvhBm3eRSQhzFBZwuG4E1SEI0Q45Tnb2gZ
lMrpTb0z/aACMCZeCqUqwN6DwCRZ0vRu6NlR79qYcRyPy6xzyNe14jOdxdBQ7vZj
pZWBELe5qYcZwCS1bSRUUAdFyE9o+hEmtufhUi2Il2neVRsLo/YzEeJH0qNOBqTr
KDXdKi32Ymj39pd4ybCCQ3tm+g7eQjfKlI0D185tw93KPoAj2z0/QRFQ691gkuCb
r/jEkZX46NGYl3SU7uUUP75+yEEidcpt05oMmQ1PzPu9bcbrWf1HIpAS0P6YEKfk
H1Dhu1UKVWswRZ37gkL+UdcBC8UV90kURg4FCfxAfA/iv4VF+/aMka0bDD8sxxZf
XSmIneR7i3yqhGbmDRjDsgu5xG2gPZv0S45tGE9QfTiS99eWrl8b2o5VY/YTmI9l
h0VMnGtlDa5V85TxBNBe8PjcLoJIVA4QQRg9LGUs6GMrIrVC97jus264tKzIX1d5
f3x8jkA82h4EJyJ8KEDnpFe+191/3uC+dGgMr9wf2LbAWpQ66FMAjdGYOXO2aNPb
ITjb4S/Lbfp5KwKou3We3bkeE0021ZEkzUlKTlNKHpAWbeHmD5hXAQ4jxaxx2LMs
mrJ8ns72a0vuebfH
=huV5
-END PGP SIGNATURE End Message ---
Bug#990048: marked as done (dhelp cron.monthly job using invalid syntax for xargs)
Your message dated Tue, 13 Jul 2021 20:17:40 + with message-id and subject line Bug#990048: fixed in dhelp 0.6.27 has caused the Debian Bug report #990048, regarding dhelp cron.monthly job using invalid syntax for xargs 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.) -- 990048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dhelp Version: 0.6.26 Severity: normal Just got this today from one of my systems: --- /etc/cron.monthly/dhelp: xargs: warning: options --max-args and --max-lines/-l are mutually exclusive, ignoring previous --max-args value -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (500, 'testing-security'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-7-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dhelp depends on: ii doc-base0.11.1 ii ghostscript 9.53.3~dfsg-7 ii libcgi-pm-perl 4.51-1 ii libdata-page-perl 2.03-1 ii libhtml-parser-perl 3.75-1+b1 ii liblocale-gettext-perl 1.07-4+b1 ii libtemplate-perl2.27-1+b3 ii liburi-perl 5.08-1 ii perl5.32.1-4 ii poppler-utils 20.09.0-3.1 ii ruby1:2.7+2 ii ruby-debian 0.3.10+b4 ii ruby-gettext3.3.3-2 ii sensible-utils 0.0.14 ii swish++ 6.1.5-5 ii ucf 3.0043 dhelp recommends no packages. Versions of packages dhelp suggests: ii catdvi 0.14-12.1+b1 ii elinks [www-browser]0.13.2-1+b1 ii firefox [www-browser] 89.0-2 ii google-chrome-stable [www-browser] 91.0.4472.114-1 ii info2www1.2.2.9-24.1 ii man2html1.6g-14 ii nginx-core [httpd-cgi] 1.18.0-6.1 ii nginx-full [httpd-cgi] 1.18.0-6.1 -- no debconf information --- End Message --- --- Begin Message --- Source: dhelp Source-Version: 0.6.27 Done: Håvard Flaget Aasen We believe that the bug you reported is fixed in the latest version of dhelp, 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 990...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Håvard Flaget Aasen (supplier of updated dhelp 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, 13 Jul 2021 11:57:45 +0200 Source: dhelp Architecture: source Version: 0.6.27 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Håvard Flaget Aasen Closes: 990048 Changes: dhelp (0.6.27) unstable; urgency=medium . * QA upload. * d/cron.monthly: Update xargs command. Closes: #990048 Checksums-Sha1: a5b43743458997977c98ff7b1e8c2f6df45044c7 1523 dhelp_0.6.27.dsc 32b2ebcc603fd334844b3d410702e1dbae231334 73424 dhelp_0.6.27.tar.xz c5c9e7ecb070c3727b6b46c7df790c00fd1de2d6 5948 dhelp_0.6.27_source.buildinfo Checksums-Sha256: 37c202cdb8a6c83a8349048a50d02e68745daa8503603e9140ebb7f75931bb07 1523 dhelp_0.6.27.dsc 366992d766021245c0bd5bda90383a250ff23e12d176682a509c2fa12779e743 73424 dhelp_0.6.27.tar.xz 885aa60bfc9fde32f1ee877c20567440c201b5c698177cee56c17b0d8e202003 5948 dhelp_0.6.27_source.buildinfo Files: e5d584daf755304d38585bec14c263a0 1523 doc optional dhelp_0.6.27.dsc 601330d6f7ebb39fa942ab02b8425934 73424 doc optional dhelp_0.6.27.tar.xz e6d331d978eb5fe9521d6e1ccb203338 5948 doc optional dhelp_0.6.27_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmDt7IwACgkQweDZLphv fH7fyhAA9fMucrHWi1HJ7tR6p1ivTTLt1eapwZ6Lat6vzJFr/YAQLpoCwN38IPiG ujuHuVMZkuRT6k8t4Nh+u/BsPQ+T6/g8m9hf5yu0bYfcHCQjsJJpbAV8dt4H+oHV M4m8IN31X1CUx1E2LckfHt8jnZn93WzmjYS/OoUOG5Sz/S03pH9jRVKzRMJisK
Bug#986686: missing b-d netpbm?
Am 13.07.2021 um 16:13 teilte Adrian Bunk mit: Control: severity -1 serious Control: tags -1 ftbfs Control: found -1 20150506-2 On Sat, Apr 10, 2021 at 07:05:05PM +0200, Hilmar Preuße wrote: Control: tags -1 + pending Am 10.04.2021 um 11:59 teilte Matthias Klose mit: On 4/9/21 11:14 PM, Hilmar Preuße wrote: Hi Adrian, The Makefile has a fallback to netpbm, but this does not work as we do not declare a B-D on netpbm. We could simply add it. What do you think? yes, that would be nice. Afaics, Ubuntu disabled that explicitly in https://launchpad.net/ubuntu/+source/imagemagick/8:6.9.10.23+dfsg-2.1ubuntu3 Patch tested and committed to github, tag pending. Please upload, since this is now also a FTBFS in Debian: https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/texworks-manual.html See #987504 for background. Will you accept a new upstream snapshot to fix the issue? In this case I'd branch from our commit d85a18296e529ed7ba4af1945fab8c90670835a6 and use that one as starter. It is just documentation so it should not break other packages. Hilmar -- sigfault OpenPGP_signature Description: OpenPGP digital signature
Bug#991050: gcc-11 should (build) depend on binutils (>= 2.36)
On Tue, Jul 13, 2021 at 04:51:40PM +0200, Matthias Klose wrote: > No, 2.36 is not required. Perfectly fine to build with 2.35.2. That's correct. But if you build with 2.36, what does the runtime dependency say? Forcing binutils (>= 2.36) for both would be the easiest way to avoid this situation. cu Adrian
Bug#991079: gir1.2-budgie-1.0 has empty Depends
Great, thanks - understand now. Cheers.
On Tue, 13 Jul 2021 at 20:28, Adrian Bunk wrote:
>
> On Tue, Jul 13, 2021 at 08:05:07PM +0100, David Mohammed wrote:
> > Please can you clarify - the contents of the gir package is as follows
> > and I can use it via python
> >...
>
> Package: gir1.2-budgie-1.0
> Source: budgie-desktop
> Version: 10.5.2-3
> Installed-Size: 44
> Maintainer: David Mohammed
> Architecture: amd64
> Replaces: gir1.2-budgie-desktop-1.0 (<< 10.3.2)
> Breaks: gir1.2-budgie-desktop-1.0 (<< 10.3.2)
> Description-en: GNOME introspection library for budgie-desktop
> ...
>
> There are no package dependencies.
>
> > On Tue, 13 Jul 2021 at 19:09, Adrian Bunk wrote:
> > >...
> > > ${gir:Depends} needs "dh --with gir" in debian/rules.
>
> After this change I get
> Depends: gir1.2-glib-2.0, gir1.2-gtk-3.0 (>= 3.24.0), gir1.2-peas-1.0,
> libbudgie-plugin0 (>= 10.5.2)
>
>
> cu
> Adrian
Bug#991079: gir1.2-budgie-1.0 has empty Depends
On Tue, Jul 13, 2021 at 08:05:07PM +0100, David Mohammed wrote:
> Please can you clarify - the contents of the gir package is as follows
> and I can use it via python
>...
Package: gir1.2-budgie-1.0
Source: budgie-desktop
Version: 10.5.2-3
Installed-Size: 44
Maintainer: David Mohammed
Architecture: amd64
Replaces: gir1.2-budgie-desktop-1.0 (<< 10.3.2)
Breaks: gir1.2-budgie-desktop-1.0 (<< 10.3.2)
Description-en: GNOME introspection library for budgie-desktop
...
There are no package dependencies.
> On Tue, 13 Jul 2021 at 19:09, Adrian Bunk wrote:
> >...
> > ${gir:Depends} needs "dh --with gir" in debian/rules.
After this change I get
Depends: gir1.2-glib-2.0, gir1.2-gtk-3.0 (>= 3.24.0), gir1.2-peas-1.0,
libbudgie-plugin0 (>= 10.5.2)
cu
Adrian
Bug#991088: gir1.2-rda-1.0 has empty Depends
Package: gir1.2-rda-1.0
Version: 0.0.5-1
Severity: serious
${gir:Depends} needs "dh --with gir" in debian/rules.
Bug#991087: gir1.2-inputpad-1.0 has empty Depends
Package: gir1.2-inputpad-1.0
Version: 1.0.3-4
Severity: serious
${gir:Depends} needs "dh --with gir" in debian/rules.
Bug#991086: gir1.2-gtklayershell-0.1 has empty Depends
Package: gir1.2-gtklayershell-0.1
Version: 0.5.2-1
Severity: serious
${gir:Depends} needs "dh --with gir" in debian/rules.
Bug#991079: gir1.2-budgie-1.0 has empty Depends
Please can you clarify - the contents of the gir package is as follows
and I can use it via python
dpkg-deb -c /home/dad/Downloads/gir1.2-budgie-1.0_10.5-1_amd64.deb
drwxr-xr-x root/root 0 2019-04-15 10:11 ./
drwxr-xr-x root/root 0 2019-04-15 10:11 ./usr/
drwxr-xr-x root/root 0 2019-04-15 10:11 ./usr/lib/
drwxr-xr-x root/root 0 2019-04-15 10:11 ./usr/lib/x86_64-linux-gnu/
drwxr-xr-x root/root 0 2019-04-15 10:11
./usr/lib/x86_64-linux-gnu/girepository-1.0/
-rw-r--r-- root/root 6824 2019-04-15 10:11
./usr/lib/x86_64-linux-gnu/girepository-1.0/Budgie-1.0.typelib
drwxr-xr-x root/root 0 2019-04-15 10:11 ./usr/share/
drwxr-xr-x root/root 0 2019-04-15 10:11 ./usr/share/doc/
drwxr-xr-x root/root 0 2019-04-15 10:11
./usr/share/doc/gir1.2-budgie-1.0/
-rw-r--r-- root/root 7027 2019-04-15 10:11
./usr/share/doc/gir1.2-budgie-1.0/changelog.Debian.gz
-rw-r--r-- root/root 5636 2019-04-15 10:11
./usr/share/doc/gir1.2-budgie-1.0/changelog.gz
-rw-r--r-- root/root 6148 2019-04-15 10:11
./usr/share/doc/gir1.2-budgie-1.0/copyright
On Tue, 13 Jul 2021 at 19:09, Adrian Bunk wrote:
>
> Package: gir1.2-budgie-1.0
> Version: 10.5-1
> Severity: serious
>
> ${gir:Depends} needs "dh --with gir" in debian/rules.
Bug#991082: gir1.2-gtd-1.0 has empty Depends
Package: gir1.2-gtd-1.0
Version: 3.28.1-2
Severity: serious
${gir:Depends} needs "dh --with gir" in debian/rules.
Something might still go wrong after that,
when trying it did not generate dependencies
on any library:
Depends: gir1.2-glib-2.0, gir1.2-gtk-3.0 (>= 3.19.5)
Bug#991081: gir1.2-diodon-1.0 lacks dependencies
Package: gir1.2-diodon-1.0
Version: 1.8.0-1
Severity: serious
${gir:Depends} needs "dh --with gir" in debian/rules.
The manual dependency on gir1.2-glib-2.0 is no longer necessary
when this is fixed.
Something still seems to go wrong afterwards,
when trying it did not generate a dependency on libdiodon0.
Bug#991079: gir1.2-budgie-1.0 has empty Depends
Package: gir1.2-budgie-1.0
Version: 10.5-1
Severity: serious
${gir:Depends} needs "dh --with gir" in debian/rules.
Bug#991078: gir1.2-aperture-0 has empty Depends
Package: gir1.2-aperture-0
Version: 0.1.0+git20200908-1
Severity: serious
${gir:Depends} needs "dh --with gir" in debian/rules.
Processed: dask.distributed: diff for NMU version 2021.01.0+ds.1-2.1
Processing control commands: > tags 987816 + pending Bug #987816 [src:dask.distributed] dask.distributed: FTBFS due to a build-time test failure Ignoring request to alter tags of bug #987816 to the same tags previously set > tags 988675 + patch Bug #988675 [python-distributed-doc] python-distributed-doc: broken symlink: /usr/share/doc/python-distributed-doc/html/_static/js/html5shiv.min.js -> /sphinx_rtd_theme/static/js/html5shiv.min.js Ignoring request to alter tags of bug #988675 to the same tags previously set > tags 988675 + pending Bug #988675 [python-distributed-doc] python-distributed-doc: broken symlink: /usr/share/doc/python-distributed-doc/html/_static/js/html5shiv.min.js -> /sphinx_rtd_theme/static/js/html5shiv.min.js Ignoring request to alter tags of bug #988675 to the same tags previously set -- 987816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987816 988675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: dask.distributed: diff for NMU version 2021.01.0+ds.1-2.1
Processing control commands: > tags 987816 + pending Bug #987816 [src:dask.distributed] dask.distributed: FTBFS due to a build-time test failure Added tag(s) pending. > tags 988675 + patch Bug #988675 [python-distributed-doc] python-distributed-doc: broken symlink: /usr/share/doc/python-distributed-doc/html/_static/js/html5shiv.min.js -> /sphinx_rtd_theme/static/js/html5shiv.min.js Added tag(s) patch. > tags 988675 + pending Bug #988675 [python-distributed-doc] python-distributed-doc: broken symlink: /usr/share/doc/python-distributed-doc/html/_static/js/html5shiv.min.js -> /sphinx_rtd_theme/static/js/html5shiv.min.js Added tag(s) pending. -- 987816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987816 988675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988675 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#987816: dask.distributed: diff for NMU version 2021.01.0+ds.1-2.1
Control: tags 987816 + pending Control: tags 988675 + patch Control: tags 988675 + pending Dear maintainer, I've prepared an NMU for dask.distributed (versioned as 2021.01.0+ds.1-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru dask.distributed-2021.01.0+ds.1/debian/changelog dask.distributed-2021.01.0+ds.1/debian/changelog --- dask.distributed-2021.01.0+ds.1/debian/changelog 2021-02-01 22:08:19.0 +0200 +++ dask.distributed-2021.01.0+ds.1/debian/changelog 2021-07-13 19:19:56.0 +0300 @@ -1,3 +1,13 @@ +dask.distributed (2021.01.0+ds.1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Backport upstream fix removing tests that fail under some +circumstances. (Closes: #987816) + * python-distributed-doc: Fix broken symlink to html5shiv.min.js, +dh_link needs absolute paths. (Closes: #988675) + + -- Adrian Bunk Tue, 13 Jul 2021 19:19:56 +0300 + dask.distributed (2021.01.0+ds.1-2) unstable; urgency=medium * Add fall-back-to-ipv6-localhost.patch to work around ipv6 networking diff -Nru dask.distributed-2021.01.0+ds.1/debian/patches/0001-Remove-tests-for-process_time-and-thread_time-4895.patch dask.distributed-2021.01.0+ds.1/debian/patches/0001-Remove-tests-for-process_time-and-thread_time-4895.patch --- dask.distributed-2021.01.0+ds.1/debian/patches/0001-Remove-tests-for-process_time-and-thread_time-4895.patch 1970-01-01 02:00:00.0 +0200 +++ dask.distributed-2021.01.0+ds.1/debian/patches/0001-Remove-tests-for-process_time-and-thread_time-4895.patch 2021-07-13 19:19:56.0 +0300 @@ -0,0 +1,73 @@ +From 668f3f1d38c27277448af6f5aa88741cd1d33f3b Mon Sep 17 00:00:00 2001 +From: James Bourbeau +Date: Wed, 9 Jun 2021 08:57:53 -0500 +Subject: Remove tests for `process_time` and `thread_time` (#4895) + +--- + distributed/tests/test_metrics.py | 46 --- + 1 file changed, 46 deletions(-) + +diff --git a/distributed/tests/test_metrics.py b/distributed/tests/test_metrics.py +index 3a27e638..58c33266 100644 +--- a/distributed/tests/test_metrics.py b/distributed/tests/test_metrics.py +@@ -1,9 +1,6 @@ +-import sys +-import threading + import time + + from distributed import metrics +-from distributed.utils_test import run_for + + + def test_wall_clock(): +@@ -18,46 +15,3 @@ def test_wall_clock(): + assert any(lambda d: 0.0 < d < 0.0001 for d in deltas), deltas + # Close to time.time() + assert t - 0.5 < samples[0] < t + 0.5 +- +- +-def test_process_time(): +-start = metrics.process_time() +-run_for(0.05) +-dt = metrics.process_time() - start +-assert 0.03 <= dt <= 0.2 +- +-# All threads counted +-t = threading.Thread(target=run_for, args=(0.1,)) +-start = metrics.process_time() +-t.start() +-t.join() +-dt = metrics.process_time() - start +-assert dt >= 0.05 +- +-# Sleep time not counted +-start = metrics.process_time() +-time.sleep(0.1) +-dt = metrics.process_time() - start +-assert dt <= 0.05 +- +- +-def test_thread_time(): +-start = metrics.thread_time() +-run_for(0.05) +-dt = metrics.thread_time() - start +-assert 0.03 <= dt <= 0.2 +- +-# Sleep time not counted +-start = metrics.thread_time() +-time.sleep(0.1) +-dt = metrics.thread_time() - start +-assert dt <= 0.05 +- +-if sys.platform == "linux": +-# Always per-thread on Linux +-t = threading.Thread(target=run_for, args=(0.1,)) +-start = metrics.thread_time() +-t.start() +-t.join() +-dt = metrics.thread_time() - start +-assert dt <= 0.05 +-- +2.20.1 + diff -Nru dask.distributed-2021.01.0+ds.1/debian/patches/series dask.distributed-2021.01.0+ds.1/debian/patches/series --- dask.distributed-2021.01.0+ds.1/debian/patches/series 2021-02-01 21:51:15.0 +0200 +++ dask.distributed-2021.01.0+ds.1/debian/patches/series 2021-07-13 19:19:56.0 +0300 @@ -7,3 +7,4 @@ use-local-favicon.patch mark-tests-require-installation.patch fall-back-to-ipv6-localhost.patch +0001-Remove-tests-for-process_time-and-thread_time-4895.patch diff -Nru dask.distributed-2021.01.0+ds.1/debian/python-distributed-doc.links dask.distributed-2021.01.0+ds.1/debian/python-distributed-doc.links --- dask.distributed-2021.01.0+ds.1/debian/python-distributed-doc.links 2021-01-17 05:54:55.0 +0200 +++ dask.distributed-2021.01.0+ds.1/debian/python-distributed-doc.links 2021-07-13 19:19:56.0 +0300 @@ -1 +1 @@ -../../../../sphinx_rtd_theme/static/js/html5shiv.min.js usr/share/doc/python-distributed-doc/html/_static/js/html5shiv.min.js +/usr/share/sphinx_rtd_theme/static/js/html5shiv.min.js usr/share/doc/python-distributed-doc/html/_static/js/html5shiv.min.js
Bug#990808: unblock: ganglia-modules-linux/1.3.4-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package ganglia-modules-linux [ Reason ] Configs path are wrong. Users must manually fix the configuration files for all modules contained in this package. Upstream uses "/usr/lib/ganglia" as path for all cases. Debian package support multiarch, so paths must be adapted for each architecture, for example "/usr/lib/x86_64-linux-gnu/ganglia" for amd64. Modules are properly allocated at install time but the values in config files are wrong. This fix is done via dpkg-architecture DEB_HOST_MULTIARCH in d/rules file. There is no other change as you can check in the diff. [ Other info ] I still not uploaded the package to sid waiting for aproval. unblock ganglia-modules-linux/1.3.4-5 diff -Nru ganglia-modules-linux-1.3.6/debian/changelog ganglia-modules-linux-1.3.6/debian/changelog --- ganglia-modules-linux-1.3.6/debian/changelog 2021-01-17 11:43:42.0 +0100 +++ ganglia-modules-linux-1.3.6/debian/changelog 2021-07-12 00:22:06.0 +0200 @@ -1,3 +1,9 @@ +ganglia-modules-linux (1.3.6-5) unstable; urgency=medium + + * Fix multiarch support in *.conf files (Closes: #990808). + + -- Marcos Fouces Mon, 12 Jul 2021 00:22:06 +0200 + ganglia-modules-linux (1.3.6-4) unstable; urgency=medium * Remove version requirement for libganglia1-dev as 3.3.5 is older than diff -Nru ganglia-modules-linux-1.3.6/debian/rules ganglia-modules-linux-1.3.6/debian/rules --- ganglia-modules-linux-1.3.6/debian/rules 2021-01-17 11:43:42.0 +0100 +++ ganglia-modules-linux-1.3.6/debian/rules 2021-07-12 00:22:06.0 +0200 @@ -2,13 +2,20 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all export DEB_CFLAGS_MAINT_APPEND = $(shell apr-1-config --cflags --cppflags --includes) -I/usr/include/tirpc/ export DEB_LDFLAGS_MAINT_APPEND = -ltirpc +DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) %: dh $@ -override_dh_auto_install: +override_dh_auto_install: debian/ganglia-modules-linux/etc/ganglia/conf.d/mod_fs.conf-sample debian/ganglia-modules-linux/etc/ganglia/conf.d/mod_io.conf debian/ganglia-modules-linux/etc/ganglia/conf.d/mod_multicpu.conf-sample dh_auto_install - cp conf.d/mod_fs.conf debian/ganglia-modules-linux/etc/ganglia/conf.d/mod_fs.conf-sample - cp conf.d/mod_io.conf debian/ganglia-modules-linux/etc/ganglia/conf.d - cp conf.d/mod_multicpu.conf debian/ganglia-modules-linux/etc/ganglia/conf.d/mod_multicpu.conf-sample find debian/ \( -name "*.la" -o -name "*.a" -o -name "modmulticpu.so" \) -delete + +debian/ganglia-modules-linux/etc/ganglia/conf.d/mod_fs.conf-sample: conf.d/mod_fs.conf + sed 's/usr\/lib\/ganglia/usr\/lib\/$(DEB_HOST_MULTIARCH)\/ganglia/g' $< > $@ + +debian/ganglia-modules-linux/etc/ganglia/conf.d/mod_io.conf: conf.d/mod_io.conf + sed 's/usr\/lib\/ganglia/usr\/lib\/$(DEB_HOST_MULTIARCH)\/ganglia/g' $< > $@ + +debian/ganglia-modules-linux/etc/ganglia/conf.d/mod_multicpu.conf-sample: conf.d/mod_multicpu.conf + sed 's/usr\/lib\/ganglia/usr\/lib\/$(DEB_HOST_MULTIARCH)\/ganglia/g' $< > $@
Bug#991044: marked as done (gcc-10-cross: Incorrect Source: version generated for binary packages in binNMUs)
Your message dated Tue, 13 Jul 2021 17:01:28 +0200 with message-id <9c7747e5-2a0b-4141-cf61-3ff0c9b52...@debian.org> and subject line Re: Incorrect Source: version generated for binary packages in binNMUs has caused the Debian Bug report #991044, regarding gcc-10-cross: Incorrect Source: version generated for binary packages in binNMUs 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.) -- 991044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-9-cross Version: 25 Severity: serious Tags: ftbfs Control: clone -1 -2 -3 -4 Control: reassign -2 gcc-9-cross-ports 23 Control: retitle -2 gcc-9-cross-ports: Incorrect Source: version generated for binary packages in binNMUs Control: reassign -3 gcc-10-cross 15 Control: retitle -3 gcc-10-cross: Incorrect Source: version generated for binary packages in binNMUs Control: reassign -4 gcc-10-cross-ports 16 Control: retitle -4 gcc-10-cross-ports: Incorrect Source: version generated for binary packages in binNMUs https://buildd.debian.org/status/package.php?p=gcc-9-cross&suite=sid https://buildd.debian.org/status/package.php?p=gcc-9-cross-ports&suite=sid https://buildd.debian.org/status/package.php?p=gcc-10-cross-ports&suite=sid ... Package: cpp-9-aarch64-linux-gnu Source: gcc-9-cross (26+b1) Version: 9.4.0-1cross2 Architecture: amd64 ... --- End Message --- --- Begin Message --- sorry, but these are bogus reports. There's no requirement that a package has to be binNMUable. And for the GCC cross packages it's plainly wrong. Just building the compilers, and not the runtime libraries lets these diverge, ending up with a mix of packages built from two different compiler versions.--- End Message ---
Bug#991045: marked as done (gcc-10-cross-ports: Incorrect Source: version generated for binary packages in binNMUs)
Your message dated Tue, 13 Jul 2021 17:01:28 +0200 with message-id <9c7747e5-2a0b-4141-cf61-3ff0c9b52...@debian.org> and subject line Re: Incorrect Source: version generated for binary packages in binNMUs has caused the Debian Bug report #991045, regarding gcc-10-cross-ports: Incorrect Source: version generated for binary packages in binNMUs 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.) -- 991045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-9-cross Version: 25 Severity: serious Tags: ftbfs Control: clone -1 -2 -3 -4 Control: reassign -2 gcc-9-cross-ports 23 Control: retitle -2 gcc-9-cross-ports: Incorrect Source: version generated for binary packages in binNMUs Control: reassign -3 gcc-10-cross 15 Control: retitle -3 gcc-10-cross: Incorrect Source: version generated for binary packages in binNMUs Control: reassign -4 gcc-10-cross-ports 16 Control: retitle -4 gcc-10-cross-ports: Incorrect Source: version generated for binary packages in binNMUs https://buildd.debian.org/status/package.php?p=gcc-9-cross&suite=sid https://buildd.debian.org/status/package.php?p=gcc-9-cross-ports&suite=sid https://buildd.debian.org/status/package.php?p=gcc-10-cross-ports&suite=sid ... Package: cpp-9-aarch64-linux-gnu Source: gcc-9-cross (26+b1) Version: 9.4.0-1cross2 Architecture: amd64 ... --- End Message --- --- Begin Message --- sorry, but these are bogus reports. There's no requirement that a package has to be binNMUable. And for the GCC cross packages it's plainly wrong. Just building the compilers, and not the runtime libraries lets these diverge, ending up with a mix of packages built from two different compiler versions.--- End Message ---
Bug#991049: marked as done (gcc-10-cross-mipsen: Incorrect Source: version generated for binary packages in binNMUs)
Your message dated Tue, 13 Jul 2021 17:01:28 +0200 with message-id <9c7747e5-2a0b-4141-cf61-3ff0c9b52...@debian.org> and subject line Re: Incorrect Source: version generated for binary packages in binNMUs has caused the Debian Bug report #991049, regarding gcc-10-cross-mipsen: Incorrect Source: version generated for binary packages in binNMUs 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.) -- 991049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-9-cross Version: 25 Severity: serious Tags: ftbfs Control: clone -1 -2 -3 -4 Control: reassign -2 gcc-9-cross-ports 23 Control: retitle -2 gcc-9-cross-ports: Incorrect Source: version generated for binary packages in binNMUs Control: reassign -3 gcc-10-cross 15 Control: retitle -3 gcc-10-cross: Incorrect Source: version generated for binary packages in binNMUs Control: reassign -4 gcc-10-cross-ports 16 Control: retitle -4 gcc-10-cross-ports: Incorrect Source: version generated for binary packages in binNMUs https://buildd.debian.org/status/package.php?p=gcc-9-cross&suite=sid https://buildd.debian.org/status/package.php?p=gcc-9-cross-ports&suite=sid https://buildd.debian.org/status/package.php?p=gcc-10-cross-ports&suite=sid ... Package: cpp-9-aarch64-linux-gnu Source: gcc-9-cross (26+b1) Version: 9.4.0-1cross2 Architecture: amd64 ... --- End Message --- --- Begin Message --- sorry, but these are bogus reports. There's no requirement that a package has to be binNMUable. And for the GCC cross packages it's plainly wrong. Just building the compilers, and not the runtime libraries lets these diverge, ending up with a mix of packages built from two different compiler versions.--- End Message ---
Bug#991042: marked as done (gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs)
Your message dated Tue, 13 Jul 2021 17:01:28 +0200 with message-id <9c7747e5-2a0b-4141-cf61-3ff0c9b52...@debian.org> and subject line Re: Incorrect Source: version generated for binary packages in binNMUs has caused the Debian Bug report #991042, regarding gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs 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.) -- 991042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-9-cross Version: 25 Severity: serious Tags: ftbfs Control: clone -1 -2 -3 -4 Control: reassign -2 gcc-9-cross-ports 23 Control: retitle -2 gcc-9-cross-ports: Incorrect Source: version generated for binary packages in binNMUs Control: reassign -3 gcc-10-cross 15 Control: retitle -3 gcc-10-cross: Incorrect Source: version generated for binary packages in binNMUs Control: reassign -4 gcc-10-cross-ports 16 Control: retitle -4 gcc-10-cross-ports: Incorrect Source: version generated for binary packages in binNMUs https://buildd.debian.org/status/package.php?p=gcc-9-cross&suite=sid https://buildd.debian.org/status/package.php?p=gcc-9-cross-ports&suite=sid https://buildd.debian.org/status/package.php?p=gcc-10-cross-ports&suite=sid ... Package: cpp-9-aarch64-linux-gnu Source: gcc-9-cross (26+b1) Version: 9.4.0-1cross2 Architecture: amd64 ... --- End Message --- --- Begin Message --- sorry, but these are bogus reports. There's no requirement that a package has to be binNMUable. And for the GCC cross packages it's plainly wrong. Just building the compilers, and not the runtime libraries lets these diverge, ending up with a mix of packages built from two different compiler versions.--- End Message ---
Bug#991043: marked as done (gcc-9-cross-ports: Incorrect Source: version generated for binary packages in binNMUs)
Your message dated Tue, 13 Jul 2021 17:01:28 +0200 with message-id <9c7747e5-2a0b-4141-cf61-3ff0c9b52...@debian.org> and subject line Re: Incorrect Source: version generated for binary packages in binNMUs has caused the Debian Bug report #991043, regarding gcc-9-cross-ports: Incorrect Source: version generated for binary packages in binNMUs 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.) -- 991043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-9-cross Version: 25 Severity: serious Tags: ftbfs Control: clone -1 -2 -3 -4 Control: reassign -2 gcc-9-cross-ports 23 Control: retitle -2 gcc-9-cross-ports: Incorrect Source: version generated for binary packages in binNMUs Control: reassign -3 gcc-10-cross 15 Control: retitle -3 gcc-10-cross: Incorrect Source: version generated for binary packages in binNMUs Control: reassign -4 gcc-10-cross-ports 16 Control: retitle -4 gcc-10-cross-ports: Incorrect Source: version generated for binary packages in binNMUs https://buildd.debian.org/status/package.php?p=gcc-9-cross&suite=sid https://buildd.debian.org/status/package.php?p=gcc-9-cross-ports&suite=sid https://buildd.debian.org/status/package.php?p=gcc-10-cross-ports&suite=sid ... Package: cpp-9-aarch64-linux-gnu Source: gcc-9-cross (26+b1) Version: 9.4.0-1cross2 Architecture: amd64 ... --- End Message --- --- Begin Message --- sorry, but these are bogus reports. There's no requirement that a package has to be binNMUable. And for the GCC cross packages it's plainly wrong. Just building the compilers, and not the runtime libraries lets these diverge, ending up with a mix of packages built from two different compiler versions.--- End Message ---
Bug#991050: marked as done (gcc-11 should (build) depend on binutils (>= 2.36))
Your message dated Tue, 13 Jul 2021 16:51:40 +0200 with message-id and subject line Re: gcc-11 should (build) depend on binutils (>= 2.36) has caused the Debian Bug report #991050, regarding gcc-11 should (build) depend on binutils (>= 2.36) 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.) -- 991050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-11 Severity: serious Helmut Grohne reported on IRC: when gcc-11 is built with experimental binutils, the binary packages do not work with unstable binutils by passing unrecognized options http://gcc.gnu.org/gcc-11/changes.html confirms that gcc 11 might optionally use binutils 2.36 functionality. Please bump runtime and build dependencies on binutils to 2.36. --- End Message --- --- Begin Message --- No, 2.36 is not required. Perfectly fine to build with 2.35.2.--- End Message ---
Bug#991070: libvirtuoso5.5-cil lost all dependencies except cli-common in bullseye
Package: libvirtuoso5.5-cil Version: 7.2.5.1+dfsg-3 Severity: serious Package: libvirtuoso5.5-cil Source: virtuoso-opensource Version: 7.2.5.1+dfsg-3 Depends: cli-common (>= 0.5.1) Package: libvirtuoso5.5-cil Source: virtuoso-opensource (6.1.6+dfsg2-4) Version: 6.1.6+dfsg2-4+b2 Depends: cli-common (>= 0.5.1), libmono-corlib4.5-cil (>= 4.6.1.3), libmono-system-data4.0-cil (>= 4.6.1.3), libmono-system-drawing4.0-cil (>= 4.6.1.3), libmono-system-enterpriseservices4.0-cil (>= 1.0), libmono-system-xml4.0-cil (>= 4.6.1.3), libmono-system4.0-cil (>= 4.6.1.3)
Bug#991050: gcc-11 should (build) depend on binutils (>= 2.36)
No, 2.36 is not required. Perfectly fine to build with 2.35.2.
Bug#989603: Fwd: Re: Fwd: Bug#989603: ocsinventory-server: Does not start after install
On Tue, Jul 13, 2021 at 02:03:19PM +0200, Yadd wrote: > Le 13/07/2021 à 11:56, Adrian Bunk a écrit : > > On Sat, Jun 26, 2021 at 09:43:07PM +0200, Yadd wrote: > >> As-tu vu que le bug a été clos ? > >> ... > > > > ocsinventory-server needs an unblock request for getting this fix > > into bullseye. > > > > cu > > Adrian > > Yes but (filtered) debdiff is big... Plan B would be uploading this fix as 2.8.1+really2.8-1. cu Adrian
Processed: found 991046 in 9.0.43-1, tagging 991046, tagging 991041, found 991041 in 1.20-1 ..., tagging 991040 ...
Processing commands for cont...@bugs.debian.org: > found 991046 9.0.43-1 Bug #991046 [src:tomcat9] tomcat9: CVE-2021-33037 CVE-2021-30640 CVE-2021-30639 Marked as found in versions tomcat9/9.0.43-1. > tags 991046 + upstream Bug #991046 [src:tomcat9] tomcat9: CVE-2021-33037 CVE-2021-30640 CVE-2021-30639 Added tag(s) upstream. > tags 991041 + upstream Bug #991041 [src:libcommons-compress-java] libcommons-compress-java: CVE-2021-36090 CVE-2021-35517 CVE-2021-35516 CVE-2021-35515 Added tag(s) upstream. > found 991041 1.20-1 Bug #991041 [src:libcommons-compress-java] libcommons-compress-java: CVE-2021-36090 CVE-2021-35517 CVE-2021-35516 CVE-2021-35515 Marked as found in versions libcommons-compress-java/1.20-1. > found 991041 1.18-2+deb10u1 Bug #991041 [src:libcommons-compress-java] libcommons-compress-java: CVE-2021-36090 CVE-2021-35517 CVE-2021-35516 CVE-2021-35515 Marked as found in versions libcommons-compress-java/1.18-2+deb10u1. > found 991041 1.18-2 Bug #991041 [src:libcommons-compress-java] libcommons-compress-java: CVE-2021-36090 CVE-2021-35517 CVE-2021-35516 CVE-2021-35515 Marked as found in versions libcommons-compress-java/1.18-2. > found 991041 1.13-1 Bug #991041 [src:libcommons-compress-java] libcommons-compress-java: CVE-2021-36090 CVE-2021-35517 CVE-2021-35516 CVE-2021-35515 Marked as found in versions libcommons-compress-java/1.13-1. > tags 991040 + upstream Bug #991040 [varnish] Varnish VSV7 Added tag(s) upstream. > found 991040 6.5.1-1 Bug #991040 [varnish] Varnish VSV7 Marked as found in versions varnish/6.5.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 991040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991040 991041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991041 991046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991068: xnee FTBFS with imagemagick with the #987504 change
Source: xnee Version: 3.19-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/xnee.html ... creating PNG /usr/bin/convert -density 144x144 xndetail.eps xndetail.png convert: attempt to perform an operation not allowed by the security policy `PS' @ error/constitute.c/IsCoderAuthorized/408. convert: no images defined `xndetail.png' @ error/convert.c/ConvertImageCommand/3258. make[3]: *** [Makefile:904: xndetail.png] Error 1 See #987504 for background.
Bug#991067: x4d-icons FTBFS with imagemagick with the #987504 change
Source: x4d-icons Version: 1.2-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/x4d-icons.html ... dh_auto_build make -j1 make[1]: Entering directory '/build/x4d-icons-1.2' TZ=UTC faketime -f '2014-05-03 00:00:00' ./generate.sh convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderA
Bug#991066: vlfeat FTBFS with imagemagick with the #987504 change
Source: vlfeat Version: 0.9.21+dfsg0-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/vlfeat.html ... CONVERT doc/figures/cell-bins.png "convert" -units PixelsPerInch -density 95 -resample 95 -trim "doc/build/figures/cell-bins.pdf" "doc/figures/cell-bins.png" convert-im6.q16: attempt to perform an operation not allowed by the security policy `PDF' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: no images defined `doc/figures/cell-bins.png' @ error/convert.c/ConvertImageCommand/3258. make[2]: *** [make/doc.mak:213: doc/figures/cell-bins.png] Error 1 See #987504 for background. The Ubuntu diff (linked from tracker.debian.org) seems to contain a fix.
Bug#991053: ftgl FTBFS with imagemagick with the #987504 change
On Tue, Jul 13, 2021 at 03:50:38PM +0300, Adrian Bunk wrote: > Source: ftgl > Version: 2.4.0-2 > Severity: serious > Tags: ftbfs > > https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/ftgl.html > > ... > Making all in docs > make[4]: Entering directory '/build/ftgl-2.4.0/docs' > for i in images/logo.png images/metrics.png images/rasterfont.png > images/vectorfont.png images/texturefont.png; do convert $i $i.eps; done > convert-im6.q16: attempt to perform an operation not allowed by the security > policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. > convert-im6.q16: attempt to perform an operation not allowed by the security > policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. > convert-im6.q16: attempt to perform an operation not allowed by the security > policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. > convert-im6.q16: attempt to perform an operation not allowed by the security > policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. > convert-im6.q16: attempt to perform an operation not allowed by the security > policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. > make[4]: *** [Makefile:604: stamp-eps] Error 1 > > > See #987504 for background. The Ubuntu diff (linked from tracker.debian.org) seems to contain a fix. cu Adrian
Bug#991064: therion FTBFS with imagemagick with the #987504 change
Source: therion
Version: 5.4.3ds1-6
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/therion.html
...
Converting images:
../samples/basics/rabbit-plan.pdf
error at 300 dpi processing ../samples/basics/rabbit-plan.pdf
error at 270 dpi processing ../samples/basics/rabbit-plan.pdf
error at 243 dpi processing ../samples/basics/rabbit-plan.pdf
error at 218 dpi processing ../samples/basics/rabbit-plan.pdf
error at 196 dpi processing ../samples/basics/rabbit-plan.pdf
error at 176 dpi processing ../samples/basics/rabbit-plan.pdf
error at 158 dpi processing ../samples/basics/rabbit-plan.pdf
error at 142 dpi processing ../samples/basics/rabbit-plan.pdf
error at 127 dpi processing ../samples/basics/rabbit-plan.pdf
error at 114 dpi processing ../samples/basics/rabbit-plan.pdf
error at 102 dpi processing ../samples/basics/rabbit-plan.pdf
error at 91 dpi processing ../samples/basics/rabbit-plan.pdf
error at 81 dpi processing ../samples/basics/rabbit-plan.pdf
error at 72 dpi processing ../samples/basics/rabbit-plan.pdf
error at 64 dpi processing ../samples/basics/rabbit-plan.pdf
error at 57 dpi processing ../samples/basics/rabbit-plan.pdf
error at 51 dpi processing ../samples/basics/rabbit-plan.pdf
error at 45 dpi processing ../samples/basics/rabbit-plan.pdf
error at 40 dpi processing ../samples/basics/rabbit-plan.pdf
error at 36 dpi processing ../samples/basics/rabbit-plan.pdf
error at 32 dpi processing ../samples/basics/rabbit-plan.pdf
error at 28 dpi processing ../samples/basics/rabbit-plan.pdf
error at 25 dpi processing ../samples/basics/rabbit-plan.pdf
error at 22 dpi processing ../samples/basics/rabbit-plan.pdf
error at 19 dpi processing ../samples/basics/rabbit-plan.pdf
error at 17 dpi processing ../samples/basics/rabbit-plan.pdf
error at 15 dpi processing ../samples/basics/rabbit-plan.pdf
error at 13 dpi processing ../samples/basics/rabbit-plan.pdf
error at 11 dpi processing ../samples/basics/rabbit-plan.pdf
convert-im6.q16: unable to open image `../samples.doc/tmp.png': No such file or
directory @ error/blob.c/OpenBlob/2874.
convert-im6.q16: no images defined `../samples.doc/00.png' @
error/convert.c/ConvertImageCommand/3258.
while executing
"exec "convert" -colorspace RGB -resize 419x419 ../samples.doc/tmp.png
../samples.doc/00.png"
("eval" body line 1)
invoked from within
"eval "exec \"$convpath\" -colorspace RGB -resize 419x419 $outd/tmp.png
$outd/$iiimg""
(procedure "create_docs" line 154)
invoked from within
"create_docs"
invoked from within
"if {([llength $argv] > 1) && [regexp -nocase {^clean$} [lindex $argv 1]]} {
scan_files ""
scan_lists
clean_files
} else {
if {[llength $argv] ..."
(file "samples.tcl" line 523)
make[3]: *** [Makefile:15: all] Error 1
See #987504 for background.
Processed: Re: Bug#986686: missing b-d netpbm?
Processing control commands: > severity -1 serious Bug #986686 [src:texworks-manual] missing b-d netpbm? Severity set to 'serious' from 'minor' > tags -1 ftbfs Bug #986686 [src:texworks-manual] missing b-d netpbm? Added tag(s) ftbfs. > found -1 20150506-2 Bug #986686 [src:texworks-manual] missing b-d netpbm? Marked as found in versions texworks-manual/20150506-2. -- 986686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#962439: sctk: use pdftoppm instead of convert in debian/replacement_files/Makefile
Processing control commands: > severity -1 serious Bug #962439 [src:sctk] sctk: use pdftoppm instead of convert in debian/replacement_files/Makefile Severity set to 'serious' from 'normal' > tags -1 patch Bug #962439 [src:sctk] sctk: use pdftoppm instead of convert in debian/replacement_files/Makefile Ignoring request to alter tags of bug #962439 to the same tags previously set -- 962439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991061: ns3 FTBFS with imagemagick with the #987504 change
Source: ns3 Version: 3.29+dfsg-3 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/ns3.html ... convert lena-dual-stripe.eps convert-im6.q16: attempt to perform an operation not allowed by the security policy `PS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: no images defined `source-temp/figures/lena-dual-stripe.png' @ error/convert.c/ConvertImageCommand/3258. make[2]: *** [Makefile:475: source-temp/figures/lena-dual-stripe.png] Error 1 See #987504 for background.
Bug#991060: mlpost FTBFS with imagemagick with the #987504 change
Source: mlpost Version: 0.8.1-8 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/mlpost.html ... convert img/circle.ps img/circle.png + convert img/circle.ps img/circle.png convert-im6.q16: attempt to perform an operation not allowed by the security policy `PS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: no images defined `img/circle.png' @ error/convert.c/ConvertImageCommand/3258. Command exited with code 1. make[2]: *** [ocamlbuild.Makefile:199: doc] Error 10 See #987504 for background.
Processed: kannel FTBFS with imagemagick with the #987504 change
Processing control commands: > close -1 1.4.5-7 Bug #991058 [src:kannel] kannel FTBFS with imagemagick with the #987504 change Marked as fixed in versions kannel/1.4.5-7. Bug #991058 [src:kannel] kannel FTBFS with imagemagick with the #987504 change Marked Bug as done -- 991058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991058 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991058: kannel FTBFS with imagemagick with the #987504 change
Source: kannel Version: 1.4.5-2 Severity: serious Tags: ftbfs Control: close -1 1.4.5-7 https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/kannel.html ... /usr/bin/convert doc/alligata/12-5.png doc/alligata/12-5.ps convert: attempt to perform an operation not allowed by the security policy `PS' @ error/constitute.c/IsCoderAuthorized/408. make[1]: *** [Makefile:217: doc/alligata/12-5.ps] Error 1
Bug#991057: gri FTBFS with imagemagick with the #987504 change
Source: gri Version: 2.12.26-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/gri.html ... cd examples; make pdf make[2]: Entering directory '/build/gri-2.12.26/doc/examples' convert FEM.ps FEM.pdf convert-im6.q16: attempt to perform an operation not allowed by the security policy `PS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: no images defined `FEM.pdf' @ error/convert.c/ConvertImageCommand/3258. make[2]: *** [Makefile:489: FEM.pdf] Error 1 See #987504 for background.
Bug#991056: foxtrotgps FTBFS with imagemagick with the #987504 change
Source: foxtrotgps Version: 1.2.1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/foxtrotgps.html ... Making all in doc make[3]: Entering directory '/build/foxtrotgps-1.2.1/doc' convert foxtrotgps-logo.png foxtrotgps-logo.eps convert screenshots/main-window.png screenshots/main-window.eps convert screenshots/map-download.png screenshots/map-download.eps convert screenshots/tracking.png screenshots/tracking.eps convert screenshots/found-route.png screenshots/found-route.eps convert screenshots/get-route.png screenshots/get-route.eps convert screenshots/route-planning.png screenshots/route-planning.eps convert cc-by-sa.png cc-by-sa.eps convert cc-by-sa_small.png cc-by-sa_small.eps make -C ../src foxtrotgps make[4]: Entering directory '/build/foxtrotgps-1.2.1/src' make[4]: 'foxtrotgps' is up to date. make[4]: Leaving directory '/build/foxtrotgps-1.2.1/src' help2man sh --output=foxtrotgps.1.in \ --help-option="-c \"../src/foxtrotgps \ --help | sed -e '1N;2s/\\n//'\"" \ --version-option="-c \"../src/foxtrotgps\ --version\"" \ --info-page=foxtrotgps \ --include=./foxtrotgps.h2m.in convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. make[3]: *** [Makefile:931: screenshots/map-download.eps] Error 1 See #987504 for background.
Processed: reassign 991049 to src:gcc-10-cross-mipsen
Processing commands for cont...@bugs.debian.org: > reassign 991049 src:gcc-10-cross-mipsen 3+c5 Bug #991049 [src:gcc-9-cross] gcc-10-cross-mipsen: Incorrect Source: version generated for binary packages in binNMUs Bug reassigned from package 'src:gcc-9-cross' to 'src:gcc-10-cross-mipsen'. No longer marked as found in versions gcc-9-cross/25. Ignoring request to alter fixed versions of bug #991049 to the same values previously set Bug #991049 [src:gcc-10-cross-mipsen] gcc-10-cross-mipsen: Incorrect Source: version generated for binary packages in binNMUs Marked as found in versions gcc-10-cross-mipsen/3+c5. > thanks Stopping processing here. Please contact me if you need assistance. -- 991049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991053: ftgl FTBFS with imagemagick with the #987504 change
Source: ftgl Version: 2.4.0-2 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/ftgl.html ... Making all in docs make[4]: Entering directory '/build/ftgl-2.4.0/docs' for i in images/logo.png images/metrics.png images/rasterfont.png images/vectorfont.png images/texturefont.png; do convert $i $i.eps; done convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. convert-im6.q16: attempt to perform an operation not allowed by the security policy `EPS' @ error/constitute.c/IsCoderAuthorized/408. make[4]: *** [Makefile:604: stamp-eps] Error 1 See #987504 for background.
Bug#991050: gcc-11 should (build) depend on binutils (>= 2.36)
Source: gcc-11 Severity: serious Helmut Grohne reported on IRC: when gcc-11 is built with experimental binutils, the binary packages do not work with unstable binutils by passing unrecognized options http://gcc.gnu.org/gcc-11/changes.html confirms that gcc 11 might optionally use binutils 2.36 functionality. Please bump runtime and build dependencies on binutils to 2.36.
Bug#990906: marked as done (xarchiver Deleting Files Outside of Archive)
Your message dated Tue, 13 Jul 2021 12:33:44 + with message-id and subject line Bug#990906: fixed in xarchiver 1:0.5.4.17-2 has caused the Debian Bug report #990906, regarding xarchiver Deleting Files Outside of Archive 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.) -- 990906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xarchiver Version: 1:0.5.4.14-1 Severity: critical Justification: causes serious data loss Dear Maintainer, Subject: xarchiver Deleting Files Outside of Archive The deleted files are linked to (ln -s) from within the archive (tar.gz), but reside outside of the archive. These external files get deleted if one double clicks on the link line within xarchiver and the file resides on an ntfs disk. # # The behaviour can be repeated as follows cd /home/david/ mkdir Example # Write a txt file to within Example echo "file red" > Example/red.txt # Utilise much spare disk space on ntfs drive # it needs to be ntfs cd /mnt/win7/david/ mkdir MoreColours echo "file green" > MoreColours/green.txt echo "file blue" > MoreColours/blue.txt # Make symbolic link to MoreColours #from within dir Example cd /home/david/Example ln -s -T /mnt/win7/david/MoreColours MoreColours # Make a tape archive of Example cd /home/david/ tar -czvf example.tar.gz Example # Open using xarchiver, and # note that MoreColours points to correct location xarchiver example.tar.gz thunar /mnt/win7/david/MoreColours # Now double click on this line in xarchiver AND # watch the files in MoreColours in thunar above # at the same time. They get REMOVED. # I would have expected a default action of double # clicking to be something like opening thunar above. # An error message pops up: 'Failed to open "/tmp/xa-43Y950/MoreColours". Error when getting information for the file "/tmp/xa-43Y950/MoreColours": No such file or directory.' # Goto the /tmp dir named in the Error Pop-up cd /tmp/xa-43Y950/ ls -l -rwxrwxrwx 1 david david10 Jul 10 13:14 blue.txt -rwxrwxrwx 1 david david11 Jul 10 13:14 green.txt drwx-- 3 david david 4096 Jul 10 13:32 xa-tmp.0XTI60 -rw-r--r-- 1 david david 10240 Jul 10 13:30 xa-tmp.decompressed # The files blue.txt and green.txt have been MOVED to /tmp/xa-43Y950/. xarchiver should not have the permission to move/delete files that are not within the archive specified by the user. When one closes xarchiver the /tmp dir is deleted along with all of ones files, 2.7Gb in my case. I lost them before seeing what was happening. There is a conflict with ntfs, the above does not happen if the linked directory is on the local ext4 disk. Is this related to the following bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862593 Possibly some escaped characters with ntfs mounts are not being dealt with properly? The ntfs disk mount is configured in /etc/fstab: UUID=id.here /mnt/win7 ntfs user,auto,uid=a.number,gid=a.number 0 0 Regards David Harte -- System Information: Debian Release: 10.10 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ.utf8, LC_CTYPE=en_NZ.utf8 (charmap=UTF-8), LANGUAGE=en_NZ:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages xarchiver depends on: ii libc6 2.28-10 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-02.58.3-2+deb10u3 ii libgtk-3-0 3.24.5-1 Versions of packages xarchiver recommends: ii bzip2 1.0.6-9.2~deb10u1 ii p7zip-full 16.02+dfsg-6 ii unzip 6.0-23+deb10u2 ii xdg-utils 1.1.3-1+deb10u1 ii xz-utils5.2.4-1 Versions of packages xarchiver suggests: pn arj ii binutils 2.31.1-16 ii cpio 2.12+dfsg-9 pn lhasa pn liblz4-tool pn lrzip pn lzip pn lzop pn ncompress pn rar pn unar ii zip 3.0-11+b1 pn zstd -- no debconf information --- End Message --- --- Begin Message --- Source: xarchiver Source-Version: 1:0.5.4.17-2 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of xarchiver, 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 t
Processed (with 1 error): Also in gcc-10-cross-mipsen
Processing commands for cont...@bugs.debian.org: > clone 991042 -1 Bug #991042 [src:gcc-9-cross] gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs Bug 991042 cloned as bug 991049 > reassign -1 src:gcc-10-cross-mipsen gcc-10-cross-mipsen 3+c5 Unknown command or malformed arguments to command. > retitle -1 gcc-10-cross-mipsen: Incorrect Source: version generated for > binary packages in binNMUs Bug #991049 [src:gcc-9-cross] gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs Changed Bug title to 'gcc-10-cross-mipsen: Incorrect Source: version generated for binary packages in binNMUs' from 'gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs'. > thanks Stopping processing here. Please contact me if you need assistance. -- 991042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991042 991049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#990906: Xarchiver Debian bug 990906
Processing control commands: > tags -1 pending Bug #990906 [xarchiver] xarchiver Deleting Files Outside of Archive Added tag(s) pending. -- 990906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#990906: Xarchiver Debian bug 990906
Control: tags -1 pending Am Dienstag, dem 13.07.2021 um 13:41 +0200 schrieb Ingo Brückl: > Hi, > > I believe that the bug you reported is fixed in the current master of > xarchiver: > > https://github.com/ib/xarchiver/commit/949854e9a74489d8d977aac7a8428ecadd526ff1 Confirmed. Thanks for the patch Ingo! signature.asc Description: This is a digitally signed message part
Bug#991046: tomcat9: CVE-2021-33037 CVE-2021-30640 CVE-2021-30639
Source: tomcat9 X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for tomcat9. Commit references below, although it's worth considering to simply update to 9.0.47, given that stable-security upgraded to new Tomcat point releases before. CVE-2021-33037[0]: | Apache Tomcat 10.0.0-M1 to 10.0.6, 9.0.0.M1 to 9.0.46 and 8.5.0 to | 8.5.66 did not correctly parse the HTTP transfer-encoding request | header in some circumstances leading to the possibility to request | smuggling when used with a reverse proxy. Specifically: - Tomcat | incorrectly ignored the transfer encoding header if the client | declared it would only accept an HTTP/1.0 response; - Tomcat honoured | the identify encoding; and - Tomcat did not ensure that, if present, | the chunked encoding was the final encoding. https://github.com/apache/tomcat/commit/45d70a86a901cbd534f8f570bed2aec9f7f7b88e (9.0.47) https://github.com/apache/tomcat/commit/05f9e8b00f5d9251fcd3c95dcfd6cf84177f46c8 (9.0.47) https://github.com/apache/tomcat/commit/a2c3dc4c96168743ac0bab613709a5bbdaec41d0 (9.0.47) CVE-2021-30640[1]: | A vulnerability in the JNDI Realm of Apache Tomcat allows an attacker | to authenticate using variations of a valid user name and/or to bypass | some of the protection provided by the LockOut Realm. This issue | affects Apache Tomcat 10.0.0-M1 to 10.0.5; 9.0.0.M1 to 9.0.45; 8.5.0 | to 8.5.65. https://bz.apache.org/bugzilla/show_bug.cgi?id=65224 https://github.com/apache/tomcat/commit/c4df8d44a959a937d507d15e5b1ca35c3dbc41eb (9.0.46) https://github.com/apache/tomcat/commit/749f3cc192c68c34f2375509aea087be45fc4434 (9.0.46) https://github.com/apache/tomcat/commit/c6b6e1015ae44c936971b6bf8bce70987935b92e (9.0.46) https://github.com/apache/tomcat/commit/91ecdc61ce3420054c04114baaaf1c1e0cbd5d56 (9.0.46) https://github.com/apache/tomcat/commit/e50067486cf86564175ca0cfdcbf7d209c6df862 (9.0.46) https://github.com/apache/tomcat/commit/b5585a9e5d4fec020cc5ebadb82f899fae22bc43 (9.0.46) https://github.com/apache/tomcat/commit/329932012d3a9b95fde0b18618416e659ecffdc0 (9.0.46) https://github.com/apache/tomcat/commit/3ce84512ed8783577d9945df28da5a033465b945 (9.0.46) CVE-2021-30639[2]: | A vulnerability in Apache Tomcat allows an attacker to remotely | trigger a denial of service. An error introduced as part of a change | to improve error handling during non-blocking I/O meant that the error | flag associated with the Request object was not reset between | requests. This meant that once a non-blocking I/O error occurred, all | future requests handled by that request object would fail. Users were | able to trigger non-blocking I/O errors, e.g. by dropping a | connection, thereby creating the possibility of triggering a DoS. | Applications that do not use non-blocking I/O are not exposed to this | vulnerability. This issue affects Apache Tomcat 10.0.3 to 10.0.4; | 9.0.44; 8.5.64. https://bz.apache.org/bugzilla/show_bug.cgi?id=65203 https://github.com/apache/tomcat/commit/8ece47c4a9fb9349e8862c84358a4dd23c643a24 (9.0.45) If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-33037 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33037 [1] https://security-tracker.debian.org/tracker/CVE-2021-30640 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-30640 [2] https://security-tracker.debian.org/tracker/CVE-2021-30639 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-30639 Please adjust the affected versions in the BTS as needed.
Processed: gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs
Processing control commands: > clone -1 -2 -3 -4 Bug #991042 [src:gcc-9-cross] gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs Bug 991042 cloned as bugs 991043-991045 > reassign -2 gcc-9-cross-ports 23 Bug #991043 [src:gcc-9-cross] gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs Bug reassigned from package 'src:gcc-9-cross' to 'gcc-9-cross-ports'. No longer marked as found in versions gcc-9-cross/25. Ignoring request to alter fixed versions of bug #991043 to the same values previously set Bug #991043 [gcc-9-cross-ports] gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs There is no source info for the package 'gcc-9-cross-ports' at version '23' with architecture '' Unable to make a source version for version '23' Marked as found in versions 23. > retitle -2 gcc-9-cross-ports: Incorrect Source: version generated for binary > packages in binNMUs Bug #991043 [gcc-9-cross-ports] gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs Changed Bug title to 'gcc-9-cross-ports: Incorrect Source: version generated for binary packages in binNMUs' from 'gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs'. > reassign -3 gcc-10-cross 15 Bug #991044 [src:gcc-9-cross] gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs Bug reassigned from package 'src:gcc-9-cross' to 'gcc-10-cross'. No longer marked as found in versions gcc-9-cross/25. Ignoring request to alter fixed versions of bug #991044 to the same values previously set Bug #991044 [gcc-10-cross] gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs There is no source info for the package 'gcc-10-cross' at version '15' with architecture '' Unable to make a source version for version '15' Marked as found in versions 15. > retitle -3 gcc-10-cross: Incorrect Source: version generated for binary > packages in binNMUs Bug #991044 [gcc-10-cross] gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs Changed Bug title to 'gcc-10-cross: Incorrect Source: version generated for binary packages in binNMUs' from 'gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs'. > reassign -4 gcc-10-cross-ports 16 Bug #991045 [src:gcc-9-cross] gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs Bug reassigned from package 'src:gcc-9-cross' to 'gcc-10-cross-ports'. No longer marked as found in versions gcc-9-cross/25. Ignoring request to alter fixed versions of bug #991045 to the same values previously set Bug #991045 [gcc-10-cross-ports] gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs There is no source info for the package 'gcc-10-cross-ports' at version '16' with architecture '' Unable to make a source version for version '16' Marked as found in versions 16. > retitle -4 gcc-10-cross-ports: Incorrect Source: version generated for binary > packages in binNMUs Bug #991045 [gcc-10-cross-ports] gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs Changed Bug title to 'gcc-10-cross-ports: Incorrect Source: version generated for binary packages in binNMUs' from 'gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs'. -- 991042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991042 991043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991043 991044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991044 991045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991042: gcc-9-cross: Incorrect Source: version generated for binary packages in binNMUs
Source: gcc-9-cross Version: 25 Severity: serious Tags: ftbfs Control: clone -1 -2 -3 -4 Control: reassign -2 gcc-9-cross-ports 23 Control: retitle -2 gcc-9-cross-ports: Incorrect Source: version generated for binary packages in binNMUs Control: reassign -3 gcc-10-cross 15 Control: retitle -3 gcc-10-cross: Incorrect Source: version generated for binary packages in binNMUs Control: reassign -4 gcc-10-cross-ports 16 Control: retitle -4 gcc-10-cross-ports: Incorrect Source: version generated for binary packages in binNMUs https://buildd.debian.org/status/package.php?p=gcc-9-cross&suite=sid https://buildd.debian.org/status/package.php?p=gcc-9-cross-ports&suite=sid https://buildd.debian.org/status/package.php?p=gcc-10-cross-ports&suite=sid ... Package: cpp-9-aarch64-linux-gnu Source: gcc-9-cross (26+b1) Version: 9.4.0-1cross2 Architecture: amd64 ...
Bug#991040: Varnish VSV00007
Package: varnish Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team https://varnish-cache.org/security/VSV7.html Patches: https://github.com/varnishcache/varnish-cache/commit/9be22198e258d0e7a5c41f4291792214a29405cf (6.0) https://github.com/varnishcache/varnish-cache/commit/82b0a629f60136e76112c6f2c6372cce77b683be (6.5) Cheers, Moritz
Bug#990906: Xarchiver Debian bug 990906
Hi, I believe that the bug you reported is fixed in the current master of xarchiver: https://github.com/ib/xarchiver/commit/949854e9a74489d8d977aac7a8428ecadd526ff1 Regards, Ingo
Processed: Re: Bug#981054: openipmi: Missing dependency on kmod
Processing control commands: > severity -1 serious Bug #981054 [openipmi] openipmi: Missing dependency on kmod Severity set to 'serious' from 'wishlist' -- 981054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991036: [Debian-on-mobile-maintainers] Bug#991036: libhandy: Should this package be removed in bookworm?
Hi, On Tue, Jul 13, 2021 at 01:36:17PM +0300, Adrian Bunk wrote: > Source: libhandy > Version: 0.0.13-3 > Severity: serious > Tags: bookworm sid > > A more recent version is already available in src:libhandy-1. > > Both versions will be in bullseye, but still shipping both in > bookworm would feel wrong. > > Please reply in case I am wrong here. I think you're right. All rdeps should have been migrated by then as well. I'll recheck once sid sees more updates again past release. Cheers, -- Guido > > ___ > Debian-on-mobile-maintainers mailing list > debian-on-mobile-maintain...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers >
Bug#991037: gnunet: binary-all FTBFS in experimental
Source: gnunet
Version: 0.14.0-5
Severity: serious
Tags: ftbfs
Control: affects -1 src:gnunet-fuse src:gnunet-gtk
https://buildd.debian.org/status/package.php?p=gnunet&suite=experimental
...
dh_install -i
debian/rules execute_after_dh_install
make[1]: Entering directory '/<>'
# Removing files already present in libgnunet from gnunet package
cd debian/libgnunet0.14 && find . -type f,l -exec rm -f ../gnunet/{} \;
sh: 1: cd: can't cd to debian/libgnunet0.14
make[1]: *** [debian/rules:40: execute_after_dh_install] Error 2
Processed: gnunet: binary-all FTBFS in experimental
Processing control commands: > affects -1 src:gnunet-fuse src:gnunet-gtk Bug #991037 [src:gnunet] gnunet: binary-all FTBFS in experimental Added indication that 991037 affects src:gnunet-fuse and src:gnunet-gtk -- 991037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#991036: libhandy: Should this package be removed in bookworm?
Source: libhandy Version: 0.0.13-3 Severity: serious Tags: bookworm sid A more recent version is already available in src:libhandy-1. Both versions will be in bullseye, but still shipping both in bookworm would feel wrong. Please reply in case I am wrong here.
Bug#989603: Fwd: Re: Fwd: Bug#989603: ocsinventory-server: Does not start after install
On Sat, Jun 26, 2021 at 09:43:07PM +0200, Yadd wrote: > As-tu vu que le bug a été clos ? >... ocsinventory-server needs an unblock request for getting this fix into bullseye. cu Adrian
Bug#991015: Acknowledgement (cannot execute due to incorrect shebang line)
On Mon, Jul 12, 2021 at 09:10:15PM -0400, Ryan Kavanagh wrote: > This bug seems to be, in part, due to a potentially (?) broken ruby > upgrade behaviour. I've been running unstable on this laptop for ~6 > years, but still had > > ii ruby2.1 [ruby-interpreter] 2.1.5-4 > ii ruby2.2 [ruby-interpreter] 2.2.4-1 > > installed as my only ruby interpreters. These are no longer available in > unstable, and ruby2.1 was last available in: > > ruby2.1| 2.1.5-2+deb8u3 | oldoldstable | source, amd64, armel, armhf, i386 > > Will users upgrading from buster to bullseye will encounter a similar > issue if they've dist-upgraded from jessie to stretch to buster? The problem is the following in the dependencies: Depends: ruby | ruby-interpreter, ... The /usr/bin/ruby symlink is in the ruby package, the alternative dependency ruby-interpreter is therefore wrong. cu Adrian
Bug#990026: uploaded a fix
Hello, as bug #990026 got no update for three weeks, I uploaded a fix to
our salsa repository, which allows characters like "=" and "/" in e-mail
addresses.
I add the patch as an attachment.
Best regards, Georges.
--
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70
diff --git a/debian/changelog b/debian/changelog
index e94afd6..f98102e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+cron (3.0pl1-137.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * authorized characters like "=", "/" in email addresses.
+the modified file is debian/patches/features/Add-MAILFROM-environment-variable.patch
+Closes: #990026
+
+ -- Georges Khaznadar Tue, 13 Jul 2021 11:04:41 +0200
+
cron (3.0pl1-137) unstable; urgency=medium
[ Laurent Combe ]
diff --git a/debian/patches/features/Add-MAILFROM-environment-variable.patch b/debian/patches/features/Add-MAILFROM-environment-variable.patch
index 1d31ed7..82edf04 100644
--- a/debian/patches/features/Add-MAILFROM-environment-variable.patch
+++ b/debian/patches/features/Add-MAILFROM-environment-variable.patch
@@ -16,11 +16,11 @@ Last-Update: 2021-02-16
do_command.c | 45 ++---
3 files changed, 39 insertions(+), 26 deletions(-)
-diff --git a/cron.8 b/cron.8
-index cae80a3..582270f 100644
a/cron.8
-+++ b/cron.8
-@@ -123,7 +123,9 @@ then wakes up every minute, examining all stored crontabs, checking
+Index: cron/cron.8
+===
+--- cron.orig/cron.8
cron/cron.8
+@@ -123,7 +123,9 @@ then wakes up every minute, examining al
each command to see if it should be run in the current minute. When
executing commands, any output is mailed to the owner of the crontab
(or to the user named in the MAILTO environment variable in the
@@ -31,11 +31,11 @@ index cae80a3..582270f 100644
processes have their name coerced to uppercase, as will be seen in the
syslog and ps output.
.PP
-diff --git a/crontab.5 b/crontab.5
-index 70e411d..969370c 100644
a/crontab.5
-+++ b/crontab.5
-@@ -100,12 +100,16 @@ on these systems, USER will be set also.)
+Index: cron/crontab.5
+===
+--- cron.orig/crontab.5
cron/crontab.5
+@@ -100,12 +100,16 @@ on these systems, USER will be set also.
.PP
In addition to LOGNAME, HOME, and SHELL,
.IR cron (8)
@@ -58,10 +58,10 @@ index 70e411d..969370c 100644
.PP
On the Debian GNU/Linux system, cron supports the
.B pam_env
-diff --git a/do_command.c b/do_command.c
-index 930e910..7a94f52 100644
a/do_command.c
-+++ b/do_command.c
+Index: cron/do_command.c
+===
+--- cron.orig/do_command.c
cron/do_command.c
@@ -52,6 +52,7 @@ static const struct pam_conv conv = {
static void child_process __P((entry *, user *)),
@@ -133,7 +133,7 @@ index 930e910..7a94f52 100644
}
+
+static int safe_p(const char *usernm, const char *s) {
-+ static const char safe_delim[] = "@!:%-.,_+"; /* conservative! */
++ static const char safe_delim[] = "@!:%-.,_+=/"; /* conservative! */
+ const char *t;
+ int ch, first;
+
signature.asc
Description: PGP signature
Bug#991025: merkaartor build depends on both libqt5webkit5-dev and qtwebengine5-dev but uses neither
Source: merkaartor Version: 0.19.0~rc1+ds-1 Severity: serious 1. the build dependency on libqt5webkit5-dev looks stale 2. the build dependency on qtwebengine5-dev should be [amd64 arm64 armhf i386 mipsel] since these are the architectures where the package exists 3. on these 5 architectures, configuring with USEWEBENGINE=1 is required to actually use it Severity set to RC since 2. would currently prevent migration to bookworm.
Bug#982459: mdadm --examine in chroot without /proc,/dev,/sys mounted corrupts host's filesystem
Hi, > I could reproduce the bug with /dev *NOT* mounted in chroot. It seems > independent of /sys being mounted in chroot. tried again but still fail to reproduce (same configuration as last time, just with /proc mounted to chroot/proc, rest not mounted). Additionally tried it with a RAID0 and also to install a kernel with initrd to the chroot, though again didn't manage to get the host file system corrupted. (system used for that second try was RC2 of bullseye on virtualbox, raid was configured using the Debian installer) I think, I need to give up on this. Maybe someone else has an idea. signature.asc Description: This is a digitally signed message part.
