Bug#883619: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev
Hi, On Tue, Feb 26, 2019 at 03:13:39PM +0800, Drew Parsons wrote: > On 2019-02-26 14:54, Andreas Tille wrote: > > > > I just pushed > > +ceres-solver (1.14.0-4) UNRELEASED; urgency=medium > ... > > to Git. Is there any reason not to upload this and simply fix #883619. > > Looks like a pretty low hanging fruit to fix an RC bug and save the > > package for Buster that I can not imagine nobody else would have > > harvested it. > > It's only downstream dependency is colmap. If colmap is happy with the new > version then it sounds like a good idea to upload it, especially if it fixes > an RC bug. I mean: There is no *effective* change since the Build-Depends we set is fullfilled anyway by the existing packages. Its just that it is explicitly declared in the package metadata. Kind regards Andreas. -- http://fam-tille.de
Bug#923226: Compiling shader doesn't work - game doesn't work
Control: reassign -1 ioquake3 1.36+u20181222.e5da13f~dfsg-1 Control: tags -1 + moreinfo On Mon, 25 Feb 2019 at 09:31:51 +0100, Julien Puydt wrote: > openarena doesn't work anymore because it doesn't manage to compile its > shaders. This is almost certainly a problem with the ioquake3 engine rather than the OpenArena game, so I'm reassigning it. > Trying to load "renderer_opengl2_x86_64.so" from "/usr/lib/ioquake3"... ... > Trying to get an OpenGL 3.2 core context > SDL_GL_CreateContext failed: Could not create GL context: GLXBadFBConfig Does the opengl1 renderer work? (See /usr/share/doc/ioquake3/NEWS.Debian.gz) If not, does an older version of ioquake3 from snapshot.debian.org work? Unfortunately ioquake3 does not have the ability to fall back from one renderer module to another if the default doesn't work. > GL_RENDERER: Mesa DRI Intel(R) Ironlake Mobile Ironlake is an Intel graphics generation from 2010, so it's entirely possible that the opengl2 renderer requires newer hardware than that. smcv
Processed: Re: Bug#923226: Compiling shader doesn't work - game doesn't work
Processing control commands: > reassign -1 ioquake3 1.36+u20181222.e5da13f~dfsg-1 Bug #923226 [openarena] Compiling shader doesn't work - game doesn't work Bug reassigned from package 'openarena' to 'ioquake3'. No longer marked as found in versions openarena/0.8.8+dfsg-2. Ignoring request to alter fixed versions of bug #923226 to the same values previously set Bug #923226 [ioquake3] Compiling shader doesn't work - game doesn't work Marked as found in versions ioquake3/1.36+u20181222.e5da13f~dfsg-1. > tags -1 + moreinfo Bug #923226 [ioquake3] Compiling shader doesn't work - game doesn't work Added tag(s) moreinfo. -- 923226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#883619: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev
On 2019-02-26 14:54, Andreas Tille wrote: I just pushed +ceres-solver (1.14.0-4) UNRELEASED; urgency=medium ... to Git. Is there any reason not to upload this and simply fix #883619. Looks like a pretty low hanging fruit to fix an RC bug and save the package for Buster that I can not imagine nobody else would have harvested it. It's only downstream dependency is colmap. If colmap is happy with the new version then it sounds like a good idea to upload it, especially if it fixes an RC bug. Drew
Bug#883619: Any reason not to simply upload ceres-solver with adjusted version of libeigen3-dev
Hi, I just pushed diff --git a/debian/changelog b/debian/changelog index db364aa..a10efd1 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +ceres-solver (1.14.0-4) UNRELEASED; urgency=medium + + * Team upload. + * Bump versioned Build-Depends: libeigen3-dev (>= 3.3.4) +Closes: #883619 + + -- Andreas Tille Tue, 26 Feb 2019 07:50:37 +0100 + ceres-solver (1.14.0-3) unstable; urgency=medium * Updated years in debian/copyright diff --git a/debian/control b/debian/control index da66ec7..108192c 100644 --- a/debian/control +++ b/debian/control @@ -8,7 +8,7 @@ Build-Depends: debhelper (>= 11~), libatlas-base-dev, libgoogle-glog-dev, libgflags-dev, - libeigen3-dev (>= 3.2.1), + libeigen3-dev (>= 3.3.4), libsuitesparse-dev (>= 1:4.4.3), python, python3-sphinx, to Git. Is there any reason not to upload this and simply fix #883619. Looks like a pretty low hanging fruit to fix an RC bug and save the package for Buster that I can not imagine nobody else would have harvested it. Kind regards Andreas. -- http://fam-tille.de
Bug#923307: coquelicot: Uploading file fails
Package: coquelicot Version: 0.9.6-1.1 Severity: serious On Debian testing (Buster), uploading files to Coquelicot results in a 500 error. This error makes the primary function of Coquelicot - uploading and sharing files, unusable. Please see the attached error log for the corresponding errors in the log file. -- Regards, Joseph Nuthalapati 10.0.2.2 - - [26/Feb/2019:05:38:15 +] "POST /coquelicot/authenticate HTTP/1.1" 200 2 0.0010 E, [2019-02-26T05:38:32.731272 #4169] ERROR -- : app error: undefined method `rewind' for # (NoMethodError) E, [2019-02-26T05:38:32.731427 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/multipart.rb:45:in `extract_multipart' E, [2019-02-26T05:38:32.731461 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/request.rb:472:in `parse_multipart' E, [2019-02-26T05:38:32.731481 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/request.rb:335:in `POST' E, [2019-02-26T05:38:32.731501 #4169] ERROR -- : (erb):225:in `pretty' E, [2019-02-26T05:38:32.731522 #4169] ERROR -- : /usr/lib/ruby/2.5.0/erb.rb:876:in `eval' E, [2019-02-26T05:38:32.731542 #4169] ERROR -- : /usr/lib/ruby/2.5.0/erb.rb:876:in `result' E, [2019-02-26T05:38:32.731561 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/show_exceptions.rb:82:in `pretty' E, [2019-02-26T05:38:32.731580 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/show_exceptions.rb:31:in `rescue in call' E, [2019-02-26T05:38:32.731600 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/show_exceptions.rb:21:in `call' E, [2019-02-26T05:38:32.731621 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:194:in `call' E, [2019-02-26T05:38:32.731641 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1957:in `call' E, [2019-02-26T05:38:32.731661 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/upr/input_wrapper.rb:48:in `call' E, [2019-02-26T05:38:32.731681 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/xss_header.rb:18:in `call' E, [2019-02-26T05:38:32.731695 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/path_traversal.rb:16:in `call' E, [2019-02-26T05:38:32.731707 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/json_csrf.rb:26:in `call' E, [2019-02-26T05:38:32.731719 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/base.rb:50:in `call' E, [2019-02-26T05:38:32.731732 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/base.rb:50:in `call' E, [2019-02-26T05:38:32.731750 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/protection/frame_options.rb:31:in `call' E, [2019-02-26T05:38:32.731772 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:232:in `context' E, [2019-02-26T05:38:32.731794 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/session/abstract/id.rb:226:in `call' E, [2019-02-26T05:38:32.731817 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/null_logger.rb:9:in `call' E, [2019-02-26T05:38:32.731833 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/head.rb:12:in `call' E, [2019-02-26T05:38:32.731845 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:194:in `call' E, [2019-02-26T05:38:32.731857 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1957:in `call' E, [2019-02-26T05:38:32.731869 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1502:in `block in call' E, [2019-02-26T05:38:32.731887 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1729:in `synchronize' E, [2019-02-26T05:38:32.731909 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:1502:in `call' E, [2019-02-26T05:38:32.731930 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/urlmap.rb:68:in `block in call' E, [2019-02-26T05:38:32.731953 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/urlmap.rb:53:in `each' E, [2019-02-26T05:38:32.731969 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/urlmap.rb:53:in `call' E, [2019-02-26T05:38:32.731981 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/common_logger.rb:33:in `call' E, [2019-02-26T05:38:32.731993 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/sinatra/base.rb:231:in `call' E, [2019-02-26T05:38:32.732007 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/chunked.rb:54:in `call' E, [2019-02-26T05:38:32.732029 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rack/content_length.rb:15:in `call' E, [2019-02-26T05:38:32.732051 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rainbows/process_client.rb:43:in `process_loop' E, [2019-02-26T05:38:32.732073 #4169] ERROR -- : /usr/lib/ruby/vendor_ruby/rainbows/thread_spawn.rb:36:in `block (3 levels) in accept_loop' signature.asc Description: OpenPGP digital signature
Bug#923185: marked as done (FTBS: javadoc: error - The code being documented uses packages in the unnamed module)
Your message dated Tue, 26 Feb 2019 05:34:15 + with message-id and subject line Bug#923185: fixed in isorelax 2004-12 has caused the Debian Bug report #923185, regarding FTBS: javadoc: error - The code being documented uses packages in the unnamed module 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.) -- 923185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: isorelax Version: 2004-11 Severity: serious Hey, Rebuilding isorelax fails to build with: javadoc: error - The code being documented uses packages in the unnamed module, but the packages defined in /usr/share/doc/default-jdk-doc/api/ are in named modules. The reproducible build logs show a similar error: https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/isorelax_2004-11.rbuild.log.gz -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.19.0-2-amd64 (SMP w/32 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: isorelax Source-Version: 2004-12 We believe that the bug you reported is fixed in the latest version of isorelax, 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 923...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated isorelax package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 25 Feb 2019 21:17:46 -0800 Source: isorelax Architecture: source Version: 2004-12 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: tony mancill Closes: 919959 923185 Changes: isorelax (2004-12) unstable; urgency=medium . * Team upload. . [ Samuel Thibault ] * Mark libisorelax-java Multi-Arch: foreign. . [ tony mancill ] * Disable javadoc link for JDK API and drop build-dep on default-jdk-doc (Closes: #923185) * Patch debian rules to ignore hidden directories (Closes: #919959) Thank you to Santiago Vila for the patch. * Bump Standards-Version to 4.3.0 * Update Vcs- URLs to point to Salsa * Update Homepage URL to use https Checksums-Sha1: 10ccfafb9cfa0bc1554bdf04d868f027c6a7bdcc 2158 isorelax_2004-12.dsc f351fd0442d692a2cf07564c78d48eeb7b158df2 5072 isorelax_2004-12.debian.tar.xz 5671f8c35d6b69dd7fc93e0ad1b83458e1c86911 10402 isorelax_2004-12_amd64.buildinfo Checksums-Sha256: 73b4d3e6c4dc8c3b54b53b7b8f632f7ee9875c110705f015aa87e0b5110d1eb9 2158 isorelax_2004-12.dsc b063dff4895302bf52c54e9f15ca9d3052bafb10a2efcf1a5e58e42b75c983bd 5072 isorelax_2004-12.debian.tar.xz 14bd6ea97856231526b4fbad6d780d08ed8add34e114ae7716810061751144bc 10402 isorelax_2004-12_amd64.buildinfo Files: 72ee9a73c27462522a4b2a75527f0940 2158 java optional isorelax_2004-12.dsc 83ed8223a528fe5ccd91e3673aea8910 5072 java optional isorelax_2004-12.debian.tar.xz 321f2d6aa48376272ff0a18ab6992870 10402 java optional isorelax_2004-12_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAlx0zRsUHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpYABhAAqz2Tv1KNYGDBrGAaOVAByw4gxQ1t ckcOkK4XyMkZXmN4aao3LKar0eEH9QqYLatVTLxywtIQFPYRLJCTxy0PgpO3zw7f SpQAjKMHqY/p1n6sG0h4akA1z+ozuJD363QcT5wqtvWSD0l/huFXlQAShKtm/oDI hSr5bIBFGrsh0LpHA8wSVdAnJfrbkJgC5kB0D7jB1/adOhaM9ZdPDpdY/nmhy+nn AGc3ykWbatIhjLEvZT4/Pf1gKIl/JvhW9LlzuzLWHR6LlfJJ6UdA7NyKrX/OYqor NFKHERD7yyQKbbIsvj+eOp1qa8p/MunfXX9R1Bs1INW5rFO9ygaeQ3WS0egJTW2q gZDUk4ihINKiVBLbGWjsBwlk2nvjZ2EWYZ2WhEq8d7hYy+ApYLYGFkZTv5/ySc0l k2A8dOREZnxEmKEAUoPYGDA99t+knGLBj9+HXw0Ox8/DsGTowMpa1cB7ptPZ6VXu 2JFrPugtOROr28HV5VluWGcVMJIgAcgkILUhr7Hc0y2FNFDW1lUri8tiLBo6da84
Bug#923204: [pkg-gnupg-maint] Bug#923204: Bug#923204: gpg-agent has a false dependency on libpam-systemd
On Mon 2019-02-25 13:33:57 +0100, Werner Koch wrote: > On Sun, 24 Feb 2019 16:56, joshud...@gmail.com said: > >> gpg-agent --server or directly from .profile (ssh sessions) by >> gpg-agent --daemon. > > FWIW, actually gpg-agent is started on-demand from all tools requiring > it. To explicitly start it "gpgconf --launch agent" can and should be > used. On systems where you actually care about all processes terminating when you log out (which is most well-managed systems), you want something that can automatically spawn and reap per-user daemons as they're needed by the user. Users of GNU/Linux systems with systemd as the process supervisor can rely on libpam-systemd to manage user sessions successfully. That way, when you log out, your agent actually goes away, any secrets currently unlocked are flushed, and your overall session (and all related processes) terminates correctly. This allows things like automated unmounting of relevant filesystems, flushing of in-kernel keys, etc. There are many other possible ways to manage per-user daemons on other systems, but if you're already using systemd, it makes no sense to have each daemon re-invent that wheel (and potentially fail to clean up at the end of the session, as Werner's suggestion above does). That's why gpg-agent Suggests: libpam-systemd. If you want to propose better integration with any system or session managers that can be used in Debian (whether systemd or otherwise), i'm all ears -- please submit those changes to the BTS as specific improvements so that we can review them and make things better for users of those systems. Regards, --dkg signature.asc Description: PGP signature
Bug#920621: marked as done (texlive-base: breaks build of forthcoming doxygen 1.8.15)
Your message dated Tue, 26 Feb 2019 09:04:34 +0900
with message-id <20190226000434.ga7...@bulldog.preining.info>
and subject line Re: Processed: Re: Bug#920621: texlive-base: breaks build of
forthcoming doxygen 1.8.15
has caused the Debian Bug report #920459,
regarding texlive-base: breaks build of forthcoming doxygen 1.8.15
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-base
Version: 2018.20190126-1
Severity: important
Dear Maintainer,
I am preparing the next relase of doxygen (1.8.15).
Last week it built fine with texlive-base 2018.20181214-1.
I tried today with 2018.20190126-1 and it fails.
You can see the trace of the successful build here:
https://salsa.debian.org/paolog-guest/doxygen/-/jobs/107680
and of the failed build here:
https://salsa.debian.org/paolog-guest/doxygen/-/jobs/115667
I attach the files necessary to reproduce (I took the files in
doxygen/debian/build at the end of the failed build and blanked a few to reduce
the size of the attachment).
Extract then launch:
/usr/bin/pdflatex -shell-escape doxygen_manual.tex
While processing Chapter 3 (starting.tex) pdflatex from texlive-base
2018.20190126-1 prints a lot of these messages:
]
! Missing } inserted.
}
l.74 \end{longtabu}
I've inserted something that you may have forgotten.
(See the above.)
With luck, this will get me unwedged. But if you
really didn't forget anything, try typing `2' now; then
my insertion and my current dilemma will both disappear.
! Missing } inserted.
}
l.74 \end{longtabu}
I've inserted something that you may have forgotten.
(See the above.)
With luck, this will get me unwedged. But if you
really didn't forget anything, try typing `2' now; then
my insertion and my current dilemma will both disappear.
! Missing } inserted.
}
l.74 \end{longtabu}
I've inserted something that you may have forgotten.
(See the above.)
With luck, this will get me unwedged. But if you
really didn't forget anything, try typing `2' now; then
my insertion and my current dilemma will both disappear.
! Missing \cr inserted.
\cr
l.74 \end{longtabu}
I'm guessing that you meant to end an alignment here.
! Misplaced \cr.
\cr
l.74 \end{longtabu}
I can't figure out why you would want to use a tab mark
or \cr or \span just now. If something like a right brace
up above has ended a previous alignment prematurely,
you're probably due for more error messages, and you
might try typing `S' now just to see what is salvageable.
then bails out with exit code 1 and no PDF file.
If I try that with pdflatex from texlive-base all 2018.20181214-1, it succeeds.
Thanks for any help,
Paolo
##
List of ls-R files
-rw-r--r-- 1 root root 1201 Jan 27 10:43 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Sep 2 14:32 /usr/share/texmf/ls-R ->
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Jan 25 23:06 /usr/share/texlive/texmf-dist/ls-R ->
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Jan 25 23:06 /usr/share/texlive/texmf-dist/ls-R ->
/var/lib/texmf/ls-R-TEXLIVEDIST
##
Config files
-rw-r--r-- 1 root root 475 Jan 27 10:43 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Jan 25 23:06 /usr/share/texmf/web2c/fmtutil.cnf ->
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Jan 25 23:06 /usr/share/texmf/web2c/updmap.cfg ->
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2763 Jan 27 10:43
/var/lib/texmf/tex/generic/config/language.dat
##
Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Sep 2 14:32 mktex.cnf
-rw-r--r-- 1 root root 475 Jan 27 10:43 texmf.cnf
##
md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
Bug#921779: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Tue, 26 Feb 2019 09:04:34 +0900 with message-id <20190226000434.ga7...@bulldog.preining.info> and subject line Re: Processed: Re: Bug#920621: texlive-base: breaks build of forthcoming doxygen 1.8.15 has caused the Debian Bug report #920459, regarding tabu: breaks with color and/or xcolor when spread or negative X coefficients are used 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.) -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:doxygen Version: 1.8.13-10 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh_testdir /usr/bin/make -C jquery install make[1]: Entering directory '/<>/jquery' java -jar /usr/share/yui-compressor/yui-compressor.jar jquery-1.7.1.js > jquery-1.7.1-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.core.js > jquery.ui-1.8.18.core-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.widget.js > jquery.ui-1.8.18.widget-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.mouse.js > jquery.ui-1.8.18.mouse-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.resizable.js > jquery.ui-1.8.18.resizable-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ba-1.3-hashchange.js > jquery.ba-1.3-hashchange-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.scrollTo-1.4.2.js > jquery.scrollTo-1.4.2-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.powertip-1.2.0.js > jquery.powertip-1.2.0-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-0.2.3.touch-punch.js > jquery.ui-0.2.3.touch-punch-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.smartmenus-1.0.0.js > jquery.smartmenus-1.0.0-min.js [... snipped ...] [100%] Generating trouble.doc cd /<>/build/doc && /usr/bin/cmake -E copy /<>/doc/trouble.doc /<>/build/doc/ [100%] Generating xmlcmds.doc cd /<>/build/doc && /usr/bin/cmake -E copy /<>/doc/xmlcmds.doc /<>/build/doc/ [100%] Generating Latex and HTML documentation. cd /<>/build/doc && /<>/build/bin/doxygen This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=latex) restricted \write18 enabled. entering extended mode (./_formulas.tex LaTeX2e <2018-12-01> make[4]: Leaving directory '/<>/build' [100%] Built target run_doxygen /usr/bin/make -f doc/CMakeFiles/doxygen_pdf.dir/build.make doc/CMakeFiles/doxygen_pdf.dir/depend make[4]: Entering directory '/<>/build' cd /<>/build && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/doc /<>/build /<>/build/doc /<>/build/doc/CMakeFiles/doxygen_pdf.dir/DependInfo.cmake --color= Dependee "/<>/build/doc/CMakeFiles/doxygen_pdf.dir/DependInfo.cmake" is newer than depender "/<>/build/doc/CMakeFiles/doxygen_pdf.dir/depend.internal". Dependee "/<>/build/doc/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/<>/build/doc/CMakeFiles/doxygen_pdf.dir/depend.internal". Scanning dependencies of target doxygen_pdf make[4]: Leaving directory '/<>/build' /usr/bin/make -f doc/CMakeFiles/doxygen_pdf.dir/build.make doc/CMakeFiles/doxygen_pdf.dir/build make[4]: Entering directory '/<>/build' [100%] Generating Doxygen Manual PDF. cd /<>/build/latex && /usr/bin/cmake -E remove refman.tex cd /<>/build/latex && /usr/bin/cmake -E copy /<>/build/doc/doxygen_manual.tex . cd /<>/build/latex && /usr/bin/cmake -E copy /<>/build/doc/manual.sty . cd /<>/build/latex && /usr/bin/epstopdf /<>/doc/doxygen_logo.eps --outfile=doxygen_logo.pdf cd /<>/build/latex && /usr/bin/pdflatex -shell-escape doxygen_manual.tex This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex) \write18 enabled. entering extended mode (./doxygen_manual.tex LaTeX2e <2018-12-01> make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:62: doc/CMakeFiles/doxygen_pdf] Error 1 make[4]: Leaving directory '/<>/build' make[3]: *** [CMakeFiles/Makefile2:445: doc/CMakeFiles/doxygen_pdf.dir/all] Error 2 make[3]: Leaving directory '/<>/build' make[2]: *** [CMakeFiles/Makefile2:484: doc/CMakeFiles/docs.dir/rule] Error 2 make[2]: Leaving directory '/<>/build' make[1]: *** [Makefile:301: docs] Error 2 make[1]: Leaving directory '/<>/build' make: *** [debian/rules:60: build-stamp] Error 2 dpkg-buildpackage: error:
Bug#921272: marked as done (texlive-latex-extra: package tabu broken when xcolor is used)
Your message dated Tue, 26 Feb 2019 09:04:34 +0900
with message-id <20190226000434.ga7...@bulldog.preining.info>
and subject line Re: Processed: Re: Bug#920621: texlive-base: breaks build of
forthcoming doxygen 1.8.15
has caused the Debian Bug report #920459,
regarding texlive-latex-extra: package tabu broken when xcolor is used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-latex-extra
Version: 2018.20190131-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Compiling the LaTeX doxygen-generated documentation for debian package
toulbar2 fails.
* What exactly did you do (or not do) that was effective (or
ineffective)?
A minimal latex file does not compile anymore on texlive (did previously)
* What was the outcome of this action?
An error (missing brace) is raised.
* What outcome did you expect instead?
A PDF file should be generated by pdflatex
*** End of the template - remove these template lines ***
-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource.
In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.
*** The Debian TeX Team is *not* a LaTeX Help Desk ***
If you report an error when running one of the TeX-related binaries
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.
Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.
Don't forget to also include minimal examples of other files that are
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!
If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at
http://www.minimalbeispiel.de/mini-en.html (english)
or
http://www.minimalbeispiel.de/mini.html (german)
##
minimal input file
\documentclass{article}
\usepackage{array}
\usepackage[table]{xcolor}
\usepackage{longtable}
\usepackage{tabu}
\begin{document}
\begin{longtabu}{X[-1]X[-1]}
\textbf{Cost Function Network Solver} & toulbar2
\end{longtabu}
\end{document}
##
other files
##
List of ls-R files
-rw-r--r-- 1 root root 1201 Feb 3 17:49 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Sep 2 12:32 /usr/share/texmf/ls-R ->
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Jan 31 03:53 /usr/share/texlive/texmf-dist/ls-R ->
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Jan 31 03:53 /usr/share/texlive/texmf-dist/ls-R ->
/var/lib/texmf/ls-R-TEXLIVEDIST
##
Config files
-rw-r--r-- 1 root root 475 Feb 3 17:49 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Jan 31 03:53 /usr/share/texmf/web2c/fmtutil.cnf ->
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Jan 31 03:53 /usr/share/texmf/web2c/updmap.cfg ->
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2763 Feb 3 17:49
/var/lib/texmf/tex/generic/config/language.dat
##
Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Aug 17 2017 mktex.cnf
-rw-r--r-- 1 root root 475 Feb 3 17:49 texmf.cnf
##
md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c /etc/texmf/texmf.d/00debian.cnf
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.12-041812-generic (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Bug#921299: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Tue, 26 Feb 2019 09:04:34 +0900 with message-id <20190226000434.ga7...@bulldog.preining.info> and subject line Re: Processed: Re: Bug#920621: texlive-base: breaks build of forthcoming doxygen 1.8.15 has caused the Debian Bug report #920459, regarding tabu: breaks with color and/or xcolor when spread or negative X coefficients are used 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.) -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: caffe Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: ! LaTeX Error: File `listofitems.sty' not found. Paolo -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled ~ --- End Message --- --- Begin Message --- Version: 2018.20190131-2 Hi > what did you do? forcemerge of closed and opened bug. > Can you please fix that, or provide new information on why > this was not fixed? Done so, I hope. Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. +JAIST +TeX Live +Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13--- End Message ---
Bug#920459: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Tue, 26 Feb 2019 09:04:34 +0900
with message-id <20190226000434.ga7...@bulldog.preining.info>
and subject line Re: Processed: Re: Bug#920621: texlive-base: breaks build of
forthcoming doxygen 1.8.15
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:toulbar2
Version: 1.0.0+dfsg3-1.1
Severity: serious
Tags: sid buster
toulbar2 ftbfs in unstable
[...]
*geometry* driver: auto-detecting
*geometry* detected driver: pdftex
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/gettitlestring.sty))
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./index.tex
(/usr/share/texlive/texmf-dist/tex/latex/wasysym/uwasy.fd)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsa.fd)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsb.fd)
! Missing } inserted.
}
l.7 \end{longtabu}
?
! Emergency stop.
}
l.7 \end{longtabu}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[4]: *** [Makefile:6: refman.pdf] Error 1
make[4]: Leaving directory
'/<>/toulbar2-1.0.0+dfsg3/obj-x86_64-linux-gnu/latex'
make[3]: *** [CMakeFiles/doc.dir/build.make:71: doc] Error 2
make[3]: Leaving directory
'/<>/toulbar2-1.0.0+dfsg3/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:76: CMakeFiles/doc.dir/all] Error 2
[...]
--- End Message ---
--- Begin Message ---
Version: 2018.20190131-2
Hi
> what did you do?
forcemerge of closed and opened bug.
> Can you please fix that, or provide new information on why
> this was not fixed?
Done so, I hope.
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13--- End Message ---
Bug#921789: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Tue, 26 Feb 2019 09:04:34 +0900
with message-id <20190226000434.ga7...@bulldog.preining.info>
and subject line Re: Processed: Re: Bug#920621: texlive-base: breaks build of
forthcoming doxygen 1.8.15
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:librostlab-blast
Version: 1.0.1-9
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
dh_update_autotools_config -i
dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:7: installing './compile'
configure.ac:5: installing './missing'
[... snipped ...]
LaTeX Warning: Reference `blast-parser-parser_8h' on page 7 undefined on input
line 5.
LaTeX Warning: Reference `blast-parser-position_8h' on page 7 undefined on inpu
t line 6.
LaTeX Warning: Reference `blast-parser-stack_8h' on page 7 undefined on input l
ine 7.
LaTeX Warning: Reference `blast-result_8h' on page 7 undefined on input line 8.
) [7] [8]
Chapter 5.
(./namespacerostlab.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
LaTeX Font Warning: Font shape `T1/pcr/bc/n' undefined
(Font) using `T1/pcr/m/n' instead on input line 27.
[9]) (./namespacerostlab_1_1blast.tex [10] [11] [12] [13] [14]
! Missing } inserted.
}
l.253 \end{DoxyParams}
?
! Emergency stop.
}
l.253 \end{DoxyParams}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
mv: cannot stat 'refman.pdf': No such file or directory
make[2]: *** [Makefile:902: ../doxygen-doc/librostlab-blast.pdf] Error 1
make[2]: Leaving directory '/<>/lib'
make[1]: *** [debian/rules:26: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/librostlab-blast.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Version: 2018.20190131-2
Hi
> what did you do?
forcemerge of closed and opened bug.
> Can you please fix that, or provide new information on why
> this was not fixed?
Done so, I hope.
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13--- End Message ---
Bug#921838: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Tue, 26 Feb 2019 09:04:34 +0900
with message-id <20190226000434.ga7...@bulldog.preining.info>
and subject line Re: Processed: Re: Bug#920621: texlive-base: breaks build of
forthcoming doxygen 1.8.15
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ppl
Version: 1:1.2-7
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh binary-indep
dh_update_autotools_config -i
dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:152: installing './compile'
configure.ac:43: installing './missing'
[... snipped ...]
d on input line 40.
) (./group__PPL__C__interface.tex)
Underfull \vbox (badness 7740) has occurred while \output is active [17]
[18] (./group__Init.tex
Underfull \hbox (badness 1) detected at line 35
[][][]
Underfull \hbox (badness 1) detected at line 48
[][][]
[19]) [20] (./group__Version.tex [21]) [22] (./group__Error.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/omsptm.fd)
Overfull \hbox (1.62299pt too wide) in paragraph at lines 6--20
[][]\OT1/ptm/m/n/10 P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]O[]U[]T[][][][]O[]F[][]
[][]M[]E[]M[]O[]RY[][], [][]P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]I[]N[]V[]A[]L[]
I[]D[][][][]A[]R[]G[]U[]M[]E[]NT[][], [][]P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]D
[]O[]M[]
Overfull \hbox (1.35289pt too wide) in paragraph at lines 6--20
[][]\OT1/ptm/m/n/10 P[]P[]L[][][][]A[]R[]I[]T[]H[]M[]E[]T[]I[]C[][][][]O[]V[]E[
]R[]F[]L[]OW[][], [][]P[]P[]L[][][][]S[]T[]D[]I[]O[][][][]E[]R[]R[]OR[][], [][]
P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]I[]N[]T[]E[]R[]N[]A[]L[][][][]E[]R[]R[]OR[]
[], [][]P[]
! Missing } inserted.
}
l.88 \end{DoxyEnumFields}
?
! Emergency stop.
}
l.88 \end{DoxyEnumFields}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory
'/<>/doc/user-configured-c-interface.latex-dir'
make[2]: *** [Makefile:2064: ppl-user-configured-c-interface-1.2.pdf] Error 2
make[2]: Leaving directory '/<>/doc'
dh_auto_build: cd doc && make -j1 user-configured returned exit code 2
make[1]: *** [debian/rules:75: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:52: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ppl.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Version: 2018.20190131-2
Hi
> what did you do?
forcemerge of closed and opened bug.
> Can you please fix that, or provide new information on why
> this was not fixed?
Done so, I hope.
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13--- End Message ---
Bug#921783: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Tue, 26 Feb 2019 09:04:34 +0900
with message-id <20190226000434.ga7...@bulldog.preining.info>
and subject line Re: Processed: Re: Bug#920621: texlive-base: breaks build of
forthcoming doxygen 1.8.15
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:graphite2
Version: 1.3.13-7
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python3 --buildsystem=cmake --builddirectory=build
dh_update_autotools_config -i -O--buildsystem=cmake -O--builddirectory=build
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_BUILD_TYPE:STRING=Release
-DGRAPHITE2_NTRACING:BOOL=ON -DLIB_SUFFIX=/x86_64-linux-gnu
-DPYTHON_EXECUTABLE=/usr/bin/python3
cd build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu
-DCMAKE_BUILD_TYPE:STRING=Release -DGRAPHITE2_NTRACING:BOOL=ON
-DLIB_SUFFIX=/x86_64-linux-gnu -DPYTHON_EXECUTABLE=/usr/bin/python3 ..
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.7.2",
minimum required is "3.6")
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
[... snipped ...]
LaTeX Warning: Reference `Font_8h' on page 5 undefined on input line 3.
LaTeX Warning: Reference `Log_8h' on page 5 undefined on input line 4.
LaTeX Warning: Reference `Segment_8h' on page 5 undefined on input line 5.
LaTeX Warning: Reference `Types_8h' on page 5 undefined on input line 6.
) [5] [6]
Chapter 4.
(./structgr__face__ops.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd) [7])
(./structgr__faceinfo.tex
! Missing } inserted.
}
l.84 \end{DoxyEnumFields}
?
! Emergency stop.
}
l.84 \end{DoxyEnumFields}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[6]: *** [Makefile:6: refman.pdf] Error 1
make[6]: Leaving directory '/<>/build/doc/doxygen/latex'
make[5]: *** [doc/CMakeFiles/docs.dir/build.make:90:
doc/doxygen/latex/refman.pdf] Error 2
make[5]: Leaving directory '/<>/build'
make[4]: *** [CMakeFiles/Makefile2:1048: doc/CMakeFiles/docs.dir/all] Error 2
make[4]: Leaving directory '/<>/build'
make[3]: *** [CMakeFiles/Makefile2:1055: doc/CMakeFiles/docs.dir/rule] Error 2
make[3]: Leaving directory '/<>/build'
make[2]: *** [Makefile:412: docs] Error 2
make[2]: Leaving directory '/<>/build'
dh_auto_build: cd build && make -j1 docs returned exit code 2
make[1]: *** [debian/rules:14: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/graphite2.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Version: 2018.20190131-2
Hi
> what did you do?
forcemerge of closed and opened bug.
> Can you please fix that, or provide new information on why
> this was not fixed?
Done so, I hope.
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian
Bug#921802: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Tue, 26 Feb 2019 09:04:34 +0900
with message-id <20190226000434.ga7...@bulldog.preining.info>
and subject line Re: Processed: Re: Bug#920621: texlive-base: breaks build of
forthcoming doxygen 1.8.15
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:primesieve
Version: 7.3+ds-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --builddirectory=_build
dh_update_autotools_config -i -O--builddirectory=_build
dh_autoreconf -i -O--builddirectory=_build
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/primesieve-7.3+ds'
dh_auto_configure -- \
-DBUILD_TESTS=ON \
-DBUILD_EXAMPLES=ON \
-DBUILD_DOC=ON
cd _build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_TESTS=ON
-DBUILD_EXAMPLES=ON -DBUILD_DOC=ON ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
[... snipped ...]
LaTeX Warning: Reference `iterator_8h' on page 9 undefined on input line 3.
LaTeX Warning: Reference `iterator_8hpp' on page 9 undefined on input line 4.
LaTeX Warning: Reference `primesieve_8h' on page 9 undefined on input line 5.
LaTeX Warning: Reference `primesieve_8hpp' on page 9 undefined on input line 6.
LaTeX Warning: Reference `primesieve__error_8hpp' on page 9 undefined on input
line 7.
) [9] [10]
Chapter 6.
(./namespaceprimesieve.tex [11]
Underfull \hbox (badness 1) detected at line 94
[][][]
[12] [13]
Underfull \hbox (badness 1) detected at line 156
[][][]
! Missing } inserted.
}
l.175 \end{DoxyParams}
?
! Emergency stop.
}
l.175 \end{DoxyParams}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory
'/<>/primesieve-7.3+ds/_build/DEBIAN/doc/latex'
make[2]: *** [debian/adhoc/Makefile:15: doc] Error 2
make[2]: Leaving directory '/<>/primesieve-7.3+ds'
make[1]: *** [debian/rules:33: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>/primesieve-7.3+ds'
make: *** [debian/rules:24: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/primesieve.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Version: 2018.20190131-2
Hi
> what did you do?
forcemerge of closed and opened bug.
> Can you please fix that, or provide new information on why
> this was not fixed?
Done so, I hope.
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13--- End Message ---
Bug#923298: chromium: file overlap with chromium-sandbox without Conficts and/or Replaces
Package: chromium Version: 72.0.3626.96-1~deb9u1 Severity: grave Justification: renders package unusable I have been tracking testing for several months. This looks to me like a missing or insufficiently versioned Replaces declaration, but I did not dig deeply into this except to check the BTS to see if it had bitten anyone else. To my surprise, it looks like it has not. # apt install chromium-sandbox Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: chromium-sandbox 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 137 kB of archives. After this operation, 851 kB of additional disk space will be used. Get:1 http://ftp.au.debian.org/debian buster/main amd64 chromium-sandbox amd64 72.0.3626.53-1 [137 kB] Fetched 137 kB in 1s (179 kB/s) Selecting previously unselected package chromium-sandbox. (Reading database ... 351969 files and directories currently installed.) Preparing to unpack .../chromium-sandbox_72.0.3626.53-1_amd64.deb ... Unpacking chromium-sandbox (72.0.3626.53-1) ... dpkg: error processing archive /var/cache/apt/archives/chromium-sandbox_72.0.3626.53-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/chromium/chrome-sandbox', which is also in package chromium 72.0.3626.96-1~deb9u1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/chromium-sandbox_72.0.3626.53-1_amd64.deb -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii libasound2 1.1.8-1 ii libatk1.0-0 2.30.0-2 ii libatomic1 8.2.0-21 ii libatspi2.0-02.30.0-7 ii libavcodec57 7:3.2.12-1~deb9u1 ii libavformat577:3.2.12-1~deb9u1 ii libavutil55 7:3.2.12-1~deb9u1 ii libc62.28-7 ii libcairo21.16.0-2 ii libcups2 2.2.10-3 ii libdbus-1-3 1.12.12-1 ii libdrm2 2.4.97-1 ii libevent-2.0-5 2.0.21-stable-3 ii libexpat12.2.6-1 ii libflac8 1.3.2-3 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3 ii libgcc1 1:8.2.0-21 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-7 ii libglib2.0-0 2.58.3-1 ii libgtk2.0-0 2.24.32-3 ii libicu57 57.1-6+deb9u2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libminizip1 1.1-8+b1 ii libnspr4 2:4.20-1 ii libnss3 2:3.42.1-1 ii libopenjp2-7 2.3.0-1.1 ii libopus0 1.3-1 ii libpango-1.0-0 1.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libpangoft2-1.0-01.42.4-6 ii libpci3 1:3.5.2-1 ii libpng16-16 1.6.36-5 ii libpulse012.2-4 ii libre2-3 20170101+dfsg-1 ii libsnappy1v5 1.1.7-1 ii libstdc++6 8.2.0-21 ii libvpx4 1.6.1-3+deb9u1 ii libwebp6 0.6.1-2 ii libwebpdemux20.6.1-2 ii libwebpmux2 0.5.2-1 ii libx11-6 2:1.6.7-1 ii libx11-xcb1 2:1.6.7-1 ii libxcb1 1.13.1-2 ii libxcomposite1 1:0.4.4-2 ii libxcursor1 1:1.1.15-2 ii libxdamage1 1:1.1.4-3 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxi6 2:1.7.9-1 ii libxml2 2.9.4+dfsg1-7+b3 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.1 1.1.32-2 ii libxss1 1:1.2.3-1 ii libxtst6 2:1.2.3-1 ii x11-utils7.7+4 ii xdg-utils1.1.3-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages chromium recommends: ii fonts-liberation 1:1.07.4-9 ii libgl1-mesa-dri 18.3.2-1 Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell pn chromium-widevine -- no debconf information
Bug#893244: Accepted jruby 9.1.17.0-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 25 Feb 2019 21:38:40 +0100 Source: jruby Binary: jruby Architecture: source Version: 9.1.17.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Andrej Shadura Description: jruby - 100% pure-Java implementation of Ruby Changes: jruby (9.1.17.0-1) unstable; urgency=medium . * New upstream release. * Refresh patches. * Trim trailing whitespace. * Use secure copyright file specification URI. * Move source package lintian overrides to debian/source. * Update Vcs-* to point to Salsa. * Use debhelper compat level 12. * Bump Standards-Version to 4.3.0. * Depend on libmodulator-java. * Use javax.annotation.processing.Generated from Java SE 9. * Disable a part of the SkinnyMethodAdapter test. Checksums-Sha1: bf5484f6bb929fc2f1d8a0704256f7a4adb50936 2815 jruby_9.1.17.0-1.dsc 3b1c96fa63efdd22070742d8a8e17a3afe3bd42a 8574514 jruby_9.1.17.0.orig.tar.gz db6e054eb07a24e3d0137b7a21295027fe97adf0 78396 jruby_9.1.17.0-1.debian.tar.xz Checksums-Sha256: 1552f4bd7585c6b7b6480b2cda2dd10ad4f7af0a52b57fb37309ad8eb6094556 2815 jruby_9.1.17.0-1.dsc b66d7c14f85075afdabb5ebf5950804c5a5d5c1d05ab833f580f04ee709b5773 8574514 jruby_9.1.17.0.orig.tar.gz 845163de6803198e2d53caa61ff7baec73bc993706e449b6a32e6f6418ea56a4 78396 jruby_9.1.17.0-1.debian.tar.xz Files: 148d4ffb85271810326b7e92c7931c00 2815 ruby optional jruby_9.1.17.0-1.dsc 38fe13908af7fe67d32f0c62f4d42746 8574514 ruby optional jruby_9.1.17.0.orig.tar.gz eeebf31e4011b1f3b653a477cf294896 78396 ruby optional jruby_9.1.17.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlx0U2oACgkQXkCM2RzY OdJqJAf/Wg20BYa4795WmV/hBjytWfby9sv5BA7EXNrXRANlcQHbcCy+wfk89/nw S2qp2qrduCGbJZ3U46F5ax7S1QG8Rdg89f4BdTbgmVy5vzuJZidd83JfQbYSYP5g 2KTj0AfqlzTUN8Kd3OPPEHNgb9pvw/TG0FWux2dHqBUSRB8Rhdo4JOG/Esua4C6b lMczq8ziQyyHr3XitNyspq53LxzStR2eazm3iBxz2uJx3F8swhHoMDfvJpyMNcp4 AhQqseuEO9wAklsHKHNQnqK3kCGg8Q78EaOUMtiyD+pWzzBxeAtPEmXgIIDAeqDF jNXHqTefPVl+pi8a0GE0rVqVsILq5w== =JikQ -END PGP SIGNATURE-
Bug#899864: Bug #899864 in vorbis-tools marked as pending
Control: tag -1 pending Hello, Bug #899864 in vorbis-tools 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/multimedia-team/vorbis-tools/commit/ae5ee5d47418793a5d9e87fd2708913ab48e74ac Set Maintainer address to Debian Multimedia Maintainers (closes: #899864) (this message was generated automatically) -- Greetings https://bugs.debian.org/899864
Processed: Bug #899864 in vorbis-tools marked as pending
Processing control commands: > tag -1 pending Bug #899864 [src:vorbis-tools] vorbis-tools: Invalid maintainer address pkg-xiph-ma...@lists.alioth.debian.org Added tag(s) pending. -- 899864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923284: Seemingly miscompiles with jdk-11
Thank you for the report Sjoerd. What error did you get when compiling gradle with the rebuilt bsh? Emmanuel Bourg
Processed: Re: jruby: system() does not work on arm64
Processing commands for cont...@bugs.debian.org: > severity 891449 important Bug #891449 [jruby] jruby: system() does not work on arm64 Severity set to 'important' from 'grave' > End of message, stopping processing here. Please contact me if you need assistance. -- 891449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#908866: marked as done (tcpdf: CVE-2018-17057)
Your message dated Mon, 25 Feb 2019 22:08:13 + with message-id and subject line Bug#908866: fixed in tcpdf 6.2.26+dfsg-1 has caused the Debian Bug report #908866, regarding tcpdf: CVE-2018-17057 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.) -- 908866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908866 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tcpdf Version: 6.2.13+dfsg-1 Severity: grave Tags: patch security upstream Hi, The following vulnerability was published for tcpdf. CVE-2018-17057[0]: | An issue was discovered in TCPDF before 6.2.22. Attackers can trigger | deserialization of arbitrary data via the phar:// wrapper. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-17057 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17057 [1] https://github.com/tecnickcom/TCPDF/commit/1861e33fe05f653b67d070f7c106463e7a5c26e Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: tcpdf Source-Version: 6.2.26+dfsg-1 We believe that the bug you reported is fixed in the latest version of tcpdf, 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 908...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emanuele Rocca (supplier of updated tcpdf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 25 Feb 2019 22:23:26 +0100 Source: tcpdf Binary: php-tcpdf Architecture: source all Version: 6.2.26+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Emanuele Rocca Description: php-tcpdf - PHP class for generating PDF files on-the-fly Closes: 908866 Changes: tcpdf (6.2.26+dfsg-1) unstable; urgency=medium . [ Emanuele Rocca ] * QA upload * New upstream release (Closes: #908866, CVE-2018-17057) . [ Jelmer Vernooij ] * Use secure copyright file specification URI. * Trim trailing whitespace. . [ Ondřej Nový ] * d/rules: Remove trailing whitespaces * d/watch: Use https protocol Checksums-Sha1: 85ac1d1bb4bd7d8ef676a102f438e4823f95ac3d 1852 tcpdf_6.2.26+dfsg-1.dsc 95f1963a36c0c321f28873ea4af39a7ea291ef7a 10777849 tcpdf_6.2.26+dfsg.orig.tar.gz b86c6c73dc28e70cd67ca05daa4ca9eb2da9ed55 5812 tcpdf_6.2.26+dfsg-1.debian.tar.xz 24f01c66658da865a7da3c9ed83071559ba3818f 7830892 php-tcpdf_6.2.26+dfsg-1_all.deb 7907e6f369cb88554bfca4d57b633d6adade6ce1 5323 tcpdf_6.2.26+dfsg-1_amd64.buildinfo Checksums-Sha256: 37a42ab41190f1092821941491a01ba8b9115af767b367366b9b992789cd3d82 1852 tcpdf_6.2.26+dfsg-1.dsc 14da284ddf8db4730ff0e4769c506f42cba3e25e7501e0e72ac8b63439815f09 10777849 tcpdf_6.2.26+dfsg.orig.tar.gz 8f20516ae7a613957d394315709bb23ba0ada5a8cdfc313cc7061118220f71ec 5812 tcpdf_6.2.26+dfsg-1.debian.tar.xz 4ca5302277c5927f234906e81d7a5c187354e82d4dd0155e764309a189f0dd01 7830892 php-tcpdf_6.2.26+dfsg-1_all.deb b7d354fe60873b4da63a9c0a3fb8b0a7f6ff14bf89b4c4961fb40f5204782d49 5323 tcpdf_6.2.26+dfsg-1_amd64.buildinfo Files: e3d0c6ae853c1407c44fee065e54003d 1852 php optional tcpdf_6.2.26+dfsg-1.dsc 239ed6e7e4bc086e8baec9b4f25c33dc 10777849 php optional tcpdf_6.2.26+dfsg.orig.tar.gz 4eef11dd355783c6a07888f2d977e733 5812 php optional tcpdf_6.2.26+dfsg-1.debian.tar.xz cc1d13c71efb1fb3211ffba830949bba 7830892 php optional php-tcpdf_6.2.26+dfsg-1_all.deb a96f6d590eff3755e4528ba2583902d9 5323 php optional tcpdf_6.2.26+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEElUWWlhkoHBf/rFiR1QhaB1D9t6MFAlx0YCcPHGVtYUBkZWJp YW4ub3JnAAoJENUIWgdQ/bejCUMQAIo2x3zbL7JeNee/DUMe4MWNgj/PBKCgsQUe 8BwZ7F+eLHEsltV7zaPvui2zLjkFW0AADYT5ZGBhAeIaMiEX8ruvJIcfG/mT9zMT YGrPcJjpZh52EihOwp/W517OV3fIU6HMsNkfUj+LNAFUFyjAnbcIpBsA8scHzZA4 RW+eNZI2LHYJ8IGJt5jzq/kkgtojb1wx11mr4GRFBfaMrxfPi82U4imo4K++ljKT FABb9vfIudy2qKwdS3y5I7pGzIDZyITkYRKdP1sNVv+3RJLga/kx8hWA4oBXcbsh +HR5gOqBmEWrJuM49MhoNw5euzVt89eyJR+CRTxM3MxHNa9U7KTp75RJvv+XO7Wg
Bug#911836: marked as done (pytest-localserver: FTBFS & autopkgtest regression)
Your message dated Mon, 25 Feb 2019 22:07:34 + with message-id and subject line Bug#911836: fixed in pytest-localserver 0.5.0-1 has caused the Debian Bug report #911836, regarding pytest-localserver: FTBFS & autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 911836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-localserver Version: 0.3.7-2 User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:python3-defaults [X-Debbugs-CC: debian...@lists.debian.org, python3-defau...@packages.debian.org] Dear maintainers, With a recent upload of python3-defaults the autopkgtest of pytest-localserver fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.6.7-1 pytest-localserver from testing0.3.7-2 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Looking at the error, it seems you need to update the tests for the version of openssl in unstable, version 1.1.1. We have a Wiki page that describes the common updates required [1]. Currently this regression is contributing to the delay of the migration of python3-defaults to testing [2]. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from python3-defaults should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from python3-defaults/3.6.7-1. I.e. due to versioned dependencies or breaks/conflicts. In this case: python3-defaults/3.6.7-1 openssl/1.1.1-1 python3-stdlib-extensions/3.7.1-1 python3.6/3.6.7-1 [1] https://wiki.debian.org/ContinuousIntegration/TriagingTips/openssl-1.1.1 [2] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/pytest-localserver/1204135/log.gz ERRORS __ ERROR at setup of test_httpsserver_funcarg __ request = > @pytest.fixture def httpsserver(request): """The returned ``httpsserver`` (note the additional S!) provides a threaded HTTP server instance similar to funcarg ``httpserver`` but with SSL encryption. """ from pytest_localserver import https > server = https.SecureContentServer() pytest_localserver/plugin.py:65: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ pytest_localserver/https.py:103: in __init__ super(SecureContentServer, self).__init__(host, port, ssl_context=(key, cert)) pytest_localserver/http.py:64: in __init__ super(ContentServer, self).__init__(host, port, self, ssl_context=ssl_context) pytest_localserver/http.py:22: in __init__ self._server = make_server(host, port, self.app, **kwargs) /usr/lib/python3/dist-packages/werkzeug/serving.py:666: in make_server passthrough_errors, ssl_context, fd=fd) /usr/lib/python3/dist-packages/werkzeug/serving.py:601: in __init__ self.socket = ssl_context.wrap_socket(sock, server_side=True) /usr/lib/python3/dist-packages/werkzeug/serving.py:511: in wrap_socket ssl_version=self._protocol, **kwargs) /usr/lib/python3.6/ssl.py:1158: in wrap_socket ciphers=ciphers) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = sock = keyfile = '/tmp/autopkgtest-lxc.4ukr44pr/downtmp/build.fTj/src/pytest_localserver/server.pem' certfile = '/tmp/autopkgtest-lxc.4ukr44pr/downtmp/build.fTj/src/pytest_localserver/server.pem' server_side = True, cert_reqs = ssl_version = <_SSLMethod.PROTOCOL_TLS: 2>, ca_certs = None do_handshake_on_connect = True, family = type = , proto = 0, fileno = None suppress_ragged_eofs = True, npn_protocols =
Processed: Bug #899590 in libvorbis marked as pending
Processing control commands: > tag -1 pending Bug #899590 [src:libvorbis] libvorbis: Invalid maintainer address pkg-xiph-ma...@lists.alioth.debian.org Added tag(s) pending. -- 899590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899590 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#911836: pytest-localserver: autopkgtest needs update for new version of openssl
On 25/02 03:29, Sandro Tosi wrote: > Emanuele, pytest-localserver has been orphaned, so you can go ahead > and upload it if you want Done. > (and i dont think it's appropriate anymore to use the DPMT git repo, i > guess you can move it to the debian/ namespace) Also done, thanks Sandro.
Bug#899590: Bug #899590 in libvorbis marked as pending
Control: tag -1 pending Hello, Bug #899590 in libvorbis 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/multimedia-team/libvorbis/commit/15c1a7fdebccac2cafec261b1a02218095f5bf0d Set Maintainer address to Debian Multimedia Maintainers (closes: #899590) (this message was generated automatically) -- Greetings https://bugs.debian.org/899590
Bug#866423: marked as done (fofix-dfsg: depends on obsolete python-imaging (replace with python3-pil or python-pil))
Your message dated Mon, 25 Feb 2019 21:34:06 + with message-id and subject line Bug#866423: fixed in fofix-dfsg 3.121-6 has caused the Debian Bug report #866423, regarding fofix-dfsg: depends on obsolete python-imaging (replace with python3-pil or python-pil) 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.) -- 866423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fofix-dfsg Version: 3.121-4 Severity: important Tags: sid buster User: d...@debian.org Usertags: imaging-pillow One or more binary packages built from this source depends on or recommends python-imaging, which is obsolete for some years now. Please build the source using the python-pil package. If your package doesn't need to be built with Python2, please consider using Python3 and depend on python3-pil. Planning to remove python-imaging for the buster release, so the severity of this issues might be raised. --- End Message --- --- Begin Message --- Source: fofix-dfsg Source-Version: 3.121-6 We believe that the bug you reported is fixed in the latest version of fofix-dfsg, 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 866...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emanuele Rocca (supplier of updated fofix-dfsg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 25 Feb 2019 21:47:57 +0100 Source: fofix-dfsg Binary: fofix Architecture: source all Version: 3.121-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Emanuele Rocca Description: fofix - rhythm game in the style of Rock Band(tm) and Guitar Hero(tm) Closes: 866423 Changes: fofix-dfsg (3.121-6) unstable; urgency=medium . * QA upload. * Depend on python-pil instead of python-imaging, obsolete since a while. Patch Video.py to ensure Image is imported from PIL. (Closes: #866423) * Set debhelper compatibility level to 11. * Bump Standards Version to 4.3.0. Checksums-Sha1: a982356caa61ea20b8bd1e3cf1173c9d92f59f1c 1765 fofix-dfsg_3.121-6.dsc f48538141aa9cff2b5e2e3819b443f419ed7b70d 6720 fofix-dfsg_3.121-6.debian.tar.xz 01738bd8eb600b64a0a003264dfb41b01fb47dd8 5786 fofix-dfsg_3.121-6_amd64.buildinfo 29a7d04cd9d9f68a1820b58241a19603234d53e8 14892484 fofix_3.121-6_all.deb Checksums-Sha256: 1b2c722d85278e98ae694d6d7daee8996c3c375a0f47325e05132229ed7b0e06 1765 fofix-dfsg_3.121-6.dsc f9e3f0daf60cbf0c79eaaa3f43723634c68dafcb58f227cac859e54b14c3d870 6720 fofix-dfsg_3.121-6.debian.tar.xz 6b2a7a540e0e2d6ed18e3948c01749cfb26351be7f39e9344e01e60063f2c497 5786 fofix-dfsg_3.121-6_amd64.buildinfo d0bd5e9eb9e939c32937df66172d883c5cd7902573f1d3d169daad4244d38a6f 14892484 fofix_3.121-6_all.deb Files: 906a6c7069f4e60a111ac59c1dbf8361 1765 games optional fofix-dfsg_3.121-6.dsc ddf7cc431d56afd4267c2370f3eec530 6720 games optional fofix-dfsg_3.121-6.debian.tar.xz 748c3657ea37ee030ad8e58375698251 5786 games optional fofix-dfsg_3.121-6_amd64.buildinfo cf0e19becbb7a1d962688018689d82a8 14892484 games optional fofix_3.121-6_all.deb -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEElUWWlhkoHBf/rFiR1QhaB1D9t6MFAlx0WDsPHGVtYUBkZWJp YW4ub3JnAAoJENUIWgdQ/bejtWUP+gPZldIfiU2lHxWaAvkeUHvHCNygiA3s8eXU OYjn/9VFSyNqc/21tQrzNFFfGARDIbMQGkIxKLG2q47ZbokTQwk9xNmehTwaReLt 856b7zhmnDx4sgnWrrOjyJoxCnevAlHtYofS1FYm+HQnm9vi1CYFuFpFuohQVlei hC13Y/u/4o760JDD5QNwq0dYd7uLzHlfKQbi+cqDjAwgiJLM7cWFm1rNEopl4U+j LCHEFAb1MiTYMJV7wHxY3qLCUXnLlloY6nxxlZJF5+Y9EDoEJhaztWLQZAYJ7CXw gBUJFTknjCfb/KlhdSUfmtf2Eai+AKFWv7gF33/wWmGDtBTl/m2fFd5vzewCQnWB NQ0qAe1qUNeSm5q2a6jQyFcOOkvZstKYRCzWm4D+ObPlV/8/ZJ5q7DxbpYtiy/SO dWan2w/bZxSKYI46Dvij0j4F8ZhfY2MYhlsXOUF0bTX9E3A43I5AiL+H1ydte/B/ +scAjNjmwH4AR3oj4FeicLVD5LdpKeglPiKXjohbe5oJf7V3+1BaqWeoq5nJleCr 0YThxICIGjIPZ3qJ+sMXoX3VqA9mHeurL1UcK99IUDRF66/ByFni14sIrJsiAd2p pYWEsLwsHiXwDGCSjKlL/Yv68ZlwcZWx4/20mmv0xa0MmrO5SXaHdVu0HkNHJuzM TPMbAUYH =DStU -END PGP SIGNATURE End Message ---
Bug#923284: Seemingly miscompiles with jdk-11
Source: bsh Version: 2.0b4-19 Severity: serious When building bsh with openjdk-11 it seems that afterwards building packages using it fails e.g. after rebuilding bsh gradle fails to build. Attached is a dockerfile which nicely shows the issue -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armhf Kernel: Linux 4.19.0-2-amd64 (SMP w/32 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled FROM debian:buster RUN apt-get update && \ apt-get install -y --no-install-recommends vim-tiny RUN cat /etc/apt/sources.list | sed 's,^deb,deb-src,g' > /etc/apt/sources.list.d/s.list RUN apt-get update && \ apt-get install -y build-essential devscripts RUN apt-get update && \ apt-get build-dep -y bsh gradle # builds fine RUN apt-get source gradle && \ cd gradle* && \ debuild -uc -us # Rebuild bsh RUN apt-get source bsh && \ cd bsh* && \ debuild -uc -us && \ cd .. && \ dpkg -i libbsh-java*.deb # fail :/ RUN apt-get source gradle && \ cd gradle* && \ debuild -uc -us
Bug#911836: pytest-localserver: autopkgtest needs update for new version of openssl
Emanuele, pytest-localserver has been orphaned, so you can go ahead and upload it if you want (and i dont think it's appropriate anymore to use the DPMT git repo, i guess you can move it to the debian/ namespace) On Mon, Feb 25, 2019 at 3:21 PM Emanuele Rocca wrote: > > tag 911836 patch > tag 911836 pending > thanks > > Fix pushed to salsa: > https://salsa.debian.org/python-team/modules/pytest-localserver/merge_requests/1/diffs?commit_id=bad8a656ec5383c5b8a1d1e52f75e7afbe7c8c1b > -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi G+: https://plus.google.com/u/0/+SandroTosi
Bug#911836: pytest-localserver: autopkgtest needs update for new version of openssl
tag 911836 patch tag 911836 pending thanks Fix pushed to salsa: https://salsa.debian.org/python-team/modules/pytest-localserver/merge_requests/1/diffs?commit_id=bad8a656ec5383c5b8a1d1e52f75e7afbe7c8c1b
Processed: Re: pytest-localserver: autopkgtest needs update for new version of openssl
Processing commands for cont...@bugs.debian.org: > tag 911836 patch Bug #911836 [src:pytest-localserver] pytest-localserver: FTBFS & autopkgtest regression Added tag(s) patch. > tag 911836 pending Bug #911836 [src:pytest-localserver] pytest-localserver: FTBFS & autopkgtest regression Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 911836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#920621: texlive-base: breaks build of forthcoming doxygen 1.8.15
Processing commands for cont...@bugs.debian.org:
> severity 920621 serious
Bug #920621 [texlive-latex-extra] texlive-base: breaks build of forthcoming
doxygen 1.8.15
Bug #921272 [texlive-latex-extra] texlive-latex-extra: package tabu broken when
xcolor is used
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> forwarded 920621 https://github.com/tabu-fixed/tabu/pull/14
Bug #920621 [texlive-latex-extra] texlive-base: breaks build of forthcoming
doxygen 1.8.15
Bug #921272 [texlive-latex-extra] texlive-latex-extra: package tabu broken when
xcolor is used
Changed Bug forwarded-to-address to
'https://github.com/tabu-fixed/tabu/pull/14' from
'https://github.com/tabu-fixed/tabu/issues/1'.
Changed Bug forwarded-to-address to
'https://github.com/tabu-fixed/tabu/pull/14' from
'https://github.com/tabu-fixed/tabu/issues/1'.
> forcemerge 920621 920459
Bug #920621 [texlive-latex-extra] texlive-base: breaks build of forthcoming
doxygen 1.8.15
Bug #921272 [texlive-latex-extra] texlive-latex-extra: package tabu broken when
xcolor is used
Bug #921299 {Done: Norbert Preining }
[texlive-latex-extra] tabu: breaks with color and/or xcolor when spread or
negative X coefficients are used
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions texlive-extra/2018.20190131-2.
No longer marked as fixed in versions texlive-extra/2018.20190131-2.
No longer marked as fixed in versions texlive-extra/2018.20190131-2.
No longer marked as fixed in versions texlive-extra/2018.20190131-2.
No longer marked as fixed in versions texlive-extra/2018.20190131-2.
No longer marked as fixed in versions texlive-extra/2018.20190131-2.
No longer marked as fixed in versions texlive-extra/2018.20190131-2.
Removed annotation that Bug was owned by t...@debian.org.
Removed annotation that Bug was owned by t...@debian.org.
Removed annotation that Bug was owned by t...@debian.org.
Removed annotation that Bug was owned by t...@debian.org.
Removed annotation that Bug was owned by t...@debian.org.
Removed annotation that Bug was owned by t...@debian.org.
Removed annotation that Bug was owned by t...@debian.org.
Removed indication that 921299 affects src:librostlab-blast, src:frobby,
src:fltk1.3, src:libstxxl, src:bliss, src:toulbar2, src:primesieve,
src:qevercloud, and doxygen
Removed indication that 920459 affects src:librostlab-blast, src:libstxxl,
src:fltk1.3, src:toulbar2, src:bliss, src:frobby, src:qevercloud,
src:primesieve, and doxygen
Removed indication that 921779 affects doxygen, src:qevercloud, src:primesieve,
src:toulbar2, src:bliss, src:libstxxl, src:fltk1.3, src:frobby, and
src:librostlab-blast
Removed indication that 921783 affects doxygen, src:qevercloud, src:primesieve,
src:toulbar2, src:bliss, src:libstxxl, src:fltk1.3, src:frobby, and
src:librostlab-blast
Removed indication that 921789 affects src:frobby, src:bliss, src:toulbar2,
src:libstxxl, src:fltk1.3, src:librostlab-blast, doxygen, src:primesieve, and
src:qevercloud
Removed indication that 921802 affects src:frobby, src:bliss, src:toulbar2,
src:libstxxl, src:fltk1.3, src:librostlab-blast, doxygen, src:primesieve, and
src:qevercloud
Removed indication that 921838 affects doxygen, src:primesieve, src:qevercloud,
src:frobby, src:toulbar2, src:bliss, src:libstxxl, src:fltk1.3, and
src:librostlab-blast
Bug #920459 [texlive-latex-extra] tabu: breaks with color and/or xcolor when
spread or negative X coefficients are used
Marked as fixed in versions texlive-extra/2018.20190131-2.
Marked as fixed in versions texlive-extra/2018.20190131-2.
Marked as fixed in versions texlive-extra/2018.20190131-2.
Marked as fixed in versions texlive-extra/2018.20190131-2.
Marked as fixed in versions texlive-extra/2018.20190131-2.
Marked as fixed in versions texlive-extra/2018.20190131-2.
Marked as fixed in versions texlive-extra/2018.20190131-2.
Bug #920621 [texlive-latex-extra] texlive-base: breaks build of forthcoming
doxygen 1.8.15
Marked as fixed in versions texlive-extra/2018.20190131-2.
Marked as fixed in versions texlive-extra/2018.20190131-2.
Added tag(s) patch, ftbfs, sid, and buster.
Added tag(s) ftbfs, sid, buster, and patch.
Bug #921272 [texlive-latex-extra] texlive-latex-extra: package tabu broken when
xcolor is used
Bug #921779 [texlive-latex-extra] tabu: breaks with color and/or xcolor when
spread or negative X coefficients are used
Bug #921783 [texlive-latex-extra] tabu: breaks with color and/or xcolor when
spread or negative X coefficients are used
Bug #921789 [texlive-latex-extra] tabu: breaks with color and/or xcolor when
spread or negative X coefficients are used
Bug #921802 [texlive-latex-extra] tabu: breaks with color and/or xcolor when
spread or negative X coefficients are used
Bug #921838 [texlive-latex-extra] tabu: breaks with color and/or xcolor when
spread or negative X
Processed: delayed NMU, patch
Processing control commands: > tag -1 pending Bug #921757 [src:os-autoinst] os-autoinst: FTBFS (failing tests) Ignoring request to alter tags of bug #921757 to the same tags previously set -- 921757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: delayed NMU, patch
Processing control commands: > tag -1 pending Bug #921757 [src:os-autoinst] os-autoinst: FTBFS (failing tests) Added tag(s) pending. -- 921757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921757: delayed NMU, patch
control: tag -1 pending
Dear maintainer,
I have been able to reproduce the issue described by Santiago Vila on a
machine provided by him. I have also been able to use that machine to
produce two patches (different from what I provided above) that fix the
issue.
I have just NMU'd os-autoinst/4.5.1527308405.8b586d5-4.1 to DELAYED/5;
please feel free to reschedule or cancel my upload as you see fit. The
patches based on the current state of the debian/sid branch of the git
repository at salsa.debian.org
(180b0e19dfed3d2c7352144674844fa67b33f9d9) are attached to this mail.
Cheers,
-Hilko
>From 2baa6f6ab0ef62ef9b9ff4214f5470b323e84c6d Mon Sep 17 00:00:00 2001
From: Hilko Bengen
Date: Mon, 25 Feb 2019 20:00:01 +0100
Subject: [PATCH 1/2] Add patch to avoid race condition in osutils::runcmd
(Cloese: #921757)
---
...6-Eliminate-race-condition-in-runcmd.patch | 45 +++
...eck-module-files-that-start-with-a-d.patch | 28
debian/patches/series | 2 +
3 files changed, 75 insertions(+)
create mode 100644 debian/patches/0006-Eliminate-race-condition-in-runcmd.patch
create mode 100644 debian/patches/0007-Do-not-syntax-check-module-files-that-start-with-a-d.patch
diff --git a/debian/patches/0006-Eliminate-race-condition-in-runcmd.patch b/debian/patches/0006-Eliminate-race-condition-in-runcmd.patch
new file mode 100644
index ..c4d3e9bd
--- /dev/null
+++ b/debian/patches/0006-Eliminate-race-condition-in-runcmd.patch
@@ -0,0 +1,45 @@
+From: Hilko Bengen
+Date: Mon, 25 Feb 2019 09:47:35 +0100
+Subject: Eliminate race condition in runcmd
+
+---
+ osutils.pm | 16 ++--
+ 1 file changed, 6 insertions(+), 10 deletions(-)
+
+diff --git a/osutils.pm b/osutils.pm
+index b06a042..05423c3 100644
+--- a/osutils.pm
b/osutils.pm
+@@ -93,19 +93,10 @@ sub quote {
+ # Open a process to run external program and check its return status
+ sub runcmd {
+ diag "running " . join(' ', @_);
+-my ($pid, $status);
+-
+-local $SIG{CHLD} = sub {
+-local ($!, $?);
+-while ((my $child = waitpid(-1, WNOHANG)) > 0) {
+-diag "runcmd pid $pid returned $child";
+-$status = $?;
+-}
+-};
+
+ my ($wtr, $rdr, $err);
+ $err = gensym;
+-$pid = open3($wtr, $rdr, $err, @_);
++my $pid = open3($wtr, $rdr, $err, @_);
+ die "couldn't open: $!" unless defined $pid;
+ close($wtr) or die "couldn't close fh: $!";
+
+@@ -125,6 +116,11 @@ sub runcmd {
+ close($rdr) or die "couldn't close fh: $!";
+ close($err) or die "couldn't close fh: $!";
+
++my $status;
++waitpid $pid, 0;
++$status = $?;
++diag "runcmd pid $pid returned $status";
++
+ my $exit_code = $status >> 8;
+ die "runcmd failed with exit code $exit_code" unless ($exit_code == 0);
+ return $exit_code;
diff --git a/debian/patches/0007-Do-not-syntax-check-module-files-that-start-with-a-d.patch b/debian/patches/0007-Do-not-syntax-check-module-files-that-start-with-a-d.patch
new file mode 100644
index ..3d90d791
--- /dev/null
+++ b/debian/patches/0007-Do-not-syntax-check-module-files-that-start-with-a-d.patch
@@ -0,0 +1,28 @@
+From: Hilko Bengen
+Date: Mon, 25 Feb 2019 20:21:55 +0100
+Subject: Do not syntax-check module files that start with a dot (such as .pc)
+
+---
+ t/00-compile-check-all.t | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/t/00-compile-check-all.t b/t/00-compile-check-all.t
+index 41896f7..f344853 100755
+--- a/t/00-compile-check-all.t
b/t/00-compile-check-all.t
+@@ -36,6 +36,7 @@ my $test = Test::Compile->new();
+ my @files = $test->all_pm_files(".");
+
+ for my $file (@files) {
++next if ($file =~ /^[.]/);
+ next if ($file =~ /main.pm/);
+ $file =~ s,^\./,,;
+ $test->ok($test->pm_file_compiles($file), "Compile test for $file");
+@@ -43,6 +44,7 @@ for my $file (@files) {
+
+ @files = ('isotovideo', $test->all_pl_files("."));
+ for my $file (@files) {
++next if ($file =~ /^[.]/);
+ $test->ok($test->pl_file_compiles($file), "Compile test for $file");
+ }
+ $test->done_testing();
diff --git a/debian/patches/series b/debian/patches/series
index 9d5b44ef..23094b11 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -3,3 +3,5 @@
0003-adjust-to-avoid-ocr-test-failure.patch
0004-avoid-make-check-doc-failure.patch
0005-set-perl-path.patch
+0006-Eliminate-race-condition-in-runcmd.patch
+0007-Do-not-syntax-check-module-files-that-start-with-a-d.patch
--
2.20.1
>From 29c142a3ef51b12a7cf846a159c8a1a1797bad09 Mon Sep 17 00:00:00 2001
From: Hilko Bengen
Date: Mon, 25 Feb 2019 20:02:15 +0100
Subject: [PATCH 2/2] release
---
debian/changelog | 7 +++
1 file changed, 7 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index a4357aad..c55467d0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+os-autoinst (4.5.1527308405.8b586d5-4.1) unstable; urgency=medium
+
+ * Non-maintainer upload
+ * Add
Processed: severity of 913165 is grave
Processing commands for cont...@bugs.debian.org: > severity 913165 grave Bug #913165 [src:zziplib] CVE-2018-7727 CVE-2018-7726 CVE-2018-7725 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 913165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913165 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#920029: marked as done (python3-zope.proxy: ships header in /usr/include/python3.7/)
Your message dated Mon, 25 Feb 2019 18:50:56 + with message-id and subject line Bug#920029: fixed in zope.proxy 4.2.0-1.1 has caused the Debian Bug report #920029, regarding python3-zope.proxy: ships header in /usr/include/python3.7/ 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.) -- 920029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-zope.proxy Version: 4.2.0-1 Severity: serious Hi, your package ships the header file(s): /usr/include/python3.7/zope.proxy/proxy.h but /usr/include/python3.7 is a symlink to python3.7m in libpython3.7-dev. This may result in silent file overwrites or depending on the unpacking order /usr/include/python3.7 being a directory in some cases, separating the headers into two independent trees. These header files must be shipped in /usr/include/python3.7m/ instead. Please talk to the python maintainers to find a proper solution for handling the packaging of python header files in a future-proof way. Cheers, Andreas --- End Message --- --- Begin Message --- Source: zope.proxy Source-Version: 4.2.0-1.1 We believe that the bug you reported is fixed in the latest version of zope.proxy, 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 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominik George (supplier of updated zope.proxy 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: Sat, 23 Feb 2019 19:19:08 +0100 Source: zope.proxy Binary: python-zope.proxy python-zope.proxy-dbgsym python3-zope.proxy python3-zope.proxy-dbgsym Architecture: source amd64 Version: 4.2.0-1.1 Distribution: unstable Urgency: high Maintainer: Debian/Ubuntu Zope Team Changed-By: Dominik George Description: python-zope.proxy - Generic transparent proxies for Python python3-zope.proxy - Generic transparent proxies for Python Closes: 920029 Changes: zope.proxy (4.2.0-1.1) unstable; urgency=high . * Non-maintainer upload. * Move header files to correct location. (Closes: #920029) Checksums-Sha1: 2397e0d4145342c5233a45bfb20489495e1d5b6d 2379 zope.proxy_4.2.0-1.1.dsc 13d8bd2dbd03e76ebb63d5690937343c8902d439 4156 zope.proxy_4.2.0-1.1.debian.tar.xz b5921a2255ea6f8fde5b6eaf30f15cd7d6347c5d 25324 python-zope.proxy-dbgsym_4.2.0-1.1_amd64.deb 28b0e3ec81ddc259cd29eb49d921d0dd99a4be51 28576 python-zope.proxy_4.2.0-1.1_amd64.deb f9d0ebde54aec22af9129c47bc5332a74d4330f3 25972 python3-zope.proxy-dbgsym_4.2.0-1.1_amd64.deb 55420f790251e504c7a8d31d3dd72dc548ae1720 28172 python3-zope.proxy_4.2.0-1.1_amd64.deb 26355d483436bcbe9089fdde727504bcb2a4675f 8621 zope.proxy_4.2.0-1.1_amd64.buildinfo Checksums-Sha256: cc3cb15ce5ff4caa4cc9a5d576cd6c6541dd6bde52976e07c6f97c9f6492c581 2379 zope.proxy_4.2.0-1.1.dsc df596012cbfa4343c00e26ce6bd205a64d0efff7f4397a1d8c36ed9cc4132329 4156 zope.proxy_4.2.0-1.1.debian.tar.xz b71be6f85a2f3509eb4c293d9d117e33f14883815cf8008b2a81dabed5f06c15 25324 python-zope.proxy-dbgsym_4.2.0-1.1_amd64.deb d48f2cf8309520570de81653150eb022d52f3f9988d78c4f6900fd40a05e919e 28576 python-zope.proxy_4.2.0-1.1_amd64.deb ff70f9d9a960a51efc80e2b2056b953aa548ea8870777a44c6b27b19700f80e7 25972 python3-zope.proxy-dbgsym_4.2.0-1.1_amd64.deb c1031519d9420081d928a45b4b55837ab500143038bf1594167fac9911223843 28172 python3-zope.proxy_4.2.0-1.1_amd64.deb 0224308200efcb7b0ebe3d17bae1b52fc320af80d607e7a31110ed25d9fbd2a7 8621 zope.proxy_4.2.0-1.1_amd64.buildinfo Files: 64df6b87b83da3db185b223760bf3674 2379 zope optional zope.proxy_4.2.0-1.1.dsc b67aeb866fc61b102f2ac4b2e7c5c35c 4156 zope optional zope.proxy_4.2.0-1.1.debian.tar.xz d23729473dcbef3edac6ccd1f23be526 25324 debug optional python-zope.proxy-dbgsym_4.2.0-1.1_amd64.deb 71231e170a525ef6de05207dacb6b6e9 28576 zope optional python-zope.proxy_4.2.0-1.1_amd64.deb 581799f9a3c14fbdbe6fb56515e1030a 25972 debug optional python3-zope.proxy-dbgsym_4.2.0-1.1_amd64.deb 8064b3c7e3446d7dff2516df42c815bf 28172 zope optional python3-zope.proxy_4.2.0-1.1_amd64.deb 60b5f8ec069551a5d67ac83af48af371 8621 zope optional
Bug#893244: jruby FTBFS with openjdk-9
Hi Markus, On Sun, Feb 24, 2019 at 08:39:48PM +0100, Markus Koschany wrote: > JRuby is a mess. I guess we "just" need to package the latest upstream > release to fix the FTBFS bugs. Nobody felt like doing that in the past > twelve months, so I think it is unrealistic to believe we can make it > happen within one week. Of course if the release team can be convinced > to accept a new upstream release there might be additional time left. I agree, jruby is a mess, mostly because of me since I didn't have almost any time during this release cycle to work on it. I think jruby should be dropped from buster and a new libspring-java upload should be prepared shortly, to disable jruby support in it. It's not realistic to think that a new upstream release for jruby can be prepared in a week and that will work to be well supported during the next stable release life cycle. Cheers, Miguel. -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available at http://miguel.cc/key. "Faith means not wanting to know what is true." -- Nietzsche signature.asc Description: PGP signature
Processed: [bts-link] source package src:mdp
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:mdp > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #867515 (http://bugs.debian.org/867515) > # Bug title: mdp FTBFS with python 3.6 as supported version > # * https://github.com/mdp-toolkit/mdp-toolkit/issues/26 > # * remote status changed: open -> closed > # * closed upstream > tags 867515 + fixed-upstream Bug #867515 [src:mdp] mdp FTBFS with python 3.6 as supported version Added tag(s) fixed-upstream. > usertags 867515 - status-open Usertags were: status-open. Usertags are now: . > usertags 867515 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 867515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921762: need help
Control: tags -1 + upstream fixed-upstream On Wed, Feb 13, 2019 at 09:21:17PM +0800, Yanhao Mo wrote: > Control: tags -1 + confirmed help This seems to be fixed upstream: https://github.com/teejee2008/timeshift/issues/375 -- WBR, wRAR signature.asc Description: PGP signature
Processed: Re: Bug#921762: need help
Processing control commands: > tags -1 + upstream fixed-upstream Bug #921762 [src:timeshift] timeshift: FTBFS (error: The type name `AppExcludeEntry' could not be found) Added tag(s) fixed-upstream and upstream. -- 921762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#919344: adequate reports obsolete-conffile in openssh-client
Processing control commands: > severity -1 serious Bug #919344 [openssh-client] adequate reports obsolete-conffile in openssh-client Severity set to 'serious' from 'normal' -- 919344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919344 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#921838: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Mon, 25 Feb 2019 16:50:57 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190131-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ppl
Version: 1:1.2-7
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules binary-indep
dh binary-indep
dh_update_autotools_config -i
dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:152: installing './compile'
configure.ac:43: installing './missing'
[... snipped ...]
d on input line 40.
) (./group__PPL__C__interface.tex)
Underfull \vbox (badness 7740) has occurred while \output is active [17]
[18] (./group__Init.tex
Underfull \hbox (badness 1) detected at line 35
[][][]
Underfull \hbox (badness 1) detected at line 48
[][][]
[19]) [20] (./group__Version.tex [21]) [22] (./group__Error.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/omsptm.fd)
Overfull \hbox (1.62299pt too wide) in paragraph at lines 6--20
[][]\OT1/ptm/m/n/10 P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]O[]U[]T[][][][]O[]F[][]
[][]M[]E[]M[]O[]RY[][], [][]P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]I[]N[]V[]A[]L[]
I[]D[][][][]A[]R[]G[]U[]M[]E[]NT[][], [][]P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]D
[]O[]M[]
Overfull \hbox (1.35289pt too wide) in paragraph at lines 6--20
[][]\OT1/ptm/m/n/10 P[]P[]L[][][][]A[]R[]I[]T[]H[]M[]E[]T[]I[]C[][][][]O[]V[]E[
]R[]F[]L[]OW[][], [][]P[]P[]L[][][][]S[]T[]D[]I[]O[][][][]E[]R[]R[]OR[][], [][]
P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]I[]N[]T[]E[]R[]N[]A[]L[][][][]E[]R[]R[]OR[]
[], [][]P[]
! Missing } inserted.
}
l.88 \end{DoxyEnumFields}
?
! Emergency stop.
}
l.88 \end{DoxyEnumFields}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory
'/<>/doc/user-configured-c-interface.latex-dir'
make[2]: *** [Makefile:2064: ppl-user-configured-c-interface-1.2.pdf] Error 2
make[2]: Leaving directory '/<>/doc'
dh_auto_build: cd doc && make -j1 user-configured returned exit code 2
make[1]: *** [debian/rules:75: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:52: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ppl.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2018.20190131-2
We believe that the bug you reported is fixed in the latest version of
texlive-extra, 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 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated texlive-extra
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: SHA384
Format: 1.8
Date: Mon, 25 Feb 2019 10:59:38 +0900
Source: texlive-extra
Binary:
Bug#921783: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Mon, 25 Feb 2019 16:50:57 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190131-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:graphite2
Version: 1.3.13-7
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --with python3 --buildsystem=cmake --builddirectory=build
dh_update_autotools_config -i -O--buildsystem=cmake -O--builddirectory=build
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_BUILD_TYPE:STRING=Release
-DGRAPHITE2_NTRACING:BOOL=ON -DLIB_SUFFIX=/x86_64-linux-gnu
-DPYTHON_EXECUTABLE=/usr/bin/python3
cd build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles"
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu
-DCMAKE_BUILD_TYPE:STRING=Release -DGRAPHITE2_NTRACING:BOOL=ON
-DLIB_SUFFIX=/x86_64-linux-gnu -DPYTHON_EXECUTABLE=/usr/bin/python3 ..
-- Found PythonInterp: /usr/bin/python3 (found suitable version "3.7.2",
minimum required is "3.6")
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
[... snipped ...]
LaTeX Warning: Reference `Font_8h' on page 5 undefined on input line 3.
LaTeX Warning: Reference `Log_8h' on page 5 undefined on input line 4.
LaTeX Warning: Reference `Segment_8h' on page 5 undefined on input line 5.
LaTeX Warning: Reference `Types_8h' on page 5 undefined on input line 6.
) [5] [6]
Chapter 4.
(./structgr__face__ops.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd) [7])
(./structgr__faceinfo.tex
! Missing } inserted.
}
l.84 \end{DoxyEnumFields}
?
! Emergency stop.
}
l.84 \end{DoxyEnumFields}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[6]: *** [Makefile:6: refman.pdf] Error 1
make[6]: Leaving directory '/<>/build/doc/doxygen/latex'
make[5]: *** [doc/CMakeFiles/docs.dir/build.make:90:
doc/doxygen/latex/refman.pdf] Error 2
make[5]: Leaving directory '/<>/build'
make[4]: *** [CMakeFiles/Makefile2:1048: doc/CMakeFiles/docs.dir/all] Error 2
make[4]: Leaving directory '/<>/build'
make[3]: *** [CMakeFiles/Makefile2:1055: doc/CMakeFiles/docs.dir/rule] Error 2
make[3]: Leaving directory '/<>/build'
make[2]: *** [Makefile:412: docs] Error 2
make[2]: Leaving directory '/<>/build'
dh_auto_build: cd build && make -j1 docs returned exit code 2
make[1]: *** [debian/rules:14: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/graphite2.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2018.20190131-2
We believe that the bug you reported is fixed in the latest version of
texlive-extra, 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 920...@bugs.debian.org,
and the
Bug#921789: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Mon, 25 Feb 2019 16:50:57 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190131-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:librostlab-blast
Version: 1.0.1-9
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
dh_update_autotools_config -i
dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:7: installing './compile'
configure.ac:5: installing './missing'
[... snipped ...]
LaTeX Warning: Reference `blast-parser-parser_8h' on page 7 undefined on input
line 5.
LaTeX Warning: Reference `blast-parser-position_8h' on page 7 undefined on inpu
t line 6.
LaTeX Warning: Reference `blast-parser-stack_8h' on page 7 undefined on input l
ine 7.
LaTeX Warning: Reference `blast-result_8h' on page 7 undefined on input line 8.
) [7] [8]
Chapter 5.
(./namespacerostlab.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1phv.fd)
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/t1pcr.fd)
LaTeX Font Warning: Font shape `T1/pcr/bc/n' undefined
(Font) using `T1/pcr/m/n' instead on input line 27.
[9]) (./namespacerostlab_1_1blast.tex [10] [11] [12] [13] [14]
! Missing } inserted.
}
l.253 \end{DoxyParams}
?
! Emergency stop.
}
l.253 \end{DoxyParams}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
mv: cannot stat 'refman.pdf': No such file or directory
make[2]: *** [Makefile:902: ../doxygen-doc/librostlab-blast.pdf] Error 1
make[2]: Leaving directory '/<>/lib'
make[1]: *** [debian/rules:26: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/librostlab-blast.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2018.20190131-2
We believe that the bug you reported is fixed in the latest version of
texlive-extra, 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 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated texlive-extra
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: SHA384
Format: 1.8
Date: Mon, 25 Feb 2019 10:59:38 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils
texlive-fonts-extra texlive-fonts-extra-doc texlive-fonts-extra-links
texlive-formats-extra texlive-games texlive-humanities texlive-humanities-doc
texlive-latex-extra texlive-latex-extra-doc texlive-music texlive-plain-generic
texlive-pstricks texlive-pstricks-doc texlive-publishers texlive-publishers-doc
texlive-science texlive-science-doc
Architecture: source all
Version: 2018.20190131-2
Bug#921802: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Mon, 25 Feb 2019 16:50:57 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190131-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:primesieve
Version: 7.3+ds-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep --builddirectory=_build
dh_update_autotools_config -i -O--builddirectory=_build
dh_autoreconf -i -O--builddirectory=_build
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/primesieve-7.3+ds'
dh_auto_configure -- \
-DBUILD_TESTS=ON \
-DBUILD_EXAMPLES=ON \
-DBUILD_DOC=ON
cd _build && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DBUILD_TESTS=ON
-DBUILD_EXAMPLES=ON -DBUILD_DOC=ON ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
[... snipped ...]
LaTeX Warning: Reference `iterator_8h' on page 9 undefined on input line 3.
LaTeX Warning: Reference `iterator_8hpp' on page 9 undefined on input line 4.
LaTeX Warning: Reference `primesieve_8h' on page 9 undefined on input line 5.
LaTeX Warning: Reference `primesieve_8hpp' on page 9 undefined on input line 6.
LaTeX Warning: Reference `primesieve__error_8hpp' on page 9 undefined on input
line 7.
) [9] [10]
Chapter 6.
(./namespaceprimesieve.tex [11]
Underfull \hbox (badness 1) detected at line 94
[][][]
[12] [13]
Underfull \hbox (badness 1) detected at line 156
[][][]
! Missing } inserted.
}
l.175 \end{DoxyParams}
?
! Emergency stop.
}
l.175 \end{DoxyParams}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory
'/<>/primesieve-7.3+ds/_build/DEBIAN/doc/latex'
make[2]: *** [debian/adhoc/Makefile:15: doc] Error 2
make[2]: Leaving directory '/<>/primesieve-7.3+ds'
make[1]: *** [debian/rules:33: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>/primesieve-7.3+ds'
make: *** [debian/rules:24: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
status 2
(The above is just how the build ends and not necessarily the most relevant
part)
The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/primesieve.html
where you can get a full build log if you need it.
If this is really a bug in one of the build-depends, please use reassign and
affects,
so that this is still visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2018.20190131-2
We believe that the bug you reported is fixed in the latest version of
texlive-extra, 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 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated texlive-extra
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: SHA384
Format: 1.8
Date: Mon, 25 Feb 2019 10:59:38 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils
texlive-fonts-extra
Bug#921779: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Mon, 25 Feb 2019 16:50:57 + with message-id and subject line Bug#920459: fixed in texlive-extra 2018.20190131-2 has caused the Debian Bug report #920459, regarding tabu: breaks with color and/or xcolor when spread or negative X coefficients are used 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.) -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:doxygen Version: 1.8.13-10 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh_testdir /usr/bin/make -C jquery install make[1]: Entering directory '/<>/jquery' java -jar /usr/share/yui-compressor/yui-compressor.jar jquery-1.7.1.js > jquery-1.7.1-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.core.js > jquery.ui-1.8.18.core-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.widget.js > jquery.ui-1.8.18.widget-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.mouse.js > jquery.ui-1.8.18.mouse-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-1.8.18.resizable.js > jquery.ui-1.8.18.resizable-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ba-1.3-hashchange.js > jquery.ba-1.3-hashchange-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.scrollTo-1.4.2.js > jquery.scrollTo-1.4.2-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.powertip-1.2.0.js > jquery.powertip-1.2.0-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.ui-0.2.3.touch-punch.js > jquery.ui-0.2.3.touch-punch-min.js java -jar /usr/share/yui-compressor/yui-compressor.jar jquery.smartmenus-1.0.0.js > jquery.smartmenus-1.0.0-min.js [... snipped ...] [100%] Generating trouble.doc cd /<>/build/doc && /usr/bin/cmake -E copy /<>/doc/trouble.doc /<>/build/doc/ [100%] Generating xmlcmds.doc cd /<>/build/doc && /usr/bin/cmake -E copy /<>/doc/xmlcmds.doc /<>/build/doc/ [100%] Generating Latex and HTML documentation. cd /<>/build/doc && /<>/build/bin/doxygen This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=latex) restricted \write18 enabled. entering extended mode (./_formulas.tex LaTeX2e <2018-12-01> make[4]: Leaving directory '/<>/build' [100%] Built target run_doxygen /usr/bin/make -f doc/CMakeFiles/doxygen_pdf.dir/build.make doc/CMakeFiles/doxygen_pdf.dir/depend make[4]: Entering directory '/<>/build' cd /<>/build && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/doc /<>/build /<>/build/doc /<>/build/doc/CMakeFiles/doxygen_pdf.dir/DependInfo.cmake --color= Dependee "/<>/build/doc/CMakeFiles/doxygen_pdf.dir/DependInfo.cmake" is newer than depender "/<>/build/doc/CMakeFiles/doxygen_pdf.dir/depend.internal". Dependee "/<>/build/doc/CMakeFiles/CMakeDirectoryInformation.cmake" is newer than depender "/<>/build/doc/CMakeFiles/doxygen_pdf.dir/depend.internal". Scanning dependencies of target doxygen_pdf make[4]: Leaving directory '/<>/build' /usr/bin/make -f doc/CMakeFiles/doxygen_pdf.dir/build.make doc/CMakeFiles/doxygen_pdf.dir/build make[4]: Entering directory '/<>/build' [100%] Generating Doxygen Manual PDF. cd /<>/build/latex && /usr/bin/cmake -E remove refman.tex cd /<>/build/latex && /usr/bin/cmake -E copy /<>/build/doc/doxygen_manual.tex . cd /<>/build/latex && /usr/bin/cmake -E copy /<>/build/doc/manual.sty . cd /<>/build/latex && /usr/bin/epstopdf /<>/doc/doxygen_logo.eps --outfile=doxygen_logo.pdf cd /<>/build/latex && /usr/bin/pdflatex -shell-escape doxygen_manual.tex This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) (preloaded format=pdflatex) \write18 enabled. entering extended mode (./doxygen_manual.tex LaTeX2e <2018-12-01> make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:62: doc/CMakeFiles/doxygen_pdf] Error 1 make[4]: Leaving directory '/<>/build' make[3]: *** [CMakeFiles/Makefile2:445: doc/CMakeFiles/doxygen_pdf.dir/all] Error 2 make[3]: Leaving directory '/<>/build' make[2]: *** [CMakeFiles/Makefile2:484: doc/CMakeFiles/docs.dir/rule] Error 2 make[2]: Leaving directory '/<>/build' make[1]: *** [Makefile:301: docs] Error 2 make[1]: Leaving directory '/<>/build' make: *** [debian/rules:60: build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2
Bug#920459: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Mon, 25 Feb 2019 16:50:57 +
with message-id
and subject line Bug#920459: fixed in texlive-extra 2018.20190131-2
has caused the Debian Bug report #920459,
regarding tabu: breaks with color and/or xcolor when spread or negative X
coefficients are used
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.)
--
920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:toulbar2
Version: 1.0.0+dfsg3-1.1
Severity: serious
Tags: sid buster
toulbar2 ftbfs in unstable
[...]
*geometry* driver: auto-detecting
*geometry* detected driver: pdftex
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/gettitlestring.sty))
[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./index.tex
(/usr/share/texlive/texmf-dist/tex/latex/wasysym/uwasy.fd)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsa.fd)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/umsb.fd)
! Missing } inserted.
}
l.7 \end{longtabu}
?
! Emergency stop.
}
l.7 \end{longtabu}
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[4]: *** [Makefile:6: refman.pdf] Error 1
make[4]: Leaving directory
'/<>/toulbar2-1.0.0+dfsg3/obj-x86_64-linux-gnu/latex'
make[3]: *** [CMakeFiles/doc.dir/build.make:71: doc] Error 2
make[3]: Leaving directory
'/<>/toulbar2-1.0.0+dfsg3/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:76: CMakeFiles/doc.dir/all] Error 2
[...]
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2018.20190131-2
We believe that the bug you reported is fixed in the latest version of
texlive-extra, 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 920...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Norbert Preining (supplier of updated texlive-extra
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: SHA384
Format: 1.8
Date: Mon, 25 Feb 2019 10:59:38 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils
texlive-fonts-extra texlive-fonts-extra-doc texlive-fonts-extra-links
texlive-formats-extra texlive-games texlive-humanities texlive-humanities-doc
texlive-latex-extra texlive-latex-extra-doc texlive-music texlive-plain-generic
texlive-pstricks texlive-pstricks-doc texlive-publishers texlive-publishers-doc
texlive-science texlive-science-doc
Architecture: source all
Version: 2018.20190131-2
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers
Changed-By: Norbert Preining
Description:
texlive-bibtex-extra - TeX Live: BibTeX additional styles
texlive-extra-utils - TeX Live: TeX auxiliary programs
texlive-font-utils - TeX Live: Graphics and font utilities
texlive-fonts-extra - TeX Live: Additional fonts
texlive-fonts-extra-doc - TeX Live: Documentation files for texlive-fonts-extra
texlive-fonts-extra-links - TeX Live:
texlive-formats-extra - TeX Live: Additional formats
texlive-games - TeX Live: Games typesetting
texlive-humanities - TeX Live: Humanities packages
texlive-humanities-doc - TeX Live: Documentation files for texlive-humanities
texlive-latex-extra - TeX Live: LaTeX additional packages
texlive-latex-extra-doc - TeX Live: Documentation files for texlive-latex-extra
texlive-music - TeX Live: Music packages
texlive-plain-generic - TeX Live: Plain (La)TeX packages
texlive-pstricks - TeX Live: PSTricks
texlive-pstricks-doc - TeX Live: Documentation files for texlive-pstricks
texlive-publishers - TeX Live: Publisher styles, theses, etc.
texlive-publishers-doc - TeX Live: Documentation files for texlive-publishers
texlive-science - TeX Live: Mathematics, natural sciences, computer science
package
texlive-science-doc - TeX Live: Documentation files for texlive-science
Closes: 920459 921653 922305
Changes:
texlive-extra (2018.20190131-2) unstable; urgency=medium
.
* recommend liblog-log4perl-perl for latexindent (Closes: #922305)
* blacklist docindex.sty, non-functional (Closes: #921653)
* Patch tabu to fix
Bug#921299: marked as done (tabu: breaks with color and/or xcolor when spread or negative X coefficients are used)
Your message dated Mon, 25 Feb 2019 16:50:57 + with message-id and subject line Bug#920459: fixed in texlive-extra 2018.20190131-2 has caused the Debian Bug report #920459, regarding tabu: breaks with color and/or xcolor when spread or negative X coefficients are used 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.) -- 920459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920459 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: caffe Severity: serious Dear Maintainer, I tested your package against a draft package for doxygen 1.8.15: https://bugs.debian.org/919413 and it FTBFS with this error: ! LaTeX Error: File `listofitems.sty' not found. Paolo -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled ~ --- End Message --- --- Begin Message --- Source: texlive-extra Source-Version: 2018.20190131-2 We believe that the bug you reported is fixed in the latest version of texlive-extra, 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 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Norbert Preining (supplier of updated texlive-extra 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: SHA384 Format: 1.8 Date: Mon, 25 Feb 2019 10:59:38 +0900 Source: texlive-extra Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils texlive-fonts-extra texlive-fonts-extra-doc texlive-fonts-extra-links texlive-formats-extra texlive-games texlive-humanities texlive-humanities-doc texlive-latex-extra texlive-latex-extra-doc texlive-music texlive-plain-generic texlive-pstricks texlive-pstricks-doc texlive-publishers texlive-publishers-doc texlive-science texlive-science-doc Architecture: source all Version: 2018.20190131-2 Distribution: unstable Urgency: medium Maintainer: Debian TeX Maintainers Changed-By: Norbert Preining Description: texlive-bibtex-extra - TeX Live: BibTeX additional styles texlive-extra-utils - TeX Live: TeX auxiliary programs texlive-font-utils - TeX Live: Graphics and font utilities texlive-fonts-extra - TeX Live: Additional fonts texlive-fonts-extra-doc - TeX Live: Documentation files for texlive-fonts-extra texlive-fonts-extra-links - TeX Live: texlive-formats-extra - TeX Live: Additional formats texlive-games - TeX Live: Games typesetting texlive-humanities - TeX Live: Humanities packages texlive-humanities-doc - TeX Live: Documentation files for texlive-humanities texlive-latex-extra - TeX Live: LaTeX additional packages texlive-latex-extra-doc - TeX Live: Documentation files for texlive-latex-extra texlive-music - TeX Live: Music packages texlive-plain-generic - TeX Live: Plain (La)TeX packages texlive-pstricks - TeX Live: PSTricks texlive-pstricks-doc - TeX Live: Documentation files for texlive-pstricks texlive-publishers - TeX Live: Publisher styles, theses, etc. texlive-publishers-doc - TeX Live: Documentation files for texlive-publishers texlive-science - TeX Live: Mathematics, natural sciences, computer science package texlive-science-doc - TeX Live: Documentation files for texlive-science Closes: 920459 921653 922305 Changes: texlive-extra (2018.20190131-2) unstable; urgency=medium . * recommend liblog-log4perl-perl for latexindent (Closes: #922305) * blacklist docindex.sty, non-functional (Closes: #921653) * Patch tabu to fix multiple FTBFS in other packages (Closes: #920459) (Thanks Thorsten Glaser) Checksums-Sha1: 771aff1d2988509f5d76cd86be53b290b067713e 3775 texlive-extra_2018.20190131-2.dsc 29072c672c97e66362dc1f71e17c8fc0f813256e 162896 texlive-extra_2018.20190131-2.debian.tar.xz 1d5d3773437ec0e9b3beea4f9a40fbf515279603 63484424
Processed: severity of 923198 is wishlist, retitle 923198 to Add elogind support to Recommends:
Processing commands for cont...@bugs.debian.org: > severity 923198 wishlist Bug #923198 [xserver-xorg-core] xserver-xorg-core: false direct dependency on libpam-systemd Severity set to 'wishlist' from 'serious' > retitle 923198 Add elogind support to Recommends: Bug #923198 [xserver-xorg-core] xserver-xorg-core: false direct dependency on libpam-systemd Changed Bug title to 'Add elogind support to Recommends:' from 'xserver-xorg-core: false direct dependency on libpam-systemd'. > thanks Stopping processing here. Please contact me if you need assistance. -- 923198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 923201 is wishlist, retitle 923201 to Add elogind support to Recommends:
Processing commands for cont...@bugs.debian.org: > severity 923201 wishlist Bug #923201 [pulseaudio] pulseaudio has a false dependency on libpam-systemd Severity set to 'wishlist' from 'serious' > retitle 923201 Add elogind support to Recommends: Bug #923201 [pulseaudio] pulseaudio has a false dependency on libpam-systemd Changed Bug title to 'Add elogind support to Recommends:' from 'pulseaudio has a false dependency on libpam-systemd'. > thanks Stopping processing here. Please contact me if you need assistance. -- 923201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923206: marked as done (RM: memleax -- RoM; NPOASR; abandoned upstream; a better option exists)
Your message dated Mon, 25 Feb 2019 15:34:29 + with message-id and subject line Bug#923205: Removed package(s) from unstable has caused the Debian Bug report #923206, regarding RM: memleax -- RoM; NPOASR; abandoned upstream; a better option exists 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.) -- 923206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923206 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: memleax Severity: serious Justification: NPOASR; abandoned upstream; a better alternative exists Removal bug for unstable has been filed against ftp.debian.org (#923205), and I am filing this one so the package will be dropped from testing asap. --- End Message --- --- Begin Message --- Version: 1.1.1-1+rm Dear submitter, as the package memleax has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/923205 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#896321: marked as done (python-tornado-pyvows: tornado_pyvows fails to import)
Your message dated Mon, 25 Feb 2019 15:29:37 +
with message-id
and subject line Bug#923192: Removed package(s) from unstable
has caused the Debian Bug report #896321,
regarding python-tornado-pyvows: tornado_pyvows fails to import
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.)
--
896321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-tornado-pyvows
Version: 0.6.1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import
After installing python-tornado-pyvows importing the module tornado_pyvows
into a python interpreter fails with the following error:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/tornado_pyvows/__init__.py", line 13,
in
from .context import (
File "/usr/lib/python2.7/dist-packages/tornado_pyvows/context.py", line 20,
in
from tornado.testing import get_unused_port
ImportError: cannot import name get_unused_port
The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.
Helmut
--- End Message ---
--- Begin Message ---
Version: 0.6.1-1+rm
Dear submitter,
as the package tornado-pyvows has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/923192
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#841428: marked as done (tornado-pyvows: FTBFS: ValueError: No JSON object could be decoded)
Your message dated Mon, 25 Feb 2019 15:29:37 +
with message-id
and subject line Bug#923192: Removed package(s) from unstable
has caused the Debian Bug report #841428,
regarding tornado-pyvows: FTBFS: ValueError: No JSON object could be decoded
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.)
--
841428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tornado-pyvows
Version: 0.6.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
tornado-pyvows fails to build from source in unstable/amd64:
[…]
/usr/bin/make test
make[2]: Entering directory
'/home/lamby/temp/cdt.20161020163609.4UfnyHb5wN.db.tornado-pyvows/tornado-pyvows-0.6.1'
INFO:tornado.access:200 GET / (127.0.0.1) 0.50ms
INFO:tornado.access:200 GET / (127.0.0.1) 0.28ms
INFO:tornado.access:200 POST / (127.0.0.1) 0.26ms
INFO:tornado.access:200 GET /echo (127.0.0.1) 0.34ms
INFO:tornado.access:200 GET /echo (127.0.0.1) 0.30ms
INFO:tornado.access:200 GET /echo (127.0.0.1) 0.34ms
INFO:tornado.access:200 POST / (127.0.0.1) 0.38ms
INFO:tornado.access:204 HEAD / (127.0.0.1) 0.25ms
INFO:tornado.access:200 GET / (127.0.0.1) 0.25ms
INFO:tornado.access:200 POST / (127.0.0.1) 0.41ms
INFO:tornado.access:200 POST / (127.0.0.1) 0.31ms
INFO:tornado.access:200 POST / (127.0.0.1) 0.36ms
INFO:tornado.access:200 POST / (127.0.0.1) 0.42ms
INFO:tornado.access:200 GET / (127.0.0.1) 0.25ms
INFO:tornado.access:200 GET /echo (127.0.0.1) 0.35ms
INFO:tornado.access:200 GET /echo (127.0.0.1) 0.30ms
Vows Results
Post
Error in topic:
No JSON object could be decoded
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/pyvows/runner/gevent.py", line
141, in _run_setup_and_topic
topic = topic_func(*topic_list)
File
"/home/lamby/temp/cdt.20161020163609.4UfnyHb5wN.db.tornado-pyvows/tornado-pyvows-0.6.1/vows/client_vows.py",
line 25, in topic
requestbin_id = json.loads(response.body)['name']
File "/usr/lib/python2.7/json/__init__.py", line 339, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
✗ OK » 63 honored • 1 broken • 94 skipped (0.112441s)
Makefile:3: recipe for target 'test' failed
make[2]: *** [test] Error 1
make[2]: Leaving directory
'/home/lamby/temp/cdt.20161020163609.4UfnyHb5wN.db.tornado-pyvows/tornado-pyvows-0.6.1'
debian/rules:7: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory
'/home/lamby/temp/cdt.20161020163609.4UfnyHb5wN.db.tornado-pyvows/tornado-pyvows-0.6.1'
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
[…]
The full build log is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
tornado-pyvows.0.6.1-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 0.6.1-1+rm
Dear submitter,
as the package tornado-pyvows has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/923192
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#922730: cannot browse anything
On Thu, 21 Feb 2019 14:01:45 +0200 Alberto Garcia wrote: > If would also be nice if you can get a backtrace. > > Berto And use G_DEBUG=fatal-warnings to get it as early as possible.
Bug#918164: marked as done (Broken with Thunderbird 60)
Your message dated Mon, 25 Feb 2019 15:28:56 + with message-id and subject line Bug#923141: Removed package(s) from unstable has caused the Debian Bug report #918164, regarding Broken with Thunderbird 60 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.) -- 918164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xul-ext-timeline Version: 0.5-5 Severity: grave The plugin is broken with Thunderbird 60 in stretch and sid, after installation it's disabled and only prints "Timeline is incompatible with Thunderbird 60.4". TB 60 was uploaded to stretch over two months ago (and three months ago to sid), given that noone filed a bug so far, it makes me wonder whether this package is used at all... Cheers, Moritz --- End Message --- --- Begin Message --- Version: 0.5-5+rm Dear submitter, as the package timeline has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/923141 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org: > forcemerge 923208 877122 Bug #923208 [libengine-pkcs11-openssl] libengine-pkcs11-openssl: libengines-pkcs11-openssl is installing to the wrong engine directory on x86 Unable to merge bugs because: package of #877122 is 'libengine-pkcs11-openssl1.1' not 'libengine-pkcs11-openssl' Failed to forcibly merge 923208: Did not alter merged bugs. > End of message, stopping processing here. Please contact me if you need assistance. -- 877122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877122 923208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org: > merge 923208 877122 Bug #923208 [libengine-pkcs11-openssl] libengine-pkcs11-openssl: libengines-pkcs11-openssl is installing to the wrong engine directory on x86 Unable to merge bugs because: package of #877122 is 'libengine-pkcs11-openssl1.1' not 'libengine-pkcs11-openssl' Failed to merge 923208: Did not alter merged bugs. > End of message, stopping processing here. Please contact me if you need assistance. -- 877122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877122 923208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing
By keeping this out of testing you are really leaving those of us running it and depending on it in a real mess. To get rails 2.5 support I had to do some serious Debian badness, this really sucks, couldn’t it just be kept out of backports if that is the issue instead of causing harm to those of us that were happy with it? Not I have 3 companies that depends on this install that are all up a creek and I can’t even convert to omni (ce) cause you can’t restore a backup of a different version and type (Don’t get me started on this part). So those of us that happy using it and are now totally FUBARed, what’s the plan for us while everyone complains and discusses things and we have completely unusable installs now? Testing is for testing things after all, how could it go any place if it’s not being tested? Stable is always too old, heck it has rails 2.3 for heavens sake and php7.0. Testing is more work but it’s were I choose to run things so I can stay relevant, and in all my years running testing (over 15 years) I have never had a major package just get pulled. I couldn’t use the back ports version since it required rails 2.3, so I had to go to experimental which is nuts. Pirate Praveen has been doing a great job trying to keep up with countless depends and keeping things up to date and stable and now he is being blocked and in turn breaking every install of testing out there. This is just insane!! This ticket is bogus and should be closed and removed so that gitlab can be fixed in testing and restore the faith of its users.
Bug#905214: marked as done (isc-kea: Incomplete debian/copyright?)
Your message dated Mon, 25 Feb 2019 14:42:04 +
with message-id
and subject line Bug#905214: fixed in isc-kea 1.5.0-1
has caused the Debian Bug report #905214,
regarding isc-kea: Incomplete debian/copyright?
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.)
--
905214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: isc-kea
Version: 1.4.0.P1-3
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Ondřej Surý , ftpmas...@debian.org
Hi,
I just ACCEPTed isc-kea from NEW but noticed it was missing
attribution in debian/copyright for at least the files under
src/lib/dhcpsrv/benchmarks.
This is in no way exhaustive so please check over the entire package
carefully and address these on your next upload. :)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--- End Message ---
--- Begin Message ---
Source: isc-kea
Source-Version: 1.5.0-1
We believe that the bug you reported is fixed in the latest version of
isc-kea, 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 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý (supplier of updated isc-kea package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 25 Feb 2019 12:12:36 +
Source: isc-kea
Binary: kea-admin kea-admin-dbgsym kea-common kea-common-dbgsym kea-ctrl-agent
kea-ctrl-agent-dbgsym kea-dev kea-dhcp-ddns-server kea-dhcp-ddns-server-dbgsym
kea-dhcp4-server kea-dhcp4-server-dbgsym kea-dhcp6-server
kea-dhcp6-server-dbgsym kea-doc python3-kea-connector
Architecture: source amd64 all
Version: 1.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Kea
Changed-By: Ondřej Surý
Description:
kea-admin - Administration utilities for ISC KEA DHCP server
kea-common - Common libraries for the ISC KEA DHCP server
kea-ctrl-agent - ISC KEA DHCP server REST API service
kea-dev- Development headers for ISC KEA DHCP server
kea-dhcp-ddns-server - ISC KEA DHCP Dynamic DNS service
kea-dhcp4-server - ISC KEA IPv4 DHCP server
kea-dhcp6-server - ISC KEA IPv6 DHCP server
kea-doc- Documentation for ISC KEA DHCP server
python3-kea-connector - Python3 management connector for ISC KEA DHCP server
Closes: 905214 905421 905977 908491 910671 916288
Changes:
isc-kea (1.5.0-1) unstable; urgency=medium
.
[ Ondřej Surý ]
* New upstream version 1.5.0 (Closes: #916288)
* Update d/watch to use better mangling and https:// URL
* Update ISC signing key
* Bump debhelper compat level to v12
* Fix some default paths to use runstatedir
* Create a non-privileged user _kea and run the Kea services under that user
(Closes: #910671)
* Add the netconf stuff to d/not-installed
* Greatly simplify d/copyright (Closes: #905214)
* Fix dpkg-statoverride usage in maintscripts
* Add adduser to kea-common Depends
* Add Pre-Depends: ${misc:Pre-Depends} for systemd Pre-Depends
* DHCPv4 daemon also needs CAP_NET_RAW
* It's Kea, not ISC KEA; fix the .service files
.
[ Yuval Freund ]
* Fix python dep issue. (Closes: #905977, #908491)
.
[ Badreddin Aboubakr ]
* Fix systemd Unit Files
+ Change lock directory (systemd nesting issue)
+ Quote RuntimeDirectory
+ Remove "LogsDirectory" and "LogsDirectoryMode" (they are not
supported in systemd 232)
.
[ Jason Guy ]
* Added a new patch to fix the kea-admin script.
* Fixed the postrm script (Closes: #905421)
Checksums-Sha1:
4bc943627611f1aea8102c4d412d160eaf98bf54 2749 isc-kea_1.5.0-1.dsc
e073afb273f17c47be68dc089b718255b003ac6b 7395257 isc-kea_1.5.0.orig.tar.gz
680dd33f366f8a5f5bfa6ed2ad02e46feca70ce4 30688 isc-kea_1.5.0-1.debian.tar.xz
8ea539a47530c048fb9282155f397fe89b4a8407 13193 isc-kea_1.5.0-1_amd64.buildinfo
3156f2894b8504e89700290df7a8a3bd5fc7293f 2058872
kea-admin-dbgsym_1.5.0-1_amd64.deb
77f4c01d38b6cf810691ffaa7735e0d3da368d19 316008 kea-admin_1.5.0-1_amd64.deb
55481e66dd4ea05a02b09d6f896f0d97b174a11c 42410896
kea-common-dbgsym_1.5.0-1_amd64.deb
Bug#905421: marked as done (kea-common: fails to remove: dpkg-statoverride: error: unknown option --remote)
Your message dated Mon, 25 Feb 2019 14:42:04 +
with message-id
and subject line Bug#905421: fixed in isc-kea 1.5.0-1
has caused the Debian Bug report #905421,
regarding kea-common: fails to remove: dpkg-statoverride: error: unknown option
--remote
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.)
--
905421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kea-common
Version: 1.4.0.P1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to remove.
>From the attached log (scroll to the bottom...):
Purging configuration files for kea-common (1.4.0.P1-3) ...
dpkg-statoverride: error: unknown option --remote
Use --help for help about overriding file stat information.
dpkg: error processing package kea-common (--purge):
installed kea-common package post-removal script subprocess returned error
exit status 2
Errors were encountered while processing:
kea-common
cheers,
Andreas
kea-common_1.4.0.P1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: isc-kea
Source-Version: 1.5.0-1
We believe that the bug you reported is fixed in the latest version of
isc-kea, 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 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý (supplier of updated isc-kea package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 25 Feb 2019 12:12:36 +
Source: isc-kea
Binary: kea-admin kea-admin-dbgsym kea-common kea-common-dbgsym kea-ctrl-agent
kea-ctrl-agent-dbgsym kea-dev kea-dhcp-ddns-server kea-dhcp-ddns-server-dbgsym
kea-dhcp4-server kea-dhcp4-server-dbgsym kea-dhcp6-server
kea-dhcp6-server-dbgsym kea-doc python3-kea-connector
Architecture: source amd64 all
Version: 1.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Kea
Changed-By: Ondřej Surý
Description:
kea-admin - Administration utilities for ISC KEA DHCP server
kea-common - Common libraries for the ISC KEA DHCP server
kea-ctrl-agent - ISC KEA DHCP server REST API service
kea-dev- Development headers for ISC KEA DHCP server
kea-dhcp-ddns-server - ISC KEA DHCP Dynamic DNS service
kea-dhcp4-server - ISC KEA IPv4 DHCP server
kea-dhcp6-server - ISC KEA IPv6 DHCP server
kea-doc- Documentation for ISC KEA DHCP server
python3-kea-connector - Python3 management connector for ISC KEA DHCP server
Closes: 905214 905421 905977 908491 910671 916288
Changes:
isc-kea (1.5.0-1) unstable; urgency=medium
.
[ Ondřej Surý ]
* New upstream version 1.5.0 (Closes: #916288)
* Update d/watch to use better mangling and https:// URL
* Update ISC signing key
* Bump debhelper compat level to v12
* Fix some default paths to use runstatedir
* Create a non-privileged user _kea and run the Kea services under that user
(Closes: #910671)
* Add the netconf stuff to d/not-installed
* Greatly simplify d/copyright (Closes: #905214)
* Fix dpkg-statoverride usage in maintscripts
* Add adduser to kea-common Depends
* Add Pre-Depends: ${misc:Pre-Depends} for systemd Pre-Depends
* DHCPv4 daemon also needs CAP_NET_RAW
* It's Kea, not ISC KEA; fix the .service files
.
[ Yuval Freund ]
* Fix python dep issue. (Closes: #905977, #908491)
.
[ Badreddin Aboubakr ]
* Fix systemd Unit Files
+ Change lock directory (systemd nesting issue)
+ Quote RuntimeDirectory
+ Remove "LogsDirectory" and "LogsDirectoryMode" (they are not
supported in systemd 232)
.
[ Jason Guy ]
* Added a new patch to fix the kea-admin script.
* Fixed the postrm script (Closes: #905421)
Checksums-Sha1:
4bc943627611f1aea8102c4d412d160eaf98bf54 2749 isc-kea_1.5.0-1.dsc
e073afb273f17c47be68dc089b718255b003ac6b 7395257 isc-kea_1.5.0.orig.tar.gz
680dd33f366f8a5f5bfa6ed2ad02e46feca70ce4 30688 isc-kea_1.5.0-1.debian.tar.xz
8ea539a47530c048fb9282155f397fe89b4a8407 13193 isc-kea_1.5.0-1_amd64.buildinfo
3156f2894b8504e89700290df7a8a3bd5fc7293f 2058872
Bug#905977: marked as done (kea-ctrl-agent: missing dependency on python3)
Your message dated Mon, 25 Feb 2019 14:42:04 +
with message-id
and subject line Bug#905977: fixed in isc-kea 1.5.0-1
has caused the Debian Bug report #905977,
regarding kea-ctrl-agent: missing dependency on python3
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.)
--
905977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kea-ctrl-agent
Version: 1.4.0.P1-3
Severity: serious
kea-ctrl-agent lacks a python3 dependency
for /usr/sbin/kea-shell
This can be fixed by adding dh-python to the build dependencies
plus python3 to the "dh $@ --with" in debian/rules.
--- End Message ---
--- Begin Message ---
Source: isc-kea
Source-Version: 1.5.0-1
We believe that the bug you reported is fixed in the latest version of
isc-kea, 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 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý (supplier of updated isc-kea package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 25 Feb 2019 12:12:36 +
Source: isc-kea
Binary: kea-admin kea-admin-dbgsym kea-common kea-common-dbgsym kea-ctrl-agent
kea-ctrl-agent-dbgsym kea-dev kea-dhcp-ddns-server kea-dhcp-ddns-server-dbgsym
kea-dhcp4-server kea-dhcp4-server-dbgsym kea-dhcp6-server
kea-dhcp6-server-dbgsym kea-doc python3-kea-connector
Architecture: source amd64 all
Version: 1.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Kea
Changed-By: Ondřej Surý
Description:
kea-admin - Administration utilities for ISC KEA DHCP server
kea-common - Common libraries for the ISC KEA DHCP server
kea-ctrl-agent - ISC KEA DHCP server REST API service
kea-dev- Development headers for ISC KEA DHCP server
kea-dhcp-ddns-server - ISC KEA DHCP Dynamic DNS service
kea-dhcp4-server - ISC KEA IPv4 DHCP server
kea-dhcp6-server - ISC KEA IPv6 DHCP server
kea-doc- Documentation for ISC KEA DHCP server
python3-kea-connector - Python3 management connector for ISC KEA DHCP server
Closes: 905214 905421 905977 908491 910671 916288
Changes:
isc-kea (1.5.0-1) unstable; urgency=medium
.
[ Ondřej Surý ]
* New upstream version 1.5.0 (Closes: #916288)
* Update d/watch to use better mangling and https:// URL
* Update ISC signing key
* Bump debhelper compat level to v12
* Fix some default paths to use runstatedir
* Create a non-privileged user _kea and run the Kea services under that user
(Closes: #910671)
* Add the netconf stuff to d/not-installed
* Greatly simplify d/copyright (Closes: #905214)
* Fix dpkg-statoverride usage in maintscripts
* Add adduser to kea-common Depends
* Add Pre-Depends: ${misc:Pre-Depends} for systemd Pre-Depends
* DHCPv4 daemon also needs CAP_NET_RAW
* It's Kea, not ISC KEA; fix the .service files
.
[ Yuval Freund ]
* Fix python dep issue. (Closes: #905977, #908491)
.
[ Badreddin Aboubakr ]
* Fix systemd Unit Files
+ Change lock directory (systemd nesting issue)
+ Quote RuntimeDirectory
+ Remove "LogsDirectory" and "LogsDirectoryMode" (they are not
supported in systemd 232)
.
[ Jason Guy ]
* Added a new patch to fix the kea-admin script.
* Fixed the postrm script (Closes: #905421)
Checksums-Sha1:
4bc943627611f1aea8102c4d412d160eaf98bf54 2749 isc-kea_1.5.0-1.dsc
e073afb273f17c47be68dc089b718255b003ac6b 7395257 isc-kea_1.5.0.orig.tar.gz
680dd33f366f8a5f5bfa6ed2ad02e46feca70ce4 30688 isc-kea_1.5.0-1.debian.tar.xz
8ea539a47530c048fb9282155f397fe89b4a8407 13193 isc-kea_1.5.0-1_amd64.buildinfo
3156f2894b8504e89700290df7a8a3bd5fc7293f 2058872
kea-admin-dbgsym_1.5.0-1_amd64.deb
77f4c01d38b6cf810691ffaa7735e0d3da368d19 316008 kea-admin_1.5.0-1_amd64.deb
55481e66dd4ea05a02b09d6f896f0d97b174a11c 42410896
kea-common-dbgsym_1.5.0-1_amd64.deb
dc2d1fd97165d1a8a58a7bba40ace3b0340a3ed5 2583168 kea-common_1.5.0-1_amd64.deb
b19ef045855d50ba41e7ae12f29152c503de8d81 1443484
kea-ctrl-agent-dbgsym_1.5.0-1_amd64.deb
aa5391669234545071a11b77ea6909f20ee73139 270072
kea-ctrl-agent_1.5.0-1_amd64.deb
0db873dac8dafc6d0015ad574dccd94191f3127d 675116
Bug#908491: marked as done (kea-shell missing modules)
Your message dated Mon, 25 Feb 2019 14:42:04 +
with message-id
and subject line Bug#908491: fixed in isc-kea 1.5.0-1
has caused the Debian Bug report #908491,
regarding kea-shell missing modules
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.)
--
908491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kea-ctrl-agent
Version: 1.4.0.P1-3
Severity: normal
Traceback (most recent call last):
File "/usr/sbin/kea-shell", line 27, in
from kea_conn import CARequest # CAResponse
ImportError: No module named 'kea_conn'
-- System Information:
Debian Release: 9.3
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages kea-ctrl-agent depends on:
ii kea-common 1.4.0.P1-3
ii libboost-system1.62.0 1.62.0+dfsg-4
ii libc6 2.24-11+deb9u1
ii libgcc11:6.3.0-18
ii libstdc++6 8.2.0-6
ii lsb-base 9.20161125
kea-ctrl-agent recommends no packages.
Versions of packages kea-ctrl-agent suggests:
ii kea-doc 1.3.0-1
-- Configuration Files:
/etc/kea/kea-ctrl-agent.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: isc-kea
Source-Version: 1.5.0-1
We believe that the bug you reported is fixed in the latest version of
isc-kea, 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 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Surý (supplier of updated isc-kea package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 25 Feb 2019 12:12:36 +
Source: isc-kea
Binary: kea-admin kea-admin-dbgsym kea-common kea-common-dbgsym kea-ctrl-agent
kea-ctrl-agent-dbgsym kea-dev kea-dhcp-ddns-server kea-dhcp-ddns-server-dbgsym
kea-dhcp4-server kea-dhcp4-server-dbgsym kea-dhcp6-server
kea-dhcp6-server-dbgsym kea-doc python3-kea-connector
Architecture: source amd64 all
Version: 1.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Kea
Changed-By: Ondřej Surý
Description:
kea-admin - Administration utilities for ISC KEA DHCP server
kea-common - Common libraries for the ISC KEA DHCP server
kea-ctrl-agent - ISC KEA DHCP server REST API service
kea-dev- Development headers for ISC KEA DHCP server
kea-dhcp-ddns-server - ISC KEA DHCP Dynamic DNS service
kea-dhcp4-server - ISC KEA IPv4 DHCP server
kea-dhcp6-server - ISC KEA IPv6 DHCP server
kea-doc- Documentation for ISC KEA DHCP server
python3-kea-connector - Python3 management connector for ISC KEA DHCP server
Closes: 905214 905421 905977 908491 910671 916288
Changes:
isc-kea (1.5.0-1) unstable; urgency=medium
.
[ Ondřej Surý ]
* New upstream version 1.5.0 (Closes: #916288)
* Update d/watch to use better mangling and https:// URL
* Update ISC signing key
* Bump debhelper compat level to v12
* Fix some default paths to use runstatedir
* Create a non-privileged user _kea and run the Kea services under that user
(Closes: #910671)
* Add the netconf stuff to d/not-installed
* Greatly simplify d/copyright (Closes: #905214)
* Fix dpkg-statoverride usage in maintscripts
* Add adduser to kea-common Depends
* Add Pre-Depends: ${misc:Pre-Depends} for systemd Pre-Depends
* DHCPv4 daemon also needs CAP_NET_RAW
* It's Kea, not ISC KEA; fix the .service files
.
[ Yuval Freund ]
* Fix python dep issue. (Closes: #905977, #908491)
.
[ Badreddin Aboubakr ]
* Fix systemd Unit Files
+ Change lock directory (systemd nesting issue)
+ Quote RuntimeDirectory
+ Remove "LogsDirectory" and "LogsDirectoryMode" (they are not
supported in systemd 232)
.
[ Jason Guy ]
* Added a new patch to fix the kea-admin script.
* Fixed the postrm script (Closes: #905421)
Processed: severity of 923249 is important
Processing commands for cont...@bugs.debian.org: > severity 923249 important Bug #923249 [libvirt0] libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking internal IPv6 networking Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 923249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923249 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923249: [Pkg-libvirt-maintainers] Bug#923249: libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking internal IPv6 networking
Hi, On Mon, Feb 25, 2019 at 02:25:57PM +0100, Ralf Jung wrote: > Package: libvirt0 > Version: 5.0.0-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > After a recent upgrade, IPv6 communication between a virtual router and > another > virtual client over an isolated network stopped working. I am seeing the > rotuer > advertisments sent by the router on vnet0, which is attached to the bridge > virbr1, but when I capture packages on the bridge, the IPv6 traffic is gone. > It > just took me several hours of debugging to realize that the reason for this is > that /proc/sys/net/ipv6/conf/virbr1/disable_ipv6 is set to 1. After setting > it > to 0, IPv6 is working as expected now. > > This is a regression, IPv6 used to work between virtual clients just fine > without having to manually fiddle with the network configuration. I'm not near a ipv6 setup atm but according to the git logs nothing changed in that area for quite some time. Please indicate which version you updated from so it's easier to check for related changes and also provide details about your setup (preferably network XML and domain XML). There were some ipv6 related changes with firewalld though which might be worth investigating. -- Guido
Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?
Dear Technical Committee members,
I call for vote immediately on the following resolution.
=== Resolution ===
The Technical Committee resolves to decline to override the debootstrap
maintainers.
Furthermore, using its §6.1.5 "Offering advice" power, the Technical
Committee considers that the desirable solution at the time of `bullseye` is:
* W: `weak`: both directory schemes are allowed, but packages should only
be built on hosts with classical directory schemes (or in such
chroots)
* M: `middle`: both directory schemes are allowed, and packages (including
official packages) can be built on hosts with either classical
or "merged `/usr`" directory schemes
* H: `hard`: both directory schemes are allowed, but packages should only
be built on hosts with "merged `/usr`" directory schemes (or in
such chroots)
* FD: Further Discussion
=== End Resolution ===
=== Rationale ===
## What is "merged `/usr`"
"Merged `/usr`" describes a possible future standard directories scheme in
which the `/{bin,sbin,lib*}/` directories have been made superfluous through
replacing them by symlinks to their `/usr` equivalents
(`/usr/{bin,sbin,lib*}`).
The motivation to get Debian systems to converge towards such a scheme is
vastly documented elsewhere ([FDO's TheCaseForTheUsrMerge][0],
[wiki.d.o UsrMerge][1]) but can be summarized as the following points:
* having separate `/` and `/usr` filesystems has been useful in the past for
booting without initramfs onto a minimal root filesystem that carried just
enough to mount the `/usr` filesystem later in the boot process. Given the
evolution of physical hosts' capabilities, initramfs'es have been default in
Debian (and elsewhere) for a long time, and most systems no longer have an
intermediate state during boot in which they have only `/`, but not `/usr`,
mounted. Booting hosts through that intermediate state is not systematically
tested in Debian anymore.
* another use-case is to share system files from `/usr` between hosts (over a
network link) or containers (locally) which use different data or
configuration. Having all software under `/usr` (instead of spread between
`/` and `/usr`) makes the centralized update and the sharing easier.
* the packaging infrastructure to install files outside of `/usr` (e.g.
installing libs under `/lib` instead of `/usr/lib`) is not standard and
represents technical debt.
* given its status as remnant "folklore", the distinction between what
_needs_ to be shipped in `/` and what can stay in `/usr` is often interpreted
arbitrarily;
* allowing shipment of identically-named libraries or binaries in different
paths can confuse common understanding of paths precedence.
[0]: https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
[1]: https://wiki.debian.org/UsrMerge
The arguments against moving the base directories' scheme towards "merged
`/usr`" are as follows:
* there's no gain in disrupting something that is not inherently broken;
* `/{bin,sbin,lib*}/` → `/usr/{bin,sbin,lib*}/` symlinks create confusing
views of the system (`/bin/cat` and `/usr/bin/cat` are the same file), and
dpkg doesn't support this situation cleanly:
[#134758](https://bugs.debian.org/134758).
* it is possible for distributions to converge towards having all system
files in `/usr` in finite time instead of shortcutting this migration with
`/{bin,sbin,lib*}/` → `/usr/{bin,sbin,lib*}/` symlinks.
The compatibility symbolic links `/lib` → `/usr/lib` and `/lib64` →
`/usr/lib64` are required by the various CPUs' platform ABIs (for example
i386 requires `/lib/ld-linux.so.2` to resolve to glibc's `ld.so`, and amd64
requires `/lib64/ld-linux-x86-64.so.2`) so there are no plans to remove them
altogether. Similarly, removing `/bin` is not under consideration because it
would break the assumption that `/bin/sh` exists, and removing `/sbin` would
break the assumption that `/sbin/fsck.*` and `/sbin/mount.*` exist.
## "merged `/usr`" in Debian
In Debian buster, the current testing suite, "merged `/usr`" is only
considered for implementation with symlinks (there are no proposals for
simply dropping `/{bin,sbin,lib*}`) and is implemented in two main ways:
* existing hosts can be made to have a "merged `/usr`" by installing the
[usrmerge][2] package;
* new hosts get the `/{bin,sbin,lib*}/`→ `/usr/{bin,sbin,lib*}/` symlinks
by default when using debootstrap >= 1.0.102.
The usrmerge package contains a `/usr/lib/convert-usrmerge` perl executable
that runs in `postinst`, that will move the contents of `/{bin,sbin,lib*}/`
and replace these directories with symlinks when empty.
It is also possible to merge `/usr` in other ways, for example with
`debootstrap --merged-usr` or by bootstrapping into a chroot that already
contains the necessary symlinks.
[2]: https://tracker.debian.org/pkg/usrmerge
## Issues from "merged `/usr`"
Since the default change in debootstrap 1.0.102, some issues
Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?
(Corrected the recipients, these mails should go to the bug). Le lundi, 25 février 2019, 14.23:31 h CET Didier 'OdyX' Raboud a écrit : > Le samedi, 23 février 2019, 12.12:13 h CET Niko Tyni a écrit : > > > * B: The desireable solution at the time of bullseye is `hard`; both > > > directory schemes should be allowed, and packages can be built on hosts > > > with either classical or "merged-`/usr`" directory schemes. > > > > Isn't this the 'middle' option above rather than 'hard'? > > Actually, it's both. The only difference between 'middle' and 'hard' is > that in 'middle', _official_ packages can be built on either directory > schemes, where in 'hard', they are only built on "merged-`/usr`" directory > schemes. > > The distinction I was trying to make in the table is the following: > > * on which directory scheme Debian would build its "official" packages on > (columns 5 & 6) ; 'weak' is "classical directory scheme", 'middle' is > "both", 'hard' is "merged-/usr". > * whether .debs built on A can break on B (columns 7 & 8). All of 'weak', > 'middle' and 'hard' long-term statuses allow .debs to be built from either > directory scheme and be installed on either without constraints Wrong, actually (hit send too fast). The intent behind 'weak' was: "merged-/ usr" is allowed, but packages built on these directory schemes can break on classical directory schemes. So that should have read: * whether .debs built on A can break on B (columns 7 & 8). 'middle' and 'hard' long-term statuses allow .debs to be built from either directory scheme and be installed on either without constraints; 'weak' permits "merged-/usr" directory schemes, but packages built there can break on classical directory schemes. Cheers, OdyX signature.asc Description: This is a digitally signed message part.
Bug#923249: libvirt0: libvirt sets disable_ipv6 on bridge, entirely breaking internal IPv6 networking
Package: libvirt0 Version: 5.0.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, After a recent upgrade, IPv6 communication between a virtual router and another virtual client over an isolated network stopped working. I am seeing the rotuer advertisments sent by the router on vnet0, which is attached to the bridge virbr1, but when I capture packages on the bridge, the IPv6 traffic is gone. It just took me several hours of debugging to realize that the reason for this is that /proc/sys/net/ipv6/conf/virbr1/disable_ipv6 is set to 1. After setting it to 0, IPv6 is working as expected now. This is a regression, IPv6 used to work between virtual clients just fine without having to manually fiddle with the network configuration. Kind regards, Ralf -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libvirt0 depends on: ii libacl1 2.2.52-3+b1 ii libapparmor12.13.2-7 ii libaudit1 1:2.8.4-2 ii libavahi-client30.7-4+b1 ii libavahi-common30.7-4+b1 ii libc6 2.28-7 ii libcap-ng0 0.7.9-2 ii libcurl3-gnutls 7.64.0-1 ii libdbus-1-3 1.12.12-1 ii libdevmapper1.02.1 2:1.02.155-2 ii libgcc1 1:8.2.0-21 ii libgnutls30 3.6.6-2 ii libnl-3-200 3.4.0-1 ii libnl-route-3-200 3.4.0-1 ii libnuma12.0.12-1 ii libsasl2-2 2.1.27+dfsg-1 ii libselinux1 2.8-1+b1 ii libssh2-1 1.8.0-2 ii libxml2 2.9.4+dfsg1-7+b3 ii libyajl22.1.0-3 Versions of packages libvirt0 recommends: ii lvm2 2.03.02-2 libvirt0 suggests no packages. -- no debconf information
Bug#923229: marked as done (linitian: Missing depends on libpath-tiny-perl)
Your message dated Mon, 25 Feb 2019 13:21:26 + with message-id and subject line Bug#923229: fixed in lintian 2.9.0 has caused the Debian Bug report #923229, regarding linitian: Missing depends on libpath-tiny-perl to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 923229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lintian Version: 2.8.0 Severity: important Hi In 2.8.0 asaics several calls were replaced to use Path::Tiny and a build-dependency was installed. But a respective Depends is missing: Could not load /usr/share/lintian/commands/lintian.pm: Can't locate Path/Tiny.pm in @INC (you may need to install the Path::Tiny module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Lintian/Util.pm line 31. BEGIN failed--compilation aborted at /usr/share/perl5/Lintian/Util.pm line 31. Compilation failed in require at /usr/share/perl5/Lintian/DepMap.pm line 25. BEGIN failed--compilation aborted at /usr/share/perl5/Lintian/DepMap.pm line 25. Compilation failed in require at /usr/share/lintian/commands/lintian.pm line 43. BEGIN failed--compilation aborted at /usr/share/lintian/commands/lintian.pm line 43. Compilation failed in require at /usr/bin/lintian line 35. Regards, Salvatore --- End Message --- --- Begin Message --- Source: lintian Source-Version: 2.9.0 We believe that the bug you reported is fixed in the latest version of lintian, 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 923...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated lintian package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 25 Feb 2019 12:36:32 + Source: lintian Binary: lintian Built-For-Profiles: nocheck Architecture: source all Version: 2.9.0 Distribution: unstable Urgency: medium Maintainer: Debian Lintian Maintainers Changed-By: Chris Lamb Description: lintian- Debian package checker Closes: 923229 923232 Changes: lintian (2.9.0) unstable; urgency=medium . [ Felix Lechner ] * Add missing runtime dependency on libpath-tiny-perl. (Closes: #923229) . [ Chris Lamb ] * Add /lib/runit/invoke/run as a known interpreter. (Closes: #923232) Checksums-Sha1: 38b6663bb0019c7d244a68a1a1a09b5f744bb84f 3817 lintian_2.9.0.dsc c10c43d0447f9ce0389f2993d9e4885e63029c76 1719136 lintian_2.9.0.tar.xz 899821f19cb5de6e82845aefede434de217d1773 1193280 lintian_2.9.0_all.deb 2bce054d1d5b6a9eee30e5c509e2db910324e486 8886 lintian_2.9.0_amd64.buildinfo Checksums-Sha256: 3e755a7442f7a968ea2740a7244835c117efe2c186ca2ad22b5bdc9e8f2b2e15 3817 lintian_2.9.0.dsc ccd8481ca3f0fb8b98518976a02da04610c6beb6fd9d70e4bde46982a00ca9b8 1719136 lintian_2.9.0.tar.xz 94c15c8d77c38748bd5520e899ca97f82982ab52070886263419df9fd782658b 1193280 lintian_2.9.0_all.deb dc94ff5a89ca8695686f1fa683ac452d77f8772eb012b937230ce877f1712d43 8886 lintian_2.9.0_amd64.buildinfo Files: 8d79f3abd31b6782dd36eda4dfe1cfd9 3817 devel optional lintian_2.9.0.dsc a42ea327e1e28fba9c207fe166493633 1719136 devel optional lintian_2.9.0.tar.xz 00abccc76002c0a22fb6f298c34d0401 1193280 devel optional lintian_2.9.0_all.deb 2eb774606a9c1c772a05c22623be8c05 8886 devel optional lintian_2.9.0_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlxz6C0ACgkQHpU+J9Qx HliZDg//Z0j9vfwz5oIFcHRQEqs5Au96o4LNa2uSp6xvoNIGgsSTrQZMykxmMQuK 8g0Kk1MAiZLX2R57MMogvKGD0K/4Bv0xhZ3BHM4k/NtfFlVH3vrJ+bAdurZb7Fs/ Vob5P61zsemN7PYR5EqsUP6BHiEsjrnDN3Dknpomk5CHHH4edJp3D1ADjXdYj3XI ZFSgwHzLy/Is/B03wLJ98M+DUWdG6uhyhUJf8C7iecMZ2veQvDniv7w5E0i4dvJ2 wdaruCZ5FFQcYW51Zj7X5msC4DThydRTJs6eqEzO5kj+45hNna0mJuKywIC/Bzlf YEGA2RVm6SL3GG6QQQguMy0T5k/zWjKOogzld+v/VlIEped2ycaNOOBHzPnOhpVA G938vxAo5fTYo5XYu0QPpYTyrxJinS9iDd7c3F8E/pT51wb9QcnAk56dlO1EaKc9 qt2O3zi1tOFuo4p9lCmU5ceFs5m/nPdejrt/fySUrqriheLNJebyTv87AXYGXonL
Bug#923204: [pkg-gnupg-maint] Bug#923204: gpg-agent has a false dependency on libpam-systemd
On Sun, 24 Feb 2019 16:56, joshud...@gmail.com said: > gpg-agent --server or directly from .profile (ssh sessions) by > gpg-agent --daemon. FWIW, actually gpg-agent is started on-demand from all tools requiring it. To explicitly start it "gpgconf --launch agent" can and should be used. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. signature.asc Description: PGP signature
Bug#922804: makehuman: FTBFS (Could not import extension sphinx.ext.pngmath)
On Sun, Feb 24, 2019 at 03:01:05PM -0800, Muammar El Khatib wrote: > > I really appreciate this. I don't have much time recently to work on > it. But I don't want to leave Debian :S I hope I can work more when I > get more stable with my job. Thanks for agreeing with my plan. I hope I was able to safe the package for Buster now and leave it for other interested persons again. Kind regards Andreas. -- http://fam-tille.de
Bug#923204: marked as done (gpg-agent has a false dependency on libpam-systemd)
Your message dated Mon, 25 Feb 2019 17:44:16 +0500 with message-id <20190225124416.ga32...@belkar.wrar.name> and subject line Re: Bug#923204: gpg-agent has a false dependency on libpam-systemd has caused the Debian Bug report #923204, regarding gpg-agent has a false dependency on libpam-systemd 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.) -- 923204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gpg-agent Version: 2.2.12-1 Severity: serious Tags: newcomer Justification: Policy 7.2 gpg-agent has a false dependency on libpam-systemd; while systemd sessions can and do start gpg-agent this is no depenency of gpg-agent. gpg-agent is designed to be started by any session manager with gpg-agent --server or directly from .profile (ssh sessions) by gpg-agent --daemon. Dependency should be removed outright. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages gpg-agent depends on: ii gpgconf 2.2.12-1 ii libassuan0 2.5.2-1 ii libc6 2.28-7 ii libgcrypt20 1.8.4-5 ii libgpg-error0 1.35-1 ii libnpth01.6-1 ii pinentry-gnome3 [pinentry] 1.1.0-1+b1 ii pinentry-gtk2 [pinentry]1.1.0-1+b1 Versions of packages gpg-agent recommends: ii gnupg 2.2.12-1 Versions of packages gpg-agent suggests: pn dbus-user-session ii libpam-systemd-apt-holepunch [libpam-systemd] 1 ii pinentry-gnome31.1.0-1+b1 pn scdaemon -- no debconf information --- End Message --- --- Begin Message --- On Sun, Feb 24, 2019 at 04:56:32PM -0800, Joshua wrote: > Package: gpg-agent > Version: 2.2.12-1 > Severity: serious > Tags: newcomer That's a wrong tag. > Justification: Policy 7.2 > gpg-agent has a false dependency on libpam-systemd; It doesn't, it's Suiggests. -- WBR, wRAR signature.asc Description: PGP signature --- End Message ---
Bug#923229: Bug #923229 in lintian marked as pending
Control: tag -1 pending Hello, Bug #923229 in lintian 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/lintian/lintian/commit/e34a2595143cc4014183a3f284fe1c3469da29d5 Add missing runtime dependency on libpath-tiny-perl. (Closes: #923229) Gbp-Dch: ignore (this message was generated automatically) -- Greetings https://bugs.debian.org/923229
Bug#918600: marked as done (ruby-backports FTBFS: Failure: test_rails(AAA_TestBackportGuards))
Your message dated Mon, 25 Feb 2019 12:20:06 +
with message-id
and subject line Bug#918600: fixed in ruby-backports 3.11.1-2
has caused the Debian Bug report #918600,
regarding ruby-backports FTBFS: Failure: test_rails(AAA_TestBackportGuards)
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.)
--
918600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-backports
Version: 3.11.1-1
Severity: serious
Tags: ftbfs
Some recent change in unstable makes ruby-backports FTBFS:
https://tests.reproducible-builds.org/debian/history/ruby-backports.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-backports.html
...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rb │
└──┘
RUBYLIB=/build/1st/ruby-backports-3.11.1/debian/ruby-backports/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-backports/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
ruby2.5 debian/ruby-tests.rb
/build/1st/ruby-backports-3.11.1/test/_backport_guards_test.rb:54: warning:
constant ::Bignum is deprecated
/build/1st/ruby-backports-3.11.1/test/_backport_guards_test.rb:54: warning:
constant ::Fixnum is deprecated
/build/1st/ruby-backports-3.11.1/test/lazy_test.rb:212: warning: assigned but
unused variable - enum
/build/1st/ruby-backports-3.11.1/test/lazy_test.rb:304: warning: assigned but
unused variable - bug7696
Loaded suite /usr/lib/ruby/vendor_ruby/rake/rake_test_loader
Started
.F
===
Failure: test_rails(AAA_TestBackportGuards):
<{Array=>[".alias_method_chain"],
Binding=>[".alias_method_chain"],
Integer=>[".alias_method_chain"],
Dir=>[".alias_method_chain"],
Comparable=>[".alias_method_chain"],
Enumerable=>[".alias_method_chain"],
FalseClass=>[".alias_method_chain"],
Float=>[".alias_method_chain"],
GC=>[".alias_method_chain"],
Hash=>[".alias_method_chain"],
IO=>[".alias_method_chain"],
Kernel=>[".alias_method_chain"],
Math=>[".alias_method_chain"],
MatchData=>[".alias_method_chain"],
Method=>[".alias_method_chain"],
Module=>[:alias_method_chain, ".alias_method_chain"],
NilClass=>[".alias_method_chain"],
Numeric=>[".alias_method_chain"],
ObjectSpace=>[".alias_method_chain"],
Proc=>[".alias_method_chain"],
Process=>[".alias_method_chain"],
Range=>[".alias_method_chain"],
Regexp=>[".alias_method_chain"],
String=>[".alias_method_chain"],
Struct=>[".alias_method_chain"],
Symbol=>[".alias_method_chain"],
TrueClass=>[".alias_method_chain"],
#>=>[".alias_method_chain"],
#>=>[".alias_method_chain"],
Enumerator=>[".alias_method_chain"]}> was expected to be nil.
/build/1st/ruby-backports-3.11.1/test/_backport_guards_test.rb:159:in
`test_rails'
156: before = digest
157: require "backports/rails"
158: after = digest
=> 159: assert_nil digest_delta(before, after)
160: end
161: end
===
.
Finished in 0.703883895 seconds.
---
51 tests, 170 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0
notifications
98.0392% passed
---
72.46 tests/s, 241.52 assertions/s
/usr/lib/ruby/vendor_ruby/rake/testtask.rb:130:in `block (3 levels) in define':
Command failed with status (1) (RuntimeError)
from /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:57:in `sh'
from /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:105:in `ruby'
from /usr/lib/ruby/vendor_ruby/rake/testtask.rb:117:in `block (2
levels) in define'
from /usr/lib/ruby/vendor_ruby/rake/file_utils_ext.rb:59:in `verbose'
from /usr/lib/ruby/vendor_ruby/rake/testtask.rb:111:in `block in define'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:271:in `block in execute'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:271:in `each'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:271:in `execute'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:213:in `block
Processed: Bug #923229 in lintian marked as pending
Processing control commands: > tag -1 pending Bug #923229 [src:lintian] linitian: Missing depends on libpath-tiny-perl Added tag(s) pending. -- 923229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918600: Bug #918600 in ruby-backports marked as pending
Control: tag -1 pending Hello, Bug #918600 in ruby-backports 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/ruby-team/ruby-backports/commit/f668014c2145f758131ffe51c24de83b367590cd Add patch to skip activesupport test as advised by upstream. Closes: #918600 (this message was generated automatically) -- Greetings https://bugs.debian.org/918600
Processed: Bug #918600 in ruby-backports marked as pending
Processing control commands: > tag -1 pending Bug #918600 [src:ruby-backports] ruby-backports FTBFS: Failure: test_rails(AAA_TestBackportGuards) Added tag(s) pending. -- 918600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#749991: A tiresome subject for YEARS.
This also happens with daily and weekly testing images: At least, tried with netinst from here: https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/ And daily from here: https://cdimage.debian.org/cdimage/daily-builds/daily/current/amd64/ PXE installation is also broken with the same issue as reported by Jan. On Mon, 11 Feb 2019 15:50:25 +0100 Jan Huijsmans wrote: > On Mon, 11 Feb 2019 15:21:12 +0100 > Jan Huijsmans wrote: > > > Sorry for the spam, PEBKAC, wront netboot.tar.gz. (wget renamed as the > > old one from just after 4.19.0-2 kernel update was still there) > > > > Linking kernel + netboot update would be great though, or is there a > > standard delay of a day or 2? > > I shouldn't do this mailing thing when I'm tired... :( > > PEBKAC on the PEBKAC report, issue still exists, the netboot.tar.gz > just downloaded for amd64 (timestamp on server ftp.nl.debian.org > 19-01-2019 18:03) contains kernel 4.19.0-1-amd64 (4.19.12 (2018-12-22)) > but the repo has 4.19.0-2-amd64 (4.19.16-1 (2019-01-17)). When I look > at the date of the netboot.tar.gz upload, it should be able to have the > new kernel, but it hasn't. > > The file I use is downloaded from: > http://ftp.nl.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/ > > The source (I guess) is at: > http://ftp.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/ > > and has timestamp 2019-01-18 20:43. > > --- > > Jan Huijsmans huysm...@koffie.nu > > ... cannot activate /dev/brain, no response from main coffee server > > > >
Processed: severity of 923229 is serious
Processing commands for cont...@bugs.debian.org: > severity 923229 serious Bug #923229 [src:lintian] linitian: Missing depends on libpath-tiny-perl Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 923229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909259: marked as done (procyon: FTBFS with Java 11 due to sun.misc.Unsafe.defineClass() removal)
Your message dated Mon, 25 Feb 2019 11:04:31 + with message-id and subject line Bug#909259: fixed in procyon 0.5.32-5 has caused the Debian Bug report #909259, regarding procyon: FTBFS with Java 11 due to sun.misc.Unsafe.defineClass() removal to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 909259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: procyon Version: 0.5.32-4 Severity: important Tags: sid buster User: debian-j...@lists.debian.org Usertags: default-java11 procyon fails to build with Java 11 due to the removal of the defineClass() method in sun.misc.Unsafe: /procyon/Procyon.Reflection/src/main/java/com/strobel/reflection/emit/TypeBuilder.java:1234: error: cannot find symbol _generatedClass = (Class) getUnsafeInstance().defineClasss( ^ symbol: method defineClasss(String,byte[],int,int,ClassLoader,ProtectionDomain) location: class Unsafe Note that gradle/4.4-2 doesn't run on Java 11 and can't build procyon yet, but that's a different issue. --- End Message --- --- Begin Message --- Source: procyon Source-Version: 0.5.32-5 We believe that the bug you reported is fixed in the latest version of procyon, 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 909...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated procyon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 25 Feb 2019 11:35:03 +0100 Source: procyon Architecture: source Version: 0.5.32-5 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 909259 Changes: procyon (0.5.32-5) unstable; urgency=medium . * Team upload. * Fixed the build failure with Java 11 (Closes: #909259) * Standards-Version updated to 4.3.0 Checksums-Sha1: 6793946ff717e97e0f1b5e4cbe9507cc6ac86e28 2123 procyon_0.5.32-5.dsc e2ba3712acf36dbb1c929963009d8ec8acb36584 10020 procyon_0.5.32-5.debian.tar.xz 7c704bae36cec19c7ce6842978fe66f4edbb937d 14191 procyon_0.5.32-5_source.buildinfo Checksums-Sha256: f8deea35518a117f89ce5032736b60a185ed3b2df14ef0eb79fb1911a5aee41d 2123 procyon_0.5.32-5.dsc 070bbe49fbaf1851cd32ef293cd03f69d8fbd476eda4643e82770250198ca6ea 10020 procyon_0.5.32-5.debian.tar.xz 6dde4f1ae55528c4e45c0ce93183870aac48d759cd3e827014204500929a2dbb 14191 procyon_0.5.32-5_source.buildinfo Files: ffac68d95455b7bdd8fd32f4fefcfec9 2123 java optional procyon_0.5.32-5.dsc 4f67b51835c6b308d2d1db52a87363cd 10020 java optional procyon_0.5.32-5.debian.tar.xz e32798fd910e44897710d16a2bfa2b02 14191 java optional procyon_0.5.32-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlxzxjwSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCs8gAP/ApOwtxeClIYCbYLDRWxRXEWIunj7RRq p8nWUC840+5a5LDpW+bJhQzjJt5WX0DUSn72nnz0niI0nBiWcMPbHcTLd+8LEDSX UlIEay/qS5tAx5QDW1yT7l5HM2S/g0QRNSaoIpdG1gQ+WQbjZSe635JPJ3xcdtMl KAeflZwAABAXf945Lk3hbueWllhKOQBUbq7d8pp5H6i5xjKOcYaGd9pBa/NYwXKk QAcd1FUFrXBCtwcVV81vDuKa1g2iFDGfzV6ai3X1zFqU89C/rPDyvcH6oMsfcbv2 s/0+iMy7lxYSpJU/gtxZDdZzoVdtr2nteeD5j9tErlhh/qyAq/59pZAiiXbZ84hs g84qWFftcRlJHrmzjlCx2EHfeq+YKfAbylF4V8G8q0133qA+v2SIywYM86F8rfhQ uF6M2JmyCk9KQ1PWHmsKU3u7jEdvDYgaUsKuvRumfI8S61mItpLBBWXMaT4lhlAF IzBF0hrgz+I/da1EOvNx4CoKIiGr6N4pRvEB/QxcBJnyDwwvJVZ33O+iMdeZ0nEf MHYtj9JS0O6pkzjtegq6Jv/xOLcXCQOoiXeptCbKXUIwHZm2RbF6cL9BrZZRMAUh jeyn7BctS4+JQuNIfOCIefsOkIE4/t8s6iKc0yUDBBnGOcNIHTdHqsZmqRuzoSiF FZL2LP6AfaVJ =gavS -END PGP SIGNATURE End Message ---
Bug#909259: Bug #909259 in procyon marked as pending
Control: tag -1 pending Hello, Bug #909259 in procyon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/procyon/commit/6cc3de7e70d327fa597af22d3da08015aabd1620 Fixed the build failure with Java 11 (Closes: #909259) (this message was generated automatically) -- Greetings https://bugs.debian.org/909259
Processed: Bug #909259 in procyon marked as pending
Processing control commands: > tag -1 pending Bug #909259 [src:procyon] procyon: FTBFS with Java 11 due to sun.misc.Unsafe.defineClass() removal Added tag(s) pending. -- 909259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 923199 is normal
Processing commands for cont...@bugs.debian.org: > severity 923199 normal Bug #923199 [openssh-server] openssh-server has a false dependency on libpam-systemd Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 923199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923238: libmarc-charset-perl: needs a rebuild on 32bit architectures?
Package: libmarc-charset-perl Version: 1.35-2 Severity: serious Hello, for some reasons the package testsuite started to fail in Ubuntu for this package and xml-perl reverse-dependency, only on armhf and i386. This happened when the new gdbm has been uploaded and rebuilds issued. I traced down the problem to some differences in the march8/utf8 Table generation, I don't know how serious it is, but the testsuite seems completely broken on armhf and i386 at least, and utf8 cjk conversion seems to return wrong values. This is the reason for me opening this bug as "serious". you can see the reports here https://autopkgtest.ubuntu.com/packages/libmarc-xml-perl and https://autopkgtest.ubuntu.com/packages/libmarc-charset-perl perl t/cjk.t 1..1 no mapping found for [0x61] at position 0 in a $1!u`!** z g0=ASCII_DEFAULT g1=EXTENDED_LATIN at /usr/share/perl5/MARC/Charset.pm line 308. not ok 1 - cjk # Failed test 'cjk' # at t/cjk.t line 17. Wide character in print at /usr/share/perl/5.28/Test2/Formatter/TAP.pm line 113. # got: 'a 埇 z' # expected: undef # Looks like you failed 1 test of 1. after a no-change rebuild of the package, and installing it, the test goes passing ok: perl t/cjk.t 1..1 ok 1 - cjk I'm not sure if a no-change rebuild fixes also libmarc-xml-perl and fixes all the test failures, this is something I'm checking right now (but I suppose it will) G.
Bug#922804: marked as done (makehuman: FTBFS (Could not import extension sphinx.ext.pngmath))
Your message dated Mon, 25 Feb 2019 10:05:26 + with message-id and subject line Bug#922804: fixed in makehuman 1.1.1-1.1 has caused the Debian Bug report #922804, regarding makehuman: FTBFS (Could not import extension sphinx.ext.pngmath) 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.) -- 922804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:makehuman Version: 1.1.1-1 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python2 --with quilt dh_quilt_patch -i Applying patch 01_makehuman.py.patch patching file makehuman/makehuman.py Now at patch 01_makehuman.py.patch dh_update_autotools_config -i debian/rules override_dh_auto_build make[1]: Entering directory '/<>' # Building docs sh debian/scripts/gendoc.sh Creating API documentation make[2]: Entering directory '/<>/docs/sphinx' sphinx-build -b html -d build/doctrees -D html_last_updated_fmt="June 24, 2017" source build/html Running Sphinx v1.8.3 WARNING: while setting up extension matplotlib.sphinxext.mathmpl: directive u'math' is already registered, it will be overridden Extension error: Could not import extension sphinx.ext.pngmath (exception: No module named pngmath) make[2]: *** [Makefile:40: html] Error 2 make[2]: Leaving directory '/<>/docs/sphinx' make[1]: *** [debian/rules:7: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:3: build-indep] Error 2 dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit status 2 The build was made in my autobuilder with "dpkg-buildpackage -A" and it also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/makehuman.html If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: makehuman Source-Version: 1.1.1-1.1 We believe that the bug you reported is fixed in the latest version of makehuman, 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 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated makehuman package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 25 Feb 2019 10:39:08 +0100 Source: makehuman Architecture: source Version: 1.1.1-1.1 Distribution: unstable Urgency: medium Maintainer: Muammar El Khatib Changed-By: Andreas Tille Closes: 922804 Changes: makehuman (1.1.1-1.1) unstable; urgency=medium . * Non-maintainer upload. * Packaging at https://salsa.debian.org/debian/makehuman * Replace pngmath by imgmath in sphinx config Closes: #922804 * Fix homepage * Do not unnecessarily Build-Depends: quilt * debhelper 9 (as set in d/compat) * Drop outdated XS-Python-Version: 2.7 * Standards-Version: 4.3.0 * Use Breaks instead of Conflicts with version * Lintian-override for false positive * DEP5 fix Checksums-Sha1: cbf61daebbcac28204410cebeb2e49e5c02aa7f2 2164 makehuman_1.1.1-1.1.dsc 2495fd4c26e86553f52bca5bb74cb0992a7e56a7 21740 makehuman_1.1.1-1.1.debian.tar.xz b1f04322d03305a43b4afb35d3b7afdf8cbac0ff 10637 makehuman_1.1.1-1.1_amd64.buildinfo Checksums-Sha256: 01183d3ce858349766a63fdcb34ea3d39a13ff99b7e737e537670e17d294be81 2164 makehuman_1.1.1-1.1.dsc 5273fe4b907826f424b85e971a94d41036ca4044c9a75c024c30a55192b479bf 21740 makehuman_1.1.1-1.1.debian.tar.xz c5d81cff428674a7f0d421b35082c7e99e7745c77117096a41e624ea5fbf99d1 10637 makehuman_1.1.1-1.1_amd64.buildinfo Files: 96b457f9484fbac51266596e47b62dae 2164 graphics optional makehuman_1.1.1-1.1.dsc 99263d796c1874c0261b751e874905bd 21740 graphics optional makehuman_1.1.1-1.1.debian.tar.xz adf6d2291fcee327a90a2a67d67b232a 10637 graphics optional
Bug#921757: Can reproduce
control: tag 921757 patch
Santjago,
can you confirm that the attached patch fixes the problem on your build
setup? (If you don't have the time for the test, I'd take you up on your
offer for SSH access.)
Cheers,
-Hilko
>From 03f0e226eff2444aa80b294eb8adeb5661a683ca Mon Sep 17 00:00:00 2001
From: Hilko Bengen
Date: Mon, 25 Feb 2019 09:47:35 +0100
Subject: [PATCH] Eliminate race condition in runcmd
---
osutils.pm | 17 +++--
1 file changed, 7 insertions(+), 10 deletions(-)
diff --git a/osutils.pm b/osutils.pm
index b06a042b..ec582c66 100644
--- a/osutils.pm
+++ b/osutils.pm
@@ -93,19 +93,10 @@ sub quote {
# Open a process to run external program and check its return status
sub runcmd {
diag "running " . join(' ', @_);
-my ($pid, $status);
-
-local $SIG{CHLD} = sub {
-local ($!, $?);
-while ((my $child = waitpid(-1, WNOHANG)) > 0) {
-diag "runcmd pid $pid returned $child";
-$status = $?;
-}
-};
my ($wtr, $rdr, $err);
$err = gensym;
-$pid = open3($wtr, $rdr, $err, @_);
+my $pid = open3($wtr, $rdr, $err, @_);
die "couldn't open: $!" unless defined $pid;
close($wtr) or die "couldn't close fh: $!";
@@ -125,6 +116,12 @@ sub runcmd {
close($rdr) or die "couldn't close fh: $!";
close($err) or die "couldn't close fh: $!";
+my $status;
+while ((my $child = waitpid(-1, WNOHANG)) > 0) {
+diag "runcmd pid $pid returned $child";
+$status = $?;
+}
+
my $exit_code = $status >> 8;
die "runcmd failed with exit code $exit_code" unless ($exit_code == 0);
return $exit_code;
--
2.20.1
Processed: Re: Bug#921757: Can reproduce
Processing control commands: > tag 921757 patch Bug #921757 [src:os-autoinst] os-autoinst: FTBFS (failing tests) Added tag(s) patch. -- 921757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#923228: FTBS: new symbols
Package: gringo
Version: 5.3.0
Severity: serious
Hey,
Gringo seems to FTBS in buster due to:
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/gringo/DEBIAN/symbols doesn't match completely
debian/symbols
--- debian/symbols (gringo_5.3.0-6_amd64)
+++ dpkg-gensymbolsj8jm57 2019-02-25 08:56:50.725562893 +
@@ -35,8 +35,8 @@
(optional=templinst|arch=amd64 arm64 hppa kfreebsd-amd64 sh4
x32|subst)_ZNSt10_HashtableI{uint64_t}{uint64_t}SaI{uint64_t}ENSt8__detail9_IdentityESt8equal_toI{uint64_t}ESt4hashI{uint64_t}ENS1_18_Mod_range_hashingENS1_20_Default_ranged_hashENS1_20_Prime_rehash_policyENS1_17_Hashtable_traitsILb0ELb1ELb1D2Ev@Base
1
#MISSING: 1#
(optional=templinst|arch=mipsel)_ZNSt11__copy_moveILb1ELb0ESt26random_access_iterator_tagE8__copy_mIPN6Gringo11IntervalSetINS3_6SymbolEE8IntervalES8_EET0_T_SA_S9_@Base
1
#MISSING: 5.3.0# (optional=templinst|arch=!alpha !amd64 !arm64 !armel !armhf
!hppa !hurd-i386 !i386 !kfreebsd-i386 !m68k !mips !mips64el !mipsel !powerpc
!powerpcspe !ppc64 !ppc64el !riscv64 !s390x
!sh4)_ZNSt11unique_lockISt5mutexE6unlockEv@Base 1
-#MISSING: 5.3.0#
(optional=templinst|arch=kfreebsd-amd64)_ZNSt12__shared_ptrIjLN9__gnu_cxx12_Lock_policyE2EEC1ERKS2_@Base
1
-#MISSING: 5.3.0#
(optional=templinst|arch=kfreebsd-amd64)_ZNSt12__shared_ptrIjLN9__gnu_cxx12_Lock_policyE2EEC2ERKS2_@Base
1
+
(optional=templinst)_ZNSt12__shared_ptrIjLN9__gnu_cxx12_Lock_policyE2EEC1ERKS2_@Base
1
+
(optional=templinst)_ZNSt12__shared_ptrIjLN9__gnu_cxx12_Lock_policyE2EEC2ERKS2_@Base
1
(optional=templinst)_ZNSt13_Bvector_baseISaIbEE13_M_deallocateEv@Base 1
(optional=templinst)_ZNSt14_Function_base13_Base_managerISt5_BindIFMN5Clasp3Cli12ClaspAppBaseEFbRNS2_11ClaspFacadeEEPN6Gringo9ClingoAppESt12_PlaceholderILi1E10_M_managerERSt9_Any_dataRKSH_St18_Manager_operation@Base
1
(optional=templinst)_ZNSt14_Function_base13_Base_managerISt5_BindIFMN5Clasp3Cli12ClaspAppBaseEFbRNS2_14ProgramBuilderEEPN6Gringo9ClingoAppESt12_PlaceholderILi1E10_M_managerERSt9_Any_dataRKSH_St18_Manager_operation@Base
1
@@ -45,11 +45,11 @@
(optional=templinst)_ZNSt15__exception_ptr12__dest_thunkISt13runtime_errorEEvPv@Base
1
(optional=templinst|arch=armel
riscv64)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE10_M_releaseEv@Base
1
(optional=templinst|arch=!armel
!riscv64)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_releaseEv@Base
1
- (optional=templinst|arch=!alpha !armhf !hurd-i386 !i386 !ia64 !kfreebsd-i386
!m68k !mips !mipsel !powerpc !powerpcspe !ppc64
!s390x)_ZNSt20__uninitialized_copyILb0EE13__uninit_copyISt13move_iteratorIPN6Gringo10CSPRelTermEES5_EET0_T_S8_S7_@Base
1
- (optional=templinst|arch=!alpha !amd64 !arm64 !armhf !hppa !hurd-i386 !i386
!kfreebsd-amd64 !kfreebsd-i386 !m68k !mips !mips64el !mipsel !powerpc
!powerpcspe !ppc64 !ppc64el !riscv64 !s390x !sh4
!x32)_ZNSt20__uninitialized_copyILb0EE13__uninit_copyISt13move_iteratorIPN6Gringo13TheoryAtomDefEES5_EET0_T_S8_S7_@Base
5.3.0
+#MISSING: 5.3.0-6# (optional=templinst|arch=!alpha !armhf !hurd-i386 !i386
!ia64 !kfreebsd-i386 !m68k !mips !mipsel !powerpc !powerpcspe !ppc64
!s390x)_ZNSt20__uninitialized_copyILb0EE13__uninit_copyISt13move_iteratorIPN6Gringo10CSPRelTermEES5_EET0_T_S8_S7_@Base
1
+
(optional=templinst)_ZNSt20__uninitialized_copyILb0EE13__uninit_copyISt13move_iteratorIPN6Gringo13TheoryAtomDefEES5_EET0_T_S8_S7_@Base
5.3.0
(optional=templinst)_ZNSt20__uninitialized_copyILb0EE13__uninit_copyISt13move_iteratorIPN6Gringo5Input10CheckLevelEES6_EET0_T_S9_S8_@Base
1
(optional=templinst)_ZNSt20__uninitialized_copyILb0EE13__uninit_copyISt13move_iteratorIPN6Gringo5Input7CSPElemEES6_EET0_T_S9_S8_@Base
1
-#MISSING: 5.3.0# (optional=templinst|arch=!alpha !amd64 !arm64 !armel !armhf
!hppa !hurd-i386 !i386 !kfreebsd-i386 !m68k !mips !mips64el !mipsel !powerpc
!powerpcspe !ppc64 !ppc64el !riscv64 !s390x
!sh4)_ZNSt20__uninitialized_copyILb0EE13__uninit_copyISt13move_iteratorIPSt4pairISt10unique_ptrIN6Gringo5Input7LiteralESt14default_deleteIS7_EESt6vectorISA_SaISA_SF_EET0_T_SI_SH_@Base
1
+
(optional=templinst)_ZNSt20__uninitialized_copyILb0EE13__uninit_copyISt13move_iteratorIPSt4pairISt10unique_ptrIN6Gringo5Input7LiteralESt14default_deleteIS7_EESt6vectorISA_SaISA_SF_EET0_T_SI_SH_@Base
1
(optional=templinst)_ZNSt20__uninitialized_copyILb0EE13__uninit_copyISt13move_iteratorIPSt4pairISt6vectorIS3_ISt10unique_ptrIN6Gringo5Input7LiteralESt14default_deleteIS8_EES4_ISB_SaISB_EEESaISE_EESD_EESI_EET0_T_SL_SK_@Base
1
(optional=templinst)_ZNSt20__uninitialized_copyILb0EE13__uninit_copyISt13move_iteratorIPSt4pairISt6vectorIS4_ISt10unique_ptrIN6Gringo5Input7LiteralESt14default_deleteIS8_EESaISB_EESaISD_EESD_EESH_EET0_T_SK_SJ_@Base
1
Bug#871285: marked as done (libxmmsclient++4v5: requires rebuild against GCC 7 and symbols/shlibs bump)
Your message dated Mon, 25 Feb 2019 08:56:12 + with message-id and subject line Bug#871285: fixed in xmms2 0.8+dfsg-18.2 has caused the Debian Bug report #871285, regarding libxmmsclient++4v5: requires rebuild against GCC 7 and symbols/shlibs bump 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.) -- 871285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxmmsclient++4v5 Version: 0.8+dfsg-18 Severity: serious Tags: sid buster User: debian-...@lists.debian.org Usertags: gcc-7-op-mangling Hi, It appears that your package provides an external symbol that is affected by the recent name mangling changes in GCC 7. See: https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling In GCC 7, the name mangling for C++ conversion operators which return a type using the abi_tag attribute (most commonly std::string) has changed. When your library is compiled with GCC 7, it will now emit two symbols for the conversion operator using the new and old naming. Executables compiled with GCC 7 will always use the new symbol, while old executables compiled using <= GCC 6 will use the old symbol. For new executables to build without undefined references, your library will need rebuilding with GCC 7. To ensure that new executables will pull in the newer version of the library built with GCC 7: - Your library package should Build-Depend on g++ (>= 4:7). - If your package provides a symbols file, ensure that the new conversion operator symbols have a version matching the version this bug is fixed in (including the Debian revision and tilde if necessary). Using apt as an example (debian/libapt-pkg5.0.symbols): (c++)"URI::operator std::__cxx11::basic_string, std::allocator >[abi:cxx11]()@APTPKG_5.0" 0.8.0 + (c++)"URI::operator std::__cxx11::basic_string, std::allocator >()@APTPKG_5.0" 1.5~beta2~ Where "1.5~beta2" is the version this bug was fixed in. - If your package does not provide a symbols file, add a dh_makeshlibs override so that tight enough dependencies are generated. Using libebml as an example (debian/rules): + override_dh_makeshlibs: + # For new symbols when compiled with GCC 7 + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)' Where "1.3.4-2" is the version this bug was fixed in. - If your package is about to be renamed due to an upstream SONAME bump, you do not need to add any special symbols handling. If you would like to know the exact name of the new symbols, using "abipkgdiff" from abigail-tools might be able to help. Thanks, James --- End Message --- --- Begin Message --- Source: xmms2 Source-Version: 0.8+dfsg-18.2 We believe that the bug you reported is fixed in the latest version of xmms2, 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 871...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emanuele Rocca (supplier of updated xmms2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 25 Feb 2019 08:12:48 +0100 Source: xmms2 Binary: libaudio-xmmsclient-perl libaudio-xmmsclient-perl-dbgsym libxmmsclient++-dev libxmmsclient++-glib-dev libxmmsclient++-glib1v5 libxmmsclient++-glib1v5-dbgsym libxmmsclient++4v5 libxmmsclient++4v5-dbgsym libxmmsclient-dev libxmmsclient-glib-dev libxmmsclient-glib1 libxmmsclient-glib1-dbgsym libxmmsclient6 libxmmsclient6-dbgsym python-xmmsclient python-xmmsclient-dbgsym ruby-xmmsclient ruby-xmmsclient-dbgsym xmms2 xmms2-client-avahi xmms2-client-avahi-dbgsym xmms2-client-cli xmms2-client-cli-dbgsym xmms2-client-medialib-updater xmms2-client-medialib-updater-dbgsym xmms2-client-nycli xmms2-core xmms2-core-dbgsym xmms2-dev xmms2-icon xmms2-plugin-airplay xmms2-plugin-airplay-dbgsym xmms2-plugin-all xmms2-plugin-alsa xmms2-plugin-alsa-dbgsym xmms2-plugin-ao xmms2-plugin-ao-dbgsym xmms2-plugin-apefile xmms2-plugin-apefile-dbgsym xmms2-plugin-asf xmms2-plugin-asf-dbgsym xmms2-plugin-asx xmms2-plugin-asx-dbgsym xmms2-plugin-avcodec xmms2-plugin-avcodec-dbgsym xmms2-plugin-cdda xmms2-plugin-cdda-dbgsym xmms2-plugin-cue xmms2-plugin-cue-dbgsym
Bug#923226: Compiling shader doesn't work - game doesn't work
Package: openarena
Version: 0.8.8+dfsg-2
Severity: grave
Hi,
openarena doesn't work anymore because it doesn't manage to compile its
shaders.
jpuydt on irc.debian.org
ioq3 1.36+u20181222.e5da13f~dfsg-1/Debian linux-x86_64 Jan 14 2019
SSE instruction set enabled
- FS_Startup -
We are looking in the current search path:
/home/jpuydt/.openarena/baseoa
/usr/lib/openarena/baseoa
/usr/lib/openarena/baseoa/z_oacmp-volume1-v3.pk3 (370 files)
/usr/lib/openarena/baseoa/pak6-patch088.pk3 (711 files)
/usr/lib/openarena/baseoa/pak6-patch085.pk3 (559 files)
/usr/lib/openarena/baseoa/pak6-misc.pk3 (229 files)
/usr/lib/openarena/baseoa/pak5-TA.pk3 (139 files)
/usr/lib/openarena/baseoa/pak4-textures.pk3 (1753 files)
/usr/lib/openarena/baseoa/pak2-players.pk3 (669 files)
/usr/lib/openarena/baseoa/pak2-players-mature.pk3 (231 files)
/usr/lib/openarena/baseoa/pak1-maps.pk3 (100 files)
/usr/lib/openarena/baseoa/pak0.pk3 (1042 files)
--
5803 files in pk3 files
execing default.cfg
couldn't exec q3config.cfg
couldn't exec autoexec.cfg
Hunk_Clear: reset the hunk ok
- Client Initialization -
Couldn't read q3history.
- Initializing Renderer
Trying to load "renderer_opengl2_x86_64.so" from "/usr/lib/ioquake3"...
---
QKEY found.
- Client Initialization Complete -
- R_Init -
SDL using driver "x11"
Initializing OpenGL display
Display aspect: 1.600
...setting mode 3: 640 480
Trying to get an OpenGL 3.2 core context
SDL_GL_CreateContext failed: Could not create GL context: GLXBadFBConfig
Reverting to default context
Using 24 color bits, 24 depth, 8 stencil display.
Available modes: '640x400 720x450 840x525 960x600 1280x800 800x512 700x450
680x384 320x180 432x243 480x270 512x288 640x360 720x405 800x450 864x486 960x540
1024x576 1280x720 360x202 684x384 320x240 400x300 512x384 576x432 640x480
700x525 800x600 896x672 928x696 960x720 1024x768 640x512'
GL_RENDERER: Mesa DRI Intel(R) Ironlake Mobile
Initializing OpenGL extensions
...ignoring GL_EXT_texture_compression_s3tc
...ignoring GL_S3_s3tc
...ignoring GL_EXT_texture_filter_anisotropic
...using GL_ARB_framebuffer_object
...using GL_ARB_vertex_array_object
...using GL_ARB_texture_float
...using GL_ARB_depth_clamp
...ignoring GL_ARB_seamless_cube_map
...using GLSL version 1.20
...GL_NVX_gpu_memory_info not found
...GL_ATI_meminfo not found
...ignoring GL_ARB_texture_compression_rgtc
...GL_ARB_texture_compression_bptc not found
...GL_EXT_direct_state_access not found
--- FBO_Init ---
--- GLSL_InitGPUShaders ---
Shader source:
#version 120
#define shadow2D(a,b) shadow2D(a,b).r
#ifndef M_PI
#define M_PI 3.14159265358979323846
#endif
#ifndef deformGen_t
#define deformGen_t
#define DGEN_WAVE_SIN 1
#define DGEN_WAVE_SQUARE 2
#define DGEN_WAVE_TRIANGLE 3
#define DGEN_WAVE_SAWTOOTH 4
#define DGEN_WAVE_INVERSE_SAWTOOTH 5
#define DGEN_BULGE 7
#define DGEN_MOVE 8
#endif
#ifndef tcGen_t
#define tcGen_t
#define TCGEN_LIGHTMAP 2
#define TCGEN_TEXTURE 3
#define TCGEN_ENVIRONMENT_MAPPED 4
#define TCGEN_FOG 5
#define TCGEN_VECTOR 6
#endif
#ifndef colorGen_t
#define colorGen_t
#define CGEN_LIGHTING_DIFFUSE 11
#endif
#ifndef alphaGen_t
#define alphaGen_t
#define AGEN_LIGHTING_SPECULAR 6
#define AGEN_PORTAL 8
#endif
#ifndef r_FBufScale
#define r_FBufScale vec2(0.001563, 0.002083)
#endif
#line 0
uniform sampler2D u_DiffuseMap;
#if defined(USE_LIGHTMAP)
uniform sampler2D u_LightMap;
#endif
#if defined(USE_NORMALMAP)
uniform sampler2D u_NormalMap;
#endif
#if defined(USE_DELUXEMAP)
uniform sampler2D u_DeluxeMap;
#endif
#if defined(USE_SPECULARMAP)
uniform sampler2D u_SpecularMap;
#endif
#if defined(USE_SHADOWMAP)
uniform sampler2D u_ShadowMap;
#endif
#if defined(USE_CUBEMAP)
uniform samplerCube u_CubeMap;
#endif
#if defined(USE_NORMALMAP) || defined(USE_DELUXEMAP) ||
defined(USE_SPECULARMAP) || defined(USE_CUBEMAP)
// y = deluxe, w = cube
uniform vec4 u_EnableTextures;
#endif
#if defined(USE_PRIMARY_LIGHT) || defined(USE_SHADOWMAP)
uniform vec3 u_PrimaryLightColor;
uniform vec3 u_PrimaryLightAmbient;
#endif
#if defined(USE_LIGHT) && !defined(USE_FAST_LIGHT)
uniform vec4 u_NormalScale;
uniform vec4 u_SpecularScale;
#endif
#if defined(USE_LIGHT) && !defined(USE_FAST_LIGHT)
#if defined(USE_CUBEMAP)
uniform vec4 u_CubeMapInfo;
#endif
#endif
uniform int u_AlphaTest;
varying vec4 var_TexCoords;
varying vec4 var_Color;
#if (defined(USE_LIGHT) && !defined(USE_FAST_LIGHT))
varying vec4 var_ColorAmbient;
#endif
#if (defined(USE_LIGHT) && !defined(USE_FAST_LIGHT))
varying vec4 var_Normal;
varying vec4 var_Tangent;
varying vec4 var_Bitangent;
#endif
#if defined(USE_LIGHT) && !defined(USE_FAST_LIGHT)
varying vec4 var_LightDir;
#endif
#if defined(USE_PRIMARY_LIGHT) || defined(USE_SHADOWMAP)
varying vec4 var_PrimaryLightDir;
#endif
#define EPSILON 0.0001
#if defined(USE_PARALLAXMAP)
float SampleDepth(sampler2D normalMap, vec2 t)
{
