Processed: Re: aolserver4: Should this package be removed?
Processing commands for cont...@bugs.debian.org: > severity 891633 normal Bug #891633 [aolserver4] aolserver4: Should this package be removed? Severity set to 'normal' from 'serious' > reassign 891633 ftp.debian.org Bug #891633 [aolserver4] aolserver4: Should this package be removed? Bug reassigned from package 'aolserver4' to 'ftp.debian.org'. No longer marked as found in versions 4.5.1-18.1. Ignoring request to alter fixed versions of bug #891633 to the same values previously set > retitle 891633 RM: aolserver4 -- RoQA; unmaintained upstream, alternatives > exist, low popcon Bug #891633 [ftp.debian.org] aolserver4: Should this package be removed? Changed Bug title to 'RM: aolserver4 -- RoQA; unmaintained upstream, alternatives exist, low popcon' from 'aolserver4: Should this package be removed?'. > End of message, stopping processing here. Please contact me if you need assistance. -- 891633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915532: marked as done (python3-astrometry package post-installation script subprocess returned error exit status 1)
Your message dated Wed, 5 Dec 2018 08:44:12 +0100 with message-id <481959a6-1ec5-fe07-5008-1c92afeba...@debian.org> and subject line Already fixed with the last upload has caused the Debian Bug report #915532, regarding python3-astrometry package post-installation script subprocess returned error exit status 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 915532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-astrometry Version: 0.76+dfsg-2 Severity: grave Justification: renders package unusable Dear Maintainer, I am unable to install the python3-astrometry package. Here is what happens: Paramétrage de python3-astrometry (0.76+dfsg-2) ... File "/usr/lib/python3/dist-packages/astrometry/util/EXIF.py", line 1183 y = 0L ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/astrometry/util/EXIF.py", line 1183 y = 0L ^ SyntaxError: invalid syntax dpkg: erreur de traitement du paquet python3-astrometry (--configure) : installed python3-astrometry package post-installation script subprocess returned error exit status 1 dpkg: des problèmes de dépendances empêchent la configuration de astrometry.net : astrometry.net dépend de python3-astrometry ; cependant : Le paquet python3-astrometry n'est pas encore configuré. dpkg: erreur de traitement du paquet astrometry.net (--configure) : problèmes de dépendances - laissé non configuré Des erreurs ont été rencontrées pendant l'exécution : python3-astrometry astrometry.net Regards, Christophe Roland -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-astrometry depends on: ii file1:5.34-2 ii libastrometry0 0.76+dfsg-2 ii libc6 2.28-1 ii libcairo2 1.16.0-1 ii libgsl232.5+dfsg-6 ii libgslcblas02.5+dfsg-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libnetpbm10 2:10.0-15.3+b2 ii libpng16-16 1.6.34-2 ii libwcs6 6.2-1 ii python3 3.7.1-2 ii python3-astropy 3.0.5-1 ii python3-numpy [python3-numpy-abi9] 1:1.15.4-2 ii zlib1g 1:1.2.11.dfsg-1 python3-astrometry recommends no packages. python3-astrometry suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: astrometry.net Source-Version: 0.76+dfsg-3 This is already fixed in the upload that was accepted a few hours ago. Cheers Ole--- End Message ---
Bug#915450: staden-io-lib FTBFS on big endian: test failures
Control: reopen 915460 Hi James, as always thanks for your timely and elaborate answer. On Tue, Dec 04, 2018 at 06:12:26PM +, James Bonfield wrote: > On Tue, Dec 04, 2018 at 07:53:35AM +0100, Andreas Tille wrote: > > unfortunately there is a series of new errors on different architectures. > > Here comes the first one. > > Hmm. Some of this at least appears to be a Debian specific thing. I can not exclude this but the fact that the issues are happening only on certain architectures while other architectures are fine is a good sign that there are other Debian systems that are OK. In general I'd recommend to have a look at https://buildd.debian.org/status/package.php?p=staden-io-lib to see what architectures are building nicely as well as links to the build logs of the others. > > > === testing ./data/c1#bounds.sam === > > > ./scram.test: 27: [: ./data/c1#bounds.sam: unexpected operator > > The [ .. unexpected operator normally comes about due to bashisms, > like if [ "$a" == "$b" ] then (etc). However this line doesn't do > that - it is a single equals (I *did* have a bashism there at one > point, but not in 1.14.11). I agree that this smells heavily like bashism and for sure we could even enforce bash for the specific build. When looking at https://salsa.debian.org/med-team/staden-io-lib/blob/master/tests/scram.test line 27 really contains the '==' (double equal) - I guess replacing it by '=' might (or might not) fix the issue. It seems that while it is actually a sh syntax error this does not lead to an actual failure of the test. I simply patched this in https://salsa.debian.org/med-team/staden-io-lib/blob/master/debian/patches/remove_bashism.patch and uploaded to exclude this as the source of any issue. In fact as you can see on the status page (first link above) the change did not changed anything - so this bashism has nothing to do with the underlying problem. > I've tested the test harness using both bash and dash and I do not get > these errors. I'm struggling to work out how come it reports this and > then continues regardless. It looks like the shell just has a warning > and doesn't treat it as a hard error. I'm confused! I guess the confusion is based on the assumption that the bashism was causing the failure - but it is not and there is some other issue causing the problem. > I'm curious to know if you're getting the same issue on x86-64 and > i386, but the more recent automakes sadly hide all test output if it > works even with VERBOSE=1 on, grrr. (The only reason I stick with > autotools is because cmake is even worse!) > > > > ../progs/scramble ./data/c1#bounds.sam test.out/c1#bounds.sam > > > ../progs/scramble -r ./data/c1.fa ./data/c1#bounds.sam > > > test.out/c1#bounds.full.cram > > > ../progs/scramble ./data/c1#bounds.sam > test.out/tmp.sam > > > ../progs/scramble test.out/c1#bounds.full.cram > > > > test.out/c1#bounds.full.sam > > > ../progs/scramble -O bam test.out/c1#bounds.full.cram > > > > test.out/c1#bounds.full.bam > > > ../progs/scramble test.out/c1#bounds.full.bam test.out/tmp.sam > > > Invalid CRC in Deflate stream: 6614764d vs 6614 > > > Failed to open file test.out/c1#bounds.full.bam > > > FAIL scram.test (exit status: 1) > > This however appears to be a genuine bug. I'll try and reproduce it. > > I'm guessing I'll need the exact OS rather than the RedHat based AWS > image I launched last time to test non-intel platforms. > Do you have AWS-ified Debian ARM images for people test launch tests > against? Debian has developer machines with purpose "Porterbox"[1] where Debian developers can get ssh access. If externals want access they can apply for it and it needs a signed mail from a DD to confirm that application. The process is not really straightforward and I for myself prefer to ask on the according mailing lists for help from porters since I usually have no idea about those architectures and porters to my perception are very helpful (in most cases). Kind regards Andreas. [1] https://db.debian.org/machines.cgi -- http://fam-tille.de
Processed: Re: Bug#915450: staden-io-lib FTBFS on big endian: test failures
Processing control commands:
> reopen 915460
Bug #915460 {Done: Andreas Tille } [src:staden-io-lib]
staden-io-lib FTBFS on armel: scramble: cram_codecs.c:1441:
cram_huffman_encode_init: Assertion `hi->data.i > 0' failed.
'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 staden-io-lib/1.14.11-3.
--
915450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915450
915460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#894359: marked as done (beast2-mcmc build depends on openjdk-8-jdk)
Your message dated Wed, 05 Dec 2018 07:34:11 + with message-id and subject line Bug#894359: fixed in beast2-mcmc 2.5.1+dfsg-1 has caused the Debian Bug report #894359, regarding beast2-mcmc build depends on openjdk-8-jdk 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.) -- 894359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: beast2-mcmc Version: 2.4.4+dfsg-1 Severity: serious Tags: buster sid beast2-mcmc build depends on openjdk-8-jdk, which is not expected to be part of the buster release. If possible, this should be changed to default-jdk (this currently depends on openjdk-9-jdk). In a semi-related note, the beast2-mcmc runtime dependency openjdk-8-jre | java8-runtime should be default-jre | java8-runtime --- End Message --- --- Begin Message --- Source: beast2-mcmc Source-Version: 2.5.1+dfsg-1 We believe that the bug you reported is fixed in the latest version of beast2-mcmc, 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 894...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated beast2-mcmc 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: Wed, 05 Dec 2018 07:57:09 +0100 Source: beast2-mcmc Binary: beast2-mcmc beast2-mcmc-examples beast2-mcmc-doc Architecture: source Version: 2.5.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: beast2-mcmc - Bayesian MCMC phylogenetic inference beast2-mcmc-doc - Bayesian MCMC phylogenetic inference - documentation beast2-mcmc-examples - Bayesian MCMC phylogenetic inference - example data Closes: 894359 Changes: beast2-mcmc (2.5.1+dfsg-1) unstable; urgency=medium . [ Steffen Moeller ] * d/u/metadata: - added RRIDs - yamllint cleanliness . [ Andreas Tille ] * New upstream version * Point Vcs fields to salsa.debian.org * debhelper 11 * Build-Depends: s/openjdk-8-jdk/default-jdk/ Closes: #894359 * Depends: s/openjdk-8-jre | java8-runtime/default-jre | java9-runtime/ * d/rules: Add antlr4-runtime.jar to CLASS_PATH * Standards-Version: 4.2.1 * d/rules: Do not parse d/changelog . [ Jelmer Vernooij ] * Use secure copyright file specification URI. * Trim trailing whitespace. Checksums-Sha1: 86fe65ffee88a3b99740192edaea168477a05c27 2349 beast2-mcmc_2.5.1+dfsg-1.dsc 65385495eec344db8c2760541423184a1ad1cf86 22306772 beast2-mcmc_2.5.1+dfsg.orig.tar.xz be0dc5fee562d0c209f868b18aee9c54de27629f 10232 beast2-mcmc_2.5.1+dfsg-1.debian.tar.xz Checksums-Sha256: 9bd8bea1fb5a7d477fc22cd1e7992e61a0c441b87e1244e863eaebf3c8307b6d 2349 beast2-mcmc_2.5.1+dfsg-1.dsc f14c5034995383e7bc75dc49cd7c91375b0bd93cb84594ffdb67d589ca51ada8 22306772 beast2-mcmc_2.5.1+dfsg.orig.tar.xz f243128639c71c22a6bc41f90f82061351d257c3251b1d2282245db12b9a7286 10232 beast2-mcmc_2.5.1+dfsg-1.debian.tar.xz Files: 267f7adeffde22cc476a8cfc650dd92f 2349 science optional beast2-mcmc_2.5.1+dfsg-1.dsc 75bf7803d258c8f85899f19904793396 22306772 science optional beast2-mcmc_2.5.1+dfsg.orig.tar.xz bcbba1587fdb6d775fc98014fff8c7c3 10232 science optional beast2-mcmc_2.5.1+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlwHe5cRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHa6Q//eObprpydeVqmV3zrVjlmbU8rdMlvtvnW 3UQfa2B0obFuBskCSGsRpRgIEPQT3Ou+iRNNKGHQtsj89w8GaxrAZDRjmEN2Yhq+ fiyTa9/JEcoCnKjiDTZvWOVJ4qCCPSEu2A46xBAOJEZ2ViLQM9pn0Vu48hNr8IOZ lv0Fpq6H5VnH5Zs8X2t5MZq5ebrgVuc0xUXI7YgXwJ1c88+rOWGHLjNGKcasWzpq UNlyzA5iBciylA+I6Wn/2VmCusR9NYMYtJR8qYaAvfV8mzGbU/a4oG5RG9S7fVcM Zc+R5/N5eOXdYb84aEyvReAMN0sFJ5Pw7OVPG8COOP7AFGppOG/mz2gza/jlSCnM HM73sVdx2leL49RHjyxmVs+8+tvxDCT+hDIkQheAwF1q2idXysYcuZ1kTmUmFgii mZDqyPUly7Ml55GDvpAp1G2q6FGosEzq0/nRMDYkubeSQADB2CFpEHHT4EndzOZE STvCgOSPdg3XxqUqa/4FNfHmj7A7G/Nl+8V6r54Rhn/+UQibFvD10XAq2Uuk6GkI CwbntGwHHVi+mlo3y2LTWamEEUQQ/yADwDLzMJsuiMLb0gGNfodM/nf6P/wsf1T8 OKmk+MbnycfsF/McMFTxOUB17MorhDyFUIKB87jXh5i3f397RWq1zo/MOe+Q7S/P S2HijjUCvuU= =X+r7 -END PGP SIGNATURE End Message ---
Processed: Re: Bug#915450: staden-io-lib FTBFS on big endian: test failures
Processing control commands: > reopen 915460 Bug #915460 [src:staden-io-lib] staden-io-lib FTBFS on armel: scramble: cram_codecs.c:1441: cram_huffman_encode_init: Assertion `hi->data.i > 0' failed. Bug 915460 is not marked as done; doing nothing. -- 915460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#915450: staden-io-lib FTBFS on big endian: test failures
Processing control commands: > reopen 915460 Bug #915460 [src:staden-io-lib] staden-io-lib FTBFS on armel: scramble: cram_codecs.c:1441: cram_huffman_encode_init: Assertion `hi->data.i > 0' failed. Bug 915460 is not marked as done; doing nothing. -- 915459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915459 915460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#894359: Help needed to port beast2-mcmc to Java 9
Thanks a lot, Andreas. On Wed, Nov 14, 2018 at 01:28:01AM +0100, Emmanuel Bourg wrote: > On Mon, 9 Apr 2018 13:24:51 +0200 Andreas Tille wrote: > > > [javac] import com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl; > > [javac] ^ > > [javac] > > /build/beast2-mcmc-2.4.8+dfsg/src/beast/util/XMLParserUtils.java:120: > > warning: CoreDocumentImpl is internal proprietary API and may be removed in > > a future release > > [javac] ((CoreDocumentImpl) doc).putIdentifier(id, > > (Element) node); > > [javac] ^ > > [javac] > > /build/beast2-mcmc-2.4.8+dfsg/src/beast/util/TreeParser.java:353: error: > > cannot find symbol > > [javac] CharStream charStream = CharStreams.fromString(newick); > > [javac] ^ > > [javac] symbol: variable CharStreams > > [javac] location: class TreeParser > > [javac] > > /build/beast2-mcmc-2.4.8+dfsg/src/beast/util/treeparser/NewickLexer.java:98: > > error: method does not override or implement a method from a supertype > > [javac] @Override > > [javac] ^ > > Hi Andreas, > > I've pushed a fix for this issue and now beast2-mcmc builds fine with > antlr 4.6. Could you give it a try? If it works that would allow us to > move forward without waiting for antlr 4.7. > > Emmanuel Bourg > -- http://fam-tille.de
Bug#914897: #914897: debootstrap, buster: Please disabled merged /usr by default
Hi, Hideki Yamane writes: > On Sun, 2 Dec 2018 15:15:21 + > Simon McVittie wrote: >> > - What is the problem? (broken build for which packages? Just R?) >> >> The problem we're aware of is: >> >> Some packages auto-detect the absolute path to an executable (for example >> bash or perl) and hard-code it into their output (for example the #! line >> of the bash scripts in quilt). > > Can we check and track this behavior in our packages? The Reproducible Builds project was so kind to help and now runs one build in a non-merged-/usr and a second build in a merged-/usr environment. Packages that hardcode the path to utilities, but would pick up the wrong one in a merged-/usr environment will result in a difference between the two builds and can thus be found. See [1] for an overview of issues found this way; as the entire archive was already rebuilt in this setup, there shouldn't be many more issues of this type that we don't know about[2]. Not all of these differences even cause issues as in a few packages the utility with the hardcoded path is not even used at all. Bug reports were already submitted for over half the packages, often including a simple patch (usually something like adding BASH=/bin/bash to dh_auto_configure). So we look to be on a good track to address the remaining issues. I don't think that the debootstrap default has to be reverted temporarily again to deal with this: there are only very few packages causing problems and these should have a patch soon. In addition one has to actually built one of the very few packages in a merged-/usr environment and then install them in a non-merged-/usr environment to actually trigger the problem and debootstrap already defaults to non-merged-usr for buildd chroots for now. Ansgar [1] https://tests.reproducible-builds.org/debian/issues/unstable/paths_vary_due_to_usrmerge_issue.html [2] https://bugs.debian.org/914897#81
Processed: Re: Bug#915585: debian-edu-artwork-spacefun: fails to install: update-alternatives: error: alternative path /usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg does
Processing control commands: > fixed -1 20181204-1 Bug #915585 [debian-edu-artwork-spacefun] debian-edu-artwork-spacefun: fails to install: update-alternatives: error: alternative path /usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg doesn't exist Marked as fixed in versions debian-edu-artwork-legacy/20181204-1. > close -1 Bug #915585 [debian-edu-artwork-spacefun] debian-edu-artwork-spacefun: fails to install: update-alternatives: error: alternative path /usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg doesn't exist Marked Bug as done -- 915585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915426: git breaks git-remote-hg autopkgtest
Paul Gevers wrote: > https://ci.debian.net/data/autopkgtest/testing/amd64/g/git-remote-hg/1428119/log.gz > > not ok 32 - pull tags The package ought to run "make TEST_OPTS=-v" to produce a more useful log[*]. Bisects to the following Git change: e198b3a740409fabe5ba774c5f1255b55fdd21c1 is the first bad commit commit e198b3a740409fabe5ba774c5f1255b55fdd21c1 Author: Junio C Hamano Date: Tue Sep 25 13:25:04 2018 -0700 fetch: replace string-list used as a look-up table with a hashmap In find_non_local_tags() helper function (used to implement the "follow tags"), we use string_list_has_string() on two string lists as a way to see if a refname has already been processed, etc. All this code predates more modern in-core lookup API like hashmap; replace them with two hashmaps and one string list---the hashmaps are used for look-ups and the string list is to keep the order of items in the returned result stable (which is the only single thing hashmap does worse than lookups on string-list). Similarly, get_ref_map() uses another string-list as a look-up table for existing refs. Replace it with a hashmap. Signed-off-by: Junio C Hamano [*] expecting success: test_when_finished "rm -rf hgrepo gitrepo" && ( hg init hgrepo && cd hgrepo && echo one > content && hg add content && hg commit -m one ) && git clone "hg::hgrepo" gitrepo && (cd hgrepo && hg tag v1.0) && (cd gitrepo && git pull) && echo "v1.0" > expected && git --git-dir=gitrepo/.git tag > actual && test_cmp expected actual Cloning into 'gitrepo'... WARNING: capability_push is disabled, only do so when really sure WARNING: various enhanced features might fail in subtle ways requesting all changes adding changesets adding manifests adding file changes added 1 changesets with 1 changes to 1 files new changesets 50e85c807eb0 progress revision walk 'bookmarks/master' (0/0) progress revision 0 'master' (0/1) WARNING: capability_push is disabled, only do so when really sure WARNING: various enhanced features might fail in subtle ways searching for changes adding changesets adding manifests adding file changes added 1 changesets with 1 changes to 1 files new changesets ff570a4c8fa2 progress revision 1 'default' (0/1) >From hg::/src/git-remote-hg/test/trash directory.main/tmp/hgrepo 5ac88dd..82ef3dd master -> origin/master 5ac88dd..82ef3dd branches/default -> origin/branches/default Updating 5ac88dd..82ef3dd Fast-forward .hgtags | 1 + 1 file changed, 1 insertion(+) create mode 100644 .hgtags --- expected2018-12-05 06:36:57.995012275 + +++ actual 2018-12-05 06:36:57.995012275 + @@ -1 +0,0 @@ -v1.0 not ok 32 - pull tags
Bug#915585: debian-edu-artwork-spacefun: fails to install: update-alternatives: error: alternative path /usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg doesn't exist
Control: fixed -1 20181204-1 Control: close -1 Hi Andreas, On Mi 05 Dez 2018 03:19:32 CET, Andreas Beckmann wrote: Package: debian-edu-artwork-spacefun Version: 20180909-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Setting up debian-edu-artwork-spacefun (20180909-1) ... update-alternatives: using /usr/share/desktop-base/debian-edu-spacefun-theme to provide /usr/share/desktop-base/active-theme (desktop-theme) in auto mode update-alternatives: using /usr/share/ldm/themes/debian-edu-spacefun to provide /usr/share/ldm/themes/default (ldm-theme) in auto mode update-alternatives: warning: alternative /usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg (part of link group desktop-background) doesn't exist; removing from list of alternatives update-alternatives: warning: /etc/alternatives/desktop-background is dangling; it will be updated with best choice update-alternatives: using /usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.png to provide /usr/share/images/desktop-base/desktop-background (desktop-background) in auto mode No schema files found: doing nothing. Setting up debian-edu-artwork-buster (2.10.1.0.3-1) ... update-alternatives: error: alternative path /usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg doesn't exist dpkg: error processing package debian-edu-artwork-buster (--configure): installed debian-edu-artwork-buster package post-installation script subprocess returned error exit status 2 Processing triggers for libc-bin (2.28-1) ... Processing triggers for systemd (239-14) ... Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.38.0+dfsg-6) ... Errors were encountered while processing: debian-edu-artwork-buster This issue should have been solved by yesterday's upload of 20181204-1. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpN8a3A2DYds.pgp Description: Digitale PGP-Signatur
Bug#915102: scilab: FTBFS on amd64: Could not find or use the Java package/jar jlatexmath-fop used by LaTex Rendering
Control: tags -1 + patch Hi, On Sun, 2 Dec 2018 19:06:53 +0100 Gilles Filippini wrote: > On Fri, 30 Nov 2018 14:57:04 +0100 Emilio Pozuelo Monfort > wrote: > > Source: scilab > > Version: 6.0.1-6 > > Severity: serious > > > > Hi, > > > > On a rebuild against libhdf5-103, scilab has failed on amd64 twice. The > > second > > failure was during configure: > > > > checking commons-logging... /usr/share/java/fop-transcoder-allinone.jar > > checking jlatexmath... /usr/share/java/jlatexmath-1.0.7.jar > > checking jlatexmath-fop... no > > configure: error: Could not find or use the Java package/jar jlatexmath-fop > > used by LaTex Rendering - FOP plugin (looking for package > > org.scilab.forge.jlatexmath.fop.JLaTeXMathObj) > > make[1]: *** [debian/rules:38: override_dh_auto_configure] Error 1 > > > > Full logs at > > https://buildd.debian.org/status/logs.php?pkg=scilab=6.0.1-6%2Bb1=amd64 > > AIUI this is due to libfop-java 2.3 now providing subsets jar in > addition to fop.jar: > > $ dpkg -L libfop-java | grep usr/share/java/ | grep 2\.3 > /usr/share/java/fop-2.3.jar > /usr/share/java/fop-core-2.3.jar > /usr/share/java/fop-events-2.3.jar > /usr/share/java/fop-sandbox-2.3.jar > /usr/share/java/fop-transcoder-2.3.jar > /usr/share/java/fop-transcoder-allinone-2.3.jar > /usr/share/java/fop-util-2.3.jar > > Then configure picks up fop-transcoder-allinone-2.3.jar instead of > fop-2.3.jar when looking for class org.apache.fop.pdf.PDFInfo: > > checking fop... /usr/share/java/fop-transcoder-allinone-2.3.jar > > I don't know how to fix that, but a temporary workaround would be to > patch configure.ac to force /usr/share/java/fop.jar into the classpath. Please find attached a path proposal. Thanks, _g. diff -Nru scilab-6.0.1/debian/changelog scilab-6.0.1/debian/changelog --- scilab-6.0.1/debian/changelog 2018-11-11 18:51:45.0 +0100 +++ scilab-6.0.1/debian/changelog 2018-12-04 22:51:10.0 +0100 @@ -1,3 +1,11 @@ +scilab (6.0.1-6.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * New patch force-fop-jar-into-classpath.patch: +force /usr/share/java/fop.jar into the classpath (Closes: #915102) + + -- Gilles Filippini Tue, 04 Dec 2018 22:51:10 +0100 + scilab (6.0.1-6) unstable; urgency=medium * Bump std-ver to 4.2.1. diff -Nru scilab-6.0.1/debian/patches/force-fop-jar-into-classpath.patch scilab-6.0.1/debian/patches/force-fop-jar-into-classpath.patch --- scilab-6.0.1/debian/patches/force-fop-jar-into-classpath.patch 1970-01-01 01:00:00.0 +0100 +++ scilab-6.0.1/debian/patches/force-fop-jar-into-classpath.patch 2018-12-04 22:51:10.0 +0100 @@ -0,0 +1,17 @@ +Description: Workaround for bug #915102 where AC_JAVA_CHECK_JAR picks up + one of the fop-.jar instead of fop.jar +Index: scilab-6.0.1/configure.ac +=== +--- scilab-6.0.1.orig/configure.ac scilab-6.0.1/configure.ac +@@ -1040,7 +1040,9 @@ interface for JOGL2 - or libGL (OpenGL l + + Mandatory for graphic_export features # + # XML to PDF/other Translator +-AC_JAVA_CHECK_JAR([fop],[org.apache.fop.pdf.PDFInfo],[XML to PDF Translator (fop)]) ++#AC_JAVA_CHECK_JAR([fop],[org.apache.fop.pdf.PDFInfo],[XML to PDF Translator (fop)]) ++PACKAGE_JAR_FILE=/usr/share/java/fop.jar ++ac_java_classpath=$ac_java_classpath:$PACKAGE_JAR_FILE + FOP=$PACKAGE_JAR_FILE + AC_SUBST(FOP) + diff -Nru scilab-6.0.1/debian/patches/series scilab-6.0.1/debian/patches/series --- scilab-6.0.1/debian/patches/series 2018-11-11 18:51:45.0 +0100 +++ scilab-6.0.1/debian/patches/series 2018-12-04 22:47:46.0 +0100 @@ -21,3 +21,4 @@ set_class_path.patch use_outside_font.patch java11-compatibility.patch +force-fop-jar-into-classpath.patch signature.asc Description: OpenPGP digital signature
Processed: Re: scilab: FTBFS on amd64: Could not find or use the Java package/jar jlatexmath-fop used by LaTex Rendering
Processing control commands: > tags -1 + patch Bug #915102 [src:scilab] scilab: FTBFS on amd64: Could not find or use the Java package/jar jlatexmath-fop used by LaTex Rendering Added tag(s) patch. -- 915102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: git breaks git-remote-hg autopkgtest
Processing commands for cont...@bugs.debian.org: > reassign 915426 git-remote-hg 0.4-0.1 Bug #915426 [src:git, src:git-remote-hg] git breaks git-remote-hg autopkgtest Bug reassigned from package 'src:git, src:git-remote-hg' to 'git-remote-hg'. No longer marked as found in versions git/1:2.20.0~rc2-1 and git-remote-hg/0.4-0.1. Ignoring request to alter fixed versions of bug #915426 to the same values previously set Bug #915426 [git-remote-hg] git breaks git-remote-hg autopkgtest Marked as found in versions git-remote-hg/0.4-0.1. > affects 915426 + git Bug #915426 [git-remote-hg] git breaks git-remote-hg autopkgtest Added indication that 915426 affects git > End of message, stopping processing here. Please contact me if you need assistance. -- 915426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915404: marked as done (htslib: mipsel accidentally dropped from architecture list)
Your message dated Wed, 05 Dec 2018 05:22:02 + with message-id and subject line Bug#915404: fixed in htslib 1.9-5 has caused the Debian Bug report #915404, regarding htslib: mipsel accidentally dropped from architecture list 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.) -- 915404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: htslib Version: 1.9-3 Severity: serious Hi, In [1], the intention was to drop i386 from the architecture list, as the commit message says. However mipsel was forgotten there. In [2], mipsel got readded for one of those binaries. However it is still missing from the other two, breaking build-rdeps of libhts-dev. Please add mipsel back. [1] https://salsa.debian.org/med-team/htslib/commit/01db69dc17c02b4a056269570b8442d0436b0884 [2] https://salsa.debian.org/med-team/htslib/commit/024c3225f88036a80ad0e71575a335f876eae1ca --- End Message --- --- Begin Message --- Source: htslib Source-Version: 1.9-5 We believe that the bug you reported is fixed in the latest version of htslib, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated htslib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 04 Dec 2018 20:56:12 -0800 Source: htslib Binary: libhts2 libhts-dev libhts-private-dev htslib-test tabix Architecture: source Version: 1.9-5 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Michael R. Crusoe Description: htslib-test - Test data for HTSlib libhts-dev - development files for the HTSlib libhts-private-dev - private development files for the HTSlib (use with care) libhts2- C library for high-throughput sequencing data formats tabix - generic indexer for TAB-delimited genome position files Closes: 915404 Changes: htslib (1.9-5) unstable; urgency=medium . * Add libdeflate for DEFLATE based (de)compression and its crc32 implementation. * Re-add mipsel to tabix & libhts-dev as well. (Closes: #915404) Checksums-Sha1: 80a8366f1dff64327e8876d5a11c976f10893784 2901 htslib_1.9-5.dsc eb9ee4c4a7f7c711cd76626a54f476b84ffa481f 13916 htslib_1.9-5.debian.tar.xz 9a02fd87cbfa8255b080b58aa8303e8695d74265 7503 htslib_1.9-5_source.buildinfo Checksums-Sha256: 25af1cd6daf6bffab7edfc3d0400064acc6ee75959aa334ca48952add0341cd0 2901 htslib_1.9-5.dsc 4b1d34b7b229f0fddc73a46091ff4b34d3569d827bea6d1944dcfa19c80ae721 13916 htslib_1.9-5.debian.tar.xz bc098c52d8e84362139a11e3ba57bea05b20256db4836faeca4b347868ce368f 7503 htslib_1.9-5_source.buildinfo Files: b4e1ad48b9741551c94af9d9b5b38bd6 2901 science optional htslib_1.9-5.dsc 1204186b004cf14258acaedce48517c9 13916 science optional htslib_1.9-5.debian.tar.xz b21f629970a1a93e32432438165d3c4a 7503 science optional htslib_1.9-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAlwHWo8ACgkQPCZ2P2xn 5uK8HRAAr8VOHKK2AYxy/KmsSDtnGxwAmO2Z5WGjI1D4kPh2PJcX0fKJKjijJXqv g+houBsBGLImOBUHXZBEhFJoouwb16rV8dEJIUFCN+7dhbChGtcWSvxzNr/aOBJ2 sl7L/63M6l6rACdysik2ZeZ0fsGds1T5FF7eBxYY/KoPHwrZ2s3MgNRtQhkw0PHX QMr9xvDMel7tTmjd/PFQI5yBoIlkTUUPKy4wEYQrGKrTinkOAAe9VGdr1o4AqEGz 6KZwsUIx8OBXZSEKJTxyv5C+RnelKUY3Yh6I4saL+2/sQ0mJkZIXyAcmMlAPfNFb g++aqWz9qz7OljcGIkzlqsOdvMGMLiEK1db+3vibsWCRrfEEGSBhiolGvCYs+sjR Dm+6dRDMieQDxN9Jw7DnjdsVvzIG2YVOteQ7Add7wAkzRIOlaYP8Ql+JFFW5pV8r e3VtBj63mRM6xiLqaxpTKK9/d81rRTD33AEuchXp+MqYwkxpA6eQ+CE01Ei7duV0 oqZad+0z6JQzbaE25FJyDrxYLW5EYZBWVikL9cd3vh4MAi7QTfMBmzHfWmYp/6dc DU+QZRt3skE50sBCpAh/aCZQ15a7TQiZEtzxC82+vyY2lhGz+hbY89bHaBik2hxQ BiiUuJDQW10QtbhSpBptGbBoreqBbhimJVfRRMfZep/yB1yRg2k= =sfvK -END PGP SIGNATURE End Message ---
Processed: block 912785 by 914838
Processing commands for cont...@bugs.debian.org: > block 912785 by 914838 Bug #912785 [src:afl] afl: Please switch to llvm-toolchain-7 912785 was not blocked by any bugs. 912785 was not blocking any bugs. Added blocking bug(s) of 912785: 914838 and 914770 > thanks Stopping processing here. Please contact me if you need assistance. -- 912785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912785 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915404: Bug #915404 in htslib marked as pending
Control: tag -1 pending Hello, Bug #915404 in htslib 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/med-team/htslib/commit/81e1ecba421cf8144072fc212f8efa5b97844a0a Re-add mipsel to tabix & libhts-dev as well. (Closes: #915404) (this message was generated automatically) -- Greetings https://bugs.debian.org/915404
Processed: Bug #915404 in htslib marked as pending
Processing control commands: > tag -1 pending Bug #915404 [src:htslib] htslib: mipsel accidentally dropped from architecture list Added tag(s) pending. -- 915404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915589: Not compatible with recent haskell-aeson
Source: debug-me Version: 1.20170810-2 Severity: serious Tags: ftbfs Control: forwarded -1 https://debug-me.branchable.com/bugs/fails_to_build_against_current_LTS_Haskell/ Current debug-me requires haskell-aeson older than 1.3. -- Sean Whitton signature.asc Description: PGP signature
Processed: Not compatible with recent haskell-aeson
Processing control commands: > forwarded -1 > https://debug-me.branchable.com/bugs/fails_to_build_against_current_LTS_Haskell/ Bug #915589 [src:debug-me] Not compatible with recent haskell-aeson Set Bug forwarded-to-address to 'https://debug-me.branchable.com/bugs/fails_to_build_against_current_LTS_Haskell/'. -- 915589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914897: #914897: debootstrap, buster: Please disabled merged /usr by default
Hi, Thanks Simon, it's perhaps clear for me now. On Sun, 2 Dec 2018 15:15:21 + Simon McVittie wrote: > > - What is the problem? (broken build for which packages? Just R?) > > The problem we're aware of is: > > Some packages auto-detect the absolute path to an executable (for example > bash or perl) and hard-code it into their output (for example the #! line > of the bash scripts in quilt). Can we check and track this behavior in our packages? Once disable merged-usr is good to prevent confusion but we detect such as a bug for manage non-merged-usr and merged-usr Debian system in the end, right? (or do you want to stay change in debootstrap 1.0.111 forever?) -- Hideki Yamane
Processed: found 905513 in 0.77.1-2, affects 915577
Processing commands for cont...@bugs.debian.org: > found 905513 0.77.1-2 Bug #905513 [sbuild-debian-developer-setup] sbuild-debian-developer-setup: unowned files after purge (policy 6.8, 10.8): /var/log/sbuild-update-all.log Marked as found in versions sbuild/0.77.1-2. > affects 915577 + haskell-mode Bug #915577 [elpa-haskell-mode] elpa-haskell-mode: missing Breaks+Replaces: haskell-mode (<< 16.1-4) Added indication that 915577 affects haskell-mode > thanks Stopping processing here. Please contact me if you need assistance. -- 905513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905513 915577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915587: nixnote2: unhandled symlink to directory conversion: /usr/share/nixnote2/help
Package: nixnote2 Version: 2.1.1~git20181202-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, an upgrade test with piuparts revealed that your package installs files over existing symlinks and possibly overwrites files owned by other packages. This usually means an old version of the package shipped a symlink but that was later replaced by a real (and non-empty) directory. This kind of overwriting another package's files cannot be detected by dpkg. This was observed on the following upgrade paths: testing -> sid For /usr/share/doc/PACKAGE this may not be problematic as long as both packages are installed, ship byte-for-byte identical files and are upgraded in lockstep. But once one of the involved packages gets removed, the other one will lose its documentation files, too, including the copyright file, which is a violation of Policy 12.5: https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information For other overwritten locations anything interesting may happen. Note that dpkg intentionally does not replace directories with symlinks and vice versa, you need the maintainer scripts to do this. See in particular the end of point 4 in https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade It is recommended to use the dpkg-maintscript-helper commands 'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14) to perform the conversion, ideally using d/$PACKAGE.maintscript. See dpkg-maintscript-helper(1) and dh_installdeb(1) for details. >From the attached log (scroll to the bottom...): 1m18.3s ERROR: installs objects over existing directory symlinks: /usr/share/nixnote2/help/about.html (nixnote2) != /usr/share/doc/nixnote2/help/about.html (?) /usr/share/nixnote2/help -> ../doc/nixnote2/help cheers, Andreas nixnote2_2.1.1~git20181202-1.log.gz Description: application/gzip
Bug#915586: tomcat9: fails to install: tomcat9.postinst: systemd-sysusers: not found
Package: tomcat9 Version: 9.0.13-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Preparing to unpack .../tomcat9_9.0.13-1_all.deb ... Unpacking tomcat9 (9.0.13-1) ... Setting up tomcat9 (9.0.13-1) ... /var/lib/dpkg/info/tomcat9.postinst: 16: /var/lib/dpkg/info/tomcat9.postinst: systemd-sysusers: not found dpkg: error processing package tomcat9 (--configure): installed tomcat9 package post-installation script subprocess returned error exit status 127 Errors were encountered while processing: tomcat9 cheers, Andreas tomcat9_9.0.13-1.log.gz Description: application/gzip
Bug#915585: debian-edu-artwork-spacefun: fails to install: update-alternatives: error: alternative path /usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg doesn't exist
Package: debian-edu-artwork-spacefun Version: 20180909-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up debian-edu-artwork-spacefun (20180909-1) ... update-alternatives: using /usr/share/desktop-base/debian-edu-spacefun-theme to provide /usr/share/desktop-base/active-theme (desktop-theme) in auto mode update-alternatives: using /usr/share/ldm/themes/debian-edu-spacefun to provide /usr/share/ldm/themes/default (ldm-theme) in auto mode update-alternatives: warning: alternative /usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg (part of link group desktop-background) doesn't exist; removing from list of alternatives update-alternatives: warning: /etc/alternatives/desktop-background is dangling; it will be updated with best choice update-alternatives: using /usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.png to provide /usr/share/images/desktop-base/desktop-background (desktop-background) in auto mode No schema files found: doing nothing. Setting up debian-edu-artwork-buster (2.10.1.0.3-1) ... update-alternatives: error: alternative path /usr/share/desktop-base/active-theme/wallpaper/contents/images/1920x1080.svg doesn't exist dpkg: error processing package debian-edu-artwork-buster (--configure): installed debian-edu-artwork-buster package post-installation script subprocess returned error exit status 2 Processing triggers for libc-bin (2.28-1) ... Processing triggers for systemd (239-14) ... Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.38.0+dfsg-6) ... Errors were encountered while processing: debian-edu-artwork-buster cheers, Andreas debian-edu-artwork-spacefun_20180909-1.log.gz Description: application/gzip
Bug#915584: dicoweb: fails to install with python 3.7
Package: dicoweb Version: 2.7-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3 (3.7.1-2) ... [Errno 2] No such file or directory: '/usr/share/dicoweb/settings.py' error running python rtupdate hook dicoweb dpkg: error processing package python3 (--configure): installed python3 package post-installation script subprocess returned error exit status 4 cheers, Andreas dicoweb_2.7-1.log.gz Description: application/gzip
Processed: reassign 752397 to libswt-gtk-3-java, fixed 752397 in 3.8.2-6+rm, reassign 911492 to src:htslib ...
Processing commands for cont...@bugs.debian.org:
> reassign 752397 libswt-gtk-3-java
Bug #752397 {Done: Debian FTP Masters }
[javahelper, libswt-gtk-3-java] javahelper doesn't add libswt-cairo-gtk-3-jni
when {java:Depends} is specified
Bug reassigned from package 'javahelper, libswt-gtk-3-java' to
'libswt-gtk-3-java'.
Ignoring request to alter found versions of bug #752397 to the same values
previously set
No longer marked as fixed in versions 3.8.2-6+rm.
> fixed 752397 3.8.2-6+rm
Bug #752397 {Done: Debian FTP Masters }
[libswt-gtk-3-java] javahelper doesn't add libswt-cairo-gtk-3-jni when
{java:Depends} is specified
There is no source info for the package 'libswt-gtk-3-java' at version
'3.8.2-6+rm' with architecture ''
Unable to make a source version for version '3.8.2-6+rm'
Marked as fixed in versions 3.8.2-6+rm.
> reassign 911492 src:htslib 1.9-3
Bug #911492 {Done: Andreas Tille } [src:htslib,
src:python-pysam] htslib breaks python-pysam autopkgtest
Bug reassigned from package 'src:htslib, src:python-pysam' to 'src:htslib'.
No longer marked as found in versions python-pysam/0.14+ds-2 and htslib/1.9-3.
No longer marked as fixed in versions htslib/1.9-4.
Bug #911492 {Done: Andreas Tille } [src:htslib] htslib breaks
python-pysam autopkgtest
Marked as found in versions htslib/1.9-3.
> fixed 911492 1.9-4
Bug #911492 {Done: Andreas Tille } [src:htslib] htslib breaks
python-pysam autopkgtest
Marked as fixed in versions htslib/1.9-4.
> reassign 912908 src:ruby-curb 0.9.6-1
Bug #912908 {Done: Cédric Boutillier } [src:curl,
src:ruby-curb] curl breaks ruby-curb autopkgtest
Bug reassigned from package 'src:curl, src:ruby-curb' to 'src:ruby-curb'.
No longer marked as found in versions curl/7.62.0-1 and ruby-curb/0.9.6-1.
No longer marked as fixed in versions ruby-curb/0.9.7-1.
Bug #912908 {Done: Cédric Boutillier } [src:ruby-curb] curl
breaks ruby-curb autopkgtest
Marked as found in versions ruby-curb/0.9.6-1.
> fixed 912908 0.9.7-1
Bug #912908 {Done: Cédric Boutillier } [src:ruby-curb] curl
breaks ruby-curb autopkgtest
Marked as fixed in versions ruby-curb/0.9.7-1.
> found 911612 5.0.10-2
Bug #911612 [tdiary-mode] tdiary-mode: files missing after upgrade from
stretch: /usr/share/emacs/site-lisp/tdiary-mode/{http,tdiary-mode}.el
Marked as found in versions tdiary-contrib/5.0.10-2.
> reassign 915220 src:cysignals 1.6.7+ds-4
Bug #915220 {Done: Jerome Benoit } [src:python3-defaults,
src:cysignals] python3-defaults breaks cysignals autopkgtest
Bug reassigned from package 'src:python3-defaults, src:cysignals' to
'src:cysignals'.
No longer marked as found in versions cysignals/1.6.7+ds-4 and
python3-defaults/3.7.1-2.
No longer marked as fixed in versions cysignals/1.7.2+ds-2.
Bug #915220 {Done: Jerome Benoit } [src:cysignals]
python3-defaults breaks cysignals autopkgtest
Marked as found in versions cysignals/1.6.7+ds-4.
> fixed 915220 1.7.2+ds-2
Bug #915220 {Done: Jerome Benoit } [src:cysignals]
python3-defaults breaks cysignals autopkgtest
Marked as fixed in versions cysignals/1.7.2+ds-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
752397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752397
911492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911492
911612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911612
912908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912908
915220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging 816756, found 915148 in 0.7.14-7
Processing commands for cont...@bugs.debian.org:
> tags 816756 + buster - stretch
Bug #816756 [php-pimple] php-pimple: Useless in Debian
Added tag(s) buster.
Bug #816756 [php-pimple] php-pimple: Useless in Debian
Removed tag(s) stretch.
> found 915148 0.7.14-7
Bug #915148 {Done: Jochen Sprickerhof } [src:ros-catkin]
cmake: regression in ros-ros-comm build
Marked as found in versions ros-catkin/0.7.14-7.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
816756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816756
915148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found 904396 in 1:0.9.18+r243-3
Processing commands for cont...@bugs.debian.org:
> found 904396 1:0.9.18+r243-3
Bug #904396 {Done: Adrian Bunk } [foma] foma: fails to upgrade
from 'sid' - trying to overwrite /usr/bin/cgflookup
Marked as found in versions foma/1:0.9.18+r243-3 and reopened.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
904396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#915430: marked as done (matplotlib: autopkgtest regression: ImportError: No module named matplotlib)
Your message dated Wed, 05 Dec 2018 00:52:34 + with message-id and subject line Bug#915430: fixed in matplotlib 2.2.3-2 has caused the Debian Bug report #915430, regarding matplotlib: autopkgtest regression: ImportError: No module named matplotlib 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.) -- 915430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: matplotlib Version: 2.2.3-1 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Control: affects -1 src:skimage Control: affects -1 src:sunpy Dear maintainers, With a recent upload of matplotlib the autopkgtest of matplotlib fails in testing when that autopkgtest is run with the binary packages of matplotlib from unstable. It passes when run with only packages from testing. In tabular form: passfail matplotlib from testing2.2.3-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is contributing to the delay of the migration to testing [1]. Can you please investigate the situation and fix it? If needed, please change the bug's severity. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=matplotlib https://ci.debian.net/data/autopkgtest/testing/amd64/m/matplotlib/1428746/log.gz autopkgtest [10:25:52]: test wxagg: [--- === WXAgg === === python2.7 === Traceback (most recent call last): File "test.py", line 4, in import matplotlib ImportError: No module named matplotlib autopkgtest [10:25:52]: test wxagg: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: matplotlib Source-Version: 2.2.3-2 We believe that the bug you reported is fixed in the latest version of matplotlib, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated matplotlib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 04 Dec 2018 19:21:13 -0500 Source: matplotlib Binary: python-matplotlib python3-matplotlib python-matplotlib-data python-matplotlib-doc python-matplotlib-dbg python3-matplotlib-dbg Architecture: source all amd64 Version: 2.2.3-2 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi Changed-By: Sandro Tosi Description: python-matplotlib - Python based plotting system in a style similar to Matlab python-matplotlib-data - Python based plotting system (data package) python-matplotlib-dbg - Python based plotting system (debug extension) python-matplotlib-doc - Python based plotting system (documentation package) python3-matplotlib - Python based plotting system in a style similar to Matlab (Python python3-matplotlib-dbg - Python based plotting system (debug extension, Python 3) Closes: 915430 Changes: matplotlib (2.2.3-2) unstable; urgency=medium . * debian/rules - more rework to install the modules files in the right locations; Closes: #915430 Checksums-Sha1: 00596fe9364d7b179a7fe7cc7154c15139da01ab 4308 matplotlib_2.2.3-2.dsc 2f29b7b774d5f2c4ed33ade026dfcce0e9baf35b 31868 matplotlib_2.2.3-2.debian.tar.xz fa38506ceb2e1869e51ef7b2eac97424ac37c51d 26878 matplotlib_2.2.3-2_amd64.buildinfo 0c6030e0142734a66e6652e6f63007a7ee11867c 4124124 python-matplotlib-data_2.2.3-2_all.deb 87dacb06041eb55d517f6104e9655230698bde1e 10121116 python-matplotlib-dbg_2.2.3-2_amd64.deb 4cd2082d9fe531f4728f274d2b67bc51b9324a82 64626848 python-matplotlib-doc_2.2.3-2_all.deb 512c39e85ee36379e35d493607cc981cc8a3bff8 5072812 python-matplotlib_2.2.3-2_amd64.deb 2f8698be9eed4bc1bfd81dd95ed3f6221b405f3e 430792 python3-matplotlib-dbg_2.2.3-2_amd64.deb 5a0d23a81ef11de26be18633b31f5c3b5a6e46f5 5079724 python3-matplotlib_2.2.3-2_amd64.deb Checksums-Sha256:
Bug#915582: Installs non-free binaries from cisco and google again
Package: firefox
Version: 62.0.3-1
Severity: serious
Justification: Policy §2.2.1
Mozilla changed the config options for the openh264 codec. The option
listed in /etc/firefox/firefox.fs (media.gmp-gmpopenh264.enabled) seems
to be no longer in use, instead about:config now lists the options
media.gmp-provider.enabled
media.gmp.decoder.enabled
media.gmp-widevinecdm.enabled
media.gmp.trial-create.enabled
And in addition to libgmpopenh264.so it also downloads and installs into
~/.mozilla a libwidevinecdm.so binary. Its license (contained in the
zip-archive from which it gets installed) reads
> "Google Inc. and its affiliates ("Google") own all legal right, title and
> interest in and to the content decryption module software ("Software") and
> related documentation, including any intellectual property rights in the
> Software. You may not use, modify, sell, or otherwise distribute the Software
> without a separate license agreement with Google. The Software is not open
> source software.
>
> If you are interested in licensing the Software, please contact
> widev...@google.com.
Cf. bug #769716 i believe these automated downloads should be disabled by
default in debian packages.
Thx
-- Package-specific info:
-- Addons package information
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (800, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.4-echse20181124 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages firefox depends on:
ii debianutils 4.8.6
ii fontconfig2.13.1-2
ii libasound21.1.7-1+b1
ii libatk1.0-0 2.30.0-1
ii libc6 2.28-1
ii libcairo-gobject2 1.16.0-1
ii libcairo2 1.16.0-1
ii libdbus-1-3 1.12.10-1
ii libdbus-glib-1-2 0.110-3
ii libevent-2.1-62.1.8-stable-4
ii libffi6 3.2.1-9
ii libfontconfig12.13.1-2
ii libfreetype6 2.9.1-3
ii libgcc1 1:8.2.0-10
ii libgdk-pixbuf2.0-02.38.0+dfsg-6
ii libglib2.0-0 2.58.1-2
ii libgtk-3-03.24.1-2
ii libjsoncpp1 1.7.4-3
ii libnspr4 2:4.20-1
ii libnss3 2:3.40-1
ii libpango-1.0-01.42.4-4
ii libsqlite3-0 3.26.0-1
ii libstartup-notification0 0.12-5
ii libstdc++68.2.0-10
ii libvpx5 1.7.0-3
ii libx11-6 2:1.6.7-1
ii libx11-xcb1 2:1.6.7-1
ii libxcb-shm0 1.13.1-1
ii libxcb1 1.13.1-1
ii libxcomposite11:0.4.4-2
ii libxdamage1 1:1.1.4-3
ii libxext6 2:1.3.3-1+b2
ii libxfixes31:5.0.3-1
ii libxrender1 1:0.9.10-1
ii libxt61:1.1.5-1
ii procps2:3.3.15-2
ii zlib1g1:1.2.11.dfsg-1
Versions of packages firefox recommends:
ii libavcodec58 7:4.0.3-1
Versions of packages firefox suggests:
ii fonts-lmodern 2.004.5-5
ii fonts-stix [otf-stix] 1.1.1-4
ii libcanberra0 0.30-6
ii libgssapi-krb5-2 1.16.1-1
ii libgtk2.0-02.24.32-3
ii pulseaudio 12.2-2
-- no debconf information
-- debsums errors found:
debsums: package firefox is not installed
Bug#915581: golang-github-gorilla-rpc-dev: missing Breaks+Replaces: golang-github-gorilla-rpc
Package: golang-github-gorilla-rpc-dev Version: 0.0~git20160927.22c016f-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../golang-github-gorilla-rpc-dev_0.0~git20160927.22c016f-2_all.deb ... Unpacking golang-github-gorilla-rpc-dev (0.0~git20160927.22c016f-2) ... dpkg: error processing archive /var/cache/apt/archives/golang-github-gorilla-rpc-dev_0.0~git20160927.22c016f-2_all.deb (--unpack): trying to overwrite '/usr/share/gocode/src/github.com/gorilla/rpc/doc.go', which is also in package golang-github-gorilla-rpc 0.0~git20160927.0.22c016f-1 Errors were encountered while processing: /var/cache/apt/archives/golang-github-gorilla-rpc-dev_0.0~git20160927.22c016f-2_all.deb cheers, Andreas golang-github-gorilla-rpc=0.0~git20160927.0.22c016f-1_golang-github-gorilla-rpc-dev=0.0~git20160927.22c016f-2.log.gz Description: application/gzip
Bug#915580: uctodata: missing Breaks+Replaces: libucto2 (<< 0.9.6-2)
Package: uctodata Version: 0.8-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../uctodata_0.8-1_all.deb ... Unpacking uctodata (0.8-1) ... dpkg: error processing archive /var/cache/apt/archives/uctodata_0.8-1_all.deb (--unpack): trying to overwrite '/usr/share/ucto/e-mail.rule', which is also in package libucto2:amd64 0.9.6-1+b1 Errors were encountered while processing: /var/cache/apt/archives/uctodata_0.8-1_all.deb The versioned contraint (<< 0.9.6-2) is expecting that an upload of ucto 0.9.6-2 will remove the files from libucto2 that are shipped currently in both uctodata and libucto2: usr/share/ucto/e-mail.rule usr/share/ucto/smiley.rule usr/share/ucto/standard-eos.eos usr/share/ucto/standard-quotes.quote usr/share/ucto/tokconfig-generic usr/share/ucto/url.rule cheers, Andreas libucto2=0.9.6-1+b1_uctodata=0.8-1.log.gz Description: application/gzip
Bug#915578: libtomcat9-embed-java: missing Breaks+Replaces: libtomcat8-embed-java
Package: libtomcat9-embed-java Version: 9.0.13-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libtomcat9-embed-java_9.0.13-1_all.deb ... Unpacking libtomcat9-embed-java (9.0.13-1) ... dpkg: error processing archive /var/cache/apt/archives/libtomcat9-embed-java_9.0.13-1_all.deb (--unpack): trying to overwrite '/usr/share/maven-repo/org/apache/tomcat/embed/tomcat-embed-core/debian/tomcat-embed-core-debian.pom', which is also in package libtomcat8-embed-java 8.5.35-2 Errors were encountered while processing: /var/cache/apt/archives/libtomcat9-embed-java_9.0.13-1_all.deb cheers, andreas libtomcat8-embed-java=8.5.35-2_libtomcat9-embed-java=9.0.13-1.log.gz Description: application/gzip
Bug#915577: elpa-haskell-mode: missing Breaks+Replaces: haskell-mode (<< 16.1-4)
Package: elpa-haskell-mode Version: 16.1-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../elpa-haskell-mode_16.1-4_all.deb ... Unpacking elpa-haskell-mode (16.1-4) ... dpkg: error processing archive /var/cache/apt/archives/elpa-haskell-mode_16.1-4_all.deb (--unpack): trying to overwrite '/usr/share/icons/locolor/scalable/logo.svg', which is also in package haskell-mode 16.1-3 Errors were encountered while processing: /var/cache/apt/archives/elpa-haskell-mode_16.1-4_all.deb cheers, Andreas haskell-mode=16.1-3_elpa-haskell-mode=16.1-4.log.gz Description: application/gzip
Bug#915575: libyaml-cpp-dev: ships /usr/include/{gmock,gtest}/*
Package: libyaml-cpp-dev Version: 0.6.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../libyaml-cpp-dev_0.6.2-1_amd64.deb ... Unpacking libyaml-cpp-dev (0.6.2-1) ... dpkg: error processing archive /var/cache/apt/archives/libyaml-cpp-dev_0.6.2-1_amd64.deb (--unpack): trying to overwrite '/usr/include/gmock/gmock-actions.h', which is also in package libgmock-dev:amd64 1.8.1-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libyaml-cpp-dev_0.6.2-1_amd64.deb Preparing to unpack .../libyaml-cpp-dev_0.6.2-1_amd64.deb ... Unpacking libyaml-cpp-dev (0.6.2-1) ... dpkg: error processing archive /var/cache/apt/archives/libyaml-cpp-dev_0.6.2-1_amd64.deb (--unpack): trying to overwrite '/usr/include/gtest/gtest-death-test.h', which is also in package libgtest-dev:amd64 1.8.1-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libyaml-cpp-dev_0.6.2-1_amd64.deb cheers, Andreas libgmock-dev=1.8.1-2_libyaml-cpp-dev=0.6.2-1.log.gz Description: application/gzip
Processed: Re: Bug#915572: intel-media-driver-non-free: FTBFS on i386
Processing control commands: > severity -1 important Bug #915572 [src:intel-media-driver-non-free] intel-media-driver-non-free: FTBFS on i386 Severity set to 'important' from 'serious' -- 915572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915572 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915574: libsimbody3.6: missing Breaks+Replaces: libsimbody3.5v5
Package: libsimbody3.6 Version: 3.6.1+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libsimbody3.6_3.6.1+dfsg-1_amd64.deb ... Unpacking libsimbody3.6:amd64 (3.6.1+dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/libsimbody3.6_3.6.1+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/simbody/libexec/simbody-visualizer', which is also in package libsimbody3.5v5:amd64 3.5.4+dfsg2-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libsimbody3.6_3.6.1+dfsg-1_amd64.deb cheers, Andreas libsimbody3.5v5=3.5.4+dfsg2-1_libsimbody3.6=3.6.1+dfsg-1.log.gz Description: application/gzip
Bug#915572: intel-media-driver-non-free: FTBFS on i386
Control: severity -1 important On 2018-12-05 00:27:28, Andreas Beckmann wrote: > Source: intel-media-driver-non-free > Version: 18.3.0+ds1-1 > Severity: serious > Justification: fails to build from source It never built there, so it's not a regression. Downgrading to important. Cheers > > Hi, > > your package FTBFS in a sid/i386 pbuilder chroot (on an amd64 host) > with some spurious missing includes. All are present in the file system. > > In file included from > /build/intel-media-driver-non-free-18.3.0+ds1/media_driver/linux/ult/ult_app/googletest/./include/gtest/gtest.h:54, > from > /build/intel-media-driver-non-free-18.3.0+ds1/media_driver/linux/ult/ult_app/googletest/src/gtest-all.cc:39: > /usr/include/c++/8/limits:42:10: fatal error: bits/c++config.h: No such file > or directory > #include > ^~ > compilation terminated. > make[3]: *** > [media_driver/linux/ult/ult_app/googletest/CMakeFiles/libgtest.dir/build.make:66: > > media_driver/linux/ult/ult_app/googletest/CMakeFiles/libgtest.dir/src/gtest-all.cc.o] > Error 1 > make[3]: *** Waiting for unfinished jobs > In file included from > /build/intel-media-driver-non-free-18.3.0+ds1/media_driver/linux/ult/ult_app/googletest/src/gtest_main.cc:30: > /usr/include/stdio.h:27:10: fatal error: bits/libc-header-start.h: No such > file or directory > #include > ^~ > compilation terminated. > make[3]: *** > [media_driver/linux/ult/ult_app/googletest/CMakeFiles/libgtest.dir/build.make:79: > > media_driver/linux/ult/ult_app/googletest/CMakeFiles/libgtest.dir/src/gtest_main.cc.o] > Error 1 > > The command lines are just too long to spot any obvious weirdness. > The full log is attached. > > I cannot reproduce this in an amd64 chroot. > > > Andreas -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#915572: intel-media-driver-non-free: FTBFS on i386
Source: intel-media-driver-non-free Version: 18.3.0+ds1-1 Severity: serious Justification: fails to build from source Hi, your package FTBFS in a sid/i386 pbuilder chroot (on an amd64 host) with some spurious missing includes. All are present in the file system. In file included from /build/intel-media-driver-non-free-18.3.0+ds1/media_driver/linux/ult/ult_app/googletest/./include/gtest/gtest.h:54, from /build/intel-media-driver-non-free-18.3.0+ds1/media_driver/linux/ult/ult_app/googletest/src/gtest-all.cc:39: /usr/include/c++/8/limits:42:10: fatal error: bits/c++config.h: No such file or directory #include ^~ compilation terminated. make[3]: *** [media_driver/linux/ult/ult_app/googletest/CMakeFiles/libgtest.dir/build.make:66: media_driver/linux/ult/ult_app/googletest/CMakeFiles/libgtest.dir/src/gtest-all.cc.o] Error 1 make[3]: *** Waiting for unfinished jobs In file included from /build/intel-media-driver-non-free-18.3.0+ds1/media_driver/linux/ult/ult_app/googletest/src/gtest_main.cc:30: /usr/include/stdio.h:27:10: fatal error: bits/libc-header-start.h: No such file or directory #include ^~ compilation terminated. make[3]: *** [media_driver/linux/ult/ult_app/googletest/CMakeFiles/libgtest.dir/build.make:79: media_driver/linux/ult/ult_app/googletest/CMakeFiles/libgtest.dir/src/gtest_main.cc.o] Error 1 The command lines are just too long to spot any obvious weirdness. The full log is attached. I cannot reproduce this in an amd64 chroot. Andreas intel-media-driver-non-free_18.3.0+ds1-1.log.gz Description: application/gzip
Processed: Bug #879228 in swt-gtk marked as pending
Processing control commands: > tag -1 pending Bug #879228 [libswt-webkit-gtk-4-jni] libswt-webkit-gtk-4-jni: Missing webkit dependency Added tag(s) pending. -- 879228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#879228: Bug #879228 in swt-gtk marked as pending
Control: tag -1 pending Hello, Bug #879228 in swt-gtk 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/swt-gtk/commit/c05f34735aea23413c0ff3f096cdb21a70cd0f4f Have libswt-webkit-gtk-4-jni depend on libwebkit2gtk-4.0-37 (Closes: #879228) (this message was generated automatically) -- Greetings https://bugs.debian.org/879228
Bug#907518: [RFC] Disable TLSv1.0 by default, but allow enabling it
On Tue, Dec 04, 2018 at 01:00:08PM +0100, Andrej Shadura wrote: > This patch is not intended to be merged into the upstream code, but I > would still like to receive comments from people involved in development. > > In the Debian bug reports #907518 and #911297 (see below), people complained > that OpenSSL 1.1.1 disables TLSv1.0 and some other insecure settings by > default, but some older networks may still require their support: This is going to break lots of WLAN connections in practice.. Unfortunately, enterprise authentication servers are something that do not really get updated easily and when something is updated, things tends to break horribly.. For that to change, I guess there would need to be a change in significant number of client devices (or something very widely used device) to start rejecting the connections with a clear message indicating that the issue is in the server and not something that the client device can fix on its own. In practice, though, wpa_supplicant may have to start overriding this type of system-wide enforcement to prevent cases where the user has no way of impact the authentication server operator, so something may need to be merged into hostap.git to get more reasonable behavior than "not working until server is updated (which may never happen)". It should also be noted that use of TLS in EAP is quite different from other cases like HTTPS, i.e., EAP uses very limited amount of application data (or even none of it in case of EAP-TLS), so the impact of various TLS issues with past versions may be different as well. There are some clear cases like not allowing too short DH keys to be used which can certainly be justified from security view point, but fully disabling TLS v1.0 by default may not be something that EAP world is ready for yet.. Some ciphers might also be possible to disable without losing too much interoperability with currently deployed authentication servers. -- Jouni MalinenPGP id EFC895FA
Bug#828483: osslsigncode: FTBFS with openssl 1.1.0
On Tue, 4 Dec 2018 23:24:56 +0100, Stephen Kitt wrote: > On Tue, 4 Dec 2018 19:09:22 +0100, Moritz Mühlenhoff wrote: > > On Tue, Jan 16, 2018 at 09:05:15PM +0100, Stephen Kitt wrote: > > > I’ve been meaning to look into all this further, but help is > > > welcome. > > > > This is unfixed for quite a while and the upstream homepage now > > mentions "This is now - and has been for a long while - abandonware". > > > > Shall we remove osslsigncode from the archive? > > Yes, thanks, it’s time to bite the bullet. I’ve filed a removal request. #915569 Regards, Stephen pgpK3JbMnFSLv.pgp Description: OpenPGP digital signature
Bug#828483: osslsigncode: FTBFS with openssl 1.1.0
Hi Moritz, On Tue, 4 Dec 2018 19:09:22 +0100, Moritz Mühlenhoff wrote: > On Tue, Jan 16, 2018 at 09:05:15PM +0100, Stephen Kitt wrote: > > I’ve been meaning to look into all this further, but help is welcome. > > This is unfixed for quite a while and the upstream homepage now > mentions "This is now - and has been for a long while - abandonware". > > Shall we remove osslsigncode from the archive? Yes, thanks, it’s time to bite the bullet. I’ve filed a removal request. Regards, Stephen pgplK3DaSbWdv.pgp Description: OpenPGP digital signature
Bug#915563: php-react-zmq : Depends: php-react-event-loop (< 0.6~~) but 1.0.0-1 is to be installed
Package: php-react-zmq Version: 0.4.0-1 Severity: serious The following packages have unmet dependencies: php-react-zmq : Depends: php-react-event-loop (< 0.6~~) but 1.0.0-1 is to be installed
Processed: fixed 853608 in pdftk/2.02-5
Processing commands for cont...@bugs.debian.org: > fixed 853608 pdftk/2.02-5 Bug #853608 [src:pdftk] pdftk: ftbfs with GCC-7 Marked as fixed in versions pdftk/2.02-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 853608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#914897: debating the wrong thing
Adam Borowski writes: > On Tue, Dec 04, 2018 at 06:48:45PM +0100, Ansgar Burchardt wrote: >> In very rare cases (an estimated 0.3% of the archive or so). I'm fairly >> confident that for more than 0.3% of the archive something can go wrong >> when building in non-clean environments. > > Your figure of ~80 packages counts only packages which went through a > reproducible-builds rebuild. So only all? > We later learned only a part of the archive got rebuilt since the bad > debootstrap backport. Yes, some packages were not yet rebuilt in testing, but having them rebuilt in unstable is enough. >> We had the discussion (usrmerge as default) already quite some time >> ago. Why start again at zero? As a random reference, the D-I Stretch >> RC 1 release announcement explicitly stated: >> >> +--- >> | * The switch to merged-/usr as the default setting for debootstrap >> |was reverted since it uncovered a number of important issues which >> |might not be all fixed in time for stretch. This setting is >> |expected to come back as the default at the beginning of the next >> |release cycle. >> +--- >> >> And just that happened (except a bit later). > > Except that the change went live only on 2018-11-10, then waited until > buildds recreated their chroots, then until dinstall and mirror push... No, anyone using testing/unstable to setup a new build chroot since June should have gotten a merged-/usr chroot. That no issues were found earlier is probably related to there being not so many issues. (Fun fact: there are ~3k debootstrap installations on testing/unstable, compared to 6.2k on stable and 2k on oldstable according to popcon.) Anyway, buildds are not using merged-/usr, so there is no problem with them. > and the sky started falling immediately after that. Hmm, two packages or so were reported to be broken. That is a quite high standard for "sky falling". What would you call an upload that breaks more packages? The monthly apocalypse which we deal with just fine? >> You could have easily asked the tech-ctte back then (or even before) >> instead of waiting until shortly before the Buster freeze and after >> people invested more work. > > It was only shortly before the Buster freeze that we saw this change in > action! Had the switch get flipped sooner we'd have a chance to see the > results. By now, it's much too late to fix things before the freeze > (and I don't see how they could be fixed even had we two years of > time). You keep saying that it is too late to fix anything or that it is too much work, but why do you think so? I've looked at patching packages and how many packages need changes and it does not seem much work; indeed after a week about half of the packages already have a (usually trivial) patch. If you think it is too much work or too many things break, please at least give an estimate of what you are talking about... I feel like only one side is doing any research here. > By now, all we can do is damage control. Which can be a hasty force-merge > or a hasty revert. Unless you can somehow make dpkg-dev omniscient. If we keep merged-/usr as default then we can /recommend/ people to install usrmerge to switch to merged-/usr; reducing the difference between newly-installed and existing setups is a good idea IMHO. I think I filed a report for this two years ago. Maybe we should also mention somewhere that it might be useful to not switch build environments (yet). Ansgar
Processed: severity of 915514 is serious
Processing commands for cont...@bugs.debian.org: > severity 915514 serious Bug #915514 [pysph] pysph: Missing build-dependency on python-pytest-runner, Debian builds pulling source from network? Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 915514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905674: GNU Parallel patch
I will update Debian's GNU parallel as soon as I can (before this next weekend, if I can). Thanks for all the discussion, Rogério. On Tue, Dec 4, 2018 at 1:12 PM Didier 'OdyX' Raboud wrote: > > Control: clone -1 -2 > Control: retitle -2 parallel 20161222-1.1 NMU removes upstream "--will-cite" > functionality > Control: reopen -2 > Control: notfound -2 20161222 > Control: found -2 20161222-1.1 > Control: severity -2 important > > Dear Ole, > > Le lundi, 3 décembre 2018, 18.55:00 h CET Ole Tange a écrit : > > I have noticed that you have submitted a patch and closed this bug: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905674#77 > > > > I am sure you are trying to do what is best for free software. But > > what looks like a good idea in the short run, may be a bad idea in the > > long run. The long term survival of Debian depends on others building > > free software that can be packaged, so destroying these people's > > livelihood is a bad long term strategy. > > > > In the reasoning for the patch you state: > > > Quoting the gpl-faq: > > [... https://www.gnu.org/licenses/gpl-faq.en.html#RequireCitation ...] > > > > > Therefore, removing this to make parallel GPL-compliant. > > > > I think this is due to a misunderstanding. > > > > Maybe you not aware that Richard M. Stallman together with the GNU > > leaders have cleared the wording and the use of the citation notice, > > and that he sees it as complying fully with GPLv3? > > I was not, but, as Debian Developer, I don't feel bound by RMS' (and "GNU > leaders", whomever this designates) statements about GPLv3. What mattered for > this now-closed bugreport is our DFSG; specifically it's article 1 (emphasis > mine) and 5. > > > DFSG 1: Free Redistribution > > The license of a Debian component may not restrict any party from selling or > > giving away the software as a component of an aggregate software > > distribution containing programs from several different sources. The license > > *may not require a royalty or other fee* for such sale. > > > DFSG 5: No Discrimination Against Persons or Groups > > The license must not discriminate against any person or group of persons. > > Le lundi, 3 décembre 2018, 18.55:00 h CET Ole Tange a écrit : > > Your patch therefore does not change the GPLv3-compliancy: The code > > was already compliant. > > I disagree; my understanding is that RMS declared parallel to carry no > problem with regards to GPLv3 compliance in October 2018, probably for the > latest upstream release. > > But Debian ships parallel 20161222 which: > * contains a request for the user to promise academic citation, > * imposes the use of either "--will-cite" or the presence of a > `~.parallel/will-cite`, which makes it unnecessarily burdensome to use > in a scripted manner. > > This is a clear attempt at side-stepping GPLv3 software freedoms by using > guilt-inducting language. As the GPLv3 allows (almost any) modification, I've > just went and did that, also to ensure that src:parallel can stay in the > Debian main archive, where it belongs. > > > But what your patch *does* do, is to make it harder to earn a living > > from developing GNU Parallel and will make it much harder for me to > > justify spending time maintaining GNU Parallel. > > Be careful with such arguments: by merely distributing GNU parallel in its > main archive, Debian is also vastly expanding the availability of GNU > parallel. And if you do insist on getting Debian to rename it, you'll > likely lose any incentive from "renamed GNU parallel" users getting it from > the Debian archive. > > > As Nadia Eghbal puts it in > > https://www.slideshare.net/NadiaEghbal/consider-the-maintainer: > > > > "Is it alright to compromise, or even deliberately ignore, the > > happiness of maintainers so we that can enjoy free and open source > > software?" > > > > This describes very well what you are doing with the patch, and I > > refuse to think that was your goal. > > For the record: > * My primary goal was to remove a "Release Critical" bug from Debian's next > stable release, during a Bug Squashing Party; > * While looking at this bug, it seemed obvious to me that merely removing the > obnoxious phrasing and functionality was an easy way to fix this bug; in a > GPLv3- and DFSG-compatible way. > * I am not the Debian maintainer of src:parallel, so my contribution was one- > -off. > * I did a Non-Maintainer Upload immediately, following DevRef 5.11.1: > > https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#nmu-guidelines > * I do think that making fine free software unnecessarily cumbersome to use, > only to increase user's knowledge of the original author's funding > initiatives is bad practice. This reduces the quality of software and > is really on the line of what makes software really "free software" > (I'm fine to disagree with RMS on that front). Weaker phrasing doesn't > make the intent any better. > * Prominent links or funding
Bug#884658: dkms: Should really depends on dpkg-dev for dpkg-architecture
Hi, If I'm not mistaken, the aforementioned patch [1] that introduced the dpkg-architecture usage is also responsible for this debian dkms bug [2]. In the bug report for [2] there is a patch provided, but apparently this has not yet been fixed in stable or testing/sid. As a user, I'd be really grateful if these dkms bugs regarding among others mkdeb could be fixed (maybe even in stable). Thanks a lot! [1] https://sources.debian.org/src/dkms/2.6.1-1/debian/patches/0004-mkbmdeb-support-for-lean-binary-package-with-only-th.patch/ [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832558
Processed: severity of 907005 is important
Processing commands for cont...@bugs.debian.org: > severity 907005 important Bug #907005 [src:cssc] cssc FTBFS on 32bit big endian: FAIL auto.sh b4 input did not produce an encoded s-file. Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 907005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915450: staden-io-lib FTBFS on big endian: test failures
On Tue, Dec 04, 2018 at 06:12:26PM +, James Bonfield wrote: > On Tue, Dec 04, 2018 at 07:53:35AM +0100, Andreas Tille wrote: >... > I'm curious to know if you're getting the same issue on x86-64 and > i386, but the more recent automakes sadly hide all test output if it > works even with VERBOSE=1 on, grrr. >... This is fixable by going back to the serial test harness with AM_INIT_AUTOMAKE([serial-tests]) > > > ../progs/scramble ./data/c1#bounds.sam test.out/c1#bounds.sam > > > ../progs/scramble -r ./data/c1.fa ./data/c1#bounds.sam > > > test.out/c1#bounds.full.cram > > > ../progs/scramble ./data/c1#bounds.sam > test.out/tmp.sam > > > ../progs/scramble test.out/c1#bounds.full.cram > > > > test.out/c1#bounds.full.sam > > > ../progs/scramble -O bam test.out/c1#bounds.full.cram > > > > test.out/c1#bounds.full.bam > > > ../progs/scramble test.out/c1#bounds.full.bam test.out/tmp.sam > > > Invalid CRC in Deflate stream: 6614764d vs 6614 > > > Failed to open file test.out/c1#bounds.full.bam > > > FAIL scram.test (exit status: 1) > > This however appears to be a genuine bug. I'll try and reproduce it. > > I'm guessing I'll need the exact OS rather than the RedHat based AWS > image I launched last time to test non-intel platforms. > Do you have AWS-ified Debian ARM images for people test launch tests > against? Note that this error is on big endian, not on ARM. > James cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Processed: affects 915430
Processing commands for cont...@bugs.debian.org: > affects 915430 src:pytest-mpl Bug #915430 [src:matplotlib] matplotlib: autopkgtest regression: ImportError: No module named matplotlib Added indication that 915430 affects src:pytest-mpl > thanks Stopping processing here. Please contact me if you need assistance. -- 915430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 915112 to src:glew, fixed 915112 in 2.1.0-3
Processing commands for cont...@bugs.debian.org:
> reassign 915112 src:glew 2.1.0-2
Bug #915112 {Done: Alastair McKinstry } [src:pymol]
pymol: FTBFS with glew 2.1
Bug reassigned from package 'src:pymol' to 'src:glew'.
No longer marked as found in versions pymol/2.2.0+dfsg-1.
No longer marked as fixed in versions glew/2.1.0-3.
Bug #915112 {Done: Alastair McKinstry } [src:glew] pymol:
FTBFS with glew 2.1
Marked as found in versions glew/2.1.0-2.
> fixed 915112 2.1.0-3
Bug #915112 {Done: Alastair McKinstry } [src:glew] pymol:
FTBFS with glew 2.1
Marked as fixed in versions glew/2.1.0-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
915112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#915339: Bug #915339 in glibc marked as pending
Control: tag -1 pending Hello, Bug #915339 in glibc 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/glibc-team/glibc/commit/b691a908e1478754fc75964c19b7e609a8e24361 debian/control.in/libc: breaks r-cran-later (<< 0.7.5+dfsg-2), ie versions built with tinycthread. Closes: #915339. (this message was generated automatically) -- Greetings https://bugs.debian.org/915339
Processed: Bug #915339 in glibc marked as pending
Processing control commands: > tag -1 pending Bug #915339 [libc6] libc6 needs Conflicts with unfixed r-cran-later Added tag(s) pending. -- 915339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 915550
Processing commands for cont...@bugs.debian.org: > tags 915550 + buster sid Bug #915550 [libautodie-perl] libautodie-perl: superseded by perl Added tag(s) sid and buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 915550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915460: marked as done (staden-io-lib FTBFS on armel: scramble: cram_codecs.c:1441: cram_huffman_encode_init: Assertion `hi->data.i > 0' failed.)
Your message dated Tue, 04 Dec 2018 19:06:39 + with message-id and subject line Bug#915460: fixed in staden-io-lib 1.14.11-3 has caused the Debian Bug report #915460, regarding staden-io-lib FTBFS on armel: scramble: cram_codecs.c:1441: cram_huffman_encode_init: Assertion `hi->data.i > 0' failed. 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.) -- 915460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915460 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: staden-io-lib Version: 1.14.11-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=staden-io-lib=armel=1.14.11-2=1543747508=0 ... === testing ./data/xx#unsorted.sam === ./scram.test: 27: [: ./data/xx#unsorted.sam: unexpected operator ../progs/scramble -t4 ./data/xx#unsorted.sam test.out/xx#unsorted.sam ../progs/scramble -t4 -r ./data/xx.fa ./data/xx#unsorted.sam test.out/xx#unsorted.full.cram scramble: cram_codecs.c:1441: cram_huffman_encode_init: Assertion `hi->data.i > 0' failed. Aborted FAIL scram_mt.test (exit status: 1) Testsuite summary for io_lib 1.14.11 # TOTAL: 9 # PASS: 7 # SKIP: 0 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 See tests/test-suite.log make[4]: *** [Makefile:716: test-suite.log] Error 1 --- End Message --- --- Begin Message --- Source: staden-io-lib Source-Version: 1.14.11-3 We believe that the bug you reported is fixed in the latest version of staden-io-lib, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated staden-io-lib package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 04 Dec 2018 19:35:00 +0100 Source: staden-io-lib Binary: staden-io-lib-utils libstaden-read-dev libstaden-read13 staden-io-lib-examples Architecture: source Version: 1.14.11-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: libstaden-read-dev - development files for libstaden-read libstaden-read13 - Staden library for reading and writing DNA sequencing results staden-io-lib-examples - programs for manipulating DNA sequencing files (usage examples) staden-io-lib-utils - programs for manipulating DNA sequencing files Closes: 915460 Changes: staden-io-lib (1.14.11-3) unstable; urgency=medium . * Remove bashism in test script Closes: #915460 Checksums-Sha1: 043f13cff8aa6e4e8cf6fc132098e1a6f30c84ef 2432 staden-io-lib_1.14.11-3.dsc 1e61340708ccbde4a3f267a711015963ec69b98d 10508 staden-io-lib_1.14.11-3.debian.tar.xz bf4377e541bd71c7786238e1fc0aefe1d7798f66 7967 staden-io-lib_1.14.11-3_amd64.buildinfo Checksums-Sha256: 657181c596577b7eda6350defece699d55cf0a25770bb6dfae528960a4b84d8d 2432 staden-io-lib_1.14.11-3.dsc ed6076cbf6968656de2ac90b0fe5f97466427cab0c8a622b57fc4e7bb746a35b 10508 staden-io-lib_1.14.11-3.debian.tar.xz 198ada7584a8492d197a7add8e154060f9e823248dd3feb5948f574dc5375620 7967 staden-io-lib_1.14.11-3_amd64.buildinfo Files: a69c8350b342c4d17b07d17304bee943 2432 science optional staden-io-lib_1.14.11-3.dsc 75eec56869af93092ea72fd221939eab 10508 science optional staden-io-lib_1.14.11-3.debian.tar.xz 232fefbfe60c869d1332f2114e6c9cb2 7967 science optional staden-io-lib_1.14.11-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlwGyoARHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGcMQ/9FGJ+EcLxwPAaBcLBAB1/nOvvleJIn/Sg QikB7c+7tNl9ZqTPAmOy1/pxH7LXGt1ihyLvavYZ7IZR6g5PXwYlu11FSXLjdXiS Lmy4Ac9BKb1VSbjvWJPn9/O51KWcq1vLy4d1HjdYbPZgh0+mCjAiZGuIIWhUtMBD IkOvC3gBYglIs6UUXjAObttmktQEyA7QOBmIv7f/Q9CfIwy0SJBDJhspiTrD2arM YXvBxcNrq+EV8V2ugYqmxTL2LHsPXhphGIRHTr+yKKYxWKZcgQcFUPuQ+wMRMaMQ 7MgorjmjgB1AbKxsm1hGdUySd1kg4vjKJjwZ8XSRNIv46WrJ+rxzDcOJwST1CEzx
Bug#914897: debating the wrong thing
On Tue, Dec 04, 2018 at 07:21:11PM +0100, Adam Borowski wrote: > Your figure of ~80 packages counts only packages which went through a > reproducible-builds rebuild. We later learned only a part of the archive > got rebuilt since the bad debootstrap backport. wrong, sigh. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Bug#913608: marked as done (libncl FTBFS: symbol changes)
Your message dated Tue, 04 Dec 2018 18:35:59 + with message-id and subject line Bug#913608: fixed in libncl 2.1.21+git20180827.c71b264-1 has caused the Debian Bug report #913608, regarding libncl FTBFS: symbol changes 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.) -- 913608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913608 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libncl Version: 2.1.21+git20171002.4becff7-2 Severity: serious Tags: ftbfs Some recent change in unstable makes libncl FTBFS: https://tests.reproducible-builds.org/debian/history/libncl.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libncl.html ... @@ -1122,14 +1122,16 @@ _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base 2.1.18 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES5_St9_IdentityIS5_ESt4lessIS5_ESaIS5_EEaSERKSB_@Base 2.1.18 (optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE11equal_rangeERS7_@Base 2.1.21+git20171002.4becff7 - _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE16_M_insert_uniqueIS6_IS5_S8_EEES6_ISt17_Rb_tree_iteratorIS9_EbEOT_@Base 2.1.18 +#MISSING: 2.1.21+git20171002.4becff7-2# _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE16_M_insert_uniqueIS6_IS5_S8_EEES6_ISt17_Rb_tree_iteratorIS9_EbEOT_@Base 2.1.18 + _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE17_M_emplace_uniqueIJS6_IS5_S8_S6_ISt17_Rb_tree_iteratorIS9_EbEDpOT_@Base 2.1.21+git20171002.4becff7-2 (optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE4findERS7_@Base 2.1.21+git20171002.4becff7 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE5eraseERS7_@Base 2.1.18 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE7_M_copyINSF_20_Reuse_or_alloc_nodeEEEPSt13_Rb_tree_nodeIS9_EPKSJ_PSt18_Rb_tree_node_baseRT_@Base 2.1.18 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE8_M_eraseEPSt13_Rb_tree_nodeIS9_E@Base 2.1.18 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_16NxsIntStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EEaSERKSF_@Base 2.1.21+git20171002.4becff7 (optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE11equal_rangeERS7_@Base 2.1.21+git20171002.4becff7 - _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE16_M_insert_uniqueIS6_IS5_S8_EEES6_ISt17_Rb_tree_iteratorIS9_EbEOT_@Base 2.1.18 +#MISSING: 2.1.21+git20171002.4becff7-2# _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE16_M_insert_uniqueIS6_IS5_S8_EEES6_ISt17_Rb_tree_iteratorIS9_EbEOT_@Base 2.1.18 + _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE17_M_emplace_uniqueIJS6_IS5_S8_S6_ISt17_Rb_tree_iteratorIS9_EbEDpOT_@Base 2.1.21+git20171002.4becff7-2 (optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE4findERS7_@Base 2.1.21+git20171002.4becff7 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE5eraseERS7_@Base 2.1.18 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_17NxsRealStepMatrixESt10_Select1stIS9_ESt4lessIS5_ESaIS9_EE7_M_copyINSF_20_Reuse_or_alloc_nodeEEEPSt13_Rb_tree_nodeIS9_EPKSJ_PSt18_Rb_tree_node_baseRT_@Base 2.1.18 @@ -1214,7 +1216,7 @@ --- End Message --- --- Begin Message --- Source: libncl Source-Version: 2.1.21+git20180827.c71b264-1 We believe
Bug#915450: staden-io-lib FTBFS on big endian: test failures
On Tue, Dec 04, 2018 at 07:53:35AM +0100, Andreas Tille wrote: > unfortunately there is a series of new errors on different architectures. > Here comes the first one. Hmm. Some of this at least appears to be a Debian specific thing. > > === testing ./data/c1#bounds.sam === > > ./scram.test: 27: [: ./data/c1#bounds.sam: unexpected operator The [ .. unexpected operator normally comes about due to bashisms, like if [ "$a" == "$b" ] then (etc). However this line doesn't do that - it is a single equals (I *did* have a bashism there at one point, but not in 1.14.11). I've tested the test harness using both bash and dash and I do not get these errors. I'm struggling to work out how come it reports this and then continues regardless. It looks like the shell just has a warning and doesn't treat it as a hard error. I'm confused! I'm curious to know if you're getting the same issue on x86-64 and i386, but the more recent automakes sadly hide all test output if it works even with VERBOSE=1 on, grrr. (The only reason I stick with autotools is because cmake is even worse!) > > ../progs/scramble ./data/c1#bounds.sam test.out/c1#bounds.sam > > ../progs/scramble -r ./data/c1.fa ./data/c1#bounds.sam > > test.out/c1#bounds.full.cram > > ../progs/scramble ./data/c1#bounds.sam > test.out/tmp.sam > > ../progs/scramble test.out/c1#bounds.full.cram > > > test.out/c1#bounds.full.sam > > ../progs/scramble -O bam test.out/c1#bounds.full.cram > > > test.out/c1#bounds.full.bam > > ../progs/scramble test.out/c1#bounds.full.bam test.out/tmp.sam > > Invalid CRC in Deflate stream: 6614764d vs 6614 > > Failed to open file test.out/c1#bounds.full.bam > > FAIL scram.test (exit status: 1) This however appears to be a genuine bug. I'll try and reproduce it. I'm guessing I'll need the exact OS rather than the RedHat based AWS image I launched last time to test non-intel platforms. Do you have AWS-ified Debian ARM images for people test launch tests against? James -- James Bonfield (j...@sanger.ac.uk) The Sanger Institute, Hinxton, Cambs, CB10 1SA -- The Wellcome Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
Bug#914897: debating the wrong thing
On Tue, Dec 04, 2018 at 06:48:45PM +0100, Ansgar Burchardt wrote:
> Ian Jackson writes:
> > Ansgar Burchardt writes ("Bug#914897: debating the wrong thing"):
> >> Switching to (1) or (3a-with-no-support-in-buster) will mean merged-/usr
> >> systems would no longer be supported. In this case someone would have
> >> to write a unusrmerge program to convert systems with merged-/usr to
> >> systems with unmerged-/usr.
> >
> > Currently merged-usr is broken because it can build packages which do
> > not work on non-merged-usr systems.
>
> In very rare cases (an estimated 0.3% of the archive or so). I'm fairly
> confident that for more than 0.3% of the archive something can go wrong
> when building in non-clean environments.
Your figure of ~80 packages counts only packages which went through a
reproducible-builds rebuild. We later learned only a part of the archive
got rebuilt since the bad debootstrap backport.
> What is technically and socially wrong is reverting a change after a
> small issue was found which is already in the process of getting fixed
> for most packages.
Making packages with non-Debian origin randomly break is not a "small
issue". Remember, we can fix only packages we make ourselves -- not any of
private/PPA/company-wide packages so many of our users make.
> > When we have stopped generating more lossage, we can start to think
> > about whether we want to transition to usrmerge as default, whether to
> > make it mandatory, and if so how the transition should be handled, and
> > on what timescale.
>
> We had the discussion (usrmerge as default) already quite some time
> ago. Why start again at zero? As a random reference, the D-I Stretch
> RC 1 release announcement explicitly stated:
>
> +---
> | * The switch to merged-/usr as the default setting for debootstrap
> |was reverted since it uncovered a number of important issues which
> |might not be all fixed in time for stretch. This setting is
> |expected to come back as the default at the beginning of the next
> |release cycle.
> +---
>
> And just that happened (except a bit later).
Except that the change went live only on 2018-11-10, then waited until
buildds recreated their chroots, then until dinstall and mirror push...
and the sky started falling immediately after that.
We train DDs to not upload packages built in an unclean environment -- I
made ~1000 uploads (mostly sponsored) which did not include a _single_
unclean build. I expect most DDs to be alike, and most of us also do
source-only except to NEW.
We tend to build outside a chroot only during development. Of course we do
test those packages but almost always on the same machine we're sitting at.
Which happens to match the usrmerge status of the package being tested...
> You could have easily asked the tech-ctte back then (or even before)
> instead of waiting until shortly before the Buster freeze and after
> people invested more work.
It was only shortly before the Buster freeze that we saw this change in
action! Had the switch get flipped sooner we'd have a chance to see the
results. By now, it's much too late to fix things before the freeze
(and I don't see how they could be fixed even had we two years of time).
> There is no such crisis. There was also enough time to discuss this in
> the last years or even since June (when it was enabled by default
> again)...
Nope, it got enabled very recently. This is a case where religiously
building stuff in a clean environment bit us -- because _that_ environment
wasn't changed.
By now, all we can do is damage control. Which can be a hasty force-merge
or a hasty revert. Unless you can somehow make dpkg-dev omniscient.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Ivan was a worldly man: born in St. Petersburg, raised in
⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned
⠈⠳⣄ to the city of his birth to die.
Bug#915112: marked as done (pymol: FTBFS with glew 2.1)
Your message dated Tue, 04 Dec 2018 18:19:23 + with message-id and subject line Bug#915112: fixed in glew 2.1.0-3 has caused the Debian Bug report #915112, regarding pymol: FTBFS with glew 2.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 915112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glew Version: 2.1.0-2 Severity: serious Control: affects -1 + src:pymol Hi, I just noticed that pymol stated to FTBFS, this seems to be caused by glew (which was updated recently, while libglvnd hasn't seen changes for some time): In file included from layer0/os_gl.h:60, from layer1/Ortho.h:28, from layer0/Err.cpp:22: /usr/include/GL/glext.h:12066:105: error: conflicting declaration 'typedef void (* PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, const GLfloat*)' typedef void (APIENTRYP PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum pname, const GLfloat *params); ^ In file included from layer0/os_gl.h:58, from layer1/Ortho.h:28, from layer0/Err.cpp:22: /usr/include/GL/glew.h:18734:28: note: previous declaration as 'typedef void (* PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, GLfloat*)' typedef void (GLAPIENTRY * PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum pname, GLfloat* params); ^~~~ In file included from layer0/os_gl.h:60, from layer1/Ortho.h:28, from layer0/Err.cpp:22: /usr/include/GL/glext.h:12068:103: error: conflicting declaration 'typedef void (* PFNGLFRAGMENTLIGHTIVSGIXPROC)(GLenum, GLenum, const GLint*)' typedef void (APIENTRYP PFNGLFRAGMENTLIGHTIVSGIXPROC) (GLenum light, GLenum pname, const GLint *params); ^ In file included from layer0/os_gl.h:58, from layer1/Ortho.h:28, from layer0/Err.cpp:22: /usr/include/GL/glew.h:18736:28: note: previous declaration as 'typedef void (* PFNGLFRAGMENTLIGHTIVSGIXPROC)(GLenum, GLenum, GLint*)' typedef void (GLAPIENTRY * PFNGLFRAGMENTLIGHTIVSGIXPROC) (GLenum light, GLenum pname, GLint* params); ^~~~ and so on... Full log attached. This happens with both pymol in sid and experimental. Andreas pymol_2.2.0+dfsg-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: glew Source-Version: 2.1.0-3 We believe that the bug you reported is fixed in the latest version of glew, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated glew package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 04 Dec 2018 17:36:36 + Source: glew Binary: glew-utils libglew-dev libglew2.1 Architecture: source amd64 Version: 2.1.0-3 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: glew-utils - OpenGL Extension Wrangler - utilities libglew-dev - OpenGL Extension Wrangler - development environment libglew2.1 - OpenGL Extension Wrangler - runtime environment Closes: 915112 Changes: glew (2.1.0-3) unstable; urgency=medium . * Fix from repo for glext.h collision: Closes: #915112 Checksums-Sha1: acf48ee1c9f33002a4282bbe22f87f3e299f79fd 2004 glew_2.1.0-3.dsc 5b642ed75c75cb20c71d8ca2f7f29fafc9ca1241 27436 glew_2.1.0-3.debian.tar.xz 9dcb97881d79e57bc9642cbf4f381ae4d81e9350 332612 glew-utils-dbgsym_2.1.0-3_amd64.deb 23daaf6019d1d033060237d13c839dd35a2fc51f 100996 glew-utils_2.1.0-3_amd64.deb 1558f50a6fcd6b6875e0ab4964f6a212d4779783 9149 glew_2.1.0-3_amd64.buildinfo 961bdb4916fe2ca6adf53cab859c34725e78e262 140844 libglew-dev_2.1.0-3_amd64.deb 7e99b91e893295dd4f93040e83652d5fe3d6276a 277960 libglew2.1-dbgsym_2.1.0-3_amd64.deb
Bug#891633: aolserver4: Should this package be removed?
severity nn normal reassign nn ftp.debian.org retitle nn RM: aolserver4 -- RoQA; unmaintained upstream, alternatives exist, low popcon thanks > > So my question: Can we remove aolserver4 from the archive? > > debian/copyright points to http://aolserver.sf.net/ where the latest news > item is about it being copied to github in 2010. > https://github.com/aolserver/aolserver got its latest commit in 2009. > > This looks fairly dead to me, and unless its maintainer knows better, I > don't think there is going to be any upstream security support. > > It has also not been uploaded since an NMU that went into stretch, so > if it's removed from unstable, it will be trivial for prospective users > or maintainers to retrieve it from stretch. No objections were raised in almost a year, reassigning for removal now. Cheers, Moritz
Bug#828483: osslsigncode: FTBFS with openssl 1.1.0
On Tue, Jan 16, 2018 at 09:05:15PM +0100, Stephen Kitt wrote: > > I’ve been meaning to look into all this further, but help is welcome. This is unfixed for quite a while and the upstream homepage now mentions "This is now - and has been for a long while - abandonware". Shall we remove osslsigncode from the archive? Cheers, Moritz
Bug#828429: mailavenger: FTBFS with openssl 1.1.0
Sebastian Andrzej Siewior wrote: > Hi, > > this is a remainder about the openssl transition [0]. We really want to > remove libssl1.0-dev from unstable for Buster. I will raise the severity > of this bug to serious in a month. Please react before that happens. Ulises, this seems to be fixed in the 0.8.5 release, the NEWS file mentions "Various changes to make it compile with newer g++ and libcrypto". Can you please upload a fixed version? This blocks the removal of openssl1.0 from the archive. Cheers, Moritz
Bug#915550: libautodie-perl: superseded by perl
Package: libautodie-perl Version: 2.29-2 Severity: serious This is a separately packaged version of a module that is also bundled with Perl core. The last upstream release of autodie was over three years ago, despite the rather serious bug in it (#798096). I don't think there's any value in releasing buster with this as a separate package. -- Niko Tyni nt...@debian.org
Bug#914897: debating the wrong thing
Ian Jackson writes:
> Ansgar Burchardt writes ("Bug#914897: debating the wrong thing"):
>> Switching to (1) or (3a-with-no-support-in-buster) will mean merged-/usr
>> systems would no longer be supported. In this case someone would have
>> to write a unusrmerge program to convert systems with merged-/usr to
>> systems with unmerged-/usr.
>
> Currently merged-usr is broken because it can build packages which do
> not work on non-merged-usr systems.
In very rare cases (an estimated 0.3% of the archive or so). I'm fairly
confident that for more than 0.3% of the archive something can go wrong
when building in non-clean environments.
> It would be quite wrong (both technically and socially) to react to
> this lack of foresight,
The reported problems are not really unexpected...
> lack of consultation,
It was discussed on -devel@ several times. I think LWN also reported
about merged-/usr developments in Debian more than once, it wasn't a
secret cabal development.
So where is the lack of consultation?
> and lack of testing, by pressing forward.
It has been tested for quite a while.
A helpful new test was recently added by the Reproducible Builds project
which allowed to identify most problematic packages.
What is technically and socially wrong is reverting a change after a
small issue was found which is already in the process of getting fixed
for most packages.
> When we have stopped generating more lossage, we can start to think
> about whether we want to transition to usrmerge as default, whether to
> make it mandatory, and if so how the transition should be handled, and
> on what timescale.
We had the discussion (usrmerge as default) already quite some time
ago. Why start again at zero? As a random reference, the D-I Stretch
RC 1 release announcement explicitly stated:
+---
| * The switch to merged-/usr as the default setting for debootstrap
|was reverted since it uncovered a number of important issues which
|might not be all fixed in time for stretch. This setting is
|expected to come back as the default at the beginning of the next
|release cycle.
+---
And just that happened (except a bit later).
You could have easily asked the tech-ctte back then (or even before)
instead of waiting until shortly before the Buster freeze and after
people invested more work.
Making it mandatory or not is an unrelated decision. That can easily
just come later.
> We need the space to discuss those options properly without being
> distracted by what is IMO currently a crisis in stretch-backports and
> buster.
There is no such crisis. There was also enough time to discuss this in
the last years or even since June (when it was enabled by default
again)...
Ansgar
Bug#914897: debating the wrong thing
Ansgar Burchardt writes ("Bug#914897: debating the wrong thing"):
> Switching to (1) or (3a-with-no-support-in-buster) will mean merged-/usr
> systems would no longer be supported. In this case someone would have
> to write a unusrmerge program to convert systems with merged-/usr to
> systems with unmerged-/usr.
Currently merged-usr is broken because it can build packages which do
not work on non-merged-usr systems. It would be quite wrong (both
technically and socially) to react to this lack of foresight, lack of
consultation, and lack of testing, by pressing forward.
What I am suggesting in this bug report is that we revert to the
status quo before the default was changed to usrmerge, that is:
[Adam:]
>> 2. supporting both merged-usr and unmerged-usr
But actually of course "supporting" it in the way that it is currently
"supported" (according to usrmerge proponents) in stretch, sid, and
buster: if you enable it you may build packages which are not
generally useable (and perhaps you may experience other bugs).
This question is urgent for buster because the longer the current
situation continues the more systems there are that build broken
packages.
It is also urgent for stretch-backports. The backports maintainers
have said that they want to keep stretch-backports in line with
buster. Regardless of the wisdom of that policy, the current
situation in stretch-backports seems very bad to me.
The easiest way to fix stretch-backports (without also generating a
need to persuade the backports maintainers to waive their usual
policies) is to revert buster.
When we have stopped generating more lossage, we can start to think
about whether we want to transition to usrmerge as default, whether to
make it mandatory, and if so how the transition should be handled, and
on what timescale.
We have at least two sketches of transitions plans. That longer-term
conversation is a much more complicated one with many more options and
many more factors.
We need the space to discuss those options properly without being
distracted by what is IMO currently a crisis in stretch-backports and
buster.
Ian.
Bug#915506: marked as done (mathgl ftbfs on mips and mipsel)
Your message dated Tue, 04 Dec 2018 16:41:10 + with message-id and subject line Bug#915506: fixed in mathgl 2.4.2.1-5 has caused the Debian Bug report #915506, regarding mathgl ftbfs on mips and mipsel 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.) -- 915506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915506 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mathgl Version: 2.4.2.1-4 Severity: serious Tags: sid buster mathgl ftbfs on mips and mipsel: [ 99%] Linking CXX executable udav cd /<>/obj-mipsel-linux-gnu/udav && /usr/bin/cmake -E cmake_link_script CMakeFiles/udav.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -Wl,-z,relro -rdynamic CMakeFiles/udav.dir/anim_dlg.cpp.o CMakeFiles/udav.dir/find_dlg.cpp.o CMakeFiles/udav.dir/mem_pnl.cpp.o CMakeFiles/udav.dir/prop_dlg.cpp.o CMakeFiles/udav.dir/textedit.cpp.o CMakeFiles/udav.dir/args_dlg.cpp.o CMakeFiles/udav.dir/help_pnl.cpp.o CMakeFiles/udav.dir/newcmd_dlg.cpp.o CMakeFiles/udav.dir/text_pnl.cpp.o CMakeFiles/udav.dir/calc_dlg.cpp.o CMakeFiles/udav.dir/hint_dlg.cpp.o CMakeFiles/udav.dir/open_dlg.cpp.o CMakeFiles/udav.dir/qmglsyntax.cpp.o CMakeFiles/udav.dir/udav_wnd.cpp.o CMakeFiles/udav.dir/dat_pnl.cpp.o CMakeFiles/udav.dir/info_dlg.cpp.o CMakeFiles/udav.dir/opt_dlg.cpp.o CMakeFiles/udav.dir/setup_dlg.cpp.o CMakeFiles/udav.dir/files_dlg.cpp.o CMakeFiles/udav.dir/plot_pnl.cpp.o CMakeFiles/udav.dir/style_dlg.cpp.o CMakeFiles/udav.dir/data_dlg.cpp.o CMakeFiles/udav.dir/subplot_dlg.cpp.o CMakeFiles/udav.dir/qrc_udav.cpp.o CMakeFiles/udav.dir/udav_autogen/mocs_compilation.cpp.o -o udav -Wl,-rpath,/<>/obj-mipsel-linux-gnu/widgets/qt5:/<>/obj-mipsel-linux-gnu/src:/usr/lib/mipsel-linux-gnu/hdf5/serial: ../widgets/qt5/libmgl-qt5.so.7.5.0 /usr/lib/mipsel-linux-gnu/libQt5PrintSupport.so.5.11.2 /usr/lib/mipsel-linux-gnu/libQt5OpenGL.so.5.11.2 -pthread /usr/lib/mipsel-linux-gnu/libQt5Widgets.so.5.11.2 /usr/lib/mipsel-linux-gnu/libQt5Gui.so.5.11.2 /usr/lib/mipsel-linux-gnu/libQt5Core.so.5.11.2 ../src/libmgl.so.7.5.0 -lGL -lGLU -lgif -lhpdf -lpng -lz -ljpeg /usr/lib/mipsel-linux-gnu/hdf5/serial/libhdf5.so -lpthread -lsz -lz -ljpeg /usr/lib/mipsel-linux-gnu/hdf5/serial/libhdf5.so -lpthread -lsz -ldl -lm -lmfhdf -ldf -lltdl -lgsl -lgslcblas -pthread -lm make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' [ 99%] Built target udav as: out of memory allocating 4072 bytes after a total of 540606464 bytes /tmp/ccrtt2Iu.s: Assembler messages: /tmp/ccrtt2Iu.s: Fatal error: can't close CMakeFiles/mgl-oct.dir/CMakeFiles/mgl-oct.dir/mathglOCTAVE_wrap.cxx.o: memory exhausted make[3]: *** [lang/CMakeFiles/mgl-oct.dir/build.make:66: lang/CMakeFiles/mgl-oct.dir/CMakeFiles/mgl-oct.dir/mathglOCTAVE_wrap.cxx.o] Error 1 make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu' --- End Message --- --- Begin Message --- Source: mathgl Source-Version: 2.4.2.1-5 We believe that the bug you reported is fixed in the latest version of mathgl, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dimitrios Eftaxiopoulos (supplier of updated mathgl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 04 Dec 2018 17:58:19 +0200 Source: mathgl Binary: mathgl udav libmgl7.5.0 libmgl-mpi7.5.0 libmgl-wnd7.5.0 libmgl-glut7.5.0 libmgl-qt5-7.5.0 libmgl-fltk7.5.0 libmgl-wx7.5.0 libmgl-data libmgl-dev python-mathgl python3-mathgl Architecture: source all amd64 Version: 2.4.2.1-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Dimitrios Eftaxiopoulos Description: libmgl-data - library for scientific graphs (data files) libmgl-dev - library for scientific graphs (development files) libmgl-fltk7.5.0 - library for scientific graphs (fltk interface for windows) libmgl-glut7.5.0 - library for scientific graphs (glut interface for windows) libmgl-mpi7.5.0 - library for scientific graphs (mpi enhanced runtime library) libmgl-qt5-7.5.0 - library for
Processed: severity of 915488 is important, reassign 915488 to lvm2
Processing commands for cont...@bugs.debian.org: > severity 915488 important Bug #915488 [initramfs-tools-core] initramfs-tools-core: after dist-upgrade to testing my system can't boot, need to go to recovery then init 5 Severity set to 'important' from 'critical' > reassign 915488 lvm2 Bug #915488 [initramfs-tools-core] initramfs-tools-core: after dist-upgrade to testing my system can't boot, need to go to recovery then init 5 Bug reassigned from package 'initramfs-tools-core' to 'lvm2'. No longer marked as found in versions initramfs-tools/0.132. Ignoring request to alter fixed versions of bug #915488 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 915488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915488 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#888081: marked as done (resteasy FTBFS: org.jboss.resteasy.specimpl.ResponseBuilderImpl is not abstract and does not override abstract method status(int,java.lang.String) in javax.ws.rs.core.Respo
Your message dated Tue, 04 Dec 2018 16:13:40 + with message-id and subject line Bug#888081: fixed in resteasy 3.6.2-1 has caused the Debian Bug report #888081, regarding resteasy FTBFS: org.jboss.resteasy.specimpl.ResponseBuilderImpl is not abstract and does not override abstract method status(int,java.lang.String) in javax.ws.rs.core.Response.ResponseBuilder 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.) -- 888081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: resteasy Version: 3.1.4-1 Severity: serious Some recent change in unstable makes resteasy FTBFS: https://tests.reproducible-builds.org/debian/history/resteasy.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/resteasy.html ... [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /build/1st/resteasy-3.1.4/resteasy-jaxrs/src/main/java/org/jboss/resteasy/specimpl/ResponseBuilderImpl.java:[33,8] org.jboss.resteasy.specimpl.ResponseBuilderImpl is not abstract and does not override abstract method status(int,java.lang.String) in javax.ws.rs.core.Response.ResponseBuilder [INFO] 1 error [INFO] - [INFO] [INFO] Reactor Summary: [INFO] [INFO] RESTEasy JAX-RS SUCCESS [ 0.829 s] [INFO] RESTEasy JAX-RS services ... SUCCESS [ 3.216 s] [INFO] RESTEasy JAX-RS Implementation . FAILURE [ 18.799 s] [INFO] RESTEasy JAX-RS Client . SKIPPED [INFO] RESTEasy Legacy SKIPPED [INFO] RESTEasy JAXB Provider . SKIPPED [INFO] RESTEasy Jettison Provider . SKIPPED [INFO] RESTEasy Jackson Provider .. SKIPPED [INFO] RESTEasy Atom Provider . SKIPPED [INFO] RESTEasy YAML Provider . SKIPPED [INFO] RESTEasy HTML Provider . SKIPPED [INFO] RESTEasy Providers . SKIPPED [INFO] RESTEasy dependencies BOM .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 24.905 s [INFO] Finished at: 2019-02-24T23:11:10-12:00 [INFO] Final Memory: 20M/606M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile) on project resteasy-jaxrs: Compilation failure [ERROR] /build/1st/resteasy-3.1.4/resteasy-jaxrs/src/main/java/org/jboss/resteasy/specimpl/ResponseBuilderImpl.java:[33,8] org.jboss.resteasy.specimpl.ResponseBuilderImpl is not abstract and does not override abstract method status(int,java.lang.String) in javax.ws.rs.core.Response.ResponseBuilder [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :resteasy-jaxrs dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/build/1st/resteasy-3.1.4 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/build/1st/resteasy-3.1.4/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/resteasy-3.1.4/debian -Dmaven.repo.local=/build/1st/resteasy-3.1.4/debian/maven-repo --batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 debian/rules:4: recipe for target 'build' failed make: *** [build] Error 2 --- End Message --- --- Begin Message --- Source: resteasy Source-Version: 3.6.2-1 We believe that the bug you reported is fixed in the latest version of resteasy, which is due to be
Bug#912395: marked as done (resteasy3.0: FTBFS with Java 11 due to JAXB removal)
Your message dated Tue, 04 Dec 2018 16:13:51 + with message-id and subject line Bug#912395: fixed in resteasy3.0 3.0.19-5 has caused the Debian Bug report #912395, regarding resteasy3.0: FTBFS with Java 11 due to JAXB 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.) -- 912395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: resteasy3.0 Version: 3.0.19-4 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/resteasy3.0.html ... [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 6.774 s [INFO] Finished at: 2018-10-30T15:41:01-12:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project resteasy-jaxrs: Compilation failure: Compilation failure: [ERROR] /build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/api/validation/ResteasyConstraintViolation.java:[5,33] package javax.xml.bind.annotation does not exist [ERROR] /build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/api/validation/ResteasyConstraintViolation.java:[6,33] package javax.xml.bind.annotation does not exist [ERROR] /build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/api/validation/ResteasyConstraintViolation.java:[7,33] package javax.xml.bind.annotation does not exist [ERROR] /build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/api/validation/ResteasyConstraintViolation.java:[16,2] cannot find symbol [ERROR] symbol: class XmlRootElement [ERROR] /build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/api/validation/ResteasyConstraintViolation.java:[17,2] cannot find symbol [ERROR] symbol: class XmlAccessorType [ERROR] /build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[25,24] package javax.activation does not exist [ERROR] /build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[40,64] cannot find symbol [ERROR] symbol: class DataSource [ERROR] /build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[105,18] cannot find symbol [ERROR] symbol: class DataSource [ERROR] location: class org.jboss.resteasy.plugins.providers.DataSourceProvider [ERROR] /build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[170,37] cannot find symbol [ERROR] symbol: class DataSource [ERROR] location: class org.jboss.resteasy.plugins.providers.DataSourceProvider [ERROR] /build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[170,11] cannot find symbol [ERROR] symbol: class DataSource [ERROR] location: class org.jboss.resteasy.plugins.providers.DataSourceProvider [ERROR] /build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[212,24] cannot find symbol [ERROR] symbol: class DataSource [ERROR] location: class org.jboss.resteasy.plugins.providers.DataSourceProvider [ERROR] /build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/plugins/providers/DataSourceProvider.java:[43,58] cannot find symbol [ERROR] symbol: class DataSource [ERROR] location: class org.jboss.resteasy.plugins.providers.DataSourceProvider [ERROR] /build/1st/resteasy3.0-3.0.19/jaxrs/resteasy-jaxrs/src/main/java/org/jboss/resteasy/api/validation/ResteasyConstraintViolation.java:[17,18] cannot find symbol [ERROR] symbol: variable XmlAccessType [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command
Bug#915321: marked as done (r-cran-later FTBFS on armel/mips/mipsel)
Your message dated Tue, 04 Dec 2018 16:13:28 + with message-id and subject line Bug#915321: fixed in r-cran-later 0.7.5+dfsg-2 has caused the Debian Bug report #915321, regarding r-cran-later FTBFS on armel/mips/mipsel 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.) -- 915321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libc6 Version: 2.28-1 Severity: critical Just after updating libc6 from 2.27-8 to 2.28-1 in Debian Unstable, loading package "httpuv" in R leads to a crash: bones@equinox2:~$ R R version 3.5.1 (2018-07-02) -- "Feather Spray" Copyright (C) 2018 The R Foundation for Statistical Computing Platform: x86_64-pc-linux-gnu (64-bit) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type 'license()' or 'licence()' for distribution details. R is a collaborative project with many contributors. Type 'contributors()' for more information and 'citation()' on how to cite R or R packages in publications. Type 'demo()' for some demos, 'help()' for on-line help, or 'help.start()' for an HTML browser interface to help. Type 'q()' to quit R. > library(httpuv) terminate called after throwing an instance of 'std::runtime_error' what(): Mutex creation failed Ακυρώθηκε bones@equinox2:~$ From the message I understand this is directly related to libc6 and not R or httpuv. Also, there was no update to R or httpuv done recently. The problem started just as I updated libc6. Kernel version is 4.18.0-3-amd64. Please tell me if any other information is needed to help identify the bug. --- End Message --- --- Begin Message --- Source: r-cran-later Source-Version: 0.7.5+dfsg-2 We believe that the bug you reported is fixed in the latest version of r-cran-later, 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 915...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated r-cran-later package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 04 Dec 2018 16:09:02 +0100 Source: r-cran-later Binary: r-cran-later Architecture: source Version: 0.7.5+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Description: r-cran-later - GNU R utilities for delaying function execution Closes: 915321 Changes: r-cran-later (0.7.5+dfsg-2) unstable; urgency=medium . [ Adrian Bunk ] * Link with libboost_atomic when needed Closes: #915321 . [ Andreas Tille ] * Remove trailing whitespace in debian/copyright * Build-Depends: libboost-atomic-dev Checksums-Sha1: ca000d6a9f1b5e7c80cd049cb6c513e392ba9611 2141 r-cran-later_0.7.5+dfsg-2.dsc fbc5b8736038887bf3df5641f001cfbf55473e3e 2944 r-cran-later_0.7.5+dfsg-2.debian.tar.xz Checksums-Sha256: 9b5298bdeaaeabcc4cfb994501c082e18fcbb76fd13af29428f5d4c8a9967e7b 2141 r-cran-later_0.7.5+dfsg-2.dsc aa33d8fd3fbb60c27ca1392d867950e9e0807c66a6162478932d1d3584f04e37 2944 r-cran-later_0.7.5+dfsg-2.debian.tar.xz Files: 8eee2aa01a8bdf4ca3c8113dca389314 2141 gnu-r optional r-cran-later_0.7.5+dfsg-2.dsc 75792294a6d7d992b965a6fc1fd7e59d 2944 gnu-r optional r-cran-later_0.7.5+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlwGmisRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGudA//QWJ4OCCGum0m71IjZt6dxo8zwDB9Ehrd ZnTeUlnIaMDtpgOEd3xfJwoqcObsGVoB2D8aZZpIcrl5QT0J5QJVz3hfCueQN93Z V/KsnH+3IQkhiimHeDU4DHvsgO8Z/miK/fCbrIpMDzQlzliAVynB7aNS3nSljikW 7ziukkkEgevX9lo0efKeaukx2cGUme/DpcSs4Gbrv8VVRHJ6iM/QYm1wRs7017qi AgPgpKp4cz5OI+zzgwuXi/8OjLz25lvkAFgQUyRPUef5KFME42TZZGZobZE2yx2O gS9XEF1s9O0I3sDTOPlBwhGp9TZllg3raRTwyTVJ1KNvL+aENyixBVCSs4fOyFQw L03cvaKEQ7WWLjrD2QL8t2Op7qD+myFr29Y5+xWY3qQekPdJWbtmorey/d9kBOiI r36sqlvd62CodQb2bD2JpCywmS+v8dFOlAEi/jfCNQM6ivJXcRg2NigZHk57gIqc INhz4t/v006Nrnjg7s8pupHIOgzs44munJt0Djxgqh3B6Ecx7O1rGyVYiFe/wTOY 7LuHN4VXRI5rnrpQj0jBwMVTQpfzhFBfBmtUZ6G0lB/yXIZptXueBEmnSm5fAtvO
Processed: your mail
Processing commands for cont...@bugs.debian.org: > fixed 888386 3.4.4+dfsg-1~exp1 Bug #888386 [src:opencv] opencv: FTBFS with FFmpeg 4.0 Marked as fixed in versions opencv/3.4.4+dfsg-1~exp1. > close 888386 Bug #888386 [src:opencv] opencv: FTBFS with FFmpeg 4.0 Marked Bug as done > -- Stopping processing here. Please contact me if you need assistance. -- 888386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 914752 in 3.3.0+dfsg-1~exp0
Processing commands for cont...@bugs.debian.org:
> fixed 914752 3.3.0+dfsg-1~exp0
Bug #914752 {Done: Mattia Rizzolo } [src:opencv] opencv:
FTBFS against python3.7.1: error: invalid conversion from 'const char*' to
'char*' [-fpermissive]
Bug #914653 {Done: Mattia Rizzolo } [src:opencv] opencv:
FTBFS against python3.7.1: error: invalid conversion from 'const char*' to
'char*' [-fpermissive]
Marked as fixed in versions opencv/3.3.0+dfsg-1~exp0.
Marked as fixed in versions opencv/3.3.0+dfsg-1~exp0.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
914653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914653
914752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#915321: Mutex creation failed
On Tue, Dec 04, 2018 at 05:22:41PM +0200, Adrian Bunk wrote: > On Tue, Dec 04, 2018 at 04:10:09PM +0100, Andreas Tille wrote: > > On Tue, Dec 04, 2018 at 04:15:54PM +0200, Adrian Bunk wrote: > > > sorry for that, now attached. > > > > No need to sorry. > > > > I guess this patch needs an explicit > > > >Build-Depends: libboost-atomic-dev > > > > (otherwise I get a build error on amd64). > > Again a need to be sorry... Again no need to. ;-) > I saw the libboost-dev in the build dependencies, and mistook > it for libboost-all-dev (and libboost-atomic-dev was already > in my chroots making it not fail for me). > > So yes you are right, thanks for catching this. This was easy to catch. ;-) Thanks for all your QA work which is really appreciated. I have total understanding if in all your work minor glitches might remain open. Kind regards Andreas. -- http://fam-tille.de
Processed: found 905674 in 20161222-1, found 905674 in 20130922-1
Processing commands for cont...@bugs.debian.org:
> found 905674 20161222-1
Bug #905674 {Done: Didier Raboud } [parallel] parallel: move
to nonfree
Marked as found in versions parallel/20161222-1.
> found 905674 20130922-1
Bug #905674 {Done: Didier Raboud } [parallel] parallel: move
to nonfree
Marked as found in versions parallel/20130922-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
905674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#915540: openjdk-8-jre-dcevm should likely not be in buster
Le 04/12/2018 à 16:06, Adrian Bunk a écrit : > With OpenJDK 8 not supported in Debian this version is > likely not suitable for buster. > > The OpenJDK 11 version seems to be at > https://github.com/HotswapProjects/openjdk-jdk11u There is no harm keeping openjdk-8-jre-dcevm in Buster though. I take this more as a RFP for the JDK 11 version.
Bug#915321: Mutex creation failed
On Tue, Dec 04, 2018 at 04:10:09PM +0100, Andreas Tille wrote: > On Tue, Dec 04, 2018 at 04:15:54PM +0200, Adrian Bunk wrote: > > sorry for that, now attached. > > No need to sorry. > > I guess this patch needs an explicit > >Build-Depends: libboost-atomic-dev > > (otherwise I get a build error on amd64). Again a need to be sorry... I saw the libboost-dev in the build dependencies, and mistook it for libboost-all-dev (and libboost-atomic-dev was already in my chroots making it not fail for me). So yes you are right, thanks for catching this. > Kind regards > >Andreas. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#905674: GNU Parallel patch
Control: clone -1 -2 Control: retitle -2 parallel 20161222-1.1 NMU removes upstream "--will-cite" functionality Control: reopen -2 Control: notfound -2 20161222 Control: found -2 20161222-1.1 Control: severity -2 important Dear Ole, Le lundi, 3 décembre 2018, 18.55:00 h CET Ole Tange a écrit : > I have noticed that you have submitted a patch and closed this bug: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905674#77 > > I am sure you are trying to do what is best for free software. But > what looks like a good idea in the short run, may be a bad idea in the > long run. The long term survival of Debian depends on others building > free software that can be packaged, so destroying these people's > livelihood is a bad long term strategy. > > In the reasoning for the patch you state: > > Quoting the gpl-faq: > [... https://www.gnu.org/licenses/gpl-faq.en.html#RequireCitation ...] > > > Therefore, removing this to make parallel GPL-compliant. > > I think this is due to a misunderstanding. > > Maybe you not aware that Richard M. Stallman together with the GNU > leaders have cleared the wording and the use of the citation notice, > and that he sees it as complying fully with GPLv3? I was not, but, as Debian Developer, I don't feel bound by RMS' (and "GNU leaders", whomever this designates) statements about GPLv3. What mattered for this now-closed bugreport is our DFSG; specifically it's article 1 (emphasis mine) and 5. > DFSG 1: Free Redistribution > The license of a Debian component may not restrict any party from selling or > giving away the software as a component of an aggregate software > distribution containing programs from several different sources. The license > *may not require a royalty or other fee* for such sale. > DFSG 5: No Discrimination Against Persons or Groups > The license must not discriminate against any person or group of persons. Le lundi, 3 décembre 2018, 18.55:00 h CET Ole Tange a écrit : > Your patch therefore does not change the GPLv3-compliancy: The code > was already compliant. I disagree; my understanding is that RMS declared parallel to carry no problem with regards to GPLv3 compliance in October 2018, probably for the latest upstream release. But Debian ships parallel 20161222 which: * contains a request for the user to promise academic citation, * imposes the use of either "--will-cite" or the presence of a `~.parallel/will-cite`, which makes it unnecessarily burdensome to use in a scripted manner. This is a clear attempt at side-stepping GPLv3 software freedoms by using guilt-inducting language. As the GPLv3 allows (almost any) modification, I've just went and did that, also to ensure that src:parallel can stay in the Debian main archive, where it belongs. > But what your patch *does* do, is to make it harder to earn a living > from developing GNU Parallel and will make it much harder for me to > justify spending time maintaining GNU Parallel. Be careful with such arguments: by merely distributing GNU parallel in its main archive, Debian is also vastly expanding the availability of GNU parallel. And if you do insist on getting Debian to rename it, you'll likely lose any incentive from "renamed GNU parallel" users getting it from the Debian archive. > As Nadia Eghbal puts it in > https://www.slideshare.net/NadiaEghbal/consider-the-maintainer: > > "Is it alright to compromise, or even deliberately ignore, the > happiness of maintainers so we that can enjoy free and open source > software?" > > This describes very well what you are doing with the patch, and I > refuse to think that was your goal. For the record: * My primary goal was to remove a "Release Critical" bug from Debian's next stable release, during a Bug Squashing Party; * While looking at this bug, it seemed obvious to me that merely removing the obnoxious phrasing and functionality was an easy way to fix this bug; in a GPLv3- and DFSG-compatible way. * I am not the Debian maintainer of src:parallel, so my contribution was one- -off. * I did a Non-Maintainer Upload immediately, following DevRef 5.11.1: https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#nmu-guidelines * I do think that making fine free software unnecessarily cumbersome to use, only to increase user's knowledge of the original author's funding initiatives is bad practice. This reduces the quality of software and is really on the line of what makes software really "free software" (I'm fine to disagree with RMS on that front). Weaker phrasing doesn't make the intent any better. * Prominent links or funding pitches are fine in _documentation_, as long as they: - don't imply that payment is mandatory; - don't impose citation; For instance, parallel 20161222 manpage's > If you pay 1 EUR you should feel free to use GNU Parallel without citing. … is not acceptable IMHO. * I am not a Debian FTP-master, in charge of specific interpretations of the DFSG. > So if you
Bug#915321: Mutex creation failed
On Tue, Dec 04, 2018 at 04:15:54PM +0200, Adrian Bunk wrote: > sorry for that, now attached. No need to sorry. I guess this patch needs an explicit Build-Depends: libboost-atomic-dev (otherwise I get a build error on amd64). Kind regards Andreas. -- http://fam-tille.de
Processed: Re: GNU Parallel patch
Processing control commands:
> clone -1 -2
Bug #905674 {Done: Didier Raboud } [parallel] parallel: move
to nonfree
Bug 905674 cloned as bug 915541
> retitle -2 parallel 20161222-1.1 NMU removes upstream "--will-cite"
> functionality
Bug #915541 {Done: Didier Raboud } [parallel] parallel: move
to nonfree
Changed Bug title to 'parallel 20161222-1.1 NMU removes upstream "--will-cite"
functionality' from 'parallel: move to nonfree'.
> reopen -2
Bug #915541 {Done: Didier Raboud } [parallel] parallel
20161222-1.1 NMU removes upstream "--will-cite" functionality
'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 parallel/20161222-1.1.
> notfound -2 20161222
Bug #915541 [parallel] parallel 20161222-1.1 NMU removes upstream "--will-cite"
functionality
There is no source info for the package 'parallel' at version '20161222' with
architecture ''
Unable to make a source version for version '20161222'
Ignoring request to alter found versions of bug #915541 to the same values
previously set
> found -2 20161222-1.1
Bug #915541 [parallel] parallel 20161222-1.1 NMU removes upstream "--will-cite"
functionality
Marked as found in versions parallel/20161222-1.1.
> severity -2 important
Bug #915541 [parallel] parallel 20161222-1.1 NMU removes upstream "--will-cite"
functionality
Severity set to 'important' from 'serious'
--
905674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905674
915541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#915540: openjdk-8-jre-dcevm should likely not be in buster
Source: openjdk-8-jre-dcevm Version: 8u181-1 Severity: serious With OpenJDK 8 not supported in Debian this version is likely not suitable for buster. The OpenJDK 11 version seems to be at https://github.com/HotswapProjects/openjdk-jdk11u
Bug#915321: Mutex creation failed
On Tue, Dec 04, 2018 at 02:43:31PM +0100, Andreas Tille wrote: > Hi Adrian, Hi Andreas, > any NMU / team upload is fine. I'd do the upload myself but there is no > patch attached. sorry for that, now attached. > Kind regards > >Andreas. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed Description: Link with libboost_atomic when needed Needed on armel/mips/mipsel/m68k/powerpc/powerpcspe. Author: Adrian Bunk --- r-cran-later-0.7.5+dfsg.orig/src/Makevars.in +++ r-cran-later-0.7.5+dfsg/src/Makevars.in @@ -1,5 +1,5 @@ PKG_CPPFLAGS = -pthread @cppflags@ -PKG_LIBS = -pthread @libs@ +PKG_LIBS = -pthread -Wl,--as-needed -lboost_atomic -Wl,--no-as-needed @libs@ # Uncomment to enable thread assertions # PKG_CPPFLAGS += -DDEBUG_THREAD -UNDEBUG
Bug#915532: marked as done (python3-astrometry package post-installation script subprocess returned error exit status 1)
Your message dated Tue, 4 Dec 2018 15:15:29 +0100 with message-id <98d59e1e-0515-9697-a711-aa1344280...@debian.org> and subject line Already fixed with the last upload has caused the Debian Bug report #915532, regarding python3-astrometry package post-installation script subprocess returned error exit status 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 915532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-astrometry Version: 0.76+dfsg-2 Severity: grave Justification: renders package unusable Dear Maintainer, I am unable to install the python3-astrometry package. Here is what happens: Paramétrage de python3-astrometry (0.76+dfsg-2) ... File "/usr/lib/python3/dist-packages/astrometry/util/EXIF.py", line 1183 y = 0L ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/astrometry/util/EXIF.py", line 1183 y = 0L ^ SyntaxError: invalid syntax dpkg: erreur de traitement du paquet python3-astrometry (--configure) : installed python3-astrometry package post-installation script subprocess returned error exit status 1 dpkg: des problèmes de dépendances empêchent la configuration de astrometry.net : astrometry.net dépend de python3-astrometry ; cependant : Le paquet python3-astrometry n'est pas encore configuré. dpkg: erreur de traitement du paquet astrometry.net (--configure) : problèmes de dépendances - laissé non configuré Des erreurs ont été rencontrées pendant l'exécution : python3-astrometry astrometry.net Regards, Christophe Roland -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-astrometry depends on: ii file1:5.34-2 ii libastrometry0 0.76+dfsg-2 ii libc6 2.28-1 ii libcairo2 1.16.0-1 ii libgsl232.5+dfsg-6 ii libgslcblas02.5+dfsg-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libnetpbm10 2:10.0-15.3+b2 ii libpng16-16 1.6.34-2 ii libwcs6 6.2-1 ii python3 3.7.1-2 ii python3-astropy 3.0.5-1 ii python3-numpy [python3-numpy-abi9] 1:1.15.4-2 ii zlib1g 1:1.2.11.dfsg-1 python3-astrometry recommends no packages. python3-astrometry suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: python3-astrometry Source-Version: 0.76+dfsg-3 This is already fixed in the upload that was accepted a few hours ago. Cheers Ole--- End Message ---
Bug#915532: python3-astrometry package post-installation script subprocess returned error exit status 1
Package: python3-astrometry Version: 0.76+dfsg-2 Severity: grave Justification: renders package unusable Dear Maintainer, I am unable to install the python3-astrometry package. Here is what happens: Paramétrage de python3-astrometry (0.76+dfsg-2) ... File "/usr/lib/python3/dist-packages/astrometry/util/EXIF.py", line 1183 y = 0L ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/astrometry/util/EXIF.py", line 1183 y = 0L ^ SyntaxError: invalid syntax dpkg: erreur de traitement du paquet python3-astrometry (--configure) : installed python3-astrometry package post-installation script subprocess returned error exit status 1 dpkg: des problèmes de dépendances empêchent la configuration de astrometry.net : astrometry.net dépend de python3-astrometry ; cependant : Le paquet python3-astrometry n'est pas encore configuré. dpkg: erreur de traitement du paquet astrometry.net (--configure) : problèmes de dépendances - laissé non configuré Des erreurs ont été rencontrées pendant l'exécution : python3-astrometry astrometry.net Regards, Christophe Roland -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-astrometry depends on: ii file1:5.34-2 ii libastrometry0 0.76+dfsg-2 ii libc6 2.28-1 ii libcairo2 1.16.0-1 ii libgsl232.5+dfsg-6 ii libgslcblas02.5+dfsg-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libnetpbm10 2:10.0-15.3+b2 ii libpng16-16 1.6.34-2 ii libwcs6 6.2-1 ii python3 3.7.1-2 ii python3-astropy 3.0.5-1 ii python3-numpy [python3-numpy-abi9] 1:1.15.4-2 ii zlib1g 1:1.2.11.dfsg-1 python3-astrometry recommends no packages. python3-astrometry suggests no packages. -- no debconf information
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> retitle 907518 openssl 1.1.1~~pre9-1 breaks connection to some wifi networks,
> such as eduroam
Bug #907518 {Done: Mattia Rizzolo } [wpasupplicant] openssl
1.1.1~~pre9-1 breaks connection to some wifi
Changed Bug title to 'openssl 1.1.1~~pre9-1 breaks connection to some wifi
networks, such as eduroam' from 'openssl 1.1.1~~pre9-1 breaks connection to
some wifi'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
907518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org:
> retitle 907518 openssl 1.1.1~~pre9-1 breaks connection to some wifi
Bug #907518 {Done: Mattia Rizzolo } [wpasupplicant] New
libssl1.1 1.1.1~~pre9-1 in unstable breaks connecting to some wifi networks
Changed Bug title to 'openssl 1.1.1~~pre9-1 breaks connection to some wifi'
from 'New libssl1.1 1.1.1~~pre9-1 in unstable breaks connecting to some wifi
networks'.
> networks, such as eduroam
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
907518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#915321: Mutex creation failed
Hi Adrian, any NMU / team upload is fine. I'd do the upload myself but there is no patch attached. Kind regards Andreas. On Mon, Dec 03, 2018 at 09:51:28PM +0200, Adrian Bunk wrote: > Control: retitle -1 r-cran-later FTBFS on armel/mips/mipsel > Control: affects -1 = > Control: notforwarded -1 > Control: tags -1 patch > > On Mon, Dec 03, 2018 at 12:21:41AM +0100, Aurelien Jarno wrote: > >... > > While the pointer to the bug is correct, I am not sure we need to > > reassign the bug there. Nothing has to be changed in r-cran-later, it > > just has to be binNMued against glibc 2.28. OTOH, we need to add a Break > > on the glibc side. > > Oh, I wasn't aware of that a binNMU would be sufficient here. > > But that won't solve the problem due to the FTBFS on armel/mips/mipsel, > a source upload is anyway required with somethng like the attached patch. -- http://fam-tille.de
Processed: fixed 913601 in 12.2.8+dfsg1-5
Processing commands for cont...@bugs.debian.org: > fixed 913601 12.2.8+dfsg1-5 Bug #913601 [src:ceph] ceph: FTBFS on mips/el: /usr/include/c++/8/bits/atomic_base.h:304: undefined reference to `__atomic_fetch_sub_8' Marked as fixed in versions ceph/12.2.8+dfsg1-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 913601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): reassigning from src:chromium-browser to src:chromium
Processing commands for cont...@bugs.debian.org: > reassign 787527 src:chromium Bug #787527 [chromium-browser] Some sources are not included in your package Bug reassigned from package 'chromium-browser' to 'src:chromium'. No longer marked as found in versions 43.0.2357.65-1 and 47.0.2526.80-1~deb8u1. Ignoring request to alter fixed versions of bug #787527 to the same values previously set > found 787527 43.0.2357.65-1 Bug #787527 [src:chromium] Some sources are not included in your package The source 'chromium' and version '43.0.2357.65-1' do not appear to match any binary packages Marked as found in versions chromium/43.0.2357.65-1. > fount 787527 47.0.2526.80-1~deb8u1 Unknown command or malformed arguments to command. > reassign 669352 src:chromium Bug #669352 [chromium-browser] Please depend on libleveldb-dev and drop convenience copy of leveldb Bug reassigned from package 'chromium-browser' to 'src:chromium'. Ignoring request to alter found versions of bug #669352 to the same values previously set Ignoring request to alter fixed versions of bug #669352 to the same values previously set > reassign 814552 src:chromium Bug #814552 [chromium-browser] chromium-browser: use system hunspell Bug reassigned from package 'chromium-browser' to 'src:chromium'. No longer marked as found in versions 48.0.2564.82-0ubuntu0.14.04.1.1108. Ignoring request to alter fixed versions of bug #814552 to the same values previously set > reassign 893159 src:chromium 65.0.3325.146-4 Bug #893159 [src:chromium-browser] src:chromium-browser: Please ship an Architecture: all hstspreload package Bug reassigned from package 'src:chromium-browser' to 'src:chromium'. No longer marked as found in versions chromium-browser/65.0.3325.146-4. Ignoring request to alter fixed versions of bug #893159 to the same values previously set Bug #893159 [src:chromium] src:chromium-browser: Please ship an Architecture: all hstspreload package The source 'chromium' and version '65.0.3325.146-4' do not appear to match any binary packages Marked as found in versions chromium/65.0.3325.146-4. > reassign 893448 src:chromium 65.0.3325.146-4 Bug #893448 [src:chromium-browser] please add a chromium-source binary package Bug reassigned from package 'src:chromium-browser' to 'src:chromium'. No longer marked as found in versions chromium-browser/65.0.3325.146-4. Ignoring request to alter fixed versions of bug #893448 to the same values previously set Bug #893448 [src:chromium] please add a chromium-source binary package The source 'chromium' and version '65.0.3325.146-4' do not appear to match any binary packages Marked as found in versions chromium/65.0.3325.146-4. > reassign 580622 src:chromium 5.0.375.29~r46008-1 Bug #580622 [chromium-browser] chromium: lcdfilter in fontconfig is not honored Bug reassigned from package 'chromium-browser' to 'src:chromium'. No longer marked as found in versions chromium-browser/5.0.375.29~r46008-3 and chromium-browser/5.0.375.29~r46008-1. Ignoring request to alter fixed versions of bug #580622 to the same values previously set Bug #580622 [src:chromium] chromium: lcdfilter in fontconfig is not honored The source 'chromium' and version '5.0.375.29~r46008-1' do not appear to match any binary packages Marked as found in versions chromium/5.0.375.29~r46008-1. > reassign 587398 src:chromium 5.0.375.86~r49890-3 Bug #587398 [chromium-browser] chromium-browser: check DISPLAY envvar Bug #596357 [chromium-browser] chromium-browser: Still fails to honour $DISPLAY properly. Bug #735527 [chromium-browser] ignores $DISPLAY on creating new windows Bug reassigned from package 'chromium-browser' to 'src:chromium'. Bug reassigned from package 'chromium-browser' to 'src:chromium'. Bug reassigned from package 'chromium-browser' to 'src:chromium'. No longer marked as found in versions chromium-browser/31.0.1650.63-1~deb7u1, chromium-browser/5.0.375.86~r49890-3, and chromium-browser/6.0.472.53~r57914-3. No longer marked as found in versions chromium-browser/31.0.1650.63-1~deb7u1, chromium-browser/5.0.375.86~r49890-3, and chromium-browser/6.0.472.53~r57914-3. No longer marked as found in versions chromium-browser/5.0.375.86~r49890-3, chromium-browser/31.0.1650.63-1~deb7u1, and chromium-browser/6.0.472.53~r57914-3. Ignoring request to alter fixed versions of bug #587398 to the same values previously set Ignoring request to alter fixed versions of bug #596357 to the same values previously set Ignoring request to alter fixed versions of bug #735527 to the same values previously set Bug #587398 [src:chromium] chromium-browser: check DISPLAY envvar Bug #596357 [src:chromium] chromium-browser: Still fails to honour $DISPLAY properly. Bug #735527 [src:chromium] ignores $DISPLAY on creating new windows The source 'chromium' and version '5.0.375.86~r49890-3' do not appear to match any binary packages Marked as found in versions chromium/5.0.375.86~r49890-3. Marked as found in versions chromium/5.0.375.86~r49890-3. Marked as found in
Bug#842428: marked as done (debsecan: error 403 forbidden since 10/27/2016)
Your message dated Tue, 4 Dec 2018 14:40:19 +0200 with message-id <20181204124019.rkh3tcxc2xpwp...@tunkki.bugs.fi> and subject line old issue has caused the Debian Bug report #842428, regarding debsecan: error 403 forbidden since 10/27/2016 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.) -- 842428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842428 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debsecan Version: 0.4.16+nmu1 Severity: grave Justification: renders package unusable Dear Maintainer, I get these error reports in my incoming email: error: while downloading http://secure-testing.debian.net/debian-secure-testing/project/debsecan/release/1/wheezy: HTTP Error 403: Forbidden several times a day since 10/27/2016. I don't get any security reports anymore. Thanks for maintaining this useful package. -- System Information: Debian Release: 7.11 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.18.43-guest-7-e34a08f-x86_64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages debsecan depends on: ii debconf [debconf-2.0] 1.5.49 ii python 2.7.3-4+deb7u1 ii python-apt 0.8.8.2 Versions of packages debsecan recommends: ii cron3.0pl1-124 ii postfix [mail-transport-agent] 2.9.6-2 debsecan suggests no packages. -- debconf information: debsecan/source: debsecan/mailto: root debsecan/report: true debsecan/suite: GENERIC --- End Message --- --- Begin Message --- X-CrossAssassin-Score: 3062--- End Message ---
Processed: tagging 914794
Processing commands for cont...@bugs.debian.org: > tags 914794 + upstream pending Bug #914794 [src:libmspack] libmspack fails tests on big endian architectures (s390x, mips) Added tag(s) pending and upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 914794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #912395 in resteasy marked as pending
Processing control commands: > tag -1 pending Bug #912395 [src:resteasy3.0] resteasy3.0: FTBFS with Java 11 due to JAXB removal Added tag(s) pending. -- 912395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912395 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#912395: Bug #912395 in resteasy marked as pending
Control: tag -1 pending Hello, Bug #912395 in resteasy 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/resteasy/commit/7b849ed7f12a63a3e77dcbb4a735505fc069c4cd control, jaxb-api-compatibility.diff: Fix build, add libjaxb-api-java to build-depends. (Closes: #912395) (this message was generated automatically) -- Greetings https://bugs.debian.org/912395
Bug#906876: marked as done (xul-ext-scrapbook no longer works with firefox-esr 60)
Your message dated Tue, 04 Dec 2018 12:01:51 + with message-id and subject line Bug#915472: Removed package(s) from unstable has caused the Debian Bug report #906876, regarding xul-ext-scrapbook no longer works with firefox-esr 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.) -- 906876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xul-ext-scrapbook Version: 1.5.13-3 Severity: serious XUL addons are no longer supported. --- End Message --- --- Begin Message --- Version: 1.5.14-1+rm Dear submitter, as the package scrapbook 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/915472 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#906851: marked as done (xul-ext-firegestures no longer works with firefox-esr 60)
Your message dated Tue, 04 Dec 2018 12:01:22 + with message-id and subject line Bug#915471: Removed package(s) from unstable has caused the Debian Bug report #906851, regarding xul-ext-firegestures no longer works with firefox-esr 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.) -- 906851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: xul-ext-firegestures Version: 1.10.9-1 Severity: serious XUL addons are no longer supported. --- End Message --- --- Begin Message --- Version: 1.10.9-1+rm Dear submitter, as the package firegestures 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/915471 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 ---
