Bug#897793: [Pkg-pascal-devel] Bug#897793: libqtpas: ftbfs with GCC-8
Hi All, On Sat, 2018-07-21 at 12:16 +0100, peter green wrote: > > > > + _Z27qRegisterNormalizedMetaTypeIP7QActionEiRK10QByteArrayPT_N9QtPr > > ivate21MetaTypeDefinedHelperIS5_Xaasr12QMetaTypeId2IS5_E7DefinedntsrSA_9IsBu > > iltInEE11DefinedTypeE@Base 2.6~beta-4 > > (optional=templinst)_Z30copyPtrIntArrayToQListTemplateIP13QGraphicsItemEvP > > vR5QListIT_E@Base 2.6~alpha > > (optional=templinst)_Z30copyPtrIntArrayToQListTemplateIP13QStandardItemEvP > > vR5QListIT_E@Base 2.6~alpha > > (optional=templinst)_Z30copyPtrIntArrayToQListTemplateIP15QTreeWidgetItemE > > vPvR5QListIT_E@Base 2.6~alpha > > @@ -8820,10 +8821,10 @@ > > (optional=templinst)_ZN5QListIiED1Ev@Base 2.6~alpha > > (optional=templinst)_ZN5QListIiED2Ev@Base 2.6~alpha > > _ZN7QVectorI6QPointE11reallocDataEii6QFlagsIN10QArrayData16AllocationOptio > > nEE@Base 2.6~alpha > > - _ZN7QVectorI6QPointEC1Ei@Base 2.6~alpha > > - _ZN7QVectorI6QPointEC2Ei@Base 2.6~alpha > > - _ZN7QVectorI7QPointFEC1Ei@Base 2.6~alpha > > - _ZN7QVectorI7QPointFEC2Ei@Base 2.6~alpha > > +#MISSING: 2.6~beta-4# _ZN7QVectorI6QPointEC1Ei@Base 2.6~alpha > > +#MISSING: 2.6~beta-4# _ZN7QVectorI6QPointEC2Ei@Base 2.6~alpha > > +#MISSING: 2.6~beta-4# _ZN7QVectorI7QPointFEC1Ei@Base 2.6~alpha > > +#MISSING: 2.6~beta-4# _ZN7QVectorI7QPointFEC2Ei@Base 2.6~alpha > > > > > These symbols seem to be template instantiations, so I believe we > should simply mark them as (optional=templinst). Anyone disagree? > If noone disagrees I will go ahead and upload the change as a > team upload. I'm not 100% sure but it is OK for me. Please go ahead. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#904314: virtualbox-dkms fails to build with kernel 4.17.0-1
Package: virtualbox-dkms Version: 5.2.10-dfsg-6 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, with the kernel 4.17.0-1-amd64 virtualbox-dkms failed: [quote] /var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c: In function ‘vboxPciLinuxDevDetachHostDriver’: /var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c:92:40: error: implicit declaration of function ‘pci_get_bus_and_slot’; did you mean ‘pci_get_domain_bus_and_slot’? [-Werror=implicit-function-declaration] # define PCI_DEV_GET_SLOT(bus, devfn) pci_get_bus_and_slot(bus, devfn) ^ /var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c:397:15: note: in expansion of macro ‘PCI_DEV_GET_SLOT’ pPciDev = PCI_DEV_GET_SLOT(uBus, uDevFn); ^~~~ /var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c:397:13: warning: assignment makes pointer from integer without a cast [-Wint- conversion] pPciDev = PCI_DEV_GET_SLOT(uBus, uDevFn); ^ /var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c: In function ‘vboxPciOsDevInit’: /var/lib/dkms/virtualbox/5.2.10/build/vboxpci/linux/VBoxPci-linux.c:648:17: warning: assignment makes pointer from integer without a cast [-Wint- conversion] pPciDev = PCI_DEV_GET_SLOT((pIns->HostPciAddress) >> 8, ^ cc1: some warnings being treated as errors [/quote] The logfile is attached. CU Jörg - -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (300, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages virtualbox-dkms depends on: ii dkms 2.3-3 Versions of packages virtualbox-dkms recommends: ii virtualbox 5.2.10-dfsg-6 virtualbox-dkms suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAltVl0sACgkQCfifPIyh 0l2TbxAAxzLVqs2ySPNb5eXmuTaV+X2piHAgKBxg5im5C0lZ/XpJRwzONBiG2Nd3 tzBiTPe93QSoxvuzTqwlpa+0awt0+Z80IDE05VNTn/Q03l5xddrqbf4K+AOGM/84 9kxs8sXKR82Xah6vVOyik22mm0dLpRaBexZ4gW9oFRqRTVbD2eVwUOBUJHSN6b64 LGMykZmlpQVGoiyUqC2vUY8rAq3VfIRc8DXn3aILH9yIfiiSREy9KbBAuWdO+OJI EiF1hAzmhZkfgHD0kt1V1RN6OP8QQs7NDdXZaMqm8B33OBSjphOorCrIzHO70ENe WPPnodarhrJkD1jKb+cPoPj4+zMZ7uhCeaaJtMTVLqGO5zRN82nB3p1V4yBplQw1 fzdKdhYKqtdDjgU+Z4gEs/e9V6guNup+/trqnrsbiGItIRw2ff2NfkUOLLWkrvOK Jv7kv/JiM7wFGY43zS8x7uNGuEO8mThNia9ZjOrz2MNy55I+beOt8zZzZknP6FBW WChrmmjbdylPdzIfuPlVqtJT1T2s5iGnRTa3+Zbdv7fntGsXf2B0iqvv4vvG5pGA REXKOTbMeyKEcU81O8n0moBUoE3CjUmnqLVQxBVN/OISxPMlqO1DSwnSgt7ggLuY B7kLDq7N0caGgAAhOM5yOOCyc+Prvc3YqIaiwN1Vu/buai0N3Fc= =eTku -END PGP SIGNATURE- DKMS make.log for virtualbox-5.2.10 for kernel 4.17.0-1-amd64 (x86_64) Mo 23. Jul 10:36:54 CEST 2018 make: Verzeichnis „/usr/src/linux-headers-4.17.0-1-amd64“ wird betreten CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/linux/SUPDrv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/SUPDrv.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/SUPDrvGip.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/SUPDrvSem.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/SUPDrvTracer.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/SUPLibAll.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/alloc-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/initterm-r0drv.o /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/.tmp_SUPDrvTracer.o: warning: objtool: .text+0x7: indirect jump found in RETPOLINE build CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/memobj-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/mpnotification-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/powernotification-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/memuserkernel-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/mp-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/mpnotification-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/process-r0drv-linux.o /var/lib/dkms/virtualbox/5.2.10/build/vboxdrv/r0drv/linux/.tmp_memuserkernel-r0drv-linux.o: warning: objtool: .fixup: unexpected end of sect
Bug#904314: virtualbox-dkms fails to build with kernel 4.17.0-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, I have test it with the release 5.2.16-dfsg-3. This release build with no errors. CU Jörg - -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAltVmd4ACgkQCfifPIyh 0l357w//TwezZFuaLT2ihTRZroxRtQuFq844MsAliuqK1itS8bHG/bt9N97whPwm RN2O5DhejByTrJA659//V1XuhQsIm2hGF/w2Tluj9n9AW8KyDNLcMLLxcBjeVNPH Gr9+EL26bEjfthF08uxWIwJ01JdP9+nUIiPRG+aBXC4PpVR779VGA9iYdGh/glQs j6Ws/vQpsANwmO/Df2WLEpAjkY6PRrAPJLCHCF9QFeOsnjO3yQuK01uQiPSI+CqB AACcXRMAq0p2tII+RW9eD56nI1OQ4JgJS0SATL7ZtnVTrV/+8VIiFiEOiNoPznma y/N8YtgSZpTWRgDRupxuZvRJJ9P+Afloxcpk/WANpSn1ngpRD9lAvwh5rlc+asQf qtP5sCsqqu4op0B2feEvGiRho1JEHz2x84rFM1ye77eRPAsaAJAUoDSpAzAd8MQQ tbFBSSyErayJuntHtPXb/nXFs0YLgENvUCMbvn0FwU1JoiJLS6MYk2gJ3CZ2GVNR cqPiddoyrYM7zDn87wJrX50As7onvV4xDhG9TZLcQ7tHNqgrDe3F1A0MNxVy+xTp yw9USffRzYMcKtJvYwkwA+UcV/P3Yk5GTpP7eoVY6fQaOUePZve/Yt+OBpIfabfl VYzJYDgXweeDapbKoZ7EuEM9y61Ut6WPfK7i0Iq2ELh6ZyLB2jI= =uks8 -END PGP SIGNATURE-
Bug#904111: clamav-daemon causing deadlocks/blocking I/O
Quack, I just upgraded and cannot reproduce this problem. I'm not using the ScanOnAccess feature. Follows collected config info. \_o< -- Package-specific info: --- configuration --- Checking configuration files in /etc/clamav Config file: clamd.conf --- BlockMax disabled PreludeEnable disabled PreludeAnalyzerName = "ClamAV" LogFile = "/var/log/clamav/clamav.log" LogFileUnlock disabled LogFileMaxSize = "4294967295" LogTime = "yes" LogClean disabled LogSyslog disabled LogFacility = "LOG_LOCAL6" LogVerbose disabled LogRotate = "yes" ExtendedDetectionInfo = "yes" PidFile disabled TemporaryDirectory disabled DatabaseDirectory = "/var/lib/clamav" OfficialDatabaseOnly disabled LocalSocket disabled LocalSocketGroup disabled LocalSocketMode disabled FixStaleSocket = "yes" TCPSocket = "3310" TCPAddr disabled MaxConnectionQueueLength = "15" StreamMaxLength = "10485760" StreamMinPort = "1024" StreamMaxPort = "2048" MaxThreads = "10" ReadTimeout = "180" CommandReadTimeout = "5" SendBufTimeout = "200" MaxQueue = "100" IdleTimeout = "30" ExcludePath disabled MaxDirectoryRecursion = "15" FollowDirectorySymlinks disabled FollowFileSymlinks disabled CrossFilesystems = "yes" SelfCheck = "3600" DisableCache disabled VirusEvent disabled ExitOnOOM = "yes" AllowAllMatchScan = "yes" Foreground disabled Debug disabled LeaveTemporaryFiles disabled User = "clamav" Bytecode = "yes" BytecodeSecurity = "TrustSigned" BytecodeTimeout = "6" BytecodeUnsigned disabled BytecodeMode = "Auto" DetectPUA disabled ExcludePUA disabled IncludePUA disabled AlgorithmicDetection = "yes" ScanPE = "yes" ScanELF = "yes" DetectBrokenExecutables disabled ScanMail = "yes" ScanPartialMessages disabled PhishingSignatures = "yes" PhishingScanURLs = "yes" PhishingAlwaysBlockCloak disabled PhishingAlwaysBlockSSLMismatch disabled PartitionIntersection disabled HeuristicScanPrecedence = "yes" StructuredDataDetection disabled StructuredMinCreditCardCount = "3" StructuredMinSSNCount = "3" StructuredSSNFormatNormal = "yes" StructuredSSNFormatStripped disabled ScanHTML = "yes" ScanOLE2 = "yes" OLE2BlockMacros disabled ScanPDF = "yes" ScanSWF = "yes" ScanXMLDOCS = "yes" ScanHWP3 = "yes" ScanArchive = "yes" ArchiveBlockEncrypted disabled ForceToDisk disabled MaxScanSize = "104857600" MaxFileSize = "26214400" MaxRecursion = "16" MaxFiles = "1" MaxEmbeddedPE = "10485760" MaxHTMLNormalize = "10485760" MaxHTMLNoTags = "2097152" MaxScriptNormalize = "5242880" MaxZipTypeRcg = "1048576" MaxPartitions = "50" MaxIconsPE = "100" MaxRecHWP3 = "16" PCREMatchLimit = "1" PCRERecMatchLimit = "5000" PCREMaxFileSize = "26214400" ScanOnAccess disabled OnAccessMountPath disabled OnAccessIncludePath disabled OnAccessExcludePath disabled OnAccessExcludeRootUID disabled OnAccessExcludeUID disabled OnAccessMaxFileSize = "5242880" OnAccessDisableDDD disabled OnAccessPrevention disabled OnAccessExtraScanning disabled DevACOnly disabled DevACDepth disabled DevPerformance disabled DevLiblog disabled DisableCertCheck disabled Config file: freshclam.conf --- LogFileMaxSize = "4294967295" LogTime disabled LogSyslog disabled LogFacility = "LOG_LOCAL6" LogVerbose disabled LogRotate = "yes" PidFile disabled DatabaseDirectory = "/var/lib/clamav/" Foreground disabled Debug disabled UpdateLogFile = "/var/log/clamav/freshclam.log" DatabaseOwner = "clamav" Checks = "24" DNSDatabaseInfo = "current.cvd.clamav.net" DatabaseMirror = "db.local.clamav.net", "database.clamav.net" PrivateMirror disabled MaxAttempts = "5" ScriptedUpdates = "yes" TestDatabases = "yes" CompressLocalDatabase disabled ExtraDatabase disabled DatabaseCustomURL disabled HTTPProxyServer disabled HTTPProxyPort disabled HTTPProxyUsername disabled HTTPProxyPassword disabled HTTPUserAgent disabled NotifyClamd = "/etc/clamav/clamd.conf" OnUpdateExecute disabled OnErrorExecute disabled OnOutdatedExecute disabled LocalIPAddress disabled ConnectTimeout = "30" ReceiveTimeout = "30" SafeBrowsing disabled Bytecode = "yes" clamav-milter.conf not found Software settings - Version: 0.100.0 Optional features supported: MEMPOOL IPv6 FRESHCLAM_DNS_FIX AUTOIT_EA06 BZIP2 LIBXML2 PCRE ICONV JSON JIT Database information Database directory: /var/lib/clamav/ WARNING: freshclam.conf and clamd.conf point to different database directories [3rd Party] phishtank.ndb: 30797 sigs [3rd Party] bofhland_malware_attach.hdb: 1835 sigs [3rd Party] winnow_bad_cw.hdb: 1 sig [3rd Party] jurlbl.ndb: 14183 sigs [3rd Party] bofhland_malware_URL.ndb: 4 sigs [3rd Party] spamattach.hdb: 14 sigs [3rd Party] winnow_malware_links.ndb: 4623 sigs [3rd Party] doppelstern.hdb: 1 sig [3rd Party] winnow_malware.hdb: 293 sigs [3rd Party] winnow_extended_malware.hdb: 245 sigs [3rd Party] sanesecurity.ftm: 170 sigs [3rd Party] rogue.hdb: 4678 sigs [3rd Party] porcupine.ndb: 3341 sigs [3rd Party] phish.ndb: 27408 sigs [3rd Party] crdfam.clamav.hdb: 1 sig [3rd Party] bofhland_cracked_URL.nd
Processed: pytest-pylint is affected by 902631
Processing commands for cont...@bugs.debian.org: > # at least the autopktest of pytest-pylint is affected, but I think > pytest-pylint > # just doesn't work with python3.7 > affects 902631 src:pytest-pylint Bug #902631 [src:astroid] astroid: Not compatible with Python 3.7 Added indication that 902631 affects src:pytest-pylint > thanks Stopping processing here. Please contact me if you need assistance. -- 902631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902631 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#895411: they are waiting for qt 5.11
I wonder the same thing as Thomas. I also have to patch away the version check every time a new debian package gets distributed. Why don't you patch away the version check in the Debian package in general? I never had a problem using Anki on a QT version officially not supproted. At least I can confirm that it works a lot better than with the version check in it. (Making the package completely unusable.) Also the bug that is trying to be prevented by the refusal of 5.10 doesn't seem to be that important, that it would suggest refusing to run the program at all. The problem is documented to cause a crash when opening the the browser and the stats window back and forth multiple times. So what? The program can be restarted afterwards, it doesn't seem to crash the database, as there shouldn't be any write operation on it at that time. (And in case of, there would be a backup of the data automatically done by Anki anyway.) -- Matthias Peter WimmerMúnich Beieren Germany Eŭropa 世界 +49-1-1 https://matthias.wimmer.name/ Developing software / Learning languages / Love to sail
Bug#903285: Bug #903285 in bundler marked as pending
Control: tag -1 pending Hello, Bug #903285 in bundler reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/bundler/commit/8a341807711a62dd9bd44f185ad62545098f8ba3 Follow ronn package rename Closes: #903285 (this message was generated automatically) -- Greetings https://bugs.debian.org/903285
Processed: Bug #903285 in bundler marked as pending
Processing control commands: > tag -1 pending Bug #903285 [src:bundler] bundler FTBFS: fails to find ronn Added tag(s) pending. -- 903285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#903285: marked as done (bundler FTBFS: fails to find ronn)
Your message dated Mon, 23 Jul 2018 09:48:49 + with message-id and subject line Bug#903285: fixed in bundler 1.16.1-3 has caused the Debian Bug report #903285, regarding bundler FTBFS: fails to find ronn 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.) -- 903285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bundler Version: 1.16.1-2 Severity: serious Tags: ftbfs bundler fails to build from source since ronn got split out from ruby-ronn into a separate package ronn. Fixing this problem will involve adding ronn to Build-Depends as the build system tries to invoke ronn with "ruby2.5 -S ronn". Adding a transitional dependency was not possible as it would have created a dependency cycle. I'm less sure about whether the ruby-ronn dependency could be dropped, because ronn is mentioned in a .gemspec file. I don't quite understand how bundler uses ronn, but it might be that it uses both the script (ronn) and the ruby module (ruby-ronn). If that is the case, it actually needs to depend on both. Helmut --- End Message --- --- Begin Message --- Source: bundler Source-Version: 1.16.1-3 We believe that the bug you reported is fixed in the latest version of bundler, 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 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated bundler package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 23 Jul 2018 09:20:24 + Source: bundler Binary: ruby-bundler bundler Architecture: source Version: 1.16.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Chris Hofstaedtler Description: bundler- Manage Ruby application dependencies ruby-bundler - Manage Ruby application dependencies (runtime) Closes: 903285 Changes: bundler (1.16.1-3) unstable; urgency=medium . * Team upload. * Follow ronn package rename (Closes: #903285) * Declare compliance with Debian Policy 4.1.5. Checksums-Sha1: bc30f1fd2cb89c7be395674e6fea750191af880c 2139 bundler_1.16.1-3.dsc 175ffdf07902e9e61ec313509b16c35608687435 10204 bundler_1.16.1-3.debian.tar.xz 119d4d61ce6e9c3684aa5c39e6e3204d0ea38558 7242 bundler_1.16.1-3_source.buildinfo Checksums-Sha256: e5b3c936599c151392ced96fb797d30465e7b2c4aa80769257b7a59a9392446a 2139 bundler_1.16.1-3.dsc 030e4748133c0cfd370e4535155012c88dd471fa1b20314228bfb92aaba2dd9c 10204 bundler_1.16.1-3.debian.tar.xz 277d4c2d889155060e69ddbb3d0fe3289e43240d217a32416fe34c54cd81edef 7242 bundler_1.16.1-3_source.buildinfo Files: 49d6fa64719bff8c5c18126055aa2893 2139 ruby optional bundler_1.16.1-3.dsc 8ad322dc7a31e0d3ed4c77de493b438c 10204 ruby optional bundler_1.16.1-3.debian.tar.xz 6f8fe79a3e1977b2e4ab1f86b334df24 7242 ruby optional bundler_1.16.1-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAltVnuwACgkQXBPW25MF LgOVHBAAhOszLQTTEY3xm2rxcEibkh5DqWBBKped9LK3K+Qw26VUQbtUOAyQexMO 9pwqVwbMlGcDTYQ+wd0/LeYUUJbcq//pqOQJC9yOf02aYZKyIySTpiecu2Q9dAWr W63yxljFJ/F7TSYXgxHbzlsVjSZx/hrB/hMRHvR9UFcyThhGB5npvFnUHw+Dql91 1xe8oaxdrSsnfgGjZJO38+5zPoAi8D6LSC6CGwTL7qKhIWlv/f50pfA5aZZiaE+S SORdhk5RB7AUpKNvVyQ5HhN4yzDkzSyG8QhXTWfCzhEJT0ESq6c8vbDqj3y3J7PR uRzAElz/6yAvT0UQnqQJXb4Vo7RUUh0wMP2MJAUMUGxg7iiJ010CXPdkgyWT90pL 3s+QKxH+jkXRw6vLDif3Q1R5UY41Ht/q5Q04kpIos8GMpuKmIQsaNTvZrUmYIdeZ VGf+LvB3XKk5tJS1vO3c0dwUU+0YHpk0XfoPz91Io4K7c/lEEoOLG581FNJJ0/1W gMS3OxxfW5PHP05s+pk6WGNoSpUl4cARU8fhEIbynu17xB2+GgKfUgt85Wuvi4OO BSWNY/M1vkdIjo+u/YqXKY8LgAibHhO2xMHIHTJC7aiQ9C1Fm8UHVTVhAcqZeuSX hsmyTIZQZYy8zEDfNAGZaxio00SqHZ3v/1u0Un3RKBP8vVnFUTk= =Pw/1 -END PGP SIGNATURE End Message ---
Bug#892139: marked as done (eclib: FTBFS on i386: tests fail: reference solution precision mismatch)
Your message dated Mon, 23 Jul 2018 09:49:02 +
with message-id
and subject line Bug#892139: fixed in eclib 20180710-2
has caused the Debian Bug report #892139,
regarding eclib: FTBFS on i386: tests fail: reference solution precision
mismatch
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.)
--
892139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eclib
Version: 20171219-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
eclib/experimental FTBFS on i386:
https://buildd.debian.org/status/fetch.php?pkg=eclib&arch=i386&ver=20171219-1&stamp=1519985150&raw=0
make check_procs check_qcurves check_qrank check_g0n
make[3]: Entering directory '/<>/tests'
Running procs checks...
for prog in smattest comptest rattest bigrattest ptest mptest tbessel mvectest
mmattest mspace thilbert tp2points tilll vectest1 vectest2 mattest1 mattest2
space1 space2 svectest1 svectest2 tcon2 tlegcert timing threading; do echo
"Testing ${prog}..."; ./${prog} < ./in_ntl/${prog}.in > ${prog}.testout
2>/dev/null && diff ${prog}.testout ./out_ntl/${prog}.out || exit $?; done
Testing smattest...
Testing comptest...
5c5
< AGM((3.125,4.25),(1,0)) = (2.07831617217326684,1.5633615899065958201)
---
> AGM((3.125,4.25),(1,0)) = (2.07831617217326684003,1.56336158990659582007)
7c7
< AGM((1,1),(2,1)) = (1.471349362864653566,1.0200541263376600196)
---
> AGM((1,1),(2,1)) = (1.47134936286465356604,1.02005412633766001965)
11,16c11,16
< Enter a real or complex: Main cube root =
(1.6289371459221758752,0.52017450230454583955)
< whose cube is(3,4)
< Next cube root = (-1.2649529063577516597,1.1506136983844504996)
< whose cube is(3,4)
< Next cube root = (-0.36398423956442421551,-1.6707882006889963392)
< whose cube is(3,4)
---
> Enter a real or complex: Main cube root =
> (1.62893714592217587521,0.520174502304545839545)
> whose cube is(2.,3.)
> Next cube root = (-1.2649529063577516597,1.15061369838445049961)
> whose cube is(2.,4.0001)
> Next cube root = (-0.363984239564424215513,-1.67078820068899633915)
> whose cube is(3.0001,3.)
18,21c18,21
< (-1.2878154795576479889,-0.85789675832849028642)
< (-1.2878154795576479889,0.85789675832849028642)
< (0.28781547955764798887,1.4160930801719079387)
< (0.28781547955764798887,-1.4160930801719079387)
---
> (-1.28781547955764798887,-0.857896758328490286416)
> (-1.28781547955764798887,0.857896758328490286416)
> (0.287815479557647988873,1.41609308017190793872)
> (0.287815479557647988873,-1.41609308017190793872)
Makefile:1285: recipe for target 'check_procs' failed
make[3]: *** [check_procs] Error 1
make[3]: Entering directory '/<>/tests'
Running qrank checks...
for prog in tmrank tequiv d2; do echo "Testing ${prog}..."; ./${prog} <
./in_ntl/${prog}.in > ${prog}.testout 2>/dev/null && diff ${prog}.testout
./out_ntl/${prog}.out || exit $?; done
Testing tmrank...
Testing tequiv...
Testing d2...
14c14
< height = 13.565420700285587132
---
> height = 13.5654207002855871318
16c16
< height = 27.130841400571174263
---
> height = 27.1308414005711742635
Makefile:1297: recipe for target 'check_qrank' failed
make[3]: *** [check_qrank] Error 1
Looks like there is now one more digit in the output ...
Andreas
--- End Message ---
--- Begin Message ---
Source: eclib
Source-Version: 20180710-2
We believe that the bug you reported is fixed in the latest version of
eclib, 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 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Julien Puydt (supplier of updated eclib package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 23 Jul 2018 09:16:59 +0200
Source: eclib
Binary: libec4 libec-dev eclib-tools
Architecture: source amd64
Version: 20180710-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Julien Puydt
Description:
eclib-tools - Programs for modular symbols and elliptic curve
Processed: python-biopython: FTBFS and test failure with Python3.7
Processing control commands: > severity -1 serious Bug #904317 [src:python-biopython] python-biopython: autopkgtest fails: not ready for Python3.7 Severity set to 'serious' from 'normal' > tags -1 + ftbfs buster sid Bug #904317 [src:python-biopython] python-biopython: autopkgtest fails: not ready for Python3.7 Added tag(s) sid, ftbfs, and buster. > retitle -1 python-biopython: FTBFS and test failure with Python3.7 Bug #904317 [src:python-biopython] python-biopython: autopkgtest fails: not ready for Python3.7 Changed Bug title to 'python-biopython: FTBFS and test failure with Python3.7' from 'python-biopython: autopkgtest fails: not ready for Python3.7'. -- 904317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#903327: marked as done (cl-usocket: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))
Your message dated Mon, 23 Jul 2018 10:18:53 + with message-id and subject line Bug#903327: fixed in cl-usocket 0.7.0.1-3 has caused the Debian Bug report #903327, regarding cl-usocket: FTBFS in buster/sid (dh_installdocs: Cannot find "README") 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.) -- 903327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cl-usocket Version: 0.7.0.1-2 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules binary-indep dh_testdir dh_testroot dh_prep dh_installdirs dh_install dh_testdir dh_testroot dh_installchangelogs dh_installdocs dh_installdocs: Cannot find (any matches for) "README" (tried in .) debian/rules:28: recipe for target 'binary-indep' failed make: *** [binary-indep] Error 2 dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit status 2 The build was made with "dpkg-buildpackage -A" in my autobuilder. Most probably, it also fails here in reproducible builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/cl-usocket.html [ Note: There has been a recent change in debhelper behaviour, the current behaviour is the intended one. See Bug #903133 for details ]. Thanks. --- End Message --- --- Begin Message --- Source: cl-usocket Source-Version: 0.7.0.1-3 We believe that the bug you reported is fixed in the latest version of cl-usocket, 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 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sébastien Villemot (supplier of updated cl-usocket package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 23 Jul 2018 12:05:32 +0200 Source: cl-usocket Binary: cl-usocket Architecture: source Version: 0.7.0.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Common Lisp Team Changed-By: Sébastien Villemot Description: cl-usocket - Common Lisp socket library Closes: 903327 Changes: cl-usocket (0.7.0.1-3) unstable; urgency=medium . * Team upload * Rewrite d/copyright using machine-readable format 1.0 * Bump to debhelper compat level 11 * Ship README.md instead of README (Closes: #903327) * Simplify d/rules using dh * Set M-A foreign * Bump S-V to 4.1.5 * Ship the CHANGES file Checksums-Sha1: 8c27f732d178963cab001097480fe08ad71a43fa 2254 cl-usocket_0.7.0.1-3.dsc 824f811b2745d11d98f15250c63b8fb16f276855 11620 cl-usocket_0.7.0.1-3.debian.tar.xz 198f0bd9917d4c2964dc5506edb4f17da7b19073 5638 cl-usocket_0.7.0.1-3_amd64.buildinfo Checksums-Sha256: 41cf9639902c1af8a6c25f35c38c012a2a03dd37323423c9c8ab18555446fe2b 2254 cl-usocket_0.7.0.1-3.dsc ee15913c606deba7a24ddd435ad19d8aab384cd2082a87edd4d7d5608e79e6d8 11620 cl-usocket_0.7.0.1-3.debian.tar.xz f820c22f0fa398d88219507a02b805245ccc00e2fec2b4eb7261e85bb4e2052b 5638 cl-usocket_0.7.0.1-3_amd64.buildinfo Files: f13e6833443e2fe60f270d1ed01b6ced 2254 lisp optional cl-usocket_0.7.0.1-3.dsc 4f3d3ea78553ad375a422136094fbee6 11620 lisp optional cl-usocket_0.7.0.1-3.debian.tar.xz 770cde897f741935802ae7a3c3d91343 5638 lisp optional cl-usocket_0.7.0.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAltVqTEACgkQLOzpNQ7O vkpiaw/9GrLzyMGjBgQI9kjdBUaVr+bXU6DviofezO0YZbr0hcAtWjj2reJQ6rII 50HIXMARBa/G1AIC5ohO1dr6sG/SCDQ6opnucEAmTN8GVEOO8d6OgD9coHzKdXky U86uwJoA71qGq0hjVQRMSZx11ggvYARlPZvkmgbsCExQSAg1pu4B5R4RWr6KXo/N hHHsRKI49GPB3c/lAkFa7U8MPbU2FtVKYJOu9td4GnwcaDNfaspPXqDdI7ys6GGS DwYart1qiHF1Wh0Wr+jNm67jj9cBlTTGHwFjH6ZsQIGPX0CK96l2kayk1jIWFjt4 aNKW9woJdC6UKHUpb1k2S8u2gAJsSrGq5phi5fLFHuxXV/VnNheu8q2V5D5wiLri lobaDIm0lq37qxIdNKqB0LG0SC56IGxhwFljnW509SeJMmUnKyMYADjv4eHxTrQr So//wFQk49cYhc7wu/clWJGxkSXDJMXYq2W4iyt477L6mgUYfPt+Sji6OqTEY9u+ MvILn+tZu3HRFBd46qih9p9eE99qUNRXy9ICu0RG9AJFwOxA2trjUY8NNUfFrASC J95ETpp/5O42WPeVYIDYnvxj91W3XYUFs4DNdnUNMDN5/x1JRAJ9696A/n2S
Processed: Upgrading bug to RC
Processing control commands: > severity -1 serious Bug #900813 [vm] vm: fails to byte-compile with unversioned emacs Severity set to 'serious' from 'important' -- 900813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: update symbols for GCC 8
Processing control commands: > tags -1 + patch Bug #897739 [src:deepin-movie-reborn] deepin-movie-reborn: ftbfs with GCC-8 Added tag(s) patch. -- 897739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897739: update symbols for GCC 8
Control: tags -1 + patch update symbols for GCC 8. A few symbols are also not emitted when building with -O3. diff -Nru deepin-movie-reborn-3.2.8/debian/changelog deepin-movie-reborn-3.2.8/debian/changelog --- deepin-movie-reborn-3.2.8/debian/changelog 2018-07-21 04:54:14.0 +0200 +++ deepin-movie-reborn-3.2.8/debian/changelog 2018-07-23 11:00:47.0 +0200 @@ -1,3 +1,9 @@ +deepin-movie-reborn (3.2.8-1ubuntu2) cosmic; urgency=medium + + * Update symbols for GCC 8. + + -- Matthias Klose Mon, 23 Jul 2018 11:00:47 +0200 + deepin-movie-reborn (3.2.8-1) unstable; urgency=medium * New upstream version 3.2.8 diff -Nru deepin-movie-reborn-3.2.8/debian/libdmr0.1.symbols deepin-movie-reborn-3.2.8/debian/libdmr0.1.symbols --- deepin-movie-reborn-3.2.8/debian/libdmr0.1.symbols 2018-07-21 04:54:14.0 +0200 +++ deepin-movie-reborn-3.2.8/debian/libdmr0.1.symbols 2018-07-23 11:00:47.0 +0200 @@ -14,7 +14,7 @@ (c++)"QFutureWatcher::~QFutureWatcher()@Base" 3.2.4 (c++)"QHash::deleteNode2(QHashData::Node*)@Base" 3.2.4 (c++)"QHash::duplicateNode(QHashData::Node*, void*)@Base" 3.2.4 - (c++)"QHash::findNode(QString const&, unsigned int) const@Base" 3.2.4 + (c++|optional)"QHash::findNode(QString const&, unsigned int) const@Base" 3.2.4 (c++)"QList::detach_helper(int)@Base" 3.2.4 (c++)"QList::~QList()@Base" 3.2.4 (c++)"QList::append(QFileInfo const&)@Base" 3.2.4 @@ -24,7 +24,7 @@ (c++)"QList >::detach_helper_grow(int, int)@Base" 3.2.4 (c++)"QList >::~QList()@Base" 3.2.4 (c++)"QList >::append(QMap const&)@Base" 3.2.4 - (c++)"QList >::clear()@Base" 3.2.4 + (c++|optional)"QList >::clear()@Base" 3.2.4 (c++)"QList >::detach_helper(int)@Base" 3.2.4 (c++)"QList >::detach_helper_grow(int, int)@Base" 3.2.4 (c++)"QList >::~QList()@Base" 3.2.4 @@ -35,7 +35,7 @@ (c++)"QList >::QList(QList > const&)@Base" 3.2.4 (c++)"QList >::append(QPair const&)@Base" 3.2.4 (c++)"QList >::detach_helper_grow(int, int)@Base" 3.2.4 - (c++)"QList >::node_copy(QList >::Node*, QList >::Node*, QList >::Node*)@Base" 3.2.4 + (c++|optional)"QList >::node_copy(QList >::Node*, QList >::Node*, QList >::Node*)@Base" 3.2.4 (c++)"QList >::~QList()@Base" 3.2.4 (c++)"QList::QList(QList const&)@Base" 3.2.4 (c++)"QList::append(QString const&)@Base" 3.2.4 @@ -50,7 +50,7 @@ (c++)"QList::operator+=(QList const&)@Base" 3.2.4 (c++)"QList::~QList()@Base" 3.2.4 (c++)"QList::append(QVariant const&)@Base" 3.2.4 -#MISSING: 3.2.8# (c++|arch=!i386 !powerpc)"QList::detach()@Base" 3.2.7 +#MISSING: 3.2.8# (c++|arch=!i386 !powerpc !ppc64el)"QList::detach()@Base" 3.2.7 (c++)"QList::detach_helper(int)@Base" 3.2.4 (c++)"QList::detach_helper_grow(int, int)@Base" 3.2.4 (c++)"QList::reserve(int)@Base" 3.2.4 @@ -60,29 +60,29 @@ (c++)"QList::detach()@Base" 3.2.4 (c++)"QList::detach_helper(int)@Base" 3.2.4 (c++)"QList::detach_helper_grow(int, int)@Base" 3.2.4 - (c++)"QList::node_copy(QList::Node*, QList::Node*, QList::Node*)@Base" 3.2.4 + (c++|optional)"QList::node_copy(QList::Node*, QList::Node*, QList::Node*)@Base" 3.2.4 (c++)"QList::operator+=(QList const&)@Base" 3.2.4 (c++)"QList::~QList()@Base" 3.2.4 (c++)"QList::append(dmr::ShooterSubtitleMeta const&)@Base" 3.2.4 - (c++)"QList::clear()@Base" 3.2.4 + (c++|optional)"QList::clear()@Base" 3.2.4 (c++)"QList::detach_helper(int)@Base" 3.2.4 (c++)"QList::detach_helper_grow(int, int)@Base" 3.2.4 (c++)"QList::~QList()@Base" 3.2.4 (c++)"QList::append(int const&)@Base" 3.2.4 #MISSING: 3.2.8# (c++)"QList::detach()@Base" 3.2.4 (c++)"QList::detach_helper_grow(int, int)@Base" 3.2.4 - (c++)"QList::~QList()@Base" 3.2.4 + (c++|optional)"QList::~QList()@Base" 3.2.4 (c++)"QList::append(long long const&)@Base" 3.2.4 (c++)"QList::detach_helper(int)@Base" 3.2.4 (c++)"QList::detach_helper_grow(int, int)@Base" 3.2.4 - (c++)"QList::~QList()@Base" 3.2.4 + (c++|optional)"QList::~QList()@Base" 3.2.4 (c++)"QMap::QMap(QMap const&)@Base" 3.2.4 - (c++)"QMap::detach_helper()@Base" 3.2.4 + (c++|optional)"QMap::detach_helper()@Base" 3.2.4 (c++)"QMap::operator[](QString const&) const@Base" 3.2.4 (c++)"QMap::operator[](QString const&)@Base" 3.2.4 (c++)"QMap::~QMap()@Base" 3.2.4 (c++)"QMapData::createNode(QString const&, QVariant const&, QMapNode*, bool)@Base" 3.2.4 - (c++)"QMapData::findNode(QString const&) const@Base" 3.2.4 + (c++|optional)"QMapData::findNode(QString const&) const@Base" 3.2.4 (c++)"QMapNode::copy(QMapData*) const@Base" 3.2.4 (c++)"QMapNode::destroySubTree()@Base" 3.2.4 (c++)"QMetaTypeId >::qt_metatype_id()::metatype_id@Base" 3.2.4 @@ -98,7 +98,7 @@ (c++)"QStringList::~QStringList()@Base" 3.2.4 (c++)"QVector::QVector(QVector const&)@Base" 3.2.4 (c++)"QVector::reallocData(int, int, QFlags)@Base" 3.2.4 - (c++)"QVector::resize(int)@Base" 3.2.4 + (c++|optional)"QVector::resize(int)@Base" 3.2.4 (c++)"QVector::~QVector()@Base" 3.2.4 (c++)"QtConcurrent::IterateKernel >::const_iterator, dmr::PlayItemInfo>::forThreadFunction()@Base" 3.2.4
Bug#904314: virtualbox-dkms fails to build with kernel 4.17.0-1
Hi,
after I upgraded to Linux v4.17.8 in Debian/buster today, I had the same issue.
root@iniza:~# cat /proc/version
Linux version 4.17.0-1-amd64 (debian-ker...@lists.debian.org) (gcc
version 7.3.0 (Debian 7.3.0-26)) #1 SMP Debian 4.17.8-1 (2018-07-20)
With upgrading to virtualbox{-dkms,-qt} (5.2.16-dfsg-3) from
Debian/sid I was able to build with no errors...
root@iniza:~# LANG=C dkms status virtualbox -v 5.2.16 -k 4.17.0-1-amd64
virtualbox, 5.2.16, 4.17.0-1-amd64, x86_64: installed
So, please provide the above working version in Debian/buster.
Thanks.
Regards,
- Sedat -
Bug#814563: xul-ext-searchload-options abandoned upstream
Hey. Well, while I guess it's functionality will be missed, you're right that it probably makes no sense to keep it, now that Mozilla broke all XUL add-ons. Cheers, Chris.
Processed: upgrading to serious
Processing control commands: > severity -1 serious Bug #900815 [egg] egg: fails to install with unversioned emacs Severity set to 'serious' from 'important' -- 900815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: FTBFS when building binary-packages only
Processing commands for cont...@bugs.debian.org: > severity 904319 serious Bug #904319 [intel-mkl] FTBFS when building binary-packages only Severity set to 'serious' from 'normal' > reassign 904319 src:intel-mkl Bug #904319 [intel-mkl] FTBFS when building binary-packages only Bug reassigned from package 'intel-mkl' to 'src:intel-mkl'. Warning: Unknown package 'src:intel-mkl' Warning: Unknown package 'src:intel-mkl' No longer marked as found in versions intel-mkl/2018.3.222-1. Warning: Unknown package 'src:intel-mkl' Warning: Unknown package 'src:intel-mkl' Ignoring request to alter fixed versions of bug #904319 to the same values previously set Warning: Unknown package 'src:intel-mkl' > found 904319 2018.3.222-1 Bug #904319 [src:intel-mkl] FTBFS when building binary-packages only Warning: Unknown package 'src:intel-mkl' Marked as found in versions intel-mkl/2018.3.222-1. Warning: Unknown package 'src:intel-mkl' > thanks Stopping processing here. Please contact me if you need assistance. -- 904319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#814563: xul-ext-searchload-options abandoned upstream
Hi Christoph, On Sat, May 14, 2016 at 01:46:51AM +0200, Christoph Anton Mitterer wrote: > I think this is any extremely helpful add-on, and just because there is > (currently) no active upstream, doesn't mean it must necessarily be > removed. […] > So pleas refrain from dropping it, unless there would be no way around > it in some point in the future. With the move to the new webext format, I guess it’s now time to get rid of xul-ext-searchload-options. I’d like to ask for it’s removal unless someone really wants to take it over. Regards David
Bug#904314: virtualbox-dkms fails to build with kernel 4.17.0-1
control: fixed -1 5.2.16-dfsg-3
control: close -1
Il Lunedì 23 Luglio 2018 12:45, Sedat Dilek ha scritto:
Hi,
after I upgraded to Linux v4.17.8 in Debian/buster today, I had the same issue.
root@iniza:~# cat /proc/version
Linux version 4.17.0-1-amd64 (debian-ker...@lists.debian.org) (gcc
version 7.3.0 (Debian 7.3.0-26)) #1 SMP Debian 4.17.8-1 (2018-07-20)
With upgrading to virtualbox{-dkms,-qt} (5.2.16-dfsg-3) from
Debian/sid I was able to build with no errors...
root@iniza:~# LANG=C dkms status virtualbox -v 5.2.16 -k 4.17.0-1-amd64
virtualbox, 5.2.16, 4.17.0-1-amd64, x86_64: installed
So, please provide the above working version in Debian/buster.
Thanks.
Regards,
- Sedat -
Processed: Re: Bug#904314: virtualbox-dkms fails to build with kernel 4.17.0-1
Processing control commands: > fixed -1 5.2.16-dfsg-3 Bug #904314 [virtualbox-dkms] virtualbox-dkms fails to build with kernel 4.17.0-1 Marked as fixed in versions virtualbox/5.2.16-dfsg-3. > close -1 Bug #904314 [virtualbox-dkms] virtualbox-dkms fails to build with kernel 4.17.0-1 Marked Bug as done -- 904314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#888326: marked as done (gst-libav1.0: FTBFS with FFmpeg 4.0)
Your message dated Mon, 23 Jul 2018 11:34:07 + with message-id and subject line Bug#888326: fixed in gst-libav1.0 1.15.0.1+git20180723+db823502-1 has caused the Debian Bug report #888326, regarding gst-libav1.0: FTBFS with FFmpeg 4.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 888326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gst-libav1.0 Version: 1.12.4-1 Severity: important User: debian-multime...@lists.debian.org Usertags: ffmpeg-3.5-transition Hi, Your package FTBFS with the upcoming version 3.5 of FFmpeg. In FFmpeg 3.5, there are a number of API changes which will cause many packages to FTBFS. For this reason I have uploaded an early development snapshot to experimental before the 3.5 release in an attempt to fix some of these a bit quicker. While 3.5 has not been finalized and the ABI is not stable yet, there should not be any significant API breakages before the release. Incomplete list of changes (based on looking at common build failures): - Some fields in AVCodecContext have been removed and replaced with private options which can be set using the av_opt_set* APIs - Most CODEC_* constants have been renamed to AV_CODEC_* - The buffer constants FF_INPUT_BUFFER_PADDING_SIZE and FF_MIN_BUFFER_SIZE have been renamed to AV_INPUT_BUFFER_PADDING_SIZE and AV_INPUT_BUFFER_MIN_SIZE. - The old resampling API provided by libavcodec has been removed. Use libswresample instead. - The libavfilter/avfiltergraph.h header has been removed, include libavfilter/avfilter.h instead. - The AVFrac structure (representing mixed rational numbers) has been removed. Build log: https://people.debian.org/~jcowgill/ffmpeg-3.5-20180122/gst-libav1.0_amd64.build Thanks, James --- End Message --- --- Begin Message --- Source: gst-libav1.0 Source-Version: 1.15.0.1+git20180723+db823502-1 We believe that the bug you reported is fixed in the latest version of gst-libav1.0, 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 888...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Dröge (supplier of updated gst-libav1.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 23 Jul 2018 13:05:46 +0300 Source: gst-libav1.0 Binary: gstreamer1.0-libav gstreamer1.0-libav-dbg Architecture: source amd64 Version: 1.15.0.1+git20180723+db823502-1 Distribution: unstable Urgency: medium Maintainer: Maintainers of GStreamer packages Changed-By: Sebastian Dröge Description: gstreamer1.0-libav - libav plugin for GStreamer gstreamer1.0-libav-dbg - libav plugin for GStreamer (debug symbols) Closes: 888326 904023 Changes: gst-libav1.0 (1.15.0.1+git20180723+db823502-1) unstable; urgency=medium . * New upstream git snapshot: + Required for ffmpeg 4.0 support (Closes: #888326). * debian/patches/00_plugin-dependencies.patch: + Add back patch to add the shared libraries as plugin dependencies (Closes: #904023). Checksums-Sha1: 6539e2ac838e7755c7dd724a7e056408805fd929 2949 gst-libav1.0_1.15.0.1+git20180723+db823502-1.dsc 64b72e9c1c9c4a0875a43c13e9131fce4964b4d4 9138768 gst-libav1.0_1.15.0.1+git20180723+db823502.orig.tar.xz ef3ec57d451ffa15eebc00dedf6ebfa06ffcb727 12028 gst-libav1.0_1.15.0.1+git20180723+db823502-1.debian.tar.xz 6ef9580b41d343ea3f995ee5e7e50b00ef730318 14242 gst-libav1.0_1.15.0.1+git20180723+db823502-1_amd64.buildinfo 06f6f8e75db6f6c459e339fc2c7c158d39ef48e6 506624 gstreamer1.0-libav-dbg_1.15.0.1+git20180723+db823502-1_amd64.deb 0894402b1e54f651d33b0d107688e267e9c5d94d 197404 gstreamer1.0-libav_1.15.0.1+git20180723+db823502-1_amd64.deb Checksums-Sha256: c9343ef90e4feb81a5c9ab997f64c7cc816ea613a5341bf9542e5a44ad83fe31 2949 gst-libav1.0_1.15.0.1+git20180723+db823502-1.dsc 75960272276773b146b9f8f8232feadb5d499ba52b4af54c8c707510c06ed5b9 9138768 gst-libav1.0_1.15.0.1+git20180723+db823502.orig.tar.xz a3fa6eb444dfbbd1f0580fa24db8a4bc34ecc9b791389e5f42f9071672efbec3 12028 gst-libav1.0_1.15.0.1+git20180723+db823502-1.debian.tar.xz eb0078e0ec372c1313c6cc7ae793bf48d513b7c5455e0568d694b00f5f2bba
Processed: bug 904004 is forwarded to https://github.com/libgit2/libgit2/issues/4737
Processing commands for cont...@bugs.debian.org: > forwarded 904004 https://github.com/libgit2/libgit2/issues/4737 Bug #904004 [libgit2] libgit2 FTBFS on armhf, ppc64el, mips64el randomly Set Bug forwarded-to-address to 'https://github.com/libgit2/libgit2/issues/4737'. > thanks Stopping processing here. Please contact me if you need assistance. -- 904004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897730: marked as done (cpprest: ftbfs with GCC-8)
Your message dated Mon, 23 Jul 2018 12:03:53 + with message-id and subject line Bug#897730: fixed in cpprest 2.10.2-8 has caused the Debian Bug report #897730, regarding cpprest: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 897730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cpprest Version: 2.10.2-6 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-8 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The severity of this report will be raised before the buster release. The full build log can be found at: http://aws-logs.debian.net/2018/05/01/gcc8/cpprest_2.10.2-6_unstable_gcc8.log.gz The last lines of the build log are at the end of this report. To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-8/porting_to.html [...] [ 15%] Building CXX object src/CMakeFiles/cpprest.dir/streams/fileio_posix.cpp.o make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DCPPREST_FORCE_HTTP_CLIENT_ASIO -DCPPREST_FORCE_HTTP_LISTENER_ASIO -DCPPREST_NO_SSL_LEAK_SUPPRESS -Dcpprest_EXPORTS -I/<>/Release/include -I/<>/Release/src/pch -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fno-strict-aliasing -fPIC -Werror -pedantic -Wall -Wextra -Wunused-parameter -Wcast-align -Wcast-qual -Wconversion -Wformat=2 -Winit-self -Winvalid-pch -Wmissing-format-attribute -Wmissing-include-dirs -Wpacked -Wredundant-decls -Wunreachable-code -o CMakeFiles/cpprest.dir/utilities/asyncrt_utils.cpp.o -c /<>/Release/src/utilities/asyncrt_utils.cpp /<>/Release/src/utilities/asyncrt_utils.cpp: In member function 'utility::string_t utility::datetime::to_string(utility::datetime::date_format) const': /<>/Release/src/utilities/asyncrt_utils.cpp:702:42: error: '%s' directive output may be truncated writing up to 8 bytes into a region of size between 1 and 65 [-Werror=format-truncation=] snprintf(output, sizeof(output), "%s%sZ", datetime_str, buf); ^~~~~~ In file included from /usr/include/stdio.h:862, from /usr/include/c++/8/cstdio:42, from /usr/include/c++/8/ext/string_conversions.h:43, from /usr/include/c++/8/bits/basic_string.h:6361, from /usr/include/c++/8/string:52, from /<>/Release/src/pch/stdafx.h:50, from /<>/Release/src/utilities/asyncrt_utils.cpp:14: /usr/include/x86_64-linux-gnu/bits/stdio2.h:64:35: note: '__builtin___snprintf_chk' output between 2 and 74 bytes into a destination of size 65 return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, ~^~~ __bos (__s), __fmt, __va_arg_pack ()); ~ cc1plus: all warnings being treated as errors make[3]: *** [src/CMakeFiles/cpprest.dir/build.make:274: src/CMakeFiles/cpprest.dir/utilities/asyncrt_utils.cpp.o] Error 1 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[3]: *** Waiting for unfinished jobs make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DCPPREST_FORCE_HTTP_CLIENT_ASIO -DCPPREST_FORCE_HTTP_LISTENER_ASIO -DCPPREST_NO_SSL_LEAK_SUPPRESS -Dcpprest_EXPORTS -I/<>/Release/include -I/<>/Release/src/pch -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -fno-strict-aliasing -fPIC -Werror -pedantic -Wall -Wextra -Wunused-parameter -Wcast-align -Wcast-qual -Wconversion -Wformat=2 -Wini
Bug#904319: FTBFS when building binary-packages only
Hi Santiago, Thanks for the report, but could you please provider a more verbose failure report? And could you please test this patch: LC_ALL=C.UTF-8 python3 debian/control.py ``` diff --git a/debian/rules b/debian/rules index 212c9aa..8d21adc 100755 --- a/debian/rules +++ b/debian/rules @@ -39,7 +39,7 @@ autogen: extract-rpms $(AUTOGEN_FILES) chmod +x debian/libmkl-dev.postinst debian/libmkl-dev.prerm debian/libmkl-dev.config override_dh_auto_configure: autogen - python3 debian/control.py # Generate install files and lintian overrides + LC_ALL=C.UTF-8 python3 debian/control.py # Generate install files and lintian overrides # deal with embedded libjs-jquery $(RM) opt/intel/documentation_2018/ja/mkl/ps2018/resources/jquery-1.11.1.min.js ```
Bug#897718: cdebconf: ftbfs with GCC-8
On 07/18/2018 02:09 AM, Cyril Brulebois wrote: > Hi, > > Matthias Klose (2018-05-04): >> The package fails to build in a test rebuild on at least amd64 with >> gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The >> severity of this report will be raised before the buster release. >> >> The full build log can be found at: >> http://aws-logs.debian.net/2018/05/01/gcc8/cdebconf_0.243_unstable_gcc8.log.gz >> The last lines of the build log are at the end of this report. >> >> To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly, >> or install the gcc, g++, gfortran, ... packages from experimental. >> >> apt-get -t=experimental install g++ >> >> Common build failures are new warnings resulting in build failures with >> -Werror turned on, or new/dropped symbols in Debian symbols files. >> For other C/C++ related build failures see the porting guide at >> http://gcc.gnu.org/gcc-8/porting_to.html > > FWIW the severity of this bug report just got upgraded to serious but it > can be directly reproduced in an up-to-date sid system, as gcc-defaults > doesn't seem to have been switched to gcc-8 yet. > > It'd be nice if someone could take a look and fix the bug though. :) > https://salsa.debian.org/installer-team/cdebconf/merge_requests/2 fixes the build failure for me. There's a number of warnings in non-Werror parts of the code base that might be worth looking at, too. Cheers, Julien
Bug#897793: libqtpas: ftbfs with GCC-8
Hi On 21-07-18 16:08, Matthias Klumpp wrote: > The absolutely easiest way to handle these huge symbols files is to > tighten the GCC dependency, make a dummy upload, have it fail on some > architectures, and then use pkgkde-symbolshelper to automatically > download the build logs and patch the symbols file. Last time I did this, I used debomatic for the "dummy" builds to not have to do this in Debian proper. Although, you could of course just do this in experimental with an experimental version and even ignore that version. Paul signature.asc Description: OpenPGP digital signature
Processed (with 1 error): forcibly merging 897899 897775 897756
Processing commands for cont...@bugs.debian.org:
> forcemerge 897899 897775 897756
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS
with GCC 8 (error "Dunno about this gcc")
Bug #897775 {Done: Andreas Beckmann } [src:insighttoolkit4]
itksnap: ftbfs with GCC-8
Failed to forcibly merge 897899: Failure while trying to adjust bugs, please
report this as a bug: Not altering archived bugs; see unarchive..
at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
897756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897756
897775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897775
897899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#904319: FTBFS when building binary-packages only
On Mon, Jul 23, 2018 at 12:16:45PM +, Lumin wrote: > Thanks for the report, but could you please provider a more verbose > failure report? Sure. I've put the full build log here: https://people.debian.org/~sanvila/build-logs/intel-mkl/ This was a binary-indep only build, i.e. "dpkg-buildpackage -A". Assuming "dpkg-buildpackage -A" is not the issue here, you would get full build logs here as well: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/intel-mkl.html but only when the page finally exists. > And could you please test this patch: > > LC_ALL=C.UTF-8 python3 debian/control.py Sorry, I can't test modified packages easily in my autobuilder setup. You should be able to reproduce this using either sbuild or pbuilder. By looking at the proposed patch I bet that this could be reproduced with a simple chroot as well, setting LC_ALL=C before dpkg-buildpackage, but I don't really know. Thanks.
Bug#904133: t-d ftbfs with memory exhaustion on many targets
On 22.07.2018 17:41, Коля Гурьев wrote: > Hi, > > 20.07.2018 14:38, Matthias Klose пишет: >> the package ftbfs at least on armel, and mips* in Debian > > It failed to build due to a missing linker option, -latomic. The fix is > already available[1], but an issue is that the option may add an > unneeded dependency. > >> Did you make any measurements how much better the code is with -flto? I'm >> unsure if it's worth the trouble for a desktop application. > > Deactivation of LTO leads to more memory consumption during compilation. > At least at my laptop building process without -flto requires 5.81 GB of > virtual memory, takes two and a half hours and produces a binary of > 29.7 MB size. In current state, building of the package requires 4.97 GB > of virtual memory, takes about one hour and produces a binary of 23.2 MB > size. To be honest, I have the laptop with 4 GB of RAM, so such a long > time in the first case is understandable. Obviously, without LTO, > results are less good, but we can try to disable link-time optimizations > as an experiment. fyi, I saw the opposite, my builds succeeding without -flto, but failing with -flto (tested only with GCC 8).
Bug#897756: 897775 & 897756 *: ftbfs with GCC-8 (because of an error in insighttooklit4)
Hi Gert, On 2018-07-22 12:45, Gert Wollny wrote: > you marked these two bugs as found in insighttoolkit4/4.12.2-dfsg1-2, > but they should actually have been merged with #897899 (maybe I did > something wrong theer), a bug that was closed by exactly this version. Tried to fix up the metadata with this information and merge the bugs, but the bts chokes there ... so all are now closed and properly found/fixed, but not merged. > Could you ellaborate why do you tagged these bugs like this? I just re- > checked and #897775 was indeed fixed by this version. The bugs were reassigned but not marked as found/fixed anywhere, therefore I assumed they still affected the version in sid. Andreas
Bug#904340: netgen: Depends on obsolete tk8.5
Package: netgen Version: 4.9.13.dfsg-11 Severity: serious In #896085 it has been suggested that tk8.5 should go away before stretch. This bug informs you of this ;-) C.
Processed: Bug #897816 in mwrap marked as pending
Processing control commands: > tag -1 pending Bug #897816 [src:mwrap] mwrap: ftbfs with GCC-8 Added tag(s) pending. -- 897816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904319: FTBFS when building binary-packages only
Thanks for the full log, very helpful! I can reproduce the failure with LC_ALL=POSIX python3 ... and it could be avoided by LC_ALL=C.UTF-8 python3 ... On Mon, Jul 23, 2018 at 02:43:41PM +0200, Santiago Vila wrote: > On Mon, Jul 23, 2018 at 12:16:45PM +, Lumin wrote: > > > Thanks for the report, but could you please provider a more verbose > > failure report? > > Sure. I've put the full build log here: > > https://people.debian.org/~sanvila/build-logs/intel-mkl/ > > This was a binary-indep only build, i.e. "dpkg-buildpackage -A". > > Assuming "dpkg-buildpackage -A" is not the issue here, you would get full > build logs here as well: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/intel-mkl.html > > but only when the page finally exists. > > > And could you please test this patch: > > > > LC_ALL=C.UTF-8 python3 debian/control.py > > Sorry, I can't test modified packages easily in my autobuilder setup. > > You should be able to reproduce this using either sbuild or pbuilder. > By looking at the proposed patch I bet that this could be reproduced > with a simple chroot as well, setting LC_ALL=C before dpkg-buildpackage, > but I don't really know. > > Thanks.
Bug#897816: Bug #897816 in mwrap marked as pending
Control: tag -1 pending Hello, Bug #897816 in mwrap 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/pkg-octave-team/mwrap/commit/a314a77d14aea1974840b40b57eb6c9c7cbbe072 d/p/compile-with-gcc-8.patch: New patch Closes: #897816 (this message was generated automatically) -- Greetings https://bugs.debian.org/897816
Processed: tagging 903860
Processing commands for cont...@bugs.debian.org: > tags 903860 + confirmed pending Bug #903860 [python3-stem] python3-stem: File "/usr/lib/python3/dist-packages/stem/util/test/test_tools.py", line 151 / self.method.async = self / ^ /SyntaxError: invalid syntax Added tag(s) confirmed and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 903860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902117: [Debian-ha-maintainers] Bug#902117: corosync-qdevice will not daemonize/run
On Fri, Jul 06, 2018 at 12:50:42PM +0200, Ferenc Wágner wrote: > Thanks for the report. I've been pretty busy with other tasks, but I'll > check this out as soon as possible, your report isn't forgotten. I ask > for you patience till then. Feri, you still want to check this or should we close this issue? -- Valentin
Processed: python3-morse-simulator: fails to install with python 3.7 as a supported python version
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 902646 903423 903016 903527 902715 903031 903218 903528 902794 903522 902766 904298 903457 903558 902757 903826 902650 903145 903784 902900 903525 903526 902761 903529 903030 902989 902631 903388 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904343 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904343: python3-morse-simulator: fails to install with python 3.7 as a supported python version
Package: python3-morse-simulator Version: 1.4-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3-morse-simulator (1.4-3) ... File "/usr/lib/python3/dist-packages/morse/core/request_manager.py", line 140 def register_service(self, component_name, callback, service_name = None, async = False): ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/morse/core/services.py", line 110 def do_service_registration(fn, component_name = None, service_name = None, async = False, request_managers = None): ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/morse/middleware/ros_request_manager.py", line 396 return services.service(fn, component = None, name = name, async = True) ^ SyntaxError: invalid syntax dpkg: error processing package python3-morse-simulator (--configure): installed python3-morse-simulator package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in python 3.7 cheers, Andreas morse-simulator=1.4-3.log.gz Description: application/gzip
Processed: block 902788 with 902817
Processing commands for cont...@bugs.debian.org: > block 902788 with 902817 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 903528 902631 903388 902757 903784 903031 903558 903522 902766 903030 903016 902761 902646 902900 903826 902989 902794 903525 903529 904298 903457 903423 903218 902715 904343 903527 903526 902650 903145 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 902817 > thanks Stopping processing here. Please contact me if you need assistance. -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#897816: marked as done (mwrap: ftbfs with GCC-8)
Your message dated Mon, 23 Jul 2018 13:21:24 + with message-id and subject line Bug#897816: fixed in mwrap 0.33-7 has caused the Debian Bug report #897816, regarding mwrap: ftbfs with GCC-8 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 897816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mwrap Version: 0.33-4 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-8 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The severity of this report will be raised before the buster release. The full build log can be found at: http://aws-logs.debian.net/2018/05/01/gcc8/mwrap_0.33-4_unstable_gcc8.log.gz The last lines of the build log are at the end of this report. To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-8/porting_to.html [...] fprintf(fp, "const mxArray*", v->name); ^~~~ mwrap-cgen.cc:300:21: warning: too many arguments for format [-Wformat-extra-args] fprintf(fp, "%s*", v->basetype, v->name); ^ mwrap-cgen.cc: In function 'void mex_unpack_input_array(FILE*, Var*)': mwrap-cgen.cc:683:13: warning: too many arguments for format [-Wformat-extra-args] "} else\n" ^~ "in%d_ = NULL;\n", ~ g++ -Wl,-z,relro -o ../mwrap mwrap.o lex.yy.o mwrap-ast.o mwrap-typecheck.o mwrap-mgen.o mwrap-cgen.o make[2]: Leaving directory '/<>/src' make[1]: Leaving directory '/<>' dh_auto_test -a make -j8 -Oline test make[1]: Entering directory '/<>' (cd testing; make) make[2]: Entering directory '/<>/testing' make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[2]: Leaving directory '/<>/testing' make[2]: Entering directory '/<>/testing' ../mwrap -mex test_transfersmex \ -c test_transfersmex.cc \ -m test_transfers.m test_transfers.mw mkoctfile --mex test_transfersmex.cc ../mwrap -cppcomplex \ -mex test_cpp_complexmex \ -c test_cpp_complexmex.cc \ -m test_cpp_complex.m test_cpp_complex.mw mkoctfile --mex test_cpp_complexmex.cc ../mwrap -c99complex \ -mex test_c99_complexmex \ -c test_c99_complexmex.c \ -m test_c99_complex.m test_c99_complex.mw mkoctfile --mex test_c99_complexmex.c ../mwrap -cppcomplex test_syntax.mw 2> test_syntax.log make[2]: [Makefile:28: test_syntax] Error 139 (ignored) diff test_syntax.log test_syntax.ref 2c2 < Segmentation fault --- > Parse error (test_syntax.mw:8): syntax error, unexpected $end, expecting ';' make[2]: *** [Makefile:29: test_syntax] Error 1 make[2]: Leaving directory '/<>/testing' make[1]: *** [Makefile:9: test] Error 2 make[1]: Leaving directory '/<>' dh_auto_test: make -j8 -Oline test returned exit code 2 make: *** [debian/rules:5: build-arch] Error 25 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 --- End Message --- --- Begin Message --- Source: mwrap Source-Version: 0.33-7 We believe that the bug you reported is fixed in the latest version of mwrap, 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 897...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rafael Laboissiere (supplier of updated mwrap 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:
Bug#904347: prewikka: /bin/prewikka-crontab fails with SyntaxError
Package: prewikka Version: 4.1.5-2 Severity: serious Hi, /bin/prewikka-crontab fails with a SyntaxError: $ /bin/prewikka-crontab File "/bin/prewikka-crontab", line 74 os.umask(027) ^ SyntaxError: invalid token Andreas
Bug#904350: snakemake: fails to install with python 3.7
Package: snakemake Version: 5.1.5-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up snakemake (5.1.5-1) ... File "/usr/lib/python3/dist-packages/snakemake/shell.py", line 69 async=False, ^ SyntaxError: invalid syntax dpkg: error processing package snakemake (--configure): installed snakemake package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in python 3.7 cheers, Andreas snakemake=5.1.5-1.log.gz Description: application/gzip
Bug#903698: marked as done (sphinxbase: build appears broken for multiple python3 versions)
Your message dated Mon, 23 Jul 2018 13:34:11 +
with message-id
and subject line Bug#903698: fixed in dh-python 3.20180723
has caused the Debian Bug report #903698,
regarding sphinxbase: build appears broken for multiple python3 versions
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.)
--
903698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxbase
Version: 0.8+5prealpha+1-2
Severity: serious
Hi all,
sphinxbase is currently involved in the python3.7 "transition"¹. I
noticed that sphinxbase was rebuild, but that is was still listed in the
"bad" category. I took a look at the amd64 build log² and spotted the
following some oddities in python3-sphinxbase.
1) it has only has the 3.6 dependencies (hence listed as bad)
2) it only has 3.7 site-packages files
3) _sphinxbase.cpython-37m-x86_64-linux-gnu.so points to a non-exitent
file. The file is in the 3.7 site-packages directory.
4) python3 versions in the build are first 3.7 and then 3.6, they seem
to be using the same build directory.
I think this is caused by the fact that we loop over $pyver in the
d/rules file, but apparently that is broken for multiple python3 versions.
I think the package is probably not working currently hence I file this
bug. (I don't know how to fix it properly yet, maybe Samuel has ideas?).
Paul
¹ https://release.debian.org/transitions/html/python3.7.html
²
https://buildd.debian.org/status/fetch.php?pkg=sphinxbase&arch=amd64&ver=0.8%2B5prealpha%2B1-2%2Bb1&stamp=1530298945&raw=0
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: dh-python
Source-Version: 3.20180723
We believe that the bug you reported is fixed in the latest version of
dh-python, 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 903...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Piotr Ożarowski (supplier of updated dh-python package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 23 Jul 2018 14:39:41 +0200
Source: dh-python
Binary: dh-python
Architecture: source all
Version: 3.20180723
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski
Changed-By: Piotr Ożarowski
Description:
dh-python - Debian helper tools for packaging Python libraries and applicatio
Closes: 739500 801710 894203 903698
Changes:
dh-python (3.20180723) unstable; urgency=medium
.
* dh-python depends on python3-distutils (as most package that use dh-python
would have to depend on it anyway, closes: 894203)
* dh_python{2,3}:
- fix \.so.* symlink renaming for non-default Python versions
(closes: 739500, 903698)
- when files cannot be shared between Python versions because of
differences, print (in --verbose mode) a unified diff for diagnostic
purposes (closes: 801710, thanks to Barry Warsaw for the original patch)
Checksums-Sha1:
f794b3f8da70ad54c22b31de2620debca5f70f36 1874 dh-python_3.20180723.dsc
707b59e4688ffd6a960f3733341314a02d589940 96212 dh-python_3.20180723.tar.xz
122e4f6f5c65bc26fc6c10962185774127b33d88 94204 dh-python_3.20180723_all.deb
7ed6cec750945864a2dfd27e1033cd0f7eab3c52 6556
dh-python_3.20180723_amd64.buildinfo
Checksums-Sha256:
10e07cc33c7085d663b9ee8d201b3ae2d6f6db76b5429b2a8db6a846f12eecd4 1874
dh-python_3.20180723.dsc
4faf130d654eba94e2551c3e180a75893df0773448d492fea32f15a4eea4bcfa 96212
dh-python_3.20180723.tar.xz
b71ce8ba73b89257963bb043605123a7146f810097846437d4a2b74aab0cd8ec 94204
dh-python_3.20180723_all.deb
14d1cc2427817037994b24ea173b135e2ba07199be8851892434fe0aba6695e8 6556
dh-python_3.20180723_amd64.buildinfo
Files:
a934f3f0dc4794649970aa4fd6d6e1d7 1874 python optional dh-python_3.20180723.dsc
a4c1f1650959b6981b91aa9981c02f32 96212 python optional
dh-python_3.20180723.tar.xz
8df1c817a035acf478f5e03d9e00fd14 94204 python optional
dh-python_3.20180723_all.deb
3410b3fb467701849f6b38bb2eed454a 6556 python optional
dh-python_3.20180723_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEHS+omFjar2IXhi33rvbxoqdFdkUFAltV0xsACgkQrvbxoqdF
dkXIrw/
Bug#897780: many packages automremoval due to GCC 8
On Mon, Jul 23, 2018 at 02:41:29PM +0200, Mattia Rizzolo wrote: > > [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897780 > > Looking at that bug, the 7 new symbols that appeared are of that > category I was talking about (looking at the unmangled naming that > c++filt reports they are things like: > > + std::_Rb_tree_iterator std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > > > std::_Rb_tree std::pair std::char_traits, std::allocator >, > std::allocator, > std::allocator > > > >, std::_Select1st std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > > >, std::greater, > std::allocator std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > > > > >::_M_emplace_hint_unique std::tuple, std::tuple<> >(std::_Rb_tree_const_iterator const, std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > > >, > std::piecewise_construct_t const&, std::tuple&&, std::tuple<>&&)@Base > 2.4.0-3 > > which is ... not something people should usually care about…), and if > added they should have the '(optional)' tag (incidentally, it feels to me > that also all the surrounding symbols should). However, that's not the > error, dpkg-gensymbols wouldn't fail for new symbols by default, but > only if some disappear: you should check the ones that disappeared. OK, maintainer in CC. > Also, I noticed the rules file is doing some funky renaming to have the > symbols file apply only on amd64. I recommend you go read > dpkg-gensymbols(1) and discover architecture-specific symbols file. This was actually my recommendation following an "the perfect is the enemy of the good" principle. We checked the possibility of having architecture-specific symbols files for all libbpp* libs. However, it turned out that the effort to maintain this would be at least one order of magnitude higher than every other maintenance work for these packages. Since having symbols files on amd64 in principle serves the purpose of detecting ABI changes and the software is in practice used only here I suggested this solution to the maintainer (who is also upstream). (This should be somewhere recorded on one Debian Med list - I'm to offline-ish currently to seek for this.) Kind regards Andreas. -- http://fam-tille.de
Processed: snakemake: fails to install with python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 903031 902761 903526 902757 903527 902817 903218 902631 903558 902715 903826 904298 904343 902794 903388 902650 903423 903457 903525 903016 903529 903784 903030 902989 903522 902900 902766 902646 903145 903528 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904350 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904350: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python3-astroquery: fails to install with python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 903527 902794 903522 904298 903826 902650 904350 903529 902646 902761 903145 903423 903218 902757 902715 904343 903526 903457 902766 903525 903558 903030 902900 903016 903388 903784 903528 902631 902989 903031 902817 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904351 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904351: python3-astroquery: fails to install with python 3.7
Package: python3-astroquery Version: 0.3.8+dfsg-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3-astroquery (0.3.8+dfsg-2) ... File "/usr/lib/python3/dist-packages/astroquery/vo_conesearch/conesearch.py", line 26 from .async import AsyncBase ^ SyntaxError: invalid syntax dpkg: error processing package python3-astroquery (--configure): installed python3-astroquery package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in python 3.7 cheers, Andreas python3-astroquery=0.3.8+dfsg-2.log.gz Description: application/gzip
Bug#902631: devscripts: CI fails in unstable due to Python 3.7
Le dimanche 22 juillet 2018 à 20:43:02-0400, Sandro Tosi a écrit : > On Sun, Jul 22, 2018 at 8:31 PM Mattia Rizzolo wrote: > > > > On Sun, Jul 22, 2018 at 03:52:04PM -0400, Sandro Tosi wrote: > > > thanks for ignoring the next paragraph in that email, so let me re-add it > > > here: > > > > I didn't ignore it, I explicitly picked on your first, fairly taunting, > > and inappropriately passive-aggressive sentence (like this one). > > good good Mmh, I tend to admit that Sandro's answers can be blunt. I assume it may be connected with a busy life, but sometimes it's a little awkward. That said, I'd rather all of us to act/behave accordingly to [1], please. Because we're all smart people, with good intentions, who share common values (the ones that made us join Debian). :) > > > since astroid/pylint only support python 3.4+, it is not as simple as > > > package the new version and upload it; i'm not even (yet) sure buster > > > should have 2.0 but maybe it should to 1.9 > > > > This is a fairly common situation for distributors. > > > > Did you also evaluate the feasibility and practicality of working on a > > patch to introduce py3.7 compatibility to the current 1.6.5? > > no, i didnt look into it myself: upstream dismissed the forwarded bug > saying to upgrade to 2.0 to get 3.7 support. > > if someone wants to try and dedicate time to that effort, that'd be > welcome and please attach a patch here when ready. Would you consider repackaging 1.6.5 without py3 support and provide another package with exclusive py3 support? That'd ease the drop of py2 in a few years, and, also, avoid big horrible patches. If you agree with this kind of idea I'd be pleased to provide the new package work and a team patch for the current package. If you really wish to go by a patch for 1.6.5, I'll try to do it after the end of my PhD thesis manuscript writing. Sincerely [1] https://www.debian.org/code_of_conduct.en.html -- Pierre-Elliott Bécue GPG: 9AE0 4D98 6400 E3B6 7528 F493 0D44 2664 1949 74E2 It's far easier to fight for one's principles than to live up to them. signature.asc Description: PGP signature
Bug#897792: [Pkg-kde-extras] Bug#897792: libqaccessibilityclient: ftbfs with GCC-8
¡Hola! El 2018-05-04 a las 12:22 +, Matthias Klose escribió: Package: src:libqaccessibilityclient Version: 0.1.1-5 Severity: normal Tags: sid buster User: debian-...@lists.debian.org Usertags: ftbfs-gcc-8 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The severity of this report will be raised before the buster release. The full build log can be found at: http://aws-logs.debian.net/2018/05/01/gcc8/libqaccessibilityclient_0.1.1-5_unstable_gcc8.log.gz The last lines of the build log are at the end of this report. To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-8/porting_to.html It seems to me that src:libqaccessibilityclient currently has not reverse dependencies, and since it's still qt4 based, we might want to get rid of it. Although, there is an "unstable" qt5 release (https://download.kde.org/unstable/libqaccessibilityclient/), and recent versions of kmag seem to be trying to use that. I'm ccing Sandro, as he might be working in kmag and adding the support of libqaccessibilityclient to our packages [1]. [1]: https://salsa.debian.org/qt-kde-team/kde/kmag/commit/6fd9637477b4eb9da465e3c5fe782352a20f607a Sandro, if you plan to upload libqaccessibilityclient 0.2 please close this issue with it. Happy hacking, -- "Executive ability is deciding quickly and getting somebody else to do the work." -- Pollard's Postulate Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature
Bug#903860: marked as done (python3-stem: File "/usr/lib/python3/dist-packages/stem/util/test/test_tools.py", line 151 / self.method.async = self
Your message dated Mon, 23 Jul 2018 13:51:23 + with message-id and subject line Bug#903860: fixed in python-stem 1.6.0-2 has caused the Debian Bug report #903860, regarding python3-stem: File "/usr/lib/python3/dist-packages/stem/util/test/test_tools.py", line 151 / self.method.async = self / ^ /SyntaxError: invalid syntax 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.) -- 903860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903860 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-stem Version: 1.6.0-1 Severity: serious Tags: a11y Justification: fails to build from source Dear Maintainer, * What led up to the situation? Package was pulled in as a dependency for nyx which is a dependency for tor-arm and onionshare * What exactly did you do (or not do) that was effective (or ineffective)? Have tried purging and building from source. Have dpkg --purge to reinstall the package but was also not effective. * What was the outcome of this action? Package still will not install * What outcome did you expect instead? Hoping a rebuild would have helped -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-stem depends on: ii python3 3.6.6-1 python3-stem recommends no packages. python3-stem suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: python-stem Source-Version: 1.6.0-2 We believe that the bug you reported is fixed in the latest version of python-stem, 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 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ulises Vitulli (supplier of updated python-stem package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 23 Jul 2018 10:25:51 -0300 Source: python-stem Binary: python-stem python3-stem Architecture: source all Version: 1.6.0-2 Distribution: unstable Urgency: high Maintainer: Ulises Vitulli Changed-By: Ulises Vitulli Description: python-stem - Tor control library for Python python3-stem - Tor control library for Python 3 series Closes: 903860 Changes: python-stem (1.6.0-2) unstable; urgency=high . * Patch for py3.7 compat issues on reserved words (Closes: #903860). Checksums-Sha1: 3b9fe6a0d44305586401285c32c949998f042a1a 1989 python-stem_1.6.0-2.dsc dba9413ea52f6f6c011c556481816b7be18449dc 4248 python-stem_1.6.0-2.debian.tar.xz 004e810433ee44345df79185a2c22bdee77dfc77 256716 python-stem_1.6.0-2_all.deb 130cdfe8b1d20b09ded7e31618aeac6278912aba 7430 python-stem_1.6.0-2_amd64.buildinfo accd177badb2bc6414f244c8b4b716a9c79dc1a3 256812 python3-stem_1.6.0-2_all.deb Checksums-Sha256: e2a8316462b3157c89082f1ae1e00673c00f47835efa892ef8f00b31012d77ed 1989 python-stem_1.6.0-2.dsc c2e96ea80a47eae9b4a2e93358ded42899240f82483424b9387d9c980800b774 4248 python-stem_1.6.0-2.debian.tar.xz 3404080e3370ac7cf25748d2714a0962c8a0c3f28455d35f9d06f417c02b0ca4 256716 python-stem_1.6.0-2_all.deb 61e9bc395600172dba2d545b2ce48d6f374d84866162770f8ece813863e3ad09 7430 python-stem_1.6.0-2_amd64.buildinfo dfdb804372a2c40996b840fd976677760d49a6e1e6e96250d456327f6e32726f 256812 python3-stem_1.6.0-2_all.deb Files: 990c5fe47f0e0a300ee5403bd19e6301 1989 python optional python-stem_1.6.0-2.dsc c23f2793fa9b099b5205292384c0a7a1 4248 python optional python-stem_1.6.0-2.debian.tar.xz 1eede75c75a040dbad58c8bb6b2dc0fc 256716 python optional python-stem_1.6.0-2_all.deb f85115aa890af4f8af11080de3eab449 7430 python optional python-stem_1.6.0-2_amd64.buildinfo 13aac80a6c7eb77f1ef07c5fc42df1aa 256812 python optional python3-stem_1.6.0-2_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvQqKQ/Vt
Bug#904357: python3-pysnmp4: fails to install with python 3.7
Package: python3-pysnmp4 Version: 4.4.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3-pysnmp4 (4.4.3-1) ... File "/usr/lib/python3/dist-packages/pysnmp/carrier/asyncio/dgram/base.py", line 86 self._lport = asyncio.async(c) ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/pysnmp/carrier/asyncio/dispatch.py", line 72 self.loopingcall = asyncio.async(self.handle_timeout()) ^ SyntaxError: invalid syntax dpkg: error processing package python3-pysnmp4 (--configure): installed python3-pysnmp4 package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in python 3.7 cheers, Andreas ceilometer-common=1%10.0.0-5.log.gz Description: application/gzip
Processed: upstream tickets
Processing commands for cont...@bugs.debian.org: > forwarded 897808 https://github.com/measurement-kit/measurement-kit/pull/1614 Bug #897808 [src:measurement-kit] measurement-kit: ftbfs with GCC-8 Set Bug forwarded-to-address to 'https://github.com/measurement-kit/measurement-kit/pull/1614'. > forwarded 897817 https://bugzilla.nasm.us/show_bug.cgi?id=3392461 Bug #897817 [src:nasm] nasm: ftbfs with GCC-8 Set Bug forwarded-to-address to 'https://bugzilla.nasm.us/show_bug.cgi?id=3392461'. > stop Stopping processing here. Please contact me if you need assistance. -- 897808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897808 897817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python3-pysnmp4: fails to install with python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 904343 902715 903145 903388 903526 903826 904298 902900 904351 902794 902761 903525 903457 903016 903558 902766 902646 902989 902817 903528 903522 903527 903784 902631 903031 904350 903218 902757 902650 903423 903529 903030 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904357 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904357 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904358: python3-aiozmq: fails to install with python 3.7
Package: python3-aiozmq Version: 0.7.1-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3-aiozmq (0.7.1-2) ... File "/usr/lib/python3/dist-packages/aiozmq/rpc/base.py", line 251 fut = asyncio.async(coro, loop=self.loop) ^ SyntaxError: invalid syntax dpkg: error processing package python3-aiozmq (--configure): installed python3-aiozmq package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in python 3.7 cheers, Andreas python3-aiozmq=0.7.1-2.log.gz Description: application/gzip
Bug#904359: pandas 0.23.3 update needed for Python 3.7 compatibility
Package: src:pandas Version: 0.22.0-8 Severity: serious Tags: sid buster an update to pandas 0.23.3 is needed for Python 3.7 compatibility. Please package the new upstream version.
Processed: python3-aiozmq: fails to install with python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 904343 902631 904351 903030 902757 903784 902900 902794 903528 902715 903388 903525 903527 904350 904298 902817 903031 903558 903529 902650 902766 902989 902646 903016 903218 903457 903522 903423 903145 902761 903526 904357 903826 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904358 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904358: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python3-aiopg: fails to install with Python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 903218 903016 903525 902900 903784 904357 903457 903522 903528 903145 902757 904351 902766 902631 903529 902817 904358 903030 902646 902761 903527 903031 902794 903423 902989 902715 904343 903558 903526 904350 903388 903826 904298 902650 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904361 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904361: python3-aiopg: fails to install with Python 3.7
Package: python3-aiopg Version: 0.14.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3-aiopg (0.14.0-1) ... File "/usr/lib/python3/dist-packages/aiopg/connection.py", line 109 self._conn = psycopg2.connect(dsn, async=True, **kwargs) ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/aiopg/utils.py", line 18 ensure_future = asyncio.async ^ SyntaxError: invalid syntax dpkg: error processing package python3-aiopg (--configure): installed python3-aiopg package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in Python 3.7 cheers, Andreas python3-aiopg=0.14.0-1.log.gz Description: application/gzip
Processed: python3-applicationinsights: fails to install with Python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 903529 903030 902989 904357 903218 902761 902650 902900 903526 904350 902817 904358 904343 903145 903826 902757 904361 903558 903016 903525 902631 903528 903527 903522 904351 902794 903031 902766 902715 904298 903388 903457 903784 903423 902646 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904363 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904363: python3-applicationinsights: fails to install with Python 3.7
Package: python3-applicationinsights Version: 0.11.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3-applicationinsights (0.11.0-1) ... File "/usr/lib/python3/dist-packages/applicationinsights/channel/contracts/RemoteDependencyData.py", line 256 def async(self): ^ SyntaxError: invalid syntax dpkg: error processing package python3-applicationinsights (--configure): installed python3-applicationinsights package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in Python 3.7 cheers, Andreas python3-applicationinsights=0.11.0-1.log.gz Description: application/gzip
Bug#862678: Switch from network-manager-dev to libnm-dev
On Sun, 22 Jul 2018 19:04:01 -0400, Ari Pollak wrote: > Thanks Gregor. I'll upload a new version with this patch. Great, thank you! Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Stan Getz & Astrud Gilberto: Desafinado signature.asc Description: Digital Signature
Bug#904364: python3-azure: fails to install with Python 3.7
Package: python3-azure Version: 20170915+git-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3-azure (20170915+git-1) ... File "/usr/lib/python3/dist-packages/azure/servicemanagement/schedulermanagementservice.py", line 113 return self._perform_put(path, body, async=True) ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/azure/servicemanagement/servicemanagementclient.py", line 372 def _perform_put(self, path, body, async=False, x_ms_version=None): ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/azure/servicemanagement/servicemanagementservice.py", line 235 async=True) ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/azure/servicemanagement/websitemanagementservice.py", line 195 xml, async=True) ^ SyntaxError: invalid syntax dpkg: error processing package python3-azure (--configure): installed python3-azure package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in Python 3.7 cheers, Andreas python3-azure=20170915+git-1.log.gz Description: application/gzip
Processed: python3-azure: fails to install with Python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 903218 904350 904343 903031 902631 902766 904358 903388 903457 902817 903016 904361 903558 903526 902650 904363 902646 903528 903525 902761 902900 903784 903522 902757 902989 903030 903527 903145 904351 903529 904298 903423 902715 903826 902794 904357 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904364 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904364 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904365: python3-cs: fails to install with Python 3.7
Package: python3-cs Version: 2.1.6-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3-cs (2.1.6-1) ... File "/usr/lib/python3/dist-packages/cs/__init__.py", line 101 if 'Async' not in command and 'jobid' in response and not options.async: ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/cs/client.py", line 36 from cs.async import AIOCloudStack # noqa ^ SyntaxError: invalid syntax dpkg: error processing package python3-cs (--configure): installed python3-cs package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in Python 3.7 cheers, Andreas python3-cs=2.1.6-1.log.gz Description: application/gzip
Processed: python3-cs: fails to install with Python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 904343 903529 903522 903218 902715 903031 904357 902794 902900 903826 902757 902989 904350 903525 903016 903558 904298 903423 902650 902761 902646 903784 903528 904364 903526 904358 904351 903388 902817 903030 904363 903527 902631 903457 903145 902766 904361 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904365 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904366: mailutils-config and the mailutils tool are unusable in 1:3.4-1
Package: libmailutils-dev
Version: 1:3.4-1
Severity: serious
Hello,
Invoking mailutils-config with any argument results in:
$ mailutils-config --info
/usr/bin/mailutils-config: 115: /usr/bin/mailutils-config: mailutils: not found
This script is in fact a wrapper around the 'mailutils' tool, but the
tool itself is included in another packet, mailutils. Now, installing
mailutils doesn't make the situation any better:
$ mailutils-config --info
mailutils: don't know what info is
This is because the mailutils tool is a dispatcher command that calls
one of the specific standalone binaries from the pkglibexecdir to
perform the requested action (see the commit 444d20f3,
http://git.savannah.gnu.org/cgit/mailutils.git/commit/?id=444d20f3c).
Now, none of these binaries is included in the package (nor in any other
sub-package of mailutils, for that matter).
The script mailutils-config is used by the AM_MAILUTILS macro, defined in
/usr/share/aclocal/mailutils.m4. This means that this bug makes it
impossible to build any projects that depend on Mailutils and use this
macro in configure.ac to detect its presence. Therefore I qualified it
as serious.
To fix this, I would suggest to move usr/bin/mailutils from package
'mailutils' to 'libmailutils-dev' and to add all mailutils-*
binaries from the pkglibexecdir directory. The proposed patch is
attached.
The patch fixes the reported bug, yet reveals another (minor)
one. Please note the 'usr/lib/mailutils/mailutils/' path in the resulting
libmailutils-dev.install file. This is because
/usr/share/cdbs/1/class/autotools-vars.mk from cdbs sets the
DEB_CONFIGURE_LIBEXECDIR variable to "\$${prefix}/lib/$(DEB_SOURCE_PACKAGE)",
thereby defeating the purpose of libexecdir, for which GNU standards say
that this is
[t]he directory for installing executable programs to be run by other
programs rather than by users.
[...]
The definition of 'libexecdir' is the same for all packages
This looks like yet another instance of the bug fixed long ago in debhelper:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541458. Perhaps it's
worth reporting to cdbs hackers. Anyway, adding
DEB_CONFIGURE_LIBEXECDIR = \$${prefix}/lib
to the debian/rules will fix this as well (obviously the paths in the
attached file should be changed accordingly).
Best regards,
Sergey
diff -pur debian-orig/libmailutils-dev.install debian/libmailutils-dev.install
--- debian-orig/libmailutils-dev.install 2018-07-23 13:54:47.755922366 +
+++ debian/libmailutils-dev.install 2018-07-23 13:58:06.908660263 +
@@ -1,4 +1,6 @@
usr/bin/mailutils-config
+usr/bin/mailutils
+usr/lib/mailutils/mailutils/mailutils-*
usr/include/mailutils/*
usr/lib/*/lib*.so
usr/share/aclocal/mailutils.m4
diff -pur debian-orig/mailutils.install debian/mailutils.install
--- debian-orig/mailutils.install 2018-07-23 13:54:47.758922443 +
+++ debian/mailutils.install 2018-07-23 13:58:44.483808011 +
@@ -1,7 +1,6 @@
usr/bin/dotlock.mailutils
usr/bin/frm.mailutils
usr/bin/from.mailutils
-usr/bin/mailutils
usr/bin/mail.mailutils
usr/bin/messages.mailutils
usr/bin/mimeview
Processed: linux-show-player: fails to install with Python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 902650 902794 903526 904351 902757 904298 904363 902715 903016 903457 903558 902766 903528 902646 903030 903031 903218 904357 904350 902989 903529 902761 903527 902631 903784 903145 904361 904358 902900 903388 903826 904364 904365 903423 902817 903525 903522 904343 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904367 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904367: linux-show-player: fails to install with Python 3.7
Package: linux-show-player Version: 0.5-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up linux-show-player (0.5-1) ... File "/usr/lib/python3/dist-packages/lisp/core/decorators.py", line 26 def async(target): ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/lisp/core/signal.py", line 31 from lisp.core.decorators import async ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/lisp/cues/cue.py", line 24 from lisp.core.decorators import async ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/lisp/cues/media_cue.py", line 25 from lisp.core.decorators import async ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/lisp/modules/action_cues/command_cue.py", line 25 from lisp.core.decorators import async ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/lisp/modules/action_cues/volume_control.py", line 28 from lisp.core.decorators import async ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/lisp/modules/remote/controller.py", line 26 from lisp.core.decorators import async ^ SyntaxError: invalid syntax dpkg: error processing package linux-show-player (--configure): installed linux-show-player package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in Python 3.7 cheers, Andreas linux-show-player=0.5-1.log.gz Description: application/gzip
Processed: python3-panoramisk: fails to install with Python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 904363 903218 902631 902715 902794 902650 902766 903526 903826 903784 904298 903016 904367 904343 902757 904361 903423 903558 902817 904364 904351 903528 903527 904358 902900 903525 902646 904357 904350 903030 902989 903031 903457 903388 903145 904365 903522 903529 902761 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904368 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904368: python3-panoramisk: fails to install with Python 3.7
Package: python3-panoramisk
Version: 1.0-1
Severity: serious
Tags: sid buster
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the attached log (scroll to the bottom...):
Setting up python3-panoramisk (1.0-1) ...
File "/usr/lib/python3/dist-packages/panoramisk/actions.py", line 64
elif msg.endswith('successfully queued') and self.async != 'false':
^
SyntaxError: invalid syntax
File "/usr/lib/python3/dist-packages/panoramisk/manager.py", line 212
asyncio.async(ret, loop=self.loop)
^
SyntaxError: invalid syntax
dpkg: error processing package python3-panoramisk (--configure):
installed python3-panoramisk package post-installation script subprocess
returned error exit status 1
"async" has become a reserved keyword in Python 3.7
cheers,
Andreas
panoramisk=1.0-1.log.gz
Description: application/gzip
Bug#904369: patroni: fails to install with Python 3.7
Package: patroni Version: 1.4.4-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up patroni (1.4.4-1) ... File "/usr/lib/python3/dist-packages/patroni/ha.py", line 610 'offline': dict(stop='fast', checkpoint=False, release=False, offline=True, async=False), ^ SyntaxError: invalid syntax dpkg: error processing package patroni (--configure): installed patroni package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in Python 3.7 cheers, Andreas patroni=1.4.4-1.log.gz Description: application/gzip
Processed: patroni: fails to install with Python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 903525 904363 903784 904361 903527 904298 903031 903522 903528 903457 904367 903145 904365 904368 903529 904350 902631 904364 902715 902817 902989 903526 902757 904358 902900 903030 903016 902646 904343 904351 903826 903558 902650 903388 902761 902766 903423 902794 904357 903218 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904369 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904370: oca-core: fails to install with Python 3.7
Package: oca-core Version: 11.0.20180420-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up oca-core (11.0.20180420-1) ... File "/usr/lib/python3/dist-packages/odoo/addons/base/ir/ir_qweb/assetsbundle.py", line 103 def to_html(self, sep=None, css=True, js=True, debug=False, async=False, url_for=(lambda url: url)): ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/odoo/addons/base/ir/ir_qweb/ir_qweb.py", line 194 def _get_asset(self, xmlid, options, css=True, js=True, debug=False, async=False, values=None): ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/odoo/addons/website/models/ir_qweb.py", line 26 def _get_asset(self, xmlid, options, css=True, js=True, debug=False, async=False, values=None): ^ SyntaxError: invalid syntax dpkg: error processing package oca-core (--configure): installed oca-core package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in Python 3.7 cheers, Andreas oca-core=11.0.20180420-1.log.gz Description: application/gzip
Processed: oca-core: fails to install with Python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 904364 903527 903528 902631 903826 903218 904358 902650 903526 902757 903388 903423 903016 903031 904351 903525 904357 902900 902989 904363 902794 902817 902646 904361 903529 904368 903457 902715 902761 904369 904367 903030 902766 903558 904298 903145 903784 904350 904365 904343 903522 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904370 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904370 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: openscap-daemon: fails to install with Python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 904363 903527 902631 903784 903826 903016 903218 902650 902761 904370 903145 904361 904298 902900 904369 904357 904343 902817 904350 904368 902757 903457 902766 904365 902715 904351 904358 903031 903423 903529 903526 903030 904364 903558 902646 904367 902794 903528 903522 903525 902989 903388 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904371 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904371: openscap-daemon: fails to install with Python 3.7
Package: openscap-daemon Version: 0.1.10-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up openscap-daemon (0.1.10-2) ... File "/usr/lib/python3/dist-packages/openscap_daemon/dbus_daemon.py", line 84 return self.system.async.get_status() ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/openscap_daemon/system.py", line 29 from openscap_daemon import async ^ SyntaxError: invalid syntax dpkg: error processing package openscap-daemon (--configure): installed openscap-daemon package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in Python 3.7 cheers, Andreas openscap-daemon=0.1.10-2.log.gz Description: application/gzip
Bug#902470: Works with tox, fails to nose
I made a quick test and could reproduce the error using nose for testing. However, using tox, all tests are ok (which is the tool described in readme of repo)
Processed: python3-opcua: fails to install with Python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 902989 904357 903145 904365 904298 903423 904371 904364 903388 902766 902631 902761 902646 903016 903784 904343 904367 902650 904350 903526 903527 904370 902794 903528 903030 904361 903218 903457 903529 902817 903826 903525 903031 904351 902900 904368 902715 903558 904363 904358 903522 904369 902757 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904373 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902470: Relates to numpy
Installing numpy 1.13.3 (from pypi) which is used version in tox.ini makes tests OK. Fails with numpy 1.14.5 (debian default) Maybe a bug should be filled upstream
Bug#904373: python3-opcua: fails to install with Python 3.7
Package: python3-opcua Version: 0.95.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3-opcua (0.95.1-1) ... File "/usr/lib/python3/dist-packages/opcua/common/utils.py", line 171 task = asyncio.async(coro, loop=self.loop) ^ SyntaxError: invalid syntax dpkg: error processing package python3-opcua (--configure): installed python3-opcua package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in Python 3.7 cheers, Andreas python-opcua-tools=0.95.1-1.log.gz Description: application/gzip
Bug#902470: created upstream issue
I created an issue on upstream repo [0] A temporary workaround could be to skip this test waiting for an upstream resolution or explanation. Indeed, problem may have no real incidence on usage but only on tests. Bug could remain opened but lowered as it does not prevent its usage or build. [0] https://github.com/influxdata/influxdb-python/issues/622
Bug#902470: Relates to numpy
On 2018-07-23 11:23 AM, olivier sallou wrote: > Maybe a bug should be filled upstream Hello, Thank you for caring and putting time into this. The bug is in influxdb-python due to a breaking change in numpy. I already marked the bug as forwarded with a link to the upstream bug, maybe you missed it? - https://github.com/influxdata/influxdb-python/pull/596 Forwarded tags don't appear in the discussion thread of the bug but they appear on the top of the page: - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902470 The reason that tests pass with tox is that tox will download specific versions of packages so it will not test with Debian's packages. Cheers, -- Alexandre Viau av...@debian.org signature.asc Description: OpenPGP digital signature
Bug#902470: Relates to numpy
Le lun. 23 juil. 2018 à 17:38, Alexandre Viau a écrit : > On 2018-07-23 11:23 AM, olivier sallou wrote: > > Maybe a bug should be filled upstream > > Hello, > > Thank you for caring and putting time into this. > > The bug is in influxdb-python due to a breaking change in numpy. > > I already marked the bug as forwarded with a link to the upstream bug, > maybe you missed it? > - https://github.com/influxdata/influxdb-python/pull/596 > > > Forwarded tags don't appear in the discussion thread of the bug but they > appear on the top of the page: > - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902470 > > I just saw it on bug page some minutes ago :-) > The reason that tests pass with tox is that tox will download specific > versions of packages so it will not test with Debian's packages. > yes, this is what I saw. one of my packages depends on python-influxdb, this is why I care so much , my package will be removed if python-influxdb is removed. Looked at your pull request, but latest code update is still failing. If issue is really only related to a str/repr problem, then I suppose that we could skip the failing test in the meanwhile to close the bug or lower its severity waiting for an upstream fix. > > Cheers, > > -- > Alexandre Viau > av...@debian.org > >
Processed: Re: Bug#904319: FTBFS when building binary-packages only
Processing control commands: > severity -1 normal Bug #904319 [src:intel-mkl] FTBFS when building binary-packages only Warning: Unknown package 'src:intel-mkl' Severity set to 'normal' from 'serious' Warning: Unknown package 'src:intel-mkl' > tags -1 + moreinfo unreproducible Bug #904319 [src:intel-mkl] FTBFS when building binary-packages only Warning: Unknown package 'src:intel-mkl' Added tag(s) moreinfo and unreproducible. Warning: Unknown package 'src:intel-mkl' -- 904319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904319: FTBFS when building binary-packages only
Control: severity -1 normal Control: tags -1 + moreinfo unreproducible Hi Daniel On 23/07/2018 11:54, Daniel Baumann wrote: However, when locally rebuilding the package I saw that it wants to check the md5sum of the upstream tarball. This fails when building binary packages only, which should be possible. dpkg-buildpackage -b works fine for me. How did you obtain the source package and what error message did you see? Regards Graham
Bug#902470: Relates to numpy
On 2018-07-23 11:47 AM, olivier sallou wrote: > Looked at your pull request, but latest code update is still failing. Yeah, my pull requests makes no attempt to fix the bug, only show it. Previous Travis builds would pass because it used an older version of numpy. > If issue is really only related to a str/repr problem, then I suppose > that we could skip the failing test in the meanwhile to close the bug > or lower its severity waiting for an upstream fix. I'd be open to that, or maybe we can just ping xginn8 again. Cheers <3 -- Alexandre Viau av...@debian.org signature.asc Description: OpenPGP digital signature
Bug#904111: clamav-daemon causing deadlocks/blocking I/O.
Same here (6 Postfix front-end servers), non-systemd, non-GUI system running Debian Stretch. Downgrading to 0.99 is a workaround. ScanOnAccess is set to false. R. -- ___ It is better to remain silent and be thought a fool, than to speak aloud and remove all doubt. +--+ | Richard Lucassen, Utrecht| +--+
Processed: [bts-link] source package src:php-db
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:php-db > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #889532 (http://bugs.debian.org/889532) > # Bug title: php-db FTBFS with PHP 7.2 > # * https://github.com/pear/DB/pull/5 > # * remote status changed: open -> closed > # * closed upstream > tags 889532 + fixed-upstream Bug #889532 [src:php-db] php-db FTBFS with PHP 7.2 Added tag(s) fixed-upstream. > usertags 889532 - status-open Usertags were: status-open. Usertags are now: . > usertags 889532 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 889532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:snapd
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:snapd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #897865 (http://bugs.debian.org/897865) > # Bug title: snapd: ftbfs with GCC-8 > # * https://github.com/snapcore/snapd/pull/5138 > # * remote status changed: (?) -> closed > # * closed upstream > tags 897865 + fixed-upstream Bug #897865 [src:snapd] snapd: ftbfs with GCC-8 Added tag(s) fixed-upstream. > usertags 897865 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 897865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897865 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:freefem++
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:freefem++ > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #897751 (http://bugs.debian.org/897751) > # Bug title: freefem++: ftbfs with GCC-8 > # * https://github.com/FreeFem/FreeFem-sources/issues/18 > # * remote status changed: (?) -> closed > # * closed upstream > tags 897751 + fixed-upstream Bug #897751 [src:freefem++] freefem++: ftbfs with GCC-8 Added tag(s) fixed-upstream. > usertags 897751 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 897751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:ruby-doorkeeper
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ruby-doorkeeper > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #903980 (http://bugs.debian.org/903980) > # Bug title: ruby-doorkeeper: CVE-2018-1000211: Public apps can't revoke > OAuth access & refresh tokens in Doorkeeper > # * https://github.com/doorkeeper-gem/doorkeeper/issues/891 > # * remote status changed: (?) -> closed > # * closed upstream > tags 903980 + fixed-upstream Bug #903980 [src:ruby-doorkeeper] ruby-doorkeeper: CVE-2018-1000211: Public apps can't revoke OAuth access & refresh tokens in Doorkeeper Added tag(s) fixed-upstream. > usertags 903980 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 903980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 904369 is forwarded to https://github.com/zalando/patroni/issues/750
Processing commands for cont...@bugs.debian.org: > forwarded 904369 https://github.com/zalando/patroni/issues/750 Bug #904369 [patroni] patroni: fails to install with Python 3.7 Set Bug forwarded-to-address to 'https://github.com/zalando/patroni/issues/750'. > thanks Stopping processing here. Please contact me if you need assistance. -- 904369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904369: Bug #904369 in patroni marked as pending
Control: tag -1 pending Hello, Bug #904369 in patroni 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/postgresql/patroni/commit/21872714586ca7cf16282295cdf8e038ce2ee3de Avoid using "async" which is a keyword in python3.7. Closes: #904369. (this message was generated automatically) -- Greetings https://bugs.debian.org/904369
Processed: Bug #904369 in patroni marked as pending
Processing control commands: > tag -1 pending Bug #904369 [patroni] patroni: fails to install with Python 3.7 Added tag(s) pending. -- 904369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python3-doublex: fails to install with Python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 902757 902646 903526 903030 902650 902900 903826 904365 904370 904373 903423 904369 903527 903522 903558 902761 902631 903145 903784 902715 903529 904357 904361 904351 904364 903031 904363 903525 902794 904358 902989 902766 904298 904343 903016 904350 903528 904368 904371 903388 902817 903218 904367 904381 903457 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904382 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#904381: python3-dns: fails to install with Python 3.7
Package: python3-dns Version: 3.1.1-1 Severity: serious Tags: sid buster User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3-dns (3.1.1-1) ... File "/usr/lib/python3/dist-packages/DNS/Base.py", line 96 self.async=None ^ SyntaxError: invalid syntax dpkg: error processing package python3-dns (--configure): installed python3-dns package post-installation script subprocess returned error exit status 1 "async" has become a reserved keyword in Python 3.7 cheers, Andreas python3-dns=3.1.1-1.log.gz Description: application/gzip
Bug#904382: python3-doublex: fails to install with Python 3.7
Package: python3-doublex Version: 1.8.2-1 Severity: serious Tags: sid buster User: debian...@lists.debian.org Usertags: piuparts Control: block 902788 with -1 Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Setting up python3-doublex (1.8.2-1) ... File "/usr/lib/python3/dist-packages/doublex/matchers.py", line 129 def async(self, timeout): ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/doublex/test/async_race_condition_test.py", line 39 assert_that(spy.write, called().async(1)) ^ SyntaxError: invalid syntax File "/usr/lib/python3/dist-packages/doublex/test/unit_tests.py", line 1333 assert_that(spy.write, called().async(timeout=1)) ^ SyntaxError: invalid syntax dpkg: error processing package python3-doublex (--configure): installed python3-doublex package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: python3-doublex "async" has become a reserved keyword in Python 3.7 cheers, Andreas python3-doublex=1.8.2-1.log.gz Description: application/gzip
Processed: python3-dns: fails to install with Python 3.7
Processing control commands: > block 902788 with -1 Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules broken by 3.7 902788 was blocked by: 903525 903030 902989 903558 902794 902715 904343 903528 903423 903388 902646 904298 904364 904357 903784 904368 903522 902761 904369 904350 902631 902817 903016 904371 904367 903218 903031 903145 904363 904365 903527 902766 904373 904358 903526 904370 902900 902650 903826 904351 904361 903457 902757 903529 902788 was blocking: 902582 903432 Added blocking bug(s) of 902788: 904381 -- 902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788 904381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904381 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
