Bug#867694: netsurf-fb: Completely unusable due to missing dependencies, symlinks and documentation
Dear Salvo, > * Depend on what's necessary (the link above suggests > xserver-xorg-video-fbdev, fbset and implicitly fonts-dejavu-core) Axel: It really needs fonts-dejavu, as it also uses at least one font from fonts-dejavue-extra And the symlinks are not needed anymore with 3.9-1 I am currently not able to confirm/test the fb part, but if any of you are feel free to update the bug report here. Jonas: I think they are, just busy more with upstream than the packaging, I'm helping out here. Best,
Processed: closing 871028
Processing commands for cont...@bugs.debian.org: > close 871028 0.8.5-1 Bug #871028 [src:mailavenger] mailavenger FTBFS with gcc 7 Marked as fixed in versions mailavenger/0.8.5-1. Bug #871028 [src:mailavenger] mailavenger FTBFS with gcc 7 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 871028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 954636 with 888548
Processing commands for cont...@bugs.debian.org: > block 954636 with 888548 Bug #954636 [src:kismet] kismet: FTBFS: socket.h:285:33: error: flexible array member ‘cmsghdr::__cmsg_data’ not at end of ‘struct’ Bug #957402 [src:kismet] kismet: ftbfs with GCC-10 954636 was not blocked by any bugs. 954636 was not blocking any bugs. Added blocking bug(s) of 954636: 888548 957402 was not blocked by any bugs. 957402 was not blocking any bugs. Added blocking bug(s) of 957402: 888548 > thanks Stopping processing here. Please contact me if you need assistance. -- 954636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954636 957402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957402 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958840: kmer: autopkgtest regression: No module named 'localAlignerInterface'
Hi,
For some reason I din't included all my previous work on my merge request.
I've recovered most of it from a binary package I've found on my machine. And
after lot of hours I've found the python module naming issue (see d/rules
changes).
All changes are now included on:
https://salsa.debian.org/med-team/kmer/-/merge_requests/4
Sorry for the long delay and the childish mistake.
Best regrads,
PS: d/changelog is unmodified in my last MR. Probably should include a
reference to close this bug.
On Sat, May 16, 2020 at 07:37:54AM +0200, Andreas Tille wrote:
> Hi Antoni,
>
> since you once dived into this which was interrupted when Salsa was
> offline: Would you be able to finish this?
>
> That would be really helpful.
>
> Kind regards
>
> Andreas.
>
> On Tue, Apr 28, 2020 at 08:43:55PM +0200, Andreas Tille wrote:
> > On Tue, Apr 28, 2020 at 04:43:30PM +, Antoni Villalonga wrote:
> > >
> > > I think I've faced that problem and fixed.
> > > Fix should be included into '2to3.patch'
> > >
> > > I think the relevant part is:
> > >
> > > --- a/atac-driver/chainer/localalign/localAlignerInterfacemodule.C
> > > +++ b/atac-driver/chainer/localalign/localAlignerInterfacemodule.C
> > > @@ -227,8 +227,17 @@
> > > };
> > >
> > >
> > > +static struct PyModuleDef cModMethods =
> > > +{
> > > +PyModuleDef_HEAD_INIT,
> > > +"localAlignerInterface", /* name of module */
> > > +"", /* module documentation, may be NULL */
> > > +-1, /* size of per-interpreter state of the module, or -1
> > > if the module keeps state in global variables. */
> > > +registration_table
> > > +};
> > > +
> > > extern "C"
> > > -void initlocalAlignerInterface() {
> > > - Py_InitModule("localAlignerInterface", registration_table);
> > > +void PyInit_localAlignerInterface() {
> > > + PyModule_Create();
> > > }
> >
> > Thanks. Looks promising.
> >
> > > Sorry I can't access salsa due to a maintenance, also can't test
> > > autopkgtest
> > > for testing for the same reason.
> >
> > Salsa and other hosts seem to be back now.
> >
> > > It worked fine for sid some days ago.
> >
> > Kind regards and thanks a lot for your contribution
> >
> > Andreas.
> >
> > --
> > http://fam-tille.de
> >
> > ___
> > Debian-med-packaging mailing list
> > debian-med-packag...@alioth-lists.debian.net
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
>
> --
> http://fam-tille.de
--
Antoni Villalonga
https://friki.cat/
Bug#960899: paramiko: autopkgtests failures
Source: paramiko Version: 2.7.1-1 Severity: serious Hello, looks like the latest paramiko version is now failing its autopkgtests. Not sure if a) "invoke" should be moved from recommends to depends b) the autopkgtest needs to install recommends too c) something else Processing triggers for libc-bin (2.30-8) ... (Reading database ... 13936 files and directories currently installed.) Removing autopkgtest-satdep (0) ... autopkgtest [19:10:54]: test upstream: [--- = test session starts == platform linux -- Python 3.8.3, pytest-4.6.9, py-1.8.1, pluggy-0.13.0 -- /usr/bin/python3 cachedir: .pytest_cache rootdir: /tmp/autopkgtest-lxc.5uagjxdu/downtmp/build.uH0/src, inifile: setup.cfg collecting ... collected 257 items / 1 errors / 256 selected ERRORS ERROR collecting tests/test_config.py _ ImportError while importing test module '/tmp/autopkgtest-lxc.5uagjxdu/downtmp/build.uH0/src/tests/test_config.py'. Hint: make sure your test modules/packages have valid Python names. Traceback: tests/test_config.py:9: in from invoke import Result E ModuleNotFoundError: No module named 'invoke' !!! Interrupted: 1 errors during collection === 1 error in 0.59 seconds autopkgtest [19:10:55]: test upstream: ---] autopkgtest [19:10:55]: test upstream: - - - - - - - - - - results - - - - - - - - - - upstream FAIL non-zero exit status 2 autopkgtest [19:10:55]: summary cheers, Gianfranco
Bug#938100: marked as done (python-pyst: Python2 removal in sid/bullseye)
Your message dated Sun, 17 May 2020 23:43:24 + with message-id and subject line Bug#960874: Removed package(s) from unstable has caused the Debian Bug report #938100, regarding python-pyst: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pyst Version: 0.6.50-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-pyst If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 0.6.50-1+rm Dear submitter, as the package python-pyst 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/960874 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Processed: tagging 960865
Processing commands for cont...@bugs.debian.org: > # just a work-around, the real issue is likely #960892 > tags 960865 + pending Bug #960865 [src:aptitude] aptitude FTBFS with new po4a Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 960865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: po4a: --srcdir ignored by [po_directory]
Processing control commands: > affects -1 src:aptitude Bug #960892 [po4a] po4a: --srcdir ignored by [po_directory] Added indication that 960892 affects src:aptitude > block 960865 by -1 Bug #960865 [src:aptitude] aptitude FTBFS with new po4a 960865 was not blocked by any bugs. 960865 was blocking: 934135 Added blocking bug(s) of 960865: 960892 -- 960865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960865 960892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unblock 933128 with 960865, block 934135 with 960865
Processing commands for cont...@bugs.debian.org: > unblock 933128 with 960865 Bug #933128 [libparse-debianchangelog-perl] libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone becomes upstream 933128 was blocked by: 933133 933131 934135 960865 933128 was not blocking any bugs. Removed blocking bug(s) of 933128: 960865 > block 934135 with 960865 Bug #934135 [aptitude] aptitude: depends on libparse-debianchangelog-perl that has no upstream maintainer 934135 was not blocked by any bugs. 934135 was blocking: 933128 Added blocking bug(s) of 934135: 960865 > thanks Stopping processing here. Please contact me if you need assistance. -- 933128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933128 934135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934135 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960871: linux-image-amd64: iwlwifi: iwl_mvm_enable_txq NULL pointer dereference, address: 0000000000000068
Package: src:linux Version: 5.6.7-1 Severity: grave Tags: upstream Justification: renders package unusable This OOPS renders system unusable: May 17 06:28:33 kernel: [541237.462244] BUG: kernel NULL pointer dereference, address: 0068 May 17 06:28:33 kernel: [541237.462252] #PF: supervisor write access in kernel mode May 17 06:28:33 kernel: [541237.462256] #PF: error_code(0x0002) - not-present page May 17 06:28:33 kernel: [541237.462259] PGD 0 P4D 0 May 17 06:28:33 kernel: [541237.462265] Oops: 0002 [#1] SMP NOPTI May 17 06:28:33 kernel: [541237.462272] CPU: 0 PID: 3881793 Comm: kworker/0:1 Tainted: GW 5.6.0-1-amd64 #1 Debian 5.6.7-1 May 17 06:28:33 kernel: [541237.462275] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H270M-ITX/ac, BIOS P2.00 03/29/2017 May 17 06:28:33 kernel: [541237.462300] Workqueue: events iwl_mvm_add_new_dqa_stream_wk [iwlmvm] May 17 06:28:33 kernel: [541237.462321] RIP: 0010:iwl_trans_pcie_txq_enable+0x5f/0x430 [iwlwifi] May 17 06:28:33 kernel: [541237.462326] Code: 63 c6 4c 8b ac c7 c8 14 00 00 f0 48 0f ab 87 c8 24 00 00 73 0d 80 3d 52 0c 03 00 00 0f 84 82 03 00 00 44 89 c7 e8 31 b4 3f e7 <49> 89 45 68 48 85 db 0f 84 b6 02 00 00 0f b6 85 aa 25 00 00 44 39 May 17 06:28:33 kernel: [541237.462330] RSP: 0018:a9b60281fd20 EFLAGS: 00010203 May 17 06:28:33 kernel: [541237.462334] RAX: 09c4 RBX: RCX: May 17 06:28:33 kernel: [541237.462337] RDX: RSI: 001f RDI: 2710 May 17 06:28:33 kernel: [541237.462340] RBP: 9acfd78d8018 R08: 2710 R09: 0001 May 17 06:28:33 kernel: [541237.462343] R10: 0040 R11: R12: 001f May 17 06:28:33 kernel: [541237.462346] R13: R14: R15: 2710 May 17 06:28:33 kernel: [541237.462350] FS: () GS:9acfdf00() knlGS: May 17 06:28:33 kernel: [541237.462353] CS: 0010 DS: ES: CR0: 80050033 May 17 06:28:33 kernel: [541237.462356] CR2: 0068 CR3: 0001b320a003 CR4: 003606f0 May 17 06:28:33 kernel: [541237.462359] DR0: DR1: DR2: May 17 06:28:33 kernel: [541237.462362] DR3: DR6: fffe0ff0 DR7: 0400 May 17 06:28:33 kernel: [541237.462364] Call Trace: May 17 06:28:33 kernel: [541237.462391] iwl_mvm_enable_txq+0x173/0x260 [iwlmvm] May 17 06:28:33 kernel: [541237.462410] iwl_mvm_add_new_dqa_stream_wk+0x1c7/0x770 [iwlmvm] May 17 06:28:33 kernel: [541237.462420] process_one_work+0x1b4/0x380 May 17 06:28:33 kernel: [541237.462426] worker_thread+0x50/0x3c0 May 17 06:28:33 kernel: [541237.462433] kthread+0xf9/0x130 May 17 06:28:33 kernel: [541237.462438] ? process_one_work+0x380/0x380 May 17 06:28:33 kernel: [541237.462443] ? kthread_park+0x90/0x90 May 17 06:28:33 kernel: [541237.462452] ret_from_fork+0x1f/0x40 May 17 06:28:33 kernel: [541237.462458] Modules linked in: tcp_diag inet_diag veth sctp ctr ccm ipt_REJECT nf_reject_ipv4 xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter iptable_nat overlay bridge stp llc sit tunnel4 ip_tunnel ip6t_REJECT nf_reject_ipv6 xt_dscp xt_mark nf_log_ipv4 nf_log_common nft_limit xt_state xt_conntrack xt_LOG xt_limit xt_multiport nft_counter btusb intel_rapl_msr intel_rapl_common btrtl btbcm btintel nft_chain_nat bluetooth xt_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp nft_compat drbg nf_tables snd_hda_codec_hdmi ansi_cprng ecdh_generic ecc nfnetlink usblp crc16 x86_pkg_temp_thermal intel_powerclamp joydev snd_hda_codec_realtek binfmt_misc snd_hda_codec_generic kvm_intel ledtrig_audio snd_hda_intel kvm snd_intel_dspcfg irqbypass iwlmvm snd_hda_codec snd_hda_core ghash_clmulni_intel mac80211 snd_hwdep snd_pcm_oss libarc4 snd_mixer_oss iwlwifi aesni_intel libaes crypto_simd cryptd glue_helper snd_pcm intel_cstate snd_timer iTCO_wdt cfg80211 May 17 06:28:33 kernel: [541237.462518] intel_uncore snd iTCO_vendor_support mei_me intel_rapl_perf pcspkr watchdog soundcore rfkill sg mei evdev acpi_pad nct6775 hwmon_vid coretemp parport_pc ppdev lp parport ip_tables x_tables autofs4 uas usb_storage btrfs blake2b_generic xor zstd_decompress zstd_compress hid_generic usbhid hid raid6_pq libcrc32c crc32c_generic sd_mod i915 nvme nvme_core t10_pi crc_t10dif crc32_pclmul crc32c_intel ahci crct10dif_generic libahci e1000e igb drm_kms_helper i2c_i801 dca ptp pps_core xhci_pci crct10dif_pclmul crct10dif_common cec i2c_algo_bit xhci_hcd libata drm usbcore scsi_mod usb_common video button May 17 06:28:33 kernel: [541237.462569] CR2: 0068 May 17 06:28:33 kernel: [541237.462574] ---[ end trace 7f0c3e199a7a8e2c ]--- May 17 06:28:33 kernel: [541237.462591] RIP: 0010:iwl_trans_pcie_txq_enable+0x5f/0x430 [iwlwifi] May
Processed: submitter 960865
Processing commands for cont...@bugs.debian.org: > # Actually the comment which made me clone the bug report was actually by > intrigeri, so let's set him as submitter > submitter 960865 intrigeri Bug #960865 [src:aptitude] aptitude FTBFS with new po4a Changed Bug submitter to 'intrigeri ' from 'Guillem Jover '. > thanks Stopping processing here. Please contact me if you need assistance. -- 960865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960010: marked as done (freefem++: FBTFS (error: multiple definition of ‘enum CBLAS_SIDE’))
Your message dated Sun, 17 May 2020 21:04:13 +
with message-id
and subject line Bug#960010: fixed in freefem++ 3.61.1+dfsg1-5.1
has caused the Debian Bug report #960010,
regarding freefem++: FBTFS (error: multiple definition of ‘enum CBLAS_SIDE’)
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.)
--
960010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freefem++
Version: 3.61.1+dfsg1-5
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: block 959133 by -1
Dear Maintainer,
Your package FTBFS during the gsl transition.
The builog shows many errors like this:
In file included from /usr/include/gsl/gsl_blas_types.h:28,
from /usr/include/gsl/gsl_matrix_complex_long_double.h:29,
from /usr/include/gsl/gsl_matrix.h:4,
from /usr/include/gsl/gsl_eigen.h:24,
from /usr/include/gsl/gsl_sf_mathieu.h:26,
from /usr/include/gsl/gsl_sf.h:31,
from gsl.cpp:32:
/usr/include/gsl/gsl_cblas.h:46:6: error: multiple definition of ‘enum
CBLAS_ORDER’
46 | enum CBLAS_ORDER {CblasRowMajor=101, CblasColMajor=102};
| ^~~
https://buildd.debian.org/status/fetch.php?pkg=freefem%2B%2B=amd64=3.61.1%2Bdfsg1-5%2Bb3=1588901371=0
Kind Regards,
Bas
--- End Message ---
--- Begin Message ---
Source: freefem++
Source-Version: 3.61.1+dfsg1-5.1
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
freefem++, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 960...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated freefem++ 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: Sun, 17 May 2020 13:41:04 -0700
Source: freefem++
Architecture: source
Version: 3.61.1+dfsg1-5.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Stefano Rivera
Closes: 960010
Changes:
freefem++ (3.61.1+dfsg1-5.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix FTBFS with gsl 2.6 (Closes: #960010)
Checksums-Sha1:
2af8ea4a9c79bd90319bd03271b75682256d8159 2225 freefem++_3.61.1+dfsg1-5.1.dsc
e0d381c01294f78728aa853ff92aa75793b4f900 13260
freefem++_3.61.1+dfsg1-5.1.debian.tar.xz
1e11f8cc6c4d79a47e394c30eedb1c16e66824f9 15476
freefem++_3.61.1+dfsg1-5.1_source.buildinfo
Checksums-Sha256:
9e7fa7fa8c9b53dcb8c87179658f92ed8b59fa5d0d54714a2075fc3dfabd47f7 2225
freefem++_3.61.1+dfsg1-5.1.dsc
db3105e76445aed04497a2347c1382031a3dc180ad2dfc00266743eeae3d79dd 13260
freefem++_3.61.1+dfsg1-5.1.debian.tar.xz
9c32e7691114fd616e89c44246ec358c159e4a37c45a55aed80668a38acc47d3 15476
freefem++_3.61.1+dfsg1-5.1_source.buildinfo
Files:
a096dc56093ec57ad66fc9a91efca251 2225 science optional
freefem++_3.61.1+dfsg1-5.1.dsc
2af3c661ba63aaab768b6cba34d4ec46 13260 science optional
freefem++_3.61.1+dfsg1-5.1.debian.tar.xz
0dc3b0fca9d82794b1a83fafe8d5d87d 15476 science optional
freefem++_3.61.1+dfsg1-5.1_source.buildinfo
-BEGIN PGP SIGNATURE-
iHUEARYKAB0WIQTumtb5BSD6EfafSCRHew2wJjpU2AUCXsGh5AAKCRBHew2wJjpU
2ErRAQCMnaOiLdaLCXP4OhbfMaaZd96V2rQgggyoYsRHrmij1AEArAHSQ4jLd6CJ
Xk0yLAW3BTZ7wMowLMPe0BtFg4GdYgc=
=nSvx
-END PGP SIGNATURE End Message ---
Bug#960013: marked as done (freefem++: FTBFS with gsl 2.6)
Your message dated Sun, 17 May 2020 21:04:13 +
with message-id
and subject line Bug#960010: fixed in freefem++ 3.61.1+dfsg1-5.1
has caused the Debian Bug report #960010,
regarding freefem++: FTBFS with gsl 2.6
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.)
--
960010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freefem++
Version: 3.61.1+dfsg1-5
Severity: serious
Tags: ftbfs bullseye sid
Hi Maintainer
In a recent rebuild for the gsl 2.6 transition, freefem++ FTBFS on all
architectures.
I 've copied what I hope is the relevant part of the log below.
Regards
Graham
[1] https://buildd.debian.org/status/package.php?p=freefem%2B%2B
./ff-c++ -auto MUMPS_seq.cpp
eval ./ff-c++ MUMPS_seq.cpp -ldmumps_seq -lzmumps_seq
-lmumps_common_seq -lpord_seq -lmpiseq_seq -lblas -lmpiseq_seq
/usr/lib/gcc/x86_64-linux-gnu/9/libgfortran.so
/usr/lib/gcc/x86_64-linux-gnu/9/libquadmath.so -DAdd_ -lpthread
g++ -Wl,-z,relro -Wl,--as-needed -c -fPIC -g
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DNDEBUG -O3 -mmmx -mavx
-DBAMG_LONG_LONG -DNCHECKPTR -fPIC -g
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DNDEBUG -O3 -mmmx -mavx
-DBAMG_LONG_LONG -DNCHECKPTR -fPIC -Wdate-time -D_FORTIFY_SOURCE=2
-I./include '-DAdd_' 'MUMPS_seq.cpp'
In file included from /usr/include/gsl/gsl_blas_types.h:28,
from /usr/include/gsl/gsl_matrix_complex_long_double.h:29,
from /usr/include/gsl/gsl_matrix.h:4,
from /usr/include/gsl/gsl_eigen.h:24,
from /usr/include/gsl/gsl_sf_mathieu.h:26,
from /usr/include/gsl/gsl_sf.h:31,
from gsl.cpp:32:
/usr/include/gsl/gsl_cblas.h:46:6: error: multiple definition of ‘enum
CBLAS_ORDER’
46 | enum CBLAS_ORDER {CblasRowMajor=101, CblasColMajor=102};
| ^~~
In file included from ./include/MatriceCreuse_tpl.hpp:19,
from ./include/ff++.hpp:32,
from gsl.cpp:30:
/usr/include/x86_64-linux-gnu/cblas.h:49:14: note: previous definition here
49 | typedef enum CBLAS_ORDER {CblasRowMajor=101,
CblasColMajor=102} CBLAS_ORDER;
| ^~~
In file included from /usr/include/gsl/gsl_blas_types.h:28,
from /usr/include/gsl/gsl_matrix_complex_long_double.h:29,
from /usr/include/gsl/gsl_matrix.h:4,
from /usr/include/gsl/gsl_eigen.h:24,
from /usr/include/gsl/gsl_sf_mathieu.h:26,
from /usr/include/gsl/gsl_sf.h:31,
from gsl.cpp:32:
/usr/include/gsl/gsl_cblas.h:47:6: error: multiple definition of ‘enum
CBLAS_TRANSPOSE’
47 | enum CBLAS_TRANSPOSE {CblasNoTrans=111, CblasTrans=112,
CblasConjTrans=113};
| ^~~
In file included from ./include/MatriceCreuse_tpl.hpp:19,
from ./include/ff++.hpp:32,
from gsl.cpp:30:
/usr/include/x86_64-linux-gnu/cblas.h:50:14: note: previous definition here
50 | typedef enum CBLAS_TRANSPOSE {CblasNoTrans=111,
CblasTrans=112, CblasConjTrans=113, CblasConjNoTrans=114}
CBLAS_TRANSPOSE;
| ^~~
In file included from /usr/include/gsl/gsl_blas_types.h:28,
from /usr/include/gsl/gsl_matrix_complex_long_double.h:29,
from /usr/include/gsl/gsl_matrix.h:4,
from /usr/include/gsl/gsl_eigen.h:24,
from /usr/include/gsl/gsl_sf_mathieu.h:26,
from /usr/include/gsl/gsl_sf.h:31,
from gsl.cpp:32:
/usr/include/gsl/gsl_cblas.h:48:6: error: multiple definition of ‘enum
CBLAS_UPLO’
48 | enum CBLAS_UPLO {CblasUpper=121, CblasLower=122};
| ^~
In file included from ./include/MatriceCreuse_tpl.hpp:19,
from ./include/ff++.hpp:32,
from gsl.cpp:30:
/usr/include/x86_64-linux-gnu/cblas.h:51:14: note: previous definition here
51 | typedef enum CBLAS_UPLO {CblasUpper=121, CblasLower=122}
CBLAS_UPLO;
| ^~
In file included from /usr/include/gsl/gsl_blas_types.h:28,
from /usr/include/gsl/gsl_matrix_complex_long_double.h:29,
from /usr/include/gsl/gsl_matrix.h:4,
from /usr/include/gsl/gsl_eigen.h:24,
from /usr/include/gsl/gsl_sf_mathieu.h:26,
from /usr/include/gsl/gsl_sf.h:31,
from gsl.cpp:32:
/usr/include/gsl/gsl_cblas.h:49:6: error:
Processed: freefem++: diff for NMU version 3.61.1+dfsg1-5.1
Processing control commands: > tags 960010 + patch Bug #960010 [src:freefem++] freefem++: FBTFS (error: multiple definition of ‘enum CBLAS_SIDE’) Bug #960013 [src:freefem++] freefem++: FTBFS with gsl 2.6 Added tag(s) patch. Added tag(s) patch. -- 960010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960010 960013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960013 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960010: freefem++: diff for NMU version 3.61.1+dfsg1-5.1
Control: tags 960010 + patch
Dear maintainer,
I've prepared an NMU for freefem++ (versioned as 3.61.1+dfsg1-5.1). The diff
is attached to this message.
Regards,
SR
diff -Nru freefem++-3.61.1+dfsg1/debian/changelog freefem++-3.61.1+dfsg1/debian/changelog
--- freefem++-3.61.1+dfsg1/debian/changelog 2019-10-05 00:21:24.0 -0700
+++ freefem++-3.61.1+dfsg1/debian/changelog 2020-05-17 13:41:04.0 -0700
@@ -1,3 +1,10 @@
+freefem++ (3.61.1+dfsg1-5.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTBFS with gsl 2.6 (Closes: #960010)
+
+ -- Stefano Rivera Sun, 17 May 2020 13:41:04 -0700
+
freefem++ (3.61.1+dfsg1-5) unstable; urgency=medium
* Team upload.
diff -Nru freefem++-3.61.1+dfsg1/debian/patches/double-cblas-import.patch freefem++-3.61.1+dfsg1/debian/patches/double-cblas-import.patch
--- freefem++-3.61.1+dfsg1/debian/patches/double-cblas-import.patch 1969-12-31 16:00:00.0 -0800
+++ freefem++-3.61.1+dfsg1/debian/patches/double-cblas-import.patch 2020-05-17 13:21:25.0 -0700
@@ -0,0 +1,25 @@
+Description: Avoid FTBFS with gsl 2.6 by including 2 incompatible cblas headers
+Bug-Debian: https://bugs.debian.org/960010
+Author: Frederic Hecht
+Origin: upstream, https://github.com/FreeFem/FreeFem-sources/commit/3bfe3eb669c580583e9290474614b45cee52a96c
+
+--- a/src/femlib/MatriceCreuse_tpl.hpp
b/src/femlib/MatriceCreuse_tpl.hpp
+@@ -12,7 +12,7 @@
+ // test blas
+ // on MacOS9 under MWERKS
+ // cblas_ddot macos-9 is not
+-#ifdef HAVE_CBLAS_H
++#ifdef HAVE_CBLAS_H_BUG
+ extern "C" {
+ #define FF_VERSION VERSION
+ #undef VERSION
+@@ -21,7 +21,7 @@
+ #define VERSION VERSION
+ }
+ #define WITHBLAS 1
+-#elif HAVE_VECLIB_CBLAS_H
++#elif HAVE_VECLIB_CBLAS_BUG
+ #include
+ #define WITHBLAS 1
+ #endif
diff -Nru freefem++-3.61.1+dfsg1/debian/patches/series freefem++-3.61.1+dfsg1/debian/patches/series
--- freefem++-3.61.1+dfsg1/debian/patches/series 2019-10-05 00:21:24.0 -0700
+++ freefem++-3.61.1+dfsg1/debian/patches/series 2020-05-17 13:17:38.0 -0700
@@ -3,3 +3,4 @@
examples++-load.patch
src_fflib.patch
fix_all.edp.patch
+double-cblas-import.patch
Processed: Re: subnetcalc: bogus autopkgtest definition file blocking migration to testing
Processing control commands: > severity -1 serious Bug #939058 [src:subnetcalc] subnetcalc: bogus autopkgtest definition file blocking migration to testing Severity set to 'serious' from 'normal' -- 939058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939058 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960880: pev: autopkgtest failure: pehash did not report ASLR status
Source: pev Version: 0.80-4 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package pev has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest are now considered RC in testing. Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/amd64/p/pev/5529710/log.gz autopkgtest [13:21:31]: test test-runs: [--- valgrind is /usr/bin/valgrind ==831== Memcheck, a memory error detector ==831== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==831== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==831== Command: pesec /usr/share/win32/gzip.exe ==831== plugins: could not open directory 'src/build/plugins' -- No such file or directory ==831== ==831== HEAP SUMMARY: ==831== in use at exit: 18 bytes in 1 blocks ==831== total heap usage: 3 allocs, 2 frees, 4,602 bytes allocated ==831== ==831== LEAK SUMMARY: ==831==definitely lost: 0 bytes in 0 blocks ==831==indirectly lost: 0 bytes in 0 blocks ==831== possibly lost: 0 bytes in 0 blocks ==831==still reachable: 18 bytes in 1 blocks ==831== suppressed: 0 bytes in 0 blocks ==831== Rerun with --leak-check=full to see details of leaked memory ==831== ==831== For lists of detected and suppressed errors, rerun with: -s ==831== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) error: pesec did not report ASLR status ==833== Memcheck, a memory error detector ==833== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==833== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info ==833== Command: pehash /usr/share/win32/gzip.exe ==833== plugins: could not open directory 'src/build/plugins' -- No such file or directory ==833== ==833== HEAP SUMMARY: ==833== in use at exit: 18 bytes in 1 blocks ==833== total heap usage: 3 allocs, 2 frees, 4,602 bytes allocated ==833== ==833== LEAK SUMMARY: ==833==definitely lost: 0 bytes in 0 blocks ==833==indirectly lost: 0 bytes in 0 blocks ==833== possibly lost: 0 bytes in 0 blocks ==833==still reachable: 18 bytes in 1 blocks ==833== suppressed: 0 bytes in 0 blocks ==833== Rerun with --leak-check=full to see details of leaked memory ==833== ==833== For lists of detected and suppressed errors, rerun with: -s ==833== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) error: pehash did not report ASLR status autopkgtest [13:21:33]: test test-runs: ---] signature.asc Description: OpenPGP digital signature
Bug#960752: FTBFS on arch-all, test-suite failure - conova buildd has broken "localhost"
Control: retitle -1 FTBFS on IPv6-only hosts
Control: found -1 188-1
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/14098
Control: tag -1 patch upstream
Hello Aurelien,
Aurelien Jarno [2020-05-16 19:27 +0200]:
> This is an IPv6 host only,
Ah! This explains the issue indeed. I'm able to reproduce this now.
To unbreak unstable users ASAP, I uploaded a binary-all build for now.
Aurelien Jarno [2020-05-17 17:04 +0200]:
> As g_network_address_parse() supports escaping addresses with [] even
> for IPv4 addresses, I guess the following *untested* patch should fix
> the issue.
>
> --- a/src/common/test-webserver.c
> +++ b/src/common/test-webserver.c
> @@ -93,7 +93,7 @@
>/* HACK: this should be "localhost", but this fails on COPR;
> https://github.com/cockpit-project/cockpit/issues/12423 */
>tc->localport = g_strdup_printf ("127.0.0.1:%d", port);
>if (str)
> -tc->hostport = g_strdup_printf ("%s:%d", str, port);
> +tc->hostport = g_strdup_printf ("[%s]:%d", str, port);
>if (inet)
> g_object_unref (inet);
>g_free (str);
Spot on, thank you! I tested this and sent an upstream PR to fix this.
Martin
Processed: Re: Bug#960752: FTBFS on arch-all, test-suite failure - conova buildd has broken "localhost"
Processing control commands: > retitle -1 FTBFS on IPv6-only hosts Bug #960752 [src:cockpit] FTBFS on arch-all, test-suite failure Changed Bug title to 'FTBFS on IPv6-only hosts' from 'FTBFS on arch-all, test-suite failure'. > found -1 188-1 Bug #960752 [src:cockpit] FTBFS on IPv6-only hosts Marked as found in versions cockpit/188-1. > forwarded -1 https://github.com/cockpit-project/cockpit/pull/14098 Bug #960752 [src:cockpit] FTBFS on IPv6-only hosts Set Bug forwarded-to-address to 'https://github.com/cockpit-project/cockpit/pull/14098'. > tag -1 patch upstream Bug #960752 [src:cockpit] FTBFS on IPv6-only hosts Added tag(s) upstream and patch. -- 960752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchiving 952335, reassign 952335 to uglify-js, severity of 952335 is important ...
Processing commands for cont...@bugs.debian.org:
> unarchive 952335
Bug #952335 {Done: Xavier Guimard } [node-commander]
uglify-js: FTBFS: ERROR: `m` is not a supported option
Unarchived Bug 952335
> reassign 952335 uglify-js
Bug #952335 {Done: Xavier Guimard } [node-commander]
uglify-js: FTBFS: ERROR: `m` is not a supported option
Bug reassigned from package 'node-commander' to 'uglify-js'.
Ignoring request to alter found versions of bug #952335 to the same values
previously set
No longer marked as fixed in versions node-commander/4.0.1+really2.20.0-1.
> severity 952335 important
Bug #952335 {Done: Xavier Guimard } [uglify-js] uglify-js:
FTBFS: ERROR: `m` is not a supported option
Severity set to 'important' from 'serious'
> retitle 952335 Please update to node-commander-4 required by node-babel 7.9.6
Bug #952335 {Done: Xavier Guimard } [uglify-js] uglify-js:
FTBFS: ERROR: `m` is not a supported option
Changed Bug title to 'Please update to node-commander-4 required by node-babel
7.9.6' from 'uglify-js: FTBFS: ERROR: `m` is not a supported option'.
> reopen 952335
Bug #952335 {Done: Xavier Guimard } [uglify-js] Please update
to node-commander-4 required by node-babel 7.9.6
Bug reopened
Ignoring request to alter fixed versions of bug #952335 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
952335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#960867: fs-uae-launcher: The application crash every time at the beginning
(You should not remove the bug tracker from the CC) On 5/17/20 9:11 PM, Davide Lombardo wrote: > Nope I had the quite same crash output with the backport version: > > $fs-uae-launcher > [LOGGING] Logging to /home/davide/Documents/FS-UAE/Cache/Logs/fs-uae- > launcher.log.txt > FS-UAE Launcher 3.0.2 > ['/usr/bin/fs-uae-launcher'] > uname_result(system='Linux', node='PC0', release='4.19.0-9-amd64', > version='#1 > SMP Debian 4.19.118-2 (2020-04-29)', machine='x86_64', processor='') > Traceback (most recent call last): > File "/usr/share/fs-uae-launcher/fsgs/archive.py", line 15, in > from lhafile import LhaFile > ModuleNotFoundError: No module named 'lhafile' > [ARCHIVE] LhaFile module import problem > [SETTINGS] No settings path specified > [SETTINGS] Using default /home/davide/Documents/FS-UAE/Data/Settings.ini > [SETTINGS] File /home/davide/Documents/FS-UAE/Data/Settings.ini does not exist > [I18N] Initialize_locale language = > [I18N] Locale is en_GB > [I18N] Checking /usr/bin/share/fs-uae-launcher/share-dir > [I18N] Checking /usr/bin/../share/fs-uae-launcher/share-dir > [I18N] bindtextdomain fs-uae-launcher: /usr/bin/../share/locale > [I18N] find translations for en_GB in local directory /usr/bin/../share/locale > [I18N] Path to mo file: None > [I18N] Translations object: 0x7f88fb118e80> > corrupted size vs. prev_size in fastbins > KCrash: crashing... crashRecursionCounter = 2 > KCrash: Application Name = python3.7 path = /usr/bin pid = 5149 > KCrash: Arguments: > Alarm clock Which is a good indicator that's not a bug in fs-uae-launcher but some other package. > #apt-get reinstall libc6 && apt-get reinstall libgettextpo0 apt-get reinstall > python3 didn't work Just re-installing packages doesn't magically fix bugs, I'm afraid. I need to install a fresh Debian stable VM next week and see if I can reproduce the problem, but I'm very sure it's not a problem with fs-uae-launcher as even buggy Python code shouldn't be able to provoke a crash in glibc. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#960201: marked as done (python-gmpy2: autopkgtest regression: RuntimeWarning: coroutine '' was never awaited)
Your message dated Sun, 17 May 2020 12:17:17 -0700 with message-id and subject line Re: Bug#960201: Update has caused the Debian Bug report #960201, regarding python-gmpy2: autopkgtest regression: RuntimeWarning: coroutine '' was never awaited 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.) -- 960201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-gmpy2 Version: 2.1.0~b4-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Because your autopkgtest was part of the tests for glibc, I spotted that the autopkgtest of python-gmpy2 regressed recently. On 2020-05-01 at 19:13 we had the last successful run on arm64 in testing, the first failure was also on 2020-05-01, even earlier: at 02:08 in unstable on amd64. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul https://ci.debian.net/data/autopkgtest/unstable/amd64/p/python-gmpy2/5338978/log.gz autopkgtest [10:48:44]: test command1: [--- Unit tests for gmpy2 2.1.0b4 with Python 3.8.3rc1 Mutliple-precision library: GMP 6.2.0 Floating-point library: MPFR 4.0.2 Complex library:MPC 1.1.0 Caching Values: (Cache size)100 Caching Values: (Size in limbs) 128 Results for: test_context Attempted: 38 Failed:0 Results for: test_gmpy2_absAttempted: 83 Failed:0 Results for: test_gmpy2_addAttempted: 82 Failed:0 Results for: test_gmpy2_binary Attempted: 106 Failed:0 Results for: test_gmpy2_cmpAttempted: 41 Failed:0 Results for: test_gmpy2_comp Attempted: 89 Failed:0 Results for: test_gmpy2_const Attempted: 33 Failed:0 Results for: test_gmpy2_constructors Attempted: 34 Failed:0 Results for: test_gmpy2_convertAttempted: 50 Failed:0 Results for: test_gmpy2_divmod Attempted: 42 Failed:0 Results for: test_gmpy2_floordiv Attempted: 72 Failed:0 Results for: test_gmpy2_format Attempted: 102 Failed:0 Results for: test_gmpy2_fused Attempted: 18 Failed:0 Results for: test_gmpy2_lucas Attempted: 23 Failed:0 Results for: test_gmpy2_math Attempted: 147 Failed:0 Results for: test_gmpy2_minus Attempted: 14 Failed:0 Results for: test_gmpy2_mpfr_misc Attempted: 66 Failed:0 Results for: test_gmpy2_mpq_misc Attempted: 31 Failed:0 Results for: test_gmpy2_mpq_misc_py3 Attempted:3 Failed:0 Results for: test_gmpy2_mpz_bitops Attempted: 106 Failed:0 Results for: test_gmpy2_mpz_divmod Attempted: 67 Failed:0 Results for: test_gmpy2_mpz_divmod2exp Attempted: 66 Failed:0 Results for: test_gmpy2_mpz_inplaceAttempted: 85 Failed:0 Results for: test_gmpy2_mpz_misc Attempted: 225 Failed:0 Results for: test_gmpy2_mpz_misc_py3 Attempted: 19 Failed:0 Results for: test_gmpy2_mulAttempted: 68 Failed:0 Results for: test_gmpy2_muldiv_2expAttempted: 24 Failed:0 Results for: test_gmpy2_plus Attempted: 16 Failed:0 Results for: test_gmpy2_powAttempted: 53 Failed:0 Results for: test_gmpy2_predicate Attempted: 120 Failed:0 Results for: test_gmpy2_prpAttempted: 57 Failed:0 Results for: test_gmpy2_root Attempted: 23 Failed:0 Results for: test_gmpy2_square Attempted: 19 Failed:0 Results for: test_gmpy2_subAttempted: 83 Failed:0 Results for: test_gmpy2_xmpz_inplace Attempted: 79 Failed:0 ** File "test/test_gmpy2_xmpz_misc.txt", line 91, in test_gmpy2_xmpz_misc.txt Failed example: [b for b in iter] Differences (ndiff with -expected +actual): - [False, False, False, False, True] ** File "test/test_gmpy2_xmpz_misc.txt", line 95, in test_gmpy2_xmpz_misc.txt Failed example: [b for b in iter] Differences (ndiff with -expected +actual): - [False, True, True, True, True]
Processed: meson 0.54.2-1 breaks bali-phy build
Processing control commands: > affects -1 src:bali-phy Bug #960877 [meson] meson 0.54.2-1 breaks bali-phy build Added indication that 960877 affects src:bali-phy -- 960877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960877: meson 0.54.2-1 breaks bali-phy build
Package: meson Version: 0.54.2-1 Severity: serious Tags: ftbfs Control: affects -1 src:bali-phy https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/bali-phy.html ... FAILED: src/builtins/Prelude.so c++ -o src/builtins/Prelude.so 'src/builtins/2382537@@Prelude@sha/Prelude.cc.o' -Wl,--as-needed -Wl,--allow-shlib-undefined -Wl,-O1 -shared -fPIC -Wl,--start-group -Wl,-soname,Prelude.so -g -O2 -ffile-prefix-map=/build/1st/bali-phy-3.5.0.1+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -Wl,-z,relro -Wl,-z,now /usr/lib/x86_64-linux-gnu/libboost_program_options.a /usr/lib/x86_64-linux-gnu/libboost_random.a /usr/lib/x86_64-linux-gnu/libboost_system.a /usr/lib/x86_64-linux-gnu/libboost_filesystem.a /usr/lib/x86_64-linux-gnu/libboost_chrono.a -Wl,--end-group /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libboost_system.a(error_code.o): relocation R_X86_64_PC32 against symbol `_ZTVN5boost6system6detail22generic_error_categoryE' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: bad value collect2: error: ld returned 1 exit status Why is it trying to link with the static library?
Bug#960876: bcalm: autopkgtest regression: python: command not found
Source: bcalm Version: 2.2.2-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of bcalm the autopkgtest of bcalm fails in testing when that autopkgtest is run with the binary packages of bcalm from unstable. It passes when run with only packages from testing. In tabular form: passfail bcalm from testing2.2.2-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Seems like you missed that python now needs to be called with a version: python2. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=bcalm https://ci.debian.net/data/autopkgtest/testing/amd64/b/bcalm/5517318/log.gz Finding links between unitigs 19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 1 pass 0 19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 2 (0kmers/0extremities)19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 1 pass 1 19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 2 (0kmers/0extremities)19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 1 pass 2 19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 2 (0kmers/0extremities)19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 1 pass 3 19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 2 (0kmers/0extremities)19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 1 pass 4 19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 2 (2kmers/2extremities)19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 1 pass 5 19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 2 (0kmers/0extremities)19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 1 pass 6 19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 2 (0kmers/0extremities)19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 1 pass 7 19:07:17 memory [current, maxRSS]: [ 80, 80] MB step 2 (0kmers/0extremities)19:07:17 memory [current, maxRSS]: [ 80, 80] MB gathering links from disk 19:07:17 memory [current, maxRSS]: [ 80, 80] MB Done finding links between unitigs 19:07:17 memory [current, maxRSS]: [ 80, 80] MB simple_test.sh: line 9: python: command not found test KO signature.asc Description: OpenPGP digital signature
Processed: e-antic breaks normaliz autopkgtest: version `LIBEANTICXX_0_1_2' not found (required by /usr/bin/normaliz)
Processing control commands: > found -1 e-antic/0.1.5+ds-1 Bug #960875 [src:e-antic, src:normaliz] e-antic breaks normaliz autopkgtest: version `LIBEANTICXX_0_1_2' not found (required by /usr/bin/normaliz) Marked as found in versions e-antic/0.1.5+ds-1. > found -1 normaliz/3.8.3+ds-2 Bug #960875 [src:e-antic, src:normaliz] e-antic breaks normaliz autopkgtest: version `LIBEANTICXX_0_1_2' not found (required by /usr/bin/normaliz) Marked as found in versions normaliz/3.8.3+ds-2. -- 960875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960875: e-antic breaks normaliz autopkgtest: version `LIBEANTICXX_0_1_2' not found (required by /usr/bin/normaliz)
Source: e-antic, normaliz Control: found -1 e-antic/0.1.5+ds-1 Control: found -1 normaliz/3.8.3+ds-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of e-antic the autopkgtest of normaliz fails in testing when that autopkgtest is run with the binary packages of e-antic from unstable. It passes when run with only packages from testing. In tabular form: passfail e-anticfrom testing0.1.5+ds-1 normaliz from testing3.8.3+ds-2 all others from testingfrom testing I copied some of the output at the bottom of this report. I'm not totally familiar with this error, but doesn't it hint at a forgotten SONAME bump in e-antic? Or is normaliz doing unconventional loading of libraries? In the latter case, is a stricter versioned dependency warranted, or should we rely on autopkgtest to catch issues like this? Currently this regression is blocking the migration of e-antic to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=e-antic https://ci.debian.net/data/autopkgtest/testing/amd64/n/normaliz/5521842/log.gz autopkgtest [19:07:43]: test command1: [--- make: Entering directory '/tmp/autopkgtest-lxc.rk7cc6n6/downtmp/build.Xon/src/test' /usr/bin/normaliz -s test-s/mode456 /usr/bin/normaliz: /lib/x86_64-linux-gnu/libeanticxx.so.0: version `LIBEANTICXX_0_1_2' not found (required by /usr/bin/normaliz) /usr/bin/normaliz: /lib/x86_64-linux-gnu/libeantic.so.0: version `LIBEANTIC_0_1_2' not found (required by /usr/bin/normaliz) /usr/bin/normaliz: /lib/x86_64-linux-gnu/libeantic.so.0: version `LIBEANTIC_0_1_2' not found (required by /lib/x86_64-linux-gnu/libnormaliz.so.3) /usr/bin/normaliz: /lib/x86_64-linux-gnu/libeanticxx.so.0: version `LIBEANTICXX_0_1_2' not found (required by /lib/x86_64-linux-gnu/libnormaliz.so.3) make: *** [Makefile.classic:126: test-s/mode456.out] Error 1 make: Leaving directory '/tmp/autopkgtest-lxc.rk7cc6n6/downtmp/build.Xon/src/test' autopkgtest [19:07:43]: test command1: ---] signature.asc Description: OpenPGP digital signature
Bug#960873: mothur: autopkgtest regression: Segmentation fault
Source: mothur Version: 1.44.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of mothur the autopkgtest of mothur fails in testing when that autopkgtest is run with the binary packages of mothur from unstable. It passes when run with only packages from testing. In tabular form: passfail mothur from testing1.44.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=mothur https://ci.debian.net/data/autopkgtest/testing/amd64/m/mothur/5517339/log.gz autopkgtest [19:10:00]: test run-unit-test: [--- TERM environment variable not set. unique.seqs(fasta=HA.fasta) command Linux version Using ReadLine mothur v.1.44.0 Last updated: 05/16/2020 by Patrick D. Schloss Department of Microbiology & Immunology University of Michigan http://www.mothur.org When using, please cite: Schloss, P.D., et al., Introducing mothur: Open-source, platform-independent, community-supported software for describing and comparing microbial communities. Appl Environ Microbiol, 2009. 75(23):7537-41. Distributed under the GNU General Public License Type 'help()' for information on the commands that are available For questions and analysis support, please visit our forum at https://forum.mothur.org Type 'quit()' to exit program [NOTE]: Setting random seed to 19760620. Batch Mode mothur > unique.seqs(fasta=HA.fasta) 599 259 Output File Names: HA.names HA.unique.fasta dist.seqs(fasta=HA.unique.fasta, countends=F, cutoff=0.01) command mothur > dist.seqs(fasta=HA.unique.fasta, countends=F, cutoff=0.01) Using 2 processors. SequenceTimeNum_Dists_Below_Cutoff 0 0 0 200 0 3443 100 0 5025 258 0 15965 182 0 16617 It took 0 secs to find distances for 259 sequences. 32582 distances below cutoff 0.01. Output File Names: HA.unique.dist cluster(method=furthest, column=HA.unique.dist, name=HA.names, cutoff=0.01, precision=1000) command mothur > cluster(method=furthest, column=HA.unique.dist, name=HA.names, cutoff=0.01, precision=1000) Using 2 processors. unique 154 211 18 2 6 0 4 2 0 2 0 0 0 1 0 0 0 0 2 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0.001 155 161 28 5 3 4 2 4 0 0 1 0 1 0 1 0 0 0 0 2 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Bug#960872: gtkgl2: autopkgtest failure: cc: not found
Source: gtkgl2 Version: 2.1.0-0.1 X-Debbugs-CC: debian...@lists.debian.org, nico...@debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Nicolas, With a recent upload of gtkgl2 an autopkgtest was added, great. However, it fails. I copied some of the output at the bottom of this report. There seems to be missing a test dependency. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? 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=gtkgl2 https://ci.debian.net/data/autopkgtest/testing/amd64/g/gtkgl2/5240227/log.gz autopkgtest [21:18:39]: test link-basic-example: [--- /tmp/autopkgtest-lxc.0adei5av/downtmp/build.N6w/src/debian/tests/link-basic-example: 9: cc: not found autopkgtest [21:18:39]: test link-basic-example: ---] signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#960867: fs-uae-launcher: The application crash every time at the beginning
Processing control commands: > tags -1 moreinfo Bug #960867 [fs-uae-launcher] fs-uae-launcher: The application crash every time at the beginning Added tag(s) moreinfo. -- 960867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960867 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960867: fs-uae-launcher: The application crash every time at the beginning
Control: tags -1 moreinfo Hello! On 5/17/20 7:57 PM, Davide Lombardo wrote: > [I18N] Initialize_locale language = > [I18N] Locale is en_GB > [I18N] Checking /usr/bin/share/fs-uae-launcher/share-dir > [I18N] Checking /usr/bin/../share/fs-uae-launcher/share-dir > [I18N] bindtextdomain fs-uae-launcher: /usr/bin/../share/locale > [I18N] find translations for en_GB in local directory /usr/bin/../share/locale > [I18N] Path to mo file: None > [I18N] Translations object: 0x7fd7ddc11eb8> > corrupted size vs. prev_size in fastbins > KCrash: crashing... crashRecursionCounter = 2 > KCrash: Application Name = python3.7 path = /usr/bin pid = 7000 > KCrash: Arguments: > Alarm clock The error message "corrupted size vs. prev_size in fastbins" indicates a crash in the C library which can normally not happen when Python code is executed. So I'm not sure this is actually a bug in fs-uae-launcher, it looks more like a problem with gettext. You can try to install fs-uae from stable-backports and see if that helps. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#947124: marked as done (apache-log4j1.2: CVE-2019-17571)
Your message dated Sun, 17 May 2020 18:17:26 + with message-id and subject line Bug#947124: fixed in apache-log4j1.2 1.2.17-7+deb9u1 has caused the Debian Bug report #947124, regarding apache-log4j1.2: CVE-2019-17571 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.) -- 947124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apache-log4j1.2 Version: 1.2.17-8 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 1.2.17-7 Control: found -1 1.2.17-5 Hi, The following vulnerability was published for apache-log4j1.2. CVE-2019-17571[0]: | Included in Log4j 1.2 is a SocketServer class that is vulnerable to | deserialization of untrusted data which can be exploited to remotely | execute arbitrary code when combined with a deserialization gadget | when listening to untrusted network traffic for log data. This affects | Log4j versions up to 1.2 up to 1.2.17. Note that this issue correponds to the old CVE-2017-5645 for the 2.x branch codebasis[1]. 1.2 reached end of life in 2015 accordingly, and the "right move" would be to switch to 2.x. Which raises a question from security support point of view: We would need to fade out apache-log4j1.2 for bullseye at least now right? From a quick check via a simulated dak rm, it looks right now impossible to actually remove it. Are there current plans from the Debian Java Maintainers for that? Or is there something I currently just miss from the big picture? If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-17571 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571 [1] https://www.openwall.com/lists/oss-security/2019/12/19/2 Regards, Salvatore --- End Message --- --- Begin Message --- Source: apache-log4j1.2 Source-Version: 1.2.17-7+deb9u1 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of apache-log4j1.2, 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 947...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated apache-log4j1.2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 02 May 2020 16:38:32 +0200 Source: apache-log4j1.2 Binary: liblog4j1.2-java liblog4j1.2-java-doc Architecture: source all Version: 1.2.17-7+deb9u1 Distribution: stretch-security Urgency: high Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Description: liblog4j1.2-java - Logging library for java liblog4j1.2-java-doc - Documentation for liblog4j1.2-java Closes: 947124 Changes: apache-log4j1.2 (1.2.17-7+deb9u1) stretch-security; urgency=high . * Team upload. * Fix CVE-2019-17571. (Closes: #947124) Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. Checksums-Sha1: ce9f1dcc0e56d66ca184e91446227245fdf74c7f 2497 apache-log4j1.2_1.2.17-7+deb9u1.dsc a03a876f4ada27f8053564b23bc04e30b6449ac5 9900 apache-log4j1.2_1.2.17-7+deb9u1.debian.tar.xz 29b16b3abc1cd94f7a5266de0ecd3eaea64d6acc 11600 apache-log4j1.2_1.2.17-7+deb9u1_amd64.buildinfo 2487f9e30f98fcceab0f717d0cf8b85c6ebea46f 248308 liblog4j1.2-java-doc_1.2.17-7+deb9u1_all.deb 18ba7701cdd240e4f1b46867ee59429a53cda2e8 430572 liblog4j1.2-java_1.2.17-7+deb9u1_all.deb Checksums-Sha256: 10a58d90a8b2c7c8ca6d2fc19e1799dc8c0cc1d78efba9bb79d2b736608f75b9 2497 apache-log4j1.2_1.2.17-7+deb9u1.dsc 963631dd761cf3275159450838d3460bfa8d7041159765a060de7a8e141c6c6d 9900 apache-log4j1.2_1.2.17-7+deb9u1.debian.tar.xz 78c17606857df9efe35463f3cb3d4205d821eb75983edddabe29afd9c73ceb01 11600 apache-log4j1.2_1.2.17-7+deb9u1_amd64.buildinfo 549886bf31a46846528055f5655d7885eacdbc360d8421cce531dbdc7f337af7 248308
Bug#942352: marked as done (python3-scales: wrong package name)
Your message dated Sun, 17 May 2020 18:03:23 + with message-id and subject line Bug#960849: Removed package(s) from unstable has caused the Debian Bug report #942352, regarding python3-scales: wrong package name 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.) -- 942352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942352 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-scales Severity: serious Hello, python3-scales installs a module in dist-packages/greplin/scales so it should be called python3-greplin.scales , please rename it (handling properly the transition) Since it violates the policy, severity is set to serious. Regards, Sandro -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-scales depends on: ii python3 3.7.3-1 ii python3-six 1.12.0-1 python3-scales recommends no packages. Versions of packages python3-scales suggests: ii python3-flask 1.0.2-3 --- End Message --- --- Begin Message --- Version: 1.0.9-2.1+rm Dear submitter, as the package python-scales 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/960849 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. 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#960867: fs-uae-launcher: The application crash every time at the beginning
Package: fs-uae-launcher Version: 2.8.4+dfsg-2 Severity: grave Justification: renders package unusable Dear Maintainer, The program crash at the beginning of the execution and print this outputin my console: $ fs-uae-launcher 2.8.3 enabling except hook enable tread exception handler uname_result(system='Linux', node='PC0', release='4.19.0-9-amd64', version='#1 SMP Debian 4.19.118-2 (2020-04-29)', machine='x86_64', processor='') ['/usr/bin/fs-uae-launcher'] FS-UAE Launcher 2.8.3 Traceback (most recent call last): File "/usr/share/fs-uae-launcher/fsgs/Archive.py", line 9, in from lhafile import LhaFile ModuleNotFoundError: No module named 'lhafile' LhaFile module import problem [SETTINGS] Constructor [SETTINGS] No settings path specified [SETTINGS] Using default /home/davide/Documents/FS-UAE/Data/Settings.ini [SETTINGS] File /home/davide/Documents/FS-UAE/Data/Settings.ini does not exist [I18N] Initialize_locale language = [I18N] Locale is en_GB [I18N] Checking /usr/bin/share/fs-uae-launcher/share-dir [I18N] Checking /usr/bin/../share/fs-uae-launcher/share-dir [I18N] bindtextdomain fs-uae-launcher: /usr/bin/../share/locale [I18N] find translations for en_GB in local directory /usr/bin/../share/locale [I18N] Path to mo file: None [I18N] Translations object: corrupted size vs. prev_size in fastbins KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = python3.7 path = /usr/bin pid = 7000 KCrash: Arguments: Alarm clock -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fs-uae-launcher depends on: ii fs-uae 2.8.4+dfsg-2 ii python3 3.7.3-1 ii python3-pyqt5 5.11.3+dfsg-1+b3 ii python3-pyqt5.qtopengl 5.11.3+dfsg-1+b3 ii python3-setuptools 40.8.0-1 fs-uae-launcher recommends no packages. fs-uae-launcher suggests no packages. -- no debconf information
Bug#936557: freeorion: Python2 removal in sid/bullseye
Why does this bug still exist? I was able to build headless Freeorion on Devuan with Python 3 just by changing the control file (see https://framagit.org/specing/debian-freeorion/-/commit/948beb224601838163bf7c9bea4d8bcf677dcb8d). It seems that Freeorion migrated from Python 2 a long time ago?
Bug#960866: libnewlib-nano FTBFS with meson 0.54.2-1
Source: libnewlib-nano Version: 2.11.2-1 Severity: serious Tags: ftbfs bullseye sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libnewlib-nano.html ... Configuring newlib.h using configuration Configuring _newlib_version.h using configuration meson.build:187: WARNING: Consider using the built-in debug option instead of using "-g". meson.build:187: WARNING: Consider using the built-in optimization level instead of using "-Os". WARNING: Target "arm_v5te_softfp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "arm_v5te_hard/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7_fp_softfp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7_fp_hard/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v6_m_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7_m_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7e_m_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7e_m_fp_softfp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7e_m_fp_hard/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7e_m_dp_softfp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7e_m_dp_hard/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v8_m_base_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v8_m_main_nofp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v8_m_main_fp_softfp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v8_m_main_fp_hard/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v8_m_main_dp_softfp/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v8_m_main_dp_hard/libc" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "arm_v5te_softfp/libm" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "arm_v5te_hard/libm" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_nofp/libm" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7_nofp/libm" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7_fp_softfp/libm" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v7_fp_hard/libm" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error in the future. WARNING: Target "thumb_v6_m_nofp/libm" has a path separator in its name. This is not supported, it can cause unexpected failures and will become a hard error
Processed: cloning 934135, retitle -1 to aptitude FTBFS with new po4a, reassign -1 to src:aptitude ...
Processing commands for cont...@bugs.debian.org: > clone 934135 -1 Bug #934135 [aptitude] aptitude: depends on libparse-debianchangelog-perl that has no upstream maintainer Bug 934135 cloned as bug 960865 933128 was blocked by: 933131 933133 934135 933128 was not blocking any bugs. Added blocking bug(s) of 933128: 960865 > retitle -1 aptitude FTBFS with new po4a Bug #960865 [aptitude] aptitude: depends on libparse-debianchangelog-perl that has no upstream maintainer Changed Bug title to 'aptitude FTBFS with new po4a' from 'aptitude: depends on libparse-debianchangelog-perl that has no upstream maintainer'. > reassign -1 src:aptitude 0.8.12-3 Bug #960865 [aptitude] aptitude FTBFS with new po4a Bug reassigned from package 'aptitude' to 'src:aptitude'. Ignoring request to alter found versions of bug #960865 to the same values previously set Ignoring request to alter fixed versions of bug #960865 to the same values previously set Bug #960865 [src:aptitude] aptitude FTBFS with new po4a Marked as found in versions aptitude/0.8.12-3. > severity -1 serious Bug #960865 [src:aptitude] aptitude FTBFS with new po4a Severity set to 'serious' from 'important' > tags -1 = ftbfs Bug #960865 [src:aptitude] aptitude FTBFS with new po4a Added tag(s) ftbfs; removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 933128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933128 934135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934135 960865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960623: marked as done (boost1.67 should build depend on libicu-dev (<< 64))
Your message dated Sun, 17 May 2020 16:18:42 + with message-id and subject line Bug#960623: fixed in boost1.67 1.67.0-18 has caused the Debian Bug report #960623, regarding boost1.67 should build depend on libicu-dev (<< 64) 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.) -- 960623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: boost1.67 Version: 1.67.0-17 Severity: serious Control: block 960193 by -1 Changing the icu version changes the libboost_regex ABI. The libboost-regex*-icu* provides untangle icu transitions from boost transitions, but reverse dependencies of libboost-regex1.67.0 in buster depend on libboost-regex1.67.0 not libboost-regex1.67.0-icu63. A build dependency on libicu-dev (<< 64) would prevent accidental recompilation with a more recent icu, avoiding problems if people would install the rebuilt libboost-regex1.67.0 on buster. If wanted I can NMU this change. --- End Message --- --- Begin Message --- Source: boost1.67 Source-Version: 1.67.0-18 Done: Giovanni Mascellani We believe that the bug you reported is fixed in the latest version of boost1.67, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Giovanni Mascellani (supplier of updated boost1.67 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: Sun, 17 May 2020 17:48:01 +0200 Source: boost1.67 Architecture: source Version: 1.67.0-18 Distribution: unstable Urgency: medium Maintainer: Debian Boost Team Changed-By: Giovanni Mascellani Closes: 958022 960623 Changes: boost1.67 (1.67.0-18) unstable; urgency=medium . * Build-Depend on libicu-dev (<< 64), to prevent recompiling with recent versions of libicu, which would break dependencies which still use the unversioned libboost-regex1.67.0 dependency (closes: #960623). * Fix allocator usage in multi_array when targetting C++20 (closes: #958022). Checksums-Sha1: c5009b287a931b631363f0f0ede797c0d98044ea 7756 boost1.67_1.67.0-18.dsc fa76c14e23c497879f619341e8b9684a97365cba 355496 boost1.67_1.67.0-18.debian.tar.xz 0c8b3ac629324a560d1db31a3de26ec356d7348b 14271 boost1.67_1.67.0-18_source.buildinfo Checksums-Sha256: 6e783165fe6c353cbd8255e79a972648aa2014267ab01579a7015a151ba3fd86 7756 boost1.67_1.67.0-18.dsc 909a84a953700601f67c32be916b470e974bae079327a5fb600be5354668cf54 355496 boost1.67_1.67.0-18.debian.tar.xz 6909f554685251b41b78f2a21ab25c76d29c64116205f75aed4f75fe86eca08d 14271 boost1.67_1.67.0-18_source.buildinfo Files: 7d5bb2eb54e747b46dcb5f8da15cbdf9 7756 libs optional boost1.67_1.67.0-18.dsc a2627e68ffc2b1a04ebdad2db95ec686 355496 libs optional boost1.67_1.67.0-18.debian.tar.xz fb5685ee2904d24dc906c68e61fd28ee 14271 libs optional boost1.67_1.67.0-18_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYKAB0WIQSiBF6hBvCQNcghJEaNr8EMz954SQUCXsFdGwAKCRCNr8EMz954 SaSJAQDPlwtKA/7g3FYuNyX0KE50yTDdOqh+6bQsOw234PhgbgD+PUCfHKbfawn7 sLOxi1TDzyJwiH8uNRcEYo4ZzIWq+g4= =4BVj -END PGP SIGNATURE End Message ---
Processed: ytcc: diff for NMU version 1.8.1-1.1
Processing control commands: > tags 960354 + patch Bug #960354 [src:ytcc] ytcc: Failed to migrate to testing for too long Added tag(s) patch. > tags 960354 + pending Bug #960354 [src:ytcc] ytcc: Failed to migrate to testing for too long Added tag(s) pending. -- 960354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960354: ytcc: diff for NMU version 1.8.1-1.1
Control: tags 960354 + patch Control: tags 960354 + pending Dear maintainer, I've prepared an NMU for ytcc (versioned as 1.8.1-1.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards. diff -Nru ytcc-1.8.1/debian/changelog ytcc-1.8.1/debian/changelog --- ytcc-1.8.1/debian/changelog2019-05-08 23:00:16.0 +0800 +++ ytcc-1.8.1/debian/changelog2020-05-17 23:31:49.0 +0800 @@ -1,3 +1,10 @@ +ytcc (1.8.1-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Source-only upload to allow testing migration. (Closes: #960354) + + -- Boyuan Yang Sun, 17 May 2020 23:31:49 +0800 + ytcc (1.8.1-1) unstable; urgency=medium * Initial release. (Closes: #928755)
Bug#951877: Patch: OpenSSL linking without license exception
[Bastian Germann] > This patch builds the package without OpenSSL. Dropping https support will make the library unusable for at least some of its current users. I thus would recommend coming up with a different approach, for example the idea about linking against wolfssl. -- Happy hacking Petter Reinholdtsen
Processed: Re: emacs: https to plain http downgrade after unhandled GNUTLS_E_AGAIN error in TLS1.3 connection
Processing commands for cont...@bugs.debian.org: > fixed 956712 1:26.3+1-2 Bug #956712 [emacs] emacs: https to plain http downgrade after unhandled GNUTLS_E_AGAIN error in TLS1.3 connection Marked as fixed in versions emacs/1:26.3+1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 956712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956712 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#956712: emacs: https to plain http downgrade after unhandled GNUTLS_E_AGAIN error in TLS1.3 connection
fixed 956712 1:26.3+1-2 thanks I can confirm that as reported by Heenec, this is fixed in unstable given it's on 26.3 now.
Bug#960752: FTBFS on arch-all, test-suite failure - conova buildd has broken "localhost"
control: tag -1 + ipv6
On 2020-05-16 19:27, Aurelien Jarno wrote:
> On 2020-05-16 17:45, Martin Pitt wrote:
> > Michael Biebl [2020-05-16 12:39 +0200]:
> > > Source: cockpit
> > > Version: 219-1
> > > Severity: serious
> > >
> > > Hi Martin,
> > >
> > > looks like the latest release reliably triggers a FTBFS on arch-all:
> > >
> > > https://buildd.debian.org/status/logs.php?pkg=cockpit=219-1=all
> > >
> > > The relevant part from the build log
> > > **
> > > cockpit-protocol:ERROR:src/common/test-webserver.c:374:perform_request:
> > > assertion failed (error == NULL): Error resolving
> > > ?2a02:16a8:dc41:100::238:46259?: Name or service not known
> > > (g-resolver-error-quark, 0)
The address 2a02:16a8:dc41:100::238:46259 is not correct. When combining
and IPv6 address and a port, the address must be escaped with []. This
means that the following code from test-webserver.c is incorrect:
| inet = cockpit_test_find_non_loopback_address ();
| /* this can fail in environments with only localhost */
| if (inet != NULL)
| str = g_inet_address_to_string (inet);
...
| if (str)
| tc->hostport = g_strdup_printf ("%s:%d", str, port);
As g_network_address_parse() supports escaping addresses with [] even
for IPv4 addresses, I guess the following *untested* patch should fix
the issue.
--- a/src/common/test-webserver.c
+++ b/src/common/test-webserver.c
@@ -93,7 +93,7 @@
/* HACK: this should be "localhost", but this fails on COPR;
https://github.com/cockpit-project/cockpit/issues/12423 */
tc->localport = g_strdup_printf ("127.0.0.1:%d", port);
if (str)
-tc->hostport = g_strdup_printf ("%s:%d", str, port);
+tc->hostport = g_strdup_printf ("[%s]:%d", str, port);
if (inet)
g_object_unref (inet);
g_free (str);
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
Bug#858037: marked as done (ikarus FTBFS on i386: recipe for target 'ikarus.boot' failed (Segmentation fault))
Your message dated Sun, 17 May 2020 15:04:11 + with message-id and subject line Bug#858037: fixed in ikarus 0.0.3+bzr.2010.01.26-7 has caused the Debian Bug report #858037, regarding ikarus FTBFS on i386: recipe for target 'ikarus.boot' failed (Segmentation fault) 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.) -- 858037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ikarus Version: 0.0.3+bzr.2010.01.26-4 Severity: serious https://buildd.debian.org/status/logs.php?pkg=ikarus=i386 ... dh_auto_build -- -C scheme make -j4 -C scheme make[2]: Entering directory '/«BUILDDIR»/ikarus-0.0.3+bzr.2010.01.26/scheme' echo '(define ikarus-version "0.0.4-rc1")' >ikarus.config.ss echo '(define ikarus-revision "1869")' >>ikarus.config.ss echo '(define ikarus-lib-dir "/usr/lib/i386-linux-gnu/ikarus")' >>ikarus.config.ss echo '(define target "i686-pc-linux-gnu")' >>ikarus.config.ss echo '(define wordsize 4)' >>ikarus.config.ss IKARUS_SRC_DIR=. \ IKARUS_BUILD_DIR=. \ IKARUS_FASL_DIRECTORY='' \ IKARUS_LIBRARY_PATH=.:.:./../lib \ ../src/ikarus -b ./ikarus.boot.4.prebuilt \ --r6rs-script ./makefile.ss Makefile:586: recipe for target 'ikarus.boot' failed make[2]: *** [ikarus.boot] Segmentation fault make[2]: Leaving directory '/«BUILDDIR»/ikarus-0.0.3+bzr.2010.01.26/scheme' dh_auto_build: make -j4 -C scheme returned exit code 2 debian/rules:7: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 --- End Message --- --- Begin Message --- Source: ikarus Source-Version: 0.0.3+bzr.2010.01.26-7 Done: b...@debian.org (Barak A. Pearlmutter) We believe that the bug you reported is fixed in the latest version of ikarus, 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 858...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated ikarus 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: Sun, 17 May 2020 15:19:14 +0100 Source: ikarus Architecture: source Version: 0.0.3+bzr.2010.01.26-7 Distribution: unstable Urgency: medium Maintainer: Barak A. Pearlmutter Changed-By: Barak A. Pearlmutter Closes: 858037 Changes: ikarus (0.0.3+bzr.2010.01.26-7) unstable; urgency=medium . * disable PIE on i386 (closes: #858037) * Bump debhelper from old 12 to 13. Checksums-Sha1: 4b4836c8b6de220d84fc3787e66b38a2bb194e8b 1964 ikarus_0.0.3+bzr.2010.01.26-7.dsc 19631669f9085f3a707bc23110edb81226d69760 46796 ikarus_0.0.3+bzr.2010.01.26-7.debian.tar.xz d3ed9e981fcb29f04e418c3b85f5d67b5e0e1623 5982 ikarus_0.0.3+bzr.2010.01.26-7_source.buildinfo Checksums-Sha256: 3e888c6bf9f84a6cc3417b5a2a52e3d9df4a3e61f98204f6773f92a796111fb4 1964 ikarus_0.0.3+bzr.2010.01.26-7.dsc 5143d655a4de9088ca97380171e3ac8b40a42c82546892706979329de5183bdb 46796 ikarus_0.0.3+bzr.2010.01.26-7.debian.tar.xz b852e2e48c21f829dc5404a0b26a09d740928ef7032700b217c6cdc1e50c9723 5982 ikarus_0.0.3+bzr.2010.01.26-7_source.buildinfo Files: f999afd4fc876ef73832bd158d845613 1964 lisp optional ikarus_0.0.3+bzr.2010.01.26-7.dsc 60d69bf63a332b376348105db28ba355 46796 lisp optional ikarus_0.0.3+bzr.2010.01.26-7.debian.tar.xz b6d9dcc7e5e75fdf70ff5c506935cba6 5982 lisp optional ikarus_0.0.3+bzr.2010.01.26-7_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEZPQp426hHMLZZlRvEltXR14ZDRgFAl7BT6kPHGJhcEBkZWJp YW4ub3JnAAoJEBJbV0deGQ0YzucP/R0swojf14i9fERXd+g7EXL2VfJ3eMOjTsTk yYWdQbOCSblyg+AunlLb6iyE4BSxCoKZzABtYdOKhJ9tOpzUhcp+zPBaJtzo4sDi Y/Xd9k/CPrQdBoaf+Nab6hwHIfaNC8zkImffID9fSkJV37tEItowNnIE9Lwx7hbo qGb3FWWQ/PS1nsrgqSvNnsxxEmysyrUs82Jb4hwRojnQuexIHmuxCUP1jCv5B5UH b1goVvHDxmB9QblylcGvw/n3UqLqurtbrZJHmFsnbRJOvPw0ooY9RszH3F00CgTP E7aIPLwppxMW9bWoV53vof/0EkA+3oGpnBd2BSA3bt4DhChkW8RH1LQwrln9r/hV DMlPJGFE8PuA4WK+DDtrMCsdbJ/gbjUErDp0g+vAKm6z6uIv9Ujt/Jfe0TJzILwO GedvIGqGGdxBvcPK57LiF/Vt7ASlYoIN5qoywuVf2nl1laYMVNJuTYnjfq6eBmeV vdLiKu7YlFAtAu0PDX41qs0EGyA0DNwIBtjtoMeTA91is+w+CrvtDUZVmZ+9aPkm MLGj7+bzAk7T6NGOWEh1drqHSzoP1LJ9zr7fud59vghq6n4w05Ei4psr3g3OUZ1H
Processed: Re: Bug#960752: FTBFS on arch-all, test-suite failure - conova buildd has broken "localhost"
Processing control commands: > tag -1 + ipv6 Bug #960752 [src:cockpit] FTBFS on arch-all, test-suite failure Added tag(s) ipv6. -- 960752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960257: marked as done (gsequencer FTBFS with lv2-dev 1.18.0-1)
Your message dated Sun, 17 May 2020 14:48:42 + with message-id and subject line Bug#960257: fixed in gsequencer 3.3.0-1 has caused the Debian Bug report #960257, regarding gsequencer FTBFS with lv2-dev 1.18.0-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 960257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gsequencer Version: 3.2.13-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gsequencer.html ... ags/X/machine/ags_live_lv2_bridge.c: In function 'ags_live_lv2_bridge_lv2ui_idle_timeout': ags/X/machine/ags_live_lv2_bridge.c:2001:81: error: dereferencing pointer to incomplete type 'struct _LV2UI_Idle_Interface' 2001 | retval = ((struct _LV2UI_Idle_Interface *) lv2ui_plugin->feature[0]->data)->idle(live_lv2_bridge->ui_handle[0]); | ^~ make[3]: *** [Makefile:18911: ags/X/machine/libgsequencer_la-ags_live_lv2_bridge.lo] Error 1 --- End Message --- --- Begin Message --- Source: gsequencer Source-Version: 3.3.0-1 Done: =?utf-8?q?IOhannes_m_zm=C3=B6lnig_=28Debian/GNU=29?= We believe that the bug you reported is fixed in the latest version of gsequencer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated gsequencer 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: Sun, 17 May 2020 16:12:49 +0200 Source: gsequencer Architecture: source Version: 3.3.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 960257 Changes: gsequencer (3.3.0-1) unstable; urgency=medium . [ Joël Krähemann ] * New upstream version 3.3.0 (Closes: #960257) * Update symbols files Checksums-Sha1: 109de5689059704cbeb95ac61bb2fadedd7883d2 3816 gsequencer_3.3.0-1.dsc eb53fd4feb244537ab1575b9b3cd42a873ff9f4b 7027780 gsequencer_3.3.0.orig.tar.gz 49e791bd41df641850a7a5711997a75ae3b1c8e3 659 gsequencer_3.3.0.orig.tar.gz.asc 9884019279fe538c2b3f403dca353183409d4602 40184 gsequencer_3.3.0-1.debian.tar.xz Checksums-Sha256: d52bc3f1b92c4672ff9fd9a2557e6b6db9e7483522603a5c6c3b717f0c9f6d60 3816 gsequencer_3.3.0-1.dsc eebf6e0069e0b083fadceb053c2d6e2638785d11d4c8e622817e5d16038029d0 7027780 gsequencer_3.3.0.orig.tar.gz 84d874b0f85cc60e7846c480963075f4c8b6b41873af47bfa7489d54d26de6f7 659 gsequencer_3.3.0.orig.tar.gz.asc 23e7dae55951eaa0502cac1aed6f042e9f611fc4fd06fd6bbce8990bc604e1fe 40184 gsequencer_3.3.0-1.debian.tar.xz Files: 2ac79f7676566c126d75268d129fb9b0 3816 sound optional gsequencer_3.3.0-1.dsc 59424467dd041afc4d322dd5609e9a48 7027780 sound optional gsequencer_3.3.0.orig.tar.gz 1900ac67c2b8af7bbc134a44bc7f3de3 659 sound optional gsequencer_3.3.0.orig.tar.gz.asc 157a55798cbac3a80d67c6b6c5d6fa48 40184 sound optional gsequencer_3.3.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAl7BS4AWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+EKlD/9SIqPOxkBw2pkeN+TgTgrGmJU+ zBIFUE4IkmcJTyLC9Y3d0e2/qe9CJY591IUZkmzky95QYpauv0IJJ7gGpbD90OeW Q8q9bzmBrIwanBEw3H4EkFhtzLQw3frAhjZEY67LipuV67I47kPMzevETI6r6w9E X+qCIOiUgQJz1PTEjPOIWr73s4aw84cZ0avaR4faAq7dyUhN8wfx63QBkkotA4gS EDGMkuGW5TpNugvQo3ecDOpWpu7JsMHLUCFC7dcrqtVGnbEC7vd3xQXfIponNlbK THVVHaPupCmAQH4xxqaAh13irmKtvfbQKrBUwFt7e1KE8Sg8UZeUufz4dWBU+FML rdF/wUGGbhiom2I3/C6B8X4FanNaGfeRr6a9gBndALGPSVUifGYTFMLeDG9bm4MJ i+i8SvDg7Gx3xeKdcfsb21AvCOQ3zcEBakEdq/UW6yqWz7onKtapWnYNhwXbbZBA rJ3PFzyd0o8U00YgGnZaCF+9cIeZ3U6sQbyOInVDyTBF3sASUpJLn9bsvK3pWBi6 9w74vQ4HSKh/J/IcxjT3NjRq0l9gQeMqQSjEj5/itckNokYFlzdeaTY061Q67J6d zJIED7VDeFzECoY50ejnGpXSA7S5u829Xt7UHuZG3GHlK6rDVCQV+ZI2u2dI/N/F 00A1HYVEZdkAzxcFRA== =KRQ/ -END PGP SIGNATURE End Message ---
Bug#938441: marked as done (schedule: Python2 removal in sid/bullseye)
Your message dated Sun, 17 May 2020 14:36:06 + with message-id and subject line Bug#938441: fixed in schedule 0.6.0-1 has caused the Debian Bug report #938441, regarding schedule: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 938441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938441 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:schedule Version: 0.3.2-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:schedule If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: schedule Source-Version: 0.6.0-1 Done: Federico Ceratto We believe that the bug you reported is fixed in the latest version of schedule, 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 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Federico Ceratto (supplier of updated schedule 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: Sun, 17 May 2020 14:53:52 +0100 Source: schedule Architecture: source Version: 0.6.0-1 Distribution: unstable Urgency: medium Maintainer: Donncha O'Cearbhaill Changed-By: Federico Ceratto Closes: 938441 Changes: schedule (0.6.0-1) unstable; urgency=medium . * New upstream release * Drop Python 2 (Closes: #938441) Checksums-Sha1: 708b7245f8dedfc65948277827d772fae072e292 2000 schedule_0.6.0-1.dsc f7895fe6cb22f0e45c00989d4aba3cecdbbeb49e 12300 schedule_0.6.0.orig.tar.gz 21ac3e2943c459f411bae51d562a47f237ce0489 2224 schedule_0.6.0-1.debian.tar.xz c2f28ec00e761c88af859cd5adf819b0189dc645 6047 schedule_0.6.0-1_amd64.buildinfo Checksums-Sha256: c0ca7ba962aa1fbcf819c4a16a5723faefdd62a86457b1fb1877cc752902db20 2000 schedule_0.6.0-1.dsc f9fb5181283de4db6e701d476dd01b6a3dd81c38462a54991ddbb9d26db857c9 12300 schedule_0.6.0.orig.tar.gz 01082c2d1179e208ded64b6985d9f3918a716cbaa0982d46f6f8091cfc4c42dd 2224
Processed: Bug#952285 marked as pending in prometheus-mongodb-exporter
Processing control commands: > tag -1 pending Bug #952285 [src:prometheus-mongodb-exporter] prometheus-mongodb-exporter: FTBFS: src/github.com/dcu/mongodb_exporter/mongodb_exporter.go:84:13: undefined: prometheus.Handler Added tag(s) pending. -- 952285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#952285: marked as pending in prometheus-mongodb-exporter
Control: tag -1 pending Hello, Bug #952285 in prometheus-mongodb-exporter 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/go-team/packages/prometheus-mongodb-exporter/-/commit/251061951fec95cd618c531357c3abaf812f09ab fix prometheus httphandler (Closes: #952285) (this message was generated automatically) -- Greetings https://bugs.debian.org/952285
Bug#936557: freeorion: Python2 removal in sid/bullseye
Am 17.05.20 um 15:36 schrieb Fedja Beader via Pkg-games-devel: > Why does this bug still exist? > > I was able to build headless Freeorion on Devuan with Python 3 just by > changing the control file (see > https://framagit.org/specing/debian-freeorion/-/commit/948beb224601838163bf7c9bea4d8bcf677dcb8d). > It seems that Freeorion migrated from Python 2 a long time ago? I suggest you check your package again and try to play the game with only Python 3 installed. Freeorion 0.4.9 is still Python 2 only, the next version will support Python 3 and then we can close this bug report. Regards, Markus signature.asc Description: OpenPGP digital signature
Processed: severity of 959236 is grave
Processing commands for cont...@bugs.debian.org: > severity 959236 grave Bug #959236 [ifenslave] Bringing up a bond results in an infinite loop Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 959236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960082: marked as done (nautilus extension fails to load: libeiciel-nautilus.so: undefined symbol: nautilus_module_initialize)
Your message dated Sun, 17 May 2020 12:33:37 + with message-id and subject line Bug#960082: fixed in eiciel 0.9.12.1-3 has caused the Debian Bug report #960082, regarding nautilus extension fails to load: libeiciel-nautilus.so: undefined symbol: nautilus_module_initialize 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.) -- 960082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: eiciel Version: 0.9.12.1-2 Severity: serious The nautilus extension provided by eiciel no longer works with nautilus 3.36. Starting nautilus from the command line: ** (org.gnome.Nautilus:7715): WARNING **: 08:07:07.542: 'nautilus_module_initialize': /usr/lib/x86_64-linux-gnu/nautilus/extensions-3.0/libeiciel-nautilus.so: undefined symbol: nautilus_module_initialize Not sure if this a breakage in nautilus or if eiciel needs to be updated. Filing against eiciel for now, but would welcome feedback from the nautilus maintainers. Regards, Michael -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND 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: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages eiciel depends on: ii libacl1 2.2.53-8 ii libatkmm-1.6-1v5 2.28.0-2 ii libc62.30-7 ii libcairomm-1.0-1v5 1.12.2-4 ii libgcc-s110.1.0-1 ii libglib2.0-0 2.64.2-1 ii libglibmm-2.4-1v52.64.2-1 ii libgtk-3-0 3.24.20-1 ii libgtkmm-3.0-1v5 3.24.2-1 ii libnautilus-extension1a 3.36.2-2 ii libsigc++-2.0-0v52.10.2-1 ii libstdc++6 10.1.0-1 Versions of packages eiciel recommends: ii nautilus 3.36.2-2 ii yelp 3.36.0-1 eiciel suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: eiciel Source-Version: 0.9.12.1-3 Done: Michael Biebl We believe that the bug you reported is fixed in the latest version of eiciel, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl (supplier of updated eiciel 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: Sun, 17 May 2020 14:17:36 +0200 Source: eiciel Architecture: source Version: 0.9.12.1-3 Distribution: unstable Urgency: medium Maintainer: Michael Biebl Changed-By: Michael Biebl Closes: 923108 960082 Changes: eiciel (0.9.12.1-3) unstable; urgency=medium . * Avoid C++ name mangling for Nautilus extension symbols (Closes: #960082) * Don't hardcode pkg-config in configure.ac (Closes: #923108) Checksums-Sha1: 913efd30f5ea24569a56c9db8877db7eaf2dd4b3 1946 eiciel_0.9.12.1-3.dsc efa7ebcc914ebd392f88af7f95db76683b6905fa 5800 eiciel_0.9.12.1-3.debian.tar.xz fafda93a08619675dfb4729a4571a2eaf289e8a2 14010 eiciel_0.9.12.1-3_source.buildinfo Checksums-Sha256: ef865d73b0b3d0996351b67654386ecd584dc1f6767894ce0f2a7d4f14413272 1946 eiciel_0.9.12.1-3.dsc 9c283af4e74199688b4d2c925ab9ecef5a85fb7a1d1464e8cb1365b4be1ce7e3 5800 eiciel_0.9.12.1-3.debian.tar.xz 82f5f44ac792f469c75f4ece339ca85512668dcb3e453f5459cbcf1c19d435bf 14010 eiciel_0.9.12.1-3_source.buildinfo Files: d458ff4e5855dd60b014581a37143d7d 1946 gnome optional eiciel_0.9.12.1-3.dsc ac3b43b8a0466b5fd235f79f9ff8118a 5800 gnome optional eiciel_0.9.12.1-3.debian.tar.xz 95684911194fd807dc5415363dc3d1dd 14010 gnome optional eiciel_0.9.12.1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAl7BLHEACgkQauHfDWCP Ityx+g/+LSHKxNSDWwJ/gDGrFrocPdLYLoyKFSPdrF2iRzqr2UmAYDSdpb1C+wiK HjPuF88h8I8+ExNR6/9inRlPWPkWtZg/Yw9A+N5NFZhu/eVbRNDb4N27MP/IpJBu eg9qCsRYBo6wJ8vrdook2ObcYs+CvPhY/6Z3AtsG15KcOCJCs1JXCLhLBqiAF8N2 ufQsDFofsxU+siliBDKs+a+KOsy27TwwDS72QGTYOSAwsn2l6bAi35p6wf1yh0wR
Processed: Bug#960082 marked as pending in eiciel
Processing control commands: > tag -1 pending Bug #960082 [eiciel] nautilus extension fails to load: libeiciel-nautilus.so: undefined symbol: nautilus_module_initialize Added tag(s) pending. -- 960082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960082 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960082: marked as pending in eiciel
Control: tag -1 pending Hello, Bug #960082 in eiciel 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/debian/eiciel/-/commit/3a191ba7bb168a721e2c0cb90f016a3e0c281097 Avoid C++ name mangling for Nautilus extension symbols Closes: #960082 (this message was generated automatically) -- Greetings https://bugs.debian.org/960082
Processed: tagging 925676
Processing commands for cont...@bugs.debian.org: > tags 925676 + ftbfs Bug #925676 [src:faumachine] faumachine: ftbfs with GCC-9 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 925676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#858037: ikarus FTBFS on i386: recipe for target 'ikarus.boot' failed (Segmentation fault)
On Sat, Apr 22, 2017 at 08:35:01PM +0100, Barak A. Pearlmutter wrote: > Well, vicare is a sort-of fork/continuation of ikarus. > If that compiles on i386, we could transition. > Or, since this problem is i386-only, and I'd imagine most users are > amd64, could just stop supporting i386. The Ubuntu patch (linked from tracker.debian.org) disables PIE on i386, which fixes the build. cu Adrian
Bug#960828: marked as done (eclipse-jdt-debug binary upload rejected)
Your message dated Sun, 17 May 2020 11:03:30 + with message-id and subject line Bug#960828: fixed in eclipse-jdt-debug 4.15-2 has caused the Debian Bug report #960828, regarding eclipse-jdt-debug binary upload rejected 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.) -- 960828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: eclipse-jdt-debug Version: 4.15-1 Severity: serious Tags: ftbfs bunk@coccia:~$ cat /srv/ftp-master.debian.org/queue/reject/eclipse-jdt-debug_4.15-1_all.changes.reason Version check failed: Your upload included the binary package libeclipse-jdt-debug-ui-java, version 3.10.300+eclipse4.12-3, for all, however testing already has version 3.10.300+eclipse4.12-3. Uploads to unstable must have a higher version than present in testing. bunk@coccia:~$ --- End Message --- --- Begin Message --- Source: eclipse-jdt-debug Source-Version: 4.15-2 Done: Emmanuel Bourg We believe that the bug you reported is fixed in the latest version of eclipse-jdt-debug, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated eclipse-jdt-debug 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: Sun, 17 May 2020 12:51:10 +0200 Source: eclipse-jdt-debug Architecture: source Version: 4.15-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 960828 Changes: eclipse-jdt-debug (4.15-2) unstable; urgency=medium . * Fixed the version of libeclipse-jdt-debug-ui-java (Closes: #960828) Checksums-Sha1: e07446fe24ae4462a96b44de2758a85dc1bcc30a 3120 eclipse-jdt-debug_4.15-2.dsc f47f8f0321dc5cf804ad10077931420251460648 7640 eclipse-jdt-debug_4.15-2.debian.tar.xz 9b12d13a4950f3a3d402373364d954eff023404b 11428 eclipse-jdt-debug_4.15-2_source.buildinfo Checksums-Sha256: 1f7cdad20a51f43a81854c3cc5baf63c1ddaf7e8bf761ab97f2f2b2d7711d733 3120 eclipse-jdt-debug_4.15-2.dsc 0ea67ec1944c3c2eec7e0b06d3223ef1c75504f710d2e9eaa8b5b867f0466104 7640 eclipse-jdt-debug_4.15-2.debian.tar.xz 325b8ee2433a63df84f92ab89bd8c23c1978458a690357b1aafd924e503717e5 11428 eclipse-jdt-debug_4.15-2_source.buildinfo Files: d969f37338d2769f8f36cbfcda50d231 3120 java optional eclipse-jdt-debug_4.15-2.dsc 338f9c93043c7856643221134f092a27 7640 java optional eclipse-jdt-debug_4.15-2.debian.tar.xz 5647d1918bf254ca314d166ba04954c7 11428 java optional eclipse-jdt-debug_4.15-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAl7BF6ASHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCs1i0P+gNWf1U+nSBG4s26QaO7Gh27Kwjw9mdK FxQl08nAr/rO17CE4k5ffsfOP9oii63SOmLIQn/HdBg4S3JYVsHyVkh3oUwpCykr qAueaSyLA3x01UIAes1fIHSViqaUCSMyQ1aQk5GA6KnwgdXTZNkIOXiIHul3oWmn S5vALqiebjEHDDeBvzsX4Woro5KmmrgylDFxsUT8a6SCqK+N72kRhmMNuERYNHZm J2FShNoFYRXrHxIJBvAIKFGEnJNtMHS4hMejtiaKZOhqNdfJ4nsCAwurwxuPribk 27fFcpNWGhl6n7UMU05EiwWNT3XcpQRitFjV5oTl1IfMKuZ/JYoIDVGggPN59ERu gZO+zr+pjNdhp1u1NCMIguln8hRR9k6NdG3fotwsDF51Ewco3s/RNaFge2x8oxT3 LPNrd1Q88y3it1/1p20xusIpQjn8Sc3puaI/qw8rIZt1JEwOJmc6H4Cb+kjIkPZL biOORJ9ORjnBbs1D1gek3m0Wb8fBRrVDmwVR608WYeyn7gt8k/c8vGiNJthj9CA/ TFtEl/d1JAzEyyPDJVBXs70isfcYA4rZrOwyXObSDrnBqO9zhDnGmPQCA1Hmg42H vqa3aHSbh0CeDMJZrc3U2+ug3yCplzXfscnybwmyXfw8XanSeQCOVlgh4EhudDd9 wauLeaBh0WfA =ULuG -END PGP SIGNATURE End Message ---
Bug#960828: marked as pending in eclipse-jdt-debug
Control: tag -1 pending Hello, Bug #960828 in eclipse-jdt-debug 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/eclipse-jdt-debug/-/commit/57553b94f695ade292e3caa2afbdbdbb4b0b20de Fixed the version of libeclipse-jdt-debug-ui-java (Closes: #960828) (this message was generated automatically) -- Greetings https://bugs.debian.org/960828
Processed: Bug#960828 marked as pending in eclipse-jdt-debug
Processing control commands: > tag -1 pending Bug #960828 [src:eclipse-jdt-debug] eclipse-jdt-debug binary upload rejected Added tag(s) pending. -- 960828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959737: marked as done (libdap: autopkgtest regression)
Your message dated Sun, 17 May 2020 10:33:42 + with message-id and subject line Bug#959737: fixed in libdap 3.20.6-2 has caused the Debian Bug report #959737, regarding libdap: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 959737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdap Version: 3.20.6-1 Severity: serious libdap fails to migrate due to a regression of its autopkgtests. See https://ci.debian.net/data/autopkgtest/testing/amd64/libd/libdap/5157447/log.gz for details. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: libdap Source-Version: 3.20.6-2 Done: Alastair McKinstry We believe that the bug you reported is fixed in the latest version of libdap, 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 959...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated libdap 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: Sun, 17 May 2020 10:42:27 +0100 Source: libdap Architecture: source Version: 3.20.6-2 Distribution: unstable Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Closes: 959737 Changes: libdap (3.20.6-2) unstable; urgency=medium . * Test depends on libdap-dev. Closes: #959737 Checksums-Sha1: 944dc4a3b3f351e80804a0f1514e6ae62a942549 2359 libdap_3.20.6-2.dsc 17ac401b826b79a66c6dc9b61c1fe683bf18dbe6 13580 libdap_3.20.6-2.debian.tar.xz Checksums-Sha256: 1d4745f610ea71f1cf69d61a75b20f1580e13e0adef0187573cfbbd514609609 2359 libdap_3.20.6-2.dsc ed7cc46876b33ce280758694e0aa41447b79594b0c457e8d0aef4a40b71ea7a0 13580 libdap_3.20.6-2.debian.tar.xz Files: 18a8233ba8a214961cdab50842b771de 2359 utils optional libdap_3.20.6-2.dsc 7a2b77558ee81b8d47a6f79a1ac07b79 13580 utils optional libdap_3.20.6-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl7BDv0ACgkQy+a7Tl2a 06XkjA//RTUgKhQ8TI1sQj5kNhOmoT1jTOceCki5iFcFduFk/tTmzn+l9eae/XHK EFK1m6vgPzJKo1akjd28qsTcOjpWhECNbFlvjwTZhAj2VneezzopQisV+CVI+ddA Qn0vEwP13BTevMCzydILgIC5iMgkCZ0IAUknrnINoUtm0rBIGkjDIDkO4/0/hY4j AXR3fd58BGxTj2a3OyyKpsL5t1o9BJ+YAx6m/FfNec4K+91uRtRzJ+ztf1RIvKhw Q99ikRD1w45Jj09dFID8rkl62Jdnq99AgkSAvF9D0OpghMtJS4pfTiaHncbtwiFL ovyLPxHjmWgl6UJMD8n/RMCDISOEZajGVFelnhNIgaVT07TcnKpyrfVmkTiSzHDJ dljrjf9w4Y5uxmZBjx+XBsDY7FZX9qUDp9R0IHqYovcX61kYBllN9T0ODCwIgTXG uttPDamBCur3FU58XZmPXUraPe2DxtpdVXKQD/Ltbj0J6RYsFEHTfOcV5azN0qXl pLt6wgYvRL0DWC2TOlu92eWx90lcKkGzYQDSSQI2ki1Y+HiYA5jhn69oinFehwU/ fmMFbK0g+9I21gjjvoXEGD2+Q8V8YoMq/h2loCgxn+NO744IU2JzfPSiKMwGZLWU 7oqjVJEh2IvWQdOead+dl/B18xz3v6ypoQBqlJPE9m/6k5i+fDc= =wWUE -END PGP SIGNATURE End Message ---
Bug#945467: Fix available (fwd)
you can look also at the CI, now that it works :) https://salsa.debian.org/science-team/veusz/pipelines/137494 Cheers Frederic
Processed: bug 955316 is forwarded to Thomas Pedersen
Processing commands for cont...@bugs.debian.org: > forwarded 955316 Thomas Pedersen Bug #955316 [src:r-cran-svglite] r-cran-svglite autopkgtest fails: Error: symbol font Changed Bug forwarded-to-address to 'Thomas Pedersen ' from 'Lionel Henry '. > thanks Stopping processing here. Please contact me if you need assistance. -- 955316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955316 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 958105 is forwarded to https://github.com/MaxKellermann/ferm/issues/63
Processing commands for cont...@bugs.debian.org: > forwarded 958105 https://github.com/MaxKellermann/ferm/issues/63 Bug #958105 [ferm] ferm: v2.5 broke @ipfilter(), resulting in deferred=ARRAY(0x55b7a9219368) errors Set Bug forwarded-to-address to 'https://github.com/MaxKellermann/ferm/issues/63'. > thanks Stopping processing here. Please contact me if you need assistance. -- 958105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#945467: Fix available (fwd)
Hi Andreas Thanks very much for looking at this. I forgot to update my build environment and something has changed in the extension module naming since then. I'm sorry about that. I've put in a fix to the repo, and checked it builds in pbuilder on an up to date sid. Thanks again Jeremy On 16/05/2020 21:23, Andreas Tille wrote: Hi Jeremy, please make sure to inject pristine-tar (according to Debian Science policy). I did so now. Unfortunately the package does not build in a pbuilder chroot: ... dh_sip3 make[1]: Leaving directory '/build/veusz-3.2.1' dh_install -O--buildsystem=pybuild dh_install: warning: Cannot find (any matches for) "usr/lib/python3*/*-packages/veusz/helpers/*.cpython-[0-9]*[!d]m-*.so" (tried in ., debian/tmp) dh_install: warning: python3-veusz.helpers missing files: usr/lib/python3*/*-packages/veusz/helpers/*.cpython-[0-9]*[!d]m-*.so dh_install: error: missing files, aborting make: *** [debian/rules:23: binary] Error 25 ... Kind regards Andreas. On Sat, May 16, 2020 at 03:05:10PM +0300, Adrian Bunk wrote: Andreas, could you sponssor that one? You already sponsored the latest 2 uploads of this package. Thanks Adrian - Forwarded message from Jeremy Sanders - Date: Fri, 17 Apr 2020 09:10:00 +0200 From: Jeremy Sanders To: 945...@bugs.debian.org Subject: Bug#945467: Fix available Resent-From: Jeremy Sanders Resent-To: debian-bugs-d...@lists.debian.org Resent-Date: Fri, 17 Apr 2020 07:21:01 + I've updated the version control to have the latest version of Veusz, 3.2.1, which should fix this bug: https://salsa.debian.org/science-team/veusz It would be great if a developer with permissions could have a look and consider uploading it. Thanks Jeremy - End forwarded message -
Bug#956694: purify: FTBFS with spdlog 1.5.0
Hi Sebastian, if spdlog does not ship with internal headersin Debian, shouldn't that define be already set internally in spdlog? Cheers Ole On 10.05.20 17:52, Sebastian Ramacher wrote: > On 2020-05-10 17:45:00 +0200, Sebastian Ramacher wrote: >> On 2020-04-26 10:49:31 +0200, Ole Streicher wrote: >>> Control: affects -1 src:purify >>> >>> This now also affects the "purify" package, which is supposed to be >>> rebuilt during the auto-casacore transition. >> As far as I can tell, spdlog's pkg-config file adds >> -DSPDLOG_FMT_EXTERNAL. With that define set, spdlog would use the >> correct include files. However, purify seems to ignore these flag and >> thus fails to build. > … and spdlog's cmake config also contains this define. > > Best
Bug#960827: marked as done (nomad FTBFS: cannot find package "github.com/docker/docker/rootless")
Your message dated Sun, 17 May 2020 08:33:34 + with message-id and subject line Bug#960827: fixed in docker.io 19.03.7+dfsg1-3 has caused the Debian Bug report #960827, regarding nomad FTBFS: cannot find package "github.com/docker/docker/rootless" 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.) -- 960827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nomad Version: 0.10.5+dfsg1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nomad.html ... cd _build && go install -trimpath -v -p 15 -a -tags "release ui nonvidia" github.com/hashicorp/nomad github.com/hashicorp/nomad/acl github.com/hashicorp/nomad/api github.com/hashicorp/nomad/api/contexts github.com/hashicorp/nomad/api/internal/testutil github.com/hashicorp/nomad/api/internal/testutil/discover github.com/hashicorp/nomad/api/internal/testutil/freeport github.com/hashicorp/nomad/client github.com/hashicorp/nomad/client/allocdir github.com/hashicorp/nomad/client/allocdir/input github.com/hashicorp/nomad/client/allochealth github.com/hashicorp/nomad/client/allocrunner github.com/hashicorp/nomad/client/allocrunner/interfaces github.com/hashicorp/nomad/client/allocrunner/state github.com/hashicorp/nomad/client/allocrunner/taskrunner github.com/hashicorp/nomad/client/allocrunner/taskrunner/getter github.com/hashicorp/nomad/client/allocrunner/taskrunner/interfaces github.com/hashicorp/nomad/client/allocrunner/taskrunner/restarts github.com/hashicorp/nomad/client/allocrunner/taskrunner/state github.com/hashicorp/nomad/client/allocrunner/taskrunner/template github.com/hashicorp/nomad/client/allocwatcher github.com/hashicorp/nomad/client/config github.com/hashicorp/nomad/client/consul github.com/hashicorp/nomad/client/devicemanager github.com/hashicorp/nomad/client/devicemanager/state github.com/hashicorp/nomad/client/fingerprint github.com/hashicorp/nomad/client/interfaces github.com/hashicorp/nomad/client/lib/fifo github.com/hashicorp/nomad/client/lib/nsutil github.com/hashicorp/nomad/client/lib/streamframer github.com/hashicorp/nomad/client/logmon github.com/hashicorp/nomad/client/logmon/logging github.com/hashicorp/nomad/client/logmon/proto github.com/hashicorp/nomad/client/pluginmanager github.com/hashicorp/nomad/client/pluginmanager/drivermanager github.com/hashicorp/nomad/client/pluginmanager/drivermanager/state github.com/hashicorp/nomad/client/servers github.com/hashicorp/nomad/client/state github.com/hashicorp/nomad/client/stats github.com/hashicorp/nomad/client/structs github.com/hashicorp/nomad/client/taskenv github.com/hashicorp/nomad/client/testutil github.com/hashicorp/nomad/client/vaultclient github.com/hashicorp/nomad/command github.com/hashicorp/nomad/command/agent github.com/hashicorp/nomad/command/agent/consul github.com/hashicorp/nomad/command/agent/monitor github.com/hashicorp/nomad/command/agent/pprof github.com/hashicorp/nomad/devices/gpu/nvidia github.com/hashicorp/nomad/devices/gpu/nvidia/cmd github.com/hashicorp/nomad/devices/gpu/nvidia/nvml github.com/hashicorp/nomad/drivers/docker github.com/hashicorp/nomad/drivers/docker/cmd github.com/hashicorp/nomad/drivers/docker/docklog github.com/hashicorp/nomad/drivers/docker/docklog/proto github.com/hashicorp/nomad/drivers/docker/util github.com/hashicorp/nomad/drivers/exec github.com/hashicorp/nomad/drivers/java github.com/hashicorp/nomad/drivers/mock github.com/hashicorp/nomad/drivers/qemu github.com/hashicorp/nomad/drivers/rawexec github.com/hashicorp/nomad/drivers/rkt github.com/hashicorp/nomad/drivers/shared/eventer github.com/hashicorp/nomad/drivers/shared/executor github.com/hashicorp/nomad/drivers/shared/executor/proto github.com/hashicorp/nomad/helper github.com/hashicorp/nomad/helper/args github.com/hashicorp/nomad/helper/boltdd github.com/hashicorp/nomad/helper/codec github.com/hashicorp/nomad/helper/constraints/semver github.com/hashicorp/nomad/helper/discover github.com/hashicorp/nomad/helper/escapingio github.com/hashicorp/nomad/helper/fields github.com/hashicorp/nomad/helper/flag-helpers github.com/hashicorp/nomad/helper/flatmap github.com/hashicorp/nomad/helper/freeport github.com/hashicorp/nomad/helper/gated-writer github.com/hashicorp/nomad/helper/logging github.com/hashicorp/nomad/helper/noxssrw github.com/hashicorp/nomad/helper/pluginutils/catalog github.com/hashicorp/nomad/helper/pluginutils/grpcutils
Bug#960656: sdpb: FTBFS on mipsel
On Fri, 15 May 2020 10:10:19 +0200 Sebastian Ramacher wrote: > sdpb failed to build on mipsel while rebuilding for the tinyxml2 transition: > https://buildd.debian.org/status/fetch.php?pkg=sdpb=mipsel=1.0-3%2Bb5=1589492907=0 sdpb has been removed from mipsel (#960747) to unblock the transition. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#846667: [rt.cpan.org #119351] occasional failures of t/poe_loop_event/wheel_run.t
https://rt.cpan.org/Ticket/Display.html?id=119351 > Dear Maintainer, The Debian perl group is reviewing packages with bugs which make them un-releasable; in particular when they are not heavily used by Debian users. We would like to remove such modules from Debian if we don't think they are likely to be fixed. POE::Loop::Event is one such module, owing to this bug, and we would like to know whether you have any plans to look at the bug in the foreseeable future before we remove the package from Debian. If we don't hear anything we will remove the package from Debian at some point, though not earlier than June 8. This of course does not affect the standing of your module on CPAN. Thank you for maintaining this module so far!
Processed: affects 960827
Processing commands for cont...@bugs.debian.org: > affects 960827 src:nomad Bug #960827 [src:docker.io] nomad FTBFS: cannot find package "github.com/docker/docker/rootless" Added indication that 960827 affects src:nomad > thanks Stopping processing here. Please contact me if you need assistance. -- 960827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 960827, reassign 960827 to src:docker.io, found 960827 in 19.03.7+dfsg1-2
Processing commands for cont...@bugs.debian.org: > tags 960827 + pending Bug #960827 [src:nomad] nomad FTBFS: cannot find package "github.com/docker/docker/rootless" Added tag(s) pending. > reassign 960827 src:docker.io Bug #960827 [src:nomad] nomad FTBFS: cannot find package "github.com/docker/docker/rootless" Bug reassigned from package 'src:nomad' to 'src:docker.io'. No longer marked as found in versions nomad/0.10.5+dfsg1-1. Ignoring request to alter fixed versions of bug #960827 to the same values previously set > found 960827 19.03.7+dfsg1-2 Bug #960827 [src:docker.io] nomad FTBFS: cannot find package "github.com/docker/docker/rootless" Marked as found in versions docker.io/19.03.7+dfsg1-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 960827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960827: nomad FTBFS: cannot find package "github.com/docker/docker/rootless"
On Sunday, 17 May 2020 4:22:07 PM AEST Adrian Bunk wrote: > src/github.com/docker/docker/registry/registry.go:22:2: cannot find > package "github.com/docker/docker/rootless" in any of: > /build/1st/nomad-0.10.5+dfsg1/_build/src/github.com/docker/docker/vendor/g > ithub.com/docker/docker/rootless (vendor tree) Yes, yes... Already fixed: https://salsa.debian.org/docker-team/docker/-/commit/4e4e7f42 -- Cheers, Dmitry Smirnov. --- A Sunday school is a prison in which children do penance for the evil conscience of their parents. -- H. L. Mencken signature.asc Description: This is a digitally signed message part.
Bug#952326: libcrcutil: diff for NMU version 1.0-5.2
On Sunday, 17 May 2020 3:30:46 PM AEST Adrian Bunk wrote: > I've prepared an NMU for libcrcutil (versioned as 1.0-5.2) and uploaded > it to DELAYED/15. Please feel free to tell me if I should cancel it. Thank you for preparing this NMU. Much appreciated. -- Cheers, Dmitry Smirnov. --- The cure for the evils of democracy is more democracy. -- H. L. Mencken signature.asc Description: This is a digitally signed message part.
Bug#960828: eclipse-jdt-debug binary upload rejected
Source: eclipse-jdt-debug Version: 4.15-1 Severity: serious Tags: ftbfs bunk@coccia:~$ cat /srv/ftp-master.debian.org/queue/reject/eclipse-jdt-debug_4.15-1_all.changes.reason Version check failed: Your upload included the binary package libeclipse-jdt-debug-ui-java, version 3.10.300+eclipse4.12-3, for all, however testing already has version 3.10.300+eclipse4.12-3. Uploads to unstable must have a higher version than present in testing. bunk@coccia:~$
Bug#960827: nomad FTBFS: cannot find package "github.com/docker/docker/rootless"
Source: nomad Version: 0.10.5+dfsg1-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nomad.html ... cd _build && go install -trimpath -v -p 15 -a -tags "release ui nonvidia" github.com/hashicorp/nomad github.com/hashicorp/nomad/acl github.com/hashicorp/nomad/api github.com/hashicorp/nomad/api/contexts github.com/hashicorp/nomad/api/internal/testutil github.com/hashicorp/nomad/api/internal/testutil/discover github.com/hashicorp/nomad/api/internal/testutil/freeport github.com/hashicorp/nomad/client github.com/hashicorp/nomad/client/allocdir github.com/hashicorp/nomad/client/allocdir/input github.com/hashicorp/nomad/client/allochealth github.com/hashicorp/nomad/client/allocrunner github.com/hashicorp/nomad/client/allocrunner/interfaces github.com/hashicorp/nomad/client/allocrunner/state github.com/hashicorp/nomad/client/allocrunner/taskrunner github.com/hashicorp/nomad/client/allocrunner/taskrunner/getter github.com/hashicorp/nomad/client/allocrunner/taskrunner/interfaces github.com/hashicorp/nomad/client/allocrunner/taskrunner/restarts github.com/hashicorp/nomad/client/allocrunner/taskrunner/state github.com/hashicorp/nomad/client/allocrunner/taskrunner/template github.com/hashicorp/nomad/client/allocwatcher github.com/hashicorp/nomad/client/config github.com/hashicorp/nomad/client/consul github.com/hashicorp/nomad/client/devicemanager github.com/hashicorp/nomad/client/devicemanager/state github.com/hashicorp/nomad/client/fingerprint github.com/hashicorp/nomad/client/interfaces github.com/hashicorp/nomad/client/lib/fifo github.com/hashicorp/nomad/client/lib/nsutil github.com/hashicorp/nomad/client/lib/streamframer github.com/hashicorp/nomad/client/logmon github.com/hashicorp/nomad/client/logmon/logging github.com/hashicorp/nomad/client/logmon/proto github.com/hashicorp/nomad/client/pluginmanager github.com/hashicorp/nomad/client/pluginmanager/drivermanager github.com/hashicorp/nomad/client/pluginmanager/drivermanager/state github.com/hashicorp/nomad/client/servers github.com/hashicorp/nomad/client/state github.com/hashicorp/nomad/client/stats github.com/hashicorp/nomad/client/structs github.com/hashicorp/nomad/client/taskenv github.com/hashicorp/nomad/client/testutil github.com/hashicorp/nomad/client/vaultclient github.com/hashicorp/nomad/command github.com/hashicorp/nomad/command/agent github.com/hashicorp/nomad/command/agent/consul github.com/hashicorp/nomad/command/agent/monitor github.com/hashicorp/nomad/command/agent/pprof github.com/hashicorp/nomad/devices/gpu/nvidia github.com/hashicorp/nomad/devices/gpu/nvidia/cmd github.com/hashicorp/nomad/devices/gpu/nvidia/nvml github.com/hashicorp/nomad/drivers/docker github.com/hashicorp/nomad/drivers/docker/cmd github.com/hashicorp/nomad/drivers/docker/docklog github.com/hashicorp/nomad/drivers/docker/docklog/proto github.com/hashicorp/nomad/drivers/docker/util github.com/hashicorp/nomad/drivers/exec github.com/hashicorp/nomad/drivers/java github.com/hashicorp/nomad/drivers/mock github.com/hashicorp/nomad/drivers/qemu github.com/hashicorp/nomad/drivers/rawexec github.com/hashicorp/nomad/drivers/rkt github.com/hashicorp/nomad/drivers/shared/eventer github.com/hashicorp/nomad/drivers/shared/executor github.com/hashicorp/nomad/drivers/shared/executor/proto github.com/hashicorp/nomad/helper github.com/hashicorp/nomad/helper/args github.com/hashicorp/nomad/helper/boltdd github.com/hashicorp/nomad/helper/codec github.com/hashicorp/nomad/helper/constraints/semver github.com/hashicorp/nomad/helper/discover github.com/hashicorp/nomad/helper/escapingio github.com/hashicorp/nomad/helper/fields github.com/hashicorp/nomad/helper/flag-helpers github.com/hashicorp/nomad/helper/flatmap github.com/hashicorp/nomad/helper/freeport github.com/hashicorp/nomad/helper/gated-writer github.com/hashicorp/nomad/helper/logging github.com/hashicorp/nomad/helper/noxssrw github.com/hashicorp/nomad/helper/pluginutils/catalog github.com/hashicorp/nomad/helper/pluginutils/grpcutils github.com/hashicorp/nomad/helper/pluginutils/hclspecutils github.com/hashicorp/nomad/helper/pluginutils/hclutils github.com/hashicorp/nomad/helper/pluginutils/loader github.com/hashicorp/nomad/helper/pluginutils/singleton github.com/hashicorp/nomad/helper/pool github.com/hashicorp/nomad/helper/stats github.com/hashicorp/nomad/helper/testlog github.com/hashicorp/nomad/helper/testtask github.com/hashicorp/nomad/helper/tlsutil github.com/hashicorp/nomad/helper/useragent github.com/hashicorp/nomad/helper/uuid github.com/hashicorp/nomad/helper/winsvc github.com/hashicorp/nomad/jobspec github.com/hashicorp/nomad/lib/circbufwriter github.com/hashicorp/nomad/lib/delayheap github.com/hashicorp/nomad/lib/kheap github.com/hashicorp/nomad/nomad github.com/hashicorp/nomad/nomad/deploymentwatcher github.com/hashicorp/nomad/nomad/drainer github.com/hashicorp/nomad/nomad/mock
Processed: tagging 839022
Processing commands for cont...@bugs.debian.org: > tags 839022 + ftbfs Bug #839022 [libgraphics-colornames-perl] libgraphics-colornames-perl: Build-Depends on perl-modules-5.22 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 839022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960746: marked as done (python-pybedtools: binary-all FTBFS)
Your message dated Sun, 17 May 2020 06:18:49 + with message-id and subject line Bug#960746: fixed in python-pybedtools 0.8.0-5 has caused the Debian Bug report #960746, regarding python-pybedtools: binary-all FTBFS 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.) -- 960746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pybedtools Version: 0.8.0-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=python-pybedtools=all=0.8.0-4=1589359748=0 ... dh_fixperms chmod -x debian/*/usr/lib/python3/dist-packages/pybedtools/scripts/pybedtools chmod: cannot access 'debian/*/usr/lib/python3/dist-packages/pybedtools/scripts/pybedtools': No such file or directory make[1]: *** [debian/rules:49: override_dh_fixperms] Error 1 --- End Message --- --- Begin Message --- Source: python-pybedtools Source-Version: 0.8.0-5 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of python-pybedtools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated python-pybedtools 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: Sun, 17 May 2020 07:51:43 +0200 Source: python-pybedtools Architecture: source Version: 0.8.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 960746 Changes: python-pybedtools (0.8.0-5) unstable; urgency=medium . * Fix binary-all build Closes: #960746 Checksums-Sha1: 24005a436dec8837a4dd2b6296da92034b8a 2531 python-pybedtools_0.8.0-5.dsc 57752a35d6121e5e37b7cd54af5b5e0aa0469408 31588 python-pybedtools_0.8.0-5.debian.tar.xz cbde01319e1a99042f26c18f655a689952ed2838 11085 python-pybedtools_0.8.0-5_amd64.buildinfo Checksums-Sha256: 1f51dcde4fa36968e8a4972f76cd8a8ea62a6df7439d8ecfbbe754141f8c105f 2531 python-pybedtools_0.8.0-5.dsc b68620883a858b19f00f6506593cd6f2c2b63ddbc2cf804d13190b75c3af4248 31588 python-pybedtools_0.8.0-5.debian.tar.xz e62e99724655205eff82ad38ce0fa765b0275ac8f4541ee1a06880faab8dcd55 11085 python-pybedtools_0.8.0-5_amd64.buildinfo Files: 35e43e079b9e676ed82f1b7047752dc7 2531 python optional python-pybedtools_0.8.0-5.dsc 76989bbdd36215e7413cb1d2303d57f9 31588 python optional python-pybedtools_0.8.0-5.debian.tar.xz 94f4610fcecfb0d4fd41a047a2277be4 11085 python optional python-pybedtools_0.8.0-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl7A01YRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtGPxQ/9GqFdJobD1jZXETwMD32tag0RCTKkAZ5f zt8Oxzqu7Ra3D3NP99i3s5NpDQSj94Qqz/LRTCNyBDjHBISsSAVjbip9qbGN71/C XaXg21hv/YBg0JtFc1eBXFiXFIS9IJoWcVT9zS2qsxzYKGIJBApbLjZtZQyib3F4 6nJ3Infg5EdUihYm+L/Dbvi9tZFobaktfc9je/f7r213G8rSkNRF6iskiymKV7cO TIVM1QPsnN/hU9NHEk9Z27iS/Uw+6/x9ZLuAUvBgv5oSqSkXB+EhYNpeOy9dszXt LKfxkzfQd3inaqU4n9vBHqkclR+7IS9zrFkLiSpVUm3+DlZAXH2JIkCoER11WTDs fcY0c2hPBoK2T8+SIRH+yVj+YZm0/9e6bpdN94kXMgY4lfclkrIGbU+Nwql+ER0K mzvhs2oD73bJVvHe9l7oehEtEq5WSiPHF9C0SsAUh/tW5/dmm9NqolnY7ZOI+UlF rs4cbQyO6XFk3sT3pJrMDK/gPHzOHqv7fEAs9+EPGPHhS4gDkQ9GCbrlR4+5J6s9 QWSQV0NllGNANkhZpDLsgHp2AhwYslOw5Wc8t1rwdSMhCgjGVZJ+O5uEZnlhPwqb F/p7wwMyapUbkDy2XDT9BZh9FpL6XeRJhtXdzTZcHjXIcA42L52mku62YK5FftJm oDzxbv32A44= =tv3V -END PGP SIGNATURE End Message ---
Bug#960826: libquazip FTBFS on 32bit: symbol difference
Source: libquazip Version: 0.9-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=libquazip=sid ... dpkg-gensymbols -plibquazip5-1 -Idebian/libquazip5-1.symbols -Pdebian/libquazip5-1 -edebian/libquazip5-1/usr/lib/i386-linux-gnu/libquazip5.so.1.0.0 dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libquazip5-1/DEBIAN/symbols doesn't match completely debian/libquazip5-1.symbols --- debian/libquazip5-1.symbols (libquazip5-1_0.9-1_i386) +++ dpkg-gensymbolsEylc_P 2020-05-16 15:33:10.245761374 + @@ -331,7 +331,8 @@ _ZNK9QuaZipDir9entryListE6QFlagsIN4QDir6FilterEES0_INS1_8SortFlagEE@Base 0.7.3 _ZNK9QuaZipDir9entryListERK11QStringList6QFlagsIN4QDir6FilterEES3_INS4_8SortFlagEE@Base 0.7.3 _ZNK9QuaZipDirixEi@Base 0.7.3 - _ZSt13__adjust_heapIN5QListI16QuaZipFileInfo64E8iteratorExS1_N9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_T0_SA_T1_T2_@Base 0.9 + _ZSt13__adjust_heapIN5QListI16QuaZipFileInfo64E8iteratorEiS1_N9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_T0_SA_T1_T2_@Base 0.9-1 +#MISSING: 0.9-1# _ZSt13__adjust_heapIN5QListI16QuaZipFileInfo64E8iteratorExS1_N9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_T0_SA_T1_T2_@Base 0.9 _ZSt13__heap_selectIN5QListI16QuaZipFileInfo64E8iteratorEN9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_S9_S9_T0_@Base 0.9 _ZSt16__insertion_sortIN5QListI16QuaZipFileInfo64E8iteratorEN9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_S9_T0_@Base 0.9 _ZSt16__introsort_loopIN5QListI16QuaZipFileInfo64E8iteratorEiN9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_S9_T0_T1_@Base 0.9 dh_makeshlibs: error: failing due to earlier errors mv debian/.debhelper/generated/libquazip5-1/triggers.new debian/.debhelper/generated/libquazip5-1/triggers rm -f debian/libquazip5-dev/DEBIAN/shlibs make: *** [debian/rules:19: binary-arch] Error 25
